> On 28 Apr 2021, at 22:40, Patrick O'Callaghan wrote:
>
> On Wed, 2021-04-28 at 10:23 -0600, home user wrote:
>> On 4/27/21 8:20 PM, Ed Greshko wrote:
>>
>>> Then the next time you boot enter your hardware's setup mode and
>>> check
>>> the time. Make sure that it is
>>> set to GMT/UTC time
On Wed, 2021-04-28 at 10:23 -0600, home user wrote:
> On 4/27/21 8:20 PM, Ed Greshko wrote:
>
> > Then the next time you boot enter your hardware's setup mode and
> > check
> > the time. Make sure that it is
> > set to GMT/UTC time (HW generally has no knowledge of time zones).
> > Also,
> > do
On 4/27/21 8:20 PM, Ed Greshko wrote:
Then the next time you boot enter your hardware's setup mode and check
the time. Make sure that it is
set to GMT/UTC time (HW generally has no knowledge of time zones). Also,
do that each time you've also
run Windows to make sure it hasn't altered your se
On 28/04/2021 09:24, home user wrote:
On 4/27/21 1:49 PM, Ed Greshko wrote:
On 28/04/2021 02:12, home user wrote:
Your reply is bringing up a vague memory that I probably had a thread on this
list 7 - 8 years ago regarding the system clock. I haven't changed anything
relating to the clock si
On 4/27/21 1:49 PM, Ed Greshko wrote:
On 28/04/2021 02:12, home user wrote:
The times at the beginning of both journal files caught my attention
too. After several seconds pondering that, it occurred to me that
those times are exactly 6 hours off, I'm in mountain time, and this
place is in d
On 4/26/21 11:51 AM, Robert McBroom via users wrote:
On 4/24/21 3:30 PM, home user wrote:
On 4/22/21 4:09 PM, Patrick O'Callaghan wrote:
On Thu, 2021-04-22 at 15:29 -0600, home user wrote:
On 4/22/21 3:23 PM, Patrick O'Callaghan wrote:
Was your original installation the default Workstation
On 28/04/2021 02:12, home user wrote:
The times at the beginning of both journal files caught my attention too.
After several seconds pondering that, it occurred to me that those times are
exactly 6 hours off, I'm in mountain time, and this place is in daylight
savings time. So something is
On 4/27/21 12:30 AM, Ed Greshko wrote:
So. You have posted the wrong journal times. ...
Since you booted a second time you'd want -b -2.
(sigh)
You're right.
You got me.
I'm busted.
The old plasma files have been removed from the google drive.
I switched to sddm, re-booted, chose plasm
journalctl --list-boots
will show all the boots and their relative numbers and start times that are
currently in the journal logs.
Also, when you do things such as login/logout you can note the time and then
use the -S (or --since)
and -U (or --until) to narrow the output of journalctl to k
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 reboote
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 Plasm
On 4/25/21 10:29 PM, Ed Greshko wrote:
On 26/04/2021 11:52, Samuel Sieb wrote:
...
What does "journalctl -b | grep nvidia" give you?
...
Run "journalctl -b" and search for "wayland"
>> ...
Search for "logind" to find a line like:
"systemd-logind[1003]: New session 1 of user "
...
Look for li
On 4/26/21 7:35 PM, home user wrote:
The sddm install did result in several error messages and instructions.
I'll make a separate post for that, ...
On 4/24 at 8:37pm US mountain time, Ed suggested that I consider using
sddm, at least to test. So I installed it. I reported back on 4/25 at
(not replying to any specific post)
I discovered last night (Sunday night US mountain time) that some of the
posts to this thread went to individual members (myself and Ed) rather
than to the whole list. Apparently, I clicked "Reply" rather than
"Reply List" when replying to a Friday night (U
On 4/24/21 3:30 PM, home user wrote:
On 4/22/21 4:09 PM, Patrick O'Callaghan wrote:
On Thu, 2021-04-22 at 15:29 -0600, home user wrote:
On 4/22/21 3:23 PM, Patrick O'Callaghan wrote:
Was your original installation the default Workstation or KDE Spin?
It was the default workstation (GNOME?)
On 26/04/2021 12:29, 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"
This may be an issue with plasma wayland in F33.
https://bugs.kde.org/show_bug.
On 26/04/2021 11:52, Samuel Sieb wrote:
On 2021-04-25 8:21 p.m., home user wrote:
On 4/25/21 9:18 PM, Samuel Sieb wrote:
Have you checked the journal to see if there's any indication of why it's not
working?
That's huge.
Please give me something to look for, or a full command.
It's hard t
On 2021-04-25 8:21 p.m., home user wrote:
On 4/25/21 9:18 PM, Samuel Sieb wrote:
Have you checked the journal to see if there's any indication of why
it's not working?
That's huge.
Please give me something to look for, or a full command.
It's hard to give anything specific and I'm not sure
On 4/25/21 9:18 PM, Samuel Sieb wrote:
On 4/25/21 7:57 PM, home user wrote:
Might Fedora
possibly
maybe
quietly
disabled or turned off wayland sometime between F-25 and F-33
inclusively?
maybe just for Nvidia graphics card users?
possibly just for certain categories of users?
No, but there
On 4/25/21 7:57 PM, home user wrote:
Might Fedora
possibly
maybe
quietly
disabled or turned off wayland sometime between F-25 and F-33 inclusively?
maybe just for Nvidia graphics card users?
possibly just for certain categories of users?
No, but there's always a possibility of it not working
On 4/25/21 6:21 AM, Patrick O'Callaghan wrote:
On Sat, 2021-04-24 at 19:41 -0600, home user wrote:
general FYI for everyone...
This Fedora docs web page says that wayland has been the default
gnome
display server, and has been the default since F-25:
"https://docs.fedoraproject.org/en-US/quick-
On 4/25/21 6:21 AM, Patrick O'Callaghan wrote:
On Sat, 2021-04-24 at 19:41 -0600, home user wrote:
general FYI for everyone...
This Fedora docs web page says that wayland has been the default
gnome
display server, and has been the default since F-25:
"https://docs.fedoraproject.org/en-US/quick-
On 4/25/21 1:21 AM, Tim via users wrote:
On Sun, 2021-04-25 at 06:24 +0800, Ed Greshko wrote:
Read Tim's comment again. "He" wrote the notes in a file. Not dnf
or another process.
Not quite. I've written my post-installation-log, but the system has
written anaconda-ks.cfg files on two insta
On 4/24/21 10:02 PM, Ed Greshko wrote:
On 25/04/2021 10:12, home user wrote:
Read Tim's comment again. "He" wrote the notes in a file. Not dnf
or another process.
The basis for my question was the sentence "I think the installation
routine leaves a couple of files about the install in there
On Sat, 2021-04-24 at 19:41 -0600, home user wrote:
> general FYI for everyone...
>
> This Fedora docs web page says that wayland has been the default
> gnome
> display server, and has been the default since F-25:
> "https://docs.fedoraproject.org/en-US/quick-docs/configuring-xorg-as-default-gnom
On Sun, 2021-04-25 at 06:24 +0800, Ed Greshko wrote:
> Read Tim's comment again. "He" wrote the notes in a file. Not dnf
> or another process.
Not quite. I've written my post-installation-log, but the system has
written anaconda-ks.cfg files on two installations, and left me a
initial-setup-ks.
On 25/04/2021 11:06, home user wrote:
Is that causing problems? I'm not sure why I did that. But most likely,
because I was not familiar with the various desktops, I gave myself the chance
to try all (or most?) of them and choose. I routinely use ksysguard and k3b
(from plasma), and caja (f
On 25/04/2021 10:12, home user wrote:
Read Tim's comment again. "He" wrote the notes in a file. Not dnf or another
process.
The basis for my question was the sentence "I think the installation routine leaves a couple of files about the install in there, itself.". But I might easily be misund
On 4/24/21 8:37 PM, Ed Greshko wrote:
On 25/04/2021 10:12, home user wrote:
I recall you once did have an option for plasma on wayland.
You still have a
/usr/share/wayland-sessions/plasmawayland.desktop
file?
yes:
bash.2[~]: su -
Password:
-bash.1[~]: ls -l /usr/share/wayland-sessions/pl
On 25/04/2021 10:12, home user wrote:
A few minutes ago, I rebooted. There is only one plasma option in the menu:
"Plasma". I chose that and completed the login.
bash.1[~]: su -
Password:
-bash.1[~]: journalctl -b 0 | grep wayland
-bash.2[~]: env | grep -i wayland
-bash.3[~]:
I recall you
On 4/24/21 4:24 PM, Ed Greshko wrote:
On 25/04/2021 03:42, home user wrote:
On 4/24/21 12:34 AM, Tim via users wrote:
For later on, once you're back working again:
Next time you do an install, leave some notes in the /root homespace
about what you've done. I think the installation routine le
general FYI for everyone...
This Fedora docs web page says that wayland has been the default gnome
display server, and has been the default since F-25:
"https://docs.fedoraproject.org/en-US/quick-docs/configuring-xorg-as-default-gnome-session/";.
___
On 25/04/2021 03:42, home user wrote:
On 4/24/21 12:34 AM, Tim via users wrote:
For later on, once you're back working again:
Next time you do an install, leave some notes in the /root homespace
about what you've done. I think the installation routine leaves a
couple of files about the instal
On Sat, 24 Apr 2021 at 16:43, home user wrote:
> On 4/24/21 12:34 AM, Tim via users wrote:
>
> > For later on, once you're back working again:
> >
> > Next time you do an install, leave some notes in the /root homespace
> > about what you've done. I think the installation routine leaves a
> > co
On 4/24/21 12:34 AM, Tim via users wrote:
For later on, once you're back working again:
Next time you do an install, leave some notes in the /root homespace
about what you've done. I think the installation routine leaves a
couple of files about the install in there, itself. And I write some
p
On 4/22/21 4:09 PM, Patrick O'Callaghan wrote:
On Thu, 2021-04-22 at 15:29 -0600, home user wrote:
On 4/22/21 3:23 PM, Patrick O'Callaghan wrote:
Was your original installation the default Workstation or KDE Spin?
It was the default workstation (GNOME?).
This would have been early spring 20
On 4/22/21 12:41 PM, Joe Zeff wrote:
On 4/22/21 11:29 AM, home user wrote:
I did that as a part of the upgrade earlier this month. But I try again:
bash.1[~]: su -
Password:
-bash.1[~]: dnf distro-sync
Last metadata expiration check: 0:51:59 ago on Thu 22 Apr 2021
10:35:59 AM MDT.
Dependenci
On Fri, 2021-04-23 at 20:24 -0600, home user wrote:
> Since my initial install was 8 years ago, I don't remember for
> certain how I did it: CD or USB stick.
For later on, once you're back working again:
Next time you do an install, leave some notes in the /root homespace
about what you've done.
On 4/23/21 9:48 PM, Ed Greshko wrote:
That caveat only applied to lightdm. I'd revert that change now that
you'e using gdm.
reverted.
rebooted. got the gdm login.
The GNOME entry re-appeared; the GNOME on Xorg entry disappeared.
logged into GNOME.
"env | grep -i wayland" returns nothing,
On 24/04/2021 11:26, home user wrote:
On 4/23/21 9:18 PM, Ed Greshko wrote:
2. Do you have the file /usr/share/wayland-sessions/gnome.desktop (You've not
disabled it)
I have it; see below. I don't know if I've disabled it; how would I check?
That question was related to earlier in the thr
On 4/23/21 9:18 PM, Ed Greshko wrote:
2. Do you have the file /usr/share/wayland-sessions/gnome.desktop
(You've not disabled it)
I have it; see below. I don't know if I've disabled it; how would I
check?
That question was related to earlier in the thread in talking about
lightdb. If one a
On 24/04/2021 11:09, home user wrote:
On 4/23/21 8:48 PM, Ed Greshko wrote:
On 24/04/2021 10:42, home user wrote:
On 4/23/21 8:28 PM, Ed Greshko wrote:
On 24/04/2021 10:24, home user wrote:
... So we're back to the starting questions. How do I get wayland working in
gnome on this workstat
On 24/04/2021 11:15, home user wrote:
Looking more slowly and closely, I see 2 of mine are more recent than Ed's:
qt5-qtwayland-5.15.2-5.fc33.x86_64 (mine)
qt5-qtwayland-5.15.2-3.fc33.x86_64 (Ed's)
xorg-x11-server-Xwayland-1.20.11-1.fc33.x86_64 (mine)
xorg-x11-server-Xwayland-1.20.10-1.fc33.x86
On 4/23/21 9:09 PM, home user wrote:
On 4/23/21 8:48 PM, Ed Greshko wrote:
On 24/04/2021 10:42, home user wrote:
On 4/23/21 8:28 PM, Ed Greshko wrote:
On 24/04/2021 10:24, home user wrote:
... So we're back to the starting questions. How do I get wayland
working in gnome on this workstatio
On 4/23/21 8:48 PM, Ed Greshko wrote:
On 24/04/2021 10:42, home user wrote:
On 4/23/21 8:28 PM, Ed Greshko wrote:
On 24/04/2021 10:24, home user wrote:
... So we're back to the starting questions. How do I get wayland
working in gnome on this workstation? Am I missing something? If
yes, w
On 24/04/2021 10:42, home user wrote:
On 4/23/21 8:28 PM, Ed Greshko wrote:
On 24/04/2021 10:24, home user wrote:
... So we're back to the starting questions. How do I get wayland working in
gnome on this workstation? Am I missing something? If yes, what? Otherwise,
what do I need to do t
On 4/23/21 8:28 PM, Ed Greshko wrote:
On 24/04/2021 10:24, home user wrote:
... So we're back to the starting questions. How do
I get wayland working in gnome on this workstation? Am I missing
something? If yes, what? Otherwise, what do I need to do to make
wayland available and properly
On 24/04/2021 10:24, home user wrote:
On 4/23/21 8:02 PM, Ed Greshko wrote:
(my apologies: I replied to him when I meant to reply to the list)
On a F33 system installed from Workstation Live the choices would show as
GNOME
GNOME Classic
GNOME on Xorg
With the top being walyand.
I don't have
On 4/23/21 8:02 PM, Ed Greshko wrote:
(my apologies: I replied to him when I meant to reply to the list)
On a F33 system installed from Workstation Live the choices would show as
GNOME
GNOME Classic
GNOME on Xorg
With the top being walyand.
I don't have that top entry.
Since my initial inst
On 24/04/2021 09:46, home user wrote:
I'm BAAAaaack!
I did not stay at the workstation so I don't know if there were any errors, warnings, or messages. But I found the gdm login screen displaying. I'm currently logged in to my Fedora user account in GNOME on Xorg and doing this message in Thun
On 4/23/21 6:14 PM, home user wrote:
On 4/23/21 5:53 PM, Ed Greshko wrote:
On 24/04/2021 07:42, home user wrote:
On 4/23/2021 4:34 PM, Ed Greshko wrote:
If both of those are "yes", would you do as Tim requested and
touch /.autorelabel
And then reboot with selinux enabled.
With or without r
On 4/23/21 5:53 PM, Ed Greshko wrote:
On 24/04/2021 07:42, home user wrote:
On 4/23/2021 4:34 PM, Ed Greshko wrote:
Before that.
Can you boot again with selinux disabled? And, if you can, does gdm
start?
Is this with or without run-level 3?
Either way. If with 3 you'll have to logi
On 24/04/2021 07:42, home user wrote:
On 4/23/2021 4:34 PM, Ed Greshko wrote:
Before that.
Can you boot again with selinux disabled? And, if you can, does gdm start?
Is this with or without run-level 3?
Either way. If with 3 you'll have to login from the text prompt and manually
sta
On 4/23/2021 4:34 PM, Ed Greshko wrote:
Before that.
Can you boot again with selinux disabled? And, if you can, does gdm start?
Is this with or without run-level 3?
If both of those are "yes", would you do as Tim requested and
touch /.autorelabel
And then reboot with selinux enabled.
On 24/04/2021 02:56, home user wrote:
On 04/22/2021 10:34 PM, home user wrote:
I'm having to use my old windows-7 partition and system for this message.
Rebooting to re-enable SELinux
It failed.
The last 4 lines of boot messages were:
[OK] Started Command Scheduler.
Started GNOME Dis
On 04/22/2021 10:34 PM, home user wrote:
I'm having to use my old windows-7 partition and system for this message.
Rebooting to re-enable SELinux
It failed.
The last 4 lines of boot messages were:
[OK] Started Command Scheduler.
Started GNOME Display Manager...
Started Hold until
On 04/23/2021 7:28 AM, Ed Greshko wrote:
On 23/04/2021 21:08, home user wrote:
My gut tells me the SELinux re-label either never finishedor never
started. The 4 lines that I put into my most recent post came up in
under 2 minutes after the grub menu disappeared, and I never saw any
hint of ou
On 23/04/2021 21:08, home user wrote:
My gut tells me the SELinux re-label either never finishedor never started. The 4 lines that I put into my most recent post came up in under 2 minutes after the grub menu disappeared, and I never saw any hint of output from a SELinux relabelling. So when I t
On Fri, 2021-04-23 at 07:08 -0600, home user wrote:
> My gut tells me the SELinux re-label either never finished or never
> started. The 4 lines that I put into my most recent post came up in
> under 2 minutes after the grub menu disappeared, and I never saw any
> hint of output from a SELinux
On 04/23/2021 12:19 AM, Joe Zeff wrote:
On 4/22/21 11:50 PM, Ed Greshko wrote:
As you did before, when you have the kernel selection menu hit e.
Then add a 3 to the end of
the linux line. Ctrl-x to continue to single user mode.
No, runlevel 3 boots you into a multi-user system with networki
On 4/22/21 11:50 PM, Ed Greshko wrote:
As you did before, when you have the kernel selection menu hit e. Then
add a 3 to the end of
the linux line. Ctrl-x to continue to single user mode.
No, runlevel 3 boots you into a multi-user system with networking, but
text based, not graphical. Howe
On 23/04/2021 12:34, home user wrote:
I'm having to use my old windows-7 partition and system for this message.
Rebooting to re-enable SELinux
It failed.
The last 4 lines of boot messages were:
[OK] Started Command Scheduler.
Started GNOME Display Manager...
Started Hold until boo
I'm having to use my old windows-7 partition and system for this message.
Rebooting to re-enable SELinux
It failed.
The last 4 lines of boot messages were:
[OK] Started Command Scheduler.
Started GNOME Display Manager...
Started Hold until boot process finishs up...
[OK] Started GN
On 4/22/21 5:55 PM, Ed Greshko wrote:
OK But that makes things slightly more "complicated".
The disabling of selinux was to determine if that would allow you to
bring up wayland.
But if you don't have that option, then nothing will be learned. You
won't get
the sealerts since selinux wa
On 23/04/2021 07:49, home user wrote:
With both gdm and the renamed file, the gear menu lists the following gnome
choices...
GNOME Classic
GNOME on Xorg
I went with GNOME on Xorg.
Same system and SELinux alerts.
Well, with the renamed file you don't seem to have "GNOME" only. That would
be the
On 4/22/21 4:56 PM, Ed Greshko wrote:
If you are a majority Gnome user I'd go with gdm
With both gdm and the renamed file, the gear menu lists the following
gnome choices...
GNOME Classic
GNOME on Xorg
I went with GNOME on Xorg.
Same system and SELinux alerts.
I just saw your post to disabl
On 23/04/2021 07:19, home user wrote:
bash.1[~]: su -
Password:
-bash.1[~]: systemctl --force enable gdm
Removed /etc/systemd/system/display-manager.service.
Created symlink /etc/systemd/system/display-manager.service →
/usr/lib/systemd/system/gdm.service.
-bash.2[~]:
I rebooted.
The login
On 4/22/21 4:56 PM, Ed Greshko wrote:
If you are a majority Gnome user I'd go with gdm
bash.1[~]: su -
Password:
-bash.1[~]: systemctl --force enable gdm
Removed /etc/systemd/system/display-manager.service.
Created symlink /etc/systemd/system/display-manager.service →
/usr/lib/systemd/system/
On 23/04/2021 06:51, home user wrote:
I thought it best to check back with you before trying gdm (which I already have) or sddm (which I don't yet have).
If you are a majority Gnome user I'd go with gdm
--
Remind me to ignore comments which aren't germane to the thread.
___
On 4/22/21 3:34 PM, Ed Greshko wrote:
This may be your problem.
Wayland session not working with duplicate GNOME entries in greeter
Some greeters (lightdm-webkit2-greeter for example) do not support two
sessions with the same name [1]. To check for duplicate entries:
ls -1 /usr/share/wayl
On 23/04/2021 06:09, Patrick O'Callaghan wrote:
I'm not sure Wayland would have been part of the default install in
2013, and if all your subsequent installs have been updates than that
could explain why you don't have it.
I would have no idea as to the minimum packages needed to support waylan
On Thu, 2021-04-22 at 15:29 -0600, home user wrote:
> On 4/22/21 3:23 PM, Patrick O'Callaghan wrote:
> > On Thu, 2021-04-22 at 11:29 -0600, home user wrote:
> > > On 4/22/21 11:10 AM, Joe Zeff wrote:
> > > > On 4/22/21 9:50 AM, home user wrote:
> > > > > I'm wondering if wayland and earlyoom did ge
On 23/04/2021 06:01, home user wrote:
On 4/22/21 3:34 PM, Ed Greshko wrote:
On 23/04/2021 05:26, home user wrote:
Or, you can try switching to a different DM.
If you have gdm or sddm installed you can do
systemctl --force enable sddm
Then reboot.
Thinking of both the present and the
On 4/22/21 3:34 PM, Ed Greshko wrote:
On 23/04/2021 05:26, home user wrote:
Or, you can try switching to a different DM.
If you have gdm or sddm installed you can do
systemctl --force enable sddm
Then reboot.
Thinking of both the present and the next few years, which of lightdm,
gdm,
On 23/04/2021 05:26, home user wrote:
bash.8[~]: systemctl status display-manager
● lightdm.service - Light Display Manager
Loaded: loaded (/usr/lib/systemd/system/lightdm.service; enabled; vendor
preset: enabled)
Active: active (running) since Thu 2021-04-22 10:57:46 MDT; 4h 27min ago
On 4/22/21 3:23 PM, Patrick O'Callaghan wrote:
On Thu, 2021-04-22 at 11:29 -0600, home user wrote:
On 4/22/21 11:10 AM, Joe Zeff wrote:
On 4/22/21 9:50 AM, home user wrote:
I'm wondering if wayland and earlyoom did get installed and then
later
removed or de-activated. I'm also wondering what
On 4/22/21 3:18 PM, Ed Greshko wrote:
On 23/04/2021 04:04, home user wrote:
Is that referring to gnome vs. plasma vs. mate vs. (etc)?
If yes, I usually log into the first GNOME entry, which is apparently
the same as GNOME on Xorg. The version is 3.38.5. The windowing
system is X11.
That i
On Thu, 2021-04-22 at 11:29 -0600, home user wrote:
> On 4/22/21 11:10 AM, Joe Zeff wrote:
> > On 4/22/21 9:50 AM, home user wrote:
> > > I'm wondering if wayland and earlyoom did get installed and then
> > > later
> > > removed or de-activated. I'm also wondering what else I should
> > > have
>
On 23/04/2021 04:04, home user wrote:
Is that referring to gnome vs. plasma vs. mate vs. (etc)?
If yes, I usually log into the first GNOME entry, which is apparently the same
as GNOME on Xorg. The version is 3.38.5. The windowing system is X11.
That is the DE or Desktop Environment
If no,
On 4/22/21 1:17 PM, Ed Greshko wrote:
That should support Wayland.
You can see the actual version of the nvidia driver with
strings /lib/modules/`uname -r`/extra/nvidia/nvidia.ko | grep ^version=
-bash.4[~]: strings /lib/modules/`uname -r`/extra/nvidia/nvidia.ko |
grep ^version=
versio
On 22/04/2021 23:50, home user wrote:
On 4/22/21 1:14 AM, Ed Greshko wrote:
On 20/04/2021 01:23, home user wrote:
How do I get wayland properly working on my workstation?
You have nVidia HW and are using the nVidia drivers packaged by rpmfusion.
To give any opinion about you chances to ge
On 4/22/21 11:29 AM, home user wrote:
I did that as a part of the upgrade earlier this month. But I try again:
bash.1[~]: su -
Password:
-bash.1[~]: dnf distro-sync
Last metadata expiration check: 0:51:59 ago on Thu 22 Apr 2021 10:35:59
AM MDT.
Dependencies resolved.
Nothing to do.
Complete!
On Thu, 22 Apr 2021 at 04:14, Ed Greshko wrote:
>
> To give any opinion about you chances to get wayland working one would need
> to know your HW and what version of the driver you're running. If your HW
> is
> 8 years old, then my guess would be your chances of getting wayland running
> are sli
On 4/22/21 11:10 AM, Joe Zeff wrote:
On 4/22/21 9:50 AM, home user wrote:
I'm wondering if wayland and earlyoom did get installed and then later
removed or de-activated. I'm also wondering what else I should have
but am missing. In other words, do I have a broader problem?
If you're concern
On 4/22/21 9:50 AM, home user wrote:
I'm wondering if wayland and earlyoom did get installed and then later
removed or de-activated. I'm also wondering what else I should have but
am missing. In other words, do I have a broader problem?
If you're concerned about that, you might consider usin
On 4/22/21 1:14 AM, Ed Greshko wrote:
On 20/04/2021 01:23, home user wrote:
How do I get wayland properly working on my workstation?
You have nVidia HW and are using the nVidia drivers packaged by rpmfusion.
To give any opinion about you chances to get wayland working one would need
to kno
On Thu, 2021-04-22 at 20:55 +0800, Ed Greshko wrote:
> On 22/04/2021 19:36, Patrick O'Callaghan wrote:
>
> > I don't currently use Wayland as I'm on KDE, but I have briefly
> > tested
> > it in F33 under Gnome. My hardware is of a similar age, i.e. the
> > mobo
> > is at least 8 years old and the
On 22/04/2021 19:36, Patrick O'Callaghan wrote:
I don't currently use Wayland as I'm on KDE, but I have briefly tested
it in F33 under Gnome. My hardware is of a similar age, i.e. the mobo
is at least 8 years old and the GPU is a GTX-1050 from 2017, using the
RPMfusion driver. It all worked fine
On Thu, 2021-04-22 at 15:14 +0800, Ed Greshko wrote:
> On 20/04/2021 01:23, home user wrote:
> > While trying to diagnose problems as a part of another thread in
> > this list, I discovered that wayland is not functional on my
> > workstation. I'm currently logged in to gnome using the top "GNOME"
On 20/04/2021 01:23, home user wrote:
While trying to diagnose problems as a part of another thread in this list, I discovered
that wayland is not functional on my workstation. I'm currently logged in to gnome using
the top "GNOME" entry in the menu of desktops that is displayed in the upper
r
While trying to diagnose problems as a part of another thread in this
list, I discovered that wayland is not functional on my workstation.
I'm currently logged in to gnome using the top "GNOME" entry in the menu
of desktops that is displayed in the upper right corner of the monitor
during login
91 matches
Mail list logo
