-
-
Notifications
You must be signed in to change notification settings - Fork 315
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Segmentation fault after the latest update 4.7.1 #371
Comments
Is it regular or occurs time to time? |
yep it is regular. |
building from source runs the ui
|
Wifi interface is blocked due to |
Having the same crash despite iw being installed |
What's the path of that config file? @awsms |
/etc/create_ap.conf I think. Thread 1 "wihotspot-gui" received signal SIGSEGV, Segmentation fault.
__strcmp_avx2 () at ../sysdeps/x86_64/multiarch/strcmp-avx2.S:283
283 VMOVU (%rdi), %ymm0
(gdb) bt
#0 __strcmp_avx2 () at ../sysdeps/x86_64/multiarch/strcmp-avx2.S:283
#1 0x0000555555558fba in init_ui_from_config () at ui/ui.c:562
#2 0x0000555555558c6c in initUi (argc=1, argv=0x7fffffffe2c8) at ui/ui.c:492
#3 0x0000555555557929 in main (argc=1, argv=0x7fffffffe2c8) at ui/main.c:34
(gdb) f 1
#1 0x0000555555558fba in init_ui_from_config () at ui/ui.c:562
562 if(strcmp(values->ieee80211ax,"1")==0){ Archlinux's package manager(pacman) does not automatically merge configuration files, and newer code will get null pointer errors when reading configuration options that don't exist in older versions. --- /etc/create_ap.conf 2023-12-31 19:42:36.221605149 +0800
+++ /etc/create_ap.conf.pacnew 2024-01-15 16:13:55.000000000 +0800
@@ -11,7 +11,8 @@
ISOLATE_CLIENTS=0
SHARE_METHOD=nat
IEEE80211N=0
-IEEE80211AC=1
+IEEE80211AC=0
+IEEE80211AX=0
HT_CAPAB=[HT40+]
VHT_CAPAB=
DRIVER=nl80211
@@ -20,12 +21,9 @@
FREQ_BAND=2.4
NEW_MACADDR=
DAEMONIZE=0
-DAEMON_PIDFILE=
-DAEMON_LOGFILE=/dev/null
-NO_HAVEGED=1
+NO_HAVEGED=0
WIFI_IFACE=wlan0
-INTERNET_IFACE=wlan0
-SSID=WifiShare
+INTERNET_IFACE=eth0
+SSID=MyAccessPoint
PASSPHRASE=12345678
USE_PSK=0
-ADDN_HOSTS= |
same issue
|
This is also segfaulting for me on arch linux under wayland. If I build either the |
As a temporary solution delete /etc/create_ap.conf and re-install the
package
…On Wed, 24 Jan 2024 at 01:16, Rob Shinn ***@***.***> wrote:
Is it regular or occurs time to time? Can you build it from source?
This is also segfaulting for me arch linux under wayland. If I build
either the master or lakinduakash-patch-3 branches from source I get the
segfault, but when I build lakinduakash-patch-2 from source I get the GUI.
—
Reply to this email directly, view it on GitHub
<#371 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADA2EXMSLJY4LJL7RUTO3W3YQAHRLAVCNFSM6AAAAABBKF5ZLCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBWHAYDSNBSGI>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***>
|
That worked. Thanks. |
Had the same issue on the AUR package and deleting /etc/create_ap.conf solved it. Wasnt expecting to have to delete /etc files to fix an issue though... |
It still broken without rm /etc/create_ap.conf.
|
Arch linux package is managed by @yochananmarqos |
@lakinduakash I just read the whole thread, this is obviously not a packaging issue. I cannot reproduce the issue, therefore I cannot help. |
From @bbaa-bbaa It seems like that issue is from the Arch Linux package manager which does not update the file. |
What is your distro? |
Thanks for the explanation @yochananmarqos . |
No, you're not. Just because it segfauted doesn't mean it's the same crash. You've hijacked this closed issue and now we're even on to a different subject. This is quite a mess. |
Maybe we should check for null pointers. |
Pop!_OS 22.04 |
Yup, simply adding |
getting this on arch linux wayland.
The text was updated successfully, but these errors were encountered: