I upgraded the x2go server to 4.0.1.18-0~949~ubuntu12.04.1 and X11 on the
client to the Beta release. The connection works now.
It still works if I roll back to X11 2.7.7.
Package: x2goclient
Version: 4.0.2.0
Observed on Commit 5d7d9966198d64ce7846c4f65706f9e9e178e8d7
(Fri, 28 Feb 2014 13:02:50 +0000 (14:02 +0100))
X2Go Client 4.0.2.0 HEAD failed to build from source.
I am using the standard setup which has worked for 4.0.1.3:
mingw32 4.4
QT 4.8.5
X2Go-WinBuilder VM (WIn7 64-bit SP1)
See attached logs. They are what happens when I run the last 2
commands mentioned in this list:
$ cd x2goclient
$ PATH=%PATH%;D:\MinGW\libexec\gcc\mingw32\4.4.0\
$ config_win.bat
$ mingw32-make
>From this page:
http://wiki.x2go.org/doku.php/wiki:development:build-howto-mswin:x2goclient
Note that there are errors in both config_win.bat's output, and in
mingw32-make's output. And they seem to be related to resources.rcc
not finding files.
Hi Alex,
On Mo 03 Mär 2014 11:22:15 CET, Oleksandr Shneyder wrote:
> I'll modify source code so, that build process will check if this files
> are present.
ok.
Mike
--
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…
Package: x2goclient
Version: 4.0.1.1
By some reason, SSH proxy authentications utilizing passphrase-locked
SSH keys let pop up the passphrase dialog.
Session profiles that do not use the SSH proxy settings can happily
authenticate via ssh-agent, also for locked keys.
Mike
--
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…
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.
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.
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…