[Touch-packages] [Bug 1352322] Re: gdebi FTBFS when the locale is not en_US

[Bug Watch Updater]

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

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

Title:
  gdebi FTBFS when the locale is not en_US

Status in “gdebi” package in Ubuntu:
  New
Status in “gdebi” package in Debian:
  Fix Released

Bug description:
  System: Xubuntu 14.04.
  Current gdebi version: 0.9.5.3ubuntu2 (from trusty-updates).

  Steps to reproduce:

  1. Have some non-en_US locale currently set in your system. I have ru_RU for 
example.
  2. sudo apt-get install dpkg-dev devscripts build-essential
  3. sudo apt-get build-dep gdebi
  4. apt-get source gdebi
  5. cd gdebi-0.9.5.3ubuntu2
  6. debuild -us -uc

  The build process will fail as shown in the first attachment.

  Now try the same with locale set to en_US (but do a cleanup first):

  7. debuild clean
  8. LC_ALL=en_US.UTF-8 debuild -us -uc

  The build process will succeed as shown in the second attachment.

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

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

[Touch-packages] [Bug 1241972] Re: Drag and drop from Dash to Desktop doesn't work

[Moris]

** Changed in: nautilus (Ubuntu)
 Assignee: (unassigned) => Moris (nerimoris)

** Changed in: unity (Ubuntu)
 Assignee: (unassigned) => Moris (nerimoris)

** Changed in: chromium-browser
 Assignee: (unassigned) => Moris (nerimoris)

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

Title:
  Drag and drop from Dash to Desktop doesn't work

Status in Chromium Browser:
  New
Status in One Hundred Papercuts:
  Triaged
Status in Unity:
  Triaged
Status in Unity 7.1 series:
  Won't Fix
Status in Unity 7.2 series:
  Triaged
Status in “nautilus” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  When you try to drag and drop an app from Dash (both from app lens and
  home lens) to Desktop, system display an error and the shortcut isn't
  created.

  The error is:
  Error while copying - There was an error getting information about "/".
  More details: The specified location is not supported

  Then there are four buttons: "Cancel" - "Skip all" - "Skip" - "Retry".

  Way to reproduce:
  - Open the dash
  - Drag an app icon and drop on desktop

  What happend:
  - An error is raised

  What expected:
  - A shortcut is created

  With file, music and photo is all ok.

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

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

[Touch-packages] [Bug 1077972] Re: doc-base files refer to non existent files

[Laurent Bonnaud]

The bug is still in Ubuntu 14.10:

# install-docs --install-all
Unregistering 118 doc-base files, re-registering 122 doc-base files...
Error in `/usr/share/doc-base/gstreamer-1.0-manual', line 11: all `Format' 
sections are invalid.
Error in `/usr/share/doc-base/gstreamer-1.0-pwg', line 14: all `Format' 
sections are invalid.
Error in `/usr/share/doc-base/gstreamer-1.0-faq', line 9: all `Format' sections 
are invalid.

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

Title:
  doc-base files refer to non existent files

Status in “gstreamer1.0” package in Ubuntu:
  New

Bug description:
  Here is the problem:

  # install-docs --install-all
  Unregistering 249 doc-base files, re-registering 252 doc-base files...
  Error in `/usr/share/doc-base/gstreamer-0.10-faq', line 9: all `Format' 
sections are invalid.
  Error in `/usr/share/doc-base/gstreamer-0.10-pwg', line 14: all `Format' 
sections are invalid.
  Error in `/usr/share/doc-base/gstreamer-0.10-manual', line 11: all `Format' 
sections are invalid.
  Note: `install-docs --verbose --check file_name' may give more details about 
the above errors.
  Registering documents with scrollkeeper...

  # install-docs --verbose --check /usr/share/doc-base/gstreamer-0.10-faq
  Warning in `/usr/share/doc-base/gstreamer-0.10-faq', line 9: file 
`/usr/share/doc/gstreamer0.10-doc/faq/html/index.html' does not exist.
  Error in `/usr/share/doc-base/gstreamer-0.10-faq', line 9: all `Format' 
sections are invalid.
  /usr/share/doc-base/gstreamer-0.10-faq: Fatal error found, the file won't be 
registered.

  # install-docs --verbose --check /usr/share/doc-base/gstreamer-0.10-pwg 
  Warning in `/usr/share/doc-base/gstreamer-0.10-pwg', line 14: file 
`/usr/share/doc/gstreamer0.10-doc/pwg/html/index.html' does not exist.
  Error in `/usr/share/doc-base/gstreamer-0.10-pwg', line 14: all `Format' 
sections are invalid.
  /usr/share/doc-base/gstreamer-0.10-pwg: Fatal error found, the file won't be 
registered.

  # install-docs --verbose --check /usr/share/doc-base/gstreamer-0.10-manual 
  Warning in `/usr/share/doc-base/gstreamer-0.10-manual', line 11: file 
`/usr/share/doc/gstreamer0.10-doc/manual/html/index.html' does not exist.
  Error in `/usr/share/doc-base/gstreamer-0.10-manual', line 11: all `Format' 
sections are invalid.
  /usr/share/doc-base/gstreamer-0.10-manual: Fatal error found, the file won't 
be registered.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: gstreamer0.10-doc 0.10.36-1ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-18.18-lowlatency 3.5.7
  Uname: Linux 3.5.0-18-lowlatency i686
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: i386
  Date: Mon Nov 12 15:59:43 2012
  EcryptfsInUse: Yes
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: gstreamer0.10
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1077972/+subscriptions

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

[Touch-packages] [Bug 1077972] Re: doc-base files refer to non existent files

[Laurent Bonnaud]

The strange thing is that Debian and Ubuntu have the same files:

# md5sum /usr/share/doc-base/gstreamer-1.0-*
  
c30c50172086674db3e1ecdeb4150b96  /usr/share/doc-base/gstreamer-1.0-core-ref
698fe14c4bd0c21c2d9e8e34711ae0b6  /usr/share/doc-base/gstreamer-1.0-faq
20f0d44ade6836951f4766ea8f50f425  /usr/share/doc-base/gstreamer-1.0-libs-ref
8d9c98d598b717443b4b98607c797c31  /usr/share/doc-base/gstreamer-1.0-manual
ab016c7b29faa89dbba92dd273cdd4da  /usr/share/doc-base/gstreamer-1.0-pwg

the same doc-base version:

ii  doc-base 0.10.6all
utilities to manage online documentation

but errors are reported in Ubuntu and not in Debian.

Does someone have a clue why?

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

Title:
  doc-base files refer to non existent files

Status in “gstreamer1.0” package in Ubuntu:
  New

Bug description:
  Here is the problem:

  # install-docs --install-all
  Unregistering 249 doc-base files, re-registering 252 doc-base files...
  Error in `/usr/share/doc-base/gstreamer-0.10-faq', line 9: all `Format' 
sections are invalid.
  Error in `/usr/share/doc-base/gstreamer-0.10-pwg', line 14: all `Format' 
sections are invalid.
  Error in `/usr/share/doc-base/gstreamer-0.10-manual', line 11: all `Format' 
sections are invalid.
  Note: `install-docs --verbose --check file_name' may give more details about 
the above errors.
  Registering documents with scrollkeeper...

  # install-docs --verbose --check /usr/share/doc-base/gstreamer-0.10-faq
  Warning in `/usr/share/doc-base/gstreamer-0.10-faq', line 9: file 
`/usr/share/doc/gstreamer0.10-doc/faq/html/index.html' does not exist.
  Error in `/usr/share/doc-base/gstreamer-0.10-faq', line 9: all `Format' 
sections are invalid.
  /usr/share/doc-base/gstreamer-0.10-faq: Fatal error found, the file won't be 
registered.

  # install-docs --verbose --check /usr/share/doc-base/gstreamer-0.10-pwg 
  Warning in `/usr/share/doc-base/gstreamer-0.10-pwg', line 14: file 
`/usr/share/doc/gstreamer0.10-doc/pwg/html/index.html' does not exist.
  Error in `/usr/share/doc-base/gstreamer-0.10-pwg', line 14: all `Format' 
sections are invalid.
  /usr/share/doc-base/gstreamer-0.10-pwg: Fatal error found, the file won't be 
registered.

  # install-docs --verbose --check /usr/share/doc-base/gstreamer-0.10-manual 
  Warning in `/usr/share/doc-base/gstreamer-0.10-manual', line 11: file 
`/usr/share/doc/gstreamer0.10-doc/manual/html/index.html' does not exist.
  Error in `/usr/share/doc-base/gstreamer-0.10-manual', line 11: all `Format' 
sections are invalid.
  /usr/share/doc-base/gstreamer-0.10-manual: Fatal error found, the file won't 
be registered.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: gstreamer0.10-doc 0.10.36-1ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-18.18-lowlatency 3.5.7
  Uname: Linux 3.5.0-18-lowlatency i686
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: i386
  Date: Mon Nov 12 15:59:43 2012
  EcryptfsInUse: Yes
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: gstreamer0.10
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1077972/+subscriptions

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

[Touch-packages] [Bug 1356468] Re: TOP RTM CRASHER: /usr/bin/trust-stored-skeleton:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::__cxa_rethrow:__shared_co

[Chris Gagnon]

** Summary changed:

- 
/usr/bin/trust-stored-skeleton:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::__cxa_rethrow:__shared_count
+ TOP RTM CRASHER: 
/usr/bin/trust-stored-skeleton:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::__cxa_rethrow:__shared_count

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

Title:
  TOP RTM CRASHER: /usr/bin/trust-stored-
  
skeleton:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::__cxa_rethrow:__shared_count

Status in “location-service” package in Ubuntu:
  Fix Released
Status in “trust-store” package in Ubuntu:
  Fix Released
Status in “location-service” package in Ubuntu RTM:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding trust-store.  This problem was most recently seen with
  version 1.0.0+14.10.20140807-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/009a6dd4d6c0da7571b0283d16f4cdf40c9d3da5
  contains more details.

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

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

[Touch-packages] [Bug 1376324] Re: /usr/sbin/unity-system-compositor:*** Error in `unity-system-compositor': free(): invalid pointer: ADDR ***

[Alan Griffiths]

This looks as though the send_response_result member of
ProtobufResponder is no longer valid (i.e. that the ProtobufResponder at
this=0xac900574 has likely been freed).

I'm not sure what sequence of events would lead to a send_response()
message being passed to a no-longer valid ProtobufResponder - but is
likely to be a race within Mir between closing the connection and the
compositor::BufferQueue::give_buffer_to_client() sending a buffer to the
client.

I'll audit the Mir code in this area.

** Changed in: mir
   Status: New => In Progress

** Changed in: mir
 Assignee: (unassigned) => Alan Griffiths (alan-griffiths)

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

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

Title:
  /usr/sbin/unity-system-compositor:*** Error in `unity-system-
  compositor': free(): invalid pointer: ADDR ***

Status in Mir:
  In Progress
Status in Unity System Compositor:
  New
Status in “mir” package in Ubuntu:
  New
Status in “unity-system-compositor” package in Ubuntu:
  New

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

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

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

[Touch-packages] [Bug 1370258] Re: /usr/bin/mtp-server:11:core::dbus::asio::Executor::on_dbus_remove_timeout:_dbus_timeout_list_remove_timeout:protected_change_timeout:_dbus_connection_remove_timeout_

[Chris Gagnon]

This is the number 2 crasher on the 20140930 image, marking critical

** Changed in: mtp (Ubuntu)
   Importance: High => Critical

** Changed in: mtp (Ubuntu)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)

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

Title:
  /usr/bin/mtp-
  
server:11:core::dbus::asio::Executor::on_dbus_remove_timeout:_dbus_timeout_list_remove_timeout:protected_change_timeout:_dbus_connection_remove_timeout_unlocked:reply_handler_timeout

Status in “mtp” package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding mtp.  This problem was most recently seen with version
  0.0.4+14.10.20140909-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/71f5a56922c283d830c3bf676a408a826b680c4e
  contains more details.

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

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

[Touch-packages] [Bug 1371086] Re: mtp-server crashed with SIGSEGV

[Chris Gagnon]

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

** This bug has been marked a duplicate of bug 1370258
   
/usr/bin/mtp-server:11:core::dbus::asio::Executor::on_dbus_remove_timeout:_dbus_timeout_list_remove_timeout:protected_change_timeout:_dbus_connection_remove_timeout_unlocked:reply_handler_timeout

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

Title:
  mtp-server crashed with SIGSEGV

Status in “mtp” package in Ubuntu:
  New

Bug description:
  image 245

  It just crashed, I was not transferring anything. I am seeing frequent
  disconnects over mtp today, so that might also be related.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: mtp-server 0.0.4+14.10.20140909-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: armhf
  CurrentDesktop: Unity
  Date: Thu Sep 18 12:24:20 2014
  ExecutablePath: /usr/bin/mtp-server
  ExecutableTimestamp: 1410235042
  InstallationDate: Installed on 2014-09-18 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140918-020205)
  ProcCmdline: /usr/bin/mtp-server
  ProcCwd: /home/phablet
  SegvAnalysis: Skipped: missing required field "Disassembly"
  Signal: 11
  SourcePackage: mtp
  Stacktrace:
   #0  0xb6de78d6 in ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
   No symbol table info available.
   #1  0xb6b91a9c in ?? () from /lib/arm-linux-gnueabihf/libdbus-1.so.3
   No symbol table info available.
   Backtrace stopped: previous frame identical to this frame (corrupt stack?)
  StacktraceTop:
   ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
   ?? () from /lib/arm-linux-gnueabihf/libdbus-1.so.3
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip plugdev sudo tty video

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

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

[Touch-packages] [Bug 1375349] Re: Can't launch videos on mako utopic #261

[Alberto Aguirre]

** Changed in: unity-scope-mediascanner
   Status: In Progress => Fix Released

** Changed in: media-hub
   Status: Fix Committed => Fix Released

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

Title:
  Can't launch videos on mako utopic #261

Status in Media Hub:
  Fix Released
Status in Unity Media Scanner Scope:
  Fix Released
Status in “unity-scope-mediascanner” package in Ubuntu:
  Fix Released

Bug description:
  Copy videos to device.
  Scroll to video scope
  Tap on video
  Nothing happens. Crash file created, video doesn't play.

  ProblemType: RecoverableProblem
  DistroRelease: Ubuntu 14.10
  Package: unity8 8.00+14.10.20140926-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: armhf
  BadURL: 
file:///home/phablet/Videos/big_buck_bunny_480p_MPEG4_MP3_25fps_1600K.AVI
  CurrentDesktop: Unity
  Date: Mon Sep 29 17:23:14 2014
  DuplicateSignature: url-dispatcher-bad-url
  ExecutablePath: /usr/bin/unity8-dash
  InstallationDate: Installed on 2014-09-29 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140929-020204)
  LocalLibraries: /android/system/lib/libm.so /android/system/lib/liblog.so 
/android/system/lib/libsync.so /android/system/lib/libgccdemangle.so 
/android/system/lib/libadreno_utils.so 
/android/system/lib/egl/libGLESv2_adreno.so /android/system/lib/libEGL.so 
/android/system/lib/libc.so /android/system/lib/libutils.so 
/android/system/lib/libui.so /android/system/lib/libdsyscalls.so 
/android/system/lib/libcorkscrew.so /android/system/lib/libmemalloc.so 
/android/system/lib/libGLESv1_CM.so /android/system/lib/egl/eglsubAndroid.so 
/android/system/lib/libstlport.so /android/system/lib/libz.so 
/android/system/lib/hw/gralloc.msm8960.so /android/system/lib/libsc-a3xx.so 
/android/system/lib/libcutils.so /android/system/lib/egl/libGLESv1_CM_adreno.so 
/android/system/lib/libGLESv2.so /android/system/lib/libqdutils.so 
/android/system/lib/libGLES_trace.so /android/system/lib/libstdc++.so 
/android/system/lib/libhardware.so /android/system/lib/egl/libEGL_adreno.so 
/android/system/lib/libgsl.so
  ProcCmdline: unity8-dash 
--desktop_file_hint=/usr/share/applications/unity8-dash.desktop
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip plugdev sudo tty video

To manage notifications about this bug go to:
https://bugs.launchpad.net/media-hub/+bug/1375349/+subscriptions

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

[Touch-packages] [Bug 1367459] Re: Messaging app should not rotate upside down

[Zsombor Egri]

Renato, as far as I know unity8 will also rotate. So it is nonsense to
implement something in toolkit then deprecate, because we need to drive
the rotation control between unity and toolkit. Of course, defining the
flags that drive the rotation direction is one thing, that can be done
as well, but I'd rather sync with unity before we do anything.
OrientationHelper can be extend any time, however that is just a temp
solution.

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

Title:
  Messaging app should not rotate upside down

Status in Messaging App:
  Confirmed
Status in Ubuntu UI Toolkit:
  Triaged
Status in “unity8” package in Ubuntu:
  New

Bug description:
  The messaging app should not rotate upside down.
  This can be confuse, and in some cases causes problems  for example the user 
can try to answer a call in the incorrect position.

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

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

[Touch-packages] [Bug 1376344] [NEW] MTP can access locked device data after rebooting

[Richard Huddie]

Public bug reported:

ENVIRONMENT:
Device: ubuntu-rtm/14.09 build 3
Desktop: Ubuntu 14.10

SUMMARY:
MTP can access locked device data after rebooting

STEPS:
1) Ensure device is locked with PIN/passphrase and showing locked greeter
2) Insert USB cable and try to access device content over MTP - No content is 
displayed as expected
3) Reboot device, leaving USB cable connected
4) When device is rebooted and still locked, try and access device content over 
MTP again

EXPECTED RESULT:
It should not be possible to view device content using MTP whilst the device is 
locked

ACTUAL RESULT:
You can copy and view all content on device using MTP whilst device is still 
locked.

** Affects: mtp (Ubuntu)
 Importance: Critical
 Status: New


** Tags: mtp rtm14

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

Title:
  MTP can access locked device data after rebooting

Status in “mtp” package in Ubuntu:
  New

Bug description:
  ENVIRONMENT:
  Device: ubuntu-rtm/14.09 build 3
  Desktop: Ubuntu 14.10

  SUMMARY:
  MTP can access locked device data after rebooting

  STEPS:
  1) Ensure device is locked with PIN/passphrase and showing locked greeter
  2) Insert USB cable and try to access device content over MTP - No content is 
displayed as expected
  3) Reboot device, leaving USB cable connected
  4) When device is rebooted and still locked, try and access device content 
over MTP again

  EXPECTED RESULT:
  It should not be possible to view device content using MTP whilst the device 
is locked

  ACTUAL RESULT:
  You can copy and view all content on device using MTP whilst device is still 
locked.

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

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

[Touch-packages] [Bug 1376346] [NEW] qmlscene crashed with signal 5 in clock_app

[Timo Jyrinki]

Public bug reported:

From
http://ci.ubuntu.com/smokeng/utopic/touch/mako/264:20141001:20140929.1/10758/ubuntu_clock_app/

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: qmlscene 5.3.0-3ubuntu12
Uname: Linux 3.4.0-5-mako armv7l
ApportVersion: 2.14.7-0ubuntu2
Architecture: armhf
CurrentDesktop: Unity
Date: Wed Oct  1 05:04:18 2014
ExecutablePath: /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene
ExecutableTimestamp: 1410860063
InstallationDate: Installed on 2014-10-01 (0 days ago)
InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141001-020204)
ProcCmdline: /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene $@ 
share/qml/ubuntu-clock-app.qml
ProcCwd: /usr/share/click/preinstalled/com.ubuntu.clock/3.1.125
RetraceOutdatedPackages:
 outdated debug symbol package for libroken18-heimdal: package version 
1.6~rc2+dfsg-8 dbgsym version 1.6~git20131207+dfsg-1ubuntu1
 outdated debug symbol package for libhcrypto4-heimdal: package version 
1.6~rc2+dfsg-8 dbgsym version 1.6~git20131207+dfsg-1ubuntu1
 libudev1 version 208-8ubuntu5 required, but 208-8ubuntu6 is available
 outdated debug symbol package for libheimntlm0-heimdal: package version 
1.6~rc2+dfsg-8 dbgsym version 1.6~git20131207+dfsg-1ubuntu1
 outdated debug symbol package for libwind0-heimdal: package version 
1.6~rc2+dfsg-8 dbgsym version 1.6~git20131207+dfsg-1ubuntu1
Signal: 5
SourcePackage: qtdeclarative-opensource-src
StacktraceSource:
 #0  0xb5dde8e6 in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
 #1  0xb5dece5e in raise () from /lib/arm-linux-gnueabihf/libc.so.6
 #2  0xb5b97bf8 in g_logv () from /lib/arm-linux-gnueabihf/libglib-2.0.so.0
 #3  0xb5b97d58 in g_log () from /lib/arm-linux-gnueabihf/libglib-2.0.so.0
 #4  0xb346f1cc in ?? () from /usr/lib/arm-linux-gnueabihf/libgio-2.0.so.0
StacktraceTop: ?? () from /usr/lib/arm-linux-gnueabihf/libgio-2.0.so.0
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm autopilot cdrom dialout dip plugdev sudo tty video

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


** Tags: apport-crash armhf need-armhf-retrace utopic

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

Title:
  qmlscene crashed with signal 5 in clock_app

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

Bug description:
  From
  
http://ci.ubuntu.com/smokeng/utopic/touch/mako/264:20141001:20140929.1/10758/ubuntu_clock_app/

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: qmlscene 5.3.0-3ubuntu12
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: armhf
  CurrentDesktop: Unity
  Date: Wed Oct  1 05:04:18 2014
  ExecutablePath: /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene
  ExecutableTimestamp: 1410860063
  InstallationDate: Installed on 2014-10-01 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141001-020204)
  ProcCmdline: /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene $@ 
share/qml/ubuntu-clock-app.qml
  ProcCwd: /usr/share/click/preinstalled/com.ubuntu.clock/3.1.125
  RetraceOutdatedPackages:
   outdated debug symbol package for libroken18-heimdal: package version 
1.6~rc2+dfsg-8 dbgsym version 1.6~git20131207+dfsg-1ubuntu1
   outdated debug symbol package for libhcrypto4-heimdal: package version 
1.6~rc2+dfsg-8 dbgsym version 1.6~git20131207+dfsg-1ubuntu1
   libudev1 version 208-8ubuntu5 required, but 208-8ubuntu6 is available
   outdated debug symbol package for libheimntlm0-heimdal: package version 
1.6~rc2+dfsg-8 dbgsym version 1.6~git20131207+dfsg-1ubuntu1
   outdated debug symbol package for libwind0-heimdal: package version 
1.6~rc2+dfsg-8 dbgsym version 1.6~git20131207+dfsg-1ubuntu1
  Signal: 5
  SourcePackage: qtdeclarative-opensource-src
  StacktraceSource:
   #0  0xb5dde8e6 in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
   #1  0xb5dece5e in raise () from /lib/arm-linux-gnueabihf/libc.so.6
   #2  0xb5b97bf8 in g_logv () from /lib/arm-linux-gnueabihf/libglib-2.0.so.0
   #3  0xb5b97d58 in g_log () from /lib/arm-linux-gnueabihf/libglib-2.0.so.0
   #4  0xb346f1cc in ?? () from /usr/lib/arm-linux-gnueabihf/libgio-2.0.so.0
  StacktraceTop: ?? () from /usr/lib/arm-linux-gnueabihf/libgio-2.0.so.0
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom dialout dip plugdev sudo tty video

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

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

[Touch-packages] [Bug 1365471] Re: Long-tapping doesn't work on any control

[Zsombor Egri]

Ah, just realised that the bug refers to any component. Actually the
problem is, that this is due to the way a MouseArea works. All
components you listed here are derived from AbstractButton, and that
component also has pressAndHold() signal. Now, that signal is a
forwarded signal from the MouseArea the component uses. And here comes
the problem: MouseArea does NOT emit clicked event if the pressAndHold
signal is connected/implemented. And we have that. So a release after a
long press actually causes a pressAndHold to be emitted, and clicked
signal to be suppressed. This is a behaviour we cannot really change.

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

Title:
  Long-tapping doesn't work on any control

Status in Ubuntu UI Toolkit:
  Triaged
Status in “ubuntu-ui-toolkit” package in Ubuntu:
  Triaged

Bug description:
  Problem occurs with: Ubuntu 14.10 r22
  Does not occur with: iOS 7, Windows Phone 8.0

  1. Long-tap on any control: for example, a button, switch, checkbox, or page 
stack item.
  2. Let go.

  What happens: Nothing.

  What should happen: Unless the control has a specific action for long-
  tapping, it should activate just as if you did a short tap.

  Fixing this would be one way of fixing bug 1289329.

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

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

[Touch-packages] [Bug 1363112] Re: StateSaver is not working on devices

[Zsombor Egri]

Seems QStandardPath has some problems with XDG_RUNTIME_DIR,
investigation continues...

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

Title:
  StateSaver is not working on devices

Status in Ubuntu UI Toolkit:
  Confirmed
Status in “apparmor-easyprof-ubuntu” package in Ubuntu:
  Fix Released
Status in “camera-app” package in Ubuntu:
  Fix Released

Bug description:
  build 212
  The StateSaver is not working anymore on devices, so apps saved state is no 
longer restored when they are relaunched after being killed by oom killer (or 
manually via kill -2)

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

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

[Touch-packages] [Bug 1296114] Re: [desktop] Bluetooth is always enabled after reboot even if it was disabled

[Mathieu Trudel-Lapierre]

Now, one issue we'll need to clear up is exactly which killswitches are
available on the system where this bug appears.

Could you please attach the output of 'rfkill list' to this bug report,
along with the output of 'lsmod' so we know what drivers are used by the
kernel?

Thanks!

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

Title:
  [desktop] Bluetooth is always enabled after reboot even if it was
  disabled

Status in Bluetooth Menu:
  Invalid
Status in “indicator-bluetooth” package in Ubuntu:
  Invalid
Status in “rfkill” package in Ubuntu:
  Incomplete
Status in “urfkill” package in Ubuntu:
  Triaged

Bug description:
  If bluetooth was disabled using the switcher in the bluetooth
  indicator, after reboot it becomes enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-bluetooth 0.0.6+14.04.20140207-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
  Uname: Linux 3.13.0-18-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Mar 22 22:34:52 2014
  InstallationDate: Installed on 2014-01-27 (54 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140124)
  SourcePackage: indicator-bluetooth
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.indicator-bluetooth.log: (bluetooth-wizard:2251): Gtk-DEBUG: 
Connecting to session manager

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

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

[Touch-packages] [Bug 1296114] Re: Bluetooth is always enabled after reboot even if it was disabled

[Mathieu Trudel-Lapierre]

I'm keeping this open because some fixes will still need to happen in
both rfkill and urfkill for this to work properly; just like there will
be at least the need to also start shipping urfkill by default on
desktop before this works better.

One of the issues is that rfkill ships scripts that currently work
fairly well for many systems, but don't work on others because of how
killswitches work on these systems. Once urfkill starts shipping on
desktop, these scripts will also need to be removed.

I'm updating the bug title to denote clearly that this is specifically a
desktop bug; there is a different bug open for touch issues: bug
1376063.

** Summary changed:

- Bluetooth is always enabled after reboot even if it was disabled
+ [desktop] Bluetooth is always enabled after reboot even if it was disabled

** Changed in: rfkill (Ubuntu)
   Status: Triaged => Incomplete

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

Title:
  [desktop] Bluetooth is always enabled after reboot even if it was
  disabled

Status in Bluetooth Menu:
  Invalid
Status in “indicator-bluetooth” package in Ubuntu:
  Invalid
Status in “rfkill” package in Ubuntu:
  Incomplete
Status in “urfkill” package in Ubuntu:
  Triaged

Bug description:
  If bluetooth was disabled using the switcher in the bluetooth
  indicator, after reboot it becomes enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-bluetooth 0.0.6+14.04.20140207-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
  Uname: Linux 3.13.0-18-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Mar 22 22:34:52 2014
  InstallationDate: Installed on 2014-01-27 (54 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140124)
  SourcePackage: indicator-bluetooth
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.indicator-bluetooth.log: (bluetooth-wizard:2251): Gtk-DEBUG: 
Connecting to session manager

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

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

[Touch-packages] [Bug 1376346] Re: qmlscene crashed with signal 5 in clock_app

[Apport retracing service]

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

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 #1376256, 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/1376346/+attachment/4221627/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1376256
   qmlscene crashed with signal 5

** Tags removed: need-armhf-retrace

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

Title:
  qmlscene crashed with signal 5 in clock_app

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

Bug description:
  From
  
http://ci.ubuntu.com/smokeng/utopic/touch/mako/264:20141001:20140929.1/10758/ubuntu_clock_app/

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: qmlscene 5.3.0-3ubuntu12
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: armhf
  CurrentDesktop: Unity
  Date: Wed Oct  1 05:04:18 2014
  ExecutablePath: /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene
  ExecutableTimestamp: 1410860063
  InstallationDate: Installed on 2014-10-01 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141001-020204)
  ProcCmdline: /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene $@ 
share/qml/ubuntu-clock-app.qml
  ProcCwd: /usr/share/click/preinstalled/com.ubuntu.clock/3.1.125
  RetraceOutdatedPackages:
   outdated debug symbol package for libroken18-heimdal: package version 
1.6~rc2+dfsg-8 dbgsym version 1.6~git20131207+dfsg-1ubuntu1
   outdated debug symbol package for libhcrypto4-heimdal: package version 
1.6~rc2+dfsg-8 dbgsym version 1.6~git20131207+dfsg-1ubuntu1
   libudev1 version 208-8ubuntu5 required, but 208-8ubuntu6 is available
   outdated debug symbol package for libheimntlm0-heimdal: package version 
1.6~rc2+dfsg-8 dbgsym version 1.6~git20131207+dfsg-1ubuntu1
   outdated debug symbol package for libwind0-heimdal: package version 
1.6~rc2+dfsg-8 dbgsym version 1.6~git20131207+dfsg-1ubuntu1
  Signal: 5
  SourcePackage: qtdeclarative-opensource-src
  StacktraceSource:
   #0  0xb5dde8e6 in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
   #1  0xb5dece5e in raise () from /lib/arm-linux-gnueabihf/libc.so.6
   #2  0xb5b97bf8 in g_logv () from /lib/arm-linux-gnueabihf/libglib-2.0.so.0
   #3  0xb5b97d58 in g_log () from /lib/arm-linux-gnueabihf/libglib-2.0.so.0
   #4  0xb346f1cc in ?? () from /usr/lib/arm-linux-gnueabihf/libgio-2.0.so.0
  StacktraceTop: ?? () from /usr/lib/arm-linux-gnueabihf/libgio-2.0.so.0
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom dialout dip plugdev sudo tty video

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

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

[Touch-packages] [Bug 1376256] Re: qmlscene crashed with signal 5

[Launchpad Bug Tracker]

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

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

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

Title:
  qmlscene crashed with signal 5

Status in “qtdeclarative-opensource-src” package in Ubuntu:
  Confirmed

Bug description:
  Not really sure what happened. Found the crash file here
  
http://ci.ubuntu.com/smokeng/utopic/touch/mako/264:20141001:20140929.1/10758/ubuntu_clock_app/1761864/

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: qmlscene 5.3.0-3ubuntu12
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: armhf
  CurrentDesktop: Unity
  Date: Wed Oct  1 05:04:18 2014
  ExecutablePath: /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene
  ExecutableTimestamp: 1410860063
  InstallationDate: Installed on 2014-10-01 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141001-020204)
  ProcCmdline: /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene $@ 
share/qml/ubuntu-clock-app.qml
  ProcCwd: /usr/share/click/preinstalled/com.ubuntu.clock/3.1.125
  Signal: 5
  SourcePackage: qtdeclarative-opensource-src
  StacktraceTop: ?? () from /usr/lib/arm-linux-gnueabihf/libgio-2.0.so.0
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom dialout dip plugdev sudo tty video

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

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

[Touch-packages] [Bug 1376281] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From emach...@br.ibm.com 2014-10-01 16:43 EDT---
The gdb packages including the patch were uploaded to:

http://ausgsa.ibm.com/~emachado/public/gdb/lp13656641/

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

Title:
  gdb: "Can't read symbols from system-supplied DSO at 0x3fffb7fa:
  File truncated"

Status in “gdb” package in Ubuntu:
  Confirmed

Bug description:
  ---Problem Description---
  GDB produces an odd message about a failure to read symbols from the system 
DSO when running executables on LE Ubuntu 14.10 with 3.16 kernel.  This is a 
regression from LE Ubuntu 14.04, where the message is not produced.

  Bad case:

  $ uname -r
  3.16.0-6-generic
  $ gdb /bin/ls
  GNU gdb (Ubuntu 7.7.91.20140723-0ubuntu1) 7.7.91.20140723-cvs
  ...
  (gdb) run
  Starting program: /bin/ls 
  Can't read symbols from system-supplied DSO at 0x3fffb7fa: File truncated
  ...
  [Inferior 1 (process 1573) exited normally]
  (gdb) 

  Note the "Can't read symbols..." message.

  Good case (LE Ubuntu 14.04):

  $ uname -r
  3.13.0-32-generic
  $ gdb /bin/ls
  GNU gdb (Ubuntu 7.7-0ubuntu3.2) 7.7
  ...
  (gdb) run
  Starting program: /bin/ls 
  ...
  [Inferior 1 (process 91140) exited normally]
  (gdb)

  I haven't tried on the 3.15 kernel, so I don't know if the problem is
  sensitve to the 3.16 kernel being ELFv2.

   
  ---uname output---
  Linux tul115p1 3.16.0-6-generic #11-Ubuntu SMP Mon Jul 28 02:00:45 UTC 2014 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8286-42A 
   
  ---Steps to Reproduce---
   See description; occurs when running any application under gdb.
   
  The failing output above is with the 3.16 kernel supplied by Ubuntu, so the 
problem happens both with locally-built and Canonical/Ubuntu-supplied kernels 
on 14.10.

  This issue was recently fixed on upstream binutils-gdb:

  https://sourceware.org/ml/gdb-patches/2014-09/msg00594.html

  The attached patch against gdb 7.8-0ubuntu1 for Ubuntu 14.10 fixes the
  issue.

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

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

[Touch-packages] [Bug 1365664] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From emach...@br.ibm.com 2014-10-01 16:45 EDT---
FYI, I rebuilt gdb packages including the aforementioned patch and uploaded 
them to:

http://ausgsa.ibm.com/~emachado/public/gdb/lp13656641/

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

Title:
  gdb source test suites are failing in Ubuntu14.10

Status in “gdb” package in Ubuntu:
  Confirmed

Bug description:
  ---Problem Description---
  gdb source test suites are failing in Ubuntu14.10
   
  Machine Type = P8 
   
  ---Steps to Reproduce---
  Install a P8 system with Power KVM and then install Ubuntu 14.10 guest.
  Then try to build and execute the gdb source test suites as below.

  root@ubuntu:~# apt-get source gdb
  root@ubuntu:~# cd gdb-7.8/
  root@ubuntu:~/gdb-7.8# dpkg-buildpackage -b 2>&1 | tee gdblog

  === gdb Summary ===

  # of expected passes25009
  # of unexpected failures287
  # of unexpected successes   2
  # of expected failures  66
  # of unknown successes  1
  # of known failures 59
  # of unresolved testcases   3
  # of untested testcases 19
  # of unsupported tests  100

   
  ---uname output---
  Linux ubuntu 3.16.0-11-generic #16-Ubuntu SMP Mon Aug 25 20:02:00 UTC 2014 
ppc64le ppc64le ppc64le GNU/Linux
   
  I've retested gdb from Ubuntu 14.04 (gdb-7.7-0ubuntu3.1) in the Ubuntu 14.10 
VM provided by Pavaman and the number of failures curiously increased to 250 
(in comparison to less than 140 on 14.04), which leads me to believe that there 
is something in the environment of Ubuntu 14.10 compromising gdb functionality 
in several testcases.

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

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

[Touch-packages] [Bug 1326954] Re: ModemManager does not seem to recognize Sierra Wireless EM7305 (Fujitsu Lifebook S904)

[Pier Paolo]

Mobile broadband not working after resume on Toshiba Tecra Z40, too.

$ lsusb
Bus 002 Device 002: ID 1199:9063 Sierra Wireless, Inc. 

How can i help troubleshooting the problem?

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

Title:
  ModemManager does not seem to recognize Sierra Wireless EM7305
  (Fujitsu Lifebook S904)

Status in ModemManager (with NetworkManager support):
  New
Status in “libmbim” package in Ubuntu:
  Confirmed
Status in “modemmanager” package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 14.04, x86_64, ModemManager-1.0.0-2ubuntu1

  Card: Sierra Wireless EM7305 (PCI Express M.2 form factor)

  Expected: Sierra plugin is used
  Happens: Generic plugin is used instead

  After cold start the card seems to work almost fine, but does not come
  back after suspend or hibernate. At least after hibernate MM may go
  into a tight loop consuming 100% CPU.

  MM debug log output (full log attached):

   [1401992536.121631] [mm-plugin-manager.c:576] build_plugins_list(): 
(Plugin Manager) [wwan0] Found '1' plugins to try...
   [1401992536.125236] [mm-plugin-manager.c:580] build_plugins_list(): 
(Plugin Manager) [wwan0]   Will try with plugin 'Generic'
   [1401992536.128923] [mm-plugin.c:700] mm_plugin_supports_port(): 
(Generic) [wwan0] probing deferred until result suggested
   [1401992536.132687] [mm-plugin-manager.c:505] 
plugin_supports_port_ready(): (Plugin Manager) [wwan0] deferring support check 
until result suggested
   [1401992536.142664] [mm-port-probe.c:536] wdm_probe_mbim(): 
(usbmisc/cdc-wdm0) probing MBIM...
   [1401992538.202591] [mm-plugin-manager.c:646] 
min_probing_timeout_cb(): (Plugin Manager) 
[/sys/devices/pci:00/:00:14.0/usb1/1-6] Minimum probing time consumed
  [/dev/cdc-wdm0] Queried max control message size: 4096[/dev/cdc-wdm0] Sent 
message...
  << RAW:
  <<   length = 16
  <<   data   = 01:00:00:00:10:00:00:00:01:00:00:00:00:10:00:00
  [/dev/cdc-wdm0] Sent message (translated)...
  << Header:
  <<   length  = 16
  <<   type= open (0x0001)
  <<   transaction = 1
  << Contents:
  <<   max_control_transfer = 4096
  [/dev/cdc-wdm0] Received message...
  >> RAW:
  >>   length = 16
  >>   data   = 01:00:00:80:10:00:00:00:01:00:00:00:00:00:00:00
   [1401992539.481429] [mm-port-probe.c:300] 
mm_port_probe_set_result_mbim(): (usbmisc/cdc-wdm0) port is MBIM-capable
  [/dev/cdc-wdm0] Sent message...
  << RAW:
  <<   length = 12
  <<   data   = 02:00:00:00:0C:00:00:00:02:00:00:00
  [/dev/cdc-wdm0] Sent message (translated)...
  << Header:
  <<   length  = 12
  <<   type= close (0x0002)
  <<   transaction = 2
  [/dev/cdc-wdm0] Received message...
  >> RAW:
  >>   length = 16
  >>   data   = 02:00:00:80:10:00:00:00:02:00:00:00:00:00:00:00
   [1401992539.545529] [mm-plugin-manager.c:417] 
plugin_supports_port_ready(): (Plugin Manager) (Generic) [cdc-wdm0] found best 
plugin for port
   [1401992539.549361] [mm-plugin-manager.c:334] 
suggest_port_probe_result(): (Plugin Manager) (Generic) [wwan0] deferred task 
completed, got suggested plugin
   [1401992539.553247] [mm-plugin-manager.c:274] 
port_probe_context_finished(): (Plugin Manager) 'cdc-wdm0' port probe finished, 
still 1 running probes in this device (wwan0)
   [1401992539.556995] [mm-plugin.c:700] mm_plugin_supports_port(): 
(Generic) [wwan0] probing deferred until result suggested
   [1401992539.560690] [mm-plugin-manager.c:485] 
plugin_supports_port_ready(): (Plugin Manager) (Generic) [wwan0] task 
completed, got suggested plugin
   [1401992539.564175] [mm-plugin-manager.c:285] 
port_probe_context_finished(): (Plugin Manager) 'wwan0' port probe finished, 
last one in device
   [1401992539.567868] [mm-plugin-manager.c:107] 
find_device_support_context_complete_and_free(): (Plugin Manager) 
[/sys/devices/pci:00/:00:14.0/usb1/1-6] device support check finished 
in '3.677528' seconds
[1401992539.571611] [mm-device.c:486] mm_device_create_modem(): 
Creating modem with plugin 'Generic' and '2' ports
   [1401992539.575477] [generic/mm-plugin-generic.c:73] create_modem(): 
MBIM-powered generic modem found...

  mmcli output:

  /org/freedesktop/ModemManager1/Modem/0 (device id 
'b3a77501ed8da196baa804a4142ff280766f6f98')
-
Hardware |   manufacturer: 'Generic'
 |  model: 'MBIM [1199:9063]'
 |   revision: 'SWI9X15C_01.12'
 |  supported: 'gsm-umts, lte'
 |current: 'gsm-umts, lte'
 |   equipment id: '356906050069168'
-
System   | device: '/sys/devices/pci:00/:00:14.0/usb1/1-6'
 |drivers: 'cdc_mbim'
 | plugin: 'Generic'
 |   primary port: 'cdc-wdm0

[Touch-packages] [Bug 1376324] Re: /usr/sbin/unity-system-compositor:*** Error in `unity-system-compositor': free(): invalid pointer: ADDR ***

[Alan Griffiths]

I've not been able to reproduce yet[1], but looking at the code I can't
see anything that prevents a buffer stream being owned by the compositor
(for composition) after the corresponding Surface and Session have been
closed. If that then attempts to "complete" a buffer swap then we would
see the above result.

If I'm right then adding code to ~BasicSurface() to prevent the
surface_buffer_stream completing pending swaps is all that is needed.

[1] I have to leave myself something to do tomorrow.

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

Title:
  /usr/sbin/unity-system-compositor:*** Error in `unity-system-
  compositor': free(): invalid pointer: ADDR ***

Status in Mir:
  In Progress
Status in Unity System Compositor:
  New
Status in “mir” package in Ubuntu:
  New
Status in “unity-system-compositor” package in Ubuntu:
  New

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

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

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

[Touch-packages] [Bug 1370146] Re: Adjust header behaviour & UI in multi select mode

[Launchpad Bug Tracker]

** Branch linked: lp:~tpeeters/ubuntu-ui-toolkit/20-sm

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

Title:
  Adjust header behaviour & UI in multi select mode

Status in Address Book App:
  Confirmed
Status in Dialer app for Ubuntu Touch:
  Confirmed
Status in Messaging App:
  Confirmed
Status in Clock application for Ubuntu devices:
  Fix Released
Status in Ubuntu UI Toolkit:
  In Progress
Status in Ubuntu UX bugs:
  Fix Released
Status in “address-book-app” package in Ubuntu:
  Confirmed
Status in “dialer-app” package in Ubuntu:
  Confirmed
Status in “messaging-app” package in Ubuntu:
  Confirmed
Status in “ubuntu-ui-toolkit” package in Ubuntu:
  In Progress

Bug description:
  Steps to reproduce:

  1. Open Messaging app (or Address Book app, Phone app), make sure you have a 
list in your messages view
  2. Long press on any of the list items

  Actual Result:
  3. Header is changing and shows an X button on the left hand side and two 
action buttons on the right hand side. Selection checkboxes appear from the 
left hand side.

  Expected result - desired solution:
  - The header should display a BACK button instead of the "X" on the left hand 
side, same as we have in all other headers
  - Remove the change in the background colour when a list item is selected, 
change in the colour of the checkbox is enough
  - Add labels for all visible actions in this mode in the header, except for 
'BACK'
  - Tapping on the BACK in this mode, cancels the multi-select mode and does 
NOT navigate back to the previous view
  - There is no title in this header

  Please see attached wireframe for reference. This change applies
  across all apps which use a multi select in their list views.

To manage notifications about this bug go to:
https://bugs.launchpad.net/address-book-app/+bug/1370146/+subscriptions

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

[Touch-packages] [Bug 1376358] [NEW] lightdm writing the same DEBUG message to /var/log/lightdm/lightdm.log

[Colin Ian King]

Public bug reported:

I was trying to figure out where excessive file system writes were
coming from on the ubuntu phone (to try to reduce flash writes and hence reduce 
power
consumption) and I spotted that /var/log/lightdm/lightdm.log is getting the 
same debug message written to every every 300 seconds:

