--- Please enter the report below this line. ---
1. One must drop firewall for phone to see desktop. Will work with firewall
afterwards but no clear how-to set this up.
2. Same-day in-out-in to WIFI will reconnect--good. Following day, PC and
phone off meanwhile, unable to use at all, with or without firewall.
3. Multiple user-KDE logons may have disabled the app. Phone sees first user,
others seem disabled, even with no pairage.
4. Not clear what to do with sshfs. Phone app kicked phone off until rebooted
(not Debian problem, obviously).
5. No documentation. If the thing does get paired, how to get to functions
besides batter charging and toast-notifications?

Debian Release: jessie/sid
  500 unstable        ftp.us.debian.org
  500 testing         ftp.us.debian.org
  500 sid             linux.dropbox.com
--- Package information. ---
Depends                           (Version) | Installed
===========================================-+-===================
libqca2                          (>= 2.0.2) | 2.0.3-6
libqca2-plugin-gnupg                        | 2.0.0~beta3-2
libqca2-plugin-ossl                         | 2.0.0~beta3-2
kde-runtime                     (>> 4:4.10) | 4:4.13.1-1
libc6                             (>= 2.14) | 2.19-7
libgcc1                        (>= 1:4.1.1) | 1:4.9.1-3
libkcmutils4                  (>= 4:4.4.95) | 4:4.13.3-2
libkdecore5                    (>= 4:4.7.1) | 4:4.13.3-2
libkdeui5                      (>= 4:4.7.0) | 4:4.13.3-2
libkfile4                      (>= 4:4.3.4) | 4:4.13.3-2
libkio5                       (>= 4:4.5.85) | 4:4.13.3-2
libqjson0                        (>= 0.8.1) | 0.8.1-3
libqt4-dbus                    (>= 4:4.5.3) | 4:4.8.6+git49-gbc62005+dfsg-1
libqt4-declarative         (>= 4:4.7.0~rc1) | 4:4.8.6+git49-gbc62005+dfsg-1
libqt4-network           (>= 4:4.7.0~beta1) | 4:4.8.6+git49-gbc62005+dfsg-1
libqt4-svg                     (>= 4:4.5.3) | 4:4.8.6+git49-gbc62005+dfsg-1
libqt4-xml                     (>= 4:4.5.3) | 4:4.8.6+git49-gbc62005+dfsg-1
libqtcore4                     (>= 4:4.8.0) | 4:4.8.6+git49-gbc62005+dfsg-1
libqtgui4                      (>= 4:4.8.0) | 4:4.8.6+git49-gbc62005+dfsg-1
libstdc++6                       (>= 4.4.0) | 4.9.1-3
libx11-6                                    | 2:1.6.2-2
libxau6                                     | 1:1.0.8-1
libxdmcp6                                   | 1:1.1.1-1
libxext6                                    | 2:1.3.2-1
libxtst6                                    | 2:1.2.2-1


Package's Recommends field is empty.

Package's Suggests field is empty.

OK, as I figured, the first login took possession of the app's connection. Yes,
I can pair, ping, etc., from this user's desktop.  But not from mine.

So, need some way to restrict the app or allow multiple clients! Client shown
as user@localhostname, filled in appropriately. This best done at the PC.

Like any network connection, need a way to "forget" a connection as well. This
needed on the device's app.

Need better documentation as to firewall rules. Right now I have the port-range
allowed to all in both directions, also (v6). Would want to restrict to the
phone, i.e. 10.0.0.2. Using ufw.

This morning, I was able to connect from my KDE session. The phone showed both
logins and I was able to pair mine.

Note that the desktop app shows the phone and the other login. I can even
request to pair with it. Interesting what that might give me (need to flip back
and forth quickly to accept :-) ).

So where there are bugs here, where there are inconsistancies, where those end
and these begin, seems quite fluid here.

Maybe file wishlist: Use cases? Multiple sessions? Multiple users? Multiple
devices/user (i.e. phone + tablet)? Should one phone be able to pair with
differing sessions--should a username be tied to the setup in the phone
(probably yes!)?

Actually worked but gave no functionality (expect any?). If not useful as a
"feature," then is a bug :-)