date:20170423

[Touch-packages] [Bug 1685705] [NEW] package libgstreamer-plugins-base0.10-0 0.10.36-1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libgstreamer-plugins-base0.10-0/changelog.D

2017-04-23 Thread sathish kumar

Public bug reported:

i having issue with this plugin

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libgstreamer-plugins-base0.10-0 0.10.36-1
ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
Uname: Linux 4.4.0-72-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Mon Apr 24 11:13:18 2017
DpkgTerminalLog:
 Preparing to unpack 
.../libgstreamer-plugins-base0.10-0_0.10.36-2ubuntu0.1_amd64.deb ...
 Unpacking libgstreamer-plugins-base0.10-0:amd64 (0.10.36-2ubuntu0.1) over 
(0.10.36-1) ...
 dpkg: error processing archive 
/var/cache/apt/archives/libgstreamer-plugins-base0.10-0_0.10.36-2ubuntu0.1_amd64.deb
 (--unpack):
  trying to overwrite shared 
'/usr/share/doc/libgstreamer-plugins-base0.10-0/changelog.Debian.gz', which is 
different from other instances of package libgstreamer-plugins-base0.10-0:amd64
DuplicateSignature:
 package:libgstreamer-plugins-base0.10-0:0.10.36-1
 Unpacking libgstreamer-plugins-base0.10-0:amd64 (0.10.36-2ubuntu0.1) over 
(0.10.36-1) ...
 dpkg: error processing archive 
/var/cache/apt/archives/libgstreamer-plugins-base0.10-0_0.10.36-2ubuntu0.1_amd64.deb
 (--unpack):
  trying to overwrite shared 
'/usr/share/doc/libgstreamer-plugins-base0.10-0/changelog.Debian.gz', which is 
different from other instances of package libgstreamer-plugins-base0.10-0:amd64
ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libgstreamer-plugins-base0.10-0/changelog.Debian.gz', which is 
different from other instances of package libgstreamer-plugins-base0.10-0:amd64
InstallationDate: Installed on 2016-03-30 (389 days ago)
InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: gst-plugins-base0.10
Title: package libgstreamer-plugins-base0.10-0 0.10.36-1 failed to 
install/upgrade: trying to overwrite shared 
'/usr/share/doc/libgstreamer-plugins-base0.10-0/changelog.Debian.gz', which is 
different from other instances of package libgstreamer-plugins-base0.10-0:amd64
UpgradeStatus: Upgraded to xenial on 2016-05-01 (357 days ago)

** Affects: gst-plugins-base0.10 (Ubuntu)
 Importance: Undecided
 Status: New


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

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

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

Status in gst-plugins-base0.10 package in Ubuntu:
  New

Bug description:
  i having issue with this plugin

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libgstreamer-plugins-base0.10-0 0.10.36-1
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Mon Apr 24 11:13:18 2017
  DpkgTerminalLog:
   Preparing to unpack 
.../libgstreamer-plugins-base0.10-0_0.10.36-2ubuntu0.1_amd64.deb ...
   Unpacking libgstreamer-plugins-base0.10-0:amd64 (0.10.36-2ubuntu0.1) over 
(0.10.36-1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libgstreamer-plugins-base0.10-0_0.10.36-2ubuntu0.1_amd64.deb
 (--unpack):
trying to overwrite shared 
'/usr/share/doc/libgstreamer-plugins-base0.10-0/changelog.Debian.gz', which is 
different from other instances of package libgstreamer-plugins-base0.10-0:amd64
  DuplicateSignature:
   package:libgstreamer-plugins-base0.10-0:0.10.36-1
   Unpacking libgstreamer-plugins-base0.10-0:amd64 (0.10.36-2ubuntu0.1) over 
(0.10.36-1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libgstreamer-plugins-base0.10-0_0.10.36-2ubuntu0.1_amd64.deb
 (--unpack):
trying to overwrite shared 
'/usr/share/doc/libgstreamer-plugins-base0.10-0/changelog.Debian.gz', which is 
different from other instances of package libgstreamer-plugins-base0.10-0:amd64
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libgstreamer-plugins-base0.10-0/changelog.Debian.gz', which is 
different from other instances of package libgstreamer-plugins-base0.10-0:amd64
  InstallationDate: Installed on 2016-03-30 (389 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: gst-plugins-base0.10
  Title: package libgstreamer-plugins-base0.10-0 0.10.36-1 failed to 
install/upgrade: trying to overwrite shared 
'/usr/share/doc/libgstreamer-plugins-base0.10-0/changelog.Debian.gz', which is 
different from other instances of package libgstreamer-plugins-base0.10-0:amd64
  UpgradeStatus: Upgraded to xenial on 2016-05-01 (357 days ago)

To

[Touch-packages] [Bug 1684481] Re: KVM guest execution start apparmor blocks on /dev/ptmx now (regression?)

2017-04-23 Thread ChristianEhrhardt

Thanks Stephane and Christian!

Since we ...

a) have a workaround by manually adding the entry to the apparmor abstraction 
(or dropping serial if that is an option)
b) having an explicit serial in the guest profile is not the default
c) KVM in LXD is more a "nice to have" solution than something everybody uses 
on a daily base (To drive KVM in LXD applying a certain amount of tricks e.g. 
to the profile is already involved)

... I think for now we can wait on the LXC update.
Please update when you know about the schedule that it might happen on.

Dropping the Kernel Task to invalid as it turns out not to be involved,
and the apparmor task to "Won't Fix" as while being involved there is no
change we want to make there.

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

