(nutty) Unable to find devices on local network

Bug #1736683 reported by Bump
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Nutty
New
Undecided
Unassigned

Bug Description

Local devices on same network are not displayed. See screenshot.

Revision history for this message
Siddhartha Das (bablu-boy) wrote :

Can you please run nutty in debug mode and provide the output here for analysis.
Please run wired and wireless interfaces to see if the wireless one works.

Revision history for this message
Bump (bump55) wrote :

I've renamed the network interface but it's the same.
Wired interface:
nutty --debug
** (process:4717): DEBUG: nutty.vala:156: Nutty Application running in debug mode - all debug messages will be displayed
[INFO 14:21:13.860417] Application.vala:154: Nutty version: 0.9
[INFO 14:21:13.860444] Application.vala:156: Kernel version: 4.13.0-17-generic
(nutty:4717): Gtk-DEBUG: Connecting to session manager
[WARNING 14:21:13.895490] [GLib] Invalid file descriptor.
[FATAL 14:21:13.896673] [GLib-GObject] g_object_ref: assertion 'G_IS_OBJECT (object)' failed
[FATAL 14:21:13.896695] [Gtk] gtk_widget_get_parent: assertion 'GTK_IS_WIDGET (widget)' failed
[WARNING 14:21:13.918509] nutty.vala:1248: Error encountered in execution of sync command [/sbin/ifconfig -a eth0]: eth0: error fetching interface information: Device$
[WARNING 14:21:29.961681] [GLib] Invalid file descriptor.

Revision history for this message
Bump (bump55) wrote :

It happens the same with wired and wireless interfaces, with or without airplane mode on.

nutty --debug
** (process:7723): DEBUG: nutty.vala:156: Nutty Application running in debug mode - all debug messages will be displayed
[INFO 14:36:37.942297] Application.vala:154: Nutty version: 0.9
[INFO 14:36:37.942326] Application.vala:156: Kernel version: 4.13.0-17-generic
(nutty:7723): Gtk-DEBUG: Connecting to session manager
[WARNING 14:36:37.978924] [GLib] Invalid file descriptor.
[FATAL 14:36:37.980047] [GLib-GObject] g_object_ref: assertion 'G_IS_OBJECT (object)' failed
[FATAL 14:36:37.980065] [Gtk] gtk_widget_get_parent: assertion 'GTK_IS_WIDGET (widget)' failed
[WARNING 14:38:01.802077] [GLib] Invalid file descriptor.

Revision history for this message
Bump (bump55) wrote :
Revision history for this message
Bump (bump55) wrote :
Revision history for this message
Siddhartha Das (bablu-boy) wrote :

Looks like /sbin/ifconfig -a eth0 is not working. Can you provide the output of the following command:
/sbin/ifconfig -a

Also, run nutty in debug like below and attach the log from from the home directory here:
nutty --debug > ~/nutty.log

When Nutty is opened, run the interfaces tab and then the search for devices tab. Then close nutty and attach the nutty.log in this issue for me to take a look.

Revision history for this message
Bump (bump55) wrote :

Here are 2 new screenshots. There is no such interfaces tab.

Revision history for this message
Bump (bump55) wrote :
Revision history for this message
Bump (bump55) wrote :
Revision history for this message
Bump (bump55) wrote :
Revision history for this message
Bump (bump55) wrote :
Revision history for this message
Bump (bump55) wrote :
Revision history for this message
Siddhartha Das (bablu-boy) wrote :

Thanks for your patience in debugging this. By Interfaces Tab I actually meant the Info Tab (my bad). Here are some next steps:

1- Is Nutty installed via snaps on your system. You can check this by running the command:
snap list
If nutty shows up in the command above, then that might be the issue (snap is not working for Nutty) and you can install via the PPA.

2- The debug log you attached does not contain enough information, may be you closed Nutty out too soon. Try the following steps:
nutty --debug > ~/nutty.log
when Nutty opens carry out the following actions:
a. In the Info tab: change the dropdown to a few different connections i.e. wireless, ethernet, etc.
b. In the Devices tab: change the dropdown to a few different connections
c. Close Nutty
d. Attach the debug.log back in this bug here.

Revision history for this message
Bump (bump55) wrote :
Revision history for this message
Bump (bump55) wrote :

I'm running plasma in case it has something to do.

Revision history for this message
Siddhartha Das (bablu-boy) wrote :

Nutty was developed for Gnome - not sure how it will work for Plasma. Although I thought the difference will only be in the look and feel. But seeing your logs it does not look like it is even printing enough debug - I have added a sample log of opening nutty in debug mode and doing some activities like a few clicks on the Info tab and the Devices tab.

I had some information on how to install from PPA here:
https://bugs.launchpad.net/nutty/+bug/1751577/comments/1

Alternatively you can build from source on GitHub with these instructions:
https://github.com/babluboy/nutty#how-to-build-nutty

Revision history for this message
Bump (bump55) wrote :
Download full text (4.0 KiB)

This is on gnome:

** (process:5930): DEBUG: nutty.vala:156: Nutty Application running in debug mode - all debug messages will be displayed
[INFO 18:02:31.255772] Application.vala:154: Nutty version: 0.9
[INFO 18:02:31.255796] Application.vala:156: Kernel version: 4.13.0-36-generic
(nutty:5930): Gtk-DEBUG: Connecting to session manager
[WARNING 18:02:31.296083] [GLib] Invalid file descriptor.
[FATAL 18:02:31.297502] [GLib-GObject] g_object_ref: assertion 'G_IS_OBJECT (object)' failed
[FATAL 18:02:31.297519] [Gtk] gtk_widget_get_parent: assertion 'GTK_IS_WIDGET (widget)' failed
[WARNING 18:02:31.387558] AT-SPI: Could not obtain desktop path or name
[WARNING 18:02:31.393291] AT-SPI: Could not obtain desktop path or name
[WARNING 18:02:31.393440] AT-SPI: Could not obtain desktop path or name
[WARNING 18:02:31.393509] AT-SPI: Could not obtain desktop path or name
[WARNING 18:02:31.393559] AT-SPI: Could not obtain desktop path or name
[WARNING 18:02:31.393606] AT-SPI: Could not obtain desktop path or name
[WARNING 18:02:31.393649] atk-bridge: get_device_events_reply: unknown signature
[WARNING 18:02:31.393670] atk-bridge: get_device_events_reply: unknown signature
[WARNING 18:02:31.393694] atk-bridge: GetRegisteredEvents returned message with unknown signature
[WARNING 18:02:31.399859] AT-SPI: Could not obtain desktop path or name
[WARNING 18:02:31.399933] atk-bridge: get_device_events_reply: unknown signature
[WARNING 18:02:31.399951] atk-bridge: get_device_events_reply: unknown signature
[WARNING 18:02:31.399968] atk-bridge: GetRegisteredEvents returned message with unknown signature
[WARNING 18:02:31.399984] atk-bridge: get_device_events_reply: unknown signature
[WARNING 18:02:31.400000] atk-bridge: get_device_events_reply: unknown signature
[WARNING 18:02:31.400016] atk-bridge: GetRegisteredEvents returned message with unknown signature
[WARNING 18:02:31.400032] atk-bridge: get_device_events_reply: unknown signature
[WARNING 18:02:31.400048] atk-bridge: get_device_events_reply: unknown signature
[WARNING 18:02:31.400064] atk-bridge: GetRegisteredEvents returned message with unknown signature
[WARNING 18:02:31.400079] atk-bridge: get_device_events_reply: unknown signature
[WARNING 18:02:31.400096] atk-bridge: get_device_events_reply: unknown signature
[WARNING 18:02:31.400111] atk-bridge: GetRegisteredEvents returned message with unknown signature
[WARNING 18:02:31.400127] atk-bridge: get_device_events_reply: unknown signature
[WARNING 18:02:31.400142] atk-bridge: get_device_events_reply: unknown signature
[WARNING 18:02:31.400158] atk-bridge: GetRegisteredEvents returned message with unknown signature
[WARNING 18:02:31.439825] AT-SPI: Could not obtain desktop path or name
[WARNING 18:02:31.439863] AT-SPI: Could not obtain desktop path or name
[WARNING 18:02:31.439894] AT-SPI: Could not obtain desktop path or name
[WARNING 18:02:31.439925] AT-SPI: Could not obtain desktop path or name
[WARNING 18:02:31.446497] AT-SPI: Could not obtain desktop path or name
[WARNING 18:02:31.446811] AT-SPI: Could not obtain desktop path or name
[WARNING 18:02:31.454202] AT-SPI: Could not obtain desktop path or name
[WARNING 18:02:31.480226] AT-SPI: Could not obta...

Read more...

Revision history for this message
Siddhartha Das (bablu-boy) wrote :

I see that this bug is pretty common for Gtk apps, but not sure what is causing the same:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1675364

https://www.linuxquestions.org/questions/linux-software-2/warning-%2A%2A-at-spi-could-not-obtain-desktop-path-or-name-4175557137/

I would shortly make Nutty available as a Flatpak, hopefully you can make use of the same without issues. This issue does not occur on Elementary OS.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.