[gentoo-user] ethereal dies abruptly

[gentoo-user] ethereal dies abruptly

[James]

Hello,

Ethereal use to work perfectly. Recently I upgraded to the newest
(portage) version of Ethereal. Now, when I terminate a capture
session, the entire Ethereal application dies off. Is there
a bug (I could not find) or did the default configuration change
or did I miss something that I need to configure, to keep the
Ethereal application running even after capture terminations?

If I try to restart a live running sessoin, it dies too. The previous 
(portage) version of ethereal did not behave like this? 

Is there a config file or somewhere in the ebuild I could check the
settings upon initialization?  Nothing I've found in the man pages
or /usr/share/ethereal/help  seems prevent  this crashing after
a capture session is terminated....

puzzled.

James

-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: ethereal dies abruptly

[James]

James <wireless <at> tampabay.rr.com> writes:

> Ethereal use to work perfectly. Recently I upgraded to the newest
> (portage) version of Ethereal. Now, when I terminate a capture
> session, the entire Ethereal application dies off. 

Well, I downgraded (isn't eix wonderful?) to ethereal 0.10.11

I got the same problem, but more details on the failure
<snip>
/home/james/.kde3.4/share/config/gtkrc:37: error: unexpected identifier
`gtk-alternative-button-order', expected keyword - e.g. `style'
<snip>

So I commented out line 37 in gtkrc
#gtk-alternative-button-order = 1

Now it does not die upon termination of a capture session....

looks like a kde_vs_gtk config/parameter feud....

so I re emerged the latest (portage) version of ethereal.

It now works fine, so line 37 in 
/home/james/.kde3.4/share/config/gtkrc:37
was/is the problem....


Comments or a more robust method of fixing/patching ethereal?

James


-- 
gentoo-user@gentoo.org mailing list