[BUG]: Unassailable Guard

[sakkamade]

Brief description of the issue.

After RSS Guard is killed by killall, it cannot be started again.
(Although no RSS Guard instances may be found by htop.)

How to reproduce the bug?

1.  $ killall rssguard

2.  $ rssguard
    ...
    time="    14.408" type="warning" -> core: Another instance of the application is already running. Notifying it.
    time="    14.408" type="debug" -> core: Destroying Application instance.
    time="    14.408" type="debug" -> core: Destroying Mutex instance.
    time="    14.914" type="debug" -> gui: Destroying IconFactory instance.

What was the expected result?

To start application after it was killed (?)

What actually happened?

It does not seem to start again.

Other information

Here is the log. Clean first start in VB. Built with debug flag.
rss-log.txt

(ran as rssguard > ~/rss-log 2>&1; but there is nothing when running it with --log <file> likewise...)

• OS: Arch Linux, Xfce
• RSS Guard version: be05100

[sakkamade]

Fixed. Thank you.

[martinrotter]

but there is nothing when running it with --log likewise

You mean that --log option does not actually produce log file?

[sakkamade]

No, it does. I meant that there is nothing regaring the time when I killed it.
It is doing exactly the same what > ~/file 2>&1 do, right?

[martinrotter]

Yes, 99% the same. It is there primarily because of windows which likes to FUCK over GUI apps.

It is funny because on Windows, GUI apps cannot by default have their command line outputs redirected in built-in cmd.exe. Powershell behaves bit better but overally the experience is so messy that I had to add the switch.

[martinrotter]

btw the issue was fixed by stale "socket" file "/tmp/rssguard..." which was not removed when "enclosing" C++ object got killed, on every other OS (Windows, osx) relevant "resources" are automatically cleared when app is killed, but given that the socket on linux is actually a file, it was left behind.

[sakkamade]

btw the issue was fixed by stale "socket" file "/tmp/rssguard..." which was not removed

Yes, it is unfortunare to accept, but my only thought of the cause was the /tmp/ directory...
Would have never expected to learn to understand so much about any of it after moving to Linux...

[martinrotter]

In 15 minutes, I learned more about OS maintenance when installing Arch than year staying with Ubuntu.

Seriously, in Ubuntu I felt like the experience is not that good. Partly it was because crazy behavior of "apt-get" package manager which sometimes decided to do some crazy shit when resolving dependecies of a package, sometimes it just decided to delete shitload of packages which totally broke the system, sometimes graphics stopped to work properly etc. It is fair to say that those were Ubuntu 10.04 times, maybe novadays it is better.

Anyway I discovered Arch quite some years back and never looked back. The system felt so amazingly clean after installation and still feels the same today. Package manager is brutal, quality of packaging is somehow breathtaking when compared to Ubuntu. It is rolling-release but I have never ever had single major problem. Maybe once when they transitioned to systemd, I fucked something when migrating, but otherwise, it is fast, clean, smooth, very dev. friendly.

[sakkamade]

In second paragraph you clearly described my experience with Manjaro KDE, from some months ago.

Ubuntu? I remember trying it a year ago in VB for some days, after which I set myself to never move to Linux. Hahaha.

[sakkamade]

(...) after which I set myself to never move to Linux.

No, this is not quite a right way to word it,
"(...) after which I acknowledged that I will never be able to move to Linux" is.
Since from what I heard at the time, it is considered the easiest Linux system to deal with, and the wisest choice for "newbies."