DBUS_SESSION_BUS_ADDRESS in .xinitrc(solved)

[pnotz17]

so i cant get dunst to work i get critical cannot connect to dbus ive been at this for 2 days,any tips?i also read that if another daemon is running it wont work, this is a fresh system with dwm and i tried setting dbus-launch in .xinitrc and it always doesnt work although on boot dbus starts,then i checked in /etc/dbus and everything is right

https://dunst-project.org/faq/
dmesg | grep dunst returns nothing and dbus-daemon is running in htop

Code: Select all

Portage 3.0.18 (python 3.9.4-final-0, default/linux/amd64/17.1/hardened, gcc-10.3.0, glibc-2.33, 5.10.27-gentoo x86_64)
=================================================================
System uname: Linux-5.10.27-gentoo-x86_64-Intel-R-_Core-TM-2_Duo_CPU_E7500_@_2.93GHz-with-glibc2.33
KiB Mem:     2023056 total,    574268 free
KiB Swap:   10485756 total,  10485756 free
Timestamp of repository gentoo: Thu, 03 Jun 2021 19:00:01 +0000
Head commit of repository gentoo: bc50cbbfdc4aaafcbca7ed3dfc9652b93dd468bf
sh bash 5.1_p8
ld GNU ld (Gentoo 2.35.2 p1) 2.35.2
app-shells/bash:          5.1_p8::gentoo
dev-lang/perl:            5.32.1::gentoo
dev-lang/python:          3.9.4_p1::gentoo
dev-lang/rust-bin:        1.51.0::gentoo
dev-util/cmake:           3.18.5::gentoo
sys-apps/baselayout:      2.7::gentoo
sys-apps/openrc:          0.42.1-r1::gentoo
sys-apps/sandbox:         2.23::gentoo
sys-devel/autoconf:       2.13-r1::gentoo, 2.69-r5::gentoo
sys-devel/automake:       1.16.3-r1::gentoo
sys-devel/binutils:       2.35.2::gentoo
sys-devel/gcc:            10.3.0::gentoo
sys-devel/gcc-config:     2.4::gentoo
sys-devel/libtool:        2.4.6-r6::gentoo
sys-devel/make:           4.3::gentoo
sys-kernel/linux-headers: 5.10::gentoo (virtual/os-headers)
sys-libs/glibc:           2.33::gentoo
Repositories:

gentoo
    location: /var/db/repos/gentoo
    sync-type: rsync
    sync-uri: rsync://rsync.gentoo.org/gentoo-portage
    priority: -1000
    sync-rsync-verify-max-age: 24
    sync-rsync-extra-opts:
    sync-rsync-verify-metamanifest: yes
    sync-rsync-verify-jobs: 1

ACCEPT_KEYWORDS="amd64"
ACCEPT_LICENSE="* -@EULA"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=core2 -O2 -pipe"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/share/gnupg/qualified.txt"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/dconf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/sandbox.d /etc/terminfo"
CXXFLAGS="-march=core2 -O2 -pipe"
DISTDIR="/var/cache/distfiles"
EMERGE_DEFAULT_OPTS="--ask-enter-invalid --jobs=2  --load-average=2"
ENV_UNSET="CARGO_HOME DBUS_SESSION_BUS_ADDRESS DISPLAY GOBIN GOPATH PERL5LIB PERL5OPT PERLPREFIX PERL_CORE PERL_MB_OPT PERL_MM_OPT XAUTHORITY XDG_CACHE_HOME XDG_CONFIG_HOME XDG_DATA_HOME XDG_RUNTIME_DIR"
FCFLAGS="-march=core2 -O2 -pipe"
FEATURES="assume-digests binpkg-docompress binpkg-dostrip binpkg-logs candy cgroup collision-protect config-protect-if-modified distlocks downgrade-backup ebuild-locks fixlafiles ipc-sandbox merge-sync multilib-strict network-sandbox news parallel-fetch pid-sandbox preserve-libs protect-owned qa-unresolved-soname-deps sandbox sfperms strict unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync xattr"
FFLAGS="-march=core2 -O2 -pipe"
GENTOO_MIRRORS="ftp://ftp.ntua.gr/pub/linux/gentoo/ http://ftp.ntua.gr/pub/linux/gentoo/"
LANG="en_US.UTF-8 UTF-8"
LDFLAGS="-Wl,-O1 -Wl,--as-needed"
MAKEOPTS="-j3"
PKGDIR="/var/cache/binpkgs"
PORTAGE_CONFIGROOT="/"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --omit-dir-times --compress --force --whole-file --delete --stats --human-readable --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --exclude=/.git"
PORTAGE_TMPDIR="/var/tmp"
USE="acl alsa amd64 bzip2 crypt dbus elogind hardened iconv ipv6 libglvnd libtirpc multilib ncurses nls nptl openmp pam pcre pie readline seccomp split-usr ssl ssp unicode x xattr xinerama xtpax zlib" ABI_X86="64" ADA_TARGET="gnat_2018" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" APACHE2_MODULES="authn_core authz_core socache_shmcb unixd actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" CALLIGRA_FEATURES="karbon sheets words" COLLECTD_PLUGINS="df interface irq load memory rrdtool swap syslog" CPU_FLAGS_X86="mmx mmxext sse sse2" ELIBC="glibc" GPSD_PROTOCOLS="ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock greis isync itrax mtk3301 nmea ntrip navcom oceanserver oldstyle oncore rtcm104v2 rtcm104v3 sirf skytraq superstar2
timing tsip tripmate tnt ublox ubx" GRUB_PLATFORMS="pc" INPUT_DEVICES="libinput" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LIBREOFFICE_EXTENSIONS="presenter-console presenter-minimizer" LUA_SINGLE_TARGET="lua5-1" LUA_TARGETS="lua5-1" OFFICE_IMPLEMENTATION="libreoffice" PHP_TARGETS="php7-3 php7-4" POSTGRES_TARGETS="postgres10 postgres11" PYTHON_SINGLE_TARGET="python3_9" PYTHON_TARGETS="python3_9" RUBY_TARGETS="ruby26" USERLAND="GNU" VIDEO_CARDS="intel i965" XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipset ipp2p iface geoip fuzzy condition tee tarpit sysrq proto steal rawnat logmark ipmark dhcpmac delude chaos account"
Unset:  CC, CPPFLAGS, CTARGET, CXX, INSTALL_MASK, LC_ALL, LINGUAS, PORTAGE_BINHOST, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, RUSTFLAGS

[The Main Man]

Don't know what to tell you, but it works fine here.
You don't need to start dbus like that, it should start by default as a service, if not it will start automatically when something asks for it.

What happens when you start dbus-monitor in one terminal and then in other terminal execute

Code: Select all

notify-send "test"

[pnotz17]

nada....

[pnotz17]

Don't know what to tell you, but it works fine here.
You don't need to start dbus like that, it should start by default as a service, if not it will start automatically when something asks for it.

What happens when you start dbus-monitor in one terminal and then in other terminal execute

Code: Select all

notify-send "test"

Failed to open connection to session bus: Using X11 for dbus-daemon autolaunch was disabled at compile time, set your DBUS_SESSION_BUS_ADDRESS instead

[fedeliallalinea]

Can you post your .xinitrc?

[pnotz17]

Code: Select all

#!/bin/sh

# X settings
xrandr --output VGA1 --mode 1408x792_60.00 --scale-from 1920x1080 &
xset r rate 400 100

# Autostart
~/.local/bin/bars/gentoo_bar &
~/.local/bin/xsession_destroyah &
~/.fehbg &
xclickroot -r ~/git/xmenu/xmenu.sh &
dunst & 

#dwm start loop
while true; do
    /usr/local/bin/dwm 2> /dev/null
done

#eval $(dbus-launch --sh-syntax --exit-with-session) i dont think i need this...dunst doesnt work regardless

i tried re emeging dev-libs/dbus-glib tried using dunst as root tried making a script in /etc/X11/xinit/xinitrc.d to find DBUS_SESSION_BUS_ADDRESS nothing worked i even re installed gentoo from scratch, i think i haed it work in ~amd64 but that shouldn't be the issue here

[Anon-E-moose]

Don't know what to tell you, but it works fine here.
You don't need to start dbus like that, it should start by default as a service, if not it will start automatically when something asks for it.

What happens when you start dbus-monitor in one terminal and then in other terminal execute

Code: Select all

notify-send "test"

Failed to open connection to session bus: Using X11 for dbus-daemon autolaunch was disabled at compile time, set your DBUS_SESSION_BUS_ADDRESS instead

From the man page (man dbus-launch)

Code: Select all

       To start a D-Bus session within a text-mode session, do not use dbus-launch. Instead, see dbus-run-session(1).

             ## test for an existing bus daemon, just to be safe
             if test -z "$DBUS_SESSION_BUS_ADDRESS" ; then
                 ## if not found, launch a new one
                 eval `dbus-launch --sh-syntax`
                 echo "D-Bus per-session daemon address is: $DBUS_SESSION_BUS_ADDRESS"
             fi

[pnotz17]

Code: Select all

echo $DBUS_SESSION_BUS_ADDRESS
unix:abstract=/tmp/dbus-fYkcEpym9U,guid=6579a3c0f9e3fd23e6cc812860ba4a5f

Code: Select all

#dwm start loop
while true; do
	exec dbus-launch --exit-with-session dwm >/tmp/wm.log 2>&1
done

[Anon-E-moose]

Seriously this isn't rocket science.

The message from dunst was that it wanted to be either started by something like systemd or set your DBUS_SESSION_BUS_ADDRESS

The snippet of code from the man page tells you how to set DBUS_SESSION_BUS_ADDRESS

Run it in .xinitrc before you try and execute dunst.

[fedeliallalinea]

Or simply use exec dbus-launch --sh-syntax --exit-with-session dwm, see dwm wiki page