From troycauble at gmail.com Sat Jun 1 04:42:31 2013 From: troycauble at gmail.com (Troy Cauble) Date: Fri, 31 May 2013 23:42:31 -0400 Subject: [winswitch] xpra client exits Message-ID: I upgraded a Linux server and OSX client to 0.9.4 from something much older and I'm having an issue. The client disappears after a few seconds. Both the client and server logs say "read thread: eof", then the client exits. Logs attached. Thanks, -troy From lists at ebourne.me.uk Tue Jun 4 02:51:32 2013 From: lists at ebourne.me.uk (Martin Ebourne) Date: Tue, 04 Jun 2013 11:21:32 +0930 Subject: [winswitch] xpra coordinate mapping error with dual screen Message-ID: <1370310692.2763.19.camel@kafirin.ebourne.me.uk> I've recently upgraded to xpra 0.9.2 and now 0.9.4 from a much older version. I also switched to using Xdummy in the process. Now I am getting an intermittent and very odd problem with the mouse pointer coordinates. After lots of quite normal operation suddenly the mouse pointer clicks will go wrong on the second (right hand side) screen. Clicking with the mouse will register the click somewhere else on the same screen, the y coordinate will be correct but the x will be much reduced, usually it will register the click near the left hand edge of the screen even if I clicked near the right hand edge. The click may turn up in an entirely different xpra window if they are suitably arranged. Non-xpra windows are not affected and the left hand screen carries on working normally. Dragging a window from the rhs screen to the lhs screen fixes the problem for that window, and putting it back causes it to go wrong again. If the window is split between screens then the part on the lhs works fine and the part on the rhs exhibits the problem. The only remedy I've found is to restart the client which solves it until the next time. This has happened on average maybe once per 20 hours of use so is not common. There are no log messages from either end when this happens. Any ideas? Cheers, Martin From antoine at nagafix.co.uk Tue Jun 4 16:01:08 2013 From: antoine at nagafix.co.uk (Antoine Martin) Date: Tue, 04 Jun 2013 22:01:08 +0700 Subject: [winswitch] xpra coordinate mapping error with dual screen In-Reply-To: <1370310692.2763.19.camel@kafirin.ebourne.me.uk> References: <1370310692.2763.19.camel@kafirin.ebourne.me.uk> Message-ID: <51AE0134.8080305@nagafix.co.uk> On 06/04/2013 08:51 AM, Martin Ebourne wrote: > I've recently upgraded to xpra 0.9.2 and now 0.9.4 from a much older > version. I also switched to using Xdummy in the process. Now I am > getting an intermittent and very odd problem with the mouse pointer > coordinates. > > After lots of quite normal operation suddenly the mouse pointer clicks > will go wrong on the second (right hand side) screen. Clicking with the > mouse will register the click somewhere else on the same screen, the y > coordinate will be correct but the x will be much reduced, usually it > will register the click near the left hand edge of the screen even if I > clicked near the right hand edge. The click may turn up in an entirely > different xpra window if they are suitably arranged. > > Non-xpra windows are not affected and the left hand screen carries on > working normally. Dragging a window from the rhs screen to the lhs > screen fixes the problem for that window, and putting it back causes it > to go wrong again. If the window is split between screens then the part > on the lhs works fine and the part on the rhs exhibits the problem. > > The only remedy I've found is to restart the client which solves it > until the next time. This has happened on average maybe once per 20 > hours of use so is not common. > > There are no log messages from either end when this happens. Any ideas? Please post your server log. It sounds like your vfb is using the wrong dimensions or that the windows are mapped in the wrong place. The first one should show up in the standard server log, for the second one you will need to run the server in debug mode (-d all). This could be related to this bug: http://xpra.org/trac/ticket/349 Antoine > > Cheers, > Martin > > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > http://lists.devloop.org.uk/mailman/listinfo/shifter-users > From lists at ebourne.me.uk Wed Jun 5 02:23:43 2013 From: lists at ebourne.me.uk (Martin Ebourne) Date: Wed, 05 Jun 2013 10:53:43 +0930 Subject: [winswitch] xpra coordinate mapping error with dual screen In-Reply-To: <51AE0134.8080305@nagafix.co.uk> References: <1370310692.2763.19.camel@kafirin.ebourne.me.uk> <51AE0134.8080305@nagafix.co.uk> Message-ID: <1370395423.2763.32.camel@kafirin.ebourne.me.uk> On Tue, 2013-06-04 at 22:01 +0700, Antoine Martin wrote: > Please post your server log. > It sounds like your vfb is using the wrong dimensions or that the > windows are mapped in the wrong place. > The first one should show up in the standard server log, for the second > one you will need to run the server in debug mode (-d all). > > This could be related to this bug: > http://xpra.org/trac/ticket/349 > Yes it happened today exactly when I plugged in the external monitor to my laptop, thus increasing the screen dimensions. Yesterdays probably also coincided with that though it must have taken a while to notice as I didn't associate the events whereas today it was obvious. I'm not sure about the couple of times in previous weeks. As I said before, there is nothing in my log from when I plugged the screen in about resolution changes, but it is correctly negotiated when I reconnect. Here's the excerpt, the problem occurred a couple of minutes before 01:16 when I reconnected, there is nothing in the log at this time. 2013-06-05 00:55:32,114 New connection received: SocketConnection(/home/USERNAME/.xpra/HOSTNAME-101) 2013-06-05 00:55:32,132 Handshake complete; enabling connection 2013-06-05 00:55:32,134 Python/Gtk2 Linux client version 0.9.4 connected from 'CLIENTNAME' 2013-06-05 00:55:32,134 using png as primary encoding 2013-06-05 00:55:32,134 max client resolution is 1920x1080 (from [[1920, 1080]]), current server resolution is 4800x1200 2013-06-05 00:55:32,152 new resolution matching 1920x1080 : screen now set to 1920x1080 2013-06-05 00:55:32,156 setting key repeat rate from client: 500ms delay / 30ms interval 2013-06-05 00:55:32,162 setting keymap: rules=evdev, model=evdev, layout=us,us 2013-06-05 00:55:32,498 setting full keymap definition from client via xkbcomp 2013-06-05 00:55:32,784 sending updated screen size to clients: 1920x1080 (max 5120x3200) 2013-06-05 00:55:32,895 using sound codec opus 2013-06-05 00:55:33,173 starting sound using pulseaudio device null.monitor 2013-06-05 00:55:33,245 unknown tag message: 2013-06-05 00:55:33,246 pipeline warning: Internal data flow problem. 2013-06-05 00:55:33,246 pipeline warning: ['gstbasesink.c(3638): gst_base_sink_chain_unlocked (): /GstPipeline:pipeline8/GstAppSink:sink:\nReceived buffer without a new-segment. Assuming timestamps start from 0.'] 2013-06-05 01:16:49,395 read connection reset for SocketConnection(/home/USERNAME/.xpra/HOSTNAME-101) 2013-06-05 01:16:49,447 connection lost: read connection reset: [Errno 104] Connection reset by peer 2013-06-05 01:16:49,448 connection closed after 34968 packets received (1049376 bytes) and 78932 packets sent (249723961 bytes) 2013-06-05 01:16:49,449 Connection lost 2013-06-05 01:16:49,455 xpra client disconnected. 2013-06-05 01:16:57,592 New connection received: SocketConnection(/home/USERNAME/.xpra/HOSTNAME-101) 2013-06-05 01:16:57,617 Handshake complete; enabling connection 2013-06-05 01:16:57,763 Python/Gtk2 Linux client version 0.9.4 connected from 'CLIENTNAME' 2013-06-05 01:16:57,763 using png as primary encoding 2013-06-05 01:16:57,763 max client resolution is 3840x1080 (from [[3840, 1080]]), current server resolution is 1920x1080 2013-06-05 01:16:57,948 new resolution matching 3840x1080 : screen now set to 4800x1200 Cheers, Martin From antoine at nagafix.co.uk Wed Jun 5 05:35:52 2013 From: antoine at nagafix.co.uk (Antoine Martin) Date: Wed, 05 Jun 2013 11:35:52 +0700 Subject: [winswitch] xpra coordinate mapping error with dual screen In-Reply-To: <1370395423.2763.32.camel@kafirin.ebourne.me.uk> References: <1370310692.2763.19.camel@kafirin.ebourne.me.uk> <51AE0134.8080305@nagafix.co.uk> <1370395423.2763.32.camel@kafirin.ebourne.me.uk> Message-ID: <51AEC028.3040207@nagafix.co.uk> On 06/05/2013 08:23 AM, Martin Ebourne wrote: > On Tue, 2013-06-04 at 22:01 +0700, Antoine Martin wrote: >> Please post your server log. >> It sounds like your vfb is using the wrong dimensions or that the >> windows are mapped in the wrong place. >> The first one should show up in the standard server log, for the second >> one you will need to run the server in debug mode (-d all). >> >> This could be related to this bug: >> http://xpra.org/trac/ticket/349 >> > > Yes it happened today exactly when I plugged in the external monitor to > my laptop, thus increasing the screen dimensions. Yesterdays probably > also coincided with that though it must have taken a while to notice as > I didn't associate the events whereas today it was obvious. I'm not sure > about the couple of times in previous weeks. > > As I said before, there is nothing in my log from when I plugged the > screen in about resolution changes, but it is correctly negotiated when > I reconnect. Can you please try this change: http://xpra.org/trac/changeset/3581/xpra from: http://xpra.org/trac/ticket/349#comment:2 If that fixes it I will backport to v0.9.x Thanks Antoine > > Here's the excerpt, the problem occurred a couple of minutes before > 01:16 when I reconnected, there is nothing in the log at this time. > > 2013-06-05 00:55:32,114 New connection received: SocketConnection(/home/USERNAME/.xpra/HOSTNAME-101) > 2013-06-05 00:55:32,132 Handshake complete; enabling connection > 2013-06-05 00:55:32,134 Python/Gtk2 Linux client version 0.9.4 connected from 'CLIENTNAME' > 2013-06-05 00:55:32,134 using png as primary encoding > 2013-06-05 00:55:32,134 max client resolution is 1920x1080 (from [[1920, 1080]]), current server resolution is 4800x1200 > 2013-06-05 00:55:32,152 new resolution matching 1920x1080 : screen now set to 1920x1080 > 2013-06-05 00:55:32,156 setting key repeat rate from client: 500ms delay / 30ms interval > 2013-06-05 00:55:32,162 setting keymap: rules=evdev, model=evdev, layout=us,us > 2013-06-05 00:55:32,498 setting full keymap definition from client via xkbcomp > 2013-06-05 00:55:32,784 sending updated screen size to clients: 1920x1080 (max 5120x3200) > 2013-06-05 00:55:32,895 using sound codec opus > 2013-06-05 00:55:33,173 starting sound using pulseaudio device null.monitor > 2013-06-05 00:55:33,245 unknown tag message: > 2013-06-05 00:55:33,246 pipeline warning: Internal data flow problem. > 2013-06-05 00:55:33,246 pipeline warning: ['gstbasesink.c(3638): gst_base_sink_chain_unlocked (): /GstPipeline:pipeline8/GstAppSink:sink:\nReceived buffer without a new-segment. Assuming timestamps start from 0.'] > 2013-06-05 01:16:49,395 read connection reset for SocketConnection(/home/USERNAME/.xpra/HOSTNAME-101) > 2013-06-05 01:16:49,447 connection lost: read connection reset: [Errno 104] Connection reset by peer > 2013-06-05 01:16:49,448 connection closed after 34968 packets received (1049376 bytes) and 78932 packets sent (249723961 bytes) > 2013-06-05 01:16:49,449 Connection lost > 2013-06-05 01:16:49,455 xpra client disconnected. > 2013-06-05 01:16:57,592 New connection received: SocketConnection(/home/USERNAME/.xpra/HOSTNAME-101) > 2013-06-05 01:16:57,617 Handshake complete; enabling connection > 2013-06-05 01:16:57,763 Python/Gtk2 Linux client version 0.9.4 connected from 'CLIENTNAME' > 2013-06-05 01:16:57,763 using png as primary encoding > 2013-06-05 01:16:57,763 max client resolution is 3840x1080 (from [[3840, 1080]]), current server resolution is 1920x1080 > 2013-06-05 01:16:57,948 new resolution matching 3840x1080 : screen now set to 4800x1200 > > Cheers, > Martin > > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > http://lists.devloop.org.uk/mailman/listinfo/shifter-users > From lists at ebourne.me.uk Wed Jun 5 14:57:30 2013 From: lists at ebourne.me.uk (Martin Ebourne) Date: Wed, 05 Jun 2013 23:27:30 +0930 Subject: [winswitch] xpra coordinate mapping error with dual screen In-Reply-To: <51AEC028.3040207@nagafix.co.uk> References: <1370310692.2763.19.camel@kafirin.ebourne.me.uk> <51AE0134.8080305@nagafix.co.uk> <1370395423.2763.32.camel@kafirin.ebourne.me.uk> <51AEC028.3040207@nagafix.co.uk> Message-ID: <1370440650.2763.38.camel@kafirin.ebourne.me.uk> On Wed, 2013-06-05 at 11:35 +0700, Antoine Martin wrote: > Can you please try this change: > http://xpra.org/trac/changeset/3581/xpra > from: > http://xpra.org/trac/ticket/349#comment:2 > > If that fixes it I will backport to v0.9.x Unfortunately no it didn't. Instead I got this from the client: ** Message: pygobject_register_sinkfunc is deprecated (GstObject) xpra client version 0.9.4 2013-06-05 23:24:53,374 Attached to ssh:SERVERHOST:101 (press Control-C to detach) 2013-06-05 23:24:54,692 unknown tag message: Traceback (most recent call last): File "/usr/lib64/python2.7/site-packages/xpra/client.py", line 1118, in _screen_size_changed self.idle_add(update_size) AttributeError: 'XpraClient' object has no attribute 'idle_add' Cheers, martin From antoine at nagafix.co.uk Wed Jun 5 16:06:10 2013 From: antoine at nagafix.co.uk (Antoine Martin) Date: Wed, 05 Jun 2013 22:06:10 +0700 Subject: [winswitch] xpra coordinate mapping error with dual screen In-Reply-To: <1370440650.2763.38.camel@kafirin.ebourne.me.uk> References: <1370310692.2763.19.camel@kafirin.ebourne.me.uk> <51AE0134.8080305@nagafix.co.uk> <1370395423.2763.32.camel@kafirin.ebourne.me.uk> <51AEC028.3040207@nagafix.co.uk> <1370440650.2763.38.camel@kafirin.ebourne.me.uk> Message-ID: <51AF53E2.4070708@nagafix.co.uk> On 06/05/2013 08:57 PM, Martin Ebourne wrote: > On Wed, 2013-06-05 at 11:35 +0700, Antoine Martin wrote: >> Can you please try this change: >> http://xpra.org/trac/changeset/3581/xpra >> from: >> http://xpra.org/trac/ticket/349#comment:2 >> >> If that fixes it I will backport to v0.9.x > > Unfortunately no it didn't. Instead I got this from the client: > > ** Message: pygobject_register_sinkfunc is deprecated (GstObject) > xpra client version 0.9.4 > 2013-06-05 23:24:53,374 Attached to ssh:SERVERHOST:101 (press Control-C to detach) > > 2013-06-05 23:24:54,692 unknown tag message: > Traceback (most recent call last): > File "/usr/lib64/python2.7/site-packages/xpra/client.py", line 1118, in _screen_size_changed > self.idle_add(update_size) > AttributeError: 'XpraClient' object has no attribute 'idle_add' Sorry about that, in 0.9.x we are still tied to pygobject, so the backport will look more like: gobject.idle_add(update_size) Antoine > > > Cheers, > martin > > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > http://lists.devloop.org.uk/mailman/listinfo/shifter-users > From antoine at nagafix.co.uk Thu Jun 6 10:45:20 2013 From: antoine at nagafix.co.uk (Antoine Martin) Date: Thu, 06 Jun 2013 16:45:20 +0700 Subject: [winswitch] [ANNOUNCE] xpra 0.9.5 (minor bug fixes) Message-ID: <51B05A30.7030505@nagafix.co.uk> Hi, This small update fixes some minor bugs * fix auto-refresh: don't refresh unnecessarily * fix wrong initial timeout when ssh takes a long time to connect * fix client monitor/resolution size change detection * fix attributes reported to clients when encoding overrides are used * Gentoo ebuild uses virtual to allow one to choose pillow or PIL The source: https://xpra.org/src/ Binaries/repositories: https://winswitch.org/downloads/ Direct binary downloads: https://xpra.org/dists/ Cheers Antoine From antoine at nagafix.co.uk Thu Jun 6 12:40:01 2013 From: antoine at nagafix.co.uk (Antoine Martin) Date: Thu, 06 Jun 2013 18:40:01 +0700 Subject: [winswitch] WinSwitch Development Question In-Reply-To: References: Message-ID: <51B07511.30107@nagafix.co.uk> Hi Mark, On 06/06/2013 12:54 AM, mark doyle wrote: > Antoine, > > I'm not writing this to address a bug issue, which seems to be the main > point of the mailing list. No, just a sign of my sloppy coding ;) > But, I have a fairly basic question about > modifying the UI of WinSwitch, but as I have just picked up Python and > gtk in the past week, my working knowledge of the source code is > somewhat limited. Essentially, what I am trying to do is modify the UI > so that dragging an open application session window to the edge of the > screen will send that application to another user. I feel like this > would add a pretty neat feature, and avoids the hassle of going through > drop down menus, clicking send, etc. Of course this approach is limited, > but I'm only trying to get it to work on just using 1 server, and 2 > users, to send the application back and forth. We had already discussed a similar thing with synergy a while back (when the software was called 'shifter'): https://groups.google.com/forum/#!msg/synergy-plus/a6dfWLf9xZU/ZEqkIqcPUwcJ See also: https://code.google.com/p/synergy-plus/issues/detail?id=588 This may help in providing a better way of detecting movements to/past the edge of the screen. > Attached is an added class I made that so far detects the running > application window and minimizes it when placed on the right-most 10% of > the screen. (a proof of concept design choice). I am now trying to add > the functionality of sending the application to another machine, but > even after spending a tremendous amount time looking through the classes > and trying a couple of things, I am still not sure what I need to import > to get access to the sending functions/server/session variables of the > winswitch application instance. Sorry about that. Winswitch was one of my first ever project in python, the coding style isn't great and MVC sometimes hides the flow behind indirection layers. > What seems to be a suitable solution would be if I could simulate a > button press on the send button in the session information popup. (also > attached): > > Any additional guidance or information on the problem would be greatly > appreciated if you have the time! What you want is just to send the "SEND_SESSION" message to the server, which will fire: send_session_to_user. To write a simple client, you may want to look at "client_cli.py" You will need to know the UUID of the user you send the application to. Let me know if you need more info, this shouldn't be too hard to get going. Cheers Antoine > > Thanks, > Mark > From lists at ebourne.me.uk Thu Jun 6 13:25:55 2013 From: lists at ebourne.me.uk (Martin Ebourne) Date: Thu, 06 Jun 2013 21:55:55 +0930 Subject: [winswitch] xpra coordinate mapping error with dual screen In-Reply-To: <51AF53E2.4070708@nagafix.co.uk> References: <1370310692.2763.19.camel@kafirin.ebourne.me.uk> <51AE0134.8080305@nagafix.co.uk> <1370395423.2763.32.camel@kafirin.ebourne.me.uk> <51AEC028.3040207@nagafix.co.uk> <1370440650.2763.38.camel@kafirin.ebourne.me.uk> <51AF53E2.4070708@nagafix.co.uk> Message-ID: <1370521555.17291.0.camel@kafirin.ebourne.me.uk> On Wed, 2013-06-05 at 22:06 +0700, Antoine Martin wrote: > On 06/05/2013 08:57 PM, Martin Ebourne wrote: > > Unfortunately no it didn't. Instead I got this from the client: > > > > ** Message: pygobject_register_sinkfunc is deprecated (GstObject) > > xpra client version 0.9.4 > > 2013-06-05 23:24:53,374 Attached to ssh:SERVERHOST:101 (press Control-C to detach) > > > > 2013-06-05 23:24:54,692 unknown tag message: > > Traceback (most recent call last): > > File "/usr/lib64/python2.7/site-packages/xpra/client.py", line 1118, in _screen_size_changed > > self.idle_add(update_size) > > AttributeError: 'XpraClient' object has no attribute 'idle_add' > > Sorry about that, in 0.9.x we are still tied to pygobject, so the > backport will look more like: > gobject.idle_add(update_size) I can confirm that 0.9.5 fixes this for me, thanks. Cheers, Martin From antoine at nagafix.co.uk Sun Jun 30 12:31:48 2013 From: antoine at nagafix.co.uk (Antoine Martin) Date: Sun, 30 Jun 2013 18:31:48 +0700 Subject: [winswitch] [ANNOUNCE] xpra 0.9.5 (many bug fixes) Message-ID: <51D01724.6080704@nagafix.co.uk> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, This update fixes a number of fairly minor bugs: * fix client exit lockups on MS Windows * fix lost clicks on some popup menus (mostly with MS Windows clients) * fix client workarea size change detection * fix reading of unique "machine-id" on posix * fix window reference leak for windows we fail to manage * fix compatibility with pillow (PIL fork) * fix session-info window graphs jumping (smoother motion) * fix webp loading code for non-Linux posix systems * fix window group-leader attribute setting * fix man page indentation * fix variable test vs use (correctness only) * static binary builds updates: Python 2.7.5, flac 1.3, PyOpenGL 3.1, numpy 1.7.1, webp 0.3.1, libav 9.7 * static binary builds switched to using pillow instead of PIL * forward compatibility with future "xpra info" namespace changes The source: https://xpra.org/src/ Binaries/repositories: https://winswitch.org/downloads/ Direct binary downloads: https://xpra.org/dists/ Cheers Antoine -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlHQFx8ACgkQGK2zHPGK1rs0fQCfeJTzW7S331L/46BF7haV/nHC COYAniO/mKvKP3HE0ziNV52NJOe0ztCy =Fnzy -----END PGP SIGNATURE----- From antoine at nagafix.co.uk Sun Jun 30 12:32:03 2013 From: antoine at nagafix.co.uk (Antoine Martin) Date: Sun, 30 Jun 2013 18:32:03 +0700 Subject: [winswitch] [ANNOUNCE] winswitch 0.12.19 Message-ID: <51D01733.8050000@nagafix.co.uk> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Version 0.12.19 is available now: http://winswitch.org/downloads/ This minor update fixes some minor bugs and brings better compatibility with the latest xpra releases and features. The binary builds (MS Windows and OSX) finally get an up to date Xpra. Cheers Antoine Full release notes: * binary builds library updates all around * binary builds include latest Xpra 0.9.6 * fix local display session detection with python-utmp * fix local display detection when running server separately from applet * fix error handling for VirtualBox session detection -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlHQFzMACgkQGK2zHPGK1rtKlgCdFwEzoyf3iEn0oTm9V0ZDKwws zdIAnjKaCwsuYII947zkvN9SkhnBHcsx =QQKy -----END PGP SIGNATURE----- From thejunk.b at gmail.com Sun Jun 30 18:09:32 2013 From: thejunk.b at gmail.com (Randy) Date: Sun, 30 Jun 2013 13:09:32 -0400 Subject: [winswitch] vbox sessions not available Message-ID: <201306301309.32902.thejunk.b@gmail.com> It seams that the latest update disabled access to the VirtualBox VM's. I have looked and the box is checked in the server config. All my machines run Debian Testing (Jessie) fully patched. -- If it ain't broke tweek it From thejunk.b at gmail.com Sun Jun 30 20:53:35 2013 From: thejunk.b at gmail.com (Randy) Date: Sun, 30 Jun 2013 15:53:35 -0400 Subject: [winswitch] vbox sessions not available In-Reply-To: <201306301309.32902.thejunk.b@gmail.com> References: <201306301309.32902.thejunk.b@gmail.com> Message-ID: <201306301553.35450.thejunk.b@gmail.com> On Sunday, June 30, 2013, you wrote: > It seams that the latest update disabled access to the VirtualBox VM's. I > have looked and the box is checked in the server config. All my machines > run Debian Testing (Jessie) fully patched. To follow up is seams that the proccess is being started with the --no-virtualbox option on all the machines that it is running on. I don't recall that I ever edited the config files by hand. -- If it ain't broke tweek it From onlyjob at member.fsf.org Sun Jun 30 21:10:07 2013 From: onlyjob at member.fsf.org (Dmitry Smirnov) Date: Mon, 1 Jul 2013 06:10:07 +1000 Subject: [winswitch] vbox sessions not available In-Reply-To: <201306301553.35450.thejunk.b@gmail.com> References: <201306301309.32902.thejunk.b@gmail.com> <201306301553.35450.thejunk.b@gmail.com> Message-ID: <201307010610.07797.onlyjob@member.fsf.org> On Mon, 1 Jul 2013 05:53:35 Randy wrote: > To follow up is seams that the proccess is being started with the > --no-virtualbox option on all the machines that it is running on. I don't > recall that I ever edited the config files by hand. Randy, you probably use Debian package where "--no-virtualbox" given in .desktop file. You won't have this problem if you run winswitch from command line. Read more about this in the following ticket: https://winswitch.org/trac/ticket/212 Regards, Dmitry Smirnov GPG key : 4096R/53968D1B --- A wise man proportions his belief to the evidence. -- David Hume, "An Inquiry Concerning Human Understanding" From thejunk.b at gmail.com Sun Jun 30 21:33:32 2013 From: thejunk.b at gmail.com (Randy) Date: Sun, 30 Jun 2013 16:33:32 -0400 Subject: [winswitch] vbox sessions not available In-Reply-To: <201307010610.07797.onlyjob@member.fsf.org> References: <201306301309.32902.thejunk.b@gmail.com> <201306301553.35450.thejunk.b@gmail.com> <201307010610.07797.onlyjob@member.fsf.org> Message-ID: <201306301633.32175.thejunk.b@gmail.com> On Sunday, June 30, 2013, Dmitry Smirnov wrote: > On Mon, 1 Jul 2013 05:53:35 Randy wrote: > > To follow up is seams that the proccess is being started with the > > --no-virtualbox option on all the machines that it is running on. I > > don't recall that I ever edited the config files by hand. > > Randy, you probably use Debian package where "--no-virtualbox" given > in .desktop file. You won't have this problem if you run winswitch > from command line. Read more about this in the following ticket: > > https://winswitch.org/trac/ticket/212 > > Regards, > Dmitry Smirnov > GPG key : 4096R/53968D1B Thanks Dmitry, I found just that in my .destop file and removed it and that fixed it. Thanks again. -- If it ain't broke tweek it