Issue description
I got no output with the command io.elementary.code --version
Then i ran:
[davidak@X230:~]$ io.elementary.code --help
GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
After that commands work normally.
cc @worldofpeace
Steps to reproduce
not reproducible again right now
Technical details
- system:
"x86_64-linux"
- host os:
Linux 4.19.59, NixOS, 19.03.173165.55b8860aa20 (Koi)
- multi-user?:
yes
- sandbox:
yes
- version:
nix-env (Nix) 2.2.2
- channels(davidak):
""
- channels(root):
"nixos-19.03.173165.55b8860aa20, nixos-hardware, nixos-unstable-19.09pre185259.362be9608c3"
- nixpkgs:
/nix/var/nix/profiles/per-user/root/channels/nixos
I am currently getting:
$ gnome-disks Failed to register: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
Had to reboot to make it work again.
Works for me under GNOME on nixos-unstable, exceptf for this hillarious gettext substitution:
$ nix run -f . pantheon.elementary-code -c io.elementary.code --help
Usage:
io.elementary.code [OPTION…] File
Help Options:
-h, --help Show help options
--help-all Show all help options
--help-gtk Show GTK+ Options
Application Options:
-t, --new-tab New Tab
-n, --new-window New Window
-v, --version Print version info and exit
-s, --set=Project-Id-Version: scratch
Report-Msgid-Bugs-To:
POT-Creation-Date: 2019-03-07 11:10-0800
PO-Revision-Date: 2019-01-28 08:10+0000
Last-Translator: Ciarán Ainsworth <ciaranainsworth@posteo.net>
Language-Team: English (United Kingdom) <https://weblate.elementary.io/projects/code/code/en_GB/>
Language: en_GB
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Plural-Forms: nplurals=2; plural=n != 1;
X-Generator: Weblate 3.0.1
X-Launchpad-Export-Date: 2017-05-03 06:04+0000
Set of plug-ins
-c, --cwd=Project-Id-Version: scratch
Report-Msgid-Bugs-To:
POT-Creation-Date: 2019-03-07 11:10-0800
PO-Revision-Date: 2019-01-28 08:10+0000
Last-Translator: Ciarán Ainsworth <ciaranainsworth@posteo.net>
Language-Team: English (United Kingdom) <https://weblate.elementary.io/projects/code/code/en_GB/>
Language: en_GB
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Plural-Forms: nplurals=2; plural=n != 1;
X-Generator: Weblate 3.0.1
X-Launchpad-Export-Date: 2017-05-03 06:04+0000
Current working directory
--display=DISPLAY X display to use
Probably something environmental. Do other applications exhibit this? Are there any more details in the journal? Does it happen again after you restart the session bus using systemctl restart --user dbus
(will kill your session)?
Thank you for your contributions.
This has been automatically marked as stale because it has had no activity for 180 days.
If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as «still important to me». This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity.
Here are suggestions that might help resolve this more quickly:
- Search for maintainers and people that previously touched the
related code and @ mention them in a comment. - Ask on the NixOS Discourse. 3. Ask on the #nixos channel on
irc.freenode.net.
stale
bot
added
the
2.status: stale
https://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md
label
Jun 1, 2020
it has had no activity for 180 days.
that does not mean it’s solved. i can still reproduce it
[davidak@gaming:~]$ io.elementary.code --version
[davidak@gaming:~]$ io.elementary.code --help
GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
[davidak@gaming:~]$ io.elementary.code --version
[WARNING 06:32:08.334429] [dbind] Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-JTQXBdtPJW: Connection refused
Code 3.4.0
- system:
"x86_64-linux"
- host os:
Linux 5.6.14, NixOS, 20.03.1950.48723f48ab9 (Markhor)
- multi-user?:
yes
- sandbox:
yes
- version:
nix-env (Nix) 2.3.4
- channels(root):
"home-manager-20.03, nixos-20.03.1950.48723f48ab9, nixos-hardware, nixos-unstable-20.09pre226148.0f5ce2fac0c"
- nixpkgs:
/nix/var/nix/profiles/per-user/root/channels/nixos
stale
bot
removed
the
2.status: stale
https://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md
label
Jun 1, 2020
I marked this as stale due to inactivity. → More info
stale
bot
added
the
2.status: stale
https://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md
label
Nov 28, 2020
I can’t reproduce this exact error, so it might be fixed.
I created another issue for this new error: #105299
[davidak@gaming:~]$ io.elementary.code --help
[WARNING 00:54:22.856048] [dbind] Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-qPxE1QbwSH: Connection refused
Usage:
io.elementary.code [OPTION…] File
Help Options:
-h, --help Show help options
--help-all Show all help options
--help-gtk Show GTK+ Options
Application Options:
-t, --new-tab New Tab
-n, --new-window New Window
-v, --version Print version info and exit
-s, --set=plugin Set of plugins
--display=DISPLAY X display to use
- system:
"x86_64-linux"
- host os:
Linux 5.8.18, NixOS, 20.09.1721.896270d629e (Nightingale)
- multi-user?:
yes
- sandbox:
yes
- version:
nix-env (Nix) 2.3.7
- channels(root):
"home-manager-20.09, nixos-20.09.1721.896270d629e, nixos-hardware, nixos-unstable-21.03pre251123.b839d4a8557"
- nixpkgs:
/nix/var/nix/profiles/per-user/root/channels/nixos
TLDR: When trying to connect to Eduroam using Connman I get «Error: Message recipient disconnected from message bus without replying».
I know that Eduroam frequently causes problems but I couldn’t find any topic with a similar problem to mine.
I’ve set up connman according to the wiki page and created the file
/var/lib/connman/eduroam.config
with following content.
[service_eduroam]
Type=wifi
Name=eduroam
EAP=peap
CACertFile=/etc/ssl/certs/Telekom.pem
Phase2=MSCHAPV2
Identify=username@ovgu.de
Passphrase=password
This is according to the recommendations of my university (page is in german).
The same settings (peap, MSCHAPV2, same Telekom.pem, same Username@ovgu.de and password) work fine on my Android device, which I’m currently using for USB-tethering.
I’m running the following commands when trying to connect to eduroam:
$ connmanctl
connmanctl> enable wifi
Error wifi: Already enabled
connmanctl> agent on
Agent registered
connmanctl> scan wifi
Scan completed for wifi
connmanctl> services
*AO Wired ethernet_aa8f44bbdc32_cable
*A OvGU-802.1X wifi_94b86d1efbf4_4f7647552d3830322e3158_managed_ieee8021x
*A eduroam wifi_94b86d1efbf4_656475726f616d_managed_ieee8021x
OvGU-Guest wifi_94b86d1efbf4_4f7647552d4775657374_managed_none
[...]
connmanctl> connect wifi_94b86d1efbf4_656475726f616d_managed_ieee8021x
Error /net/connman/service/wifi_94b86d1efbf4_656475726f616d_managed_ieee8021x: Message recipient disconnected from message bus without replying
OvGU-802.1X is another WPA2-enterprise network with the same setup. When trying to connect to it, I get the same error.
Connecting using connman-gtk also doesn’t work.
$ connman-gtk
** (connman-gtk:32468): WARNING **: 13:40:16.299: failed to toggle connection state: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
** (connman-gtk:32468): WARNING **: 13:40:16.308: failed to scan wifi: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
In case you need additional information about the network card:
$ lspci -s 02: -vv
02:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
Subsystem: Intel Corporation Dual Band Wireless-AC 8265
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 139
Region 0: Memory at e1200000 (64-bit, non-prefetchable) [size=8K]
Capabilities: <access denied>
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi
$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp0s31f6: <NO-CARRIER,BROADCAST,MULTICAST,DYNAMIC,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
link/ether 54:ee:75:fe:2b:3f brd ff:ff:ff:ff:ff:ff
3: wlp2s0: <NO-CARRIER,BROADCAST,MULTICAST,DYNAMIC,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether 94:b8:6d:1e:fb:f4 brd ff:ff:ff:ff:ff:ff
5: usb0: <BROADCAST,MULTICAST,DYNAMIC,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000
link/ether aa:8f:44:bb:dc:32 brd ff:ff:ff:ff:ff:ff
inet 192.168.42.17/24 brd 192.168.42.255 scope global usb0
valid_lft forever preferred_lft forever
inet6 fe80::a88f:44ff:febb:dc32/64 scope link
valid_lft forever preferred_lft forever
If you know logs that could be helpful, please tell me.
Edit:
I’ve found this information in journalctl:
Nov 19 13:40:05 elda connmand[32255]: Connection Manager version 1.36
Nov 19 13:40:05 elda connmand[32255]: Adding configuration eduroam
Nov 19 13:40:05 elda connmand[32255]: Unknown configuration key Identify in [service_eduroam]
Nov 19 13:40:05 elda connmand[32255]: Adding service configuration eduroam
Nov 19 13:40:05 elda connmand[32255]: Adding configuration OvGU-802.1X
Nov 19 13:40:05 elda connmand[32255]: Unknown configuration key Identify in [service_OvGU-802.1X]
Nov 19 13:40:05 elda connmand[32255]: Adding service configuration OvGU-802.1X
Nov 19 13:40:05 elda connman-vpnd[479]: usb0 {update} flags 36866 <DOWN>
Nov 19 13:40:05 elda connman-vpnd[479]: usb0 {newlink} index 5 address AA:8F:44:BB:DC:32 mtu 1500
Nov 19 13:40:05 elda connman-vpnd[479]: usb0 {newlink} index 5 operstate 2 <DOWN>
Nov 19 13:40:05 elda audit: NETFILTER_CFG table=filter family=2 entries=4
Nov 19 13:40:05 elda audit[32255]: SYSCALL arch=c000003e syscall=54 success=yes exit=0 a0=9 a1=0 a2=40 a3=561ccc71a8a0 items=0 ppid=1 pid=32255 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="connmand" exe="/usr/bin/connmand" key=(null)
Nov 19 13:40:05 elda audit: PROCTITLE proctitle=2F7573722F62696E2F636F6E6E6D616E64002D6E
Nov 19 13:40:05 elda audit: NETFILTER_CFG table=mangle family=2 entries=6
Nov 19 13:40:05 elda audit[32255]: SYSCALL arch=c000003e syscall=54 success=yes exit=0 a0=9 a1=0 a2=40 a3=561ccc71ca40 items=0 ppid=1 pid=32255 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="connmand" exe="/usr/bin/connmand" key=(null)
Nov 19 13:40:05 elda audit: PROCTITLE proctitle=2F7573722F62696E2F636F6E6E6D616E64002D6E
Nov 19 13:40:05 elda audit: NETFILTER_CFG table=nat family=2 entries=5
Nov 19 13:40:05 elda audit[32255]: SYSCALL arch=c000003e syscall=54 success=yes exit=0 a0=9 a1=0 a2=40 a3=561ccc71d4d0 items=0 ppid=1 pid=32255 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="connmand" exe="/usr/bin/connmand" key=(null)
Nov 19 13:40:05 elda audit: PROCTITLE proctitle=2F7573722F62696E2F636F6E6E6D616E64002D6E
Nov 19 13:40:05 elda connmand[32255]: Checking loopback interface settings
Nov 19 13:40:05 elda connmand[32255]: System hostname is elda
Nov 19 13:40:05 elda connmand[32255]: __connman_inet_get_pnp_nameservers: Cannot read /proc/net/pnp Failed to open file “/proc/net/pnp”: No such file or directory
Nov 19 13:40:05 elda connmand[32255]: Cannot create /var/run/connman/resolv.conf falling back to /etc/resolv.conf
Nov 19 13:40:05 elda connmand[32255]: lo {newlink} index 1 address 00:00:00:00:00:00 mtu 65536
Nov 19 13:40:05 elda connmand[32255]: lo {newlink} index 1 operstate 0 <UNKNOWN>
Nov 19 13:40:05 elda connmand[32255]: enp0s31f6 {create} index 2 type 1 <ETHER>
Nov 19 13:40:05 elda connmand[32255]: enp0s31f6 {update} flags 36867 <UP>
Nov 19 13:40:05 elda connmand[32255]: enp0s31f6 {newlink} index 2 address 54:EE:75:FE:2B:3F mtu 1500
Nov 19 13:40:05 elda connmand[32255]: enp0s31f6 {newlink} index 2 operstate 2 <DOWN>
Nov 19 13:40:05 elda connmand[32255]: Adding interface enp0s31f6 [ ethernet ]
Nov 19 13:40:05 elda connmand[32255]: wlp2s0 {create} index 3 type 1 <ETHER>
Nov 19 13:40:05 elda connmand[32255]: wlp2s0 {update} flags 36867 <UP>
Nov 19 13:40:05 elda connmand[32255]: wlp2s0 {newlink} index 3 address 94:B8:6D:1E:FB:F4 mtu 1500
Nov 19 13:40:05 elda connmand[32255]: wlp2s0 {newlink} index 3 operstate 2 <DOWN>
Nov 19 13:40:05 elda connmand[32255]: Adding interface wlp2s0 [ wifi ]
Nov 19 13:40:05 elda connmand[32255]: usb0 {create} index 5 type 1 <ETHER>
Nov 19 13:40:05 elda connmand[32255]: usb0 {RX} 10789 packets 8829439 bytes
Nov 19 13:40:05 elda connmand[32255]: usb0 {TX} 8794 packets 1341059 bytes
Nov 19 13:40:05 elda connmand[32255]: usb0 {update} flags 36866 <DOWN>
Nov 19 13:40:05 elda connmand[32255]: usb0 {newlink} index 5 address AA:8F:44:BB:DC:32 mtu 1500
Nov 19 13:40:05 elda connmand[32255]: usb0 {newlink} index 5 operstate 2 <DOWN>
Nov 19 13:40:05 elda connman-vpnd[479]: usb0 {update} flags 102467 <UP,RUNNING,LOWER_UP>
Nov 19 13:40:05 elda connman-vpnd[479]: usb0 {newlink} index 5 address AA:8F:44:BB:DC:32 mtu 1500
Nov 19 13:40:05 elda connman-vpnd[479]: usb0 {newlink} index 5 operstate 0 <UNKNOWN>
Nov 19 13:40:05 elda connmand[32255]: Adding interface usb0 [ ethernet ]
Nov 19 13:40:05 elda connmand[32255]: usb0 {RX} 10789 packets 8829439 bytes
Nov 19 13:40:05 elda connmand[32255]: usb0 {TX} 8794 packets 1341059 bytes
Nov 19 13:40:05 elda connmand[32255]: usb0 {update} flags 102467 <UP,RUNNING,LOWER_UP>
Nov 19 13:40:05 elda connmand[32255]: usb0 {newlink} index 5 address AA:8F:44:BB:DC:32 mtu 1500
Nov 19 13:40:05 elda connmand[32255]: usb0 {newlink} index 5 operstate 0 <UNKNOWN>
Nov 19 13:40:05 elda connmand[32255]: Failed to set hostname to elda
Nov 19 13:40:05 elda connmand[32255]: usb0 {add} route fe80:: gw :: scope 0 <UNIVERSE>
Nov 19 13:40:05 elda connmand[32255]: usb0 {add} address 192.168.42.17/24 label usb0 family 2
Nov 19 13:40:05 elda connmand[32255]: usb0 {add} route 192.168.42.0 gw 0.0.0.0 scope 253 <LINK>
Nov 19 13:40:05 elda connmand[32255]: usb0 {add} route 192.168.42.129 gw 0.0.0.0 scope 253 <LINK>
Nov 19 13:40:05 elda connmand[32255]: usb0 {add} route 0.0.0.0 gw 192.168.42.129 scope 0 <UNIVERSE>
Nov 19 13:40:05 elda connmand[32255]: usb0 {add} route 0.0.0.0 gw 192.168.42.129 scope 0 <UNIVERSE>
Nov 19 13:40:05 elda connmand[32255]: usb0 {add} route 192.168.42.0 gw 0.0.0.0 scope 253 <LINK>
Nov 19 13:40:05 elda connmand[32255]: usb0 {add} route 192.168.42.129 gw 0.0.0.0 scope 253 <LINK>
Nov 19 13:40:05 elda connmand[32255]: usb0 {add} route 212.227.81.55 gw 192.168.42.129 scope 0 <UNIVERSE>
Nov 19 13:40:06 elda connmand[32255]: usb0 {del} route 212.227.81.55 gw 192.168.42.129 scope 0 <UNIVERSE>
Nov 19 13:40:16 elda connmand[32255]: Aborting (signal 11) [/usr/bin/connmand]
Nov 19 13:40:16 elda connmand[32255]: ++++++++ backtrace ++++++++
Nov 19 13:40:16 elda connmand[32255]: #0 0x7fba1028ae00 in /usr/lib/libc.so.6
Nov 19 13:40:16 elda connmand[32255]: #1 0x7fba103b2715 in /usr/lib/libc.so.6
Nov 19 13:40:16 elda connmand[32255]: #2 0x7fba105f1ec5 in /usr/lib/libdbus-1.so.3
Nov 19 13:40:16 elda connmand[32255]: #3 0x7fba105de009 in /usr/lib/libdbus-1.so.3
Nov 19 13:40:16 elda connmand[32255]: #4 0x7fba105e0725 in /usr/lib/libdbus-1.so.3
Nov 19 13:40:16 elda connmand[32255]: #5 0x561cca8cb625 in /usr/bin/connmand
Nov 19 13:40:16 elda connmand[32255]: #6 0x561cca8b0b39 in /usr/bin/connmand
Nov 19 13:40:16 elda connmand[32255]: #7 0x561cca8cb788 in /usr/bin/connmand
Nov 19 13:40:16 elda connmand[32255]: #8 0x561cca8b0fb5 in /usr/bin/connmand
Nov 19 13:40:16 elda connmand[32255]: #9 0x561cca8ac577 in /usr/bin/connmand
Nov 19 13:40:16 elda connmand[32255]: #10 0x561cca8ad2de in /usr/bin/connmand
Nov 19 13:40:16 elda connmand[32255]: #11 0x561cca8ed82b in /usr/bin/connmand
Nov 19 13:40:16 elda connmand[32255]: #12 0x7fba105e573e in /usr/lib/libdbus-1.so.3
Nov 19 13:40:16 elda connmand[32255]: #13 0x7fba105d5dfd in /usr/lib/libdbus-1.so.3
Nov 19 13:40:16 elda connmand[32255]: #14 0x561cca8e9ed1 in /usr/bin/connmand
Nov 19 13:40:16 elda connmand[32255]: #15 0x7fba1067d271 in /usr/lib/libglib-2.0.so.0
Nov 19 13:40:16 elda connmand[32255]: #16 0x7fba1067ef89 in /usr/lib/libglib-2.0.so.0
Nov 19 13:40:16 elda connmand[32255]: #17 0x7fba1067ff62 in /usr/lib/libglib-2.0.so.0
Nov 19 13:40:16 elda connmand[32255]: #18 0x561cca864c8b in /usr/bin/connmand
Nov 19 13:40:16 elda connmand[32255]: #19 0x7fba10277223 in /usr/lib/libc.so.6
Nov 19 13:40:16 elda connmand[32255]: +++++++++++++++++++++++++++
Nov 19 13:40:16 elda systemd[1]: connman.service: Main process exited, code=exited, status=1/FAILURE
Nov 19 13:40:16 elda systemd[1]: connman.service: Failed with result 'exit-code'.
Nov 19 13:40:16 elda audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=connman comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Nov 19 13:40:16 elda kernel: kauditd_printk_skb: 17 callbacks suppressed
Nov 19 13:40:16 elda kernel: audit: type=1131 audit(1542631216.273:144): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=connman comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Nov 19 13:40:16 elda systemd[1]: connman.service: Service RestartSec=100ms expired, scheduling restart.
Nov 19 13:40:16 elda systemd[1]: connman.service: Scheduled restart job, restart counter is at 4.
Nov 19 13:40:16 elda kernel: audit: type=1130 audit(1542631216.596:145): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=connman comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 19 13:40:16 elda kernel: audit: type=1131 audit(1542631216.596:146): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=connman comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 19 13:40:16 elda audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=connman comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 19 13:40:16 elda audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=connman comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 19 13:40:16 elda systemd[1]: Stopped Connection service.
Nov 19 13:40:16 elda systemd[1]: Starting Connection service...
Nov 19 13:40:16 elda systemd[1]: Started Connection service.
Nov 19 13:40:16 elda audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=connman comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 19 13:40:16 elda connmand[32691]: Connection Manager version 1.36
Nov 19 13:40:16 elda kernel: audit: type=1130 audit(1542631216.713:147): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=connman comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 19 13:40:16 elda connmand[32691]: Adding configuration eduroam
Nov 19 13:40:16 elda connmand[32691]: Unknown configuration key Identify in [service_eduroam]
Nov 19 13:40:16 elda connmand[32691]: Adding service configuration eduroam
Nov 19 13:40:16 elda connmand[32691]: Adding configuration OvGU-802.1X
Nov 19 13:40:16 elda connmand[32691]: Unknown configuration key Identify in [service_OvGU-802.1X]
Nov 19 13:40:16 elda connmand[32691]: Adding service configuration OvGU-802.1X
Nov 19 13:40:16 elda connman-vpnd[479]: usb0 {update} flags 36866 <DOWN>
Nov 19 13:40:16 elda connman-vpnd[479]: usb0 {newlink} index 5 address AA:8F:44:BB:DC:32 mtu 1500
Nov 19 13:40:16 elda connman-vpnd[479]: usb0 {newlink} index 5 operstate 2 <DOWN>
Nov 19 13:40:16 elda audit: NETFILTER_CFG table=filter family=2 entries=4
Nov 19 13:40:16 elda audit[32691]: SYSCALL arch=c000003e syscall=54 success=yes exit=0 a0=9 a1=0 a2=40 a3=56030c6ce8a0 items=0 ppid=1 pid=32691 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="connmand" exe="/usr/bin/connmand" key=(null)
Nov 19 13:40:16 elda audit: PROCTITLE proctitle=2F7573722F62696E2F636F6E6E6D616E64002D6E
Nov 19 13:40:16 elda kernel: audit: type=1325 audit(1542631216.730:148): table=filter family=2 entries=4
Nov 19 13:40:16 elda kernel: audit: type=1300 audit(1542631216.730:148): arch=c000003e syscall=54 success=yes exit=0 a0=9 a1=0 a2=40 a3=56030c6ce8a0 items=0 ppid=1 pid=32691 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="connmand" exe="/usr/bin/connmand" key=(null)
Nov 19 13:40:16 elda kernel: audit: type=1327 audit(1542631216.730:148): proctitle=2F7573722F62696E2F636F6E6E6D616E64002D6E
Nov 19 13:40:16 elda audit: NETFILTER_CFG table=mangle family=2 entries=6
Nov 19 13:40:16 elda audit[32691]: SYSCALL arch=c000003e syscall=54 success=yes exit=0 a0=9 a1=0 a2=40 a3=56030c6d0a40 items=0 ppid=1 pid=32691 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="connmand" exe="/usr/bin/connmand" key=(null)
Nov 19 13:40:16 elda audit: PROCTITLE proctitle=2F7573722F62696E2F636F6E6E6D616E64002D6E
Nov 19 13:40:16 elda kernel: audit: type=1325 audit(1542631216.736:149): table=mangle family=2 entries=6
Nov 19 13:40:16 elda kernel: audit: type=1300 audit(1542631216.736:149): arch=c000003e syscall=54 success=yes exit=0 a0=9 a1=0 a2=40 a3=56030c6d0a40 items=0 ppid=1 pid=32691 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="connmand" exe="/usr/bin/connmand" key=(null)
Nov 19 13:40:16 elda kernel: audit: type=1327 audit(1542631216.736:149): proctitle=2F7573722F62696E2F636F6E6E6D616E64002D6E
Nov 19 13:40:16 elda audit: NETFILTER_CFG table=nat family=2 entries=5
Nov 19 13:40:16 elda audit[32691]: SYSCALL arch=c000003e syscall=54 success=yes exit=0 a0=9 a1=0 a2=40 a3=56030c6d14d0 items=0 ppid=1 pid=32691 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="connmand" exe="/usr/bin/connmand" key=(null)
Nov 19 13:40:16 elda audit: PROCTITLE proctitle=2F7573722F62696E2F636F6E6E6D616E64002D6E
Nov 19 13:40:16 elda connmand[32691]: Checking loopback interface settings
Nov 19 13:40:16 elda connmand[32691]: System hostname is elda
Nov 19 13:40:16 elda connmand[32691]: __connman_inet_get_pnp_nameservers: Cannot read /proc/net/pnp Failed to open file “/proc/net/pnp”: No such file or directory
Nov 19 13:40:16 elda connmand[32691]: Cannot create /var/run/connman/resolv.conf falling back to /etc/resolv.conf
Nov 19 13:40:16 elda connmand[32691]: lo {newlink} index 1 address 00:00:00:00:00:00 mtu 65536
Nov 19 13:40:16 elda connmand[32691]: lo {newlink} index 1 operstate 0 <UNKNOWN>
Nov 19 13:40:16 elda connmand[32691]: enp0s31f6 {create} index 2 type 1 <ETHER>
Nov 19 13:40:16 elda connmand[32691]: enp0s31f6 {update} flags 36867 <UP>
Nov 19 13:40:16 elda connmand[32691]: enp0s31f6 {newlink} index 2 address 54:EE:75:FE:2B:3F mtu 1500
Nov 19 13:40:16 elda connmand[32691]: enp0s31f6 {newlink} index 2 operstate 2 <DOWN>
Nov 19 13:40:16 elda connmand[32691]: Adding interface enp0s31f6 [ ethernet ]
Nov 19 13:40:16 elda connmand[32691]: wlp2s0 {create} index 3 type 1 <ETHER>
Nov 19 13:40:16 elda connmand[32691]: wlp2s0 {update} flags 36867 <UP>
Nov 19 13:40:16 elda connmand[32691]: wlp2s0 {newlink} index 3 address 94:B8:6D:1E:FB:F4 mtu 1500
Nov 19 13:40:16 elda connmand[32691]: wlp2s0 {newlink} index 3 operstate 2 <DOWN>
Nov 19 13:40:16 elda connmand[32691]: Adding interface wlp2s0 [ wifi ]
Nov 19 13:40:16 elda connmand[32691]: usb0 {create} index 5 type 1 <ETHER>
Nov 19 13:40:16 elda connmand[32691]: usb0 {RX} 10845 packets 8839323 bytes
Nov 19 13:40:16 elda connmand[32691]: usb0 {TX} 8885 packets 1358038 bytes
Nov 19 13:40:16 elda connmand[32691]: usb0 {update} flags 36866 <DOWN>
Nov 19 13:40:16 elda connmand[32691]: usb0 {newlink} index 5 address AA:8F:44:BB:DC:32 mtu 1500
Nov 19 13:40:16 elda connmand[32691]: usb0 {newlink} index 5 operstate 2 <DOWN>
Nov 19 13:40:16 elda connman-vpnd[479]: usb0 {update} flags 102467 <UP,RUNNING,LOWER_UP>
Nov 19 13:40:16 elda connman-vpnd[479]: usb0 {newlink} index 5 address AA:8F:44:BB:DC:32 mtu 1500
Nov 19 13:40:16 elda connman-vpnd[479]: usb0 {newlink} index 5 operstate 0 <UNKNOWN>
Nov 19 13:40:16 elda connmand[32691]: Adding interface usb0 [ ethernet ]
Nov 19 13:40:16 elda connmand[32691]: usb0 {RX} 10845 packets 8839323 bytes
Nov 19 13:40:16 elda connmand[32691]: usb0 {TX} 8885 packets 1358038 bytes
Nov 19 13:40:16 elda connmand[32691]: usb0 {update} flags 102467 <UP,RUNNING,LOWER_UP>
Nov 19 13:40:16 elda connmand[32691]: usb0 {newlink} index 5 address AA:8F:44:BB:DC:32 mtu 1500
Nov 19 13:40:16 elda connmand[32691]: usb0 {newlink} index 5 operstate 0 <UNKNOWN>
Nov 19 13:40:16 elda connmand[32691]: usb0 {add} route fe80:: gw :: scope 0 <UNIVERSE>
Nov 19 13:40:16 elda connmand[32691]: Failed to set hostname to elda
Nov 19 13:40:16 elda connmand[32691]: usb0 {add} address 192.168.42.17/24 label usb0 family 2
Nov 19 13:40:16 elda connmand[32691]: usb0 {add} route 192.168.42.0 gw 0.0.0.0 scope 253 <LINK>
Nov 19 13:40:16 elda connmand[32691]: usb0 {add} route 192.168.42.129 gw 0.0.0.0 scope 253 <LINK>
Nov 19 13:40:16 elda connmand[32691]: usb0 {add} route 0.0.0.0 gw 192.168.42.129 scope 0 <UNIVERSE>
Nov 19 13:40:16 elda connmand[32691]: usb0 {add} route 212.227.81.55 gw 192.168.42.129 scope 0 <UNIVERSE>
Nov 19 13:40:18 elda connmand[32691]: usb0 {del} route 212.227.81.55 gw 192.168.42.129 scope 0 <UNIVERSE>
Nov 19 13:40:46 elda audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 19 13:40:46 elda kernel: kauditd_printk_skb: 3 callbacks suppressed
Nov 19 13:40:46 elda kernel: audit: type=1131 audit(1542631246.826:151): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Last edited by Anaeijon (2018-11-19 13:08:27)
- Forum
- The Ubuntu Forum Community
- Ubuntu Official Flavours Support
- Desktop Environments
- [ubuntu] DBus error org.freedesktop.DBus.Error.NoReply: Message did not receive a reply
-
DBus error org.freedesktop.DBus.Error.NoReply: Message did not receive a reply
When trying to connect my iPhone via USB I get the error:
Unable to Mount Brads iPhone:
DBus error org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
I searched on google and came to a Mandriva thread and the solution was because the user had 4G of RAM the install attempted to run/use the server repositories/files instead of the desktops. Could this be a possibility with Linux?
-
Re: DBus error org.freedesktop.DBus.Error.NoReply: Message did not receive a reply
-
Re: DBus error org.freedesktop.DBus.Error.NoReply: Message did not receive a reply
I have the same problem — all was ok until this week. Is it an update issue?
John
-
Re: DBus error org.freedesktop.DBus.Error.NoReply: Message did not receive a reply
I have the same problem — all was ok until this week. Is it an update issue?
John
-
Re: DBus error org.freedesktop.DBus.Error.NoReply: Message did not receive a reply
I’m having the same issue. Any help would be appreciated!!
-
Re: DBus error org.freedesktop.DBus.Error.NoReply: Message did not receive a reply
My daughter updated her iPhone 3G the other day and it won’t mount any longer?!
Worked fine before the update…
DBus error org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
-
Re: DBus error org.freedesktop.DBus.Error.NoReply: Message did not receive a reply
Hm at first I though it was because I did a jailbreak on my phone…But now seeing that others are having the same issue I know it can’t be that.
-
Re: DBus error org.freedesktop.DBus.Error.NoReply: Message did not receive a reply
I found this site here and it sugested the following terminal commands:
Code:
sudo add-apt-repository ppa:pmcenery/ppa sudo apt-get update sudo apt-get dist-upgrade
It worked for me.
-
Re: DBus error org.freedesktop.DBus.Error.NoReply: Message did not receive a reply
Originally Posted by animaex
I found this site here and it sugested the following terminal commands:
Code:
sudo add-apt-repository ppa:pmcenery/ppa sudo apt-get update sudo apt-get dist-upgrade
It worked for me.
I didn’t need the
Code:
sudo add-apt-repository ppa:pmcenery/ppa
Update and dist-upgrade was enough to get it working for me.
apt-get moo
-
Re: DBus error org.freedesktop.DBus.Error.NoReply: Message did not receive a reply
This worked for me too. I still can’t seem to sync iTunes to my iPhone 4 though.
harecanadaharecanada
Ubuntu Maverick 10.10 1.5tb Hard drive 3gb RAM
Dell Inspiron 531
AMD Athlon 64×2 Dual Core Proccessor 5600+
Bookmarks
Bookmarks

Posting Permissions
Error: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected
Edit Ive moved all the logs and things that served as a diary of investigating this problem, from looking at gdbus and so forth to the bottom, since I’ve found (in hindsight glaringly obivous) python errors in my syslog that correspond to every time I do an apt update — and ever since I upgraded dbus (and python3 upgraded its dbus library that same day/week)
Last resort (after investigating changes to the dbus that have been made from Oct 31 and through November. a big bunch of Python3 stuff, which has provided a bunch of dbus, moving away from 2.7? perhaps — anyway I copied my syslog, then truncated it to 0 and immediately did another apt update. Sure enough, I think these few lines may provide my best clue yet:
Check out the error! Here is my problem!!
I’ve edited the dates to make the lines shorter and easier to read (the syslog without edit is immediately below it)
This one is as above but without redactions###
For history, here is what used to be at the top of this post:
Months of fairly issue free ubuntu-ing and now I find myself asking my third question in as many days 😞 — maybe I just like your friendly open-sourced hugs🤗!
Anyway, I have started getting this error (I’ve seen it a few times, but it’s become noticable today when I have been doing more apt install than usual.) I don’t think its a problem cauthissed by apt , but it is appearing sometimes when doing apt .
I keep getting this error message Error: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying in my terminal on occasion, and as I say, I notice it when I’m doing things with apt update or apt install . Again, I don’t think (but cannot confirm) that it is limited to doing apt stuff, and I think it would be good for me to try to determine whether that is or is not true. I’m sure I have seen it at other times, but don’t have any terminal history to hand with an example.
Anyway, here are some of examples today of when it appeared: (edit I put the error message inside » quotes so that it appears green with shell code highlighting — wasn’t sure how else to make it stand out better)
Error: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
(*Removed some quoted blocks that have since been determined irrelevant/duplicated)
Whilst it might not be specifically APT causing this message, I think I have re-evaluated my position, it does have something to do with the repositories anyhow. Unrelated to investigating this, I was in the software updater and decided to open Software & Updates so that I can finally get around to removing that I tualatrix PPA, since it hasn’t been updated since like ubuntu 14 — I’ve just been too lazy thus far, and lo and hehold, what happened when I unticked it? (1) I got this pop up!
And though its not directly apt, it must have to do with the sources it tries to use. The Other Software tab, after closing this popup, it had unticked the ppa repository despite the error, so I can test the theory that this was the cause, perhaps. I’ll do some more stuff with apt shortly, and I hope not to see this error and that will prove it one way or another.
My thanks to @Rinzwind and @matigo who have made similar suggestions in the comments below relating to this particular entry in my sources.d list. I had independently started some housekeeping, and they’d made their observations in the meantime so credit where credit is due — if I’d seen their comments first, I’d have headed straight for add-apt-repository —remove (so probably wouldn’t have seen this new dialog — so with hindsight I’m glad I opened the SW Updater first, instead of re-opening this thread, elshttps://askubuntu.com/users/15811/rinzwinde I wouldn’t have gained that additional piece of evidence, relying solely on their experience for guidance. With this dialog, I can be more confident these guys «know their shizle» should they try to help me in future).
EDIT 2
Darn. False call. I disabled the tualatrix, and did a simple sudo apt update
So, no url to query, no error message 🤯 🤕 I think all I’ve proved is that apt sends a message to this service when an existing list is finished being queried. Its not actually anything to do with apt, or software update, other than thats one thing thats sending this message. Time to look in another place, such as in DBus
Since I’ve gotten my grey matter working on this stupid thing for the last few hours, I vaguely recall doing something several weeks ago that might have changed what bus I have. This was around the time I was putting Manjaro on my other, very resource limited, laptop, and might have tried to copy over something to this one that gave a performance boost. Chrome was blowing this laptop up at the time, and on the other one, even worse. Manjaro made it better, but in the end I made a bare-bones chrome for lapjaro. Now, Lapuntu might have inherited a different bus. By mistake? Maybe. Whatever was in the USB stick when I put it back over.
So, anyway, there is more than one DBus; freedesktop.org developed a free and open-source software library called libdbus; a reference implementation of the specification. This library should not be confused with D-Bus itself, as other implementations of the D-Bus specification also exist, such as GDBus (GNOME),[9] QtDBus (Qt/KDE),[10] dbus-java[11] and sd-bus (part of systemd).[12]
It appears from the error message that I am using GDBus, and I should be, right? I’m using Gnome. All is well. but if I look at my `/var/log/apt/history (having to do a bit of gunzipping here)
There a reference I didn’t expect to see, but it chimes with that vague recollection about maybe changing some bus thingy? I certainly cannot recall ever seeing this error DBus.Error.NoReply yada yada prior to the last few weeks. Investigating further (and I’ll stop updating this until I find something more concrete — I thought at least this recollection should be placed here, in case anyone has an idea)
In my /var/log/apt/term logfile, I used to see this when doing apt upgrade
And now its this:
(EDIT Taken out another large chunk of now irrelevant logs/code quotres)
Источник
Dbus error send message org freedesktop dbus error noreply
This page is for bindings authors to discuss what generic errors should be sent by the binding:
Name | Description | Comments |
ServiceUnknown | The recipient bus name is not taken | In Core |
UnknownObject | The sender has called a method on an object not exported on this connection (the service name is valid) | Used by Java |
UnknownInterface | The sender has specified an interface this object does not implement (but the object is valid) | Requested by Thiago |
UnknownMethod | The specified method is not implemented on this object (but the object and the interface names are valid) | In core |
InvalidParameters | Method was called with an invalid number or type of parameters. (Comment: org.freedesktop.DBus.Error.InvalidArgs seems more suitable for this use, especially considering there is no «parameter» in D-Bus terminology — alp) | Suggested by Matt |
Please add other errors you think should, or could possibly, be useful
- What about errors in executing the method within the binding? There could be problems with marshalling and so on? At the moment I send an internal error with a specific message, should there be a generic error type? — Matt
- About InvalidParameters: some bindings could not implement it and use only UnknownMethod. Methods in those bindings are recognised by both the method name and signature. The bindings that support overloading through parameters are the case (C++ and Java especially).
- Objects that have children must never reply with UnknownObject.
The format of error messages
The spec suggests that error messages can contain different arguments and aren’t restricted to a single string. Do any core errors or binding errors make use of this? Would this be useful when mapping exceptions thrown by an object binding, say for the stack trace etc.?
The spec should specifically say whether the string is mandatory as the first parameter or not. It should also make it clear if more parameters are permitted or not.
Well-known core errors
This is a list of core errors for reference. They are usually kept in order because it seems the glib binding puts them in an enumeration. Are these documented anywhere?
Источник
GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying #65235
Comments
davidak commented Jul 21, 2019
Issue description
I got no output with the command io.elementary.code —version
After that commands work normally.
Steps to reproduce
not reproducible again right now
Technical details
- system: «x86_64-linux»
- host os: Linux 4.19.59, NixOS, 19.03.173165.55b8860aa20 (Koi)
- multi-user?: yes
- sandbox: yes
- version: nix-env (Nix) 2.2.2
- channels(davidak): «»
- channels(root): «nixos-19.03.173165.55b8860aa20, nixos-hardware, nixos-unstable-19.09pre185259.362be9608c3»
- nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos
The text was updated successfully, but these errors were encountered:
alexeymuranov commented Nov 25, 2019 •
I am currently getting:
Had to reboot to make it work again.
jtojnar commented Nov 25, 2019 •
Works for me under GNOME on nixos-unstable, exceptf for this hillarious gettext substitution:
Probably something environmental. Do other applications exhibit this? Are there any more details in the journal? Does it happen again after you restart the session bus using systemctl restart —user dbus (will kill your session)?
stale bot commented Jun 1, 2020
Thank you for your contributions.
This has been automatically marked as stale because it has had no activity for 180 days.
If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as «still important to me». This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity.
Here are suggestions that might help resolve this more quickly:
- Search for maintainers and people that previously touched the
related code and @ mention them in a comment. - Ask on the NixOS Discourse. 3. Ask on the #nixos channel on
irc.freenode.net.
davidak commented Jun 1, 2020
it has had no activity for 180 days.
that does not mean it’s solved. i can still reproduce it
Источник
(pulseaudio) bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply
I was looking through my logs and I found this at the top:
[pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
I have no idea what it means. My computer starts fine, and I haven’t noticed any errors so far. But just to be safe, does anyone know how to resolve this?
Also, just to be clear, I’ve read the error and I can see the ‘possible causes’ part, but I don’t know what it means by ‘remote application’ or ‘message bus security.’
1 Answer 1
The short answer is to execute the following command:
By googling around a bit I found that pulseaudio is the audio subsystem in Ubuntu nowadays, and the pactl command can be used to fiddle with its settings.
This command has quite a few subcommands, the most interesting of which is list .
By executing pactl list short you can see that there is a module that contains the word bluez in its name, and it is bluetooth related.
I am using a desktop computer which is not equipped with bluetooth, so there should be no bluetooth-related modules running.
Executing pactl unload-module for each bluetooth-related module did not work, because on reboot the modules were loaded again, and so the error appeared in the log again. One should take hint from the fact that pactl is billed as a program to «Control a running PulseAudio sound server»: it does not actually modify the persisted configuration of the sound server.
By googling around a bit more I found that PulseAudio settings are stored in some default.pa file, and I found two instances of this file on my system, a fat one under /etc/pulse/ and a skinny one under /usr/share/gdm/ .
Obviously, the fat one is global PulseAudio settings, and the skinny one is user-specific settings somehow related to the gnome desktop manager.
The contents of the user-specific default.pa were very interesting, as it contained commands to do precisely what I wanted to do: disable the bluetooth-related modules. It does not disable the bluez module per se, but by fiddling with pactl earlier I discovered that disabling the other two bluetooth-related modules has the effect of automagically also disabling the bluez module.
Only problem is, gdm’s configuration file is kind of useless to me, because it does not get executed when I log in.
By googling around even a bit more I found that the location for a user-local instance of this settings file is supposed to be
Hence, I reasoned that if I just copied gdm’s file to this location on my profile, the problem would be fixed.
And indeed it has.
For those who do not have a copy of the file with bluetooth unloading logic, here’s the section of the file (from ubuntu 20.04) which implements that functionality.
Источник
Arch Linux
You are not logged in.
#1 2014-10-13 12:04:54
[SOLVED] D-bus not working (I guess)
Hello
I got a problem when it comes to D-bus.
Neither pulseaudio nor network-manager-applet is working for me due to this error that comes up:
this is the error report from pulseaudio.
The error report from nm-applet:
when I startx I have this in the .xinitrc
I saw that this could solve it, but it did not, so I am now turning to a new post.
USB connection works, and I can get internet from USB tethering, so there should be nothing wrong with my USB busses (is not that, that D-bus controls?)
if you want more info I will answer as fast as I can
Last edited by f4rm0r (2014-10-20 13:31:09)
#2 2014-10-13 12:13:13
Re: [SOLVED] D-bus not working (I guess)
Dbus has nothing to do with usb.
Can you post the actual commands you are running and the full output? The output that is there suggests you are trying to run the program(s) as root. Is this true? Why?
«UNIX is simple and coherent. » — Dennis Ritchie, «GNU’s Not UNIX» — Richard Stallman
#3 2014-10-13 18:00:32
Re: [SOLVED] D-bus not working (I guess)
Dbus has nothing to do with usb.
Can you post the actual commands you are running and the full output? The output that is there suggests you are trying to run the program(s) as root. Is this true? Why?
when it comes to pulseaudio, I just ran «pulseaudio».
as a normal user it just comes to this:
it gives no output at all. but I can’t see anything that says that it is working either.
in my tray it says «networkManager is not running»
but the icon dissapears when I press ctrl-c.
so I tried to run as root, but nothing.
now I will try to install package «bluez5» and see if that helps.
I tried installing bluez, and I got another error:
I installed alsa instead and I got sound working.
now i just need to get nm-applet to work, or install something ele that can manage PEAP and encrypted networks
Last edited by f4rm0r (2014-10-13 18:15:29)
#4 2014-10-13 18:24:52
Re: [SOLVED] D-bus not working (I guess)
nm-applet is just an applet. You need to have NetworkManager running in order for it to do anything:
https://wiki.archlinux.org/index.php/NetworkManager
«UNIX is simple and coherent. » — Dennis Ritchie, «GNU’s Not UNIX» — Richard Stallman
#5 2014-10-14 13:45:58
Re: [SOLVED] D-bus not working (I guess)
nm-applet is just an applet. You need to have NetworkManager running in order for it to do anything:
https://wiki.archlinux.org/index.php/NetworkManager
I feel incredibly foolish for not realising that!
Anyway it is fixed now
Ty for your help!
#6 2014-10-14 14:15:34
Re: [SOLVED] D-bus not working (I guess)
No problem. Please remember to mark your thread as [SOLVED] by editting your first post to revise the title.
Also, for future reference, you will likely receive the best help here if you stick to describing the symptoms. If you wish to speculate on potential causes in an initial post, there is no harm, but the title of a thread in particularl should stick to the objectively observable symptom(s) as much as possible. This avoids any confusion due to your suspected diagnosis being incorrect. This thread, for example, has nothing to do with dbus not working (it’s about tools not being able to find their dbus ‘partners’ as the partners were not running). However a bit of the error message, or a comment about dbus connections failing would have been more accurate.
«UNIX is simple and coherent. » — Dennis Ritchie, «GNU’s Not UNIX» — Richard Stallman
Источник