[Touch-packages] [Bug 1512131] [NEW] Apparmor complains about multiple /run/dovecot file access

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Hi, since I upgraded from XUbuntu 15.04 to 15.10 I started to get a lot
of apparmor complains about dovecot. The complains were more or less
like this:

operation="connect" profile="/usr/lib/dovecot/auth" 
name="/run/dovecot/anvil-auth-penalty" comm="auth" requested_mask="wr" 
denied_mask="wr" fsuid=0 ouid=0
operation="connect" profile="/usr/lib/dovecot/auth" 
name="/run/dovecot/auth-worker" comm="auth" requested_mask="wr" 
denied_mask="wr" fsuid=117 ouid=117
operation="file_perm" profile="/usr/lib/dovecot/anvil" 
name="/run/dovecot/anvil-auth-penalty" comm="anvil" requested_mask="r" 
denied_mask="r" fsuid=117 ouid=0
operation="file_perm" profile="/usr/lib/dovecot/anvil" 
name="/run/dovecot/anvil" comm="anvil" requested_mask="r" denied_mask="r" 
fsuid=117 ouid=0
operation="file_perm" profile="/usr/lib/dovecot/anvil" 
name="/run/dovecot/anvil" comm="anvil" requested_mask="w" denied_mask="w" 
fsuid=117 ouid=0
operation="file_perm" profile="/usr/lib/dovecot/auth" 
name="/run/dovecot/anvil-auth-penalty" comm="auth" requested_mask="w" 
denied_mask="w" fsuid=0 ouid=0
operation="file_perm" profile="/usr/lib/dovecot/auth" 
name="/run/dovecot/auth-master" comm="auth" requested_mask="w" denied_mask="w" 
fsuid=117 ouid=0
operation="file_perm" profile="/usr/lib/dovecot/auth" 
name="/run/dovecot/auth-worker" comm="auth" requested_mask="r" denied_mask="r" 
fsuid=0 ouid=117
operation="file_perm" profile="/usr/lib/dovecot/auth" 
name="/run/dovecot/auth-worker" comm="auth" requested_mask="w" denied_mask="w" 
fsuid=117 ouid=117
operation="file_perm" profile="/usr/lib/dovecot/auth" 
name="/run/dovecot/login/login" comm="auth" requested_mask="r" denied_mask="r" 
fsuid=117 ouid=0
operation="file_perm" profile="/usr/lib/dovecot/auth" 
name="/run/dovecot/login/login" comm="auth" requested_mask="w" denied_mask="w" 
fsuid=117 ouid=0
operation="file_perm" profile="/usr/lib/dovecot/imap" 
name="/run/dovecot/login/imap" comm="imap" requested_mask="r" denied_mask="r" 
fsuid=0 ouid=0
operation="file_perm" profile="/usr/lib/dovecot/imap" 
name="/run/dovecot/login/imap" comm="imap" requested_mask="w" denied_mask="w" 
fsuid=0 ouid=0
operation="file_perm" profile="/usr/lib/dovecot/ssl-params" 
name="/run/dovecot/login/ssl-params" comm="ssl-params" requested_mask="w" 
denied_mask="w" fsuid=0 ouid=0
operation="file_receive" profile="/usr/lib/dovecot/imap" comm="imap" 
family="unix" sock_type="stream" protocol=0 requested_mask="send receive" 
denied_mask="send receive" addr=none peer_addr=none 
peer="/usr/lib/dovecot/imap-login"
operation="file_receive" profile="/usr/lib/dovecot/imap-login" comm="imap" 
family="unix" sock_type="stream" protocol=0 requested_mask="send receive" 
denied_mask="send receive" addr=none peer_addr=none peer="/usr/lib/dovecot/imap"
operation="signal" profile="/usr/sbin/dovecot" comm="dovecot" 
requested_mask="send" denied_mask="send" signal=int peer="/usr/lib/dovecot/auth"


To avoid them, I added some stuff to the /etc/apparmor.d/local directory, patch 
attached.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: dovecot-core 1:2.2.18-2ubuntu2
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
CurrentDesktop: XFCE
Date: Sun Nov  1 19:42:56 2015
InstallationDate: Installed on 2012-11-11 (1085 days ago)
InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1)
SourcePackage: dovecot
UpgradeStatus: Upgraded to wily on 2015-11-01 (0 days ago)

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


** Tags: amd64 apport-bug patch wily
-- 
Apparmor complains about multiple /run/dovecot file access
https://bugs.launchpad.net/bugs/1512131
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to apparmor 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 1512131] Re: Apparmor complains about multiple /run/dovecot file access

[Marc Deslauriers]

** Package changed: dovecot (Ubuntu) => apparmor (Ubuntu)

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

Title:
  Apparmor complains about multiple /run/dovecot file access

Status in apparmor package in Ubuntu:
  New

Bug description:
  Hi, since I upgraded from XUbuntu 15.04 to 15.10 I started to get a
  lot of apparmor complains about dovecot. The complains were more or
  less like this:

  operation="connect" profile="/usr/lib/dovecot/auth" 
name="/run/dovecot/anvil-auth-penalty" comm="auth" requested_mask="wr" 
denied_mask="wr" fsuid=0 ouid=0
  operation="connect" profile="/usr/lib/dovecot/auth" 
name="/run/dovecot/auth-worker" comm="auth" requested_mask="wr" 
denied_mask="wr" fsuid=117 ouid=117
  operation="file_perm" profile="/usr/lib/dovecot/anvil" 
name="/run/dovecot/anvil-auth-penalty" comm="anvil" requested_mask="r" 
denied_mask="r" fsuid=117 ouid=0
  operation="file_perm" profile="/usr/lib/dovecot/anvil" 
name="/run/dovecot/anvil" comm="anvil" requested_mask="r" denied_mask="r" 
fsuid=117 ouid=0
  operation="file_perm" profile="/usr/lib/dovecot/anvil" 
name="/run/dovecot/anvil" comm="anvil" requested_mask="w" denied_mask="w" 
fsuid=117 ouid=0
  operation="file_perm" profile="/usr/lib/dovecot/auth" 
name="/run/dovecot/anvil-auth-penalty" comm="auth" requested_mask="w" 
denied_mask="w" fsuid=0 ouid=0
  operation="file_perm" profile="/usr/lib/dovecot/auth" 
name="/run/dovecot/auth-master" comm="auth" requested_mask="w" denied_mask="w" 
fsuid=117 ouid=0
  operation="file_perm" profile="/usr/lib/dovecot/auth" 
name="/run/dovecot/auth-worker" comm="auth" requested_mask="r" denied_mask="r" 
fsuid=0 ouid=117
  operation="file_perm" profile="/usr/lib/dovecot/auth" 
name="/run/dovecot/auth-worker" comm="auth" requested_mask="w" denied_mask="w" 
fsuid=117 ouid=117
  operation="file_perm" profile="/usr/lib/dovecot/auth" 
name="/run/dovecot/login/login" comm="auth" requested_mask="r" denied_mask="r" 
fsuid=117 ouid=0
  operation="file_perm" profile="/usr/lib/dovecot/auth" 
name="/run/dovecot/login/login" comm="auth" requested_mask="w" denied_mask="w" 
fsuid=117 ouid=0
  operation="file_perm" profile="/usr/lib/dovecot/imap" 
name="/run/dovecot/login/imap" comm="imap" requested_mask="r" denied_mask="r" 
fsuid=0 ouid=0
  operation="file_perm" profile="/usr/lib/dovecot/imap" 
name="/run/dovecot/login/imap" comm="imap" requested_mask="w" denied_mask="w" 
fsuid=0 ouid=0
  operation="file_perm" profile="/usr/lib/dovecot/ssl-params" 
name="/run/dovecot/login/ssl-params" comm="ssl-params" requested_mask="w" 
denied_mask="w" fsuid=0 ouid=0
  operation="file_receive" profile="/usr/lib/dovecot/imap" comm="imap" 
family="unix" sock_type="stream" protocol=0 requested_mask="send receive" 
denied_mask="send receive" addr=none peer_addr=none 
peer="/usr/lib/dovecot/imap-login"
  operation="file_receive" profile="/usr/lib/dovecot/imap-login" comm="imap" 
family="unix" sock_type="stream" protocol=0 requested_mask="send receive" 
denied_mask="send receive" addr=none peer_addr=none peer="/usr/lib/dovecot/imap"
  operation="signal" profile="/usr/sbin/dovecot" comm="dovecot" 
requested_mask="send" denied_mask="send" signal=int peer="/usr/lib/dovecot/auth"

  
  To avoid them, I added some stuff to the /etc/apparmor.d/local directory, 
patch attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: dovecot-core 1:2.2.18-2ubuntu2
  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
  CurrentDesktop: XFCE
  Date: Sun Nov  1 19:42:56 2015
  InstallationDate: Installed on 2012-11-11 (1085 days ago)
  InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  SourcePackage: dovecot
  UpgradeStatus: Upgraded to wily on 2015-11-01 (0 days ago)

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

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

[Touch-packages] [Bug 1509507] Re: berkeley pacman crashes xorg

[Sai Hei Yeung]

I had the same problem on Ubuntu 14.04 64-bit.  I've attached the crash
report.  Thanks.

** Attachment added: "xorg_crash.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1509507/+attachment/4516303/+files/xorg_crash.txt

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

Title:
  berkeley pacman crashes xorg

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Related bug:
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1457311

  From the Berkeley Pacman game (written in Python), xorg completely crashes. 
Sometimes it restarts but most of the time the whole system hangs. Berkeley 
Pacman here:
  Info: http://ai.berkeley.edu/search.html
  Source: 
https://s3-us-west-2.amazonaws.com/cs188websitecontent/projects/release/search/v1/001/search.zip

  I found that commenting out line 217 in file "graphicsUtil.py" fixes
  the problem (yet alters the game). Of course there may be bugs in the
  software, but those bugs should never be able to hang a system.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-31-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.17.2-0ubuntu1.5
  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: Fri Oct 23 12:45:05 2015
  DistroCodename: vivid
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:050e]
   NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell Device [1028:050e]
  InstallationDate: Installed on 2015-03-16 (221 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: Dell Inc. Dell System XPS L502X
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-31-generic 
root=UUID=3c903114-3866-4521-b1a9-b6df85728552 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to vivid on 2015-04-30 (176 days ago)
  dmi.bios.date: 09/07/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0NJT03
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd09/07/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvr:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L502X
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid2
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Fri Oct 23 12:40:30 2015
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id6125 
   vendor AUO
  xserver.version: 2:1.17.1-0ubuntu3.1

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

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

[Touch-packages] [Bug 1508260] Re: un-starring a scope jumps several scopes to the right

[Alberto Mardegan]

Fix ready at https://codereview.qt-project.org/#/c/140510/

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

Title:
  un-starring a scope jumps several scopes to the right

Status in qtdeclarative-opensource-src package in Ubuntu:
  In Progress
Status in unity-scopes-shell package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  When I tap the star in a scope to un-favorite it, the view
  spontaneously shifts several scopes to the right.  For example, if I
  flash a completely fresh image (such as arale rc-proposed 143), boot
  the first time, and tap the Today scope's star, the view shifts to the
  News scope instead of the Nearby scope.

  In older images, the view would shift only to the nearest neighbor,
  preferring right-most when one existed.

  Could we revert this back to the older behavior?  Skipping multiple
  scopes seems like a bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1508260/+subscriptions

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

[Sebastien Bacher]

Thank you for your bug report. it seems like the change could apply to
Debian as well, could you report the bug to the Debian BTS as well?

-- 
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 1486878] Re: Sync llvm-toolchain-3.4 1:3.4.2-15 (universe) from Debian unstable (main)

[Sebastien Bacher]

k, synced meanwhile then

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

Title:
  Sync llvm-toolchain-3.4 1:3.4.2-15 (universe) from Debian unstable
  (main)

Status in llvm-toolchain-3.4 package in Ubuntu:
  Fix Released

Bug description:
  Please sync llvm-toolchain-3.4 1:3.4.2-15 (universe) from Debian
  unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* Merge with Debian; remaining changes:
  - Revert to using the static copy of libjsoncpp, since the shared
library lacks sane versioning, and this is only a few thousand
lines of cargo-culted code from a reasonably stagnant upstream.
  - Drop lcov build-dep to avoid pulling it into main, due to its
being fundamentally incompatibe with our newer GCC versions.
  - Build-depend on gcc-multilib on amd64 and i386.
  - Backport upstream patch to not try to handle [SU]MUL_LOHI nodes
on aarch64, needed to build ghc.
  - Unconditionally link lldb with -latomic on all architectures.
  - Don't build python-lldb-3.4 on arm64.
* Disable polly. Not ready for ISL 0.14.
* Merge with Debian; remaining changes:
  - Revert to using the static copy of libjsoncpp, since the shared
library lacks sane versioning, and this is only a few thousand
lines of cargo-culted code from a reasonably stagnant upstream.
  - Drop lcov build-dep to avoid pulling it into main, due to its
being fundamentally incompatibe with our newer GCC versions.
  - Build-depend on gcc-multilib on amd64 and i386.
  - Backport upstream patch to not try to handle [SU]MUL_LOHI nodes
on aarch64, needed to build ghc.
  - Unconditionally link lldb with -latomic on all architectures.
  - Don't build python-lldb-3.4 on arm64.
* Disable polly. Not ready for ISL 0.14.
* Merge with Debian; remaining changes:
  - Revert to using the static copy of libjsoncpp, since the shared
library lacks sane versioning, and this is only a few thousand
lines of cargo-culted code from a reasonably stagnant upstream.
  - Drop lcov build-dep to avoid pulling it into main, due to its
being fundamentally incompatibe with our newer GCC versions.
  - Build-depend on gcc-multilib on amd64 and i386.
  - Backport upstream patch to not try to handle [SU]MUL_LOHI nodes
on aarch64, needed to build ghc.
  - Unconditionally link lldb with -latomic on all architectures.
* Don't build python-lldb-3.4 on arm64.
* Merge with Debian; remaining changes:
  - Revert to using the static copy of libjsoncpp, since the shared
library lacks sane versioning, and this is only a few thousand
lines of cargo-culted code from a reasonably stagnant upstream.
  - Drop lcov build-dep to avoid pulling it into main, due to its
being fundamentally incompatibe with our newer GCC versions.
  - Build-depend on gcc-multilib on amd64 and i386.
  - Backport upstream patch to not try to handle [SU]MUL_LOHI nodes
on aarch64, needed to build ghc.
  - Unconditionally link lldb with -latomic on all architectures.
* Don't build python-lldb-3.4 on arm64.
* debian/rules: fix compiler-rt/libclang-3.4-dev FTBFS on !x86.
* debian/rules: fix compiler-rt/libclang-3.4-dev FTBFS on !x86.
* debian/rules: fix compiler-rt/libclang-3.4-dev FTBFS on !x86.
* debian/rules: fix compiler-rt/libclang-3.4-dev FTBFS on !x86.
* Backport upstream patch to not try to handle [SU]MUL_LOHI nodes on
  aarch64, needed to build ghc.
* Backport upstream patch to not try to handle [SU]MUL_LOHI nodes on
  aarch64, needed to build ghc.
* Unconditionally link lldb with -latomic.
* Rebuild for ocaml-4.01.
* Bring over Ubuntu changes from 3.3:
  - Revert to using the static copy of libjsoncpp, since the shared
library lacks sane versioning, and this is only a few thousand
lines of cargo-culted code from a reasonably stagnant upstream.
  - Drop lcov build-dep to avoid pulling it into main, due to its
being fundamentally incompatibe with our newer GCC versions.
* Don't run the lldb tests on armhf (time out on the buildd).
* Don't run the lldb tests on armhf (time out on the buildd).
* Disable the lldb build for AArch64.
* Build-depend on gcc-multilib on amd64 and i386.
* Disable the lldb build for AArch64.
* Build-depend on gcc-multilib on amd64 and i386.
* Disable the lldb build for AArch64.
* Build-depend on gcc-multilib on amd64 and i386.

  
  I don't know the reason for gcc-multilib, but libjsoncpp is fixed and in main,
  the same for gconv.

  the other failures should be fixed in wily

  Changelog entries since current wily version 1:3.4.2-13ubuntu2:

  llvm-toolchain-3.4 (1:3.4.2-15) unstable; 

[Touch-packages] [Bug 1514908] [NEW] add support for non-root X sessions

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Xenial now has an xserver which supports running it as a normal user
with the help of logind and libpam-systemd. Consider adding support for
it like GDM has.

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

-- 
add support for non-root X sessions
https://bugs.launchpad.net/bugs/1514908
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to lightdm 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 1514880] Re: If a song does not have an album art, quality of displayed note image is very low

[Andrew Hayzen]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

I believe this bug is infact from the thumbnailer which is providing the
fallback image, as you can replicate the same behaviour from the local
music scope (bug 1324142 should also be noted as the refers to providing
custom fallback images).

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

** Changed in: music-app
   Status: New => Invalid

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

Title:
  If a song does not have an album art, quality of displayed note image
  is very low

Status in Ubuntu Music App:
  Invalid
Status in thumbnailer package in Ubuntu:
  New

Bug description:
  I have some songs/albums which don't have its own image to show when
  the song is being played. In that case there's a generic image
  visible. Problem is that image does not look very good. See screenshot
  attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/music-app/+bug/1514880/+subscriptions

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

[Touch-packages] [Bug 1514860] Re: OptionSelector does not work with keyboard

[Bill Filler]

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Zoltan Balogh (bzoltan)

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

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

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

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

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

Title:
  OptionSelector does not work with keyboard

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

Bug description:
  OptionSelector does not fully work with only keyboard. There is no way
  to select a option on OptionSelector using only the keyboard.

  Pressing the arrows does not navigate on the options. And it does not
  have any visual feedback that it contains focus.

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

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

[Touch-packages] [Bug 1514850] Re: There is no visual feedback for Header actions with focus

[Bill Filler]

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Zoltan Balogh (bzoltan)

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

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

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

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

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

Title:
  There is no visual feedback for Header actions  with focus

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

Bug description:
  While implementing  keyboard navigation on address-book I notice that
  the actions in the header (and buttons) are receiving focus but there
  is no visible feedback which action contains the focus.

  Besides that the focus never returns to the page items, as you can see
  on the attached example. Pressing "tab" does not move the focus to
  next item in the chain.

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

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

[Touch-packages] [Bug 1480411] Re: rm -r * fails to delete directories when using overlayfs in a user-namespace

[Serge Hallyn]

@oleg,

yes, but it is not an lxc bug, there's nothing lxc can do about it.
Stéphane un-marked it from lxc to make the lxc bug view more usable so
we can use it rather than ignore it :)

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

Title:
  rm -r * fails to delete directories when using overlayfs in a user-
  namespace

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

Bug description:
  rm -r * fails to delete directories when using overlayfs in a user-
  namespace.

  If overlayfs is mounted as follows,

     mount -n -t overlay overlay -o
  lowerdir=lowerdir,upperdir=upperdir,workdir=workdir mntpt

  and if lowerdir contains lowerdir/foo/bar.txt, then,

     rm -r mntpt/foo

  fails with error message,

     "rm: cannot remove ‘mntpt/foo’: Operation not permitted"

  strace shows,

  unlinkat(AT_FDCWD, "mntpt/foo", AT_REMOVEDIR) = -1 EPERM
  (Operation not permitted)

  OS details: 64-bit ubuntu 14.04.2 with the linux-generic-lts-vivid
  kernel (3.19).

  The bug does not occur on ubuntu 14.04.2 with the default linux-
  generic 3.13 kernel.

  The bug occurs for any vanilla 3.18+ kernel to which the 1-line patch,
  "overlayfs: allow unprivileged mounts" is added.  (The patch is at,
  http://kernel.ubuntu.com/git/ubuntu/ubuntu-
  vivid.git/commit/?id=78ec45495b15d27d4cc6d05cc454e30ec5b587ea)

  The bug occurs regardless of whether the filesystem underlying
  overlayfs is tmpfs or ext4.

  The bug also occurs when running ubuntu 15.04 (ubuntu vivid) in a
  virtual machine (qemu-system-x86_64).  The host is ubuntu 14.04.2 with
  the default 3.13 kernel.

  A script which reproduces the bug is attached and is also available at
  http://paste.ubuntu.com/11974137/

  Hardware: intel core2 duo processor in a macbook-4.1

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

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

[Touch-packages] [Bug 1486878] Re: Sync llvm-toolchain-3.4 1:3.4.2-15 (universe) from Debian unstable (main)

[Sebastien Bacher]

This bug was fixed in the package llvm-toolchain-3.4 - 1:3.4.2-16
Sponsored for LocutusOfBorg (costamagnagianfranco)

---
llvm-toolchain-3.4 (1:3.4.2-16) unstable; urgency=medium

  * Silent the Bindings/Ocaml/bitwriter.ml test to unbreak the build
on i386/amd64
- Fix compilation with OCaml 4.02 (Stéphane Glondu) (Closes: #789403)

 -- Sylvestre Ledru   Thu, 29 Oct 2015 09:55:59
+0100

llvm-toolchain-3.4 (1:3.4.2-15) unstable; urgency=medium

  * Team upload
  * d/rules: fix gcc-5 detection, since gcc-5.2
doesn't provide a g++-5.2 binary (but it is called
g++-5)
(copying the patch from llvm-3.7)

 -- Gianfranco Costamagna   Mon, 10 Aug 2015
12:54:45 +0200

llvm-toolchain-3.4 (1:3.4.2-14) unstable; urgency=medium

  * d/patches/isl-0.13-compat.diff, ensure compatibility with libisl13
(Closes: #783686)
We are planning to remove llvm 3.4 soon but this upload will help
the libisl transition.

 -- Gianfranco Costamagna   Tue, 05 May
2015 12:39:15 +0200

** Changed in: llvm-toolchain-3.4 (Ubuntu)
   Status: New => Fix Released

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

Title:
  Sync llvm-toolchain-3.4 1:3.4.2-15 (universe) from Debian unstable
  (main)

Status in llvm-toolchain-3.4 package in Ubuntu:
  Fix Released

Bug description:
  Please sync llvm-toolchain-3.4 1:3.4.2-15 (universe) from Debian
  unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* Merge with Debian; remaining changes:
  - Revert to using the static copy of libjsoncpp, since the shared
library lacks sane versioning, and this is only a few thousand
lines of cargo-culted code from a reasonably stagnant upstream.
  - Drop lcov build-dep to avoid pulling it into main, due to its
being fundamentally incompatibe with our newer GCC versions.
  - Build-depend on gcc-multilib on amd64 and i386.
  - Backport upstream patch to not try to handle [SU]MUL_LOHI nodes
on aarch64, needed to build ghc.
  - Unconditionally link lldb with -latomic on all architectures.
  - Don't build python-lldb-3.4 on arm64.
* Disable polly. Not ready for ISL 0.14.
* Merge with Debian; remaining changes:
  - Revert to using the static copy of libjsoncpp, since the shared
library lacks sane versioning, and this is only a few thousand
lines of cargo-culted code from a reasonably stagnant upstream.
  - Drop lcov build-dep to avoid pulling it into main, due to its
being fundamentally incompatibe with our newer GCC versions.
  - Build-depend on gcc-multilib on amd64 and i386.
  - Backport upstream patch to not try to handle [SU]MUL_LOHI nodes
on aarch64, needed to build ghc.
  - Unconditionally link lldb with -latomic on all architectures.
  - Don't build python-lldb-3.4 on arm64.
* Disable polly. Not ready for ISL 0.14.
* Merge with Debian; remaining changes:
  - Revert to using the static copy of libjsoncpp, since the shared
library lacks sane versioning, and this is only a few thousand
lines of cargo-culted code from a reasonably stagnant upstream.
  - Drop lcov build-dep to avoid pulling it into main, due to its
being fundamentally incompatibe with our newer GCC versions.
  - Build-depend on gcc-multilib on amd64 and i386.
  - Backport upstream patch to not try to handle [SU]MUL_LOHI nodes
on aarch64, needed to build ghc.
  - Unconditionally link lldb with -latomic on all architectures.
* Don't build python-lldb-3.4 on arm64.
* Merge with Debian; remaining changes:
  - Revert to using the static copy of libjsoncpp, since the shared
library lacks sane versioning, and this is only a few thousand
lines of cargo-culted code from a reasonably stagnant upstream.
  - Drop lcov build-dep to avoid pulling it into main, due to its
being fundamentally incompatibe with our newer GCC versions.
  - Build-depend on gcc-multilib on amd64 and i386.
  - Backport upstream patch to not try to handle [SU]MUL_LOHI nodes
on aarch64, needed to build ghc.
  - Unconditionally link lldb with -latomic on all architectures.
* Don't build python-lldb-3.4 on arm64.
* debian/rules: fix compiler-rt/libclang-3.4-dev FTBFS on !x86.
* debian/rules: fix compiler-rt/libclang-3.4-dev FTBFS on !x86.
* debian/rules: fix compiler-rt/libclang-3.4-dev FTBFS on !x86.
* debian/rules: fix compiler-rt/libclang-3.4-dev FTBFS on !x86.
* Backport upstream patch to not try to handle [SU]MUL_LOHI nodes on
  aarch64, needed to build ghc.
* Backport upstream patch to not try to handle [SU]MUL_LOHI nodes on
  aarch64, needed to build ghc.
* 

[Touch-packages] [Bug 1513909] Re: unity8 crash on unplug of monitor

[Gerry Boland]

http://pastebin.ubuntu.com/13216662/ is useful log. It indicates that 2
displays are detected by mir, and are not being cloned. However it
appears that there is only a single DisplayBuffer available
(Screen::setMirDisplayBuffer should be called for each DisplayBuffer,
but only called once)

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

Title:
  unity8 crash on unplug of monitor

Status in canonical-pocket-desktop:
  New
Status in mir package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Stability of hotplug is much better -  so this is not a duplicate of bug 
1488863
  Maybe every 1/4 unplug event will see unity8 crashstrangely, didn't 
capture a crash log until now.

  This configuration is 
  latest PD image + silo 18 (with point release fixes for Mir0.17)
  also libertine/puritine installed
  xmir is from libertine devel ppa

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1513909/+subscriptions

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

[Touch-packages] [Bug 1486878] Re: Sync llvm-toolchain-3.4 1:3.4.2-15 (universe) from Debian unstable (main)

[Sebastien Bacher]

is that still needed for xenial? you wrote before that it's not going to
be needed for wily+1

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

Title:
  Sync llvm-toolchain-3.4 1:3.4.2-15 (universe) from Debian unstable
  (main)

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

Bug description:
  Please sync llvm-toolchain-3.4 1:3.4.2-15 (universe) from Debian
  unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* Merge with Debian; remaining changes:
  - Revert to using the static copy of libjsoncpp, since the shared
library lacks sane versioning, and this is only a few thousand
lines of cargo-culted code from a reasonably stagnant upstream.
  - Drop lcov build-dep to avoid pulling it into main, due to its
being fundamentally incompatibe with our newer GCC versions.
  - Build-depend on gcc-multilib on amd64 and i386.
  - Backport upstream patch to not try to handle [SU]MUL_LOHI nodes
on aarch64, needed to build ghc.
  - Unconditionally link lldb with -latomic on all architectures.
  - Don't build python-lldb-3.4 on arm64.
* Disable polly. Not ready for ISL 0.14.
* Merge with Debian; remaining changes:
  - Revert to using the static copy of libjsoncpp, since the shared
library lacks sane versioning, and this is only a few thousand
lines of cargo-culted code from a reasonably stagnant upstream.
  - Drop lcov build-dep to avoid pulling it into main, due to its
being fundamentally incompatibe with our newer GCC versions.
  - Build-depend on gcc-multilib on amd64 and i386.
  - Backport upstream patch to not try to handle [SU]MUL_LOHI nodes
on aarch64, needed to build ghc.
  - Unconditionally link lldb with -latomic on all architectures.
  - Don't build python-lldb-3.4 on arm64.
* Disable polly. Not ready for ISL 0.14.
* Merge with Debian; remaining changes:
  - Revert to using the static copy of libjsoncpp, since the shared
library lacks sane versioning, and this is only a few thousand
lines of cargo-culted code from a reasonably stagnant upstream.
  - Drop lcov build-dep to avoid pulling it into main, due to its
being fundamentally incompatibe with our newer GCC versions.
  - Build-depend on gcc-multilib on amd64 and i386.
  - Backport upstream patch to not try to handle [SU]MUL_LOHI nodes
on aarch64, needed to build ghc.
  - Unconditionally link lldb with -latomic on all architectures.
* Don't build python-lldb-3.4 on arm64.
* Merge with Debian; remaining changes:
  - Revert to using the static copy of libjsoncpp, since the shared
library lacks sane versioning, and this is only a few thousand
lines of cargo-culted code from a reasonably stagnant upstream.
  - Drop lcov build-dep to avoid pulling it into main, due to its
being fundamentally incompatibe with our newer GCC versions.
  - Build-depend on gcc-multilib on amd64 and i386.
  - Backport upstream patch to not try to handle [SU]MUL_LOHI nodes
on aarch64, needed to build ghc.
  - Unconditionally link lldb with -latomic on all architectures.
* Don't build python-lldb-3.4 on arm64.
* debian/rules: fix compiler-rt/libclang-3.4-dev FTBFS on !x86.
* debian/rules: fix compiler-rt/libclang-3.4-dev FTBFS on !x86.
* debian/rules: fix compiler-rt/libclang-3.4-dev FTBFS on !x86.
* debian/rules: fix compiler-rt/libclang-3.4-dev FTBFS on !x86.
* Backport upstream patch to not try to handle [SU]MUL_LOHI nodes on
  aarch64, needed to build ghc.
* Backport upstream patch to not try to handle [SU]MUL_LOHI nodes on
  aarch64, needed to build ghc.
* Unconditionally link lldb with -latomic.
* Rebuild for ocaml-4.01.
* Bring over Ubuntu changes from 3.3:
  - Revert to using the static copy of libjsoncpp, since the shared
library lacks sane versioning, and this is only a few thousand
lines of cargo-culted code from a reasonably stagnant upstream.
  - Drop lcov build-dep to avoid pulling it into main, due to its
being fundamentally incompatibe with our newer GCC versions.
* Don't run the lldb tests on armhf (time out on the buildd).
* Don't run the lldb tests on armhf (time out on the buildd).
* Disable the lldb build for AArch64.
* Build-depend on gcc-multilib on amd64 and i386.
* Disable the lldb build for AArch64.
* Build-depend on gcc-multilib on amd64 and i386.
* Disable the lldb build for AArch64.
* Build-depend on gcc-multilib on amd64 and i386.

  
  I don't know the reason for gcc-multilib, but libjsoncpp is fixed and in main,
  the same for gconv.

  the other failures should be fixed in wily

  Changelog entries since current wily version 

[Touch-packages] [Bug 1514856] Re: Receiving "Ambiguous shortcut" even when action is not in use

[Bill Filler]

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

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Zoltan Balogh (bzoltan)

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

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

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

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

Title:
  Receiving "Ambiguous shortcut" even when action is not in use

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

Bug description:
  I am trying to use "Esc" shortcut for several actions on my project
  (most of than for the back button action on Page header), but even
  when only one back button is visible/active/in use I still receiving
  the message "QML Action: Ambiguous shortcut: Esc".

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

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

[Touch-packages] [Bug 1509507] Re: berkeley pacman crashes xorg

[Sai Hei Yeung]

I had the same problem on Ubuntu 14.04 64-bit.  I've attached the crash
report.  Thanks.

** Attachment added: "xorg_crash.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1509507/+attachment/4516304/+files/xorg_crash.txt

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

Title:
  berkeley pacman crashes xorg

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Related bug:
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1457311

  From the Berkeley Pacman game (written in Python), xorg completely crashes. 
Sometimes it restarts but most of the time the whole system hangs. Berkeley 
Pacman here:
  Info: http://ai.berkeley.edu/search.html
  Source: 
https://s3-us-west-2.amazonaws.com/cs188websitecontent/projects/release/search/v1/001/search.zip

  I found that commenting out line 217 in file "graphicsUtil.py" fixes
  the problem (yet alters the game). Of course there may be bugs in the
  software, but those bugs should never be able to hang a system.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-31-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.17.2-0ubuntu1.5
  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: Fri Oct 23 12:45:05 2015
  DistroCodename: vivid
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:050e]
   NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell Device [1028:050e]
  InstallationDate: Installed on 2015-03-16 (221 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: Dell Inc. Dell System XPS L502X
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-31-generic 
root=UUID=3c903114-3866-4521-b1a9-b6df85728552 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to vivid on 2015-04-30 (176 days ago)
  dmi.bios.date: 09/07/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0NJT03
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd09/07/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvr:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L502X
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid2
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Fri Oct 23 12:40:30 2015
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id6125 
   vendor AUO
  xserver.version: 2:1.17.1-0ubuntu3.1

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

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

[Touch-packages] [Bug 1513909] Re: unity8 crash on unplug of monitor

[Gerry Boland]

http://bazaar.launchpad.net/~mir-
team/qtmir/trunk/view/head:/src/platforms/mirserver/screencontroller.cpp#L157
is the relevant line of code. This triggers after compositor start, to
match mir DisplayBuffers with Qt Screens. I've designed it under the
assumption that each Mir Display will always have a DisplayBuffer on
compositor start.

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

Title:
  unity8 crash on unplug of monitor

Status in canonical-pocket-desktop:
  New
Status in mir package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Stability of hotplug is much better -  so this is not a duplicate of bug 
1488863
  Maybe every 1/4 unplug event will see unity8 crashstrangely, didn't 
capture a crash log until now.

  This configuration is 
  latest PD image + silo 18 (with point release fixes for Mir0.17)
  also libertine/puritine installed
  xmir is from libertine devel ppa

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1513909/+subscriptions

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

[Touch-packages] [Bug 1514519] Re: Font in Terminal is incorrectly massive since recent update

[Gerry Boland]

oops wrong bug, please ignore above

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

Title:
  Font in Terminal is incorrectly massive since recent update

Status in Canonical System Image:
  Confirmed
Status in logviewer:
  New
Status in Ubuntu Terminal App:
  New
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Last know good image: 166
  Changes on 167: 
http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-proposed/167.commitlog
  Landing request for Unity8/Mir: 
https://requests.ci-train.ubuntu.com/#/ticket/564

  After updating my Nexus 4 and Krillin over the weekend I notice the
  terminal now has really huge text. Even dialling down the font size in
  the app to 8pt results in huge unusable text.

  Before:- 
http://people.canonical.com/~alan/screenshots/device-2015-11-09-165137.png
  After:- 
http://people.canonical.com/~alan/screenshots/device-2015-11-09-165130.png

  With the same font size setting on both.

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

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

[Touch-packages] [Bug 1337873] Re: Precise, Trusty, Utopic - ifupdown initialization problems caused by race condition

[Martin Pitt]

Sponsored the patch for xenial. Let's give this some maturing there
first.

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

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

Title:
  Precise, Trusty, Utopic - ifupdown initialization problems caused by
  race condition

Status in ifupdown package in Ubuntu:
  Fix Committed
Status in ifupdown source package in Precise:
  Confirmed
Status in ifupdown source package in Trusty:
  Confirmed
Status in ifupdown source package in Vivid:
  Confirmed
Status in ifupdown package in Debian:
  New

Bug description:
  [Impact]

   * Lack of proper synchronization in ifupdown causes a race condition
  resulting in occasional incorrect network interface initialization
  (e.g. in bonding case - wrong bonding settings, network unavailable
  because slave<->master interfaces initialization order was wrong

   * This is very annoying in case of large deployments (e.g. when
  bringing up 1000 machines it is almost guaranteed that at least a few
  of them will end up with network down).

   * It has been fixed by introducing hierarchical and per-interface
  locking mechanism ensuring the right order (along with the correct
  order in the /e/n/interfaces file) of initialization

  [Test Case]

   1. Create a VM with bonding configured with at least 2 slave interfaces.
   2. Reboot.
   3. If all interfaces are up - go to 2.

  [Regression Potential]

   * This change has been introduced upstream in Debian.
   * It does not require any config changes to existing installations.

  [Other Info]

  Original bug description:

  * please consider my bonding examples are using eth1 and eth2 as slave
   interfaces.

  ifupdown some race conditions explained bellow. ifenslave does not
  behave well with sysv networking and upstart network-interface scripts
  running together.

  
  case 1)
  (a) ifup eth0 (b) ifup -a for eth0
  -
  1-1. Lock ifstate.lock file.
    1-1. Wait for locking ifstate.lock
    file.
  1-2. Read ifstate file to check
   the target NIC.
  1-3. close(=release) ifstate.lock
   file.
  1-4. Judge that the target NIC
   isn't processed.
    1-2. Read ifstate file to check
     the target NIC.
    1-3. close(=release) ifstate.lock
     file.
    1-4. Judge that the target NIC
     isn't processed.
  2. Lock and update ifstate file.
     Release the lock.
    2. Lock and update ifstate file.
   Release the lock.
  !!!

  to be explained

  !!!
  case 2)
  (a) ifenslave of eth0  (b) ifenslave of eth0
  --
  3. Execute ifenslave of eth0.  3. Execute ifenslave of eth0.
  4. Link down the target NIC.
  5. Write NIC id to
     /sys/class/net/bond0/bonding
     /slaves then NIC gets up
    4. Link down the target NIC.
    5. Fails to write NIC id to
   /sys/class/net/bond0/bonding/
   slaves it is already written.
  !!!

  #

   My setup:

  root@provisioned:~# cat /etc/modprobe.d/bonding.conf
  alias bond0 bonding options bonding mode=1 arp_interval=2000

  Both, /etc/init.d/networking and upstart network-interface begin
  enabled.

   Beginning:

  root@provisioned:~# cat /etc/network/interfaces
  # /etc/network/interfaces

  auto lo
  iface lo inet loopback

  auto eth0
  iface eth0 inet dhcp

  I'm able to boot with both scripts (networking and network-interface
  enabled) with no problem. I can also boot with only "networking"
  script enabled:

  ---
  root@provisioned:~# initctl list | grep network
  network-interface stop/waiting
  networking start/running
  ---

  OR only the script "network-interface" enabled:

  ---
  root@provisioned:~# initctl list | grep network
  network-interface (eth2) start/running
  network-interface (lo) start/running
  network-interface (eth0) start/running
  network-interface (eth1) start/running
  ---

   Enabling bonding:

  Following ifenslave configuration example (/usr/share/doc/ifenslave/
  examples/two_hotplug_ethernet), my /etc/network/interfaces has to
  look like this:

  ---
  auto eth1
  iface eth1 inet manual
  bond-master bond0

  auto eth2
  iface eth2 inet manual
  bond-master bond0

  auto bond0
  iface bond0 inet static
  bond-mode 1
  

[Touch-packages] [Bug 1013597] Re: No default route for stateful DHCPv6

[Thiago Martins]

So, nobody will look into this anymore (apparently), are we moving to
systemd's networkd (16.04) to "fix" this? I'm so tired of ifupdown...
:-P

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

Title:
  No default route for stateful DHCPv6

Status in ifupdown package in Ubuntu:
  Fix Released
Status in ifupdown source package in Precise:
  Triaged

Bug description:
  The default route cannot be provided via DHCPv6, it must be obtained
  from router advertisements. However, when using the dhcp method for
  inet6 in /etc/network/interfaces (e.g. "iface eth0 inet6 dhcp"), ifup
  will set net.ipv6.conf..accept_ra=0, resulting in no default
  route for IPv6. Instead, it should explicitly set accept_ra=1.

  A workaround is to set it in a post-up script. However, Linux
  apparently only sends router solicitations when the interface is
  brought up, so if unsolicited RA:s are infrequent the host will be
  without a default route until the next RA.

  Another problem is that when bringing the interface down on dual-stack
  hosts, there will be a long timeout. This is because bringing down
  IPv4 also brings the interface link down, and afterwards dhclient
  cannot release the DHCPv6 lease due to the link being down ("RTNETLINK
  answers: Cannot assign requested address"). The workaround is to bring
  the link back up before bringing IPv6 down.

  So the workarounds (which obviously should not be needed) for a dual-
  stack dhcp client look like this:

  iface eth0 inet dhcp
  iface eth0 inet6 dhcp
  up sysctl net.ipv6.conf.$IFACE.accept_ra=1
  pre-down ip link set dev $IFACE up

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

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

[Touch-packages] [Bug 1337873] Re: Precise, Trusty, Utopic - ifupdown initialization problems caused by race condition

[Sebastien Bacher]

(unsubscribing sponsors for now then, please subscribe them back after
getting some feedback from the xenial update)

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

Title:
  Precise, Trusty, Utopic - ifupdown initialization problems caused by
  race condition

Status in ifupdown package in Ubuntu:
  Fix Committed
Status in ifupdown source package in Precise:
  Confirmed
Status in ifupdown source package in Trusty:
  Confirmed
Status in ifupdown source package in Vivid:
  Confirmed
Status in ifupdown package in Debian:
  New

Bug description:
  [Impact]

   * Lack of proper synchronization in ifupdown causes a race condition
  resulting in occasional incorrect network interface initialization
  (e.g. in bonding case - wrong bonding settings, network unavailable
  because slave<->master interfaces initialization order was wrong

   * This is very annoying in case of large deployments (e.g. when
  bringing up 1000 machines it is almost guaranteed that at least a few
  of them will end up with network down).

   * It has been fixed by introducing hierarchical and per-interface
  locking mechanism ensuring the right order (along with the correct
  order in the /e/n/interfaces file) of initialization

  [Test Case]

   1. Create a VM with bonding configured with at least 2 slave interfaces.
   2. Reboot.
   3. If all interfaces are up - go to 2.

  [Regression Potential]

   * This change has been introduced upstream in Debian.
   * It does not require any config changes to existing installations.

  [Other Info]

  Original bug description:

  * please consider my bonding examples are using eth1 and eth2 as slave
   interfaces.

  ifupdown some race conditions explained bellow. ifenslave does not
  behave well with sysv networking and upstart network-interface scripts
  running together.

  
  case 1)
  (a) ifup eth0 (b) ifup -a for eth0
  -
  1-1. Lock ifstate.lock file.
    1-1. Wait for locking ifstate.lock
    file.
  1-2. Read ifstate file to check
   the target NIC.
  1-3. close(=release) ifstate.lock
   file.
  1-4. Judge that the target NIC
   isn't processed.
    1-2. Read ifstate file to check
     the target NIC.
    1-3. close(=release) ifstate.lock
     file.
    1-4. Judge that the target NIC
     isn't processed.
  2. Lock and update ifstate file.
     Release the lock.
    2. Lock and update ifstate file.
   Release the lock.
  !!!

  to be explained

  !!!
  case 2)
  (a) ifenslave of eth0  (b) ifenslave of eth0
  --
  3. Execute ifenslave of eth0.  3. Execute ifenslave of eth0.
  4. Link down the target NIC.
  5. Write NIC id to
     /sys/class/net/bond0/bonding
     /slaves then NIC gets up
    4. Link down the target NIC.
    5. Fails to write NIC id to
   /sys/class/net/bond0/bonding/
   slaves it is already written.
  !!!

  #

   My setup:

  root@provisioned:~# cat /etc/modprobe.d/bonding.conf
  alias bond0 bonding options bonding mode=1 arp_interval=2000

  Both, /etc/init.d/networking and upstart network-interface begin
  enabled.

   Beginning:

  root@provisioned:~# cat /etc/network/interfaces
  # /etc/network/interfaces

  auto lo
  iface lo inet loopback

  auto eth0
  iface eth0 inet dhcp

  I'm able to boot with both scripts (networking and network-interface
  enabled) with no problem. I can also boot with only "networking"
  script enabled:

  ---
  root@provisioned:~# initctl list | grep network
  network-interface stop/waiting
  networking start/running
  ---

  OR only the script "network-interface" enabled:

  ---
  root@provisioned:~# initctl list | grep network
  network-interface (eth2) start/running
  network-interface (lo) start/running
  network-interface (eth0) start/running
  network-interface (eth1) start/running
  ---

   Enabling bonding:

  Following ifenslave configuration example (/usr/share/doc/ifenslave/
  examples/two_hotplug_ethernet), my /etc/network/interfaces has to
  look like this:

  ---
  auto eth1
  iface eth1 inet manual
  bond-master bond0

  auto eth2
  iface eth2 inet manual
  bond-master bond0

  auto bond0
  iface bond0 inet static
  bond-mode 1
  bond-miimon 100
  bond-primary eth1 eth2
  

[Touch-packages] [Bug 1508767] Re: IBM POWER8 unhandled signal 11 / SEGV

[Chris J Arges]

** Tags added: kernel-key

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

Title:
  IBM POWER8 unhandled signal 11 / SEGV

Status in Ubuntu Cloud Archive:
  New
Status in apparmor package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in linux-meta-lts-vivid package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  We have a few IBM POWER8 servers which we're currently using as
  OpenStack nova compute nodes. It seems we're regularly running into
  issues where processes are segfaulting:

  | hloeung@gligar:~$ zgrep -E '(SEGV)|(unhandled signal 11)' 
/var/log/syslog.5.gz
  | Oct 16 23:31:38 gligar kernel: [88351.465559] neutron-openvsw[29733]: 
unhandled signal 11 at 88f90100 nip 100ba0d8 lr 
101ad860 code 30001
  | Oct 16 23:31:38 gligar kernel: [88351.566909] init: 
neutron-plugin-openvswitch-agent main process (29733) killed by SEGV signal
  | Oct 16 23:31:38 gligar kernel: [88351.746611] apport[29500]: unhandled 
signal 11 at 8850e467250040a8 nip 10201f80 lr 10202984 code 
30001
  | Oct 16 23:31:39 gligar kernel: [88352.245829] neutron-rootwra[29749]: 
unhandled signal 11 at 0809c4b61000 nip 1014ae4c lr 
1014b544 code 30001
  | Oct 16 23:31:50 gligar kernel: [88364.040340] neutron-rootwra[30060]: 
unhandled signal 11 at 08a305c12b00 nip 100b74d0 lr 
100b73e4 code 30001
  | Oct 16 23:31:51 gligar kernel: [88364.174218] neutron-rootwra[30065]: 
unhandled signal 11 at 088eb28e2f004078 nip 100b5974 lr 
100aa794 code 30001
  | Oct 16 23:31:52 gligar kernel: [88365.195380] neutron-rootwra[30098]: 
unhandled signal 11 at 88c939e32208 nip 100c8b28 lr 
10060384 code 30001
  | Oct 16 23:31:52 gligar kernel: [88365.362374] neutron-rootwra[30106]: 
unhandled signal 11 at 882c58ad2800f04f nip 3fffaef81220 lr 
3fffaef811a0 code 30001
  | Oct 16 23:32:27 gligar kernel: [88400.966976] neutron-rootwra[30341]: 
unhandled signal 11 at 88d1fbe922001008 nip 100c8b28 lr 
10060384 code 30001
  | Oct 16 23:32:47 gligar kernel: [88420.953053] neutron-rootwra[30412]: 
unhandled signal 11 at 11b6629054008000 nip 3fff9a864ac4 lr 
3fff9a84c42c code 30001
  | Oct 16 23:34:49 gligar kernel: [88542.778503] neutron-rootwra[30977]: 
unhandled signal 11 at 88540f0010a8 nip 100aa768 lr 
100b74e8 code 30001
  | Oct 16 23:35:23 gligar kernel: [88576.700721] neutron-openvsw[29739]: 
unhandled signal 11 at 08bfcbf721a8 nip 100ab390 lr 
100b7c38 code 30001
  | Oct 16 23:35:23 gligar kernel: [88576.804961] init: 
neutron-plugin-openvswitch-agent main process (29739) killed by SEGV signal
  | Oct 16 23:36:01 gligar kernel: [88614.995497] nova-compute[31662]: 
unhandled signal 11 at 8846c1c81f004008 nip 1014c2f0 lr 
10151080 code 30001
  | Oct 16 23:36:02 gligar kernel: [88615.110735] nova-compute[4331]: unhandled 
signal 11 at 88befae9220010a8 nip 100b5c8c lr 1014c734 code 
30001
  | Oct 16 23:36:02 gligar kernel: [88615.219436] init: nova-compute main 
process (4331) killed by SEGV signal
  | Oct 17 03:59:56 gligar kernel: [104449.890256] landscape-packa[63283]: 
unhandled signal 11 at 02f8 nip 101abeac lr 
100a8738 code 30001
  | Oct 17 04:05:00 gligar kernel: [104753.718195] sudo[63915]: unhandled 
signal 11 at 08e06105d1dcfff8 nip 3fffb15cf7e4 lr 3fffb15cfa00 code 
30001

  
  | hloeung@floette:~$ zgrep -E '(SEGV)|(unhandled signal 11)' 
/var/log/syslog.7.gz
  | Oct 14 16:55:30 floette kernel: [149326.697938] rsync[9915]: unhandled 
signal 11 at 37cb nip 3fffa242d054 lr 3fffa2426560 code 
30001
  | Oct 14 21:05:57 floette kernel: [164353.333697] apparmor_parser[102284]: 
unhandled signal 11 at 08680f00 nip 1004bbf8 lr 
10028de4 code 30001
  | Oct 14 22:21:24 floette kernel: [168880.481778] neutron-rootwra[153488]: 
unhandled signal 11 at 8860fbe21fa8 nip 100aa768 lr 
100b74e8 code 30001
  | Oct 14 22:21:26 floette kernel: [168882.078608] neutron-openvsw[4546]: 
unhandled signal 11 at 8822cbf03d08 nip 100aa764 lr 
100e6900 code 30001
  | Oct 14 22:21:37 floette kernel: [168893.597834] init: 
neutron-plugin-openvswitch-agent main process (4546) killed by SEGV signal
  | Oct 14 22:21:39 floette kernel: [168894.949777] nova-rootwrap[153708]: 
unhandled signal 11 at 88d495c93ca8 nip 100a57d4 lr 
100ab42c code 30001
  | Oct 14 22:21:43 floette kernel: [168898.973700] neutron-rootwra[153847]: 
unhandled signal 11 at 08c90df31820 nip 101ac260 lr 
101ad92c code 30001
  | Oct 14 22:21:44 floette kernel: [168900.785421] neutron-rootwra[153850]: 
unhandled signal 11 at 88d87b783fa8 nip 101abf40 lr 

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

[Sebastien Bacher]

sponsored to precise/trusty/vivid (though i'm unsure vivid is useful
since it's not the current stable)

-- 
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 1513756] Re: Mediascanner looping constantly causing battery exhaustion

[Alejandro J. Cura]

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

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

Title:
  Mediascanner looping constantly causing battery exhaustion

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

Bug description:
  Woke up to find my krillin retail device on OTA-7 battery almost dead.
  I unplugged it when I went to bed last night, so it discharged
  completely in ~10 hours.

  http://people.canonical.com/~alan/screenshots/device-2015-11-06-083113.png

  ssh'ed in and found mediascanner consuming some CPU time (I haven't
  changed the media on the device for some time). Checking the logs
  (attached) it looks like this has been happening for days. Due to UOS
  and other things I've not used this phone much over the past week, so
  it's juts been sat there dying until I plug it in.

  mediascanner log attached. I don't think this is bug 1508142 because I
  checked and I have no webm files on the device, and it doesn't seem to
  be scanning, just starting and dying.

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

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

[Touch-packages] [Bug 1514908] Re: add support for non-root X sessions

[Timo Aaltonen]

** Package changed: nautilus (Ubuntu) => lightdm (Ubuntu)

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

Title:
  add support for non-root X sessions

Status in lightdm package in Ubuntu:
  New

Bug description:
  Xenial now has an xserver which supports running it as a normal user
  with the help of logind and libpam-systemd. Consider adding support
  for it like GDM has.

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

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

[Touch-packages] [Bug 1505241] Re: Phone does not suspend

[Simon Fels]

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

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

Title:
  Phone does not suspend

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

Bug description:
  I am seeing both the MX4 on proposed and the E4.5 on stable exhibit similar 
behavior
  According to the logs they are not able to suspend due to active wakeup 
sources.
  (I am running a BT test kernel on the MX4 3.10.35+)

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

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

Re: [Touch-packages] [Bug 1513928] Re: AMD Catalyst (amdcccle) - 4.2 Linux Kernel bug

[Jaime Peña Álvarez]

jaimepena7@jaimepena7-Satellite-P55-B:~$ sudo dmidecode -s bios-version &&
sudo dmidecode -s bios-release-date
[sudo] password for jaimepena7:
1.50
12/09/2014


Saludos y bendiciones,

Jaime.

---


*El Señor cumplirá en mí su propósito.Tu gran amor, Señor, perdura para
siempre;¡no abandones la obra de tus manos!*

*Salmo 138:8 (Nueva Versión Internacional NVI
)*


2015-11-10 6:03 GMT-03:00 Christopher M. Penalver <
christopher.m.penal...@gmail.com>:

> Jaime Peña Álvarez, please provide the output of the following terminal
> command:
> sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1513928
>
> Title:
>   AMD Catalyst (amdcccle) - 4.2 Linux Kernel bug
>
> Status in xorg package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Xubuntu 15.10 does not detect a AMD card, hence AMD Catalyst
>   (amdcccle) does not work. First, it is necessary to initialize it,
>   first rebooting the system after installation of fglrx-updates,
>   copying the /usr/lib/fglrx folder to /usr/lib64/fglrx, and using
>   "aticonfig --initial". In spite of that, these steps are not enough
>   due to the bug, that it is temporally solved by installing wily-
>   proposed files, as described in :
>
>   http://www.phoronix.com/scan.php?page=news_item=Ubuntu-15.10-fglrx-
>   Fix
>
>   A Fix For AMD Catalyst On Ubuntu 15.10 Is Coming
>   Written by Michael Larabel in AMD on 27 October 2015 at 05:36 PM EDT. 25
> Comments
>   While Ubuntu 15.10 launched last week, the AMD Catalyst driver hasn't
> been working but that's in the process of changing.
>
>   While there's been patches for letting AMD Catalyst work on Ubuntu up
>   through the Linux 4.2 kernel, the binary driver has ended up failing
>   to work on Ubuntu's 4.2 kernel as found in Ubuntu 15.10. So even right
>   now with a sudo apt-get install fglrx on Ubuntu 15.10, the driver will
>   not work.
>
>   As reported in the earlier article, users have found the workaround to
>   be just downgrading to the Linux 4.1 kernel where the patched Catalyst
>   15.9 driver then plays happy. However, this new workaround that's in
>   the process of landing in the Wily archive, fixes the issue by
>   building the fglrx driver's shim against GCC 4.9 rather than GCC 5.
>
>   Alberto Milone pushed a fixed driver into wily-proposed. "Add a
>   dependency on gcc-4.9, and force fglrx to use gcc-4.9. This prevents
>   fglrx from dying on initialisation. Credit for finding out the actual
>   problem and for suggesting a workaround goes to David Burrows. Note:
>   this is only a workaround, and it will be dropped as soon as a proper
>   fix from upstream is available."
>
>   This lengthy bug report details the struggle people have faced in
>   getting AMD's proprietary driver working on this newest Ubuntu Linux
>   release. If you want to get your Ubuntu 15.10 box running with AMD's
>   blob prior to the new update landing in the official Ubuntu package
>   archive, you can follow the steps for using the driver from wily-
>   proposed via this bug comment.
>
>
>   and
>
>
>
> https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1493888/comments/123
>
>   Comment 123 for bug 1493888
>   Đorđe (djole94hns) wrote on 2015-10-27:   #123
>   @Mikael Thurberg
>
>   -In Software & Updates, tick "proposed"
>   -Create the file /etc/apt/preferences.d/proposed-updates with this
> content:
>
>   Package: *
>   Pin: release a=wily-proposed
>   Pin-Priority: 400
>
>   Just so you don't install proposed updates automatically, but
>   selectively (so you can choose which to install)
>
>   -sudo apt-get update
>   -sudo apt-get install fglrx-updates/wily-proposed
> fglrx-updates-core/wily-proposed fglrx-amdcccle-updates/wily-proposed
>   -reboot and you're done!
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 15.10
>   Package: xorg 1:7.7+7ubuntu4
>   ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
>   Uname: Linux 4.2.0-17-generic x86_64
>   NonfreeKernelModules: fglrx
>   ApportVersion: 2.19.1-0ubuntu4
>   Architecture: amd64
>   CompizPlugins: No value set for
> `/apps/compiz-1/general/screen0/options/active_plugins'
>   CompositorRunning: None
>   CurrentDesktop: XFCE
>   Date: Fri Nov  6 15:29:55 2015
>   DistUpgraded: Fresh install
>   DistroCodename: wily
>   DistroVariant: ubuntu
>   DkmsStatus:
>fglrx-updates-core, 15.201, 4.2.0-16-generic, x86_64: installed
>fglrx-updates-core, 15.201, 4.2.0-17-generic, x86_64: installed
>   ExtraDebuggingInterest: Yes, including running git bisection searches
>   GraphicsCard:
>Intel Corporation 4th Gen Core Processor Integrated Graphics Controller
> [8086:0416] (rev 06) (prog-if 00 [VGA controller])
>  Subsystem: Toshiba America Info Systems Device [1179:f945]
>  Subsystem: Toshiba America Info Systems Device 

[Touch-packages] [Bug 1513909] Re: unity8 crash on unplug of monitor

[Alan Griffiths]

There's a whole host of Mir bugs in this area due to races detecting and
responding to display configuration changes (either from hardware
changes or from a session getting focus) with the creation of the nested
servers fullscreen surfaces. A chunk of these are fixed by lp:~alan-
griffiths/mir/fix-1506846 - but there's probably more to come.

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

Title:
  unity8 crash on unplug of monitor

Status in canonical-pocket-desktop:
  New
Status in mir package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Stability of hotplug is much better -  so this is not a duplicate of bug 
1488863
  Maybe every 1/4 unplug event will see unity8 crashstrangely, didn't 
capture a crash log until now.

  This configuration is 
  latest PD image + silo 18 (with point release fixes for Mir0.17)
  also libertine/puritine installed
  xmir is from libertine devel ppa

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1513909/+subscriptions

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

[Touch-packages] [Bug 1509081] Re: nano segfaults as root after upgrade to 15.10

[Arthur Khasanov]

Wow, thanks for reply.

I've pressed affect link :)

And "comment out the "set locking" in your /etc/nanorc file." - had
helped me :)

Thanks again !

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

Title:
  nano segfaults as root after upgrade to 15.10

Status in nano package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 15.10
  Release:  15.10

  nano:
Installed: 2.4.2-1
Candidate: 2.4.2-1
Version table:
   *** 2.4.2-1 0
  500 http://mirror.bytemark.co.uk/ubuntu/ wily/main amd64 Packages
  100 /var/lib/dpkg/status

  
  After upgrading Ubuntu 15.04 to 15.10, when I run nano as root on a file it 
just segfaults. I'm not having this problem on other 15.04->15.10 upgrades

  strace is https://p.defau.lt/?q7xGwt3HoqB74xTawUUHDA
  catchsegv is https://p.defau.lt/?0SPQY_bDj6F6j1ZKeToQoA

  
  Under gdb with nano-dbgsym installed, it gives

  #0  main (argc=2, argv=0x7fffe688) at ../../src/nano.c:2768

  
  If I run it as sudo nano filename.txt, it gives an error as below rather than 
segfaulting

  [ Couldn't determine hostname for lock file: File name too long ]


  Both my user and root have the same locale settings. I've tried
  regenerating the locales

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

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

[Touch-packages] [Bug 1486878] Re: Sync llvm-toolchain-3.4 1:3.4.2-15 (universe) from Debian unstable (main)

[LocutusOfBorg]

It is needed if ghc still is at 7.8

I really hope ghc folks will be able to migrate to 7.10 sooner than
later

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

Title:
  Sync llvm-toolchain-3.4 1:3.4.2-15 (universe) from Debian unstable
  (main)

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

Bug description:
  Please sync llvm-toolchain-3.4 1:3.4.2-15 (universe) from Debian
  unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* Merge with Debian; remaining changes:
  - Revert to using the static copy of libjsoncpp, since the shared
library lacks sane versioning, and this is only a few thousand
lines of cargo-culted code from a reasonably stagnant upstream.
  - Drop lcov build-dep to avoid pulling it into main, due to its
being fundamentally incompatibe with our newer GCC versions.
  - Build-depend on gcc-multilib on amd64 and i386.
  - Backport upstream patch to not try to handle [SU]MUL_LOHI nodes
on aarch64, needed to build ghc.
  - Unconditionally link lldb with -latomic on all architectures.
  - Don't build python-lldb-3.4 on arm64.
* Disable polly. Not ready for ISL 0.14.
* Merge with Debian; remaining changes:
  - Revert to using the static copy of libjsoncpp, since the shared
library lacks sane versioning, and this is only a few thousand
lines of cargo-culted code from a reasonably stagnant upstream.
  - Drop lcov build-dep to avoid pulling it into main, due to its
being fundamentally incompatibe with our newer GCC versions.
  - Build-depend on gcc-multilib on amd64 and i386.
  - Backport upstream patch to not try to handle [SU]MUL_LOHI nodes
on aarch64, needed to build ghc.
  - Unconditionally link lldb with -latomic on all architectures.
  - Don't build python-lldb-3.4 on arm64.
* Disable polly. Not ready for ISL 0.14.
* Merge with Debian; remaining changes:
  - Revert to using the static copy of libjsoncpp, since the shared
library lacks sane versioning, and this is only a few thousand
lines of cargo-culted code from a reasonably stagnant upstream.
  - Drop lcov build-dep to avoid pulling it into main, due to its
being fundamentally incompatibe with our newer GCC versions.
  - Build-depend on gcc-multilib on amd64 and i386.
  - Backport upstream patch to not try to handle [SU]MUL_LOHI nodes
on aarch64, needed to build ghc.
  - Unconditionally link lldb with -latomic on all architectures.
* Don't build python-lldb-3.4 on arm64.
* Merge with Debian; remaining changes:
  - Revert to using the static copy of libjsoncpp, since the shared
library lacks sane versioning, and this is only a few thousand
lines of cargo-culted code from a reasonably stagnant upstream.
  - Drop lcov build-dep to avoid pulling it into main, due to its
being fundamentally incompatibe with our newer GCC versions.
  - Build-depend on gcc-multilib on amd64 and i386.
  - Backport upstream patch to not try to handle [SU]MUL_LOHI nodes
on aarch64, needed to build ghc.
  - Unconditionally link lldb with -latomic on all architectures.
* Don't build python-lldb-3.4 on arm64.
* debian/rules: fix compiler-rt/libclang-3.4-dev FTBFS on !x86.
* debian/rules: fix compiler-rt/libclang-3.4-dev FTBFS on !x86.
* debian/rules: fix compiler-rt/libclang-3.4-dev FTBFS on !x86.
* debian/rules: fix compiler-rt/libclang-3.4-dev FTBFS on !x86.
* Backport upstream patch to not try to handle [SU]MUL_LOHI nodes on
  aarch64, needed to build ghc.
* Backport upstream patch to not try to handle [SU]MUL_LOHI nodes on
  aarch64, needed to build ghc.
* Unconditionally link lldb with -latomic.
* Rebuild for ocaml-4.01.
* Bring over Ubuntu changes from 3.3:
  - Revert to using the static copy of libjsoncpp, since the shared
library lacks sane versioning, and this is only a few thousand
lines of cargo-culted code from a reasonably stagnant upstream.
  - Drop lcov build-dep to avoid pulling it into main, due to its
being fundamentally incompatibe with our newer GCC versions.
* Don't run the lldb tests on armhf (time out on the buildd).
* Don't run the lldb tests on armhf (time out on the buildd).
* Disable the lldb build for AArch64.
* Build-depend on gcc-multilib on amd64 and i386.
* Disable the lldb build for AArch64.
* Build-depend on gcc-multilib on amd64 and i386.
* Disable the lldb build for AArch64.
* Build-depend on gcc-multilib on amd64 and i386.

  
  I don't know the reason for gcc-multilib, but libjsoncpp is fixed and in main,
  the same for gconv.

  the other failures should be fixed in wily

  Changelog entries since current 

[Touch-packages] [Bug 1503832] Re: SDK cross build does not set PKG_CONFIG_PATH properly according to the architecture

[Benjamin Zeller]

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

** Changed in: qtcreator-plugin-ubuntu (Ubuntu)
   Status: Incomplete => Triaged

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

Title:
  SDK cross build does not set PKG_CONFIG_PATH properly according to the
  architecture

Status in click package in Ubuntu:
  New
Status in qtcreator-plugin-ubuntu package in Ubuntu:
  Triaged

Bug description:
  Trying to build a library under click-ubuntu-sdk-15.04-armhf.
  Library requires libpay2-dev to compile.
  I have manually installed the package for armhf on the chroot using the 
"Maintain" option.

  (click-ubuntu-sdk-15.04-armhf)root@beasty:/home/antti# dpkg-query -L 
libpay2-dev:armhf
     ...
  /usr/lib/arm-linux-gnueabihf/pkgconfig/pay-2.pc

  (click-ubuntu-sdk-15.04-armhf)root@beasty:/home/antti# pkg-config --debug 
--exists pay-2
  Cannot open directory '/usr/local/lib/x86_64-linux-gnu/pkgconfig' in package 
search path: No such file or directory
    ...
  Looking for package 'pay-2'
  Looking for package 'pay-2-uninstalled'

  (click-ubuntu-sdk-15.04-armhf)root@beasty:/home/antti# export 
PKG_CONFIG_PATH=/usr/lib/arm-linux-gnueabihf/pkgconfig/
  (click-ubuntu-sdk-15.04-armhf)root@beasty:/home/antti# pkg-config --exists 
pay-2 && echo $?
  0

  
  Because the arch specific pkg-config path is not set, any qmake project that 
relies on pkg-config to find libraries will fail on qmake run.

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

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

[Touch-packages] [Bug 1514822] Re: activeFocusOnTab is not accessible

[Bill Filler]

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

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Zoltan Balogh (bzoltan)

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

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

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

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

Title:
  activeFocusOnTab is not accessible

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

Bug description:
  I am using  QtQuick 2.4 and Ubuntu.Components.ListItems 1.3.

  By default all ListItems receive focus. For my app I want to disable
  focus for some of the items.

  I am trying to set "activeFocusOnTab" to false but I am receiving this error 
message: 
  "ListItem.Empty.activeFocusOnTab" is not available due to component 
versioning"

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

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

[Touch-packages] [Bug 1512454] Re: Refresh change colours

[Dominik]

The original computer model is Samsung R540, but most parts of this
computer been replaced (motherboard due to hardware damage, and it is
likely that it is not from this model but similar model, CPU replaced
for faster Intel I5 - 540M, and also Hard drive changed, and if I
remember properly RAM memory also has been replaced)

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

Title:
  Refresh change colours

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I had experienced few times that refreshing window causes some places to lose 
right information about colour. I mean that colours change to different for 
e.g. grey become yellowish, and strips are visible. Also in web browser some 
letters disappear.
  It is happening not often, maybe about 2/3 times per month. I am using Ubuntu 
14.04, with following Hardware:
  Intel core I5 540M 2.53 GHz x 2 with Intel Ironlake Mobile graphics. System 
Is 64 bit version. 3,7GiB Ram.
  I'm using two screens with different size. First one is built-in laptop 
screen with resolution 1366x768 (16:9) and second one is Hitachi 22HXJ06U with 
resolution 1920x1080 (16:9). This happened to me also in Ubuntu 15.04, and 
before on Ubuntu 14.10. (In all cases the same hardware and two screens). Until 
now I notice this bug only when on firefox so I thought it could be something 
wrong with firefox, but today I noticed this bug on Terminal Window. I cannot 
really provide information how to create this bug - twice it happened on 
facebook when board automatically refreshed, and today it happened on Terminal 
when I clicked on firefox. I tried to repeat the problem with terminal, using 
the same commands but without positive results. Bug is fixing when window / 
application getting refreshed - scrolling up / down or moving window on screen 
fixing it. Creating Screenshot doesn't fixing it (done by default Print Screen 
with animation that everything becoming white and going to normal imag
 e)
  I also checked logs (/var/log/Xorg.0.log) but I dont see any error message or 
something - log finishing after screen setting up.
  I attached picture with example in firefox window (screenshots was bit edited 
- facebook's board, chat and chat list been deleted).
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.18
  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
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 4.3.10: added
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 18) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd Device [144d:c06a]
  InstallationDate: Installed on 2015-10-17 (23 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Lsusb:
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth 
Dongle (HCI mode)
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: SAMSUNG ELECTRONICS CO., LTD. R530/R730
  Package: xorg 1:7.7+1ubuntu8.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic 
root=UUID=6a48f3d5-02ba-4f34-94c0-92cfcb90d476 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
  Tags:  trusty ubuntu compiz-0.9
  Uname: Linux 3.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/24/2010
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 04JV.M012.20100324.hkk
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: R530/R730
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr04JV.M012.20100324.hkk:bd03/24/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR530/R730:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR530/R730:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: R530/R730
  dmi.product.version: Not Applicable
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  

[Touch-packages] [Bug 1513450] Re: ActivityIndicators cause very high cpu usage for unity8/mir even when visible: false

[Alberto Aguirre]

Also worth noting that the 40% figure is with the default "ondemand"
governor, which changes cpu clock "ondemand" and can potentially also
change gpu clocks.

Using the "performance" governor (which fixes the cpu clock and
potentially the gpu clock) the figure is closer to 10% cpu load on an
N7.

On a vegetahd, with the default cpu governor, the server cpu load is
around 20%. With the performance governor, the cpu load is around 11%.

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

Title:
  ActivityIndicators cause very high cpu usage for unity8/mir even when
  visible: false

Status in Canonical System Image:
  In Progress
Status in canonical-pocket-desktop:
  New
Status in Mir:
  In Progress
Status in QtMir:
  New
Status in Online Accounts setup for Ubuntu Touch:
  New
Status in Ubuntu UI Toolkit:
  New
Status in ubuntu-system-settings package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  running in window mode, open u-s-s, run top
  unity8 running at ~40% cpu on N7 cpu freq ~1GHz

  no monitor attached

  note: testing with silo 18 of mir containing
  lp:~albaguirre/mir/fix-1499039 (equivalent for 0.17)

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

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

[Touch-packages] [Bug 1514928] Re: ListItem outside ListView segfaults

[Bill Filler]

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

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Zoltan Balogh (bzoltan)

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

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

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

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

Title:
  ListItem outside ListView segfaults

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

Bug description:
  Reproduce:
  Use the code from the documentation [1] but add selected: true to any 
ListItem.

  What happens:
  UUITK segfaults

  What should happen:
  It should highlight and not crash

  Stack trace:
  http://pastebin.ubuntu.com/13217004/

  Seems selectedList.contains(-1) segfaults for some reason.

  [1] http://pastebin.ubuntu.com/13217263/

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

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

[Touch-packages] [Bug 1514940] Re: [Phone] Leaving wifi or mobile coverage, later connection is not correctly restored

[Nelux]

** Attachment added: "Leaving mobile coverage. Connection is re-established but 
system doesn't set a route"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1514940/+attachment/4516356/+files/syslog_not_working_mobile

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

Title:
  [Phone] Leaving wifi or mobile coverage, later connection is not
  correctly restored

Status in network-manager package in Ubuntu:
  New

Bug description:
  Sorry for my English, still is not good.

  This bug is similar to https://bugs.launchpad.net/ubuntu/+source
  /network-manager/+bug/1436427 Connection is established but system
  doesn't set a route. Executing ip route is empty.

  phablet@ubuntu-phablet:~$ sudo system-image-cli -i
  current build number: 26
  device name: krillin
  channel: ubuntu-touch/stable/bq-aquaris.en
  last update: 2015-10-22 14:14:45
  version version: 26
  version ubuntu: 20151015
  version device: 20150821-736d127
  version custom: 20150925-901-35-40-vivid

  This bug is very very difficult to reproduce. You can follow this
  steps and sometimes fail:

  1- Keep always screen off.
  2- Go to a zone without wifi nor mobile coverage, for example, an underground 
parking.
  3- Stay in for a few minutes.
  4- When you go out and screen on mobile you observe connection is 
established, but sometimes system doesn't set a route, so you don't have 
Internet access regardless you have a connection established.

  In the screenshot attached you can view that.

  Workaround: enable plane mode then disable.

  This bug happens with wifi connected or disconnected, and with wifi
  enabled or disabled. And happens only when phone is suspended. It
  seems it's too many suspended and NetworkManager can't perform certain
  actions.

  I will attach 4 syslog's from early days ago, here you can see when
  it's working well and when not.

  I've observed that when it works this line is present:
  NetworkManager[1500]:  Policy set ..[(ccmni0) or (wlan0)] as
  default for IPv4 routing and DNS.

  If this line is not present it doesn't works.

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

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

[Touch-packages] [Bug 1514880] Re: If a song does not have an album art, quality of displayed note image is very low

[Michal Predotka]

Although the source of this problem might be the thumbnailer, it clearly
affects the Music app.

** Changed in: music-app
   Status: Invalid => New

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

Title:
  If a song does not have an album art, quality of displayed note image
  is very low

Status in Ubuntu Music App:
  New
Status in thumbnailer package in Ubuntu:
  New

Bug description:
  I have some songs/albums which don't have its own image to show when
  the song is being played. In that case there's a generic image
  visible. Problem is that image does not look very good. See screenshot
  attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/music-app/+bug/1514880/+subscriptions

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

[Touch-packages] [Bug 1514943] [NEW] The battery indicator shows always full on the car handsfree display

[Javier Garcia]

Public bug reported:

On my VW car handsfree display, when my ubuntu phone is paired, the
battery indicator shows always full (at any state of charge).

I am using my Aquaris E4.5 with Ubuntu 15.04 (r26)

** Affects: bluetooth-touch (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  The battery indicator shows always full on the car handsfree display

Status in bluetooth-touch package in Ubuntu:
  New

Bug description:
  On my VW car handsfree display, when my ubuntu phone is paired, the
  battery indicator shows always full (at any state of charge).

  I am using my Aquaris E4.5 with Ubuntu 15.04 (r26)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluetooth-touch/+bug/1514943/+subscriptions

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

[Touch-packages] [Bug 1506412] Re: /usr/sbin/NetworkManager:11:nm_device_get_unmanaged_flag:nm_device_get_default_unmanaged:_set_state_full:nm_device_state_changed:queued_set_state

[Launchpad Bug Tracker]

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

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  
/usr/sbin/NetworkManager:11:nm_device_get_unmanaged_flag:nm_device_get_default_unmanaged:_set_state_full:nm_device_state_changed:queued_set_state

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding network-manager.  This problem was most recently seen with
  version 1.0.4-0ubuntu4, the problem page at
  https://errors.ubuntu.com/problem/f5cac0a2baf0d8d9ff1fa1c87e16a74167a6dcc7
  contains more details.

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

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

[Sebastien Bacher]

Could you also maybe explain what you changed in the regexp and why and
how that resolves the issue?

-- 
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 1507463] Re: OverlayFS: Wrong mnt_id and path reported in /proc in linux-3.13

[oleg]

** No longer affects: lxc (Ubuntu)

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

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

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

[Matthias Goldhoorn]

Debian testing is not affected i use it too

On 10.11.2015 17:57, Sebastien Bacher wrote:
> Debian as well, could you report the bug to the Debian BTS as well?

-- 
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 878434] Re: No devices support color management detected

[ML]

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

** This bug is no longer a duplicate of bug 853056
   Cannot select ICC profile
** This bug has been marked a duplicate of bug 1469273
ICC profile doesn't get applied when proprietary Nvidia driver is in use

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

Title:
  No devices support color management detected

Status in colord package in Ubuntu:
  Confirmed

Bug description:
  I have a Samsung SyncMaster 2493HM monitor connected over DVI to a
  Nvidia GeForce 8600 graphics card.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: colord 0.1.12-1ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  CheckboxSubmission: 8b5778459c1f0a1989b8d1d888befce0
  CheckboxSystem: 4ed15c40009aa6f7770f606350a390a2
  Date: Wed Oct 19 20:59:20 2011
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  ProcEnviron:
   LANGUAGE=en
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: colord
  UpgradeStatus: Upgraded to oneiric on 2011-10-18 (0 days ago)

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

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

[Touch-packages] [Bug 1514942] Re: lxc-tests no runtime help (no man page, no --help, etc) for any of the lxc-tests tools

[Stéphane Graber]

Pushed to all packaging branches.

** Changed in: lxc (Ubuntu)
   Status: New => Fix Committed

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

Title:
  lxc-tests no runtime help (no man page, no --help, etc) for any of the
  lxc-tests tools

Status in lxc package in Ubuntu:
  Fix Committed

Bug description:
  I'm investigating lxc-tests and have very little idea what they
  actually do.  I had hoped to read a man page, or even just pass --help
  to them to get some idea of what each is actually doing.

  For example, lxc-test-apparmor, I know it does something with
  apparmor, but no idea what.  And as they all seem to ignore --help, I
  have no idea at all what it is actually doing.

  Please document these tests so users actually understand what they are
  testing.  Many tests pass, but some fail, and I really don't know why
  they're failing, or what they're even doing in the first place to
  cause a fail.

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

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

[Touch-packages] [Bug 1514942] Re: lxc-tests no runtime help (no man page, no --help, etc) for any of the lxc-tests tools

[Stéphane Graber]

The lxc-tests package was introduced so that autopkgtest can run all the
LXC tests on upload through the debian/tests/exercise script.

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

Title:
  lxc-tests no runtime help (no man page, no --help, etc) for any of the
  lxc-tests tools

Status in lxc package in Ubuntu:
  Fix Committed

Bug description:
  I'm investigating lxc-tests and have very little idea what they
  actually do.  I had hoped to read a man page, or even just pass --help
  to them to get some idea of what each is actually doing.

  For example, lxc-test-apparmor, I know it does something with
  apparmor, but no idea what.  And as they all seem to ignore --help, I
  have no idea at all what it is actually doing.

  Please document these tests so users actually understand what they are
  testing.  Many tests pass, but some fail, and I really don't know why
  they're failing, or what they're even doing in the first place to
  cause a fail.

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

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

[Launchpad Bug Tracker]

This bug was fixed in the package indicator-sound -
12.10.2+16.04.20151103.2-0ubuntu1

---
indicator-sound (12.10.2+16.04.20151103.2-0ubuntu1) xenial; urgency=medium

  [ Xavi Garcia ]
  * Added OSD notifications to show output source when the volume or
source change (LP: #1382548, LP: #1415480, LP: #1484589)

  [ CI Train Bot ]
  * New rebuild forced.

 -- Xavi Garcia   Tue, 03 Nov 2015
17:47:10 +

** Changed in: indicator-sound (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Spurious volume notification when changing output role with headphones

Status in Canonical System Image:
  In Progress
Status in indicator-sound package in Ubuntu:
  Fix Released
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 1415480] Re: [indicators]/OSD provide no visual clue that they modify bluetooth device volumes

[Launchpad Bug Tracker]

This bug was fixed in the package indicator-sound -
12.10.2+16.04.20151103.2-0ubuntu1

---
indicator-sound (12.10.2+16.04.20151103.2-0ubuntu1) xenial; urgency=medium

  [ Xavi Garcia ]
  * Added OSD notifications to show output source when the volume or
source change (LP: #1382548, LP: #1415480, LP: #1484589)

  [ CI Train Bot ]
  * New rebuild forced.

 -- Xavi Garcia   Tue, 03 Nov 2015
17:47:10 +

** Changed in: indicator-sound (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  [indicators]/OSD provide no visual clue that they modify bluetooth
  device volumes

Status in Canonical System Image:
  In Progress
Status in Ubuntu UX:
  Triaged
Status in indicator-bluetooth package in Ubuntu:
  Invalid
Status in indicator-sound package in Ubuntu:
  Fix Released

Bug description:
  Connect a bluetooth audio device (headset, speakers) to the ubuntu
  phone.

  Play music/enter into a call, so that you have active audio to the
  device.

  Adjust the volume, using the UI or keys on the ubuntu phone.

  The volume of the bluetooth headset changes (good) but the ui contains
  no clue that this is what the phone is doing (less good). The standard
  volume indicator is shown. This can lead to user confusion if they are
  not currently using the paired bluetooth accessory, and have forgotten
  it is paired. On other devices the volume indicator changes to provide
  visual feedback that the bluetooth device volume is being set.

  --

  Desired resolution:

  Please use this icon to replace the volume icon. The icon is bluetooth
  volume which we had design already.

  https://www.dropbox.com/s/a5r3ro1h0917p0a/audio-speakers-bluetooth-
  symbolic.svg?dl=0

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

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

[Touch-packages] [Bug 1205713] Re: unable to type Greek characters to the dash

[Brandon Schaefer]

** Changed in: nux/2.0
   Status: In Progress => Triaged

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

Title:
  unable to type Greek characters to the dash

Status in Nux:
  Fix Released
Status in Nux 2.0 series:
  Triaged
Status in Unity:
  Invalid
Status in nux package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Invalid

Bug description:
  On Ubuntu 13.10 Saucy, when i switch to the Greek layout, i cannot type any 
greek character to the Dash's search field.
  The pointer does not move at all, which means that it is not just an 
appearance problem, but there is no input at all of the character.
  The same applies when i try to use the "Execute command" field that appears 
when pressing the Alt+F2 keyboard shortcut.
  This has only to do wiith greek characters, as other characters that are not 
related to the keyboard layout (such as numerical characters, dots, comas, 
hyphens etc) can be typed normally regardless of the keyboard layout setting.

  ** Workaround **
  In the terminal:
im-config -n xim

  Then reboot!

  ProblemType: BugDistroRelease: Ubuntu 13.10
  Package: unity 7.0.2+13.10.20130723.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.10.0-5.15-generic 3.10.2
  Uname: Linux 3.10.0-5-generic x86_64
  ApportVersion: 2.11-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sat Jul 27 23:02:46 2013
  InstallationDate: Installed on 2013-07-12 (15 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130711)
  MarkForUpload: TrueSourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1458952] Re: Memory leak in InputMethodIBus

[Brandon Schaefer]

** Changed in: nux (Ubuntu)
   Status: In Progress => Triaged

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

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

Title:
  Memory leak in InputMethodIBus

Status in Nux:
  Fix Released
Status in Nux trusty series:
  Triaged
Status in nux package in Ubuntu:
  Fix Released

Bug description:
  There are two memory leaks in InputMethodIBus. One is with releasing
  the ibus_bus and the other being the keybinding.

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

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

[Touch-packages] [Bug 1514080] Re: lxc-templates lacks template for ubuntu core

[Serge Hallyn]

The download template (which is recommended) installs no ssh and no
ubuntu password.

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

Title:
  lxc-templates lacks template for ubuntu core

Status in lxc package in Ubuntu:
  New

Bug description:
  Hi,

  lxc-templates comes with tamples for ubuntu and ubuntu-cloud, but both
  are rather large and „complete”, too large for most applications. E.g.
  it does not make sense to have multiple consoles running in a
  container or an sshd.

  Would be nice to have a template for ubuntu-core as an absolute
  minimal system.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: lxc-templates 1.1.4-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Nov  7 16:04:54 2015
  InstallationDate: Installed on 2015-10-08 (29 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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

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

[Touch-packages] [Bug 1514940] Re: [Phone] Leaving wifi or mobile coverage, later connection is not correctly restored

[Nelux]

** Attachment added: "Leaving mobile coverage. Connection is correctly 
re-established"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1514940/+attachment/4516355/+files/syslog_working_mobile

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

Title:
  [Phone] Leaving wifi or mobile coverage, later connection is not
  correctly restored

Status in network-manager package in Ubuntu:
  New

Bug description:
  Sorry for my English, still is not good.

  This bug is similar to https://bugs.launchpad.net/ubuntu/+source
  /network-manager/+bug/1436427 Connection is established but system
  doesn't set a route. Executing ip route is empty.

  phablet@ubuntu-phablet:~$ sudo system-image-cli -i
  current build number: 26
  device name: krillin
  channel: ubuntu-touch/stable/bq-aquaris.en
  last update: 2015-10-22 14:14:45
  version version: 26
  version ubuntu: 20151015
  version device: 20150821-736d127
  version custom: 20150925-901-35-40-vivid

  This bug is very very difficult to reproduce. You can follow this
  steps and sometimes fail:

  1- Keep always screen off.
  2- Go to a zone without wifi nor mobile coverage, for example, an underground 
parking.
  3- Stay in for a few minutes.
  4- When you go out and screen on mobile you observe connection is 
established, but sometimes system doesn't set a route, so you don't have 
Internet access regardless you have a connection established.

  In the screenshot attached you can view that.

  Workaround: enable plane mode then disable.

  This bug happens with wifi connected or disconnected, and with wifi
  enabled or disabled. And happens only when phone is suspended. It
  seems it's too many suspended and NetworkManager can't perform certain
  actions.

  I will attach 4 syslog's from early days ago, here you can see when
  it's working well and when not.

  I've observed that when it works this line is present:
  NetworkManager[1500]:  Policy set ..[(ccmni0) or (wlan0)] as
  default for IPv4 routing and DNS.

  If this line is not present it doesn't works.

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

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

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

[Matthias Goldhoorn]

The rexexp checks for availible compiler versions.
Theregexp checks for X.X.X i changed the regexpt to X.X

The fallback was to use gcc 4.9 which was availible on ubuntu.
The new gcc is 5.2, therefore now the new regexpt matches.

I do not checked the originial debian rules from the debian project. I 
can only say that the bug does not exist there..


On 10.11.2015 18:17, Sebastien Bacher wrote:
> Could you also maybe explain what you changed in the regexp and why and
> how that resolves the issue?
>

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

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

[Matthias Goldhoorn]

On 10.11.2015 18:17, Sebastien Bacher wrote:
> Could you also maybe explain what you changed in the regexp and why and
> how that resolves the issue?
>
additon:
By changing the regexpt the package got now compiled with gcc5.2 instead 
of 4.9

-- 
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 1514940] [NEW] [Phone] Leaving wifi or mobile coverage, later connection is not correctly restored

[Nelux]

Public bug reported:

Sorry for my English, still is not good.

This bug is similar to https://bugs.launchpad.net/ubuntu/+source
/network-manager/+bug/1436427 Connection is established but system
doesn't set a route. Executing ip route is empty.

phablet@ubuntu-phablet:~$ sudo system-image-cli -i
current build number: 26
device name: krillin
channel: ubuntu-touch/stable/bq-aquaris.en
last update: 2015-10-22 14:14:45
version version: 26
version ubuntu: 20151015
version device: 20150821-736d127
version custom: 20150925-901-35-40-vivid

This bug is very very difficult to reproduce. You can follow this steps
and sometimes fail:

1- Keep always screen off.
2- Go to a zone without wifi nor mobile coverage, for example, an underground 
parking.
3- Stay in for a few minutes.
4- When you go out and screen on mobile you observe connection is established, 
but sometimes system doesn't set a route, so you don't have Internet access 
regardless you have a connection established.

In the screenshot attached you can view that.

Workaround: enable plane mode then disable.

This bug happens with wifi connected or disconnected, and with wifi
enabled or disabled. And happens only when phone is suspended. It seems
it's too many suspended and NetworkManager can't perform certain
actions.

I will attach 4 syslog's from early days ago, here you can see when it's
working well and when not.

I've observed that when it works this line is present:
NetworkManager[1500]:  Policy set ..[(ccmni0) or (wlan0)] as
default for IPv4 routing and DNS.

If this line is not present it doesn't works.

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


** Tags: manager network phone touch ubuntu

** Attachment added: "screenshot20151104_100839757.png"
   
https://bugs.launchpad.net/bugs/1514940/+attachment/4516352/+files/screenshot20151104_100839757.png

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

Title:
  [Phone] Leaving wifi or mobile coverage, later connection is not
  correctly restored

Status in network-manager package in Ubuntu:
  New

Bug description:
  Sorry for my English, still is not good.

  This bug is similar to https://bugs.launchpad.net/ubuntu/+source
  /network-manager/+bug/1436427 Connection is established but system
  doesn't set a route. Executing ip route is empty.

  phablet@ubuntu-phablet:~$ sudo system-image-cli -i
  current build number: 26
  device name: krillin
  channel: ubuntu-touch/stable/bq-aquaris.en
  last update: 2015-10-22 14:14:45
  version version: 26
  version ubuntu: 20151015
  version device: 20150821-736d127
  version custom: 20150925-901-35-40-vivid

  This bug is very very difficult to reproduce. You can follow this
  steps and sometimes fail:

  1- Keep always screen off.
  2- Go to a zone without wifi nor mobile coverage, for example, an underground 
parking.
  3- Stay in for a few minutes.
  4- When you go out and screen on mobile you observe connection is 
established, but sometimes system doesn't set a route, so you don't have 
Internet access regardless you have a connection established.

  In the screenshot attached you can view that.

  Workaround: enable plane mode then disable.

  This bug happens with wifi connected or disconnected, and with wifi
  enabled or disabled. And happens only when phone is suspended. It
  seems it's too many suspended and NetworkManager can't perform certain
  actions.

  I will attach 4 syslog's from early days ago, here you can see when
  it's working well and when not.

  I've observed that when it works this line is present:
  NetworkManager[1500]:  Policy set ..[(ccmni0) or (wlan0)] as
  default for IPv4 routing and DNS.

  If this line is not present it doesn't works.

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

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

Just checked debian testing does a simliar change with a slighly
different reg-exp:

old:
http://http.debian.net/debian/pool/main/l/llvm-toolchain-3.4/llvm-toolchain-3.4_3.4.2-13.debian.tar.xz
new:
http://http.debian.net/debian/pool/main/l/llvm-toolchain-3.4/llvm-toolchain-3.4_3.4.2-16.debian.tar.xz

-- 
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 1311362] Re: Ubuntu Gnome 14.04 - NVidia 331 - OpenCL broken (using Darktable)

[The Bright Side]

For Darktable, I'm pretty sure all you'll need to do is install the
nvidia-modprobe package after you activate the Nvidia drivers. It'll
then work without any further ado. Let me know if that does the trick
for you - it's been working for me over the past 3 Ubuntu releases,
across 3 PCs.

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

Title:
  Ubuntu Gnome 14.04 - NVidia 331 - OpenCL broken (using Darktable)

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  ** Steps to Reproduce: **
  1. Perform a fresh installation of Ubuntu Gnome 14.04 64-bit on a clean PC
  2. Using the "Additional Drivers" application, install latest NVidia driver 
(331)
  3. Reboot
  4. Install latest Darktable (1.4) from Ubuntu's repositories
  5. In Terminal, run "darktable -d opencl"

  ** Actual Result: **
  In Ubuntu Gnome 14.04, using the NVidia 331 driver, Darktable won't run with 
OpenCL support. The following debug output is observed in the terminal:

  [opencl_init] opencl related configuration options:
  [opencl_init]
  [opencl_init] opencl: 1
  [opencl_init] opencl_library: ''
  [opencl_init] opencl_memory_requirement: 768
  [opencl_init] opencl_memory_headroom: 300
  [opencl_init] opencl_device_priority: '*/!0,*/*/*'
  [opencl_init] opencl_size_roundup: 16
  [opencl_init] opencl_async_pixelpipe: 0
  [opencl_init] opencl_synch_cache: 0
  [opencl_init] opencl_number_event_handles: 25
  [opencl_init] opencl_micro_nap: 1000
  [opencl_init] opencl_use_pinned_memory: 0
  [opencl_init] opencl_use_cpu_devices: 0
  [opencl_init] opencl_avoid_atomics: 0
  [opencl_init] opencl_omit_whitebalance: 0
  [opencl_init]
  [opencl_init] trying to load opencl library: ''
  [opencl_init] could not find opencl runtime library 'libOpenCL'
  [opencl_init] no working opencl library found. Continue with opencl disabled
  [opencl_init] FINALLY: opencl is NOT AVAILABLE on this system.
  [opencl_init] initial status of opencl enabled flag is OFF.
  [pixelpipe_process] [thumbnail] using device -1
  [pixelpipe_process] [thumbnail] using device -1

  ** Expected Result: **
  Software using OpenCL should continue to work as it did in Ubuntu 13.10.

  ** Notes: **
  Graphics card: GeForce GTX 680 (Gigabyte GV-N680OC-2GD)
  Encuontered on Ubuntu Gnome 14.04, 64 bit.
  Likely occurs on regular Ubuntu (not Ubuntu Gnome) as well.
  This issue also occurs when running NVidia 331 Update, NVidia Legacy 304 as 
well as Nouveau.
  This issue did not occur on Ubuntu Gnome 13.10.
  Bug filed in Darktable: 
http://www.darktable.org/redmine/issues/9913#change-24936

  ** Troubleshooting: **
  The following files and directories relating to OpenCL were found on the test 
system:

  locate -i libopencl
  /usr/lib/i386-linux-gnu/libOpenCL.so.1
  /usr/lib/i386-linux-gnu/libOpenCL.so.1.0
  /usr/lib/i386-linux-gnu/libOpenCL.so.1.0.0
  /usr/lib/x86_64-linux-gnu/libOpenCL.so.1
  /usr/lib/x86_64-linux-gnu/libOpenCL.so.1.0
  /usr/lib/x86_64-linux-gnu/libOpenCL.so.1.0.0
  /usr/share/doc/nvidia-libopencl1-331
  /usr/share/doc/nvidia-libopencl1-331/changelog.Debian.gz
  /usr/share/doc/nvidia-libopencl1-331/copyright
  /var/cache/apt/archives/nvidia-libopencl1-331_331.38-0ubuntu7_amd64.deb
  /var/lib/dpkg/info/nvidia-libopencl1-331.list
  /var/lib/dpkg/info/nvidia-libopencl1-331.md5sums
  /var/lib/dpkg/info/nvidia-libopencl1-331.postinst
  /var/lib/dpkg/info/nvidia-libopencl1-331.postrm
  /var/lib/dpkg/info/nvidia-libopencl1-331.shlibs

  installed the packages "opencl-headers" and "nvidia-profiler", but that made 
no difference.
  Manually edited /etc/ld.so.conf to include the directories found containing 
the OpenCL libraries (from the list above). Ran ldconfig. No difference.

  Output of clinfo:

  clinfo: /usr/lib/x86_64-linux-gnu/libOpenCL.so.1: no version information 
available (required by clinfo)
  E: -30

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.38  Wed Jan  8 19:32:30 
PST 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Tue Apr 22 17:59:29 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-24-generic, x86_64: installed
   nvidia-331-updates, 331.38, 3.13.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
  

[Touch-packages] [Bug 1514940] Re: [Phone] Leaving wifi or mobile coverage, later connection is not correctly restored

[Nelux]

** Attachment added: "Leaving wifi coverage. Mobile connects correctly."
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1514940/+attachment/4516353/+files/syslog_working_wifi

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

Title:
  [Phone] Leaving wifi or mobile coverage, later connection is not
  correctly restored

Status in network-manager package in Ubuntu:
  New

Bug description:
  Sorry for my English, still is not good.

  This bug is similar to https://bugs.launchpad.net/ubuntu/+source
  /network-manager/+bug/1436427 Connection is established but system
  doesn't set a route. Executing ip route is empty.

  phablet@ubuntu-phablet:~$ sudo system-image-cli -i
  current build number: 26
  device name: krillin
  channel: ubuntu-touch/stable/bq-aquaris.en
  last update: 2015-10-22 14:14:45
  version version: 26
  version ubuntu: 20151015
  version device: 20150821-736d127
  version custom: 20150925-901-35-40-vivid

  This bug is very very difficult to reproduce. You can follow this
  steps and sometimes fail:

  1- Keep always screen off.
  2- Go to a zone without wifi nor mobile coverage, for example, an underground 
parking.
  3- Stay in for a few minutes.
  4- When you go out and screen on mobile you observe connection is 
established, but sometimes system doesn't set a route, so you don't have 
Internet access regardless you have a connection established.

  In the screenshot attached you can view that.

  Workaround: enable plane mode then disable.

  This bug happens with wifi connected or disconnected, and with wifi
  enabled or disabled. And happens only when phone is suspended. It
  seems it's too many suspended and NetworkManager can't perform certain
  actions.

  I will attach 4 syslog's from early days ago, here you can see when
  it's working well and when not.

  I've observed that when it works this line is present:
  NetworkManager[1500]:  Policy set ..[(ccmni0) or (wlan0)] as
  default for IPv4 routing and DNS.

  If this line is not present it doesn't works.

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

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

[Touch-packages] [Bug 1514940] Re: [Phone] Leaving wifi or mobile coverage, later connection is not correctly restored

[Nelux]

** Attachment added: "Leaving wifi coverage. Mobile connection is stablished 
but system doesn't set a route"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1514940/+attachment/4516354/+files/syslog_not_working_wifi

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

Title:
  [Phone] Leaving wifi or mobile coverage, later connection is not
  correctly restored

Status in network-manager package in Ubuntu:
  New

Bug description:
  Sorry for my English, still is not good.

  This bug is similar to https://bugs.launchpad.net/ubuntu/+source
  /network-manager/+bug/1436427 Connection is established but system
  doesn't set a route. Executing ip route is empty.

  phablet@ubuntu-phablet:~$ sudo system-image-cli -i
  current build number: 26
  device name: krillin
  channel: ubuntu-touch/stable/bq-aquaris.en
  last update: 2015-10-22 14:14:45
  version version: 26
  version ubuntu: 20151015
  version device: 20150821-736d127
  version custom: 20150925-901-35-40-vivid

  This bug is very very difficult to reproduce. You can follow this
  steps and sometimes fail:

  1- Keep always screen off.
  2- Go to a zone without wifi nor mobile coverage, for example, an underground 
parking.
  3- Stay in for a few minutes.
  4- When you go out and screen on mobile you observe connection is 
established, but sometimes system doesn't set a route, so you don't have 
Internet access regardless you have a connection established.

  In the screenshot attached you can view that.

  Workaround: enable plane mode then disable.

  This bug happens with wifi connected or disconnected, and with wifi
  enabled or disabled. And happens only when phone is suspended. It
  seems it's too many suspended and NetworkManager can't perform certain
  actions.

  I will attach 4 syslog's from early days ago, here you can see when
  it's working well and when not.

  I've observed that when it works this line is present:
  NetworkManager[1500]:  Policy set ..[(ccmni0) or (wlan0)] as
  default for IPv4 routing and DNS.

  If this line is not present it doesn't works.

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

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

[Touch-packages] [Bug 1514940] Re: [Phone] Leaving wifi or mobile coverage, later connection is not correctly restored

[Nelux]

** Description changed:

  Sorry for my English, still is not good.
  
  This bug is similar to https://bugs.launchpad.net/ubuntu/+source
  /network-manager/+bug/1436427 Connection is established but system
  doesn't set a route. Executing ip route is empty.
  
  phablet@ubuntu-phablet:~$ sudo system-image-cli -i
  current build number: 26
  device name: krillin
  channel: ubuntu-touch/stable/bq-aquaris.en
  last update: 2015-10-22 14:14:45
  version version: 26
  version ubuntu: 20151015
  version device: 20150821-736d127
  version custom: 20150925-901-35-40-vivid
  
  This bug is very very difficult to reproduce. You can follow this steps
  and sometimes fail:
  
  1- Keep always screen off.
  2- Go to a zone without wifi nor mobile coverage, for example, an underground 
parking.
  3- Stay in for a few minutes.
  4- When you go out and screen on mobile you observe connection is 
established, but sometimes system doesn't set a route, so you don't have 
Internet access regardless you have a connection established.
  
  In the screenshot attached you can view that.
  
  Workaround: enable plane mode then disable.
  
  This bug happens with wifi connected or disconnected, and with wifi
  enabled or disabled. And happens only when phone is suspended. It seems
  it's too many suspended and NetworkManager can't perform certain
  actions.
  
- I will attach 4 syslog's from early days ago, here you can see when it's
+ I will attach 4 syslogs from early days ago, here you can see when it's
  working well and when not.
  
  I've observed that when it works this line is present:
  NetworkManager[1500]:  Policy set ..[(ccmni0) or (wlan0)] as
  default for IPv4 routing and DNS.
  
  If this line is not present it doesn't works.

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

Title:
  [Phone] Leaving wifi or mobile coverage, later connection is not
  correctly restored

Status in network-manager package in Ubuntu:
  New

Bug description:
  Sorry for my English, still is not good.

  This bug is similar to https://bugs.launchpad.net/ubuntu/+source
  /network-manager/+bug/1436427 Connection is established but system
  doesn't set a route. Executing ip route is empty.

  phablet@ubuntu-phablet:~$ sudo system-image-cli -i
  current build number: 26
  device name: krillin
  channel: ubuntu-touch/stable/bq-aquaris.en
  last update: 2015-10-22 14:14:45
  version version: 26
  version ubuntu: 20151015
  version device: 20150821-736d127
  version custom: 20150925-901-35-40-vivid

  This bug is very very difficult to reproduce. You can follow this
  steps and sometimes fail:

  1- Keep always screen off.
  2- Go to a zone without wifi nor mobile coverage, for example, an underground 
parking.
  3- Stay in for a few minutes.
  4- When you go out and screen on mobile you observe connection is 
established, but sometimes system doesn't set a route, so you don't have 
Internet access regardless you have a connection established.

  In the screenshot attached you can view that.

  Workaround: enable plane mode then disable.

  This bug happens with wifi connected or disconnected, and with wifi
  enabled or disabled. And happens only when phone is suspended. It
  seems it's too many suspended and NetworkManager can't perform certain
  actions.

  I will attach 4 syslogs from early days ago, here you can see when
  it's working well and when not.

  I've observed that when it works this line is present:
  NetworkManager[1500]:  Policy set ..[(ccmni0) or (wlan0)] as
  default for IPv4 routing and DNS.

  If this line is not present it doesn't works.

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

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

[Touch-packages] [Bug 1514928] [NEW] ListItem outside ListView segfaults

[Jonas G. Drange]

Public bug reported:

Reproduce:
Use the code from the documentation [1] but add selected: true to any ListItem.

What happens:
UUITK segfaults

What should happen:
It should highlight and not crash

Stack trace:
http://pastebin.ubuntu.com/13217004/

Seems selectedList.contains(-1) segfaults for some reason.

[1] http://pastebin.ubuntu.com/13217263/

** Affects: canonical-devices-system-image
 Importance: High
 Assignee: Zoltan Balogh (bzoltan)
 Status: New

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: High
 Assignee: Zoltan Balogh (bzoltan)
 Status: New

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

Title:
  ListItem outside ListView segfaults

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

Bug description:
  Reproduce:
  Use the code from the documentation [1] but add selected: true to any 
ListItem.

  What happens:
  UUITK segfaults

  What should happen:
  It should highlight and not crash

  Stack trace:
  http://pastebin.ubuntu.com/13217004/

  Seems selectedList.contains(-1) segfaults for some reason.

  [1] http://pastebin.ubuntu.com/13217263/

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

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

[Touch-packages] [Bug 1514950] [NEW] lxc-test-checkpoint-restore can't run because no criu installed

[Jeff Lane]

Public bug reported:

on a default 15.10 installation, I have installed lxc-tests and am
running through them individually.

lxc-test-checkpoint-restore fails to run because the package criu is not
installed

ubuntu@xwing:~$ sudo lxc-test-checkpoint-restore
/usr/bin/lxc-test-checkpoint-restore: 22: /usr/bin/lxc-test-checkpoint-restore: 
criu: not found
SKIP: skipping test because no (or wrong) criu installed.

installing lxc-tests should also install any test dependencies like
criu.

** Affects: lxc (Ubuntu)
 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/1514950

Title:
  lxc-test-checkpoint-restore can't run because no criu installed

Status in lxc package in Ubuntu:
  New

Bug description:
  on a default 15.10 installation, I have installed lxc-tests and am
  running through them individually.

  lxc-test-checkpoint-restore fails to run because the package criu is
  not installed

  ubuntu@xwing:~$ sudo lxc-test-checkpoint-restore
  /usr/bin/lxc-test-checkpoint-restore: 22: 
/usr/bin/lxc-test-checkpoint-restore: criu: not found
  SKIP: skipping test because no (or wrong) criu installed.

  installing lxc-tests should also install any test dependencies like
  criu.

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

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

[Touch-packages] [Bug 1514950] Re: lxc-test-checkpoint-restore can't run because no criu installed

[Stéphane Graber]

The behavior of the test is perfectly correct.

This test depends on a CRIU version which can't be found in the Ubuntu
archive and criu itself isn't available on most architectures.

As mentioned in the other bug report, lxc-tests is meant to be used by
autopkgtest through our autopkgtest test script, not directly by manual
users.

Also note that the lxc-test-* binaries DO NOT clean after themselves on
failure which will cause subsequent failures.

Those binaries are there to be run by people who contribute to LXC and
so know precisely what they do when tracking down regressions and for
use by autopkgtest, not by normal users.

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

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

Title:
  lxc-test-checkpoint-restore can't run because no criu installed

Status in lxc package in Ubuntu:
  Invalid

Bug description:
  on a default 15.10 installation, I have installed lxc-tests and am
  running through them individually.

  lxc-test-checkpoint-restore fails to run because the package criu is
  not installed

  ubuntu@xwing:~$ sudo lxc-test-checkpoint-restore
  /usr/bin/lxc-test-checkpoint-restore: 22: 
/usr/bin/lxc-test-checkpoint-restore: criu: not found
  SKIP: skipping test because no (or wrong) criu installed.

  installing lxc-tests should also install any test dependencies like
  criu.

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

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

[Touch-packages] [Bug 1514942] Re: lxc-tests no runtime help (no man page, no --help, etc) for any of the lxc-tests tools

[Stéphane Graber]

I'll update the package description to make it clear that users aren't
supposed to install that package :)

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

Title:
  lxc-tests no runtime help (no man page, no --help, etc) for any of the
  lxc-tests tools

Status in lxc package in Ubuntu:
  Fix Committed

Bug description:
  I'm investigating lxc-tests and have very little idea what they
  actually do.  I had hoped to read a man page, or even just pass --help
  to them to get some idea of what each is actually doing.

  For example, lxc-test-apparmor, I know it does something with
  apparmor, but no idea what.  And as they all seem to ignore --help, I
  have no idea at all what it is actually doing.

  Please document these tests so users actually understand what they are
  testing.  Many tests pass, but some fail, and I really don't know why
  they're failing, or what they're even doing in the first place to
  cause a fail.

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

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

[Touch-packages] [Bug 1480411] Re: rm -r * fails to delete directories when using overlayfs in a user-namespace

[oleg]

@Serge,

Thanks for the clarification;  I'll revert the status to un-marked.

** No longer affects: lxc (Ubuntu)

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

Title:
  rm -r * fails to delete directories when using overlayfs in a user-
  namespace

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  rm -r * fails to delete directories when using overlayfs in a user-
  namespace.

  If overlayfs is mounted as follows,

     mount -n -t overlay overlay -o
  lowerdir=lowerdir,upperdir=upperdir,workdir=workdir mntpt

  and if lowerdir contains lowerdir/foo/bar.txt, then,

     rm -r mntpt/foo

  fails with error message,

     "rm: cannot remove ‘mntpt/foo’: Operation not permitted"

  strace shows,

  unlinkat(AT_FDCWD, "mntpt/foo", AT_REMOVEDIR) = -1 EPERM
  (Operation not permitted)

  OS details: 64-bit ubuntu 14.04.2 with the linux-generic-lts-vivid
  kernel (3.19).

  The bug does not occur on ubuntu 14.04.2 with the default linux-
  generic 3.13 kernel.

  The bug occurs for any vanilla 3.18+ kernel to which the 1-line patch,
  "overlayfs: allow unprivileged mounts" is added.  (The patch is at,
  http://kernel.ubuntu.com/git/ubuntu/ubuntu-
  vivid.git/commit/?id=78ec45495b15d27d4cc6d05cc454e30ec5b587ea)

  The bug occurs regardless of whether the filesystem underlying
  overlayfs is tmpfs or ext4.

  The bug also occurs when running ubuntu 15.04 (ubuntu vivid) in a
  virtual machine (qemu-system-x86_64).  The host is ubuntu 14.04.2 with
  the default 3.13 kernel.

  A script which reproduces the bug is attached and is also available at
  http://paste.ubuntu.com/11974137/

  Hardware: intel core2 duo processor in a macbook-4.1

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

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

[Touch-packages] [Bug 1462664] Re: [Ubuntu Phone] With WIFI = ON the GPS stops

[Pat McGowan]

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

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

Title:
  [Ubuntu Phone] With WIFI = ON the GPS stops

Status in Canonical System Image:
  Fix Committed
Status in Oxide:
  New
Status in ubuntu-system-settings:
  New
Status in location-service package in Ubuntu:
  In Progress

Bug description:
  Hi!

  Steps: 
  1. Enable WIFI = ON on phone.
  2. Run one of these apps: GPS Navigation, HERE maps, Sensor Status.
  3. Drive.
  4. When you'll be into a WIFI area as a town or city, I'm thinking the WIFI 
will try to search WIFIs and then the GPS will stop, the GPS apps will not 
receive more new positions from the GPS.

  Extra info1: If you had GPS Navigation & Sensor running, both of them
  will not receive new GPS positions from the device. If you restart for
  example GPS Navigation, GPS Navigation will receive new positions, but
  Sensor Status not, until you restart it too.

  Extra info2: When the GPS stops the icon in the status disappears, but
  it you kill and relaunch the app, the icon will appear again.

  Thanks in advance!

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

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

[Touch-packages] [Bug 1493003] Re: 15:10: /usr/share/accounts/services/google-im.service provided by two packages, causing upgrade failure

[k0st1x]

2 @SoloTurn: I've used "apt-get purge" instead of "wajig purge" and
command is not helped for me : (

is there any workaround?

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

Title:
  15:10: /usr/share/accounts/services/google-im.service provided by two
  packages, causing upgrade failure

Status in account-plugins package in Ubuntu:
  Invalid
Status in ktp-accounts-kcm package in Ubuntu:
  Triaged

Bug description:
  sudo apt-get install kubuntu-full

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: kde-config-telepathy-accounts (not installed)
  Uname: Linux 4.1-6.dmz.1-liquorix-amd64 x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.18-0ubuntu9
  Architecture: amd64
  Date: Mon Sep  7 12:52:07 2015
  DuplicateSignature: package:kde-config-telepathy-accounts:(not 
installed):försöker skriva över 
"/usr/share/accounts/services/google-im.service" som också finns i paketet 
account-plugin-google 0.12+15.10.20150723-0ubuntu1
  ErrorMessage: försöker skriva över 
"/usr/share/accounts/services/google-im.service" som också finns i paketet 
account-plugin-google 0.12+15.10.20150723-0ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu3
   apt  1.0.9.10ubuntu6
  SourcePackage: ktp-accounts-kcm
  Title: package kde-config-telepathy-accounts (not installed) failed to 
install/upgrade: försöker skriva över 
"/usr/share/accounts/services/google-im.service" som också finns i paketet 
account-plugin-google 0.12+15.10.20150723-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1493003/+subscriptions

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

[Touch-packages] [Bug 1387643] Re: Pruning of probably stale sessions should be less aggressive

[Pat McGowan]

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

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

Title:
  Pruning of probably stale sessions should be less aggressive

Status in Canonical System Image:
  Fix Committed
Status in location-service package in Ubuntu:
  Confirmed

Bug description:
  Right now, after 10 non-successful attempts to deliver location
  updates to clients, the service considers the client to be hanging or
  dead and prunes the session from the service's cache. With that, if
  the app wakes up again, it does not receive updates for the same
  session anymore. A restart of the app fixes the issue.

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

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

[Touch-packages] [Bug 1514960] [NEW] lxc-test-checkpoint-restore fails with no explanation why

[Jeff Lane]

Public bug reported:

Ran the ste lxc-test-checkpoint-restore and that failed, but there is no
explanation in the output as to why it failed.  All the output I was
able to create says it created the container fine, but then just failed
for some reason:

I: Configuring libsemanage1:amd64...
I: Configuring libacl1:amd64...
I: Configuring makedev...
I: Configuring bsdutils...
I: Configuring coreutils...
I: Configuring tar...
I: Configuring dpkg...
I: Configuring sed...
I: Configuring perl-base...
I: Configuring grep...
I: Configuring debconf...
I: Configuring tzdata...
I: Configuring gzip...
I: Configuring dash...
I: Configuring sysv-rc...
I: Configuring libpam0g:amd64...
I: Configuring libpam-modules-bin...
I: Configuring bash...
I: Configuring libpam-modules:amd64...
I: Configuring libpam-runtime...
I: Configuring passwd...
I: Configuring login...
I: Configuring adduser...
I: Configuring libuuid1:amd64...
I: Configuring libblkid1:amd64...
I: Configuring libmount1:amd64...
I: Configuring libcryptsetup4:amd64...
I: Configuring mount...
I: Configuring libfdisk1:amd64...
I: Configuring initscripts...
I: Configuring util-linux...
I: Configuring e2fsprogs...
I: Configuring procps...
I: Configuring udev...
I: Configuring systemd...
I: Configuring dmsetup...
I: Configuring systemd-sysv...
I: Configuring init...
I: Configuring libc-bin...
I: Unpacking the base system...
I: Unpacking apt...
I: Unpacking apt-utils...
I: Unpacking busybox-initramfs...
I: Unpacking bzip2...
I: Unpacking console-setup...
I: Unpacking console-setup-linux...
I: Unpacking cpio...
I: Unpacking cron...
I: Unpacking debconf-i18n...
I: Unpacking dh-python...
I: Unpacking eject...
I: Unpacking file...
I: Unpacking gnupg...
I: Unpacking gpgv...
I: Unpacking init-system-helpers...
I: Unpacking initramfs-tools...
I: Unpacking initramfs-tools-bin...
I: Unpacking iputils-ping...
I: Unpacking isc-dhcp-client...
I: Unpacking isc-dhcp-common...
I: Unpacking kbd...
I: Unpacking keyboard-configuration...
I: Unpacking klibc-utils...
I: Unpacking kmod...
I: Unpacking language-pack-en...
I: Unpacking language-pack-en-base...
I: Unpacking less...
I: Unpacking libalgorithm-c3-perl...
I: Unpacking libapt-inst1.7:amd64...
I: Unpacking libapt-pkg4.16:amd64...
I: Unpacking libarchive-extract-perl...
I: Unpacking libatm1:amd64...
I: Unpacking libb-hooks-endofscope-perl...
I: Unpacking libb-hooks-op-check-perl...
I: Unpacking libbareword-filehandles-perl...
I: Unpacking libbsd0:amd64...
I: Unpacking libcgi-fast-perl...
I: Unpacking libcgi-pm-perl...
I: Unpacking libck-connector0:amd64...
I: Unpacking libclass-c3-perl...
I: Unpacking libclass-c3-xs-perl...
I: Unpacking libclass-method-modifiers-perl...
I: Unpacking libclass-xsaccessor-perl...
I: Unpacking libcpan-changes-perl...
I: Unpacking libcpan-meta-perl...
I: Unpacking libdata-optlist-perl...
I: Unpacking libdata-perl-perl...
I: Unpacking libdata-section-perl...
I: Unpacking libdbus-1-3:amd64...
I: Unpacking libdevel-caller-perl...
I: Unpacking libdevel-globaldestruction-perl...
I: Unpacking libdevel-lexalias-perl...
I: Unpacking libdns-export100...
I: Unpacking libdpkg-perl...
I: Unpacking libedit2:amd64...
I: Unpacking libencode-locale-perl...
I: Unpacking libestr0...
I: Unpacking libexporter-tiny-perl...
I: Unpacking libfcgi-perl...
I: Unpacking libffi6:amd64...
I: Unpacking libfile-fcntllock-perl...
I: Unpacking libfile-slurp-perl...
I: Unpacking libfribidi0:amd64...
I: Unpacking libgdbm3:amd64...
I: Unpacking libgetopt-long-descriptive-perl...
I: Unpacking libgmp10:amd64...
I: Unpacking libgnutls-deb0-28:amd64...
I: Unpacking libgnutls-openssl27:amd64...
I: Unpacking libgpm2:amd64...
I: Unpacking libgssapi-krb5-2:amd64...
I: Unpacking libhogweed4:amd64...
I: Unpacking libhtml-parser-perl...
I: Unpacking libhtml-tagset-perl...
I: Unpacking libhttp-date-perl...
I: Unpacking libhttp-message-perl...
I: Unpacking libimport-into-perl...
I: Unpacking libindirect-perl...
I: Unpacking libio-html-perl...
I: Unpacking libio-stringy-perl...
I: Unpacking libirs-export91...
I: Unpacking libisc-export95...
I: Unpacking libisccfg-export90...
I: Unpacking libjson-c2:amd64...
I: Unpacking libk5crypto3:amd64...
I: Unpacking libkeyutils1:amd64...
I: Unpacking libklibc...
I: Unpacking libkrb5-3:amd64...
I: Unpacking libkrb5support0:amd64...
I: Unpacking liblexical-sealrequirehints-perl...
I: Unpacking liblist-moreutils-perl...
I: Unpacking liblocale-gettext-perl...
I: Unpacking liblog-message-perl...
I: Unpacking liblog-message-simple-perl...
I: Unpacking liblwp-mediatypes-perl...
I: Unpacking libmagic1:amd64...
I: Unpacking libmodule-build-perl...
I: Unpacking libmodule-implementation-perl...
I: Unpacking libmodule-pluggable-perl...
I: Unpacking libmodule-runtime-perl...
I: Unpacking libmodule-signature-perl...
I: Unpacking libmoo-perl...
I: Unpacking libmoox-handlesvia-perl...
I: Unpacking libmpdec2:amd64...
I: Unpacking libmro-compat-perl...
I: Unpacking libmultidimensional-perl...
I: Unpacking 

[Touch-packages] [Bug 1514961] [NEW] lxc-test-checkpoint-restore doesn't clean up after itself and I am unable to re-run it

[Jeff Lane]

Public bug reported:

I ran lxc-test-checkpoint-restore and it failed.  So I decided to try
one additional attempt to verify the failure.  However now I am unable
to re-run the test because apparently the container already exists
(previous test did not clean up after itself), however, lxc list does
not show any running containers...

ubuntu@xwing:~$ lxc list
+--+---+--+--+---+---+
| NAME | STATE | IPV4 | IPV6 | EPHEMERAL | SNAPSHOTS |
+--+---+--+--+---+---+
+--+---+--+--+---+---+
ubuntu@xwing:~$ sudo lxc-test-checkpoint-restore
Container already exists
Failed creating container
ubuntu@xwing:~$ sudo lxc list
+--+---+--+--+---+---+
| NAME | STATE | IPV4 | IPV6 | EPHEMERAL | SNAPSHOTS |
+--+---+--+--+---+---+
+--+---+--+--+---+---+

** Affects: lxc (Ubuntu)
 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/1514961

Title:
  lxc-test-checkpoint-restore doesn't clean up after itself and I am
  unable to re-run it

Status in lxc package in Ubuntu:
  New

Bug description:
  I ran lxc-test-checkpoint-restore and it failed.  So I decided to try
  one additional attempt to verify the failure.  However now I am unable
  to re-run the test because apparently the container already exists
  (previous test did not clean up after itself), however, lxc list does
  not show any running containers...

  ubuntu@xwing:~$ lxc list
  +--+---+--+--+---+---+
  | NAME | STATE | IPV4 | IPV6 | EPHEMERAL | SNAPSHOTS |
  +--+---+--+--+---+---+
  +--+---+--+--+---+---+
  ubuntu@xwing:~$ sudo lxc-test-checkpoint-restore
  Container already exists
  Failed creating container
  ubuntu@xwing:~$ sudo lxc list
  +--+---+--+--+---+---+
  | NAME | STATE | IPV4 | IPV6 | EPHEMERAL | SNAPSHOTS |
  +--+---+--+--+---+---+
  +--+---+--+--+---+---+

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

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

[Sean Sosik-Hamor]

Confirming fixed on linux-image-4.2.0-18-generic, however it took about
5 seconds before the password-entry screen would take any input from the
keyboard.

-- 
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:
  Confirmed

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 1238194] Re: keyboard doesn't work to enter password with encrypted partitions ubuntu 13.10 saucy

[dreh23]

** Also affects: initramfs-tools
   Importance: Undecided
   Status: New

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

Title:
  keyboard doesn't work to enter password with encrypted partitions
  ubuntu 13.10 saucy

Status in initramfs-tools:
  New
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Precise:
  Fix Released
Status in initramfs-tools source package in Saucy:
  Fix Released

Bug description:
  [Justification]
  With the kernel in 13.10, some systems use a different USB host driver than 
previously.  Failing to include this driver in the initramfs causes regressions 
for users who need to interact with the system in early boot using a USB 
keyboard, such as users with an encrypted root filesystem.  Such systems are 
not bootable with this host driver missing.

  [Test case]
  1. On an affected system, reboot to a kernel from 13.04.
  2. Install the initramfs-tools package from -proposed.
  3. Reboot to the kernel from 13.10.
  4. Verify that you are able to type your passphrase at the prompt in the 
initramfs.

  [Regression potential]
  Minimal.  The update-initramfs script will ignore missing modules (such as 
the many other modules in the list which are built-ins), and the only change 
made is to copy the module into the initramfs: it will only be loaded in the 
initramfs if udev determines it's needed, just as it would load it after 
switching to the root filesystem.

  
  Is the same problem as here but in the new ubuntu 13.10 saucy 
https://bugs.launchpad.net/bugs/1066376

  I just can't use (i can install) a encrypted partition because when is
  time to introduce the password to unlock partition keyboard is not
  working.

  I don't know how to edit a bug to report it afects other version of
  ubuntu so i created this new bug...

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

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

[Touch-packages] [Bug 1513024] Re: Display-server randomly crashing in Ubuntu 15.10 after upgrade

[Launchpad Bug Tracker]

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

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

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

Title:
  Display-server randomly crashing in Ubuntu 15.10 after upgrade

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  On: Ubuntu 15.10

  After some random amount of time (at first correlated with actions
  such as switching between screens, max-/minimising windows, but now
  also sometimes not), the display server seems to die completely,
  restarting after a few seconds to dump me at the login screen.

  Getting errors like:

  $ dmesg
  ...
  [  239.809761] WARNING: CPU: 0 PID: 1879 at 
/build/linux-AxjFAn/linux-4.2.0/drivers/gpu/drm/i915/i915_gem.c:5269 
i915_gem_track_fb+0x129/0x140 [i915]()
  [  239.809762] WARN_ON(!(old->frontbuffer_bits & frontbuffer_bits))
  [  239.809763] Modules linked in:
  [  239.809765]  rfcomm msr acpi_call(OE) pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) vboxdrv(OE) openafs(POE) binfmt_misc bnep btusb btrtl btbcm 
btintel bluetooth uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core 
v4l2_common videodev media arc4 intel_rapl iosf_mbi x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
aesni_intel iwlmvm aes_x86_64 lrw gf128mul glue_helper mac80211 ablk_helper 
cryptd joydev input_leds snd_seq_midi serio_raw snd_seq_midi_event 
snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi thinkpad_acpi 
snd_rawmidi nvram iwlwifi snd_seq snd_hda_intel rtsx_pci_ms memstick 
snd_hda_codec lpc_ich cfg80211 snd_hda_core snd_hwdep snd_pcm mei_me 
ie31200_edac mei snd_seq_device edac_core shpchp snd_timer snd soundcore
  [  239.809798]  ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 mac_hid xt_hl ip6t_rt 
nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 
nf_log_common xt_LOG xt_limit xt_tcpudp xt_addrtype nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack ip6table_filter ip6_tables nf_conntrack_netbios_ns 
nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack 
iptable_filter ip_tables x_tables parport_pc ppdev lp parport autofs4 
rtsx_pci_sdmmc nouveau i915 mxm_wmi ttm e1000e i2c_algo_bit psmouse ahci 
drm_kms_helper libahci ptp rtsx_pci pps_core drm wmi video
  [  239.809822] CPU: 0 PID: 1879 Comm: Xorg Tainted: P   OE   
4.2.0-16-generic #19-Ubuntu
  [  239.809824] Hardware name: LENOVO 20AWS37E00/20AWS37E00, BIOS GLET77WW 
(2.31 ) 01/27/2015
  [  239.809825]   2aa5ef7b 8800a922fac8 
817e8c09
  [  239.809827]   8800a922fb20 8800a922fb08 
8107b3c6
  [  239.809829]  880425a47840 0010 8804256a 
8804256a
  [  239.809831] Call Trace:
  [  239.809836]  [] dump_stack+0x45/0x57
  [  239.809841]  [] warn_slowpath_common+0x86/0xc0
  [  239.809843]  [] warn_slowpath_fmt+0x55/0x70
  [  239.809853]  [] i915_gem_track_fb+0x129/0x140 [i915]
  [  239.809868]  [] intel_prepare_plane_fb+0xe7/0x1a0 [i915]
  [  239.809874]  [] 
drm_atomic_helper_prepare_planes+0x59/0xe0 [drm_kms_helper]
  [  239.809887]  [] ? drm_atomic_check_only+0x215/0x540 [drm]
  [  239.809901]  [] intel_atomic_commit+0x42/0x100 [i915]
  [  239.809910]  [] drm_atomic_commit+0x37/0x60 [drm]
  [  239.809915]  [] 
drm_atomic_helper_plane_set_property+0x87/0xc0 [drm_kms_helper]
  [  239.809922]  [] ? _object_find+0x69/0xa0 [drm]
  [  239.809930]  [] drm_mode_plane_set_obj_prop+0x2d/0x90 
[drm]
  [  239.809939]  [] 
drm_mode_obj_set_property_ioctl+0x1c6/0x270 [drm]
  [  239.809944]  [] drm_ioctl+0x125/0x610 [drm]
  [  239.809947]  [] ? fsnotify+0x316/0x4a0
  [  239.809954]  [] ? 
drm_mode_obj_get_properties_ioctl+0xa0/0xa0 [drm]
  [  239.809957]  [] do_vfs_ioctl+0x295/0x480
  [  239.809959]  [] ? __sb_end_write+0x35/0x70
  [  239.809961]  [] ? vfs_write+0x15a/0x1a0
  [  239.809963]  [] SyS_ioctl+0x79/0x90
  [  239.809966]  [] entry_SYSCALL_64_fastpath+0x16/0x75
  [  239.809967] ---[ end trace d4f1687d97169580 ]---
  [  240.634359] nouveau E[   PIBUS][:02:00.0] HUB0: 0x6013d4 0x5704 
(0x1c708200)
  [  240.634368] nouveau E[   PIBUS][:02:00.0] GPC0: 0x4188ac 0x0001 
(0x1c70822e)

  where the latter part also appears in the error log after xserver
  crashed, briefly visible before its restart.

  Any help is appreciated.

  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
  NonfreeKernelModules: openafs
  .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'
  

[Touch-packages] [Bug 1514942] [NEW] lxc-tests no runtime help (no man page, no --help, etc) for any of the lxc-tests tools

[Jeff Lane]

Public bug reported:

I'm investigating lxc-tests and have very little idea what they actually
do.  I had hoped to read a man page, or even just pass --help to them to
get some idea of what each is actually doing.

For example, lxc-test-apparmor, I know it does something with apparmor,
but no idea what.  And as they all seem to ignore --help, I have no idea
at all what it is actually doing.

Please document these tests so users actually understand what they are
testing.  Many tests pass, but some fail, and I really don't know why
they're failing, or what they're even doing in the first place to cause
a fail.

** Affects: lxc (Ubuntu)
 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/1514942

Title:
  lxc-tests no runtime help (no man page, no --help, etc) for any of the
  lxc-tests tools

Status in lxc package in Ubuntu:
  New

Bug description:
  I'm investigating lxc-tests and have very little idea what they
  actually do.  I had hoped to read a man page, or even just pass --help
  to them to get some idea of what each is actually doing.

  For example, lxc-test-apparmor, I know it does something with
  apparmor, but no idea what.  And as they all seem to ignore --help, I
  have no idea at all what it is actually doing.

  Please document these tests so users actually understand what they are
  testing.  Many tests pass, but some fail, and I really don't know why
  they're failing, or what they're even doing in the first place to
  cause a fail.

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

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

[Touch-packages] [Bug 1514557] Re: New upstream bugfix release 1.1.5 (LXC MRE)

[Hans Joachim Desserud]

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

Looks like this is the same as bug 1514558. (Maybe created twice by
Launchpad, it seems to do that sometimes.) I've taken the liberty of
marking this as a duplicate.

** This bug has been marked a duplicate of bug 1514558
   New upstream bugfix release 1.1.5 (LXC MRE)

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

Title:
  New upstream bugfix release 1.1.5 (LXC MRE)

Status in lxc package in Ubuntu:
  New

Bug description:
  We have released LXC 1.1.5 upstream:
  https://linuxcontainers.org/lxc/news

  This will be the second and probably last upstream bugfix release to
  hit vivid. The upstream changes are detailed at the URL above.

  The MRE was reviewed by Martin Pitt here:
  https://lists.ubuntu.com/archives/technical-
  board/2014-April/001869.html

  As for testing, this version went through both automated testing (all
  the tests present in lxc-tests + the python3 API tests) as well as
  manual testing done by myself, LXC contributors and LXC users who've
  been building the git stable branch for a while now.

  This release is being uploaded to:
   - xenial (dev release)
   - wily (SRU with MRE)
   - vivid (SRU with MRE)
   - trusty (backports)

  We're looking forward to this consistency which should make keeping
  track of and fixing bugs significantly easier for us.

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

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

[Touch-packages] [Bug 1514519] Re: Font in Terminal is incorrectly massive since recent update

[Lukáš Tinkl]

Browser is affected too

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

Title:
  Font in Terminal is incorrectly massive since recent update

Status in Canonical System Image:
  Confirmed
Status in logviewer:
  New
Status in Ubuntu Terminal App:
  New
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Last know good image: 166
  Changes on 167: 
http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-proposed/167.commitlog
  Landing request for Unity8/Mir: 
https://requests.ci-train.ubuntu.com/#/ticket/564

  After updating my Nexus 4 and Krillin over the weekend I notice the
  terminal now has really huge text. Even dialling down the font size in
  the app to 8pt results in huge unusable text.

  Before:- 
http://people.canonical.com/~alan/screenshots/device-2015-11-09-165137.png
  After:- 
http://people.canonical.com/~alan/screenshots/device-2015-11-09-165130.png

  With the same font size setting on both.

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

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

[Touch-packages] [Bug 1512919] Re: `dpkg --configure initramfs-tools` fails

[Michael Abrahams]

Yeah... same error is now affecting my kernel upgrade attempt.  :\

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

Title:
  `dpkg --configure initramfs-tools` fails

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I encountered a problem trying to install 4.3 kernel on Wily.  (This
  is not the bug I'm reporting.) http://pastebin.com/Lp6ZgWV0

  
  Investigating the complaint that initramfs-tools was not configured, I tried 
the command listed in the summary.

  > dpkg --configure initramfs-tools

  The result was this.  http://pastebin.com/X2Bg4YWs

  The line "ln: error: /proc/mounts: file is empty" seemed very strange,
  because /proc/mounts is a symlink to /proc/self/mounts, which is not
  empty.

  The error occurs even after purging all the 4.3 kernels, uninstalling
  all microcode and proprietary drivers.  Note the error is encountered
  when processing the 4.2 kernel, not 4.3.


  
  Release: 
  Description:Ubuntu 15.10
  Release:15.10

  
  initramfs-tools: 
Installed: 0.120ubuntu6
Candidate: 0.120ubuntu6
Version table:
   *** 0.120ubuntu6 0
  500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1512100] Re: Meizu MX4 (Arale r6=OTA7) - Blinking screen during the call if you remove the phone from your ear

[Pat McGowan]

Note the reason code is 3 which is proximity

Ken mentioned he received several message notifications during the call but had 
not looked at them.
Comment in u-s-c says 
Notifications don't turn on the screen directly, they rely on proximity events

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

Title:
  Meizu MX4 (Arale r6=OTA7) - Blinking screen during the call if you
  remove the phone from your ear

Status in Canonical System Image:
  Confirmed
Status in powerd package in Ubuntu:
  New
Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  I have a problem with my Meizu MX4 (Arale r6). 
  During a call if you remove the phone from your ear, sometimes (not always) 
the screen remains turned off. When you try to push the power button to wake up 
the screen, that starts blinking and it's not possible to hang up. The screen 
remains in that condition even after the end of the call.
  When it keeps blinking I try to hold the button down and in few seconds the 
screen turns black and the phone starts working again. Sometimes, instead, it 
starts working again by itself.

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

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

[Touch-packages] [Bug 1514990] [NEW] Primary screen not listed in Gnome color manager

[Francisco Cribari]

Public bug reported:

I am running Ubuntu Gnome 15.10 64 bit, kernel 4.2.0-18, Gnome 3.16,
colord 1.2.11 (fresh install). My computer's primary screen is not
listed in the Gnome color manager. It only lists my printers. colormgr
get-devices only return a list of my printers as well. A screenshot can
be viewed at

https://dl.dropboxusercontent.com/u/2171814/gnome-color-manager.png

cribari@darwin3:~$ colormgr get-devices
Object Path:   
/org/freedesktop/ColorManager/devices/cups_HP_LaserJet_P3010_Series
Owner: root
Created:   novembro 10 2015, 06:24:46 
Modified:  novembro 10 2015, 06:24:46 
Type:  printer
Enabled:   Yes
Embedded:  No
Model: HP LaserJet P3010 Series
Vendor:Hewlett Packard
Serial:BRBHB6F720
Format:ColorSpace.MediaType.Resolution
Scope: temp
Colorspace:gray
Device ID: cups-HP-LaserJet-P3010-Series
Profile 1: HP-LaserJet-P3010-Series-Gray..
Metadata:  OwnerCmdline=/usr/sbin/cupsd -l 

Object Path:   
/org/freedesktop/ColorManager/devices/cups_HP_LaserJet_Professional_P1606dn
Owner: root
Created:   novembro 10 2015, 06:24:46 
Modified:  novembro 10 2015, 06:24:46 
Type:  printer
Enabled:   Yes
Embedded:  No
Model: HP LaserJet Pro P1606dn
Vendor:Hewlett Packard
Serial:0RL136FTPR1a
Format:ColorSpace.MediaType.Resolution
Scope: temp
Colorspace:gray
Device ID: cups-HP-LaserJet-Professional-P1606dn
Profile 1: HP-LaserJet-Professional-P1606dn-Gray..
Metadata:  OwnerCmdline=/usr/sbin/cupsd -l 
cribari@darwin3:~$ colormgr get-devices-by-kind display
cribari@darwin3:~$ 

Hardware: DELL XPS 13 (2013 model) notebook, Intel GPU.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: colord 1.2.11-0ubuntu2
ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
Uname: Linux 4.2.0-18-generic x86_64
ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
Date: Tue Nov 10 17:01:18 2015
ExecutablePath: /usr/lib/colord/colord
InstallationDate: Installed on 2015-11-09 (1 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: colord
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug wily

** Attachment added: "Screenshot"
   
https://bugs.launchpad.net/bugs/1514990/+attachment/4516467/+files/gnome-color-manager.png

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

Title:
  Primary screen not listed in Gnome color manager

Status in colord package in Ubuntu:
  New

Bug description:
  I am running Ubuntu Gnome 15.10 64 bit, kernel 4.2.0-18, Gnome 3.16,
  colord 1.2.11 (fresh install). My computer's primary screen is not
  listed in the Gnome color manager. It only lists my printers. colormgr
  get-devices only return a list of my printers as well. A screenshot
  can be viewed at

  https://dl.dropboxusercontent.com/u/2171814/gnome-color-manager.png

  cribari@darwin3:~$ colormgr get-devices
  Object Path:   
/org/freedesktop/ColorManager/devices/cups_HP_LaserJet_P3010_Series
  Owner: root
  Created:   novembro 10 2015, 06:24:46 
  Modified:  novembro 10 2015, 06:24:46 
  Type:  printer
  Enabled:   Yes
  Embedded:  No
  Model: HP LaserJet P3010 Series
  Vendor:Hewlett Packard
  Serial:BRBHB6F720
  Format:ColorSpace.MediaType.Resolution
  Scope: temp
  Colorspace:gray
  Device ID: cups-HP-LaserJet-P3010-Series
  Profile 1: HP-LaserJet-P3010-Series-Gray..
  Metadata:  OwnerCmdline=/usr/sbin/cupsd -l 

  Object Path:   
/org/freedesktop/ColorManager/devices/cups_HP_LaserJet_Professional_P1606dn
  Owner: root
  Created:   novembro 10 2015, 06:24:46 
  Modified:  novembro 10 2015, 06:24:46 
  Type:  printer
  Enabled:   Yes
  Embedded:  No
  Model: HP LaserJet Pro P1606dn
  Vendor:Hewlett Packard
  Serial:0RL136FTPR1a
  Format:ColorSpace.MediaType.Resolution
  Scope: temp
  Colorspace:gray
  Device ID: cups-HP-LaserJet-Professional-P1606dn
  Profile 1: HP-LaserJet-Professional-P1606dn-Gray..
  Metadata:  OwnerCmdline=/usr/sbin/cupsd -l 
  cribari@darwin3:~$ colormgr get-devices-by-kind display
  cribari@darwin3:~$ 

  Hardware: DELL XPS 13 (2013 model) notebook, Intel GPU.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: colord 1.2.11-0ubuntu2
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  Date: Tue Nov 10 17:01:18 2015
  ExecutablePath: /usr/lib/colord/colord
  InstallationDate: Installed on 2015-11-09 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 

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

[Alex N.]

** Also affects: skype (Ubuntu)
   Importance: Undecided
   Status: 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 skype package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  Confirmed

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/skype/+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 1337873] Re: Precise, Trusty, Utopic - ifupdown initialization problems caused by race condition

[Launchpad Bug Tracker]

This bug was fixed in the package ifupdown - 0.7.54ubuntu2

---
ifupdown (0.7.54ubuntu2) xenial; urgency=medium

  * Per-interface hierarchical locking. Backported from Debian git head.
(LP: #1337873, Closes: #753755)

 -- Dariusz Gadomski   Thu, 10 Nov 2015
11:30:14 +0200

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

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

Title:
  Precise, Trusty, Utopic - ifupdown initialization problems caused by
  race condition

Status in ifupdown package in Ubuntu:
  Fix Released
Status in ifupdown source package in Precise:
  Confirmed
Status in ifupdown source package in Trusty:
  Confirmed
Status in ifupdown source package in Vivid:
  Confirmed
Status in ifupdown package in Debian:
  New

Bug description:
  [Impact]

   * Lack of proper synchronization in ifupdown causes a race condition
  resulting in occasional incorrect network interface initialization
  (e.g. in bonding case - wrong bonding settings, network unavailable
  because slave<->master interfaces initialization order was wrong

   * This is very annoying in case of large deployments (e.g. when
  bringing up 1000 machines it is almost guaranteed that at least a few
  of them will end up with network down).

   * It has been fixed by introducing hierarchical and per-interface
  locking mechanism ensuring the right order (along with the correct
  order in the /e/n/interfaces file) of initialization

  [Test Case]

   1. Create a VM with bonding configured with at least 2 slave interfaces.
   2. Reboot.
   3. If all interfaces are up - go to 2.

  [Regression Potential]

   * This change has been introduced upstream in Debian.
   * It does not require any config changes to existing installations.

  [Other Info]

  Original bug description:

  * please consider my bonding examples are using eth1 and eth2 as slave
   interfaces.

  ifupdown some race conditions explained bellow. ifenslave does not
  behave well with sysv networking and upstart network-interface scripts
  running together.

  
  case 1)
  (a) ifup eth0 (b) ifup -a for eth0
  -
  1-1. Lock ifstate.lock file.
    1-1. Wait for locking ifstate.lock
    file.
  1-2. Read ifstate file to check
   the target NIC.
  1-3. close(=release) ifstate.lock
   file.
  1-4. Judge that the target NIC
   isn't processed.
    1-2. Read ifstate file to check
     the target NIC.
    1-3. close(=release) ifstate.lock
     file.
    1-4. Judge that the target NIC
     isn't processed.
  2. Lock and update ifstate file.
     Release the lock.
    2. Lock and update ifstate file.
   Release the lock.
  !!!

  to be explained

  !!!
  case 2)
  (a) ifenslave of eth0  (b) ifenslave of eth0
  --
  3. Execute ifenslave of eth0.  3. Execute ifenslave of eth0.
  4. Link down the target NIC.
  5. Write NIC id to
     /sys/class/net/bond0/bonding
     /slaves then NIC gets up
    4. Link down the target NIC.
    5. Fails to write NIC id to
   /sys/class/net/bond0/bonding/
   slaves it is already written.
  !!!

  #

   My setup:

  root@provisioned:~# cat /etc/modprobe.d/bonding.conf
  alias bond0 bonding options bonding mode=1 arp_interval=2000

  Both, /etc/init.d/networking and upstart network-interface begin
  enabled.

   Beginning:

  root@provisioned:~# cat /etc/network/interfaces
  # /etc/network/interfaces

  auto lo
  iface lo inet loopback

  auto eth0
  iface eth0 inet dhcp

  I'm able to boot with both scripts (networking and network-interface
  enabled) with no problem. I can also boot with only "networking"
  script enabled:

  ---
  root@provisioned:~# initctl list | grep network
  network-interface stop/waiting
  networking start/running
  ---

  OR only the script "network-interface" enabled:

  ---
  root@provisioned:~# initctl list | grep network
  network-interface (eth2) start/running
  network-interface (lo) start/running
  network-interface (eth0) start/running
  network-interface (eth1) start/running
  ---

   Enabling bonding:

  Following ifenslave configuration example (/usr/share/doc/ifenslave/
  examples/two_hotplug_ethernet), my 

[Touch-packages] [Bug 1514960] Re: lxc-test-checkpoint-restore fails with no explanation why

[Tycho Andersen]

Hi,

What version of criu do you have installed? What's the host? Can you
show the output of /tmp/checkpont/{dump,restore}.log after the failure?

Thanks

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

Title:
  lxc-test-checkpoint-restore fails with no explanation why

Status in lxc package in Ubuntu:
  New

Bug description:
  Ran the ste lxc-test-checkpoint-restore and that failed, but there is
  no explanation in the output as to why it failed.  All the output I
  was able to create says it created the container fine, but then just
  failed for some reason:

  I: Configuring libsemanage1:amd64...
  I: Configuring libacl1:amd64...
  I: Configuring makedev...
  I: Configuring bsdutils...
  I: Configuring coreutils...
  I: Configuring tar...
  I: Configuring dpkg...
  I: Configuring sed...
  I: Configuring perl-base...
  I: Configuring grep...
  I: Configuring debconf...
  I: Configuring tzdata...
  I: Configuring gzip...
  I: Configuring dash...
  I: Configuring sysv-rc...
  I: Configuring libpam0g:amd64...
  I: Configuring libpam-modules-bin...
  I: Configuring bash...
  I: Configuring libpam-modules:amd64...
  I: Configuring libpam-runtime...
  I: Configuring passwd...
  I: Configuring login...
  I: Configuring adduser...
  I: Configuring libuuid1:amd64...
  I: Configuring libblkid1:amd64...
  I: Configuring libmount1:amd64...
  I: Configuring libcryptsetup4:amd64...
  I: Configuring mount...
  I: Configuring libfdisk1:amd64...
  I: Configuring initscripts...
  I: Configuring util-linux...
  I: Configuring e2fsprogs...
  I: Configuring procps...
  I: Configuring udev...
  I: Configuring systemd...
  I: Configuring dmsetup...
  I: Configuring systemd-sysv...
  I: Configuring init...
  I: Configuring libc-bin...
  I: Unpacking the base system...
  I: Unpacking apt...
  I: Unpacking apt-utils...
  I: Unpacking busybox-initramfs...
  I: Unpacking bzip2...
  I: Unpacking console-setup...
  I: Unpacking console-setup-linux...
  I: Unpacking cpio...
  I: Unpacking cron...
  I: Unpacking debconf-i18n...
  I: Unpacking dh-python...
  I: Unpacking eject...
  I: Unpacking file...
  I: Unpacking gnupg...
  I: Unpacking gpgv...
  I: Unpacking init-system-helpers...
  I: Unpacking initramfs-tools...
  I: Unpacking initramfs-tools-bin...
  I: Unpacking iputils-ping...
  I: Unpacking isc-dhcp-client...
  I: Unpacking isc-dhcp-common...
  I: Unpacking kbd...
  I: Unpacking keyboard-configuration...
  I: Unpacking klibc-utils...
  I: Unpacking kmod...
  I: Unpacking language-pack-en...
  I: Unpacking language-pack-en-base...
  I: Unpacking less...
  I: Unpacking libalgorithm-c3-perl...
  I: Unpacking libapt-inst1.7:amd64...
  I: Unpacking libapt-pkg4.16:amd64...
  I: Unpacking libarchive-extract-perl...
  I: Unpacking libatm1:amd64...
  I: Unpacking libb-hooks-endofscope-perl...
  I: Unpacking libb-hooks-op-check-perl...
  I: Unpacking libbareword-filehandles-perl...
  I: Unpacking libbsd0:amd64...
  I: Unpacking libcgi-fast-perl...
  I: Unpacking libcgi-pm-perl...
  I: Unpacking libck-connector0:amd64...
  I: Unpacking libclass-c3-perl...
  I: Unpacking libclass-c3-xs-perl...
  I: Unpacking libclass-method-modifiers-perl...
  I: Unpacking libclass-xsaccessor-perl...
  I: Unpacking libcpan-changes-perl...
  I: Unpacking libcpan-meta-perl...
  I: Unpacking libdata-optlist-perl...
  I: Unpacking libdata-perl-perl...
  I: Unpacking libdata-section-perl...
  I: Unpacking libdbus-1-3:amd64...
  I: Unpacking libdevel-caller-perl...
  I: Unpacking libdevel-globaldestruction-perl...
  I: Unpacking libdevel-lexalias-perl...
  I: Unpacking libdns-export100...
  I: Unpacking libdpkg-perl...
  I: Unpacking libedit2:amd64...
  I: Unpacking libencode-locale-perl...
  I: Unpacking libestr0...
  I: Unpacking libexporter-tiny-perl...
  I: Unpacking libfcgi-perl...
  I: Unpacking libffi6:amd64...
  I: Unpacking libfile-fcntllock-perl...
  I: Unpacking libfile-slurp-perl...
  I: Unpacking libfribidi0:amd64...
  I: Unpacking libgdbm3:amd64...
  I: Unpacking libgetopt-long-descriptive-perl...
  I: Unpacking libgmp10:amd64...
  I: Unpacking libgnutls-deb0-28:amd64...
  I: Unpacking libgnutls-openssl27:amd64...
  I: Unpacking libgpm2:amd64...
  I: Unpacking libgssapi-krb5-2:amd64...
  I: Unpacking libhogweed4:amd64...
  I: Unpacking libhtml-parser-perl...
  I: Unpacking libhtml-tagset-perl...
  I: Unpacking libhttp-date-perl...
  I: Unpacking libhttp-message-perl...
  I: Unpacking libimport-into-perl...
  I: Unpacking libindirect-perl...
  I: Unpacking libio-html-perl...
  I: Unpacking libio-stringy-perl...
  I: Unpacking libirs-export91...
  I: Unpacking libisc-export95...
  I: Unpacking libisccfg-export90...
  I: Unpacking libjson-c2:amd64...
  I: Unpacking libk5crypto3:amd64...
  I: Unpacking libkeyutils1:amd64...
  I: Unpacking libklibc...
  I: Unpacking libkrb5-3:amd64...
  I: Unpacking libkrb5support0:amd64...
 

[Touch-packages] [Bug 1227212] Re: Session logout takes too long

[Mina]

I'm on Ubuntu 14.04 64 bits. I have this same exact problem with a fast
machine. my logout time takes minimum 30 seconds.

this also affects shutting down and restart. It's clear that there's
some bug. ...actually when I press restart from the top-right menu, it
then shows a little window to either select "restart" or "shutdown" then
it doesn't wait for user input! it just goes on to restart immediately
(which takes the 30 seconds)

...sometimes the case beeps once! (the sound you should actually hear
when starting the computer). I'm so ready to debug but I need exact
steps.

...btw there was one time (just ONE) that it logged off in normal time.
took just a few seconds.

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

Title:
  Session logout takes too long

Status in upstart :
  Fix Released
Status in upstart package in Ubuntu:
  Fix Released

Bug description:
  This seems to be an issue confirmed across Ubuntu-flavors in Saucy at
  the moment: logging out of the session takes longer than expected
  (that is 5+seconds even on fast machines).

  It's not clear to me what exactly is going on, what component is the
  culprit. I started debugging xfce4-session (as I'm a Xubuntu team
  member) and then dug around lightdm, but without result. Maybe more
  able people can take a peek at this one...

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

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

[Touch-packages] [Bug 1460301] Re: [Dialer] Incoming call - no info which SIM card was called (dual SIM)

[Bill Filler]

I would think we should add a label in the incoming call notification.
Currently it says:
"
Calling from "

If multi sim's detected, it should say:
"
Calling from  on "

regarding comment #3
1) the recents call does show what sim the call was received on, have to left 
swipe and press "i" button
2) you can already edit the sim label to your liking. Go to System Settings-> 
Cellular -> Edit SIM Name



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

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

Title:
  [Dialer] Incoming call - no info which SIM card was called (dual SIM)

Status in Canonical System Image:
  New
Status in Ubuntu UX:
  Triaged
Status in telephony-service package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 14.10 (r22)

  (Don't know how to find a package version :/, but I checked for
  updates on 29-05-2015 and all apps are up to date)

  
  I have two SIM cards inserted into BQ Aquaris 4.5

  On incoming call I expect to see information if SIM1 or SIM2 was dialled by 
caller alongside caller ID.
  I see only caller ID.

  It may be useful if one of the SIM cards is in roaming, or when one of
  the SIMs is a company number while other is a private number.

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

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

[Touch-packages] [Bug 1514556] Re: With occlusion detection, apps stop responding when switching from another app.

[Launchpad Bug Tracker]

This bug was fixed in the package qtubuntu -
0.62+16.04.20151109-0ubuntu1

---
qtubuntu (0.62+16.04.20151109-0ubuntu1) xenial; urgency=medium

  [ Nick Dedekind ]
  * Reverted occlusion detection (lp#1514556) (LP: #1514556)

 -- Gerry Boland   Mon, 09 Nov 2015 22:43:18
+

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

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

Title:
  With occlusion detection, apps stop responding when switching from
  another app.

Status in Canonical System Image:
  In Progress
Status in qtmir package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Fix Released

Bug description:
  If you switch from one app to the next, and start scrolling around (eg
  in dash) very soon after switching, the app will sometimes stop
  rendering.

  Reproduce:
  1) Start an app (eg dialer) from dash
  2) wait a few seconds in dialer.
  3) Do a quick switch back to dash, and immediately start scrolling/swiping 
around.

  Expected:
  app behaves normally and responds to user input.

  Actual:
  sometimes the dash will stop responding for an undetermined amount of time, 
or until you interact with another part of the shell.

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

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

[Touch-packages] [Bug 1513985] Re: ffmpeg test idct8x8 (SIMPLE-ARM) fails on ARM32 when built with binutils from the trunk

[Andreas Cadhalpun]

A small clarification: the SIMPLE-ARM implementation can also be
selected at runtime, e.g. with the '-idct simplearm' option. That's
mainly useful for debugging purposes, though.

Regarding the binutils bug:
Attached testcase test.S doesn't require compiling ffmpeg, but simply:
$ gcc -g -c -o test.o test.S

Analyzing the difference of 'objdump -d test.o' between variants built
with working and broken binutils show that the working binutils always
always uses 'ldr.w' for ldr, while the broken version sometimes
optimizes this to 'movw', which is a correct alternative, but one time
to 'movt', which only sets half of the register.

** Attachment added: "testcase"
   
https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1513985/+attachment/4516473/+files/test.S

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

Title:
  ffmpeg test idct8x8 (SIMPLE-ARM) fails on ARM32 when built with
  binutils from the trunk

Status in binutils:
  Unknown
Status in binutils package in Ubuntu:
  Confirmed
Status in ffmpeg package in Ubuntu:
  Fix Released

Bug description:
  ffmpeg test idct8x8 (NEON) fails on ARM32 when built with binutils
  from the trunk

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

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

[Touch-packages] [Bug 1448566] Re: Ubuntu 15.04 - Macbook Pro Early 2015 (12, 1) Bluetooth disabled

[Joe Barnett]

this is also in the bluetooth (not bluetooth-next) repo:
https://git.kernel.org/cgit/linux/kernel/git/bluetooth/bluetooth.git/commit/?id=22f8e9dbf671a2f36d90d3d8723a2a0c5227fa4b
, would it be possible to include in the wily kernel as a SAUCE patch at
this point?

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

Title:
  Ubuntu 15.04 - Macbook Pro Early 2015 (12,1) Bluetooth disabled

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Fresh install of 15.04 on a Macbook Pro 12,1.

  I get no Bluetooth icon in the status bar, and in System Settings >
  Bluetooth, everything is greyed out (i.e., can't turn it on).

  
  $lsusb; dmesg | grep -i bluetooth; dmesg | grep -i firmware; rfkill list all; 
lsmod | grep bluetooth; hciconfig -a; uname -a

  Bus 002 Device 002: ID 05ac:8406 Apple, Inc.
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 05ac:0273 Apple, Inc.
  Bus 001 Device 004: ID 05ac:8290 Apple, Inc.
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  [ 32.369395] usb 1-3: Product: Bluetooth USB Host Controller
  [ 32.435743] input: Broadcom Corp. Bluetooth USB Host Controller as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/0003:05AC:8290.0006/input/input7
  [ 32.490662] hid-generic 0003:05AC:8290.0006: input,hidraw5: USB HID v1.11 
Keyboard [Broadcom Corp. Bluetooth USB Host Controller] on 
usb-:00:14.0-3/input0
  [ 32.490750] input: Broadcom Corp. Bluetooth USB Host Controller as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.1/0003:05AC:8290.0007/input/input8
  [ 32.490995] hid-generic 0003:05AC:8290.0007: input,hidraw6: USB HID v1.11 
Mouse [Broadcom Corp. Bluetooth USB Host Controller] on 
usb-:00:14.0-3/input1
  [ 34.866186] Bluetooth: Core ver 2.20
  [ 34.866205] Bluetooth: HCI device and connection manager initialized
  [ 34.866751] Bluetooth: HCI socket layer initialized
  [ 34.866754] Bluetooth: L2CAP socket layer initialized
  [ 34.866759] Bluetooth: SCO socket layer initialized
  [ 0.158493] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
  [ 0.168342] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain  [bus 
00-9b] only partially covers this bridge
  [ 35.003383] brcmfmac :03:00.0: Direct firmware load for 
brcm/brcmfmac43602-pcie.txt failed with error -2
  [ 35.290656] brcmf_c_preinit_dcmds: Firmware version = wl0: Mar 13 2015 
08:11:08 version 7.35.177.36 (r540934) FWID 01-e4dc15b
  0: phy0: Wireless LAN
   Soft blocked: no
   Hard blocked: no
  bluetooth 491520 1 btusb
  Linux hxn-laptop-linux 3.19.0-15-generic #15-Ubuntu SMP Thu Apr 16 23:32:37 
UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

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

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

[Touch-packages] [Bug 1515007] [NEW] isc-dhcp-server-ldap doesn't wait for the local slapd to start on boot

[Stephen Pape]

Public bug reported:

When using a local ldap server to manage dhcp, the slapd server is not
ready before the dhcp server tries to launch.

The result is that the service does not start on boot:

Nov 10 13:53:27 oldgateway1 dhcpd: Error: Cannot login into ldap server 
localhost:389: Can't contact LDAP server
Nov 10 13:53:27 oldgateway1 dhcpd: Configuration file errors encountered -- 
exiting

Once the slapd instance is running, the dhcp server can be successfully
launched.

Just test on wily, but I've had this problem for the past several Ubuntu
releases.

** Affects: isc-dhcp (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  isc-dhcp-server-ldap doesn't wait for the local slapd to start on boot

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  When using a local ldap server to manage dhcp, the slapd server is not
  ready before the dhcp server tries to launch.

  The result is that the service does not start on boot:

  Nov 10 13:53:27 oldgateway1 dhcpd: Error: Cannot login into ldap server 
localhost:389: Can't contact LDAP server
  Nov 10 13:53:27 oldgateway1 dhcpd: Configuration file errors encountered -- 
exiting

  Once the slapd instance is running, the dhcp server can be
  successfully launched.

  Just test on wily, but I've had this problem for the past several
  Ubuntu releases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1515007/+subscriptions

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

[Touch-packages] [Bug 1515012] [NEW] SIM not selected in header on incoming call

[Bill Filler]

Public bug reported:

latest rc-proposed
When you receive a call, the dialer shows the correct SIM label in the header 
but it is not selected. It should be selected (i.e. should have orange 
highlighting).

See attached screenshot

** Affects: canonical-devices-system-image
 Importance: High
 Assignee: Bill Filler (bfiller)
 Status: Confirmed

** Affects: dialer-app (Ubuntu)
 Importance: High
 Assignee: Gustavo Pichorim Boiko (boiko)
 Status: Confirmed

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

Title:
  SIM not selected in header on incoming call

Status in Canonical System Image:
  Confirmed
Status in dialer-app package in Ubuntu:
  Confirmed

Bug description:
  latest rc-proposed
  When you receive a call, the dialer shows the correct SIM label in the header 
but it is not selected. It should be selected (i.e. should have orange 
highlighting).

  See attached screenshot

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

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

[Touch-packages] [Bug 1515012] Re: SIM not selected in header on incoming call

[Bill Filler]

** Attachment added: "screenshot20151110_163004406.png"
   
https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1515012/+attachment/4516492/+files/screenshot20151110_163004406.png

** Changed in: dialer-app (Ubuntu)
 Assignee: (unassigned) => Gustavo Pichorim Boiko (boiko)

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

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

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

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

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

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

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

Title:
  SIM not selected in header on incoming call

Status in Canonical System Image:
  Confirmed
Status in dialer-app package in Ubuntu:
  Confirmed

Bug description:
  latest rc-proposed
  When you receive a call, the dialer shows the correct SIM label in the header 
but it is not selected. It should be selected (i.e. should have orange 
highlighting).

  See attached screenshot

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

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

[Touch-packages] [Bug 1375513] Re: [phone-app] bypass lock on shell possible

[Bill Filler]

** Changed in: dialer-app (Ubuntu)
   Status: New => Fix Released

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

Title:
  [phone-app] bypass lock on shell possible

Status in dialer-app:
  Fix Released
Status in Ubuntu UX:
  Fix Released
Status in dialer-app package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  from a private bug 1374773

  With the "Recent" option in the dialer in emergency call mode it's
  possible to get to the task switcher, app scope

  Steps to reproduce

  1. Set a passcode
  2. Swipe away welcome screen
  3. Tap 'emergency call' - phone opens
  4. Swipe "Recent" bottom edge up
  5. Swipe a contact left, choose message (screen locks, wait for osk)
  6. Swipe away osk
  7. Tap 'emergency call' - phone opens again to 'recent'
  8. Swipe left a person, tap person icon (screen locks)
  9. Tap 'emergency call'
  10. Swipe in from right of screen, observe muliple apps, and you can pick any 
of them.

  This bypasses screen lock.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dialer-app/+bug/1375513/+subscriptions

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

[Touch-packages] [Bug 1460301] Re: [Dialer] Incoming call - no info which SIM card was called (dual SIM)

[Bill Filler]

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

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

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

** Changed in: telephony-service (Ubuntu)
 Assignee: (unassigned) => Tiago Salem Herrmann (tiagosh)

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

** Changed in: telephony-service (Ubuntu)
   Importance: Undecided => High

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

Title:
  [Dialer] Incoming call - no info which SIM card was called (dual SIM)

Status in Canonical System Image:
  New
Status in Ubuntu UX:
  Triaged
Status in telephony-service package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 14.10 (r22)

  (Don't know how to find a package version :/, but I checked for
  updates on 29-05-2015 and all apps are up to date)

  
  I have two SIM cards inserted into BQ Aquaris 4.5

  On incoming call I expect to see information if SIM1 or SIM2 was dialled by 
caller alongside caller ID.
  I see only caller ID.

  It may be useful if one of the SIM cards is in roaming, or when one of
  the SIMs is a company number while other is a private number.

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

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

[Touch-packages] [Bug 1512100] Re: Meizu MX4 (Arale r6=OTA7) - Blinking screen during the call if you remove the phone from your ear

[Pat McGowan]

Powerd log from Ken

The signals are coming from 1:18 which is unity-system-compositor

** Attachment added: "powerd.log"
   
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512100/+attachment/4516414/+files/powerd.log

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

Title:
  Meizu MX4 (Arale r6=OTA7) - Blinking screen during the call if you
  remove the phone from your ear

Status in Canonical System Image:
  Confirmed
Status in powerd package in Ubuntu:
  New
Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  I have a problem with my Meizu MX4 (Arale r6). 
  During a call if you remove the phone from your ear, sometimes (not always) 
the screen remains turned off. When you try to push the power button to wake up 
the screen, that starts blinking and it's not possible to hang up. The screen 
remains in that condition even after the end of the call.
  When it keeps blinking I try to hold the button down and in few seconds the 
screen turns black and the phone starts working again. Sometimes, instead, it 
starts working again by itself.

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

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

[Touch-packages] [Bug 1514781] Re: package linux-image-extra-4.2.0-18-generic 4.2.0-18.22 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Launchpad Bug Tracker]

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

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

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

Title:
  package linux-image-extra-4.2.0-18-generic 4.2.0-18.22 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  I remedied the inability to boot by selecting linux-kernel-4.2.0-17 in
  GRUB.

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: linux-image-extra-4.2.0-18-generic 4.2.0-18.22
  ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
  Uname: Linux 4.2.0-17-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Date: Mon Nov  9 20:15:43 2015
  DuplicateSignature: 
package:linux-image-extra-4.2.0-18-generic:4.2.0-18.22:run-parts: 
/etc/kernel/postinst.d/initramfs-tools exited with return code 1
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2015-10-24 (16 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Hewlett-Packard HP EliteBook 8460p
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-17-generic 
root=UUID=637a9e85-b32a-4fcc-a79f-ca6f70c8dd05 ro quiet splash 
init=/sbin/upstart
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-29
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-4.2.0-18-generic 4.2.0-18.22 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/23/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SCF Ver. F.41
  dmi.board.name: 161C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 97.4D
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SCFVer.F.41:bd05/23/2013:svnHewlett-Packard:pnHPEliteBook8460p:pvrA0001D02:rvnHewlett-Packard:rn161C:rvrKBCVersion97.4D:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8460p
  dmi.product.version: A0001D02
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1514996] [NEW] Unit tests fail on Wily

[Alexandre Abreu]

Public bug reported:

FAIL!  : QmlTests::HistoryViewWide::test_search_highlight() Compared values are 
not the same
   Actual   (): 1
   Expected (): 3
   Loc: 
[/home/alex/dev/work/webapps/branches/webbrowser-app/fix-url-updates-for-manifest-webapps/tests/unittests/qml/tst_HistoryViewWide.qml(357)]

FAIL!  : QmlTests::TabsBar::test_context_menu_close() Uncaught exception: 
Cannot read property 'x' of undefined
   Loc: 
[/home/alex/dev/work/webapps/branches/webbrowser-app/fix-url-updates-for-manifest-webapps/tests/unittests/qml/tst_TabsBar.qml(94)]
FAIL!  : QmlTests::TabsBar::test_context_menu_new_tab() Uncaught exception: 
Cannot read property 'x' of undefined
   Loc: 
[/home/alex/dev/work/webapps/branches/webbrowser-app/fix-url-updates-for-manifest-webapps/tests/unittests/qml/tst_TabsBar.qml(94)]
FAIL!  : QmlTests::TabsBar::test_context_menu_reload() Uncaught exception: 
Cannot read property 'x' of undefined
   Loc: 
[/home/alex/dev/work/webapps/branches/webbrowser-app/fix-url-updates-for-manifest-webapps/tests/unittests/qml/tst_TabsBar.qml(94)]
PASS   : QmlTests::TabsBar::test_create_new_tab()
PASS   : QmlTests::TabsBar::test_drag_tab()
FAIL!  : QmlTests::TabsBar::test_menu_states_on_new_tab() Uncaught exception: 
Cannot read property 'enabled' of null
   Loc: 
[/home/alex/dev/work/webapps/branches/webbrowser-app/fix-url-updates-for-manifest-webapps/tests/unittests/qml/tst_TabsBar.qml(241)]
FAIL!  : QmlTests::TabsBar::test_menu_states_on_page() Uncaught exception: 
Cannot read property 'enabled' of null
   Loc: 
[/home/alex/dev/work/webapps/branches/webbrowser-app/fix-url-updates-for-manifest-webapps/tests/unittests/qml/tst_TabsBar.qml(252)]

** Affects: webbrowser-app (Ubuntu)
 Importance: Critical
 Assignee: Alexandre Abreu (abreu-alexandre)
 Status: In Progress

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

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

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

Title:
  Unit tests fail on Wily

Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  FAIL!  : QmlTests::HistoryViewWide::test_search_highlight() Compared values 
are not the same
 Actual   (): 1
 Expected (): 3
 Loc: 
[/home/alex/dev/work/webapps/branches/webbrowser-app/fix-url-updates-for-manifest-webapps/tests/unittests/qml/tst_HistoryViewWide.qml(357)]

  FAIL!  : QmlTests::TabsBar::test_context_menu_close() Uncaught exception: 
Cannot read property 'x' of undefined
 Loc: 
[/home/alex/dev/work/webapps/branches/webbrowser-app/fix-url-updates-for-manifest-webapps/tests/unittests/qml/tst_TabsBar.qml(94)]
  FAIL!  : QmlTests::TabsBar::test_context_menu_new_tab() Uncaught exception: 
Cannot read property 'x' of undefined
 Loc: 
[/home/alex/dev/work/webapps/branches/webbrowser-app/fix-url-updates-for-manifest-webapps/tests/unittests/qml/tst_TabsBar.qml(94)]
  FAIL!  : QmlTests::TabsBar::test_context_menu_reload() Uncaught exception: 
Cannot read property 'x' of undefined
 Loc: 
[/home/alex/dev/work/webapps/branches/webbrowser-app/fix-url-updates-for-manifest-webapps/tests/unittests/qml/tst_TabsBar.qml(94)]
  PASS   : QmlTests::TabsBar::test_create_new_tab()
  PASS   : QmlTests::TabsBar::test_drag_tab()
  FAIL!  : QmlTests::TabsBar::test_menu_states_on_new_tab() Uncaught exception: 
Cannot read property 'enabled' of null
 Loc: 
[/home/alex/dev/work/webapps/branches/webbrowser-app/fix-url-updates-for-manifest-webapps/tests/unittests/qml/tst_TabsBar.qml(241)]
  FAIL!  : QmlTests::TabsBar::test_menu_states_on_page() Uncaught exception: 
Cannot read property 'enabled' of null
 Loc: 
[/home/alex/dev/work/webapps/branches/webbrowser-app/fix-url-updates-for-manifest-webapps/tests/unittests/qml/tst_TabsBar.qml(252)]

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

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

[Touch-packages] [Bug 1514908] Re: add support for non-root X sessions

[Robert Ancell]

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

** This bug has been marked a duplicate of bug 1292324
   Support non-root X

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

Title:
  add support for non-root X sessions

Status in lightdm package in Ubuntu:
  New

Bug description:
  Xenial now has an xserver which supports running it as a normal user
  with the help of logind and libpam-systemd. Consider adding support
  for it like GDM has.

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

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

[Touch-packages] [Bug 1292324] Re: Support non-root X

[Robert Ancell]

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

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

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

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

Title:
  Support non-root X

Status in Light Display Manager:
  Triaged
Status in lightdm package in Ubuntu:
  Triaged

Bug description:
  Support running X as an unprivileged user.

  Currently X servers are run as root means a large complex process has
  access to services it might not need (i.e. potential security and
  stability problems). It would be nice to run each X server as either
  an unprivileged user or in the session they are being used in.

  Logind provides a system for sharing access to the display and input
  devices so this can be done - this seems like the most likely
  implementation of non-root X.

  For more information see Hans de Goede request:
  http://lists.freedesktop.org/archives/lightdm/2014-March/000539.html

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

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

[Touch-packages] [Bug 1514996] Re: Unit tests fail on Wily

[Alexandre Abreu]

It is a red herring, invalidating it

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

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

Title:
  Unit tests fail on Wily

Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  FAIL!  : QmlTests::HistoryViewWide::test_search_highlight() Compared values 
are not the same
 Actual   (): 1
 Expected (): 3
 Loc: 
[/home/alex/dev/work/webapps/branches/webbrowser-app/fix-url-updates-for-manifest-webapps/tests/unittests/qml/tst_HistoryViewWide.qml(357)]

  FAIL!  : QmlTests::TabsBar::test_context_menu_close() Uncaught exception: 
Cannot read property 'x' of undefined
 Loc: 
[/home/alex/dev/work/webapps/branches/webbrowser-app/fix-url-updates-for-manifest-webapps/tests/unittests/qml/tst_TabsBar.qml(94)]
  FAIL!  : QmlTests::TabsBar::test_context_menu_new_tab() Uncaught exception: 
Cannot read property 'x' of undefined
 Loc: 
[/home/alex/dev/work/webapps/branches/webbrowser-app/fix-url-updates-for-manifest-webapps/tests/unittests/qml/tst_TabsBar.qml(94)]
  FAIL!  : QmlTests::TabsBar::test_context_menu_reload() Uncaught exception: 
Cannot read property 'x' of undefined
 Loc: 
[/home/alex/dev/work/webapps/branches/webbrowser-app/fix-url-updates-for-manifest-webapps/tests/unittests/qml/tst_TabsBar.qml(94)]
  PASS   : QmlTests::TabsBar::test_create_new_tab()
  PASS   : QmlTests::TabsBar::test_drag_tab()
  FAIL!  : QmlTests::TabsBar::test_menu_states_on_new_tab() Uncaught exception: 
Cannot read property 'enabled' of null
 Loc: 
[/home/alex/dev/work/webapps/branches/webbrowser-app/fix-url-updates-for-manifest-webapps/tests/unittests/qml/tst_TabsBar.qml(241)]
  FAIL!  : QmlTests::TabsBar::test_menu_states_on_page() Uncaught exception: 
Cannot read property 'enabled' of null
 Loc: 
[/home/alex/dev/work/webapps/branches/webbrowser-app/fix-url-updates-for-manifest-webapps/tests/unittests/qml/tst_TabsBar.qml(252)]

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

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

[Touch-packages] [Bug 1514556] Re: With occlusion detection, apps stop responding when switching from another app.

[Jean-Baptiste Lallement]

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

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

Title:
  With occlusion detection, apps stop responding when switching from
  another app.

Status in Canonical System Image:
  Fix Committed
Status in qtmir package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Fix Released

Bug description:
  If you switch from one app to the next, and start scrolling around (eg
  in dash) very soon after switching, the app will sometimes stop
  rendering.

  Reproduce:
  1) Start an app (eg dialer) from dash
  2) wait a few seconds in dialer.
  3) Do a quick switch back to dash, and immediately start scrolling/swiping 
around.

  Expected:
  app behaves normally and responds to user input.

  Actual:
  sometimes the dash will stop responding for an undetermined amount of time, 
or until you interact with another part of the shell.

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

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

[Touch-packages] [Bug 1448657] Re: isc-dhcp-server: Can't create PID file /run/dhcp-server/dhcpd.pid: Permission denied

[Stephen Pape]

It looks like the line in /lib/systemd/system/isc-dhcp-server.service:

exec dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-
server/dhcpd.pid -cf $CONFIG_FILE $INTERFACES'

 is hardcoded and ignores the DHCPD_PID variable from /etc/default/isc-
dhcp-server.

  I think it should be:

exec dhcpd -user dhcpd -group dhcpd -f -4 -pf $DHCPD_PID -cf
$CONFIG_FILE $INTERFACES'

Then there are other issues with the file, like it always tries to run:

ExecStartPre=/bin/chown dhcpd:dhcpd /run/dhcp-server

regardless of the specified path. Also, if you don't set the variable in
/etc/default/isc-dhcp-server, no default is given and the service fails
to start.

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

Title:
  isc-dhcp-server: Can't create PID file /run/dhcp-server/dhcpd.pid:
  Permission denied

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  Just upgraded from 14-10 to 15-04, and now see the following in
  syslog:

  Apr 26 10:50:08 server kernel: [70470.960718] audit: type=1400 
audit(1430045408.725:8): apparmor="DENIED" operation="capable" 
profile="/usr/sbin/dhcpd" pid=8619 comm="dhcpd" capability=1  capname="dac_ove
  rride"
  Apr 26 10:50:08 server sh[8619]: Can't create PID file 
/run/dhcp-server/dhcpd.pid: Permission denied.

  Description:Ubuntu 15.04
  Release:15.04

  isc-dhcp-server:
Installed: 4.3.1-5ubuntu2

  --- 8x -

  # cat /etc/default/isc-dhcp-server

  # Defaults for isc-dhcp-server initscript
  # sourced by /etc/init.d/isc-dhcp-server
  # installed at /etc/default/isc-dhcp-server by the maintainer scripts

  #
  # This is a POSIX shell fragment
  #

  # Path to dhcpd's config file (default: /etc/dhcp/dhcpd.conf).
  #DHCPD_CONF=/etc/dhcp/dhcpd.conf

  # Path to dhcpd's PID file (default: /var/run/dhcpd.pid).
  #DHCPD_PID=/var/run/dhcpd.pid

  # Additional options to start dhcpd with.
  #   Don't use options -cf or -pf here; use DHCPD_CONF/ DHCPD_PID instead
  #OPTIONS=""

  # On what interfaces should the DHCP server (dhcpd) serve DHCP requests?
  #   Separate multiple interfaces with spaces, e.g. "eth0 eth1".
  INTERFACES=""

  --- 8x -

  # ls -la /var/run
  lrwxrwxrwx 1 root root 4 Oct 24  2013 /var/run -> /run

  # ls -la /run/dhcp-server/
  total 0
  drwxr-xr-x  2 dhcpd dhcpd   40 Apr 26 10:59 .
  drwxr-xr-x 34 root  root  1060 Apr 26 11:33 ..

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1448657/+subscriptions

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

[Touch-packages] [Bug 1512956] Re: Update IBus to 1.5.11 on Wily

[HeroCC]

** Summary changed:

- ibus update to 1.5.11 on wily
+ Update IBus to 1.5.11 on Wily

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

Title:
  Update IBus to 1.5.11 on Wily

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  newest release of Intellj IDEA does shows a warning:
  "IBus prior to 1.5.11 may cause input problems."

  that's why i request for an update of ibus to that version.

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

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