Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

minknow GUI not starting ubuntu 24 #70

Open
warthmann opened this issue Nov 21, 2024 · 2 comments
Open

minknow GUI not starting ubuntu 24 #70

warthmann opened this issue Nov 21, 2024 · 2 comments

Comments

@warthmann
Copy link

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.

@0x55555555
Copy link
Contributor

Hi @warthmann - we have fixes planned for this in the upcoming release of minknow.

Thanks,

  • George

@warthmann
Copy link
Author

warthmann commented Nov 21, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants