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

Can't access settings #23

Open
mackaaij opened this issue Aug 22, 2016 · 12 comments
Open

Can't access settings #23

mackaaij opened this issue Aug 22, 2016 · 12 comments

Comments

@mackaaij
Copy link

If I try to access settings, QBlocker quits and shows this error reporting screen:

schermafbeelding 2016-08-22 om 12 48 00

@hehachris
Copy link

same here

@steve228uk
Copy link
Owner

Can you check in System Preferences > Users > Login items for any items with a ⚠️

@mackaaij
Copy link
Author

QBlocker was listed as hidden, unknown type and without an icon. I removed QBlocker from there, that fixed this issue.

@3raxton
Copy link

3raxton commented Oct 2, 2016

It is not there for me and I continue to get the problem. Any further help? @steve228uk

@abulwcse
Copy link

It is not there for me as well and still I would not access settings menu.. Any further help? @steve228uk

@steve228uk
Copy link
Owner

@abulwcse Are you able to submit a log file from Console.app when it crashes?

@abulwcse
Copy link

abulwcse commented Nov 16, 2016

QBlocker[52932]: Handling crash with signal 4... is what I see in system.log
Also found this
QBlocker not switching as we're not in ~/Library/Keychains/: /Library/Keychains/System.keychain (0)

@steve228uk

@steve228uk
Copy link
Owner

Thanks @abulwcse, I'll have a look. We shouldn't be hitting the keychain at all so something is awry here.

@3raxton
Copy link

3raxton commented Nov 16, 2016

Yes, I am

On Nov 16, 2016, at 03:43, Abul Hassan Anwar Hussain [email protected] wrote:

QBlocker[52932]: Handling crash with signal 4... is what I see in system.log @steve228uk


You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

@3raxton
Copy link

3raxton commented Nov 16, 2016

Brilliant, thanks so much!

On Nov 16, 2016, at 04:20, Stephen Radford [email protected] wrote:

Thanks @abulwcse, I'll have a look. We shouldn't be hitting the keychain at all so something is awry here.


You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

@3raxton
Copy link

3raxton commented Mar 27, 2017

It's been a bit but I am still curious as to how this process is coming along. Please let me know! @steve228uk

@fharper
Copy link

fharper commented Jun 29, 2019

I also have this issue!

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

6 participants