touch-packages team mailing list archive

[Manuel de la Peña <manuel.delapena@xxxxxxxxxxxxx>]

I have been looking into the issue and when gdb attached I get the
following:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb4aff3c0 (LWP 9459)]
0xb6c2d7c2 in pthread_mutex_lock () from /lib/arm-linux-gnueabihf/libpthread.so.0
(gdb) bt
#0  0xb6c2d7c2 in pthread_mutex_lock () from /lib/arm-linux-gnueabihf/libpthread.so.0
#1  0xb6c83eb8 in __gthread_mutex_lock (__mutex=<optimized out>) at /usr/include/arm-linux-gnueabihf/c++/4.9/bits/gthr-default.h:748
#2  std::mutex::lock (this=<optimized out>) at /usr/include/c++/4.9/mutex:135
#3  0xb6c890e2 in lock_guard (__m=..., this=<synthetic pointer>) at /usr/include/c++/4.9/mutex:377
#4  core::Signal<bool>::operator() (this=0x18d3050, args#0=<optimized out>) at /usr/include/core/signal.h:134
#5  0xb6c80d92 in operator= (rhs=@0xb4afe998: true, this=0x18d3028) at /usr/include/core/property.h:82
#6  detail::CachedRadioCell::on_network_registration_property_changed (this=0x18d2f90, tuple=...)
    at /build/buildd/location-service-2.1+14.10.20141013/src/location_service/com/ubuntu/location/connectivity/cached_radio_cell.cpp:495
#7  0xb6ca4d48 in core::dbus::Signal<org::Ofono::Manager::Modem::NetworkRegistration::PropertyChanged, std::tuple<std::string, core::dbus::types::Variant> >::operator() (
    this=0x18d29b8, msg=...) at /usr/include/core/dbus/impl/signal.h:343
#8  0xb6e23546 in ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
#9  0xb6e19d54 in ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
#10 0xb6e18572 in core::dbus::Bus::handle_message(std::shared_ptr<core::dbus::Message> const&) () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
#11 0xb6e1860e in ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
#12 0xb6a242e2 in dbus_connection_dispatch () from /lib/arm-linux-gnueabihf/libdbus-1.so.3
#13 0xb6e309c8 in ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
#14 0xb6e2e4d8 in ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
#15 0xb6e2e7b6 in ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
#16 0xb6e17958 in core::dbus::Bus::run() () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
#17 0xb6bf4360 in ?? () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
#18 0xb6c2bf98 in start_thread () from /lib/arm-linux-gnueabihf/libpthread.so.0
#19 0xb6ae722c in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)


The/A way to reproduce it is to start the location service and turn on and off the aerplane mode (with a sim that needs to be unlocked). 

** Changed in: location-service (Ubuntu)
       Status: New => Confirmed

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

Title:
  ubuntu-location-service crash

Status in “location-service” package in Ubuntu:
  Confirmed
Status in “unity8-desktop-session” package in Ubuntu:
  New

Bug description:
  Hallo
  Testing unity8-MIR image ubuntu-desktop-next in dmesg there was this repeated a bunch of times:

  [   13.446215] init: ubuntu-location-service main process (682) killed by SEGV signal
  [   13.446228] init: ubuntu-location-service main process ended, respawning
  [   13.454540] init: ubuntu-location-service main process (817) killed by SEGV signal
  [   13.454551] init: ubuntu-location-service main process ended, respawning

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: ubuntu-location-service-bin 1.0.0+14.10.20140630-0ubuntu1
  ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0
  Uname: Linux 3.15.0-6-generic x86_64
  ApportVersion: 2.14.3-0ubuntu2
  Architecture: amd64
  Date: Fri Jul  4 00:44:15 2014
  InstallationDate: Installed on 2014-07-03 (0 days ago)
  InstallationMedia: Ubuntu-Desktop-Next 14.10 "Utopic Unicorn" - Alpha amd64 (20140703)
  SourcePackage: location-service
  UpgradeStatus: No upgrade log present (probably fresh install)

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