obsproject / obsproject/obs-studio
OBS v4l2-input errno: Device or resource busy
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 76.4k
- Forks
- 10.2k
- Avg merge
- 4d 23h
- Merged PRs (30d)
- 12
Description
Operating System Info
Other
Other OS
Linux Mint 22.1
OBS Studio Version
32.0.2
OBS Studio Version (Other)
No response
OBS Studio Log URL
https://obsproject.com/logs/kZfFRUjlBgk2dsG2
OBS Studio Crash Log URL
No response
Expected Behavior
Utilize V4l2-input for webcam and capture card service.
Current Behavior
Until a day or so ago after updating, I was able to use my webcam just fine. However, after a big update, seems nothing works properly now ONLY within OBS. I was using the stable 32.0.2 version from the released .deb file, then tried installing 32.0.3 from the newest .deb file but now OBS never loads. So I had to reinstall using the software available version 32.0.2.1-3build1.. and now my docked chats have disappeared and my webcam still does not work.
I have verified my webcam works in every single program except OBS. When I configure the webcam, it just gives an Input error message in the logs, and shows the device as busy. However, I'm able to confirm OBS is the ONLY thing using the device and nothing else is touching it. It's like OBS starts the v4l2 service, but then can't do anything with it. It locks itself out of any v4l2 device.
I've tried several previous kernels, tried different versions of OBS.. nothing helps. I really need this to work..
UPDATE: now OBS crashes instantly when I try to use any Window Capture..
Steps to Reproduce
1.Open OBS
2. No webcam shows
3. Configure webcam, nothing saves, logs show device is busy, but is only being used by OBS
...
Anything else we should know?
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the OBS log URL and the reported v4l2-input “Device or resource busy” error, then compare the webcam and capture-card behavior described under Current Behavior. No source file or test is identified. Done means reproducing the device-busy failure and the Window Capture crash, with both behaviors resolved or narrowed to a specific cause.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- audio-video-rtc, desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 24/100