Control: forwarded -1 https://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1171
[Wolfgang Schweer]
> Any news on this one? Debian Edu Bullseye intends to use x2goserver on
> LTSP servers for Thin Client support...
The upstream issue is still open, at least.
(Just a quick reply to set the forwared
Moin Mike,
On Wed, 06 Feb 2019 11:25:54 + Mike Gabriel
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 will look
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
control: severity -1 serious
# x2go-server is now in buster
thanks
On Sun, Feb 25, 2018 at 02:09:00PM +, Holger Levsen wrote:
> 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
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
Hi Wolfgang,
On Di 20 Nov 2018 22:08:44 CET, Wolfgang Schweer wrote:
On Tue, Nov 20, 2018 at 02:33:53PM +, Mike Gabriel wrote:
I am not sure, if the patch is not a functional overkill.
Hi Mike,
I don't think that this is the case:
My observation was, that the x2goagent processes got
On Tue, Nov 20, 2018 at 02:33:53PM +, Mike Gabriel wrote:
> I am not sure, if the patch is not a functional overkill.
Hi Mike,
I don't think that this is the case:
> My observation was, that the x2goagent processes got killed by killer.
Yes, but if the user's x2goagent process gets killed,
On Mon, Nov 19, 2018 at 12:00:20AM +0100, Petter Reinholdtsen wrote:
> I had a look at the patch, and it is not obviously wrong, at least. I do
> not know the code well any more, but did test and read it, and it might
> work. I do not have x2go myself, so I can not test that part, though.
Hi Wolfgang,
On Di 20 Nov 2018 15:27:25 CET, Wolfgang Schweer wrote:
On Mon, Nov 19, 2018 at 12:00:20AM +0100, Petter Reinholdtsen wrote:
I had a look at the patch, and it is not obviously wrong, at least. I do
not know the code well any more, but did test and read it, and it might
work. I
[Wolfgang Schweer]
> Mike, could you test this change to killer (might be smarter, some one
> w/ Perl skills should check it:
I had a look at the patch, and it is not obviously wrong, at least. I do
not know the code well any more, but did test and read it, and it might
work. I do not have
On Sun, Feb 25, 2018 at 03:14:03PM +0100, Petter Reinholdtsen wrote:
> [Mike Gabriel]
> > This is at most a dirty work around. The killer command wipes
> > x2goagent hourly and this must be prevented in killer itself somehow.
> >
> > With the above patch you disable killer system-wide once at
[Mike Gabriel]
> This is at most a dirty work around. The killer command wipes
> x2goagent hourly and this must be prevented in killer itself somehow.
>
> With the above patch you disable killer system-wide once at least one
> X2Go Session is running on the host. Not the right approach.
It do
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
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
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
24 matches
Mail list logo
