After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 663518 - dasher.gschema.xml: invalid name 'DrawMouseLine': must begin with a lowercase letter
dasher.gschema.xml: invalid name 'DrawMouseLine': must begin with a lowercase...
Status: RESOLVED OBSOLETE
Product: dasher
Classification: Applications
Component: general
4.11
Other Linux
: Normal minor
: ---
Assigned To: Patrick Welche
dasher-maint
: 753089 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2011-11-06 18:13 UTC by André Klapper
Modified: 2021-05-26 09:58 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Proposed patch. (9.58 KB, patch)
2014-01-24 21:59 UTC, Mike Gorse
none Details | Review

Description André Klapper 2011-11-06 18:13:04 UTC
After adding the lines

  <autotools id="dasher" autogenargs="--with-gnome">
    <branch/>
    <dependencies>
      <dep package="intltool"/>
      <dep package="at-spi"/>
      <dep package="gnome-doc-utils"/>
    </dependencies>
  </autotools>

to my jhbuild moduleset definitions I ran the command

  jhbuild buildone -afc dasher

The very last output is:

make[1]: Leaving directory `/home/andre/git-gnome/dasher'
I: Moving temporary DESTDIR u'/home/andre/opt-gnome/_jhbuild/root-dasher' into build prefix
I: Install complete: 505 files copied
I: Running post-installation trigger script: 'glib'
/home/andre/opt-gnome//share/glib-2.0/schemas/dasher.gschema.xml: Error on line 4 char 1: invalid name 'DrawMouseLine': names must begin with a lowercase letter.  This entire file has been ignored.
I: Running post-installation trigger script: 'gtk+'
gtk-update-icon-cache: Cache file created successfully.
Comment 1 Patrick Welche 2011-11-10 12:45:39 UTC
In Data/Makefile.am I use

compile-schemas: dasher.gschema.xml
        $(GLIB_COMPILE_SCHEMAS) --allow-any-name $(schemasdir)

Does your binary no longer support --allow-any-name? (I know it is there as a "temporary" measure - the problem is that I use the same names for the Windows registry. Just changing the names would break it, so again, this cosmetic gconf->gsettings change has more consequences than immediately evident.)
Comment 2 Mike Gorse 2014-01-24 21:59:30 UTC
Created attachment 267162 [details] [review]
Proposed patch.

Patch to modify key names when creating a gsettings schema or read/write keys. Shouldn't affect environments that don't use gsettings.
Comment 3 Patrick Welche 2015-08-18 10:20:27 UTC
*** Bug 753089 has been marked as a duplicate of this bug. ***
Comment 4 André Klapper 2021-05-26 09:58:22 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new enhancement request ticket at
  https://gitlab.gnome.org/GNOME/dasher/-/issues/

Thank you for your understanding and your help.