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
Seems this issue returns after updates. The Minknow GUI does not want to start upon mouseclick on the icon. Luckily starting it from the command line gives useful information. I had fixed it the same way before, but it reoccurred just now.
norman@MS-7E26:~$ /opt/ont/ui/kingfisher/MinKNOW\ UI
[7358:1121/123627.621464:FATAL:setuid_sandbox_host.cc(158)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I am aborting now. You need to make sure that /opt/ont/ui/kingfisher/chrome-sandbox is owned by root and has mode 4755.
Trace/breakpoint trap (core dumped)
norman@MS-7E26:~$ sudo chmod 4755 /opt/ont/ui/kingfisher/chrome-sandbox
the chmod fixed the issue.
The text was updated successfully, but these errors were encountered:
Great, thanks, and while I have your attention: It just happened to me that minion stopped sequencing my FLO114 after the first scheduled porescan about 1h 45 min in, claiming "0 pores available". I waited for 10 min and then manually hit "start porescan". It then found 57 pores (4 pores more than at the start of the run) and resumed the sequencing on 57 pores. Any idea what happened there? the same happened again at the next (2nd) schedule porescan 1.5 h later, where it again found no pores (0). It then set idle for ca 90 minutes until the next scheduled porescan. It then found 58 pores and sequenced happily ever after, with no subsequent porescan ever reading 0 again. Maybe a good idea to schedule the next porescan earlier when it erroneously/unexpectedly finds 0 pores.
Seems this issue returns after updates. The Minknow GUI does not want to start upon mouseclick on the icon. Luckily starting it from the command line gives useful information. I had fixed it the same way before, but it reoccurred just now.
the chmod fixed the issue.
The text was updated successfully, but these errors were encountered: