Activity for Fincer
-
Fincer posted a comment on ticket #341
Qt4 version works (Arch Linux AUR repository) so either Qt5 integration or something else is broken
-
Whitelisting is broken with pglgui (connection type missing etc.)
-
Looks pretty much the same old issue that I have analyzed here: PGL not working on Arh/AntergOS Especially this part: PROBLEM 2 HERE: User can bug the "automatic updates" feature in GUI, leading to two existing pglcmd files, for example one in /etc/cron.daily/ folder and another one in /etc/cron.weekly/ folder. Better code logic to handle such situations is needed here.
-
I guess this is the same issue I have talked about here: PGL not working on Arh/AntergOS
-
I guess this is the same issue I have talked about here: PGL not working on Arh/AntergOS
-
Looks pretty much the same old issue that I have analyzed here: PGL not working on Arh/AntergOS Especially this part: PROBLEM 2 HERE: User can bug the "automatic updates" feature in GUI, leading to two existing pglcmd files, for example one in /etc/cron.daily/ folder and another one in /etc/cron.weekly/ folder. Better code logic to handle such situations is needed here.
-
Yes, it is more an upstream issue of PeerGuardian's cron/automatic update implementation. Visible to user as strange error messages appearing whenever "Applying changes" by executing /tmp/execute-all-pgl-commands.sh If cron is not installed on the system, commands which are generated by PeerGuardian are 1 2 3 4 5#!/bin/sh set -e mv /tmp/pglcmd.conf /etc/pgl/pglcmd.conf mv <arg1> <arg2> /usr/bin/pglcmd reload Where <arg1> <arg2> are cron arguments (for example, mv /etc/cron.daily/pglcmd /etc/cron.weekly/pglcmd)....
-
Yes, it is more an upstream issue of PeerGuardian's cron/automatic update implementation. Visible to user as strange error messages appearing whenever "Applying changes" by executing /tmp/execute-all-pgl-commands.sh If cron is not installed on the system, commands which are generated by PeerGuardian are 1 2 3 4 5#!/bin/sh set -e mv /tmp/pglcmd.conf /etc/pgl/pglcmd.conf mv <arg1> <arg2> /usr/bin/pglcmd reload Where <arg1> <arg2> are cron arguments (for example, mv /etc/cron.daily/pglcmd /etc/cron.weekly/pglcmd)....
-
Yes, it is more an upstream issue of PeerGuardian's cron/automatic update implementation. Visible to user as strange error messages appearing whenever "Applying changes" by executing /tmp/execute-all-pgl-commands.sh If cron is not installed on the system, commands which are generated by PeerGuardian are 1 2 3 4 5#!/bin/sh set -e mv /tmp/pglcmd.conf /etc/pgl/pglcmd.conf mv <arg1> <arg2> /usr/bin/pglcmd reload Where <arg1> <arg2> are cron arguments (for example, mv /etc/cron.daily/pglcmd /etc/cron.weekly/pglcmd)....
-
Yes, it is more an upstream issue of PeerGuardian's cron/automatic update implementation. Visible to user as strange error messages appearing whenever "Applying changes" by executing /tmp/execute-all-pgl-commands.sh If cron is not installed on the system, commands which are generated by PeerGuardian are 1 2 3 4 5#!/bin/sh set -e mv /tmp/pglcmd.conf /etc/pgl/pglcmd.conf mv <arg1> <arg2> /usr/bin/pglcmd reload Where <arg1> <arg2> are cron arguments (for example, mv /etc/cron.daily/pglcmd /etc/cron.weekly/pglcmd)....
-
Yes, it is more an upstream issue of PeerGuardian's cron/automatic update implementation. Visible to user as strange error messages appearing whenever "Applying changes" by executing /tmp/execute-all-pgl-commands.sh If cron is not installed on the system, commands which are generated by PeerGuardian are 1 2 3 4 5#!/bin/sh set -e mv /tmp/pglcmd.conf /etc/pgl/pglcmd.conf mv <arg1> <arg2> /usr/bin/pglcmd reload Where <arg1> <arg2> are cron arguments (for example, mv /etc/cron.daily/pglcmd /etc/cron.weekly/pglcmd)....
-
Yes, it is more an upstream issue of PeerGuardian's cron/automatic update implementation. Visible to user as strange error messages appearing whenever "Applying changes" by executing /tmp/execute-all-pgl-commands.sh If cron is not installed on the system, commands which are generated by PeerGuardian are 1 2 3 4 5#!/bin/sh set -e mv /tmp/pglcmd.conf /etc/pgl/pglcmd.conf mv <arg1> <arg2> /usr/bin/pglcmd reload Where <arg1> <arg2> are cron arguments (for example, mv /etc/cron.daily/pglcmd /etc/cron.weekly/pglcmd)....
-
Yes, it is more an upstream issue of PeerGuardian's cron/automatic update implementation. Visible to user as strange error messages appearing whenever "Applying changes" by executing /tmp/execute-all-pgl-commands.sh If cron is not installed on the system, commands which are generated by PeerGuardian are 1 2 3 4 5#!/bin/sh set -e mv /tmp/pglcmd.conf /etc/pgl/pglcmd.conf mv <arg1> <arg2> /usr/bin/pglcmd reload Where <arg1> <arg2> are cron arguments (for example, mv /etc/cron.daily/pglcmd /etc/cron.weekly/pglcmd)....
-
I studied PeerGuardian source code for a little while. As a conclusion, I think the parts of Cron implementation is a mess. Several issues here: By default, PeerGuardian installs (or wants to install) /etc/cron.daily/pglcmd file. NOTE: This is not same file than /usr/bin/pglcmd It looks like that in /src/pglgui.cpp it is always expected that /etc/cron.{daily,weekly,monthly}/pglcmd file exists. Especially lines 622-624 + functions getUpdateFrequencyPath() and getUpdateFrequencyCurrentPath(). Equivalent...
-
I studied PeerGuardian source code for a little while. As a conclusion, I think the parts of Cron implementation is a mess. Several issues here: By default, PeerGuardian installs (or wants to install) /etc/cron.daily/pglcmd file. NOTE: This is not same file than /usr/bin/pglcmd It looks like that in /src/pglgui.cpp it is always expected that /etc/cron.{daily,weekly,monthly}/pglcmd file exists. Especially lines 622-624 + functions getUpdateFrequencyPath() and getUpdateFrequencyCurrentPath(). If no...
-
Change UI title 'Peerguadian Linux' -> 'PeerGuardian Linux'
-
Remove 'Times New Roman' used in Qt5 GUI
-
Sorry for late answer. Encountered exactly same error. Solved by installing 'cron' package. Please see my detailed answer here: https://aur.archlinux.org/packages/pgl-git/#comment-625632
1