Comments

233 Comments

This update has been unpushed.

karma

Freezes after login screen on Dell XPS 15 L502X (SandyBridge) with i5-2520M CPU, Intel 2nd gen GPU and nVidia GeForce GT 525M. There seems to be a regression in nouveau driver: https://bugs.freedesktop.org/show_bug.cgi?id=105174 .

karma

Seems to work fine here as well, thanks.

FYI, I got:

...
  Upgrading        : certbot-0.21.1-1.fc26.noarch                                        4/9
  Running scriptlet: certbot-0.21.1-1.fc26.noarch                                        4/9
ValueError: File context for /etc/(letsencrypt|certbot)/(live|archive)(/.*)? already defined
...

when updating from 0.20.0-1.fc26.

karma

Fixes the 100% CPU usage bug with LibreOffice. I haven't seen the timedatex issue either with this version or with any earlier one.

karma

Actually I'm seeing the same issues after suspend/resume. Sorry for not noticing this earlier. Going back to 5.47-2.fc27 does help.

Works for me and fixes bug #1514969 on one of my machines.

karma

Works for me.

karma

Works for me.

No regressions noted.

No regressions noted.

karma

Works for me on Intel Haswell platform (device 8087:07dc).

karma

Works for me for auto-mounting NFS shares on LAN.

@sagitter Please remove all installed uBlock Origin versions, including the one in your home dir and try again.

@sagitter Obviously it works for me, did you quit firefox before installing and restart it twice afterwards?

Thanks for doing the update, but this fails a number of tests, including the most important ABI check. Have you verified that all dependent packages still work with this update and don't need rebuilding?

@robatino I'm not doing anything different than mozilla-https-everywhere package, so either the WebExtension version is somehow compatible with FF56 or you have a local copy of the add-on in your home directory.

@robatino, no, the XUL version is installed in SeaMonkey-specific folder. Firefox will "see" only the WebExtension version, so this works only with FF57+.

karma

Works for me and fixes #1483272 for me.

That's not a bug in NoScript, that's a bug in Firefox and no reason to block this update. It looks like a case of bug #1508827 which I reported some time ago.