Arch Linux

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#11455 - [openbox] issue with autostart.sh and 'which' causing needless logging

Attached to Project: Arch Linux
Opened by eliott (cactus) - Friday, 12 September 2008, 05:47 GMT
Last edited by Andrea Scarpino (BaSh) - Saturday, 03 October 2009, 13:33 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Andrea Scarpino (BaSh)
Architecture All
Severity Low
Priority Normal
Reported Version None
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Note:

While on irc, a user ran into this issue. Reporting for him.

Upstream issue, but listed here for notification. Also..upstream uses bugzilla? I didn't want to create an account just to report this.

Issue description:

autostart.sh for openbox (/etc/xdg/openbox/autostart.sh) uses which to determine if certain binaries exist in the path. This is well and good, except that the version of 'which' that arch uses, reports _not finding things_ to stderr. Older versions (on other distros) just report nothing when not finding a binary in the path, relying on the return value (or lack of an output path) to be sufficient.

Fix:
Add 2>&1 to the test conditions where which is tested. Someone with an account at the upstream bugtracker could reference this ticket I suppose.

Additional info:
* package version(s)
* config and/or log files etc.


Steps to reproduce:
Start openbox with openbox-session, when you do have a custom autostart in ~/.config, so that the system autostart is called. then look in ~/.xsession-errors or on the terminal after startx returns (X is closed when called from the cli).
This task depends upon

Closed by  Andrea Scarpino (BaSh)
Saturday, 03 October 2009, 13:33 GMT
Reason for closing:  Fixed
Additional comments about closing:  openbox 3.4.7.2-3
Comment by eliott (cactus) - Friday, 12 September 2008, 05:49 GMT
correction to above:
Start openbox with openbox-session in .xinitrc, when you do _not_ have a custom autostart in ~/.config, so that the system autostart is called. then look in ~/.xsession-errors or on the terminal after startx returns (X is closed when called from the cli).
Comment by Greg (dolby) - Monday, 02 February 2009, 01:03 GMT
I once wanted to report a small bug in pidgin. It was a very tiny issue so instead of creating an account, i went to the IRC channel and reported it there.
It was fixed in next release. Maybe you could do the same if its an still a problem.

Loading...