[SOLVED] Spotify doesn't launch (probably due to D-Bus)

arash28134 · 2024-08-18 06:54:27

When I run spotify-launcher, this is the output:

[2024-08-18T06:02:38Z INFO  spotify_launcher::config] Loading configuration file at "/etc/spotify-launcher.conf"
[2024-08-18T06:02:38Z INFO  spotify_launcher] No update needed

(spotify:231640): libayatana-appindicator-WARNING **: 09:32:58.809: Unable to get the session bus: Unknown or unsupported transport “disabled” for address “disabled:”

(spotify:231640): LIBDBUSMENU-GLIB-WARNING **: 09:32:58.809: Unable to get session bus: Unknown or unsupported transport “disabled” for address “disabled:”

I'm using startx for running my wm (i3) and other scripts, this is my .xinitrc:

#!/bin/sh
if [ -d /etc/X11/xinit/xinitrc.d ] ; then
 for f in /etc/X11/xinit/xinitrc.d/?*.sh ; do
  [ -x "$f" ] && . "$f"
 done
 unset f
fi

/home/viper/.config/specific-scripts/setup_screens.sh
/home/viper/.config/scripts/setup_keyboard.sh
exec i3

Output of journalctl until when I connect to USB Tethering and start spotify-launcher

Last edited by arash28134 (2024-08-19 20:51:33)

seth · 2024-08-18 08:44:19

loginctl session-status
echo $DBUS_SESSION_BUS_ADDRESS

Though is is from LIBDBUSMENU-GLIB-WARNING ie. the thing that tries to put the application menubar into the top menubar (like on a mac)
Does this work on other clients, eg. gtk3-demo-application ?

arash28134 · 2024-08-18 09:44:28

output of loginctl

just checked, DBUS_SESSION_BUS_ADDRESS is unset. I think the issue stems from D-Bus

seth · 2024-08-18 15:24:39

DBUS_SESSION_BUS_ADDRESS is unset

Not good, but also not really explained by xinitrc or session status - do you get the same before starting X11?
What does your zshrc look like? Do you maybe use OMZ ?

arash28134 · 2024-08-18 19:09:22

I just managed to temporarily fix it by adding these lines to .xinitrc, not sure if this is the right way though:

#!/bin/sh
if [ -d /etc/X11/xinit/xinitrc.d ] ; then
 for f in /etc/X11/xinit/xinitrc.d/?*.sh ; do
  [ -x "$f" ] && . "$f"
 done
 unset f
fi

/home/viper/.config/specific-scripts/setup_screens.sh 
/home/viper/.config/scripts/setup_keyboard.sh
# Start D-Bus session
if command -v dbus-launch >/dev/null && test -z "$DBUS_SESSION_BUS_ADDRESS"; then
    eval "$(dbus-launch --sh-syntax --exit-with-session)"
fi

# Set environment variables for D-Bus
export $(dbus-launch)

exec i3

DBUS_SESSION_BUS_ADDRESS is now set to

unix:path=/tmp/dbus-HPMlpiacCX,guid=3441b5def32e77ce56d1cbd666c24452

This is now the output of spotify-launcher (and it also launches spotify)

[2024-08-18T18:59:50Z INFO  spotify_launcher::config] Loading configuration file at "/etc/spotify-launcher.conf"
[2024-08-18T18:59:50Z INFO  spotify_launcher] No update needed

Yes, I do use OMZ. This is what my .zshrc looks like:

# Path to oh-my-zsh installation.
export ZSH="$HOME/.oh-my-zsh"

ZSH_THEME=""

plugins=(
  git
  zsh-autosuggestions
  zsh-syntax-highlighting
)      

# Preferred editor for local and remote sessions
export EDITOR='vim'

ZSH_AUTOSUGGEST_HIGHLIGHT_STYLE="fg=#666666"

source $ZSH/oh-my-zsh.sh

# Aliases
alias cpf="xclip -selection c <"
alias vpn="sudo ./.config/specific-scripts/vpn.sh"
alias syu="yay -Syu"
alias s="yay -S --needed"

export PATH=$HOME/.config/rofi/scripts:$PATH

eval "$(starship init zsh)"

Last edited by arash28134 (2024-08-18 19:10:04)

seth · 2024-08-18 20:56:58

You're hiding a problem behind a bigger problem - undo that fix, comment the OMZ and starship invocation and check $DBUS_SESSION_BUS_ADDRESS before you start X11

They don't sound prone to it, but /home/viper/.config/specific-scripts/setup_screens.sh and /home/viper/.config/scripts/setup_keyboard.sh don't do any dbus related stuff?

arash28134 · 2024-08-19 08:15:24

I commented any OMZ and Starship related commands/invocation in .zshrc, removed that fix. $DBUS_SESSION_BUS_ADDRESS was indeed set to unix:path=/run/user/1000/bus, and spotify-launcher ran with no errors (in tty of course). but as soon as I started X, that variable was again unset (empty).

Not really, setup_keyboard.sh:

#!/bin/sh
setxkbmap -layout eu,ir
setxkbmap -option 'grp:alt_shift_toggle'

