Recordmydesktop Crashing With Segmentation Fault

Bug #1964449 reported by Mukesh Kumar
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
recordmydesktop
New
Undecided
Unassigned
recordmydesktop (Ubuntu)
New
Undecided
Unassigned

Bug Description

Hi Team,

While trying to explore features/bugs in recordmydesktop application, I have come across a situation where the Application is crashing and showing the message "Segmentation Fault". I tried to debug the issue, but for some reason couldn't figure it out. The crash is very simple to reproduce. Please find below all the information:

recordmydesktop version: recordMyDesktop v0.4.0
OS used: Kali linux 2020.3 Vbox

Steps to repro:

1. Start the recording using default command with default options "recordmyscreen"
2. Once, the recording is started and it shows "Capturing", press "CTRL+ C" twice pretty fast.
3. Once, the 2nd CTRL+C is pressed, it will show the error "Please wait...
Output file: out-16.ogv
[5%] ^CSegmentation fault
"
4. Also, there won't be any recording saved as well.

I have pasted the entire transaction below and attached a screenshot as well:

kali@kali:~$ recordmydesktop
Initial recording window is set to:
X:0 Y:0 Width:1920 Height:940
Adjusted recording window is set to:
X:0 Y:6 Width:1920 Height:928
Your window manager appears to be Xfwm4

Detected compositing window manager.
Reverting to full screen capture at every frame.
To disable this check run with --no-wm-check
(though that is not advised, since it will probably produce faulty results).

Initializing...
Buffer size adjusted to 4096 from 4096 frames.
Opened PCM device default
Recording on device default is set to:
1 channels at 22050Hz
Capturing!
^C
*********************************************

Cached 2 MB, from 122 MB that were received.
Average cache compression ratio: 97.8 %

*********************************************
Saved 18 frames in a total of 17 requests
Shutting down.....
STATE:ENCODING
Encoding started!
This may take several minutes.
Pressing Ctrl-C will cancel the procedure (resuming will not be possible, but
any portion of the video, which is already encoded won't be deleted).
Please wait...
Output file: out-16.ogv
[5%] ^CSegmentation fault
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2022-03-10 (0 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
Package: recordmydesktop 0.3.8.1+svn602-1.1ubuntu1
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
Tags: focal
Uname: Linux 5.13.0-35-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True

Revision history for this message
Mukesh Kumar (theserpent) wrote :
Revision history for this message
Chris Guiver (guiverc) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:

apport-collect 1964449

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

Changed in recordmydesktop (Ubuntu):
status: New → Incomplete
Revision history for this message
Mukesh Kumar (theserpent) wrote : Dependencies.txt

apport information

tags: added: apport-collected focal
description: updated
Revision history for this message
Mukesh Kumar (theserpent) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Mukesh Kumar (theserpent) wrote : ProcEnviron.txt

apport information

Changed in recordmydesktop (Ubuntu):
status: Incomplete → New
Revision history for this message
Mukesh Kumar (theserpent) wrote :

For getting the debug log, I installed the recordmydesktop on a new installation of Ubuntu and reproduced the issues

Revision history for this message
Mukesh Kumar (theserpent) wrote :

NOt sure if the debug file got uploaded successfully or not, hence uploading it manually

Revision history for this message
Mukesh Kumar (theserpent) wrote :

Hi Team,
Not sure if there is any other action pending from my end to get tis bug triaged. Can someone please check the bug and confirm the issue.

information type: Public → Private Security
Revision history for this message
Alex Murray (alexmurray) wrote : Bug is not a security issue

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

information type: Private Security → Public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.