[Touch-packages] [Bug 1503554] Re: System freezes when playing videos or games.

[dvdmchl]

I have dist-upgraded to Ubuntu 15.10, the problem still persists.

With Nvidia binary drivers it freezes very often, with nouveau driver it
freezes not very often.

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

Title:
  System freezes when playing videos or games.

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  It has to do something with GPU as it happens only when using app that
  uses OpenGL.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  304.128  Wed Aug 26 10:38:05 
PDT 2015
   GCC version:  gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13)
  .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: Wed Oct  7 08:36:04 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.19.0-30-generic, x86_64: installed
   nvidia-304, 304.128, 3.19.0-30-generic, x86_64: installed
   vboxhost, 5.0.6, 3.19.0-30-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GT200 [GeForce GTX 280] [10de:05e1] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: XFX Pine Group Inc. Device [1682:2400]
  InstallationDate: Installed on 2015-10-03 (3 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Lsusb:
   Bus 001 Device 002: ID 18a5:0302 Verbatim, Ltd 32GB Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 045e:001e Microsoft Corp. IntelliMouse Explorer
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: XFX XFX nForce 790i Ultra 3-Way SLI
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic 
root=UUID=fe12b377-bee0-4361-b4e5-cdf0dd3d3f5c ro text
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/25/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: XFX nForce 790i Ultra 3-Way SLI
  dmi.board.vendor: XFX
  dmi.board.version: 1
  dmi.chassis.type: 3
  dmi.chassis.vendor: XFX
  dmi.chassis.version: XFX nForce 790i Ultra 3-Way SLI
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd06/25/2008:svnXFX:pnXFXnForce790iUltra3-WaySLI:pvr1:rvnXFX:rnXFXnForce790iUltra3-WaySLI:rvr1:cvnXFX:ct3:cvrXFXnForce790iUltra3-WaySLI:
  dmi.product.name: XFX nForce 790i Ultra 3-Way SLI
  dmi.product.version: 1
  dmi.sys.vendor: XFX
  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.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.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: Wed Oct  7 08:18:06 2015
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputMicrosoft Microsoft IntelliMouse® Explorer MOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.17.1-0ubuntu3.1

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

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

[Touch-packages] [Bug 1505368] Re: Bug reports after segmentation fault are never generated

[Karl-Philipp Richter]

I need to figure out [how to reproduce this
reliably](http://askubuntu.com/questions/684856/how-to-provoke-apport-
dialog-after-segmentation-fault-for-testing).

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

Title:
  Bug reports after segmentation fault are never generated

Status in apport package in Ubuntu:
  New

Bug description:
  After `apport` recognizes a segmentation fault it displays a dialog
  which allows to close or restart the application and contains a
  checkbox which offers the option to file a bug online. Even if the box
  is checked no online form to open a new bug report is opened in the
  browser.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: apport 2.17.2-0ubuntu1.5
  ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-31-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 12 21:29:18 2015
  InstallationDate: Installed on 2015-09-14 (27 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1446441] Re: /usr/bin/system-settings:6:qt_message_fatal:QMessageLogger::fatal:UbuntuClientIntegration::UbuntuClientIntegration:UbuntuMirClientIntegrationPlugin::create:loadInteg

[Timo Jyrinki]

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

** This bug has been marked a duplicate of bug 1422797
   Qt app aborts if it cannot connect to Mir - QtMir rejecting the connection

** This bug is no longer a duplicate of bug 1422797
   Qt app aborts if it cannot connect to Mir - QtMir rejecting the connection
** This bug has been marked a duplicate of bug 1365673
   
/usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene:6:qt_message_fatal:QMessageLogger::fatal:
 
UbuntuClientIntegration::UbuntuClientIntegration:UbuntuMirClientIntegrationPlugin::create:loadIntegration

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

Title:
  /usr/bin/system-
  
settings:6:qt_message_fatal:QMessageLogger::fatal:UbuntuClientIntegration::UbuntuClientIntegration:UbuntuMirClientIntegrationPlugin::create:loadIntegration

Status in qtubuntu package in Ubuntu:
  New

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

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

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

[Touch-packages] [Bug 1482868] Re: package qmlscene 5.4.1-1ubuntu5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Timo Jyrinki]

This sounds like a package manager / filesystem problem. As the
information says, one might need to force reinstallation of the package.

** Changed in: qtdeclarative-opensource-src (Ubuntu)
   Status: New => Incomplete

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

Title:
  package qmlscene 5.4.1-1ubuntu5 failed to install/upgrade: package is
  in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

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

Bug description:
  when upgrade from ubuntu 14.05 to 15.04 i get error

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: qmlscene 5.4.1-1ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-62.101-generic 3.13.11-ckt24
  Uname: Linux 3.13.0-62-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  Date: Sat Aug  8 19:49:45 2015
  DuplicateSignature: package:qmlscene:5.4.1-1ubuntu5:package is in a very bad 
inconsistent state; you should  reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2015-07-05 (33 days ago)
  InstallationMedia: ChaletOS 14.04 - Release amd64
  SourcePackage: qtdeclarative-opensource-src
  Title: package qmlscene 5.4.1-1ubuntu5 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1493532] Re: /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene:6:google::logging_fail:google::LogMessage::Fail:google::LogMessage::SendToLog:google::LogMessage::Flush:google::LogMess

[Timo Jyrinki]

** Package changed: qtdeclarative-opensource-src (Ubuntu) => ubuntu-
download-manager (Ubuntu)

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

Title:
  /usr/lib/arm-linux-
  
gnueabihf/qt5/bin/qmlscene:6:google::logging_fail:google::LogMessage::Fail:google::LogMessage::SendToLog:google::LogMessage::Flush:google::LogMessageFatal::~LogMessageFatal

Status in ubuntu-download-manager package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding qtdeclarative-opensource-src.  This problem was most
  recently seen with version 5.4.1-1ubuntu8, the problem page at
  https://errors.ubuntu.com/problem/35586438dd8bb25edb8b0e23120283d939b2473f
  contains more details.

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

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

[Touch-packages] [Bug 1493489] Re: /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene:6:qt_message_print:qt_message:QMessageLogger::fatal:deallocate:~QString

[Timo Jyrinki]

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

** This bug has been marked a duplicate of bug 1493530
   
/usr/bin/unity8-dash:6:qt_message_print:qt_message:QMessageLogger::fatal:deallocate:~QString

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

Title:
  /usr/lib/arm-linux-
  
gnueabihf/qt5/bin/qmlscene:6:qt_message_print:qt_message:QMessageLogger::fatal:deallocate:~QString

Status in qtdeclarative-opensource-src package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding qtdeclarative-opensource-src.  This problem was most
  recently seen with version 5.4.1-1ubuntu8, the problem page at
  https://errors.ubuntu.com/problem/6edb6d4b69ffcdb298874df071ddfb7f9644425f
  contains more details.

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

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

[Touch-packages] [Bug 1426822] Re: package base-files 7.2ubuntu5.2 failed to install/upgrade: unable to install `/etc/lsb-release.dpkg-new' as `/etc/lsb-release': Operation not permitted

[Launchpad Bug Tracker]

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

** Changed in: base-files (Ubuntu)
   Status: New => Confirmed

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

Title:
  package base-files 7.2ubuntu5.2 failed to install/upgrade: unable to
  install `/etc/lsb-release.dpkg-new' as `/etc/lsb-release': Operation
  not permitted

Status in base-files package in Ubuntu:
  Confirmed

Bug description:
  Just got a system error.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: base-files 7.2ubuntu5.2
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  AptOrdering:
   base-files: Install
   base-files: Configure
  Architecture: amd64
  Date: Fri Feb 20 12:54:21 2015
  Dependencies:
   
  DuplicateSignature: package:base-files:7.2ubuntu5.2:unable to install 
`/etc/lsb-release.dpkg-new' as `/etc/lsb-release': Operation not permitted
  ErrorMessage: unable to install `/etc/lsb-release.dpkg-new' as 
`/etc/lsb-release': Operation not permitted
  InstallationDate: Installed on 2014-03-09 (356 days ago)
  InstallationMedia: Linux Mint 16 "petra" - Release amd64 20131126
  SourcePackage: base-files
  Title: package base-files 7.2ubuntu5.2 failed to install/upgrade: unable to 
install `/etc/lsb-release.dpkg-new' as `/etc/lsb-release': Operation not 
permitted
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.legal:
   
  modified.conffile..etc.lsb.release:
   DISTRIB_ID=Ubuntu
   DISTRIB_RELEASE=17
   DISTRIB_CODENAME=qiana
   DISTRIB_DESCRIPTION="Linux Mint 17 Qiana"
  mtime.conffile..etc.legal: 2015-02-25T16:51:23.687562
  mtime.conffile..etc.lsb.release: 2014-11-21T12:02:32.158086
  mtime.conffile..etc.update.motd.d.10.help.text: 2015-02-25T16:51:38.018724

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1426822/+subscriptions

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

[Touch-packages] [Bug 1505507] Re: unity-scope-loader crashed with SIGSEGV in g_desktop_app_info_get_is_hidden()

[Apport retracing service]

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  unity-scope-loader crashed with SIGSEGV in
  g_desktop_app_info_get_is_hidden()

Status in libunity package in Ubuntu:
  New

Bug description:
  unity-scope-loader crashed with SIGSEGV in
  g_desktop_app_info_get_is_hidden()

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: libunity9 7.1.4+15.10.20151002-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Oct 13 08:27:37 2015
  ExecutablePath: /usr/bin/unity-scope-loader
  InstallationDate: Installed on 2015-10-10 (2 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151010)
  ProcCmdline: /usr/bin/unity-scope-loader applications/applications.scope 
applications/scopes.scope commands.scope
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=ru
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f6834f9d3d0 : 
movzbl 0xc0(%rdi),%eax
   PC (0x7f6834f9d3d0) ok
   source "0xc0(%rdi)" (0x00c0) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: libunity
  StacktraceTop:
   g_desktop_app_info_get_is_hidden () from 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/libgnome-menu-3.so.0
   ?? () from /usr/lib/libgnome-menu-3.so.0
   gmenu_tree_load_sync () from /usr/lib/libgnome-menu-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/unity/unity-scope-applications.so
  Title: unity-scope-loader crashed with SIGSEGV in 
g_desktop_app_info_get_is_hidden()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1504894] Re: Unity battery indicator missing in Ubuntu 15.04

[Jagadeesan A S]

i don't have external battery in my system (like removing and inserting
battery). I didn't get this laptop from normal vendor. In my college
very got this laptop for research purpose.

Model No. Acer Aspire E 15 Start, ES1-512-P1LP, intel Pentium quad core
processor N3540.

In windows i can see by battery status. But in Ubuntu Unity panel i'm
not able to see. I tried to reinstall unity once as well i google lot.

Then finally yesterday little i reinstalled indicator-power it's started
to showing..!!

Now another problem started, not able to shutdown/suspend/restart
showing something like "starting daemon" then got hanged. Everytime i
need to long press my power button to shutdown my laptop.

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

Title:
  Unity battery indicator missing in Ubuntu 15.04

Status in indicator-power package in Ubuntu:
  Incomplete

Bug description:
  In indicator panel Battery notification is missing... I tried Unity
  tweak tool also but not working.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: compiz-core 1:0.9.12.1+15.04.20150410.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-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: Sun Oct 11 12:20:27 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus: focaltech, 1.5, 3.19.0-30-generic, x86_64: installed
  ExecutablePath: /usr/bin/compiz
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:0936]
  InstallationDate: Installed on 2015-10-10 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Acer Aspire ES1-512
  ProcEnviron:
   PATH=(custom, no user)
   SHELL=/bin/bash
   LANG=en_IN
   LANGUAGE=en_IN:en
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic 
root=UUID=57ecf55c-91aa-459d-83b9-ead0c791604a ro quiet splash acpi=off 
vt.handoff=7
  SourcePackage: compiz
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/24/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.09a1
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Aspire ES1-512
  dmi.board.vendor: Acer
  dmi.board.version: V1.09a1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.09a1
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.09a1:bd10/24/2014:svnAcer:pnAspireES1-512:pvrV1.09a1:rvnAcer:rnAspireES1-512:rvrV1.09a1:cvnAcer:ct10:cvrV1.09a1:
  dmi.product.name: Aspire ES1-512
  dmi.product.version: V1.09a1
  dmi.sys.vendor: Acer
  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: Sun Oct 11 12:15:12 2015
  xserver.configfile: default
  xserver.devices:
   inputVGA Webcam   KEYBOARD, id 6
   inputAT Translated Set 2 keyboard KEYBOARD, id 7
   inputPS/2 Generic Mouse   MOUSE, id 8
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1110 
   vendor LGD
  xserver.version: 2:1.17.1-0ubuntu3.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1504894/+subscriptions

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

[Touch-packages] [Bug 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable

[Vinicius]

The whole procedure

vinicius@vinicius-iron:~/Downloads/epson$ sudo dpkg -i 
epson-inkjet-printer-201304w_1.0.0-1lsb3.2_amd64.deb 5
[sudo] password for vinicius: 
Selecting previously unselected package epson-inkjet-printer-201304w.
(Reading database ... 229356 files and directories currently installed.)
Preparing to unpack epson-inkjet-printer-201304w_1.0.0-1lsb3.2_amd64.deb ...
Unpacking epson-inkjet-printer-201304w (1.0.0-1lsb3.2) ...
dpkg: error processing archive 5 (--install):
 cannot access archive: No such file or directory
dpkg: dependency problems prevent configuration of epson-inkjet-printer-201304w:
 epson-inkjet-printer-201304w depends on lsb (>= 3.2); however:
  Package lsb is not installed.

dpkg: error processing package epson-inkjet-printer-201304w (--install):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 5
 epson-inkjet-printer-201304w
vinicius@vinicius-iron:~/Downloads/epson$ sudo apt-get -f install
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Correcting dependencies... Done
The following extra packages will be installed:
  alien at debugedit lib32z1 libjpeg62 libpod-plainer-perl librpmbuild3
  librpmsign1 lsb lsb-core lsb-cxx lsb-desktop lsb-graphics lsb-languages
  lsb-multimedia lsb-printing lsb-security ncurses-term pax rpm
Suggested packages:
  rpm-i18n elfutils rpmlint rpm2html
Recommended packages:
  libqt3-mt
The following NEW packages will be installed:
  alien at debugedit lib32z1 libjpeg62 libpod-plainer-perl librpmbuild3
  librpmsign1 lsb lsb-core lsb-cxx lsb-desktop lsb-graphics lsb-languages
  lsb-multimedia lsb-printing lsb-security ncurses-term pax rpm
0 upgraded, 20 newly installed, 0 to remove and 3 not upgraded.
1 not fully installed or removed.
Need to get 806 kB of archives.
After this operation, 4.719 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://br.archive.ubuntu.com/ubuntu/ vivid/main at amd64 3.1.16-1ubuntu1 
[37,6 kB]
Get:2 http://br.archive.ubuntu.com/ubuntu/ vivid/main ncurses-term all 
5.9+20140712-2ubuntu2 [248 kB]
Get:3 http://br.archive.ubuntu.com/ubuntu/ vivid/main pax amd64 1:20140703-2 
[78,8 kB]
Get:4 http://br.archive.ubuntu.com/ubuntu/ vivid/main librpmbuild3 amd64 
4.11.3-1.1 [58,0 kB]
Get:5 http://br.archive.ubuntu.com/ubuntu/ vivid/main librpmsign1 amd64 
4.11.3-1.1 [8.062 B]
Get:6 http://br.archive.ubuntu.com/ubuntu/ vivid/main debugedit amd64 
4.11.3-1.1 [15,8 kB]
Get:7 http://br.archive.ubuntu.com/ubuntu/ vivid/main rpm amd64 4.11.3-1.1 [115 
kB]
Get:8 http://br.archive.ubuntu.com/ubuntu/ vivid/main alien all 8.93 [54,0 kB]
Get:9 http://br.archive.ubuntu.com/ubuntu/ vivid/main lib32z1 amd64 
1:1.2.8.dfsg-2ubuntu1 [52,9 kB]
Get:10 http://br.archive.ubuntu.com/ubuntu/ vivid/main lsb-security amd64 
4.1+Debian11ubuntu8 [4.884 B]
Get:11 http://br.archive.ubuntu.com/ubuntu/ vivid/main lsb-core amd64 
4.1+Debian11ubuntu8 [27,4 kB]
Get:12 http://br.archive.ubuntu.com/ubuntu/ vivid/main lsb-graphics amd64 
4.1+Debian11ubuntu8 [2.894 B]
Get:13 http://br.archive.ubuntu.com/ubuntu/ vivid/main lsb-cxx amd64 
4.1+Debian11ubuntu8 [2.868 B]
Get:14 http://br.archive.ubuntu.com/ubuntu/ vivid/main lsb-multimedia amd64 
4.1+Debian11ubuntu8 [2.872 B]
Get:15 http://br.archive.ubuntu.com/ubuntu/ vivid/main libjpeg62 amd64 
6b1-4ubuntu1 [78,4 kB]
Get:16 http://br.archive.ubuntu.com/ubuntu/ vivid/main lsb-desktop amd64 
4.1+Debian11ubuntu8 [4.026 B]
Get:17 http://br.archive.ubuntu.com/ubuntu/ vivid/main lsb-printing amd64 
4.1+Debian11ubuntu8 [2.912 B]
Get:18 http://br.archive.ubuntu.com/ubuntu/ vivid/main libpod-plainer-perl all 
1.04-1 [5.928 B]
Get:19 http://br.archive.ubuntu.com/ubuntu/ vivid/main lsb-languages amd64 
4.1+Debian11ubuntu8 [2.900 B]
Get:20 http://br.archive.ubuntu.com/ubuntu/ vivid/main lsb all 
4.1+Debian11ubuntu8 [2.856 B]
Fetched 806 kB in 1s (413 kB/s)  
debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another 
process: Resource temporarily unavailable
Selecting previously unselected package at.
(Reading database ... 229393 files and directories currently installed.)
Preparing to unpack .../at_3.1.16-1ubuntu1_amd64.deb ...
Unpacking at (3.1.16-1ubuntu1) ...
Selecting previously unselected package ncurses-term.
Preparing to unpack .../ncurses-term_5.9+20140712-2ubuntu2_all.deb ...
Unpacking ncurses-term (5.9+20140712-2ubuntu2) ...
Selecting previously unselected package pax.
Preparing to unpack .../pax_1%3a20140703-2_amd64.deb ...
Unpacking pax (1:20140703-2) ...
Selecting previously unselected package librpmbuild3.
Preparing to unpack .../librpmbuild3_4.11.3-1.1_amd64.deb ...
Unpacking librpmbuild3 (4.11.3-1.1) ...
Selecting previously unselected package librpmsign1.
Preparing to unpack .../librpmsign1_4.11.3-1.1_amd64.deb ...
Unpacking librpmsign1 (4.11.3-1.1) ...
Selecting previously unselected package debugedit.
Preparing to unpack .../debugedit_4.11.3-1.1_amd64.deb ...
Unpacking debugedi

