Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#77995 - [obsidian] Does not work with GNOME (GTK 4)

Attached to Project: Community Packages
Opened by Thomas (uhthomas) - Saturday, 25 March 2023, 17:17 GMT
Last edited by Toolybird (Toolybird) - Saturday, 06 May 2023, 01:46 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sven-Hendrik Haase (Svenstaro)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Obsidian doesn't run with GNOME.

```
❯ obsidian
2023-03-25 17:14:43 Loading main app package /usr/lib/obsidian/obsidian.asar

(process:1178489): Gtk-ERROR **: 17:14:43.145: GTK 2/3 symbols detected. Using GTK 2/3 and GTK 4 in the same process is not supported
zsh: trace trap (core dumped) obsidian
```

Additional info:
* package version(s)

```
❯ paru -Q gnome-shell obsidian
gnome-shell 1:43.3-2
obsidian 1.1.16-1
```

* config and/or log files etc.

N/A

* link to upstream bug report, if any

N/A

Steps to reproduce: Install GNOME and Obsidian. Try to run Obsidian.
This task depends upon

Closed by  Toolybird (Toolybird)
Saturday, 06 May 2023, 01:46 GMT
Reason for closing:  Upstream
Additional comments about closing:  See comments
Comment by Toolybird (Toolybird) - Saturday, 25 March 2023, 21:18 GMT
Cannot repro. Runs fine for me in a fresh GNOME install in a VM.

> core dumped

This is a closed source app. But please get a backtrace [1] to see if it sheds any light on where it goes wrong on your system.

[1] https://wiki.archlinux.org/title/Debugging/Getting_traces#Debuginfod
Comment by Jiaye Yang (lumen_yang) - Monday, 27 March 2023, 18:27 GMT
I can confirm this on KDE wayland. Exact same with core dump problem. I'm switching to AUR electron22 package to see if its incompatiabilty with the community package of electron
Comment by Jiaye Yang (lumen_yang) - Monday, 27 March 2023, 18:43 GMT
For people who are using obsidian with the following electron flags

> --enable-features=UseOzonePlatform
> --ozone-platform=wayland
> --enable-wayland-ime

If you experience the same coredump problem. You can try the aur/electron22-bin and launch your app with the following command

> exec /bin/electron22 /usr/lib/obsidian/app.asar --enable-wayland-ime --ozone-platform=wayland "$@"

It helps my obsidian to work. And this is the contribution from q234rty. A fellow archlinux user in telegram group archlinuxcn
Comment by Toolybird (Toolybird) - Monday, 27 March 2023, 21:45 GMT
> using obsidian with the following electron flags

Still no crash for me even with those flags.
Comment by Jiaye Yang (lumen_yang) - Tuesday, 28 March 2023, 16:52 GMT
> Still no crash for me even with those flags.

Hi, Toolybird. Yes, I also have problem reproducing it on other computers, therefore I just offer more information and provide a temporary workaround. According to q234rty, who has helped me with this, he suspects the compile problem of electron from the community repo. I've helped him to obtain some debug info, and he might raise the case if he is confident with that hypothesis.
Comment by Thomas (uhthomas) - Tuesday, 28 March 2023, 17:45 GMT
You make a good point. I hadn't considered the global electron flags.

I had followed https://wiki.archlinux.org/title/wayland#Command_line_flags and put "--gtk-version=4" in "~/.config/electron-flags.conf". Removing this line allows Obsidian to start.

That said, I'm sorry to hear you're also having issues even without that flag. Should we open an upstream issue with Obsidian?
Comment by Toolybird (Toolybird) - Wednesday, 29 March 2023, 06:26 GMT
> --gtk-version=4

Ahh, that's the key. It now crashes for me when that flag is present. I tried to get a backtrace but my VM doesn't have enough RAM and gdb gets killed.
Comment by Sven-Hendrik Haase (Svenstaro) - Thursday, 30 March 2023, 03:54 GMT
I'm not really sure what I can do here to be honest. I just package obsidian as-is.
Comment by Sven-Hendrik Haase (Svenstaro) - Saturday, 06 May 2023, 00:59 GMT
I still don't know what to do here and there's no way I see that would fix this for all users and not break it for others.
Comment by Toolybird (Toolybird) - Saturday, 06 May 2023, 01:45 GMT
Being closed source, IMHO there's nothing Arch can do. Now that the trigger is known, someone motivated needs to:
a) try contacting upstream
and/or
b) document the problem in the Wiki.

Loading...