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

Doesn't work with Pushbullet in Canary 49.0.2623.0 #1252

Closed
riesza opened this issue Jan 18, 2016 · 18 comments
Closed

Doesn't work with Pushbullet in Canary 49.0.2623.0 #1252

riesza opened this issue Jan 18, 2016 · 18 comments

Comments

@riesza
Copy link

riesza commented Jan 18, 2016

This has been happening for a few days now and it took me a while to narrow it down but it seems that sites don't load at all if Pushbullet and uBO are active at the same time. I get a "waiting for extension uBlock Origin..." in the bottom left whenever I try to open a page and trying to access the options through the extension menu (the button in the top right corner doesn't work at all) leads to this: lmhrox 1

I set up Chromium after this and it works fine with both enabled. It didn't occur to me that PB might be the problem so I thought it was just uBO. Anyway I'm not sure how to troubleshoot the cause any further.

@riesza
Copy link
Author

riesza commented Jan 18, 2016

Or maybe it's not related to PB at all, it just stopped working again even with it disabled. This could just be a Canary problem for all I know but I really don't know how to troubleshoot this.

@gorhill
Copy link
Owner

gorhill commented Jan 18, 2016

I do not understand the report. Make a very detail step-by-step of what is wrong. See CONTRIBUTING -- marking as invalid until a better detailed issue is provided. Also, always check "Collect errors" if you do not know how to access an extension's dev console and report errors in it.

@gorhill
Copy link
Owner

gorhill commented Jan 18, 2016

I tested uBO 1.5.6 with Google Chrome 49.0.2618.8 dev (64-bit) and all is fine. You will have to make the case there is an issue with uBO itself. Use the browser dev tools to investigate. I will reopen if you make the case there is an issue with uBO.

@gorhill gorhill closed this as completed Jan 18, 2016
@riesza
Copy link
Author

riesza commented Jan 18, 2016

Sorry about that. How do I access the error collection logs?

This whole thing seems incredibly inconsistent but right now it seems to be centered around Pushbullet, RedditEnhancementSuite, Fauxbar Lite + Fauxbar Memory Helper and Tampermonkey. Other than those I have everything else turned off right now. Turning them on and off in different combinations causes it to happen sometimes but not consistently.
Resetting uBO 1.5.6 completely didn't help. Regardless of what other extension seems to cause this incompatibility, turning off uBO will always fix it.

Here's an example (default settings uBO 1.5.6):

  1. uBO on, everything off it works fine.
  2. Restart, turn on Tampermonkey, everything fine.
  3. Turn on RES, restart, everything fine.
  4. Turn on PB, restart, it's broken
  5. Turn off PB, restart, still broken.
  6. Restart without turning off anything else, it works.
  7. Turn on PB, restart, it works.
  8. Turn on Fauxbar and the memory helper, restart, it's broken.
  9. Turn off Fauxbar again, everything works.
  10. Turn it on again, restart, it's broken.
  11. Turn it off again, restart, still broken
  12. Disable uBO without restarting and the site loads immediately

Overall I have no clue what to make of it because it's so random but what it has in common is that it always works as soon as I disable uBO.

@gorhill
Copy link
Owner

gorhill commented Jan 18, 2016

How do I access the error collection logs?

In the screenshot you posted above, there is a "Collect errors" checkbox. Check it. Then if errors are reported when the issue occur, report these errors here.

@riesza
Copy link
Author

riesza commented Jan 18, 2016

Oh, I had it checked all the while I did that test run and nothing popped up.

@gorhill
Copy link
Owner

gorhill commented Jan 18, 2016

Try the same with other extensions, probably Pushbullet first.

@riesza
Copy link
Author

riesza commented Jan 18, 2016

Tampemonkey showed this http://pastebin.com/qnHkqYi0
Pushbullet showed http://pastebin.com/9EVVfemx

Not sure if I copied those correctly or if they're of any help to you.

After collecting those I restarted and it worked again. Then I turned off both Fauxbars, restarted and it broke. Restarting again did nothing but turning off uBO afterwards fixed it immediately.

@riesza
Copy link
Author

riesza commented Jan 18, 2016

Just did the following thing three times: I turned on all the extensions and restarted the browser 5-6 times until it worked. Then on the next restart or the one after it stops working again.

@gorhill
Copy link
Owner

gorhill commented Jan 18, 2016

Tampemonkey showed ...

There is nothing I can do with this, the type of error and the line at which the error occurred is the most important information, you did not provide it.

@riesza
Copy link
Author

riesza commented Jan 18, 2016

This any better?

@gorhill
Copy link
Owner

gorhill commented Jan 18, 2016

Not really. A screenshot of the reported errors would be much better. Example:

a

Notice that I also expanded the Stack Trace item.

@riesza
Copy link
Author

riesza commented Jan 18, 2016

https://my.mixtape.moe/zizqzk.png
https://my.mixtape.moe/fcnlsx.png
https://my.mixtape.moe/shdmss.png
https://my.mixtape.moe/auzjbu.png
https://my.mixtape.moe/wabkkc.png

Can't seem to make the popup bigger but the errors are in full in the last pastebin in the same order.

@gorhill
Copy link
Owner

gorhill commented Jan 18, 2016

These are all Tampermonkey errors. So disable Tampermonkey and see if the issue persist -- as said, I deal only with uBO's own issues, not that of other extensions.

@riesza
Copy link
Author

riesza commented Jan 18, 2016

I just got it to break with just uBO and uMatrix on and recorded it. Shortly after that it also broke the same way with just uBO on at browser start.

Here it is with just uBO after turning off uMatrix.

@gorhill
Copy link
Owner

gorhill commented Jan 18, 2016

Ok. All this started with 49.0.2623.0?

@riesza
Copy link
Author

riesza commented Jan 18, 2016

Yup.

@gorhill gorhill reopened this Jan 18, 2016
@gorhill
Copy link
Owner

gorhill commented Jan 18, 2016

Ok new rule, I just do not have the time to address issues in dev builds of Chrome/Firefox. So if an issue only occurs in these builds, and not on stable or beta, an issue should not be opened. I updated CONTRIBUTING. If you can't reproduce the issue here on Chrome stable or beta, please close the issue.

@riesza riesza closed this as completed Jan 18, 2016
gorhill pushed a commit that referenced this issue Sep 26, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants