Debugging

General Debugging

Once you have enabled debug mode in the extension preferences, basic output can be viewed by running the following command in an open terminal:

$ journalctl /usr/bin/gnome-shell -f -o cat
[[email protected]]: DEBUG: initializing extension
[[email protected]]: DEBUG: enabling extension
[[email protected]]: DEBUG: extension.SystemIndicator._serviceAppeared()
[[email protected]]: DEBUG: extension.SystemIndicator._deviceAdded(/modules/kdeconnect/devices/5dd3aea571d9f746)
[[email protected]]: DEBUG: extension.DeviceMenu._statusChanged(/modules/kdeconnect/devices/5dd3aea571d9f746)
[[email protected]]: DEBUG: extension.DeviceMenu._pluginsChanged()
[[email protected]]: DEBUG: extension.DeviceMenu._batteryChanged(false,47)
[[email protected]]: DEBUG: extension.DeviceIndicator._sync()

Debugging Share and SMS

The Share/Send To plugin and the SMS Application are implemented as stand-alone programs, and require a little more work to debug.

To debug either, you need to find an active device ID, which can be done using share.js:

$ cd ~/.local/share/gnome-shell/extensions/[email protected]
$ gjs share.js --list-available
Nexus 4: 5dd3aea571d9f746

From here you could debug sending a file to your device by running:

# open a file chooser dialog
$ gjs share.js --device=5dd3aea571d9f746
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.

# send a file (currently only by uri) or link
$ gjs share.js --device=5dd3aea571d9f746 --share=file:///home/andrew/.local/share/gnome-shell/extensions/[email protected]/share.js

# getting help
$ gjs share.js --help
Usage:
  MConnect File Share [OPTION…]

Help Options:
  -h, --help                   Show help options
  --help-all                   Show all help options
  --help-gapplication          Show GApplication options

Application Options:
  -d, --device=<device-id>     Device ID
  -s, --share=<uri>            Share a local (eg. file:///...) or remote uri with <device-id>
  -l, --list-devices           List all devices
  -a, --list-available         List available (paired and reachable) devices

$

Similarly, you can debug the SMS Application:

$ gjs sms.js --help
Usage:
  MConnect SMS [OPTION…]

Help Options:
  -h, --help                   Show help options
  --help-all                   Show all help options
  --help-gapplication          Show GApplication options
  --help-gtk                   Show GTK+ Options

Application Options:
  -d, --device=<device-id>     Device ID
  --display=DISPLAY            X display to use

$ gjs sms.js --device=5dd3aea571d9f746

Debugging Folks Contact Integration

Folks integration relies on a Python shim written by @hugosenari. First ensure you have all the required dependencies installed. If you are still encountering problems with contact integration, the Python shim can be executed directly with the following command:

$ python3 ~/.local/share/gnome-shell/extensions/[email protected]/folks.py

The script should output a list of contacts in the format:

Ghostbusters	555-2368	work

If it does not, please open a new issue and include any errors printed to the console.

Debugging DBus

The easiest way to debug the DBus interface of either KDE Connect or MConnect is using D-Feet, which should be available from your distribution's package manager. This can give you a lot of useful information to aid in tracking down problems, and can even let you execute some commands directly.