| 1 |
James <wireless <at> tampabay.rr.com> writes: |
| 2 |
|
| 3 |
> Ethereal use to work perfectly. Recently I upgraded to the newest |
| 4 |
> (portage) version of Ethereal. Now, when I terminate a capture |
| 5 |
> session, the entire Ethereal application dies off. |
| 6 |
|
| 7 |
Well, I downgraded (isn't eix wonderful?) to ethereal 0.10.11 |
| 8 |
|
| 9 |
I got the same problem, but more details on the failure |
| 10 |
<snip> |
| 11 |
/home/james/.kde3.4/share/config/gtkrc:37: error: unexpected identifier |
| 12 |
`gtk-alternative-button-order', expected keyword - e.g. `style' |
| 13 |
<snip> |
| 14 |
|
| 15 |
So I commented out line 37 in gtkrc |
| 16 |
#gtk-alternative-button-order = 1 |
| 17 |
|
| 18 |
Now it does not die upon termination of a capture session.... |
| 19 |
|
| 20 |
looks like a kde_vs_gtk config/parameter feud.... |
| 21 |
|
| 22 |
so I re emerged the latest (portage) version of ethereal. |
| 23 |
|
| 24 |
It now works fine, so line 37 in |
| 25 |
/home/james/.kde3.4/share/config/gtkrc:37 |
| 26 |
was/is the problem.... |
| 27 |
|
| 28 |
|
| 29 |
Comments or a more robust method of fixing/patching ethereal? |
| 30 |
|
| 31 |
James |
| 32 |
|
| 33 |
|
| 34 |
-- |
| 35 |
gentoo-user@g.o mailing list |
Archives