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

failed to run then started working #662

Open
qrkourier opened this issue Mar 9, 2024 · 2 comments
Open

failed to run then started working #662

qrkourier opened this issue Mar 9, 2024 · 2 comments

Comments

@qrkourier
Copy link

The desktop integration shortcut failed to open Flatseal flatpak, so I tried to run it interactively inside tmux and got this error.

❯ flatpak run com.github.tchx84.Flatseal
libEGL warning: DRI3: Screen seems not DRI3 capable
libEGL warning: DRI2: failed to authenticate
libEGL warning: DRI3: Screen seems not DRI3 capable
libEGL warning: DRI3: Screen seems not DRI3 capable
libEGL warning: DRI2: failed to authenticate
libEGL warning: DRI3: Screen seems not DRI3 capable

(com.github.tchx84.Flatseal:2): Gdk-WARNING **: 13:44:03.254: The program 'com.github.tchx84.Flatseal' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 1917 error_code 8 request_code 149 (unknown) minor_code 4)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

Suspecting that problem could be related to running inside a terminal multiplexer like tmux, I was able to work around by running it without tmux:

gnome-terminal -- flatpak run com.github.tchx84.Flatseal

After running it once this way, now I can open it normally with desktop integration.

I'm unsure what the original problem was.

@tchx84
Copy link
Owner

tchx84 commented Mar 27, 2024

@qrkourier thanks for sharing this report, I am honestly unsure as well... could you:

  1. Describe your environment, e.g., OS version, flatpak version, etc.
  2. Is this reproducible with another GTK4 application? e.g., say Decibels.
  3. If reproducible, describe the exact steps.

@qrkourier
Copy link
Author

I didn't encounter this issue with Decibels. It's no longer reproducible but it was until I ran it once outside of tmux.

❯ cat /etc/lsb-release /etc/os-release
DISTRIB_ID=Pop
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION="Pop!_OS 22.04 LTS"
NAME="Pop!_OS"
VERSION="22.04 LTS"
ID=pop
ID_LIKE="ubuntu debian"
PRETTY_NAME="Pop!_OS 22.04 LTS"
VERSION_ID="22.04"
HOME_URL="https://pop.system76.com"
SUPPORT_URL="https://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=jammy
UBUNTU_CODENAME=jammy
LOGO=distributor-logo-pop-os

❯ lsb_release -a
No LSB modules are available.
Distributor ID: Pop
Description:    Pop!_OS 22.04 LTS
Release:        22.04
Codename:       jammy

❯ echo $DISPLAY
:1

❯ echo $WAYLAND_DISPLAY

❯ gnome-shell --version
** (process:352986): WARNING **: 09:34:56.654: Failed to set RT scheduler: Operation not permitted
GNOME Shell 42.5

❯ echo $XDG_CURRENT_DESKTOP
pop:GNOME

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

2 participants