[Wayland-bugs] [Bug 103757] eglGetDisplay() is broken for Wayland

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=103757

--- Comment #10 from Pekka Paalanen  ---
(In reply to Michael Olbrich from comment #9)
> (In reply to Pekka Paalanen from comment #1)
> > Any reason you cannot use EGL_KHR_platform_wayland?
> 
> It's not my code. It's somewhere in gstreamer-vaapi. I was just debugging
> why my application was crashing.

Ok, while this issue is being worked on in Mesa, I would very much recommend
filing a bug against gstreamer-vaapi to start using the EGL platform extensions
whenever available. It's the only reliable way forward.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 103594] Touchpad works horrible

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=103594

--- Comment #9 from Max S  ---
(In reply to Pavel from comment #7)

I have 2 Xiaomi 12.5 here. They already have kernel 4.14 running.

I am typing this now after switching to kernel 4.10.17-2-MANJARO
The problem does definitely not occur! This is reproducable to me only by
switching kernels.

By the way, I use X.org.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 103210] One-finger tap registered as two-finger tap when touch-size-based palm rejection is triggered

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=103210

--- Comment #19 from Peter Hutterer  ---
yep, it's a thumb detection bug. Should be fixed now on that branch with
58bee17f, thanks

-- 
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 101140] Expose an acceleration setting

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=101140

Nate Graham  changed:

   What|Removed |Added

 Resolution|--- |WONTFIX
 Status|REOPENED|RESOLVED

--- Comment #5 from Nate Graham  ---
I've seen the light regarding your perspective on new options after seeing how
masterfully you solved the hysteresis issue. We can fix this in other ways.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 98535] libinput touchpad acceleration tracker bug

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=98535
Bug 98535 depends on bug 101140, which changed state.

Bug 101140 Summary: Expose an acceleration setting
https://bugs.freedesktop.org/show_bug.cgi?id=101140

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |WONTFIX

-- 
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 99268] With Clickfinger behavior, pointer movement briefly turns into a scroll when a thumb is dropped onto the pad

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=99268

--- Comment #7 from Nate Graham  ---
Created attachment 135511
  --> https://bugs.freedesktop.org/attachment.cgi?id=135511=edit
evemu record with git master and kernel 4.13.0

Correction: I was mistakenly using areas mode when I tested; clickfinger mode
still has this issue, I'm afraid, as of tonight's git master and kernel 4.13.0.
evemu recording attached.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 99268] With Clickfinger behavior, pointer movement briefly turns into a scroll when a thumb is dropped onto the pad

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=99268

Nate Graham  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|FIXED   |---

-- 
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 101139] Acceleration still too slow with medium finger movements

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=101139

--- Comment #4 from Greg Reichow  ---
Created attachment 135510
  --> https://bugs.freedesktop.org/attachment.cgi?id=135510=edit
Patch for Macbook Pro 8,2 testing

Patch from libinput 1.9.1 attached

Changes:
1. Added thumb detection based on size, improves detection on MacbookPro
2. Raised height at which thumb detection is triggered (was 15%, now is 40% up
from bottom).  This better matches Apple and the mtrack driver.
3. Lower scroll lock distance threshold
4. New Apple MacbookPro acceleration profile based on MacOS profiling
5. Fixed two finger click to activate right mouse button instead of middle
6. Disabled some gestures that were causing problems
7. Slowed down scrolling speed slightly (may not be working)

NOTE:  The new acceleration profile is only triggered if the touch device
registers as EVDEV_MODEL_APPLE_TOUCHPAD.  This worked for my Macbook Pro 8,2.

The new acceleration profile is pretty fast relative to the standard libinput
settings.  The normal mouse speed setting (for example in Gnome settings) can
be used to adjust the speed.  It adjusts both the speed and acceleration ramp
up.  

All of the other changes are general and may cause problems for non-Apple
products.  I have only tested this on my MacbookPro 8,2.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 99267] Cursor resolution/refresh rate decreases when a thumb is resting on the pad, especially with clickfinger behavior

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=99267

--- Comment #16 from Nate Graham  ---
OK, so I am now running libinput from git master and I have the 4.13.0 kernel,
but there is still no improvement here. xinput still shows "SynPS/2 Synaptics
TouchPad"

How do I turn on RMI4 mode?

-- 
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 101147] Elantech touchpad double Tap Time too short on ASUS Zenbook UX410UQ

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=101147

