foxtrotgps not compatible with newer kernel?

Bug #1770918 reported by Ri on 2018-05-13
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
FoxtrotGPS
Undecided
Unassigned

Bug Description

Hi, I cannot get Foxtrotgps to render the GPS location on the following;

Ubuntu 16.04 64bit
Lubuntu 16.04
Xubuntu 18.04
Peppermint 6
Peppermint 7

Maps cache is fine, it is just the GPS location indicator which is the issue.

I have an old machine running Ubuntu Natty 11.04 with Tangogps and that works perfectly.
I used to run Peppermint 3 on the same machine and that also worked with Foxtrot ok.

Output from terminal below;

riri@riri-VGN-FS415B:~$ foxtrotgps

(foxtrotgps:4781): Gtk-CRITICAL **: IA__gtk_toolbar_set_icon_size: assertion 'icon_size != GTK_ICON_SIZE_INVALID' failed

(foxtrotgps:4781): Gtk-CRITICAL **: IA__gtk_toolbar_set_icon_size: assertion 'icon_size != GTK_ICON_SIZE_INVALID' failed
REPOLIST == NULL
*** on_drawingarea1_configure_event():
pixmap created
Not autocentering map due to missing gps data
Not autocentering map due to missing gps data

(foxtrotgps:4781): Gtk-CRITICAL **: IA__gtk_entry_set_text: assertion 'GTK_IS_ENTRY (entry)' failed
connection to gpsd SUCCEEDED

_______________________________________________

Many thanks.

R.

On Sun, 2018-05-13 at 06:18 +0000, Ri wrote:

> foxtrotgps not compatible with newer kernel?

FoxtrotGPS doesn't use the Linux kernel for GPS locations.

> Not autocentering map due to missing gps data
> Not autocentering map due to missing gps data
>
> (foxtrotgps:4781): Gtk-CRITICAL **: IA__gtk_entry_set_text: assertion 'GTK_IS_ENTRY (entry)' failed
> connection to gpsd SUCCEEDED

Which host are you running gpsd on?

What are your GPSD settings in FoxtrotGPS?

Are the gpsd-clients tools working?

--
bye,
pabs

https://wiki.debian.org/PaulWise

Ri (ys99x) wrote :

"Hi Paul; I have tried leaving the gpsd host as default "localhost" and changed it to 127.0.0.1 as this was working with Tango. In both cases I left the port at 2847.

I can get some output from terminal gpsd -h I will see what output I get from gpsd -L etc; difficult as I do not know what I am doing!

R.

Try installing gpsd-clients and running gps, xgps, gpsmon or gpspipe to
debug what the gpsd daemon is outputting

Another debugging tool is gpscat, it connects directly to the device
without gpsd in between.

Another thing you could do is run gpsfake and have foxtrotgps connect
to it instead of gpsd. That would allow you to test foxtrotgps
independently of a working GPS device with gpsd support.

--
bye,
pabs

https://wiki.debian.org/PaulWise

Ri (ys99x) wrote :

SOLVED BY NEW GPS MOUSE

Thanks for your help with this; whatever I did with the old stick gps-clients only worked with Natty gpsd 2.94-2 but not with anything with gpsd 3.15-2. I checked both gpsd compatibilities and the list was nearly identical. My original GPS stick spec;

- Chipset: MTK ultra high sensitivity
- Sensitivity: -148dBm
- Operating system: Windows 2000, Windows XP, Windows Vista, Windows 7
- GPS receiving channel: 66 parallel channel
- Hot startup time: < 1 second
- Warm startup time: < 33 seconds
- Cold startup time: < 36 seconds
- Location accuracy: 3~5m
- Antenna: Built-in

Control type: Plug in and play

- Interfaces: USB 2.0
- Operating voltage: 3.0V~3.6V
- Operational altitude: < 18000m
- Operational velocity: < 515 m/s
- Operational acceleration: Less than 4g
- Authentication: RoHS compliant (Lead-free)
- Supports AGPS / WAAS / EGNOS

I finally gave up and as a last resort purchased a new U-Blox GPS mouse - and of course it now works fine on later 'buntu's but not on old Natty - so I guess it was a gpsd compatibility problem.

Thanks for your help - I have learned a lot about the GPS-clients since investigating.

Paul Wise (Debian) (pabs) wrote :

If you have the time it might be worth reporting this issue to the gpsd
upstream folks, seems this is a regression in gpsd 3.15-2 or earlier.

If you are comfortable with compiling gpsd from source, it might be
worth doing a `git bisect` between gpsd 2.94 and gpsd 3.15 so that
you can report exactly which commit introduced the problem.

https://git-scm.com/docs/git-bisect
https://git.savannah.gnu.org/cgit/gpsd.git
http://catb.org/gpsd/hacking.html

--
bye,
pabs

https://wiki.debian.org/PaulWise

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers