[Touch-packages] [Bug 1553739] Re: The unity doesn't launch automatically due to xorg crash

[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/1553739

Title:
  The unity doesn't launch automatically due to xorg crash

Status in xorg package in Ubuntu:
  Expired

Bug description:
  1) manish@manish-Vostro-3446:~$ lsb_release -rd
  Description:  Ubuntu 15.10
  Release:  15.10
  2) manish@manish-Vostro-3446:~$ apt-cache policy xorg
  xorg:
Installed: 1:7.7+7ubuntu4
Candidate: 1:7.7+7ubuntu4
Version table:
   *** 1:7.7+7ubuntu4 0
  500 http://archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
  100 /var/lib/dpkg/status
  manish@manish-Vostro-3446:~$ 
  3) Expected : Unity should launch automatically
  4) Actual : Unity doesn't launches automatically , force start via command 
setsid unity .

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  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: Sun Mar  6 20:05:34 2016
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20130203-1
  DistroCodename: wily
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0662]
  InstallationDate: Installed on 2014-08-23 (561 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20130203-13:50
  LightdmGreeterLog: Error writing X authority: Failed to open X authority 
/var/lib/lightdm/.Xauthority: No such file or directory
  LightdmGreeterLogOld: Error writing X authority: Failed to open X authority 
/var/lib/lightdm/.Xauthority: No such file or directory
  MachineType: Dell Inc. Vostro 3446
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic 
root=UUID=f21d4315-5692-4816-81a0-d9ff963da937 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/03/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0JKRPT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A09
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd11/03/2015:svnDellInc.:pnVostro3446:pvrNotSpecified:rvnDellInc.:rn0JKRPT:rvrA09:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Vostro 3446
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.65-3
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.4-1intel1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.4-1intel1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Sun Mar  6 19:49:01 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1523 
   vendor BOE
  xserver.version: 2:1.17.2-1ubuntu9.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1553739/+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 1553611] Re: xorg

[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/1553611

Title:
  xorg

Status in xorg package in Ubuntu:
  Expired

Bug description:
  autosent.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-51.58-generic 3.19.8-ckt13
  Uname: Linux 3.19.0-51-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  304.131  Sun Nov  8 21:43:33 
PST 2015
   GCC version:  gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.17.2-0ubuntu1.8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Mar  5 17:48:18 2016
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-304-updates, 304.131, 3.19.0-49-generic, x86_64: installed
   nvidia-304-updates, 304.131, 3.19.0-51-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation G71 [GeForce 7950 GT] [10de:0295] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. Device [3842:c636]
  InstallationDate: Installed on 2015-12-26 (70 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. Vostro 470
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-51-generic 
root=UUID=a79174a4-ca20-406d-9c3d-f26c9748c837 ro quiet splash
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/05/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0YJPT1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd09/05/2012:svnDellInc.:pnVostro470:pvr:rvnDellInc.:rn0YJPT1:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.name: Vostro 470
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.1+15.04.20150922-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.65+git20151026.c745e541-0ubuntu0ricotz~vivid
  version.libgl1-mesa-dri: libgl1-mesa-dri 
11.0.4~git20151026+11.0.ec14e6f8-0ubuntu0ricotz~vivid
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 
11.0.4~git20151026+11.0.ec14e6f8-0ubuntu0ricotz~vivid
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.99+git20150521.d64a13eb-0ubuntu0ricotz~vivid
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20151202.da9ad388-0ubuntu0sarvatt~vivid
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11+git20150926.1ff13a92-0ubuntu0sarvatt~vivid
  xserver.bootTime: Sat Mar  5 17:27:54 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputLogitech K360KEYBOARD, id 8
   inputDell Dell USB Keyboard KEYBOARD, id 9
   inputMicrosoft Microsoft 3-Button Mouse with IntelliEye(TM) MOUSE, 
id 10
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.17.1-0ubuntu3.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1553611/+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 1526568] Re: /usr/bin/unity8:6:qt_message_fatal:QMessageLogger::fatal:init_platform:QGuiApplicationPrivate::createPlatformIntegration:QGuiApplicationPrivate::createEventDispatche

[Launchpad Bug Tracker]

[Expired for unity8 (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  
/usr/bin/unity8:6:qt_message_fatal:QMessageLogger::fatal:init_platform:QGuiApplicationPrivate::createPlatformIntegration:QGuiApplicationPrivate::createEventDispatcher

Status in unity8 package in Ubuntu:
  Expired

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity8.  This problem was most recently seen with version
  8.11+15.04.20151208.1-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/322818aab54dbf8b43ec2742a750f27c6e88d02a
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1526568/+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 1553536] Re: fail to start network connection

[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/1553536

Title:
  fail to start network connection

Status in xorg package in Ubuntu:
  Expired

Bug description:
  fail to start a internet connection and mozilla firefox crashed at
  every 2 minute

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic i686
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: i386
  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  5 18:53:22 2016
  DistUpgraded: 2015-11-09 16:58:01,930 DEBUG enabling apt cron job
  DistroCodename: wily
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Device [1179:fd3c]
  InstallationDate: Installed on 2014-03-23 (713 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
  MachineType: TOSHIBA Satellite C660
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic 
root=UUID=0565d99e-ae92-48a0-8125-73012050d591 ro nopat plymouth:debug 
vesafb.invalid=1 drm.debug=0xe
  SourcePackage: xorg
  UpgradeStatus: Upgraded to wily on 2015-11-09 (117 days ago)
  dmi.bios.date: 02/14/11
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: 1.50
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: PWWAA
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: *
  dmi.chassis.type: 9
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnTOSHIBA:bvr1.50:bd02/14/11:svnTOSHIBA:pnSatelliteC660:pvrPSC0SE-00W011G5:rvnTOSHIBA:rnPWWAA:rvr1.00:cvnTOSHIBA:ct9:cvrN/A:
  dmi.product.name: Satellite C660
  dmi.product.version: PSC0SE-00W011G5
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Sat Mar  5 18:37:59 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id8940 
   vendor AUO
  xserver.version: 2:1.17.2-1ubuntu9.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1553536/+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 1554344] Re: Mouse left click stops working

[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/1554344

Title:
  Mouse left click stops working

Status in xorg package in Ubuntu:
  Expired

Bug description:
  HP Elitebook 8770w. Mouse left/right click & scroll wheel works only
  on system panels (Window menus, choosing application, shutdown etc.),
  not anywhere else. Reboot fixes problem, but it reappears after
  unknown time period (usually overnight).

  This problem is the same with touchpad buttons & external usb mouse.
  Replugging mouse does not help.

  I chose xorg package because this was instructed on older similar
  bugs.

  Ubuntu 14.04.4 LTS 64bit, all upgrades

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  352.63  Sat Nov  7 21:25:42 
PST 2015
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04)
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar  8 06:51:26 2016
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   NVIDIA Corporation GK104GLM [Quadro K4000M] [10de:11bd] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:176c]
  InstallationDate: Installed on 2014-07-17 (599 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP EliteBook 8770w
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic 
root=UUID=56df02cb-50ae-47b0-a07e-c197445ca7cd ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IAV Ver. F.06
  dmi.board.name: 176C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 50.19
  dmi.chassis.asset.tag: CNU2429YXD
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IAVVer.F.06:bd08/15/2012:svnHewlett-Packard:pnHPEliteBook8770w:pvrA1009D11:rvnHewlett-Packard:rn176C:rvrKBCVersion50.19:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8770w
  dmi.product.version: A1009D11
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1.1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.6
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Mar  7 12:08:47 2016
  xserver.configfile: default
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.15.1-0ubuntu2.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1554344/+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 1553553] Re: GIMP lags while Xorg uses much CPU

[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/1553553

Title:
  GIMP lags while Xorg uses much CPU

Status in xorg package in Ubuntu:
  Expired

Bug description:
  GIMP lags to the point of not being of any use, when either the windowed 
Single-Window-Mode is being used or the Non-Single-Window-Mode has an image 
loaded (the lag occurs only in the main window)
  Selecting a menu bar item works fine, also the tooltips for the drawing tools 
pop up on time, but the main window content needs up to several seconds to 
react to clicks and even hovering over a drawing tool (in the 
Single-Window-Mode).
  No rulers were visible, I do not use a tablet and the resizing the window did 
not reduce the lag.

  This bug affected the 2.8.14 version supplied via the ubuntu
  repositories, also my current 2.8.16 version, which was supplied via
  ppa:otto-kesselgulasch/gimp

  I ran top while moving the mouse over the window:
   - "Xorg" uses between 15% and 25%
   - "Compiz" uses between 5% and 10%
   - "gimp-2.8" uses at most 5%

  "dpkg-query -W xorg" returned "xorg 1:7.7+7ubuntu4"

  With compizconfig-settings-manager I disabled all effects, which did
  not fix the problem

  I seem to be also affected by
  https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1072206, but
  only if the Non-Single-Window-Mode is being used.

  My System:
  OS:   Ubuntu 15.10 (Kernel 4.2.0-23-generic x86_64)
  CPU:  Intel(R) Core(TM) i7-3610QM CPU @ 2.30GHz
  GPU:  Nvidia Geforce GT 630M (using the Nvidia driver 361.28)

  I originally filed a bug to the GIMP bugtracker
  (https://bugzilla.gnome.org/show_bug.cgi?id=763138), but I was
  encouraged to file a bug here instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6
  Uname: Linux 4.2.0-23-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.28  Wed Feb  3 15:48:04 
PST 2016
   GCC version:  gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2)
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Mar  5 19:15:11 2016
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.2.0-16-generic, x86_64: installed
   bbswitch, 0.7, 4.2.0-23-generic, x86_64: installed
   nvidia-361, 361.28, 4.2.0-23-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:10bc]
   NVIDIA Corporation GF108M [GeForce GT 630M] [10de:0de9] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:10bc]
  InstallationDate: Installed on 2016-01-15 (50 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: ASUSTeK COMPUTER INC. K75VM
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-23-generic 
root=UUID=47915adc-f8da-436b-8c87-3e2a1e6c76d8 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/25/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 234
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: K75VM
  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.:bvr234:bd11/25/2014:svnASUSTeKCOMPUTERINC.:pnK75VM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK75VM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: K75VM
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  

[Touch-packages] [Bug 1490347] Re: [Regresision] 16:04 + 15:10 - Cannot pair with devices using (Legacy) PIN codes

[Noah J. Chelliah]

I was able to work around this issue by using the "blueman" package to
pair the keyboard.

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

Title:
  [Regresision] 16:04 + 15:10 - Cannot pair with devices using (Legacy)
  PIN codes

Status in Bluez Utilities:
  New
Status in bluez package in Ubuntu:
  Triaged
Status in bluez source package in Wily:
  Triaged

Bug description:
  Bluez 5.3 does not have support for pairing with devices (such as
  keyboards) that use a PIN code for pairing.

  A mouse pairs correctly.

  From my research it seems as if the ChromeOS project developed patches
  to fix this and they are supposed to have been included in Bluez 5.4
  (that statement dated April 2013) but I've not yet identified them.

  "The agent's implementation in bt_console/bluetoothctl upstream is
  incomplete, missing some functions like DisplayPincode."

  https://code.google.com/p/chromium/issues/detail?id=222661

  Along with the loss of Headset profiles meaning VoIP applications can
  no longer use HSP/HFP profiles (requiring functionality yet to land in
  Ofono) this cripples the use of Bluetooth for much else than A2DP or
  mouse input.

  Attempting to pair with, for example, an Apple Wireless Keyboard that
  pairs and works correctly with 14.04 LTS, fails totally on 15.10.

  The mouse shown below is already paired, connected, and working.

  $ bluetoothctl
  [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]
  [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard
  [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse
  [bluetooth]# agent on
  Agent registered
  [bluetooth]# default-agent
  Default agent request successful
  [bluetooth]# scan on
  Discovery started
  [CHG] Controller 00:1F:3A:E0:0A:AF Discovering: yes
  [CHG] Device 00:0A:95:4B:BD:C2 LegacyPairing: yes
  [CHG] Device 00:0A:95:4B:BD:C2 RSSI: -48
  [bluetooth]# pair 00:0A:95:4B:BD:C2
  Attempting to pair with 00:0A:95:4B:BD:C2

  >>> at this point nothing is happening

  >>> so I press Enter on the keyboard and...
  [agent] PIN code: 791166
  >>> I type 791166 Enter and ...
  [agent] PIN code: 237744
  >>> I type 237744 Enter and...
  [agent] PIN code: 358866
  >>> I type 358866 Enter and...
  Request PIN code
  [agent] Enter PIN code: 1234
  >>> I type 1234 Enter on the keyboard and 1234 at the prompt...
  Failed to pair: org.bluez.Error.AuthenticationFailed

  This cycle repeats in various permuations. Sometimes the final
  "Request PIN code" does not appear.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1490347/+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 1577128] Re: Screen locking fade issue

[Phil UK]

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

>From the description it sure seems like it is the same issue. Thank you
for adding the bug number. I see that the status is set to fixed
committed. So hopefully therr will be an update deployed shortly and the
issue will be resolved.

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

Title:
  Screen locking fade issue

Status in powerd package in Ubuntu:
  New
Status in unity-system-compositor package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  On my Ubuntu phone, I have set my screen lock to come on after a
  minute of none use. This is in the Settings > Security & Privacy >
  Locking & Unlocking. The lock does come on as requested however, it is
  instant. One second the screen is on and then the next the screen is
  locked and black. There is no fade (like on my Ubuntu tablet), which
  fades out giving me the option to cancel the locking, if you wish to.

  Is there a setting that stops my phone from locking so fast and where
  I can increase the fade?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/powerd/+bug/1577128/+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 1577795] Re: Ubuntu touch Frieza ota-10.1 dropping connection to logitech k810

[Paul Spain]

I can confirm Niels observation that the K810 works ok as long as its
the only device connected to the M10. As soon as I connect the Ultrathin
Mouse, I lose the keyboard. When I disconnect the mouse, The keyboard
works again.

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

Title:
  Ubuntu touch Frieza ota-10.1 dropping connection to logitech k810

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  I can successfully pair the k810 to my BQ Aquaris M10 FHD tablet.
  The connection state flips every few seconds between connected and 
disconected and the signal strength between excellent and none.
  I have tried forgetting the connection and repairing, and power-cycling then 
repeating the process, to no avail.
  Both the tablet and keyboard have a full charge.
  I have successfully paired and am using a Logitech Ultrathin mouse with the 
tablet.
  I have succesfully paired and use the k810 keyboard with several Android 
devices across multiple versions of Android.
  I have also paired and use the keyboard with Ubuntu 14.04 LTS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1577795/+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 1579451] [NEW] Network manager doesn't ask for password in new connections

[mrmarcato]

Public bug reported:

When trying to connect to a new WPA-PSK encrypted network, I click in the 
wireless icon and select the network I want to connect. Then the wireless icon 
suffers a glitch, I'm not prompted a password, and I'm informed that I'm 
offline.
There's the first time in 2 or 3 months that I tried to connect to a new 
network.
Despite this, in /etc/NetworkManager/system-connections/ there is the file 
matching the network I tried to connect, without a psk=... item on it. Then I 
edited it, put the password and could connect to the network like if I was 
already connected to it.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: network-manager 0.9.8.8-0ubuntu7.2
ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32
Uname: Linux 3.13.0-77-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
CurrentDesktop: Unity
Date: Sat May  7 21:30:11 2016
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2016-02-05 (92 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
IpRoute:
 default via 192.168.2.1 dev wlan0  proto static 
 192.168.2.0/24 dev wlan0  proto kernel  scope link  src 192.168.2.6  metric 9 
 192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICE TYPE  STATE DBUS-PATH   
   
 wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/2  
 eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/1  
 eth1   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
 RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   WIFI  
 WWAN-HARDWARE   WWAN  
 running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

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


** Tags: amd64 apport-bug trusty

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

Title:
  Network manager doesn't ask for password in new connections

Status in network-manager package in Ubuntu:
  New

Bug description:
  When trying to connect to a new WPA-PSK encrypted network, I click in the 
wireless icon and select the network I want to connect. Then the wireless icon 
suffers a glitch, I'm not prompted a password, and I'm informed that I'm 
offline.
  There's the first time in 2 or 3 months that I tried to connect to a new 
network.
  Despite this, in /etc/NetworkManager/system-connections/ there is the file 
matching the network I tried to connect, without a psk=... item on it. Then I 
edited it, put the password and could connect to the network like if I was 
already connected to it.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager 0.9.8.8-0ubuntu7.2
  ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32
  Uname: Linux 3.13.0-77-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat May  7 21:30:11 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-02-05 (92 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  IpRoute:
   default via 192.168.2.1 dev wlan0  proto static 
   192.168.2.0/24 dev wlan0  proto kernel  scope link  src 192.168.2.6  metric 
9 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/2  
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/1  
   eth1   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

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

-- 
Mailing list: 

[Touch-packages] [Bug 1565567] Re: segv in sudo_getgrgid

[Ben Kulbertis]

I've tested 1.8.16-0ubuntu1.1 in xenial-proposed on my xenial install
where sudo was segfaulting when a user authenticated via sssd. I can
confirm this fixes the issue I was having. User's commands now execute
as expected instead of a segfault.

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

Title:
  segv in sudo_getgrgid

Status in sudo:
  Unknown
Status in sudo package in Ubuntu:
  Fix Released
Status in sudo source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  In certain environments, for example when using LDAP, users can end up
  in a group with no name. When that happens, sudo crashes when
  attempting to look up the group name for the debug log.

  Upstream has commited a simple fix for this issue, it has been
  commited to Yakkety, and uploaded to Xenial.

  [Test Case]

  I currently don't know an easy way to reproduce this, it is
  environment-specific. A package containing the fix was successfully
  tested in the problematic environment.

  [Regression Potential]

  A regression in the patch would prevent users from using sudo. The
  risk of regression is low since the patch only changes the debug log.


  Original report:

  If the user is in a group with no name (because libnss-db got removed
  and the group was defined there, for example...) then:

  the call to sudo_debug_printf in sudo_getgrgid
  (plugins/sudoers/pwutil.c, line 462) causes a SEGV when trying to get
  item->d.gr->gr_name (since item->d.gr is NULL).

To manage notifications about this bug go to:
https://bugs.launchpad.net/sudo/+bug/1565567/+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 1572250] Re: Wrong type of Wi-Fi device (wlp2s0) after boot

[Yuriy Vidineev]

Atheros AR9462 - the same problem. rmmod ath9k && modprobe ath9k fixes
the problem

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

Title:
  Wrong type of Wi-Fi device (wlp2s0) after boot

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello
  My Wi-Fi adapter is Intel 7260. After boot I have

  nmcli device status
  DEVICE  TYPE  STATECONNECTION 
  wlp2s0  ethernet  unavailable  -- 
  lo  loopback  unmanaged--

  after some dirty fix (sudo rmmod iwlmvm iwlwifi && sudo modprobe
  iwlwifi)

  nmcli device status
  DEVICE  TYPE  STATE CONNECTION 
  wlp2s0  wifi  disconnected  -- 
  lo  loopback  unmanaged --

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Apr 19 22:22:59 2016
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
   
   #auto wlp2s0
  IpRoute:
   default via 192.168.1.1 dev wlp2s0  proto static  metric 600 
   169.254.0.0/16 dev wlp2s0  scope link  metric 1000 
   192.168.1.0/24 dev wlp2s0  proto kernel  scope link  src 192.168.1.123  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp2s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/2  
libreCMC91f33459-b8b5-43ea-a742-a09720f20821  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --   
   ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1572250/+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 1579298] Re: network-manager manual proxy not work for apt

[公输目]

this problem may because: "Ubuntu 16.04 uses systemd, some config file
changed"

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

Title:
  network-manager manual proxy not work for apt

Status in network-manager package in Ubuntu:
  New

Bug description:
  I'm in China.
  setting manual proxy socks5 at network-manager, but the proxy not work for 
apt, for example: `apt update` and `select best server` for software mirror etc.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat May  7 11:43:05 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-04-30 (6 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.1.10 dev enp3s0  proto static  metric 100 
   169.254.0.0/16 dev enp3s0  scope link  metric 1000 
   192.168.1.0/24 dev enp3s0  proto kernel  scope link  src 192.168.1.1  metric 
100
  IwConfig:
   enp3s0no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL  AUTOCONNECT  
AUTOCONNECT-PRIORITY  READONLY  DBUS-PATH   
ACTIVE  DEVICE  STATE  ACTIVE-PATH
   Wired connection 1  08e80fd3-0779-4bef-86d9-6501e4023370  802-3-ethernet  
1462592381  2016年05月07日 星期六 11时39分41秒  yes  4294966297no
/org/freedesktop/NetworkManager/Settings/0  yes enp3s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/0
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   enp3s0  ethernet  connected  /org/freedesktop/NetworkManager/Devices/0  
Wired connection 1  08e80fd3-0779-4bef-86d9-6501e4023370  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
   ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1579298/+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 1573229] Re: Greeter does not rotate

[Eugène]

I do agree about the portrait mode for all the Scopes. It's very
unconfortable to switch between portrait and landscape manually when
switching between an app that accepts portrait mode and a scope that
doesn't.

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

Title:
  Greeter does not rotate

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

Bug description:
  The Ubuntu Touch start/welcome screen (with the big wheel) does not
  rotate following the tablet orientation.

  Device: Aquaris M10
  Ubuntu version: Ubuntu touch OTA 10.1

  This bug can be very tedious for convergence, when you are in desktop
  mode, with the tablet on the table upside-down and using a bluetooth
  mouse tryng to start the desktop (with no security configuration)
  because the cursor movements follow an opposite direction to mouse
  movements.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1573229/+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 1570310] Re: package systemd 229-4ubuntu4 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 2

[Steven Collins]

@pitti, This is probably not useful, since I just ran aptitude as soon
as the upgrade to 16 completed with errors, and had it fix the broken
packages (with no problems). So systemd seems to be installed fine for
me too, now. Just in case there is some clue, though, here is the
current output from the two debug commands you mentioned:

steven@goliath:~$ sudo sed -i '2 s/^.*/set -x/' /var/lib/dpkg/info/systemd.prerm
steven@goliath:~$ sudo apt-get install --reinstall systemd
Reading package lists... Done
Building dependency tree   
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 0 B/3,643 kB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 186822 files and directories currently installed.)
Preparing to unpack .../systemd_229-4ubuntu4_amd64.deb ...
+ set -e
+ [ upgrade = remove ]
+ dpkg-maintscript-helper rm_conffile 
/etc/X11/xinit/xinitrc.d/50-systemd-user.sh 228-3~ -- upgrade 229-4ubuntu4
+ dpkg-maintscript-helper rm_conffile 
/etc/dbus-1/system.d/org.freedesktop.machine1.conf 228-5~ -- upgrade 
229-4ubuntu4
+ dpkg-maintscript-helper mv_conffile /etc/systemd/systemd-journald.conf 
/etc/systemd/journald.conf 204-1~ -- upgrade 229-4ubuntu4
+ dpkg-maintscript-helper mv_conffile /etc/systemd/systemd-logind.conf 
/etc/systemd/logind.conf 204-1~ -- upgrade 229-4ubuntu4
+ dpkg-maintscript-helper rm_conffile 
/etc/bash_completion.d/systemd-bash-completion.sh 204-1~ -- upgrade 229-4ubuntu4
+ dpkg-maintscript-helper rm_conffile 
/etc/bash_completion.d/systemctl-bash-completion.sh 204-1~ -- upgrade 
229-4ubuntu4
Unpacking systemd (229-4ubuntu4) over (229-4ubuntu4) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for dbus (1.10.6-1ubuntu3) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up systemd (229-4ubuntu4) ...
addgroup: The group `systemd-journal' already exists as a system group. Exiting.
steven@goliath:~$

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

Title:
  package systemd 229-4ubuntu4 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 2

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I was upgrading from 15.10 to 16.04 when this error occur.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  Date: Wed Apr 13 21:41:53 2016
  DpkgTerminalLog:
   Preparing to unpack .../systemd_229-4ubuntu4_amd64.deb ...
   De-configuring udev (225-1ubuntu9.1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/systemd_229-4ubuntu4_amd64.deb (--unpack):
subprocess installed pre-removal script returned error exit status 2
  DuplicateSignature:
   De-configuring udev (225-1ubuntu9.1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/systemd_229-4ubuntu4_amd64.deb (--unpack):
subprocess installed pre-removal script returned error exit status 2
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 2
  InstallationDate: Installed on 2016-01-08 (96 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Lsusb:
   Bus 002 Device 002: ID 0781:5583 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b483 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X455LJ
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=70fa96eb-e0d8-4e65-b049-9cb150759b40 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   
   3 overridden configuration files found.
  Title: package systemd 229-4ubuntu4 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 2
  UpgradeStatus: Upgraded to xenial on 2016-04-13 (0 days ago)
  dmi.bios.date: 04/22/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X455LJ.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X455LJ
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  

[Touch-packages] [Bug 1577596] Re: ntpd not started when using ntpdate

[Paul Donohue]

Aha! I've found the issue.

/etc/network/if-up.d/ntpdate is called when each network interface comes
up.  This happens before network.target is reached, so it happens before
ntp.service would normally be automatically started by systemd.

/etc/network/if-up.d/ntpdate calls `invoke-rc.d ntp stop`, then it runs
ntpdate, then it calls `invoke-rc.d ntp start`.

`invoke-rc.d ntp stop` runs `systemctl stop ntp.service`, which causes
systemd to cancel the ntp.service start task that was automatically
scheduled to happen after network.target.

`invoke-rc.d ntp start` calls `/sbin/runlevel` to determine the current
runlevel so that it can verify the existence of a /etc/rc?.d/S??ntp
symlink for the current runlevel.  However, `/sbin/runlevel` returns
"unknown" because systemd has not reached multi-user.target yet.
Therefore, invoke-rc.d determines that the appropriate /etc/rc?.d/S??ntp
symlink does not exist, so it does not call `systemctl start
ntp.service` to start ntp.

Changing /etc/network/if-up.d/ntpdate so that it calls `systemctl start
ntp.service` instead of `invoke-rc.d ntp start` fixes the problem.

However, I think I would consider this to be a bug in invoke-rc.d and
not ntpdate, since invoke-rc.d simply does not work properly when
systemd is being used and invoke-rc.d is called at boot time.  At the
very least, I would think invoke-rc.d should document that this is
unsupported, and it should detect and report this condition if invoke-
rc.d is called at boot time (rather than just silently failing).

** Also affects: init-system-helpers (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  ntpd not started when using ntpdate

Status in init-system-helpers package in Ubuntu:
  New
Status in ntp package in Ubuntu:
  Confirmed

Bug description:
  After updating from 14.04 to 16.04 on a number of my systems, ntpd no
  longer starts at boot on any of those systems.

  `systemctl status ntp` shows:
 ntp.service - LSB: Start NTP daemon
 Loaded: loaded (/etc/init.d/ntp; bad; vendor preset: enabled)
 Active: inactive (dead)
   Docs: man:systemd-sysv-generator(8)
  May 02 19:10:14 host systemd[1]: Stopped LSB: Start NTP daemon.
  May 02 19:10:17 host systemd[1]: Stopped LSB: Start NTP daemon.

  Manually starting it using `systemctl start ntp` works fine.  However,
  systemd does not seem to want to start it automatically at boot time.


  As best as I can tell based on trial and error, there is something
  special about the combination of the service being named "ntp.service"
  and the service depending on network.target.  However, I haven't been
  able to identify exactly what is causing this.

  If I copy the init script to any other name, everything works fine:
  cp /etc/init.d/ntp /etc/init.d/ntpd
  Edit /etc/init.d/ntpd and change "Provides: ntp" to "Provides: ntpd"
  systemctl enable ntpd
  # After a reboot, ntpd.service is started, but ntp.service is not.

  If I remove "$network" from the "# Required-Start: $network $remote_fs
  $syslog" line in /etc/init.d/ntp, then systemd starts it automatically
  ... But of course it is started before the network comes up, so it
  fails.

  If I replace /etc/init.d/ntp with a file containing only the following, 
systemd won't try to start it automatically at boot:
  #!/bin/sh
  ### BEGIN INIT INFO
  # Provides: ntp
  # Required-Start: $network
  # Required-Stop: $network
  # Default-Start: 2 3 4 5
  # Default-Stop: 1
  # Short-Description: Start NTP daemon
  ### END INIT INFO
  echo "script was run" >> /ntp.log

  If I rename that same dummy script to /etc/init.d/ntp2, it is started
  automatically at boot.

  However, grepping the systemd source code and my systemd config files for ntp 
doesn't seem to find anything that might cause this behavior:
  /etc/systemd# grep -iR ntp *
  timesyncd.conf:#NTP=
  timesyncd.conf:#FallbackNTP=ntp.ubuntu.com
  /lib/systemd# grep -R ntp *
  
system/systemd-timesyncd.service.d/disable-with-time-daemon.conf:ConditionFileIsExecutable=!/usr/sbin/ntpd
  
system/systemd-timesyncd.service.d/disable-with-time-daemon.conf:ConditionFileIsExecutable=!/usr/sbin/openntpd
  Binary file systemd-networkd matches
  Binary file systemd-timedated matches
  Binary file systemd-timesyncd matches

  What else can I do to debug this further?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1577596/+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 1574969] Re: Regression: "lxc-create -B best" stopped working

[Quanah]

This is breaking the ability to use vagrant with LXC boxes.

/opt/vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/batch_action.rb:82:in 
`block (2 levels) in run'
 INFO interface: error: There was an error executing ["sudo", "/usr/bin/env", 
"lxc-create", "-B", "best", "--template", 
"/home/quanah/.vagrant.d/gems/gems/vagrant-lxc-1.2.1/scripts/lxc-template", 
"--name", "u1690_default_1462660055308_76102", "--", "--tarball", 
"/home/quanah/.vagrant.d/boxes/developerinlondon-VAGRANTSLASH-lxc-xenial/0.1/lxc/rootfs.tar.gz",
 "--config", 
"/home/quanah/.vagrant.d/boxes/developerinlondon-VAGRANTSLASH-lxc-xenial/0.1/lxc/lxc-config"]

For more information on the failure, enable detailed logging by setting
the environment variable VAGRANT_LOG to DEBUG.
There was an error executing ["sudo", "/usr/bin/env", "lxc-create", "-B", 
"best", "--template", 
"/home/quanah/.vagrant.d/gems/gems/vagrant-lxc-1.2.1/scripts/lxc-template", 
"--name", "u1690_default_1462660055308_76102", "--", "--tarball", 
"/home/quanah/.vagrant.d/boxes/developerinlondon-VAGRANTSLASH-lxc-xenial/0.1/lxc/rootfs.tar.gz",
 "--config", 
"/home/quanah/.vagrant.d/boxes/developerinlondon-VAGRANTSLASH-lxc-xenial/0.1/lxc/lxc-config"]

For more information on the failure, enable detailed logging by setting
the environment variable VAGRANT_LOG to DEBUG.
 INFO interface: Machine: error-exit ["Vagrant::LXC::Errors::ExecuteError", 
"There was an error executing [\"sudo\", \"/usr/bin/env\", \"lxc-create\", 
\"-B\", \"best\", \"--template\", 
\"/home/quanah/.vagrant.d/gems/gems/vagrant-lxc-1.2.1/scripts/lxc-template\", 
\"--name\", \"u1690_default_1462660055308_76102\", \"--\", \"--tarball\", 
\"/home/quanah/.vagrant.d/boxes/developerinlondon-VAGRANTSLASH-lxc-xenial/0.1/lxc/rootfs.tar.gz\",
 \"--config\", 
\"/home/quanah/.vagrant.d/boxes/developerinlondon-VAGRANTSLASH-lxc-xenial/0.1/lxc/lxc-config\"]\n\nFor
 more information on the failure, enable detailed logging by setting\nthe 
environment variable VAGRANT_LOG to DEBUG."]
quanah@ub16:~/vagrant/u1690$ sudo su -
root@ub16:~# lxc-create -B best --template 
/home/quanah/.vagrant.d/gems/gems/vagrant-lxc-1.2.1/scripts/lxc-template --name 
u1690_default_1462660055308_76102 -- --tarball 
/home/quanah/.vagrant.d/boxes/developerinlondon-VAGRANTSLASH-lxc-xenial/0.1/lxc/rootfs.tar.gz
 --config 
/home/quanah/.vagrant.d/boxes/developerinlondon-VAGRANTSLASH-lxc-xenial/0.1/lxc/lxc-config
best is not a valid backing storage type.

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

Title:
  Regression: "lxc-create -B best" stopped working

Status in Auto Upgrade Testing:
  Triaged
Status in lxc:
  New
Status in lxc package in Ubuntu:
  Confirmed

Bug description:
  I want to use btrfs storage if available, otherwise the plain old
  directory/copies. Until not too long ago, this worked:

$ sudo lxc-create -B best --name=adt-xenial -t ubuntu -- -r xenial

  But now in final xenial it fails with "best is not a valid backing
  storage type.".

  But the manpage still documents it:

If backingstore is 'best', then lxc will try, in order, btrfs, 
zfs, lvm, and finally a  di‐
rectory backing store.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lxc 2.0.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: i3
  Date: Tue Apr 26 08:33:14 2016
  EcryptfsInUse: Yes
  PackageArchitecture: all
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx
  dnsmasq.conf:
   enable-tftp
   tftp-root=/tmp/tftp
   dhcp-boot=pxelinux.0
  lxc.conf: lxc.lxcpath = /srv/lxc

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-upgrade-testing/+bug/1574969/+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 1575239] Re: sudo sssd ldap segmentation fault

[Marc Deslauriers]

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

Thanks for testing it. Could you please add a comment to bug 1565567
that you tested it successfully? Thanks!

** This bug has been marked a duplicate of bug 1565567
   segv in sudo_getgrgid

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

Title:
  sudo sssd ldap segmentation fault

Status in sudo package in Ubuntu:
  Confirmed

Bug description:
  This seems to be comparable to this bug: 
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1327268
  The same situation with the same results but in 16.04 Xenial Release - 
sudo_1.8.16-0ubuntu1_amd64.deb.

  The problem is resolved by installing the Trusty sudo package -
  sudo_1.8.9p5-1ubuntu1.1_amd64.deb.

  This problem does not exist if sssd is not installed.

  lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  apt-cache policy sudo
  sudo:
    Installed: 1.8.16-0ubuntu1
    Candidate: 1.8.16-0ubuntu1
    Version table:
   *** 1.8.16-0ubuntu1 500
  500 ftp://ls-mirror.csir.co.za/mirrors/ubuntu/repositories/xenial 
xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  The local repo is built from archive.ubuntu.com via debmirror.
  All updates installed.

  Expected result:
  sudo -l to show sudo permissions

  Received result:
  Segmentation fault (core dumped)

  /var/log/syslog:
  Apr 26 17:17:24 cstrydom-vm1 kernel: [  709.535083] sudo[10116]: segfault at 
0 ip 7fa7a7aac944 sp 7ffe547c4458 error 4 in 
sudoers.so[7fa7a7a8+4b000]

  gdb output:
  Starting program: /usr/bin/sudo
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  sudo: effective uid is not 0, is /usr/bin/sudo on a file system with the 
'nosuid' option set or an NFS file system without root privileges?
  [Inferior 1 (process 4911) exited with code 01]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1575239/+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 1565567] Re: segv in sudo_getgrgid

[Marc Deslauriers]

Don't worry about it, I changed it back. :)

** Changed in: sudo (Ubuntu Xenial)
   Status: Fix Released => Fix Committed

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

Title:
  segv in sudo_getgrgid

Status in sudo:
  Unknown
Status in sudo package in Ubuntu:
  Fix Released
Status in sudo source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  In certain environments, for example when using LDAP, users can end up
  in a group with no name. When that happens, sudo crashes when
  attempting to look up the group name for the debug log.

  Upstream has commited a simple fix for this issue, it has been
  commited to Yakkety, and uploaded to Xenial.

  [Test Case]

  I currently don't know an easy way to reproduce this, it is
  environment-specific. A package containing the fix was successfully
  tested in the problematic environment.

  [Regression Potential]

  A regression in the patch would prevent users from using sudo. The
  risk of regression is low since the patch only changes the debug log.


  Original report:

  If the user is in a group with no name (because libnss-db got removed
  and the group was defined there, for example...) then:

  the call to sudo_debug_printf in sudo_getgrgid
  (plugins/sudoers/pwutil.c, line 462) causes a SEGV when trying to get
  item->d.gr->gr_name (since item->d.gr is NULL).

To manage notifications about this bug go to:
https://bugs.launchpad.net/sudo/+bug/1565567/+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 1575152] Re: [SRU] gstreamer 1.8.1

[KyL416]

gstreamer-vaapi needs to be updated too or else the updated packages
refuse to install without removing it first.

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

Title:
  [SRU] gstreamer 1.8.1

Status in gst-libav1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-base1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-ugly1.0 package in Ubuntu:
  Fix Released
Status in gstreamer1.0 package in Ubuntu:
  Fix Released
Status in gst-libav1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-bad1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-base1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-good1.0 source package in Xenial:
  Fix Committed
Status in gst-plugins-ugly1.0 source package in Xenial:
  Fix Committed
Status in gstreamer1.0 source package in Xenial:
  Fix Committed

Bug description:
  [ Description ]

  We should keep up with GStreamer's bugfix releases in the 1.8 series
  that 16.04 shipped with.

  [ QA and testing ]

  Play a range of videos in Totem. Play a range of audio tracks in
  Rhythmbox. Try to stream audio and/or video. Try to install a missing
  codec.

  In all cases, make sure that everything which worked before still
  works.

  [ Regression potential ]

  One of the fixes could be bad. Watch out for it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: libgstreamer1.0-0 1.8.0-1
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Apr 26 13:16:04 2016
  InstallationDate: Installed on 2015-06-05 (325 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150605)
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1575152/+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 1387908] Re: [udev] FIDO u2f security keys should be supported out of the box

[Alex Willmer]

systemd-229-4ubuntu5 / udev-229-4ubuntu5 fixed this for me. Tested using
https://demo.yubico.com, a Yubikey Edge and Chromium 49.0.2623.108 on
x86_64.

** Tags removed: 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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1387908

Title:
  [udev] FIDO u2f security keys should be supported out of the box

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Trusty:
  Confirmed