--- Comment #15 from Peter Hutterer  ---
sorry, completely swamped. I just sent the patch for replacing the tool with a
python version to the list. It doesn't do double-tap yet though.

https://lists.freedesktop.org/archives/wayland-devel/2017-November/035843.html

-- 
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 103594] Touchpad works horrible

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=103594

Peter Hutterer  changed:

   What|Removed |Added

 Depends on||98839

--- Comment #8 from Peter Hutterer  ---
The fixes for bug 98839 should make things a bit better, at least for small
movements.


Referenced Bugs:

https://bugs.freedesktop.org/show_bug.cgi?id=98839
[Bug 98839] Somehow conditionalize hysteresis (hardware black/whitelist, device
property introspection, user-exposed setting, etc)
-- 
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 98839] Somehow conditionalize hysteresis (hardware black/whitelist, device property introspection, user-exposed setting, etc)

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=98839

Peter Hutterer  changed:

   What|Removed |Added

 Blocks||103594


Referenced Bugs:

https://bugs.freedesktop.org/show_bug.cgi?id=103594
[Bug 103594] Touchpad works horrible
-- 
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 101139] Acceleration still too slow with medium finger movements

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=101139

--- Comment #3 from Nate Graham  ---
Greg, if you put that in patch form, I'd love to test it out.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 103594] Touchpad works horrible

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=103594

--- Comment #7 from Pavel  ---
(In reply to Max S from comment #5)

Are you sure it is not libinput, but kernel?

My kernel version is 
4.13.0-16-generic

I have described problems on Ubuntu 17.10 Wayland session. 
BUT on X.org session touchpad works perfect. Almost like my Macbook's touchpad. 

The difference between session is:
Wayland uses libinput
X.org uses synclient

Both sessions use same kernel.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 103594] Touchpad works horrible

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=103594

--- Comment #5 from log...@mx-s.me ---
Hello,

I stumbled upon this bug; I noticed the same behaviour earlier this year.

You can find a short thread here:
https://bbs.archlinux.org/viewtopic.php?pid=1731889#p1731889


I'm pretty sure it is no libinput-related issue but rather a kernel issue,
since I was able to reproduce the issue only in Kernel 4.11, but not in 4.10.


At some point I got stuck, but I am pretty sure that the behaviour got intruced
through some of the changes in this commit:
http://lkml.iu.edu/hypermail/linux/kernel/1702.2/04627.html

I want to point out that the touchpad Synaptics TM3242-001 is in general not
working well. In fact, I am using Peter Hutterer's "hack" (?)
LIBINPUT_MODEL_HP_STREAM11_TOUCHPAD to enforce the option clickfinger on this
touchpad, which it is obviously capable of, but is not being advertised to the
kernel.

I would greatly appreciate any hints on where to submit this - is this a case
for the kernel bug tracker?

-- 
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 103757] eglGetDisplay() is broken for Wayland

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=103757

--- Comment #9 from Michael Olbrich  ---
(In reply to Pekka Paalanen from comment #1)
> Any reason you cannot use EGL_KHR_platform_wayland?

It's not my code. It's somewhere in gstreamer-vaapi. I was just debugging why
my application was crashing.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 103757] eglGetDisplay() is broken for Wayland

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=103757

--- Comment #8 from Michael Olbrich  ---
(In reply to Daniel Stone from comment #7)
> Good point - I guess it'd have to be if
> (_eglPointerIsDereferencable(child_pointer) &&
> _eglPointerIsDereferencable(((char *) child_pointer) + strlen("wl_display")
> + 1) && strcmp(interface->name, "wl_display") == 0) ... ugh. Does that work
> for you?

Yes that works.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 103757] eglGetDisplay() is broken for Wayland

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=103757

--- Comment #7 from Daniel Stone  ---
(In reply to Michael Olbrich from comment #6)
> (In reply to Daniel Stone from comment #2)
> 
> > Michael, I'll attach a compiled but untested patch; can you please let me
> > know if it helps?
> 
> Looks good. It does the right thing for wayland and drm at least.
> is _eglPointerIsDereferencable() sufficient to ensure that the whole string
> is accessible?

Good point - I guess it'd have to be if
(_eglPointerIsDereferencable(child_pointer) &&
_eglPointerIsDereferencable(((char *) child_pointer) + strlen("wl_display") +
1) && strcmp(interface->name, "wl_display") == 0) ... ugh. Does that work for
you?

-- 
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 103757] eglGetDisplay() is broken for Wayland

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=103757

--- Comment #6 from Michael Olbrich  ---
(In reply to Daniel Stone from comment #2)

> Michael, I'll attach a compiled but untested patch; can you please let me
> know if it helps?

Looks good. It does the right thing for wayland and drm at least.
is _eglPointerIsDereferencable() sufficient to ensure that the whole string is
accessible?

-- 
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 103561] libinput 1.8.3 -> 1.9.1: laptop keyboard not working

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=103561

--- Comment #27 from dpaessler  ---
(In reply to Benjamin Berg from comment #26)
but it looks like it might be fixing the issue that dpaessler is seeing.

Thanks for pointing this out, that indeed fixed it for me (kernel 4.14.0). you
really made my day!

-- 
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 103757] eglGetDisplay() is broken for Wayland

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=103757

--- Comment #5 from Daniel Stone  ---
(In reply to Emil Velikov from comment #4)
> 
> I do recall mentioning that exposing the same symbol(s) will lead to bad
> experiences. Followed by some ideas...
> 

Yep, as per the discussion on inlining wayland_drm_buffer_get. :)

It certainly hurts, but then again breaking ABI and forcing every single
Wayland user to rebuild - probably having to change every symbol name in the
API to make sure there was no clash between the two when loaded - would be
uncharted depths of pain.

On the other hand, the solution is the same: look at the interface name, rather
than ever compare pointers equally. Unfortunately, we can't use the same
solution since the wayland-drm one only works for wl_resource in
libwayland-server rather than a plain wl_interface or a wl_proxy ... oh well.

> A better heuristic would be to use dladdr() for eglGetDisplay. See the
> analogous GBM patch [1].

I don't think that would necessarily fix it, particularly if the
wayland-client.so.1 being loaded differed, e.g. due to people linking their own
copies?

-- 
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 103757] eglGetDisplay() is broken for Wayland

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=103757

--- Comment #4 from Emil Velikov  ---

I do recall mentioning that exposing the same symbol(s) will lead to bad
experiences. Followed by some ideas...


WRT eglGetDisplay - I'd recommend moving towards the EGL_*_platform_*
extensions ASAP - EGL_EXT_platform_wayland or EGL_KHR_platform_wayland in this
case.

A better heuristic would be to use dladdr() for eglGetDisplay. See the
analogous GBM patch [1].


https://patchwork.freedesktop.org/patch/187918/

-- 
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 103673] Missing mouse button release event when multiple buttons are released

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=103673

--- Comment #3 from Antti Korpi  ---
Just confirming that I agree this is a duplicate. Thanks!

-- 
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 103757] eglGetDisplay() is broken for Wayland

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=103757

--- Comment #3 from Daniel Stone  ---
Created attachment 135490
  --> https://bugs.freedesktop.org/attachment.cgi?id=135490=edit
egldisplay-try-interface-name-for-wl-display.patch

-- 
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 103757] eglGetDisplay() is broken for Wayland

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=103757

--- Comment #2 from Daniel Stone  ---
(In reply to Pekka Paalanen from comment #1)
> eglGetDisplay() is by definition broken on multi-platform implementations,
> yes.

Ugh. It is broken by definition, but Mesa does go to great lengths to try to
make it work by auto-detecting: see _eglNativePlatformDetectNativeDisplay()
inside src/egl/main/egldisplay.c.

Michael, I'll attach a compiled but untested patch; can you please let me know
if it helps?

-- 
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 790201] Settings in ~/.config/gtk-3.0/settings.ini ignored with GDK_BACKEND=wayland

[gtk+]

https://bugzilla.gnome.org/show_bug.cgi?id=790201

--- Comment #4 from Alex Ivanov  ---
Created attachment 363679
  --> https://bugzilla.gnome.org/attachment.cgi?id=363679=edit
don't provide gsetting if dconf is not available

Fix for Emmanuele Bassi case
> Alternatively, remove dconf, and GTK will use the settings.ini file
Prior default from translation table
(https://git.gnome.org/browse/gtk+/tree/gdk/wayland/gdkdisplay-wayland.c#n1571)
was taken. In init_settings() we return if
g_settings_schema_source_get_default() fails, so we should do in
gdk_wayland_display_get_setting(). This now matches what gdkscreen-x11.c does
(in case of not available xsettings)
https://git.gnome.org/browse/gtk+/tree/gdk/x11/gdkscreen-x11.c#n958

However this patch doesn't fix the issue, since at least some distributions
wrap Gtk3 programs with GSettings schemas path
https://github.com/NixOS/nixpkgs/blob/master/pkgs/applications/networking/p2p/transmission/default.nix#L46

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 103757] eglGetDisplay() is broken for Wayland

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=103757

--- Comment #1 from Pekka Paalanen  ---
eglGetDisplay() is by definition broken on multi-platform implementations, yes.

Any reason you cannot use EGL_KHR_platform_wayland?

-- 
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 103757] eglGetDisplay() is broken for Wayland

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=103757

Bug ID: 103757
   Summary: eglGetDisplay() is broken for Wayland
   Product: Mesa
   Version: git
  Hardware: Other
OS: All
Status: NEW
  Severity: normal
  Priority: medium
 Component: EGL/Wayland
  Assignee: wayland-bugs@lists.freedesktop.org
  Reporter: m.olbr...@pengutronix.de
QA Contact: mesa-...@lists.freedesktop.org

_eglNativePlatformDetectNativeDisplay() (called by eglGetDisplay()) detects
Wayland by checking if the native display object starts with a pointer to
wl_display_interface.

Unfortunately wl_display_interface is defined in both libwayland-server.so and
libwayland-client.so. libEGL links to both and in all my tests it always picks
the one from libwayland-server.so.
The wl_display object passed as native display however contains the version
from libwayland-client.so so the check fails.

There is an old thread about this[1] on the wayland-devel list, but it seems
nothing happened since then.

[1]
https://lists.freedesktop.org/archives/wayland-devel/2014-October/017783.html

-- 
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 790201] Settings in ~/.config/gtk-3.0/settings.ini ignored with GDK_BACKEND=wayland

[gtk+]

https://bugzilla.gnome.org/show_bug.cgi?id=790201

--- Comment #3 from Alex Ivanov  ---
> My strong suggestion is for you to change the GSettings, if you're running 
> under Wayland, instead of trying to use a key/value file for everything

That's hard to achieve outside of Gnome, because then I need to figure what
exact parts of Gnome (gnome session, gnome settings and etc daemons) to run to
get Gtk3 applications see my dconf settings.
Also available customization programs like lxappearance or kde-gtk-config still
use settings.ini.

> Alternatively, remove dconf, and GTK will use the settings.ini file

Strange, but that doesn't work for me. If dconf is not available, then
gdkscreen-wayland uses built-in defaults
https://git.gnome.org/browse/gtk+/tree/gdk/wayland/gdkdisplay-wayland.c#n1571
forcibly overriding GtkSettings.
Here's another user having the same issue
https://bbs.archlinux.org/viewtopic.php?id=225553

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 790201] Settings in ~/.config/gtk-3.0/settings.ini ignored with GDK_BACKEND=wayland

[gtk+]

https://bugzilla.gnome.org/show_bug.cgi?id=790201

Emmanuele Bassi (:ebassi)  changed:

   What|Removed |Added

 CC||eba...@gmail.com

--- Comment #2 from Emmanuele Bassi (:ebassi)  ---
I very, *very* much doubt we're going to add a new environment variable for
that, but I'll let the maintainer of GTK to answer this authoritatively.

The only reason why the X11 backend falls back to the settings.ini file is
because you're clearly not running an XSettings bridge, to expose settings
(coming from GSettings, in the GNOME/GTK case) over X11 events. Since Wayland
does not have this weird contraption, we access GSettings directly, if its
available on the system.

My strong suggestion is for you to change the GSettings, if you're running
under Wayland, instead of trying to use a key/value file for everything.
Alternatively, remove dconf, and GTK will use the settings.ini file.

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 790201] Settings in ~/.config/gtk-3.0/settings.ini ignored with GDK_BACKEND=wayland

[gtk+]

https://bugzilla.gnome.org/show_bug.cgi?id=790201

--- Comment #1 from Alex Ivanov  ---
Created attachment 363663
  --> https://bugzilla.gnome.org/attachment.cgi?id=363663=edit
ability to use GtkSettings under Wayland

This patch adds GDK_WAYLAND_USE_GTKSETTINGS environment variable which when is
set allows to pick settings from GtkSettings (settings.ini and friends) instead
of GSettings (dconf and friends)

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 103476] RFE: libinput: Add support for Trust TB-4200 Wireless Scroll Tablet (Aiptek based)

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=103476

--- Comment #5 from Martin Kolman  ---
(In reply to Peter Hutterer from comment #4)
> ping?

Sorry, I was quite busy so far, but I should be able to take a look at it on
Friday. :)

-- 
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs