date:20160307

** Tags added: latest-bios-217

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

Title:
  Only one monitor working at the time (xorg-amdgpu)

Status in xorg package in Ubuntu:
  New

Bug description:
  When external monitor is connected to VGA port (AMD Radeon 7470m) internal 
laptop monitor stops working. I'm able to set laptop monitor as primary which 
disables external monitor (and vice-versa) 
  I was using fglrx without problems however after fglrx support dropped in 
recent Ubuntu update I was forced to return to xorg driver. Tried manual switch 
to mainline Linux 4.5 kernel, same thing. Tested on 14.04, 15.10, 16.04 with 
same results.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.5.0-040500rc6-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Mar  5 04:32:48 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.14, 4.4.0-10-generic, x86_64: installed
   virtualbox, 5.0.14, 4.4.0-8-generic, x86_64: installed
   virtualbox, 5.0.14, 4.5.0-040500rc6-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7640G] [1002:9903] 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Trinity [Radeon HD 7640G] [1043:106b]
   Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M 
Series] [1002:6760] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2016-02-18 (15 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: ASUSTeK COMPUTER INC. K55DR
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.5.0-040500rc6-generic 
root=UUID=e0064410-4660-40b7-b961-76f320a921a6 ro amdgpu.powerplay=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/07/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 217
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K55DR
  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.:bvr217:bd09/07/2012:svnASUSTeKCOMPUTERINC.:pnK55DR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK55DR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: K55DR
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160209-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu3
  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.6.1-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160218-1ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Mar  5 04:27:41 2016
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.1-1ubuntu3
  xserver.video_driver: radeon

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

claudia fischer, thank you for reporting this and helping make Ubuntu
better.

Could you please provide the full computer model as noted on the sticker
of the computer itself (not from the Bug Description)?

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

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

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

Title:
  recover items

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  suddenly, my  dash border, changed items, installed before, and  it's
  impossible to recover the authentic version

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-79.123-generic 3.13.11-ckt33
  Uname: Linux 3.13.0-79-generic i686
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Mar  4 22:38:01 2016
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile 945GSE Express Integrated Graphics Controller 
[8086:27ae] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:361a]
 Subsystem: Hewlett-Packard Company Device [103c:361a]
  InstallationDate: Installed on 2014-08-07 (575 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  MachineType: Hewlett-Packard Compaq Mini
  ProcEnviron:
   LANGUAGE=es_ES
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-79-generic 
root=UUID=ae740fb9-720f-48b0-91f0-d0635e397c26 ro vesafb.invalid=1 
plymouth:debug nopat drm.debug=0xe
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/07/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 361A0 Ver. F.05
  dmi.board.name: 361A
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 02.0D
  dmi.chassis.asset.tag: CNU8513JRY
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr361A0Ver.F.05:bd11/07/2008:svnHewlett-Packard:pnCompaqMini:pvrF.05:rvnHewlett-Packard:rn361A:rvrKBCVersion02.0D:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: Compaq Mini
  dmi.product.version: F.05
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  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.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: Fri Mar  4 22:02:54 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1260 
   vendor CPT
  xserver.version: 2:1.15.1-0ubuntu2.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1553397/+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 1554254] Re: /usr/bin/online-accounts-ui:11:strlen:QByteArray::QByteArray:Accounts::Provider::domDocument:OnlineAccountsUi::ApplicationManager::providerInfo:OnlineAccountsUi::Pro

2016-03-07 Thread Alberto Mardegan

** Changed in: ubuntu-system-settings-online-accounts (Ubuntu)
   Status: New => In Progress

** Changed in: ubuntu-system-settings-online-accounts (Ubuntu)
   Importance: Undecided => High

** Changed in: ubuntu-system-settings-online-accounts (Ubuntu)
 Assignee: (unassigned) => Alberto Mardegan (mardy)

** Also affects: webapps-sprint
   Importance: Undecided
   Status: New

** Changed in: webapps-sprint
Milestone: None => sprint-19

** Changed in: webapps-sprint
 Assignee: (unassigned) => Alberto Mardegan (mardy)

** Changed in: webapps-sprint
   Importance: Undecided => High

** Changed in: webapps-sprint
   Status: New => In Progress

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

Title:
  /usr/bin/online-accounts-
  
ui:11:strlen:QByteArray::QByteArray:Accounts::Provider::domDocument:OnlineAccountsUi::ApplicationManager::providerInfo:OnlineAccountsUi::ProviderRequestPrivate::start

Status in webapps-sprint:
  In Progress
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  In Progress

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding ubuntu-system-settings-online-accounts.  This problem was
  most recently seen with version 0.7+15.04.20160111-0ubuntu1, the
  problem page at
  https://errors.ubuntu.com/problem/8f2f8f5d25b7f00989051db7128ed6d2c66995fb
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/webapps-sprint/+bug/1554254/+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 1527354] Re: [Jawbone ERA] HFP features not working with Bluez5 when phone initiates connection

@Tony: With your last comment: BlueZ 5.37 doesn't fix that problem too?
Or do you still see this with bluez 5.37?

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

Title:
  [Jawbone ERA] HFP features not working with Bluez5 when phone
  initiates connection

Status in Canonical System Image:
  New
Status in bluez package in Ubuntu:
  In Progress

Bug description:
  While debugging some re-factoring work on the ofono upower plugin, I
  noticed that I wasn't able to answer or terminate calls using my
  Jawbone ERA headset.  I bought this headset last year, and although
  it's an older model, it's spec sheet states that it supports HSP 1.1,
  and HFP 1.5.

  I can pair the device with my krillin, and it properly auto connects (
  note, this seems to work better than my iPhone ).   In-call audio
  works for both incoming and outgoing calls, however I get no ringtone
  in the headset and as mentioned above, I can't answer or terminate the
  call.   I've verified on my iPhone6, that the headset works.  In
  addition to a ringtone in the earpiece, the headset also announces the
  incoming phone number.

  From looking at the ofono debug output, I'm never seeing a new HFP
  connection occur.  I noticed as the upower plugin uses a foreach_atom
  (HFP) style call to update the battery indicators on all attached HFP
  devices.

  I've tested this extensively on krillin, running rc-proposed:

  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 205
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-12-16 17:53:19
  version version: 205
  version ubuntu: 20151216
  version device: 20151204-2254a36
  version custom: 2015--36-46-vivid

  I've also tested on mako, rc-proposed ( #317 ).

  For reference here's the versions of bluez, ofono, and PulseAudio on
  the device:

  bluez 5.36-0ubuntu2~overlay1
  ofono  1.17.bzr6908+15.04.20151203-0ubuntu1~awe3
  pulseaudio1:6.0-0ubuntu9.11

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1527354/+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 1491340] Re: Bluetooth keyboard is configured with wrong keyboard layout

2016-03-07 Thread Victor gonzalez

** Tags added: bq-feedback

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

Title:
  Bluetooth keyboard is configured with wrong keyboard layout

Status in The Avila project:
  In Progress
Status in Canonical System Image:
  In Progress
Status in Canonical Pocket Desktop:
  In Progress
Status in bluez package in Ubuntu:
  Invalid
Status in ubuntu-system-settings package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Phone: Meizu MX4 (15.04 r4)
  OS Language: German

  What you expected to happen:
  When connecting a Bluetooth keyboard I expect that the keyboard layout is the 
same as the keyboard hardware key layout (German) or that it is possible to 
change the keyboard layout in the Bluetooth setting for the connected Bluetooth 
device.

  What happened instead:
  The Bluetooth keyboard worked, but wasn't set to German key layout. In the 
Bluetooth device setting I couldn't find any option to change the Bluetooth 
keyboard key layout.

To manage notifications about this bug go to:
https://bugs.launchpad.net/avila/+bug/1491340/+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 1500751] Re: Cryptsetup Keyboard not working on Xubuntu 3.19.0-30

2016-03-07 Thread Timo Aaltonen

the vivid task can be dropped by now

** Changed in: initramfs-tools (Ubuntu Vivid)
   Status: Triaged => Won't Fix

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

Title:
  Cryptsetup Keyboard not working on Xubuntu 3.19.0-30

Status in cryptsetup package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in cryptsetup source package in Trusty:
  Invalid
Status in initramfs-tools source package in Trusty:
  Triaged
Status in cryptsetup source package in Vivid:
  Invalid
Status in initramfs-tools source package in Vivid:
  Won't Fix

Bug description:
  I am running Xubuntu 15.04 and just upgraded to the latest kernel (3.19.0-30).
  After upgrading the boot time is longer (what is negligible) but the more 
severe error is, that I cannot enter my passphrase when I see the crypt dialog.
  I just see the dialog to enter my passphrase, but when I try to enter it, 
nothing appears in the textfield. I tried with the builtin laptop keyboard but 
also with an external USB keyboard.

  I thought about supplying more information, but things like the syslog
  are not helping apparently (I was not able to boot until the syslog
  would capture information...). If you need anything I can provide, I
  gladly help.

  [Test case]
  1. On an affected system boot into kernel 3.19.0-30

  [Solution]
  The "solution" for now is booting the older Kernel 3.19.0-28 (which isn't a 
real solution).

  PS.: Bugs like the following are either not applicable or the solution is not 
working for me:
  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/229732
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359689
  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1238194

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1500751/+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 1554366] Re: BQ E4.5: QWERTZ keyboard per bluetooth

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

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

Title:
  BQ E4.5: QWERTZ keyboard per bluetooth

Status in ubuntu-keyboard package in Ubuntu:
  Confirmed

Bug description:
  
  I think I have now found exactly what I was locking for as BT keyboard with 
mouse "on board":

  http://www.amazon.de/dp/B0142BCTT2?psc=1
  
http://www.amazon.co.uk/BATTOP-Ultra-Thin-Bluetooth-Wireless-Keyboard/dp/B0142BCTT2

  This has a German QWERTZ layout and it pairs fine with the E4.5
  The only problem I have is, it is German QWERTZ layout and I do
  not know how to change this in the Ubuntu BQ E4.5. Normaly in Ubuntu
  desktop you can change this, or in FreeBSD, in KDE, etc. How this must
  be done in the BQ E4.5, maybe with some command from phablets shell.

  I tried, for example

  $ sudo dpkg-reconfigure keyboard-configuration

  but this complains about the root FS being read-only.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1554366/+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 1241101]

2016-03-07 Thread Marc-andre-laperle

I'll assign to myself for now to investigate a fix in Ubuntu. Otherwise
we can try to apply the patch in SWT.

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

Title:
  Java crash in libglib-2.0 after upgrade from 13.04 to 13.10

Status in Eclipse:
  Confirmed
Status in gtk+2.0 package in Ubuntu:
  Triaged
Status in unity package in Ubuntu:
  Invalid
Status in gtk+2.0 package in Suse:
  New

Bug description:
  Running smartgit 4.6.4 on 13.10 64 bits. After registering the
  product, smartgit crash when trying to open a new repository. Java
  error log :

  # A fatal error has been detected by the Java Runtime Environment:
  #
  #  SIGSEGV (0xb) at pc=0x7fa59061f9c0, pid=12494, tid=140349308167936
  #
  # JRE version: 7.0_25-b30
  # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 
compressed oops)
  # Problematic frame:
  # C  [libglib-2.0.so.0+0x389c0]  g_str_hash+0x0

  I tried different version of Java (Oracle v7 and v6 jre) with same
  result. Also, Eclipse display blank menus so there's a general java
  problem with displays.

To manage notifications about this bug go to:
https://bugs.launchpad.net/eclipse/+bug/1241101/+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 1554365] Re: UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 2886: ordinal not in range(128)

2016-03-07 Thread Marius Gedminas

I got this error email from four different OpenVZ-based VPSes, but not
from any other servers.  I wonder what's peculiar about their
configuration.  Locale used by cron?

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

Title:
  UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position
  2886: ordinal not in range(128)

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  I got this in the mail:

  From: Cron Daemon 
  To: root@...
  Subject: Cron  test -x /usr/sbin/anacron || ( cd / && 
run-parts --report /etc/cron.daily )
  Date: Thu, 25 Feb 2016 02:11:47 +0200 (EET)

  /etc/cron.daily/apt:
  Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 1255, in 
  main(options)
File "/usr/bin/unattended-upgrade", line 1205, in main
  pkgs, pkg_install_success, pkgs_kept_back, mem_log, logfile_dpkg)
File "/usr/bin/unattended-upgrade", line 752, in send_summary_mail
  body += fp.read()
File "/usr/lib/python3.4/encodings/ascii.py", line 26, in decode
  return codecs.ascii_decode(input, self.errors)[0]
  UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 
2886: ordinal not in range(128)

  According to /var/log/apt/history.log.1.gz, the packages upgraded that
  day were

  Start-Date: 2016-02-25  02:06:22
  Upgrade: libgnutls-openssl27:amd64 (2.12.23-12ubuntu2.4, 
2.12.23-12ubuntu2.5), libssl1.0.0:amd64 (1.0.1f-1ubuntu2.16, 
1.0.1f-1ubuntu2.17), libvirt0:amd64 (1.2.2-0ubuntu13.1.16, 
1.2.2-0ubuntu13.1.17), libssl-dev:amd64 (1.0.1f-1ubuntu2.16, 
1.0.1f-1ubuntu2.17), ca-certificates:amd64 (20141019ubuntu0.14.04.1, 
20160104ubuntu0.14.04.1), libgnutls26:amd64 (2.12.23-12ubuntu2.4, 
2.12.23-12ubuntu2.5), libssl-doc:amd64 (1.0.1f-1ubuntu2.16, 
1.0.1f-1ubuntu2.17), openssl:amd64 (1.0.1f-1ubuntu2.16, 1.0.1f-1ubuntu2.17)
  End-Date: 2016-02-25  02:06:36

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unattended-upgrades 0.82.1ubuntu2.4
  Uname: Linux 2.6.32-042stab108.8 x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Tue Mar  8 08:26:05 2016
  PackageArchitecture: all
  ProcEnviron:
   LC_CTYPE=lt_LT.UTF-8
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=lt_LT.UTF-8
   SHELL=/bin/bash
  SourcePackage: unattended-upgrades
  UpgradeStatus: Upgraded to trusty on 2016-02-06 (30 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1554365/+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 1551858] Re: [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt

@Tony: Can you reproduce this once again and record the HCI packets by
running

 $ sudo btmon -w test.cap

Then attach test.cap here.

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

Title:
  [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt

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

Bug description:
  Connecting to the latest generation Apple BT keyboard ( the one with
  the USB port & no batteries ) fails on an Ubuntu Touch device, as when
  you press the "Connect" button on the device page, a dialog titled
  "Bluetooth Pairing Request" is displayed, with the following text:

  Please confirm that the PIN displayed on 'Magic Keyboard' matches this
  one: XX

  The dialog has "Cancel" and "Confirm PIN" buttons.

  The keyboard has no display on which a PIN could be displayed.

  When using other devices ( Ubuntu Desktop 15.10, 16.04, Android, OS X,
  ... ) to connect this keyboard all that's necessary is to click/press
  the 'Connect' button in the appropriate place, and the keyboard
  automatically connects, and is usable with no other actions required
  from the user.

  Reproduced on krillin ( rc-proposed/bq-aquris.en/270 ) which has bluez
  5.36-0ubuntu2~overlay1 installed.

  Reproduced on arale ( rc-proposed/meizu.en/258 ) which has bluez 5.37
  installed from silo 39.

  Note, after dismissing the dialog, subsequent attempts to connect may
  not re-display the PIN dialog, instead nothing happens.  I've found
  that this requires power cycling the keyboard to clear and cause the
  PIN dialog to be displayed again.

  [bluetooth]# show
  Controller B8:64:91:48:2B:1E
Name: Aquaris E4.5 Ubuntu Edition
Alias: Aquaris E4.5 Ubuntu Edition
Class: 0x1c020c
Powered: yes
Discoverable: no
Pairable: yes
UUID: Headset AG(1112--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb)
UUID: Phonebook Access Server   (112f--1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0525
Discovering: no

  [bluetooth]# devices
  Device 18:EE:69:21:6C:D3 18-EE-69-21-6C-D3
  Device DE:76:E2:04:9D:6F BB-9D6F
  Device 7C:D1:C3:1C:B4:03 7C-D1-C3-1C-B4-03
  Device 7C:D1:C3:19:2B:D8 7C-D1-C3-19-2B-D8
  Device 84:38:35:67:0C:3D ubuntu-0
  Device 04:69:F8:C2:A0:09 tony espy’s Keyboard
  Device 00:21:3C:A0:14:A6 Jawbone ERA
  Device 1C:1A:C0:B2:9A:D7 1C-1A-C0-B2-9A-D7

  Device info *before* pairing attempt:

  Device 04:69:F8:C2:A0:09
Name: tony espy’s Keyboard
Alias: tony espy’s Keyboard
Class: 0x002540
Icon: input-keyboard
Paired: no
Trusted: no
Blocked: no
Connected: no
LegacyPairing: no
Modalias: bluetooth:v004Cp0267d0066

  No changes in any of the attributes after *after* the pairing attempt
  ( output of info command is the same ).

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551858/+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 1554366] Re: BQ E4.5: QWERTZ keyboard per bluetooth

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

** This bug has been marked a duplicate of bug 1412492
   can't change the keyboard layout

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

Title:
  BQ E4.5: QWERTZ keyboard per bluetooth

Status in ubuntu-keyboard package in Ubuntu:
  New

Bug description:
  
  I think I have now found exactly what I was locking for as BT keyboard with 
mouse "on board":

  http://www.amazon.de/dp/B0142BCTT2?psc=1
  
http://www.amazon.co.uk/BATTOP-Ultra-Thin-Bluetooth-Wireless-Keyboard/dp/B0142BCTT2

  This has a German QWERTZ layout and it pairs fine with the E4.5
  The only problem I have is, it is German QWERTZ layout and I do
  not know how to change this in the Ubuntu BQ E4.5. Normaly in Ubuntu
  desktop you can change this, or in FreeBSD, in KDE, etc. How this must
  be done in the BQ E4.5, maybe with some command from phablets shell.

  I tried, for example

  $ sudo dpkg-reconfigure keyboard-configuration

  but this complains about the root FS being read-only.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1554366/+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 1554365] Re: UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 2886: ordinal not in range(128)

2016-03-07 Thread Marius Gedminas

/var/log/unattended-upgrades/unattended-upgrades-
dpkg_2016-02-25_02:06:20.971350.log contains this line:

Adding
debian:TÜRKTRUST_Elektronik_Sertifika_Hizmet_Sağlayıcısı_H5.pem

the Ü is at byte position 2888 of 10432 according to vim (which uses a
1-based offset and probably points to the last byte of multi-byte
characters).

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

Title:
  UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position
  2886: ordinal not in range(128)

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  I got this in the mail:

  From: Cron Daemon 
  To: root@...
  Subject: Cron  test -x /usr/sbin/anacron || ( cd / && 
run-parts --report /etc/cron.daily )
  Date: Thu, 25 Feb 2016 02:11:47 +0200 (EET)

  /etc/cron.daily/apt:
  Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 1255, in 
  main(options)
File "/usr/bin/unattended-upgrade", line 1205, in main
  pkgs, pkg_install_success, pkgs_kept_back, mem_log, logfile_dpkg)
File "/usr/bin/unattended-upgrade", line 752, in send_summary_mail
  body += fp.read()
File "/usr/lib/python3.4/encodings/ascii.py", line 26, in decode
  return codecs.ascii_decode(input, self.errors)[0]
  UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 
2886: ordinal not in range(128)

  According to /var/log/apt/history.log.1.gz, the packages upgraded that
  day were

  Start-Date: 2016-02-25  02:06:22
  Upgrade: libgnutls-openssl27:amd64 (2.12.23-12ubuntu2.4, 
2.12.23-12ubuntu2.5), libssl1.0.0:amd64 (1.0.1f-1ubuntu2.16, 
1.0.1f-1ubuntu2.17), libvirt0:amd64 (1.2.2-0ubuntu13.1.16, 
1.2.2-0ubuntu13.1.17), libssl-dev:amd64 (1.0.1f-1ubuntu2.16, 
1.0.1f-1ubuntu2.17), ca-certificates:amd64 (20141019ubuntu0.14.04.1, 
20160104ubuntu0.14.04.1), libgnutls26:amd64 (2.12.23-12ubuntu2.4, 
2.12.23-12ubuntu2.5), libssl-doc:amd64 (1.0.1f-1ubuntu2.16, 
1.0.1f-1ubuntu2.17), openssl:amd64 (1.0.1f-1ubuntu2.16, 1.0.1f-1ubuntu2.17)
  End-Date: 2016-02-25  02:06:36

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unattended-upgrades 0.82.1ubuntu2.4
  Uname: Linux 2.6.32-042stab108.8 x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Tue Mar  8 08:26:05 2016
  PackageArchitecture: all
  ProcEnviron:
   LC_CTYPE=lt_LT.UTF-8
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=lt_LT.UTF-8
   SHELL=/bin/bash
  SourcePackage: unattended-upgrades
  UpgradeStatus: Upgraded to trusty on 2016-02-06 (30 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1554365/+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 1554366] [NEW] BQ E4.5: QWERTZ keyboard per bluetooth

2016-03-07 Thread Matthias Apitz

Public bug reported:


I think I have now found exactly what I was locking for as BT keyboard with 
mouse "on board":

http://www.amazon.de/dp/B0142BCTT2?psc=1
http://www.amazon.co.uk/BATTOP-Ultra-Thin-Bluetooth-Wireless-Keyboard/dp/B0142BCTT2

This has a German QWERTZ layout and it pairs fine with the E4.5
The only problem I have is, it is German QWERTZ layout and I do
not know how to change this in the Ubuntu BQ E4.5. Normaly in Ubuntu
desktop you can change this, or in FreeBSD, in KDE, etc. How this must
be done in the BQ E4.5, maybe with some command from phablets shell.

I tried, for example

$ sudo dpkg-reconfigure keyboard-configuration

but this complains about the root FS being read-only.

