<html>
    <head>
      <base href="https://bugzilla.gnome.org/" />
    </head>
    <body>
      <p>
        <div>
            <b><a class="bz_bug_link 
          bz_status_NEW "
   title="NEW - gdk/wayland: Add support for the gtk-enable-primary-paste gsetting"
   href="https://bugzilla.gnome.org/show_bug.cgi?id=775846#c4">Comment # 4</a>
              on <a class="bz_bug_link 
          bz_status_NEW "
   title="NEW - gdk/wayland: Add support for the gtk-enable-primary-paste gsetting"
   href="https://bugzilla.gnome.org/show_bug.cgi?id=775846">bug 775846</a>
              from <span class="vcard"><a href="page.cgi?id=describeuser.html&login=tiagomatos%40gmail.com" title="Rui Matos <tiagomatos@gmail.com>"> <span class="fn">Rui Matos</span></a>
</span></b>
        <pre>Created <span class=""><a href="attachment.cgi?id=343170&action=diff" name="attach_343170" title="gdk/wayland: Handle non-existant gsettings keys">attachment 343170</a> <a href="attachment.cgi?id=343170&action=edit" title="gdk/wayland: Handle non-existant gsettings keys">[details]</a></span> <a href='review?bug=775846&attachment=343170'>[review]</a>
gdk/wayland: Handle non-existant gsettings keys

Since we're a library, crashing on gsettings keys, whose presence is out
of our control, isn't appropriate.
--

I was going to push but realized that unlike other modules, I don't
think gtk+ (particularly the 3-22 branch) can depend on a new enough
gsettings-desktop-schemas, so I think we'll need something like this
patch too.</pre>
        </div>
      </p>
      <hr>
      <span>You are receiving this mail because:</span>
      
      <ul>
          <li>You are on the CC list for the bug.</li>
      </ul>
    </body>
</html>