x2go-dev July 2016

x2go-dev@lists.x2go.org

20 participants
125 discussions

Bug#864: Port X2Go Client to Qt5
by Mike Gabriel 28 Jun '17

28 Jun '17

Package: x2goclient Severity: important Qt4 will have end of life in 2017. X2Go Client and other X2Go componets (e.g., X2Go Desktop Sharing) will be affected by that. See [1] for reference. Greets, Mike [1] http://perezmeyer.blogspot.de/search/label/planetdebian-en -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabriel(a)das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.x…

2 1

Bug#618: KDE panel and LXDE panel are hidden after login to x2go session
by Aki Ketolainen 29 May '17

29 May '17

Package: x2goagent Version: 2:3.5.0.27-0~446~ubuntu14.04.1 Package: x2goserver Version: 4.0.1.15-0~847~ubuntu14.04.1 Package: x2goserver-extensions Version: 4.0.1.15-0~847~ubuntu14.04.1 Package: x2goclient Version: 4.0.2.1+hotfix1+build4 Server = Ubuntu 14.04.1 LTS (x86) Client = Windows 8.1 (x86_64) After logging into x2go Server, I see either KDE or LXDE start up, as configured. Start up finishes but the panel in either KDE or LXDE is not shown. I press Alt+F2 to open the 'Run' application and start xterm. I run 'xrandr -s 1280x720', the x2go/X11 window size changes OK and the menu in either KDE or LXDE shows up automatically. I saw that someone had ran into this bug in 2012: http://readlist.com/lists/gentoo.org/gentoo-user/33/169010.html but there was just a temporary resolution to the problem.

3 4

Bug#1046: x2go session causes dbus conflicts with logged in desktop on Fedora 24
by Andy Wang 10 Mar '17

10 Mar '17

Package: x2goserver Version: 4.0.1.19-8.fc24 When attempting to login with a client desktop session that uses dbus while logged in as the same user on the console causes an error to appear in a pop up window: Could not acquire name on session bus You can dismiss the error but the desktop never full starts and attempts to logout triggers the logout on the console session. >From the error, I this appears to be resolved by using a custom session script in x2go and making sure to call: unset DBUS_SESSION_BUS_ADDRESS For example: #!/bin/sh unset DBUS_SESSION_BUS_ADDRESS # redirect to /dev/null due to x2go bug 914 /usr/bin/mate-session > /dev/null Doing some digging, it looks like the dbus socket (/usr/lib/systemd/user/dbus.socket) on fedora 24 (dbus-1.11.2-1.fc24.x86_64) does this: ExecStartPost=-/usr/bin/systemctl --user set-environment DBUS_SESSION_BUS_ADDRESS=unix:path=%t/bus And sets the DBUS_SESSION_BUS_ADDRESS for all logins for your user. This same workaround appears to be what tigervnc used as their permanent solution: https://github.com/TigerVNC/tigervnc/commit/c071e493a093d7ee9a568729dd2e151… So I think this is the proper solution. FYI, a bug was filed against Fedora as well: https://bugzilla.redhat.com/show_bug.cgi?id=1350004

3 2

Bug#486: Addendum
by Denny Milakara 01 Mar '17

01 Mar '17

No problem to continue session with McOS Client 4.0.3.1.

2 1

Bug#499: Fwd: [Bug 1097757] New: [abrt] x2goclient: QString(): x2goclient killed by SIGSEGV
by Orion Poplawski 01 Mar '17

01 Mar '17

Package: x2goclient Version: 4.0.2.0 Looks like: #1 id (this=0x0) at ../sessionbutton.h:39 No locals. #2 ONMainWindow::slotSuspendSess (this=this@entry=0x1ad1ab0) at ../onmainwindow.cpp:4620 X2goSettings st ( "sessions" ); QString sid=lastSession->id(); lastSession is null and not being checked. Probably applies to other parts of the code as well. -------- Original Message -------- Subject: [Bug 1097757] New: [abrt] x2goclient: QString(): x2goclient killed by SIGSEGV Date: Wed, 14 May 2014 13:12:55 +0000 From: bugzilla(a)redhat.com To: orion(a)cora.nwra.com https://bugzilla.redhat.com/show_bug.cgi?id=1097757 Bug ID: 1097757 Summary: [abrt] x2goclient: QString(): x2goclient killed by SIGSEGV Product: Fedora Version: 20 Component: x2goclient Assignee: orion(a)cora.nwra.com Reporter: ndbecker2(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: orion(a)cora.nwra.com Group: fedora_contrib_private Description of problem: clicked on grayed-out resume button, or something like that Version-Release number of selected component: x2goclient-4.0.2.0-1.fc20 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/bin/x2goclient crash_function: QString executable: /usr/bin/x2goclient kernel: 3.14.2-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 QString at /usr/include/QtCore/qstring.h:725 #1 id at ../sessionbutton.h:39 #2 ONMainWindow::slotSuspendSess at ../onmainwindow.cpp:4620 #3 ONMainWindow::slotResumeSess at ../onmainwindow.cpp:4526 #4 ONMainWindow::slotResumeDoubleClick at ../onmainwindow.cpp:6005 #5 ONMainWindow::qt_static_metacall at moc_onmainwindow.cpp:399 #6 QMetaObject::activate at kernel/qobject.cpp:3567 #7 QAbstractItemView::activated at .moc/release-shared/moc_qabstractitemview.cpp:361 #8 QAbstractItemView::mouseReleaseEvent at itemviews/qabstractitemview.cpp:1821 #9 QWidget::event at kernel/qwidget.cpp:8389 -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