** Changed in: apparmor (Ubuntu)
   Status: New => Won't Fix

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

Title:
  KVM guest execution start apparmor blocks on /dev/ptmx now
  (regression?)

Status in apparmor package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Invalid
Status in lxc package in Ubuntu:
  Fix Committed
Status in lxd package in Ubuntu:
  Invalid

Bug description:
  Setup:
  - Xenial host
  - lxd guests with Trusty, Xenial, ...
  - add a LXD profile to allow kvm [3] (inspired by stgraber)
  - spawn KVM guests in the LXD guests using the different distro release 
versions
  - guests are based on the uvtool default template which has a serial console 
[4]

  Issue:
  - guest starting with serial device gets blocked by apparmor and killed on 
creation
  - This affects at least ppc64el and x86 (s390x has no serial concept that 
would match)
  - This appeared in our usual checks on -proposed releases so maybe we 
can/should stop something?
Last good was "Apr 5, 2017 10:40:50 AM" first bad one "Apr 8, 2017 5:11:22 
AM"

  Background:
  We use this setup for a while and it was working without a change on our end.
  Also the fact that it still works in the Trusty LXD makes it somewhat 
suspicious.
  Therefore I'd assume an SRUed change in LXD/Kernel/Apparmor might be the 
reason and open this bug to get your opinion on it.

  You can look into [1] and search for uvt-kvm create in it.

  Deny in dmesg:
  [652759.606218] audit: type=1400 audit(1492671353.134:4520): 
apparmor="DENIED" operation="open" 
namespace="root//lxd-testkvm-xenial-from_" 
profile="libvirt-668e21f1-fa55-4a30-b325-0ed5cfd55e5b" name="/dev/pts/ptmx" 
pid=27162 comm="qemu-system-ppc" requested_mask="wr" denied_mask="wr" fsuid=0 
ouid=0

  Qemu-log:
  2017-04-20T06:55:53.139450Z qemu-system-ppc64: -chardev pty,id=charserial0: 
Failed to create PTY: No such file or directory

  There was a similar issue on qmeu namespacing (which we don't use on any of 
these releases) [2].
  While we surely don't have the "same" issue the debugging on the namespacing 
might be worth as it could be related.

  Workaround for now:
  - drop serial section from guest xml

  [1]: 
https://jenkins.ubuntu.com/server/view/Virt/job/virt-migration-cross-release-amd64/78/consoleFull
  [2]: https://bugzilla.redhat.com/show_bug.cgi?id=1421036
  [3]: 
https://git.launchpad.net/~ubuntu-server/ubuntu/+source/qemu-migration-test/tree/kvm_profile.yaml
  [4]: https://libvirt.org/formatdomain.html#elementsCharPTY
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: ppc64el
  DistroRelease: Ubuntu 16.04
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: lxd
  PackageArchitecture: ppc64el
  ProcKernelCmdline: root=UUID=902eaad1-2164-4f9a-bec4-7ff3abc15804 ro 
console=hvc0
  ProcLoadAvg: 3.15 3.02 3.83 1/3056 79993
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -1
  ProcVersion: Linux version 4.4.0-72-generic (buildd@bos01-ppc64el-022) (gcc 
version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #93-Ubuntu SMP Fri 
Mar 31 14:05:15 UTC 2017
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Syslog:
   
  Tags:  xenial uec-images
  Uname: Linux 4.4.0-72-generic ppc64le
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: utah
  _MarkForUpload: True
  cpu_cores: Number of cores present = 20
  cpu_coreson: Number of cores online = 20
  cpu_smt: SMT is off
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: ppc64el
  DistroRelease: Ubuntu 16.04
  NonfreeKernelModules: cfg80211 ebtable_broute ebtable_nat binfmt_misc veth 
nbd openvswitch vhost_net vhost macvtap macvlan xt_conntrack ipt_REJECT 
nf_reject_ipv4 ebtable_filter ebtables ip6t_MASQUERADE nf_nat_masquerade_ipv6 
ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_filter 
ip6_tables xt_comment xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat

[Touch-packages] [Bug 1496051] Re: kswapd pegging cpu

2017-04-23 Thread Launchpad Bug Tracker

[Expired for lxc-android-config (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: lxc-android-config (Ubuntu)
   Status: Incomplete => Expired

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

Title:
   kswapd pegging cpu

Status in Canonical System Image:
  Incomplete
Status in lxc-android-config package in Ubuntu:
  Expired

Bug description:
  while debugging bug 1491566
  On arale, rc-proposed circa sept 14
  I had launched phone, messaging, browser (on cnn.com), camera (taken pics), 
gallery (edit mode of pic), clock, ubuntu-system-settings, cut-the-rope, dash 
(of course) - toggling between them in the spread, just selecting them, mostly 
clock, browser, gallery
  and at the same time running the phone/text script as found in bug 1491566 
(modified to text, call, then text 5 times)

  I just happened to be running top and then noticed process
  kswapd
  would run & peg cpu intermittently, sometimes it would peg the cpu for just 1 
second or so, but then sometimes it would appear to run at 95%+ for like 10 
seconds or more.
  It didn't seem to follow a particular pattern, but i could definitely tell it 
was effecting the ui (stalling)

  ogra indicated our swappiness should be very low.
  so i did sudo sysctl vm.swappiness=10 as instructed, however as i continued 
testing, i continued to see kswapd continue to run and peg the cpu at about the 
same frequency.

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

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

[Touch-packages] [Bug 1657553] Re: Laptop stick and touchpad problems after linux 4.4 update

2017-04-23 Thread Po-Hsu Lin

Hello,
Can you confirm the parameter for "POINTINGSTICK_CONST_ACCEL" should be 0.025
or 0.25?

Thanks

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

Title:
Laptop stick and touchpad problems after linux 4.4 update

Status in linux package in Ubuntu:
Incomplete
Status in systemd package in Ubuntu:
Confirmed
Status in linux source package in Xenial:
Incomplete
Status in systemd source package in Xenial:
Confirmed

Bug description:
Ever since the 4.4.0-53 kernel update the touchpad and trackpoint have
behaved erratically on my Dell Precision 7510:
* The trackpoint moves WAY too fast and there don't seem to be any parameters
I can change in xinput to fix this. It is essentially unusable.
* The touchpad starts with parameters set incorrectly.
* Touchpad tap to click is now turned on again and is very sensitive. This I
can change through xinput but the change is still odd.
* The two finger scrolling is set incorrectly to be highly sensitive. This I
can also change through xinput.
* Two finger scrolling still activates often during normal use of the
trackpad. To the extent that I had to turn off two finger scrolling to stop
inadvertent scrolling.

All of the above behavior is new going from 4.4.0-47 to -53.
Previously this all worked perfectly on this machine.

Seems to be symptoms noted by these other users on askubuntu here as
well: http://askubuntu.com/questions/862527/laptop-stick-mouse-
problems-after-linux-4-4-update-on-14-04

The touchpad symptoms I seem to be able to work around my changing
xinput parameters, but the trackpoint I have not been able to fix at
all (which is sad since that is my primary mouse device normally).
Would appreciate any suggestions as to how to revert the old behavior.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-53-generic 4.4.0-53.74
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: jpeverill 2813 F pulseaudio
/dev/snd/controlC0: jpeverill 2813 F pulseaudio
Date: Wed Jan 18 10:21:55 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-07-17 (916 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 8087:0a2b Intel Corp.
Bus 001 Device 004: ID 1bcf:2b91 Sunplus Innovation Technology Inc.
Bus 001 Device 003: ID 0a5c:5832 Broadcom Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Precision 7510
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic.efi.signed
root=UUID=4a4cfeb0-ad39-4293-bcaf-000d6538b550 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-4.4.0-59-generic N/A
linux-backports-modules-4.4.0-59-generic N/A
linux-firmware1.157.6
SourcePackage: linux
UpgradeStatus: Upgraded to xenial on 2016-05-01 (262 days ago)
dmi.bios.date: 01/24/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.3.10
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.3.10:bd01/24/2016:svnDellInc.:pnPrecision7510:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
dmi.product.name: Precision 7510
dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1685688] Re: "watch --interval" does not take decimal

2017-04-23 Thread Terrance

Oops, my bad.

I was trying LC_TIME=en_DK, but accidentally changed whole system LC to
en_DK. Which uses ',' instead of '.' as a decimal point...

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

Title:
  "watch --interval" does not take decimal

Status in procps package in Ubuntu:
  New

Bug description:
  
  Package: procps
  Version: 2:3.3.10-4ubuntu2.3
  Origin: Ubuntu


  ```
  % watch --interval 0.1 date
  watch: failed to parse argument: '0.1'
  % 
  ```

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

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

[Touch-packages] [Bug 1685688] Re: "watch --interval" does not take decimal

2017-04-23 Thread Terrance

Oops, my bad.

I was trying LC_TIME=en_DK, but accidentally changed whole system LC to
en_DK. Which uses ',' instead of '.' as a decimal point...

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

Title:
  "watch --interval" does not take decimal

Status in procps package in Ubuntu:
  New

Bug description:
  
  Package: procps
  Version: 2:3.3.10-4ubuntu2.3
  Origin: Ubuntu


  ```
  % watch --interval 0.1 date
  watch: failed to parse argument: '0.1'
  % 
  ```

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

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

[Touch-packages] [Bug 1632772] Re: Login option 'GNOME on Wayland' does not start from LightDM

2017-04-23 Thread Daniel van Vugt

ubuntu-meta (1.380) artful; urgency=medium

  * update.cfg; zesty -> artful
  * Refreshed dependencies
  * Removed unity8-desktop-session from desktop-recommends [amd64 arm64
armhf i386 ppc64el]

 -- Dimitri John Ledkov   Sun, 23 Apr 2017 15:03:58
+0100

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

** Changed in: ubuntu-meta (Ubuntu)
   Importance: Undecided => Critical

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

** Changed in: ubuntu-meta (Ubuntu)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

** Changed in: unity8-desktop-session (Ubuntu)
   Status: Confirmed => Won't Fix

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

** Changed in: gnome-session (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: unity8-desktop-session
   Status: Confirmed => Invalid

** Changed in: ubuntu-gnome
   Status: Confirmed => Invalid

** Changed in: unity8-desktop-session
   Status: Invalid => Won't Fix

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

Title:
  Login option 'GNOME on Wayland' does not start from LightDM

Status in Ubuntu GNOME:
  Invalid
Status in unity8-desktop-session:
  Won't Fix
Status in gnome-session package in Ubuntu:
  Invalid
Status in lightdm package in Ubuntu:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in unity8-desktop-session package in Ubuntu:
  Won't Fix

Bug description:
  When picking GNOME on Wayland as session and attempting to login from
  LightDM then it fails, all you see is a black screen with a blinking
  cursor.

  However, manually running:
  $ dbus-run-session gnome-shell --display-server --wayland
  from the console/vt1 (Ctrl+Alt+F1) seems to work.
  But from LightDM it does not work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-session-wayland 3.20.2-1ubuntu7
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Wed Oct 12 18:06:13 2016
  InstallationDate: Installed on 2013-12-26 (1020 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1685688] [NEW] "watch --interval" does not take decimal

2017-04-23 Thread Terrance

Public bug reported:


Package: procps
Version: 2:3.3.10-4ubuntu2.3
Origin: Ubuntu


```
% watch --interval 0.1 date
watch: failed to parse argument: '0.1'
% 
```

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

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

Title:
  "watch --interval" does not take decimal

Status in procps package in Ubuntu:
  New

Bug description:
  
  Package: procps
  Version: 2:3.3.10-4ubuntu2.3
  Origin: Ubuntu


  ```
  % watch --interval 0.1 date
  watch: failed to parse argument: '0.1'
  % 
  ```

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

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

[Touch-packages] [Bug 1685683] Re: Update evolution to 3.24.1

2017-04-23 Thread Jeremy Bicha

** Description changed:

  We should update the Evolution stack to 3.24 for Ubuntu 17.10. The big
  change here is that it now uses cmake instead of autotools.
  
  The update is staged in this PPA and rebuilds of all rdepends have been done:
  https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/transitions/+packages
  
  I made a few packaging changes we should review with Debian.
  
  1. I dropped https://sources.debian.net/src/evolution-data-
- server/3.22.7-1/debian/patches/01-noinst-libedbus-private.patch/ and
+ server/unstable/debian/patches/01-noinst-libedbus-private.patch/ and
  added a libedbus-private0 package and had all the e-d-s libraries depend
  on it.
  
  2. I dropped
- https://sources.debian.net/src/evolution/3.22.6-1/debian/patches
+ https://sources.debian.net/src/evolution/unstable/debian/patches
  /10_revert_libevolution_avoid-version.patch/ since it does not directly
  apply to cmake and it doesn't seem needed. The soname hasn't been bumped
  in 5 years. I had to have libevolution Breaks/Replaces evolution-dev
  since there are no .so symlinks any more.
  
- 3. I disabled since it didn't seem to be needed.
+ 3. I disabled
+ 
https://sources.debian.net/src/evolution/unstable/debian/patches/02_nss_paths.patch/
+ since it didn't seem to be needed.
  
  To Do
  =
  4. https://bugzilla.gnome.org/show_bug.cgi?id=781645
  
  5. Hook up the new installed-tests packages to be ran as autopkgtests

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

Title:
  Update evolution to 3.24.1

Status in evolution package in Ubuntu:
  New
Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  We should update the Evolution stack to 3.24 for Ubuntu 17.10. The big
  change here is that it now uses cmake instead of autotools.

  The update is staged in this PPA and rebuilds of all rdepends have been done:
  https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/transitions/+packages

  I made a few packaging changes we should review with Debian.

  1. I dropped https://sources.debian.net/src/evolution-data-
  server/unstable/debian/patches/01-noinst-libedbus-private.patch/ and
  added a libedbus-private0 package and had all the e-d-s libraries
  depend on it.

  2. I dropped
  https://sources.debian.net/src/evolution/unstable/debian/patches
  /10_revert_libevolution_avoid-version.patch/ since it does not
  directly apply to cmake and it doesn't seem needed. The soname hasn't
  been bumped in 5 years. I had to have libevolution Breaks/Replaces
  evolution-dev since there are no .so symlinks any more.

  3. I disabled
  
https://sources.debian.net/src/evolution/unstable/debian/patches/02_nss_paths.patch/
  since it didn't seem to be needed.

  To Do
  =
  4. https://bugzilla.gnome.org/show_bug.cgi?id=781645

  5. Hook up the new installed-tests packages to be ran as autopkgtests

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

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

[Touch-packages] [Bug 1685671] Re: package console-setup-linux 1.108ubuntu15.3 failed to install/upgrade: trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package keyb

2017-04-23 Thread Launchpad Bug Tracker

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

** Changed in: console-setup (Ubuntu)
   Status: New => Confirmed

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

Title:
  package console-setup-linux 1.108ubuntu15.3 failed to install/upgrade:
  trying to overwrite '/lib/systemd/system/console-setup.service', which
  is also in package keyboard-configuration 1.108ubuntu15.3

Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  package console-setup-linux 1.108ubuntu15.3 failed to install/upgrade:
  trying to overwrite '/lib/systemd/system/console-setup.service', which
  is also in package keyboard-configuration 1.108ubuntu15.3

  ProblemType: Package
  DistroRelease: Kali 2017.1
  Package: console-setup-linux 1.108ubuntu15.3
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Sun Apr 23 17:58:11 2017
  ErrorMessage: trying to overwrite 
'/lib/systemd/system/console-setup.service', which is also in package 
keyboard-configuration 1.108ubuntu15.3
  InstallationDate: Installed on 2017-02-28 (54 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.23kali1
   apt  1.2.19
  SourcePackage: console-setup
  Title: package console-setup-linux 1.108ubuntu15.3 failed to install/upgrade: 
trying to overwrite '/lib/systemd/system/console-setup.service', which is also 
in package keyboard-configuration 1.108ubuntu15.3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1685683] [NEW] Update evolution to 3.24.1

2017-04-23 Thread Jeremy Bicha

Public bug reported:

We should update the Evolution stack to 3.24 for Ubuntu 17.10. The big
change here is that it now uses cmake instead of autotools.

The update is staged in this PPA and rebuilds of all rdepends have been done:
https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/transitions/+packages

I made a few packaging changes we should review with Debian.

1. I dropped https://sources.debian.net/src/evolution-data-
server/3.22.7-1/debian/patches/01-noinst-libedbus-private.patch/ and
added a libedbus-private0 package and had all the e-d-s libraries depend
on it.

2. I dropped
https://sources.debian.net/src/evolution/3.22.6-1/debian/patches
/10_revert_libevolution_avoid-version.patch/ since it does not directly
apply to cmake and it doesn't seem needed. The soname hasn't been bumped
in 5 years. I had to have libevolution Breaks/Replaces evolution-dev
since there are no .so symlinks any more.

3. I disabled since it didn't seem to be needed.

To Do
=
4. https://bugzilla.gnome.org/show_bug.cgi?id=781645

5. Hook up the new installed-tests packages to be ran as autopkgtests

** Affects: evolution (Ubuntu)
 Importance: Wishlist
 Status: New

** Affects: evolution-data-server (Ubuntu)
 Importance: Wishlist
 Status: New


** Tags: upgrade-software-version

** Description changed:

  We should update the Evolution stack to 3.24 for Ubuntu 17.10. The big
  change here is that it now uses cmake instead of autotools.
  
  The update is staged in this PPA and rebuilds of all rdepends have been done:
  https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/transitions/+packages
  
  I made a few packaging changes we should review with Debian.
  
  1. I dropped https://sources.debian.net/src/evolution-data-
  server/3.22.7-1/debian/patches/01-noinst-libedbus-private.patch/ and
  added a libedbus-private0 package and had all the e-d-s libraries depend
  on it.
  
  2. I dropped
  https://sources.debian.net/src/evolution/3.22.6-1/debian/patches
  /10_revert_libevolution_avoid-version.patch/ since it does not directly
  apply to cmake and it doesn't seem needed. The soname hasn't been bumped
  in 5 years. I had to have libevolution Breaks/Replaces evolution-dev
  since there are no .so symlinks any more.
  
  3. I disabled since it didn't seem to be needed.
  
- To Do:
- 1. https://bugzilla.gnome.org/show_bug.cgi?id=781645
+ To Do
+ =
+ 4. https://bugzilla.gnome.org/show_bug.cgi?id=781645
  
- 2. Hook up the new installed-tests packages to be ran as autopkgtests
+ 5. Hook up the new installed-tests packages to be ran as autopkgtests

** Also affects: evolution-data-server (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: evolution-data-server (Ubuntu)
   Importance: Undecided => Wishlist

** Summary changed:

- Update to 3.24.1
+ Update evolution to 3.24.1

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

Title:
  Update evolution to 3.24.1

Status in evolution package in Ubuntu:
  New
Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  We should update the Evolution stack to 3.24 for Ubuntu 17.10. The big
  change here is that it now uses cmake instead of autotools.

  The update is staged in this PPA and rebuilds of all rdepends have been done:
  https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/transitions/+packages

  I made a few packaging changes we should review with Debian.

  1. I dropped https://sources.debian.net/src/evolution-data-
  server/3.22.7-1/debian/patches/01-noinst-libedbus-private.patch/ and
  added a libedbus-private0 package and had all the e-d-s libraries
  depend on it.

  2. I dropped
  https://sources.debian.net/src/evolution/3.22.6-1/debian/patches
  /10_revert_libevolution_avoid-version.patch/ since it does not
  directly apply to cmake and it doesn't seem needed. The soname hasn't
  been bumped in 5 years. I had to have libevolution Breaks/Replaces
  evolution-dev since there are no .so symlinks any more.

  3. I disabled since it didn't seem to be needed.

  To Do
  =
  4. https://bugzilla.gnome.org/show_bug.cgi?id=781645

  5. Hook up the new installed-tests packages to be ran as autopkgtests

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

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

[Touch-packages] [Bug 1632772] Re: Login option 'GNOME on Wayland' does not start from LightDM

2017-04-23 Thread Daniel van Vugt

Confirmed, thanks willmo. The simple fix for zesty and artful is:

$ sudo apt remove unity8-desktop-session
$ sudo apt autoremove


** Changed in: unity8-desktop-session
   Status: New => Confirmed

** Changed in: unity8-desktop-session
   Importance: Undecided => High

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

Title:
  Login option 'GNOME on Wayland' does not start from LightDM

Status in Ubuntu GNOME:
  Confirmed
Status in unity8-desktop-session:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed
Status in unity8-desktop-session package in Ubuntu:
  Confirmed

Bug description:
  When picking GNOME on Wayland as session and attempting to login from
  LightDM then it fails, all you see is a black screen with a blinking
  cursor.

  However, manually running:
  $ dbus-run-session gnome-shell --display-server --wayland
  from the console/vt1 (Ctrl+Alt+F1) seems to work.
  But from LightDM it does not work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-session-wayland 3.20.2-1ubuntu7
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Wed Oct 12 18:06:13 2016
  InstallationDate: Installed on 2013-12-26 (1020 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1681652] Re: Laptop screen does not turn off when closing lid from login screen.

2017-04-23 Thread Mathew Tebbens

I believe that is correct, it does not turn off under this
configuration.


** Summary changed:

- Laptop screen does not turn off when closing lid from login screen.
+ Unity Lockscreen does not turn off under this configuration

** Summary changed:

- Unity Lockscreen does not turn off under this configuration
+ Unity Lockscreen does not turn off under this configuration:

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

Title:
  Unity Lockscreen does not turn off under this configuration:

Status in systemd package in Ubuntu:
  New
Status in unity package in Ubuntu:
  New

Bug description:
  I'm running a new install of Ubuntu 16.04.2 LTS on a Dell Rugged Extreme 7414.
  I only changed in Power Settings: When plugged in >  When lid is close = Do 
Nothing
  Brightness & Lock Settings were not changed; Lock Screen after: Screen turns 
off

  If I close the laptop lid while logged in at the Unity Desktop, the
  screen will fade to black and turn off, which I think is normal and
  expected.

  Then when I open the lid I get the login screen, which I also expect.

  Now, if I don't login and just close the lid, the screen does not fade to 
black nor turn off.
  I would expect the screen to fade to black and turn off also from the login 
screen.

  This appears to be a small issue, at least on my system.
  If anyone needs specific information about the system, please ask.

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

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

[Touch-packages] [Bug 1681652] Re: Unity Lockscreen does not turn off under this configuration:

2017-04-23 Thread Mathew Tebbens

Bug report title changed, and still an issue (small).

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

Title:
  Unity Lockscreen does not turn off under this configuration:

Status in systemd package in Ubuntu:
  New
Status in unity package in Ubuntu:
  New

Bug description:
  I'm running a new install of Ubuntu 16.04.2 LTS on a Dell Rugged Extreme 7414.
  I only changed in Power Settings: When plugged in >  When lid is close = Do 
Nothing
  Brightness & Lock Settings were not changed; Lock Screen after: Screen turns 
off

  If I close the laptop lid while logged in at the Unity Desktop, the
  screen will fade to black and turn off, which I think is normal and
  expected.

  Then when I open the lid I get the login screen, which I also expect.

  Now, if I don't login and just close the lid, the screen does not fade to 
black nor turn off.
  I would expect the screen to fade to black and turn off also from the login 
screen.

  This appears to be a small issue, at least on my system.
  If anyone needs specific information about the system, please ask.

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

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

[Touch-packages] [Bug 1685682] [NEW] package libqtcore4 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/xdg/Trolltech.conf', which is different from other instances of pack

2017-04-23 Thread Sabin RanaBhat

Public bug reported:

I was trying to install fbreader on my ubuntu-gnome 17.04
sudo apt-get install fbreader

Reading package lists... Done
Building dependency tree   
Reading state information... Done
fbreader is already the newest version (0.99.4-1).
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
 fbreader : Depends: libqtcore4 (>= 4:4.7.0~beta1) but it is not going to be 
installed
 libqt4-declarative : Depends: libqtcore4 (= 4:4.8.7+dfsg-7ubuntu1) but it is 
not going to be installed
 libqt4-network : Depends: libqtcore4 (= 4:4.8.7+dfsg-7ubuntu1) but it is not 
going to be installed
 libqt4-script : Depends: libqtcore4 (= 4:4.8.7+dfsg-7ubuntu1) but it is not 
going to be installed
 libqt4-sql : Depends: libqtcore4 (= 4:4.8.7+dfsg-7ubuntu1) but it is not going 
to be installed
 libqt4-sql-mysql : Depends: libqtcore4 (= 4:4.8.7+dfsg-7ubuntu1) but it is not 
going to be installed
 libqt4-xml : Depends: libqtcore4 (= 4:4.8.7+dfsg-7ubuntu1) but it is not going 
to be installed
 libqt4-xmlpatterns : Depends: libqtcore4 (= 4:4.8.7+dfsg-7ubuntu1) but it is 
not going to be installed
 libqtdbus4 : Depends: libqtcore4 (= 4:4.8.7+dfsg-7ubuntu1) but it is not going 
to be installed
 libqtgui4 : Depends: libqtcore4 (= 4:4.8.7+dfsg-7ubuntu1) but it is not going 
to be installed
 libzlui-qt4 : Depends: libqtcore4 (>= 4:4.7.0~beta1) but it is not going to be 
installed
 qdbus : Depends: libqtcore4 (= 4:4.8.7+dfsg-7ubuntu1) but it is not going to 
be installed
 qt-at-spi : Depends: libqtcore4 (>= 4:4.8~) but it is not going to be installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or 
specify a solution).


I had tried 
sudo apt --fix-broken install

output was

Reading package lists... Done
Building dependency tree   
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
  libzlcore-data libzlcore0.13 libzltext-data libzltext0.13 libzlui-qt4
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  libqtcore4
Suggested packages:
  libicu55
The following NEW packages will be installed:
  libqtcore4
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
14 not fully installed or removed.
Need to get 0 B/1,552 kB of archives.
After this operation, 5,084 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
(Reading database ... 158925 files and directories currently installed.)
Preparing to unpack .../libqtcore4_4%3a4.8.7+dfsg-7ubuntu1_amd64.deb ...
Unpacking libqtcore4:amd64 (4:4.8.7+dfsg-7ubuntu1) ...
dpkg: error processing archive 
/var/cache/apt/archives/libqtcore4_4%3a4.8.7+dfsg-7ubuntu1_amd64.deb (--unpack):
 trying to overwrite shared '/etc/xdg/Trolltech.conf', which is different from 
other instances of package libqtcore4:amd64
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/libqtcore4_4%3a4.8.7+dfsg-7ubuntu1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: libqtcore4 (not installed)
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
AptOrdering:
 libqtcore4:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Mon Apr 24 07:44:46 2017
DpkgHistoryLog:
 Start-Date: 2017-04-24  07:44:45
 Commandline: apt --fix-broken install
 Requested-By: sabin (1000)
 Install: libqtcore4:amd64 (4:4.8.7+dfsg-7ubuntu1, automatic)
DpkgTerminalLog:
 Preparing to unpack .../libqtcore4_4%3a4.8.7+dfsg-7ubuntu1_amd64.deb ...
 Unpacking libqtcore4:amd64 (4:4.8.7+dfsg-7ubuntu1) ...
 [1mdpkg:[0m error processing archive 
/var/cache/apt/archives/libqtcore4_4%3a4.8.7+dfsg-7ubuntu1_amd64.deb (--unpack):
  trying to overwrite shared '/etc/xdg/Trolltech.conf', which is different from 
other instances of package libqtcore4:amd64
ErrorMessage: trying to overwrite shared '/etc/xdg/Trolltech.conf', which is 
different from other instances of package libqtcore4:amd64
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: qt4-x11
Title: package libqtcore4 (not installed) failed to install/upgrade: trying to 
overwrite shared '/etc/xdg/Trolltech.conf', which is different from other 
instances of package libqtcore4:amd64
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: qt4-x11 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package zesty

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

Title:
  package libqtcore4 (not installed) failed to install/upgrade: trying
  to overwrite shared '/etc/xdg/Trolltech.conf', which is different from

[Touch-packages] [Bug 1685186] Re: Mir needs to be updated in 16.04 and the dependency tree trimmed

2017-04-23 Thread Launchpad Bug Tracker

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

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

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

Title:
  Mir needs to be updated in 16.04 and the dependency tree trimmed

Status in mir package in Ubuntu:
  Confirmed

Bug description:
  [Impact]
  Snap development using Mir has been using the "stable phone overlay" PPA 
which is both inconvenient and a legacy of the cancelled Unity8 project.

  It would greatly simplify things if Mir were updated in the Xenial
  archive.

  [Test Case]

  Build a Mir client snap (e.g. lp:~albaguirre/+snap/mir-client-demos)
  against "Primary Ubuntu Archive" and deploy as described in
  https://developer.ubuntu.com/en/snappy/guides/mir-snaps/

  Expected: the client apps start and are visible on screen
  Actual: the client don't apps start and are not visible on screen

  [Regression Potential]
  Mir has two categories of dependent project:

    1 packages related to Unity8 (and unity-system-compositor)
    2 toolkits and other "clients" of Mir

  We should remove the first category to avoid regressions as it is not
  helpful to carry these in the LTS.

  The second category is dependent only on libmirclient which is ABI
  stable.

  The principle type of regression would be FTBFS where APIs have been
  deprecated.

  notes:

  A recursive search or rdependencies identifies the following packages
  in category 1:

  camera-app-autopilot
  gallery-app-autopilot
  indicator-network-autopilot
  indicators-client
  qtdeclarative5-qtmir-plugin
  qtmir-android
  qtmir-desktop
  qtmir-tests
  ubuntu-desktop-mir
  ubuntu-experience-tests
  ubuntu-pocket-desktop
  ubuntu-push-autopilot
  ubuntu-touch
  ubuntu-touch-session
  unity8
  unity8-autopilot
  unity8-desktop-session-mir
  unity-scope-click-autopilot
  unity-system-compositor
  unity-system-compositor-autopilot

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

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

[Touch-packages] [Bug 1632772] Re: Login option 'GNOME on Wayland' does not start from LightDM

2017-04-23 Thread Daniel van Vugt

** Summary changed:

- GNOME on Wayland does not start from LightDM
+ Login option 'GNOME on Wayland' does not start from LightDM

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

Title:
  Login option 'GNOME on Wayland' does not start from LightDM

Status in Ubuntu GNOME:
  Confirmed
Status in unity8-desktop-session:
  New
Status in gnome-session package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed
Status in unity8-desktop-session package in Ubuntu:
  Confirmed

Bug description:
  When picking GNOME on Wayland as session and attempting to login from
  LightDM then it fails, all you see is a black screen with a blinking
  cursor.

  However, manually running:
  $ dbus-run-session gnome-shell --display-server --wayland
  from the console/vt1 (Ctrl+Alt+F1) seems to work.
  But from LightDM it does not work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-session-wayland 3.20.2-1ubuntu7
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Wed Oct 12 18:06:13 2016
  InstallationDate: Installed on 2013-12-26 (1020 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1685186] Re: Mir needs to be updated in 16.04 and the dependency tree trimmed

2017-04-23 Thread Daniel van Vugt

Yeah I agree. Mir lives on in a new form, and that should be without
PPAs. Thus the archive should be updated if anything Mir-related is
desired on xenial.

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

Title:
  Mir needs to be updated in 16.04 and the dependency tree trimmed

Status in mir package in Ubuntu:
  Confirmed

Bug description:
  [Impact]
  Snap development using Mir has been using the "stable phone overlay" PPA 
which is both inconvenient and a legacy of the cancelled Unity8 project.

  It would greatly simplify things if Mir were updated in the Xenial
  archive.

  [Test Case]

  Build a Mir client snap (e.g. lp:~albaguirre/+snap/mir-client-demos)
  against "Primary Ubuntu Archive" and deploy as described in
  https://developer.ubuntu.com/en/snappy/guides/mir-snaps/

  Expected: the client apps start and are visible on screen
  Actual: the client don't apps start and are not visible on screen

  [Regression Potential]
  Mir has two categories of dependent project:

    1 packages related to Unity8 (and unity-system-compositor)
    2 toolkits and other "clients" of Mir

  We should remove the first category to avoid regressions as it is not
  helpful to carry these in the LTS.

  The second category is dependent only on libmirclient which is ABI
  stable.

  The principle type of regression would be FTBFS where APIs have been
  deprecated.

  notes:

  A recursive search or rdependencies identifies the following packages
  in category 1:

  camera-app-autopilot
  gallery-app-autopilot
  indicator-network-autopilot
  indicators-client
  qtdeclarative5-qtmir-plugin
  qtmir-android
  qtmir-desktop
  qtmir-tests
  ubuntu-desktop-mir
  ubuntu-experience-tests
  ubuntu-pocket-desktop
  ubuntu-push-autopilot
  ubuntu-touch
  ubuntu-touch-session
  unity8
  unity8-autopilot
  unity8-desktop-session-mir
  unity-scope-click-autopilot
  unity-system-compositor
  unity-system-compositor-autopilot

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

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

[Touch-packages] [Bug 1632772] Re: GNOME on Wayland does not start from LightDM

2017-04-23 Thread Launchpad Bug Tracker

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

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

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

Title:
  GNOME on Wayland does not start from LightDM

Status in Ubuntu GNOME:
  Confirmed
Status in unity8-desktop-session:
  New
Status in gnome-session package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed
Status in unity8-desktop-session package in Ubuntu:
  Confirmed

Bug description:
  When picking GNOME on Wayland as session and attempting to login from
  LightDM then it fails, all you see is a black screen with a blinking
  cursor.

  However, manually running:
  $ dbus-run-session gnome-shell --display-server --wayland
  from the console/vt1 (Ctrl+Alt+F1) seems to work.
  But from LightDM it does not work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-session-wayland 3.20.2-1ubuntu7
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Wed Oct 12 18:06:13 2016
  InstallationDate: Installed on 2013-12-26 (1020 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1632772] Re: GNOME on Wayland does not start from LightDM

2017-04-23 Thread willmo

It looks like the bug is actually in unity8-desktop-session. It installs
/usr/share/lightdm/lightdm.conf.d/45-unity8.conf, which sets session-
wrapper=lightdm-unity8-session, which means lightdm-unity8-session is
run in order to start *any* session. lightdm-unity8-session is a shell
script that's also part of unity8-desktop-session, and looking at its
contents, it appears to be buggy because it assumes that any session
that doesn't use X (such as Wayland) is Unity 8 and should run upstart
instead of lightdm-session.

I was able to work around this by creating a file
/etc/lightdm/lightdm.conf.d/00-willmo.conf with contents

[Seat:*]
session-wrapper=lightdm-session

This overrides the offending setting in 45-unity8.conf and sets session-
wrapper back to the default, avoiding the Unity 8 assumptions in
lightdm-unity8-session. After rebooting, Wayland sessions now work for
me.

** Also affects: unity8-desktop-session
   Importance: Undecided
   Status: New

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

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

Title:
  GNOME on Wayland does not start from LightDM

Status in Ubuntu GNOME:
  Confirmed
Status in unity8-desktop-session:
  New
Status in gnome-session package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed
Status in unity8-desktop-session package in Ubuntu:
  Confirmed

Bug description:
  When picking GNOME on Wayland as session and attempting to login from
  LightDM then it fails, all you see is a black screen with a blinking
  cursor.

  However, manually running:
  $ dbus-run-session gnome-shell --display-server --wayland
  from the console/vt1 (Ctrl+Alt+F1) seems to work.
  But from LightDM it does not work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-session-wayland 3.20.2-1ubuntu7
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Wed Oct 12 18:06:13 2016
  InstallationDate: Installed on 2013-12-26 (1020 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Re: [Touch-packages] [Bug 1684902] Re: browser unity app crashes apparmor profile

2017-04-23 Thread Carl

Dear Seth Arnold,

You are welcome, and if I can help troubleshoot the fix, please let me
know. I have been around since Burroughs R4K and CPM-DOS 1.0, just as an
operator, but a pretty fair hand (I can follow directions about 98% of
the time... wish I could get above my life "average" of 85% LOL!).

Sincerely,

Carl

On 04/23/2017 06:00 PM, Seth Arnold wrote:
> Beautiful! Thanks Carl.
>

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

Title:
  browser unity app crashes apparmor profile

Status in apparmor package in Ubuntu:
  New
Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Integrated browser (app?) that comes pre-loaded with Ubuntu 16.04.2
  amd64 (A lightweight web browser tailored for Ubuntu, based on the
  Oxide browser engine and using the Ubuntu UI components.), Shown as
  Version 0.23+16.04.20161028-0ubuntu2, if removed from the system,
  causes apparmor to read errors in the system profile and fail to start
  (apparmor).

  I discovered that (per session), you can get apparmor to correct the
  failure and start, but as soon as you reboot, the system returns to
  the default profile set and fails to start apparmor. As far as I can
  tell, it does not indicate that the failure was caused by the browser
  uninstall, just that it failed to start for some reason.

  I tried to send this via apport, but it will not auto-locate the
  program, and since it is integrated with unity and oxide, I think it
  "sees" the program as a required OS file.

  Repaired issue by (1) Re-install browser (app?), (2) reset apparmor, (3) 
updated grub file, (4) reboot
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2017-04-12 (8 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Package: webbrowser-app
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic 
root=UUID=176948b3-104a-4075-bfbb-dbce1626a99d ro vesafb.invalid=1
  ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17
  Syslog:
   Apr 21 10:05:37 V2410US dbus[627]: [system] AppArmor D-Bus mediation is 
enabled
   Apr 21 11:15:30 V2410US dbus[665]: [system] AppArmor D-Bus mediation is 
enabled
  Tags:  xenial
  Uname: Linux 4.8.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True

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

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

86 matches

Mail list logo