Processing control commands:
> severity -1 important
Bug #890517 [x2goserver] killer's CRON logs out users once per hour
Severity set to 'important' from 'serious'
--
890517: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890517
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Control: severity -1 important
Hi Adrian,
On Di 05 Feb 2019 15:22:06 CET, Adrian Bunk wrote:
control: severity -1 serious
# x2go-server is now in buster
thanks
neither x2goserver nor killer are unusable due to the missing
utmp/wtmp registration. Thus, reducing severity to imporant.
I
control: reassign -1 x2goserver
thanks
On Tue, Feb 05, 2019 at 04:22:06PM +0200, Adrian Bunk wrote:
> control: severity -1 serious
> # x2go-server is now in buster
right, thanks for raising the severity.
> > On Tue, Feb 20, 2018 at 10:30:57AM +0100, Wolfgang Schweer wrote:
> > > > If NX do not
Processing control commands:
> reassign -1 x2goserver
Bug #890517 [killer] killer's CRON logs out users once per hour
Bug reassigned from package 'killer' to 'x2goserver'.
Ignoring request to alter found versions of bug #890517 to the same values
previously set
Ignoring request to alter fixed
Processing control commands:
> severity -1 serious
Bug #890517 [killer] killer's CRON logs out users once per hour
Severity set to 'serious' from 'important'
--
890517: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890517
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Processing control commands:
> severity -1 important
Bug #890517 [killer] killer's CRON logs out users once per hour
Severity set to 'important' from 'serious'
--
890517: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890517
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
control: severity -1 important
# x2go-server is not in Debian, this lowering the severity…
thanks
On Tue, Feb 20, 2018 at 10:30:57AM +0100, Wolfgang Schweer wrote:
> > If NX do not update utmp/wtmp for logged in users, I would claim that
> > NX is broken, and if it is by design, then NX is
Hi Wolfgang,
On Do 22 Feb 2018 20:02:31 CET, Wolfgang Schweer wrote:
On Tue, Feb 20, 2018 at 12:54:26PM +0100, Wolfgang Schweer wrote:
Seems to be X2Go Bug #1171 Create wtmp entry for x2go sessions
See: https://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1171
After testing x2goserver on a
On Tue, Feb 20, 2018 at 12:54:26PM +0100, Wolfgang Schweer wrote:
> Seems to be X2Go Bug #1171 Create wtmp entry for x2go sessions
>
> See: https://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1171
After testing x2goserver on a Stretch system I noticed that X2Go
sessions can be detected reliably due
On Tue, Feb 20, 2018 at 10:30:57AM +0100, Wolfgang Schweer wrote:
> Right. This bug should be reassiged to the x2go-server package
Seems to be X2Go Bug #1171 Create wtmp entry for x2go sessions
See: https://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1171
Wolfgang
signature.asc
Description: PGP
On Tue, Feb 20, 2018 at 06:32:22AM +0100, Petter Reinholdtsen wrote:
> [Wolfgang Schweer]
> > IIRC, for connections to a system that runs Nomachine technology (not
> > part of Debian) the utmp/wtmp files are not used by design (on the
> > system running NX server). Instead, NX keeps track of the
[Wolfgang Schweer]
> IIRC, for connections to a system that runs Nomachine technology (not
> part of Debian) the utmp/wtmp files are not used by design (on the
> system running NX server). Instead, NX keeps track of the forwarded
> sessions itself.
Updating utmp/wtmp is not only for 'keeping
On Thu, Feb 15, 2018 at 03:21:41PM +, Mike Gabriel wrote:
> On Do 15 Feb 2018 15:23:46 CET, Petter Reinholdtsen wrote:
>
> > [Mike Gabriel]
> > > We never came to the point to investigate this closer, but personally,
> > > I think that killer on a Debian Edu system with MATE desktop env has
On Do 15 Feb 2018 15:23:46 CET, Petter Reinholdtsen wrote:
[Mike Gabriel]
We never came to the point to investigate this closer, but personally,
I think that killer on a Debian Edu system with MATE desktop env has
not been usable at least since jessie.
The only way I can think of that this
[Mike Gabriel]
> We never came to the point to investigate this closer, but personally,
> I think that killer on a Debian Edu system with MATE desktop env has
> not been usable at least since jessie.
The only way I can think of that this can happen, is if the display
manager is broken and
Package: killer
Severity: serious
Hi,
since Debian jessie, we disable killer in Debian Edu installations as
killer causes hourly logouts from user sessions.
We never came to the point to investigate this closer, but personally,
I think that killer on a Debian Edu system with MATE desktop
16 matches
Mail list logo
