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

error code sigsegv #2784

Open
3 tasks
Devious3901 opened this issue Apr 2, 2024 · 4 comments
Open
3 tasks

error code sigsegv #2784

Devious3901 opened this issue Apr 2, 2024 · 4 comments
Labels
bug need info Need feedback to proceed

Comments

@Devious3901
Copy link

OS/Platform

Debian, Ubuntu, and derivatives

Installed

Flatpak

Version

Version 123.0.6312.86 (Official Build, ungoogled-chromium) (64-bit)

Have you tested that this is not an upstream issue or an issue with your configuration?

  • I have tried reproducing this issue in Chrome and it could not be reproduced there
  • I have tried reproducing this issue in vanilla Chromium and it could not be reproduced there
  • I have tried reproducing this issue in ungoogled-chromium with a new and empty profile using --user-data-dir command line argument and it could not be reproduced there

Description

error code sigsegv after flatpak update

How to Reproduce?

This happened after the flatpak update

Actual behaviour

Check screenshot https://imgur.com/a/JmFnKYa

Expected behaviour

Hi, two days ago I updated all the apps to flashpak, and I got this problem that pops up in ungoogled chrome, how to fix it, before that it was not there, that is, before the update of the flashpak version.

Relevant log output

No response

Additional context

No response

@Devious3901 Devious3901 added the bug label Apr 2, 2024
@PF4Public
Copy link
Contributor

@rany2 Have you encountered such issue?

@PF4Public PF4Public added the need info Need feedback to proceed label Apr 6, 2024
@rany2
Copy link
Member

rany2 commented Apr 6, 2024

Nope, I don't have a clue about this. Sorry

@PF4Public
Copy link
Contributor

@Devious3901 Have you tried submitting this issue to Flatpak? I very much doubt it being an issue of ungoogled-chromium.

@rany2
Copy link
Member

rany2 commented Apr 6, 2024

@PF4Public The only thing I could think of is that the flatpak was updated and he didn't exit UGC and relaunch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug need info Need feedback to proceed
Projects
None yet
Development

No branches or pull requests

3 participants