Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Device status showing like connected, despite not connected #1869

Open
Altonss opened this issue Sep 27, 2024 · 2 comments
Open

Device status showing like connected, despite not connected #1869

Altonss opened this issue Sep 27, 2024 · 2 comments
Labels
needs info An issue that needs more information

Comments

@Altonss
Copy link

Altonss commented Sep 27, 2024

Describe the bug

The associated device is showing as if it was connected (battery status, possibility to click on send files...), despite not being connected.

Steps to reproduce

No response

Expected behavior

It should show an up to date status of the connection.

GSConnect version

57

Installed from

GNOME Extensions website

GNOME Shell version

46

Linux distribution/release

Fedora Linux 40 (Workstation Edition)

Paired device(s)

No response

KDE Connect app version

1.32.2 (F-Droid)

Plugin(s)

No response

Support log

No response

Screenshots

No response

Notes

No response

@github-actions github-actions bot added the triage An issue that needs confirmation and labeling label Sep 27, 2024
@ferdnyc
Copy link
Member

ferdnyc commented Sep 30, 2024

@Altonss

Hmm, that's not a whole lot to go on, unfortunately. A few questions:

  1. If the device is showing data in the extension, what makes you say it's not connected? (I believe you, I'm just wondering how you determined that. Does it not show up on the Android side? Is the Android device offline? Does trying to interact with it via GSConnect fail?)
  2. Is this something that just happened once, or does it happen repeatably?
  3. What about if you open the GSConnect Preferences ("Mobile Settings" from the user menu); (a) does it show as "Connected" in the device list, and (b) what happens if you hit the Refresh button in the upper-left corner?

Unfortunately the "Generate Support Log" debugging tool doesn't work in the release version of v57, or I'd recommend collecting logs that way. But you can run journalctl --user -b --grep gsconnect in a terminal window, to see if there have been any messages logged since boot; JavaScript errors would be the most interesting data, if there are any.

You'll probably see at least one "Failed to start app-gnome-org.gnome.Shell.Extensions.GSConnect.Preferences..." message; if the preferences did start, then you can disregard those.

@ferdnyc ferdnyc added needs info An issue that needs more information and removed triage An issue that needs confirmation and labeling labels Sep 30, 2024
@Altonss
Copy link
Author

Altonss commented Sep 30, 2024

If the device is showing data in the extension, what makes you say it's not connected? (I believe you, I'm just wondering how you determined that. Does it not show up on the Android side? Is the Android device offline? Does trying to interact with it via GSConnect fail?)

The battery level was wrong, which indicates it was still displaying data from a past connection. And on the Android side it wasn't showing up as connected too :)

Is this something that just happened once, or does it happen repeatably?

Right now I'm not sure, maybe it already happened in the past but I don't remember.

What about if you open the GSConnect Preferences ("Mobile Settings" from the user menu); (a) does it show as "Connected" in the device list, and (b) what happens if you hit the Refresh button in the upper-left corner?

IIRC it was showing as connected in the device list.

I'll try to collect logs if I see this issue again :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs info An issue that needs more information
Projects
None yet
Development

No branches or pull requests

2 participants