Michael wrote:
> On Thursday 5 September 2024 15:34:06 BST Dale wrote:
>> Michael wrote:
>>> Since I upgraded to KDE Frameworks 6 I have observed some rather unwanted
>>> window behaviours.
>>>
>>> 1. Window Interaction with Gkrellm
>>>
>>> DESIRED BEHAVIOUR:
>>> ==
>>> I have Gkrel
Michael wrote:
> On Thursday 5 September 2024 19:55:56 BST Frank Steinmetzger wrote:
>> Am Thu, Sep 05, 2024 at 06:30:54AM -0500 schrieb Dale:
Use rsync with:
--checksum
and
--dry-run
>> I suggest calculating a checksum file from your active files. Then you don’t
>>
On Friday 6 September 2024 00:21:31 BST Peter Humphrey wrote:
> I think I know what it is: the kernel's list of firmware blobs is empty. I
> don't know where they all went, but it shouldn't be too hard to find them.
Indeed it was so. Now fixed and working fine.
--
Regards,
Peter.
On Thursday 5 September 2024 22:29:14 BST Michael wrote:
> At a simple level you can check this file for any obvious problem:
>
> ~/.local/share/sddm/wayland-session.log
>
> Your symptom could be related to software rendering used by the kwin
> compositor, as opposed to OpenGL. Mesa with approp
On Thu, Sep 5, 2024 at 12:00 PM Peter Humphrey
wrote:
>
> On Thursday 5 September 2024 15:43:00 BST Iwrote:
> > On Thursday 5 September 2024 13:47:29 BST I wrote:
> > > ... Perhaps I should start recompiling things...
> >
> > After an emerge -e1 kwayland plasma-workspace and a reboot,
kwin_wayland
On Thursday 5 September 2024 19:55:56 BST Frank Steinmetzger wrote:
> Am Thu, Sep 05, 2024 at 06:30:54AM -0500 schrieb Dale:
> > > Use rsync with:
> > > --checksum
> > >
> > > and
> > >
> > > --dry-run
>
> I suggest calculating a checksum file from your active files. Then you don’t
> have to r
On Thursday 5 September 2024 20:00:12 BST Peter Humphrey wrote:
> On Thursday 5 September 2024 15:43:00 BST Iwrote:
> > On Thursday 5 September 2024 13:47:29 BST I wrote:
> > > ... Perhaps I should start recompiling things...
> >
> > After an emerge -e1 kwayland plasma-workspace and a reboot, kwin
Thanks Jack,
On Thursday 5 September 2024 21:30:54 BST Jack wrote:
> On 2024.09.05 09:22, Michael wrote:
> > Since I upgraded to KDE Frameworks 6 I have observed some rather
> > unwanted
> > window behaviours.
> >
> > 1. Window Interaction with Gkrellm
>
> [snipped lots ]
>
> The latest rel
On 2024.09.05 09:22, Michael wrote:
Since I upgraded to KDE Frameworks 6 I have observed some rather
unwanted
window behaviours.
1. Window Interaction with Gkrellm
[snipped lots ]
The latest release of gkrellm seems to have been over three years ago,
and unfortunately, I suspect there
On Thursday 5 September 2024 15:43:00 BST Iwrote:
> On Thursday 5 September 2024 13:47:29 BST I wrote:
> > ... Perhaps I should start recompiling things...
>
> After an emerge -e1 kwayland plasma-workspace and a reboot, kwin_wayland is
> down to 20-60% CPU and plasma_shell is barely visible in /to
Am Thu, Sep 05, 2024 at 06:30:54AM -0500 schrieb Dale:
> > Use rsync with:
> >
> > --checksum
> >
> > and
> >
> > --dry-run
I suggest calculating a checksum file from your active files. Then you don’t
have to read the files over and over for each backup iteration you compare
it against.
> >
On Thursday 5 September 2024 15:34:06 BST Dale wrote:
> Michael wrote:
> > Since I upgraded to KDE Frameworks 6 I have observed some rather unwanted
> > window behaviours.
> >
> > 1. Window Interaction with Gkrellm
> >
> > DESIRED BEHAVIOUR:
> > ==
> > I have Gkrellm started up by
On Thursday 5 September 2024 16:08:36 BST Peter Humphrey wrote:
> On Thursday 5 September 2024 07:32:21 BST I wrote:
> > Has anyone else seen grossly excessive CPU load since adopting the new
> > Wayland way of doing things? /Top/ is showing 1300% going on kwin_wayland
> > and the whole of the rest
On Thursday 5 September 2024 07:32:21 BST I wrote:
> Has anyone else seen grossly excessive CPU load since adopting the new
> Wayland way of doing things? /Top/ is showing 1300% going on kwin_wayland
> and the whole of the rest going on plasmashell.
Another thing: the plasma system is not preserv
On Thursday 5 September 2024 13:47:29 BST I wrote:
> ... Perhaps I should start recompiling things...
After an emerge -e1 kwayland plasma-workspace and a reboot, kwin_wayland is
down to 20-60% CPU and plasma_shell is barely visible in /top/.
Much improved, but it still isn't right.
--
Regards
Michael wrote:
> Since I upgraded to KDE Frameworks 6 I have observed some rather unwanted
> window behaviours.
>
> 1. Window Interaction with Gkrellm
>
> DESIRED BEHAVIOUR:
> ==
> I have Gkrellm started up by Plasma at login and placed at the top left of
> the
> screen. I can't
Since I upgraded to KDE Frameworks 6 I have observed some rather unwanted
window behaviours.
1. Window Interaction with Gkrellm
DESIRED BEHAVIOUR:
==
I have Gkrellm started up by Plasma at login and placed at the top left of the
screen. I can't remember where/how I set this up,
On Thursday 5 September 2024 08:50:39 BST Michael wrote:
> On Thursday 5 September 2024 07:32:21 BST Peter Humphrey wrote:
> > Greetings,
> >
> > Has anyone else seen grossly excessive CPU load since adopting the new
> > Wayland way of doing things? /Top/ is showing 1300% going on kwin_wayland
> >
Michael wrote:
> On Thursday 5 September 2024 11:53:16 BST Dale wrote:
>>
>> I made my backups last weekend. I'm sure it was working fine then.
>> After all, it would have failed to compile packages if it was bad. I'm
>> thinking about checking against that copy like you mentioned but I have
>>
On Thursday 5 September 2024 11:53:16 BST Dale wrote:
> Michael wrote:
> > On Thursday 5 September 2024 09:36:36 BST Dale wrote:
> >> I've ran fsck before mounting on every file system so far. I ran it on
> >> the OS file systems while booted from the Live image. The others I just
> >> did before
Frank Steinmetzger wrote:
> Am Thu, Sep 05, 2024 at 10:36:19AM +0100 schrieb Michael:
>
>>> Maybe that it only catches 1-bit errors, but Dale has more broken bits?
>> Or it could be Dale's kit is DDR4?
> You may be right. We talked about AM5 at great length during the concept
> phase and then I th
Michael wrote:
> On Thursday 5 September 2024 09:36:36 BST Dale wrote:
>
>> I've ran fsck before mounting on every file system so far. I ran it on
>> the OS file systems while booted from the Live image. The others I just
>> did before mounting. I realize this doesn't mean the files themselves
>
Michael wrote:
> On Thursday 5 September 2024 08:36:46 BST Dale wrote:
>> Dale wrote:
>>> Howdy,
>>>
>>> I don't do emerge -e world very often but this is weird. This is the
>>> complaint emerge spits out:
>>>
>>>
>>>
>>> !!! The following update(s) have been skipped due to unsatisfied
>>> depende
Am Thu, Sep 05, 2024 at 10:36:19AM +0100 schrieb Michael:
> > Maybe that it only catches 1-bit errors, but Dale has more broken bits?
>
> Or it could be Dale's kit is DDR4?
You may be right. We talked about AM5 at great length during the concept
phase and then I think I actually asked back beca
On Thursday 5 September 2024 10:08:08 BST Frank Steinmetzger wrote:
> Am Wed, Sep 04, 2024 at 11:38:01PM +0100 schrieb Michael:
> > Some MoBos are more tolerant than others.
> >
> > Regarding Dale's question, which has already been answered - yes, anything
> > the bad memory has touched is suspect
Am Wed, Sep 04, 2024 at 11:38:01PM +0100 schrieb Michael:
> Some MoBos are more tolerant than others.
> Regarding Dale's question, which has already been answered - yes, anything
> the
> bad memory has touched is suspect of corruption. Without ECC RAM a dodgy
> module can cause a lot of damag
On Thursday 5 September 2024 09:36:36 BST Dale wrote:
> I've ran fsck before mounting on every file system so far. I ran it on
> the OS file systems while booted from the Live image. The others I just
> did before mounting. I realize this doesn't mean the files themselves
> are OK but at least
Michael wrote:
> On Thursday 5 September 2024 01:11:13 BST Dale wrote:
>
>> When I built this rig, I first booted the Gentoo Live boot image and
>> just played around a bit. Mostly to let the CPU grease settle in a
>> bit. Then I ran memtest through a whole test until it said it passed.
>> Only
On Thursday 5 September 2024 08:36:46 BST Dale wrote:
> Dale wrote:
> > Howdy,
> >
> > I don't do emerge -e world very often but this is weird. This is the
> > complaint emerge spits out:
> >
> >
> >
> > !!! The following update(s) have been skipped due to unsatisfied
> > dependencies
> > !!!
On Thursday 5 September 2024 01:11:13 BST Dale wrote:
> When I built this rig, I first booted the Gentoo Live boot image and
> just played around a bit. Mostly to let the CPU grease settle in a
> bit. Then I ran memtest through a whole test until it said it passed.
> Only then did I start worki
On Thursday 5 September 2024 07:32:21 BST Peter Humphrey wrote:
> Greetings,
>
> Has anyone else seen grossly excessive CPU load since adopting the new
> Wayland way of doing things? /Top/ is showing 1300% going on kwin_wayland
> and the whole of the rest going on plasmashell.
Ouch! No, this is
Dale wrote:
> Howdy,
>
> I don't do emerge -e world very often but this is weird. This is the
> complaint emerge spits out:
>
>
>
> !!! The following update(s) have been skipped due to unsatisfied
> dependencies
> !!! triggered by backtracking:
>
> x11-drivers/nvidia-drivers:0
> x11-base/xorg-driv
32 matches
Mail list logo