2 1

Bug#454: [X2Go-User] Buggy File & Folder sharing
by Mike Gabriel 28 Feb '17

28 Feb '17

Package: x2goclient Tag: build-macosx Severity: important Version: 3.99.2.1 Hi Graham, hi Thierry, [I forward this bug repport to our bug tracker On Do 13 Mär 2014 15:01:42 CET, Graham Stoddart-Stones wrote: > Thierry: > > Just to confirm that we are encountering the same problem with Mac > OSX 3.5.1, X2Goclient 3.99.2.1: > > When you start up X2Goclient on the Mac, you get an error dialog: > > "sshd client not started, you'll need sshd for printing and file > sharing....." > > In OSX, openssh-server is built-in, and is activated by setting > "Enable Remote Login" in System Preferences Sharing, as many others > have noted. However, this does not stop the error dialog from > recurring every time. That leads to another error message "File > cannot be opened". If one ignores this, X2Goclient starts and runs > normally, provided one wishes to neither print locally, nor share > files from the Mac with the remote server. > > I have seen lots of other emails on this topic, suggesting that the > error message does not necessarily apply to the Mac (ie sshd is in > fact running, the error message simply means that the x2goclient > code is looking for a response from a Linux-like file (which does > not occur in the same place in OSX), similarly the "File Cannot be > opened" again refers to a file that is either not used on a Mac, or > is in a wholly different location from where that file is actually > stored on a Mac. I have not seen this point formally answered > anywhere. > > For me, the concern is that, whether sshd is running on the Mac or > not, File Sharing does not appear to be working. I am not > sufficiently familiar with X2Go nor with the Mac to know where to > look on the server for the Mac shared folders, but I do know that > there is nothing under "media", as there is with Linux and a PC, > which is where I normally look. Again, I have searched the bulletins > and forums, and often seen this point raised - I have just not found > the answer on how to get round it. > > So, am keen to see how you get on, and whether anybody else can > please shed any light! Can you cross-check the observed problem with latest X2Go Client [1]??? Can you launch X2Go Client from a terminal on Mac OS X and use a tool like strace (if that exists) and check its output for pointers to file-not-found errors? That would be really helpful for tracking down this issue. Mike [1] http://code.x2go.org/releases/binary-macosx/x2goclient/releases/4.0.1.3/ -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabriel(a)das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.x…

3 2

Bug#236: x2goclient on mac ignores users language setting
by Anders Bruun Olsen 28 Feb '17

28 Feb '17

Package: x2goclient Version: 4.0.1.0 Severity: minor On Mac X2goclient will be shown in the language chosen at the time of installing OS X (system wide). If the user chose danish as the language upon first starting the machine, and then later changes the language to english for his account, x2goclient will still be in danish, despite everything else he starts being in english. -- Anders Bruun Olsen It-ansvarlig Det Danske Sprog- og Litteraturselskab (Society for Danish Language and Literature)

4 3

Bug#234: x2goclient on mac without sshd reports error
by Anders Bruun Olsen 28 Feb '17

28 Feb '17

Package: x2goclient Version: 4.0.1.0 Severity: minor On Macs where sshd (system preferences -> sharing -> remote login) hasn't ever been enabled, there does not exist any ssh host key. X2goclient looks for this key (/etc/ssh_host_rsa_key.pub) and if it does not find it, it opens a dialog box, complaining that sshd isn't running and that filesharing and local printing won't work. This despite the session given by x2gobroker has these features disabled. X2goclient should only complain about none-running/working sshd if it is actually needed. -- Anders Bruun Olsen It-ansvarlig Det Danske Sprog- og Litteraturselskab (Society for Danish Language and Literature)

3 2

Bug#884: nxagent fails to run with "Could not open default font 'fixed'"
by devsk 05 Feb '17

05 Feb '17

Package: nx-libsVersion: 3.5.0.30Distro: Gentoo ~amd64, fully updated.x2goclient: 4.0.3.2x2server: 4.0.1.19nx-libs (package nx in gentoo): 3.5.0.30fontsproto: 2.1.3libXfont: 1.5.1xorg-server: 1.17.1All font packages for xorg-x11 are installed and fonts.dir and fonts.alias files are correctly present and readable.Detailed troubleshooting: https://forums.gentoo.org/viewtopic-p-7755384.html The client connects and the server spawns the nxagent but then the session is unexpectedly terminated. Looking at the server side log, we see: Info: Using shared memory parameters 1/1/0/0K. Info: Using alpha channel in render extension. Info: Not using local device configuration changes. keyboard file created Error: Aborting session with 'Could not open default font 'fixed''. Session: Aborting session at 'Tue May 26 23:22:22 2015'. Session: Session aborted at 'Tue May 26 23:22:22 2015'. I ran the nxagent through strace -ff -tt -v and its clear that it loads all fonts (at least it finds all font.alias and reads them fine) correctly. None of the children it spawns run into any issues with missing files or folders. The snippet below (you can read longer strace on gentoo forum post): 22:11:10.608011 open("/usr/share/fonts/100dpi/fonts.alias", O_RDONLY) = 4 22:11:10.608108 fstat(4, {st_mode=S_IFREG|0644, st_size=3154, ...}) = 0 22:11:10.608217 fstat(4, {st_mode=S_IFREG|0644, st_size=3154, ...}) = 0 22:11:10.608308 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f29ca5a9000 22:11:10.608398 read(4, "lucidasans-bolditalic-8 -b&h-luc"..., 4096) = 3154 22:11:10.608496 brk(0x1f01000) = 0x1f01000 22:11:10.608688 read(4, "", 4096) = 0 22:11:10.608781 close(4) = 0 22:11:10.608868 munmap(0x7f29ca5a9000, 4096) = 0 22:11:10.609148 write(2, "Error: Aborting session with '", 30Error: Aborting session with ') = 30 22:11:10.609277 write(2, "Could not open default font 'fix"..., 35Could not open default font 'fixed') = 35 22:11:10.609395 write(2, "'.\n", 3'. ) = 3 Looking at the code, the origin of the error is: InitFonts(); if (loadableFonts) { SetFontPath(0, 0, (unsigned char *)defaultFontPath, &error); } else { if (SetDefaultFontPath(defaultFontPath) != Success) ErrorF("failed to set default font path '%s'", defaultFontPath); } if (!SetDefaultFont(defaultTextFont)) FatalError("could not open default font '%s'", defaultTextFont); SetDefaultFont() is failing. Looking at that function (text below from IRC channel): [19:57] <devsk> SetDefaultFont(char *defaultfontname)[19:57] <devsk> {[19:57] <devsk> int err;[19:57] <devsk> FontPtr pf;[19:57] <devsk> XID fid;[19:57] <devsk> fid = FakeClientID(0);[19:57] <devsk> err = OpenFont(serverClient, fid, FontLoadAll | FontOpenSync,[19:57] <devsk> (unsigned) strlen(defaultfontname), defaultfontname);[19:57] <devsk> if (err != Success)[19:57] <devsk> return FALSE;[19:57] <devsk> pf = (FontPtr) LookupIDByType(fid, RT_FONT);[19:57] <devsk> if (pf == (FontPtr) NULL)[19:57] <devsk> return FALSE;[19:57] <devsk> defaultFont = pf;[19:57] <devsk> return TRUE;[19:57] <devsk> I have a feeling that LookupIDByType() is the one failing[19:58] <devsk> OpenFont() has error paths for malloc failures and none of those looked like plausible[19:58] <devsk> LookupIDByType() was obsoleted quite a while ago in xorg code[19:59] <devsk> nx-X11 of course is hanging onto old code[19:59] <devsk> is it possible that there is some interaction there with newer libXfont which is making that function fail now[20:00] <devsk> unfortunately for me, its not possible to go back to libXfont-1.4. There is a bunch of crap which needs to be downgraded as well. And dependency hell breaks loose if I try that[20:00] <devsk> above snippet is in ./programs/Xserver/dix/dixfonts.c I did this experiment for localhost connection to avoid differences in client and server packages (which is not the case anyway because for me both client and remote server are Gentoo ~amd64 updated systems). Anybody got any ideas of why this is happening? Is it really about the newer fontsproto and libXfont not being compatible with nx-libs? Thanks,devsk

2 2

Bug#884: nxagent aborts session with 'Could not open default font 'fixed''
by devsk 05 Feb '17

05 Feb '17

Hi, As per suggestion I built the code from https://github.com/ArcticaProject/nx-libs. And I still run into the same issue. Does anybody here know that part of the code (snippet in the report)? -devsk

5 27

← Newer
1
...
6
7
8
9
10
11
12
13
Older →

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

x2go-dev July 2016