Start-UP Command Field Doesn't Support More Than One Command
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-session (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
I have an application (sudo apt-get install autokey-qt) that doesn't provide an option to launch minimized (see https:/
In Startup Applications, I attempted to solve this problem by running two command at once:
autokey-qt ; wmctrl -k on
From the command line the line above both launches autokey-qt and minimizes all windows, but as a Startup-
It would be nice if Startup Applications supported the ability to both (1) "allow you to launch an application" and (2) allow you to provide an additional command for controlling the window of that application.
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: gnome-session-
ProcVersionSign
Uname: Linux 3.5.0-18-generic x86_64
ApportVersion: 2.6.1-0ubuntu6
Architecture: amd64
Date: Wed Nov 14 08:51:32 2012
Dependencies:
InstallationDate: Installed on 2012-10-19 (26 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MarkForUpload: True
PackageArchitec
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-session
UpgradeStatus: No upgrade log present (probably fresh install)
summary: |
- Start Command Field Doesn't Support More Then One Command + Start-UP Command Field Doesn't Support More Then One Command |
summary: |
- Start-UP Command Field Doesn't Support More Then One Command + Start-UP Command Field Doesn't Support More Than One Command |
description: | updated |
description: | updated |
Thank you for reporting this bug to Ubuntu.
Ubuntu 12.10 (quantal) reached end-of-life on May 16, 2014.
See this document for currently supported Ubuntu releases: /wiki.ubuntu. com/Releases
https:/
We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed.