James wrote:
Richard Fish <bigfish <at> asmallpond.org> writes:
When I run ethereal as root (su -p) in a kde session,
it dies off when I end the capture session. I do not use
gnome, so I do not know if the problem exist there.
If I comment out this line:
gtk-alternative-button-order = 1
#gtk-alternative-button-order = 1
in the file:
.kde3.4/share/config/gtkrc
It does not die off (temporary fix)
But each time I reboot the portable
I have to edit the file again.
What KDE theme & style are you using? I don't seem to have this setting
(or problem) in my gtkrc file...so I think maybe it is a theme-specific
issue.
Good question. I have never set this(these) setting. Going through
'control panel'
Theme Manager Nothing is selected or highlighted under
'Choose your visual KDE theme:
At the bottom under 'style' is says 'plastik is the 'widget style'.
Can you be more specific as to what parameters I need to look at,
or maybe they are consolitdated in a config file somewhere?
James
You can check your current style/theme at:
~ > grep CurrentTheme .kde3.4/share/config/kcmthememanagerrc
CurrentTheme=Plastik
~ > grep widgetStyle .kde3.4/share/config/kdeglobals
widgetStyle=Plastik
Also, I did some more checking. I do not have the
gtk-alternative-button-order setting in .kde3.4/share/config/gtkrc file,
but it *is* in my .kde3.4/.../gtkrc-2.0 file. Coincidentally, my USE
flags for ethereal specify gtk2.0:
carcharias rjf # emerge -Dv --pretend ethereal
...
[ebuild R ] net-analyzer/ethereal-0.10.12 -adns -gtk +gtk2 +ipv6
-kerberos -snmp +ssl 0 kB
Are you building ethereal against gtk1.2 or gtk2.0?
-Richard
--
gentoo-user@gentoo.org mailing list
