Mailinglist Archive: opensuse-bugs (4297 mails)

< Previous Next >
[Bug 1041500] New: Documentation comment in system-wide default gtkrc refers to non-existent gtk2-doc package
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Tue, 30 May 2017 01:27:10 +0000
  • Message-id: <>

Bug ID: 1041500
Summary: Documentation comment in system-wide default gtkrc
refers to non-existent gtk2-doc package
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 42.2
Hardware: x86-64
OS: openSUSE 42.2
Status: NEW
Severity: Minor
Priority: P5 - None
Component: GNOME
Assignee: bnc-team-gnome@xxxxxxxxxxxxxxxxxxxxxx
Reporter: nedu@xxxxxxxxxxxx
QA Contact: qa-bugs@xxxxxxx
Found By: ---
Blocker: ---

User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
Build Identifier:

openSUSE Leap 42.2
package gtk2-branding-openSUSE-13.1-1.2.noarch.rpm
contains file /etc/gtk-2.0/gtkrc

That system-wide default gtkrc file begins with a comment. That comment refers
to further documentation in the non-existent "gtk2-doc package".

Reproducible: Always

Steps to Reproduce:
1. cat /etc/gtk-2.0/gtkrc
2. zypper info gtk2-doc

Actual Results:
$ cat /etc/gtk-2.0/gtkrc #partial extract from comment

# For complete list of available settings see devhelp documentation in
# gtk2-doc package, section GTK+ Core Reference -> Resource Files

$ zypper info gtk2-doc #partial output
package 'gtk2-doc' not found.

Expected Results:
Comment in gtkrc file should refer to a locatable resource.

Note especially that the gtkrc comment does NOT and most probably should NOT
refer to the gtk-doc package, despite the lexical similarity between "gtk2-doc"
(in comment) and "gtk-doc" (an actual package in repository).

Rather the correct reference apparently would be to the gtk2-devel package.

However, from the standpoint of administrative convenience, it might make more
sense for this gtkrc comment to refer the reader to the online docs at--

Looking at the larger picture, though, a user or system administrator looking
for further info on the gtkrc file may find the developer-oriented
documentation to be rather opaque.

You are receiving this mail because:
You are on the CC list for the bug.
< Previous Next >
This Thread
  • No further messages