After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 412063 - can't launch gnome-terminal with a specified profile
can't launch gnome-terminal with a specified profile
Status: RESOLVED INVALID
Product: gnome-terminal
Classification: Core
Component: general
2.16.x
Other All
: Normal normal
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
: 528679 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-02-25 22:42 UTC by John Pye
Modified: 2008-07-03 12:24 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description John Pye 2007-02-25 22:42:56 UTC
Please describe the problem:
It seems that the command-line options for gnome-terminal are missing the necessary options to launch gnome-terminal with a specified profile, as opposed to opening and *additional* window, which the --window-with-profile option does.


Steps to reproduce:
I have added a launcher to my gnome-panel which runs

gnome-terminal --window-with-profile=ipython

with ipython being a named profile in my gnome-terminal configuration. 

Actual results:
This launcher opens *two* windows -- one with my default profile and another with my ipython profile.

Expected results:
A single window with the 'ipython' profile

Does this happen every time?
Yes

Other information:
gnome-terminal --help explains that this is the intended behaviour, but I think that the intended behaviour is wrong in the case where there are not yet any open gnome-terminal windows.
Comment 1 Ryan Hayle 2007-10-27 06:48:13 UTC
I can't reproduce this with 2.18 and have never seen this behaviour.  I have used gnome-terminal --window-with-profile in my startup session for years.
Comment 2 Christian Persch 2008-05-29 20:44:35 UTC
*** Bug 528679 has been marked as a duplicate of this bug. ***
Comment 3 Christian Persch 2008-06-24 18:25:53 UTC
Not reproducible on svn trunk either, closing.
Comment 4 John Pye 2008-07-03 12:24:13 UTC
Looks right. Possibly the problem was that when creating the Launcher, I may have selected the 'Application in Terminal' option. In any case, I was able now to create launchers with the correct behaviour.