Bug 431330

Funny, I just put a newer upstream version in updates-testing 10 days ago. :-)

Could you try:

yum --enablerepo=updates-testing upgrade clusterssh

and let me know if 3.22-1.fc8 is similarly affected?

If not, I think I'll be pushing that to updates-released sooner rather than later.

Thanks!

Hello,

Sorry, the latest upstream in updates-testing is similarly affected ... 
I don't know what have changed in perl-tk but something have broke clusterssh.

Cheers. 

Poking upstream.  Hi Duncan!

I can confirm, clusterssh-3.22-1 fails to display its menus with
perl-Tk-804.028-2, but succeeds with 804.027-12.  Duncan, any potential thoughts
on this?  The former was apparently released to Fedora on or around 2008-01-11;
I admit I must have overlooked the lack of menus during my testing (I mainly use
the text entry field).  And huh: with the older perl-Tk, I'm getting those
segfaults again!

This does seem to be an issue with Tk rather than cssh - the only reports I have had about this are on FC8 
and I don't have access to that OS any more to investigate further.

  Duncs

Duncan is correct, the problem lies with the perl-Tk package.

The menus appear correctly when using a build of Tk-804.028 straight from CPAN.
The segfault-on-disconnect problem also doesn't occur, at least with the basic
testing I've done.

It do not seem i can change the "assigned to" field ... only the component.

Is there any bugzilla master out there ? ;)

So, it looks like the menu problem is due to this section from the
perl-Tk-seg.patch:

+
+    if (!optionPtr->specPtr->type) {
+       return NULL;
+    }
+

I reworked the patch to take out that section, and the menus come right back. I
also tested the failure case from bz 235666 (which was the original reason for
the patch), and I couldn't reproduce it.

With the reworked patch, make test also passes (it was failing before). It also
resolves upstream bug 33880. I've committed the changes to rawhide, and I'll let
the perl-Tk maintainer do the F-7/F-8 errata. ;)

Fixed rawhide build: http://koji.fedoraproject.org/koji/buildinfo?buildID=42646

Hi,

Any chance to have this fix pushed to F-8 and F-7 ?

Cheers.

Can we please have this pushed to F-8?

This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '8'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 8's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 8 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

This issue is resolved in F10 (Tested on x86_64 install)