[Mesa-dev] [Bug 104926] swrast: Mesa 17.3.3 produces: HW cursor for format 875713089 not supported

2018-09-19 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=104926

Adam Jackson  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

--- Comment #9 from Adam Jackson  ---
commit 194bf0a2e01769f4b29df06febf27ce340c1cd68 (HEAD -> master, origin/master,
origin/HEAD)
Author: Michal Srb 
Date:   Thu Mar 15 17:27:57 2018 +0100

st/dri: don't set queryDmaBufFormats/queryDmaBufModifiers if the driver
does not implement it

This is equivalent to commit a65db0ad1c3, but for dri_kms_init_screen.
Without
this gbm_dri_is_format_supported always returns false.

Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=104926
Fixes: e14fe41e0bf ("st/dri: implement createImageFromRenderbuffer(2)")
Reviewed-by: Emil Velikov 
Reviewed-by: Adam Jackson 
Tested-by: Adam Williamson 

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


[Mesa-dev] [Bug 104926] swrast: Mesa 17.3.3 produces: HW cursor for format 875713089 not supported

2018-09-19 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=104926

--- Comment #8 from Adam Williamson  ---
Confirmed the patch fixes the error message flood, makes my VM cursor move much
more smoothly, and somehow seems to fix paste from the host system into the VM
too. Maybe I should see if it can pick my lotto numbers for me as well...

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


[Mesa-dev] [Bug 104926] swrast: Mesa 17.3.3 produces: HW cursor for format 875713089 not supported

2018-09-19 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=104926

--- Comment #7 from Adam Williamson  ---
I'm seeing exactly these same message floods running Fedora 29 images in VMs,
and indeed the fix seems to have got lost - there was one reply to the message,
then crickets after that, and it's still broken in git master. :(

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


[Mesa-dev] [Bug 104926] swrast: Mesa 17.3.3 produces: HW cursor for format 875713089 not supported

2018-07-17 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=104926

--- Comment #6 from Stefan Dirsch  ---
Hmm. Fix is not yet in git master. :-(

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


[Mesa-dev] [Bug 104926] swrast: Mesa 17.3.3 produces: HW cursor for format 875713089 not supported

2018-04-13 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=104926

Timothy Arceri  changed:

   What|Removed |Added

  Component|Other   |Drivers/Gallium/llvmpipe

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


[Mesa-dev] [Bug 104926] swrast: Mesa 17.3.3 produces: HW cursor for format 875713089 not supported

2018-03-16 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=104926

--- Comment #5 from Wayne Blaszczyk  ---
The above patch has fixed the issue for me.

Thanks!

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


[Mesa-dev] [Bug 104926] swrast: Mesa 17.3.3 produces: HW cursor for format 875713089 not supported

2018-03-16 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=104926

--- Comment #4 from Stefan Dirsch  ---
https://lists.freedesktop.org/archives/mesa-dev/2018-March/189030.html

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


[Mesa-dev] [Bug 104926] swrast: Mesa 17.3.3 produces: HW cursor for format 875713089 not supported

2018-03-15 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=104926

--- Comment #3 from Michal Srb  ---
I was able to reproduce the `gbm_device_is_format_supported` failure. The call
sequence is following:

* gbm_device_is_format_supported
* gbm_dri_is_format_supported (gbm->is_format_supported)
  - `dri->image->base.version` is now 17 (this changed in the bisected commit
 e14fe41e0!) and `dri->image->queryDmaBufModifiers` is set, so it will be
 called.
* dri2_query_dma_buf_modifiers (dri->image->queryDmaBufModifiers)
  - oh no, `pscreen->query_dmabuf_modifiers` is 0, so return false...

The situation depends on whether the screen was initialized with
`dri2_init_screen` or with `dri_kms_init_screen`. In case of `dri2_init_screen`
the `dri->image->queryDmaBufModifiers` is not set if
`pscreen->query_dmabuf_modifiers` is null. In case of `dri_kms_init_screen` it
is set unconditionally.

The condition was added to `dri2_init_screen` in commit a65db0ad1c3. I think
that equivalent condition is needed in `dri_kms_init_screen`. Will send
patch...

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


[Mesa-dev] [Bug 104926] swrast: Mesa 17.3.3 produces: HW cursor for format 875713089 not supported

2018-03-15 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=104926

Frederic Crozat  changed:

   What|Removed |Added

 CC||f...@crozat.net

--- Comment #2 from Frederic Crozat  ---
Problem is still present with Mesa 18.0-rc4

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


[Mesa-dev] [Bug 104926] swrast: Mesa 17.3.3 produces: HW cursor for format 875713089 not supported

2018-03-04 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=104926

--- Comment #1 from pipep  ---
Same problem here with Gnome 3.2.6 under Virtualbox and Mesa 17.3.6.

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


[Mesa-dev] [Bug 104926] swrast: Mesa 17.3.3 produces: HW cursor for format 875713089 not supported

2018-02-04 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=104926

pipep  changed:

   What|Removed |Added

 CC||a...@gmx.ch

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


[Mesa-dev] [Bug 104926] swrast: Mesa 17.3.3 produces: HW cursor for format 875713089 not supported

2018-02-03 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=104926

Bug ID: 104926
   Summary: swrast: Mesa 17.3.3 produces:  HW cursor for format
875713089 not supported
   Product: Mesa
   Version: 17.3
  Hardware: Other
OS: All
Status: NEW
  Severity: normal
  Priority: medium
 Component: Other
  Assignee: mesa-dev@lists.freedesktop.org
  Reporter: wblas...@bigpond.net.au
QA Contact: mesa-dev@lists.freedesktop.org

Under a guest VM running Gnome 3.26.2 Wayland, the mouse cursor becomes laggy,
and a double cursor (both host and guest I presume) when Mesa 17.3.x is
installed including the latest, 17.3.3. Reverting back to 17.2.8 and the
problem goes away.
In the system logs the following can be found:

Feb 03 22:03:19 lfs13 org.gnome.Shell.desktop[651]: Window manager warning: HW
cursor for format 875713089 not supported

I've done a git bisect: 
e14fe41e0bf5d82c0b22eda2f8dcea058ac6e610 is the first bad commit

Tracking it even further, it seems to be related to __DRI_IMAGE being changed
from 15 to 17 in src/gallium/state_trackers/dri/dri2.c .

More info:

GL_RENDERER: llvmpipe (LLVM 5.0, 256 bits)
kms_swrast_dri.so

I wrote a simple test program, and the following function returns false under
17.3.3, and returns true under 17.2.8.

gbm_device_is_format_supported (gbm, gbm_format, GBM_BO_USE_CURSOR |
GBM_BO_USE_WRITE)

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