Like the title says.
I was doing a fresh install and decided to go with dinit this time (I used s6) just to try it out since I liked the syntax for wrtiting services, anyhow, to make a long story short:
Right after logging in for the first time I started installing stuff, and when I tried to open the system settings on plasma, it took a long while to launch, which is weird because I have and SSD and an nvme drive, and it didn't launch and only the program icon bounced but nothing happened, so I tried it again a few times and it did not launch at all as the only feedback I got was the bouncing icon.
I tried launching ksysguard just because I like its simplyicty compared to the newish system monitor program, to see what was up, and ksysguard also refused to launch.
To debug this I opened a konsole session and launched ksysguard from there and as soon as it launched, it crashed with a message that basically said to export the result of launching a program
export $(dbus-launch)
So I did, and that fixed it, but only for the duration of that knonsole session and only if I launched the programs through bash.
After giving up, I tried to shutdown the machine and I also couldn't as my system locked up for a few seconds, something 20 to 30 seconds, and when I rebooted manually by typing
reboot -r
on the terminal, when I restarted, everything seemed to have settled for a while, until I installed something that restarted the dbus service or after I opened and closed ksysguard or system settings, or any other program that needs dbus. A couple of times, even just as I logged in for the first time, the dbus just simply didn't work and apps that relied on it, despite being a freshly booted system, just didn't want to start.
Something I tested, which kind of worked, was I deactivated my swap (swapfile on /swapfile) and the dbus issue took longer to happen, but it did after a while.
I'm using xfs on root and on a home partition btw. Just in case this is useful, my partitions look like this on fstab
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/nvme0n1p2 LABEL=root
UUID=1ecf8457-014f-4d1f-8c33-6b29e9a8da99 / xfs rw,relatime,attr2,inode64,logbufs=8,logbsize=32k,noquota 0 1
# /dev/sda1 LABEL=home
UUID=a05e9c14-dda5-4178-9407-10025ab1ca2d /home xfs rw,relatime,attr2,inode64,logbufs=8,logbsize=32k,noquota 0 2
# /dev/nvme0n1p1 LABEL=BOOT
UUID=C552-822E /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
/swapfile none swap defaults 0 0
Just in case that's relevant given my experience.
Anyway, I gave up after searching only for like an hour and came up short, and installed the s6 variant of Artix again, which works flawlessly.
Anyway, what's the deal? I could re-install the dinit variant if logs are needed or something.
My hardware is:
Ryzen 7 4700u
AMD Renoir IGPU
16G of RAM
512GB nvme drive
1tb ssd
Topic: dbus issues on plasma (Read 526 times)
previous topic - next topic
