Custom Query (230 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (154 - 156 of 230)

Ticket Resolution Summary Owner Reporter
#290 fixed CentOS 6.8 package directory is missing "winswitch" package (maybe others) badpens
Description

The http://winswitch.org/dists/CentOS/6.8/x86_64/ directory is missing the "winswitch-0.12....." package.

The http://winswitch.org/dists/CentOS/6.7/x86_64/ directory does have packages like winswitch-0.12.22-1.x86_64.rpm

Do I need to hardcode my /etc/yum.repos.d/winswitch.repo to use 6.7 instead of $releasever ?

#291 fixed When attempting to start an application on Fedora 24 using WindowSwitch 0.12.21 you are informed that xpra is not supported. jayce1996 jayce1996
Description

If you try to start an application on a Fedora 24 server using WindowSwitch? 0.12.21, you get the following error dialog:

You have requested an xpra session but this server does not support it.

Attempting to start an xpra session directly using: xpra start ssh:localhost:100 --start-child=xchat

actually produces an application.

xpra is installed in the same location that winswitch thinks it is.

#296 fixed Xpra version mismatch error thinksilicon
Description

Hi, I've checked out latest release of winswitch (0.12.20) and compiled on my openSUSE 42.2. Works fine so far, except I get an error-message on start-up:

"Xpra version mismatch,xpra version on the server is 2.0.1-r15494, your version is 2.0.1-r15494. Xpra support has been disabled"

As you can see, this message doesn't really make sense, as it's the exact same version of xpra. I took a look into the xpra_version_compat(self, v1, v2) function and if I'm not taken wrong it looks like, the function has a problem with the git-release-number in my xpra-verion. Would you be able to provide a patch, so xpra_version_compat() is more resilient against those version-numbers?

Thank you and keep up the good work!

Note: See TracQuery for help on using queries.