Using Android phone as mic on Discord on Linux - segmentation fault on refocusing window

[annalasko]

Environment

• OS: Arch Linux (6.14.7-arch2-1)
• Scrcpy version: 3.2
• Installation method: pacman
• Device model: Google Pixel 9 Pro
• Android version: 15 (BP1A.250405.007.D1)

Describe the bug

I have been attempting to use my phone as a mic on Discord, and I am encountering a bug.

Upon clicking back into the Discord window, scrcpy segfaults.

I have taken the steps outlined in Ristovski's comment on #4208, and it produces the following error:

scrcpy 3.2 <https://github.com/Genymobile/scrcpy>
No video mirroring, SDK mouse disabled
INFO: ADB device found:
INFO:     -->   (usb)  XXXXXXXXXXXXXX                  device  Pixel_9_Pro
/usr/share/scrcpy/scrcpy-server: 1 file pushed, 0 skipped. 281.2 MB/s (90888 bytes in 0.000s)
[server] INFO: Device: [Google] google Pixel 9 Pro (Android 15)
INFO: Recording started to wav file: /tmp/mic_pipe
zsh: segmentation fault (core dumped)  scrcpy --no-video --no-window -N --audio-source=mic --audio-codec=raw

I am unsure how to best capture the relevant output of adb logcat, as my experience with ADB is limited.

I'm willing to give more information as needed. Any help would be appreciated, thanks.

[annalasko]

It would seem this is an issue with Discord not using Wayland. I was able to modify iliqiliev's script, also from #4208 to suit my purposes:

#!/usr/bin/sh

LATENCY=10
MODULE_ID=$(pactl load-module module-pipe-source source_name="Scrcpy" channels=2 format=16 rate=48000 file=/tmp/scrcpy_pipe)

# parec --raw > /dev/null &

scrcpy --no-video --no-window --no-playback --audio-source=mic --audio-codec=raw --record-format=wav --record=/tmp/scrcpy_pipe --audio-buffer=$LATENCY --audio-output-buffer=10 &

discord --enable-features=UseOzonePlatform --ozone-platform=wayland

pactl unload-module $MODULE_ID

In order to fix keybinds, I allowed legacy X11 apps to read keystrokes in all apps in the KDE settings. I'm not sure if there are similar settings in other DEs.

I can't help but feel like this is more of a workaround than a fix. Is there any way to get scrcpy to play nice with X11 apps? Thank you.

[rom1v]

If the crash is related to wayland, you should report to https://github.com/libsdl-org/SDL (a lib used by scrcpy).

Provide the result of scrcpy --version.

If you can build from sourced, enable ASAN to get a stack trace:

meson setup d -Db_sanitize=address
ninja -Cd

and run:

./run d

[annalasko]

Part of my efforts to fix it saw me install it from the AUR, so this is my current version:

scrcpy v3.2.r3.gc5ed2cf <https://github.com/Genymobile/scrcpy>

Dependencies (compiled / linked):
 - SDL: 2.32.56 / 2.32.56
 - libavcodec: 61.19.101 / 61.19.101
 - libavformat: 61.7.100 / 61.7.100
 - libavutil: 59.39.100 / 59.39.100
 - libavdevice: 61.3.100 / 61.3.100
 - libusb: - / 1.0.28

After compiling from source, this is my new version:

scrcpy 3.2 <https://github.com/Genymobile/scrcpy>

Dependencies (compiled / linked):
 - SDL: 2.32.6 / 2.32.6
 - libavcodec: 61.19.101 / 61.19.101
 - libavformat: 61.7.100 / 61.7.100
 - libavutil: 59.39.100 / 59.39.100
 - libavdevice: 61.3.100 / 61.3.100
 - libusb: - / 1.0.28

Upon building with the commands you listed, I am met with this stack trace:

scrcpy 3.2 <https://github.com/Genymobile/scrcpy>
INFO: No video mirroring, SDK mouse disabled
* daemon not running; starting now at tcp:5037
* daemon started successfully
INFO: ADB device found:
INFO:     -->   (usb)  XXXXXXXXXXXXXX                  device  Pixel_9_Pro
DEBUG: Device serial: XXXXXXXXXXXXXX
DEBUG: Using SCRCPY_SERVER_PATH: d/server/scrcpy-server
d/server/scrcpy-server: 1 file pushed, 0 skipped. 198.3 MB/s (147874 bytes in 0.001s)
[server] INFO: Device: [Google] google Pixel 9 Pro (Android 15)
DEBUG: Server connected
DEBUG: Starting controller thread
DEBUG: Starting receiver thread
DEBUG: Demuxer 'audio': starting thread
INFO: Recording started to wav file: /tmp/mic_pipe
AddressSanitizer:DEADLYSIGNAL
=================================================================
==4468==ERROR: AddressSanitizer: SEGV on unknown address (pc 0x556710b33193 bp 0x7ffd94abd9b0 sp 0x7ffd94abd9a0 T0)
==4468==The signal is caused by a READ memory access.
==4468==Hint: this fault was caused by a dereference of a high value address (see register values below).  Disassemble the provided pc to learn which register was used.
    #0 0x556710b33193 in sc_screen_is_relative_mode ../app/src/screen.c:162
    #1 0x556710b3854d in sc_screen_handle_event ../app/src/screen.c:864
    #2 0x556710b2bf19 in event_loop ../app/src/scrcpy.c:200
    #3 0x556710b315e1 in scrcpy ../app/src/scrcpy.c:936
    #4 0x556710af1691 in main_scrcpy ../app/src/main.c:89
    #5 0x556710af17c0 in main ../app/src/main.c:108
    #6 0x7f630dc6b6b4  (/usr/lib/libc.so.6+0x276b4) (BuildId: 468e3585c794491a48ea75fceb9e4d6b1464fc35)
    #7 0x7f630dc6b768 in __libc_start_main (/usr/lib/libc.so.6+0x27768) (BuildId: 468e3585c794491a48ea75fceb9e4d6b1464fc35)
    #8 0x556710af1094 in _start (/home/annal/.scratch/scrcpy/d/app/scrcpy+0x30094) (BuildId: 9fc918c1d5c57c9de1c9641f5f524df7ae5070f9)

==4468==Register values:
rax = 0x2a2a2a2a2a2a2a2a  rbx = 0x00007b62f8e00100  rcx = 0x2a2a2a2a2a2a2a32  rdx = 0x05454545c544c546  
rdi = 0x0000556710c38b58  rsi = 0x00007b62f8e00120  rbp = 0x00007ffd94abd9b0  rsp = 0x00007ffd94abd9a0  
 r8 = 0x000000000000ffff   r9 = 0x0000000000000000  r10 = 0x0000000000000000  r11 = 0x00007b62f8e00120  
r12 = 0x00007b62f8e001a0  r13 = 0x00000f6c5f1c0020  r14 = 0x00007ffd94abda10  r15 = 0x0000556710b95af0  
AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: SEGV ../app/src/screen.c:162 in sc_screen_is_relative_mode
==4468==ABORTING
[server] DEBUG: Controller stopped                                              
[server] DEBUG: Device message sender stopped
[server] DEBUG: Audio recorder stopped

Thank you.

[rom1v]

Oh, can you test on dev branch, please? It might already be fixed (see #5970).

Thank you for the stack trace 👍