Custom Query (230 matches)


Show under each result:

Results (97 - 99 of 230)

Ticket Resolution Summary Owner Reporter
#131 worksforme winswitch not running on debian sid Antoine Martin peter12

after running "winswitch_applet" got the folowing failure feedback:

Traceback (most recent call last):
  File "/usr/bin/winswitch_applet", line 3, in <module>
    from winswitch.client import applet_wrapper
ImportError: No module named winswitch.client
lsb_release -a
LSB Version:    core-2.0-ia32:core-2.0-noarch:core-3.0-ia32:core-3.0-noarch:core-3.1-ia32:core-3.1-noarch:core-3.2-ia32:core-3.2-noarch
Distributor ID: Debian
Description:    Debian GNU/Linux unstable (sid)
Release:        unstable
Codename:       sid
#133 fixed open file remotely without using ssh channel Antoine Martin Antoine Martin

The sftp code was removed with paramiko, what we can do to restore the functionality is to define a new message type for file transfers and send the file through the normal client-server channel.

  • new accept_files option for servers (defaults to off?)
  • keep file pointer + index in server connection
  • send first chunk of data, below the max_line limit and also taking into account the link speed
  • server creates a temporary file in configurable download location (default to ~/Download)
  • server sends an ack after each packet is received (potential small delay here to ensure we prioritize other packets ahead of file transfers)
  • client fire progress_update callbacks registered with the file transfer
  • client sends the next chunk (potential delay here - same reason as above), taking into account how long the first previous took (so we can keep UI updates regular - say 1 second target)
  • if the server (or client) does not ack (or send the next chunk) within a certain amount of time (tbd - dynamic?), we cancel the whole thing and tell the other end. The server can delete the temporary file.
  • When the transfer is complete, we ask the server to open it.
  • Ensure file data is encrypted over the wire
#134 fixed move all internal scripts to /usr/libexec - these aren't meant to be used directly Antoine Martin Antoine Martin

Only a few scripts should remain in /usr/bin:

  • winswitch_applet / winswitch_server : essentials
  • winswitch_away / winswitch_back : can be used by blueproximity, etc
  • winswitch_command_wrapper : used by .desktop command lines, must be on PATH to make it user friendly
  • winswitch_stdio_socket / winswitch_stdio_tcp : can be used by users for diagnosys (maybe)

Almost everything else we can move to libexec. This is cleaner and better for packaging. Means we don't need so many manual pages.

Note: See TracQuery for help on using queries.