menu
Centro de ayuda

Busca en las guías o explóralas según lo que quieras hacer.

search
navigate_before Volver

Record a bug report a developer can act on EN

Window or screen capture, the system sound, and the log file that goes with it.

To record a bug report a developer can act on, capture the whole window or screen where the problem happens, keep the system sound on, and turn on Logging so a log file comes with the recording. The video shows what you did. The log file shows what the extension was doing at the time.

Before you record

  1. Click the Rekorder icon in your Chrome toolbar to open the popup.
  2. Open the settings and go to the Advanced tab. Turn on Logging. It's off by default, so it only covers recordings you make after you switch it on.
  3. Go to the Audio tab and check that Source sound is on. It's on by default. When you record a window or your entire screen, it records the system sound, meaning whatever your computer is playing. That captures alerts, error beeps and video or audio the bug involves.
  4. Get the app or page into the state just before the problem, so the recording doesn't start with minutes of setup.

If the bug shows information you don't want to share, see Blur sensitive information before you record and Record something confidential.

Record the problem

  1. In the popup, choose to record a window or your entire screen. Use a window when the bug is in one app. Use the entire screen when it involves more than one window, or when the whole screen changes. What you can record: tab, window, screen or camera explains the modes.
  2. In the sharing dialog Chrome shows, pick the window or screen to share. If the dialog offers an option to share audio, leave it ticked. Without it, Rekorder records the picture without system sound. Chrome on Linux can't capture system sound at all. See Why there is no system sound on Linux.
  3. Repeat the problem, one step at a time. Say out loud what you're doing and what you expected to happen. Your microphone is recorded along with the system sound.
  4. When the problem has happened, stop the recording.

Some things make the recording easier to follow:

Send it to the developer

  1. Share the recording and copy its link. See Share a recording, and Private, specific people, or anyone with the link for who can open it.
  2. Send the link with a short written description: what you did, what you expected and what happened instead.
  3. Send the log file if the developer is Rekorder support, or if they asked for it.

How you get the log file depends on your mode:

  • Cloud mode: the log is sent to Rekorder together with the recording. You don't need to attach anything.
  • Offline mode: the log stays on your computer. Open the popup and go to the Advanced tab. Logging then shows Saved logs, with a count and a Download link. The link bundles every saved log into one archive and then clears the stored logs. Send that archive to whoever is investigating. See Cloud mode and Offline mode: which one you are in.

The log covers a recording you stop normally, one you cancel, and one that fails to start.

Reporting a problem with Rekorder itself

If the bug is in Rekorder, use the steps above and then write to support. See How do I report a bug from inside the app? for the feedback dialog and How do I contact support? for what to include.

error_outline
Logotipo de Rekorder
¡Graba tu pestaña, ventana o pantalla y comparte el vídeo!
Al usar Rekorder.dev, aceptas nuestros
Términos del servicio y nuestra Política de privacidad
Asegúrate de cumplir todas las leyes sobre grabaciones e informar a los participantes cuando sea obligatorio.