Is it sufficient to have one of these three in Ubuntu 19.04? Is it possible to have all three and how to configure them so they were not conflicting?
Does systemd-networkd started by networking.service?
I'd like to completely avoid DM phase and run straight into desktop environment. Is there any systemd service for that?
All that is needed is to correctly restart Xorg when it is killed by Ctrl + Alt + Backspace and not restart it when it was killed by a crash or another measure. So any ready solutions would be greatly appreciated.
Notes on 19.04 and prior versions (in my particular setup):
- Autologin is broken in LXDM.
- Ctrl+Alt+Backspace is broken in LXDM.
- SDDM is broken and doesn't start.
- Good user-friendly and nicely working KDM is gone.
Since KDE display configuration is broken (and by other reasons) it is better to configure displays via xorg.conf. But after that KDE starts to display bogus dialog asking to change display mode. How to disable it completely and tell KDE to not try to reconfigure displays?
Xorg -configure generates xorg.conf but does not fill out these fields properly though it should. Are there any measures to correct them without manual editing?
After upgrade to 19.04 KDE doesn't start, just blank screen freeze. When starting KDevelop from lxde it freezes also and slowly floods the following in terminal:
org.kde.solid.udisks2: Error getting props: "org.freedesktop.DBus.Error.NoReply" "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."
org.kde.solid.udisks2: Error getting props: "org.freedesktop.DBus.Error.NoReply" "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."
org.kde.solid.udisks2: Error getting props: "org.freedesktop.DBus.Error.NoReply" "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."
...
It's worth to mention that SDDM is also broken: it just freezes without entering to graphics mode. LXDM starts though.
After ~10 minutes it finally started:
org.kde.solid.udisks2: Error getting props: "org.freedesktop.DBus.Error.NoReply" "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."
kdeinit5: preparing to launch '/usr/lib/x86_64-linux-gnu/libexec/kf5/klauncher'
kdeinit5: Launched KLauncher, pid = 29609, result = 0
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
kdeinit5: opened connection to :0.0
kdeinit5: Got EXEC_NEW '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/man.so' from launcher.
kdeinit5: preparing to launch '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/man.so'
log_kio_man: STARTING
kdeinit5: Got EXEC_NEW '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so' from launcher.
kdeinit5: preparing to launch '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so'
log_kio_man: QUrl("man://")
kdeinit5: Got EXEC_NEW '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so' from launcher.
kdeinit5: preparing to launch '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so'
log_kio_man: After if
log_kio_man: After if
log_kio_man: After if
...
Several years I notice that Ubuntu is lacking packages full descriptions. F.ex. Debian have this description for 'aptitude':
Package: aptitude (0.6.8.2-1)
terminal-based package manager
aptitude is a package manager with a number of useful features, including: a mutt-like syntax for matching packages in a flexible manner, dselect-like persistence of user actions, the ability to retrieve and display the Debian changelog of most packages, and a command-line mode similar to that of apt-get.
aptitude is also Y2K-compliant, non-fattening, naturally cleansing, and housebroken.
Ubuntu has this poor description:
terminal-based package manager
It have happened since 'precise' release. 'trusty', 'utopic' and 'vivid' are affected too. What's wrong with the package description?