[Touch-packages] [Bug 1723239] Re: libxatracker2 update causes problems with Lenovo notebooks

2018-05-08 Thread Rhonda D'Vine
** Also affects: mesa (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: pkg-website
   Status: New => Invalid

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

Title:
  libxatracker2 update causes problems with Lenovo notebooks

Status in pkg-website:
  Invalid
Status in mesa package in Ubuntu:
  New

Bug description:
  Lenovo IdeaPad 510-15IKB, Mint 18.2, installed 3 days ago. Apt-get
  update && apt-get upgrade clean was being applied after every
  istallation. Everything worked fine. One moment, I decided to apply
  available system updates via system security center (shield sign in
  tray). After that WiFi started to disconnect in about 7-10 minutes
  after system restart. Reproduced in 100% cases.

  I tried to update Linux core. Initially it was 4.10.037, I tried
  4.11.0-13, then 4.11.0-14 - no effect, 100% as it was.

  Then I decided to rollback packages. There were 6 ones updated during
  system update. I was removing them one by one (via apt-get remove),
  removed 2 of them (every time reloaded laptop, and applied update-
  upgrade), there was no effect till I removed libxatracker2, WiFi
  returned to stable working. Update center reported that the package
  was updated from 12.0.6 (Ubuntu 16.04.1) (stable behavior) to 17.0.7
  (Ubuntu 16.04.2) - problems started just after this. Hopeful, this
  helps. Being clear, it is still not perfect so far but better than 2
  hours ago... may be I need laptop with non-realtek WiFi.

  Regards, Serge.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pkg-website/+bug/1723239/+subscriptions

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


[Touch-packages] [Bug 1747411] Re: Change of default database file format to SQL

2018-05-08 Thread ChristianEhrhardt
** Merge proposal linked:
   https://code.launchpad.net/~paelzer/ubuntu/+source/nss/+git/nss/+merge/345213

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

Title:
  Change of default database file format to SQL

Status in certmonger package in Ubuntu:
  Fix Released
Status in corosync package in Ubuntu:
  New
Status in dogtag-pki package in Ubuntu:
  Fix Released
Status in freeipa package in Ubuntu:
  Fix Released
Status in libapache2-mod-nss package in Ubuntu:
  Won't Fix
Status in nss package in Ubuntu:
  New

Bug description:
  nss in version 3.35 in upstream changed [2] the default file format [1] (if 
no explicit one is specified).
  For now we reverted that change in bug 1746947 until all packages depending 
on it are ready to work with that correctly.

  This bug here is about to track when the revert can be dropped.
  Therefore we list all known-to-be-affected packages and once all are resolved 
this can be dropped.

  [1]: https://fedoraproject.org/wiki/Changes/NSSDefaultFileFormatSql
  [2]: 
https://github.com/nss-dev/nss/commit/33b114e38278c4ffbb6b244a0ebc9910e5245cd3

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

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


[Touch-packages] [Bug 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.

2018-05-08 Thread Dylan Borg
Can't canonical turn libcurl3 into a transitional package for libcurl4?
When I did so manually I got stuff to work fine. Most 3rd party binaries
use dot target libcurl3 as there was no libcurl4 package when in fact
they'd work fine against libcurl4 since the ABI did nto change between
curl 3 and 4, only the headers got changed. Please have this fixed. An
LTS should be reliable in every aspect including the fact that it should
not break installs.

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

Title:
  After last updated libcurl3 on libcurl4, some apps are removed.

Status in curl package in Ubuntu:
  Confirmed

Bug description:
  Hi!

  After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) 
deleted such applications as:
  virtualbox-5.2
  opera-stable
  slack-desktop

  I really need these applications, I installed them with broken
  dependencies, but they are deleted after each update. Is it possible
  to make the dependence of the libcurl3 in libcurl4, and not remove it
  altogether from system?

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

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


[Touch-packages] [Bug 1742954] Re: glib-pacrunner crashed on PAC file - proxy settingy and environment settings remain unset

2018-05-08 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: glib-networking (Ubuntu)
   Status: New => Confirmed

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

Title:
  glib-pacrunner crashed on PAC file - proxy settingy and environment
  settings remain unset

Status in glib-networking package in Ubuntu:
  Confirmed

Bug description:
  # lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  $ LANG=C apt-cache policy glib-networking
  glib-networking:
Installed: 2.54.1-2
Candidate: 2.54.1-2
Version table:
   *** 2.54.1-2 500
  500 http://cz.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  
  Expected behavoir:
  Setting "Proxy Automatic" or "Proxy Automatic with PAC file URL" in Network 
manager should result in setting HTTP (and others) proxy for GNOME and 
environment variables for terminal applications.

  
  What happened: 
  When I set network manager for using Automatic settings 
  (Automatic proxy settings with PAC file URL or without URL). 

  glib-pacrunner is crashing every time i reconnect network interface to
  LAN or WiFi with PAC


  It is probably the same bug reported a repaired HERE: 
  https://codereview.qt-project.org/#/c/200463/

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: glib-networking-services 2.54.1-2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 12 14:39:47 2018
  InstallationDate: Installed on 2018-01-06 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  SourcePackage: glib-networking
  UpgradeStatus: Upgraded to bionic on 2018-01-12 (0 days ago)

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

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


[Touch-packages] [Bug 1768797] Re: LivePatch in Software & Updates shows that LP is not enabled when the U1 account has expired in g-o-a

2018-05-08 Thread Will Cooke
Ah yeah, you're right.  It is still checked, but is greyed out.

However, I think that is still misleading as, to me at least, it implies
that LivePatch isn't working because I'm not signed in.

Am I right in thinking that you can still disabled LP if the u1 account
has expired?  If so I think that if LP is active and can be disabled in
this state, then it should be possible to disable it without having to
refresh the u1 creds.

But, we should get input from design.

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

Title:
  LivePatch in Software & Updates shows that LP is not enabled when the
  U1 account has expired in g-o-a

Status in gnome-online-accounts package in Ubuntu:
  Incomplete

Bug description:
  I enabled LivePatch via gnome-initial-setup and added my U1 account to
  g-o-a.

  My U1 account gets marked as expired quite often.  When it's expired
  the LP entry in Software & Updates is not ticked to show that LP is
  running.  When my u1 account is re-authenticated then everything shows
  correctly.

  This could make it seem that LivePatch does not run if your account
  expires, which is not the case.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1768797/+subscriptions

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


[Touch-packages] [Bug 1767283] Re: nc doesn't support "-s IP" option

2018-05-08 Thread ChristianEhrhardt
1.190-2 is in cosmic-proposed, but right now some tests still fail for 
18.10/Cosmic not being fully open (e.g. no autotest/cloud images or missing 
18.10 in postgres common.
So I have to beg your pardon to wait a bit more :-/

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

Title:
  nc doesn't support "-s IP" option

Status in netcat-openbsd package in Ubuntu:
  Confirmed
Status in netcat-openbsd package in Debian:
  Fix Released

Bug description:
  Hey,

  netcat shows a usage error if i try to use the "-s" option:

  Example in Bionic:

  $ netcat -s 127.0.0.1 127.0.0.1 22 < /dev/null
  usage: nc [-46CDdFhklNnrStUuvZz] [-I length] [-i interval] [-M ttl]
     [-m minttl] [-O length] [-P proxy_username] [-p source_port]
     [-q seconds] [-s source] [-T keyword] [-V rtable] [-W recvlimit] [-w 
timeout]
     [-X proxy_protocol] [-x proxy_address[:port]][destination] [port]

  Example in Xenial:

  netcat -s 127.0.0.1 127.0.0.1 22 < /dev/null
  SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.4

  Manpage shows that the option is still availible and should work. Both
  systems use openbsd netcat.

  $ type netcat
  netcat is hashed (/bin/netcat)
  $ ls -lah /bin/netcat
  lrwxrwxrwx 1 root root 24 Apr 25 21:56 /bin/netcat -> /etc/alternatives/netcat
  $ ls -lah /etc/alternatives/netcat
  lrwxrwxrwx 1 root root 15 Apr 25 21:56 /etc/alternatives/netcat -> 
/bin/nc.openbsd

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: netcat-openbsd 1.187-1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri Apr 27 13:41:20 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libbsd0 0.8.7-1
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: netcat-openbsd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1759300] Re: Gnome Shell: Touchpad right click (bottom right) area does not work

2018-05-08 Thread Javier
I have an Acer Aspire 3 and Ubuntu 18.04, the touchpad works correctly 
according to the gnome configuration, that is, a finger anywhere is primary or 
left click, two fingers is secondary or right click and three fingers central 
click. However my notebook also has two physical buttons, left and right. The 
left behaves as it should, but the right behaves like left (that is, the two 
behave as a primary button).
Of course it is very comfortable behavior with the default configuration and no 
need to use physical buttons (in fact, I do not think that use in the future), 
but it is a small inconvenience that the right physical button behaves as left. 
Maybe a small correction is not difficult.
In ubuntu 16.04 both physical buttons worked as expected.
Anyway, I congratulate the developers for such a wonderful user experience!

Regards...
Javier Beluge

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

Title:
  Gnome Shell: Touchpad right click (bottom right) area does not work

Status in gsettings-desktop-schemas package in Ubuntu:
  Invalid

Bug description:
  The right (second) touchpad click does not work.
  It ceased to work about three months ago.
  ubuntu 18,04 aser ex2519

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1759300/+subscriptions

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


[Touch-packages] [Bug 1769480] Re: Ubuntu 18.04 - networkmanager dont show other wifi after few minutes

2018-05-08 Thread lnly
There are no usefull logfiles. Either dmesg nor syslog show anything usefull.
I am connected now. Problem exists like always.

dmesg only show the mac-addresses (privacy) that its connecting to.

syslog only show no errors. Just:
NetworkManager[804]:   [1525771468.8177] manager: NetworkManager state is 
now CONNECTED_GLOBAL
systemd[1]: Starting Network Manager Script Dispatcher Service...
dbus-daemon[758]: [system] Activating via systemd: service 
name='org.freedesktop.nm_dispatcher' 
unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.14' (uid=0 
pid=804 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
systemd[1]: Started Network Manager Script Dispatcher Service.
dbus-daemon[758]: [system] Successfully activated service 
'org.freedesktop.nm_dispatcher'
nm-dispatcher: req:1 'connectivity-change': new request (1 scripts)
nm-dispatcher: req:1 'connectivity-change': start running ordered scripts...
whoopsie[934]: [xx:xx:xx] online (i removed the time)

It then synchronised with the time and that was it. Not a single error
in the logfile.

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

Title:
  Ubuntu 18.04 - networkmanager dont show other wifi after few minutes

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  how to reproduce:

  dd the iso to an usb drive and boot from it.
  List all wifi devices in live-mode and connect to one of it. Use the web for 
some minutes. Open up the wifi on the top right again and list the available 
networks - it dont show any others any more. Just the one you are connected to.

  How to overcome the bug: put the computer into airplane mode and go
  away from airplane mode again. Or: disconnect the usb wifi device and
  connect it again.

  Does this bug exist also on installed 18.04 and updated to last (apt update, 
apt upgrade, apt dist-upgrade)?
  Yes

  What wifi device is been used:
  ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 3572, rev 0223 detected
  ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 0009 detected
  ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
  usbcore: registered new interface driver rt2800usb
  ...
  ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 
'rt2870.bin'
  ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - 
version: 0.36

  uname -a
  Linux t 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 
x86_64 x86_64 GNU/Linux

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

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


[Touch-packages] [Bug 1769316] Re: Notification of Live patch sign-in is inconsistent depending on how Software & Updates is started

2018-05-08 Thread Andrea Azzarone
The problem is that synaptic launches software-properties-gtk has root.
Marking as low considering that synaptic is not officially supported.

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

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

Title:
  Notification of Live patch sign-in is inconsistent depending on how
  Software & Updates is started

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  This issue has I think been partly covered in other bug reports that
  are currently marked incomplete but none describe my exact issue with
  Livepatch signing in..

  I'm creating this report in the hope that it does provide enough
  information with regards to what I am seeing here and have been doing
  so since before the release of Ubuntu 18.04.

  Last night I enabled Livepatch by signing into the appropriate tab of
  Software & Updates. As a result of briefly discussing this elsewhere I
  decided to check whether I was still logged in or not.

  1) I started synaptic and pulled up "Software & Updates" from the
  Settings menu. The Updates tab shows the Livepatch box as being
  checked but a message of "To use Livepatch you need to sign in" and a
  Sign-in button is displayed. If I attempt to sign in I see a "Choose
  an account" dialog. Clicking on "Sign in.." displays an empty panel
  with "Devices" in the top left corner. This is obviously the Settings
  application with no text being displayed.

  2) I then started "Software & Updates" as a stand alone application.
  The Updates tab shows that I am signed in, my email address is shown
  along with a "Sign out" button and the message "Use Canonical
  Livepatch to increase security between restarts is displayed
  immediately above.

  Restarting "Software & Updates" alternately through synaptic and as a
  stand alone application shows either an unsuccessful login or a
  successful log-in as described in points 1) and 2).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: software-properties-gtk 0.96.24.32.1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat May  5 08:38:38 2018
  InstallationDate: Installed on 2017-11-07 (178 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to bionic on 2018-02-21 (72 days ago)

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

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


[Touch-packages] [Bug 1769324] Re: canonical-livepatch: unable to enable it through software-properties-gtk

2018-05-08 Thread Andrea Azzarone
What happens if you click on "Accedi..." ?

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

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

Title:
  canonical-livepatch: unable to enable it through software-properties-
  gtk

Status in software-properties package in Ubuntu:
  Incomplete

Bug description:
  Trying to enable canonical-livepatch through software-properties-gtk, the 
application itself gets stuck on access window.
  Nothing happens.

  Even when trying to enable canonical-livepatch through a terminal,
  running: sudo canonical-livepatch enable  I receive the message:
  "canonical-livepatch command not found"

  I succeded running the command through gksu

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: software-properties-gtk 0.96.24.32.1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat May  5 11:06:30 2018
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1765819] Re: Canonical Livepatch snap cannot be installed

2018-05-08 Thread Andrea Azzarone
What if you try to install from the terminal?

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

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

Title:
  Canonical Livepatch snap cannot be installed

Status in software-properties package in Ubuntu:
  Incomplete

Bug description:
  I was trying to setup livepatch in software-properties and got the
  following error message:

  "Canonical Livepatch snap cannot be installed"

  How do I go about sorting that out?

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

-- 
Mailing list: https://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 1769324] Re: canonical-livepatch: unable to enable it through software-properties-gtk

2018-05-08 Thread vimo
Il mar 8 mag 2018, 12:11 Andrea Azzarone  ha
scritto:

> What happens if you click on "Accedi..." ?
>
>
> Absolutely nothing. I tried several times waiting up to 20 minutes.
>


>

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

Title:
  canonical-livepatch: unable to enable it through software-properties-
  gtk

Status in software-properties package in Ubuntu:
  Incomplete

Bug description:
  Trying to enable canonical-livepatch through software-properties-gtk, the 
application itself gets stuck on access window.
  Nothing happens.

  Even when trying to enable canonical-livepatch through a terminal,
  running: sudo canonical-livepatch enable  I receive the message:
  "canonical-livepatch command not found"

  I succeded running the command through gksu

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: software-properties-gtk 0.96.24.32.1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat May  5 11:06:30 2018
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1768755] Re: Missing links to libGL.so and libglapi.so

2018-05-08 Thread Roland65
OK, thanks for the info and sorry for the noise.

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

Title:
  Missing links to libGL.so and libglapi.so

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  In Ubuntu 18.04, the package libgl1-mesa-dev:amd64 does not contain
  the symbolic links libGL.so and libglapi.so.

  Thus, it is not possible to use the -lGL option to compile a
  program...

  System: Ubuntu 18.04 LTS (Bionic Beaver) 64-bit
  Package: libgl1-mesa-dev:amd64 18.0.0~rc5-1ubuntu1

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

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


[Touch-packages] [Bug 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work

2018-05-08 Thread Azur
No, thx bro. It should work out of the box, i have back to my "working"
windows 7...

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

Title:
  Lenovo Y700-17ISK subwoofer doesn't work

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB)
  Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 
4.4.0-10-generic, nvidia 361.28)

  Problem: Notebook subwoofer doesn't work.

  Judging from alsa-info.sh output, there is no pin declared for the bass 
output by BIOS.
  Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins'

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-10-generic 4.4.0-10.25
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aljosa 1776 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Mar  6 11:02:21 2016
  HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125
  InstallationDate: Installed on 2016-03-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  MachineType: LENOVO 80Q0
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed 
root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-10-generic N/A
   linux-backports-modules-4.4.0-10-generic  N/A
   linux-firmware1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CDCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Allsparks 7A
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad Y700-17ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK:
  dmi.product.name: 80Q0
  dmi.product.version: Lenovo ideapad Y700-17ISK
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1768232] Re: Stuck at ubuntu logo while booting after installing Ubuntu 18.04 (i915 driver issue)

2018-05-08 Thread d a i s y
** Summary changed:

- i915 driver issue in Ubuntu 18.04
+ Stuck at ubuntu logo while booting after installing Ubuntu 18.04 (i915 driver 
issue)

** Summary changed:

- Stuck at ubuntu logo while booting after installing Ubuntu 18.04 (i915 driver 
issue)
+ Stuck at ubuntu logo while booting after installing Ubuntu 18.04 (Resolution 
1024x768 after nomodeset, i915 driver issue)

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

Title:
  Stuck at ubuntu logo while booting after installing Ubuntu 18.04
  (Resolution 1024x768 after nomodeset, i915 driver issue)

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  My system stuck at ubuntu logo while booting. To resolve it, I've set
  nomodeset.

  But now it occurs a resolution issue to 1024x768. Here are the
  necessary information:

  lspci -nnk | grep -iA2 vga
  00:02.0 VGA compatible controller [0300]: Intel Corporation 82945G/GZ 
Integrated Graphics Controller [8086:2772] (rev 02)
  Subsystem: Hewlett-Packard Company 82945G/GZ Integrated Graphics 
Controller [103c:302a]
  Kernel modules: i915, intelfb

  and

  xrandr
  xrandr: Failed to get size of gamma for output default
  Screen 0: minimum 1024 x 768, current 1024 x 768, maximum 1024 x 768
  default connected primary 1024x768+0+0 0mm x 0mm
     1024x768  76.00*

  Output of sudo lshw -c display

  *-display UNCLAIMED
     description: VGA compatible controller
     product: 82945G/GZ Integrated Graphics Controller
     vendor: Intel Corporation
     physical id: 2
     bus info: pci@:00:02.0
     version: 02
     width: 32 bits
     clock: 33MHz
     capabilities: msi pm vga_controller bus_master cap_list
     configuration: latency=0
     resources: memory:e200-e207 ioport:c000(size=8) 
memory:d000-dfff memory:e208-e20b memory:c-d

  This issue occurred only after installing it, not when I choose 'Try
  without Installing', I don't need to set nomodeset in that case.

  Intel Graphics Update Tool shows:

  Checking if Intel graphics card available...
    • checking for i915 module in /sys/module
    • i915 module found
  Checking if Intel graphics card available... OK
  Retrieving information from 01.org...
    • fetching https://download.01.org/gfx/ilg-config.cfg
    • saving to /home/test/.ilg-config
    • fetched 1626 bytes
    • fetched 9818 bytes
    • fetched 12301 bytes
    • looking up [Ubuntu bionic] configuration
  Retrieving information from 01.org... OK
  Checking distribution... Failed

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  1 17:16:20 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 
02) (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company 82945G/GZ Integrated Graphics 
Controller [103c:302a]
  InstallationDate: Installed on 2018-05-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Hewlett-Packard HP dx2080 MT(KS826PA)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=7ec4f610-9b62-44f3-867d-01abd93de14d ro quiet splash nomodeset 
vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section "Device"
    Identifier "Intel Graphics"
    Driver "intel"
    Option "AccelMethod" "uxa"
   EndSection
  dmi.bios.date: 11/28/2007
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: V1.03
  dmi.board.name: 0AD8h
  dmi.board.vendor: Board Manufacturer
  dmi.chassis.asset.tag: INA8100LFY
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrV1.03:bd11/28/2007:svnHewlett-Packard:pnHPdx2080MT(KS826PA):pvr:rvnBoardManufacturer:rn0AD8h:rvr:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: HP dx2080 MT(KS826PA)
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91+git1804271336.50426f~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2~git1804301930.1c5f4f~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2~git1804301930.1c5f4f~oibaf~b
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-i

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

2018-05-08 Thread niconil
** Bug watch added: Debian Bug tracker #898177
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898177

** Changed in: cron (Debian)
   Importance: Undecided => Unknown

** Changed in: cron (Debian)
   Status: New => Unknown

** Changed in: cron (Debian)
 Remote watch: None => Debian Bug tracker #898177

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

Title:
  cron doesn't support MAILFROM

Status in cron package in Ubuntu:
  Triaged
Status in cron package in Debian:
  Unknown

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

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

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

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

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

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

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


[Touch-packages] [Bug 1765531] ProcEnviron.txt

2018-05-08 Thread Battant
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1765531/+attachment/5136037/+files/ProcEnviron.txt

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

Title:
  python 2.7 UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in
  position 56: ordinal not in range(128)

Status in python2.7 package in Ubuntu:
  New

Bug description:
  Hello,

  I have eclipse 4.7

  https://www.eclipse.org/downloads/

  
  vim

  and openjdk-8-jre

  I just try to install eclim

  http://eclim.org/

  Here us my install process log

  ./eclim_2.7.2.bin 
  Welcome to the installer for eclim 2.7.2.

  Please specify the root directory of your eclipse install.
Ex: /opt/eclipse
/usr/local/eclipse

  
  Please specify the directory where you would like the eclim vimfiles 
installed.
  If you do not want to install the vimfiles (eg: emacs-eclim users), then 
type: skip
Ex: ~/.vim
~/.vim/bundle/eclim
  > ../.vim

  Choose which eclim features you would like to install.
  Type the number for each feature you want to install:
Ex (Java and Python): 0 5
Ex (Java and Python): 0,5
Ex (Java, Web, and C/C++): 0-2
  0) Java Development
  1) Web Development
  2) C/C++ Development
  3) Ruby Development
  4) Php Development
  5) Python Development
  6) Scala Development
  7) Groovy Development
  8) Android Development
  > 5
  Eclim plugins to install:
Python Development
  Is this correct? (y/n): y

  running: ['java', '-Djava.net.useSystemProxies=true', '-jar', 
'/home/mparchet/Applications_d\xc3\xa9veloppement/rcp-oxygen2/eclipse/plugins/org.eclipse.equinox.launcher_1.4.0.v20161219-1356.jar',
 '-initialize', '-debug'] ... Traceback (most recent call last):
File "/tmp/eclim-installer.6Bte/install", line 1205, in 
  main()
File "/tmp/eclim-installer.6Bte/install", line 96, in main
  install(options, eclim)
File "/tmp/eclim-installer.6Bte/install", line 116, in install
  step_dependencies(options, eclipse, plugins)
File "/tmp/eclim-installer.6Bte/install", line 361, in step_dependencies
  eclipse.gc()
File "/tmp/eclim-installer.6Bte/install", line 921, in gc
  '-application', 'org.eclipse.equinox.p2.garbagecollector.application',
File "/tmp/eclim-installer.6Bte/install", line 929, in execute
  self._initialize()
File "/tmp/eclim-installer.6Bte/install", line 900, in _initialize
  info = self.execute('-initialize', '-debug')
File "/tmp/eclim-installer.6Bte/install", line 936, in execute
  stdout, stderr = execute(cmd)
File "/tmp/eclim-installer.6Bte/install", line 624, in execute
  stdout = stdout.decode()
  UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 56: 
ordinal not in range(128)

  Could you help me please to fix this bug ?

  Thanks by advance for your support

  Best regards

  Battant

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: python2.7 2.7.15~rc1-1
  ProcVersionSignature: Ubuntu 4.15.0-17.18-generic 4.15.17
  Uname: Linux 4.15.0-17-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 19 23:48:56 2018
  SourcePackage: python2.7
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-29 (8 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: python2.7 2.7.15~rc1-1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-21.22-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-21-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/python2.7/+bug/1765531/+subscriptions

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


[Touch-packages] [Bug 1769075] UdevDb.txt

2018-05-08 Thread Alan Lobo
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1769075/+attachment/5136050/+files/UdevDb.txt

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

Title:
  [regression][bionic] Bluetooth keyboard battery reports 0%

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d"
  reports always 0% as battery percentage of the bluetooth Logitech K810 
keyboard.
  Which is a bit annoying since I get a KDE warning on the battery.

  Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery
native-path:  hid-34:88:5d:5e:0c:2f-battery
model:Logitech K810
power supply: no
updated:  Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago)
has history:  yes
has statistics:   yes
keyboard
  present: yes
  rechargeable:yes
  state:   unknown
  warning-level:   none
  percentage:  0%
  icon-name:  'battery-missing-symbolic'

  My guess is that the issue is in the bluetooth rather in the upowerd
  since the reporting in the /sys/devices shows battery level of 0
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bnv1714 F pulseaudio
   /dev/snd/pcmC0D0p:   bnv1714 F...m pulseaudio
   /dev/snd/controlC0:  bnv1714 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf
  InstallationDate: Installed on 2017-11-02 (185 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  IwConfig:
   lono wireless extensions.
   
   enp0s25   no wireless extensions.
  MachineType: Dell Inc. Precision Tower 5810
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago)
  UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0K240Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision Tower 5810
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1769075] ProcInterrupts.txt

2018-05-08 Thread Alan Lobo
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1769075/+attachment/5136046/+files/ProcInterrupts.txt

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

Title:
  [regression][bionic] Bluetooth keyboard battery reports 0%

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d"
  reports always 0% as battery percentage of the bluetooth Logitech K810 
keyboard.
  Which is a bit annoying since I get a KDE warning on the battery.

  Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery
native-path:  hid-34:88:5d:5e:0c:2f-battery
model:Logitech K810
power supply: no
updated:  Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago)
has history:  yes
has statistics:   yes
keyboard
  present: yes
  rechargeable:yes
  state:   unknown
  warning-level:   none
  percentage:  0%
  icon-name:  'battery-missing-symbolic'

  My guess is that the issue is in the bluetooth rather in the upowerd
  since the reporting in the /sys/devices shows battery level of 0
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bnv1714 F pulseaudio
   /dev/snd/pcmC0D0p:   bnv1714 F...m pulseaudio
   /dev/snd/controlC0:  bnv1714 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf
  InstallationDate: Installed on 2017-11-02 (185 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  IwConfig:
   lono wireless extensions.
   
   enp0s25   no wireless extensions.
  MachineType: Dell Inc. Precision Tower 5810
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago)
  UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0K240Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision Tower 5810
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1769075] WifiSyslog.txt

2018-05-08 Thread Alan Lobo
apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1769075/+attachment/5136051/+files/WifiSyslog.txt

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

Title:
  [regression][bionic] Bluetooth keyboard battery reports 0%

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d"
  reports always 0% as battery percentage of the bluetooth Logitech K810 
keyboard.
  Which is a bit annoying since I get a KDE warning on the battery.

  Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery
native-path:  hid-34:88:5d:5e:0c:2f-battery
model:Logitech K810
power supply: no
updated:  Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago)
has history:  yes
has statistics:   yes
keyboard
  present: yes
  rechargeable:yes
  state:   unknown
  warning-level:   none
  percentage:  0%
  icon-name:  'battery-missing-symbolic'

  My guess is that the issue is in the bluetooth rather in the upowerd
  since the reporting in the /sys/devices shows battery level of 0
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bnv1714 F pulseaudio
   /dev/snd/pcmC0D0p:   bnv1714 F...m pulseaudio
   /dev/snd/controlC0:  bnv1714 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf
  InstallationDate: Installed on 2017-11-02 (185 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  IwConfig:
   lono wireless extensions.
   
   enp0s25   no wireless extensions.
  MachineType: Dell Inc. Precision Tower 5810
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago)
  UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0K240Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision Tower 5810
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1765531] ProcCpuinfoMinimal.txt

2018-05-08 Thread Battant
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1765531/+attachment/5136036/+files/ProcCpuinfoMinimal.txt

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

Title:
  python 2.7 UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in
  position 56: ordinal not in range(128)

Status in python2.7 package in Ubuntu:
  New

Bug description:
  Hello,

  I have eclipse 4.7

  https://www.eclipse.org/downloads/

  
  vim

  and openjdk-8-jre

  I just try to install eclim

  http://eclim.org/

  Here us my install process log

  ./eclim_2.7.2.bin 
  Welcome to the installer for eclim 2.7.2.

  Please specify the root directory of your eclipse install.
Ex: /opt/eclipse
/usr/local/eclipse

  
  Please specify the directory where you would like the eclim vimfiles 
installed.
  If you do not want to install the vimfiles (eg: emacs-eclim users), then 
type: skip
Ex: ~/.vim
~/.vim/bundle/eclim
  > ../.vim

  Choose which eclim features you would like to install.
  Type the number for each feature you want to install:
Ex (Java and Python): 0 5
Ex (Java and Python): 0,5
Ex (Java, Web, and C/C++): 0-2
  0) Java Development
  1) Web Development
  2) C/C++ Development
  3) Ruby Development
  4) Php Development
  5) Python Development
  6) Scala Development
  7) Groovy Development
  8) Android Development
  > 5
  Eclim plugins to install:
Python Development
  Is this correct? (y/n): y

  running: ['java', '-Djava.net.useSystemProxies=true', '-jar', 
'/home/mparchet/Applications_d\xc3\xa9veloppement/rcp-oxygen2/eclipse/plugins/org.eclipse.equinox.launcher_1.4.0.v20161219-1356.jar',
 '-initialize', '-debug'] ... Traceback (most recent call last):
File "/tmp/eclim-installer.6Bte/install", line 1205, in 
  main()
File "/tmp/eclim-installer.6Bte/install", line 96, in main
  install(options, eclim)
File "/tmp/eclim-installer.6Bte/install", line 116, in install
  step_dependencies(options, eclipse, plugins)
File "/tmp/eclim-installer.6Bte/install", line 361, in step_dependencies
  eclipse.gc()
File "/tmp/eclim-installer.6Bte/install", line 921, in gc
  '-application', 'org.eclipse.equinox.p2.garbagecollector.application',
File "/tmp/eclim-installer.6Bte/install", line 929, in execute
  self._initialize()
File "/tmp/eclim-installer.6Bte/install", line 900, in _initialize
  info = self.execute('-initialize', '-debug')
File "/tmp/eclim-installer.6Bte/install", line 936, in execute
  stdout, stderr = execute(cmd)
File "/tmp/eclim-installer.6Bte/install", line 624, in execute
  stdout = stdout.decode()
  UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 56: 
ordinal not in range(128)

  Could you help me please to fix this bug ?

  Thanks by advance for your support

  Best regards

  Battant

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: python2.7 2.7.15~rc1-1
  ProcVersionSignature: Ubuntu 4.15.0-17.18-generic 4.15.17
  Uname: Linux 4.15.0-17-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 19 23:48:56 2018
  SourcePackage: python2.7
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-29 (8 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: python2.7 2.7.15~rc1-1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-21.22-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-21-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/python2.7/+bug/1765531/+subscriptions

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


[Touch-packages] [Bug 1769880] [NEW] ubuntu 14.04 amd / ati radeon 6400/7400 video card is continuously requesting the monitor configuration

2018-05-08 Thread deivid
Public bug reported:

Hi, my ubuntu 14.04 amd / ati radeon 6400/7400 video card is
continuously requesting the monitor configuration, it has so many
requests that it looks like virus windows. I appreciate the help and
patience.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 4.4.0-31.50~14.04.1-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.27
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue May  8 09:29:55 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2018-03-06 (63 days ago)
InstallationMedia: Xubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug corruption trusty

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

Title:
  ubuntu 14.04 amd / ati radeon 6400/7400 video card is continuously
  requesting the monitor configuration

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi, my ubuntu 14.04 amd / ati radeon 6400/7400 video card is
  continuously requesting the monitor configuration, it has so many
  requests that it looks like virus windows. I appreciate the help and
  patience.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-31.50~14.04.1-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue May  8 09:29:55 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-03-06 (63 days ago)
  InstallationMedia: Xubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 
(20160803)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1769075] Lsusb.txt

2018-05-08 Thread Alan Lobo
apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1769075/+attachment/5136043/+files/Lsusb.txt

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

Title:
  [regression][bionic] Bluetooth keyboard battery reports 0%

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d"
  reports always 0% as battery percentage of the bluetooth Logitech K810 
keyboard.
  Which is a bit annoying since I get a KDE warning on the battery.

  Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery
native-path:  hid-34:88:5d:5e:0c:2f-battery
model:Logitech K810
power supply: no
updated:  Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago)
has history:  yes
has statistics:   yes
keyboard
  present: yes
  rechargeable:yes
  state:   unknown
  warning-level:   none
  percentage:  0%
  icon-name:  'battery-missing-symbolic'

  My guess is that the issue is in the bluetooth rather in the upowerd
  since the reporting in the /sys/devices shows battery level of 0
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bnv1714 F pulseaudio
   /dev/snd/pcmC0D0p:   bnv1714 F...m pulseaudio
   /dev/snd/controlC0:  bnv1714 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf
  InstallationDate: Installed on 2017-11-02 (185 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  IwConfig:
   lono wireless extensions.
   
   enp0s25   no wireless extensions.
  MachineType: Dell Inc. Precision Tower 5810
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago)
  UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0K240Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision Tower 5810
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1769075] CurrentDmesg.txt

2018-05-08 Thread Alan Lobo
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1769075/+attachment/5136040/+files/CurrentDmesg.txt

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

Title:
  [regression][bionic] Bluetooth keyboard battery reports 0%

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d"
  reports always 0% as battery percentage of the bluetooth Logitech K810 
keyboard.
  Which is a bit annoying since I get a KDE warning on the battery.

  Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery
native-path:  hid-34:88:5d:5e:0c:2f-battery
model:Logitech K810
power supply: no
updated:  Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago)
has history:  yes
has statistics:   yes
keyboard
  present: yes
  rechargeable:yes
  state:   unknown
  warning-level:   none
  percentage:  0%
  icon-name:  'battery-missing-symbolic'

  My guess is that the issue is in the bluetooth rather in the upowerd
  since the reporting in the /sys/devices shows battery level of 0
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bnv1714 F pulseaudio
   /dev/snd/pcmC0D0p:   bnv1714 F...m pulseaudio
   /dev/snd/controlC0:  bnv1714 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf
  InstallationDate: Installed on 2017-11-02 (185 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  IwConfig:
   lono wireless extensions.
   
   enp0s25   no wireless extensions.
  MachineType: Dell Inc. Precision Tower 5810
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago)
  UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0K240Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision Tower 5810
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1769075] ProcCpuinfoMinimal.txt

2018-05-08 Thread Alan Lobo
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1769075/+attachment/5136045/+files/ProcCpuinfoMinimal.txt

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

Title:
  [regression][bionic] Bluetooth keyboard battery reports 0%

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d"
  reports always 0% as battery percentage of the bluetooth Logitech K810 
keyboard.
  Which is a bit annoying since I get a KDE warning on the battery.

  Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery
native-path:  hid-34:88:5d:5e:0c:2f-battery
model:Logitech K810
power supply: no
updated:  Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago)
has history:  yes
has statistics:   yes
keyboard
  present: yes
  rechargeable:yes
  state:   unknown
  warning-level:   none
  percentage:  0%
  icon-name:  'battery-missing-symbolic'

  My guess is that the issue is in the bluetooth rather in the upowerd
  since the reporting in the /sys/devices shows battery level of 0
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bnv1714 F pulseaudio
   /dev/snd/pcmC0D0p:   bnv1714 F...m pulseaudio
   /dev/snd/controlC0:  bnv1714 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf
  InstallationDate: Installed on 2017-11-02 (185 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  IwConfig:
   lono wireless extensions.
   
   enp0s25   no wireless extensions.
  MachineType: Dell Inc. Precision Tower 5810
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago)
  UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0K240Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision Tower 5810
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1769075] RfKill.txt

2018-05-08 Thread Alan Lobo
apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1769075/+attachment/5136049/+files/RfKill.txt

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

Title:
  [regression][bionic] Bluetooth keyboard battery reports 0%

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d"
  reports always 0% as battery percentage of the bluetooth Logitech K810 
keyboard.
  Which is a bit annoying since I get a KDE warning on the battery.

  Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery
native-path:  hid-34:88:5d:5e:0c:2f-battery
model:Logitech K810
power supply: no
updated:  Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago)
has history:  yes
has statistics:   yes
keyboard
  present: yes
  rechargeable:yes
  state:   unknown
  warning-level:   none
  percentage:  0%
  icon-name:  'battery-missing-symbolic'

  My guess is that the issue is in the bluetooth rather in the upowerd
  since the reporting in the /sys/devices shows battery level of 0
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bnv1714 F pulseaudio
   /dev/snd/pcmC0D0p:   bnv1714 F...m pulseaudio
   /dev/snd/controlC0:  bnv1714 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf
  InstallationDate: Installed on 2017-11-02 (185 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  IwConfig:
   lono wireless extensions.
   
   enp0s25   no wireless extensions.
  MachineType: Dell Inc. Precision Tower 5810
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago)
  UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0K240Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision Tower 5810
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1769075] PulseList.txt

2018-05-08 Thread Alan Lobo
apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1769075/+attachment/5136048/+files/PulseList.txt

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

Title:
  [regression][bionic] Bluetooth keyboard battery reports 0%

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d"
  reports always 0% as battery percentage of the bluetooth Logitech K810 
keyboard.
  Which is a bit annoying since I get a KDE warning on the battery.

  Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery
native-path:  hid-34:88:5d:5e:0c:2f-battery
model:Logitech K810
power supply: no
updated:  Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago)
has history:  yes
has statistics:   yes
keyboard
  present: yes
  rechargeable:yes
  state:   unknown
  warning-level:   none
  percentage:  0%
  icon-name:  'battery-missing-symbolic'

  My guess is that the issue is in the bluetooth rather in the upowerd
  since the reporting in the /sys/devices shows battery level of 0
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bnv1714 F pulseaudio
   /dev/snd/pcmC0D0p:   bnv1714 F...m pulseaudio
   /dev/snd/controlC0:  bnv1714 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf
  InstallationDate: Installed on 2017-11-02 (185 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  IwConfig:
   lono wireless extensions.
   
   enp0s25   no wireless extensions.
  MachineType: Dell Inc. Precision Tower 5810
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago)
  UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0K240Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision Tower 5810
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1765531] Re: python 2.7 UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 56: ordinal not in range(128)

2018-05-08 Thread Battant
apport information

** Tags added: apport-collected

** Description changed:

  Hello,
  
  I have eclipse 4.7
  
  https://www.eclipse.org/downloads/
  
  
  vim
  
  and openjdk-8-jre
  
  I just try to install eclim
  
  http://eclim.org/
  
  Here us my install process log
  
  ./eclim_2.7.2.bin 
  Welcome to the installer for eclim 2.7.2.
  
  Please specify the root directory of your eclipse install.
Ex: /opt/eclipse
/usr/local/eclipse
  
  
  Please specify the directory where you would like the eclim vimfiles 
installed.
  If you do not want to install the vimfiles (eg: emacs-eclim users), then 
type: skip
Ex: ~/.vim
~/.vim/bundle/eclim
  > ../.vim
  
  Choose which eclim features you would like to install.
  Type the number for each feature you want to install:
Ex (Java and Python): 0 5
Ex (Java and Python): 0,5
Ex (Java, Web, and C/C++): 0-2
  0) Java Development
  1) Web Development
  2) C/C++ Development
  3) Ruby Development
  4) Php Development
  5) Python Development
  6) Scala Development
  7) Groovy Development
  8) Android Development
  > 5
  Eclim plugins to install:
Python Development
  Is this correct? (y/n): y
  
  running: ['java', '-Djava.net.useSystemProxies=true', '-jar', 
'/home/mparchet/Applications_d\xc3\xa9veloppement/rcp-oxygen2/eclipse/plugins/org.eclipse.equinox.launcher_1.4.0.v20161219-1356.jar',
 '-initialize', '-debug'] ... Traceback (most recent call last):
File "/tmp/eclim-installer.6Bte/install", line 1205, in 
  main()
File "/tmp/eclim-installer.6Bte/install", line 96, in main
  install(options, eclim)
File "/tmp/eclim-installer.6Bte/install", line 116, in install
  step_dependencies(options, eclipse, plugins)
File "/tmp/eclim-installer.6Bte/install", line 361, in step_dependencies
  eclipse.gc()
File "/tmp/eclim-installer.6Bte/install", line 921, in gc
  '-application', 'org.eclipse.equinox.p2.garbagecollector.application',
File "/tmp/eclim-installer.6Bte/install", line 929, in execute
  self._initialize()
File "/tmp/eclim-installer.6Bte/install", line 900, in _initialize
  info = self.execute('-initialize', '-debug')
File "/tmp/eclim-installer.6Bte/install", line 936, in execute
  stdout, stderr = execute(cmd)
File "/tmp/eclim-installer.6Bte/install", line 624, in execute
  stdout = stdout.decode()
  UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 56: 
ordinal not in range(128)
  
  Could you help me please to fix this bug ?
  
  Thanks by advance for your support
  
  Best regards
  
  Battant
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: python2.7 2.7.15~rc1-1
  ProcVersionSignature: Ubuntu 4.15.0-17.18-generic 4.15.17
  Uname: Linux 4.15.0-17-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 19 23:48:56 2018
  SourcePackage: python2.7
  UpgradeStatus: No upgrade log present (probably fresh install)
+ --- 
+ ApportVersion: 2.20.9-0ubuntu7
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2018-04-29 (8 days ago)
+ InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
+ Package: python2.7 2.7.15~rc1-1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 4.15.0-21.22-generic 4.15.17
+ Tags:  bionic
+ Uname: Linux 4.15.0-21-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1765531/+attachment/5136035/+files/Dependencies.txt

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

Title:
  python 2.7 UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in
  position 56: ordinal not in range(128)

Status in python2.7 package in Ubuntu:
  New

Bug description:
  Hello,

  I have eclipse 4.7

  https://www.eclipse.org/downloads/

  
  vim

  and openjdk-8-jre

  I just try to install eclim

  http://eclim.org/

  Here us my install process log

  ./eclim_2.7.2.bin 
  Welcome to the installer for eclim 2.7.2.

  Please specify the root directory of your eclipse install.
Ex: /opt/eclipse
/usr/local/eclipse

  
  Please specify the directory where you would like the eclim vimfiles 
installed.
  If you do not want to install the vimfiles (eg: emacs-eclim users), then 
type: skip
Ex: ~/.vim
~/.vim/bundle/eclim
  > ../.vim

  Choose which eclim features you would like to install.
  Type the number for each feature you want to install:
Ex (Java and Python): 0 5
Ex (Java and Python): 0,5
Ex (Java, Web, and C/C++): 0-2
  0) Java Development
  1) Web Development
  2) C/C++ Development
  3) Ruby Development
  4) Php Develop

[Touch-packages] [Bug 1769075] apport information

2018-05-08 Thread Alan Lobo
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  alan   1290 F pulseaudio
 /dev/snd/controlC0:  alan   1290 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2018-04-27 (10 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Dell Inc. XPS 13 9360
Package: linux (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=3161f6a4-dd39-499c-a6f2-bbe799f75e0c ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-20-generic N/A
 linux-backports-modules-4.15.0-20-generic  N/A
 linux-firmware 1.173
Tags:  bionic
Uname: Linux 4.15.0-20-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 01/18/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.3.2
dmi.board.name: 0839Y6
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0839Y6:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9360
dmi.sys.vendor: Dell Inc.

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

Title:
  [regression][bionic] Bluetooth keyboard battery reports 0%

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d"
  reports always 0% as battery percentage of the bluetooth Logitech K810 
keyboard.
  Which is a bit annoying since I get a KDE warning on the battery.

  Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery
native-path:  hid-34:88:5d:5e:0c:2f-battery
model:Logitech K810
power supply: no
updated:  Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago)
has history:  yes
has statistics:   yes
keyboard
  present: yes
  rechargeable:yes
  state:   unknown
  warning-level:   none
  percentage:  0%
  icon-name:  'battery-missing-symbolic'

  My guess is that the issue is in the bluetooth rather in the upowerd
  since the reporting in the /sys/devices shows battery level of 0
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bnv1714 F pulseaudio
   /dev/snd/pcmC0D0p:   bnv1714 F...m pulseaudio
   /dev/snd/controlC0:  bnv1714 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf
  InstallationDate: Installed on 2017-11-02 (185 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  IwConfig:
   lono wireless extensions.
   
   enp0s25   no wireless extensions.
  MachineType: Dell Inc. Precision Tower 5810
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago)
  UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0K240Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision Tower 5810
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1769075] IwConfig.txt

2018-05-08 Thread Alan Lobo
apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1769075/+attachment/5136041/+files/IwConfig.txt

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

Title:
  [regression][bionic] Bluetooth keyboard battery reports 0%

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d"
  reports always 0% as battery percentage of the bluetooth Logitech K810 
keyboard.
  Which is a bit annoying since I get a KDE warning on the battery.

  Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery
native-path:  hid-34:88:5d:5e:0c:2f-battery
model:Logitech K810
power supply: no
updated:  Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago)
has history:  yes
has statistics:   yes
keyboard
  present: yes
  rechargeable:yes
  state:   unknown
  warning-level:   none
  percentage:  0%
  icon-name:  'battery-missing-symbolic'

  My guess is that the issue is in the bluetooth rather in the upowerd
  since the reporting in the /sys/devices shows battery level of 0
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bnv1714 F pulseaudio
   /dev/snd/pcmC0D0p:   bnv1714 F...m pulseaudio
   /dev/snd/controlC0:  bnv1714 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf
  InstallationDate: Installed on 2017-11-02 (185 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  IwConfig:
   lono wireless extensions.
   
   enp0s25   no wireless extensions.
  MachineType: Dell Inc. Precision Tower 5810
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago)
  UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0K240Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision Tower 5810
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1769075] ProcModules.txt

2018-05-08 Thread Alan Lobo
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1769075/+attachment/5136047/+files/ProcModules.txt

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

Title:
  [regression][bionic] Bluetooth keyboard battery reports 0%

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d"
  reports always 0% as battery percentage of the bluetooth Logitech K810 
keyboard.
  Which is a bit annoying since I get a KDE warning on the battery.

  Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery
native-path:  hid-34:88:5d:5e:0c:2f-battery
model:Logitech K810
power supply: no
updated:  Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago)
has history:  yes
has statistics:   yes
keyboard
  present: yes
  rechargeable:yes
  state:   unknown
  warning-level:   none
  percentage:  0%
  icon-name:  'battery-missing-symbolic'

  My guess is that the issue is in the bluetooth rather in the upowerd
  since the reporting in the /sys/devices shows battery level of 0
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bnv1714 F pulseaudio
   /dev/snd/pcmC0D0p:   bnv1714 F...m pulseaudio
   /dev/snd/controlC0:  bnv1714 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf
  InstallationDate: Installed on 2017-11-02 (185 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  IwConfig:
   lono wireless extensions.
   
   enp0s25   no wireless extensions.
  MachineType: Dell Inc. Precision Tower 5810
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago)
  UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0K240Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision Tower 5810
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1769075] AlsaInfo.txt

2018-05-08 Thread Alan Lobo
apport information

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1769075/+attachment/5136038/+files/AlsaInfo.txt

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

Title:
  [regression][bionic] Bluetooth keyboard battery reports 0%

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d"
  reports always 0% as battery percentage of the bluetooth Logitech K810 
keyboard.
  Which is a bit annoying since I get a KDE warning on the battery.

  Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery
native-path:  hid-34:88:5d:5e:0c:2f-battery
model:Logitech K810
power supply: no
updated:  Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago)
has history:  yes
has statistics:   yes
keyboard
  present: yes
  rechargeable:yes
  state:   unknown
  warning-level:   none
  percentage:  0%
  icon-name:  'battery-missing-symbolic'

  My guess is that the issue is in the bluetooth rather in the upowerd
  since the reporting in the /sys/devices shows battery level of 0
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bnv1714 F pulseaudio
   /dev/snd/pcmC0D0p:   bnv1714 F...m pulseaudio
   /dev/snd/controlC0:  bnv1714 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf
  InstallationDate: Installed on 2017-11-02 (185 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  IwConfig:
   lono wireless extensions.
   
   enp0s25   no wireless extensions.
  MachineType: Dell Inc. Precision Tower 5810
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago)
  UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0K240Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision Tower 5810
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1767468] Re: Upgrade from 16.04 to 18.04, then uninstalling unity disables hardware acceleration

2018-05-08 Thread Thomas Mortagne
I reproduced the bug with the following:
* 17.10 itself upgraded from 17.04
* uninstalled Unity (to workaround a bug but I don't remember which one)
* upgrade to 18.04 today

-> hardware acceleration disabled

lspci:
> 00:02.0 VGA compatible controller: Intel Corporation Device 5a85 (rev 0b)

The workaround described in #6 worked like a charm for me.

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

Title:
  Upgrade from 16.04 to 18.04, then uninstalling unity disables hardware
  acceleration

Status in nux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 16.04 to 18.04 on a very plain Intel Skylake
  graphics, hardware acceleration is gone. Glxinfo and System
  Information report 'llvmpipe' (software rasterizer)

  It is caused by the file
  /etc/X11/Xsession.d/50_check_unity_support
  which can be deleted and then this problem goes away.

  > 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 520
  (rev 07)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libglvnd0 1.0.0-2ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 27 20:24:48 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-21 (735 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: libglvnd
  UpgradeStatus: Upgraded to bionic on 2018-04-26 (0 days ago)

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

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


[Touch-packages] [Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''

2018-05-08 Thread Iain Lane
Ah, I'm sorry, I didn't see that there had been a bionic upload for this
since the vcs was untouched and there was nothing in the unapproved
queue... I just uploaded ubiquity for this to *cosmic* - not bionic yet.
If it gets approved it should be in the next day's dailies and hopefully
someone can test those to verify it's good.

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

Title:
  [regression] ubiquity crashed in debconf.py:104 with ValueError:
  invalid literal for int() with base 10: ''

Status in cairo:
  Confirmed
Status in OEM Priority Project:
  Triaged
Status in cairo package in Ubuntu:
  In Progress
Status in ubiquity package in Ubuntu:
  In Progress
Status in cairo source package in Bionic:
  In Progress
Status in ubiquity source package in Bionic:
  In Progress

Bug description:
  * Impact
  The Ubuntu installer crashes on some machines (seems more often on hiDPI 
machines (QHD/UHD etc)).

  * Test case
  Try installing Ubuntu on an hidpi machine, it should complete installation 
instead of crashing.

  * Regression potential
  The fix in ubiquity touches the code handle uid drop/privilege, that can have 
unexpected side effects so we need proper/complete testing of the installer

  --

  Update: Actually the crash occurs on slow-ish systems due to a race
  condition. It's not strictly only hi-DPI machines - that's just the
  most common place it is experienced.

  ---

  https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
  https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15
  https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7
  https://errors.ubuntu.com/problem/cb82f70f9ede07369e8104da9ddf87e28b42257d
  https://errors.ubuntu.com/problem/84a5563af3d2b85f098da832ece4cb8450bfd524

  ---

  WORKAROUND:

  1. Boot into the live session.
  2. Settings > Devices > Displays > Scale = 100%
  3. Click Apply.
  4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".

  ---

  Crashed in a VM in the middle of installation. The host is Bionic up
  to date.

  From the journal
  Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3 
ip:7f5a76936961 sp:7ffde5090c50 error:0 in 
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
  Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
  Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 757, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 135, in run
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 505, in copy_all
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 + 
copy_progress)
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 83, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw: 
self.command(command, *args, **kw))
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
  Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
  Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for 
int() with base 10: ''

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ubiquity 18.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.388
  Date: Fri Feb 23 12:52:28 2018
  ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr 
keyboard-configuration/variantcode=oss
  InterpreterPath: /usr/bin/python3.6
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  Signal: 5
  SourcePackage: ubiquity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: ubiquity crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGro

[Touch-packages] [Bug 1769075] Lspci.txt

2018-05-08 Thread Alan Lobo
apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1769075/+attachment/5136042/+files/Lspci.txt

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

Title:
  [regression][bionic] Bluetooth keyboard battery reports 0%

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d"
  reports always 0% as battery percentage of the bluetooth Logitech K810 
keyboard.
  Which is a bit annoying since I get a KDE warning on the battery.

  Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery
native-path:  hid-34:88:5d:5e:0c:2f-battery
model:Logitech K810
power supply: no
updated:  Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago)
has history:  yes
has statistics:   yes
keyboard
  present: yes
  rechargeable:yes
  state:   unknown
  warning-level:   none
  percentage:  0%
  icon-name:  'battery-missing-symbolic'

  My guess is that the issue is in the bluetooth rather in the upowerd
  since the reporting in the /sys/devices shows battery level of 0
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bnv1714 F pulseaudio
   /dev/snd/pcmC0D0p:   bnv1714 F...m pulseaudio
   /dev/snd/controlC0:  bnv1714 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf
  InstallationDate: Installed on 2017-11-02 (185 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  IwConfig:
   lono wireless extensions.
   
   enp0s25   no wireless extensions.
  MachineType: Dell Inc. Precision Tower 5810
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago)
  UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0K240Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision Tower 5810
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1769075] CRDA.txt

2018-05-08 Thread Alan Lobo
apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1769075/+attachment/5136039/+files/CRDA.txt

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

Title:
  [regression][bionic] Bluetooth keyboard battery reports 0%

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d"
  reports always 0% as battery percentage of the bluetooth Logitech K810 
keyboard.
  Which is a bit annoying since I get a KDE warning on the battery.

  Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery
native-path:  hid-34:88:5d:5e:0c:2f-battery
model:Logitech K810
power supply: no
updated:  Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago)
has history:  yes
has statistics:   yes
keyboard
  present: yes
  rechargeable:yes
  state:   unknown
  warning-level:   none
  percentage:  0%
  icon-name:  'battery-missing-symbolic'

  My guess is that the issue is in the bluetooth rather in the upowerd
  since the reporting in the /sys/devices shows battery level of 0
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bnv1714 F pulseaudio
   /dev/snd/pcmC0D0p:   bnv1714 F...m pulseaudio
   /dev/snd/controlC0:  bnv1714 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf
  InstallationDate: Installed on 2017-11-02 (185 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  IwConfig:
   lono wireless extensions.
   
   enp0s25   no wireless extensions.
  MachineType: Dell Inc. Precision Tower 5810
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago)
  UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0K240Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision Tower 5810
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1769075] ProcCpuinfo.txt

2018-05-08 Thread Alan Lobo
apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1769075/+attachment/5136044/+files/ProcCpuinfo.txt

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

Title:
  [regression][bionic] Bluetooth keyboard battery reports 0%

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d"
  reports always 0% as battery percentage of the bluetooth Logitech K810 
keyboard.
  Which is a bit annoying since I get a KDE warning on the battery.

  Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery
native-path:  hid-34:88:5d:5e:0c:2f-battery
model:Logitech K810
power supply: no
updated:  Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago)
has history:  yes
has statistics:   yes
keyboard
  present: yes
  rechargeable:yes
  state:   unknown
  warning-level:   none
  percentage:  0%
  icon-name:  'battery-missing-symbolic'

  My guess is that the issue is in the bluetooth rather in the upowerd
  since the reporting in the /sys/devices shows battery level of 0
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bnv1714 F pulseaudio
   /dev/snd/pcmC0D0p:   bnv1714 F...m pulseaudio
   /dev/snd/controlC0:  bnv1714 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf
  InstallationDate: Installed on 2017-11-02 (185 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  IwConfig:
   lono wireless extensions.
   
   enp0s25   no wireless extensions.
  MachineType: Dell Inc. Precision Tower 5810
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago)
  UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0K240Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision Tower 5810
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1769891] [NEW] UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 37: ordinal not in range(128)

2018-05-08 Thread Battant
Public bug reported:

Hello

duplicity crash after backup because there is a python error

Step to reproduce.

1. Active developper option in software center
2. install the backup python pyckage
3. Lanch a backup with duplicity command

Result :


 Type of backup set:Time:   Number of volumes:
Full Tue Feb 20 22:00:34 2018  2284
 Incremental Thu Feb 22 03:26:48 2018 1
 Incremental Fri Feb 23 23:23:09 201842
 Incremental Wed Apr  4 15:54:05 2018   151
 Incremental Thu Apr  5 04:27:55 2018 1
 Incremental Sat Apr 14 21:51:41 2018 1
-
Also found 0 backup sets not part of any chain,
and 1 incomplete backup set.
These may be deleted by running duplicity with the "cleanup" command.
Registering (mktemp) temporary file 
/tmp/duplicity-hFkoYG-tempdir/mktemp-1HIleQ-2
Deleting /tmp/duplicity-hFkoYG-tempdir/mktemp-1HIleQ-2
Forgetting temporary file /tmp/duplicity-hFkoYG-tempdir/mktemp-1HIleQ-2
Processing remote manifest 
duplicity-inc.20180405T022755Z.to.20180414T195141Z.manifest (154)
Found manifest volume 1
Found 1 volumes in manifest
Registering (mktemp) temporary file 
/tmp/duplicity-hFkoYG-tempdir/mktemp-AW3xfd-3
Backtrace of previous error: Traceback (innermost last):
  File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 369, in 
inner_retry
return fn(self, *args)
  File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 556, in get
"from backend") % util.ufn(local_path.name))
 BackendException: File /tmp/duplicity-hFkoYG-tempdir/mktemp-AW3xfd-3 not found 
locally after get from backend

Attempt 1 failed. BackendException: File 
/tmp/duplicity-hFkoYG-tempdir/mktemp-AW3xfd-3 not found locally after get from 
backend
Backtrace of previous error: Traceback (innermost last):
  File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 369, in 
inner_retry
return fn(self, *args)
  File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 552, in get
self.backend._get(remote_filename, local_path)
  File "/usr/lib/python2.7/dist-packages/duplicity/backends/giobackend.py", 
line 151, in _get
self.__copy_file(source_file, target_file)
  File "/usr/lib/python2.7/dist-packages/duplicity/backends/giobackend.py", 
line 124, in __copy_file
None, self.__copy_progress, None)
 Error: g-io-error-quark: Error opening file 
“/tmp/duplicity-hFkoYG-tempdir/mktemp-AW3xfd-3”: No such file or directory 
(1)

Releasing lockfile 
/home/username/.cache/deja-dup/078943ce1c0e98d4e44486ca87a6cdd8/lockfile
Removing still remembered temporary file 
/tmp/duplicity-hFkoYG-tempdir/mkstemp-useaK1-1
Removing still remembered temporary file 
/tmp/duplicity-hFkoYG-tempdir/mktemp-AW3xfd-3
Cleanup of temporary directory /tmp/duplicity-hFkoYG-tempdir failed - this is 
probably a bug.
Releasing lockfile 
/home/username/.cache/deja-dup/078943ce1c0e98d4e44486ca87a6cdd8/lockfile
Traceback (innermost last):
  File "/usr/bin/duplicity", line 1555, in 
with_tempdir(main)
  File "/usr/bin/duplicity", line 1541, in with_tempdir
fn()
  File "/usr/bin/duplicity", line 1393, in main
do_backup(action)
  File "/usr/bin/duplicity", line 1523, in do_backup
incremental_backup(sig_chain)
  File "/usr/bin/duplicity", line 658, in incremental_backup
sig_chain.get_fileobjs())
  File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 539, 
in get_fileobjs
return [filename_to_fileobj(f) for f in self.get_filenames(time)]
  File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 676, in 
get_fileobj_read
self.get(filename, tdp)
  File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 392, in 
inner_retry
util.uexc(e)), code=code, extra=extra)
  File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 79, in uexc
return ufn(unicode(e).encode('utf-8'))
 UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 37: 
ordinal not in range(128)

Releasing lockfile /home/username/.cache/deja-
dup/078943ce1c0e98d4e44486ca87a6cdd8/lockfile

Note : this bug affect eclim and other python pyckages

http://eclim.org


Could you help me please to fix this issus

Best regards

