Github messages for voidlinux
 help / color / mirror / Atom feed
* [ISSUE] chromium: Jitsi Meet not loadable in Wayland-native mode (BUS_ADRERR)
@ 2021-08-03 21:38 klardotsh
  2021-08-06 12:37 ` fosslinux
                   ` (8 more replies)
  0 siblings, 9 replies; 10+ messages in thread
From: klardotsh @ 2021-08-03 21:38 UTC (permalink / raw)
  To: ml

[-- 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

![screenshot-2021-08-03-21:35:38Z](https://user-images.githubusercontent.com/799439/128089543-398337ac-aca0-4ed2-bc7f-2dff0ccf8052.png)

```
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 :)


^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: chromium: Jitsi Meet not loadable in Wayland-native mode (BUS_ADRERR)
  2021-08-03 21:38 [ISSUE] chromium: Jitsi Meet not loadable in Wayland-native mode (BUS_ADRERR) klardotsh
@ 2021-08-06 12:37 ` fosslinux
  2021-08-17 18:45 ` sburris0
                   ` (7 subsequent siblings)
  8 siblings, 0 replies; 10+ messages in thread
From: fosslinux @ 2021-08-06 12:37 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 226 bytes --]

New comment by fosslinux on void-packages repository

https://github.com/void-linux/void-packages/issues/32313#issuecomment-894230556

Comment:
I have seen this before, and it is not ozone limited, all wayland DM/WMs do this.

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: chromium: Jitsi Meet not loadable in Wayland-native mode (BUS_ADRERR)
  2021-08-03 21:38 [ISSUE] chromium: Jitsi Meet not loadable in Wayland-native mode (BUS_ADRERR) klardotsh
  2021-08-06 12:37 ` fosslinux
@ 2021-08-17 18:45 ` sburris0
  2021-08-17 21:11 ` klardotsh
                   ` (6 subsequent siblings)
  8 siblings, 0 replies; 10+ messages in thread
From: sburris0 @ 2021-08-17 18:45 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 189 bytes --]

New comment by sburris0 on void-packages repository

https://github.com/void-linux/void-packages/issues/32313#issuecomment-900544524

Comment:
This happens to me on Firefox / sway as well.

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: chromium: Jitsi Meet not loadable in Wayland-native mode (BUS_ADRERR)
  2021-08-03 21:38 [ISSUE] chromium: Jitsi Meet not loadable in Wayland-native mode (BUS_ADRERR) klardotsh
  2021-08-06 12:37 ` fosslinux
  2021-08-17 18:45 ` sburris0
@ 2021-08-17 21:11 ` klardotsh
  2021-08-18 18:48 ` sburris0
                   ` (5 subsequent siblings)
  8 siblings, 0 replies; 10+ messages in thread
From: klardotsh @ 2021-08-17 21:11 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 264 bytes --]

New comment by klardotsh on void-packages repository

https://github.com/void-linux/void-packages/issues/32313#issuecomment-900633001

Comment:
Interesting - I've never had issues with FF+Sway... I wonder what the difference in our setups might be to lead to that

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: chromium: Jitsi Meet not loadable in Wayland-native mode (BUS_ADRERR)
  2021-08-03 21:38 [ISSUE] chromium: Jitsi Meet not loadable in Wayland-native mode (BUS_ADRERR) klardotsh
                   ` (2 preceding siblings ...)
  2021-08-17 21:11 ` klardotsh
@ 2021-08-18 18:48 ` sburris0
  2021-09-13 20:56 ` klardotsh
                   ` (4 subsequent siblings)
  8 siblings, 0 replies; 10+ messages in thread
From: sburris0 @ 2021-08-18 18:48 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 245 bytes --]

New comment by sburris0 on void-packages repository

https://github.com/void-linux/void-packages/issues/32313#issuecomment-901347950

Comment:
I encountered what appears to be the same issue with Google Meet.
Does this also happen in Chromium?

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: chromium: Jitsi Meet not loadable in Wayland-native mode (BUS_ADRERR)
  2021-08-03 21:38 [ISSUE] chromium: Jitsi Meet not loadable in Wayland-native mode (BUS_ADRERR) klardotsh
                   ` (3 preceding siblings ...)
  2021-08-18 18:48 ` sburris0
