On Sunday 15 May 2016 06:53:08 Gregory Woodbury wrote:
> Just on a hunch: check that /var/lib/sddm exists and is owned by the sddm
> user. This bit me (through my own fault) just a week ago.
I have not messed about with the sddm defaults other than creating a (default)
con
Hi there,
After last update, on one machine sddm-0.17.0-r1 no longer does not anything
anymore. Systemd starts the service, and systemctl status shows that the sddm
is running, and also ps jax shows a running sddm.
apollo ~ # systemctl status sddm
● sddm.service - Simple Desktop Display
On 10/14/2017 05:37 PM, Alan McKinnon wrote:
> Hi
>
> A quick heads-up to anyone who like me uses sddm on a plain openrc box
> with USE="-elogind -systemd" and upgrades to sddm-0.16.0 (recently released)
>
> That combination does not work. The xdm service starts, sdd
Hi
A quick heads-up to anyone who like me uses sddm on a plain openrc box
with USE="-elogind -systemd" and upgrades to sddm-0.16.0 (recently released)
That combination does not work. The xdm service starts, sddm launches,
logs a message that doesn't look too ominous and then does .
Hello,
I have installed kde-frameworks-5.16 & kde-plasma-5.5 and when I start
sddm I get the following error:
/usr/bin/xauth: (stdin):1: bad "remove" command line
/usr/bin/xauth: (stdin):2: bad "add" command line
sddm does not start
Using openrc
Version x11-misc/s
On Sunday 15 May 2016 12:22:20 you wrote:
> On Sunday 15 May 2016 06:53:08 Gregory Woodbury wrote:
> > Just on a hunch: check that /var/lib/sddm exists and is owned by the sddm
> > user. This bit me (through my own fault) just a week ago.
>
> I have not messed about with th
On 14 October 2017 at 08:37, Alan McKinnon <alan.mckin...@gmail.com> wrote:
> A quick heads-up to anyone who like me uses sddm on a plain openrc box
> with USE="-elogind -systemd" and upgrades to sddm-0.16.0 (recently
> released)
>
> That combination does not wor
Am Mittwoch, 4. April 2018, 17:20:17 CEST schrieb Jack:
> On 2018.04.04 11:14, Alexander Puchmayr wrote:
> > Hi there,
> >
> > After last update, on one machine sddm-0.17.0-r1 no longer does not
> > anything anymore. Systemd starts the service, and systemctl sta
Just on a hunch: check that /var/lib/sddm exists and is owned by the sddm
user. This bit me (through my own fault) just a week ago.
--
G.Wolfe Woodbury
redwo...@gmail.com
On 04/04/18 23:14, Alexander Puchmayr wrote:
> Hi there,
>
> After last update, on one machine sddm-0.17.0-r1 no longer does not anything
> anymore. Systemd starts the service, and systemctl status shows that the sddm
> is running, and also ps jax shows a running sddm.
>
>
On 2018.04.04 11:14, Alexander Puchmayr wrote:
Hi there,
After last update, on one machine sddm-0.17.0-r1 no longer does not
anything anymore. Systemd starts the service, and systemctl status
shows that the sddm is running, and also ps jax shows a running sddm.
apollo ~ # systemctl status
Thelma,
On Thursday, 2021-06-10 15:42:10 -0600, you wrote:
> ...
> In: /usr/share/sddm/sddm.conf.d/00default.conf
> I change to
> Numlock=on
No! Directory "/usr/share/sddm/" contains the default configuration for
"sddm" for reference only. You should
On Wed, 13 Apr 2016 08:30:48 -0500, »Q« wrote:
> > > > That's because kdm is dead. I found sddm a little flakey. On my
> > > > laptop it works more or less as expected, but on my desktop,
> > > > selecting reboot or power off from the desktop drops me back to
On 14/10/2017 11:55, Arve Barsnes wrote:
> On 14 October 2017 at 08:37, Alan McKinnon <alan.mckin...@gmail.com
> <mailto:alan.mckin...@gmail.com>> wrote:
>
> A quick heads-up to anyone who like me uses sddm on a plain openrc box
> with USE="-elogind -syst
On 15/10/2017 11:02, Michael Palimaka wrote:
> On 10/14/2017 05:37 PM, Alan McKinnon wrote:
>> Hi
>>
>> A quick heads-up to anyone who like me uses sddm on a plain openrc box
>> with USE="-elogind -systemd" and upgrades to sddm-0.16.0 (recently released)
On Thursday, 4 April 2024 05:55:20 BST Markus Gustafsson wrote:
> Hi again,
>
> I tried to catch the error again and while doing so I realized you guys are
of course correct: sddm usually starts on tty 2. I don't know why I got it
into my head that it would start on tty 8. Anywa
Hi
I've opened issue #1159 on SDDM Github [1], with a patch that makes
better use of "initgroups" and "pam_setcreds", I hope.
@Remy Blank if you could try the patch and comment on the issue, that
may help SDDM project members to evaluate it.
Thanks
Best regards
Mick
On Saturday 28 November 2015 12:51:59 john wrote:
> Hello,
>
> I have installed kde-frameworks-5.16 & kde-plasma-5.5 and when I start
> sddm I get the following error:
>
> /usr/bin/xauth: (stdin):1: bad "remove" command line
> /usr/bin/xauth: (stdin):2: ba
Arve Barsnes wrote:
> On 14 October 2017 at 08:37, Alan McKinnon <alan.mckin...@gmail.com
> <mailto:alan.mckin...@gmail.com>> wrote:
>
> A quick heads-up to anyone who like me uses sddm on a plain openrc box
> with USE="-elogind -systemd"
On Wednesday, 26 June 2019 15:22:45 BST Peter Humphrey wrote:
> On Wednesday, 26 June 2019 11:20:20 BST Mick wrote:
> > I just looked at another installation. The default sddm configuration
> > file (/usr/share/sddm/sddm.conf.d/00default.conf) shows this:
> >
> > [
On Thursday, 27 June 2019 10:55:16 BST Mick wrote:
> The next thing to try:
>
> I don't have elogind starting up as a boot level rc service, because it is
> launched when needed by dbus or pam. Perhaps if elogind is running as a
> background service sddm will (re)launch diffe
On Saturday, 9 April 2022 11:26:13 BST Neil Bothwick wrote:
> On Sat, 09 Apr 2022 10:13:00 +0100, Michael wrote:
> > I'm trying to understand why one PC in particular fails to start SDDM
> > since an update to x11-misc/sddm-0.18.1-r6 and ends up with a blank
> > page on VT7
Hi, everyone.
I have a very starge phenomenon for a long time. I note that when I boot my
computer with mouse attached, the mouse couldn't be recognized on sddm login
ui. But I can see my mouse powered before sddm started. Strangely mouse can be
recognized after I pull it out and insert
On Fri, 19 Jun 2020 10:55:46 +0100, Peter Humphrey wrote:
> And today, pam and pambase are restored to their earlier versions
> because sddm requires them. But sddm has not changed versions, so why
> did portage want to upgrade pam and pambase on Wednesday?
The sddm ebuild has change
t; log-in.
I switched to "sddm" and it works, but it is "ugly".
How to enable "num-lock" with sddm?
I have "num-lock" in default run-level and it turns on when system is booting
but when the "sddm" starts the num-lock is OFF again.
not be cleaned by the
> automatic cleanup (or disable automatic cleanup).
Good shout. Upstream has created a fix, but it is not in a release (yet).
https://github.com/sddm/sddm/commit/b002d02bbe9281b8362fa549991b7581b7758668
I'll try that and see if my version of the problem appears again.
Cheers,
Arve
On 01/09/2015 02:20 PM, behrouz khosravi wrote:
There is definitely a ton to unmask, and if you want kde4 alongside
there are some USE flags to mess around with. I don't really remember
which anymore, but portage should give some hints.
I don't use SDDM, it looked nice, but I like LightDM
On Tue, 12 Apr 2016 14:00:37 -0700, Daniel Frey wrote:
> > That's because kdm is dead. I found sddm a little flakey. On my
> > laptop it works more or less as expected, but on my desktop,
> > selecting reboot or power off from the desktop drops me back to sddm
> > without
On Sunday 10 Apr 2016 11:41:11 Mick wrote:
> Hi All,
>
> I noticed that sddm comes up with a US keyboard layout and there is no other
> choice on the dropdown list. Shouldn't it pick up my env somehow? How can
> I change this, short of using my own xinit or .xses
an McKinnon <alan.mckin...@gmail.com
> <mailto:alan.mckin...@gmail.com>
> > <mailto:alan.mckin...@gmail.com <mailto:alan.mckin...@gmail.com>>>
> wrote:
> >
> > A quick heads-up to anyone who like me uses sddm on a plain openrc
On Wednesday, 26 June 2019 16:49:11 BST Arve Barsnes wrote:
> On Wed, 26 Jun 2019 at 17:13, Neil Bothwick wrote:
> > > Could it be loginctl is there to confirm if a local button operation
> > > can run / sbin/poweroff, rather than actually running the command as
> >
On Fri, 19 Jun 2020 at 12:49, Neil Bothwick wrote:
>
> On Fri, 19 Jun 2020 10:55:46 +0100, Peter Humphrey wrote:
>
> > And today, pam and pambase are restored to their earlier versions
> > because sddm requires them. But sddm has not changed versions, so why
> > did
and the system accept it but I still can not
>> log-in.
> I switched to "sddm" and it works, but it is "ugly".
>
> How to enable "num-lock" with sddm?
> I have "num-lock" in default run-level and it turns on when system is booting
>
On Sat, 09 Apr 2022 10:13:00 +0100, Michael wrote:
> I'm trying to understand why one PC in particular fails to start SDDM
> since an update to x11-misc/sddm-0.18.1-r6 and ends up with a blank
> page on VT7. I suspect some pam module malfunction, but I don't
> understand why this ha
both systems after cold boot login. Here's an example
(same on both hosts):
---
Jun 11 23:13:04 somehost sddm-helper: pam_unix(sddm-greeter:session):
session opened for user sddm(uid=) by (uid=0)
Jun 11 23:13:06 somehost start-stop-daemon:
pam_unix(start-stop-daemon:session): session opened for us
SDDM is merely upstreams replacement for KDM, as I understand it. There
also may be security vulnerabilities in SDDM, I know several versions
have been masked because of that.
Good to know. Thanks
I will keep my slim, and see if slim is able to do job.
On Sat, 28 Nov 2015 14:25:31 +
Peter Humphrey <pe...@prh.myzen.co.uk> wrote:
> On Saturday 28 November 2015 12:51:59 john wrote:
> > Hello,
> >
> > I have installed kde-frameworks-5.16 & kde-plasma-5.5 and when I
> > start sddm I get the following erro
Hi All,
I noticed that sddm comes up with a US keyboard layout and there is no other
choice on the dropdown list. Shouldn't it pick up my env somehow? How can I
change this, short of using my own xinit or .xsession?
--
Regards,
Mick
signature.asc
Description: This is a digitally signed
I've upgraded a PC to plasma5 and sddm won't launch it. Instead it launches
only Enlightenment, which happens to be the first on the sddm list, no matter
what desktop I choose from the drop down.
Have I missed some setting? I followed the plasma 5 upgrade guide. How can I
troubleshoot
I updated to x11-misc/sddm-0.14.0-r2 and as the title says, the DM re-logs in
once when I try to log out. The second time it logs out properly. What might
be causing this strange behaviour? Have you noticed the same?
--
Regards,
Mick
signature.asc
Description: This is a digitally signed
haps if
> > elogind is running as a background service sddm will (re)launch
> > differently?
>
> I just tried it and it works. :-)
>
> With elogind running as a boot service, sddm launches with the
> Shutdown/Reboot buttons shown and they work as expected. However,
How are you starting X in the first place? Are you using a
display manager? Are you running startx?
In the former case, this is perfectly normal for many display
managers, including SDDM. GDM, if I'm not mistaken, can and does
run X as a regular user if possible. Upstream has been talking
I'm trying to understand why one PC in particular fails to start SDDM since an
update to x11-misc/sddm-0.18.1-r6 and ends up with a blank page on VT7. I
suspect some pam module malfunction, but I don't understand why this happens
or how to troubleshoot it. Interestingly, if I restart
t; > to check what Xorg log shows . . . O_O
> > >
> > > Well, what do you know! SDDM started properly, with mouse, GUI and
> > > all. No pam_unix problem. I am now even more confused than before.
> > > Why would the presence of an
On Saturday, 9 April 2022 11:36:45 BST Michael wrote:
> On Saturday, 9 April 2022 11:26:13 BST Neil Bothwick wrote:
> > On Sat, 09 Apr 2022 10:13:00 +0100, Michael wrote:
> > > I'm trying to understand why one PC in particular fails to start SDDM
> > > since an update
I upgraded to KDE 5 recently, and was using LightDM as the display
manager. It seems that KDE 5 prefers SDDM though and offers a config
module for it in System Settings.
So I installed SDDM. However, when I log in with SDDM, I get no sound.
My sound card just... disappears. alsamixer -c0 says
I cannot use my mice at sddm-greeter but I can use my synaptics. When I login
my kde, I just retach my mice, and it works again.
I am use sddm 0.13-r1 and kf-5.15, plasma-5.4.1, qt-5.4.2, gcc-4.9.3,
glibc-2.21-r1.
--
为爱上色
公益活动
在 2015-12-06 08:46:41，"Wallance Lee" <ha...@126
On Tue, 12 Apr 2016 13:21:37 -0500, Dale wrote:
> Oh, I had to switch to sddm for this too. You just change the setting
> from kdm to sddm and it just works. It looks different but it works
> fine. That may have carried over some settings. It selected the user
> and was ready for
On Tuesday, April 12, 2016 07:53:34 PM Neil Bothwick wrote:
> On Tue, 12 Apr 2016 13:21:37 -0500, Dale wrote:
> > Oh, I had to switch to sddm for this too. You just change the setting
> > from kdm to sddm and it just works. It looks different but it works
> > fine. That
On Wed, 13 Apr 2016 00:17:48 +0100
Neil Bothwick <n...@digimed.co.uk> wrote:
> On Tue, 12 Apr 2016 14:00:37 -0700, Daniel Frey wrote:
>
> > > That's because kdm is dead. I found sddm a little flakey. On my
> > > laptop it works more or less as expected, but on my d
On Wed, 26 Jun 2019 11:20:20 +0100
Mick wrote:
> On Tuesday, 25 June 2019 17:09:55 BST »Q« wrote:
> > On Mon, 24 Jun 2019 21:19:09 +0100
> >
> > Mick wrote:
> > > Also, the sddm DM shutdown/reboot buttons now do not work. O_O
> >
> > Those have
On 19/06/2020 15:31, Arve Barsnes wrote:
On Fri, 19 Jun 2020 at 12:49, Neil Bothwick wrote:
On Fri, 19 Jun 2020 10:55:46 +0100, Peter Humphrey wrote:
And today, pam and pambase are restored to their earlier versions
because sddm requires them. But sddm has not changed versions, so why
did
On Sun, 10 Apr 2022 10:18:29 +0100, Michael wrote:
> > The PC is a laptop, which is usually connected to ethernet. Following
> > Neil's prompt I just started it, without an ethernet cable connected,
> > to check what Xorg log shows . . . O_O
> >
> > Well, w
service,
> > > because it is launched when needed by dbus or pam. Perhaps if
> > > elogind is running as a background service sddm will (re)launch
> > > differently?
> >
> > I just tried it and it works. :-)
> >
> > With elogind running as a boo
> Opening file "/tmp/sddm-:0-NpHoUj" failed, ignoring: No such device or
> address
I've not checked keepassxc (running, in the system tray) after this, but
everything GUI (that I have tried) that was already running continues to
run okay, but nothing new can start.
>
> > Does anyone have a hint on the origin of this problem ?
>
> Yes, this is triggered by restarting the xdm service, possibly limited
> to sddm users.
>
> I have noticed the same issue here. Groups are correct after a reboot,
> but if I do:
>
> $ /etc/init.d/x
ittle memory usage meter on the bottom of my screen was down to a more
> > normal level. It was already logging me out so to late to stop it. It
> > seems that it dropped after I closed Firefox. I tend to have two
> > profiles running and they use quite a bit of memory on their ow
Hi again,
I tried to catch the error again and while doing so I realized you guys are of
course correct: sddm usually starts on tty 2. I don't know why I got it into my
head that it would start on tty 8. Anyway, when I finally got it to reproduce
(took a few restarts) I didn't get a blinking
nks, Neil, good point. Not that I can tell. /var/log/auth.log looks
> identical on both systems after cold boot login. Here's an example
> (same on both hosts):
>
> ---
> Jun 11 23:13:04 somehost sddm-helper: pam_unix(sddm-greeter:session):
> session opened for user sddm(uid=) by (uid=0
On Wed, 13 Apr 2016 21:19:30 +0100
Neil Bothwick <n...@digimed.co.uk> wrote:
> On Wed, 13 Apr 2016 08:30:48 -0500, »Q« wrote:
>
> > > > > That's because kdm is dead. I found sddm a little flakey. On
> > > > > my laptop it works more or less as expect
On 15 October 2017 at 10:32, Alan McKinnon <alan.mckin...@gmail.com> wrote:
> On 14/10/2017 11:55, Arve Barsnes wrote:
> > On 14 October 2017 at 08:37, Alan McKinnon <alan.mckin...@gmail.com
> > <mailto:alan.mckin...@gmail.com>> wrote:
> >
> > A q
oot overnight and installed on the live system early this morning.
So far, it is using memory like it used to. This is what ps shows for
it, easiest command I know to show it.
root@fireball / # ps aux | grep sddm-helper
root 1384 0.0 0.0 7652 748 pts/8 S+ 12:31 0:00 grep
--colour=auto -i
prompt I just started it, without an ethernet cable connected,
> > > > to check what Xorg log shows . . . O_O
> > > >
> > > > Well, what do you know! SDDM started properly, with mouse, GUI and
> > > > all. No pam_unix problem. I am now even mo
Mick <michaelkintz...@gmail.com> wrote:
> On Friday 15 Apr 2016 12:24:46 Francisco Ares wrote:
> > Hi, alll.
> >
> > After upgrading to kde 5 (plasma), there is a big problem.
> >
> > No matter if I use sddm to manage user authentication, or common
On Friday 15 Apr 2016 20:02:04 cov...@ccs.covici.com wrote:
> Mick <michaelkintz...@gmail.com> wrote:
> > On Friday 15 Apr 2016 14:11:18 Francisco Ares wrote:
> > > > hmmm, I am using gnome and also get the blank screen, and I don't have
> > > > an sddm use
Hi,
after the update and installation of gentoo-sources-4.14.7 my two machines no
longer switch to SDDM on
VT7, it stays on VT1. However, I can switch manually using CTRL-ALT-7 to SDDM
and login as usual. If I boot
with the last stable kernel 4.12.12 anything is back to normal and the login
On 25/06/2020 17:24, inasprecali wrote:
How are you starting X in the first place? Are you using a
display manager? Are you running startx?
In the former case, this is perfectly normal for many display
managers, including SDDM. GDM, if I'm not mistaken, can and does
run X as a regular user
Michael wrote:
> On Sunday, 3 December 2023 02:18:34 GMT Dale wrote:
>> Michael wrote:
>>> On Saturday, 2 December 2023 05:41:06 GMT Dale wrote:
>>>
>>> Unless you create your own sddm config file in /etc, the sddm package uses
>>> a default c
gt; from scratch in spare disk partitions, choosing the plasma profile
> > and the kde overlay, and using openrc. My frameworks are at version
> > 5.14.0 and kde- plasma is at 5.4.3.
> >
> > I did have a bit of trouble getting sddm to run at first, but after
> > prowling
doesn't work for me. Neither does putting mine in single
or double quotes. Neither does switching sddm themes.
I don't actually ever want/need to shutdown or reboot from the greeter,
so I'll let it be. I found <https://github.com/sddm/sddm/issues/458>,
so I don't feel so all alone. :)
On Wednesday, 26 June 2019 11:34:47 BST Neil Bothwick wrote:
> On Wed, 26 Jun 2019 11:20:20 +0100, Mick wrote:
> > I just looked at another installation. The default sddm configuration
> > file (/ usr/share/sddm/sddm.conf.d/00default.conf) shows this:
> >
> > [
. After I hit logout, I noticed the
>>> little memory usage meter on the bottom of my screen was down to a more
>>> normal level. It was already logging me out so to late to stop it. It
>>> seems that it dropped after I closed Firefox. I tend to have two
>>> profiles runni
rd) I
> > changed/updated the password and the system accept it but I still can not
> > log-in.
> I switched to "sddm" and it works, but it is "ugly".
There are some themes you could choose from, or make your own to improve the
aesthetics of its default appe
On 03/04/2024 19:53, Jack wrote:
Are you certain it hasn't started on some TTY other than 8? I always
start out on TTY1, although I start up text only, no SDDM. However, I do
have a very vague memory of something similar, and I believe it was that
I needed to change one of the kernel FB
There is definitely a ton to unmask, and if you want kde4 alongside
there are some USE flags to mess around with. I don't really remember
which anymore, but portage should give some hints.
I don't use SDDM, it looked nice, but I like LightDM too much
I am not planning to use kde4, so I
More adventures with sddm, but I thought of posting separately about this.
I emerge numlockx and created a bash script in /etc/X11/xinit/xinitrc.d/95-
numlockx to run 'numlockx on'.
sddm launches e20.6 with the numlock switched on. Then kmail asks for a
passwd and as soon as the user starts
On Friday 15 Apr 2016 12:24:46 Francisco Ares wrote:
> Hi, alll.
>
> After upgrading to kde 5 (plasma), there is a big problem.
>
> No matter if I use sddm to manage user authentication, or common console
> login to bash and then to X and kde, the result is the sa
On Friday 15 Apr 2016 14:11:18 Francisco Ares wrote:
> > hmmm, I am using gnome and also get the blank screen, and I don't have
> > an sddm user at all, so I wonder if its a bit more basic.
OK, is x11-misc/sddm installed?
Did you create a config file as advise by the elog?
--
R
> On 2018-05-29, at 18:40, Mick wrote:
>
> It seems the shutdown, suspend, et al options are gone from the plasma
> desktop
> after an update at the end of the week. The user still has the option to
> logout and then use the sddm menu to shutdown, but other options h
On Wed, 26 Jun 2019 at 17:13, Neil Bothwick wrote:
> > Could it be loginctl is there to confirm if a local button operation
> > can run / sbin/poweroff, rather than actually running the command as
> > shown in the sddm config file?
>
> No, not when I tried it
>
>
On Wednesday, 26 June 2019 11:20:20 BST Mick wrote:
> I just looked at another installation. The default sddm configuration file
> (/ usr/share/sddm/sddm.conf.d/00default.conf) shows this:
>
> [General]
> # Halt command
> HaltCommand=/usr/bin/loginctl poweroff
>
Howdy,
I been noticing that sddm is using a lot of memory. In the past, it
would use a few hundred megabytes but nothing out of the norm for a GUI
command. This is what ps aux shows.
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME
COMMAND
root 19256 1.0 10.3
On Fri, 5 Jan 2024 at 02:49, Spackman, Chris wrote:
> Any thoughts on possible causes or fixes?
I've also had this happen a few times over the last months, with error
mails about SDDM tmp files from cron. Just wanted to pipe in and say
that I don't have either rkhunter or keepassxc, so they m
Hoël Bézier wrote:
>> However, it does wake up if I switch to another TTY (e.g.
>> ctrl+alt+F4) and lets me log on, so it has obviously booted up. If I
>> switch back to TTY 8 from there it just shows a blinking cursor (i.e.
>> not SDDM, which is what I'd expect).
;
> >>> I'm not sure on where you got the black screen. If it is when X
> >>> started, did you switch to sddm or some other compatible display
> >>> manager? The old kdm isn't supported and from what I read, doesn't
> >>> work. That may explai
Shatroff wrote:
>>>> Hi Dale,
>>>>
>>>>> I'm not sure on where you got the black screen. If it is when X
>>>>> started, did you switch to sddm or some other compatible display
>>>>> manager? The old kdm isn't supported and from what
On 6/26/19 8:16 AM, Mick wrote:
On Wednesday, 26 June 2019 15:22:45 BST Peter Humphrey wrote:
On Wednesday, 26 June 2019 11:20:20 BST Mick wrote:
I just looked at another installation. The default sddm configuration
file (/usr/share/sddm/sddm.conf.d/00default.conf) shows this:
[General
ps. This is not used under normal circumstances. Instead I use
> > > > a USB 3.0 1Gbps ethernet adaptor. Following your prompts I unplugged
> > > > the USB ethernet adaptor, connected the ethernet cable to the NIC on
> > > > the MoBo and rebooted. No problem. SDDM launches
up. If I switch back to TTY 8
> from there it just shows a blinking cursor (i.e. not SDDM, which is what
> I'd expect). If I reboot from the TTY that lets me log on, the boot process
> is usually normal and leaves me at the SDDM login.
As others have mentioned sddm now starts in the first a
However, it does wake up if I switch to another TTY (e.g. ctrl+alt+F4) and lets
me log on, so it has obviously booted up. If I switch back to TTY 8 from there
it just shows a blinking cursor (i.e. not SDDM, which is what I'd expect). If I
reboot from the TTY that lets me log on, the boot
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2015-07-21 14:12, Nikos Chantziaras wrote:
I upgraded to KDE 5 recently, and was using LightDM as the display
manager. It seems that KDE 5 prefers SDDM though and offers a
config module for it in System Settings.
So I installed SDDM
On 04/12/16 11:53, Neil Bothwick wrote:
> On Tue, 12 Apr 2016 13:21:37 -0500, Dale wrote:
>
>> Oh, I had to switch to sddm for this too. You just change the setting
>> from kdm to sddm and it just works. It looks different but it works
>> fine. That may have ca
t;>> 14.04.2016 00:49, Dale wrote:
>>>>> Yuri K. Shatroff wrote:
>>>> Hi Dale,
>>>>
>>>>> I'm not sure on where you got the black screen. If it is
>>>>> when X started, did you switch to sddm or some other
>>>&g
he default "lightdm" for login but whenever I type-in
> >>> the password it it puts me back to login screen (asking for password) I
> >>> changed/updated the password and the system accept it but I still can
> >>> not
> >>> log-in.
> >>
&
On 22/07/2015 04:34 πμ, Jonathan Callen wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2015-07-21 14:12, Nikos Chantziaras wrote:
I upgraded to KDE 5 recently, and was using LightDM as the display
manager. It seems that KDE 5 prefers SDDM though and offers a
config module
On 12/04/2016 22:10, Frank Steinmetzger wrote:
> On Tue, Apr 12, 2016 at 07:53:34PM +0100, Neil Bothwick wrote:
>> On Tue, 12 Apr 2016 13:21:37 -0500, Dale wrote:
8<
>>> Oh, I had to switch to sddm for this too. You just change the setting
>>> from kdm to sdd
Neil Bothwick wrote:
> On Tue, 12 Apr 2016 13:21:37 -0500, Dale wrote:
>
>> Oh, I had to switch to sddm for this too. You just change the setting
>> from kdm to sddm and it just works. It looks different but it works
>> fine. That may have carried over some setting
14.04.2016 10:43, J. Roeleveld wrote:
On Thursday, April 14, 2016 10:33:10 AM Yuri K. Shatroff wrote:
14.04.2016 00:49, Dale wrote:
Yuri K. Shatroff wrote:
Hi Dale,
I'm not sure on where you got the black screen. If it is when X
started, did you switch to sddm or some other compatible
On Monday 06 Feb 2017 19:56:51 you wrote:
> I updated to x11-misc/sddm-0.14.0-r2 and as the title says, the DM re-logs
> in once when I try to log out. The second time it logs out properly. What
> might be causing this strange behaviour? Have you noticed the same?
I got some tim
2020 10:55:46 +0100, Peter Humphrey wrote:
> >>
> >>> And today, pam and pambase are restored to their earlier versions
> >>> because sddm requires them. But sddm has not changed versions, so why
> >>> did portage want to upgrade pam and pambase on Wedne
1 - 100 of 435 matches
Mail list logo
