You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Last VPS update, along with OpenBG 5.3.013 update, causes a crash if you want to change the channel, at the moment you want to create a timer.
I mean: you create a new timer (for instance starting from EPG, you want to change the channel (for instance to avoid conflicts between timers), you choose the alternative and, when you press OK the image crashes.
Not only that: there are many blank lines showing up at the bottom of the timer lines, before the last one (just the VPS-related one).
I tried to remove the plugin and reinstall, also using force reinstall option, and nothing changed.
Obviously, when you uninstall the plugin, the timer's creation goes well.
The text was updated successfully, but these errors were encountered:
P.S. To be more detailed: if you create a new timer, regardless of the way (from EPG or manually) and if you don't TRY and change the channel, the only issue are the many blank lines at the bottom, before the VPS specific one.
But if you want to choose a different channel from the one automatically used by the new timer, then you have the crash. Enigma2_crash_2023-12-07_20-18-30.txt
Last VPS update, along with OpenBG 5.3.013 update, causes a crash if you want to change the channel, at the moment you want to create a timer.
I mean: you create a new timer (for instance starting from EPG, you want to change the channel (for instance to avoid conflicts between timers), you choose the alternative and, when you press OK the image crashes.
Not only that: there are many blank lines showing up at the bottom of the timer lines, before the last one (just the VPS-related one).
I tried to remove the plugin and reinstall, also using force reinstall option, and nothing changed.
Obviously, when you uninstall the plugin, the timer's creation goes well.
The text was updated successfully, but these errors were encountered: