-
Notifications
You must be signed in to change notification settings - Fork 258
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
Port already in use, but not by KDE. #1555
Comments
Two possibilities:
|
Ignore my first thought, if it happened right after boot then it's not likely to be an upgrade issue. It's probably number 2. |
It's just in |
I would conjecture that installing more clients will not solve your problem. Can you show the output of |
Or can you check the output of |
and
;)
|
The command should have been netstat, not netcat |
It sounds like there are two versions of GSConnect installed. Can you check if there are two processes running? |
I thought then it must be displayed in tray drop down menu (or how it titles right...) |
The solution is to uninstall it from everywhere except the extensions website. If you installed it with Extension Manager, you should uninstall any distribution package.
GSConnect can only run one instance. The only way this can happen is if another copy of GSConnect is installed or another KDE Connect client is installed. |
Describe the bug
Port already in use, but not by KDE. 1716 used by gjs
Steps to reproduce
Expected behavior
It works automatically after the boot
GSConnect version
50
Installed from
GNOME Extensions website
GNOME Shell version
42.5
Linux distribution/release
Ubuntu 22.04.1 LTS
Paired device(s)
Redmi Note 7 Pro
KDE Connect app version
1.21.1
Plugin(s)
No response
Support log
GSConnect: 50 (user)
GJS: 17400
Session: wayland
OS: Ubuntu 22.04.1 LTS
Hint: You are currently not seeing messages from other users and the system.
Users in groups 'adm', 'systemd-journal' can see all messages.
Pass -q to turn off this notice.
янв 19 17:31:04 zeitgeist-datah[7484]: /home/rio/.local/share/applications/defaults.list contains a [Added Associations] group, but it is not permitted here. Only the non-desktop-specific mimeapps.list file may add or remove associations.
янв 19 17:31:04 zeitgeist-daemon[8810]: [14:31:04.882410 WARNING] ext-fts.vala:138: Ошибка вызова StartServiceByName для org.gnome.zeitgeist.SimpleIndexer: Время ожидания истекло
янв 19 17:31:06 gjs[9432]: /home/rio/.local/share/applications/defaults.list contains a [Added Associations] group, but it is not permitted here. Only the non-desktop-specific mimeapps.list file may add or remove associations.
янв 19 17:31:06 gvfsd[9511]: smbXcli_negprot_smb1_done: No compatible protocol selected by server.
янв 19 17:31:06 gvfsd[9511]: got no contact to IPC$
янв 19 17:31:06 gvfsd[9511]: smbXcli_negprot_smb1_done: No compatible protocol selected by server.
янв 19 17:31:06 gvfsd[9511]: got no contact to IPC$
янв 19 17:31:07 pkexec[9547]: rio: Error executing command as another user: Not authorized [USER=root] [TTY=unknown] [CWD=/home/rio] [COMMAND=/usr/lib/update-notifier/package-system-locked]
янв 19 17:31:07 update-notifier.desktop[9547]: Error executing command as another user: Not authorized
янв 19 17:31:07 update-notifier.desktop[9547]: This incident has been reported.
янв 19 17:31:07 update-notifier[9391]: /home/rio/.local/share/applications/defaults.list contains a [Added Associations] group, but it is not permitted here. Only the non-desktop-specific mimeapps.list file may add or remove associations.
янв 19 17:31:07 gnome-shell[2700]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
янв 19 17:31:07 [email protected][2700]: unable to update icon for software-update-available
янв 19 17:31:07 gnome-shell[2700]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
янв 19 17:31:07 [email protected][2700]: unable to update icon for livepatch
Screenshots
No response
Notes
No response
The text was updated successfully, but these errors were encountered: