[Touch-packages] [Bug 1686361] Re: systemd does not respect nofile ulimit when running in container

2017-04-26 Thread Dimitri John Ledkov 
** Changed in: systemd (Ubuntu)
Milestone: None => ubuntu-17.05

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

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

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

Title:
  systemd does not respect nofile ulimit when running in container

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  When systemd currently starts in a container that has RLIMIT_NOFILE set to 
e.g.
  10 systemd will lower it to 65536 since this value is hard-coded into 
systemd.
  I've pushed a patch to systemd upstream that will try to set
  the nofile limit to the allowed kernel maximum. If this fails, it will compute
  the minimum of the current set value (the limit that is set on the container)
  and the maximum value as soft limit and the currently set maximum value as the
  maximum value. This way it retains the limit set on the container.
  It would be great if we could backport this patch to have system adhere to
  nofile limits set for the container. This is especially important since user
  namespaces will allow you to lower the limit but not raise it back up 
afterwards.
  The upstream patch is appended.

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

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

[Touch-packages] [Bug 1685900] Re: On artful, no working dns after upgrading to systemd 233-5ubuntu1

2017-04-26 Thread Harry 
Dimitri,

Just added a sosreport as you requested.

My setup is a nearly minimal setup, containing only the applications I
need.

The issue here is what packages are needed to get the new systemd 233-5ubuntu1 
and its resolved working.
And more, exactly those packages that were not needed to get systemd 
232-21ubuntu3 resolved working, because that was OK in my setup.

I hope this helps a bit.

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

Title:
  On artful, no working dns after upgrading to systemd 233-5ubuntu1

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to the newest systemd 233-5ubuntu1 (in artful proposed) I got 
no network.
  This is very likely a DNS issue.
  As a workaround downgrading back to systemd 232-21ubuntu3 the network and DNS 
work fine.

  So something odd has happened between these versions.

  My setup is a fully upgraded artful with proposed repo turned on.
  I use only Gnome DE with GDM.
  Everything else works fine, but not systemd 233-5ubuntu1.

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

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

[Touch-packages] [Bug 1685900] Re: On artful, no working dns after upgrading to systemd 233-5ubuntu1

2017-04-26 Thread Harry 
Sosreport of my setup.

** Attachment added: "Sosreport"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1685900/+attachment/4868196/+files/sosreport-HarryKaasinen.systemd-20170426130934.tar.xz

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

Title:
  On artful, no working dns after upgrading to systemd 233-5ubuntu1

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to the newest systemd 233-5ubuntu1 (in artful proposed) I got 
no network.
  This is very likely a DNS issue.
  As a workaround downgrading back to systemd 232-21ubuntu3 the network and DNS 
work fine.

  So something odd has happened between these versions.

  My setup is a fully upgraded artful with proposed repo turned on.
  I use only Gnome DE with GDM.
  Everything else works fine, but not systemd 233-5ubuntu1.

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

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

[Touch-packages] [Bug 1686361] [NEW] systemd does not respect nofile ulimit when running in container

2017-04-26 Thread Christian Brauner 
Public bug reported:

When systemd currently starts in a container that has RLIMIT_NOFILE set to e.g.
10 systemd will lower it to 65536 since this value is hard-coded into 
systemd.
I've pushed a patch to systemd upstream that will try to set
the nofile limit to the allowed kernel maximum. If this fails, it will compute
the minimum of the current set value (the limit that is set on the container)
and the maximum value as soft limit and the currently set maximum value as the
maximum value. This way it retains the limit set on the container.
It would be great if we could backport this patch to have system adhere to
nofile limits set for the container. This is especially important since user
namespaces will allow you to lower the limit but not raise it back up 
afterwards.
The upstream patch is appended.

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

** Patch added: "0001-main-improve-RLIMIT_NOFILE-handling-5795.patch"
   
https://bugs.launchpad.net/bugs/1686361/+attachment/4868175/+files/0001-main-improve-RLIMIT_NOFILE-handling-5795.patch

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

Title:
  systemd does not respect nofile ulimit when running in container

Status in systemd package in Ubuntu:
  New

Bug description:
  When systemd currently starts in a container that has RLIMIT_NOFILE set to 
e.g.
  10 systemd will lower it to 65536 since this value is hard-coded into 
systemd.
  I've pushed a patch to systemd upstream that will try to set
  the nofile limit to the allowed kernel maximum. If this fails, it will compute
  the minimum of the current set value (the limit that is set on the container)
  and the maximum value as soft limit and the currently set maximum value as the
  maximum value. This way it retains the limit set on the container.
  It would be great if we could backport this patch to have system adhere to
  nofile limits set for the container. This is especially important since user
  namespaces will allow you to lower the limit but not raise it back up 
afterwards.
  The upstream patch is appended.

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

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

[Touch-packages] [Bug 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable

2017-04-26 Thread iGadget 
What's up with all the spamming on Launchpad lately? Please, ban these accounts.
Unsubscribing to all notificiatons on this bug (also since despite it's 
affecting over 650 people and has a heat value of over 4000, it's not even 
assigned to anyone...).

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

Title:
  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

Status in Ambasa:
  New
Status in Debconf:
  New
Status in aptdaemon package in Ubuntu:
  Triaged
Status in debconf package in Ubuntu:
  Triaged

Bug description:
  Upgrading packages that use debconf sometimes fail with the following
  error:

  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

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

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

[Touch-packages] [Bug 1649310] Re: RM Upstart, obsolete, superseded by systemd

2017-04-26 Thread Khurshid Alam 
It can be removed as systemd-sysv doesn't depend on upstart anymore.

Also I noticed lsb-base. Why is it still using upstart scripts?

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

Title:
  RM Upstart, obsolete, superseded by systemd

Status in cgmanager package in Ubuntu:
  Triaged
Status in lxc-android-config package in Ubuntu:
  Triaged
Status in ubuntu-touch-meta package in Ubuntu:
  Triaged
Status in ubuntu-touch-session package in Ubuntu:
  Triaged
Status in unity8-desktop-session package in Ubuntu:
  Triaged
Status in upstart package in Ubuntu:
  Triaged
Status in upstart-watchdog package in Ubuntu:
  Triaged

Bug description:
  In 18.04 LTS src:upstart should not be part of Ubuntu.
  It has already been removed from Debian.
  And most products have migrated to systemd.
  This is a tracking bug to remove a collection of packages that need to go 
away together with upstart.

  Some of these have been ported to systemd under different names, or no
  longer at all required.

  = Removal order =

  * ubuntu-touch-meta
  * unity8-desktop-session

  * ubuntu-touch-session
  * upstart-watchdog
  * lxc-android-config

  * upstart

  * cgmanager

  = Reverse depends checks =

  $ reverse-depends -b src:upstart
  Reverse-Build-Depends
  =
  * tarantool (for upstart)
    ./debian/control: dh-systemd (>= 1.22) | sysvinit (<< 2.88dsf-59) | upstart 
(<< 1.13),
  * unity (for libupstart-dev)
    https://code.launchpad.net/~xnox/unity/no-more-upstart-dep/+merge/322283
    https://bileto.ubuntu.com/#/ticket/2730

  $ reverse-depends src:upstart
  Reverse-Depends
  ===
  * ubuntu-touch-session  (for upstart)
  * unity8-desktop-session(for upstart)
  * upstart-watchdog  (for upstart)

  $ reverse-depends src:ubuntu-touch-session
  Reverse-Depends
  ===
  * ubuntu-touch  (for ubuntu-touch-session)
  $ reverse-depends -b src:ubuntu-touch-session
  No reverse dependencies found

  $ reverse-depends upstart-watchdog
  Reverse-Depends
  ===
  * ubuntu-touch
  $ reverse-depends -b src:upstart-watchdog
  No reverse dependencies found

  $ reverse-depends src:ubuntu-touch-meta
  No reverse dependencies found
  $ reverse-depends -b src:ubuntu-touch-meta
  No reverse dependencies found

  $ reverse-depends src:unity8-desktop-session
  No reverse dependencies found
  $ reverse-depends -b src:unity8-desktop-session
  No reverse dependencies found

  $ reverse-depends src:cgmanager
  Reverse-Depends
  ===
  * lxc-android-config(for cgmanager)
  * numad (for cgmanager)
    ./debian/control:Depends: systemd-sysv | cgmanager
  * upstart [amd64 arm64 armhf i386 ppc64el]  (for libcgmanager0)

  $ reverse-depends -b src:cgmanager
  Reverse-Build-Depends
  =
  * upstart   (for libcgmanager-dev)

  $ reverse-depends src:lxc-android-config
  Reverse-Depends
  ===
  * ubuntu-touch  (for lxc-android-config)

  $ reverse-depends -b src:lxc-android-config
  No reverse dependencies found

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

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

[Touch-packages] [Bug 1100326] Re: Location requested by websites should be able to use GPS/mobile positioning

2017-04-26 Thread Olivier Tilloy 
The default location provider in chromium-browser is network-based, it
doesn’t look like it knows how to talk to GPS hardware.

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

Title:
  Location requested by websites should be able to use GPS/mobile
  positioning

Status in Chromium Browser:
  Fix Committed
Status in Mozilla Firefox:
  Confirmed
Status in GeoClue:
  Won't Fix
Status in WebKit:
  Fix Released
Status in chromium-browser package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New
Status in geoclue-2.0 package in Ubuntu:
  Fix Released
Status in geoclue-providers package in Ubuntu:
  Invalid

Bug description:
  It would be nice if location requested by websites could use location
  found from GPS or GSM/CDMA positioning.

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/1100326/+subscriptions

-- 
Mailing list: https://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 1562308] Re: missing or duplicate lines caused by a wrapped line with wide characters

2017-04-26 Thread Mitsuya Shibata 
Hi Brian and G.M.,

>> until comment #17 is investigated further.
>
> IMHO, comment #17 is other bug and not affect this patch.
>
> Is it can reproduce on 16.04 or 16.10?
>
> If not, could you filed your problem as other bug?

Is there any update?

Thanks,

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

Title:
  missing or duplicate lines caused by a wrapped line with wide
  characters

Status in less package in Ubuntu:
  Fix Released
Status in less source package in Xenial:
  Fix Committed
Status in less source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]

  Currently less doesn't work correctly with UTF-8 encoded Japanese
  characters,  wrapping the lines in an invalid manner, missing or
  duplicating them (see original description below for exact error
  cases). For locale like these it breaks the general workflow, making
  the tool unreliable.

  [Test Case]

  1. Open xterm.
  2. Set the geometory of xterm to 71x22.
  3. Open the attached lesstest.long_jap.txt with less (maybe you need
 environment variable LANG=ja_JP.UTF-8)
  4. Type "j", then you will see "003" at the top and only the first part of 
 the wrapped line should be shown.
  5. Type "k", then you will see "001", "002" and "003" at the top.

  [Regression Potential]

  Rather low as the fix is present in the beta version of less for over
  5 months already, which seems to be enough time for general audience
  testing. But since the width tables are modified potentially this
  could lead to other similar breakages related to wide-character
  handling.

  [Original Description]

  When you scroll down text with "j" key and encounter a wrapped line
  with wide characters (such as UTF8-encoded Japanese characters),
  "less" seems to show the whole wrapped line at a single "j" key,
  causing the view scroll down by 2 lines at once. Strangely, if you
  type "k" to scroll up, it does that by only 1 line. As a result, there
  is a missing line that should have been shown.

  Even stranger stuff (i.e., duplicate lines) happens when you type "j"
  and "k" alternately when a wrapped line with wide characters is at the
  bottom of the view.

  # Steps to reproduce

  1. Open xterm.
  2. Set the geometory of xterm to 71x22.
  3. Open the attached lesstest.long_jap.txt with less (maybe you need
     environment variable LANG=ja_JP.UTF-8)
  4. Type "j", then you will see "003" at the top, and a long wrapped
     line with Japanese characters at the bottom.
  5. Type "k", then you will see "001" and "003" at the top. "002" is
     missing.

  # Expected behavior

  In step 4, only the first part of the wrapped line should be shown.

  In step 5, all "001", "002" and "003" should be shown.

  # Test Environment

  - Xubuntu 16.04 (Xenial) beta (in VirtualBox on Xubuntu 14.04)
  - less: 481-2.1
  - xterm: 322-1ubuntu1
  - Japanese environment (LANG=ja_JP.UTF-8)

  # Note

  - The same problem happens on xfce4-terminal (0.6.3-2ubuntu1)
  - lv (4.51-2.3build1) doesn't have such problem.
  - In "less" in Xubuntu 14.04 (version 458-2), this problem didn't
    exist.

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

-- 
Mailing list: https://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 1685900] Re: On artful, no working dns after upgrading to systemd 233-5ubuntu1

2017-04-26 Thread Dimitri John Ledkov 
On 26 April 2017 at 09:11, Harry <1685...@bugs.launchpad.net> wrote:
> Dimitri,
>
> My setup does not need the package bind9.
> But I need to start systemd-resolved service manually.
>
> So, what do I have to do to get this working automatically at the boot?
>

Artful is not ready for general usage. And -proposed packages in
artful are not ready for general consumption at all and are meant for
automatic testing only. Especially if one doesn't know how to check
the logs of individual services and fix their own systems.

I guess the easiest would be to collect a full sosreport.

Install package called sosreport and run `sudo sosreport` to collect
extensive information about your system. The tarball produced will be
large, please upload it.

Unfortunately, the questions you are asking are more suitable as
support questions on how to use journalctl / systemctl - please check
https://www.ubuntu.com/support/community-support or
https://www.ubuntu.com/support

-- 
Regards,

Dimitri.

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

Title:
  On artful, no working dns after upgrading to systemd 233-5ubuntu1

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to the newest systemd 233-5ubuntu1 (in artful proposed) I got 
no network.
  This is very likely a DNS issue.
  As a workaround downgrading back to systemd 232-21ubuntu3 the network and DNS 
work fine.

  So something odd has happened between these versions.

  My setup is a fully upgraded artful with proposed repo turned on.
  I use only Gnome DE with GDM.
  Everything else works fine, but not systemd 233-5ubuntu1.

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

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

[Touch-packages] [Bug 1667113] Re: System users appears in Ligthdm and user switcher (Accountsservice has no filter for shell types)

2017-04-26 Thread ChristianEhrhardt 
Hi Ali,
as I outlined before the fix likely has to take place in accountsservice not in 
libvirt.
You assigned yourself, so I wanted to ask what you have in mind to do?

In case this was an accident you might want to unassign yourself, but
"subscribe" [1] you to the bug to stay up to date on this - you find the
box to do so to the right of the bug launchpad page.

[1]: https://help.launchpad.net/Bugs/Subscriptions

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

Title:
  System users appears in Ligthdm and user switcher (Accountsservice has
  no filter for shell types)

Status in accountsservice package in Ubuntu:
  Confirmed
Status in base-passwd package in Ubuntu:
  Invalid
Status in ceph package in Ubuntu:
  Confirmed
Status in ifmail package in Ubuntu:
  Confirmed
Status in libvirt package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed
Status in netqmail package in Ubuntu:
  Confirmed

Bug description:
  "Technical" user libvirt Qemu appears in the list of user in Ligthdm,
  among the real regular users. It probably shouldn't

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: libvirt-bin 2.5.0-3ubuntu2
  ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
  Uname: Linux 4.9.0-15-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Wed Feb 22 22:09:24 2017
  InstallationDate: Installed on 2017-02-01 (21 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170201)
  KernLog:
   
  SourcePackage: libvirt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1685271] Re: gnome-shell: corners are not rounded

2017-04-26 Thread Daniel van Vugt 
Yes, what Amr said...

$ dpkg -s light-themes | grep Source
Source: ubuntu-themes

** Changed in: light-themes (Ubuntu Artful)
   Status: Confirmed => Invalid

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

Title:
  gnome-shell: corners are not rounded

Status in light-themes package in Ubuntu:
  Invalid
Status in ubuntu-themes package in Ubuntu:
  Confirmed
Status in light-themes source package in Artful:
  Invalid
Status in ubuntu-themes source package in Artful:
  Confirmed

Bug description:
  Under gnome-shell apps have dark black squared top corners when they
  should be rounded.  See attached screenshot.

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

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

[Touch-packages] [Bug 1667113] Re: System users appears in Ligthdm and user switcher (Accountsservice has no filter for shell types)

2017-04-26 Thread ali salama 
** Changed in: libvirt (Ubuntu)
 Assignee: (unassigned) => ali salama (alisalama)

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

Title:
  System users appears in Ligthdm and user switcher (Accountsservice has
  no filter for shell types)

Status in accountsservice package in Ubuntu:
  Confirmed
Status in base-passwd package in Ubuntu:
  Invalid
Status in ceph package in Ubuntu:
  Confirmed
Status in ifmail package in Ubuntu:
  Confirmed
Status in libvirt package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed
Status in netqmail package in Ubuntu:
  Confirmed

Bug description:
  "Technical" user libvirt Qemu appears in the list of user in Ligthdm,
  among the real regular users. It probably shouldn't

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: libvirt-bin 2.5.0-3ubuntu2
  ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
  Uname: Linux 4.9.0-15-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Wed Feb 22 22:09:24 2017
  InstallationDate: Installed on 2017-02-01 (21 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170201)
  KernLog:
   
  SourcePackage: libvirt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1686344] [NEW] Mesa 17.0.x stable release

2017-04-26 Thread Timo Aaltonen 
Public bug reported:

[Impact]

Mesa stable release for zesty & backport to xenial.

[Test case]

Install, run desktop session, test xonotic.

the important hw drivers to test:
- i965 (Intel)
- radeonsi (AMD)

[Regression potential]

Spec compliance test suites are already run by Intel and others, so
feature regressions should not be possible. GLESv1 support has been
dropped from the packaging though, but packages that depend on
libgles1-mesa have been pushed to proposed to drop the dependency, see
bug 1676845 (applies to xenial).

[Other info]

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

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

Title:
  Mesa 17.0.x stable release

Status in mesa package in Ubuntu:
  New

Bug description:
  [Impact]

  Mesa stable release for zesty & backport to xenial.

  [Test case]

  Install, run desktop session, test xonotic.

  the important hw drivers to test:
  - i965 (Intel)
  - radeonsi (AMD)

  [Regression potential]

  Spec compliance test suites are already run by Intel and others, so
  feature regressions should not be possible. GLESv1 support has been
  dropped from the packaging though, but packages that depend on
  libgles1-mesa have been pushed to proposed to drop the dependency, see
  bug 1676845 (applies to xenial).

  [Other info]

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

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

[Touch-packages] [Bug 1686189] Re: External monitor connecting problem

2017-04-26 Thread Giacomo Orlandi 
I have the same problem on 16.04.2 Xenial since upgrading the Kernel to 
4.4.0-75 yesterday.
Booting the the older kernel version 4.4.0-72-generic seems to be a workaround.

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

Title:
  External monitor connecting problem

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I am facing a problem with Intel Graphics driver. I have external
  monitor and in display settings the second monitor is detecting but
  it's not working, so could you email me a solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.4.25-040425-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  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 Apr 25 21:45:16 2017
  DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9]
  InstallationDate: Installed on 2017-04-25 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  MachineType: Dell Inc. Inspiron 3537
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic 
root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago)
  dmi.bios.date: 04/30/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 03JPPR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn03JPPR:rvrA00:cvnDellInc.:ct8:cvrA08:
  dmi.product.name: Inspiron 3537
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Apr 25 21:37:24 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   17900 
   vendor AUO
  xserver.version: 2:1.18.4-0ubuntu0.2

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

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

[Touch-packages] [Bug 1686189] Re: External monitor connecting problem

2017-04-26 Thread Launchpad Bug Tracker 
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  External monitor connecting problem

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I am facing a problem with Intel Graphics driver. I have external
  monitor and in display settings the second monitor is detecting but
  it's not working, so could you email me a solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.4.25-040425-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  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 Apr 25 21:45:16 2017
  DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9]
  InstallationDate: Installed on 2017-04-25 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  MachineType: Dell Inc. Inspiron 3537
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic 
root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago)
  dmi.bios.date: 04/30/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 03JPPR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn03JPPR:rvrA00:cvnDellInc.:ct8:cvrA08:
  dmi.product.name: Inspiron 3537
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Apr 25 21:37:24 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   17900 
   vendor AUO
  xserver.version: 2:1.18.4-0ubuntu0.2

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

-- 
Mailing list: https://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 1682934] Re: package python3 3.5.1-4 failed to install/upgrade: pre-dependency problem - not installing python3

2017-04-26 Thread Brian Kelly 
I too removed the references from /usr/local/lib and also from 
/usr/local/bin and ran the 'sudo apt-get -f install' and it fixed 
everything, including re-installing and configuring Python 3.5.

I suspect I caused the problem by manually installing Python to get 
around the missing library problem I got when trying to run 
'Transmageddon' so it points to a Python installer issue rather than 
Ubuntu per se.

Interestingly if I type 'python' in a Terminal window it says I have 
version 2.7.13 installed, even after the fix and update.  Typing 
'python3' says 3.5.3 is installed with a slightly earlier date than the 
2.7 version.

Brian.

On 26/04/2017 00:31, Brian Murray wrote:
> I tested installing python3 using the instructions at
> https://passingcuriosity.com/2015/installing-python-from-source/ and
> sure enough I received the same Traceback.
> 
> Setting up python3.5-minimal (3.5.3-1) ...
> Traceback (most recent call last):
>File "/usr/lib/python3.5/py_compile.py", line 6, in 
>  import importlib._bootstrap_external
>File "/usr/lib/python3.5/importlib/__init__.py", line 57, in 
>  import types
>File "/usr/lib/python3.5/types.py", line 166, in 
>  import functools as _functools
>File "/usr/lib/python3.5/functools.py", line 23, in 
>  from weakref import WeakKeyDictionary
>File "/usr/lib/python3.5/weakref.py", line 12, in 
>  from _weakref import (
> ImportError: cannot import name '_remove_dead_weakref'
> dpkg: error processing package python3.5-minimal (--configure):
>   subprocess installed post-installation script returned error exit status 1
> dpkg: dependency problems prevent configuration of python3-minimal:
>   python3-minimal depends on python3.5-minimal (>= 3.5.3-1~); however:
>Package python3.5-minimal is not configured yet.
> 
> dpkg: error processing package python3-minimal (--configure):
>   dependency problems - leaving unconfigured
> No apport report written because the error message indicates its a followup 
> error from a previous failure.
>   
>  Errors were encountered while processing:
>   python3.5-minimal
>   python3-minimal
> 
> Once I removed /usr/local/bin/python3.5 I was then able to fix the
> upgrade via 'sudo apt-get -f install'.
>

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

Title:
  package python3 3.5.1-4 failed to install/upgrade: pre-dependency
  problem - not installing python3

Status in python3-defaults package in Ubuntu:
  Confirmed

Bug description:
  Got this error while using "Transmageddon Video Transcoder" and again
  while updating 16.10 to 17.04.

  Seems to have something to do with needing that Python3 version for
  Teletext decoding in media that is in transport stream format (.ts).

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: python3 3.5.1-4
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Fri Apr 14 19:27:33 2017
  ErrorMessage: pre-dependency problem - not installing python3
  InstallationDate: Installed on 2015-05-01 (714 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: python3-defaults
  Title: package python3 3.5.1-4 failed to install/upgrade: pre-dependency 
problem - not installing python3
  UpgradeStatus: Upgraded to zesty on 2017-04-14 (0 days ago)

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

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

[Touch-packages] [Bug 1685900] Re: On artful, no working dns after upgrading to systemd 233-5ubuntu1

2017-04-26 Thread Harry 
Dimitri,

My setup does not need the package bind9.
But I need to start systemd-resolved service manually.

After that the output of systemd-resolve --status is OK:
Global
 DNS Servers: 8.8.8.8
  8.8.4.4
  2001:4860:4860::
  2001:4860:4860::8844
  DNSSEC NTA: 10.in-addr.arpa
  16.172.in-addr.arpa
  168.192.in-addr.arpa
  17.172.in-addr.arpa
  18.172.in-addr.arpa
  19.172.in-addr.arpa
  20.172.in-addr.arpa
  21.172.in-addr.arpa
  22.172.in-addr.arpa
  23.172.in-addr.arpa
  24.172.in-addr.arpa
  25.172.in-addr.arpa
  26.172.in-addr.arpa
  27.172.in-addr.arpa
  28.172.in-addr.arpa
  29.172.in-addr.arpa
  30.172.in-addr.arpa
  31.172.in-addr.arpa
  corp
  d.f.ip6.arpa
  home
  internal
  intranet
  lan
  local
  private
  test

Link 2 (eth0)
  Current Scopes: LLMNR/IPv4 LLMNR/IPv6
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: allow-downgrade
DNSSEC supported: yes


So, what do I have to do to get this working automatically at the boot?

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

Title:
  On artful, no working dns after upgrading to systemd 233-5ubuntu1

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to the newest systemd 233-5ubuntu1 (in artful proposed) I got 
no network.
  This is very likely a DNS issue.
  As a workaround downgrading back to systemd 232-21ubuntu3 the network and DNS 
work fine.

  So something odd has happened between these versions.

  My setup is a fully upgraded artful with proposed repo turned on.
  I use only Gnome DE with GDM.
  Everything else works fine, but not systemd 233-5ubuntu1.

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

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

[Touch-packages] [Bug 1686081] Re: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work

2017-04-26 Thread Timo Aaltonen 
the only one that needs -synaptics is unity

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

Title:
  If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't
  work

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I'm splitting this issue off from LP: #1685542 (which made xserver-
  xorg-input-all no longer recommend xserver-xorg-input-synaptics) for
  tracking the remaining issues.

  gnome-control-center only supports libinput. If xserver-xorg-input-
  synaptics is installed (because it's used by some desktops which
  haven't been ported to libinput yet), synaptics overrides libinput.
  That makes gnome-control-center's Mouse & Touchpad settings panel only
  show basic settings and important configurations don't work.

  Questions
  -
  1. Which desktops/apps still need -synaptics?
  - Unity
  - Xfce?
  - LXDE? LXQt?
  All the other major desktops have already been ported (LP: #1417980)

  2. Can these apps be ported or removed before 18.04 LTS is released?

  3. Can the desktops be ported and how bad is it if they are not ported
  and -synaptics is no longer available?

  4. If -synaptics can't be removed completely from 18.04 LTS, does it
  make sense to have gnome-control-center Conflicts: xserver-xorg-input-
  synaptics?

  5. Is there any other way we can fix this conflict?

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

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

[Touch-packages] [Bug 1380702] Re: No keyboards shortcuts in QT apps

2017-04-26 Thread Javier Coleto 
As Anatoli, I also updated the package to libqt5widgets5 xenial-proposed
5.5.1+dfsg-16ubuntu7.4 and it didn't solve the problem.

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

Title:
  No keyboards shortcuts in QT apps

Status in appmenu-qt5:
  In Progress
Status in Canonical System Image:
  In Progress
Status in sni-qt:
  New
Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Xenial:
  Fix Committed
Status in qtbase-opensource-src source package in Yakkety:
  Confirmed

Bug description:
  Impact
  ==

  This affects all Qt applications on Unity and other desktops which use
  global menu, either via appmenu-qt5 or via native implementation on
  Yakkety.

  Any shortcut is not working if the corresponding action is attached
  only to the menubar (i.e. and not also to the toolbar). It can be
  reproduced with almost any application by removing the toolbar (right-
  clicking on it and deselecting it).

  Test Case
  =

  * Open Qt Assistant;
  * Press Ctrl+T (this action is not on the toolbar).

  Expected: a new tab should be opened. Current result: nothing happens.

  In Yakkety the fix should work both with and without appmenu-qt5.

  Proposed Fix
  

  The proposed fix is a backport of the upstream fix at
  https://code.qt.io/cgit/qt/qtbase.git/commit/?id=287f548d4c7cc594.

  Actually just the qshortcut.cpp part would be sufficient, but the
  other parts make sure it plays fine together with https://cgit.kde.org
  /plasma-integration.git/commit/?id=aef74e97e2ed462a.

  Regression Potential
  

  The fix is in Zesty for 1½ months now (in upstream even longer), and
  so far nobody complained. People have verified that the fix works (see
  comment #63).

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt5/+bug/1380702/+subscriptions

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

[Touch-packages] [Bug 1685900] Re: On artful, no working dns after upgrading to systemd 233-5ubuntu1

2017-04-26 Thread Harry 
Dimitri,
one more test I just did.

I started systemd-resolved manually:
~$ sudo service systemd-resolved restart

After that the output of systemd-resolve --status is OK:
Global
 DNS Servers: 8.8.8.8
  8.8.4.4
  2001:4860:4860::
  2001:4860:4860::8844
  DNSSEC NTA: 10.in-addr.arpa
  16.172.in-addr.arpa
  168.192.in-addr.arpa
  17.172.in-addr.arpa
  18.172.in-addr.arpa
  19.172.in-addr.arpa
  20.172.in-addr.arpa
  21.172.in-addr.arpa
  22.172.in-addr.arpa
  23.172.in-addr.arpa
  24.172.in-addr.arpa
  25.172.in-addr.arpa
  26.172.in-addr.arpa
  27.172.in-addr.arpa
  28.172.in-addr.arpa
  29.172.in-addr.arpa
  30.172.in-addr.arpa
  31.172.in-addr.arpa
  corp
  d.f.ip6.arpa
  home
  internal
  intranet
  lan
  local
  private
  test
Link 2 (eth0)
  Current Scopes: LLMNR/IPv4 LLMNR/IPv6
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: allow-downgrade
DNSSEC supported: yes

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

Title:
  On artful, no working dns after upgrading to systemd 233-5ubuntu1

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to the newest systemd 233-5ubuntu1 (in artful proposed) I got 
no network.
  This is very likely a DNS issue.
  As a workaround downgrading back to systemd 232-21ubuntu3 the network and DNS 
work fine.

  So something odd has happened between these versions.

  My setup is a fully upgraded artful with proposed repo turned on.
  I use only Gnome DE with GDM.
  Everything else works fine, but not systemd 233-5ubuntu1.

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

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

[Touch-packages] [Bug 1686335] [NEW] package libgstreamer0.10-0 0.10.36-1.5 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libgstreamer0.10-0/changelog.Debian.gz', which is diff

2017-04-26 Thread Eshel A. Nir 
Public bug reported:

XX

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libgstreamer0.10-0 0.10.36-1.5
ProcVersionSignature: Ubuntu 4.4.0-41.61-generic 4.4.21
Uname: Linux 4.4.0-41-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Wed Apr 26 10:49:08 2017
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
DuplicateSignature:
 Unpacking libgstreamer0.10-0:amd64 (0.10.36-1.5ubuntu1) over (0.10.36-1.5) ...
 dpkg: error processing archive 
/var/cache/apt/archives/libgstreamer0.10-0_0.10.36-1.5ubuntu1_amd64.deb 
(--unpack):
  trying to overwrite shared 
'/usr/share/doc/libgstreamer0.10-0/changelog.Debian.gz', which is different 
from other instances of package libgstreamer0.10-0:amd64
ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libgstreamer0.10-0/changelog.Debian.gz', which is different 
from other instances of package libgstreamer0.10-0:amd64
InstallationDate: Installed on 2017-04-01 (24 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt  1.2.10ubuntu1
SourcePackage: gstreamer0.10
Title: package libgstreamer0.10-0 0.10.36-1.5 failed to install/upgrade: trying 
to overwrite shared '/usr/share/doc/libgstreamer0.10-0/changelog.Debian.gz', 
which is different from other instances of package libgstreamer0.10-0:amd64
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gstreamer0.10 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package need-duplicate-check package-conflict xenial

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

Title:
  package libgstreamer0.10-0 0.10.36-1.5 failed to install/upgrade:
  trying to overwrite shared
  '/usr/share/doc/libgstreamer0.10-0/changelog.Debian.gz', which is
  different from other instances of package libgstreamer0.10-0:amd64

Status in gstreamer0.10 package in Ubuntu:
  New

Bug description:
  XX

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libgstreamer0.10-0 0.10.36-1.5
  ProcVersionSignature: Ubuntu 4.4.0-41.61-generic 4.4.21
  Uname: Linux 4.4.0-41-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Wed Apr 26 10:49:08 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DuplicateSignature:
   Unpacking libgstreamer0.10-0:amd64 (0.10.36-1.5ubuntu1) over (0.10.36-1.5) 
...
   dpkg: error processing archive 
/var/cache/apt/archives/libgstreamer0.10-0_0.10.36-1.5ubuntu1_amd64.deb 
(--unpack):
trying to overwrite shared 
'/usr/share/doc/libgstreamer0.10-0/changelog.Debian.gz', which is different 
from other instances of package libgstreamer0.10-0:amd64
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libgstreamer0.10-0/changelog.Debian.gz', which is different 
from other instances of package libgstreamer0.10-0:amd64
  InstallationDate: Installed on 2017-04-01 (24 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: gstreamer0.10
  Title: package libgstreamer0.10-0 0.10.36-1.5 failed to install/upgrade: 
trying to overwrite shared 
'/usr/share/doc/libgstreamer0.10-0/changelog.Debian.gz', which is different 
from other instances of package libgstreamer0.10-0:amd64
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/1686335/+subscriptions

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

[Touch-packages] [Bug 1684854] Re: The default behaviour for search domains changed from 16.10 to 17.04

2017-04-26 Thread Stanislav Bocinec 
This isssue is not relevant to VPN connections only but also for normal
workin local network. systemd-resolve and systemd-resolved stub listener
are behaving differently - the stub does not accept the domain/search
domains sent by DHCP. THis is really weird. Isn't the issue in
domain/search domains not properly put into a dynamic /etc/resolv.conf
?

Here are few examples (domain name change to fictive example.org):
1. Test of the Domain resolving using systemd-resolve:

$ systemd-resolve test
test: 192.168.0.53
  (test.example.org)

-- Information acquired via protocol DNS in 3.0ms.
-- Data is authenticated: no
sob@linno ~ $ nslookup test
Server: 127.0.0.53
Address:127.0.0.53#53

** server can't find test: SERVFAIL

2. DNS resolve using the stub resolver:
$ nslookup - 127.0.0.53
> test
Server: 127.0.0.53
Address:127.0.0.53#53

** server can't find test: SERVFAIL
> test.example.org
Server: 127.0.0.53
Address:127.0.0.53#53

Non-authoritative answer:
Name:   test.example.org
Address: 192.168.0.53
> 


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

nameserver 127.0.0.53

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

Title:
  The default behaviour for search domains changed from 16.10 to 17.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Since Ubuntu 17.04 uses systemd-resolved for DNS lookups the default
  behaviour for search domains changed. By default systemd-resolved does
  not use the domain supplied by DHCP as a search domain.

  So network-manager should at least have an option to tell systemd-
  networkd to change it's behaviour. In systemd-networkd the
  corresponding option is named "UseDomains".

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

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

[Touch-packages] [Bug 1686332] [NEW] Bug after MAJ

2017-04-26 Thread Merlan jp 
Public bug reported:

I don't speak english, i speak french.
Sorry, thank you.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
Uname: Linux 4.10.0-20-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Wed Apr 26 09:39:43 2017
DistUpgraded: 2017-04-25 15:15:49,488 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: L'exécution du processus fils « 
./xorg_fix_proprietary.py » a échoué (No such file or directory) (8))
DistroCodename: zesty
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation GT215 [GeForce GT 320] [10de:0ca2] (rev a2) (prog-if 00 
[VGA controller])
   Subsystem: PC Partner Limited / Sapphire Technology GT215 [GeForce GT 320] 
[174b:2150]
InstallationDate: Installed on 2016-12-17 (129 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: Packard Bell imedia S3210
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic 
root=UUID=c5d2d972-c6c9-4dc9-9c2e-f7a0abc19de0 ro splash quiet
SourcePackage: xorg
UpgradeStatus: Upgraded to zesty on 2017-04-25 (0 days ago)
dmi.bios.date: 11/06/2009
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: P01-B2
dmi.board.name: WMCP78M
dmi.board.vendor: Packard Bell
dmi.chassis.type: 3
dmi.chassis.vendor: Packard Bell
dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrP01-B2:bd11/06/2009:svnPackardBell:pnimediaS3210:pvr:rvnPackardBell:rnWMCP78M:rvr:cvnPackardBell:ct3:cvr:
dmi.product.name: imedia S3210
dmi.sys.vendor: Packard Bell
version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1
xserver.bootTime: Wed Apr 26 09:34:31 2017
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputLogitech USB RECEIVER MOUSE, id 8
 inputAT Translated Set 2 keyboard KEYBOARD, 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.version: 2:1.19.3-1ubuntu1
xserver.video_driver: nouveau

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


** Tags: amd64 apport-bug ubuntu zesty

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

Title:
  Bug after MAJ

Status in xorg package in Ubuntu:
  New

Bug description:
  I don't speak english, i speak french.
  Sorry, thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Apr 26 09:39:43 2017
  DistUpgraded: 2017-04-25 15:15:49,488 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: L'exécution du processus fils « 
./xorg_fix_proprietary.py » a échoué (No such file or directory) (8))
  DistroCodename: zesty
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GT215 [GeForce GT 320] [10de:0ca2] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology GT215 [GeForce GT 320] 
[174b:2150]
  InstallationDate: Installed on 2016-12-17 (129 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Packard Bell imedia S3210
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic 
root=UUID=c5d2d972-c6c9-4dc9-9c2e-f7a0abc19de0 ro splash quiet
  SourcePackage: xorg
  UpgradeStatus: Upgraded to zesty on 2017-04-25 (0 days ago)
  dmi.bios.date: 11/06/2009
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: P01-B2
  dmi.board.name: WMCP78M
  dmi.board.vendor: Packard Bell
  dmi.chassis.type: 3
  dmi.chassis.vendor: Packard Bell
  dmi.modalias:

[Touch-packages] [Bug 1685900] Re: On artful, no working dns after upgrading to systemd 233-5ubuntu1

2017-04-26 Thread Harry 
Dimitri,
thank you for the information.

Now, as I am not very familiar with the systemd nor the dns setup, I
would be happy if you could give me advice how to proceed on this issue.

The status of my setup is as follows.
I have installed all the latest packages of artful aardvark, also from proposed 
repo.

Network:
I have now installed systemd 233-5ubuntu1.
Like I wrote, if I install dnsutils and bind9-host, I get no working dns (not 
even after several reboots).
But, if I install bind9, the dns is working (after one reboot).
This means already, I suppose, I do not have systemd-resolved working.
My setup is using bind9 dns server instead.


Here is the output of systemd-resolve --status:
Failed to get global data: Unit dbus-org.freedesktop.resolve1.service not found.


Here is the output of systemctl status systemd-journald.service:
● systemd-journald.service - Journal Service
   Loaded: loaded (/lib/systemd/system/systemd-journald.service; static; vendor 
preset: enabled)
   Active: active (running) since Wed 2017-04-26 09:59:31 EEST; 18min ago
 Docs: man:systemd-journald.service(8)
   man:journald.conf(5)
 Main PID: 301 (systemd-journal)
   Status: "Processing requests..."
Tasks: 1 (limit: 4915)
   CGroup: /system.slice/systemd-journald.service
   └─301 /lib/systemd/systemd-journald
april 26 09:59:31 Sabertooth systemd-journald[301]: Journal started
april 26 09:59:31 Sabertooth systemd-journald[301]: Runtime journal 
(/run/log/journal/bd732b34a1caf7
156751544d541ed208) is 8.0M, max 157.3M, 149.3M free.
april 26 09:59:31 Sabertooth systemd-journald[301]: Runtime journal 
(/run/log/journal/bd732b34a1caf7
156751544d541ed208) is 8.0M, max 157.3M, 149.3M free.
Warning: Journal has been rotated since unit was started. Log output is 
incomplete or unavailable.


Here is the output of 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.


* * * * *

Now, with the older systemd 232-21ubuntu3 the systemd-resolved was working OK 
(and dns).
Here is the output from systemd 232-21ubuntu3 systemd-resolve --status:
Global
  DNSSEC NTA: 10.in-addr.arpa
  16.172.in-addr.arpa
  168.192.in-addr.arpa
  17.172.in-addr.arpa
  18.172.in-addr.arpa
  19.172.in-addr.arpa
  20.172.in-addr.arpa
  21.172.in-addr.arpa
  22.172.in-addr.arpa
  23.172.in-addr.arpa
  24.172.in-addr.arpa
  25.172.in-addr.arpa
  26.172.in-addr.arpa
  27.172.in-addr.arpa
  28.172.in-addr.arpa
  29.172.in-addr.arpa
  30.172.in-addr.arpa
  31.172.in-addr.arpa
  corp
  d.f.ip6.arpa
  home
  internal
  intranet
  lan
  local
  private
  test
Link 2 (eth0)
  Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no
 DNS Servers: 193.210.18.18
  193.210.19.19
  DNS Domain: dhcp.inet.fi


* * * * * * * *

So please, can you print what specific commands or installations should
I do now in order to get systemd-resolved service running and
resolf.conf pointing at it?

Also how do I get the journal logs?
Runtime journal (/run/log/journal/bd732b34a1caf7156751544d541ed208) is 8.0M, so 
it is a very big file indeed.

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

Title:
  On artful, no working dns after upgrading to systemd 233-5ubuntu1

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to the newest systemd 233-5ubuntu1 (in artful proposed) I got 
no network.
  This is very likely a DNS issue.
  As a workaround downgrading back to systemd 232-21ubuntu3 the network and DNS 
work fine.

  So something odd has happened between these versions.

  My setup is a fully upgraded artful with proposed repo turned on.
  I use only Gnome DE with GDM.
  Everything else works fine, but not systemd 233-5ubuntu1.

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

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

[Touch-packages] [Bug 1684854] Re: The default behaviour for search domains changed from 16.10 to 17.04

2017-04-26 Thread ThyMythos 
Seems this lines of code are responsible:

src/dns/nm-dns-systemd-resolved.c:

static void
add_domain (GVariantBuilder *domains,
const char *domain,
gboolean never_default)
{
/* If this link is never the default (e.g. only used for resources on 
this
 * network) add a routing domain. */
g_variant_builder_add (domains, "(sb)", domain, never_default);
}


So someone actually wanted this behavious. The question is "why"? I definitly 
want to use my VPN only for resources on that network and yes I want to resolve 
the internal names of this network using a search domain.

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

Title:
  The default behaviour for search domains changed from 16.10 to 17.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Since Ubuntu 17.04 uses systemd-resolved for DNS lookups the default
  behaviour for search domains changed. By default systemd-resolved does
  not use the domain supplied by DHCP as a search domain.

  So network-manager should at least have an option to tell systemd-
  networkd to change it's behaviour. In systemd-networkd the
  corresponding option is named "UseDomains".

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

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

[Touch-packages] [Bug 1664491] Re: package systemd-sysv 229-4ubuntu16 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv

2017-04-26 Thread Launchpad Bug Tracker 
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  package systemd-sysv 229-4ubuntu16 failed to install/upgrade: pre-
  dependency problem - not installing systemd-sysv

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The package systemd-sysv 229-4ubuntu16 failed to install after upgrade
  from 15.10 to 16.4

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd-sysv 229-4ubuntu16
  ProcVersionSignature: Ubuntu 4.4.0-63.84-generic 4.4.44
  Uname: Linux 4.4.0-63-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Tue Feb 14 01:04:34 2017
  ErrorMessage: pre-dependency problem - not installing systemd-sysv
  InstallationDate: Installed on 2014-09-01 (896 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20120427-02:14
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: systemd
  Title: package systemd-sysv 229-4ubuntu16 failed to install/upgrade: 
pre-dependency problem - not installing systemd-sysv
  UpgradeStatus: Upgraded to xenial on 2017-02-14 (0 days ago)

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

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

[Touch-packages] [Bug 1441253] Re: hanging suspend job prevents shutdown

2017-04-26 Thread mohtaw 
i have the same issue on 16.10 Dell Latitude E6430 
i can't use the interface to shutdown or reboot and for 

#shutdown -h 
ubuntu Failed to power off system via logind: There's already a shutdown or 
sleep operation in progress

and only i can reboot or shutdown using the -f

# shutdown -f

$ uname  -a 
Linux XLAP 4.8.0-46-generic #49-Ubuntu SMP Fri Mar 31 13:57:14 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux

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

Title:
  hanging suspend job prevents shutdown

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  poweroff (systemd poweroff) and reboot no longer work

  running sudo sytemd poweroff generates this:

  Failed to start poweroff.target: Transaction is destructive.

  journal log also shows:

  Apr 07 18:30:12 alice polkitd(authority=local)[1088]: Registered 
Authentication Agent for unix-process:32412:2895609 (system bus name :1.194 
[/usr/bin/pkttyagent --notify-fd 5 --fallback], object path 
/org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
  Apr 07 18:30:12 alice systemd[1]: Requested transaction contradicts existing 
jobs: Transaction is destructive.
  Apr 07 18:30:12 alice polkitd(authority=local)[1088]: Unregistered 
Authentication Agent for unix-process:32412:2895609 (system bus name :1.194, 
object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale 
en_US.UTF-8) (disconnected from bus)

  
  Output of systemctl list-jobs
   JOB UNITTYPE  STATE  
  6009 suspend.target  start waiting
  6010 systemd-suspend.service start running
  6014 anacron-resume.service  start waiting

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-6ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  Date: Tue Apr  7 18:32:27 2015
  MachineType: Hewlett-Packard HP EliteBook 8560w
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-12-generic 
root=UUID=90fa42f5-708d-4432-9241-315b9c08ba98 ro nomodeset rootflags=subvol=@
  SourcePackage: systemd
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: Upgraded to vivid on 2015-03-02 (36 days ago)
  dmi.bios.date: 08/04/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SVD Ver. F.50
  dmi.board.name: 1631
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 01.3D
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SVDVer.F.50:bd08/04/2014:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.3D:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8560w
  dmi.product.version: A0001D02
  dmi.sys.vendor: Hewlett-Packard

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

-- 
Mailing list: https://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