-
Notifications
You must be signed in to change notification settings - Fork 625
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
[BUG] "input buffer overflow, can't enlarge buffer because scanner uses REJECT" when using error dialog for large text #1855
Comments
That is a lot of text for an error box, a use case I never expected. |
It worked in 2020 and after some update stopped working. |
I think we need a more fundamental fix for this. Passing > 14kbyte as an argument is not the best way to do this. maybe |
|
Thanks! I tested both cases. And they both work. text=$(curl "http://wttr.in/Тольятти?lang=ru" | sed "s/[ \t]$//" | ansifilter --ignore-csi --pango --font="Liberation Mono" --font-size=15) works after commit 635fbd0 curl "http://wttr.in/Тольятти?lang=ru" | sed "s/[ \t]$//" | ansifilter --ignore-csi --pango --font="Liberation Mono" --font-size=15 works after commit 7814da7 |
Thanks for testing. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Rofi version (rofi -v)
Version: 1.7.5
Configuration
https://gist.github.com/itspec-ru/0c5cb29341c5e51bc2a1deb5aaf68c60
Theme
https://gist.github.com/itspec-ru/9fa95059076302b65602461079938966
Timing report
No response
Launch command
rofi -theme bw -markup -e "${text}"
Step to reproduce
preparing Pango Markup Text of a sufficiently large size
using error dialog for display text
Expected behavior
Some time ago it worked and broke after the update.
Actual behavior
an error has occurred
input buffer overflow, can't enlarge buffer because scanner uses REJECT
Additional information
If the same text is first output to a file and truncated, the program will display it correctly.
Using wayland display server protocol
I've checked if the issue exists in the latest stable release
The text was updated successfully, but these errors were encountered: