Search Criteria
Package Details: forticlient 7.2.2.0753-1
Git Clone URL: | https://aur.archlinux.org/forticlient.git (read-only, click to copy) |
---|---|
Package Base: | forticlient |
Description: | An endpoint protection application |
Upstream URL: | https://www.forticlient.com |
Keywords: | forticlient |
Licenses: | custom |
Provides: | forticlient |
Submitter: | Harms |
Maintainer: | dnikoloski |
Last Packager: | dnikoloski |
Votes: | 16 |
Popularity: | 0.22 |
First Submitted: | 2018-10-29 20:50 (UTC) |
Last Updated: | 2023-10-23 08:31 (UTC) |
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 Next › Last »
oklein commented on 2020-04-03 07:19 (UTC)
The download fails because the range is not satisfiable. ** Resuming transfer from byte position 160474612 curl: (22) The requested URL returned error: 416
The URL is correct: https://repo.fortinet.com/repo/ubuntu/pool/multiverse/forticlient/forticlient_6.0.8.0140_amd64.deb
Do you how to change the build file to correct this?
Warepire commented on 2020-03-20 17:28 (UTC)
I thought I needed this package so I tried to re-direct it to use the system electron2 package and didn't see a segfault (though, very limited testing), but I did see some other wonky things like forticlient hanging if libappindicator-gtk2 is installed.
My attempt can seen here for those interested in continuing to tinker with it: https://github.com/Warepire/aur-forticlient
aminvakil commented on 2020-02-23 20:21 (UTC)
Any update on segmentation fault?
I used forticlient_6.0.6.0125_amd64.deb too, but it gives me the same error.
dmoebius commented on 2020-01-25 17:54 (UTC)
Got a similar stack trace. Played around with various ideas, e.g. using libnode.so from arch package electron2, or using the forticlient deb for Ubuntu 18 or CentOS, but nothing helped. :(
Here's mine stack trace:
Program terminated with signal SIGSEGV, Segmentation fault.
0 0x0000000000a4fa30 in ?? ()
(gdb) where
0 0x0000000000a4fa30 in ()
1 0x00007f9c086902b2 in node::http2::Http2Session::Callbacks::Callbacks(bool) () at /opt/forticlient/gui/FortiClient-linux-x64/libnode.so
2 0x00007f9c08690375 in () at /opt/forticlient/gui/FortiClient-linux-x64/libnode.so
3 0x00007f9c088eb72a in call_init.part () at /lib64/ld-linux-x86-64.so.2
Harms commented on 2019-11-21 17:13 (UTC) (edited on 2019-11-21 17:15 (UTC) by Harms)
Who knows what version of libnode.so they've bundled. Considering the nature of this software I'm uneasy about naively replacing any component of it. There's even a chance they've made some changes to it too.
Harms commented on 2019-11-21 17:11 (UTC) (edited on 2019-11-21 17:14 (UTC) by Harms)
Well the good news is I have the same issue now (I think...). The bad news is I'm not sure what to make of it. It seems it's the same issue as this: https://stackoverflow.com/questions/53084955/why-does-slack-return-a-segmentation-fault-after-fedora-29-upgrade
I get:
==35507== Process terminating with default action of signal 11 (SIGSEGV): dumping core
==35507== Bad permissions for mapped region at address 0xA4FA30
==35507== at 0xA4FA30: ??? (in /opt/forticlient/gui/FortiClient-linux-x64/FortiClient)
==35507== by 0x70FD2B1: node::http2::Http2Session::Callbacks::Callbacks(bool) (in /opt/forticlient/gui/FortiClient-linux-x64/libnode.so)
==35507== by 0x70FD374: ??? (in /opt/forticlient/gui/FortiClient-linux-x64/libnode.so)
==35507== by 0x583E729: call_init.part.0 (in /usr/lib/ld-2.30.so)
==35507== by 0x583E830: _dl_init (in /usr/lib/ld-2.30.so)
==35507== by 0x5830139: ??? (in /usr/lib/ld-2.30.so)
titao commented on 2019-11-18 16:36 (UTC)
i'm also having segmentation fault.
Harms commented on 2019-11-06 18:15 (UTC)
Is it still an issue? I haven't managed to reproduce this so far. The files it complains about are not part of the package.
alaz commented on 2019-10-18 17:41 (UTC) (edited on 2019-10-18 18:42 (UTC) by alaz)
Segmentation fault https://pastebin.com/6L2guDA7
It seems something related to [fortiClient_Home]/tls/haswell/ libs not being found. Or something about "/etc/gnutls/config" not being found.
moxin commented on 2019-10-07 09:46 (UTC)
Segmentation fault (core dumped)
« First ‹ Previous 1 2 3 4 5 6 Next › Last »