could not start d-bus can you call qbus

Questions specific to the KDE DE go here
Gazzzman
Posts: 6
Joined: 20 Oct 2017 09:25

could not start d-bus can you call qbus

Postby Gazzzman » 20 Oct 2017 09:37

Hi everyone!
I am new hear, but have been using Solydxk for a couple of years.
yesterday, I decided (maybe stupidly) to run the update script to 9
three quarters through the upgrade I started getting "cannot write to disk /dev/sda5" read only filesystem and then it crashed
I had to restart using a live CD and chkdsk /dev/sda5
it sorted several errors then completed
upon restart I had a partially broken version of 8
I then ran "sudo apt-get --configure -a" and the upgrade continued, completing with no further incident.
upon reboot I get to the gui login screen, put in my credentials. and i get a box saying "could not start d-bus can you call qbus" if I click ok, it goes back to login
any thoughts?
Gazzzman

User avatar
ilu
Posts: 1941
Joined: 09 Oct 2013 12:45

Re: could not start d-bus can you call qbus

Postby ilu » 20 Oct 2017 10:42

We need some info about your system. Try to log into the console with ctrl-alt-f1. If that's not possible, these commands should also work after booting into the live ISO.

Code: Select all

inxi -Fxz
df --output=source,fstype,ipcent,size,pcent,file,target
ls -l /etc/init.d
journalctl | grep dbus*
It seems that this error can be caused by a lot of different reasons, among them errors in the kde start scripts (unlikely), installing certain buggy packages (https://forums.opensuse.org/showthread. ... -qdbus-qt5) and by file corruption (likely in your case).

Gazzzman
Posts: 6
Joined: 20 Oct 2017 09:25

Re: could not start d-bus can you call qbus

Postby Gazzzman » 20 Oct 2017 12:56

Hi ilu!
thanks for your help!
I have temporarily installed icewm and that has at least enabled me to get the browser and some bits running :)

