One thing to weigh when considering signing is that no matter how vague they make wording, they can not have you waive all your rights simply by consenting. If they could, no organisation would be wasting time and money to comply with GDPR; they would all just change their consent forms to be as vague as possible like this to cover their butts. That would obviously defeat the whole purpose behind the new law, and the fact that we don’t see that indicates to me that no organisations (apart from Watchtower, apparently) believe that they could get away with it.
That is not to say that you should just sign the thing without a thought, but just to ease the concern someone might have that if you are forced to sign, you’ll lose any and all privacy rights you have for good.
(Disclaimer: Just my 2 cents, I’m no expert either.)
In addition to Totem, Firefox also exhibits this with fullscreen HTML5 video. Here’s a good test: https://www.youtube.com/watch?v=5xkNy9gfKOg
My bug #1762400 got marked as a duplicate for this one, but I don’t have Dropbox installed.
Possible duplicates with bug #1607919
== Steps to reproduce ==
1. Create a password protected 7z archive: `echo hello >hello.txt; 7z a hello.7z hello.txt -ppassword`
2. Left-click the archive in Nautilus
== What happens ==
Nautilus shows an empty window, and together with gnome-shell they eat up the CPU until you close the Nautilus window. Alternatively, a crash report prompt appears.
== What I expect to happen ==
Preferably to prompt for a password and then open the archive contents. At the very least to not eat all the CPU, and inform the user that Nautilus is incapable of handling this file format.
== Other info ==
I don’t have Dropbox installed unlike in bug #1734891.
Upstream issue: https://gitlab.gnome.org/GNOME/nautilus/issues/51
Red Hat issue: https://bugzilla.redhat.com/show_bug.cgi?id=1499401
Lumen alla vaarallisen sileää jäätä, edes nastakengillä ei meinannut pysyä pystyssä.
The shortcode examples on the FAQ page seem to be rendered (”It’s only fair to share…” + sharing icons) by the plugin instead of being shown as code. You should probably escape the shortcodes in those examples.
Haven’t seen this since upgrading to 18.04, and can’t reproduce it following the instructions anymore either, so it appears to be fixed.