Below is my experience. Any errors/omissions are solely mine. What, if
anything one does with this information is on them. I do everything from a
terminal.

A second experiment is listed under 'SYSTEMD' below. Other than some add-on
expected breakages, other issues are unknown. With the listed changes, the
.deb packages were compiled, but not installed by me. I make absolutely no
guarantee as to what might happen with your machine if you try this
second experiment (or the first experiment for that matter).

Suggest a backup be made before proceeding. Have another means of booting your
computer should something go wrong. Try not to do this on a production
computer.
...

Environment: Devuan Excalibur with only the default repositories enabled and
used. Work was done within the XFCE environment.

Instructions for compiling MythTV on Debian from mythtv.org are assumed, and
only changes I made are noted here.
https://wiki.mythtv.org/wiki/Installing … _on_Debian
last edited "3 May 2026"

Problem: error below returned and compile halted.
conflict between libsystemd0 and ...elogin...

I ran:

`DEBIAN_SUFFIX='devuan' ./build-debs.sh fixes/36`

   Note: this will include 'devuan' in the package names. I suggest adding your
   initials as well (Ex. devuanABC).

build-debs.sh runs `dpkg-checkbuilddeps` against debian/control. A 'zero'
return indicates all dependencies are met. We can run the above manually from
the directory we executed `build-debs.sh`

dpkg-checkbuilddeps

dpkg-checkbuilddeps: error: unmet build dependencies: build-essential:native ccache default-libmysqlclient-dev | libmysqlclient-dev
...

For me, lower down in this list is 'libsystemd-dev'. I manually installed
files listed above as user 'root' or with `sudo` in several steps until
libsystemd-dev was about the only unmet dependency left.
Note that the '|' in the output means to install either the .deb left of
the '|' or the .deb package right of '|'

I made a list of installed .deb packages to help with this task.

dpkg-query -l > myinstalled.debs.txt

I can for instance run: `grep libmysqlclient myinstalled.debs.txt`
Note the '-dev' is omitted in the search.

For '-dev' dependencies needed, this might tell you which '-dev' packages you
need. If nothing is returned, you can try to install both, and `apt` will
complain about one .deb not being found. Remove that .deb package from your
'apt install' command and try again. This is the main reason I install
dependencies slowly and resolve libsystemd-dev last; it avoids confusion.

I ran:

apt install libsystemd-dev

...
Installing:
  libsystemd-dev

Installing dependencies:
  dummy-logind  libcap-dev  libsystemd0

REMOVING:
  desktop-base  libelogind-compat  libpam-elogind  task-desktop  task-xfce-desktop

preceeded by over one hundred packages that were 'no longer required'. Note that
*desktop* files are minimal .deb packages that install other .deb packages.
Removing, for instance, task-xfce-desktop does not delete the XFCE desktop.

Note the .deb packages listed below 'Installing:', 'Installing dependencies:', and
'REMOVING:' as these changes will be later reversed.

I accepted install of libsystemd-dev. Do not log out or reboot once
libsystemd-dev is installed.

I ran `dpkg-checkbuilddeps` until its only output was a prompt return.

Now we are ready to retry the ./build-debs.sh command (See above).
This command successfully created .deb packages in the packaging/deb/
directory.

Follow the MythTV instructions for creating a repository listing and install
you desired packages. Note MythTV urges ...mythtv.list should be removed
once the packages are installed.

Reverse the changes we made to allow MythTV to compile. In my case:

apt install desktop-base  libelogind-compat  libpam-elogind  task-desktop \
 task-xfce-desktop

REMOVING:
  dummy-logind  libsystemd-dev  libsystemd0

I accepted this change, to revert changes to the computer made earlier.
-----

I ran:

apt install mythtv-frontend

(my MythTV backend runs on a systemd enabled operating system at this time).

When I first ran `mythfrontend`, it complained that the user did not have
'mythtv' in the user's groups listing. Following the prompting of the
pop-up window, this was attempted, but failed. The complaint was not
being able to run `systemctl daemon-reload`. I had to manually add 'mythtv'
to the users group (Ex. usermod -a -G mythtv myuser # subbing for myuser),
then log out for the change to be committed.

Done!
-----
SYSTEMD
I ran:

grep systemd packaging/deb/mythtv/mythtv/configure

and it listed:
--disable-systemd_notify
--disable-systemd_journal

as possible inputs to the configure script. These can be added to
'packaging/deb/debian/rules' before beginning the compile (backup the
'rules' file before changing).

Searching the 'control' file, there are two mentions of systemd:
libsystemd-dev  is within the base 'Build-Depends:'
python3-systemd is within 'Package: libmyth-python'
"This package contains files needed for some python MythTV add-ons."

So can we not build the libmyth-python package and accept loss of some MythTV
add-ons? Can we simply remove 'libsystemd-dev' as a dependency?
'libmyth-python' is listed as a dependency of 'Package: mythtv-frontend'
Lets try it!!

Backup the control file. Within the 'control' file:
Delete the 'libsystemd-dev' dependency
Delete the 'Package: libmyth-python' section (we have made a backup!)
Delete 'libmyth-python' dependency within 'Package: mythtv-frontend'
and 'Package: mythtv-backend'

Run `build-debs.sh` as indicated above

The compile ran to completion and created .deb packages. As expected,
a 'libmyth-python' .deb package was not created. I have not installed this
compile, and will not install at this time.

-----

MythTV seems tied to systemd (at least weakly). I intent to file a feature
request to add a '--disable-systemd' to the `configure` script and see if the
MythTV developers deem this something worth their time to pursue.

If the feature is accepted, I will test and report back on this post.

ALL discs are found as far as I can tell but not all Artists.
So 'We Saw A Bozo Under The Sea' is there but does not appear under Zoot Horn Rollo in Artists. No Artist appears after Terry Riley with 'In C'.

I took to working on just Tangerine Dream until I got it the way I wanted it - namely as the 5 albums Phaedra Cyclone Rubycon Ricochet Stratosfear. I used MusicBrainz Picard to change the album from The Virgin Years to Phaedra etc. I did it on my MacBook Pro running Devuan Ceres because it is a lot faster than the Kunbus with its little Raspberry Pi!
Once I know everything is as it should be the USB drive will get transferred to the Kunbus, and Plan A is to copy the Jellyfin databases over to the Kunbus rather than do a slow re-scan.

I did a full backup of all the audio files and then formatted the USB drive to ext4. I'm working alphabetically backwards as I load up the USB drive so I can spot exactly where things go wrong and fix it. Zoot Horn Rollo is there!

to make the duration more tolerable we moved as much as possible to cold-storage/verified-backups to eliminate the "Save/Restore Evolution Data" workload.

keep us posted on your progress!

As well on SteveM's git repository, the dependency conflict with gir1.2-gtk-2.0 to also keep stuff like Dia around has been fixed, and can be installed alongside gir1.2-dtk.

Get the Daedalus DEBs below:

amd64 | i386

Get the Excalibur DEBs below:

amd64

i mean, writing the software i want to use is what i do when the existing software doesn't work the way i want and i cannot reconcile with the codebase to work on fixing existing software.

I use OpenRC user services to start (and supervise) dbus-daemon explicitly, so I know that it was launched with '--address ${XDG_RUNTIME_DIR:-"/run/user/$(id -u)"}/bus'. This may not be the case in your setup, which is why I said "Something along the lines of" rather than "copy-paste this".
If you're using dbus-launch, you can a: Manually ensure DBUS_SESSION_BUS_ADDRESS is already set in the environment dbus-launch runs with (and set the same for anything that needs to connect to it) b: Make sure everything that needs to connect to the session bus inherits dbus-launch's environment (since it will set DBUS_SESSION_BUS_ADDRESS itself if it is empty) or c: Use dbus-update-activation-environment as EDX-0 described above.

When you launch applications with dbus-launch or dbus-run-session, you often end up creating a new dbus session just for that application - (so it will start, but it won't be able to do IPC with anything else), or in the case of something like hyprland, starting a session but not propagating the bus address to applications started later (usually because something, like a greeter or launcher, is stripping environment). Launching subsequent applications with dbus-run-session risks starting another isolated dbus session, and you end up  back in scenario 1.

If anyone’s interested, I’d seriously recommend taking advantage now instead of waiting. Personally, I’ve seen this as one of the only games where regular players can still make cash almost for free just by understanding the system and staying active.

This breakdown explains the active pool pretty well:
https://blog.cs2.ad/cs2-active-drop-pool/

Surprised? Not.

Its linux baby, here nothing works good
Bugs at linux have name - "features"

picom --backend glx --vsync & xrandr --output eDP-1 --brightness 0.7 --mode 1280x720 & dwm