screenBloom icon indicating copy to clipboard operation
screenBloom copied to clipboard

Opens Safari or Firefox rather than default browser on Mac

Open humanthrope opened this issue 7 years ago • 3 comments

First time install of version 2.2 causes Safari to launch on Mac OS X Sierra rather than the default browser (Chrome). On my laptop (also running Sierra) where Firefox is installed, that is opened rather than Safari or my default browser.

humanthrope avatar Jun 25 '17 20:06 humanthrope

Hey there,

This would be some pretty odd behavior. Can you double check that Safari is not set as your default browser? The reason I'm skeptical is because the only way ScreenBloom interacts with your web browser is by calling the Python webbrowser module. You can see it in action in the ScreenBloom code here.

webbrowser.open will call your current system's default browser to open the URL provided. So in essence ScreenBloom doesn't have access to anything BUT your default browser.

kershner avatar Jun 26 '17 14:06 kershner

So it turns out that the problem started happening with the osx 10.12.5. There's a discussion on the python bug tracker about it. I might have to wait for 10.12.6 for a non-hacky fix.

Are there any instructions on how to build the project? I keep running into miscellaneous problems like

ImportError: No module named 'jinja2.asyncfilters'

even though I've installed the modules from requirements.txt. If I remove jinja2 from setup.py:

copying static/images/icon.ico -> build/exe.macosx-10.10-intel-2.7/icon.ico error: [Errno 2] No such file or directory: 'static/images/icon.ico'

And if I remove the icon path:

... copying /System/Library/Frameworks/Tcl.framework/Versions/8.5/Tcl -> build/exe.macosx-10.10-intel-2.7/tcl error: [Errno 1] Operation not permitted: 'build/exe.macosx-10.10-intel-2.7/tcl' $ build/exe.macosx-10.10-intel-2.7/tcl -bash: build/exe.macosx-10.10-intel-2.7/tcl: cannot execute binary file

and then I gave up.

humanthrope avatar Jun 27 '17 01:06 humanthrope

Yep, build instructions at the bottom of the readme: ScreenBloom Developer Quick Start

You shouldn't need to fully build/compile it if you're just trying to figure out where you're experiencing a bug. If you get to that point and still want to build it, let me know and I'll pass you the PyInstaller spec file to get it going.

kershner avatar Jun 27 '17 14:06 kershner