The original one was the one where I restarted the backend. With the backend restarted and debugging in place to get a log that was the result. It went further through the driver install and locked up at 80%. But at the time it was the only way to get a log.
The last log is the one that shows up the original issue which is the window for download opens up after you use policykit and then jockey just stops.
Pitti
This log is the one in var/log/jockey.log
The original one was the one where I restarted the backend. With the backend restarted and debugging in place to get a log that was the result. It went further through the driver install and locked up at 80%. But at the time it was the only way to get a log.
The last log is the one that shows up the original issue which is the window for download opens up after you use policykit and then jockey just stops.
Hope that was well enough explained.