here is the info..
I have a nasty suspicion you are going to tell me to backup my home directory and start again :(

Code: Select all

rodger@solydxk-dee ~ $ inxi -Fxz
System:    Host: solydxk-dee Kernel: 4.9.0-4-amd64 x86_64 (64 bit gcc: 6.3.0) Desktop: IceWM 1.3.8+mod+20161220
           Distro: SolydXK
Machine:   Device: server Mobo: Tyan model: S2915 v: REFERENCE BIOS: Phoenix v: 1.01B.2915 date: 12/19/2006
CPU(s):    2 Dual core AMD Opteron 2218 HEs (-HT-SMP-) cache: 4096 KB
           flags: (lm nx sse sse2 sse3 svm) bmips: 20906
           clock speeds: max: 2613 MHz 1: 2613 MHz 2: 2613 MHz 3: 2613 MHz 4: 2613 MHz
Graphics:  Card: NVIDIA G71GL [Quadro FX 1500] bus-ID: 06:00.0
           Display Server: X.Org 1.19.2 driver: nvidia Resolution: 1280x1024@60.02hz
           GLX Renderer: Quadro FX 1500/PCIe/SSE2 GLX Version: 2.1.2 NVIDIA 304.135 Direct Rendering: Yes
Audio:     Card NVIDIA MCP55 High Definition Audio driver: snd_hda_intel bus-ID: 00:06.1
           Sound: Advanced Linux Sound Architecture v: k4.9.0-4-amd64
Network:   Card-1: NVIDIA MCP55 Ethernet driver: forcedeth port: 3808 bus-ID: 00:08.0
           IF: eth1 state: down mac: <filter>
           Card-2: NVIDIA MCP55 Ethernet driver: forcedeth port: 3810 bus-ID: 00:09.0
           IF: eth2 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives:    HDD Total Size: 2000.4GB (1.9% used)
           ID-1: /dev/sdb model: SAMSUNG_HD103UJ size: 1000.2GB
           ID-2: /dev/sdc model: ST3500630NS size: 500.1GB
           ID-3: /dev/sda model: MM0500EANCR size: 500.1GB
Partition: ID-1: / size: 96G used: 15G (17%) fs: ext4 dev: /dev/sda2
           ID-2: /home size: 122G used: 19G (17%) fs: ext4 dev: /dev/sda3
           ID-3: swap-1 size: 2.14GB used: 0.00GB (0%) fs: swap dev: /dev/sdb5
Sensors:   System Temperatures: cpu: 45.0C mobo: N/A gpu: 0.0:55C
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 212 Uptime: 29 min Memory: 672.2/16051.1MB Init: systemd runlevel: 5 Gcc sys: 6.3.0
           Client: Shell (bash 4.4.121) inxi: 2.3.5 
rodger@solydxk-dee ~ $ 

Code: Select all

df --output=source,fstype,ipcent,size,pcent,file,target
Filesystem     Type     IUse% 1K-blocks Use% File Mounted on
udev           devtmpfs    1%   8170288   0% -    /dev
tmpfs          tmpfs       1%   1643636   1% -    /run
/dev/sda2      ext4        7% 100660656  17% -    /
tmpfs          tmpfs       1%   8218172   1% -    /dev/shm
tmpfs          tmpfs       1%      5120   1% -    /run/lock
tmpfs          tmpfs       1%   8218172   0% -    /sys/fs/cgroup
/dev/sda3      ext4        3% 126937884  17% -    /home
tmpfs          tmpfs       1%   1643632   1% -    /run/user/1000

Code: Select all

ls -l /etc/init.d
total 440
-rwxr-xr-x 1 root root 2269 Sep 20  2016 acpid
-rwxr-xr-x 1 root root 5336 Feb  1  2016 alsa-utils
-rwxr-xr-x 1 root root 2014 May 21  2012 anacron
-rwxr-xr-x 1 root root 1071 Nov 23  2009 atd
-rwxr-xr-x 1 root root 2401 Dec  7  2013 avahi-daemon
-rwxr-xr-x 1 root root 1322 May 22  2013 binfmt-support
-rwxr-xr-x 1 root root 2948 Aug 18  2014 bluetooth
-rwxr-xr-x 1 root root 1276 Aug 31  2012 bootlogs
-rwxr-xr-x 1 root root 1248 Apr 21  2014 bootmisc.sh
-rwxr-xr-x 1 root root 3807 Feb 12  2017 checkfs.sh
-rwxr-xr-x 1 root root 1072 Apr 21  2014 checkroot-bootclean.sh
-rwxr-xr-x 1 root root 9353 Feb 12  2017 checkroot.sh
-rwxr-xr-x 1 root root 7692 May 26  2016 clamav-freshclam
-rwxr-xr-x 1 root root 1232 Apr  7  2017 console-setup.sh
-rwxr-xr-x 1 root root 2489 May 15  2010 cpufrequtils
-rwxr-xr-x 1 root root 3049 Oct 25  2014 cron
-rwxr-xr-x 1 root root  937 Mar  3  2014 cryptdisks
-rwxr-xr-x 1 root root  896 Nov 28  2012 cryptdisks-early
-rwxr-xr-x 1 root root 2816 Mar 12  2014 cups
-rwxr-xr-x 1 root root 1961 Mar 11  2014 cups-browsed
-rwxr-xr-x 1 root root 2813 Nov  6  2014 dbus
-rwxr-xr-x 1 root root 1172 Feb 15  2014 dns-clean
-rwxr-xr-x 1 root root 6754 Apr 18  2017 exim4
-rwxr-xr-x 1 root root 1553 Aug 27  2013 fancontrol
-rwxr-xr-x 1 root root 2914 May 27  2011 fuse
-rwxr-xr-x 1 root root 1604 Feb  2  2017 gdomap
-rwxr-xr-x 1 root root 4052 Mar 20  2014 gpsd
-rwxr-xr-x 1 root root 1336 Apr 21  2014 halt
-rwxr-xr-x 1 root root 2363 Jul 17 14:31 haveged
-rwxr-xr-x 1 root root 3060 Oct 30  2011 hddtemp
-rwxr-xr-x 1 root root 1423 Aug 15  2010 hostname.sh
-rwxr-xr-x 1 root root 3809 Mar 22  2017 hwclock.sh
-rwxr-xr-x 1 root root 2448 Dec 30  2016 irqbalance
-rwxr-xr-x 1 root root 1479 May 19  2016 keyboard-setup.sh
-rwxr-xr-x 1 root root 1300 Apr 21  2014 killprocs
-rwxr-xr-x 1 root root 2044 Dec 26  2016 kmod
-rwxr-xr-x 1 root root 2610 Jul 25  2011 lightdm
-rwxr-xr-x 1 root root 1625 Oct 31  2016 lircd
-rwxr-xr-x 1 root root 1540 Oct 31  2016 lircmd
-rwxr-xr-x 1 root root  883 May 17  2016 lm-sensors
-rwxr-xr-x 1 root root 6912 May  6  2012 loadcpufreq
-rwxr-xr-x 1 root root  695 Jan 17  2015 lvm2
-rwxr-xr-x 1 root root  571 Mar 17  2017 lvm2-lvmetad
-rwxr-xr-x 1 root root  586 Mar 17  2017 lvm2-lvmpolld
-rwxr-xr-x 1 root root 2241 Jul 14  2014 minissdpd
-rwxr-xr-x 1 root root  995 Aug 31  2012 motd
-rwxr-xr-x 1 root root  677 Apr 21  2014 mountall-bootclean.sh
-rwxr-xr-x 1 root root 2301 Feb 12  2017 mountall.sh
-rwxr-xr-x 1 root root 1461 Apr 21  2014 mountdevsubfs.sh
-rwxr-xr-x 1 root root 1564 Apr 21  2014 mountkernfs.sh
-rwxr-xr-x 1 root root  685 Apr 21  2014 mountnfs-bootclean.sh
-rwxr-xr-x 1 root root 2456 Apr 21  2014 mountnfs.sh
-rwxr-xr-x 1 root root 4597 Sep 16  2016 networking
-rwxr-xr-x 1 root root 1757 May 19  2014 network-manager
-rwxr-xr-x 1 root root 5658 Aug 13  2014 nfs-common
-rwxr-xr-x 1 root root 2064 Sep 25 14:11 nmbd
-rwxr-xr-x 1 root root 9138 Jul 18 21:15 openvpn
-rwxr-xr-x 1 root root 3720 Jan 16  2013 pcscd
-rwxr-xr-x 1 root root 1366 Dec 18  2016 plymouth
-rwxr-xr-x 1 root root  752 Apr 25  2014 plymouth-log
-rwxr-xr-x 1 root root  612 Jan 27  2014 pppd-dns
-rwxr-xr-x 1 root root 1191 Nov 22  2016 procps
-rwxr-xr-x 1 root root 6290 Feb 12  2017 rc
-rwxr-xr-x 1 root root  820 Apr 21  2014 rc.local
-rwxr-xr-x 1 root root  117 Feb 12  2017 rcS
-rw-r--r-- 1 root root 2427 Feb 12  2017 README
-rwxr-xr-x 1 root root  661 Apr 21  2014 reboot
-rwxr-xr-x 1 root root 1042 Jul 14  2013 rmnologin
-rwxr-xr-x 1 root root 2358 May  5 18:46 rpcbind
-rwxr-xr-x 1 root root 4355 Jul 10  2014 rsync
-rwxr-xr-x 1 root root 2868 Jan 18  2017 rsyslog
-rwxr-xr-x 1 root root 1348 Sep 25 14:11 samba
-rwxr-xr-x 1 root root 2389 Sep 25 14:11 samba-ad-dc
-rwxr-xr-x 1 root root 2330 May 21 09:04 saned
-rwxr-xr-x 1 root root 1222 Apr  3  2017 screen-cleanup
-rwxr-xr-x 1 root root 1808 Mar 14  2017 sddm
-rwxr-xr-x 1 root root 3207 Apr 21  2014 sendsigs
-rwxr-xr-x 1 root root  597 Apr 21  2014 single
-rw-r--r-- 1 root root 1087 Feb 12  2017 skeleton
-rwxr-xr-x 1 root root 3505 Oct 21  2014 smartmontools
-rwxr-xr-x 1 root root 2005 Sep 25 14:11 smbd
-rwxr-xr-x 1 root root 2117 Aug  2 01:42 speech-dispatcher
-rwxr-xr-x 1 root root 4033 Jun 18 01:08 ssh
-rwxr-xr-x 1 root root  731 Oct  9  2013 sudo
-rwxr-xr-x 1 root root 2522 May 21  2010 timidity
-rwxr-xr-x 1 root root 6087 Jul  5 21:31 udev
-rwxr-xr-x 1 root root 2083 Jan 10  2017 ufw
-rwxr-xr-x 1 root root 2748 Feb 12  2017 umountfs
-rwxr-xr-x 1 root root 2202 Apr 21  2014 umountnfs.sh
-rwxr-xr-x 1 root root 1234 Feb 12  2017 umountroot
-rwxr-xr-x 1 root root 1391 May  6 11:57 unattended-upgrades
-rwxr-xr-x 1 root root 3111 Apr  9  2012 urandom
-rwxr-xr-x 1 root root 1306 Mar 22  2017 uuidd
-rwxr-xr-x 1 root root 6452 Nov 29  2016 virtualbox
-rwxr-xr-x 1 root root 1612 Sep 25 14:11 winbind
-rwxr-xr-x 1 root root 2757 Nov 23  2016 x11-common
rodger@solydxk-dee ~ $ 

Code: Select all

journalctl | grep dbus*
Oct 20 13:16:36 solydxk-dee dbus[699]: [system] Successfully activated service 'org.freedesktop.systemd1'
Oct 20 13:16:41 solydxk-dee dbus[699]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service'
Oct 20 13:16:42 solydxk-dee dbus[699]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Oct 20 13:16:42 solydxk-dee dbus[699]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Oct 20 13:16:43 solydxk-dee dbus[699]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service'
Oct 20 13:16:43 solydxk-dee dbus[699]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Oct 20 13:16:44 solydxk-dee dbus[699]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Oct 20 13:16:44 solydxk-dee dbus[699]: [system] Successfully activated service 'org.freedesktop.hostname1'
Oct 20 13:16:45 solydxk-dee dbus[699]: [system] Successfully activated service 'org.freedesktop.ColorManager'
Oct 20 13:16:52 solydxk-dee dbus[699]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Oct 20 13:16:53 solydxk-dee pulseaudio[944]: [pulseaudio] server-lookup.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
Oct 20 13:16:53 solydxk-dee pulseaudio[944]: [pulseaudio] main.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
Oct 20 13:17:01 solydxk-dee dbus-daemon[1495]: Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service'
Oct 20 13:17:01 solydxk-dee dbus-daemon[1495]: Successfully activated service 'org.a11y.Bus'
Oct 20 13:17:01 solydxk-dee dbus-daemon[1495]: Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service'
Oct 20 13:17:02 solydxk-dee dbus-daemon[1495]: Successfully activated service 'org.gtk.vfs.Daemon'
Oct 20 13:17:04 solydxk-dee dbus[699]: [system] Activating via systemd: service name='org.freedesktop.ConsoleKit' unit='console-kit-daemon.service'
Oct 20 13:17:05 solydxk-dee dbus[699]: [system] Successfully activated service 'org.freedesktop.ConsoleKit'
Oct 20 13:17:17 solydxk-dee dbus[699]: [system] Failed to activate service 'org.bluez': timed out
Oct 20 13:17:17 solydxk-dee dbus[699]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service'
Oct 20 13:17:17 solydxk-dee dbus[699]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Oct 20 13:18:24 solydxk-dee dbus-daemon[2466]: Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service'
Oct 20 13:18:24 solydxk-dee dbus-daemon[2466]: Successfully activated service 'org.gtk.vfs.Daemon'
Oct 20 13:18:37 solydxk-dee dbus-daemon[2466]: Activating service name='org.gnome.GConf'
Oct 20 13:18:37 solydxk-dee dbus-daemon[2466]: Successfully activated service 'org.gnome.GConf'
Oct 20 13:18:45 solydxk-dee dbus[699]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Oct 20 13:19:10 solydxk-dee dbus[699]: [system] Failed to activate service 'org.bluez': timed out
Oct 20 13:37:28 solydxk-dee dbus-daemon[2466]: Activating via systemd: service name='org.gtk.vfs.UDisks2VolumeMonitor' unit='gvfs-udisks2-volume-monitor.service'
Oct 20 13:37:28 solydxk-dee dbus[699]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service'
Oct 20 13:37:28 solydxk-dee dbus[699]: [system] Successfully activated service 'org.freedesktop.UDisks2'
Oct 20 13:37:28 solydxk-dee dbus-daemon[2466]: Successfully activated service 'org.gtk.vfs.UDisks2VolumeMonitor'
Oct 20 13:37:28 solydxk-dee dbus-daemon[2466]: Activating via systemd: service name='org.gtk.vfs.GPhoto2VolumeMonitor' unit='gvfs-gphoto2-volume-monitor.service'
Oct 20 13:37:28 solydxk-dee dbus-daemon[2466]: Successfully activated service 'org.gtk.vfs.GPhoto2VolumeMonitor'
Oct 20 13:37:28 solydxk-dee dbus-daemon[2466]: Activating via systemd: service name='org.gtk.vfs.MTPVolumeMonitor' unit='gvfs-mtp-volume-monitor.service'
Oct 20 13:37:28 solydxk-dee dbus-daemon[2466]: Successfully activated service 'org.gtk.vfs.MTPVolumeMonitor'
Oct 20 13:37:28 solydxk-dee dbus-daemon[2466]: Activating via systemd: service name='org.gtk.vfs.AfcVolumeMonitor' unit='gvfs-afc-volume-monitor.service'
Oct 20 13:37:28 solydxk-dee dbus-daemon[2466]: Successfully activated service 'org.gtk.vfs.AfcVolumeMonitor'
Oct 20 13:37:28 solydxk-dee dbus-daemon[2466]: Activating via systemd: service name='org.gtk.vfs.GoaVolumeMonitor' unit='gvfs-goa-volume-monitor.service'
Oct 20 13:37:28 solydxk-dee dbus-daemon[2466]: Successfully activated service 'org.gtk.vfs.GoaVolumeMonitor'
Oct 20 13:43:16 solydxk-dee dbus-daemon[2466]: Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service'
Oct 20 13:43:16 solydxk-dee dbus-daemon[2466]: Successfully activated service 'org.a11y.Bus'
Oct 20 13:43:19 solydxk-dee dbus[699]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service'
Oct 20 13:43:19 solydxk-dee dbus[699]: [system] Successfully activated service 'org.freedesktop.UPower

User avatar
ilu
Posts: 1941
Joined: 09 Oct 2013 12:45

Re: could not start d-bus can you call qbus

Postby ilu » 20 Oct 2017 16:14

I've formatted the code for you, please have a look what I did, in order to do it yourself next time - it's much easier to read, isn't it?

A backup is always a very good idea. But I wouldn't do a complete reinstall just yet. Some people solved the problem by reinstalling x11, kde and (maybe) qt. It can't hurt to try that.

/etc/init.d looks correct. In the df output I'm missing the sda5 that had the error. Are those all partitions?

Did you do the systemctl output under icewm? That won't help because that system started up ok and the error will not be present. All sources say that the problem has something to do with KDE, so you will have to systemctl | grep without icewm. At least I think so. You could also try to grep for "err".

Gazzzman
Posts: 6
Joined: 20 Oct 2017 09:25

Re: could not start d-bus can you call qbus

Postby Gazzzman » 24 Oct 2017 14:39

Hi there ilu
thanks for all your help!
because I needed the PC for work, in the end, I just backed up my home directory, and reinstalled!
I am beginning to regret the whole episode now LOL
version 9 runs considerably slower, and seems to have more "issues" than version 8.
its probably just something I have done wrong (probably "lots")
but processor usage is in the high 80% area constantly, and everything is very slow!
when I have caught up on my work, I will have to look properly, looks like plasma and video driver issues..
for now, it is at least working!
thanks again!
Love and peace
Gazzzman

User avatar
ilu
Posts: 1941
Joined: 09 Oct 2013 12:45

Re: could not start d-bus can you call qbus

Postby ilu » 24 Oct 2017 20:02

Your processor is - if I'm not mistaken - from 2007. That's much too old for the new KDE even if it comes with a twin. I don't think you'll get satisfying results with SolydK9. Either stay with SolydK8 - which I wouldn't do for a professional system - or switch to SolydX9. SolydX doesn't have the bells and whistles SolydK has but it will run sufficiently fast.

Gazzzman
Posts: 6
Joined: 20 Oct 2017 09:25

Re: could not start d-bus can you call qbus

Postby Gazzzman » 25 Oct 2017 12:50

hi there iLu
again, thanks for your help!

hmm!
to be honest that surprises me a little..
I have no difficulties with this machine running 6 copies of windows 7 simultaneously in ProxMox
or Ubuntu 17.10
we "are" talking old but pretty reasonable processors..
anyhow, I suspect I will be reverting to 8, as it seems much more stable, and mature..
on a separate note, what happened to Linux?
it used to be, that feature for feature, the hardware requirements were a lot less than Windows. yet I am really struggling with this,
and W10 zips along with very low loading on the same machine..
what am I missing?
I have several of these Tyan thunder boards with twin opterons and 16GB of RAM mostly running Server 2012 and ProxMox
I think if the newest version of KDE is "this" resource hungry, we would be better off with "Unity" LOL

User avatar
ilu
Posts: 1941
Joined: 09 Oct 2013 12:45

Re: could not start d-bus can you call qbus

Postby ilu » 25 Oct 2017 15:27

I don't use KDE but I think KDE Plasma and Unity are in the same "resource hoggers" league. They are also heavy in the graphics department. I don't have any experience with your kind of machine, so I don't know ... I just thought that before you sink to much time into maybe useless debugging I should say something.

Gazzzman
Posts: 6
Joined: 20 Oct 2017 09:25

Re: could not start d-bus can you call qbus

Postby Gazzzman » 26 Oct 2017 08:46

Hi ilu!
thanks for your help my friend..
sorry if my vented frustration seemed to be aimed at you!
that wasn't the case at all, and, I really appreciate the time and effort you have taken.
I think my frustration is aimed at much bigger issues, like the direction "all" operating systems seem to be headed.
so packed with stuff we don't need (or want) facebook integration other social stuff, and way over the top GUIs
it's an operating system FFS LOL
I liked some of the things (convenience that 8 brought to the table, but 9 is just too much I think..
I "really" didn't want to start again...
when will I ever learn "if it ain't broke...."
time to look for pastures new I think :(
thanks for all your help!
love and peace
Gazzzman

User avatar
ilu
Posts: 1941
Joined: 09 Oct 2013 12:45

Re: could not start d-bus can you call qbus

Postby ilu » 26 Oct 2017 13:23

No offense taken.
Gazzzman wrote:I think my frustration is aimed at much bigger issues, like the direction "all" operating systems seem to be headed.
so packed with stuff we don't need (or want) facebook integration other social stuff, and way over the top GUIs
it's an operating system FFS LOL
If you think like that KDE Plasma is not for you. You should consider switching to XFCE. Its GUI has everything necessary but nothing more. Some remaining problems in Debian8 are fixed in 9. I'm totally content with SolydX9.

Gazzzman
Posts: 6
Joined: 20 Oct 2017 09:25

Re: could not start d-bus can you call qbus

Postby Gazzzman » 26 Oct 2017 15:48

hi again ilu !
thankyou my friend :)
I will continue looking through some live CD's and see what I find!
again, thanks :)
love and peace
Gazzzman


Return to “KDE specific (SolydK)”

Who is online

Users browsing this forum: No registered users and 1 guest