Re: firefox no longer starts - could it be wayland package?

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



On Fri, 2023-04-07 at 09:22 -0400, Genes Lists wrote:
> This may have to do with updated updated wayland package (1.22.0-1) - 
> didn't see much else that may be related.

Hi,

I'm migrating from old Intel to new Intel hardware. Firefox works very
well on both X11 machines, but Falkon as well as Chrome behave
completely different, depending on the used graphics driver (in case of
my GPU and X11 intel or modesetting) and kernel version.

Since you are in favour of Wayland, I suspect that the used browser, GPU
and kernel version are related to the issue, too.

Keep in mind that web browser nowadays are usually the most bloated and
GPU dependent software we usually run on desktop machines and hardware
support isn't good for Linux.

IOW unless Wayland isn't the the Holy Grail, I suspect a combination of
used hardware, Wayland, kernel and browser. In my experiences the
combination of hardware, X11, kernel and used browser makes a big
difference. Why should it be different when replacing the established
X11 with the half-baked Wayland?

Regards,
Ralf




[Index of Archives]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]

  Powered by Linux