From: klardotsh <klardotsh@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] chromium: Jitsi Meet not loadable in Wayland-native mode (BUS_ADRERR)
Date: Tue, 03 Aug 2021 23:38:24 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32313@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 3693 bytes --]
New issue by klardotsh on void-packages repository
https://github.com/void-linux/void-packages/issues/32313
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname: `Void 5.12.17_1 x86_64 AuthenticAMD notuptodate rrrmFFFFFF`
* package: `chromium-91.0.4472.114_1`
### Expected behavior
Can join an AV conference on Jitsi Meet (or other WebRTC platforms) when running Chromium with the Wayland backend (read: not in XWayland, the default, which works fine here).
### Actual behavior
```
Received signal 7 BUS_ADRERR 7f7af406f000
#0 0x55cfe7147db9 (/usr/lib/chromium/chromium+0x4623db8)
#1 0x55cfe70b8843 (/usr/lib/chromium/chromium+0x4594842)
#2 0x55cfe7147961 (/usr/lib/chromium/chromium+0x4623960)
#3 0x7f7b2bd9e900 (/usr/lib/libpthread-2.32.so+0x138ff)
#4 0x55cfe803ff81 (/usr/lib/chromium/chromium+0x551bf80)
#5 0x55cfe802993e (/usr/lib/chromium/chromium+0x550593d)
#6 0x55cfe8027ab6 (/usr/lib/chromium/chromium+0x5503ab5)
#7 0x55cfe4688624 (/usr/lib/chromium/chromium+0x1b64623)
#8 0x55cfe468a034 (/usr/lib/chromium/chromium+0x1b66033)
#9 0x55cfeb6b9a3e (/usr/lib/chromium/chromium+0x8b95a3d)
#10 0x55cfeb6b9747 (/usr/lib/chromium/chromium+0x8b95746)
#11 0x55cfeb6b898f (/usr/lib/chromium/chromium+0x8b9498e)
#12 0x55cfe71593bf Received signal 7 BUS_ADRERR 7f7adc396800
#0 0x55cfe7147db9 (/usr/lib/chromium/chromium+0x4623db8)
#1 0x55cfe70b8843 (/usr/lib/chromium/chromium+0x4594842)
#2 0x55cfe7147961 (/usr/lib/chromium/chromium+0x4623960)
#3 0x7f7b2bd9e900 (/usr/lib/libpthread-2.32.so+0x138ff)
#4 0x55cfe803ff81 (/usr/lib/chromium/chromium+0x551bf80)
#5 0x55cfe802993e (/usr/lib/chromium/chromium+0x550593d)
#6 0x55cfe8027ab6 (/usr/lib/chromium/chromium+0x5503ab5)
#7 0x55cfe4688624 (/usr/lib/chromium/chromium+0x1b64623)
#8 0x55cfe468a034 (/usr/lib/chromium/chromium+0x1b66033)
#9 0x55cfeb6b9a3e (/usr/lib/chromium/chromium+0x8b95a3d)
#10 0x55cfeb6b9747 (/usr/lib/chromium/chromium+0x8b95746)
#11 0x55cfeb6b898f (/usr/lib/chromium/chromium+0x8b9498e)
#12 0x55cfe71593bf (/usr/lib/chromium/chromium+0x46353be)
#13 0x7f7b2bd93eae start_thread
#14 0x7f7b27d5c2ff __GI___clone
r8: 0000000000061800 r9: 0000000000000138 r10: 0000000000000280 r11: 0000000000000280
r12: 000055cfe803ff70 r13: 0000000000000000 r14: 00007f7af4151800 r15: 0000000000000001
di: 00007f7af4151840 si: 00007f7adc396800 bp: 00007f7af7ffaff0 bx: 00007f7adc396800
dx: 0000000000061800 ax: 0000000000000000 cx: 000055cfe803ff70 sp: 00007f7af7ffaff0
ip: 000055cfe803ff81 efl: 0000000000010202 cgf: 002b000000000033 erf: 0000000000000006
trp: 000000000000000e msk: 0000000000000000 cr2: 00007f7adc396800
[end of stack trace]
Calling _exit(1). Core file will not be generated.
```
### Steps to reproduce the behavior
- Run Chromium in Wayland+Ozone mode (in my case, I'm running in Sway): `chromium --enable-features=UseOzonePlatform --ozone-platform=wayland`
- Go to [Jitsi](https://meet.jit.si)
- Hit `Start Meeting` to join a random empty call
- Crash occurs seemingly when Jitsi attempts to access the camera and/or microphone, not totally sure which, or whether it's the access to the camera/microphone causing the problem, or Chromium is failing to pop up the permission request. Not really sure how to go about narrowing down the search here, either, though admittedly I'm filing this during the workday so I'm kinda going quickly :)
next reply other threads:[~2021-08-03 21:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-03 21:38 klardotsh [this message]
2021-08-06 12:37 ` fosslinux
2021-08-17 18:45 ` sburris0
2021-08-17 21:11 ` klardotsh
2021-08-18 18:48 ` sburris0
2021-09-13 20:56 ` klardotsh
2022-05-31 2:13 ` github-actions
2022-05-31 6:11 ` fosslinux
2022-08-31 2:14 ` github-actions
2022-09-15 2:17 ` [ISSUE] [CLOSED] " github-actions
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32313@inbox.vuxu.org \
--to=klardotsh@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).