@ 2021-09-13 20:56 ` klardotsh
  2022-05-31  2:13 ` github-actions
                   ` (3 subsequent siblings)
  8 siblings, 0 replies; 10+ messages in thread
From: klardotsh @ 2021-09-13 20:56 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 639 bytes --]

New comment by klardotsh on void-packages repository

https://github.com/void-linux/void-packages/issues/32313#issuecomment-918569484

Comment:
This ticket is all about Chromium, yeah.

Decided to try this again today and I get a new issue: rather than a tab or browser crash, it just locks the entire browser, seemingly when trying to init the webcam. Almost nothing in the logs:

```
[0913/135532.847572:ERROR:scoped_ptrace_attach.cc(37)] process not stopped
[0913/135532.847640:ERROR:scoped_ptrace_attach.cc(27)] ptrace: No such process (3)
[0913/135532.847662:ERROR:scoped_ptrace_attach.cc(27)] ptrace: No such process (3)
```

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: chromium: Jitsi Meet not loadable in Wayland-native mode (BUS_ADRERR)
  2021-08-03 21:38 [ISSUE] chromium: Jitsi Meet not loadable in Wayland-native mode (BUS_ADRERR) klardotsh
                   ` (4 preceding siblings ...)
  2021-09-13 20:56 ` klardotsh
@ 2022-05-31  2:13 ` github-actions
  2022-05-31  6:11 ` fosslinux
                   ` (2 subsequent siblings)
  8 siblings, 0 replies; 10+ messages in thread
From: github-actions @ 2022-05-31  2:13 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 293 bytes --]

New comment by github-actions[bot] on void-packages repository

https://github.com/void-linux/void-packages/issues/32313#issuecomment-1141597509

Comment:
Issues become stale 90 days after last activity and are closed 14 days after that.  If this issue is still relevant bump it or assign it.

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: chromium: Jitsi Meet not loadable in Wayland-native mode (BUS_ADRERR)
  2021-08-03 21:38 [ISSUE] chromium: Jitsi Meet not loadable in Wayland-native mode (BUS_ADRERR) klardotsh
                   ` (5 preceding siblings ...)
  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
  8 siblings, 0 replies; 10+ messages in thread
From: fosslinux @ 2022-05-31  6:11 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 176 bytes --]

New comment by fosslinux on void-packages repository

https://github.com/void-linux/void-packages/issues/32313#issuecomment-1141705001

Comment:
Believe this is still occuring

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: chromium: Jitsi Meet not loadable in Wayland-native mode (BUS_ADRERR)
  2021-08-03 21:38 [ISSUE] chromium: Jitsi Meet not loadable in Wayland-native mode (BUS_ADRERR) klardotsh
                   ` (6 preceding siblings ...)
  2022-05-31  6:11 ` fosslinux
@ 2022-08-31  2:14 ` github-actions
  2022-09-15  2:17 ` [ISSUE] [CLOSED] " github-actions
  8 siblings, 0 replies; 10+ messages in thread
From: github-actions @ 2022-08-31  2:14 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 293 bytes --]

New comment by github-actions[bot] on void-packages repository

https://github.com/void-linux/void-packages/issues/32313#issuecomment-1232369425

Comment:
Issues become stale 90 days after last activity and are closed 14 days after that.  If this issue is still relevant bump it or assign it.

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: [ISSUE] [CLOSED] chromium: Jitsi Meet not loadable in Wayland-native mode (BUS_ADRERR)
  2021-08-03 21:38 [ISSUE] chromium: Jitsi Meet not loadable in Wayland-native mode (BUS_ADRERR) klardotsh
                   ` (7 preceding siblings ...)
  2022-08-31  2:14 ` github-actions
@ 2022-09-15  2:17 ` github-actions
  8 siblings, 0 replies; 10+ messages in thread
From: github-actions @ 2022-09-15  2:17 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 3696 bytes --]

Closed 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

![screenshot-2021-08-03-21:35:38Z](https://user-images.githubusercontent.com/799439/128089543-398337ac-aca0-4ed2-bc7f-2dff0ccf8052.png)

```
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 :)


^ permalink raw reply	[flat|nested] 10+ messages in thread

end of thread, other threads:[~2022-09-15  2:17 UTC | newest]

Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-08-03 21:38 [ISSUE] chromium: Jitsi Meet not loadable in Wayland-native mode (BUS_ADRERR) klardotsh
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

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).