Your message dated Fri, 20 Apr 2007 08:28:41 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#419920: gtk-qt-engine: Gtk application(s) not accessing
.gtkrc-2.0-kde
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: gtk-qt-engine
Version: 1:0.8~svn-rev36-2
Severity: normal
On a fresh install of gtk-qt-engine, I open the "GTK Styles and Fonts" section
in the KDE control center and select "Use my KDE style in GTK
applications". This creates the file .gtkrc-2.0-kde. However, at least some gtk
applications don't access this file. When I run strace
gnome-system-monitor, I see this:
lstat("/etc/gtk-2.0/gtkrc", 0x7fff7deaace0) = -1 ENOENT (No such file or
directory)
access("/etc/gtk-2.0/gtkrc.en_US", F_OK) = -1 ENOENT (No such file or directory)
access("/etc/gtk-2.0/gtkrc.en", F_OK) = -1 ENOENT (No such file or directory)
lstat("/home/tna/.gtkrc-2.0", 0x7fff7deaace0) = -1 ENOENT (No such file or
directory)
access("/home/tna/.gtkrc-2.0.en_US", F_OK) = -1 ENOENT (No such file or
directory)
access("/home/tna/.gtkrc-2.0.en", F_OK) = -1 ENOENT (No such file or directory)
lstat("/home/tna/.gnome2/gtkrc-2.0", 0x7fff7deaace0) = -1 ENOENT (No such file
or directory)
access("/home/tna/.gnome2/gtkrc-2.0.en_US", F_OK) = -1 ENOENT (No such file or
directory)
access("/home/tna/.gnome2/gtkrc-2.0.en", F_OK) = -1 ENOENT (No such file or
directory)
lstat("/home/tna/.gnome2/gnome-system-monitorrc", 0x7fff7deaace0) = -1 ENOENT
(No such file or directory)
access("/home/tna/.gnome2/gnome-system-monitorrc.en_US", F_OK) = -1 ENOENT (No
such file or directory)
access("/home/tna/.gnome2/gnome-system-monitorrc.en", F_OK) = -1 ENOENT (No
such file or directory)
access("/home/tna/.themes/Raleigh/gtk-2.0/gtkrc", F_OK) = -1 ENOENT (No such
file or directory)
access("/usr/share/themes/Raleigh/gtk-2.0/gtkrc", F_OK) = 0
lstat("/usr/share/themes/Raleigh/gtk-2.0/gtkrc", {st_mode=S_IFREG|0644,
st_size=69, ...}) = 0
open("/usr/share/themes/Raleigh/gtk-2.0/gtkrc", O_RDONLY) = 16
read(16, "#\n# This theme is the default th"..., 4000) = 69
If I rename the file .gtkrc-2.0, it works.
Dave
-- System Information:
Debian Release: 4.0
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.19.1 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ISO-8859-1) (ignored: LC_ALL set to en_US)
Shell: /bin/sh linked to /bin/bash
Versions of packages gtk-qt-engine depends on:
ii libc6 2.5-2 GNU C Library: Shared libraries
ii libglib2.0-0 2.12.11-3 The GLib library of C routines
ii libgtk2.0-0 [gtk2.0-binver-2. 2.10.11-2 The GTK+ graphical user interface
ii libpango1.0-0 1.16.2-1 Layout and rendering of internatio
ii libqt3-mt 3:3.3.7-3 Qt GUI Library (Threaded runtime v
ii libstdc++6 4.1.1-21 The GNU Standard C++ Library v3
ii libx11-6 2:1.0.3-5 X11 client-side library
gtk-qt-engine recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Closing bug on request of submitter.
Am 19.04.2007 00:45 schrieb David Liontooth:
> Bastian Venthur wrote:
>> A workaround this bug could be to source the .gtkrc-2.0-kde in your
>> remote .bashrc (or whatever shell you use), but please note that then
>> you enable gtk-qt-engine for all desktop environments for you on this
>> machine (which could cause problems).
>>
> Well, this sounds fine to me, and seems to be working well. I just
> append this to .bashrc:
>
> # Make sure our customised gtkrc file is loaded.
> # (Activated independently of desktop environment.)
> export GTK2_RC_FILES=$HOME/.gtkrc-2.0-kde
>
> Please close the bug report; no need to keep it lingering around. If
> David finds a more
> elegant solution, let me know!
--
Bastian Venthur http://venthur.de
Debian Developer venthur at debian org
--- End Message ---