Battant

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: python2.7 2.7.15~rc1-1
ProcVersionSignature: Ubuntu 4.15.0-21.22-generic 4.15.17
Uname: Linux 4.15.0-21-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue May  8 14:11:35 2018
InstallationDate: Installed on 2018-04-29 (8 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: python2.7
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: deja-dup
 Importance: Undecided
 Status: New

** Affects: python2.7 (Ubuntu)
 Importa

[Touch-packages] [Bug 1769893] [NEW] Unauthorized when using Chrome browser

2018-05-08 Thread Terrance
Public bug reported:

Using Chrome Version 66.0.3359.139 (Official Build) (64-bit)

I am able to access and add a printer through Chrome by going to the
page http://localhost:631/admin/login and I can add a printer fine.  But
I cannot add the printer if I go directly to http://localhost:631/admin
and bypass the login.  If I need to change any defaults of the printer
through the same pages it gives me the "Unauthorized" and will not
change anything.  I can change it in Firefox and the printers control
panel.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: cups 2.2.7-1ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CupsErrorLog:
 E [08/May/2018:00:07:44 -0600] Filter \"pstops\" not found.
 E [08/May/2018:00:07:44 -0600] Filter \"pstops\" not found.
 E [08/May/2018:07:01:45 -0600] [Client 20] pam_authenticate() returned 7 
(Authentication failure)
 E [08/May/2018:07:02:01 -0600] [cups-deviced] PID 15052 (gutenprint52+usb) 
stopped with status 1!
CurrentDesktop: XFCE
Date: Tue May  8 07:18:47 2018
InstallationDate: Installed on 2018-05-05 (2 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Lpstat:
 device for Deskjet_3520_series_75C0A7_: 
ipp://HP6C3BE575C0A7.local:631/ipp/print
 device for HP_Color_LaserJet_CP1518ni: socket://10.0.0.253
MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7508
Papersize: letter
PpdFiles:
 Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Deskjet_3520_series_75C0A7_.ppd', 
'/etc/cups/ppd/HP_Color_LaserJet_CP1518ni.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Deskjet_3520_series_75C0A7_.ppd: Permission denied
 grep: /etc/cups/ppd/HP_Color_LaserJet_CP1518ni.ppd: Permission denied
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=5dae0d38-9bbe-48de-b110-62763c862892 ro nosplash net.ifnames=0 
biosdevname=0
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/30/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V3.8
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: K9N2GM-FIH(MS-7508)
dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV3.8:bd09/30/2010:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7508:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnK9N2GM-FIH(MS-7508):rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: MS-7508
dmi.product.version: 1.0
dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD

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


** Tags: amd64 apparmor apport-bug bionic

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

Title:
  Unauthorized when using Chrome browser

Status in cups package in Ubuntu:
  New

Bug description:
  Using Chrome Version 66.0.3359.139 (Official Build) (64-bit)

  I am able to access and add a printer through Chrome by going to the
  page http://localhost:631/admin/login and I can add a printer fine.
  But I cannot add the printer if I go directly to
  http://localhost:631/admin and bypass the login.  If I need to change
  any defaults of the printer through the same pages it gives me the
  "Unauthorized" and will not change anything.  I can change it in
  Firefox and the printers control panel.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CupsErrorLog:
   E [08/May/2018:00:07:44 -0600] Filter \"pstops\" not found.
   E [08/May/2018:00:07:44 -0600] Filter \"pstops\" not found.
   E [08/May/2018:07:01:45 -0600] [Client 20] pam_authenticate() returned 7 
(Authentication failure)
   E [08/May/2018:07:02:01 -0600] [cups-deviced] PID 15052 (gutenprint52+usb) 
stopped with status 1!
  CurrentDesktop: XFCE
  Date: Tue May  8 07:18:47 2018
  InstallationDate: Installed on 2018-05-05 (2 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Lpstat:
   device for Deskjet_3520_series_75C0A7_: 
ipp://HP6C3BE575C0A7.local:631/ipp/print
   device for HP_Color_LaserJet_CP1518ni: socket://10.0.0.253
  MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7508
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Deskjet_3520_series_75C0A7_.ppd', 
'/etc/cups/ppd/HP_Color_LaserJet_CP1518ni.ppd'] failed with exit code 2: grep: 
/et

[Touch-packages] [Bug 1767831] Re: package avahi-dnsconfd 0.6.32-1ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2018-05-08 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  package avahi-dnsconfd 0.6.32-1ubuntu1 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 1

Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  Got bug when did upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: avahi-dnsconfd 0.6.32-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  Date: Sun Apr 29 20:07:16 2018
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-05-05 (723 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: avahi
  Title: package avahi-dnsconfd 0.6.32-1ubuntu1 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: Upgraded to artful on 2017-10-20 (191 days ago)

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

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


[Touch-packages] [Bug 1767831] Re: package avahi-dnsconfd 0.6.32-1ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2018-05-08 Thread Joe Jepsen
I am unable to update my system.

joe@joe-linux:~$ sudo apt-get install avahi-daemon avahi-dnsconfd avahi-utils
[sudo] password for joe: 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
avahi-daemon is already the newest version (0.6.32-1ubuntu1.1).
avahi-utils is already the newest version (0.6.32-1ubuntu1.1).
The following packages will be upgraded:
  avahi-dnsconfd
1 upgraded, 0 newly installed, 0 to remove and 7 not upgraded.
Need to get 0 B/14.0 kB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
(Reading database ... 392091 files and directories currently installed.)
Preparing to unpack .../avahi-dnsconfd_0.6.32-1ubuntu1.1_amd64.deb ...
Job for avahi-daemon.socket canceled.
dpkg: warning: subprocess old pre-removal script returned error exit status 1
dpkg: trying script from the new package instead ...
Job for avahi-daemon.socket canceled.
dpkg: error processing archive 
/var/cache/apt/archives/avahi-dnsconfd_0.6.32-1ubuntu1.1_amd64.deb (--unpack):
 subprocess new pre-removal script returned error exit status 1
Errors were encountered while processing:
 /var/cache/apt/archives/avahi-dnsconfd_0.6.32-1ubuntu1.1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
joe@joe-linux:~$ sudo apt-get install avahi-daemon avahi-dnsconfd avahi-utils
Reading package lists... Done
Building dependency tree   
Reading state information... Done
avahi-daemon is already the newest version (0.6.32-1ubuntu1.1).
avahi-utils is already the newest version (0.6.32-1ubuntu1.1).
The following packages will be upgraded:
  avahi-dnsconfd
1 upgraded, 0 newly installed, 0 to remove and 7 not upgraded.
Need to get 0 B/14.0 kB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] Y
(Reading database ... 392091 files and directories currently installed.)
Preparing to unpack .../avahi-dnsconfd_0.6.32-1ubuntu1.1_amd64.deb ...
Job for avahi-daemon.socket canceled.
dpkg: warning: subprocess old pre-removal script returned error exit status 1
dpkg: trying script from the new package instead ...
Job for avahi-daemon.socket canceled.
dpkg: error processing archive 
/var/cache/apt/archives/avahi-dnsconfd_0.6.32-1ubuntu1.1_amd64.deb (--unpack):
 subprocess new pre-removal script returned error exit status 1
Errors were encountered while processing:
 /var/cache/apt/archives/avahi-dnsconfd_0.6.32-1ubuntu1.1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


joe@joe-linux:~$ sudo apt-get dist-upgrade
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  avahi-dnsconfd libpam-systemd libsystemd0 libsystemd0:i386 libudev1 systemd
  systemd-sysv udev
8 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 4,484 kB/4,498 kB of archives.
After this operation, 10.2 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 libpam-systemd 
amd64 234-2ubuntu12.3 [111 kB]
Get:2 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 libudev1 amd64 
234-2ubuntu12.3 [52.4 kB]
Get:3 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 udev amd64 
234-2ubuntu12.3 [1,091 kB]
Get:4 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 systemd amd64 
234-2ubuntu12.3 [2,781 kB]
Get:5 http://archive.ubuntu.com/ubuntu artful-updates/main i386 libsystemd0 
i386 234-2ubuntu12.3 [227 kB]
Get:6 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 libsystemd0 
amd64 234-2ubuntu12.3 [209 kB]
Get:7 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 systemd-sysv 
amd64 234-2ubuntu12.3 [11.6 kB]
Fetched 4,484 kB in 2s (2,078 kB/s)  
(Reading database ... 392091 files and directories currently installed.)
Preparing to unpack .../libpam-systemd_234-2ubuntu12.3_amd64.deb ...
Unpacking libpam-systemd:amd64 (234-2ubuntu12.3) over (234-2ubuntu12.1) ...
Preparing to unpack .../libudev1_234-2ubuntu12.3_amd64.deb ...
Unpacking libudev1:amd64 (234-2ubuntu12.3) over (234-2ubuntu12.1) ...
Setting up libudev1:amd64 (234-2ubuntu12.3) ...
(Reading database ... 392091 files and directories currently installed.)
Preparing to unpack .../udev_234-2ubuntu12.3_amd64.deb ...
Unpacking udev (234-2ubuntu12.3) over (234-2ubuntu12.1) ...
Preparing to unpack .../systemd_234-2ubuntu12.3_amd64.deb ...
Unpacking systemd (234-2ubuntu12.3) over (234-2ubuntu12.1) ...
Preparing to unpack .../libsystemd0_234-2ubuntu12.3_amd64.deb ...
De-configuring libsystemd0:i386 (234-2ubuntu12.1) ...
Unpacking libsystemd0:amd64 (234-2ubuntu12.3) over (234-2ubuntu12.1) ...
Preparing to unpack .../libsystemd0_234-2ubuntu12.3_i386.deb ...
Unpacking libsystemd0:i386 (234-2ubuntu12.3) over (234-2ubuntu12.1) ...
Setting up libsystemd0:amd64 (234-2ubuntu12.3) ...
Setting up libsystemd0:i386 (234-

[Touch-packages] [Bug 1769324] Re: canonical-livepatch: unable to enable it through software-properties-gtk

2018-05-08 Thread Andrea Azzarone
Is there an "Ubuntu Single Sign-On" row in gnome-control-center in the
"Online Accounts" panel?

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

Title:
  canonical-livepatch: unable to enable it through software-properties-
  gtk

Status in software-properties package in Ubuntu:
  Incomplete

Bug description:
  Trying to enable canonical-livepatch through software-properties-gtk, the 
application itself gets stuck on access window.
  Nothing happens.

  Even when trying to enable canonical-livepatch through a terminal,
  running: sudo canonical-livepatch enable  I receive the message:
  "canonical-livepatch command not found"

  I succeded running the command through gksu

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: software-properties-gtk 0.96.24.32.1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat May  5 11:06:30 2018
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1766872] Re: 'Enable Network' in recovery mode not working in Bionic

2018-05-08 Thread Eric Desrochers
The only problem missing is the dbus aspect.

dbus.service is necessary for NetworkManager but cannot be started
manually[1], preventing NetworkManager to start succefully.

[1] dbus.service
# we don't properly stop D-Bus (see ExecStop=), thus disallow restart
RefuseManualStart=yes

As a debug exercise, I have commented (#RefuseManualStart=yes) start
dbus.service by hand and then pick the 'Enable Networking' option and it
works.

Need to find a way to make dbus.service to start with friendly-recovery
or when 'Enable Network' is chosen.

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

Title:
  'Enable Network' in recovery mode not working in Bionic

Status in friendly-recovery package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  This bug has been noticed after the introduction of the fix of (LP:
  #1682637) in Bionic.

  I have notice a block in Bionic when choosing 'Enable Network' option
  in recovery mode on different bionic vanilla system and I can
  reproduce all the time.

  I also asked colleagues to give it a try (for a second pair of eye on
  this) and they have the same result as me.

  Basically, when choosing 'Enable Network' it get block or lock.
  If we hit 'ctrl-c', then a shell arrive and the system has network 
connectivity.

  Here's what I find while enabling "systemd.debug-shell=1" from vtty9 :

  # pstree
  systemd-+-bash---pstree
  |-recovery-menu---network---systemctl---systemd-tty-ask
  |-systemd-journal
  

  # ps
  root 486 473 0 08:29 tty1 00:00:00 /bin/systemd-tty-ask-password-agent

  root 473 486 0 08:29 tty1 00:00:00 systemctl start dbus.socket

  root 486 283 0 08:29 tty1 00:00:00 /bin/sh /lib/recovery-
  mode/options/network

  Additionally,

  systemd-analyze blame:
  "Bootup is not yet finished. Please try again later"

  "systemctl list-jobs" is showing a 100 jobs in 'waiting' state

  The only 'running' unit is friendly-recovery.service :
  52 friendly-recovery.service start running

  The rest are all "waiting". My understanding is that "waiting" units
  will be executed only after those which are "running" are completed.
  Which explain why the "ctlr-c" allow the boot to continue.

  All the systemd special unit important at boot-up are waiting.
  7 sysinit.target start waiting
  3 basic.target   start waiting
  .

  Seems like systemd is not fully initialise in 'Recovery Mode' and
  doesn't allow any 'systemctl start' operation without
  password/passphrase request, which I suspect is hidden by the
  recovery-mode menu.

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

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


[Touch-packages] [Bug 1766872] Re: 'Enable Network' in recovery mode not working in Bionic

2018-05-08 Thread Eric Desrochers
So the --job-mode=ignore-dependencies approach cover the scenario when
using systemd-networkd, but NetworkManager still fails for the reason
above ^ (dbus.service) not starting.

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

Title:
  'Enable Network' in recovery mode not working in Bionic

Status in friendly-recovery package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  This bug has been noticed after the introduction of the fix of (LP:
  #1682637) in Bionic.

  I have notice a block in Bionic when choosing 'Enable Network' option
  in recovery mode on different bionic vanilla system and I can
  reproduce all the time.

  I also asked colleagues to give it a try (for a second pair of eye on
  this) and they have the same result as me.

  Basically, when choosing 'Enable Network' it get block or lock.
  If we hit 'ctrl-c', then a shell arrive and the system has network 
connectivity.

  Here's what I find while enabling "systemd.debug-shell=1" from vtty9 :

  # pstree
  systemd-+-bash---pstree
  |-recovery-menu---network---systemctl---systemd-tty-ask
  |-systemd-journal
  

  # ps
  root 486 473 0 08:29 tty1 00:00:00 /bin/systemd-tty-ask-password-agent

  root 473 486 0 08:29 tty1 00:00:00 systemctl start dbus.socket

  root 486 283 0 08:29 tty1 00:00:00 /bin/sh /lib/recovery-
  mode/options/network

  Additionally,

  systemd-analyze blame:
  "Bootup is not yet finished. Please try again later"

  "systemctl list-jobs" is showing a 100 jobs in 'waiting' state

  The only 'running' unit is friendly-recovery.service :
  52 friendly-recovery.service start running

  The rest are all "waiting". My understanding is that "waiting" units
  will be executed only after those which are "running" are completed.
  Which explain why the "ctlr-c" allow the boot to continue.

  All the systemd special unit important at boot-up are waiting.
  7 sysinit.target start waiting
  3 basic.target   start waiting
  .

  Seems like systemd is not fully initialise in 'Recovery Mode' and
  doesn't allow any 'systemctl start' operation without
  password/passphrase request, which I suspect is hidden by the
  recovery-mode menu.

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

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


[Touch-packages] [Bug 1769893] Re: CUPS Unauthorized when using Chrome browser

2018-05-08 Thread Terrance
** Summary changed:

- Unauthorized when using Chrome browser
+ CUPS Unauthorized when using Chrome browser

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

Title:
  CUPS Unauthorized when using Chrome browser

Status in cups package in Ubuntu:
  New

Bug description:
  Using Chrome Version 66.0.3359.139 (Official Build) (64-bit)

  I am able to access and add a printer through Chrome by going to the
  page http://localhost:631/admin/login and I can add a printer fine.
  But I cannot add the printer if I go directly to
  http://localhost:631/admin and bypass the login.  If I need to change
  any defaults of the printer through the same pages it gives me the
  "Unauthorized" and will not change anything.  I can change it in
  Firefox and the printers control panel.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CupsErrorLog:
   E [08/May/2018:00:07:44 -0600] Filter \"pstops\" not found.
   E [08/May/2018:00:07:44 -0600] Filter \"pstops\" not found.
   E [08/May/2018:07:01:45 -0600] [Client 20] pam_authenticate() returned 7 
(Authentication failure)
   E [08/May/2018:07:02:01 -0600] [cups-deviced] PID 15052 (gutenprint52+usb) 
stopped with status 1!
  CurrentDesktop: XFCE
  Date: Tue May  8 07:18:47 2018
  InstallationDate: Installed on 2018-05-05 (2 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Lpstat:
   device for Deskjet_3520_series_75C0A7_: 
ipp://HP6C3BE575C0A7.local:631/ipp/print
   device for HP_Color_LaserJet_CP1518ni: socket://10.0.0.253
  MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7508
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Deskjet_3520_series_75C0A7_.ppd', 
'/etc/cups/ppd/HP_Color_LaserJet_CP1518ni.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Deskjet_3520_series_75C0A7_.ppd: Permission denied
   grep: /etc/cups/ppd/HP_Color_LaserJet_CP1518ni.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=5dae0d38-9bbe-48de-b110-62763c862892 ro nosplash net.ifnames=0 
biosdevname=0
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V3.8
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: K9N2GM-FIH(MS-7508)
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV3.8:bd09/30/2010:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7508:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnK9N2GM-FIH(MS-7508):rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: MS-7508
  dmi.product.version: 1.0
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD

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

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


[Touch-packages] [Bug 1769907] [NEW] HDMI extended monitor has very low resolution in mirrored display mode

2018-05-08 Thread Wang Xuancong
Public bug reported:

It seems that recent versions of Ubuntu (16.04) has a bug in handling extended 
HDMI monitors. The HDMI monitor has up to 1980x1080 resolution, my laptop has 
up to 1366x768 resolution. Both screens have native 16:9 ratio.
However, in "mirrored display" mode, I can only select 1024x768 and 800x600 
resolution as shown in the image attached.

In such mode, my laptop screen has two blank strip on the left and right
side. On the HDMI monitor, it shows a squashed screen (1024x768
resolution stretched to 16:9 full screen).

I have temporarily developed a workaround, see
https://xuancong84.blogspot.sg/2018/05/ubuntu-hdmi-extended-monitor-
low.html ,  but I still hope the bug can be solved.

Thank you very much!

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-15.16~16.04.1-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Tue May  8 22:21:37 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.10.0-28-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:07a0]
InstallationDate: Installed on 2018-03-09 (59 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 1bcf:2b96 Sunplus Innovation Technology Inc. 
 Bus 001 Device 002: ID 17ef:6025 Lenovo ThinkPad Travel Mouse
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Latitude 7480
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic 
root=UUID=3f217eea-d2a7-4c61-9f9a-0a111e2e3cdf ro quiet splash 
intel_pstate=disable vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/09/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.9.3
dmi.board.name: 00F6D3
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.3:bd03/09/2018:svnDellInc.:pnLatitude7480:pvr:rvnDellInc.:rn00F6D3:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude 7480
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug compiz-0.9 resolution ubuntu xenial

** Attachment added: "bug screenshot"
   https://bugs.launchpad.net/bugs/1769907/+attachment/5136129/+files/bug.jpg

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

Title:
  HDMI extended monitor has very low resolution in mirrored display mode

Status in xorg package in Ubuntu:
  New

Bug description:
  It seems that recent versions of Ubuntu (16.04) has a bug in handling 
extended HDMI monitors. The HDMI monitor has up to 1980x1080 resolution, my 
laptop has up to 1366x768 resolution. Both screens have native 16:9 ratio.
  However, in "mirrored display" mode, I can only select 1024x768 and 800x600 
resolution as shown in the image attached.

  In such mode, my laptop screen has two blank strip on the left and
  right side. On the HDMI monitor, it shows a squashed screen (1024x768
  resolution stretched to 16:9 full screen).

  I have temporarily developed a workaround, see
  https://xuancong84.blogspot.sg/2018/05/ubuntu-hdmi-extended-monitor-
  low.html ,  but I still hope the bug can be solved.

  Thank you very much!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-15.16~16.04.1-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_p

[Touch-packages] [Bug 1769324] Re: canonical-livepatch: unable to enable it through software-properties-gtk

2018-05-08 Thread Andrea Azzarone
You're on xubuntu. For the moment it's not supported. I guess we should
hide that checkbox. For the moment you can enable it from here:
https://www.ubuntu.com/server/livepatch

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

Title:
  canonical-livepatch: unable to enable it through software-properties-
  gtk

Status in software-properties package in Ubuntu:
  Incomplete

Bug description:
  Trying to enable canonical-livepatch through software-properties-gtk, the 
application itself gets stuck on access window.
  Nothing happens.

  Even when trying to enable canonical-livepatch through a terminal,
  running: sudo canonical-livepatch enable  I receive the message:
  "canonical-livepatch command not found"

  I succeded running the command through gksu

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: software-properties-gtk 0.96.24.32.1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat May  5 11:06:30 2018
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1769324] Re: canonical-livepatch: unable to enable it through software-properties-gtk

2018-05-08 Thread vimo
Il mar 8 mag 2018, 16:15 Andrea Azzarone  ha
scritto:

> Is there an "Ubuntu Single Sign-On" row in gnome-control-center in the
> "Online Accounts" panel?
>
> bug/1769324/+subscriptions
> 


No. I attached a screenshot of the window

>
>

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

Title:
  canonical-livepatch: unable to enable it through software-properties-
  gtk

Status in software-properties package in Ubuntu:
  Incomplete

Bug description:
  Trying to enable canonical-livepatch through software-properties-gtk, the 
application itself gets stuck on access window.
  Nothing happens.

  Even when trying to enable canonical-livepatch through a terminal,
  running: sudo canonical-livepatch enable  I receive the message:
  "canonical-livepatch command not found"

  I succeded running the command through gksu

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: software-properties-gtk 0.96.24.32.1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat May  5 11:06:30 2018
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''

2018-05-08 Thread Iain Lane
Removed the .gladep file; it seems to have crept in by error during the
git migration (also in my cosmic upload) and uploaded bionic. Thanks and
sorry cyphermox if this treads on your toes.

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

Title:
  [regression] ubiquity crashed in debconf.py:104 with ValueError:
  invalid literal for int() with base 10: ''

Status in cairo:
  Confirmed
Status in OEM Priority Project:
  Triaged
Status in cairo package in Ubuntu:
  In Progress
Status in ubiquity package in Ubuntu:
  In Progress
Status in cairo source package in Bionic:
  In Progress
Status in ubiquity source package in Bionic:
  In Progress

Bug description:
  * Impact
  The Ubuntu installer crashes on some machines (seems more often on hiDPI 
machines (QHD/UHD etc)).

  * Test case
  Try installing Ubuntu on an hidpi machine, it should complete installation 
instead of crashing.

  * Regression potential
  The fix in ubiquity touches the code handle uid drop/privilege, that can have 
unexpected side effects so we need proper/complete testing of the installer

  --

  Update: Actually the crash occurs on slow-ish systems due to a race
  condition. It's not strictly only hi-DPI machines - that's just the
  most common place it is experienced.

  ---

  https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
  https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15
  https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7
  https://errors.ubuntu.com/problem/cb82f70f9ede07369e8104da9ddf87e28b42257d
  https://errors.ubuntu.com/problem/84a5563af3d2b85f098da832ece4cb8450bfd524

  ---

  WORKAROUND:

  1. Boot into the live session.
  2. Settings > Devices > Displays > Scale = 100%
  3. Click Apply.
  4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".

  ---

  Crashed in a VM in the middle of installation. The host is Bionic up
  to date.

  From the journal
  Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3 
ip:7f5a76936961 sp:7ffde5090c50 error:0 in 
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
  Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
  Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 757, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 135, in run
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 505, in copy_all
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 + 
copy_progress)
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 83, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw: 
self.command(command, *args, **kw))
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
  Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
  Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for 
int() with base 10: ''

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ubiquity 18.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.388
  Date: Fri Feb 23 12:52:28 2018
  ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr 
keyboard-configuration/variantcode=oss
  InterpreterPath: /usr/bin/python3.6
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  Signal: 5
  SourcePackage: ubiquity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: ubiquity crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

-- 
Mailing list: https://l

Re: [Touch-packages] [Bug 1769324] Re: canonical-livepatch: unable to enable it through software-properties-gtk

2018-05-08 Thread vimo
Il mar 8 mag 2018, 16:36 Andrea Azzarone  ha
scritto:

> You're on xubuntu. For the moment it's not supported. I guess we should
> hide that checkbox. For the moment you can enable it from here:
> https://www.ubuntu.com/server/livepatch
>
>
> In my bug report I said that I had already installed livepatch and
> explained the way I did it.



Thank you for the support.

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

Title:
  canonical-livepatch: unable to enable it through software-properties-
  gtk

Status in software-properties package in Ubuntu:
  Incomplete

Bug description:
  Trying to enable canonical-livepatch through software-properties-gtk, the 
application itself gets stuck on access window.
  Nothing happens.

  Even when trying to enable canonical-livepatch through a terminal,
  running: sudo canonical-livepatch enable  I receive the message:
  "canonical-livepatch command not found"

  I succeded running the command through gksu

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: software-properties-gtk 0.96.24.32.1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat May  5 11:06:30 2018
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1769914] [NEW] PulseAudio configures Fiio E10K DAC/headphone amp as input, but it only is a sink

2018-05-08 Thread Julian Andres Klode
Public bug reported:

PulseAudio thinks that a Fiio E10K can capture audio and tries to
configure that, leading to a ton of:

retire_capture_urb: 2492 callbacks suppressed

messages in dmesg. The device has no capture ability, alsamixer also
only shows one master playback control; no capture one.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: pulseaudio 1:11.1-1ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC2D0p:   jak2367 F...m pulseaudio
 /dev/snd/controlC2:  jak2367 F pulseaudio
 /dev/snd/controlC1:  jak2367 F pulseaudio
 /dev/snd/controlC0:  jak2367 F pulseaudio
CurrentDesktop: GNOME
Date: Tue May  8 16:43:47 2018
InstallationDate: Installed on 2018-03-14 (54 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/22/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: N22ET31W (1.08 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20L8S02D00
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET31W(1.08):bd01/22/2018:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T480s
dmi.product.name: 20L8S02D00
dmi.product.version: ThinkPad T480s
dmi.sys.vendor: LENOVO

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


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

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

Title:
  PulseAudio configures Fiio E10K DAC/headphone amp as input, but it
  only is a sink

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  PulseAudio thinks that a Fiio E10K can capture audio and tries to
  configure that, leading to a ton of:

  retire_capture_urb: 2492 callbacks suppressed

  messages in dmesg. The device has no capture ability, alsamixer also
  only shows one master playback control; no capture one.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: pulseaudio 1:11.1-1ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC2D0p:   jak2367 F...m pulseaudio
   /dev/snd/controlC2:  jak2367 F pulseaudio
   /dev/snd/controlC1:  jak2367 F pulseaudio
   /dev/snd/controlC0:  jak2367 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue May  8 16:43:47 2018
  InstallationDate: Installed on 2018-03-14 (54 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET31W (1.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L8S02D00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET31W(1.08):bd01/22/2018:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L8S02D00
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1769914] Re: PulseAudio configures Fiio E10K DAC/headphone amp as input, but it only is a sink

2018-05-08 Thread Julian Andres Klode
Attaching lsusb -vv of the device.

** Attachment added: "lsusb.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1769914/+attachment/5136192/+files/lsusb.txt

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

Title:
  PulseAudio configures Fiio E10K DAC/headphone amp as input, but it
  only is a sink

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  PulseAudio thinks that a Fiio E10K can capture audio and tries to
  configure that, leading to a ton of:

  retire_capture_urb: 2492 callbacks suppressed

  messages in dmesg. The device has no capture ability, alsamixer also
  only shows one master playback control; no capture one.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: pulseaudio 1:11.1-1ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC2D0p:   jak2367 F...m pulseaudio
   /dev/snd/controlC2:  jak2367 F pulseaudio
   /dev/snd/controlC1:  jak2367 F pulseaudio
   /dev/snd/controlC0:  jak2367 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue May  8 16:43:47 2018
  InstallationDate: Installed on 2018-03-14 (54 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET31W (1.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L8S02D00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET31W(1.08):bd01/22/2018:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L8S02D00
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1769682] Re: NFS-based remote root hangs when running 'netplan apply'

2018-05-08 Thread Mathieu Trudel-Lapierre
** Description changed:

+ [Impact]
+ Netboot users with a remote filesystem over NFS (possibly over other 
networked filesystems).
+ 
+ [Test cases]
+ 1) Boot a system with its root filesystem over NFS.
+ 2) Run 'sudo netplan apply'
+ 3) Validate that the system remains responsive and keeps connectivity over 
the same IP address  as it had.
+ 
+ [Regression potential]
+ This SRU changes network properties, and enforces that networkd does not 
release and re-request an IP address from DHCP when it is restarted. 
Environments relying on the IP release/renew behavior may find themselves 
staying on the previous IP address, which might negatively impact connectivity. 
Changes in connectivity on a system running netplan should be investigated as a 
potential regression from this SRU. Other regression possibilities would 
include failure to get a new IP address over time (usually seen as losing 
connectivity) or possible IP conflicts on a network.
+ 
+ ---
+ 
  With a system booted on the network, with its remote root fs on NFS:
  
  Running 'netplan apply' restarts systemd-networkd, which releases the IP
  received from DHCP. With no IP (and and IP potentially changing), the
  NFS server can't be reached so the system hangs.
  
  'netplan apply' or restarting systemd-networkd should not affect teh
  system, it should continue working normally despite "changing" network
  states, as long as the effective IP remains the same.

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

** Also affects: initramfs-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 initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1769682

Title:
  NFS-based remote root hangs when running 'netplan apply'

Status in initramfs-tools package in Ubuntu:
  New
Status in netplan.io package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  New

Bug description:
  [Impact]
  Netboot users with a remote filesystem over NFS (possibly over other 
networked filesystems).

  [Test cases]
  1) Boot a system with its root filesystem over NFS.
  2) Run 'sudo netplan apply'
  3) Validate that the system remains responsive and keeps connectivity over 
the same IP address  as it had.

  [Regression potential]
  This SRU changes network properties, and enforces that networkd does not 
release and re-request an IP address from DHCP when it is restarted. 
Environments relying on the IP release/renew behavior may find themselves 
staying on the previous IP address, which might negatively impact connectivity. 
Changes in connectivity on a system running netplan should be investigated as a 
potential regression from this SRU. Other regression possibilities would 
include failure to get a new IP address over time (usually seen as losing 
connectivity) or possible IP conflicts on a network.

  ---

  With a system booted on the network, with its remote root fs on NFS:

  Running 'netplan apply' restarts systemd-networkd, which releases the
  IP received from DHCP. With no IP (and and IP potentially changing),
  the NFS server can't be reached so the system hangs.

  'netplan apply' or restarting systemd-networkd should not affect teh
  system, it should continue working normally despite "changing" network
  states, as long as the effective IP remains the same.

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

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


[Touch-packages] [Bug 1732002] Re: cloud images in lxc get ipv6 address

2018-05-08 Thread Mathieu Trudel-Lapierre
This got landed in netplan.io 0.35 in bionic. The changes still should
be part of a SRU.

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

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

Title:
  cloud images in lxc get ipv6 address

Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  New

Bug description:
  [Impact]
  All users of netplan.

  [Test case]

  == LXD containers ==
  1) Start an LXD container (artful or bionic)
  2) Verify that an IPv6 address is present
  3) Verify that the system is brought up in a reasonable time (does not wait 2 
minutes to be reachable).

  == servers / cloud instances ==
  1) Start a bionic system, with no IPv6 connectivity (no router to advertise a 
prefix)
  2) Verify that the system boots quickly (does not wait 2 minutes to be 
reachable).

  [Regression potential]
  Since this changes default IPv6 behavior, care should be taken to validate 
that systems are maintaining IPv6 connectivity when it is available, and 
similarly that systems where no IPv6 connectivity is available on the network 
are behaving correctly: there should not be long boot delays, and no extra IPv6 
addresses aside from link-local addresses generated by the kernel.

  --

  I noticed that lxd (lxc list) reports that an lxc container has an
  ipv6 address in artful or bionic.  It does not list this in xenial or
  zesty.  I suspect this change occurred in the switch over to
  netplan/networkd.

  This may at first seem harmless or even desired, but note that the
  user configuration did not request ipv6 config, so its presence is a
  bug.

  $ for rel in xenial zesty artful bionic; do
     lxc launch ubuntu-daily:$rel $rel-demo; done
  Creating xenial-demo
  Starting xenial-demo
  ..
  Creating bionic-demo
  Starting bionic-demo

  $ sleep 10
  $ lxc list
  $ lxc list
  
+-+-+--+++---+
  |NAME |  STATE  | IPV4 |  IPV6
  |TYPE| SNAPSHOTS |
  
+-+-+--+++---+
  | artful-demo | RUNNING | 10.75.205.208 (eth0) | 
fd42:eee5:7c43:3d62:3a42:611c:3f6f:1184 (eth0) | PERSISTENT | 0 |
  
+-+-+--+++---+
  | bionic-demo | RUNNING | 10.75.205.187 (eth0) | 
fd42:eee5:7c43:3d62:6f4:155b:39cc:fc3d (eth0)  | PERSISTENT | 0 |
  
+-+-+--+++---+
  | xenial-demo | RUNNING | 10.75.205.143 (eth0) |  
  | PERSISTENT | 0 |
  
+-+-+--+++---+
  | zesty-demo  | RUNNING | 10.75.205.123 (eth0) |  
  | PERSISTENT | 0 |
  
+-+-+--+++---+

  ## Here is the config that was provided by lxd
  $ lxc exec bionic-demo cat /var/lib/cloud/seed/nocloud-net/network-config
  version: 1
  config:
  - type: physical
    name: eth0
    subnets:
    - type: dhcp
  control: auto

  ## Here is the config that cloud-init rendered.
  $ lxc exec bionic-demo -- grep -v '^#' /etc/netplan/50-cloud-init.yaml
  network:
  version: 2
  ethernets:
  eth0:
  dhcp4: true

  $ lxc exec bionic-demo cat /run/systemd/network/10-netplan-eth0.network
  [Match]
  Name=eth0

  [Network]
  DHCP=ipv4

  [DHCP]
  UseMTU=true
  RouteMetric=100

  $ lxc exec bionic-demo  -- systemctl status --no-pager --full systemd-networkd
  ● systemd-networkd.service - Network Service
     Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; 
vendor preset: enabled)
     Active: active (running) since Mon 2017-11-13 18:37:34 UTC; 8min ago
   Docs: man:systemd-networkd.service(8)
   Main PID: 118 (systemd-network)
     Status: "Processing requests..."
  Tasks: 1 (limit: 4915)
     Memory: 2.0M
    CPU: 19ms
     CGroup: /system.slice/systemd-networkd.service
     └─118 /lib/systemd/systemd-networkd

  Nov 13 18:37:34 bionic-demo systemd[1]: Starting Network Service...
  Nov 13 18:37:34 bionic-demo systemd-networkd[118]: eth0: Gained IPv6LL
  Nov 13 18:37:34 bionic-demo systemd-networkd[118]: Enumeration completed
  Nov 13 18:37:34 bionic-demo systemd[1]: Started Network Service.
  Nov 13 18:37:37 bionic-demo systemd-networkd[118]: eth0: DHCPv6 address 
fd42:eee5:7c43:3d62:6f4:155b:39cc:

[Touch-packages] [Bug 1732002] Re: cloud images in lxc get ipv6 address

2018-05-08 Thread Mathieu Trudel-Lapierre
** Description changed:

+ [Impact]
+ All users of netplan.
+ 
+ [Test case]
+ 
+ == LXD containers ==
+ 1) Start an LXD container (artful or bionic)
+ 2) Verify that an IPv6 address is present
+ 3) Verify that the system is brought up in a reasonable time (does not wait 2 
minutes to be reachable).
+ 
+ == servers / cloud instances ==
+ 1) Start a bionic system, with no IPv6 connectivity (no router to advertise a 
prefix)
+ 2) Verify that the system boots quickly (does not wait 2 minutes to be 
reachable).
+ 
+ [Regression potential]
+ Since this changes default IPv6 behavior, care should be taken to validate 
that systems are maintaining IPv6 connectivity when it is available, and 
similarly that systems where no IPv6 connectivity is available on the network 
are behaving correctly: there should not be long boot delays, and no extra IPv6 
addresses aside from link-local addresses generated by the kernel.
+ 
+ --
+ 
  I noticed that lxd (lxc list) reports that an lxc container has an ipv6
  address in artful or bionic.  It does not list this in xenial or zesty.
  I suspect this change occurred in the switch over to netplan/networkd.
  
  This may at first seem harmless or even desired, but note that the user
  configuration did not request ipv6 config, so its presence is a bug.
  
  $ for rel in xenial zesty artful bionic; do
-lxc launch ubuntu-daily:$rel $rel-demo; done
+    lxc launch ubuntu-daily:$rel $rel-demo; done
  Creating xenial-demo
  Starting xenial-demo
  ..
  Creating bionic-demo
  Starting bionic-demo
- 
  
  $ sleep 10
  $ lxc list
  $ lxc list
  
+-+-+--+++---+
  |NAME |  STATE  | IPV4 |  IPV6
  |TYPE| SNAPSHOTS |
  
+-+-+--+++---+
  | artful-demo | RUNNING | 10.75.205.208 (eth0) | 
fd42:eee5:7c43:3d62:3a42:611c:3f6f:1184 (eth0) | PERSISTENT | 0 |
  
+-+-+--+++---+
  | bionic-demo | RUNNING | 10.75.205.187 (eth0) | 
fd42:eee5:7c43:3d62:6f4:155b:39cc:fc3d (eth0)  | PERSISTENT | 0 |
  
+-+-+--+++---+
  | xenial-demo | RUNNING | 10.75.205.143 (eth0) |  
  | PERSISTENT | 0 |
  
+-+-+--+++---+
  | zesty-demo  | RUNNING | 10.75.205.123 (eth0) |  
  | PERSISTENT | 0 |
  
+-+-+--+++---+
  
  ## Here is the config that was provided by lxd
  $ lxc exec bionic-demo cat /var/lib/cloud/seed/nocloud-net/network-config
  version: 1
  config:
- - type: physical
-   name: eth0
-   subnets:
-   - type: dhcp
- control: auto
+ - type: physical
+   name: eth0
+   subnets:
+   - type: dhcp
+ control: auto
  
  ## Here is the config that cloud-init rendered.
  $ lxc exec bionic-demo -- grep -v '^#' /etc/netplan/50-cloud-init.yaml
  network:
- version: 2
- ethernets:
- eth0:
- dhcp4: true
+ version: 2
+ ethernets:
+ eth0:
+ dhcp4: true
  
  $ lxc exec bionic-demo cat /run/systemd/network/10-netplan-eth0.network
  [Match]
  Name=eth0
  
  [Network]
  DHCP=ipv4
  
  [DHCP]
  UseMTU=true
  RouteMetric=100
  
  $ lxc exec bionic-demo  -- systemctl status --no-pager --full systemd-networkd
  ● systemd-networkd.service - Network Service
-Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; 
vendor preset: enabled)
-Active: active (running) since Mon 2017-11-13 18:37:34 UTC; 8min ago
-  Docs: man:systemd-networkd.service(8)
-  Main PID: 118 (systemd-network)
-Status: "Processing requests..."
- Tasks: 1 (limit: 4915)
-Memory: 2.0M
-   CPU: 19ms
-CGroup: /system.slice/systemd-networkd.service
-└─118 /lib/systemd/systemd-networkd
+    Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; 
vendor preset: enabled)
+    Active: active (running) since Mon 2017-11-13 18:37:34 UTC; 8min ago
+  Docs: man:systemd-networkd.service(8)
+  Main PID: 118 (systemd-network)
+    Status: "Processing requests..."
+ Tasks: 1 (limit: 4915)
+    Memory: 2.0M
+   CPU: 19ms
+    CGroup: /system.slice/systemd-networkd.service
+    └─118 /lib/systemd/systemd-networkd
  
  Nov 13 18:37:34 bionic-demo systemd[1]: Starting Network Service...
  Nov 13 18:37:34 bionic-demo systemd-networkd[118]: eth0: Gained 

[Touch-packages] [Bug 1769075] Re: [regression][bionic] Bluetooth keyboard battery reports 0%

2018-05-08 Thread Alan Lobo
I have this issue for both my Logitech K810 Keyboard as well as my
Logitech T630 Mouse.

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

Title:
  [regression][bionic] Bluetooth keyboard battery reports 0%

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d"
  reports always 0% as battery percentage of the bluetooth Logitech K810 
keyboard.
  Which is a bit annoying since I get a KDE warning on the battery.

  Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery
native-path:  hid-34:88:5d:5e:0c:2f-battery
model:Logitech K810
power supply: no
updated:  Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago)
has history:  yes
has statistics:   yes
keyboard
  present: yes
  rechargeable:yes
  state:   unknown
  warning-level:   none
  percentage:  0%
  icon-name:  'battery-missing-symbolic'

  My guess is that the issue is in the bluetooth rather in the upowerd
  since the reporting in the /sys/devices shows battery level of 0
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bnv1714 F pulseaudio
   /dev/snd/pcmC0D0p:   bnv1714 F...m pulseaudio
   /dev/snd/controlC0:  bnv1714 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf
  InstallationDate: Installed on 2017-11-02 (185 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  IwConfig:
   lono wireless extensions.
   
   enp0s25   no wireless extensions.
  MachineType: Dell Inc. Precision Tower 5810
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago)
  UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0K240Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision Tower 5810
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1769922] [NEW] my left speaker has crackling sound. when i was hearing music in my laptop speaker the window locked. At that time the crackling sound started

2018-05-08 Thread Gokul
Public bug reported:

please fix this soon.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: pulseaudio 1:10.0-1ubuntu2
ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17
Uname: Linux 4.10.0-42-generic x86_64
NonfreeKernelModules: wl
AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.10.0-42-generic.
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.4-0ubuntu4.10
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0c:   gokul  1656 F...m pulseaudio
 /dev/snd/controlC0:  gokul  1656 F pulseaudio
Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
Date: Tue May  8 20:35:43 2018
InstallationDate: Installed on 2018-04-11 (27 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcEnviron:
 LANGUAGE=en_IN:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_IN
 SHELL=/bin/bash
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/15/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: R0210DA
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0210DA:bd07/15/2013:svnSonyCorporation:pnSVF15212SNW:pvrC10HUWG0:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.name: SVF15212SNW
dmi.product.version: C10HUWG0
dmi.sys.vendor: Sony Corporation

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


** Tags: amd64 apport-bug zesty

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

Title:
  my left speaker has crackling sound. when i was hearing music in my
  laptop speaker the window locked. At that  time the crackling sound
  started

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  please fix this soon.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  NonfreeKernelModules: wl
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.10.0-42-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.4-0ubuntu4.10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   gokul  1656 F...m pulseaudio
   /dev/snd/controlC0:  gokul  1656 F pulseaudio
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Date: Tue May  8 20:35:43 2018
  InstallationDate: Installed on 2018-04-11 (27 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0210DA
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0210DA:bd07/15/2013:svnSonyCorporation:pnSVF15212SNW:pvrC10HUWG0:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: SVF15212SNW
  dmi.product.version: C10HUWG0
  dmi.sys.vendor: Sony Corporation

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

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


[Touch-packages] [Bug 1769920] [NEW] Enable support for Rocky Cloud Archive

2018-05-08 Thread Corey Bryant
Public bug reported:

Please add support for:

   cloud-archive:rocky
   cloud-archive:rocky-proposed

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

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

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

[Regression potential]
Limited - just a data item addition

** Affects: software-properties (Ubuntu)
 Importance: High
 Status: Triaged

** Affects: software-properties (Ubuntu Bionic)
 Importance: High
 Status: Triaged

** Affects: software-properties (Ubuntu Cosmic)
 Importance: High
 Status: Triaged

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

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

** Changed in: software-properties (Ubuntu Bionic)
   Importance: Undecided => High

** Changed in: software-properties (Ubuntu Bionic)
   Status: New => Triaged

** Changed in: software-properties (Ubuntu Cosmic)
   Status: New => Triaged

** Changed in: software-properties (Ubuntu Cosmic)
   Importance: Undecided => High

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

Title:
  Enable support for Rocky Cloud Archive

Status in software-properties package in Ubuntu:
  Triaged
Status in software-properties source package in Bionic:
  Triaged
Status in software-properties source package in Cosmic:
  Triaged

Bug description:
  Please add support for:

 cloud-archive:rocky
 cloud-archive:rocky-proposed

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

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

  [Test case]
  sudo add-apt-repository cloud-archive:rocky
  sudo add-apt-repository cloud-archive:rocky-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/1769920/+subscriptions

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


[Touch-packages] [Bug 1768970] Re: Bionic: ubuntu-bug / apport not present

2018-05-08 Thread Brian Murray
How did you end up running Ubuntu 18.04? Did you upgrade from a previous
version of Ubuntu or did you install fresh? If you did a fresh install
from what media did you install?

Are you certain that it said apport was not installed or did was it
actually 'python3-launchpadlib' that needed installing?

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

Title:
  Bionic: ubuntu-bug / apport not present

Status in Lubuntu Next:
  Won't Fix
Status in apport package in Ubuntu:
  Triaged

Bug description:
  [I am not sure if apport was present in the previous (17.10) Lubuntu
  Next, or that as now, I had to install it...]

  I wished to report a bug, as I have often done before, and used the terminal 
to invoke ubuntu-bug.
  I was informed that I needed to install apport to gain that command.

  I did so, but then wondered if apport's absence was a mistake, or an
  intentional decision to omit the  package...

  The ability to report crashes/bugs seems like such an obvious and
  necessary thing to include, for any distro...

To manage notifications about this bug go to:
https://bugs.launchpad.net/lubuntu-next/+bug/1768970/+subscriptions

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


[Touch-packages] [Bug 1765304] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused)

2018-05-08 Thread Diep Pham
Should we just ask author of
https://salsa.debian.org/debian/ibus/commit/097e35c350edf76015c637c26ef637d80191052d
commit to know the reason why the ibus-xx-f19-password.patch is removed?
As I see from this comment in ibus' github page:
https://github.com/ibus/ibus/issues/2002#issuecomment-386537208, @Raytar
told that the problem will happen in Ubuntu 17.10 too with the patch
removed. So, I think there is no harm apply the patch to mitigate the
problem temporarily?

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

Title:
  Ubuntu 18.04's ibus package breaks password fields in Firefox (by
  lowering & raising window whenever they're focused)

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  tl;dr: starting in Ubuntu 18.04, "ibus" seems to lower and raise
  Firefox, whenever the user tries to focus an 
  field on a web page.  This is not a regression in Firefox, as the same
  Firefox version runs just fine in Ubuntu 17.10 -- it seems to be a bug
  in ibus, because it only happens (in 18.04) when the environmental
  variable GTK_IM_MODULE is at its default value (which is "ibus").  It
  had this same value in 17.10 but the bug didn't happen there; hence,
  I'm guessing there was a change in ibus (or a related package) that
  caused this breakage / lowering+raising.

  This is pretty bad, because in some cases, the focus-loss can mean users are 
simply unable to fill in password fields that previously were working fine. 
(see "ACTUAL RESULTS" below)
   
  STEPS TO REPRODUCE #1, via "BitWarden" Firefox extension:
  =
   1. Start Firefox. (fresh profile if you like)
   2. Install BitWarden from 
https://addons.mozilla.org/en-US/firefox/addon/bitwarden-password-manager/
   3. Click the BitWarden toolbar icon to spawn a menu-pane.
   4. Click "Log in" at the bottom of that pane.
   5. Click the "Master Password" field.

  ACTUAL RESULTS:
   The menu pane disappears as soon as the Master Password field receives focus.
  EXPECTED RESULTS:
   I should be able to type in a password; pane shouldn't disappear.

  
  STEPS TO REPRODUCE #2, via Reddit:
  =
   1. Visit https://www.reddit.com/r/firefox/ (or any reddit page)
   2. Click "Log in or sign up in seconds" at the extreme upper right of the 
page.
(click the "Log in" part of that sentence)
   3. Try to click the password field (or "tab" into it) and type in some text.

  ACTUAL RESULTS:
   Try as you might, the password field never receives focus.
  EXPECTED RESULTS:
   Password field should accept focus & let me type text into it.

  If I run firefox from the command line with env var GTK_IM_MODULE="",
  then I get "expected results".  But with the default value of that env
  var, I get "actual results" (broken behavior, unable to enter
  passwords).


  I initially reported this in Firefox, here:
  https://bugzilla.mozilla.org/show_bug.cgi?id=1451466 (with a few
  dependent bugs for the usage-specific STR quoted above).  But I think
  it's a bug in ibus, hence filing here now.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 18 23:22:05 2018
  InstallationDate: Installed on 2018-04-17 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1746582] Re: package lvm2 2.02.176-4.1ubuntu2 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1

2018-05-08 Thread Yevhen
I think I have found possible flow to reproduce the issue and workaround
to fix it:

1) sudo apt install lvm2

Here installation finishes successfully.

2) sudo apt remove lvm2

3) sudo apt install lvm2

Here this issue appears.

4) sudo apt purge lvm2

5) sudo apt install lvm2

Here the issue disappears and installation finishes successfully.

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

Title:
  package lvm2 2.02.176-4.1ubuntu2 failed to install/upgrade: installed
  lvm2 package post-installation script subprocess returned error exit
  status 1

Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  I *think* this was from trying to install python-guestfs

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: lvm2 2.02.176-4.1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  Date: Wed Jan 31 09:56:36 2018
  ErrorMessage: installed lvm2 package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2017-06-28 (217 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~alpha7ubuntu1
  SourcePackage: lvm2
  Title: package lvm2 2.02.176-4.1ubuntu2 failed to install/upgrade: installed 
lvm2 package post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to bionic on 2018-01-30 (0 days ago)

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

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


[Touch-packages] [Bug 1765304] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused)

2018-05-08 Thread Diep Pham
I rebuild the ibus-gtk3 package myself and it seems to work fine so far:
https://bugzilla.mozilla.org/show_bug.cgi?id=1405634#c16.

** Bug watch added: Mozilla Bugzilla #1405634
   https://bugzilla.mozilla.org/show_bug.cgi?id=1405634

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

Title:
  Ubuntu 18.04's ibus package breaks password fields in Firefox (by
  lowering & raising window whenever they're focused)

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  tl;dr: starting in Ubuntu 18.04, "ibus" seems to lower and raise
  Firefox, whenever the user tries to focus an 
  field on a web page.  This is not a regression in Firefox, as the same
  Firefox version runs just fine in Ubuntu 17.10 -- it seems to be a bug
  in ibus, because it only happens (in 18.04) when the environmental
  variable GTK_IM_MODULE is at its default value (which is "ibus").  It
  had this same value in 17.10 but the bug didn't happen there; hence,
  I'm guessing there was a change in ibus (or a related package) that
  caused this breakage / lowering+raising.

  This is pretty bad, because in some cases, the focus-loss can mean users are 
simply unable to fill in password fields that previously were working fine. 
(see "ACTUAL RESULTS" below)
   
  STEPS TO REPRODUCE #1, via "BitWarden" Firefox extension:
  =
   1. Start Firefox. (fresh profile if you like)
   2. Install BitWarden from 
https://addons.mozilla.org/en-US/firefox/addon/bitwarden-password-manager/
   3. Click the BitWarden toolbar icon to spawn a menu-pane.
   4. Click "Log in" at the bottom of that pane.
   5. Click the "Master Password" field.

  ACTUAL RESULTS:
   The menu pane disappears as soon as the Master Password field receives focus.
  EXPECTED RESULTS:
   I should be able to type in a password; pane shouldn't disappear.

  
  STEPS TO REPRODUCE #2, via Reddit:
  =
   1. Visit https://www.reddit.com/r/firefox/ (or any reddit page)
   2. Click "Log in or sign up in seconds" at the extreme upper right of the 
page.
(click the "Log in" part of that sentence)
   3. Try to click the password field (or "tab" into it) and type in some text.

  ACTUAL RESULTS:
   Try as you might, the password field never receives focus.
  EXPECTED RESULTS:
   Password field should accept focus & let me type text into it.

  If I run firefox from the command line with env var GTK_IM_MODULE="",
  then I get "expected results".  But with the default value of that env
  var, I get "actual results" (broken behavior, unable to enter
  passwords).


  I initially reported this in Firefox, here:
  https://bugzilla.mozilla.org/show_bug.cgi?id=1451466 (with a few
  dependent bugs for the usage-specific STR quoted above).  But I think
  it's a bug in ibus, hence filing here now.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 18 23:22:05 2018
  InstallationDate: Installed on 2018-04-17 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1769920] Re: Enable support for Rocky Cloud Archive

2018-05-08 Thread Launchpad Bug Tracker
** 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/1769920

Title:
  [SRU] Enable support for Rocky Cloud Archive

Status in software-properties package in Ubuntu:
  Triaged
Status in software-properties source package in Bionic:
  Triaged
Status in software-properties source package in Cosmic:
  Triaged

Bug description:
  Please add support for:

 cloud-archive:rocky
 cloud-archive:rocky-proposed

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

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

  [Test case]
  sudo add-apt-repository cloud-archive:rocky
  sudo add-apt-repository cloud-archive:rocky-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/1769920/+subscriptions

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


[Touch-packages] [Bug 1769920] Re: [SRU] Enable support for Rocky Cloud Archive

2018-05-08 Thread Corey Bryant
** Summary changed:

- Enable support for Rocky Cloud Archive
+ [SRU] Enable support for Rocky Cloud Archive

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

Title:
  [SRU] Enable support for Rocky Cloud Archive

Status in software-properties package in Ubuntu:
  Triaged
Status in software-properties source package in Bionic:
  Triaged
Status in software-properties source package in Cosmic:
  Triaged

Bug description:
  Please add support for:

 cloud-archive:rocky
 cloud-archive:rocky-proposed

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

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

  [Test case]
  sudo add-apt-repository cloud-archive:rocky
  sudo add-apt-repository cloud-archive:rocky-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/1769920/+subscriptions

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


[Touch-packages] [Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''

2018-05-08 Thread Launchpad Bug Tracker
This bug was fixed in the package ubiquity - 18.10.1

---
ubiquity (18.10.1) cosmic; urgency=medium

  [ Iain Lane ]
  * Bump sources to cosmic
  * Automatic update of included source packages: bterm-unifont 1.5,
choose-mirror 2.78ubuntu4, preseed 1.71ubuntu8.

  [ Andrea Azzarone ]
  * misc.py: Restore the corrent euid in regain_privileges_save. Calling
regain_privileges_save should restore the effective user-id to the one
before the call  to drop_privileges_save. We need to call os.setresuid and
os.setresgid twice to avoid permission issues when calling os.setgroups.
(LP: #1751252)

 -- Iain Lane   Tue, 08 May 2018 12:07:44 +0100

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

Title:
  [regression] ubiquity crashed in debconf.py:104 with ValueError:
  invalid literal for int() with base 10: ''

Status in cairo:
  Confirmed
Status in OEM Priority Project:
  Triaged
Status in cairo package in Ubuntu:
  In Progress
Status in ubiquity package in Ubuntu:
  Fix Released
Status in cairo source package in Bionic:
  In Progress
Status in ubiquity source package in Bionic:
  In Progress

Bug description:
  * Impact
  The Ubuntu installer crashes on some machines (seems more often on hiDPI 
machines (QHD/UHD etc)).

  * Test case
  Try installing Ubuntu on an hidpi machine, it should complete installation 
instead of crashing.

  * Regression potential
  The fix in ubiquity touches the code handle uid drop/privilege, that can have 
unexpected side effects so we need proper/complete testing of the installer

  --

  Update: Actually the crash occurs on slow-ish systems due to a race
  condition. It's not strictly only hi-DPI machines - that's just the
  most common place it is experienced.

  ---

  https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
  https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15
  https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7
  https://errors.ubuntu.com/problem/cb82f70f9ede07369e8104da9ddf87e28b42257d
  https://errors.ubuntu.com/problem/84a5563af3d2b85f098da832ece4cb8450bfd524

  ---

  WORKAROUND:

  1. Boot into the live session.
  2. Settings > Devices > Displays > Scale = 100%
  3. Click Apply.
  4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".

  ---

  Crashed in a VM in the middle of installation. The host is Bionic up
  to date.

  From the journal
  Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3 
ip:7f5a76936961 sp:7ffde5090c50 error:0 in 
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
  Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
  Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 757, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 135, in run
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 505, in copy_all
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 + 
copy_progress)
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 83, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw: 
self.command(command, *args, **kw))
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
  Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
  Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for 
int() with base 10: ''

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ubiquity 18.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.388
  Date: Fri Feb 23 12:52:28 2018
  ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr 
keyboard-configuration/variantcode=oss
  InterpreterPath: /usr/bin/python3.6
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  Signal: 5
  SourcePackage: ubiquity
  Stacktrace

[Touch-packages] [Bug 1762127] Re: Ubuntu stuck in loop at boot after upgrade from 17.10 to 18.04

2018-05-08 Thread tim
Removing amdgpu-pro by running "amdgpu-pro-uninstall" from ubuntu
recovery mode solved this problem for me.

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

Title:
  Ubuntu stuck in loop at boot after upgrade from 17.10 to 18.04

Status in xdiagnose package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  * I did a do-release-upgrade -d
  * After the upgrade was done, I rebooted

  Result:

  My computer was stuck in a boot loop, showing alternatively a black
  screen, a text log and a set of random pixels.

  Here is a GIF of the loop: https://imgur.com/zGGTzma

  As I had to make my computer work again I had to reinstal Ubuntu from
  a 18.04 live USB stick, so I'm not sure if I could get information
  from the previous installation. Reinstalling made my computer work
  fine with 18.04. I just need to reinstall all my applications.

  I had an external Mesa installation on 17.10 from Padoka Stable PPA.
  May it be related? At the moment, Mesa version from Padoka Stable is
  18.0.0~*~padoka0, whereas after a 18.04 reinstall it is 18.0.0-rc5

  Note: I tried to boot in safe mode with graphics, but it does not start, I 
get this error in the console:
  /usr/share/xdiagnose/failsafeXinit: line 194 : [: == : unary operator expected

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.13
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr  8 08:56:54 2018
  InstallationDate: Installed on 2018-04-07 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180403)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1769936] [NEW] [80X7, Realtek ALC236, Mic, Internal] Sound is distorted Lenovo Yoga 720

2018-05-08 Thread Asif Youssuff
Public bug reported:

Happy to do further testing, fresh install of Bionic. Discovered this
when trying to do a video conference using the built in mic and was able
to verify the issue by installing gnome-sound-recorder.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   asif   2213 F...m pulseaudio
 /dev/snd/controlC0:  asif   2213 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Tue May  8 11:58:37 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2018-04-28 (9 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
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 successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Mic, Internal
Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
Symptom_Type: Digital clip or distortion, or "overdriven" sound
Title: [80X7, Realtek ALC236, Mic, Internal] Sound is distorted
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/08/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: 4MCN31WW(V2.03)
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 31
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo YOGA 720-15IKB
dmi.modalias: 
dmi:bvnLENOVO:bvr4MCN31WW(V2.03):bd03/08/2018:svnLENOVO:pn80X7:pvrLenovoYOGA720-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA720-15IKB:
dmi.product.family: YOGA 720-15IKB
dmi.product.name: 80X7
dmi.product.version: Lenovo YOGA 720-15IKB
dmi.sys.vendor: LENOVO

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

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

Title:
  [80X7, Realtek ALC236, Mic, Internal] Sound is distorted Lenovo Yoga
  720

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Happy to do further testing, fresh install of Bionic. Discovered this
  when trying to do a video conference using the built in mic and was
  able to verify the issue by installing gnome-sound-recorder.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   asif   2213 F...m pulseaudio
   /dev/snd/controlC0:  asif   2213 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  8 11:58:37 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-04-28 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  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 successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Mic, Internal
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [80X7, Realtek ALC236, Mic, Internal] Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/08/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4MCN31WW(V2.03)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 720-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4MCN31WW(V2.03):bd03/08/2018:svnLENOVO:pn80X7:pvrLenovoYOGA720-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA720-15IKB:
  dmi.product.family: YOGA 720-15IKB
  dmi.product.name: 80X7
  dmi.product.version: Lenovo YOGA 720-15IKB
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1769936] Re: [80X7, Realtek ALC236, Mic, Internal] Sound is distorted Lenovo Yoga 720

2018-05-08 Thread Asif Youssuff
FWIW, I tried the Position_fix quirking suggestions here:
https://wiki.ubuntu.com/Audio/PositionReporting and didn't see any
improvement.

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

Title:
  [80X7, Realtek ALC236, Mic, Internal] Sound is distorted Lenovo Yoga
  720

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Happy to do further testing, fresh install of Bionic. Discovered this
  when trying to do a video conference using the built in mic and was
  able to verify the issue by installing gnome-sound-recorder.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   asif   2213 F...m pulseaudio
   /dev/snd/controlC0:  asif   2213 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  8 11:58:37 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-04-28 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  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 successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Mic, Internal
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [80X7, Realtek ALC236, Mic, Internal] Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/08/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4MCN31WW(V2.03)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 720-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4MCN31WW(V2.03):bd03/08/2018:svnLENOVO:pn80X7:pvrLenovoYOGA720-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA720-15IKB:
  dmi.product.family: YOGA 720-15IKB
  dmi.product.name: 80X7
  dmi.product.version: Lenovo YOGA 720-15IKB
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1736618] Re: debconf: Switch GNOME frontend to gtk3

2018-05-08 Thread Mantas Kriaučiūnas
** Also affects: baltix-default-settings
   Importance: Undecided
   Status: New

** Changed in: baltix-default-settings
 Assignee: (unassigned) => Mantas Kriaučiūnas (mantas)

** Changed in: baltix-default-settings
   Importance: Undecided => High

** Changed in: baltix-default-settings
   Status: New => In Progress

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

Title:
  debconf: Switch GNOME frontend to gtk3

Status in Default settings and artwork for Baltix OS:
  In Progress
Status in Debconf:
  Fix Released
Status in debconf package in Ubuntu:
  Fix Released

Bug description:
  Please switch debconf's GNOME backend to gtk3.

  debconf's GNOME backend is one of the last 3 things to pull gtk2 in to
  a default Ubuntu 18.04 install (without extra input methods). The
  other two are Firefox and Thunderbird which have fixes in progress.

To manage notifications about this bug go to:
https://bugs.launchpad.net/baltix-default-settings/+bug/1736618/+subscriptions

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


[Touch-packages] [Bug 1769941] [NEW] grep fails to match an empty line using perl regexp if it's the last line in a file

2018-05-08 Thread Evgeniy Shchetinin
Public bug reported:

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
Description:Ubuntu 16.04.4 LTS
Release:16.04

2) The version of the package you are using, via 'apt-cache policy pkgname' or 
by checking in Software Center
grep:
  Installed: 2.25-1~16.04.1
  Candidate: 2.25-1~16.04.1
  Version table:
 *** 2.25-1~16.04.1 500
500 http://ru.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 2.24-1 500
500 http://ru.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

3) What you expected to happen
(echo 123; echo; ) | grep -P '^$'
$ # output contains one empty line
$ (echo 123; echo;) | grep -P '^$'

$

4) What happened instead
$ # output contains no line
$ (echo 123; echo;) | grep -P '^$'
$

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: grep 2.25-1~16.04.1
ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
CurrentDesktop: Unity
Date: Tue May  8 18:49:45 2018
InstallationDate: Installed on 2018-02-13 (83 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
SourcePackage: grep
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  grep fails to match an empty line using perl regexp if it's the last
  line in a file

Status in grep package in Ubuntu:
  New

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  grep:
Installed: 2.25-1~16.04.1
Candidate: 2.25-1~16.04.1
Version table:
   *** 2.25-1~16.04.1 500
  500 http://ru.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.24-1 500
  500 http://ru.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  3) What you expected to happen
  (echo 123; echo; ) | grep -P '^$'
  $ # output contains one empty line
  $ (echo 123; echo;) | grep -P '^$'

  $

  4) What happened instead
  $ # output contains no line
  $ (echo 123; echo;) | grep -P '^$'
  $

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: grep 2.25-1~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue May  8 18:49:45 2018
  InstallationDate: Installed on 2018-02-13 (83 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: grep
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 19749] Re: SATA HDD not recognized during Breezy Colony 4 install or Dapper Flight 3 or Edgy Eft or Feisty Fawn

2018-05-08 Thread Phillip Susi
** Changed in: linux-source-2.6.15 (Ubuntu)
 Assignee: Anuradha ishan (123ishan) => Ben Collins (ben-collins)

** Changed in: linux (Ubuntu)
 Assignee: Anuradha ishan (123ishan) => (unassigned)

** Changed in: initramfs-tools (Ubuntu)
 Assignee: Anuradha ishan (123ishan) => (unassigned)

** Changed in: linux-source-2.6.20 (Ubuntu)
 Assignee: Anuradha ishan (123ishan) => (unassigned)

** Changed in: ubiquity (Ubuntu)
 Assignee: Anuradha ishan (123ishan) => (unassigned)

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

Title:
  SATA HDD not recognized during Breezy Colony 4 install or Dapper
  Flight 3 or Edgy Eft or Feisty Fawn

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-source-2.6.15 package in Ubuntu:
  Won't Fix
Status in linux-source-2.6.20 package in Ubuntu:
  Won't Fix
Status in ubiquity package in Ubuntu:
  Fix Released

Bug description:
  Machine is a Canonical supplied Toshiba Portege S100 - S113TD. Intel Pentium M
  Processor 740 [1.73Ghz, 2MB L2 cache, 533Mhz FSB]. Mobile Intel 915PM Express
  Chipset. Intel PRO/Wireless 2200BG WiFi. 512MB PC4200 DDR2 RAM. 60GB, 5400RPM
  Serial-ATA HDD. 

  Jeff Waugh pretty much told me that Hoary wouldn't run on this machine, so I
  went straight to Breezy Colony 2. I'm able to boot the CD, choose my location
  and language, and the installer stops because it's unable to detect a HDD. 
I've
  tried passing all the various ACPI options during boot with no success. The
  machine also supports Intel's software RAID, which I've tried disabling via
  Toshiba's own sparse BIOS settings with no success.

  I was able to mount a USB thumbdrive while in the installer and save some
  diagnostic stuff and the logs in /var/log. They can be found at the URL I
  provided. Additionally, ArminRonacher has added some notes to my Laptop 
Testing
  Team page confirming what I've also found - that nobody has been able to 
install
  Linux on this machine yet. That page can be found here:

  https://wiki.ubuntu.com/LaptopTestingTeam/ToshibaPortegeS100

  I can get to a console while in the installer if there are additional
  diagnostics that would be helpful. Just let me know.

  breezy log files: http://www.volvoguy.net/ubuntu/laptop-breezy/
  dapper log files: http://www.volvoguy.net/ubuntu/laptop-dapper/

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

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


[Touch-packages] [Bug 1663050] Re: Intel 7265 wireless device disconnect: link is not ready

2018-05-08 Thread Ubuntu Kernel Bot
** Package changed: linux-hwe (Ubuntu) => linux (Ubuntu)

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

Title:
  Intel 7265 wireless device disconnect: link is not ready

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

Bug description:
  The wifi device disconnect sometime randomly or sometime when switching 
hotspot with the following dmesg output:
  [ 1039.212949] iwlwifi :01:00.0: L1 Enabled - LTR Enabled
  [ 1039.213503] iwlwifi :01:00.0: L1 Enabled - LTR Enabled
  [ 1039.221549] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 1039.221561] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 1039.221566] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 1039.221569] pcieport :00:1c.0:[ 0] Receiver Error (First)
  [ 1039.239086] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready

  The device at pcieport :00:1c.0 seems to be the Intel 7265 wireless:
  $ lspci -tv
  -[:00]-+-00.0  Intel Corporation Device 5904
 +-02.0  Intel Corporation Device 5916
 +-14.0  Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller
 +-14.2  Intel Corporation Sunrise Point-LP Thermal subsystem
 +-16.0  Intel Corporation Sunrise Point-LP CSME HECI #1
 +-17.0  Intel Corporation Sunrise Point-LP SATA Controller [AHCI 
mode]
 +-1c.0-[01]00.0  Intel Corporation Wireless 7265
 +-1d.0-[02]00.0  Samsung Electronics Co Ltd NVMe SSD Controller
 +-1f.0  Intel Corporation Device 9d58
 +-1f.2  Intel Corporation Sunrise Point-LP PMC
 +-1f.3  Intel Corporation Device 9d71
 \-1f.4  Intel Corporation Sunrise Point-LP SMBus

  To allow the device to connect again I use the following:
  $ sudo systemctl restart network-manager.service

  That said, the pcieport :00:1c.0 dmesg outputs sometimes appears
  without affecting the wifi connection...

  $ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  $ inxi -Abd
  System:Host: 710s Kernel: 4.4.0-62-generic x86_64 (64 bit) Desktop: Unity 
7.4.0  Distro: Ubuntu 16.04 xenial
  Machine:   System: LENOVO (portable) product: 80VQ v: Lenovo ideapad 
710S-13IKB
 Mobo: LENOVO model: Lenovo ideapad 710S-13IKB v: SDK0J40709 WIN
 Bios: LENOVO v: 3HCN12S2 date: 10/07/2016
  CPU:   Dual core Intel Core i7-7500U (-HT-MCP-) speed/max: 600/2701 MHz
  Graphics:  Card: Intel Device 5916
 Display Server: X.Org 1.18.4 drivers: intel (unloaded: fbdev,vesa) 
Resolution: 1920x1080@60.02hz
 GLX Renderer: Mesa DRI Intel Kabylake GT2 GLX Version: 3.0 Mesa 
11.2.0
  Audio: Card Intel Device 9d71 driver: snd_hda_intel Sound: ALSA v: 
k4.4.0-62-generic
  Network:   Card: Intel Wireless 7265 driver: iwlwifi
  Drives:HDD Total Size: NA (-) ID-1: /dev/nvme0n1 model: N/A size: 256.1GB
 Optical: No optical drives detected.
  Info:  Processes: 244 Uptime: 34 min Memory: 2000.8/7876.3MB Client: 
Shell (bash) inxi: 2.2.35

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

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


[Touch-packages] [Bug 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.

2018-05-08 Thread Antonio Pérez
What a shame! In this situations I always remember Linus Torvalds words:
never break user experience.

https://felipec.wordpress.com/2013/10/07/the-linux-way/
https://unix.stackexchange.com/a/235532

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

Title:
  After last updated libcurl3 on libcurl4, some apps are removed.

Status in curl package in Ubuntu:
  Confirmed

Bug description:
  Hi!

  After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) 
deleted such applications as:
  virtualbox-5.2
  opera-stable
  slack-desktop

  I really need these applications, I installed them with broken
  dependencies, but they are deleted after each update. Is it possible
  to make the dependence of the libcurl3 in libcurl4, and not remove it
  altogether from system?

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

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


[Touch-packages] [Bug 1746582] Re: package lvm2 2.02.176-4.1ubuntu2 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1

2018-05-08 Thread Yevhen
In my case I have installed gnome-boxes before, lvm2 was installed as
dependency. Then I removed gnome-boxes and made apt autoremove. I think
after that the issue appeared for me.

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

Title:
  package lvm2 2.02.176-4.1ubuntu2 failed to install/upgrade: installed
  lvm2 package post-installation script subprocess returned error exit
  status 1

Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  I *think* this was from trying to install python-guestfs

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: lvm2 2.02.176-4.1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  Date: Wed Jan 31 09:56:36 2018
  ErrorMessage: installed lvm2 package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2017-06-28 (217 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~alpha7ubuntu1
  SourcePackage: lvm2
  Title: package lvm2 2.02.176-4.1ubuntu2 failed to install/upgrade: installed 
lvm2 package post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to bionic on 2018-01-30 (0 days ago)

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

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


[Touch-packages] [Bug 1769977] [NEW] jackd2 don't install in fresh installation of Ubuntu 18.04 LTS

2018-05-08 Thread Esteban
Public bug reported:

jackd2 package don't install in Ubuntu 18.04 LTS.

Broken dependencies, libreadline6 can't be installed anymore.

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

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

Title:
  jackd2 don't install in fresh installation of Ubuntu 18.04 LTS

Status in jackd2 package in Ubuntu:
  New

Bug description:
  jackd2 package don't install in Ubuntu 18.04 LTS.

  Broken dependencies, libreadline6 can't be installed anymore.

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

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


[Touch-packages] [Bug 1635382] Re: PrivateNetwork=yes (hostnamed, localed) does not work in lxd

2018-05-08 Thread Christian Brauner
What? That's totally possible. Simply try unshare -n inside an
unprivileged container as root.

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

Title:
  PrivateNetwork=yes (hostnamed, localed) does not work in lxd

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  $ lxc launch ubuntu-daily:yakkety y-hostname1
  $ sleep 10
  $ lxc exec y-hostname1 -- hostnamectl set-hostname smoser
  
  Could not set property: Connection timed out

  $ lxc exec y-hostname1 -- systemctl status --no-pager -l systemd-hostnamed 
  ● systemd-hostnamed.service - Hostname Service
 Loaded: loaded (/lib/systemd/system/systemd-hostnamed.service; static; 
vendor preset: enabled)
 Active: failed (Result: exit-code) since Thu 2016-10-20 19:19:16 UTC; 1min 
9s ago
   Docs: man:systemd-hostnamed.service(8)
 man:hostname(5)
 man:machine-info(5)
 http://www.freedesktop.org/wiki/Software/systemd/hostnamed
Process: 561 ExecStart=/lib/systemd/systemd-hostnamed (code=exited, 
status=225/NETWORK)
   Main PID: 561 (code=exited, status=225/NETWORK)

  Oct 20 19:19:16 y-hostname1 systemd[1]: Starting Hostname Service...
  Oct 20 19:19:16 y-hostname1 systemd[1]: systemd-hostnamed.service: Main 
process exited, code=exited, status=225/NETWORK
  Oct 20 19:19:16 y-hostname1 systemd[1]: Failed to start Hostname Service.
  Oct 20 19:19:16 y-hostname1 systemd[1]: systemd-hostnamed.service: Unit 
entered failed state.
  Oct 20 19:19:16 y-hostname1 systemd[1]: systemd-hostnamed.service: Failed 
with result 'exit-code'.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-9git1
  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: Thu Oct 20 19:02:29 2016
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic.efi.signed 
root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.vendor: Intel Corporation

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

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


[Touch-packages] [Bug 1751303] Re: util-linux 2.27.1-6ubuntu3.4 subprocess installed post-installation script returned error exit status 139

2018-05-08 Thread Phillip Susi
Please run the memtest option from the boot menu for at least 15 minutes
and let us know if it finds problems.


** Changed in: util-linux (Ubuntu)
   Status: New => Incomplete

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

Title:
  util-linux 2.27.1-6ubuntu3.4  subprocess installed post-installation
  script returned error exit status 139

Status in util-linux package in Ubuntu:
  Incomplete

Bug description:
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04


  
  Need to get 0 B/38.0 MB of archives.
  After this operation, 247 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Segmentation fault (core dumped)
  Setting up util-linux (2.27.1-6ubuntu3.4) ...
  Segmentation fault (core dumped)
  dpkg: error processing package util-linux (--configure):
   subprocess installed post-installation script returned error exit status 139
  Errors were encountered while processing:
   util-linux
  E: Sub-process /usr/bin/dpkg returned an error code (1)


  from syslog:

  Feb 23 09:17:51 faxor kernel: [ 1707.779093] dpkg-preconfigu[3359]: segfault 
at 126cfc8 ip 004bec94 sp 7ffcc3f59e00 error 6 in 
perl[40+1cf000]
  Feb 23 09:17:51 faxor kernel: [ 1707.946664] update-rc.d[3368]: segfault at 
1b4 ip 004bea0a sp 7ffc091a9b40 error 4 in perl[40+1cf000]
  Feb 23 09:17:51 faxor kernel: [ 1708.068377] update-rc.d[3370]: segfault at 
1b4 ip 004bea0a sp 7ffce3c40040 error 4 in perl[40+1cf000]

  apt-cache policy util-linux

  util-linux:
Installed: 2.27.1-6ubuntu3.4
Candidate: 2.27.1-6ubuntu3.4
Version table:
   *** 2.27.1-6ubuntu3.4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.27.1-6ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

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

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


[Touch-packages] [Bug 1749662] Re: package util-linux 2.27.1-6ubuntu3.4 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1

2018-05-08 Thread Phillip Susi
You have a broken init script installed named lwsmd.  You will need to
remove it.


** Changed in: util-linux (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  package util-linux 2.27.1-6ubuntu3.4 failed to install/upgrade: el
  subproceso instalado el script post-installation devolvió el código de
  salida de error 1

Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  apt upgrade
  Leyendo lista de paquetes... Hecho
  Creando árbol de dependencias   
  Leyendo la información de estado... Hecho
  Calculando la actualización... Hecho
  Se actualizarán los siguientes paquetes:
libblkid1 libfdisk1 libmount1 libsmartcols1 libunity-control-center1 
libuuid1 libuuid1:i386 mount unity-control-center unity-control-center-faces 
util-linux uuid-runtime
  12 actualizados, 0 nuevos se instalarán, 0 para eliminar y 0 no actualizados.
  1 no instalados del todo o eliminados.
  Se necesita descargar 2.546 kB de archivos.
  Se utilizarán 8.192 B de espacio de disco adicional después de esta operación.
  ¿Desea continuar? [S/n] s
  Des:1 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 util-linux 
amd64 2.27.1-6ubuntu3.4 [849 kB]
  Des:2 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 mount amd64 
2.27.1-6ubuntu3.4 [121 kB]
  Des:3 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 uuid-runtime 
amd64 2.27.1-6ubuntu3.4 [26,1 kB]
  Des:4 http://archive.ubuntu.com/ubuntu xenial-updates/main i386 libuuid1 i386 
2.27.1-6ubuntu3.4 [16,3 kB]
  Des:5 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 libuuid1 
amd64 2.27.1-6ubuntu3.4 [15,2 kB]
  Des:6 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 libblkid1 
amd64 2.27.1-6ubuntu3.4 [107 kB]
  Des:7 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 libfdisk1 
amd64 2.27.1-6ubuntu3.4 [139 kB]
  Des:8 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 libmount1 
amd64 2.27.1-6ubuntu3.4 [114 kB]
  Des:9 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
libsmartcols1 amd64 2.27.1-6ubuntu3.4 [62,8 kB]
  Des:10 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
libunity-control-center1 amd64 15.04.0+16.04.20171130-0ubuntu1 [81,1 kB]
  Des:11 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
unity-control-center amd64 15.04.0+16.04.20171130-0ubuntu1 [835 kB]
  Des:12 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
unity-control-center-faces all 15.04.0+16.04.20171130-0ubuntu1 [180 kB]
  Descargados 2.546 kB en 2s (957 kB/s)
  (Leyendo la base de datos ... 287355 ficheros o directorios instalados 
actualmente.)
  Preparando para desempaquetar .../util-linux_2.27.1-6ubuntu3.4_amd64.deb ...
  Desempaquetando util-linux (2.27.1-6ubuntu3.4) sobre (2.27.1-6ubuntu3.3) ...
  Procesando disparadores para ureadahead (0.100.0-19) ...
  Procesando disparadores para man-db (2.7.5-1) ...
  Procesando disparadores para mime-support (3.59ubuntu1) ...
  Configurando util-linux (2.27.1-6ubuntu3.4) ...
  insserv: Script lwsmd is broken: incomplete LSB comment.
  insserv: missing `Provides:' entry: please add.
  insserv: missing `Required-Start:' entry: please add even if empty.
  insserv: missing `Required-Stop:'  entry: please add even if empty.
  insserv: missing `Default-Start:'  entry: please add even if empty.
  insserv: missing `Default-Stop:'   entry: please add even if empty.
  insserv: warning: script 'K01GlassFish_aytohuelva' missing LSB tags and 
overrides
  insserv: warning: script 'K01postgresql-9.4' missing LSB tags and overrides
  insserv: Script likewise is broken: incomplete LSB comment.
  insserv: missing `Provides:' entry: please add.
  insserv: missing `Required-Start:' entry: please add even if empty.
  insserv: missing `Required-Stop:'  entry: please add even if empty.
  insserv: missing `Default-Start:'  entry: please add even if empty.
  insserv: missing `Default-Stop:'   entry: please add even if empty.
  insserv: Script lwsmd is broken: incomplete LSB comment.
  insserv: missing `Provides:' entry: please add.
  insserv: missing `Required-Start:' entry: please add even if empty.
  insserv: missing `Required-Stop:'  entry: please add even if empty.
  insserv: missing `Default-Start:'  entry: please add even if empty.
  insserv: missing `Default-Stop:'   entry: please add even if empty.
  insserv: Script likewise is broken: incomplete LSB comment.
  insserv: missing `Provides:' entry: please add.
  insserv: missing `Required-Start:' entry: please add even if empty.
  insserv: missing `Required-Stop:'  entry: please add even if empty.
  insserv: missing `Default-Start:'  entry: please add even if empty.
  insserv: missing `Default-Stop:'   entry: please add even if empty.
  insserv: Script likewise is broken: incomplete LSB comment.
  insserv: missing 

[Touch-packages] [Bug 1769682] Re: NFS-based remote root hangs when running 'netplan apply'

2018-05-08 Thread Mathieu Trudel-Lapierre
** Also affects: initramfs-tools (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: nplan (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: netplan.io (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

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

** Also affects: netplan.io (Ubuntu Artful)
   Importance: Undecided
   Status: New

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

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

** Also affects: netplan.io (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

** Changed in: netplan.io (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: netplan.io (Ubuntu Artful)
   Status: New => Invalid

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

Title:
  NFS-based remote root hangs when running 'netplan apply'

Status in initramfs-tools package in Ubuntu:
  New
Status in netplan.io package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  Invalid
Status in initramfs-tools source package in Xenial:
  New
Status in netplan.io source package in Xenial:
  Invalid
Status in nplan source package in Xenial:
  New
Status in initramfs-tools source package in Artful:
  New
Status in netplan.io source package in Artful:
  Invalid
Status in nplan source package in Artful:
  New
Status in initramfs-tools source package in Bionic:
  New
Status in netplan.io source package in Bionic:
  New
Status in nplan source package in Bionic:
  Invalid

Bug description:
  [Impact]
  Netboot users with a remote filesystem over NFS (possibly over other 
networked filesystems).

  [Test cases]
  1) Boot a system with its root filesystem over NFS.
  2) Run 'sudo netplan apply'
  3) Validate that the system remains responsive and keeps connectivity over 
the same IP address  as it had.

  [Regression potential]
  This SRU changes network properties, and enforces that networkd does not 
release and re-request an IP address from DHCP when it is restarted. 
Environments relying on the IP release/renew behavior may find themselves 
staying on the previous IP address, which might negatively impact connectivity. 
Changes in connectivity on a system running netplan should be investigated as a 
potential regression from this SRU. Other regression possibilities would 
include failure to get a new IP address over time (usually seen as losing 
connectivity) or possible IP conflicts on a network.

  ---

  With a system booted on the network, with its remote root fs on NFS:

  Running 'netplan apply' restarts systemd-networkd, which releases the
  IP received from DHCP. With no IP (and and IP potentially changing),
  the NFS server can't be reached so the system hangs.

  'netplan apply' or restarting systemd-networkd should not affect teh
  system, it should continue working normally despite "changing" network
  states, as long as the effective IP remains the same.

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

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


[Touch-packages] [Bug 1769682] Re: NFS-based remote root hangs when running 'netplan apply'

2018-05-08 Thread Brian Murray
Hello Mathieu, or anyone else affected,

Accepted netplan.io into bionic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/netplan.io/0.36.2
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: netplan.io (Ubuntu Bionic)
   Status: New => Fix Committed

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

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

Title:
  NFS-based remote root hangs when running 'netplan apply'

Status in initramfs-tools package in Ubuntu:
  New
Status in netplan.io package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  Invalid
Status in initramfs-tools source package in Xenial:
  New
Status in netplan.io source package in Xenial:
  Invalid
Status in nplan source package in Xenial:
  New
Status in initramfs-tools source package in Artful:
  New
Status in netplan.io source package in Artful:
  Invalid
Status in nplan source package in Artful:
  New
Status in initramfs-tools source package in Bionic:
  New
Status in netplan.io source package in Bionic:
  Fix Committed
Status in nplan source package in Bionic:
  Invalid

Bug description:
  [Impact]
  Netboot users with a remote filesystem over NFS (possibly over other 
networked filesystems).

  [Test cases]
  1) Boot a system with its root filesystem over NFS.
  2) Run 'sudo netplan apply'
  3) Validate that the system remains responsive and keeps connectivity over 
the same IP address  as it had.

  [Regression potential]
  This SRU changes network properties, and enforces that networkd does not 
release and re-request an IP address from DHCP when it is restarted. 
Environments relying on the IP release/renew behavior may find themselves 
staying on the previous IP address, which might negatively impact connectivity. 
Changes in connectivity on a system running netplan should be investigated as a 
potential regression from this SRU. Other regression possibilities would 
include failure to get a new IP address over time (usually seen as losing 
connectivity) or possible IP conflicts on a network.

  ---

  With a system booted on the network, with its remote root fs on NFS:

  Running 'netplan apply' restarts systemd-networkd, which releases the
  IP received from DHCP. With no IP (and and IP potentially changing),
  the NFS server can't be reached so the system hangs.

  'netplan apply' or restarting systemd-networkd should not affect teh
  system, it should continue working normally despite "changing" network
  states, as long as the effective IP remains the same.

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

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


[Touch-packages] [Bug 1769682] Re: NFS-based remote root hangs when running 'netplan apply'

2018-05-08 Thread Brian Murray
Hello Mathieu, or anyone else affected,

Accepted nplan into artful-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/nplan/0.32~17.10.4 in
a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-artful to verification-done-artful. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-artful. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: nplan (Ubuntu Artful)
   Status: New => Fix Committed

** Tags added: verification-needed-artful

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

Title:
  NFS-based remote root hangs when running 'netplan apply'

Status in initramfs-tools package in Ubuntu:
  New
Status in netplan.io package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  Invalid
Status in initramfs-tools source package in Xenial:
  New
Status in netplan.io source package in Xenial:
  Invalid
Status in nplan source package in Xenial:
  New
Status in initramfs-tools source package in Artful:
  New
Status in netplan.io source package in Artful:
  Invalid
Status in nplan source package in Artful:
  Fix Committed
Status in initramfs-tools source package in Bionic:
  New
Status in netplan.io source package in Bionic:
  Fix Committed
Status in nplan source package in Bionic:
  Invalid

Bug description:
  [Impact]
  Netboot users with a remote filesystem over NFS (possibly over other 
networked filesystems).

  [Test cases]
  1) Boot a system with its root filesystem over NFS.
  2) Run 'sudo netplan apply'
  3) Validate that the system remains responsive and keeps connectivity over 
the same IP address  as it had.

  [Regression potential]
  This SRU changes network properties, and enforces that networkd does not 
release and re-request an IP address from DHCP when it is restarted. 
Environments relying on the IP release/renew behavior may find themselves 
staying on the previous IP address, which might negatively impact connectivity. 
Changes in connectivity on a system running netplan should be investigated as a 
potential regression from this SRU. Other regression possibilities would 
include failure to get a new IP address over time (usually seen as losing 
connectivity) or possible IP conflicts on a network.

  ---

  With a system booted on the network, with its remote root fs on NFS:

  Running 'netplan apply' restarts systemd-networkd, which releases the
  IP received from DHCP. With no IP (and and IP potentially changing),
  the NFS server can't be reached so the system hangs.

  'netplan apply' or restarting systemd-networkd should not affect teh
  system, it should continue working normally despite "changing" network
  states, as long as the effective IP remains the same.

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

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


[Touch-packages] [Bug 1732002] Re: cloud images in lxc get ipv6 address

2018-05-08 Thread Brian Murray
Hello Scott, or anyone else affected,

Accepted nplan into artful-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/nplan/0.32~17.10.4 in
a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-artful to verification-done-artful. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-artful. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: nplan (Ubuntu Artful)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-artful

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

Title:
  cloud images in lxc get ipv6 address

Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  New
Status in nplan source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  All users of netplan.

  [Test case]

  == LXD containers ==
  1) Start an LXD container (artful or bionic)
  2) Verify that an IPv6 address is present
  3) Verify that the system is brought up in a reasonable time (does not wait 2 
minutes to be reachable).

  == servers / cloud instances ==
  1) Start a bionic system, with no IPv6 connectivity (no router to advertise a 
prefix)
  2) Verify that the system boots quickly (does not wait 2 minutes to be 
reachable).

  [Regression potential]
  Since this changes default IPv6 behavior, care should be taken to validate 
that systems are maintaining IPv6 connectivity when it is available, and 
similarly that systems where no IPv6 connectivity is available on the network 
are behaving correctly: there should not be long boot delays, and no extra IPv6 
addresses aside from link-local addresses generated by the kernel.

  --

  I noticed that lxd (lxc list) reports that an lxc container has an
  ipv6 address in artful or bionic.  It does not list this in xenial or
  zesty.  I suspect this change occurred in the switch over to
  netplan/networkd.

  This may at first seem harmless or even desired, but note that the
  user configuration did not request ipv6 config, so its presence is a
  bug.

  $ for rel in xenial zesty artful bionic; do
     lxc launch ubuntu-daily:$rel $rel-demo; done
  Creating xenial-demo
  Starting xenial-demo
  ..
  Creating bionic-demo
  Starting bionic-demo

  $ sleep 10
  $ lxc list
  $ lxc list
  
+-+-+--+++---+
  |NAME |  STATE  | IPV4 |  IPV6
  |TYPE| SNAPSHOTS |
  
+-+-+--+++---+
  | artful-demo | RUNNING | 10.75.205.208 (eth0) | 
fd42:eee5:7c43:3d62:3a42:611c:3f6f:1184 (eth0) | PERSISTENT | 0 |
  
+-+-+--+++---+
  | bionic-demo | RUNNING | 10.75.205.187 (eth0) | 
fd42:eee5:7c43:3d62:6f4:155b:39cc:fc3d (eth0)  | PERSISTENT | 0 |
  
+-+-+--+++---+
  | xenial-demo | RUNNING | 10.75.205.143 (eth0) |  
  | PERSISTENT | 0 |
  
+-+-+--+++---+
  | zesty-demo  | RUNNING | 10.75.205.123 (eth0) |  
  | PERSISTENT | 0 |
  
+-+-+--+++---+

  ## Here is the config that was provided by lxd
  $ lxc exec bionic-demo cat /var/lib/cloud/seed/nocloud-net/network-config
  version: 1
  config:
  - type: physical
    name: eth0
    subnets:
    - type: dhcp
  control: auto

  ## Here is the config that cloud-init rendered.
  $ lxc exec bionic-demo -- grep -v '^#' /etc/netplan/50-cloud-init.yaml
  network:
  version: 2
  ethernets:
  eth0:
  dhcp4: true

  $ lxc exec bionic-demo cat /run/systemd/network/10-netplan-eth0.network
  [Match]
  Name=e

[Touch-packages] [Bug 1732002] Re: cloud images in lxc get ipv6 address

2018-05-08 Thread Brian Murray
Hello Scott, or anyone else affected,

Accepted nplan into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/nplan/0.32~16.04.5 in
a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: nplan (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed-xenial

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

Title:
  cloud images in lxc get ipv6 address

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

Bug description:
  [Impact]
  All users of netplan.

  [Test case]

  == LXD containers ==
  1) Start an LXD container (artful or bionic)
  2) Verify that an IPv6 address is present
  3) Verify that the system is brought up in a reasonable time (does not wait 2 
minutes to be reachable).

  == servers / cloud instances ==
  1) Start a bionic system, with no IPv6 connectivity (no router to advertise a 
prefix)
  2) Verify that the system boots quickly (does not wait 2 minutes to be 
reachable).

  [Regression potential]
  Since this changes default IPv6 behavior, care should be taken to validate 
that systems are maintaining IPv6 connectivity when it is available, and 
similarly that systems where no IPv6 connectivity is available on the network 
are behaving correctly: there should not be long boot delays, and no extra IPv6 
addresses aside from link-local addresses generated by the kernel.

  --

  I noticed that lxd (lxc list) reports that an lxc container has an
  ipv6 address in artful or bionic.  It does not list this in xenial or
  zesty.  I suspect this change occurred in the switch over to
  netplan/networkd.

  This may at first seem harmless or even desired, but note that the
  user configuration did not request ipv6 config, so its presence is a
  bug.

  $ for rel in xenial zesty artful bionic; do
     lxc launch ubuntu-daily:$rel $rel-demo; done
  Creating xenial-demo
  Starting xenial-demo
  ..
  Creating bionic-demo
  Starting bionic-demo

  $ sleep 10
  $ lxc list
  $ lxc list
  
+-+-+--+++---+
  |NAME |  STATE  | IPV4 |  IPV6
  |TYPE| SNAPSHOTS |
  
+-+-+--+++---+
  | artful-demo | RUNNING | 10.75.205.208 (eth0) | 
fd42:eee5:7c43:3d62:3a42:611c:3f6f:1184 (eth0) | PERSISTENT | 0 |
  
+-+-+--+++---+
  | bionic-demo | RUNNING | 10.75.205.187 (eth0) | 
fd42:eee5:7c43:3d62:6f4:155b:39cc:fc3d (eth0)  | PERSISTENT | 0 |
  
+-+-+--+++---+
  | xenial-demo | RUNNING | 10.75.205.143 (eth0) |  
  | PERSISTENT | 0 |
  
+-+-+--+++---+
  | zesty-demo  | RUNNING | 10.75.205.123 (eth0) |  
  | PERSISTENT | 0 |
  
+-+-+--+++---+

  ## Here is the config that was provided by lxd
  $ lxc exec bionic-demo cat /var/lib/cloud/seed/nocloud-net/network-config
  version: 1
  config:
  - type: physical
    name: eth0
    subnets:
    - type: dhcp
  control: auto

  ## Here is the config that cloud-init rendered.
  $ lxc exec bionic-demo -- grep -v '^#' /etc/netplan/50-cloud-init.yaml
  network:
  version: 2
  ethernets:
  eth0:
  dhcp4: true

  $ lxc exec bionic-demo cat /run/systemd/network/10-n

[Touch-packages] [Bug 1756322] Re: 'netplan apply' fails when trying to activate another interface on another QETH device ...

2018-05-08 Thread Brian Murray
Hello Frank, or anyone else affected,

Accepted nplan into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/nplan/0.32~16.04.5 in
a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: nplan (Ubuntu Artful)
   Status: New => Won't Fix

** Changed in: nplan (Ubuntu Xenial)
   Status: New => Fix Committed

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

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

Title:
  'netplan apply' fails when trying to activate another interface on
  another QETH device ...

Status in netplan:
  Fix Released
Status in Ubuntu on IBM z Systems:
  Fix Released
Status in netplan.io package in Ubuntu:
  Fix Released
Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Invalid
Status in netplan.io source package in Xenial:
  Invalid
Status in nplan source package in Xenial:
  Fix Committed
Status in systemd source package in Xenial:
  Invalid
Status in netplan.io source package in Artful:
  Invalid
Status in nplan source package in Artful:
  Won't Fix
Status in systemd source package in Artful:
  Invalid

Bug description:
  [Impact]
  Server users on s390x configuring qeth devices.

  [Test case]
  1) Reconfigure an interface for a QETH device
  2) Verify that 'netplan apply' completes successfully, without error.

  [Regression potential]
  This change has minimal potential for regression, and it only skip qeth-based 
devices from "replugging", which "disconnects" them by unbinding and rebinding 
the driver. Potential issues would be limited to failure to rename interfaces 
without a reboot, for configurations that depend on this (but it already would 
not have worked due to netplan apply failing to rebind the device).

  ---

  When trying to add another interface for a QETH device on a s390x
  system netplan apply fails:

  sudo netplan apply
  Cannot replug encc003: [Errno 19] No such device
  Traceback (most recent call last):
    File "/usr/sbin/netplan", line 23, in 
  netplan.main()
    File "/usr/share/netplan/netplan/cli/core.py", line 50, in main
  self.run_command()
    File "/usr/share/netplan/netplan/cli/utils.py", line 110, in run_command
  self.func()
    File "/usr/share/netplan/netplan/cli/commands/apply.py", line 40, in run
  self.run_command()
    File "/usr/share/netplan/netplan/cli/utils.py", line 110, in run_command
  self.func()
    File "/usr/share/netplan/netplan/cli/commands/apply.py", line 87, in 
command_apply
  stdout=fd, stderr=fd)
    File "/usr/lib/python3.6/subprocess.py", line 291, in check_call
  raise CalledProcessError(retcode, cmd)
  subprocess.CalledProcessError: Command '['udevadm', 'test-builtin', 
'net_setup_link', '/sys/class/net/encc003']' returned non-zero exit status 4.

  It seems like rebinding of qeth devices is not allowed.
  With qeth devices, I guess one needs to "offline & online" them...
  Or like unbind a whole group of them, as there are three of them per 
interface.

  ubuntu@s1lp14:/sys/class/net/encc006/device$ ls -latr
  total 0
  drwxr-xr-x 5 root root0 Mar 16 02:06 ..
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 uevent
  drwxr-xr-x 6 root root0 Mar 16 13:44 .
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 online
  lrwxrwxrwx 1 root root0 Mar 16 13:44 subsystem -> ../../../bus/ccwgroup
  lrwxrwxrwx 1 root root0 Mar 16 13:44 driver -> 
../../../bus/ccwgroup/drivers/qeth
  drwxr-xr-x 2 root root0 Mar 16 13:44 vnicc
  --w--- 1 root root 4096 Mar 16 13:44 recover
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 priority_queueing
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 portno
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 portname
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 performance_stats
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 layer2
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 isolation
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 hw_trap
  lrwxrwxrwx 1 root root0 Mar 16 13:44 cdev2 -> ../../css0/0.0.0bb4/0.0.c008
  lrwxrwxrwx 1 root root0 Mar 16 13:44 cdev1 -> ../..

[Touch-packages] [Bug 1752411] Re: bind9-host, avahi-daemon-check-dns.sh hang forever causes network connections to get stuck

2018-05-08 Thread Bug Watch Updater
** Changed in: avahi (Debian)
   Status: Unknown => New

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

Title:
  bind9-host, avahi-daemon-check-dns.sh hang forever causes network
  connections to get stuck

Status in avahi package in Ubuntu:
  Confirmed
Status in bind9 package in Ubuntu:
  Confirmed
Status in openconnect package in Ubuntu:
  Invalid
Status in avahi package in Debian:
  New

Bug description:
  On 18.04 Openconnect connects successfully to any of multiple VPN
  concentrators but network traffic does not flow across the VPN tunnel
  connection. When testing on 16.04 this works flawlessly. This also
  worked on this system when it was on 17.10.

  I have tried reducing the mtu of the tun0 network device but this has
  not resulted in me being able to successfully ping the IP address.

  Example showing ping attempt to the IP of DNS server:

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

  nameserver 172.29.88.11
  nameserver 127.0.0.53

  liam@liam-lat:~$ netstat -nr
  Kernel IP routing table
  Destination Gateway Genmask Flags   MSS Window  irtt Iface
  0.0.0.0 192.168.1.1 0.0.0.0 UG0 0  0 
wlp2s0
  105.27.198.106  192.168.1.1 255.255.255.255 UGH   0 0  0 
wlp2s0
  169.254.0.0 0.0.0.0 255.255.0.0 U 0 0  0 
docker0
  172.17.0.0  0.0.0.0 255.255.0.0 U 0 0  0 
docker0
  172.29.0.0  0.0.0.0 255.255.0.0 U 0 0  0 tun0
  172.29.88.110.0.0.0 255.255.255.255 UH0 0  0 tun0
  192.168.1.0 0.0.0.0 255.255.255.0   U 0 0  0 
wlp2s0
  liam@liam-lat:~$ ping 172.29.88.11
  PING 172.29.88.11 (172.29.88.11) 56(84) bytes of data.
  ^C
  --- 172.29.88.11 ping statistics ---
  4 packets transmitted, 0 received, 100% packet loss, time 3054ms

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: openconnect 7.08-3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 28 22:11:33 2018
  InstallationDate: Installed on 2017-06-15 (258 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: openconnect
  UpgradeStatus: Upgraded to bionic on 2018-02-22 (6 days ago)

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

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


[Touch-packages] [Bug 1769682] Re: NFS-based remote root hangs when running 'netplan apply'

2018-05-08 Thread Brian Murray
Hello Mathieu, or anyone else affected,

Accepted nplan into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/nplan/0.32~16.04.5 in
a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: nplan (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed-xenial

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

Title:
  NFS-based remote root hangs when running 'netplan apply'

Status in initramfs-tools package in Ubuntu:
  New
Status in netplan.io package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  Invalid
Status in initramfs-tools source package in Xenial:
  New
Status in netplan.io source package in Xenial:
  Invalid
Status in nplan source package in Xenial:
  Fix Committed
Status in initramfs-tools source package in Artful:
  New
Status in netplan.io source package in Artful:
  Invalid
Status in nplan source package in Artful:
  Fix Committed
Status in initramfs-tools source package in Bionic:
  New
Status in netplan.io source package in Bionic:
  Fix Committed
Status in nplan source package in Bionic:
  Invalid

Bug description:
  [Impact]
  Netboot users with a remote filesystem over NFS (possibly over other 
networked filesystems).

  [Test cases]
  1) Boot a system with its root filesystem over NFS.
  2) Run 'sudo netplan apply'
  3) Validate that the system remains responsive and keeps connectivity over 
the same IP address  as it had.

  [Regression potential]
  This SRU changes network properties, and enforces that networkd does not 
release and re-request an IP address from DHCP when it is restarted. 
Environments relying on the IP release/renew behavior may find themselves 
staying on the previous IP address, which might negatively impact connectivity. 
Changes in connectivity on a system running netplan should be investigated as a 
potential regression from this SRU. Other regression possibilities would 
include failure to get a new IP address over time (usually seen as losing 
connectivity) or possible IP conflicts on a network.

  ---

  With a system booted on the network, with its remote root fs on NFS:

  Running 'netplan apply' restarts systemd-networkd, which releases the
  IP received from DHCP. With no IP (and and IP potentially changing),
  the NFS server can't be reached so the system hangs.

  'netplan apply' or restarting systemd-networkd should not affect teh
  system, it should continue working normally despite "changing" network
  states, as long as the effective IP remains the same.

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

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


[Touch-packages] [Bug 1769812] Re: "installed ca-certificates package post-installation script subprocess returned error exit status 1"

2018-05-08 Thread Seth Arnold
*** This bug is a duplicate of bug 1767864 ***
https://bugs.launchpad.net/bugs/1767864

** This bug has been marked a duplicate of bug 1767864
   package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 1

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

Title:
  "installed ca-certificates package post-installation script subprocess
  returned error exit status 1"

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  happened during upgrade to Ubuntu 18.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ca-certificates 20180409
  ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  NonfreeKernelModules: r8168
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  8 06:55:36 2018
  InstallationDate: Installed on 2016-01-24 (834 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: ca-certificates
  UpgradeStatus: Upgraded to bionic on 2018-05-08 (0 days ago)

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

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


[Touch-packages] [Bug 1769920] Re: [SRU] Enable support for Rocky Cloud Archive

2018-05-08 Thread Launchpad Bug Tracker
This bug was fixed in the package software-properties - 0.96.24.33

---
software-properties (0.96.24.33) cosmic; urgency=medium

  * cloudarchive: Enable support for the Rocky Ubuntu Cloud Archive on
18.04 (LP: #1769920).

 -- Corey Bryant   Tue, 08 May 2018 10:58:48
-0400

** Changed in: software-properties (Ubuntu Cosmic)
   Status: Triaged => Fix Released

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

Title:
  [SRU] Enable support for Rocky Cloud Archive

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Bionic:
  Triaged
Status in software-properties source package in Cosmic:
  Fix Released

Bug description:
  Please add support for:

 cloud-archive:rocky
 cloud-archive:rocky-proposed

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

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

  [Test case]
  sudo add-apt-repository cloud-archive:rocky
  sudo add-apt-repository cloud-archive:rocky-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/1769920/+subscriptions

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


[Touch-packages] [Bug 1753333] Re: Using "Software and Updates -> Additional Drivers" to Switch Fails

2018-05-08 Thread Launchpad Bug Tracker
This bug was fixed in the package software-properties - 0.96.24.33

---
software-properties (0.96.24.33) cosmic; urgency=medium

  * cloudarchive: Enable support for the Rocky Ubuntu Cloud Archive on
18.04 (LP: #1769920).

 -- Corey Bryant   Tue, 08 May 2018 10:58:48
-0400

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

Title:
  Using "Software and Updates -> Additional Drivers" to Switch Fails

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Bionic:
  Fix Committed

Bug description:
  SRU Request:

  [Impact]
  Currently, the Additional Drivers tool uninstalls only the driver package 
that ships the modaliases. When it comes to the NVIDIA drivers (>=390), that 
package is only a meta-package. Removing the meta-package will not uninstall 
the driver.

  We should make sure to uninstall all its nvidia related dependencies,
  not only the meta-package.

  [Test Case]
  1) Open the "Software & Updates" app, and select the "Additional Drivers" tab

  2) Uninstall the NVIDIA 390 driver

  3) Check that, for example, the nvidia-dkms-390 package was
  uninstalled:

  apt-cache policy nvidia-dkms-390

  The package will be reported as installed, because the current code
  didn't remove it.

  [Regression Potential]
  Relatively low, as the change in behaviour only affects the nvidia driver, 
and it only causes the Additional Drivers tool to remove dependencies of the 
meta-package that have the "nvidia" string in their name.

  __
  When you are in the initial install state, you can easily switch from the 
Nouvea drivers to the Nvidia drivers by choosing the option in "Software and 
Updates -> Additional Drivers".  However, when you attempt to switch back (by 
selecting the nouveau option and clicking Apply), and subsequently reboot, your 
system will still come up using the Nvidia drivers, and you will WTF.

  And then, if you visit Additional Drivers, you will be presented with
  grayed out options for both nvidia and nouvea, and the only selectable
  option will be "continue using manually installed driver".

  The reason for this is that the tool, when reselecting nvidia in the
  GUI, uninstalls the nvidia-drivers-390 package, but because it's a
  metapackage (or at least I presume this is the reason), it doesn't
  uninstall its dependencies, which causes the Additional Drivers tool
  to believe it's in a non-automanaged state, and the nvidia drivers
  never actually get uninstalled.

  You can fix it by doing an apt autoremove and rerunning the Additional
  Drivers tool.  But obviously there is no real way for inexperienced
  users to know this.

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

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


[Touch-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

2018-05-08 Thread Tom
This all might be related to https://bugs.launchpad.net/ubuntu/+source
/nvidia-prime/+bug/1765363  I think...

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

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

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


[Touch-packages] [Bug 1736618] Re: debconf: Switch GNOME frontend to gtk3

2018-05-08 Thread Launchpad Bug Tracker
** Branch linked: lp:~baltix-members/baltix-default-settings/ubuntu-
defaults-baltix

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

Title:
  debconf: Switch GNOME frontend to gtk3

Status in Default settings and artwork for Baltix OS:
  Fix Committed
Status in Debconf:
  Fix Released
Status in debconf package in Ubuntu:
  Fix Released

Bug description:
  Please switch debconf's GNOME backend to gtk3.

  debconf's GNOME backend is one of the last 3 things to pull gtk2 in to
  a default Ubuntu 18.04 install (without extra input methods). The
  other two are Firefox and Thunderbird which have fixes in progress.

To manage notifications about this bug go to:
https://bugs.launchpad.net/baltix-default-settings/+bug/1736618/+subscriptions

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


[Touch-packages] [Bug 1736618] Re: debconf: Switch GNOME frontend to gtk3

2018-05-08 Thread Mantas Kriaučiūnas
** Changed in: baltix-default-settings
   Status: In Progress => Fix Committed

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

Title:
  debconf: Switch GNOME frontend to gtk3

Status in Default settings and artwork for Baltix OS:
  Fix Committed
Status in Debconf:
  Fix Released
Status in debconf package in Ubuntu:
  Fix Released

Bug description:
  Please switch debconf's GNOME backend to gtk3.

  debconf's GNOME backend is one of the last 3 things to pull gtk2 in to
  a default Ubuntu 18.04 install (without extra input methods). The
  other two are Firefox and Thunderbird which have fixes in progress.

To manage notifications about this bug go to:
https://bugs.launchpad.net/baltix-default-settings/+bug/1736618/+subscriptions

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


[Touch-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

2018-05-08 Thread Symin
In my case it was... complicated.

Turns out that after upgrade to 18.04 wayland was on by default for me.
prime-select intel worked fine
prime-select nvidia gdm would not show

Changing wayland to xorg in gdm (with intel) would not work - login
screen just kept reapearing. Forcing xorg through /etc/gdm3/custom.conf
only made it worse.

In the end I have decided to try and unplug my DP cable from the
mainboard and plug it into the gfx card. This has worked. After the
reboot GDM has showed up and only xorg was available (I have switched to
xorg before I swapped the cable, though).

No reverse prime for me :( Hopefuly plymouth works with nvidia these
days or this gets fixed soon.

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

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

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


[Touch-packages] [Bug 1750780] Re: Race with local file systems can make open-vm-tools fail to start

2018-05-08 Thread Chris Halse Rogers
Hello ChristianEhrhardt, or anyone else affected,

Accepted open-vm-tools into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/open-vm-
tools/2:10.2.0-3~ubuntu0.16.04.1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: open-vm-tools (Ubuntu Xenial)
   Status: Triaged => Fix Committed

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

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

Title:
  Race with local file systems can make open-vm-tools fail to start

Status in cloud-init:
  Invalid
Status in open-vm-tools package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in open-vm-tools source package in Xenial:
  Fix Committed
Status in systemd source package in Xenial:
  New
Status in open-vm-tools source package in Artful:
  Triaged
Status in open-vm-tools package in Debian:
  Fix Released

Bug description:
  Since the change in [1] open-vm-tools-service starts very (very) early.
  Not so much due to the 
  Before=cloud-init-local.service
  But much more by
  DefaultDependencies=no

  That can trigger an issue that looks like
  root@ubuntuguest:~# systemctl status -l open-vm-tools.service
  ● open-vm-tools.service - Service for virtual machines hosted on VMware
 Loaded: loaded (/lib/systemd/system/open-vm-tools.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: resources)

  
  As it is right now open-vm-tools can race with the other early start and then 
fail.
  In detail one can find a message like:
open-vm-tools.service: Failed to run 'start' task: Read-only file system"

  This is due to privtaeTmp=yes which is also set needing a writable
  /var/tmp [2]

  To ensure this works PrivateTmp would have to be removed (not good) or some 
after dependencies added that make this work reliably.
  I added
  After=local-fs.target
  which made it work for me in 3/3 tests.

  I' like to have an ack by the cloud-init Team that this does not totally kill 
the originally intended Before=cloud-init-local.service
  I think it does not as local-fs can complete before cloud-init-local, then 
open-vm-tools can initialize and finally cloud-init-local can pick up the data.

  To summarize:
  # cloud-init-local #
  DefaultDependencies=no
  Wants=network-pre.target
  After=systemd-remount-fs.service
  Before=NetworkManager.service
  Before=network-pre.target
  Before=shutdown.target
  Before=sysinit.target
  Conflicts=shutdown.target
  RequiresMountsFor=/var/lib/cloud

  # open-vm-tools #
  DefaultDependencies=no
  Before=cloud-init-local.service

  Proposed is to add to the latter:
  After=local-fs.target

  [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859677
  [2]: https://github.com/systemd/systemd/issues/5610

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

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


[Touch-packages] [Bug 1750780] Re: Race with local file systems can make open-vm-tools fail to start

2018-05-08 Thread Chris Halse Rogers
Hello ChristianEhrhardt, or anyone else affected,

Accepted open-vm-tools into artful-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/open-vm-
tools/2:10.2.0-3~ubuntu0.17.10.1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-artful to verification-done-artful. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-artful. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: open-vm-tools (Ubuntu Artful)
   Status: Triaged => Fix Committed

** Tags added: verification-needed-artful

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

Title:
  Race with local file systems can make open-vm-tools fail to start

Status in cloud-init:
  Invalid
Status in open-vm-tools package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in open-vm-tools source package in Xenial:
  Fix Committed
Status in systemd source package in Xenial:
  New
Status in open-vm-tools source package in Artful:
  Fix Committed
Status in open-vm-tools package in Debian:
  Fix Released

Bug description:
  Since the change in [1] open-vm-tools-service starts very (very) early.
  Not so much due to the 
  Before=cloud-init-local.service
  But much more by
  DefaultDependencies=no

  That can trigger an issue that looks like
  root@ubuntuguest:~# systemctl status -l open-vm-tools.service
  ● open-vm-tools.service - Service for virtual machines hosted on VMware
 Loaded: loaded (/lib/systemd/system/open-vm-tools.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: resources)

  
  As it is right now open-vm-tools can race with the other early start and then 
fail.
  In detail one can find a message like:
open-vm-tools.service: Failed to run 'start' task: Read-only file system"

  This is due to privtaeTmp=yes which is also set needing a writable
  /var/tmp [2]

  To ensure this works PrivateTmp would have to be removed (not good) or some 
after dependencies added that make this work reliably.
  I added
  After=local-fs.target
  which made it work for me in 3/3 tests.

  I' like to have an ack by the cloud-init Team that this does not totally kill 
the originally intended Before=cloud-init-local.service
  I think it does not as local-fs can complete before cloud-init-local, then 
open-vm-tools can initialize and finally cloud-init-local can pick up the data.

  To summarize:
  # cloud-init-local #
  DefaultDependencies=no
  Wants=network-pre.target
  After=systemd-remount-fs.service
  Before=NetworkManager.service
  Before=network-pre.target
  Before=shutdown.target
  Before=sysinit.target
  Conflicts=shutdown.target
  RequiresMountsFor=/var/lib/cloud

  # open-vm-tools #
  DefaultDependencies=no
  Before=cloud-init-local.service

  Proposed is to add to the latter:
  After=local-fs.target

  [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859677
  [2]: https://github.com/systemd/systemd/issues/5610

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

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


[Touch-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

2018-05-08 Thread Kyle Weber
I hear Pop!_OS 18.04 doesn't have this issue. I'm unfortunately about to
give up on Ubuntu and give that a try. Some word of reassurance from the
Ubuntu team here would be nice. Where they marked this as fixed, I'm not
hopeful of a fix--at least anytime soon. If anyone has found a true and
simple workaround, please let us know! Otherwise, I think my hardware
will require me to look somewhere else...

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

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

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


[Touch-packages] [Bug 1768830] Re: the audio can't work on Lenovo machines with dual analogue codecs under ubuntu 18.04

2018-05-08 Thread Launchpad Bug Tracker
This bug was fixed in the package alsa-lib - 1.1.6-1ubuntu1

---
alsa-lib (1.1.6-1ubuntu1) cosmic; urgency=medium

  * 
debian/patches/0008-ucm-adding-the-folder-of-card_long_name-when-finding.patch
  * debian/patches/0009-conf-ucm-increase-the-input-volume-for-LineIn.patch
 - Backport 2 patches to make audio work on Lenovo machines with dual 
codecs.
   (LP: #1768830)

 -- Hui Wang   Tue, 08 May 2018 03:28:26 +

** Changed in: alsa-lib (Ubuntu)
   Status: New => Fix Released

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

Title:
  the audio can't work on Lenovo machines with dual analogue codecs
  under ubuntu 18.04

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Bionic:
  New

Bug description:
  Steps:
  1. Install the ubuntu 18.04 on the machine of Lenovo P520.
  2. Login system.
  3. Plug in an external headset to record and playback in front and rear panel.

  Expected result:
  Output and input audio should work in front and rear panel.

  Actual result:
  Front panel audio doesn't work at all.
  Just output audio working, input audio does't work in rear panel.

  SRU Document:

  [Impact]

  We have several Lenovo machines like Lenovo P520 which have 2 analogue
  audio codecs on them, the internal speaker and front headset are
  connected to the 1st codec, the Rear mic, Line in and Line out are
  connected to the 2nd codec. So far, under ubuntu 18.04 with the alsa-
  lib/libasound2 v1.1.3-5, only the audio devices (internal speaker and
  front headset) on the 1st codec can work. To make all audio devices
  work on this machine, upstream provided 3 patches for kernel audio
  driver and 5 patches for alsa-lib. The kernel patches are already in
  the linux-4.12, so this is not a problem anymore under 18.04 since we
  use linux-4.15 in 18.04. For the 5 patches of alsa-lib, we need to
  backport them to v1.1.3-5, the 5 patches are list as below:

  2b9b3f01 ucm: Assure the user input card name not to exceed max size of card 
long name (it is in the alsa-lib v1.1.4)
  4b9297e6 ucm: Load device-specific configuration file based on the card long 
name (it is in the alsa-lib v1.1.4)
  b7e56af8 conf/ucm: Add dual HD-audio codecs config for Lenovo (it is in the 
alsa-lib v1.1.6)
  181f8e25 ucm: adding the folder of card_long_name when finding verb conf file 
(it is in the alsa-lib v1.1.6+)
  81db276f conf/ucm: increase the input volume for LineIn (it is in the 
alsa-lib v1.1.6+)

  Some explanation for these 5 patches, to make the audio work, the
  alsa-lib needs to add an audio configuration file and verb conf file
  for lenovo machines with dual codecs, these two files are put in a
  folder named by card_long_name, and the name of configuration file
  itself is also named by card_long_name, this is implemented by the
  patches of NO. 3rd and 5th.

  But the alsa-lib v1.1.3-5 itself doesn't support to search conf file with 
card_long_name, it only support searching with card_name, So we need to 
backport 3 patches to let alsa-lib v1.1.3-5 support to search with 
card_long_name, these 3 patches are No. 1st, 2nd and 4th.
   
  [Test Case]

  On the Lenovo machines with dual codecs (p520), I insatlled the
  libasound2 v1.1.3-5ubuntu1 and libasound2-data v1.1.3-5ubuntu1, the
  alsa-lib can find the conf file and can parse the conf file
  successfully, and I tested the internal speaker, front headset, rear
  mic, line out and line in, all audio devices work well.

  On a HP and Dell machines without dual codecs, I insatlled the
  libasound2 v1.1.3-5ubuntu1 and libasound2-data v1.1.3-5ubuntu1, the
  alsa-lib can't find conf file by card_long_name and card_name, the
  pulseaudio will drive the sound card as before, so all audio functions
  worked well as before.

  [Regression Potential]

  After adding these 5 patches, there 2 two changes introduced into the
  alsa-lib v1.1.3-5ubuntu1:

  1) before: only have folder and conf files named by card_name; after: has one 
folder and conf file named by card_long_name, this folder and conf file will 
not affect others,
  2) before: the ucm parser will search the conf file/folder by card_name only; 
 after: the ucm parser will search the conf file/foler by card_long_name first, 
if it fails, it will fallback to use card_name to search again. So this change 
is compatible with old version.

  There is no regression since there is only one folder named by
  card_long_name in v1.1.3-5ubuntu1, if it runs on lenovo machine with
  dual codecs, it will find the conf file by card_long_name, if it runs
  on other machines, the search by card_long_name will definitely fail
  and fall back to search by card_name, then it will be same as before.
  So the objective of these 5 patches is to let lenovo machines with
  dual codecs find the conf file by card_long_

[Touch-packages] [Bug 1770052] [NEW] display crashes

2018-05-08 Thread shyju
Public bug reported:

i am using ASROCK N68C-GS FX mother board and AMD SEMPRON LE1250 processor with 
1GB RAM,500GB HDD,
UBUNTU 14.04 INSTALLED WITHOUT ANY WARNING MESSAGES.but now the display crashes

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 4.4.0-22.40~14.04.1-generic 4.4.8
Uname: Linux 4.4.0-22-generic i686
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Wed May  9 07:14:59 2018
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus: bcmwl, 6.30.223.248+bdcom, 4.4.0-22-generic, i686: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) 
(prog-if 00 [VGA controller])
   Subsystem: ASRock Incorporation Device [1849:03d6]
InstallationDate: Installed on 2018-05-08 (0 days ago)
InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 (20160217.1)
Lsusb:
 Bus 001 Device 002: ID 148f:7601 Ralink Technology, Corp. MT7601U Wireless 
Adapter
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=efc9f66a-4d8f-412d-b243-becd83011893 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/18/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.00
dmi.board.name: N68C-GS FX
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.00:bd01/18/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68C-GSFX: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.
version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Wed May  9 12:23:14 2018
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputAT Translated Set 2 keyboard KEYBOARD, id 8
 inputImExPS/2 Logitech Explorer Mouse MOUSE, id 9
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs: Output   VGA-1
xserver.version: 2:1.17.2-1ubuntu9.1~trusty1
xserver.video_driver: nouveau

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


** Tags: apport-bug i386 trusty ubuntu

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

Title:
  display crashes

Status in xorg package in Ubuntu:
  New

Bug description:
  i am using ASROCK N68C-GS FX mother board and AMD SEMPRON LE1250 processor 
with 1GB RAM,500GB HDD,
  UBUNTU 14.04 INSTALLED WITHOUT ANY WARNING MESSAGES.but now the display 
crashes

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-22.40~14.04.1-generic 4.4.8
  Uname: Linux 4.4.0-22-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed May  9 07:14:59 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.248+bdcom, 4.4.0-22-generic, i686: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) 
(prog-if 00 [VGA controller])
 Subsystem: ASRock Incorporation Device [1849:03d6]
  InstallationDate: Installed on 2018-05-08 (0 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 
(20160217.1)
  Lsusb:
   Bus 001 Device 

[Touch-packages] [Bug 1769075] Re: [regression][bionic] Bluetooth keyboard battery reports 0%

2018-05-08 Thread Daniel van Vugt
Please try some different kernels, old and new:

http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D

and tell us which ones work and which don't.

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

Title:
  [regression][bionic] Bluetooth keyboard battery reports 0%

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d"
  reports always 0% as battery percentage of the bluetooth Logitech K810 
keyboard.
  Which is a bit annoying since I get a KDE warning on the battery.

  Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery
native-path:  hid-34:88:5d:5e:0c:2f-battery
model:Logitech K810
power supply: no
updated:  Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago)
has history:  yes
has statistics:   yes
keyboard
  present: yes
  rechargeable:yes
  state:   unknown
  warning-level:   none
  percentage:  0%
  icon-name:  'battery-missing-symbolic'

  My guess is that the issue is in the bluetooth rather in the upowerd
  since the reporting in the /sys/devices shows battery level of 0
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bnv1714 F pulseaudio
   /dev/snd/pcmC0D0p:   bnv1714 F...m pulseaudio
   /dev/snd/controlC0:  bnv1714 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf
  InstallationDate: Installed on 2017-11-02 (185 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  IwConfig:
   lono wireless extensions.
   
   enp0s25   no wireless extensions.
  MachineType: Dell Inc. Precision Tower 5810
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago)
  UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0K240Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision Tower 5810
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1759300] Re: Gnome Shell: Touchpad right click (bottom right) area does not work

2018-05-08 Thread Daniel van Vugt
Javier,

If your physical buttons (the ones that move independently of the
touchpad, and not just painted on) are not behaving correctly then
please log a bug with:

  ubuntu-bug libinput10

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

Title:
  Gnome Shell: Touchpad right click (bottom right) area does not work

Status in gsettings-desktop-schemas package in Ubuntu:
  Invalid

Bug description:
  The right (second) touchpad click does not work.
  It ceased to work about three months ago.
  ubuntu 18,04 aser ex2519

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1759300/+subscriptions

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


  1   2   >