From antoine at nagafix.co.uk Sun Feb 6 16:57:49 2011 From: antoine at nagafix.co.uk (Antoine Martin) Date: Sun, 06 Feb 2011 23:57:49 +0700 Subject: [shifter-users] 100% CPU bug on *nix - [SOLVED], sort of... In-Reply-To: <4D46871D.1030602@nagafix.co.uk> References: <4D46871D.1030602@nagafix.co.uk> Message-ID: <4D4ED30D.2020202@nagafix.co.uk> A quick status update on this particularly annoying issue: * Windows is not affected (does not use *nix poll code) * OSX images have been rebuilt with the pygtk patch: http://winswitch.org/dists/osx/ * Debian was unaffected (has a patch for pygth 2.17) * Gentoo has pushed a fix to testing (2.22 will be marked stable soon). * Fedora seems to ignore the bug so I have built fixed pygtk RPMs (using the Debian patch for 2.17/F13, upstream patch for F14/F15): http://winswitch.org/dists/rpm/Fedora/ * Ubuntu seems to ignore the bug too, so I have built fixed DEBs (*). http://winswitch.org/dists/ I have not checked the status of the other distros yet. As you can see, the response time varies greatly... One would think that the constant stream of package updates for both ubuntu and fedora does include stuff less important than a trivial local DoS bug... Cheers Antoine (*) Ubuntu note: Since this is a system package, I have not added it to the winswitch repository file, you will have to download the updated package yourself. Point and click from the browser should work. On 01/31/2011 04:55 PM, Antoine Martin wrote: > Hi all, > > Many of you have been reporting the "processes use 100% cpu" bug > recently, which has a bug entry here: > http://winswitch.org/trac/ticket/90 > I believe newer Linux distros have started shipping libraries > which make it unavoidable to trigger this bug. > > Now, the good news is the bug has been found thanks to exarkun: > http://twistedmatrix.com/trac/ticket/4658#comment:16 > The bad news is that it is a PyGTK bug I can do nothing about: > https://bugzilla.gnome.org/show_bug.cgi?id=640738 > > So if you get high cpu usage, bug your distro and/or PyGTK to release > the fix which has been provided. > > Cheers > Antoine From antoine at devloop.org.uk Tue Feb 15 07:36:23 2011 From: antoine at devloop.org.uk (Antoine Martin) Date: Tue, 15 Feb 2011 14:36:23 +0700 Subject: [shifter-users] Window Switch problem In-Reply-To: References: Message-ID: <4D5A2CF7.8080608@devloop.org.uk> Can you login via ssh as that user? Multicast is tricky but you are right: if it has connected before, it should be ok. Try running avahi-discover to browse the services it advertises. The quick-connect window does use ssh if you select it, which should not be necessary since you have disabled the firewalls, but is worth trying anyway. Note: the server should be running on the system before you attempt to connect. If the applet is running, it should have started a server for you already (unless you disabled it in the options). The accounts do not have to be the same, it shouldn't make much difference unless you start fiddling the user account multicast filter ("match username"). If all else fails, you can run the server in debug mode and send me the log output (starting when you attempt to connect if possible): winswitch_server --debug-mode Cheers Antoine On 15/02/11 10:19, Jimi Bove wrote: > I forgot to add, I think it might have something to do with the users. > I can't figure out how to create users the computers can log into, but > I don't know how they could log in to some random user. I mean it > requires a password. How do I set all that stuff? And does the fact > that the usernames of the accounts on both computers are the same, as > are the usernames connected to their local servers, change anything? > > On Mon, Feb 14, 2011 at 7:17 PM, Jimi Bove > wrote: > > I'm trying to get my Linux and Windows computers connected with > this program and it just refuses to work. When I first tried it, I > launched winsitch_applet through the terminal in Linux. The tray > icon didn't appear, but the server started and the Windows > computer automatically connected. After that incident, the tray > icon now appears and both computers see each other, but they can't > connect. I've tried every setting with both firewalls disabled, > and I don't know what else to try. The fact that it worked once > rules out multicast issues, doesn't it? > > From jimijames.bove at gmail.com Tue Feb 15 17:08:54 2011 From: jimijames.bove at gmail.com (Jimi Bove) Date: Tue, 15 Feb 2011 09:08:54 -0800 Subject: [shifter-users] Window Switch problem In-Reply-To: <4D5A2CF7.8080608@devloop.org.uk> References: <4D5A2CF7.8080608@devloop.org.uk> Message-ID: I think we have found the problem. avahi-discover can see everything on my network and get the information on it all just fine, including other Linux and Mac stuff. However, anything that comes from my Windows computer is detected, but I can't get any info on it. It just says "Error: org.freedesktop.Avahi.TimeoutError: Timeout reached". I don't have another Windows device, so the problem is either A) my Linux computer can't talk to Windows or B) something besides the firewall is messing up on Windows. On Mon, Feb 14, 2011 at 11:36 PM, Antoine Martin wrote: > Can you login via ssh as that user? > Multicast is tricky but you are right: if it has connected before, it > should be ok. > Try running avahi-discover to browse the services it advertises. > > The quick-connect window does use ssh if you select it, which should not be > necessary since you have disabled the firewalls, but is worth trying anyway. > > Note: the server should be running on the system before you attempt to > connect. If the applet is running, it should have started a server for you > already (unless you disabled it in the options). > > The accounts do not have to be the same, it shouldn't make much difference > unless you start fiddling the user account multicast filter ("match > username"). > > If all else fails, you can run the server in debug mode and send me the log > output (starting when you attempt to connect if possible): > winswitch_server --debug-mode > > Cheers > Antoine > > > > > On 15/02/11 10:19, Jimi Bove wrote: > >> I forgot to add, I think it might have something to do with the users. I >> can't figure out how to create users the computers can log into, but I don't >> know how they could log in to some random user. I mean it requires a >> password. How do I set all that stuff? And does the fact that the usernames >> of the accounts on both computers are the same, as are the usernames >> connected to their local servers, change anything? >> >> On Mon, Feb 14, 2011 at 7:17 PM, Jimi Bove > jimijames.bove at gmail.com>> wrote: >> >> I'm trying to get my Linux and Windows computers connected with >> this program and it just refuses to work. When I first tried it, I >> launched winsitch_applet through the terminal in Linux. The tray >> icon didn't appear, but the server started and the Windows >> computer automatically connected. After that incident, the tray >> icon now appears and both computers see each other, but they can't >> connect. I've tried every setting with both firewalls disabled, >> and I don't know what else to try. The fact that it worked once >> rules out multicast issues, doesn't it? >> >> >> > From antoine at nagafix.co.uk Tue Feb 15 23:41:50 2011 From: antoine at nagafix.co.uk (Antoine Martin) Date: Wed, 16 Feb 2011 06:41:50 +0700 Subject: [shifter-users] Window Switch problem In-Reply-To: References: <4D5A2CF7.8080608@devloop.org.uk> Message-ID: <4D5B0F3E.4010006@nagafix.co.uk> On 16/02/11 00:08, Jimi Bove wrote: > I think we have found the problem. avahi-discover can see everything > on my network and get the information on it all just fine, including > other Linux and Mac stuff. However, anything that comes from my > Windows computer is detected, but I can't get any info on it. It just > says "Error: org.freedesktop.Avahi.TimeoutError: Timeout reached". I > don't have another Windows device, so the problem is either A) my > Linux computer can't talk to Windows or B) something besides the > firewall is messing up on Windows. Good work. It tells me that the mDNS info is coming out of the windows box (multicast), but that all the requests for detailed information are not.. (either not being received or not being responded to) Since you've checked that the firewall is not blocking mDNS traffic, something else must be... 1) First option: winswitch + mDNS is broken on windows. That's unlikely, but I could have missed it, I will check at the earliest opportunity. 2) More likely, something is preventing bonjour from operating properly on windows. So I would use normal network diagnostic tools (telnet, tcpdump, etc) to figure out where things get stuck, comparing it with the traffic from a working setup. Assuming that the problem is indeed from mdns, you may be able to get more help on a list dedicated to it. A potential workaround, which I have not used in a long time, is the "reverse multicast" option of winswitch. This would have to be enabled on *all* the clients, and would require an extra port to be punched through their firewalls.. not ideal. Cheers Antoine > > On Mon, Feb 14, 2011 at 11:36 PM, Antoine Martin > > wrote: > > Can you login via ssh as that user? > Multicast is tricky but you are right: if it has connected before, > it should be ok. > Try running avahi-discover to browse the services it advertises. > > The quick-connect window does use ssh if you select it, which > should not be necessary since you have disabled the firewalls, but > is worth trying anyway. > > Note: the server should be running on the system before you > attempt to connect. If the applet is running, it should have > started a server for you already (unless you disabled it in the > options). > > The accounts do not have to be the same, it shouldn't make much > difference unless you start fiddling the user account multicast > filter ("match username"). > > If all else fails, you can run the server in debug mode and send > me the log output (starting when you attempt to connect if possible): > winswitch_server --debug-mode > > Cheers > Antoine > > > > > On 15/02/11 10:19, Jimi Bove wrote: > > I forgot to add, I think it might have something to do with > the users. I can't figure out how to create users the > computers can log into, but I don't know how they could log in > to some random user. I mean it requires a password. How do I > set all that stuff? And does the fact that the usernames of > the accounts on both computers are the same, as are the > usernames connected to their local servers, change anything? > > On Mon, Feb 14, 2011 at 7:17 PM, Jimi Bove > > >> wrote: > > I'm trying to get my Linux and Windows computers connected with > this program and it just refuses to work. When I first > tried it, I > launched winsitch_applet through the terminal in Linux. The > tray > icon didn't appear, but the server started and the Windows > computer automatically connected. After that incident, the tray > icon now appears and both computers see each other, but > they can't > connect. I've tried every setting with both firewalls disabled, > and I don't know what else to try. The fact that it worked once > rules out multicast issues, doesn't it? > > > >