Even attempting to install a Samba server (with the command sudo apt-get install samba-server^) ends with the same level of errors. It's beta, I get it. I understand this is a beta release. Tutorial: Install Gnome Desktop and Gnome Display Manager on OpenBSD 4.7. Tutorial: Install Gnome Desktop and Gnome Display Manager on OpenBSD 4.7. Installing Gnome in OpenBSD 4.7. I have tried so many times to have a working desktop on DragonFly BSD without success that finally decided to post here in hope that somebody could have the. Tutorial: Install Gnome Desktop and Gnome Display Manager on OpenBSD 4.7. Tutorial: Install Gnome Desktop and Gnome Display Manager on OpenBSD 4.7. Installing Gnome in OpenBSD 4.7. I have tried so many times to have a working desktop on DragonFly BSD without success that finally decided to post here in hope that somebody could have the.
It is my second day in *nix world and search didn't help me to solve my issue. This question here is not relevant either.
I installed FreeBSD 11 and I installed KDE.
I tried to run it like
but turns out that I also need X server to run a UI. Ok. So I installed it like
Wine lets you run Windows software on other operating systems. With Wine, you can install and run these applications just like you would in Windows. Wine enables Linux, Mac, FreeBSD, and Solaris users to run Windows applications without a copy of Microsoft Windows. Wine is free software under constant development. Other platforms may benefit as well. How To Install A Public Git Repository On A Debian Server Git is a free distributed revision control, was initially created by Linus Torvalds for Linux kernel development. It is primarily developed on Linux, but can be used on other Unix operating systems including BSD, Solaris and Darwin. If you want to play SuperTux, TuxRacer, Chromium, or GLtron, a prompt asking if the user wants to install WINE pops up. Selecting Yes installs WINE and all of the WINE games. I am at a complete loss as to why these games are using the Windows versions when Linux versions are available.
Now I'm running X with 'startx' and then I'm running KDE with 'startkde'and I'm getting
Could not start d-bus. can you call qdbus?
How I can call qdbus? What's that?
Update 1
As was suggested I edited rc.config and added
result is the same
Update 2
I followed §5.7.2 of a handbook and /proc was mounted by adding this line to /etc/fstab:
/etc/rc.conf was edited and now has three lines:
Now if I'm running startkde I'm getting error:
I found somewhere that I need to execute
to check if plasma-desktop is installed, and looks like it is fine. Not sure about kde. Here it is:
Dragonfly Bsd Review
2 Answers
Generate an xorg.conf configuration file then copy it to your /etc/X11/xorg.conf :
To test it run
To exit press Ctrl+Alt+ Backspace then run:
Also you should have the following line under ~/.xinitrc file:
Make it executable chmod +x .xinitrc
Run startx
GAD3RGAD3RReally, if the error message asks you whether you can run the qdbus tool, you should be asking a question that tells the world what happened when you ran the qdbus tool. This question in the error message is there for a reason.
That said, there is enough here to know what is going on, and running qdbus manually will largely only confirm what this already tells us.
You do not have an /etc/machine-id file. As I said in question comments, that is a separate question all in itself. See 'Missing /etc/machine-id on FreeBSD/TrueOS/DragonFly BSD et al' and its further reading.
The problem here is that the fallback behaviour of D-Bus is malfunctioning. It is not falling back to non-systemd mechanisms at all.
There are two Desktop Bus brokers in a system running a desktop environment like GNOME or KDE. You have started the system-wide one that runs as the superuser with the dbus_enable='YES' setting in /etc/rc.conf. But you also need another per-user or per-session one that runs as the logged-in user, for these desktop environments to work. They contact the per-user or per-session broker, not the system-wide broker. They do this by being invoked with the location of that per-user or per-session broker passed to them as an environment variable.
startkde is trying to run dbus-launch to achieve this, expecting it to run a Desktop Bus broker whose location startkde can pass along to the desktop environment. It also attempts to run qdbus itself, which if a broker has not yet been launched will also attempt to run dbus-launch, passing it the --autolaunch option. As you can see from the dbus-launch manual page, this option takes a machine ID as a mandatory option argument. qdbus is trying to obtain this machine ID and pass it as that argument.
You can probably now guess what is happening.
Because qdbus has not managed to obtain a machine ID, because it is only looking in the non-existent /etc/machine-id, it is passing the --autolaunch option with an empty machine ID string to dbus-launch, which is crashing that program, which means that no per-session Desktop Bus broker is started and neither is your desktop environment attached to that broker.
To fix this, simply make /etc/machine-id be a copy of the D-Bus machine ID, using the setup-machine-id tool or move-and-symbolic-link options in the answer to 'Missing /etc/machine-id on FreeBSD/TrueOS/DragonFly BSD et al'.
You'll be glad to hear that KDE developer Lubos Lunak declared KDE's Desktop Bus broker autostart mechanism to be broken ten years ago, and no-one has since come along with a fix.
- Lubos Lunak (2007-10-22). I officially declare dbus autolaunch to be broken. . KDE/kde-workspace. GitHub.
- Bernard Mentink (2016-06-24). Trouble running KDE or Gnome. dragonfly-users.