sddm

sddm: setting image as background does not save full path

Mon, 02/13/2017 - 15:14 - augustin

I use systemsettings > login > sddm settings and configure a custom image as background.
I select the image from a file using the dialog, then save.

But when I manually look at configuration file ( breeze # vi theme.conf.user), only the file name is saved, but not the full path.
I actually have to edit the conf file manually myself for it to work.

sddm: Image: Error decoding: file:video.mp4: Unsupported image format

Mon, 02/13/2017 - 14:40 - augustin

After having added a video as background:

# sudo gpasswd -a sddm video
$ sddm-greeter --test --theme /usr/share/sddm/themes/breeze/
[22:36:22.426] (WW) GREETER: file:///usr/share/sddm/themes/breeze//Background.qml:37:5: QML Image: Error decoding: file://...video.avi: Unsupported image format

sddm: remember last user in tty

Sun, 02/05/2017 - 08:18 - augustin

An apparent regression compared to KDM in KDE 4, is that KDM used to remember which user last logged in on the current tty.

I regularly open two, sometimes 3 sessions, and they are usually ordered in the same way.
I open my main session in tty7. I would often open a secondary session in tty8, and more rarely a 3rd one in tty8.
The main session in tty7 would always be the same user.
Most of the time, the session in tty8 would be a different user than in tty7, but the same one.

sddm: Add screen locker

Sun, 02/05/2017 - 08:16 - augustin

see:
https://github.com/sddm/sddm/issues/773

sddm upgrade: missing logs and missing maui theme

Wed, 02/01/2017 - 06:50 - augustin

Last night, I did an emerge update @world, which included an upgrade of sddm

I think it's this package x11-misc/sddm, but I'm not sure.
Installed versions: 0.14.0-r2(12:07:07 30/01/17)(consolekit pam -systemd)

In any case, when I logged in this morning, I was greeted by the sddm session manager with the message:
"The current theme cannot be loaded due to the errors below. please select another theme."
"file:///usr/share/sddm/themes/maui/Main.qml: file not found."

I know where and how to configure the sddm theme.

The problems are:

/etc/sddm.conf

Main configuration file for the SDDM display manager.
See:
http://linux.overshoot.tv/wiki/simple_desktop_display_manager_sddm

Theme configuration:

[Theme]
# Current theme name
Current=maui

Themes are located within /usr/share/sddm/themes/.
Each subdirectory represents a theme and should contain a file Main.qml.
E.g. /usr/share/sddm/themes/maui/Main.qml

Simple Desktop Display Manager (SDDM)

https://en.wikipedia.org/wiki/Simple_Desktop_Display_Manager

http://linux.overshoot.tv/etc/sddm.conf
http://linux.overshoot.tv/usr/share/sddm
http://linux.overshoot.tv/x11-misc/sddm
https://github.com/sddm/sddm

Theming

https://github.com/sddm/sddm/wiki/Theming

sddm-greeter --test --theme /usr/share/sddm/themes/breeze/

Configuration

/etc/conf.d/xdm:

DISPLAYMANAGER="sddm"

The variables in your theme's theme.conf.user override those in theme.conf.

Video background

/usr/share/sddm/

http://linux.overshoot.tv/wiki/simple_desktop_display_manager_sddm

Themes

Themes are located within /usr/share/sddm/themes/.
Each subdirectory represents a theme and should contain a file Main.qml.
E.g. /usr/share/sddm/themes/maui/Main.qml

Configuration

http://linux.overshoot.tv/etc/sddm.conf

/usr/share/sddm/scripts/Xsetup
To use a dvorak keyboard in sddm, you can add a line in the above file:
# setxkbmap "dvorak"
http://linux.overshoot.tv/wiki/keyboard

KDE will not start (blackscreen)

When KDE won't start, it may be due to a huge variety of reasons.
Use this page to document further the debugging workflow that will lead to the proper solution for each case.

Is X working?

Signs that X Server is working: You can see a black screen, and maybe a mouse cursor shaped like an X, but nothing else.
In tty1, you can do:

# ps aux | grep tty7

and see that X.org is running.
If you kill the X.org process, it restarts automatically, with the same results.
Thus, X.org is properly running and is not the culprit.

Check /var/log/

sddm

KDE and systemd

logind

logind depends on systemd.
The bug below shows that KDE developers fully expect users to use logind and systemd:

Bug 360489 -  kscreenlocker suggests running "loginctl unlock-sessions" even though I don't use systemd
https://bugs.kde.org/show_bug.cgi?id=360489  

A reply from a KDE developer says that they won't fix this for users not using systemd:

Martin Gräßlin 2016-03-14 :

Syndicate content