Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Peek crashes on Ubuntu 22 #1094

Open
bkjohnson opened this issue Jul 19, 2022 · 13 comments
Open

Peek crashes on Ubuntu 22 #1094

bkjohnson opened this issue Jul 19, 2022 · 13 comments

Comments

@bkjohnson
Copy link

bkjohnson commented Jul 19, 2022

System Information

  • Distribution package: .deb
  • Peek version: 1.5.1
  • GTK: 3.24.33
  • Additional info if applicable: Ubuntu 22.04 w/ Regolith Linux 2.x

Describe the bug

When I click "Start recording" or press Ctrl+R, peek crashes once the countdown ends.

To Reproduce

  1. Start peek
  2. Try to start recording from the GUI
  3. Notice the crash

Expected behavior
I expect peek to record the area in its frame and to be able to stop the recording when I want.

Additional context

Here is a sample of the error I get when I start the GUI from the command line and then try to start recording:

Error message containing: "fish: Job 1, 'peek' terminated by signal SIGSEGV (Address boundary error)"

@luketrenaman
Copy link

luketrenaman commented Aug 9, 2022

Getting the same error on Ubuntu 22.04 on Regolith Linux 2.x, GTK version 3.24.33, Peek version 1.5.1, compositor is picom.
image

Using Unity Desktop does not cause this error.

@gedasss
Copy link

gedasss commented Sep 8, 2022

Getting the same error on Ubuntu 22.04 on Regolith Linux 2.x, GTK version 3.24.33, Peek version 1.5.1, compositor is picom. image

Using Unity Desktop does not cause this error.

Same problem to me on Ubuntu 22.04/Regolith2.0. Works only if I start it with ffmpeg flag: peek -b ffmpeg

@yzcyayaya
Copy link

  • ubuntu22.04 gnome42
    Using screen recorder backend gnome-shell
    Failed to initialize recorder: Could not start GNOME Shell recorder.

Missing codec or another active screen recording using org.gnome.Shell.Screencast?

Please see the FAQ at https://github.com/phw/peek#what-is-the-cause-for-could-not-start-gnome-shell-recorder-errors

@luizwbr
Copy link

luizwbr commented Oct 17, 2022

Running this command worked for me ( upgraded Ubuntu version from 20 LTS to 22 ) :

rm -rf ~/.cache/gstreamer-1.0

@Sharcoux
Copy link

What worked for me was to run peek -b ffmpeg

@lfilhomindfulcare
Copy link

Thanks, that works for me too!

@RadoRado
Copy link

Can confirm the solution from @Sharcoux works for me too. Cheers ✨

@bkjohnson
Copy link
Author

@Sharcoux 's solution worked for me as well. Given the recent deprecation, I may try to make a fork that has that configurable in the GUI preferences menu rather than just a cli option

@AsaAyers
Copy link

AsaAyers commented Jan 22, 2023 via email

@gustavotrott
Copy link

Yes, peek -b ffmpeg works.
But how can I set this flag as default? It's tough to run via terminal every time.

@Sharcoux
Copy link

Yes, peek -b ffmpeg works. But how can I set this flag as default? It's tough to run via terminal every time.

https://linuxize.com/post/how-to-create-bash-aliases/

@gustavotrott
Copy link

Yes, peek -b ffmpeg works. But how can I set this flag as default? It's tough to run via terminal every time.

linuxize.com/post/how-to-create-bash-aliases

Thanks.

I created a Launcher for the correct command..

vi ~/.local/share/applications/peek.desktop

[Desktop Entry]
Name=Peek ffmpeg
Exec=/usr/bin/peek -b ffmpeg
Type=Application
Icon=studio

Now I can call it from Applications menu 😄

@luggie
Copy link

luggie commented Mar 21, 2024

or addings this to .bashrc or .profile
alias peek='peek -b ffmpeg'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests