Processing commands for control(a)bugs.x2go.org:
> notfixed 870 4.1.0.1
Bug #870 [x2goclient] x2goclient: undefined symbol: ssh_forward_listen
There is no source info for the package 'x2goclient' at version '4.1.0.1' with architecture ''
Unable to make a source version for version '4.1.0.1'
No longer marked as fixed in versions 4.1.0.1.
> fixed 870 4.1.1.0
Bug #870 [x2goclient] x2goclient: undefined symbol: ssh_forward_listen
There is no source info for the package 'x2goclient' at version '4.1.1.0' with architecture ''
Unable to make a source version for version '4.1.1.0'
Marked as fixed in versions 4.1.1.0.
> notfixed 1121 4.1.0.1
Bug #1121 [x2goclient] x2goclient Doesn't Use libssh Config File
Bug #212 [x2goclient] x2go doesn't honour ssh (client) configuration
There is no source info for the package 'x2goclient' at version '4.1.0.1' with architecture ''
Unable to make a source version for version '4.1.0.1'
No longer marked as fixed in versions 4.1.0.1.
No longer marked as fixed in versions 4.1.0.1.
> fixed 1121 4.1.1.0
Bug #1121 [x2goclient] x2goclient Doesn't Use libssh Config File
Bug #212 [x2goclient] x2go doesn't honour ssh (client) configuration
There is no source info for the package 'x2goclient' at version '4.1.1.0' with architecture ''
Unable to make a source version for version '4.1.1.0'
Marked as fixed in versions 4.1.1.0.
Marked as fixed in versions 4.1.1.0.
> notfixed 1093 4.1.0.1
Bug #1093 [x2goclient] x2goclient on OS X not finding MacPorts xmodmap executable in /opt/local/bin then crashes
There is no source info for the package 'x2goclient' at version '4.1.0.1' with architecture ''
Unable to make a source version for version '4.1.0.1'
No longer marked as fixed in versions 4.1.0.1.
> fixed 1093 4.1.1.0
Bug #1093 [x2goclient] x2goclient on OS X not finding MacPorts xmodmap executable in /opt/local/bin then crashes
There is no source info for the package 'x2goclient' at version '4.1.1.0' with architecture ''
Unable to make a source version for version '4.1.1.0'
Marked as fixed in versions 4.1.1.0.
> notfixed 31 4.1.0.1
Bug #31 [x2goclient] X2Go Clients Gr-Tunnel (client-side endpoint) listens on all TCP/IP address (probably should be: loopback only)
There is no source info for the package 'x2goclient' at version '4.1.0.1' with architecture ''
Unable to make a source version for version '4.1.0.1'
No longer marked as fixed in versions 4.1.0.1.
> fixed 31 4.1.1.0
Bug #31 [x2goclient] X2Go Clients Gr-Tunnel (client-side endpoint) listens on all TCP/IP address (probably should be: loopback only)
There is no source info for the package 'x2goclient' at version '4.1.1.0' with architecture ''
Unable to make a source version for version '4.1.1.0'
Marked as fixed in versions 4.1.1.0.
> notfixed 499 4.1.0.1
Bug #499 [x2goclient] Fwd: [Bug 1097757] New: [abrt] x2goclient: QString(): x2goclient killed by SIGSEGV
There is no source info for the package 'x2goclient' at version '4.1.0.1' with architecture ''
Unable to make a source version for version '4.1.0.1'
No longer marked as fixed in versions 4.1.0.1.
> fixed 499 4.1.1.0
Bug #499 [x2goclient] Fwd: [Bug 1097757] New: [abrt] x2goclient: QString(): x2goclient killed by SIGSEGV
There is no source info for the package 'x2goclient' at version '4.1.1.0' with architecture ''
Unable to make a source version for version '4.1.1.0'
Marked as fixed in versions 4.1.1.0.
> notfixed 1119 4.1.0.1
Bug #1119 [x2goclient] Fwd: [Bug 1399281] [abrt] x2goclient: privatekey_from_file(): x2goclient killed by SIGSEGV
Bug #1112 [x2goclient] segfault on missing ssh-key
There is no source info for the package 'x2goclient' at version '4.1.0.1' with architecture ''
Unable to make a source version for version '4.1.0.1'
No longer marked as fixed in versions 4.1.0.1.
No longer marked as fixed in versions 4.1.0.1.
> fixed 1119 4.1.1.0
Bug #1119 [x2goclient] Fwd: [Bug 1399281] [abrt] x2goclient: privatekey_from_file(): x2goclient killed by SIGSEGV
Bug #1112 [x2goclient] segfault on missing ssh-key
There is no source info for the package 'x2goclient' at version '4.1.1.0' with architecture ''
Unable to make a source version for version '4.1.1.0'
Marked as fixed in versions 4.1.1.0.
Marked as fixed in versions 4.1.1.0.
> notfixed 930 4.1.0.1
Bug #930 [x2goclient] x2goclient package for Mac OS X -- use disk image icon instead of X2Go icon for mounted disk image
There is no source info for the package 'x2goclient' at version '4.1.0.1' with architecture ''
Unable to make a source version for version '4.1.0.1'
No longer marked as fixed in versions 4.1.0.1.
> fixed 930 4.1.1.0
Bug #930 [x2goclient] x2goclient package for Mac OS X -- use disk image icon instead of X2Go icon for mounted disk image
There is no source info for the package 'x2goclient' at version '4.1.1.0' with architecture ''
Unable to make a source version for version '4.1.1.0'
Marked as fixed in versions 4.1.1.0.
> notfixed 966 4.1.0.1
Bug #966 [x2goclient] x2goclient SSH fails with keyboard-interactive + banner
There is no source info for the package 'x2goclient' at version '4.1.0.1' with architecture ''
Unable to make a source version for version '4.1.0.1'
No longer marked as fixed in versions 4.1.0.1.
> fixed 966 4.1.1.0
Bug #966 [x2goclient] x2goclient SSH fails with keyboard-interactive + banner
There is no source info for the package 'x2goclient' at version '4.1.1.0' with architecture ''
Unable to make a source version for version '4.1.1.0'
Marked as fixed in versions 4.1.1.0.
> notfixed 592 4.1.0.1
Bug #592 [x2goclient] Expired password
There is no source info for the package 'x2goclient' at version '4.1.0.1' with architecture ''
Unable to make a source version for version '4.1.0.1'
No longer marked as fixed in versions 4.1.0.1.
> fixed 592 4.1.1.0
Bug #592 [x2goclient] Expired password
There is no source info for the package 'x2goclient' at version '4.1.1.0' with architecture ''
Unable to make a source version for version '4.1.1.0'
Marked as fixed in versions 4.1.1.0.
> notfixed 31 4.1.0.1
Bug #31 [x2goclient] X2Go Clients Gr-Tunnel (client-side endpoint) listens on all TCP/IP address (probably should be: loopback only)
There is no source info for the package 'x2goclient' at version '4.1.0.1' with architecture ''
Unable to make a source version for version '4.1.0.1'
Ignoring request to alter fixed versions of bug #31 to the same values previously set
> fixed 31 4.1.1.0
Bug #31 [x2goclient] X2Go Clients Gr-Tunnel (client-side endpoint) listens on all TCP/IP address (probably should be: loopback only)
There is no source info for the package 'x2goclient' at version '4.1.1.0' with architecture ''
Unable to make a source version for version '4.1.1.0'
Ignoring request to alter fixed versions of bug #31 to the same values previously set
> unarchive 1152
Bug #1152 {Done: Mike DePaulo <mikedep333(a)gmail.com>} [x2goclient] X2GoClient on Windows has issues with Audio when playing HTML5 Videos
Unarchived Bug 1152
> reopen 1152
Bug #1152 {Done: Mike DePaulo <mikedep333(a)gmail.com>} [x2goclient] X2GoClient on Windows has issues with Audio when playing HTML5 Videos
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 4.1.0.1.
> notfixed 1152 4.1.0.1
Bug #1152 [x2goclient] X2GoClient on Windows has issues with Audio when playing HTML5 Videos
There is no source info for the package 'x2goclient' at version '4.1.0.1' with architecture ''
Unable to make a source version for version '4.1.0.1'
Ignoring request to alter fixed versions of bug #1152 to the same values previously set
> fixed 1152 4.1.1.0
Bug #1152 [x2goclient] X2GoClient on Windows has issues with Audio when playing HTML5 Videos
There is no source info for the package 'x2goclient' at version '4.1.1.0' with architecture ''
Unable to make a source version for version '4.1.1.0'
Marked as fixed in versions 4.1.1.0.
> notfixed 1165 4.1.0.1
Bug #1165 [x2goclient] Random background support
There is no source info for the package 'x2goclient' at version '4.1.0.1' with architecture ''
Unable to make a source version for version '4.1.0.1'
No longer marked as fixed in versions 4.1.0.1.
> fixed 1165 4.1.1.0
Bug #1165 [x2goclient] Random background support
There is no source info for the package 'x2goclient' at version '4.1.1.0' with architecture ''
Unable to make a source version for version '4.1.1.0'
Marked as fixed in versions 4.1.1.0.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1093: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1093
1112: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1112
1119: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1119
1121: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1121
1152: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1152
1165: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1165
212: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=212
31: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=31
499: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=499
592: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=592
870: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=870
930: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=930
966: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=966
X2Go Bug Tracking System
Contact owner(a)bugs.x2go.org with problems
[crossposting this to x2go-dev/x2go-user; please reply to x2go-dev only]
Hi $LIST,
there have been numerous complaints in the past about Firefox' lack of
performance when used in an X2Go session, especially over WAN connections.
During some extensive testing and comparison of browser engines, we
discovered that setting the following three values in about:config bring
some improvement to current Firefox versions:
gfx.xrender.enabled (boolean) true
gfx.canvas.azure.backends (string) cairo
gfx.content.azure.backends (string) cairo
Note that xrender support is going away soon.
What we also discovered is that the KDE3-fork Trinity
<https://www.trinitydesktop.org/> brings a Konqueror browser version
that performs way better than Firefox, even with the above three
parameters enabled.
Next, we discovered an actively maintained fork of Firefox 28 - named
Pale Moon <https://www.palemoon.org/>. This gives comparable performance
to Trinity-Konqueror, with the advantage of being way closer to Firefox
in both UI design and codebase, so pages that work fine in Firefox
should work fine in Pale Moon as well - something I wouldn't want to
take for granted with Trinity-Konqueror.
I have uploaded two demo videos showing the performance of Firefox (with
XRENDER only, not cairo) vs. Trinity-Konqueror and vs. Pale Moon:
Firefox (left) vs. TDE-Konqueror (right): https://youtu.be/GfTVhX0UT8M
Firefox (left) vs. Pale Moon (right): https://youtu.be/kilDivhvMZw
I decided to talk to the Pale Moon developers on IRC and it turns out
they plan to revamp their core component
<http://personal.mattatobin.com/image/capture/c4d873f0-9048-4523-8abf-ba5763…>
some time next year ("port Pale Moon to the up and coming Unified XUL
Platform from the
current platform code we have now").
The one person I talked to in particular, Matt A. Tobin, suggested that
the drop in performance came with the drop of support for GTK2.
The Pale Moon developers would be interested in keeping GTK2 support
even in their new core component, but would need some cash and
especially some additional manpower in the form of skilled coders.
So this is a call for help:
- If you're a company that uses X2Go and is interested in supporting
Pale Moon development, either financially or by assigning your own
coders to the project, please let me know.
- If you're a professional coder interested in working on Pale Moon
as long as you get paid for it, please let me know.
- If you're a volunteer coder that wants to work on Pale Moon just for
the greater good of all, please let me know too.
-> I will be coordinating all efforts from the X2Go side of things.
Any questions, suggestions, comments, etc. please follow up either in
X2Go-Dev or via PM.
Kind Regards,
Stefan Baur
--
BAUR-ITCS UG (haftungsbeschränkt)
Geschäftsführer: Stefan Baur
Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364
Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243
Iirc systemd refused usernames starting with a number. There was a huge
discussion in the systemd bugtracker but I don't remeber the outcome
anymore.
Part of the problem is that commands accept both usernames and userid AS
parameters and there just be some clear way to distinguish those two.
I suggest checking the systemd bugtracker before starting another
discussion here ;-) See here: https://github.com/systemd/systemd/issues/6237
Uli
Am 24.10.2017 21:42 schrieb "Norman Gray" <gray(a)nxg.name>:
Greetings.
[I'm happy to submit this as a bug at bugs.x2go.org, but <
https://wiki.x2go.org/doku.php/wiki:bugs> recommends discussing potential
bugs here beforehand]
At present, x2goserver sanitises usernames with a regexp in x2goutils.pm
and in x2gosqlitewrapper.pl (same in both places). That's:
if ($string =~ /^([a-zA-Z\_][a-zA-Z0-9\_\-\.\
@]{0,47}[\$]?)\-([\d]{2,4})\-([\d]{9,12})\_[a-zA-Z0-9\_\-\.]*\_dp[\d]{1,2}$/)
{
A username of, eg, '1234567x' fails this test. I believe such a username
should not fail.
* POSIX/Single Unix says of the username simply "To be portable across
systems conforming to POSIX.1-2008, the value is composed of characters
from the portable filename character set. The <hyphen-minus> character
should not be used as the first character of a portable user name." (see <
http://pubs.opengroup.org/onlinepubs/9699919799/>, paragraph 3.437)
* The Debian useradd(8) page recommends something matching
/^[a-z_][a-z0-9_-]*$/, but goes on to say "On Debian, the only constraints
are that usernames must neither start with a dash ('-') nor contain a colon
(':') or a whitespace (space: ' ', end of line: '\n', tabulation: '\t',
etc.). Note that using a slash ('/') may break the default algorithm for
the definition of the user's home directory." (see eg <
https://www.unix.com/man-page/linux/8/useradd/>)
* The corresponding RedHat/CentOS manpage doesn't even include that, and
instead says only "Usernames may only be up to 32 characters long."
FreeBSD is similarly laid-back about the username.
I myself think that a username like '1234567x' is asking for at least a
little bit of trouble, but those are the networked usernames I'm having to
deal with, so that trouble is not of my asking. Also, I suspect that the
trailing character is there precisely in order to avoid this matching
/^[0-9]+$/, and thus to be interpretable as a number.
This does appear to be the source of my login problems, since if I hack the
two files above, to have the regexp start with [a-zA-Z0-9\_], then my users
can log in without difficulty. This hacking is obviously not a great
solution.
This issue was discussed on the user list a little while ago <
http://lists.x2go.org/pipermail/x2go-user/2015-April/003161.html> (that's
what gave me the aha!). There, Mihai Moldovan said "That's
non-standard-compliant and you're basically on your own when doing "funky
stuff"." To be clear, I think such usernames are less than ideal, but I
don't think they count as funky or non-compliant.
----
As a distinct but related matter, when a failing username is rejected by
this test, the session doesn't fail, but simply seems to hang, giving no
feedback about the problem, nor, as far as I can see, reporting anything in
the logs. Whatever the decision about this report, it would be useful to
fail in a more communicative way.
I'd be interested in your views.
Best wishes,
Norman
--
Norman Gray : https://nxg.me.uk
_______________________________________________
x2go-dev mailing list
x2go-dev(a)lists.x2go.org
https://lists.x2go.org/listinfo/x2go-dev
Hi
This is just a short notice to let you know that I put Jenkins into shutdown
mode which doesn't allow new builds.
This is a precaution measure until the Debian bug that might upload nightly
packages into the release repository[0] is fixed.
Please do not override or disable it manually.
I will send out an update once the bug is fixed and builds can safely be
performed again.
Mihai
[0] https://bugs.debian.org/879667
Greetings.
[I'm happy to submit this as a bug at bugs.x2go.org, but
<https://wiki.x2go.org/doku.php/wiki:bugs> recommends discussing
potential bugs here beforehand]
At present, x2goserver sanitises usernames with a regexp in x2goutils.pm
and in x2gosqlitewrapper.pl (same in both places). That's:
if ($string =~
/^([a-zA-Z\_][a-zA-Z0-9\_\-\.\@]{0,47}[\$]?)\-([\d]{2,4})\-([\d]{9,12})\_[a-zA-Z0-9\_\-\.]*\_dp[\d]{1,2}$/)
{
A username of, eg, '1234567x' fails this test. I believe such a
username should not fail.
* POSIX/Single Unix says of the username simply "To be portable
across systems conforming to POSIX.1-2008, the value is composed of
characters from the portable filename character set. The <hyphen-minus>
character should not be used as the first character of a portable user
name." (see <http://pubs.opengroup.org/onlinepubs/9699919799/>,
paragraph 3.437)
* The Debian useradd(8) page recommends something matching
/^[a-z_][a-z0-9_-]*$/, but goes on to say "On Debian, the only
constraints are that usernames must neither start with a dash ('-') nor
contain a colon (':') or a whitespace (space: ' ', end of line: '\n',
tabulation: '\t', etc.). Note that using a slash ('/') may break the
default algorithm for the definition of the user's home directory." (see
eg <https://www.unix.com/man-page/linux/8/useradd/>)
* The corresponding RedHat/CentOS manpage doesn't even include that,
and instead says only "Usernames may only be up to 32 characters long."
FreeBSD is similarly laid-back about the username.
I myself think that a username like '1234567x' is asking for at least a
little bit of trouble, but those are the networked usernames I'm having
to deal with, so that trouble is not of my asking. Also, I suspect that
the trailing character is there precisely in order to avoid this
matching /^[0-9]+$/, and thus to be interpretable as a number.
This does appear to be the source of my login problems, since if I hack
the two files above, to have the regexp start with [a-zA-Z0-9\_], then
my users can log in without difficulty. This hacking is obviously not a
great solution.
This issue was discussed on the user list a little while ago
<http://lists.x2go.org/pipermail/x2go-user/2015-April/003161.html>
(that's what gave me the aha!). There, Mihai Moldovan said "That's
non-standard-compliant and you're basically on your own when doing
"funky stuff"." To be clear, I think such usernames are less than
ideal, but I don't think they count as funky or non-compliant.
----
As a distinct but related matter, when a failing username is rejected by
this test, the session doesn't fail, but simply seems to hang, giving no
feedback about the problem, nor, as far as I can see, reporting anything
in the logs. Whatever the decision about this report, it would be
useful to fail in a more communicative way.
I'd be interested in your views.
Best wishes,
Norman
--
Norman Gray : https://nxg.me.uk