Closed Bug 1803066 Opened 2 years ago Closed 2 years ago

[flatpak] webrtc share screen causes instant crash on Gnome: Crash in [@ libpipewire-0.3.so.0@0x9021e ] with address 0x0000000000000000

Categories

(Core :: WebRTC, defect)

Firefox 107
x86_64
Linux
defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: berend, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: crash)

Crash Data

Attachments

(1 file)

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:107.0) Gecko/20100101 Firefox/107.0

Steps to reproduce:

Open google meet
Share screen

Actual results:

The share screen dialog pops up, asking entire screen or just a single application. The only valid choice on Linux is entire screen. Choosing entire screen instantly crashes firefox

Expected results:

The screen should be shared

Failing that, an error should be displayed that shows that sharing the screen is not possible.

The Bugbug bot thinks this bug should belong to the 'Core::WebRTC' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → WebRTC
Product: Firefox → Core

Likely a dupe of bug 1803016, which is in triage.

See Also: → 1803016

Thanks for the report! Please open about:support, click on "Copy text to clipboard" and paste it here.

Keywords: crash
OS: Unspecified → Linux
Hardware: Unspecified → x86_64

No crash reports because of # 1653852

I managed to change the Flatpak rules and get a crash report submitted. It's under ID 071c4d0b-ce99-4225-8f66-293b50221213.

Blocks: flatpak
Crash Signature: [@ libpipewire-0.3.so.0@0x9021e ]
Summary: [flatpak] webrtc share screen causes instant crash → [flatpak] webrtc share screen causes instant crash: Crash in [@ libpipewire-0.3.so.0@0x9021e ] with address 0x0000000000000000
Summary: [flatpak] webrtc share screen causes instant crash: Crash in [@ libpipewire-0.3.so.0@0x9021e ] with address 0x0000000000000000 → [flatpak] webrtc share screen causes instant crash on Gnome: Crash in [@ libpipewire-0.3.so.0@0x9021e ] with address 0x0000000000000000

The bug has a crash signature, thus the bug will be considered confirmed.

Status: UNCONFIRMED → NEW
Ever confirmed: true

The severity field is not set for this bug.
:mjf, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(mfroman)

I think this is probably related to Bug 1790496. I'll let Nico confirm that, but until then I'll make the severity match.

Severity: -- → S3
Flags: needinfo?(mfroman) → needinfo?(na-g)

Closing because no crashes reported for 12 weeks.

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WORKSFORME
Flags: needinfo?(na-g)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: