Processing commands for control(a)bugs.x2go.org:
> reopen #742
Bug #742 {Done: Michael DePaulo <mikedep333(a)gmail.com>} [x2goclient] Executing parec seems unnecessary now that X2Go Client for Windows 4.0.3.0 uses PulseAudio 5.0
'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.0.3.2.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
742: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=742
X2Go Bug Tracking System
Contact owner(a)bugs.x2go.org with problems
Processing commands for control(a)bugs.x2go.org:
> fixed #742 4.0.3.2
Bug #742 {Done: Michael DePaulo <mikedep333(a)gmail.com>} [x2goclient] Executing parec seems unnecessary now that X2Go Client for Windows 4.0.3.0 uses PulseAudio 5.0
There is no source info for the package 'x2goclient' at version '4.0.3.2' with architecture ''
Unable to make a source version for version '4.0.3.2'
Ignoring request to alter fixed versions of bug #742 to the same values previously set
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
742: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=742
X2Go Bug Tracking System
Contact owner(a)bugs.x2go.org with problems
Processing commands for control(a)bugs.x2go.org:
> tag #742 pending
Bug #742 {Done: Michael DePaulo <mikedep333(a)gmail.com>} [x2goclient] Executing parec seems unnecessary now that X2Go Client for Windows 4.0.3.0 uses PulseAudio 5.0
Added tag(s) pending.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
742: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=742
X2Go Bug Tracking System
Contact owner(a)bugs.x2go.org with problems
Package: x2goclient
Version: 4.0.3.0
When trying to figure out why I get
'Object::connect: No such slot ONMainWindow::slotSndTunOk(int)'
in the debugging output of X2Go Client for Windows 4.0.3.0,
I bumped onto a common error:
Argument mismatch between function call and function definition.
That prevents slotSndTunOk() from ever executing.
slotStartParec() depends on slotSndTunOk() to execute parec.
Executing parec was needed due to a PulseAudio's bug as explained in
http://x2go-dev.x2go.narkive.com/wNgRoxTO/parec
One peculiar thing is that after fixing that mismatch,
which enabled parec to execute,
x2goclient became extremely sluggish.
The only way to revert things back to normal
was to prevent parec from ever executing.
It seems that parec in not needed now that X2Go Client uses PulseAudio 5.0.
The attached patch saves x2goclient from calling slotStartParec()
once per second unnecessarily.
Dept. of Applied Informatics, University of Macedonia
George Trakatelis
tag #646 pending
fixed #646 0.5.0.4
thanks
Hello,
X2Go issue #646 (src:pyhoca-gui) reported by you has been
fixed in X2Go Git. You can see the changelog below, and you can
check the diff of the fix at:
http://code.x2go.org/gitweb?p=pyhoca-gui.git;a=commitdiff;h=06284de
The issue will most likely be fixed in src:pyhoca-gui (0.5.0.4).
light+love
X2Go Git Admin (on behalf of the sender of this mail)
---
commit 06284de76076ac1cd27b7a979ca7087498e41f40
Author: Mike DePaulo <mikedep333(a)gmail.com>
Date: Sat Jan 24 15:03:49 2015 -0500
Update changelog about Python (lib) updates
diff --git a/debian/changelog b/debian/changelog
index 3b15a2e..6decc15 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -27,6 +27,9 @@ pyhoca-gui (0.5.0.4-0x2go1) UNRELEASED; urgency=medium
- Windows: Update nxproxy's Cygwin libraries from the
latest versions as of 2014-06-09 to the
latest versions as of 2014-10-18.
+ - Windows: Update python from 2.7.8 to 2.7.9
+ - Windows: Update bundled Python libraries to latest versions
+ as of 2015-01-24 (Fixes: #646)
-- Mike Gabriel <mike.gabriel(a)das-netzwerkteam.de> Thu, 27 Nov 2014 12:34:20 +0100
Package: nx-libs
Version: 3.5.0.28
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x0000000000493916 in nxagentDisconnectPicture (p0=0x19b1250,
x1=48234557, p2=p2@entry=0x7fff92ebd2d4) at Render.c:2798
2798 nxagentPicture(pPicture) = None;
Thread 1 (Thread 0x7fc5d4482740 (LWP 2701)):
#0 0x0000000000493916 in nxagentDisconnectPicture (p0=0x19b1250,
x1=48234557, p2=p2@entry=0x7fff92ebd2d4) at Render.c:2798
x1 = 48234557
p2 = 0x7fff92ebd2d4
p0 = 0x19b1250
pPicture = 0x19b1250
pBool = 0x7fff92ebd2d4
Looks like we may need a check if nxagentPicture(pPicture) is null.
-------- Forwarded Message --------
Subject: [Bug 1185552] New: [abrt] nxagent: nxagentDisconnectPicture():
nxagent killed by SIGSEGV
Date: Sat, 24 Jan 2015 15:53:03 +0000
From: bugzilla(a)redhat.com
To: orion(a)cora.nwra.com
https://bugzilla.redhat.com/show_bug.cgi?id=1185552
Bug ID: 1185552
Summary: [abrt] nxagent: nxagentDisconnectPicture(): nxagent
killed by SIGSEGV
Product: Fedora
Version: 21
Component: nx-libs
Assignee: orion(a)cora.nwra.com
Reporter: carlos.em.esteves(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: orion(a)cora.nwra.com
Description of problem:
MacOSX 10.10 - Maximize Client X2GO...
Version-Release number of selected component:
nxagent-3.5.0.28-1.fc21
Additional info:
reporter: libreport-2.3.0
backtrace_rating: 4
cmdline: /usr/lib64/nx/../x2go/bin/x2goagent -extension XFIXES
-nolisten
tcp -nolisten tcp -dpi 72 -D -auth /home/cesteves/.Xauthority -geometry
800x600
-name X2GO-cesteves-50-1422109911_stDXFCE_dp32 :50
crash_function: nxagentDisconnectPicture
executable: /usr/lib64/nx/bin/nxagent
kernel: 3.17.8-300.fc21.x86_64
runlevel: N 5
type: CCpp
uid: 1000
Truncated backtrace:
Thread no. 1 (9 frames)
#0 nxagentDisconnectPicture at Render.c:2798
#1 FindClientResourcesByType at X/NXresource.c:835
#2 nxagentDisconnectAllPicture at Render.c:2814
#3 nxagentDisconnectSession at Reconnect.c:383
#4 nxagentHandleConnectionStates at Reconnect.c:218
#5 nxagentWakeupHandler at Handlers.c:589
#6 WakeupHandler at dixutils.c:472
#7 WaitForSomething at WaitFor.c:389
#8 Dispatch at X/NXdispatch.c:619
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
close #649
thanks
Hello,
we are very hopeful that X2Go issue #649 reported by you
has been resolved in the new release (0.5.0.3) of the
X2Go source project »src:pyhoca-gui«.
You can view the complete changelog entry of src:pyhoca-gui (0.5.0.3)
below, and you can use the following link to view all the code changes
between this and the last release of src:pyhoca-gui.
http://code.x2go.org/gitweb?p=pyhoca-gui.git;a=commitdiff;h=03b4e45f1288d21…
If you feel that the issue has not been resolved satisfyingly, feel
free to reopen this bug report or submit a follow-up report with
further observations described based on the new released version
of src:pyhoca-gui.
Thanks a lot for contributing to X2Go!!!
light+love
X2Go Git Admin (on behalf of the sender of this mail)
---
X2Go Component: src:pyhoca-gui
Version: 0.5.0.3-20150124
Status: RELEASE
Date: Sat, 24 Jan 2015 11:03:07 -0500
Fixes: 108 649
Changes:
pyhoca-gui (0.5.0.3-20150124) RELEASED; urgency=medium
.
[ Mike DePaulo ]
* New upstream version (Windows Only) (0.5.0.3-20150124):
- Fix win32 build (missing win32gui.pyd) (Fixes: #649)
- Windows: Install VcXsrv "misc" fonts by default, and make all 4 font
groups optional: misc, 75dpi, 100dpi and others (Fixes: #108)
Note: The fact that all the fonts are included makes the installer about
30MB larger.
- Windows: Upgrade from VcXsrv-xp 1.14.3.2 to
VcXsrv 1.15.2.2-xp+vc2013+x2go1
This new major version includes security fixes such as:
OpenSSL update to 1.0.1k
xorg-server CVE-2014-8091..8103 fixes
- Windows: Update nxproxy's Cygwin libraries from the
latest versions as of 2014-06-09 to the
latest versions as of 2014-10-18.
tag #649 pending
fixed #649 0.5.0.4
thanks
Hello,
X2Go issue #649 (src:pyhoca-gui) reported by you has been
fixed in X2Go Git. You can see the changelog below, and you can
check the diff of the fix at:
http://code.x2go.org/gitweb?p=pyhoca-gui.git;a=commitdiff;h=d02f989
The issue will most likely be fixed in src:pyhoca-gui (0.5.0.4).
light+love
X2Go Git Admin (on behalf of the sender of this mail)
---
commit d02f98964b825b426022c3b82f5bdde9053138b0
Author: Mike DePaulo <mikedep333(a)gmail.com>
Date: Sat Jan 24 01:03:52 2015 -0500
Fix win32 build (Fixes: #649)
Conflicts:
debian/changelog
diff --git a/debian/changelog b/debian/changelog
index 4827fa1..fb3b4f5 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -12,6 +12,10 @@ pyhoca-gui (0.5.0.4-0x2go1) UNRELEASED; urgency=medium
* New upstream version (0.5.0.4):
- Add Turkish translation to PyHoca-GUI.
+ [ Mike DePaulo ]
+ * New upstream version (0.5.0.4):
+ - Fix win32 build (missing win32gui.pyd) (Fixes: #649)
+
-- Mike Gabriel <mike.gabriel(a)das-netzwerkteam.de> Thu, 27 Nov 2014 12:34:20 +0100
pyhoca-gui (0.5.0.3-0x2go1) unstable; urgency=medium
Package: x2goclient
Version: 4.0.3.1
Hello x2go dev team,
I have Ubuntu 14.04.1 LTS on a client machine and use ALT+SHIFT to
switch the keyboard layout.
As a client a use X2Go Client V. 4.0.3.1 - the latest thing available
from your repository at the moment.
On a remote machine I have Debian Wheezy with KDE 4.8.4 and the latest
x2go server from http://packages.x2go.org/debian. So should be
4.0.1.18-0x2go1+git20141006.949+wheezy.main.1
The problem is that if in KDE Keyboard settings in "Layouts" as a main
shortcut for switching layout i'll select the same layout I use locally
(ALT+SHIFT in my case) it will not work properly.
If you work on a remote machine and hit ALT+SHIFT - layout only switches
on a local machine. If you hit ALT+SHIFT multiple times quite fast
sometimes layout on a remote machine switches too. Sometimes not.
I tried to set different keyboard settings in the session settings -
does not help. If I set something other than the 'do not configure'
after connecting to the remote instead of 2 layouts I have a third one -
undef. Which will disappear if I just go to keyboard settings and apply
the same settings i had. Maybe that resets some settings which x2go does
after connection is established. But that 'undef' thing is not what
bothers me.
Problem with the layout switching has appeared long ago- since the
Ubuntu 13. As I remeber 12 was the latest one which worked normally.
After the upgrade from 12 to 13 even locally ALT+SHIFT combo didn't
work. That was a really big problem and that has a confirmed bug
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1218322.
There are some other related bugs, I can try to find them if needed.
It is partially fixed - at least ALT+SHIFT now works locally but since
that time I have a problem witch x2go as I described earlier.
I tried to use CAPS Lock on both machines - same problem. As I remember
I tried installing MATE instead of KDE - didn't help.
I believe that problem is in Ubuntu - in how it now intercepts keyboard
shortcuts. Through the 12->13 transition they changed something.
Please take a look at the problem. Currently I have different shortcuts
on remote a local machine. It's quite uncofortable.