Re: Problems after upgrade to Fedora-34

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 2021-07-01 at 06:54 -0700, Jonathan Ryshpan wrote:
> On Wed, 2021-06-30 at 22:27 +0100, Patrick O'Callaghan wrote:
> > On Wed, 2021-06-30 at 12:24 -0700, Jonathan Ryshpan wrote:
> > > > Most if not all these issues are related to Wayland (other than
> > > > Discover, which is something else). Try KDE under Xorg.
> > > 
> > > Not so easy to do.  The login screen allows a choice between
> > > Wayland
> > > and Xorg; but the change is not sticky.   The only instructions I
> > > can
> > > find on the web are for Gnome and require editing a file
> > > /etc/gdm/custom.conf that does not exist on my system; in fact
> > > there
> > > is no directory /etc/gdm/ .
> > 
> > Not in my experience. I've used both sddm and gdm, and in both
> > cases
> > the choice is remembered across sessions, i.e. sticky. I didn't
> > have to
> > edit anything.
> 
> Gdm is not available on my system (by default) since I run KDE.  Sddm
> works, except that I had to change SDDM > Behavior from "Plasma
> (X11)"
> where I found it to "Plasma (Wayland)" and back in order to get
> sessions to start using X11 rather than Wayland.
> 
> Now that I am running X11, sddm behaves strangely: It runs properly
> when invoked in System Settings but when I run it from the command
> line
> ($ sddm), I see this:
>    $ sddm
>    [06:49:24.239] (EE) DAEMON: Failed to open VT master: Permission
> denied
>    [06:49:24.243] (EE) DAEMON: Failed to read display number from
> pipe
>    [06:49:24.243] (WW) DAEMON: Attempt 1 starting the Display server
> on vt -1 failed
>    [06:49:26.348] (EE) DAEMON: Failed to read display number from
> pipe
>    [06:49:26.348] (WW) DAEMON: Attempt 2 starting the Display server
> on vt -1 failed
>    [06:49:28.352] (EE) DAEMON: Failed to read display number from
> pipe
>    [06:49:28.352] (WW) DAEMON: Attempt 3 starting the Display server
> on vt -1 failed
>    [06:49:28.352] (EE) DAEMON: Could not start Display server on vt -
> 1
> Running sddm using "$ sudo sddm" starts a completely new session.  I
> don't remember this happening under Wayland.

I'm not sure why anyone would run sddm (or indeed any display manager)
from the command line. That is not the normal mode of operation and it
doesn't surprise me that its behaviour is odd.

poc
_______________________________________________
kde mailing list -- kde@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to kde-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/kde@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure




[Index of Archives]     [KDE Users]     [Fedora General Discussion]     [Older Fedora Users Mail]     [Fedora Advisory Board]     [Fedora Security]     [Fedora Maintainers]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Mentors]     [Fedora Package Announce]     [Fedora Package Review]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Triage]     [Coolkey]     [Yum Users]     [Yosemite Forum]     [Fedora Art]     [Fedora Docs]     [Asterisk PBX]

  Powered by Linux