Package Details: flightradar24 1.0.34-1

Git Clone URL: https://aur.archlinux.org/flightradar24.git (read-only, click to copy)
Package Base: flightradar24
Description: Feeder software for Flightradar24.com (fr24feed)
Upstream URL: https://www.flightradar24.com/share-your-data
Licenses: custom
Submitter: yuvadm
Maintainer: jimmyxu
Last Packager: jimmyxu
Votes: 7
Popularity: 0.000000
First Submitted: 2014-03-13 15:31 (UTC)
Last Updated: 2023-01-19 15:56 (UTC)

Latest Comments

1 2 3 4 Next › Last »

hotaru commented on 2020-08-22 05:33 (UTC)

looks like 1.0.25-4 fixed the segmentation fault on x86_64.

a36233 commented on 2019-12-26 11:54 (UTC) (edited on 2019-12-26 12:28 (UTC) by a36233)

systemd-coredump[875]: Process 865 (fr24feed) of user 991 dumped core.

                                            Stack trace of thread 865:
                                            #0  0x00007fd054badf43 n/a (/usr/lib/libnss_resolve.so.2 + 0x6f43)
                                            #1  0x00007fd054bba47e n/a (/usr/lib/libnss_resolve.so.2 + 0x1347e)
                                            #2  0x00007fd054bd9109 n/a (/usr/lib/libnss_resolve.so.2 + 0x32109)
                                            #3  0x00007fd054bd9395 n/a (/usr/lib/libnss_resolve.so.2 + 0x32395)
                                            #4  0x00007fd054bd9966 n/a (/usr/lib/libnss_resolve.so.2 + 0x32966)
                                            #5  0x00007fd054bdcf61 _nss_resolve_gethostbyname3_r (/usr/lib/libnss_resolve.so.2 + 0x35f61)
                                            #6  0x00007fd054bdd66a _nss_resolve_gethostbyname_r (/usr/lib/libnss_resolve.so.2 + 0x3666a)
                                            #7  0x00000000009633af n/a (/usr/bin/fr24feed + 0x5633af)
                                            #8  0x0000000000962b4f n/a (/usr/bin/fr24feed + 0x562b4f)
                                            #9  0x000000000049781c n/a (/usr/bin/fr24feed + 0x9781c)
                                            #10 0x000000000041c097 n/a (/usr/bin/fr24feed + 0x1c097)
                                            #11 0x00000000008cb350 n/a (/usr/bin/fr24feed + 0x4cb350)
                                            #12 0x00000000004185ea n/a (/usr/bin/fr24feed + 0x185ea)

                                            Stack trace of thread 867:
                                            #0  0x00000000007d4f94 n/a (/usr/bin/fr24feed + 0x3d4f94)
                                            #1  0x00000000008f7518 n/a (/usr/bin/fr24feed + 0x4f7518)
                                            #2  0x00000000008fac22 n/a (/usr/bin/fr24feed + 0x4fac22)
                                            #3  0x00000000008f1e6a n/a (/usr/bin/fr24feed + 0x4f1e6a)
                                            #4  0x00000000008f154b n/a (/usr/bin/fr24feed + 0x4f154b)
                                            #5  0x000000000049ce89 n/a (/usr/bin/fr24feed + 0x9ce89)
                                            #6  0x00000000007cfb72 n/a (/usr/bin/fr24feed + 0x3cfb72)
                                            #7  0x0000000000960bdf n/a (/usr/bin/fr24feed + 0x560bdf)

                                            Stack trace of thread 866:
                                            #0  0x00000000007d3ba5 n/a (/usr/bin/fr24feed + 0x3d3ba5)
                                            #1  0x00000000004a510a n/a (/usr/bin/fr24feed + 0xa510a)
                                            #2  0x00000000004a5530 n/a (/usr/bin/fr24feed + 0xa5530)
                                            #3  0x00000000008098df n/a (/usr/bin/fr24feed + 0x4098df)
                                            #4  0x00000000007cfb72 n/a (/usr/bin/fr24feed + 0x3cfb72)
                                            #5  0x0000000000960bdf n/a (/usr/bin/fr24feed + 0x560bdf)

jimmyxu commented on 2019-11-24 07:58 (UTC)

@test0 I'm drawing a blank on the scheme as there were days where even the pkgver of amd64 and armhf differed. I initially thought about 1.0.24_5_7-1 but considered it a tad messy. So if you have any ideas.

test0 commented on 2019-11-23 07:11 (UTC)

Will be possible to add a sub-revision number in order not to mess up with the official release number and differentiate between architectures?

jimmyxu commented on 2019-11-22 17:27 (UTC) (edited on 2019-11-22 18:26 (UTC) by jimmyxu)

Just added a hostname script to hopefully get rid of the "invalid option -- 'I'" warning. Please let me know if I borked anything.

From my testing, the only latest thing working on x86_64 right now is their i386 version (fr24feed_1.0.24-5_i386). Disabling mlat does not help.

So if you want to run that, just change source_x86_64 and sha256sums_x86_64 to read the same as _i686.

hotaru commented on 2019-11-19 08:32 (UTC)

update: just got a response to the message I sent via the contact form. apparently they think clearing cookies and cache in my browser is going to somehow fix fr24feed segfaulting on a completely different machine.

hotaru commented on 2019-11-18 21:40 (UTC)

looks like posting on their forum just resulted a flood of off-topic spam and trolls defending the spam.

I did manage to find a contact form on the flightradar24 site, and reported the bug that way as well. I don't have high hopes for it being fixed, though.

hotaru commented on 2019-11-07 21:41 (UTC)

@frankenstein20 you can check out old commits from AUR to build an older version of the package.

frankenstein20 commented on 2019-11-07 21:38 (UTC)

Unfortunately I also did an update and don't have an old package anymore. I'm also getting a segmentation fault. With these two packages I have the problem flightradar24-1.0.24-5-x86_64.pkg.tar.xz and flightradar24-1.0.24-6-x86_64.pkg.tar.xz.

jimmyxu commented on 2019-11-07 11:33 (UTC)

@test0 I've put the name in the description so at least searching should work better now.

1 2 3 4 Next › Last »