== Steps to reproduce ==
`wget -q https://www.google.com/ &`

== What happens ==
wget says it’s ”Redirecting output to ’wget-log'” and creates an empty wget-log file in the current directory.

== What I expect to happen ==
No wget-log file to be created.

== Details ==
Wget has a -b (–background) option, for which the man page says: ”If no output file is specified via the -o, output is redirected to wget-log.” There’s also the -q (–quiet) option, for which the man page says: ”Turn off Wget’s output.”

When both are given, wget goes to background, and no wget-log gets created, as expected.

When only -b is given, wget goes to background, and creates wget-log, also as expected.

When only -q is given, wget runs in the foreground, and no wget-log is created, still as expected.

When only -q is given, but & is added to the end of the command line, wget goes to background, but also creates wget-log, which I find unexpected (and inconsistent).

Kuuntelin tunnarin Youtubesta, enkä tunnistanut. Debunked!

(Videon kommenteissa oli vähän keskustelua Hubbardin lainauksista.)

Henry Lee Lucas of course had Ottis Toole as his accomplice, and the picture of super-prolific sexual predators that the two painted of themselves with their confessions sort of matches how the perpetrator(s) of this case come across. But I’d imagine (or at least hope) that officials would have tested Lucas’ DNA as well, unless they had already ruled him out via other means.

I’ve had this happen a couple of times now since upgrading to 18.04: soon (perhaps within a minute) after logging in, Gnome session ends abruptly and I’m thrown back to the login screen. IIRC, in both instances this occurred on the first login after boot, so it does not reoccur on the subsequent re-login, and not on every login (very rarely in fact), and for now I have no better steps to reproduce this other than ”boot, log in”.

Bug #1663839 (reported against 17.04) seems similar, as does bug #1731428 (reported against 17.10).

journalctl output during the issue:

Apr 16 07:00:30 saegusa gnome-session[4342]: gnome-session-binary[4342]: WARNING: Application ’org.gnome.SettingsDaemon.Color.desktop’ failed to register before timeout
Apr 16 07:00:30 saegusa gnome-session-binary[4342]: WARNING: Application ’org.gnome.SettingsDaemon.Color.desktop’ failed to register before timeout
Apr 16 07:00:30 saegusa gnome-session-binary[4342]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop
Apr 16 07:00:30 saegusa gnome-session[4342]: gnome-session-binary[4342]: CRITICAL: We failed, but the fail whale is dead. Sorry….
Apr 16 07:00:30 saegusa gnome-session-binary[4342]: CRITICAL: We failed, but the fail whale is dead. Sorry….

Olisin väittänyt Mighty Ducks -ilmiön kytkeytyneen Teemu Selänteen NHL-uraan, koska omassa mielessäni joukkueen nimi kytkeytyi 90-luvun Selänne-faneihin. Wikipedian mukaan Selänne kuitenkin myytiin Anaheimiin vasta 1996, joten 1993 on ihan liian aikaista aikaa selittääkseen tuota ilmiötä.

Ja minäkin pidin joukkuetta alunalkujaan pelkkänä parodiana, tai Disneyn fiktiona.

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