** Affects: ubuntu-keyboard (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/1554366

Title:
  BQ E4.5: QWERTZ keyboard per bluetooth

Status in ubuntu-keyboard package in Ubuntu:
  New

Bug description:
  
  I think I have now found exactly what I was locking for as BT keyboard with 
mouse "on board":

  http://www.amazon.de/dp/B0142BCTT2?psc=1
  
http://www.amazon.co.uk/BATTOP-Ultra-Thin-Bluetooth-Wireless-Keyboard/dp/B0142BCTT2

  This has a German QWERTZ layout and it pairs fine with the E4.5
  The only problem I have is, it is German QWERTZ layout and I do
  not know how to change this in the Ubuntu BQ E4.5. Normaly in Ubuntu
  desktop you can change this, or in FreeBSD, in KDE, etc. How this must
  be done in the BQ E4.5, maybe with some command from phablets shell.

  I tried, for example

  $ sudo dpkg-reconfigure keyboard-configuration

  but this complains about the root FS being read-only.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1554366/+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 1554365] [NEW] UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 2886: ordinal not in range(128)

2016-03-07 Thread Marius Gedminas

Public bug reported:

I got this in the mail:

From: Cron Daemon 
To: root@...
Subject: Cron  test -x /usr/sbin/anacron || ( cd / && run-parts 
--report /etc/cron.daily )
Date: Thu, 25 Feb 2016 02:11:47 +0200 (EET)

/etc/cron.daily/apt:
Traceback (most recent call last):
  File "/usr/bin/unattended-upgrade", line 1255, in 
main(options)
  File "/usr/bin/unattended-upgrade", line 1205, in main
pkgs, pkg_install_success, pkgs_kept_back, mem_log, logfile_dpkg)
  File "/usr/bin/unattended-upgrade", line 752, in send_summary_mail
body += fp.read()
  File "/usr/lib/python3.4/encodings/ascii.py", line 26, in decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 2886: 
ordinal not in range(128)

According to /var/log/apt/history.log.1.gz, the packages upgraded that
day were

Start-Date: 2016-02-25  02:06:22
Upgrade: libgnutls-openssl27:amd64 (2.12.23-12ubuntu2.4, 
2.12.23-12ubuntu2.5), libssl1.0.0:amd64 (1.0.1f-1ubuntu2.16, 
1.0.1f-1ubuntu2.17), libvirt0:amd64 (1.2.2-0ubuntu13.1.16, 
1.2.2-0ubuntu13.1.17), libssl-dev:amd64 (1.0.1f-1ubuntu2.16, 
1.0.1f-1ubuntu2.17), ca-certificates:amd64 (20141019ubuntu0.14.04.1, 
20160104ubuntu0.14.04.1), libgnutls26:amd64 (2.12.23-12ubuntu2.4, 
2.12.23-12ubuntu2.5), libssl-doc:amd64 (1.0.1f-1ubuntu2.16, 
1.0.1f-1ubuntu2.17), openssl:amd64 (1.0.1f-1ubuntu2.16, 1.0.1f-1ubuntu2.17)
End-Date: 2016-02-25  02:06:36

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unattended-upgrades 0.82.1ubuntu2.4
Uname: Linux 2.6.32-042stab108.8 x86_64
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
Date: Tue Mar  8 08:26:05 2016
PackageArchitecture: all
ProcEnviron:
 LC_CTYPE=lt_LT.UTF-8
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=lt_LT.UTF-8
 SHELL=/bin/bash
SourcePackage: unattended-upgrades
UpgradeStatus: Upgraded to trusty on 2016-02-06 (30 days ago)

** Affects: unattended-upgrades (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 unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1554365

Title:
  UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position
  2886: ordinal not in range(128)

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  I got this in the mail:

  From: Cron Daemon 
  To: root@...
  Subject: Cron  test -x /usr/sbin/anacron || ( cd / && 
run-parts --report /etc/cron.daily )
  Date: Thu, 25 Feb 2016 02:11:47 +0200 (EET)

  /etc/cron.daily/apt:
  Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 1255, in 
  main(options)
File "/usr/bin/unattended-upgrade", line 1205, in main
  pkgs, pkg_install_success, pkgs_kept_back, mem_log, logfile_dpkg)
File "/usr/bin/unattended-upgrade", line 752, in send_summary_mail
  body += fp.read()
File "/usr/lib/python3.4/encodings/ascii.py", line 26, in decode
  return codecs.ascii_decode(input, self.errors)[0]
  UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 
2886: ordinal not in range(128)

  According to /var/log/apt/history.log.1.gz, the packages upgraded that
  day were

  Start-Date: 2016-02-25  02:06:22
  Upgrade: libgnutls-openssl27:amd64 (2.12.23-12ubuntu2.4, 
2.12.23-12ubuntu2.5), libssl1.0.0:amd64 (1.0.1f-1ubuntu2.16, 
1.0.1f-1ubuntu2.17), libvirt0:amd64 (1.2.2-0ubuntu13.1.16, 
1.2.2-0ubuntu13.1.17), libssl-dev:amd64 (1.0.1f-1ubuntu2.16, 
1.0.1f-1ubuntu2.17), ca-certificates:amd64 (20141019ubuntu0.14.04.1, 
20160104ubuntu0.14.04.1), libgnutls26:amd64 (2.12.23-12ubuntu2.4, 
2.12.23-12ubuntu2.5), libssl-doc:amd64 (1.0.1f-1ubuntu2.16, 
1.0.1f-1ubuntu2.17), openssl:amd64 (1.0.1f-1ubuntu2.16, 1.0.1f-1ubuntu2.17)
  End-Date: 2016-02-25  02:06:36

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unattended-upgrades 0.82.1ubuntu2.4
  Uname: Linux 2.6.32-042stab108.8 x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Tue Mar  8 08:26:05 2016
  PackageArchitecture: all
  ProcEnviron:
   LC_CTYPE=lt_LT.UTF-8
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=lt_LT.UTF-8
   SHELL=/bin/bash
  SourcePackage: unattended-upgrades
  UpgradeStatus: Upgraded to trusty on 2016-02-06 (30 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1554365/+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 1551858] Re: [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt

Just as a additional note: The actual pairing method is selected in the
kernel. See
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/net/bluetooth/smp.c#n859

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

Title:
  [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt

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

Bug description:
  Connecting to the latest generation Apple BT keyboard ( the one with
  the USB port & no batteries ) fails on an Ubuntu Touch device, as when
  you press the "Connect" button on the device page, a dialog titled
  "Bluetooth Pairing Request" is displayed, with the following text:

  Please confirm that the PIN displayed on 'Magic Keyboard' matches this
  one: XX

  The dialog has "Cancel" and "Confirm PIN" buttons.

  The keyboard has no display on which a PIN could be displayed.

  When using other devices ( Ubuntu Desktop 15.10, 16.04, Android, OS X,
  ... ) to connect this keyboard all that's necessary is to click/press
  the 'Connect' button in the appropriate place, and the keyboard
  automatically connects, and is usable with no other actions required
  from the user.

  Reproduced on krillin ( rc-proposed/bq-aquris.en/270 ) which has bluez
  5.36-0ubuntu2~overlay1 installed.

  Reproduced on arale ( rc-proposed/meizu.en/258 ) which has bluez 5.37
  installed from silo 39.

  Note, after dismissing the dialog, subsequent attempts to connect may
  not re-display the PIN dialog, instead nothing happens.  I've found
  that this requires power cycling the keyboard to clear and cause the
  PIN dialog to be displayed again.

  [bluetooth]# show
  Controller B8:64:91:48:2B:1E
Name: Aquaris E4.5 Ubuntu Edition
Alias: Aquaris E4.5 Ubuntu Edition
Class: 0x1c020c
Powered: yes
Discoverable: no
Pairable: yes
UUID: Headset AG(1112--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb)
UUID: Phonebook Access Server   (112f--1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0525
Discovering: no

  [bluetooth]# devices
  Device 18:EE:69:21:6C:D3 18-EE-69-21-6C-D3
  Device DE:76:E2:04:9D:6F BB-9D6F
  Device 7C:D1:C3:1C:B4:03 7C-D1-C3-1C-B4-03
  Device 7C:D1:C3:19:2B:D8 7C-D1-C3-19-2B-D8
  Device 84:38:35:67:0C:3D ubuntu-0
  Device 04:69:F8:C2:A0:09 tony espy’s Keyboard
  Device 00:21:3C:A0:14:A6 Jawbone ERA
  Device 1C:1A:C0:B2:9A:D7 1C-1A-C0-B2-9A-D7

  Device info *before* pairing attempt:

  Device 04:69:F8:C2:A0:09
Name: tony espy’s Keyboard
Alias: tony espy’s Keyboard
Class: 0x002540
Icon: input-keyboard
Paired: no
Trusted: no
Blocked: no
Connected: no
LegacyPairing: no
Modalias: bluetooth:v004Cp0267d0066

  No changes in any of the attributes after *after* the pairing attempt
  ( output of info command is the same ).

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551858/+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 1551858] Re: [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt

And there we go:

Mar  7 15:08:44 ubuntu-phablet bluetoothd[890]: src/device.c:new_auth() 
Requesting agent authentication for 04:69:F8:C2:A0:09
Mar  7 15:08:44 ubuntu-phablet bluetoothd[890]: src/agent.c:agent_ref() 
0xb8c78950: ref=3
Mar  7 15:08:44 ubuntu-phablet bluetoothd[890]: 
src/agent.c:agent_request_confirmation() Calling Agent.RequestConfirmation: 
name=:1.119, path=/com/canonical/SettingsBluetoothAgent/adapteragent, 
passkey=800772

I expected bluez to call DisplayPasskey here rather than
RequestConfirmation. So what settings displays is correct (in terms of
what it was asked for).

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

Title:
  [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt

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

Bug description:
  Connecting to the latest generation Apple BT keyboard ( the one with
  the USB port & no batteries ) fails on an Ubuntu Touch device, as when
  you press the "Connect" button on the device page, a dialog titled
  "Bluetooth Pairing Request" is displayed, with the following text:

  Please confirm that the PIN displayed on 'Magic Keyboard' matches this
  one: XX

  The dialog has "Cancel" and "Confirm PIN" buttons.

  The keyboard has no display on which a PIN could be displayed.

  When using other devices ( Ubuntu Desktop 15.10, 16.04, Android, OS X,
  ... ) to connect this keyboard all that's necessary is to click/press
  the 'Connect' button in the appropriate place, and the keyboard
  automatically connects, and is usable with no other actions required
  from the user.

  Reproduced on krillin ( rc-proposed/bq-aquris.en/270 ) which has bluez
  5.36-0ubuntu2~overlay1 installed.

  Reproduced on arale ( rc-proposed/meizu.en/258 ) which has bluez 5.37
  installed from silo 39.

  Note, after dismissing the dialog, subsequent attempts to connect may
  not re-display the PIN dialog, instead nothing happens.  I've found
  that this requires power cycling the keyboard to clear and cause the
  PIN dialog to be displayed again.

  [bluetooth]# show
  Controller B8:64:91:48:2B:1E
Name: Aquaris E4.5 Ubuntu Edition
Alias: Aquaris E4.5 Ubuntu Edition
Class: 0x1c020c
Powered: yes
Discoverable: no
Pairable: yes
UUID: Headset AG(1112--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb)
UUID: Phonebook Access Server   (112f--1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0525
Discovering: no

  [bluetooth]# devices
  Device 18:EE:69:21:6C:D3 18-EE-69-21-6C-D3
  Device DE:76:E2:04:9D:6F BB-9D6F
  Device 7C:D1:C3:1C:B4:03 7C-D1-C3-1C-B4-03
  Device 7C:D1:C3:19:2B:D8 7C-D1-C3-19-2B-D8
  Device 84:38:35:67:0C:3D ubuntu-0
  Device 04:69:F8:C2:A0:09 tony espy’s Keyboard
  Device 00:21:3C:A0:14:A6 Jawbone ERA
  Device 1C:1A:C0:B2:9A:D7 1C-1A-C0-B2-9A-D7

  Device info *before* pairing attempt:

  Device 04:69:F8:C2:A0:09
Name: tony espy’s Keyboard
Alias: tony espy’s Keyboard
Class: 0x002540
Icon: input-keyboard
Paired: no
Trusted: no
Blocked: no
Connected: no
LegacyPairing: no
Modalias: bluetooth:v004Cp0267d0066

  No changes in any of the attributes after *after* the pairing attempt
  ( output of info command is the same ).

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551858/+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 1551858] Re: [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt

Because what pairing method is selected is chosen further down the stack
so settings only reacts on what bluez tells it should do. I suspect the
keyboard uses pairing capability KeyboardOnly which then should lead to
passkey entry where the initiator displays and the responder inputs the
PIN (we use KeyboardDisplay) [see Core spec 4.0 page 1968].

However the described dialog on your side is incorrect as it just asks
the user to confirm or cancel which could still be an settings app issue
just displaying the dialog but also an issue down the stack.

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

Title:
  [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt

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

Bug description:
  Connecting to the latest generation Apple BT keyboard ( the one with
  the USB port & no batteries ) fails on an Ubuntu Touch device, as when
  you press the "Connect" button on the device page, a dialog titled
  "Bluetooth Pairing Request" is displayed, with the following text:

  Please confirm that the PIN displayed on 'Magic Keyboard' matches this
  one: XX

  The dialog has "Cancel" and "Confirm PIN" buttons.

  The keyboard has no display on which a PIN could be displayed.

  When using other devices ( Ubuntu Desktop 15.10, 16.04, Android, OS X,
  ... ) to connect this keyboard all that's necessary is to click/press
  the 'Connect' button in the appropriate place, and the keyboard
  automatically connects, and is usable with no other actions required
  from the user.

  Reproduced on krillin ( rc-proposed/bq-aquris.en/270 ) which has bluez
  5.36-0ubuntu2~overlay1 installed.

  Reproduced on arale ( rc-proposed/meizu.en/258 ) which has bluez 5.37
  installed from silo 39.

  Note, after dismissing the dialog, subsequent attempts to connect may
  not re-display the PIN dialog, instead nothing happens.  I've found
  that this requires power cycling the keyboard to clear and cause the
  PIN dialog to be displayed again.

  [bluetooth]# show
  Controller B8:64:91:48:2B:1E
Name: Aquaris E4.5 Ubuntu Edition
Alias: Aquaris E4.5 Ubuntu Edition
Class: 0x1c020c
Powered: yes
Discoverable: no
Pairable: yes
UUID: Headset AG(1112--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb)
UUID: Phonebook Access Server   (112f--1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0525
Discovering: no

  [bluetooth]# devices
  Device 18:EE:69:21:6C:D3 18-EE-69-21-6C-D3
  Device DE:76:E2:04:9D:6F BB-9D6F
  Device 7C:D1:C3:1C:B4:03 7C-D1-C3-1C-B4-03
  Device 7C:D1:C3:19:2B:D8 7C-D1-C3-19-2B-D8
  Device 84:38:35:67:0C:3D ubuntu-0
  Device 04:69:F8:C2:A0:09 tony espy’s Keyboard
  Device 00:21:3C:A0:14:A6 Jawbone ERA
  Device 1C:1A:C0:B2:9A:D7 1C-1A-C0-B2-9A-D7

  Device info *before* pairing attempt:

  Device 04:69:F8:C2:A0:09
Name: tony espy’s Keyboard
Alias: tony espy’s Keyboard
Class: 0x002540
Icon: input-keyboard
Paired: no
Trusted: no
Blocked: no
Connected: no
LegacyPairing: no
Modalias: bluetooth:v004Cp0267d0066

  No changes in any of the attributes after *after* the pairing attempt
  ( output of info command is the same ).

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551858/+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 1554244] Re: Switching cameras requires web page reload in webbrowser-app, not available in webapp-container

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

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

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

Title:
  Switching cameras requires web page reload in webbrowser-app, not
  available in webapp-container

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  When a web site uses WebRTC for video conferencing the webbrowser-app
  accesses the rear camera by default. The user can switch cameras via
  Settings -> Privacy & Permissions -> Camera & Microphone.
  Unfortunately, changing this setting doesn't immediately have effect
  on the open web page. You have to reload the page first, which is not
  intuitive.

  Tested with bq Aquaris E5 Ubuntu Edition, OTA-9.1 (vegeta).

  Additional question: How can switching cameras be handled in web apps
  (driven by the webapp-container binary)? The webapp-container does
  neither provide a feature to specify a (different) default camera nor
  an interactive possibility to do so. An API call to switch cameras
  would be awesome.

  Expected Behavior
  -

  - Switching cameras via the settings immediately has effect on the camera 
used by web sites open in the webbrowser-app.
  - Specifying a default camera (startup settings) is available with the 
webapp-container binary.
  - Switching cameras programmatically (via an API call) and/or interactively 
is possible in web apps driven by the webapp-container.

  How to Reproduce
  

  1.) Go to e.g. https://appear.in/test-drive on your Ubuntu phone (default 
webbrowser-app)
  2.) When prompted for "Allow this domain access the camera and microphone" 
choose "Yes"
  3.) Click away the chat window (touch the down-arrow at right lower corner)
  4.) Touch the screen to dismiss the "help text" (the video captured by the 
rear camera is shown)
  5.) In the browser address bar got to Menu -> Settings -> Privacy & 
Permissions -> Camera & Microphone, and switch to the front camera; go out of 
the menu going back the hierarchy; the rear camera video is still shown
  6.) Tap the address bar, tap on the "Reload" icon to reload the page; the 
front camera video is finally shown

  Other Details
  -

  - https://github.com/bittner/appear-in/issues/1 (conversation
  demonstrating users are confused about browser behavior)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1554244/+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] [NEW] Mouse left click stops working

2016-03-07 Thread Petteri Kähärä

Public bug reported:

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

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


** Tags: amd64 apport-bug third-party-packages trusty ubuntu

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

Title:
  Mouse left click stops working

Status in xorg package in Ubuntu:
  New

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

[Touch-packages] [Bug 1554335] [NEW] Mouse auto select text in some windows

2016-03-07 Thread Otavio

Public bug reported:

The bug occurs when the touchpad is disabled.

Some windows (Like Atom or Ubuntu Software Center or Configuration),
when i move the mouse, it select the text automatic, without holding.


enabling and clicking with touchpad, solve the problem until next restart.

Has a video in attachment explaining.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3
Uname: Linux 4.2.0-30-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.19
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 Mar  8 00:58:31 2016
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:0643]
   Subsystem: Dell Device [1028:0643]
InstallationDate: Installed on 2016-03-08 (0 days ago)
InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1)
MachineType: Dell Inc. Inspiron 5548
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic.efi.signed 
root=UUID=a88bc94f-0a36-47ff-8388-5e458dbe7800 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/15/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A04
dmi.board.name: 0YDTG3
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A04
dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd05/15/2015:svnDellInc.:pnInspiron5548:pvrA04:rvnDellInc.:rn0YDTG3:rvrA00:cvnDellInc.:ct8:cvrA04:
dmi.product.name: Inspiron 5548
dmi.product.version: A04
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Tue Mar  8 00:54:36 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id4333 
 vendor AUO
xserver.version: 2:1.17.2-1ubuntu9.1~trusty1

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


** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu

** Attachment added: "bug.mkv"
   https://bugs.launchpad.net/bugs/1554335/+attachment/4592197/+files/bug.mkv

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

Title:
  Mouse auto select text in some windows

Status in xorg package in Ubuntu:
  New

Bug description:
  The bug occurs when the touchpad is disabled.

  Some windows (Like Atom or Ubuntu Software Center or Configuration),
  when i move the mouse, it select the text automatic, without holding.

  
  enabling and clicking with touchpad, solve the problem until next restart.

  Has a video in attachment explaining.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.19
  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 Mar  8 00:58:31 2016
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0643]
 Subsystem: Dell Device [1028:0643]
  InstallationDate: Installed on 2016-03-08 (0 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  MachineType: Dell Inc. Inspiron 5548
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic.efi.signed 
root=UUID=a88bc94f-0a36-47ff-8388-5e458dbe7800 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No

[Touch-packages] [Bug 1481832] Re: VA-API implementation for gallium missing

2016-03-07 Thread RussianNeuroMancer

Oibaf, you mean there is native VA-API implementation via
gallium_drv_video.so, not via vdpau-va-driver package?

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

Title:
  VA-API implementation for gallium missing

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  [needs-packaging] mesa
  Please include "gallium_drv_video.so" which is a native va-api state tracker 
for mesa(gallium).

  URL: http://mesa3d.sourceforge.net/
  URL: http://freedesktop.org/wiki/Software/vaapi/ #intel/vdpau
  License: http://www.mesa3d.org/license.html

  Notes:
  Currently (as of today) in ubuntu 15.10 nightly amd64, va-api(vaapi) on 
AMD/Ati radeon opensource display hardware is using a vdpau backend  0.7.4 by 
Splitted-Desktop Systems (wrapper) on gallium r600. Although its possible and 
probably preferred (better performance less copying) to use a native 
implementation which mesa(gallium) 10.4 and higher delivers in a form of a 
va-api state tracker.

  vainfo #current default setup vdpau backend
  libva info: VA-API version 0.38.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/r600_drv_video.so
  libva info: Found init function __vaDriverInit_0_37
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 0.38 (libva 1.6.0)
  vainfo: Driver version: Splitted-Desktop Systems VDPAU backend for VA-API - 
0.7.4
  vainfo: Supported profile and entrypoints
    VAProfileMPEG2Simple:   VAEntrypointVLD
    VAProfileMPEG2Main  :   VAEntrypointVLD
    VAProfileMPEG4Simple:   VAEntrypointVLD
    VAProfileMPEG4AdvancedSimple:   VAEntrypointVLD
    VAProfileH264Baseline   :   VAEntrypointVLD
    VAProfileH264Main   :   VAEntrypointVLD
    VAProfileH264High   :   VAEntrypointVLD
    VAProfileVC1Advanced:   VAEntrypointVLD

  The preferred setup needs that "gallium_drv_video.so" binary which is
  currently unavailable in ubuntu and debian. As an example I added a
  package/binary from archlinux. Copying the gallium_drv_video.so to
  /usr/lib/x86_64-linux-gnu/dri/ and symlinking(correcting) the
  libLLVM-3.6.so to arch-linux default /usr/lib/ location and exporting
  a variable was enough to make it work!
  https://www.archlinux.org/packages/extra/x86_64/libva-mesa-driver/
  #example by archlinux

  export LIBVA_DRIVER_NAME=gallium
  vainfo #preferred setup using gallium va-api from arch-linux (symlinked 
libLLVM-3.6.so to /usr/lib)
  libva info: VA-API version 0.38.0
  libva info: va_getDriverName() returns 0
  libva info: User requested driver 'gallium'
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/gallium_drv_video.so
  libva info: Found init function __vaDriverInit_0_38
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 0.38 (libva 1.6.0)
  vainfo: Driver version: mesa gallium vaapi
  vainfo: Supported profile and entrypoints
    VAProfileMPEG2Simple:   VAEntrypointVLD
    VAProfileMPEG2Main  :   VAEntrypointVLD
    VAProfileMPEG4Simple:   VAEntrypointVLD
    VAProfileMPEG4AdvancedSimple:   VAEntrypointVLD
    VAProfileVC1Advanced:   VAEntrypointVLD
    VAProfileH264Baseline   :   VAEntrypointVLD
    VAProfileH264Main   :   VAEntrypointVLD
    VAProfileH264High   :   VAEntrypointVLD

  I guess this binary "gallium_drv_video.so" might be available as a
  compile flag in the current mesa implementation... intel and vdpau has
  their own current implementation in a separate libva branch
  http://cgit.freedesktop.org/vaapi/libva/ ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1481832/+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 1311368] Re: Won't install on precise (over ssh), blocking installation of ia32-libs

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

Title:
  Won't install on precise (over ssh), blocking installation of
  ia32-libs

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  bluez package fails to install via apt-get, which prevents me from
  installing ia32-libs, on precise.  Running over ssh, not sure if that
  could be relevant.  I'm not interested in using the bluez package at
  all, this is a server.

  # apt-get install bluez
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following NEW packages will be installed:
bluez
  0 upgraded, 1 newly installed, 0 to remove and 39 not upgraded.
  Need to get 0 B/969 kB of archives.
  After this operation, 2,525 kB of additional disk space will be used.
  Selecting previously unselected package bluez.
  (Reading database ... 89815 files and directories currently installed.)
  Unpacking bluez (from .../bluez_4.98-2ubuntu7.1_amd64.deb) ...
  Processing triggers for man-db ...
  Processing triggers for ureadahead ...
  Setting up bluez (4.98-2ubuntu7.1) ...
  reload: Unknown instance: 
  invoke-rc.d: initscript dbus, action "force-reload" failed.
  start: Job failed to start
  invoke-rc.d: initscript bluetooth, action "start" failed.
  dpkg: error processing bluez (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   bluez
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  
  # apt-get install ia32-libs
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following extra packages will be installed:
bluez bluez-alsa:i386 ia32-libs-multiarch:i386
  Suggested packages:
libpam-ldap:i386 libpam-winbind:i386 libnss-ldap:i386
  The following NEW packages will be installed:
bluez bluez-alsa:i386 ia32-libs ia32-libs-multiarch:i386
  0 upgraded, 4 newly installed, 0 to remove and 39 not upgraded.
  Need to get 0 B/1,111 kB of archives.
  After this operation, 2,987 kB of additional disk space will be used.
  Do you want to continue [Y/n]? 
  Selecting previously unselected package bluez.
  (Reading database ... 89815 files and directories currently installed.)
  Unpacking bluez (from .../bluez_4.98-2ubuntu7.1_amd64.deb) ...
  Selecting previously unselected package bluez-alsa:i386.
  Unpacking bluez-alsa:i386 (from .../bluez-alsa_4.98-2ubuntu7.1_i386.deb) ...
  Selecting previously unselected package ia32-libs-multiarch:i386.
  Unpacking ia32-libs-multiarch:i386 (from 
.../ia32-libs-multiarch_20090808ubuntu36_i386.deb) ...
  Selecting previously unselected package ia32-libs.
  Unpacking ia32-libs (from .../ia32-libs_20090808ubuntu36_amd64.deb) ...
  Processing triggers for man-db ...
  Processing triggers for ureadahead ...
  Setting up bluez (4.98-2ubuntu7.1) ...
  reload: Unknown instance: 
  invoke-rc.d: initscript dbus, action "force-reload" failed.
  start: Job failed to start
  invoke-rc.d: initscript bluetooth, action "start" failed.
  dpkg: error processing bluez (--configure):
   subprocess installed post-installation script returned error exit status 1
  dpkg: dependency problems prevent configuration of bluez-alsa:i386:
   bluez-alsa:i386 depends on bluez; however:
Package bluez is not configured yet.
  dpkg: error processing bluez-alsa:i386 (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of ia32-libs-multiarch:i386:
   ia32-libs-multiarch:i386 depends on bluez-alsa; however:
Package bluez-alsa:i386 is not configured yet.
  dpkg: error processing ia32-libs-multiarch:i386 (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of ia32-libs:
   ia32-libs depends on ia32-libs-multiarch; however:
Package ia32-libs-multiarch is not installed.
Package ia32-libs-multiarch:i386 is not configured yet.
  dpkg: error processing ia32-libs (--configure):
   dependency problems - leaving unconfigured
  No apport report written because the error message indicates its a followup 
error from a previous failure.

Errors were encountered while processing:
   bluez
   bluez-alsa:i386
   ia32-libs-multiarch:i386
   ia32-libs
  E: Sub-process /usr/bin/dpkg returned an error code (1)

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

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

[Touch-packages] [Bug 1381483] Re: Desktop sharing display frozen

L-Train, it will help immensely if you filed a new report with Ubuntu by 
ensuring you have the package xdiagnose installed, and that you click the Yes 
button for attaching additional debugging information running the following 
from a terminal:
ubuntu-bug xorg

Also, please feel free to subscribe me to it.

For more on why this is helpful, please see
https://wiki.ubuntu.com/ReportingBugs.

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

Title:
  Desktop sharing display frozen

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I can connect to a 14.10 desktop, but the update of the display is
  frozen in the VNC client. I see the desktop, with launcher and panel,
  but the time is stuck. Clicking on an app in the launcher does start
  the app, but the app does not appear on the VNC client screen. This
  happens when logging in using either Remmina on Ubuntu 14.04 on
  UltraVNC from a Windows 8.1 PC. Someone reported in the forums that
  this also happens when using x11vnc.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4
  Uname: Linux 3.16.0-22-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.7-0ubuntu6
  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: Wed Oct 15 12:41:01 2014
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller])
     Subsystem: Elitegroup Computer Systems Device [1019:903a]
     Subsystem: Elitegroup Computer Systems Device [1019:903a]
  InstallationDate: Installed on 2014-10-11 (3 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141011)
  MachineType: DIXONSXP DIXONSXP
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-22-generic 
root=UUID=8b9c4b4b-0d6b-4ae2-89cd-504d7a77e096 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2007
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 1.00DIX
  dmi.board.name: DIXONSXP
  dmi.board.vendor: DIXONSXP
  dmi.chassis.type: 10
  dmi.chassis.vendor: DIXONSXP
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr1.00DIX:bd08/31/2007:svnDIXONSXP:pnDIXONSXP:pvr:rvnDIXONSXP:rnDIXONSXP:rvr:cvnDIXONSXP:ct10:cvr:
  dmi.product.name: DIXONSXP
  dmi.sys.vendor: DIXONSXP
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
  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.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Wed Oct 15 12:03:23 2014
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id8564
   vendor AUO
  xserver.version: 2:1.16.0-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1381483/+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 1374759] Re: >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old

2016-03-07 Thread Thiago Martins

I'm seeing this BUG on most recent Xenial Beta release (updated today).

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

Title:
  >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is
  ufstype=old

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Triaged
Status in os-prober package in Ubuntu:
  Confirmed
Status in os-prober package in Debian:
  Fix Released

Bug description:
  [  556.734157] SGI XFS with ACLs, security attributes, realtime, large 
block/inode numbers, no debug enabled
  [  556.746268] JFS: nTxBlock = 8192, nTxLock = 65536
  [  556.763789] ntfs: driver 2.1.30 [Flags: R/O MODULE].
  [  556.792231] QNX4 filesystem 0.2.3 registered.
  [  557.922469] EXT4-fs (sda4): unable to read superblock
  [  557.925868] EXT4-fs (sda4): unable to read superblock
  [  557.928967] EXT4-fs (sda4): unable to read superblock
  [  557.931784] FAT-fs (sda4): bogus number of reserved sectors
  [  557.931791] FAT-fs (sda4): Can't find a valid FAT filesystem
  [  557.946740] XFS (sda4): Invalid superblock magic number
  [  557.951904] FAT-fs (sda4): bogus number of reserved sectors
  [  557.951911] FAT-fs (sda4): Can't find a valid FAT filesystem
  [  557.959099] MINIX-fs: unable to read superblock
  [  557.965712] attempt to access beyond end of device
  [  557.965721] sda4: rw=16, want=3, limit=2
  [  557.965725] hfsplus: unable to find HFS+ superblock
  [  557.968487] qnx4: no qnx4 filesystem (no root dir).
  [  557.971203] You didn't specify the type of your ufs filesystem

  mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep
  |nextstep-cd|openstep ...

  >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is 
ufstype=old
  [  557.974459] hfs: can't find a HFS filesystem on dev sda4
  [  564.034208] EXT4-fs (sda4): unable to read superblock
  [  564.040322] EXT4-fs (sda4): unable to read superblock
  [  564.043485] EXT4-fs (sda4): unable to read superblock
  [  564.047076] FAT-fs (sda4): bogus number of reserved sectors
  [  564.047083] FAT-fs (sda4): Can't find a valid FAT filesystem
  [  564.059578] XFS (sda4): Invalid superblock magic number
  [  564.064473] FAT-fs (sda4): bogus number of reserved sectors
  [  564.064489] FAT-fs (sda4): Can't find a valid FAT filesystem
  [  564.072080] MINIX-fs: unable to read superblock
  [  564.074564] attempt to access beyond end of device
  [  564.074571] sda4: rw=16, want=3, limit=2
  [  564.074576] hfsplus: unable to find HFS+ superblock
  [  564.076688] qnx4: no qnx4 filesystem (no root dir).
  [  564.078847] You didn't specify the type of your ufs filesystem

  mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep
  |nextstep-cd|openstep ...

  >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is 
ufstype=old
  [  564.080902] hfs: can't find a HFS filesystem on dev sda4
  [  570.554296] EXT4-fs (sda4): unable to read superblock
  [  570.557647] EXT4-fs (sda4): unable to read superblock
  [  570.560516] EXT4-fs (sda4): unable to read superblock
  [  570.563451] FAT-fs (sda4): bogus number of reserved sectors
  [  570.563460] FAT-fs (sda4): Can't find a valid FAT filesystem
  [  570.574953] XFS (sda4): Invalid superblock magic number
  [  570.580796] FAT-fs (sda4): bogus number of reserved sectors
  [  570.580806] FAT-fs (sda4): Can't find a valid FAT filesystem
  [  570.588340] MINIX-fs: unable to read superblock
  [  570.590983] attempt to access beyond end of device
  [  570.590993] sda4: rw=16, want=3, limit=2
  [  570.590999] hfsplus: unable to find HFS+ superblock
  [  570.593321] qnx4: no qnx4 filesystem (no root dir).
  [  570.595556] You didn't specify the type of your ufs filesystem

  mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep
  |nextstep-cd|openstep ...

  >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is 
ufstype=old
  [  570.597775] hfs: can't find a HFS filesystem on dev sda4
  [  576.795014] EXT4-fs (sda4): unable to read superblock
  [  576.797554] EXT4-fs (sda4): unable to read superblock
  [  576.800063] EXT4-fs (sda4): unable to read superblock
  [  576.802647] FAT-fs (sda4): bogus number of reserved sectors
  [  576.802655] FAT-fs (sda4): Can't find a valid FAT filesystem
  [  576.813305] XFS (sda4): Invalid superblock magic number
  [  576.820257] FAT-fs (sda4): bogus number of reserved sectors
  [  576.820276] FAT-fs (sda4): Can't find a valid FAT filesystem
  [  576.830945] MINIX-fs: unable to read superblock
  [  576.834108] attempt to access beyond end of device
  [  576.834119] sda4: rw=16, want=3, limit=2
  [  576.834125] hfsplus: unable to find HFS+ superblock
  [  576.837264] qnx4: no qnx4 filesystem (no root dir).
  [  576.840408] You didn't specify the type of your ufs filesystem

  mount -t ufs -o

Re: [Touch-packages] [Bug 1543697] Re: Unprivileged nested Xenial container will not start inside a privileged Xenial container

2016-03-07 Thread Serge Hallyn

this should be fixed by the fix to bug 1554269.

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

Title:
  Unprivileged nested Xenial container will not start inside a
  privileged Xenial container

Status in lxc package in Ubuntu:
  Fix Released

Bug description:
  I have a host where I create a privileged Xenial container.  Inside
  that privileged container, I create an unprivileged Xenial container
  using the ubuntu user in the privileged container.  When I try
  starting the unprivileged container, I get the following error:

    lxc-start 20160209133200.970 INFO lxc_cgroup - 
cgroup.c:cgroup_init:65 - cgroup driver cgroupfs initing for test-lxc
    lxc-start 20160209133200.971 ERRORlxc_cgfs - cgfs.c:cgfs_init:2248 
- cgroupfs failed to detect cgroup metadata
    lxc-start 20160209133200.971 ERRORlxc_start - 
start.c:lxc_spawn:1023 - failed initializing cgroup support
    lxc-start 20160209133200.971 ERRORlxc_start - 
start.c:__lxc_start:1273 - failed to spawn 'test-lxc'

  I've tried both Trusty host w/ ppa:ubuntu-lxc/lxc-stable installed and
  a Xenial host with the same results.   I've also tried using ppa
  :ubuntu-lxc/daily in the privileged Xenial LXC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1543697/+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 1549841] Re: Change display settings to use two monitors on Ubuntu 14.04 with HP notebook nx6325

2016-03-07 Thread BrOne

Unfortunately on my notebook nx6325 I have only installed Ubuntu, I
don't have a dual boot with Windows. Then I do not have to update the
BIOS because the update program (.exe.) only runs on Windows.

By the way, this problem didn't exist in version 12.04.03 . It appeared
after upgrade to the version 14.04.03. In 12.04.03 version I could see
both monitors with the corresponding resolution (1360 x 768 (16: 9) for
my AOC monitor and 1024 x 768 (4: 3) for the notebook monitor).

Therefore, I think it should not be a problem for updating the BIOS.

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

Title:
  Change display settings to use two monitors on Ubuntu 14.04 with HP
  notebook nx6325

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I upgraded from 12.04.03 to 14.04.03. After the update both monitors
  can only be configured 1024 x 768 (4: 3). If I change the display
  settings for the second monitor, just as it had in 12.04: 1360 x 768
  (16: 9) Ubuntu claim with the following error:

  "No se pudo aplicar la configuración seleccionada para las pantallas

  El tamaño requerido (2384, 768) excede el límite de hardware 3D (2048, 2048).
  Debe reorganizar la pantalla para que quepa dentro de un cuadrado de (2048, 
2048)."

  And later:

  "Fallo al aplicar la configuración: %s

  Se alcanzó el tiempo de expiración"

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-79.123-generic 3.13.11-ckt33
  Uname: Linux 3.13.0-79-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.19
  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: Thu Feb 25 11:28:57 2016
  DistUpgraded: 2016-02-17 20:53:17,451 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   vboxhost, 5.0.14, 3.13.0-74-generic, x86_64: installed
   vboxhost, 5.0.14, 3.13.0-76-generic, x86_64: installed
   vboxhost, 5.0.14, 3.13.0-77-generic, x86_64: installed
   vboxhost, 5.0.14, 3.13.0-79-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS482M [Mobility Radeon Xpress 200] 
[1002:5975] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:30b0]
  InstallationDate: Installed on 2015-12-29 (58 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
  MachineType: Hewlett-Packard HP Compaq nx6325 (RJ361LA#ABM)
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=es_CL:es
   PATH=(custom, no user)
   LANG=es_CL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-79-generic 
root=UUID=b56b4003-70a1-4db5-961a-8a2769426cf1 ro drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2016-02-17 (7 days ago)
  dmi.bios.date: 12/21/2006
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68TT2 Ver. F.06
  dmi.board.name: 30B0
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 40.15
  dmi.chassis.asset.tag: CNU70506VT
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68TT2Ver.F.06:bd12/21/2006:svnHewlett-Packard:pnHPCompaqnx6325(RJ361LA#ABM):pvrF.06:rvnHewlett-Packard:rn30B0:rvrKBCVersion40.15:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP Compaq nx6325 (RJ361LA#ABM)
  dmi.product.version: F.06
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  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.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: Thu Feb 25 11:27:36 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu2.7
  xserver.video_driver: radeon

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post

[Touch-packages] [Bug 1533343] Re: No sound from internal speakers after boot with connected headphones

2016-03-07 Thread Raymond

Pin-ctls: 0x00: --- > 
Pin-ctls: 0x40: OUT 


Driver mute speaker pin complex by set pin ctls to 0 instead of OUT

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

Title:
  No sound from internal speakers after boot with connected headphones

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On Lenovo L450 laptop, when I boot the PC with headphones attached,
  then the sound via headphones will work, but there will be no sound
  from internal speakers when headphones are detached.

  I tested this couple of times and the problem is always reproduced.
  This is the procedure A:

  1. When the problem is not present, sound is present in laptop's speakers, 
connect the headphones
  2. initiate reboot
  3. once booted, initiate playing of some audio and check the sound from 
headphones - it will work OK
  4. disconnect the headphones - there is no sound from internal speakers

  Procedure B:
  1. turn off the laptop (power off)
  2. connect the headphones to the laptop
  3. power on the laptop and boot into Ubuntu 15.10
  4. once booted, initiate playing of some audio and check the sound from 
headphones - it will work OK
  5. disconnect the headphones - there is no sound from internal speakers

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6
  Uname: Linux 4.2.0-23-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ygzo   2125 F pulseaudio
   /dev/snd/controlC0:  ygzo   2125 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jan 12 20:44:49 2016
  InstallationDate: Installed on 2015-10-05 (99 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_Type: Only some of outputs are working
  Title: [20DT0003XS, Realtek ALC3232, Speaker, Internal] Playback problem
  UpgradeStatus: Upgraded to wily on 2015-11-03 (70 days ago)
  dmi.bios.date: 08/19/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JDET54WW (1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: Intel powered classmate PC
  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:bvrJDET54WW(1.16):bd08/19/2015:svnLENOVO:pn20DT0003XS:pvrThinkPadL450:rvnLENOVO:rnIntelpoweredclassmatePC:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20DT0003XS
  dmi.product.version: ThinkPad L450
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1533343/+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 1381483] Re: Desktop sharing display frozen

2016-03-07 Thread L-Train

This is still happening even in Ubuntu 15.10

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

Title:
  Desktop sharing display frozen

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I can connect to a 14.10 desktop, but the update of the display is
  frozen in the VNC client. I see the desktop, with launcher and panel,
  but the time is stuck. Clicking on an app in the launcher does start
  the app, but the app does not appear on the VNC client screen. This
  happens when logging in using either Remmina on Ubuntu 14.04 on
  UltraVNC from a Windows 8.1 PC. Someone reported in the forums that
  this also happens when using x11vnc.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4
  Uname: Linux 3.16.0-22-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.7-0ubuntu6
  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: Wed Oct 15 12:41:01 2014
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller])
     Subsystem: Elitegroup Computer Systems Device [1019:903a]
     Subsystem: Elitegroup Computer Systems Device [1019:903a]
  InstallationDate: Installed on 2014-10-11 (3 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141011)
  MachineType: DIXONSXP DIXONSXP
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-22-generic 
root=UUID=8b9c4b4b-0d6b-4ae2-89cd-504d7a77e096 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2007
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 1.00DIX
  dmi.board.name: DIXONSXP
  dmi.board.vendor: DIXONSXP
  dmi.chassis.type: 10
  dmi.chassis.vendor: DIXONSXP
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr1.00DIX:bd08/31/2007:svnDIXONSXP:pnDIXONSXP:pvr:rvnDIXONSXP:rnDIXONSXP:rvr:cvnDIXONSXP:ct10:cvr:
  dmi.product.name: DIXONSXP
  dmi.sys.vendor: DIXONSXP
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
  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.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Wed Oct 15 12:03:23 2014
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id8564
   vendor AUO
  xserver.version: 2:1.16.0-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1381483/+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 1554223] Re: apt-get update fails with "Unable to find expected entry 'main/binary-i386/Packages' in Release file" on pure x86_64 repos

2016-03-07 Thread Dan Kegel

Chrome's going to fix it on their end,
https://bugs.chromium.org/p/chromium/issues/detail?id=591480

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

Title:
  apt-get update fails with "Unable to find expected entry
  'main/binary-i386/Packages' in Release file" on pure x86_64 repos

Status in apt package in Ubuntu:
  New

Bug description:
  (ubuntu-bug wouldn't let me report bugs against apt, go figure.)

  I run my own apt repo for a third-party app, and I have to include a
  dummy i386 package to avoid an error from apt-get.

  Along comes Chrome's decision to desupport i386, and suddenly this problem 
matters to a lot of people,
  who are all seeing apt-get update fail with:

  W: Failed to fetch http://dl.google.com/linux/chrome/deb/dists/stable/Release 
 Unable to find expected entry 'main/binary-i386/Packages' in Release file 
(Wrong sources.list entry or malformed file)
  E: Some index files failed to download. They have been ignored, or old ones 
used instead.

  While it would be easy for Google to include a dummy i386 package in
  their repo, it would be even better if apt-get didn't barf like this
  on pure 64 bit repos.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1554223/+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 1550137] Re: Crash loop with rc-proposed build 375

2016-03-07 Thread Michi Henning

After downgrading to r375 (mako, rc-proposed), I'm getting the crash
loop again. Rebooting fixes the problem.

I then upgraded to r382, and the problem is gone. Whatever this was, it
looks like it's gone away.

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

Title:
  Crash loop with rc-proposed build 375

Status in unity-scopes-shell package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  I just flashed 375 from rc-proposed. After the reboot, the shell is
  stuck in a crash loop. After unlocking, the shell briefly appears with
  the main click scope page showing and the activity bar at the bottom
  bouncing left/right. Then the crash, back to the spinner in the center
  of the screen ("Scope"), back to the main page, bottom bar bouncing,
  crash, ad infinitum.

  Crash dump attached.

  After rebooting, the crash loop stopped.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1550137/+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 1554202] Re: [webapp-container] No access to video provided despite policy_group "camera" in .apparmour file

2016-03-07 Thread Alexandre Abreu

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

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

Title:
  [webapp-container] No access to video provided despite policy_group
  "camera" in .apparmour file

Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  A web app that displays a website trying to access camera and
  microphone (for video conferencing, using WebRTC) will be refused to
  access the camera despite the "camera" policy_group in apparmour.

  The trust-store dialog pops up in the webbrowser-app for a website
  such as [1], but it doesn't pop up when the website is embedded with
  webapp-container.

  [1] https://appear.in/test-drive

  Details
  ---

  - Detailed explanations on the mailing list: 
https://lists.launchpad.net/ubuntu-phone/msg18658.html
  - Affected web app (Store): 
https://uappexplorer.com/app/appear-in.peter-bittner
  - Affected web app (rev 2): 
https://myapps.developer.ubuntu.com/dev/click-apps/4646/rev/2/
  - Bug report for affected app: https://github.com/bittner/appear-in/issues/1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1554202/+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 1543697] Re: Unprivileged nested Xenial container will not start inside a privileged Xenial container

2016-03-07 Thread Serge Hallyn

Hi - there should be a way, we just need to get sudo running the pam
module.

Perhaps libpam-cgfs should be added to /etc/pam.d/common-session-
noninteractive.

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

Title:
  Unprivileged nested Xenial container will not start inside a
  privileged Xenial container

Status in lxc package in Ubuntu:
  Fix Released

Bug description:
  I have a host where I create a privileged Xenial container.  Inside
  that privileged container, I create an unprivileged Xenial container
  using the ubuntu user in the privileged container.  When I try
  starting the unprivileged container, I get the following error:

    lxc-start 20160209133200.970 INFO lxc_cgroup - 
cgroup.c:cgroup_init:65 - cgroup driver cgroupfs initing for test-lxc
    lxc-start 20160209133200.971 ERRORlxc_cgfs - cgfs.c:cgfs_init:2248 
- cgroupfs failed to detect cgroup metadata
    lxc-start 20160209133200.971 ERRORlxc_start - 
start.c:lxc_spawn:1023 - failed initializing cgroup support
    lxc-start 20160209133200.971 ERRORlxc_start - 
start.c:__lxc_start:1273 - failed to spawn 'test-lxc'

  I've tried both Trusty host w/ ppa:ubuntu-lxc/lxc-stable installed and
  a Xenial host with the same results.   I've also tried using ppa
  :ubuntu-lxc/daily in the privileged Xenial LXC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1543697/+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 1552082] Re: String settings with special characters become quoted

2016-03-07 Thread Brian Douglass

Thanks for the update and the suggestion. I'll have to implement
something like that.

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

Title:
  String settings with special characters become quoted

Status in unity-js-scopes:
  Invalid
Status in unity-api package in Ubuntu:
  In Progress
Status in unity-scopes-shell package in Ubuntu:
  In Progress

Bug description:
  I'm unsure if this is a bug in the JS scopes or in scopes themselves,
  but a string setting that has special characters entered into it (like
  `=`) end up being surrounded by quotes when pulled in the code. For
  example I have a string setting that I entered `abc=abc`, the result
  in the code is `"abc=abc"`. I find this behavior to be very odd and
  unexpected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-js-scopes/+bug/1552082/+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 1554265] Re: NetworkManager crashed with SIGSEGV in nm_device_uses_assumed_connection()

2016-03-07 Thread Apport retracing service

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1545804, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1554265/+attachment/4591987/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1554265/+attachment/4591989/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1554265/+attachment/4591998/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1554265/+attachment/4591999/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1554265/+attachment/4592000/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1554265/+attachment/4592001/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1554265/+attachment/4592002/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1545804

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  NetworkManager crashed with SIGSEGV in
  nm_device_uses_assumed_connection()

Status in network-manager package in Ubuntu:
  New

Bug description:
  I dont know

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.0.4-0ubuntu10
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  Date: Mon Mar  7 19:41:52 2016
  ExecutablePath: /usr/sbin/NetworkManager
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-03-06 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  IpRoute:
   default via 192.168.178.1 dev wlx74ea3a8e3b2d  proto static  metric 600 
   169.254.0.0/16 dev wlx74ea3a8e3b2d  scope link  metric 1000 
   192.168.178.0/24 dev wlx74ea3a8e3b2d  proto kernel  scope link  src 
192.168.178.23  metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcCmdline: /usr/sbin/NetworkManager --no-daemon
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SegvAnalysis:
   Segfault happened at: 0x44cc19 :   
cmpq   $0x0,0x108(%rbx)
   PC (0x0044cc19) ok
   source "$0x0" ok
   destination "0x108(%rbx)" (0x0108) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: network-manager
  StacktraceTop:
   nm_device_uses_assumed_connection ()
   ?? ()
   ?? () from 
/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-wifi.so
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: NetworkManager crashed with SIGSEGV in 
nm_device_uses_assumed_connection()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH
  CONNECTION   CON-UUID  CON-PATH   

   wlx74ea3a8e3b2d  wifi  connected
/org/freedesktop/NetworkManager/Devices/1  folkiwlan 1  
c1765c93-3c24-4ca0-a3d0-37f9f200a547  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   enp2s0   ethernet  unavailable  
/org/freedesktop/NetworkManager/Devices/2  --   --  
  -- 
   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/1554265/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to

[Touch-packages] [Bug 1554266] [NEW] sshd does not start on newly installed desktop system

2016-03-07 Thread Max Brustkern

Public bug reported:

When I preseed a desktop install using utah for daily iso testing, the
ssh service is not running when it starts up. journalctl -u ssh shows no
entries. If I manually start the ssh service, it seems to work. If I
reboot, sshd is running. On the first boot, however, it is not. This
problem appears to have started on the March 5 image.

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

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

Title:
  sshd does not start on newly installed desktop system

Status in openssh package in Ubuntu:
  New

Bug description:
  When I preseed a desktop install using utah for daily iso testing, the
  ssh service is not running when it starts up. journalctl -u ssh shows
  no entries. If I manually start the ssh service, it seems to work. If
  I reboot, sshd is running. On the first boot, however, it is not. This
  problem appears to have started on the March 5 image.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1554266/+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 1554255] Re: NetworkManager crashed with SIGSEGV in g_closure_invoke()

2016-03-07 Thread Apport retracing service

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1433835, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1554255/+attachment/4591937/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1554255/+attachment/4591939/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1554255/+attachment/4591955/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1554255/+attachment/4591956/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1554255/+attachment/4591957/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1554255/+attachment/4591959/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1554255/+attachment/4591960/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1433835

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  NetworkManager crashed with SIGSEGV in g_closure_invoke()

Status in network-manager package in Ubuntu:
  New

Bug description:
  I got this after resume from suspend.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.0.4-0ubuntu10
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Mon Mar  7 22:57:38 2016
  ExecutablePath: /usr/sbin/NetworkManager
  InstallationDate: Installed on 2011-10-20 (1600 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
   WimaxEnabled=true
  ProcCmdline: /usr/sbin/NetworkManager --no-daemon
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x4cde00:  mov0x0(%r13),%r12
   PC (0x004cde00) ok
   source "0x0(%r13)" (0x32bba0030) not located in a known VMA region 
(needed readable region)!
   destination "%r12" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: network-manager
  StacktraceTop:
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: NetworkManager crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: Upgraded to xenial on 2016-02-26 (10 days ago)
  UserGroups:
   
  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/1554255/+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 1554254] [NEW] /usr/bin/online-accounts-ui:11:strlen:QByteArray::QByteArray:Accounts::Provider::domDocument:OnlineAccountsUi::ApplicationManager::providerInfo:OnlineAccountsUi::P

2016-03-07 Thread errors.ubuntu.com bug bridge

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding ubuntu-system-settings-online-accounts.  This problem was most
recently seen with version 0.7+15.04.20160111-0ubuntu1, the problem page
at
https://errors.ubuntu.com/problem/8f2f8f5d25b7f00989051db7128ed6d2c66995fb
contains more details.

** Affects: ubuntu-system-settings-online-accounts (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: vivid

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

Title:
  /usr/bin/online-accounts-
  
ui:11:strlen:QByteArray::QByteArray:Accounts::Provider::domDocument:OnlineAccountsUi::ApplicationManager::providerInfo:OnlineAccountsUi::ProviderRequestPrivate::start

Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding ubuntu-system-settings-online-accounts.  This problem was
  most recently seen with version 0.7+15.04.20160111-0ubuntu1, the
  problem page at
  https://errors.ubuntu.com/problem/8f2f8f5d25b7f00989051db7128ed6d2c66995fb
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings-online-accounts/+bug/1554254/+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 1554244] Re: Switching cameras requires web page reload in webbrowser-app, not available in webapp-container

** Description changed:

  When a web site uses WebRTC for video conferencing the webbrowser-app
  accesses the rear camera by default. The user can switch cameras via
- Settings -> Privacy & permissions -> Camera & Microphone. Unfortunately,
+ Settings -> Privacy & Permissions -> Camera & Microphone. Unfortunately,
  changing this setting doesn't immediately have effect on the open web
  page. You have to reload the page first, which is not intuitive.
  
- Tested / discovered with bq Aquaris E5 Ubuntu Edition, OTA-9.1 (vegeta,
- latest stable as of today).
+ Tested with bq Aquaris E5 Ubuntu Edition, OTA-9.1 (vegeta).
  
  Additional question: How can switching cameras be handled in web apps
  (driven by the webapp-container binary)? The webapp-container does
  neither provide a feature to specify a (different) default camera nor an
  interactive possibility to do so. An API call to switch cameras would be
  awesome.
  
  Expected Behavior
  -
  
  - Switching cameras via the settings immediately has effect on the camera 
used by web sites open in the webbrowser-app.
  - Specifying a default camera (startup settings) is available with the 
webapp-container binary.
  - Switching cameras programmatically (via an API call) and/or interactively 
is possible in web apps driven by the webapp-container.
  
  How to Reproduce
  
  
  1.) Go to e.g. https://appear.in/test-drive on your Ubuntu phone (default 
webbrowser-app)
  2.) When prompted for "Allow this domain access the camera and microphone" 
choose "Yes"
  3.) Click away the chat window (touch the down-arrow at right lower corner)
  4.) Touch the screen to dismiss the "help text" (the video captured by the 
rear camera is shown)
- 5.) In the browser address bar got to Menu -> Settings -> Privacy & 
permissions -> Camera & Microphone, and switch to the front camera; go out of 
the menu going back the hierarchy; the rear camera video is still shown 
+ 5.) In the browser address bar got to Menu -> Settings -> Privacy & 
Permissions -> Camera & Microphone, and switch to the front camera; go out of 
the menu going back the hierarchy; the rear camera video is still shown
  6.) Tap the address bar, tap on the "Reload" icon to reload the page; the 
front camera video is finally shown
  
  Other Details
  -
  
- - https://github.com/bittner/appear-in/issues/1 (conversion
+ - https://github.com/bittner/appear-in/issues/1 (conversation
  demonstrating users are confused about browser behavior)

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

Title:
  Switching cameras requires web page reload in webbrowser-app, not
  available in webapp-container

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  When a web site uses WebRTC for video conferencing the webbrowser-app
  accesses the rear camera by default. The user can switch cameras via
  Settings -> Privacy & Permissions -> Camera & Microphone.
  Unfortunately, changing this setting doesn't immediately have effect
  on the open web page. You have to reload the page first, which is not
  intuitive.

  Tested with bq Aquaris E5 Ubuntu Edition, OTA-9.1 (vegeta).

  Additional question: How can switching cameras be handled in web apps
  (driven by the webapp-container binary)? The webapp-container does
  neither provide a feature to specify a (different) default camera nor
  an interactive possibility to do so. An API call to switch cameras
  would be awesome.

  Expected Behavior
  -

  - Switching cameras via the settings immediately has effect on the camera 
used by web sites open in the webbrowser-app.
  - Specifying a default camera (startup settings) is available with the 
webapp-container binary.
  - Switching cameras programmatically (via an API call) and/or interactively 
is possible in web apps driven by the webapp-container.

  How to Reproduce
  

  1.) Go to e.g. https://appear.in/test-drive on your Ubuntu phone (default 
webbrowser-app)
  2.) When prompted for "Allow this domain access the camera and microphone" 
choose "Yes"
  3.) Click away the chat window (touch the down-arrow at right lower corner)
  4.) Touch the screen to dismiss the "help text" (the video captured by the 
rear camera is shown)
  5.) In the browser address bar got to Menu -> Settings -> Privacy & 
Permissions -> Camera & Microphone, and switch to the front camera; go out of 
the menu going back the hierarchy; the rear camera video is still shown
  6.) Tap the address bar, tap on the "Reload" icon to reload the page; the 
front camera video is finally shown

  Other Details
  -

  - https://github.com/bittner/appear-in/issues/1 (conversation
  demonstrating users are confused about browser behavior)

To manage notifications about this bug go to:

[Touch-packages] [Bug 1539759] Re: Tab button does not appear when using the new header API

2016-03-07 Thread Tim Peeters

You can use the leadingActionBar.actions now to control the navigation,
and it will look the same as the Tabs used to look. See example 2 on
https://developer.ubuntu.com/en/blog/2016/02/24/pageheader-tutorial/

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

Title:
  Tab button does not appear when using the new header API

Status in Ubuntu UX:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  Incomplete

Bug description:
  Declaring a page with the new header API causes the tab switcher
  button to disappear.

  Check attached example.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1539759/+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 1554244] [NEW] Switching cameras requires web page reload in webbrowser-app, not available in webapp-container

Public bug reported:

When a web site uses WebRTC for video conferencing the webbrowser-app
accesses the rear camera by default. The user can switch cameras via
Settings -> Privacy & permissions -> Camera & Microphone. Unfortunately,
changing this setting doesn't immediately have effect on the open web
page. You have to reload the page first, which is not intuitive.

Tested / discovered with bq Aquaris E5 Ubuntu Edition, OTA-9.1 (vegeta,
latest stable as of today).

Additional question: How can switching cameras be handled in web apps
(driven by the webapp-container binary)? The webapp-container does
neither provide a feature to specify a (different) default camera nor an
interactive possibility to do so. An API call to switch cameras would be
awesome.

Expected Behavior
-

- Switching cameras via the settings immediately has effect on the camera used 
by web sites open in the webbrowser-app.
- Specifying a default camera (startup settings) is available with the 
webapp-container binary.
- Switching cameras programmatically (via an API call) and/or interactively is 
possible in web apps driven by the webapp-container.

How to Reproduce


1.) Go to e.g. https://appear.in/test-drive on your Ubuntu phone (default 
webbrowser-app)
2.) When prompted for "Allow this domain access the camera and microphone" 
choose "Yes"
3.) Click away the chat window (touch the down-arrow at right lower corner)
4.) Touch the screen to dismiss the "help text" (the video captured by the rear 
camera is shown)
5.) In the browser address bar got to Menu -> Settings -> Privacy & permissions 
-> Camera & Microphone, and switch to the front camera; go out of the menu 
going back the hierarchy; the rear camera video is still shown 
6.) Tap the address bar, tap on the "Reload" icon to reload the page; the front 
camera video is finally shown

Other Details
-

- https://github.com/bittner/appear-in/issues/1 (conversion
demonstrating users are confused about browser behavior)

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


** Tags: camera settings usability webapp-container webrtc

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

Title:
  Switching cameras requires web page reload in webbrowser-app, not
  available in webapp-container

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  When a web site uses WebRTC for video conferencing the webbrowser-app
  accesses the rear camera by default. The user can switch cameras via
  Settings -> Privacy & permissions -> Camera & Microphone.
  Unfortunately, changing this setting doesn't immediately have effect
  on the open web page. You have to reload the page first, which is not
  intuitive.

  Tested / discovered with bq Aquaris E5 Ubuntu Edition, OTA-9.1
  (vegeta, latest stable as of today).

  Additional question: How can switching cameras be handled in web apps
  (driven by the webapp-container binary)? The webapp-container does
  neither provide a feature to specify a (different) default camera nor
  an interactive possibility to do so. An API call to switch cameras
  would be awesome.

  Expected Behavior
  -

  - Switching cameras via the settings immediately has effect on the camera 
used by web sites open in the webbrowser-app.
  - Specifying a default camera (startup settings) is available with the 
webapp-container binary.
  - Switching cameras programmatically (via an API call) and/or interactively 
is possible in web apps driven by the webapp-container.

  How to Reproduce
  

  1.) Go to e.g. https://appear.in/test-drive on your Ubuntu phone (default 
webbrowser-app)
  2.) When prompted for "Allow this domain access the camera and microphone" 
choose "Yes"
  3.) Click away the chat window (touch the down-arrow at right lower corner)
  4.) Touch the screen to dismiss the "help text" (the video captured by the 
rear camera is shown)
  5.) In the browser address bar got to Menu -> Settings -> Privacy & 
permissions -> Camera & Microphone, and switch to the front camera; go out of 
the menu going back the hierarchy; the rear camera video is still shown 
  6.) Tap the address bar, tap on the "Reload" icon to reload the page; the 
front camera video is finally shown

  Other Details
  -

  - https://github.com/bittner/appear-in/issues/1 (conversion
  demonstrating users are confused about browser behavior)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1554244/+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 1554223] Re: apt-get update fails with "Unable to find expected entry 'main/binary-i386/Packages' in Release file" on pure x86_64 repos

2016-03-07 Thread Dan Kegel

Oh, this is on ubuntu 15.10 (i.e. apt 1.0.10.2.ubuntu1), and probably all 
previous versions.
It does not seem to affect ubuntu 16.04 beta 1 (i.e. apt 1.2.3).

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

Title:
  apt-get update fails with "Unable to find expected entry
  'main/binary-i386/Packages' in Release file" on pure x86_64 repos

Status in apt package in Ubuntu:
  New

Bug description:
  (ubuntu-bug wouldn't let me report bugs against apt, go figure.)

  I run my own apt repo for a third-party app, and I have to include a
  dummy i386 package to avoid an error from apt-get.

  Along comes Chrome's decision to desupport i386, and suddenly this problem 
matters to a lot of people,
  who are all seeing apt-get update fail with:

  W: Failed to fetch http://dl.google.com/linux/chrome/deb/dists/stable/Release 
 Unable to find expected entry 'main/binary-i386/Packages' in Release file 
(Wrong sources.list entry or malformed file)
  E: Some index files failed to download. They have been ignored, or old ones 
used instead.

  While it would be easy for Google to include a dummy i386 package in
  their repo, it would be even better if apt-get didn't barf like this
  on pure 64 bit repos.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1554223/+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 1553482] Re: Access to microphone is allowed even when user denies access to "video and microphone"

@chrisccoulson can you please specify which channel you are testing,
describe the environment and test device.

I'm on a bq Aquaris E5 Ubuntu Edition with OS build details:
- OTA-9.1
- 20160217.1
- Ubuntu 15.04 - armhf (20160217--111536)
- 20160108-efc96d8
- VEGETA01A-S23A_BQ_L100EN_2010_160217
- 20160111-926-36--vivid

If you're testing a newer build and features are covered by unit test, awesome!
Then we can fully focus on bug 1554202.

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

Title:
  Access to microphone is allowed even when user denies access to "video
  and microphone"

Status in Oxide:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  The plain web browser can access the microphone when you deny the
  permission to access camera and microphone.

  Tested / discovered with bq Aquaris E5 Ubuntu Edition, OTA-9.1
  (vegeta, latest stable as of today).

  How to Reproduce
  

  1.) Go to e.g. https://appear.in/test-drive on your Ubuntu phone (default web 
browser app)
  2.) When prompted for "Allow this domain access the camera and microphone" 
choose "No"
  3.) Click away the chat window (touch the down-arrow at right lower corner)
  4.) Touch the screen to dismiss the "help text" ("Video off" is shown 
prominently)
  5.) Touch the screen again to show the video controls, touch on the 
"microphone" icon; "Audio only" is shown on the screen
  6.) Log in to the same URL from a PC (or another phone) to verify audio works

  Other Details
  -

  Discussion on the mailing list:
  https://lists.launchpad.net/ubuntu-phone/msg18659.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1553482/+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 1553770] Re: apt-utils: xz support is gone.

2016-03-07 Thread Colin Watson

apt (1.2.5) unstable; urgency=medium

  [ Daniel Kahn Gillmor ]
  * apt-key del should correctly handle keyids prefixed with 0x

  [ David Kalnischkies ]
  * support APT::Get::Build-Dep-Automatic again in build-dep
  * add test for apt-key 0xKEY and use parameter expansion.
