When you shut down your computer or your terminal window with Toaster still running, when you next try to start it up you must kill it and restart it. Toaster should shut down gracefully when the terminal window is closed or the computer is shut down.
On dora-toaster:e5cf3e598e1e36b87a6cb07829f8a5013d78f534 This works wonderfully if I close my terminal window while Toaster is running, then: 1. open a new terminal 2. set up my build environment 3. type the toaster start command. It still reports a bitbake lock state error if I close my terminal window while Toaster is running, then: 1. open a new terminal 2. set up my build environment 3. type the toaster stop command If I issue the toaster stop command when toaster is not running, I would expect to be told: "Toaster is not running so it cannot be stopped. Would you like to start Toaster? [y/n]" kind of thing.
After the latest changes to bin/bitbake from Jason Wessel, the server is stopped when attempting to launch oe-init-build-env from another terminal. This leads to an inconsistency in setup and failure of toaster. Using this bug to track all the problems related to starting toaster.
Patches submitted for review.
Any update about these patches, I'm still experiencing the problem with the latest toaster/master
This patch was submitted for review with the set of patches for Toaster build functionality, but probably will not be merged in 1.6.
Simplified patch submitted for review. This patch just forces a toaster shutdown on the stop command.
Merged into origin/master.
Created attachment 1832 [details] lock state error message This is how the new error message looks like. Jessica, Paul: feel free to comment as needed.
This isn't the fix we discussed. What we discussed was toaster starting what needs to be started even if part of it is running, with a warning if some previous (known invalid) state is present.
A new bug will be opened for this issue and I will set this as verified.