-
Notifications
You must be signed in to change notification settings - Fork 208
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
khal 0.11.3 with urwid 2.6.1 crashes on editing event #1340
Comments
@geier any ideas? khal is currently broken on Arch Linux due to this issue 😅 |
I can confirm this bug, but I'm not sure yet if this is an issue with khal or urwid. Still happens with urwid 2.6.7 |
This commit fixes the issue, but moves the export dialog to the top. But according to urwid's documentation, a value of |
I have submitted an issue at urwid/urwid#851 |
The issue is fixed with urwid 2.6.8. I might implement a workaround for urwid version 2.4.3-2.6.7, but no guarantees. |
@geier thanks for looking into this! I'll bump the urwid package on Arch Linux (in the hopes that it won't introduce regressions for other consumers 🥲 ) |
If upgrading urwid breaks something else, please ping me again. |
This was mostly meant "in regards to other packages using urwid". So far there have been no other complaints though, so I guess it's safe to say that this is fixed with 2.6.8! 🎉 |
Describe the bug
When pressing 'e' on an existing event in ikhal, the application crashes.
If applicable: Stack Trace
To Reproduce
Open ikhal, press 'e' on existing event.
Expected behavior
Khal does not crash.
Screenshots
n/a
OS, version, khal version and how you installed it:
pip freeze
]:python-atomicwrites
1.4.1-3
python-click
8.1.7-1
python-click-log
0.4.0-3
python-configobj
5.0.8-4
python-dateutil
2.8.2-6
python-icalendar
5.0.11-1
python-pytz
2024.1-1
python-pyxdg
0.28-2
python-tzlocal
5.2-1
python-urwid
2.6.1-1
Additional context
Add any other context about the problem here. Especially, if the issue came up when reading an .ics file, please provide the content of that file (anonymize if needed).
The text was updated successfully, but these errors were encountered: