| Summary: | starting gtk apps from within kde forces default gtk engine | ||
|---|---|---|---|
| Product: | [Applications] systemsettings | Reporter: | Alexander Jenisch <nt> |
| Component: | general | Assignee: | David Faure <faure> |
| Status: | CLOSED FIXED | ||
| Severity: | normal | CC: | finex, kevin.kofler, rdieter, tuju |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | don't lose systemGtkrc | ||
|
Description
Alexander Jenisch
2007-06-14 12:46:39 UTC
I have this behaviour in KDE 4 from SVN. You can try a workaround here: http://www.kde-forum.org/thread.php?threadid=18141 It doesn't help, KDE4 overwrites it on restart. I tried setting file attribute +i and changing permissions but KDE4 still must have read/write access to ~/.kde/share/config directory so it just DELETES the file and recreates it!!! A major flaw. Why not leave GTK apps alone if not do it properly. Same problem here. I created 2 "scripts" (for Firefox and Thunderbird) and saved them on the desktop, so I don't need to run the commands from a terminal. If I start gtk apps from the menu, I get the ugly GTK default theme. This blog entry describes as well what this bug consists of: http://vizzzion.org/?blogentry=814 confirmed, see also related downstream report: https://bugzilla.redhat.com/show_bug.cgi?id=443309 Created attachment 24672 [details]
don't lose systemGtkrc
Here's a patch we tested to work, to ensure that systemGtkrc doesn't get lost.
Not sure exactly why the old code didn't work (it's almost the same as the kde3
versions that were ok).
I couldn't figure out why the old code doesn't work anymore either, all I know is that the above patch (which I wrote and Rex tested) makes it more robust and in particular makes it work. :-) No idea why this bug is assigned to me ;) Kevin Kofler: you committed to this code previously, I see, feel free to commit your fix. SVN commit 805915 by rdieter: BUG: 146779 Not sure exactly why the old code didn't work (it's almost the same as the kde3 versions that were ok), butthis ensures systemGtkrc doesn't get lost. M +6 -5 krdb.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=805915 SVN commit 805916 by rdieter: CCBUG: 146779 backport fix from trunk. Not sure exactly why the old code didn't work (it's almost the same as the kde3 versions that were ok), but this ensures systemGtkrc doesn't get lost. M +6 -5 krdb.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=805916 This isn't working. SVN from today. Ubuntu 8.04, self compiled binaries. echo GTK2_RC_FILES outputs /etc/gtk/gtkrc:/home/orville/.gtkrc::/home/orville/.kde/share/config/gtkrc As you can see there's something missing between the gtkrc found in home and the one in $kdehome. Can't help out more after this as it's not my machine. The problem there is that you have /etc/gtk/gtkrc instead of /etc/gtk-2.0/gtkrc (and other GTK+ 1 config files), I don't know why. Are you sure what you posted is GTK2_RC_FILES and not GTK_RC_FILES? Bug closed. Kdesktop is no more mantained. This is about KDE 4 (the kcontrol/krdb code in kdebase-workspace), not the KDE 3 kdesktop. Reassigning to systemsettings for lack of a more fitting category. But it's already fixed anyway. |