date:20150401

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding messaging-app.  This problem was most recently seen with
version 0.1+15.04.20150218~rtm-0ubuntu1, the problem page at
https://errors.ubuntu.com/problem/9bea725c27a004c7417ccb08453e598dfb6929c0
contains more details.

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


** Tags: rtm-14.09 utopic vivid

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

Title:
  /usr/bin/messaging-
  
app:11:QList:QtVersit::VersitUtils::changeCodec:QtVersit::VersitUtils::newlineList:QtVersit::LineReader::LineReader:QtVersit::QVersitReaderPrivate::read

Status in messaging-app package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding messaging-app.  This problem was most recently seen with
  version 0.1+15.04.20150218~rtm-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/9bea725c27a004c7417ccb08453e598dfb6929c0
  contains more details.

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

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

[Touch-packages] [Bug 1439528] [NEW] /usr/lib/arm-linux-gnueabihf/unity-scopes/scoperunner:11:QHostInfoLookupManager::abortLookup:QHostInfo::abortHostLookup:QAbstractSocket::disconnectFromHost:QAbstra

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding unity-scopes-api.  This problem was most recently seen with
version 0.6.10+15.04.20141212-0ubuntu1, the problem page at
https://errors.ubuntu.com/problem/5201e937d07d123ac9659e077a9a68de677ddfda
contains more details.

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


** Tags: rtm-14.09 vivid

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

Title:
  /usr/lib/arm-linux-gnueabihf/unity-
  
scopes/scoperunner:11:QHostInfoLookupManager::abortLookup:QHostInfo::abortHostLookup:QAbstractSocket::disconnectFromHost:QAbstractSocket::close:QAbstractSocket::~QAbstractSocket

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

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity-scopes-api.  This problem was most recently seen with
  version 0.6.10+15.04.20141212-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/5201e937d07d123ac9659e077a9a68de677ddfda
  contains more details.

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

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

[Touch-packages] [Bug 1439530] [NEW] /usr/lib/telepathy/telepathy-ofono:6:pa_context_send_simple_command:pa_context_get_server_info:QPulseAudioEngine::setupVoiceCall:QPulseAudioEngine::setCallMode:ena

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding telepathy-ofono.  This problem was most recently seen with
version 0.2+15.04.20150223~rtm-0ubuntu1, the problem page at
https://errors.ubuntu.com/problem/d1ec5eff89d95990375ff6fd1cb46a0dd8ff25c8
contains more details.

** Affects: telepathy-ofono (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: rtm-14.09 utopic vivid

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

Title:
  /usr/lib/telepathy/telepathy-
  
ofono:6:pa_context_send_simple_command:pa_context_get_server_info:QPulseAudioEngine::setupVoiceCall:QPulseAudioEngine::setCallMode:enable_earpiece

Status in telepathy-ofono package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding telepathy-ofono.  This problem was most recently seen with
  version 0.2+15.04.20150223~rtm-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/d1ec5eff89d95990375ff6fd1cb46a0dd8ff25c8
  contains more details.

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

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

[Touch-packages] [Bug 1439526] [NEW] /usr/bin/telephony-service-indicator:6:g_assertion_message:g_assertion_message_expr:g_variant_type_info_check:g_variant_type_info_get_type_string:g_variant_is_of_t

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding telephony-service.  This problem was most recently seen with
version 0.1+15.04.20150218~rtm-0ubuntu1, the problem page at
https://errors.ubuntu.com/problem/5abd14fb2c2d7e68b391ec7d1cf38ef1321896dc
contains more details.

** Affects: telephony-service (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: rtm-14.09

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

Title:
  /usr/bin/telephony-service-
  
indicator:6:g_assertion_message:g_assertion_message_expr:g_variant_type_info_check:g_variant_type_info_get_type_string:g_variant_is_of_type

Status in telephony-service package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding telephony-service.  This problem was most recently seen with
  version 0.1+15.04.20150218~rtm-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/5abd14fb2c2d7e68b391ec7d1cf38ef1321896dc
  contains more details.

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

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

[Touch-packages] [Bug 1439529] [NEW] /usr/lib/arm-linux-gnueabihf/indicator-sound/indicator-sound-service:6:g_assertion_message:g_assertion_message_expr:g_variant_type_info_check:g_variant_type_info_g

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding indicator-sound.  This problem was most recently seen with
version 12.10.2+15.04.20150106~rtm-0ubuntu1, the problem page at
https://errors.ubuntu.com/problem/0b740cea298dea3bb30a5adbd0ac98d50cea9672
contains more details.

** Affects: indicator-sound (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: rtm-14.09

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

Title:
  /usr/lib/arm-linux-gnueabihf/indicator-sound/indicator-sound-
  
service:6:g_assertion_message:g_assertion_message_expr:g_variant_type_info_check:g_variant_type_info_get_type_string:g_variant_get_type

Status in indicator-sound package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding indicator-sound.  This problem was most recently seen with
  version 12.10.2+15.04.20150106~rtm-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/0b740cea298dea3bb30a5adbd0ac98d50cea9672
  contains more details.

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

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

[Touch-packages] [Bug 1439515] Re: NetworkManager crashed with SIGSEGV in g_closure_invoke()

2015-04-01 Thread Apport retracing service

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  NetworkManager crashed with SIGSEGV in g_closure_invoke()

Status in network-manager package in Ubuntu:
  New

Bug description:
  Crash after fresh boot to apply latest Vivid updates.

  'sudo service NetworkManager restart' got things reconnected.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu13
  ProcVersionSignature: Ubuntu 3.19.0-11.11-generic 3.19.3
  Uname: Linux 3.19.0-11-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CRDA:
   country SG: DFS-UNSET
(2402 - 2482 @ 40), (N/A, 20), (N/A)
(5170 - 5250 @ 40), (N/A, 20), (N/A)
(5250 - 5330 @ 40), (N/A, 20), (0 ms), DFS
(5735 - 5835 @ 40), (N/A, 20), (N/A)
  CrashCounter: 1
  Date: Thu Apr  2 13:02:30 2015
  ExecutablePath: /usr/sbin/NetworkManager
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-03-13 (19 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcCmdline: /usr/sbin/NetworkManager --no-daemon
  SegvAnalysis:
   Segfault happened at: 0x487202:  mov(%rbx),%rdi
   PC (0x00487202) ok
   source "(%rbx)" (0x0002) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: network-manager
  StacktraceTop:
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: NetworkManager crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: Upgraded to vivid on 2015-03-16 (16 days ago)
  UserGroups:
   
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1394204] Re: dbus daemon spinning with NM AP properties change event

** No longer affects: location-service

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

Title:
  dbus daemon spinning with NM AP properties change event

Status in the base for Ubuntu mobile products:
  Fix Released
Status in network-manager package in Ubuntu:
  Invalid
Status in location-service package in Ubuntu RTM:
  Fix Released
Status in network-manager package in Ubuntu RTM:
  Invalid

Bug description:
  I am consistently seeing this in the Bluefin office this week
  Mako running 133

  Phone gets warm in pocket, wake up the phone and attach
  top shows dbus-daemon at 100%+ cpu and network-manager next at 10-20%
  It never quiets own, at least not for over 5 mins

  3g data is turned off
  Cellular is roaming to local carrier fwiw
  Seems to happen whenever I leave the AP coverage, whether I return or not

  Reproducing the issue: The problem is easily reproducible when forcing NM to 
roam between multiple access points and never quite finishing the association 
to one AP. At home, I reproduce by
  roaming between different floors, where each floor has got its own WiFi. Any 
sufficiently complex office WiFi setup should trigger it, too.

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

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

[Touch-packages] [Bug 1216483] Re: No implementation of ua_location_service_create_controller()

** Changed in: platform-api
   Status: Fix Committed => Fix Released

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

Title:
  No implementation of ua_location_service_create_controller()

Status in Platform API:
  Fix Released
Status in platform-api package in Ubuntu:
  Fix Released

Bug description:
  ua_location_service_create_controller() is prototyped in
  include/ubuntu/application/location/service.h, but there's no
  implementation of it in the platform-api repo.

  This makes it difficult to use the UALocationServiceController. :-)

To manage notifications about this bug go to:
https://bugs.launchpad.net/platform-api/+bug/1216483/+subscriptions

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

[Touch-packages] [Bug 1398614] Re: mediascanner-service-2.0 using large amounts of CPU

Attached .crash file.

** Attachment added: "_usr_bin_mediascanner-service-2.0.32011.crash"
   
https://bugs.launchpad.net/ubuntu/+source/mediascanner2/+bug/1398614/+attachment/4363832/+files/_usr_bin_mediascanner-service-2.0.32011.crash

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

Title:
  mediascanner-service-2.0 using large amounts of CPU

Status in mediascanner2 package in Ubuntu:
  Confirmed

Bug description:
  Each time I plug my external USB hard disk the mediascanner-service process 
is activ and is using large amount of CPU for long minutes without interruption.
  I have the same problem in utopic and vivid

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: mediascanner2.0 0.105+15.04.20141030.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Dec  3 00:29:43 2014
  InstallationDate: Installed on 2011-05-26 (1286 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  SourcePackage: mediascanner2
  UpgradeStatus: Upgraded to vivid on 2013-11-26 (371 days ago)

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

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

[Touch-packages] [Bug 1290847] Re: pyvenv fails due to mising ensurepip module

2015-04-01 Thread Rob Speer

> This should work after you apt-get install python3-venv
> (python3.4-venv).

venv is a module in the Python 3 standard library. I don't understand
why it would need a separate package on Ubuntu.

Someone who's installing additional packages could just as well install
the better-understood python3-virtualenv. But the idea of venv was that
it'd be built into Python, so that someone could finally write example
code about setting up a Python environment without the "...and here's
what you need to do differently on Ubuntu" section.

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

Title:
  pyvenv fails due to mising ensurepip module

Status in python3-defaults package in Ubuntu:
  Fix Released
Status in python3.4 package in Ubuntu:
  Fix Released
Status in python3.4 package in Debian:
  Fix Released

Bug description:
  Hello,

  I noticed the following

  # fails
  python3.4 -m venv --clear python-venv
  Error: Command '['.../external/python-venv/bin/python3.4', '-Im', 
'ensurepip', '--upgrade', '--default-pip']' returned non-zero exit status 1

  # works, but no pip
  python3.4 -m venv --clear --without-pip python-venv

  Thank you

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

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

[Touch-packages] [Bug 1361642] Re: DBus.Properties.Get/Set having a hardcoded default timeout of 1000ms

** Changed in: dbus-cpp
   Status: Confirmed => Fix Released

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

Title:
  DBus.Properties.Get/Set having a hardcoded default timeout of 1000ms

Status in DBus C++:
  Fix Released
Status in dbus-cpp package in Ubuntu:
  Fix Released
Status in dbus-cpp package in Ubuntu RTM:
  Fix Released

Bug description:
  This causes issues such as found here:

  https://code.launchpad.net/~jpakkane/indicator-
  network/grace/+merge/232194

To manage notifications about this bug go to:
https://bugs.launchpad.net/dbus-cpp/+bug/1361642/+subscriptions

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

[Touch-packages] [Bug 1387734] Re: Location service uses the cached authorization, even if the user denied location access to an app

** Changed in: trust-store
   Status: In Progress => Fix Released

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

Title:
  Location service uses the cached authorization, even if the user
  denied location access to an app

Status in the base for Ubuntu mobile products:
  Fix Released
Status in trust-store:
  Fix Released
Status in location-service package in Ubuntu:
  Invalid
Status in trust-store package in Ubuntu:
  Fix Released
Status in location-service source package in Utopic:
  Invalid
Status in trust-store source package in Utopic:
  In Progress
Status in location-service source package in Vivid:
  Invalid
Status in trust-store source package in Vivid:
  Fix Released
Status in trust-store package in Ubuntu RTM:
  Fix Released

Bug description:
  The bug occurs after removing location access authorization to an
  application. The location is still available to the application,
  despite the user having revoked access from within USS > Privacy >
  Location.

  To reproduce:

  1. Open a map application, like Here map
  2. Allow access to location
  3. Switch to System Settings > Privacy > Location
  4. Disable location access for Maps
  5. Kill Here map, and restart it

  What should happen: you should not have access anymore (and should not see a 
prompt)
  What happens instead: the app still has access to your location, as shown in 
the logs:

  I1030 16:15:38.167752  3100 cached_agent_glog_reporter.cpp:32]
  CachedAgent::authenticate_request_with_parameters: Application pid:
  27975 Application uid: 32011 Application id:  com.nokia.heremaps_here
  Cached request:   Request(from: com.nokia.heremaps_here, feature: 0,
  when: 1414682114882519283, answer: granted)

  I confirmed that the trust store had recorded the authorization change
  as in:

  phablet@ubuntu-phablet:~$ sqlite3 
~/.local/share/UbuntuLocationService/trust.db "select * from requests"
  1|unconfined|0|1414098093331252474|1
  2|com.nokia.heremaps_here|0|1414682114882519283|1
  3|com.nokia.heremaps_here|0|1414682131206341515|0

  From a user's perspective: Despite having explicitly rejected trust to
  an application, the app would still be able to access services.

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

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

[Touch-packages] [Bug 1438036] Re: Unable to acknowledge alarm

Attached .crash file.

** Attachment added: "_usr_bin_unity8.32011.crash"
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1438036/+attachment/4363831/+files/_usr_bin_unity8.32011.crash

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

Title:
  Unable to acknowledge alarm

Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Happened this morning with Bq Aquarius (software version 20). The
  alarm went off, but it was impossible to acknowledge it as the view
  didn't respond to anything. I had to reboot the device.

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

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

2015-04-01 Thread Recep GUCLUER

Hi, I am using 14.04 and having this issue as described in bug
description. I am using linux for desktop for nearly 15 months. These
types of errors not good for newcomers like me. Of course I will search
and will try to find a workaround , but this is a basic operation and
must be fixed. (basic as in fundemental)

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

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 1398614] Re: mediascanner-service-2.0 using large amounts of CPU

I think that in my case mediascanner-service is constantly crashing and
that's why it seem to never stop.

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

Title:
  mediascanner-service-2.0 using large amounts of CPU

Status in mediascanner2 package in Ubuntu:
  Confirmed

Bug description:
  Each time I plug my external USB hard disk the mediascanner-service process 
is activ and is using large amount of CPU for long minutes without interruption.
  I have the same problem in utopic and vivid

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: mediascanner2.0 0.105+15.04.20141030.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Dec  3 00:29:43 2014
  InstallationDate: Installed on 2011-05-26 (1286 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  SourcePackage: mediascanner2
  UpgradeStatus: Upgraded to vivid on 2013-11-26 (371 days ago)

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

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

[Touch-packages] [Bug 1434379] Re: GPS always active when a scope that uses location is in the background

2015-04-01 Thread Ricardo Salveti

Any progress on this one?

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

Title:
  GPS always active when a scope that uses location is in the background

Status in the base for Ubuntu mobile products:
  In Progress
Status in unity-scopes-shell package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  current build number: 256
  device name: krillin
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2015-03-13 11:19:04
  version version: 256
  version ubuntu: 20150312
  version device: 20150310-3201c0a
  version custom: 20150216-561-29-186

  (same for arale/vivid as well)

  If you happen to have a scope that uses location data in background,
  your GPS will always be active, doesn't matter what is in the
  foreground.

  This is a an issue with krillin (standard channel) as the main scope
  (Today's) can easily on background when you're using other apps.

  If you move to the apps scopes, then GPS will automatically be
  disabled, and this won't happen (same for any other scope that doesn't
  use location data).

  This is only when the user is actively using the phone, as the GPS
  gets automatically disabled once the screen turns off. And there is no
  timeout at all, it stays there until you move to another scope or turn
  off the screen.

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

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

[Touch-packages] [Bug 1420395] Re: upower consuming over 17% cpu

2015-04-01 Thread Ricardo Salveti

After profiling upower, this is actually not an issue in there, as the
only thing it is doing is getting the battery change event from the
kernel, updating the internal struct and sending another dbus message so
the clients could see the changes.

The main issue here is that the kernel is sending a big amount of
battery events (all valid, and different changes), which results in
udev, upower and dbus consuming a bit of your cpu.

Verified this bug against both krillin and arale and that is not the
case there, as I already did the profiling and reduced the amount of
battery events.

As this bug is just specific to mako, and would require a kernel change
to reduce the amount of events, we can lower the priority and fix in
vivid only.

** Summary changed:

- upower consuming over 17% cpu 
+ [mako] upower consuming over 17% cpu when in idle

** Description changed:

  From the meta battery bug # 1372413
  mako running 191
  
  As device was not suspending and battery level running down, upower is 
reported at 17%+ cpu by the cpustat tool
-  mpdecision and systemd-udevd also change their behavior.
+  mpdecision and systemd-udevd also change their behavior.
+ 
+ The upower cpu consumption is just a side effect of the amount of
+ battery related events the kernel send, and specific to mako.

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

Title:
  [mako] upower consuming over 17% cpu when in idle

Status in the base for Ubuntu mobile products:
  Confirmed
Status in upower package in Ubuntu:
  Confirmed

Bug description:
  From the meta battery bug # 1372413
  mako running 191

  As device was not suspending and battery level running down, upower is 
reported at 17%+ cpu by the cpustat tool
   mpdecision and systemd-udevd also change their behavior.

  The upower cpu consumption is just a side effect of the amount of
  battery related events the kernel send, and specific to mako.

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

-- 
Mailing list: https://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 1437486] Re: sms notification baloon dont work to send sms directly

2015-04-01 Thread Buzea Bogdan

2015-04-02 4:46 GMT+03:00 Tiago Salem Herrmann :

> The output might contain private data (like your phone number), so feel
> free to change it before posting.
>

bogdan@bogdan-Lenovo-B580:~$ adb shell mc-tool dump
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
 Account: ofono/ofono/account1
Display Name: SIM 2
  Normalized: 
 Enabled: enabled
Icon: im-ofono
Connects: automatically
Nickname: 
 Service: ofono

Presences:
   Automatic: available (2) ""
 Current: registered (2) "Digi.Mobil"
   Requested: available (2) ""
Changing: no

  (string) modem-objpath = /ril_1



 Account: ofono/ofono/account0
Display Name: SIM 1
  Normalized: 
 Enabled: enabled
Icon: im-ofono
Connects: automatically
Nickname: 
 Service: ofono

Presences:
   Automatic: available (2) ""
 Current: nosim (1) ""
   Requested: available (2) ""
Changing: no

  (string) modem-objpath = /ril_0


-- 
Buzea Bogdan

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

Title:
  sms notification baloon dont work to send sms directly

Status in telephony-service package in Ubuntu:
  Confirmed

Bug description:
  When the Ubuntu Touch phone (BQ) is sleeping and I receive an SMS, if
  I click the ballon, a input appears, I completed the answer to that
  SMS, and clicked SEND, but the SMS never arrived and never left from
  my phone. I repetead those steps one hour later, the same behaviour.

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

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

[Touch-packages] [Bug 1414887] Re: dns query from localnetwork ignored

[Expired for dnsmasq (Ubuntu) because there has been no activity for 60
days.]

** Changed in: dnsmasq (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  dns query from localnetwork ignored

Status in dnsmasq package in Ubuntu:
  Expired

Bug description:
  Hi,

  I followed the following to config dnsmasq as DHCP and DNS server
  http://sfxpt.wordpress.com/2013/11/30/dnsmasq-installation-
  configuration-5/

  It works well till Ubuntu 13.10. However, with Ubuntu 14.10, the dns
  query from localnetwork will always timeout. The configurations are
  exactly the same, What could be the problem?

  From within localnetwork:

  ~~~
  $ dig google.ca

  ; <<>> DiG 9.9.5-4.3-Ubuntu <<>> google.ca
  ;; global options: +cmd
  ;; connection timed out; no servers could be reached

  dig @192.168.2.100 maroon

  ; <<>> DiG 9.9.5-4.3-Ubuntu <<>> @192.168.2.100 maroon
  ; (1 server found)
  ;; global options: +cmd
  ;; connection timed out; no servers could be reached
  ~~~

  On the DNS sever itself:

  ~~~
  $ dig google.ca @127.0.0.1
  ...
  ;; ANSWER SECTION:
  google.ca.  299 IN  A   173.194.43.111
  ...
  ;; Query time: 50 msec
  ;; SERVER: 127.0.0.1#53(127.0.0.1)

  $ dig @192.168.2.100 maroon
  ...
  ;; ANSWER SECTION:
  maroon. 0   IN  A   192.168.2.100

  ;; Query time: 1 msec
  ;; SERVER: 192.168.2.100#53(192.168.2.100)
  ...
  ~~~

  This is the debug output from dnsmasq log:

  ~~~
  Jan  1 13:26:10 maroon dnsmasq[2833]: reply google.ca is 173.194.43.119
  Jan  1 13:26:10 maroon dnsmasq[2833]: reply google.ca is 173.194.43.120
  *** DEBUG 2015-01-01 13:26:21-05:00 DEBUG ***
  Jan  1 13:27:42 maroon dnsmasq[2833]: query[A] maroon from 192.168.2.100
  Jan  1 13:27:42 maroon dnsmasq[2833]: /etc/dnsmasq.hosts maroon is
  192.168.2.100
  *** DEBUG 2015-01-01 13:28:19-05:00 DEBUG ***
  ~~~

  All other dns queries from localnetwork did not generate any log entries.
  So, because the local dns query work, I think something is blocking the 
dnsmasq
   from sending the dns query results back to localnetwork. What could it
  be?

  I didn't limit the dnsmasq listen address:

  ~~~
  $ grep listen-address /etc/dnsmasq.conf /etc/dnsmasq.d/*
  /etc/dnsmasq.conf:#listen-address=
  ~~~

  My /etc/hosts.deny and hosts.allow files are untouched either, and I can
  ping my DNS server, and ssh into its IP address as well. So I think the
  blocking is only at the DNS level since other access are just fine. It is
  not because of iptables rules either:

  $ sudo iptables-save | wc
    0   0   0

  I've installed dnsmasq on two different machines, one being freshly
  installed today, and both of them are showing exactly the  same
  symptom. Again, it only happens to Ubuntu 14.10. It was working well
  till Ubuntu 13.10 before.

  I've run out of all the possibilities.
  What could be the problem?

  Thanks

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 14.10
  Release:14.10
  Codename:   utopic

  $ apt-cache policy dnsmasq
  dnsmasq:
    Installed: 2.71-1
    Candidate: 2.71-1
    Version table:
   *** 2.71-1 0
  500 http://us.archive.ubuntu.com/ubuntu/ utopic/universe amd64 
Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1438036] Re: Unable to acknowledge alarm

Today this happened again so that the Battery low dialog(?) was active
while alarm went off. The UI didn't respond to anything and the only
thing I could do was to reboot.

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

Title:
  Unable to acknowledge alarm

Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Happened this morning with Bq Aquarius (software version 20). The
  alarm went off, but it was impossible to acknowledge it as the view
  didn't respond to anything. I had to reboot the device.

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

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

[Touch-packages] [Bug 1390625] Re: mouse cursor gets corrupted

2015-04-01 Thread Cassidy James

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

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

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

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

Title:
  mouse cursor gets corrupted

Status in elementary OS:
  Confirmed
Status in Unity:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 14.10, the mouse cursor graphic gets corrupted under certain
  occasions. It then looks flipped, sheared or shows fragments of a
  previous cursor.

  * when switching the cursor them forth and back in Gnome Tweak Tool
  * when drag&dropping a document icon

  Maybe related, the cursor does not always show the correct image scale
  on a high-dpi display (this was working right in 14.04). For example
  after login, or when hovering specific areas, or on mouse down to
  start a drag&drop, the cursor appears 1/4 the expected size.

  Attached is a photo of a corrupted cursor (whereas a screenshot with
  Gimp showed the uncorrupted cursor).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity 7.3.1+14.10.20141016-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  BootLog:
   * Setting up X socket directories...   [400G
  [394G[ OK ]
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Nov  7 22:12:52 2014
  DistUpgraded: 2014-11-04 18:35:56,188 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:3978]
  InstallationDate: Installed on 2014-02-02 (278 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140201)
  MachineType: LENOVO 20266
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed 
root=UUID=4bfb3686-b9f7-487d-81f6-eceb41097ad9 ro quiet splash 
acpi_backlight=vendor
  SourcePackage: unity
  UpgradeStatus: Upgraded to utopic on 2014-11-04 (3 days ago)
  dmi.bios.date: 10/31/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN31WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 Pro
  dmi.modalias: 
dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
  dmi.product.name: 20266
  dmi.product.version: Lenovo Yoga 2 Pro
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Fri Nov  7 14:54:59 2014
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors: [dix] ELAN Touchscreen: unable to find touch point 1
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16970
   vendor SDC
  xserver.version: 2:1.16.0-1ubuntu1

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

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

[Touch-packages] [Bug 1438360] Re: PCI/internal sound card not detected

Raymond, you are awesome. I am so embarrased that I did not think to
check the BIOS! I got it from the factory and it was disabled? Why? I
have never received a new Motherboard with the sound disabled.

On the bright side, I learned a lot, so that is cool. I don't know how
to close this.

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

Title:
PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
Incomplete

Bug description:
This is a Jetway NC 9I motherboard with Intel NC10 chipset and a
RealTek ALC662 sound chip imbedded. It has an Intel Atom D525
processor on it. I have 30 of these boards I was hoping to put Ubuntu
on for people that need them.

I have spent over three weeks on this trying to follow the forums on how to
solve this problem. I have also gone to Realtek's website and tried to use
their instructions to solve the problem. From the dignostic reports that I saw
it looks like the sound chip or codec cannot be found and that pulse is somehow
working instead?
I went here: https://help.ubuntu.com/community/SoundTroubleshootingProcedure
and got this result:
http://www.alsa-project.org/db/?f=f057abda5a101970d2980eae4341684ee857cbeb

I went to realtek's site and downloaded their Linux HD drivers here:

http://152.104.125.41/downloads/downloadsView.aspx?Langid=1&PNid=24&PFid=24&Level=4&Conn=3&DownTypeID=3&GetDown=false

I also went here: http://ubuntuforums.org/showthread.php?t=1026931
I didn't see any results from these either.

When I go into system sound it just says "Play sound through Dummy
Output"

I have tested the speakers, they work on other devices. It is plugged
into the right output...

It does not work in Ubuntu 12 or 14.04, 64 bit. It does not work in
Lubuntu either. I have not tried 32 bit.

I must be doing something out of order as I don't see anyone else
reporting this problem and Jetway says that no one has reported a
problem to them?

Thank you in advance for your help.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7
Uname: Linux 3.16.0-33-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.8
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: Unity
Date: Mon Mar 30 11:17:24 2015
InstallationDate: Installed on 2015-03-20 (10 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64
(20150218.1)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/26/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080016
dmi.chassis.type: 3
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr080016:bd02/26/2013:svn:pn:pvr:rvn:rn:rvr:cvn:ct3:cvr:

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

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

[Touch-packages] [Bug 1414706] Re: [20ALCTO1WW, Realtek ALC292, Black Mic, Left][Lenovo ThinkPad X240] external mic has no sound at all

2015-04-01 Thread Taihsiang Ho

Hi Raymond,  thanks for indicating that.
The tests I have done above is tested with a ctia headset,
except the comment no.7, which using both of OMTP and CTIA.

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

Title:
  [20ALCTO1WW, Realtek ALC292, Black Mic, Left][Lenovo ThinkPad X240]
  external mic has no sound at all

Status in HWE Next Project:
  Incomplete
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  During this test, an error dialog was thrown, reading:

  The following mixer control(s) might be incorrectly set: 
  Mic is at 0.0%

  Mic is muted
  Please try to fix that (e g by running 
  "alsamixer -D hw:PCH" in a terminal) and see if that solves the problem.
  Would you like to continue troubleshooting anyway?

  However, the System Settings... -> Sound UI shows the mic as not
  muted. When I tried running the alsamixer command, I saw mic and mic-
  boost were both showing 0; I cranked them up to 100, but it made no
  difference. I also tried re-running this command with the mic/mic-
  boost still set to 100 and it threw the same error.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  doctorow   2636 F pulseaudio
   /dev/snd/pcmC1D0c:   doctorow   2636 F...m pulseaudio
   /dev/snd/pcmC1D0p:   doctorow   2636 F...m pulseaudio
   /dev/snd/controlC0:  doctorow   2636 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jan 26 16:20:49 2015
  InstallationDate: Installed on 2014-09-10 (138 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_AlsaRecordingTestStderr: a r e c o r d :   p c m _ r e a d : 2 0 3 1 
:   r e a d   e r r o r :   I n p u t / o u t p u t   e r r o r
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  doctorow   2636 F pulseaudio
   /dev/snd/pcmC1D0c:   doctorow   2636 F...m pulseaudio
   /dev/snd/pcmC1D0p:   doctorow   2636 F...m pulseaudio
   /dev/snd/controlC0:  doctorow   2636 F pulseaudio
  Symptom_Jack: Black Mic, Left
  Symptom_Type: No sound at all
  Title: [20ALCTO1WW, Realtek ALC292, Black Mic, Left] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/24/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GIET75WW (2.25 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ALCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 PRO
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGIET75WW(2.25):bd06/24/2014:svnLENOVO:pn20ALCTO1WW:pvrThinkPadX240:rvnLENOVO:rn20ALCTO1WW:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20ALCTO1WW
  dmi.product.version: ThinkPad X240
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2015-01-22T13:36:22.741441

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1414706/+subscriptions

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

[Touch-packages] [Bug 1130809] Re: lxc scripts break when user has PYTHONPATH set

2015-04-01 Thread Stephanie

** Changed in: juju (Ubuntu)
 Assignee: Martin Packman (gz) => Stephanie (districtmellow-1904)

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

Title:
  lxc scripts break when user has PYTHONPATH set

Status in pyjuju:
  Fix Committed
Status in juju package in Ubuntu:
  Fix Released
Status in lxc package in Ubuntu:
  Invalid

Bug description:
  The various lxc scripts installed in /usr/bin are Python 3 only. If
  the user has PYTHONPATH or other similar environment variables set,
  these scripts can incorrectly inherit details from the user's Python 2
  setup when run.

  This can result in either a crash as per the initial report, or a
  traceback over syntax differences such as the following in juju:

  Traceback (most recent call last):
 File "/usr/lib/python2.7/dist-packages/juju/agents/machine.py", line 97, 
in watch_service_units
   yield self.unit_deployer.start_service_unit(unit_name)
 File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 
1069, in _inlineCallbacks
   result = result.throwExceptionIntoGenerator(g)
 File "/usr/lib/python2.7/dist-packages/twisted/python/failure.py", line 
389, in throwExceptionIntoGenerator
   return g.throw(self.type, self.value, self.tb)
 File "/usr/lib/python2.7/dist-packages/juju/unit/deploy.py", line 91, in 
start_service_unit
   running = yield deployment.is_running()
 File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 
1069, in _inlineCallbacks
   result = result.throwExceptionIntoGenerator(g)
 File "/usr/lib/python2.7/dist-packages/twisted/python/failure.py", line 
389, in throwExceptionIntoGenerator
   return g.throw(self.type, self.value, self.tb)
 File "/usr/lib/python2.7/dist-packages/juju/machine/unit.py", line 301, in 
is_running
   prefix=self.container.container_name)
 File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 
1069, in _inlineCallbacks
   result = result.throwExceptionIntoGenerator(g)
 File "/usr/lib/python2.7/dist-packages/twisted/python/failure.py", line 
389, in throwExceptionIntoGenerator
   return g.throw(self.type, self.value, self.tb)
 File "/usr/lib/python2.7/dist-packages/juju/lib/lxc/__init__.py", line 
147, in get_containers
   _, output = yield deferToThread(_cmd, ["lxc-ls"])
 File "/usr/lib/python2.7/dist-packages/twisted/python/threadpool.py", line 
172, in _worker
   result = context.call(ctx, function, *args, **kwargs)
 File "/usr/lib/python2.7/dist-packages/twisted/python/context.py", line 
118, in callWithContext
   return self.currentContext().callWithContext(ctx, func, *args, **kw)
 File "/usr/lib/python2.7/dist-packages/twisted/python/context.py", line 
81, in callWithContext
   return func(*args,**kw)
 File "/usr/lib/python2.7/dist-packages/juju/lib/lxc/__init__.py", line 48, 
in _cmd
   raise LXCError(stdout_data)
   LXCError: Fatal Python error: Py_Initialize: Unable to get the locale 
encoding
 File "/usr/lib/python2.7/encodings/__init__.py", line 123
   raise CodecRegistryError,\
   ^
   SyntaxError: invalid syntax

  
  WORKAROUND:
  Add "-Es" to /usr/bin/lxc-ls (after /usr/bin/python3 ) so that those 
environment variables are ignored.

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

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

[Touch-packages] [Bug 1334968] Re: [HP ProBook 445 G1] Microphone mute key does not work

2015-04-01 Thread Hui Wang

** Changed in: hwe-next
   Status: Fix Committed => Fix Released

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

Title:
  [HP ProBook 445 G1] Microphone mute key does not work

Status in HWE Next Project:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  CID: 201307-13919 HP ProBook 445 G1

  The microphone mute key does not work on this system
  Keystroke cannot be detected by xev, but it shows:
  keycode 465 press
  keycode 465 release
  from "sudo showkey -k"

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-30-generic 3.13.0-30.54
  ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 1508 F pulseaudio
   /dev/snd/pcmC1D0c:   ubuntu 1508 F...m pulseaudio
   /dev/snd/controlC0:  ubuntu 1508 F pulseaudio
  CRDA:
   country TW:
(2402 - 2472 @ 40), (3, 27)
(5270 - 5330 @ 40), (3, 17), DFS
(5735 - 5815 @ 40), (3, 30)
  CurrentDesktop: Unity
  Date: Fri Jun 27 01:10:10 2014
  HibernationDevice: RESUME=UUID=be96939f-ffde-4407-a99e-17beebf60ad5
  InstallationDate: Installed on 2014-06-27 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP ProBook 445 G1 Notebook PC
  ProcFB:
   0 radeondrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic 
root=UUID=fd8269ec-b9ab-4f08-8eaf-6c3bfa26a4e1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-30-generic N/A
   linux-backports-modules-3.13.0-30-generic  N/A
   linux-firmware 1.127.4
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/05/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68CPE Ver. F.21
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1950
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 91.0B
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68CPEVer.F.21:bd09/05/2013:svnHewlett-Packard:pnHPProBook445G1NotebookPC:pvrA201BC1203:rvnHewlett-Packard:rn1950:rvrKBCVersion91.0B:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 445 G1 Notebook PC
  dmi.product.version: A201BC1203
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1334968/+subscriptions

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

[Touch-packages] [Bug 1429687] Re: Cannot import two files with the same name to ContentStore.App

2015-04-01 Thread Ken VanDine

** Changed in: content-hub
   Status: Confirmed => Fix Released

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

Title:
  Cannot import two files with the same name to ContentStore.App

Status in Content sharing/picking infrastructure and service:
  Fix Released
Status in content-hub package in Ubuntu:
  Fix Released

Bug description:
  When you import a file using a ContentScope and ContentStore.App, it
  gets copied to ~/.local/share///.  If
  you try to import another file with the same name and content type,
  the existing file will be left in place and the new file not copied
  over.  However, you get a ContentItem returned with the a URL pointing
  to the old imported file.

  My expectation is that the new file should be copied to file(1) or
  similar.  Perhaps this should only happen if the files are distinct.
  Failing this, ContentHub should throw an error and not let me think
  that the import succeeded.

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

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

[Touch-packages] [Bug 1429695] Re: Import broken for ContentTypes without default apps

2015-04-01 Thread Ken VanDine

** Changed in: content-hub
   Status: Confirmed => Fix Released

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

Title:
  Import broken for ContentTypes without default apps

Status in Content sharing/picking infrastructure and service:
  Fix Released
Status in content-hub package in Ubuntu:
  Fix Released

Bug description:
  The content hub is broken when trying to import a content type for
  which there is no default handler (for example, ContentType.EBooks).
  When you try to import from the default provider, the
  ContentTransferHint will open and start a spinner, but nothing else
  happens.  If you try to choose a provider, you at least get an error
  message stating that there are no providers.

  This is seen on a device running vivid/devel r1.

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

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

[Touch-packages] [Bug 1439483] [NEW] crash at logon

2015-04-01 Thread clean

Public bug reported:

crash at logon

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

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

Title:
  crash at logon

Status in colord package in Ubuntu:
  New

Bug description:
  crash at logon

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

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

[Touch-packages] [Bug 1437486] Re: sms notification baloon dont work to send sms directly

2015-04-01 Thread Tiago Salem Herrmann

In order to debug this issue it would be good to have some additional
information that can be retrieved using the terminal app available in
the ubuntu store.

Once you are able to reliably reproduce the bug, try the following
steps:

1) open terminal application
2) type "mc-tool dump" and press return
3) dismiss the keyboard by swiping it down
4) long press anywhere on the screen to invoke the popup menu, select the text, 
copy the output and paste it here.

However, if you happen to have adb access from your desktop to your device 
(developer mode active), this is way easier: 
adb shell mc-tool dump

The output might contain private data (like your phone number), so feel
free to change it before posting.

Thank you.

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

Title:
  sms notification baloon dont work to send sms directly

Status in telephony-service package in Ubuntu:
  Confirmed

Bug description:
  When the Ubuntu Touch phone (BQ) is sleeping and I receive an SMS, if
  I click the ballon, a input appears, I completed the answer to that
  SMS, and clicked SEND, but the SMS never arrived and never left from
  my phone. I repetead those steps one hour later, the same behaviour.

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

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

[Touch-packages] [Bug 518056] Re: cedilla appears as accented c (ć instead of ç) when typing 'c

2015-04-01 Thread Gunnar Hjalmarsson

On 2015-04-01 19:24, Rico Tzschichholz wrote:
> @gunnarhj: The syntax of cedilla-brazil.sh is erroneous.

Ouch! It was not a syntax error, really, but still a stupid error. :(
Fixed in language-selector 0.142.

Thanks for pointing it out!

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

Title:
  cedilla appears as accented c (ć instead of ç) when typing 'c

Status in central project for keyboard configuration:
  Confirmed
Status in gtk+2.0 package in Ubuntu:
  Confirmed
Status in language-selector package in Ubuntu:
  Fix Released
Status in libx11 package in Ubuntu:
  New
Status in xkeyboard-config package in Ubuntu:
  Confirmed

Bug description:
  
  When typing in a US-international keyboard with dead-keys (or 
UK-international), 
  typing 'c results in an accented c instead of a cedilla.

  There is a workaround, which is editing the

  /usr/lib/gtk-2.0/2.10.0/immodule-files.d/libgtk2.0-0.immodules

  file and changing the line

  "cedilla" "Cedilla" "gtk20" "/usr/share/locale"
  "az:ca:co:fr:gv:oc:pt:sq:tr:wa"

  to

  "cedilla" "Cedilla" "gtk20" "/usr/share/locale"
  "az:ca:co:fr:gv:oc:pt:sq:tr:wa:en"

  (add the 'en' at the end).

  However, every time some update on this file is applied, one looses the 
change,
  and we get back to the accented c. That means having to modify the file again,
  logout and login.

  For me this is no problem. But for my brother, mom, dad, etc, it is always 
something
  that at least makes me less proud of having convinced them to use Ubuntu, 
because
  they don't know what to do each time this happens.

  I think we really need a configurable keyboard layout, or at least (and that 
would
  be very easy), the inclusion of alternate layouts on install that for the 
dead-key
  options (as US-deadkey and UK-deakey), alternate layouts as 
US-deadkey-cedilla.

  This change is relevant for at least Portuguese and French.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xkeyboard-config/+bug/518056/+subscriptions

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

[Touch-packages] [Bug 1437486] Re: sms notification baloon dont work to send sms directly

2015-04-01 Thread Bill Filler

The expected behavior is for the message to disappear from the menu
after it is sent. The original message and your reply should show up in
the messaging app. Sounds like this is not happening for you so it's
definitely a bug. If either of you can attach the telephony service log
to this bug that would be extremely

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

Title:
  sms notification baloon dont work to send sms directly

Status in telephony-service package in Ubuntu:
  Confirmed

Bug description:
  When the Ubuntu Touch phone (BQ) is sleeping and I receive an SMS, if
  I click the ballon, a input appears, I completed the answer to that
  SMS, and clicked SEND, but the SMS never arrived and never left from
  my phone. I repetead those steps one hour later, the same behaviour.

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

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

[Touch-packages] [Bug 1439445] Re: systemd-fsck laps 30s on boot for /dev/mapper/home

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1439445/+attachment/4363682/+files/CurrentDmesg.txt

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

Title:
  systemd-fsck laps 30s on boot for /dev/mapper/home

Status in systemd package in Ubuntu:
  New

Bug description:
  Using 15.04 beta 2 witht the following setup:
  /dev/sda is a SSD (crucial mx100) in main SATA port of Inspiron 15 3521
  /dev/sdb is a hdd in an hdd caddy in sata original dvd drive bay

  root is /dev/sda4 on SSD
  /dev/sda5 is a caching bcache partition (on SSD) for the /dev/sdb5 bcache 
backing LUKS home partition

  /etc/crypttab:
  home/dev/bcache0 
/root/.x-64bd-44ca-a46e-xx.bin luks

  For an unknown reason, during boot, systemd-fsck laps 30s for doing a fsck on 
/dev/mapper/home.
  But the fsck is not really run, it should return immediatly

  $ systemd-analyze blame|head -3
   32.241s systemd-fsck@dev-mapper-home.service
    8.137s plymouth-quit-wait.service
    7.691s NetworkManager-wait-online.service

  $ systemctl status systemd-fsck@dev-mapper-home.service
  ● systemd-fsck@dev-mapper-home.service - File System Check on /dev/mapper/home
     Loaded: loaded (/lib/systemd/system/systemd-fsck@.service; static; vendor 
preset: enabled)
     Active: active (exited) since mer. 2015-04-01 22:45:58 CEST; 2h 45min ago
   Docs: man:systemd-fsck@.service(8)
   Main PID: 821 (code=exited, status=0/SUCCESS)

  avril 01 22:45:58 callisto systemd-fsck[821]: Cannot communicate fsck 
progress to fsckd: Broken pipe
  avril 01 22:45:58 callisto systemd-fsck[821]: Cannot communicate fsck 
progress to fsckd: Broken pipe
  avril 01 22:45:58 callisto systemd-fsck[821]: Cannot communicate fsck 
progress to fsckd: Broken pipe
  avril 01 22:45:58 callisto systemd-fsck[821]: Cannot communicate fsck 
progress to fsckd: Broken pipe
  avril 01 22:45:58 callisto systemd-fsck[821]: Cannot communicate fsck 
progress to fsckd: Broken pipe
  avril 01 22:45:58 callisto systemd-fsck[821]: Cannot communicate fsck 
progress to fsckd: Broken pipe
  avril 01 22:45:58 callisto systemd-fsck[821]: Cannot communicate fsck 
progress to fsckd: Broken pipe
  avril 01 22:45:58 callisto systemd-fsck[821]: Cannot communicate fsck 
progress to fsckd: Broken pipe
  avril 01 22:45:58 callisto systemd-fsck[821]: /dev/mapper/home : 
169002/13148160 fichiers (0.8% non contigus), 36631520/52566272 blocs
  avril 01 22:45:58 callisto systemd[1]: Started File System Check on 
/dev/mapper/home.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-4ubuntu10
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr  2 01:24:15 2015
  InstallationDate: Installed on 2015-04-01 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
  MachineType: Dell Inc. Inspiron 3521
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic.efi.signed 
root=UUID=cx---x-xxx ro quiet splash
  SourcePackage: systemd
  UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: XX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd10/25/2013:svnDellInc.:pnInspiron3521:pvrA12:rvnDellInc.:rnX:rvrA02:cvnDellInc.:ct8:cvrA12:
  dmi.product.name: Inspiron 3521
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1439445] Re: systemd-fsck laps 30s on boot for /dev/mapper/home

** Attachment removed: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1439445/+attachment/4363619/+files/CurrentDmesg.txt

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

Title:
  systemd-fsck laps 30s on boot for /dev/mapper/home

Status in systemd package in Ubuntu:
  New

Bug description:
  Using 15.04 beta 2 witht the following setup:
  /dev/sda is a SSD (crucial mx100) in main SATA port of Inspiron 15 3521
  /dev/sdb is a hdd in an hdd caddy in sata original dvd drive bay

  root is /dev/sda4 on SSD
  /dev/sda5 is a caching bcache partition (on SSD) for the /dev/sdb5 bcache 
backing LUKS home partition

  /etc/crypttab:
  home/dev/bcache0 
/root/.x-64bd-44ca-a46e-xx.bin luks

  For an unknown reason, during boot, systemd-fsck laps 30s for doing a fsck on 
/dev/mapper/home.
  But the fsck is not really run, it should return immediatly

  $ systemd-analyze blame|head -3
   32.241s systemd-fsck@dev-mapper-home.service
    8.137s plymouth-quit-wait.service
    7.691s NetworkManager-wait-online.service

  $ systemctl status systemd-fsck@dev-mapper-home.service
  ● systemd-fsck@dev-mapper-home.service - File System Check on /dev/mapper/home
     Loaded: loaded (/lib/systemd/system/systemd-fsck@.service; static; vendor 
preset: enabled)
     Active: active (exited) since mer. 2015-04-01 22:45:58 CEST; 2h 45min ago
   Docs: man:systemd-fsck@.service(8)
   Main PID: 821 (code=exited, status=0/SUCCESS)

  avril 01 22:45:58 callisto systemd-fsck[821]: Cannot communicate fsck 
progress to fsckd: Broken pipe
  avril 01 22:45:58 callisto systemd-fsck[821]: Cannot communicate fsck 
progress to fsckd: Broken pipe
  avril 01 22:45:58 callisto systemd-fsck[821]: Cannot communicate fsck 
progress to fsckd: Broken pipe
  avril 01 22:45:58 callisto systemd-fsck[821]: Cannot communicate fsck 
progress to fsckd: Broken pipe
  avril 01 22:45:58 callisto systemd-fsck[821]: Cannot communicate fsck 
progress to fsckd: Broken pipe
  avril 01 22:45:58 callisto systemd-fsck[821]: Cannot communicate fsck 
progress to fsckd: Broken pipe
  avril 01 22:45:58 callisto systemd-fsck[821]: Cannot communicate fsck 
progress to fsckd: Broken pipe
  avril 01 22:45:58 callisto systemd-fsck[821]: Cannot communicate fsck 
progress to fsckd: Broken pipe
  avril 01 22:45:58 callisto systemd-fsck[821]: /dev/mapper/home : 
169002/13148160 fichiers (0.8% non contigus), 36631520/52566272 blocs
  avril 01 22:45:58 callisto systemd[1]: Started File System Check on 
/dev/mapper/home.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-4ubuntu10
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr  2 01:24:15 2015
  InstallationDate: Installed on 2015-04-01 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
  MachineType: Dell Inc. Inspiron 3521
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic.efi.signed 
root=UUID=cx---x-xxx ro quiet splash
  SourcePackage: systemd
  UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: XX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd10/25/2013:svnDellInc.:pnInspiron3521:pvrA12:rvnDellInc.:rnX:rvrA02:cvnDellInc.:ct8:cvrA12:
  dmi.product.name: Inspiron 3521
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1439440] Re: Laptop does not go to sleep when closing lid with external monitor connected

** Attachment removed: "UdevDb.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1439440/+attachment/4363590/+files/UdevDb.txt

** Attachment added: "UdevDb.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1439440/+attachment/4363656/+files/UdevDb.txt

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

Title:
  Laptop does not go to sleep when closing lid with external monitor
  connected

Status in xorg package in Ubuntu:
  New

Bug description:
  Using Dell Inspiron 15 3521 with Intel HD 4000 and an external monitor on 
HDMI output, in 15.04 beta 2:
  when closing the lid of the laptop, the laptop does not go to sleep (suspend 
to ram) as expected, but instead stays on, with the external monitor still on.

  I excepted that the laptop goes to sleep and the external monitor was
  blanked and turned off. This was the behavior on 14.10

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Apr  2 01:17:27 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 3.19.0-10-generic, x86_64: installed
   virtualbox, 4.3.26, 3.19.0-10-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0597]
  InstallationDate: Installed on 2015-04-01 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
  MachineType: Dell Inc. Inspiron 3521
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic.efi.signed 
root=UUID=cc1a2c64-75d0-49d2-a4ab-b3101863b06a ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 06RYX8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd10/25/2013:svnDellInc.:pnInspiron3521:pvrA12:rvnDellInc.:rn06RYX8:rvrA02:cvnDellInc.:ct8:cvrA12:
  dmi.product.name: Inspiron 3521
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.1+15.04.20150303-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.59-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Thu Apr  2 00:14:49 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 939 
   vendor LGD
  xserver.version: 2:1.17.1-0ubuntu3

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

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

[Touch-packages] [Bug 1439445] Re: systemd-fsck laps 30s on boot for /dev/mapper/home

** Attachment added: "UdevDb.txt"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1439445/+attachment/4363655/+files/UdevDb.txt

** Description changed:

  Using 15.04 beta 2 witht the following setup:
  /dev/sda is a SSD (crucial mx100) in main SATA port of Inspiron 15 3521
  /dev/sdb is a hdd in an hdd caddy in sata original dvd drive bay
  
  root is /dev/sda4 on SSD
  /dev/sda5 is a caching bcache partition (on SSD) for the /dev/sdb5 bcache 
backing LUKS home partition
  
  /etc/crypttab:
  home/dev/bcache0 
/root/.x-64bd-44ca-a46e-xx.bin luks
  
  For an unknown reason, during boot, systemd-fsck laps 30s for doing a fsck on 
/dev/mapper/home.
  But the fsck is not really run, it should return immediatly
  
  $ systemd-analyze blame|head -3
-  32.241s systemd-fsck@dev-mapper-home.service
-   8.137s plymouth-quit-wait.service
-   7.691s NetworkManager-wait-online.service
+  32.241s systemd-fsck@dev-mapper-home.service
+   8.137s plymouth-quit-wait.service
+   7.691s NetworkManager-wait-online.service
  
  $ systemctl status systemd-fsck@dev-mapper-home.service
  ● systemd-fsck@dev-mapper-home.service - File System Check on /dev/mapper/home
-Loaded: loaded (/lib/systemd/system/systemd-fsck@.service; static; vendor 
preset: enabled)
-Active: active (exited) since mer. 2015-04-01 22:45:58 CEST; 2h 45min ago
-  Docs: man:systemd-fsck@.service(8)
-  Main PID: 821 (code=exited, status=0/SUCCESS)
+    Loaded: loaded (/lib/systemd/system/systemd-fsck@.service; static; vendor 
preset: enabled)
+    Active: active (exited) since mer. 2015-04-01 22:45:58 CEST; 2h 45min ago
+  Docs: man:systemd-fsck@.service(8)
+  Main PID: 821 (code=exited, status=0/SUCCESS)
  
  avril 01 22:45:58 callisto systemd-fsck[821]: Cannot communicate fsck 
progress to fsckd: Broken pipe
  avril 01 22:45:58 callisto systemd-fsck[821]: Cannot communicate fsck 
progress to fsckd: Broken pipe
  avril 01 22:45:58 callisto systemd-fsck[821]: Cannot communicate fsck 
progress to fsckd: Broken pipe
  avril 01 22:45:58 callisto systemd-fsck[821]: Cannot communicate fsck 
progress to fsckd: Broken pipe
  avril 01 22:45:58 callisto systemd-fsck[821]: Cannot communicate fsck 
progress to fsckd: Broken pipe
  avril 01 22:45:58 callisto systemd-fsck[821]: Cannot communicate fsck 
progress to fsckd: Broken pipe
  avril 01 22:45:58 callisto systemd-fsck[821]: Cannot communicate fsck 
progress to fsckd: Broken pipe
  avril 01 22:45:58 callisto systemd-fsck[821]: Cannot communicate fsck 
progress to fsckd: Broken pipe
  avril 01 22:45:58 callisto systemd-fsck[821]: /dev/mapper/home : 
169002/13148160 fichiers (0.8% non contigus), 36631520/52566272 blocs
  avril 01 22:45:58 callisto systemd[1]: Started File System Check on 
/dev/mapper/home.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-4ubuntu10
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr  2 01:24:15 2015
  InstallationDate: Installed on 2015-04-01 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
  MachineType: Dell Inc. Inspiron 3521
- ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic.efi.signed 
root=UUID=cc1a2c64-75d0-49d2-a4ab-b3101863b06a ro quiet splash
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic.efi.signed 
root=UUID=cx---x-xxx ro quiet splash
  SourcePackage: systemd
  UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
- dmi.board.name: 06RYX8
+ dmi.board.name: XX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
- dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd10/25/2013:svnDellInc.:pnInspiron3521:pvrA12:rvnDellInc.:rn06RYX8:rvrA02:cvnDellInc.:ct8:cvrA12:
+ dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd10/25/2013:svnDellInc.:pnInspiron3521:pvrA12:rvnDellInc.:rnX:rvrA02:cvnDellInc.:ct8:cvrA12:
  dmi.product.name: Inspiron 3521
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.

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

Title:
  systemd-fsck laps 30s on boot for /dev/mapper/home

Status in systemd package in Ubuntu:
  New

Bug description:
  Using 15.04 beta 2 witht the following setup:
  /dev/sda is a SSD (crucial mx100) in main SATA port of Inspiron 15 3521
  /dev/sdb is a hdd in an hdd caddy in sata original dvd drive bay

  root is /dev/sda4 on SSD
  /dev/sda5 is a caching bcache partition (on SSD) for

[Touch-packages] [Bug 1434579] Re: Unable to install VirtualBox Guest Service in 15.04

2015-04-01 Thread Adam Conrad

This isn't a bug in software-properties.  What I can't decide is if it's
a bug in virtualbox-guest* or ubuntu-drivers-common.  Basically, here's
what's happening:

1) The virtualbox-guest* packages have a modalias for the "guest services", but 
not the VGA controller.
2) We pulled the DKMS drivers into the kernel.
3) The above situation confuses ubuntu-drivers-common, which really wants to 
install vbox-dkms, but we have it builtin.
4) Nothing wants to install vbox-x11, which we actually want.

So, the lack of modaliases on vbox-x11 is definitely a vbox bug, and the
dependencies are also a bit strong between vbox packages (we should drop
some recommends to suggests, to stop trying to forcefully install
compilers to get an X driver).

That said, we might also want to quirk the ubuntu-drivers-common
detection a bit to either hide vbox-dkms altogether, or actually let us
use it if it's a potential upgrade.  Currently, neither of these options
is in play, and we see it, but it's greyed out, which is amazingly
confusing.

** Package changed: software-properties (Ubuntu) => ubuntu-drivers-
common (Ubuntu)

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

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

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

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

Title:
  Unable to install VirtualBox Guest Service in 15.04

Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed
Status in virtualbox package in Ubuntu:
  Confirmed

Bug description:
  It is not longer possible to select VirtualBox Guest Service in 15.04.
  The only options available are:

* Continue using a manually install driver
* Do not use the device

  The option 'Using x86 virtualisation solution - guest addition module'
  is no longer selectable. See the attached screen shot. This is from a
  fresh install of Ubuntu MATE 15.04 daily (20th March) and no drivers
  have been manually installed.

  In light of the Virtualbox issue where new installs on Virtualbox have
  a resolution of 640x480
  (https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1368784/)
  this is going to be a frustration for many users.

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

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

[Touch-packages] [Bug 1439445] [NEW] systemd-fsck laps 30s on boot for /dev/mapper/home

Public bug reported:

Using 15.04 beta 2 witht the following setup:
/dev/sda is a SSD (crucial mx100) in main SATA port of Inspiron 15 3521
/dev/sdb is a hdd in an hdd caddy in sata original dvd drive bay

root is /dev/sda4 on SSD
/dev/sda5 is a caching bcache partition (on SSD) for the /dev/sdb5 bcache 
backing LUKS home partition

/etc/crypttab:
home/dev/bcache0 /root/.x-64bd-44ca-a46e-xx.bin 
luks

For an unknown reason, during boot, systemd-fsck laps 30s for doing a fsck on 
/dev/mapper/home.
But the fsck is not really run, it should return immediatly

$ systemd-analyze blame|head -3
 32.241s systemd-fsck@dev-mapper-home.service
  8.137s plymouth-quit-wait.service
  7.691s NetworkManager-wait-online.service

$ systemctl status systemd-fsck@dev-mapper-home.service
● systemd-fsck@dev-mapper-home.service - File System Check on /dev/mapper/home
   Loaded: loaded (/lib/systemd/system/systemd-fsck@.service; static; vendor 
preset: enabled)
   Active: active (exited) since mer. 2015-04-01 22:45:58 CEST; 2h 45min ago
 Docs: man:systemd-fsck@.service(8)
 Main PID: 821 (code=exited, status=0/SUCCESS)

avril 01 22:45:58 callisto systemd-fsck[821]: Cannot communicate fsck progress 
to fsckd: Broken pipe
avril 01 22:45:58 callisto systemd-fsck[821]: Cannot communicate fsck progress 
to fsckd: Broken pipe
avril 01 22:45:58 callisto systemd-fsck[821]: Cannot communicate fsck progress 
to fsckd: Broken pipe
avril 01 22:45:58 callisto systemd-fsck[821]: Cannot communicate fsck progress 
to fsckd: Broken pipe
avril 01 22:45:58 callisto systemd-fsck[821]: Cannot communicate fsck progress 
to fsckd: Broken pipe
avril 01 22:45:58 callisto systemd-fsck[821]: Cannot communicate fsck progress 
to fsckd: Broken pipe
avril 01 22:45:58 callisto systemd-fsck[821]: Cannot communicate fsck progress 
to fsckd: Broken pipe
avril 01 22:45:58 callisto systemd-fsck[821]: Cannot communicate fsck progress 
to fsckd: Broken pipe
avril 01 22:45:58 callisto systemd-fsck[821]: /dev/mapper/home : 
169002/13148160 fichiers (0.8% non contigus), 36631520/52566272 blocs
avril 01 22:45:58 callisto systemd[1]: Started File System Check on 
/dev/mapper/home.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: systemd 219-4ubuntu10
ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
Uname: Linux 3.19.0-10-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.16.2-0ubuntu4
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Apr  2 01:24:15 2015
InstallationDate: Installed on 2015-04-01 (0 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
MachineType: Dell Inc. Inspiron 3521
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic.efi.signed 
root=UUID=cc1a2c64-75d0-49d2-a4ab-b3101863b06a ro quiet splash
SourcePackage: systemd
UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/25/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A12
dmi.board.name: 06RYX8
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A12
dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd10/25/2013:svnDellInc.:pnInspiron3521:pvrA12:rvnDellInc.:rn06RYX8:rvrA02:cvnDellInc.:ct8:cvrA12:
dmi.product.name: Inspiron 3521
dmi.product.version: A12
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug third-party-packages vivid

** Attachment removed: "UdevDb.txt"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1439445/+attachment/4363628/+files/UdevDb.txt

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

Title:
  systemd-fsck laps 30s on boot for /dev/mapper/home

Status in systemd package in Ubuntu:
  New

Bug description:
  Using 15.04 beta 2 witht the following setup:
  /dev/sda is a SSD (crucial mx100) in main SATA port of Inspiron 15 3521
  /dev/sdb is a hdd in an hdd caddy in sata original dvd drive bay

  root is /dev/sda4 on SSD
  /dev/sda5 is a caching bcache partition (on SSD) for the /dev/sdb5 bcache 
backing LUKS home partition

  /etc/crypttab:
  home/dev/bcache0 
/root/.x-64bd-44ca-a46e-xx.bin luks

  For an unknown reason, during boot, systemd-fsck laps 30s for doing a fsck on 
/dev/mapper/home.
  But the fsck is not really run, it should return immediatly

  $ systemd-analyze blame|head -3
   32.241s systemd-fsck@dev-mapper-home.service
8.137s plymouth-quit-wait.service
7.691s NetworkManager-wait-online.service

  $ systemctl status systemd-fsck@dev-mapper-home.service
  ● systemd-fsck@dev-mapper-home.service - File System Check on /dev/mapper/home
 Loaded: loaded (/lib/systemd/system/systemd-fsck@.service; static

[Touch-packages] [Bug 1439440] [NEW] Laptop does not go to sleep when closing lid with external monitor connected

Public bug reported:

Using Dell Inspiron 15 3521 with Intel HD 4000 and an external monitor on HDMI 
output, in 15.04 beta 2:
when closing the lid of the laptop, the laptop does not go to sleep (suspend to 
ram) as expected, but instead stays on, with the external monitor still on.

I excepted that the laptop goes to sleep and the external monitor was
blanked and turned off. This was the behavior on 14.10

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
Uname: Linux 3.19.0-10-generic x86_64
NonfreeKernelModules: wl
.tmp.unity.support.test.0:
 
ApportVersion: 2.16.2-0ubuntu4
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Thu Apr  2 01:17:27 2015
DistUpgraded: Fresh install
DistroCodename: vivid
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.248+bdcom, 3.19.0-10-generic, x86_64: installed
 virtualbox, 4.3.26, 3.19.0-10-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:0597]
InstallationDate: Installed on 2015-04-01 (0 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
MachineType: Dell Inc. Inspiron 3521
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic.efi.signed 
root=UUID=cc1a2c64-75d0-49d2-a4ab-b3101863b06a ro quiet splash
SourcePackage: xorg
Symptom: display
UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/25/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A12
dmi.board.name: 06RYX8
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A12
dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd10/25/2013:svnDellInc.:pnInspiron3521:pvrA12:rvnDellInc.:rn06RYX8:rvrA02:cvnDellInc.:ct8:cvrA12:
dmi.product.name: Inspiron 3521
dmi.product.version: A12
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.1+15.04.20150303-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.59-0ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2build1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
xserver.bootTime: Thu Apr  2 00:14:49 2015
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 939 
 vendor LGD
xserver.version: 2:1.17.1-0ubuntu3

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


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

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

Title:
  Laptop does not go to sleep when closing lid with external monitor
  connected

Status in xorg package in Ubuntu:
  New

Bug description:
  Using Dell Inspiron 15 3521 with Intel HD 4000 and an external monitor on 
HDMI output, in 15.04 beta 2:
  when closing the lid of the laptop, the laptop does not go to sleep (suspend 
to ram) as expected, but instead stays on, with the external monitor still on.

  I excepted that the laptop goes to sleep and the external monitor was
  blanked and turned off. This was the behavior on 14.10

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Apr  2 01:17:27 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 3.19.0-10-generic, x86_64: installed
   virtualbox, 4.3.26, 3.19.0-10-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controlle

[Touch-packages] [Bug 1429695] Re: Import broken for ContentTypes without default apps

This bug was fixed in the package content-hub -
0.0+15.04.20150331-0ubuntu1

---
content-hub (0.0+15.04.20150331-0ubuntu1) vivid; urgency=medium

  [ Ken VanDine ]
  * When requesting an import from an unknown peer, abort the transfer.
This is most likely to occur when requesting the default peer for a
ContentType that has no default registered. (LP: #1429695)
 -- CI Train BotTue, 31 Mar 2015 14:10:11 +

** Changed in: content-hub (Ubuntu)
   Status: New => Fix Released

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

Title:
  Import broken for ContentTypes without default apps

Status in Content sharing/picking infrastructure and service:
  Confirmed
Status in content-hub package in Ubuntu:
  Fix Released

Bug description:
  The content hub is broken when trying to import a content type for
  which there is no default handler (for example, ContentType.EBooks).
  When you try to import from the default provider, the
  ContentTransferHint will open and start a spinner, but nothing else
  happens.  If you try to choose a provider, you at least get an error
  message stating that there are no providers.

  This is seen on a device running vivid/devel r1.

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

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

[Touch-packages] [Bug 1435287] Re: cups-browsed crashed with SIGSEGV in g_slist_foreach()

2015-04-01 Thread Till Kamppeter

If you are able ny repeatedly rebooting your machine to get a sufficient
number of crashes, please try the following changes (alway one at a
time) to see whether the crashes go away:

1. Modify /etc/cups/cups-browsed.conf, changing the line

BrowseRemoteProtocols dnssd cups

to

BrowseRemoteProtocols dnssd

If this does not improve the situation, try

BrowseRemoteProtocols cups

2. Downgrade to an older version of cups-filters

3. Downgrade to an older version of libglib2.0-0

4. Temporarily make shared print queues on remote machines not being
shared.

5. Turn off network printers (printers connected by Ethernet or WiFi,
independent whether you have a local print queue for them or not.

Do one or more of these measures eliminate the crashing?

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

Title:
  cups-browsed crashed with SIGSEGV in g_slist_foreach()

Status in cups-filters package in Ubuntu:
  Incomplete
Status in glib2.0 package in Ubuntu:
  Incomplete

Bug description:
  Daily build from Mar 23rd 2015, booted from USB on Lenovo T440s.
  Selected 'Try Ubuntu', crash occured during startup

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: cups-browsed 1.0.67-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.355
  CupsErrorLog:
   
  Date: Mon Mar 23 11:14:22 2015
  ExecutablePath: /usr/sbin/cups-browsed
  LiveMediaBuild: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150323)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: LENOVO 20AQ007TGE
  Papersize: a4
  ProcCmdline: /usr/sbin/cups-browsed
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true persistent 
file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet 
splash --- maybe-ubiquity
  SegvAnalysis:
   Segfault happened at: 0x7f926f1a2cd0 :   mov
0x8(%rdi),%rbx
   PC (0x7f926f1a2cd0) ok
   source "0x8(%rdi)" (0x0009) not located in a known VMA region (needed 
readable region)!
   destination "%rbx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: cups-filters
  StacktraceTop:
   g_slist_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_slist_free_full () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: cups-browsed crashed with SIGSEGV in g_slist_foreach()
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 09/03/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET79WW (2.29 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AQ007TGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET79WW(2.29):bd09/03/2014:svnLENOVO:pn20AQ007TGE:pvrThinkPadT440s:rvnLENOVO:rn20AQ007TGE:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20AQ007TGE
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1438360] Re: PCI/internal sound card not detected

2015-04-01 Thread Raymond

do you mean NC 91 ?

http://www.jetwaycomputer.com/NC91.html

refer to user manual
check wthether you disable hda audio in bios setup 


usually HDA audio controller is at 00:1b.0

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  This is a Jetway NC 9I motherboard with Intel NC10 chipset and a
  RealTek ALC662 sound chip imbedded.  It has an Intel Atom D525
  processor on it.  I have 30 of these boards I was hoping to put Ubuntu
  on for people that need them.

   I have spent over three weeks on this trying to follow the forums on how to 
solve this problem.  I have also gone to Realtek's website and tried to use 
their instructions to solve the problem.  From the dignostic reports that I saw 
it looks like the sound chip or codec cannot be found and that pulse is somehow 
working instead?  
  I went here: https://help.ubuntu.com/community/SoundTroubleshootingProcedure
and got this result:  
http://www.alsa-project.org/db/?f=f057abda5a101970d2980eae4341684ee857cbeb

  I went to realtek's site and downloaded their Linux HD drivers here:
  
http://152.104.125.41/downloads/downloadsView.aspx?Langid=1&PNid=24&PFid=24&Level=4&Conn=3&DownTypeID=3&GetDown=false

  I also went here:  http://ubuntuforums.org/showthread.php?t=1026931 
I didn't see any results from these either.  

  When I go into system sound it just says "Play sound through Dummy
  Output"

  I have tested the speakers, they work on other devices.  It is plugged
  into the right output...

  It does not work in Ubuntu 12 or 14.04, 64 bit.  It does not work in
  Lubuntu either.  I have not tried 32 bit.

  I must be doing something out of order as I don't see anyone else
  reporting this problem and Jetway says that no one has reported a
  problem to them?

  Thank you in advance for your help.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7
  Uname: Linux 3.16.0-33-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.8
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Mon Mar 30 11:17:24 2015
  InstallationDate: Installed on 2015-03-20 (10 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/26/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080016
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080016:bd02/26/2013:svn:pn:pvr:rvn:rn:rvr:cvn:ct3:cvr:

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

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

[Touch-packages] [Bug 1439436] [NEW] NM in vivid tries to take over my libvirt bridge, deconfigures its address

2015-04-01 Thread Steve Langasek

Public bug reported:

Over the past couple of months in vivid, from time to time I have
noticed that my virbr0 interface, which is set up and managed by
libvirt-bin, has been in an "up" state with no IP address configured.

As I don't use VMs on my laptop very frequently, I don't know when the
problem started and I don't know when exactly the problem is being
triggered.  But a search through logs shows the following:

Mar 16 16:48:56 virgil systemd[1]: Stopping Network Manager...
[...]
Mar 16 16:48:56 virgil NetworkManager[32588]:  (virbr0): device state 
change: activated -> deactivating (reason 'removed') [100 110 36]
Mar 16 16:48:56 virgil NetworkManager[32588]:  (virbr0): device state 
change: deactivating -> unmanaged (reason 'removed') [110 10 36]
Mar 16 16:48:56 virgil NetworkManager[32588]:  (virbr0): deactivating 
device (reason 'removed') [36]
Mar 16 16:48:56 virgil avahi-daemon[1336]: Withdrawing address record for 
192.168.122.1 on virbr0.
[...]
Mar 16 16:48:56 virgil systemd[1]: Starting Network Manager Script Dispatcher 
Service...
[...]
Mar 16 16:48:56 virgil systemd[1]: Started Network Manager Script Dispatcher 
Service.
[...]
Mar 16 16:48:56 virgil nm-dispatcher: Dispatching action 'down' for virbr0
[...]
Mar 16 16:48:56 virgil systemd[1]: Starting Network Manager...
[...]
Mar 16 16:48:56 virgil NetworkManager[6097]:  devices added (path: 
/sys/devices/virtual/net/virbr0, iface: virbr0)
Mar 16 16:48:56 virgil NetworkManager[6097]:  device added (path: 
/sys/devices/virtual/net/virbr0, iface: virbr0): no ifupdown configuration 
found.
[...]
Mar 16 16:49:01 virgil systemd[1]: Started Network Manager.
[...]
Mar 16 16:49:02 virgil NetworkManager[6097]:  (virbr0): carrier is OFF
Mar 16 16:49:02 virgil NetworkManager[6097]:  (virbr0): new Bridge device 
(driver: 'bridge' ifindex: 5)
Mar 16 16:49:02 virgil NetworkManager[6097]:  (virbr0): exported as 
/org/freedesktop/NetworkManager/Devices/4
Mar 16 16:49:02 virgil NetworkManager[6097]:  (virbr0): device state 
change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Mar 16 16:49:02 virgil NetworkManager[6097]:  (virbr0): device not up 
after timeout!
Mar 16 16:49:02 virgil NetworkManager[6097]:  (virbr0): preparing device
Mar 16 16:49:02 virgil NetworkManager[6097]: nm_device_get_device_type: 
assertion 'NM_IS_DEVICE (self)' failed


The interface 'virbr0' also shows up in nm-applet's display, which was never 
the case before.  This interface has always been managed by the libvirt-bin 
startup scripts (which causes problems of its own, since a 'service libvirt-bin 
restart' does not reinitialize the network and a 'service libvirt-bin stop' 
does not stop it).  The bring-up of virbr0 appears to still be handled by 
libvirt-bin, not by NM; but somehow NM has a device configuration for it and is 
downing the interface on service stop - and not restoring it on service start.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: network-manager 0.9.10.0-4ubuntu13
ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
Uname: Linux 3.19.0-7-generic x86_64
ApportVersion: 2.17-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Apr  1 15:48:28 2015
InstallationDate: Installed on 2010-09-24 (1650 days ago)
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
IpRoute:
 default via 192.168.15.1 dev wlan2  proto static  metric 1024 
 169.254.0.0/16 dev virbr0  scope link  metric 1000 
 192.168.15.0/24 dev wlan2  proto kernel  scope link  src 192.168.15.71 
 192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1 
 207.224.24.209 via 192.168.15.1 dev wlan2  proto dhcp  metric 10
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WWanEnabled=true
SourcePackage: network-manager
UpgradeStatus: Upgraded to vivid on 2014-12-06 (116 days ago)
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: 
Error: Object 'nm' is unknown, try 'nmcli help'.

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


** Tags: amd64 apport-bug vivid

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

Title:
  NM in vivid tries to take over my libvirt bridge, deconfigures its
  address

Status in network-manager package in Ubuntu:
  New

Bug description:
  Over the past couple of months in vivid, from time to time I have
  noticed that my virbr0 interface, which is set up and managed by
  libvirt-bin, has been in an "up" state with no IP address configured.

  As I don't use VMs on my laptop very frequently, I don't know when the
  problem started and I don't know when exactly the problem is being
  triggered.  But a search through logs shows the following:

  Mar 16 16:48:56 virgil systemd[1]: Stopping Network Manager...
  [...]
  Mar 16 16:48:56 virgil NetworkManager[32588]:  (virbr0): devic

[Touch-packages] [Bug 1434579] Re: Unable to install VirtualBox Guest Service in 15.04

2015-04-01 Thread Martin Wimpress

Yes, the multiverse enabled.

I've just installed the Ubuntu MATE daily in a clean VM and confirm that
multiverse is enabled by default.

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

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

Title:
  Unable to install VirtualBox Guest Service in 15.04

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  It is not longer possible to select VirtualBox Guest Service in 15.04.
  The only options available are:

* Continue using a manually install driver
* Do not use the device

  The option 'Using x86 virtualisation solution - guest addition module'
  is no longer selectable. See the attached screen shot. This is from a
  fresh install of Ubuntu MATE 15.04 daily (20th March) and no drivers
  have been manually installed.

  In light of the Virtualbox issue where new installs on Virtualbox have
  a resolution of 640x480
  (https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1368784/)
  this is going to be a frustration for many users.

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

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

[Touch-packages] [Bug 1429695] Re: Import broken for ContentTypes without default apps

** Branch linked: lp:ubuntu/vivid-proposed/content-hub

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

Title:
  Import broken for ContentTypes without default apps

Status in Content sharing/picking infrastructure and service:
  Confirmed
Status in content-hub package in Ubuntu:
  New

Bug description:
  The content hub is broken when trying to import a content type for
  which there is no default handler (for example, ContentType.EBooks).
  When you try to import from the default provider, the
  ContentTransferHint will open and start a spinner, but nothing else
  happens.  If you try to choose a provider, you at least get an error
  message stating that there are no providers.

  This is seen on a device running vivid/devel r1.

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

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

[Touch-packages] [Bug 1438935] Re: ? just got the something wrong procedure

2015-04-01 Thread Jim Leinweber

logged off first user, logged in a second user, just after a round of
apt-get {update,dist-upgrade,clean,autoremove} and rebooting onto kernel
3.19.0-11-generic.

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

Title:
  ? just got the something wrong procedure

Status in upstart package in Ubuntu:
  New

Bug description:
  no forther information at hand

  ProblemType: RecoverableProblem
  DistroRelease: Ubuntu 15.04
  Package: upstart 1.13.2-0ubuntu10
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic i686
  ApportVersion: 2.17-0ubuntu1
  Architecture: i386
  Date: Wed Apr  1 00:13:26 2015
  DuplicateSignature: indicator-session-unknown-user-error
  ExecutablePath: /sbin/upstart
  InstallationDate: Installed on 2015-03-31 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta i386 (20150326)
  ProcCmdline: upstart --user --startup-event indicator-services-start
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/false
  SourcePackage: upstart
  UpgradeStatus: No upgrade log present (probably fresh install)
  UpstartBugCategory: Session
  UpstartRunningSessionCount: 2
  UpstartRunningSystemVersion: Error: command ['initctl', '--system', 
'version'] failed with exit code 1: initctl: Name "com.ubuntu.Upstart" does not 
exist
  UserGroups:
   
  icon_file: (null)
  is_current_user: false
  is_logged_in: false
  real_name: (null)
  uid: 0
  user_name: (null)

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

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

[Touch-packages] [Bug 1211514] Re: Shutdowns fail to finish if laptop lid is closed before completely shutdown

2015-04-01 Thread Andy Carver

Well that was embarrassing...  -p

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

Title:
  Shutdowns fail to finish if laptop lid is closed before completely
  shutdown

Status in systemd-shim package in Ubuntu:
  Fix Released
Status in systemd-shim source package in Saucy:
  Fix Released
Status in systemd-shim source package in Trusty:
  Fix Released

Bug description:
  Only seen in a ubuntu (unity) session, others report gnome sessions

  SRU INFORMATION
  

  TEST CASE on laptop:
   - Shutdown machine from session indicator, close laptop lid right after 
selecting shutdown or reboot from pop up window.
   - What should happen: lid close gets ignored and machine should complete 
shutdown process
  - What does happen: machine gets suspended until the laptop lid is re-opened, 
then it either completes the shutdown (if the lid close happened early enough), 
or hangs eternally

  FIX: https://github.com/desrt/systemd-shim/commit/6c65a113 and
  https://github.com/desrt/systemd-shim/commit/b8f324dae5 (both are
  needed)

  REGRESSION POTENTIAL: A broken systemd-shim can potentially completely
  prevent shutdown, reboot, suspend, hibernate. This code has been
  tested with all scenarios, with both doing suspend/lid close during
  normal operation, and during shutdown (at which point lid close is now
  ignored).

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.0+13.10.20130812.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-1.4-generic 3.11.0-rc4
  Uname: Linux 3.11.0-1-generic x86_64
  ApportVersion: 2.12-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Mon Aug 12 17:01:09 2013
  InstallationDate: Installed on 2013-08-07 (4 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130803)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1211514] Re: Shutdowns fail to finish if laptop lid is closed before completely shutdown

2015-04-01 Thread Andy Carver

Update. 
Ignored all lid items in file
Shuts down via VNC..

Am I using the correct Unix command?

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

Title:
  Shutdowns fail to finish if laptop lid is closed before completely
  shutdown

Status in systemd-shim package in Ubuntu:
  Fix Released
Status in systemd-shim source package in Saucy:
  Fix Released
Status in systemd-shim source package in Trusty:
  Fix Released

Bug description:
  Only seen in a ubuntu (unity) session, others report gnome sessions

  SRU INFORMATION
  

  TEST CASE on laptop:
   - Shutdown machine from session indicator, close laptop lid right after 
selecting shutdown or reboot from pop up window.
   - What should happen: lid close gets ignored and machine should complete 
shutdown process
  - What does happen: machine gets suspended until the laptop lid is re-opened, 
then it either completes the shutdown (if the lid close happened early enough), 
or hangs eternally

  FIX: https://github.com/desrt/systemd-shim/commit/6c65a113 and
  https://github.com/desrt/systemd-shim/commit/b8f324dae5 (both are
  needed)

  REGRESSION POTENTIAL: A broken systemd-shim can potentially completely
  prevent shutdown, reboot, suspend, hibernate. This code has been
  tested with all scenarios, with both doing suspend/lid close during
  normal operation, and during shutdown (at which point lid close is now
  ignored).

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.0+13.10.20130812.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-1.4-generic 3.11.0-rc4
  Uname: Linux 3.11.0-1-generic x86_64
  ApportVersion: 2.12-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Mon Aug 12 17:01:09 2013
  InstallationDate: Installed on 2013-08-07 (4 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130803)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1436733] Re: /usr/sbin/cups-browsed:11:g_slist_foreach:g_slist_free_full:g_source_unref_internal:g_main_dispatch:g_main_context_dispatch

Looking at the crashes reports in the error tracker we can see these
versions of libglib2.0-0 were installed on the crashing systems:

2.43.3-1: 1
2.43.92-1: 227
2.43.91-1: 1
2.44.0-1: 5
2.42.1-1~ubuntu1: 2

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

Title:
  /usr/sbin/cups-
  
browsed:11:g_slist_foreach:g_slist_free_full:g_source_unref_internal:g_main_dispatch:g_main_context_dispatch

Status in cups-filters package in Ubuntu:
  Incomplete
Status in glib2.0 package in Ubuntu:
  Incomplete

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding cups-filters.  This problem was most recently seen with
  version 1.0.67-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/3290d48cdb8a0877a97dd5501f2edc6c1b1d705b
  contains more details.

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

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

[Touch-packages] [Bug 1439186] Re: [REGRESSION] Predictor tag fails to be written correctly

2015-04-01 Thread Mathew Hodson

** Tags added: regression-update

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

Title:
  [REGRESSION] Predictor tag fails to be written correctly

Status in tiff package in Ubuntu:
  Confirmed
Status in tiff source package in Lucid:
  Fix Released
Status in tiff source package in Precise:
  Fix Released
Status in tiff source package in Trusty:
  Fix Released
Status in tiff source package in Utopic:
  Fix Released
Status in tiff source package in Vivid:
  Confirmed

Bug description:
  The patch debian/patches/CVE-2014-8128-5.patch appears to break saving TIFF 
files with compression predictor.
  It seems the data is correctly saved, but the "predictor" tag is not, which 
prevents reading the data correctly again.

  This happens both on precise (release 3.9.5-2ubuntu1.7) and on trusty
  (release 4.0.3-7ubuntu0.2).

  I'm attaching an example TIFF file "small.tiff" for showing the
  behaviour. It is compressed in LZW without predictor, so it is
  written/read correctly.

  However, if you recompress it with this command, the error happens:
  $ tiffcp -c lzw:2 small.tiff small-c2.tiff

  Then displaying it in eog shows a completely different image. Tiffinfo 
indicates a problem with the tags:
  $ tiffinfo small-c2-bad.tiff | grep Predictor
  TIFFReadDirectory: Warning, small-c2-bad.tiff: unknown field with tag 8224 
(0x2020) encountered.

  Comparing it with a good version of the file (generated with a previous 
version of libtiff):
  $ tiffinfo small-c2-good.tiff | grep Predictor
Predictor: horizontal differencing 2 (0x2)

  $ tiffcmp small-c2.tiff small-c2-good.tiff 
  TIFFReadDirectory: Warning, small-c2-bad.tiff: unknown field with tag 8224 
(0x2020) encountered.
  Predictor tag appears only in small-c2-good.tiff

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

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

[Touch-packages] [Bug 1211514] Re: Shutdowns fail to finish if laptop lid is closed before completely shutdown

2015-04-01 Thread Andy Carver

It appears it to be a partial workaround. Shut down command via ssh
halted.  Reboot command via ssh appears successful.

It may have been because of a zombie. They eat celeron brains for
breakfast.

I'll confirm when I can.

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

Title:
  Shutdowns fail to finish if laptop lid is closed before completely
  shutdown

Status in systemd-shim package in Ubuntu:
  Fix Released
Status in systemd-shim source package in Saucy:
  Fix Released
Status in systemd-shim source package in Trusty:
  Fix Released

Bug description:
  Only seen in a ubuntu (unity) session, others report gnome sessions

  SRU INFORMATION
  

  TEST CASE on laptop:
   - Shutdown machine from session indicator, close laptop lid right after 
selecting shutdown or reboot from pop up window.
   - What should happen: lid close gets ignored and machine should complete 
shutdown process
  - What does happen: machine gets suspended until the laptop lid is re-opened, 
then it either completes the shutdown (if the lid close happened early enough), 
or hangs eternally

  FIX: https://github.com/desrt/systemd-shim/commit/6c65a113 and
  https://github.com/desrt/systemd-shim/commit/b8f324dae5 (both are
  needed)

  REGRESSION POTENTIAL: A broken systemd-shim can potentially completely
  prevent shutdown, reboot, suspend, hibernate. This code has been
  tested with all scenarios, with both doing suspend/lid close during
  normal operation, and during shutdown (at which point lid close is now
  ignored).

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.0+13.10.20130812.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-1.4-generic 3.11.0-rc4
  Uname: Linux 3.11.0-1-generic x86_64
  ApportVersion: 2.12-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Mon Aug 12 17:01:09 2013
  InstallationDate: Installed on 2013-08-07 (4 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130803)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1417658] Re: apparmor denied operation file_inherit from networkmanager when using HWE kernel

2015-04-01 Thread Bernhard

Tested packages: amd64
isc-dhcp-client  4.2.4-7ubuntu12.1
isc-dhcp-common   4.2.4-7ubuntu12.1

with kernels: amd64
vivid-lts  3.19.0-10.10
utopic-lts 3.16.0- 34.27

No "apparmor="DENIED" operation"-messages anymore => the patched
packages work.

Thank you for your support!
Best regards, Bernhard

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

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

Title:
  apparmor denied operation file_inherit from networkmanager when using
  HWE kernel

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Trusty:
  Fix Committed
Status in isc-dhcp source package in Vivid:
  Fix Released

Bug description:
  [Impact]
  AppArmor denials appear in dhclient when using using HWE kernel on 14.04. 
This can result in incorrect dhcp operation on client systems. The fix is to 
add these rules:
network inet dgram,
network inet6 dgram,

  to the dhclient profile for nm-dhcp-client.action and dhclient-script,
  like we did in 4.2.4-7ubuntu14.

  [Test Case]
  Install HWE kernel and use network manager to obtain an IP address.

  [Regression Potential]
  Extremely low since the update only adds access that dhclient didn't have.

  Original description:

  Hallo,

  on Kubuntu 14.04.x dmesg shows me the following apparmor messages;

  Is this normal or is this a security issue together with network-
  manager?

  [   16.171766] audit: type=1400 audit(1422595680.679:68): apparmor="DENIED" 
operation="file_inherit" 
profile="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=2229 
comm="nm-dhcp-client." lport=10320 family="inet" sock_type="dgram" protocol=17
  [   16.171772] audit: type=1400 audit(1422595680.679:69): apparmor="DENIED" 
operation="file_inherit" 
profile="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=2229 
comm="nm-dhcp-client." lport=21985 family="inet6" sock_type="dgram" protocol=17
  [   16.199936] audit: type=1400 audit(1422595680.707:70): apparmor="DENIED" 
operation="file_inherit" 
profile="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=2246 
comm="nm-dhcp-client." lport=10320 family="inet" sock_type="dgram" protocol=17
  [   16.199943] audit: type=1400 audit(1422595680.707:71): apparmor="DENIED" 
operation="file_inherit" 
profile="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=2246 
comm="nm-dhcp-client." lport=21985 family="inet6" sock_type="dgram" protocol=17
  [   16.201369] audit: type=1400 audit(1422595680.707:72): apparmor="DENIED" 
operation="file_inherit" 
profile="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=2248 
comm="nm-dhcp-client." lport=10320 family="inet" sock_type="dgram" protocol=17
  [   16.201379] audit: type=1400 audit(1422595680.707:73): apparmor="DENIED" 
operation="file_inherit" 
profile="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=2248 
comm="nm-dhcp-client." lport=21985 family="inet6" sock_type="dgram" protocol=17
  [   17.206342] audit: type=1400 audit(1422595681.711:74): apparmor="DENIED" 
operation="file_inherit" 
profile="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=2468 
comm="nm-dhcp-client." lport=10320 family="inet" sock_type="dgram" protocol=17
  [   17.206349] audit: type=1400 audit(1422595681.711:75): apparmor="DENIED" 
operation="file_inherit" 
profile="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=2468 
comm="nm-dhcp-client." lport=21985 family="inet6" sock_type="dgram" protocol=17

  When I logon to KDE, KDE hangs sometimes  for 3sec at the login-
  process , when there is no internet connection (DSL modem did not
  dial-in yet).

  Thanks for your help!
  Best regards, Bernhard

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

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

[Touch-packages] [Bug 1439041] Re: Address-Book lists contacts from second google account without permission

2015-04-01 Thread Seth Arnold

** Tags added: bq

** Information type changed from Public to Public Security

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

Title:
  Address-Book lists contacts from second google account without
  permission

Status in address-book-app package in Ubuntu:
  New

Bug description:
  Hello,
  I am using the BQ phone. I have two google accounts registered in my 
online-accounts. The first account has access to all applications listed in 
online accounts. The second account is supposed to deliver only the calendar 
events of my wife. Hence I enabled for the second account only access to 
"calendar" and "com.ubuntu.developer...". 

  However my address-book lists all contacts of my wife even though no
  access is granted in online accounts.

  The behavior not only affects the usability but is also a security
  issue.

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

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

[Touch-packages] [Bug 1439136] Re: Messages readable when phone locked..

2015-04-01 Thread Seth Arnold

** Tags added: bq

** Information type changed from Private Security to Public Security

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

Title:
  Messages readable when phone locked..

Status in indicator-messages package in Ubuntu:
  New

Bug description:
  When the phone is in a locked state swiping down you are able to get
  access to the notification tab,

  from here you are able to read recent SMS messages -- which is all
  well and good if you want quick access to your text messages but you
  are also able to reply to the text message without unlocking the
  phone.

  in summary;

  You are able to read and send SMS messages without unlocking the
  phone.

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

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

[Touch-packages] [Bug 1366418] Re: Bluetooth BCM43142A0 doesn’t work

2015-04-01 Thread Pilot6

This fix is already in 'proposed' kernel. You do not need to use mine
any more.

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

Title:
  Bluetooth BCM43142A0 doesn’t work

Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  I’ve installed ubuntu 14.04 and my computer’s builtin bluetooth
  (computer is an Asus x550ln) doesn’t work at all. Bluetooth is not
  displayed in the menu bar, if I open the bluetooth UI and switch on,
  nothing happens and the result of “hcitool dev” is empty.

  I have tried to install the windows driver with ndiswrapper, and the
  bluetooth device seems to be detected as an usb bluetooth device but
  still not working. I then add the device to the bluetooth usb device
  and was able to activate bluetooth in the UI but it does not detect
  any other devices (I’ve tested with a smartphone).

  The driver I have installed can be found in asus page =>
  http://www.asus.com/fr/Notebooks_Ultrabooks/X550LN/HelpDesk_Download/
  Select Windows OS, then “bluetooth” section, take the Broadcom driver
  (should be the first one).

  If you extract this archive, you will find a file named “bcbtums-
  win8x64-brcm.inf” which I installed using the following command:

  ndiswrapper -i bcbtums-win8x64-brcm.inf

  Then, the result of “ndiswrapper -l” is:

  bcbtums-win8x64-brcm : driver installed
device (04CA:2006) present

  in usb-devices, I find a device which was not present before
  installation (I might have activated btusb before on this paste):

  T:  Bus=02 Lev=01 Prnt=01 Port=05 Cnt=02 Dev#=  3 Spd=12  MxCh= 0
  D:  Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
  P:  Vendor=04ca ProdID=2006 Rev=01.12
  S:  Manufacturer=Broadcom Corp
  S:  Product=BCM43142A0
  S:  SerialNumber=B8EE6593D989
  C:  #Ifs= 4 Cfg#= 1 Atr=e0 MxPwr=0mA
  I:  If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
  I:  If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
  I:  If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
  I:  If#= 3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=01 Driver=(none)

  then, “echo "04ca 2006" > /sys/bus/usb/drivers/btusb/new_id”, and I
  can switch usb on, but no device will be detected and I’ve found this
  in the dmesg:

  [2200.843126] Bluetooth: hci0 command 0x1003 tx timeout

  which looks pretty much like a “bluetooth not working” message which I
  don’t understand in details.

  I leave here my full dmesg:

  [0.253889] NetLabel:  domain hash size = 128
  [0.253890] NetLabel:  protocols = UNLABELED CIPSOv4
  [0.253901] NetLabel:  unlabeled traffic allowed by default
  [0.253959] hpet0: at MMIO 0xfed0, IRQs 2, 8, 0, 0, 0, 0, 0, 0
  [0.253965] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
  [0.255995] Switched to clocksource hpet
  [0.260468] AppArmor: AppArmor Filesystem Enabled
  [0.260488] pnp: PnP ACPI init
  [0.260500] ACPI: bus type PNP registered
  [0.260592] system 00:00: [mem 0xfed4-0xfed44fff] has been reserved
  [0.260596] system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
  [0.260642] pnp 00:01: [dma 4]
  [0.260658] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
  [0.260678] pnp 00:02: Plug and Play ACPI device, IDs INT0800 (active)
  [0.260782] pnp 00:03: Plug and Play ACPI device, IDs PNP0103 (active)
  [0.260924] system 00:04: [io  0x0680-0x069f] has been reserved
  [0.260927] system 00:04: [io  0x] has been reserved
  [0.260928] system 00:04: [io  0x] has been reserved
  [0.260930] system 00:04: [io  0x] has been reserved
  [0.260932] system 00:04: [io  0x1c00-0x1cfe] has been reserved
  [0.260934] system 00:04: [io  0x1d00-0x1dfe] has been reserved
  [0.260935] system 00:04: [io  0x1e00-0x1efe] has been reserved
  [0.260937] system 00:04: [io  0x1f00-0x1ffe] has been reserved
  [0.260939] system 00:04: [io  0x1800-0x18fe] could not be reserved
  [0.260941] system 00:04: [io  0x164e-0x164f] has been reserved
  [0.260943] system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
  [0.260969] pnp 00:05: Plug and Play ACPI device, IDs PNP0b00 (active)
  [0.261012] system 00:06: [io  0x1854-0x1857] has been reserved
  [0.261014] system 00:06: Plug and Play ACPI device, IDs INT3f0d PNP0c02 
(active)
  [0.261059] system 00:07: [io  0x04d0-0x04d1] has been reserved
  [0.261061] system 00:07: Plug and Play ACPI device, IDs PNP0c02 (active)
  [0.261089] system 00:08: [io  0x0240-0x0259] has been reserved
  [0.261091] system 00:08: Plug and Play ACPI device, IDs PNP0c02 (active)
  [0.261144] pnp 00:09: Plug and Play ACPI device, IDs FLT0101 SYN0a00 
SYN0002 PNP0f03 PNP0f13 PNP0f12 (active)

[Touch-packages] [Bug 1439384] Re: systemd-logind crashed with SIGABRT

2015-04-01 Thread Apport retracing service

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

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 #1429544, 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/1439384/+attachment/4363371/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1429544
   systemd-logind crashed with SIGABRT in session_start_scope()

** Tags removed: need-amd64-retrace

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

Title:
  systemd-logind crashed with SIGABRT

Status in systemd package in Ubuntu:
  New

Bug description:
  15.04
  upgrade

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-5ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Apr  1 22:23:09 2015
  ExecutablePath: /lib/systemd/systemd-logind
  MachineType: Acer Aspire V5-551
  ProcCmdline: /lib/systemd/systemd-logind
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic.efi.signed 
root=UUID=bdba8918-495e-47cf-bc7c-8dc076ec2212 ro console=tty2 noplymouth 
acpi_backlight=vendor nomdmonddf nomdmonisw crashkernel=384M-:128M
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: systemd-logind crashed with SIGABRT
  UpgradeStatus: Upgraded to vivid on 2015-03-31 (1 days ago)
  UserGroups:
   
  dmi.bios.date: 04/19/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Havok
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.16:bd04/19/2013:svnAcer:pnAspireV5-551:pvrV2.16:rvnAcer:rnHavok:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire V5-551
  dmi.product.version: V2.16
  dmi.sys.vendor: Acer

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

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

[Touch-packages] [Bug 1437538] Re: Battery Applet appears in English with Gnome in Ubuntu 12.04

2015-04-01 Thread Alfonso

Help me please!!!

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

Title:
  Battery Applet appears in English with Gnome in Ubuntu 12.04

Status in indicator-power package in Ubuntu:
  New

Bug description:
  Use Ubuntu 12.04 on a Toshiba NB500. I use the Gnome desktop environment, but 
I found a bug:
  The battery applet appears in English, but with Unity appears in Spanish, but 
I still use Gnome !. So I ask you traduzcais battery applet to Spanish. If you 
ask me I missing some information. a greeting

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

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

[Touch-packages] [Bug 1366418] Re: Bluetooth BCM43142A0 doesn’t work

2015-04-01 Thread ghortor

Works fine ! \o/

I followed the instructions here =>
https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel to build the kernel
with the diff posted by Pilot6 (useful if you are using ubuntu :D).

I also “apt-get purged” my current linux-image et linux-headers so that
they could be fully replaced by the one I’ve built. Rebooted and could
finally use the bluetooth device of my computer..

Thanks very much everyone, (special thanks to Pilot6 :-) ).

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

Title:
  Bluetooth BCM43142A0 doesn’t work

Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  I’ve installed ubuntu 14.04 and my computer’s builtin bluetooth
  (computer is an Asus x550ln) doesn’t work at all. Bluetooth is not
  displayed in the menu bar, if I open the bluetooth UI and switch on,
  nothing happens and the result of “hcitool dev” is empty.

  I have tried to install the windows driver with ndiswrapper, and the
  bluetooth device seems to be detected as an usb bluetooth device but
  still not working. I then add the device to the bluetooth usb device
  and was able to activate bluetooth in the UI but it does not detect
  any other devices (I’ve tested with a smartphone).

  The driver I have installed can be found in asus page =>
  http://www.asus.com/fr/Notebooks_Ultrabooks/X550LN/HelpDesk_Download/
  Select Windows OS, then “bluetooth” section, take the Broadcom driver
  (should be the first one).

  If you extract this archive, you will find a file named “bcbtums-
  win8x64-brcm.inf” which I installed using the following command:

  ndiswrapper -i bcbtums-win8x64-brcm.inf

  Then, the result of “ndiswrapper -l” is:

  bcbtums-win8x64-brcm : driver installed
device (04CA:2006) present

  in usb-devices, I find a device which was not present before
  installation (I might have activated btusb before on this paste):

  T:  Bus=02 Lev=01 Prnt=01 Port=05 Cnt=02 Dev#=  3 Spd=12  MxCh= 0
  D:  Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
  P:  Vendor=04ca ProdID=2006 Rev=01.12
  S:  Manufacturer=Broadcom Corp
  S:  Product=BCM43142A0
  S:  SerialNumber=B8EE6593D989
  C:  #Ifs= 4 Cfg#= 1 Atr=e0 MxPwr=0mA
  I:  If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
  I:  If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
  I:  If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
  I:  If#= 3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=01 Driver=(none)

  then, “echo "04ca 2006" > /sys/bus/usb/drivers/btusb/new_id”, and I
  can switch usb on, but no device will be detected and I’ve found this
  in the dmesg:

  [2200.843126] Bluetooth: hci0 command 0x1003 tx timeout

  which looks pretty much like a “bluetooth not working” message which I
  don’t understand in details.

  I leave here my full dmesg:

  [0.253889] NetLabel:  domain hash size = 128
  [0.253890] NetLabel:  protocols = UNLABELED CIPSOv4
  [0.253901] NetLabel:  unlabeled traffic allowed by default
  [0.253959] hpet0: at MMIO 0xfed0, IRQs 2, 8, 0, 0, 0, 0, 0, 0
  [0.253965] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
  [0.255995] Switched to clocksource hpet
  [0.260468] AppArmor: AppArmor Filesystem Enabled
  [0.260488] pnp: PnP ACPI init
  [0.260500] ACPI: bus type PNP registered
  [0.260592] system 00:00: [mem 0xfed4-0xfed44fff] has been reserved
  [0.260596] system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
  [0.260642] pnp 00:01: [dma 4]
  [0.260658] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
  [0.260678] pnp 00:02: Plug and Play ACPI device, IDs INT0800 (active)
  [0.260782] pnp 00:03: Plug and Play ACPI device, IDs PNP0103 (active)
  [0.260924] system 00:04: [io  0x0680-0x069f] has been reserved
  [0.260927] system 00:04: [io  0x] has been reserved
  [0.260928] system 00:04: [io  0x] has been reserved
  [0.260930] system 00:04: [io  0x] has been reserved
  [0.260932] system 00:04: [io  0x1c00-0x1cfe] has been reserved
  [0.260934] system 00:04: [io  0x1d00-0x1dfe] has been reserved
  [0.260935] system 00:04: [io  0x1e00-0x1efe] has been reserved
  [0.260937] system 00:04: [io  0x1f00-0x1ffe] has been reserved
  [0.260939] system 00:04: [io  0x1800-0x18fe] could not be reserved
  [0.260941] system 00:04: [io  0x164e-0x164f] has been reserved
  [0.260943] system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
  [0.260969] pnp 00:05: Plug and Play ACPI device, IDs PNP0b00 (active)
  [0.261012] system 00:06: [io  0x1854-0x1857] has been reserved
  [0.261014] system 00:06: Plug and Play ACPI device, IDs INT3f0d PNP0c02 
(active)
  [0.261059] system 00:07: [io  0x04d0-0x04

[Touch-packages] [Bug 1439384] [NEW] systemd-logind crashed with SIGABRT

2015-04-01 Thread Marcos K

Public bug reported:

15.04
upgrade

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: systemd 219-5ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
Uname: Linux 3.19.0-10-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.17-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Wed Apr  1 22:23:09 2015
ExecutablePath: /lib/systemd/systemd-logind
MachineType: Acer Aspire V5-551
ProcCmdline: /lib/systemd/systemd-logind
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic.efi.signed 
root=UUID=bdba8918-495e-47cf-bc7c-8dc076ec2212 ro console=tty2 noplymouth 
acpi_backlight=vendor nomdmonddf nomdmonisw crashkernel=384M-:128M
Signal: 6
SourcePackage: systemd
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: systemd-logind crashed with SIGABRT
UpgradeStatus: Upgraded to vivid on 2015-03-31 (1 days ago)
UserGroups:
 
dmi.bios.date: 04/19/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V2.16
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Havok
dmi.board.vendor: Acer
dmi.board.version: Type2 - A01 Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.16:bd04/19/2013:svnAcer:pnAspireV5-551:pvrV2.16:rvnAcer:rnHavok:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: Aspire V5-551
dmi.product.version: V2.16
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-crash need-amd64-retrace vivid

** Information type changed from Private to Public

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

Title:
  systemd-logind crashed with SIGABRT

Status in systemd package in Ubuntu:
  New

Bug description:
  15.04
  upgrade

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-5ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Apr  1 22:23:09 2015
  ExecutablePath: /lib/systemd/systemd-logind
  MachineType: Acer Aspire V5-551
  ProcCmdline: /lib/systemd/systemd-logind
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic.efi.signed 
root=UUID=bdba8918-495e-47cf-bc7c-8dc076ec2212 ro console=tty2 noplymouth 
acpi_backlight=vendor nomdmonddf nomdmonisw crashkernel=384M-:128M
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: systemd-logind crashed with SIGABRT
  UpgradeStatus: Upgraded to vivid on 2015-03-31 (1 days ago)
  UserGroups:
   
  dmi.bios.date: 04/19/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Havok
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.16:bd04/19/2013:svnAcer:pnAspireV5-551:pvrV2.16:rvnAcer:rnHavok:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire V5-551
  dmi.product.version: V2.16
  dmi.sys.vendor: Acer

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

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

[Touch-packages] [Bug 1438360] Re: PCI/internal sound card not detected

This is from /var/log/syslog:

File: syslog
 

Apr  1 10:11:34 headadmin-desktop rsyslogd: [origin software="rsyslogd" 
swVersion="7.4.4" x-pid="536" x-info="http://www.rsyslog.com"$
Apr  1 10:11:38 headadmin-desktop anacron[795]: Job `cron.daily' terminated
Apr  1 10:11:38 headadmin-desktop anacron[795]: Normal exit (1 job run)
Apr  1 10:17:01 headadmin-desktop CRON[2820]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
Apr  1 11:17:01 headadmin-desktop CRON[2976]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
Apr  1 12:17:01 headadmin-desktop CRON[3263]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)

--
sudo aplay -l gives this output:

headadmin@headadmin-desktop:/var/log$ sudo aplay -l
[sudo] password for headadmin: 
aplay: device_list:268: no soundcards found...

---
I also re-installed the alsa sound here according to another post and this was 
the result:  

headadmin@headadmin-desktop:/proc$ sudo apt-get install alsa-base alsa-utils 
alsa-tools libasound2 libasound2-plugins
Reading package lists... Done
Building dependency tree   
Reading state information... Done
alsa-base is already the newest version.
alsa-utils is already the newest version.
libasound2 is already the newest version.
libasound2-plugins is already the newest version.
libasound2-plugins set to manually installed.
The following packages were automatically installed and are no longer required:
  libapparmor-perl linux-headers-3.16.0-30 linux-headers-3.16.0-30-generic
  linux-image-3.16.0-30-generic linux-image-extra-3.16.0-30-generic
Use 'apt-get autoremove' to remove them.
The following NEW packages will be installed:
  alsa-toolsheadadmin@headadmin-desktop:/proc$ sudo apt-get install alsa-base 
alsa-utils alsa-tools libasound2 libasound2-plugins
Reading package lists... Doneheadadmin@headadmin-desktop:/proc$ sudo apt-get 
install alsa-base alsa-utils alsa-tools libasound2 libasound2-plugins
Reading package lists... Done
Building dependency tree   
Reading state information... Done
alsa-base is already the newest version.
alsa-utils is already the newest version.
libasound2 is already the newest version.
libasound2-plugins is already the newest version.
libasound2-plugins set to manually installed.
The following packages were automatically installed and are no longer required:
  libapparmor-perl linux-headers-3.16.0-30 linux-headers-3.16.0-30-generic
  linux-image-3.16.0-30-generic linux-image-extra-3.16.0-30-generic
Use 'apt-get autoremove' to remove them.
The following NEW packages will be installed:
  alsa-tools
0 upgraded, 1 newly installed, 0 to remove and 12 not upgraded.
Need to get 50.4 kB of archives.
After this operation, 216 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://us.archive.ubuntu.com/ubuntu/ trusty/universe alsa-tools amd64 
1.0.27-2ubuntu3 [50.4 kB]
Fetched 50.4 kB in 0s (104 kB/s)  
Selecting previously unselected package alsa-tools.
(Reading database ... 225035 files and directories currently installed.)
Preparing to unpack .../alsa-tools_1.0.27-2ubuntu3_amd64.deb ...
Unpacking alsa-tools (1.0.27-2ubuntu3) ...headadmin@headadmin-desktop:/proc$ 
sudo apt-get install alsa-base alsa-utils alsa-tools libasound2 
libasound2-plugins
Reading package lists... Done
Building dependency tree   
Reading state information... Done
alsa-base is already the newest version.
alsa-utils is already the newest version.
libasound2 is already the newest version.
libasound2-plugins is already the newest version.
libasound2-plugins set to manually installed.
The following packages were automatically installed and are no longer required:
  libapparmor-perl linux-headers-3.16.0-30 linux-headers-3.16.0-30-generic
  linux-image-3.16.0-30-generic linux-image-extra-3.16.0-30-generic
Use 'apt-get autoremove' to remove them.
The following NEW packages will be installed:
  alsa-tools
0 upgraded, 1 newly installed, 0 to remove and 12 not upgraded.
Need to get 50.4 kB of archives.
After this operation, 216 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://us.archive.ubuntu.com/ubuntu/ trusty/universe alsa-tools amd64 
1.0.27-2ubuntu3 [50.4 kB]
Fetched 50.4 kB in 0s (104 kB/s)  
Selecting previously unselected package alsa-tools.
(Reading database ... 225035 files and directories currently installed.)
Preparing to unpack .../alsa-tools_1.0.27-2ubuntu3_amd64.deb ...
Unpacking alsa-tools (1.0.27-2ubuntu3) ...
Processing triggers for man-db (2.6.7.1-1ubuntu1) ...
Setting up alsa-tools (1.0.27-2ubuntu3) ...headadmin@headadmin-desktop:/proc$ 
sudo apt-get install alsa-base alsa-utils alsa-tools libasound2 
libasound2-plugins
Reading package lists... Done
Building dependency tree

[Touch-packages] [Bug 1370008] Re: url-dispatcher-bad-url

2015-04-01 Thread Olivier Tilloy

This is not a crash, it’s a recoverable problem. It seems to happen when
trying to open market:// URLs in the browser (from pages that
incorrectly assume that they are running on an android device).

I can easily reproduce the issue by opening a test page in the browser
that contains this code:

  
   
click me
   
  

When clicking this link, I’m seeing the following error in the browser’s
log:

  ** (process:14120): WARNING **: Unable to dispatch url
'market://details?id=com.google.android.voicesearch':GDBus.Error:com.canonical.URLDispatcher.BadURL:
URL 'market://details?id=com.google.android.voicesearch' is not
handleable by the URL Dispatcher


We could probably have a default application that registers as a handler for 
this type of URLs and informs the user that android applications are not 
compatible with Ubuntu (adding an ubuntu-ux task to get input from the design 
team).

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

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

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

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

Title:
  url-dispatcher-bad-url

Status in Ubuntu UX bugs:
  New
Status in gallery-app package in Ubuntu:
  Invalid
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding gallery-app.  This problem was most recently seen with
  version 13.10.0+14.10.20140908.1-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/b1f16000af092461aeb85b5c7edfd3dc3f1271c8
  contains more details.

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

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

[Touch-packages] [Bug 1437803] Re: kubuntu 15.04 ubuntu-bug broken - File "/usr/share/apport/apport-kde", line 43 from PyQt5 uic ^ SyntaxError: invalid syntax

2015-04-01 Thread yossarian_uk

Thank you !

All fixed now.

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

Title:
  kubuntu 15.04 ubuntu-bug broken -  File "/usr/share/apport/apport-
  kde", line 43 from PyQt5 uic   ^ SyntaxError: invalid syntax

Status in apport package in Ubuntu:
  Fix Released

Bug description:
  Using 15.04 (kubuntu amd64) I am unable to use ubuntu-bug.

  i.e

  
--
  morgan@morgan-MS-7758:~$ ubuntu-bug apport-kde 
File "/usr/share/apport/apport-kde", line 43
  from PyQt5 uic
   ^
  SyntaxError: invalid syntax
  
--

  seeing as its the devel versio the bug-reporting tool is of fairly
  high importance.

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

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

[Touch-packages] [Bug 1439186] Re: [REGRESSION] Predictor tag fails to be written correctly

** Branch linked: lp:ubuntu/precise-security/tiff

** Branch linked: lp:ubuntu/utopic-security/tiff

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

Title:
  [REGRESSION] Predictor tag fails to be written correctly

Status in tiff package in Ubuntu:
  Confirmed
Status in tiff source package in Lucid:
  Fix Released
Status in tiff source package in Precise:
  Fix Released
Status in tiff source package in Trusty:
  Fix Released
Status in tiff source package in Utopic:
  Fix Released
Status in tiff source package in Vivid:
  Confirmed

Bug description:
  The patch debian/patches/CVE-2014-8128-5.patch appears to break saving TIFF 
files with compression predictor.
  It seems the data is correctly saved, but the "predictor" tag is not, which 
prevents reading the data correctly again.

  This happens both on precise (release 3.9.5-2ubuntu1.7) and on trusty
  (release 4.0.3-7ubuntu0.2).

  I'm attaching an example TIFF file "small.tiff" for showing the
  behaviour. It is compressed in LZW without predictor, so it is
  written/read correctly.

  However, if you recompress it with this command, the error happens:
  $ tiffcp -c lzw:2 small.tiff small-c2.tiff

  Then displaying it in eog shows a completely different image. Tiffinfo 
indicates a problem with the tags:
  $ tiffinfo small-c2-bad.tiff | grep Predictor
  TIFFReadDirectory: Warning, small-c2-bad.tiff: unknown field with tag 8224 
(0x2020) encountered.

  Comparing it with a good version of the file (generated with a previous 
version of libtiff):
  $ tiffinfo small-c2-good.tiff | grep Predictor
Predictor: horizontal differencing 2 (0x2)

  $ tiffcmp small-c2.tiff small-c2-good.tiff 
  TIFFReadDirectory: Warning, small-c2-bad.tiff: unknown field with tag 8224 
(0x2020) encountered.
  Predictor tag appears only in small-c2-good.tiff

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

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

[Touch-packages] [Bug 1347020] Re: systemd does not boot in a container

2015-04-01 Thread Stéphane Graber

Not anytime soon unfortunately. The backport of all the needed bits as
SRUs will be very very tricky to get right, currently our timeframe is
"by 16.04".

If you're maintaining a PPA already, you could pick up the required
trusty packages from ppa:ubuntu-lxc/daily or just include your own
backports of cgmanager, lxcfs and lxc. They all work great on trusty
(that's what I'm using here) but we can't just push them as is into a
stable release.

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

Title:
  systemd does not boot in a container

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Trusty:
  Triaged

Bug description:
  Opening against cloud-init for now, but ultimately might end up as
  bug-fixes / srus against some other packages in trusty.

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

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

[Touch-packages] [Bug 1439186] Re: [REGRESSION] Predictor tag fails to be written correctly

This bug was fixed in the package tiff - 4.0.3-10ubuntu0.2

---
tiff (4.0.3-10ubuntu0.2) utopic-security; urgency=medium

  * SECURITY REGRESSION: regression when saving TIFF files with compression
predictor (LP: #1439186)
- debian/patches/CVE-2014-8128-5.patch: disable until proper upstream
  fix is available.
 -- Marc DeslauriersWed, 01 Apr 2015 14:05:44 
-0400

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

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

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

Title:
  [REGRESSION] Predictor tag fails to be written correctly

Status in tiff package in Ubuntu:
  Confirmed
Status in tiff source package in Lucid:
  Fix Released
Status in tiff source package in Precise:
  Fix Released
Status in tiff source package in Trusty:
  Fix Released
Status in tiff source package in Utopic:
  Fix Released
Status in tiff source package in Vivid:
  Confirmed

Bug description:
  The patch debian/patches/CVE-2014-8128-5.patch appears to break saving TIFF 
files with compression predictor.
  It seems the data is correctly saved, but the "predictor" tag is not, which 
prevents reading the data correctly again.

  This happens both on precise (release 3.9.5-2ubuntu1.7) and on trusty
  (release 4.0.3-7ubuntu0.2).

  I'm attaching an example TIFF file "small.tiff" for showing the
  behaviour. It is compressed in LZW without predictor, so it is
  written/read correctly.

  However, if you recompress it with this command, the error happens:
  $ tiffcp -c lzw:2 small.tiff small-c2.tiff

  Then displaying it in eog shows a completely different image. Tiffinfo 
indicates a problem with the tags:
  $ tiffinfo small-c2-bad.tiff | grep Predictor
  TIFFReadDirectory: Warning, small-c2-bad.tiff: unknown field with tag 8224 
(0x2020) encountered.

  Comparing it with a good version of the file (generated with a previous 
version of libtiff):
  $ tiffinfo small-c2-good.tiff | grep Predictor
Predictor: horizontal differencing 2 (0x2)

  $ tiffcmp small-c2.tiff small-c2-good.tiff 
  TIFFReadDirectory: Warning, small-c2-bad.tiff: unknown field with tag 8224 
(0x2020) encountered.
  Predictor tag appears only in small-c2-good.tiff

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

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

[Touch-packages] [Bug 1439186] Re: [REGRESSION] Predictor tag fails to be written correctly

This bug was fixed in the package tiff - 3.9.5-2ubuntu1.8

---
tiff (3.9.5-2ubuntu1.8) precise-security; urgency=medium

  * SECURITY REGRESSION: regression when saving TIFF files with compression
predictor (LP: #1439186)
- debian/patches/CVE-2014-8128-5.patch: disable until proper upstream
  fix is available.
 -- Marc DeslauriersWed, 01 Apr 2015 14:08:49 
-0400

** Branch linked: lp:ubuntu/lucid-security/tiff

** Branch linked: lp:ubuntu/trusty-security/tiff

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

Title:
  [REGRESSION] Predictor tag fails to be written correctly

Status in tiff package in Ubuntu:
  Confirmed
Status in tiff source package in Lucid:
  Fix Released
Status in tiff source package in Precise:
  Fix Released
Status in tiff source package in Trusty:
  Fix Released
Status in tiff source package in Utopic:
  Fix Released
Status in tiff source package in Vivid:
  Confirmed

Bug description:
  The patch debian/patches/CVE-2014-8128-5.patch appears to break saving TIFF 
files with compression predictor.
  It seems the data is correctly saved, but the "predictor" tag is not, which 
prevents reading the data correctly again.

  This happens both on precise (release 3.9.5-2ubuntu1.7) and on trusty
  (release 4.0.3-7ubuntu0.2).

  I'm attaching an example TIFF file "small.tiff" for showing the
  behaviour. It is compressed in LZW without predictor, so it is
  written/read correctly.

  However, if you recompress it with this command, the error happens:
  $ tiffcp -c lzw:2 small.tiff small-c2.tiff

  Then displaying it in eog shows a completely different image. Tiffinfo 
indicates a problem with the tags:
  $ tiffinfo small-c2-bad.tiff | grep Predictor
  TIFFReadDirectory: Warning, small-c2-bad.tiff: unknown field with tag 8224 
(0x2020) encountered.

  Comparing it with a good version of the file (generated with a previous 
version of libtiff):
  $ tiffinfo small-c2-good.tiff | grep Predictor
Predictor: horizontal differencing 2 (0x2)

  $ tiffcmp small-c2.tiff small-c2-good.tiff 
  TIFFReadDirectory: Warning, small-c2-bad.tiff: unknown field with tag 8224 
(0x2020) encountered.
  Predictor tag appears only in small-c2-good.tiff

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

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

[Touch-packages] [Bug 1438360] Re: PCI/internal sound card not detected

This is from /var/log/syslog:

File: syslog
 

Apr  1 10:11:34 headadmin-desktop rsyslogd: [origin software="rsyslogd" 
swVersion="7.4.4" x-pid="536" x-info="http://www.rsyslog.com"$
Apr  1 10:11:38 headadmin-desktop anacron[795]: Job `cron.daily' terminated
Apr  1 10:11:38 headadmin-desktop anacron[795]: Normal exit (1 job run)
Apr  1 10:17:01 headadmin-desktop CRON[2820]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
Apr  1 11:17:01 headadmin-desktop CRON[2976]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
Apr  1 12:17:01 headadmin-desktop CRON[3263]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)

--
sudo aplay -l gives this output:

headadmin@headadmin-desktop:/var/log$ sudo aplay -l
[sudo] password for headadmin: 
aplay: device_list:268: no soundcards found...

---
I also re-installed the alsa sound here according to another post and this was 
the result:  

headadmin@headadmin-desktop:/proc$ sudo apt-get install alsa-base alsa-utils 
alsa-tools libasound2 libasound2-plugins
Reading package lists... Done
Building dependency tree   
Reading state information... Done
alsa-base is already the newest version.
alsa-utils is already the newest version.
libasound2 is already the newest version.
libasound2-plugins is already the newest version.
libasound2-plugins set to manually installed.
The following packages were automatically installed and are no longer required:
  libapparmor-perl linux-headers-3.16.0-30 linux-headers-3.16.0-30-generic
  linux-image-3.16.0-30-generic linux-image-extra-3.16.0-30-generic
Use 'apt-get autoremove' to remove them.
The following NEW packages will be installed:
  alsa-toolsheadadmin@headadmin-desktop:/proc$ sudo apt-get install alsa-base 
alsa-utils alsa-tools libasound2 libasound2-plugins
Reading package lists... Doneheadadmin@headadmin-desktop:/proc$ sudo apt-get 
install alsa-base alsa-utils alsa-tools libasound2 libasound2-plugins
Reading package lists... Done
Building dependency tree   
Reading state information... Done
alsa-base is already the newest version.
alsa-utils is already the newest version.
libasound2 is already the newest version.
libasound2-plugins is already the newest version.
libasound2-plugins set to manually installed.
The following packages were automatically installed and are no longer required:
  libapparmor-perl linux-headers-3.16.0-30 linux-headers-3.16.0-30-generic
  linux-image-3.16.0-30-generic linux-image-extra-3.16.0-30-generic
Use 'apt-get autoremove' to remove them.
The following NEW packages will be installed:
  alsa-tools
0 upgraded, 1 newly installed, 0 to remove and 12 not upgraded.
Need to get 50.4 kB of archives.
After this operation, 216 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://us.archive.ubuntu.com/ubuntu/ trusty/universe alsa-tools amd64 
1.0.27-2ubuntu3 [50.4 kB]
Fetched 50.4 kB in 0s (104 kB/s)  
Selecting previously unselected package alsa-tools.
(Reading database ... 225035 files and directories currently installed.)
Preparing to unpack .../alsa-tools_1.0.27-2ubuntu3_amd64.deb ...
Unpacking alsa-tools (1.0.27-2ubuntu3) ...headadmin@headadmin-desktop:/proc$ 
sudo apt-get install alsa-base alsa-utils alsa-tools libasound2 
libasound2-plugins
Reading package lists... Done
Building dependency tree   
Reading state information... Done
alsa-base is already the newest version.
alsa-utils is already the newest version.
libasound2 is already the newest version.
libasound2-plugins is already the newest version.
libasound2-plugins set to manually installed.
The following packages were automatically installed and are no longer required:
  libapparmor-perl linux-headers-3.16.0-30 linux-headers-3.16.0-30-generic
  linux-image-3.16.0-30-generic linux-image-extra-3.16.0-30-generic
Use 'apt-get autoremove' to remove them.
The following NEW packages will be installed:
  alsa-tools
0 upgraded, 1 newly installed, 0 to remove and 12 not upgraded.
Need to get 50.4 kB of archives.
After this operation, 216 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://us.archive.ubuntu.com/ubuntu/ trusty/universe alsa-tools amd64 
1.0.27-2ubuntu3 [50.4 kB]
Fetched 50.4 kB in 0s (104 kB/s)  
Selecting previously unselected package alsa-tools.
(Reading database ... 225035 files and directories currently installed.)
Preparing to unpack .../alsa-tools_1.0.27-2ubuntu3_amd64.deb ...
Unpacking alsa-tools (1.0.27-2ubuntu3) ...
Processing triggers for man-db (2.6.7.1-1ubuntu1) ...
Setting up alsa-tools (1.0.27-2ubuntu3) ...headadmin@headadmin-desktop:/proc$ 
sudo apt-get install alsa-base alsa-utils alsa-tools libasound2 
libasound2-plugins
Reading package lists... Done
Building dependency tree

[Touch-packages] [Bug 1439186] Re: [REGRESSION] Predictor tag fails to be written correctly

This bug was fixed in the package tiff - 4.0.3-7ubuntu0.3

---
tiff (4.0.3-7ubuntu0.3) trusty-security; urgency=medium

  * SECURITY REGRESSION: regression when saving TIFF files with compression
predictor (LP: #1439186)
- debian/patches/CVE-2014-8128-5.patch: disable until proper upstream
  fix is available.
 -- Marc DeslauriersWed, 01 Apr 2015 14:07:34 
-0400

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

Title:
  [REGRESSION] Predictor tag fails to be written correctly

Status in tiff package in Ubuntu:
  Confirmed
Status in tiff source package in Lucid:
  Fix Released
Status in tiff source package in Precise:
  Fix Released
Status in tiff source package in Trusty:
  Fix Released
Status in tiff source package in Utopic:
  Fix Released
Status in tiff source package in Vivid:
  Confirmed

Bug description:
  The patch debian/patches/CVE-2014-8128-5.patch appears to break saving TIFF 
files with compression predictor.
  It seems the data is correctly saved, but the "predictor" tag is not, which 
prevents reading the data correctly again.

  This happens both on precise (release 3.9.5-2ubuntu1.7) and on trusty
  (release 4.0.3-7ubuntu0.2).

  I'm attaching an example TIFF file "small.tiff" for showing the
  behaviour. It is compressed in LZW without predictor, so it is
  written/read correctly.

  However, if you recompress it with this command, the error happens:
  $ tiffcp -c lzw:2 small.tiff small-c2.tiff

  Then displaying it in eog shows a completely different image. Tiffinfo 
indicates a problem with the tags:
  $ tiffinfo small-c2-bad.tiff | grep Predictor
  TIFFReadDirectory: Warning, small-c2-bad.tiff: unknown field with tag 8224 
(0x2020) encountered.

  Comparing it with a good version of the file (generated with a previous 
version of libtiff):
  $ tiffinfo small-c2-good.tiff | grep Predictor
Predictor: horizontal differencing 2 (0x2)

  $ tiffcmp small-c2.tiff small-c2-good.tiff 
  TIFFReadDirectory: Warning, small-c2-bad.tiff: unknown field with tag 8224 
(0x2020) encountered.
  Predictor tag appears only in small-c2-good.tiff

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

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

[Touch-packages] [Bug 1439186] Re: [REGRESSION] Predictor tag fails to be written correctly

This bug was fixed in the package tiff - 3.9.2-2ubuntu0.16

---
tiff (3.9.2-2ubuntu0.16) lucid-security; urgency=medium

  * SECURITY REGRESSION: regression when saving TIFF files with compression
predictor (LP: #1439186)
- debian/patches/CVE-2014-8128-5.patch: disable until proper upstream
  fix is available.
 -- Marc DeslauriersWed, 01 Apr 2015 14:09:19 
-0400

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

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

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

Title:
  [REGRESSION] Predictor tag fails to be written correctly

Status in tiff package in Ubuntu:
  Confirmed
Status in tiff source package in Lucid:
  Fix Released
Status in tiff source package in Precise:
  Fix Released
Status in tiff source package in Trusty:
  Fix Released
Status in tiff source package in Utopic:
  Fix Released
Status in tiff source package in Vivid:
  Confirmed

Bug description:
  The patch debian/patches/CVE-2014-8128-5.patch appears to break saving TIFF 
files with compression predictor.
  It seems the data is correctly saved, but the "predictor" tag is not, which 
prevents reading the data correctly again.

  This happens both on precise (release 3.9.5-2ubuntu1.7) and on trusty
  (release 4.0.3-7ubuntu0.2).

  I'm attaching an example TIFF file "small.tiff" for showing the
  behaviour. It is compressed in LZW without predictor, so it is
  written/read correctly.

  However, if you recompress it with this command, the error happens:
  $ tiffcp -c lzw:2 small.tiff small-c2.tiff

  Then displaying it in eog shows a completely different image. Tiffinfo 
indicates a problem with the tags:
  $ tiffinfo small-c2-bad.tiff | grep Predictor
  TIFFReadDirectory: Warning, small-c2-bad.tiff: unknown field with tag 8224 
(0x2020) encountered.

  Comparing it with a good version of the file (generated with a previous 
version of libtiff):
  $ tiffinfo small-c2-good.tiff | grep Predictor
Predictor: horizontal differencing 2 (0x2)

  $ tiffcmp small-c2.tiff small-c2-good.tiff 
  TIFFReadDirectory: Warning, small-c2-bad.tiff: unknown field with tag 8224 
(0x2020) encountered.
  Predictor tag appears only in small-c2-good.tiff

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

-- 
Mailing list: https://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 1438201] Re: package rsyslog-pgsql 7.4.4-1ubuntu2.5 failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 1

2015-04-01 Thread Pietro Guglielmi

Thank you, I ll configure it manually.
Il 01/apr/2015 09:50 PM "Brian Murray"  ha scritto:

> It looks the package failed to install when trying to communicate with
> your database:
>
> Configurazione di rsyslog-mysql (7.4.4-1ubuntu2.5)...
> dbconfig-common: writing config to /etc/dbconfig-common/rsyslog-mysql.conf
>
> Creating config file /etc/dbconfig-common/rsyslog-mysql.conf with new
> version
>
> Creating config file /etc/rsyslog.d/mysql.conf with new version
> ERROR 2002 (HY000): Can't connect to local MySQL server through socket
> '/var/run/mysqld/mysqld.sock' (2).
> unable to connect to mysql server.
> error encountered creating user:
> ERROR 2002 (HY000): Can't connect to local MySQL server through socket
> '/var/run/mysqld/mysqld.sock' (2)
> dbconfig-common: rsyslog-mysql configure: aborted.
> dbconfig-common: flushing administrative password
> dpkg: errore nell'elaborare il pacchetto rsyslog-mysql (--configure):
>  il sottoprocesso installato script di post-installation ha restituito lo
> stato di errore 1
> Configurazione di rsyslog-pgsql (7.4.4-1ubuntu2.5)...
> dbconfig-common: writing config to /etc/dbconfig-common/rsyslog-pgsql.conf
>
> Creating config file /etc/dbconfig-common/rsyslog-pgsql.conf with new
> version
>
> Creating config file /etc/rsyslog.d/pgsql.conf with new version
> warning: database package not installed?
> dbconfig-common: rsyslog-pgsql configure: aborted.
> dbconfig-common: flushing administrative password
> dpkg: errore nell'elaborare il pacchetto rsyslog-pgsql (--configure):
>  il sottoprocesso installato script di post-installation ha restituito lo
> stato di errore 1
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1438201
>
> Title:
>   package rsyslog-pgsql 7.4.4-1ubuntu2.5 failed to install/upgrade: il
>   sottoprocesso installato script di post-installation ha restituito lo
>   stato di errore 1
>
> Status in rsyslog package in Ubuntu:
>   New
>
> Bug description:
>   I don't know what is happen, i was installing more than 10GB software
>   using synaptic softwares list
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 14.04
>   Package: rsyslog-pgsql 7.4.4-1ubuntu2.5
>   ProcVersionSignature: Ubuntu 3.13.0-49.81-generic 3.13.11-ckt17
>   Uname: Linux 3.13.0-49-generic x86_64
>   ApportVersion: 2.14.1-0ubuntu3.8
>   Architecture: amd64
>   Date: Mon Mar 30 15:35:33 2015
>   DuplicateSignature: package:rsyslog-pgsql:7.4.4-1ubuntu2.5:il
> sottoprocesso installato script di post-installation ha restituito lo stato
> di errore 1
>   ErrorMessage: il sottoprocesso installato script di post-installation ha
> restituito lo stato di errore 1
>   InstallationDate: Installed on 2015-03-28 (1 days ago)
>   InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64
> (20140417)
>   SourcePackage: rsyslog
>   Title: package rsyslog-pgsql 7.4.4-1ubuntu2.5 failed to install/upgrade:
> il sottoprocesso installato script di post-installation ha restituito lo
> stato di errore 1
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1438201/+subscriptions
>

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

Title:
  package rsyslog-pgsql 7.4.4-1ubuntu2.5 failed to install/upgrade: il
  sottoprocesso installato script di post-installation ha restituito lo
  stato di errore 1

Status in rsyslog package in Ubuntu:
  New

Bug description:
  I don't know what is happen, i was installing more than 10GB software
  using synaptic softwares list

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: rsyslog-pgsql 7.4.4-1ubuntu2.5
  ProcVersionSignature: Ubuntu 3.13.0-49.81-generic 3.13.11-ckt17
  Uname: Linux 3.13.0-49-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.8
  Architecture: amd64
  Date: Mon Mar 30 15:35:33 2015
  DuplicateSignature: package:rsyslog-pgsql:7.4.4-1ubuntu2.5:il sottoprocesso 
installato script di post-installation ha restituito lo stato di errore 1
  ErrorMessage: il sottoprocesso installato script di post-installation ha 
restituito lo stato di errore 1
  InstallationDate: Installed on 2015-03-28 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: rsyslog
  Title: package rsyslog-pgsql 7.4.4-1ubuntu2.5 failed to install/upgrade: il 
sottoprocesso installato script di post-installation ha restituito lo stato di 
errore 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1439363] [NEW] Arabic language is not searchable in contacs app

2015-04-01 Thread Aiman

Public bug reported:

Hello everybody, 
I got bq E4.5 Ubuntu edition with the Ubuntu 14.10 (r20). I saved some contacts 
in Arabic language. When I search for these contacts no result is showed up 
while the English language is works as expected.

I hope this issue is ironed to enjoy using my loved Ubuntu touch. Arabic
is my main language.

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


** Tags: arabic contacts touch

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

Title:
  Arabic language is not searchable in contacs app

Status in address-book-app package in Ubuntu:
  New

Bug description:
  Hello everybody, 
  I got bq E4.5 Ubuntu edition with the Ubuntu 14.10 (r20). I saved some 
contacts in Arabic language. When I search for these contacts no result is 
showed up while the English language is works as expected.

  I hope this issue is ironed to enjoy using my loved Ubuntu touch.
  Arabic is my main language.

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

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

[Touch-packages] [Bug 1347020] Re: systemd does not boot in a container

2015-04-01 Thread Christopher Townsend

Any ideas when this will be fixed in Trusty?  This is blocking
unity8-lxc from working anymore on Trusty hosts.

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

Title:
  systemd does not boot in a container

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Trusty:
  Triaged

Bug description:
  Opening against cloud-init for now, but ultimately might end up as
  bug-fixes / srus against some other packages in trusty.

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

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

[Touch-packages] [Bug 1438360] Re: PCI/internal sound card not detected

This is from /var/log/syslog:

File: syslog
 

Apr  1 10:11:34 headadmin-desktop rsyslogd: [origin software="rsyslogd" 
swVersion="7.4.4" x-pid="536" x-info="http://www.rsyslog.com"$
Apr  1 10:11:38 headadmin-desktop anacron[795]: Job `cron.daily' terminated
Apr  1 10:11:38 headadmin-desktop anacron[795]: Normal exit (1 job run)
Apr  1 10:17:01 headadmin-desktop CRON[2820]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
Apr  1 11:17:01 headadmin-desktop CRON[2976]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
Apr  1 12:17:01 headadmin-desktop CRON[3263]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)

--
sudo aplay -l gives this output:

headadmin@headadmin-desktop:/var/log$ sudo aplay -l
[sudo] password for headadmin: 
aplay: device_list:268: no soundcards found...

---
I also re-installed the alsa sound here according to another post and this was 
the result:  

headadmin@headadmin-desktop:/proc$ sudo apt-get install alsa-base alsa-utils 
alsa-tools libasound2 libasound2-plugins
Reading package lists... Done
Building dependency tree   
Reading state information... Done
alsa-base is already the newest version.
alsa-utils is already the newest version.
libasound2 is already the newest version.
libasound2-plugins is already the newest version.
libasound2-plugins set to manually installed.
The following packages were automatically installed and are no longer required:
  libapparmor-perl linux-headers-3.16.0-30 linux-headers-3.16.0-30-generic
  linux-image-3.16.0-30-generic linux-image-extra-3.16.0-30-generic
Use 'apt-get autoremove' to remove them.
The following NEW packages will be installed:
  alsa-toolsheadadmin@headadmin-desktop:/proc$ sudo apt-get install alsa-base 
alsa-utils alsa-tools libasound2 libasound2-plugins
Reading package lists... Doneheadadmin@headadmin-desktop:/proc$ sudo apt-get 
install alsa-base alsa-utils alsa-tools libasound2 libasound2-plugins
Reading package lists... Done
Building dependency tree   
Reading state information... Done
alsa-base is already the newest version.
alsa-utils is already the newest version.
libasound2 is already the newest version.
libasound2-plugins is already the newest version.
libasound2-plugins set to manually installed.
The following packages were automatically installed and are no longer required:
  libapparmor-perl linux-headers-3.16.0-30 linux-headers-3.16.0-30-generic
  linux-image-3.16.0-30-generic linux-image-extra-3.16.0-30-generic
Use 'apt-get autoremove' to remove them.
The following NEW packages will be installed:
  alsa-tools
0 upgraded, 1 newly installed, 0 to remove and 12 not upgraded.
Need to get 50.4 kB of archives.
After this operation, 216 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://us.archive.ubuntu.com/ubuntu/ trusty/universe alsa-tools amd64 
1.0.27-2ubuntu3 [50.4 kB]
Fetched 50.4 kB in 0s (104 kB/s)  
Selecting previously unselected package alsa-tools.
(Reading database ... 225035 files and directories currently installed.)
Preparing to unpack .../alsa-tools_1.0.27-2ubuntu3_amd64.deb ...
Unpacking alsa-tools (1.0.27-2ubuntu3) ...headadmin@headadmin-desktop:/proc$ 
sudo apt-get install alsa-base alsa-utils alsa-tools libasound2 
libasound2-plugins
Reading package lists... Done
Building dependency tree   
Reading state information... Done
alsa-base is already the newest version.
alsa-utils is already the newest version.
libasound2 is already the newest version.
libasound2-plugins is already the newest version.
libasound2-plugins set to manually installed.
The following packages were automatically installed and are no longer required:
  libapparmor-perl linux-headers-3.16.0-30 linux-headers-3.16.0-30-generic
  linux-image-3.16.0-30-generic linux-image-extra-3.16.0-30-generic
Use 'apt-get autoremove' to remove them.
The following NEW packages will be installed:
  alsa-tools
0 upgraded, 1 newly installed, 0 to remove and 12 not upgraded.
Need to get 50.4 kB of archives.
After this operation, 216 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://us.archive.ubuntu.com/ubuntu/ trusty/universe alsa-tools amd64 
1.0.27-2ubuntu3 [50.4 kB]
Fetched 50.4 kB in 0s (104 kB/s)  
Selecting previously unselected package alsa-tools.
(Reading database ... 225035 files and directories currently installed.)
Preparing to unpack .../alsa-tools_1.0.27-2ubuntu3_amd64.deb ...
Unpacking alsa-tools (1.0.27-2ubuntu3) ...
Processing triggers for man-db (2.6.7.1-1ubuntu1) ...
Setting up alsa-tools (1.0.27-2ubuntu3) ...headadmin@headadmin-desktop:/proc$ 
sudo apt-get install alsa-base alsa-utils alsa-tools libasound2 
libasound2-plugins
Reading package lists... Done
Building dependency tree

[Touch-packages] [Bug 1438201] Re: package rsyslog-pgsql 7.4.4-1ubuntu2.5 failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 1

It looks the package failed to install when trying to communicate with
your database:

Configurazione di rsyslog-mysql (7.4.4-1ubuntu2.5)...
dbconfig-common: writing config to /etc/dbconfig-common/rsyslog-mysql.conf

Creating config file /etc/dbconfig-common/rsyslog-mysql.conf with new
version

Creating config file /etc/rsyslog.d/mysql.conf with new version
ERROR 2002 (HY000): Can't connect to local MySQL server through socket 
'/var/run/mysqld/mysqld.sock' (2).
unable to connect to mysql server.
error encountered creating user:
ERROR 2002 (HY000): Can't connect to local MySQL server through socket 
'/var/run/mysqld/mysqld.sock' (2)
dbconfig-common: rsyslog-mysql configure: aborted.
dbconfig-common: flushing administrative password
dpkg: errore nell'elaborare il pacchetto rsyslog-mysql (--configure):
 il sottoprocesso installato script di post-installation ha restituito lo stato 
di errore 1
Configurazione di rsyslog-pgsql (7.4.4-1ubuntu2.5)...
dbconfig-common: writing config to /etc/dbconfig-common/rsyslog-pgsql.conf

Creating config file /etc/dbconfig-common/rsyslog-pgsql.conf with new
version

Creating config file /etc/rsyslog.d/pgsql.conf with new version
warning: database package not installed?
dbconfig-common: rsyslog-pgsql configure: aborted.
dbconfig-common: flushing administrative password
dpkg: errore nell'elaborare il pacchetto rsyslog-pgsql (--configure):
 il sottoprocesso installato script di post-installation ha restituito lo stato 
di errore 1

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

Title:
  package rsyslog-pgsql 7.4.4-1ubuntu2.5 failed to install/upgrade: il
  sottoprocesso installato script di post-installation ha restituito lo
  stato di errore 1

Status in rsyslog package in Ubuntu:
  New

Bug description:
  I don't know what is happen, i was installing more than 10GB software
  using synaptic softwares list

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: rsyslog-pgsql 7.4.4-1ubuntu2.5
  ProcVersionSignature: Ubuntu 3.13.0-49.81-generic 3.13.11-ckt17
  Uname: Linux 3.13.0-49-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.8
  Architecture: amd64
  Date: Mon Mar 30 15:35:33 2015
  DuplicateSignature: package:rsyslog-pgsql:7.4.4-1ubuntu2.5:il sottoprocesso 
installato script di post-installation ha restituito lo stato di errore 1
  ErrorMessage: il sottoprocesso installato script di post-installation ha 
restituito lo stato di errore 1
  InstallationDate: Installed on 2015-03-28 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: rsyslog
  Title: package rsyslog-pgsql 7.4.4-1ubuntu2.5 failed to install/upgrade: il 
sottoprocesso installato script di post-installation ha restituito lo stato di 
errore 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1438205] Re: package rsyslog-mysql 7.4.4-1ubuntu2.5 failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 1

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

** This bug has been marked a duplicate of bug 1438201
   package rsyslog-pgsql 7.4.4-1ubuntu2.5 failed to install/upgrade: il 
sottoprocesso installato script di post-installation ha restituito lo stato di 
errore 1

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

Title:
  package rsyslog-mysql 7.4.4-1ubuntu2.5 failed to install/upgrade: il
  sottoprocesso installato script di post-installation ha restituito lo
  stato di errore 1

Status in rsyslog package in Ubuntu:
  New

Bug description:
  I don't know what is happen, i was installing more than 10 GB using
  synaptic softwares list

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: rsyslog-mysql 7.4.4-1ubuntu2.5
  ProcVersionSignature: Ubuntu 3.13.0-49.81-generic 3.13.11-ckt17
  Uname: Linux 3.13.0-49-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.8
  Architecture: amd64
  Date: Mon Mar 30 15:34:45 2015
  DuplicateSignature: package:rsyslog-mysql:7.4.4-1ubuntu2.5:il sottoprocesso 
installato script di post-installation ha restituito lo stato di errore 1
  ErrorMessage: il sottoprocesso installato script di post-installation ha 
restituito lo stato di errore 1
  InstallationDate: Installed on 2015-03-28 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: rsyslog
  Title: package rsyslog-mysql 7.4.4-1ubuntu2.5 failed to install/upgrade: il 
sottoprocesso installato script di post-installation ha restituito lo stato di 
errore 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1370008] Re: url-dispatcher-bad-url

2015-04-01 Thread Bill Filler

Seems to be 1165 occurrances of this crash according to:
https://errors.ubuntu.com/?channel_name=ubuntu-touch/stable/bq-aquaris.en&device_name=krillin&period=week&pkg_arch=armhf

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

Title:
  url-dispatcher-bad-url

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

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding gallery-app.  This problem was most recently seen with
  version 13.10.0+14.10.20140908.1-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/b1f16000af092461aeb85b5c7edfd3dc3f1271c8
  contains more details.

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

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

[Touch-packages] [Bug 1370008] Re: url-dispatcher-bad-url

2015-04-01 Thread Bill Filler

this appears to be a webbrowser-app issue not a gallery issue, please
take a look

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

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

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

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

Title:
  url-dispatcher-bad-url

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

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding gallery-app.  This problem was most recently seen with
  version 13.10.0+14.10.20140908.1-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/b1f16000af092461aeb85b5c7edfd3dc3f1271c8
  contains more details.

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

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

[Touch-packages] [Bug 1439186] Re: [REGRESSION] Predictor tag fails to be written correctly

** Branch linked: lp:ubuntu/vivid-proposed/tiff

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

Title:
  [REGRESSION] Predictor tag fails to be written correctly

Status in tiff package in Ubuntu:
  Confirmed
Status in tiff source package in Lucid:
  Confirmed
Status in tiff source package in Precise:
  Confirmed
Status in tiff source package in Trusty:
  Confirmed
Status in tiff source package in Utopic:
  Confirmed
Status in tiff source package in Vivid:
  Confirmed

Bug description:
  The patch debian/patches/CVE-2014-8128-5.patch appears to break saving TIFF 
files with compression predictor.
  It seems the data is correctly saved, but the "predictor" tag is not, which 
prevents reading the data correctly again.

  This happens both on precise (release 3.9.5-2ubuntu1.7) and on trusty
  (release 4.0.3-7ubuntu0.2).

  I'm attaching an example TIFF file "small.tiff" for showing the
  behaviour. It is compressed in LZW without predictor, so it is
  written/read correctly.

  However, if you recompress it with this command, the error happens:
  $ tiffcp -c lzw:2 small.tiff small-c2.tiff

  Then displaying it in eog shows a completely different image. Tiffinfo 
indicates a problem with the tags:
  $ tiffinfo small-c2-bad.tiff | grep Predictor
  TIFFReadDirectory: Warning, small-c2-bad.tiff: unknown field with tag 8224 
(0x2020) encountered.

  Comparing it with a good version of the file (generated with a previous 
version of libtiff):
  $ tiffinfo small-c2-good.tiff | grep Predictor
Predictor: horizontal differencing 2 (0x2)

  $ tiffcmp small-c2.tiff small-c2-good.tiff 
  TIFFReadDirectory: Warning, small-c2-bad.tiff: unknown field with tag 8224 
(0x2020) encountered.
  Predictor tag appears only in small-c2-good.tiff

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

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

[Touch-packages] [Bug 1434579] Re: Unable to install VirtualBox Guest Service in 15.04

Do you have the multiverse repository enabled? That is where the
virtualbox-guest-x11 package is located.

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

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

Title:
  Unable to install VirtualBox Guest Service in 15.04

Status in software-properties package in Ubuntu:
  Incomplete

Bug description:
  It is not longer possible to select VirtualBox Guest Service in 15.04.
  The only options available are:

* Continue using a manually install driver
* Do not use the device

  The option 'Using x86 virtualisation solution - guest addition module'
  is no longer selectable. See the attached screen shot. This is from a
  fresh install of Ubuntu MATE 15.04 daily (20th March) and no drivers
  have been manually installed.

  In light of the Virtualbox issue where new installs on Virtualbox have
  a resolution of 640x480
  (https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1368784/)
  this is going to be a frustration for many users.

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

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

[Touch-packages] [Bug 1410190] Re: /usr/bin/ubuntu-location-serviced:* Error in `/usr/bin/ubuntu-location-serviced': malloc(): memory corruption (fast): ADDR *

** Changed in: location-service (Ubuntu)
 Assignee: (unassigned) => Thomas Voß (thomas-voss)

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

Title:
  /usr/bin/ubuntu-location-serviced:*** Error in `/usr/bin/ubuntu-
  location-serviced': malloc(): memory corruption (fast): ADDR ***

Status in location-service package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding location-service.  This problem was most recently seen with
  version 2.1+15.04.20150106~rtm-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/284a0959d15e8ca7d2d39ec2dbb85d403132b356
  contains more details.

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

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

[Touch-packages] [Bug 1438931] Re: qtcreator crash when window on monitor which is unplugged

2015-04-01 Thread Dmitry Shachnev

Attaching the stack trace here, as on paste.ubuntu.com it can expire and
be deleted.

** Attachment added: "qtcreator_trace.txt"
   
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1438931/+attachment/4363301/+files/qtcreator_trace.txt

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

Title:
  qtcreator crash when window on monitor which is unplugged

Status in qtbase-opensource-src package in Ubuntu:
  Invalid
Status in qtcreator package in Ubuntu:
  New

Bug description:
  Steps to Repro:
  1. Multimonitor setup needed
  2. Open QtCreator, open a Qt project of some kind
  3. Move the QtCreator window to the monitor you can unplug
  4. unplug that monitor

  Expected result
  Window Manager relocates the QtCreator window to the remaining monitor

  Actual result
  QtCreator crashes

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

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

[Touch-packages] [Bug 1434991] Re: python attributeError 'SSLTimeoutError' after upgrade

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

** Changed in: python-defaults (Ubuntu)
   Status: New => Confirmed

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

Title:
  python attributeError 'SSLTimeoutError' after upgrade

Status in python-defaults package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu 14.04.2 LTS

  I use use a nagios script called check_esxi_hardware.py to check several esxi 
platforms.
  After last uBuntu upgrade it stopped working giving the following error:

  ##
  Traceback (most recent call last):
File "/usr/lib/nagios/plugins/check_esxi_hardware.py", line 619, in 
  instance_list = wbemclient.EnumerateInstances(classe)
File "/usr/lib/pymodules/python2.7/pywbem/cim_operations.py", line 421, in 
EnumerateInstances
  **params)
File "/usr/lib/pymodules/python2.7/pywbem/cim_operations.py", line 183, in 
imethodcall
  no_verification = self.no_verification)
File "/usr/lib/pymodules/python2.7/pywbem/cim_http.py", line 268, in 
wbem_request
  h.endheaders()
File "/usr/lib/python2.7/httplib.py", line 969, in endheaders
  self._send_output(message_body)
File "/usr/lib/python2.7/httplib.py", line 829, in _send_output
  self.send(msg)
File "/usr/lib/pymodules/python2.7/pywbem/cim_http.py", line 115, in send
  self.connect()
File "/usr/lib/pymodules/python2.7/pywbem/cim_http.py", line 167, in connect
  except ( Err.SSLError, SSL.SSLError, SSL.SSLTimeoutError
  AttributeError: 'module' object has no attribute 'SSLTimeoutError'
  

  -  'module' here refers to m2crypto. This look like an incompatibility between
  the versions of python-m2crypto and python-pywbem.

  -  python-m2crypto did not exist before the upgrade

  Here is the comparison of installed python packages, before and after
  the upgrade, and

  $ diff python-packages-no-problem.txt python-packages-problem.txt 
  2d1
  < ii  libfile-copy-recursive-perl 0.38-1   
all  Perl extension for recursively copying files and directories
  8d6
  < rc  libpython3.3-minimal:amd64  3.3.2-7ubuntu3.1 
amd64Minimal subset of the Python language (version 3.3)
  19a18
  > ii  python-m2crypto 0.21.1-3ubuntu5  
amd64a crypto and SSL toolkit for Python
  21d19
  < ii  python-newt 0.52.15-2ubuntu5 
amd64NEWT module for Python
  27,28c25,26
  < ii  python-pywbem   0.7.0-4  
all  Python WBEM Client and Provider Interface
  < ii  python-requests 2.2.1-1ubuntu0.1 
all  elegant and simple HTTP library for Python, built for human beings
  ---
  > ii  python-pywbem   0.7.0-4ubuntu1~14.04.1   
all  Python WBEM Client and Provider Interface
  > ii  python-requests 2.2.1-1ubuntu0.2 
all  elegant and simple HTTP library for Python, built for human beings
  51a50
  > ii  python3-newt0.52.15-2ubuntu5 
amd64NEWT module for Python3
  56,57d54
  < rc  python3.3   3.3.2-7ubuntu3.1 
amd64Interactive high-level object-oriented language (version 3.3)
  < rc  python3.3-minimal   3.3.2-7ubuntu3.1 
amd64Minimal subset of the Python language (version 3.3)

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

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

[Touch-packages] [Bug 1439350] [NEW] contacts in Gmail groups not imported

2015-04-01 Thread Ronnie Tucker

Public bug reported:

Any contacts listed under 'My Contacts' are automatically imported after
signing into the account. Any contacts in groups will not be imported.

Ubuntu 14.10 (r20) on the BQ E4.5 phone

** Affects: address-book-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 address-book-app in
Ubuntu.
https://bugs.launchpad.net/bugs/1439350

Title:
  contacts in Gmail groups not imported

Status in address-book-app package in Ubuntu:
  New

Bug description:
  Any contacts listed under 'My Contacts' are automatically imported
  after signing into the account. Any contacts in groups will not be
  imported.

  Ubuntu 14.10 (r20) on the BQ E4.5 phone

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

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

[Touch-packages] [Bug 1438360] Re: PCI/internal sound card not detected

Raymond, I ran lspci - and here is the output.  Hopefully this helps?  I 
don't understand it all yet.  
---

headadmin@headadmin-desktop:~$ lspci -
00:00.0 Host bridge: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx DMI 
Bridge (rev 02)
Subsystem: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx DMI 
Bridge
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: agpgart-intel

00:02.0 VGA compatible controller: Intel Corporation Atom Processor 
D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller (rev 02) (prog-if 00 [VGA 
controller])
Subsystem: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx 
Integrated Graphics Controller
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR-  [disabled]
Capabilities: 
Kernel driver in use: i915

00:02.1 Display controller: Intel Corporation Atom Processor 
D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller (rev 02)
Subsystem: Intel Corporation Device a001
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

00:1c.0 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 1 (rev 
02) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:1c.1 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 2 (rev 
02) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:1c.3 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 4 (rev 
02) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:1d.0 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller 
#1 (rev 02) (prog-if 00 [UHCI])
Subsystem: Intel Corporation NM10/ICH7 Family USB UHCI Controller #1
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- 
Kernel driver in use: ehci-pci

00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2) (prog-if 
01 [Subtractive decode])
Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- 
Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 

00:1f.0 ISA bridge: Intel Corporation NM10 Family LPC Controller (rev 02)
Subsystem: Intel Corporation NM10 Family LPC Controller
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: lpc_ich

00:1f.2 IDE interface: Intel Corporation NM10/ICH7 Family SATA Controller [IDE 
mode] (rev 02) (prog-if 8a [Master SecP PriP])
Subsystem: Intel Corporation NM10/ICH7 Family SATA Controller [IDE mode]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: ata_piix

00:1f.3 SMBus: Intel Corporation NM10/ICH7 Family SMBus Controller (rev 02)
Subsystem: Intel Corporation NM10/ICH7 Family SMBus Controller
Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- TAbort- SERR- 
Kernel driver in use: r8169

headadmin@headadmin-deskto

[Touch-packages] [Bug 1439222] Re: Implement emoji in Ubuntu

2015-04-01 Thread nicolas

I found two more related bugs, both for Ubuntu Phone:
* #1269017 for both display and input, on mobile and not desktop, resolved with 
Symbola (like #1137630) and with #1340598.
* #1340598 which is for input, resolved by having a emoji keyboard on mobile! 
Great, it would be great to have something similar for desktop.

Recap of emoji-related bugs:
* #1439222 (desktop & phone) (display, input) (this one): full emoji 
experience: colour display, qualitative set, input UI. Unresolved.
* #1137630 (desktop & phone) (display): simple display of emoji. Resolved with 
Symbola.
* #1269017 (phone) (display, input): display and input for mobile. Resolved 
with Symbola and next bug.
* #1340598 (phone) (input): input for mobile. Resolved with an emoji keyboard.
* #820034: emoji set design for the Ubuntu Font Family. Unresolved.

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

Title:
  Implement emoji in Ubuntu

Status in ubuntu-meta package in Ubuntu:
  New
Status in ubuntu-touch-meta package in Ubuntu:
  New

Bug description:
  This bug is about implementing emoji display and insertion in Ubuntu,
  desktop and phone.

  I wrote a page about possible ways to implement emoji in Gnu/Linux systems:
  http://probablement.net/txt/emojilinux

  To sum it up:

  * The first thing to do is having the Symbola font (in ttf-ancient-
  fonts) as part of the default installation, so users can see
  monochrome emoji. If I understand, it’s what is being done in bug
  #1137630 (which is about not seeing emoji: Symbola certainly resolve
  it but isn’t a full implementation of emoji as we expect them).

  * The second thing is replacing Symbola with a proper colour emoji
  set, like Emoji One, Noto Color Emoji, or Twemoji. There’s different
  ways to implement this (layered colour font, SVG font, substitution
  with individual SVG files, …) but if I understand correctly comment #6
  in #1137630 FreeType is already compatible with colour fonts! (I will
  update my page)

  * An optional third step would be designing a custom Emoji set. That’s
  more or less bug #820034 even if I’m unsure about it being part of the
  Ubuntu Font Family, even if drawn in stylistically consistent way with
  it.

  * Lastly, we need a system wide UI to browse, pick and insert emoji. I
  added some existing examples on the page; basically, the choice is
  making it only for emoji or part of larger UI for inserting
  characters.

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

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

[Touch-packages] [Bug 1439313] Re: apt-key del keyid is case sensitive

2015-04-01 Thread Bug Watch Updater

** Changed in: apt (Debian)
   Status: Unknown => New

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

Title:
  apt-key del keyid is case sensitive

Status in apt package in Ubuntu:
  Confirmed
Status in apt package in Debian:
  New

Bug description:
  Note:
  Confirmed on Ubuntu utopic with apt 1.0.9.2ubuntu2
  Confirmed on Debian jessie apt 1.0.9.7

  Behavior NOT seen on Ubuntu precise with apt 0.8.16~exp12ubuntu10.22
  Behavior NOT seen on Debian wheezy apt 0.9.7.9+deb7u7

  apt-key export is not case-sensitive to the hex keyid specified.
  Inconsistently, apt-key del is case-sensitive and won't match unless
  the hex keyid is uppercase. This is highly exacerbated by bug #1256565
  which results in "OK" being printed and success being returned when
  apt-key del doesn't match anything.

  The user is reasonably left to conclude that the key has been deleted
  from the trusted keyring when it has not.

  Example:

  # apt-key export 7fac5991
  -BEGIN PGP PUBLIC KEY BLOCK-
  Version: GnuPG v1

  mQGiBEXwb0YRBADQva2NLpYXxgjNkbuP0LnPoEXruGmvi3XMIxjEUFuGNCP4Rj/a
  kv2E5VixBP1vcQFDRJ+p1puh8NU0XERlhpyZrVMzzS/RdWdyXf7E5S8oqNXsoD1z
  fvmI+i9b2EhHAA19Kgw7ifV8vMa4tkwslEmcTiwiw8lyUl28Wh4Et8SxzwCggDcA
  feGqtn3PP5YAdD0km4S4XeMEAJjlrqPoPv2Gf//tfznY2UyS9PUqFCPLHgFLe80u
  QhI2U5jt6jUKN4fHauvR6z3seSAsh1YyzyZCKxJFEKXCCqnrFSoh4WSJsbFNc4PN
  b0V0SqiTCkWADZyLT5wll8sWuQ5ylTf3z1ENoHf+G3um3/wk/+xmEHvj9HCTBEXP
  78X0A/0Tqlhc2RBnEf+AqxWvM8sk8LzJI/XGjwBvKfXe+l3rnSR2kEAvGzj5Sg0X
  4XmfTg4Jl8BNjWyvm2Wmjfet41LPmYJKsux3g0b8yzQxeOA4pQKKAU3Z4+rgzGmf
  HdwCG5MNT2A5XxD/eDd+L4fRx0HbFkIQoAi1J3YWQSiTk15fw7RMR29vZ2xlLCBJ
  bmMuIExpbnV4IFBhY2thZ2UgU2lnbmluZyBLZXkgPGxpbnV4LXBhY2thZ2VzLWtl
  eW1hc3RlckBnb29nbGUuY29tPohjBBMRAgAjAhsDBgsJCAcDAgQVAggDBBYCAwEC
  HgECF4AFAkYVdn8CGQEACgkQoECDD3+sWZHKSgCfdq3HtNYJLv+XZleb6HN4zOcF
  AJEAniSFbuv8V5FSHxeRimHx25671az+uQINBEXwb0sQCACuA8HT2nr+FM5y/kzI
  A51ZcC46KFtIDgjQJ31Q3OrkYP8LbxOpKMRIzvOZrsjOlFmDVqitiVc7qj3lYp6U
  rgNVaFv6Qu4bo2/ctjNHDDBdv6nufmusJUWq/9TwieepM/cwnXd+HMxu1XBKRVk9
  XyAZ9SvfcW4EtxVgysI+XlptKFa5JCqFM3qJllVohMmr7lMwO8+sxTWTXqxsptJo
  pZeKz+UBEEqPyw7CUIVYGC9ENEtIMFvAvPqnhj1GS96REMpry+5s9WKuLEaclWpd
  K3krttbDlY1NaeQUCRvBYZ8iAG9YSLHUHMTuI2oea07Rh4dtIAqPwAX8xn36JAYG
  2vgLAAMFB/wKqaycjWAZwIe98Yt0qHsdkpmIbarD9fGiA6kfkK/UxjL/k7tmS4Vm
  CljrrDZkPSQ/19mpdRcGXtb0NI9+nyM5trweTvtPw+HPkDiJlTaiCcx+izg79Fj9
  KcofuNb3lPdXZb9tzf5oDnmm/B+4vkeTuEZJ//IFty8cmvCpzvY+DAz1Vo9rA+Zn
  cpWY1n6z6oSS9AsyT/IFlWWBZZ17SpMHu+h4Bxy62+AbPHKGSujEGQhWq8ZRoJAT
  G0KSObnmZ7FwFWu1e9XFoUCt0bSjiJWTIyaObMrWu/LvJ3e9I87HseSJStfw6fki
  5og9qFEkMrIrBCp3QGuQWBq/rTdMuwNFiEkEGBECAAkFAkXwb0sCGwwACgkQoECD
  D3+sWZF/WACfeNAu1/1hwZtUo1bR+MWiCjpvHtwAnA1R3IHqFLQ2X3xJ40XPuAyY
  /FJG
  =Quqp
  -END PGP PUBLIC KEY BLOCK-
  # apt-key del 7fac5991
  OK
  # echo $?
  0
  # apt-key export 7fac5991
  -BEGIN PGP PUBLIC KEY BLOCK-
  Version: GnuPG v1

  mQGiBEXwb0YRBADQva2NLpYXxgjNkbuP0LnPoEXruGmvi3XMIxjEUFuGNCP4Rj/a
  kv2E5VixBP1vcQFDRJ+p1puh8NU0XERlhpyZrVMzzS/RdWdyXf7E5S8oqNXsoD1z
  fvmI+i9b2EhHAA19Kgw7ifV8vMa4tkwslEmcTiwiw8lyUl28Wh4Et8SxzwCggDcA
  feGqtn3PP5YAdD0km4S4XeMEAJjlrqPoPv2Gf//tfznY2UyS9PUqFCPLHgFLe80u
  QhI2U5jt6jUKN4fHauvR6z3seSAsh1YyzyZCKxJFEKXCCqnrFSoh4WSJsbFNc4PN
  b0V0SqiTCkWADZyLT5wll8sWuQ5ylTf3z1ENoHf+G3um3/wk/+xmEHvj9HCTBEXP
  78X0A/0Tqlhc2RBnEf+AqxWvM8sk8LzJI/XGjwBvKfXe+l3rnSR2kEAvGzj5Sg0X
  4XmfTg4Jl8BNjWyvm2Wmjfet41LPmYJKsux3g0b8yzQxeOA4pQKKAU3Z4+rgzGmf
  HdwCG5MNT2A5XxD/eDd+L4fRx0HbFkIQoAi1J3YWQSiTk15fw7RMR29vZ2xlLCBJ
  bmMuIExpbnV4IFBhY2thZ2UgU2lnbmluZyBLZXkgPGxpbnV4LXBhY2thZ2VzLWtl
  eW1hc3RlckBnb29nbGUuY29tPohjBBMRAgAjAhsDBgsJCAcDAgQVAggDBBYCAwEC
  HgECF4AFAkYVdn8CGQEACgkQoECDD3+sWZHKSgCfdq3HtNYJLv+XZleb6HN4zOcF
  AJEAniSFbuv8V5FSHxeRimHx25671az+uQINBEXwb0sQCACuA8HT2nr+FM5y/kzI
  A51ZcC46KFtIDgjQJ31Q3OrkYP8LbxOpKMRIzvOZrsjOlFmDVqitiVc7qj3lYp6U
  rgNVaFv6Qu4bo2/ctjNHDDBdv6nufmusJUWq/9TwieepM/cwnXd+HMxu1XBKRVk9
  XyAZ9SvfcW4EtxVgysI+XlptKFa5JCqFM3qJllVohMmr7lMwO8+sxTWTXqxsptJo
  pZeKz+UBEEqPyw7CUIVYGC9ENEtIMFvAvPqnhj1GS96REMpry+5s9WKuLEaclWpd
  K3krttbDlY1NaeQUCRvBYZ8iAG9YSLHUHMTuI2oea07Rh4dtIAqPwAX8xn36JAYG
  2vgLAAMFB/wKqaycjWAZwIe98Yt0qHsdkpmIbarD9fGiA6kfkK/UxjL/k7tmS4Vm
  CljrrDZkPSQ/19mpdRcGXtb0NI9+nyM5trweTvtPw+HPkDiJlTaiCcx+izg79Fj9
  KcofuNb3lPdXZb9tzf5oDnmm/B+4vkeTuEZJ//IFty8cmvCpzvY+DAz1Vo9rA+Zn
  cpWY1n6z6oSS9AsyT/IFlWWBZZ17SpMHu+h4Bxy62+AbPHKGSujEGQhWq8ZRoJAT
  G0KSObnmZ7FwFWu1e9XFoUCt0bSjiJWTIyaObMrWu/LvJ3e9I87HseSJStfw6fki
  5og9qFEkMrIrBCp3QGuQWBq/rTdMuwNFiEkEGBECAAkFAkXwb0sCGwwACgkQoECD
  D3+sWZF/WACfeNAu1/1hwZtUo1bR+MWiCjpvHtwAnA1R3IHqFLQ2X3xJ40XPuAyY
  /FJG
  =Quqp
  -END PGP PUBLIC KEY BLOCK-
  # apt-key del 7FAC5991
  OK
  # echo $?
  0
  # apt-key export 7fac5991
  gpg: WARNING: nothing exported

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

-- 
Mailing list: https://launc

[Touch-packages] [Bug 875017] Re: Translation for "Wired Connection %s" not displayed

2015-04-01 Thread Pascal S

I am experiencing this bug with Ubuntu 14.10. 
nm-applet displays "wired" though I expect it to be translated in French.

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

Title:
  Translation for "Wired Connection %s" not displayed

Status in NetworkManager:
  Fix Released
Status in Ubuntu Translations:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  The string "Wired Connection %d" (where %d is a number) which is
  displayed when you connect to the Internet using an ethernet cable
  does show up in English, although there is a translation available and
  has been submitted in time. If you have an ethernet cable connected
  the string also appears when you click the network-icon.

  You'll find the affected string here:
  
https://translations.launchpad.net/ubuntu/oneiric/+source/network-manager-applet/+pots/nm-applet/de/+translate?batch=10&show=all&search=wired+connection

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: network-manager-gnome 0.9.1.90-0ubuntu6
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic-pae 3.0.4
  Uname: Linux 3.0.0-12-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu3
  Architecture: i386
  CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden
  Date: Sat Oct 15 15:15:51 2011
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  IpRoute:
   default via 192.168.2.1 dev eth0  proto static 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.2.0/24 dev eth0  proto kernel  scope link  src 192.168.2.124  metric 
1 
   192.168.2.0/24 dev wlan0  proto kernel  scope link  src 192.168.2.121  
metric 2
  Keyfiles: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager-applet
  UpgradeStatus: Upgraded to oneiric on 2011-10-14 (1 days ago)

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

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

[Touch-packages] [Bug 1417920] Re: Cannot drag up/down launcher if right-edge DDA area covers the whole panel

2015-04-01 Thread Daniel d'Andrada

** Branch linked: lp:~dandrader/unity8/ddaImprovements

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

Title:
  Cannot drag up/down launcher if right-edge DDA area covers the whole
  panel

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  One way to easily reproduce this is to change the Launcher's DDA to be
  as wide as the Launcher itself. Then reveal the Launcher and try to
  drag it up/down. Instead of moving up/down it will hide again.

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

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

[Touch-packages] [Bug 1438301] Re: suspends after a few minutes on machines with a bogus (closed) lid switch

** Tags added: vivid

** Also affects: systemd (Ubuntu Vivid)
   Importance: Low
   Status: Triaged

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

Title:
  suspends after a few minutes on machines with a bogus (closed) lid
  switch

Status in systemd package in Ubuntu:
  Triaged
Status in systemd source package in Vivid:
  Triaged

Bug description:
  On a desktop machine which claims to have a closed lid (on the
  motherboard), but doesn't actually have a lid, logind will suspend the
  machine shortly after boot as a safety measure to avoid burning your
  laptop in a bag. This is wrong in the above situation where the
  announced lid switch does not exist or isn't actually closed.

  Workaround: Set HandleLidSwitch=ignore in /etc/systemd/logind.conf

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

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

[Touch-packages] [Bug 1434847] Re: does not start a display manager

Could you answer Martin's question so that we can proceed?

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

Title:
  does not start a display manager

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  After updating all packages, I can't boot by choosing Ubuntu in the 
bootloader anymore. Kubuntu logo remains until the terminal shows, "Starting 
version 219".
  I can boot successfully by choosing Ubuntu...(Updstart).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-4ubuntu7 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Mar 21 12:02:06 2015
  InstallationDate: Installed on 2015-03-21 (0 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150224.1)
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic.efi.signed 
root=UUID=ed2ae459-760e-4bd7-b5a0-f7f221d2d7fe ro quiet splash 
init=/sbin/upstart
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   
   1 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/29/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.25
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 183E
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 56.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.25:bd05/29/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088512005D160:rvnHewlett-Packard:rn183E:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.version: 088512005D160
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 518056] Re: cedilla appears as accented c (ć instead of ç) when typing 'c

2015-04-01 Thread Leandro

Concerning the pt_PT: The portuguese from Portugal, although it has its 
differences relative to brazilian
portuguese, has the same accents and it also requires the cedilla the same way, 
so I suspected that they
had the same problem. I checked, then, the existence of the same tipe of claim 
in forums from Portugal,
using Google 
(https://www.google.pt/?gws_rd=ssl#q=cedilha+ubuntu&tbs=ctr:countryPT&cr=countryPT).

Indeed, we can find exactly the same problem for them. Although, as Portugal 
has 5% the population of Brazil,
the number of posts is much smaller.

Therefore, I think that the fix for this problem should be applied to pt_PT 
too. And, if there is any other
variation of portuguese (I am not sure if there is one for Angola, Moçambique, 
etc.), they all sould be 
fixed.

Leandro.

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

Title:
  cedilla appears as accented c (ć instead of ç) when typing 'c

Status in central project for keyboard configuration:
  Confirmed
Status in gtk+2.0 package in Ubuntu:
  Confirmed
Status in language-selector package in Ubuntu:
  Fix Released
Status in libx11 package in Ubuntu:
  New
Status in xkeyboard-config package in Ubuntu:
  Confirmed

Bug description:
  
  When typing in a US-international keyboard with dead-keys (or 
UK-international), 
  typing 'c results in an accented c instead of a cedilla.

  There is a workaround, which is editing the

  /usr/lib/gtk-2.0/2.10.0/immodule-files.d/libgtk2.0-0.immodules

  file and changing the line

  "cedilla" "Cedilla" "gtk20" "/usr/share/locale"
  "az:ca:co:fr:gv:oc:pt:sq:tr:wa"

  to

  "cedilla" "Cedilla" "gtk20" "/usr/share/locale"
  "az:ca:co:fr:gv:oc:pt:sq:tr:wa:en"

  (add the 'en' at the end).

  However, every time some update on this file is applied, one looses the 
change,
  and we get back to the accented c. That means having to modify the file again,
  logout and login.

  For me this is no problem. But for my brother, mom, dad, etc, it is always 
something
  that at least makes me less proud of having convinced them to use Ubuntu, 
because
  they don't know what to do each time this happens.

  I think we really need a configurable keyboard layout, or at least (and that 
would
  be very easy), the inclusion of alternate layouts on install that for the 
dead-key
  options (as US-deadkey and UK-deakey), alternate layouts as 
US-deadkey-cedilla.

  This change is relevant for at least Portuguese and French.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xkeyboard-config/+bug/518056/+subscriptions

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

[Touch-packages] [Bug 1417658] Re: apparmor denied operation file_inherit from networkmanager when using HWE kernel

2015-04-01 Thread Chris J Arges

Hello Bernhard, or anyone else affected,

Accepted isc-dhcp into trusty-proposed. The package will build now and
be available at http://launchpad.net/ubuntu/+source/isc-
dhcp/4.2.4-7ubuntu12.1 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: isc-dhcp (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 isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1417658

Title:
  apparmor denied operation file_inherit from networkmanager when using
  HWE kernel

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Trusty:
  Fix Committed
Status in isc-dhcp source package in Vivid:
  Fix Released

Bug description:
  [Impact]
  AppArmor denials appear in dhclient when using using HWE kernel on 14.04. 
This can result in incorrect dhcp operation on client systems. The fix is to 
add these rules:
network inet dgram,
network inet6 dgram,

  to the dhclient profile for nm-dhcp-client.action and dhclient-script,
  like we did in 4.2.4-7ubuntu14.

  [Test Case]
  Install HWE kernel and use network manager to obtain an IP address.

  [Regression Potential]
  Extremely low since the update only adds access that dhclient didn't have.

  Original description:

  Hallo,

  on Kubuntu 14.04.x dmesg shows me the following apparmor messages;

  Is this normal or is this a security issue together with network-
  manager?

  [   16.171766] audit: type=1400 audit(1422595680.679:68): apparmor="DENIED" 
operation="file_inherit" 
profile="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=2229 
comm="nm-dhcp-client." lport=10320 family="inet" sock_type="dgram" protocol=17
  [   16.171772] audit: type=1400 audit(1422595680.679:69): apparmor="DENIED" 
operation="file_inherit" 
profile="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=2229 
comm="nm-dhcp-client." lport=21985 family="inet6" sock_type="dgram" protocol=17
  [   16.199936] audit: type=1400 audit(1422595680.707:70): apparmor="DENIED" 
operation="file_inherit" 
profile="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=2246 
comm="nm-dhcp-client." lport=10320 family="inet" sock_type="dgram" protocol=17
  [   16.199943] audit: type=1400 audit(1422595680.707:71): apparmor="DENIED" 
operation="file_inherit" 
profile="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=2246 
comm="nm-dhcp-client." lport=21985 family="inet6" sock_type="dgram" protocol=17
  [   16.201369] audit: type=1400 audit(1422595680.707:72): apparmor="DENIED" 
operation="file_inherit" 
profile="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=2248 
comm="nm-dhcp-client." lport=10320 family="inet" sock_type="dgram" protocol=17
  [   16.201379] audit: type=1400 audit(1422595680.707:73): apparmor="DENIED" 
operation="file_inherit" 
profile="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=2248 
comm="nm-dhcp-client." lport=21985 family="inet6" sock_type="dgram" protocol=17
  [   17.206342] audit: type=1400 audit(1422595681.711:74): apparmor="DENIED" 
operation="file_inherit" 
profile="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=2468 
comm="nm-dhcp-client." lport=10320 family="inet" sock_type="dgram" protocol=17
  [   17.206349] audit: type=1400 audit(1422595681.711:75): apparmor="DENIED" 
operation="file_inherit" 
profile="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=2468 
comm="nm-dhcp-client." lport=21985 family="inet6" sock_type="dgram" protocol=17

  When I logon to KDE, KDE hangs sometimes  for 3sec at the login-
  process , when there is no internet connection (DSL modem did not
  dial-in yet).

  Thanks for your help!
  Best regards, Bernhard

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

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

[Touch-packages] [Bug 1439318] Re: Indicator can take over a whole screen app.

2015-04-01 Thread Michał Sawicz

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

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

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Michael Zanetti (mzanetti)

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

Title:
  Indicator can take over a whole screen app.

Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  STEPS:
  1. Install machine vs machines
  2. Start the app
  3. Start the game
  4. Tap on the play button bottom left
  5. if it pauses correctly try lapping slightly to the left of the play button
  6. The indicator shoot to the bottom of the page
  Repeat steps 2-6 but in gallery app and select an image so it is full screen

  EXPECTED:
  I expect to be able to interact with the whole app when it is full screen and 
the indicator to only appear on a drap down the page

  ACTUAL:
  Indicator shoots to the bottom of the page.  See video.

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

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

[Touch-packages] [Bug 1065427] Re: Dash previews cache cover-art images until unity restarts

2015-04-01 Thread Christopher Townsend

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

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

** Changed in: unity
 Assignee: Nick Dedekind (nick-dedekind) => (unassigned)

** Changed in: unity
Milestone: 7.3.3 => None

** Tags added: backlog

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

Title:
  Dash previews cache cover-art images until unity restarts

Status in Unity:
  Triaged
Status in unity package in Ubuntu:
  Triaged

Bug description:
  The dash preview art-work is cached by the icon loader until unity
  restarts. So the more you preview, the more memory is taken. This
  applies to all non-generated images, e.g. App preview screenshots,
  music album covers and file previews where an icon is shown.

  Desired solution is to cache only while the dash previews are open to
  help smooth navigation.

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

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

[Touch-packages] [Bug 1436626] Re: aptd crashed with SIGSEGV in _IO_vfprintf_internal()