On Wed, Sep 25, 2024 at 08:25:12PM -0400, Eli Schwartz wrote
> I think the two of you are talking past each other. What did Arsen mean
> by "the vague concept of IPv6"? I suspect he meant:
>
> You are trying to solve a concrete user issue with your browsing.
Correct.
> Your idea of how to sol
On 9/25/24 6:21 PM, Walter Dnes wrote:
>> There is no reason to disable IPv6 support, as Eli said (especially if
>> yo do not know _what_ you're trying to disable, and are just trying to
>> blanket-disable a vague concept of IPv6).
>
> This is *NOT* about a "vague concept". This is about solvin
On 2024-09-24 21:42:23, Eli Schwartz wrote:
>
> Please do not disable the USE=ipv6, as that is *utterly* insane. It also
> does approximately nothing. In packages which support this USE flag,
> which is rare, it causes the code to use old, untested APIs which only
> support ipv4, rather than new,
On Wed, Sep 25, 2024 at 01:53:49PM +0200, Arsen Arsenović wrote
> I suspect your Firefox anecdote happened due to misconfiguration
> (I think network.http.fast-fallback-to-IPv4 dictates the use of this
> algorithm in Firefox).
I do not recall ever touching it in about:config. In my current
bro
On 9/25/24 7:26 AM, Eli Schwartz wrote:
On 9/25/24 6:00 AM, Walter Dnes wrote:
>My system is actually very stable. In the shitstorm that erupted on
> this list at "ipv6" enabling I did not see any mention of sysctl. In my
> /etc/default/grub file I have...
>
> GRUB_CMDLINE_LINUX_DEFAULT
On 9/25/24 6:00 AM, Walter Dnes wrote:
> My system is actually very stable. In the shitstorm that erupted on
> this list at "ipv6" enabling I did not see any mention of sysctl. In my
> /etc/default/grub file I have...
>
> GRUB_CMDLINE_LINUX_DEFAULT="noexec=on net.ifnames=0 ipv6.disable=1"
>
>
Walter Dnes writes:
> On Tue, Sep 24, 2024 at 09:42:23PM -0400, Eli Schwartz wrote
>
>> If you actually want to disable ipv6, instead of insanely rebuilding
>> binaries to use untested broken segfaulting code, use the sysctl
>> knob to tell the kernel "when asked to give some application a bit
>>
On Tue, Sep 24, 2024 at 09:42:23PM -0400, Eli Schwartz wrote
> If you actually want to disable ipv6, instead of insanely rebuilding
> binaries to use untested broken segfaulting code, use the sysctl
> knob to tell the kernel "when asked to give some application a bit
> of internet traffic, don't u
On 9/24/24 6:00 PM, Walter Dnes wrote:
> On Mon, Sep 23, 2024 at 05:11:14PM -0400, Eli Schwartz wrote
>
>> Do you have that little faith in the Gentoo Developers, that you
>> think we'd make a USE flag change that made everyone's systems
>> suddenly break?
>>
>> :(
>
> I was around way back whe
On 24/9/24 19:46, Mitchell Dorrell wrote:
Do you specifically use the closed-source drivers, though?
Yes. In both the 'kernel-open' and regular flavours.
On 24/09/2024 19:32, k...@aspodata.se wrote:
So should computer words be defined by non-professionals or thoose
who knows ?
Well, before computers, I thought servers worked in restaurants ...
(And what the hell are thoose :-)
One effect of letting non-professionals define words is the case w
On Mon, Sep 23, 2024 at 05:11:14PM -0400, Eli Schwartz wrote
> Do you have that little faith in the Gentoo Developers, that you
> think we'd make a USE flag change that made everyone's systems
> suddenly break?
>
> :(
I was around way back when "ipv6" became the default. I was using
Firefox b
Wol:
> On 23/09/2024 23:53, k...@aspodata.se wrote:
> > It's just the pc hoard that thinks a server is some machine handling
(that should be horde, not hoard even though it sounds funny...)
> > databases, mail, files, printers or what
>
> In other words, X uses the words the other way round than m
Alan,
On Mon, 23 Sep 2024 22:08:56 + you wrote:
> ...
> For example, emerge
> --depclean on my system wants to unmerge openrc. Not a deliberate move
> by the developers, just some accident. But it's the reason I don't do
> emerge --depclean, ever
On Mon, Sep 23, 2024 at 9:13 PM Matt Jolly wrote:
> On 24/9/24 10:52, Mitchell Dorrell wrote:
>
> > I run a four-monitor system using NVIDIA's closed-source drivers. Last
> > I heard, Wayland did not work with such a combination. Has that
> > changed?
>
> I run several 3-monitor NVIDIA setups on W
On 23/09/2024 23:53, k...@aspodata.se wrote:
It's just the pc hoard that thinks a server is some machine handling
databases, mail, files, printers or what
In other words, X uses the words the other way round than most people -
what I said.
Doesn't mean the majority are right! As far as I'm a
On 9/23/24 8:52 PM, Mitchell Dorrell wrote:
> I run a lean X system for desktop workflows, with USE="-wayland".
> Every unconditional dev-libs/wayland dependency I've encountered has
> used dlopen. These were proprietary binary applications like Zoom and
> Slack. On an X system, they work completel
On 24/9/24 10:52, Mitchell Dorrell wrote:
I run a four-monitor system using NVIDIA's closed-source drivers. Last
I heard, Wayland did not work with such a combination. Has that
changed?
I run several 3-monitor NVIDIA setups on Wayland with no issue.
One of my 4-monitor setups has one scree
On Mon, Sep 23, 2024 at 5:11 PM Eli Schwartz wrote:
> The resulting packages pull in support libraries that implement both
> technologies. This is (usually, absent dlopen tricks) a fundamental
> requirement of "ld.so", the runtime loader: if you compile support for
> it, you have to have it instal
On Mon, 2024-09-23 at 22:08 +, Alan Mackenzie wrote:
>
> But the unused code still gets built in, doesn't it? That's a somewhat
> un-gentoo like situation.
>
It depends on the language, but in a compiled language, not usually.
Regardless: if you aren't a fan of widespread changes to global
On 9/23/24 6:08 PM, Alan Mackenzie wrote:
>> Do you have that little faith in the Gentoo Developers, that you think
>> we'd make a USE flag change that made everyone's systems suddenly break?
>
> It happens, from time to time, by accident. For example, emerge
> --depclean on my system wants to un
Wol:
...
> X comes in two halves, the front end (or server, they use the words the
> other way round to normal),
...
No, server is a software concept, a program that waits and responds to
inbound calls, the X-server is just that. A client is a program/user
that pokes at the server and get respon
Hello, Eli.
On Mon, Sep 23, 2024 at 17:11:14 -0400, Eli Schwartz wrote:
> On 9/23/24 4:14 PM, Alan Mackenzie wrote:
> > Hello, Gentoo.
> > I got a nasty shock earlier on this evening when I was updating my
> > (still newish) system. Around (perhaps) 70 packages to be updated or
> > reloaded, sev
On 23/09/2024 21:14, Alan Mackenzie wrote:
What on Earth is going on? I never asked for wayland, and I haven't
received any news items about it in the last few weeks. I know little
about this X substitute, but one thing's vitually certain; that
installing it as emerge intended would lead to a l
Hello, Alan,
Alan Mackenzie writes:
> Hello, Gentoo.
>
> I got a nasty shock earlier on this evening when I was updating my
> (still newish) system. Around (perhaps) 70 packages to be updated or
> reloaded, several of them big packages. What's going on?
>
> There were lots of qt and kde packag
On 9/23/24 4:14 PM, Alan Mackenzie wrote:
> Hello, Gentoo.
>
> I got a nasty shock earlier on this evening when I was updating my
> (still newish) system. Around (perhaps) 70 packages to be updated or
> reloaded, several of them big packages. What's going on?
>
> There were lots of qt and kde p
Hello, Gentoo.
I got a nasty shock earlier on this evening when I was updating my
(still newish) system. Around (perhaps) 70 packages to be updated or
reloaded, several of them big packages. What's going on?
There were lots of qt and kde packages being sucked in. But what stood
out prominently
On Friday 6 September 2024 11:41:03 BST Michael wrote:
> You could have inadvertently cleaned this package from your
> /var/lib/portage/ world, or unmerged it for some reason.
No, nothing like that. The sources and config files were all present, but the
extra_firmware entries had been deleted.
On Friday 6 September 2024 10:45:26 BST Peter Humphrey wrote:
> On Friday 6 September 2024 10:10:47 BST Michael wrote:
> > On Friday 6 September 2024 01:33:04 BST Peter Humphrey wrote:
> > > On Friday 6 September 2024 00:21:31 BST Peter Humphrey wrote:
> > > > I think I know what it is: the kernel'
On Friday 6 September 2024 10:10:47 BST Michael wrote:
> On Friday 6 September 2024 01:33:04 BST Peter Humphrey wrote:
> > 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
On Friday 6 September 2024 01:33:04 BST Peter Humphrey wrote:
> 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
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 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
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
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
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
> >
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
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.
I need hardly say this doesn't make a responsive system.
--
Regards,
Peter.
On 20/11/2021 19:59, Wol wrote:
Okay, I rebooted the system, and tried to start Wayland. The first log
is the output of my first attempt. This hung and I had to kill it.
Actually, it was worse than that, caused the video
driver or somesuch to crash - I ended up with a scrambled display, and
On 17/11/2021 23:54, Jack wrote:
On 2021.11.14 17:51, Wol wrote:
I'm still trying to get Wayland to work reliably. At the moment I log
in at a TTY, then fire it up with "startplasma-wayland" ... except it
doesn't start properly!
Seems to work fine for me (with minimal testing.)
I'm GUESSING
On 2021.11.14 17:51, Wol wrote:
I'm still trying to get Wayland to work reliably. At the moment I log
in at a TTY, then fire it up with "startplasma-wayland" ... except it
doesn't start properly!
Seems to work fine for me (with minimal testing.)
I'm GUESSING part of the problem is my video
On 17/11/2021 20:59, Wol wrote:
On 17/11/2021 19:13, Marco Rebhan wrote:
On Sunday, 14 November 2021 23:51:37 CET Wol wrote:
I'm still trying to get Wayland to work reliably. At the moment I log
in at a TTY, then fire it up with "startplasma-wayland" ... except it
doesn't start properly!
Have
On 17/11/2021 19:13, Marco Rebhan wrote:
On Sunday, 14 November 2021 23:51:37 CET Wol wrote:
I'm still trying to get Wayland to work reliably. At the moment I log
in at a TTY, then fire it up with "startplasma-wayland" ... except it
doesn't start properly!
Have you tried starting it with "dbus
On 2021.11.14 17:51, Wol wrote:
I'm still trying to get Wayland to work reliably. At the moment I log
in at a TTY, then fire it up with "startplasma-wayland" ... except it
doesn't start properly!
I'm GUESSING part of the problem is my video card isn't set up
properly. But I thought I'd fol
I'm still trying to get Wayland to work reliably. At the moment I log in
at a TTY, then fire it up with "startplasma-wayland" ... except it
doesn't start properly!
I'm GUESSING part of the problem is my video card isn't set up properly.
But I thought I'd followed the gentoo guide, and compiled
On Monday, 28 December 2020 00:10:54 GMT Michael wrote:
> On Sunday, 27 December 2020 21:01:09 GMT antlists wrote:
> > On 27/12/2020 18:51, Michael wrote:
> > > Restarting the desktop using Xorg does NOT fix this problem. Otherwise,
> > > both Plasma on Wayland and Xorg work fine - except the clip
On Sunday, 27 December 2020 21:01:09 GMT antlists wrote:
> On 27/12/2020 18:51, Michael wrote:
> > Restarting the desktop using Xorg does NOT fix this problem. Otherwise,
> > both Plasma on Wayland and Xorg work fine - except the clipboard does not
> > work on Wayland (middle click won't paste sel
On 27/12/2020 18:51, Michael wrote:
Restarting the desktop using Xorg does NOT fix this problem. Otherwise, both
Plasma on Wayland and Xorg work fine - except the clipboard does not work on
Wayland (middle click won't paste selected text on another window).
This sounds to me like a side-effect
I tried launching Plasma on Wayland and noticed on Kmail the message preview
pane was black. As I move the mouse around or click on it, the black preview
window becomes transparent and the desktop wallpaper or other windows behind
Kmail appear, but it can flip back to black if I continue moving
Am 2017-07-11 um 13:37 schrieb Rasmus Thomsen:
> Hello,
>
> I use GNOME with Wayland for some time and I actually didn't notice that
> I switched until I tried to get synergy working ( mouse sharing
> software, which only works on X ), seems like GDM automatically chose
> Wayland since some upgrad
On Tuesday 11 Jul 2017 09:02:59 Rich Freeman wrote:
> On Tue, Jul 11, 2017 at 7:37 AM, Rasmus Thomsen
>
> wrote:
> > I use GNOME with Wayland for some time and I actually didn't notice that I
> > switched until I tried to get synergy working ( mouse sharing software,
> > which only works on X ),
On Tue, Jul 11, 2017 at 7:37 AM, Rasmus Thomsen
wrote:
>
> I use GNOME with Wayland for some time and I actually didn't notice that I
> switched until I tried to get synergy working ( mouse sharing software,
> which only works on X ), seems like GDM automatically chose Wayland since
> some upgrade
Hello,
I use GNOME with Wayland for some time and I actually didn't notice that I
switched until I tried to get synergy working ( mouse sharing software, which
only works on X ), seems like GDM automatically chose Wayland since some
upgrade. XWayland works pretty seamlessly as well, so I'll jus
Hi All,
Reading about Wayland as the next big architectural switch in windowing for
Linux, I have been thinking if it is time to switch to Wayland. I don't know
if Wayland will be the way the Linux desktop will be running in the future, if
there will be a migration path to it, a big switch ove
Am 25.07.2014 06:32, schrieb Pavel Volkov:
> On Tuesday, July 22, 2014 1:40:36 AM MSK, James wrote:
>> Bloatware like gnome and KDE will be the last to get QT5, Wayland and a
>> myriad of new, super_fast, secure desktop toys, imho.
>
> Well, KDE is already on Qt 5.
> Strictly speaking, there's no
On Tuesday, July 22, 2014 1:40:36 AM MSK, James wrote:
Bloatware like gnome and KDE will be the last to get QT5, Wayland and a
myriad of new, super_fast, secure desktop toys, imho.
Well, KDE is already on Qt 5.
Strictly speaking, there's no "KDE" or "KDE SC" anymore.
There are 3 separate projec
Anyone playing with wayland already?
Maybe even using it as "daily driver" ?
I did some steps to compile and use it on my systems ... so far I wasn't
able to start up gnome 3.12 (~ gnome-shell) with gdm here.
Is it possible already?
Stefan
61 matches
Mail list logo
