Bug 482738

Summary:	[Video Recording] Rectangular region video recording fails when format is set to MP4/H.264
Product:	[Applications] Spectacle	Reporter:	David G. <david>
Component:	General	Assignee:	Noah Davis <noahadvs>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	babochyk, david, kde, kdebugs, nate, smowtenshi
Priority:	NOR	Keywords:	qt6
Version First Reported In:	24.02.0
Target Milestone:	---
Platform:	Other
OS:	Other
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	Picture of error

Description David G. 2024-03-07 15:54:36 UTC

SUMMARY
When recording a video with Spectacle 24.02 with the video format set to MP4/H.264, after pressing the tray icon to stop the recording, no notification that the recording succeeded is sent and no video is saved in the specified folder.


STEPS TO REPRODUCE
1. Set video format in Spectacle settings Video Saving tab to MP4/H.264
2. Start recording
3. Stop recording

OBSERVED RESULT
Recording stops and Spectacle closes
No notification about recording success
No video saved

EXPECTED RESULT
Recording stops and Spectacle closes
Notification about recording success sent
Video saved

SOFTWARE/OS VERSIONS
Operating System: EndeavourOS 
KDE Plasma Version: 6.0.1
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.7.8-arch1-1 (64-bit)
Graphics Platform: Wayland

Comment 1 David G. 2024-06-21 19:39:05 UTC

This is now fixed. I don't know when the issue disappeared, but it is not present anymore in Spectacle 24.05.1.

Comment 2 Jed 2024-09-08 12:43:59 UTC

I am experiencing this problem with Spectacle v24.08.0
When the format is set to "MP4/H.264", after stopping recording  I get

Error -- Spectacle
Failed to export video: Temporary file URL must be an existing local file

This does not happen when the format is WebM/VP9

Comment 3 Jed 2024-09-08 12:45:16 UTC

Created attachment 173440 [details]
Picture of error

Comment 4 Nate Graham 2024-09-16 14:10:00 UTC

That's actually a different issue; see Bug 485733.

Comment 5 Nate Graham 2024-10-29 14:23:18 UTC


*** This bug has been marked as a duplicate of bug 485733 ***