plasma-desktop crashed with SIGSEGV in gps_sock_read()

[piotrekw1]

after instalation kde-desktop

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: plasma-desktop 4:4.7.3a-0ubuntu4.1
ProcVersionSignature: Ubuntu 3.2.0-4.10-generic 3.2.0-rc5
Uname: Linux 3.2.0-4-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.90-0ubuntu1
Architecture: amd64
Date: Tue Dec 13 21:59:30 2011
ExecutablePath: /usr/bin/plasma-desktop
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111130.1)
ProcCmdline: /usr/bin/plasma-desktop --nocrashhandler
ProcEnviron:
 PATH=(custom, no user)
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f97f7f03a1e <gps_sock_read+46>: cmpb $0xa,0x10(%r12)
 PC (0x7f97f7f03a1e) ok
 source "$0xa" ok
 destination "0x10(%r12)" (0x000001a1) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: kde-workspace
StacktraceTop:
 gps_sock_read () from /usr/lib/x86_64-linux-gnu/libgps.so.20
 gps_read () from /usr/lib/x86_64-linux-gnu/libgps.so.20
 ?? () from /usr/lib/kde4/plasma-geolocation-gps.so
 ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
 ?? () from /usr/lib/nvidia-current/libGL.so.1
Title: plasma-desktop crashed with SIGSEGV in gps_sock_read()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 gps_sock_read (gpsdata=0x3bfb200) at libgps_sock.c:154
 gps_read (gpsdata=0x3bfb200) at libgps_core.c:144
 Gpsd::run (this=0x3be7660) at ../../../../../plasma/generic/dataengines/geolocation/location_gps.cpp:55
 QThreadPrivate::start (arg=0x3be7660) at thread/qthread_unix.cpp:331
 ?? ()

[Miriam España Acebal (mirespace)]

Hi,

While doing some bug cleanup, I found this old bug.

First of all, thank you for reporting this bug to Ubuntu.

Ubuntu 12.04 (precise) reached end-of-life on April 28 2017, so I'm afraid this bug can't be fixed. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner, but it appears to be no further action possible at this time.

Due to the above, I'm marking this bug as "Won't fix".