Comment 56 for bug 328575
Revision history for this message
| Russel Winder (russel) wrote Re: Cannot start gnome-terminal because of gconf error | #56 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Having just upgraded to Jaunty from Intrepid, I have arrived at this "cannot do 'gksu gnome-terminal'" bug. How did this happen? What change was made Intrepid -> Jaunty that broke this oft used (even if some people consider it the wrong thing to do) feature? I really am not looking for workarounds, I am looking for this not to have been broken in the first place.
This problem has clearly been known about since the beginning of this year and still Jaunty was released with the bug for us unsuspecting people to get hit by.
This really does need to be considered as a security bug and fixed asap: the whole point of using this idiom is that it requires the password and it gives a new type of terminal so that it can be coloured differently from other terminals to show it is a dangerous terminal.