setup_screens.sh:

#!/bin/sh
xrandr --output DP-4 --off --output HDMI-2 --off --output HDMI-3 --off --output HDMI-4 --off --output DP-5 --mode 1920x1080 --rate 60 --right-of HDMI-1-0 --rotate normal --output DVI-D-1-0 --off --output HDMI-1-0 --primary --mode 1920x1080 --rate 60 --pos 0x0 --rotate normal --output DP-1-0 --off --output DP-1-1 --off --output DP-1-2 --off --output DP-1-3 --off --output DP-1-4 --off --output DP-1-5 --off

I also once commented these two scripts in .xinitrc and again once I started X, that environment variable was unset.

seth · 2024-08-19 08:23:45

ls /etc/X11/xinit/xinitrc.d/
pacman -Qikk systemd
cat /etc/X11/xinit/xinitrc.d/50-systemd-user.sh

Is the variable set pre startx even if you restore omz and starship invocation?

arash28134 · 2024-08-19 08:37:15

Yes, that variable is set pre startx even when I restore all omz and starship invocations

25-xlogin.sh                  50-systemd-user.sh     90xbrlapi
40-libcanberra-gtk-module.sh  80xapp-gtk3-module.sh

Name            : systemd
Version         : 256.4-1
Description     : system and service manager
Architecture    : x86_64
URL             : https://www.github.com/systemd/systemd
Licenses        : LGPL-2.1-or-later  CC0-1.0  GPL-2.0-or-later  MIT-0
Groups          : None
Provides        : nss-myhostname  systemd-tools=256.4  udev=256.4
Depends On      : systemd-libs=256.4  acl  libacl.so=1-64  bash  cryptsetup  libcryptsetup.so=12-64  dbus  dbus-units  kbd  kmod  hwdata  libcap  libcap.so=2-64  libgcrypt  libxcrypt  libcrypt.so=2-64  libidn2  lz4  pam  libelf  libseccomp  libseccomp.so=2-64  util-linux  libblkid.so=1-64  libmount.so=1-64  xz  pcre2  audit  libaudit.so=1-64  openssl  libcrypto.so=3-64  libssl.so=3-64
Optional Deps   : libmicrohttpd: systemd-journal-gatewayd and systemd-journal-remote [installed]
                  quota-tools: kernel-level quota management
                  systemd-sysvcompat: symlink package to provide sysvinit binaries [installed]
                  systemd-ukify: combine kernel and initrd into a signed Unified Kernel Image
                  polkit: allow administration as unprivileged user [installed]
                  curl: systemd-journal-upload, machinectl pull-tar and pull-raw [installed]
                  gnutls: systemd-journal-gatewayd and systemd-journal-remote [installed]
                  qrencode: show QR codes
                  iptables: firewall features [installed]
                  libarchive: convert DDIs to tarballs [installed]
                  libbpf: support BPF programs [installed]
                  libpwquality: check password quality
                  libfido2: unlocking LUKS2 volumes with FIDO2 token
                  libp11-kit: support PKCS#11 [installed]
                  tpm2-tss: unlocking LUKS2 volumes with TPM2 [installed]
Required By     : accountsservice  at-spi2-core  base  cups  gvfs  libcolord  libei  libgudev  libpulse  mdadm  mkinitcpio  phodav  polkit  rtkit  systemd-sysvcompat  vte3  xdg-desktop-portal  xdg-user-dirs  xlogin-git
Optional For    : None
Conflicts With  : nss-myhostname  systemd-tools  udev
Replaces        : nss-myhostname  systemd-tools  udev
Installed Size  : 32.43 MiB
Packager        : Christian Hesse <eworm@archlinux.org>
Build Date      : Wed 24 Jul 2024 04:38:04 PM +0330
Install Date    : Fri 26 Jul 2024 05:16:46 PM +0330
Install Reason  : Installed as a dependency for another package
Install Script  : Yes
Validated By    : Signature

warning: systemd: /var/log/journal (GID mismatch)
systemd: 1543 total files, 1 altered file

#!/bin/sh
#  SPDX-License-Identifier: LGPL-2.1-or-later
#
#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it
#  under the terms of the GNU Lesser General Public License as published by
#  the Free Software Foundation; either version 2.1 of the License, or
#  (at your option) any later version.

systemctl --user import-environment DISPLAY XAUTHORITY

if command -v dbus-update-activation-environment >/dev/null 2>&1; then
    dbus-update-activation-environment DISPLAY XAUTHORITY
fi

seth · 2024-08-19 08:41:10

cat /etc/X11/xinit/xinitrc.d/25-xlogin.sh # my money is on this one
cat /etc/X11/xinit/xinitrc.d/90xbrlapi
cat /etc/X11/xinit/xinitrc.d/80xapp-gtk3-module.sh

arash28134 · 2024-08-19 09:08:23

seth wrote:

cat /etc/X11/xinit/xinitrc.d/25-xlogin.sh # my money is on this one
cat /etc/X11/xinit/xinitrc.d/90xbrlapi
cat /etc/X11/xinit/xinitrc.d/80xapp-gtk3-module.sh

seems like you were right. why is it unsetting that variable?

#! /usr/bin/bash

# Don't use the systemd user bus for the X session
if [ "$DBUS_SESSION_BUS_ADDRESS" = "unix:path=$XDG_RUNTIME_DIR/bus" ]; then
    unset DBUS_SESSION_BUS_ADDRESS
fi

# startup script for /etc/X11/Xsession.d

prefix="/usr"
exec_prefix="${prefix}"
drivers_directory="${exec_prefix}/lib/brltty"
program_directory="${exec_prefix}/bin"
xbrlapi="$program_directory/xbrlapi"
brltty="$program_directory/brltty"

if [ -x "${xbrlapi}" ]; then
  if "${xbrlapi}" 2>/dev/null ; then
    # xbrlapi could connect to BrlAPI, try to start brltty with AtSpi2 driver.
    if [ -x "${brltty}" -a \
         -e "$drivers_directory/libbrlttybba.so" -a \
         -e "$drivers_directory/libbrlttyxa2.so" ]; then
      "${brltty}" -b ba -s no -x a2 -N 2>/dev/null
    fi
  fi
fi

#!/bin/bash
# This file is sourced by xinit(1) or a display manager's Xsession, not executed.

if [ -z "$GTK3_MODULES" ] ; then
    GTK3_MODULES="xapp-gtk3-module"
else
    GTK3_MODULES="$GTK3_MODULES:xapp-gtk3-module"
fi

export GTK3_MODULES

seth · 2024-08-19 09:12:04

why is it unsetting that variable?

Because it's stupid, the more interesting question is where it's coming from:

pacman -Qo /etc/X11/xinit/xinitrc.d/25-xlogin.sh

arash28134 · 2024-08-19 09:31:01

/etc/X11/xinit/xinitrc.d/25-xlogin.sh is owned by xlogin-git 14-1

This is from the package I used for autologging into x using systemd...

arash28134 · 2024-08-19 10:44:36

Update: I removed that package, now the problem's gone. that variable is set both pre and post startx.

But any reason why that package does that?!

seth · 2024-08-19 15:02:09

It's pointed out in teh AUR comments and the wiki, the upstream readme indicates it's fully deliberate, but that's like equipping your new airhammer model with a feature that will detect when the muzzle is pointing at your foot and trigger an autorelease. Sure, you /can/ do that…

I'm also not entirely sure what the point of the thing is, you can just agetty auto-login and conditionally exec startx *shrug*

arash28134 · 2024-08-19 16:12:16

seth wrote:

It's pointed out in teh AUR comments and the wiki, the upstream readme indicates it's fully deliberate, but that's like equipping your new airhammer model with a feature that will detect when the muzzle is pointing at your foot and trigger an autorelease. Sure, you /can/ do that…
I'm also not entirely sure what the point of the thing is, you can just agetty auto-login and conditionally exec startx *shrug*

Yeah I have no clue why I did that
Anyway, thanks a lot for the help

seth · 2024-08-19 20:48:26

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Arch Linux

#1 2024-08-18 06:54:27

[SOLVED] Spotify doesn't launch (probably due to D-Bus)

#2 2024-08-18 08:44:19

Re: [SOLVED] Spotify doesn't launch (probably due to D-Bus)

#3 2024-08-18 09:44:28

Re: [SOLVED] Spotify doesn't launch (probably due to D-Bus)

#4 2024-08-18 15:24:39

Re: [SOLVED] Spotify doesn't launch (probably due to D-Bus)

#5 2024-08-18 19:09:22

Re: [SOLVED] Spotify doesn't launch (probably due to D-Bus)

#6 2024-08-18 20:56:58

Re: [SOLVED] Spotify doesn't launch (probably due to D-Bus)

#7 2024-08-19 08:15:24

Re: [SOLVED] Spotify doesn't launch (probably due to D-Bus)

#8 2024-08-19 08:23:45

Re: [SOLVED] Spotify doesn't launch (probably due to D-Bus)

#9 2024-08-19 08:37:15

Re: [SOLVED] Spotify doesn't launch (probably due to D-Bus)

#10 2024-08-19 08:41:10

Re: [SOLVED] Spotify doesn't launch (probably due to D-Bus)

#11 2024-08-19 09:08:23

Re: [SOLVED] Spotify doesn't launch (probably due to D-Bus)

#12 2024-08-19 09:12:04

Re: [SOLVED] Spotify doesn't launch (probably due to D-Bus)

#13 2024-08-19 09:31:01

Re: [SOLVED] Spotify doesn't launch (probably due to D-Bus)

#14 2024-08-19 10:44:36

Re: [SOLVED] Spotify doesn't launch (probably due to D-Bus)

#15 2024-08-19 15:02:09

Re: [SOLVED] Spotify doesn't launch (probably due to D-Bus)

#16 2024-08-19 16:12:16

Re: [SOLVED] Spotify doesn't launch (probably due to D-Bus)

#17 2024-08-19 20:48:26

Re: [SOLVED] Spotify doesn't launch (probably due to D-Bus)

Board footer