Timur Kristóf
Timur Kristóf
Can you guys confirm that this issue has been solved?
Hi, This repo is no longer being maintained since ACO was merged in upstream Mesa since late 2019. If you have issues with it, please open an issue in upstream...
Hi, This repo is no longer being maintained since ACO was merged in upstream Mesa since late 2019. If you have issues with it, please open an issue in upstream...
Hi, This repo is no longer being maintained since ACO was merged in upstream Mesa since late 2019. If you have issues with it, please open an issue in upstream...
Hi, This repo is no longer being maintained since ACO was merged in upstream Mesa since late 2019. If you have issues with it, please open an issue in upstream...
You don't need to restart. It is enough to long-press the network in the left pulley and disconnect / reconnect. However it really should reconnect automatically.
It's supposed to work, but many times it's unreliable. As we discussed on IRC, sometimes it just gives up and doesn't reconnect. I never quite figured out why, but it...
Nice work, so the issue is that it takes too long before a NetworkError is handled?
The command you execute on connect should be persistent.
@jpnurmi What's up with this? I think the quassel support should go to the backend (libcommuni or communi-shared maybe), and then just needs to be exposed from the UI.