[Touch-packages] [Bug 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable

[Vinicius]

It happened to me when trying to install my Epson XP214 printer. I
downloaded epson's official drivers

epson-inkjet-printer-escpr_1.6.0-1lsb3.2_amd64.deb
iscan_2.30.1-1~usb0.1.ltdl7_amd64.deb
iscan-data_1.36.0-1_all.deb
iscan-network-nt_1.1.1-1_amd64.deb

but epson-inkjet-printer-escpr_1.6.0-1lsb3.2_amd64.deb failed due to lsb
being misconfigured. I tryed to repair it but it breaks everytime after
a simple "apt-get install lsb" on 15.04

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

Title:
  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

Status in Ambasa:
  New
Status in Debconf:
  New
Status in aptdaemon package in Ubuntu:
  Confirmed
Status in debconf package in Ubuntu:
  Triaged

Bug description:
  Upgrading packages that use debconf sometimes fail with the following
  error:

  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

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

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

[Touch-packages] [Bug 1418213] Re: Scrolling is sometimes going in the other direction than wanted

[Daniel van Vugt]

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

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

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

Title:
  Scrolling is sometimes going in the other direction than wanted

Status in Mir:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Nexus 4 Mako vivid. r.89 but notice since a year ago.

  This happens in every app, dash or things where you can scroll down or up.
  Not sure if its related to the sensitivity of the screen.

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

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

[Touch-packages] [Bug 1505461] [NEW] Expose LED color setting

[Dennis O'Flaherty]

Public bug reported:

It would be nice you could change the color the LED blinks when you have
notifications.  If not through a GUI, at least through gsettings.

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

** Branch linked: lp:~doflah/unity8/led_color

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

Title:
  Expose LED color setting

Status in unity8 package in Ubuntu:
  New

Bug description:
  It would be nice you could change the color the LED blinks when you
  have notifications.  If not through a GUI, at least through gsettings.

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

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

[Rodrigo]

Happens to me too,  Ubuntu 15.04 on lenovo t450s

After the kernel update to 3.19.0-30, the keyboard doesn't work, if I
select the  3.19.0-28 it works.

-- 
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 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/ubuntu/+source/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 1505447] [NEW] /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene:11:getenv:qEnvironmentVariableIsEmpty:QThreadPrivate::createEventDispatcher:QThreadPrivate::start:start_thread

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding qtdeclarative-opensource-src.  This problem was most recently
seen with version 5.4.1-1ubuntu10, the problem page at
https://errors.ubuntu.com/problem/8f6f06b586f1f71e35bb497ab187ce5acd91ed81
contains more details.

** Affects: qtdeclarative-opensource-src (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: vivid

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

Title:
  /usr/lib/arm-linux-
  
gnueabihf/qt5/bin/qmlscene:11:getenv:qEnvironmentVariableIsEmpty:QThreadPrivate::createEventDispatcher:QThreadPrivate::start:start_thread

Status in qtdeclarative-opensource-src package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding qtdeclarative-opensource-src.  This problem was most
  recently seen with version 5.4.1-1ubuntu10, the problem page at
  https://errors.ubuntu.com/problem/8f6f06b586f1f71e35bb497ab187ce5acd91ed81
  contains more details.

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

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

[Touch-packages] [Bug 1505216] Re: Display freezes randomly

[Christopher M. Penalver]

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

As per http://support.lenovo.com/us/en/products/laptops-and-
netbooks/lenovo-g-series-laptops/lenovo-g580-notebook an update to your
computer's buggy and outdated BIOS is available (5ECN96WW). If you
update to this following https://help.ubuntu.com/community/BIOSUpdate
does it change anything?

If it doesn't, could you please both specify what happened, and provide the 
output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

For more on BIOS updates and linux, please see
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette
.

Please note your current BIOS is already in the Bug Description, so
posting this on the old BIOS would not be helpful. As well, you don't
have to create a new bug report.

Once the BIOS is updated, if the problem is still reproducible, and the
information above is provided, then please mark this report Status
Confirmed. Otherwise, please mark this as Invalid.

Thank you for your understanding.

** Summary changed:

- Bug 1277245
+ Display freezes randomly

** Tags added: bios-5ecn96ww

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

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

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

Title:
  Display freezes randomly

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Using the nvidia card with prime-select nvidia, display freezes
  randomly. Recovery possible by ctrlaltF1 altF7.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.93  Wed Aug 19 16:49:15 
PDT 2015
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04)
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 12 14:17:07 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3901]
   NVIDIA Corporation GF108M [GeForce GT 630M] [10de:0de9] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo Device [17aa:3901]
  InstallationDate: Installed on 2014-12-11 (304 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: LENOVO Lenovo G580
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic 
root=UUID=d7e6e24a-be6e-41ac-a885-7ae1d3fc2319 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/06/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5ECN33WW(V2.03)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Product Name
  dmi.board.vendor: LENOVO
  dmi.board.version: Mainboard version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G580
  dmi.modalias: 
dmi:bvnLENOVO:bvr5ECN33WW(V2.03):bd06/06/2012:svnLENOVO:pnLenovoG580:pvrLenovoG580:rvnLENOVO:rnProductName:rvrMainboardversion:cvnLENOVO:ct10:cvrLenovoG580:
  dmi.product.name: Lenovo G580
  dmi.product.version: Lenovo G580
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.6
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Oct 12 14:16:14 2015
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 826 
   vendor LGD
  xserver.version: 2:1.15.1-0ubuntu2.7

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

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

[Touch-packages] [Bug 1505368] Re: Bug reports after segmentation fault are never generated

[Lysenko Denis]

Tested in 15.04, not confirmed. Tested with "apport-bug -w" in terminal
on calculator, it's collected data and opened for me browser to create
report with all data.

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

Title:
  Bug reports after segmentation fault are never generated

Status in apport package in Ubuntu:
  New

Bug description:
  After `apport` recognizes a segmentation fault it displays a dialog
  which allows to close or restart the application and contains a
  checkbox which offers the option to file a bug online. Even if the box
  is checked no online form to open a new bug report is opened in the
  browser.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: apport 2.17.2-0ubuntu1.5
  ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-31-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 12 21:29:18 2015
  InstallationDate: Installed on 2015-09-14 (27 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1504894] Re: Unity battery indicator missing in Ubuntu 15.04

[Sebastien Bacher]

do you have a battery in your computer? could you get a upower --dump
log? is indicator-power-service in the processes list?

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

Title:
  Unity battery indicator missing in Ubuntu 15.04

Status in indicator-power package in Ubuntu:
  Incomplete

Bug description:
  In indicator panel Battery notification is missing... I tried Unity
  tweak tool also but not working.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: compiz-core 1:0.9.12.1+15.04.20150410.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-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: Sun Oct 11 12:20:27 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus: focaltech, 1.5, 3.19.0-30-generic, x86_64: installed
  ExecutablePath: /usr/bin/compiz
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:0936]
  InstallationDate: Installed on 2015-10-10 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Acer Aspire ES1-512
  ProcEnviron:
   PATH=(custom, no user)
   SHELL=/bin/bash
   LANG=en_IN
   LANGUAGE=en_IN:en
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic 
root=UUID=57ecf55c-91aa-459d-83b9-ead0c791604a ro quiet splash acpi=off 
vt.handoff=7
  SourcePackage: compiz
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/24/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.09a1
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Aspire ES1-512
  dmi.board.vendor: Acer
  dmi.board.version: V1.09a1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.09a1
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.09a1:bd10/24/2014:svnAcer:pnAspireES1-512:pvrV1.09a1:rvnAcer:rnAspireES1-512:rvrV1.09a1:cvnAcer:ct10:cvrV1.09a1:
  dmi.product.name: Aspire ES1-512
  dmi.product.version: V1.09a1
  dmi.sys.vendor: Acer
  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: Sun Oct 11 12:15:12 2015
  xserver.configfile: default
  xserver.devices:
   inputVGA Webcam   KEYBOARD, id 6
   inputAT Translated Set 2 keyboard KEYBOARD, id 7
   inputPS/2 Generic Mouse   MOUSE, id 8
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1110 
   vendor LGD
  xserver.version: 2:1.17.1-0ubuntu3.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1504894/+subscriptions

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

[Touch-packages] [Bug 1505227] Re: Secondary monitor does not turn on using a KVM switch

[Brian Murray]

** Tags added: trusty

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

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

Title:
  Secondary monitor does not turn on using a KVM switch

Status in xorg package in Ubuntu:
  New

Bug description:
  Using a StarTech.com switch (SV231DPDDUA), the secondary monitor does
  not turn on.

  Both DELL TFT-s are with displayport connected to the StarTech.com
  switch.

  The computers have 2 displayport outputs. 4 displayports go into the
  switch to switch 2 monitors at once.

  If computer boots up, it does not recognize the second monitor. The second 
monitor is recognized under
  windows, but it cannot be turned on: driver failure.

  
  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor 
DRAM Controller (rev 09)
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen 
Core processor Graphics Controller (rev 09)
  00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family 
USB xHCI Host Controller (rev 04)
  00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series 
Chipset Family MEI Controller #1 (rev 04)
  00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network 
Connection (rev 04)
  00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family 
USB Enhanced Host Controller #2 (rev 04)
  00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family 
High Definition Audio Controller (rev 04)
  00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family 
USB Enhanced Host Controller #1 (rev 04)
  00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a4)
  00:1f.0 ISA bridge: Intel Corporation Q77 Express Chipset LPC Controller (rev 
04)
  00:1f.2 SATA controller: Intel Corporation 7 Series/C210 Series Chipset 
Family 6-port SATA Controller [AHCI mode] (rev 04)
  00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus 
Controller (rev 04)

  uname -a

  Linux  3.13.0-65-generic #106-Ubuntu SMP Fri Oct 2 22:08:27 UTC
  2015 x86_64 x86_64 x86_64 GNU/Linux

  Ubuntu 14.04 LTS

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

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

[Touch-packages] [Bug 1505227] [NEW] Secondary monitor does not turn on using a KVM switch

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Using a StarTech.com switch (SV231DPDDUA), the secondary monitor does
not turn on.

Both DELL TFT-s are with displayport connected to the StarTech.com
switch.

The computers have 2 displayport outputs. 4 displayports go into the
switch to switch 2 monitors at once.

If computer boots up, it does not recognize the second monitor. The second 
monitor is recognized under
windows, but it cannot be turned on: driver failure.


00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor 
DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen 
Core processor Graphics Controller (rev 09)
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family 
USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series 
Chipset Family MEI Controller #1 (rev 04)
00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network 
Connection (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family 
USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family 
High Definition Audio Controller (rev 04)
00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family 
USB Enhanced Host Controller #1 (rev 04)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a4)
00:1f.0 ISA bridge: Intel Corporation Q77 Express Chipset LPC Controller (rev 
04)
00:1f.2 SATA controller: Intel Corporation 7 Series/C210 Series Chipset Family 
6-port SATA Controller [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus 
Controller (rev 04)

uname -a

Linux  3.13.0-65-generic #106-Ubuntu SMP Fri Oct 2 22:08:27 UTC 2015
x86_64 x86_64 x86_64 GNU/Linux

Ubuntu 14.04 LTS

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


** Tags: bot-comment trusty
-- 
Secondary monitor does not turn on using a KVM switch
https://bugs.launchpad.net/bugs/1505227
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

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

[Touch-packages] [Bug 1505390] Re: apport-kde crashed with SIGSEGV in QPropertyAnimation::updateState()

[Apport retracing service]

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  apport-kde crashed with SIGSEGV in QPropertyAnimation::updateState()

Status in apport package in Ubuntu:
  New

Bug description:
  I was using NM to share a lan connection when apport crashed.  I would
  be surprised if they are related.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: apport-kde 2.19.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: KDE
  Date: Mon Oct 12 12:58:28 2015
  ExecutablePath: /usr/share/apport/apport-kde
  InstallationDate: Installed on 2015-10-01 (10 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150930)
  InterpreterPath: /usr/bin/python3.4
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-kde
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f6f15671ddb:cmp0x8(%rbx),%ebp
   PC (0x7f6f15671ddb) ok
   source "0x8(%rbx)" (0xb0008) not located in a known VMA region (needed 
readable region)!
   destination "%ebp" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: apport
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   QPropertyAnimation::updateState(QAbstractAnimation::State, 
QAbstractAnimation::State) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   QAbstractAnimation::stop() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   QPropertyAnimation::~QPropertyAnimation() () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/styles/breeze.so
  Title: apport-kde crashed with SIGSEGV in QPropertyAnimation::updateState()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1427566] Re: [Clock][UX] Add timers functionality

[Bartosz Kosiorek]

** Changed in: ubuntu-clock-app
   Status: Triaged => Incomplete

** Changed in: ubuntu-clock-app
   Importance: Wishlist => Low

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

Title:
  [Clock][UX] Add timers functionality

Status in Indicator Date and Time:
  New
Status in Ubuntu Clock App:
  Incomplete
Status in Ubuntu UX:
  Triaged
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  I'm greatly missing timers from the clock app. In Android I use them
  all the time for fixed time periods (laundry/bread/cooking/tea is
  ready, etc.), and it's rather inconvenient to have to create a
  gazillion alarms at a fixed time for these.

  I'm not sure why they got removed, but could we have them back please?
  Thanks for considering!

  Before we will implement this we need to fix:
  https://bugs.launchpad.net/ubuntu/+source/ubuntu-clock-app/+bug/1480200

  -- Additional feature request,
  I have a UX request when setting the timer. In addition to setting the time 
remaining until it expires (as you'd expect), I'd like to also switch to the 
ability to setting the clock time that I want it to expire. This would be very 
similar to setting an alarm of course, but the alarm setting UI is geared 
towards persistent alarms, not ephemeral ones.

  Example use case: there's a one-off thing I need to do at 2pm. I could
  set an alarm for 2pm by adding a new alarm, and then going in and
  deleting the alarm after it has rung but this is tedious.
  Alternatively I could calculate the time until 2pm myself and then
  quickly set a timer for that length of time. This way there is no
  alarm to delete after it has expired. I'd like to just go to the timer
  section and add a timer to ring at 2pm by toggling to an "ETA" display
  instead of "time remaining" and setting it from there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/1427566/+subscriptions

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

[Touch-packages] [Bug 1266675] Re: newusers error adding more than one user

[Tobias Verbeke]

(still) present on Ubuntu 14.04.3 LTS

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

Title:
  newusers error adding more than one user

Status in shadow package in Ubuntu:
  Confirmed

Bug description:
  1)
  mcegielka@ftp-geodezja:~$ lsb_release -rd
  Description:Ubuntu 13.10
  Release:13.10

  2)
  mcegielka@ftp-geodezja:~$ sudo apt-cache policy passwd
  passwd:
Installed: 1:4.1.5.1-1ubuntu6
Candidate: 1:4.1.5.1-1ubuntu6

  3)
  Expected: add system users from file given as argument:

  mcegielka@ftp-geodezja:~$ cat testusers.txt
  test1:a:::test user 1,,,:/home/test1:/bin/bash
  test2:b:::test user 2,,,:/home/test2:/bin/bash

  4)
  Instead: errors:

  mcegielka@ftp-geodezja:~$ sudo newusers testusers.txt
  *** Error in `newusers': free(): invalid next size (fast): 0x09319cd0 ***
  *** Error in `newusers': malloc(): memory corruption: 0x09319d00 ***

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: passwd 1:4.1.5.1-1ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic i686
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: i386
  Date: Tue Jan  7 09:04:11 2014
  InstallationDate: Installed on 2014-01-07 (0 days ago)
  InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release i386 
(20131016)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: shadow
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1504690] Re: www.playkeepout.com/ doesn't work (WebGL game)

[Olivier Tilloy]

And it works well too in chromium on my desktop.
I’m not seeing anything relevant in the logs, the only info we ever get is:

[JS] (http://www.playkeepout.com/js/three.min.js:9)
THREE.WebGLRenderer

Note that examples at http://threejs.org/examples/ work well in
webbrowser-app, both on desktop and on a phone (krillin). The issue
seems to be specific with keepout.

Overriding the UA string does not improve things.

I’ve noted that on a phone, the initial screen is black, but if I rotate
to portrait and back to landscape, some rendering happens and the sound
effects start playing, although the game doesn’t become playable.

Needs more investigation.

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

** Also affects: oxide
   Importance: Undecided
   Status: New

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

Title:
  www.playkeepout.com/ doesn't work (WebGL game)

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

Bug description:
  http://www.playkeepout.com/ webgl game doesn't work (on desktop or
  phone). the content is partially loaded. i see the UI but the game
  content is black

  works perfectly well on chrome stable

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

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

[Touch-packages] [Bug 1503572] Re: Crypt Login freeze and random system freeze

[David]

I can also confirm this bug on a 2015 ThinkPad x1 carbon.

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

Title:
  Crypt Login freeze and random system freeze

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  After last two kernel updates in Ubuntu 15.04 (so 30 and 28) I am 
experiencing the random screen freeze as well as there is no way to write my 
Crypt password the first time I boot (through graphical interface). My 
workaround is that when Crypt login screen appears I hold power button to 
reboot the machine (Lenovo T450s) which then gives me terminal login through 
Crypt. Additional regression appears as whole system freeze at random moments 
(can be in browser or in OpenOffice). What is even more worrying is that I have 
dmesg full of errors ([drm:gen8_irq_handler [i915_bpo]] *ERROR* The master 
control interrupt lied (SDE)!
  ) - something that was not there before.

  Also it does not matter if I have external monitor connected over HDMI
  or not, it does not matter if I have USB devices connected or not, the
  Crypt login freeze is repeatable 100%, but I do not know how to get
  logs from that boot or what to look.

  [9.155615] ACPI: Video Device [VID] (multi-head: yes  rom: no  post: no)
  [9.155987] input: Video Bus as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input15
  [9.158359] device-mapper: multipath: version 1.7.0 loaded
  [9.158591] [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control 
interrupt lied (SDE)!
  [9.158772] [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control 
interrupt lied (SDE)!
  ...
  [9.280656] [drm] GMBUS [i915 gmbus dpb] timed out, falling back to bit 
banging on pin 5
  [9.297274] [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control 
interrupt lied (SDE)!
  [9.297445] snd_hda_intel :00:03.0: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915_bpo])
  [9.297453] [drm] Initialized i915_bpo 1.6.0 20150522 for :00:02.0 on 
minor 0
  [9.298242] fbcon: inteldrmfb (fb0) is primary device
  [   10.275607] [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control 
interrupt lied (SDE)!
  ..
  [   10.337233] Console: switching to colour frame buffer device 240x67
  [   10.343218] i915_bpo :00:02.0: fb0: inteldrmfb frame buffer device
  [   10.343218] i915_bpo :00:02.0: registered panic notifier
  [   10.356167] Adding 8077308k swap on /dev/mapper/ubuntu--vg-swap_1.  
Priority:-1 extents:1 across:8077308k SSFS
  ...
  [   32.521174] [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control 
interrupt lied (SDE)!
  [   32.521473] [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control 
interrupt lied (SDE)!
  [   32.536040] [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control 
interrupt lied (SDE)!

  lshw for display:
  *-display
   description: VGA compatible controller
   product: Broadwell-U Integrated Graphics
   vendor: Intel Corporation
   physical id: 2
   bus info: pci@:00:02.0
   version: 09
   width: 64 bits
   clock: 33MHz
   capabilities: msi pm vga_controller bus_master cap_list rom
   configuration: driver=i915_bpo latency=0
   resources: irq:49 memory:e000-e0ff 
memory:d000-dfff ioport:3000(size=64)

  3.19.0-30-generic #34-Ubuntu

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

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

[Touch-packages] [Bug 1505368] [NEW] Bug reports after segmentation fault are never generated

[Karl-Philipp Richter]

Public bug reported:

After `apport` recognizes a segmentation fault it displays a dialog
which allows to close or restart the application and contains a checkbox
which offers the option to file a bug online. Even if the box is checked
no online form to open a new bug report is opened in the browser.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: apport 2.17.2-0ubuntu1.5
ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
Uname: Linux 3.19.0-31-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.5
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Oct 12 21:29:18 2015
InstallationDate: Installed on 2015-09-14 (27 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug vivid

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

Title:
  Bug reports after segmentation fault are never generated

Status in apport package in Ubuntu:
  New

Bug description:
  After `apport` recognizes a segmentation fault it displays a dialog
  which allows to close or restart the application and contains a
  checkbox which offers the option to file a bug online. Even if the box
  is checked no online form to open a new bug report is opened in the
  browser.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: apport 2.17.2-0ubuntu1.5
  ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-31-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 12 21:29:18 2015
  InstallationDate: Installed on 2015-09-14 (27 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1505340] Re: Crashes too often

[Olivier Tilloy]

Can you please specify on what device / system configuration that is?
Are there relevant crash files in /var/crash that you could attach to this bug? 
Without further information, there’s not much we can investigate. Thanks in 
advance!

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

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

Title:
  Crashes too often

Status in webbrowser-app package in Ubuntu:
  Incomplete

Bug description:
  As the object: it (browser and webapps as facebook) crashes every 3
  seconds, it is unusable.

  lsb_release: ubuntu 15.04

  package version: 0.23+15.04.20150817-0ubuntu1

  thanks in advance

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

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

[Touch-packages] [Bug 1504506] Re: FTBFS due to failing unit tests

[Bug Watch Updater]

** Changed in: telepathy-glib (Debian)
   Status: Confirmed => Fix Released

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

Title:
  FTBFS due to failing unit tests

Status in telepathy-glib package in Ubuntu:
  In Progress
Status in telepathy-glib package in Debian:
  Fix Released

Bug description:
  In the wily test-rebuild [1], telepathy-glib seems to fail on all
  arches due to failures in the unit tests. Log:

  make  check-TESTS check-local
  make[5]: Entering directory '/«PKGBUILDDIR»/tests/dbus'
  make[6]: Entering directory '/«PKGBUILDDIR»/tests/dbus'
  (...)
  ../../build-aux/test-driver: line 107: 25472 Trace/breakpoint trap   (core 
dumped) "$@" > $log_file 2>&1
  FAIL: test-account
  (...)
  ../../build-aux/test-driver: line 107: 21815 Trace/breakpoint trap   "$@" > 
$log_file 2>&1
  FAIL: test-cm
  (...)
  ../../build-aux/test-driver: line 107: 26166 Trace/breakpoint trap   (core 
dumped) "$@" > $log_file 2>&1
  FAIL: test-contact-lists
  ../../build-aux/test-driver: line 107: 26173 Trace/breakpoint trap   (core 
dumped) "$@" > $log_file 2>&1
  FAIL: test-contact-list-client
  (...)
  etc.

  [1] http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-
  rebuild-20151001-wily.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-glib/+bug/1504506/+subscriptions

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

[Touch-packages] [Bug 1368365] Re: Bluetooth pairing not working on all devices

[greenBird]

It is one of the essential function of a phone connecting to a car
headset. With my Mecedes Benz the pairing starts. Ask me for the couple
code. I put '' to pair the system. It seams to be connecting at the
phone. For some seconds at the phones display I can read 'connect'. But,
the car system still waiting for some additional data and disconnect
finally the phone.

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

Title:
  Bluetooth pairing not working on all devices

Status in indicator-bluetooth package in Ubuntu:
  Confirmed

Bug description:
  Nexus 4 with MultiROM, utopic r235

  There ar, a few bluetooth devices that still don't work together with
  Ubuntu Touch. These devices work perfectly well when booting the phone
  as Android. The devices that fails to connect for me are BlueAnt
  Supertooth 3
  (http://www.myblueant.com/shop/us/products/st3.php#related) and My
  Volvo car bluetooth system, both with Bluetooth version 2.0
  specifications.

  With BlueAnt Ubuntu can discover the unit and attempts to connect,
  opening a pairing dialogue with the digits "". Confirming the pin
  code (which is correct) doesn't do anything, my Ubuntu phone is not
  recognized by BlueAnt and won't show as a connected device in the
  phone's bluetooth settings, but shows up under "Connect other device
  followed by ..." The bluetooth indicator, however, shows as connected.

  With My Volvo Car, pairing works differently. The bluetooth system in
  the car searches for devices and shows "Nexus 4" and then prompts me
  to connect with a 4-digit pin code, but the Ubuntu phone doesn't react
  at all and after a while the car system says that it failed to
  connect.

  Oh, adding to that, the indicator remains "lit" even after turning
  BlueAnt off and toggling Bluetooth off/on in the phone settings.

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

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

[Touch-packages] [Bug 1368365] Re: Bluetooth pairing not working on all devices

[Launchpad Bug Tracker]

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

** Changed in: indicator-bluetooth (Ubuntu)
   Status: New => Confirmed

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

Title:
  Bluetooth pairing not working on all devices

Status in indicator-bluetooth package in Ubuntu:
  Confirmed

Bug description:
  Nexus 4 with MultiROM, utopic r235

  There ar, a few bluetooth devices that still don't work together with
  Ubuntu Touch. These devices work perfectly well when booting the phone
  as Android. The devices that fails to connect for me are BlueAnt
  Supertooth 3
  (http://www.myblueant.com/shop/us/products/st3.php#related) and My
  Volvo car bluetooth system, both with Bluetooth version 2.0
  specifications.

  With BlueAnt Ubuntu can discover the unit and attempts to connect,
  opening a pairing dialogue with the digits "". Confirming the pin
  code (which is correct) doesn't do anything, my Ubuntu phone is not
  recognized by BlueAnt and won't show as a connected device in the
  phone's bluetooth settings, but shows up under "Connect other device
  followed by ..." The bluetooth indicator, however, shows as connected.

  With My Volvo Car, pairing works differently. The bluetooth system in
  the car searches for devices and shows "Nexus 4" and then prompts me
  to connect with a 4-digit pin code, but the Ubuntu phone doesn't react
  at all and after a while the car system says that it failed to
  connect.

  Oh, adding to that, the indicator remains "lit" even after turning
  BlueAnt off and toggling Bluetooth off/on in the phone settings.

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

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

[Touch-packages] [Bug 1504894] Re: Unity battery indicator missing in Ubuntu 15.04

[Jagadeesan A S]

I mean in system settings -> power : i selected show battery status in
the menu bar "When battery is charging/in use" but in panel i didn't see
power indicator.

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

Title:
  Unity battery indicator missing in Ubuntu 15.04

Status in indicator-power package in Ubuntu:
  Incomplete

Bug description:
  In indicator panel Battery notification is missing... I tried Unity
  tweak tool also but not working.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: compiz-core 1:0.9.12.1+15.04.20150410.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-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: Sun Oct 11 12:20:27 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus: focaltech, 1.5, 3.19.0-30-generic, x86_64: installed
  ExecutablePath: /usr/bin/compiz
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:0936]
  InstallationDate: Installed on 2015-10-10 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Acer Aspire ES1-512
  ProcEnviron:
   PATH=(custom, no user)
   SHELL=/bin/bash
   LANG=en_IN
   LANGUAGE=en_IN:en
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic 
root=UUID=57ecf55c-91aa-459d-83b9-ead0c791604a ro quiet splash acpi=off 
vt.handoff=7
  SourcePackage: compiz
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/24/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.09a1
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Aspire ES1-512
  dmi.board.vendor: Acer
  dmi.board.version: V1.09a1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.09a1
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.09a1:bd10/24/2014:svnAcer:pnAspireES1-512:pvrV1.09a1:rvnAcer:rnAspireES1-512:rvrV1.09a1:cvnAcer:ct10:cvrV1.09a1:
  dmi.product.name: Aspire ES1-512
  dmi.product.version: V1.09a1
  dmi.sys.vendor: Acer
  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: Sun Oct 11 12:15:12 2015
  xserver.configfile: default
  xserver.devices:
   inputVGA Webcam   KEYBOARD, id 6
   inputAT Translated Set 2 keyboard KEYBOARD, id 7
   inputPS/2 Generic Mouse   MOUSE, id 8
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1110 
   vendor LGD
  xserver.version: 2:1.17.1-0ubuntu3.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1504894/+subscriptions

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

[Touch-packages] [Bug 1505340] [NEW] Crashes too often

[Andrea Zagli]

Public bug reported:

As the object: it (browser and webapps as facebook) crashes every 3
seconds, it is unusable.

lsb_release: ubuntu 15.04

package version: 0.23+15.04.20150817-0ubuntu1

thanks in advance

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

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

Title:
  Crashes too often

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  As the object: it (browser and webapps as facebook) crashes every 3
  seconds, it is unusable.

  lsb_release: ubuntu 15.04

  package version: 0.23+15.04.20150817-0ubuntu1

  thanks in advance

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

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

[Touch-packages] [Bug 798414] Re: update-initramfs should produce a more helpful error when there isn't enough free space

[Justin]

I had this problem about a month ago and deleted old kernels and it
worked fine at that point. I had tried a few different flavors before I
settled on Lubuntu so I thought that might be why I had the older kernel
versions floating around. Here I am with the same problem again.

Filesystem   Size  Used Avail Use% Mounted on
/dev/mapper/ubuntu--vg-root  228G   14G  204G   7% /
none 4.0K 0  4.0K   0% /sys/fs/cgroup
udev 479M  8.0K  479M   1% /dev
tmpfs 99M  1.5M   98M   2% /run
none 5.0M 0  5.0M   0% /run/lock
none 493M   76K  493M   1% /run/shm
none 100M   24K  100M   1% /run/user
/dev/sda2237M  232M 0 100% /boot

sda2 is chock full again so I checked my kernels:

i   linux-image-3.16.0-44-generic   - Linux kernel image for version 3.16.0 on 3
i   linux-image-3.16.0-45-generic   - Linux kernel image for version 3.16.0 on 3
i   linux-image-3.16.0-46-generic   - Linux kernel image for version 3.16.0 on 3
i   linux-image-3.16.0-48-generic   - Linux kernel image for version 3.16.0 on 3
i   linux-image-3.16.0-49-generic   - Linux kernel image for version 3.16.0 on 3
i   linux-image-3.16.0-50-generic   - Linux kernel image for version 3.16.0 on 3
i   linux-image-extra-3.16.0-44-gen - Linux kernel extra modules for version 3.1
i   linux-image-extra-3.16.0-45-gen - Linux kernel extra modules for version 3.1
i   linux-image-extra-3.16.0-46-gen - Linux kernel extra modules for version 3.1
i   linux-image-extra-3.16.0-48-gen - Linux kernel extra modules for version 3.1
i   linux-image-extra-3.16.0-49-gen - Linux kernel extra modules for version 3.1

I am confident that I had deleted all but 49 and 50 last time but here
they are again. I'll admit that I am a relative noob on linux so the
problem may be with the user! I am posting this information primarily to
try and help. I'm going to delete the extra kernels again and see how it
goes.

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

Title:
  update-initramfs should produce a more helpful error when there isn't
  enough  free space

Status in initramfs-tools:
  Confirmed
Status in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: initramfs-tools

  When generating a new initramfs there is no check for available free
  space, subsequently its possible for update-initramfs to fail due to a
  lack of free space.  This is resulting in package installation
  failures for initramfs-tools.  For example:

  Setting up initramfs-tools (0.98.8ubuntu3) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools ...
  update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic

  gzip: stdout: No space left on device
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic
  dpkg: error processing initramfs-tools (--configure):
   subprocess installed post-installation script returned error exit status 1

  WORKAROUND:

  Remove unused kernels using computer janitor or manually free space on
  your partition containing the /boot file system.

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

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

[Touch-packages] [Bug 1505335] [NEW] package hicolor-icon-theme 0.14-0ubuntu1 failed to install/upgrade: triggers looping, abandoned

[carlos palma]

Public bug reported:

crash on a 15.04 to 15.10 (Beta 2) upgrade

ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: hicolor-icon-theme 0.14-0ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
Uname: Linux 3.19.0-31-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.5
Architecture: amd64
Date: Mon Oct 12 20:12:01 2015
Dependencies:
 
DuplicateSignature: package:hicolor-icon-theme:0.14-0ubuntu1:triggers looping, 
abandoned
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2014-05-19 (511 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.2ubuntu4
 apt  1.0.10.2ubuntu1
SourcePackage: hicolor-icon-theme
Title: package hicolor-icon-theme 0.14-0ubuntu1 failed to install/upgrade: 
triggers looping, abandoned
UpgradeStatus: Upgraded to wily on 2015-10-12 (0 days ago)

** Affects: hicolor-icon-theme (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package wily

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

Title:
  package hicolor-icon-theme 0.14-0ubuntu1 failed to install/upgrade:
  triggers looping, abandoned

Status in hicolor-icon-theme package in Ubuntu:
  New

Bug description:
  crash on a 15.04 to 15.10 (Beta 2) upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: hicolor-icon-theme 0.14-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-31-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  Date: Mon Oct 12 20:12:01 2015
  Dependencies:
   
  DuplicateSignature: package:hicolor-icon-theme:0.14-0ubuntu1:triggers 
looping, abandoned
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2014-05-19 (511 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu4
   apt  1.0.10.2ubuntu1
  SourcePackage: hicolor-icon-theme
  Title: package hicolor-icon-theme 0.14-0ubuntu1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to wily on 2015-10-12 (0 days ago)

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

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

[Touch-packages] [Bug 1505335] Re: package hicolor-icon-theme 0.14-0ubuntu1 failed to install/upgrade: triggers looping, abandoned

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package hicolor-icon-theme 0.14-0ubuntu1 failed to install/upgrade:
  triggers looping, abandoned

Status in hicolor-icon-theme package in Ubuntu:
  New

Bug description:
  crash on a 15.04 to 15.10 (Beta 2) upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: hicolor-icon-theme 0.14-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-31-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  Date: Mon Oct 12 20:12:01 2015
  Dependencies:
   
  DuplicateSignature: package:hicolor-icon-theme:0.14-0ubuntu1:triggers 
looping, abandoned
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2014-05-19 (511 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu4
   apt  1.0.10.2ubuntu1
  SourcePackage: hicolor-icon-theme
  Title: package hicolor-icon-theme 0.14-0ubuntu1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to wily on 2015-10-12 (0 days ago)

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

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

[Touch-packages] [Bug 1505328] Re: Cups SSL is vulernable to POODLE

[Thomas Ward]

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-3566

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

Title:
  Cups SSL is vulernable to POODLE

Status in cups package in Ubuntu:
  New

Bug description:
  On 12.04 and 14.04 if you enable cups ssl you are vulnerable to
  poodle, and there does not appear to be any way to mitigate it in Cups
  config.

  Ubuntu 14.04 - 
https://www.ssllabs.com/ssltest/analyze.html?d=190.35.213.162.lcy-02.canonistack.canonical.com&hideResults=on
  Ubuntu 12.04 - 
https://www.ssllabs.com/ssltest/analyze.html?d=191.35.213.162.lcy-02.canonistack.canonical.com&hideResults=on

  Fixed in wily - 
https://www.ssllabs.com/ssltest/analyze.html?d=192.35.213.162.lcy-02.canonistack.canonical.com&hideResults=on
  Upstream fix - https://www.cups.org/str.php?L4476

  Should we disable ssvl3 in the 12.04/14.04 cups by default and
  backport the option to turn it back on?

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

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

[Touch-packages] [Bug 1505328] [NEW] Cups SSL is vulernable to POODLE

[Bryan Quigley]

*** This bug is a security vulnerability ***

Public security bug reported:

On 12.04 and 14.04 if you enable cups ssl you are vulnerable to poodle,
and there does not appear to be any way to mitigate it in Cups config.

Ubuntu 14.04 - 
https://www.ssllabs.com/ssltest/analyze.html?d=190.35.213.162.lcy-02.canonistack.canonical.com&hideResults=on
Ubuntu 12.04 - 
https://www.ssllabs.com/ssltest/analyze.html?d=191.35.213.162.lcy-02.canonistack.canonical.com&hideResults=on

Fixed in wily - 
https://www.ssllabs.com/ssltest/analyze.html?d=192.35.213.162.lcy-02.canonistack.canonical.com&hideResults=on
Upstream fix - https://www.cups.org/str.php?L4476

Should we disable ssvl3 in the 12.04/14.04 cups by default and backport
the option to turn it back on?

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

** Information type changed from Public to Public Security

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

Title:
  Cups SSL is vulernable to POODLE

Status in cups package in Ubuntu:
  New

Bug description:
  On 12.04 and 14.04 if you enable cups ssl you are vulnerable to
  poodle, and there does not appear to be any way to mitigate it in Cups
  config.

  Ubuntu 14.04 - 
https://www.ssllabs.com/ssltest/analyze.html?d=190.35.213.162.lcy-02.canonistack.canonical.com&hideResults=on
  Ubuntu 12.04 - 
https://www.ssllabs.com/ssltest/analyze.html?d=191.35.213.162.lcy-02.canonistack.canonical.com&hideResults=on

  Fixed in wily - 
https://www.ssllabs.com/ssltest/analyze.html?d=192.35.213.162.lcy-02.canonistack.canonical.com&hideResults=on
  Upstream fix - https://www.cups.org/str.php?L4476

  Should we disable ssvl3 in the 12.04/14.04 cups by default and
  backport the option to turn it back on?

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

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

[Touch-packages] [Bug 1504894] Re: Unity battery indicator missing in Ubuntu 15.04

[Sebastien Bacher]

what do you mean "it's showing but not working properly"? what is it
doing?

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

Title:
  Unity battery indicator missing in Ubuntu 15.04

Status in indicator-power package in Ubuntu:
  Incomplete

Bug description:
  In indicator panel Battery notification is missing... I tried Unity
  tweak tool also but not working.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: compiz-core 1:0.9.12.1+15.04.20150410.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-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: Sun Oct 11 12:20:27 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus: focaltech, 1.5, 3.19.0-30-generic, x86_64: installed
  ExecutablePath: /usr/bin/compiz
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:0936]
  InstallationDate: Installed on 2015-10-10 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Acer Aspire ES1-512
  ProcEnviron:
   PATH=(custom, no user)
   SHELL=/bin/bash
   LANG=en_IN
   LANGUAGE=en_IN:en
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic 
root=UUID=57ecf55c-91aa-459d-83b9-ead0c791604a ro quiet splash acpi=off 
vt.handoff=7
  SourcePackage: compiz
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/24/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.09a1
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Aspire ES1-512
  dmi.board.vendor: Acer
  dmi.board.version: V1.09a1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.09a1
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.09a1:bd10/24/2014:svnAcer:pnAspireES1-512:pvrV1.09a1:rvnAcer:rnAspireES1-512:rvrV1.09a1:cvnAcer:ct10:cvrV1.09a1:
  dmi.product.name: Aspire ES1-512
  dmi.product.version: V1.09a1
  dmi.sys.vendor: Acer
  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: Sun Oct 11 12:15:12 2015
  xserver.configfile: default
  xserver.devices:
   inputVGA Webcam   KEYBOARD, id 6
   inputAT Translated Set 2 keyboard KEYBOARD, id 7
   inputPS/2 Generic Mouse   MOUSE, id 8
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1110 
   vendor LGD
  xserver.version: 2:1.17.1-0ubuntu3.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1504894/+subscriptions

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

[Touch-packages] [Bug 1449282] Re: xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0

[Launchpad Bug Tracker]

This bug was fixed in the package lightdm - 1.16.3-0ubuntu2

---
lightdm (1.16.3-0ubuntu2) wily; urgency=medium

  * debian/patches/xorg-1.17.patch:
- Fix xserver-allow-tcp=true option not working with X.org 1.17
  (LP: #1449282)

 -- Robert Ancell   Mon, 12 Oct 2015
14:57:47 +0100

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

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

Title:
  xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0

Status in Light Display Manager:
  Triaged
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Vivid:
  Fix Committed
Status in lightdm source package in Wily:
  Fix Released

Bug description:
  [Impact]
  xserver-allow-tcp=true option no longer works with X.org 1.17.

  [Test Case]
  1. Edit /etc/lightdm/lightdm.conf and set [SeatDefaults] 
xserver-allow-tcp=true
  2. Start LightDM
  3. Attempt to connect to the X server using TCP

  Expected result:
  Able to connect

  Observed result:
  Unable to connect

  [Regression potential]
  Low. X.org changed their default behaviour from listen by default to listen 
if "-listen tcp" is passed as a command line flag. This is just the equivalent 
change in LightDM. Since this is a new flag to X.org if a user was to use 
another X server there is a risk it would not understand that flag. However it 
seems unlikely since X.org is the only actively developed X server.

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

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

[Touch-packages] [Bug 1504049] Re: apparmor rules too tight for chromium

[Robert Ancell]

** Changed in: lightdm
   Importance: Undecided => Medium

** Changed in: lightdm
   Status: New => Fix Committed

** Changed in: lightdm
Milestone: None => 1.17.0

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

Title:
  apparmor rules too tight for chromium

Status in Light Display Manager:
  Fix Committed
Status in Light Display Manager 1.10 series:
  New
Status in Light Display Manager 1.14 series:
  New
Status in Light Display Manager 1.16 series:
  New
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  New
Status in chromium-browser source package in Trusty:
  New
Status in lightdm source package in Trusty:
  New
Status in chromium-browser source package in Vivid:
  New
Status in lightdm source package in Vivid:
  New
Status in chromium-browser source package in Wily:
  Confirmed
Status in lightdm source package in Wily:
  New

Bug description:
  Hi,

  when running chromium, I get lots of apparmor alerts and warnings,
  although actions seem to be legitimate and normal. Looks as if the
  apparmor ruleset is too tight.

  See attached logs.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: chromium-browser 45.0.2454.101-0ubuntu1.1201
  ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
  Uname: Linux 4.2.0-14-generic x86_64
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  CurrentDesktop: XFCE
  DRM.card0.DP.1:
   edid-base64: 
   dpms: On
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0.DP.2:
   edid-base64: 
   dpms: On
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0.DP.3:
   edid-base64: 
   dpms: On
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0.HDMI.A.1:
   edid-base64: 
   dpms: On
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0.HDMI.A.2:
   edid-base64: 
   dpms: On
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0.HDMI.A.3:
   edid-base64: 
AP///wAQrFagTFdHMAQWAQOAPCJ46o4FrU8zsCYNUFSlSwCBALMAcU+pQIGAAQEBAQEBAjqAGHE4LUBYLCUAVVAhAAAe/wBHNjA2VDIxUTBHV0wK/ABERUxMIFUyNzExCiAg/QA4TB5REQAKICAgICAgAccCAynxUJAFBAMCBxYBBhESFRMUHyAjDX8HZwMMABAAOC2DDwAA4wUDAQI6gBhxOC1AWCwlAFVQIQAAHgEdgBhxHBYgWCwlAFVQIQAAngEdAHJR0B4gbihVAFVQIQAAHowK0Iog4C0QED6WAFVQIQAAGAAAaA==
   dpms: On
   modes: 1920x1080 1920x1080 1920x1080 1920x1080i 1920x1080i 1920x1080 
1920x1080i 1920x1080 1920x1080 1600x1200 1680x1050 1280x1024 1280x1024 1280x800 
1152x864 1280x720 1280x720 1280x720 1024x768 1024x768 800x600 800x600 720x576 
720x576i 720x480 720x480 720x480i 720x480i 640x480 640x480 640x480 720x400
   enabled: enabled
   status: connected
  Date: Thu Oct  8 11:48:15 2015
  Desktop-Session:
   'xubuntu'
   '/etc/xdg/xdg-xubuntu:/usr/share/upstart/xdg:/etc/xdg:/etc/xdg'
   
'/usr/share/xubuntu:/usr/share/xfce4:/usr/local/share/:/usr/share/:/usr/share'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2015-09-03 (34 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825)
  InstalledPlugins:
   
  Load-Avg-1min: 0.47
  Load-Processes-Running-Percent:   0.2%
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-14-generic 
root=UUID=881c90c8-ac82-4df6-98d7-83045b0f9c1b ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: chromium-browser
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: N3150-NUC
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd07/16/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3150-NUC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
  modified.conffile..etc.default.chromium.browser: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/lig

[Touch-packages] [Bug 1504894] Re: Unity battery indicator missing in Ubuntu 15.04

[Jagadeesan A S]

Yes it showing but not working properly..!! Here by i attaching
indicator-power.log file..!!

** Attachment added: "indicator-power.log.1.gz"
   
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1504894/+attachment/4492591/+files/indicator-power.log.1.gz

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

Title:
  Unity battery indicator missing in Ubuntu 15.04

Status in indicator-power package in Ubuntu:
  Incomplete

Bug description:
  In indicator panel Battery notification is missing... I tried Unity
  tweak tool also but not working.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: compiz-core 1:0.9.12.1+15.04.20150410.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-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: Sun Oct 11 12:20:27 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus: focaltech, 1.5, 3.19.0-30-generic, x86_64: installed
  ExecutablePath: /usr/bin/compiz
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:0936]
  InstallationDate: Installed on 2015-10-10 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Acer Aspire ES1-512
  ProcEnviron:
   PATH=(custom, no user)
   SHELL=/bin/bash
   LANG=en_IN
   LANGUAGE=en_IN:en
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic 
root=UUID=57ecf55c-91aa-459d-83b9-ead0c791604a ro quiet splash acpi=off 
vt.handoff=7
  SourcePackage: compiz
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/24/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.09a1
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Aspire ES1-512
  dmi.board.vendor: Acer
  dmi.board.version: V1.09a1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.09a1
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.09a1:bd10/24/2014:svnAcer:pnAspireES1-512:pvrV1.09a1:rvnAcer:rnAspireES1-512:rvrV1.09a1:cvnAcer:ct10:cvrV1.09a1:
  dmi.product.name: Aspire ES1-512
  dmi.product.version: V1.09a1
  dmi.sys.vendor: Acer
  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: Sun Oct 11 12:15:12 2015
  xserver.configfile: default
  xserver.devices:
   inputVGA Webcam   KEYBOARD, id 6
   inputAT Translated Set 2 keyboard KEYBOARD, id 7
   inputPS/2 Generic Mouse   MOUSE, id 8
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1110 
   vendor LGD
  xserver.version: 2:1.17.1-0ubuntu3.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1504894/+subscriptions

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

[Touch-packages] [Bug 1504049] Re: apparmor rules too tight for chromium

[Chad Miller]

** Branch linked: lp:~cmiller/lightdm/guest-session-chromium-sandbox-
cgroups

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

Title:
  apparmor rules too tight for chromium

Status in Light Display Manager:
  Fix Committed
Status in Light Display Manager 1.10 series:
  New
Status in Light Display Manager 1.14 series:
  New
Status in Light Display Manager 1.16 series:
  New
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  New
Status in chromium-browser source package in Trusty:
  New
Status in lightdm source package in Trusty:
  New
Status in chromium-browser source package in Vivid:
  New
Status in lightdm source package in Vivid:
  New
Status in chromium-browser source package in Wily:
  Confirmed
Status in lightdm source package in Wily:
  New

Bug description:
  Hi,

  when running chromium, I get lots of apparmor alerts and warnings,
  although actions seem to be legitimate and normal. Looks as if the
  apparmor ruleset is too tight.

  See attached logs.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: chromium-browser 45.0.2454.101-0ubuntu1.1201
  ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
  Uname: Linux 4.2.0-14-generic x86_64
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  CurrentDesktop: XFCE
  DRM.card0.DP.1:
   edid-base64: 
   dpms: On
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0.DP.2:
   edid-base64: 
   dpms: On
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0.DP.3:
   edid-base64: 
   dpms: On
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0.HDMI.A.1:
   edid-base64: 
   dpms: On
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0.HDMI.A.2:
   edid-base64: 
   dpms: On
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0.HDMI.A.3:
   edid-base64: 
AP///wAQrFagTFdHMAQWAQOAPCJ46o4FrU8zsCYNUFSlSwCBALMAcU+pQIGAAQEBAQEBAjqAGHE4LUBYLCUAVVAhAAAe/wBHNjA2VDIxUTBHV0wK/ABERUxMIFUyNzExCiAg/QA4TB5REQAKICAgICAgAccCAynxUJAFBAMCBxYBBhESFRMUHyAjDX8HZwMMABAAOC2DDwAA4wUDAQI6gBhxOC1AWCwlAFVQIQAAHgEdgBhxHBYgWCwlAFVQIQAAngEdAHJR0B4gbihVAFVQIQAAHowK0Iog4C0QED6WAFVQIQAAGAAAaA==
   dpms: On
   modes: 1920x1080 1920x1080 1920x1080 1920x1080i 1920x1080i 1920x1080 
1920x1080i 1920x1080 1920x1080 1600x1200 1680x1050 1280x1024 1280x1024 1280x800 
1152x864 1280x720 1280x720 1280x720 1024x768 1024x768 800x600 800x600 720x576 
720x576i 720x480 720x480 720x480i 720x480i 640x480 640x480 640x480 720x400
   enabled: enabled
   status: connected
  Date: Thu Oct  8 11:48:15 2015
  Desktop-Session:
   'xubuntu'
   '/etc/xdg/xdg-xubuntu:/usr/share/upstart/xdg:/etc/xdg:/etc/xdg'
   
'/usr/share/xubuntu:/usr/share/xfce4:/usr/local/share/:/usr/share/:/usr/share'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2015-09-03 (34 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825)
  InstalledPlugins:
   
  Load-Avg-1min: 0.47
  Load-Processes-Running-Percent:   0.2%
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-14-generic 
root=UUID=881c90c8-ac82-4df6-98d7-83045b0f9c1b ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: chromium-browser
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: N3150-NUC
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd07/16/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3150-NUC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
  modified.conffile..etc.default.chromium.browser: [deleted]

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

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

[Touch-packages] [Bug 1464958] Re: chromium-browser does not run in guest account

[Chad Miller]

** Branch linked: lp:~cmiller/apparmor/guest-session-chromium-sandbox-
cgroups

** Branch linked: lp:~cmiller/lightdm/guest-session-chromium-sandbox-
cgroups

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

Title:
  chromium-browser does not run in guest account

Status in Chromium Browser:
  Unknown
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in google-chrome-beta package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  New

Bug description:
  Description:

  In guest account, start chromium browser shows nothing.  Start with
  command line shows error:

  guest-1qFsXl@home:~$ chromium-browser http://www.google.com
  Check failed: NamespaceUtils::DenySetgroups()

  This used to work for months and found failed for few weeks.

  Version:

  Ubuntu 14.04 LTS
  chromium-browser43.0.2357.81-0ubuntu0.14.04.1.1
  linux-image-3.13.0-54-generic3.13.0-54.91
  --- 
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  Desktop-Session:
   'None'
   'None'
   'None'
  DetectedPlugins:
   
  DistroRelease: Ubuntu 14.04
  EcryptfsInUse: Yes
  Env:
   'None'
   'None'
  Load-Avg-1min: 0.28
  Load-Processes-Running-Percent:   0.2%
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia
  Package: chromium-browser 43.0.2357.81-0ubuntu0.14.04.1.1089
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-54-generic 
root=UUID=85a7733c-fbc4-49bf-84ce-02be4c5ba907 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-54.91-generic 3.13.11-ckt20
  Tags: third-party-packages trusty
  Uname: Linux 3.13.0-54-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: H97M-ITX/ac
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd12/15/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH97M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.default.chromium.browser: [deleted]
  mtime.conffile..etc.chromium.browser.default: 2015-01-14T08:39:14.796369

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/1464958/+subscriptions

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

[Touch-packages] [Bug 1504049] Re: apparmor rules too tight for chromium

[Robert Ancell]

** Also affects: lightdm
   Importance: Undecided
   Status: New

** Also affects: lightdm/1.10
   Importance: Undecided
   Status: New

** Also affects: lightdm/trunk
   Importance: Undecided
   Status: New

** Also affects: lightdm/1.16
   Importance: Undecided
   Status: New

** Also affects: lightdm/1.14
   Importance: Undecided
   Status: New

** No longer affects: lightdm/trunk

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

Title:
  apparmor rules too tight for chromium

Status in Light Display Manager:
  New
Status in Light Display Manager 1.10 series:
  New
Status in Light Display Manager 1.14 series:
  New
Status in Light Display Manager 1.16 series:
  New
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  New
Status in chromium-browser source package in Trusty:
  New
Status in lightdm source package in Trusty:
  New
Status in chromium-browser source package in Vivid:
  New
Status in lightdm source package in Vivid:
  New
Status in chromium-browser source package in Wily:
  Confirmed
Status in lightdm source package in Wily:
  New

Bug description:
  Hi,

  when running chromium, I get lots of apparmor alerts and warnings,
  although actions seem to be legitimate and normal. Looks as if the
  apparmor ruleset is too tight.

  See attached logs.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: chromium-browser 45.0.2454.101-0ubuntu1.1201
  ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
  Uname: Linux 4.2.0-14-generic x86_64
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  CurrentDesktop: XFCE
  DRM.card0.DP.1:
   edid-base64: 
   dpms: On
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0.DP.2:
   edid-base64: 
   dpms: On
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0.DP.3:
   edid-base64: 
   dpms: On
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0.HDMI.A.1:
   edid-base64: 
   dpms: On
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0.HDMI.A.2:
   edid-base64: 
   dpms: On
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0.HDMI.A.3:
   edid-base64: 
AP///wAQrFagTFdHMAQWAQOAPCJ46o4FrU8zsCYNUFSlSwCBALMAcU+pQIGAAQEBAQEBAjqAGHE4LUBYLCUAVVAhAAAe/wBHNjA2VDIxUTBHV0wK/ABERUxMIFUyNzExCiAg/QA4TB5REQAKICAgICAgAccCAynxUJAFBAMCBxYBBhESFRMUHyAjDX8HZwMMABAAOC2DDwAA4wUDAQI6gBhxOC1AWCwlAFVQIQAAHgEdgBhxHBYgWCwlAFVQIQAAngEdAHJR0B4gbihVAFVQIQAAHowK0Iog4C0QED6WAFVQIQAAGAAAaA==
   dpms: On
   modes: 1920x1080 1920x1080 1920x1080 1920x1080i 1920x1080i 1920x1080 
1920x1080i 1920x1080 1920x1080 1600x1200 1680x1050 1280x1024 1280x1024 1280x800 
1152x864 1280x720 1280x720 1280x720 1024x768 1024x768 800x600 800x600 720x576 
720x576i 720x480 720x480 720x480i 720x480i 640x480 640x480 640x480 720x400
   enabled: enabled
   status: connected
  Date: Thu Oct  8 11:48:15 2015
  Desktop-Session:
   'xubuntu'
   '/etc/xdg/xdg-xubuntu:/usr/share/upstart/xdg:/etc/xdg:/etc/xdg'
   
'/usr/share/xubuntu:/usr/share/xfce4:/usr/local/share/:/usr/share/:/usr/share'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2015-09-03 (34 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825)
  InstalledPlugins:
   
  Load-Avg-1min: 0.47
  Load-Processes-Running-Percent:   0.2%
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-14-generic 
root=UUID=881c90c8-ac82-4df6-98d7-83045b0f9c1b ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: chromium-browser
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: N3150-NUC
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd07/16/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3150-NUC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/

[Touch-packages] [Bug 1504049] Re: apparmor rules too tight for chromium

[Chad Miller]

** Branch linked: lp:~cmiller/apparmor/guest-session-chromium-sandbox-
cgroups

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

Title:
  apparmor rules too tight for chromium

Status in Light Display Manager:
  New
Status in Light Display Manager 1.10 series:
  New
Status in Light Display Manager 1.14 series:
  New
Status in Light Display Manager 1.16 series:
  New
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  New
Status in chromium-browser source package in Trusty:
  New
Status in lightdm source package in Trusty:
  New
Status in chromium-browser source package in Vivid:
  New
Status in lightdm source package in Vivid:
  New
Status in chromium-browser source package in Wily:
  Confirmed
Status in lightdm source package in Wily:
  New

Bug description:
  Hi,

  when running chromium, I get lots of apparmor alerts and warnings,
  although actions seem to be legitimate and normal. Looks as if the
  apparmor ruleset is too tight.

  See attached logs.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: chromium-browser 45.0.2454.101-0ubuntu1.1201
  ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
  Uname: Linux 4.2.0-14-generic x86_64
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  CurrentDesktop: XFCE
  DRM.card0.DP.1:
   edid-base64: 
   dpms: On
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0.DP.2:
   edid-base64: 
   dpms: On
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0.DP.3:
   edid-base64: 
   dpms: On
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0.HDMI.A.1:
   edid-base64: 
   dpms: On
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0.HDMI.A.2:
   edid-base64: 
   dpms: On
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0.HDMI.A.3:
   edid-base64: 
AP///wAQrFagTFdHMAQWAQOAPCJ46o4FrU8zsCYNUFSlSwCBALMAcU+pQIGAAQEBAQEBAjqAGHE4LUBYLCUAVVAhAAAe/wBHNjA2VDIxUTBHV0wK/ABERUxMIFUyNzExCiAg/QA4TB5REQAKICAgICAgAccCAynxUJAFBAMCBxYBBhESFRMUHyAjDX8HZwMMABAAOC2DDwAA4wUDAQI6gBhxOC1AWCwlAFVQIQAAHgEdgBhxHBYgWCwlAFVQIQAAngEdAHJR0B4gbihVAFVQIQAAHowK0Iog4C0QED6WAFVQIQAAGAAAaA==
   dpms: On
   modes: 1920x1080 1920x1080 1920x1080 1920x1080i 1920x1080i 1920x1080 
1920x1080i 1920x1080 1920x1080 1600x1200 1680x1050 1280x1024 1280x1024 1280x800 
1152x864 1280x720 1280x720 1280x720 1024x768 1024x768 800x600 800x600 720x576 
720x576i 720x480 720x480 720x480i 720x480i 640x480 640x480 640x480 720x400
   enabled: enabled
   status: connected
  Date: Thu Oct  8 11:48:15 2015
  Desktop-Session:
   'xubuntu'
   '/etc/xdg/xdg-xubuntu:/usr/share/upstart/xdg:/etc/xdg:/etc/xdg'
   
'/usr/share/xubuntu:/usr/share/xfce4:/usr/local/share/:/usr/share/:/usr/share'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2015-09-03 (34 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825)
  InstalledPlugins:
   
  Load-Avg-1min: 0.47
  Load-Processes-Running-Percent:   0.2%
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-14-generic 
root=UUID=881c90c8-ac82-4df6-98d7-83045b0f9c1b ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: chromium-browser
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: N3150-NUC
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd07/16/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3150-NUC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
  modified.conffile..etc.default.chromium.browser: [deleted]

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

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

[Touch-packages] [Bug 1505302] Re: core_pattern is incorrect on boot with crash reporting enabled

[Jean-Baptiste Lallement]

** Summary changed:

- core_pattern is incorrect on boot on rc-proposed devices
+ core_pattern is incorrect on boot with crash reporting enabled

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

Title:
  core_pattern is incorrect on boot with crash reporting enabled

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

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

  On rc-proposed with crash reporting enabled core_pattern is incorrect on boot:
  $ cat /proc/sys/kernel/core_pattern
  /bad_core_pattern

  Instead of:
  |/usr/share/apport/apport %p %s %c %P

  and crash reporting is disabled while it should be enabled.

  According to the apport.log attached, core_pattern should be set
  correctly.

  If the user disables/enables crash reporting the pattern is correct.

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

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

[Touch-packages] [Bug 1504049] Re: apparmor rules too tight for chromium

[Robert Ancell]

** Also affects: chromium-browser (Ubuntu Wily)
   Importance: Undecided
   Status: Confirmed

** Also affects: lightdm (Ubuntu Wily)
   Importance: Undecided
 Assignee: Robert Ancell (robert-ancell)
   Status: New

** Also affects: chromium-browser (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Also affects: lightdm (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Also affects: chromium-browser (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

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

Title:
  apparmor rules too tight for chromium

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  New
Status in chromium-browser source package in Trusty:
  New
Status in lightdm source package in Trusty:
  New
Status in chromium-browser source package in Vivid:
  New
Status in lightdm source package in Vivid:
  New
Status in chromium-browser source package in Wily:
  Confirmed
Status in lightdm source package in Wily:
  New

Bug description:
  Hi,

  when running chromium, I get lots of apparmor alerts and warnings,
  although actions seem to be legitimate and normal. Looks as if the
  apparmor ruleset is too tight.

  See attached logs.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: chromium-browser 45.0.2454.101-0ubuntu1.1201
  ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
  Uname: Linux 4.2.0-14-generic x86_64
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  CurrentDesktop: XFCE
  DRM.card0.DP.1:
   edid-base64: 
   dpms: On
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0.DP.2:
   edid-base64: 
   dpms: On
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0.DP.3:
   edid-base64: 
   dpms: On
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0.HDMI.A.1:
   edid-base64: 
   dpms: On
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0.HDMI.A.2:
   edid-base64: 
   dpms: On
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0.HDMI.A.3:
   edid-base64: 
AP///wAQrFagTFdHMAQWAQOAPCJ46o4FrU8zsCYNUFSlSwCBALMAcU+pQIGAAQEBAQEBAjqAGHE4LUBYLCUAVVAhAAAe/wBHNjA2VDIxUTBHV0wK/ABERUxMIFUyNzExCiAg/QA4TB5REQAKICAgICAgAccCAynxUJAFBAMCBxYBBhESFRMUHyAjDX8HZwMMABAAOC2DDwAA4wUDAQI6gBhxOC1AWCwlAFVQIQAAHgEdgBhxHBYgWCwlAFVQIQAAngEdAHJR0B4gbihVAFVQIQAAHowK0Iog4C0QED6WAFVQIQAAGAAAaA==
   dpms: On
   modes: 1920x1080 1920x1080 1920x1080 1920x1080i 1920x1080i 1920x1080 
1920x1080i 1920x1080 1920x1080 1600x1200 1680x1050 1280x1024 1280x1024 1280x800 
1152x864 1280x720 1280x720 1280x720 1024x768 1024x768 800x600 800x600 720x576 
720x576i 720x480 720x480 720x480i 720x480i 640x480 640x480 640x480 720x400
   enabled: enabled
   status: connected
  Date: Thu Oct  8 11:48:15 2015
  Desktop-Session:
   'xubuntu'
   '/etc/xdg/xdg-xubuntu:/usr/share/upstart/xdg:/etc/xdg:/etc/xdg'
   
'/usr/share/xubuntu:/usr/share/xfce4:/usr/local/share/:/usr/share/:/usr/share'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2015-09-03 (34 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825)
  InstalledPlugins:
   
  Load-Avg-1min: 0.47
  Load-Processes-Running-Percent:   0.2%
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-14-generic 
root=UUID=881c90c8-ac82-4df6-98d7-83045b0f9c1b ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: chromium-browser
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: N3150-NUC
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd07/16/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3150-NUC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/ic

[Touch-packages] [Bug 1505302] Re: core_pattern is incorrect on boot on rc-proposed devices

[Jean-Baptiste Lallement]

** Description changed:

  current build number: 136
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  
- On rc-proposed with crash reporting enabled core_pattern is incorrect:
- $ cat /proc/sys/kernel/core_pattern 
+ On rc-proposed with crash reporting enabled core_pattern is incorrect on boot:
+ $ cat /proc/sys/kernel/core_pattern
  /bad_core_pattern
  
  Instead of:
  |/usr/share/apport/apport %p %s %c %P
  
  and crash reporting is disabled while it should be enabled.
  
  According to the apport.log attached, core_pattern should be set
  correctly.
+ 
+ If the user disables/enables crash reporting the pattern is correct.

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Pat McGowan (pat-mcgowan)

** 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 apport in Ubuntu.
https://bugs.launchpad.net/bugs/1505302

Title:
  core_pattern is incorrect on boot on rc-proposed devices

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

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

  On rc-proposed with crash reporting enabled core_pattern is incorrect on boot:
  $ cat /proc/sys/kernel/core_pattern
  /bad_core_pattern

  Instead of:
  |/usr/share/apport/apport %p %s %c %P

  and crash reporting is disabled while it should be enabled.

  According to the apport.log attached, core_pattern should be set
  correctly.

  If the user disables/enables crash reporting the pattern is correct.

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

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

[Touch-packages] [Bug 1505302] Re: core_pattern is incorrect on boot on rc-proposed devices

[Dave Morley]

Confirmed

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

Title:
  core_pattern is incorrect on boot on rc-proposed devices

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

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

  On rc-proposed with crash reporting enabled core_pattern is incorrect on boot:
  $ cat /proc/sys/kernel/core_pattern
  /bad_core_pattern

  Instead of:
  |/usr/share/apport/apport %p %s %c %P

  and crash reporting is disabled while it should be enabled.

  According to the apport.log attached, core_pattern should be set
  correctly.

  If the user disables/enables crash reporting the pattern is correct.

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

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

[Touch-packages] [Bug 1505302] Re: core_pattern is incorrect on boot on rc-proposed devices

[Launchpad Bug Tracker]

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

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

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

Title:
  core_pattern is incorrect on boot on rc-proposed devices

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

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

  On rc-proposed with crash reporting enabled core_pattern is incorrect on boot:
  $ cat /proc/sys/kernel/core_pattern
  /bad_core_pattern

  Instead of:
  |/usr/share/apport/apport %p %s %c %P

  and crash reporting is disabled while it should be enabled.

  According to the apport.log attached, core_pattern should be set
  correctly.

  If the user disables/enables crash reporting the pattern is correct.

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

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

[Touch-packages] [Bug 1505301] [NEW] Make all user visible applications recommends not depends for Ubuntu Desktop

[Will Cooke]

Public bug reported:

Removing, for example, file-roller should not uninstall the ubuntu-
desktop meta package.

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


** Tags: rls-w-incoming

** Tags added: rls-w-incoming

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

Title:
  Make all user visible applications recommends not depends for Ubuntu
  Desktop

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Removing, for example, file-roller should not uninstall the ubuntu-
  desktop meta package.

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

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

[Touch-packages] [Bug 1505302] [NEW] core_pattern is incorrect on boot on rc-proposed devices

[Jean-Baptiste Lallement]

Public bug reported:

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

On rc-proposed with crash reporting enabled core_pattern is incorrect on boot:
$ cat /proc/sys/kernel/core_pattern
/bad_core_pattern

Instead of:
|/usr/share/apport/apport %p %s %c %P

and crash reporting is disabled while it should be enabled.

According to the apport.log attached, core_pattern should be set
correctly.

If the user disables/enables crash reporting the pattern is correct.

** Affects: canonical-devices-system-image
 Importance: Critical
 Assignee: Pat McGowan (pat-mcgowan)
 Status: Confirmed

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

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

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

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

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

Title:
  core_pattern is incorrect on boot on rc-proposed devices

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

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

  On rc-proposed with crash reporting enabled core_pattern is incorrect on boot:
  $ cat /proc/sys/kernel/core_pattern
  /bad_core_pattern

  Instead of:
  |/usr/share/apport/apport %p %s %c %P

  and crash reporting is disabled while it should be enabled.

  According to the apport.log attached, core_pattern should be set
  correctly.

  If the user disables/enables crash reporting the pattern is correct.

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

-- 
Mailing list: https://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 1389954] Re: Make .lxc domain name resolution easier to discover and enable

[Serge Hallyn]

Hi,

personally in 15.10 I have

# Tell any system-wide dnsmasq instance to make sure to bind to interfaces
# instead of listening on 0.0.0.0
# WARNING: changes to this file will get lost if lxc is removed.
bind-interfaces
except-interface=lxcbr0
server=/lxc/10.0.3.1

in /etc/dnsmaq.d/lxc

and it does work:

ping precise-gui.lxc
PING precise-gui.lxc (10.0.3.57) 56(84) bytes of data.

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

Title:
  Make .lxc domain name resolution easier to discover and enable

Status in lxc package in Ubuntu:
  Confirmed

Bug description:
  The lxc package on ubuntu does almost nothing to help a user enable
  DNS resolution for containers via dnsmaq, let alone discover that it
  is possible. How about enabling it by default? I think all it would
  take is adding server=/lxc/10.0.3.1 to a file in
  /etc/NetworkManager/dnsmasq.d/ and uncommenting LXC_DOMAIN="lxc" in
  /etc/default/lxc-net.

  Even if there's a good reason not to enable this by default, shouldn't
  it at least be clearly documented someplace obvious instead of buried
  in a system config file with a misleading comment that mentions the
  wrong dnsmasq file to edit? (The one currently mentioned by
  /etc/default/lxc-net does nothing on ubuntu desktop systems, because
  ubuntu's NetworkManager starts dnsmasq with a special config
  directory.)

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

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

[Touch-packages] [Bug 1504600] Re: Need libpython3.4 (version 3.4.2) for Trustee (for Libreoffice)

[Bob]

** Description changed:

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

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

Title:
  Need libpython3.4 (version 3.4.2) for Trustee (for Libreoffice)

Status in libreoffice package in Ubuntu:
  Confirmed
Status in python3.4 package in Ubuntu:
  Confirmed

Bug description:
  The current version of libpython for trustee is 3.4.0.

  That means that libreoffice will not build on ubuntu 14.0.4.3.
  (because Libreoffice requires python3-uno, which in turns requires
  libpython3.4 (>= 3.4.2).

  The dependency chain is this:

  > sudo apt-get install libreoffice
  > -- Fails due to Depends: python3-uno (>= 4.0~)
  > sudo apt-get install python3-uno
  > -- Fails due to: python3-uno : Depends: libpython3.4 (>= 3.4.2) but
  > 3.4.0-2ubuntu1.1 is to be installed

  So until we can get an updated version of libpython, Libreoffice won't
  work on Ubuntu 14.04.

  Could we please get an updated version of libpython3.4 for Trustee?

  Thank you,

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

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

[Touch-packages] [Bug 1504049] Re: apparmor rules too tight for chromium

[Chad Miller]

** Attachment added: "debdiff punching holes for cr sandbox to lightdm guest 
session"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1504049/+attachment/4492589/+files/lightdm-debdiff

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

** Changed in: lightdm (Ubuntu)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

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

Title:
  apparmor rules too tight for chromium

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  New

Bug description:
  Hi,

  when running chromium, I get lots of apparmor alerts and warnings,
  although actions seem to be legitimate and normal. Looks as if the
  apparmor ruleset is too tight.

  See attached logs.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: chromium-browser 45.0.2454.101-0ubuntu1.1201
  ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
  Uname: Linux 4.2.0-14-generic x86_64
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  CurrentDesktop: XFCE
  DRM.card0.DP.1:
   edid-base64: 
   dpms: On
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0.DP.2:
   edid-base64: 
   dpms: On
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0.DP.3:
   edid-base64: 
   dpms: On
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0.HDMI.A.1:
   edid-base64: 
   dpms: On
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0.HDMI.A.2:
   edid-base64: 
   dpms: On
   modes: 
   enabled: disabled
   status: disconnected
  DRM.card0.HDMI.A.3:
   edid-base64: 
AP///wAQrFagTFdHMAQWAQOAPCJ46o4FrU8zsCYNUFSlSwCBALMAcU+pQIGAAQEBAQEBAjqAGHE4LUBYLCUAVVAhAAAe/wBHNjA2VDIxUTBHV0wK/ABERUxMIFUyNzExCiAg/QA4TB5REQAKICAgICAgAccCAynxUJAFBAMCBxYBBhESFRMUHyAjDX8HZwMMABAAOC2DDwAA4wUDAQI6gBhxOC1AWCwlAFVQIQAAHgEdgBhxHBYgWCwlAFVQIQAAngEdAHJR0B4gbihVAFVQIQAAHowK0Iog4C0QED6WAFVQIQAAGAAAaA==
   dpms: On
   modes: 1920x1080 1920x1080 1920x1080 1920x1080i 1920x1080i 1920x1080 
1920x1080i 1920x1080 1920x1080 1600x1200 1680x1050 1280x1024 1280x1024 1280x800 
1152x864 1280x720 1280x720 1280x720 1024x768 1024x768 800x600 800x600 720x576 
720x576i 720x480 720x480 720x480i 720x480i 640x480 640x480 640x480 720x400
   enabled: enabled
   status: connected
  Date: Thu Oct  8 11:48:15 2015
  Desktop-Session:
   'xubuntu'
   '/etc/xdg/xdg-xubuntu:/usr/share/upstart/xdg:/etc/xdg:/etc/xdg'
   
'/usr/share/xubuntu:/usr/share/xfce4:/usr/local/share/:/usr/share/:/usr/share'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2015-09-03 (34 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825)
  InstalledPlugins:
   
  Load-Avg-1min: 0.47
  Load-Processes-Running-Percent:   0.2%
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-14-generic 
root=UUID=881c90c8-ac82-4df6-98d7-83045b0f9c1b ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: chromium-browser
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: N3150-NUC
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd07/16/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3150-NUC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
  modified.conffile..etc.default.chromium.browser: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1504049/+subscriptions

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

[Touch-packages] [Bug 1500768] Re: python3.4.3 SRU break requests

[Matthias Klose]

** Package changed: python3.4 (Ubuntu) => python-urllib3 (Ubuntu)

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

Title:
  python3.4.3 SRU break requests

Status in python-urllib3 package in Ubuntu:
  Invalid
Status in python-urllib3 source package in Trusty:
  Triaged

Bug description:
  Sicne the upgade to python 3.4.3 on trusty, I'm getting this error when using 
a squid proxy:
  
https://jenkins.qa.ubuntu.com/view/All/job/udtc-trusty-tests/1946/label=ps-trusty-desktop-amd64-1,type=large/testReport/tests.large.test_android/AndroidSDKTests/test_default_android_sdk_install/

  The code is using python-requests, with verify=True for ssl connection
  (default). Some tests are testing that invalid certificates are
  rejected:  https://github.com/ubuntu/ubuntu-
  make/blob/master/umake/network/download_center.py#L129

  Rerunning the same code with previous trusty package (3.4.0~trusty1)
  doesn't show up this issue. It seems that SNI is broken for the trusty
  version of python3-requests with 3.4.3. (See the FAQ http://www
  .python-requests.org/en/latest/community/faq/ with "What are “hostname
  doesn’t match” errors?" and the stackoverflow question.

  I did run a test, grabbing requests 2.7 and backporting it to trusty
  (I needed to as well to take python3-urllib3 willy version).

  So, 3.4.3 has an incompatible change for existing projects and people
  with proxys are starting to see some breakage like in
  https://bugs.launchpad.net/ubuntu/+source/ubuntu-make/+bug/1499890.

  Can we get it fix somehow, reverting the incompatible change breaking
  SNI (I wonder if this is "Changed in version 3.4.3: This class now
  performs all the necessary certificate and hostname checks by default.
  To revert to the previous, unverified, behavior
  ssl._create_unverified_context() can be passed to the context
  parameter." in https://docs.python.org/3/library/http.client.html or
  something else) so that existing code can either get a new compatible
  python-requests or avoid incompatible changes in python 3.4.3?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-urllib3/+bug/1500768/+subscriptions

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

[Touch-packages] [Bug 1438465] Re: It's possible to put a window under the top panel

[kevin gunn]

** No longer affects: qtmir

** No longer affects: qtmir (Ubuntu)

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

Title:
  It's possible to put a window under the top panel

Status in canonical-pocket-desktop:
  New
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  so many times,when i drag the window to the top, the max-min-button
  will be overlaied by panel,so i can not drag this window back and i
  can not see these buttons

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

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

[Touch-packages] [Bug 1412916]

[Martin McDowell]

It has been a year since a last post of this bug but I am still getting
this problem in October 2015. I have Ubuntu 14.04. The PDF is viewed in
the default Evince document viewer 3.10.3

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

Title:
  evince: Bad PDF rendering: invalid font scale

Status in Poppler:
  Fix Released
Status in poppler package in Ubuntu:
  Fix Released

Bug description:
  Evince in ubuntu 14.04 (3.10.3-0ubuntu10.1) suffers from this bug:
  https://www.libreoffice.org/bugzilla/show_bug.cgi?id=78042

  The test case which is attached to the upstream bug demonstrates the
  problem with Evince in Ubuntu.

  Hopefully, the patch attached to the upstream bug report would fix the
  problem in ubuntu.

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

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

[Touch-packages] [Bug 1412916]

[Adrian Johnson]

(In reply to Martin McDowell from comment #8)
> It has been a year since a last post of this bug but I am still getting this
> problem in October 2015. I have Ubuntu 14.04. The PDF is viewed in the
> default Evince document viewer 3.10.3

The fix is in poppler 0.28 released in Nov 2014.

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

Title:
  evince: Bad PDF rendering: invalid font scale

Status in Poppler:
  Fix Released
Status in poppler package in Ubuntu:
  Fix Released

Bug description:
  Evince in ubuntu 14.04 (3.10.3-0ubuntu10.1) suffers from this bug:
  https://www.libreoffice.org/bugzilla/show_bug.cgi?id=78042

  The test case which is attached to the upstream bug demonstrates the
  problem with Evince in Ubuntu.

  Hopefully, the patch attached to the upstream bug report would fix the
  problem in ubuntu.

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

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

[Touch-packages] [Bug 1505148] Re: shell restarts spontaneously

[Jean-Baptiste Lallement]

unfortunatly there is no crash report.

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

Title:
  shell restarts spontaneously

Status in unity8 package in Ubuntu:
  Incomplete

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

  I opened the spread, dismissed an app (dekko IIRC) the shell froze for
  a couple of seconds and restarted (only the shell not the device) Then
  everything resumed as if nothing happened.

  It was not an out of memory situation or the watchdog. Logs attached.
  It happened around 8:19 local time in syslog.

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

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

[Touch-packages] [Bug 1438465] Re: It's possible to put a window under the top panel

[Gerry Boland]

QtMir not responsible for window positioning.

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

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

Title:
  It's possible to put a window under the top panel

Status in canonical-pocket-desktop:
  New
Status in QtMir:
  New
Status in qtmir package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  so many times,when i drag the window to the top, the max-min-button
  will be overlaied by panel,so i can not drag this window back and i
  can not see these buttons

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

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

[Touch-packages] [Bug 1504065] Re: Cannot play videos when a wired headphone is connected

[Matthew Paul Thomas]

To expand on Michał's hypothesis...

1. You connect a headset for which the remembered "alert" volume < 85 dBA, but 
"multimedia" volume > 85 dBA.
2. You start playing a video, so the active audio output role switches from 
"alert" to "multimedia".
3. Since the "multimedia" volume > 85 dBA, the snap decision appears.
4. Since the video has lost focus, it stops playing.
5. Since the video has stopped playing, the active role switches back to 
"alert".
6. Since the active audio output role is no longer one with volume > 85 dBA, 
the snap decision disappears.
7. You're left with nothing but a paused video.

If so, there are a few possible solutions, not mutually exclusive...

(1) Perhaps Ubuntu should clamp all restored volumes to 85 dBA? But that
might be annoying if you accidentally unplugged a headset for a couple
of seconds, plugged it back in, and had to re-amp the volume.

(2, 5) This particular symptom might be suppressed by merging "alert"
and "multimedia", though it might still occur while bug 1485522 is
unfixed (apps being allowed to override the system-set multimedia
volume). Even if that was fixed too, though, you might get a similar
problem if, for example, you had set the "alarm" volume to be greater
than 85 dBA. Either the volume warning snap decision would suppress the
alarm snap decision, and would immediately disappear because the alarm
was no longer playing; or the volume warning wouldn't appear at all,
because it couldn't appear until the alarm stopped, at which point it
would no longer apply.

(4) It might be reasonable to pause video playback when a dialog appears
in *some* cases -- for example, incoming call, alarm, or timer done. I
doubt this is always true, though -- probably not for volume warnings,
and certainly not for dialogs in general on a PC. Pause if you switch to
a different app, sure, but not merely for a dialog on top of the current
app.

(7) If video playback does pause for a dialog in general, maybe it
should resume when the dialog goes away. But that seems unlikely; if
loud music was interrupted by a 40-minute phone call, the call
unexpectedly disconnecting shouldn't cause the music to suddenly blare
in your ears. Anyway, changing that wouldn't fix this bug, it would just
make it even worse by turning it into an endless loop.

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

Title:
  Cannot play videos when a wired headphone is connected

Status in The Sound Menu:
  New
Status in mediaplayer-app:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  When having a wired headset connected to the device, video playback
  keeps on being paused as soon as playback is started. Looks like some
  snap-decision notification is shown, but it's too short time to read
  what it actually says because it disappears again when the playback
  stops again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-sound/+bug/1504065/+subscriptions

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

[Touch-packages] [Bug 1464958] Re: chromium-browser does not run in guest account

[Chad Miller]

apparmor="DENIED" operation="open" 
profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/sys/kernel/cap_last_cap" pid=20779 comm="dbus-daemon" 
requested_mask="r" denied_mask="r" fsuid=135 ouid=0
apparmor="DENIED" operation="open" 
profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/sys/kernel/cap_last_cap" pid=20800 comm="gnome-keyring-d" 
requested_mask="r" denied_mask="r" fsuid=135 ouid=0
apparmor="DENIED" operation="open" 
profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/sys/kernel/cap_last_cap" pid=20806 comm="gnome-keyring-d" 
requested_mask="r" denied_mask="r" fsuid=135 ouid=0
apparmor="DENIED" operation="exec" info="profile not found" error=-2 
profile="/usr/lib/lightdm/lightdm-guest-session" name="/bin/fusermount" 
pid=20882 comm="gvfsd-fuse" requested_mask="x" denied_mask="x" fsuid=135 ouid=0
apparmor="DENIED" operation="exec" info="profile not found" error=-2 
profile="/usr/lib/lightdm/lightdm-guest-session" name="/bin/fusermount" 
pid=20882 comm="gvfsd-fuse" requested_mask="x" denied_mask="x" fsuid=135 ouid=0
apparmor="DENIED" operation="exec" info="profile not found" error=-2 
profile="/usr/lib/lightdm/lightdm-guest-session" name="/bin/fusermount" 
pid=20888 comm="gvfsd-fuse" requested_mask="x" denied_mask="x" fsuid=135 ouid=0
apparmor="DENIED" operation="exec" info="profile not found" error=-2 
profile="/usr/lib/lightdm/lightdm-guest-session" name="/bin/fusermount" 
pid=20888 comm="gvfsd-fuse" requested_mask="x" denied_mask="x" fsuid=135 ouid=0
apparmor="DENIED" operation="open" 
profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/sys/kernel/cap_last_cap" pid=21048 comm="dbus-daemon" 
requested_mask="r" denied_mask="r" fsuid=135 ouid=0
apparmor="DENIED" operation="open" 
profile="/usr/lib/lightdm/lightdm-guest-session" name="/proc/1/cgroup" 
pid=21042 comm="gnome-session" requested_mask="r" denied_mask="r" fsuid=135 
ouid=0
apparmor="DENIED" operation="open" 
profile="/usr/lib/lightdm/lightdm-guest-session" name="/proc/1/cgroup" 
pid=21097 comm="indicator-messa" requested_mask="r" denied_mask="r" fsuid=135 
ouid=0

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

Title:
  chromium-browser does not run in guest account

Status in Chromium Browser:
  Unknown
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in google-chrome-beta package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  New

Bug description:
  Description:

  In guest account, start chromium browser shows nothing.  Start with
  command line shows error:

  guest-1qFsXl@home:~$ chromium-browser http://www.google.com
  Check failed: NamespaceUtils::DenySetgroups()

  This used to work for months and found failed for few weeks.

  Version:

  Ubuntu 14.04 LTS
  chromium-browser43.0.2357.81-0ubuntu0.14.04.1.1
  linux-image-3.13.0-54-generic3.13.0-54.91
  --- 
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  Desktop-Session:
   'None'
   'None'
   'None'
  DetectedPlugins:
   
  DistroRelease: Ubuntu 14.04
  EcryptfsInUse: Yes
  Env:
   'None'
   'None'
  Load-Avg-1min: 0.28
  Load-Processes-Running-Percent:   0.2%
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia
  Package: chromium-browser 43.0.2357.81-0ubuntu0.14.04.1.1089
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-54-generic 
root=UUID=85a7733c-fbc4-49bf-84ce-02be4c5ba907 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-54.91-generic 3.13.11-ckt20
  Tags: third-party-packages trusty
  Uname: Linux 3.13.0-54-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: H97M-ITX/ac
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd12/15/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH97M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.default.chromium.browser: [deleted]
  mtime.conffile..etc.chromium.browser.default: 2015-01-14T08:39:14.796369

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/1464958/+subscriptions

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

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

[kevin gunn]

if it were screen related mir team might be able to help, but this seems
to be strictly power mode issue, cmiiaw

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

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

Title:
  Phone did not suspend

Status in Canonical System Image:
  New
Status in powerd package in Ubuntu:
  New

Bug description:
  Noticed a quick batter drain, no idea what was keeping it awake all
  day and night.

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

[Touch-packages] [Bug 1464958] Re: chromium-browser does not run in guest account

[Chad Miller]

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

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

Title:
  chromium-browser does not run in guest account

Status in Chromium Browser:
  Unknown
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in google-chrome-beta package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  New

Bug description:
  Description:

  In guest account, start chromium browser shows nothing.  Start with
  command line shows error:

  guest-1qFsXl@home:~$ chromium-browser http://www.google.com
  Check failed: NamespaceUtils::DenySetgroups()

  This used to work for months and found failed for few weeks.

  Version:

  Ubuntu 14.04 LTS
  chromium-browser43.0.2357.81-0ubuntu0.14.04.1.1
  linux-image-3.13.0-54-generic3.13.0-54.91
  --- 
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  Desktop-Session:
   'None'
   'None'
   'None'
  DetectedPlugins:
   
  DistroRelease: Ubuntu 14.04
  EcryptfsInUse: Yes
  Env:
   'None'
   'None'
  Load-Avg-1min: 0.28
  Load-Processes-Running-Percent:   0.2%
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia
  Package: chromium-browser 43.0.2357.81-0ubuntu0.14.04.1.1089
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-54-generic 
root=UUID=85a7733c-fbc4-49bf-84ce-02be4c5ba907 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-54.91-generic 3.13.11-ckt20
  Tags: third-party-packages trusty
  Uname: Linux 3.13.0-54-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: H97M-ITX/ac
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd12/15/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH97M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.default.chromium.browser: [deleted]
  mtime.conffile..etc.chromium.browser.default: 2015-01-14T08:39:14.796369

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/1464958/+subscriptions

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

[Touch-packages] [Bug 1488417] Re: nexus4 window mode mouse motion bounded incorrectly with external monitor

[kevin gunn]

this is fixed in silo 22 which should land soon

** Branch linked: lp:~unity-team/unity8/mousePointer

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

** Changed in: canonical-pocket-desktop
   Status: New => In Progress

** Changed in: canonical-pocket-desktop
 Assignee: (unassigned) => kevin gunn (kgunn72)

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

Title:
  nexus4 window mode mouse motion bounded incorrectly with external
  monitor

Status in canonical-pocket-desktop:
  In Progress
Status in Mir:
  New
Status in QtMir:
  New
Status in mir package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  In Progress

Bug description:
  when connecting a monitor to the Nexus4 during windowed mode, the
  device is put into landscape mode. the mouse motion appears to not
  have followed the orientation and is bounded by roughly portrait width
  instead of landscape width

  
  The problem is that when unity8 configures cloning, it picks the intersection 
of all displays. While the input subsystem uses the bounding rectangle of all 
displays. Thus it allows the cursor to move around in (1200x1920) while the 
only surface is 1080x1920. So there is a dead zone between the display extent 
and the surface extent. When the cursor hits that area the 
SurfaceInputDispatcher has no surface underneath, so it decides to not send any 
further mouse input to Unity8.

  We can fix that by extending the behaviour of display_input_region.cpp
  to use the intersection of displays when necessary.

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

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

[Touch-packages] [Bug 1505148] Re: shell restarts spontaneously

[Michał Sawicz]

A mir exception can be found in the log:

terminate called after throwing an instance of 'std::length_error'
  what():  basic_string::_S_create

Any chance you could provide the corresponding .crash file?

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

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

Title:
  shell restarts spontaneously

Status in unity8 package in Ubuntu:
  Incomplete

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

  I opened the spread, dismissed an app (dekko IIRC) the shell froze for
  a couple of seconds and restarted (only the shell not the device) Then
  everything resumed as if nothing happened.

  It was not an out of memory situation or the watchdog. Logs attached.
  It happened around 8:19 local time in syslog.

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

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

[Touch-packages] [Bug 1505272] [NEW] X crashes more and more often

[francois]

Public bug reported:


Kubuntu 14.04 Trusty - Nvidia driver - used to work very well, now regularly 
crashes while browsing with Firefox.

libpthread.so.0 -> libc.so.6 -> Segmentation fault -> Signal 11 -> X
dies, back to login

[  1650.853] (EE)
[  1650.853] (EE) Backtrace:
[  1650.881] (EE) 0: /usr/bin/X (xorg_backtrace+0x48) [0x7fbb4b732848]
[  1650.881] (EE) 1: /usr/bin/X (0x7fbb4b589000+0x1ad539) [0x7fbb4b736539]
[  1650.881] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7fbb4a685000+0x10340) [0x7fbb4a695340]
[  1650.881] (EE) 3: /usr/bin/X (0x7fbb4b589000+0x107f8f) [0x7fbb4b690f8f]
[  1650.881] (EE) 4: /usr/bin/X (_CallCallbacks+0x34) [0x7fbb4b5e4054]
[  1650.881] (EE) 5: /usr/bin/X (XaceHook+0xe4) [0x7fbb4b68b764]
[  1650.881] (EE) 6: /usr/bin/X (dixLookupResourceByType+0x113) [0x7fbb4b602693]
[  1650.881] (EE) 7: /usr/bin/X (0x7fbb4b589000+0x128fb2) [0x7fbb4b6b1fb2]
[  1650.881] (EE) 8: /usr/bin/X (0x7fbb4b589000+0x55f0e) [0x7fbb4b5def0e]
[  1650.881] (EE) 9: /usr/bin/X (0x7fbb4b589000+0x59d9a) [0x7fbb4b5e2d9a]
[  1650.881] (EE) 10: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf5) 
[0x7fbb490c3ec5]
[  1650.881] (EE) 11: /usr/bin/X (0x7fbb4b589000+0x451ee) [0x7fbb4b5ce1ee]
[  1650.881] (EE)
[  1650.881] (EE) Segmentation fault at address 0x2730001
[  1650.881] (EE)
Fatal server error:
[  1650.881] (EE) Caught signal 11 (Segmentation fault). Server aborting
[  1650.881] (EE)

** Affects: xorg (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/1505272

Title:
  X crashes more and more often

Status in xorg package in Ubuntu:
  New

Bug description:
  
  Kubuntu 14.04 Trusty - Nvidia driver - used to work very well, now regularly 
crashes while browsing with Firefox.

  libpthread.so.0 -> libc.so.6 -> Segmentation fault -> Signal 11 -> X
  dies, back to login

  [  1650.853] (EE)
  [  1650.853] (EE) Backtrace:
  [  1650.881] (EE) 0: /usr/bin/X (xorg_backtrace+0x48) [0x7fbb4b732848]
  [  1650.881] (EE) 1: /usr/bin/X (0x7fbb4b589000+0x1ad539) [0x7fbb4b736539]
  [  1650.881] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7fbb4a685000+0x10340) [0x7fbb4a695340]
  [  1650.881] (EE) 3: /usr/bin/X (0x7fbb4b589000+0x107f8f) [0x7fbb4b690f8f]
  [  1650.881] (EE) 4: /usr/bin/X (_CallCallbacks+0x34) [0x7fbb4b5e4054]
  [  1650.881] (EE) 5: /usr/bin/X (XaceHook+0xe4) [0x7fbb4b68b764]
  [  1650.881] (EE) 6: /usr/bin/X (dixLookupResourceByType+0x113) 
[0x7fbb4b602693]
  [  1650.881] (EE) 7: /usr/bin/X (0x7fbb4b589000+0x128fb2) [0x7fbb4b6b1fb2]
  [  1650.881] (EE) 8: /usr/bin/X (0x7fbb4b589000+0x55f0e) [0x7fbb4b5def0e]
  [  1650.881] (EE) 9: /usr/bin/X (0x7fbb4b589000+0x59d9a) [0x7fbb4b5e2d9a]
  [  1650.881] (EE) 10: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf5) [0x7fbb490c3ec5]
  [  1650.881] (EE) 11: /usr/bin/X (0x7fbb4b589000+0x451ee) [0x7fbb4b5ce1ee]
  [  1650.881] (EE)
  [  1650.881] (EE) Segmentation fault at address 0x2730001
  [  1650.881] (EE)
  Fatal server error:
  [  1650.881] (EE) Caught signal 11 (Segmentation fault). Server aborting
  [  1650.881] (EE)

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

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

[Touch-packages] [Bug 1238979] Re: [Scopes] Scope result models are cleared on updates

[Pawel Stolowski]

I've linked a new MP - diff-updates branch - which IMHO improves current
dash interactions *a lot*

It gets rid of results model clearing and instead only updates the model
as results arrive, after a small delay (to have a chance of accumulating
some results).  Now, whether we should still consider disabling the view
while waiting for new search to finish is an open question, but I think
it's not necessary - the bouncing bar above OSK gives clear indication
that things are about to change. While some jumping may in theory
happen, in practice it works very well (I've played with several
scopes). These changes are currently available in silo 20 for testing.

Note, the suggestion to "enforce that an existing item cannot change
physical location when a new item arrives" is not really possible to
accomplish - the order of results is up to the scope, a new search may
return the same items as previous one, only in different order, in which
case we will just move items around.

** Branch unlinked: lp:~stolowski/unity-scopes-shell/delay-clear

** Branch unlinked: lp:~stolowski/unity-api/results-enabled-flag

** Branch unlinked: lp:~aacid/unity8/results-enabled-flag

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

Title:
  [Scopes] Scope result models are cleared on updates

Status in Ubuntu UX:
  Fix Committed
Status in Unity Media Scanner Scope:
  Invalid
Status in unity-scopes-shell package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  The result models are cleared when updated, which causes abrupt
  changes in the dash. We need a better way for updating the models
  without clearing them :/

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

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

[Touch-packages] [Bug 1504853] Re: Certificate errors in the browser are confusing

[Chris Coulson]

For non-overridable errors, this change will require webbrowser-app to
explicitly destroy CertificateError once the error sheet is dismissed,
in order to work correctly.

Olivier, that shouldn't be a problem, should it?

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

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

Title:
  Certificate errors in the browser are confusing

Status in Oxide:
  In Progress
Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  When the browser displays a certificate error, it indicates the
  request URL that the error originated from. This is fine. However, if
  the navigation is content initiated then the addressbar will indicate
  the URL of the currently committed page (which will be different to
  the URL of the page causing the error, which is displayed in the error
  UI provided by the browser).

  I have an idea to fix this by navigating the webview to a placeholder
  interstitial page whilst waiting for a response from the browser. This
  will update the addressbar, keep the navigation history consistent and
  also make the back button behave the same as Chrome.

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

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

[Touch-packages] [Bug 1238979] Re: [Scopes] Scope result models are cleared on updates

[Pawel Stolowski]

** Branch linked: lp:~stolowski/unity-scopes-shell/diff-updates

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

Title:
  [Scopes] Scope result models are cleared on updates

Status in Ubuntu UX:
  Fix Committed
Status in Unity Media Scanner Scope:
  Invalid
Status in unity-scopes-shell package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  The result models are cleared when updated, which causes abrupt
  changes in the dash. We need a better way for updating the models
  without clearing them :/

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

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

[Touch-packages] [Bug 1501588] Re: Wily's wpasupplicant frequently fails on WPA enterprise networks

[Jean-Louis Dupond]

Arch had same issue it seems:
https://projects.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/wpa_supplicant&id=7562b98bd83fe5bce43e6952e0e922e7791e18b5

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

Title:
  Wily's wpasupplicant frequently fails on WPA enterprise networks

Status in wpa package in Ubuntu:
  New

Bug description:
  Ever since I upgraded from vivid to wily on my laptop, I'm running
  into problems when connecting to my home WPA2 enterprise network.

  Typically the first connection immediately after the driver is loaded
  works as expected, however any further reconnection and the occasional
  roaming between APs cause wpasupplicant to freeze entirely requiring
  me to kill it and most often also reload my wireless driver to get
  things working again.

  ## A failed (hanging) association looks like:
  Sep 30 23:31:06 castiana NetworkManager[25815]:   (wlan0): Activation: 
(wifi) connection 'stgraber.net-secure' has security, and secrets exist.  No 
new secrets needed.
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 'ssid' 
value 'stgraber.net-secure'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 
'scan_ssid' value '1'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 
'key_mgmt' value 'WPA-EAP'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 'eap' 
value 'TLS'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 
'fragment_size' value '1300'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 
'ca_cert' value '/home/stgraber/data/certs/stgraber-radius/ca.crt'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 
'private_key' value '/home/stgraber/data/certs/stgraber-radius/castiana.p12'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 
'private_key_passwd' value ''
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 
'identity' value 'castiana'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 
'bgscan' value 'simple:30:-65:300'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 
'proactive_key_caching' value '1'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Connection 
disconnected (reason -3)
  Sep 30 23:31:06 castiana NetworkManager[25815]:   (wlan0): supplicant 
interface state: associated -> disconnected
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Failed to 
GDBus.Error:fi.w1.wpa_supplicant1.NotConnected: This interface is not 
connected: disconnect.
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Failed to 
GDBus.Error:fi.w1.wpa_supplicant1.NotConnected: This interface is not 
connected: disconnect.
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: set interface 
ap_scan to 1
  Sep 30 23:31:06 castiana NetworkManager[25815]:   (wlan0): supplicant 
interface state: disconnected -> scanning
  Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: SME: Trying to 
authenticate with 24:a4:3c:c8:69:03 (SSID='stgraber.net-secure' freq=2412 MHz)
  Sep 30 23:31:07 castiana kernel: [102903.079940] wlan0: authenticate with 
24:a4:3c:c8:69:03
  Sep 30 23:31:07 castiana kernel: [102903.085128] wlan0: send auth to 
24:a4:3c:c8:69:03 (try 1/3)
  Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: Trying to associate 
with 24:a4:3c:c8:69:03 (SSID='stgraber.net-secure' freq=2412 MHz)
  Sep 30 23:31:07 castiana NetworkManager[25815]:   (wlan0): supplicant 
interface state: scanning -> authenticating
  Sep 30 23:31:07 castiana kernel: [102903.086942] wlan0: authenticated
  Sep 30 23:31:07 castiana kernel: [102903.090103] wlan0: associate with 
24:a4:3c:c8:69:03 (try 1/3)
  Sep 30 23:31:07 castiana NetworkManager[25815]:   (wlan0): supplicant 
interface state: authenticating -> associating
  Sep 30 23:31:07 castiana kernel: [102903.101962] wlan0: RX AssocResp from 
24:a4:3c:c8:69:03 (capab=0x411 status=0 aid=1)
  Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: Associated with 
24:a4:3c:c8:69:03
  Sep 30 23:31:07 castiana kernel: [102903.103701] wlan0: associated
  Sep 30 23:31:07 castiana NetworkManager[25815]:   (wlan0): supplicant 
interface state: associating -> associated
  Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: CTRL-EVENT-EAP-STARTED 
EAP authentication started
  Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: 
CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=13
  Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: CTRL-EVENT-EAP-METHOD 
EAP vendor 0 method 13 (TLS) selected
  Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: 
CTRL-EVENT-EAP-PEER-CERT depth=2 
subject='/C=CA/ST=Quebec/L=Montreal/O=stgraber.net/OU=Internal 
Infrastructure/CN=stgraber.net Root CA/name=stgraber.net Infrastructure Root 
CA/emailAddress=stgra...@stgraber.org' 
hash=87b9750baadddac7f05164d7fde3a0eb3d3efe0c948b430a3ecd093c629956e9
  Sep 30 23:3

[Touch-packages] [Bug 1505261] [NEW] /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene:11:QQmlTypeCompiler::compile:QQmlTypeData::compile:QQmlTypeData::done:QQmlDataBlob::tryDone:QQmlDataLoader::setData

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding qtdeclarative-opensource-src.  This problem was most recently
seen with version 5.4.1-1ubuntu10, the problem page at
https://errors.ubuntu.com/problem/161d8198780e2dc76fdd08a6e652889e7953cef3
contains more details.

** Affects: qtdeclarative-opensource-src (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: vivid

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

Title:
  /usr/lib/arm-linux-
  
gnueabihf/qt5/bin/qmlscene:11:QQmlTypeCompiler::compile:QQmlTypeData::compile:QQmlTypeData::done:QQmlDataBlob::tryDone:QQmlDataLoader::setData

Status in qtdeclarative-opensource-src package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding qtdeclarative-opensource-src.  This problem was most
  recently seen with version 5.4.1-1ubuntu10, the problem page at
  https://errors.ubuntu.com/problem/161d8198780e2dc76fdd08a6e652889e7953cef3
  contains more details.

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

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

[Touch-packages] [Bug 1505197] Re: AdaptivePageLayout doesn't handle errors in QML of loaded pages

[Launchpad Bug Tracker]

** Branch linked: lp:~ubuntu-sdk-team/ubuntu-ui-toolkit/incubateNull

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

Title:
  AdaptivePageLayout doesn't handle errors in QML of loaded pages

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

Bug description:
  If a Page within AdaptivePageLayout has errors like type errors or
  invalid syntax you will get the following cryptic message:

  QQmlComponent: Component is not ready
  
file:///home/rumo/bau/uut.staging/qml/Ubuntu/Components/1.3/PageWrapperUtils.js:76:
 TypeError: Cannot read property 'status' of null

  It's unhelpfully pointing toward an internal component of the APL and
  nothing hints at the actual source of the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1505197/+subscriptions

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

[Touch-packages] [Bug 1483882] Re: init-script does not control slave dnsmasq

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

Title:
  init-script does not control slave dnsmasq

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  `service network-manager stop` does not kill the slave dnsmasq
  process.

  I expected changes that I made to files in
  `/etc/NetworkManager/dnsmasq.d/` to come into effect when I used
  NetworkManager's init script to restart it.

  But the dnsmasq process is not controlled from the init-script.

  I know that the inclusion of dnsmasq in NetworkManager has raised some
  controversy (bug #993298).

  Fixing this issue may help alleviate that somewhat, perhaps?

  In any case, I think this should be fixed. Seems like an easy fix to
  me. Just make sure that the slave dnsmasq, if exists (as it can be
  disabled), is sent some kill signal.

  Any thoughts?

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: network-manager 0.9.10.0-4ubuntu21
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  ApportVersion: 2.18-0ubuntu6
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Aug 11 23:25:37 2015
  IfupdownConfig:
   auto lo
   iface lo inet loopback
   
   #auto eth1
   #iface eth1 inet dhcp
  InstallationDate: Installed on 2010-10-12 (1764 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  IpRoute:
   default via 192.168.0.1 dev eth0  proto static  metric 100 
   192.168.0.0/24 dev eth0  proto kernel  scope link  metric 100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to wily on 2014-11-11 (273 days ago)
  nmcli-dev:
   DEVICETYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   eth0  ethernet  connected/org/freedesktop/NetworkManager/Devices/2  
wire to router  fc8584db-811e-4099-acbf-93f53c51b3ef  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   eth1  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  
--  ----
 
   vboxnet1  ethernet  unmanaged/org/freedesktop/NetworkManager/Devices/3  
--  ----
 
   loloopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  
--  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1244578] Re: lightdm-session runs xrdb with -nocpp option

[Robert Ancell]

** Tags removed: verification-needed-vivid
** Tags added: verification-done-vivid

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

Title:
  lightdm-session runs xrdb with -nocpp option

Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Precise:
  Fix Committed
Status in lightdm source package in Trusty:
  Fix Released
Status in lightdm source package in Utopic:
  Fix Committed
Status in lightdm source package in Vivid:
  Fix Committed

Bug description:
  [Impact]

  lightdm-session runs xrdb for .Xresources file with the -nocpp option
  (Line 37 and 43), which prevents the xrdb from preprocessing the
  .Xresources file. Many configurations like the popular solarized color
  theme (https://github.com/solarized/xresources/blob/master/solarized)
  use this and you find some complaints about in on the internet

  https://bbs.archlinux.org/viewtopic.php?id=164108
  https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1163129
  
http://superuser.com/questions/655857/urxvt-uses-pink-instead-of-solarized-until-i-run-xrdb-xresources/656213

  I don't see a reason for not using the preprocessor and so did the
  editor of Xsession (the option is not used in
  /etc/X11/Xsession.d/30x11-common_xresources)

  [Test Case]

   - Install solarized theme
  https://github.com/solarized/xresources/blob/master/solarized

  - Load default Xresources file (xrdb < .XDefaults )

  - Now every macro supported by CPP will not work.

  
  [Regression Potential] 

  * No regression potential advised, small (0.001%) load average increase
  on startup time because of enabling Cpp.

  [Solution]

  Backport default wily session to older releases.

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

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

[Touch-packages] [Bug 1500768] Re: python3.4.3 SRU break requests

[Cory Benfield]

Hi folks, I'm a requests and urllib3 maintainer.

Looks like you're running into urllib3 issue #385. This was fixed in
urllib3 1.8.3 by the changelog. However, it should be a simple matter to
backport the relevant patch from #385, which should get your systems
working again.

[0]: https://github.com/shazow/urllib3/pull/385

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

Title:
  python3.4.3 SRU break requests

Status in python3.4 package in Ubuntu:
  Invalid
Status in python3.4 source package in Trusty:
  Triaged

Bug description:
  Sicne the upgade to python 3.4.3 on trusty, I'm getting this error when using 
a squid proxy:
  
https://jenkins.qa.ubuntu.com/view/All/job/udtc-trusty-tests/1946/label=ps-trusty-desktop-amd64-1,type=large/testReport/tests.large.test_android/AndroidSDKTests/test_default_android_sdk_install/

  The code is using python-requests, with verify=True for ssl connection
  (default). Some tests are testing that invalid certificates are
  rejected:  https://github.com/ubuntu/ubuntu-
  make/blob/master/umake/network/download_center.py#L129

  Rerunning the same code with previous trusty package (3.4.0~trusty1)
  doesn't show up this issue. It seems that SNI is broken for the trusty
  version of python3-requests with 3.4.3. (See the FAQ http://www
  .python-requests.org/en/latest/community/faq/ with "What are “hostname
  doesn’t match” errors?" and the stackoverflow question.

  I did run a test, grabbing requests 2.7 and backporting it to trusty
  (I needed to as well to take python3-urllib3 willy version).

  So, 3.4.3 has an incompatible change for existing projects and people
  with proxys are starting to see some breakage like in
  https://bugs.launchpad.net/ubuntu/+source/ubuntu-make/+bug/1499890.

  Can we get it fix somehow, reverting the incompatible change breaking
  SNI (I wonder if this is "Changed in version 3.4.3: This class now
  performs all the necessary certificate and hostname checks by default.
  To revert to the previous, unverified, behavior
  ssl._create_unverified_context() can be passed to the context
  parameter." in https://docs.python.org/3/library/http.client.html or
  something else) so that existing code can either get a new compatible
  python-requests or avoid incompatible changes in python 3.4.3?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1500768/+subscriptions

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

[Touch-packages] [Bug 1501588] Re: Wily's wpasupplicant frequently fails on WPA enterprise networks

[Jean-Louis Dupond]

I'm also running Wily since a week, and I'm unable to connect to my corporate 
WiFi anymore.
I did a downgrade to the wpa-supplicant version in Debian Sid (2.3-2.1) and the 
connection works fine again.

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

Title:
  Wily's wpasupplicant frequently fails on WPA enterprise networks

Status in wpa package in Ubuntu:
  New

Bug description:
  Ever since I upgraded from vivid to wily on my laptop, I'm running
  into problems when connecting to my home WPA2 enterprise network.

  Typically the first connection immediately after the driver is loaded
  works as expected, however any further reconnection and the occasional
  roaming between APs cause wpasupplicant to freeze entirely requiring
  me to kill it and most often also reload my wireless driver to get
  things working again.

  ## A failed (hanging) association looks like:
  Sep 30 23:31:06 castiana NetworkManager[25815]:   (wlan0): Activation: 
(wifi) connection 'stgraber.net-secure' has security, and secrets exist.  No 
new secrets needed.
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 'ssid' 
value 'stgraber.net-secure'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 
'scan_ssid' value '1'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 
'key_mgmt' value 'WPA-EAP'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 'eap' 
value 'TLS'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 
'fragment_size' value '1300'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 
'ca_cert' value '/home/stgraber/data/certs/stgraber-radius/ca.crt'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 
'private_key' value '/home/stgraber/data/certs/stgraber-radius/castiana.p12'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 
'private_key_passwd' value ''
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 
'identity' value 'castiana'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 
'bgscan' value 'simple:30:-65:300'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 
'proactive_key_caching' value '1'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Connection 
disconnected (reason -3)
  Sep 30 23:31:06 castiana NetworkManager[25815]:   (wlan0): supplicant 
interface state: associated -> disconnected
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Failed to 
GDBus.Error:fi.w1.wpa_supplicant1.NotConnected: This interface is not 
connected: disconnect.
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Failed to 
GDBus.Error:fi.w1.wpa_supplicant1.NotConnected: This interface is not 
connected: disconnect.
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: set interface 
ap_scan to 1
  Sep 30 23:31:06 castiana NetworkManager[25815]:   (wlan0): supplicant 
interface state: disconnected -> scanning
  Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: SME: Trying to 
authenticate with 24:a4:3c:c8:69:03 (SSID='stgraber.net-secure' freq=2412 MHz)
  Sep 30 23:31:07 castiana kernel: [102903.079940] wlan0: authenticate with 
24:a4:3c:c8:69:03
  Sep 30 23:31:07 castiana kernel: [102903.085128] wlan0: send auth to 
24:a4:3c:c8:69:03 (try 1/3)
  Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: Trying to associate 
with 24:a4:3c:c8:69:03 (SSID='stgraber.net-secure' freq=2412 MHz)
  Sep 30 23:31:07 castiana NetworkManager[25815]:   (wlan0): supplicant 
interface state: scanning -> authenticating
  Sep 30 23:31:07 castiana kernel: [102903.086942] wlan0: authenticated
  Sep 30 23:31:07 castiana kernel: [102903.090103] wlan0: associate with 
24:a4:3c:c8:69:03 (try 1/3)
  Sep 30 23:31:07 castiana NetworkManager[25815]:   (wlan0): supplicant 
interface state: authenticating -> associating
  Sep 30 23:31:07 castiana kernel: [102903.101962] wlan0: RX AssocResp from 
24:a4:3c:c8:69:03 (capab=0x411 status=0 aid=1)
  Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: Associated with 
24:a4:3c:c8:69:03
  Sep 30 23:31:07 castiana kernel: [102903.103701] wlan0: associated
  Sep 30 23:31:07 castiana NetworkManager[25815]:   (wlan0): supplicant 
interface state: associating -> associated
  Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: CTRL-EVENT-EAP-STARTED 
EAP authentication started
  Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: 
CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=13
  Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: CTRL-EVENT-EAP-METHOD 
EAP vendor 0 method 13 (TLS) selected
  Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: 
CTRL-EVENT-EAP-PEER-CERT depth=2 
subject='/C=CA/ST=Quebec/L=Montreal/O=stgraber.net/OU=Internal 
Infrastructure/CN=stgraber.net Root CA/name=stgraber.net Infrastructure Root 
CA/emailAddress=stgra...@stgraber.org' 
hash=87b9750baadddac7f05164d7fde3a0eb3d3efe0c9

[Touch-packages] [Bug 1495178] Re: Failed to set wall message, ignoring: Message recipient disconnected from message bus without replying

[Martin Pitt]

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

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

Title:
  Failed to set wall message, ignoring: Message recipient disconnected
  from message bus without replying

Status in systemd package in Ubuntu:
  In Progress

Bug description:
  Tried to shutdonw in 3 min 
  got this message.
   repeatable  happened yesterday as well
  15.04

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: systemd 225-1ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Sat Sep 12 22:54:23 2015
  ExecutablePath: /lib/systemd/systemd-logind
  InstallationDate: Installed on 2015-01-29 (226 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 10117
  ProcCmdline: /lib/systemd/systemd-logind
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic 
root=UUID=94709fac-8bfa-41bf-8d29-24abdd9f77cc ro drm.debug=0xe plymouth:debug
  SegvAnalysis:
   Segfault happened at: 0x7f1002cbc6fa :movdqu (%rax),%xmm12
   PC (0x7f1002cbc6fa) ok
   source "(%rax)" (0x55907c00) not located in a known VMA region (needed 
readable region)!
   destination "%xmm12" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: systemd
  StacktraceTop:
   strlen () at ../sysdeps/x86_64/strlen.S:106
   __GI___strdup (s=0x55907c00 ) at strdup.c:41
   ?? ()
   ?? ()
   ?? ()
  Title: systemd-logind crashed with SIGSEGV in strlen()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 11/05/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: I7KT31AUS
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058 STD
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.modalias: 
dmi:bvnLENOVO:bvrI7KT31AUS:bd11/05/2013:svnLENOVO:pn10117:pvrLenovoH535:rvnLENOVO:rn:rvr31900058STD:cvnLENOVO:ct3:cvr:
  dmi.product.name: 10117
  dmi.product.version: Lenovo H535
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1467609] Re: vibrations on MSI gt72 2qe scren

[guillaume le louet]

Just posting here to close it : The bug is no more present. Maybe last
versions of kernel did correct it ?

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

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

Title:
  vibrations on MSI gt72 2qe scren

Status in xorg package in Ubuntu:
  Fix Released

Bug description:
  With the nvidia proprietary drivers (ex. nvidia 352 from their site)
  it works good for the external screen I have, but now the integrated
  screen is vibrating as per the attached screenshot. As you can notice,
  lines are shifted to left/right on several positions of the screen. It
  makes the use of the screen very unpleasant. So I usually switch it
  off.

  WORKAROUND: Use nouveau.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
  Uname: Linux 3.19.0-21-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  352.21  Tue Jun  9 21:53:31 
PDT 2015
   GCC version:  gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13)
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jun 22 18:40:33 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.19.0-15-generic, x86_64: installed
   bbswitch, 0.7, 3.19.0-21-generic, x86_64: installed
   nvidia-352, 352.21, 3.19.0-21-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GM204M [GeForce GTX 980M] [10de:13d7] (rev a1) (prog-if 
00 [VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1129]
  InstallationDate: Installed on 2015-06-19 (2 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Micro-Star International Co., Ltd. GT72 2QE
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-21-generic 
root=UUID=4fabaada-02c5-4230-a634-0b88cf228b5f ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1781IMS.10H
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1781
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.C
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10H:bd11/21/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QE:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: GT72 2QE
  dmi.product.version: REV:0.C
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  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.61+git20150614.97be70b4-0ubuntu0ricotz~vivid
  version.libgl1-mesa-dri: libgl1-mesa-dri 
10.6.0~git20150616+10.6.5d327b37-0ubuntu0ricotz~vivid
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 
10.6.0~git20150616+10.6.5d327b37-0ubuntu0ricotz~vivid
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.99+git20150521.d64a13eb-0ubuntu0ricotz~vivid
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150528.fb1643f0-0ubuntu0sarvatt~vivid
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11+git20150528.27234dbe-0ubuntu0sarvatt~vivid
  xserver.bootTime: Mon Jun 22 18:11:59 2015
  xserver.configfile: default
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.17.1-0ubuntu3

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

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

[Touch-packages] [Bug 1449282] Re: xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0

[Robert Ancell]

I've patched the vivid / wily versions since we know that X.org 1.17 is
used. We still need to decide how to fix this for the LightDM project in
a generic way.

** Changed in: lightdm (Ubuntu Vivid)
   Status: Triaged => Fix Committed

** Changed in: lightdm (Ubuntu Wily)
   Status: Triaged => Fix Committed

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

Title:
  xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0

Status in Light Display Manager:
  Triaged
Status in lightdm package in Ubuntu:
  Fix Committed
Status in lightdm source package in Vivid:
  Fix Committed
Status in lightdm source package in Wily:
  Fix Committed

Bug description:
  [Impact]
  xserver-allow-tcp=true option no longer works with X.org 1.17.

  [Test Case]
  1. Edit /etc/lightdm/lightdm.conf and set [SeatDefaults] 
xserver-allow-tcp=true
  2. Start LightDM
  3. Attempt to connect to the X server using TCP

  Expected result:
  Able to connect

  Observed result:
  Unable to connect

  [Regression potential]
  Low. X.org changed their default behaviour from listen by default to listen 
if "-listen tcp" is passed as a command line flag. This is just the equivalent 
change in LightDM. Since this is a new flag to X.org if a user was to use 
another X server there is a risk it would not understand that flag. However it 
seems unlikely since X.org is the only actively developed X server.

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

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

[Touch-packages] [Bug 1505164] Re: Ubuntu Docker images include packages deleted from trusty-updates

[Mark Henwood]

Thank you @racb for taking the time to look into this and reassign it
correctly - apols for my clumsy assignment.

Dan @daniel-thewatkins - thanks dude.

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

Title:
  Ubuntu Docker images include packages deleted from trusty-updates

Status in docker.io package in Ubuntu:
  In Progress
Status in mod-wsgi package in Ubuntu:
  Invalid
Status in python3.4 package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce (using a docker container):

  $ docker pull ubuntu:trusty

  $ docker run --rm -it ubuntu:trusty /bin/bash

  # lsb_release -rd
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04

  # apt-get update

  # apt-get install python3.4
  python3.4 is already the newest version.

  # python3 --version
  Python 3.4.3

  # dpkg -l python3.4
  ii  python3.4 3.4.3-1ubuntu1~14.0

  # apt-get install apache2
  ...

  # apt-get install libapache2-mod-wsgi-py3
  The following packages have unmet dependencies:
   libapache2-mod-wsgi-py3 : Depends: libpython3.4 (>= 3.4~b1) but it is not 
going to be installed
  E: Unable to correct problems, you have held broken packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1505164/+subscriptions

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

[Touch-packages] [Bug 1473269] Re: Wily login screen shows an all black notification bubble

[Lars Uebernickel]

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

** Changed in: notify-osd (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: notify-osd (Ubuntu)
 Assignee: (unassigned) => Lars Uebernickel (larsu)

** Branch linked: lp:~larsu/notify-osd/lp1473269

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

Title:
  Wily login screen shows an all black notification bubble

Status in gtk+3.0 package in Ubuntu:
  Opinion
Status in notify-osd package in Ubuntu:
  In Progress

Bug description:
  Wily login screen shows an all black notification bubble. No idea what
  it says, obviously.

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

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

[Touch-packages] [Bug 1504496] Re: package lxc 1.1.4-0ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Nick Moffitt]

I was hitting problems with lxc on just normal package upgrades in vivid
earlier, but I was able to dpkg --configure -a this problem away and
finish out the release upgrade by hand (apt-get dist-upgrade (noop),
apt-get autoremove, reboot)

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

Title:
  package lxc 1.1.4-0ubuntu0.1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in lxc package in Ubuntu:
  New

Bug description:
  A dist-upgrade failed in the maintainer scripts while trying to
  restart the lxc networking, I think:

  Reading package lists... Done
  The following NEW packages will be installed:
linux-image-3.19.0-31-generic{a} linux-image-extra-3.19.0-31-generic{a} 
linux-signed-image-3.19.0-31-generic{a} 
  The following packages will be upgraded:
juju juju-core juju-local liblxc1 linux-image-generic linux-libc-dev 
linux-signed-image-generic 
lxc lxc-templates mutt python3-lxc 
  The following packages are RECOMMENDED but will NOT be installed:
citadel-mta courier-mta dma dma:i386 esmtp-run exim4-daemon-heavy 
exim4-daemon-light 
lsb-invalid-mta masqmail msmtp-mta nullmailer opensmtpd postfix qmail-run 
sendmail-bin ssmtp 
xmail 
  11 packages upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
  Need to get 0 B/90.5 MB of archives. After unpacking 259 MB will be used.
  Do you want to continue? [Y/n/?] 
  (Reading database ... 357199 files and directories currently installed.)
  Preparing to unpack .../python3-lxc_1.1.4-0ubuntu0.1_amd64.deb ...
  Unpacking python3-lxc (1.1.4-0ubuntu0.1) over (1.1.2-0ubuntu3.2) ...
  Preparing to unpack .../lxc-templates_1.1.4-0ubuntu0.1_amd64.deb ...
  Unpacking lxc-templates (1.1.4-0ubuntu0.1) over (1.1.2-0ubuntu3.2) ...
  Preparing to unpack .../liblxc1_1.1.4-0ubuntu0.1_amd64.deb ...
  Unpacking liblxc1 (1.1.4-0ubuntu0.1) over (1.1.2-0ubuntu3.2) ...
  Preparing to unpack .../lxc_1.1.4-0ubuntu0.1_amd64.deb ...
  Unpacking lxc (1.1.4-0ubuntu0.1) over (1.1.2-0ubuntu3.2) ...
  Selecting previously unselected package linux-image-3.19.0-31-generic.
  Preparing to unpack .../linux-image-3.19.0-31-generic_3.19.0-31.36_amd64.deb 
...
  Done.
  Unpacking linux-image-3.19.0-31-generic (3.19.0-31.36) ...
  Selecting previously unselected package linux-image-extra-3.19.0-31-generic.
  Preparing to unpack 
.../linux-image-extra-3.19.0-31-generic_3.19.0-31.36_amd64.deb ...
  Unpacking linux-image-extra-3.19.0-31-generic (3.19.0-31.36) ...
  Preparing to unpack .../linux-image-generic_3.19.0.31.30_amd64.deb ...
  Unpacking linux-image-generic (3.19.0.31.30) over (3.19.0.30.29) ...
  Preparing to unpack .../linux-libc-dev_3.19.0-31.36_amd64.deb ...
  Unpacking linux-libc-dev:amd64 (3.19.0-31.36) over (3.19.0-30.34) ...
  Selecting previously unselected package linux-signed-image-3.19.0-31-generic.
  Preparing to unpack 
.../linux-signed-image-3.19.0-31-generic_3.19.0-31.36_amd64.deb ...
  Unpacking linux-signed-image-3.19.0-31-generic (3.19.0-31.36) ...
  Preparing to unpack .../linux-signed-image-generic_3.19.0.31.30_amd64.deb ...
  Unpacking linux-signed-image-generic (3.19.0.31.30) over (3.19.0.30.29) ...
  Preparing to unpack .../mutt_1.5.23-3ubuntu1_amd64.deb ...
  Unpacking mutt (1.5.23-3ubuntu1) over (1.5.23-3) ...
  Preparing to unpack .../juju-core_1.24.6-0ubuntu1~15.04.1_amd64.deb ...
  Unpacking juju-core (1.24.6-0ubuntu1~15.04.1) over 
(1.23.2-0ubuntu1~14.10.1~juju1) ...
  Preparing to unpack .../juju_1.24.6-0ubuntu1~15.04.1_all.deb ...
  Unpacking juju (1.24.6-0ubuntu1~15.04.1) over (1.23.2-0ubuntu1~14.10.1~juju1) 
...
  Preparing to unpack .../juju-local_1.24.6-0ubuntu1~15.04.1_all.deb ...
  Unpacking juju-local (1.24.6-0ubuntu1~15.04.1) over 
(1.23.2-0ubuntu1~14.10.1~juju1) ...
  Processing triggers for man-db (2.7.0.2-5) ...
  Processing triggers for ureadahead (0.100.0-19) ...
  ureadahead will be reprofiled on next reboot
  Processing triggers for doc-base (0.10.6) ...
  Processing 1 changed doc-base file...
  Registering documents with scrollkeeper...
  Processing triggers for gnome-menus (3.10.1-0ubuntu5) ...
  Processing triggers for desktop-file-utils (0.22-1ubuntu3) ...
  Processing triggers for bamfdaemon (0.5.1+15.04.20150202-0ubuntu1) ...
  Rebuilding /usr/share/applications/bamf-2.index...
  Processing triggers for mime-support (3.58ubuntu1) ...
  Setting up liblxc1 (1.1.4-0ubuntu0.1) ...
  Setting up python3-lxc (1.1.4-0ubuntu0.1) ...
  Setting up lxc (1.1.4-0ubuntu0.1) ...
  Installing new version of config file 
/etc/apparmor.d/lxc/lxc-default-with-nesting ...
  Installing new version of config file /etc/bash_completion.d/lxc ...
  Installing new version of config file /etc/init/lxc.conf ...
  Job for lxc-net.service failed. See "systemctl status lxc-net.service" and 
"journalctl -xe" for details.
  invoke-rc.d: initscript

[Touch-packages] [Bug 1505251] Re: package libgcc-4.8-dev (not installed) failed to install/upgrade: Extrahierte Daten für »./usr/lib/gcc/x86_64-linux-gnu/4.8/libquadmath.a« können nicht nach »/usr/li

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package libgcc-4.8-dev (not installed) failed to install/upgrade:
  Extrahierte Daten für »./usr/lib/gcc/x86_64-linux-
  gnu/4.8/libquadmath.a« können nicht nach »/usr/lib/gcc/x86_64-linux-
  gnu/4.8/libquadmath.a.dpkg-new« kopiert werden: Unerwartetes Ende der
  Datei oder des Datenstroms

Status in gcc-4.8 package in Ubuntu:
  New

Bug description:
  i upgrade my server from ubunti 12.04.5 LTS to 14.04.1 LTS automatically.
  During the upgrade process, the process stop with this information.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libgcc-4.8-dev (not installed)
  ProcVersionSignature: Ubuntu 3.11.0-26.45~precise1-generic 3.11.10.12
  Uname: Linux 3.11.0-26-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: amd64
  Date: Mon Oct 12 15:50:09 2015
  DpkgHistoryLog:
   Start-Date: 2015-10-12  15:50:07
   Install: libgcc-4.8-dev:amd64 (4.8.4-2ubuntu1~14.04, automatic)
   Upgrade: initramfs-tools:amd64 (0.99ubuntu13.5, 0.103ubuntu4.2)
  DuplicateSignature: package:libgcc-4.8-dev:(not installed):Extrahierte Daten 
für »./usr/lib/gcc/x86_64-linux-gnu/4.8/libquadmath.a« können nicht nach 
»/usr/lib/gcc/x86_64-linux-gnu/4.8/libquadmath.a.dpkg-new« kopiert werden: 
Unerwartetes Ende der Datei oder des Datenstroms
  EcryptfsInUse: Yes
  ErrorMessage: Extrahierte Daten für 
»./usr/lib/gcc/x86_64-linux-gnu/4.8/libquadmath.a« können nicht nach 
»/usr/lib/gcc/x86_64-linux-gnu/4.8/libquadmath.a.dpkg-new« kopiert werden: 
Unerwartetes Ende der Datei oder des Datenstroms
  InstallationDate: Installed on 2014-03-07 (584 days ago)
  InstallationMedia: Ubuntu-Server 12.04.4 LTS "Precise Pangolin" - Release 
amd64 (20140204)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.4
   apt  1.0.1ubuntu2.10
  SourcePackage: gcc-4.8
  Title: package libgcc-4.8-dev (not installed) failed to install/upgrade: 
Extrahierte Daten für »./usr/lib/gcc/x86_64-linux-gnu/4.8/libquadmath.a« können 
nicht nach »/usr/lib/gcc/x86_64-linux-gnu/4.8/libquadmath.a.dpkg-new« kopiert 
werden: Unerwartetes Ende der Datei oder des Datenstroms
  UpgradeStatus: Upgraded to trusty on 2015-10-12 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1505251/+subscriptions

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

[Touch-packages] [Bug 199094] Re: hdparm.conf settings (other than apm) are lost on suspend/resume?

[Graeme Hewson]

Also:

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

** Bug watch added: Debian Bug tracker #725284
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725284

** Bug watch added: Debian Bug tracker #779412
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779412

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

Title:
  hdparm.conf settings (other than apm) are lost on suspend/resume?

Status in hdparm package in Ubuntu:
  Confirmed
Status in pm-utils package in Ubuntu:
  Confirmed

Bug description:
  Update: This is on Intrepid.

  Problem:
  - Hard disks lose settings (the APM level for example) when they are powered 
off.
  => Settings in /etc/hdparm.conf persist only from boot to next suspend.

  Expected:
  All settings in /etc/hdparm.conf should persist across 
{suspend,hibernate}/resume.

  Effects:
  At least the apm setting in hdparm.conf is lost. This makes 
https://bugs.launchpad.net/ubuntu/+source/acpi-support/+bug/59695 so bad - 
users are not able to set the apm value without messing with their system 
(installing stuff from forums) because of this bug.

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

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

[Touch-packages] [Bug 1505164] Re: Ubuntu Docker images include packages deleted from trusty-updates

[Dan Watkins]

For avoidance of doubt, this problem was caused by the actions taken to
remedy bug 1500768. Workarounds to get an instance unstuck can be found
there.


Dan

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

Title:
  Ubuntu Docker images include packages deleted from trusty-updates

Status in docker.io package in Ubuntu:
  In Progress
Status in mod-wsgi package in Ubuntu:
  Invalid
Status in python3.4 package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce (using a docker container):

  $ docker pull ubuntu:trusty

  $ docker run --rm -it ubuntu:trusty /bin/bash

  # lsb_release -rd
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04

  # apt-get update

  # apt-get install python3.4
  python3.4 is already the newest version.

  # python3 --version
  Python 3.4.3

  # dpkg -l python3.4
  ii  python3.4 3.4.3-1ubuntu1~14.0

  # apt-get install apache2
  ...

  # apt-get install libapache2-mod-wsgi-py3
  The following packages have unmet dependencies:
   libapache2-mod-wsgi-py3 : Depends: libpython3.4 (>= 3.4~b1) but it is not 
going to be installed
  E: Unable to correct problems, you have held broken packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1505164/+subscriptions

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

[Touch-packages] [Bug 1500768] Re: python3.4.3 SRU break requests

[Ben Howard]

See Bug #1505164:

# apt-get install libapache2-mod-wsgi-py3
The following packages have unmet dependencies:
 libapache2-mod-wsgi-py3 : Depends: libpython3.4 (>= 3.4~b1) but it is not 
going to be installed
E: Unable to correct problems, you have held broken packages.

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

Title:
  python3.4.3 SRU break requests

Status in python3.4 package in Ubuntu:
  Invalid
Status in python3.4 source package in Trusty:
  Triaged

Bug description:
  Sicne the upgade to python 3.4.3 on trusty, I'm getting this error when using 
a squid proxy:
  
https://jenkins.qa.ubuntu.com/view/All/job/udtc-trusty-tests/1946/label=ps-trusty-desktop-amd64-1,type=large/testReport/tests.large.test_android/AndroidSDKTests/test_default_android_sdk_install/

  The code is using python-requests, with verify=True for ssl connection
  (default). Some tests are testing that invalid certificates are
  rejected:  https://github.com/ubuntu/ubuntu-
  make/blob/master/umake/network/download_center.py#L129

  Rerunning the same code with previous trusty package (3.4.0~trusty1)
  doesn't show up this issue. It seems that SNI is broken for the trusty
  version of python3-requests with 3.4.3. (See the FAQ http://www
  .python-requests.org/en/latest/community/faq/ with "What are “hostname
  doesn’t match” errors?" and the stackoverflow question.

  I did run a test, grabbing requests 2.7 and backporting it to trusty
  (I needed to as well to take python3-urllib3 willy version).

  So, 3.4.3 has an incompatible change for existing projects and people
  with proxys are starting to see some breakage like in
  https://bugs.launchpad.net/ubuntu/+source/ubuntu-make/+bug/1499890.

  Can we get it fix somehow, reverting the incompatible change breaking
  SNI (I wonder if this is "Changed in version 3.4.3: This class now
  performs all the necessary certificate and hostname checks by default.
  To revert to the previous, unverified, behavior
  ssl._create_unverified_context() can be passed to the context
  parameter." in https://docs.python.org/3/library/http.client.html or
  something else) so that existing code can either get a new compatible
  python-requests or avoid incompatible changes in python 3.4.3?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1500768/+subscriptions

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

[Touch-packages] [Bug 1505164] Re: Ubuntu Docker images include packages deleted from trusty-updates

[Dan Watkins]

Hi Mark, all,

At some point, Python 3.4.3 was released to the trusty archive. However,
a (serious) regression was found, and it was removed from the archive.
This image was built after the release, but before the removal, which
means it has ended up in a state that apt-get doesn't understand.

The fix for this is simply to release a new image; I have pinged Tianon,
the awesome community member who handles the Docker Ubuntu images, on
IRC (and subscribed him to this bug) to make that happen. He's based on
the West Coast, so the earliest we'll see this happen is in a few hours.

Apologies for the broken state that things ended up in; we strive to
produce images of the highest quality, and don't like it when we fall
short of that.


Thanks,

Dan

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

Title:
  Ubuntu Docker images include packages deleted from trusty-updates

Status in docker.io package in Ubuntu:
  In Progress
Status in mod-wsgi package in Ubuntu:
  Invalid
Status in python3.4 package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce (using a docker container):

  $ docker pull ubuntu:trusty

  $ docker run --rm -it ubuntu:trusty /bin/bash

  # lsb_release -rd
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04

  # apt-get update

  # apt-get install python3.4
  python3.4 is already the newest version.

  # python3 --version
  Python 3.4.3

  # dpkg -l python3.4
  ii  python3.4 3.4.3-1ubuntu1~14.0

  # apt-get install apache2
  ...

  # apt-get install libapache2-mod-wsgi-py3
  The following packages have unmet dependencies:
   libapache2-mod-wsgi-py3 : Depends: libpython3.4 (>= 3.4~b1) but it is not 
going to be installed
  E: Unable to correct problems, you have held broken packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1505164/+subscriptions

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

[Touch-packages] [Bug 1505251] [NEW] package libgcc-4.8-dev (not installed) failed to install/upgrade: Extrahierte Daten für »./usr/lib/gcc/x86_64-linux-gnu/4.8/libquadmath.a« können nicht nach »/usr/

[det]

Public bug reported:

i upgrade my server from ubunti 12.04.5 LTS to 14.04.1 LTS automatically.
During the upgrade process, the process stop with this information.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libgcc-4.8-dev (not installed)
ProcVersionSignature: Ubuntu 3.11.0-26.45~precise1-generic 3.11.10.12
Uname: Linux 3.11.0-26-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.15
Architecture: amd64
Date: Mon Oct 12 15:50:09 2015
DpkgHistoryLog:
 Start-Date: 2015-10-12  15:50:07
 Install: libgcc-4.8-dev:amd64 (4.8.4-2ubuntu1~14.04, automatic)
 Upgrade: initramfs-tools:amd64 (0.99ubuntu13.5, 0.103ubuntu4.2)
DuplicateSignature: package:libgcc-4.8-dev:(not installed):Extrahierte Daten 
für »./usr/lib/gcc/x86_64-linux-gnu/4.8/libquadmath.a« können nicht nach 
»/usr/lib/gcc/x86_64-linux-gnu/4.8/libquadmath.a.dpkg-new« kopiert werden: 
Unerwartetes Ende der Datei oder des Datenstroms
EcryptfsInUse: Yes
ErrorMessage: Extrahierte Daten für 
»./usr/lib/gcc/x86_64-linux-gnu/4.8/libquadmath.a« können nicht nach 
»/usr/lib/gcc/x86_64-linux-gnu/4.8/libquadmath.a.dpkg-new« kopiert werden: 
Unerwartetes Ende der Datei oder des Datenstroms
InstallationDate: Installed on 2014-03-07 (584 days ago)
InstallationMedia: Ubuntu-Server 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.4
 apt  1.0.1ubuntu2.10
SourcePackage: gcc-4.8
Title: package libgcc-4.8-dev (not installed) failed to install/upgrade: 
Extrahierte Daten für »./usr/lib/gcc/x86_64-linux-gnu/4.8/libquadmath.a« können 
nicht nach »/usr/lib/gcc/x86_64-linux-gnu/4.8/libquadmath.a.dpkg-new« kopiert 
werden: Unerwartetes Ende der Datei oder des Datenstroms
UpgradeStatus: Upgraded to trusty on 2015-10-12 (0 days ago)

** Affects: gcc-4.8 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package trusty

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

Title:
  package libgcc-4.8-dev (not installed) failed to install/upgrade:
  Extrahierte Daten für »./usr/lib/gcc/x86_64-linux-
  gnu/4.8/libquadmath.a« können nicht nach »/usr/lib/gcc/x86_64-linux-
  gnu/4.8/libquadmath.a.dpkg-new« kopiert werden: Unerwartetes Ende der
  Datei oder des Datenstroms

Status in gcc-4.8 package in Ubuntu:
  New

Bug description:
  i upgrade my server from ubunti 12.04.5 LTS to 14.04.1 LTS automatically.
  During the upgrade process, the process stop with this information.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libgcc-4.8-dev (not installed)
  ProcVersionSignature: Ubuntu 3.11.0-26.45~precise1-generic 3.11.10.12
  Uname: Linux 3.11.0-26-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: amd64
  Date: Mon Oct 12 15:50:09 2015
  DpkgHistoryLog:
   Start-Date: 2015-10-12  15:50:07
   Install: libgcc-4.8-dev:amd64 (4.8.4-2ubuntu1~14.04, automatic)
   Upgrade: initramfs-tools:amd64 (0.99ubuntu13.5, 0.103ubuntu4.2)
  DuplicateSignature: package:libgcc-4.8-dev:(not installed):Extrahierte Daten 
für »./usr/lib/gcc/x86_64-linux-gnu/4.8/libquadmath.a« können nicht nach 
»/usr/lib/gcc/x86_64-linux-gnu/4.8/libquadmath.a.dpkg-new« kopiert werden: 
Unerwartetes Ende der Datei oder des Datenstroms
  EcryptfsInUse: Yes
  ErrorMessage: Extrahierte Daten für 
»./usr/lib/gcc/x86_64-linux-gnu/4.8/libquadmath.a« können nicht nach 
»/usr/lib/gcc/x86_64-linux-gnu/4.8/libquadmath.a.dpkg-new« kopiert werden: 
Unerwartetes Ende der Datei oder des Datenstroms
  InstallationDate: Installed on 2014-03-07 (584 days ago)
  InstallationMedia: Ubuntu-Server 12.04.4 LTS "Precise Pangolin" - Release 
amd64 (20140204)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.4
   apt  1.0.1ubuntu2.10
  SourcePackage: gcc-4.8
  Title: package libgcc-4.8-dev (not installed) failed to install/upgrade: 
Extrahierte Daten für »./usr/lib/gcc/x86_64-linux-gnu/4.8/libquadmath.a« können 
nicht nach »/usr/lib/gcc/x86_64-linux-gnu/4.8/libquadmath.a.dpkg-new« kopiert 
werden: Unerwartetes Ende der Datei oder des Datenstroms
  UpgradeStatus: Upgraded to trusty on 2015-10-12 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1505251/+subscriptions

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

[Touch-packages] [Bug 1504600] Re: Need libpython3.4 (version 3.4.2) for Trustee (for Libreoffice)

[Bob]

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

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

Title:
  Need libpython3.4 (version 3.4.2) for Trustee (for Libreoffice)

Status in libreoffice package in Ubuntu:
  New
Status in python3.4 package in Ubuntu:
  Confirmed

Bug description:
  The current version of libpython for trustee is 3.4.0.

  That means that libreoffice will not build on ubuntu 14.0.4.3.
  (because Libreoffice requires python3-uno, which in turns requires
  libpython3.4 (>= 3.4.2).

  The dependency chain is this:

  > sudo apt-get install libreoffice
  > -- Fails due to Depends: python3-uno (>= 4.0~)
  > sudo apt-get install python3-uno
  > -- Fails due to: python3-uno : Depends: libpython3.4 (>= 3.4.2) but
  > 3.4.0-2ubuntu1.1 is to be installed

  So until we can get an updated version of libpython, Libreoffice won't
  work on Ubuntu 14.04.

  Could we please get an updated version of libpython3.4 for Trustee?

  Thank you,

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

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

[Touch-packages] [Bug 1505164] Re: Ubuntu Docker images include packages deleted from trusty-updates

[Ben Howard]

This was caused by Bug #1500768.

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

Title:
  Ubuntu Docker images include packages deleted from trusty-updates

Status in docker.io package in Ubuntu:
  In Progress
Status in mod-wsgi package in Ubuntu:
  Invalid
Status in python3.4 package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce (using a docker container):

  $ docker pull ubuntu:trusty

  $ docker run --rm -it ubuntu:trusty /bin/bash

  # lsb_release -rd
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04

  # apt-get update

  # apt-get install python3.4
  python3.4 is already the newest version.

  # python3 --version
  Python 3.4.3

  # dpkg -l python3.4
  ii  python3.4 3.4.3-1ubuntu1~14.0

  # apt-get install apache2
  ...

  # apt-get install libapache2-mod-wsgi-py3
  The following packages have unmet dependencies:
   libapache2-mod-wsgi-py3 : Depends: libpython3.4 (>= 3.4~b1) but it is not 
going to be installed
  E: Unable to correct problems, you have held broken packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1505164/+subscriptions

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

[Touch-packages] [Bug 1505164] Re: Ubuntu Docker images include packages deleted from trusty-updates

[Robie Basak]

** Summary changed:

- Ubuntu Docker images incorrectly include packages from trusty-proposed
+ Ubuntu Docker images include packages deleted from trusty-updates

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

Title:
  Ubuntu Docker images include packages deleted from trusty-updates

Status in docker.io package in Ubuntu:
  In Progress
Status in mod-wsgi package in Ubuntu:
  Invalid
Status in python3.4 package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce (using a docker container):

  $ docker pull ubuntu:trusty

  $ docker run --rm -it ubuntu:trusty /bin/bash

  # lsb_release -rd
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04

  # apt-get update

  # apt-get install python3.4
  python3.4 is already the newest version.

  # python3 --version
  Python 3.4.3

  # dpkg -l python3.4
  ii  python3.4 3.4.3-1ubuntu1~14.0

  # apt-get install apache2
  ...

  # apt-get install libapache2-mod-wsgi-py3
  The following packages have unmet dependencies:
   libapache2-mod-wsgi-py3 : Depends: libpython3.4 (>= 3.4~b1) but it is not 
going to be installed
  E: Unable to correct problems, you have held broken packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1505164/+subscriptions

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

[Touch-packages] [Bug 1449282] Re: xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0

[Robert Ancell]

** Description changed:

- In order to enable X11 forwarding from an external host you must
- explicitly set the Xserver to listen by overriding the xserver-command.
- Previously you could set the xserver-allow-tcp=true and it would do this
- automatically.
+ [Impact]
+ xserver-allow-tcp=true option no longer works with X.org 1.17.
  
- I would have expected this change in behaviour to show up in
- README.Debian.gz but since it did not, perhaps the functionality of the
- "xserver-allow-tcp=true" is not working as expected.
+ [Test Case]
+ 1. Edit /etc/lightdm/lightdm.conf and set [SeatDefaults] 
xserver-allow-tcp=true
+ 2. Start LightDM
+ 3. Attempt to connect to the X server using TCP
  
- Below shows my before (no TCP listener on 6000) and after (TCP listener
- on 6000) lightdm.conf to re-enable the listener after the 15.04 upgrade.
+ Expected result:
+ Able to connect
  
- Before (14.10):
+ Observed result:
+ Unable to connect
  
- ~$ cat /etc/lightdm/lightdm.conf
- 
- [SeatDefaults]
- xserver-allow-tcp=true
- 
- After (15.04):
- 
- ~$ cat /etc/lightdm/lightdm.conf
- 
- [SeatDefaults]
- xserver-command=X -core -listen tcp
- xserver-allow-tcp=true
- 
- ProblemType: Bug
- DistroRelease: Ubuntu 15.04
- Package: lightdm 1.14.0-0ubuntu2
- ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
- Uname: Linux 3.19.0-15-generic x86_64
- ApportVersion: 2.17.2-0ubuntu1
- Architecture: amd64
- CurrentDesktop: Unity
- Date: Mon Apr 27 17:33:26 2015
- InstallationDate: Installed on 2014-12-18 (130 days ago)
- InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
- LightdmConfig:
-  [SeatDefaults]
-  xserver-command=X -core -listen tcp
-  xserver-allow-tcp=true
- SourcePackage: lightdm
- UpgradeStatus: Upgraded to vivid on 2015-04-27 (0 days ago)
- 
- ###
- i haven't /etc/lightdm/lightdm.conf
- when i tried to create it and write the lines above it was worse, my system 
didin't start.
- after a few experiment i have found something that works:
- i change my /usr/share/lightdm/lightdm.conf.d/50-xserver-command.conf
- 
- before it was:
- [SeatDefaults]
- # Dump core
- xserver-command=X -core
- 
- now:
- [SeatDefaults]
- # Dump core
- xserver-command=X -core
- xserver-allow-tcp=true
- 
- and it works!
+ [Regression potential]
+ Low. X.org changed their default behaviour from listen by default to listen 
if "-listen tcp" is passed as a command line flag. This is just the equivalent 
change in LightDM. Since this is a new flag to X.org if a user was to use 
another X server there is a risk it would not understand that flag. However it 
seems unlikely since X.org is the only actively developed X server.

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

Title:
  xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0

Status in Light Display Manager:
  Triaged
Status in lightdm package in Ubuntu:
  Triaged
Status in lightdm source package in Vivid:
  Triaged
Status in lightdm source package in Wily:
  Triaged

Bug description:
  [Impact]
  xserver-allow-tcp=true option no longer works with X.org 1.17.

  [Test Case]
  1. Edit /etc/lightdm/lightdm.conf and set [SeatDefaults] 
xserver-allow-tcp=true
  2. Start LightDM
  3. Attempt to connect to the X server using TCP

  Expected result:
  Able to connect

  Observed result:
  Unable to connect

  [Regression potential]
  Low. X.org changed their default behaviour from listen by default to listen 
if "-listen tcp" is passed as a command line flag. This is just the equivalent 
change in LightDM. Since this is a new flag to X.org if a user was to use 
another X server there is a risk it would not understand that flag. However it 
seems unlikely since X.org is the only actively developed X server.

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

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

[Touch-packages] [Bug 1505164] Re: Ubuntu Docker images incorrectly include packages from trusty-proposed

[Dan Watkins]

** Changed in: docker.io (Ubuntu)
 Assignee: (unassigned) => Dan Watkins (daniel-thewatkins)

** Changed in: docker.io (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  Ubuntu Docker images include packages deleted from trusty-updates

Status in docker.io package in Ubuntu:
  In Progress
Status in mod-wsgi package in Ubuntu:
  Invalid
Status in python3.4 package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce (using a docker container):

  $ docker pull ubuntu:trusty

  $ docker run --rm -it ubuntu:trusty /bin/bash

  # lsb_release -rd
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04

  # apt-get update

  # apt-get install python3.4
  python3.4 is already the newest version.

  # python3 --version
  Python 3.4.3

  # dpkg -l python3.4
  ii  python3.4 3.4.3-1ubuntu1~14.0

  # apt-get install apache2
  ...

  # apt-get install libapache2-mod-wsgi-py3
  The following packages have unmet dependencies:
   libapache2-mod-wsgi-py3 : Depends: libpython3.4 (>= 3.4~b1) but it is not 
going to be installed
  E: Unable to correct problems, you have held broken packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1505164/+subscriptions

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

[Touch-packages] [Bug 1505164] Re: Ubuntu Docker images incorrectly include packages from trusty-proposed

[Ben Howard]

Scratch comment #3.

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

Title:
  Ubuntu Docker images incorrectly include packages from trusty-proposed

Status in docker.io package in Ubuntu:
  In Progress
Status in mod-wsgi package in Ubuntu:
  Invalid
Status in python3.4 package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce (using a docker container):

  $ docker pull ubuntu:trusty

  $ docker run --rm -it ubuntu:trusty /bin/bash

  # lsb_release -rd
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04

  # apt-get update

  # apt-get install python3.4
  python3.4 is already the newest version.

  # python3 --version
  Python 3.4.3

  # dpkg -l python3.4
  ii  python3.4 3.4.3-1ubuntu1~14.0

  # apt-get install apache2
  ...

  # apt-get install libapache2-mod-wsgi-py3
  The following packages have unmet dependencies:
   libapache2-mod-wsgi-py3 : Depends: libpython3.4 (>= 3.4~b1) but it is not 
going to be installed
  E: Unable to correct problems, you have held broken packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1505164/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-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 did not suspend after incoming text message

[Pat McGowan]

Actually this is from the previous log, this is repeated thousand of
times

Oct 11 05:16:54 ubuntu-phablet kernel: [82715.640877] active wakeup source: 
MT662x
Oct 11 05:16:54 ubuntu-phablet kernel: [82715.640896] active wakeup source: 
EINT wakelock
Oct 11 05:16:55 ubuntu-phablet kernel: [82716.655950] active wakeup source: 
MT662x
Oct 11 05:16:57 ubuntu-phablet kernel: [82718.728492] PM: suspend entry 
2015-10-11 09:16:57.752096077 UTC
Oct 11 05:16:57 ubuntu-phablet kernel: [82718.728512] PM: Syncing filesystems 
... done.
Oct 11 05:16:57 ubuntu-phablet kernel: [82718.759147] Freezing user space 
processes ... 
Oct 11 05:16:57 ubuntu-phablet kernel: [82718.760219] active wakeup source: 
MT662x
Oct 11 05:16:57 ubuntu-phablet kernel: [82718.760250] active wakeup source: 
EINT wakelock
Oct 11 05:16:57 ubuntu-phablet kernel: [82718.760260] 
Oct 11 05:16:57 ubuntu-phablet kernel: [82718.760275] Freezing of tasks aborted 
after 0.001 seconds (20 tasks refusing to freeze, wq_busy=0):
Oct 11 05:16:57 ubuntu-phablet kernel: [82718.760315] 
Oct 11 05:16:57 ubuntu-phablet kernel: [82718.760323] Restarting tasks ... done.
Oct 11 05:16:57 ubuntu-phablet kernel: [82718.762588] msdc: 
0,mmc_schedule_delayed_work ret= 1
Oct 11 05:16:57 ubuntu-phablet kernel: [82718.762658] PM: suspend exit 
2015-10-11 09:16:57.786272461 UTC
Oct 11 05:16:57 ubuntu-phablet kernel: [82718.762692] WQ warning! work 
(try_to_suspend, c0f38b2c) execute more than 1 sec, time: 3121820846 ns
Oct 11 05:16:57 ubuntu-phablet kernel: [82718.762946] active wakeup source: 
MT662x
Oct 11 05:16:57 ubuntu-phablet kernel: [82718.762966] active wakeup source: 
EINT wakelock
Oct 11 05:16:58 ubuntu-phablet kernel: [82719.775967] active wakeup source: 
MT662x
Oct 11 05:17:00 ubuntu-phablet kernel: [82721.868468] PM: suspend entry 
2015-10-11 09:17:00.892072692 UTC
Oct 11 05:17:00 ubuntu-phablet kernel: [82721.868487] PM: Syncing filesystems 
... done.
Oct 11 05:17:00 ubuntu-phablet kernel: [82721.895468] Freezing user space 
processes ... 
Oct 11 05:17:00 ubuntu-phablet kernel: [82721.896555] active wakeup source: 
MT662x
Oct 11 05:17:00 ubuntu-phablet kernel: [82721.896585] 
Oct 11 05:17:00 ubuntu-phablet kernel: [82721.896600] Freezing of tasks aborted 
after 0.001 seconds (20 tasks refusing to freeze, wq_busy=0):
Oct 11 05:17:00 ubuntu-phablet kernel: [82721.896641] 
Oct 11 05:17:00 ubuntu-phablet kernel: [82721.896649] Restarting tasks ... done.
Oct 11 05:17:00 ubuntu-phablet kernel: [82721.898617] msdc: 
0,mmc_schedule_delayed_work ret= 1
Oct 11 05:17:00 ubuntu-phablet kernel: [82721.898685] PM: suspend exit 
2015-10-11 09:17:00.922299385 UTC
Oct 11 05:17:00 ubuntu-phablet kernel: [82721.898717] WQ warning! work 
(try_to_suspend, c0f38b2c) execute more than 1 sec, time: 3135993923 ns
Oct 11 05:17:00 ubuntu-phablet kernel: [82721.898757] active wakeup source: 
MT662x
Oct 11 05:17:01 ubuntu-phablet CRON[11160]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)


** Summary changed:

- Phone did not suspend after incoming text message
+ Phone did not suspend

** Description changed:

- From the syslog, see that at 16:47 an incoming SMS wakes the phone. The
- phone was in a pocket. From that point on the phone does not suspend and
- battery drains overnight. You can see NM scan requests every two mins.
+ Noticed a quick batter drain, no idea what was keeping it awake all day
+ and night.

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

Title:
  Phone did not suspend

Status in Canonical System Image:
  New
Status in powerd package in Ubuntu:
  New

Bug description:
  Noticed a quick batter drain, no idea what was keeping it awake all
  day and night.

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

[Touch-packages] [Bug 199094] Re: hdparm.conf settings (other than apm) are lost on suspend/resume?

[Torsten Krah]

"Nice" thread about systemd + hdparm:

http://lists.freedesktop.org/archives/systemd-
devel/2012-June/005595.html

So it seems users should write their own udev rules to get this working
:-| or some custom distro specific stuff. Its really weird that this one
is still around after that many years which have passed now.

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

Title:
  hdparm.conf settings (other than apm) are lost on suspend/resume?

Status in hdparm package in Ubuntu:
  Confirmed
Status in pm-utils package in Ubuntu:
  Confirmed

Bug description:
  Update: This is on Intrepid.

  Problem:
  - Hard disks lose settings (the APM level for example) when they are powered 
off.
  => Settings in /etc/hdparm.conf persist only from boot to next suspend.

  Expected:
  All settings in /etc/hdparm.conf should persist across 
{suspend,hibernate}/resume.

  Effects:
  At least the apm setting in hdparm.conf is lost. This makes 
https://bugs.launchpad.net/ubuntu/+source/acpi-support/+bug/59695 so bad - 
users are not able to set the apm value without messing with their system 
(installing stuff from forums) because of this bug.

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

-- 
Mailing list: https://launchpad.net/~touch-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 did not suspend after incoming text message

[Pat McGowan]

The phone was plugged in from around 5pm to 8pm. Quick drain can be seen
from that time on. (The graph incorrectly shows a gain in charge from
2pm which is not possible, I assume it missed some events.

** Attachment added: "graph.png"
   
https://bugs.launchpad.net/ubuntu/+source/powerd/+bug/1505241/+attachment/4492518/+files/graph.png

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => kevin gunn (kgunn72)

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

Title:
  Phone did not suspend

Status in Canonical System Image:
  New
Status in powerd package in Ubuntu:
  New

Bug description:
  Noticed a quick batter drain, no idea what was keeping it awake all
  day and night.

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

[Touch-packages] [Bug 1505241] Re: Phone did not suspend after incoming text message

[Pat McGowan]

The phone was plugged in from around 5pm to 8pm. Quick drain can be seen
from that time on. (The graph incorrectly shows a gain in charge from
2pm which is not possible, I assume it missed some events.

** Attachment added: "graph.png"
   
https://bugs.launchpad.net/ubuntu/+source/powerd/+bug/1505241/+attachment/4492517/+files/graph.png

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

Title:
  Phone did not suspend

Status in Canonical System Image:
  New
Status in powerd package in Ubuntu:
  New

Bug description:
  Noticed a quick batter drain, no idea what was keeping it awake all
  day and night.

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