Bug#1029731: libglapi-mesa: Apps fail with 'DRM_IOCTL_MODE_CREATE_DUMB failed: Cannot allocate memory' after upgrade from 22.3.2-1 to 22.3.3-1
Hi All, Just a note that it looks like this patch got picked up in the 22.3.6 release that just went out. On Thu, 23 Feb 2023 at 06:03, Diederik de Haas wrote: > Control: tag -1 upstream fixed-upstream patch > > On Tue, 31 Jan 2023 01:19:54 +0300 Andrey Skvortsov > wrote: > > Here is link to created upstream issue. > > https://gitlab.freedesktop.org/mesa/mesa/-/issues/8198 > > In https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/21330 this > issue > got fixed upstream and I've attached the patch/diff to this message. > > When adding it to debian/patches and adding it to debian/patches/series > and > running `debian/rules patch`, it applies cleanly (which is not the case > for > all of them): > > ``` > me@laptop:~/dev/debian/salsa/xorg-team/lib/mesa$ debian/rules patch > dh patch --with quilt \ > --builddirectory=build/ \ > --buildsystem=meson >dh_quilt_patch -O--builddirectory=build/ -O--buildsystem=meson > Applying patch 07_gallium-fix-build-failure-on-powerpcspe.diff > patching file src/gallium/include/pipe/p_config.h > > Applying patch path_max.diff > patching file src/util/tests/cache_test.cpp > Hunk #1 succeeded at 82 (offset 1 line). > patching file src/util/tests/process_test.c > patching file src/gallium/auxiliary/pipe-loader/pipe_loader.c > Hunk #1 succeeded at 42 (offset -1 lines). > > Applying patch src_glx_dri_common.h.diff > patching file src/glx/dri_common.h > Hunk #1 succeeded at 57 (offset 2 lines). > > Applying patch bug102973-lima.diff > patching file src/gallium/drivers/lima/lima_resource.c > > Now at patch bug102973-lima.diff > ``` > > HTH -- Stuart Young (aka Cefiar)
Bug#1017499: mesa: Updates to 22.2 RCs cause artifacts on nouveau and blank screen on VirtIO
There's been no new RC release from Mesa since rc3, which was 4 weeks ago. I think they're overdue for one. On Fri, 16 Sept 2022 at 02:03, Leandro Cunha wrote: > Hi, > > Yes, I reported it to upstream and it's an issue that went undetected > until I take action like this. And the upload (I don't know if it was > accidental) to an unstable version of rc (release candidate) helped to > discover that there were issues that needed attention. Thanks to Karol > who took the necessary attention to solve the problem. And fixed > upstream and upstream tags are already added. Upload only for pending > fix now. I have no information if a new version of rc has been > released. > > -- > Cheers, > Leandro Cunha > > -- Stuart Young (aka Cefiar)
Bug#972736: Mesa 20.2.1 fails to build on x32 (debian\rules issue)
Hi Mesa Maintainers, The patch attached to this bug has been tested on multiple platforms, and resolves the issue for x32 builds. Any chance we get this applied to the next release please? Note: As this is a rules issue, it will also apply to Mesa 20.3.* and beyond as well. On Tue, 3 Nov 2020 at 15:50, Stuart Young wrote: > Patch for debian/rules attached to resolve this bug. > > Note: By just checking if the variable is empty first, the patch is > non-specific to x32. It covers the x32 build issue, but will also avoid > such issues for any platform that AMD vulkan drivers aren't built on, but > that can support intel vulkan drivers. > > -- > Stuart Young (aka Cefiar) > -- Stuart Young (aka Cefiar)
Bug#973675: mesa: Fix warnings for deprecated options
Package: mesa
Version: 20.2.1-1
Attached is a patch that fixes a bunch of warnings about
deprecated commands along the lines of:
option "true" deprecated, please use "enabled" instead.
option "false" deprecated, please use "disabled" instead.
Suspect that these changes will become mandatory in the future, so best to
get the warnings sorted now.
Tested build on amd64.
Note: Doesn't seem to affect all options that take true/false, or at least
the ones that affect amd64.
--
Stuart Young (aka Cefiar)
--- a/debian/rules 2020-11-03 06:03:30.0 +
+++ b/debian/rules 2020-11-03 06:01:29.350023534 +
@@ -34,7 +34,7 @@
GALLIUM_DRIVERS =
VULKAN_DRIVERS =
-confflags_DRI3 = -Ddri3=false
+confflags_DRI3 = -Ddri3=disabled
# hurd doesn't do direct rendering
ifeq ($(DEB_HOST_ARCH_OS), hurd)
@@ -42,7 +42,7 @@
EGL_PLATFORMS = x11
confflags_DIRECT_RENDERING = -Dglx-direct=false
- confflags_GBM = -Dgbm=false
+ confflags_GBM = -Dgbm=disabled
confflags_OSMESA = -Dosmesa=classic
else
DRI_DRIVERS += r200,r100
@@ -56,7 +56,7 @@
endif
ifeq ($(DEB_HOST_ARCH_OS), linux)
- confflags_DRI3 = -Ddri3=true
+ confflags_DRI3 = -Ddri3=enabled
DRI_DRIVERS += ,nouveau
# Gallium drivers which require kernel support, not yet ported to non-Linux
GALLIUM_DRIVERS += ,nouveau,virgl
@@ -74,7 +74,7 @@
ifneq (,$(filter $(DEB_HOST_ARCH), amd64 i386 x32))
GALLIUM_DRIVERS += ,svga,zink
# svga needs xa state tracker
- confflags_GALLIUM += -Dgallium-xa=true
+ confflags_GALLIUM += -Dgallium-xa=enabled
VULKAN_DRIVERS += ,intel
endif
@@ -82,7 +82,7 @@
EGL_PLATFORMS += ,wayland
ifneq (,$(filter $(DEB_HOST_ARCH), amd64 arm64 armhf i386 mips64el mipsel powerpc ppc64 ppc64el s390x))
- confflags_VALGRIND += -Dvalgrind=true
+ confflags_VALGRIND += -Dvalgrind=enabled
endif
endif
@@ -96,7 +96,7 @@
# It's also required for building OpenCL support.
ifneq (,$(filter $(DEB_HOST_ARCH), amd64 arm64 armel armhf i386 kfreebsd-amd64 kfreebsd-i386 mips64el mipsel powerpc ppc64 ppc64el s390x sparc64))
GALLIUM_DRIVERS += ,radeonsi,swrast
- confflags_GALLIUM += -Dllvm=true
+ confflags_GALLIUM += -Dllvm=enabled
confflags_GALLIUM += -Dgallium-opencl=icd
confflags_OSMESA = -Dosmesa=gallium
@@ -106,7 +106,7 @@
endif
else
DRI_DRIVERS += ,swrast
- confflags_GALLIUM += -Dllvm=false
+ confflags_GALLIUM += -Dllvm=disabled
confflags_OSMESA = -Dosmesa=classic
endif
@@ -117,18 +117,18 @@
endif
confflags_DIRECT_RENDERING = -Dglx-direct=true
- confflags_GBM = -Dgbm=true
+ confflags_GBM = -Dgbm=enabled
confflags_GALLIUM += -Dgallium-extra-hud=true
- confflags_GALLIUM += -Dgallium-vdpau=true
- confflags_GALLIUM += -Dlmsensors=true
+ confflags_GALLIUM += -Dgallium-vdpau=enabled
+ confflags_GALLIUM += -Dlmsensors=enabled
ifeq (,$(filter pkg.mesa.nolibva,$(DEB_BUILD_PROFILES)))
-confflags_GALLIUM += -Dgallium-va=true
+confflags_GALLIUM += -Dgallium-va=enabled
endif
endif
confflags_EGL = -Dplatforms="$(EGL_PLATFORMS)"
-confflags_GLES = -Dgles1=false -Dgles2=true
+confflags_GLES = -Dgles1=disabled -Dgles2=enabled
confflags_GALLIUM += -Dgallium-drivers="$(GALLIUM_DRIVERS)"
confflags += \
@@ -137,8 +137,8 @@
-Ddri-search-path='/usr/lib/$(DEB_HOST_MULTIARCH)/dri:\{ORIGIN}/dri:/usr/lib/dri' \
-Dvulkan-drivers="$(VULKAN_DRIVERS)" \
-Dglvnd=true \
- -Dshared-glapi=true \
- -Dgallium-xvmc=false \
+ -Dshared-glapi=enabled \
+ -Dgallium-xvmc=disabled \
-Dgallium-omx=disabled \
-Db_ndebug=true \
-Dbuild-tests=true \
Bug#972736: Mesa 20.2.1 fails to build on x32 (debian\rules issue)
Patch for debian/rules attached to resolve this bug. Note: By just checking if the variable is empty first, the patch is non-specific to x32. It covers the x32 build issue, but will also avoid such issues for any platform that AMD vulkan drivers aren't built on, but that can support intel vulkan drivers. -- Stuart Young (aka Cefiar) --- a/debian/rules 2020-11-03 15:11:24.262177791 +1100 +++ b/debian/rules 2020-11-03 15:20:36.960909848 +1100 @@ -75,7 +75,12 @@ GALLIUM_DRIVERS += ,svga,zink # svga needs xa state tracker confflags_GALLIUM += -Dgallium-xa=true - VULKAN_DRIVERS += ,intel + # VULKAN_DRIVERS var may be empty + ifeq ($(strip $(VULKAN_DRIVERS)),) + VULKAN_DRIVERS = intel + else + VULKAN_DRIVERS += ,intel + endif endif # Non-Linux ports also lack *_CLOEXEC and epoll, so wayland isn't ready yet:
Bug#973673: Mesa FTBFS due to build dep on hurd
Package: mesa
Version: 20.2.1-1
Since forever (ie: the 9 yrs of salsa history I could go back through with
git blame), libdrm-dev has been marked not to be a build dep on hurd for
mesa.
eg: From debian/control in 20.2.1-1:
libdrm-dev (>= 2.4.101) [!hurd-any]
Changes to upstream mesa's surfaceless EGL now basically require libdrm-dev.
>From meson.build in 20.2.1 @ lines 337 -> 343:
if _platforms.contains('surfaceless') warning('Platform `surfaceless`
is now always selected; setting this option will be an error in Mesa
20.3')endifif _platforms.contains('drm') warning('Platform `drm` is
now automatically selected; setting this option will be an error in
Mesa 20.3')endif
FWIW: Looks like these changes were made upstream about 3 months ago.
Relaxing the restriction on libdrm-dev actually allows the package to
build, and libdrm is being built already on hurd.
Another way I that may work would be to disable EGL in debian/rules, but
not sure if that's a suitable option?
Note: I can't actually test anything further though as I can't currently
get either mesa 18.3.6 or 20.2.1 to work with qemu passthru on my machine.
--
Stuart Young (aka Cefiar)
Bug#972736: Mesa 20.2.1 fails to build on x32 (debian\rules issue)
Package: mesa
Version: 20.2.1-1
In debian\rules, there is the following at lines 74-79:
ifneq (,$(filter $(DEB_HOST_ARCH), amd64 i386 x32)) GALLIUM_DRIVERS +=
,svga,zink # svga needs xa state tracker confflags_GALLIUM +=
-Dgallium-xa=true VULKAN_DRIVERS += ,intel endif
When this is parsed on x32, the value of VULKAN_DRIVERS is blank. This puts
a , at the start of the variable, which breaks the build using meson.
This works on other platforms as earlier the AMD driver is added (see lines
54-56).
>From the buildd logs, the CFLAGS passed are:
CFLAGS="-g -O2 -fdebug-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -Wall"
CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" CXXFLAGS="-g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong
-Wformat -Werror=format-security -Wall" FCFLAGS="-g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong"
FFLAGS="-g -O2 -fdebug-prefix-map=/<>=.
-fstack-protector-strong" GCJFLAGS="-g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong"
LDFLAGS="-Wl,-z,relro" OBJCFLAGS="-g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong
-Wformat -Werror=format-security" OBJCXXFLAGS="-g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong
-Wformat -Werror=format-security" dh_auto_configure -- \
-Ddri-drivers="r200,r100 ,nouveau ,i915, i965 ,swrast"
-Ddri-drivers-path=/usr/lib/x86_64-linux-gnux32/dri
-Ddri-search-path='/usr/lib/x86_64-linux-gnux32/dri:\$${ORIGIN}/dri:/usr/lib/dri'
-Dvulkan-drivers=",intel" -Dglvnd=true -Dshared-glapi=true
-Dgallium-xvmc=false -Dgallium-omx=disabled -Db_ndebug=true
-Dbuild-tests=true -Dglx-direct=true -Dgbm=true -Ddri3=true
-Dplatforms="drm,surfaceless,x11 ,wayland" -Dgallium-xa=true
-Dllvm=false -Dgallium-extra-hud=true -Dgallium-vdpau=true
-Dlmsensors=true -Dgallium-va=true -Dgallium-drivers="r600,r300
,nouveau,virgl ,svga,zink ,iris" -Dgles1=false -Dgles2=true
-Dosmesa=classic -Dvulkan-device-select-layer=true
-Dvulkan-overlay-layer=true
cd build && LC_ALL=C.UTF-8 meson .. --wrap-mode=nodownload
--buildtype=plain --prefix=/usr --sysconfdir=/etc --localstatedir=/var
--libdir=lib/x86_64-linux-gnux32 "-Ddri-drivers=r200,r100 ,nouveau
,i915, i965 ,swrast"
-Ddri-drivers-path=/usr/lib/x86_64-linux-gnux32/dri
-Ddri-search-path=/usr/lib/x86_64-linux-gnux32/dri:\\\$\${ORIGIN}/dri:/usr/lib/dri
-Dvulkan-drivers=,intel -Dglvnd=true -Dshared-glapi=true
-Dgallium-xvmc=false -Dgallium-omx=disabled -Db_ndebug=true
-Dbuild-tests=true -Dglx-direct=true -Dgbm=true -Ddri3=true
"-Dplatforms=drm,surfaceless,x11 ,wayland" -Dgallium-xa=true
-Dllvm=false -Dgallium-extra-hud=true -Dgallium-vdpau=true
-Dlmsensors=true -Dgallium-va=true "-Dgallium-drivers=r600,r300
,nouveau,virgl ,svga,zink ,iris" -Dgles1=false -Dgles2=true
-Dosmesa=classic -Dvulkan-device-select-layer=true
-Dvulkan-overlay-layer=true
Notably from that:
-Dvulkan-drivers=",intel"
Suggest that lines 74-79 need to be modified to check if the VULKAN_DRIVERS
variable already has some value set or not, or treat x32 as a special case,
before adding ",intel" or "intel" to the VULKAN_DRIVERS variable as
appropriate.
Note: I don't have an x32 build env. I just saw the failed buildd logs via
the debian Mesa tracker.
--
Stuart Young (aka Cefiar)
Bug#969040: mesa: [hurd] FTBFS on hurd due to PATH_MAX
If you are going to package mesa 20.1.10, would you consider applying this patch? -- Stuart Young (aka Cefiar)
Bug#908827: mesa: Fails to build on Stretch, missing min build dep
Commit has made it into the queue for 18.2.2. On Thu, 27 Sep 2018 at 18:12, Stuart Young wrote: > This was an upstream issue due to new work in the vulkan driver that uses > newer libxcb functions (only in 1.13+). > > For Mesa 18.2.1, the following upstream commit resolves the build issue: > dd333c66bdcb11c0d7c5 "vulkan: Disable randr lease for libxcb < 1.13" > > Hopefully this should make it into Mesa 18.2.2 shortly. > > -- > Stuart Young (aka Cefiar) > -- Stuart Young (aka Cefiar)
Bug#908827: mesa: Fails to build on Stretch, missing min build dep
This was an upstream issue due to new work in the vulkan driver that uses newer libxcb functions (only in 1.13+). For Mesa 18.2.1, the following upstream commit resolves the build issue: dd333c66bdcb11c0d7c5 "vulkan: Disable randr lease for libxcb < 1.13" Hopefully this should make it into Mesa 18.2.2 shortly. -- Stuart Young (aka Cefiar)
Bug#896447: mesa: Lintian wishlist: Add notes to glvnd-fix-gl-dot-pc.patch
Seems like this upstream commit may negate the need for this patch: https://cgit.freedesktop.org/mesa/mesa/commit/?id=d5ac23647110fd530f9bf5002762587be446866d Has been also tagged for the stable queue, so may affect 18.1.6+, as well as 18.2.x. Note: Completely untested by me. On Sat, 2 Jun 2018 at 13:02, Stuart Young wrote: > Update: Fix still not present in mesa 18.1.1, so the original patch is > still required. > > On 30 May 2018 at 17:51, Stuart Young wrote: > >> Seems that the source issue of this patch is going to be addressed >> upstream. This should mean that once it's addressed, the original >> glvnd-fix-gl-dot-pc.patch file can be dropped entirely from the >> debian/patches/ tree of this package. >> >> References: >> https://lists.freedesktop.org/archives/mesa-dev/2018-May/196034.html >> https://lists.freedesktop.org/archives/mesa-dev/2018-May/196038.html >> >> Note: Nothing has been accepted upstream yet. May or may not happen >> before 18.1.1 is released. Will update this bug if I can when this patch is >> no longer needed. >> >> -- >> Stuart Young (aka Cefiar) >> > > > > -- > Stuart Young (aka Cefiar) > -- Stuart Young (aka Cefiar)
Bug#901789: mesa: white screen when running Xfwm4 with compositing
Hi All, Can any of you try the fix for Bug 901497 ? This could be an Xwayland issue that until recently was hard to trigger. Alternatively try using the X.org X server rather than the Wayland one to see if that helps. On Sat, 23 Jun. 2018, 02:33 Margot Berg, wrote: > Hello Yves-Alexis, > > the same error on my debian sid with xfce 4.13 - gtk3, kernel 4.17.2, > intel kabylake. > It is experimental and not stable, therefore I have no hope, that this > error will be corrected. > I am using apt-pinning on version 18.0.5-1. > > best regards > MB >
Bug#901533: mesa: please build
Hi Laurent, I submitted a bug upstream about the source for this tool not being included in the upstream tarball in the first place. https://bugs.freedesktop.org/show_bug.cgi?id=106778 This was due to the fact that when it was added to Mesa, it wasn't included in the Autotools build system, only the meson build system. All the tarballs are made using Autotools (even upstream). Unfortunately this patch didn't make it into Mesa 18.1.1. Also, the fix provided upstream has been to simply add the files to EXTRA_DIST, which means they'll make it into the tarball, but they're not compiled by Autotools. I would suggest logging a bug upstream against this to have the necessary tool built by Autotools, as the Debian builds use Autotools as far as I know. Feel free to reference my bug. In the meantime, if you need this tool for debugging, I would suggest you grab the Debian source using `apt-get source` and try building it yourself. Note: Every time I've tried to add meson/ninja to my system to do a build, it wanted to remove all the Debian build helper tools, which doesn't help any. PS: Mesa 18.1.2 upstream is due for release today (15th June), so I would not expect to see any changes in this behaviour till Mesa 18.1.3 at the earliest (29th June). This is based on the release calendar currently at https://mesa.freedesktop.org/release-calendar.html On Fri, 15 Jun 2018 at 00:21, Laurent Bonnaud wrote: > Source: mesa > Severity: wishlist > > > Dear Maintainer, > > the Mesa source package contains this file: > > ./mesa-18.1.1/src/intel/tools/intel_sanitize_gpu.c > > but it is not built during the Debian binary packages creation. Could you > please build it? > > It would be very helpful to debug Mesa issues, such as: > > https://bugs.freedesktop.org/show_bug.cgi?id=106859 > > > -- System Information: > Debian Release: buster/sid > APT prefers unstable-debug > APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, > 'experimental-debug'), (1, 'experimental') > Architecture: amd64 (x86_64) > > Kernel: Linux 4.16.0-2-rt-amd64 (SMP w/2 CPU cores; PREEMPT) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), > LANGUAGE=en_US.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > -- > Laurent. > > -- Stuart Young (aka Cefiar)
Bug#901497: Hard system hangs after upgrade from 18.0.5-1 to 18.1.1-1
Which specific versions of Firefox are you using? Are you using FlashPlayer with Firefox at all, and if so, which version? On Thu, 14 Jun 2018 at 20:24, Tehnic wrote: > Exactly the same problem here with this URL: > > https://www.golem.de/news/spionagevorwurf-eu-parlament-will-kaspersky-l > oswerden-1806-134949.html > <https://www.golem.de/news/spionagevorwurf-eu-parlament-will-kaspersky-loswerden-1806-134949.html> > > I can reproduce the effect with Firefox and Firefox ESR. Chromium is > not affected by this. > > I not downgraded until now so if you need more information please > contact me. > > Regards, Robert > > -- > Tehnic > > -- Stuart Young (aka Cefiar)
Bug#896447: mesa: Lintian wishlist: Add notes to glvnd-fix-gl-dot-pc.patch
Update: Fix still not present in mesa 18.1.1, so the original patch is still required. On 30 May 2018 at 17:51, Stuart Young wrote: > Seems that the source issue of this patch is going to be addressed > upstream. This should mean that once it's addressed, the original > glvnd-fix-gl-dot-pc.patch file can be dropped entirely from the > debian/patches/ tree of this package. > > References: > https://lists.freedesktop.org/archives/mesa-dev/2018-May/196034.html > https://lists.freedesktop.org/archives/mesa-dev/2018-May/196038.html > > Note: Nothing has been accepted upstream yet. May or may not happen before > 18.1.1 is released. Will update this bug if I can when this patch is no > longer needed. > > -- > Stuart Young (aka Cefiar) > -- Stuart Young (aka Cefiar)
Bug#896447: mesa: Lintian wishlist: Add notes to glvnd-fix-gl-dot-pc.patch
Seems that the source issue of this patch is going to be addressed upstream. This should mean that once it's addressed, the original glvnd-fix-gl-dot-pc.patch file can be dropped entirely from the debian/patches/ tree of this package. References: https://lists.freedesktop.org/archives/mesa-dev/2018-May/196034.html https://lists.freedesktop.org/archives/mesa-dev/2018-May/196038.html Note: Nothing has been accepted upstream yet. May or may not happen before 18.1.1 is released. Will update this bug if I can when this patch is no longer needed. -- Stuart Young (aka Cefiar)
Bug#898620: libglu: Update VCS links in debian/control
Realised I got the files around the wrong way in the patch. While it'll probably apply, it'd be better to get it right. Correct patch attached. On 14 May 2018 at 20:51, Stuart Young <cef...@gmail.com> wrote: > Source: libglu > Severity: normal > Tags: patch > > Dear Maintainer, > > The current Vcs tags in debian/control still refer to git.debian.org > > Attached is a patch to update them to point to the source at > salsa.debian.org > -- Stuart Young (aka Cefiar) --- libglu/debian/control.orig 2018-05-14 20:43:11.553964761 +1000 +++ libglu/debian/control 2018-05-14 20:44:04.912681221 +1000 @@ -9,8 +9,8 @@ dh-autoreconf, pkg-config, libgl1-mesa-dev, -Vcs-Git: git://git.debian.org/git/pkg-xorg/lib/libglu -Vcs-Browser: http://git.debian.org/?p=pkg-xorg/lib/libglu.git +Vcs-Git: https://salsa.debian.org/xorg-team/lib/libglu.git +Vcs-Browser: https://salsa.debian.org/xorg-team/lib/libglu Package: libglu1-mesa Section: libs
Bug#898620: libglu: Update VCS links in debian/control
Source: libglu Severity: normal Tags: patch Dear Maintainer, The current Vcs tags in debian/control still refer to git.debian.org Attached is a patch to update them to point to the source at salsa.debian.org --- libglu/debian/control 2018-05-14 20:44:04.912681221 +1000 +++ libglu/debian/control.orig 2018-05-14 20:43:11.553964761 +1000 @@ -9,8 +9,8 @@ dh-autoreconf, pkg-config, libgl1-mesa-dev, -Vcs-Git: https://salsa.debian.org/xorg-team/lib/libglu.git -Vcs-Browser: https://salsa.debian.org/xorg-team/lib/libglu +Vcs-Git: git://git.debian.org/git/pkg-xorg/lib/libglu +Vcs-Browser: http://git.debian.org/?p=pkg-xorg/lib/libglu.git Package: libglu1-mesa Section: libs
Bug#898257: libclc-r600: unable to compile any kernels for Radeon HD 5770
Upstream patch (2 parts) that may be related (untested): http://lists.llvm.org/pipermail/libclc-dev/2018-March/002851.html Might be worth cherry-picking this patch to see if it helps, or simply picking up latest upstream git. On 9 May 2018 at 20:00, 10dmar10 <10dma...@gmail.com> wrote: > Package: libclc-r600 > Version: 0.2.0+git20180312-2 > Severity: normal > > Hi, > > after recent upgrading I wasn't able to run any OpenCL application anymore. > > Any attempt to compile an OpenCL kernel fails with following error: > fatal error: cannot open file '/usr/lib/clc/juniper-r600--.bc': Invalid > record > > > file /usr/lib/clc/juniper-r600--.bc > /usr/lib/clc/juniper-r600--.bc: symbolic link to cedar-r600--.bc > > file /usr/lib/clc/cedar-r600--.bc > /usr/lib/clc/cedar-r600--.bc: LLVM IR bitcode > > Hardware: > 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] > Juniper XT [Radeon HD 5770] > > clinfo output (other OpenCL programms fail with same error): > > Number of platforms 1 > Platform Name Clover > Platform Vendor Mesa > Platform VersionOpenCL 1.1 Mesa 17.3.9 > Platform ProfileFULL_PROFILE > Platform Extensions cl_khr_icd > Platform Extensions function suffix MESA > > Platform Name Clover > Number of devices 1 > Device Name AMD JUNIPER (DRM 2.50.0 > / 4.16.6, LLVM 5.0.1) > Device Vendor AMD > Device Vendor ID0x1002 > Device Version OpenCL 1.1 Mesa 17.3.9 > Driver Version 17.3.9 > Device OpenCL C Version OpenCL C 1.1 > Device Type GPU > Device Profile FULL_PROFILE > Device AvailableYes > Compiler Available Yes > Max compute units 10 > Max clock frequency 850MHz > Max work item dimensions3 > Max work item sizes 256x256x256 > Max work group size 256 > === CL_PROGRAM_BUILD_LOG === > fatal error: cannot open file '/usr/lib/clc/juniper-r600--.bc': Invalid > record > Preferred work group size multiple program : error -11> > Preferred / native vector sizes > char16 / 16 > short8 / 8 > int 4 / 4 > long 2 / 2 > half 0 / 0(n/a) > float4 / 4 > double 0 / 0(n/a) > > ** REST OMITTED *** > > > > > -- System Information: > Debian Release: buster/sid > APT prefers testing > APT policy: (990, 'testing') > Architecture: amd64 (x86_64) > > Kernel: Linux 4.16.6 (SMP w/3 CPU cores) > Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), > LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages libclc-r600 depends on: > ii libclang-common-6.0-dev 1:6.0-3 > ii libclc-dev 0.2.0+git20180312-2 > > libclc-r600 recommends no packages. > > libclc-r600 suggests no packages. > > -- no debconf information > > -- Stuart Young (aka Cefiar)
Bug#898021: linux-image-4.16.0-1-amd64: kernel 4.16 infinite wait after dm login on ivy bridge and bay trail
My workarounds for this at the moment are to install tools that increase the kernel entropy pool. If not a virtual machine, and `grep -i -o -m 1 rdrand /proc/cpuinfo` returns 'rdrand', then I install the 'rng-tools5' package which uses the hardware rng in many cpu's to provide entropy to the kernel. If that fails or if it's a virtual machine, then I install the 'haveged' package. Note: Neither of these are fixes. They're work-arounds for the current issue that allow somewhat normal operation. eg; Some people have issues around how random the hardware rng is in some machines. PS: Have seen a number of people suffering this issue in #debian on freenode, and also on #debian & #debian-next on oftc. On 10 May 2018 at 15:43, <chris...@trash-mail.com> wrote: > > > I can reproduce the described delay behavior on a virtualized installation > of testing using kvm after installing kernel 4.16.0-1-amd64. With > 4.15.0-3-amd64 no problem. > > Chris > > > -- Stuart Young (aka Cefiar)
Bug#898021: linux-image-4.16.0-1-amd64: kernel 4.16 infinite wait after dm login on ivy bridge and bay trail
I'm seeing this on a few laptops with SSD's. The behaviour is that if the device isn't interacted with in any way, the machines hang for 2-4 mins at boot. Seems to be related to the fix for CVE-2018-1108 - random: fix crng_ready() test https://security-tracker.debian.org/tracker/CVE-2018-1108 Pedro & Sten, can you try introducing entropy into the systems affected when they appear to hang, to see if this reduces the delays? eg: moving the mouse, tapping shift/ctrl/alt keys, pinging the device on the network if network is already up, etc? I suspect this bug can be merged with 897599, 897632 and 897917. -- Stuart Young (aka Cefiar)
Bug#896447: mesa: Lintian wishlist: Add notes to glvnd-fix-gl-dot-pc.patch
Source: mesa Severity: wishlist Tags: patch Dear Maintainer, Attached patch provides notes for the glvnd build patch shipped with Debian. Note: I have not tried compiling without glvnd-fix-gl-dot-pc.patch so I have no idea if this patch is even needed anymore, but having some provenance info listed in the actual patch may help determine that at some future time. --- debian/patches/glvnd-fix-gl-dot-pc.patch.orig 2018-04-21 16:40:41.045683013 +1000 +++ debian/patches/glvnd-fix-gl-dot-pc.patch2018-04-21 17:27:00.755255524 +1000 @@ -1,3 +1,13 @@ +Patch which seems originate from Redhat/Fedora to not use the variable library +name in pkg-config input. Appears to be required for building with glvnd +support. + +First appears in Fedora at: + https://src.fedoraproject.org/rpms/mesa/c/0e83570d6c2560dc879061c9a50b3526a96c4bcf?branch=master + +Appears to be a revert of upstream commit: + https://cgit.freedesktop.org/mesa/mesa/commit/src/mesa/gl.pc.in?id=a9c97c5f2a9b880d01336a23134600e4b34429d0 + diff -up mesa-12.0.3/src/mesa/gl.pc.in.jx mesa-12.0.3/src/mesa/gl.pc.in --- mesa-12.0.3/src/mesa/gl.pc.in.jx 2016-01-18 02:39:26.0 -0500 +++ mesa-12.0.3/src/mesa/gl.pc.in 2016-10-25 13:06:44.013159358 -0400
Bug#896146: mesa: Update control file to point at salsa
Source: mesa Severity: minor Tags: patch Dear Maintainer, Attached is a patch that updates the Vcs-Git and Vcs-Browser fields in debian/control to point at salsa rather than anonscm. This fixes current lintian warnings on these entries. Note: Patch should apply as is directly to both 17.3.9 (unstable) and 18.0.1 (experimental) branches. --- debian/control.orig 2018-04-20 17:59:50.724171710 +1000 +++ debian/control 2018-04-20 18:00:33.935088336 +1000 @@ -48,8 +48,8 @@ wayland-protocols (>= 1.9), zlib1g-dev, libglvnd-core-dev, -Vcs-Git: https://anonscm.debian.org/git/pkg-xorg/lib/mesa.git -Vcs-Browser: https://anonscm.debian.org/cgit/pkg-xorg/lib/mesa.git +Vcs-Git: https://salsa.debian.org/xorg-team/lib/mesa.git +Vcs-Browser: https://salsa.debian.org/xorg-team/lib/mesa Homepage: https://mesa3d.org/ Package: libxatracker2
Bug#260833: cyrus21-imapd: Cyrus Mailbox creation script
Package: cyrus21-imapd Followup-For: Bug #260833 I realise that no one upstream wants the autocreate patch, and that it's unlikely to be included in Debian either. So after a little bit of research, I decided to work my way around the problem by writing a script that pulls all the users out of LDAP and creates them in Cyrus for you. The script attached is designed to be able to run from cron if necessary. It can also report users who are in LDAP but not Cyrus (and vice versa). More info in the comments of the script itself (including the Debian perl libs required). Feel free to include this in the contribs directory for cyrus-* if you wish. I'm still working on this script, so it's not very (internally) pretty. I may even decide to add support for DBI sources down the track, but patches are always welcome. syncldap2cyrus.pl Description: Perl program
Bug#293265: (no subject)
My bad. I forgot to check the 'Use a proxy server' for the server entry in question. So this bug doesn't actually exist. Please close. However, it might be worth adding a little note in the screen where you configure the proxy that the proxy won't be used unless the 'Use a proxy server' box is ticked in the server entry. -- Stuart Young (aka Cef) [EMAIL PROTECTED] is for Debian and related email only -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#293266: reportbug: SMTP/Mail Server failure handling
Package: reportbug Version: 3.7.1 Severity: normal Perhaps this should really be wishlist, but it's annoying none the less. If you configure an smtphost for reportbug, and for some reason, the smtphost is uncontactable, reportbug exits with an error (fortunately after saving a copy of the bug in /tmp). I believe it does the same if sendmail fails to exit cleanly, so the same method described below would be useful all round. It would be really nice if reportbug actually provided the user with a simple prompt to either: Fail does as it currently does Retry tries sending again as already configured re-read Configs then retry eg: for switching from smtphost to sendmail, or changing the smtphost IMHO, this would remind me that I haven't got the smtp tunnel to the mail server running so that I could start it and juts hit Retry. *grin* -- Package-specific info: -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.9-1-686 Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1) Versions of packages reportbug depends on: ii python2.32.3.4+2.3.5c1-1 An interactive high-level object-o -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
