6:53 a.m.
Is just me getting Plasma problems since recent updates?
I apply Fedora updates once a week and since last week I'm getting
frequent (only something like once a day) problems.
I've had a couple of total hangs, I think these were linked to viewing
a website that has a particularly active js header in FireFox, though
to be fair that might be 'cos it turned out I also had 90 other tabs
open.
Other than that I seem to get a "race condition", my auto-hiding
control bar sometimes shows a flickering tooltip, nothing seems to fix
that other than closing the session (log off or reboot). I've just had
a screen corruption, the right hand side (15%?) got a portion of some
other page fixed on it, changing virtual desktop fixed that.
This is new since last week.
Mark
F39, X11.
7 a.m.
On Thu, 2024-04-18 at 12:53 +0100, Mark @ GMail wrote:
Is just me getting Plasma problems since recent updates?
I apply Fedora updates once a week and since last week I'm getting
frequent (only something like once a day) problems.
I've had a couple of total hangs, I think these were linked to
viewing
a website that has a particularly active js header in FireFox, though
to be fair that might be 'cos it turned out I also had 90 other tabs
open.
Other than that I seem to get a "race condition", my auto-hiding
control bar sometimes shows a flickering tooltip, nothing seems to
fix
that other than closing the session (log off or reboot). I've just
had
a screen corruption, the right hand side (15%?) got a portion of some
other page fixed on it, changing virtual desktop fixed that.
This is new since last week.
I haven't seen that specifically, but I occasionally after resuming
from hibernation the Plasma bar isn't there for some reason. Probably a
different issue from what you have, but it prompted me to create a
little script to restore it (from a suggestion of Rex Dieter):
#!/bin/sh
# Restart the Plasma workspace under KDE. Use if Plasma crashes or
# Autohide stops working.
http://forum.kde.org/viewtopic.php?f=67&t=87132&p=154341#p154341
# KDE list 06/01/2019 Rex Dieter <rdieter(a)gmail.com>
kquitapp5 plasmashell
killall plasmashell
kstart5 plasmashell &
No doubt it could be more elegant but it works.
poc
7:08 a.m.
On Thu, Apr 18, 2024 at 8:01 AM Patrick O'Callaghan
<pocallaghan(a)gmail.com> wrote:
On Thu, 2024-04-18 at 12:53 +0100, Mark @ GMail wrote:
> Is just me getting Plasma problems since recent updates?
>
> I apply Fedora updates once a week and since last week I'm getting
> frequent (only something like once a day) problems.
>
> I've had a couple of total hangs, I think these were linked to
> viewing
> a website that has a particularly active js header in FireFox, though
> to be fair that might be 'cos it turned out I also had 90 other tabs
> open.
>
> Other than that I seem to get a "race condition", my auto-hiding
> control bar sometimes shows a flickering tooltip, nothing seems to
> fix
> that other than closing the session (log off or reboot). I've just
> had
> a screen corruption, the right hand side (15%?) got a portion of some
> other page fixed on it, changing virtual desktop fixed that.
>
> This is new since last week.
I haven't seen that specifically, but I occasionally after resuming
from hibernation the Plasma bar isn't there for some reason. Probably a
different issue from what you have, but it prompted me to create a
little script to restore it (from a suggestion of Rex Dieter):
#!/bin/sh
# Restart the Plasma workspace under KDE. Use if Plasma crashes or
# Autohide stops working.
http://forum.kde.org/viewtopic.php?f=67&t=87132&p=154341#p154341
# KDE list 06/01/2019 Rex Dieter <rdieter(a)gmail.com>
kquitapp5 plasmashell
killall plasmashell
kstart5 plasmashell &
No doubt it could be more elegant but it works.
I think this particular issue should be fixed with Plasma Wayland in
Plasma 6, since Plasma detects when the shell dies and restarts itself
automatically (I've seen it happen a few times when my graphics card
chokes).
--
真実はいつも一つ！/ Always, there's only one truth!
7:17 a.m.
On Thu, 2024-04-18 at 08:08 -0400, Neal Gompa wrote:
I think this particular issue should be fixed with Plasma Wayland in
Plasma 6, since Plasma detects when the shell dies and restarts
itself
automatically (I've seen it happen a few times when my graphics card
chokes).
Hmm, am I brave enough to use Wayland all the time? :-/
In fairness, it's working very well for me nowadays. I did use it for
a while last week, I don't remember why I switched back. Not sure if
it was something concrete or just nerves.
Plasma 6 looks exciting. Any idea when it's going to get into the
Fedora repo?
Mark
7:19 a.m.
On Thu, Apr 18, 2024 at 8:17 AM Mark @ GMail <mrkr.st(a)gmail.com> wrote:
On Thu, 2024-04-18 at 08:08 -0400, Neal Gompa wrote:
> I think this particular issue should be fixed with Plasma Wayland in
> Plasma 6, since Plasma detects when the shell dies and restarts
> itself
> automatically (I've seen it happen a few times when my graphics card
> chokes).
Hmm, am I brave enough to use Wayland all the time? :-/
In fairness, it's working very well for me nowadays. I did use it for
a while last week, I don't remember why I switched back. Not sure if
it was something concrete or just nerves.
Plasma 6 looks exciting. Any idea when it's going to get into the
Fedora repo?
You will get it as part of upgrading to Fedora 40. It's a big
backwards incompatible upgrade, so it is F40+ only.
--
真実はいつも一つ！/ Always, there's only one truth!
7:36 a.m.
On Thu, 2024-04-18 at 13:17 +0100, Mark @ GMail wrote:
On Thu, 2024-04-18 at 08:08 -0400, Neal Gompa wrote:
> I think this particular issue should be fixed with Plasma Wayland
> in
> Plasma 6, since Plasma detects when the shell dies and restarts
> itself
> automatically (I've seen it happen a few times when my graphics
> card
> chokes).
Hmm, am I brave enough to use Wayland all the time? :-/
In fairness, it's working very well for me nowadays. I did use it
for
a while last week, I don't remember why I switched back. Not sure if
it was something concrete or just nerves.
Plasma 6 looks exciting. Any idea when it's going to get into the
Fedora repo?
It'll be in F40. For me the big issue is the lack of proper session
save/restore. We are promised a workaround in Plasma 6 to support some
of that functionality. I'm anxious to see how well it works.
poc
1:56 p.m.
On Thu, Apr 18, 2024 at 8:36 AM Patrick O'Callaghan
<pocallaghan(a)gmail.com> wrote:
On Thu, 2024-04-18 at 13:17 +0100, Mark @ GMail wrote:
> On Thu, 2024-04-18 at 08:08 -0400, Neal Gompa wrote:
> > I think this particular issue should be fixed with Plasma Wayland
> > in
> > Plasma 6, since Plasma detects when the shell dies and restarts
> > itself
> > automatically (I've seen it happen a few times when my graphics
> > card
> > chokes).
>
> Hmm, am I brave enough to use Wayland all the time? :-/
>
> In fairness, it's working very well for me nowadays. I did use it
> for
> a while last week, I don't remember why I switched back. Not sure if
> it was something concrete or just nerves.
>
> Plasma 6 looks exciting. Any idea when it's going to get into the
> Fedora repo?
It'll be in F40. For me the big issue is the lack of proper session
save/restore. We are promised a workaround in Plasma 6 to support some
of that functionality. I'm anxious to see how well it works.
I backported it for you a while back:
https://src.fedoraproject.org/rpms/plasma-workspace/c/d03958da910f3ba08c5...
So it's present in Plasma 6.0 in Fedora 40. :)
--
真実はいつも一つ！/ Always, there's only one truth!
4:13 p.m.
On Thu, 2024-04-18 at 14:56 -0400, Neal Gompa wrote:
On Thu, Apr 18, 2024 at 8:36 AM Patrick O'Callaghan
<pocallaghan(a)gmail.com> wrote:
>
> On Thu, 2024-04-18 at 13:17 +0100, Mark @ GMail wrote:
> > On Thu, 2024-04-18 at 08:08 -0400, Neal Gompa wrote:
> > > I think this particular issue should be fixed with Plasma
> > > Wayland
> > > in
> > > Plasma 6, since Plasma detects when the shell dies and restarts
> > > itself
> > > automatically (I've seen it happen a few times when my graphics
> > > card
> > > chokes).
> >
> > Hmm, am I brave enough to use Wayland all the time? :-/
> >
> > In fairness, it's working very well for me nowadays. I did use
> > it
> > for
> > a while last week, I don't remember why I switched back. Not
> > sure if
> > it was something concrete or just nerves.
> >
> > Plasma 6 looks exciting. Any idea when it's going to get into
> > the
> > Fedora repo?
>
> It'll be in F40. For me the big issue is the lack of proper session
> save/restore. We are promised a workaround in Plasma 6 to support
> some
> of that functionality. I'm anxious to see how well it works.
>
I backported it for you a while back:
https://src.fedoraproject.org/rpms/plasma-workspace/c/d03958da910f3ba08c5...
So it's present in Plasma 6.0 in Fedora 40. :)
Yes, I think I commented at the time. I'll wait for the official F40 to
see how it goes.
poc
2:47 p.m.
On 4/18/24 8:17 AM, Mark @ GMail wrote:
On Thu, 2024-04-18 at 08:08 -0400, Neal Gompa wrote:
> I think this particular issue should be fixed with Plasma Wayland in
> Plasma 6, since Plasma detects when the shell dies and restarts
> itself
> automatically (I've seen it happen a few times when my graphics card
> chokes).
Hmm, am I brave enough to use Wayland all the time? :-/
In fairness, it's working very well for me nowadays. I did use it for
a while last week, I don't remember why I switched back. Not sure if
it was something concrete or just nerves.
Plasma 6 looks exciting. Any idea when it's going to get into the
Fedora repo?
Mouse movement is very jumpy in Wayland. Doesn't integrate witH NVIDIA.
4:37 p.m.
On Mon, 2024-04-22 at 15:47 -0400, Robert McBroom wrote:
NVIDIA
Seems all nvidia legacy drivers don't support wayland, neither the
kernel option "simpledrm", simpledrm is enabled by default in kernel
and in Nvidia legacy was disable recently with an hack in Fedora kernel
[1] , If nvidia-drm.modeset=1 . The other option is disable nividia-
drm.modeset (which is put video in vga mode) .
So the only good option to not break is use kde-x11 , I guess.
[1}
https://gitlab.com/cki-project/kernel-ark/-/commit/43f3e284f6c98c0cb6133a...
--
Sérgio M. B.
2:29 a.m.
I don't remember that being a problem. Mouse movement in Wayland with
my nvidia card seemed ok. I'll have another look when I update to F40.
Mark
On Mon, 2024-04-22 at 22:37 +0100, Sérgio Basto wrote:
> On Mon, 2024-04-22 at 15:47 -0400, Robert McBroom wrote:
> > NVIDIA
>
> Seems all nvidia legacy drivers don't support wayland, neither the
> kernel option "simpledrm", simpledrm is enabled by default in kernel
> and in Nvidia legacy was disable recently with an hack in Fedora
> kernel
> [1] , If nvidia-drm.modeset=1 . The other option is disable nividia-
> drm.modeset (which is put video in vga mode) .
> So the only good option to not break is use kde-x11 , I guess.
6:45 a.m.
Yeah a friend of mine has a 3070ti and he was suffering from massive
stutterings in wayland. For now, he is forced to remain in xorg, but
hopefully in a month or two when the problem is fixed, then hell be able to
go back in wayland
On Tue, Apr 23, 2024 at 03:30 Mark @ GMail <mrkr.st(a)gmail.com> wrote:
I don't remember that being a problem. Mouse movement in Wayland
with
my nvidia card seemed ok. I'll have another look when I update to F40.
Mark
On Mon, 2024-04-22 at 22:37 +0100, Sérgio Basto wrote:
> On Mon, 2024-04-22 at 15:47 -0400, Robert McBroom wrote:
> > NVIDIA
>
> Seems all nvidia legacy drivers don't support wayland, neither the
> kernel option "simpledrm", simpledrm is enabled by default in kernel
> and in Nvidia legacy was disable recently with an hack in Fedora
> kernel
> [1] , If nvidia-drm.modeset=1 . The other option is disable nividia-
> drm.modeset (which is put video in vga mode) .
> So the only good option to not break is use kde-x11 , I guess.
--
_______________________________________________
kde mailing list -- kde(a)lists.fedoraproject.org
To unsubscribe send an email to kde-leave(a)lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
7:04 a.m.
On Tue, 2024-04-23 at 08:29 +0100, Mark @ GMail wrote:
I don't remember that being a problem. Mouse movement in
Wayland
with
my nvidia card seemed ok. I'll have another look when I update to
F40.
please check if you got simpledrm enabled
#dmesg | grep simple
[ 1.212839] [drm] Initialized simpledrm 1.0.0 20200625 for simple-framebuffer.0 on
minor 0
[ 1.213422] simple-framebuffer simple-framebuffer.0: [drm] fb0: simpledrmdrmfb frame
buffer device
Mark
On Mon, 2024-04-22 at 22:37 +0100, Sérgio Basto wrote:
> On Mon, 2024-04-22 at 15:47 -0400, Robert McBroom wrote:
> > NVIDIA
>
> Seems all nvidia legacy drivers don't support wayland, neither the
> kernel option "simpledrm", simpledrm is enabled by default in
> kernel
> and in Nvidia legacy was disable recently with an hack in Fedora
> kernel
> [1] , If nvidia-drm.modeset=1 . The other option is disable
> nividia-
> drm.modeset (which is put video in vga mode) .
> So the only good option to not break is use kde-x11 , I guess.
--
_______________________________________________
kde mailing list -- kde(a)lists.fedoraproject.org
To unsubscribe send an email to kde-leave(a)lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
--
Sérgio M. B.
8:01 a.m.
dmesg: read kernel buffer failed: Operation not permitted
On Tue, 2024-04-23 at 13:04 +0100, Sérgio Basto wrote:
>
> On Tue, 2024-04-23 at 08:29 +0100, Mark @ GMail wrote:
> > I don't remember that being a problem. Mouse movement in Wayland
> > with
> > my nvidia card seemed ok. I'll have another look when I update to
> > F40.
> >
>
> please check if you got simpledrm enabled
>
> #dmesg | grep simple
>
> [ 1.212839] [drm] Initialized simpledrm 1.0.0 20200625 for simple-
> framebuffer.0 on minor 0
> [ 1.213422] simple-framebuffer simple-framebuffer.0: [drm] fb0:
> simpledrmdrmfb frame buffer device
8:07 a.m.
On Tue, 2024-04-23 at 14:01 +0100, Mark @ GMail wrote:
dmesg: read kernel buffer failed: Operation not permitted
you need run dmesg as root or with sudo
On Tue, 2024-04-23 at 13:04 +0100, Sérgio Basto wrote:
>
> On Tue, 2024-04-23 at 08:29 +0100, Mark @ GMail wrote:
> > I don't remember that being a problem. Mouse movement in Wayland
> > with
> > my nvidia card seemed ok. I'll have another look when I update
> > to
> > F40.
> >
>
> please check if you got simpledrm enabled
>
> #dmesg | grep simple
>
> [ 1.212839] [drm] Initialized simpledrm 1.0.0 20200625 for
> simple-
> framebuffer.0 on minor 0
> [ 1.213422] simple-framebuffer simple-framebuffer.0: [drm] fb0:
> simpledrmdrmfb frame buffer device
--
_______________________________________________
kde mailing list -- kde(a)lists.fedoraproject.org
To unsubscribe send an email to kde-leave(a)lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
--
Sérgio M. B.
8:14 a.m.
Sorry, should've realised that.
[ 0.000000] The simpledrm driver will not be probed
On Tue, 2024-04-23 at 14:07 +0100, Sérgio Basto wrote:
>
> On Tue, 2024-04-23 at 14:01 +0100, Mark @ GMail wrote:
> > dmesg: read kernel buffer failed: Operation not permitted
>
> you need run dmesg as root or with sudo
>
> > On Tue, 2024-04-23 at 13:04 +0100, Sérgio Basto wrote:
> > >
> > > On Tue, 2024-04-23 at 08:29 +0100, Mark @ GMail wrote:
> > > > I don't remember that being a problem. Mouse movement in
> > > > Wayland
> > > > with
> > > > my nvidia card seemed ok. I'll have another look when I update
> > > > to
> > > > F40.
> > > >
> > >
> > > please check if you got simpledrm enabled
> > >
> > > #dmesg | grep simple
> > >
> > > [ 1.212839] [drm] Initialized simpledrm 1.0.0 20200625 for
> > > simple-
> > > framebuffer.0 on minor 0
> > > [ 1.213422] simple-framebuffer simple-framebuffer.0: [drm]
> > > fb0:
> > > simpledrmdrmfb frame buffer device
8:48 a.m.
** if your nvidia is not use a legacy driver **
as root run:
grubby --update-kernel=ALL --remove-args='nvidia-drm.modeset=1'
because nvidia-drm.modeset is automatically enabled and will enable
simpledrm
On Tue, 2024-04-23 at 14:14 +0100, Mark @ GMail wrote:
Sorry, should've realised that.
[ 0.000000] The simpledrm driver will not be probed
On Tue, 2024-04-23 at 14:07 +0100, Sérgio Basto wrote:
>
> On Tue, 2024-04-23 at 14:01 +0100, Mark @ GMail wrote:
> > dmesg: read kernel buffer failed: Operation not permitted
>
> you need run dmesg as root or with sudo
>
> > On Tue, 2024-04-23 at 13:04 +0100, Sérgio Basto wrote:
> > >
> > > On Tue, 2024-04-23 at 08:29 +0100, Mark @ GMail wrote:
> > > > I don't remember that being a problem. Mouse movement in
> > > > Wayland
> > > > with
> > > > my nvidia card seemed ok. I'll have another look when I
> > > > update
> > > > to
> > > > F40.
> > > >
> > >
> > > please check if you got simpledrm enabled
> > >
> > > #dmesg | grep simple
> > >
> > > [ 1.212839] [drm] Initialized simpledrm 1.0.0 20200625 for
> > > simple-
> > > framebuffer.0 on minor 0
> > > [ 1.213422] simple-framebuffer simple-framebuffer.0: [drm]
> > > fb0:
> > > simpledrmdrmfb frame buffer device
--
_______________________________________________
kde mailing list -- kde(a)lists.fedoraproject.org
To unsubscribe send an email to kde-leave(a)lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
--
Sérgio M. B.
3:04 a.m.
Errr, I'm not sure about this Sergio.
My Wayland setup (on F39) *was* working, fairly well.
Anyhow, given other comments here I've taken an early leap into F40. I
didn't see an option to switch KDE to X11 even if I'd wanted to (though
I didn't look hard). I'm now running F40 with Wayland and, so far, it
seems to be working fine.
Mark
On Tue, 2024-04-23 at 14:48 +0100, Sérgio Basto wrote:
>
> ** if your nvidia is not use a legacy driver **
>
> as root run:
>
> grubby --update-kernel=ALL --remove-args='nvidia-drm.modeset=1'
>
>
> because nvidia-drm.modeset is automatically enabled and will enable
> simpledrm
>
>
> On Tue, 2024-04-23 at 14:14 +0100, Mark @ GMail wrote:
> > Sorry, should've realised that.
> >
> > [ 0.000000] The simpledrm driver will not be probed
> >
> >
> > On Tue, 2024-04-23 at 14:07 +0100, Sérgio Basto wrote:
> > >
> > > On Tue, 2024-04-23 at 14:01 +0100, Mark @ GMail wrote:
> > > > dmesg: read kernel buffer failed: Operation not permitted
> > >
> > > you need run dmesg as root or with sudo
> > >
> > > > On Tue, 2024-04-23 at 13:04 +0100, Sérgio Basto wrote:
> > > > >
> > > > > On Tue, 2024-04-23 at 08:29 +0100, Mark @ GMail wrote:
> > > > > > I don't remember that being a problem. Mouse movement
in
> > > > > > Wayland
> > > > > > with
> > > > > > my nvidia card seemed ok. I'll have another look when
I
> > > > > > update
> > > > > > to
> > > > > > F40.
> > > > > >
> > > > >
> > > > > please check if you got simpledrm enabled
> > > > >
> > > > > #dmesg | grep simple
> > > > >
> > > > > [ 1.212839] [drm] Initialized simpledrm 1.0.0 20200625 for
> > > > > simple-
> > > > > framebuffer.0 on minor 0
> > > > > [ 1.213422] simple-framebuffer simple-framebuffer.0: [drm]
> > > > > fb0:
> > > > > simpledrmdrmfb frame buffer device
> > --
> > _______________________________________________
> > kde mailing list -- kde(a)lists.fedoraproject.org
> > To unsubscribe send an email to kde-leave(a)lists.fedoraproject.org
> > 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@lists.fedoraproject.org
> > Do not reply to spam, report it:
> > https://pagure.io/fedora-infrastructure/new_issue
>
> --
> Sérgio M. B.
> --
> _______________________________________________
> kde mailing list -- kde(a)lists.fedoraproject.org
> To unsubscribe send an email to kde-leave(a)lists.fedoraproject.org
> 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@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
6:33 a.m.
In case you're wondering, Wayland seems to work pretty well for me. It
looks like the Nouveau drivers have loaded rather than the NVidia ones,
but almost all seems good.
I think the problems I'm having may all be down to XScreensaver.
Everything I can find states that it shouldn't work under Wayland, but
it does, fairly well. It doesn't seem to recognise activity, so every
now and then it tries to take over the screen. It only seems to
recognise mouse click as activity. This is a small price to pay for
its lovely display functionality though.
Mark
On Tue, 2024-04-23 at 14:48 +0100, Sérgio Basto wrote:
>
> ** if your nvidia is not use a legacy driver **
>
> as root run:
>
> grubby --update-kernel=ALL --remove-args='nvidia-drm.modeset=1'
>
>
> because nvidia-drm.modeset is automatically enabled and will enable
> simpledrm
>
>
> On Tue, 2024-04-23 at 14:14 +0100, Mark @ GMail wrote:
> > Sorry, should've realised that.
> >
> > [ 0.000000] The simpledrm driver will not be probed
> >
> >
> > On Tue, 2024-04-23 at 14:07 +0100, Sérgio Basto wrote:
> > >
> > > On Tue, 2024-04-23 at 14:01 +0100, Mark @ GMail wrote:
> > > > dmesg: read kernel buffer failed: Operation not permitted
> > >
> > > you need run dmesg as root or with sudo
> > >
> > > > On Tue, 2024-04-23 at 13:04 +0100, Sérgio Basto wrote:
> > > > >
> > > > > On Tue, 2024-04-23 at 08:29 +0100, Mark @ GMail wrote:
> > > > > > I don't remember that being a problem. Mouse movement
in
> > > > > > Wayland
> > > > > > with
> > > > > > my nvidia card seemed ok. I'll have another look when
I
> > > > > > update
> > > > > > to
> > > > > > F40.
> > > > > >
> > > > >
> > > > > please check if you got simpledrm enabled
> > > > >
> > > > > #dmesg | grep simple
> > > > >
> > > > > [ 1.212839] [drm] Initialized simpledrm 1.0.0 20200625 for
> > > > > simple-
> > > > > framebuffer.0 on minor 0
> > > > > [ 1.213422] simple-framebuffer simple-framebuffer.0: [drm]
> > > > > fb0:
> > > > > simpledrmdrmfb frame buffer device
> > --
> > _______________________________________________
> > kde mailing list -- kde(a)lists.fedoraproject.org
> > To unsubscribe send an email to kde-leave(a)lists.fedoraproject.org
> > 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@lists.fedoraproject.org
> > Do not reply to spam, report it:
> > https://pagure.io/fedora-infrastructure/new_issue
>
> --
> Sérgio M. B.
> --
> _______________________________________________
> kde mailing list -- kde(a)lists.fedoraproject.org
> To unsubscribe send an email to kde-leave(a)lists.fedoraproject.org
> 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@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
1:53 p.m.
On Thursday, 18 April 2024 13.00.21 WEST Patrick O'Callaghan wrote:
I haven't seen that specifically, but I occasionally after
resuming
from hibernation the Plasma bar isn't there for some reason. Probably a
different issue from what you have, but it prompted me to create a
little script to restore it (from a suggestion of Rex Dieter):
#!/bin/sh
# Restart the Plasma workspace under KDE. Use if Plasma crashes or
# Autohide stops working.
http://forum.kde.org/viewtopic.php?f=67&t=87132&p=154341#p154341
# KDE list 06/01/2019 Rex Dieter <rdieter(a)gmail.com>
kquitapp5 plasmashell
killall plasmashell
kstart5 plasmashell &
No doubt it could be more elegant but it works.
poc
As far as I remember nowadays this should be enough:
plasmashell --replace
When I had these problems I ran that and it worked.
I am now using F40 and funnily it has been working. :-)
--
José Abílio Matos
4:15 p.m.
On Thu, 2024-04-18 at 19:53 +0100, José Abílio Matos wrote:
On Thursday, 18 April 2024 13.00.21 WEST Patrick O'Callaghan
wrote:
> I haven't seen that specifically, but I occasionally after resuming
> from hibernation the Plasma bar isn't there for some reason.
> Probably a
> different issue from what you have, but it prompted me to create a
> little script to restore it (from a suggestion of Rex Dieter):
>
> #!/bin/sh
> # Restart the Plasma workspace under KDE. Use if Plasma crashes
> or
> # Autohide stops working.
>
> http://forum.kde.org/viewtopic.php?f=67&t=87132&p=154341#p154341
>
> # KDE list 06/01/2019 Rex Dieter <rdieter(a)gmail.com>
> kquitapp5 plasmashell
> killall plasmashell
> kstart5 plasmashell &
>
> No doubt it could be more elegant but it works.
>
> poc
As far as I remember nowadays this should be enough:
plasmashell --replace
Good to know, thanks.
poc
6:38 a.m.
On Fri, 2024-04-19 at 11:43 +0200, Marc Deop i Argemí wrote:
On Thursday, 18 April 2024 20:53:36 CEST José Abílio Matos wrote:
> As far as I remember nowadays this should be enough:
>
> plasmashell --replace
Even better:
systemctl restart --user plasma-plasmashell
Very good :-)
poc
23
days inactive
32
days old
23 comments
8 participants
participants (8)
-
José Abílio Matos -
Marc Deop i Argemí -
Mark ＠ GMail -
Neal Gompa -
Patrick O'Callaghan -
Robert McBroom -
Steve Cossette -
Sérgio Basto