We also have crashes in the following way:
(gdb) bt
#0 0x0000004c in ?? ()
#1 0xb6c8527e in operator() (__args#0=@0xb170196c: false, this=0xb1701980) at
/usr/include/c++/4.9/functional:2439
#2 core::Property<bool>::set (this=0xb1701968, new_value=<optimized out>) at
/usr/include/core/property.h:147
#3 0xb6c7cd92 in operator= (rhs=@0xb4afe998: false, this=0xb1701968) at
/usr/include/core/property.h:82
#4 detail::CachedRadioCell::on_network_registration_property_changed
(this=0xb17018d0, tuple=...)
at
/build/buildd/location-service-2.1+14.10.20141013/src/location_service/com/ubuntu/location/connectivity/cached_radio_cell.cpp:495
#5 0xb6ca0d48 in
core::dbus::Signal<org::Ofono::Manager::Modem::NetworkRegistration::PropertyChanged,
std::tuple<std::string, core::dbus::types::Variant> >::operator() (
this=0x1759550, msg=...) at /usr/include/core/dbus/impl/signal.h:343
#6 0xb6e1f546 in ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
#7 0xb6e15d54 in ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
#8 0xb6e14572 in
core::dbus::Bus::handle_message(std::shared_ptr<core::dbus::Message> const&) ()
from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
#9 0xb6e1460e in ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
#10 0xb6a202e2 in dbus_connection_dispatch () from
/lib/arm-linux-gnueabihf/libdbus-1.so.3
#11 0xb6e2c9c8 in ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
#12 0xb6e2a4d8 in ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
#13 0xb6e2a7b6 in ?? () from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
#14 0xb6e13958 in core::dbus::Bus::run() () from
/usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
#15 0xb6bf0360 in ?? () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
#16 0xb6c27f98 in start_thread () from /lib/arm-linux-gnueabihf/libpthread.so.0
#17 0xb6ae322c in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Whichs is not realted to the previous backtrace.
--
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
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
