@oibaf thanks, I reported it:
- https://gitlab.freedesktop.org/mesa/mesa/-/issues/1
(nice issue number by the way ☺️)
** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #1
https://gitlab.freedesktop.org/mesa/mesa/-/issues/1
--
You received this bug notification becaus
I reproduce the bug with current Mesa
(d97427f41c1603db2f657b5d9c3f91a97f74b1c0) and LLVM 16.0.6. I don't know
if the bug is on drm side or on Mesa side.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchp
I reproduce the same issue if I just do:
```
DRI_PRIME=1 glxinfo -B
name of display: :1
```
Which means the fault happens when using the AMD FirePro S7150, NOT the
AMD Radeon PRO W7600.
Maybe for some reasons Unigine Superposition tries to use all GPUs
available?
So, the bug is now easier to re
** Description changed:
When I run Unigine Superposition 1.1, it doesn't open any window and
dmesg is filled with:
```
[36881.961064] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.962579] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memo
In the log file you may see notice of some amdgpu-pro OpenCL components
like ROCm ROCr OpenCL or Legacy Orca OpenCL, there is no amdgpu-pro
OpenGL or dkms module installed though. Removing entirely the amdgpu-pro
OpenCL packages produce the same bug anyway. The contrary would have
been surprising s
Public bug reported:
When I run Unigine Superposition 1.1, it doesn't open any window and
dmesg is filled with:
```
[36881.961064] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.962579] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command
To be even more precise: you activated a countdown that would
automatically close this issue if no answer would be given to the only
question that was not answerable because of the very nature of this bug.
The Launchpad software is just obeying to human decisions, there.
--
You received this bug
I may update that sentence:
> You're just saying no one tried to reproduce the bug, this is
different.
You're just saying no one tried to reproduce the bug _and it was just
decided to let it expire with the distribution version itself_, this is
different.
Launchpad can't be taken responsible for
There was enough information to be actionable:
1. Get Ubuntu with the version the bug is reported for.
2. Apply the reproduction steps given in the very first message reporting the
bug:
```
killall nautilus
GTK_THEME=
nautilus
```
The bug was said to be a rendering bug, any human with functiona
This looks fixed in Ubuntu 23.04 and this was reported against Ubuntu 22.10.
So, now that Ubuntu 22.10 is not supported, this can be considered fixed.
That said, I don't understand why this bug was closed because “there has
been no activity for 60 days”.
The bug was still reproducible on Ubuntu 2
Public bug reported:
In Ubuntu 22.10, nautilus rendering is broken as soon as GTK_THEME
environment exists, and there are some other components of GNOME that
sets it at desktop launch (for example the Desktop may set it as
GTK_THEME=Adwaita:dark).
I have found no GTK_THEME value to make nautilus
Public bug reported:
This can be verified with any OpenCL application that actually tries to
compute something (clinfo may not be enough).
A very simple application to reproduce the bug is cl-mem:
```
git clone https://github.com/nerdralph/cl-mem.git
cd cl-mem
make
./cl-mem
OpenCL build failed
Public bug reported:
Context: the computer is running nvidia-340 to workaround suspend bug
happening when using nouveau.
Since more than a year, the system isn't bootable with the default boot
option because nvidia-340 can't be built against newer default kernels.
ProblemType: Package
DistroRele
Hi, I'm getting the exact same problem with my thumbnailer:
https://github.com/illwieckz/crunch-thumbnailer
After investigations using "G_MESSAGES_DEBUG=all" I discovered the
thumbnailer is called by nautilus this way:
bwrap --ro-bind /usr /usr --ro-bind /etc/ld.so.cache /etc/ld.so.cache
--ro-bin
Thanks littlelion for the workaround, it was broken here too (Thinkpad X61
Tablet) and the .rules file fixed it.
After upgrading from Trusty to Utopic, there was no
/lib/udev/rules.d/69-xserver-xorg-input-wacom.rules and no
/lib/udev/rules.d/69-wacom.rules/wacom.rules at all here.
--
You recei
15 matches
Mail list logo
