This bug was fixed in the package gpsd - 3.25-3ubuntu3.1
---
gpsd (3.25-3ubuntu3.1) noble; urgency=medium
* d/p/lp-2076191-*: Fix gpsmon crash in NMEA (LP: #2076191)
-- Christian Ehrhardt Wed, 04 Dec
2024 11:36:00 +0100
** Changed in: gpsd (Ubuntu Noble)
Status: Fix Comm
This bug was fixed in the package gpsd - 3.25-4ubuntu0.1
---
gpsd (3.25-4ubuntu0.1) oracular; urgency=medium
* d/p/lp-2076191-*: Fix gpsmon crash in NMEA (LP: #2076191)
-- Christian Ehrhardt Wed, 04 Dec
2024 11:34:30 +0100
** Changed in: gpsd (Ubuntu Oracular)
Status: Fi
After a do-release-upgrade to oracular I was on
ubuntu@nuc:~$ apt policy gpsd
gpsd:
Installed: 3.25-4
Candidate: 3.25-4
Version table:
3.25-4ubuntu0.1 100
100 http://de.archive.ubuntu.com/ubuntu oracular-proposed/main amd64
Packages
*** 3.25-4 500
500 http://de.archiv
Before upgrading to Oracular it was too easy to test noble to not also
do it
Verified the bug still happened before
ubuntu@nuc:~$ apt policy gpsd
gpsd:
Installed: 3.25-3ubuntu3
Candidate: 3.25-3ubuntu3
Version table:
3.25-3ubuntu3.1 100
100 http://de.archive.ubuntu.com/ubuntu n
Thank you Mario and Nico,
updating the verification tags for Noble per your feedback and myself testing
Oracular then to be complete.
** Tags removed: verification-needed-noble
** Tags added: verification-done-noble
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Noble release tested on ARM64 hardware and works, error is not present
anymore / gpsmon does not crash anymore on NMEA data.
Test:
- Started gpds with GPSD_OPTIONS=" -b -n -p -s 38400 " to deny it to talk to
the gps receiver so that it stays on NMEA data format
- Started gpsmon and received corre
Hello Mario, or anyone else affected,
Accepted gpsd into oracular-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/gpsd/3.25-4ubuntu0.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.
Thank you Mario and Nico,
that is enough for now - thanks for checking my PPA.
I've uploaded it to the latest Ubuntu where it is already fixed now.
Furthermore I uploaded the fix to noble and oracular -unapproved. There it now
waits for SRU handling [1].
Once picked up there by the SRU team they
Am 04. Dez 2024, um 10:48:14 schrieb Christian Ehrhardt :
>
> I built a new PPA with what we could SRU if you can confirm this now to
> be working better.
>
> PPA: https://launchpad.net/~paelzer/+archive/ubuntu/lp-2076191-fix-
> crashes-in-nmea0183
>
> I've three MRs to review once the pre-test
Sorry, my bad, there were still parts of gpsd-clients and the old libgps
packages installed.
I removed them now and installed from your PPA, this is working now, yes! :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
I tried to install your ppa but it did not work:
The following packages have unmet dependencies:
gpsd : Depends: libgps30t64 (= 3.25-3ubuntu3.1~nobleppa2) but
3.25-3ubuntu4~noble1 is to be installed
E: Unable to correct problems, you have held broken packages.
Currently running on
Distributor
Fixes pre-tested and uploaded to -unapproved
** Description changed:
[ Impact ]
* There are two bugs in gpsd that break gpsmon on noble. On one hand a re-use
of freed resources and on the other a compile issue with fortify source.
One leads to a crash, the other to an assertio
This bug was fixed in the package gpsd - 3.25-4ubuntu1
---
gpsd (3.25-4ubuntu1) plucky; urgency=medium
* d/p/lp-2076191-*: Fix gpsmon crash in NMEA (LP: #2076191)
-- Christian Ehrhardt Wed, 04 Dec
2024 11:31:36 +0100
** Changed in: gpsd (Ubuntu)
Status: Triaged => Fix Re
** Changed in: gpsd (Ubuntu)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2076191
Title:
gpsmon crashes (segfault)
To manage notificat
I've uncovered a few (3) old GPS receivers and might be able to recreate this:
Is that how it looks for you?
$ gpsmon
tcp://localhost:2947 JSON slave driver>
(82)
{"class":"VERSION","release":"3.25","rev":"3.25","proto_major":3,"proto_minor":15}
(313)
{"class":"DEVICES","devices":[{"cla
** Description changed:
+ [ Impact ]
+
+ * There are two bugs in gpsd that break gpsmon on noble. On one hand a
re-use
+ of freed resources and on the other a compile issue with fortify source.
+ One leads to a crash, the other to an assertion.
+
+ * Upstream has fixes for that, and
Thanks for spotting that Nico!
Sadly there are plenty of style and strnlen related changes in the context, so
the backports are a bit bigger than I was hoping - but still it should be just
what we want for this bug.
I built a new PPA with what we could SRU if you can confirm this now to
be worki
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/gpsd/+git/gpsd/+merge/477724
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/gpsd/+git/gpsd/+merge/477725
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+sou
Latest release does fix the issue, it was a compiler bug:
https://gitlab.com/gpsd/gpsd/-/commit/67f33e815b6209cdbe1ffe438e8bfeffdbb89d1b
So this could be packaged as a new release?
@ahasenack, @mitchdz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
One of the last commits deprecated gpsmon:
https://gitlab.com/gpsd/gpsd/-/commit/182bfaf4271059af8393c3043848a6b8acd88d38
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2076191
Title:
gpsmon crashes
@Mitchell Um, no its... not. It then changes again from Assertion to Core Dump
after Buffer Overflow. Reason, I am quite sure now, is the newer ncurses
version on Ubuntu 24.04 LTS. Because, if you run gpsmon --nocurses it will work
right away with your PPA. Same with my newly build version.
I o
Nico, are you able to test the latest upstream and see if it's fixed
there?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2076191
Title:
gpsmon crashes (segfault)
To manage notifications about this
Yeah I concur, I am glad that still gpsd at least works, but gpsmon
would be an important tool to also judge the quality of data, so it
would be nice if Ubuntu would be able to ship working packages for it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Ok, so we advanced from a segfault-at-start, to an assertion-crash-at-
start :/
So we need another fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2076191
Title:
gpsmon crashes (segfault)
To ma
@Andreas I installed it and I can say that starting gpsmon now directly
results in a crash and output "gpsmon: assertion failure, probable I/O
error". I don't know, its an ARM64 system and it installed following
packages:
Get:1 https://ppa.launchpadcontent.net/mitchdz/gpsd-avoid-double-delwin/ubun
Let's deal with the problem we have a confirmed fix for.
@Nico, can you also confirm that the package from the ppa[1] fixes the
issue for you?
1. https://launchpad.net/~mitchdz/+archive/ubuntu/gpsd-avoid-double-delwin
** Changed in: gpsd (Ubuntu)
Status: Incomplete => Confirmed
** Chang
Just found this bug report after installating gpsd on Ubuntu 24.04 LTS with
current packages and can confirm gpsmon segfault is occuring as soon as you try
to open it.
Any fix for that in route?
Thanks a lot!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
Great to hear back from you Mario.
I'd suggest opening an upstream bug for the reconnect issue.
Regarding the assertion error, I wasn't able to immediately pin down the
commit that would fix that. Happen to have a commit you'd like me to try
to add to the PPA?
--
You received this bug notificat
Bryce,
I can report the following:
Am 14. Aug 2024, um 15:22:30 schrieb Bryce Harrington:
> Mario, can you provide a log showing the assertion failure?
It simply says:
gpsmon: assertion failure, probable I/O error
Or with gpsmon -D5 to provide some more details:
gpsmon:INFO: startup at 2024-08
Hello Bryce,
That is why I mentioned it. Problem is just I am on a business trip and
will not be home until sunday, so no logs until then.
The bright side is that according to
shipping status notifications another (different) GPS module has arrived
at home. So early next week I will hopefully have
Mario, can you provide a log showing the assertion failure?
Given the patch is not yet provided in an upstream release, it may be
worth discussing the issue with upstream, to ensure the resulting patch
is one that'll be safe to ship.
** Tags removed: bitesize
** Changed in: gpsd (Ubuntu)
Interesting. Glad to see the segfault is resolved, but that's not
friendly with the assertion failure. Please keep us posted!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2076191
Title:
gpsmon cras
Hi Mitchell,
I have installed the PPA and it seems to solve the issue, no segfault
anymore.
I however do now see an assertion failure if I turn off the GPS and then
turn it on again. I'll see if I can investigate this over the weekend to
find out if this is related or a different issue. I'll keep
Hi, I've kicked off a build in my PPA here[0].
Mario, feel free to test the package in my PPA once it finishes building
(should hopefully take about 4-5 hours from the time I'm making this
comment.
This is different from the -proposed pocket validation, I'm just making
sure it builds in LP :)
[0
Hello, as long as you are willing to help with verifying the fix once it
lands in the Ubuntu -proposed pockets, I think we can work on delivering
a fix.
73 de Paride IZ3SUS
** Changed in: gpsd (Ubuntu)
Status: Incomplete => Triaged
** Tags added: server-todo
** Tags added: bitesize
--
Since this is the only GPS hardware I have here at the moment, I can not know
if it only affects my hardware.
I had gdb'd the issue down and it was obvious enough. I then found that it has
been already been fixed in upstream gpsd gitlab -master.
I only assume that this is triggered only under ce
Thank you for taking the time to report a bug and improve Ubuntu.
It is good to know that you can reproduce this problem locally and have
also checked that the upstream patch seems to fix it. If I understand
correctly, it's not possible to trigger the issue without having
specific GPS hardware, r
37 matches
Mail list logo
