Im Using KDE for my desktop, i want to change my login screen, i've installing the themes from system settings and applied the changes. the theme is working on boot login, but somehow if i manage to lock screen it wont make a changes. im using login theme called "Sweet" .
here's code from /etc/sddm.conf.d/kde_settings.conf
[Autologin]
Relogin=false
Session=
User=
[General]
HaltCommand=/usr/bin/systemctl poweroff
RebootCommand=/usr/bin/systemctl reboot
[Theme]
Current=Sweet
[Users]
MaximumUid=60000
MinimumUid=1000
[X11]
ServerArguments=-dpi 0
i've tried to edit my /usr/lib/sddm/sddm.conf.d/default.conf to same as /etc/sddm.conf.d/kde_settings.conf then rebooted as well but same like before, it wont work on lock screen
btw, here's the output from sddm --test-mode
[kuntulsu#Harissen ~] $ sddm --test-mode
[23:24:16.675] (II) DAEMON: Initializing...
[23:24:16.713] (II) DAEMON: Starting...
[23:24:16.714] (II) DAEMON: Adding new display on vt 1 ...
[23:24:16.715] (II) DAEMON: Loading theme configuration from ""
[23:24:16.715] (II) DAEMON: Display server starting...
[23:24:16.719] (EE) DAEMON: Failed to start display server process.
[23:24:16.719] (EE) DAEMON: Display server failed to start. Exiting
Aborted (core dumped)
i have noticed that line 4, the themes is not defined but i have no idea to do to fix that, please help me
In KDE Login Screen is not the same as Lock Screen. You installed and changed your Login Screen (SDDM theme). The lockscreen is part of KDE theming, nothing to do with sddm.
You can find your lockscreen config at ~/.config/kscreenlockerrc
Related
New for viscode editor.
Environment: No Internet-access, but local network is perfect. Login in as root. Client: window-10, Server: Ubuntu 20
Description: when Carl+S is pressed, no any promotion appears, but a white dot besides the file name always showing. When close the vscode app, it tells:
Closing the window is taking a bit longer…
The following operations are still running:
- saving test files
Permission: 777 for all files and folder.
Others issues: install extensions by clicking install in SSH, showing XHR failed in bottom-left corner.
Any suggestion to solve this problem?
I am using thunderbird 91.7.0 with Ubuntu 20.04.4 LTS
I got some issues with no enough free space to make updates (I'm on a laptop) and so I used the command sudo apt autoremove and was then able to make the updates. However, since then, whenever I try to attach a file (either on a new email or in a response) in thunderbird, it instantly crashes without any warning or crash report.
I tried to launch thunderbird in safe-mode with the same result, and the message I get in the terminal as the process finishes is:
~/ $> thunderbird --safe-mode
Gtk-Message: 15:22:22.654: Failed to load module "canberra-gtk-module"
Gtk-Message: 15:22:22.656: Failed to load module "canberra-gtk-module"
[GFX1-]: glxtest: libpci missing
(thunderbird:30046): Gtk-WARNING **: 15:22:37.510: Could not load a pixbuf from icon theme.
This may indicate that pixbuf loaders or the mime database could not be found.
**
Gtk:ERROR:../src/gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: assertion failed (error == NULL): Failed to load /snap/thunderbird/195/data-dir/icons/Yaru/16x16/status/image-missing.png: Unrecognized image file format (gdk-pixbuf-error-quark, 3)
Bail out! Gtk:ERROR:../src/gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: assertion failed (error == NULL): Failed to load /snap/thunderbird/195/data-dir/icons/Yaru/16x16/status/image-missing.png: Unrecognized image file format (gdk-pixbuf-error-quark, 3)
Redirecting call to abort() to mozalloc_abort
ExceptionHandler::GenerateDump cloned child 30391
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
ExceptionHandler::WaitForContinueSignal waiting for continue signal...
Exiting due to channel error.
N.B. #1: it doesn't matter if I click on the 'attach' paperclip button or if I use the short-cut Ctrl-Shift-A command.
N.B. #2: the same occurs if I try to save an attached file from an email in my inbox, but curiously not if I just display it in a new tab in Thunderbird.
N.B. #3: everything else seems working properly...
Any help would be greatly appreciated, because I do not know how to live without TB anymore...
EDIT: here is the crash report
https://crash-stats.thunderbird.net/report/bp-c8db5ddd-d87a-4c89-b006-3c76b1220323
I'm having some problems getting the XFCE Power Manager to lock using physlock. When I set the Lock Screen on Lid Close action, upon opening my laptop lid I'm presented with an alternate lock screen, and after entering my password I get the error None of the screen lock tools ran successfully, the screen will not be locked.
However when I manually run xflock4 from a terminal emulator, physlock is correctly used.
The relevant xfconf LockCommand setting is thus:
➜ ~ xfconf-query -c xfce4-session -p /general/LockCommand -v
physlock
And my power manager settings are this:
physlock was correctly working in the past using these settings, but as this stopped working some months ago, I'm afraid I won't be much help in narrowing down what triggered the initial change.
I followed the tutorial on this site, to get my RaspberryPi NoIR-Cam running. After starting it i am retrieving the following error:
mmal: mmal_component_create_core: could not create component 'vc.ril.camera' (1)
sh: 1: /var/www/html/macros/error_hard.sh: Permission denied
mmal: mmal_vc_component_create: failed to create component 'vc.ril.camera' (1:ENOMEM)
This looks like a permission thing, but I executed
chmod u+x *.sh
just like they mentioned in the tutorial. Do you have any idea what I am doing wrong here?
Explanation: It is a permission problem, the RPi interface is trying to use the pi camera at the same time as something else, and that something else has root privileges.
I have used this interface before to stream PiCamera data into a webserver, and use three.js to render it and make it vr compatible. This RPi web interface is pretty frustrating for me. But, I have had that problem before. First, check your camera connection to the pi. To do this type raspistill -t 0 into the terminal. If it brings up a preview window, that is not the problem, if it doesn't bring up a preview window, fiddle with the connection and try again. Next, if that doesn't work, run ./RPi_Cam_Web_Interface_Installer.sh. This should bring up a crude GUI. Use your arrow keys to select number 4, or start camera. Once it starts, it should say 'started' next to it. You may get an error message at the bottom saying mmal: mmal_component_create_core: could not create component 'vc.ril.camera' (1)
sh: 1: /var/www/html/macros/error_hard.sh: Permission denied
mmal: mmal_vc_component_create: failed to create component 'vc.ril.camera' (1:ENOMEM) (or the same error you got). To fix this, close the terminal, open up a new one, and cd RPi_Web_Interface and then run again ./RPi_Web_Interface_Installer.sh select configure, enable autostart and camera. Then reboot. When the pi boots up, immediately open a terminal cd RPi_Web_Interface and ./RPi_Web_Interface_Installer.sh and check if the camera is started (you will know because the green started message will be next to the start option). If it isn't started, start it. IF you get the same error messages, I don't know what to tell you.
Had this exact error so:
ran sudo raspi-config and re-enabled the camera -problem went away
I use tmux 1.6-2 on a Debian 7.6 (wheezy).
I open a new session and start a long running script that gives updates in form of a progress bar and an activity indicator (spinning bar: /-\|/ ).
When I detach and reattach everything is still fine. But after some random time when I reattach the screen content is stuck. No spinning bar, no progress. I looked into the following:
I can see in top that the process is still running
I can successfully enter tmux commands (like new window, detach, etc.)
I can kill the script with Ctrl-C, but the tmux screen doesn't change
Ctrl-S and Ctrl-Q (like suggested in other threads) doesn't help
Any help is very much appreciated.
I managed to unfreeze my tmux session by running choose-client command from tmux's command line <prefix> :
where prefix is C-b by default
I found the solution in the bug report (by Taisuke Yamada).