Bug 376911 - no devices
Summary: no devices
Status: RESOLVED FIXED
Alias: None
Product: kdeconnect
Classification: Applications
Component: plasmoid (show other bugs)
Version: 1.3
Platform: Fedora RPMs Linux
: NOR grave
Target Milestone: ---
Assignee: Albert Vaca Cintora
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-02-25 09:30 UTC by know1
Modified: 2017-07-14 00:01 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
gui with no devices (46.67 KB, image/png)
2017-02-25 12:40 UTC, know1
Details
rename (11.93 KB, image/png)
2017-02-25 13:12 UTC, know1
Details
log from login (2.15 KB, text/plain)
2017-02-25 14:10 UTC, know1
Details
kdeconnect working machine log (1.45 KB, text/plain)
2017-02-25 14:29 UTC, know1
Details
caught after polkit reinstall and deps with KDE apps (39.12 KB, image/png)
2017-02-25 21:42 UTC, know1
Details

Note You need to log in before you can comment on or make changes to this bug.
Description know1 2017-02-25 09:30:20 UTC
Fresh install with Fedora workstation from iso. (am thinking this may be where it's hit the fan? as I copied and pasted from another machine, almost identical in hardware, using the package manager list and giving/transferring it to dnf on the problem install, to cut time down to the minimum).
Anyways, nothing shows when refreshing the gui and when run from terminal nothing is indicating anything wrong. Have installed using source and still nothing showing in terms of devices connected.
My 'droids don't see the machine or other Fedora installs. Ive reinstalled the program, maybe I need to reinstall my OS? (not much chance in the latter hozay)
Comment 1 know1 2017-02-25 12:40:00 UTC
Created attachment 104214 [details]
gui with no devices
Comment 2 know1 2017-02-25 12:42:18 UTC
ports are open for the program 
2 other Fedora25 machines don't see it and 5 Android devices also have no connection with it even adding the IP address produces nothing
Comment 3 Albert Vaca Cintora 2017-02-25 12:55:13 UTC
Maybe the kdeconnect config from your old distro doesn't work on the new one. Go to ~/.config and rename kdeconnect to something else. Log out and log in again so the config is recreated and let me know if it solves the problem.
Comment 4 know1 2017-02-25 13:12:56 UTC
Created attachment 104215 [details]
rename

after rename and re-login 
this showing in logs; recurring 

Feb 20 13:05:02 localhost.localdomain /usr/libexec/gdm-x-session[1362]: Fail set label TypeError: menuitem is null
Comment 5 know1 2017-02-25 13:13:35 UTC
no change to the program being visible!!
Comment 6 Albert Vaca Cintora 2017-02-25 13:23:56 UTC
In that case I'm not sure what the error can be. Try running the kdeconnectd binary on a terminal and see what the output looks like. The location of the binary changes depending on the distribution (eg: on Arch it's in /usr/lib/libexec/kdeconnectd). Also make sure to "killall kdeconnectd" before running it, as if it detects another instance is running it just terminates without doing anything.
Comment 7 know1 2017-02-25 14:10:05 UTC
Created attachment 104218 [details]
log from login

Is the polkit the problem
Comment 8 know1 2017-02-25 14:15:02 UTC
I have looked at the logs upon login using 2 machines and the/this bad 1 is showing the auto start service with the url omitting my home directory which DOES SHOW on the good machine

i.e. "/etc/xdg/autostart
instead of ~/.config/autostart/*
and polkit Registered
(trying to login... sorry on my other laptop, much easier when this program works)
Comment 9 know1 2017-02-25 14:29:17 UTC
Created attachment 104219 [details]
kdeconnect working machine log

shows the polkit registering on a good machine, so if thisis the problem, how do I fix it?
Comment 10 know1 2017-02-25 15:04:09 UTC
    localhost ~]$ /usr/libexec/kdeconnectd



    nothing
Comment 11 Albert Vaca Cintora 2017-02-25 15:13:51 UTC
killall kdeconnectd; /usr/libexec/kdeconnectd
Comment 12 know1 2017-02-25 15:14:45 UTC
did that

and not a sausage
Comment 13 Albert Vaca Cintora 2017-02-25 15:34:51 UTC
Then something is really broken with your system. You should at least see "kdeconnect.core: KdeConnect daemon starting". Make sure your kdeconnectd is actually dead, before starting the new one!
Comment 14 know1 2017-02-25 15:39:03 UTC
I'll remove a some packages with the bunch of deps and see if anything changes, I've started with removing polkit and doing a kernel update @tm so if anything changes there'll be a report on here.
Thanks for your speedy reply, oh yes all kdeconnectd was killed before executing
Comment 15 know1 2017-02-25 15:47:33 UTC
when I say nothing happened within the terminal command, the kdeconnectd did start again but there was no change to the program
Comment 16 Albert Vaca Cintora 2017-02-25 18:12:06 UTC
What was the output? Any message that looks like an error?
Comment 17 know1 2017-02-25 18:29:21 UTC
'blank' on the problem machine 
and just icon missing with the good 1
Comment 18 Albert Vaca Cintora 2017-02-25 18:36:19 UTC
It should print something on the console where you execute it.
Comment 19 know1 2017-02-25 18:41:02 UTC
(In reply to Albert Vaca from comment #18)
> It should print something on the console where you execute it.

nope
(nothing on my working desktop aswell)
Comment 20 know1 2017-02-25 18:48:23 UTC
the cursor is just wedged to the left and blank
Comment 21 know1 2017-02-25 21:42:34 UTC
Created attachment 104223 [details]
caught after polkit reinstall and deps with KDE apps

After removing polkit and reinstalling all the essential deps back again after a few reboots, first there was a component crash in the top right of screen but no indication of which (shall have to crawl through the journalctl (shall see if I can see anything) did a couple of logins after reinstalling KDE and apps ('cause polkit requires loads of deps) kdecrashed + other.
This was noticed on my initial install (lots of crashes, like the snapshot) but didn't catch it with screenshot
Comment 22 know1 2017-02-25 21:55:10 UTC
As you would guess! no change in the kdeconnect💣
Comment 23 know1 2017-02-26 11:11:31 UTC
Was just about to hose my system after doing some backups, when I thought of rebooting just 1 last time.
I had previously removed some troublesome packages relating to (nVidia, I'm with Linus on this 1 and they deserve the finger, lost sleep over it trying to get it to work), anyways, after logging in I found no WiFi to connect with and plugged in my wired connection. Opened KDE Connect (BOOM), low and behold >> Devices to connect to.
Comment 24 know1 2017-02-26 11:12:42 UTC
I'll try to nail the problem when I do a bit more investigation, but can safely say it's fixed for now!!
Comment 25 know1 2017-02-26 22:42:17 UTC
Come to the conclusion my install si BORKED.
The program failed again so I'm going to wipe it out of my miserable life and try a fresh / install
Comment 26 know1 2017-02-27 22:15:06 UTC
comment #13
summed it up.
Something went bad with the system.
All is good now with a fresh install.
The GChrome Ext' is great addition btw 
Thanks for your support Albert
Comment 27 Aleix Pol 2017-07-14 00:01:13 UTC
Seems like it wasn't a problem in the end.