Hi
This is a mass mail to all X2Go lists.
During the past few weeks, I have upgraded the mailing list infrastructure from
Mailman 2.1 to Mailman 3.0. All subscriptions and archived messages have been
imported. Users will NOT need to resubscribe and will continue to get mails.
Apologies for the long downtime, but especially the archive imports took weeks
to complete and had to be done twice, since the backend used in the first run
wasn't suited to the load and amount of data.
Unfortunately, the machine is struggling with the load, and web UI operations
sometimes take quite long to complete or even time out completely. Just try to
refresh and retry the last operation if you see this happening. We will probably
want to upgrade this machine in the future.
I'll split this mail up into a user, an administrator and a technical part. Feel
free to skip the parts that do not interest you.
************************
* USER-VISIBLE CHANGES *
************************
The old Mailman 2.1 infrastructure was quite basic - consisting of a mostly
static HTML-based web interface and statically generated HTML pages for each
message in the archives.
By contrast, Mailman 3.x is much more complex. The web interface is more fancy
and also uses Javascript, the archiver is a separate component known as
Hyperkitty and everything is plugged together via a Python-based Django uwsgi
web service communicating with an internal REST service.
Most importantly, you will have to register to the Django-powered Postorius
service to manage your subscriptions. Management is now centralized and you
won't get password reminders every month for each individual list.
To see a list of all public lists, head to
https://lists.x2go.org/postorius/lists/ ( https://lists.x2go.org/ will redirect
there).
To create an account, use the "Sign Up" button/link in the upper right corner of
the page.
After you have created an account, you will be able to modify all your
subscriptions in one place and all your subscriptions should show up
automatically (provided the account you signed up for uses the same email
address as your subscriptions).
This includes setting digest options, pausing mail transfer, subscribing and
unsubscribing.
If you do not wish to create an account, you can still join or leave mailing
lists by sending messages to nameoflist-join(a)lists.x2go.org or
nameoflist-leave(a)lists.x2go.org. nameoflist-subscribe(a)lists.x2go.org and
nameoflist-unsubscribe(a)lists.x2go.org are aliases that also work. In this case,
you will, however, be unable to change other options.
Archives can be found at https://lists.x2go.org/hyperkitty - note that if you're
logged in to Postorius, you will also be automatically logged in to Hyperkitty.
The archives for a list can also be reached by following the Archive link/button
in Postorius's mailing list info page.
In order not to break old links, the old archive is also still accessible at
https://lists.x2go.org/pipermail/ - albeit in a read-only state that will not be
updated any longer. I have added information to the index pages to reflect that.
**************************
* ADMINISTRATION CHANGES *
**************************
Mailman 3.x allows making users administrators or owners of lists, which can
then change settings, tend to held messages and the like.
Historically, in Mailman 2.1, administration was based upon a password.
I have created a super user account named listadmins(a)lists.x2go.org with the
known password. This user is owner of all lists and can be used to manage every
aspect.
As soon as you are logged in to an account that is either and administrator or
owner of one or multiple lists, you can use Postorius (
https://lists.x2go.org/postorius/lists ) to manage settings, held messages and
the like.
Especially the "held message" interface deserves a bit of explanation.
By default, 10 messages are shown per page. Each message can be selected/ticked
individually or you can all select all messages in a page at once by using the
checkbox left of "Subject" in the table header.
Clicking the buttons "Accept", "Reject" or "Discard" will carry out the
appropriate action on all selected messages. Note, however, that this will not
add the sender to any of the auto-accept, auto-reject or auto-discard lists.
In order to also add the sender of a message to a specific auto-action list,
click on a message. A javascript-based popup will appear with the whole message
text. The popup might not show up instantly, especially if the machine is slow,
so please wait after clicking on message! If you get an error about the message
not existing, refresh the page and retry. The popup includes two buttons at the
bottom to show either the full source of the message or just the headers, which
can be very handy. Above the "Rejection reason" text box, a "--- Set member
moderation ---" drop down menu can be used to select the desired auto action
(hold, reject, discard, accept or default processing). After setting this
correctly, use any of the "Accept", "Reject" or "Discard" buttons below the text
box to submit the result and carry out the desired action.
Django has a special admin interface at https://lists.x2go.org/admin that can be
used to manage data in Hyperkitty (the archiver), for instance to delete
messages from the archive. Usually, you will not need to use this admin interface.
*************************
* TECHNICAL INFORMATION *
*************************
Unfortunately, Mailman 3.x is horribly broken by default in Ubuntu 24.04 (c.f.,
https://bugs.launchpad.net/ubuntu/+source/mailman-suite/+bug/2062960 and other
bug reports).
The mailman version is too old to be compatible with dependencies it needs,
leading to a non-working setup out of the box.
Upstream recommends installing mailman via a Python venv, but that would
essentially decouple it from the system (and system updates), which I don't like.
For this reason, I backported a lot of code to fix the Mailman 3 as installed
via the distro packages.
However, I've only done so purely on the file system and haven't created
modified .deb packages.
Please be extra careful when upgrading ymir and please don't update any packages
related to Django, Mailman, Hyperkitty or Xapian! This will undo all of my
changes and break the whole mailing list infrastructure.
I plan on backporting newer versions from Debian Testing or Unstable to Ubuntu
24.04/noble in a proper .deb-based way, but that's not something I can easily do
right away.
Initially, I set up Mailman and Hyperkitty to use SQLite3 as its database
backened, but that turned out to be excruciatingly slow.
It's now using the PostgreSQL 16 backend, which works better, but also uses
quite a bit of system memory, so the machine's swap space is always in use.
When upgrading PostgreSQL in the future, the databases will also need to be
migrated correctly.
Hyperkitty can optionally use a full-text search engine to provide better search
capabilities. Initially, I used Whoosh, but it turned out to be rather resource
hungry and, unfortunately, also slow. We're now using Xapian with a fix for long
terms, which unfortunately has not been applied upstream yet. (
https://github.com/notanumber/xapian-haystack/pull/238 )
I've enabled Markdown rendering mode in Hyperkitty for x2go-announcements,
x2go-dev, x2go-user, x2go-user and x2go-i18n. This crashed badly on some mails
yesterday, but should now fall back correctly to the basic text renderer in case
of failures.
Mihai
Dear $ALL,
As stated in the subject line, X2Go: The Gathering 2024 will take place
at Linuxhotel, Essen, Germany, from Friday afternoon, 2024-06-28, to
Sunday afternoon/evening, 2024-06-30 and will, again, be a three-day
"work and play" (coding, chatting, sightseeing, socializing) event.
X2Go: The Gathering is the annual event where users, admins, and
developers (including the i18n volunteers) of X2Go meet face to face, to
discuss current X2Go-related issues, fix open bugs, and have a good time
getting to know each other.
As there is some overlap between X2Go, Arctica, and orca e.V., you can
expect to see members of those groups as well.
After 4 years spent "in exile" (with a skeleton crew of volunteers
meeting at shackspace in 2020, and going completely virtual in the years
2021-2023) due to the pandemic situation, we are finally returning to a
full real-life event at Linuxhotel (though we will be
streaming/recording our sessions, so you can join in remotely as well).
Note that while we do not require masks to be worn, it is still
recommended and endorsed, especially in indoor areas.
At the time of writing this invitation, and using some educated guesses
regarding under-reporting and wastewater analysis, Covid infection rate
in Germany is roughly somewhere between 1 out of 1000 and 1 out of 500
people per week.
*ATTENTION!*
If you want to join us *and* want to sleep in one of the hotel rooms at
the Linuxhotel, we need the number of beds and nights you want to
reserve, as well as *your full name* (as printed on your passport) and
*your nationality* by *2024-06-07* *23:59:59* *CEST*!!!
Very important!!! After that date, we cannot guarantee that we will
still be able to reserve a room for you! First come, first serve! As
single rooms are in short supply, please book your bed in a 2- or 3-bed
room, unless you absolutely have to use a single room.
Please send your reservation request to <mailto:vorstand@orca-ev.de>
with the text "The Gathering" somewhere in the subject and bug me
publicly on the X2Go-Project list if you don't receive a confirmation by
e-mail after a day or two.
If for some reason or other you do *not* need a place to sleep at
Linuxhotel, but *do* want to join us, please *still* let us know in
advance that you're planning to visit. There's no such hard deadline as
for the room reservations, but you will need to "check in" (and there
will be an "Admission fee") for our gathering with the Linuxhotel staff,
so please *do* let us know in advance.
We will be updating the Wiki page
<http://wiki.x2go.org/doku.php/events:x2go-gathering-2024> as more
information becomes available.
We already have one sponsor for the event - CFD.direct have kindly
offered to sponsor the Pizzas on Friday evening - but the more, the
merrier, so if you know someone willing and able to co-sponsor the
event, please let us know at <mailto:vorstand@orca-ev.de> as well.
Whether they wish to send us some "swag" with their company branding, or
pledge money that we can use to lower dining and lodging costs for our
participants (or to lower their health risks by providing masks,
sanitizers and free testing), their sponsorship is greatly appreciated.
Sincerely,
Stefan Baur, "X2Go: The Gathering" event organizer
Dear $ALL,
In exactly one month, from December 11th to December 15th, we'll have
our annual X2Go meeting for users, admins and code contributors to X2Go
- once again, 100% virtual/online, so it's a "The Spread" and not a "The
Gathering" once more. We're hoping to see you there.
We'll post a link to a virtual meeting room in due time, and expect to
be streaming/recording the event to YouTube or a similar platform as well.
Starting time will likely be 20:00 CET, as last year, unless a
significant number of participants requests an earlier start time (say,
18:00 CET or 19:00 CET) - please let me know (off-list, see below for
contact details) if you'd like to request an earlier start time.
Sadly, in summer, where Covid numbers and weather conditions would have
allowed for a real-life meeting, we had a scheduling conflict. And as
the numbers are rising again, we cannot in good conscience host a
real-life international conference - especially as some of our members
have vulnerable household members or are vulnerable persons themselves.
The event page (still work in progress) can be found here:
<https://wiki.x2go.org/doku.php/events:x2go-spread-2023>
Each evening has one, max. two time slots for a talk/presentation.
At the moment, three topics are confirmed:
- The usual "X2Go: State of the Union" opening speech
- A report looking back at our latest stable X2Go release, which brought
KDrive into the stable repository, and showing what still needs to be
done Re: KDrive.
- A report on how we used betterplace.org for collecting X2Go-related
donations in the last 18 months, and an open discussion on how we
could improve our usage of this platform.
I am also hoping for a certain volunteer to commit to a fourth
presentation regarding the latest changes and improvements in NX-Libs -
since Arctica/NX-Libs pushed out a new release as well (on which our
X2Go release is also based, obviously).
This means we will have at least one more open talk slot - possibly
more, if the two release reports for NX-Libs and X2Go only take 10-15
minutes each.
If nobody volunteers, I might fill that remaining slot with a quick demo
of how to netboot X2Go-TCE-Live via iPXE in EFI and legacy mode.
But I'm really hoping for more volunteers for talks/demos/presentations
- so if you would like to present something
X2Go/NX-Libs/Arctica-related, please let me know (again, off-list, see
below for contact details).
We also have the option to prerecord your talk, in case your schedule
doesn't allow for a live presentation and/or your internet connection is
too flaky. It would be nice if you're available for a live Q&A round
after your talk, though (via text-only chat or audio-only stream is fine).
Please note that this time, the orca e.V. annual meeting will take place
on the Sunday morning *before* the start of X2Go: The Spread 2023. All
orca e.V. members have already received their invitation.
To contact me, please do not hit "reply"/"reply to all"/"reply to list",
but rather, send a *new* E-Mail to <mailto:X2Go-ML-1@baur-itcs.de>.
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
Dear $ALL,
As stated in the subject line, X2Go: The Gathering 2021 - AKA "Over
9000!" - will be an entirely virtual event and will take place from
Friday afternoon, 2021-12-03, to Sunday afternoon/evening, 2021-12-05.
If you're wondering what the “Over 9000!” is about, take a look at
<https://en.wikipedia.org/wiki/It%27s_Over_9000!> and at
<https://experience.arcgis.com/experience/478220a4c454480e823b17327b2bf1d4>,
especially the box titled “COVID-19-Fälle” (active Covid-19 cases),
which is way over 9000.
Under normal conditions, X2Go: The Gathering would be the annual event
where users, admins, and developers (including the i18n volunteers) of
X2Go, as well as members from the Arctica project and the orca e.V.
nonprofit meet face to face, to discuss current X2Go-related issues, fix
open bugs, and have a good time getting to know each other.
Sadly, due to the ongoing Covid-19 pandemic, this year's X2Go: The
Gathering will have to remain entirely virtual.
Due to various reasons, we were unable to schedule the event earlier in
the year, where Covid-19 infection numbers were lower and where meeting
outside or keeping the windows open all day might have worked, so we're
stuck with this late event date, which sadly coincides with the fourth
Covid-19 wave here in Germany.
This means we will be meeting via Jitsi and we will be live-streaming
the event via YouTube. Links to the streams will be posted on
<http://wiki.x2go.org/doku.php/events:x2go-gathering-2021> each day
before the stream begins.
You can join in any time, even on short notice, no sign-up required.
We will be updating the Wiki page
<http://wiki.x2go.org/doku.php/events:x2go-gathering-2021> as more
information becomes available - especially the schedule, which is
currently still in the works.
We plan to release (at least) three new features for X2Go at or at least
shortly after this year's X2Go: The Gathering, namely:
- the HTML5 client
- server-side X2Go-KDrive support, and
- X2Go support in Remmina.
The former two are currently already available via nightly builds, but
we intend to declare them stable and turn them into a proper release.
The latter should become available with the next Remmina release.
Also, we intend to present the current state of X2Go-TCE on the
Raspberry Pi.
If time permits (and the individuals required for this are available for
it), we will also attempt to move our bugtracker and git to our own
gitlab instance (at least for new bugs).
As this year's event is an entirely virtual event, there is not really a
need for event sponsorships.
However, if you're a company that had planned to sponsor the event, we'd
appreciate it if you'd redirect the money to some paid work on X2Go
instead.
A list of companies/individuals available for this can be found
here: <https://wiki.x2go.org/doku.php/doc:professional-support>
If you're not sure what to sponsor - while the features already
mentioned above are ready to be included in a stable release, they could
still use some more love and affection.
For example:
- The HTML5 and Remmina clients don't support file and printer
sharing yet
- The HTML5 client also lacks sound support
- The HTML5 client only works with KDrive, not "classic" X2Go-NX
(to be honest, NX inside HTML5 doesn't really make sense since we are
about to release KDrive as stable, but if you feel you have a good
reason for it, let us know ...)
- Remmina only works with "classic" X2Go-NX, not KDrive, and only on a
client that still supports X11 (even though Remmina in general also
works on a Wayland-only client) -> KDrive support would require a
shared library for KDrive, either written in GTK or with more low
level rendering toolskits (e.g. Glib-2.0 and Cairo, etc.).
- KDrive probably needs some more work on the Windows (and possibly
macOS) Client side.
- X2Go-TCE on the Pi, while functional in general, still has some
untested areas and is a little rough around the edges.
- Also, we have been contacted once again regarding USB forwarding
support in X2Go, so anyone interested in co-sponsoring this feature
should speak up or at least contact me off-list - maybe we can get a
co-sponsoring going, lowering the cost for all parties involved.
And of course, you can also make donations, either in general or
specifically earmarked for X2Go, via orca e.V.
The entire schedule, save for the time and date of the orca e.V. meeting
on Sunday, is still in a state of flux. We may move some presentations
to a Saturday slot, depending on the availability of the speakers
involved. If you would like to present something, please contact me via
E-Mail (<mailto:X2Go-ML-1@baur-itcs.de>) and let me know the title of
your presentation/talk, the expected duration and the times you would be
available. Of course, you can also pre-record your presentation/talk if
you want, but you will have to upload it to YouTube yourself and let us
know the link (it may be unlisted, but must not be marked "private").
Sincerely,
Stefan Baur, "X2Go: The Gathering" event organizer
PS: Please heed the "reply-to" when replying, and make sure your reply
gets sent only to <mailto:x2go-ml-1@baur-itcs.de>, as this message is
sent to multiple X2Go mailing lists at once (and it is likely you are
not subscribed to all of them, so your replies would clog up the
moderation queue for the others).
--
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
* On 2/6/20 3:35 PM, Klaus Ade Johnstad wrote:
> And here is the nb_no file.
Thanks!
Applied as
https://code.x2go.org/gitweb?p=x2goclient.git;a=commitdiff;h=e9557b0403e66b…
with fixups in
https://code.x2go.org/gitweb?p=x2goclient.git;a=commitdiff;h=f858e937d4bcf7…
.
I noticed that you didn't include a plural translation for "X.Org serveren
startet ikke etter %n forsøk." - the same old singular/plural form translation
stuff again...
If I understand the Norwegian grammar correctly, forsøk is both singular and
indefinite plural, while the definite plural would look like forsøka or
forsøkene. Since forsøk is used in its indefinite form, based on the context,
the same sentence can be used in both cases, right? I've hence added it the
plural case as well, unmodified.
Next, there seems to be some inconsistency regarding "suspend(/,ing,ed)".
Sometimes the translation uses "frakoblet" (which seems to roughly translate to
"disconnected" or "offline"), sometimes you're using "henge" (which seems to
roughly translate to "hang", but also "suspend") and other times you're using
"utset" (which seems to roughly translate to "delay", "postpone", "defer" etc.).
I'd argue that this might be confusing to users. Maybe we should consolidate
that? I don't like "henge" in this context, since I believe that it refers to
the physical act of suspending something (e.g., suspending/hanging something
from a tree), which doesn't seem to fit here. Likewise, "utset" is more likely
connoted with putting something aside for later review, which might not actually
be a bad metaphor, but I'm still not sure whether it would fit the English
meaning of "disconnect to interrupt" used in this context. Due to this,
"frakoblet" (and its forms) might actually come closest to the meaning we want
to deliver here. I've seen that Norwegian also includes the word "suspendere",
but it might be archaic and not be used and understood widely (or at all). What
are your thoughts?
Lastly, some original strings include descriptions like "The client's behavior
is undefined if this flag is used for [...]". You've sometimes translated that
as "Dette valget har kun betydning ved faktisk autentisering mot [...]" (which
seems to roughly translate back to "This option only matters/has a meaning when
actually authenticating with [...]") and once with "Dette valget har ingen
effekt om du ikke benytter deg av en [...]" (which seems to roughly translate
back to "This option has no effect if you do not use [...]").
I've chosen the original string very carefully and while programmers should be
very familiar with the meaning of "undefined", users and translators might not
be. The (subtle) difference between "no effect" and "undefined" is that using
the former is safe since it won't change any behavior, but invoking "undefined"
behavior might lead to anything. It *could* be safe because nothing happens, but
it could likewise also crash the program or delete random files from your file
system or eject optical drive trays or feed a cat or drown a fish or ...
That is, "undefined" can mean having positive, neutral or negative effects. It
is, implicitly and by extension, also a warning to not use the options if the
mentioned broker type is not used. The current translation is misleading in that
it only emphasizes the neutral (or positive) aspects, while ignoring any
negative ones. Can we find a better way of translating this "undefined behavior"
into Norwegian?
Mihai
Hi
I plan to release a new version of X2Go Client in about two weeks.
The deadline for translations a normal two-weeks one: February 8, 2020.
Current status in X2Go Client (compared to the previous release):
Updating 'res/i18n/x2goclient_cs.ts'...
Found 705 source text(s) (4 new and 701 already existing)
Updating 'res/i18n/x2goclient_de.ts'...
Found 705 source text(s) (7 new and 698 already existing)
Kept 8 obsolete entries
Updating 'res/i18n/x2goclient_da.ts'...
Found 705 source text(s) (7 new and 698 already existing)
Kept 1 obsolete entries
Updating 'res/i18n/x2goclient_es.ts'...
Found 705 source text(s) (7 new and 698 already existing)
Kept 1 obsolete entries
Updating 'res/i18n/x2goclient_et.ts'...
Found 705 source text(s) (7 new and 698 already existing)
Kept 8 obsolete entries
Updating 'res/i18n/x2goclient_fi.ts'...
Found 705 source text(s) (7 new and 698 already existing)
Kept 8 obsolete entries
Updating 'res/i18n/x2goclient_fr.ts'...
Found 705 source text(s) (7 new and 698 already existing)
Kept 1 obsolete entries
Updating 'res/i18n/x2goclient_nb_no.ts'...
Found 705 source text(s) (7 new and 698 already existing)
Kept 1 obsolete entries
Updating 'res/i18n/x2goclient_nl.ts'...
Found 705 source text(s) (7 new and 698 already existing)
Kept 1 obsolete entries
Updating 'res/i18n/x2goclient_pt.ts'...
Found 705 source text(s) (7 new and 698 already existing)
Kept 1 obsolete entries
Updating 'res/i18n/x2goclient_ru.ts'...
Found 705 source text(s) (7 new and 698 already existing)
Kept 1 obsolete entries
Updating 'res/i18n/x2goclient_sv.ts'...
Found 705 source text(s) (7 new and 698 already existing)
Kept 1 obsolete entries
Updating 'res/i18n/x2goclient_tr.ts'...
Found 705 source text(s) (7 new and 698 already existing)
Kept 1 obsolete entries
Updating 'res/i18n/x2goclient_zh_tw.ts'...
Found 705 source text(s) (7 new and 698 already existing)
Kept 1 obsolete entries
For a description of the translation process, please refer to
https://wiki.x2go.org/doku.php/wiki:development:i18n and the corresponding
README.i18n files in the component repository:
- https://code.x2go.org/gitweb?p=x2goclient.git;a=blob;f=README.i18n;hb=master
Mihai
* On 2/5/20 11:52 PM, Ruda Vallo wrote:
> I have a problem with sending the mail to the mailing list, so I am
> sending to you directly the Czech translations for X2Go client in
> attachment.
Thanks... and weird. I haven't seen any rejected messages (e.g., due to the file
size being too big) and you're subscribed to the list. Might have been the spam
filter catching it for some reason.
Nevertheless:
Applied as
https://code.x2go.org/gitweb?p=x2goclient.git;a=commitdiff;h=d9cacbd246adbb…
with fixups in
https://code.x2go.org/gitweb?p=x2goclient.git;a=commitdiff;h=03d4d3d0a0d741…
.
Just a whitespace fix and marking an actually translated entry as translated
now. The comment is pretty much obsolete as well, so I removed it.
Mihai
Dear $ALL,
As stated in the subject line, X2Go: The Gathering 2019 will take place
at Linuxhotel, Essen, Germany, from Friday afternoon, 2019-09-27, to
Sunday afternoon/evening, 2019-09-29m and will, again, be a three-day
"work and play" (coding, chatting, sightseeing, socializing).
X2Go: The Gathering is the annual event where users, admins, and
developers (including the i18n volunteers) of X2Go meet face to face, to
discuss current X2Go-related issues, fix open bugs, and have a good time
getting to know each other.
As there is some overlap between X2Go, Arctica, and orca e.V., you can
expect to see members of those groups as well.
*ATTENTION!* If you want to join us *and* want to sleep in one of the
hotel rooms at the Linuxhotel, we need the number of beds and nights you
want to reserve, as well as *your full name* (as printed on your
passport) and *your nationality* by *2019-08-19* *23:59:59* *CEST* (yes,
that's 2019-08-19, *not* 2019-09-19)!!! Very important!!! After that
date, we will be unable to reserve a room for you! First come, first
serve! As single rooms are in short supply, please book your bed in a
2- or 3-bed room, unless you absolutely have to use a single room.
Please send your reservation request to X2Go-ML-1(a)baur-itcs.de with the
text "The Gathering" somewhere in the subject and bug me publicly on the
X2Go-Project list if you don't receive a confirmation by e-mail after a
day or two.
Currently, the following core team members already have valid
registrations and thus do not need to re-register:
- Baur, Stefan 'Stefan#1' (BAUR-ITCS)
- DePaulo, Michael Swinick 'Mike#2'
- Mike 'Mike#1' Gabriel (DAS-NETZWERKTEAM)
- Grabowski, Juri (LiHAS)
- Moldovan, Mihai 'ionic' (BAUR-ITCS)
- Sibiller, Ulrich
- Graesing, Heinz-M. 'h1.org'
- Shneyder, Oleksandr 'Alex' (phoca)
If for some reason or other you do *not* need a place to sleep at
Linuxhotel, but *do* want to join us, please *still* let us know in
advance that you're planning to visit. There's no such hard deadline as
for the room reservations, but you will need to "check in" (and there
will be an "Admission fee") for our gathering with the Linuxhotel staff,
so please *do* let us know in advance.
We will be updating the Wiki page
<http://wiki.x2go.org/doku.php/events:x2go-gathering-2019>
as more information becomes available. Certain things, like our
breakfast options, or having lunch/dinner served by Linuxhotel instead
of having to order from a delivery service, can only be planned once we
know the exact number of participants.
Since we're still in the early planning phase, we do not yet have any
sponsors for the event (though we plan to approach the "usual suspects"
from previous years), so if you know someone willing and able to
co-sponsor the event, please let me know at <X2Go-ML-1(a)baur-itcs.de>.
Whether they wish to send us some "swag" with their company branding, or
pledge money that we can use to lower dining and lodging costs for our
participants, their sponsorship is greatly appreciated.
Sincerely,
Stefan Baur, "X2Go: The Gathering" event organizer
--
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
Hello Mike,
here is my locale setup:
LANG=cs_CZ.UTF-8
LANGUAGE=cs_CZ
LC_CTYPE="cs_CZ.UTF-8"
LC_NUMERIC="cs_CZ.UTF-8"
LC_TIME="cs_CZ.UTF-8"
LC_COLLATE="cs_CZ.UTF-8"
LC_MONETARY="cs_CZ.UTF-8"
LC_MESSAGES="cs_CZ.UTF-8"
LC_PAPER="cs_CZ.UTF-8"
LC_NAME="cs_CZ.UTF-8"
LC_ADDRESS="cs_CZ.UTF-8"
LC_TELEPHONE="cs_CZ.UTF-8"
LC_MEASUREMENT="cs_CZ.UTF-8"
LC_IDENTIFICATION="cs_CZ.UTF-8"
LC_ALL=
Thanks and greets,
Ruda
Dne 21. 02. 19 v 12:00 x2go-i18n-request(a)lists.x2go.org napsal(a):
> Send x2go-i18n mailing list submissions to
> x2go-i18n(a)lists.x2go.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.x2go.org/listinfo/x2go-i18n
> or, via email, send a message with subject or body 'help' to
> x2go-i18n-request(a)lists.x2go.org
>
> You can reach the person managing the list at
> x2go-i18n-owner(a)lists.x2go.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of x2go-i18n digest..."
>
>
> Today's Topics:
>
> 1. Re: Czech translation of X2Go's PyHoca-GUI (Mike Gabriel)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 20 Feb 2019 12:22:43 +0000
> From: Mike Gabriel <mike.gabriel(a)das-netzwerkteam.de>
> To: Ruda Vallo <ruda(a)vallo.cz>
> Cc: x2go-i18n(a)lists.x2go.org
> Subject: Re: [X2Go-i18n] Czech translation of X2Go's PyHoca-GUI
> Message-ID:
> <20190220122243.Horde.x-NtKhu_q3b_7YOPI6VyYhz(a)mail.das-netzwerkteam.de>
>
> Content-Type: text/plain; charset="utf-8"; Format="flowed";
> DelSp="Yes"
>
> Hi Ruda,
>
> On Mo 18 Feb 2019 21:59:16 CET, Ruda Vallo wrote:
>
>> Hi Mike,
>>
>> I am sending a Czech translation in attachment.
> Thanks!
>
>> I have some issues with translation testing:
>>
>> 1) I have trouble with UTF-8 characters, while pyhoca-gui is connecting
>> to X2Go server.
> Ok...
>
>> This is debug output:
>>
>> ### PyHoca-GUI running in development mode ###
>> pyhoca-gui[8148] (x2gosessregistry-pylib) NOTICE: registering X2Go
>> session x2go-staging...
>> pyhoca-gui[8148] (x2goclient-pylib) NOTICE: initializing X2Go session...
>> pyhoca-gui[8148] (x2gocontrolsession-pylib) NOTICE: connecting to
>> [x2go-staging]:22
>> Traceback (most recent call last):
>> File "/usr/lib/python2.7/dist-packages/gevent/greenlet.py", line 536,
>> in run
>> result = self._run(*self.args, **self.kwargs)
>> File "/usr/lib/python2.7/dist-packages/pyhoca/wxgui/frontend.py", line
>> 779, in _do_authenticate
>> self.notifier.send('%s - unknown error' % profile_name, _(u'An
>> unknown error occurred during authentication!'), icon='auth_error',
>> timeout=4000)
>> File "/usr/lib/python2.7/dist-packages/pyhoca/wxgui/notify.py", line
>> 138, in send
>> self._pyhoca_logger('[%s] %s' % (title.encode(utils.get_encoding()),
>> text.encode(utils.get_encoding())), loglevel=log.loglevel_NOTICE)
>> File "/usr/lib/python2.7/dist-packages/x2go/log.py", line 102, in message
>> msg = msg.encode(utils.get_encoding())
>> UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 38:
>> ordinal not in range(128)
> Ok....
>
>> I googled it and created HOTFIX to pyhoca-gui. I added this to the
>> beginning of the file:
>>
>> import sys
>> reload(sys)
>> sys.setdefaultencoding('UTF8')
> Urgh... Ok... need to take a look at that. PyHoca-GUI is still at
> Python2 whereas PyHoca-CLI is already Python3. I guess the proper
> solution is to switch to Python3 (where all strings are UTF-8).
>
> What is your system's locale that pyhoca-gui is running under (send me
> output of the "locale" command).
>
>> I use Ubuntu 18.04 with Gnome3 and Mate.
> Ok.
>
>> 2) I have problem with Gnome3 and pyhoca-gui. In Gnome3 on startup
>> pyhoca-gui is hidden in systray, but Gnome 3 does not show it.
>>
>> I installed Mate. With Mate everything works and I have tested on it.
> This is a known issue. GNOMEv3 dropped Xembed support and PyHoca-GUI
> uses Xembed to embed its icon into the notification area of
> traditional desktops.
>
> I will port the Xembed based tray icon to Ayatana AppIndicator in the
> far future, then you may get it visible on GNOMEv3 again, if you are
> lucky (the GNOMEv3 people think about dropping Indicator support from
> GNOMEv4, soo...).
>
> Greets,
> Mike
Hi Ruda,
I am about to prepare a release for X2Go's alternative client GUI,
called PyHcoa-GUI. I plan to upload the package asap.
Did you start with the translation of PyHoca-GUI at the time we
exchanged emails on X2Go translations already?
If not, do you think you can work on that on short notice?
Most other languages are ok'ish and I will probably get a permission
for uploading i18n changes in upstream to Debian after the upcoming
soft-freeze (for Debian 10).
Greets,
Mike
--
DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139
GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31
mail: mike.gabriel(a)das-netzwerkteam.de, http://das-netzwerkteam.de