from:"ChristianEhrhardt"

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

@Spiegel - yes I think so, thanks for finding the old reference.
Marking as a Dup.

Could someone of the desktop Team give this a look from the 18.04/gnome-
shell POV - will this go away?

** This bug has been marked a duplicate of bug 857651
   Unable to hide users from login screen / user switcher

-- 
You received this bug notification because you are a member of Desktop
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:
  Won't Fix
Status in ifmail package in Ubuntu:
  Won't Fix
Status in libvirt package in Ubuntu:
  Won't Fix
Status in lightdm package in Ubuntu:
  Confirmed
Status in netqmail package in Ubuntu:
  Won't Fix
Status in sddm package in Ubuntu:
  Fix Released

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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

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

If we stick to depend on accountsservice, then it comes down to the following
$ dbus-send --print-reply=literal --system --dest=org.freedesktop.Accounts 
/org/freedesktop/Accounts org.freedesktop.Accounts.ListCachedUsers

Which should get some sort of the old hiddenShells feature back to
exclude those users.

-- 
You received this bug notification because you are a member of Desktop
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:
  Won't Fix
Status in ifmail package in Ubuntu:
  Won't Fix
Status in libvirt package in Ubuntu:
  Won't Fix
Status in lightdm package in Ubuntu:
  Confirmed
Status in netqmail package in Ubuntu:
  Won't Fix
Status in sddm package in Ubuntu:
  Fix Released

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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

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

Arrr wanted to send that update to the dup target ...

-- 
You received this bug notification because you are a member of Desktop
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:
  Won't Fix
Status in ifmail package in Ubuntu:
  Won't Fix
Status in libvirt package in Ubuntu:
  Won't Fix
Status in lightdm package in Ubuntu:
  Confirmed
Status in netqmail package in Ubuntu:
  Won't Fix
Status in sddm package in Ubuntu:
  Fix Released

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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 857651] Re: Unable to hide users from login screen / user switcher

I was made aware in bug #1667113 that this seems to be the root bug to dup this 
onto.
I know this comes down to accountsservice, as others not using it like sddm are 
just fine.

If we stick to depend on accountsservice, then it comes down to the following
$ dbus-send --print-reply=literal --system --dest=org.freedesktop.Accounts 
/org/freedesktop/Accounts org.freedesktop.Accounts.ListCachedUsers

Which should get some sort of the old hiddenShells feature back to
exclude those users.

Could someone of the desktop Team give this a look from the 18.04/gnome-
shell POV - will this go away?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/857651

Title:
  Unable to hide users from login screen / user switcher

Status in accountsservice:
  Confirmed
Status in accountsservice package in Ubuntu:
  Triaged
Status in lightdm package in Ubuntu:
  Triaged

Bug description:
  Users that I have appended to the 'hidden-users' field in
  /etc/lightdm/users.conf are not actually hidden. They are still listed
  on the login screen and in Unity's user switching menu.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: lightdm 0.9.7-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
  Uname: Linux 3.0.0-11-generic x86_64
  ApportVersion: 1.23-0ubuntu1
  Architecture: amd64
  Date: Fri Sep 23 11:44:29 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110413)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to oneiric on 2011-09-23 (0 days ago)
  mtime.conffile..etc.lightdm.users.conf: 2011-09-23T08:46:55.039175

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

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

[Desktop-packages] [Bug 1747394] Re: libvirtd crashed with SIGSEGV in xmlHashLookup3__internal_alias()

2018-02-05 Thread ChristianEhrhardt

Hi Sosha,
the crash itself is in libxml2 so I add a bug task for that.

>From the libvirt POV this seems to be in a stage where it initializes its 
>state drivers.
virStateInitialize iterates on drivers and calls stateInitialize of the 
respective backend.

I can't see from your trace which that is, but I assume this triggers right 
when you start libvirtd?
If so did you register special backends?
The following is the list of drivers with such a function

0 bhyve_driver.c 1753 .stateInitialize = bhyveStateInitialize,
2 interface_backend_netcf.c  1139 .stateInitialize = netcfStateInitialize,
3 interface_backend_udev.c   1211 .stateInitialize = udevStateInitialize,
4 libxl_driver.c 6594 .stateInitialize = libxlStateInitialize,
5 lxc_driver.c   5590 .stateInitialize = lxcStateInitialize,
6 bridge_driver.c4272 .stateInitialize = networkStateInitialize,
7 node_device_hal.c   778 .stateInitialize = nodeStateInitialize,
8 node_device_udev.c 2070 .stateInitialize = nodeStateInitialize,
9 nwfilter_driver.c   640 .stateInitialize = nwfilterStateInitialize,
a qemu_driver.c 21355 .stateInitialize = qemuStateInitialize,
b remote_driver.c8648 .stateInitialize = remoteStateInitialize,
c secret_driver.c 578 .stateInitialize = secretStateInitialize,
d storage_driver.c   2743 .stateInitialize = storageStateInitialize,
0 uml_driver.c   3020 .stateInitialize = umlStateInitialize,
1 vz_driver.c4171 .stateInitialize = vzStateInitialize,
2 xen_driver.c269 .stateInitialize = xenUnifiedStateInitialize,

Since it has netcf entries down the stack trace I can only assume it is the 
init of netcf.
That would be in netcfStateInitialize

There is calls ncf_init and the lib also has libxml2 bindings.
I fail to derive more from the stack trace as-is, but that already meand we 
should also add a task for netcf.

I wonder:
1. is this reproducible on e.g. every restart of libvirtd?
2. do you have any non-default network configuration on the system or in 
libvirt that might be what we would need to reproduce that?

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

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

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libxml2 in Ubuntu.
https://bugs.launchpad.net/bugs/1747394

Title:
  libvirtd crashed with SIGSEGV in xmlHashLookup3__internal_alias()

Status in libvirt package in Ubuntu:
  Incomplete
Status in libxml2 package in Ubuntu:
  New
Status in netcf package in Ubuntu:
  New

Bug description:
  after upgrade packages...

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: libvirt-daemon 4.0.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  Date: Mon Feb  5 04:19:29 2018
  ExecutablePath: /usr/sbin/libvirtd
  InstallationDate: Installed on 2017-09-02 (156 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcAttrCurrent: /usr/sbin/libvirtd (enforce)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic.efi.signed 
root=UUID=a5d262b4-1b0f-4856-9935-f6a7f6d6d406 ro quiet splash vt.handoff=7
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x7ff92a1ee4b5 :mov
0x28(%rbx),%eax
   PC (0x7ff92a1ee4b5) ok
   source "0x28(%rbx)" (0xdc9b6a9060306869) not located in a known VMA region 
(needed readable region)!
   destination "%eax" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: libvirt
  StacktraceTop:
   xmlHashLookup () from /usr/lib/x86_64-linux-gnu/libxml2.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libxml2.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libxml2.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libxml2.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libxml2.so.2
  Title: libvirtd crashed with SIGSEGV in xmlHashLookup()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

2018-04-04 Thread ChristianEhrhardt

I heard people talk about it, but realized the tracker is missing a Task for 
openvswitch:
/etc/network/if-post-down.d/openvswitch
/etc/network/if-pre-up.d/openvswitch

IIRC all the discussions correctly that was one of the harder cases due
to "Pre" not really being a defined thing anymore.

The question is how much OVS relies on that to work as PRE, or if it can
be later (or totally ignored).

I'll ping Jamespage about this for his OVS experience.

P.S. sorry if I duplicate some work here, but I can't find it in the bug
at all, so better twice than missed.

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1718227

Title:
  replacement of ifupdown with netplan needs integration for
  /etc/network/if{up,down}.d scripts

Status in aiccu package in Ubuntu:
  Invalid
Status in aoetools package in Ubuntu:
  New
Status in avahi package in Ubuntu:
  New
Status in bind9 package in Ubuntu:
  Invalid
Status in chrony package in Ubuntu:
  Confirmed
Status in clamav package in Ubuntu:
  Triaged
Status in controlaula package in Ubuntu:
  New
Status in epoptes package in Ubuntu:
  New
Status in ethtool package in Ubuntu:
  New
Status in guidedog package in Ubuntu:
  New
Status in htpdate package in Ubuntu:
  New
Status in ifenslave package in Ubuntu:
  Won't Fix
Status in ifmetric package in Ubuntu:
  Won't Fix
Status in ifupdown-multi package in Ubuntu:
  New
Status in ifupdown-scripts-zg2 package in Ubuntu:
  Invalid
Status in isatapd package in Ubuntu:
  New
Status in lprng package in Ubuntu:
  New
Status in miredo package in Ubuntu:
  New
Status in mythtv package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  New
Status in nss-pam-ldapd package in Ubuntu:
  New
Status in ntp package in Ubuntu:
  New
Status in openntpd package in Ubuntu:
  New
Status in openresolv package in Ubuntu:
  Won't Fix
Status in openssh package in Ubuntu:
  New
Status in openvpn package in Ubuntu:
  New
Status in openvswitch package in Ubuntu:
  New
Status in postfix package in Ubuntu:
  New
Status in quicktun package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New
Status in sendmail package in Ubuntu:
  New
Status in shorewall-init package in Ubuntu:
  New
Status in sidedoor package in Ubuntu:
  New
Status in slrn package in Ubuntu:
  New
Status in tinc package in Ubuntu:
  New
Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ucarp package in Ubuntu:
  New
Status in uml-utilities package in Ubuntu:
  New
Status in uruk package in Ubuntu:
  New
Status in vlan package in Ubuntu:
  Won't Fix
Status in vzctl package in Ubuntu:
  Triaged
Status in wide-dhcpv6 package in Ubuntu:
  New
Status in wpa package in Ubuntu:
  New

Bug description:
  when network is configured with ifupdown, scripts in
  /etc/network/ifup.d/ were called on network being brought up and
  /etc/network/ifdown.d were called on network being brought down.

  Any packages that shipped these hooks need to be verified to have the
  same functionality under a netplan configured system.

  # binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
  # for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u

  aiccu
  aoetools
  avahi
  bind9
  chrony
  clamav
  controlaula
  epoptes
  ethtool
  guidedog
  htpdate
  ifenslave
  ifmetric
  ifupdown-extra
  ifupdown-multi
  ifupdown-scripts-zg2
  isatapd
  lprng
  miredo
  mythtv-backend
  nss-pam-ldapd
  ntp
  openntpd
  openresolv
  openssh
  openvpn
  postfix
  quicktun
  resolvconf
  sendmail
  shorewall-init
  sidedoor
  slrn
  tinc
  ubuntu-fan
  ucarp
  uml-utilities
  uruk
  vlan
  vzctl
  wide-dhcpv6
  wpa

  
  Related bugs:
   * bug 1718227: replacement of ifupdown with netplan needs integration for 
/etc/network/if{up,down}.d scripts 
   * bug 1713803: replacement of resolvconf with systemd needs integration 
   * bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: netplan (not installed)
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Sep 19 10:53:08 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (789 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: plan
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.l

[Desktop-packages] [Bug 857651] Re: Unable to hide users from login screen / user switcher

2018-04-11 Thread ChristianEhrhardt

** Tags added: bionic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/857651

Title:
  Unable to hide users from login screen / user switcher

Status in accountsservice:
  Confirmed
Status in accountsservice package in Ubuntu:
  Triaged
Status in lightdm package in Ubuntu:
  Triaged

Bug description:
  Users that I have appended to the 'hidden-users' field in
  /etc/lightdm/users.conf are not actually hidden. They are still listed
  on the login screen and in Unity's user switching menu.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: lightdm 0.9.7-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
  Uname: Linux 3.0.0-11-generic x86_64
  ApportVersion: 1.23-0ubuntu1
  Architecture: amd64
  Date: Fri Sep 23 11:44:29 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110413)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to oneiric on 2011-09-23 (0 days ago)
  mtime.conffile..etc.lightdm.users.conf: 2011-09-23T08:46:55.039175

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

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

[Desktop-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

2018-04-16 Thread ChristianEhrhardt

Nice summary, but wrong bug - sorry for the noise here :-/

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1718227

Title:
  replacement of ifupdown with netplan needs integration for
  /etc/network/if{up,down}.d scripts

Status in aiccu package in Ubuntu:
  Invalid
Status in aoetools package in Ubuntu:
  New
Status in avahi package in Ubuntu:
  New
Status in bind9 package in Ubuntu:
  Invalid
Status in chrony package in Ubuntu:
  Confirmed
Status in clamav package in Ubuntu:
  Triaged
Status in controlaula package in Ubuntu:
  New
Status in epoptes package in Ubuntu:
  New
Status in ethtool package in Ubuntu:
  New
Status in guidedog package in Ubuntu:
  New
Status in htpdate package in Ubuntu:
  New
Status in ifenslave package in Ubuntu:
  Won't Fix
Status in ifmetric package in Ubuntu:
  Won't Fix
Status in ifupdown-multi package in Ubuntu:
  New
Status in ifupdown-scripts-zg2 package in Ubuntu:
  Invalid
Status in isatapd package in Ubuntu:
  New
Status in lprng package in Ubuntu:
  New
Status in miredo package in Ubuntu:
  New
Status in mythtv package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  New
Status in nss-pam-ldapd package in Ubuntu:
  New
Status in ntp package in Ubuntu:
  New
Status in openntpd package in Ubuntu:
  New
Status in openresolv package in Ubuntu:
  Won't Fix
Status in openssh package in Ubuntu:
  New
Status in openvpn package in Ubuntu:
  New
Status in openvswitch package in Ubuntu:
  New
Status in postfix package in Ubuntu:
  New
Status in quicktun package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New
Status in sendmail package in Ubuntu:
  New
Status in shorewall-init package in Ubuntu:
  New
Status in sidedoor package in Ubuntu:
  New
Status in slrn package in Ubuntu:
  New
Status in tinc package in Ubuntu:
  New
Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ucarp package in Ubuntu:
  New
Status in uml-utilities package in Ubuntu:
  New
Status in uruk package in Ubuntu:
  New
Status in vlan package in Ubuntu:
  Won't Fix
Status in vzctl package in Ubuntu:
  Triaged
Status in wide-dhcpv6 package in Ubuntu:
  New
Status in wpa package in Ubuntu:
  New

Bug description:
  when network is configured with ifupdown, scripts in
  /etc/network/ifup.d/ were called on network being brought up and
  /etc/network/ifdown.d were called on network being brought down.

  Any packages that shipped these hooks need to be verified to have the
  same functionality under a netplan configured system.

  # binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
  # for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u

  aiccu
  aoetools
  avahi
  bind9
  chrony
  clamav
  controlaula
  epoptes
  ethtool
  guidedog
  htpdate
  ifenslave
  ifmetric
  ifupdown-extra
  ifupdown-multi
  ifupdown-scripts-zg2
  isatapd
  lprng
  miredo
  mythtv-backend
  nss-pam-ldapd
  ntp
  openntpd
  openresolv
  openssh
  openvpn
  postfix
  quicktun
  resolvconf
  sendmail
  shorewall-init
  sidedoor
  slrn
  tinc
  ubuntu-fan
  ucarp
  uml-utilities
  uruk
  vlan
  vzctl
  wide-dhcpv6
  wpa

  
  Related bugs:
   * bug 1718227: replacement of ifupdown with netplan needs integration for 
/etc/network/if{up,down}.d scripts 
   * bug 1713803: replacement of resolvconf with systemd needs integration 
   * bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: netplan (not installed)
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Sep 19 10:53:08 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (789 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: plan
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

2018-04-16 Thread ChristianEhrhardt

Lets break this into use cases in Bionic:

I was not sure who should win in each case.
We might either want the clear "order" chrony > ntp > openntp > 
systemd-timesyncd
Or we might want a "last installed" approach, but that is hard as upgrades to 
not count here only real "install". What would "--reinstall" be in these cases?
Maybe we should stick with the clear order, that at least seems more 
deterministic.
Cases 4-6 try to cover testing that order invariancy.

This is an "ideal world" approach, not sure if we can achieve that in the short 
term.
After the "=>" assignment is the service that should run (and only this one).

0. default install - systemd-timesyncd

1. default install - install chrony => Chrony
1b.- remove chrony => systemd-timesyncd

2. default install - install ntp  => NTP
2b.- remove ntp => systemd-timesyncd

3. default install - install openntp => openntp
3b.- remove openntp => systemd-timesyncd

4. default install - install ntp, install chrony => Chrony
4b.  remove chrony => NTP
4c.  remove NTP => systemd-timesyncd

5. default install - install chrony, install NTP => Chrony
5b.  remove Chrony => NTP
5c.  remove NTP => systemd-timesyncd

6. default install - install openntp => openntp
6b.  install NTP => NTP
6c.  install chrony => chrony
6d.  remote NTP & Chrony => openntp
6e.  remove openntp => systemd-timesyncd

7. xenial with ntp - upgrade to B => NTP

8. xenial with ntp - upgrade to B, install chrony => Chrony

9. xenial with ntp - upgrade to B, remove NTP => systemd-timesyncd

10. xenial without ntp - upgrade to B => systemd-timesyncd

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1718227

Title:
  replacement of ifupdown with netplan needs integration for
  /etc/network/if{up,down}.d scripts

Status in aiccu package in Ubuntu:
  Invalid
Status in aoetools package in Ubuntu:
  New
Status in avahi package in Ubuntu:
  New
Status in bind9 package in Ubuntu:
  Invalid
Status in chrony package in Ubuntu:
  Confirmed
Status in clamav package in Ubuntu:
  Triaged
Status in controlaula package in Ubuntu:
  New
Status in epoptes package in Ubuntu:
  New
Status in ethtool package in Ubuntu:
  New
Status in guidedog package in Ubuntu:
  New
Status in htpdate package in Ubuntu:
  New
Status in ifenslave package in Ubuntu:
  Won't Fix
Status in ifmetric package in Ubuntu:
  Won't Fix
Status in ifupdown-multi package in Ubuntu:
  New
Status in ifupdown-scripts-zg2 package in Ubuntu:
  Invalid
Status in isatapd package in Ubuntu:
  New
Status in lprng package in Ubuntu:
  New
Status in miredo package in Ubuntu:
  New
Status in mythtv package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  New
Status in nss-pam-ldapd package in Ubuntu:
  New
Status in ntp package in Ubuntu:
  New
Status in openntpd package in Ubuntu:
  New
Status in openresolv package in Ubuntu:
  Won't Fix
Status in openssh package in Ubuntu:
  New
Status in openvpn package in Ubuntu:
  New
Status in openvswitch package in Ubuntu:
  New
Status in postfix package in Ubuntu:
  New
Status in quicktun package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New
Status in sendmail package in Ubuntu:
  New
Status in shorewall-init package in Ubuntu:
  New
Status in sidedoor package in Ubuntu:
  New
Status in slrn package in Ubuntu:
  New
Status in tinc package in Ubuntu:
  New
Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ucarp package in Ubuntu:
  New
Status in uml-utilities package in Ubuntu:
  New
Status in uruk package in Ubuntu:
  New
Status in vlan package in Ubuntu:
  Won't Fix
Status in vzctl package in Ubuntu:
  Triaged
Status in wide-dhcpv6 package in Ubuntu:
  New
Status in wpa package in Ubuntu:
  New

Bug description:
  when network is configured with ifupdown, scripts in
  /etc/network/ifup.d/ were called on network being brought up and
  /etc/network/ifdown.d were called on network being brought down.

  Any packages that shipped these hooks need to be verified to have the
  same functionality under a netplan configured system.

  # binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
  # for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u

  aiccu
  aoetools
  avahi
  bind9
  chrony
  clamav
  controlaula
  epoptes
  ethtool
  guidedog
  htpdate
  ifenslave
  ifmetric
  ifupdown-extra
  ifupdown-multi
  ifupdown-scripts-zg2
  isatapd
  lprng
  miredo
  mythtv-backend
  nss-pam-ldapd
  ntp
  openntpd
  openresolv
  openssh
  openvpn
  postfix
  quicktun
  resolvconf
  sendmail
  shorewall-init
  sidedoor
  slrn
  tinc
  ubuntu-fan
  ucarp
  uml-utilities
  uruk
  vlan
  vzctl
  wide-

[Desktop-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

2018-04-18 Thread ChristianEhrhardt

Tested on chrony which has a NetworkManager dispatch script that also
works as a hook for networkd-dispatcher.

Works fine by just dropping the links for now.
Changes visible when these hooks are in place

1. when sources get unreachable it detects offlining immediately (instead of 
trying all the time)
2. when a network drops but sources stay reachable nothing happens (no 
accidental offline)
3. when sources are offline and network is attached without connecting to 
anything they stay offline
4. when sources are offline and a connecting network is attached they all 
become online immediately
5. when a network is lost that was connecting to just to some sources only 
those get set offline.

P.S. most of these cases can be well tested with virsh attach-device /
detach-device with multiple network cards (one that connects to network
and one that does not for example)

The biggest issue is that reusing that is very nice, but OTOH dangerous if it 
gets NM only code.
I'll start discussing that upstream before using it in any way.
That happened post 3.2 in
  b563048 "examples: ignore non-up/down events in nm-dispatcher script"

I'm now doing:
1. discussing upstream how we want to do it
2. bring that upstream for networkd-dispatcher
3. backport the change to Bionic chrony package
4. place the files to trigger the callbacks

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1718227

Title:
  replacement of ifupdown with netplan needs integration for
  /etc/network/if{up,down}.d scripts

Status in aiccu package in Ubuntu:
  Invalid
Status in aoetools package in Ubuntu:
  New
Status in avahi package in Ubuntu:
  New
Status in bind9 package in Ubuntu:
  Invalid
Status in chrony package in Ubuntu:
  Confirmed
Status in clamav package in Ubuntu:
  Triaged
Status in controlaula package in Ubuntu:
  New
Status in epoptes package in Ubuntu:
  New
Status in ethtool package in Ubuntu:
  New
Status in guidedog package in Ubuntu:
  New
Status in htpdate package in Ubuntu:
  New
Status in ifenslave package in Ubuntu:
  Won't Fix
Status in ifmetric package in Ubuntu:
  Won't Fix
Status in ifupdown-multi package in Ubuntu:
  New
Status in ifupdown-scripts-zg2 package in Ubuntu:
  Invalid
Status in isatapd package in Ubuntu:
  New
Status in lprng package in Ubuntu:
  New
Status in miredo package in Ubuntu:
  New
Status in mythtv package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  New
Status in nss-pam-ldapd package in Ubuntu:
  New
Status in ntp package in Ubuntu:
  New
Status in openntpd package in Ubuntu:
  New
Status in openresolv package in Ubuntu:
  Won't Fix
Status in openssh package in Ubuntu:
  New
Status in openvpn package in Ubuntu:
  New
Status in openvswitch package in Ubuntu:
  New
Status in postfix package in Ubuntu:
  New
Status in quicktun package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New
Status in sendmail package in Ubuntu:
  New
Status in shorewall-init package in Ubuntu:
  New
Status in sidedoor package in Ubuntu:
  New
Status in slrn package in Ubuntu:
  New
Status in tinc package in Ubuntu:
  New
Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ucarp package in Ubuntu:
  New
Status in uml-utilities package in Ubuntu:
  New
Status in uruk package in Ubuntu:
  New
Status in vlan package in Ubuntu:
  Won't Fix
Status in vzctl package in Ubuntu:
  Triaged
Status in wide-dhcpv6 package in Ubuntu:
  New
Status in wpa package in Ubuntu:
  New

Bug description:
  when network is configured with ifupdown, scripts in
  /etc/network/ifup.d/ were called on network being brought up and
  /etc/network/ifdown.d were called on network being brought down.

  Any packages that shipped these hooks need to be verified to have the
  same functionality under a netplan configured system.

  # binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
  # for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u

  aiccu
  aoetools
  avahi
  bind9
  chrony
  clamav
  controlaula
  epoptes
  ethtool
  guidedog
  htpdate
  ifenslave
  ifmetric
  ifupdown-extra
  ifupdown-multi
  ifupdown-scripts-zg2
  isatapd
  lprng
  miredo
  mythtv-backend
  nss-pam-ldapd
  ntp
  openntpd
  openresolv
  openssh
  openvpn
  postfix
  quicktun
  resolvconf
  sendmail
  shorewall-init
  sidedoor
  slrn
  tinc
  ubuntu-fan
  ucarp
  uml-utilities
  uruk
  vlan
  vzctl
  wide-dhcpv6
  wpa

  
  Related bugs:
   * bug 1718227: replacement of ifupdown with netplan needs integration for 
/etc/network/if{up,down}.d scripts 
   * bug 1713803: replacement of resolvconf with systemd needs integration 
   * bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: netplan (not installed)
  Proc

[Desktop-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

2018-04-19 Thread ChristianEhrhardt

Fix for chrony (following networkd-dispatcher change in bug 1765152)
uploaded to bionic-unapproved as 3.2-4ubuntu4

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1718227

Title:
  replacement of ifupdown with netplan needs integration for
  /etc/network/if{up,down}.d scripts

Status in aiccu package in Ubuntu:
  Invalid
Status in aoetools package in Ubuntu:
  New
Status in avahi package in Ubuntu:
  New
Status in bind9 package in Ubuntu:
  Invalid
Status in chrony package in Ubuntu:
  Confirmed
Status in clamav package in Ubuntu:
  Triaged
Status in controlaula package in Ubuntu:
  New
Status in epoptes package in Ubuntu:
  New
Status in ethtool package in Ubuntu:
  New
Status in guidedog package in Ubuntu:
  New
Status in htpdate package in Ubuntu:
  New
Status in ifenslave package in Ubuntu:
  Won't Fix
Status in ifmetric package in Ubuntu:
  Won't Fix
Status in ifupdown-multi package in Ubuntu:
  New
Status in ifupdown-scripts-zg2 package in Ubuntu:
  Invalid
Status in isatapd package in Ubuntu:
  New
Status in lprng package in Ubuntu:
  New
Status in miredo package in Ubuntu:
  New
Status in mythtv package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  New
Status in nss-pam-ldapd package in Ubuntu:
  New
Status in ntp package in Ubuntu:
  New
Status in openntpd package in Ubuntu:
  New
Status in openresolv package in Ubuntu:
  Won't Fix
Status in openssh package in Ubuntu:
  New
Status in openvpn package in Ubuntu:
  New
Status in openvswitch package in Ubuntu:
  New
Status in postfix package in Ubuntu:
  New
Status in quicktun package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New
Status in sendmail package in Ubuntu:
  New
Status in shorewall-init package in Ubuntu:
  New
Status in sidedoor package in Ubuntu:
  New
Status in slrn package in Ubuntu:
  New
Status in tinc package in Ubuntu:
  New
Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ucarp package in Ubuntu:
  New
Status in uml-utilities package in Ubuntu:
  New
Status in uruk package in Ubuntu:
  New
Status in vlan package in Ubuntu:
  Won't Fix
Status in vzctl package in Ubuntu:
  Triaged
Status in wide-dhcpv6 package in Ubuntu:
  New
Status in wpa package in Ubuntu:
  New

Bug description:
  when network is configured with ifupdown, scripts in
  /etc/network/ifup.d/ were called on network being brought up and
  /etc/network/ifdown.d were called on network being brought down.

  Any packages that shipped these hooks need to be verified to have the
  same functionality under a netplan configured system.

  # binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
  # for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u

  aiccu
  aoetools
  avahi
  bind9
  chrony
  clamav
  controlaula
  epoptes
  ethtool
  guidedog
  htpdate
  ifenslave
  ifmetric
  ifupdown-extra
  ifupdown-multi
  ifupdown-scripts-zg2
  isatapd
  lprng
  miredo
  mythtv-backend
  nss-pam-ldapd
  ntp
  openntpd
  openresolv
  openssh
  openvpn
  postfix
  quicktun
  resolvconf
  sendmail
  shorewall-init
  sidedoor
  slrn
  tinc
  ubuntu-fan
  ucarp
  uml-utilities
  uruk
  vlan
  vzctl
  wide-dhcpv6
  wpa

  
  Related bugs:
   * bug 1718227: replacement of ifupdown with netplan needs integration for 
/etc/network/if{up,down}.d scripts 
   * bug 1713803: replacement of resolvconf with systemd needs integration 
   * bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: netplan (not installed)
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Sep 19 10:53:08 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (789 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: plan
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1734212] Re: package openssh-server 1:7.5p1-10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-11-24 Thread ChristianEhrhardt

Hi tenwit,
thanks for your report!
You did just right to clean up and complete the installation.

On the error that occurred, what I can find related in your log is:
  frontend: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

I found various such issues across the past - not frequent but every now and 
then:
- bug 951404
- bug 821630

None came to a perfect conclusion, but it matches the error in your log as well 
as the symptom "the graphical login having crashed".
That took down everything else with it, so the upgrade which you completed 
later on.

You might read through those bugs, there are some hints on lightdm.conf
being responsible, but since you are "out of the bug" already that might
not matter to you anymore.

On the actual issue I don't see openssh related in any way - instead I'll 
re-file this against 
Given that this seems to be something like an X server dying checking and 
attaching those logs might help the Team around lightdm and such as well.

** Package changed: openssh (Ubuntu) => lightdm (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1734212

Title:
  package openssh-server 1:7.5p1-10 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in lightdm package in Ubuntu:
  New

Bug description:
  Happened during upgrade of Ubuntu from 17.04 to 17.10.
  Stepped away from desk; when I came back I was locked out.
  I didn't recognize the lock screen.
  There was no way to log back into the session, no password prompt etc.
  I switched to a VT and monitored top for a while: "artful" was minimally 
active, but never about 2% CPU and memory never changed; I guessed it was 
waiting for a user prompt which I'd never be able to give, so I rebooted.
  I got this error on boot.

  The system is now usable. I've done `dpkg configure -a; apt upgrade`
  and it's all working as I'd expect.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: openssh-server 1:7.5p1-10
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  Date: Fri Nov 24 10:52:14 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-10-12 (42 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  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: openssh
  Title: package openssh-server 1:7.5p1-10 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to artful on 2017-11-23 (0 days ago)

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

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

[Desktop-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

2017-11-03 Thread ChristianEhrhardt

Per former comments setting 17.10 to fix released.

** Changed in: network-manager (Ubuntu Artful)
   Status: Confirmed => Fix Released

** Changed in: network-manager (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Zesty:
  Confirmed
Status in network-manager source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * NetworkManager incorrectly handles dns-priority of the VPN-like
  connections, which leads to leaking DNS queries outside of the VPN
  into the general internet.

   * Upstream has resolved this issue in master and 1.8 to correctly
  configure any dns backends with negative dns-priority settings.

  [Test Case]

  #FIXME#

   * detailed instructions how to reproduce the bug

   * these should allow someone who is not familiar with the affected
 package to reproduce the bug and verify that the updated package fixes
 the problem.

  #FIXME#

  [Regression Potential]

   * If this issue is changed DNS resolution will change, for certain
  queries, to go via VPN rather than general internet. And therefore,
  one may get new/different results or even loose access to
  resolve/access certain parts of the interent depending on what the DNS
  server on VPN chooses to respond to.

  [Other Info]
   
   * Original bug report

  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

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

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

[Desktop-packages] [Bug 1487679] Re: CRITICAL BUG: Breaking ordering cycle by deleting job NetworkManager.service/start

2017-11-10 Thread ChristianEhrhardt

There are many potential affected packages I have no insight, but for
nbd this should be fixed since  1:3.14-1 by upstream now providing a
native systemd service.

That means >=Zesty should be fixed in that regard.
Not sure on backporting that - one would need to check the potential further 
context that needs to go back to Xenial, but that might be the proper solution 
that one might want to try.


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

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

** Also affects: nfs-utils (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

** Also affects: network-manager (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: open-iscsi (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

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

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

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

Title:
  CRITICAL BUG: Breaking ordering cycle by deleting job
  NetworkManager.service/start

Status in systemd:
  Fix Released
Status in avahi package in Ubuntu:
  Confirmed
Status in nbd package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Won't Fix
Status in nfs-utils package in Ubuntu:
  Confirmed
Status in open-iscsi package in Ubuntu:
  New
Status in rpcbind package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Confirmed
Status in util-linux package in Ubuntu:
  Confirmed
Status in avahi source package in Xenial:
  New
Status in nbd source package in Xenial:
  Triaged
Status in network-manager source package in Xenial:
  New
Status in nfs-utils source package in Xenial:
  New
Status in open-iscsi source package in Xenial:
  New
Status in rpcbind source package in Xenial:
  New
Status in systemd source package in Xenial:
  New
Status in util-linux source package in Xenial:
  New
Status in nbd package in Debian:
  Unknown

Bug description:
  
  $ lsb_release -rd
  Description:  Ubuntu 15.04
  Release:  15.04

  $ apt-cache policy nbd-client
  nbd-client:
    Installed: 1:3.8-4ubuntu0.1
    Candidate: 1:3.8-4ubuntu0.1
    Version table:
   *** 1:3.8-4ubuntu0.1 0
  500 http://ch.archive.ubuntu.com/ubuntu/ vivid-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ vivid-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.8-4 0
  500 http://ch.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages

  I'm using the nbd-client to mount some raw disk images over the
  network but starting the nbd-client automatically during bootup does
  not happen due to the following:

  Aug 22 08:54:20 fractal kernel: [   11.875885] systemd[1]: Found dependency 
on nbd-client.service/start
  Aug 22 08:54:20 fractal kernel: [   11.875890] systemd[1]: Breaking ordering 
cycle by deleting job nbd-client.service/start
  Aug 22 08:54:20 fractal kernel: [   11.875891] systemd[1]: Job 
nbd-client.service/start deleted to break ordering cycle starting with 
basic.target/start

  Meaning after boot, I have to manually run `sudo ndb-client start`
  every time I want to access these images. Note that this is no
  diskless system, the images I mount via NBD do not contain the local
  system, they are totally unrelated.

  
  -
  Bug with NFS-server and RPC-bind is indicated by messages:

  $ journalctl | grep -i break
  ноя 06 22:49:57 norbert-vaio systemd[1]: network.target: Breaking ordering 
cycle by deleting job NetworkManager.service/start
  ноя 06 22:49:57 norbert-vaio systemd[1]: NetworkManager.service: Job 
NetworkManager.service/start deleted to break ordering cycle starting with 
network.target/start
  ноя 06 22:49:57 norbert-vaio systemd[1]: nfs-server.service: Breaking 
ordering cycle by deleting job rpcbind.socket/start
  ноя 06 22:49:57 norbert-vaio systemd[1]: rpcbind.socket: Job 
rpcbind.socket/start deleted to break ordering cycle starting with 
nfs-server.service/start

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

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

[Desktop-packages] [Bug 1713098] Re: Frequent DEP8 test failures related to ftp

2017-09-06 Thread ChristianEhrhardt

The errors read like networking or concurrency breaking it.
I agree to have the bug to debug and improve the case.

For now I re-triggered the one hanging test on artful.
The release Team can mark dep8 tests as flaky to skip them blocking a
migration, but that would prereq an analysis of the case as an argument.

--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1713098

Title:
Frequent DEP8 test failures related to ftp

Status in gvfs package in Ubuntu:
New

Bug description:
There are somewhat constant, but intermittent, DEP8 test failures in the gvfs
package. They seem to always be around ftp:
tp:// anonymous (API with flag) ... FAIL

- dbus stdout -

- dbus stderr -

test_anonymous_api_user (__main__.Ftp)
ftp:// anonymous (API with user) ... ok
test_anonymous_cli_option (__main__.Ftp)
ftp:// anonymous (CLI with option) ... Error mounting location: Location is
already mounted
ERROR

- dbus stdout -

- dbus stderr -

test_anonymous_cli_user (__main__.Ftp)
ftp:// anonymous (CLI with user) ... ok
test_authenticated_api (__main__.Ftp)
ftp:// authenticated (API) ... FAIL

- dbus stdout -

- dbus stderr -

test_authenticated_cli (__main__.Ftp)
ftp:// authenticated (CLI) ... FAIL

- dbus stdout -

- dbus stderr -

Here is a link:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/g/gvfs/20170825_135452_c32a9@/log.gz

This bug is to investigate these ftp tests, determine why they are
flaky, and fix them if possible.

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

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

[Desktop-packages] [Bug 1713098] Re: Frequent DEP8 test failures related to ftp

2017-09-06 Thread ChristianEhrhardt

s390x and arm skip the test so all green there isn't worth anything.

The others fail in ~30% of the cases I'd say:
http://autopkgtest.ubuntu.com/packages/gvfs/artful/ppc64el
http://autopkgtest.ubuntu.com/packages/gvfs/artful/i386
http://autopkgtest.ubuntu.com/packages/gvfs/artful/amd64

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1713098

Title:
  Frequent DEP8 test failures related to ftp

Status in gvfs package in Ubuntu:
  New

Bug description:
  There are somewhat constant, but intermittent, DEP8 test failures in the gvfs 
package. They seem to always be around ftp:
  tp:// anonymous (API with flag) ... FAIL

  - dbus stdout -

  - dbus stderr -

  
  test_anonymous_api_user (__main__.Ftp)
  ftp:// anonymous (API with user) ... ok
  test_anonymous_cli_option (__main__.Ftp)
  ftp:// anonymous (CLI with option) ... Error mounting location: Location is 
already mounted
  ERROR

  - dbus stdout -

  - dbus stderr -

  
  test_anonymous_cli_user (__main__.Ftp)
  ftp:// anonymous (CLI with user) ... ok
  test_authenticated_api (__main__.Ftp)
  ftp:// authenticated (API) ... FAIL

  - dbus stdout -

  - dbus stderr -

  
  test_authenticated_cli (__main__.Ftp)
  ftp:// authenticated (CLI) ... FAIL

  - dbus stdout -

  - dbus stderr -

  
  Here is a link: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/g/gvfs/20170825_135452_c32a9@/log.gz

  This bug is to investigate these ftp tests, determine why they are
  flaky, and fix them if possible.

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

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

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

2017-09-11 Thread ChristianEhrhardt

KDE and Gnome seem to not have the issue in general (To admit - I didn't try 
myself the Gnome case yet), so in Artful it might be resolved by the switch to 
Gnome.
I didn't hear from the Desktop Team yet about accountsservice getting a fix.

Also for now there is a workaround in [1]
If this gets no attention for a (more correct and preferred general solution by 
the desktop Team) we might add that in a libvirt update, but as it is a 
symptomatic fix only I'd prefer the other solution.
And in turn all the affected packages would have to get such a fix (probably 
even more and in general as users could add "hidden-shell" type users on their 
own - and those shouldn't be displayed as well.

[1]:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1667113/comments/18

-- 
You received this bug notification because you are a member of Desktop
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
Status in sddm package in Ubuntu:
  Fix Released

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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

2017-09-15 Thread ChristianEhrhardt

Thanks Tom, I agree that loosing the hidden-shells seems to be a regression.
And to make the state more clear that this in the current state is considered a 
an issue of accountservice or lightdm lets mark the other packages won't fix 
for now. Otherwise everybody assumes "the other will do it".

This give a better overview and in general it isn't feasible to fix
"all-those" and since there can be high-id system-users added manually
by users the issue would still persist even when all those other
packages would be fixed.

** Changed in: netqmail (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: libvirt (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: ifmail (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: ceph (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to accountsservice 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:
  Won't Fix
Status in ifmail package in Ubuntu:
  Won't Fix
Status in libvirt package in Ubuntu:
  Won't Fix
Status in lightdm package in Ubuntu:
  Confirmed
Status in netqmail package in Ubuntu:
  Won't Fix
Status in sddm package in Ubuntu:
  Fix Released

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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1718719] Re: qemu can't capture keys properly under wayland

2017-09-21 Thread ChristianEhrhardt

Hi Mathieu,
thanks for the report but since we are up-to-date with qemu and I can't find an 
obvious breakage we might have introduced for this, this should go to 
qmeu-upstream in this case.

Furthermore are these actually two issues?:
#1 - wayland crashes under spice
 more of a wayland bug then I'd expect, but upstream qemu
 might have heard of it and have good pointers
#2 - new qemu does not recognize keys correctly with the default (SDL I'd 
think) frontend?
 That is worth to report upstream qemu for sure.

I added an upstream qemu (and a wayland) task and you can help them to
recreate in case they have questions on how exactly to do so.

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

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wayland in Ubuntu.
https://bugs.launchpad.net/bugs/1718719

Title:
  qemu can't capture keys properly under wayland

Status in QEMU:
  New
Status in qemu package in Ubuntu:
  New
Status in wayland package in Ubuntu:
  New

Bug description:
  This appears to be different than the previous similar bugs; patches
  do look to be applied to use libinput in the wayland case. Still:

  unknown keycodes `(unnamed)', please report to qemu-de...@nongnu.org

  I am using qemu-system-x86   1:2.10+dfsg-0ubuntu1
  on artful.

  Many key inputs work correctly, but at boot the system will not
  properly catch the arrow keys, the above error shows up immediately
  after hitting Esc (for instance) to get to the boot menu. Booting from
  CD onto a daily Ubuntu desktop image, I can't navigate the splash
  menu.

  The same works correctly through virt-manager (which uses spice
  AFAICT, but wayland tends to crash when running virt-manager), and
  things work if I switch my session to Xorg rather than wayland.

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

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

[Desktop-packages] [Bug 1718719] Re: qemu can't capture keys properly under wayland

2017-09-22 Thread ChristianEhrhardt

I wanted to write steps to reproduce, which should be as simple as:
$ wget http://cdimage.ubuntu.com/daily-live/current/artful-desktop-amd64.iso
$ qemu-system-x86_64 -m 512 -boot d -cdrom artful-desktop-amd64.iso

But that works for me as seen in the attached video.
@Mathieu - can you elaborate how to trigger the missing key issue?

** Attachment added: "Screencast 2017-09-22 08:52:05.mp4"
   
https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1718719/+attachment/4954840/+files/Screencast%202017-09-22%2008%3A52%3A05.mp4

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wayland in Ubuntu.
https://bugs.launchpad.net/bugs/1718719

Title:
  qemu can't capture keys properly under wayland

Status in QEMU:
  New
Status in qemu package in Ubuntu:
  New
Status in wayland package in Ubuntu:
  New

Bug description:
  This appears to be different than the previous similar bugs; patches
  do look to be applied to use libinput in the wayland case. Still:

  unknown keycodes `(unnamed)', please report to qemu-de...@nongnu.org

  I am using qemu-system-x86   1:2.10+dfsg-0ubuntu1
  on artful.

  Many key inputs work correctly, but at boot the system will not
  properly catch the arrow keys, the above error shows up immediately
  after hitting Esc (for instance) to get to the boot menu. Booting from
  CD onto a daily Ubuntu desktop image, I can't navigate the splash
  menu.

  The same works correctly through virt-manager (which uses spice
  AFAICT, but wayland tends to crash when running virt-manager), and
  things work if I switch my session to Xorg rather than wayland.

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

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

[Desktop-packages] [Bug 1313550] Re: ping does not work as a normal user on trusty tarball cloud images.

2017-09-28 Thread ChristianEhrhardt

The remaining trusty task is fixed in curtin according to c#29 as well,
updating the tasks to match that.

** Changed in: maas (Ubuntu Trusty)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to iputils in Ubuntu.
https://bugs.launchpad.net/bugs/1313550

Title:
  ping does not work as a normal user on trusty tarball cloud images.

Status in curtin:
  Fix Committed
Status in MAAS:
  Fix Released
Status in curtin package in Ubuntu:
  Fix Released
Status in iputils package in Ubuntu:
  Fix Released
Status in maas package in Ubuntu:
  Fix Released
Status in tar package in Ubuntu:
  Fix Released
Status in tar source package in Precise:
  Confirmed
Status in maas source package in Saucy:
  Won't Fix
Status in tar source package in Saucy:
  Won't Fix
Status in curtin source package in Trusty:
  Fix Released
Status in maas source package in Trusty:
  Fix Released
Status in tar source package in Trusty:
  Fix Released
Status in maas source package in Vivid:
  Won't Fix
Status in maas source package in Wily:
  Fix Released

Bug description:
  With trusty, /bin/ping relies on having extended attributes and kernel
  capabilities to gain the cap_net_raw+p capability. This allows
  removing the suid bit.

  However, the tarball cloud images do not preserve the extended
  attributes, and thus /bin/ping does not work on a system derived from
  them.

  Summary of problem per package:
   * lxc: ubuntu cloud template needs to extract
   * download template needs to extract with xattr flags
   * server side download creation tools need xattr flags
   * [unconfirmed] tarball caches need creation and extraction with xattr flags
   * tar: need the '--xattr' and '--acl' flags backported
   * maas: uec2roottgz needs to use xattr/acl flags
   * curtin: extraction needs to use xattr/acl flags.
   * cloud-image-build: needs to create -root.tar.gz with xattr/acl flags

  Related Bugs:
   * bug 1382632: horizon insecure key file permissions
   * bug 1386237: tar strange behavior with --acl and xattr
   * bug 1313550: ping broken (xattrs lost in tar extraction)

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

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

[Desktop-packages] [Bug 1718719] Re: qemu can't capture keys properly under wayland

2017-09-29 Thread ChristianEhrhardt

So it is likely a wayland <-> SDL thing.
@Desktop Team could you take alook into this - the repro steps in c#2 are 
pretty easy I'd think but none of us would know where in the UI stack to look 
for.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wayland in Ubuntu.
https://bugs.launchpad.net/bugs/1718719

Title:
  qemu can't capture keys properly under wayland

Status in QEMU:
  New
Status in qemu package in Ubuntu:
  New
Status in wayland package in Ubuntu:
  New

Bug description:
  This appears to be different than the previous similar bugs; patches
  do look to be applied to use libinput in the wayland case. Still:

  unknown keycodes `(unnamed)', please report to qemu-de...@nongnu.org

  I am using qemu-system-x86   1:2.10+dfsg-0ubuntu1
  on artful.

  Many key inputs work correctly, but at boot the system will not
  properly catch the arrow keys, the above error shows up immediately
  after hitting Esc (for instance) to get to the boot menu. Booting from
  CD onto a daily Ubuntu desktop image, I can't navigate the splash
  menu.

  The same works correctly through virt-manager (which uses spice
  AFAICT, but wayland tends to crash when running virt-manager), and
  things work if I switch my session to Xorg rather than wayland.

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

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

[Desktop-packages] [Bug 1646786] Re: laptop freezes up on resume from suspension

2016-12-05 Thread ChristianEhrhardt

Hi,
thank you for reporting the bug and your help to make Ubuntu better.

But unfortunately I can't give a generic "thats it" answer to this report.
You'll have to debug your special case so we can understand what happens n your 
case.
You might take a look at this page to guide you to do so 
https://wiki.ubuntu.com/DebuggingKernelSuspend

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

Title:
  laptop freezes up on resume from suspension

Status in pm-utils package in Ubuntu:
  New

Bug description:
  suspended the laptop. However on resume it freezes up, so I have to do a hard 
reset.
  I have tried the option:
  sudo pm-suspend  --quirk-dpms-on
  with some success though, will let you know if it continues to be successful 
or develops freezing again.
  thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pm-utils 1.4.1-16
  ProcVersionSignature: Ubuntu 4.4.0-51.72-generic 4.4.30
  Uname: Linux 4.4.0-51-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Dec  2 10:40:06 2016
  InstallationDate: Installed on 2016-11-30 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1636868] Re: pm-is-supported return 0, but doesn't work

2016-10-27 Thread ChristianEhrhardt

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

I must admit this isn't enough to understand your issue.
- pm-is-supported has options, which one did you check --suspended / 
--hibernate?
- When you shut down are you selecting to suspend/hibernate?
- Depending on your UI that usually is close to logout/shutdown and most 
configure it on lid-close
- I think as command it would be "pm-suspend", but not sure if that is still 
what should be used

It almost appears to me as it just shutdown and made clean fresh boot.
Please provide more info what you did and how your actual issue surfaces.


Since there isn't enough information in your report to differentiate between a 
local configuration problem and a bug in Ubuntu, I'm marking this bug as 
Incomplete.

If indeed this is a local configuration problem, you can find pointers
to get help for this sort of problem here:
http://www.ubuntu.com/support/community

Or if you believe that this is really a bug, then you may find it
helpful to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem,
explain why you believe this is a bug in Ubuntu rather than a problem
specific to your system, and then change the bug status back to New.

** Changed in: pm-utils (Ubuntu)
   Status: New => Incomplete

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

Title:
  pm-is-supported return 0, but doesn't work

Status in pm-utils package in Ubuntu:
  Incomplete

Bug description:
  pm-is-supported return 0, however it doesn't work well:
  PC shuts down and when is started it doesn't reopen programs as at shutdown 
were.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pm-utils 1.4.1-16
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Oct 26 16:03:48 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-10-17 (9 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1667113] Re: Libvirt Qemu appears in the list of users in Ligthdm and user switecher

2017-02-23 Thread ChristianEhrhardt

The user Objects have an attribute for system accounts:
property Boolean SystemAccount
Whether or not the account is a system account, such as adm. System accounts 
aren't returned by ListCachedUsers and should generally be ignored.

It also has a shell property, but that (by default) seems to have no impact on 
listCachedUsers
property String Shell, method SetShell(String path)
The user's login shell.

ListCachedUsers then is what is used by lightdm to fetch the list:
method ListCachedUsers()
returns: users: an array of paths for the user objects
Returns a subset of the users who exist, typically those who have logged in 
recently, for populating chooser lists such as those used by GDM's greeter.
Currently the accountsservice process scans /etc/passwd for users, filters out 
those with UID values which are below a threshold point to screen out system 
users, and sorts the rest by the number of times the users in question appear 
in /var/log/wtmp. Above a certain length, it's expected that the caller will 
disregard the list and present only an entry field. The entry field always 
needs to be available because we know that some results may be missing from 
this list.


Best API def I found so far is from sssd:
https://fedorahosted.org/sssd/wiki/DesignDocs/AccountsService

Call is from lightdm at load_users in common/user-list.c

This can be reproduced more easily by a direct dbus call:
$ dbus-send --print-reply=literal --system --dest=org.freedesktop.Accounts 
/org/freedesktop/Accounts org.freedesktop.Accounts.ListCachedUsers


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

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

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

** Changed in: base-passwd (Ubuntu)
   Status: New => Invalid

** Summary changed:

- Libvirt Qemu appears in the list of users in Ligthdm and user switecher
+ System users appears in Ligthdm and user switcher (Accountsservice has no 
filter for shell types)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to accountsservice 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:
  New
Status in base-passwd package in Ubuntu:
  Invalid
Status in ceph package in Ubuntu:
  Confirmed
Status in libvirt package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  New

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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

2017-02-23 Thread ChristianEhrhardt

So while I understand to unify code paths by relying on accoutnsservice
lightdm needs to get back the feature of "hidden-shells=" IMHO.

So in some sense this is a regression in lightdm due to the change to
use accountsservice.

The solution clearly extceeds my Dbus-foo, but shouldn't lightdm be able
to get back "hidden-shells" by implementing a filter on the "Shell"
property of each user that accountsservice provides?

Maybe this was discussed in the lightdm/accountsservice communities -
I'm not part of them and search engines didn't find it for me - but
given how often the question how to hid users came up I'd think some
discussion on the shell filtering might already exist.

Waiting for the expertise of the triagers of lightdm/accountsservice on
that bug now.

-- 
You received this bug notification because you are a member of Desktop
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:
  New
Status in base-passwd package in Ubuntu:
  Invalid
Status in ceph package in Ubuntu:
  Confirmed
Status in libvirt package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  New

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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

2017-02-24 Thread ChristianEhrhardt

Found more in fidonet and qmail, adding tasks.
But the more that are affected the more I think then general solution in 
lightdm would be the right thing to do.

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

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

** No longer affects: fidogate (Ubuntu)

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

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

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

-- 
You received this bug notification because you are a member of Desktop
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:
  New
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:
  New
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1654662] Re: While in tmpfs mode, cannot connect to wifi access point

2017-02-28 Thread ChristianEhrhardt

I'm not a 100% sure if network-manager is the right package to file this
to, but is certainly is not cloud-initramfs-tools. I hope this now is at
least closer to where it belongs to.

** Package changed: cloud-initramfs-tools (Ubuntu) => network-manager
(Ubuntu)

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

Title:
  While in tmpfs mode, cannot connect to wifi access point

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I have a fresh 16.04 64 bit install. I installed overlayroot.

  In "tmpfs" mode, I cannot connect to wifi access points using the
  network-manager applet.

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

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

[Desktop-packages] [Bug 1663553] Re: crossdomain access denied

2017-02-28 Thread ChristianEhrhardt

Following
https://productforums.google.com/forum/#!topic/chrome/mi1JwnbyDvY - not
sure how much it matches - have you tried with pepperflashplugin-nonfree
as well?

** Package changed: init-system-helpers (Ubuntu) => flashplugin-nonfree
(Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to flashplugin-nonfree in Ubuntu.
https://bugs.launchpad.net/bugs/1663553

Title:
  crossdomain access denied

Status in flashplugin-nonfree package in Ubuntu:
  New

Bug description:
  I'm trying to use http://mywebtv.info with different choices (like
  http://mywebtv.info/nrj-12 )  but always get that error: " Cannot load
  M3U8 Crossdomain access denied " using chromium-browser or midori.

  Find nothing related being logged.
  Sidenote: reported against 'init' but apport change it to 
'init-system-helpers' which seems unrelated; and possibly concern some other 
package(s).

  oem@u64:~$ dpkg --list | grep "^ii" | grep "flash"
  ii  adobe-flash-properties-gtk  1:20170110.1-0ubuntu1 
   amd64GTK+ control panel for Adobe Flash Player plugin
  ii  adobe-flashplugin   1:20170110.1-0ubuntu1 
   amd64Adobe Flash Player plugin
  ii  browser-plugin-freshplayer-pepperflash  0.3.5-1ubuntu4
   amd64PPAPI-host NPAPI-plugin adapter for pepperflash

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: init 1.47
  ProcVersionSignature: Ubuntu 4.9.0-16.17-generic 4.9.6
  Uname: Linux 4.9.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Feb 10 11:42:17 2017
  SourcePackage: init-system-helpers
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1663553] Re: crossdomain access denied

2017-02-28 Thread ChristianEhrhardt

BTW - reassigned from init-system-helpers

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to flashplugin-nonfree in Ubuntu.
https://bugs.launchpad.net/bugs/1663553

Title:
  crossdomain access denied

Status in flashplugin-nonfree package in Ubuntu:
  New

Bug description:
  I'm trying to use http://mywebtv.info with different choices (like
  http://mywebtv.info/nrj-12 )  but always get that error: " Cannot load
  M3U8 Crossdomain access denied " using chromium-browser or midori.

  Find nothing related being logged.
  Sidenote: reported against 'init' but apport change it to 
'init-system-helpers' which seems unrelated; and possibly concern some other 
package(s).

  oem@u64:~$ dpkg --list | grep "^ii" | grep "flash"
  ii  adobe-flash-properties-gtk  1:20170110.1-0ubuntu1 
   amd64GTK+ control panel for Adobe Flash Player plugin
  ii  adobe-flashplugin   1:20170110.1-0ubuntu1 
   amd64Adobe Flash Player plugin
  ii  browser-plugin-freshplayer-pepperflash  0.3.5-1ubuntu4
   amd64PPAPI-host NPAPI-plugin adapter for pepperflash

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: init 1.47
  ProcVersionSignature: Ubuntu 4.9.0-16.17-generic 4.9.6
  Uname: Linux 4.9.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Feb 10 11:42:17 2017
  SourcePackage: init-system-helpers
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1673491] Re: [Zesty] libvirtd Segmentation fault after running virt-manager

2017-03-16 Thread ChristianEhrhardt

Trigger is libvirt (or others following the github issue) but fix would
be in libnl, so adding that.

** Changed in: libnl3 (Ubuntu)
   Importance: Undecided => Critical

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libnl3 in Ubuntu.
https://bugs.launchpad.net/bugs/1673491

Title:
  [Zesty] libvirtd  Segmentation fault after running virt-manager

Status in libnl3 package in Ubuntu:
  New
Status in libvirt package in Ubuntu:
  New

Bug description:
  in Ubuntu 17.04 we can't open a virt-manager, we see sefault

  This issue happen when we update from kernel 4.10.0-9-generic to
  4.10.0-11-generic

  root@:~# /usr/sbin/libvirtd
  Segmentation fault (core dumped)   

  root@:~# gdb /usr/sbin/libvirtd ./core 
  GNU gdb (Ubuntu 7.12.50.20170314-0ubuntu1) 7.12.50.20170314-git
  Copyright (C) 2017 Free Software Foundation, Inc.  
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.   
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"   
  and "show warranty" for details. 
  This GDB was configured as "x86_64-linux-gnu".   
  Type "show configuration" for configuration details. 
  For bug reporting instructions, please see:  
  . 
  Find the GDB manual and other documentation resources online at: 
  .
  For help, type "help".   
  Type "apropos word" to search for commands related to "word"...  
  Reading symbols from /usr/sbin/libvirtd...(no debugging symbols found)...done.
  [New LWP 4232]
  [New LWP 4216]
  [New LWP 4219]
  [New LWP 4218]
  [New LWP 4231]
  [New LWP 4215]
  [New LWP 4220]
  [New LWP 4224]
  [New LWP 4221]
  [New LWP 4223]
  [New LWP 4222]
  [New LWP 4217]
  [New LWP 4225]
  [New LWP 4227]
  [New LWP 4230]
  [New LWP 4229]
  [New LWP 4228]
  [Thread debugging using libthread_db enabled] 
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Core was generated by `/usr/sbin/libvirtd'.   
  Program terminated with signal SIGSEGV, Segmentation fault.   
  #0  0x7f97fa93367f in rtnl_link_sriov_parse_vflist () from 
/usr/lib/x86_64-linux-gnu/libnl-route-3.so.200
  [Current thread is 1 (Thread 0x7f97dff94700 (LWP 4232))]  
   
  (gdb) where   
   
  #0  0x7f97fa93367f in rtnl_link_sriov_parse_vflist () from 
/usr/lib/x86_64-linux-gnu/libnl-route-3.so.200
  #1  0x7f97fa927fad in ?? () from 
/usr/lib/x86_64-linux-gnu/libnl-route-3.so.200  
  #2  0x7f980bfb76c3 in nl_cache_parse () from 
/lib/x86_64-linux-gnu/libnl-3.so.200
  #3  0x7f980bfb770b in ?? () from /lib/x86_64-linux-gnu/libnl-3.so.200 
   
  #4  0x7f980bfbdc1c in nl_recvmsgs_report () from 
/lib/x86_64-linux-gnu/libnl-3.so.200
  #5  0x7f980bfbe049 in nl_recvmsgs () from 
/lib/x86_64-linux-gnu/libnl-3.so.200   
  #6  0x7f980bfb6aab in ?? () from /lib/x86_64-linux-gnu/libnl-3.so.200 
   
  #7  0x7f980bfb763d in nl_cache_pickup () from 
/lib/x86_64-linux-gnu/libnl-3.so.200   
  #8  0x7f980bfb7871 in nl_cache_refill () from 
/lib/x86_64-linux-gnu/l

[Desktop-packages] [Bug 1673491] Re: [Zesty] libvirtd Segmentation fault after running virt-manager

2017-03-16 Thread ChristianEhrhardt

Talat, thank you for your report and also pulling out the github issue
already!

** Tags added: server-next

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libnl3 in Ubuntu.
https://bugs.launchpad.net/bugs/1673491

Title:
  [Zesty] libvirtd  Segmentation fault after running virt-manager

Status in libnl3 package in Ubuntu:
  New
Status in libvirt package in Ubuntu:
  New

Bug description:
  in Ubuntu 17.04 we can't open a virt-manager, we see sefault

  This issue happen when we update from kernel 4.10.0-9-generic to
  4.10.0-11-generic

  root@:~# /usr/sbin/libvirtd
  Segmentation fault (core dumped)   

  root@:~# gdb /usr/sbin/libvirtd ./core 
  GNU gdb (Ubuntu 7.12.50.20170314-0ubuntu1) 7.12.50.20170314-git
  Copyright (C) 2017 Free Software Foundation, Inc.  
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.   
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"   
  and "show warranty" for details. 
  This GDB was configured as "x86_64-linux-gnu".   
  Type "show configuration" for configuration details. 
  For bug reporting instructions, please see:  
  . 
  Find the GDB manual and other documentation resources online at: 
  .
  For help, type "help".   
  Type "apropos word" to search for commands related to "word"...  
  Reading symbols from /usr/sbin/libvirtd...(no debugging symbols found)...done.
  [New LWP 4232]
  [New LWP 4216]
  [New LWP 4219]
  [New LWP 4218]
  [New LWP 4231]
  [New LWP 4215]
  [New LWP 4220]
  [New LWP 4224]
  [New LWP 4221]
  [New LWP 4223]
  [New LWP 4222]
  [New LWP 4217]
  [New LWP 4225]
  [New LWP 4227]
  [New LWP 4230]
  [New LWP 4229]
  [New LWP 4228]
  [Thread debugging using libthread_db enabled] 
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Core was generated by `/usr/sbin/libvirtd'.   
  Program terminated with signal SIGSEGV, Segmentation fault.   
  #0  0x7f97fa93367f in rtnl_link_sriov_parse_vflist () from 
/usr/lib/x86_64-linux-gnu/libnl-route-3.so.200
  [Current thread is 1 (Thread 0x7f97dff94700 (LWP 4232))]  
   
  (gdb) where   
   
  #0  0x7f97fa93367f in rtnl_link_sriov_parse_vflist () from 
/usr/lib/x86_64-linux-gnu/libnl-route-3.so.200
  #1  0x7f97fa927fad in ?? () from 
/usr/lib/x86_64-linux-gnu/libnl-route-3.so.200  
  #2  0x7f980bfb76c3 in nl_cache_parse () from 
/lib/x86_64-linux-gnu/libnl-3.so.200
  #3  0x7f980bfb770b in ?? () from /lib/x86_64-linux-gnu/libnl-3.so.200 
   
  #4  0x7f980bfbdc1c in nl_recvmsgs_report () from 
/lib/x86_64-linux-gnu/libnl-3.so.200
  #5  0x7f980bfbe049 in nl_recvmsgs () from 
/lib/x86_64-linux-gnu/libnl-3.so.200   
  #6  0x7f980bfb6aab in ?? () from /lib/x86_64-linux-gnu/libnl-3.so.200 
   
  #7  0x7f980bfb763d in nl_cache_pickup () from 
/lib/x86_64-linux-gnu/libnl-3.so.200   
  #8  0x7f980bfb7871 in nl_cache_refill () from 
/lib/x86_64-linux-gnu/libnl-3.so.200   
  #9  0x7f97fa926975

[Desktop-packages] [Bug 1673491] Re: [Zesty] libvirtd Segmentation fault after running virt-manager

2017-03-17 Thread ChristianEhrhardt

We are ahead of Debian, so we won't be able to sync a fix atm.
Also I have no upload rights to fully fix it.

The merge has to commits:
*   faf9d90 sriov: merge branch 'sriov-crash-issue126'
| * 20ed636 sriov: avoid buffer overrun in rtnl_link_sriov_parse_vflist()
| * 2d11f40 sriov: fix crash in rtnl_link_sriov_parse_vflist

I prepared a fix that you could test in https://launchpad.net/~ci-train-
ppa-service/+archive/ubuntu/2603

Dep8 tests still running there.
Also I'd like to hear Talats verify on the ppa then it should be considered as 
a zesty fix.

@xnox you did the upload of the base version, do you think you could
take a look and sponsor the bileto ticket if it is appropriate?

** Summary changed:

- [Zesty] libvirtd  Segmentation fault after running virt-manager
+ [Zesty] libnl3 Segmentation fault in sriov environments

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libnl3 in Ubuntu.
https://bugs.launchpad.net/bugs/1673491

Title:
  [Zesty] libnl3 Segmentation fault in sriov environments

Status in libnl3 package in Ubuntu:
  New
Status in libvirt package in Ubuntu:
  New

Bug description:
  in Ubuntu 17.04 we can't open a virt-manager, we see sefault

  This issue happen when we update from kernel 4.10.0-9-generic to
  4.10.0-11-generic

  root@:~# /usr/sbin/libvirtd
  Segmentation fault (core dumped)   

  root@:~# gdb /usr/sbin/libvirtd ./core 
  GNU gdb (Ubuntu 7.12.50.20170314-0ubuntu1) 7.12.50.20170314-git
  Copyright (C) 2017 Free Software Foundation, Inc.  
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.   
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"   
  and "show warranty" for details. 
  This GDB was configured as "x86_64-linux-gnu".   
  Type "show configuration" for configuration details. 
  For bug reporting instructions, please see:  
  . 
  Find the GDB manual and other documentation resources online at: 
  .
  For help, type "help".   
  Type "apropos word" to search for commands related to "word"...  
  Reading symbols from /usr/sbin/libvirtd...(no debugging symbols found)...done.
  [New LWP 4232]
  [New LWP 4216]
  [New LWP 4219]
  [New LWP 4218]
  [New LWP 4231]
  [New LWP 4215]
  [New LWP 4220]
  [New LWP 4224]
  [New LWP 4221]
  [New LWP 4223]
  [New LWP 4222]
  [New LWP 4217]
  [New LWP 4225]
  [New LWP 4227]
  [New LWP 4230]
  [New LWP 4229]
  [New LWP 4228]
  [Thread debugging using libthread_db enabled] 
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Core was generated by `/usr/sbin/libvirtd'.   
  Program terminated with signal SIGSEGV, Segmentation fault.   
  #0  0x7f97fa93367f in rtnl_link_sriov_parse_vflist () from 
/usr/lib/x86_64-linux-gnu/libnl-route-3.so.200
  [Current thread is 1 (Thread 0x7f97dff94700 (LWP 4232))]  
   
  (gdb) where   
   
  #0  0x7f97fa93367f in rtnl_link_sriov_parse_vflist () from 
/usr/lib/x86_64-linux-gnu/libnl-route-3.so.200
  #1  0x7f97fa927fad in ?? () from 
/usr/lib/x86_64-linux-gnu/libnl-route-3.so.200  
  #2  0x7f980bfb76c3 in nl_cache_parse () from 
/lib/x86_64-linux-gnu/libnl-3.so.200

[Desktop-packages] [Bug 1673491] Re: [Zesty] libnl3 Segmentation fault in sriov environments

2017-03-20 Thread ChristianEhrhardt

Dimitri was not available, but I found another sponsor.
Thanks APW!

@Talat if you could finally post if the version that is released is good
as well that would be nice.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libnl3 in Ubuntu.
https://bugs.launchpad.net/bugs/1673491

Title:
  [Zesty] libnl3 Segmentation fault in sriov environments

Status in libnl3 package in Ubuntu:
  Fix Released
Status in libvirt package in Ubuntu:
  New

Bug description:
  in Ubuntu 17.04 we can't open a virt-manager, we see sefault

  This issue happen when we update from kernel 4.10.0-9-generic to
  4.10.0-11-generic

  root@:~# /usr/sbin/libvirtd
  Segmentation fault (core dumped)   

  root@:~# gdb /usr/sbin/libvirtd ./core 
  GNU gdb (Ubuntu 7.12.50.20170314-0ubuntu1) 7.12.50.20170314-git
  Copyright (C) 2017 Free Software Foundation, Inc.  
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.   
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"   
  and "show warranty" for details. 
  This GDB was configured as "x86_64-linux-gnu".   
  Type "show configuration" for configuration details. 
  For bug reporting instructions, please see:  
  . 
  Find the GDB manual and other documentation resources online at: 
  .
  For help, type "help".   
  Type "apropos word" to search for commands related to "word"...  
  Reading symbols from /usr/sbin/libvirtd...(no debugging symbols found)...done.
  [New LWP 4232]
  [New LWP 4216]
  [New LWP 4219]
  [New LWP 4218]
  [New LWP 4231]
  [New LWP 4215]
  [New LWP 4220]
  [New LWP 4224]
  [New LWP 4221]
  [New LWP 4223]
  [New LWP 4222]
  [New LWP 4217]
  [New LWP 4225]
  [New LWP 4227]
  [New LWP 4230]
  [New LWP 4229]
  [New LWP 4228]
  [Thread debugging using libthread_db enabled] 
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Core was generated by `/usr/sbin/libvirtd'.   
  Program terminated with signal SIGSEGV, Segmentation fault.   
  #0  0x7f97fa93367f in rtnl_link_sriov_parse_vflist () from 
/usr/lib/x86_64-linux-gnu/libnl-route-3.so.200
  [Current thread is 1 (Thread 0x7f97dff94700 (LWP 4232))]  
   
  (gdb) where   
   
  #0  0x7f97fa93367f in rtnl_link_sriov_parse_vflist () from 
/usr/lib/x86_64-linux-gnu/libnl-route-3.so.200
  #1  0x7f97fa927fad in ?? () from 
/usr/lib/x86_64-linux-gnu/libnl-route-3.so.200  
  #2  0x7f980bfb76c3 in nl_cache_parse () from 
/lib/x86_64-linux-gnu/libnl-3.so.200
  #3  0x7f980bfb770b in ?? () from /lib/x86_64-linux-gnu/libnl-3.so.200 
   
  #4  0x7f980bfbdc1c in nl_recvmsgs_report () from 
/lib/x86_64-linux-gnu/libnl-3.so.200
  #5  0x7f980bfbe049 in nl_recvmsgs () from 
/lib/x86_64-linux-gnu/libnl-3.so.200   
  #6  0x7f980bfb6aab in ?? () from /lib/x86_64-linux-gnu/libnl-3.so.200 
   
  #7  0x7f980bfb763d in nl_cache_pickup () from 
/lib/x86_64-linux-gnu/libnl-3.so.200   
  #8  0x7f980bfb7871 in nl_cache_refill () from 
/lib/x86_64-linux-gnu/

[Desktop-packages] [Bug 1528735] Re: Suspend fails every second time on some laptops in UEFI mode

2017-03-20 Thread ChristianEhrhardt

So far the only kernel tag with that fix is v4.11-rc1, I haven't seen it being 
sent to stable trees.
Neither were there other platforms added - I see the G70 and S435 in the bug 
here.
You might want to follow the kernel bug link and mention your platoform showing 
the issue there as recommended by Carloslp in comment #23.

Adding a task for the kernel Team to consider a fix.

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

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

Title:
  Suspend fails every second time on some laptops in UEFI mode

Status in kernel-package package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in pm-utils package in Ubuntu:
  Confirmed

Bug description:
  Fresh install of Xubuntu 14.04.3, replacing existing OEM Windows 10.
  Install detected UEFI, and installed in UEFI mode. (I have attempted
  to change to legacy boot, and got it to a state where it was booting
  without /sys/firmware/efi/ being present, but behaviour persisted.)

  Suspending the laptop, whether by closing the lid, choosing the
  suspend option from the menu, or directly typing "sudo pm-suspend"
  works perfectly well... once.

  The second attempt to suspend, whether immediately or hours later,
  suspends the laptop (I can see the screen turn off, and hear the disk
  and fans stop, but a moment later the screen shows bright yellow
  console text declaring "Warning!!! Boot script table modified!!!
  Please contact your vendor.", and then it hard reboots.

  This appears to be a weird interaction between suspend and UEFI
  protection, but others have reported that they have had working
  suspend when installed alone (and presumably in legacy from the
  start), but this behaviour appeared when reinstalled as dual-boot
  (when presumably UEFI would have had to be on).
  (http://askubuntu.com/questions/675683/suspend-does-not-work-more-
  than-once-after-reboot-ubuntu-15-04-dual-boot/712232 and earlier
  http://askubuntu.com/questions/651481/boot-script-table-modified-
  please-contact-vendor, from different people.)

  Beyond the investigations I have done, I know next to nothing about
  UEFI, or how Suspend might be interacting with it. Much less why it
  appears to work perfectly exactly once.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pm-utils 1.4.1-13ubuntu0.1
  ProcVersionSignature: Ubuntu 4.2.0-22.27~14.04.1-generic 4.2.6
  Uname: Linux 4.2.0-22-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Dec 23 13:27:11 2015
  InstallationDate: Installed on 2015-12-19 (3 days ago)
  InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

2017-03-21 Thread ChristianEhrhardt

The suggestion was made to add a accountsservice file for it like:
echo -e "[User]\nSystemAccount=true" > 
/var/lib/AccountsService/users/libvirt-qemu

I agree this might be an option - and I might even be forced to take it at some 
point, but then I ask myself for how many extra Desktop envs/services would we 
make extra files if more are found.
Do we really want to make this a custom change in all those packages (and any 
else in the future who add system users).
- OR -
Wouldn't it make much much more sense to make accountsservice realize on non 
login shells as all other logins seem to do (e.g. sddm) and as itself did in 
the past (hidden-shells)?

-- 
You received this bug notification because you are a member of Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

2017-03-22 Thread ChristianEhrhardt

After some IRC discussions I'm increasing prio in accountsservice as
more people are convinced this is the place to fix it and it seems to
get a rise in "popularity".

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to accountsservice 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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1548486] Re: Sleep hook in a subdirectory ignored but causes double execution of previous hook

Given the slow (=no) movement of upstream we should expect the Delta to be a 
long term one.
That combined with the fact that this bug is present in Debian too, and Ubuntu 
currently doesn't make any changes over the Debian package. So this bug would 
be best fixed directly in Debian, and then Ubuntu will pick up the fix 
automatically.

** Also affects: pm-utils via
   https://bugs.freedesktop.org/show_bug.cgi?id=94323
   Importance: Unknown
   Status: Unknown

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

Title:
  Sleep hook in a subdirectory ignored but causes double execution of
  previous hook

Status in pm-utils:
  Unknown
Status in pm-utils package in Ubuntu:
  Confirmed

Bug description:
  The set of sleep hooks provided in /usr/lib/pm-utils/sleep.d includes
  one (95packagekit/95packagekit) that is stored in a subdirectory. This
  has two effects:

  1the hook is not run;

  2the previous hook, currently /usr/lib/pm-utils/sleep.d/95led, is
  run for a second time instead.

  Presumably #1 is wrong, and results from an installation fault in
  packagekit,  separately reported as bug 1548480.

  #2 occurs because the function run_hooks() in /usr/lib/pm-utils/pm-
  functions computes a list of to-be-executed hooks that includes
  directories but neither fully validates each such hook as a regular
  file nor handles a set of to-be-executed hooks in a subdirectory.

  At lines 243 on, there is  a code path with no else clause through
  which the $hook from the previous iteration can be accidentally
  reused:

if [ -f "$syshooks/$base" ]; then
hook="$syshooks/$base"
elif [ -f "$phooks/$base" ]; then
hook="$phooks/$base"
fi

  An easy fix is to insert the missing else clause before the fi line so
  that the script skips the subdirectory or other non-regular file and
  carries on with the next correctly specified hook:

if [ -f "$syshooks/$base" ]; then
hook="$syshooks/$base"
elif [ -f "$phooks/$base" ]; then
hook="$phooks/$base"
else 
continue
fi

  Observed in Lubuntu 14.04.3,4 with pm-utils 1.4.1-13ubuntu0.1,2.
  However the relevant pm-utils code dates back to 2008, pm-utils
  upstream version 1.1.0.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pm-utils 1.4.1-13ubuntu0.2 [modified: usr/lib/pm-utils/pm-functions]
  ProcVersionSignature: Ubuntu 4.2.0-29.34~14.04.1-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-29-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  Date: Mon Feb 22 17:10:53 2016
  InstallationDate: Installed on 2016-02-21 (0 days ago)
  InstallationMedia: Lubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 
(20160217.1)
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/pm-utils/+bug/1548486/+subscriptions

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

[Desktop-packages] [Bug 1548486] Re: Sleep hook in a subdirectory ignored but causes double execution of previous hook

While not a totally critical bug it is sad that upstream did not respond at all 
yet which I guess everyone here was waiting for as well which made nothing move 
at all :-/.
At this point it might be worth considering to take that as a delta - 
subscribing a few to hope one finds time to pick it up.

If you want you might ping on the upstream bug once more.

** Changed in: pm-utils (Ubuntu)
   Status: New => Confirmed

** Changed in: pm-utils (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Sleep hook in a subdirectory ignored but causes double execution of
  previous hook

Status in pm-utils:
  Unknown
Status in pm-utils package in Ubuntu:
  Confirmed

Bug description:
  The set of sleep hooks provided in /usr/lib/pm-utils/sleep.d includes
  one (95packagekit/95packagekit) that is stored in a subdirectory. This
  has two effects:

  1the hook is not run;

  2the previous hook, currently /usr/lib/pm-utils/sleep.d/95led, is
  run for a second time instead.

  Presumably #1 is wrong, and results from an installation fault in
  packagekit,  separately reported as bug 1548480.

  #2 occurs because the function run_hooks() in /usr/lib/pm-utils/pm-
  functions computes a list of to-be-executed hooks that includes
  directories but neither fully validates each such hook as a regular
  file nor handles a set of to-be-executed hooks in a subdirectory.

  At lines 243 on, there is  a code path with no else clause through
  which the $hook from the previous iteration can be accidentally
  reused:

if [ -f "$syshooks/$base" ]; then
hook="$syshooks/$base"
elif [ -f "$phooks/$base" ]; then
hook="$phooks/$base"
fi

  An easy fix is to insert the missing else clause before the fi line so
  that the script skips the subdirectory or other non-regular file and
  carries on with the next correctly specified hook:

if [ -f "$syshooks/$base" ]; then
hook="$syshooks/$base"
elif [ -f "$phooks/$base" ]; then
hook="$phooks/$base"
else 
continue
fi

  Observed in Lubuntu 14.04.3,4 with pm-utils 1.4.1-13ubuntu0.1,2.
  However the relevant pm-utils code dates back to 2008, pm-utils
  upstream version 1.1.0.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pm-utils 1.4.1-13ubuntu0.2 [modified: usr/lib/pm-utils/pm-functions]
  ProcVersionSignature: Ubuntu 4.2.0-29.34~14.04.1-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-29-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  Date: Mon Feb 22 17:10:53 2016
  InstallationDate: Installed on 2016-02-21 (0 days ago)
  InstallationMedia: Lubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 
(20160217.1)
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/pm-utils/+bug/1548486/+subscriptions

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

[Desktop-packages] [Bug 1548486] Re: Sleep hook in a subdirectory ignored but causes double execution of previous hook

I linked up the upstream bug here for now

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

Title:
  Sleep hook in a subdirectory ignored but causes double execution of
  previous hook

Status in pm-utils:
  Unknown
Status in pm-utils package in Ubuntu:
  Confirmed

Bug description:
  The set of sleep hooks provided in /usr/lib/pm-utils/sleep.d includes
  one (95packagekit/95packagekit) that is stored in a subdirectory. This
  has two effects:

  1the hook is not run;

  2the previous hook, currently /usr/lib/pm-utils/sleep.d/95led, is
  run for a second time instead.

  Presumably #1 is wrong, and results from an installation fault in
  packagekit,  separately reported as bug 1548480.

  #2 occurs because the function run_hooks() in /usr/lib/pm-utils/pm-
  functions computes a list of to-be-executed hooks that includes
  directories but neither fully validates each such hook as a regular
  file nor handles a set of to-be-executed hooks in a subdirectory.

  At lines 243 on, there is  a code path with no else clause through
  which the $hook from the previous iteration can be accidentally
  reused:

if [ -f "$syshooks/$base" ]; then
hook="$syshooks/$base"
elif [ -f "$phooks/$base" ]; then
hook="$phooks/$base"
fi

  An easy fix is to insert the missing else clause before the fi line so
  that the script skips the subdirectory or other non-regular file and
  carries on with the next correctly specified hook:

if [ -f "$syshooks/$base" ]; then
hook="$syshooks/$base"
elif [ -f "$phooks/$base" ]; then
hook="$phooks/$base"
else 
continue
fi

  Observed in Lubuntu 14.04.3,4 with pm-utils 1.4.1-13ubuntu0.1,2.
  However the relevant pm-utils code dates back to 2008, pm-utils
  upstream version 1.1.0.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pm-utils 1.4.1-13ubuntu0.2 [modified: usr/lib/pm-utils/pm-functions]
  ProcVersionSignature: Ubuntu 4.2.0-29.34~14.04.1-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-29-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  Date: Mon Feb 22 17:10:53 2016
  InstallationDate: Installed on 2016-02-21 (0 days ago)
  InstallationMedia: Lubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 
(20160217.1)
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/pm-utils/+bug/1548486/+subscriptions

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

[Desktop-packages] [Bug 1548853] Re: 00powersave sleep hook misses claimed patch

This is the second bug I've seen from you and I feel embarrassed that
nobody looked at them yet, Iso I wanted to beg a pardon and thank you
for your work.

To fix this it would mean backporting 
debian/patches/16-no-powersave-before-suspend.patch for an SRU.
Not complex to but somewhat discussion worthy if the effect is worth an SRU.

The fix documents this as:
"do not run pm-powersave on ARM during suspend; the 1.5 seconds that it takes 
to run it don't nearly compensate the potentially slightly slower suspend 
operation in low power mode"

Fixed in 1.4.1-14 so everything >=Vivid is good.

** Changed in: pm-utils (Ubuntu)
   Status: New => Triaged

** Changed in: pm-utils (Ubuntu)
   Importance: Undecided => Low

** Tags removed: package-from-proposed
** Tags added: bitesize patch

** Changed in: pm-utils (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  00powersave sleep hook misses claimed patch

Status in pm-utils package in Ubuntu:
  Fix Released

Bug description:
  The pm-utils sleep hook installed at /usr/lib/pm-
  utils/sleep.d/00powersave was supposed to have been patched to prevent
  it running on ARM architectures. However a new case was added without
  deleting the preceding existing one (lines 12 on):

  case $1 in
  suspend|hibernate) pm-powersave false ;;
  suspend|hibernate) [ "$ARCH" != "${ARCH#arm}" ] || pm-powersave false ;;
  resume|thaw)   pm-powersave ;;
  *) exit $NA ;;
  esac

  Observed in and affects 14.04.3,4.; seems to be OK in 14.10-15.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pm-utils 1.4.1-13ubuntu0.2 [modified: usr/lib/pm-utils/pm-functions]
  ProcVersionSignature: Ubuntu 4.2.0-29.34~14.04.1-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-29-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  Date: Tue Feb 23 13:51:14 2016
  InstallationDate: Installed on 2016-02-21 (1 days ago)
  InstallationMedia: Lubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 
(20160217.1)
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1664478] [NEW] New upstream microreleases 9.3.16, 9.5.6

2017-02-14 Thread ChristianEhrhardt

Public bug reported:

https://www.postgresql.org/about/news/1733/

As per the standing micro-release exception these should land in stable
Ubuntu releases.

** Affects: postgresql-9.3 (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: postgresql-9.5 (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: postgresql-9.3 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: postgresql-9.5 (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: postgresql-9.1 (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to postgresql-9.1 in Ubuntu.
https://bugs.launchpad.net/bugs/1664478

Title:
  New upstream microreleases 9.3.16, 9.5.6

Status in postgresql-9.3 package in Ubuntu:
  New
Status in postgresql-9.5 package in Ubuntu:
  New

Bug description:
  https://www.postgresql.org/about/news/1733/

  As per the standing micro-release exception these should land in
  stable Ubuntu releases.

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

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

[Desktop-packages] [Bug 1675683] Re: Computer sluggish/irresponsive for several minutes after hibernation

Thanks YS1 for your check.
There is no clear error in the messages, so it is down trying to log what 
activity goes on while it is waking up.

Chances are that the things we set up are too sluggish as well and only start 
to report after we unfrozen far enough, yet it is worth a try.
You could run things like 

$ sar -A -I XALL 1 > freezeslow.sar
$ dstat -tvins --top-io-adv --top-bio-adv --top-latency 1 > freezeslow.dstat
$ iostat -xtdk 1 > freezeslow.iostat

Then suspend restore and the processes should wake up and log again.
With some luck (before going much deeper on debugging suspend) we can catch 
something that makes things worse in your case.

** Changed in: pm-utils (Ubuntu)
   Status: New => Incomplete

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

Title:
  Computer sluggish/irresponsive for several minutes after hibernation

Status in pm-utils package in Ubuntu:
  Incomplete

Bug description:
  Hi,
  my computer is very sluggish for a good five minutes after thawing from 
hibernation.

  Booting the system and the thawing process in itself seems to run fine
  : the console displays the progress of reloading contents into RAM at
  a satisfying pace, then the lightdm unlock interface displays.

  From this point on, things become strange : the computer has an
  constant and intense hard drive activity and applications do not
  respond to input in a swift manner (moving the mouse cursor works in
  "real time" though, and the clock, which displays seconds, also works
  almost normally).

  This reminds me of what happens when you set focus back to an
  application that had been paged to swap : it is irresponsive until it
  is back in RAM. Except this happens for all applications at once.

  This stops after several minutes (more than five) and the computer
  becomes usable again.

  I experienced the problem today again. The current RAM usage is 7.2
  Gio / 15.6 Gio and swap usage is 4.2 Gio / 31.3 Gio.

  Main memory usage is :
  firefox 3.4 Gio
  firefox (other instance) 1.7 Gio
  thunderbird 624 Mio
  xfwm4 213 Mio

  Hibernation with TuxOnIce did not induce this problem (I am not using
  it currently due to mismanagement of video drivers).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pm-utils 1.4.1-16
  ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49
  Uname: Linux 4.4.0-67-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 24 09:20:15 2017
  InstallationDate: Installed on 2016-09-07 (197 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1675683] Re: Computer sluggish/irresponsive for several minutes after hibernation

I found [1] which might help going deeper into this case if needed.
But also [2] which might be a solution for your issue right away.

[1]: 
https://01.org/blogs/rzhang/2015/best-practice-debug-linux-suspend/hibernate-issues
[2]: 
https://askubuntu.com/questions/792605/ubuntu-16-04-lts-too-slow-after-suspend-and-resume

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

Title:
  Computer sluggish/irresponsive for several minutes after hibernation

Status in pm-utils package in Ubuntu:
  Incomplete

Bug description:
  Hi,
  my computer is very sluggish for a good five minutes after thawing from 
hibernation.

  Booting the system and the thawing process in itself seems to run fine
  : the console displays the progress of reloading contents into RAM at
  a satisfying pace, then the lightdm unlock interface displays.

  From this point on, things become strange : the computer has an
  constant and intense hard drive activity and applications do not
  respond to input in a swift manner (moving the mouse cursor works in
  "real time" though, and the clock, which displays seconds, also works
  almost normally).

  This reminds me of what happens when you set focus back to an
  application that had been paged to swap : it is irresponsive until it
  is back in RAM. Except this happens for all applications at once.

  This stops after several minutes (more than five) and the computer
  becomes usable again.

  I experienced the problem today again. The current RAM usage is 7.2
  Gio / 15.6 Gio and swap usage is 4.2 Gio / 31.3 Gio.

  Main memory usage is :
  firefox 3.4 Gio
  firefox (other instance) 1.7 Gio
  thunderbird 624 Mio
  xfwm4 213 Mio

  Hibernation with TuxOnIce did not induce this problem (I am not using
  it currently due to mismanagement of video drivers).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pm-utils 1.4.1-16
  ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49
  Uname: Linux 4.4.0-67-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 24 09:20:15 2017
  InstallationDate: Installed on 2016-09-07 (197 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1685387] Re: Suspending machine takes too long

With the current information there isn't enough to debug/help more -
setting incomplete for now.

** Changed in: pm-utils (Ubuntu)
   Status: New => Incomplete

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

Title:
  Suspending machine takes too long

Status in pm-utils package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu 16.04 and Ubuntu 16.10

  2) pm-utils 1.4.1-16

  3) I expect the machine to suspend without delay. On Ubuntu 15.10 the
  my machine used to suspend in 1-2 seconds.

  4) It takes over 10 seconds before the machine is suspended.

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

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

[Desktop-packages] [Bug 1685387] Re: Suspending machine takes too long

Usually hooks are called to let everybody suspend, maybe in the Mate
environment there are others active that slow things down?

Maybe debugging along [1] can help to spot the issue in more detail.

In general you'd want to try to track down what activity is running
while this unexpected delay is going on. Since everything is freezing at
that point you will have to setup logs to go to file and pick them up
after resume.

[1]: https://01.org/blogs/rzhang/2015/best-practice-debug-linux-suspend
/hibernate-issues

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

Title:
  Suspending machine takes too long

Status in pm-utils package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu 16.04 and Ubuntu 16.10

  2) pm-utils 1.4.1-16

  3) I expect the machine to suspend without delay. On Ubuntu 15.10 the
  my machine used to suspend in 1-2 seconds.

  4) It takes over 10 seconds before the machine is suspended.

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

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

[Desktop-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 Desktop
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1548486] Re: Sleep hook in a subdirectory ignored but causes double execution of previous hook

2017-07-14 Thread ChristianEhrhardt

I revisit dormant bugs on a regular scheduling following our triaging policy.
It seems nothing happened upstream still.

For the Debian reporting you can do so through the mail interface - you don't 
need a Debian system.
Usually it is preferred that the reporter does so, but if you need help or want 
me to do that please ping here and I'll do so.

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

Title:
  Sleep hook in a subdirectory ignored but causes double execution of
  previous hook

Status in pm-utils:
  Unknown
Status in pm-utils package in Ubuntu:
  Confirmed

Bug description:
  The set of sleep hooks provided in /usr/lib/pm-utils/sleep.d includes
  one (95packagekit/95packagekit) that is stored in a subdirectory. This
  has two effects:

  1the hook is not run;

  2the previous hook, currently /usr/lib/pm-utils/sleep.d/95led, is
  run for a second time instead.

  Presumably #1 is wrong, and results from an installation fault in
  packagekit,  separately reported as bug 1548480.

  #2 occurs because the function run_hooks() in /usr/lib/pm-utils/pm-
  functions computes a list of to-be-executed hooks that includes
  directories but neither fully validates each such hook as a regular
  file nor handles a set of to-be-executed hooks in a subdirectory.

  At lines 243 on, there is  a code path with no else clause through
  which the $hook from the previous iteration can be accidentally
  reused:

if [ -f "$syshooks/$base" ]; then
hook="$syshooks/$base"
elif [ -f "$phooks/$base" ]; then
hook="$phooks/$base"
fi

  An easy fix is to insert the missing else clause before the fi line so
  that the script skips the subdirectory or other non-regular file and
  carries on with the next correctly specified hook:

if [ -f "$syshooks/$base" ]; then
hook="$syshooks/$base"
elif [ -f "$phooks/$base" ]; then
hook="$phooks/$base"
else 
continue
fi

  Observed in Lubuntu 14.04.3,4 with pm-utils 1.4.1-13ubuntu0.1,2.
  However the relevant pm-utils code dates back to 2008, pm-utils
  upstream version 1.1.0.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pm-utils 1.4.1-13ubuntu0.2 [modified: usr/lib/pm-utils/pm-functions]
  ProcVersionSignature: Ubuntu 4.2.0-29.34~14.04.1-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-29-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  Date: Mon Feb 22 17:10:53 2016
  InstallationDate: Installed on 2016-02-21 (0 days ago)
  InstallationMedia: Lubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 
(20160217.1)
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/pm-utils/+bug/1548486/+subscriptions

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

[Desktop-packages] [Bug 1679435] Re: GNOME Software fails to install .deb packages that trigger debconf prompts

2017-07-19 Thread ChristianEhrhardt

** Tags added: triage

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1679435

Title:
  GNOME Software fails to install .deb packages that trigger debconf
  prompts

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Released
Status in gnome-software source package in Yakkety:
  Fix Released
Status in gnome-software source package in Zesty:
  Fix Released
Status in gnome-software source package in Artful:
  Fix Released

Bug description:
  [Impact]
  GNOME Software doesn't provide debconf support when using aptd. This means 
any package installation / upgrade that triggers a debconf prompt can fail. The 
requested package might not do a prompt, but some dependency can.

  [Test Case]
  1. Install a .deb file that causes a debconf prompt 
(https://launchpad.net/~vorlon/+archive/ubuntu/debconf-tests contains a test 
package).
  $ gnome-software --local-filename=noisy-fake-driver_0.6_amd64.deb

  Expected result:
  Package is installed after a debconf prompt is shown.

  Observed result:
  Package fails to install, no prompt is shown.

  [Regression Potential]
  The solution was to provide a pipe when using aptd to allow the debconf 
prompt to be handled in the session. This could introduce new bugs and/or 
security issues.

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

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

[Desktop-packages] [Bug 1705551] Re: close lid suspends correctly and wakealarm resumes from suspend to run cron jobs but opening lid reveals no display

2017-07-21 Thread ChristianEhrhardt

Hi,
you said "all sorts of keyboard combinations" but maybe it is worth a try. I 
had a similar case where it actually enabled the display, but at brightness 0 - 
you might not accidentally have the same case? I could get it on by using the 
FN keys to increase brightness in those cases.

Another question would be if you never close the lid, but suspend via SW.
And next day you wakeup via the alarm (while the lid was still open when 
sleeping) - is it then waking up normally with display enabled?

Finally - I beg your pardon as I'm not an expert on this - but the following 
could enable it.
You might need tweaks to actually "reach" your xorg, but I'm sure you can do 
that. Once you did call:
 $ xset dpms force off
That should disable the power saving blank that your screen is in.

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

Title:
  close lid suspends correctly and wakealarm resumes from suspend to run
  cron jobs but opening lid reveals no display

Status in pm-utils package in Ubuntu:
  Incomplete

Bug description:
  [Problem]

  When I close the laptop lid, pm-action runs the following code which I
  have added:

  sh -c "echo 0 > /sys/class/rtc/rtc0/wakealarm" # clear alarm
  sh -c "echo `date '+%s' -d '7am next day + 30 minutes'` > 
/sys/class/rtc/rtc0/wakealarm" # set alarm

  and then suspends. At 7:30 AM the next day, the laptop resumes from
  suspend with the lid closed and executes cron jobs (e.g. some
  backups). If I open the lid then there is no display. I tried several
  options to resume the display:

  - [FAILS] all sorts of keyboard combinations
  - [FAILS] ssh -X into laptop and execute "sudo -u bierre env DISPLAY=:0 
/usr/bin/xrandr --auto" (n.b. when I run "sudo -u bierre env" there is no 
DISPLAY variable)
  - [MANUAL HACK] closing the lid causes the laptop to suspend and then opening 
the lid causes it to resume with a normal working display

  I would like a solution or SOFTWARE HACK which I could add to /usr/lib
  /pm-utils/sleep.d/99video during resume from suspend triggered by
  wakealarm so that opening the lid would reveal a working display.

  [Laptop System Information]

  laptop = MacBookPro5,5
  pm-utils version = 1.4.1-13ubuntu0.2
  kernel = Linux version 3.19.0-32-generic (buildd@lgw01-43) (gcc version 4.8.2 
(Ubuntu 4.8.2-19ubuntu1) ) #37~14.04.1-Ubuntu SMP Thu Oct 22 09:41:40 UTC 2015
  OS = "Linux Mint 17.3 Rosa" based on "14.04.3 LTS, Trusty Tahr"
  desktop environment = XFCE
  video card = NVIDIA Corporation C79 [GeForce 9400M] (rev b1) (prog-if 00 [VGA 
controller])
  video driver = [633938.944] (II) NOUVEAU(0): Output LVDS-1

  [Additional Information]

  After my cron backup job is finished it will check if the lid is
  closed. If it is closed then it will run pm-suspend. If I then open
  the lid, the laptop resumes with a normal working display. So the
  problem of no visible display occurs only when I open the lid after
  resume from wakealarm and before the backup job suspends the laptop.

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

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

[Desktop-packages] [Bug 1705551] Re: close lid suspends correctly and wakealarm resumes from suspend to run cron jobs but opening lid reveals no display

2017-07-21 Thread ChristianEhrhardt

incomplete - waiting for more feedback

** Changed in: pm-utils (Ubuntu)
   Status: New => Incomplete

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

Title:
  close lid suspends correctly and wakealarm resumes from suspend to run
  cron jobs but opening lid reveals no display

Status in pm-utils package in Ubuntu:
  Incomplete

Bug description:
  [Problem]

  When I close the laptop lid, pm-action runs the following code which I
  have added:

  sh -c "echo 0 > /sys/class/rtc/rtc0/wakealarm" # clear alarm
  sh -c "echo `date '+%s' -d '7am next day + 30 minutes'` > 
/sys/class/rtc/rtc0/wakealarm" # set alarm

  and then suspends. At 7:30 AM the next day, the laptop resumes from
  suspend with the lid closed and executes cron jobs (e.g. some
  backups). If I open the lid then there is no display. I tried several
  options to resume the display:

  - [FAILS] all sorts of keyboard combinations
  - [FAILS] ssh -X into laptop and execute "sudo -u bierre env DISPLAY=:0 
/usr/bin/xrandr --auto" (n.b. when I run "sudo -u bierre env" there is no 
DISPLAY variable)
  - [MANUAL HACK] closing the lid causes the laptop to suspend and then opening 
the lid causes it to resume with a normal working display

  I would like a solution or SOFTWARE HACK which I could add to /usr/lib
  /pm-utils/sleep.d/99video during resume from suspend triggered by
  wakealarm so that opening the lid would reveal a working display.

  [Laptop System Information]

  laptop = MacBookPro5,5
  pm-utils version = 1.4.1-13ubuntu0.2
  kernel = Linux version 3.19.0-32-generic (buildd@lgw01-43) (gcc version 4.8.2 
(Ubuntu 4.8.2-19ubuntu1) ) #37~14.04.1-Ubuntu SMP Thu Oct 22 09:41:40 UTC 2015
  OS = "Linux Mint 17.3 Rosa" based on "14.04.3 LTS, Trusty Tahr"
  desktop environment = XFCE
  video card = NVIDIA Corporation C79 [GeForce 9400M] (rev b1) (prog-if 00 [VGA 
controller])
  video driver = [633938.944] (II) NOUVEAU(0): Output LVDS-1

  [Additional Information]

  After my cron backup job is finished it will check if the lid is
  closed. If it is closed then it will run pm-suspend. If I then open
  the lid, the laptop resumes with a normal working display. So the
  problem of no visible display occurs only when I open the lid after
  resume from wakealarm and before the backup job suspends the laptop.

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

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

[Desktop-packages] [Bug 1688364] Re: Non existent host causes 100% cpu utilization by systemd-resolved and dnsmasq

2017-05-09 Thread ChristianEhrhardt

Hi,
ok so you don't have an .dhclient that provides your dns resolution 
as provided by dhcp.
Furthermore I see you have a networkmanager config while I have none.

Networkmanager is not in use on Ubuntu Server, but on Desktop. So I
assume you are running a [ULK..]Ubuntu Desktop edition while running
into this issue?

Also just to confirm your system gets its IP and DNS infos via dhcp is that 
correct?
I assume that in your case somehow network manager is soaking that up which 
leads to the issue of dnsmasq not being able to find the info when starting up.

This more and more leaves my area of expertise :-/
Adding a networkmanager task as well for now.

** Also affects: network-manager (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Non existent host causes 100% cpu utilization by systemd-resolved and
  dnsmasq

Status in dnsmasq package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New

Bug description:
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 can

[Desktop-packages] [Bug 1688364] Re: Non existent host causes 100% cpu utilization by systemd-resolved and dnsmasq

2017-05-09 Thread ChristianEhrhardt

As a temporary workaround until this gets proper handling/fix you might 
(depending on preference and on how static or not your config is):
a) switch back from resolved to dnsmasq as described in [1], you need to follow 
both answers since you are also running Network Manager
b) set your DNS address in a file in /etc/resolvconf/resolv.conf.d/
c) we understand why/how NetworkManager is stopping/avoiding dhclient to place 
the info as it had doen for me in /run/resolvconf/interface/eth0.dhclient and 
fix that. The update hook should be /etc/dhcp/dhclient-enter-hooks.d/resolvconf


[1]: 
https://askubuntu.com/questions/898605/how-to-disable-systemd-resolved-and-resolve-dns-with-dnsmasq

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

Title:
  Non existent host causes 100% cpu utilization by systemd-resolved and
  dnsmasq

Status in dnsmasq package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New

Bug description:
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.co

[Desktop-packages] [Bug 1641919] Re: hibernation has stopped working in 16.10 Yakkety Yak

2017-05-19 Thread ChristianEhrhardt

@mprotic - be careful
xserver-xorg-video-nouveau is the Xorg driver for it
While the kernel module you unload is from linux-image-extra

None of it is safe to uninstall, the former will due to dependencies take xorg 
away and the latter holds much more kernel modules.
If you have a setup without nouveau at all and want to avoid it loading you 
should follow [1].

[1]: https://wiki.debian.org/KernelModuleBlacklisting

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

Title:
  hibernation has stopped working in 16.10 Yakkety Yak

Status in nouveau-firmware package in Ubuntu:
  Confirmed
Status in pm-utils package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 16.10 (from 16.04) hibernation has stopped working.
  I've been using hibernation for years already without problems (with
  some initial tuning).

  I am talking about using "pm-hibernate"

  There is a workaround to make it work I've described here:
  http://askubuntu.com/a/849679/208566

  Also, there are some warnings while updating initramfs, which had not been 
present before:
  
  sudo update-initramfs -u
  update-initramfs: Generating /boot/initrd.img-4.8.0-27-generic
  W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for 
module i915
  W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin for module 
i915
  

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: ubuntu-release-upgrader-core 1:16.10.8
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: XFCE
  Date: Tue Nov 15 12:19:19 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-11-06 (374 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to yakkety on 2016-11-12 (3 days ago)
  VarLogDistupgradeTermlog:

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

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

[Desktop-packages] [Bug 1536204] Re: alsa-utils conflicts with bareos-bat

2017-06-09 Thread ChristianEhrhardt

I came by cleaning up long time dormant bugs, this is actually already
fixed in 1.1.0-2 and thereby >=Yakkety.

** Changed in: alsa-utils (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1536204

Title:
  alsa-utils conflicts with bareos-bat

Status in alsa-utils package in Ubuntu:
  Fix Released
Status in bacula package in Ubuntu:
  Invalid
Status in bareos package in Ubuntu:
  Invalid
Status in alsa-utils package in Debian:
  Fix Released

Bug description:
  dcarbone@paperone:~$ sudo aptitude install bareos-bconsole bareos-bat 
bareos-client bareos-tools
  bareos-bconsole è già installato e si trova alla versione richiesta (14.2.6-2)
  bareos-client è già installato e si trova alla versione richiesta (14.2.6-2)
  bareos-tools è già installato e si trova alla versione richiesta (14.2.6-2)
  bareos-bconsole è già installato e si trova alla versione richiesta (14.2.6-2)
  bareos-client è già installato e si trova alla versione richiesta (14.2.6-2)
  bareos-tools è già installato e si trova alla versione richiesta (14.2.6-2)
  I seguenti pacchetti NUOVI (NEW) saranno installati:
bareos-bat 
  0 pacchetti aggiornati, 1 installati, 0 da rimuovere e 0 non aggiornati.
  È necessario prelevare 0 B/508 kB di archivi. Dopo l'estrazione, verranno 
occupati 1.554 kB.
  (Lettura del database... 214782 file e directory attualmente installati.)
  Preparativi per estrarre .../bareos-bat_14.2.6-2_amd64.deb...
  Estrazione di bareos-bat (14.2.6-2)...
  dpkg: errore nell'elaborare l'archivio 
/var/cache/apt/archives/bareos-bat_14.2.6-2_amd64.deb (--unpack):
   tentata sovrascrittura di "/usr/share/man/man1/bat.1.gz" presente anche nel 
pacchetto alsa-utils 1.1.0-0ubuntu2
  dpkg-deb: errore: il sottoprocesso paste è stato terminato dal segnale (Pipe 
interrotta)
  Elaborazione dei trigger per doc-base (0.10.6)...
  Elaborazione dei trigger per man-db (2.7.5-1)...
  Si sono verificati degli errori nell'elaborazione:
   /var/cache/apt/archives/bareos-bat_14.2.6-2_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  Failed to perform requested operation on package.  Trying to recover:

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

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

[Desktop-packages] [Bug 1536204] Re: alsa-utils conflicts with bareos-bat

2017-06-09 Thread ChristianEhrhardt

The conflict only needs to be resolved on one side, so by alsa-utils
being fixed the others are now "invalid"

** Changed in: bacula (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: bareos (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1536204

Title:
  alsa-utils conflicts with bareos-bat

Status in alsa-utils package in Ubuntu:
  Fix Released
Status in bacula package in Ubuntu:
  Invalid
Status in bareos package in Ubuntu:
  Invalid
Status in alsa-utils package in Debian:
  Fix Released

Bug description:
  dcarbone@paperone:~$ sudo aptitude install bareos-bconsole bareos-bat 
bareos-client bareos-tools
  bareos-bconsole è già installato e si trova alla versione richiesta (14.2.6-2)
  bareos-client è già installato e si trova alla versione richiesta (14.2.6-2)
  bareos-tools è già installato e si trova alla versione richiesta (14.2.6-2)
  bareos-bconsole è già installato e si trova alla versione richiesta (14.2.6-2)
  bareos-client è già installato e si trova alla versione richiesta (14.2.6-2)
  bareos-tools è già installato e si trova alla versione richiesta (14.2.6-2)
  I seguenti pacchetti NUOVI (NEW) saranno installati:
bareos-bat 
  0 pacchetti aggiornati, 1 installati, 0 da rimuovere e 0 non aggiornati.
  È necessario prelevare 0 B/508 kB di archivi. Dopo l'estrazione, verranno 
occupati 1.554 kB.
  (Lettura del database... 214782 file e directory attualmente installati.)
  Preparativi per estrarre .../bareos-bat_14.2.6-2_amd64.deb...
  Estrazione di bareos-bat (14.2.6-2)...
  dpkg: errore nell'elaborare l'archivio 
/var/cache/apt/archives/bareos-bat_14.2.6-2_amd64.deb (--unpack):
   tentata sovrascrittura di "/usr/share/man/man1/bat.1.gz" presente anche nel 
pacchetto alsa-utils 1.1.0-0ubuntu2
  dpkg-deb: errore: il sottoprocesso paste è stato terminato dal segnale (Pipe 
interrotta)
  Elaborazione dei trigger per doc-base (0.10.6)...
  Elaborazione dei trigger per man-db (2.7.5-1)...
  Si sono verificati degli errori nell'elaborazione:
   /var/cache/apt/archives/bareos-bat_14.2.6-2_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  Failed to perform requested operation on package.  Trying to recover:

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

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

[Desktop-packages] [Bug 1673491] Re: [Zesty] libnl3 Segmentation fault in sriov environments

2017-06-13 Thread ChristianEhrhardt

Since libvirt was only the trigger, taking that off the tasks here.

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

** Tags removed: server-next

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libnl3 in Ubuntu.
https://bugs.launchpad.net/bugs/1673491

Title:
  [Zesty] libnl3 Segmentation fault in sriov environments

Status in libnl3 package in Ubuntu:
  Fix Released
Status in libvirt package in Ubuntu:
  Invalid

Bug description:
  in Ubuntu 17.04 we can't open a virt-manager, we see sefault

  This issue happen when we update from kernel 4.10.0-9-generic to
  4.10.0-11-generic

  root@:~# /usr/sbin/libvirtd
  Segmentation fault (core dumped)   

  root@:~# gdb /usr/sbin/libvirtd ./core 
  GNU gdb (Ubuntu 7.12.50.20170314-0ubuntu1) 7.12.50.20170314-git
  Copyright (C) 2017 Free Software Foundation, Inc.  
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.   
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"   
  and "show warranty" for details. 
  This GDB was configured as "x86_64-linux-gnu".   
  Type "show configuration" for configuration details. 
  For bug reporting instructions, please see:  
  . 
  Find the GDB manual and other documentation resources online at: 
  .
  For help, type "help".   
  Type "apropos word" to search for commands related to "word"...  
  Reading symbols from /usr/sbin/libvirtd...(no debugging symbols found)...done.
  [New LWP 4232]
  [New LWP 4216]
  [New LWP 4219]
  [New LWP 4218]
  [New LWP 4231]
  [New LWP 4215]
  [New LWP 4220]
  [New LWP 4224]
  [New LWP 4221]
  [New LWP 4223]
  [New LWP 4222]
  [New LWP 4217]
  [New LWP 4225]
  [New LWP 4227]
  [New LWP 4230]
  [New LWP 4229]
  [New LWP 4228]
  [Thread debugging using libthread_db enabled] 
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Core was generated by `/usr/sbin/libvirtd'.   
  Program terminated with signal SIGSEGV, Segmentation fault.   
  #0  0x7f97fa93367f in rtnl_link_sriov_parse_vflist () from 
/usr/lib/x86_64-linux-gnu/libnl-route-3.so.200
  [Current thread is 1 (Thread 0x7f97dff94700 (LWP 4232))]  
   
  (gdb) where   
   
  #0  0x7f97fa93367f in rtnl_link_sriov_parse_vflist () from 
/usr/lib/x86_64-linux-gnu/libnl-route-3.so.200
  #1  0x7f97fa927fad in ?? () from 
/usr/lib/x86_64-linux-gnu/libnl-route-3.so.200  
  #2  0x7f980bfb76c3 in nl_cache_parse () from 
/lib/x86_64-linux-gnu/libnl-3.so.200
  #3  0x7f980bfb770b in ?? () from /lib/x86_64-linux-gnu/libnl-3.so.200 
   
  #4  0x7f980bfbdc1c in nl_recvmsgs_report () from 
/lib/x86_64-linux-gnu/libnl-3.so.200
  #5  0x7f980bfbe049 in nl_recvmsgs () from 
/lib/x86_64-linux-gnu/libnl-3.so.200   
  #6  0x7f980bfb6aab in ?? () from /lib/x86_64-linux-gnu/libnl-3.so.200 
   
  #7  0x7f980bfb763d in nl_cache_pickup () from 
/lib/x86_64-linux-gnu/libnl-3.so.200   
  #8  0x7f980bfb7871 in nl_cache_refill () from 
/lib/x86_64-linux-gnu/libnl

[Desktop-packages] [Bug 1699664] Re: package libnl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attemptin

2017-06-23 Thread ChristianEhrhardt

Hi Dipak,
for issues like that I recommend following [1] but adapted for your package 
(libnl-3-200).

Please report back if that did not resolve the case for you.

[1]: https://askubuntu.com/questions/148715/how-to-fix-package-is-in-a
-very-bad-inconsistent-state-error

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libnl3 in Ubuntu.
https://bugs.launchpad.net/bugs/1699664

Title:
  package libnl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in libnl3 package in Ubuntu:
  Incomplete

Bug description:
  issue in installing packages.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libnl-3-200:amd64 3.2.27-1ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-54-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Thu Jun 22 01:06:06 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu7
   libgcc1 1:6.0.1-0ubuntu1
  DuplicateSignature:
   package:libnl-3-200:amd64:3.2.27-1ubuntu0.16.04.1
   Processing triggers for fontconfig (2.11.94-0ubuntu1.1) ...
   dpkg: error processing package libnl-3-200:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-04-08 (74 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: libnl3
  Title: package libnl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1699664] Re: package libnl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attemptin

2017-06-23 Thread ChristianEhrhardt

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.

If indeed this is a local configuration problem, you can find pointers
to get help for this sort of problem here:
http://www.ubuntu.com/support/community

Or if you believe that this is really a bug, then you may find it
helpful to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem,
explain why you believe this is a bug in Ubuntu rather than a problem
specific to your system, and then change the bug status back to New.

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libnl3 in Ubuntu.
https://bugs.launchpad.net/bugs/1699664

Title:
  package libnl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in libnl3 package in Ubuntu:
  Incomplete

Bug description:
  issue in installing packages.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libnl-3-200:amd64 3.2.27-1ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-54-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Thu Jun 22 01:06:06 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu7
   libgcc1 1:6.0.1-0ubuntu1
  DuplicateSignature:
   package:libnl-3-200:amd64:3.2.27-1ubuntu0.16.04.1
   Processing triggers for fontconfig (2.11.94-0ubuntu1.1) ...
   dpkg: error processing package libnl-3-200:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-04-08 (74 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: libnl3
  Title: package libnl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1581370] [NEW] Keyboard/Mouse input dead after upgrade to Xenial

2016-05-13 Thread ChristianEhrhardt

Public bug reported:

Following
https://help.ubuntu.com/community/ReportingBugs#Desktop_Applications and
https://wiki.ubuntu.com/X/Troubleshooting/Freeze as good as applicable:

dmesg: http://paste.ubuntu.com/16386293/
/var/log/Xorg.0.log: http://paste.ubuntu.com/16386296/
/sys/kernel/debug/dri/0/i915_error_state: http://paste.ubuntu.com/16386300/

Have you experienced just one lockup, or have you had a series of these lockups?
=> 100% reproducible

If you've had several, how often does it occur? Every few hours? Once or twice 
a day? Couple times a week?
=> hits lockup (or just all input devices failing) on everey init of lightdm/X11

When did you first notice it?
=> After Dist-Upgrade from Trusty->Xenial


After changing compositing (Desktop Effects) settings?
=> No changes made yet, let me know if I should

Only when using compositing (Unity, et al)
=> I had a short moment of a living lxde, but it was not reproducible
=> Tried Unity and KDE as well, but it hangs at the greeter already - before 
the Desktop system is up

Kernels:
I noticed also some graphical glitches with the Xenial Kernel (some colors are 
wrong, like highlights would flip to cyan)
Can't make a screenshot

Xorg:
I didn't see an xorg-edgers or ubuntu-x-swat for Xenial yet, so I couldn't 
easily try something here.

Debugging only works via ssh login atm - but since lokal input is broken anyway 
...
If I boot into recovery more without UI and also in Bios Key&Mouse are working 
fine.
So it shouldn't be a general HW issue.

It stops me from auto-reporting by telling me about "This is not an official 
Ubuntu package. Please remove any third party package and try again."
I ran ppa-purge on all I had - still doesn't let me do it.
I also purged all of gnome/xorg/unity and reinstalled, but no improvement - 
maybe I missed something.
Since it didn't make a difference I reinstalled what I considered needed chrome 
and google-musicmanager.

I'm willing to help debugging, but I'm not experienced in doing so for X11 - 
especially since none of the logs I checked contain an obvious error pointing 
me to something.
If you have more logs to check or some other advice please let me know.


Potentially involved:
2560 /usr/lib/xorg/Xorg
2611 /usr/sbin/lightdm
2650 /usr/sbin/unity-greeter

||/ Name Version Architecture   
 Description
+++--===-===-==
ii  lightdm  1.18.1-0ubuntu1 amd64  
 Display Manager
ii  unity-greeter16.04.2-0ubuntu1amd64  
 Unity Greeter
ii  xorg 1:7.7+13ubuntu3 amd64  
 X.Org X Window System

I hope that apport attaches more files to this as it said it would to
help you check my case and recommend next steps.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xserver-xorg-core 2:1.18.3-1ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
Date: Fri May 13 10:19:21 2016
DistUpgraded: 2016-05-09 17:56:18,056 DEBUG running doUpdate() 
(showErrors=False)
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus: vboxhost, 4.3.38, 4.4.0-22-generic, x86_64: installed
ExecutablePath: /usr/lib/xorg/Xorg
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:844d]
InstallationDate: Installed on 2012-04-29 (1474 days ago)
InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Release amd64 
(20120424.1)
MachineType: System manufacturer System Product Name
ProcEnviron:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=eacb9ac2-7523-41c7-bde4-b78a3cd3cf97 ro bootdegraded=true nosplash 
apm=on apm=power-off nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw
SourcePackage: xorg-server
UpgradeStatus: Upgraded to xenial on 2016-05-09 (3 days ago)
dmi.bios.date: 12/04/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0907
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8H67-I
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0907:bd12/04/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H67-I:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassis

[Desktop-packages] [Bug 1581370] Re: Keyboard/Mouse input dead after upgrade to Xenial

2016-05-13 Thread ChristianEhrhardt

I decided that it is about time to do some serious cleanup.
I found no good guide cleaning to the extend I wanted so I wrote one.

This fixed the issue for me.
If anybody comes by this bug - I hope it might help you as well.

If you, like me installed and uninstalled a lot the following might help you to 
clean up.
In my case I had a Server that srated on 12.04 and went through various ppa's 
and ups/downs.
For example I once had issues with KDE leading me to round robin 
uninstalls/reinstalls/purges.
Eventually I realized that set a lot of things to installed which would be no 
more needed or even trigger issues now.
That left me with a lot of crap that affected my otherwise nice new upgrade to 
16.04

To clean up and get rid of a lot without really reinstalling I did the
following:

# First I wanted to get rid of old ppas, especially in case they still would 
overwrite even the newer packages
ppa-purge "ppaname"

Other than just apt-add-repository -r this also tries to revert to the original
See this for more: 
http://askubuntu.com/questions/309966/difference-between-ppa-purge-and-add-apt-repository-r

# Next I got a list of all manual installed packages
comm -23 <(apt-mark showmanual | sort -u) <(gzip -dc 
/var/log/installer/initial-status.gz | sed -n 's/^Package: //p' | sort -u) > 
manual.txt

# Clean up in this file, remove all packages from this list that you would like 
to keep
vim manual.txt


# Then set all these packages from manual to auto installed
while read p; do sudo apt-mark auto ${p}; done  Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1581370

Title:
  Keyboard/Mouse input dead after upgrade to Xenial

Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Following
  https://help.ubuntu.com/community/ReportingBugs#Desktop_Applications
  and https://wiki.ubuntu.com/X/Troubleshooting/Freeze as good as
  applicable:

  dmesg: http://paste.ubuntu.com/16386293/
  /var/log/Xorg.0.log: http://paste.ubuntu.com/16386296/
  /sys/kernel/debug/dri/0/i915_error_state: http://paste.ubuntu.com/16386300/

  Have you experienced just one lockup, or have you had a series of these 
lockups?
  => 100% reproducible

  If you've had several, how often does it occur? Every few hours? Once or 
twice a day? Couple times a week?
  => hits lockup (or just all input devices failing) on everey init of 
lightdm/X11

  When did you first notice it?
  => After Dist-Upgrade from Trusty->Xenial

  
  After changing compositing (Desktop Effects) settings?
  => No changes made yet, let me know if I should

  Only when using compositing (Unity, et al)
  => I had a short moment of a living lxde, but it was not reproducible
  => Tried Unity and KDE as well, but it hangs at the greeter already - before 
the Desktop system is up

  Kernels:
  I noticed also some graphical glitches with the Xenial Kernel (some colors 
are wrong, like highlights would flip to cyan)
  Can't make a screenshot

  Xorg:
  I didn't see an xorg-edgers or ubuntu-x-swat for Xenial yet, so I couldn't 
easily try something here.

  Debugging only works via ssh login atm - but since lokal input is broken 
anyway ...
  If I boot into recovery more without UI and also in Bios Key&Mouse are 
working fine.
  So it shouldn't be a general HW issue.

  It stops me from auto-reporting by telling me about "This is not an official 
Ubuntu package. Please remove any third party package and try again."
  I ran ppa-purge on all I had - still doesn't let me do it.
  I also purged all of gnome/xorg/unity and reinstalled, but no improvement - 
maybe I missed something.
  Since it didn't make a difference I reinstalled what I considered needed 
chrome and google-musicmanager.

  I'm willing to help debugging, but I'm not experienced in doing so for X11 - 
especially since none of the logs I checked contain an obvious error pointing 
me to something.
  If you have more logs to check or some other advice please let me know.

  
  Potentially involved:
  2560 /usr/lib/xorg/Xorg
  2611 /usr/sbin/lightdm
  2650 /usr/sbin/unity-greeter

  ||/ Name Version Architecture 
   Description
  
+++--===-===-==
  ii  lightdm  1.18.1-0ubuntu1 amd64
   Display Manager
  ii  unity-greeter16.04.2-0ubuntu1amd64
   Unity Greeter
  ii  xorg 1:7.7+13ubuntu3 amd64
   X.Org X Window System

  I hope that apport attaches more files to this as it said it would to
  help you check my case and recommend next steps.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-core 2:1.18.3-1ubu

[Desktop-packages] [Bug 1373070] Re: full fix for disconnected path (paths)

2016-07-25 Thread ChristianEhrhardt

Actually the dovecot profiles are in apparmor and not dovecot source
packages - so it would be an apparmor task then.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1373070

Title:
  full fix for disconnected path (paths)

Status in cups package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in rsyslog package in Ubuntu:
  New

Bug description:
  With the apparmor 3 RC1 upload, there is an incomplete bug fix for
  disconnected paths. This bug is to track that work.

  This denial may be related:
  Sep 23 10:10:50 localhost kernel: [40262.517799] audit: type=1400 
audit(1411485050.722:2862): apparmor="DENIED" operation="sendmsg" info="Failed 
name lookup - disconnected path" error=-13 profile="/usr/sbin/rsyslogd" 
name="dev/log" pid=7011 comm="logger" requested_mask="r" denied_mask="r" 
fsuid=0 ouid=0

  This is related to bug 1375410

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

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

[Desktop-packages] [Bug 1373070] Re: full fix for disconnected path (paths)

2016-07-25 Thread ChristianEhrhardt

Hi,
I think bug 1594202 is another data point for this:

Jun 20 01:49:24 omicron kernel: [ 962.491873] audit: type=1400
audit(1466380164.941:90): apparmor="ALLOWED" operation="sendmsg"
info="Failed name lookup - disconnected path" error=-13
profile="/usr/lib/dovecot/log" name="run/systemd/journal/dev-log"
pid=2175 comm="log" requested_mask="w" denied_mask="w" fsuid=0 ouid=0

But before I close-as-dup and open a dovecot task here I'd ask if one
that has worked on this issue  take a look if that is true?

If so are we still supposed to add workarounds like the
attach_disconnected or were there updates to this issue which didn't
make it to the bug yet?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1373070

Title:
  full fix for disconnected path (paths)

Status in cups package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in rsyslog package in Ubuntu:
  New

Bug description:
  With the apparmor 3 RC1 upload, there is an incomplete bug fix for
  disconnected paths. This bug is to track that work.

  This denial may be related:
  Sep 23 10:10:50 localhost kernel: [40262.517799] audit: type=1400 
audit(1411485050.722:2862): apparmor="DENIED" operation="sendmsg" info="Failed 
name lookup - disconnected path" error=-13 profile="/usr/sbin/rsyslogd" 
name="dev/log" pid=7011 comm="logger" requested_mask="r" denied_mask="r" 
fsuid=0 ouid=0

  This is related to bug 1375410

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

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

[Desktop-packages] [Bug 928576] Re: No password prompt (occasionally) on resume, causes unity problems

** Tags added: notserv

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

Title:
  No password prompt (occasionally) on resume, causes unity problems

Status in pm-utils package in Ubuntu:
  New

Bug description:
  On occasion, not too often, but i caught it twice so far in last 48
  hours of using Ubuntu 11.10 on new HP Laptop, i've noticed the
  following:

  When I resume from sleep/suspend (when i close my laptop lid and
  reopen it), on occasion, it will not prompt for password.  It will
  simply reopen my desktop but with the following caveats:   There is no
  taskbar on the left and no menubar on the top.  Also, i can not
  drag/move/close any windows that are on the screen (but i can interact
  with them).

  I've seen other people report (on askubuntu) that on resume from sleep
  they have no menubar/taskbar, but i noticed that when this happens for
  me there is no password prompt first.  I noticed this because i have a
  habit of when i open my laptop the first thing i do is enter my
  password, either in Linux or Windows, and these times there was no
  password prompt on resume from suspend.

  This leads me to believe unity is waiting for the password to be
  enterred to resume, but since there is no password prompt, unity never
  resumes its display.

  Again, this does not happen every time, it's only happened for sure
  twice in 2 days of heavy usage.

  -Rob

  p.s. I was told at askubuntu.com to report the bug, and was also told
  it would probably get low priority because it does not ALWAYS happen.
  I understand that, but hope someone can find something easy to fix
  here.

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

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

[Desktop-packages] [Bug 970281] Re: Suspend test fails for System Testing

** Tags added: notserv

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

Title:
  Suspend test fails for System Testing

Status in pm-utils package in Ubuntu:
  New

Bug description:
  When running the "System Testing" suspend test (tried twice) from
  booted from Beta 2 USB stick the screen goes black but system doesn't
  suspend or return to desktop. Wireless LED continues to blink. Short
  press of power button doesn't return control, so long press / power
  off reset is needed. This hardware suspends fine from 11.10 desktop
  (booted from partition on HD).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: pm-utils 1.4.1-9
  ProcVersionSignature: Ubuntu 3.2.0-20.33-generic-pae 3.2.12
  Uname: Linux 3.2.0-20-generic-pae i686
  ApportVersion: 1.95-0ubuntu1
  Architecture: i386
  CasperVersion: 1.312
  CheckboxCommand: sleep_test -d
  CheckboxData: System hangs with blank black screen but backlight on. Have to 
hold power button to reboot to get system back. Wireless light continues to 
flash during test but system never suspends and doesn't return control.
  CheckboxTest: suspend/suspend_advanced
  Date: Sat Mar 31 18:37:17 2012
  LiveMediaBuild: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120328)
  PackageArchitecture: all
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1019362] Re: Use suspend_hybrid where supported

** Tags added: notserv

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

Title:
  Use suspend_hybrid where supported

Status in pm-utils package in Ubuntu:
  New

Bug description:
  If a system reports that  hybrid suspend is supported, as a result of
  pm-is-supported --suspend-hybrid then suspend should default to using
  hybrid suspend. Allow an override via /etc/defaults in case there are
  systems that report hybrid supported that then don't work.

  See this blog posting - http://daniel.hahler.de/use-hybrid-suspend-
  method-by-default

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: pm-utils 1.4.1-9
  ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18
  Uname: Linux 3.2.0-25-generic i686
  ApportVersion: 2.0.1-0ubuntu9
  Architecture: i386
  Date: Fri Jun 29 19:01:46 2012
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100427.1)
  PackageArchitecture: all
  ProcEnviron:
   SHELL=/bin/bash
   TERM=xterm
   PATH=(custom, user)
   LANG=en_GB.UTF-8
  SourcePackage: pm-utils
  UpgradeStatus: Upgraded to precise on 2012-04-15 (75 days ago)

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

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

[Desktop-packages] [Bug 989175] Re: Powernap should ensure WoL is enabled before Second Stage