Terminal Emulator is set to an empty Custom command by default

Bug #133130 reported by Chris Lee
22
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
Fix Released
Low
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gnome-panel

I have a custom application launcher on my gnome-panel, which was working (in Gutsy) before the last day or two. The launcher is for an application in a terminal. The '_Command' is a script, which is runnable. When I press the launcher button on the panel, a dialog reports

   Could not launch application

   Failed to execute child process "-x" (No such file or directory)

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. What command are you putting in the entry of the launcher? works fine here with "gnome-terminal -x /usr/local/bin/lalala" and that script with execution permission of course, may you check and tell us? thanks.

Changed in gnome-panel:
assignee: nobody → desktop-bugs
status: New → Incomplete
Revision history for this message
Chris Lee (chris-lee-gertner) wrote :

If I select

   '_Type': Application
   '_Command:' gnome-terminal -x {my-script}

it works, but if I do:

  '_Type': Application in terminal
  '_Command': {my-script}

I get the error.

Revision history for this message
Chris Lee (chris-lee-gertner) wrote :

Oh -- I figured it out.

I went to 'System->Preferences->Preferred Applications->System'

and saw that my 'Terminal emulator' was 'Custom' with no command.

I switched to 'gnome-terminal', and all was OK.

So I guess there was maybe some change in gconf usage, probably gnome-wide (not related to gnome-panel) that caused my terminal emulator setting to get lost or something on upgrade. I have never explicitly changed this -- I've always used the default emulator on this system, which has always been gnome-terminal.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Yes is empty here too, re-assigning to gnome-control-center, thanks.

Changed in gnome-panel:
importance: Undecided → Low
status: Incomplete → Triaged
Revision history for this message
Sebastien Bacher (seb128) wrote :

does it work with a new user? the schemas has the correct value and that looks like an user configuration issue

Changed in gnome-control-center:
status: Triaged → Incomplete
Revision history for this message
Chris Lee (chris-lee-gertner) wrote :

I created a new user to test. The setting was correct for the new user.

(p.s., Interestingly, desktop effects worked for the new user, while they no longer work for my account(!!). I guess the problem is not my xserver settings....).

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Not an issue anymore for me with a new user, may someone else confirm? I'm using Gutsy with full updates till today.

Revision history for this message
Chris Lee (chris-lee-gertner) wrote :

Seems not an issue for me either. Looks good.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Marking it as fixed then, thanks for your report.

Changed in gnome-control-center:
status: Incomplete → Fix Released
Revision history for this message
Justin Dugger (jldugger) wrote :

Uh... does upgrading work correctly then? I don't think it's wise to simply mark the bug closed simply because you can create a new user to fix the upgrade.

Revision history for this message
Chris Lee (chris-lee-gertner) wrote :

The correct terminal setting is now preserved for the user I'm using all the time. Previously, it would "forget" the setting each time I logged off. So I think upgrading should be OK.

Revision history for this message
Nthalk (phocis) wrote :

I'm confirming that this bug exists when doing a dist-upgrade from feisty to gutsy flight 5.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.