Linux version
No connection after update today. I upgraded to newest version (4.10.3) and it connected once then after update will not connect either.
WTF is going on with your software engineers?
This is not acceptable.
Yes, it seems software and programming has been a challenge as of late.
Have you reached out to Aillio directly?
What about reverting to an older version? For my part, I’ve started to save downloads of versions of RoasTime and Bullet R2 Pro firmware files just for this reason. You never know when you have to downgrade to avoid a bug with a new update.
I hear your frustration.
How about giving us some more info to work on?
Hardware used,
Linux version / build.
RoasTime software component versions (you can see these in settings)
etc etc etc…
The more info we have the faster we can solve this.
Hey,
As Jacob said, any info is helpful! Here are a few things to try:
- Checking to make sure no processes were left open for some reason (using an Activity Monitor and searching for “roastime”)
- Restart your computer (maybe the USB was not released properly and we can no longer claim it)
- If the above fail, removing your roastime-comms dependency in
~/.config/roastime/depsand restarting RoasTime.
For what it is worth, we did add an option to Disable Updates in the Settings on the latest version to where you can manually choose to update or not.
Dell Optiplex 9010
Intel Core i3-2120
Linux Mint 20.3 Una
Kernel: 5.4.0-200-generic x86_64 bits
RoastTime v4.10.3
Current versions
ClientLatest v1.152.2v1.150.0 v1.150.0
Proxy serviceLatest v1.58.3v1.55.0 v1.55.0
Communication serviceLatest v2.5.1v2.2.6 v2.2.6
Bullet R2
SN 007381
Firmware: ROASTER NOT CONNECTED
Also…
Everytime I run it it says it’s applyihg updates. I can run it a dozen times in a row and every time it says it’s appying updates. It seems it never finishes applying updates.
Have you tried completely erasing the app from your PC and do a clean re-install?
Have you tried completely erasing the app from your PC and do a clean re-install?
Many times
I just now downloaded 4.10.3 again
Same as before. Works first time, Then after restarting app it is disconnected.
I even disabled updates in the settings and it updated anyhow.,
Right now, the only way to use it is to reinstall EVERY TIME I USE IT
- Checking to make sure no processes were left open for some reason (using an Activity Monitor and searching for “roastime”)
- Restart your computer (maybe the USB was not released properly and we can no longer claim it)
- If the above fail, removing your roastime-comms dependency in
~/.config/roastime/depsand restarting RoasTime.For what it is worth, we did add an option to Disable Updates in the Settings on the latest version to where you can manually choose to update or not.
Right now, what I am doing is leaving the downloaded file in the download folder and copying it to an apps folder. I can change the executable permission on the newly copied file and run it, and it connects without changing anything else.
It downloads an update before I can disable updates in the settings. And then the next time the app is started it applies the update, ignoring the disable updates setting. And then it won’t connect to the Bullet anymore.
The fact that all I have to do is copy the unmolested file into the apps folder and run it in order to connect to the Bullet tells me this has nothing to do with dependencies or open processes or the USB not being released, etc.
What good is that setting to disable updates if the update is downloaded before you can change that setting?
Is there a config file I can edit somewhere before running the app?
This is the SECOND TIME that updates have disabled the software.The first time the app was crashing after the update. Did your software engineers come from Microsoft?
OK, so here is what I did.
I erased all roatime folders in .config
I copied an unmolested v4.10.3 file to apps
I unplugged the network cord
I ran v4.10.3 and let it rebuild dependencies (done this a number of times before,but that alone didn’t fix anything)
When it got to the login, I put in my username and password and hit “login”
I reconneced the network cord just long enough for the authentication then unplugged it again.
I went in and disabled updates in the settings.
I shut down the app.
I plugged the network cord back in
I restarted the app
No more updates, and NO MORE PROBLEMS
I am a retired IT director. I started doing programming in the 1970s. There is one rule that has always served me well:
IF IT AIN’T BROKE, DON’T FIX IT!!!
2 Likes
Hey,
Apologies you are having issues and happy to hear you got this resolved, but from your previous message, it looks like the comms dependency is stuck in an update loop (Which is why it is not connecting. It is not the actual release, but the update failing for some reason)
Communication service (Latest v2.5.1) v2.2.6
FWIW - I develop on Arch, but I do not officially test on any other distro, so we do not guarantee it will work (even though it is an AppImage and should). We officially support Windows and MacOS, but unfortunately our Linux user base is small enough that it doesn’t get as much love.
We definitely want to understand what is actually happening on your end, so if you ever have time - let me know and we can debug. As a retired programmer, I am sure you can understand the difficulty and nuances when developing programs for multiple platforms and architectures.
I’ll get back to you tomorrow (actually it’s already tomorrow, but I’m going to bed now)
Let me know when a good time is (Eastern time)
I am very familiar with cross platform development, but that was, as they say, a long time ago in galaxy far far away 