search

v1cont / yad

Yet Another Dialog
GNU General Public License v3.0
686 stars 57 forks source link

7.2: --field="":LBL "" causes segfault or hangs #105

Open Antiquete opened 4 years ago

Antiquete commented 4 years ago

Tested on version 7.2 from yad-git through Arch User Repository

Antiquete commented 4 years ago

Workaround mentioned in #100 seems to work on this issue as well. Using " " instead of "" avoids the segfaults.

v1cont commented 4 years ago

both yad --form --field '':lbl and yad --form --field ':lbl' works fine for me. can you show complete example that reproduce the bug?

Antiquete commented 4 years ago

Sorry for late reply, here's the output from my end. I tried running all these 3 commands in terminal and all of them seem to result in segmentation fault.

% yad --field="":LBL ""
[1]    50210 segmentation fault (core dumped)  yad --field="":LBL ""
% yad --form --field '':lbl
[1]    50580 segmentation fault (core dumped)  yad --form --field '':lbl
% yad --form --field ':lbl'
[1]    50712 segmentation fault (core dumped)  yad --form --field ':lbl'

% yad --field=" ":LBL " " runs without issues though and launches a window with cancel and ok button.

can you show complete example that reproduce the bug?

I was encountering this while using steamtinkerlaunch which uses yad for gui but worked around it by placing a space in between quotes.

I am using the following yad version btw and from this repository.

% yad --version
7.2 (GTK+ 3.24.23)

I don't know if this is distro or DE specific or not, but I am using KDE and tried both on manjaro and arch with same results.

Thanks for looking into this, do tell me if you need any other logs from my side.

v1cont commented 4 years ago

please check latest git

frostworx commented 3 years ago

Hi, I'm the author of above mentioned steamtinkerlaunch. Hope @Antiquete is fine. I could not reproduce this issue when it came up first on my side. Using Arch as well, but not using yad-git from AUR.

The AUR PKGBUILD has other build options than the official one, but as both work here, maybe simply some dependency was broken when yad-git was built when the issue came up.