Re: wayward wayland.

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

 



On 27/04/2021 12:16, home user wrote:
On 4/25/21 10:29 PM, Ed Greshko wrote:

Or if using KDE plasma-shell.  FWIW, since the OP is getting a blank screen with plasma it may be useful
to reboot the system and use "journalctl -b -1 | grep plasma-shell"

Once again, I switched to sddm and rebooted.  In the login screen, I chose Plasma on wayland and logged in.  The screen went black. After a minute, I did a hard shutdown.  I booted into run-level 3, switched back to gdm, shutdown, booted up, and logged in.

I saved the text of the journal file by doing "journalctl -b -1 > jplasma.txt".  I then put it on the google drive.  Here's the link to the journal file:
"https://drive.google.com/file/d/1HvBJI4RxSqXoAzTwSYtE69iiSQwvXdRo/view?usp=sharing";.

I did some searches.  What I saw in the lines surrounding the hits did not make adequate sense to me.  I did the searches again by doing "journalctl -b -1 | grep -i -n [string]", and then pasted the results into another text file.  I then put it on the google drive.  Here's the link to the search results:
"https://drive.google.com/file/d/1KYzKYyoRD36e5X6wbER-1-eIqsqz3EQI/view?usp=sharing";.


None of your logs make any sense.  First off, you should be grepping for plasmashell.
But that doesn't matter as there is no plasmashell in jplasma.txt. Also, there is no
sign of sddm or a user login.

Booting a VM system here.  (Not using nvidia, but not relevant).  I would see....

Apr 27 13:42:58 f33k.greshko.com systemd-logind[678]: New session c1 of user sddm.
Apr 27 13:42:58 f33k.greshko.com systemd[1]: Created slice User Slice of UID 990.

when sddm is starting.  Note....

[egreshko@f33k ~]$ grep sddm /etc/passwd
sddm:x:990:983:Simple Desktop Display Manager:/var/lib/sddm:/sbin/nologin

And I see no sign of a user login other than root.

But now I just realized you said....

I did a hard shutdown.  I booted into run-level 3, switched back to gdm, shutdown, booted up,

So.....  You have posted the wrong journal times.  You need to keep track of the wall clock and boot times.
Since you booted a second time you'd want -b -2.

journalctl --list-boots

will show all the boots and their relative numbers and start times that are currently in the journal logs.








--
Remind me to ignore comments which aren't germane to the thread.

_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-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/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux