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#78493 - [obsidian] opens electron page instead of application

Attached to Project: Community Packages
Opened by Thomas Girod (tgirod) - Friday, 12 May 2023, 06:03 GMT
Task Type Bug Report
Category Packages
Status Assigned
Assigned To Sven-Hendrik Haase (Svenstaro)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

Description:

when starting obsidian, the app opens up to the default electron page instead of running the application.

I'm running version 1.2.8-1

Steps to reproduce:

1. pacman -S obsidian
2. run obsidian
This task depends upon

Comment by Sven-Hendrik Haase (Svenstaro) - Friday, 12 May 2023, 13:51 GMT
Can't reproduce.
Comment by Thomas Girod (tgirod) - Friday, 12 May 2023, 15:40 GMT
I found the culprit!

This command works : /usr/lib/electron/electron /usr/lib/obsidian/app.asar

But this one does not : /usr/bin/electron /usr/lib/obsidian/app.asar

Looking at the content of /usr/bin/electron, it calls for a file called .config/electron-flags.conf. If I remove that file, the application starts correctly.

On my computer that file contains the following lines :

$ cat .config/electron-flags.conf
--enable-features=UseOzonePlatform
--ozone-platform=wayland

Apparently this is making the app break silently. I haven't tried with another electron app, maybe the bug should be reported to the electron package.
Comment by Caleb Maclennan (alerque) - Monday, 15 May 2023, 08:00 GMT
I've seen this happen before. I don't think it's the fault of the obsidian package. The user config file has flags being set that likely work for/help some other app, but they are a missmatch for this app. Setting them globally in a user flags file is problematic because many different electron versions and apps will try to read the same flags. I usually handle those cases with aliases or launch scripts that pass the flags relevant to a single app without creating a flags file.

Loading...