Preface: Issue in Figure
If you are moving to non-systemd environment, you might notice that your window manager might behave differently. I mean, there is no such different with Desktop Environment, but Window Manager under Desktop Manager does not contain dbus session. In short dbus session is not working under certain circumstances,
no removable drive,
other partition not shown,
operation permitted for root only,
and so on.
It will be easier to figure out the issue with figures.
Thunar without dbus
Thunar with dbus
There are at least three solutions to run dbus to suit your needs.
Window Manager Session
System Wide, under Desktop Manager
This is not really a desktop tutorial, but more like a system case.
All you need is to type
But typing repetitively over and over again, could be cumbersome.
Window Manager Session
Another temporary workaround is to mess
that is located in
This is also not the best practice, since I have to edit every Window Manager after installation procedure.
Init 3: Using startx
dbus run without any issue in this init.
I can run
init 3 after login.
And voila, the mighty thunar will show my storage device.
In Slackware you can use
that will create
.xsession in home directory.
Do not forget to remove .xsession if you want to use init 4
Here is an example of
It also has
dbus-launch in it.
No need to alter anything. Everything works well here.
Init 4: Using Desktop Manager
This is where the most issue happened. The solution depends on the Desktop Manager.
Intead of different DM, I also give different tiers [DM - distro - init]:
LightDM – Slackware - SysVinit.
SDDM - Artix - OpenRC
SLiM - Devuan - SysVinit
Before you begin, make sure dbus service is actively running.
LightDM on Slackware
Activate the messagebus daemon first.
Now we can simply use LightDM’s Xsession wrapper,
by altering the
(the last line).
I’m using LightDM - Slackware - SysVinit.
You can switch to
init 3 and switchback to
Or just kill the DM.
SDDM on Artix
There is also similar file in SDDM,
I’m using SDDM - Artix - OpenRC.
Restart using daemon manager.
Note that this sddm run under
SLiM (or XDM) on Devuan
There is not much to say with this Devuan. dbus with WMs works properly without further configuration.
Unless you do not turn off the dbus daemon, your dbus will be fine.
If you have policy issue with message ‘not authorized to perform’
while mounting device form Thunar,
you can run
lxsession from terminal to enable it.
Thank you to folks at Slackware Indonesia Telegram Group, for being a good company while solving these dbus issues.
Your ideas pointing to right direction.
Thank you for reading
- February 2018
- Telegram Bot - Manual Page
- Telegram Bot - Makefile
- Telegram Bot - BASH Group Tools
- Telegram Bot - BASH Option Argument
- Telegram Bot - BASH Script
- Telegram Bot - BASH CLI
- Telegram Bot - Getting Token
- Telegram Bot - Overview
- Distribution - Slackware Post Install Log
- Using Git for Working Between Computer
- Bootstrap CLI Webtools - Part Three
- Bootstrap CLI Webtools - Part Two
- Bootstrap CLI Webtools - Part One
- Bootstrap CLI Webtools - Summary
- Using Cloud for Daily Activity
- File System - Trapped in Snapper Rollback
- Jekyll Installation on openSUSE
- openSUSE Tumbleweed Tiling Experience