Opened 3 years ago

Last modified 3 months ago

#12534 new bug

Apps started via Shortcuts prefs don't get env variables

Reported by: humdinger Owned by: nobody
Priority: normal Milestone: Unscheduled
Component: Preferences/Shortcuts Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

This is hrev49919.

According to axel in IRC: the input_server is started by the app_server. Both are in the "system" hierarchy and are started without SetupUserEnvironment. Therefore there are almost no env available which are therefore not available for apps started thru the Shortcuts preferences.

Change History (15)

comment:1 Changed 3 years ago by humdinger

Component: Servers/input_serverPreferences/Shortcuts
Owner: changed from korli to nobody

comment:2 Changed 3 years ago by zephjc

I will take a look at this

comment:3 Changed 2 years ago by humdinger

I've had that issue with "Pe". Pe always crashed when invoked with QuickLaunch or with a keycombo set in the Shortcuts prefs. Now, launching Pe works with either of those[[BR]] Can't say what commit has made the difference, but life just got a tiny bit better! Close the ticket?

comment:5 Changed 2 years ago by humdinger

Right! And the Pe package was updated January 10th. Still not sure if the ticket is still valid, because the underlying issue in Haiku is probably still there...

comment:6 Changed 2 years ago by humdinger

Another instance of this, as reported by diver as a QuickLaunch issue #15 is the app "qBittorrent" (currently only installable in 64bit Haiku). That one needs export QT_STYLE_OVERRIDE=haiku in ~/config/settings/boot/UserSetupEnvironment.

qBittorrent won't start from QuickLaunch, LaunchBox or with the Shortcuts prefs.

comment:7 Changed 19 months ago by humdinger

Another example is BurnItNow. When started from Terminal the cloning of an audio CD works. When started via double-click it doesn't. Reading in the audio CD with:

cdda2wav dev=10,1,0 paraopts=proof -vall cddb=0 -B -Owav /boot/home/Soundgarden/

fails with:

cdda2wav: Invalid Argument. Cannot open output fd 0.

comment:8 Changed 19 months ago by humdinger

To add, the cdda2wav error comes from here, if that's any help:
https://gist.github.com/humdingerb/7d70d30814d5d7a9865b01ccb18e5dce#file-gistfile1-txt-L140

A maybe similar issue: after having successfully read in a CD with cdda2wav by having started BurnItNow from Terminal, burning the wavs with cdrecord later fails with:

cdrecord: No such file or directory. Cannot open '/boot/system/cache/burnitnow_clone_wavs/*.wav'.

That's with the same cdrecord line that works when done 'manually' in Terminal:

cdrecord -eject -sao dev=10,1,0 gracetime=2 -v -dao -useinfo -text /boot/system/cache/burnitnow_clone_wavs/*.wav

comment:9 in reply to:  7 Changed 19 months ago by vidrep

We can consider this a 64 bit specific failure. I was able to successfully copy an audioCD using BurnItNow with cdda2wav on x86_gcc2h without launching from terminal, and no error message.

Replying to humdinger:

Another example is BurnItNow. When started from Terminal the cloning of an audio CD works. When started via double-click it doesn't. Reading in the audio CD with:

cdda2wav dev=10,1,0 paraopts=proof -vall cddb=0 -B -Owav /boot/home/Soundgarden/

fails with:

cdda2wav: Invalid Argument. Cannot open output fd 0.

comment:10 Changed 19 months ago by diver

Did you launch it from Tracker or QuickLaunch?

comment:11 Changed 19 months ago by vidrep

double click

comment:12 Changed 14 months ago by vidrep

Reading in a CD with cdda2wav is now working on both 64 bit and gcc2h, but we are still left with the second problem: cdrecord: No such file or directory. Cannot open '/boot/system/cache/burnitnow_clone_wavs/*.wav'.

comment:13 Changed 14 months ago by vidrep

I'm going to move all cdda2wav associated issues to a new trac ticket.

https://dev.haiku-os.org/ticket/14038

comment:14 Changed 3 months ago by humdinger

Was this fixed recently? qBittorrent at least launches now with Shortcuts and QuickLaunch...

comment:15 Changed 3 months ago by diver

qBittorrent has seen quite a number of updates and was probably fixed in the meantime. However, this issue is still not fixed.

Note: See TracTickets for help on using tickets.