Hi again, I have been told that we don't close upstream bugs. In fact, you clearly tagged it accordingly. Therefore, I guess you should forget my comment. I will reopen this bug and flag it as forwarded to the upstream issue I mentioned before. We'll wait for reoslution from upstream.
Regards, On Sun, Jan 05, 2020 at 04:17:58PM -0500, Simon Désaulniers wrote: > Hi, > > > Unlike the man page suggests, i3lock-fancy does not fork, no matter if the > > -n argument was supplied or not. > > This issue is not related to any manipulation on the packager's end. This is > an > upstream issue. In fact, a bug report has been filed [1] in upstream's bug > tracking system exactly 6 months before your bug report here. There is > nothing I > can do really. You can try to make some noise in upstream's BTS. > > Keep in mind that the Debian package is also based on dualmonitor branch of > upstream's project. If there was a fix over there, it would have to be ported > to > the dualmonitor branch also for us to use this fix. > > Since there's nothing to do really here, I will close this bug report. > > Regards, > > [1]: https://github.com/meskarune/i3lock-fancy/issues/144 > > Le sam. 10 août 2019, à 21 h 51, dirdi <deb...@dirdi.name> a écrit : > > > Package: i3lock-fancy > > Version: 0.0~git20160228.0.0fcb933-2 > > Severity: normal > > Tags: upstream > > > > Unlike the man page suggests, i3lock-fancy does not fork, no matter if the > > -n argument was supplied or not. > > > > -- System Information: > > Debian Release: bullseye/sid > > APT prefers testing > > APT policy: (500, 'testing'), (50, 'unstable') > > Architecture: amd64 (x86_64) > > > > Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores) > > Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE > > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), > > LANGUAGE=en_US:en (charmap=UTF-8) > > Shell: /bin/sh linked to /usr/bin/dash > > Init: systemd (via /run/systemd/system) > > LSM: AppArmor: enabled > > > > Versions of packages i3lock-fancy depends on: > > ii gawk 1:4.2.1+dfsg-1.1 > > ii i3lock 2.11.1-1 > > ii imagemagick 8:6.9.10.23+dfsg-2.1 > > ii imagemagick-6.q16 [imagemagick] 8:6.9.10.23+dfsg-2.1 > > ii mawk 1.3.3-17+b3 > > ii scrot 1.1.1-1 > > > > i3lock-fancy recommends no packages. > > > > Versions of packages i3lock-fancy suggests: > > pn maim <none> > > pn wmctrl <none> > > > > -- no debconf information > > > s > Le sam. 10 août 2019, à 21 h 51, dirdi <[1]deb...@dirdi.name> a écrit : > > Package: i3lock-fancy > Version: 0.0~git20160228.0.0fcb933-2 > Severity: normal > Tags: upstream > > Unlike the man page suggests, i3lock-fancy does not fork, no matter if > the -n argument was supplied or not. > > -- System Information: > Debian Release: bullseye/sid > APT prefers testing > APT policy: (500, 'testing'), (50, 'unstable') > Architecture: amd64 (x86_64) > > Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores) > Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), > LANGUAGE=en_US:en (charmap=UTF-8) > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages i3lock-fancy depends on: > ii gawk 1:4.2.1+dfsg-1.1 > ii i3lock 2.11.1-1 > ii imagemagick 8:6.9.10.23+dfsg-2.1 > ii imagemagick-6.q16 [imagemagick] 8:6.9.10.23+dfsg-2.1 > ii mawk 1.3.3-17+b3 > ii scrot 1.1.1-1 > > i3lock-fancy recommends no packages. > > Versions of packages i3lock-fancy suggests: > pn maim <none> > pn wmctrl <none> > > -- no debconf information > > References > > Visible links > 1. mailto:deb...@dirdi.name -- Simon Désaulniers sim.desaulni...@gmail.com
signature.asc
Description: PGP signature
