flathub / flathub/com.google.Chrome
Google Chrome Flatpak crashes on Nobara 43 with AMD GPU
- Dominant language
- Shell
- Stars
- 67
- Forks
- 39
- Avg merge
- 6h 48m
- Merged PRs (30d)
- 7
Description
## Summary
Google Chrome Flatpak (com.google.Chrome) crashes immediately on launch with SIGBUS (signal 7) on Nobara Linux 43 with AMD Radeon GPU.
## System Information
### OS:
ID=nobara
VERSION_ID=43
PRETTY_NAME="Nobara Linux 43 (KDE Plasma Desktop Edition)"
### Desktop Environment:
x11
### GPU:
OpenGL renderer string: AMD Radeon RX 6600 XT (radeonsi, navi23, LLVM 21.1.7, DRM 3.64, 6.18.6-200.nobara.fc43.x86_64)
### Chrome Flatpak Version:
Google Chrome com.google.Chrome 144.0.7559.96-1 stable user
## Steps to Reproduce
1. Install Chrome Flatpak: `flatpak install com.google.Chrome`
2. Launch Chrome: `flatpak run com.google.Chrome`
3. Application crashes immediately
## Actual Behavior
Chrome crashes with SIGBUS (signal 7) - memory bus error. The crash occurs consistently every time.
## Expected Behavior
Chrome should launch and display the browser window.
## Workaround
Native Chrome RPM installation works correctly:
```bash
wget https://dl.google.com/linux/direct/google-chrome-stable_current_x86_64.rpm
sudo dnf install google-chrome-stable_current_x86_64.rpm
```
## Crash Details
From coredumpctl:
```
Signal: 7 (BUS)
Command: /app/extra/chrome --disable-features=VizDisplayCompositor,WebAssemblyTrapHandler,DesktopPWAsRunOnOsLogin --disable-gpu --in-process-gpu --disable-crash-reporter
```
Stack trace shows crash at offset 0x614504d in chrome binary.
## Additional Context
- Native Chrome RPM (144.0.7559.109) works perfectly on the same system
- Issue appears specific to Flatpak build + AMD GPU + Nobara 43
- Similar issues may affect other Fedora 43-based distributions
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the crash with `flatpak run com.google.Chrome` on Nobara Linux 43 using an AMD Radeon GPU, then inspect the coredump with `coredumpctl` and compare it with the working native RPM. Check whether the failure is specific to the Flatpak runtime, Chrome build, or GPU configuration; done means the Flatpak launches successfully or the required upstream diagnosis is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100