| Commit message (Collapse) | Author | Age |
... | |
|\ \
| | |
| | | |
Warn for conflict between synaptics and libinput
|
| | | |
|
|/ /
| |
| |
| | |
See #17487.
|
| |
| |
| |
| |
| |
| |
| | |
Instead of one package `extra-cmake-modules`, there is now `ecm` and
`ecmNoHooks`. The latter is used when one does not want to incur a Qt 5
dependency; it is also available as a top-level package
`extra-cmake-modules`.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
See #17054
|
| |
| |
| |
| |
| | |
This adds configuration options for automatic login and disabling the
greeter (this should avoid the dependency on gtk).
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
KDM and LightDM (at least with autologin) call the xsession-script with
two arguments: the first is the path of the xsession script itself,
while the second one are the actual arguments. The line to re-exec the
script under systemd-cat only forwarded a single argument, therefore
breaking LightDM and KDM login. This commit fixes the issue by always
forwarding all the arguments.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
We need to pass certain environment variables through the wrapper, but I
don't know how to do that yet. The setuid-root feature serves only to
hide kdeinit from the OOM killer, so this is not critical.
|
| | |
|
|\ \
| | |
| | | |
Add in PackageKit
|
| | |
| | |
| | |
| | |
| | |
| | | |
- init gnome-software for gnome3 at 3.18.3
- list gnome-software as an "optional package" for gnome3
- enable packagekit service when gnome3 is enabled
|
|\ \ \
| | | |
| | | | |
pulseaudio service: set DISPLAY
|
| | | | |
|
| |/ / |
|
|\ \ \
| | | |
| | | | |
pekwm: init at 0.1.17
|
| |/ / |
|
|/ /
| |
| |
| | |
See https://bugzilla.gnome.org/show_bug.cgi?id=764257#c12
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fixes this (line wrapped):
$ gnome-control-center
[... click on the "Color" item ...]
(gnome-control-center:3977): color-cc-panel-WARNING **: \
The name org.freedesktop.ColorManager was not provided by any .service files
With this patch applied, the above warnings are not printed and the GUI
shows some devices that can be managed (my printer and display). Without
this patch the GUI is empty (non-functional).
(cups will also complain in the journal with a similar message when
doing print jobs, without this patch.)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
...by adding system-config-printer to services.dbus.packages (if
services.printing.enable is true).
Without this patch, trying to add a printer will result in a little dialog
saying "Failed to add new printer" and gnome-control-center will print this to
the terminal (line wrapped):
(gnome-control-center:3546): printers-cc-panel-WARNING **: \
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: \
The name org.fedoraproject.Config.Printing was not provided by any .service files
system-config-printer supplies the "org.fedoraproject.Config.Printing" dbus
service, thus fixing the problem.
|
| |
| |
| |
| |
| |
| | |
xsession lines
Could be extended to other window managers/desktops as well
|
| |
| |
| |
| | |
Closes #15917
|
|\ \
| | |
| | | |
xbanish service: init at 1.4
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
Fixes #16094.
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | | |
This reverts commit 285061d50c1f0216a420a811d812e31ad4fe88a7.
|
| | | |
| | | |
| | | |
| | | | |
frameworkintegration was split with plasma-integration in Plasma 5.6.
|
| |/ / |
|
|/ / |
|
|\ \
| |/
|/|
| | |
... and fglrxCompat to maintain compatibility.
|
| |
| |
| |
| |
| | |
... and add its man page.
Now I seem to be running fine with the new server.
|
| | |
|
|\ \
| | |
| | |
| | | |
... to get the systemd update (rebuilding ~7k jobs).
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
... rather than ~/.xsession-errors. It might make sense to make this
the default, in order to eliminate ad hoc, uncentralised, poorly
discoverable log files.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This ensures that "journalctl -u display-manager" does what you would
expect in 2016. However, the main reason is to ensure that our VM
tests show the output of the X server.
A slight problem is that with KDE user switching, messages from the
various X servers end up in the same place. However, that's an
improvement over the previous situation, where the second X server
would overwrite the /var/log/X.0.log of the first. (This was caused by
the fact that we were passing a hard-coded value for -logfile.)
|
|\| |
| | |
| | |
| | | |
That's to get mesa rebuild from master, as it's nontrivial.
|
| |/
| |
| |
| |
| | |
This driver is part of xorg-server now, so we were using an outdated
version.
|
| | |
|