tail -f /var/log/lightdm/lightdm.log
[+5109.66s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
[+5409.67s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
[+5709.66s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
[+6009.66s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
[+6309.64s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
[+6609.65s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
[+6909.67s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
[+7209.66s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
[+7509.66s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
[+7809.57s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
[+8109.65s] DEBUG: User /org/freedesktop/Accounts/User32011 changed

while this isn't much of a message, it still is causing file system
writes every 5 minutes for the same debug message. Is this necessary?
The fact that it is the same message about the same account and that it
occurs every 300 seconds make me wonder if we can cull this particular
piece of repeated logging.

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

Title:
  lightdm writing the same DEBUG message to /var/log/lightdm/lightdm.log

Status in “lightdm” package in Ubuntu:
  New

Bug description:
  I was trying to figure out where excessive file system writes were
  coming from on the ubuntu phone (to try to reduce flash writes and hence 
reduce power
  consumption) and I spotted that /var/log/lightdm/lightdm.log is getting the 
same debug message written to every every 300 seconds:

  tail -f /var/log/lightdm/lightdm.log
  [+5109.66s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+5409.67s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+5709.66s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+6009.66s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+6309.64s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+6609.65s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+6909.67s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+7209.66s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+7509.66s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+7809.57s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+8109.65s] DEBUG: User /org/freedesktop/Accounts/User32011 changed

  while this isn't much of a message, it still is causing file system
  writes every 5 minutes for the same debug message. Is this necessary?
  The fact that it is the same message about the same account and that
  it occurs every 300 seconds make me wonder if we can cull this
  particular piece of repeated logging.

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

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

[Touch-packages] [Bug 1376357] [NEW] lightdm writing the same DEBUG message to /var/log/lightdm/lightdm.log

[Colin Ian King]

Public bug reported:

I was trying to figure out where excessive file system writes were
coming from on the ubuntu phone (to try to reduce flash writes and hence reduce 
power
consumption) and I spotted that /var/log/lightdm/lightdm.log is getting the 
same debug message written to every every 300 seconds:

tail -f /var/log/lightdm/lightdm.log
[+5109.66s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
[+5409.67s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
[+5709.66s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
[+6009.66s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
[+6309.64s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
[+6609.65s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
[+6909.67s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
[+7209.66s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
[+7509.66s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
[+7809.57s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
[+8109.65s] DEBUG: User /org/freedesktop/Accounts/User32011 changed

while this isn't much of a message, it still is causing file system
writes every 5 minutes for the same debug message. Is this necessary?
The fact that it is the same message about the same account and that it
occurs every 300 seconds make me wonder if we can cull this particular
piece of repeated logging.

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

Title:
  lightdm writing the same DEBUG message to /var/log/lightdm/lightdm.log

Status in “lightdm” package in Ubuntu:
  New

Bug description:
  I was trying to figure out where excessive file system writes were
  coming from on the ubuntu phone (to try to reduce flash writes and hence 
reduce power
  consumption) and I spotted that /var/log/lightdm/lightdm.log is getting the 
same debug message written to every every 300 seconds:

  tail -f /var/log/lightdm/lightdm.log
  [+5109.66s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+5409.67s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+5709.66s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+6009.66s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+6309.64s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+6609.65s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+6909.67s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+7209.66s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+7509.66s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+7809.57s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+8109.65s] DEBUG: User /org/freedesktop/Accounts/User32011 changed

  while this isn't much of a message, it still is causing file system
  writes every 5 minutes for the same debug message. Is this necessary?
  The fact that it is the same message about the same account and that
  it occurs every 300 seconds make me wonder if we can cull this
  particular piece of repeated logging.

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

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

[Touch-packages] [Bug 1371032] Re: Cannot send MMS from "Yoigo"

[Tony Espy]

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

** Changed in: nuntium (Ubuntu)
 Assignee: (unassigned) => Sergio Schvezov (sergiusens)

** Changed in: network-manager (Ubuntu)
   Importance: Critical => High

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

** Changed in: nuntium (Ubuntu)
   Status: New => In Progress

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

** Changed in: ofono (Ubuntu)
   Importance: Critical => High

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

Title:
  Cannot send MMS from "Yoigo"

Status in “messaging-app” package in Ubuntu:
  New
Status in “network-manager” package in Ubuntu:
  Incomplete
Status in “nuntium” package in Ubuntu:
  In Progress
Status in “ofono” package in Ubuntu:
  Invalid

Bug description:
  phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-contexts
  [ /ril_1 ]
  [ /ril_0 ]
  [ /ril_0/context1 ]
  AccessPointName = internet
  Name = Yoigo Internet
  Password = 
  Protocol = ip
  IPv6.Settings = { }
  Type = internet
  Active = 1
  Username = 
  Settings = { DomainNameServers=217.168.13.34,46.6.113.2, 
Address=10.192.132.31 Method=static Netmask=255.255.255.0 Gateway=10.192.132.31 
Interface=ccmni0 }

  [ /ril_0/context2 ]
  AccessPointName = mms
  MessageCenter = http://mmss/
  Name = Yoigo MMS
  Password = 
  Protocol = ip
  MessageProxy = 193.209.134.141:80
  IPv6.Settings = { }
  Type = mms
  Active = 0
  Username = 
  Settings = { }

  phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/activate-context /ril_0 2
  Error activating /ril_0/context2: org.ofono.Error.NotAttached: GPRS is not 
attached

  phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/activate-context
  /ril_0 1

  Additional info:
  - I didn't see any error in the messaging app.
  - Couldn't send nor receive MMS.
  - 3G connection is activated, but usually after a reboot. After a while, it 
looses it.

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

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

[Touch-packages] [Bug 1376361] [NEW] Need to open up path for cached QML bytecode

[Ricardo Mendoza]

Public bug reported:

The upcoming introduction of cacheable QML compilation units require an
application-specific path to store the binaries.

The proposed  and accepted path is

$HOME/.cache/QML/Apps/$APP_ID

where $APP_ID = @{APP_PKGNAME}_@{APP_APPNAME}_@{APP_VERSION} for click apps
and simple desktop file name for legacy apps.

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

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

Title:
  Need to open up path for cached QML bytecode

Status in “apparmor-easyprof-ubuntu” package in Ubuntu:
  New

Bug description:
  The upcoming introduction of cacheable QML compilation units require
  an application-specific path to store the binaries.

  The proposed  and accepted path is

  $HOME/.cache/QML/Apps/$APP_ID

  where $APP_ID = @{APP_PKGNAME}_@{APP_APPNAME}_@{APP_VERSION} for click apps
  and simple desktop file name for legacy apps.

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

-- 
Mailing list: https://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 1371574] Re: After installing clicks to /custom/click, /usr/share/click/preinstalled version are still preferred

[Colin Watson]

OK.  I'm convinced by your arguments about app IDs; I didn't realise
that the profile name needed to be known outside just aa-exec-click
(which does have the application path in hand as well as the app ID).

I like your proposal of putting all the possible database names in
CLICK_DIR.  Would it be reasonable to just add all the valid click
databases there, regardless of whether a given package happens to be
unpacked there at the moment?  In that case, the necessary API for that
already exists, albeit a little obscurely:

  >>> from gi.repository import Click
  >>> db = Click.DB()
  >>> db.read()
  >>> [db.get(i).props.root for i in range(db.props.size)]
  ['/usr/share/click/preinstalled', '/custom/click', '/opt/click.ubuntu.com']

It might then be unnecessary to change click at all, which is obviously
fantastic from my point of view. ;-)  But this does genuinely seem like
a better technical solution, and would let us stop playing whack-a-mole
with the precise ordering of various database operations.  Given that
click-apparmor is the only system-level hook in the phone stack right
now, we could mandate this kind of thing as required behaviour for
future system-level hooks.

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

Title:
  After installing clicks to /custom/click,
  /usr/share/click/preinstalled version are still preferred

Status in “click” package in Ubuntu:
  In Progress

Bug description:
  This occurs while moving click apps from the rootfs into the custom
  tarball.  Because of this some apps fail to launch.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: click 0.4.32.1
  ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1
  Uname: Linux 3.16.0-10-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Sep 19 07:53:58 2014
  InstallationDate: Installed on 2013-04-26 (510 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: click
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1376361] Re: Need to open up path for cached QML bytecode

[Jamie Strandboge]

** Also affects: apparmor-easyprof-ubuntu (Ubuntu RTM)
   Importance: Undecided
   Status: New

** Changed in: apparmor-easyprof-ubuntu (Ubuntu)
   Importance: Undecided => Critical

** Changed in: apparmor-easyprof-ubuntu (Ubuntu RTM)
   Importance: Undecided => Critical

** Changed in: apparmor-easyprof-ubuntu (Ubuntu)
   Status: New => In Progress

** Changed in: apparmor-easyprof-ubuntu (Ubuntu RTM)
   Status: New => In Progress

** Changed in: apparmor-easyprof-ubuntu (Ubuntu)
 Assignee: (unassigned) => Jamie Strandboge (jdstrand)

** Changed in: apparmor-easyprof-ubuntu (Ubuntu RTM)
 Assignee: (unassigned) => Jamie Strandboge (jdstrand)

** Tags added: application-confinement rtm14 touch-2014-10-09

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

Title:
  Need to open up path for cached QML bytecode

Status in “apparmor-easyprof-ubuntu” package in Ubuntu:
  In Progress
Status in “apparmor-easyprof-ubuntu” package in Ubuntu RTM:
  In Progress

Bug description:
  The upcoming introduction of cacheable QML compilation units require
  an application-specific path to store the binaries.

  The proposed  and accepted path is

  $HOME/.cache/QML/Apps/$APP_ID

  where $APP_ID = @{APP_PKGNAME}_@{APP_APPNAME}_@{APP_VERSION} for click apps
  and simple desktop file name for legacy apps.

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

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

[Touch-packages] [Bug 1371032] Re: Cannot send MMS from "Yoigo"

[Tony Espy]

Somehow my last comment explaining my updates to the bug went missing,
so I'll try again...

Based on the network logs we reviewed, the phone is bouncing back and
forth between Yoigo's network ( MCC=214 MNC=04 ) and the movistar (
MCC=214 MNC=07 ) network.   This explains the occasional loss of mobile
data, as unless "Data Roaming" is enabled, you will lose mobile data
every time the phone roams to the movistar network.   Further log
analysis reveals that nuntium tries to send the MMS while roaming, which
fails.

It turns out that Yoigo's network doesn't fully support UMTS and as such
they have a roaming agreement with movistar to provide UMTS coverage.
As we have no way to detect this, nor do we support a "national roaming"
capability ( ie. allow data roaming only within the same country ),
there's not much you can do other than enable "Data roaming", and be
careful to disable if you leave the country.   It also should be noted
that if/when phones are sold in conjunction with Yoigo, that the phones
are probably customized to be aware of this roaming arrangement.   I
will enter ofono wishlist bugs for both of these and will link to this
bug.

I've assigned a nuntium task to Sergio as he's working on adding retry
logic to nuntium, and also a messaging-app task to Tiago, as the
messaging-app should have reported an error when the send failed.

@Victor - when you lose mobile data connectivity, does it ever come
back, or do you need to reboot?  If the latter, then could you open a
new network-manager bug for that specific problem?

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

Title:
  Cannot send MMS from "Yoigo"

Status in “messaging-app” package in Ubuntu:
  New
Status in “network-manager” package in Ubuntu:
  Incomplete
Status in “nuntium” package in Ubuntu:
  In Progress
Status in “ofono” package in Ubuntu:
  Invalid

Bug description:
  phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-contexts
  [ /ril_1 ]
  [ /ril_0 ]
  [ /ril_0/context1 ]
  AccessPointName = internet
  Name = Yoigo Internet
  Password = 
  Protocol = ip
  IPv6.Settings = { }
  Type = internet
  Active = 1
  Username = 
  Settings = { DomainNameServers=217.168.13.34,46.6.113.2, 
Address=10.192.132.31 Method=static Netmask=255.255.255.0 Gateway=10.192.132.31 
Interface=ccmni0 }

  [ /ril_0/context2 ]
  AccessPointName = mms
  MessageCenter = http://mmss/
  Name = Yoigo MMS
  Password = 
  Protocol = ip
  MessageProxy = 193.209.134.141:80
  IPv6.Settings = { }
  Type = mms
  Active = 0
  Username = 
  Settings = { }

  phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/activate-context /ril_0 2
  Error activating /ril_0/context2: org.ofono.Error.NotAttached: GPRS is not 
attached

  phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/activate-context
  /ril_0 1

  Additional info:
  - I didn't see any error in the messaging app.
  - Couldn't send nor receive MMS.
  - 3G connection is activated, but usually after a reboot. After a while, it 
looses it.

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

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

[Touch-packages] [Bug 1354318] Re: whoopsie-upload-all has a wrong check for whether the upload is done

[Launchpad Bug Tracker]

** Branch linked: lp:~brian-murray/ubuntu/utopic/apport/bug-1354318

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

Title:
  whoopsie-upload-all has a wrong check for whether the upload is done

Status in “apport” package in Ubuntu:
  New

Bug description:
  Currently, the way whoopsie-upload-all works is that, whenever a new
  .crash file is seen, /etc/init/apport-noui.conf triggers to run
  whoopsie-upload-all from a single-threaded job that iterates through
  all as-yet-unprocessed .crash files, process them via apport, marks
  them for upload, and then waits for apport to upload them.

  There are several problems with this:

   - The "wait for apport to upload them" is racy.  Once a report is submitted, 
it is legitimate for something to remove all of the related files (.crash, 
.upload, .uploaded).  On our test infrastructure, that has resulted in buggy 
behavior because the test harness is removing these files /while 
whoopsie-upload-all is polling/, causing it to poll for a very long time 
waiting for a file that will never be found and then time out.
   - waiting for apport to upload is pointless anyway for its designed use, 
since whoopsie-upload-all is called from an upstart job that's 
inotify-triggered so nothing waits for the return from this command anyway.  
The utah scripts appear to currently be waiting for it; however this should be 
non-default, exceptional behavior, because...
   - since apport-noui is not an 'instance' job, as long as the job is running 
(presumably blocking on files that are never going to show up), *newly* created 
.crash files will not be processed.
   - the job furthermore is written to assume that it will be called separately 
for crashes done as different users.  However, since whoopsie-upload-all will 
process all the crashes that it can each time that it runs, there is a race 
condition whereby a crash written as non-root will be processed by 
whoopsie-upload-all running as root, resulting in wrong permissions on the 
related files anyway.

  Proposed solution to this:

   - Change apport-noui to be 'instance $MATCH'.  This will result in a 
separate whoopsie-upload-all process spawned each time a new .crash is created.
   - Keep the current semantics of whoopsie-upload-all iterating over *all* 
.crash files that it finds and submitting them.  This ensures that if a 
previous crash is missed out for any reason, we manage to catch it later.
   - Ensure that process_report() can be safely called from multiple processes 
at the same time on the same .crash file (by locking with correct semantics and 
having subsequent calls skip)
   - Handle any necessary file uid changes /within/ whoopsie-upload-all, 
instead of relying on a racy sudo invocation from the upstart job.
   - Disable the current wait_uploaded() behavior unless a timeout argument is 
given explicitly; and also fix the behavior to detect when the .upload file has 
been removed after we started watching.

  I believe with those changes, whoopsie-upload-all should give us
  reliable report processing in all cases.

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

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

[Touch-packages] [Bug 1270200] Re: autopilot list view emulator will fail selecting an item not yet created

[Leo Arias]

** Changed in: ubuntu-ui-toolkit
   Status: In Progress => Fix Released

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

Title:
  autopilot list view emulator will fail selecting an item not yet
  created

Status in Ubuntu UI Toolkit:
  Fix Released
Status in “ubuntu-ui-toolkit” package in Ubuntu:
  Fix Released

Bug description:
  When a list is big, not all the items are created at once. So we need
  to scroll to the bottom before selection the last items of big lists.

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

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

[Touch-packages] [Bug 1324556] Re: The header autopilot helper will fail if the parent is not called MainView

[Leo Arias]

** Changed in: ubuntu-ui-toolkit
   Status: In Progress => Fix Released

** Changed in: gallery-app
   Status: In Progress => Invalid

** Changed in: gallery-app (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  The header autopilot helper will fail if the parent is not called
  MainView

Status in Gallery App:
  Invalid
Status in Ubuntu UI Toolkit:
  Fix Released
Status in “gallery-app” package in Ubuntu:
  Invalid

Bug description:
  On the header autopilot helper we are assuming that the container is
  called MainView. There are many applications that extend the MainView
  component and it gets a new name. We should use a different way to get
  the parent without knowing the name.

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

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

[Touch-packages] [Bug 1371310] Re: docker.io doesn't work with apparmor 3.0 RC1 kernel

[Jamie Strandboge]

I can confirm that reverting the patch John Johansen mentioned makes
docker.io work as well as in previous releases. We will have this fixed
before 14.10 release.

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

Title:
  docker.io doesn't work with apparmor 3.0 RC1 kernel

Status in “apparmor” package in Ubuntu:
  Invalid
Status in “docker.io” package in Ubuntu:
  Invalid
Status in “linux” package in Ubuntu:
  In Progress

Bug description:
  Steps to reproduce (from
  https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor):

  1. sudo apt-get install docker.io # 1.2.0~dfsg1-1

  2. sudo docker pull ubuntu:trusty

  3. sudo docker run ubuntu:trusty uptime
  2014/09/18 15:48:48 Error response from daemon: Cannot start container 
fcdfaaf7945bcd9455fb5e0bde9950451152af14556880033818df7b50ddb1f4: set apparmor 
profile docker-default: permission denied

  What is expected? uptime to return something like:
  $ sudo docker run ubuntu:trusty uptime
   20:31:21 up 1 min,  0 users,  load average: 0.09, 0.06, 0.03

  I set 'sudo sysctl -w kernel.printk_ratelimit=0' but there is nothing
  apparmor related in the logs. If I boot an earlier kernel without the
  3.0 RC1 patches, it works.

  FYI, 3.16.0-17.23 is in utopic-proposed now and on its way to utopic,
  which will affect docker.io in Ubuntu. Workaround until this bug is
  fixed is to boot into 3.16.0-16.22 or earlier.

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

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

[Touch-packages] [Bug 1376371] [NEW] nvidia driver problem

[gerry]

Public bug reported:

when i try to run optirun  command i take this 
gerry@Deep-blue:~$ optirun firefox
[   74.002117] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) 
NVIDIA(0): Failed to initialize the NVIDIA GPU at PCI:1:0:0.  Please

[   74.002158] [ERROR]Aborting because fallback start is disabled

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
Uname: Linux 3.13.0-36-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.117  Tue Nov 26 21:25:36 
PST 2013
 GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.4
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Wed Oct  1 20:44:00 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 3.13.0-36-generic, x86_64: installed
 nvidia-304, 304.117, 3.13.0-36-generic, x86_64: installed
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Fujitsu Limited. Device [10cf:16c2]
 NVIDIA Corporation GF108M [GeForce GT 620M] [10de:0de8] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Fujitsu Limited. Device [10cf:1767]
InstallationDate: Installed on 2014-09-29 (2 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: FUJITSU LIFEBOOK AH532/G21
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic 
root=UUID=5979bda2-aa14-4d9b-8314-194a1a18db67 ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/20/2013
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 2.09
dmi.board.name: FJNBB2B
dmi.board.vendor: FUJITSU
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU
dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion2.09:bd02/20/2013:svnFUJITSU:pnLIFEBOOKAH532/G21:pvr:rvnFUJITSU:rnFJNBB2B:rvr:cvnFUJITSU:ct10:cvr:
dmi.product.name: LIFEBOOK AH532/G21
dmi.sys.vendor: FUJITSU
version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
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.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Wed Oct  1 20:35:49 2014
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   13378 
 vendor SEC
xserver.version: 2:1.15.1-0ubuntu2.1

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


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

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

Title:
  nvidia driver problem

Status in “xorg” package in Ubuntu:
  New

Bug description:
  when i try to run optirun  command i take this 
  gerry@Deep-blue:~$ optirun firefox
  [   74.002117] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) 
NVIDIA(0): Failed to initialize the NVIDIA GPU at PCI:1:0:0.  Please

  [   74.002158] [ERROR]Aborting because fallback start is disabled

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-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.117  Tue Nov 26 21:25:36 
PST 2013
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRun

[Touch-packages] [Bug 1376374] [NEW] whoopsie-upload-all will run hooks on a corrupt crash file multiple times

[Brian Murray]

Public bug reported:

whoopsie-upload-all in it's process_report() function will try to
collect information for a crash with a truncated core dump every time it
is called thereby wasting resources on a device.

I'm looking at the following code:

if 'Dependencies' in r:
print('%s already has info collected' % report)
else:
print('Collecting info for %s...' % report)
r.add_os_info()
# add minimal hook information here; whoopsie only considers
# ApportVersion, NonfreeKernelModules, SystemImageInfo
try:
r.add_hooks_info(None)
except Exception as e:
sys.stderr.write('WARNING: hook failed for processing %s: %s\n' % 
(report, str(e)))

try:
r.add_gdb_info()
except (IOError, EOFError) as e:
sys.stderr.write('ERROR: processing %s: %s\n' % (report, str(e)))
return None

Because the report is never written Dependencies is never added to the
report, so every time whoopsie-upload-all is called it will run
add_hooks_info() and add_gdb_info() for the same report.

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


** Tags: utopic

** Tags added: utopic

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

Title:
  whoopsie-upload-all will run hooks on a corrupt crash file multiple
  times

Status in “apport” package in Ubuntu:
  New

Bug description:
  whoopsie-upload-all in it's process_report() function will try to
  collect information for a crash with a truncated core dump every time
  it is called thereby wasting resources on a device.

  I'm looking at the following code:

  if 'Dependencies' in r:
  print('%s already has info collected' % report)
  else:
  print('Collecting info for %s...' % report)
  r.add_os_info()
  # add minimal hook information here; whoopsie only considers
  # ApportVersion, NonfreeKernelModules, SystemImageInfo
  try:
  r.add_hooks_info(None)
  except Exception as e:
  sys.stderr.write('WARNING: hook failed for processing %s: %s\n' % 
(report, str(e)))

  try:
  r.add_gdb_info()
  except (IOError, EOFError) as e:
  sys.stderr.write('ERROR: processing %s: %s\n' % (report, str(e)))
  return None

  Because the report is never written Dependencies is never added to the
  report, so every time whoopsie-upload-all is called it will run
  add_hooks_info() and add_gdb_info() for the same report.

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

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

[Touch-packages] [Bug 1320020] Re: [Inspiron 1470, Realtek ALC272, Speaker, Internal] No sound at all

[Isiah Meadows]

That was my hypothesis. I know little about the internals of ALSA.]

It has lately started happening less often for me, but I haven't made a
concerted attempt recently to see if it still repros on my machine.

I apparently haven't posted repro instructions yet, so here they are
(only works on laptops)

1. Boot and log in.
2. Put machine into sleep mode.
3. Wake the machine.
4. As it's waking (and the screen comes on), put it to sleep while it is 
loading. This means closing the lid in the case for laptops.
5. Wake the machine again. 
6. Sound now stops working through speakers.
7. Put the machine to sleep.
8. Wake it again, and unlock it if necessary.
9. Sound now works through speakers.

Note: this works about 30-50% of the time, but it is rare for it to take
more than 3-5 tries to trigger it. The typical case I've found is 2.

I also have libtiff4 installed,  but I don't have the easiest access to
a clean install.

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

Title:
  [Inspiron 1470, Realtek ALC272, Speaker, Internal] No sound at all

Status in “alsa-driver” package in Ubuntu:
  Confirmed

Bug description:
  I can get perfect sound through headphones, and the kernel recognizes
  the internal speaker, but nothing is ever played through it. I have
  personally tested a pair of earbuds to make sure that sound could play
  through the headphone port, and that isn't a problem. The sound driver
  just refuses to recognize the existence of the speaker, even though
  the kernel does.

  I wouldn't be surprised if the last upstream update had something to
  do with it.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  isiah  7361 F pulseaudio
  CurrentDesktop: GNOME
  Date: Thu May 15 18:07:52 2014
  InstallationDate: Installed on 2014-01-29 (106 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 
(20131017)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  isiah  7361 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Inspiron 1470, Realtek ALC272, Speaker, Internal] No sound at all
  UpgradeStatus: Upgraded to trusty on 2014-05-04 (11 days ago)
  dmi.bios.date: 03/23/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0M7CYJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A05
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd03/23/2011:svnDellInc.:pnInspiron1470:pvrA05123:rvnDellInc.:rn0M7CYJ:rvrA05:cvnDellInc.:ct8:cvrA05:
  dmi.product.name: Inspiron 1470
  dmi.product.version: A05123
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1371032] Re: Cannot send MMS from "Yoigo"

[Tony Espy]

I created bug #1376375 to track the lack of a roaming agreement
customization feature in ofono.

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

Title:
  Cannot send MMS from "Yoigo"

Status in “messaging-app” package in Ubuntu:
  New
Status in “network-manager” package in Ubuntu:
  Incomplete
Status in “nuntium” package in Ubuntu:
  In Progress
Status in “ofono” package in Ubuntu:
  Invalid

Bug description:
  phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-contexts
  [ /ril_1 ]
  [ /ril_0 ]
  [ /ril_0/context1 ]
  AccessPointName = internet
  Name = Yoigo Internet
  Password = 
  Protocol = ip
  IPv6.Settings = { }
  Type = internet
  Active = 1
  Username = 
  Settings = { DomainNameServers=217.168.13.34,46.6.113.2, 
Address=10.192.132.31 Method=static Netmask=255.255.255.0 Gateway=10.192.132.31 
Interface=ccmni0 }

  [ /ril_0/context2 ]
  AccessPointName = mms
  MessageCenter = http://mmss/
  Name = Yoigo MMS
  Password = 
  Protocol = ip
  MessageProxy = 193.209.134.141:80
  IPv6.Settings = { }
  Type = mms
  Active = 0
  Username = 
  Settings = { }

  phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/activate-context /ril_0 2
  Error activating /ril_0/context2: org.ofono.Error.NotAttached: GPRS is not 
attached

  phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/activate-context
  /ril_0 1

  Additional info:
  - I didn't see any error in the messaging app.
  - Couldn't send nor receive MMS.
  - 3G connection is activated, but usually after a reboot. After a while, it 
looses it.

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

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

[Touch-packages] [Bug 1354571] Re: apport-retrace ignores warnings from gdb

[Brian Murray]

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

** Changed in: apport (Ubuntu Trusty)
   Status: New => In Progress

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

** Changed in: apport (Ubuntu Trusty)
 Assignee: (unassigned) => Brian Murray (brian-murray)

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

Title:
  apport-retrace ignores warnings from gdb

Status in “apport” package in Ubuntu:
  Fix Released
Status in “apport” source package in Trusty:
  In Progress

Bug description:
  I was trying to investigate a failed retrace on armhf and received the
  following when running apport-retrace with -g.

  Calling gdb command: gdb-multiarch --ex 'set architecture arm' --ex 'set 
gnutarget elf32-littlearm' --ex 'set debug-file-directory /tmp/apport
  -utopic/usr/lib/debug' --ex 'set solib-absolute-prefix /tmp/apport-utopic' 
--ex 'file "/tmp/apport-utopic//usr/lib/ubuntu-push-client/signing-
  helper"' --ex 'core-file /tmp/apport_core_36z3Va'
  GNU gdb (Ubuntu 7.7-0ubuntu3.2) 7.7
  Copyright (C) 2014 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .
  For help, type "help".
  Type "apropos word" to search for commands related to "word".
  The target architecture is assumed to be arm
  Reading symbols from 
/tmp/apport-utopic//usr/lib/ubuntu-push-client/signing-helper...Reading symbols 
from /tmp/apport-utopic/usr/lib/debug/.bu
  ild-id/0d/28e75c6b9149132f8940077618a904989a75ed.debug...done.
  done.
  BFD: Warning: /tmp/apport_core_36z3Va is truncated: expected core file size 
>= 19316736, found: 9502720.
  [New LWP 15327]
  [New LWP 15530]
  [New LWP 15321]
  Cannot access memory at address 0xb6fa7948
  Cannot access memory at address 0xb6fa7944

  When running apport-retrace with -o, a new crash file is created with
  a broken Stacktrace.  This makes sense given that the core file is
  corrupt.

  However, I think apport-retrace should do something different here, as
  you have no idea why the retraced report is bad. Maybe it should write
  a RetraceFailure key to the report, not write the report at all, or
  just exit with an error regarding the core file size difference.

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

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

[Touch-packages] [Bug 1376342] Re: [HP Compaq dc7900 Ultra-Slim Desktop, Analog Devices AD1884A, Black Headphone Out, Front] No sound at all

[Seth Arnold]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  [HP Compaq dc7900 Ultra-Slim Desktop, Analog Devices AD1884A, Black
  Headphone Out, Front] No sound at all

Status in “alsa-driver” package in Ubuntu:
  New

Bug description:
  The sound to play in Rythmbox don't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic i686
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fernapro   2145 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Oct  1 18:26:40 2014
  InstallationDate: Installed on 2013-08-15 (412 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful
  Symptom_Card: Audio Interno - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fernapro   2145 F pulseaudio
  Symptom_Jack: Black Headphone Out, Front
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [HP Compaq dc7900 Ultra-Slim Desktop, Analog Devices AD1884A, Black 
Headphone Out, Front] No sound at all
  UpgradeStatus: Upgraded to trusty on 2014-04-21 (162 days ago)
  dmi.bios.date: 03/05/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786G1 v01.16
  dmi.board.asset.tag: CZC944BY74
  dmi.board.name: 3033h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC944BY74
  dmi.chassis.type: 15
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786G1v01.16:bd03/05/2009:svnHewlett-Packard:pnHPCompaqdc7900Ultra-SlimDesktop:pvr:rvnHewlett-Packard:rn3033h:rvr:cvnHewlett-Packard:ct15:cvr:
  dmi.product.name: HP Compaq dc7900 Ultra-Slim Desktop
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1371032] Re: Cannot send MMS from "Yoigo"

[Sergio Schvezov]

The nuntium task will only alleviate activating the context if it is at
all possible; but given the network stability, it can still fail.

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

Title:
  Cannot send MMS from "Yoigo"

Status in “messaging-app” package in Ubuntu:
  New
Status in “network-manager” package in Ubuntu:
  Incomplete
Status in “nuntium” package in Ubuntu:
  In Progress
Status in “ofono” package in Ubuntu:
  Invalid

Bug description:
  phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-contexts
  [ /ril_1 ]
  [ /ril_0 ]
  [ /ril_0/context1 ]
  AccessPointName = internet
  Name = Yoigo Internet
  Password = 
  Protocol = ip
  IPv6.Settings = { }
  Type = internet
  Active = 1
  Username = 
  Settings = { DomainNameServers=217.168.13.34,46.6.113.2, 
Address=10.192.132.31 Method=static Netmask=255.255.255.0 Gateway=10.192.132.31 
Interface=ccmni0 }

  [ /ril_0/context2 ]
  AccessPointName = mms
  MessageCenter = http://mmss/
  Name = Yoigo MMS
  Password = 
  Protocol = ip
  MessageProxy = 193.209.134.141:80
  IPv6.Settings = { }
  Type = mms
  Active = 0
  Username = 
  Settings = { }

  phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/activate-context /ril_0 2
  Error activating /ril_0/context2: org.ofono.Error.NotAttached: GPRS is not 
attached

  phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/activate-context
  /ril_0 1

  Additional info:
  - I didn't see any error in the messaging app.
  - Couldn't send nor receive MMS.
  - 3G connection is activated, but usually after a reboot. After a while, it 
looses it.

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

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

[Touch-packages] [Bug 1371032] Re: Cannot send MMS from "Yoigo"

[Launchpad Bug Tracker]

** Branch linked: lp:~sergiusens/nuntium/not_attached

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

Title:
  Cannot send MMS from "Yoigo"

Status in “messaging-app” package in Ubuntu:
  New
Status in “network-manager” package in Ubuntu:
  Incomplete
Status in “nuntium” package in Ubuntu:
  In Progress
Status in “ofono” package in Ubuntu:
  Invalid

Bug description:
  phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-contexts
  [ /ril_1 ]
  [ /ril_0 ]
  [ /ril_0/context1 ]
  AccessPointName = internet
  Name = Yoigo Internet
  Password = 
  Protocol = ip
  IPv6.Settings = { }
  Type = internet
  Active = 1
  Username = 
  Settings = { DomainNameServers=217.168.13.34,46.6.113.2, 
Address=10.192.132.31 Method=static Netmask=255.255.255.0 Gateway=10.192.132.31 
Interface=ccmni0 }

  [ /ril_0/context2 ]
  AccessPointName = mms
  MessageCenter = http://mmss/
  Name = Yoigo MMS
  Password = 
  Protocol = ip
  MessageProxy = 193.209.134.141:80
  IPv6.Settings = { }
  Type = mms
  Active = 0
  Username = 
  Settings = { }

  phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/activate-context /ril_0 2
  Error activating /ril_0/context2: org.ofono.Error.NotAttached: GPRS is not 
attached

  phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/activate-context
  /ril_0 1

  Additional info:
  - I didn't see any error in the messaging app.
  - Couldn't send nor receive MMS.
  - 3G connection is activated, but usually after a reboot. After a while, it 
looses it.

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

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

[Touch-packages] [Bug 1376283] Re: Process of "init --user" gradually eats all RAM then the system starts using swap and hangs.

[Seth Arnold]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  Process of "init --user" gradually eats all RAM then the system starts
  using swap and hangs.

Status in “upstart” package in Ubuntu:
  New

Bug description:
  Process of "init --user" gradually eats all RAM then the system starts
  using swap and hangs.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: upstart 1.12.1-0ubuntu4.2
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: i386
  Date: Wed Oct  1 18:06:48 2014
  InstallationDate: Installed on 2013-11-09 (325 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release i386 (20131016)
  SourcePackage: upstart
  UpgradeStatus: Upgraded to trusty on 2014-07-20 (72 days ago)
  UpstartBugCategory: Session
  UpstartRunningSessionCount: 2
  UpstartRunningSystemVersion: init (upstart 1.12.1)

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

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

[Touch-packages] [Bug 1314095] Re: Unity Lockscreen in 14.04 can't unlock when using LDAP account

[Stefan Michalowski]

I have the same problem, though I don't have any unix_chkpwd errors as
it's not installed on my systems.

I  was able to solve it by replacing:
1) libpam-ldap by libpam-ldapd
2) libnss-ldap by libnss-ldapd
3) nscd by nslcd

I think it is related to my use of self signed certificates that libpam-
ldap has trouble handling.

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

Title:
  Unity Lockscreen in 14.04 can't unlock when using LDAP account

Status in Unity:
  Incomplete
Status in “unity” package in Ubuntu:
  Incomplete

Bug description:
  My setup is:

  Ubuntu 14.04 LTS,
  ldap accounts,
  krb5 authentication,
  Lightdm,
  Unity session

  ldap+krb5 is configured using nss-ldapd and nslcd. It works fine. getent 
passwd and getent shadow works fine.
  I am able to login in console without any problems.
  I was able to login in lightdm.
  Then I used the lock screen.
  I could not disable the lock screen using my password.
  I rebooted my computer.

  Now:
  After logging in through lightdm, the unity lockscreen locks the screen 
immediately and I can not disable it using my password.

  From my short inspection of auth.log and unix_chkpwd sources it seems,
  that unix_chkpwd works fine when called from lightdm and fails to get
  user info when called from unity lockscreen.


  lsb_release -rd
  Description:  Ubuntu 14.04 LTS
  Release:  14.04

  apt-cache policy unity lightdm libpam-modules
  unity:
Installed: 7.2.0+14.04.20140416-0ubuntu1
Candidate: 7.2.0+14.04.20140416-0ubuntu1
Version table:
   *** 7.2.0+14.04.20140416-0ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status
  lightdm:
Installed: 1.10.0-0ubuntu3
Candidate: 1.10.0-0ubuntu3
Version table:
   *** 1.10.0-0ubuntu3 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status
  libpam-modules:
Installed: 1.1.8-1ubuntu2
Candidate: 1.1.8-1ubuntu2
Version table:
   *** 1.1.8-1ubuntu2 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  Contents of /var/log/auth.log:

  Apr 29 06:49:27 localhost lightdm: pam_succeed_if(lightdm:auth): requirement 
"user ingroup nopasswdlogin" not met by user "user"
  Apr 29 06:49:31 localhost lightdm: pam_unix(lightdm:auth): authentication 
failure; logname= uid=0 euid=0 tty=:2 ruser= rhost=  user=user
  Apr 29 06:49:31 localhost lightdm: pam_krb5(lightdm:auth): user user 
authenticated as user@NETWORK
  Apr 29 06:49:32 localhost lightdm[15604]: pam_unix(lightdm-greeter:session): 
session closed for user lightdm
  Apr 29 06:49:37 localhost unix_chkpwd[15825]: check pass; user unknown
  Apr 29 06:49:37 localhost unix_chkpwd[15825]: password check failed for user 
(user)
  Apr 29 06:49:37 localhost compiz: pam_unix(lightdm:auth): authentication 
failure; logname= uid=1001 euid=1001 tty= ruser= rhost=  user=user
  Apr 29 06:49:37 localhost compiz: pam_krb5(lightdm:auth): user user 
authenticated as user@NETWORK
  Apr 29 06:49:37 localhost unix_chkpwd[15826]: could not obtain user info 
(user)
  Apr 29 06:49:37 localhost unix_chkpwd[15827]: could not obtain user info 
(user)
  Apr 29 06:49:37 localhost compiz: pam_succeed_if(lightdm:auth): requirement 
"user ingroup nopasswdlogin" not met by user "user"

  cat /etc/pam.d/common-auth 
  account requiredpam_unix.so
  authrequiredpam_group.so
  auth [success=2 default=ignore] pam_unix.so try_first_pass nullok_secure
  auth [success=1 default=ignore] pam_krb5.so try_first_pass minimum_uid=200
  authrequisite   pam_deny.so
  authrequiredpam_permit.so

  authoptionalpam_afs_session.so minimum_uid=200
  authoptionalpam_ecryptfs.so unwrap
  authoptionalpam_cap.so

  cat /etc/pam.d/common-account 
  account requiredpam_unix.so

  cat /etc/pam.d/lightdm
  authrequisite   pam_nologin.so
  authsufficient  pam_succeed_if.so user ingroup nopasswdlogin
  @include common-auth
  authoptionalpam_gnome_keyring.so
  @include common-account
  session [success=ok ignore=ignore module_unknown=ignore default=bad] 
pam_selinux.so close
  authoptionalpam_group.so
  session requiredpam_limits.so
  @include common-session
  session [success=ok ignore=ignore module_unknown=ignore default=bad] 
pam_selinux.so open
  session optionalpam_gnome_keyring.so auto_start
  session requiredpam_env.so readenv=1
  session requiredpam_env.so readenv=1 user_readenv=1 
envfile=/etc/default/locale
  @include common-password

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

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

[Touch-packages] [Bug 1376411] [NEW] Firefox profile resulting in ptrace read denials

[John Johansen]

Public bug reported:

The firefox profile on utopic is resulting in denials like

[  351.414861] audit: type=1400 audit(1412190024.478:83):
apparmor="DENIED" operation="ptrace" profile="firefox" pid=4505
comm="firefox" requested_mask="read" denied_mask="read" peer="/usr/bin
/mediascanner-service-2.0"

[  351.414875] audit: type=1400 audit(1412190024.478:86):
apparmor="DENIED" operation="ptrace" profile="firefox" pid=4505
comm="firefox" requested_mask="read" denied_mask="read"
peer="unconfined"


This is most likely due to firefox scanning for information via /proc//

which will result in a ptrace read permission request in the kernel

atm I have locally added the rule*
deny ptrace read peer=[^f][^i][^r][^e][^f][^o][^x],

*my local firefox profile is patched to be named
profile firefox /usr/lib/firefox/firefox{,*[^s][^h]} {

instead of the default of using the attachment path as a name

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

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

Title:
  Firefox profile resulting in ptrace read denials

Status in “apparmor” package in Ubuntu:
  New

Bug description:
  The firefox profile on utopic is resulting in denials like

  [  351.414861] audit: type=1400 audit(1412190024.478:83):
  apparmor="DENIED" operation="ptrace" profile="firefox" pid=4505
  comm="firefox" requested_mask="read" denied_mask="read" peer="/usr/bin
  /mediascanner-service-2.0"

  [  351.414875] audit: type=1400 audit(1412190024.478:86):
  apparmor="DENIED" operation="ptrace" profile="firefox" pid=4505
  comm="firefox" requested_mask="read" denied_mask="read"
  peer="unconfined"

  
  This is most likely due to firefox scanning for information via /proc//

  which will result in a ptrace read permission request in the kernel

  atm I have locally added the rule*
  deny ptrace read peer=[^f][^i][^r][^e][^f][^o][^x],

  *my local firefox profile is patched to be named
  profile firefox /usr/lib/firefox/firefox{,*[^s][^h]} {

  instead of the default of using the attachment path as a name

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

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

[Touch-packages] [Bug 1376411] Re: Firefox profile resulting in ptrace read denials

[Jamie Strandboge]

** Tags added: apparmor

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

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

Title:
  Firefox profile resulting in ptrace read denials

Status in “firefox” package in Ubuntu:
  New

Bug description:
  The firefox profile on utopic is resulting in denials like

  [  351.414861] audit: type=1400 audit(1412190024.478:83):
  apparmor="DENIED" operation="ptrace" profile="firefox" pid=4505
  comm="firefox" requested_mask="read" denied_mask="read" peer="/usr/bin
  /mediascanner-service-2.0"

  [  351.414875] audit: type=1400 audit(1412190024.478:86):
  apparmor="DENIED" operation="ptrace" profile="firefox" pid=4505
  comm="firefox" requested_mask="read" denied_mask="read"
  peer="unconfined"

  
  This is most likely due to firefox scanning for information via /proc//

  which will result in a ptrace read permission request in the kernel

  atm I have locally added the rule*
  deny ptrace read peer=[^f][^i][^r][^e][^f][^o][^x],

  *my local firefox profile is patched to be named
  profile firefox /usr/lib/firefox/firefox{,*[^s][^h]} {

  instead of the default of using the attachment path as a name

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

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

[Touch-packages] [Bug 1376416] [NEW] apparmor denial for yelp

[Jamie Strandboge]

Public bug reported:

In a recent test run, the following denial was observed:
Oct  1 18:13:05 ubuntu-phablet kernel: [  130.968843] 
(3)[6618:com.ubuntu.yelp]type=1400 audit(1412187185.260:127): apparmor="DENIED" 
operation="mkdir" profile="com.ubuntu.yelp_yelp_1.0.26" 
name="/home/phablet/.local/share/unity-scopes/com.ubuntu.yelp_yelp/" pid=6618 
comm="com.ubuntu.yelp" requested_mask="c" denied_mask="c" fsuid=32011 ouid=32011

Yelp is using the wrong directory. It is using:
@{HOME}/.local/share/unity-scopes/@{APP_PKGNAME}_@{APP_APPNAME}

but apparmor policy says to use:
@{HOME}/.local/share/unity-scopes/leaf-net/@{APP_PKGNAME}

Note: this is a different bug than the one dealing with XDG_RUNTIME_DIR
paths, where we do use @{APP_APPNAME}.

Adding rtm14 tag with High priority since this seems to affect scopes in
the store. Please readjust as necessary.

** Affects: unity-scopes-api (Ubuntu)
 Importance: High
 Status: New


** Tags: application-confinement rtm14

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

Title:
  apparmor denial for yelp

Status in “unity-scopes-api” package in Ubuntu:
  New

Bug description:
  In a recent test run, the following denial was observed:
  Oct  1 18:13:05 ubuntu-phablet kernel: [  130.968843] 
(3)[6618:com.ubuntu.yelp]type=1400 audit(1412187185.260:127): apparmor="DENIED" 
operation="mkdir" profile="com.ubuntu.yelp_yelp_1.0.26" 
name="/home/phablet/.local/share/unity-scopes/com.ubuntu.yelp_yelp/" pid=6618 
comm="com.ubuntu.yelp" requested_mask="c" denied_mask="c" fsuid=32011 ouid=32011

  Yelp is using the wrong directory. It is using:
  @{HOME}/.local/share/unity-scopes/@{APP_PKGNAME}_@{APP_APPNAME}

  but apparmor policy says to use:
  @{HOME}/.local/share/unity-scopes/leaf-net/@{APP_PKGNAME}

  Note: this is a different bug than the one dealing with
  XDG_RUNTIME_DIR paths, where we do use @{APP_APPNAME}.

  Adding rtm14 tag with High priority since this seems to affect scopes
  in the store. Please readjust as necessary.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1376416/+subscriptions

-- 
Mailing list: https://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 1373221] Re: guvcview crashed with SIGSEGV in get_ctrl_by_id()

[Alberto Salvia Novella]

Paulo Assis:
> 1.7.3 won't work with kernels >=3.16, you will need a newer version,
> uvcvideo suffered a regression that will only be fixed (hopefully) in
> 3.18, the developer already posted a patch to fix it.
> I'll make a new release (2.0.1) in the next couple of days with a
> workaround for this. you will need this version to get guvcview up and
> running with uvcvideo devices.
>
> Note: libv4l2 (1.4.0 and 1.5.0) is also broken, a fix is expected in
> 1.6.0, but you will be able to disable its use in guvcview in this
> version.

What are you plans to guvcview not to be affected by these breakdowns in 
future?

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

Title:
  guvcview crashed with SIGSEGV in get_ctrl_by_id()

Status in GTK uvc viewer:
  Confirmed
Status in One Hundred Papercuts:
  Triaged
Status in libv4l v4l-utils:
  Confirmed
Status in “guvcview” package in Ubuntu:
  Triaged
Status in “v4l-utils” package in Ubuntu:
  Triaged

Bug description:
  HOW TO REPRODUCE:
  - Launch guvcview

  EXPECTED BEHAVIOUR:
  - The application to start normally.

  REAL BEHAVIOUR:
  - The application crashes.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: guvcview 1.7.3-1.1build2
  ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3
  Uname: Linux 3.16.0-17-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Sep 24 06:35:20 2014
  ExecutablePath: /usr/bin/guvcview
  InstallationDate: Installed on 2013-05-21 (490 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  ProcCmdline: guvcview
  SegvAnalysis:
   Segfault happened at: 0x42d970:  mov0x0,%eax
   PC (0x0042d970) ok
   source "0x0" (0x) not located in a known VMA region (needed readable 
region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: guvcview
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   __libc_start_main (main=0x409920, argc=1, argv=0x7fff32c34208, 
init=, fini=, rtld_fini=, 
stack_end=0x7fff32c341f8) at libc-start.c:287
  Title: guvcview crashed with SIGSEGV in __libc_start_main()
  UpgradeStatus: Upgraded to utopic on 2014-09-24 (0 days ago)
  UserGroups: adm lpadmin sambashare sudo

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

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

[Touch-packages] [Bug 1376430] [NEW] some scopes need access to android libraries

[Jamie Strandboge]

Public bug reported:

Oct  1 18:13:04 ubuntu-phablet kernel: [  130.672099]
(1)[6551:scoperunner]type=1400 audit(1412187184.960:123):
apparmor="DENIED" operation="open" profile=""
name="/android/system/lib/libGLESv2.so" pid=6551 comm="scoperunner"
requested_mask="r" denied_mask="r" fsuid=32011 ouid=0

** Affects: apparmor-easyprof-ubuntu (Ubuntu)
 Importance: Critical
 Assignee: Jamie Strandboge (jdstrand)
 Status: In Progress

** Affects: apparmor-easyprof-ubuntu (Ubuntu RTM)
 Importance: Critical
 Assignee: Jamie Strandboge (jdstrand)
 Status: In Progress


** Tags: application-confiement rtm14 touch-2014-10-09

** Also affects: apparmor-easyprof-ubuntu (Ubuntu RTM)
   Importance: Undecided
   Status: New

** Changed in: apparmor-easyprof-ubuntu (Ubuntu)
   Importance: Undecided => Critical

** Changed in: apparmor-easyprof-ubuntu (Ubuntu)
   Status: New => In Progress

** Changed in: apparmor-easyprof-ubuntu (Ubuntu)
 Assignee: (unassigned) => Jamie Strandboge (jdstrand)

** Changed in: apparmor-easyprof-ubuntu (Ubuntu RTM)
   Status: New => In Progress

** Changed in: apparmor-easyprof-ubuntu (Ubuntu RTM)
   Importance: Undecided => Critical

** Changed in: apparmor-easyprof-ubuntu (Ubuntu RTM)
 Assignee: (unassigned) => Jamie Strandboge (jdstrand)

** Tags added: application-confiement rtm14 touch-2014-10-09

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

Title:
  some scopes need access to android libraries

Status in “apparmor-easyprof-ubuntu” package in Ubuntu:
  In Progress
Status in “apparmor-easyprof-ubuntu” package in Ubuntu RTM:
  In Progress

Bug description:
  Oct  1 18:13:04 ubuntu-phablet kernel: [  130.672099]
  (1)[6551:scoperunner]type=1400 audit(1412187184.960:123):
  apparmor="DENIED" operation="open" profile=""
  name="/android/system/lib/libGLESv2.so" pid=6551 comm="scoperunner"
  requested_mask="r" denied_mask="r" fsuid=32011 ouid=0

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

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

[Touch-packages] [Bug 1376436] [NEW] thumbnailer icon denial

[Jamie Strandboge]

Public bug reported:

apparmor="DENIED" operation="open" 
 profile="com.ubuntu.camera_camera_3.0.0.387" 
 name="/usr/share/thumbnailer/icons/video_missing.png" 
 pid=7499 comm="QQuickPixmapRea" requested_mask="r" 
 denied_mask="r" fsuid=32011 ouid=0

** Affects: apparmor-easyprof-ubuntu (Ubuntu)
 Importance: High
 Assignee: Jamie Strandboge (jdstrand)
 Status: In Progress

** Affects: apparmor-easyprof-ubuntu (Ubuntu RTM)
 Importance: High
 Assignee: Jamie Strandboge (jdstrand)
 Status: In Progress


** Tags: application-confinement rtm14 touch-2014-10-09

** Also affects: apparmor-easyprof-ubuntu (Ubuntu RTM)
   Importance: Undecided
   Status: New

** Changed in: apparmor-easyprof-ubuntu (Ubuntu RTM)
   Status: New => In Progress

** Changed in: apparmor-easyprof-ubuntu (Ubuntu RTM)
   Importance: Undecided => High

** Changed in: apparmor-easyprof-ubuntu (Ubuntu RTM)
 Assignee: (unassigned) => Jamie Strandboge (jdstrand)

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

Title:
  thumbnailer icon denial

Status in “apparmor-easyprof-ubuntu” package in Ubuntu:
  In Progress
Status in “apparmor-easyprof-ubuntu” package in Ubuntu RTM:
  In Progress

Bug description:
  apparmor="DENIED" operation="open" 
   profile="com.ubuntu.camera_camera_3.0.0.387" 
   name="/usr/share/thumbnailer/icons/video_missing.png" 
   pid=7499 comm="QQuickPixmapRea" requested_mask="r" 
   denied_mask="r" fsuid=32011 ouid=0

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

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

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

[wlraider70]

Sorry for the vauge message erlier.


server@gateway:~$ sudo apt-get upgrade -y
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done

start: Job is already running: systemd-logind
invoke-rc.d: initscript systemd-logind, action "start" failed.
dpkg: error processing package libpam-systemd:amd64 (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 dbus
 language-selector-common
 libpam-systemd:amd64

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

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

Status in “systemd” package in Ubuntu:
  Fix Released
Status in “systemd” source package in Trusty:
  Triaged
Status in “systemd” source package in Utopic:
  Fix Released

Bug description:
  Hi,

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

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

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

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

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

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

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

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

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

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

  
  perhaps related to older launchpad bug #1305395 ?

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

  
  thanks,
  Hamish

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

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

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

[wlraider70]

E: Sub-process /usr/bin/dpkg returned an error code (1)



(hmmm, no way to edit comments? That's not good for me)

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

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

Status in “systemd” package in Ubuntu:
  Fix Released
Status in “systemd” source package in Trusty:
  Triaged
Status in “systemd” source package in Utopic:
  Fix Released

Bug description:
  Hi,

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

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

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

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

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

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

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

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

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

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

  
  perhaps related to older launchpad bug #1305395 ?

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

  
  thanks,
  Hamish

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

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

[Touch-packages] [Bug 1376437] [NEW] [FFe] LXC 1.1~alpha2

[Stéphane Graber]

Public bug reported:

Dear release team,

LXC 1.1~alpha2 was just tagged upstream and we'd like to get that into
Ubuntu 14.10.

The main reasons for this are:
 - Isn't broken on the current utopic kernel
 - Makes nova-compute-flex work properly
 - Fix LXC to work on Ubuntu systems running with systemd
 - Fixes a bunch of bugs which have now been fixed in Trusty (through the 1.0.6 
release)

The main features that were added between alpha1 and alpha2 are:
 - openvswitch support (required for nova-compute-flex and a candidate for 
inclusion in stable)
 - lxc-start now defaults to backgrounded mode (I will revert that change prior 
to upload to avoid potential last minute breakages)
 - Support for checkpoint/restart with recent CRIU. This feature will however 
not be available in 14.10 due to the ancient CRIU currently in the archive.
 - Introduction of lxc-top which used to be only available in our PPA through 
the lua-lxc package. It's now been rewritten in C and is included in the 
default set of commands.

The whole changelog is:
 - pivot_root: umount ., not /
 - sysconfig/lxc: Reverse sourcing logic
 - apparmor: restrict signal and ptrace for processes
 - add file/func/line to debug info
 - fixups to init script rework
 - Rework init scripts
 - doc: Drop lxc.pivotdir from Japanese lxc.container.conf(5)
 - apparmor: silence 'silent' mount denials
 - Include network prefix when ipv4/ipv6 keys are queried
 - add src/python-lxc/setup.py into .gitignore
 - Fix presentation of IPv6 addresses and gateway
 - Initialize cgroups on lxc-checkpoint -r
 - lxc-checkpoint should fail if criu gets signal
 - doc: Update Japanese lxc-top(1) for porting C version
 - doc: Add lxc.aa_allow_incomplete flag to Japanese man
 - port lxc-top from lua to C for wider availability
 - download: Make --keyserver actually work
 - doc: Add description about ignoring lxc.cgroup.use when using cgmanager
 - Fix typo in lsm.h breaking android build
 - Fix the unprivileged tests cgroup management
 - document the new lxc.aa_allow_incomplete flag
 - Fix build error(ISO C90 specs violation) in lxc.c
 - apparmor: make sure sysfs and securityfs are mounted when checking for mount 
feature
 - apparmor: improve behavior when kernel lacks mount restrictions (v2)
 - pivot_root: switch to a new mechanism (v2)
 - log: fix quiet mode
 - support use of 'all' containers when cgmanager supports it
 - lxc-checkpoint should actually log things
 - tests: require criu >= 1.3.1 for criu test
 - c/r: use --restore-sibling option in CRIU
 - lxc_map_ids: add a comment
 - lxc-gentoo: keep original uid/gid of files/dirs when installing
 - finalize handler in lxcapi_restore
 - Exit on errors in restore()'s worker
 - Allow criu >= 1.3 in c/r test
 - lxc-checkpoint: use --force-irmap criu option
 - lxc-plamo: keep original uid/gid of files/dirs when installing
 - config: fix the handling of lxc.hook and hwaddrs in unexpanded config
 - Discontinue the use of in-line comments
 - Report container exit status to monitord
 - lxc-cgm: fix issue with nested chowning
 - doc: Translate lxc-checkpoint(1) into Japanese
 - Add lxc-restore-net to extra_DIST
 - Fix build failure due to wrong test name
 - handle hashed command socket names (v2)
 - Add support for checkpoint and restore via CRIU
 - build: Make setup.py run from srcdir to avoid distutils errors
 - build: don't remove configuration template on clean
 - tests: Copy the download cache when available [v2]
 - Prevent compiler warning by initializing ifindex
 - lxc-user-nic: be more paranoid
 - lxc-archlinux: Properly set default locale in /etc/locale.conf
 - Additional checks in ALTLinux template
 - Update the openvswitch bridge attach code
 - use lxcpath as unprivileged containers log directory
 - statvfs: do nothing if statvfs does not exist (android/bionic)
 - lxc_mount_auto_mounts: honor existing nodev etc at remounts
 - mount_entry: use statvfs
 - build: Fix support for split build and source dirs
 - chmod container dir to 0770 (v2)
 - load_config_locked: update unexp network
 - ignore SIGKILL (CTRL-C) and SIGQUIT (CTRL-\) - issue #313
 - show additional info if btrfs subvolume deletion fails (issue #315)
 - lxc_map_ids: don't do bogus chekc for newgidmap
 - Update plamo template
 - doc: Fix Japanese translation of lxc.containers.conf(5)
 - tests: Call sync before testing a shutdown
 - do_mount_entry: add nexec, nosuid, nodev, rdonly flags if needed at remount
 - monitor: fix sockname calculation for long lxcpaths
 - command socket: use hash if needed
 - Revert "chmod container dir to 0770"
 - Fix typo in the previous commit...
 - Add extra debugging
 - Updated template for ALTLinux.
 - doc: language correction
 - As discussed on ML, do not clean autodev dir on reboot
 - clean autodev dir on container exit
 - chmod container dir to 0770
 - cgmanager get/set: clean up child (v2)
 - introduce --with-distro=raspbian
 - lxc-test-unpriv: test lxc-clone -s
 - coverity: malloc the right size for btrs_node tree
 - coverity: do

[Touch-packages] [Bug 1334807] Re: gallery-app crashes when trying to delete multiple photos

[Brendan Donegan]

Not reproducible on the latest RTM image (#75). There is another bug
with the tabulation of the number of images (it counts the event as an
image), but this bug I can't reproduce.

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

Title:
  gallery-app crashes when trying to delete multiple photos

Status in Gallery App:
  In Progress
Status in “gallery-app” package in Ubuntu:
  In Progress

Bug description:
  Mako #162
  OOPS: https://errors.ubuntu.com/oops/00ec1658-1892-11e4-9140-fa163e5bb1a2

  On the main Events page when I try to delete multiple images from
  different days the app crashes.

  TEST CASE:
  1. Open the camera and take several photos (half a dozen)
  2. Open the gallery
  3. Long press the shape with the date of the day to select all the photos 
that have just been taken.
  2. Tap 'Delete' in the toolbar

  ACTUAL RESULT
  the app crashes. see the attached .crash file.

  EXPECTED RESULT
  It doesn't crash

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: gallery-app (not installed)
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.3-0ubuntu2
  Architecture: armhf
  Date: Thu Jun 26 23:50:19 2014
  InstallationDate: Installed on 2014-06-26 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140626-020204)
  SourcePackage: gallery-app
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1248326] Re: Invalidated tokens not handled gracefully

[Rodney Dawes]

** Changed in: ubuntuone-client
   Status: Confirmed => Won't Fix

** Changed in: ubuntuone-control-panel
   Status: Fix Committed => Fix Released

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

Title:
  Invalidated tokens not handled gracefully

Status in Ubuntu One Client:
  Won't Fix
Status in Ubuntu One Control Panel:
  Fix Released
Status in “ubuntuone-credentials” package in Ubuntu:
  Confirmed
Status in “unity-scope-click” package in Ubuntu:
  Fix Released

Bug description:
  Currently, when you remove a token/device from U1, you're stuck with a broken 
account.
  U1 client applications should handle this more gracefully and ask the user 
for his password again and get a new token, transparently.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntuone-client/+bug/1248326/+subscriptions

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

[Touch-packages] [Bug 1373462] Re: [background] Preview/Background is black for some images

[Michael Terry]

unity8 (8.00+14.10.20140930.2-0ubuntu1) utopic; urgency=low

  [ Alexandros Frantzis ]
  * Remove stale trusted socket before starting unity8 from upstart (LP:
#1371597) (LP: #1371597)

  [ CI bot ]
  * Resync trunk

  [ Andrea Cimitan ]
  * Move activity indicator on top of keyboard (LP: #1354519)

  [ Gerry Boland ]
  * Cleanup: Remove unused member and fix small syntax error in
OrientationLock

  [ josharenson ]
  * Fix lp:1367894 by correcting how the minute value is calculated in
the panel. (LP: #1367894)

  [ Nick Dedekind ]
  * Fixed DefaultIndicatorPage test. Fixed warnings from test.

  [ Ying-Chun Liu ]
  * Remove maxLineCount in preview. (LP: 1328513) (LP: #1328513)

  [ Michael Terry ]
  * Fix some code that accidentally landed in trunk before it got
cleaned up. The current code just has some duplication to it that
should be unified.
  * Implement latest visual designs for passphrase lockscreen.
  * Make it easier to use the Lockscreen component from the welcome
wizard.
  * Limit how much memory we reserve for the greeter background image,
allowing giant images to appear correctly.

  [ Daniel d'Andrada ]
  * Add gdbTestComponentName build targets
 -- Ubuntu daily releaseTue, 30 Sep 2014 
16:57:28 +

** Changed in: unity8 (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  [background] Preview/Background is black for some images

Status in “ubuntu-system-settings” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu:
  Fix Released

Bug description:
  With some images the preview and the background is black but the image
  is fine in the gallery app.

  For example picture attached looks correct, but preview and background
  are black.

  TEST CASE:
  1. Upload the attached picture to the phone with mtp
  2. Go to system-settings / background
  3. Tap 'Add an image'
  4. Select this image
-> Verify that the preview is correct
  5. Validate your choice,
  6. Press the power button twice to show the greeter
-> Verify that the background is correct

  ACTUAL RESULT
  Background and preview are black.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: ubuntu-system-settings 0.3+14.10.20140913-0ubuntu1 [origin: Ubuntu 
RTM]
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: armhf
  Date: Wed Sep 24 16:34:18 2014
  InstallationDate: Installed on 2014-09-16 (8 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140916-030205)
  SourcePackage: ubuntu-system-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1354571] Re: apport-retrace ignores warnings from gdb

[Brian Murray]

** Description changed:

- I was trying to investigate a failed retrace on armhf and received the
- following when running apport-retrace with -g.
+ [Impact]
+ Crash reports with damaged core dumps are being sent to the Ubuntu Error 
Tracker, where they are added to the retracing queue and then an attempt is 
made to retrace them. These retraces fail because the core dump is damaged so 
resources are wasted.  We should stop sending these to the Error Tracker.
+ 
+ [Test Case]
+ apport's test_report.py has gained a new test called 
test_add_gdb_info_damaged which tests that a crash report with a damaged core 
dump raises an IOError.
+ Running this test with the version of the package in trusty-updates will fail 
with an AssertionError.
+ Running the test with the version of the package from trusty-proposed will 
pass.
+ 
+ 
+ I was trying to investigate a failed retrace on armhf and received the 
following when running apport-retrace with -g.
  
  Calling gdb command: gdb-multiarch --ex 'set architecture arm' --ex 'set 
gnutarget elf32-littlearm' --ex 'set debug-file-directory /tmp/apport
  -utopic/usr/lib/debug' --ex 'set solib-absolute-prefix /tmp/apport-utopic' 
--ex 'file "/tmp/apport-utopic//usr/lib/ubuntu-push-client/signing-
  helper"' --ex 'core-file /tmp/apport_core_36z3Va'
  GNU gdb (Ubuntu 7.7-0ubuntu3.2) 7.7
  Copyright (C) 2014 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .
  For help, type "help".
  Type "apropos word" to search for commands related to "word".
  The target architecture is assumed to be arm
  Reading symbols from 
/tmp/apport-utopic//usr/lib/ubuntu-push-client/signing-helper...Reading symbols 
from /tmp/apport-utopic/usr/lib/debug/.bu
  ild-id/0d/28e75c6b9149132f8940077618a904989a75ed.debug...done.
  done.
  BFD: Warning: /tmp/apport_core_36z3Va is truncated: expected core file size 
>= 19316736, found: 9502720.
  [New LWP 15327]
  [New LWP 15530]
  [New LWP 15321]
  Cannot access memory at address 0xb6fa7948
  Cannot access memory at address 0xb6fa7944
  
  When running apport-retrace with -o, a new crash file is created with a
  broken Stacktrace.  This makes sense given that the core file is
  corrupt.
  
  However, I think apport-retrace should do something different here, as
  you have no idea why the retraced report is bad. Maybe it should write a
  RetraceFailure key to the report, not write the report at all, or just
  exit with an error regarding the core file size difference.

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

Title:
  apport-retrace ignores warnings from gdb

Status in “apport” package in Ubuntu:
  Fix Released
Status in “apport” source package in Trusty:
  In Progress

Bug description:
  [Impact]
  Crash reports with damaged core dumps are being sent to the Ubuntu Error 
Tracker, where they are added to the retracing queue and then an attempt is 
made to retrace them. These retraces fail because the core dump is damaged so 
resources are wasted.  We should stop sending these to the Error Tracker.

  [Test Case]
  apport's test_report.py has gained a new test called 
test_add_gdb_info_damaged which tests that a crash report with a damaged core 
dump raises an IOError.
  Running this test with the version of the package in trusty-updates will fail 
with an AssertionError.
  Running the test with the version of the package from trusty-proposed will 
pass.

  
  I was trying to investigate a failed retrace on armhf and received the 
following when running apport-retrace with -g.

  Calling gdb command: gdb-multiarch --ex 'set architecture arm' --ex 'set 
gnutarget elf32-littlearm' --ex 'set debug-file-directory /tmp/apport
  -utopic/usr/lib/debug' --ex 'set solib-absolute-prefix /tmp/apport-utopic' 
--ex 'file "/tmp/apport-utopic//usr/lib/ubuntu-push-client/signing-
  helper"' --ex 'core-file /tmp/apport_core_36z3Va'
  GNU gdb (Ubuntu 7.7-0ubuntu3.2) 7.7
  Copyright (C) 2014 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reportin

[Touch-packages] [Bug 1376445] [NEW] Addition of signon-apparmor-extension causes token lookup problems

[Rodney Dawes]

Public bug reported:

As of image ~264 of ubuntu-touch, the signon-apparmor-extension package
is included. As a result, apps like pay-ui cannot find the token any
longer, and are not being notified that they are not allowed to access
the token. The following error appears in the payui log file:

2014-10-01 19:15:51,550 - DEBUG -
../../../../lib/SignOn/authsessionimpl.cpp 184 errorSlot
QDBusError("com.google.code.AccountsSSO.SingleSignOn.Error.PermissionDenied",
"Client has insuficient permissions to access the
service.Method:getAuthSessionObjectPath")

** Affects: ubuntuone-credentials (Ubuntu)
 Importance: Critical
 Status: Triaged

** Affects: ubuntuone-credentials (Ubuntu RTM)
 Importance: Critical
 Status: Triaged


** Tags: rtm14 touch-2014-10-09

** Also affects: ubuntuone-credentials (Ubuntu RTM)
   Importance: Undecided
   Status: New

** Changed in: ubuntuone-credentials (Ubuntu RTM)
   Status: New => Triaged

** Changed in: ubuntuone-credentials (Ubuntu RTM)
   Importance: Undecided => Critical

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

Title:
  Addition of signon-apparmor-extension causes token lookup problems

Status in “ubuntuone-credentials” package in Ubuntu:
  Triaged
Status in “ubuntuone-credentials” package in Ubuntu RTM:
  Triaged

Bug description:
  As of image ~264 of ubuntu-touch, the signon-apparmor-extension
  package is included. As a result, apps like pay-ui cannot find the
  token any longer, and are not being notified that they are not allowed
  to access the token. The following error appears in the payui log
  file:

  2014-10-01 19:15:51,550 - DEBUG -
  ../../../../lib/SignOn/authsessionimpl.cpp 184 errorSlot
  QDBusError("com.google.code.AccountsSSO.SingleSignOn.Error.PermissionDenied",
  "Client has insuficient permissions to access the
  service.Method:getAuthSessionObjectPath")

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

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

[Touch-packages] [Bug 1376443] [NEW] Default ACL not inherited as Access ACL on copy

[Bib]

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

Public security bug reported:

Ubuntu Desktop 14.04 fresh default installation
Default ACL and gid are set OK on parent folder (/srv/parent). (ext4)
mkdir child /srv/parent
and
touch /srv/parent/file /srv/parent/child/file
OK Both /srv/parent/file, /srv/parent/child/,  /srv/parent/child/file show 
correct same acl as /srv/parent (getfacl)

cp -r /media///SomeTree ends in corrupted ACL where Access ACL 
mask::--- instead of rwx, resulting in acl set for named users and groups are 
ineffective. KO
Although, default:mask::rwx is ok.

For regular (i.e. non dir) files in the copied SomeTree,  Access ACL
mask::r-- instead of rwx, resulting in only r out of the set permissions
for named users and groups will survive. KO

setfacl --set or -m reports no error

Workaround : grant permissions to users that would not have them, eg.
o+rX or adduser reader writersgroup

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

** Information type changed from Private Security to Public Security

** Description changed:

  Ubuntu Desktop 14.04 fresh default installation
  Default ACL and gid are set OK on parent folder (/srv/parent). (ext4)
  mkdir child /srv/parent
  and
  touch /srv/parent/file /srv/parent/child/file
  OK Both /srv/parent/file, /srv/parent/child/,  /srv/parent/child/file show 
correct same acl as /srv/parent (getfacl)
  
  cp -r /media///SomeTree ends in corrupted ACL where Access ACL 
mask::--- instead of rwx, resulting in acl set for named users and groups are 
ineffective. KO
  Although, default:mask::rwx is ok.
  
  For regular (i.e. non dir) files in the copied SomeTree,  Access ACL
  mask::r-- instead of rwx, resulting in only r out of the set permissions
  for named users and groups will survive. KO
  
  setfacl --set or -m reports no error
  
- Workaround : grant permissions to users would not have them, eg. o+rX or
- adduser reader writersgroup
+ Workaround : grant permissions to users that would not have them, eg.
+ o+rX or adduser reader writersgroup

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

Title:
  Default ACL not inherited as Access ACL on copy

Status in “acl” package in Ubuntu:
  New

Bug description:
  Ubuntu Desktop 14.04 fresh default installation
  Default ACL and gid are set OK on parent folder (/srv/parent). (ext4)
  mkdir child /srv/parent
  and
  touch /srv/parent/file /srv/parent/child/file
  OK Both /srv/parent/file, /srv/parent/child/,  /srv/parent/child/file show 
correct same acl as /srv/parent (getfacl)

  cp -r /media///SomeTree ends in corrupted ACL where Access ACL 
mask::--- instead of rwx, resulting in acl set for named users and groups are 
ineffective. KO
  Although, default:mask::rwx is ok.

  For regular (i.e. non dir) files in the copied SomeTree,  Access ACL
  mask::r-- instead of rwx, resulting in only r out of the set
  permissions for named users and groups will survive. KO

  setfacl --set or -m reports no error

  Workaround : grant permissions to users that would not have them, eg.
  o+rX or adduser reader writersgroup

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

-- 
Mailing list: https://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 1347147] Re: krb5 database operations enter infinite loop

[Sam Hartman]

> "Iain" == Iain Lane  writes:

Iain> Thanks Sam, I've uploaded krb5.  ** Changed in: krb5 (Ubuntu
Iain> Trusty) Status: Triaged => In Progress

Hi.
I haven't seen this hit proposed yet.
Is that expected?  What is the next step?

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

Title:
  krb5 database operations enter infinite loop

Status in The GNU Compiler Collection:
  Fix Released
Status in Network Authentication System:
  Unknown
Status in “gcc-4.8” package in Ubuntu:
  Fix Released
Status in “gcc-4.9” package in Ubuntu:
  Fix Released
Status in “krb5” package in Ubuntu:
  Fix Released
Status in “gcc-4.8” source package in Trusty:
  Confirmed
Status in “krb5” source package in Trusty:
  In Progress

Bug description:
  [Impact]

  On krb5 KDC databases with more than a few hundred principals,
  operations can enter an infinite loop in the database library.  This
  affects both read and write operations.  If operators are fortunate,
  they will encounter this bug while testing a migration.  If they are
  not so fortunate, they will encounter this bug in a production KDC
  when the number of principals crosses the threshold where this bug
  manifests, resulting in a service outage and possible database
  corruption.  Probably the only way to restore service in that
  situation is to install a patched KDC or to downgrade to an unaffected
  version.

  Both Trusty and Utopic amd64 have been verified to have this issue.

  One concrete reported example is an invocation of kdb5_util load (as
  part of a slave KDC propagation) spinning:

  http://mailman.mit.edu/pipermail/kerberos/2014-July/020007.html

  Additional failure modes are likely

  A branch is linked including the upstream work around for this bug,
  along with two other patches to bugs already nominated for trusty
  applied to the krb5 in trusty.

  For utopic, the simplest fix is to rebuild krb5 with the compiler
  currently in utopic.  An alternative is to request that the Debian
  maintainers (both monitoring this bug for such a request) upload the
  upstream work around to Debian and sync that.  You could do an ubuntu-
  specific upload but it seems undesirable to introduce a change between
  Ubuntu and Debian when all the right parties are happy to avoid it.

  The upstream patch works around a compiler optimizer bug in the
  gcc-4.8 series, which incorrectly deduces that a strict aliasing
  violation has occurred and miscompiles part of the bundled libdb2
  library that the KDC database back end depends upon.  The
  miscompilation causes a data structure to contain an inappropriate
  cycle, which leads to an infinite loop when the structure is
  traversed.

  [Test Case]

  apt-get install krb5-kdc krb5-admin-server
  kdb5_util -W -r T create -s
  awk 'BEGIN{ for (i = 0; i < 1024; i++) { printf("ank -randkey a%06d\n", i) } 
}' /dev/null | kadmin.local -r T

  (Enter any password for the master key when requested.)

  On platforms with this issue, kadmin.local spins consuming 100% CPU
  after a few hundred principals have been created.  (This is "a000762"
  on two examples.)

  To clean up,

  rm /etc/krb5kdc/principal*

  or

  krb5kdc -r T destroy

  but the latter can possibly enter the same infinite loop.

  [Regression Potential]

  Negligible.

  It is theoretically possible that our upstream workaround, which
  involves using TAILQ macros instead of CIRCLEQ macros in the bundled
  libdb2 that backs the KDC database, will have some as-yet undiscovered
  bugs or compiler interactions with consequences worse than this
  current issue.  I think this is rather unlikely.

  The patched libdb2 passes both the extensive libdb2 test suite and the
  rest of the krb5 test suite.  Prior to patching, compiling krb5 with
  an affected gcc would cause the krb5 test suite to stall when it
  reached the libdb2 test suite.  (The test suite stall is how we became
  aware of the gcc optimizer bug.)

  The BSD TAILQ macros are generally considered to be safer than the
  CIRCLEQ macros, and the various open-source BSD derivatives have made
  the corresponding change to their libdb sources years ago, with no
  reported ill effects that I can see.

  Original report from Ben Kaduk:

  ==

  In some conditions, propagating a kerberos database to a slave KDC server can 
stall.
  This is due to a misoptimization by gcc 4.8 of the CIRCLEQ famliy of macros, 
apparently due to overzealous strict aliasing deductions.

  One case of this stall is reported at
  http://mailman.mit.edu/pipermail/kerberos/2014-July/020007.html (and
  the rest of the thread), and there is an entry in the upstream
  bugtracker at http://krbdev.mit.edu/rt/Ticket/Display.html?id=7860 .

  gcc 4.9 (as used in Debian unstable at present) is not believed to
  induce this problem.  Upstream has patched their code to use the TAILQ
  family of macr

[Touch-packages] [Bug 1376447] [NEW] When forcing TLSv1.2, the cipher list is truncated

[Marc Deslauriers]

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

Public security bug reported:

Back in 2012, enabling TLSv1.2 would break connecting to certain
servers. This was worked around in two ways in Ubuntu 12.04 LTS:

- OPENSSL_MAX_TLS1_2_CIPHER_LENGTH was set to 50, so that the cipher list sent 
would be truncated and wouldn't cause failures when connecting to certain 
servers that couldn't handle > 256 bytes
- OPENSSL_NO_TLS1_2_CLIENT was set to disable TLSv1.2 for clients by default

Although TLSv1.2 is disabled by default for clients, if it is forced,
the cipher list gets truncated.

This will cause the following issues:
- Important ciphers may get dropped
- Secure renegotiation breaks

Ubuntu 14.04 LTS shipped with TLSv1.2 turned on by default, and two
years later a lot of problematic equipment has been replaced or
upgraded.

** Affects: openssl (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: openssl (Ubuntu Precise)
 Importance: Undecided
 Assignee: Marc Deslauriers (mdeslaur)
 Status: Confirmed

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

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

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

** Changed in: openssl (Ubuntu Precise)
 Assignee: (unassigned) => Marc Deslauriers (mdeslaur)

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

Title:
  When forcing TLSv1.2, the cipher list is truncated

Status in “openssl” package in Ubuntu:
  Invalid
Status in “openssl” source package in Precise:
  Confirmed

Bug description:
  Back in 2012, enabling TLSv1.2 would break connecting to certain
  servers. This was worked around in two ways in Ubuntu 12.04 LTS:

  - OPENSSL_MAX_TLS1_2_CIPHER_LENGTH was set to 50, so that the cipher list 
sent would be truncated and wouldn't cause failures when connecting to certain 
servers that couldn't handle > 256 bytes
  - OPENSSL_NO_TLS1_2_CLIENT was set to disable TLSv1.2 for clients by default

  Although TLSv1.2 is disabled by default for clients, if it is forced,
  the cipher list gets truncated.

  This will cause the following issues:
  - Important ciphers may get dropped
  - Secure renegotiation breaks

  Ubuntu 14.04 LTS shipped with TLSv1.2 turned on by default, and two
  years later a lot of problematic equipment has been replaced or
  upgraded.

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

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

[Touch-packages] [Bug 1376447] Re: When forcing TLSv1.2, the cipher list is truncated

[Marc Deslauriers]

This is brought to our attention here:

https://twitter.com/andreasdotorg/status/517328756365873152

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

Title:
  When forcing TLSv1.2, the cipher list is truncated

Status in “openssl” package in Ubuntu:
  Invalid
Status in “openssl” source package in Precise:
  Confirmed

Bug description:
  Back in 2012, enabling TLSv1.2 would break connecting to certain
  servers. This was worked around in two ways in Ubuntu 12.04 LTS:

  - OPENSSL_MAX_TLS1_2_CIPHER_LENGTH was set to 50, so that the cipher list 
sent would be truncated and wouldn't cause failures when connecting to certain 
servers that couldn't handle > 256 bytes
  - OPENSSL_NO_TLS1_2_CLIENT was set to disable TLSv1.2 for clients by default

  Although TLSv1.2 is disabled by default for clients, if it is forced,
  the cipher list gets truncated.

  This will cause the following issues:
  - Important ciphers may get dropped
  - Secure renegotiation breaks

  Ubuntu 14.04 LTS shipped with TLSv1.2 turned on by default, and two
  years later a lot of problematic equipment has been replaced or
  upgraded.

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

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

[Touch-packages] [Bug 1374215] Re: Can't invoke UnlockAllModems() twice via dbus

[Antti Kaijanmäki]

** Branch linked: lp:~unity-api-team/indicator-
network/dual_sim_pin_unlock

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

Title:
  Can't invoke UnlockAllModems() twice via dbus

Status in Network Menu:
  Triaged
Status in “indicator-network” package in Ubuntu:
  Triaged

Bug description:
  Dialer-app now calls UnlockAllModems() when needed via dbus, but it
  only works for the first time. If I call the method once and then
  cancel the sim unlock screen, I can't call it again. The method just
  returns and the sim unlock screen never appears.

  Also, I noticed that after that sometimes the contents of the network
  indicator simply disappears as if the service was not running, but it
  in fact is. No crashes are observed.

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

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

[Touch-packages] [Bug 1376437] Re: [FFe] LXC 1.1~alpha2

[Stéphane Graber]

20:59 < infinity> stgraber: So, yeah, copy and paste to bugs as
necessary, but this is me saying if you can fix things that depend on
the old lxc-start behaviour, please don't revert it, and you're okay for
the alpha2 upload.

So that's a +1 on the plan above with the change that I will not do any
revert, instead I'll first upload a new lxc-android-config passing -F to
lxc-start and have it declare a versioned dependency on LXC 1.1 alpha-2.

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

** Also affects: lxc-android-config (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: lxc-android-config (Ubuntu)
   Status: New => Triaged

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

Title:
  [FFe] LXC 1.1~alpha2

Status in “lxc” package in Ubuntu:
  Triaged
Status in “lxc-android-config” package in Ubuntu:
  Triaged

Bug description:
  Dear release team,

  LXC 1.1~alpha2 was just tagged upstream and we'd like to get that into
  Ubuntu 14.10.

  The main reasons for this are:
   - Isn't broken on the current utopic kernel
   - Makes nova-compute-flex work properly
   - Fix LXC to work on Ubuntu systems running with systemd
   - Fixes a bunch of bugs which have now been fixed in Trusty (through the 
1.0.6 release)

  The main features that were added between alpha1 and alpha2 are:
   - openvswitch support (required for nova-compute-flex and a candidate for 
inclusion in stable)
   - lxc-start now defaults to backgrounded mode (I will revert that change 
prior to upload to avoid potential last minute breakages)
   - Support for checkpoint/restart with recent CRIU. This feature will however 
not be available in 14.10 due to the ancient CRIU currently in the archive.
   - Introduction of lxc-top which used to be only available in our PPA through 
the lua-lxc package. It's now been rewritten in C and is included in the 
default set of commands.

  The whole changelog is:
   - pivot_root: umount ., not /
   - sysconfig/lxc: Reverse sourcing logic
   - apparmor: restrict signal and ptrace for processes
   - add file/func/line to debug info
   - fixups to init script rework
   - Rework init scripts
   - doc: Drop lxc.pivotdir from Japanese lxc.container.conf(5)
   - apparmor: silence 'silent' mount denials
   - Include network prefix when ipv4/ipv6 keys are queried
   - add src/python-lxc/setup.py into .gitignore
   - Fix presentation of IPv6 addresses and gateway
   - Initialize cgroups on lxc-checkpoint -r
   - lxc-checkpoint should fail if criu gets signal
   - doc: Update Japanese lxc-top(1) for porting C version
   - doc: Add lxc.aa_allow_incomplete flag to Japanese man
   - port lxc-top from lua to C for wider availability
   - download: Make --keyserver actually work
   - doc: Add description about ignoring lxc.cgroup.use when using cgmanager
   - Fix typo in lsm.h breaking android build
   - Fix the unprivileged tests cgroup management
   - document the new lxc.aa_allow_incomplete flag
   - Fix build error(ISO C90 specs violation) in lxc.c
   - apparmor: make sure sysfs and securityfs are mounted when checking for 
mount feature
   - apparmor: improve behavior when kernel lacks mount restrictions (v2)
   - pivot_root: switch to a new mechanism (v2)
   - log: fix quiet mode
   - support use of 'all' containers when cgmanager supports it
   - lxc-checkpoint should actually log things
   - tests: require criu >= 1.3.1 for criu test
   - c/r: use --restore-sibling option in CRIU
   - lxc_map_ids: add a comment
   - lxc-gentoo: keep original uid/gid of files/dirs when installing
   - finalize handler in lxcapi_restore
   - Exit on errors in restore()'s worker
   - Allow criu >= 1.3 in c/r test
   - lxc-checkpoint: use --force-irmap criu option
   - lxc-plamo: keep original uid/gid of files/dirs when installing
   - config: fix the handling of lxc.hook and hwaddrs in unexpanded config
   - Discontinue the use of in-line comments
   - Report container exit status to monitord
   - lxc-cgm: fix issue with nested chowning
   - doc: Translate lxc-checkpoint(1) into Japanese
   - Add lxc-restore-net to extra_DIST
   - Fix build failure due to wrong test name
   - handle hashed command socket names (v2)
   - Add support for checkpoint and restore via CRIU
   - build: Make setup.py run from srcdir to avoid distutils errors
   - build: don't remove configuration template on clean
   - tests: Copy the download cache when available [v2]
   - Prevent compiler warning by initializing ifindex
   - lxc-user-nic: be more paranoid
   - lxc-archlinux: Properly set default locale in /etc/locale.conf
   - Additional checks in ALTLinux template
   - Update the openvswitch bridge attach code
   - use lxcpath as unprivileged containers log directory
   - statvfs: do nothing if statvfs does not exist (android/bionic)
   - lxc_mount_auto_mounts: honor existing nodev etc at remounts
   -

[Touch-packages] [Bug 1375067] Re: Can't open pdf file from webdav share, apparmor denies access to dbus

[Jamie Strandboge]

This should already be covered by this rule in the gnome abstraction:
  unix (send, receive, connect) type=stream 
peer=(addr="@/dbus-vfs-daemon/socket-*"),

Does /etc/apparmor.d/abstractions/gnome not contain this rule?

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

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

Title:
  Can't open pdf file from webdav share, apparmor denies access to dbus

Status in “apparmor” package in Ubuntu:
  Incomplete

Bug description:
  I've recently upgraded to Ubuntu utopic.

  When trying to access a pdf file on a dav:// share, I get a
  "permission denied" error.

  
  While getting peer-to-peer dbus connection: Verbindung ist gescheitert: Keine 
Berechtigung

  In dmesg, I see this

  [ 1394.331262] audit: type=1400 audit(1411945678.080:57):
  apparmor="DENIED" operation="connect" profile="/usr/bin/evince"
  pid=18278 comm="EvJobScheduler" family="unix" sock_type="stream"
  protocol=0 requested_mask="send receive connect" denied_mask="send
  connect" addr=none peer_addr="@/dbus-vfs-daemon/socket-8Ij86BjH"
  peer="unconfined"

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

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

[Touch-packages] [Bug 1373085] Re: Parser error when using regex profile names in IPC rules

[Jamie Strandboge]

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

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

Title:
  Parser error when using regex profile names in IPC rules

Status in “apparmor” package in Ubuntu:
  In Progress

Bug description:
  I tried to add this rule to the firefox profile:
  unix (send, receive) type=stream 
peer=(label=/usr/lib/firefox/firefox\{,\*\[^s\]\[^h\]\}//plugincontainer),

  apparmor_parser fails with:
  syntax error, unexpected TOK_CONDID, expecting TOK_EQUALS or TOK_IN

  When I add quotes around the label the parser fails with:
  Found unexpected character: '"'

  I found this minimal test case:
  unix peer=(label=\{,\}),
  and
  unix peer=(label="\{,\}"),

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

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

[Touch-packages] [Bug 1339727] Re: lightdm xauthority path is wrong

[Jamie Strandboge]

** Changed in: apparmor (Ubuntu)
 Assignee: (unassigned) => Steve Beattie (sbeattie)

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

Title:
  lightdm xauthority path is wrong

Status in “apparmor” package in Ubuntu:
  Confirmed

Bug description:
  The default apparmor 'X' abstraction permits access to
  /{,var/}run/lightdm/authority/[0-9]*, ostensibly for the xauthority
  file.  Except on Trusty, that's not where the xauthority file is.  It
  is instead in /run/lightdm/$USER, and named "xauthority".   I have had
  to udpated my apparmor configuration, lest apparmor convince Evince of
  being a filthy script kiddie, out to corrupt my xauth file.

  Please consider adding the following to the 'X' abstraction:

  owner /{,var/}run/lightdm/*/xauthority r,

  Relevant info:

  apparmor:
Installed: 2.8.95~2430-0ubuntu5
Candidate: 2.8.95~2430-0ubuntu5
Version table:
   *** 2.8.95~2430-0ubuntu5 0
  500 http://mirrors.mit.edu/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1356468] Re: TOP RTM CRASHER: /usr/bin/trust-stored-skeleton:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::__cxa_rethrow:__shared_co

[Thomas Voß]

If this abort() arises during long-running tests, I would appreciate a
pointer to further information that will allow us to reproduce the
issue. I haven't seen it in quite some time and thus have difficulties
testing for it.

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

Title:
  TOP RTM CRASHER: /usr/bin/trust-stored-
  
skeleton:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::__cxa_rethrow:__shared_count

Status in “location-service” package in Ubuntu:
  Fix Released
Status in “trust-store” package in Ubuntu:
  Fix Released
Status in “location-service” package in Ubuntu RTM:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding trust-store.  This problem was most recently seen with
  version 1.0.0+14.10.20140807-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/009a6dd4d6c0da7571b0283d16f4cdf40c9d3da5
  contains more details.

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

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

[Touch-packages] [Bug 1375805] Re: Lightdm fails to start in VirtualBox

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 208-8ubuntu7

---
systemd (208-8ubuntu7) utopic; urgency=medium

  * Reinstate udev-fallback-graphics.conf fix below fails to
install this replaced init script.  Fixes brown paper bag fail.
(LP: #1375805)
 -- Andy WhitcroftWed, 01 Oct 2014 13:19:40 +0100

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

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

Title:
  Lightdm fails to start in VirtualBox

Status in “lightdm” package in Ubuntu:
  Invalid
Status in “systemd” package in Ubuntu:
  Fix Released

Bug description:
  Current daily - install and boot.

  Fails to boot.

  service lightdm status is stop/waiting

  once lightdm starts and logged in cat /proc/fb shows 0 VESA VGA - same
  result prior to lightdm start

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: lightdm 1.11.9-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3
  Uname: Linux 3.16.0-18-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  Date: Tue Sep 30 14:40:39 2014
  InstallationDate: Installed on 2014-09-30 (0 days ago)
  InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140930)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1375821] Re: ifupdown doesn't bring loopback to state up

[Launchpad Bug Tracker]

This bug was fixed in the package ifupdown - 0.7.48.1ubuntu5

---
ifupdown (0.7.48.1ubuntu5) utopic; urgency=medium

  * Fix broken loopback handling due to incorrect patching of the Debian
source. (LP: #1375821)
 -- Stephane GraberWed, 01 Oct 2014 11:43:43 -0400

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

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

Title:
  ifupdown doesn't bring loopback to state up

Status in “ifupdown” package in Ubuntu:
  Fix Released

Bug description:
  Upon booting a machine with the following setup on a relatively
  slimmed down netboot machine the loopback interface isn't brought up
  properly:

  cat /etc/network/interfaces
  auto lo
  iface lo inet loopback
  iface lo inet6 loopback

  auto eth0
  iface eth0 inet6 auto
  dhcp 1
  #iface eth0 inet ipv4ll

  auto eth1
  iface eth1 inet6 auto
  dhcp 1
  #iface eth1 inet ipv4ll

  Upon boot Loopback is unconfigured:
  root@:~# ip addr show dev lo
  1: lo:  mtu 65536 qdisc noop state DOWN group default 
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

  Try to bring the interface up:
  root@:~# ifup -v lo
  ifup: interface lo already configured

  Bring it down and up:
  root@:~# ifdown -v lo
  Configuring interface lo=lo (inet)
  run-parts --verbose /etc/network/if-down.d
  run-parts: executing /etc/network/if-down.d/avahi-autoipd
  run-parts: executing /etc/network/if-down.d/upstart
  run-parts --verbose /etc/network/if-post-down.d
  Configuring interface lo=lo (inet)
  run-parts --verbose /etc/network/if-down.d
  run-parts: executing /etc/network/if-down.d/avahi-autoipd
  run-parts: executing /etc/network/if-down.d/upstart
  run-parts --verbose /etc/network/if-post-down.d
  Configuring interface lo=lo (inet6)
  run-parts --verbose /etc/network/if-down.d
  run-parts: executing /etc/network/if-down.d/avahi-autoipd
  run-parts: executing /etc/network/if-down.d/upstart
  run-parts --verbose /etc/network/if-post-down.d

  root@:~# ifup -v lo
  Configuring interface lo=lo (inet)
  run-parts --verbose /etc/network/if-pre-up.d
  run-parts --verbose /etc/network/if-up.d
  run-parts: executing /etc/network/if-up.d/avahi-autoipd
  run-parts: executing /etc/network/if-up.d/openssh-server
  run-parts: executing /etc/network/if-up.d/upstart
  Configuring interface lo=lo (inet)
  run-parts --verbose /etc/network/if-pre-up.d
  run-parts --verbose /etc/network/if-up.d
  run-parts: executing /etc/network/if-up.d/avahi-autoipd
  run-parts: executing /etc/network/if-up.d/openssh-server
  run-parts: executing /etc/network/if-up.d/upstart
  Configuring interface lo=lo (inet6)
  run-parts --verbose /etc/network/if-pre-up.d
  run-parts --verbose /etc/network/if-up.d
  run-parts: executing /etc/network/if-up.d/avahi-autoipd
  run-parts: executing /etc/network/if-up.d/openssh-server
  run-parts: executing /etc/network/if-up.d/upstart

  no change:
  root@:~# ip addr show dev lo
  1: lo:  mtu 65536 qdisc noop state DOWN group default 
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

  bring it down again:
  root@:~# ifdown lo

  And up, but this time with --no-loopback:
  root@:~# ifup -v --no-loopback lo
  Configuring interface lo=lo (inet)
  run-parts --verbose /etc/network/if-pre-up.d
  ip link set dev lo up
  run-parts --verbose /etc/network/if-up.d
  run-parts: executing /etc/network/if-up.d/avahi-autoipd
  run-parts: executing /etc/network/if-up.d/openssh-server
  run-parts: executing /etc/network/if-up.d/upstart
  Configuring interface lo=lo (inet6)
  run-parts --verbose /etc/network/if-pre-up.d
  ip link set dev lo up 2>/dev/null
  ip addr add dev lo ::1 2>/dev/null
  run-parts --verbose /etc/network/if-up.d
  run-parts: executing /etc/network/if-up.d/avahi-autoipd
  run-parts: executing /etc/network/if-up.d/openssh-server
  run-parts: executing /etc/network/if-up.d/upstart

  now it seems like something actually happened!

  check:
  root@:~# ip addr show dev lo
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default 
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host 
 valid_lft forever preferred_lft forever

  All seems fine, everything is working from here on.

  My expectation is that ifup should configure the interface and set
  state to up, and ifdown should set state to down, even though it's a
  loopback that may or may not be magically autoconfigured somewhere
  else.

  And a question:
  If the case is that ifup shouldn't configure the loopback, what should 
configure it?

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

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

[Touch-packages] [Bug 1333377] Re: allow 'ptrace (read) peer=@{profile_name}' in abstractions/base

[Jamie Strandboge]

This was fixed some time ago.

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

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

Title:
  allow 'ptrace (read)  peer=@{profile_name}' in abstractions/base

Status in “apparmor” package in Ubuntu:
  Fix Released

Bug description:
  Summary says it all. Not processes need ptrace read of themselves, but
  it seems quite reasonable to allow them the access by default.

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

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

[Touch-packages] [Bug 1376357] Re: lightdm writing the same DEBUG message to /var/log/lightdm/lightdm.log

[Robert Ancell]

I'd like to find out what is changing on this user every 300s - this
doesn't occur on desktop and there's nothing that I can see that should
be frequently changed for a user. The debugging is useful, but can be
removed if there is a legitimate reason for a user to change this
frequently.

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

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

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

Title:
  lightdm writing the same DEBUG message to /var/log/lightdm/lightdm.log

Status in “lightdm” package in Ubuntu:
  Incomplete

Bug description:
  I was trying to figure out where excessive file system writes were
  coming from on the ubuntu phone (to try to reduce flash writes and hence 
reduce power
  consumption) and I spotted that /var/log/lightdm/lightdm.log is getting the 
same debug message written to every every 300 seconds:

  tail -f /var/log/lightdm/lightdm.log
  [+5109.66s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+5409.67s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+5709.66s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+6009.66s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+6309.64s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+6609.65s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+6909.67s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+7209.66s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+7509.66s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+7809.57s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+8109.65s] DEBUG: User /org/freedesktop/Accounts/User32011 changed

  while this isn't much of a message, it still is causing file system
  writes every 5 minutes for the same debug message. Is this necessary?
  The fact that it is the same message about the same account and that
  it occurs every 300 seconds make me wonder if we can cull this
  particular piece of repeated logging.

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

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

[Touch-packages] [Bug 1373981] Re: ubuntu 14.10 server, amd64 - lxc-start fails to start container

[Serge Hallyn]

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

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

** Description changed:

+ =
+ ec2-run-instances ami-3021fb58 -t m1.small
+ 
+ ssh into the instance,
+ 
+ sudo ip link add type veth
+ 
+ fails.  I also often cannot log in.  I think it's just a bad
+ ami, but am not sure.
+ =
  I had previously created an lxc container successfully using either:
  $ sudo lxc-create -t download -n test_cn
  -or-
  $ sudo lxc-create -t ubuntu -n test_cn
  
  However... when trying to start it fails with the following?
-  
+ 
  $ sudo lxc-start -n test_cn
  lxc-start: failed to create vethBQ6TPB-vethV9VF9A : Operation not supported
  lxc-start: failed to create netdev
  lxc-start: failed to create the network
  lxc-start: failed to spawn 'test_cn'
  lxc-start: The container failed to start.
  lxc-start: Additional information can be obtained by setting the --logfile 
and --log-priority options.
  
  To check if the "veth" kernel module is loaded I updated the server and
  rebooted
  
  I ran "sudo modprobe veth" and it shows an error also?
  
  $ sudo modprobe veth
  modprobe: ERROR: could not insert 'veth': Cannot allocate memory
  
- 
  This server is running on AWS EC2.
  
  $ uname -a
  Linux ip-10-69-148-9 3.16.0-10-generic #15-Ubuntu SMP Thu Aug 21 16:26:44 UTC 
2014 x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  ubuntu 14.10 server, amd64 - lxc-start fails to start container

Status in “linux” package in Ubuntu:
  Invalid

Bug description:
  =
  ec2-run-instances ami-3021fb58 -t m1.small

  ssh into the instance,

  sudo ip link add type veth

  fails.  I also often cannot log in.  I think it's just a bad
  ami, but am not sure.
  =
  I had previously created an lxc container successfully using either:
  $ sudo lxc-create -t download -n test_cn
  -or-
  $ sudo lxc-create -t ubuntu -n test_cn

  However... when trying to start it fails with the following?

  $ sudo lxc-start -n test_cn
  lxc-start: failed to create vethBQ6TPB-vethV9VF9A : Operation not supported
  lxc-start: failed to create netdev
  lxc-start: failed to create the network
  lxc-start: failed to spawn 'test_cn'
  lxc-start: The container failed to start.
  lxc-start: Additional information can be obtained by setting the --logfile 
and --log-priority options.

  To check if the "veth" kernel module is loaded I updated the server
  and rebooted

  I ran "sudo modprobe veth" and it shows an error also?

  $ sudo modprobe veth
  modprobe: ERROR: could not insert 'veth': Cannot allocate memory

  This server is running on AWS EC2.

  $ uname -a
  Linux ip-10-69-148-9 3.16.0-10-generic #15-Ubuntu SMP Thu Aug 21 16:26:44 UTC 
2014 x86_64 x86_64 x86_64 GNU/Linux

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

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

[Touch-packages] [Bug 1365664] Re: gdb source test suites are failing in Ubuntu14.10

[Matthias Klose]

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

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

Title:
  gdb source test suites are failing in Ubuntu14.10

Status in “binutils” package in Ubuntu:
  New
Status in “gdb” package in Ubuntu:
  Confirmed

Bug description:
  ---Problem Description---
  gdb source test suites are failing in Ubuntu14.10
   
  Machine Type = P8 
   
  ---Steps to Reproduce---
  Install a P8 system with Power KVM and then install Ubuntu 14.10 guest.
  Then try to build and execute the gdb source test suites as below.

  root@ubuntu:~# apt-get source gdb
  root@ubuntu:~# cd gdb-7.8/
  root@ubuntu:~/gdb-7.8# dpkg-buildpackage -b 2>&1 | tee gdblog

  === gdb Summary ===

  # of expected passes25009
  # of unexpected failures287
  # of unexpected successes   2
  # of expected failures  66
  # of unknown successes  1
  # of known failures 59
  # of unresolved testcases   3
  # of untested testcases 19
  # of unsupported tests  100

   
  ---uname output---
  Linux ubuntu 3.16.0-11-generic #16-Ubuntu SMP Mon Aug 25 20:02:00 UTC 2014 
ppc64le ppc64le ppc64le GNU/Linux
   
  I've retested gdb from Ubuntu 14.04 (gdb-7.7-0ubuntu3.1) in the Ubuntu 14.10 
VM provided by Pavaman and the number of failures curiously increased to 250 
(in comparison to less than 140 on 14.04), which leads me to believe that there 
is something in the environment of Ubuntu 14.10 compromising gdb functionality 
in several testcases.

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

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

[Touch-packages] [Bug 1170647] Me gustaría que mantuviéramos el contacto

[martincasc]

¡Hola!

A partir de ahora voy a utilizar Perpetuall para cambiar mis datos de
contacto.

Si no quieres que perdamos el contacto, dale una oportunidad a esta app.

A ver qué te parece.

DESCARGA PERPETUALL http://get.perpetuall.net

Copyright © 2014 Perpetuall Software S.L. All rights reserved.

Perpetuall Software S.L. Ctra. Bilbao Galdakao 6A 1er piso. Edificio
Metroalde Bilbao, Bizkaia 48004 España

 If you would like to unsubscribe and stop receiving these emails click
here: https://u816718.ct.sendgrid.net/wf/unsubscribe?upn=CvrJS5E6Zyh-
2FG-2BLAx4qXgvXB-
2Fhq0ez1WuBcloYYayDvUVXhmE6nDZjbvqWiMEfqbNHj26D7Q7VKimvdnWej787ohB6
-2BMN0i3lGQaW-
2BaahqkujMzKt7MOpEHQadDrMHlcbkwwIAmppmY7IlSF8PlgjGRTUnWSYufZcnLRZKUnUdSwpUBdzWTy29fBP-
2FWXbR88NXtrTJdUfkBKAc0SNEwe6x5TWvTRHzxVZ8tZVnpotbq7fTwOZJNRZy8NYtXEWUgHLruHdaTAg56l-
2Fo6jGHx4IA-3D-3D.

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

Title:
  After minimizing an external media, clicking on the "Files" icon on
  the Launcher doesn't restore the minimized window, but opens a new one

Status in One Hundred Papercuts:
  Triaged
Status in Unity:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  ***
   ISSUE
  ***

  HOW TO REPRODUCE

  1. Connect a removable media to the computer.
  2. On the launcher, click on the "Files" icon.
  3. On the left sidebar, click on the removable media icon or the trash.
  4. Minimize the window.
  5. Click on the "Files" icon.

  EXPECTED BEHAVIOUR

  - The Files window to be maximized.

  REAL BEHAVIOUR

  - A new window is opened.

  RELEVANT DETAILS

  - The only way to navigate between windows at this moment is to use
  the "control + tabulation" key combination, or to click again on the
  "Files" icon so windows are exposed.

  **
   SOLUTION
  **

  WORK-AROUND

  - On the launcher, left click on the "Files" icon and select the
  "unlock from Launcher" option.

  FIX

  - The launcher icon for "Files" to be treated the same way as if it
  was unlocked.

  REGRESSION POTENTIAL

  - Clicking on the "Files" icon won't send the user to its home folder,
  but to the latest opened Files window.

  
   TECHNICAL INFO
  

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu16
  ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6
  Uname: Linux 3.8.0-18-generic i686
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: i386
  Date: Fri Apr 19 11:33:13 2013
  EcryptfsInUse: Yes
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'814x493+136+38'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'182'
  InstallationDate: Installed on 2011-07-23 (635 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110426)
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to raring on 2013-04-14 (4 days ago)

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

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

[Touch-packages] [Bug 1376357] Re: lightdm writing the same DEBUG message to /var/log/lightdm/lightdm.log

[Robert Ancell]

I think this might be the XHasMessages property that is being set, since
the patch for that doesn't stop Changed from being emitted if the value
has not changed. The other properties seem to correctly check if they
are changed.

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

Title:
  lightdm writing the same DEBUG message to /var/log/lightdm/lightdm.log

Status in “lightdm” package in Ubuntu:
  Incomplete

Bug description:
  I was trying to figure out where excessive file system writes were
  coming from on the ubuntu phone (to try to reduce flash writes and hence 
reduce power
  consumption) and I spotted that /var/log/lightdm/lightdm.log is getting the 
same debug message written to every every 300 seconds:

  tail -f /var/log/lightdm/lightdm.log
  [+5109.66s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+5409.67s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+5709.66s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+6009.66s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+6309.64s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+6609.65s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+6909.67s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+7209.66s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+7509.66s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+7809.57s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+8109.65s] DEBUG: User /org/freedesktop/Accounts/User32011 changed

  while this isn't much of a message, it still is causing file system
  writes every 5 minutes for the same debug message. Is this necessary?
  The fact that it is the same message about the same account and that
  it occurs every 300 seconds make me wonder if we can cull this
  particular piece of repeated logging.

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

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

[Touch-packages] [Bug 1354571] Re: apport-retrace ignores warnings from gdb

[Brian Murray]

We should also see a decrease in the growth rate of the graphite metric
missing.missing_sas_amd64.count at least when the fixed version of the
package moves to -updates.

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

Title:
  apport-retrace ignores warnings from gdb

Status in “apport” package in Ubuntu:
  Fix Released
Status in “apport” source package in Trusty:
  In Progress

Bug description:
  [Impact]
  Crash reports with damaged core dumps are being sent to the Ubuntu Error 
Tracker, where they are added to the retracing queue and then an attempt is 
made to retrace them. These retraces fail because the core dump is damaged so 
resources are wasted.  We should stop sending these to the Error Tracker.

  [Test Case]
  apport's test_report.py has gained a new test called 
test_add_gdb_info_damaged which tests that a crash report with a damaged core 
dump raises an IOError.
  Running this test with the version of the package in trusty-updates will fail 
with an AssertionError.
  Running the test with the version of the package from trusty-proposed will 
pass.

  
  I was trying to investigate a failed retrace on armhf and received the 
following when running apport-retrace with -g.

  Calling gdb command: gdb-multiarch --ex 'set architecture arm' --ex 'set 
gnutarget elf32-littlearm' --ex 'set debug-file-directory /tmp/apport
  -utopic/usr/lib/debug' --ex 'set solib-absolute-prefix /tmp/apport-utopic' 
--ex 'file "/tmp/apport-utopic//usr/lib/ubuntu-push-client/signing-
  helper"' --ex 'core-file /tmp/apport_core_36z3Va'
  GNU gdb (Ubuntu 7.7-0ubuntu3.2) 7.7
  Copyright (C) 2014 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .
  For help, type "help".
  Type "apropos word" to search for commands related to "word".
  The target architecture is assumed to be arm
  Reading symbols from 
/tmp/apport-utopic//usr/lib/ubuntu-push-client/signing-helper...Reading symbols 
from /tmp/apport-utopic/usr/lib/debug/.bu
  ild-id/0d/28e75c6b9149132f8940077618a904989a75ed.debug...done.
  done.
  BFD: Warning: /tmp/apport_core_36z3Va is truncated: expected core file size 
>= 19316736, found: 9502720.
  [New LWP 15327]
  [New LWP 15530]
  [New LWP 15321]
  Cannot access memory at address 0xb6fa7948
  Cannot access memory at address 0xb6fa7944

  When running apport-retrace with -o, a new crash file is created with
  a broken Stacktrace.  This makes sense given that the core file is
  corrupt.

  However, I think apport-retrace should do something different here, as
  you have no idea why the retraced report is bad. Maybe it should write
  a RetraceFailure key to the report, not write the report at all, or
  just exit with an error regarding the core file size difference.

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

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

[Touch-packages] [Bug 1306916] Re: cgroup-lite should be added as an explicit dependency

[Stéphane Graber]

You can read some more about cgmanager at
https://cgmanager.linuxcontainers.org

cgroup-lite's goal was simply to mount the cgroup filesystem in a
consistent manner, cgmanager instead is a daemon which handles all
cgroup actions through a dbus API and allows for proper user delegation
of cgroups including across user namespaces.

Since Ubuntu 14.04, cgmanager is the preferred way of managing cgroups.

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

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

Title:
  cgroup-lite should be added as an explicit dependency

Status in “cgmanager” package in Ubuntu:
  Fix Released
Status in “lxc” package in Ubuntu:
  Invalid

Bug description:
  Otherwise you'll get an error

  sudo lxc-start -n mycontainer
  lxc: call to cgmanager_move_pid_abs_sync(blkio) failed: invalid request
  lxc-start: Could not find writable mount point for cgroup hierarchy 11 while 
trying to create cgroup.
  lxc-start: Device or resource busy - cgroup_rmdir: failed to delete 
/sys/fs/cgroup/blkio/grp_1
  lxc-start: Device or resource busy - cgroup_rmdir: failed to delete 
/sys/fs/cgroup/cpu/sys_daemon
  lxc-start: Device or resource busy - cgroup_rmdir: failed to delete 
/sys/fs/cgroup/cpuset/
  lxc-start: failed creating cgroups
  lxc-start: failed to spawn 'mycontainer'

  Or at least let the "lxc-start" check of the presence of the "cgroup-
  lite" and show a meaningful error message.

  Ubuntu vanilla installs the "cgroup-lite" automatically, so it doesn't
  affect fresh installs.

  System: Ubuntu 14.04 64 bit
  --- 
  ApportVersion: 2.14.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  adam   2813 F pulseaudio
   /dev/snd/pcmC0D0p:   adam   2813 F...m pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-04-04 (9 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140404)
  MachineType: ASUSTeK COMPUTER INC. N56VZ
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic.efi.signed 
root=UUID=926fa7cc-6f97-4672-85a7-a1ed8f5bd842 ro rootflags=subvol=@ quiet 
splash intel_pstate=enable vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127
  Tags:  trusty
  Uname: Linux 3.13.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/06/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N56VZ.216
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N56VZ
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN56VZ.216:bd12/06/2012:svnASUSTeKCOMPUTERINC.:pnN56VZ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VZ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N56VZ
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1368827] Re: [touch] indicator needs to be able to control volume per audio role

[Steve Langasek]

This requires changes to the indicator-sound package, which is present
not only on touch images but also on the desktop.  This should therefore
go through the FFe process, and be reviewed to ensure there's no risk to
the desktop.

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

Title:
  [FFe] [touch] indicator needs to be able to control volume per audio
  role

Status in “indicator-sound” package in Ubuntu:
  New

Bug description:
  Dear Release Team,

  From the Sound design for Touch (https://wiki.ubuntu.com/Sound#Phone),
  we need to change the default behaviour of the indicator in order to
  be able to change volume per audio roles, and not only the master
  volume.

  On touch the master volume will always be at 100%, and each media role
  will have its own volume values, so we can have a different volume
  level for multimedia, ringtone and alarms.

  This can be done using the streamrestore module in pulseaudio (via another 
dbus entry point that is only enabled on touch atm):
  
http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/Developer/Clients/DBus/StreamRestore/

  There's also a sample script on python that can be used to set/get volume per 
roles:
  https://raw.githubusercontent.com/jusa/pulseaudio-utils/master/pasr.py

  And the current roles supporter by touch are: multimedia, alert, phone
  and alarm.

  This change is touch specific as it needs a combination of configs
  that are available in ubuntu-touch-session for it to be used
  (different code path that only gets used on touch).

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

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

[Touch-packages] [Bug 1354571] Re: apport-retrace ignores warnings from gdb

[Launchpad Bug Tracker]

** Branch linked: lp:~ubuntu-core-dev/ubuntu/trusty/apport/ubuntu

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

Title:
  apport-retrace ignores warnings from gdb

Status in “apport” package in Ubuntu:
  Fix Released
Status in “apport” source package in Trusty:
  In Progress

Bug description:
  [Impact]
  Crash reports with damaged core dumps are being sent to the Ubuntu Error 
Tracker, where they are added to the retracing queue and then an attempt is 
made to retrace them. These retraces fail because the core dump is damaged so 
resources are wasted.  We should stop sending these to the Error Tracker.

  [Test Case]
  apport's test_report.py has gained a new test called 
test_add_gdb_info_damaged which tests that a crash report with a damaged core 
dump raises an IOError.
  Running this test with the version of the package in trusty-updates will fail 
with an AssertionError.
  Running the test with the version of the package from trusty-proposed will 
pass.

  
  I was trying to investigate a failed retrace on armhf and received the 
following when running apport-retrace with -g.

  Calling gdb command: gdb-multiarch --ex 'set architecture arm' --ex 'set 
gnutarget elf32-littlearm' --ex 'set debug-file-directory /tmp/apport
  -utopic/usr/lib/debug' --ex 'set solib-absolute-prefix /tmp/apport-utopic' 
--ex 'file "/tmp/apport-utopic//usr/lib/ubuntu-push-client/signing-
  helper"' --ex 'core-file /tmp/apport_core_36z3Va'
  GNU gdb (Ubuntu 7.7-0ubuntu3.2) 7.7
  Copyright (C) 2014 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .
  For help, type "help".
  Type "apropos word" to search for commands related to "word".
  The target architecture is assumed to be arm
  Reading symbols from 
/tmp/apport-utopic//usr/lib/ubuntu-push-client/signing-helper...Reading symbols 
from /tmp/apport-utopic/usr/lib/debug/.bu
  ild-id/0d/28e75c6b9149132f8940077618a904989a75ed.debug...done.
  done.
  BFD: Warning: /tmp/apport_core_36z3Va is truncated: expected core file size 
>= 19316736, found: 9502720.
  [New LWP 15327]
  [New LWP 15530]
  [New LWP 15321]
  Cannot access memory at address 0xb6fa7948
  Cannot access memory at address 0xb6fa7944

  When running apport-retrace with -o, a new crash file is created with
  a broken Stacktrace.  This makes sense given that the core file is
  corrupt.

  However, I think apport-retrace should do something different here, as
  you have no idea why the retraced report is bad. Maybe it should write
  a RetraceFailure key to the report, not write the report at all, or
  just exit with an error regarding the core file size difference.

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

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

[Touch-packages] [Bug 1375194] Re: lightdm session constantly switches screen appearance

[Simon Lambourn]

Update:  I have found a workaround by .config/compiz-1 and .config/dconf
(I have a backup of the .config/dconf if this might help to debug this
issue, but not the compiz one, sorry).   This makes the screen behave
normally again...

** Attachment added: ".xsession-errors shows a whole multitude of problems 
starting with at-spi2-registryd respawning too fast, then indicator-sound 
aborting, then unity-settings-daemon aborting ..."
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1375194/+attachment/4221901/+files/.xsession-errors.old

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

Title:
  lightdm session constantly switches screen appearance

Status in “xorg” package in Ubuntu:
  New

Bug description:
  After installing regular software updates on 23 Sept, my screen
  session has become almost unusable.  The screen "appearance" (font,
  button style, window menu bar location) alternates about twice a
  second between my usual settings and what I guess are the default un-
  decorated settings.   This means that text, buttons, and input areas
  are often moving around on the screen as the font size changes or the
  window menu bar comes and goes.

  In addition, keyboard input characters take a variable time to appear (up to 
a few seconds?) and can appear in the wrong order.
  CPU utilisation is much higher when I am logged on.   See TOP output below.   
I get the same problems with any one of Chromium, Firefox, Thunderbird, Ubuntu 
Software Centre, BASH terminal window.

  When I first sign on, I get a message "system software problem
  detected" in a panel by itself, before the desktop is displayed, and
  again after the desktop is displayed.  This is connected with the bug,
  but I can't find out the details of the error.   I have selected
  "report the problem" repeatedly.

  The software installed on 23 Sept included Dbus , libdbus-1-3,  and
  dbus-x11 versions 1.6.18-0ubuntu4.2.  I tried downgrading these 3 to
  -0ubuntu4 but the problem remained after a reboot.   There were about
  20-30 packages updated at the same time, including linux-image, but I
  can't spot which might be causing the problem.   I'm using a clean
  install of ubuntu 14.04 but with my /home directory from an older
  ubuntu installation.

  
  TOP output:
  24974 simon 20   0 2357692 181696  65696 R  27.6  4.5   2:34.62 
software-c+ 
   2253 root  20   0  279028  58104  19416 S  26.6  1.4   3:19.18 Xorg  
  
  11096 simon 20   0 1391072 186192  81872 R  22.9  4.6   5:02.98 
chromium-b+ 
   3899 simon 20   0  719408  32324  17924 R  19.9  0.8   2:55.82 
hud-service 
  17259 simon 20   0 1036360 203656  48764 R  17.9  5.0   2:47.82 
thunderbird 
   4291 simon 20   0 1591956 113836  41064 S  11.6  2.8   1:20.75 compiz
  
   5857 simon 20   0  860872  76324  14440 S   5.3  1.9   1:09.93 
gnome-term+ 
   3915 simon 20   0  590728  71048  10796 S   2.7  1.8   0:41.92 
ibus-ui-gt+ 
   3918 simon 20   0  769636  73648  11544 S   2.7  1.8   0:42.82 
unity-pane+ 
   4402 simon 20   0  511960  71072  12024 S   2.7  1.8   0:41.36 nm-applet 
  
   7212 simon 20   0  847244  67792  12680 S   2.7  1.7   0:37.13 
update-not+ 
   3865 simon 20   0  666200  67632   7956 S   2.3  1.7   0:37.61 
bamfdaemon  
   3911 simon 20   0  906492  68264   7816 S   2.3  1.7   0:38.02 
gnome-sess+ 
   4130 simon 20   0  776980  67892   8080 S   2.3  1.7   0:36.34 
indicator-+ 
   4146 simon 20   0  499124  66596   8156 S   2.3  1.6   0:35.04 
indicator-+ 
   4410 simon 20   0  405976  73952   9800 S   2.3  1.8   0:34.70 
smart-noti+ 
   4194 simon 20   0  391836  65148   7236 S   2.0  1.6   0:35.79 notify-osd

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.4
  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: Mon Sep 29 10:06:59 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:2127]
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 0

[Touch-packages] [Bug 1368827] Re: [FFe] [touch] indicator needs to be able to control volume per audio role

[Ricardo Salveti]

** Summary changed:

- [touch] indicator needs to be able to control volume per audio role
+ [FFe] [touch] indicator needs to be able to control volume per audio role

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

** Description changed:

+ Dear Release Team,
+ 
  From the Sound design for Touch (https://wiki.ubuntu.com/Sound#Phone),
  we need to change the default behaviour of the indicator in order to be
  able to change volume per audio roles, and not only the master volume.
  
  On touch the master volume will always be at 100%, and each media role
  will have its own volume values, so we can have a different volume level
  for multimedia, ringtone and alarms.
  
  This can be done using the streamrestore module in pulseaudio (via another 
dbus entry point that is only enabled on touch atm):
  
http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/Developer/Clients/DBus/StreamRestore/
  
  There's also a sample script on python that can be used to set/get volume per 
roles:
  https://raw.githubusercontent.com/jusa/pulseaudio-utils/master/pasr.py
  
  And the current roles supporter by touch are: multimedia, alert, phone
  and alarm.
+ 
+ This change is touch specific as it needs a combination of configs that
+ are available in ubuntu-touch-session for it to be used (different code
+ path that only gets used on touch).

** Description changed:

  Dear Release Team,
+ 
+ I would like to request a FFe for indicator-sound, in order to deliver
+ the remaining features needed for Ubuntu Touch.
  
  From the Sound design for Touch (https://wiki.ubuntu.com/Sound#Phone),
  we need to change the default behaviour of the indicator in order to be
  able to change volume per audio roles, and not only the master volume.
  
  On touch the master volume will always be at 100%, and each media role
  will have its own volume values, so we can have a different volume level
  for multimedia, ringtone and alarms.
  
  This can be done using the streamrestore module in pulseaudio (via another 
dbus entry point that is only enabled on touch atm):
  
http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/Developer/Clients/DBus/StreamRestore/
  
  There's also a sample script on python that can be used to set/get volume per 
roles:
  https://raw.githubusercontent.com/jusa/pulseaudio-utils/master/pasr.py
  
  And the current roles supporter by touch are: multimedia, alert, phone
  and alarm.
  
  This change is touch specific as it needs a combination of configs that
  are available in ubuntu-touch-session for it to be used (different code
  path that only gets used on touch).

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

Title:
  [FFe] [touch] indicator needs to be able to control volume per audio
  role

Status in “indicator-sound” package in Ubuntu:
  New

Bug description:
  Dear Release Team,

  I would like to request a FFe for indicator-sound, in order to deliver
  the remaining features needed for Ubuntu Touch.

  From the Sound design for Touch (https://wiki.ubuntu.com/Sound#Phone),
  we need to change the default behaviour of the indicator in order to
  be able to change volume per audio roles, and not only the master
  volume.

  On touch the master volume will always be at 100%, and each media role
  will have its own volume values, so we can have a different volume
  level for multimedia, ringtone and alarms.

  This can be done using the streamrestore module in pulseaudio (via another 
dbus entry point that is only enabled on touch atm):
  
http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/Developer/Clients/DBus/StreamRestore/

  There's also a sample script on python that can be used to set/get volume per 
roles:
  https://raw.githubusercontent.com/jusa/pulseaudio-utils/master/pasr.py

  And the current roles supporter by touch are: multimedia, alert, phone
  and alarm.

  This change is touch specific as it needs a combination of configs
  that are available in ubuntu-touch-session for it to be used
  (different code path that only gets used on touch).

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

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

[Touch-packages] [Bug 1347147] Re: krb5 database operations enter infinite loop

[Anders Kaseorg]

It’s currently sitting in Unapproved:

https://launchpad.net/ubuntu/trusty/+queue?queue_state=1&queue_text=krb5

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

Title:
  krb5 database operations enter infinite loop

Status in The GNU Compiler Collection:
  Fix Released
Status in Network Authentication System:
  Unknown
Status in “gcc-4.8” package in Ubuntu:
  Fix Released
Status in “gcc-4.9” package in Ubuntu:
  Fix Released
Status in “krb5” package in Ubuntu:
  Fix Released
Status in “gcc-4.8” source package in Trusty:
  Confirmed
Status in “krb5” source package in Trusty:
  In Progress

Bug description:
  [Impact]

  On krb5 KDC databases with more than a few hundred principals,
  operations can enter an infinite loop in the database library.  This
  affects both read and write operations.  If operators are fortunate,
  they will encounter this bug while testing a migration.  If they are
  not so fortunate, they will encounter this bug in a production KDC
  when the number of principals crosses the threshold where this bug
  manifests, resulting in a service outage and possible database
  corruption.  Probably the only way to restore service in that
  situation is to install a patched KDC or to downgrade to an unaffected
  version.

  Both Trusty and Utopic amd64 have been verified to have this issue.

  One concrete reported example is an invocation of kdb5_util load (as
  part of a slave KDC propagation) spinning:

  http://mailman.mit.edu/pipermail/kerberos/2014-July/020007.html

  Additional failure modes are likely

  A branch is linked including the upstream work around for this bug,
  along with two other patches to bugs already nominated for trusty
  applied to the krb5 in trusty.

  For utopic, the simplest fix is to rebuild krb5 with the compiler
  currently in utopic.  An alternative is to request that the Debian
  maintainers (both monitoring this bug for such a request) upload the
  upstream work around to Debian and sync that.  You could do an ubuntu-
  specific upload but it seems undesirable to introduce a change between
  Ubuntu and Debian when all the right parties are happy to avoid it.

  The upstream patch works around a compiler optimizer bug in the
  gcc-4.8 series, which incorrectly deduces that a strict aliasing
  violation has occurred and miscompiles part of the bundled libdb2
  library that the KDC database back end depends upon.  The
  miscompilation causes a data structure to contain an inappropriate
  cycle, which leads to an infinite loop when the structure is
  traversed.

  [Test Case]

  apt-get install krb5-kdc krb5-admin-server
  kdb5_util -W -r T create -s
  awk 'BEGIN{ for (i = 0; i < 1024; i++) { printf("ank -randkey a%06d\n", i) } 
}' /dev/null | kadmin.local -r T

  (Enter any password for the master key when requested.)

  On platforms with this issue, kadmin.local spins consuming 100% CPU
  after a few hundred principals have been created.  (This is "a000762"
  on two examples.)

  To clean up,

  rm /etc/krb5kdc/principal*

  or

  krb5kdc -r T destroy

  but the latter can possibly enter the same infinite loop.

  [Regression Potential]

  Negligible.

  It is theoretically possible that our upstream workaround, which
  involves using TAILQ macros instead of CIRCLEQ macros in the bundled
  libdb2 that backs the KDC database, will have some as-yet undiscovered
  bugs or compiler interactions with consequences worse than this
  current issue.  I think this is rather unlikely.

  The patched libdb2 passes both the extensive libdb2 test suite and the
  rest of the krb5 test suite.  Prior to patching, compiling krb5 with
  an affected gcc would cause the krb5 test suite to stall when it
  reached the libdb2 test suite.  (The test suite stall is how we became
  aware of the gcc optimizer bug.)

  The BSD TAILQ macros are generally considered to be safer than the
  CIRCLEQ macros, and the various open-source BSD derivatives have made
  the corresponding change to their libdb sources years ago, with no
  reported ill effects that I can see.

  Original report from Ben Kaduk:

  ==

  In some conditions, propagating a kerberos database to a slave KDC server can 
stall.
  This is due to a misoptimization by gcc 4.8 of the CIRCLEQ famliy of macros, 
apparently due to overzealous strict aliasing deductions.

  One case of this stall is reported at
  http://mailman.mit.edu/pipermail/kerberos/2014-July/020007.html (and
  the rest of the thread), and there is an entry in the upstream
  bugtracker at http://krbdev.mit.edu/rt/Ticket/Display.html?id=7860 .

  gcc 4.9 (as used in Debian unstable at present) is not believed to
  induce this problem.  Upstream has patched their code to use the TAILQ
  family of macros instead, as a workaround, but that workaround has not
  yet appeared in an upstream release:
  https://github.com/krb5/krb5/co

[Touch-packages] [Bug 1354571] Re: apport-retrace ignores warnings from gdb

[Chris J Arges]

Hello Brian, or anyone else affected,

Accepted apport into trusty-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/apport/2.14.1-0ubuntu3.5 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

** Tags added: verification-needed

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

Title:
  apport-retrace ignores warnings from gdb

Status in “apport” package in Ubuntu:
  Fix Released
Status in “apport” source package in Trusty:
  Fix Committed

Bug description:
  [Impact]
  Crash reports with damaged core dumps are being sent to the Ubuntu Error 
Tracker, where they are added to the retracing queue and then an attempt is 
made to retrace them. These retraces fail because the core dump is damaged so 
resources are wasted.  We should stop sending these to the Error Tracker.

  [Test Case]
  apport's test_report.py has gained a new test called 
test_add_gdb_info_damaged which tests that a crash report with a damaged core 
dump raises an IOError.
  Running this test with the version of the package in trusty-updates will fail 
with an AssertionError.
  Running the test with the version of the package from trusty-proposed will 
pass.

  
  I was trying to investigate a failed retrace on armhf and received the 
following when running apport-retrace with -g.

  Calling gdb command: gdb-multiarch --ex 'set architecture arm' --ex 'set 
gnutarget elf32-littlearm' --ex 'set debug-file-directory /tmp/apport
  -utopic/usr/lib/debug' --ex 'set solib-absolute-prefix /tmp/apport-utopic' 
--ex 'file "/tmp/apport-utopic//usr/lib/ubuntu-push-client/signing-
  helper"' --ex 'core-file /tmp/apport_core_36z3Va'
  GNU gdb (Ubuntu 7.7-0ubuntu3.2) 7.7
  Copyright (C) 2014 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .
  For help, type "help".
  Type "apropos word" to search for commands related to "word".
  The target architecture is assumed to be arm
  Reading symbols from 
/tmp/apport-utopic//usr/lib/ubuntu-push-client/signing-helper...Reading symbols 
from /tmp/apport-utopic/usr/lib/debug/.bu
  ild-id/0d/28e75c6b9149132f8940077618a904989a75ed.debug...done.
  done.
  BFD: Warning: /tmp/apport_core_36z3Va is truncated: expected core file size 
>= 19316736, found: 9502720.
  [New LWP 15327]
  [New LWP 15530]
  [New LWP 15321]
  Cannot access memory at address 0xb6fa7948
  Cannot access memory at address 0xb6fa7944

  When running apport-retrace with -o, a new crash file is created with
  a broken Stacktrace.  This makes sense given that the core file is
  corrupt.

  However, I think apport-retrace should do something different here, as
  you have no idea why the retraced report is bad. Maybe it should write
  a RetraceFailure key to the report, not write the report at all, or
  just exit with an error regarding the core file size difference.

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

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

[Touch-packages] [Bug 1376357] Re: lightdm writing the same DEBUG message to /var/log/lightdm/lightdm.log

[Robert Ancell]

Hmm, not finding anything that sets this. Other candidates are
XKeyboardLayouts, BackgroundFile and IconFile which also may emit
Changed even if they are not.

I checked the properties of this user on a phone and confirm they are
unchanged before and after this signal occurs.

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

Title:
  lightdm writing the same DEBUG message to /var/log/lightdm/lightdm.log

Status in “lightdm” package in Ubuntu:
  Incomplete

Bug description:
  I was trying to figure out where excessive file system writes were
  coming from on the ubuntu phone (to try to reduce flash writes and hence 
reduce power
  consumption) and I spotted that /var/log/lightdm/lightdm.log is getting the 
same debug message written to every every 300 seconds:

  tail -f /var/log/lightdm/lightdm.log
  [+5109.66s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+5409.67s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+5709.66s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+6009.66s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+6309.64s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+6609.65s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+6909.67s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+7209.66s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+7509.66s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+7809.57s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+8109.65s] DEBUG: User /org/freedesktop/Accounts/User32011 changed

  while this isn't much of a message, it still is causing file system
  writes every 5 minutes for the same debug message. Is this necessary?
  The fact that it is the same message about the same account and that
  it occurs every 300 seconds make me wonder if we can cull this
  particular piece of repeated logging.

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

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

[Touch-packages] [Bug 1376430] Re: some scopes need access to android libraries

[Launchpad Bug Tracker]

This bug was fixed in the package apparmor-easyprof-ubuntu - 1.2.32

---
apparmor-easyprof-ubuntu (1.2.32) utopic; urgency=medium

  * ubuntu/1.2/ubuntu-scope-network, pending/ubuntu-scope-local-content:
allow access to android libraries (LP: #1376430)
  * ubuntu/ubuntu-{sdk,webapp}: allow read access for thumbnailer icons
(LP: #1376436)
 -- Jamie StrandbogeWed, 01 Oct 2014 15:13:35 -0500

** Changed in: apparmor-easyprof-ubuntu (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  some scopes need access to android libraries

Status in “apparmor-easyprof-ubuntu” package in Ubuntu:
  Fix Released
Status in “apparmor-easyprof-ubuntu” package in Ubuntu RTM:
  In Progress

Bug description:
  Oct  1 18:13:04 ubuntu-phablet kernel: [  130.672099]
  (1)[6551:scoperunner]type=1400 audit(1412187184.960:123):
  apparmor="DENIED" operation="open" profile=""
  name="/android/system/lib/libGLESv2.so" pid=6551 comm="scoperunner"
  requested_mask="r" denied_mask="r" fsuid=32011 ouid=0

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

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

[Touch-packages] [Bug 1376361] Re: Need to open up path for cached QML bytecode

[Launchpad Bug Tracker]

This bug was fixed in the package apparmor-easyprof-ubuntu - 1.2.32

---
apparmor-easyprof-ubuntu (1.2.32) utopic; urgency=medium

  * ubuntu/1.2/ubuntu-scope-network, pending/ubuntu-scope-local-content:
allow access to android libraries (LP: #1376430)
  * ubuntu/ubuntu-{sdk,webapp}: allow read access for thumbnailer icons
(LP: #1376436)
 -- Jamie StrandbogeWed, 01 Oct 2014 15:13:35 -0500

** Changed in: apparmor-easyprof-ubuntu (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Need to open up path for cached QML bytecode

Status in “apparmor-easyprof-ubuntu” package in Ubuntu:
  Fix Released
Status in “apparmor-easyprof-ubuntu” package in Ubuntu RTM:
  In Progress

Bug description:
  The upcoming introduction of cacheable QML compilation units require
  an application-specific path to store the binaries.

  The proposed  and accepted path is

  $HOME/.cache/QML/Apps/$APP_ID

  where $APP_ID = @{APP_PKGNAME}_@{APP_APPNAME}_@{APP_VERSION} for click apps
  and simple desktop file name for legacy apps.

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

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

[Touch-packages] [Bug 1376436] Re: thumbnailer icon denial

[Launchpad Bug Tracker]

This bug was fixed in the package apparmor-easyprof-ubuntu - 1.2.32

---
apparmor-easyprof-ubuntu (1.2.32) utopic; urgency=medium

  * ubuntu/1.2/ubuntu-scope-network, pending/ubuntu-scope-local-content:
allow access to android libraries (LP: #1376430)
  * ubuntu/ubuntu-{sdk,webapp}: allow read access for thumbnailer icons
(LP: #1376436)
 -- Jamie StrandbogeWed, 01 Oct 2014 15:13:35 -0500

** Changed in: apparmor-easyprof-ubuntu (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  thumbnailer icon denial

Status in “apparmor-easyprof-ubuntu” package in Ubuntu:
  Fix Released
Status in “apparmor-easyprof-ubuntu” package in Ubuntu RTM:
  In Progress

Bug description:
  apparmor="DENIED" operation="open" 
   profile="com.ubuntu.camera_camera_3.0.0.387" 
   name="/usr/share/thumbnailer/icons/video_missing.png" 
   pid=7499 comm="QQuickPixmapRea" requested_mask="r" 
   denied_mask="r" fsuid=32011 ouid=0

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

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

[Touch-packages] [Bug 1063350] Re: curl corrupts floating point context

[Barry Warsaw]

I've verified this patch is no longer necessary with pycurl 7.19.5,
which I will FFe shortly into Utopic.  It could be building it against
gnutls28, or changes in pycurl itself.

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

Title:
  curl corrupts floating point context

Status in “pycurl” package in Ubuntu:
  Triaged

Bug description:
  # add-apt-repository ppa:ubuntu-wine/ppa
  You are about to add the following PPA to your system:
   Welcome to the Wine Team PPA.  Here you can get the latest available Wine 
betas for every supported version of Ubuntu.  This PPA is managed by Scott 
Ritchie and Maarten Lankhorst.
   More info: https://launchpad.net/~ubuntu-wine/+archive/ppa
  Press [ENTER] to continue or ctrl-c to cancel adding it

  Exception in thread Thread-1:
  Traceback (most recent call last):
File "/usr/lib/python2.7/threading.py", line 551, in __bootstrap_inner
  self.run()
File "/usr/lib/python2.7/dist-packages/softwareproperties/ppa.py", line 99, 
in run
  self.add_ppa_signing_key(self.ppa_path)
File "/usr/lib/python2.7/dist-packages/softwareproperties/ppa.py", line 
132, in add_ppa_signing_key
  tmp_keyring_dir = tempfile.mkdtemp()
File "/usr/lib/python2.7/tempfile.py", line 322, in mkdtemp
  name = names.next()
File "/usr/lib/python2.7/tempfile.py", line 141, in next
  letters = [choose(c) for dummy in "123456"]
File "/usr/lib/python2.7/random.py", line 274, in choice
  return seq[int(self.random() * len(seq))]  # raises IndexError if seq is 
empty
  ValueError: cannot convert float NaN to integer

  I have tried a purge and install but it doesn't fix this.

  No idea how to work around this.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: python-software-properties 0.82.7.3
  ProcVersionSignature: Ubuntu 3.2.0-31.50-generic-pae 3.2.28
  Uname: Linux 3.2.0-31-generic-pae i686
  ApportVersion: 2.0.1-0ubuntu13
  Architecture: i386
  Date: Sun Oct  7 18:43:46 2012
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to precise on 2012-10-03 (4 days ago)

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

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

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

[jox]

@wlraider70

This seems not to be directly related. Same as #16 by @Michael
Heuberger.

The issue of this thread is about this message:

  invoke-rc.d: unknown initscript, /etc/init.d/systemd-logind.

It can not find the initscript and thus is not able to execute it.

Whereas your message...

  invoke-rc.d: initscript systemd-logind, action "start" failed.

...indicates that the initscript was in fact executed, but did fail
(even though it's strange that "Job is already running" produces a fail.
On my system (14.04) it does not produce an error when I run "invoke-
rc.d systemd-logind start" as root, while it is already running).

Maybe this thread helps (specifically #4):

"invoke-rc.d: initscript systemd-logind, action "start" failed."
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1320563

Btw. I was also surprised at not being able to edit comments. I guess it's 
because the posts end up in a mailing list.
e.g. http://www.mail-archive.com/ubuntu-bugs@lists.ubuntu.com/msg4504011.html

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

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

Status in “systemd” package in Ubuntu:
  Fix Released
Status in “systemd” source package in Trusty:
  Triaged
Status in “systemd” source package in Utopic:
  Fix Released

Bug description:
  Hi,

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

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

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

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

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

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

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

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

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

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

  
  perhaps related to older launchpad bug #1305395 ?

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

  
  thanks,
  Hamish

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

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

[Touch-packages] [Bug 1373085] Re: Parser error when using regex profile names in IPC rules

[Launchpad Bug Tracker]

** Branch linked: lp:apparmor

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

Title:
  Parser error when using regex profile names in IPC rules

Status in “apparmor” package in Ubuntu:
  In Progress

Bug description:
  I tried to add this rule to the firefox profile:
  unix (send, receive) type=stream 
peer=(label=/usr/lib/firefox/firefox\{,\*\[^s\]\[^h\]\}//plugincontainer),

  apparmor_parser fails with:
  syntax error, unexpected TOK_CONDID, expecting TOK_EQUALS or TOK_IN

  When I add quotes around the label the parser fails with:
  Found unexpected character: '"'

  I found this minimal test case:
  unix peer=(label=\{,\}),
  and
  unix peer=(label="\{,\}"),

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

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

[Touch-packages] [Bug 1376495] [NEW] autopilot3 run camera_app.tests.test_zoom.TestCameraZoom.test_slider_zoom_out crashes camera-app

[Chris Gagnon]

Public bug reported:

Summary:
autopilot3 run camera_app.tests.test_zoom.TestCameraZoom.test_slider_zoom_out 
crashes camera-app

steps:
1. phablet-click-test-setup -s $ANDROID_SERIAL
2. phablet-config -s $ANDROID_SERIAL autopilot --dbus-probe enable
3. adb -s $ANDROID_SERIAL shell
4. cd autopilot 
5. autopilot3 run 
camera_app.tests.test_zoom.TestCameraZoom.test_slider_zoom_out -
6. ls /var/crash

expected results:
test passes without crashing camera app

actual results:
test crashes camera app

base: system-image.ubuntu.com
http_port: 80
https_port: 443
channel: ubuntu-touch/devel-proposed
device: mako
build_number: 263
channel_target: ubuntu-touch/utopic-proposed
version_detail: ubuntu=20140930,device=20140929.1,custom=mako-0.6,version=263

com.ubuntu.camera   3.0.0.387

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

Title:
  autopilot3 run
  camera_app.tests.test_zoom.TestCameraZoom.test_slider_zoom_out crashes
  camera-app

Status in “camera-app” package in Ubuntu:
  New

Bug description:
  Summary:
  autopilot3 run camera_app.tests.test_zoom.TestCameraZoom.test_slider_zoom_out 
crashes camera-app

  steps:
  1. phablet-click-test-setup -s $ANDROID_SERIAL
  2. phablet-config -s $ANDROID_SERIAL autopilot --dbus-probe enable
  3. adb -s $ANDROID_SERIAL shell
  4. cd autopilot 
  5. autopilot3 run 
camera_app.tests.test_zoom.TestCameraZoom.test_slider_zoom_out -
  6. ls /var/crash

  expected results:
  test passes without crashing camera app

  actual results:
  test crashes camera app

  base: system-image.ubuntu.com
  http_port: 80
  https_port: 443
  channel: ubuntu-touch/devel-proposed
  device: mako
  build_number: 263
  channel_target: ubuntu-touch/utopic-proposed
  version_detail: ubuntu=20140930,device=20140929.1,custom=mako-0.6,version=263

  com.ubuntu.camera   3.0.0.387

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

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

[Touch-packages] [Bug 1368827] Re: [FFe] [touch] indicator needs to be able to control volume per audio role

[Steve Langasek]

 rsalveti: so the idea here is that the 
sink-input-by-media-role:$foo are only present if we're on touch?
 slangasek: they can be part of the desktop, but the dbus module that 
export that interface to the indicator is only available on touch
 the stream can have basically any role, as the app is responsible 
for setting that up, we just have a small set of supported ones on touch
 and this additional work was to enable this extra dbus interface so 
it can be used to change volume per roles
 so if the dbus interface and the needed roles are not available in 
the stream-restore internal database, it'll act like today (only controlling 
the main sink)
 if the dbus interface is available, and the required set of roles 
are available in stream-restore, then the volume will reflect on the current 
active role (or alert by default)
 ok. what package provides this new dbus interface?
 slangasek: pulse itself, but that's disabled by default, and the 
config enabling that is part of ubuntu-touch-session


FFe approved.

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

Title:
  [FFe] [touch] indicator needs to be able to control volume per audio
  role

Status in “indicator-sound” package in Ubuntu:
  New

Bug description:
  Dear Release Team,

  I would like to request a FFe for indicator-sound, in order to deliver
  the remaining features needed for Ubuntu Touch.

  From the Sound design for Touch (https://wiki.ubuntu.com/Sound#Phone),
  we need to change the default behaviour of the indicator in order to
  be able to change volume per audio roles, and not only the master
  volume.

  On touch the master volume will always be at 100%, and each media role
  will have its own volume values, so we can have a different volume
  level for multimedia, ringtone and alarms.

  This can be done using the streamrestore module in pulseaudio (via another 
dbus entry point that is only enabled on touch atm):
  
http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/Developer/Clients/DBus/StreamRestore/

  There's also a sample script on python that can be used to set/get volume per 
roles:
  https://raw.githubusercontent.com/jusa/pulseaudio-utils/master/pasr.py

  And the current roles supporter by touch are: multimedia, alert, phone
  and alarm.

  This change is touch specific as it needs a combination of configs
  that are available in ubuntu-touch-session for it to be used
  (different code path that only gets used on touch).

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

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

[Touch-packages] [Bug 1376500] [NEW] [regression] thumbnails and image previews displayed wrong

[Bill Filler]

Public bug reported:

build 76 rtm-proposed on krillin

Take a picture with camera-app
swipe to the right to display it
it looks squashed and like it's being displayed at the wrong aspect ration
open the gallery-app and view the photo and it looks equally bad
share the photo to messaging-app, and the preview of the photo is black
copy the photo to your desktop and open there and the photo looks fine

these are all new regressions, not sure what layer it's in bug guessing
a low layer as gallery, camera and messaging-app have not changed in
this regard

** Affects: camera-app
 Importance: Critical
 Assignee: Florian Boucault (fboucault)
 Status: New

** Affects: gallery-app
 Importance: Undecided
 Status: New

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

** Affects: thumbnailer (Ubuntu)
 Importance: Critical
 Assignee: Jussi Pakkanen (jpakkane)
 Status: New


** Tags: rtm14

** Also affects: camera-app
   Importance: Undecided
   Status: New

** Also affects: gallery-app
   Importance: Undecided
   Status: New

** Changed in: thumbnailer (Ubuntu)
   Importance: Undecided => Critical

** Changed in: camera-app
   Importance: Undecided => Critical

** Changed in: camera-app
 Assignee: (unassigned) => Florian Boucault (fboucault)

** Changed in: thumbnailer (Ubuntu)
 Assignee: (unassigned) => Jussi Pakkanen (jpakkane)

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

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

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

** Tags added: rtm14

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

Title:
  [regression] thumbnails and image previews displayed wrong

Status in Camera App:
  New
Status in Gallery App:
  New
Status in Ubuntu UI Toolkit:
  New
Status in “thumbnailer” package in Ubuntu:
  New

Bug description:
  build 76 rtm-proposed on krillin

  Take a picture with camera-app
  swipe to the right to display it
  it looks squashed and like it's being displayed at the wrong aspect ration
  open the gallery-app and view the photo and it looks equally bad
  share the photo to messaging-app, and the preview of the photo is black
  copy the photo to your desktop and open there and the photo looks fine

  these are all new regressions, not sure what layer it's in bug
  guessing a low layer as gallery, camera and messaging-app have not
  changed in this regard

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

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

[Touch-packages] [Bug 1368827] Re: [FFe] [touch] indicator needs to be able to control volume per audio role

[Ricardo Salveti]

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

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

Title:
  [FFe] [touch] indicator needs to be able to control volume per audio
  role

Status in “indicator-sound” package in Ubuntu:
  In Progress

Bug description:
  Dear Release Team,

  I would like to request a FFe for indicator-sound, in order to deliver
  the remaining features needed for Ubuntu Touch.

  From the Sound design for Touch (https://wiki.ubuntu.com/Sound#Phone),
  we need to change the default behaviour of the indicator in order to
  be able to change volume per audio roles, and not only the master
  volume.

  On touch the master volume will always be at 100%, and each media role
  will have its own volume values, so we can have a different volume
  level for multimedia, ringtone and alarms.

  This can be done using the streamrestore module in pulseaudio (via another 
dbus entry point that is only enabled on touch atm):
  
http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/Developer/Clients/DBus/StreamRestore/

  There's also a sample script on python that can be used to set/get volume per 
roles:
  https://raw.githubusercontent.com/jusa/pulseaudio-utils/master/pasr.py

  And the current roles supporter by touch are: multimedia, alert, phone
  and alarm.

  This change is touch specific as it needs a combination of configs
  that are available in ubuntu-touch-session for it to be used
  (different code path that only gets used on touch).

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

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

[Touch-packages] [Bug 1354571] Re: apport-retrace ignores warnings from gdb

[Brian Murray]

This is probably also worth SRU'ing to Precise since we seem to get some
invalid core dumps from that release too.

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

Title:
  apport-retrace ignores warnings from gdb

Status in “apport” package in Ubuntu:
  Fix Released
Status in “apport” source package in Trusty:
  Fix Committed

Bug description:
  [Impact]
  Crash reports with damaged core dumps are being sent to the Ubuntu Error 
Tracker, where they are added to the retracing queue and then an attempt is 
made to retrace them. These retraces fail because the core dump is damaged so 
resources are wasted.  We should stop sending these to the Error Tracker.

  [Test Case]
  apport's test_report.py has gained a new test called 
test_add_gdb_info_damaged which tests that a crash report with a damaged core 
dump raises an IOError.
  Running this test with the version of the package in trusty-updates will fail 
with an AssertionError.
  Running the test with the version of the package from trusty-proposed will 
pass.

  
  I was trying to investigate a failed retrace on armhf and received the 
following when running apport-retrace with -g.

  Calling gdb command: gdb-multiarch --ex 'set architecture arm' --ex 'set 
gnutarget elf32-littlearm' --ex 'set debug-file-directory /tmp/apport
  -utopic/usr/lib/debug' --ex 'set solib-absolute-prefix /tmp/apport-utopic' 
--ex 'file "/tmp/apport-utopic//usr/lib/ubuntu-push-client/signing-
  helper"' --ex 'core-file /tmp/apport_core_36z3Va'
  GNU gdb (Ubuntu 7.7-0ubuntu3.2) 7.7
  Copyright (C) 2014 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .
  For help, type "help".
  Type "apropos word" to search for commands related to "word".
  The target architecture is assumed to be arm
  Reading symbols from 
/tmp/apport-utopic//usr/lib/ubuntu-push-client/signing-helper...Reading symbols 
from /tmp/apport-utopic/usr/lib/debug/.bu
  ild-id/0d/28e75c6b9149132f8940077618a904989a75ed.debug...done.
  done.
  BFD: Warning: /tmp/apport_core_36z3Va is truncated: expected core file size 
>= 19316736, found: 9502720.
  [New LWP 15327]
  [New LWP 15530]
  [New LWP 15321]
  Cannot access memory at address 0xb6fa7948
  Cannot access memory at address 0xb6fa7944

  When running apport-retrace with -o, a new crash file is created with
  a broken Stacktrace.  This makes sense given that the core file is
  corrupt.

  However, I think apport-retrace should do something different here, as
  you have no idea why the retraced report is bad. Maybe it should write
  a RetraceFailure key to the report, not write the report at all, or
  just exit with an error regarding the core file size difference.

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

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

[Touch-packages] [Bug 1376342] Re: [HP Compaq dc7900 Ultra-Slim Desktop, Analog Devices AD1884A, Black Headphone Out, Front] No sound at all

[Raymond]

headphone is not plugged


try hda jack. sense test


ports:
analog-output: Salida analógica (priority 9900, latency offset 
0 usec, available: unknown)
properties:

analog-output-speaker: Altavoces (priority 1, latency 
offset 0 usec, available: unknown)
properties:
device.icon_name = "audio-speakers"
analog-output-headphones: Auriculares analógicos (priority 
9000, latency offset 0 usec, available: no)
properties:
device.icon_name = "audio-headphones"
active port: 



control.26 {
iface CARD
name 'Line Out Jack'
value false
comment {
access read
type BOOLEAN
count 1
}
}
control.27 {
iface CARD
name 'Front Headphone Jack'
value false
comment {
access read
type BOOLEAN
count 1
}
}
control.28 {
iface CARD
name 'Speaker Phantom Jack'
value true
comment {
access read
type BOOLEAN
count 1
}
}

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

Title:
  [HP Compaq dc7900 Ultra-Slim Desktop, Analog Devices AD1884A, Black
  Headphone Out, Front] No sound at all

Status in “alsa-driver” package in Ubuntu:
  New

Bug description:
  The sound to play in Rythmbox don't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic i686
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fernapro   2145 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Oct  1 18:26:40 2014
  InstallationDate: Installed on 2013-08-15 (412 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful
  Symptom_Card: Audio Interno - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fernapro   2145 F pulseaudio
  Symptom_Jack: Black Headphone Out, Front
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [HP Compaq dc7900 Ultra-Slim Desktop, Analog Devices AD1884A, Black 
Headphone Out, Front] No sound at all
  UpgradeStatus: Upgraded to trusty on 2014-04-21 (162 days ago)
  dmi.bios.date: 03/05/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786G1 v01.16
  dmi.board.asset.tag: CZC944BY74
  dmi.board.name: 3033h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC944BY74
  dmi.chassis.type: 15
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786G1v01.16:bd03/05/2009:svnHewlett-Packard:pnHPCompaqdc7900Ultra-SlimDesktop:pvr:rvnHewlett-Packard:rn3033h:rvr:cvnHewlett-Packard:ct15:cvr:
  dmi.product.name: HP Compaq dc7900 Ultra-Slim Desktop
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1367832] Re: gdbserver gets conditionals wrong on ppc64le

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/utopic-proposed/gdb

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

Title:
  gdbserver gets conditionals wrong on ppc64le

Status in “gdb” package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  Single stepping has issues with conditionals when debugging with gdbserver, 
taking the wrong path through the code.
   
  Machine Type = Power8 LE 
   
  ---Steps to Reproduce---
   ubuntu@ubuntu:~$ cat > test.c
  #include 
  #include 

  typedef enum {
Success = 0,
Failure,
  } dev_status_t;

  dev_status_t getDeviceCount(int *countp)
  { 
*countp = 1;
return Success;
  }

  int
  main(int argc, char **argv)
  { 
int count = 0;
dev_status_t status = getDeviceCount(&count);

if (status != Success)
  { 
printf("getDeviceCount returned %d\n", (int)status);
printf("Result = FAIL\n");
exit(EXIT_FAILURE);
  }

if (count == 0)
  { 
printf("There are no devices\n");
  }
else
  { 
printf("Detected %d device(s)\n", count);
  }

exit(EXIT_SUCCESS);
  }

  ubuntu@ubuntu:~$ gcc -g test.c -o test
  ubuntu@ubuntu:~$ gdbserver : ./test
  Process ./test created; pid = 25600
  Listening on port 
  Remote debugging from host 127.0.0.1

  In another terminal, run gdb:

  ubuntu@ubuntu:~$ gdb ./test 
  GNU gdb (Ubuntu 7.8-0ubuntu1) 7.8
  Copyright (C) 2014 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .
  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from ./test...done.
  (gdb) target remote :
  Remote debugging using :
  Reading symbols from /lib64/ld64.so.2...(no debugging symbols found)...done.
  Loaded symbols for /lib64/ld64.so.2
  Can't read symbols from system-supplied DSO at 0x3fffb7fa: File truncated
  0x3fffb7fc1a60 in ?? () from /lib64/ld64.so.2
  (gdb) b main
  Breakpoint 1 at 0x16d4: file test.c, line 17.
  (gdb) cont
  Continuing.

  Breakpoint 1, main (argc=1, argv=0x3088) at test.c:17
  17  {
  (gdb) next
  18int count = 0;
  (gdb) next
  19dev_status_t status = getDeviceCount(&count);
  (gdb) next
  21if (status != Success)
  (gdb) next
  23printf("getDeviceCount returned %d\n", (int)status);
  (gdb) print status
  $1 = Success

  Notice the program took the wrong direction on if() block.
   
  ---uname output---
  Linux ubuntu 3.16.0-14-generic #20-Ubuntu SMP Sat Sep 6 23:45:12 UTC 2014 
ppc64le ppc64le ppc64le GNU/Linux
   
  Userspace tool common name: gdbserver

  The root cause of this issue was a routine that collect/supply ptrace
  registers on gdbserver, originally developed for BE only.

  The attached patch against gdb 7.8-0ubuntu1 sources fixes this problem
  on gdbserver. It was already accepted and committed upstream:

  https://sourceware.org/ml/gdb-patches/2014-09/msg00181.html

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

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

[Touch-packages] [Bug 1376357] Re: lightdm writing the same DEBUG message to /var/log/lightdm/lightdm.log

[Launchpad Bug Tracker]

** Branch linked: lp:~robert-ancell/accountsservice/lp1376357

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

Title:
  lightdm writing the same DEBUG message to /var/log/lightdm/lightdm.log

Status in “lightdm” package in Ubuntu:
  Incomplete

Bug description:
  I was trying to figure out where excessive file system writes were
  coming from on the ubuntu phone (to try to reduce flash writes and hence 
reduce power
  consumption) and I spotted that /var/log/lightdm/lightdm.log is getting the 
same debug message written to every every 300 seconds:

  tail -f /var/log/lightdm/lightdm.log
  [+5109.66s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+5409.67s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+5709.66s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+6009.66s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+6309.64s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+6609.65s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+6909.67s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+7209.66s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+7509.66s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+7809.57s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+8109.65s] DEBUG: User /org/freedesktop/Accounts/User32011 changed

  while this isn't much of a message, it still is causing file system
  writes every 5 minutes for the same debug message. Is this necessary?
  The fact that it is the same message about the same account and that
  it occurs every 300 seconds make me wonder if we can cull this
  particular piece of repeated logging.

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

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

[Touch-packages] [Bug 1365664] Re: gdb source test suites are failing in Ubuntu14.10

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/utopic-proposed/gdb

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

Title:
  gdb source test suites are failing in Ubuntu14.10

Status in “binutils” package in Ubuntu:
  New
Status in “gdb” package in Ubuntu:
  Confirmed

Bug description:
  ---Problem Description---
  gdb source test suites are failing in Ubuntu14.10
   
  Machine Type = P8 
   
  ---Steps to Reproduce---
  Install a P8 system with Power KVM and then install Ubuntu 14.10 guest.
  Then try to build and execute the gdb source test suites as below.

  root@ubuntu:~# apt-get source gdb
  root@ubuntu:~# cd gdb-7.8/
  root@ubuntu:~/gdb-7.8# dpkg-buildpackage -b 2>&1 | tee gdblog

  === gdb Summary ===

  # of expected passes25009
  # of unexpected failures287
  # of unexpected successes   2
  # of expected failures  66
  # of unknown successes  1
  # of known failures 59
  # of unresolved testcases   3
  # of untested testcases 19
  # of unsupported tests  100

   
  ---uname output---
  Linux ubuntu 3.16.0-11-generic #16-Ubuntu SMP Mon Aug 25 20:02:00 UTC 2014 
ppc64le ppc64le ppc64le GNU/Linux
   
  I've retested gdb from Ubuntu 14.04 (gdb-7.7-0ubuntu3.1) in the Ubuntu 14.10 
VM provided by Pavaman and the number of failures curiously increased to 250 
(in comparison to less than 140 on 14.04), which leads me to believe that there 
is something in the environment of Ubuntu 14.10 compromising gdb functionality 
in several testcases.

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

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