From: superiums <superiums@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] blueman-manager couldn't launch by blueman-applet
Date: Wed, 31 May 2023 06:45:38 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44188@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2814 bytes --]
New issue by superiums on void-packages repository
https://github.com/void-linux/void-packages/issues/44188
Description:
to reproduce:
1. launch blueman-applet
2. right-click on the applet.
3. on the menu , click devices.
4. no window show, but report:
```bash
~ ❯❯❯ blueman-applet
blueman-applet 12.34.49 WARNING PluginManager:94 load_plugin: Failed to start plugin GameControllerWakelock: Only X11 platform is supported
blueman-applet 12.34.49 WARNING PluginManager:151 __load_plugin: Not loading PPPSupport because its conflict has higher priority
blueman-applet 12.34.49 WARNING PluginManager:151 __load_plugin: Not loading DhcpClient because its conflict has higher priority
Traceback (most recent call last):
File "/usr/lib/python3.11/site-packages/blueman/main/DBusProxies.py", line 52, in call_finish
proxy.call_finish(resp)
gi.repository.GLib.GError: g-dbus-error-quark: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying (4)
Traceback (most recent call last):
File "/usr/lib/python3.11/site-packages/blueman/main/DBusProxies.py", line 52, in call_finish
proxy.call_finish(resp)
gi.repository.GLib.GError: g-dbus-error-quark: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying (4)
```
the blueman-manager could be start from terminal.
but can't start by blueman-applet.
i'm on wayland, using wayfire as my wm.
my dbus service was enabled and runing.
all packages are up to date.
```bash
~ ❯❯❯ sudo sv status /var/service/*
run: /var/service/acpid: (pid 1124) 7825s
run: /var/service/agetty-tty1: (pid 1136) 7825s
run: /var/service/agetty-tty2: (pid 1131) 7825s
run: /var/service/agetty-tty3: (pid 1122) 7825s
run: /var/service/agetty-tty4: (pid 1129) 7825s
run: /var/service/agetty-tty5: (pid 1125) 7825s
run: /var/service/agetty-tty6: (pid 1123) 7825s
run: /var/service/bluetoothd: (pid 1140) 7825s; run: log: (pid 1137) 7825s
run: /var/service/cupsd: (pid 1144) 7825s; run: log: (pid 1142) 7825s
run: /var/service/dbus: (pid 1141) 7825s; run: log: (pid 1138) 7825s
run: /var/service/greetd: (pid 1126) 7825s
run: /var/service/NetworkManager: (pid 1150) 7825s; run: log: (pid 1147) 7825s
run: /var/service/pipewire: (pid 1148) 7825s; run: log: (pid 1146) 7825s
run: /var/service/pipewire-pulse: (pid 1139) 7825s; run: log: (pid 1135) 7825s
run: /var/service/polkitd: (pid 1121) 7825s
run: /var/service/postgresql14: (pid 1134) 7825s; run: log: (pid 1127) 7825s
run: /var/service/udevd: (pid 1133) 7825s
run: /var/service/uuidd: (pid 1130) 7825s; run: log: (pid 1128) 7825s
run: /var/service/wireplumber: (pid 1145) 7825s; run: log: (pid 1132) 7825s
```
next reply other threads:[~2023-05-31 4:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 4:45 superiums [this message]
2023-05-31 6:06 ` [ISSUE] [CLOSED] " classabbyamp
-- strict thread matches above, loose matches on Subject: below --
2023-05-31 4:42 [ISSUE] " superiums
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44188@inbox.vuxu.org \
--to=superiums@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).