Status in systemd source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * Users plugin U2F key and it does not work in Google Chrome

  [Test Case]

   * Have stock ubuntu install, without custom U2F rules or libu2f-host0
  installed

   * Use U2F factor authentication website e.g. google apps, github,
  yubico, etc.

   * Pluging in the key, should just work and complete U2F
  authentication instead of timing out

  [Regression Potential]

   * Should not conflict with libu2f-host0 udev rules which is where
  these are currently shipped

  FIDO u2f is an emerging standard for public-private cryptography based
  2nd factor authentication, which improves on OTP by mitigating
  phishing, man-in-the-middle attacks and reply attacks.

  Google Chrome supports u2f devices which are now widely available from
  Yubico (new premium neo Yubikeys and Security keys).

  However, udev rules are required to setup permissions to allow the
  web-browsers which are running as regular users to access the devices
  in question.

  E.g.:

  KERNEL=="hidraw*", SUBSYSTEM=="hidraw", MODE="0664", GROUP="plugdev",
  ATTRS{idVendor}=="1050", ATTRS{idProduct}=="0113|0114|0115|0116|0120"

  Something like that should be enabled by default, however probably not
  encode on the vendor/productid as other vendors will also make u2f
  devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1387908/+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 1577795] Re: Ubuntu touch Frieza ota-10.1 dropping connection to logitech k810

[Launchpad Bug Tracker]

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

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

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

Title:
  Ubuntu touch Frieza ota-10.1 dropping connection to logitech k810

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  I can successfully pair the k810 to my BQ Aquaris M10 FHD tablet.
  The connection state flips every few seconds between connected and 
disconected and the signal strength between excellent and none.
  I have tried forgetting the connection and repairing, and power-cycling then 
repeating the process, to no avail.
  Both the tablet and keyboard have a full charge.
  I have successfully paired and am using a Logitech Ultrathin mouse with the 
tablet.
  I have succesfully paired and use the k810 keyboard with several Android 
devices across multiple versions of Android.
  I have also paired and use the keyboard with Ubuntu 14.04 LTS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1577795/+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 1577795] Re: Ubuntu touch Frieza ota-10.1 dropping connection to logitech k810

[Niels Hoilm Frederiksen]

I have a m10 and a k810 and a Ultrathin mouse.

I found out that I can only connect one of the to devices. If some other
(mouse) is connected the logitech keyboard K810 disconects/reconects.

Testet with a dell travell mouse and i get the same k810
disconect/reconect error.

Though I can connect both mice and have them working side by side...

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

Title:
  Ubuntu touch Frieza ota-10.1 dropping connection to logitech k810

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  I can successfully pair the k810 to my BQ Aquaris M10 FHD tablet.
  The connection state flips every few seconds between connected and 
disconected and the signal strength between excellent and none.
  I have tried forgetting the connection and repairing, and power-cycling then 
repeating the process, to no avail.
  Both the tablet and keyboard have a full charge.
  I have successfully paired and am using a Logitech Ultrathin mouse with the 
tablet.
  I have succesfully paired and use the k810 keyboard with several Android 
devices across multiple versions of Android.
  I have also paired and use the keyboard with Ubuntu 14.04 LTS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1577795/+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 1565567] Re: segv in sudo_getgrgid

[Ben Kulbertis]

For the record, I did not intend to edit the status of this as recorded
above and am unable to revert it. That's embarrassing, sorry. I was
simply looking to see if there was more info about when this might be
released.

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

Title:
  segv in sudo_getgrgid

Status in sudo:
  Unknown
Status in sudo package in Ubuntu:
  Fix Released
Status in sudo source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  In certain environments, for example when using LDAP, users can end up
  in a group with no name. When that happens, sudo crashes when
  attempting to look up the group name for the debug log.

  Upstream has commited a simple fix for this issue, it has been
  commited to Yakkety, and uploaded to Xenial.

  [Test Case]

  I currently don't know an easy way to reproduce this, it is
  environment-specific. A package containing the fix was successfully
  tested in the problematic environment.

  [Regression Potential]

  A regression in the patch would prevent users from using sudo. The
  risk of regression is low since the patch only changes the debug log.


  Original report:

  If the user is in a group with no name (because libnss-db got removed
  and the group was defined there, for example...) then:

  the call to sudo_debug_printf in sudo_getgrgid
  (plugins/sudoers/pwutil.c, line 462) causes a SEGV when trying to get
  item->d.gr->gr_name (since item->d.gr is NULL).

To manage notifications about this bug go to:
https://bugs.launchpad.net/sudo/+bug/1565567/+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 1565567] Re: segv in sudo_getgrgid

[Ben Kulbertis]

** Changed in: sudo (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  segv in sudo_getgrgid

Status in sudo:
  Unknown
Status in sudo package in Ubuntu:
  Fix Released
Status in sudo source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  In certain environments, for example when using LDAP, users can end up
  in a group with no name. When that happens, sudo crashes when
  attempting to look up the group name for the debug log.

  Upstream has commited a simple fix for this issue, it has been
  commited to Yakkety, and uploaded to Xenial.

  [Test Case]

  I currently don't know an easy way to reproduce this, it is
  environment-specific. A package containing the fix was successfully
  tested in the problematic environment.

  [Regression Potential]

  A regression in the patch would prevent users from using sudo. The
  risk of regression is low since the patch only changes the debug log.


  Original report:

  If the user is in a group with no name (because libnss-db got removed
  and the group was defined there, for example...) then:

  the call to sudo_debug_printf in sudo_getgrgid
  (plugins/sudoers/pwutil.c, line 462) causes a SEGV when trying to get
  item->d.gr->gr_name (since item->d.gr is NULL).

To manage notifications about this bug go to:
https://bugs.launchpad.net/sudo/+bug/1565567/+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 1575239] Re: sudo sssd ldap segmentation fault

[Ben Kulbertis]

Thanks Marc. I just tested with 1.8.16-0ubuntu1.1 on xenial and it fixed
the issue for me. It would seem to me this is a duplicate.

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

Title:
  sudo sssd ldap segmentation fault

Status in sudo package in Ubuntu:
  Confirmed

Bug description:
  This seems to be comparable to this bug: 
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1327268
  The same situation with the same results but in 16.04 Xenial Release - 
sudo_1.8.16-0ubuntu1_amd64.deb.

  The problem is resolved by installing the Trusty sudo package -
  sudo_1.8.9p5-1ubuntu1.1_amd64.deb.

  This problem does not exist if sssd is not installed.

  lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  apt-cache policy sudo
  sudo:
    Installed: 1.8.16-0ubuntu1
    Candidate: 1.8.16-0ubuntu1
    Version table:
   *** 1.8.16-0ubuntu1 500
  500 ftp://ls-mirror.csir.co.za/mirrors/ubuntu/repositories/xenial 
xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  The local repo is built from archive.ubuntu.com via debmirror.
  All updates installed.

  Expected result:
  sudo -l to show sudo permissions

  Received result:
  Segmentation fault (core dumped)

  /var/log/syslog:
  Apr 26 17:17:24 cstrydom-vm1 kernel: [  709.535083] sudo[10116]: segfault at 
0 ip 7fa7a7aac944 sp 7ffe547c4458 error 4 in 
sudoers.so[7fa7a7a8+4b000]

  gdb output:
  Starting program: /usr/bin/sudo
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  sudo: effective uid is not 0, is /usr/bin/sudo on a file system with the 
'nosuid' option set or an NFS file system without root privileges?
  [Inferior 1 (process 4911) exited with code 01]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1575239/+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 1575239] Re: sudo sssd ldap segmentation fault

[Marc Deslauriers]

This may be a dupe of bug 1565567.

Have you tried the sudo package in xenial-proposed? (1.8.16-0ubuntu1.1)

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

Title:
  sudo sssd ldap segmentation fault

Status in sudo package in Ubuntu:
  Confirmed

Bug description:
  This seems to be comparable to this bug: 
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1327268
  The same situation with the same results but in 16.04 Xenial Release - 
sudo_1.8.16-0ubuntu1_amd64.deb.

  The problem is resolved by installing the Trusty sudo package -
  sudo_1.8.9p5-1ubuntu1.1_amd64.deb.

  This problem does not exist if sssd is not installed.

  lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  apt-cache policy sudo
  sudo:
    Installed: 1.8.16-0ubuntu1
    Candidate: 1.8.16-0ubuntu1
    Version table:
   *** 1.8.16-0ubuntu1 500
  500 ftp://ls-mirror.csir.co.za/mirrors/ubuntu/repositories/xenial 
xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  The local repo is built from archive.ubuntu.com via debmirror.
  All updates installed.

  Expected result:
  sudo -l to show sudo permissions

  Received result:
  Segmentation fault (core dumped)

  /var/log/syslog:
  Apr 26 17:17:24 cstrydom-vm1 kernel: [  709.535083] sudo[10116]: segfault at 
0 ip 7fa7a7aac944 sp 7ffe547c4458 error 4 in 
sudoers.so[7fa7a7a8+4b000]

  gdb output:
  Starting program: /usr/bin/sudo
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  sudo: effective uid is not 0, is /usr/bin/sudo on a file system with the 
'nosuid' option set or an NFS file system without root privileges?
  [Inferior 1 (process 4911) exited with code 01]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1575239/+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 1579419] [NEW] Bluetooth Mouse microsoft mobile 3600 not detected in GUI

[Javier Puiggros]

Public bug reported:

I turn on the bluetooth, scan for devices and can't detect the mouse, so I cant 
pair. The I opened a terminal and use bluetoothctl. It shows the mouse as new. 
Then use the pair command and the mouse start working.
The I back to the bluetooth GUI and nothing showing about the mouse. 
It worked fine with logitech keyboard without the need of the terminal command.

lsb_release -rd shows ubuntu 15.04
bluez 5.37-0ubuntu5~overlay1

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

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

Title:
  Bluetooth Mouse microsoft mobile 3600 not detected in GUI

Status in bluez package in Ubuntu:
  New

Bug description:
  I turn on the bluetooth, scan for devices and can't detect the mouse, so I 
cant pair. The I opened a terminal and use bluetoothctl. It shows the mouse as 
new. Then use the pair command and the mouse start working.
  The I back to the bluetooth GUI and nothing showing about the mouse. 
  It worked fine with logitech keyboard without the need of the terminal 
command.

  lsb_release -rd shows ubuntu 15.04
  bluez 5.37-0ubuntu5~overlay1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1579419/+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 585908] Fw: new message

[Philipp Schlesinger]

Hello!


You have a new message, please read 


phil...@sadleder.de

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

Title:
  Document all events (was: cross-comment events and *.conf files)

Status in upstart package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: upstart

  Finding where events are asserted and which *.conf files are sensitive
  to an asserted event is difficult.

  As a documentation habit, it would be good to have comments in both
  the *.conf files and the scripts that make assertiongs and the man
  pages for commands that assert events.

  For example,  /etc/init/rc-sysinit.conf is sensitive to the events
  "filesystem" and "net-device-up IFACE=lo".

  I believe "filesystem" is asserted by mountall,
  "strings /sbin/mountall" shows me strings for virtual-, local-, and 
remote-filesystems which I see in /etc/init/*.conf files.

  I see the assertion for "net-device-up" in /etc/network/if-
  up.d/upstart .

  These linkages would be easier to track and maintain if   
/etc/init/rc-sysinit.conf  pointed to mountall(8) and
  /etc/network/if-up.d/upstart  and if  those would point at   
/etc/init/rc-sysinit.conf .

  It might be useful to add an  "assert"  stanza to *.conf scripts so
  the absence of a support file, especially when it is unique, would be
  noted in an warning message or even cause an error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/585908/+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 1579417] [NEW] A wish to be able to record a phonecall

[GTriderXC]

Public bug reported:

It is just as simple. "My old Nokia phones..." :-))) all of them were
able to record the phone call. I miss this function.

** Affects: dialer-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 dialer-app in Ubuntu.
https://bugs.launchpad.net/bugs/1579417

Title:
  A wish to be able to record a phonecall

Status in dialer-app package in Ubuntu:
  New

Bug description:
  It is just as simple. "My old Nokia phones..." :-))) all of them were
  able to record the phone call. I miss this function.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1579417/+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 453330] Re: [Karmic] pipes are somewhat brocken

[ahtwbg]

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

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

Title:
  [Karmic] pipes are somewhat brocken

Status in tar package in Ubuntu:
  Fix Released
Status in tar package in Debian:
  Fix Released

Bug description:
  Binary package hint: bash

  some kind of pipes seem to be broken.

  Running a simple chain like:

  tar -xzOf zlib_1.2.3-3_i386.ipk ./data.tar.gz | tar tzf - | sed
  -e"s/^\\.//"

  works when run from the shell but failes when run from a skript. This
  used to work in Jaunty.

  I'll attach a simple test skript that triggers the error every time.

  ProblemType: Bug
  Architecture: amd64
  Date: Fri Oct 16 19:40:59 2009
  DistroRelease: Ubuntu 9.10
  NonfreeKernelModules: nvidia
  Package: bash 4.0-5ubuntu2
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-14.46-generic
  SourcePackage: bash
  Uname: Linux 2.6.31-14-generic x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tar/+bug/453330/+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 1575239] Re: sudo sssd ldap segmentation fault

[Marcus]

This is a major problem for me. I also cannot log into X.

Any ideal when this will get fixed?

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

Title:
  sudo sssd ldap segmentation fault

Status in sudo package in Ubuntu:
  Confirmed

Bug description:
  This seems to be comparable to this bug: 
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1327268
  The same situation with the same results but in 16.04 Xenial Release - 
sudo_1.8.16-0ubuntu1_amd64.deb.

  The problem is resolved by installing the Trusty sudo package -
  sudo_1.8.9p5-1ubuntu1.1_amd64.deb.

  This problem does not exist if sssd is not installed.

  lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  apt-cache policy sudo
  sudo:
    Installed: 1.8.16-0ubuntu1
    Candidate: 1.8.16-0ubuntu1
    Version table:
   *** 1.8.16-0ubuntu1 500
  500 ftp://ls-mirror.csir.co.za/mirrors/ubuntu/repositories/xenial 
xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  The local repo is built from archive.ubuntu.com via debmirror.
  All updates installed.

  Expected result:
  sudo -l to show sudo permissions

  Received result:
  Segmentation fault (core dumped)

  /var/log/syslog:
  Apr 26 17:17:24 cstrydom-vm1 kernel: [  709.535083] sudo[10116]: segfault at 
0 ip 7fa7a7aac944 sp 7ffe547c4458 error 4 in 
sudoers.so[7fa7a7a8+4b000]

  gdb output:
  Starting program: /usr/bin/sudo
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  sudo: effective uid is not 0, is /usr/bin/sudo on a file system with the 
'nosuid' option set or an NFS file system without root privileges?
  [Inferior 1 (process 4911) exited with code 01]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1575239/+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 1546641] Re: unity-settings-daemon crashed with SIGSEGV in up_exported_daemon_get_lid_is_closed()

[Muhammad Suleman Hasib]

I have been facing this issue for a while now.

Some details of my system are as follows:

System:Host: sitspak Kernel: 4.4.0-22-generic x86_64 (64 bit) Desktop: 
Unity 7.4.0
   Distro: Ubuntu 16.04 xenial
Machine:   System: Hewlett-Packard (portable) product: HP ZBook 15 G2 v: 
A3009DD10303
   Mobo: Hewlett-Packard model: 2253 v: KBC Version 03.10
   Bios: Hewlett-Packard v: M70 Ver. 01.07 date: 02/26/2015
CPU:   Quad core Intel Core i7-4810MQ (-HT-MCP-) cache: 6144 KB 
   clock speeds: max: 3800 MHz 1: 2805 MHz 2: 2801 MHz 3: 2800 MHz 4: 
2987 MHz 5: 2800 MHz
   6: 2800 MHz 7: 2808 MHz 8: 2879 MHz
Graphics:  Card-1: Intel 4th Gen Core Processor Integrated Graphics Controller
   Card-2: NVIDIA GK106GLM [Quadro K2100M]
   Display Server: X.Org 1.18.3 driver: nvidia Resolution: 
1920x1080@60.01hz
   GLX Renderer: Quadro K2100M/PCIe/SSE2 GLX Version: 4.5.0 NVIDIA 
361.42

I have observed following:

1. This happens when a external usb webcam is attached; dmesg regarding
camera is as follows.

uvcvideo: Found UVC 1.00 device A4 TECH HD PC Camera (0ac8:3500)
[  +0.000882] input: A4 TECH HD PC Camera as 
/devices/pci:00/:00:14.0/usb3/3-10/3-10:1.0/inpu
[  +0.000116] usbcore: registered new interface driver uvcvideo
[  +0.02] USB Video Class driver (1.1.1)

2. My themes fall back to classic gnome as well. To get around I restart 
lightdm service.
3. It was worse in Ubuntu 15.10 but in 16.04 some window decorations, icons & 
fonts fall back.
4. A dmesg related to Nvidia which might be interesting:

ACPI Warning: \_SB_.PCI0.PEGP.DGFX._DSM: Argument #4 type mismatch -
Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)

Hope this helps!

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

Title:
  unity-settings-daemon crashed with SIGSEGV in
  up_exported_daemon_get_lid_is_closed()

Status in unity-settings-daemon package in Ubuntu:
  Triaged
Status in upower package in Ubuntu:
  Confirmed
Status in unity-settings-daemon source package in Xenial:
  Triaged
Status in upower source package in Xenial:
  Confirmed
Status in unity-settings-daemon source package in Yakkety:
  Triaged
Status in upower source package in Yakkety:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/8ca9c548fc4e2fc1d4bf827bbd85c72df59313f8

  Ubuntu 16.04 crashes immediately on login. Default settings not
  applied and appearance is a bit ugly (incorrect font hinting, in-
  window menus etc).

  ---

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Feb 17 13:52:13 2016
  ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon
  InstallationDate: Installed on 2016-02-08 (8 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205)
  ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x3aae60fe69 : 
mov(%rbx),%rdi
   PC (0x3aae60fe69) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity-settings-daemon
  StacktraceTop:
   up_exported_daemon_get_lid_is_closed () from 
/usr/lib/x86_64-linux-gnu/libupower-glib.so.3
   gsd_power_manager_start () from 
/usr/lib/unity-settings-daemon-1.0/libpower.so
   ?? () from /usr/lib/unity-settings-daemon-1.0/libpower.so
   gnome_settings_plugin_info_activate ()
   ?? ()
  Title: unity-settings-daemon crashed with SIGSEGV in 
up_exported_daemon_get_lid_is_closed()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1546641/+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 1579407] JournalErrors.txt

[bankey]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1579407/+attachment/4658234/+files/JournalErrors.txt

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

Title:
  actually addition to bugreport 1579404

Status in lightdm package in Ubuntu:
  New

Bug description:
  apologies, maybe this one should be merged with report 1579404..

  after some more google it's more a lightdm issue then xorg I think.

  regards,

  Arno

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.39-lowlatency 4.4.8
  Uname: Linux 4.4.0-22-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat May  7 20:06:39 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-09-24 (225 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  LightdmGreeterLogOld:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   upstart: indicator-application main process (2821) killed by TERM signal
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (14 days ago)
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-09-24 (225 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  LightdmGreeterLogOld:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   upstart: indicator-application main process (2821) killed by TERM signal
  Package: lightdm 1.18.1-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-22.39-lowlatency 4.4.8
  Tags:  xenial
  Uname: Linux 4.4.0-22-lowlatency x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (14 days ago)
  UserGroups:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1579407/+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 1579407] Re: actually addition to bugreport 1579404

[bankey]

these logs were after reproducing the issue.
If any more info is needed, please let me know.

regards,

Arno

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

Title:
  actually addition to bugreport 1579404

Status in lightdm package in Ubuntu:
  New

Bug description:
  apologies, maybe this one should be merged with report 1579404..

  after some more google it's more a lightdm issue then xorg I think.

  regards,

  Arno

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.39-lowlatency 4.4.8
  Uname: Linux 4.4.0-22-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat May  7 20:06:39 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-09-24 (225 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  LightdmGreeterLogOld:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   upstart: indicator-application main process (2821) killed by TERM signal
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (14 days ago)
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-09-24 (225 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  LightdmGreeterLogOld:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   upstart: indicator-application main process (2821) killed by TERM signal
  Package: lightdm 1.18.1-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-22.39-lowlatency 4.4.8
  Tags:  xenial
  Uname: Linux 4.4.0-22-lowlatency x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (14 days ago)
  UserGroups:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1579407/+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 1579407] LightdmDisplayLog.txt

[bankey]

apport information

** Attachment added: "LightdmDisplayLog.txt"
   
https://bugs.launchpad.net/bugs/1579407/+attachment/4658235/+files/LightdmDisplayLog.txt

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

Title:
  actually addition to bugreport 1579404

Status in lightdm package in Ubuntu:
  New

Bug description:
  apologies, maybe this one should be merged with report 1579404..

  after some more google it's more a lightdm issue then xorg I think.

  regards,

  Arno

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.39-lowlatency 4.4.8
  Uname: Linux 4.4.0-22-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat May  7 20:06:39 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-09-24 (225 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  LightdmGreeterLogOld:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   upstart: indicator-application main process (2821) killed by TERM signal
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (14 days ago)
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-09-24 (225 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  LightdmGreeterLogOld:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   upstart: indicator-application main process (2821) killed by TERM signal
  Package: lightdm 1.18.1-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-22.39-lowlatency 4.4.8
  Tags:  xenial
  Uname: Linux 4.4.0-22-lowlatency x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (14 days ago)
  UserGroups:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1579407/+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 1579407] LightdmUsersConfig.txt

[bankey]

apport information

** Attachment added: "LightdmUsersConfig.txt"
   
https://bugs.launchpad.net/bugs/1579407/+attachment/4658238/+files/LightdmUsersConfig.txt

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

Title:
  actually addition to bugreport 1579404

Status in lightdm package in Ubuntu:
  New

Bug description:
  apologies, maybe this one should be merged with report 1579404..

  after some more google it's more a lightdm issue then xorg I think.

  regards,

  Arno

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.39-lowlatency 4.4.8
  Uname: Linux 4.4.0-22-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat May  7 20:06:39 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-09-24 (225 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  LightdmGreeterLogOld:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   upstart: indicator-application main process (2821) killed by TERM signal
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (14 days ago)
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-09-24 (225 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  LightdmGreeterLogOld:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   upstart: indicator-application main process (2821) killed by TERM signal
  Package: lightdm 1.18.1-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-22.39-lowlatency 4.4.8
  Tags:  xenial
  Uname: Linux 4.4.0-22-lowlatency x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (14 days ago)
  UserGroups:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1579407/+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 1579407] LightdmLog.txt

[bankey]

apport information

** Attachment added: "LightdmLog.txt"
   
https://bugs.launchpad.net/bugs/1579407/+attachment/4658237/+files/LightdmLog.txt

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

Title:
  actually addition to bugreport 1579404

Status in lightdm package in Ubuntu:
  New

Bug description:
  apologies, maybe this one should be merged with report 1579404..

  after some more google it's more a lightdm issue then xorg I think.

  regards,

  Arno

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.39-lowlatency 4.4.8
  Uname: Linux 4.4.0-22-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat May  7 20:06:39 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-09-24 (225 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  LightdmGreeterLogOld:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   upstart: indicator-application main process (2821) killed by TERM signal
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (14 days ago)
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-09-24 (225 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  LightdmGreeterLogOld:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   upstart: indicator-application main process (2821) killed by TERM signal
  Package: lightdm 1.18.1-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-22.39-lowlatency 4.4.8
  Tags:  xenial
  Uname: Linux 4.4.0-22-lowlatency x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (14 days ago)
  UserGroups:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1579407/+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 1579407] ProcEnviron.txt

[bankey]

apport information

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

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

Title:
  actually addition to bugreport 1579404

Status in lightdm package in Ubuntu:
  New

Bug description:
  apologies, maybe this one should be merged with report 1579404..

  after some more google it's more a lightdm issue then xorg I think.

  regards,

  Arno

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.39-lowlatency 4.4.8
  Uname: Linux 4.4.0-22-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat May  7 20:06:39 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-09-24 (225 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  LightdmGreeterLogOld:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   upstart: indicator-application main process (2821) killed by TERM signal
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (14 days ago)
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-09-24 (225 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  LightdmGreeterLogOld:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   upstart: indicator-application main process (2821) killed by TERM signal
  Package: lightdm 1.18.1-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-22.39-lowlatency 4.4.8
  Tags:  xenial
  Uname: Linux 4.4.0-22-lowlatency x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (14 days ago)
  UserGroups:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1579407/+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 1579407] Dependencies.txt

[bankey]

apport information

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

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

Title:
  actually addition to bugreport 1579404

Status in lightdm package in Ubuntu:
  New

Bug description:
  apologies, maybe this one should be merged with report 1579404..

  after some more google it's more a lightdm issue then xorg I think.

  regards,

  Arno

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.39-lowlatency 4.4.8
  Uname: Linux 4.4.0-22-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat May  7 20:06:39 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-09-24 (225 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  LightdmGreeterLogOld:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   upstart: indicator-application main process (2821) killed by TERM signal
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (14 days ago)
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-09-24 (225 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  LightdmGreeterLogOld:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   upstart: indicator-application main process (2821) killed by TERM signal
  Package: lightdm 1.18.1-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-22.39-lowlatency 4.4.8
  Tags:  xenial
  Uname: Linux 4.4.0-22-lowlatency x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (14 days ago)
  UserGroups:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1579407/+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 1579407] LightdmGreeterLog.txt

[bankey]

apport information

** Attachment added: "LightdmGreeterLog.txt"
   
https://bugs.launchpad.net/bugs/1579407/+attachment/4658236/+files/LightdmGreeterLog.txt

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

Title:
  actually addition to bugreport 1579404

Status in lightdm package in Ubuntu:
  New

Bug description:
  apologies, maybe this one should be merged with report 1579404..

  after some more google it's more a lightdm issue then xorg I think.

  regards,

  Arno

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.39-lowlatency 4.4.8
  Uname: Linux 4.4.0-22-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat May  7 20:06:39 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-09-24 (225 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  LightdmGreeterLogOld:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   upstart: indicator-application main process (2821) killed by TERM signal
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (14 days ago)
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-09-24 (225 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  LightdmGreeterLogOld:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   upstart: indicator-application main process (2821) killed by TERM signal
  Package: lightdm 1.18.1-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-22.39-lowlatency 4.4.8
  Tags:  xenial
  Uname: Linux 4.4.0-22-lowlatency x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (14 days ago)
  UserGroups:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1579407/+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 1579407] Re: actually addition to bugreport 1579404

[bankey]

the info now is after restart lightdm.
in a little i'll reproduce the error and will add the logs again. (properly i 
hope)


** Tags added: apport-collected

** Description changed:

  apologies, maybe this one should be merged with report 1579404..
  
  after some more google it's more a lightdm issue then xorg I think.
  
  regards,
  
  Arno
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.39-lowlatency 4.4.8
  Uname: Linux 4.4.0-22-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat May  7 20:06:39 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-09-24 (225 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  LightdmGreeterLogOld:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   upstart: indicator-application main process (2821) killed by TERM signal
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (14 days ago)
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2
+ Architecture: amd64
+ DistroRelease: Ubuntu 16.04
+ EcryptfsInUse: Yes
+ InstallationDate: Installed on 2015-09-24 (225 days ago)
+ InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
+ LightdmGreeterLogOld:
+  ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
+  ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
+  ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
+  upstart: indicator-application main process (2821) killed by TERM signal
+ Package: lightdm 1.18.1-0ubuntu1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 4.4.0-22.39-lowlatency 4.4.8
+ Tags:  xenial
+ Uname: Linux 4.4.0-22-lowlatency x86_64
+ UpgradeStatus: Upgraded to xenial on 2016-04-22 (14 days ago)
+ UserGroups:
+  
+ _MarkForUpload: True

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

Title:
  actually addition to bugreport 1579404

Status in lightdm package in Ubuntu:
  New

Bug description:
  apologies, maybe this one should be merged with report 1579404..

  after some more google it's more a lightdm issue then xorg I think.

  regards,

  Arno

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.39-lowlatency 4.4.8
  Uname: Linux 4.4.0-22-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat May  7 20:06:39 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-09-24 (225 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  LightdmGreeterLogOld:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   upstart: indicator-application main process (2821) killed by TERM signal
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (14 days ago)
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-09-24 (225 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  LightdmGreeterLogOld:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   upstart: indicator-application main process (2821) killed by TERM signal
  Package: lightdm 1.18.1-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-22.39-lowlatency 4.4.8
  Tags:  xenial
  Uname: Linux 4.4.0-22-lowlatency x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (14 days ago)
  UserGroups:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1579407/+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 1579407] [NEW] actually addition to bugreport 1579404

[bankey]

Public bug reported:

apologies, maybe this one should be merged with report 1579404..

after some more google it's more a lightdm issue then xorg I think.

regards,

Arno

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lightdm 1.18.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-22.39-lowlatency 4.4.8
Uname: Linux 4.4.0-22-lowlatency x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Sat May  7 20:06:39 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-09-24 (225 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
LightdmGreeterLogOld:
 ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
 ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
 ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
 upstart: indicator-application main process (2821) killed by TERM signal
SourcePackage: lightdm
UpgradeStatus: Upgraded to xenial on 2016-04-22 (14 days ago)
--- 
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
DistroRelease: Ubuntu 16.04
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-09-24 (225 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
LightdmGreeterLogOld:
 ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
 ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
 ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
 upstart: indicator-application main process (2821) killed by TERM signal
Package: lightdm 1.18.1-0ubuntu1
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 4.4.0-22.39-lowlatency 4.4.8
Tags:  xenial
Uname: Linux 4.4.0-22-lowlatency x86_64
UpgradeStatus: Upgraded to xenial on 2016-04-22 (14 days ago)
UserGroups:
 
_MarkForUpload: True

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


** Tags: 1579404 amd64 apport-bug apport-collected xenial

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

Title:
  actually addition to bugreport 1579404

Status in lightdm package in Ubuntu:
  New

Bug description:
  apologies, maybe this one should be merged with report 1579404..

  after some more google it's more a lightdm issue then xorg I think.

  regards,

  Arno

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.39-lowlatency 4.4.8
  Uname: Linux 4.4.0-22-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat May  7 20:06:39 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-09-24 (225 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  LightdmGreeterLogOld:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   upstart: indicator-application main process (2821) killed by TERM signal
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (14 days ago)
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-09-24 (225 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  LightdmGreeterLogOld:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   upstart: indicator-application main process (2821) killed by TERM signal
  Package: lightdm 1.18.1-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-22.39-lowlatency 4.4.8
  Tags:  xenial
  Uname: Linux 4.4.0-22-lowlatency x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (14 days ago)
  UserGroups:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1579407/+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 1579407] Re: actually addition to bugreport 1579404

[bankey]

mouse not visible, but working after resume.

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

Title:
  actually addition to bugreport 1579404

Status in lightdm package in Ubuntu:
  New

Bug description:
  apologies, maybe this one should be merged with report 1579404..

  after some more google it's more a lightdm issue then xorg I think.

  regards,

  Arno

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.39-lowlatency 4.4.8
  Uname: Linux 4.4.0-22-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat May  7 20:06:39 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-09-24 (225 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  LightdmGreeterLogOld:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   upstart: indicator-application main process (2821) killed by TERM signal
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (14 days ago)
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-09-24 (225 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  LightdmGreeterLogOld:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   upstart: indicator-application main process (2821) killed by TERM signal
  Package: lightdm 1.18.1-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-22.39-lowlatency 4.4.8
  Tags:  xenial
  Uname: Linux 4.4.0-22-lowlatency x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (14 days ago)
  UserGroups:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1579407/+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 1538701] Re: For printing on Ubuntu Touch with daemons running on-demand, correct *.override files are needed

[Pat McGowan]

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

** This bug has been marked a duplicate of bug 1520346
   /etc/init/cups.override needs to get updated to work with the current 
version of CUPS

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

Title:
  For printing on Ubuntu Touch with daemons running on-demand, correct
  *.override files are needed

Status in Canonical System Image:
  In Progress
Status in lxc-android-config package in Ubuntu:
  In Progress

Bug description:
  I am working on getting the Ubuntu printing stack onto the phone, see
  bug 1520346, bug 1519914, and bug 1509423 (see details about my setup
  in these bug reports).

  For that the packages cups-daemon, cups-browsed, avahi-daemon,  cups-
  core-drivers, cups-filters-core-drivers, cups-client, and their
  dependencies are planned to be added to the system.

  In addition, the system needs to be configured to run avahi-daemon,
  cups-browsed, and cupsd on-demand. To do so, the following three
  *.override files are needed in /etc/init/:

  avahi-daemon.override:

  --
  # avahi-daemon - mDNS/DNS-SD daemon
  # overrides for touch
  # do not start avahi-daemon on boot
  manual
  --

  cups-browsed.override:

  --
  # cups-browsed - Bonjour remote printer browsing daemon
  # overrides for touch
  # do not start cups-browsed on boot
  manual
  # do not respawn when cups-browsed shuts down by itself
  normal exit 0
  # start cups-browsed in auto-shutdown mode, creating queues for native IPP
  # network printers, and using IPv4 IPs to reference remote printers
  exec /usr/sbin/cups-browsed --autoshutdown=avahi -o IPBasedDeviceURIs=IPv4 -o 
CreateIPPPrinterQueues=Yes
  --

  cups.override:

  --
  # cups - CUPS Printing spooler and server
  # overrides for touch
  # socket activation
  start on socket PROTO=inet PORT=631 ADDR=127.0.0.1
  # do not respawn when cupsd shuts down by itself
  normal exit 0
  # start cupsd in auto-shutdown mode
  exec /usr/sbin/cupsd -f -l
  --

  I have tested these files on a Nexus 4 with the current Xenial
  development environment:

  ubuntu-device-flash touch --channel=ubuntu-touch/devel-proposed/ubuntu

  A print dialog working according to the principles of the attached
  script phone-print.sh will print in this environment and all daemons
  will terminate when printing is done.

  Run the script always with three arguments:

  ./phone-print.sh   

   is the time how long the printer list is shown,  is
  the queue on which you print the test job, and  is the file to
  be printed, preferably PDF. The script will at first show the printer
  list updating every second, then print a job and afterwards observe
  the cups-related processes, so that it demoes nicely the process.

  A merge proposal for the *.override files will be added to this bug
  report.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1538701/+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 1579404] Re: mouse indicator lost after resume

[bankey]

apologies. workaround was to logoff and logon again, till this mornings apt-get 
update && apt-get upgrade -y.. :-(
Now is my workaround to restart lightgdm. logoff and login is not sufficient 
anymore.. :-(

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

Title:
  mouse indicator lost after resume

Status in xorg package in Ubuntu:
  New

Bug description:
  mouse is lost after resume
  Workaround is logoff and logon after resume (or reboot)

  similar like this post: http://askubuntu.com/questions/360795/mouse-
  arrow-disappear-after-computer-wake-up-from-suspend-mode-in-
  ubuntu-13-10

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.39-lowlatency 4.4.8
  Uname: Linux 4.4.0-22-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat May  7 19:50:36 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-09-24 (225 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (14 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1579404/+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 1579403] [NEW] Random characters in screen text suddenly disappear after wake from sleep or switching user

[Eugene Romanenko]

Public bug reported:

After wake from sleep or switching user, characters suddenly disappear.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
Uname: Linux 4.4.0-18-generic x86_64
NonfreeKernelModules: wl
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
BootLog:
 
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: Sat May  7 20:51:58 2016
DistUpgraded: 2016-03-03 21:54:17,365 DEBUG enabling apt cron job
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.271+bdcom, 4.4.0-18-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 4.4.0-21-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 4.4.0-22-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:3978]
InstallationDate: Installed on 2015-12-02 (156 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 006: ID 04f3:0446 Elan Microelectronics Corp. 
 Bus 001 Device 003: ID 105b:e065 Foxconn International, Inc. BCM43142A0 
Bluetooth module
 Bus 001 Device 002: ID 0c45:6514 Microdia 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 20404
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic.efi.signed 
root=UUID=fe6b4e61-411f-4d2c-8503-d340e6c8bd4c ro quiet splash pcie_aspm 
i915.lvds_downclock=1 i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2016-03-03 (64 days ago)
dmi.bios.date: 05/21/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: A0CN26WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Lenovo Flex 2-14
dmi.board.vendor: LENOVO
dmi.board.version: 31900058 Std
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo Flex 2-14
dmi.modalias: 
dmi:bvnLENOVO:bvrA0CN26WW:bd05/21/2014:svnLENOVO:pn20404:pvrLenovoFlex2-14:rvnLENOVO:rnLenovoFlex2-14:rvr31900058Std:cvnLENOVO:ct10:cvrLenovoFlex2-14:
dmi.product.name: 20404
dmi.product.version: Lenovo Flex 2-14
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-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.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
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: Fri May  6 18:09:14 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id1094 
 vendor LGD
xserver.version: 2:1.18.3-1ubuntu2

** 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/1579403

Title:
   Random characters in screen text suddenly disappear after wake from
  sleep or switching user

Status in xorg package in Ubuntu:
  New

Bug description:
  After wake from sleep or switching user, characters suddenly
  disappear.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog:
   
  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: Sat May  7 20:51:58 2016
  DistUpgraded: 2016-03-03 21:54:17,365 DEBUG enabling apt cron job
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.4.0-18-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.4.0-21-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.4.0-22-generic, x86_64: installed
  

[Touch-packages] [Bug 1579403] Re: Random characters in screen text suddenly disappear after wake from sleep or switching user

[Eugene Romanenko]

** Attachment added: "Screenshot of nautilus"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1579403/+attachment/4658191/+files/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202016-05-07%2020-58-25.png

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

Title:
   Random characters in screen text suddenly disappear after wake from
  sleep or switching user

Status in xorg package in Ubuntu:
  New

Bug description:
  After wake from sleep or switching user, characters suddenly
  disappear.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog:
   
  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: Sat May  7 20:51:58 2016
  DistUpgraded: 2016-03-03 21:54:17,365 DEBUG enabling apt cron job
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.4.0-18-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.4.0-21-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.4.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:3978]
  InstallationDate: Installed on 2015-12-02 (156 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 04f3:0446 Elan Microelectronics Corp. 
   Bus 001 Device 003: ID 105b:e065 Foxconn International, Inc. BCM43142A0 
Bluetooth module
   Bus 001 Device 002: ID 0c45:6514 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20404
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic.efi.signed 
root=UUID=fe6b4e61-411f-4d2c-8503-d340e6c8bd4c ro quiet splash pcie_aspm 
i915.lvds_downclock=1 i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-03-03 (64 days ago)
  dmi.bios.date: 05/21/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A0CN26WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo Flex 2-14
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058 Std
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Flex 2-14
  dmi.modalias: 
dmi:bvnLENOVO:bvrA0CN26WW:bd05/21/2014:svnLENOVO:pn20404:pvrLenovoFlex2-14:rvnLENOVO:rnLenovoFlex2-14:rvr31900058Std:cvnLENOVO:ct10:cvrLenovoFlex2-14:
  dmi.product.name: 20404
  dmi.product.version: Lenovo Flex 2-14
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-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.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  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: Fri May  6 18:09:14 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1094 
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1579403/+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 1579403] Re: Random characters in screen text suddenly disappear after wake from sleep or switching user

[Eugene Romanenko]

I think it related to the intel driver, as I never seen such problem on
nvidia-based desktop PC.

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

Title:
   Random characters in screen text suddenly disappear after wake from
  sleep or switching user

Status in xorg package in Ubuntu:
  New

Bug description:
  After wake from sleep or switching user, characters suddenly
  disappear.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog:
   
  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: Sat May  7 20:51:58 2016
  DistUpgraded: 2016-03-03 21:54:17,365 DEBUG enabling apt cron job
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.4.0-18-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.4.0-21-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.4.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:3978]
  InstallationDate: Installed on 2015-12-02 (156 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 04f3:0446 Elan Microelectronics Corp. 
   Bus 001 Device 003: ID 105b:e065 Foxconn International, Inc. BCM43142A0 
Bluetooth module
   Bus 001 Device 002: ID 0c45:6514 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20404
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic.efi.signed 
root=UUID=fe6b4e61-411f-4d2c-8503-d340e6c8bd4c ro quiet splash pcie_aspm 
i915.lvds_downclock=1 i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-03-03 (64 days ago)
  dmi.bios.date: 05/21/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A0CN26WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo Flex 2-14
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058 Std
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Flex 2-14
  dmi.modalias: 
dmi:bvnLENOVO:bvrA0CN26WW:bd05/21/2014:svnLENOVO:pn20404:pvrLenovoFlex2-14:rvnLENOVO:rnLenovoFlex2-14:rvr31900058Std:cvnLENOVO:ct10:cvrLenovoFlex2-14:
  dmi.product.name: 20404
  dmi.product.version: Lenovo Flex 2-14
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-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.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  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: Fri May  6 18:09:14 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1094 
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1579403/+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 1579405] [NEW] configure idle menu item does not run and freezes entire menu bar

[Sam Schulman]

Public bug reported:

Ubuntu Xenial Xerus
Using idle for python 3.5.1
Clicked on menu item "Configure IDLE" in "Options" menu
Expected settings and configuration dialog to popup
Nothing happened, and the entire menu bar froze and would not work.


Error as returned when running application from terminal:

Exception in Tkinter callback
Traceback (most recent call last):
  File "/usr/lib/python3.5/tkinter/__init__.py", line 1553, in __call__
return self.func(*args)
  File "/usr/lib/python3.5/idlelib/EditorWindow.py", line 516, in config_dialog
configDialog.ConfigDialog(self.top,'Settings')
  File "/usr/lib/python3.5/idlelib/configDialog.py", line 74, in __init__
self.LoadConfigs()
  File "/usr/lib/python3.5/idlelib/configDialog.py", line 1086, in LoadConfigs
self.LoadFontCfg()
  File "/usr/lib/python3.5/idlelib/configDialog.py", line 988, in LoadFontCfg
self.SetFontSample()
  File "/usr/lib/python3.5/idlelib/configDialog.py", line 866, in SetFontSample
self.labelFontSample.config(font=newFont)
  File "/usr/lib/python3.5/tkinter/__init__.py", line 1333, in configure
return self._configure('configure', cnf, kw)
  File "/usr/lib/python3.5/tkinter/__init__.py", line 1324, in _configure
self.tk.call(_flatten((self._w, cmd)) + self._options(cnf))
_tkinter.TclError: expected integer but got ""

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: idle3 3.5.1-3
ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Sat May  7 13:41:42 2016
InstallationDate: Installed on 2016-05-04 (2 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitecture: all
SourcePackage: python3-defaults
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: python3-defaults (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 python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/1579405

Title:
  configure idle menu item does not run and freezes entire menu bar

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  Ubuntu Xenial Xerus
  Using idle for python 3.5.1
  Clicked on menu item "Configure IDLE" in "Options" menu
  Expected settings and configuration dialog to popup
  Nothing happened, and the entire menu bar froze and would not work.

  
  Error as returned when running application from terminal:

  Exception in Tkinter callback
  Traceback (most recent call last):
File "/usr/lib/python3.5/tkinter/__init__.py", line 1553, in __call__
  return self.func(*args)
File "/usr/lib/python3.5/idlelib/EditorWindow.py", line 516, in 
config_dialog
  configDialog.ConfigDialog(self.top,'Settings')
File "/usr/lib/python3.5/idlelib/configDialog.py", line 74, in __init__
  self.LoadConfigs()
File "/usr/lib/python3.5/idlelib/configDialog.py", line 1086, in LoadConfigs
  self.LoadFontCfg()
File "/usr/lib/python3.5/idlelib/configDialog.py", line 988, in LoadFontCfg
  self.SetFontSample()
File "/usr/lib/python3.5/idlelib/configDialog.py", line 866, in 
SetFontSample
  self.labelFontSample.config(font=newFont)
File "/usr/lib/python3.5/tkinter/__init__.py", line 1333, in configure
  return self._configure('configure', cnf, kw)
File "/usr/lib/python3.5/tkinter/__init__.py", line 1324, in _configure
  self.tk.call(_flatten((self._w, cmd)) + self._options(cnf))
  _tkinter.TclError: expected integer but got ""

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: idle3 3.5.1-3
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat May  7 13:41:42 2016
  InstallationDate: Installed on 2016-05-04 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: python3-defaults
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1579405/+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 1579403] Re: Random characters in screen text suddenly disappear after wake from sleep or switching user

[Eugene Romanenko]

** Attachment added: "Screenshot of thunderbird"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1579403/+attachment/4658190/+files/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202016-05-07%2020-57-48.png

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

Title:
   Random characters in screen text suddenly disappear after wake from
  sleep or switching user

Status in xorg package in Ubuntu:
  New

Bug description:
  After wake from sleep or switching user, characters suddenly
  disappear.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog:
   
  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: Sat May  7 20:51:58 2016
  DistUpgraded: 2016-03-03 21:54:17,365 DEBUG enabling apt cron job
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.4.0-18-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.4.0-21-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.4.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:3978]
  InstallationDate: Installed on 2015-12-02 (156 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 04f3:0446 Elan Microelectronics Corp. 
   Bus 001 Device 003: ID 105b:e065 Foxconn International, Inc. BCM43142A0 
Bluetooth module
   Bus 001 Device 002: ID 0c45:6514 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20404
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic.efi.signed 
root=UUID=fe6b4e61-411f-4d2c-8503-d340e6c8bd4c ro quiet splash pcie_aspm 
i915.lvds_downclock=1 i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-03-03 (64 days ago)
  dmi.bios.date: 05/21/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A0CN26WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo Flex 2-14
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058 Std
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Flex 2-14
  dmi.modalias: 
dmi:bvnLENOVO:bvrA0CN26WW:bd05/21/2014:svnLENOVO:pn20404:pvrLenovoFlex2-14:rvnLENOVO:rnLenovoFlex2-14:rvr31900058Std:cvnLENOVO:ct10:cvrLenovoFlex2-14:
  dmi.product.name: 20404
  dmi.product.version: Lenovo Flex 2-14
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-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.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  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: Fri May  6 18:09:14 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1094 
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1579403/+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 1579404] [NEW] mouse indicator lost after resume

[bankey]

Public bug reported:

mouse is lost after resume
Workaround is logoff and logon after resume (or reboot)

similar like this post: http://askubuntu.com/questions/360795/mouse-
arrow-disappear-after-computer-wake-up-from-suspend-mode-in-ubuntu-13-10

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-22.39-lowlatency 4.4.8
Uname: Linux 4.4.0-22-lowlatency x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: XFCE
Date: Sat May  7 19:50:36 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-09-24 (225 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to xenial on 2016-04-22 (14 days ago)

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


** Tags: amd64 apport-bug mouse resume 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/1579404

Title:
  mouse indicator lost after resume

Status in xorg package in Ubuntu:
  New

Bug description:
  mouse is lost after resume
  Workaround is logoff and logon after resume (or reboot)

  similar like this post: http://askubuntu.com/questions/360795/mouse-
  arrow-disappear-after-computer-wake-up-from-suspend-mode-in-
  ubuntu-13-10

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.39-lowlatency 4.4.8
  Uname: Linux 4.4.0-22-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat May  7 19:50:36 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-09-24 (225 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (14 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1579404/+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 1579182] Re: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A

[Marcelo Fernandez]

I've upgraded from Ubuntu 14.04, and I'm sure that this issue wasn't
there.

But in the bug #1525390 the user said that was happening in 15.10, so it
seems to be affecting that version too.

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

Title:
  [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on
  pipe A

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 16.04 upgraded from Ubuntu 14.04 on a Dell Inspiron 14z, w
  /Intel-ATI hybrid graphics (but DIS card is OFF through
  vgaswitcheroo).

  Just like bug no. #1525390 [1], Chrome shows some artifacts randomly
  and I have the same kernel trace but from 10 days ago (I use this
  system everyday and it didn't happened since then).

  [1] https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1525390

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  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: Fri May  6 15:17:08 2016
  DistUpgraded: 2016-04-25 18:04:08,937 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: vboxhost, 5.0.20, 4.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:057f]
   Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7550M/7570M/7650M] 
[1002:6841] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2013-08-12 (997 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  LightdmDisplayLog:
   [dix] EventToCore: Not implemented yet 
   [dix] EventToCore: Not implemented yet
  MachineType: Dell Inc. Inspiron 5423
  ProcEnviron:
   LANGUAGE=es_AR:es
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=es_AR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-25 (10 days ago)
  dmi.bios.date: 05/18/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 05WDP7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A13
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd05/18/2013:svnDellInc.:pnInspiron5423:pvrNotSpecified:rvnDellInc.:rn05WDP7:rvrA13:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 5423
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-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.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  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: Fri May  6 09:34:55 2016
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id9020 
   vendor AUO
  xserver.version: 2:1.18.3-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1579182/+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 1562733] Re: apt signature requierements prevent updates from some repositories

[Julian Andres Klode]

Hi Fabio,

in your case, everything seems to be fine signature wise on your system.

Now, the Ign you see are for InRelease files, because APT falls back to
Release files a few lines later.

I don't know why you don't see the docker-engine package. Are you
perhaps running i386? The docker package is only provided for amd64. You
should also see the heroku-toolbelt package.

Finally, your system seems a bit messed up. Please delete the files in
/var/lib/apt/lists/partial, as there seems to be some permission issue.

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

Title:
  apt signature requierements prevent updates from some repositories

Status in apt package in Ubuntu:
  In Progress

Bug description:
  Since xenial updated the requirements for the strength of PGP
  signatures of packages, packages from some repositories are no longer
  updated. Apt-get update reports these errors:

  E: Failed to fetch http://[...]/Release  No Hash entry in Release file 
/var/lib/apt/lists/partial/[...] which is considered strong enough for security 
purposes
  E: Some index files failed to download. They have been ignored, or old ones 
used instead.

  While the motivation for the change is valid, the result is a
  potential security problem, as the new versions of the packages that
  may fix recently discovered vulnerabilities are not automatically
  installed.

  One less important but unfortunate effect is a scary message that is
  displayed to the user, without clear explanation that the problem
  needs to be addressed by the repository owner.

  Related: Bug #1558331

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1562733/+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 1285444] Re: Login Successful, Desktop Never Loads

[Karl William]

Here is mine dconf dump txt. I have exactly this problem after an fresh
install and I could not solve it with reinitialisation om compiz and
unity...

** Attachment added: "dconf-dump.txt"
   
https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1285444/+attachment/4658138/+files/dconf-dump.txt

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

Title:
  Login Successful, Desktop Never Loads

Status in at-spi2-core package in Ubuntu:
  Confirmed

Bug description:
  Here is what I encounter
  1. Boot computer, boot proceeds normally
  2. Reach standard Ubuntu login screen, nothing seems to be amiss
  3. Enter user name and password
  4. Login disappears, just see the pink "Ubuntu 14.04" background

  The desktop never loads, not even after ~30 minutes. The launcher
  never appears, and the Desktop background never changes to the user-
  configured background.

  Other features:
  * Cursor works fine, it can be moved around the screen
  * No error messages pop up
  * ALT+F1 etc. can be used to switch to different TTYs; all files on the 
system appear to be intact
  * Print screen button works (I will upload a screen shot when I get a chance 
to copy it onto a USB drive)
  * Hitting power button pops up a window prompting the user to decide whether 
to shut down
  * CTRL+ALT+DELETE prompts the user to log out
  * Desktop does not load on any user accounts, including the guest account

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1285444/+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 1579393] [NEW] package linux-image-4.4.0-22-generic 4.4.0-22.39 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2

[Mika Mantere]

Public bug reported:

It asked if I want to report a system problem

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-22-generic 4.4.0-22.39
ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  mika   1988 F pulseaudio
 /dev/snd/controlC1:  mika   1988 F pulseaudio
 /dev/snd/controlC2:  mika   1988 F pulseaudio
Date: Sat May  7 04:55:24 2016
Df:
 
Dmesg:
 
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
HibernationDevice: RESUME=UUID=fff79885-820b-4ca1-b9ce-5b1c2354f9d6
InstallationDate: Installed on 2016-04-22 (14 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Dell Inc. XPS 8900
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=bc1727bd-53d7-49f4-938e-02cd919952ef ro quiet splash pcie_aspm=off 
vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc N/A
SourcePackage: initramfs-tools
Title: package linux-image-4.4.0-22-generic 4.4.0-22.39 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/20/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.1.3
dmi.board.name: 0XJ8C4
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr2.1.3:bd01/20/2016:svnDellInc.:pnXPS8900:pvr:rvnDellInc.:rn0XJ8C4:rvrA00:cvnDellInc.:ct3:cvr:
dmi.product.name: XPS 8900
dmi.sys.vendor: Dell Inc.

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package linux-image-4.4.0-22-generic 4.4.0-22.39 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 2

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  It asked if I want to report a system problem

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.39
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mika   1988 F pulseaudio
   /dev/snd/controlC1:  mika   1988 F pulseaudio
   /dev/snd/controlC2:  mika   1988 F pulseaudio
  Date: Sat May  7 04:55:24 2016
  Df:
   
  Dmesg:
   
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  HibernationDevice: RESUME=UUID=fff79885-820b-4ca1-b9ce-5b1c2354f9d6
  InstallationDate: Installed on 2016-04-22 (14 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. XPS 8900
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=bc1727bd-53d7-49f4-938e-02cd919952ef ro quiet splash pcie_aspm=off 
vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: initramfs-tools
  Title: package linux-image-4.4.0-22-generic 4.4.0-22.39 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/20/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.1.3
  dmi.board.name: 0XJ8C4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.1.3:bd01/20/2016:svnDellInc.:pnXPS8900:pvr:rvnDellInc.:rn0XJ8C4:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.name: XPS 8900
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1579393/+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 1579393] Re: package linux-image-4.4.0-22-generic 4.4.0-22.39 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-4.4.0-22-generic 4.4.0-22.39 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 2

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  It asked if I want to report a system problem

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.39
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mika   1988 F pulseaudio
   /dev/snd/controlC1:  mika   1988 F pulseaudio
   /dev/snd/controlC2:  mika   1988 F pulseaudio
  Date: Sat May  7 04:55:24 2016
  Df:
   
  Dmesg:
   
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  HibernationDevice: RESUME=UUID=fff79885-820b-4ca1-b9ce-5b1c2354f9d6
  InstallationDate: Installed on 2016-04-22 (14 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. XPS 8900
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=bc1727bd-53d7-49f4-938e-02cd919952ef ro quiet splash pcie_aspm=off 
vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: initramfs-tools
  Title: package linux-image-4.4.0-22-generic 4.4.0-22.39 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/20/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.1.3
  dmi.board.name: 0XJ8C4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.1.3:bd01/20/2016:svnDellInc.:pnXPS8900:pvr:rvnDellInc.:rn0XJ8C4:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.name: XPS 8900
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1579393/+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 1542691] Re: QSystemTrayIcon doesn't work when several.

[Launchpad Bug Tracker]

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

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New => Confirmed

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

Title:
  QSystemTrayIcon doesn't work when several.

Status in qtbase-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  I've report this bug in Qt forum:
  https://forum.qt.io/topic/62137/qsystemtrayicon-ubuntu-15-10
  But they say to ask you.

  With new version of Ubuntu (with Unity) 15.10 and compiled with Qt 4.8.6, the 
QSystemTrayIcon doesn't work properly.
  We have multi icons depends the service notification. When we trigger .show() 
for service icon, a new main icon appears (with its ContextMenu). And when we 
trigger .hide() the new icon stay.
  So, to test it, I've wrote a litle application with only SystrayIcon. You can 
find Test Project on original thread.
  I've tested it with different version of Qt5. Only 5.5.1 works, but with only 
one icon. When I want to show the second directly, no one appears. If I don't 
show second, the first take its own and the second's context menu. When I 
trigger second.show() nothing happens.
  showMessage() is working well (not msecs) with one or two icons.
  contextmenu only works with one icon shown.
  toolTip doesn't work.
  activated signal isn't triggered.

  I've reinstalled fresh ubuntu 15.10 (in VirtualBox) with its own qt5.4.2.
  Now main icon appears two time (with same context menu).

  What can I do to get icons (or something else) in systray?

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: qtbase5-dev 5.4.2+dfsg-2ubuntu9
  ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Feb  6 19:09:14 2016
  InstallationDate: Installed on 2015-12-26 (42 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: qtbase-opensource-src
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1542691/+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 1542691] Re: QSystemTrayIcon doesn't work when several.

[Felix Moreno]

Hi, that's what happen using retroshare with qt in ubuntu 16.04 and
15.10.

** Attachment added: "Captura de pantalla de 2016-05-04 22-57-17.png"
   
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1542691/+attachment/4658111/+files/Captura%20de%20pantalla%20de%202016-05-04%2022-57-17.png

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

Title:
  QSystemTrayIcon doesn't work when several.

Status in qtbase-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  I've report this bug in Qt forum:
  https://forum.qt.io/topic/62137/qsystemtrayicon-ubuntu-15-10
  But they say to ask you.

  With new version of Ubuntu (with Unity) 15.10 and compiled with Qt 4.8.6, the 
QSystemTrayIcon doesn't work properly.
  We have multi icons depends the service notification. When we trigger .show() 
for service icon, a new main icon appears (with its ContextMenu). And when we 
trigger .hide() the new icon stay.
  So, to test it, I've wrote a litle application with only SystrayIcon. You can 
find Test Project on original thread.
  I've tested it with different version of Qt5. Only 5.5.1 works, but with only 
one icon. When I want to show the second directly, no one appears. If I don't 
show second, the first take its own and the second's context menu. When I 
trigger second.show() nothing happens.
  showMessage() is working well (not msecs) with one or two icons.
  contextmenu only works with one icon shown.
  toolTip doesn't work.
  activated signal isn't triggered.

  I've reinstalled fresh ubuntu 15.10 (in VirtualBox) with its own qt5.4.2.
  Now main icon appears two time (with same context menu).

  What can I do to get icons (or something else) in systray?

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: qtbase5-dev 5.4.2+dfsg-2ubuntu9
  ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Feb  6 19:09:14 2016
  InstallationDate: Installed on 2015-12-26 (42 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: qtbase-opensource-src
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1542691/+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 1579387] Re: Keyboard covers completely important parts of the web pages

[GTriderXC]

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

** Changed in: ubuntu-keyboard (Ubuntu)
   Status: New => Invalid

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

Title:
  Keyboard covers completely important parts of the web pages

Status in ubuntu-keyboard package in Ubuntu:
  Invalid
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  As You can see in the photo I'm unable to log in into my Launchpad
  account: I can't provide a password. In this case from my first
  picture, the browser allows me to scroll the page down bug the browser
  "sees" the end of the page as the lower end (bottom) of a screen.
  Where the the end of a screen for a browser should be the upper edge
  of the keyboard. I'm not sure whether it is a browser or a keyboard
  problem.

  To be able to log in I have to close the keyboard, place the cursor in
  a Password , then the keyboard opens again and I write blind the
  password, somewhere under the keyboard.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1579387/+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 1562733] Re: apt signature requierements prevent updates from some repositories

[Fabio C. Barrionuevo]

Julian, please see:
https://asciinema.org/a/1xwbdc2r2qcdbby1qpucmztvb

I do not know, but these problems with apt-get are almost making me go
back to 14.04

other related problems:
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1570141

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

Title:
  apt signature requierements prevent updates from some repositories

Status in apt package in Ubuntu:
  In Progress

Bug description:
  Since xenial updated the requirements for the strength of PGP
  signatures of packages, packages from some repositories are no longer
  updated. Apt-get update reports these errors:

  E: Failed to fetch http://[...]/Release  No Hash entry in Release file 
/var/lib/apt/lists/partial/[...] which is considered strong enough for security 
purposes
  E: Some index files failed to download. They have been ignored, or old ones 
used instead.

  While the motivation for the change is valid, the result is a
  potential security problem, as the new versions of the packages that
  may fix recently discovered vulnerabilities are not automatically
  installed.

  One less important but unfortunate effect is a scary message that is
  displayed to the user, without clear explanation that the problem
  needs to be addressed by the repository owner.

  Related: Bug #1558331

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1562733/+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 1545118] Re: [AdaptivePageLayout] can't easily grab scrollbar if dual column

[Andrea Bernabei]

because Dekko is not currently using AdaptivePageLayout

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

Title:
  [AdaptivePageLayout] can't easily grab scrollbar if dual column

Status in Canonical System Image:
  In Progress
Status in Ubuntu UX:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu RTM:
  Confirmed

Bug description:
  If you have an app that uses AdaptivePageLayout and supports 2
  columns, if there is a scrollbar in the first column, it's very
  difficult to grab it with your mouse because when you get close to it,
  you get the horizontal arrows showing to allow resizing of the panels
  in the multi-column layout.

  You can try this with messaging-app in silo 30 (soon to land)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1545118/+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 1579387] [NEW] Keyboard covers completely important parts of the web pages

[GTriderXC]

Public bug reported:

As You can see in the photo I'm unable to log in into my Launchpad
account: I can't provide a password. In this case from my first picture,
the browser allows me to scroll the page down bug the browser "sees" the
end of the page as the lower end (bottom) of a screen. Where the the end
of a screen for a browser should be the upper edge of the keyboard. I'm
not sure whether it is a browser or a keyboard problem.

To be able to log in I have to close the keyboard, place the cursor in a
Password , then the keyboard opens again and I write blind the
password, somewhere under the keyboard.

** Affects: ubuntu-keyboard (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: webbrowser-app (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Attachment added: "IMG_20160503_112335.jpg"
   
https://bugs.launchpad.net/bugs/1579387/+attachment/4658083/+files/IMG_20160503_112335.jpg

** Also affects: webbrowser-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 ubuntu-keyboard in Ubuntu.
https://bugs.launchpad.net/bugs/1579387

Title:
  Keyboard covers completely important parts of the web pages

Status in ubuntu-keyboard package in Ubuntu:
  Invalid
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  As You can see in the photo I'm unable to log in into my Launchpad
  account: I can't provide a password. In this case from my first
  picture, the browser allows me to scroll the page down bug the browser
  "sees" the end of the page as the lower end (bottom) of a screen.
  Where the the end of a screen for a browser should be the upper edge
  of the keyboard. I'm not sure whether it is a browser or a keyboard
  problem.

  To be able to log in I have to close the keyboard, place the cursor in
  a Password , then the keyboard opens again and I write blind the
  password, somewhere under the keyboard.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1579387/+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 1545118] Re: [AdaptivePageLayout] can't easily grab scrollbar if dual column

[Kugi Eusebio]

It seems that Dekko is not affected by this bug.

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

Title:
  [AdaptivePageLayout] can't easily grab scrollbar if dual column

Status in Canonical System Image:
  In Progress
Status in Ubuntu UX:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu RTM:
  Confirmed

Bug description:
  If you have an app that uses AdaptivePageLayout and supports 2
  columns, if there is a scrollbar in the first column, it's very
  difficult to grab it with your mouse because when you get close to it,
  you get the horizontal arrows showing to allow resizing of the panels
  in the multi-column layout.

  You can try this with messaging-app in silo 30 (soon to land)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1545118/+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 1534682] Re: Not requesting desktop content when connected to monitor

[Olivier Tilloy]

Any update on this?

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

Title:
  Not requesting desktop content when connected to monitor

Status in Canonical System Image:
  In Progress
Status in Canonical Pocket Desktop:
  In Progress
Status in qtubuntu package in Ubuntu:
  In Progress
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  The ua string is supposed to change based on screensize and other
  hueristics, but this is not happening. Getting mobile ua string
  always, even when connected to monitor via slimport

  using this build:
  (r112) ubuntu-device-flash touch --channel=ubuntu-touch/rc-proposed/ubuntu-pd

  Not seeing any messages in the browser log when I plug/unplug the
  monitor

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1534682/+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 1390728] Re: Selecting "5" using the long press on the "T"

[GTriderXC]

There is a very same situation that I described by another bug with
Polish Keyboard here:

https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1468799

in #2

in "short":

"What drives me mad when I write on 4.5 with my touchpen is "Ó" and "Ę" as well 
as "ö,ä,ü " in German. There is the same issue under Android where You want to 
write "Ę" but the very first suggestion you get on the list is "3".
My proposition would be to modify the keyboard so that we get the letters we 
want as fast as possible: If I want to write "Ó" I press and hold the O but the 
first default answer is Ó, not 9!
When You write a text it is more probable that You need letters, not digits. 
And when You need digits then You mostly need more of them so You switch to 
numerical mode. Today when I write something on my 4.5, I have to fight with my 
touchpen for every "Ó" I need by moving the rubber-ended touchpen on a glass 
screen. I can do it for a "9" but I BEG YOU not for every "Ó"."

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

Title:
  Selecting "5" using the long press on the "T"

Status in Ubuntu Mobile Phone:
  New
Status in ubuntu-keyboard package in Ubuntu:
  Confirmed

Bug description:
  This bug relates to the Ubuntu Phone key pad:
  When you long press "T" or "t" you get the option of "5" or "Þ"
  I would expect it to be easier to get a result of "5" rather than the other 
character, but I find that I have to be really careful to ensure that I get a 
"5".

  I don't know the importance of the other character ("Þ") but it seems
  that it is getting equal importance to "5" based on its position.

  There are only two long press characters for "t" and perhaps the "5"
  can be centrally positioned with the "Þ" offset to the left or right.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu+mobile+phone/+bug/1390728/+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 1409606] Re: Default keyboard colour scheme slows users down

[GTriderXC]

i++ for Jouni Helminen (jounihelminen) at #2

I think exactly the same

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

Title:
  Default keyboard colour scheme slows users down

Status in ubuntu-keyboard:
  Confirmed
Status in Ubuntu UX:
  Opinion
Status in ubuntu-keyboard package in Ubuntu:
  Confirmed

Bug description:
  I feel the default keyboard colour scheme is slowing me down.

  It's made up of grey and white. This does not provide adequate visual
  contrast to be able to type as quickly as I can on other devices. I
  feel a slight mental pause as I have to expend slightly more effort to
  distinguish the similarly coloured elements in the keyboard.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-keyboard/+bug/1409606/+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 1574732] Re: Regression: Kernel Update in 16.04 from last days renders nvidia driver unusable

[Johnny Arthur]

First of all, thank you for your fast response! It is amazing!

Yes, there was a question about secure boot, but - just as other users
who experienced the same problem - I was not aware about the significant
change in the handling of secure boot and the consequences thereof.
Formerly Ubuntu worked with secure boot enabled, hence I saw no reason
to disable it. There was some explanation about 3rd-Party-modules on
that dialog, yes, but because I do not use any other sources other than
those provided by Ubuntu, I didn't feel concerned. Maybe the German
translation is even more misleading (however I do not recall the exact
wording of the dialog on upgrade), because the section in the control
panel is called "Zusätzlich Treiber" and it mentions "Proprietäre
Treiber" in the text in the control panel, but not 3rd Party Software,
what I think was the term used on the upgrade dialog (though I am not
quite sure about that). And since everything worked when I selected the
older Kernel 4.2.0-35 I did not think about this at all any longer :-(
and it took quite a while to figure out the reason of the problem...

If those modules get signed automatically in the future, this will help
a lot... Maybe meanwhile the Dialog on Upgrade could be made a little
bit more clear about the problems and that those using nvidia drivers
will not be able to log in after upgrade?

I uninstalled nvidia, booted with secure boot enabled and installed
nvidia again (using the control panel -> "Zusätzliche Treiber" =
"additional drivers"), but there was no message about secure boot there.
After reboot I couldn't log in again as expected.

For me it is ok now that I know the reason. But I think a lot of people
might run into severe troubles...

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

Title:
  Regression: Kernel Update in 16.04 from last days renders nvidia
  driver unusable

Status in shim:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I am running Ubuntu 16.04 since at least four months, always with the
  nvidia proprietary drivers (installed from the repository). I used
  nvidia-361 for a while with no issues (and i need it for steam
  gaming). However, an update installed on my machine yesterday breaks
  the nvidia drivers. I tried purging the driver, rebooting and
  reinstalling and i tried a newer version for the ubuntu-drivers ppa.
  Nothing helps: With the nvidia driver installed, i get a low-
  resolution login screen, but cannot login due to missing 3d
  acceleration. Running on nouveau works fine.

  This seems very strange to since everything worked until this
  afternoon. Yesterday, i was happily playing games on steam, installed
  some updates and now, my graphics are broken.


  
  $ lspci | grep NVIDIA
  01:00.0 VGA compatible controller: NVIDIA Corporation GM107 [GeForce GTX 750] 
(rev a2)
  01:00.1 Audio device: NVIDIA Corporation Device 0fbc (rev a1)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  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: Mon Apr 25 17:45:12 2016
  DistUpgraded: 2016-03-11 21:34:38,175 DEBUG enabling apt cron job
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-21-generic, x86_64: installed
   virtualbox, 5.0.18, 4.4.0-18-generic, x86_64: installed
   virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GM107 [GeForce GTX 750] [10de:1381] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Palit Microsystems Inc. GM107 [GeForce GTX 750] [1569:1381]
  InstallationDate: Installed on 2016-01-05 (110 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=ed669b2d-c3af-4570-9eb7-2978557208ae ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to xenial on 2016-03-11 (44 days ago)
  dmi.bios.date: 05/18/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.30
  dmi.board.name: H97 Performance
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 

[Touch-packages] [Bug 802998] Re: [K42Jr, Realtek ALC269VB, Speaker, Internal] No sound at all

[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/802998

Title:
  [K42Jr, Realtek ALC269VB, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 11.04 - the Natty Narwhal - released in April 2011 and
  supported until October 2012.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: alsa-base 1.0.24+dfsg-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2
  Uname: Linux 2.6.38-8-generic-pae i686
  NonfreeKernelModules: fglrx
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC269VB Analog [ALC269VB Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yeowherchyn   1415 F pulseaudio
   /dev/snd/pcmC0D0p:   yeowherchyn   1415 F...m pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf7a0 irq 46'
 Mixer name : 'Realtek ALC269VB'
 Components : 'HDA:10ec0269,10431313,00100100'
 Controls  : 12
 Simple ctrls  : 7
  Card1.Amixer.info:
   Card hw:1 'Generic'/'HD-Audio Generic at 0xf004 irq 47'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100200'
 Controls  : 4
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Date: Tue Jun 28 21:26:31 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Internal Audio - HDA Intel
  Symptom_DevicesInUse:
   1415  2059  2278  1415gdm   F pulseaudio
yeowherchyn  F alsamixer
   /dev/snd/pcmC0D0p:   yeowherchyn  F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [K42Jr, Realtek ALC269VB, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/02/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 504
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K42Jr
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: 0x
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr504:bd09/02/2010:svnASUSTeKComputerInc.:pnK42Jr:pvr1.0:rvnASUSTeKComputerInc.:rnK42Jr:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: K42Jr
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/802998/+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 1377096] Re: [OSK] Ubuntu Touch should allow alternative keyboard layouts

[GTriderXC]

I reported a quite similar issue a few days ago here:

https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1573990

Having an old-modern "1-9" mobile phone keyboard would be also a great
idea. Perhaps we would be able again to write without looking on the
screen as I described.

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

Title:
  [OSK] Ubuntu Touch should allow alternative keyboard layouts

Status in Ubuntu UX:
  Triaged
Status in ubuntu-keyboard package in Ubuntu:
  Triaged

Bug description:
  It would be nice if alternative keyboard layouts were available for
  Ubuntu Touch.

  On Android devices I use the Hacker's Keyboard
  https://code.google.com/p/hackerskeyboard/ from F-Droid
  
https://f-droid.org/repository/browse/?fdfilter=org.pocketworkstation.pckeyboard=org.pocketworkstation.pckeyboard
  as this allows customisation and easy access to keys such as Ctrl,
  Esc, !, : and - and these are keys that take a lot of key presses with
  the current Ubuntu touch keyboard (I use vim). In addition key
  combinations such as Ctrl-n and Ctrl-p (next and previous channel in
  IRSSI) are not possible with the current Ubuntu Touch keyboard.

  Having said the above the gestures, double tap for tab, swipe up, down
  , left and right for the arrow keys is great and I now find myself
  trying to use these gestures on Android devices...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1377096/+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 1377096] Re: [OSK] Ubuntu Touch should allow alternative keyboard layouts

[GTriderXC]

I support the idea as we have a "fight" about the topic in polish layout:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1468799

As You see in the comments on different devices there are different
problems. In the bug I pasted You see as a theoretically great solution
for a tablet is a bad one for an Aquaris 4.5 where the screen is not as
big as in M10.

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

Title:
  [OSK] Ubuntu Touch should allow alternative keyboard layouts

Status in Ubuntu UX:
  Triaged
Status in ubuntu-keyboard package in Ubuntu:
  Triaged

Bug description:
  It would be nice if alternative keyboard layouts were available for
  Ubuntu Touch.

  On Android devices I use the Hacker's Keyboard
  https://code.google.com/p/hackerskeyboard/ from F-Droid
  
https://f-droid.org/repository/browse/?fdfilter=org.pocketworkstation.pckeyboard=org.pocketworkstation.pckeyboard
  as this allows customisation and easy access to keys such as Ctrl,
  Esc, !, : and - and these are keys that take a lot of key presses with
  the current Ubuntu touch keyboard (I use vim). In addition key
  combinations such as Ctrl-n and Ctrl-p (next and previous channel in
  IRSSI) are not possible with the current Ubuntu Touch keyboard.

  Having said the above the gestures, double tap for tab, swipe up, down
  , left and right for the arrow keys is great and I now find myself
  trying to use these gestures on Android devices...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1377096/+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 1468799] Re: Too many keys in Polish keyboard

[GTriderXC]

I will support Krzysztof in that matter. I also like that few Polish
extra keys more. I like them even more on my M10. BUT(!) Bartosz is
right about the small screen. I have both bqs: 4.5 and M10. As I like
the idea on M10, on 4.5 I write with a touchpen. For small screens this
solution is not the best one.

Possible solution:
I'd find it cool to be able to choose the keyboards layouts, cause as I said 
the by Bartosz criticized solution DOES the job on M10 perfectly!
The only problem I want to report as a bug is "Ź" letter not under "Alt+X" but 
under "Alt+Z". As the X letter is free on a keyboard, we could use it for "Ź" 
and Z for "Ż".

What drives me mad when I write on 4.5 with my touchpen is "Ó" and "Ę" as well 
as "ö,ä,ü " in German. There is the same issue under Android where You want to 
write "Ę" but the very first suggestion you get on the list is "3".
My proposition would be to modify the keyboard so that we get the letters we 
want as fast as possible: If I want to write "Ó" I press and hold the O but the 
first default answer is Ó, not 9!
When You write a text it is more probable that You need letters, not digits. 
And when You need digits then You mostly need more of them so You switch to 
numerical mode. Today when I write something on my 4.5, I have to fight with my 
touchpen for every "Ó" I need by moving the rubber-ended touchpen on a glass 
screen. I can do it for a "9" but I BEG YOU not for every "Ó".

What can be done so that everyone is satysfied:
1. Ź under X
2. Ó default after long pressing O and 9 or ö on as a choice to swipe.
3. As You see I support both ideas present and proposed by Bartosz. Krzysztof 
has an 5 inch screen in his MX4. In Aquaris typing without a touchpen is not 
pleasant experience. On the other hand having a standard "Polish Programmer" 
keyboard on a tablet is a pity. The buttons of the tablet as so HUGE that all 
Polish diactric signs could be present as a extra signs.
4. Do not copy Android solutions: see the weaknesses and improve them in Ubuntu 
:-)

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

Title:
  Too many keys in Polish keyboard

Status in ubuntu-keyboard package in Ubuntu:
  In Progress

Bug description:
  For Polish keyboard, to standard QWERTY keyboard the new column with
  Polish letters was added.

  It is not optimal because:
  1. Adding additional key column, takes space, and for small devices (BQ E4.5) 
it is hard to use
  2. For Polish language there are 9 diactric signs, (ą, ć, ę, ł, ń, ó, ś, ź, 
ż) but only 3 is available as separate keys
  3. In Poland most common used is "Polish Programmer" keyboard (it is also 
used on Android phone). The diactric sign are available with SHIFT modifier 
(Example: SHIFT+a = ą, SHIFT+c = ć etc.)

  Proposal:
  To improve UX of Polish keyboard, I would like propose to remove Polish keys 
and use "Polish Programmer" style (with SHIFT modifier). With that solution it 
will be much easier typying on Polish keyboard.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1468799/+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 1579379] Re: package systemd-sysv 229-4ubuntu4 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv

[Apport retracing service]

** Tags removed: need-duplicate-check

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

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

Status in systemd package in Ubuntu:
  New

Bug description:
  Upgrading from 15.10 to 16.04, using the Software Updater.

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

  $ apt-cache policy systemd-sysv
  systemd-sysv:
Installed: 229-4ubuntu4
Candidate: 229-4ubuntu4
Version table:
   *** 229-4ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  I expected the upgrade to complete without errors.

  I received errors.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd-sysv 229-4ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat May  7 08:40:54 2016
  ErrorMessage: pre-dependency problem - not installing systemd-sysv
  InstallationDate: Installed on 2015-07-16 (295 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: systemd
  Title: package systemd-sysv 229-4ubuntu4 failed to install/upgrade: 
pre-dependency problem - not installing systemd-sysv
  UpgradeStatus: Upgraded to xenial on 2016-05-07 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1579379/+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 1527843] Re: systemd-logind failed to enable subscription: launch helper exited with unknown return code 1

[Eric Bruce]

Found your post after I had the exact same problem after installing some
packages, in my case looks like caused by blueman2.0.4-1ubuntu2

You may have a different cause but symptoms looks about the same. I just
got my system back up by running the following from the cmd line once
you log in to the CLI:


sudo start lightdm

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

Title:
  systemd-logind failed to enable subscription: launch helper exited
  with unknown return code 1

Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Wily:
  Expired

Bug description:
  Started my machine succesfully at night and the next morning the screen is 
blank/black and no GUI available.
  Switching to TTY1 i got after the login these messages:

  [31989] systemd-logind[4272]: Failed to enable subscription: Launch helper 
exited with unknown return code 1
  [31989] systemd-logind[4272]: Failed to fully start up daemon: Input/output 
error

  The much bigger problem is:
  PC does *not* start with normal boot options, i have to choose manually the 
upstart option in GRUB2.
  #1527806

  It is a fresh installed Xubuntu 15.10, all packages installed via
  Synaptic or CLI.

  
  Xubuntu 15.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1527843/+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 1579379] [NEW] package systemd-sysv 229-4ubuntu4 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv

[Gary Nelson]

Public bug reported:

Upgrading from 15.10 to 16.04, using the Software Updater.

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

$ apt-cache policy systemd-sysv
systemd-sysv:
  Installed: 229-4ubuntu4
  Candidate: 229-4ubuntu4
  Version table:
 *** 229-4ubuntu4 500
500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status

I expected the upgrade to complete without errors.

I received errors.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: systemd-sysv 229-4ubuntu4
ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Sat May  7 08:40:54 2016
ErrorMessage: pre-dependency problem - not installing systemd-sysv
InstallationDate: Installed on 2015-07-16 (295 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt  1.2.10ubuntu1
SourcePackage: systemd
Title: package systemd-sysv 229-4ubuntu4 failed to install/upgrade: 
pre-dependency problem - not installing systemd-sysv
UpgradeStatus: Upgraded to xenial on 2016-05-07 (0 days ago)

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


** Tags: amd64 apport-package xenial

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

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

Status in systemd package in Ubuntu:
  New

Bug description:
  Upgrading from 15.10 to 16.04, using the Software Updater.

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

  $ apt-cache policy systemd-sysv
  systemd-sysv:
Installed: 229-4ubuntu4
Candidate: 229-4ubuntu4
Version table:
   *** 229-4ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  I expected the upgrade to complete without errors.

  I received errors.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd-sysv 229-4ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat May  7 08:40:54 2016
  ErrorMessage: pre-dependency problem - not installing systemd-sysv
  InstallationDate: Installed on 2015-07-16 (295 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: systemd
  Title: package systemd-sysv 229-4ubuntu4 failed to install/upgrade: 
pre-dependency problem - not installing systemd-sysv
  UpgradeStatus: Upgraded to xenial on 2016-05-07 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1579379/+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 1579380] [NEW] package initramfs-tools 0.122ubuntu8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[tonyscam]

Public bug reported:

Received this error message during the 15.10 to 16.04 upgrade process.
Subsequent attempts to install this package have failed.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: initramfs-tools 0.122ubuntu8
ProcVersionSignature: Ubuntu 3.18.0-25.26-rpi2 3.18.17
Uname: Linux 3.18.0-25-rpi2 armv7l
ApportVersion: 2.20.1-0ubuntu2
Architecture: armhf
Date: Sat May  7 09:27:15 2016
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt  1.2.10ubuntu1
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.122ubuntu8 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2016-05-07 (0 days ago)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package armhf xenial

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

Title:
  package initramfs-tools 0.122ubuntu8 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Received this error message during the 15.10 to 16.04 upgrade process.
  Subsequent attempts to install this package have failed.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8
  ProcVersionSignature: Ubuntu 3.18.0-25.26-rpi2 3.18.17
  Uname: Linux 3.18.0-25-rpi2 armv7l
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: armhf
  Date: Sat May  7 09:27:15 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.122ubuntu8 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-05-07 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1579380/+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 1579375] Re: package systemd-sysv 229-4ubuntu4 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv

[Apport retracing service]

** Tags removed: need-duplicate-check

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

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

Status in systemd package in Ubuntu:
  New

Bug description:
  no clue how to provide further details

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd-sysv 229-4ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic i686
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  Date: Sat May  7 15:55:05 2016
  ErrorMessage: pre-dependency problem - not installing systemd-sysv
  InstallationDate: Installed on 2015-10-31 (189 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: systemd
  Title: package systemd-sysv 229-4ubuntu4 failed to install/upgrade: 
pre-dependency problem - not installing systemd-sysv
  UpgradeStatus: Upgraded to xenial on 2016-05-07 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1579375/+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 1579375] [NEW] package systemd-sysv 229-4ubuntu4 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv

[miobrad]

Public bug reported:

no clue how to provide further details

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: systemd-sysv 229-4ubuntu4
ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
Uname: Linux 4.4.0-22-generic i686
ApportVersion: 2.20.1-0ubuntu2
Architecture: i386
Date: Sat May  7 15:55:05 2016
ErrorMessage: pre-dependency problem - not installing systemd-sysv
InstallationDate: Installed on 2015-10-31 (189 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt  1.2.10ubuntu1
SourcePackage: systemd
Title: package systemd-sysv 229-4ubuntu4 failed to install/upgrade: 
pre-dependency problem - not installing systemd-sysv
UpgradeStatus: Upgraded to xenial on 2016-05-07 (0 days ago)

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


** Tags: apport-package i386 xenial

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

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

Status in systemd package in Ubuntu:
  New

Bug description:
  no clue how to provide further details

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd-sysv 229-4ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic i686
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  Date: Sat May  7 15:55:05 2016
  ErrorMessage: pre-dependency problem - not installing systemd-sysv
  InstallationDate: Installed on 2015-10-31 (189 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: systemd
  Title: package systemd-sysv 229-4ubuntu4 failed to install/upgrade: 
pre-dependency problem - not installing systemd-sysv
  UpgradeStatus: Upgraded to xenial on 2016-05-07 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1579375/+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 1577760] Re: Screen Display 'Apply' fails

[Launchpad Bug Tracker]

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

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

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

Title:
  Screen Display 'Apply' fails

Status in upower package in Ubuntu:
  New

Bug description:
  Since upgrading to 16.04, when I click on the 'Apply' button of the
  'Screen Display' utility (without setting anything), I get an error
  dialog:

  "Failed to apply configuration: %s
  GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface 
'org.gnome.SettingsDaemon.XRANDR_2' on object at path 
/org/gnome/SettingsDaemon/XRANDR"

  What I expect to be able to configure multiple monitors - though it
  fails even when I have none connected.

  It is a Lenovo X250 with a docking station (though it doesn't make any
  difference if the docking station is used or not).

  WORKAROUND: sudo ln -s /usr/lib/x86_64-linux-gnu/libusbmuxd.so.4.0.0
  /usr/lib/x86_64-linux-gnu/libusbmuxd.so.2

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue May  3 13:20:37 2016
  DistUpgraded: 2016-04-22 10:05:12,580 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
     Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:2226]
  InstallationDate: Installed on 2015-05-20 (348 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20CM001QUK
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (11 days ago)
  dmi.bios.date: 04/06/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N10ET33W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CM001QUK
  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:bvrN10ET33W(1.12):bd04/06/2015:svnLENOVO:pn20CM001QUK:pvrThinkPadX250:rvnLENOVO:rn20CM001QUK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20CM001QUK
  dmi.product.version: ThinkPad X250
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-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.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  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 May  3 12:33:42 2016
  xserver.configfile: default
  xserver.errors:
   intel(0): page flipping failed, on CRTC:25 (pipe=1), disabling synchronous 
page flips
   intel(0): failed to set mode: No such file or directory [2]
   intel(0): Failed to restore display configuration
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1079
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1577760/+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 1577760] Re: Screen Display 'Apply' fails

[Christopher M. Penalver]

** Package changed: xorg (Ubuntu) => upower (Ubuntu)

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

Title:
  Screen Display 'Apply' fails

Status in upower package in Ubuntu:
  New

Bug description:
  Since upgrading to 16.04, when I click on the 'Apply' button of the
  'Screen Display' utility (without setting anything), I get an error
  dialog:

  "Failed to apply configuration: %s
  GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface 
'org.gnome.SettingsDaemon.XRANDR_2' on object at path 
/org/gnome/SettingsDaemon/XRANDR"

  What I expect to be able to configure multiple monitors - though it
  fails even when I have none connected.

  It is a Lenovo X250 with a docking station (though it doesn't make any
  difference if the docking station is used or not).

  WORKAROUND: sudo ln -s /usr/lib/x86_64-linux-gnu/libusbmuxd.so.4.0.0
  /usr/lib/x86_64-linux-gnu/libusbmuxd.so.2

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue May  3 13:20:37 2016
  DistUpgraded: 2016-04-22 10:05:12,580 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
     Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:2226]
  InstallationDate: Installed on 2015-05-20 (348 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20CM001QUK
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (11 days ago)
  dmi.bios.date: 04/06/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N10ET33W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CM001QUK
  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:bvrN10ET33W(1.12):bd04/06/2015:svnLENOVO:pn20CM001QUK:pvrThinkPadX250:rvnLENOVO:rn20CM001QUK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20CM001QUK
  dmi.product.version: ThinkPad X250
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-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.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  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 May  3 12:33:42 2016
  xserver.configfile: default
  xserver.errors:
   intel(0): page flipping failed, on CRTC:25 (pipe=1), disabling synchronous 
page flips
   intel(0): failed to set mode: No such file or directory [2]
   intel(0): Failed to restore display configuration
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1079
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1577760/+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 1577760] Re: Screen Display 'Apply' fails

[Christopher M. Penalver]

Max Waterman, for now, let this be recast to the upower package, given
this issue has been root caused to it pointing to the wrong file
version.

** Changed in: xorg (Ubuntu)
   Importance: Low => Medium

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

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

Title:
  Screen Display 'Apply' fails

Status in upower package in Ubuntu:
  New

Bug description:
  Since upgrading to 16.04, when I click on the 'Apply' button of the
  'Screen Display' utility (without setting anything), I get an error
  dialog:

  "Failed to apply configuration: %s
  GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface 
'org.gnome.SettingsDaemon.XRANDR_2' on object at path 
/org/gnome/SettingsDaemon/XRANDR"

  What I expect to be able to configure multiple monitors - though it
  fails even when I have none connected.

  It is a Lenovo X250 with a docking station (though it doesn't make any
  difference if the docking station is used or not).

  WORKAROUND: sudo ln -s /usr/lib/x86_64-linux-gnu/libusbmuxd.so.4.0.0
  /usr/lib/x86_64-linux-gnu/libusbmuxd.so.2

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue May  3 13:20:37 2016
  DistUpgraded: 2016-04-22 10:05:12,580 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
     Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:2226]
  InstallationDate: Installed on 2015-05-20 (348 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20CM001QUK
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (11 days ago)
  dmi.bios.date: 04/06/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N10ET33W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CM001QUK
  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:bvrN10ET33W(1.12):bd04/06/2015:svnLENOVO:pn20CM001QUK:pvrThinkPadX250:rvnLENOVO:rn20CM001QUK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20CM001QUK
  dmi.product.version: ThinkPad X250
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-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.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  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 May  3 12:33:42 2016
  xserver.configfile: default
  xserver.errors:
   intel(0): page flipping failed, on CRTC:25 (pipe=1), disabling synchronous 
page flips
   intel(0): failed to set mode: No such file or directory [2]
   intel(0): Failed to restore display configuration
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1079
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1577760/+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 1571686] Re: "Ask me each time" for SMS does not work

[Pat McGowan]

** Changed in: canonical-devices-system-image
   Status: In Progress => Fix Committed

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

Title:
  "Ask me each time" for SMS does not work

Status in Canonical System Image:
  Fix Committed
Status in messaging-app package in Ubuntu:
  Fix Released

Bug description:
  BQ Aquaris E4.5 with OTA 10.1
  Settings "Ask me each time" in "For messages, use" in "Cellular" in "Settings"

  I am using 2 SIM cards and since the beginning of my usage (started
  with release21 this settings was working as expected -> when I wanted
  to send SMS and did not select SIM card by myself (so no SIM card was
  highlighted in the Messages app), I was asked to select one.

  Since some time (OTA-9?) there is always (first one) SIM card selected
  despite the above mentioned settings. And, by whatever reason
  sometimes the SMS is send from other then selected SIM card. Because
  it is now happening much more often and I see that "nice" info: "You
  switched to XXX XX" (PS: no I did not!), it becomes really annoying (I
  have one SIM card in roaming mode) and people are receiving my
  messages from different number and therefore I decided to open this
  bug report.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1571686/+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 1577760] Re: Screen Display 'Apply' fails

[Christopher M. Penalver]

** Tags added: regression-release

** Description changed:

- When I click on the 'Apply' button of the 'Screen Display' utility
- (without setting anything), I get an error dialog :
+ Since upgrading to 16.04, when I click on the 'Apply' button of the
+ 'Screen Display' utility (without setting anything), I get an error
+ dialog:
  
  "Failed to apply configuration: %s
  GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface 
'org.gnome.SettingsDaemon.XRANDR_2' on object at path 
/org/gnome/SettingsDaemon/XRANDR"
  
- 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System
- -> About Ubuntu
- 
- Description:  Ubuntu 16.04 LTS
- Release:  16.04
- 
- 2) The version of the package you are using, via 'apt-cache policy
- pkgname' or by checking in Software Center
- 
- It is the 'Screen Display' utility on the 'System Settings' tool - I
- don't know how to find out what binary that is or the package it is in.
- 
- 3) What you expected to happen
- 
- I expect to be able to configure multiple monitors - though it fails
- even when I have none connected.
- 
- 4) What happened instead
- 
- I get the above error message any time I press 'Apply'.
- 
- I've had this ever since upgrading to 16.04.
- 
- In case this is useful :
- 
- [~]$ lspci
- 00:00.0 Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI (rev 09)
- 00:02.0 VGA compatible controller: Intel Corporation Broadwell-U Integrated 
Graphics (rev 09)
- 00:03.0 Audio device: Intel Corporation Broadwell-U Audio Controller (rev 09)
- 00:14.0 USB controller: Intel Corporation Wildcat Point-LP USB xHCI 
Controller (rev 03)
- 00:16.0 Communication controller: Intel Corporation Wildcat Point-LP MEI 
Controller #1 (rev 03)
- 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection (3) 
I218-LM (rev 03)
- 00:1b.0 Audio device: Intel Corporation Wildcat Point-LP High Definition 
Audio Controller (rev 03)
- 00:1c.0 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port 
#6 (rev e3)
- 00:1c.1 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port 
#3 (rev e3)
- 00:1d.0 USB controller: Intel Corporation Wildcat Point-LP USB EHCI 
Controller (rev 03)
- 00:1f.0 ISA bridge: Intel Corporation Wildcat Point-LP LPC Controller (rev 03)
- 00:1f.2 SATA controller: Intel Corporation Wildcat Point-LP SATA Controller 
[AHCI Mode] (rev 03)
- 00:1f.3 SMBus: Intel Corporation Wildcat Point-LP SMBus Controller (rev 03)
- 00:1f.6 Signal processing controller: Intel Corporation Wildcat Point-LP 
Thermal Management Controller (rev 03)
- 02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5227 PCI 
Express Card Reader (rev 01)
- 03:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
- [~]$ 
+ What I expect to be able to configure multiple monitors - though it
+ fails even when I have none connected.
  
  It is a Lenovo X250 with a docking station (though it doesn't make any
  difference if the docking station is used or not).
  
- IMO, this isn't related to graphics specifically...more to do with some
- DBus service...
+ WORKAROUND: sudo ln -s /usr/lib/x86_64-linux-gnu/libusbmuxd.so.4.0.0
+ /usr/lib/x86_64-linux-gnu/libusbmuxd.so.2
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
-  
+ 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue May  3 13:20:37 2016
  DistUpgraded: 2016-04-22 10:05:12,580 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
-  Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
-Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:2226]
+  Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
+    Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:2226]
  InstallationDate: Installed on 2015-05-20 (348 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20CM001QUK
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (11 days ago)
  dmi.bios.date: 04/06/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N10ET33W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CM001QUK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
 

Re: [Touch-packages] [Bug 1577051] Re: aa-logprof fails with unknown mode "reweive"

[lysdexia]

But . . . But . . . I've worked years on this collection. Most of my debug
logs are mint-in-box! Some are from Slackware 3.1!
On May 6, 2016 5:06 PM, "Christian Boltz" <1577...@bugs.launchpad.net>
wrote:

> ** Changed in: apparmor
>Status: New => Confirmed
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1577051
>
> Title:
>   aa-logprof fails with unknown mode "reweive"
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/apparmor/+bug/1577051/+subscriptions
>

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

Title:
  aa-logprof fails with unknown mode "reweive"

Status in AppArmor:
  Confirmed
Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04.

  Profiling apache tomcat.
   
  1) aa-genprof on the catalina.sh script that is used to start and stop 
tomcat. 
  2) Start and stop tomcat. 
  3) Scan and save the profile.
  4) aa-complain on the tomcat profile
  5) Start tomcat again and this time also send a http request to tomcat.
  6) Run aa-logprof which fails with this message

  Reading log entries from /var/log/syslog.
  Updating AppArmor profiles in /etc/apparmor.d.
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 402, in 
read_log
  self.add_event_to_tree(event)
File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 206, in 
add_event_to_tree
  e = self.parse_event_for_tree(e)
File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 303, in 
parse_event_for_tree
  raise AppArmorException(_('Log contains unknown mode %s') % rmask)
  apparmor.common.AppArmorException: 'Log contains unknown mode reweive'

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File "/usr/sbin/aa-logprof", line 50, in 
  apparmor.do_logprof_pass(logmark)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2189, in 
do_logprof_pass
  log = log_reader.read_log(logmark)
File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 407, in 
read_log
  raise AppArmorBug(ex_msg)  # py3-only: from None
  apparmor.common.AppArmorBug: Log contains unknown mode reweive

  This error was caused by the log line:
  Apr 30 21:53:05 nova kernel: [24668.960760] audit: type=1400 
audit(1462045985.636:2154): apparmor="ALLOWED" operation="file_perm" 
profile="/usr/local/apache-tomcat-8.0.33/bin/catalina.sh///usr/local/jdk1.8.0_92/bin/java"
 pid=12529 comm="java" laddr=:::127.0.0.1 lport=8080 faddr=:::127.0.0.1 
fport=52308 family="inet6" sock_type="stream" protocol=6 
requested_mask="receive" denied_mask="receive"

  
  An unexpected error occoured!

  For details, see /tmp/apparmor-bugreport-wj6gamog.txt
  Please consider reporting a bug at https://bugs.launchpad.net/apparmor/
  and attach this file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1577051/+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 1500242] Re: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5

[Mike Jelfs]

Meizu MX4
OTA 10.1

This could be related, I can pair my phone with my Honda CRV (2014) but
no audio output from either the car or the phone when making or
receiving a call.

-- 
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 1579369] Re: package resolvconf 1.77ubuntu1 failed to install/upgrade: underproces installerede post-installation-script returnerede afslutningsstatus 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package resolvconf 1.77ubuntu1 failed to install/upgrade: underproces
  installerede post-installation-script returnerede afslutningsstatus 1

Status in resolvconf package in Ubuntu:
  New

Bug description:
  Upgrade 14.04 LTS to 16.04
  ...
  Upgrade first from 14.04 to 15.10, which failed (locked screen for hours).
  apt-get dist-upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: resolvconf 1.77ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
  Uname: Linux 4.2.0-35-generic i686
  ApportVersion: 2.19.1-0ubuntu5
  AptOrdering:
   resolvconf: Configure
   NULL: ConfigurePending
  Architecture: i386
  Date: Sat May  7 15:31:59 2016
  DuplicateSignature: package:resolvconf:1.77ubuntu1:underproces installerede 
post-installation-script returnerede afslutningsstatus 1
  ErrorMessage: underproces installerede post-installation-script returnerede 
afslutningsstatus 1
  InstallationDate: Installed on 2011-12-03 (1616 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5.1
   apt  1.0.10.2ubuntu2
  SourcePackage: resolvconf
  Title: package resolvconf 1.77ubuntu1 failed to install/upgrade: underproces 
installerede post-installation-script returnerede afslutningsstatus 1
  UpgradeStatus: Upgraded to wily on 2016-05-07 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1579369/+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 1574732] Re: Regression: Kernel Update in 16.04 from last days renders nvidia driver unusable

[Tim Gardner]

That is the goal. I'm surprised that you didn't get a dialog on upgrade
that requested a decision on secure boot mode. You might if you remove
and reinstall the nVidia driver.

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

Title:
  Regression: Kernel Update in 16.04 from last days renders nvidia
  driver unusable

Status in shim:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I am running Ubuntu 16.04 since at least four months, always with the
  nvidia proprietary drivers (installed from the repository). I used
  nvidia-361 for a while with no issues (and i need it for steam
  gaming). However, an update installed on my machine yesterday breaks
  the nvidia drivers. I tried purging the driver, rebooting and
  reinstalling and i tried a newer version for the ubuntu-drivers ppa.
  Nothing helps: With the nvidia driver installed, i get a low-
  resolution login screen, but cannot login due to missing 3d
  acceleration. Running on nouveau works fine.

  This seems very strange to since everything worked until this
  afternoon. Yesterday, i was happily playing games on steam, installed
  some updates and now, my graphics are broken.


  
  $ lspci | grep NVIDIA
  01:00.0 VGA compatible controller: NVIDIA Corporation GM107 [GeForce GTX 750] 
(rev a2)
  01:00.1 Audio device: NVIDIA Corporation Device 0fbc (rev a1)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  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: Mon Apr 25 17:45:12 2016
  DistUpgraded: 2016-03-11 21:34:38,175 DEBUG enabling apt cron job
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-21-generic, x86_64: installed
   virtualbox, 5.0.18, 4.4.0-18-generic, x86_64: installed
   virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GM107 [GeForce GTX 750] [10de:1381] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Palit Microsystems Inc. GM107 [GeForce GTX 750] [1569:1381]
  InstallationDate: Installed on 2016-01-05 (110 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=ed669b2d-c3af-4570-9eb7-2978557208ae ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to xenial on 2016-03-11 (44 days ago)
  dmi.bios.date: 05/18/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.30
  dmi.board.name: H97 Performance
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.30:bd05/18/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH97Performance:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-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.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  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: Mon Apr 25 17:44:29 2016
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/shim/+bug/1574732/+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 1579369] [NEW] package resolvconf 1.77ubuntu1 failed to install/upgrade: underproces installerede post-installation-script returnerede afslutningsstatus 1

[Hazard Klubben]

Public bug reported:

Upgrade 14.04 LTS to 16.04
...
Upgrade first from 14.04 to 15.10, which failed (locked screen for hours).
apt-get dist-upgrade

ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: resolvconf 1.77ubuntu1
ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
Uname: Linux 4.2.0-35-generic i686
ApportVersion: 2.19.1-0ubuntu5
AptOrdering:
 resolvconf: Configure
 NULL: ConfigurePending
Architecture: i386
Date: Sat May  7 15:31:59 2016
DuplicateSignature: package:resolvconf:1.77ubuntu1:underproces installerede 
post-installation-script returnerede afslutningsstatus 1
ErrorMessage: underproces installerede post-installation-script returnerede 
afslutningsstatus 1
InstallationDate: Installed on 2011-12-03 (1616 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.2ubuntu5.1
 apt  1.0.10.2ubuntu2
SourcePackage: resolvconf
Title: package resolvconf 1.77ubuntu1 failed to install/upgrade: underproces 
installerede post-installation-script returnerede afslutningsstatus 1
UpgradeStatus: Upgraded to wily on 2016-05-07 (0 days ago)

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


** Tags: apport-package i386 third-party-packages wily

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

Title:
  package resolvconf 1.77ubuntu1 failed to install/upgrade: underproces
  installerede post-installation-script returnerede afslutningsstatus 1

Status in resolvconf package in Ubuntu:
  New

Bug description:
  Upgrade 14.04 LTS to 16.04
  ...
  Upgrade first from 14.04 to 15.10, which failed (locked screen for hours).
  apt-get dist-upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: resolvconf 1.77ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
  Uname: Linux 4.2.0-35-generic i686
  ApportVersion: 2.19.1-0ubuntu5
  AptOrdering:
   resolvconf: Configure
   NULL: ConfigurePending
  Architecture: i386
  Date: Sat May  7 15:31:59 2016
  DuplicateSignature: package:resolvconf:1.77ubuntu1:underproces installerede 
post-installation-script returnerede afslutningsstatus 1
  ErrorMessage: underproces installerede post-installation-script returnerede 
afslutningsstatus 1
  InstallationDate: Installed on 2011-12-03 (1616 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5.1
   apt  1.0.10.2ubuntu2
  SourcePackage: resolvconf
  Title: package resolvconf 1.77ubuntu1 failed to install/upgrade: underproces 
installerede post-installation-script returnerede afslutningsstatus 1
  UpgradeStatus: Upgraded to wily on 2016-05-07 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1579369/+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 1474435] Re: [dialler] "Smart dialing" is not supported

[Phil UK]

This is something that I think would be a great addition to have on the
phone and help bring the phone up to the standards that people would now
expect.

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

Title:
  [dialler] "Smart dialing" is not supported

Status in Ubuntu UX:
  Triaged
Status in dialer-app package in Ubuntu:
  Incomplete

Bug description:
  In Android, Windows phone, and older platforms (meaning, everywhere
  but iOS and apparently Jolla) you can  use the T9 letters in the
  dialer app to type the beginning of names and get suggested phone
  numbers.

  For example, if "Mom" is a contact, then typing 66 will suggest
  contacts that start with / contain "mo", even if the number doesn't
  include 66.

  I swear that Mom being 666 in this context is purely a coincidence, my
  mom is a perfectly lovely person :-)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1474435/+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 1551491] Re: Emoji skin tones are rendered as missing characters

[Launchpad Bug Tracker]

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

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

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

Title:
  Emoji skin tones are rendered as missing characters

Status in Canonical System Image:
  Confirmed
Status in messaging-app package in Ubuntu:
  Confirmed
Status in ubuntu-keyboard package in Ubuntu:
  Confirmed

Bug description:
  U+1F3FB through U+1F3FF are not rendered in the messaging app.
  Instead the "empty rectangle" missing-character symbol is rendered.

  These characters are the "EMOJI MODIFIER FITZPATRICK TYPE" characters.
  They are meant to indicate skin tone of the preceding emoji.

  I know that on the messaging app, all emoji are currently rendered as
  black and white.  I assume that is a design choice.  In the case we
  given specific color information, we either could render the color as
  requested or ignore it.  But in neither case should we show the
  "missing-character" symbol.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551491/+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 1551491] Re: Emoji skin tones are rendered as missing characters

[Launchpad Bug Tracker]

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

** Changed in: ubuntu-keyboard (Ubuntu)
   Status: New => Confirmed

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

Title:
  Emoji skin tones are rendered as missing characters

Status in Canonical System Image:
  Confirmed
Status in messaging-app package in Ubuntu:
  Confirmed
Status in ubuntu-keyboard package in Ubuntu:
  Confirmed

Bug description:
  U+1F3FB through U+1F3FF are not rendered in the messaging app.
  Instead the "empty rectangle" missing-character symbol is rendered.

  These characters are the "EMOJI MODIFIER FITZPATRICK TYPE" characters.
  They are meant to indicate skin tone of the preceding emoji.

  I know that on the messaging app, all emoji are currently rendered as
  black and white.  I assume that is a design choice.  In the case we
  given specific color information, we either could render the color as
  requested or ignore it.  But in neither case should we show the
  "missing-character" symbol.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551491/+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 1416038] Re: Wide emoji should be hidden

[Launchpad Bug Tracker]

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

** Changed in: ubuntu-keyboard (Ubuntu)
   Status: New => Confirmed

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

Title:
  Wide emoji should be hidden

Status in ubuntu-keyboard:
  New
Status in ubuntu-keyboard package in Ubuntu:
  Confirmed
Status in ubuntu-keyboard package in Ubuntu RTM:
  New

Bug description:
  There still remain a few emoji which are wider than the key space,
  these should be added to the list of emojis to skip.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-keyboard/+bug/1416038/+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 1428611] Re: Support two languages simultaneously

[Launchpad Bug Tracker]

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

** Changed in: ubuntu-keyboard (Ubuntu)
   Status: New => Confirmed

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

Title:
  Support two languages simultaneously

Status in ubuntu-keyboard:
  New
Status in ubuntu-keyboard package in Ubuntu:
  Confirmed

Bug description:
  (copy-pasted from a post comment)  The Sony Android soft keyboard has
  an amazing feature: it lets you have more than one language active at
  once. When you start writing you will get suggestions from both
  languages, but within a few words it will settle on the language you
  currently use (though still give you exact matches in the other). If
  you start typing in the other language it will again shift to that
  language by the third word or so.

  This is extraordinary useful. It's a constant irritant to have to
  manually switch languages all the time, and this completely eliminates
  it.

  Example:

  * The user has Swedish and English enabled. She starts writing "s t o r", and 
the suggestions "stor" (Swedish for "big"), "storage" and "storm" ("storm" in 
both Swedish and English) appear. She selects "storm". That's valid for both 
languages, so no decision is made. 
  * Next she writes "eye" which exists only in English. The input notes that 
but a single word is too little to go on. 
  * "is" is a word in both languages, so it doesn't change the language 
determination. 
  * "very" is again English, and now we have two recent votes for English and 
none for Swedish, enough to decide.
  * She starts typing "l a r", and English "large" comes up as a suggestion, 
while Swedish "larvig" (silly) does not.
  * She continues to type and actually writes "larvig". Since it's an exact 
match, the input will show it even though it uses English as the current 
language.

  
  In an ideal world, this would cover Japanese, Chinese and other 
non-alphabetic languages as well. They have long used the "present alternatives 
while the user types" approach already, and at least for Japanese it is common 
to spell out the word in alphabet, and get kana and kanji suggestions (I'm 
sorry I don't know the typical way for Chinese, Thai, Korean/Hangul or other 
languages). 

  So one approach for Japanese would be to present the hiragana
  transliteration as the sole Japanse option. If the user selects that,
  you'd switch to Japanese mode where all suggestions would be japanese
  except for the romaji (alphabet) transkription. Selecting that would
  again switch back to alphabet mode.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-keyboard/+bug/1428611/+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 1578693] Re: Would be useful to expose maximum OSK height

[Launchpad Bug Tracker]

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

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

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

Title:
  Would be useful to expose maximum OSK height

Status in qtmir package in Ubuntu:
  Confirmed
Status in ubuntu-keyboard package in Ubuntu:
  Confirmed

Bug description:
  There is a request from Design that on the greeter, we position the
  password input box above the OSK (so that it never has to move when
  the OSK appears).

  For unity8, we could probably hack together something that makes
  assumptions about size of OSK, but that's brittle, especially
  considering the future, when we might have input methods or custom
  keyboards.

  So I'm proposing that we add an UbuntuKeyboardInfo.maximumHeight field
  (and I guess maximumWidth to go with it...).  This would need support
  in ubuntu-keyboard too.

  I don't know the OSK design space super well though, so please provide
  commentary if this could be done a nicer way.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1578693/+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 1578693] Re: Would be useful to expose maximum OSK height

[Launchpad Bug Tracker]

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

** Changed in: ubuntu-keyboard (Ubuntu)
   Status: New => Confirmed

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

Title:
  Would be useful to expose maximum OSK height

Status in qtmir package in Ubuntu:
  Confirmed
Status in ubuntu-keyboard package in Ubuntu:
  Confirmed

Bug description:
  There is a request from Design that on the greeter, we position the
  password input box above the OSK (so that it never has to move when
  the OSK appears).

  For unity8, we could probably hack together something that makes
  assumptions about size of OSK, but that's brittle, especially
  considering the future, when we might have input methods or custom
  keyboards.

  So I'm proposing that we add an UbuntuKeyboardInfo.maximumHeight field
  (and I guess maximumWidth to go with it...).  This would need support
  in ubuntu-keyboard too.

  I don't know the OSK design space super well though, so please provide
  commentary if this could be done a nicer way.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1578693/+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 1578461] Re: Black screen: Mir servers (unity8, unity-system-compositor, mir_demo*) all crash on start-up in libhybris [linker.c:27: android_dlopen: Assertion `0' failed.']

[kevin gunn]

** Changed in: mir
   Status: New => Invalid

** Changed in: mir/0.22
   Status: New => Invalid

** Changed in: mir/0.23
   Status: New => Invalid

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

** Changed in: unity-system-compositor (Ubuntu)
   Status: Confirmed => Invalid

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

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => John McAleely (john.mcaleely)

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

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

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

Title:
  Black screen: Mir servers (unity8, unity-system-compositor, mir_demo*)
  all crash on start-up in libhybris [linker.c:27: android_dlopen:
  Assertion `0' failed.']

Status in Canonical System Image:
  In Progress
Status in Mir:
  Invalid
Status in Mir 0.22 series:
  Invalid
Status in Mir 0.23 series:
  Invalid
Status in libhybris package in Ubuntu:
  In Progress
Status in mir package in Ubuntu:
  Invalid
Status in unity-system-compositor package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Having mir-graphics-drivers-android9:amd64 installed prevents unity-
  system-compositor starting:

  [2016-05-05 10:19:09.118354] mirplatform: Found graphics driver: mir:mesa-kms 
(version 0.22.0)
  android_dlopen called but not implemented!
  unity-system-compositor: linker.c:27: android_dlopen: Assertion `0' failed.

  which was caused by:

  sudo apt-add-repository ppa:ci-train-ppa-service/stable-phone-overlay

  WORKING: hybris 0.1.0+git20151016+6d424c9-0ubuntu7
  FAILING: hybris 0.1.0+git20151016+6d424c9-0ubuntu11

  WORKAROUNDS:
   * Remove ppa:ci-train-ppa-service/stable-phone-overlay from your system to 
completely solve the problem; or
   * Don't use Unity8 -- other Mir servers will work after you remove package 
mir-graphics-drivers-android9:amd64 which is their last remaining dependency on 
libhybris.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1578461/+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 1385417] Re: [OSK] The OSK should switch to search layout when a space is entered after a word

[Launchpad Bug Tracker]

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

** Changed in: ubuntu-keyboard (Ubuntu)
   Status: New => Confirmed

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

Title:
  [OSK] The OSK should switch to search layout when a space is entered
  after a word

Status in ubuntu-keyboard:
  Confirmed
Status in Ubuntu UX:
  Fix Committed
Status in ubuntu-keyboard package in Ubuntu:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  In the Browser, the OSK should switch to search layout when a space is
  entered after a word.

  Currently, the same keyboard layout is used.

  UX:
  
https://docs.google.com/a/canonical.com/presentation/d/1Qrd4Flfs3EH-fI79IfrYgLdAx2nce-L7ve8NKLCX324/edit#slide=id.g2b64bc8c2_57

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-keyboard/+bug/1385417/+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 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04

[Sam Brookfield]

Affects HP Spectre z360 also (suspend works from interface but does not
happen when lid closed despite setting in power settings) - had to both
upgrade to kernel 4.4.8 from 4.4.0 and add the workarounds to
/etc/systemd/login.d to get it to work - just upgrade / workaround did
not work separately. No multiple displays or dock (xrandr confirmed) -
but haven't checked if power connecter removed works without workaround
(not any use to me).

systemd-inhibit output - 
 Who: sam (UID 1000/sam, PID 1750/unity-settings-)
What: handle-power-key:handle-suspend-key:handle-hibernate-key
 Why: GNOME handling keypresses
Mode: block

 Who: sam (UID 1000/sam, PID 1750/unity-settings-)
What: sleep
 Why: GNOME needs to lock the screen
Mode: delay

 Who: NetworkManager (UID 0/root, PID 873/NetworkManager)
What: sleep
 Why: NetworkManager needs to turn off networks
Mode: delay

 Who: sam (UID 1000/sam, PID 1757/gnome-session-b)
What: shutdown:sleep
 Why: user session inhibited
Mode: block

4 inhibitors listed.

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

Title:
  Notebook doesn't suspend when lid is closed after update to 16.04

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  My notebook does not suspend after upgrading from 15.10 to 16.04.

  According to system settings the notebook should suspend when lid is
  closed but actually this does not happen. Instead it continues to run
  as if nothing had happened.

  With the previous versions of ubuntu (14.04-15.10) everything worked
  fine.

  My System: HP Pavilion dv7.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: acpi (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr 23 23:11:15 2016
  InstallationDate: Installed on 2015-10-29 (176 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: acpi
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1574120/+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 1510659] Re: Enable T9 for names search with dialer

[Anupam]

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

** This bug has been marked a duplicate of bug 1474435
   [dialler] "Smart dialing" is not supported

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

Title:
  Enable T9 for names search with dialer

Status in Ubuntu UX:
  Triaged
Status in dialer-app package in Ubuntu:
  Confirmed

Bug description:
  In the dialer app of the OS with the green robot it is possible to
  search for telephone numbers by inputting the names via T9.

  Example:
  A "Dave" and his phone number could be found by typing 3, 2, 8 and 3, as 
these are the T9 keys for the D, A, V and E.

  I don't like green robots, but this function is snappy.

  Thank you + best regards!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1510659/+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 1579354] [NEW] update to symbol files for ubuntuBSD

[Jon Boden]

Public bug reported:

Hi

Please could you update symbol files to support ubuntuBSD?

Patch available at:

https://bazaar.launchpad.net/~ubuntubsd/ubuntubsd/patches-
xenial/download/jon%40ubuntubsd.org-20160507101512-x4utf9ar71uy4j31/qtdeclarativeopensou-20160426081048-uj0038tten98r2t3-56
/qtdeclarative-opensource-src.diff

Thank you!

** Affects: qtdeclarative-opensource-src (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: patch ubuntubsd

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

Title:
  update to symbol files for ubuntuBSD

Status in qtdeclarative-opensource-src package in Ubuntu:
  New

Bug description:
  Hi

  Please could you update symbol files to support ubuntuBSD?

  Patch available at:

  https://bazaar.launchpad.net/~ubuntubsd/ubuntubsd/patches-
  
xenial/download/jon%40ubuntubsd.org-20160507101512-x4utf9ar71uy4j31/qtdeclarativeopensou-20160426081048-uj0038tten98r2t3-56
  /qtdeclarative-opensource-src.diff

  Thank you!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1579354/+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