Thanks to James McCoy for the suggestion. (Closes: 816691)
  * do not move not-failed pdiff-patches into CWD on failure (Closes: #816837)
  * get group again after potential remap in Source: parse.
Thanks to Francesco Poli and Marc Haber for testdata. (Closes: 812251)

  [ Colin Watson ]
  * Fix lzma write support to handle "try again" case (Closes: #751688)

  [ Julian Andres Klode ]
  * Prevent double remapping of iterators and string views
  * debian/control: Set Standards-Version to 3.9.7

 -- Julian Andres Klode   Sun, 06 Mar 2016 19:47:45
+0100

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

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

Title:
  apt-utils: xz support is gone.

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Trusty:
  New
Status in apt package in Debian:
  Fix Released

Bug description:
  Stable release update justification:

  [Impact] apt-ftparchive fails to produce .xz compressed files with 
sufficiently large data sets.  This prevents migration of the Ubuntu archive to 
.xz.
  [Test Case] Grab trusty/main/amd64 with debmirror, construct a suitable file 
list, and ask apt-ftparchive to generate files for this with Packages::Compress 
set to include xz.  We can easily test this on the Launchpad "dogfood" instance 
where we do QA of the archive publisher.
  [Regression Potential] Confined to lzma/xz compression, which I think is 
basically just apt-ftparchive, but we should make sure that other compression 
methods still work there.

  Original report follows:

  Imported from Debian bug http://bugs.debian.org/751688:

  Package: apt-utils
  Version: 0.9.15.5
  Severity: normal

  Dear Maintainer,

  Tested with 1.0.4 and reinstalled working 0.9.15.5

  Packages::Compress seems to not work anymore with xz compression.

  Only . (uncompressed), gzip and bzip2 seems to work, xz now return errors
  (see at the bottom).

  Same error with Sources::Compress

  Christian

  $ apt-ftparchive generate apt.conf
   dists/unstable/main/binary-amd64/:E: write, still have 32768 to write but
  couldn't
  E: IO to subprocess/file failed - write (0: Success)
  E: write, still have 32768 to write but couldn't
  E: IO to subprocess/file failed - write (0: Success)
  E: write, still have 4096 to write but couldn't
  E: IO to subprocess/file failed - write (0: Success)
  E: write, still have 4096 to write but couldn't
  E: IO to subprocess/file failed - write (0: Success)
  E: write, still have 4096 to write but couldn't
  E: IO to subprocess/file failed - write (0: Success)
  E: write, still have 4096 to write but couldn't
  E: IO to subprocess/file failed - write (0: Success)
  E: write, still have 4096 to write but couldn't
  E: IO to subprocess/file failed - write (0: Success)
  E: write, still have 4096 to write but couldn't
  E: IO to subprocess/file failed - write (0: Success)
  E: write, still have 4096 to write but couldn't
  E: IO to subprocess/file failed - write (0: Success)
  E: write, still have 4096 to write but couldn't
  E: IO to subprocess/file failed - write (0: Success)
  E: write, still have 4096 to write but couldn't
  E: IO to subprocess/file failed - write (0: Success)
  E: write, still have 4096 to write but couldn't
  E: IO to subprocess/file failed - write (0: Success)
  E: write, still have 4096 to write but couldn't
  E: IO to subprocess/file failed - write (0: Success)
  E: write, still have 4096 to write but couldn't
  E: IO to subprocess/file failed - write (0: Success)

  E: Sub-process Compress child returned an error code (100)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1553770/+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 1553482] Re: Access to microphone is allowed even when user denies access to "video and microphone"

2016-03-07 Thread Chris Coulson

I'm not reproducing the issue described in the description here. When I
dismiss the permission request in the browser, microphone access is
blocked and I can't hear audio via another machine.

We have unit tests to verify that denying permission requests causes
getUserMedia to fail, and those continue to work too.

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

Title:
  Access to microphone is allowed even when user denies access to "video
  and microphone"

Status in Oxide:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  The plain web browser can access the microphone when you deny the
  permission to access camera and microphone.

  Tested / discovered with bq Aquaris E5 Ubuntu Edition, OTA-9.1
  (vegeta, latest stable as of today).

  How to Reproduce
  

  1.) Go to e.g. https://appear.in/test-drive on your Ubuntu phone (default web 
browser app)
  2.) When prompted for "Allow this domain access the camera and microphone" 
choose "No"
  3.) Click away the chat window (touch the down-arrow at right lower corner)
  4.) Touch the screen to dismiss the "help text" ("Video off" is shown 
prominently)
  5.) Touch the screen again to show the video controls, touch on the 
"microphone" icon; "Audio only" is shown on the screen
  6.) Log in to the same URL from a PC (or another phone) to verify audio works

  Other Details
  -

  Discussion on the mailing list:
  https://lists.launchpad.net/ubuntu-phone/msg18659.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1553482/+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 1543697] Re: Unprivileged nested Xenial container will not start inside a privileged Xenial container

2016-03-07 Thread Christopher Townsend

Hi Serge,

Thanks for working with me on this.

So it does work when I ssh into the privileged container as user ubuntu
and then start the unprivileged container.

I'm guessing there may be no way to start the unprivileged container
from lxc-attach like I want to, right?

Here is the output you requested:

$ sudo lxc-attach -n test-libertine -- sudo -u ubuntu -H cat /proc/self/cgroup
11:cpuset:/
10:pids:/
9:memory:/
8:blkio:/
7:perf_event:/
6:freezer:/
5:hugetlb:/
4:devices:/
3:cpu,cpuacct:/
2:net_cls,net_prio:/
1:name=systemd:/

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

Title:
  Unprivileged nested Xenial container will not start inside a
  privileged Xenial container

Status in lxc package in Ubuntu:
  Fix Released

Bug description:
  I have a host where I create a privileged Xenial container.  Inside
  that privileged container, I create an unprivileged Xenial container
  using the ubuntu user in the privileged container.  When I try
  starting the unprivileged container, I get the following error:

    lxc-start 20160209133200.970 INFO lxc_cgroup - 
cgroup.c:cgroup_init:65 - cgroup driver cgroupfs initing for test-lxc
    lxc-start 20160209133200.971 ERRORlxc_cgfs - cgfs.c:cgfs_init:2248 
- cgroupfs failed to detect cgroup metadata
    lxc-start 20160209133200.971 ERRORlxc_start - 
start.c:lxc_spawn:1023 - failed initializing cgroup support
    lxc-start 20160209133200.971 ERRORlxc_start - 
start.c:__lxc_start:1273 - failed to spawn 'test-lxc'

  I've tried both Trusty host w/ ppa:ubuntu-lxc/lxc-stable installed and
  a Xenial host with the same results.   I've also tried using ppa
  :ubuntu-lxc/daily in the privileged Xenial LXC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1543697/+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 1546304] Re: [scopes] crashes when attaching a bluetooth keyboard, stays closed

2016-03-07 Thread Hajo Möller

/var/crash was empty to begin with, there doesn't seem to be a crash logged.
I will try to reproduce soon.

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

Title:
  [scopes] crashes when attaching a bluetooth keyboard,  stays closed

Status in Canonical System Image:
  Incomplete
Status in unity-scope-click package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  The "Scopes" application sometimes crashes when I connect a bt keyboard.
  If it doesn't crash right away I can close the "Scopes" window, which tries 
to reopen itself for a few times before giving up when I keep closing it.

  "restart unity8-dash" doesn't help, here's what appears in .xsession-errors:
  upstart: application-legacy (unit8-dash-1455655669031059) main process (8349) 
killed by TRAP signal
  upstart: unity8-dash main process (7754) killed by TERM signal

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1546304/+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 997020] Re: apport-collect does not work on headless servers

** Tags added: trusty

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

Title:
  apport-collect does not work on headless servers

Status in apport package in Ubuntu:
  Triaged

Bug description:
  It is essential that apport-collect  works on a headless/non-X
  installs in order to report bugs. In this case, apport-collect tries
  to use a text-based browser to attempt to login to Launchpad.

  I tried lynx, links2, elinks and w3m. With elinks I get the following
  message: "Your Page Was Stale" after selecting "continue".

  This bug is related to #556927, #645024 and #683337. As these only
  concern the functioning of w3m, I would here like to raise the issue
  that a proper installation must make sure that a compatible text-based
  browser is installed and set as default.

  WORKAROUND: Execute the following:
  sudo apt-get install w3m
  sudo update-alternatives --set www-browser /usr/bin/w3m

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/997020/+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 1554099] Re: Changing what action for security updates unusable

2016-03-07 Thread Jason Gerard DeRose

Same is happening with latest Ubuntu (Unity) Xenial daily ISO (sha1sum
8e06dd499bfe357ebbad44c827d8428d70baacf4).

I attached a screenshot of the same problem under Unity.

This bug has been around for a few weeks or so, although I'm not exactly
sure when it was introduced.

** Attachment added: "Screenshot from 2016-03-07 14-34-51.png"
   
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1554099/+attachment/4591889/+files/Screenshot%20from%202016-03-07%2014-34-51.png

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

Title:
  Changing what action for security updates unusable

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Open software-properties.

  Important security updates is not enabled on install.

  Secondly - it is not possible to change the action to take with
  security updates even if it is enabled (note: I enabled security
  updates, reloaded cache and restarted software-properties before
  trying to change the action)

  eg - the Display Immediately/Download automatically/Download and
  install automatically

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: software-properties-gtk 0.96.18
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Mar  7 15:35:24 2016
  InstallationDate: Installed on 2016-03-07 (0 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1554099/+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 1554223] [NEW] apt-get update fails with "Unable to find expected entry 'main/binary-i386/Packages' in Release file" on pure x86_64 repos

2016-03-07 Thread Dan Kegel

Public bug reported:

(ubuntu-bug wouldn't let me report bugs against apt, go figure.)

I run my own apt repo for a third-party app, and I have to include a
dummy i386 package to avoid an error from apt-get.

Along comes Chrome's decision to desupport i386, and suddenly this problem 
matters to a lot of people,
who are all seeing apt-get update fail with:

W: Failed to fetch http://dl.google.com/linux/chrome/deb/dists/stable/Release  
Unable to find expected entry 'main/binary-i386/Packages' in Release file 
(Wrong sources.list entry or malformed file)
E: Some index files failed to download. They have been ignored, or old ones 
used instead.

While it would be easy for Google to include a dummy i386 package in
their repo, it would be even better if apt-get didn't barf like this on
pure 64 bit repos.

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

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

Title:
  apt-get update fails with "Unable to find expected entry
  'main/binary-i386/Packages' in Release file" on pure x86_64 repos

Status in apt package in Ubuntu:
  New

Bug description:
  (ubuntu-bug wouldn't let me report bugs against apt, go figure.)

  I run my own apt repo for a third-party app, and I have to include a
  dummy i386 package to avoid an error from apt-get.

  Along comes Chrome's decision to desupport i386, and suddenly this problem 
matters to a lot of people,
  who are all seeing apt-get update fail with:

  W: Failed to fetch http://dl.google.com/linux/chrome/deb/dists/stable/Release 
 Unable to find expected entry 'main/binary-i386/Packages' in Release file 
(Wrong sources.list entry or malformed file)
  E: Some index files failed to download. They have been ignored, or old ones 
used instead.

  While it would be easy for Google to include a dummy i386 package in
  their repo, it would be even better if apt-get didn't barf like this
  on pure 64 bit repos.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1554223/+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 1554220] Re: Text truncated in media permission prompt

Reference to the design specification for those prompts:
https://docs.google.com/presentation/d/1Qrd4Flfs3EH-fI79IfrYgLdAx2nce-
L7ve8NKLCX324/edit#slide=id.gdf2088339_2_22

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

** Changed in: webbrowser-app (Ubuntu)
   Importance: Undecided => High

** Also affects: ubuntu-ux
   Importance: Undecided
   Status: New

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

Title:
  Text truncated in media permission prompt

Status in Ubuntu UX:
  New
Status in webbrowser-app package in Ubuntu:
  Triaged

Bug description:
  This appears to be the case in several languages, including English, German 
and French.
  To observe, browse to e.g. https://appear.in/foobarbaz. You’ll get a prompt 
to allow the browser to access the camera and microphone. Given that the 
question is in the title of the dialog (which is limited to 2 lines of text, 
and ellipsized), it is truncated, making it hard to understand the question at 
all.
  See attached screenshot (in French).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1554220/+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 1553482] Re: Access to microphone is allowed even when user denies access to "video and microphone"

> Same small glitch with the ellipsis (long text) in the dialog with
> English, btw:

That’s because they are not the same prompts. One is the browser prompt
(the one with truncated text), the other one is from the trust store.

As mpt pointed out in bug #1553713, the mere fact that the browser uses
a dialog to prompt for permissions is confusing and not optimal, a non-
modal ribbon at the top/bottom of the webview would be more suited.

In any case, thanks for pointing out this truncation issue, I’ve filed
bug #1554220 to track it separately.

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

Title:
  Access to microphone is allowed even when user denies access to "video
  and microphone"

Status in Oxide:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  The plain web browser can access the microphone when you deny the
  permission to access camera and microphone.

  Tested / discovered with bq Aquaris E5 Ubuntu Edition, OTA-9.1
  (vegeta, latest stable as of today).

  How to Reproduce
  

  1.) Go to e.g. https://appear.in/test-drive on your Ubuntu phone (default web 
browser app)
  2.) When prompted for "Allow this domain access the camera and microphone" 
choose "No"
  3.) Click away the chat window (touch the down-arrow at right lower corner)
  4.) Touch the screen to dismiss the "help text" ("Video off" is shown 
prominently)
  5.) Touch the screen again to show the video controls, touch on the 
"microphone" icon; "Audio only" is shown on the screen
  6.) Log in to the same URL from a PC (or another phone) to verify audio works

  Other Details
  -

  Discussion on the mailing list:
  https://lists.launchpad.net/ubuntu-phone/msg18659.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1553482/+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 1554099] Re: Changing what action for security updates unusable

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

** Changed in: software-properties (Ubuntu)
   Status: New => Confirmed

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

Title:
  Changing what action for security updates unusable

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Open software-properties.

  Important security updates is not enabled on install.

  Secondly - it is not possible to change the action to take with
  security updates even if it is enabled (note: I enabled security
  updates, reloaded cache and restarted software-properties before
  trying to change the action)

  eg - the Display Immediately/Download automatically/Download and
  install automatically

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: software-properties-gtk 0.96.18
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Mar  7 15:35:24 2016
  InstallationDate: Installed on 2016-03-07 (0 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Re: [Touch-packages] [Bug 1543697] Re: Unprivileged nested Xenial container will not start inside a privileged Xenial container

2016-03-07 Thread Serge Hallyn

Quoting Christopher Townsend (christopher.towns...@canonical.com):
> I tried adding "lxc.include = /usr/share/lxc/config/nesting.conf" as I
> didn't know this existed.  However, it didn't help.
> 
> As you say, I can create unprivileged containers as user ubuntu, I just
> can't start them.  Are you able to start unprivileged containers as user
> ubuntu?  If so, how are you starting them?  I need to start them from

Yes.  I start them by ssh'ing in as user ubuntu and doing lxc-start.
Does that work for you?

> the host's shell, so I'm doing something like this:
> 
> $ sudo lxc-attach -n test-libertine -- sudo -u ubuntu -H lxc-start -n
> test

This may not be enough to trigger pam-cgfs to create cgroups for you,
so that may be the reason it fails.  What does

sudo lxc-attach -n test-libertine -- sudo -u ubuntu -H cat
/proc/self/cgroup

show?

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

Title:
  Unprivileged nested Xenial container will not start inside a
  privileged Xenial container

Status in lxc package in Ubuntu:
  Fix Released

Bug description:
  I have a host where I create a privileged Xenial container.  Inside
  that privileged container, I create an unprivileged Xenial container
  using the ubuntu user in the privileged container.  When I try
  starting the unprivileged container, I get the following error:

    lxc-start 20160209133200.970 INFO lxc_cgroup - 
cgroup.c:cgroup_init:65 - cgroup driver cgroupfs initing for test-lxc
    lxc-start 20160209133200.971 ERRORlxc_cgfs - cgfs.c:cgfs_init:2248 
- cgroupfs failed to detect cgroup metadata
    lxc-start 20160209133200.971 ERRORlxc_start - 
start.c:lxc_spawn:1023 - failed initializing cgroup support
    lxc-start 20160209133200.971 ERRORlxc_start - 
start.c:__lxc_start:1273 - failed to spawn 'test-lxc'

  I've tried both Trusty host w/ ppa:ubuntu-lxc/lxc-stable installed and
  a Xenial host with the same results.   I've also tried using ppa
  :ubuntu-lxc/daily in the privileged Xenial LXC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1543697/+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 1554220] [NEW] Text truncated in media permission prompt

Public bug reported:

This appears to be the case in several languages, including English, German and 
French.
To observe, browse to e.g. https://appear.in/foobarbaz. You’ll get a prompt to 
allow the browser to access the camera and microphone. Given that the question 
is in the title of the dialog (which is limited to 2 lines of text, and 
ellipsized), it is truncated, making it hard to understand the question at all.
See attached screenshot (in French).

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

** Attachment added: "appearin.png"
   
https://bugs.launchpad.net/bugs/1554220/+attachment/4591884/+files/appearin.png

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

Title:
  Text truncated in media permission prompt

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  This appears to be the case in several languages, including English, German 
and French.
  To observe, browse to e.g. https://appear.in/foobarbaz. You’ll get a prompt 
to allow the browser to access the camera and microphone. Given that the 
question is in the title of the dialog (which is limited to 2 lines of text, 
and ellipsized), it is truncated, making it hard to understand the question at 
all.
  See attached screenshot (in French).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1554220/+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 1553482] Re: Access to microphone is allowed even when user denies access to "video and microphone"

> (B) the browser can somehow use the microphone without trust-store
> granting it permission: this bug report, apparently (but then why
> doesn’t it belong to trust-store or pulseaudio?)

Regardless of apparmor policies, if the user denied access to
audio/video, oxide shouldn’t even try to access the hardware. Obviously
if it does and succeeds in doing so, there’s also a bug lower down the
stack. Both issues need to be investigated and fixed (can be done
separately).

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

Title:
  Access to microphone is allowed even when user denies access to "video
  and microphone"

Status in Oxide:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  The plain web browser can access the microphone when you deny the
  permission to access camera and microphone.

  Tested / discovered with bq Aquaris E5 Ubuntu Edition, OTA-9.1
  (vegeta, latest stable as of today).

  How to Reproduce
  

  1.) Go to e.g. https://appear.in/test-drive on your Ubuntu phone (default web 
browser app)
  2.) When prompted for "Allow this domain access the camera and microphone" 
choose "No"
  3.) Click away the chat window (touch the down-arrow at right lower corner)
  4.) Touch the screen to dismiss the "help text" ("Video off" is shown 
prominently)
  5.) Touch the screen again to show the video controls, touch on the 
"microphone" icon; "Audio only" is shown on the screen
  6.) Log in to the same URL from a PC (or another phone) to verify audio works

  Other Details
  -

  Discussion on the mailing list:
  https://lists.launchpad.net/ubuntu-phone/msg18659.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1553482/+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 1554149] Re: Asks for separate permission for microphone and camera

@Peter: the prompt you’re seeing is the one to grant access to the web
API (MediaDevices.getUserMedia()). The trust store / apparmor operate at
an entirely different level, by intercepting direct access to the
hardware. You’re probably not seeing the trust store prompts because you
have already granted those permissions for the browser.

Note that the web API prompt is per domain (and permissions are not
remembered across browsing sessions, that’s a missing feature in oxide,
https://blueprints.launchpad.net/oxide/+spec/site-settings), whereas the
trust store permissions are per app, so they are going to be prompted
only once for the browser the first time a site requests those
permissions).

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

Title:
  Asks for separate permission for microphone and camera

Status in Oxide:
  New

Bug description:
  0. Flash the phone.
  1. In the Browser, go to a page that asks both to record video and use the 
microphone, such as .

  What happens:
  * A prompt appears asking to record audio.
  * Another prompt appears asking to use the camera.

  What should happen:
  * Only one prompt appears, asking to record video, which includes the ability 
to use the microphone.
  

  This might not be fixable, if the Web APIs for recording video and
  audio are separate.

  If it is fixable, it might first require implementing the combined
  permission in trust-store.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1554149/+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 1554149] Re: Asks for separate permission for microphone and camera

> This might not be fixable, if the Web APIs for recording
> video and audio are separate.

Not sure about that, this will require some investigation in oxide.


** Package changed: webbrowser-app (Ubuntu) => oxide

** Changed in: oxide
   Status: Confirmed => New

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

Title:
  Asks for separate permission for microphone and camera

Status in Oxide:
  New

Bug description:
  0. Flash the phone.
  1. In the Browser, go to a page that asks both to record video and use the 
microphone, such as .

  What happens:
  * A prompt appears asking to record audio.
  * Another prompt appears asking to use the camera.

  What should happen:
  * Only one prompt appears, asking to record video, which includes the ability 
to use the microphone.
  

  This might not be fixable, if the Web APIs for recording video and
  audio are separate.

  If it is fixable, it might first require implementing the combined
  permission in trust-store.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1554149/+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 1548031] Re: wrong date in series schedule

** Changed in: ubuntu-calendar-app
Milestone: None => 0.5

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

Title:
  wrong date in series schedule

Status in Ubuntu Calendar App:
  Triaged
Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  Had the Problem that i have some series schedule, but the Alarm ring one 
month to early.
  see attach

  21.03.2016 is the schedule, but got today the alarm.

  Calendar App Version: 0.4.757

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1548031/+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 1364653] Re: Daily Recurring Events need refresh to appear when created from DayView

** Changed in: ubuntu-calendar-app
Milestone: None => 0.5

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

Title:
  Daily Recurring Events need refresh to appear when created from
  DayView

Status in Ubuntu Calendar App:
  Confirmed
Status in qtorganizer5-eds package in Ubuntu:
  Confirmed

Bug description:
  When I create a daily recurring event from the DayView that starts on
  that day, the EventBubble does not immediately appear on the current
  Day.  I can swipe to go to future days, and the EventBubble appears
  there.  If I swipe back to return to the original Day, or I go to a
  different view (MonthView, WeekView, etc.) the event appears.

  Since the EventBubble appears after re-navigating to the page in any
  way, this appears to be a "refreshing" problem, where the DayView
  isn't updated after creating a recurring event.

  Steps to Reproduce
  
  1) Open the Calendar App, and go to any day on the DayView.
  2) Create a recurring event starting on that day, which re-occurs daily.
  3) Save the new event and return to the DayView.  The EventBubble should not 
appear on the DayView for the current Day.

  Expected: The EventBubble should appear on the DayView page
  immediately after returning from creating the event.

  A reproduction of this behavior can be seen at:
  https://www.youtube.com/watch?v=9NK9m8ZznrA=youtu.be

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1364653/+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 1319546] Re: Remove sync-monitor policy rules

** Changed in: ubuntu-calendar-app
   Status: New => Triaged

** Changed in: address-book-app (Ubuntu)
   Status: New => Triaged

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

Title:
  Remove sync-monitor policy rules

Status in Ubuntu Calendar App:
  Triaged
Status in address-book-app package in Ubuntu:
  Triaged
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  New

Bug description:
  Sync monitor should not be accessed by the applications, the sync
  operation should be triggered by the push notification.

  We should remove any policy rules related with sync monitor as soon as
  we get sync monitor integrated with push notification system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1319546/+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 997020] Re: apport-collect does not work on headless servers

This has a compelling reason given a fair amount of original reporters
are doing so via Server OSes (i.e. no GUI).

This would want to be addressed as resources become available to ease
triaging, and server original report confusion.

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

** Changed in: apport (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: apport (Ubuntu)
   Importance: Medium => Wishlist

** Description changed:

  It is essential that apport-collect  works on a headless/non-X installs
  in order to report bugs. In this case, apport-collect tries to use a
  text-based browser to attempt to login to Launchpad.
  
- I tried lynx, links2, elinks and w3m, of which only w3m worked. With
- elinks I get the following message: "Your Page Was Stale" after
- selecting "continue".
- 
- To make apport-collect work, execute the following:
- 
- sudo apt-get install w3m
- sudo update-alternatives --set www-browser /usr/bin/w3m
+ I tried lynx, links2, elinks and w3m. With elinks I get the following
+ message: "Your Page Was Stale" after selecting "continue".
  
  This bug is related to #556927, #645024 and #683337. As these only
  concern the functioning of w3m, I would here like to raise the issue
  that a proper installation must make sure that a compatible text-based
  browser is installed and set as default.
+ 
+ WORKAROUND: Execute the following:
+ sudo apt-get install w3m
+ sudo update-alternatives --set www-browser /usr/bin/w3m

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

Title:
  apport-collect does not work on headless servers

Status in apport package in Ubuntu:
  Triaged

Bug description:
  It is essential that apport-collect  works on a headless/non-X
  installs in order to report bugs. In this case, apport-collect tries
  to use a text-based browser to attempt to login to Launchpad.

  I tried lynx, links2, elinks and w3m. With elinks I get the following
  message: "Your Page Was Stale" after selecting "continue".

  This bug is related to #556927, #645024 and #683337. As these only
  concern the functioning of w3m, I would here like to raise the issue
  that a proper installation must make sure that a compatible text-based
  browser is installed and set as default.

  WORKAROUND: Execute the following:
  sudo apt-get install w3m
  sudo update-alternatives --set www-browser /usr/bin/w3m

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/997020/+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 1508438] Re: Do not notify for events marked as not attending

2016-03-07 Thread Renato Araujo Oliveira Filho

this need to be implemented in the indicator.

** Also affects: indicator-datetime (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Do not notify for events marked as not attending

Status in Ubuntu Calendar App:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  This is a follow-up from bug #1371871. While it was marked as Fix
  Released, it doesn't seem to have had any effect. I'm reporting it as
  two separate bugs to reopen it now.

  I've got a few events in my calendar for meetings where I'm marked as
  not going, which I still want to see in my calendar unless I
  explicitly delete them.

  An example is a recurring event which I've got on my work calendar. During my 
holiday:
  - I'll mark myself as not attending
  - I will not delete the event
  - I don't expect to be notified

  As I'm not marked as attending, I wouldn't expect to get a reminder
  notification, even less if I'm in a different timezone and it's 3:00
  a.m. :)

  See bug 1508440 for the "display events not being attended clearly"
  part.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1508438/+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 1554189] Re: Can no longer swipe between scope results

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

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

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

Title:
  Can no longer swipe between scope results

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

Bug description:
  Until a few days ago, when browsing through an RSS feed scope, it was
  possible to switch to the previous/next article by using swipe
  gestures. This does no longer work for me now and basically makes RSS
  feed scopes useless, as I do not want to click on each article and
  then go back to the overview again just to browse through the article
  summaries.

  $ system-image-cli -i
  current build number: 382
  device name: mako
  channel: ubuntu-touch/rc-proposed/ubuntu
  last update: 2016-03-05 18:18:13
  version version: 382
  version ubuntu: 20160305
  version device: 20160304.2
  version custom: 20160305

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1554189/+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 1544030] Re: wrong time of event shown from pulldown menu

2016-03-07 Thread Michal

Just for completeness, the UTC offset set in my phone is UTC+1 and the
events show 1 hour before the actual start of event.

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

Title:
  wrong time of event shown from pulldown menu

Status in Ubuntu Calendar App:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  When scheduling an event if you select 'Reminder' -> 'No reminder',
  the time of event shown from the pulldown top menu displays a time
  which is one hour BEFORE the actual set start of the event. When
  setting  'Reminder' to any other option, both times are equal. Fix:if
  it is a feature just make an option to disable it or set both times
  equal by default.

  Also, if actual time is less than one hour before the planned start of
  the event (with reminder set to 'No Reminder'), the event disappears
  from the pulldown top menu list. Fix: don't let the event disappear
  from the pulldown top menu until its duration has expired.

  Thanks!

  Using BQ Aquaris 4.5 / OTA 9 / calendar 0.4.757

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1544030/+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 1439049] Re: Indicator entry doesn’t open event details

2016-03-07 Thread Nekhelesh Ramananthan

** Changed in: ubuntu-calendar-app
Milestone: None => 0.5

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

Title:
  Indicator entry doesn’t open event details

Status in Ubuntu Calendar App:
  In Progress
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  When activating the indicator entry for an event, the calendar app is
  launched, but starts with the default view (e.g., the current day). I
  would expect the calendar to show the event details, in the same way
  as when I click an event in the calendar app itself.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1439049/+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 1408015] Re: [sdk][UX] Confirmation in the header bar confusing

2016-03-07 Thread Nekhelesh Ramananthan

** Changed in: ubuntu-calendar-app
Assignee: (unassigned) => Nekhelesh Ramananthan (nik90)

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

Title:
[sdk][UX] Confirmation in the header bar confusing

Status in Quick Memo:
New
Status in Ubuntu Calendar App:
Triaged
Status in Ubuntu Clock App:
Fix Released
Status in Ubuntu UX:
Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
In Progress

Bug description:
Imagine a form of some sort, you fill a few fields of data top-down,
and at the end of it you need to tap in the header at the top to
save/confirm.

Pair that with the header going off-screen to leave more screen for
the content, you have to pull the header in first (and you need to
know that's where the button will be).

An example of this behaviour is the calendar app when adding/editing
an event. One other example (although that could be improved easily by
auto-saving the new note as soon as it's edited) is the Quick Memo
app, where when you create a note in the first place you need to tap
the ✓ icon, but when you're editing, it's all auto-saved and you need
to tap 〈 to go back to the list of notes.

I feel like we need to at least come up with clear guidance on what
belongs in the header, and where a footer with buttons should be used
(we have a way to stick something on top of the keyboard after all¹).

http://developer.ubuntu.com/api/qml/sdk-1.0/Ubuntu.Components.MainView
/#anchorToKeyboard-prop

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: qtdeclarative5-ubuntu-ui-toolkit-plugin
1.1.1364+15.04.20141209-0ubuntu2
Uname: Linux 3.4.67 armv7l
ApportVersion: 2.15-0ubuntu3
Architecture: armhf
Date: Tue Jan 6 17:03:54 2015
InstallationDate: Installed on 2014-12-17 (20 days ago)
InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf
(20141217-020204)
SourcePackage: ubuntu-ui-toolkit
UpgradeStatus: No upgrade log present (probably fresh install)

--- UX comment & resolution --

The back button in the header should never be used as a confirmation but can
mean CANCEL and not just BACK.
If an action or any alterations within the content/screen have to be
confirmed/saved then it requires a visible call to action. This call to action
sits by default in the header unless differently specified by
designer/developer.

In all here described cases the UX can be improved easily by adding
clarity to the UI and sometimes just adding a call to action.

The header can be fixed or can go off-screen the specification for
that lies with the designer/developer. This means if I have an
important action in the header which I want to present to the user all
the time, then the header stays fixed, even if the content is
scrolled.

Clock app:
When creating a new alarm by swiping from the bottom of the screen, the tick
(confirmation) icon should be disabled. Only after interacting with the screen,
by changing one of the parameters for example, the tick should be enabled. This
will signal to user that there was a change and this needs to be confirmed.
Even more informative is a simple word instead of the tick: SAVE. The SAVE
option is a new addition to the header and wasn't available so far.
This concept is already documented in the UI - Toolkit spec which is at the
bottom of this post. If user taps back before saving then the alarm won't be
created. Additionally there can be visual feedback by adding the "feedback
bubble" to the UI.
If the user taps back before saving the feedback bubble states, e.g. "Alarm
not saved". If the tick icon is tapped, it can state "Alarm saved" (see
Notification spec).
In the Repeat section the select all icon has to move one to the left and a
tick or "save added". The behaviour will then follow as described above.

Note app:
There is nothing wrong with the note app approach but it is a custom made
behaviour which is up to the developer. This person decided not to use our
pattern and include a tick or SAVE into the header. There are many note taking
apps on iOS which are not using their patterns either. This doesn't mean they
are bad, they just work differently.

While it is ok to use a "Send Order" or a NEXT at the end of a form,
for some instances and apps it won't be efficient. This means <
CANCEL/BACK and CONFIRM (tick/save/done) can sit in the header but it
is not possible to control apps which don't want to user out UI-
Toolkit, hence the other solutions will exist too.

We are constantly improving the UI-Toolit and I will add the
footer/toolbar idea to potential new projects for design.

Please see for reference the notification spec:

https://docs.google.com/document/d/1xDSZ_dnAMAlhgFnnyjJEibaITXjVLp1_pnj_tATNm9I/edit?pli=1#

Please see for reference the UI - Toolkit spec:

[Touch-packages] [Bug 1537753] Re: ucf --purge reaches code where basename doesn't have a parameter

2016-03-07 Thread Paul Gevers

Isn't this fixed in 3.0033 in commit:
http://anonscm.debian.org/cgit/users/srivasta/debian/ucf.git/commit/?id=599bdf9413ecd06ea18ed02e58d8fcac0bda4bd3

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

Title:
  ucf --purge reaches code where basename doesn't have a parameter

Status in One Hundred Papercuts:
  Triaged
Status in ucf package in Ubuntu:
  Triaged

Bug description:
  When I was clearing up unpurged packages, grub-pc was not being purged 
because of an error "basename: missing operand".  Looked at the code and "ucf 
--purge /etc/default/grub" was bailing out at line 472, which has the code:
  old_mdsum_file="$source_dir/$(basename ${new_file}).md5sum";
  Looking at ${new_file} at the code above, sure enough, it wasn't being 
initialized at purge (line numbers 349 - 374).  So I changed the else to test 
if $new_file was there and I was able to purge grub-pc.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ucf 3.0032 [modified: usr/bin/ucf]
  ProcVersionSignature: Ubuntu 4.3.0-6.17-generic 4.3.3
  Uname: Linux 4.3.0-6-generic x86_64
  ApportVersion: 2.19.3-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jan 25 21:08:03 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-09-28 (118 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: ucf
  UpgradeStatus: Upgraded to xenial on 2016-01-06 (18 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1537753/+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 1552939] Re: arm64 build doesn't use asm and is 4x-16x slower than it could be

2016-03-07 Thread dann frazier

This is a change to a Debian-specific targets, so marking it Invalid for
the upstream OpenSSL project.

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

** Changed in: openssl (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  arm64 build doesn't use asm and is 4x-16x slower than it could be

Status in OpenSSL:
  Invalid
Status in openssl package in Ubuntu:
  Fix Committed
Status in openssl package in Debian:
  New

Bug description:
  The openssl build for arm64 doesn't compile in the assembly that is
  present in openssl as of version 1.0.2 for aarch64 because the debian-
  targets.patch that is applied specifies a target that doesn't have
  assembly. The line at issue is debian-arm64 target which needs
  ${no_asm}  changed to ${aarch64_asm}:linux64. Running openssl speed
  -evp aes-128-gcm shows a 4x-16x improvement in performance with this
  change made and the package rebuilt. Other aes and sha variants show
  similar performance gains by enabling asm.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openssl/+bug/1552939/+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 1552939] Re: arm64 build doesn't use asm and is 4x-16x slower than it could be

2016-03-07 Thread dann frazier

fyi, this is now available in xenial-proposed.

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

Title:
  arm64 build doesn't use asm and is 4x-16x slower than it could be

Status in OpenSSL:
  Invalid
Status in openssl package in Ubuntu:
  Fix Committed
Status in openssl package in Debian:
  New

Bug description:
  The openssl build for arm64 doesn't compile in the assembly that is
  present in openssl as of version 1.0.2 for aarch64 because the debian-
  targets.patch that is applied specifies a target that doesn't have
  assembly. The line at issue is debian-arm64 target which needs
  ${no_asm}  changed to ${aarch64_asm}:linux64. Running openssl speed
  -evp aes-128-gcm shows a 4x-16x improvement in performance with this
  change made and the package rebuilt. Other aes and sha variants show
  similar performance gains by enabling asm.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openssl/+bug/1552939/+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 1552860] Re: [MIR] qtsystems-opensource-src

2016-03-07 Thread Michael Terry

So is that a real failure or just the test not being run under dbus?  If
it just needs dbus, maybe we can run the tests under dbus-run-session?

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

Title:
  [MIR] qtsystems-opensource-src

Status in qtsystems-opensource-src package in Ubuntu:
  Incomplete

Bug description:
  This is a MIR for qtsystems-opensource-src, which is currently in
  universe.

  1. Availability: the package has been in universe since Trusty, and it
  builds on all supported architectures.

  2. Rationale: In Ubuntu Touch applications, the recommended way of
  enumerating input devices (physical keyboards, mice, touchpads, etc…)
  is the QInputDeviceInfo API. We would like to start using that API in
  webbrowser-app, which is in main.

  3. Security: nothing to highlight, but the security team might want to
  acknowledge that. Note that a preliminary review was already done a
  couple of years ago, see Jamie’s comments at
  https://bugs.launchpad.net/ubuntu/+source/qtsystems-opensource-
  src/+bug/1217001/comments/10.

  4. QA: the package comes with automated unit tests as well as manual
  tests. The unit tests are run as part of the package build. Bugs in
  ubuntu: https://bugs.launchpad.net/ubuntu/+source/qtsystems-
  opensource-src. The package is not in debian (see
  https://wiki.debian.org/Mobile/Ubuntu).

  5. UI standards: N/A

  6. Dependencies: all build and runtime dependencies are in main.

  7. Standards compliance: complies with debian packaging standards.

  8. Maintenance: actively maintained by Timo Jyrinki .

  9. Background information: package descriptions are meaningful.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtsystems-opensource-src/+bug/1552860/+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 1552860] Re: [MIR] qtsystems-opensource-src

Interestingly, a local build with all the original patches still fails
(although differently):

QT_PLUGIN_PATH=/usr/lib/x86_64-linux-gnu/qt5/plugins 
LD_LIBRARY_PATH='/build/qtsystems-opensource-src-5.0~git20141206~44f70d99/lib:/usr/lib/x86_64-linux-gnu'${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}
  ./tst_qremoteserviceregister 
* Start testing of tst_QRemoteServiceRegister *
Config: Using QtTest library 5.5.1, Qt 5.5.1 (x86_64-little_endian-lp64 shared 
(dynamic) release build; by GCC 5.3.1 20160225)
QWARN  : tst_QRemoteServiceRegister::initTestCase() Service Framework:- Unable 
to open or create database at: 
/nonexistent/.config/Nokia/QtServiceFramework_5.5_user.db
FAIL!  : tst_QRemoteServiceRegister::initTestCase() 'r' returned FALSE. (Cannot 
register RSRExampleService - 
/build/qtsystems-opensource-src-5.0~git20141206~44f70d99/tests/auto/serviceframework/qremoteserviceregister//xmldata/rsrexampleservice.xml)
   Loc: [tst_qremoteserviceregister.cpp(122)]
QWARN  : tst_QRemoteServiceRegister::cleanupTestCase() Service Framework:- 
Unable to open or create database at: 
/nonexistent/.config/Nokia/QtServiceFramework_5.5_user.db
PASS   : tst_QRemoteServiceRegister::cleanupTestCase()
Totals: 1 passed, 1 failed, 0 skipped, 0 blacklisted
* Finished testing of tst_QRemoteServiceRegister *

The test build was done in a clean xenial amd64 chroot.

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

Title:
  [MIR] qtsystems-opensource-src

Status in qtsystems-opensource-src package in Ubuntu:
  Incomplete

Bug description:
  This is a MIR for qtsystems-opensource-src, which is currently in
  universe.

  1. Availability: the package has been in universe since Trusty, and it
  builds on all supported architectures.

  2. Rationale: In Ubuntu Touch applications, the recommended way of
  enumerating input devices (physical keyboards, mice, touchpads, etc…)
  is the QInputDeviceInfo API. We would like to start using that API in
  webbrowser-app, which is in main.

  3. Security: nothing to highlight, but the security team might want to
  acknowledge that. Note that a preliminary review was already done a
  couple of years ago, see Jamie’s comments at
  https://bugs.launchpad.net/ubuntu/+source/qtsystems-opensource-
  src/+bug/1217001/comments/10.

  4. QA: the package comes with automated unit tests as well as manual
  tests. The unit tests are run as part of the package build. Bugs in
  ubuntu: https://bugs.launchpad.net/ubuntu/+source/qtsystems-
  opensource-src. The package is not in debian (see
  https://wiki.debian.org/Mobile/Ubuntu).

  5. UI standards: N/A

  6. Dependencies: all build and runtime dependencies are in main.

  7. Standards compliance: complies with debian packaging standards.

  8. Maintenance: actively maintained by Timo Jyrinki .

  9. Background information: package descriptions are meaningful.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtsystems-opensource-src/+bug/1552860/+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 1554202] Re: [webapp-container] No access to video provided despite policy_group "camera" in .apparmour file

The webapp container needs to hook to the webview’s
mediaAccessPermissionRequested signal, similar to what’s done for
geolocationPermissionRequested.

** Changed in: webbrowser-app (Ubuntu)
   Importance: Undecided => High

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

** Changed in: webbrowser-app (Ubuntu)
 Assignee: (unassigned) => Alexandre Abreu (abreu-alexandre)

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

Title:
  [webapp-container] No access to video provided despite policy_group
  "camera" in .apparmour file

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  A web app that displays a website trying to access camera and
  microphone (for video conferencing, using WebRTC) will be refused to
  access the camera despite the "camera" policy_group in apparmour.

  The trust-store dialog pops up in the webbrowser-app for a website
  such as [1], but it doesn't pop up when the website is embedded with
  webapp-container.

  [1] https://appear.in/test-drive

  Details
  ---

  - Detailed explanations on the mailing list: 
https://lists.launchpad.net/ubuntu-phone/msg18658.html
  - Affected web app (Store): 
https://uappexplorer.com/app/appear-in.peter-bittner
  - Affected web app (rev 2): 
https://myapps.developer.ubuntu.com/dev/click-apps/4646/rev/2/
  - Bug report for affected app: https://github.com/bittner/appear-in/issues/1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1554202/+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 1551858] Re: [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt

** Attachment added: "system settings log from krillin"
   
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551858/+attachment/4591779/+files/application-legacy-ubuntu-system-settings-.log

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

Title:
  [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt

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

Bug description:
  Connecting to the latest generation Apple BT keyboard ( the one with
  the USB port & no batteries ) fails on an Ubuntu Touch device, as when
  you press the "Connect" button on the device page, a dialog titled
  "Bluetooth Pairing Request" is displayed, with the following text:

  Please confirm that the PIN displayed on 'Magic Keyboard' matches this
  one: XX

  The dialog has "Cancel" and "Confirm PIN" buttons.

  The keyboard has no display on which a PIN could be displayed.

  When using other devices ( Ubuntu Desktop 15.10, 16.04, Android, OS X,
  ... ) to connect this keyboard all that's necessary is to click/press
  the 'Connect' button in the appropriate place, and the keyboard
  automatically connects, and is usable with no other actions required
  from the user.

  Reproduced on krillin ( rc-proposed/bq-aquris.en/270 ) which has bluez
  5.36-0ubuntu2~overlay1 installed.

  Reproduced on arale ( rc-proposed/meizu.en/258 ) which has bluez 5.37
  installed from silo 39.

  Note, after dismissing the dialog, subsequent attempts to connect may
  not re-display the PIN dialog, instead nothing happens.  I've found
  that this requires power cycling the keyboard to clear and cause the
  PIN dialog to be displayed again.

  [bluetooth]# show
  Controller B8:64:91:48:2B:1E
Name: Aquaris E4.5 Ubuntu Edition
Alias: Aquaris E4.5 Ubuntu Edition
Class: 0x1c020c
Powered: yes
Discoverable: no
Pairable: yes
UUID: Headset AG(1112--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb)
UUID: Phonebook Access Server   (112f--1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0525
Discovering: no

  [bluetooth]# devices
  Device 18:EE:69:21:6C:D3 18-EE-69-21-6C-D3
  Device DE:76:E2:04:9D:6F BB-9D6F
  Device 7C:D1:C3:1C:B4:03 7C-D1-C3-1C-B4-03
  Device 7C:D1:C3:19:2B:D8 7C-D1-C3-19-2B-D8
  Device 84:38:35:67:0C:3D ubuntu-0
  Device 04:69:F8:C2:A0:09 tony espy’s Keyboard
  Device 00:21:3C:A0:14:A6 Jawbone ERA
  Device 1C:1A:C0:B2:9A:D7 1C-1A-C0-B2-9A-D7

  Device info *before* pairing attempt:

  Device 04:69:F8:C2:A0:09
Name: tony espy’s Keyboard
Alias: tony espy’s Keyboard
Class: 0x002540
Icon: input-keyboard
Paired: no
Trusted: no
Blocked: no
Connected: no
LegacyPairing: no
Modalias: bluetooth:v004Cp0267d0066

  No changes in any of the attributes after *after* the pairing attempt
  ( output of info command is the same ).

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551858/+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 1551858] Re: [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt

Re-tested on krillin ( rc-proposed/bq-aquaris.en / 270 ), this time with
bluez 5.37 installed from the silo.

@Simon, how could this not be a system settings app failure?  As I
pointed out in my description, pairing this keyboard works fine with
every other device I tried, including two Ubuntu desktop systems.

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

Title:
  [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt

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

Bug description:
  Connecting to the latest generation Apple BT keyboard ( the one with
  the USB port & no batteries ) fails on an Ubuntu Touch device, as when
  you press the "Connect" button on the device page, a dialog titled
  "Bluetooth Pairing Request" is displayed, with the following text:

  Please confirm that the PIN displayed on 'Magic Keyboard' matches this
  one: XX

  The dialog has "Cancel" and "Confirm PIN" buttons.

  The keyboard has no display on which a PIN could be displayed.

  When using other devices ( Ubuntu Desktop 15.10, 16.04, Android, OS X,
  ... ) to connect this keyboard all that's necessary is to click/press
  the 'Connect' button in the appropriate place, and the keyboard
  automatically connects, and is usable with no other actions required
  from the user.

  Reproduced on krillin ( rc-proposed/bq-aquris.en/270 ) which has bluez
  5.36-0ubuntu2~overlay1 installed.

  Reproduced on arale ( rc-proposed/meizu.en/258 ) which has bluez 5.37
  installed from silo 39.

  Note, after dismissing the dialog, subsequent attempts to connect may
  not re-display the PIN dialog, instead nothing happens.  I've found
  that this requires power cycling the keyboard to clear and cause the
  PIN dialog to be displayed again.

  [bluetooth]# show
  Controller B8:64:91:48:2B:1E
Name: Aquaris E4.5 Ubuntu Edition
Alias: Aquaris E4.5 Ubuntu Edition
Class: 0x1c020c
Powered: yes
Discoverable: no
Pairable: yes
UUID: Headset AG(1112--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb)
UUID: Phonebook Access Server   (112f--1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0525
Discovering: no

  [bluetooth]# devices
  Device 18:EE:69:21:6C:D3 18-EE-69-21-6C-D3
  Device DE:76:E2:04:9D:6F BB-9D6F
  Device 7C:D1:C3:1C:B4:03 7C-D1-C3-1C-B4-03
  Device 7C:D1:C3:19:2B:D8 7C-D1-C3-19-2B-D8
  Device 84:38:35:67:0C:3D ubuntu-0
  Device 04:69:F8:C2:A0:09 tony espy’s Keyboard
  Device 00:21:3C:A0:14:A6 Jawbone ERA
  Device 1C:1A:C0:B2:9A:D7 1C-1A-C0-B2-9A-D7

  Device info *before* pairing attempt:

  Device 04:69:F8:C2:A0:09
Name: tony espy’s Keyboard
Alias: tony espy’s Keyboard
Class: 0x002540
Icon: input-keyboard
Paired: no
Trusted: no
Blocked: no
Connected: no
LegacyPairing: no
Modalias: bluetooth:v004Cp0267d0066

  No changes in any of the attributes after *after* the pairing attempt
  ( output of info command is the same ).

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551858/+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 1551858] Re: [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt

** Description changed:

  Connecting to the latest generation Apple BT keyboard ( the one with the
  USB port & no batteries ) fails on an Ubuntu Touch device, as when you
  press the "Connect" button on the device page, a dialog titled
  "Bluetooth Pairing Request" is displayed, with the following text:
  
  Please confirm that the PIN displayed on 'Magic Keyboard' matches this
  one: XX
  
  The dialog has "Cancel" and "Confirm PIN" buttons.
  
  The keyboard has no display on which a PIN could be displayed.
  
  When using other devices ( Ubuntu Desktop 15.10, 16.04, Android, OS X,
  ... ) to connect this keyboard all that's necessary is to click/press
  the 'Connect' button in the appropriate place, and the keyboard
  automatically connects, and is usable with no other actions required
  from the user.
  
  Reproduced on krillin ( rc-proposed/bq-aquris.en/270 ) which has bluez
  5.36-0ubuntu2~overlay1 installed.
  
  Reproduced on arale ( rc-proposed/meizu.en/258 ) which has bluez 5.37
  installed from silo 39.
  
  Note, after dismissing the dialog, subsequent attempts to connect may
  not re-display the PIN dialog, instead nothing happens.  I've found that
  this requires power cycling the keyboard to clear and cause the PIN
  dialog to be displayed again.
+ 
+ [bluetooth]# show
+ Controller B8:64:91:48:2B:1E
+   Name: Aquaris E4.5 Ubuntu Edition
+   Alias: Aquaris E4.5 Ubuntu Edition
+   Class: 0x1c020c
+   Powered: yes
+   Discoverable: no
+   Pairable: yes
+   UUID: Headset AG(1112--1000-8000-00805f9b34fb)
+   UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
+   UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
+   UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
+   UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
+   UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
+   UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
+   UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
+   UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb)
+   UUID: Phonebook Access Server   (112f--1000-8000-00805f9b34fb)
+   Modalias: usb:v1D6Bp0246d0525
+   Discovering: no
+ 
+ [bluetooth]# devices
+ Device 18:EE:69:21:6C:D3 18-EE-69-21-6C-D3
+ Device DE:76:E2:04:9D:6F BB-9D6F
+ Device 7C:D1:C3:1C:B4:03 7C-D1-C3-1C-B4-03
+ Device 7C:D1:C3:19:2B:D8 7C-D1-C3-19-2B-D8
+ Device 84:38:35:67:0C:3D ubuntu-0
+ Device 04:69:F8:C2:A0:09 tony espy’s Keyboard
+ Device 00:21:3C:A0:14:A6 Jawbone ERA
+ Device 1C:1A:C0:B2:9A:D7 1C-1A-C0-B2-9A-D7
+ 
+ Device info *before* pairing attempt:
+ 
+ Device 04:69:F8:C2:A0:09
+   Name: tony espy’s Keyboard
+   Alias: tony espy’s Keyboard
+   Class: 0x002540
+   Icon: input-keyboard
+   Paired: no
+   Trusted: no
+   Blocked: no
+   Connected: no
+   LegacyPairing: no
+   Modalias: bluetooth:v004Cp0267d0066
+ 
+ No changes in any of the attributes after *after* the pairing attempt (
+ output of info command is the same ).

** Attachment added: "syslog from krillin w/bluez debug enabled"
   
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551858/+attachment/4591778/+files/syslog

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

Title:
  [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt

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

Bug description:
  Connecting to the latest generation Apple BT keyboard ( the one with
  the USB port & no batteries ) fails on an Ubuntu Touch device, as when
  you press the "Connect" button on the device page, a dialog titled
  "Bluetooth Pairing Request" is displayed, with the following text:

  Please confirm that the PIN displayed on 'Magic Keyboard' matches this
  one: XX

  The dialog has "Cancel" and "Confirm PIN" buttons.

  The keyboard has no display on which a PIN could be displayed.

  When using other devices ( Ubuntu Desktop 15.10, 16.04, Android, OS X,
  ... ) to connect this keyboard all that's necessary is to click/press
  the 'Connect' button in the appropriate place, and the keyboard
  automatically connects, and is usable with no other actions required
  from the user.

  Reproduced on krillin ( rc-proposed/bq-aquris.en/270 ) which has bluez
  5.36-0ubuntu2~overlay1 installed.

  Reproduced on arale ( rc-proposed/meizu.en/258 ) which has bluez 5.37
  installed from silo 39.

  Note, after dismissing the dialog, subsequent attempts to connect may
  not re-display the PIN dialog, instead nothing happens.  I've found
  that this requires power cycling the keyboard to clear and cause the
  PIN dialog to be displayed again.

  [bluetooth]# show
  Controller B8:64:91:48:2B:1E
Name: Aquaris

[Touch-packages] [Bug 1551858] Re: [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt

** Attachment added: "dbus log from krillin"
   
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551858/+attachment/4591780/+files/dbus.log

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

Title:
  [bluetooth] Connecting to Apple BT keyboard fails due to PIN prompt

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

Bug description:
  Connecting to the latest generation Apple BT keyboard ( the one with
  the USB port & no batteries ) fails on an Ubuntu Touch device, as when
  you press the "Connect" button on the device page, a dialog titled
  "Bluetooth Pairing Request" is displayed, with the following text:

  Please confirm that the PIN displayed on 'Magic Keyboard' matches this
  one: XX

  The dialog has "Cancel" and "Confirm PIN" buttons.

  The keyboard has no display on which a PIN could be displayed.

  When using other devices ( Ubuntu Desktop 15.10, 16.04, Android, OS X,
  ... ) to connect this keyboard all that's necessary is to click/press
  the 'Connect' button in the appropriate place, and the keyboard
  automatically connects, and is usable with no other actions required
  from the user.

  Reproduced on krillin ( rc-proposed/bq-aquris.en/270 ) which has bluez
  5.36-0ubuntu2~overlay1 installed.

  Reproduced on arale ( rc-proposed/meizu.en/258 ) which has bluez 5.37
  installed from silo 39.

  Note, after dismissing the dialog, subsequent attempts to connect may
  not re-display the PIN dialog, instead nothing happens.  I've found
  that this requires power cycling the keyboard to clear and cause the
  PIN dialog to be displayed again.

  [bluetooth]# show
  Controller B8:64:91:48:2B:1E
Name: Aquaris E4.5 Ubuntu Edition
Alias: Aquaris E4.5 Ubuntu Edition
Class: 0x1c020c
Powered: yes
Discoverable: no
Pairable: yes
UUID: Headset AG(1112--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb)
UUID: Phonebook Access Server   (112f--1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0525
Discovering: no

  [bluetooth]# devices
  Device 18:EE:69:21:6C:D3 18-EE-69-21-6C-D3
  Device DE:76:E2:04:9D:6F BB-9D6F
  Device 7C:D1:C3:1C:B4:03 7C-D1-C3-1C-B4-03
  Device 7C:D1:C3:19:2B:D8 7C-D1-C3-19-2B-D8
  Device 84:38:35:67:0C:3D ubuntu-0
  Device 04:69:F8:C2:A0:09 tony espy’s Keyboard
  Device 00:21:3C:A0:14:A6 Jawbone ERA
  Device 1C:1A:C0:B2:9A:D7 1C-1A-C0-B2-9A-D7

  Device info *before* pairing attempt:

  Device 04:69:F8:C2:A0:09
Name: tony espy’s Keyboard
Alias: tony espy’s Keyboard
Class: 0x002540
Icon: input-keyboard
Paired: no
Trusted: no
Blocked: no
Connected: no
LegacyPairing: no
Modalias: bluetooth:v004Cp0267d0066

  No changes in any of the attributes after *after* the pairing attempt
  ( output of info command is the same ).

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551858/+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 1554205] Re: systemd crashed with SIGABRT

2016-03-07 Thread Apport retracing service

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1547851, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1554205/+attachment/4591781/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1554205/+attachment/4591784/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1554205/+attachment/4591790/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1554205/+attachment/4591792/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1554205/+attachment/4591793/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1554205/+attachment/4591794/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1554205/+attachment/4591795/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1547851

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  systemd crashed with SIGABRT

Status in systemd package in Ubuntu:
  New

Bug description:
  No idea

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-2ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Mon Mar  7 21:17:42 2016
  ExecutablePath: /lib/systemd/systemd
  InstallationDate: Installed on 2015-12-29 (69 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  MachineType: LENOVO 6468AF4
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcCmdline: /lib/systemd/systemd --user
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic 
root=UUID=f4457ebc-0b50-4985-af9f-ef80749359d2 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  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.
  SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', 
'Error:'] failed with exit code 1: Failed to get properties: Failed to activate 
service 'org.freedesktop.systemd1': timed out
  Title: systemd crashed with SIGABRT
  UpgradeStatus: Upgraded to xenial on 2016-02-24 (11 days ago)
  UserGroups: adm cdrom dip fax lpadmin plugdev sambashare sudo vboxusers 
www-data
  dmi.bios.date: 02/27/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7LETD0WW (2.30 )
  dmi.board.name: 6468AF4
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: 6468AF4L3C2596
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7LETD0WW(2.30):bd02/27/2012:svnLENOVO:pn6468AF4:pvrThinkPadT61:rvnLENOVO:rn6468AF4:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 6468AF4
  dmi.product.version: ThinkPad T61
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1554205/+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 1553907] Re: fsck man page refers to missing -p option

It is not in the man but it is in fsck's help:

 $ fsck --help
fsck from util-linux 2.27.1
fsck.ext4: invalid option -- 'h'
Usage: fsck.ext4 [-panyrcdfvtDFV] [-b superblock] [-B blocksize]
[-I inode_buffer_blocks] [-P process_inode_size]
[-l|-L bad_blocks_file] [-C fd] [-j external_journal]
[-E extended-options] device

Emergency help:
 -p   Automatic repair (no questions)


** Changed in: util-linux (Ubuntu)
   Status: New => Triaged

** Changed in: util-linux (Ubuntu)
   Importance: Undecided => Low

** Tags added: xenial

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

Title:
  fsck man page refers to missing -p option

Status in util-linux package in Ubuntu:
  Triaged

Bug description:
  Hello there,

  in the fsck man mage there are references to a '-p' option:
  -s says it must be used in conjunction with -a or p
  -a suggests -p is probably better to use instead of -a

  Anyway, there is no -p option in the man page.
  There is -P but, for what I know, options are case-sensitive so it's not 
related.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: util-linux 2.26.2-6ubuntu3
  ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Mar  7 08:24:33 2016
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to wily on 2015-10-31 (128 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1553907/+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 1553591] Re: xenial: Wide character ???? in * at /usr/bin/ckbcomp line *

** Changed in: console-setup (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  xenial: Wide character  in * at /usr/bin/ckbcomp line *

Status in console-setup:
  Fix Released
Status in console-setup package in Ubuntu:
  Triaged

Bug description:
  Created a 16.04 chroot via deboostrap without a UTF-8 locale set and
  get:

  dpkg-reconfigure console-setup
  ...
  perl: warning: Falling back to the standard locale ("C").
  Wide character (U+215B) in pattern match (m//) at /usr/bin/ckbcomp line 3763.
  Wide character (U+215B) in pattern match (m//) at /usr/bin/ckbcomp line 3763.
  Wide character (U+215B) in pattern match (m//) at /usr/bin/ckbcomp line 3763.
  Wide character (U+215B) in pattern match (m//) at /usr/bin/ckbcomp line 3763.
  Wide character (U+215B) in lc at /usr/bin/ckbcomp line 4287.
  Wide character (U+215B) in uc at /usr/bin/ckbcomp line 4288.
  Wide character (U+215B) in lc at /usr/bin/ckbcomp line 4287.
  Wide character (U+215B) in uc at /usr/bin/ckbcomp line 4288.
  Wide character (U+215B) in lc at /usr/bin/ckbcomp line 4287.
  Wide character (U+215B) in uc at /usr/bin/ckbcomp line 4288.
  Wide character (U+215B) in lc at /usr/bin/ckbcomp line 4287.
  Wide character (U+215B) in uc at /usr/bin/ckbcomp line 4288.
  Wide character (U+20AC) in pattern match (m//) at /usr/bin/ckbcomp line 3763.
  Wide character (U+20AC) in pattern match (m//) at /usr/bin/ckbcomp line 3763.
  Wide character (U+20AC) in pattern match (m//) at /usr/bin/ckbcomp line 3763.
  Wide character (U+20AC) in pattern match (m//) at /usr/bin/ckbcomp line 3763.
  Wide character (U+20AC) in lc at /usr/bin/ckbcomp line 4287.
  Wide character (U+20AC) in uc at /usr/bin/ckbcomp line 4288.
  Wide character (U+20AC) in lc at /usr/bin/ckbcomp line 4287.
  Wide character (U+20AC) in uc at /usr/bin/ckbcomp line 4288.
  Wide character (U+20AC) in lc at /usr/bin/ckbcomp line 4287.
  Wide character (U+20AC) in uc at /usr/bin/ckbcomp line 4288.
  Wide character (U+20AC) in lc at /usr/bin/ckbcomp line 4287.
  Wide character (U+20AC) in uc at /usr/bin/ckbcomp line 4288.
  Wide character (U+215C) in pattern match (m//) at /usr/bin/ckbcomp line 3763.
  Wide character (U+215C) in pattern match (m//) at /usr/bin/ckbcomp line 3763.
  Wide character (U+215C) in pattern match (m//) at /usr/bin/ckbcomp line 3763.
  Wide character (U+215C) in pattern match (m//) at /usr/bin/ckbcomp line 3763.
  Wide character (U+215C) in lc at /usr/bin/ckbcomp line 4287.
  Wide character (U+215C) in uc at /usr/bin/ckbcomp line 4288.
  Wide character (U+215C) in lc at /usr/bin/ckbcomp line 4287.
  Wide character (U+215C) in uc at /usr/bin/ckbcomp line 4288.
  Wide character (U+215C) in lc at /usr/bin/ckbcomp line 4287.
  Wide character (U+215C) in uc at /usr/bin/ckbcomp line 4288.
  Wide character (U+215C) in lc at /usr/bin/ckbcomp line 4287.
  Wide character (U+215C) in uc at /usr/bin/ckbcomp line 4288.
  Wide character (U+215D) in pattern match (m//) at /usr/bin/ckbcomp line 3763.
  Wide character (U+215D) in pattern match (m//) at /usr/bin/ckbcomp line 3763.
  Wide character (U+215D) in pattern match (m//) at /usr/bin/ckbcomp line 3763.
  Wide character (U+215D) in pattern match (m//) at /usr/bin/ckbcomp line 3763.
  Wide character (U+215D) in lc at /usr/bin/ckbcomp line 4287.
  Wide character (U+215D) in uc at /usr/bin/ckbcomp line 4288.
  Wide character (U+215D) in lc at /usr/bin/ckbcomp line 4287.
  Wide character (U+215D) in uc at /usr/bin/ckbcomp line 4288.
  Wide character (U+215D) in lc at /usr/bin/ckbcomp line 4287.
  Wide character (U+215D) in uc at /usr/bin/ckbcomp line 4288.
  Wide character (U+215D) in lc at /usr/bin/ckbcomp line 4287.
  Wide character (U+215D) in uc at /usr/bin/ckbcomp line 4288.
  Wide character (U+215E) in pattern match (m//) at /usr/bin/ckbcomp line 3763.
  Wide character (U+215E) in pattern match (m//) at /usr/bin/ckbcomp line 3763.
  Wide character (U+215E) in pattern match (m//) at /usr/bin/ckbcomp line 3763.
  Wide character (U+215E) in pattern match (m//) at /usr/bin/ckbcomp line 3763.
  Wide character (U+215E) in lc at /usr/bin/ckbcomp line 4287.
  Wide character (U+215E) in uc at /usr/bin/ckbcomp line 4288.
  Wide character (U+215E) in lc at /usr/bin/ckbcomp line 4287.
  Wide character (U+215E) in uc at /usr/bin/ckbcomp line 4288.
  Wide character (U+215E) in lc at /usr/bin/ckbcomp line 4287.
  Wide character (U+215E) in uc at /usr/bin/ckbcomp line 4288.
  Wide character (U+215E) in lc at /usr/bin/ckbcomp line 4287.
  Wide character (U+215E) in uc at /usr/bin/ckbcomp line 4288.
  Wide character (U+2122) in pattern match (m//) at /usr/bin/ckbcomp line 3763.
  Wide character (U+2122) in pattern match (m//) at /usr/bin/ckbcomp line 3763.
  Wide character (U+2122) in pattern match (m//) at /usr/bin/ckbcomp line 3763.
  Wide character

[Touch-packages] [Bug 1553353] Re: tail'ing a file in a script session hangs

** Tags added: regression-release

** Also affects: util-linux (Ubuntu Xenial)
   Importance: High
   Status: Confirmed

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

Title:
  tail'ing a file in a script session hangs

Status in util-linux package in Ubuntu:
  Confirmed
Status in util-linux source package in Xenial:
  Confirmed

Bug description:
  Steps to reproduce:

  1) Start script session (same issue when script is saving to /dev/null)
  script # or: script /dev/null
  2) Tail a file
  tail -f /var/log/syslog
  3) Press "Enter" 2 times
  4) Notice the script process taking 100% CPU

  This regression is rather new but I don't know which update introduced
  it. Reverting util-linux/bsdutils to the previous version doesn't help
  so maybe it's not even script's fault. tail/coreutils hasn't been
  update in a long time so I'm not sure who's fault it is. I can
  reproduce the problem with kernel 4.4.0-9-generic and
  4.4.0-10-generic.


  $ lsb_release -rd
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  $ apt-cache policy util-linux bsdutils coreutils
  util-linux:
Installed: 2.27.1-4ubuntu1
Candidate: 2.27.1-4ubuntu1
Version table:
   *** 2.27.1-4ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.27.1-3ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  bsdutils:
Installed: 1:2.27.1-4ubuntu1
Candidate: 1:2.27.1-4ubuntu1
Version table:
   *** 1:2.27.1-4ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:2.27.1-3ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  coreutils:
Installed: 8.25-2ubuntu2
Candidate: 8.25-2ubuntu2
Version table:
   *** 8.25-2ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-4ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar  4 15:14:15 2016
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1553353/+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 1554203] [NEW] sync never returns

2016-03-07 Thread Karl-Philipp Richter

Public bug reported:

`sync` never returns. Verified with Linux 4.4.0-10-generic and 4.4.3
mainline.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: coreutils 8.25-2ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
Uname: Linux 4.4.0-10-generic x86_64
NonfreeKernelModules: openafs
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Mar  7 21:10:56 2016
InstallationDate: Installed on 2013-10-17 (872 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
SourcePackage: coreutils
UpgradeStatus: Upgraded to xenial on 2016-03-04 (2 days ago)

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


** Tags: amd64 apport-bug xenial

** Description changed:

- `sync` never returns. Also verified with Linux 4.4.3 mainline.
+ `sync` never returns. Verified with Linux 4.4.0-10-generic and 4.4.3
+ mainline.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: coreutils 8.25-2ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar  7 21:10:56 2016
  InstallationDate: Installed on 2013-10-17 (872 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: coreutils
  UpgradeStatus: Upgraded to xenial on 2016-03-04 (2 days ago)

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

Title:
  sync never returns

Status in coreutils package in Ubuntu:
  New

Bug description:
  `sync` never returns. Verified with Linux 4.4.0-10-generic and 4.4.3
  mainline.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: coreutils 8.25-2ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar  7 21:10:56 2016
  InstallationDate: Installed on 2013-10-17 (872 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: coreutils
  UpgradeStatus: Upgraded to xenial on 2016-03-04 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1554203/+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 1553163] Re: remove limitation to only be able to report if the running kernel is no mainline kernel

There may be some concern here about apport gathering information about
the kernel not in use.  Like maybe /proc/fb is different or something.

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

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

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

Title:
  remove limitation to only be able to report if the running kernel is
  no mainline kernel

Status in apport package in Ubuntu:
  Triaged

Bug description:
  Whilst it's necessary to enforce mainline kernel bugs to be directed
  upstream immediately it's not constructive to prevent reporting issues
  of an Ubuntu kernel if a mainline kernel is running, e.g. if the
  Ubuntu kernel 4.4.0-9-generic of 16.04 doesn't start, but the
  previously installed 4.2.5 mainline does, then the user might want to
  invoke `ubuntu-bug linux-image-4.4.0-9-generic` and report against the
  Ubuntu kernel, but can't because `apport` refuses since a mainline
  kernel is running.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: apport 2.19.1-0ubuntu5
  Uname: Linux 4.4.3-040403-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CrashReports: 600:0:116:629218:2016-02-29 21:56:39.476244786 +0100:2016-02-29 
21:56:38.308256442 +0100:/var/crash/dlm.0.crash
  CurrentDesktop: Unity
  Date: Fri Mar  4 12:56:25 2016
  InstallationDate: Installed on 2013-10-17 (868 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to wily on 2015-11-19 (105 days ago)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2013-10-21T23:07:05.378054

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1553163/+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 1554202] [NEW] [webapp-container] No access to video provided despite policy_group "camera" in .apparmour file

Public bug reported:

A web app that displays a website trying to access camera and microphone
(for video conferencing, using WebRTC) will be refused to access the
camera despite the "camera" policy_group in apparmour.

The trust-store dialog pops up in the webbrowser-app for a website such
as [1], but it doesn't pop up when the website is embedded with webapp-
container.

[1] https://appear.in/test-drive

Details
---

- Detailed explanations on the mailing list: 
https://lists.launchpad.net/ubuntu-phone/msg18658.html
- Affected web app (Store): https://uappexplorer.com/app/appear-in.peter-bittner
- Affected web app (rev 2): 
https://myapps.developer.ubuntu.com/dev/click-apps/4646/rev/2/
- Bug report for affected app: https://github.com/bittner/appear-in/issues/1

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


** Tags: apparmour camera trust-store webapp-container

** Description changed:

  A web app that displays a website trying to access camera and microphone
  (for video conferencing, using WebRTC) will be refused to access the
  camera despite the "camera" policy_group in apparmour.
  
  The trust-store dialog pops up in the webbrowser-app for a website such
  as [1], but it doesn't pop up when the website is embedded with webapp-
  container.
  
  [1] https://appear.in/test-drive
  
  Details
  ---
  
  - Detailed explanations on the mailing list: 
https://lists.launchpad.net/ubuntu-phone/msg18658.html
  - Affected web app (Store): 
https://uappexplorer.com/app/appear-in.peter-bittner
  - Affected web app (rev 2): 
https://myapps.developer.ubuntu.com/dev/click-apps/4646/rev/2/
- - But report for affected app: https://github.com/bittner/appear-in/issues/1
+ - Bug report for affected app: https://github.com/bittner/appear-in/issues/1

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

Title:
  [webapp-container] No access to video provided despite policy_group
  "camera" in .apparmour file

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  A web app that displays a website trying to access camera and
  microphone (for video conferencing, using WebRTC) will be refused to
  access the camera despite the "camera" policy_group in apparmour.

  The trust-store dialog pops up in the webbrowser-app for a website
  such as [1], but it doesn't pop up when the website is embedded with
  webapp-container.

  [1] https://appear.in/test-drive

  Details
  ---

  - Detailed explanations on the mailing list: 
https://lists.launchpad.net/ubuntu-phone/msg18658.html
  - Affected web app (Store): 
https://uappexplorer.com/app/appear-in.peter-bittner
  - Affected web app (rev 2): 
https://myapps.developer.ubuntu.com/dev/click-apps/4646/rev/2/
  - Bug report for affected app: https://github.com/bittner/appear-in/issues/1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1554202/+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 1553416] Re: kernel_oops crashed with AssertionError in get_system_architecture()

** Information type changed from Private to Public

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

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

Title:
  kernel_oops crashed with AssertionError in get_system_architecture()

Status in apport package in Ubuntu:
  Triaged

Bug description:
  Fresh Install.  That was after running Software updater for the first
  time.  There is nothing abnormal.  Testing Tracker ISO Daily.  Didn't
  have any bugs with the installation.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashReports:
   640:1000:116:57629:2016-03-04 18:16:50.273453474 -0500:2016-03-04 
18:16:51.273453474 -0500:/var/crash/_usr_bin_blueman-applet.1000.crash
   640:1000:116:1216278:2016-03-04 18:26:56.085548162 -0500:2016-03-04 
18:26:57.185549119 
-0500:/var/crash/_usr_lib_x86_64-linux-gnu_xfce4_panel_wrapper-1.0.1000.crash
   600:109:116:0:2016-03-04 18:26:58.769562795 -0500:2016-03-04 
18:26:58.769562795 
-0500:/var/crash/_usr_lib_x86_64-linux-gnu_xfce4_panel_wrapper-1.0.1000.uploaded
   664:1000:116:0:2016-03-04 18:26:57.173549015 -0500:2016-03-04 
18:26:57.173549015 
-0500:/var/crash/_usr_lib_x86_64-linux-gnu_xfce4_panel_wrapper-1.0.1000.upload
   640:115:116:14869:2016-03-04 18:32:15.171937465 -0500:2016-03-04 
18:32:16.171937465 -0500:/var/crash/_usr_share_apport_kernel_oops.115.crash
  Date: Fri Mar  4 18:32:16 2016
  ExecutablePath: /usr/share/apport/kernel_oops
  InstallationDate: Installed on 2016-03-04 (0 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/kernel_oops 191362
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  PythonArgs: ['/usr/share/apport/kernel_oops', '191362']
  SourcePackage: apport
  Title: kernel_oops crashed with AssertionError in get_system_architecture()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1553416/+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 1544030] Re: wrong time of event shown from pulldown menu

confirmed. For me it's worse. The event is scheduled for 16:00 (4pm) and
shows up in the indicator at 9pm. Must have something to do with UTC
offset, as I'm set at UTC-5.

Seem like events with no reminders are not honoring UTC offset.

** Changed in: ubuntu-calendar-app
   Status: New => Confirmed

** Changed in: ubuntu-calendar-app
   Importance: Undecided => High

** Changed in: ubuntu-calendar-app
 Assignee: (unassigned) => Renato Araujo Oliveira Filho (renatofilho)

** Also affects: indicator-datetime (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: indicator-datetime (Ubuntu)
   Importance: Undecided => High

** Changed in: ubuntu-calendar-app
Milestone: None => 0.5

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

Title:
  wrong time of event shown from pulldown menu

Status in Ubuntu Calendar App:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  When scheduling an event if you select 'Reminder' -> 'No reminder',
  the time of event shown from the pulldown top menu displays a time
  which is one hour BEFORE the actual set start of the event. When
  setting  'Reminder' to any other option, both times are equal. Fix:if
  it is a feature just make an option to disable it or set both times
  equal by default.

  Also, if actual time is less than one hour before the planned start of
  the event (with reminder set to 'No Reminder'), the event disappears
  from the pulldown top menu list. Fix: don't let the event disappear
  from the pulldown top menu until its duration has expired.

  Thanks!

  Using BQ Aquaris 4.5 / OTA 9 / calendar 0.4.757

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1544030/+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 1554189] Re: Can no longer swipe between scope results

2016-03-07 Thread Niklas Wenzel

Thank you, Jean-Baptiste, for agreeing that this still makes sense to
have! :)

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

Title:
  Can no longer swipe between scope results

Status in Canonical System Image:
  New
Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Until a few days ago, when browsing through an RSS feed scope, it was
  possible to switch to the previous/next article by using swipe
  gestures. This does no longer work for me now and basically makes RSS
  feed scopes useless, as I do not want to click on each article and
  then go back to the overview again just to browse through the article
  summaries.

  $ system-image-cli -i
  current build number: 382
  device name: mako
  channel: ubuntu-touch/rc-proposed/ubuntu
  last update: 2016-03-05 18:18:13
  version version: 382
  version ubuntu: 20160305
  version device: 20160304.2
  version custom: 20160305

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1554189/+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 1553482] Re: Access to microphone is allowed even when user denies access to "video and microphone"

Same small glitch with the ellipsis (long text) in the dialog with
English, btw:

"Allow this domain to
 access your camera an...

https://appear.in/

 [   Yes   ]  [No]"

Missing text is obviously "and microphone?"

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

Title:
  Access to microphone is allowed even when user denies access to "video
  and microphone"

Status in Oxide:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  The plain web browser can access the microphone when you deny the
  permission to access camera and microphone.

  Tested / discovered with bq Aquaris E5 Ubuntu Edition, OTA-9.1
  (vegeta, latest stable as of today).

  How to Reproduce
  

  1.) Go to e.g. https://appear.in/test-drive on your Ubuntu phone (default web 
browser app)
  2.) When prompted for "Allow this domain access the camera and microphone" 
choose "No"
  3.) Click away the chat window (touch the down-arrow at right lower corner)
  4.) Touch the screen to dismiss the "help text" ("Video off" is shown 
prominently)
  5.) Touch the screen again to show the video controls, touch on the 
"microphone" icon; "Audio only" is shown on the screen
  6.) Log in to the same URL from a PC (or another phone) to verify audio works

  Other Details
  -

  Discussion on the mailing list:
  https://lists.launchpad.net/ubuntu-phone/msg18659.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1553482/+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 1554189] Re: Can no longer swipe between scope results

2016-03-07 Thread Jean-Baptiste Lallement

Horizontal swiping has actually been removed on purpose (bug 1541967)

However I agree with Nicklas, it is a pretty convenient way to browser
content of several scope. RSS is an example but it is also very useful
for any news scopes or photo scopes to quickly navigate through the
content without going back to the main view.

** Also affects: ubuntu-ux
   Importance: Undecided
   Status: New

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

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

Title:
  Can no longer swipe between scope results

Status in Canonical System Image:
  New
Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Until a few days ago, when browsing through an RSS feed scope, it was
  possible to switch to the previous/next article by using swipe
  gestures. This does no longer work for me now and basically makes RSS
  feed scopes useless, as I do not want to click on each article and
  then go back to the overview again just to browse through the article
  summaries.

  $ system-image-cli -i
  current build number: 382
  device name: mako
  channel: ubuntu-touch/rc-proposed/ubuntu
  last update: 2016-03-05 18:18:13
  version version: 382
  version ubuntu: 20160305
  version device: 20160304.2
  version custom: 20160305

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1554189/+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 1525147] Re: webapp-container needs some help

Currently, it's not possible to show `--help` neither in the Terminal
app nor in an SSH session connected to the phone.

   $ webapp-container --help
   Loading module: 'libubuntu_application_api_touch_mirclient.so.3.0.0'
   UbuntuClientIntegration: connection to Mir server failed. Check that a Mir 
server is
   running, and the correct socket is being used and is accessible. The shell 
may have
   rejected the incoming connection, so check its log file
   Aborted (core dumped)

Looks like the webapp-container binary requires a successful connection
to the Mir server. This should not be required, I believe.

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

Title:
  webapp-container needs some help

Status in webapps-sprint:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  webapp-container doesn't provide much help on the command line:

  $ webapp-container 
  Could not open manifest file:  
"/usr/share/unity-webapps/userscripts/unity-webapps-amazon/manifest.json" 
  Invalid webapps installation found:  
"/usr/share/unity-webapps/userscripts/unity-webapps-amazon" 
  Using Oxide as the web engine backend 
  QQmlComponent: Component destroyed while completion pending

To manage notifications about this bug go to:
https://bugs.launchpad.net/webapps-sprint/+bug/1525147/+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 1554189] [NEW] Can no longer swipe between scope results

2016-03-07 Thread Niklas Wenzel

Public bug reported:

Until a few days ago, when browsing through an RSS feed scope, it was
possible to switch to the previous/next article by using swipe gestures.
This does no longer work for me now and basically makes RSS feed scopes
useless, as I do not want to click on each article and then go back to
the overview again just to browse through the article summaries.

$ system-image-cli -i
current build number: 382
device name: mako
channel: ubuntu-touch/rc-proposed/ubuntu
last update: 2016-03-05 18:18:13
version version: 382
version ubuntu: 20160305
version device: 20160304.2
version custom: 20160305

** Affects: canonical-devices-system-image
 Importance: Undecided
 Status: New

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

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

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

Title:
  Can no longer swipe between scope results

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

Bug description:
  Until a few days ago, when browsing through an RSS feed scope, it was
  possible to switch to the previous/next article by using swipe
  gestures. This does no longer work for me now and basically makes RSS
  feed scopes useless, as I do not want to click on each article and
  then go back to the overview again just to browse through the article
  summaries.

  $ system-image-cli -i
  current build number: 382
  device name: mako
  channel: ubuntu-touch/rc-proposed/ubuntu
  last update: 2016-03-05 18:18:13
  version version: 382
  version ubuntu: 20160305
  version device: 20160304.2
  version custom: 20160305

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1554189/+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 1553482] Re: Access to microphone is allowed even when user denies access to "video and microphone"

MPT, apart from bug (A) I also cannot confirm bug (D), at least for the
German translation. On my device the dialog says:

"Dieser Domain den Zugriff
 zur Kamera und Mikrofo...

  https://appear.in/

[Ja]   [  Nein   ]"

Note the ellipsis, which truncates the lengthy German translation. (Missing 
part of the text is "Mikrofon geben?")
This is both fine for me though, works perfectly fine in the web-browser app 
(not in the webapp-container though, which does not show any dialog, even with 
"camera" in .apparmour).

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

Title:
  Access to microphone is allowed even when user denies access to "video
  and microphone"

Status in Oxide:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  The plain web browser can access the microphone when you deny the
  permission to access camera and microphone.

  Tested / discovered with bq Aquaris E5 Ubuntu Edition, OTA-9.1
  (vegeta, latest stable as of today).

  How to Reproduce
  

  1.) Go to e.g. https://appear.in/test-drive on your Ubuntu phone (default web 
browser app)
  2.) When prompted for "Allow this domain access the camera and microphone" 
choose "No"
  3.) Click away the chat window (touch the down-arrow at right lower corner)
  4.) Touch the screen to dismiss the "help text" ("Video off" is shown 
prominently)
  5.) Touch the screen again to show the video controls, touch on the 
"microphone" icon; "Audio only" is shown on the screen
  6.) Log in to the same URL from a PC (or another phone) to verify audio works

  Other Details
  -

  Discussion on the mailing list:
  https://lists.launchpad.net/ubuntu-phone/msg18659.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1553482/+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 1554149] Re: Asks for separate permission for microphone and camera

This works for me already on vegeta (OTA-9.1), i.e. only a single dialog
pops up asking for access to both camera and microphone. At least for
the German translation the dialog says it like this (see bug 1553482).

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

Title:
  Asks for separate permission for microphone and camera

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  0. Flash the phone.
  1. In the Browser, go to a page that asks both to record video and use the 
microphone, such as .

  What happens:
  * A prompt appears asking to record audio.
  * Another prompt appears asking to use the camera.

  What should happen:
  * Only one prompt appears, asking to record video, which includes the ability 
to use the microphone.
  

  This might not be fixable, if the Web APIs for recording video and
  audio are separate.

  If it is fixable, it might first require implementing the combined
  permission in trust-store.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1554149/+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 1554142] Re: Camera permission includes video but not microphone

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

** Changed in: trust-store (Ubuntu)
   Status: New => Confirmed

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

Title:
  Camera permission includes video but not microphone

Status in camera-app package in Ubuntu:
  Confirmed
Status in trust-store package in Ubuntu:
  Confirmed

Bug description:
  0. Flash the phone.
  1. Launch the Camera.
  2. Tap the video button.
  3. When something you want to record is about to start, tap the record button.

  What happens: 
  1. The system asks for permission to let Camera use the camera.
  2. Nothing.
  3. The system asks for permission to let Camera use the microphone — at the 
worst possible moment.

  What should happen:
  1. The system asks for permission to let Camera take photos.
  2. The system asks for permission to let Camera record video.
  3. Nothing, because the ability to record video includes the ability to use 
the microphone.
  

  The relevant trust-store permission may not exist yet. If it doesn’t,
  this needs fixing in trust-store first.

  Then, the camera app needs fixing to try recording *video* before you
  actually tap record, i.e. when you first switch to video mode, so that
  the prompt isn’t triggered later at the worst possible moment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1554142/+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 1554142] Re: Camera permission includes video but not microphone

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

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

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

Title:
  Camera permission includes video but not microphone

Status in camera-app package in Ubuntu:
  Confirmed
Status in trust-store package in Ubuntu:
  Confirmed

Bug description:
  0. Flash the phone.
  1. Launch the Camera.
  2. Tap the video button.
  3. When something you want to record is about to start, tap the record button.

  What happens: 
  1. The system asks for permission to let Camera use the camera.
  2. Nothing.
  3. The system asks for permission to let Camera use the microphone — at the 
worst possible moment.

  What should happen:
  1. The system asks for permission to let Camera take photos.
  2. The system asks for permission to let Camera record video.
  3. Nothing, because the ability to record video includes the ability to use 
the microphone.
  

  The relevant trust-store permission may not exist yet. If it doesn’t,
  this needs fixing in trust-store first.

  Then, the camera app needs fixing to try recording *video* before you
  actually tap record, i.e. when you first switch to video mode, so that
  the prompt isn’t triggered later at the worst possible moment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1554142/+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 1554149] Re: Asks for separate permission for microphone and camera

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

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

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

Title:
  Asks for separate permission for microphone and camera

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  0. Flash the phone.
  1. In the Browser, go to a page that asks both to record video and use the 
microphone, such as .

  What happens:
  * A prompt appears asking to record audio.
  * Another prompt appears asking to use the camera.

  What should happen:
  * Only one prompt appears, asking to record video, which includes the ability 
to use the microphone.
  

  This might not be fixable, if the Web APIs for recording video and
  audio are separate.

  If it is fixable, it might first require implementing the combined
  permission in trust-store.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1554149/+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 1316518] Re: [900X3G, Realtek ALC282, Mic, Internal] inverted mic not working

2016-03-07 Thread cgampert

Referring to comment #24, using hda-analyzer, I could see that:
- Converter audio stream is set to 1 on node 0x11 when the Mic jack is unplugged
- Converter audio stream is set to 1 on node 0x08 when the Mic jack is plugged 
in

Having the mic jack plugged-in, it seems  to reduce noise but it's still
the internal mic which capture sound.

Referring to comment #25, using hda-analyser, I tried to mute right
channel of node 0x11 but I couldn't see any difference...

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

Title:
  [900X3G, Realtek ALC282, Mic, Internal] inverted mic not working

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Internal Mic of Samsung Ativ book 9 (NP900X3G) is not supported
  properly.

  Stereo recording in audacity records sound from mic in L channel and only 
loud noise in R channel (phase inverted?)
  Muting R channel, and setting L channel to around 16%, in pavucontrol allows 
to record audio, but in poor quality.

  alsa-info.sh output: http://www.alsa-
  project.org/db/?f=064f0b536a1b068efd30d58c2641b5ec2348f059

  Ubuntu Gnome 14.04

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sarah  2014 F pulseaudio
    sarah  8509 F alsamixer
   /dev/snd/controlC0:  sarah  2014 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue May  6 11:55:36 2014
  InstallationDate: Installed on 2014-04-29 (6 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Internes Audio - HDA Intel PCH
  Symptom_Jack: Mic, Internal
  Symptom_Type: None of the above
  Title: [900X3G, Realtek ALC282, Mic, Internal] Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/14/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P04ADU.023.140414.PS
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP900X3G-K02DE
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SAMSUNG_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP04ADU.023.140414.PS:bd04/14/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3G:pvrP04ADU:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP900X3G-K02DE:rvrSAMSUNG_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: 900X3G
  dmi.product.version: P04ADU
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sarah  2004 F pulseaudio
   /dev/snd/controlC1:  sarah  2004 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=b4bd3914-d1c4-40f0-ba32-fb19aa9af13c
  InstallationDate: Installed on 2014-04-29 (27 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3G
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=92ac4966-692f-4e06-a1dd-da069008e861 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127.2
  StagingDrivers: rts5139
  Tags:  trusty trusty staging
  Uname: Linux 3.13.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/14/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P04ADU.023.140414.PS
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP900X3G-K02DE
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SAMSUNG_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS

[Touch-packages] [Bug 1535484] Re: package lightdm 1.10.6-0ubuntu1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1

2016-03-07 Thread Jacques Malaprade

I have the desktop background but no unity ribbon or status bar etc.

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

Title:
  package lightdm 1.10.6-0ubuntu1 failed to install/upgrade: subprocess
  installed post-removal script returned error exit status 1

Status in lightdm package in Ubuntu:
  New

Bug description:
  e: subprocess installed post-removal script returned error exit status
  1package lightdm 1.10.6-0ubuntu1 failed to install/upgrad

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.6-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30
  Uname: Linux 3.13.0-74-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.19
  AptOrdering: lightdm: Purge
  Architecture: i386
  Date: Sat Jan 16 17:35:42 2016
  DuplicateSignature: package:lightdm:1.10.6-0ubuntu1:subprocess installed 
post-removal script returned error exit status 1
  ErrorMessage: subprocess installed post-removal script returned error exit 
status 1
  InstallationDate: Installed on 2013-02-07 (1075 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  LightdmConfig:
   [SeatDefaults]
   user-session=ubuntu
   greeter-session=unity-greeter
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.5
   apt  1.0.1ubuntu2.10
  SourcePackage: lightdm
  Title: package lightdm 1.10.6-0ubuntu1 failed to install/upgrade: subprocess 
installed post-removal script returned error exit status 1
  UpgradeStatus: Upgraded to trusty on 2016-01-17 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1535484/+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 1552860] Re: [MIR] qtsystems-opensource-src