[Touch-packages] [Bug 1612012] Re: Valgrind errors in NesterServer.* cause subsequent tests (ServerDisconnect, ServerStartup, UnresponsiveClient) to fail

2016-09-27 Thread Daniel van Vugt
Still happening in the 0.24 branch:

https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
mir/arch=i386,compiler=gcc,platform=mesa,release=xenial+overlay/2340/consoleFull

** Also affects: mir/0.24
   Importance: Undecided
   Status: New

** Changed in: mir/0.24
Milestone: None => 0.24.1

** Changed in: mir/0.24
   Importance: Undecided => Medium

** Changed in: mir/0.24
   Status: New => Triaged

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

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

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

** Changed in: mir/0.24
 Assignee: (unassigned) => Alexandros Frantzis (afrantzis)

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

Title:
  Valgrind errors in NesterServer.* cause subsequent tests
  (ServerDisconnect, ServerStartup, UnresponsiveClient) to fail

Status in Mir:
  Fix Committed
Status in Mir 0.24 series:
  Triaged
Status in mir package in Ubuntu:
  Triaged

Bug description:
  Tests always fail together: ServerDisconnect, ServerStartup,
  UnresponsiveClient

  17:27:52 9: [ FAILED ] 5 tests, listed below:
  17:27:52 9: [ FAILED ] ServerDisconnect.is_detected_by_client
  17:27:52 9: [ FAILED ] 
ServerDisconnect.doesnt_stop_client_calling_API_functions
  17:27:52 9: [ FAILED ] ServerStartup.creates_endpoint_on_filesystem
  17:27:52 9: [ FAILED ] 
ServerStartup.after_server_sigkilled_can_start_new_instance
  17:27:52 9: [ FAILED ] UnresponsiveClient.does_not_hang_server

  [https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  
mir/arch=amd64,compiler=clang,platform=mesa,release=vivid+overlay/1772/consoleFull]

  This is happening regularly in CI. These failures occur together.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1612012/+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 1570698] Re: CI failure in TestClientInput.receives_one_touch_event_per_frame

2016-09-27 Thread Daniel van Vugt
** Changed in: mir
   Status: Fix Committed => In Progress

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

Title:
  CI failure in TestClientInput.receives_one_touch_event_per_frame

Status in Mir:
  In Progress
Status in mir package in Ubuntu:
  Triaged

Bug description:
  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  mir/arch=i386,compiler=gcc,platform=mesa,release=xenial/863/consoleFull

  02:44:41 11: [ RUN ] TestClientInput.receives_one_touch_event_per_frame
  02:44:41 11: [2016-04-15 02:44:41.425619] mirserver: Starting
  02:44:41 11: [2016-04-15 02:44:41.430805] mirserver: Selected driver: dummy 
(version 0.22.0)
  02:44:41 11: [2016-04-15 02:44:41.499565] mirserver: Using software cursor
  02:44:41 11: [2016-04-15 02:44:41.509983] mirserver: Initial display 
configuration:
  02:44:41 11: [2016-04-15 02:44:41.510510] mirserver: 1.1: VGA 0.0" 0x0mm
  02:44:41 11: [2016-04-15 02:44:41.510809] mirserver: Current mode 1000x800 
60.00Hz
  02:44:41 11: [2016-04-15 02:44:41.511107] mirserver: Preferred mode 1000x800 
60.00Hz
  02:44:41 11: [2016-04-15 02:44:41.511379] mirserver: Logical position +0+0
  02:44:41 11: [2016-04-15 02:44:41.565602] mirserver: Selected input driver: 
mir:stub-input (version: 0.22.0)
  02:44:41 11: [2016-04-15 02:44:41.568428] mirserver: Mir version 0.22.0
  02:44:44 11: 
  02:44:44 11: GMOCK WARNING:
  02:44:44 11: Uninteresting mock function call - returning directly.
  02:44:44 11: Function call: handle_input(touch_event(when=2480338825735318 
(133.240680ms ago), from=3, touch = {{id=1, action=change, tool=finger, 
x=7.68054, y=12.2889, pressure=1, major=5, minor=8, size=8}, modifiers=1))
  02:44:44 11: Stack trace:
  02:44:44 11: 
/��BUILDDIR��/mir-0.22.0+xenial881bzr3443/tests/acceptance-tests/test_client_input.cpp:639:
 Failure
  02:44:44 11: The difference between 1.0f and client_input_events_per_frame is 
0.2400953674316, which exceeds 0.2f, where
  02:44:44 11: 1.0f evaluates to 1,
  02:44:44 11: client_input_events_per_frame evaluates to 0.7599046325684, 
and
  02:44:44 11: 0.2f evaluates to 0.2000298023224.
  02:44:44 11: 
  02:44:44 11: GMOCK WARNING:
  02:44:44 11: Uninteresting mock function call - returning directly.
  02:44:45 11: Function call: handle_input(touch_event(when=2480339119018976 
(10.576963ms ago), from=3, touch = {{id=1, action=change, tool=finger, 
x=7.80214, y=12.4834, pressure=1, major=5, minor=8, size=8}, modifiers=1))
  02:44:45 11: Stack trace:
  02:44:45 11: 
  02:44:45 11: GMOCK WARNING:
  02:44:45 11: Uninteresting mock function call - returning directly.
  02:44:45 11: Function call: handle_input(touch_event(when=2480339135968128 
(14.812916ms ago), from=3, touch = {{id=1, action=change, tool=finger, 
x=7.84436, y=12.551, pressure=1, major=5, minor=8, size=8}, modifiers=1))
  02:44:45 11: Stack trace:
  02:44:45 11: [2016-04-15 02:44:45.407565] mirserver: Stopping
  02:44:45 11: [ FAILED ] TestClientInput.receives_one_touch_event_per_frame 
(4083 ms)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1570698/+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 1609612] Re: clang builds fail (again)

2016-09-27 Thread Daniel van Vugt
** Also affects: mir (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

Title:
  clang builds fail (again)

Status in Mir:
  Fix Committed
Status in Mir 0.24 series:
  Fix Committed
Status in mir package in Ubuntu:
  Triaged

Bug description:
  clang builds fail (again) since yakkety switched to gcc 6 today.

  And I only got clang working again yesterday :(
  https://code.launchpad.net/~vanvugt/mir/fix-clang-20160803/+merge/301869

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1609612/+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 1598904] Re: X server crashes sporadically with a segfault

2016-09-27 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

** Changed in: xorg (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  X server crashes sporadically with a segfault

Status in xorg package in Ubuntu:
  Expired

Bug description:
  My desktop session crashes sporadically. Often this happens when I
  leave the computer and the screensaver starts (Euphoria GL
  screensaver). This bug is not reproducible on demand.

  Attached is my Xorg log file which seems to indicate that this problem
  is related to the i915 driver code.

  ---
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: kwin
  DistUpgraded: 2016-06-15 15:16:54,383 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:5036]
  InstallationDate: Installed on 2016-05-26 (59 days ago)
  InstallationMedia: Kubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  LightdmGreeterLog:
   QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such 
file or directory
   QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
   Bus::open: Can not get ibus-daemon's address.
   IBusInputContext::createInputContext: no connection to ibus-daemon
   file:///usr/share/kde4/apps/lightdm-kde-greeter/themes/userbar/main.qml:135: 
Unable to assign [undefined] to QString usersession
  LightdmGreeterLogOld:
   QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such 
file or directory
   QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
   Bus::open: Can not get ibus-daemon's address.
   IBusInputContext::createInputContext: no connection to ibus-daemon
   file:///usr/share/kde4/apps/lightdm-kde-greeter/themes/userbar/main.qml:135: 
Unable to assign [undefined] to QString usersession
  MachineType: LENOVO 20BWS18900
  Package: xorg 1:7.7+1ubuntu8.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.3-040603-generic 
root=UUID=285091fd-ac1a-4801-8055-c356ab9083a5 ro quiet splash vt.handoff=7
  Tags:  trusty ubuntu
  Uname: Linux 4.6.3-040603-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2016-06-15 (39 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 03/02/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET46WW (1.11 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BWS18900
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET46WW(1.11):bd03/02/2015:svnLENOVO:pn20BWS18900:pvrThinkPadT450s:rvnLENOVO:rn20BWS18900:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BWS18900
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Mon Jul 25 09:49:33 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1133
   vendor LGD
  xserver.version: 2:1.17.2-1ubuntu9.1~trusty1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1598904/+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 1607212] Re: HDMI connection issue (Ubuntu 16.04 and GeForce GTX 960M)

2016-09-27 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

** Changed in: xorg (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  HDMI connection issue (Ubuntu 16.04 and GeForce GTX 960M)

Status in xorg package in Ubuntu:
  Expired

Bug description:
  I'm working with an acer VN7-592G, with an Intel Core i7 Quad-Core-
  Prozessor and the NVIDIA GeForce GTX 960M. Since the upgrade to Ubuntu
  16.04 I have problems with the HDMI connection.

  If plugged in, the HDMI is recognised (xrandr), but the second monitor
  shows "no signal". After restarting the lightdm service (sudo service
  lightdm restart), the second monitor is working in most cases.
  Sometimes ubuntu freezes after lightdm restart and a hard reset has to
  be performed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1)
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Jul 28 08:13:41 2016
  DistUpgraded: 2016-06-05 13:36:30,607 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
     Subsystem: Acer Incorporated [ALI] Skylake Integrated Graphics [1025:1039]
     Subsystem: Acer Incorporated [ALI] GM107M [GeForce GTX 960M] [1025:1039]
  InstallationDate: Installed on 2015-11-24 (246 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Acer Aspire VN7-592G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=347e424a-f916-4ca8-a254-caa35281e9c3 ro noprompt persistent quiet 
splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-06-05 (52 days ago)
  dmi.bios.date: 09/25/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.03
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-592G
  dmi.board.vendor: Acer
  dmi.board.version: V1.03
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.03
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.03:bd09/25/2015:svnAcer:pnAspireVN7-592G:pvrV1.03:rvnAcer:rnAspireVN7-592G:rvrV1.03:cvnAcer:ct10:cvrV1.03:
  dmi.product.name: Aspire VN7-592G
  dmi.product.version: V1.03
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Jul 27 09:13:51 2016
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors: evdev: Dell Dell USB Wired Entry Keyboard: Unable to open 
evdev device "/dev/input/event7".
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1607212/+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 1607330] Re: Not possible to edit online accounts

2016-09-27 Thread Launchpad Bug Tracker
[Expired for ubuntu-system-settings-online-accounts (Ubuntu) because
there has been no activity for 60 days.]

** Changed in: ubuntu-system-settings-online-accounts (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Not possible to edit online accounts

Status in Canonical System Image:
  Incomplete
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Expired

Bug description:
  Once a user account is created its not possible to edit the
  credentials.

  For example if the user creates a google online account and later
  wants to change the password, its not possible without deleting the
  account and creating a new one.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607330/+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 1627502] Re: Black screen, cursor shown, wifi connection popup shown

2016-09-27 Thread Robert Ancell
Looking at your seat0-greeter.log seems to show something might be going
wrong with unity-settings-daemon / your X server:

(unity-settings-daemon:2377): Gdk-WARNING **: unity-settings-daemon:
Fatal IO error 11 (Resurssi ei tilapäisesti ole käytettävissä) on X
server :0.

Did you recently update any drivers?

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

Title:
  Black screen, cursor shown, wifi connection popup shown

Status in lightdm package in Ubuntu:
  New

Bug description:
  My yakkety installation is now for some reason in shape that lightdm
  only starts with a black screen, although mouse cursor is shown and
  movable and "wifi networks available" popup is shown at the top right
  corner.

  After some while this disappears and the system goes to some sort of
  tty switching loop where sometimes text cursor is shown and sometimes
  just blank screen. If I want to recover text console control of
  machine I need to quickly after booting switch to tty1 and stop
  lightdm.

  This started happening last week after some upgrades and a reboot.

  I've tried reinstalling and everything I can think of, but I can't fix
  it. Meanwhile using sddm I can't log in to Unity 7 or 8, and gdm
  doesn't start at all. So I'm using sddm + Plasma now but would like to
  be also be able to run Unity 7 and Unity 8.

  I couldn't also use ubuntu-bug since I can't use the browser interface
  from command line (otherwise it works fine until that point) and it
  segfaults under Plasma environment while collecting information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1627502/+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 1627304] Re: User locking problems - guest login crashing

2016-09-27 Thread Robert Ancell
Note you can test changes like this by running:
$ sudoedit /etc/apparmor.d/abstractions/lightdm
$ sudo systemctl reload apparmor.service

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

Title:
  User locking problems - guest login crashing

Status in apparmor package in Ubuntu:
  Invalid
Status in gnome-session package in Ubuntu:
  Incomplete
Status in lightdm package in Ubuntu:
  Triaged
Status in lightdm-gtk-greeter package in Ubuntu:
  Incomplete
Status in unity-greeter package in Ubuntu:
  Incomplete
Status in xubuntu-default-settings package in Ubuntu:
  Incomplete

Bug description:
  Vanilla Ubuntu install.

  Lock user - login to guest account, desktop crashes. Ctrl+Alt+F7
  allows you to resume user after unlocking.

  Add new user - am able to switch between locked users properly.

  Can logout of one user and be able to resume other locked session.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: lightdm 1.19.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7
  Uname: Linux 4.8.0-14-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Sep 24 13:38:09 2016
  InstallationDate: Installed on 2016-09-24 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1627304/+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 1622303] Re: Fails to unlock/ resumes to black screen

2016-09-27 Thread Robert Ancell
Sorry, didn't notice this bug go past. I can't think of anything that
would have changed in LightDM and the log isn't showing anything going
wrong. I was going to suggest you try downgrading LightDM but you've
done that. My best guess is the session / light-locker haven't realised
they've been unlocked for some reason? Either that or something to do
with VT switching (driver issues?).

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

Title:
  Fails to unlock/ resumes to black screen

Status in light-locker package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  New
Status in lightdm-gtk-greeter package in Ubuntu:
  New

Bug description:
  Lock screen (or suspend)

  System allows for password to unlock

  No desktop shown after unlocking

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xfce4-power-manager 1.4.4-4ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Sep 11 10:04:39 2016
  InstallationDate: Installed on 2016-06-11 (91 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160611)
  SourcePackage: xfce4-power-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2016-06-11 (95 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160611)
  Package: light-locker 1.7.0-2ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Tags:  yakkety
  Uname: Linux 4.4.0-9136-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1622303/+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 1627304] Re: User locking problems - guest login crashing

2016-09-27 Thread Launchpad Bug Tracker
** Branch linked: lp: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/1627304

Title:
  User locking problems - guest login crashing

Status in apparmor package in Ubuntu:
  Invalid
Status in gnome-session package in Ubuntu:
  Incomplete
Status in lightdm package in Ubuntu:
  Triaged
Status in lightdm-gtk-greeter package in Ubuntu:
  Incomplete
Status in unity-greeter package in Ubuntu:
  Incomplete
Status in xubuntu-default-settings package in Ubuntu:
  Incomplete

Bug description:
  Vanilla Ubuntu install.

  Lock user - login to guest account, desktop crashes. Ctrl+Alt+F7
  allows you to resume user after unlocking.

  Add new user - am able to switch between locked users properly.

  Can logout of one user and be able to resume other locked session.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: lightdm 1.19.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7
  Uname: Linux 4.8.0-14-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Sep 24 13:38:09 2016
  InstallationDate: Installed on 2016-09-24 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1627304/+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 1627304] Re: User locking problems - guest login crashing

2016-09-27 Thread Robert Ancell
The following fix to the abstraction seems to fix the issue:

=== modified file 'data/apparmor/abstractions/lightdm'
--- data/apparmor/abstractions/lightdm  2015-10-19 10:44:23 +
+++ data/apparmor/abstractions/lightdm  2016-09-28 03:39:54 +
@@ -95,7 +95,7 @@
   unix (receive) peer=(label=unconfined),
   unix (create),
   unix (getattr, getopt, setopt, shutdown),
-  unix (bind, listen) type=stream addr="@/com/ubuntu/upstart-session/**",
+  unix (bind, listen, accept, receive, send) type=stream 
addr="@/com/ubuntu/upstart-session/**",
   unix (bind, listen) type=stream addr="@/tmp/dbus-*",
   unix (bind, listen) type=stream addr="@/tmp/.ICE-unix/[0-9]*",
   unix (bind, listen) type=stream addr="@/dbus-vfs-daemon/*",

I figure that something (Unity?) is now making more use of the upstart
session. So we need to allow all operations on it.

I'm not an upstart expert but I figure this is safe to allow?

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

Title:
  User locking problems - guest login crashing

Status in apparmor package in Ubuntu:
  Invalid
Status in gnome-session package in Ubuntu:
  Incomplete
Status in lightdm package in Ubuntu:
  Triaged
Status in lightdm-gtk-greeter package in Ubuntu:
  Incomplete
Status in unity-greeter package in Ubuntu:
  Incomplete
Status in xubuntu-default-settings package in Ubuntu:
  Incomplete

Bug description:
  Vanilla Ubuntu install.

  Lock user - login to guest account, desktop crashes. Ctrl+Alt+F7
  allows you to resume user after unlocking.

  Add new user - am able to switch between locked users properly.

  Can logout of one user and be able to resume other locked session.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: lightdm 1.19.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7
  Uname: Linux 4.8.0-14-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Sep 24 13:38:09 2016
  InstallationDate: Installed on 2016-09-24 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1627304/+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 1451728] Re: [master] kde-config-telepathy-accounts package install error

2016-09-27 Thread Shawn
Just the answer I needed to hear to uninstall and never attempt to use
or suggest using and in fact cant uninstall it so back to the drawing
board. Better yet, to the trash with the drawing baord and back to my
beloved Windows.

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

Title:
  [master] kde-config-telepathy-accounts package install error

Status in Kubuntu PPA:
  Fix Released
Status in Telepathy KDE:
  Fix Released
Status in kaccounts-integration package in Ubuntu:
  In Progress
Status in kaccounts-providers package in Ubuntu:
  Triaged
Status in ktp-accounts-kcm package in Ubuntu:
  Triaged
Status in libaccounts-glib package in Ubuntu:
  Fix Released
Status in kaccounts-providers source package in Wily:
  Triaged
Status in ktp-accounts-kcm source package in Wily:
  Triaged

Bug description:
  Installing from Kubuntu 15.04 backports:

  Unpacking kde-config-telepathy-accounts (15.04.0-0ubuntu1~ubuntu15.04~ppa1) 
over (0.9.0-0ubuntu1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/kde-config-telepathy-accounts_15.04.0-0ubuntu1~ubuntu15.04~ppa1_amd64.deb
 (--unpack):
   trying to overwrite '/usr/share/accounts/services/facebook-im.service', 
which is also in package account-plugin-facebook 0.12+15.04.20150415.1-0ubuntu1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)

To manage notifications about this bug go to:
https://bugs.launchpad.net/kubuntu-ppa/+bug/1451728/+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 1607920] Re: zfs services fail on firstboot if zfs-utils is integrated into the deployment image

2016-09-27 Thread Eric Desrochers
** Description changed:

  [Impact]
  
   * zfs services fail on firstboot if zfs-utils is integrated into the
  deployment image.
  
   * Output from systemd -
  sudo systemctl --failed
  UNIT LOAD ACTIVE SUB DESCRIPTION
  ● zfs-import-scan.service loaded failed failed Import ZFS pools by device 
scanning
  ● zfs-mount.service loaded failed failed Mount ZFS filesystems
  
   * This is particularly frustrating for users who use automated
  monitoring as it means virtual machines must always be restarted before
  showing as clean.
  
   * This failure is due to zfs services starting up before /etc/mtab has
  a chance to be symlinked to /proc/mounts.
  
  [Test Case]
  
   1. Grab a stock xenial image, and unpack it and add zfs-utils to it.  Repack 
it.
   2. Boot machine
   3. Check systemctl --failed.
  
  [Regression Potential]
  
-  * none expected, patch has been merged upstream and ubuntu package has
- been tested by people from the community.
+  * none expected, patch has been intensively tested by the zfs test
+ scripts and then merged upstream.
+ 
+  * A ubuntu package has been tested as well by a user of the community
+ facing this bug, and confirmed it fixes the problem (see comment #7).
  
  [Other Info]
  
-  * Author: Eric Desrochers 
-  
-  * Origin: 
https://github.com/zfsonlinux/zfs/commit/792517389fad5c495a2738b61c2e9c65dedaaa9a
+  * Author: Eric Desrochers 
  
-  * Bug: https://github.com/zfsonlinux/zfs/issues/4680
+  * Origin:
+ 
https://github.com/zfsonlinux/zfs/commit/792517389fad5c495a2738b61c2e9c65dedaaa9a
+ 
+  * Bug: https://github.com/zfsonlinux/zfs/issues/4680

** Tags added: sts-sponsor sts-sru

** Description changed:

  [Impact]
  
   * zfs services fail on firstboot if zfs-utils is integrated into the
  deployment image.
  
   * Output from systemd -
  sudo systemctl --failed
  UNIT LOAD ACTIVE SUB DESCRIPTION
  ● zfs-import-scan.service loaded failed failed Import ZFS pools by device 
scanning
  ● zfs-mount.service loaded failed failed Mount ZFS filesystems
  
   * This is particularly frustrating for users who use automated
  monitoring as it means virtual machines must always be restarted before
  showing as clean.
  
   * This failure is due to zfs services starting up before /etc/mtab has
  a chance to be symlinked to /proc/mounts.
  
  [Test Case]
  
   1. Grab a stock xenial image, and unpack it and add zfs-utils to it.  Repack 
it.
   2. Boot machine
   3. Check systemctl --failed.
  
  [Regression Potential]
  
   * none expected, patch has been intensively tested by the zfs test
  scripts and then merged upstream.
  
-  * A ubuntu package has been tested as well by a user of the community
+  * A ubuntu package has been tested as well by a user of the community
  facing this bug, and confirmed it fixes the problem (see comment #7).
  
  [Other Info]
  
   * Author: Eric Desrochers 
  
-  * Origin:
+  * Upstream commit :
  
https://github.com/zfsonlinux/zfs/commit/792517389fad5c495a2738b61c2e9c65dedaaa9a
  
-  * Bug: https://github.com/zfsonlinux/zfs/issues/4680
+  * Upstream bug: https://github.com/zfsonlinux/zfs/issues/4680

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

Title:
  zfs services fail on firstboot if zfs-utils is integrated into the
  deployment image

Status in sysvinit package in Ubuntu:
  Won't Fix
Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  [Impact]

   * zfs services fail on firstboot if zfs-utils is integrated into the
  deployment image.

   * Output from systemd -
  sudo systemctl --failed
  UNIT LOAD ACTIVE SUB DESCRIPTION
  ● zfs-import-scan.service loaded failed failed Import ZFS pools by device 
scanning
  ● zfs-mount.service loaded failed failed Mount ZFS filesystems

   * This is particularly frustrating for users who use automated
  monitoring as it means virtual machines must always be restarted
  before showing as clean.

   * This failure is due to zfs services starting up before /etc/mtab
  has a chance to be symlinked to /proc/mounts.

  [Test Case]

   1. Grab a stock xenial image, and unpack it and add zfs-utils to it.  Repack 
it.
   2. Boot machine
   3. Check systemctl --failed.

  [Regression Potential]

   * none expected, patch has been intensively tested by the zfs test
  scripts and then merged upstream.

   * A ubuntu package has been tested as well by a user of the community
  facing this bug, and confirmed it fixes the problem (see comment #7).

  [Other Info]

   * Author: Eric Desrochers 

   * Upstream commit :
  
https://github.com/zfsonlinux/zfs/commit/792517389fad5c495a2738b61c2e9c65dedaaa9a

   * Upstream bug: https://github.com/zfsonlinux/zfs/issues/4680

To manage notifications about this bug go to:

[Touch-packages] [Bug 1583088] Re: Randomly corrupt characters in Unity8

2016-09-27 Thread Daniel van Vugt
Comments #11 and #12 are not this bug at all. I have hidden those now to
avoid confusion.

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

Title:
  Randomly corrupt characters in Unity8

Status in Canonical System Image:
  New
Status in gnome-desktop package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Corrupted characters in text rendering, mainly in Unity8 window
  titlebars.

  I think this is a new issue. It only started happening (on xenial
  desktop) in the past month or two.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1583088/+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 1627600] Re: unity8-dash failed to launch

2016-09-27 Thread Daniel van Vugt
** Changed in: unity-scopes-shell (Ubuntu)
   Status: Incomplete => Invalid

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

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

Title:
  unity8-dash failed to launch

Status in unity-scopes-shell package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  failed to run unity8-dash on xenial(amd64).

  
  gary@ubuntu:~$ unity8-dash --mousetouch
  [2016-09-26:14:07:25.432] QQmlApplicationEngine failed to load component
  [2016-09-26:14:07:25.432] 
file:///usr/share/unity8//Dash/DashApplication.qml:35 Type Dash unavailable
  file:///usr/share/unity8//Dash/Dash.qml:20 plugin cannot be loaded for module 
"Unity": Cannot load library 
/usr/lib/x86_64-linux-gnu/unity8/qml/Unity/libUnity-qml.so: 
(/usr/lib/x86_64-linux-gnu/unity8/qml/Unity/libUnity-qml.so: undefined symbol: 
_ZN5unity6scopes18SearchListenerBase4pushERKNSt7__cxx114listISt10shared_ptrIKNS0_10FilterBaseEESaIS7_EEE)
  .

  gary@ubuntu:~$ apt-cache policy unity8
  unity8:
Installed: 8.14+16.04.20160922-0ubuntu1
Candidate: 8.14+16.04.20160922-0ubuntu1
Version table:
   *** 8.14+16.04.20160922-0ubuntu1 500
  500 
http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu 
xenial/main amd64 Packages
  100 /var/lib/dpkg/status
   8.12+16.04.20160401-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1627600/+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 1628042] Re: Doesn't vibrate on incoming calls if "Other vibrations" not active

2016-09-27 Thread Zhang Enwei
** Changed in: usensord (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  Doesn't vibrate on incoming calls if "Other vibrations" not active

Status in Canonical System Image:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  New
Status in usensord package in Ubuntu:
  In Progress

Bug description:
  Steps:
  1. Set "Vibrate on ring" and "Vibrate in silent mode" active under "Ringtone" 
in System settings > Sound.
  2. Make sure "Other vibrations" is NOT active in System settings > Sound.
  3. Get an incoming call.

  Expected:
  Phone vibrates.

  What happens:
  Phone doesn't vibrate. If the "Other vibrations" is set active, then the 
vibration works.

  Device: E5, stable, OTA-13.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1628042/+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 1626912] Re: Rename platform 'ubuntumirclient' to 'mirclient'

2016-09-27 Thread Daniel van Vugt
** Changed in: qtubuntu
   Status: New => Confirmed

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

Title:
  Rename platform 'ubuntumirclient' to 'mirclient'

Status in qtubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Confirmed

Bug description:
  Rename platform 'ubuntumirclient' to 'mirclient' because it should not
  be ubuntu-specific, just mir-specific. If that's not true yet, we
  should work toward it...

  Certainly when upstreamed we ideally don't want Qt apps depending on
  "ubuntu". They should depend on "mir".

To manage notifications about this bug go to:
https://bugs.launchpad.net/qtubuntu/+bug/1626912/+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 1622303] Re: Fails to unlock/ resumes to black screen

2016-09-27 Thread Sean Davis
I tried downgrading lightdm (and related packages) to their xenial
versions (1.18.x) and the bug persists, so it seems less likely to be
directly related to 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/1622303

Title:
  Fails to unlock/ resumes to black screen

Status in light-locker package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  New
Status in lightdm-gtk-greeter package in Ubuntu:
  New

Bug description:
  Lock screen (or suspend)

  System allows for password to unlock

  No desktop shown after unlocking

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xfce4-power-manager 1.4.4-4ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Sep 11 10:04:39 2016
  InstallationDate: Installed on 2016-06-11 (91 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160611)
  SourcePackage: xfce4-power-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2016-06-11 (95 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160611)
  Package: light-locker 1.7.0-2ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Tags:  yakkety
  Uname: Linux 4.4.0-9136-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1622303/+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 1492252] Re: Allow direct linking to a Preview via uri

2016-09-27 Thread Brian Douglass
Thanks for the update! Out of curiosity, what sort of changes need to
happen in unity8?

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

Title:
  Allow direct linking to a Preview via uri

Status in Client Developer Experience:
  New
Status in Canonical System Image:
  Confirmed
Status in unity-scopes-api package in Ubuntu:
  Confirmed
Status in unity-scopes-shell package in Ubuntu:
  Confirmed

Bug description:
  I can already link to a scopes search via the scope:// protocol but it
  would be great to be able to link directly to a preview page via a
  scope:// uri. This would be especially helpful for uApp Explorer to
  link directly to an app in the official store (rather than the search
  page like it does now).

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-developer-experience/+bug/1492252/+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 1628306] Re: network booting fails for iscsi root if no ip is set

2016-09-27 Thread Steve Langasek
Hello Mathieu, or anyone else affected,

Accepted initramfs-tools into xenial-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/initramfs-
tools/0.122ubuntu8.3 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: initramfs-tools (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

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

Title:
  network booting fails for iscsi root if no ip is set

Status in initramfs-tools package in Ubuntu:
  In Progress
Status in initramfs-tools source package in Xenial:
  Fix Committed
Status in initramfs-tools source package in Yakkety:
  In Progress

Bug description:
  [Impact]
  Remote-root installs (eg. / over iscsi and similar) where the configuration 
is simple, and no extra parameters are included on the kernel command-line (as 
opposed to MaaS specifying everything).

  [Test case]
  1) do an installation with /boot on a local disk and / and swap over a remote 
LUN (iSCSI is simple to do).
  2) Update to initramfs-tools with isc-dhcp support.

  [Regression potential]
  This is in itself a fix for a regression found in initramfs-tools 
(0.125ubuntu4 on yakkety, or 0.122ubuntu8.2 on xenial). Failure to boot on a 
remote root filesystem would constitue a regression.

  --

  I did a new install with /boot on /dev/sda, and everything else (/ and
  swap) on an iSCSI LUN.

  Booting this with initramfs-tools using ipconfig works without issues.

  Booting this with initramfs-tools (0.125ubuntu4 on yakkety, or
  0.122ubuntu8.2 on xenial) fails because no interface is specified.

  This appears to be because ipconfig interprets "" as meaning to try
  every interface until one works (or all fail), whereas calling
  dhclient without an interface name simply returns a failure.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1628306/+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 1607920] Re: zfs services fail on firstboot if zfs-utils is integrated into the deployment image

2016-09-27 Thread Eric Desrochers
Thanks scotte for the feedbacks, I will now start the SRU process.

Eric

** Description changed:

  [Impact]
  
-  * zfs services fail on firstboot if zfs-utils is integrated into the
+  * zfs services fail on firstboot if zfs-utils is integrated into the
  deployment image.
  
-  * Output from systemd - 
- sudo systemctl --failed 
- UNIT LOAD ACTIVE SUB DESCRIPTION 
- ● zfs-import-scan.service loaded failed failed Import ZFS pools by device 
scanning 
- ● zfs-mount.service loaded failed failed Mount ZFS filesystems 
+  * Output from systemd -
+ sudo systemctl --failed
+ UNIT LOAD ACTIVE SUB DESCRIPTION
+ ● zfs-import-scan.service loaded failed failed Import ZFS pools by device 
scanning
+ ● zfs-mount.service loaded failed failed Mount ZFS filesystems
  
-  * This is particularly frustrating for users who use automated
+  * This is particularly frustrating for users who use automated
  monitoring as it means virtual machines must always be restarted before
  showing as clean.
  
-  * This failure is due to zfs services starting up before /etc/mtab has
+  * This failure is due to zfs services starting up before /etc/mtab has
  a chance to be symlinked to /proc/mounts.
  
  [Test Case]
  
-  1. Grab a stock xenial image, and unpack it and add zfs-utils to it.  Repack 
it. 
-  2. Boot machine
-  3. Check systemctl --failed.
+  1. Grab a stock xenial image, and unpack it and add zfs-utils to it.  Repack 
it.
+  2. Boot machine
+  3. Check systemctl --failed.
  
  [Regression Potential]
  
-  *
+  * none expected, patch has been merged upstream and ubuntu package has
+ been tested by people from the community.
+ 
+ [Other Info]
+ 
+  * Author: Eric Desrochers 
   
- [Other Info]
-  
-  * This can likely be resolved in the systemd init scripts, by modifying 
zfs-linux to depend on /proc/mounts instead, or inclusion of 
/lib/init/mount-functions.sh in initscripts (sysvinit).
+  * Origin: 
https://github.com/zfsonlinux/zfs/commit/792517389fad5c495a2738b61c2e9c65dedaaa9a
+ 
+  * Bug: https://github.com/zfsonlinux/zfs/issues/4680

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

Title:
  zfs services fail on firstboot if zfs-utils is integrated into the
  deployment image

Status in sysvinit package in Ubuntu:
  Won't Fix
Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  [Impact]

   * zfs services fail on firstboot if zfs-utils is integrated into the
  deployment image.

   * Output from systemd -
  sudo systemctl --failed
  UNIT LOAD ACTIVE SUB DESCRIPTION
  ● zfs-import-scan.service loaded failed failed Import ZFS pools by device 
scanning
  ● zfs-mount.service loaded failed failed Mount ZFS filesystems

   * This is particularly frustrating for users who use automated
  monitoring as it means virtual machines must always be restarted
  before showing as clean.

   * This failure is due to zfs services starting up before /etc/mtab
  has a chance to be symlinked to /proc/mounts.

  [Test Case]

   1. Grab a stock xenial image, and unpack it and add zfs-utils to it.  Repack 
it.
   2. Boot machine
   3. Check systemctl --failed.

  [Regression Potential]

   * none expected, patch has been merged upstream and ubuntu package
  has been tested by people from the community.

  [Other Info]

   * Author: Eric Desrochers 
   
   * Origin: 
https://github.com/zfsonlinux/zfs/commit/792517389fad5c495a2738b61c2e9c65dedaaa9a

   * Bug: https://github.com/zfsonlinux/zfs/issues/4680

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1607920/+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 1627942] Re: unity8 of 16.10 can't start, keep black screen, lenovo R61i

2016-09-27 Thread Golanguage
** Attachment added: "unity8-dash.log"
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1627942/+attachment/4749842/+files/unity8-dash.log

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

Title:
  unity8 of 16.10 can't start, keep black screen, lenovo R61i

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

Bug description:
  I only install openbox, LXQT and Unity8 session.
  LxQt is fine.

  After input password,
  The screen is black few seconds.
  Next in screen there are is a small rectangle with text "Scope".
  Next In the rectangle there is a ubuntu arc logo is rolling.
  Next the rolling logo is frozen.
  Next all are black few seconds.
  From a ssh console ,I can see the cpu rate of unity8, unity8.dash or applet.y 
is very high(70% --100%)

  And again and again.

  If anybody need more info, comments on the issue.
  This is its upstart.log:

  [2016-09-27:13:35:18.182] qtmir.screens: ScreensModel::ScreensModel
  [2016-09-27 13:35:18.198252] mirplatform: Found graphics driver: mir:mesa-kms 
(version 0.24.0)
  [2016-09-27 13:35:18.198494] mirplatform: Found graphics driver: mir:mesa-x11 
(version 0.24.0)
  [2016-09-27:13:35:18.200] qtmir.mir: MirServer created
  [2016-09-27:13:35:18.200] qtmir.mir: Command line arguments passed to Qt: 
("unity8", "--mode=full-shell")
  [2016-09-27:13:35:18.203] QSocketNotifier: Can only be used with threads 
started with QThread
  [2016-09-27 13:35:18.204972] mirserver: Starting
  [2016-09-27 13:35:18.254431] mirserver: Using nested cursor
  [2016-09-27 13:35:18.255972] mirserver: Initial display configuration:
  [2016-09-27 13:35:18.258509] mirserver:   0.30: LVDS 14.0" 300x190mm
  [2016-09-27 13:35:18.258591] mirserver: Current mode 1280x800 60.00Hz
  [2016-09-27 13:35:18.258637] mirserver: Preferred mode 1280x800 
60.00Hz
  [2016-09-27 13:35:18.258672] mirserver: Logical position +0+0
  [2016-09-27 13:35:18.258716] mirserver:   0.40: unused VGA
  [2016-09-27 13:35:18.258755] mirserver:   0.43: unused DVI-D
  [2016-09-27:13:35:18.259] qtmir.mir: 
PromptSessionListener::PromptSessionListener - this= 
PromptSessionListener(0x7f5b6c204630)
  [2016-09-27:13:35:18.259] qtmir.mir: SessionListener::SessionListener - this= 
SessionListener(0x7f5b6c204540)
  [2016-09-27:13:35:18.261] qtmir.mir: 
MirWindowManagerImpl::MirWindowManagerImpl
  [2016-09-27 13:35:18.263049] mirserver: Mir version 0.24.0
  [2016-09-27:13:35:18.263] qtmir.screens: QtCompositor::start
  [2016-09-27:13:35:18.342] qtmir.screens: ScreensModel::update
  [2016-09-27:13:35:18.343] qtmir.sensor: Screen - nativeOrientation is: 
Qt::ScreenOrientation(LandscapeOrientation)
  [2016-09-27:13:35:18.344] qtmir.sensor: Screen - initial currentOrientation 
is: Qt::ScreenOrientation(LandscapeOrientation)
  [2016-09-27:13:35:18.355] qtmir.screens: Added Screen with id 30 and geometry 
QRect(0,0 1280x800)
  [2016-09-27:13:35:18.355] qtmir.screens: Screen::setMirDisplayBuffer 
Screen(0x5570d2904f40) 0x7f5b6c1d2ca0 0x7f5b6c2028f0
  [2016-09-27:13:35:18.355] qtmir.screens: 
===
  [2016-09-27:13:35:18.355] qtmir.screens: Screen(0x5570d2904f40) - id: 30 
geometry: QRect(0,0 1280x800) window: 0x0 type: "LVDS" scale: 1
  [2016-09-27:13:35:18.355] qtmir.screens: 
===
  [2016-09-27:13:35:18.484] qtmir.applications: 
UnityApplicationPlugin::registerTypes - this= 
UnityApplicationPlugin(0x7f5b40047ba0) uri= Unity.Application
  [2016-09-27:13:35:20.824] Using "/etc/ubuntu/devices.conf" as device 
configuration file
  [2016-09-27:13:35:20.832] QObject: Cannot create children for a parent that 
is in a different thread.
  (Parent is DashCommunicator(0x5570d2a8fbf0), parent's thread is 
QThread(0x5570d28a83f0), current thread is DashCommunicator(0x5570d2a8fbf0)
  [2016-09-27:13:35:20.833] unity.topsurfacelist: TopLevelSurfaceList()
  [2016-09-27:13:35:20.834] qtmir.surfaces: MirSurfaceItem::MirSurfaceItem
  [2016-09-27:13:35:20.842] 
file:///usr/share/unity8//Components/Showable.qml:43: Error: Cannot assign to 
non-existent property "target"
  [2016-09-27:13:35:20.843] 
file:///usr/share/unity8//Components/Showable.qml:42: Error: Cannot assign to 
non-existent property "target"
  [2016-09-27:13:35:20.891] Fail to connect with service: 
QDBusError("org.freedesktop.DBus.Error.ServiceUnknown", "The name 
com.canonical.pim was not provided by any .service files")
  [2016-09-27:13:35:21.211] Failed to get all properties for 
"com.ubuntu.location.providers.here.AccountsService" : "No such interface"
  [2016-09-27:13:35:21.226] CursorImageProvider: "" not found (nor its 
fallbacks, if any). Going for "left_ptr" as a last resort.
  [2016-09-27:13:35:21.257] qtmir.applications: applicationManagerSingleton - 
engine= 0x5570d28e7cd0 scriptEngine= 0x5570d28e7cd0
  

[Touch-packages] [Bug 1607920] Re: zfs services fail on firstboot if zfs-utils is integrated into the deployment image

2016-09-27 Thread scotte
I tested this using my reproduction method in AWS EC2 with a test
package/PPA provided by Eric@Ubuntu (slashd) containing the commit
referenced in comment #6.

All looks good now - systemd units for ZFS no longer fail. Thanks for
moving this along!

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

Title:
  zfs services fail on firstboot if zfs-utils is integrated into the
  deployment image

Status in sysvinit package in Ubuntu:
  Won't Fix
Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  [Impact]

   * zfs services fail on firstboot if zfs-utils is integrated into the
  deployment image.

   * Output from systemd - 
  sudo systemctl --failed 
  UNIT LOAD ACTIVE SUB DESCRIPTION 
  ● zfs-import-scan.service loaded failed failed Import ZFS pools by device 
scanning 
  ● zfs-mount.service loaded failed failed Mount ZFS filesystems 

   * This is particularly frustrating for users who use automated
  monitoring as it means virtual machines must always be restarted
  before showing as clean.

   * This failure is due to zfs services starting up before /etc/mtab
  has a chance to be symlinked to /proc/mounts.

  [Test Case]

   1. Grab a stock xenial image, and unpack it and add zfs-utils to it.  Repack 
it. 
   2. Boot machine
   3. Check systemctl --failed.

  [Regression Potential]

   *
   
  [Other Info]
   
   * This can likely be resolved in the systemd init scripts, by modifying 
zfs-linux to depend on /proc/mounts instead, or inclusion of 
/lib/init/mount-functions.sh in initscripts (sysvinit).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1607920/+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 1628285] Re: apparmor should be allowed to start in containers

2016-09-27 Thread Stéphane Graber
You can check for "lxd-*" or "lxc-*", that should catch anything we do
with LXC or LXD.

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

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

Title:
  apparmor should be allowed to start in containers

Status in apparmor package in Ubuntu:
  New

Bug description:
  Now that we have support for apparmor namespacing and stacking,
  unprivileged containers can and should be allowed to load apparmor
  profiles.

  The following changes are needed at least:
   - Change the systemd unit to remove the "!container" condition
   - Change the apparmor init script, replacing the current simple container 
check for something along the lines of:
  - If /proc/self/attr/current says "unconfined"
  - And /sys/kernel/security/apparmor/features/domain/stack contains "yes"
  - And /sys/kernel/security/apparmor/features/domain/version is 1.2 or 
higher
  - Then continue execing the script, otherwise exit 0

  John suggested he could add a file which would provide a more reliable
  way to do this check ^

  
  In either case, we need this change so that containers can behave more like 
normal systems as far as apparmor is concerned. That change should also be 
SRUed back to Xenial at the same time the kernel support for stacking is pushed.

  This bug is effectively a blocker for snapd inside LXD as without
  this, snap-confine and snapd itself will not be confined after
  container restart.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1628285/+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 1625930] Re: thumbnailer FTBFS on arm64 ppc64el

2016-09-27 Thread Matthias Klose
** Changed in: gcc-6 (Ubuntu)
   Status: New => Invalid

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

Title:
  thumbnailer FTBFS on arm64 ppc64el

Status in gcc-6 package in Ubuntu:
  Invalid
Status in glibc package in Ubuntu:
  New
Status in qtbase-opensource-src package in Ubuntu:
  Incomplete
Status in thumbnailer package in Ubuntu:
  Fix Released

Bug description:
  See bug #1613561.

  --
  still ftbfs on arm64 and ppc64el, where it built before:
  https://launchpad.net/ubuntu/+source/thumbnailer/2.4+16.10.20160825-0ubuntu1
  --
  For the record, the so far included post-5.6.1 QDBus patches in our packages:

  https://codereview.qt-project.org/#/c/167480/
  https://codereview.qt-project.org/#/c/170356/

  Thiago is the main contact in upstream.
  --
  We had also problems with telepathy-qt and signon with QDBus, but two patches 
were landed that made QDBus ok with those. However, do note that the QDBus 
rewrite in Qt 5.6 from event loop based to threaded might easily require 
changes in our code, as it did for telepathy-qt:

  
http://launchpadlibrarian.net/280893997/telepathy-qt_0.9.6.1-6ubuntu1_0.9.6.1-7ubuntu2.diff.gz
  
http://launchpadlibrarian.net/284273846/telepathy-qt_0.9.6.1-7ubuntu2_0.9.6.1-9ubuntu6.diff.gz

  Maybe those could give some ideas on what to change in thumbnailer?

  --

  ...although the thumbnailer problems seems a bit different as it's
  limited to two rarer 64-bit architectures instead of happening on all
  of them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-6/+bug/1625930/+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 1613670] Re: Webview turns white after clicking on it

2016-09-27 Thread Jeremy Bicha
** Tags added: iso-testing rls-y-incoming

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

Title:
  Webview turns white after clicking on it

Status in oxide-qt package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtdeclarative-opensource-src package in Ubuntu:
  In Progress

Bug description:
  This happens on yakkety with unity7 (xcb).

  1) Go to System Settings -> Online Accounts
  2) Choose "Add account"
  3) Choose Google, Facebook, Evernote or any web-base providers
  4) Wait for the page to load
  5) Click anywhere on the page (even clicking on a scrollbar triggers this 
behaviour)

  After step 5, the webview will turn white, and apparently stop responding.
  When running signon-ui with logging enabled, one can see several warnings 
coming from Oxide:

  http://paste.ubuntu.com/23061298/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/oxide-qt/+bug/1613670/+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 1628285] Re: apparmor should be allowed to start in containers

2016-09-27 Thread Tyler Hicks
I'm willing to update the apparmor init script to fix this bug. What
pattern should I check for when examining ns_name to decide if it is an
LXC container?

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

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

Title:
  apparmor should be allowed to start in containers

Status in apparmor package in Ubuntu:
  Incomplete

Bug description:
  Now that we have support for apparmor namespacing and stacking,
  unprivileged containers can and should be allowed to load apparmor
  profiles.

  The following changes are needed at least:
   - Change the systemd unit to remove the "!container" condition
   - Change the apparmor init script, replacing the current simple container 
check for something along the lines of:
  - If /proc/self/attr/current says "unconfined"
  - And /sys/kernel/security/apparmor/features/domain/stack contains "yes"
  - And /sys/kernel/security/apparmor/features/domain/version is 1.2 or 
higher
  - Then continue execing the script, otherwise exit 0

  John suggested he could add a file which would provide a more reliable
  way to do this check ^

  
  In either case, we need this change so that containers can behave more like 
normal systems as far as apparmor is concerned. That change should also be 
SRUed back to Xenial at the same time the kernel support for stacking is pushed.

  This bug is effectively a blocker for snapd inside LXD as without
  this, snap-confine and snapd itself will not be confined after
  container restart.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1628285/+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 1624644] Re: Unable to automatically remove packages that become unused in conjunction with updating by other software

2016-09-27 Thread Alberto Salvia Novella
** Changed in: unattended-upgrades (Ubuntu)
   Importance: Undecided => High

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

Title:
  Unable to automatically remove packages that become unused in
  conjunction with updating by other software

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  When using default settings for unattended-upgrades i.e.
  Unattended-Upgrade::Remove-Unused-Dependencies "false"; 
  # default "false"
  Unattended-Upgrade::Remove-New-Unused-Dependencies "true"; 
  # default "true"
  in configuration file /etc/apt/apt.conf.d/50unattended-upgrades,
  U-U is unable to remove packages that become unused in conjunction with 
updating by other software such as update-manager or apt full-upgrade. This is 
because U-U compares the list of unneeded packages before and after it upgrades 
packages to detect which packages are new unused ones.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Sat Sep 17 11:28:44 2016
  InstallationDate: Installed on 2016-09-05 (11 days ago)
  InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1624644/+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 1628285] Re: apparmor should be allowed to start in containers

2016-09-27 Thread John Johansen
slight revision

/sys/kernel/security/apparmor/features/domain/ns_stacked   contains
yes/no if stacked across policy namespace

/sys/kernel/security/apparmor/features/domain/ns_name  contains the
name of the namespace


as long as lxc sets up a detectable namespace ns_name can be used to detect if 
it should load or not, as stacking, and stacking across namespaces will start 
to be used in other ways. So testing for just stack or ns_stack might not be 
enough

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

Title:
  apparmor should be allowed to start in containers

Status in apparmor package in Ubuntu:
  New

Bug description:
  Now that we have support for apparmor namespacing and stacking,
  unprivileged containers can and should be allowed to load apparmor
  profiles.

  The following changes are needed at least:
   - Change the systemd unit to remove the "!container" condition
   - Change the apparmor init script, replacing the current simple container 
check for something along the lines of:
  - If /proc/self/attr/current says "unconfined"
  - And /sys/kernel/security/apparmor/features/domain/stack contains "yes"
  - And /sys/kernel/security/apparmor/features/domain/version is 1.2 or 
higher
  - Then continue execing the script, otherwise exit 0

  John suggested he could add a file which would provide a more reliable
  way to do this check ^

  
  In either case, we need this change so that containers can behave more like 
normal systems as far as apparmor is concerned. That change should also be 
SRUed back to Xenial at the same time the kernel support for stacking is pushed.

  This bug is effectively a blocker for snapd inside LXD as without
  this, snap-confine and snapd itself will not be confined after
  container restart.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1628285/+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 1587142] Re: Shutdown hangs in md kworker after "Reached target Shutdown."

2016-09-27 Thread Alberto Salvia Novella
** Changed in: systemd (Ubuntu)
   Importance: Undecided => High

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

Title:
  Shutdown hangs in md kworker after "Reached target Shutdown."

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I'm booting a fully patched 16.04 from an Intel Rapid Storage
  Technology enterprise RAID1 volume (ThinkServer TS140 with two SATA
  ST1000NM0033-9ZM drives, ext4 root partition, no LVM, UEFI mode).

  If the RAID volume is recovering or resyncing for whatever reason, then `sudo 
systemctl reboot` and `sudo systemctl poweroff` work fine (I had to `sudo 
systemctl --now disable lvm2-lvmetad lvm2-lvmpolld lvm2-monitor` in order to 
consistently get that). However, once the recovery/resync is complete and 
clean, the reboot and poweroff commands above hang forever after "Reached 
target Shutdown.". Note that issuing `sudo swapoff -a` beforehand (suggested in 
the bug #1464917) does not help.
  [EDIT]Actually, the shutdown also hangs from time to time during a resync. 
But I've never seen it succeed once the resync is complete.[/EDIT]

  Then, if the server has been forcibly restarted with the power button,
  the Intel Matrix Storage Manager indicates a "Normal" status for the
  RAID1 volume, but Ubuntu then resyncs the volume anyway:

  [1.223649] md: bind
  [1.228426] md: bind
  [1.230030] md: bind
  [1.230738] md: bind
  [1.232985] usbcore: registered new interface driver usbhid
  [1.233494] usbhid: USB HID core driver
  [1.234022] md: raid1 personality registered for level 1
  [1.234876] md/raid1:md126: not clean -- starting background reconstruction
  [1.234956] input: CHESEN USB Keyboard as 
/devices/pci:00/:00:14.0/usb3/3-10/3-10:1.0/0003:0A81:0101.0001/input/input5
  [1.236273] md/raid1:md126: active with 2 out of 2 mirrors
  [1.236797] md126: detected capacity change from 0 to 1000202043392
  [1.246271] md: md126 switched to read-write mode.
  [1.246834] md: resync of RAID array md126
  [1.247325] md: minimum _guaranteed_  speed: 1000 KB/sec/disk.
  [1.247503]  md126: p1 p2 p3 p4
  [1.248269] md: using maximum available idle IO bandwidth (but not more 
than 20 KB/sec) for resync.
  [1.248774] md: using 128k window, over a total of 976759940k.

  Note that the pain of "resync upon every (re)boot" cannot even be a
  bit relieved thanks to bitmaps because mdadm does not support them for
  IMSM containers:

  $ sudo mdadm --grow --bitmap=internal /dev/md126
  mdadm: Cannot add bitmaps to sub-arrays yet

  I also get this in syslog during boot when the individual drives are
  detected, but this seems to be harmless:

  May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/sbin/mdadm --incremental 
/dev/sdb --offroot' failed with exit code 1.
  May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/lib/udev/hdparm' failed 
with exit code 1.

  May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/sbin/mdadm --incremental 
/dev/sda --offroot' failed with exit code 1.
  May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/lib/udev/hdparm' failed 
with exit code 1.

  During a resync, `sudo sh -c 'echo idle >
  /sys/block/md126/md/sync_action'` actually stops it as expected, but
  it restarts immediately though nothing seems to have triggered it:

  May 30 18:17:02 wssrv1 kernel: [ 3106.826710] md: md126: resync interrupted.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836320] md: checkpointing resync of 
md126.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836623] md: resync of RAID array md126
  May 30 18:17:02 wssrv1 kernel: [ 3106.836625] md: minimum _guaranteed_  
speed: 1000 KB/sec/disk.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836626] md: using maximum available 
idle IO bandwidth (but not more than 20 KB/sec) for resync.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836627] md: using 128k window, over a 
total of 976759940k.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836628] md: resuming resync of md126 
from checkpoint.
  May 30 18:17:02 wssrv1 mdadm[982]: RebuildStarted event detected on md device 
/dev/md/Volume0

  I attach screenshots of the hanging shutdown log after a `sudo sh -c 'echo 8 
> /proc/sys/kernel/printk'`. The second screenshot shows that the kernel has 
deadlocked in md_write_start(). Note that `sudo systemctl start debug-shell` is 
unusable on this machine at this point because Ctrl+Alt+F9 brings tty9 without 
any keyboard.
  [EDIT]But I can still switch back to tty1.[/EDIT]

  I have also tried with much lower values for vm.dirty_background_ratio
  and vm.dirty_ratio, but to no avail.

  Linux 4.6.0-040600-generic_4.6.0-040600.201605151930_amd64 from
  http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety/ did not
  help either.

  More information below:

  $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  $ 

[Touch-packages] [Bug 1572199] Re: cups 2.1.3-4 causes Lubuntu 16.04 to hang on shutdown

2016-09-27 Thread Alberto Salvia Novella
** Changed in: cups (Ubuntu)
   Importance: Undecided => High

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

Title:
  cups 2.1.3-4 causes Lubuntu 16.04 to hang on shutdown

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  cups 2.1.3-3 does not have this problem.  Confirmed on 32 bit virtual
  and real machines.  Problem was reported on VM.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic i686
  ApportVersion: 2.20-0ubuntu3
  Architecture: i386
  CasperVersion: 1.368
  CupsErrorLog:
   
  CurrentDesktop: LXDE
  Date: Tue Apr 19 15:12:05 2016
  LiveMediaBuild: Lubuntu 16.04 LTS "Xenial Xerus" - Beta i386 (20160323)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Papersize: a4
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash ---
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1572199/+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 1628314] [NEW] Cups trouble shooter asked me to run a command that doesn't work

2016-09-27 Thread david braun
Public bug reported:

The Cups trouble shooter claimed it couldn't find log files saying it was 
possible the it wasn't running as an administrator (which was correct). It 
asked me to run
   su -c 'journalctl -u cups.service --since="None" --until="2016-09-27 
18:17:05"' > troubleshoot-logs.txt
which failed for 2 reasons
1. I don't know the cups.service password (so I ran the command as root)
2. the None specification for "--since" is not valid

Also the cups logs showed that cups couldn't create
/var/spool/cups/tmp/.hplip but didn't say what caused the failure (turns
out it already existed - shouldn't be an error!)

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: cups 2.1.3-4
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Sep 27 18:41:10 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-05-31 (485 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 0bda:57b5 Realtek Semiconductor Corp. 
 Bus 001 Device 005: ID 03f0:0317 Hewlett-Packard LaserJet 1200
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. X551MA
Papersize: letter
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=dadede94-9cd3-484a-963a-db3e27379a9b ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: Upgraded to xenial on 2016-08-04 (54 days ago)
dmi.bios.date: 08/12/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X551MA.512
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X551MA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX551MA.512:bd08/12/2014:svnASUSTeKCOMPUTERINC.:pnX551MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX551MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: X551MA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug xenial

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

Title:
  Cups trouble shooter asked me to run a command that doesn't work

Status in cups package in Ubuntu:
  New

Bug description:
  The Cups trouble shooter claimed it couldn't find log files saying it was 
possible the it wasn't running as an administrator (which was correct). It 
asked me to run
 su -c 'journalctl -u cups.service --since="None" --until="2016-09-27 
18:17:05"' > troubleshoot-logs.txt
  which failed for 2 reasons
  1. I don't know the cups.service password (so I ran the command as root)
  2. the None specification for "--since" is not valid

  Also the cups logs showed that cups couldn't create
  /var/spool/cups/tmp/.hplip but didn't say what caused the failure
  (turns out it already existed - shouldn't be an error!)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Sep 27 18:41:10 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-05-31 (485 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:57b5 Realtek Semiconductor Corp. 
   Bus 001 Device 005: ID 03f0:0317 Hewlett-Packard LaserJet 1200
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X551MA
  Papersize: letter
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=dadede94-9cd3-484a-963a-db3e27379a9b ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: Upgraded to xenial on 2016-08-04 (54 days ago)
  dmi.bios.date: 08/12/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X551MA.512
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X551MA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX551MA.512:bd08/12/2014:svnASUSTeKCOMPUTERINC.:pnX551MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX551MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X551MA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:

[Touch-packages] [Bug 1628315] [NEW] Add the possibility to create groups of contacts

2016-09-27 Thread Antoine Motte dit Falisse
Public bug reported:

Add the possibility to create groups of contacts, and a way to send a
message directly to every people in a group.

** Affects: address-book-app (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: contact group ota14

** Tags added: ota14

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

Title:
  Add the possibility to create groups of contacts

Status in address-book-app package in Ubuntu:
  New

Bug description:
  Add the possibility to create groups of contacts, and a way to send a
  message directly to every people in a group.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/address-book-app/+bug/1628315/+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 1628306] [NEW] network booting fails for iscsi root if no ip is set

2016-09-27 Thread Mathieu Trudel-Lapierre
Public bug reported:

[Impact]
Remote-root installs (eg. / over iscsi and similar) where the configuration is 
simple, and no extra parameters are included on the kernel command-line (as 
opposed to MaaS specifying everything).

[Test case]
1) do an installation with /boot on a local disk and / and swap over a remote 
LUN (iSCSI is simple to do).
2) Update to initramfs-tools with isc-dhcp support.

[Regression potential]
This is in itself a fix for a regression found in initramfs-tools (0.125ubuntu4 
on yakkety, or 0.122ubuntu8.2 on xenial). Failure to boot on a remote root 
filesystem would constitue a regression.

--

I did a new install with /boot on /dev/sda, and everything else (/ and
swap) on an iSCSI LUN.

Booting this with initramfs-tools using ipconfig works without issues.

Booting this with initramfs-tools (0.125ubuntu4 on yakkety, or
0.122ubuntu8.2 on xenial) fails because no interface is specified.

This appears to be because ipconfig interprets "" as meaning to try
every interface until one works (or all fail), whereas calling dhclient
without an interface name simply returns a failure.

** Affects: initramfs-tools (Ubuntu)
 Importance: Critical
 Assignee: Mathieu Trudel-Lapierre (cyphermox)
 Status: In Progress

** Affects: initramfs-tools (Ubuntu Xenial)
 Importance: Critical
 Assignee: Mathieu Trudel-Lapierre (cyphermox)
 Status: In Progress

** Affects: initramfs-tools (Ubuntu Yakkety)
 Importance: Critical
 Assignee: Mathieu Trudel-Lapierre (cyphermox)
 Status: In Progress

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Triaged

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => Critical

** Changed in: initramfs-tools (Ubuntu)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)

** Also affects: initramfs-tools (Ubuntu Yakkety)
   Importance: Critical
 Assignee: Mathieu Trudel-Lapierre (cyphermox)
   Status: Triaged

** Also affects: initramfs-tools (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: initramfs-tools (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: initramfs-tools (Ubuntu Xenial)
   Importance: Undecided => Critical

** Changed in: initramfs-tools (Ubuntu Xenial)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)

** Changed in: initramfs-tools (Ubuntu Xenial)
   Status: Triaged => In Progress

** Changed in: initramfs-tools (Ubuntu Yakkety)
   Status: Triaged => In Progress

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

Title:
  network booting fails for iscsi root if no ip is set

Status in initramfs-tools package in Ubuntu:
  In Progress
Status in initramfs-tools source package in Xenial:
  In Progress
Status in initramfs-tools source package in Yakkety:
  In Progress

Bug description:
  [Impact]
  Remote-root installs (eg. / over iscsi and similar) where the configuration 
is simple, and no extra parameters are included on the kernel command-line (as 
opposed to MaaS specifying everything).

  [Test case]
  1) do an installation with /boot on a local disk and / and swap over a remote 
LUN (iSCSI is simple to do).
  2) Update to initramfs-tools with isc-dhcp support.

  [Regression potential]
  This is in itself a fix for a regression found in initramfs-tools 
(0.125ubuntu4 on yakkety, or 0.122ubuntu8.2 on xenial). Failure to boot on a 
remote root filesystem would constitue a regression.

  --

  I did a new install with /boot on /dev/sda, and everything else (/ and
  swap) on an iSCSI LUN.

  Booting this with initramfs-tools using ipconfig works without issues.

  Booting this with initramfs-tools (0.125ubuntu4 on yakkety, or
  0.122ubuntu8.2 on xenial) fails because no interface is specified.

  This appears to be because ipconfig interprets "" as meaning to try
  every interface until one works (or all fail), whereas calling
  dhclient without an interface name simply returns a failure.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1628306/+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 1628295] Re: Change in kernel stacking behavior causes regression tests to fail

2016-09-27 Thread Launchpad Bug Tracker
** Branch linked: lp:~apparmor-dev/apparmor/apparmor-ubuntu-citrain

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

Title:
  Change in kernel stacking behavior causes regression tests to fail

Status in apparmor package in Ubuntu:
  In Progress
Status in apparmor source package in Trusty:
  New
Status in apparmor source package in Xenial:
  New
Status in apparmor source package in Yakkety:
  In Progress

Bug description:
  [Impact]

   * Two regression tests fail due to a behavior change in recent Xenial
  and Yakkety kernels

   * Adjusting the regression tests appropriately allows the kernel and
  security teams to use QRT's test-apparmor.py to test kernel and
  userspace AppArmor changes with confidence

  [Test Case]

  $ apt-get source apparmor
  $ cd tests/regression/apparmor
  $ make USE_SYSTEM=1
  $ sudo bash stackonexec.sh
  Error: transition failed. Test 'STACKONEXEC (stacked with unconfined - 
okcon)' was expected to 'pass'. Reason for failure 'FAIL - current mode 
"enforce" != expected_mode "mixed"'
  Error: transition passed. Test 'STACKONEXEC (stacked with unconfined - bad 
mode)' was expected to 'fail'
  $ sudo bash stackprofile.sh
  Error: transition failed. Test 'STACKPROFILE (stacked with unconfined - 
okcon)' was expected to 'pass'. Reason for failure 'FAIL - current mode 
"enforce" != expected_mode "mixed"'

  The two previous commands should result in no output and return value of 0 
once
  the regression test is properly updated.

  [Regression Potential]

   * This is an extremely low risk change since it only touches
  regression testing code that is not user-facing.

  [Other Info]

   * This bug has already been fixed upstream:

 https://bazaar.launchpad.net/~apparmor-
  dev/apparmor/master/revision/3505

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1628295/+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 1613561] Re: [MIR] thumbnailer

2016-09-27 Thread Michi Henning
Looks like 1991 has landed now.

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

Title:
  [MIR] thumbnailer

Status in thumbnailer package in Ubuntu:
  Incomplete

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by many Ubuntu Touch applications and scopes, 
such as gallery app, music app, today scope, music scope, etc.

  [Security]
   * No known security issues at this time. It has been reviewed by security in 
the past for use on the phone.

  [Quality assurance]
   * This package has unit tests.

  [Dependencies]
   Most dependencies are already in main with the exception of the following:
   * libboost-filesystem-dev
   * libunity-api-dev (Bug #1613563)
   * persistent-cache-cpp-dev (Bug #1613560)

   Note that the package has other dependencies that are not in main,
  but these are used only for the tests and are not runtime
  dependencies.

  [Standards compliance]
   * This package uses cmake.

  [Maintenance]
   * This package is maintained by Canonical and actively in use on the phone 
images.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thumbnailer/+bug/1613561/+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 1625930] Re: thumbnailer FTBFS on arm64 ppc64el

2016-09-27 Thread Michi Henning
** Changed in: thumbnailer (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  thumbnailer FTBFS on arm64 ppc64el

Status in gcc-6 package in Ubuntu:
  New
Status in glibc package in Ubuntu:
  New
Status in qtbase-opensource-src package in Ubuntu:
  Incomplete
Status in thumbnailer package in Ubuntu:
  Fix Released

Bug description:
  See bug #1613561.

  --
  still ftbfs on arm64 and ppc64el, where it built before:
  https://launchpad.net/ubuntu/+source/thumbnailer/2.4+16.10.20160825-0ubuntu1
  --
  For the record, the so far included post-5.6.1 QDBus patches in our packages:

  https://codereview.qt-project.org/#/c/167480/
  https://codereview.qt-project.org/#/c/170356/

  Thiago is the main contact in upstream.
  --
  We had also problems with telepathy-qt and signon with QDBus, but two patches 
were landed that made QDBus ok with those. However, do note that the QDBus 
rewrite in Qt 5.6 from event loop based to threaded might easily require 
changes in our code, as it did for telepathy-qt:

  
http://launchpadlibrarian.net/280893997/telepathy-qt_0.9.6.1-6ubuntu1_0.9.6.1-7ubuntu2.diff.gz
  
http://launchpadlibrarian.net/284273846/telepathy-qt_0.9.6.1-7ubuntu2_0.9.6.1-9ubuntu6.diff.gz

  Maybe those could give some ideas on what to change in thumbnailer?

  --

  ...although the thumbnailer problems seems a bit different as it's
  limited to two rarer 64-bit architectures instead of happening on all
  of them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-6/+bug/1625930/+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 1628161] Re: SlotsLayout height is not dynamically updated when main paddings change

2016-09-27 Thread Andrea Bernabei
Here is a report of my investigation and my chat with Marco this
afternoon:

The problem is topChanged and bottomChanged are connected to _q_relayout().
The relayout function does the relayout of the element, it doesn't update the 
height of the layout.

They should instead trigger _q_updateSize(), that will call
_q_relayout() after updating the size.

There were already functionality and unit tests in place that ensure
that the height is updated whenever the slot-specific paddings change.

There was a test checking that having the "global" top/bottom padding 
*initialized* to a *custom* value would produce a layout with the correct 
height, but there was no test checking that *changing
* the global padding *after* initialization would update the layout height.

Well spotted, and sorry for the inconvenience, Marco!

Thanks a ton for the fix and the unit test! :)

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

Title:
  SlotsLayout height is not dynamically updated when main paddings
  change

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  You can see this in the attached testcase.

  When paddings are changed, the SlotsLayout height is not updated
  dynamically.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1628161/+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 1611680] Re: Scrolling on www.ceskenoviny.cz is very slow

2016-09-27 Thread Olivier Tilloy
** Changed in: webbrowser-app (Ubuntu)
   Status: Confirmed => In Progress

** Branch linked: lp:~osomon/webbrowser-app/loadEvent-optimizations

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

Title:
  Scrolling on  www.ceskenoviny.cz is very slow

Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  Hello,
  the Czech news site I am reading quite often was recently updated to a new 
design and as of this update scrolling on the site gets quite tricky. On some 
articles scrolling is almost impossible.

  Now this is not the first site I find difficult to scroll on with an
  Ubuntu's web browser unfortunately, though it is usually the case of
  some heavy javascript ballast on the site I am sure.

  The worst experience I am getting so far is on this article:
  http://www.ceskenoviny.cz/zpravy/francouzska-justice-obvinila-16letou-
  divku-z-planovani-teroru/1379685 where scrolling is very laggy and
  more or less only gets me either to the absolute top or the absolute
  bottom of the article, not anywhere in the middle. Slow scrolling
  won't help the issue.

  Other articles like this one http://www.ceskenoviny.cz/zpravy/ceske-
  drahy-dostaly-pokutu-150-000-kc-za-chybejici-ceniky/1380181 feels only
  very laggy but not that bad from my experience.

  I've been testing this on my Meizu MX4 with rc-proposed. Maybe this is
  only the device issue though I doubt it.

  Is there something you can do about it?
  Thank you very much.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1611680/+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 1628295] [NEW] Change in kernel stacking behavior causes regression tests to fail

2016-09-27 Thread Tyler Hicks
Public bug reported:

[Impact]

 * Two regression tests fail due to a behavior change in recent Xenial
and Yakkety kernels

 * Adjusting the regression tests appropriately allows the kernel and
security teams to use QRT's test-apparmor.py to test kernel and
userspace AppArmor changes with confidence

[Test Case]

$ apt-get source apparmor
$ cd tests/regression/apparmor
$ make USE_SYSTEM=1
$ sudo bash stackonexec.sh
Error: transition failed. Test 'STACKONEXEC (stacked with unconfined - okcon)' 
was expected to 'pass'. Reason for failure 'FAIL - current mode "enforce" != 
expected_mode "mixed"'
Error: transition passed. Test 'STACKONEXEC (stacked with unconfined - bad 
mode)' was expected to 'fail'
$ sudo bash stackprofile.sh
Error: transition failed. Test 'STACKPROFILE (stacked with unconfined - okcon)' 
was expected to 'pass'. Reason for failure 'FAIL - current mode "enforce" != 
expected_mode "mixed"'

The two previous commands should result in no output and return value of 0 once
the regression test is properly updated.

[Regression Potential]

 * This is an extremely low risk change since it only touches regression
testing code that is not user-facing.

[Other Info]

 * This bug has already been fixed upstream:

   https://bazaar.launchpad.net/~apparmor-
dev/apparmor/master/revision/3505

** Affects: apparmor (Ubuntu)
 Importance: Low
 Assignee: Tyler Hicks (tyhicks)
 Status: In Progress

** Affects: apparmor (Ubuntu Trusty)
 Importance: Low
 Assignee: Tyler Hicks (tyhicks)
 Status: New

** Affects: apparmor (Ubuntu Xenial)
 Importance: Low
 Assignee: Tyler Hicks (tyhicks)
 Status: New

** Affects: apparmor (Ubuntu Yakkety)
 Importance: Low
 Assignee: Tyler Hicks (tyhicks)
 Status: In Progress

** Also affects: apparmor (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: apparmor (Ubuntu Yakkety)
   Importance: Low
 Assignee: Tyler Hicks (tyhicks)
   Status: In Progress

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

** Changed in: apparmor (Ubuntu Xenial)
   Importance: Undecided => Low

** Changed in: apparmor (Ubuntu Trusty)
   Importance: Undecided => Low

** Changed in: apparmor (Ubuntu Xenial)
 Assignee: (unassigned) => Tyler Hicks (tyhicks)

** Changed in: apparmor (Ubuntu Trusty)
 Assignee: (unassigned) => Tyler Hicks (tyhicks)

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

Title:
  Change in kernel stacking behavior causes regression tests to fail

Status in apparmor package in Ubuntu:
  In Progress
Status in apparmor source package in Trusty:
  New
Status in apparmor source package in Xenial:
  New
Status in apparmor source package in Yakkety:
  In Progress

Bug description:
  [Impact]

   * Two regression tests fail due to a behavior change in recent Xenial
  and Yakkety kernels

   * Adjusting the regression tests appropriately allows the kernel and
  security teams to use QRT's test-apparmor.py to test kernel and
  userspace AppArmor changes with confidence

  [Test Case]

  $ apt-get source apparmor
  $ cd tests/regression/apparmor
  $ make USE_SYSTEM=1
  $ sudo bash stackonexec.sh
  Error: transition failed. Test 'STACKONEXEC (stacked with unconfined - 
okcon)' was expected to 'pass'. Reason for failure 'FAIL - current mode 
"enforce" != expected_mode "mixed"'
  Error: transition passed. Test 'STACKONEXEC (stacked with unconfined - bad 
mode)' was expected to 'fail'
  $ sudo bash stackprofile.sh
  Error: transition failed. Test 'STACKPROFILE (stacked with unconfined - 
okcon)' was expected to 'pass'. Reason for failure 'FAIL - current mode 
"enforce" != expected_mode "mixed"'

  The two previous commands should result in no output and return value of 0 
once
  the regression test is properly updated.

  [Regression Potential]

   * This is an extremely low risk change since it only touches
  regression testing code that is not user-facing.

  [Other Info]

   * This bug has already been fixed upstream:

 https://bazaar.launchpad.net/~apparmor-
  dev/apparmor/master/revision/3505

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1628295/+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 1622002] Fix included in openstack/neutron 9.0.0.0rc2

2016-09-27 Thread OpenStack Infra
This issue was fixed in the openstack/neutron 9.0.0.0rc2 release
candidate.

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

Title:
  dhcp_release6 can be called when it is not present

Status in neutron:
  Fix Released
Status in dnsmasq package in Ubuntu:
  New

Bug description:
  If someone enables dhcpv6-stateful addressing on a subnet, but they
  are running an old version of dnsmasq (<2.76), then the dhcp agent
  could try and run dhcp_release6 even though it isn't present.  An
  example:

  http://logs.openstack.org/53/365653/5/check/gate-tempest-dsvm-neutron-
  multinode-full-ubuntu-
  xenial/813d16d/logs/screen-q-dhcp.txt.gz#_2016-09-06_11_40_02_272

  Checking it's present first would fix this problem.

  Since the change to call dhcp_release6 was just added in
  https://review.openstack.org/#/c/301747/ we should fix this before
  Newton ships and people complain.

  There is also an effort to get Cirros to support DHCPv6 so that we can test 
this in the gate,
  https://bugs.launchpad.net/cirros/+bug/1487041 - hopefully that gets done so 
we can add a functional test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1622002/+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 1583088] Re: Randomly corrupt characters in Unity8

2016-09-27 Thread draco
Screenshot on comment 12 seems very close to behaviour in bug #1573959 ,
which is present only on Intel graphic cards. Could it be the same bug ?

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

Title:
  Randomly corrupt characters in Unity8

Status in Canonical System Image:
  New
Status in gnome-desktop package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Corrupted characters in text rendering, mainly in Unity8 window
  titlebars.

  I think this is a new issue. It only started happening (on xenial
  desktop) in the past month or two.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1583088/+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 1626808] Re: Unable to log in from bq Aquaris tablet

2016-09-27 Thread Mark Anson
Rodney,

Thank you for looking into this.

Mark

On Wed, Sep 28, 2016 at 3:03 AM, Rodney Dawes <1626...@bugs.launchpad.net>
wrote:

> Setting this to invalid then, as the problem seems to have resolved
> itself per comment #6.
>
> ** Changed in: ubuntuone-credentials (Ubuntu)
>Status: New => Invalid
>
> ** Changed in: canonical-identity-provider
>Status: New => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1626808
>
> Title:
>   Unable to log in from bq Aquaris tablet
>
> Status in Canonical SSO provider:
>   Invalid
> Status in ubuntuone-credentials package in Ubuntu:
>   Invalid
>
> Bug description:
>   Hi
>
>   I have five Aquaris tablets I am installing some new products I have
>   built onto.
>
>   On one tablet, when I try to log in to the Ubuntu One so I can get the
>   terminal app, I enter my email and password (correct) to log in, but I
>   am not logged in and the terminal app does not download.
>
>   Without the terminal app installed I cannot run any diagnostics or get
>   any information about what is going wrong.
>
>   This setup, where terminal is not on the Tablet OS by default, totally
>   SUCKS.
>
>   I need support urgently.
>
>   I cannot provide log files to you or anything else. Presumably the
>   Ubuntu Web web site logs will say that I am trying to log in from a
>   Tablet device. I wish I had some logs myself...
>
>   Mark Anson
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/canonical-identity-provider/+
> bug/1626808/+subscriptions
>


-- 

Mobile 0423 799 972


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

Title:
  Unable to log in from bq Aquaris tablet

Status in Canonical SSO provider:
  Invalid
Status in ubuntuone-credentials package in Ubuntu:
  Invalid

Bug description:
  Hi

  I have five Aquaris tablets I am installing some new products I have
  built onto.

  On one tablet, when I try to log in to the Ubuntu One so I can get the
  terminal app, I enter my email and password (correct) to log in, but I
  am not logged in and the terminal app does not download.

  Without the terminal app installed I cannot run any diagnostics or get
  any information about what is going wrong.

  This setup, where terminal is not on the Tablet OS by default, totally
  SUCKS.

  I need support urgently.

  I cannot provide log files to you or anything else. Presumably the
  Ubuntu Web web site logs will say that I am trying to log in from a
  Tablet device. I wish I had some logs myself...

  Mark Anson

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-identity-provider/+bug/1626808/+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 1628042] Re: Doesn't vibrate on incoming calls if "Other vibrations" not active

2016-09-27 Thread Pat McGowan
usensord only has an exception for the osk,  but there are 2 other cases
where we have separate settings which is for calls and messages. These
settings are in the account service and not passed to usensord.  Seems
easiest to add exceptions for whatever processes are making those
requests.

Longer term we should consider moving all these settings to usensord and
adding corresponding methods to the dbus interface.

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

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

** Changed in: usensord (Ubuntu)
 Assignee: (unassigned) => Zhang Enwei (zhangew401)

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Yuan-Chen Cheng (ycheng-twn)

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

Title:
  Doesn't vibrate on incoming calls if "Other vibrations" not active

Status in Canonical System Image:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  New
Status in usensord package in Ubuntu:
  Confirmed

Bug description:
  Steps:
  1. Set "Vibrate on ring" and "Vibrate in silent mode" active under "Ringtone" 
in System settings > Sound.
  2. Make sure "Other vibrations" is NOT active in System settings > Sound.
  3. Get an incoming call.

  Expected:
  Phone vibrates.

  What happens:
  Phone doesn't vibrate. If the "Other vibrations" is set active, then the 
vibration works.

  Device: E5, stable, OTA-13.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1628042/+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 1628042] Re: Doesn't vibrate on incoming calls if "Other vibrations" not active

2016-09-27 Thread Pat McGowan
** Also affects: usensord (Ubuntu)
   Importance: Undecided
   Status: New

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

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

** Changed in: canonical-devices-system-image
Milestone: None => 14

** Tags added: regression-proposed

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

Title:
  Doesn't vibrate on incoming calls if "Other vibrations" not active

Status in Canonical System Image:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  New
Status in usensord package in Ubuntu:
  New

Bug description:
  Steps:
  1. Set "Vibrate on ring" and "Vibrate in silent mode" active under "Ringtone" 
in System settings > Sound.
  2. Make sure "Other vibrations" is NOT active in System settings > Sound.
  3. Get an incoming call.

  Expected:
  Phone vibrates.

  What happens:
  Phone doesn't vibrate. If the "Other vibrations" is set active, then the 
vibration works.

  Device: E5, stable, OTA-13.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1628042/+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 1628285] [NEW] apparmor should be allowed to start in containers

2016-09-27 Thread Stéphane Graber
Public bug reported:

Now that we have support for apparmor namespacing and stacking,
unprivileged containers can and should be allowed to load apparmor
profiles.

The following changes are needed at least:
 - Change the systemd unit to remove the "!container" condition
 - Change the apparmor init script, replacing the current simple container 
check for something along the lines of:
- If /proc/self/attr/current says "unconfined"
- And /sys/kernel/security/apparmor/features/domain/stack contains "yes"
- And /sys/kernel/security/apparmor/features/domain/version is 1.2 or higher
- Then continue execing the script, otherwise exit 0

John suggested he could add a file which would provide a more reliable
way to do this check ^


In either case, we need this change so that containers can behave more like 
normal systems as far as apparmor is concerned. That change should also be 
SRUed back to Xenial at the same time the kernel support for stacking is pushed.

This bug is effectively a blocker for snapd inside LXD as without this,
snap-confine and snapd itself will not be confined after container
restart.

** Affects: apparmor (Ubuntu)
 Importance: High
 Status: New


** Tags: lxd

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

** Tags added: lxd

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

Title:
  apparmor should be allowed to start in containers

Status in apparmor package in Ubuntu:
  New

Bug description:
  Now that we have support for apparmor namespacing and stacking,
  unprivileged containers can and should be allowed to load apparmor
  profiles.

  The following changes are needed at least:
   - Change the systemd unit to remove the "!container" condition
   - Change the apparmor init script, replacing the current simple container 
check for something along the lines of:
  - If /proc/self/attr/current says "unconfined"
  - And /sys/kernel/security/apparmor/features/domain/stack contains "yes"
  - And /sys/kernel/security/apparmor/features/domain/version is 1.2 or 
higher
  - Then continue execing the script, otherwise exit 0

  John suggested he could add a file which would provide a more reliable
  way to do this check ^

  
  In either case, we need this change so that containers can behave more like 
normal systems as far as apparmor is concerned. That change should also be 
SRUed back to Xenial at the same time the kernel support for stacking is pushed.

  This bug is effectively a blocker for snapd inside LXD as without
  this, snap-confine and snapd itself will not be confined after
  container restart.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1628285/+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 1377996] Re: dialer is freezing on active call screen

2016-09-27 Thread Pat McGowan
*** This bug is a duplicate of bug 1576989 ***
https://bugs.launchpad.net/bugs/1576989

** This bug has been marked a duplicate of bug 1576989
   stale lock files freeze apps

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

Title:
  dialer is  freezing on active call screen

Status in Canonical System Image:
  Incomplete
Status in Ubuntu UX:
  Fix Committed
Status in dialer-app package in Ubuntu:
  Incomplete
Status in unity-mir package in Ubuntu:
  Incomplete

Bug description:
  Steps to reproduce:
  1. phone device (make sure phone app is not running & the device is awake)
  2. accept the call from the incoming snap decision
  3. wait until active call screen appears
  4. navigate back to the keypad 
  5. tap the now green indicator bar to return back to call
  6. tap the tone dial in call controls

  7. Actual result: One the first, 2nd or 3rd tap the screen is frozen. Even if 
you hang up the phone you called from, the screen remains. Sometimes the screen 
freezes when you try to navigate back and forth from keypad to active call. Try 
several different ways.
  A few times, I was able to hang up the phone I was calling from but the 
active call screen stayed on the device. The only way to make the phone app 
work again was to force quit it. 

  As an alternative route. Try to call the phone when the phone-app is
  running. Accept the call and wait until the active call screen
  appears. Try to interact with the tone dial icon in the call controls.
  I was able to reproduce the freeze this way as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1377996/+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 1499069] Re: display freezes after hanging up a phonecall

2016-09-27 Thread Pat McGowan
*** This bug is a duplicate of bug 1576989 ***
https://bugs.launchpad.net/bugs/1576989

** This bug is no longer a duplicate of bug 1377996
   dialer is  freezing on active call screen
** This bug has been marked a duplicate of bug 1576989
   stale lock files freeze apps

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

Title:
  display freezes after hanging up a phonecall

Status in dialer-app package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  when i am phoning and trying to hang up ( pressing the "red" button) my 
display freezes and when i am touching it nothing happens. But it dont get 
dark, and when e.g. someone calls the call will be displayed.
  The only way to use the phone after that is to restart.

  Phone details:
  Ubuntu 15.04  (r25)

  Has anyone an idea?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1499069/+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 1577215] Re: Origin pattern is unexpected on dpkg-reconfigure

2016-09-27 Thread Iiro Laiho
The questions don't even seem to affect everything. Maybe they should be
disabled altogether.

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

Title:
  Origin pattern is unexpected on dpkg-reconfigure

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  In testing out the new unattended-upgrades behaviour I was asked an
  unexpected question about the "unattended-upgrades Origin-Pattern".
  This is not a great experience, it doesn't match anything other than
  internal code patterns.

  For example, the default offered does NOT look like a sensible Ubuntu
  default for Ubuntu users:

"origin=Debian,codename=${distro_codename},label=Debian-
  Security";___

  Is that correct, or a mistake?

  What I would expect is simply this:

   Install security updates (Y/N)
   Install performance and reliability updates (Y/N)
   Install updates from unofficial archives (Y/N)

  The latter would map to all PPAs etc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1577215/+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 1577215] Re: Origin pattern is unexpected on dpkg-reconfigure

2016-09-27 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: unattended-upgrades (Ubuntu)
   Status: New => Confirmed

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

Title:
  Origin pattern is unexpected on dpkg-reconfigure

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  In testing out the new unattended-upgrades behaviour I was asked an
  unexpected question about the "unattended-upgrades Origin-Pattern".
  This is not a great experience, it doesn't match anything other than
  internal code patterns.

  For example, the default offered does NOT look like a sensible Ubuntu
  default for Ubuntu users:

"origin=Debian,codename=${distro_codename},label=Debian-
  Security";___

  Is that correct, or a mistake?

  What I would expect is simply this:

   Install security updates (Y/N)
   Install performance and reliability updates (Y/N)
   Install updates from unofficial archives (Y/N)

  The latter would map to all PPAs etc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1577215/+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 1556459] Re: [Lenovo ThinkPad W530] Regression: cannot set up 3 display configuration any more (Optimus)

2016-09-27 Thread Arthur Fabre
I am experiencing the same issue, using a Thinkpad W520, on 16.04.
Two external monitors are connected via DVI.
On boot, all three monitors are mirrored, and correctly show the Ubuntu log.
After logging in, I get the same error messages:

The selected configuration for displays could not be applied
could not set the configuration for CRTC 64

and

GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._gsd_2drr_2derror_2dquark.Code2:
could not set the configuration for CRTC 64

One of the monitors is disabled. If I enable it using the Unity Settings
app, the same error message show up. Tailing -f /var/log/Xorg.0.log
while enabling the monitor reveals:

[   451.532] (II) intel(0): resizing framebuffer to 5440x1672
[   451.582] Cannot do multiple crtcs without X server dirty tracking 2 
interface
[   451.582] randr: failed to set shadow slave pixmap
[   451.582] (EE) NOUVEAU(G0): failed to set mode: No space left on device

This appears to be the same bug as #1597437. It also seems to have been
resolved in Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=1307204.

** Bug watch added: Red Hat Bugzilla #1307204
   https://bugzilla.redhat.com/show_bug.cgi?id=1307204

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

Title:
  [Lenovo ThinkPad W530] Regression: cannot set up 3 display
  configuration any more (Optimus)

Status in xorg package in Ubuntu:
  Triaged

Bug description:
  I cannot set up the third monitor any more (it was working beginning
  of March 2016 with Ubuntu 16.04).

  The configuration with NVIDIA Optimus starts with builtin display (of
  Thinkpad W530) and one of (3K) monitors, the second monitor is
  detected, but not used.

  The unity configuration tool shows me two message boxes:

  "The selected configuration for displays could not be applied
  could not set the configuration for CRTC 64"

  and

  "Failed to apply configuration: %s

  
GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._gsd_2drr_2derror_2dquark.Code2: 
could not set the configuration for CRTC 64
  "

  The first one I have seen at boot time on login screen (with 3
  displays) previously, the second one is new.

  The third monitor works if Optimus gets disabled in  BIOS and the
  machine runs with Nvidia only

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Mar 12 18:44:54 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.16, 4.4.0-10-generic, x86_64: installed
   virtualbox, 5.0.16, 4.4.0-11-generic, x86_64: installed
   virtualbox, 5.0.16, 4.4.0-12-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f5]
   NVIDIA Corporation GK107GLM [Quadro K2000M] [10de:0ffb] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo GK107GLM [Quadro K2000M] [17aa:21f5]
  InstallationDate: Installed on 2016-02-25 (15 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160225)
  MachineType: LENOVO 2447MU0
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-12-generic 
root=UUID=c01ceec8-4b0c-447f-af8f-3e9c4ae90e15 ro rootflags=subvol=@ quiet 
splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G5ETA3WW (2.63 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2447MU0
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG5ETA3WW(2.63):bd09/18/2015:svnLENOVO:pn2447MU0:pvrThinkPadW530:rvnLENOVO:rn2447MU0:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2447MU0
  dmi.product.version: ThinkPad W530
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160209-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 

[Touch-packages] [Bug 1574568] Re: Missing dual monitor support

2016-09-27 Thread Pat McGowan
Thats just the term launchpad provides for a "feature". This will
happen.

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

Title:
  Missing dual monitor support

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

Bug description:
  A wish list suggestion to use the tablet along with the monitor or TV
  like if we were using 2 monitors. Duplicate screens, share screens
  etc... to use them as two different work desktops

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1574568/+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 1508092] Re: [Asus 1011PX, Realtek ALC269VB, Speaker, Internal] no sound from speakers, only headphones

2016-09-27 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: alsa-driver (Ubuntu)
   Status: New => Confirmed

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

Title:
  [Asus 1011PX, Realtek ALC269VB, Speaker, Internal] no sound from
  speakers, only headphones

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Sound comes out of the headphones when I insert the jack, but does NOT
  come out of the speakers when I unplug it. This includes sound from
  any source, including aplay.

  This is a newly installed Lubuntu daily build (Lubuntu 15.10 "Wily
  Werewolf" - Alpha i386 20151017.1). If I go back to running from the
  Live USB install media, the sound works fine from the speakers OR the
  headphones, as expected.

  As suggested by 
https://help.ubuntu.com/community/SoundTroubleshootingProcedure I have tried:
  * killing and reloading pulseaudio and alsa-mixer 
  * purging (.config/) .pulse/ then killing/reloading and rebooting
  * installing and reinstalling pavucontrol linux-sound-base alsa-base 
alsa-utils libasound2

  In the installed version I notice that in Volume Control (pavucontrol)
  the output switches automatically between headphones and speaker when
  the jack is plugged and unplugged - as one would expect - and in
  alsamixer I can see the inactive device being muted automatically.
  However the speaker never issues any sound :(  On the contrary in the
  live usb I notice that alsamixer leaves both outputs active (unmuted)
  and simply relies on the microswitch in the headphone jack to control
  whether the speaker can be heard or not.

  For reference I past the output of the FAILING test case's alsa-
  info.sh below and attach the output of the WORKING test case's alsa-
  info.sh

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic i686
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   elda   1480 F...m pulseaudio
   /dev/snd/pcmC0D0p:   elda   1480 F...m pulseaudio
   /dev/snd/controlC0:  elda   1480 F pulseaudio
  CurrentDesktop: LXDE
  Date: Tue Oct 20 16:36:58 2015
  InstallationDate: Installed on 2015-10-19 (0 days ago)
  InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Alpha i386 (20151017.1)
  JournalErrors:
   No journal files were found.
   -- No entries --
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/06/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 1015PE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: x.xx
  dmi.chassis.asset.tag: 0x
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer INC.
  dmi.chassis.version: x.x
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd05/06/2011:svnASUSTeKComputerINC.:pn1011PX:pvrx.x:rvnASUSTeKComputerINC.:rn1015PE:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
  dmi.product.name: 1011PX
  dmi.product.version: x.x
  dmi.sys.vendor: ASUSTeK Computer INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1508092/+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 1613490] Re: [MIR] telephony-service

2016-09-27 Thread Steve Langasek
Override component to main
telephony-service 0.1+16.10.20160909.1-0ubuntu1 in yakkety: universe/libs -> 
main
qtdeclarative5-ubuntu-telephony-phonenumber0.1 0.1+16.10.20160909.1-0ubuntu1 in 
yakkety amd64: universe/libs/optional/100% -> main
qtdeclarative5-ubuntu-telephony-phonenumber0.1 0.1+16.10.20160909.1-0ubuntu1 in 
yakkety arm64: universe/libs/optional/100% -> main
qtdeclarative5-ubuntu-telephony-phonenumber0.1 0.1+16.10.20160909.1-0ubuntu1 in 
yakkety armhf: universe/libs/optional/100% -> main
qtdeclarative5-ubuntu-telephony-phonenumber0.1 0.1+16.10.20160909.1-0ubuntu1 in 
yakkety i386: universe/libs/optional/100% -> main
qtdeclarative5-ubuntu-telephony-phonenumber0.1 0.1+16.10.20160909.1-0ubuntu1 in 
yakkety powerpc: universe/libs/optional/100% -> main
qtdeclarative5-ubuntu-telephony-phonenumber0.1 0.1+16.10.20160909.1-0ubuntu1 in 
yakkety ppc64el: universe/libs/optional/100% -> main
qtdeclarative5-ubuntu-telephony0.1 0.1+16.10.20160909.1-0ubuntu1 in yakkety 
amd64: universe/libs/optional/100% -> main
qtdeclarative5-ubuntu-telephony0.1 0.1+16.10.20160909.1-0ubuntu1 in yakkety 
arm64: universe/libs/optional/100% -> main
qtdeclarative5-ubuntu-telephony0.1 0.1+16.10.20160909.1-0ubuntu1 in yakkety 
armhf: universe/libs/optional/100% -> main
qtdeclarative5-ubuntu-telephony0.1 0.1+16.10.20160909.1-0ubuntu1 in yakkety 
i386: universe/libs/optional/100% -> main
qtdeclarative5-ubuntu-telephony0.1 0.1+16.10.20160909.1-0ubuntu1 in yakkety 
powerpc: universe/libs/optional/100% -> main
qtdeclarative5-ubuntu-telephony0.1 0.1+16.10.20160909.1-0ubuntu1 in yakkety 
ppc64el: universe/libs/optional/100% -> main
telephony-service 0.1+16.10.20160909.1-0ubuntu1 in yakkety amd64: 
universe/libs/optional/100% -> main
telephony-service 0.1+16.10.20160909.1-0ubuntu1 in yakkety arm64: 
universe/libs/optional/100% -> main
telephony-service 0.1+16.10.20160909.1-0ubuntu1 in yakkety armhf: 
universe/libs/optional/100% -> main
telephony-service 0.1+16.10.20160909.1-0ubuntu1 in yakkety i386: 
universe/libs/optional/100% -> main
telephony-service 0.1+16.10.20160909.1-0ubuntu1 in yakkety powerpc: 
universe/libs/optional/100% -> main
telephony-service 0.1+16.10.20160909.1-0ubuntu1 in yakkety ppc64el: 
universe/libs/optional/100% -> main
19 publications overridden.


** Changed in: telephony-service (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [MIR] telephony-service

Status in telephony-service package in Ubuntu:
  Fix Released

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by unity8

  [Security]
   * No known security issues at this time. It has been reviewed by security in 
the past for use on the phone.

  [Quality assurance]
   * This package has unit tests that are executed at build time

  [Dependencies]
   Most dependencies are already in main with the exception of the following:
   * history-service (bug #1613486)
   * telepathy-qt5 (bug #1613474)
   * libphonenumber
   * platform-api
   * libusermetrics
   * dbus-test-runner
   * telepathy-mission-control-5
   * xvfb

  [Standards compliance]
   * This package uses cmake and is properly translated.

  [Maintenance]
   * This package is maintained by Canonical and actively in use on the phone 
images

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1613490/+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 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

2016-09-27 Thread Mathew Hodson
** Changed in: network-manager (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: network-manager (Ubuntu Trusty)
   Importance: Undecided => Medium

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

Title:
  dhclient incorrectly assumes a /64 ipv6 prefix

Status in isc-dhcp package in Ubuntu:
  Fix Committed
Status in network-manager package in Ubuntu:
  Fix Committed
Status in isc-dhcp source package in Precise:
  Fix Released
Status in network-manager source package in Precise:
  Invalid
Status in isc-dhcp source package in Trusty:
  Fix Released
Status in network-manager source package in Trusty:
  Triaged
Status in isc-dhcp source package in Xenial:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Committed
Status in isc-dhcp source package in Yakkety:
  Fix Committed
Status in network-manager source package in Yakkety:
  Fix Committed
Status in isc-dhcp package in Debian:
  Fix Released

Bug description:
  [Impact]

  clients who get an ipv6 address from a dhcpv6 server assume the
  address has a /64 prefix, but that is not necessarily true, and if the
  subnet is different than /64 those clients will not be able to reach
  other addresses in that /64 prefix because the other systems are not
  on-link.  This /64 assumption of dhclient effectively breaks the
  client networking for certain addresses.

  [Test Case]

  Set up a server with two interface nics, and one client connected to
  each of those interfaces.  On the server, set up a ipv6 subnet on each
  interface, with a larger prefix than /64, e.g.:

  2001:db8:0:0:1::/96
  2001:db8:0:0:2::/96

  configure dhcpv6 on the server, to provide ipv6 addresses on each
  interface.  Set the server as the default ipv6 route for the clients.

  Allow the clients to get dhcpv6 ipv6 addresses from the server.  The
  clients will each get a ipv6 address with a /64 prefix, due to the bug
  in dhclient.

  Try to ping (or otherwise communicate) between the clients.  Since
  they have /64 prefixes, they think they are on-link with each other,
  but they are not, so they can't communicate.

  After the dhclient bug is fixed, repeat the above setup, and the
  clients will get /128 prefixes instead, and then will be able to
  communicate with each other, because they will route the traffic to
  each other through the server.

  [Regression Potential]

  Non-standard (i.e. not /64) subnets served by dhcpv6 currently are
  broken, this fixes that.

  However, any ipv6 network configurations that rely on the previous
  incorrect assumed /64 behavior (as described here:
  https://tools.ietf.org/html/rfc5942#section-5) in order to allow
  dhcpv6 clients to communicate with other systems inside the subnet,
  but do not use RA to also provide clients with the actual prefix len,
  will break.

  To clarify: a server that provides clients with dhcpv6 addresses, but
  does not also provide the prefix len via RA, will change behavior;
  previously, all clients on the subnet could talk directly to each
  other, with this update the clients cannot talk to each other
  directly; all traffic between clients will be routed through the
  default gateway.

  Further, if the network does not provide a default gateway - for
  example a local network that is intended only for traffic between
  local servers - the clients will not be able to talk to each other at
  all.

  Note that such configurations *are* broken configurations, that just
  happened to work before because of incorrect dhcp client behavior;
  such configurations must be updated to perform RA to provide the
  prefix len to clients.

  See comment 30 for details on how to configure radvd to restore
  network functionality.

  [Other Info]

  This is fixed in debian:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684009

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1609898/+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 1613486] Re: [MIR] history-service

2016-09-27 Thread Steve Langasek
Override component to main
history-service 0.1+16.10.20160909.1-0ubuntu1 in yakkety: universe/libs -> main
history-service 0.1+16.10.20160909.1-0ubuntu1 in yakkety amd64: 
universe/libs/optional/100% -> main
history-service 0.1+16.10.20160909.1-0ubuntu1 in yakkety arm64: 
universe/libs/optional/100% -> main
history-service 0.1+16.10.20160909.1-0ubuntu1 in yakkety armhf: 
universe/libs/optional/100% -> main
history-service 0.1+16.10.20160909.1-0ubuntu1 in yakkety i386: 
universe/libs/optional/100% -> main
history-service 0.1+16.10.20160909.1-0ubuntu1 in yakkety powerpc: 
universe/libs/optional/100% -> main
history-service 0.1+16.10.20160909.1-0ubuntu1 in yakkety ppc64el: 
universe/libs/optional/100% -> main
history-service 0.1+16.10.20160909.1-0ubuntu1 in yakkety s390x: 
universe/libs/optional/100% -> main
history-service-tools 0.1+16.10.20160909.1-0ubuntu1 in yakkety amd64: 
universe/utils/optional/100% -> main
history-service-tools 0.1+16.10.20160909.1-0ubuntu1 in yakkety arm64: 
universe/utils/optional/100% -> main
history-service-tools 0.1+16.10.20160909.1-0ubuntu1 in yakkety armhf: 
universe/utils/optional/100% -> main
history-service-tools 0.1+16.10.20160909.1-0ubuntu1 in yakkety i386: 
universe/utils/optional/100% -> main
history-service-tools 0.1+16.10.20160909.1-0ubuntu1 in yakkety powerpc: 
universe/utils/optional/100% -> main
history-service-tools 0.1+16.10.20160909.1-0ubuntu1 in yakkety ppc64el: 
universe/utils/optional/100% -> main
history-service-tools 0.1+16.10.20160909.1-0ubuntu1 in yakkety s390x: 
universe/utils/optional/100% -> main
libhistoryservice-dev 0.1+16.10.20160909.1-0ubuntu1 in yakkety amd64: 
universe/libdevel/optional/100% -> main
libhistoryservice-dev 0.1+16.10.20160909.1-0ubuntu1 in yakkety arm64: 
universe/libdevel/optional/100% -> main
libhistoryservice-dev 0.1+16.10.20160909.1-0ubuntu1 in yakkety armhf: 
universe/libdevel/optional/100% -> main
libhistoryservice-dev 0.1+16.10.20160909.1-0ubuntu1 in yakkety i386: 
universe/libdevel/optional/100% -> main
libhistoryservice-dev 0.1+16.10.20160909.1-0ubuntu1 in yakkety powerpc: 
universe/libdevel/optional/100% -> main
libhistoryservice-dev 0.1+16.10.20160909.1-0ubuntu1 in yakkety ppc64el: 
universe/libdevel/optional/100% -> main
libhistoryservice-dev 0.1+16.10.20160909.1-0ubuntu1 in yakkety s390x: 
universe/libdevel/optional/100% -> main
libhistoryservice0 0.1+16.10.20160909.1-0ubuntu1 in yakkety amd64: 
universe/libs/optional/100% -> main
libhistoryservice0 0.1+16.10.20160909.1-0ubuntu1 in yakkety arm64: 
universe/libs/optional/100% -> main
libhistoryservice0 0.1+16.10.20160909.1-0ubuntu1 in yakkety armhf: 
universe/libs/optional/100% -> main
libhistoryservice0 0.1+16.10.20160909.1-0ubuntu1 in yakkety i386: 
universe/libs/optional/100% -> main
libhistoryservice0 0.1+16.10.20160909.1-0ubuntu1 in yakkety powerpc: 
universe/libs/optional/100% -> main
libhistoryservice0 0.1+16.10.20160909.1-0ubuntu1 in yakkety ppc64el: 
universe/libs/optional/100% -> main
libhistoryservice0 0.1+16.10.20160909.1-0ubuntu1 in yakkety s390x: 
universe/libs/optional/100% -> main
qtdeclarative5-ubuntu-history0.1 0.1+16.10.20160909.1-0ubuntu1 in yakkety 
amd64: universe/libs/optional/100% -> main
qtdeclarative5-ubuntu-history0.1 0.1+16.10.20160909.1-0ubuntu1 in yakkety 
arm64: universe/libs/optional/100% -> main
qtdeclarative5-ubuntu-history0.1 0.1+16.10.20160909.1-0ubuntu1 in yakkety 
armhf: universe/libs/optional/100% -> main
qtdeclarative5-ubuntu-history0.1 0.1+16.10.20160909.1-0ubuntu1 in yakkety i386: 
universe/libs/optional/100% -> main
qtdeclarative5-ubuntu-history0.1 0.1+16.10.20160909.1-0ubuntu1 in yakkety 
powerpc: universe/libs/optional/100% -> main
qtdeclarative5-ubuntu-history0.1 0.1+16.10.20160909.1-0ubuntu1 in yakkety 
ppc64el: universe/libs/optional/100% -> main
qtdeclarative5-ubuntu-history0.1 0.1+16.10.20160909.1-0ubuntu1 in yakkety 
s390x: universe/libs/optional/100% -> main
36 publications overridden.


** Changed in: history-service (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [MIR] history-service

Status in history-service package in Ubuntu:
  Fix Released

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by unity8

  [Security]
   * No known security issues at this time. It has been reviewed by security in 
the past for use on the phone.

  [Quality assurance]
   * This package has unit tests that are executed at build time

  [Dependencies]
   Most dependencies are already in main with the exception of the following:
   * telepathy-qt5 (bug #1613474)
   * dbus-test-runner
   * telepathy-mission-control-5
   * xvfb

  [Standards compliance]
   * This package uses cmake and is properly translated.

  [Maintenance]
   * This package is maintained by Canonical and actively in 

[Touch-packages] [Bug 1575109] Re: Upgrade failed, x86_64-linux-gnu/crti.o: unrecognized relocation (0x2a) in section `.init'

2016-09-27 Thread Ubuntu Foundations Team Bug Bot
** Tags added: wily2xenial

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

Title:
  Upgrade failed, x86_64-linux-gnu/crti.o: unrecognized relocation
  (0x2a) in section `.init'

Status in binutils:
  New
Status in binutils package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed
Status in binutils package in Debian:
  Fix Released

Bug description:
  Running sa-compile (may take a long time)
  /usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/5/../../../x86_64-linux-gnu/crti.o: unrecognized 
relocation (0x2a) in section `.init'
  /usr/bin/ld: final link failed: Bad value
  collect2: error: ld returned 1 exit status
  make: *** [blib/arch/auto/Mail/SpamAssassin/CompiledRegexps/body_0/body_0.so] 
Error 1
  command 'make >>/tmp/.spamassassin6654c6JaRRtmp/log' failed: exit 2
  dpkg: error processing package sa-compile (--configure):
   subprocess installed post-installation script returned error exit status 25
  Errors were encountered while processing:
   libgmp-dev:amd64
   systemd
   sa-compile

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:15.10.14.4
  ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
  Uname: Linux 4.2.0-35-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Tue Apr 26 11:38:01 2016
  InstallationDate: Installed on 2012-02-04 (1542 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to xenial on 2016-04-26 (0 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
127: pkexec must be setuid root

To manage notifications about this bug go to:
https://bugs.launchpad.net/binutils/+bug/1575109/+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 1366266] Re: Images with transparency look wrong in the dash

2016-09-27 Thread Jamie Strandboge
I'm going to mark this as "Won't Fix"-- this is really up to the
uploader to make sure it looks correct on the device. That said, if
someone wanted to provide an MP, I would review it.

** Changed in: click-reviewers-tools
   Status: Triaged => Won't Fix

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

Title:
  Images with transparency look wrong in the dash

Status in Canonical Click Reviewers tools:
  Won't Fix
Status in unity-scope-click package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Opinion

Bug description:
  How to reproduce:
  - Go to the store scope
  - Select the "Music & Audio" department
  - Scroll to the bottom

  What happens: the cards with overlays on top of images look wrong if
  the image has transparent areas. Please see attached screenshot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/click-reviewers-tools/+bug/1366266/+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 1627769] Re: limits.conf not applied

2016-09-27 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: lightdm (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/1627769

Title:
  limits.conf not applied

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  Since upgraded to 16.10 Yakkety, modifications in
  /etc/security/limits.conf are not taken into consideration when
  logging in the graphical interface.

  
  /etc/security/limits.conf:
  @audio   -  rtprio 99
  @audio   -  memlockunlimited

  I tried the same settings in /etc/security/limits.d/audio.conf, to the
  same results.

  
  After logging in Unity, opening a console, the limits are not set:
  blablack@ideaon:~$ ulimit -l -r
  max locked memory   (kbytes, -l) 64
  real-time priority  (-r) 0

  
  Reloging to my user via bash DOES apply the limits:
  blablack@ideaon:~$ ulimit -l -r
  max locked memory   (kbytes, -l) 64
  real-time priority  (-r) 0
  blablack@ideaon:~$ su blablack
  Password: 
  blablack@ideaon:~$ ulimit -l -r
  max locked memory   (kbytes, -l) unlimited
  real-time priority  (-r) 95

  
  Switching to a console (ctrl+alt+f1) and logging in would apply the limits as 
well.



  The exact same setup used to work fine on Xenial 16.04 before upgrade.

  
  If you need any more information, please let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: lightdm 1.19.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7
  Uname: Linux 4.8.0-16-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Sep 26 17:27:10 2016
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1627769/+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 1628260] [NEW] Upgrade libglew package to also include libglew2

2016-09-27 Thread Raul Tambre
Public bug reported:

Currently glew package only includes versions up to 1.13, but the latest
release is 2.0. As a developer, it would be best to have libglew2 and
libglew2-dev available on Ubuntu. See http://glew.sourceforge.net/ for
more information about the new (and previous) version(s).

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


** Tags: upgrade-software-version

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

Title:
  Upgrade libglew package to also include libglew2

Status in glew package in Ubuntu:
  New

Bug description:
  Currently glew package only includes versions up to 1.13, but the
  latest release is 2.0. As a developer, it would be best to have
  libglew2 and libglew2-dev available on Ubuntu. See
  http://glew.sourceforge.net/ for more information about the new (and
  previous) version(s).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glew/+bug/1628260/+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 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

2016-09-27 Thread Martin Pitt
http://autopkgtest.ubuntu.com/packages/n/network-manager succeeds again
on xenial, thus verified.

** Tags removed: verification-done-precise verification-done-trusty 
verification-done-xenial verification-done-yakkety verification-needed
** Tags added: verification-done

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

Title:
  dhclient incorrectly assumes a /64 ipv6 prefix

Status in isc-dhcp package in Ubuntu:
  Fix Committed
Status in network-manager package in Ubuntu:
  Fix Committed
Status in isc-dhcp source package in Precise:
  Fix Released
Status in network-manager source package in Precise:
  Invalid
Status in isc-dhcp source package in Trusty:
  Fix Released
Status in network-manager source package in Trusty:
  Triaged
Status in isc-dhcp source package in Xenial:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Committed
Status in isc-dhcp source package in Yakkety:
  Fix Committed
Status in network-manager source package in Yakkety:
  Fix Committed
Status in isc-dhcp package in Debian:
  Fix Released

Bug description:
  [Impact]

  clients who get an ipv6 address from a dhcpv6 server assume the
  address has a /64 prefix, but that is not necessarily true, and if the
  subnet is different than /64 those clients will not be able to reach
  other addresses in that /64 prefix because the other systems are not
  on-link.  This /64 assumption of dhclient effectively breaks the
  client networking for certain addresses.

  [Test Case]

  Set up a server with two interface nics, and one client connected to
  each of those interfaces.  On the server, set up a ipv6 subnet on each
  interface, with a larger prefix than /64, e.g.:

  2001:db8:0:0:1::/96
  2001:db8:0:0:2::/96

  configure dhcpv6 on the server, to provide ipv6 addresses on each
  interface.  Set the server as the default ipv6 route for the clients.

  Allow the clients to get dhcpv6 ipv6 addresses from the server.  The
  clients will each get a ipv6 address with a /64 prefix, due to the bug
  in dhclient.

  Try to ping (or otherwise communicate) between the clients.  Since
  they have /64 prefixes, they think they are on-link with each other,
  but they are not, so they can't communicate.

  After the dhclient bug is fixed, repeat the above setup, and the
  clients will get /128 prefixes instead, and then will be able to
  communicate with each other, because they will route the traffic to
  each other through the server.

  [Regression Potential]

  Non-standard (i.e. not /64) subnets served by dhcpv6 currently are
  broken, this fixes that.

  However, any ipv6 network configurations that rely on the previous
  incorrect assumed /64 behavior (as described here:
  https://tools.ietf.org/html/rfc5942#section-5) in order to allow
  dhcpv6 clients to communicate with other systems inside the subnet,
  but do not use RA to also provide clients with the actual prefix len,
  will break.

  To clarify: a server that provides clients with dhcpv6 addresses, but
  does not also provide the prefix len via RA, will change behavior;
  previously, all clients on the subnet could talk directly to each
  other, with this update the clients cannot talk to each other
  directly; all traffic between clients will be routed through the
  default gateway.

  Further, if the network does not provide a default gateway - for
  example a local network that is intended only for traffic between
  local servers - the clients will not be able to talk to each other at
  all.

  Note that such configurations *are* broken configurations, that just
  happened to work before because of incorrect dhcp client behavior;
  such configurations must be updated to perform RA to provide the
  prefix len to clients.

  See comment 30 for details on how to configure radvd to restore
  network functionality.

  [Other Info]

  This is fixed in debian:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684009

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1609898/+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 1498202] Re: No policy available for in-app-purchases

2016-09-27 Thread Jamie Strandboge
This was fixed long ago in the review tools.

** Changed in: click-reviewers-tools
   Status: New => Fix Released

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

Title:
  No policy available for in-app-purchases

Status in Canonical Click Reviewers tools:
  Fix Released
Status in Ubuntu Developer Portal:
  New
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Fix Released
Status in ubuntu-personal-security package in Ubuntu:
  Fix Released

Bug description:
  There is currently no security policy available for in-app-purchases.
  We will need such a policy, in order to deliver the feature for
  developers to use.

To manage notifications about this bug go to:
https://bugs.launchpad.net/click-reviewers-tools/+bug/1498202/+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 1366266] Re: Images with transparency look wrong in the dash

2016-09-27 Thread Jamie Strandboge
** Changed in: click-reviewers-tools
   Status: New => Triaged

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

Title:
  Images with transparency look wrong in the dash

Status in Canonical Click Reviewers tools:
  Triaged
Status in unity-scope-click package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Opinion

Bug description:
  How to reproduce:
  - Go to the store scope
  - Select the "Music & Audio" department
  - Scroll to the bottom

  What happens: the cards with overlays on top of images look wrong if
  the image has transparent areas. Please see attached screenshot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/click-reviewers-tools/+bug/1366266/+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 1628255] [NEW] package libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 failed to install/upgrade: le paquet libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 ne peut pas être configu

2016-09-27 Thread Mahtar Nóla
Public bug reported:

...

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1
ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
Uname: Linux 4.8.0-17-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
Date: Tue Sep 27 20:18:33 2016
Dependencies:
 gcc-6-base 6.2.0-3ubuntu15
 libc6 2.24-0ubuntu1
 libcomerr2 1.43.1-1
 libgcc1 1:6.2.0-3ubuntu15
 libroken18-heimdal 1.7~git20160703+dfsg-1
ErrorMessage: le paquet libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 ne peut 
pas être configuré parce que la version de libasn1-8-heimdal:i386 est 
différente (1.7~git20150920+dfsg-4ubuntu1)
InstallationDate: Installed on 2016-04-22 (158 days ago)
InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3
SourcePackage: heimdal
Title: package libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 failed to 
install/upgrade: le paquet libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 ne 
peut pas être configuré parce que la version de libasn1-8-heimdal:i386 est 
différente (1.7~git20150920+dfsg-4ubuntu1)
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package package-from-proposed yakkety

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

Title:
  package libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 failed to
  install/upgrade: le paquet libasn1-8-heimdal:amd64
  1.7~git20160703+dfsg-1 ne peut pas être configuré parce que la version
  de libasn1-8-heimdal:i386 est différente (1.7~git20150920+dfsg-
  4ubuntu1)

Status in heimdal package in Ubuntu:
  New

Bug description:
  ...

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Tue Sep 27 20:18:33 2016
  Dependencies:
   gcc-6-base 6.2.0-3ubuntu15
   libc6 2.24-0ubuntu1
   libcomerr2 1.43.1-1
   libgcc1 1:6.2.0-3ubuntu15
   libroken18-heimdal 1.7~git20160703+dfsg-1
  ErrorMessage: le paquet libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 ne 
peut pas être configuré parce que la version de libasn1-8-heimdal:i386 est 
différente (1.7~git20150920+dfsg-4ubuntu1)
  InstallationDate: Installed on 2016-04-22 (158 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3
  SourcePackage: heimdal
  Title: package libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 failed to 
install/upgrade: le paquet libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 ne 
peut pas être configuré parce que la version de libasn1-8-heimdal:i386 est 
différente (1.7~git20150920+dfsg-4ubuntu1)
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1628255/+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 1628254] [NEW] package libwind0-heimdal:amd64 1.7~git20160703+dfsg-1 failed to install/upgrade: le paquet libwind0-heimdal:amd64 1.7~git20160703+dfsg-1 ne peut pas être configuré

2016-09-27 Thread Mahtar Nóla
Public bug reported:

...

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: libwind0-heimdal:amd64 1.7~git20160703+dfsg-1
ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
Uname: Linux 4.8.0-17-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
Date: Tue Sep 27 20:18:32 2016
Dependencies:
 gcc-6-base 6.2.0-3ubuntu15
 libc6 2.24-0ubuntu1
 libcomerr2 1.43.1-1
 libgcc1 1:6.2.0-3ubuntu15
 libroken18-heimdal 1.7~git20160703+dfsg-1
ErrorMessage: le paquet libwind0-heimdal:amd64 1.7~git20160703+dfsg-1 ne peut 
pas être configuré parce que la version de libwind0-heimdal:i386 est différente 
(1.7~git20150920+dfsg-4ubuntu1)
InstallationDate: Installed on 2016-04-22 (158 days ago)
InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3
SourcePackage: heimdal
Title: package libwind0-heimdal:amd64 1.7~git20160703+dfsg-1 failed to 
install/upgrade: le paquet libwind0-heimdal:amd64 1.7~git20160703+dfsg-1 ne 
peut pas être configuré parce que la version de libwind0-heimdal:i386 est 
différente (1.7~git20150920+dfsg-4ubuntu1)
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package package-from-proposed yakkety

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

Title:
  package libwind0-heimdal:amd64 1.7~git20160703+dfsg-1 failed to
  install/upgrade: le paquet libwind0-heimdal:amd64
  1.7~git20160703+dfsg-1 ne peut pas être configuré parce que la version
  de libwind0-heimdal:i386 est différente (1.7~git20150920+dfsg-
  4ubuntu1)

Status in heimdal package in Ubuntu:
  New

Bug description:
  ...

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libwind0-heimdal:amd64 1.7~git20160703+dfsg-1
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Tue Sep 27 20:18:32 2016
  Dependencies:
   gcc-6-base 6.2.0-3ubuntu15
   libc6 2.24-0ubuntu1
   libcomerr2 1.43.1-1
   libgcc1 1:6.2.0-3ubuntu15
   libroken18-heimdal 1.7~git20160703+dfsg-1
  ErrorMessage: le paquet libwind0-heimdal:amd64 1.7~git20160703+dfsg-1 ne peut 
pas être configuré parce que la version de libwind0-heimdal:i386 est différente 
(1.7~git20150920+dfsg-4ubuntu1)
  InstallationDate: Installed on 2016-04-22 (158 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3
  SourcePackage: heimdal
  Title: package libwind0-heimdal:amd64 1.7~git20160703+dfsg-1 failed to 
install/upgrade: le paquet libwind0-heimdal:amd64 1.7~git20160703+dfsg-1 ne 
peut pas être configuré parce que la version de libwind0-heimdal:i386 est 
différente (1.7~git20150920+dfsg-4ubuntu1)
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1628254/+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 1628251] [NEW] package libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 failed to install/upgrade: le paquet libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 ne peut pas être con

2016-09-27 Thread Mahtar Nóla
Public bug reported:

I don't know

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1
ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
Uname: Linux 4.8.0-17-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
Date: Tue Sep 27 20:18:33 2016
ErrorMessage: le paquet libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 ne 
peut pas être configuré parce que la version de libhcrypto4-heimdal:i386 est 
différente (1.7~git20150920+dfsg-4ubuntu1)
InstallationDate: Installed on 2016-04-22 (158 days ago)
InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3
SourcePackage: heimdal
Title: package libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 failed to 
install/upgrade: le paquet libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 ne 
peut pas être configuré parce que la version de libhcrypto4-heimdal:i386 est 
différente (1.7~git20150920+dfsg-4ubuntu1)
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package package-from-proposed yakkety

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

Title:
  package libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 failed to
  install/upgrade: le paquet libhcrypto4-heimdal:amd64
  1.7~git20160703+dfsg-1 ne peut pas être configuré parce que la version
  de libhcrypto4-heimdal:i386 est différente (1.7~git20150920+dfsg-
  4ubuntu1)

Status in heimdal package in Ubuntu:
  New

Bug description:
  I don't know

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Tue Sep 27 20:18:33 2016
  ErrorMessage: le paquet libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 ne 
peut pas être configuré parce que la version de libhcrypto4-heimdal:i386 est 
différente (1.7~git20150920+dfsg-4ubuntu1)
  InstallationDate: Installed on 2016-04-22 (158 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3
  SourcePackage: heimdal
  Title: package libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 failed to 
install/upgrade: le paquet libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 ne 
peut pas être configuré parce que la version de libhcrypto4-heimdal:i386 est 
différente (1.7~git20150920+dfsg-4ubuntu1)
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1628251/+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 1627294] Re: 'cd' command missing features

2016-09-27 Thread Matthias Klose
that never worked before, however you can set your own aliases

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

Title:
  'cd' command missing features

Status in bash package in Ubuntu:
  Won't Fix

Bug description:
  I was surprised to discover that 'cd..' command which i have used in
  the past, now is unknown.

  cd. & cd.. features are so simple to use, to step back one level or
  two, i can't imagine they have been dropped by decisions. Please set
  them back.

  oem@u64:~$ cd /var/
  oem@u64:/var$ cd lib
  oem@u64:/var/lib$ cd.
  No command 'cd.' found, did you mean:
   Command 'cde' from package 'cde' (universe)
   Command 'cdv' from package 'codeville' (universe)
   Command 'cd5' from package 'cd5' (universe)
   Command 'cdw' from package 'cdw' (universe)
   Command 'cdo' from package 'cdo' (universe)
   Command 'cdi' from package 'cdo' (universe)
   Command 'cdb' from package 'tinycdb' (main)
   Command 'cdp' from package 'irpas' (multiverse)
  cd.: command not found
  oem@u64:/var/lib$ cd..
  cd..: command not found

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: bash 4.3-15ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7
  Uname: Linux 4.8.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Sep 24 13:18:40 2016
  SourcePackage: bash
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1627294/+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 1610231] Re: tst_sections.13 fails with Qt 5.6

2016-09-27 Thread Tim Peeters
** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  tst_sections.13 fails with Qt 5.6

Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Committed

Bug description:
  tests/xvfb.sh tests/unit/runtest.sh _build/tests/unit/visual/visual 
tests/unit/visual/tst_sections.13.qml
  [...]
  FAIL!  : components::SectionsApi::initTestCase() Action 0 was triggered with 
selectedIndex: 1.
   Actual (): true
   Expected (): false
   Loc:[./tests/unit/visual/tst_sections.13.qml(149)]

  More information about Qt 5.6 at
  https://wiki.ubuntu.com/Touch/QtTesting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1610231/+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 1621509] Re: 'window' contextProperty is registered after components are completed

2016-09-27 Thread Tim Peeters
** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  'window' contextProperty is registered after components are completed

Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Committed

Bug description:
  This is the cause for the Sections index resetting after
  initialization, see bug 1610231.

  Use this code:
  -- ModelFromList13.qml --
  import QtQuick 2.4

  // This component is used in tst_listview_bug1621509.13.qml
  Item {
  id: root
  property var myObject
  property int count: 0 // will hold the number of changes to myObject 
after Component.completed.

  onMyObjectChanged: {
  print("myObject changed to "+myObject)
  count++;
  }
  Component.onCompleted: {
  count = 0;
  }
  }

  -- tst_list_model_from_list_bug1621509.13.qml --
  import QtQuick 2.4
  import QtTest 1.0

  // Ubuntu.Components is not explicitly used below, but its import causes bug 
#1621509.
  import Ubuntu.Components 1.3

  TestCase {
  id: testCase
  name: "EmbeddedListView"
  width: 100
  height: 100

  // Bug #1621509 only occurs when we wait for the window to be visible.
  // Forces the components to be completed before the test functions are 
executed.
  when: windowShown

  ModelFromList13 {
  id: embeddedListView
  QtObject {
  objectName: "one"
  id: objectOne
  }
  myObject: objectOne
  }

  Component.onCompleted: {
  print("Component completed."); // must print something to reproduce 
the bug.
  }

  function test_no_model_change_after_completed_bug1621509_bug1610231() {
  compare(embeddedListView.count, 0,
  "The model was changed after the component was completed.");
  }
  }
  --

  the test will fail. Also, one can replace the TestCase by Item (and
  remove when: windowShown) and simply use qmlscene to start the app. It
  will show that myObject is set twice: before the component completed,
  and then again afterwards. I suspect the reason for this is the change
  of the 'window' context property which causes everything in the
  context (objectOne) and properties that depend on that to be re-
  evaluated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1621509/+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 1585723] Re: UbuntuShape on intel i915 (Atom) uses fallback CPU rendering

2016-09-27 Thread Emanuele Antonio Faraone
Thanks Andrea!

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

Title:
  UbuntuShape on intel i915 (Atom) uses fallback CPU rendering

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

Bug description:
  I'm digging into unity8 performance problems on older generation Intel
  GPUs - specifically i915 Atom GPUs.

  I've tested a simple QML file with a single empty UbuntuShape in it:

  import QtQuick 2.4
  import Ubuntu.Components 1.3

  Rectangle {
  width: 400
  height: 300
  color: "blue"

  UbuntuShape {}
  }

  Running it with INTEL_DEBUG=perf env var set, I get this output:

  i915_program_error: Exceeded max ALU instructions (76 out of 64)
  ENTER FALLBACK 1: Program
  Mapping a busy BO, causing a stall on the GPU.

  which implies that MESA was unable to compile one of the UbuntuShape
  shaders as it created more ALU instructions than the GPU could deal
  with. MESA falls back to CPU rendering as a result.

  The GPU stall message I guess is related to that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1585723/+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 1625137] Re: Layouts unit tests fail on Yakkety

2016-09-27 Thread Tim Peeters
** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Layouts unit tests fail on Yakkety

Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Committed

Bug description:
  /«BUILDDIR»/ubuntu-ui-toolkit-1.3.2104+16.10.20160919.2/tests/checkresults.sh 
/«BUILDDIR»/ubuntu-ui-toolkit-1.3.2104+16.10.20160919.2/tests/*.xml || exit 1; 
pep8 /«BUILDDIR»/ubuntu-ui-toolkit-1.3.2104+16.10.20160919.2 || exit 1;
  3 fatal warnings which MUST be fixed:
layouts


  Only warnings, but our shell script checks for warnings and makes them
  fatal.


  * Start testing of tst_Layouts *
  Config: Using QtTest library 5.6.1, Qt 5.6.1 (x86_64-little_endian-lp64 
shared (dynamic) release build; by GCC 6.2.0 20160914)
  PASS   : tst_Layouts::initTestCase()
  [New Thread 0x7fffe1824700 (LWP 19588)]
  [New Thread 0x7fffe1023700 (LWP 19589)]
  [New Thread 0x7fffe0822700 (LWP 19590)]
  [New Thread 0x7fffe0021700 (LWP 19591)]
  [New Thread 0x7fffdf820700 (LWP 19592)]
  [Thread 0x7fffdf820700 (LWP 19592) exited]
  PASS   : tst_Layouts::testCase_NoLayouts()
  [New Thread 0x7fffdf820700 (LWP 19593)]
  [Thread 0x7fffdf820700 (LWP 19593) exited]
  PASS   : tst_Layouts::testCase_SimpleLayout()
  [New Thread 0x7fffdf820700 (LWP 19594)]
  [Thread 0x7fffdf820700 (LWP 19594) exited]
  PASS   : tst_Layouts::testCase_SimpleLayout_Medium()
  [New Thread 0x7fffdf820700 (LWP 19595)]
  [Thread 0x7fffdf820700 (LWP 19595) exited]
  PASS   : tst_Layouts::testCase_SimpleLayout_Large()
  [New Thread 0x7fffdf820700 (LWP 19596)]
  [Thread 0x7fffdf820700 (LWP 19596) exited]
  PASS   : tst_Layouts::testCase_OverlappingCondition()
  [New Thread 0x7fffdf820700 (LWP 19597)]
  [Thread 0x7fffdf820700 (LWP 19597) exited]
  PASS   : tst_Layouts::testCase_ExternalLayouts()
  [New Thread 0x7fffdf820700 (LWP 19598)]
  [Thread 0x7fffdf820700 (LWP 19598) exited]
  PASS   : tst_Layouts::testCase_ExternalLayouts_Medium()
  [New Thread 0x7fffdf820700 (LWP 19599)]
  [Thread 0x7fffdf820700 (LWP 19599) exited]
  PASS   : tst_Layouts::testCase_ExternalLayouts_Large()
  [New Thread 0x7fffdf820700 (LWP 19600)]
  [Thread 0x7fffdf820700 (LWP 19600) exited]
  PASS   : tst_Layouts::testCase_NestedLayouts()
  [New Thread 0x7fffdf820700 (LWP 19601)]
  [Thread 0x7fffdf820700 (LWP 19601) exited]
  PASS   : tst_Layouts::testCase_NestedLayouts_ExtraLarge()
  [New Thread 0x7fffdf820700 (LWP 19602)]
  [Thread 0x7fffdf820700 (LWP 19602) exited]
  PASS   : tst_Layouts::testCase_ResizingContainers()
  [New Thread 0x7fffdf820700 (LWP 19603)]
  XFAIL  : tst_Layouts::testCase_CurrentLayoutChange() Layout change should not 
happen when component is not defined
 Loc: [tst_layouts.cpp(387)]
  [Thread 0x7fffdf820700 (LWP 19603) exited]
  PASS   : tst_Layouts::testCase_CurrentLayoutChange()
  [New Thread 0x7fffdf820700 (LWP 19604)]
  XFAIL  : tst_Layouts::testCase_PositioningOnLayoutChange() Layout change 
should not happen when component is not defined
 Loc: [tst_layouts.cpp(408)]
  [Thread 0x7fffdf820700 (LWP 19604) exited]
  PASS   : tst_Layouts::testCase_PositioningOnLayoutChange()
  [New Thread 0x7fffdf820700 (LWP 19605)]
  [Thread 0x7fffdf820700 (LWP 19605) exited]
  PASS   : tst_Layouts::testCase_LaidOutItemsOutsideOfLayout()
  [New Thread 0x7fffdf820700 (LWP 19606)]
  [Thread 0x7fffdf820700 (LWP 19606) exited]
  PASS   : tst_Layouts::testCase_OverlaidInItemLayout()
  [New Thread 0x7fffdf820700 (LWP 19607)]
  [Thread 0x7fffdf820700 (LWP 19607) exited]
  PASS   : tst_Layouts::testCase_AnchorFilledReparenting()
  [New Thread 0x7fffdf820700 (LWP 19608)]
  [Thread 0x7fffdf820700 (LWP 19608) exited]
  PASS   : tst_Layouts::testCase_AnchorFilledMargins()
  [New Thread 0x7fffdf820700 (LWP 19609)]
  [Thread 0x7fffdf820700 (LWP 19609) exited]
  PASS   : tst_Layouts::testCase_AnchorFilledSeparateMargins()
  [New Thread 0x7fffdf820700 (LWP 19610)]
  [Thread 0x7fffdf820700 (LWP 19610) exited]
  PASS   : tst_Layouts::testCase_AnchorCenteredInDefault()
  [New Thread 0x7fffdf820700 (LWP 19611)]
  [Thread 0x7fffdf820700 (LWP 19611) exited]
  PASS   : tst_Layouts::testCase_AnchorVerticalCenter()
  [New Thread 0x7fffdf820700 (LWP 19612)]
  [Thread 0x7fffdf820700 (LWP 19612) exited]
  PASS   : tst_Layouts::testCase_AnchorVerticalCenterOffset()
  [New Thread 0x7fffdf820700 (LWP 19613)]
  [Thread 0x7fffdf820700 (LWP 19613) exited]
  PASS   : tst_Layouts::testCase_AnchorHorizontalCenter()
  [New Thread 0x7fffdf820700 (LWP 19614)]
  [Thread 0x7fffdf820700 (LWP 19614) exited]
  PASS   : tst_Layouts::testCase_AnchorHorizontalCenterOffset()
  [New Thread 0x7fffdf820700 (LWP 19615)]
  [Thread 0x7fffdf820700 (LWP 19615) exited]
  PASS   : tst_Layouts::testCase_AnchorCenterWithOffset()
  [New Thread 0x7fffdf820700 (LWP 19616)]
  [Thread 0x7fffdf820700 (LWP 19616) 

[Touch-packages] [Bug 1625993] Re: tst_MainView::testLabsSettings has a lot of warnings

2016-09-27 Thread Tim Peeters
** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: In Progress => Fix Committed

** Tags added: qt5.6

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

Title:
  tst_MainView::testLabsSettings has a lot of warnings

Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Committed

Bug description:
  ubuntu@xenial1:~/dev/ubuntu-ui-toolkit/staging/tests/unit/mainview$ 
./mainview 
  * Start testing of tst_MainView *
  Config: Using QtTest library 5.6.1, Qt 5.6.1 (x86_64-little_endian-lp64 
shared (dynamic) release build; by GCC 5.4.0 20160609)
  PASS   : tst_MainView::initTestCase()
  PASS   : tst_MainView::testCase_AppName()
  PASS   : tst_MainView::testSetApplicationName()
  PASS   : tst_MainView::testExpectedDataFolder()
  PASS   : tst_MainView::testExpectedCacheFolder()
  PASS   : tst_MainView::testLocalStorage()
  QWARN  : tst_MainView::testLabsSettings() 
file:///home/ubuntu/dev/ubuntu-ui-toolkit/staging/qml/Ubuntu/Components/1.3/TextField.qml:938:5:
 QML AbstractButton: Mixing of Ubuntu.Components module versions 1.3 and 1.2 
detected!
  QWARN  : tst_MainView::testLabsSettings() 
file:///home/ubuntu/dev/ubuntu-ui-toolkit/staging/qml/Ubuntu/Components/Themes/Ambiance/1.3/SectionsForPageHeadStyle.qml:44:
 TypeError: Cannot read property 'background' of undefined
  QWARN  : tst_MainView::testLabsSettings() 
file:///home/ubuntu/dev/ubuntu-ui-toolkit/staging/qml/Ubuntu/Components/Themes/Ambiance/1.3/SectionsForPageHeadStyle.qml:37:42:
 Unable to assign [undefined] to QColor
  QWARN  : tst_MainView::testLabsSettings() 
file:///home/ubuntu/dev/ubuntu-ui-toolkit/staging/qml/Ubuntu/Components/Themes/Ambiance/1.3/SectionsForPageHeadStyle.qml:30:34:
 Unable to assign [undefined] to QColor
  QWARN  : tst_MainView::testLabsSettings() 
file:///home/ubuntu/dev/ubuntu-ui-toolkit/staging/qml/Ubuntu/Components/Themes/Ambiance/1.3/ActionBarStyle.qml:37:
 TypeError: Cannot read property 'background' of undefined
  QWARN  : tst_MainView::testLabsSettings() 
file:///home/ubuntu/dev/ubuntu-ui-toolkit/staging/qml/Ubuntu/Components/Themes/Ambiance/1.3/ActionBarStyle.qml:35:
 TypeError: Cannot read property 'backgroundText' of undefined
  QWARN  : tst_MainView::testLabsSettings() 
file:///home/ubuntu/dev/ubuntu-ui-toolkit/staging/qml/Ubuntu/Components/Themes/Ambiance/1.3/PageHeadStyle.qml:107:
 TypeError: Cannot read property 'background' of undefined
  QWARN  : tst_MainView::testLabsSettings() 
file:///home/ubuntu/dev/ubuntu-ui-toolkit/staging/qml/Ubuntu/Components/Themes/Ambiance/1.3/PageHeadStyle.qml:80:
 TypeError: Cannot read property 'background' of undefined
  QWARN  : tst_MainView::testLabsSettings() 
file:///home/ubuntu/dev/ubuntu-ui-toolkit/staging/qml/Ubuntu/Components/Themes/Ambiance/1.3/TextAreaStyle.qml:44:32:
 Unable to assign [undefined] to QColor
  QWARN  : tst_MainView::testLabsSettings() 
file:///home/ubuntu/dev/ubuntu-ui-toolkit/staging/qml/Ubuntu/Components/Themes/Ambiance/1.3/TextAreaStyle.qml:33:39:
 Unable to assign [undefined] to QColor
  QWARN  : tst_MainView::testLabsSettings() 
file:///home/ubuntu/dev/ubuntu-ui-toolkit/staging/qml/Ubuntu/Components/Themes/Ambiance/1.3/FocusShape.qml:26:12:
 Unable to assign [undefined] to QColor
  PASS   : tst_MainView::testLabsSettings()
  PASS   : tst_MainView::testQSettings()
  PASS   : tst_MainView::testNoWarnings_bug186065()
  QDEBUG : tst_MainView::testWindowTitleFromPage() qml: Page.tools is a 
deprecated property. Please use Page.head instead.
  PASS   : tst_MainView::testWindowTitleFromPage()
  QDEBUG : tst_MainView::testWindowTitleFromStack() qml: Page.tools is a 
deprecated property. Please use Page.head instead.
  PASS   : tst_MainView::testWindowTitleFromStack()
  QDEBUG : tst_MainView::testWindowTitleFromTabs() qml: Page.tools is a 
deprecated property. Please use Page.head instead.
  PASS   : tst_MainView::testWindowTitleFromTabs()
  PASS   : tst_MainView::cleanupTestCase()
  Totals: 13 passed, 0 failed, 0 skipped, 0 blacklisted
  * Finished testing of tst_MainView *

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1625993/+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 1626912] Re: Rename platform 'ubuntumirclient' to 'mirclient'

2016-09-27 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Rename platform 'ubuntumirclient' to 'mirclient'

Status in qtubuntu:
  New
Status in qtubuntu package in Ubuntu:
  Confirmed

Bug description:
  Rename platform 'ubuntumirclient' to 'mirclient' because it should not
  be ubuntu-specific, just mir-specific. If that's not true yet, we
  should work toward it...

  Certainly when upstreamed we ideally don't want Qt apps depending on
  "ubuntu". They should depend on "mir".

To manage notifications about this bug go to:
https://bugs.launchpad.net/qtubuntu/+bug/1626912/+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 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

2016-09-27 Thread Jarno Suni
fksdlofioenvdfsdji, 
How did you "want to update && upgrade your server"?
How many kernels can your /boot partition hold? (What is the size of your /boot 
partition?)

Contents of "50unattended-upgrades" is misleading, as there is no
mention of the new configuration variable Unattended-Upgrade::Remove-
New-Unused-Dependencies which defaults to "true" in the file (in Ubuntu
16.04).

Replacing line
// Unattended-Upgrade::Remove-Unused-Dependencies "false";
by
Unattended-Upgrade::Remove-Unused-Dependencies "true";
may help you, if you don't mind that it removes all packages that 'sudo apt-get 
autoremove' would.

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

Title:
  Kernels not autoremoving, causing out of space error on LVM or
  Encrypted installation or on any installation, when /boot partition
  gets full

Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  Currently if one chooses to use LVM or encrypted install, a /boot
  partition is created of 236Mb

  Once kernel updates start being released this partition soon fills
  until people are left unable to upgrade.

  While you and I might know that we need to watch partition space, many
  of the people we have installing think that a windows disk is a disk
  and not a partition, education is probably the key - but in the
  meantime support venues keep needing to deal with the fact the
  partition is too small and/or old kernels are not purged as new ones
  install.

  For workaround and sytem repair, see
  https://help.ubuntu.com/community/Lubuntu/Documentation/RemoveOldKernels

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093/+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 1563035] Re: Downloading blob: URLs fails

2016-09-27 Thread Launchpad Bug Tracker
*** This bug is a duplicate of bug 1490749 ***
https://bugs.launchpad.net/bugs/1490749

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

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

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

Title:
  Downloading blob: URLs fails

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  If I attempt to download a blob: URL from a site, I am presented with
  a dialog asking to choose an application as destination, and then
  after choosing I am presented with "NetworkError 301: Protocol 'blob'
  is unknown". (Replicate by, for example, going to
  https://www.photoeditorsdk.com/, choosing "Try HTML5 editor", and then
  hitting Export in the editor.) I think that the browser probably hands
  off the URL in question to the download manager, which does not
  understand blob URLs (and should not). The browser should handle this
  itself; it is the only thing that can understand blob URLs, which may
  be (and in this case was) dynamically generated and stored in memory
  only. (If handing off to the download manager is still required, then
  perhaps the browser should serialise to a file or a data URL and then
  hand that URL to the DLM.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1563035/+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 1628167] Re: "video format not supported"

2016-09-27 Thread Philip
pixilated images only when the image is taken when the phone is in the
vertical position. Horizontal, or wide screen are just fine.

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

Title:
  "video format not supported"

Status in camera-app package in Ubuntu:
  New

Bug description:
  Meizu Pro5 15.04 OTA-13 
  After video saved and attempt to play back"Video format not supported" is the 
error message.
  The video format is mp4. Video plays on my Ubuntu desktop, sound is fine, 
however  the playback image is severely pixilated. 
  Front and rear cameras give the same result. 
  Will not play at all in the Meizu ubuntu-touch Phone

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1628167/+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 1574568] Re: Missing dual monitor support

2016-09-27 Thread Robin Heroldich
Why is this a "whish"? I use this feature everyday on Unity7. This
should be a basic feature on Unity8 too.

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

Title:
  Missing dual monitor support

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

Bug description:
  A wish list suggestion to use the tablet along with the monitor or TV
  like if we were using 2 monitors. Duplicate screens, share screens
  etc... to use them as two different work desktops

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1574568/+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 1628133] Re: lubuntu beta2 alternate install fails with: "lubuntu-core : Depends: xserver-xorg-input-all but it is not going to be installed"

2016-09-27 Thread Steve Langasek
fix uploaded, but forgot to include the bug reference.

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

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

Title:
  lubuntu beta2 alternate install fails with: "lubuntu-core : Depends:
  xserver-xorg-input-all but it is not going to be installed"

Status in xorg package in Ubuntu:
  Fix Released

Bug description:
  Beta installs fail in the middle with:

lubuntu-core : Depends: xserver-xorg-input-all but it is not going
  to be installed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1628133/+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 1628133] Re: lubuntu beta2 alternate install fails with: "lubuntu-core : Depends: xserver-xorg-input-all but it is not going to be installed"

2016-09-27 Thread Steve Langasek
My fault.  xserver-xorg-input-vmmouse was removed from Debian as
obsolete, and I missed that -input-all still depended on it. Fixing.

** Package changed: lubuntu-meta (Ubuntu) => xorg (Ubuntu)

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

Title:
  lubuntu beta2 alternate install fails with: "lubuntu-core : Depends:
  xserver-xorg-input-all but it is not going to be installed"

Status in xorg package in Ubuntu:
  Fix Released

Bug description:
  Beta installs fail in the middle with:

lubuntu-core : Depends: xserver-xorg-input-all but it is not going
  to be installed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1628133/+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 1628165] Re: venv: bin/activate.fish doesn't work

2016-09-27 Thread roland
I have this bug with 3.5.

** Package changed: python3.4 (Ubuntu) => python3.5 (Ubuntu)

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

Title:
  venv: bin/activate.fish doesn't work

Status in python3.5 package in Ubuntu:
  New

Bug description:
  Creating a virtual env with pyvenv and activating it using the fish shell 
will throw an error.
  This is due to a '$' being added to the venv prompt.
  This is behavior that is not in python 3.5: 
https://hg.python.org/cpython/file/3.5/Lib/venv/

  /tmp> pyvenv venv
  /tmp> source venv/bin/activate.fish 
  The “$” character begins a variable name. The character “(”, which directly 
followed a “$”, is not allowed as a part of a variable name, and variable names 
may not be zero characters long. To learn more about variable expansion in 
fish, type “help expand-variable”.
  venv/bin/activate.fish (line 58): if test -n "$(venv) "
   ^
  from sourcing file venv/bin/activate.fish
called on standard input

  source: Error while reading file “venv/bin/activate.fish”

  
  Ubuntu 16.04.1 LTS
  pyvenvv-3.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3.5/+bug/1628165/+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 1626808] Re: Unable to log in from bq Aquaris tablet

2016-09-27 Thread Rodney Dawes
Setting this to invalid then, as the problem seems to have resolved
itself per comment #6.

** Changed in: ubuntuone-credentials (Ubuntu)
   Status: New => Invalid

** Changed in: canonical-identity-provider
   Status: New => Invalid

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

Title:
  Unable to log in from bq Aquaris tablet

Status in Canonical SSO provider:
  Invalid
Status in ubuntuone-credentials package in Ubuntu:
  Invalid

Bug description:
  Hi

  I have five Aquaris tablets I am installing some new products I have
  built onto.

  On one tablet, when I try to log in to the Ubuntu One so I can get the
  terminal app, I enter my email and password (correct) to log in, but I
  am not logged in and the terminal app does not download.

  Without the terminal app installed I cannot run any diagnostics or get
  any information about what is going wrong.

  This setup, where terminal is not on the Tablet OS by default, totally
  SUCKS.

  I need support urgently.

  I cannot provide log files to you or anything else. Presumably the
  Ubuntu Web web site logs will say that I am trying to log in from a
  Tablet device. I wish I had some logs myself...

  Mark Anson

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-identity-provider/+bug/1626808/+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 1628133] [NEW] lubuntu beta2 alternate install fails with: "lubuntu-core : Depends: xserver-xorg-input-all but it is not going to be installed"

2016-09-27 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Beta installs fail in the middle with:

  lubuntu-core : Depends: xserver-xorg-input-all but it is not going to
be installed

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


** Tags: iso-testing
-- 
lubuntu beta2 alternate install fails with: "lubuntu-core : Depends: 
xserver-xorg-input-all but it is not going to be installed"
https://bugs.launchpad.net/bugs/1628133
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

-- 
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 1625172] Re: [MIR] address-book-service

2016-09-27 Thread Steve Langasek
Override component to main
address-book-service 0.1.2+16.10.20160920-0ubuntu1 in yakkety: universe/utils 
-> main
address-book-service 0.1.2+16.10.20160920-0ubuntu1 in yakkety amd64: 
universe/utils/optional/100% -> main
address-book-service 0.1.2+16.10.20160920-0ubuntu1 in yakkety arm64: 
universe/utils/optional/100% -> main
address-book-service 0.1.2+16.10.20160920-0ubuntu1 in yakkety armhf: 
universe/utils/optional/100% -> main
address-book-service 0.1.2+16.10.20160920-0ubuntu1 in yakkety i386: 
universe/utils/optional/100% -> main
address-book-service 0.1.2+16.10.20160920-0ubuntu1 in yakkety powerpc: 
universe/utils/optional/100% -> main
address-book-service 0.1.2+16.10.20160920-0ubuntu1 in yakkety ppc64el: 
universe/utils/optional/100% -> main
address-book-service-dummy 0.1.2+16.10.20160920-0ubuntu1 in yakkety amd64: 
universe/utils/optional/100% -> main
address-book-service-dummy 0.1.2+16.10.20160920-0ubuntu1 in yakkety arm64: 
universe/utils/optional/100% -> main
address-book-service-dummy 0.1.2+16.10.20160920-0ubuntu1 in yakkety armhf: 
universe/utils/optional/100% -> main
address-book-service-dummy 0.1.2+16.10.20160920-0ubuntu1 in yakkety i386: 
universe/utils/optional/100% -> main
address-book-service-dummy 0.1.2+16.10.20160920-0ubuntu1 in yakkety powerpc: 
universe/utils/optional/100% -> main
address-book-service-dummy 0.1.2+16.10.20160920-0ubuntu1 in yakkety ppc64el: 
universe/utils/optional/100% -> main
address-book-service-testability 0.1.2+16.10.20160920-0ubuntu1 in yakkety 
amd64: universe/utils/optional/100% -> main
address-book-service-testability 0.1.2+16.10.20160920-0ubuntu1 in yakkety 
arm64: universe/utils/optional/100% -> main
address-book-service-testability 0.1.2+16.10.20160920-0ubuntu1 in yakkety 
armhf: universe/utils/optional/100% -> main
address-book-service-testability 0.1.2+16.10.20160920-0ubuntu1 in yakkety i386: 
universe/utils/optional/100% -> main
address-book-service-testability 0.1.2+16.10.20160920-0ubuntu1 in yakkety 
powerpc: universe/utils/optional/100% -> main
address-book-service-testability 0.1.2+16.10.20160920-0ubuntu1 in yakkety 
ppc64el: universe/utils/optional/100% -> main
address-book-service-testability 0.1.2+16.10.20160920-0ubuntu1 in yakkety 
s390x: universe/utils/optional/100% -> main
address-book-updater 0.1.2+16.10.20160920-0ubuntu1 in yakkety amd64: 
universe/utils/optional/100% -> main
address-book-updater 0.1.2+16.10.20160920-0ubuntu1 in yakkety arm64: 
universe/utils/optional/100% -> main
address-book-updater 0.1.2+16.10.20160920-0ubuntu1 in yakkety armhf: 
universe/utils/optional/100% -> main
address-book-updater 0.1.2+16.10.20160920-0ubuntu1 in yakkety i386: 
universe/utils/optional/100% -> main
address-book-updater 0.1.2+16.10.20160920-0ubuntu1 in yakkety powerpc: 
universe/utils/optional/100% -> main
address-book-updater 0.1.2+16.10.20160920-0ubuntu1 in yakkety ppc64el: 
universe/utils/optional/100% -> main
evolution-data-server-utouch 0.1.2+16.10.20160920-0ubuntu1 in yakkety amd64: 
universe/utils/optional/100% -> main
evolution-data-server-utouch 0.1.2+16.10.20160920-0ubuntu1 in yakkety arm64: 
universe/utils/optional/100% -> main
evolution-data-server-utouch 0.1.2+16.10.20160920-0ubuntu1 in yakkety armhf: 
universe/utils/optional/100% -> main
evolution-data-server-utouch 0.1.2+16.10.20160920-0ubuntu1 in yakkety i386: 
universe/utils/optional/100% -> main
evolution-data-server-utouch 0.1.2+16.10.20160920-0ubuntu1 in yakkety powerpc: 
universe/utils/optional/100% -> main
evolution-data-server-utouch 0.1.2+16.10.20160920-0ubuntu1 in yakkety ppc64el: 
universe/utils/optional/100% -> main
evolution-data-server-utouch-dev 0.1.2+16.10.20160920-0ubuntu1 in yakkety 
amd64: universe/utils/optional/100% -> main
evolution-data-server-utouch-dev 0.1.2+16.10.20160920-0ubuntu1 in yakkety 
arm64: universe/utils/optional/100% -> main
evolution-data-server-utouch-dev 0.1.2+16.10.20160920-0ubuntu1 in yakkety 
armhf: universe/utils/optional/100% -> main
evolution-data-server-utouch-dev 0.1.2+16.10.20160920-0ubuntu1 in yakkety i386: 
universe/utils/optional/100% -> main
evolution-data-server-utouch-dev 0.1.2+16.10.20160920-0ubuntu1 in yakkety 
powerpc: universe/utils/optional/100% -> main
evolution-data-server-utouch-dev 0.1.2+16.10.20160920-0ubuntu1 in yakkety 
ppc64el: universe/utils/optional/100% -> main
qtcontact5-galera 0.1.2+16.10.20160920-0ubuntu1 in yakkety amd64: 
universe/utils/optional/100% -> main
qtcontact5-galera 0.1.2+16.10.20160920-0ubuntu1 in yakkety arm64: 
universe/utils/optional/100% -> main
qtcontact5-galera 0.1.2+16.10.20160920-0ubuntu1 in yakkety armhf: 
universe/utils/optional/100% -> main
qtcontact5-galera 0.1.2+16.10.20160920-0ubuntu1 in yakkety i386: 
universe/utils/optional/100% -> main
qtcontact5-galera 0.1.2+16.10.20160920-0ubuntu1 in yakkety powerpc: 
universe/utils/optional/100% -> main
qtcontact5-galera 0.1.2+16.10.20160920-0ubuntu1 in yakkety ppc64el: 
universe/utils/optional/100% -> main
44 publications overridden.


** Changed 

[Touch-packages] [Bug 1627318] Re: pasted crashed with SIGSEGV in __run_exit_handlers()

2016-09-27 Thread dinamic
yay! added unity8 to the bug report, maybe u8 people can help with this
bug

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

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

Title:
  pasted crashed with SIGSEGV in __run_exit_handlers()

Status in Libertine:
  In Progress
Status in Libertine devel series:
  In Progress
Status in Libertine trunk series:
  Triaged
Status in libertine package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  New

Bug description:
  pasted crashed with SIGSEGV in __run_exit_handlers()

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: libertine-tools 1.4+16.10.20160908-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7
  Uname: Linux 4.8.0-16-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Sat Sep 24 14:01:54 2016
  ExecutablePath: /usr/bin/pasted
  InstallationDate: Installed on 2016-06-05 (110 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcCmdline: pasted
  SegvAnalysis:
   Segfault happened at: 0x7fdbbc18f235 <__run_exit_handlers+69>:   mov
(%rcx),%rdx
   PC (0x7fdbbc18f235) ok
   source "(%rcx)" (0xb14284f8c8520) not located in a known VMA region (needed 
readable region)!
   destination "%rdx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: libertine
  StacktraceTop:
   __run_exit_handlers (status=1, listp=0x7fdbbc5165d8 <__exit_funcs>, 
run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at 
exit.c:55
   __GI_exit (status=) at exit.c:105
   QXcbConnection::processXcbEvents() () from 
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
   QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   QApplicationPrivate::notify_helper(QObject*, QEvent*) () from 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
  Title: pasted crashed with SIGSEGV in __run_exit_handlers()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1627318/+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 1606144] Re: [Precision 5510, Realtek ALC3266, Black Headphone Out, Left] No sound at all

2016-09-27 Thread Odysseas
I am having the same issue with Dell Precision 5510 on Ubuntu 16.04.
I've also tried the 4.6.7 and 4.7.5 kernel and it is also not working.

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

Title:
  [Precision 5510, Realtek ALC3266, Black Headphone Out, Left] No sound
  at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Sound works on laptop speakers, but there is no sound coming from the
  headphones jack. The laptop keeps playing from its own speakers
  instead of using the headphones I've plugged in.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.4.8-040408-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   stian  4028 F...m pulseaudio
   /dev/snd/controlC0:  stian  4028 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jul 25 10:03:23 2016
  InstallationDate: Installed on 2016-06-02 (52 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   stian  4028 F...m pulseaudio
   /dev/snd/controlC0:  stian  4028 F pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [Precision 5510, Realtek ALC3266, Black Headphone Out, Left] No sound 
at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N8J4R
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0N8J4R:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 5510
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-07-25T10:01:11.561836

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1606144/+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 1600220] Re: Nested server needs full control over cursor position

2016-09-27 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/1600220

Title:
  Nested server needs full control over cursor position

Status in Mir:
  In Progress
Status in mir package in Ubuntu:
  Confirmed

Bug description:
  Unity 8, a nested server of unity-system-compositor, needs full
  control over the cursor position.

  Mir doesn't have the needed context information to know how to move or
  position the cursor in all situations. Only Unity 8 has this
  information, which lives mainly in its QML scene.

  Once this is granted Unity 8 can dump its QML cursor implementation
  and move to use the more performant hardware cursor that mir has
  access to.

  Related to bug 1513883.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1600220/+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 1628198] [NEW] No communcation with graphics card

2016-09-27 Thread Paul Cain
Public bug reported:

Resolution incorrect. Appears to be using on-board graphics. Hardware
was working perfectly before with older distros.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
BootLog:
 * Setting up X socket directories...    
[ OK ]
 Running 0dns-down to make sure resolv.conf is ok...done.
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Tue Sep 27 23:24:21 2016
DistUpgraded: 2016-08-11 02:26:50,924 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory))
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.4.0-34-generic, x86_64: installed
 nvidia-340, 340.96, 4.4.0-34-generic, x86_64: installed
DpkgLog:
 
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA 
controller])
   Subsystem: ASUSTeK Computer Inc. GT218 [GeForce 210] [1043:848e]
InstallationDate: Installed on 2015-01-16 (620 days ago)
InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
MachineType: HP-Pavilion KY789AA-AKL p6175l
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=495ee15a-c5aa-43dc-80a3-f5133ad56d59 ro quiet drm.debug=0xe 
plymouth:debug splash vesafb.invalid=1
Renderer: Software
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2016-08-10 (47 days ago)
dmi.bios.date: 05/07/2009
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 5.22
dmi.board.name: Boston
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr5.22:bd05/07/2009:svnHP-Pavilion:pnKY789AA-AKLp6175l:pvr:rvnMSI:rnBoston:rvr1.0:cvnHewlett-Packard:ct3:cvr:
dmi.product.name: KY789AA-AKL p6175l
dmi.sys.vendor: HP-Pavilion
version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Tue Sep 27 23:21:10 2016
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputLogitech USB Receiver KEYBOARD, id 8
 inputLogitech USB Receiver KEYBOARD, id 9
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.3-1ubuntu2.3

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


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

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

Title:
  No communcation with graphics card

Status in xorg package in Ubuntu:
  New

Bug description:
  Resolution incorrect. Appears to be using on-board graphics. Hardware
  was working perfectly before with older distros.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog:
   * Setting up X socket directories...    
[ OK ]
   Running 0dns-down to make sure resolv.conf is ok...done.
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Sep 27 23:24:21 2016
  DistUpgraded: 2016-08-11 02:26:50,924 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory))
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-34-generic, x86_64: installed
   nvidia-340, 340.96, 4.4.0-34-generic, x86_64: installed
 

[Touch-packages] [Bug 1536353] Re: [Regression] Epson's printer driver packages cannot be installed as lsb package is not available anymore

2016-09-27 Thread Aravind Gopal
What is the problem? , its hardware or software problem?. Is it possible to use 
the scanner? Status shows "fix released" and Importance "medium".
Confused

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

Title:
  [Regression] Epson's printer driver packages cannot be installed as
  lsb package is not available anymore

Status in lsb:
  New
Status in cups-filters package in Ubuntu:
  Fix Released
Status in epson-inkjet-printer-escpr package in Ubuntu:
  Fix Released
Status in lsb package in Ubuntu:
  Fix Released
Status in cups-filters source package in Xenial:
  Fix Released
Status in epson-inkjet-printer-escpr source package in Xenial:
  Fix Released
Status in lsb source package in Xenial:
  Fix Released

Bug description:
  [SRU justification]
  Previous releases were compatible with third-party printer drivers provided 
in LSB package format (and also as .deb packages depending on the lsb package). 
 As of 16.04, because the LSB specifies ABIs for various libraries that are no 
longer supported in Ubuntu as obsolete, the packages for the lsb modules have 
been dropped in both Debian and Ubuntu.  This includes dropping of lsb-core, 
which is the component which provides the LSB-mandated ELF loader path - 
without which no lsb executable will work.

  This SRU will restore the bare minimum of LSB compatibility necessary
  to support known third-party LSB printer driver packages on Ubuntu
  16.04.

  [Regression potential]
  The reintroduced 'lsb' binary package is known to not fully satisfy the 
requirements for a complete LSB-compliant system.  This is a regression vs. 
Ubuntu 14.04; so anyone using LSB packages on Ubuntu 14.04 who upgrades to 
Ubuntu 16.04 may have the upgrade succeed without any warning from the package 
manager.

  As there are very few lsb packages in use in the wild, this is
  considered an acceptable regression, especially as this will land
  before the first 16.04 point release.

  [Test case]
  1. Download the epsion 201106w printer driver package from 
http://download.ebz.epson.net/dsc/op/stable/debian/dists/lsb3.2/main/binary-amd64/epson-inkjet-printer-201106w_1.0.1-1lsb3.2_amd64.deb
  2. Install the package and confirm that its dependencies are not satisfiable.
  3. Enable xenial-proposed.
  4. Install the package again and confirm that the dependencies are satisfied.
  5. Verify that 
/opt/epson-inkjet-printer-201106w/cups/lib/filter/epson_inkjet_printer_filter 
can be run without errors about missing lsb ld.so or missing libraries.

  Starting with Xenial, lsb compatibility packages were dropped (besides
  lsb-release and lsb-base):

  lsb (9.20150826) unstable; urgency=low

    * Drop all the LSB compatibility packages besides lsb-release and lsb-base
  - Drop packages-availability checking in lsb-release
  - Truncate README.Debian to a minimum
  - Document this in lsb-base.NEWS.Debian
    * Change the versioning number to avoid any ambiguity; use joeyh's
  version.date, with version being Debian next stable's

   -- Didier Raboud   Wed, 26 Aug 2015 12:00:00 +0200

  The problem is that downloadable printer drivers (like the ones from
  Openprinting, but also from other available providers) that are
  suggested when installing a printer on Ubuntu depends on lsb, which is
  not available anymore:

  epson-inkjet-printer-201106w:
   Dépend: lsb (>=3.2) but it is not installable

  This triggers a regression where it is not possible to setup a printer
  this way (downloading a driver where no local driver is available)
  anymore.

  I see two possible solutions:

  - Add a proper replaces field to one of the remaining lsb-* packages,
  to hopefully fix missing lsb package (maybe it would be useful to also
  replace other compability packages that are not built anymore).

  - Re-introduce LSB compatibility packages, but that might be an
  overkill.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lsb/+bug/1536353/+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 1627600] Re: unity8-dash failed to launch

2016-09-27 Thread Gary.Wang
Aha, I double-checked them and indeed, libunity-scopes1.0 didn't get updated on 
my side.
libunity-scopes1.0:
  Installed: 1.0.6+16.04.20160617-0ubuntu1
  Candidate: 1.0.7+16.04.20160921-0ubuntu2
  Version table:
 1.0.7+16.04.20160921-0ubuntu2 500
500 
http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu 
xenial/main amd64 Packages
 *** 1.0.6+16.04.20160617-0ubuntu1 100
100 /var/lib/dpkg/status
 1.0.4+16.04.20160402.4-0ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

after latest one is installed, everything works fine now.
Thanks.

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

Title:
  unity8-dash failed to launch

Status in unity-scopes-shell package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  failed to run unity8-dash on xenial(amd64).

  
  gary@ubuntu:~$ unity8-dash --mousetouch
  [2016-09-26:14:07:25.432] QQmlApplicationEngine failed to load component
  [2016-09-26:14:07:25.432] 
file:///usr/share/unity8//Dash/DashApplication.qml:35 Type Dash unavailable
  file:///usr/share/unity8//Dash/Dash.qml:20 plugin cannot be loaded for module 
"Unity": Cannot load library 
/usr/lib/x86_64-linux-gnu/unity8/qml/Unity/libUnity-qml.so: 
(/usr/lib/x86_64-linux-gnu/unity8/qml/Unity/libUnity-qml.so: undefined symbol: 
_ZN5unity6scopes18SearchListenerBase4pushERKNSt7__cxx114listISt10shared_ptrIKNS0_10FilterBaseEESaIS7_EEE)
  .

  gary@ubuntu:~$ apt-cache policy unity8
  unity8:
Installed: 8.14+16.04.20160922-0ubuntu1
Candidate: 8.14+16.04.20160922-0ubuntu1
Version table:
   *** 8.14+16.04.20160922-0ubuntu1 500
  500 
http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu 
xenial/main amd64 Packages
  100 /var/lib/dpkg/status
   8.12+16.04.20160401-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1627600/+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 1618886] Re: unity-gtk-module.service is racy; session services don't stop if session terminates

2016-09-27 Thread Iain Lane
This isn't quite enough in this situation.

- Log in over SSH or in a vt (so there is a logind session alive for your user)
- Log into the same user in Unity
- Simulate an Xorg crash (pkill -f -SEGV Xorg)
- Log back in

You don't have GTK_MODULES set properly. The previous gnome-session is
lingering.

To fix that, something like comment #3 is needed. Such as looping over
all 'active' units that are PartOf graphical-session.target and stopping
them all.

gnome-session needs a fix to its ExecStopPost to not kill the one we
just started.

I'll upload this and it can be reviewed in the queue.

** Changed in: gnome-session (Ubuntu)
   Status: Fix Released => Triaged

** Changed in: gnome-session (Ubuntu)
   Importance: Undecided => High

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

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

** Changed in: gnome-session (Ubuntu)
   Importance: High => Medium

** Changed in: gnome-session (Ubuntu)
 Assignee: Martin Pitt (pitti) => Iain Lane (laney)

** Changed in: upstart (Ubuntu)
 Assignee: Martin Pitt (pitti) => Iain Lane (laney)

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

Title:
  unity-gtk-module.service is racy; session services don't stop if
  session terminates

Status in gnome-session package in Ubuntu:
  Triaged
Status in unity-gtk-module package in Ubuntu:
  Fix Released
Status in upstart package in Ubuntu:
  Triaged

Bug description:
  Sometimes on session start unity-gtk-module.service runs too late or
  something, and $GTK_MODULES does not include "unity". It is in
  "systemctl --user show-environment" but not in a terminal bash.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1618886/+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 1627310] Re: Guest session fails to log out

2016-09-27 Thread flocculant
*** This bug is a duplicate of bug 1627304 ***
https://bugs.launchpad.net/bugs/1627304

test@test-Standard-PC-i440FX-PIIX-1996:~$ dmesg | grep DENIED
[   50.801345] audit: type=1400 audit(1474991831.922:27): apparmor="DENIED" 
operation="mknod" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/1722/fd/2" pid=1722 comm="lightdm-session" requested_mask="c" 
denied_mask="c" fsuid=996 ouid=996
[   50.803080] audit: type=1400 audit(1474991831.922:28): apparmor="DENIED" 
operation="mknod" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/1724/fd/2" pid=1724 comm="lightdm-session" requested_mask="c" 
denied_mask="c" fsuid=996 ouid=996
[   50.932125] audit: type=1400 audit(1474991832.054:29): apparmor="DENIED" 
operation="connect" profile="/usr/lib/lightdm/lightdm-guest-session" pid=1846 
comm="initctl" family="unix" sock_type="stream" protocol=0 requested_mask="send 
receive accept" denied_mask="send accept" 
addr="@/com/ubuntu/upstart-session/996/1720" peer_addr=none peer="unconfined"
[   50.941490] audit: type=1400 audit(1474991832.062:30): apparmor="DENIED" 
operation="connect" profile="/usr/lib/lightdm/lightdm-guest-session" pid=1862 
comm="initctl" family="unix" sock_type="stream" protocol=0 requested_mask="send 
receive accept" denied_mask="send accept" 
addr="@/com/ubuntu/upstart-session/996/1720" peer_addr=none peer="unconfined"
[   50.946784] audit: type=1400 audit(1474991832.066:31): apparmor="DENIED" 
operation="connect" profile="/usr/lib/lightdm/lightdm-guest-session" pid=1866 
comm="initctl" family="unix" sock_type="stream" protocol=0 requested_mask="send 
receive accept" denied_mask="send accept" 
addr="@/com/ubuntu/upstart-session/996/1720" peer_addr=none peer="unconfined"
[   50.949328] audit: type=1400 audit(1474991832.070:32): apparmor="DENIED" 
operation="connect" profile="/usr/lib/lightdm/lightdm-guest-session" pid=1870 
comm="initctl" family="unix" sock_type="stream" protocol=0 requested_mask="send 
receive accept" denied_mask="send accept" 
addr="@/com/ubuntu/upstart-session/996/1720" peer_addr=none peer="unconfined"
[   50.951780] audit: type=1400 audit(1474991832.074:33): apparmor="DENIED" 
operation="connect" profile="/usr/lib/lightdm/lightdm-guest-session" pid=1874 
comm="initctl" family="unix" sock_type="stream" protocol=0 requested_mask="send 
receive accept" denied_mask="send accept" 
addr="@/com/ubuntu/upstart-session/996/1720" peer_addr=none peer="unconfined"
[   50.954141] audit: type=1400 audit(1474991832.074:34): apparmor="DENIED" 
operation="connect" profile="/usr/lib/lightdm/lightdm-guest-session" pid=1878 
comm="initctl" family="unix" sock_type="stream" protocol=0 requested_mask="send 
receive accept" denied_mask="send accept" 
addr="@/com/ubuntu/upstart-session/996/1720" peer_addr=none peer="unconfined"
[   62.395078] audit: type=1400 audit(1474991843.538:35): apparmor="DENIED" 
operation="connect" profile="/usr/lib/lightdm/lightdm-guest-session" pid=2127 
comm="initctl" family="unix" sock_type="stream" protocol=0 requested_mask="send 
receive accept" denied_mask="send accept" 
addr="@/com/ubuntu/upstart-session/996/1720" peer_addr=none peer="unconfined"
[   62.397757] audit: type=1400 audit(1474991843.542:36): apparmor="DENIED" 
operation="connect" profile="/usr/lib/lightdm/lightdm-guest-session" pid=2129 
comm="dbus-send" family="unix" sock_type="stream" protocol=0 
requested_mask="send receive accept" denied_mask="send accept" 
addr="@/com/ubuntu/upstart-session/996/1720" peer_addr=none peer="unconfined"
test@test-Standard-PC-i440FX-PIIX-1996:~$ 


** This bug has been marked a duplicate of bug 1627304
   User locking problems - guest login crashing

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

Title:
  Guest session fails to log out

Status in lightdm package in Ubuntu:
  Confirmed
Status in xfce4-session package in Ubuntu:
  Confirmed

Bug description:
  Vanilla Xubuntu install. When logging out from the guest session,
  everything is closed and the desktop wallpaper is the only thing that
  remains. The user is never returned to the login screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xfce4-session 4.12.1-3ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Uname: Linux 4.8.0-11-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Sep 24 09:18:31 2016
  InstallationDate: Installed on 2016-09-24 (0 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921)
  SourcePackage: xfce4-session
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2016-09-24 (0 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921)
  

[Touch-packages] [Bug 1547844] Re: systemd-fsckd does not allow fsck to finish

2016-09-27 Thread kex
hi,

the packet fails to install:

kex@xpc:~$ LANG=en sudo apt-get install systemd/xenial-proposed
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Selected version '229-4ubuntu9' (Ubuntu:16.04/xenial-proposed [amd64]) for 
'systemd'
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 systemd : Depends: libsystemd0 (= 229-4ubuntu9) but 229-4ubuntu8 is to be 
installed
   Recommends: libpam-systemd but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

If I try to install both, a scary list of packages will be removed (I
have no courage now to do that):

kex@xpc:~$ LANG=en sudo apt-get install libsystemd0/xenial-proposed 
systemd/xenial-proposed
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Selected version '229-4ubuntu9' (Ubuntu:16.04/xenial-proposed [amd64]) for 
'libsystemd0'
Selected version '229-4ubuntu9' (Ubuntu:16.04/xenial-proposed [amd64]) for 
'systemd'
The following packages were automatically installed and are no longer required:
  account-plugin-tools accountsservice-ubuntu-schemas argyll argyll-ref 
dbus-property-service gir1.2-gdesktopenums-3.0
  gir1.2-gnomedesktop-3.0 gir1.2-udisks-2.0 gnome-shell-common 
gstreamer1.0-plugins-base:i386 libaudio2:i386 libcdparanoia0:i386
  libconnectivity-qt1 libdbus-cpp5 libglib2.0-0:i386 
libgstreamer-plugins-base1.0-0:i386 libgstreamer1.0-0:i386 libhybris 
libhybris-utils
  libjpeg62:i386 libmedia1 libmng2:i386 libmysqlclient20:i386 
libonline-accounts-client1 libonline-accounts-daemon1 libonline-accounts-qt1
  liboobs-1-5 libopts25 libopus0:i386 liborc-0.4-0:i386 libpkcs11-helper1 
libprocess-cpp3 libqgsttools-p1 libqmenumodel0 libqofono-qt5-0
  libqt4-sql:i386 libqt4-sql-mysql:i386 libqt4-xml:i386 
libqt5multimedia5-plugins libqt5multimediaquick-p5 libqt5multimediawidgets5
  libqt5systeminfo5 libqt5xmlpatterns5 libqtcore4:i386 libsystemsettings1 
libtheora0:i386 libtrust-store2 libubuntuoneauth-2.0-0
  libvisual-0.4-0:i386 libvisual-0.4-plugins:i386 libxss1:i386 libxtst6:i386 
libxv1:i386 mate-polkit-common mutter-common
  network-manager-openvpn ntp openvpn plainbox-secure-policy python-gpgme 
python3-gnupg python3-guacamole python3-jinja2
  python3-markupsafe python3-padme python3-pyparsing python3-xlsxwriter 
qmenumodel-qml qml-module-qtmultimedia qml-module-qtsysteminfo
  qml-module-ubuntu-connectivity qml-module-ubuntu-onlineaccounts2 
qtdeclarative5-gsettings1.0 qtdeclarative5-ofono0.2
  qtdeclarative5-ubuntu-settings-components sqlite3 system-image-common 
system-image-dbus system-tools-backends ubuntu-keyboard-data
  ubuntuone-credentials-common urfkill
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  apparmor-easyprof apparmor-easyprof-ubuntu click click-apparmor 
gir1.2-click-0.4 gir1.2-gee-0.8 libboost-log1.58.0 libboost-regex1.58.0
  libboost-thread1.58.0 libc-ares2 libclick-0.4-0 libcontent-hub0 libgflags2v5 
libgoogle-glog0v5 libhardware2 libhybris-common1
  liblibertine1 liblttng-ust-ctl2 liblttng-ust0 libubuntu-app-launch2 
libubuntu-application-api3 libubuntu-download-manager-client1
  libubuntu-download-manager-common1 libubuntu-platform-hardware-api3 
libudm-common1 liburcu4 ofono powerd python3-apparmor
  python3-apparmor-click python3-click-package python3-libapparmor 
qtdeclarative5-ubuntu-content1 ubuntu-application-api3-test
Suggested packages:
  click-reviewers-tools ubuntu-app-launch-tools | upstart-app-launch-tools 
content-hub systemd-ui systemd-container
Recommended packages:
  libpam-systemd
The following packages will be REMOVED:
  aptdaemon brasero checkbox checkbox-converged checkbox-gui checkbox-qt colord 
deja-dup-backend-gvfs gnome-bluetooth gnome-color-manager
  gnome-control-center gnome-disk-utility gnome-session gnome-settings-daemon 
gnome-system-log gnome-system-tools gnome-tweak-tool
  gnome-user-share gvfs gvfs-backends gvfs-daemons gvfs-fuse hplip 
indicator-bluetooth indicator-sound landscape-client-ui-install
  language-selector-gnome libasound2-plugins:i386 libavahi-client3:i386 
libcanberra-pulse libcups2:i386 libdbus-1-3:i386
  libdbusmenu-qt2:i386 libpam-systemd libpulse0:i386 libqt4-dbus:i386 
libqt4-declarative:i386 libqt4-network:i386 libqt4-opengl:i386
  libqt4-script:i386 libqt4-xmlpatterns:i386 libqtdbus4:i386 libqtgui4:i386 
libqtwebkit4:i386 libsane:i386 libsystemd0:i386 nautilus
  nautilus-dropbox nautilus-sendto nautilus-share network-manager 
network-manager-gnome plainbox-provider-checkbox
  plainbox-provider-resource-generic policykit-1 policykit-1-gnome 
printer-driver-postscript-hp pulseaudio 

[Touch-packages] [Bug 1500242] Re: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5

2016-09-27 Thread Stefan Hammes
Aquaris E5 HD
Porsche 911 car, model 997 (2011)

Update with OTA 13:

Again no sucess to connect the phone to the car.

After typing the 4-digit pin code into the Aquaris E5,
the phone displays, it is connected to the car's PCM (Porsche Communication 
Management).
The car displays, that there "is still a confirmation by the phone missing". 
But no confirmation dialog is promting on the phone.
After that the displayed connection with the car disappers from the phone.

Dear Konrad,
I understand well, that it takes time to take things bit by bit.
So I am still disappointed after so many OTAs, but hopeful and patient.

Greetings, Stefan

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

Title:
  Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected
  with BQ Aquaris 4.5

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  Confirmed
Status in ofono package in Ubuntu:
  Incomplete

Bug description:
  STEPS:
  Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old 
one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi 
car kit (A3 2012 model)

  1. Put Jabra BT250 into receiving mode
  2. Phone searches automatically every 15 - 30 seconds for a new blue tooth 
device
  3. Phone finds Jabra BT250 and asks for pairing code
  4. Enter code into phone
  5. Jabra BT250 automatically exits the pairing mode (which is a sign that 
pairing should have worked)
  6. Phone looses connection to Jabra BT250
  7. Manual reconnection via phone works (shows Jabra BT250 as being connected) 
but ignores the device

  Same behaviour with Audi car kit (Audi A3, 2012 model)

  EXPECTED:
  I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012 
model) where the blue tooth pairing etc. works great (except some bugs which 
are already filed).

  ACTUAL:
  No connection to the blue tooth device

  VERSIONS:
  OS-Build-Number: 25
  Ubuntu-Image: 20150825.1

  POSSIBLE ROOT CAUSE:
  Is this issue also solved as soon as bluez5 is implemented? When will this be?

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1500242/+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 1584965] Re: [browser] scrolling uneven and queues up

2016-09-27 Thread Santosh
Bill confirmed that scrolling is quite improved with latest oxide1.17 and the 
same issue
is not observable.

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

Title:
  [browser] scrolling uneven and queues up

Status in Canonical System Image:
  Confirmed
Status in Oxide:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  I've noticed this on a bunch of websites, mainly on Arale but also on
  krillin, both running latest rc-proposed with and without oxide 1.15

  The scenario is I'm on page A, navigate to page B, press back button,
  then try to scroll page A (flicking up). The page doesn't move for a
  short time then scrolls super fast almost to the bottom. Seems like
  the scroll events are getting queued up and then all applied at once.

  This site reproduces it pretty easy for me:

  1) goto boston.craigslist.org
  2) type "kayak" in the search field
  3) you'll get a page full of results
  4) click on one of the results
  5) wait till page fully loads, flick quickly a few times, first flicks 
ignored. then press back button
  6) wait till page fully loads and then start scrolling (flicking up, multiple 
times), first flicks ignored/queued then scrolling happens fast

  Expected results:
  the page should start scrolling immediately and keep up with action of finger

  Actual results:
  the page is not responsive for a few seconds then scrolls super fast toward 
the bottom

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1584965/+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 1628161] Re: SlotsLayout height is not dynamically updated when main paddings change

2016-09-27 Thread Launchpad Bug Tracker
** Branch linked: lp:~3v1n0/ubuntu-ui-toolkit/slotslayout-paddings-
changes-updates-size

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

Title:
  SlotsLayout height is not dynamically updated when main paddings
  change

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  You can see this in the attached testcase.

  When paddings are changed, the SlotsLayout height is not updated
  dynamically.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1628161/+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 1628165] [NEW] venv: bin/activate.fish doesn't work

2016-09-27 Thread roland
Public bug reported:

Creating a virtual env with pyvenv and activating it using the fish shell will 
throw an error.
This is due to a '$' being added to the venv prompt.
This is behavior that is not in python 3.5: 
https://hg.python.org/cpython/file/3.5/Lib/venv/

/tmp> pyvenv venv
/tmp> source venv/bin/activate.fish 
The “$” character begins a variable name. The character “(”, which directly 
followed a “$”, is not allowed as a part of a variable name, and variable names 
may not be zero characters long. To learn more about variable expansion in 
fish, type “help expand-variable”.
venv/bin/activate.fish (line 58): if test -n "$(venv) "
 ^
from sourcing file venv/bin/activate.fish
called on standard input

source: Error while reading file “venv/bin/activate.fish”


Ubuntu 16.04.1 LTS
pyvenvv-3.5

** Affects: python3.4 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  venv: bin/activate.fish doesn't work

Status in python3.4 package in Ubuntu:
  New

Bug description:
  Creating a virtual env with pyvenv and activating it using the fish shell 
will throw an error.
  This is due to a '$' being added to the venv prompt.
  This is behavior that is not in python 3.5: 
https://hg.python.org/cpython/file/3.5/Lib/venv/

  /tmp> pyvenv venv
  /tmp> source venv/bin/activate.fish 
  The “$” character begins a variable name. The character “(”, which directly 
followed a “$”, is not allowed as a part of a variable name, and variable names 
may not be zero characters long. To learn more about variable expansion in 
fish, type “help expand-variable”.
  venv/bin/activate.fish (line 58): if test -n "$(venv) "
   ^
  from sourcing file venv/bin/activate.fish
called on standard input

  source: Error while reading file “venv/bin/activate.fish”

  
  Ubuntu 16.04.1 LTS
  pyvenvv-3.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1628165/+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 1628167] [NEW] "video format not supported"

2016-09-27 Thread Philip
Public bug reported:

Meizu Pro5 15.04 OTA-13 
After video saved and attempt to play back"Video format not supported" is the 
error message.
The video format is mp4. Video plays on my Ubuntu desktop, sound is fine, 
however  the playback image is severely pixilated. 
Front and rear cameras give the same result. 
Will not play at all in the Meizu ubuntu-touch Phone

** Affects: camera-app (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  "video format not supported"

Status in camera-app package in Ubuntu:
  New

Bug description:
  Meizu Pro5 15.04 OTA-13 
  After video saved and attempt to play back"Video format not supported" is the 
error message.
  The video format is mp4. Video plays on my Ubuntu desktop, sound is fine, 
however  the playback image is severely pixilated. 
  Front and rear cameras give the same result. 
  Will not play at all in the Meizu ubuntu-touch Phone

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1628167/+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 1626611] Re: camera not detected when running confined on desktop

2016-09-27 Thread Tyler Hicks
** Changed in: apparmor-easyprof-ubuntu (Ubuntu)
   Status: New => Invalid

** Changed in: apparmor-easyprof-ubuntu (Ubuntu)
 Assignee: Jamie Strandboge (jdstrand) => (unassigned)

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

Title:
  camera not detected when running confined on desktop

Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Invalid
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  Running on xenial + xenial overlay.

  The camera cannot be accessed. Seeing the following apparmor denials:

  bfiller@blackhorse:~$ tail -f /var/log/syslog | grep DEN
  Sep 22 11:14:11 blackhorse dbus[1811]: apparmor="DENIED" 
operation="dbus_method_call"  bus="session" path="/org/gtk/vfs/Daemon" 
interface="org.gtk.vfs.Daemon" member="ListMonitorImplementations" mask="send" 
name=":1.7" pid=4207 label="webbrowser-app" peer_pid=1919 
peer_label="unconfined"
  Sep 22 11:14:11 blackhorse kernel: [ 2448.215755] audit: type=1400 
audit(1474557251.512:59): apparmor="DENIED" operation="open" 
profile="webbrowser-app" name="/usr/share/gvfs/remote-volume-monitors/" 
pid=4207 comm="webbrowser-app" requested_mask="r" denied_mask="r" fsuid=1000 
ouid=0
  Sep 22 11:14:11 blackhorse kernel: [ 2448.224997] audit: type=1400 
audit(1474557251.524:60): apparmor="DENIED" operation="open" 
profile="webbrowser-app" name="/sys/bus/" pid=4207 comm="webbrowser-app" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  Sep 22 11:14:11 blackhorse kernel: [ 2448.225064] audit: type=1400 
audit(1474557251.524:61): apparmor="DENIED" operation="open" 
profile="webbrowser-app" name="/sys/class/drm/" pid=4207 comm="webbrowser-app" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  Sep 22 11:14:11 blackhorse dbus[1811]: apparmor="DENIED" 
operation="dbus_method_call"  bus="session" path="/org/gtk/vfs/mounttracker" 
interface="org.gtk.vfs.MountTracker" member="ListMountableInfo" mask="send" 
name=":1.7" pid=4207 label="webbrowser-app" peer_pid=1919 
peer_label="unconfined"
  Sep 22 11:14:11 blackhorse kernel: [ 2448.663730] audit: type=1400 
audit(1474557251.960:62): apparmor="DENIED" operation="open" 
profile="webbrowser-app//oxide_helper" 
name="/sys/devices/system/cpu/cpufreq/policy0/cpuinfo_max_freq" pid=4220 
comm="oxide-renderer" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  Sep 22 11:14:11 blackhorse kernel: [ 2448.670941] audit: type=1400 
audit(1474557251.968:63): apparmor="DENIED" operation="open" 
profile="webbrowser-app//oxide_helper" 
name="/opt/google/chrome/PepperFlash/manifest.json" pid=4220 
comm="oxide-renderer" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  Sep 22 11:14:11 blackhorse kernel: [ 2448.675938] audit: type=1400 
audit(1474557251.972:64): apparmor="DENIED" operation="open" 
profile="webbrowser-app" name="/sys/bus/" pid=4207 comm="webbrowser-app" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  Sep 22 11:14:11 blackhorse kernel: [ 2448.675983] audit: type=1400 
audit(1474557251.972:65): apparmor="DENIED" operation="open" 
profile="webbrowser-app" name="/sys/class/drm/" pid=4207 comm="webbrowser-app" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  Sep 22 11:14:11 blackhorse kernel: [ 2448.680663] audit: type=1400 
audit(1474557251.976:66): apparmor="DENIED" operation="open" 
profile="webbrowser-app" name="/opt/google/chrome/PepperFlash/manifest.json" 
pid=4207 comm="webbrowser-app" requested_mask="r" denied_mask="r" fsuid=1000 
ouid=0
  Sep 22 11:14:12 blackhorse kernel: [ 2448.723161] audit: type=1400 
audit(1474557252.020:67): apparmor="DENIED" operation="open" 
profile="webbrowser-app" name="/dev/shm/lttng-ust-wait-6-1000" pid=4243 
comm="QQmlThread" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
  Sep 22 11:14:12 blackhorse kernel: [ 2448.723181] audit: type=1400 
audit(1474557252.020:68): apparmor="DENIED" operation="open" 
profile="webbrowser-app" name="/dev/shm/lttng-ust-wait-6" pid=4242 
comm="QQmlThread" requested_mask="r" denied_mask="r" fsuid=1000 ouid=108
  Sep 22 11:14:17 blackhorse kernel: [ 2453.723913] audit: type=1400 
audit(1474557257.020:73): apparmor="DENIED" operation="open" 
profile="webbrowser-app" name="/dev/shm/lttng-ust-wait-6-1000" pid=4243 
comm="QQmlThread" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
  Sep 22 11:14:17 blackhorse kernel: [ 2453.724018] audit: type=1400 
audit(1474557257.020:74): apparmor="DENIED" operation="open" 
profile="webbrowser-app" name="/dev/shm/lttng-ust-wait-6" pid=4242 
comm="QQmlThread" requested_mask="r" denied_mask="r" fsuid=1000 ouid=108
  Sep 22 11:14:17 blackhorse kernel: [ 2453.724120] audit: type=1400 
audit(1474557257.020:75): apparmor="DENIED" operation="open" 
profile="webbrowser-app" name="/dev/shm/lttng-ust-wait-6-1000" pid=4243 
comm="QQmlThread" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
  Sep 22 

[Touch-packages] [Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix

2016-09-27 Thread Andy Whitcroft
Hello Dan, or anyone else affected,

Accepted network-manager into xenial-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/network-
manager/1.2.2-0ubuntu0.16.04.3 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Tags added: verification-needed

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

Title:
  dhclient incorrectly assumes a /64 ipv6 prefix

Status in isc-dhcp package in Ubuntu:
  Fix Committed
Status in network-manager package in Ubuntu:
  Fix Committed
Status in isc-dhcp source package in Precise:
  Fix Released
Status in network-manager source package in Precise:
  Invalid
Status in isc-dhcp source package in Trusty:
  Fix Released
Status in network-manager source package in Trusty:
  Triaged
Status in isc-dhcp source package in Xenial:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Committed
Status in isc-dhcp source package in Yakkety:
  Fix Committed
Status in network-manager source package in Yakkety:
  Fix Committed
Status in isc-dhcp package in Debian:
  Fix Released

Bug description:
  [Impact]

  clients who get an ipv6 address from a dhcpv6 server assume the
  address has a /64 prefix, but that is not necessarily true, and if the
  subnet is different than /64 those clients will not be able to reach
  other addresses in that /64 prefix because the other systems are not
  on-link.  This /64 assumption of dhclient effectively breaks the
  client networking for certain addresses.

  [Test Case]

  Set up a server with two interface nics, and one client connected to
  each of those interfaces.  On the server, set up a ipv6 subnet on each
  interface, with a larger prefix than /64, e.g.:

  2001:db8:0:0:1::/96
  2001:db8:0:0:2::/96

  configure dhcpv6 on the server, to provide ipv6 addresses on each
  interface.  Set the server as the default ipv6 route for the clients.

  Allow the clients to get dhcpv6 ipv6 addresses from the server.  The
  clients will each get a ipv6 address with a /64 prefix, due to the bug
  in dhclient.

  Try to ping (or otherwise communicate) between the clients.  Since
  they have /64 prefixes, they think they are on-link with each other,
  but they are not, so they can't communicate.

  After the dhclient bug is fixed, repeat the above setup, and the
  clients will get /128 prefixes instead, and then will be able to
  communicate with each other, because they will route the traffic to
  each other through the server.

  [Regression Potential]

  Non-standard (i.e. not /64) subnets served by dhcpv6 currently are
  broken, this fixes that.

  However, any ipv6 network configurations that rely on the previous
  incorrect assumed /64 behavior (as described here:
  https://tools.ietf.org/html/rfc5942#section-5) in order to allow
  dhcpv6 clients to communicate with other systems inside the subnet,
  but do not use RA to also provide clients with the actual prefix len,
  will break.

  To clarify: a server that provides clients with dhcpv6 addresses, but
  does not also provide the prefix len via RA, will change behavior;
  previously, all clients on the subnet could talk directly to each
  other, with this update the clients cannot talk to each other
  directly; all traffic between clients will be routed through the
  default gateway.

  Further, if the network does not provide a default gateway - for
  example a local network that is intended only for traffic between
  local servers - the clients will not be able to talk to each other at
  all.

  Note that such configurations *are* broken configurations, that just
  happened to work before because of incorrect dhcp client behavior;
  such configurations must be updated to perform RA to provide the
  prefix len to clients.

  See comment 30 for details on how to configure radvd to restore
  network functionality.

  [Other Info]

  This is fixed in debian:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684009

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1609898/+subscriptions

-- 
Mailing list: 

[Touch-packages] [Bug 1627281] Re: Double tapping the title bar in desktop mode does not maximize the app window

2016-09-27 Thread Lukáš Tinkl
** Branch linked: lp:~lukas-kde/unity8/doubleTapToMaximize

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

Title:
  Double tapping the title bar in desktop mode does not maximize the app
  window

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

Bug description:
  bq M10 rc-proposed r196
  I've noticed the double tapping the title bar of an app does no longer works 
to maximize the app window. It works though if the window is maximized to 
return it to the previous size.

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

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


  1   2   3   >