firefox no longer starts - could it be wayland package?
Running on gnome This may have to do with updated updated wayland package (1.22.0-1) - didn't see much else that may be related. I tried rolling back firefox and makes no difference - I also tried with and without MOZ_ENABLE_WAYLAND - always get instant crash with: ExceptionHandler::GenerateDump cloned child 5628 ExceptionHandler::SendContinueSignalToChild sent continue signal to child ExceptionHandler::WaitForContinueSignal waiting for continue signal... Anyone else seeing similar and any suggestions for fix? thanks gene
On 4/7/23 09:22, Genes Lists wrote:
Running on gnome
This may have to do with updated updated wayland package (1.22.0-1) -
I confirm the problem goes away if I roll wayland back to prev version (1.21.0-2) So indeed the problem package is wayland.
On 4/7/23 09:27, Genes Lists wrote: Closing the loop - this is now been fixed by mesa 23.0.2 in testing repo. Big thanks to heftig for sorting it out so quickly! gene
This may have to do with updated updated wayland package (1.22.0-1) - didn't see much else that may be related. I tried rolling back firefox and makes no difference - I also tried with and without MOZ_ENABLE_WAYLAND - always get instant crash with:
ExceptionHandler::GenerateDump cloned child 5628 ExceptionHandler::SendContinueSignalToChild sent continue signal to child ExceptionHandler::WaitForContinueSignal waiting for continue signal...
Anyone else seeing similar and any suggestions for fix?
Can confirm the exact same behavior on my end. Updated all packages yesterday evening, and both Firefox and Thunderbird crash on startup unless I explicitly enable safe mode. Running wayland 1.22.0-1, firefox-developer-edition 112.0b9-1 and thunderbird 102.9.1-1. My wayland compositor is swayfx 0.2-2. Best, Petr
On 4/7/23 09:31, Petr Mánek wrote: See also: https://bugs.archlinux.org/task/78137 Best I can tell there are 2 (possibly related) issues - (a) firefox crashes on start and (b) firefox crashes on exit. Course to get to (b) you have to not experience (a) :) gene
On Fri, Apr 07, 2023 at 01:31:29PM +0000, Petr Mánek wrote:
This may have to do with updated updated wayland package (1.22.0-1) - didn't see much else that may be related. I tried rolling back firefox and makes no difference - I also tried with and without MOZ_ENABLE_WAYLAND - always get instant crash with:
ExceptionHandler::GenerateDump cloned child 5628 ExceptionHandler::SendContinueSignalToChild sent continue signal to child ExceptionHandler::WaitForContinueSignal waiting for continue signal...
Anyone else seeing similar and any suggestions for fix?
Can confirm the exact same behavior on my end. Updated all packages yesterday evening, and both Firefox and Thunderbird crash on startup unless I explicitly enable safe mode.
Running wayland 1.22.0-1, firefox-developer-edition 112.0b9-1 and thunderbird 102.9.1-1. My wayland compositor is swayfx 0.2-2.
Best, Petr
I'm not having any problems with Firefox/Thunderbird; or any other application that runs under wayland/sway. sway 1:1.8.1-1 wayland 1.22.0-1 firefox 111.0.1-1 thunderbird 102.9.1-1 Merell -- To stay young requires unceasing cultivation of the ability to unlearn old falsehoods. -- Lazarus Long, "Time Enough For Love"
On Fri, Apr 7, 2023 at 2:56 PM Merell L. Matlock, Jr.
On Fri, Apr 07, 2023 at 01:31:29PM +0000, Petr Mánek wrote:
This may have to do with updated updated wayland package (1.22.0-1) - didn't see much else that may be related. I tried rolling back firefox and makes no difference - I also tried with and without MOZ_ENABLE_WAYLAND - always get instant crash with:
ExceptionHandler::GenerateDump cloned child 5628 ExceptionHandler::SendContinueSignalToChild sent continue signal to child ExceptionHandler::WaitForContinueSignal waiting for continue signal...
Anyone else seeing similar and any suggestions for fix?
Can confirm the exact same behavior on my end. Updated all packages yesterday evening, and both Firefox and Thunderbird crash on startup unless I explicitly enable safe mode.
Running wayland 1.22.0-1, firefox-developer-edition 112.0b9-1 and thunderbird 102.9.1-1. My wayland compositor is swayfx 0.2-2.
Best, Petr
I'm not having any problems with Firefox/Thunderbird; or any other application that runs under wayland/sway.
sway 1:1.8.1-1 wayland 1.22.0-1 firefox 111.0.1-1 thunderbird 102.9.1-1
Merell -- To stay young requires unceasing cultivation of the ability to unlearn old falsehoods. -- Lazarus Long, "Time Enough For Love"
I only have the issue that both Firefox and Thunderbox crash on exit with Wayland 1.22.0-1 running in the Plasma desktop as a wayland session. Downgrading wayland back to 1.21.0-2 also fixes this issue for me, and both firefox and thunderbird (beta) no longer crash on exit. I am on firefox 111.0.1-1 and thunderbird 112.0b7 -- mike c
"Merell L. Matlock, Jr."
[[PGP Signed Part:Undecided]]
[...]
I'm not having any problems with Firefox/Thunderbird; or any other application that runs under wayland/sway.
sway 1:1.8.1-1 wayland 1.22.0-1 firefox 111.0.1-1 thunderbird 102.9.1-1
[...] Firefox 111.0.1 is working fine on Hyprland too, -- Thanos https://thanosapollo.com
On Fri, 2023-04-07 at 18:20 +0300, Thanos Apollo wrote:
Firefox 111.0.1 is working fine on Hyprland too,
Why does nobody mention the used hardware? The used compositor, browser software etc. are interacting with the hardware!
Ralf Mardorf
On Fri, 2023-04-07 at 18:20 +0300, Thanos Apollo wrote:
Firefox 111.0.1 is working fine on Hyprland too,
Why does nobody mention the used hardware? The used compositor, browser software etc. are interacting with the hardware!
True, should have mentioned /but I think it'd be more important to have people that actually have issues with it instead of me./ All applications I'm using are working fine on Hyprland using the following hardware: Laptops: - Thinkpad x220 - Thinkpad T460 Desktop with: - CPU: AMD Ryzen 7 5800X - GPU: AMD ATI Radeon -- Thanos https://thanosapollo.com
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
PS: The new GPU I'm using even prevents from enabling legacy boot! The vendor of my new mobo confirmed that using the same CPU with another graphics allows to enable legacy boot. Since issues already start at BIOS level, I'm not surprised that operating systems and software make a big difference, especially when using operating systems and software that are not well supported by vendors, if supported at all.
participants (6)
-
Genes Lists
-
Merell L. Matlock, Jr.
-
Mike Cloaked
-
Petr Mánek
-
Ralf Mardorf
-
Thanos Apollo