© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
I'm the developer of SSHMenu - here's my response to a similar report on SourceForge:
I don't have access to a system with the latest gnome-terminal, so remote debugging is the order of the day :-)
Ultimately, all SSHMenu does is call gnome-terminal with a list of arguments. I'm guessing that the gnome-terminal segfault will be reproducible if we can directly invoke gnome-terminal with the same arguments - and thus take SSHMenu out of the equation.
Looking at the commit history for gnome-terminal, it looks like command-line option handling was ported from popt to Goption in January and this may be relevant.
It's also possible that gnome-terminal's valid options have changed and SSHMenu will need to be tweaked to generate command lines compatible with the new version.
If a host is defined in SSHMenu with these parameters ...
Title: Local Host
Hostname: localhost
Geometry:
Profile: <None>
... then this is the command which will be run:
gnome-terminal --title="Local Host" -e "sh -c \"ssh localhost\""
If the geometry is set to the top right corner then this command will be run:
gnome-terminal --geometry=
If the "Big Font" profile is selected, then this command will be run:
gnome-terminal --geometry=
If a non-Unicode Polish locale is selected by setting:
Hostname: LC_ALL=
Then this command will be run:
LC_ALL=
Can you please try these commands and see if any of them cause the same segfault?
The latest version of sshmenu.rb in subversion accepts a '-d' option which enables debugging output to STDOUT. I use it by invoking the standalone (non-applet) version of SSHMenu like this:
sshmenu-gnome -d
The latest version of this library is here:
https:/
Let me know how you get on.
Thanks
Grant
<email address hidden>