[Touch-packages] [Bug 1510570] Re: BLE pairing fail

[Martin Pitt]

@Mathieu: Is enabling "AutoEnable" something we want to do and is
generally safe?

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

Title:
  BLE pairing fail

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  On 15.10 we now have bluez 5 so we can pair BLE devices like the
  Microsoft Arc Touch Bluetooth Mouse.

  But this pairing doesn't work very well. Mouse is seen but pairing fail.
  More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5

  This is due to udev rule that use "hcitool" to power on device.
  Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used 
instead of udev rules.

  here is a commit with this parameter: 
http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138
  And a ppa to test it: 
https://code.launchpad.net/~guilhem-fr/+archive/ubuntu/bluez-autoenable

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

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

[Touch-packages] [Bug 1510640] Re: PayUI unable to log in Ubuntu One

[Jean-Baptiste Lallement]

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Alejandro J. Cura (alecu)

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

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

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

Title:
  PayUI unable to log in Ubuntu One

Status in Canonical System Image:
  In Progress
Status in Online Accounts setup for Ubuntu Touch:
  In Progress
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  In Progress

Bug description:
  Test case.
  - Find an app available for purchase in the store, by searching for 
"price:2.99" (capitalization is important, and other values may be used as 
well).
  - Tap on the "Purchase" button in the Preview.

  Expected result.
  - Verify the "Ubuntu One" log-in/register page is opened.

  Actual result.
  - Page is opened briefly and then closes, preventing log in into Ubuntu One.

  Rodney Dawes, Alberto Mardegan and me have been investigating the
  problem. We think the issue is that payui online-accounts hook is not
  updating this file:
  .local/share/accounts/applications/com.canonical.payui_payui.application
  That file have settings that remain with the old pay-ui click package
  version. online-accounts-service refuses to validate the new click
  package with the wrong versioning. Removing the file does the trick.

  current build number: 148
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en

  https://jenkins.qa.ubuntu.com/job/generic-click-
  
builder-14.09-armhf/39/artifact/output/com.canonical.payui_15.01.133_armhf.click

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

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

[Touch-packages] [Bug 1507480] Re: Privilege escalation through Python module imports

[Launchpad Bug Tracker]

This bug was fixed in the package apport - 2.19.2-0ubuntu1

---
apport (2.19.2-0ubuntu1) xenial; urgency=medium

  * New upstream release. Changes since previous snapshot:
- SECURITY FIX: When determining the path of a Python module for a program
  like "python -m module_name", avoid actually importing and running the
  module; this could lead to local root privilege escalation. Thanks to
  Gabriel Campana for discovering this and the fix!
  (CVE-2015-1341, LP: #1507480)
- test_backend_apt_dpkg.py: Reset internal apt caches between tests.
  Avoids random test failures due to leaking paths from previous test
  cases.
  * debian/control: Adjust Vcs-Bzr: for xenial branch.
  * debian/control: Drop obsolete XS-Testsuite: header.

 -- Martin Pitt   Tue, 27 Oct 2015 14:33:28
+0100

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

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

Title:
  Privilege escalation through Python module imports

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Precise:
  Fix Released
Status in apport source package in Trusty:
  Fix Released
Status in apport source package in Vivid:
  Fix Released
Status in apport source package in Wily:
  Fix Released
Status in apport source package in Xenial:
  Fix Released

Bug description:
  Gabriel Campana  reported a security
  vulnerability in Apport:

  ummary
  ===

  A privilege escalation was discovered in apport.

  
  Details
  ===

  The command line of the process triggering the coredump is checked to
  determine if it's a script. If the interpreter is Python and the first
  argument is ``-m``, the method ``_python_module_path`` is called to find
  the path of the culprit module
  (``/usr/lib/python3/dist-packages/apport/report.py``)::

  @classmethod
  def _python_module_path(klass, module):
  '''Determine path of given Python module'''

  module = module.replace('/', '.')

  try:
  m = __import__(module)
  m
  except:
  return None

  [...]

  Any Python module in ``sys.path`` can be imported because the variable
  ``module`` is under control of the attacker. It should be noted that
  ``_python_module_path`` is called with euid=0, and apport relies on the
  process name to determine if the process is an interpreter. A crash of
  Python isn't required to reach this function: any process name starting
  with ``python`` and producing a core dump is enough. As an example, the
  following bash script triggers the bug::

 #!/bin/bash

  cat < python.c
  int main(void) { *(int *)0 = 0; return 0; }
  EOF
  gcc -o python python.c
  ./python -m venv.__main__

  and results in the creation of a "lightweight virtual Python
  environment" in the root directory::

  $ ./lol.sh
  ./lol.sh: line 8:  7665 Segmentation fault  (core dumped)
  $ ls -l / | head -4
  total 100
  drw-rw   5 root root  4096 Sep 29 16:09 7665
  drwxr-xr-x   2 root root  4096 Sep 29 05:41 bin
  drwxr-xr-x   3 root root  4096 Sep 29 06:20 boot

  
  Criticity
  =

  Importing an arbitrary module is a security issue because a few standard
  modules rely on files in the home directory associated to the uid of the
  dumped process. A fully working exploit has been written (targetting
  Python2 and Python3), giving an instant root shell to the attacker.
  While the exploitation is straightforward for Python2, a bit more work
  was required to find a suitable module for Python3.

  The vulnerability seems to be limited to Ubuntu Dekstop because apport
  is disabled on Ubuntu Server.

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

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

[Touch-packages] [Bug 1501300] Re: Wily (15.10) this package got not compiled with __cxx11 support

[Matthias Goldhoorn]

If i added this somehow wrong please let me know. i provided a solution which 
should be correct to add it to mainstream.
This patch really complicates our development or our projects on a Ubuntu 15.10 
target.

Moreover the proposed patch should be review able by any Ubuntu
maintainer, the problem is not llvm specific (renamed from gcc-x.x to
gcc-x in ubntu15.10). It makes for me a really not good impression for
(ubuntu in general) that a review of a straight forward patch took so
long

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

Title:
  Wily (15.10) this package got not compiled with __cxx11 support

Status in llvm-toolchain-3.4 package in Ubuntu:
  Confirmed

Bug description:
  This packages does not contain any __cxx11 symbols when installed. This 
causes the problem that user-space applications cannot link successfully to it.
  Recompile the (untouched) dpkg source package on the same machine and 
installing it solved the problem.

  There seems something in the package generation broken.

  Steps to reproduce try to compile the attached minimal example
  https://github.com/goldhoorn/clang-sandbox

  
  Errors:
  CMakeFiles/main.dir/main.cpp.o: In function `foo()':
  /tmp/clang-sandbox/main.cpp:25: undefined reference to 
`clang::NamedDecl::getQualifiedNameAsString[abi:cxx11]() const'
  CMakeFiles/main.dir/main.cpp.o: In function 
`clang::QualType::getAsString[abi:cxx11](clang::SplitQualType)':
  /usr/lib/llvm-3.4/include/clang/AST/Type.h:868: undefined reference to 
`clang::QualType::getAsString[abi:cxx11](clang::Type const*, clang::Qualifiers)'
  CMakeFiles/main.dir/main.cpp.o: In function 
`clang::ast_matchers::internal::matcher_matchesName0Matcher::matches(clang::NamedDecl
 const&, clang::ast_matchers::internal::ASTMatchFinder*, 
clang::ast_matchers::internal::BoundNodesTreeBuilder*) const':
  /usr/lib/llvm-3.4/include/clang/ASTMatchers/ASTMatchers.h:1439: undefined 
reference to `clang::NamedDecl::getQualifiedNameAsString[abi:cxx11]() const'
  CMakeFiles/main.dir/main.cpp.o: In function 
`clang::ast_matchers::internal::matcher_hasName0Matcher::matches(clang::NamedDecl
 const&, clang::ast_matchers::internal::ASTMatchFinder*, 
clang::ast_matchers::internal::BoundNodesTreeBuilder*) const':
  /usr/lib/llvm-3.4/include/clang/ASTMatchers/ASTMatchers.h:1411: undefined 
reference to `clang::NamedDecl::getQualifiedNameAsString[abi:cxx11]() const'
  /usr/lib/llvm-3.4/lib/libclangAST.a(ExprConstant.o): In function 
`handleIntIntBinOp((anonymous namespace)::EvalInfo&, clang::Expr const*, 
llvm::APSInt const&, clang::BinaryOperatorKind, llvm::APSInt, llvm::APSInt&)':
  (.text+0x6a35): undefined reference to `llvm::APInt::toString(unsigned int, 
bool) const'
  /usr/lib/llvm-3.4/lib/libclangAST.a(StmtPrinter.o): In function `(anonymous 
namespace)::StmtPrinter::VisitIntegerLiteral(clang::IntegerLiteral*) [clone 
.isra.302]':

  ...

  This example is workign on privious ubuntus and debians

  Sysinfo:
  Description:  Ubuntu Wily Werewolf (development branch)
  Release:  15.10
  In a VirtualBox

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.4/+bug/1501300/+subscriptions

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

[Touch-packages] [Bug 1510816] [NEW] libdrm 2.4.60 causes Chromium to be unstable

[Sjoerd Langkemper]

Public bug reported:

I am experiencing issues where libdrm 2.4.60 that is shipped with Ubuntu
15.04 causes Chromium to freeze the whole system. It happens multiple
times a day, and I also have some coworkers that experience this. A
solution would be to ship any version other than 2.4.60 with vivid.
Since I use libdrm 2.4.64 from wily I have no problems anymore.

Related bugs:
https://code.google.com/p/chromium/issues/detail?id=513685
https://bugs.freedesktop.org/show_bug.cgi?id=89842

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

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

Title:
  libdrm 2.4.60 causes Chromium to be unstable

Status in libdrm package in Ubuntu:
  New

Bug description:
  I am experiencing issues where libdrm 2.4.60 that is shipped with
  Ubuntu 15.04 causes Chromium to freeze the whole system. It happens
  multiple times a day, and I also have some coworkers that experience
  this. A solution would be to ship any version other than 2.4.60 with
  vivid. Since I use libdrm 2.4.64 from wily I have no problems anymore.

  Related bugs:
  https://code.google.com/p/chromium/issues/detail?id=513685
  https://bugs.freedesktop.org/show_bug.cgi?id=89842

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

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

[Touch-packages] [Bug 1509747] Re: Intermittent lxc failures on wily

[Martin Pitt]

I'm running wily LXC on wily (or now xenial) pretty much every day, so
this isn't very straightforward to reproduce. lxc's own autopkgtests
also do that, and they run in the cloud in a wily instance, pretty
similar to your's.

I tried a wily cloud image, created an LXC container, and started it,
which works as expected:

  nova boot --flavor m1.small --image 
ubuntu/ubuntu-wily-daily-amd64-server-20151026-disk1.img test1
  ssh [... into test1 instance ]
  sudo lxc-create -n w1 -t download -- -d ubuntu -r wily -a amd64
  sudo lxc-start -n w1 -F

Thanks for the strace; there's nothing unusual in it, so the reason why
it thinks it fails must be somewhere else.

But either way: You can set "ExecStart=/bin/false" in systemd-update-
utmp-runlevel.service to force the unit to fail, but that's in no way
fatal to the container; it boots, and you just have this one failed
unit. Nothing else depends on this, this will just make "runlevel" spit
out an updated value, so that legacy software becomes a bit more
compatible. So while that unit certainly should not fail (this is a
bug), this is almost surely *not* the reason what breaks you, so this is
far from 'critical'.

I had a look at your user-data: this dance around a temporary systemd
unit to shut down the machine is rather complex. You can just have a
runcmd like

 - (while [ ! -e /var/lib/cloud/instance/boot-finished ]; do sleep 1;
done; shutdown -P now) &

It also looks wrong: your runcmd *immediately* starts the unit, which
(tries to) shutdown the container while cloud-init is still running. My
hunch is that calling "shutdown" at this point will hang or fail as
there is still the boot transaction running, so this smells like a
deadlock which would explain why cloud-init never finishes.

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

Title:
  Intermittent lxc failures on wily

Status in juju-core:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Frequently, when creating an lxc container on wily (either through
  --to lxc:#, or using the local provider on wily), the template never
  stops and errors out here:

  [ 2300.885573] cloud-init[2758]: Cloud-init v. 0.7.7 running 'modules:final' 
at Sun, 25 Oct 2015 00:28:57 +. Up 182 seconds.
  [ 2300.886101] cloud-init[2758]: Cloud-init v. 0.7.7 finished at Sun, 25 Oct 
2015 00:29:03 +. Datasource DataSourceNoCloudNet 
[seed=/var/lib/cloud/seed/nocloud-net][dsmode=net].  Up 189 seconds
  [  OK  ] Started Execute cloud user/final scripts.
  [  OK  ] Reached target Multi-User System.
  [  OK  ] Reached target Graphical Interface.
   Starting Update UTMP about System Runlevel Changes...
  [  OK  ] Started /dev/initctl Compatibility Daemon.
  [FAILED] Failed to start Update UTMP about System Runlevel Changes.
  See 'systemctl status systemd-update-utmp-runlevel.service' for details.

  Attaching to the container and running the above command yields:

  ubuntu@cherylj-wily-local-lxc:~$ sudo lxc-attach --name juju-wily-lxc-template
  root@juju-wily-lxc-template:~# systemctl status 
systemd-update-utmp-runlevel.service
  ● systemd-update-utmp-runlevel.service - Update UTMP about System Runlevel 
Changes
 Loaded: loaded (/lib/systemd/system/systemd-update-utmp-runlevel.service; 
static; vendor preset: enabled)
 Active: failed (Result: exit-code) since Sun 2015-10-25 00:30:29 UTC; 2h 
23min ago
   Docs: man:systemd-update-utmp.service(8)
 man:utmp(5)
Process: 3963 ExecStart=/lib/systemd/systemd-update-utmp runlevel 
(code=exited, status=1/FAILURE)
   Main PID: 3963 (code=exited, status=1/FAILURE)

  Oct 25 00:29:46 juju-wily-lxc-template systemd[1]: Starting Update UTMP about 
System Runlevel Changes...
  Oct 25 00:30:29 juju-wily-lxc-template systemd[1]: 
systemd-update-utmp-runlevel.service: Main process exited, code=exited, 
status=1/FAILURE
  Oct 25 00:30:30 juju-wily-lxc-template systemd[1]: Failed to start Update 
UTMP about System Runlevel Changes.
  Oct 25 00:30:30 juju-wily-lxc-template systemd[1]: 
systemd-update-utmp-runlevel.service: Unit entered failed state.
  Oct 25 00:30:30 juju-wily-lxc-template systemd[1]: 
systemd-update-utmp-runlevel.service: Failed with result 'exit-code'.

  
  I have seen this on ec2 and in canonistack.  The canonistack machine is 
available for further debugging.  Ping me for access.

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1509747/+subscriptions

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

[Touch-packages] [Bug 1510382] Re: Window contents become slightly blurry after moving/resizing the window

[Daniel van Vugt]

** Description changed:

  Using Unity8 on wily desktop, window contents become slightly blurry
  after moving/resizing the window.
  
  I first noticed this in Xmir. But now see you can reproduce it just by
- opening System Settings.
+ opening System Settings and moving/resizing the window.

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

Title:
  Window contents become slightly blurry after moving/resizing the
  window

Status in QtMir:
  New
Status in qtmir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Using Unity8 on wily desktop, window contents become slightly blurry
  after moving/resizing the window.

  I first noticed this in Xmir. But now see you can reproduce it just by
  opening System Settings and moving/resizing the window.

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

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

[Touch-packages] [Bug 1510821] [NEW] Ubuntu Freezes With No Obvious Reason

[Plamen]

Public bug reported:

I am dev and I know how this sounds but at a certain periods ubuntu
freezes entirely. The only exit is the power button. I dont know what
could be helpful information in this case so I will write everything I
noticed so far (sry for the spam).

This used to happen a lot while building with Android Studio but lately
it freezes even when the studio is closed. The last time it happened
after I closed(or tried to) Chrome tab while updating ubuntu. This
behavior started a few weeks ago. I haven't updated to 15.10 at the time
so I did. But it still continued to block. I thought it might be from
the video driver so I switched from nvidia-340 to nouveau with no
success.

I cant find anything helpful in kern.log if its needed I can attach the
log just before the freeze. What I find strange is in the syslog. At the
time of the freeze it is filled with NULs. See attached image
syslog.png. The time of the freeze was around 8:57. At this point the
mouse cursor was active but there was nothing that reacted to my
desperate clicks or keyboard shortcuts. After awhile the mouse stops as
well and there is nothing I can do but the power button.

Is there some other log that could be helpful or anything else I can do?


Thank you in advance

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic x86_64
ApportVersion: 2.19.1-0ubuntu3
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Wed Oct 28 09:36:12 2015
DistUpgraded: 2015-10-27 13:34:15,610 DEBUG enabling apt cron job
DistroCodename: wily
DistroVariant: ubuntu
DkmsStatus:
 vboxhost, 5.0.2, 3.19.0-31-generic, x86_64: installed
 vboxhost, 5.0.2, 4.2.0-16-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation G92 [GeForce GTS 250] [10de:0615] (rev a2) (prog-if 00 [VGA 
controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:82e6]
InstallationDate: Installed on 2015-06-17 (132 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=db78bb87-80bc-4175-935a-18f69d5c471d ro quiet splash vt.handoff=7
SourcePackage: xorg
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: Upgraded to wily on 2015-10-27 (0 days ago)
dmi.bios.date: 05/13/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0401
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M4A78-AM
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0401:bd05/13/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A78-AM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.64-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
xserver.bootTime: Wed Oct 28 10:00:45 2015
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 input USB OPTICAL MOUSE   MOUSE, id 8
 inputAT Translated Set 2 keyboard KEYBOARD, id 9
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
 NOUVEAU(0): [COPY] failed to allocate class.
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.17.2-1ubuntu9
xserver.video_driver: nouveau

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


** Tags: amd64 apport-bug ubuntu wily

** Attachment added: "Syslog just before the freeze"
   https://bugs.launchpad.net/bugs/1510821/+attachment/4507300/+files/syslog.png

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

Title:
  Ubuntu Freezes With No Obvious Reason

Status in xorg package in Ubuntu:
  New

[Touch-packages] [Bug 1510648] Re: [Ubuntu 15.10] Realtek RTL8723AE cannot connect to WPA2/AES

[jean-christophe manciot]

Some additional information:
- no similar issue on the same laptop with Ubuntu ***desktop*** 15.04/15.10
- same issue with Ubuntu ***server*** 15.04/15.10

I've modified the title to reflect these informations.

** Summary changed:

- [Ubuntu 15.10] Realtek RTL8723AE cannot connect to WPA2/AES 
+ [Ubuntu Server 15.04/15.10] Realtek RTL8723AE cannot connect to WPA2/AES

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

Title:
  [Ubuntu Server 15.04/15.10] Realtek RTL8723AE cannot connect to
  WPA2/AES

Status in network-manager package in Ubuntu:
  New

Bug description:
  Ubuntu Gnome Server 15.10 - 4.2.0-16-generic - network-manager-gnome  0.9.10.1
  
---
  sudo systemctl status NetworkManager.service
  ● NetworkManager.service - Network Manager
 Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: enabled)
 Active: active (running) since Tue 2015-10-27 12:15:32 CET; 1min 17s ago
   Main PID: 1204 (NetworkManager)
 CGroup: /system.slice/NetworkManager.service
 └─1204 /usr/sbin/NetworkManager --no-daemon

  Oct 27 12:15:59 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:00 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:00 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:02 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:03 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:03 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:03 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:05 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:20 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed
  Oct 27 12:16:20 msi-ge60-ubuntu NetworkManager[1204]: 
nm_urfkill_get_wlan_state: assertion 'self->wlan_proxy != NULL' failed

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

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

[Touch-packages] [Bug 1509747] Re: Intermittent lxc failures on wily

[Martin Pitt]

I tried that user-data (minus the extra packages: and
ssh_authorized_keys: as they are irrelevant) on the current wily cloud
image with QEMU, and I get:

[   13.799851] cloud-init[1010]: Cloud-init v. 0.7.7 running 'modules:config' 
at Wed, 28 Oct 2015 08:11:33 +. Up 13.12 seconds.
[   14.189822] cloud-init[1088]: + mkdir -p 
/var/lib/juju/init/juju-template-restart
[   14.192818] cloud-init[1088]: + cat
[   14.194669] cloud-init[1088]: + /bin/systemctl link 
/var/lib/juju/init/juju-template-restart/juju-template-restart.service
[   14.208282] cloud-init[1088]: Created symlink from 
/etc/systemd/system/juju-template-restart.service to 
/var/lib/juju/init/juju-template-restart/juju-template-restart.service.
[   14.271740] cloud-init[1088]: + /bin/systemctl daemon-reload
[   14.342206] cloud-init[1088]: + /bin/systemctl enable 
/var/lib/juju/init/juju-template-restart/juju-template-restart.service
[   14.348218] cloud-init[1088]: Created symlink from 
/etc/systemd/system/multi-user.target.wants/juju-template-restart.service to 
/var/lib/juju/init/juju-template-restart/juju-template-restart.service.
[   14.416085] cloud-init[1088]: + /bin/systemctl start 
juju-template-restart.service
Cloud-init 0.7.7 received SIGTERM, exiting...
  Filename: /usr/lib/python3.4/logging/__init__.py
  Function: handle
  Line number: 855
Filename: /usr/lib/python3.4/logging/__init__.py
Function: callHandlers
Line number: 1486
  Filename: /usr/lib/python3.4/logging/__init__.py
  Function: handle
  Line number: 1424
[   16.204669] reboot: Power down

So that's a different timing/behaviour than your's, but it shows the
race condition with this juju-template-restart.service. Reopening juju
task for that. Can you please try to change the runcmd to drop all this
and just use

   - (while [ ! -e /var/lib/cloud/instance/boot-finished ]; do sleep 1;
done; shutdown -P now) &

?

Note that more recent versions of cloud-init have better support for
this (http://cloudinit.readthedocs.org/en/latest/topics/examples.html
#reboot-poweroff-when-finished), but I believe that's not yet available
on trusty; hence in autopkgtest I use the above while loop in the
background instead of "power_state:".

** Changed in: juju-core
   Status: Invalid => Confirmed

** Summary changed:

- Intermittent lxc failures on wily
+ Intermittent lxc failures on wily, juju-template-restart.service is racy

** Summary changed:

- Intermittent lxc failures on wily, juju-template-restart.service is racy
+ Intermittent lxc failures on wily, juju-template-restart.service race 
condition

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

Title:
  Intermittent lxc failures on wily, juju-template-restart.service race
  condition

Status in juju-core:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Frequently, when creating an lxc container on wily (either through
  --to lxc:#, or using the local provider on wily), the template never
  stops and errors out here:

  [ 2300.885573] cloud-init[2758]: Cloud-init v. 0.7.7 running 'modules:final' 
at Sun, 25 Oct 2015 00:28:57 +. Up 182 seconds.
  [ 2300.886101] cloud-init[2758]: Cloud-init v. 0.7.7 finished at Sun, 25 Oct 
2015 00:29:03 +. Datasource DataSourceNoCloudNet 
[seed=/var/lib/cloud/seed/nocloud-net][dsmode=net].  Up 189 seconds
  [  OK  ] Started Execute cloud user/final scripts.
  [  OK  ] Reached target Multi-User System.
  [  OK  ] Reached target Graphical Interface.
   Starting Update UTMP about System Runlevel Changes...
  [  OK  ] Started /dev/initctl Compatibility Daemon.
  [FAILED] Failed to start Update UTMP about System Runlevel Changes.
  See 'systemctl status systemd-update-utmp-runlevel.service' for details.

  Attaching to the container and running the above command yields:

  ubuntu@cherylj-wily-local-lxc:~$ sudo lxc-attach --name juju-wily-lxc-template
  root@juju-wily-lxc-template:~# systemctl status 
systemd-update-utmp-runlevel.service
  ● systemd-update-utmp-runlevel.service - Update UTMP about System Runlevel 
Changes
 Loaded: loaded (/lib/systemd/system/systemd-update-utmp-runlevel.service; 
static; vendor preset: enabled)
 Active: failed (Result: exit-code) since Sun 2015-10-25 00:30:29 UTC; 2h 
23min ago
   Docs: man:systemd-update-utmp.service(8)
 man:utmp(5)
Process: 3963 ExecStart=/lib/systemd/systemd-update-utmp runlevel 
(code=exited, status=1/FAILURE)
   Main PID: 3963 (code=exited, status=1/FAILURE)

  Oct 25 00:29:46 juju-wily-lxc-template systemd[1]: Starting Update UTMP about 
System Runlevel Changes...
  Oct 25 00:30:29 juju-wily-lxc-template systemd[1]: 
systemd-update-utmp-runlevel.service: Main process exited, code=exited, 
status=1/FAILURE
  Oct 25 00:30:30 juju-wily-lxc-template systemd[1]: Failed to start Update 
UTMP about System Runlevel Changes.

[Touch-packages] [Bug 1510824] [NEW] PolkitAgentSession ignores multiline output (with pam_vas)

[Dariusz Gadomski]

Public bug reported:

There is an error observed when Ubuntu is configured to perform
authentication via pam_vas (Vintela Authentication Services by Dell) in
a disconnected mode (using cached authentication).

Steps to reproduce:
1. Configure pam_vas client authenticating to a remote server.
2. Perform authentication to cache the credentials.
3. Disconnect from the network where the server is reachable (to force using 
cached information).
4. Perform an action requiring polkit authentication.

Expected result:
Authentication succeeds accompanied by the following message "You have logged 
in using cached account information.  Some network services will be 
unavailable".

Actual result:
Authentication fails accompanied by the following message "You have logged in 
using cached account information.  Some network services will be unavailable".

Probable cause:
The PolkitAgentSession part of polkit is designed to interpret only 1-line 
output, while interaction with pam_vas in the above scenario triggers helper to 
produce the following 2-line output:
PAM_TEXT_INFO You have logged in using cached account information.  Some 
network services will be unavailable
SUCCESS

The 'SUCCESS' part is never read so the authentication never ends
successfully.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: policykit-1 0.105-4ubuntu2.14.04.1
ProcVersionSignature: Ubuntu 3.16.0-52.71~14.04.1-generic 3.16.7-ckt18
Uname: Linux 3.16.0-52-generic x86_64
NonfreeKernelModules: nvidia zfs zunicode zcommon znvpair zavl
ApportVersion: 2.14.1-0ubuntu3.18
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Oct 28 09:01:37 2015
InstallationDate: Installed on 2015-04-13 (197 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
SourcePackage: policykit-1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: policykit-1 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug sts trusty

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

Title:
  PolkitAgentSession ignores multiline output (with pam_vas)

Status in policykit-1 package in Ubuntu:
  New

Bug description:
  There is an error observed when Ubuntu is configured to perform
  authentication via pam_vas (Vintela Authentication Services by Dell)
  in a disconnected mode (using cached authentication).

  Steps to reproduce:
  1. Configure pam_vas client authenticating to a remote server.
  2. Perform authentication to cache the credentials.
  3. Disconnect from the network where the server is reachable (to force using 
cached information).
  4. Perform an action requiring polkit authentication.

  Expected result:
  Authentication succeeds accompanied by the following message "You have logged 
in using cached account information.  Some network services will be 
unavailable".

  Actual result:
  Authentication fails accompanied by the following message "You have logged in 
using cached account information.  Some network services will be unavailable".

  Probable cause:
  The PolkitAgentSession part of polkit is designed to interpret only 1-line 
output, while interaction with pam_vas in the above scenario triggers helper to 
produce the following 2-line output:
  PAM_TEXT_INFO You have logged in using cached account information.  Some 
network services will be unavailable
  SUCCESS

  The 'SUCCESS' part is never read so the authentication never ends
  successfully.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: policykit-1 0.105-4ubuntu2.14.04.1
  ProcVersionSignature: Ubuntu 3.16.0-52.71~14.04.1-generic 3.16.7-ckt18
  Uname: Linux 3.16.0-52-generic x86_64
  NonfreeKernelModules: nvidia zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Oct 28 09:01:37 2015
  InstallationDate: Installed on 2015-04-13 (197 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: policykit-1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1510824/+subscriptions

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

[Touch-packages] [Bug 1509747] Re: Intermittent lxc failures on wily, juju-template-restart.service race condition

[Martin Pitt]

I read  up on juju-local, and tried this in a clean wily amd64 cloud
image:

sudo apt install -y juju-local
juju init
juju switch local
juju bootstrap

I'm not entirely sure what I'm supposed to do now; there is a "juju
machine add" command, but this doesn't accept custom user data. But it
sounds like the above user data will already be created by juju itself?

So I ran

  sudo juju machine add

and get

$ juju status
environment: local
available-version: 1.24.7
machines:
  "0":
agent-state: started
agent-version: 1.24.6.1
dns-name: localhost
instance-id: localhost
series: wily
state-server-member-status: has-vote
  "1":
instance-id: pending
series: trusty
services: {}

But there's no new machine anywhere, just the template from
bootstrapping:


$ sudo lxc-ls -f
NAME  STATEIPV4  IPV6  GROUPS  AUTOSTART  

juju-trusty-lxc-template  STOPPED  - - -   NO 


... and now I just realize that this is trusty, not wily. So this should at 
least work, no? In trusty we don't have systemd yet.

/var/log/juju-ubuntu-local/all-machines.log just spits out a series of

machine-0: 2015-10-28 08:27:55 ERROR juju.worker.diskmanager
lsblk.go:116 error checking if "fd0" is in use: open /dev/fd0: no such
device or address

but doesn't otherwise seem to do anything.

For completeness I retried the above steps with wily, and set "default-
series: wily" in ~/.juju/environments.yaml before bootstrap. But now
after bootstrap it doesn't even build a template container,
/var/lib/lxc/ stays empty and "sudo tail -f /var/log/juju-ubuntu-
local/*" again just shows a series of these /dev/fd0 checks. I gave up
after 10 minutes.

While these look like bugs, they look unrelated to this issue. Can you
please tell me how this bug can be reproduced starting from a fresh wily
install?


** Changed in: systemd (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Intermittent lxc failures on wily, juju-template-restart.service race
  condition

Status in juju-core:
  Confirmed
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Frequently, when creating an lxc container on wily (either through
  --to lxc:#, or using the local provider on wily), the template never
  stops and errors out here:

  [ 2300.885573] cloud-init[2758]: Cloud-init v. 0.7.7 running 'modules:final' 
at Sun, 25 Oct 2015 00:28:57 +. Up 182 seconds.
  [ 2300.886101] cloud-init[2758]: Cloud-init v. 0.7.7 finished at Sun, 25 Oct 
2015 00:29:03 +. Datasource DataSourceNoCloudNet 
[seed=/var/lib/cloud/seed/nocloud-net][dsmode=net].  Up 189 seconds
  [  OK  ] Started Execute cloud user/final scripts.
  [  OK  ] Reached target Multi-User System.
  [  OK  ] Reached target Graphical Interface.
   Starting Update UTMP about System Runlevel Changes...
  [  OK  ] Started /dev/initctl Compatibility Daemon.
  [FAILED] Failed to start Update UTMP about System Runlevel Changes.
  See 'systemctl status systemd-update-utmp-runlevel.service' for details.

  Attaching to the container and running the above command yields:

  ubuntu@cherylj-wily-local-lxc:~$ sudo lxc-attach --name juju-wily-lxc-template
  root@juju-wily-lxc-template:~# systemctl status 
systemd-update-utmp-runlevel.service
  ● systemd-update-utmp-runlevel.service - Update UTMP about System Runlevel 
Changes
 Loaded: loaded (/lib/systemd/system/systemd-update-utmp-runlevel.service; 
static; vendor preset: enabled)
 Active: failed (Result: exit-code) since Sun 2015-10-25 00:30:29 UTC; 2h 
23min ago
   Docs: man:systemd-update-utmp.service(8)
 man:utmp(5)
Process: 3963 ExecStart=/lib/systemd/systemd-update-utmp runlevel 
(code=exited, status=1/FAILURE)
   Main PID: 3963 (code=exited, status=1/FAILURE)

  Oct 25 00:29:46 juju-wily-lxc-template systemd[1]: Starting Update UTMP about 
System Runlevel Changes...
  Oct 25 00:30:29 juju-wily-lxc-template systemd[1]: 
systemd-update-utmp-runlevel.service: Main process exited, code=exited, 
status=1/FAILURE
  Oct 25 00:30:30 juju-wily-lxc-template systemd[1]: Failed to start Update 
UTMP about System Runlevel Changes.
  Oct 25 00:30:30 juju-wily-lxc-template systemd[1]: 
systemd-update-utmp-runlevel.service: Unit entered failed state.
  Oct 25 00:30:30 juju-wily-lxc-template systemd[1]: 
systemd-update-utmp-runlevel.service: Failed with result 'exit-code'.

  
  I have seen this on ec2 and in canonistack.  The canonistack machine is 
available for further debugging.  Ping me for access.

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1509747/+subscriptions

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

[Touch-packages] [Bug 1510769] [NEW] app icon is old

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

New icon shows on Gnome.
However, old icon shows on Unity.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: totem 3.16.4-0ubuntu2
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Oct 28 11:56:37 2015
InstallationDate: Installed on 2015-09-23 (34 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
SourcePackage: totem
UpgradeStatus: Upgraded to wily on 2015-10-25 (3 days ago)

** Affects: humanity-icon-theme (Ubuntu)
 Importance: Low
 Status: Confirmed


** Tags: amd64 apport-bug wily
-- 
app icon is old
https://bugs.launchpad.net/bugs/1510769
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to humanity-icon-theme in Ubuntu.

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

[Touch-packages] [Bug 1510640] Re: PayUI unable to log in Ubuntu One

[Launchpad Bug Tracker]

** Branch linked: lp:~mardy/ubuntu-system-settings-online-accounts
/hooks-timestamp

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

Title:
  PayUI unable to log in Ubuntu One

Status in Canonical System Image:
  In Progress
Status in Online Accounts setup for Ubuntu Touch:
  In Progress
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  In Progress

Bug description:
  Test case.
  - Find an app available for purchase in the store, by searching for 
"price:2.99" (capitalization is important, and other values may be used as 
well).
  - Tap on the "Purchase" button in the Preview.

  Expected result.
  - Verify the "Ubuntu One" log-in/register page is opened.

  Actual result.
  - Page is opened briefly and then closes, preventing log in into Ubuntu One.

  Rodney Dawes, Alberto Mardegan and me have been investigating the
  problem. We think the issue is that payui online-accounts hook is not
  updating this file:
  .local/share/accounts/applications/com.canonical.payui_payui.application
  That file have settings that remain with the old pay-ui click package
  version. online-accounts-service refuses to validate the new click
  package with the wrong versioning. Removing the file does the trick.

  current build number: 148
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en

  https://jenkins.qa.ubuntu.com/job/generic-click-
  
builder-14.09-armhf/39/artifact/output/com.canonical.payui_15.01.133_armhf.click

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

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

[Touch-packages] [Bug 1510769] Re: app icon is old

[Sebastien Bacher]

Thanks, that's a theme issue, humanity ships a totem icon

** Package changed: totem (Ubuntu) => humanity-icon-theme (Ubuntu)

** Changed in: humanity-icon-theme (Ubuntu)
   Importance: Undecided => Low

** Changed in: humanity-icon-theme (Ubuntu)
   Status: New => Confirmed

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

Title:
  app icon is old

Status in humanity-icon-theme package in Ubuntu:
  Confirmed

Bug description:
  New icon shows on Gnome.
  However, old icon shows on Unity.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: totem 3.16.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Oct 28 11:56:37 2015
  InstallationDate: Installed on 2015-09-23 (34 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: totem
  UpgradeStatus: Upgraded to wily on 2015-10-25 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1510769/+subscriptions

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

[Touch-packages] [Bug 1510839] [NEW] do-release-upgrade to Wily hangs

[Ferry Toth]

Public bug reported:

I have experienced a hang during the upgrade to Wily on 2 separate
machines, probably at the same point.

The upgrade is started from Muon, so the release upgrade uses:
do-release-upgrade -m desktop -f DistUpgradeViewKDE -d

The hangs appears to occur on dpkg trying to configure a bunch of
packages. The hanging dpkg uses 0% CPU, and appears to be waiting for
something.

Killing the upgrade and running:
sudo dpkg --configure -a

continues configuring the packages, until it requests user input when
configuring dll.conf (part of saned).

After this I need to clean up unneeded packages manually, but furtunaly
are able to reboot.

** Affects: ubuntu-release-upgrader (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: 15.10 kubuntu

** Package changed: apport (Ubuntu) => ubuntu-release-upgrader (Ubuntu)

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

Title:
  do-release-upgrade to Wily hangs

Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  I have experienced a hang during the upgrade to Wily on 2 separate
  machines, probably at the same point.

  The upgrade is started from Muon, so the release upgrade uses:
  do-release-upgrade -m desktop -f DistUpgradeViewKDE -d

  The hangs appears to occur on dpkg trying to configure a bunch of
  packages. The hanging dpkg uses 0% CPU, and appears to be waiting for
  something.

  Killing the upgrade and running:
  sudo dpkg --configure -a

  continues configuring the packages, until it requests user input when
  configuring dll.conf (part of saned).

  After this I need to clean up unneeded packages manually, but
  furtunaly are able to reboot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1510839/+subscriptions

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

[Touch-packages] [Bug 1404068] Re: No internet connection with Huawei E3272 4G modem

[Mantas Kriaučiūnas]

** Also affects: baltix-default-settings
   Importance: Undecided
   Status: New

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

Title:
  No internet connection with Huawei E3272 4G modem

Status in Default settings and artwork for Baltix OS:
  New
Status in ModemManager:
  Incomplete
Status in modemmanager package in Ubuntu:
  Incomplete
Status in usb-modeswitch-data package in Ubuntu:
  Invalid
Status in usb-modeswitch-data package in Debian:
  Fix Released

Bug description:
  There is no internet connection. My mobile broadband LTE modem is Huawei 
E3272. Attached a syslog.
  Ubuntu 14.10
  modemmanager 1.2.0-1

  This might contain useful information:
  http://askubuntu.com/questions/525965/huawei-e3272-ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/baltix-default-settings/+bug/1404068/+subscriptions

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

[Touch-packages] [Bug 1510570] Re: BLE pairing fail

[Guilhem Lettron]

@Martin, changelog from 5.35 is quite explicit:
"
A noteworthy new feature is the ability to configure bluetoothd to 
automatically enable (power on) all new adapters. One use of this is to replace 
unreliable “hciconfig hci0 up” commands that some distributions use in their 
init/udev scripts. The feature can be enabled by having AutoEnable=true under 
the [Policy] section of /etc/bluetooth/main.conf.
"
http://www.bluez.org/release-of-bluez-5-35/

But yes more advice are welcome :)

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

Title:
  BLE pairing fail

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  On 15.10 we now have bluez 5 so we can pair BLE devices like the
  Microsoft Arc Touch Bluetooth Mouse.

  But this pairing doesn't work very well. Mouse is seen but pairing fail.
  More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5

  This is due to udev rule that use "hcitool" to power on device.
  Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used 
instead of udev rules.

  here is a commit with this parameter: 
http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138
  And a ppa to test it: 
https://code.launchpad.net/~guilhem-fr/+archive/ubuntu/bluez-autoenable

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

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

[Touch-packages] [Bug 1510769] Re: totem's app icon is old

[Kenichi Ito]

** Summary changed:

- app icon is old
+ totem's app icon is old

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

Title:
  totem's app icon is old

Status in humanity-icon-theme package in Ubuntu:
  Confirmed

Bug description:
  New icon shows on Gnome.
  However, old icon shows on Unity.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: totem 3.16.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Oct 28 11:56:37 2015
  InstallationDate: Installed on 2015-09-23 (34 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: totem
  UpgradeStatus: Upgraded to wily on 2015-10-25 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1510769/+subscriptions

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

[Touch-packages] [Bug 1510824] Re: PolkitAgentSession ignores multiline output (with pam_vas)

[Louis Bouchard]

** Also affects: policykit-1 (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Also affects: policykit-1 (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: policykit-1 (Ubuntu Vivid)
   Importance: Undecided
   Status: New

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

Title:
  PolkitAgentSession ignores multiline output (with pam_vas)

Status in policykit-1 package in Ubuntu:
  New
Status in policykit-1 source package in Trusty:
  New
Status in policykit-1 source package in Vivid:
  New
Status in policykit-1 source package in Wily:
  New

Bug description:
  There is an error observed when Ubuntu is configured to perform
  authentication via pam_vas (Vintela Authentication Services by Dell)
  in a disconnected mode (using cached authentication).

  Steps to reproduce:
  1. Configure pam_vas client authenticating to a remote server.
  2. Perform authentication to cache the credentials.
  3. Disconnect from the network where the server is reachable (to force using 
cached information).
  4. Perform an action requiring polkit authentication.

  Expected result:
  Authentication succeeds accompanied by the following message "You have logged 
in using cached account information.  Some network services will be 
unavailable".

  Actual result:
  Authentication fails accompanied by the following message "You have logged in 
using cached account information.  Some network services will be unavailable".

  Probable cause:
  The PolkitAgentSession part of polkit is designed to interpret only 1-line 
output, while interaction with pam_vas in the above scenario triggers helper to 
produce the following 2-line output:
  PAM_TEXT_INFO You have logged in using cached account information.  Some 
network services will be unavailable
  SUCCESS

  The 'SUCCESS' part is never read so the authentication never ends
  successfully.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: policykit-1 0.105-4ubuntu2.14.04.1
  ProcVersionSignature: Ubuntu 3.16.0-52.71~14.04.1-generic 3.16.7-ckt18
  Uname: Linux 3.16.0-52-generic x86_64
  NonfreeKernelModules: nvidia zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Oct 28 09:01:37 2015
  InstallationDate: Installed on 2015-04-13 (197 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: policykit-1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1510824/+subscriptions

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

[Touch-packages] [Bug 1506358] Re: libmirclient gives up and exits prematurely with "std::exception::what: disconnected: no new buffers" via ExchangeSemantics::submit()

[Daniel van Vugt]

** Changed in: xorg-server (Ubuntu)
   Importance: Undecided => High

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

Title:
  libmirclient gives up and exits prematurely with
  "std::exception::what: disconnected: no new buffers" via
  ExchangeSemantics::submit()

Status in Mir:
  New
Status in mir package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Under heavy resizing (stress testing under Valgrind), my Mir client
  (Xmir) crashed with:

  [1444895332.392862]  MirBufferStreamAPI: Caught exception at client 
library boundary (in mir_buffer_stream_swap_buffers): 
/build/mir-7io2Aj/mir-0.16.0+15.10.20150921.1/src/client/buffer_stream.cpp(169):
 Throw in function virtual MirWaitHandle* 
{anonymous}::ExchangeSemantics::submit(const std::function&, 
mir::geometry::Size, MirPixelFormat, int)
  Dynamic exception type: 
boost::exception_detail::clone_impl
 >
  std::exception::what: disconnected: no new buffers

  The strange thing is it's only the client that died. The server
  survived and I can connect new clients to it.

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

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

[Touch-packages] [Bug 1420573] Re: [enhancement] Missing client function for surface resizing

[Daniel van Vugt]

Note to self: I suspect this functionality isn't working properly. Need
to write a Mir demo client to take Xmir out of the equation.

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

Title:
  [enhancement] Missing client function for surface resizing

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Missing client API for client-initiated interactive resizing (eg: drag
  on the client-drawn resize handles)

  Actually there are two types of client initiated resizing we need to
  support:

  (a) Client specifies new width and height (e.g. video player loaded new file 
or System Settings switched panel).
  (b) Edge resizing for client-drawn decorations (which is closely related to 
bug 1420334).

  (a) Would be something like:
     mir_surface_resize(surface, width, height);

  (b) Could be something like:
     mir_surface_move_resize(surface, delta_top, delta_bottom, delta_left, 
delta_right);
  which would solve bug 1420334 also, as you can then say:

  void mir_surface_move_by(MirSurface *s, int dx, int dy)
  {
  mir_surface_move_resize(s, dy, dy, dx, dx);
  }

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

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

[Touch-packages] [Bug 1506713] Re: Xmir: Menus don't always close

[Daniel van Vugt]

** Changed in: xorg-server (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Xmir: Menus don't always close

Status in Mir:
  New
Status in mir package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Using Xmir, app menus don't always close when you click outside of
  them.

  They only close (in some cases) if you click on the app itself or are
  forced to select a menu item.

  This is an expected problem, as Mir does not yet implement pointer
  grabs, which is what toolkits use to auto-close menus when you click
  outside them.

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

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

[Touch-packages] [Bug 1510570] Re: BLE pairing fail

[Simon Fels]

@pitti: Yes, they implemented it to allow us to replace our hack udev
rule
(https://bazaar.launchpad.net/~bluetooth/bluez/ubuntu/view/head:/debian/50
-bluetooth-hci-auto-poweron.rules) with that. "that some distributions "
includes Ubuntu.

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

Title:
  BLE pairing fail

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  On 15.10 we now have bluez 5 so we can pair BLE devices like the
  Microsoft Arc Touch Bluetooth Mouse.

  But this pairing doesn't work very well. Mouse is seen but pairing fail.
  More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5

  This is due to udev rule that use "hcitool" to power on device.
  Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used 
instead of udev rules.

  here is a commit with this parameter: 
http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138
  And a ppa to test it: 
https://code.launchpad.net/~guilhem-fr/+archive/ubuntu/bluez-autoenable

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

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

[Touch-packages] [Bug 1507463] Re: OverlayFS: Wrong mnt_id and path reported in /proc in linux-3.13

[oleg]

Related bug #1347746 :  Overlayfs breaks /proc/self/exe link

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

Title:
  OverlayFS: Wrong mnt_id and path reported in /proc in linux-3.13

Status in linux package in Ubuntu:
  Confirmed
Status in lxc package in Ubuntu:
  Confirmed

Bug description:
  I am running Ubuntu Trusty (3.13.0-65-generic #106-Ubuntu SMP Fri Oct
  2 22:08:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux).

  There are two issues in OverlayFS as follows:

   1. /proc//fdinfo/ reports wrong mnt_id (non-existent in
  /proc//mountinfo)

   2. /proc//fd/ shows incorrect path for the symlink target

  These issues were previously reported and patched for the Ubuntu Vivid
  kernel (3.19) in bug #1479468, but the patch was not applied to the
  3.13 kernel, possibly because it contains an older version of
  overlayfs.

  These issues are now adversely affecting some versions of lxc when
  used in conjunction with the 3.13 kernel, because lxc has recently
  been patched to pass /proc//fd/ to the mount syscall.  This
  change to lxc was made in response to cve-2015-1335; see bug #1476662.

  The kernel issues cause some overlayfs-backed containers to fail to
  start, with error message,

  strace: mount("/home/ubuntu/test.txt", "/proc/self/fd/16",
  0x7ffd4c3f7fdb, MS_BIND, NULL) = -1 EACCES (Permission denied)

  The mount fails because /proc/self/fd/16, which should point to a file
  in overlayfs, has an invalid value.

  The version of lxc in the trusty-updates repository, lxc-1.0.7-0ubuntu0.7,
  is not affected.  The following versions of lxc are affected:

  repository lxc version
  
  ppa:ubuntu-lxc/lxc-git-stable-1.0  1.0.7+stable~20151014-2143-0ubuntu1~trusty
  ppa:ubuntu-lxc/lxc-git-stable-1.1  1.1.3+stable~20151007-2301-0ubuntu1~trusty
  ppa:ubuntu-lxc/lxc-git-master  1.1.3+master~20151012-0541-0ubuntu1~trusty

  To reproduce the lxc failure-to-start issue:

  # Install the 3.13 kernel and also an affected version of lxc.
  lxc-create -t download -n trusty -- -d ubuntu -r trusty -a amd64;
  touch $HOME/test.txt;
  echo "lxc.mount.entry = $HOME/test.txt home/ubuntu/test.txt none 
bind,create=file 0 0" >> $HOME/.local/share/lxc/trusty/config;
  lxc-clone -s -B overlayfs trusty trusty_overlay;
  lxc-start -n trusty_overlay; # fails to start

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

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

[Touch-packages] [Bug 1509118] Re: U1 account stops working and prevents using the store

[Julia Palandri]

Confirmed that setting the time to automatic fixed the issue for others
users too - the question of if we still want to allow users to set the
time to manual (instead of letting them just choose the timezone)
remains. Any ideas?

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

Title:
  U1 account stops working and prevents using the store

Status in Canonical System Image:
  Confirmed
Status in pay-service package in Ubuntu:
  New
Status in pay-ui package in Ubuntu:
  New
Status in ubuntu-push package in Ubuntu:
  New
Status in ubuntuone-credentials package in Ubuntu:
  New
Status in unity-scope-click package in Ubuntu:
  New

Bug description:
  In a phone with a U1 account configured and working, some users
  reported that about a week ago (i.e. before OTA-7) they started having
  problems to upgrade software or install new apps.

  When they want to upgrade/install, they are asked for their U1
  information as in no account was set up in the phone. If they add the
  account through Accounts in Settings, the phone apparently stores the
  information but when the user wants to use the store it disappears
  again.

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

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

[Touch-packages] [Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices

[Andrea Bernabei]

krillin, rc-proposed, r157

network-manager 0.9.10.0-4ubuntu15.1.8

No improvements so far, the phone still locks consistently when WiFi is
enabled.

While using software that force a new wifi scan, such as the location
service, the phone is completely unusable.

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

Title:
  Access points' "PropertiesChanged" dbus signals freeze UI on mobile
  devices

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu RTM:
  Fix Released

Bug description:
  Krillin, rc-proposed, r83

  
  DESCRIPTION:
  I've been trying to track down the cause of the occasional UI freezes on my 
Krillin device, and I noticed that whenever the UI freezes for 2-4 seconds, I 
get a burst of "PropertiesChanged" signals in dbus-monitor

  Here's a log of what's shown in dbus-monitor:
  http://pastebin.ubuntu.com/11992322/

  I'd guess the problem is in the code that actually catches the signals
  and acts accordingly.

  HOW TO REPRODUCE: 
  1) Move to a place where many wifi hotspots are available
  2) Connect the device via USB and run "phablet-shell" and then "dbus-monitor"
  3) Use the device while keeping an eye on dbus-monitor output

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

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

[Touch-packages] [Bug 1478799] Re: bluetooth not working in 15.10

[Prahlad Yeri]

I have the same issue as BarryD9545. I can send files via bluetooth, but
cannot receive from the smart-phone.

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

Title:
  bluetooth not working in 15.10

Status in Linux:
  Unknown
Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 15.10 Wily

  No bluetooth indicator visible.

  I can't activate bluetooth in the bluetooth system-settings.

  Bluetooth mouse not working (I can't pair it).

  syslog:
  Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: Starting SDP server
  Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: DIS cannot start: GATT 
is disabled
  Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: Failed to init 
deviceinfo plugin
  Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: Failed to init 
proximity plugin
  Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: Failed to init time 
plugin
  Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: Failed to init alert 
plugin
  Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: Failed to init 
thermometer plugin
  Jul 28 10:44:51 norbert-Aspire-5737Z NetworkManager[647]:  VPN: loaded 
org.freedesktop.NetworkManager.pptp
  Jul 28 10:44:51 norbert-Aspire-5737Z NetworkManager[647]:  DNS: loaded 
plugin dnsmasq
  Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: bluetoothd[677]: 
Starting SDP server
  Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: bluetoothd[677]: DIS 
cannot start: GATT is disabled
  Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: bluetoothd[677]: Failed 
to init deviceinfo plugin
  Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: bluetoothd[677]: Failed 
to init proximity plugin
  Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: bluetoothd[677]: Failed 
to init time plugin
  Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: bluetoothd[677]: Failed 
to init alert plugin
  Jul 28 10:44:51 norbert-Aspire-5737Z bluetoothd[677]: bluetoothd[677]: Failed 
to init thermometer plugin
  Jul 28 10:44:51 norbert-Aspire-5737Z avahi-daemon[680]: Successfully called 
chroot().
  Jul 28 10:44:51 norbert-Aspire-5737Z avahi-daemon[680]: Successfully dropped 
remaining capabilities.
  Jul 28 10:44:51 norbert-Aspire-5737Z avahi-daemon[680]: No service file found 
in /etc/avahi/services.
  Jul 28 10:44:51 norbert-Aspire-5737Z avahi-daemon[680]: Network interface 
enumeration completed.
  Jul 28 10:44:51 norbert-Aspire-5737Z systemd[1]: Started Avahi mDNS/DNS-SD 
Stack.
  Jul 28 10:44:51 norbert-Aspire-5737Z avahi-daemon[680]: Registering HINFO 
record with values 'X86_64'/'LINUX'.
  Jul 28 10:44:51 norbert-Aspire-5737Z systemd[1]: Started Bluetooth service.

  hciconfig 
  hci0: Type: BR/EDR  Bus: USB
BD Address: 00:15:83:15:A3:0B  ACL MTU: 672:4  SCO MTU: 48:1
DOWN 
RX bytes:445 acl:0 sco:0 events:15 errors:0
TX bytes:63 acl:0 sco:0 commands:15 errors:0

  rfkill list 
  0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

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

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

[Touch-packages] [Bug 1510647] Re: Inconsistent use of haptic feedback across the UI

[James Mulholland]

** Changed in: ubuntu-ux
 Assignee: (unassigned) => James Mulholland (jamesjosephmulholland)

** Changed in: ubuntu-ux
   Importance: Undecided => Medium

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

Title:
  Inconsistent use of haptic feedback across the UI

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

Bug description:
  Filing this bug for webbrowser-app, but it’s likely that it’s
  affecting other applications.

  I’m not aware of design guidelines regarding the use of haptics
  feedback when pressing/tapping UI elements on a touch device. In the
  UITK, it seems that anything that is a button (including anything
  inheriting from AbstractButton) will by default trigger a haptic
  response. List items are not button, so tapping them doesn’t trigger
  haptic feedback. However it’s pretty easy to build custom list items
  that embed an AbstractButton, and thus introduce inconsistency.

  An example of this inconsistent behaviour is the Settings screen in
  the browser app: the first two items ("search engines" and "homepage")
  are custom, they are haptics-enabled. The remaining items are not.

  We need clear design guidelines. Once we have them, we need to go
  through every UI element of the apps and fix them if they don’t comply
  with the guidelines.

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

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

[Touch-packages] [Bug 1408347] Re: bump version to 1.11 in ubuntu 15.04?

[Sebastien Bacher]

The new version is still in Debian experimental, seems like a non
trivial one which probably needs testing and coordination

** Changed in: glew (Ubuntu)
   Importance: Undecided => Wishlist

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

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

Title:
  bump version to 1.11 in ubuntu 15.04?

Status in glew package in Ubuntu:
  Triaged

Bug description:
  Debian Experimental already has 1.11 which introduces support for
  OpenGL 4.5.

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

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

[Touch-packages] [Bug 1510876] [NEW] Update to 3.18.2

[Sebastien Bacher]

Public bug reported:

That's being worked on, a first version is available in the desktop team
ppa and in the packaging vcs, the Mir backend still needs updating

** Affects: gtk+3.0 (Ubuntu)
 Importance: High
 Status: In Progress


** Tags: upgrade-software-version

** Changed in: gtk+3.0 (Ubuntu)
   Importance: Undecided => High

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => In Progress

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

Title:
  Update to 3.18.2

Status in gtk+3.0 package in Ubuntu:
  In Progress

Bug description:
  That's being worked on, a first version is available in the desktop
  team ppa and in the packaging vcs, the Mir backend still needs
  updating

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1510876/+subscriptions

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

[Touch-packages] [Bug 1510824] Re: PolkitAgentSession ignores multiline output (with pam_vas)

[Dariusz Gadomski]

** Changed in: policykit-1 (Ubuntu)
 Assignee: (unassigned) => Dariusz Gadomski (dgadomski)

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

Title:
  PolkitAgentSession ignores multiline output (with pam_vas)

Status in policykit-1 package in Ubuntu:
  New
Status in policykit-1 source package in Trusty:
  New
Status in policykit-1 source package in Vivid:
  New
Status in policykit-1 source package in Wily:
  New

Bug description:
  There is an error observed when Ubuntu is configured to perform
  authentication via pam_vas (Vintela Authentication Services by Dell)
  in a disconnected mode (using cached authentication).

  Steps to reproduce:
  1. Configure pam_vas client authenticating to a remote server.
  2. Perform authentication to cache the credentials.
  3. Disconnect from the network where the server is reachable (to force using 
cached information).
  4. Perform an action requiring polkit authentication.

  Expected result:
  Authentication succeeds accompanied by the following message "You have logged 
in using cached account information.  Some network services will be 
unavailable".

  Actual result:
  Authentication fails accompanied by the following message "You have logged in 
using cached account information.  Some network services will be unavailable".

  Probable cause:
  The PolkitAgentSession part of polkit is designed to interpret only 1-line 
output, while interaction with pam_vas in the above scenario triggers helper to 
produce the following 2-line output:
  PAM_TEXT_INFO You have logged in using cached account information.  Some 
network services will be unavailable
  SUCCESS

  The 'SUCCESS' part is never read so the authentication never ends
  successfully.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: policykit-1 0.105-4ubuntu2.14.04.1
  ProcVersionSignature: Ubuntu 3.16.0-52.71~14.04.1-generic 3.16.7-ckt18
  Uname: Linux 3.16.0-52-generic x86_64
  NonfreeKernelModules: nvidia zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Oct 28 09:01:37 2015
  InstallationDate: Installed on 2015-04-13 (197 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: policykit-1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1510824/+subscriptions

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

[Touch-packages] [Bug 1474944] Re: Settings "Display results from SCOPE" is not translated

[Pawel Stolowski]

** Branch linked: lp:~stolowski/unity-scopes-shell/init-gettext

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

Title:
  Settings "Display results from SCOPE" is not translated

Status in Canonical System Image:
  Confirmed
Status in The Savilerow project:
  Triaged
Status in Ubuntu Translations:
  Fix Committed
Status in unity-scopes-api package in Ubuntu:
  Invalid
Status in unity-scopes-shell package in Ubuntu:
  Confirmed

Bug description:
  Since keyword support was added, agg scopes automatically get user
  settings to enable/disable child scopes.

  PROBLEM: Theses always display in English for me.

  I flashed with a --wipe:
  ubuntu-device-flash --wipe --channel=ubuntu-touch/rc-proposed/bq-aquaris.en

  On first boot welcome wizard I chose Spanish/Spain.

  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 67
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-07-15 16:17:29
  version version: 67
  version ubuntu: 20150715
  version device: 20150529-8e13c5f
  version custom: 20150709-814-29-21-vivid

  See screenshot of Video agg.

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

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

[Touch-packages] [Bug 1510647] Re: Inconsistent use of haptic feedback across the UI

[James Mulholland]

** Changed in: ubuntu-ux
   Status: New => Triaged

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

Title:
  Inconsistent use of haptic feedback across the UI

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

Bug description:
  Filing this bug for webbrowser-app, but it’s likely that it’s
  affecting other applications.

  I’m not aware of design guidelines regarding the use of haptics
  feedback when pressing/tapping UI elements on a touch device. In the
  UITK, it seems that anything that is a button (including anything
  inheriting from AbstractButton) will by default trigger a haptic
  response. List items are not button, so tapping them doesn’t trigger
  haptic feedback. However it’s pretty easy to build custom list items
  that embed an AbstractButton, and thus introduce inconsistency.

  An example of this inconsistent behaviour is the Settings screen in
  the browser app: the first two items ("search engines" and "homepage")
  are custom, they are haptics-enabled. The remaining items are not.

  We need clear design guidelines. Once we have them, we need to go
  through every UI element of the apps and fix them if they don’t comply
  with the guidelines.

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

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

[Touch-packages] [Bug 1506206] Re: systemd abort

[Launchpad Bug Tracker]

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

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

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

Title:
  systemd abort

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd package in Fedora:
  Unknown

Bug description:
  

  sudo systemctl stop mariadb

  # needs to be fast, do not sleep more than 1 sec

  sudo systemctl start mariadb

  # delay does not matter

  sudo systemctl disable mariadb

  # delay does not matter

  sudo systemctl enable mariadb

  # delay does not matter

  sudo systemctl status mariadb

  

  Here the service starts showing the infamous

  

  ● mariadb.service - MariaDB database server
  Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor 
  preset: enabled)
 Drop-In: /etc/systemd/system/mariadb.service.d
  └─migrated-from-my.cnf-settings.conf
  Active: inactive (dead) since Wed 2015-10-14 15:04:58 UTC; 58s ago
Main PID: 880 (mysqld)
  Status: "Taking your SQL requests now..."
  CGroup: /system.slice/mariadb.service
  └─880 /usr/sbin/mysqld

  

  If I then shut down the MariaDB server, e.g. via the shutdown command 
  (or just SIGTERM the process), I get

  

  Broadcast message from systemd-journald@ubuntu-vivid-amd64 (Wed 
  2015-10-14 15:14:18 UTC):

  systemd[1]: Caught , dumped core as pid 960.

  
  Broadcast message from systemd-journald@ubuntu-vivid-amd64 (Wed 
  2015-10-14 15:14:18 UTC):

  systemd[1]: Freezing execution.

  

  systemd:

  ii  libpam-systemd:amd64219-7ubuntu3 
  amd64system and service manager - PAM module
  ii  libsystemd0:amd64   219-7ubuntu3 
  amd64systemd utility library
  ii  systemd 219-7ubuntu3 
  amd64system and service manager
  ii  systemd-sysv219-7ubuntu3 
  amd64system and service manager - SysV links

  
  with also occurs on Redhat - backtrace: 
https://bugzilla.redhat.com/show_bug.cgi?id=1271832

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

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

[Touch-packages] [Bug 1305699] Re: upowerd crashed with SIGSEGV in service_client_free()

[Andy_D]

Related: now getting
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1005418

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

Title:
  upowerd crashed with SIGSEGV in service_client_free()

Status in upower package in Ubuntu:
  Fix Released

Bug description:
  it looks like nothing happend. When I switch on the PC and after loging in 
this window with 'report an error/bug' appeard. so I guess it is minor.
  thanks for doing :)

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: upower 0.9.23-2ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic i686
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: i386
  Date: Wed Apr  9 15:37:43 2014
  ExecutablePath: /usr/lib/upower/upowerd
  InstallationDate: Installed on 2014-04-04 (5 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Beta i386 
(20140326)
  ProcCmdline: /usr/lib/upower/upowerd
  ProcEnviron:
   
  SegvAnalysis:
   Segfault happened at: 0xb74e9919 :   mov
(%esi),%eax
   PC (0xb74e9919) ok
   source "(%esi)" (0x302e) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: upower
  StacktraceTop:
   service_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4
   property_list_service_client_free () from 
/usr/lib/i386-linux-gnu/libimobiledevice.so.4
   lockdownd_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4
   ?? ()
   g_object_unref () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: upowerd crashed with SIGSEGV in service_client_free()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1408347] Re: bump version to 1.11 in ubuntu 15.04?

[Nigel Stewart]

I'm the upstream maintainer of GLEW, my comment is that although a lot
of packages depend on GLEW, the vast majority of changes are fully
backwards compatible.  1.11.0 is itself nearly one year old and is two
versions behind.  Fortunately for me I'm not having too much traffic
about obsolete bugs, but it's fairly discouraging to see such a delay
between fresh new OpenGL functionality and widespread availability to
GLEW-based apps.  I do think it would be good to see something newer
than 1.10.0 show up in Ubuntu 16.04

- Nigel

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

Title:
  bump version to 1.11 in ubuntu 15.04?

Status in glew package in Ubuntu:
  Triaged

Bug description:
  Debian Experimental already has 1.11 which introduces support for
  OpenGL 4.5.

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

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

[Touch-packages] [Bug 1509135] Re: Discrete Radeon graphics unit won't stay *off*

[Christopher M. Penalver]

foobar, could you please test the latest upstream kernel available from
the very top line at the top of the page from http://kernel.ubuntu.com
/~kernel-ppa/mainline/?C=N;O=D (the release names are irrelevant for
testing, and please do not test the daily folder)? Install instructions
are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds . This
will allow additional upstream developers to examine the issue.

If the latest kernel did not allow you to test to the issue (ex. you couldn't 
boot into the OS) please make a comment in your report about this, and continue 
to test the next most recent kernel version until you can test to the issue. 
Once you've tested the upstream kernel, please comment on which kernel version 
specifically you tested. If this issue is fixed in the mainline kernel, please 
add the following tags by clicking on the yellow circle with a black pencil 
icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, Y, and Z are numbers corresponding to the kernel version.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of
kernel-bug-exists-upstream.

Once testing of the latest upstream kernel is complete, please mark this
report's Status as Confirmed. Please let us know your results.

Thank you for your understanding.

** Tags added: latest-bios-f.29

** Tags added: regression-release

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

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

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

Title:
  Discrete Radeon graphics unit won't stay *off*

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from Ubuntu 15.04 to 15.10, the AMD discrete card
  keeps coming on.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: ubuntu-release-upgrader-core 1:15.10.14
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Thu Oct 22 16:30:42 2015
  InstallationDate: Installed on 2015-07-25 (89 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to wily on 2015-10-22 (0 days ago)
  VarLogDistupgradeTermlog:
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DistUpgraded: 2015-10-22 15:54:58,273 DEBUG enabling apt cron job
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250] 
[1002:9712] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:1641]
   Advanced Micro Devices, Inc. [AMD/ATI] Robson CE [Radeon HD 6370M/7370M] 
[1002:68e4] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2015-07-25 (94 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=08f5c22a-157d-4ff4-886f-b5e3e42acd66 ro quiet splash radeon.dpm=0 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Tags:  wily ubuntu compiz-0.9
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-16-generic x86_64
  UpgradeStatus: Upgraded to wily on 2015-10-22 (4 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 02/25/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.29
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1641
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 67.33
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.29:bd02/25/2013:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr058312242B2620100:rvnHewlett-Packard:rn1641:rvr67.33:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.version: 058312242B2620100
  dmi.sys.vendor: Hewlett-Packar

[Touch-packages] [Bug 1497170] Re: New file creation - not opening with file editor

[Bug Watch Updater]

** Changed in: glib
   Status: Confirmed => Fix Released

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

Title:
  New file creation - not opening with file editor

Status in GLib:
  Fix Released
Status in One Hundred Papercuts:
  Confirmed
Status in glib2.0 package in Ubuntu:
  Fix Released
Status in xdg-utils package in Ubuntu:
  Invalid

Bug description:
  Create a new file from File - Create Empty File.

  Open new document:

  expected behaviour - document opens in text editor

  actual behaviour - Open With dialogue opens requiring an application
  to open file.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: thunar 1.6.10-1
  ProcVersionSignature: Ubuntu 4.2.0-10.11-generic 4.2.0
  Uname: Linux 4.2.0-10-generic x86_64
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Sep 18 09:05:54 2015
  InstallationDate: Installed on 2015-09-17 (0 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150917)
  SourcePackage: thunar
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 15.10
  InstallationDate: Installed on 2015-09-17 (1 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150917)
  Package: xdg-utils 1.1.0~rc3+git20150907-1ubuntu2
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 4.2.0-10.11-generic 4.2.0
  Tags:  wily
  Uname: Linux 4.2.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1301033] Re: glew fails to build from source on armhf

[Nigel Stewart]

GLEW does not support OpenGLES.  Therefore it seems doubtful that
openimageio-1.3.12 supports OpenGLES unless there is some kind of build
option for that.

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

Title:
  glew fails to build from source on armhf

Status in glew package in Ubuntu:
  Confirmed
Status in glew source package in Trusty:
  Confirmed

Bug description:
  trying to build openimageio on armhf, ignoring the b-d on opencolorio,
  you get a build failure:

  In file included from /usr/include/qt4/QtOpenGL/QGLWidget:1:0,
   from 
/home/doko/tmp/openimageio-1.3.12~dfsg0/src/iv/ivgl.h:52,
   from 
/home/doko/tmp/openimageio-1.3.12~dfsg0/src/iv/imageviewer.cpp:32:
  /usr/include/qt4/QtOpenGL/qgl.h:85:17: error: conflicting declaration 
'typedef GLfloat GLdouble'
   typedef GLfloat GLdouble;
   ^
  In file included from 
/home/doko/tmp/openimageio-1.3.12~dfsg0/src/iv/imageviewer.h:50:0,
   from 
/home/doko/tmp/openimageio-1.3.12~dfsg0/src/iv/imageviewer.cpp:31:
  /usr/include/GL/glew.h:283:16: error: 'GLdouble' has a previous declaration 
as 'typedef double GLdouble'
   typedef double GLdouble;
  ^
  make[4]: *** [src/iv/CMakeFiles/iv.dir/imageviewer.cpp.o] Error 1
  make[4]: Leaving directory `/home/doko/tmp/openimageio-1.3.12~dfsg0/build'

  how ready is openimageio for OpenGLES?

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

-- 
Mailing list: https://launchpad.net/~touch-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

[tiredpixel]

I confirm that this issue has been experienced on Dell XPS 13 (9343),
Ubuntu 15.04, not working with kernels `3.19.0-30-generic` and
`3.19.0-31-generic`, but working with kernel `3.19.0-28-generic`, and
that the `copy_modules_dir kernel/ubuntu/i915` described in #54 sorts
the issue for kernel `3.19.0-31-generic`. Thank you, all! :) Peace,
tiredpixel

-- 
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:
  In Progress
Status in cryptsetup source package in Vivid:
  Invalid
Status in initramfs-tools source package in Vivid:
  New

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 1507484] Re: Window Graphics Corrupted for Skype

[vilbara]

Update to A15 BIOS on the Dell Latitude E7240 has solved Skype (and also
Spotify) window graphics corruptions.

Thanks!

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

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

Title:
  Window Graphics Corrupted for Skype

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  After update to pre-release ubuntu 15.10, skype window graphics is
  corrupted. Resizing and moving the window do not help. Till now, skype
  is the only application having this.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  BootLog:
   fsck from util-linux 2.26.2
   /dev/sda5: clean, 654139/11739136 files, 12149761/46937856 blocks
  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: Mon Oct 19 09:52:18 2015
  DistUpgraded: 2015-10-18 22:05:24,442 DEBUG enabling apt cron job
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.4, 3.19.0-30-generic, x86_64: installed
   virtualbox, 5.0.4, 4.2.0-16-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:05ca]
  InstallationDate: Installed on 2014-11-03 (349 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Latitude E7240
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=4b8a3a17-f006-45f8-b65f-397b75c1d209 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to wily on 2015-10-18 (0 days ago)
  dmi.bios.date: 05/01/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 05PTPV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd05/01/2014:svnDellInc.:pnLatitudeE7240:pvr01:rvnDellInc.:rn05PTPV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7240
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Sun Oct 18 22:05:47 2015
  xserver.configfile: default
  xserver.errors: intel(0): sna_mode_check: invalid state found on pipe 1, 
disabling CRTC:25
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id8300 
   vendor AUO
  xserver.version: 2:1.17.2-1ubuntu9

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

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

[Touch-packages] [Bug 1325142] Re: failure to update libpam-systemd in 14.04 due to missing logind init script

[Rob Brew]

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

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

Title:
  failure to update libpam-systemd in 14.04 due to missing logind init
  script

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Trusty:
  Fix Released
Status in systemd source package in Utopic:
  Fix Released

Bug description:
  Hi,

  while running inside an i386 lubuntu 14.04 chroot, upgrading libpam-
  systemd to version 204-5ubuntu20.2 fails leaving dpkg in a broken
  state. 'apt-get -f install' from within the chroot will not fix it,
  but if the build is made bootable and put into a iso/VM you can
  recover that way in a live session.

  the problem seems to be the /var/lib/dpkg/info/libpam-systemd:i386.prerm 
script failing to bring down the logind daemon with 'invoke-rc.d systemd-logind 
stop', because invoke-rd.d is only looking for the /etc/init.d/ script (doesn't 
exist) and not /etc/init/systemd-logind.conf (does exist).
  ?

  
  Reading package lists...
  Building dependency tree...
  Reading state information...
  The following packages will be upgraded:
libpam-systemd
  1 upgraded, 0 newly installed, 0 to remove and 113 not upgraded.
  3 not fully installed or removed.
  Need to get 0 B/25.2 kB of archives.
  After this operation, 1024 B of additional disk space will be used.
  (Reading database ... 113986 files and directories currently installed.)
  Preparing to unpack .../libpam-systemd_204-5ubuntu20.2_i386.deb ...
  invoke-rc.d: unknown initscript, /etc/init.d/systemd-logind not found.
  dpkg: warning: subprocess old pre-removal script returned error exit status 
100
  dpkg: trying script from the new package instead ...
  invoke-rc.d: unknown initscript, /etc/init.d/systemd-logind not found.
  dpkg: error processing archive 
/var/cache/apt/archives/libpam-systemd_204-5ubuntu20.2_i386.deb (--unpack):
   subprocess new pre-removal script returned error exit status 100
  invoke-rc.d: unknown initscript, /etc/init.d/systemd-logind not found.
  dpkg: error while cleaning up:
   subprocess installed post-installation script returned error exit status 100
  Errors were encountered while processing:
   /var/cache/apt/archives/libpam-systemd_204-5ubuntu20.2_i386.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  
  Our build logs available upon request, but the scripts to setup the chroot to 
recreate it are here:

https://trac.osgeo.org/osgeo/browser/livedvd/gisvm/trunk/bin/build_chroot_nightly.sh

https://trac.osgeo.org/osgeo/browser/livedvd/gisvm/trunk/bin/inchroot_nightly.sh

  
  In a web-search I notice a few others running into the same bug,

  chatter on irc at [18:10], http://irclogs.ubuntu.com/2013/05/28
  /%23ubuntu-devel.txt

  someone else's build log:
  https://launchpad.net/~qutim/+archive/qutim/+build/6039800

  launchpad bug #1323575 seems to be a duplicate of this one.

  
  perhaps related to older launchpad bug #1305395 ?

  note we are also suffering from a failure with update-initramfs, not sure of 
the root cause of that one but I thought I'd mention it in case they were 
related, since they both started happening about the same time, a couple weeks 
ago. (launchpad bug #1317602)
  It all worked ok after the inital releases of 14.04, so something to do with 
a package update since then.

  
  thanks,
  Hamish

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

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

[Touch-packages] [Bug 1064497] Re: [HDA-Intel - HDA Intel PCH, playback] ThinkPad Mini Dock Series 3 no sound on 3.5 mm TRS socket

[uo]

Problem is gone, even back in 12.04, probably with the HWE-Stack update.
I think this can be closed.

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

Title:
  [HDA-Intel - HDA Intel PCH, playback] ThinkPad Mini Dock Series 3 no
  sound on 3.5 mm TRS socket

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Same Problem as:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/893611
  or
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1026953

  Seems my Model needs to be added to the table:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/893611/comments/12

  Workaround via  /etc/modprobe.d/alsa-base.conf brings no change,
  neither  does kernel update to 3.2.0-30.48.

  Keep up the good work!

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-31.50-generic-pae 3.2.28
  Uname: Linux 3.2.0-31-generic-pae i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu13
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: ALC3202 Analog [ALC3202 Analog]
 Subdevices: 0/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  claudia1694 F pulseaudio
   /dev/snd/pcmC0D0c:   claudia1694 F...m pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xf253 irq 45'
 Mixer name : 'Intel PantherPoint HDMI'
 Components : 'HDA:10ec0269,17aa21f3,00100203 
HDA:80862806,80860101,0010'
 Controls  : 36
 Simple ctrls  : 13
  Card29.Amixer.info:
   Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 
unknown'
 Mixer name : 'ThinkPad EC (unknown)'
 Components : ''
 Controls  : 1
 Simple ctrls  : 1
  Card29.Amixer.values:
   Simple mixer control 'Console',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Date: Tue Oct  9 17:53:36 2012
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Eingebautes Audio - HDA Intel PCH
  Symptom_Type: Only some of outputs are working
  Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/25/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ET41WW (1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2344CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ET41WW(1.16):bd05/25/2012:svnLENOVO:pn2344CTO:pvrThinkPadT430:rvnLENOVO:rn2344CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2344CTO
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2012-10-09T15:38:41.282970

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

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

[Touch-packages] [Bug 1082031] Re: Package mpg123 for arm with option "--with-cpu=generic_fpu"

[James Cowgill]

Was fixed in 1.18.0-1ubuntu1 (utopic).

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

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

Title:
  Package mpg123 for arm with option "--with-cpu=generic_fpu"

Status in AC100_enablement:
  New
Status in audacious package in Ubuntu:
  Confirmed
Status in mpg123 package in Ubuntu:
  Fix Released

Bug description:
  Listening music with audacious on Lubuntu 12.10 (installed according to [1]) 
fails with the message:
  „mpg123: Error opening file a.mp3: Unable to set up output format! (code 1).“

  According to the Audacious-Board [2] this happens because has no ARM-
  assembly code for playing anything else than 16bit. It can be resolved
  by recompiling mpg123 with option "--with-cpu=generic_fpu"

  [1] https://wiki.ubuntu.com/ARM/TEGRA/AC100
  [2] http://redmine.audacious-media-player.org/boards/2/topics/315

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

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

[Touch-packages] [Bug 1510926] [NEW] problem driver intel 4 seriesa chipset integrated graphics controller

[espantaperros]

Public bug reported:

hi

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.19.1-0ubuntu4
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 28 13:38:24 2015
DistUpgraded: 2015-10-27 09:32:49,838 DEBUG enabling apt cron job
DistroCodename: wily
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.0.4, 3.19.0-31-generic, x86_64: installed
 virtualbox, 5.0.4, 4.2.0-16-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e12] 
(rev 03) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Device [1025:0151]
   Subsystem: Acer Incorporated [ALI] Device [1025:0151]
InstallationDate: Installed on 2015-05-07 (174 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
MachineType: Acer Veriton S670G
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=b0cd3f1a-045d-4b5e-87f4-bf104916c033 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to wily on 2015-10-27 (1 days ago)
dmi.bios.date: 11/20/2008
dmi.bios.vendor: Acer
dmi.bios.version: R01-A2L
dmi.board.name: EQ45M
dmi.board.vendor: Acer
dmi.chassis.type: 3
dmi.chassis.vendor: Acer
dmi.modalias: 
dmi:bvnAcer:bvrR01-A2L:bd11/20/2008:svnAcer:pnVeritonS670G:pvr:rvnAcer:rnEQ45M:rvr:cvnAcer:ct3:cvr:
dmi.product.name: Veriton S670G
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.64-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
xserver.bootTime: Wed Oct 28 09:47:04 2015
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputCherry GmbH SmartBoard XX44 KEYBOARD, id 8
 inputLogitech USB Optical Mouse MOUSE, id 9
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id1935 
 vendor MAX
xserver.version: 2:1.17.2-1ubuntu9

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


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

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

Title:
  problem driver intel 4 seriesa chipset integrated graphics controller

Status in xorg package in Ubuntu:
  New

Bug description:
  hi

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu4
  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 28 13:38:24 2015
  DistUpgraded: 2015-10-27 09:32:49,838 DEBUG enabling apt cron job
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.4, 3.19.0-31-generic, x86_64: installed
   virtualbox, 5.0.4, 4.2.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e12] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:0151]
 Subsystem: Acer Incorporated [ALI] Device [1025:0151]
  InstallationDate: Installed on 2015-05-07 (174 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: Acer Veriton S670G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=b0cd3f1a-045d-4b5e-87f4-bf104916c033 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to wily on 2015-10-27 (1 days ago)
  dmi.bios.date: 11/20/20

[Touch-packages] [Bug 1509769] Re: package initramfs-tools 0.120ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[david cawsey]

In case it's relevant, my installation is on a usb stick, not on sd card
(ecept for the boot)

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

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

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Error occured during UBUNTU Mate upgrade to 15.10 on Raspberry PI2 and
  once trying perform manual update getting:

  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Setting up initramfs-tools (0.120ubuntu6) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools (0.120ubuntu6) ...
  update-initramfs: Generating /boot/initrd.img-3.18.0-25-rpi2
  Unsupported platform.
  run-parts: /etc/initramfs/post-update.d//flash-kernel exited with return code 
1
  dpkg: error processing package initramfs-tools (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   initramfs-tools
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: initramfs-tools 0.120ubuntu6
  ProcVersionSignature: Ubuntu 3.18.0-25.26-rpi2 3.18.17
  Uname: Linux 3.18.0-25-rpi2 armv7l
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: armhf
  Date: Sun Oct 25 08:19:08 2015
  DuplicateSignature: package:initramfs-tools:0.120ubuntu6:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5
   apt  1.0.10.2ubuntu1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.120ubuntu6 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to wily on 2015-10-25 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1509769/+subscriptions

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

[Touch-packages] [Bug 1510824] Re: PolkitAgentSession ignores multiline output (with pam_vas)

[Dariusz Gadomski]

** Description changed:

  There is an error observed when Ubuntu is configured to perform
  authentication via pam_vas (Vintela Authentication Services by Dell) in
  a disconnected mode (using cached authentication).
  
  Steps to reproduce:
  1. Configure pam_vas client authenticating to a remote server.
  2. Perform authentication to cache the credentials.
  3. Disconnect from the network where the server is reachable (to force using 
cached information).
  4. Perform an action requiring polkit authentication.
  
  Expected result:
  Authentication succeeds accompanied by the following message "You have logged 
in using cached account information.  Some network services will be 
unavailable".
  
  Actual result:
  Authentication fails accompanied by the following message "You have logged in 
using cached account information.  Some network services will be unavailable".
  
  Probable cause:
  The PolkitAgentSession part of polkit is designed to interpret only 1-line 
output, while interaction with pam_vas in the above scenario triggers helper to 
produce the following 2-line output:
  PAM_TEXT_INFO You have logged in using cached account information.  Some 
network services will be unavailable
  SUCCESS
  
- The 'SUCCESS' part is never read so the authentication never ends
+ The 'SUCCESS' part is never read so the authentication never finishes
  successfully.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: policykit-1 0.105-4ubuntu2.14.04.1
  ProcVersionSignature: Ubuntu 3.16.0-52.71~14.04.1-generic 3.16.7-ckt18
  Uname: Linux 3.16.0-52-generic x86_64
  NonfreeKernelModules: nvidia zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Oct 28 09:01:37 2015
  InstallationDate: Installed on 2015-04-13 (197 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: policykit-1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  PolkitAgentSession ignores multiline output (with pam_vas)

Status in policykit-1 package in Ubuntu:
  New
Status in policykit-1 source package in Trusty:
  New
Status in policykit-1 source package in Vivid:
  New
Status in policykit-1 source package in Wily:
  New

Bug description:
  There is an error observed when Ubuntu is configured to perform
  authentication via pam_vas (Vintela Authentication Services by Dell)
  in a disconnected mode (using cached authentication).

  Steps to reproduce:
  1. Configure pam_vas client authenticating to a remote server.
  2. Perform authentication to cache the credentials.
  3. Disconnect from the network where the server is reachable (to force using 
cached information).
  4. Perform an action requiring polkit authentication.

  Expected result:
  Authentication succeeds accompanied by the following message "You have logged 
in using cached account information.  Some network services will be 
unavailable".

  Actual result:
  Authentication fails accompanied by the following message "You have logged in 
using cached account information.  Some network services will be unavailable".

  Probable cause:
  The PolkitAgentSession part of polkit is designed to interpret only 1-line 
output, while interaction with pam_vas in the above scenario triggers helper to 
produce the following 2-line output:
  PAM_TEXT_INFO You have logged in using cached account information.  Some 
network services will be unavailable
  SUCCESS

  The 'SUCCESS' part is never read so the authentication never finishes
  successfully.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: policykit-1 0.105-4ubuntu2.14.04.1
  ProcVersionSignature: Ubuntu 3.16.0-52.71~14.04.1-generic 3.16.7-ckt18
  Uname: Linux 3.16.0-52-generic x86_64
  NonfreeKernelModules: nvidia zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Oct 28 09:01:37 2015
  InstallationDate: Installed on 2015-04-13 (197 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: policykit-1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1510824/+subscriptions

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

[Touch-packages] [Bug 1510938] [NEW] package dictionaries-common 1.26.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[martin suc]

Public bug reported:

apt-cache policy dictionaries-common
dictionaries-common:
  Installed: 1.26.2
  Candidate: 1.26.2
  Version table:
 *** 1.26.2 0
500 http://archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
100 /var/lib/dpkg/status

lsb_release -rd
Description:Ubuntu 15.10
Release:15.10

ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: dictionaries-common 1.26.2
ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
Uname: Linux 4.2.0-17-generic x86_64
ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
Date: Wed Oct 28 12:11:03 2015
DuplicateSignature: package:dictionaries-common:1.26.2:subprocess installed 
post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2015-04-02 (209 days ago)
InstallationMedia:
 
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.2ubuntu5
 apt  1.0.10.2ubuntu1
SourcePackage: dictionaries-common
Title: package dictionaries-common 1.26.2 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to wily on 2015-04-02 (209 days ago)

** Affects: dictionaries-common (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package need-duplicate-check wily

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

Title:
  package dictionaries-common 1.26.2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in dictionaries-common package in Ubuntu:
  New

Bug description:
  apt-cache policy dictionaries-common
  dictionaries-common:
Installed: 1.26.2
Candidate: 1.26.2
Version table:
   *** 1.26.2 0
  500 http://archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
  100 /var/lib/dpkg/status

  lsb_release -rd
  Description:  Ubuntu 15.10
  Release:  15.10

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: dictionaries-common 1.26.2
  ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
  Uname: Linux 4.2.0-17-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  Date: Wed Oct 28 12:11:03 2015
  DuplicateSignature: package:dictionaries-common:1.26.2:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-04-02 (209 days ago)
  InstallationMedia:
   
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5
   apt  1.0.10.2ubuntu1
  SourcePackage: dictionaries-common
  Title: package dictionaries-common 1.26.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to wily on 2015-04-02 (209 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dictionaries-common/+bug/1510938/+subscriptions

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

[Touch-packages] [Bug 1507484] Re: Window Graphics Corrupted for Skype

[vilbara]

** Attachment added: "skype-still-corrupt.png"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1507484/+attachment/4507531/+files/skype-still-corrupt.png

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

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

Title:
  Window Graphics Corrupted for Skype

Status in xorg package in Ubuntu:
  New

Bug description:
  After update to pre-release ubuntu 15.10, skype window graphics is
  corrupted. Resizing and moving the window do not help. Till now, skype
  is the only application having this.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  BootLog:
   fsck from util-linux 2.26.2
   /dev/sda5: clean, 654139/11739136 files, 12149761/46937856 blocks
  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: Mon Oct 19 09:52:18 2015
  DistUpgraded: 2015-10-18 22:05:24,442 DEBUG enabling apt cron job
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.4, 3.19.0-30-generic, x86_64: installed
   virtualbox, 5.0.4, 4.2.0-16-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:05ca]
  InstallationDate: Installed on 2014-11-03 (349 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Latitude E7240
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=4b8a3a17-f006-45f8-b65f-397b75c1d209 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to wily on 2015-10-18 (0 days ago)
  dmi.bios.date: 05/01/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 05PTPV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd05/01/2014:svnDellInc.:pnLatitudeE7240:pvr01:rvnDellInc.:rn05PTPV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7240
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Sun Oct 18 22:05:47 2015
  xserver.configfile: default
  xserver.errors: intel(0): sna_mode_check: invalid state found on pipe 1, 
disabling CRTC:25
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id8300 
   vendor AUO
  xserver.version: 2:1.17.2-1ubuntu9

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

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

[Touch-packages] [Bug 1507484] Re: Window Graphics Corrupted for Skype

[vilbara]

Unfortunately, I was too fast to report success - corruption still
occurs:

sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

A15
05/19/2015


Corruption looks like parts of skype window are not redrawn properly. I've 
attached another example screen-shot.

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

Title:
  Window Graphics Corrupted for Skype

Status in xorg package in Ubuntu:
  New

Bug description:
  After update to pre-release ubuntu 15.10, skype window graphics is
  corrupted. Resizing and moving the window do not help. Till now, skype
  is the only application having this.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  BootLog:
   fsck from util-linux 2.26.2
   /dev/sda5: clean, 654139/11739136 files, 12149761/46937856 blocks
  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: Mon Oct 19 09:52:18 2015
  DistUpgraded: 2015-10-18 22:05:24,442 DEBUG enabling apt cron job
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.4, 3.19.0-30-generic, x86_64: installed
   virtualbox, 5.0.4, 4.2.0-16-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:05ca]
  InstallationDate: Installed on 2014-11-03 (349 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Latitude E7240
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=4b8a3a17-f006-45f8-b65f-397b75c1d209 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to wily on 2015-10-18 (0 days ago)
  dmi.bios.date: 05/01/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 05PTPV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd05/01/2014:svnDellInc.:pnLatitudeE7240:pvr01:rvnDellInc.:rn05PTPV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7240
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Sun Oct 18 22:05:47 2015
  xserver.configfile: default
  xserver.errors: intel(0): sna_mode_check: invalid state found on pipe 1, 
disabling CRTC:25
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id8300 
   vendor AUO
  xserver.version: 2:1.17.2-1ubuntu9

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

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

[Touch-packages] [Bug 1510942] [NEW] package apport 2.19.1-0ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[John Bales]

Public bug reported:

This was a scheduled software-updater update
Description:Ubuntu 15.10
Release:15.10
apport:
  Installed: 2.19.1-0ubuntu4
  Candidate: 2.19.1-0ubuntu4
  Version table:
 *** 2.19.1-0ubuntu4 0
500 http://us.archive.ubuntu.com/ubuntu/ wily-updates/main i386 Packages
500 http://security.ubuntu.com/ubuntu/ wily-security/main i386 Packages
100 /var/lib/dpkg/status
 2.19.1-0ubuntu3 0
500 http://us.archive.ubuntu.com/ubuntu/ wily/main i386 Packages

ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: apport 2.19.1-0ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic i686
ApportLog:
 
ApportVersion: 2.19.1-0ubuntu4
Architecture: i386
Date: Wed Oct 28 08:22:12 2015
DuplicateSignature: package:apport:2.19.1-0ubuntu4:subprocess installed 
post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2015-10-25 (3 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.2ubuntu5
 apt  1.0.10.2ubuntu1
SourcePackage: apport
Title: package apport 2.19.1-0ubuntu4 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 need-duplicate-check wily

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

Title:
  package apport 2.19.1-0ubuntu4 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in apport package in Ubuntu:
  New

Bug description:
  This was a scheduled software-updater update
  Description:  Ubuntu 15.10
  Release:  15.10
  apport:
Installed: 2.19.1-0ubuntu4
Candidate: 2.19.1-0ubuntu4
Version table:
   *** 2.19.1-0ubuntu4 0
  500 http://us.archive.ubuntu.com/ubuntu/ wily-updates/main i386 
Packages
  500 http://security.ubuntu.com/ubuntu/ wily-security/main i386 
Packages
  100 /var/lib/dpkg/status
   2.19.1-0ubuntu3 0
  500 http://us.archive.ubuntu.com/ubuntu/ wily/main i386 Packages

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: apport 2.19.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic i686
  ApportLog:
   
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: i386
  Date: Wed Oct 28 08:22:12 2015
  DuplicateSignature: package:apport:2.19.1-0ubuntu4:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-10-25 (3 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5
   apt  1.0.10.2ubuntu1
  SourcePackage: apport
  Title: package apport 2.19.1-0ubuntu4 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1510919] Re: developer mode toggle does nothing

[Jean-Baptiste Lallement]

Reverting these imports in /usr/share/ubuntu/settings/system/qml-
plugins/about/DevMode.qml to 0.1 fixes the problem:

import Ubuntu.Components 1.3
import Ubuntu.Components.ListItems 1.3 as ListItem


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

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

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

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

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Zoltan Balogh (bzoltan)

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

Title:
  developer mode toggle does nothing

Status in Canonical System Image:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  Last know good image: 157
  Commit log for 158: 
http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-proposed/158.commitlog

  TEST CASE:
  1. Flash a device with bootstrap or upgrade to latest image
  2. Go to system-settings / About / Developer mode
  3. Toggle developer mode

  ACTUAL RESULT
  On a freshly flashed device, toggling dev mode on does nothing
  On an upgraded device with dev mode enabled, toggling dev mode off does 
nothing

  WORKAROUND
  Flash with --developer-mode

  = original description =
  Using a krillin on rc-proposed, developer mode does not enable an adb shell:

  ubuntu-touch/rc-proposed/bq-aquaris.en #159

  $ ubuntu-device-flash touch --bootstrap --channel ubuntu-touch/rc-
  proposed/bq-aquaris.en --recovery-image recovery-krillin.img

  Then boot device to wizard, walk through (I configured wifi, 
  passcode and have 2 SIMs online in the device). Defaults for location.

  Open System settings | about this phone | developer mode

  Enable developer mode

  On your pc:

  $ adb shell
  error: device not found

  Expected: a phablet shell on the device.

  Additionally, if you now reboot, the setting for developer mode is
  forgotten.

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

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

[Touch-packages] [Bug 1352783] Re: Facebook app banner is back

[Olivier Tilloy]

** No longer affects: webbrowser-app (Ubuntu RTM)

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

Title:
  Facebook app banner is back

Status in webbrowser-app package in Ubuntu:
  Triaged

Bug description:
  The Ubuntu WebView component comes preloaded with a user script that
  removes the app banner that facebook displays on its login page to
  advertise its native android application (see
  http://bazaar.launchpad.net/~phablet-team/webbrowser-
  app/trunk/view/head:/src/Ubuntu/Web/fb-no-appbanner.js).

  Facebook changed recently their login page layout, and the script
  stopped working. The banner used to be enclosed in a div with class
  "appBanner", which made it easy to detect and suppress. It no longer
  has this class, here is what the code looks like now:


  https://m.facebook.com/click.php?redir_url=market%3A%2F%2Fdetails%3Fid%3Dcom.facebook.katana&app_id=350685531728&cref=mb&no_fw=1&refid=8";
 target="_top" data-sigil="touchable marea">

  
  
Get Facebook for Android and browse faster.
  

  


To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1352783/+subscriptions

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

[Touch-packages] [Bug 1476559] Re: Hard to tap links at the very bottom of webpage

[Olivier Tilloy]

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

** This bug has been marked a duplicate of bug 1474533
   Taps at the bottom of the screen trigger a bottom edge gesture

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

Title:
  Hard to tap links at the very bottom of webpage

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  When touching the very bottom of the window, the webbrowser-app brings
  up the new-tab bottom-of-screen panel.  This means that if a webpage
  has links on the very bottom of the page, it is impossible to click
  them.

  Prior to r24, it was possible to deal with this by rotating to
  horizontal view, and tapping the link, since "bottom of the screen"
  was defined on one screen edge only.  However, since r24 brings full
  shell rotation, this is no longer the case.

  Example webpage where this affects the ability to navigate:
  http://forum.dlang.org/thread/mnp350$7ql$2...@digitalmars.com (scroll
  down to the bottom for the « First   ‹ Prev | Next ›   Last » links,
  these are now impossible to use).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1476559/+subscriptions

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

[Touch-packages] [Bug 1458609] Re: Requested surface format is ignored

[Loïc Molinari]

** Branch linked: lp:~unity-team/qtubuntu/requested-surface-format-fix

** Branch unlinked: lp:~loic.molinari/qtubuntu/qtubuntu-requested-
surface-format-fix

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

Title:
  Requested surface format is ignored

Status in qtubuntu package in Ubuntu:
  In Progress

Bug description:
  QPlatformIntegration::createOpenGLContext() and
  QPlatformIntegration::createPlatformWindow()are given a QSurfaceFormat
  describing the format (and other options like the swap interval)
  requested by the user. This is currently ignored by QtUbuntu which
  always creates an ARGB context and an ARGB surface.

  Telling mir whether the requested surface is opaque or not allows
  compositing optimization by rendering opaque surfaces front-to-back
  with depth write/test on (early z-culling) and blending off.

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

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

[Touch-packages] [Bug 1509747] Re: Intermittent lxc failures on wily, juju-template-restart.service race condition

[Cheryl Jennings]

Thanks for digging into this so much, Martin!

1 - Yes, I will try the runcmd you mention and see if it works.

2 - However, I thought adding in After=cloud-config.target would ensure
that it wouldn't start until after cloud-init completes?

3 - The recreate steps for this are:
- Bootstrap local env on wily  (this won't create a container)
- Deploy using the command: `juju deploy wily/ubuntu`.  It may take some time 
before you see the container started as juju will download the image before 
starting the template container.

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

Title:
  Intermittent lxc failures on wily, juju-template-restart.service race
  condition

Status in juju-core:
  Confirmed
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Frequently, when creating an lxc container on wily (either through
  --to lxc:#, or using the local provider on wily), the template never
  stops and errors out here:

  [ 2300.885573] cloud-init[2758]: Cloud-init v. 0.7.7 running 'modules:final' 
at Sun, 25 Oct 2015 00:28:57 +. Up 182 seconds.
  [ 2300.886101] cloud-init[2758]: Cloud-init v. 0.7.7 finished at Sun, 25 Oct 
2015 00:29:03 +. Datasource DataSourceNoCloudNet 
[seed=/var/lib/cloud/seed/nocloud-net][dsmode=net].  Up 189 seconds
  [  OK  ] Started Execute cloud user/final scripts.
  [  OK  ] Reached target Multi-User System.
  [  OK  ] Reached target Graphical Interface.
   Starting Update UTMP about System Runlevel Changes...
  [  OK  ] Started /dev/initctl Compatibility Daemon.
  [FAILED] Failed to start Update UTMP about System Runlevel Changes.
  See 'systemctl status systemd-update-utmp-runlevel.service' for details.

  Attaching to the container and running the above command yields:

  ubuntu@cherylj-wily-local-lxc:~$ sudo lxc-attach --name juju-wily-lxc-template
  root@juju-wily-lxc-template:~# systemctl status 
systemd-update-utmp-runlevel.service
  ● systemd-update-utmp-runlevel.service - Update UTMP about System Runlevel 
Changes
 Loaded: loaded (/lib/systemd/system/systemd-update-utmp-runlevel.service; 
static; vendor preset: enabled)
 Active: failed (Result: exit-code) since Sun 2015-10-25 00:30:29 UTC; 2h 
23min ago
   Docs: man:systemd-update-utmp.service(8)
 man:utmp(5)
Process: 3963 ExecStart=/lib/systemd/systemd-update-utmp runlevel 
(code=exited, status=1/FAILURE)
   Main PID: 3963 (code=exited, status=1/FAILURE)

  Oct 25 00:29:46 juju-wily-lxc-template systemd[1]: Starting Update UTMP about 
System Runlevel Changes...
  Oct 25 00:30:29 juju-wily-lxc-template systemd[1]: 
systemd-update-utmp-runlevel.service: Main process exited, code=exited, 
status=1/FAILURE
  Oct 25 00:30:30 juju-wily-lxc-template systemd[1]: Failed to start Update 
UTMP about System Runlevel Changes.
  Oct 25 00:30:30 juju-wily-lxc-template systemd[1]: 
systemd-update-utmp-runlevel.service: Unit entered failed state.
  Oct 25 00:30:30 juju-wily-lxc-template systemd[1]: 
systemd-update-utmp-runlevel.service: Failed with result 'exit-code'.

  
  I have seen this on ec2 and in canonistack.  The canonistack machine is 
available for further debugging.  Ping me for access.

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1509747/+subscriptions

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

[Touch-packages] [Bug 1415854] Re: Tab captures are not deleted when starting a new session

[Olivier Tilloy]

This was fixed at revision 1228 of lp:webbrowser-app, released with
version 0.23+15.10.20151013.1-0ubuntu1 of webbrowser-app.

** Changed in: webbrowser-app (Ubuntu)
 Assignee: Olivier Tilloy (osomon) => Ugo Riboni (uriboni)

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

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

Title:
  Tab captures are not deleted when starting a new session

Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  Tab captures are stored on disk under ~/.cache/webbrowser-app/captures/. 
Captures are deleted when a tab is closed.
  However no cleanup is performed when the app is started with the 
--new-session parameter, which discards all saved tabs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1415854/+subscriptions

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

[Touch-packages] [Bug 1484589] Re: Spurious volume notification when changing output role with headphones

[Jean-Baptiste Lallement]

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

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

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Alejandro J. Cura (alecu)

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

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

Title:
  Spurious volume notification when changing output role with headphones

Status in Canonical System Image:
  Confirmed
Status in indicator-sound package in Ubuntu:
  Fix Committed
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Ubuntu 15.04 r90

  1. Install the "Maroon in Trouble" game.
  2. With headphones connected, start a new game.
  3. After a while, disconnect the headphones.

  What happens:
  2. There's a volume notification each time a sound plays.
  3. There are no more volume notifications.

  What should happen:
  2. There are no volume notifications, because neither the sound output nor 
the volume is changing.

  : "When the primary sound
  output changes for any reason except an app request, or when the sound
  volume changes for any reason, a confirmation bubble should appear ...
  There should be no special notification when the active output role
  changes."

  This could be a side-effect of bug 1418210, but probably not, since it
  is idempotent: the notifications keep happening even if you don't
  change the volume in the meantime.

  [Split off bug 1478506.]

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

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

[Touch-packages] [Bug 1419829] Re: [Scope] location settings are enabled by default

[Alejandro J. Cura]

** Changed in: canonical-devices-system-image
Milestone: ww46-2015 => ww02-2016

** Changed in: unity-scopes-shell (Ubuntu)
 Assignee: Pete Woods (pete-woods) => Pawel Stolowski (stolowski)

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

Title:
  [Scope] location settings are enabled by default

Status in Canonical System Image:
  In Progress
Status in Ubuntu UX:
  Opinion
Status in unity-scopes-shell package in Ubuntu:
  Confirmed

Bug description:
  This is in contrast to the rest of the system where user have to
  explicitly grant access right upfront.

  Possible solution would be to add a new page in phone setup wizard
  asking for whether scopes are allowed to use location or not and then
  applying this to individual scope location settings.

  UX comment-

  Potential new project: When scopes will be launched as apps, we'll
  probably need some coach marks // independent onboard experience to
  explain data consumption and location services usage.

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

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

[Touch-packages] [Bug 1402966] Re: libxcb new version 1.11

[Bug Watch Updater]

** Changed in: libxcb (Debian)
   Status: New => Fix Released

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

Title:
  libxcb new version 1.11

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

Bug description:
  There is a new version of the package

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

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

[Touch-packages] [Bug 1481388] Re: NTP : Use-after-free in routing socket code after dropping root

[Eric Desrochers]

Hi Mathew,

I have the knowledge of the code, I will rebase the debdiffs for V/T/P

Note: I checked and Xenial has the patch already.

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

Title:
  NTP : Use-after-free in routing socket code after dropping root

Status in NTP:
  Fix Released
Status in ntp package in Ubuntu:
  Fix Released
Status in ntp source package in Precise:
  In Progress
Status in ntp source package in Trusty:
  In Progress
Status in ntp source package in Vivid:
  In Progress
Status in ntp source package in Wily:
  Fix Released
Status in ntp package in Debian:
  Fix Released

Bug description:
  [Impact]

   * User experienced repeated segfaults at the same instruction pointer

  i/o error on routing socket No buffer space available - disabling
  segfault at 31 ip 0031 sp 79f11788 error 14 in 
libpthread-2.15.so[7f967a5d9000+18000] 

  The remove_ and delete_ functions remove the current element from the
  asyncio_reader_list, and free it, respectively.

  We then return back to the loop at the top, wherein the asyncio_reader 
variable still points at the now-freed element, whose contents are (in theory) 
now scrambled
  by having link pointers, etc, from internal malloc state overlaying the data.

  [Test Case]

  You can easily reproduce the bug by :

  - Lowering the sysctl value net.core.rmem_max

  $ sysctl -w net.core.wmem_max=
  This sets the max OS send buffer size for all types of connections.

  - Adding multiple network interfaces and static routes.

  [Regression Potential]

  None expected since the fix is already available upstream
  (https://github.com/ntp-project/ntp.git) and Debian package.

  If after installing the patch, user are receiving this kind of message in 
/var/log/syslog : "routing socket reports: No buffer space available".
  The next step, would be to increase the "net.core.rmem_max" and 
"net.core.wmem_max" values equally until the "routing socket reports: No buffer 
space available" message no longer showed up.

  [Other Info]

  NTP upstream (https://github.com/ntp-project/ntp.git)
  [Bug 2224] Use-after-free in routing socket code after dropping root. - 
Commit: d6df9d3
  [Bug 2890] Ignore ENOBUFS on routing netlink socket. - Commit: db47bd4 

  The use-after-free bug has been fix in Debian release (closes: #795315)
  Will submit the ignore-ENOBUFS-on-routing-netlink-socket in Debian in the 
next days.

  [Original Description]

  We have 1 server (among hundreds) that its ntp service is crashing.

  A few minute/seconds after a start attempts we can see the following in 
syslog:
  ntpd[2729]: peers refreshed
  ntpd[2729]: Listening on routing socket on fd #49 for interface updates
  ntpd[2729]: i/o error on routing socket No buffer space available - disabling
  kernel: [157516.495224] ntpd[2729]: segfault at 31 ip 0031 sp 
79f11788 error 14 in libpthread-2.15.so[7f967a5d9000+18000]

  OS: Ubuntu 12.04.4 LTS
  Kernel: 3.11.0-19-generic

  I tried to compare it to other servers, and the only thing I could find that 
is different is that while it's up (before it crashes) I can see the following 
when running "lsof | grep ntp":
  ntpd 2729 ntp 49u sock 0,7 0t0 2473952565 can't identify protocol.

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

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

[Touch-packages] [Bug 1510619] Re: Wily: add machine fails using kvm and lxcbr0

[Ryan Harper]

https://lists.linuxcontainers.org/pipermail/lxc-
devel/2015-October/012630.html

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

Title:
  Wily: add machine fails using kvm and lxcbr0

Status in juju-core:
  Invalid
Status in lxc package in Ubuntu:
  New

Bug description:
  Juju fails to start a machine after add-machine takes place.

  My environments.yaml:

  local:
type: local
container: kvm
network-bridge: lxcbr0

  Status output:

  ubuntu@ancient-spot:~$ juju status
  environment: local
  machines:
"0":
  agent-state: started
  agent-version: 1.24.7.1
  dns-name: localhost
  instance-id: localhost
  series: wily
  state-server-member-status: has-vote
"1":
  agent-state: pending
  instance-id: ubuntu-local-machine-1
  series: wily
  hardware: arch=amd64 cpu-cores=1 mem=512M root-disk=8192M

  debug log:

  http://paste.ubuntu.com/12980615/

  
  I never see anything in the logs which indicate machine-1 is being deployed 
or what else could be going on with it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1510619/+subscriptions

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

[Touch-packages] [Bug 1504781] Re: lxc-test-ubuntu hangs forever in trusty-proposed with Linux 3.13.0-66: AppArmor denies /dev/ptmx mounting

[Serge Hallyn]

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

** Also affects: lxc (Ubuntu Precise)
   Importance: Undecided
   Status: New

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

Title:
  lxc-test-ubuntu hangs forever in trusty-proposed with Linux 3.13.0-66:
  AppArmor denies /dev/ptmx mounting

Status in linux package in Ubuntu:
  Invalid
Status in lxc package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New
Status in lxc source package in Precise:
  New
Status in linux source package in Trusty:
  Invalid
Status in lxc source package in Trusty:
  Fix Released

Bug description:
  ==
  SRU Justification (for precise):
  Impact: containers fail to start!
  Regression potential: we only add a copy of an existing apparmor allow rule
    with a different syntax (no trailing /), leaving the old one for older
    aa/kernel.  There should be no regressions.
  Test case: lxc-create -t ubuntu -n u1; lxc-start -n u1
  ==

  We are seeing test suite failures under ADT testing with linux, linux-
  lts-utopic and linux-lts-vivid kernels:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/amd64/l/lxc/20151010_103318@/log.gz
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/i386/l/lxc/20151010_103325@/log.gz

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/amd64/l/lxc/20151009_085841@/log.gz
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/i386/l/lxc/20151009_091723@/log.gz

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/amd64/l/lxc/20151010_105332@/log.gz
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/i386/l/lxc/20151010_114021@/log.gz

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

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

[Touch-packages] [Bug 1510964] [NEW] window focus is unpredictable

[Dubstar_04]

Public bug reported:

window focus doen't follow mouse cursor so things like scrolling are
unpredictable as the window behind the selected window scrolls.

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

Title:
  window focus is unpredictable

Status in unity8 package in Ubuntu:
  New

Bug description:
  window focus doen't follow mouse cursor so things like scrolling are
  unpredictable as the window behind the selected window scrolls.

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

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

[Touch-packages] [Bug 1424819] Re: [icons] Missing import contacts from sim card icon

[Bill Filler]

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

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Bill Filler (bfiller)

** Changed in: address-book-app (Ubuntu)
   Importance: Undecided => Medium

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

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

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

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

Title:
  [icons] Missing import contacts from sim card icon

Status in Canonical System Image:
  In Progress
Status in Ubuntu theme:
  New
Status in Ubuntu UX:
  Fix Released
Status in address-book-app package in Ubuntu:
  In Progress

Bug description:
  We need a "import from sim" icon to use in address book app header.

  -- UX comment & resolution -

  As per bug comment, SIM import shouldn't sit permanently in the header. This 
feature is already available in the app settings of the Address Book app. 
  The only time user see the "Import" icon is at first time launch but this is 
a different issue.

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

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

[Touch-packages] [Bug 1510967] [NEW] Operating the OSK with mouse double-clicks buttons

[Michael Zanetti]

Public bug reported:

Pair a Bluetooth mouse with a phone but no keyboard. That will still
give you the OSK and allow typing things with the mouse on the OSK.
However, each button is pressed twice.

** Affects: ubuntu-keyboard
 Importance: Undecided
 Status: New

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

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

** Description changed:

- Pair a Bluetooth mouse with a phone but no Keyboard. That will still
+ Pair a Bluetooth mouse with a phone but no keyboard. That will still
  give you the OSK and allow typing things with the mouse on the OSK.
  However, each button is pressed twice.

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

Title:
  Operating the OSK with mouse double-clicks buttons

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

Bug description:
  Pair a Bluetooth mouse with a phone but no keyboard. That will still
  give you the OSK and allow typing things with the mouse on the OSK.
  However, each button is pressed twice.

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

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

[Touch-packages] [Bug 1510964] Re: window focus is unpredictable

[kevin gunn]

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

there are 2 bugs that might duplicate this one, but i'll just choose the
best

** This bug has been marked a duplicate of bug 1497091
   Mouse wheel does not work consistently

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

Title:
  window focus is unpredictable

Status in unity8 package in Ubuntu:
  New

Bug description:
  window focus doen't follow mouse cursor so things like scrolling are
  unpredictable as the window behind the selected window scrolls.

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

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

[Touch-packages] [Bug 1510968] [NEW] external monitor grid units are not set correctly

[Dubstar_04]

Public bug reported:

external monitor grid units are not set correctly so the desktop is
incorectly scaled.

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

Title:
  external monitor grid units are not set correctly

Status in unity8 package in Ubuntu:
  New

Bug description:
  external monitor grid units are not set correctly so the desktop is
  incorectly scaled.

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

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

[Touch-packages] [Bug 1510966] [NEW] Scolling is unpredictable

[Dubstar_04]

Public bug reported:

scolling the mousewheel is unpredictable. sometimes it works sometimes
it doesn't. it seems as if the mouse needs to be stationary for a period
of time before the scroll will be recognised.

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

** Attachment added: "unity8.log"
   https://bugs.launchpad.net/bugs/1510966/+attachment/4507583/+files/unity8.log

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

Title:
  Scolling is unpredictable

Status in unity8 package in Ubuntu:
  New

Bug description:
  scolling the mousewheel is unpredictable. sometimes it works sometimes
  it doesn't. it seems as if the mouse needs to be stationary for a
  period of time before the scroll will be recognised.

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

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

[Touch-packages] [Bug 1510972] [NEW] bsdtar default file name is /dev/st0

[Ryan Harper]

Public bug reported:

1. % lsb_release -rd
Description:Ubuntu Wily Werewolf (development branch)
Release:15.10

2.  % apt-cache policy bsdtar
bsdtar:
  Installed: 3.1.2-11build1
  Candidate: 3.1.2-11build1
  Version table:
 *** 3.1.2-11build1 0
500 http://us.archive.ubuntu.com/ubuntu/ wily/universe amd64 Packages
100 /var/lib/dpkg/status

3.  bsdtar -t should read from standard in if a file name is not
specified

4.  % bsdtar -t
bsdtar: Error opening archive: Failed to open '/dev/st0'


Note that if you specify -f -  (aka stdin) it works as expected.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: bsdtar 3.1.2-11build1
ProcVersionSignature: Ubuntu 4.0.0-4.6-generic 4.0.7
Uname: Linux 4.0.0-4-generic x86_64
ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
Date: Wed Oct 28 09:50:36 2015
InstallationDate: Installed on 2015-05-10 (170 days ago)
InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: libarchive
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug wily

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

Title:
  bsdtar default file name is /dev/st0

Status in libarchive package in Ubuntu:
  New

Bug description:
  1. % lsb_release -rd
  Description:  Ubuntu Wily Werewolf (development branch)
  Release:  15.10

  2.  % apt-cache policy bsdtar
  bsdtar:
Installed: 3.1.2-11build1
Candidate: 3.1.2-11build1
Version table:
   *** 3.1.2-11build1 0
  500 http://us.archive.ubuntu.com/ubuntu/ wily/universe amd64 Packages
  100 /var/lib/dpkg/status

  3.  bsdtar -t should read from standard in if a file name is not
  specified

  4.  % bsdtar -t
  bsdtar: Error opening archive: Failed to open '/dev/st0'

  
  Note that if you specify -f -  (aka stdin) it works as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: bsdtar 3.1.2-11build1
  ProcVersionSignature: Ubuntu 4.0.0-4.6-generic 4.0.7
  Uname: Linux 4.0.0-4-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  Date: Wed Oct 28 09:50:36 2015
  InstallationDate: Installed on 2015-05-10 (170 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libarchive
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1510971] [NEW] Sound indicator always appears muted

[Dubstar_04]

Public bug reported:

The sound indicator icon always appears to be muted even when sound is
playing. rc-proposed 28/10/15

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

Title:
  Sound indicator always appears muted

Status in unity8 package in Ubuntu:
  New

Bug description:
  The sound indicator icon always appears to be muted even when sound is
  playing. rc-proposed 28/10/15

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

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

[Touch-packages] [Bug 1510919] Re: developer mode toggle does nothing

[Jonas G. Drange]

Mako is affected, I was running the wrong build. Please ignore comment
#5.

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

Title:
  developer mode toggle does nothing

Status in Canonical System Image:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  Last know good image: 157
  Commit log for 158: 
http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-proposed/158.commitlog

  TEST CASE:
  1. Flash a device with bootstrap or upgrade to latest image
  2. Go to system-settings / About / Developer mode
  3. Toggle developer mode

  ACTUAL RESULT
  On a freshly flashed device, toggling dev mode on does nothing
  On an upgraded device with dev mode enabled, toggling dev mode off does 
nothing

  WORKAROUND
  Flash with --developer-mode

  = original description =
  Using a krillin on rc-proposed, developer mode does not enable an adb shell:

  ubuntu-touch/rc-proposed/bq-aquaris.en #159

  $ ubuntu-device-flash touch --bootstrap --channel ubuntu-touch/rc-
  proposed/bq-aquaris.en --recovery-image recovery-krillin.img

  Then boot device to wizard, walk through (I configured wifi, 
  passcode and have 2 SIMs online in the device). Defaults for location.

  Open System settings | about this phone | developer mode

  Enable developer mode

  On your pc:

  $ adb shell
  error: device not found

  Expected: a phablet shell on the device.

  Additionally, if you now reboot, the setting for developer mode is
  forgotten.

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

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

[Touch-packages] [Bug 1510969] [NEW] Windows cannot be resized

[Dubstar_04]

Public bug reported:

when in pocket pc mode windows with borders near the edges of the
display cannot be resized without accessing the launcher or spread.

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

Title:
  Windows cannot be resized

Status in unity8 package in Ubuntu:
  New

Bug description:
  when in pocket pc mode windows with borders near the edges of the
  display cannot be resized without accessing the launcher or spread.

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

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

[Touch-packages] [Bug 1510967] Re: Operating the OSK with mouse double-clicks buttons

[kevin gunn]

** Also affects: canonical-pocket-desktop
   Importance: Undecided
   Status: New

** Changed in: canonical-pocket-desktop
   Importance: Undecided => Medium

** Changed in: canonical-pocket-desktop
   Importance: Medium => High

** Changed in: ubuntu-keyboard
   Importance: Undecided => High

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

** Changed in: canonical-pocket-desktop
 Assignee: (unassigned) => kevin gunn (kgunn72)

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

Title:
  Operating the OSK with mouse double-clicks buttons

Status in canonical-pocket-desktop:
  New
Status in ubuntu-keyboard:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Pair a Bluetooth mouse with a phone but no keyboard. That will still
  give you the OSK and allow typing things with the mouse on the OSK.
  However, each button is pressed twice.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1510967/+subscriptions

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

[Touch-packages] [Bug 1510919] Re: developer mode toggle does nothing

[Zsombor Egri]

2015-10-28 13:40:25,358 - WARNING - QQmlExpression: Expression 
file:///usr/share/ubuntu/settings/system/qml-plugins/about/DevMode.qml:94:30 
depends on non-NOTIFYable properties:
2015-10-28 13:40:25,358 - WARNING - StorageAbout::developerMode
2015-10-28 13:40:33,696 - WARNING - QQmlExpression: Expression 
file:///usr/share/ubuntu/settings/system/qml-plugins/about/DevMode.qml:94:30 
depends on non-NOTIFYable properties:
2015-10-28 13:40:33,697 - WARNING - StorageAbout::developerMode

These warnings I assume come to the line [1]. If the property value is
false during the Switch.checked property initialization, the actual
value will not be updated to the Switch, as the property it is bound to
has no notify signal.

[1] http://bazaar.launchpad.net/~system-settings-touch/ubuntu-system-
settings/trunk/view/head:/plugins/about/DevMode.qml#L94

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

Title:
  developer mode toggle does nothing

Status in Canonical System Image:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  Last know good image: 157
  Commit log for 158: 
http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-proposed/158.commitlog

  TEST CASE:
  1. Flash a device with bootstrap or upgrade to latest image
  2. Go to system-settings / About / Developer mode
  3. Toggle developer mode

  ACTUAL RESULT
  On a freshly flashed device, toggling dev mode on does nothing
  On an upgraded device with dev mode enabled, toggling dev mode off does 
nothing

  WORKAROUND
  Flash with --developer-mode

  = original description =
  Using a krillin on rc-proposed, developer mode does not enable an adb shell:

  ubuntu-touch/rc-proposed/bq-aquaris.en #159

  $ ubuntu-device-flash touch --bootstrap --channel ubuntu-touch/rc-
  proposed/bq-aquaris.en --recovery-image recovery-krillin.img

  Then boot device to wizard, walk through (I configured wifi, 
  passcode and have 2 SIMs online in the device). Defaults for location.

  Open System settings | about this phone | developer mode

  Enable developer mode

  On your pc:

  $ adb shell
  error: device not found

  Expected: a phablet shell on the device.

  Additionally, if you now reboot, the setting for developer mode is
  forgotten.

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

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

[Touch-packages] [Bug 1501300] Re: Wily (15.10) this package got not compiled with __cxx11 support

[mitko]

I might be hitting the same or at least a related bug: I am using clang
3.7 to compile an application that itself uses libclang3.7 to do some
C++ parsing. I get unresolved symbol errors from the linker. Namely this
one single error, many times:

undefined reference to `clang::NamedDecl::getQualifiedNameAsString()
const'

The same source code compiles fine using gcc 5.2 so it really seems it's
a problem with the string ABI change of gcc and stale libraries.

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

Title:
  Wily (15.10) this package got not compiled with __cxx11 support

Status in llvm-toolchain-3.4 package in Ubuntu:
  Confirmed

Bug description:
  This packages does not contain any __cxx11 symbols when installed. This 
causes the problem that user-space applications cannot link successfully to it.
  Recompile the (untouched) dpkg source package on the same machine and 
installing it solved the problem.

  There seems something in the package generation broken.

  Steps to reproduce try to compile the attached minimal example
  https://github.com/goldhoorn/clang-sandbox

  
  Errors:
  CMakeFiles/main.dir/main.cpp.o: In function `foo()':
  /tmp/clang-sandbox/main.cpp:25: undefined reference to 
`clang::NamedDecl::getQualifiedNameAsString[abi:cxx11]() const'
  CMakeFiles/main.dir/main.cpp.o: In function 
`clang::QualType::getAsString[abi:cxx11](clang::SplitQualType)':
  /usr/lib/llvm-3.4/include/clang/AST/Type.h:868: undefined reference to 
`clang::QualType::getAsString[abi:cxx11](clang::Type const*, clang::Qualifiers)'
  CMakeFiles/main.dir/main.cpp.o: In function 
`clang::ast_matchers::internal::matcher_matchesName0Matcher::matches(clang::NamedDecl
 const&, clang::ast_matchers::internal::ASTMatchFinder*, 
clang::ast_matchers::internal::BoundNodesTreeBuilder*) const':
  /usr/lib/llvm-3.4/include/clang/ASTMatchers/ASTMatchers.h:1439: undefined 
reference to `clang::NamedDecl::getQualifiedNameAsString[abi:cxx11]() const'
  CMakeFiles/main.dir/main.cpp.o: In function 
`clang::ast_matchers::internal::matcher_hasName0Matcher::matches(clang::NamedDecl
 const&, clang::ast_matchers::internal::ASTMatchFinder*, 
clang::ast_matchers::internal::BoundNodesTreeBuilder*) const':
  /usr/lib/llvm-3.4/include/clang/ASTMatchers/ASTMatchers.h:1411: undefined 
reference to `clang::NamedDecl::getQualifiedNameAsString[abi:cxx11]() const'
  /usr/lib/llvm-3.4/lib/libclangAST.a(ExprConstant.o): In function 
`handleIntIntBinOp((anonymous namespace)::EvalInfo&, clang::Expr const*, 
llvm::APSInt const&, clang::BinaryOperatorKind, llvm::APSInt, llvm::APSInt&)':
  (.text+0x6a35): undefined reference to `llvm::APInt::toString(unsigned int, 
bool) const'
  /usr/lib/llvm-3.4/lib/libclangAST.a(StmtPrinter.o): In function `(anonymous 
namespace)::StmtPrinter::VisitIntegerLiteral(clang::IntegerLiteral*) [clone 
.isra.302]':

  ...

  This example is workign on privious ubuntus and debians

  Sysinfo:
  Description:  Ubuntu Wily Werewolf (development branch)
  Release:  15.10
  In a VirtualBox

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.4/+bug/1501300/+subscriptions

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

[Touch-packages] [Bug 1510971] Re: Sound indicator always appears muted

[Dubstar_04]

** Attachment added: "image20151028_141113888.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1510971/+attachment/4507587/+files/image20151028_141113888.jpg

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

Title:
  Sound indicator always appears muted

Status in unity8 package in Ubuntu:
  New

Bug description:
  The sound indicator icon always appears to be muted even when sound is
  playing. rc-proposed 28/10/15

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

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

[Touch-packages] [Bug 1419829] Re: [Scope] location settings are enabled by default

[Alejandro J. Cura]

Adding location service to the bug.

** Also affects: location-service (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: location-service (Ubuntu)
   Importance: Undecided => High

** Changed in: location-service (Ubuntu)
 Assignee: (unassigned) => Thomas Voß (thomas-voss)

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

Title:
  [Scope] location settings are enabled by default

Status in Canonical System Image:
  In Progress
Status in Ubuntu UX:
  Opinion
Status in location-service package in Ubuntu:
  New
Status in unity-scopes-shell package in Ubuntu:
  Confirmed

Bug description:
  This is in contrast to the rest of the system where user have to
  explicitly grant access right upfront.

  Possible solution would be to add a new page in phone setup wizard
  asking for whether scopes are allowed to use location or not and then
  applying this to individual scope location settings.

  UX comment-

  Potential new project: When scopes will be launched as apps, we'll
  probably need some coach marks // independent onboard experience to
  explain data consumption and location services usage.

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

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

[Touch-packages] [Bug 1510919] Re: developer mode toggle does nothing

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: Zoltan Balogh (bzoltan) => Zsombor Egri (zsombi)

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

Title:
  developer mode toggle does nothing

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

Bug description:
  Last know good image: 157
  Commit log for 158: 
http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-proposed/158.commitlog

  TEST CASE:
  1. Flash a device with bootstrap or upgrade to latest image
  2. Go to system-settings / About / Developer mode
  3. Toggle developer mode

  ACTUAL RESULT
  On a freshly flashed device, toggling dev mode on does nothing
  On an upgraded device with dev mode enabled, toggling dev mode off does 
nothing

  WORKAROUND
  Flash with --developer-mode

  = original description =
  Using a krillin on rc-proposed, developer mode does not enable an adb shell:

  ubuntu-touch/rc-proposed/bq-aquaris.en #159

  $ ubuntu-device-flash touch --bootstrap --channel ubuntu-touch/rc-
  proposed/bq-aquaris.en --recovery-image recovery-krillin.img

  Then boot device to wizard, walk through (I configured wifi, 
  passcode and have 2 SIMs online in the device). Defaults for location.

  Open System settings | about this phone | developer mode

  Enable developer mode

  On your pc:

  $ adb shell
  error: device not found

  Expected: a phablet shell on the device.

  Additionally, if you now reboot, the setting for developer mode is
  forgotten.

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

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

[Touch-packages] [Bug 1504781] Re: lxc-test-ubuntu hangs forever in trusty-proposed with Linux 3.13.0-66: AppArmor denies /dev/ptmx mounting

[Serge Hallyn]

** Description changed:

+ ==
+ SRU Justification:
+ Impact: containers fail to start!
+ Regression potential: we only add a copy of an existing apparmor allow rule
+   with a different syntax (no trailing /), leaving the old one for older
+   aa/kernel.  There should be no regressions.
+ Test case: lxc-create -t ubuntu -n u1; lxc-start -n u1
+ ==
+ 
  We are seeing test suite failures under ADT testing with linux, linux-
  lts-utopic and linux-lts-vivid kernels:
  
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/amd64/l/lxc/20151010_103318@/log.gz
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/i386/l/lxc/20151010_103325@/log.gz
  
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/amd64/l/lxc/20151009_085841@/log.gz
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/i386/l/lxc/20151009_091723@/log.gz
  
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/amd64/l/lxc/20151010_105332@/log.gz
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/i386/l/lxc/20151010_114021@/log.gz

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

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

** Description changed:

  ==
- SRU Justification:
+ SRU Justification (for precise):
  Impact: containers fail to start!
  Regression potential: we only add a copy of an existing apparmor allow rule
-   with a different syntax (no trailing /), leaving the old one for older
-   aa/kernel.  There should be no regressions.
+   with a different syntax (no trailing /), leaving the old one for older
+   aa/kernel.  There should be no regressions.
  Test case: lxc-create -t ubuntu -n u1; lxc-start -n u1
  ==
  
  We are seeing test suite failures under ADT testing with linux, linux-
  lts-utopic and linux-lts-vivid kernels:
  
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/amd64/l/lxc/20151010_103318@/log.gz
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/i386/l/lxc/20151010_103325@/log.gz
  
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/amd64/l/lxc/20151009_085841@/log.gz
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/i386/l/lxc/20151009_091723@/log.gz
  
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/amd64/l/lxc/20151010_105332@/log.gz
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/i386/l/lxc/20151010_114021@/log.gz

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

Title:
  lxc-test-ubuntu hangs forever in trusty-proposed with Linux 3.13.0-66:
  AppArmor denies /dev/ptmx mounting

Status in linux package in Ubuntu:
  Invalid
Status in lxc package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New
Status in lxc source package in Precise:
  New
Status in linux source package in Trusty:
  Invalid
Status in lxc source package in Trusty:
  Fix Released

Bug description:
  ==
  SRU Justification (for precise):
  Impact: containers fail to start!
  Regression potential: we only add a copy of an existing apparmor allow rule
    with a different syntax (no trailing /), leaving the old one for older
    aa/kernel.  There should be no regressions.
  Test case: lxc-create -t ubuntu -n u1; lxc-start -n u1
  ==

  We are seeing test suite failures under ADT testing with linux, linux-
  lts-utopic and linux-lts-vivid kernels:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/amd64/l/lxc/20151010_103318@/log.gz
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/i386/l/lxc/20151010_103325@/log.gz

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/amd64/l/lxc/20151

[Touch-packages] [Bug 1509752] Re: Bug in ensure_not_symlink() from 0003-CVE-2015-1335.patch

[Serge Hallyn]

Yup, switching in the upstream fix works - will upload that in a bit.

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

Title:
  Bug in ensure_not_symlink() from 0003-CVE-2015-1335.patch

Status in lxc package in Ubuntu:
  Confirmed

Bug description:
  This bug/limitation is present in lxc from 1.0.7-0ubuntu0.5 through
  1.0.7-0ubuntu0.9 (or anything that incorporates
  0003-CVE-2015-1335.patch).  Basically, the limitation is obvious when
  using recursive bind mounts because ensure_not_symlink() only checks
  the last line of /proc/self/mountinfo which will be a submount so will
  always fail the test and trigger:

  ensure_not_symlink: 1413 Mount onto /usr/lib/x86_64-linux-
  gnu/lxc/storage resulted in /usr/lib/x86_64-linux-
  gnu/lxc/storage/submount, not /usr/lib/x86_64-linux-gnu/lxc/storage

  Sorry if this is a duplicate, I did spend quite some time trying to
  find a similar report.

  Thanks!

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

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

[Touch-packages] [Bug 1501300] Re: Wily (15.10) this package got not compiled with __cxx11 support

[Matthias Goldhoorn]

I just uploaded a patched version of the 3.7 to my personal PPA, the 3.7 has 
the same issue than this 3.4.
Please try the llvm-toolchain-3.7 1:3.7-2ubuntu2 from my rock-ppa if this helps 
you create a bug report on the 3.7 and i will add the patch there also, 
hopefully the package maintainer will respond and merge them soon...

P.S. the package needs a bit to build on the ubuntu servers:
https://launchpad.net/~matthias-l/+archive/ubuntu/rock-
ppa/+build/8213723

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

Title:
  Wily (15.10) this package got not compiled with __cxx11 support

Status in llvm-toolchain-3.4 package in Ubuntu:
  Confirmed

Bug description:
  This packages does not contain any __cxx11 symbols when installed. This 
causes the problem that user-space applications cannot link successfully to it.
  Recompile the (untouched) dpkg source package on the same machine and 
installing it solved the problem.

  There seems something in the package generation broken.

  Steps to reproduce try to compile the attached minimal example
  https://github.com/goldhoorn/clang-sandbox

  
  Errors:
  CMakeFiles/main.dir/main.cpp.o: In function `foo()':
  /tmp/clang-sandbox/main.cpp:25: undefined reference to 
`clang::NamedDecl::getQualifiedNameAsString[abi:cxx11]() const'
  CMakeFiles/main.dir/main.cpp.o: In function 
`clang::QualType::getAsString[abi:cxx11](clang::SplitQualType)':
  /usr/lib/llvm-3.4/include/clang/AST/Type.h:868: undefined reference to 
`clang::QualType::getAsString[abi:cxx11](clang::Type const*, clang::Qualifiers)'
  CMakeFiles/main.dir/main.cpp.o: In function 
`clang::ast_matchers::internal::matcher_matchesName0Matcher::matches(clang::NamedDecl
 const&, clang::ast_matchers::internal::ASTMatchFinder*, 
clang::ast_matchers::internal::BoundNodesTreeBuilder*) const':
  /usr/lib/llvm-3.4/include/clang/ASTMatchers/ASTMatchers.h:1439: undefined 
reference to `clang::NamedDecl::getQualifiedNameAsString[abi:cxx11]() const'
  CMakeFiles/main.dir/main.cpp.o: In function 
`clang::ast_matchers::internal::matcher_hasName0Matcher::matches(clang::NamedDecl
 const&, clang::ast_matchers::internal::ASTMatchFinder*, 
clang::ast_matchers::internal::BoundNodesTreeBuilder*) const':
  /usr/lib/llvm-3.4/include/clang/ASTMatchers/ASTMatchers.h:1411: undefined 
reference to `clang::NamedDecl::getQualifiedNameAsString[abi:cxx11]() const'
  /usr/lib/llvm-3.4/lib/libclangAST.a(ExprConstant.o): In function 
`handleIntIntBinOp((anonymous namespace)::EvalInfo&, clang::Expr const*, 
llvm::APSInt const&, clang::BinaryOperatorKind, llvm::APSInt, llvm::APSInt&)':
  (.text+0x6a35): undefined reference to `llvm::APInt::toString(unsigned int, 
bool) const'
  /usr/lib/llvm-3.4/lib/libclangAST.a(StmtPrinter.o): In function `(anonymous 
namespace)::StmtPrinter::VisitIntegerLiteral(clang::IntegerLiteral*) [clone 
.isra.302]':

  ...

  This example is workign on privious ubuntus and debians

  Sysinfo:
  Description:  Ubuntu Wily Werewolf (development branch)
  Release:  15.10
  In a VirtualBox

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.4/+bug/1501300/+subscriptions

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

[Touch-packages] [Bug 1330959] Today's client exec meeting is cancelled...

[Joe Odukoya]

... normal service will resume next week.

Cheers

Joe
-
Joe Odukoya
Product Manager | Ubuntu Mobile

Mobile: +44 (0) 7901 558 437
Office: +44 (0) 20 7630 2467

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

Title:
  Art in cards with backgrounds are Ubuntu-shaped

Status in Canonical System Image:
  Incomplete
Status in Ubuntu UX:
  Won't Fix
Status in ubuntu-ui-toolkit package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Won't Fix
Status in unity8 package in Ubuntu RTM:
  Won't Fix

Bug description:
  When a card has its background enabled, the art should not have its
  bottom edge shaped.

  Until the new shape item comes, we should probably use the
  UbuntuShapeForItem component.

  -

  Desired resolution:

  This is part of a bigger redesign project (Scopes toolkit) and it
  can't be fixed as a single bug. The description and specs will be
  updated as soon as they are available.

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

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

[Touch-packages] [Bug 1510971] Re: Sound indicator always appears muted

[Lukáš Tinkl]

** Also affects: indicator-sound (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/1510971

Title:
  Sound indicator always appears muted

Status in indicator-sound package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  The sound indicator icon always appears to be muted even when sound is
  playing. rc-proposed 28/10/15

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1510971/+subscriptions

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

[Touch-packages] [Bug 1510969] Re: Windows cannot be resized

[Lukáš Tinkl]

The situation should improve once we implement the push-against-edge to
show launcher/spread.

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

Title:
  Windows cannot be resized

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  when in pocket pc mode windows with borders near the edges of the
  display cannot be resized without accessing the launcher or spread.

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

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

[Touch-packages] [Bug 1510893] [NEW] "ubuntu-bug" crashes

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

When I type "ubuntu-bug", after selecting X-org and "other", and typing
my password for sudo, I get

christine@pengo:~$ ubuntu-bug
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
ERROR: hook /usr/share/apport/package-hooks/source_xorg.py crashed:
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/apport/report.py", line 197, in _run_hook
symb['add_info'](report, ui)
  File "/usr/share/apport/package-hooks/source_xorg.py", line 677, in add_info
attach_nvidia_info(report, ui)
  File "/usr/share/apport/package-hooks/source_xorg.py", line 521, in 
attach_nvidia_info
attach_file(report, logfile)
  File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 115, in 
attach_file
report[key] = read_file(path, force_unicode=force_unicode)
  File "/usr/lib/python3/dist-packages/problem_report.py", line 627, in 
__setitem__
assert k.replace('.', '').replace('-', '').replace('_', '').isalnum()
AssertionError

** Affects: apport (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: bot-comment
-- 
"ubuntu-bug" crashes
https://bugs.launchpad.net/bugs/1510893
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to apport in Ubuntu.

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

[Touch-packages] [Bug 1507678] Re: include skype and spotify repositories by default

[Adam Conrad]

We won't include any non-Ubuntu repositories in the default
configuration, as we have no way of verifying what's in them.

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

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

Title:
  include skype and spotify repositories by default

Status in apt package in Ubuntu:
  Won't Fix

Bug description:
  include skype and spotify repositories by default

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

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

[Touch-packages] [Bug 1509752] Re: Bug in ensure_not_symlink() from 0003-CVE-2015-1335.patch

[Serge Hallyn]

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

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

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

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

Title:
  Bug in ensure_not_symlink() from 0003-CVE-2015-1335.patch

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Trusty:
  New

Bug description:
  This bug/limitation is present in lxc from 1.0.7-0ubuntu0.5 through
  1.0.7-0ubuntu0.9 (or anything that incorporates
  0003-CVE-2015-1335.patch).  Basically, the limitation is obvious when
  using recursive bind mounts because ensure_not_symlink() only checks
  the last line of /proc/self/mountinfo which will be a submount so will
  always fail the test and trigger:

  ensure_not_symlink: 1413 Mount onto /usr/lib/x86_64-linux-
  gnu/lxc/storage resulted in /usr/lib/x86_64-linux-
  gnu/lxc/storage/submount, not /usr/lib/x86_64-linux-gnu/lxc/storage

  Sorry if this is a duplicate, I did spend quite some time trying to
  find a similar report.

  Thanks!

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

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

[Touch-packages] [Bug 1510972] Re: bsdtar default file name is /dev/st0

[Andreas Henriksson]

See http://sources.debian.net/src/libarchive/3.1.2-11/tar/bsdtar.c/#L74
for explanation/reason and where to hack if you want to change the
behaviour. (See apple ifdef for reference.)

Feel free to convince upstream about changing the behaviour if you still
think it should be done after investigating the above.

(// the Debian maintainer of libarchive.)

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

Title:
  bsdtar default file name is /dev/st0

Status in libarchive package in Ubuntu:
  New

Bug description:
  1. % lsb_release -rd
  Description:  Ubuntu Wily Werewolf (development branch)
  Release:  15.10

  2.  % apt-cache policy bsdtar
  bsdtar:
Installed: 3.1.2-11build1
Candidate: 3.1.2-11build1
Version table:
   *** 3.1.2-11build1 0
  500 http://us.archive.ubuntu.com/ubuntu/ wily/universe amd64 Packages
  100 /var/lib/dpkg/status

  3.  bsdtar -t should read from standard in if a file name is not
  specified

  4.  % bsdtar -t
  bsdtar: Error opening archive: Failed to open '/dev/st0'

  
  Note that if you specify -f -  (aka stdin) it works as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: bsdtar 3.1.2-11build1
  ProcVersionSignature: Ubuntu 4.0.0-4.6-generic 4.0.7
  Uname: Linux 4.0.0-4-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  Date: Wed Oct 28 09:50:36 2015
  InstallationDate: Installed on 2015-05-10 (170 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libarchive
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1510988] [NEW] greeter password prompt doesn't shift up when bt mouse is connected

[kevin gunn]

Public bug reported:

when the N7 is in touch mode, no mouse connected, selecting the password
prompt on the greeter/lockscreen - will cause the OSK to appear and the
password prompt to shift up

when a bt mouse is connected, the password prompt doesn't shift up -
with the no bt keyboard case this is a problem

** Affects: canonical-pocket-desktop
 Importance: Medium
 Assignee: kevin gunn (kgunn72)
 Status: New

** Affects: unity8 (Ubuntu)
 Importance: Medium
 Status: New

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

** Changed in: canonical-pocket-desktop
   Importance: Undecided => Medium

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

** Changed in: canonical-pocket-desktop
 Assignee: (unassigned) => kevin gunn (kgunn72)

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

Title:
  greeter password prompt doesn't shift up when bt mouse is connected

Status in canonical-pocket-desktop:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  when the N7 is in touch mode, no mouse connected, selecting the
  password prompt on the greeter/lockscreen - will cause the OSK to
  appear and the password prompt to shift up

  when a bt mouse is connected, the password prompt doesn't shift up -
  with the no bt keyboard case this is a problem

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1510988/+subscriptions

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

[Touch-packages] [Bug 1510969] Re: Windows cannot be resized

[Michael Zanetti]

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

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Daniel d'Andrada (dandrader)

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

Title:
  Windows cannot be resized

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  when in pocket pc mode windows with borders near the edges of the
  display cannot be resized without accessing the launcher or spread.

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

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

[Touch-packages] [Bug 1510969] Re: Windows cannot be resized

[Lukáš Tinkl]

** Branch linked: lp:~dandrader/unity8/mouseEdgePush

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

Title:
  Windows cannot be resized

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  when in pocket pc mode windows with borders near the edges of the
  display cannot be resized without accessing the launcher or spread.

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

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

[Touch-packages] [Bug 1503693] Re: Dim timeout gsetting key not set anymore

[Jonas G. Drange]

** Also affects: gsettings-qt (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Dim timeout gsetting key not set anymore

Status in Canonical System Image:
  Confirmed
Status in gsettings-qt package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete

Bug description:
  The dim-timeout gsettings key is not set anymore when the activity-
  timeout key changes, so a default value of 45sec is used for dim-
  timeout regardless of the activity timeout selected by the user in the
  batter plugin.

  The logic to set the dim timeout value is there in
  battery/SleepValues.xml in the GSettings onChanged handler, but it
  seems that the onChanged handler is not called when the activity-
  timeout value changes.

  Not sure if this is a problem in the way ubuntu-system-settings uses
  the GSettings QML item, or if the item implementation itself is broken
  somehow.

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

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

[Touch-packages] [Bug 1510893] Re: "ubuntu-bug" crashes

[Brian Murray]

What release of Ubuntu is this? What version of apport are you using?

** Package changed: ubuntu => apport (Ubuntu)

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

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

Title:
  "ubuntu-bug" crashes

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  When I type "ubuntu-bug", after selecting X-org and "other", and
  typing my password for sudo, I get

  christine@pengo:~$ ubuntu-bug
  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
  ERROR: hook /usr/share/apport/package-hooks/source_xorg.py crashed:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 197, in 
_run_hook
  symb['add_info'](report, ui)
File "/usr/share/apport/package-hooks/source_xorg.py", line 677, in add_info
  attach_nvidia_info(report, ui)
File "/usr/share/apport/package-hooks/source_xorg.py", line 521, in 
attach_nvidia_info
  attach_file(report, logfile)
File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 115, in 
attach_file
  report[key] = read_file(path, force_unicode=force_unicode)
File "/usr/lib/python3/dist-packages/problem_report.py", line 627, in 
__setitem__
  assert k.replace('.', '').replace('-', '').replace('_', '').isalnum()
  AssertionError

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

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

[Touch-packages] [Bug 1510919] Re: developer mode toggle does nothing

[Launchpad Bug Tracker]

** Branch linked: lp:~zsombi/ubuntu-ui-toolkit/checkFix

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

Title:
  developer mode toggle does nothing

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

Bug description:
  Last know good image: 157
  Commit log for 158: 
http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-proposed/158.commitlog

  TEST CASE:
  1. Flash a device with bootstrap or upgrade to latest image
  2. Go to system-settings / About / Developer mode
  3. Toggle developer mode

  ACTUAL RESULT
  On a freshly flashed device, toggling dev mode on does nothing
  On an upgraded device with dev mode enabled, toggling dev mode off does 
nothing

  WORKAROUND
  Flash with --developer-mode

  = original description =
  Using a krillin on rc-proposed, developer mode does not enable an adb shell:

  ubuntu-touch/rc-proposed/bq-aquaris.en #159

  $ ubuntu-device-flash touch --bootstrap --channel ubuntu-touch/rc-
  proposed/bq-aquaris.en --recovery-image recovery-krillin.img

  Then boot device to wizard, walk through (I configured wifi, 
  passcode and have 2 SIMs online in the device). Defaults for location.

  Open System settings | about this phone | developer mode

  Enable developer mode

  On your pc:

  $ adb shell
  error: device not found

  Expected: a phablet shell on the device.

  Additionally, if you now reboot, the setting for developer mode is
  forgotten.

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

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

[Touch-packages] [Bug 1509752] Re: Bug in ensure_not_symlink() from 0003-CVE-2015-1335.patch

[Serge Hallyn]

No, sadly one testcase - lxc-test-unpriv -  still fails:

Oct 28 15:33:49 lxct1 kernel: [ 2659.417204] type=1400
audit(1446046429.177:52): apparmor="DENIED" operation="mount"
info="failed flags match" error=-13 profile="/usr/bin/lxc-start"
name="/home/lxcunpriv/.local/share/lxc/c1/rootfs/dev/console" pid=23805
comm="lxc-start" srcname="/dev/console" flags="rw, bind"

(Note that running unprivileged containers by hand does work)

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

Title:
  Bug in ensure_not_symlink() from 0003-CVE-2015-1335.patch

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Trusty:
  New

Bug description:
  This bug/limitation is present in lxc from 1.0.7-0ubuntu0.5 through
  1.0.7-0ubuntu0.9 (or anything that incorporates
  0003-CVE-2015-1335.patch).  Basically, the limitation is obvious when
  using recursive bind mounts because ensure_not_symlink() only checks
  the last line of /proc/self/mountinfo which will be a submount so will
  always fail the test and trigger:

  ensure_not_symlink: 1413 Mount onto /usr/lib/x86_64-linux-
  gnu/lxc/storage resulted in /usr/lib/x86_64-linux-
  gnu/lxc/storage/submount, not /usr/lib/x86_64-linux-gnu/lxc/storage

  Sorry if this is a duplicate, I did spend quite some time trying to
  find a similar report.

  Thanks!

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

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

[Touch-packages] [Bug 1503693] Re: Dim timeout gsetting key not set anymore

[Jonas G. Drange]

I did this:
1. Build and install gsettings-qt from 
lp:~unity-team/gsettings-qt/bump-changelog
2. Log on onChanged in GSettings in SleepValues.qml
3. Change the sleep value, I get a log and therefore changed event.
4. Reinstall using sudo apt-get install 
{libgsettings-qt1,qtdeclarative5-gsettings1.0}=0.1+15.04.20150810-0ubuntu1
5. Do step 2 and 3 without any log.

It seems changing a setting using the GSettings binding does not
generate the “changed“, but changing it from the command line does.

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

Title:
  Dim timeout gsetting key not set anymore

Status in Canonical System Image:
  Confirmed
Status in gsettings-qt package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete

Bug description:
  The dim-timeout gsettings key is not set anymore when the activity-
  timeout key changes, so a default value of 45sec is used for dim-
  timeout regardless of the activity timeout selected by the user in the
  batter plugin.

  The logic to set the dim timeout value is there in
  battery/SleepValues.xml in the GSettings onChanged handler, but it
  seems that the onChanged handler is not called when the activity-
  timeout value changes.

  Not sure if this is a problem in the way ubuntu-system-settings uses
  the GSettings QML item, or if the item implementation itself is broken
  somehow.

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

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

[Touch-packages] [Bug 1510919] Re: developer mode toggle does nothing

[Zsombor Egri]

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

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

Title:
  developer mode toggle does nothing

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

Bug description:
  Last know good image: 157
  Commit log for 158: 
http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-proposed/158.commitlog

  TEST CASE:
  1. Flash a device with bootstrap or upgrade to latest image
  2. Go to system-settings / About / Developer mode
  3. Toggle developer mode

  ACTUAL RESULT
  On a freshly flashed device, toggling dev mode on does nothing
  On an upgraded device with dev mode enabled, toggling dev mode off does 
nothing

  WORKAROUND
  Flash with --developer-mode

  = original description =
  Using a krillin on rc-proposed, developer mode does not enable an adb shell:

  ubuntu-touch/rc-proposed/bq-aquaris.en #159

  $ ubuntu-device-flash touch --bootstrap --channel ubuntu-touch/rc-
  proposed/bq-aquaris.en --recovery-image recovery-krillin.img

  Then boot device to wizard, walk through (I configured wifi, 
  passcode and have 2 SIMs online in the device). Defaults for location.

  Open System settings | about this phone | developer mode

  Enable developer mode

  On your pc:

  $ adb shell
  error: device not found

  Expected: a phablet shell on the device.

  Additionally, if you now reboot, the setting for developer mode is
  forgotten.

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

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

[Touch-packages] [Bug 1510969] Re: Windows cannot be resized

[kevin gunn]

** Also affects: canonical-pocket-desktop
   Importance: Undecided
   Status: New

** Changed in: canonical-pocket-desktop
 Assignee: (unassigned) => kevin gunn (kgunn72)

** Changed in: canonical-pocket-desktop
   Importance: Undecided => High

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

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

Title:
  Windows cannot be resized

Status in canonical-pocket-desktop:
  New
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  when in pocket pc mode windows with borders near the edges of the
  display cannot be resized without accessing the launcher or spread.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1510969/+subscriptions

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