as fallout from this: Gone a week, update hung, power cycled, now in emergency mode - #10 by czrpb
after logging in i am getting an error dialog saying:
Unable to get connection to the message bus session
Error spawning command line "dbus-launch --autolaunch=BLAH --binary-syntax --close-stderr": Child process exited with code 1
well, not sure if this dialog is coming this way, but i can get a very similar error via:
❯ blueman-manager ─╯
(blueman-manager:198838): dconf-WARNING **: 15:03:14.029: failed to commit changes to dconf: Error spawning command line “dbus-launch --autolaunch=3197e33cf1534d708db35f045aa26d0c --binary-syntax --close-stderr”: Child process exited with code 1
Blueman applet needs to be running
researching isnt going well . . .
Is your bluetooth functioning properly?
ugh .. im worried i am too much a newbie for linux!
so, i dont know how to answer that since before my update issue, i usually just did:
super+shift+D -> type: bluetooth -> to run the
but, because it doesnt run i researched how to run in the terminal, and hopefully that is
example of more problems which means i should probably just blow away my current install and start again:
super+shift+D -> type: assistant -> to run
gives me a dialog:
Elevated rights required for application function
running via cmd-line is no help, still gives error dialog:
❯ sudo garuda-assistant ─╯
[sudo] password for czrpb:
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
QMetaObject::connectSlotsByName: No matching signal for on_checkBox_clicked(QWidget*)
QMetaObject::connectSlotsByName: Connecting slot on_comboBox_btrfsdevice_activated() with the first of the following compatible signals: ("activated(int)", "activated(QString)")
QMetaObject::connectSlotsByName: Connecting slot on_comboBox_snapper_configs_activated() with the first of the following compatible signals: ("activated(int)", "activated(QString)")
QMetaObject::connectSlotsByName: Connecting slot on_comboBox_snapper_config_settings_activated() with the first of the following compatible signals: ("activated(int)", "activated(QString)")
QObject::connect: No such slot GarudaAssistant::rootBashFinished(int, NULL)
QObject::connect: (receiver name: 'GarudaAssistant')
pretty sure it didnt do that before my failed update . . .
Please, post your inxi -Faz
systemctl enable --now blueman-manager
In addition to the
inxi -Faz, maybe you could check
systemctl status dbus.service
and, in case of errors, start troubleshooting from there.
But this seems to be really technical stuff. Just an idea, I'm no expert there...
thx for the help!! i actually just reinstalled with the latest image. everything up and running it seems.
sure, i lost a bit of configuration, but all actual personal stuff is on a different drive yes?!!
also, upgrading this way actually results in a nicer garuda: sure
updates are supposed to do so, but the newest install definitely has a nicer feel so love it!!
is it just i get the newest cfg files? dont know, but great job!