You are not logged in.
Pages: 1
Hello all
running into a few issues when trying to run a few applications.
Looks like I am getting some dbus issues:
[chris@arch:~][1]$ sudo pamac-manager
** (pamac-manager:10241): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-O2nkjAnxmn: Connection refused
(pamac-manager:10241): GLib-GIO-CRITICAL **: g_dbus_proxy_new_sync: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
(pamac-manager:10241): GLib-GIO-CRITICAL **: g_dbus_proxy_get_name_owner: assertion 'G_IS_DBUS_PROXY (proxy)' failed
[chris@arch:~][130]$ nemo
** (nemo:10263): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-O2nkjAnxmn: Connection refused
I was told told I was having permission errors, but I am able to use sudo command. When I run sudo find / -name "pacnew" I get:
find: ‘/run/user/1000/gvfs’: Permission denied
This is on a clean install of arch. Im not sure what is causing it or if I did something to cause this (pretty sure it could be the case)
Offline
What WM/DE are you using and how do you start X?
Note that you shouldn't start graphical programs with sudo, use gksu or kdesu.
edit: damn typos that invert the meaning.
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
I use lightdm GM to start either i3 or cinnamon
Offline
I confirm this bug, if you downgrade LightDM to version 1.20.0, then errors do not occur. I'm using LightDM + MATE.
Last edited by Infernales (2017-03-30 13:49:20)
Offline
hmm wouldn't think it would be a LightDM bug, has to do with permissions
Offline
Why not, DMs often screw up such things. In any case, it is very easy to test - just start with startx.
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
Why not, DMs often screw up such things. In any case, it is very easy to test - just start with startx.
Nope, same thing
Offline
/tmp/dbus-O2nkjAnxmn indicates a temporary dbus session address it should be of the form /run/user/$(id -u)/bus
Is the DBUS_SESSION_BUS_ADDRESS environment variable set?
Have you worked through General_troubleshooting#Session_permissions?
Is dbus-launch being used in any initialization files?
Offline
Note that you should start graphical programs with sudo, use gksu or kdesu.
I think you dropped a "not" somewhere
My Arch Linux Stuff • Forum Etiquette • Community Ethos - Arch is not for everyone
Offline
/tmp/dbus-O2nkjAnxmn indicates a temporary dbus session address it should be of the form /run/user/$(id -u)/bus
Is the DBUS_SESSION_BUS_ADDRESS environment variable set?
Have you worked through General_troubleshooting#Session_permissions?
Is dbus-launch being used in any initialization files?
How would I check this? I am sorta new
Offline
Is the DBUS_SESSION_BUS_ADDRESS environment variable set?
$ printenv DBUS_SESSION_BUS_ADDRESS
Have you worked through General_troubleshooting#Session_permissions?
Commands are on the wiki page .
Is dbus-launch being used in any initialization files?
Unless you added dbus-launch to any files the answer is probably no.
Offline
loqs wrote:Is the DBUS_SESSION_BUS_ADDRESS environment variable set?
$ printenv DBUS_SESSION_BUS_ADDRESS
loqs wrote:Have you worked through General_troubleshooting#Session_permissions?
Commands are on the wiki page .
loqs wrote:Is dbus-launch being used in any initialization files?
Unless you added dbus-launch to any files the answer is probably no.
Thanks!
I ran printenv DBUS_SESSION_BUS_ADDRESS and the output is unix:path=/run/user/1000/bus
mkinitcpio -p linux >> $HOME/issue.log gives me a few errors
[chris@arch:~]$ mkinitcpio -p linux >> $HOME/issue.log
==> ERROR: Unable to write to /boot/initramfs-linux.img
==> ERROR: Unable to write to /boot/initramfs-linux-fallback.img
running loginctl show-session $XDG_SESSION_ID contains Remote: No and Active: Yes
Is dbus-launch being used in any initialization files? No, you are correct
my log: https://ptpb.pw/pIeJ
Last edited by Chr|s (2017-03-31 01:04:07)
Offline
You used nemo in the first post as an example but does nemo function as expected?
If you run pamac-manager with gksudo or kdesu does it function as expected?
Edit:
Does the following run without the warning?
$ NO_AT_BRIDGE=1 nemo
Last edited by loqs (2017-03-31 10:17:42)
Offline
You used nemo in the first post as an example but does nemo function as expected?
If you run pamac-manager with gksudo or kdesu does it function as expected?
Edit:
Does the following run without the warning?$ NO_AT_BRIDGE=1 nemo
Running that command gives me no warnings
Offline
You can either set the Environment_variable or ignore the warning from nemo with respect to pamac-manager it should resolve the first warning.
Offline
You can either set the Environment_variable or ignore the warning from nemo with respect to pamac-manager it should resolve the first warning.
So its not really a permission issue ? I just hate seeing errors or warnings lol
Offline
So its not really a permission issue ? I just hate seeing errors or warnings lol
The output related to the accessibility is not a permissions issue.
Offline
Pages: 1