OpenSUSE has this "feature" that I absolutely hate that when you restart, it
automatically starts whatever applications you had running when you restarted.
I'm sure I can disable it somewhere but that's not the point: as long as this
feature exists, it has to work decently. Actually, it has to work perfectly,
but decently would be a start.

So, here's what happened.

I had one (ONE) instance of FileZilla open and I restarted the system.

After restart, FileZilla didn't seem to be running. There was no FileZilla
window anywhere, and is pinned icon in the task manager was not highlighted.
This was not a problem, because as I said, I don't even like applications that
I left open to be automatically started after reboot, so the less there are the
better, and I didn't even notice. I didn't remember that I had left it open.

SPOILER: in reality it _was_ running but as I said, I had no way of knowing.

So, I rebooted several times because I was trying installing and uninstalling
stuff repeatedly, so I rebooted half a dozen times.
Never did I ever notice that filezilla was running.


Now, it doesn't matter what made me think of it, but I ran this in a terminal:

   $ ps aux | grep filezilla

and it turned out there were half a dozen processes of it running. One for
every time that I had rebooted.

So I hit Alt+Tab and found out that there were a bunch of FileZilla windows,
but it was not the main window, but rather a popup with an error message that
said that there were some issues with utf8 characters in filenames or whatnot.

So there are several things that went wrong here:

1. The feature that, at startup, automatically launches the applications that
were left open prior to reboot, is completely broken. Most of these
applications have issues when run this way. FileZilla always shows this error
related to utf-8 or unicode or whatever when launched automatically at startup
(it does not show the error when launched manually normally). Thunderbird is
forever unable to connect to the network when it is launched this way. While
probably each of those applications have their own bugs, you are clearly
launching them "too soon" or in some wrong way. So, this is one issue, leading
to FileZilla showing (or wanting to show) that error popup

2. The popup with the error message didn't actually popup. It was somehow
buried behind other windows, or completely invisible. Only when I used Alt+Tab
was I ever able to discover its existence. That's wrong on its own

3. FileZilla's icon in the task manager should have been highlighted, so that I
should have been able to see that there was, in fact, a filezilla window open
(the error message popup), and I should have been able to access it by clicking
on the task-manager icon (which instead would open a brand new FileZilla
window). But no, the popup apparently doesn't count as window for the task
manager. Only after I close the error popup, does the icon in the task manager
become highlighted.

4. When I rebooted again, with the filezilla process running, with the
invisible error-message popup waiting to be discovered and closed, after
reboot, somehow TWO FileZilla processes were launched; and at the next reboot
they were 3, and so on. Actually, I can't be sure of that. All I know for sure
is that after like 6 or 7 reboots I had like 6 or 7 filezilla processes
running, all of them with the error popup waiting to be closed (which I found
and closed one by one with Alt+Tab).

The whole thing is ridiculous.