Bug#1066545: xserver-xorg-video-openchrome: FTBFS: ../../src/via_driver.c:1678:45: error: implicit declaration of function ‘shadowUpdatePackedWeak’; did you mean ‘shadowUpdatePacked’? [-Werror=implici

2025-04-26 Thread Alan Coopersmith
On Wed, 13 Mar 2024 12:58:50 +0100 Lucas Nussbaum wrote: Source: xserver-xorg-video-openchrome Version: 1:0.6.0-5 [...] ../../src/via_driver.c: In function ‘VIACreateScreenResources’: ../../src/via_driver.c:1678:45: error: implicit declaration of function ‘shadowUpdatePackedWeak’; did you

Bug#1040617: marked as done (Spelling error in the upstream web address and a new version)

2025-03-26 Thread Debian Bug Tracking System
Your message dated Wed, 26 Mar 2025 18:22:02 + with message-id and subject line Bug#1040617: fixed in xorg-docs 1:1.7.3-1 has caused the Debian Bug report #1040617, regarding Spelling error in the upstream web address and a new version to be marked as done. This means that you claim that the

Bug#1101290: marked as done (libxrender FTBFS: error: expected ';' before 'elt')

2025-03-25 Thread Debian Bug Tracking System
Your message dated Tue, 25 Mar 2025 13:04:31 + with message-id and subject line Bug#1101290: fixed in libxrender 1:0.9.12-1 has caused the Debian Bug report #1101290, regarding libxrender FTBFS: error: expected ';' before 'elt' to be marked as done. This means that you cl

Bug#1101290: libxrender FTBFS: error: expected ';' before 'elt'

2025-03-25 Thread Helmut Grohne
-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c ../../src/Glyph.c -fPIC -DPIC -o .libs/Glyph.o ../../src/Glyph.c: In function 'XRenderCompositeText8': ../../src/Glyph.c:481:13: error: expected ';' before 'elt' 481 |

Processed: Re: xserver-xorg-video-ivtvdev: FTBFS with GCC 14: error: assignment ... from incompatible pointer type ...

2025-03-01 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + patch Bug #1078229 [src:xserver-xorg-video-ivtvdev] xserver-xorg-video-ivtvdev: FTBFS with GCC 14: error: assignment ... from incompatible pointer type ... Added tag(s) patch. -- 1078229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078229 Deb

Bug#1078229: xserver-xorg-video-ivtvdev: FTBFS with GCC 14: error: assignment ... from incompatible pointer type ...

2025-03-01 Thread Petter Reinholdtsen
Control: tags -1 + patch The following patch should get the package building again: Description: Fix build problems with newer Xorg and compiler. Ensure correct method and variable declaration to avoid fatal compiler warnings. Author: Petter Reinholdtsen Forwarded: no Last-Update: 2025-03-01 -

Bug#1095270: lightdm: /usr/share/xsessions/lightdm-autologin.desktop error in exec statement

2025-02-07 Thread Yves-Alexis Perez
X-Debbugs-Cc: f...@axnet.nu > > dist-upgrading Feb 5 2025 using autologin with lightdm with the attached > config > in particular setting >   autologin-session=lightdm-autologin > in /etc/lightdm/lightdm.conf > > we get the following error: > >    Xsession: unable to l

Processed: Re: Bug#1095270: lightdm: /usr/share/xsessions/lightdm-autologin.desktop error in exec statement

2025-02-07 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 x11-common Bug #1095270 [lightdm] lightdm: /usr/share/xsessions/lightdm-autologin.desktop error in exec statement Bug reassigned from package 'lightdm' to 'x11-common'. No longer marked as found in versions lightdm/1.32.0-6. Ig

Processed: Re: Bug#1095270: lightdm: /usr/share/xsessions/lightdm-autologin.desktop error in exec statement

2025-02-07 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 x11-common Bug #1095270 [x11-common] lightdm: /usr/share/xsessions/lightdm-autologin.desktop error in exec statement Bug #1094494 [x11-common] xorg-common: 20x11-common_process-args: fails on xsession executable with args Ignoring request to reass

Processed (with 1 error): Re: Bug#1094023: Errors while running CTest of lomiri-system-settings_1.3.0-3

2025-01-24 Thread Debian Bug Tracking System
Processing control commands: > forcemerge #1092890 -1 Bug #1092890 [libglx-mesa0] mesa: regression in 24.3: software rendering crashes on ppc64el with segmentation fault Unable to merge bugs because: package of #1094023 is 'lomiri-system-settings' not 'libglx-mesa0' Failed to forcibly merge 10928

Bug#1087279: marked as done (xserver-xorg-video-vesa FTBFS: error: implicit declaration of function 'outb')

2025-01-24 Thread Debian Bug Tracking System
Your message dated Fri, 24 Jan 2025 09:23:50 + with message-id and subject line Bug#1087279: fixed in xserver-xorg-video-vesa 1:2.6.0-2 has caused the Debian Bug report #1087279, regarding xserver-xorg-video-vesa FTBFS: error: implicit declaration of function 'outb' to be mark

Bug#1066263: marked as done (xfonts-utils: FTBFS: ../fonttosfnt/util.c:89:10: error: implicit declaration of function ‘vasprintf’; did you mean ‘vsprintf’? [-Werror=implicit-function-declaration])

2025-01-23 Thread Debian Bug Tracking System
Your message dated Thu, 23 Jan 2025 18:50:34 +0100 with message-id <2507d119-da17-4651-bb82-9da239434...@debian.org> and subject line Re: xfonts-utils: FTBFS: ../fonttosfnt/util.c:89:10: error: implicit declaration of function ‘vasprintf’; did you mean ‘vsprintf’? [-Werror=implicit-fu

Bug#1093365: vulkan-tools: FTBFS: error: â??VK_DRIVER_ID_RESERVED_27â?? was not declared in this scope

2025-01-23 Thread Simon McVittie
On Thu, 23 Jan 2025 at 13:22:20 +0200, Timo Aaltonen wrote: > Simon McVittie kirjoitti 23.1.2025 klo 13.11: > > Is there something blocking upload of that version? > > vulkan-volk needs an update I opened a bug asking for the new version to be packaged, and it has now been closed by an upload to u

Bug#1093365: vulkan-tools: FTBFS: error: â??VK_DRIVER_ID_RESERVED_27â?? was not declared in this scope

2025-01-23 Thread Timo Aaltonen
info.hpp:103:15: error: ‘VK_DRIVER_ID_RESERVED_27’ was not declared in this scope; did you mean ‘VK_DRIVER_ID_MESA_VENUS’? It looks like this has been fixed in the upstream 1.4.304.0 release, which is staged in the packaging git repository but has not yet been uploaded. Is there someth

Processed: Re: Bug#1093365: vulkan-tools: FTBFS: error: â??VK_DRIVER_ID_RESERVED_27â?? was not declared in this scope

2025-01-23 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + fixed-upstream pending Bug #1093365 [src:vulkan-tools] vulkan-tools: FTBFS: error: ‘VK_DRIVER_ID_RESERVED_27’ was not declared in this scope Added tag(s) fixed-upstream and pending. -- 1093365: https://bugs.debian.org/cgi-bin/bugreport.cgi?

Bug#1093365: vulkan-tools: FTBFS: error: â??VK_DRIVER_ID_RESERVED_27â?? was not declared in this scope

2025-01-23 Thread Simon McVittie
Control: tags -1 + fixed-upstream pending On Fri, 17 Jan 2025 at 18:54:30 +, Santiago Vila wrote: > /<>/vulkaninfo/generated/vulkaninfo.hpp: In function > ‘std::string VkDriverIdString(VkDriverId)’: > /<>/vulkaninfo/generated/vulkaninfo.hpp:103:15: error: > ‘V

Bug#1093365: vulkan-tools: FTBFS: error: ‘VK_DRIVER_ID_RESERVED_27’ was not declared in this scope

2025-01-17 Thread Santiago Vila
g: ‘vk::DebugUtilsMessengerCreateInfoEXT::DebugUtilsMessengerCreateInfoEXT(vk::DebugUtilsMessengerCreateFlagsEXT, vk::DebugUtilsMessageSeverityFlagsEXT, vk::DebugUtilsMessageTypeFlagsEXT, PFN_vkDebugUtilsMessengerCallbackEXT, void*, const void*)’ is deprecated: This constructor is deprecated. Use

Bug#1091583: marked as done (vkmark: FTBFS on i386: dh_auto_test: error: cd obj-i686-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test returned exit code 1)

2025-01-07 Thread Debian Bug Tracking System
Your message dated Tue, 07 Jan 2025 11:23:47 + with message-id and subject line Bug#1091583: fixed in vkmark 2017.08+git20220909-2 has caused the Debian Bug report #1091583, regarding vkmark: FTBFS on i386: dh_auto_test: error: cd obj-i686-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=de

Bug#1091583: vkmark: FTBFS on i386: dh_auto_test: error: cd obj-i686-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test returned exit code 1

2024-12-28 Thread Lucas Nussbaum
Source: vkmark Version: 2017.08+git20220909-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20241228 ftbfs-trixie Hi, During a rebuild of all packages in sid, this package failed to build on i386. This package currently has binary packages o

Bug#1087279: xserver-xorg-video-vesa FTBFS: error: implicit declaration of function 'outb'

2024-11-10 Thread Helmut Grohne
/stdlib.h:687:25: note: expected 'void *' but argument is of type 'const char *' | 687 | extern void free (void *__ptr) __THROW; | | ~~^~~~~ | ../../src/vesa.c: In function 'VESALoadPalette': | ../../src/vesa.c:1437:12: error: implicit

Bug#1076172: marked as done (pixman: FTBFS on armhf: Error: garbage following instruction -- `bne 01f')

2024-11-07 Thread Debian Bug Tracking System
Your message dated Thu, 07 Nov 2024 23:15:45 +0100 with message-id <12594627.O9o76ZdvQC@bagend> and subject line Re: pixman: FTBFS on armhf: Error: garbage following instruction -- `bne 01f' has caused the Debian Bug report #1076172, regarding pixman: FTBFS on armhf: Error: garbag

Processed (with 1 error): Re: [Debian-on-mobile-maintainers] Bug#1082985: Bug#1082985: chatty: fails to build on armhf

2024-11-06 Thread Debian Bug Tracking System
Processing control commands: > forcemerge 1084230 1082985 Bug #1084230 [xvfb] xvfb: please consider disabling libunwind, at least on armhf Unable to merge bugs because: package of #1082985 is 'src:chatty' not 'xvfb' Failed to forcibly merge 1084230: Did not alter merged bugs. -- 1082985: https:

[Git][xorg-team/xserver/xorg-server][debian-unstable] 25 commits: ephyr: Fix incompatible pointer type build error

2024-10-29 Thread Julien Cristau (@jcristau)
Julien Cristau pushed to branch debian-unstable at X Strike Force / xserver / xorg-server Commits: 8407181c by José Expósito at 2024-05-12T08:00:00+00:00 ephyr: Fix incompatible pointer type build error Fix a compilation error on 32 bits architectures with gcc 14: ephyr_glamor_xv.c: In

[Git][xorg-team/wayland/wayland-protocols][upstream-unstable] 25 commits: xdg-decoration: add invalid_mode error

2024-10-14 Thread @daissi
Dylan Aïssi pushed to branch upstream-unstable at X Strike Force / wayland / wayland-protocols Commits: df2b5e5e by Simon Ser at 2024-09-03T10:27:40+00:00 xdg-decoration: add invalid_mode error There is no error defined for invalid mode values. Signed-off-by: Simon Ser <cont...@emersion

Bug#1081880: marked as done (vulkan-tools: FTBFS: vulkaninfo/generated/vulkaninfo.hpp:102:15: error: ‘VK_DRIVER_ID_MESA_AGXV’ was not declared in this scope)

2024-09-16 Thread Debian Bug Tracking System
Your message dated Mon, 16 Sep 2024 08:55:28 + with message-id and subject line Bug#1081880: fixed in vulkan-tools 1.3.290.0+dfsg1-1 has caused the Debian Bug report #1081880, regarding vulkan-tools: FTBFS: vulkaninfo/generated/vulkaninfo.hpp:102:15: error: ‘VK_DRIVER_ID_MESA_AGXV’ was not

Bug#1081880: vulkan-tools: FTBFS: vulkaninfo/generated/vulkaninfo.hpp:102:15: error: ‘VK_DRIVER_ID_MESA_AGXV’ was not declared in this scope

2024-09-15 Thread Santiago Vila
-f vulkaninfo/CMakeFiles/vulkaninfo.dir/build.make vulkaninfo/CMakeFiles/vulkaninfo.dir/build make[3]: Entering directory '/<>/build' [ 75%] Building CXX object vulkaninfo/CMakeFiles/vulkaninfo.dir/vulkaninfo.cpp.o cd /<>/build/vulkaninfo && /usr/bin/c++ -DVK_ENAB

Bug#1081863: gfxreconstruct: FTBFS: framework/generated/generated_vulkan_enum_to_string.cpp:3644:10: error: ‘VK_DRIVER_ID_MESA_AGXV’ was not declared in this scope

2024-09-15 Thread Santiago Vila
DISPLAY_KHR -DVK_USE_PLATFORM_HEADLESS -DVK_USE_PLATFORM_WAYLAND_KHR -DVK_USE_PLATFORM_XCB_KHR -DVK_USE_PLATFORM_XLIB_KHR -DVK_USE_PLATFORM_XLIB_XRANDR_EXT -DWAYLAND_LIBRARY=\"/usr/lib/x86_64-linux-gnu/libwayland-client.so\" -DX11_XCB_LIBRARY=\"/usr/lib/x86_64-linux-gnu/libX11-xcb.so\&

Processed: Re: Bug#1080435: mesa: 24.2.x regression on riscv64: JIT session error, Failed to materialize symbols

2024-09-07 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 src:llvm-toolchain-18 Bug #1080435 [src:mesa] mesa: 24.2.x regression on riscv64: JIT session error, Failed to materialize symbols Bug reassigned from package 'src:mesa' to 'src:llvm-toolchain-18'. No longer marked as found in

Bug#1080435: mesa: 24.2.x regression on riscv64: JIT session error, Failed to materialize symbols

2024-09-07 Thread Aurelien Jarno
ncies > > * build gtk4 (it will fail build-time tests) > > * To run one of the affected tests: > > schroot -c $chroot -r -- \ > > env GDK_DEBUG=opengl,vulkan,gl-debug GDK_BACKEND=x11 \ > > xvfb-run -a \ > > debian/build/deb/testsuite/gdk/memorytexture --tap -k >

Bug#1080435: mesa: 24.2.x regression on riscv64: JIT session error, Failed to materialize symbols

2024-09-03 Thread Eric Long
ot -r -- \ env GDK_DEBUG=opengl,vulkan,gl-debug GDK_BACKEND=x11 \ xvfb-run -a \ debian/build/deb/testsuite/gdk/memorytexture --tap -k Expected result: test passes Actual result: > JIT session error: No HI20 PCREL relocation type be found for LO12 PCREL relocation type > Failed to

Bug#1080435: mesa: 24.2.x regression on riscv64: JIT session error, Failed to materialize symbols

2024-09-03 Thread Simon McVittie
xvfb-run -a \ debian/build/deb/testsuite/gdk/memorytexture --tap -k Expected result: test passes Actual result: > JIT session error: No HI20 PCREL relocation type be found for LO12 PCREL > relocation type > Failed to materialize symbols: { (fs681_variant0_14, { fs_v

Processed: mesa: 24.2.x regression on riscv64: JIT session error, Failed to materialize symbols

2024-09-03 Thread Debian Bug Tracking System
Processing control commands: > affects -1 + src:gtk4 Bug #1080435 [src:mesa] mesa: 24.2.x regression on riscv64: JIT session error, Failed to materialize symbols Added indication that 1080435 affects src:gtk4 -- 1080435: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080435 Debian

Bug#1061616: pixman: FTBFS on armhf: Error: garbage following instruction -- `bne 01f'

2024-08-26 Thread Diederik de Haas
Control: tag -1 -patch -upstream -fixed-upstream Control: notforwarded -1 On 26 Aug 2024 17:22:19 +0200 Diederik de Haas wrote: > Control: tag -1 upstream fixed-upstream patch > Control: forwarded -1 https://gitlab.freedesktop.org/pixman/pixman/-/issues/96 Oeps, my CC-ing this bug also modified

Processed: Re: pixman: FTBFS on armhf: Error: garbage following instruction -- `bne 01f'

2024-08-26 Thread Debian Bug Tracking System
Processing control commands: > tag -1 -patch -upstream -fixed-upstream Bug #1061616 [src:pixman] pixman: New upstream version 0.43.4 Removed tag(s) patch. Bug #1061616 [src:pixman] pixman: New upstream version 0.43.4 Removed tag(s) upstream. Bug #1061616 [src:pixman] pixman: New upstream version 0

Processed: Re: pixman: FTBFS on armhf: Error: garbage following instruction -- `bne 01f'

2024-08-26 Thread Debian Bug Tracking System
Processing control commands: > tag -1 upstream fixed-upstream patch Bug #1076172 [src:pixman] pixman: FTBFS on armhf: Error: garbage following instruction -- `bne 01f' Added tag(s) upstream, fixed-upstream, and patch. > forwarded -1 https://gitlab.freedesktop.org/pixman/pixman/-/is

Bug#1061616: pixman: FTBFS on armhf: Error: garbage following instruction -- `bne 01f'

2024-08-26 Thread Diederik de Haas
ent sid/testing with: > > ../../pixman/pixman-arm-simd-asm.h:821: Error: garbage following instruction > -- `bne 01f' > ../../pixman/pixman-arm-simd-asm.h:869: Info: macro invoked from here > ... > See https://gitlab.freedesktop.org/pixman/pixman/-/issues/96 and bug >

Processed: Re: pixman: FTBFS on armhf: Error: garbage following instruction -- `bne 01f'

2024-08-26 Thread Debian Bug Tracking System
Processing control commands: > tag -1 upstream fixed-upstream patch Bug #1061616 [src:pixman] pixman: New upstream version 0.43.4 Added tag(s) upstream, fixed-upstream, and patch. > forwarded -1 https://gitlab.freedesktop.org/pixman/pixman/-/issues/96 Bug #1061616 [src:pixman] pixman: New upstream

Processed (with 1 error): Forwarded upstream

2024-08-19 Thread Debian Bug Tracking System
Processing control commands: > tags -1 upstream Bug #883278 [xbacklight] Offer non-linear stepping Added tag(s) upstream. > forwarded https://gitlab.freedesktop.org/xorg/app/xbacklight/-/issues/7 Unknown command or malformed arguments to command. -- 883278: https://bugs.debian.org/cgi-bin/bugre

Bug#1078229: xserver-xorg-video-ivtvdev: FTBFS with GCC 14: error: assignment ... from incompatible pointer type ...

2024-08-08 Thread Andreas Beckmann
7;: ../../src/ivtv.c:350:13: warning: assignment discards 'const' qualifier from pointer target type [-Wdiscarded-qualifiers] 350 | dev = xf86FindOptionValue(devSections[i]->options, "fbdev"); | ^ ../../src/ivtv.c:373:26: error: assignment to &#x

Processed (with 1 error): BTS housekeeping

2024-07-26 Thread Debian Bug Tracking System
075262 [src:mbedtls] mbedtls: ftbfs with GCC-14 Marked as fixed in versions mbedtls/3.6.0-2. Bug #1075262 [src:mbedtls] mbedtls: ftbfs with GCC-14 Marked Bug as done > tags 1075443 experimental Bug #1075443 [src:rep-gtk] rep-gtk: ftbfs with GCC-14 Added tag(s) experimental. > forcemerge 1066328

Processed (with 1 error): Re: /usr/bin/firefox: crashes when trying to view a PDF file

2024-07-14 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 libegl-mesa0 24.1.0-2 Bug #1072557 [firefox] /usr/bin/firefox: crashes when trying to view a PDF file Bug reassigned from package 'firefox' to 'libegl-mesa0'. No longer marked as found in versions firefox/126.0.1-1. Ignoring request to alter fixed version

Bug#1076172: pixman: FTBFS on armhf: Error: garbage following instruction -- `bne 01f'

2024-07-11 Thread Mike Hommey
Source: pixman Version: 0.42.2-1 Severity: serious Dear Maintainer, The package fails to build on armhf on current sid/testing with: ../../pixman/pixman-arm-simd-asm.h:821: Error: garbage following instruction -- `bne 01f' ../../pixman/pixman-arm-simd-asm.h:869: Info: macro invoked from

Bug#1073310: marked as done (vulkan-tools: FTBFS: vulkan_hpp_macros.hpp:135:38: error: operator '==' has no left operand)

2024-06-18 Thread Debian Bug Tracking System
Your message dated Tue, 18 Jun 2024 07:50:22 + with message-id and subject line Bug#1073310: fixed in vulkan-tools 1.3.283.0+dfsg1-1 has caused the Debian Bug report #1073310, regarding vulkan-tools: FTBFS: vulkan_hpp_macros.hpp:135:38: error: operator '==' has no left operand to

Bug#1073310: vulkan-tools: FTBFS: vulkan_hpp_macros.hpp:135:38: error: operator '==' has no left operand

2024-06-16 Thread Lucas Nussbaum
kcube-wayland.dir/xdg-shell-code.c.o.d -o > CMakeFiles/vkcube-wayland.dir/xdg-shell-code.c.o -c > /<>/build/cube/xdg-shell-code.c > In file included from /usr/include/vulkan/vulkan.hpp:16, > from /<>/cube/cube.cpp:44: > /usr/include/vulka

Processed: Re: x11-apps: FTBFS on arm64: configure: error: Package requirements (x11-xcb xcb-present >= 1.9 xcb-xfixes xcb-damage) were not met

2024-04-27 Thread Debian Bug Tracking System
Processing control commands: > retitle -1 x11-apps: FTBFS with libxcb 1.17: Package requirements (x11-xcb > xcb-present >= 1.9 xcb-xfixes xcb-damage) were not met Bug #1069405 [src:x11-apps] x11-apps: FTBFS on arm64: configure: error: Package requirements (x11-xcb xcb-present >= 1.

Bug#1069405: x11-apps: FTBFS on arm64: configure: error: Package requirements (x11-xcb xcb-present >= 1.9 xcb-xfixes xcb-damage) were not met

2024-04-27 Thread Andreas Beckmann
Followup-For: Bug #1069405 Control: retitle -1 x11-apps: FTBFS with libxcb 1.17: Package requirements (x11-xcb xcb-present >= 1.9 xcb-xfixes xcb-damage) were not met Control: block -1 with 1069408 This happens on all architectures and is probably caused by the missing libxcb-dri3-dev dependency i

Processed: Re: Bug#1069408: kwin: FTBFS on arm64: present.h:20:10: fatal error: dri3.h: No such file or directory

2024-04-21 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 libxcb Bug #1069408 [src:kwin] kwin: FTBFS on arm64: present.h:20:10: fatal error: dri3.h: No such file or directory Bug reassigned from package 'src:kwin' to 'libxcb'. No longer marked as found in versions kwin/4:5.27.10-1. Ig

Bug#1069405: x11-apps: FTBFS on arm64: configure: error: Package requirements (x11-xcb xcb-present >= 1.9 xcb-xfixes xcb-damage) were not met

2024-04-20 Thread Lucas Nussbaum
ing if gcc supports -Werror=attributes... yes > checking whether make supports nested variables... (cached) yes > checking for xi >= 1.7 x11 xt xext xmu xproto >= 7.0.17... yes > checking for xrender >= 0.4... yes > checking for x11-xcb xcb-present >= 1.9 xcb-xfixes xcb-dama

Bug#1067312: spirv-tools: FTBFS: operand.kinds-unified1.inc:566:97: error: ‘SPV_OPERAND_TYPE_NAMED_MAXIMUM_NUMBER_OF_REGISTERS’ was not declared in this scope

2024-04-02 Thread Giovanni Mascellani
Hi, On Wed, 20 Mar 2024 21:58:27 +0100 Lucas Nussbaum wrote:> During a rebuild of all packages in sid, your package failed to build on amd64. I'm having the same problem. As a data point, builds succeeds as soon as I revert spirv-headers to 1.6.1+1.3.275.0-1. HTH, Gio.

Bug#1067312: spirv-tools: FTBFS: operand.kinds-unified1.inc:566:97: error: ‘SPV_OPERAND_TYPE_NAMED_MAXIMUM_NUMBER_OF_REGISTERS’ was not declared in this scope

2024-03-20 Thread Lucas Nussbaum
-Wno-sign-conversion -fno-exceptions -MD -MT > source/CMakeFiles/SPIRV-Tools-static.dir/print.cpp.o -MF > CMakeFiles/SPIRV-Tools-static.dir/print.cpp.o.d -o > CMakeFiles/SPIRV-Tools-static.dir/print.cpp.o -c > "/<>/source/print.cpp" > In file included from /<>/source/op

Bug#1067012: renderdoc: FTBFS with glslang 14: fatal error: glslang/Include/Types.h: No such file or directory

2024-03-16 Thread Andreas Beckmann
lang_compile.cpp.o -c /build/renderdoc-1.27+dfsg/renderdoc/driver/shaders/spirv/glslang_compile.cpp /build/renderdoc-1.27+dfsg/renderdoc/driver/shaders/spirv/glslang_compile.cpp:32:10: fatal error: glslang/Include/Types.h: No such file or directory 32 | #include "glslang/Include/Types.h" | ^ compilation terminated. Andreas

Bug#1066382: marked as done (xserver-xorg-video-nouveau: FTBFS: ../../src/nv_driver.c:1451:23: error: implicit declaration of function ‘wfbScreenInit’; did you mean ‘fbScreenInit’? [-Werror=implicit-f

2024-03-15 Thread Debian Bug Tracking System
Your message dated Fri, 15 Mar 2024 20:22:20 + with message-id and subject line Bug#1066382: fixed in xserver-xorg-video-nouveau 1:1.0.17-3 has caused the Debian Bug report #1066382, regarding xserver-xorg-video-nouveau: FTBFS: ../../src/nv_driver.c:1451:23: error: implicit declaration of

Bug#1066382: xserver-xorg-video-nouveau: FTBFS: ../../src/nv_driver.c:1451:23: error: implicit declaration of function ‘wfbScreenInit’; did you mean ‘fbScreenInit’? [-Werror=implicit-function-declarat

2024-03-14 Thread Sven Joachim
gt; -fcf-protection -Wall -minline-all-stringops -I/usr/include/xorg >>> -fvisibility=hidden -I/usr/include/pixman-1 -I/usr/include/X11/dri >>> -I/usr/include/libdrm -c -o nv04_xv_ovl.lo ../../src/nv04_xv_ovl.c >>> ../../src/nv_driver.c: In function ‘NVScreenInit’: >>

Bug#1066263: xfonts-utils: FTBFS: ../fonttosfnt/util.c:89:10: error: implicit declaration of function ‘vasprintf’; did you mean ‘vsprintf’? [-Werror=implicit-function-declaration]

2024-03-14 Thread Thomas Dickey
On Wed, Mar 13, 2024 at 10:44:07PM +0500, Andrey Rakhmatullin wrote: > On Wed, Mar 13, 2024 at 12:46:49PM +0100, Lucas Nussbaum wrote: > > > ../fonttosfnt/util.c: In function ‘vsprintf_alloc’: > > > ../fonttosfnt/util.c:89:10: error: implicit declaration of function >

Bug#1066263: xfonts-utils: FTBFS: ../fonttosfnt/util.c:89:10: error: implicit declaration of function ‘vasprintf’; did you mean ‘vsprintf’? [-Werror=implicit-function-declaration]

2024-03-13 Thread Andrey Rakhmatullin
On Wed, Mar 13, 2024 at 12:46:49PM +0100, Lucas Nussbaum wrote: > > ../fonttosfnt/util.c: In function ‘vsprintf_alloc’: > > ../fonttosfnt/util.c:89:10: error: implicit declaration of function > > ‘vasprintf’; did you mean ‘vsprintf’? > > [-Werror=implicit-function-decl

Processed: Re: Bug#1066382: xserver-xorg-video-nouveau: FTBFS: ../../src/nv_driver.c:1451:23: error: implicit declaration of function ‘wfbScreenInit’; did you mean ‘fbScreenInit’? [-Werror=implicit-fu

2024-03-13 Thread Debian Bug Tracking System
Processing control commands: > forwarded -1 > https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/-/issues/569 Bug #1066382 [src:xserver-xorg-video-nouveau] xserver-xorg-video-nouveau: FTBFS: ../../src/nv_driver.c:1451:23: error: implicit declaration of function ‘wfbScreenInit

Bug#1066382: xserver-xorg-video-nouveau: FTBFS: ../../src/nv_driver.c:1451:23: error: implicit declaration of function ‘wfbScreenInit’; did you mean ‘fbScreenInit’? [-Werror=implicit-function-declarat

2024-03-13 Thread Sven Joachim
nv04_xv_ovl.lo ../../src/nv04_xv_ovl.c >> ../../src/nv_driver.c: In function ‘NVScreenInit’: >> ../../src/nv_driver.c:1451:23: error: implicit declaration of >> function ‘wfbScreenInit’; did you mean

Bug#1066545: xserver-xorg-video-openchrome: FTBFS: ../../src/via_driver.c:1678:45: error: implicit declaration of function ‘shadowUpdatePackedWeak’; did you mean ‘shadowUpdatePacked’? [-Werror=implici

2024-03-13 Thread Lucas Nussbaum
~~~ > ../../src/via_display.c: In function ‘iga2_crtc_commit’: > ../../src/via_display.c:4254:9: warning: ‘xf86_reload_cursors’ is deprecated > [-Wdeprecated-declarations] > 4254 | xf86_reload_cursors(cr

Bug#1066382: xserver-xorg-video-nouveau: FTBFS: ../../src/nv_driver.c:1451:23: error: implicit declaration of function ‘wfbScreenInit’; did you mean ‘fbScreenInit’? [-Werror=implicit-function-declarat

2024-03-13 Thread Lucas Nussbaum
/dri -I/usr/include/libdrm -c -o > nv04_xv_ovl.lo ../../src/nv04_xv_ovl.c > ../../src/nv_driver.c: In function ‘NVScreenInit’: > ../../src/nv_driver.c:1451:23: error: implicit declaration of function > ‘wfbScreenInit’; did you mean ‘fbScreenInit’? > [-Werror=implicit-function-declaratio

Bug#1066263: xfonts-utils: FTBFS: ../fonttosfnt/util.c:89:10: error: implicit declaration of function ‘vasprintf’; did you mean ‘vsprintf’? [-Werror=implicit-function-declaration]

2024-03-13 Thread Lucas Nussbaum
> int} > ../fonttosfnt/read.c:239:43: warning: format ‘%d’ expects argument of type > ‘int’, but argument 5 has type ‘FT_Pos’ {aka ‘long int’} [-Wformat=] > 239 | fprintf(stderr, "size %d: %dx%d\n", > | ~^ > | | > |

How to debug this X error

2024-02-04 Thread picca
Hello, on of my package 'hkl' is using asymptote in order to generate a few figures. But when I use it on my laptop (MacBook pro) I get this error message make[3] : on entre dans le répertoire « /home/picca/src/repo.or.cz/hkl/Documentation/figures » /usr/bin/asy -config "&q

Bug#1058218: marked as done (libei: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test --timeout-multiplier 2 returned e

2024-01-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Jan 2024 17:57:47 -0500 with message-id and subject line re: libei: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test --timeout-multiplier 2 returned exit code 1 has caused th

Processed (with 1 error): Re: mesa-vdpau-drivers: Upgrade to 23.3.* breaks video rendering in tkinter

2024-01-24 Thread Debian Bug Tracking System
Processing control commands: > retitle -1: Upgrade to 23.3.* breaks video rendering Unknown command or malformed arguments to command. > severity -1 serious Bug #1059782 [mesa-vdpau-drivers] mesa-vdpau-drivers: Upgrade to 23.3.* breaks video rendering in tkinter Severity set to 'serious' from 'i

Processed: Re: Bug#1058218: libei: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test --timeout-multiplier 2 returned ex

2023-12-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1058218 upstream Bug #1058218 [src:libei] libei: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test --timeout-multiplier 2 returned exit code 1

Bug#1058218: libei: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test --timeout-multiplier 2 returned exit code 1

2023-12-13 Thread Sebastien Bacher
The build is failing on ppc64el for Ubuntu so it might be more of a timing issue than architecture specific. I've reported it upstream to https://bugs.launchpad.net/ubuntu/+source/libei/+bug/2046357

Bug#1058405: mesa: FTBFS: ../src/gallium/drivers/d3d12/d3d12_video_enc_h264.cpp:127:16: error: ‘D3D12_VIDEO_ENCODER_RATE_CONTROL_FLAG_ENABLE_EXTENDED_QVBR1_SUPPORT’ was not declared in this scope; did

2023-12-12 Thread Lucas Nussbaum
p/d3d12_video_enc_h264.cpp.o.d -o > src/gallium/drivers/d3d12/libd3d12.a.p/d3d12_video_enc_h264.cpp.o -c > ../src/gallium/drivers/d3d12/d3d12_video_enc_h264.cpp > ../src/gallium/drivers/d3d12/d3d12_video_enc_h264.cpp: In function ‘void > d3d12_video_encoder_update_current_rate_control_h26

Bug#1058218: libei: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test --timeout-multiplier 2 returned exit code 1

2023-12-12 Thread Lucas Nussbaum
t; test_ei_keymap_set [ OK] [ 0.54313485 / 0.54306673 CPU ] > test_ei_keymap_invalid [ OK] [ 1.24930054 / 1.24926505 CPU ] > test_ei_device_multitouch[ OK] [ 1.88969743 / 1.88946218 CPU ] > test_ei_device_touch [ OK

Bug#994411: marked as done (error: ‘DRM_IOCTL_I915_GEM_MMAP_OFFSET’ undeclared)

2023-11-08 Thread Debian Bug Tracking System
Your message dated Wed, 08 Nov 2023 16:33:44 +0100 with message-id <6541022.USpHSMS00B@bagend> and subject line Re: error: ‘DRM_IOCTL_I915_GEM_MMAP_OFFSET’ un declared has caused the Debian Bug report #994411, regarding error: ‘DRM_IOCTL_I915_GEM_MMAP_OFFSET’ undeclared to be marked as done.

Bug#1054709: vulkan-validationlayers: FTBFS: gpu_validation.cpp:959:55: error: too many arguments to function ‘spvtools::Optimizer::PassToken spvtools::CreateInstBindlessCheckPass(uint32_t, uint32_t)’

2023-10-27 Thread Lucas Nussbaum
; /<>/layers/object_tracker/object_tracker_utils.cpp > /<>/layers/gpu_validation/gpu_validation.cpp: In member function > ‘virtual bool GpuAssisted::InstrumentShader(const vvl::span int>&, std::vector&, uint32_t*)’: > /<>/layers/gpu_validation/gpu_validation.cpp:959

Processed: Re: Bug#1053469: libx11 FTBFS: dh_quilt_unpatch: error: quilt --quiltrc /dev/null pop -a || test $? = 1 returned exit code 1

2023-10-04 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 quilt Bug #1053469 [src:libx11] libx11 FTBFS: dh_quilt_unpatch: error: quilt --quiltrc /dev/null pop -a || test $? = 1 returned exit code 1 Bug reassigned from package 'src:libx11' to 'quilt'. No longer marked as found in ve

Bug#1053469: libx11 FTBFS: dh_quilt_unpatch: error: quilt --quiltrc /dev/null pop -a || test $? = 1 returned exit code 1

2023-10-04 Thread Sven Joachim
akeroot debian/rules clean > dh clean --with quilt --builddirectory=build/ >dh_auto_clean -O--builddirectory=build/ >dh_autoreconf_clean -O--builddirectory=build/ >dh_quilt_unpatch -O--builddirectory=build/ > No patch removed > dh_quilt_unpatch: error: quilt --quiltrc /dev

Bug#1053469: libx11 FTBFS: dh_quilt_unpatch: error: quilt --quiltrc /dev/null pop -a || test $? = 1 returned exit code 1

2023-10-04 Thread Adrian Bunk
tory=build/ dh_quilt_unpatch -O--builddirectory=build/ No patch removed dh_quilt_unpatch: error: quilt --quiltrc /dev/null pop -a || test $? = 1 returned exit code 1 make: *** [debian/rules:4: clean] Error 25

Processed (with 1 error): merging 1050844 1050994

2023-09-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > merge 1050844 1050994 Bug #1050844 [xutils-dev] xutils-dev: Please add support for new arch Loongarch Unable to merge bugs because: package of #1050994 is 'src:xutils-dev' not 'xutils-dev' Failed to merge 1050844: Did not alter merged bugs. > tha

Bug#1043429: xserver-xorg-input-libinput: "xinput set-prop" command fails with error

2023-08-10 Thread Gordon Shumway
Package: xserver-xorg-input-libinput Version: 1.3.0-1 Severity: important X-Debbugs-Cc: g.shumw...@gmx.net -- Package-specific info: /etc/X11/X does not exist. /etc/X11/X is not a symlink. /etc/X11/X is not executable. VGA-compatible devices on PCI bus: -- 05:00

Bug#1040617: Spelling error in the upstream web address and a new version

2023-07-07 Thread Bjarni Ingi Gislason
Package: xorg-docs-core Version: 1:1.7.1-1.2 Severity: normal Dear Maintainer, A '/' is missing between 'org' and 'releases' There is a new version 1.7.2 from 2022-04-04. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd

Bug#1035014: marked as done (installation-reports: Graphical installer has Xorg "no screens found" error)

2023-05-02 Thread Debian Bug Tracking System
Your message dated Wed, 03 May 2023 02:37:51 + with message-id and subject line Bug#1035014: fixed in xorg-server 2:21.1.7-3 has caused the Debian Bug report #1035014, regarding installation-reports: Graphical installer has Xorg "no screens found" error to be marked as done. This

Bug#1035014: installation-reports: Graphical installer has Xorg "no screens found" error

2023-05-02 Thread Cyril Brulebois
Hi Timo! Timo Aaltonen (2023-05-02): > Hi, fine by me! Thanks, uploaded. I'll keep an eye on it, and request an unblock (letting debian-x@ know via X-Debbugs-Cc) once I've checked britney doesn't report any red flags. It's going to be on two different radars of mine anyway: - https://d-i.debi

Bug#1035014: installation-reports: Graphical installer has Xorg "no screens found" error

2023-05-02 Thread Timo Aaltonen
Cyril Brulebois kirjoitti 1.5.2023 klo 18.50: Control: reassign -1 xserver-xorg-core-udeb 2:21.1.1-1 Control: affects -1 debian-installer Hello debian-x, Cyril Brulebois (2023-04-27): Tracked down to 9c81b8f5b5 upstream: https://cgit.freedesktop.org/xorg/xserver/commit/?id=9c81b8f5b5 Flip

Processed: Re: Bug#1035014: installation-reports: Graphical installer has Xorg "no screens found" error

2023-05-01 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 xserver-xorg-core-udeb 2:21.1.1-1 Bug #1035014 [installation-reports] installation-reports: Graphical installer has Xorg "no screens found" error Bug reassigned from package 'installation-reports' to 'xserver-xorg-core-udeb

Re: Bug#1035014: installation-reports: Graphical installer has Xorg "no screens found" error

2023-05-01 Thread Cyril Brulebois
Control: reassign -1 xserver-xorg-core-udeb 2:21.1.1-1 Control: affects -1 debian-installer Hello debian-x, Cyril Brulebois (2023-04-27): > Tracked down to 9c81b8f5b5 upstream: > https://cgit.freedesktop.org/xorg/xserver/commit/?id=9c81b8f5b5 > > Flipping the switch and wrapping it up in a ne

Re: Bug#1035014: installation-reports: Graphical installer has Xorg "no screens found" error

2023-04-27 Thread kt programs
On Thu Apr 27, 2023 at 10:39 PM +08, Cyril Brulebois wrote: > Control: tag -1 patch > > Hi Keith and X team, > > and thanks for your report. > > Keith Toh (2023-04-27): > > Image version: > > http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/arm64/iso-cd/debian-testing-arm64-netins

Re: Bug#1035014: installation-reports: Graphical installer has Xorg "no screens found" error

2023-04-27 Thread Cyril Brulebois
Control: tag -1 patch Hi Keith and X team, and thanks for your report. Keith Toh (2023-04-27): > Image version: > http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/arm64/iso-cd/debian-testing-arm64-netinst.iso > (2023-04-24 23:09) For the avoidance of doubt: same story with am

Bug#1025389: libgl1-mesa-dri: AIGLX error: dlopen of /usr/lib/x86_64-linux-gnu/dri/i965_dri.so

2023-03-05 Thread bob_smith_1337
rendering. you can check if you have the same issue by using MESA_LOADER_DRIVER_OVERRIDE=iris (if iris is the one corresponding to your intel graphics): :~$ xdriinfo libGL error: MESA-LOADER: failed to open i965: /usr/lib/dri/i965_dri.so: cannot open shared object file: No such file or directory

Bug#1025389: libgl1-mesa-dri: AIGLX error: dlopen of /usr/lib/x86_64-linux-gnu/dri/i965_dri.so

2023-03-05 Thread bob_smith_1337
tting driver: i915, version 1.6.0 20201103 [ 18.829] (II) intel(0): [DRI2] DRI driver: i965 [ 18.867] (EE) AIGLX error: dlopen of /usr/lib/x86_64-linux-gnu/dri/i965_dri.so failed (/usr/lib/x86_64-linux-gnu/dri/i965_dri.so: cannot open shared object file: No such file or directory) [ 18.867] (EE) AIGL

Bug#1026585: marked as done (gfxreconstruct: FTBFS: generated_vulkan_enum_to_string.cpp:2006:10: error: ‘VK_STRUCTURE_TYPE_VIDEO_PROFILE_KHR’ was not declared in this scope; did you mean ‘VK_STRUCTURE

2023-01-17 Thread Debian Bug Tracking System
Your message dated Tue, 17 Jan 2023 22:42:23 + with message-id and subject line Bug#1026585: fixed in gfxreconstruct 0.9.16.1+dfsg-1 has caused the Debian Bug report #1026585, regarding gfxreconstruct: FTBFS: generated_vulkan_enum_to_string.cpp:2006:10: error

Bug#1004154: marked as done (xserver-xorg-video-qxl: XOrg frequently crashes when using qxl driver: qxl(0): error doing QXL_ALLOC)

2023-01-07 Thread Debian Bug Tracking System
Your message dated Sat, 7 Jan 2023 17:10:57 +0100 with message-id and subject line Re: Fwd: Bug#1004154: xserver-xorg-video-qxl: XOrg frequently crashes when using qxl driver: qxl(0): error doing QXL_ALLOC has caused the Debian Bug report #1004154, regarding xserver-xorg-video-qxl: XOrg

Bug#1004154: Fwd: Bug#1004154: xserver-xorg-video-qxl: XOrg frequently crashes when using qxl driver: qxl(0): error doing QXL_ALLOC

2023-01-07 Thread Felix Leimbach
Thanks for forwarding Bernhard. TJ, the problem is gone for me. It was either due to upgrading the RAM size or a subsequent kernel update. Haven't had the problem in months and I'm currently running linux-image-5.19.0-2-amd64. I think you can close this issue.

Bug#1004154: Fwd: Bug#1004154: xserver-xorg-video-qxl: XOrg frequently crashes when using qxl driver: qxl(0): error doing QXL_ALLOC

2023-01-07 Thread Bernhard Übelacker
Forwarding, as the email from TJ possibly did not reach Felix. On Fri, 21 Oct 2022 11:43:07 +0100 TJ wrote: On Sat, 12 Feb 2022 08:21:55 + Felix Leimbach wrote: > I noticed that vgamem_mb was still low (32 MB). > So I changed to this (slightly wasteful) command-line and am now running the

Processed: Re: libgl1-mesa-dri: AIGLX error: dlopen of /usr/lib/x86_64-linux-gnu/dri/i965_dri.so

2023-01-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1025389 normal Bug #1025389 [libgl1-mesa-dri] libgl1-mesa-dri: AIGLX error: dlopen of /usr/lib/x86_64-linux-gnu/dri/i965_dri.so Severity set to 'normal' from 'serious' > thanks Stopping processing here. Ple

Bug#1025389: libgl1-mesa-dri: AIGLX error: dlopen of /usr/lib/x86_64-linux-gnu/dri/i965_dri.so

2023-01-02 Thread Eduard Bloch
severity 1025389 normal thanks Hallo, * Fabio Pedretti [Mon, Jan 02 2023, 10:10:24AM]: > Hi, i965 driver was removed, and replaced by iris, crocus and (gallium > version of) i915. > > Did you have any reference to i965 in your configuration? > > cd /etc/ && grep -ri i965 > > If so try to remove th

Bug#761163: libgl1-mesa-dri: DRI3 causes error messages on i915 driver

2023-01-02 Thread Fabio Pedretti
Are you still able to reproduce this on a newer Debian system?

Bug#1025389: libgl1-mesa-dri: AIGLX error: dlopen of /usr/lib/x86_64-linux-gnu/dri/i965_dri.so

2023-01-02 Thread Fabio Pedretti
Hi, i965 driver was removed, and replaced by iris, crocus and (gallium version of) i915. Did you have any reference to i965 in your configuration? cd /etc/ && grep -ri i965 If so try to remove them, the system should be able to pick up the proper driver. Il giorno dom 1 gen 2023 alle ore 23:47

Bug#1025389: libgl1-mesa-dri: AIGLX error: dlopen of /usr/lib/x86_64-linux-gnu/dri/i965_dri.so

2023-01-01 Thread Eduard Bloch
Am Sun, Jan 01, 2023 at 11:02:08PM +0100 schrieb Eduard Bloch: > reopen 1025389 > severity 1025389 serious > thanks > > Am Sun, Jan 01, 2023 at 02:29:01PM +0100 schrieb Fabio Pedretti: > > Version: 22.3.0-3 > > > > 22.3.0-3 reenabled two intel drivers missing in previou release. > > Why the heck

Processed: Re: libgl1-mesa-dri: AIGLX error: dlopen of /usr/lib/x86_64-linux-gnu/dri/i965_dri.so

2023-01-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reopen 1025389 Bug #1025389 {Done: Fabio Pedretti } [libgl1-mesa-dri] libgl1-mesa-dri: AIGLX error: dlopen of /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 'reopen' may be inappropriate when a bug has been closed with a version; all f

Bug#1025389: libgl1-mesa-dri: AIGLX error: dlopen of /usr/lib/x86_64-linux-gnu/dri/i965_dri.so

2023-01-01 Thread Eduard Bloch
y program requesting GLX support reports: libGL error: MESA-LOADER: failed to open i965: /usr/lib/dri/i965_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri) and that's basically it.

Bug#1025389: marked as done (libgl1-mesa-dri: AIGLX error: dlopen of /usr/lib/x86_64-linux-gnu/dri/i965_dri.so)

2023-01-01 Thread Debian Bug Tracking System
Your message dated Sun, 1 Jan 2023 14:29:01 +0100 with message-id and subject line libgl1-mesa-dri: AIGLX error: dlopen of /usr/lib/x86_64-linux-gnu/dri/i965_dri.so has caused the Debian Bug report #1025389, regarding libgl1-mesa-dri: AIGLX error: dlopen of /usr/lib/x86_64-linux-gnu/dri

Bug#1026585: gfxreconstruct: FTBFS: generated_vulkan_enum_to_string.cpp:2006:10: error: ‘VK_STRUCTURE_TYPE_VIDEO_PROFILE_KHR’ was not declared in this scope; did you mean ‘VK_STRUCTURE_TYPE_VIDEO_PROF

2022-12-20 Thread Lucas Nussbaum
anMemoryAllocator/include -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security "-Wno-error=stringop-overflow=" -Wdate-time > -D_FORTIFY_SOURCE=2 -O3 -DNDEBUG -fPIC -Werror -std=gnu++14 -MD -MT > framework/dec

Bug#1025389: libgl1-mesa-dri: AIGLX error: dlopen of /usr/lib/x86_64-linux-gnu/dri/i965_dri.so

2022-12-18 Thread Bernhard Übelacker
On Sat, 03 Dec 2022 11:48:55 -0800 Jeremiah Mahler wrote: [14.027] (EE) Backtrace: [14.028] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x562070f40c59] [14.028] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x40) [0x7f12c3a5af90] [14.029] (EE) unw_get_proc_name fai

Processed (with 1 error): your mail

2022-12-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1025326 mesa 22.3.0-1 Bug #1025326 [tigervnc-standalone-server] tigervnc-standalone-server: Upgrade of libgl1-mesa-dri to 22.3.0 breaks Xvnc Bug reassigned from package 'tigervnc-standalone-server' to 'mesa'. No longer marked as found in

Processed (with 1 error): Re: Bug#1026116: Patches not applied in security release deb10u6, FTBFS

2022-12-15 Thread Debian Bug Tracking System
Processing control commands: > forcemerge 989852 -1 Bug #989852 [src:xorg-server] xorg-server-source: Cannot build X from provided source tarball Unable to merge bugs because: package of #1026116 is 'xorg-server-source' not 'src:xorg-server' Failed to forcibly merge 989852: Did not alter merged b

  1   2   3   4   5   6   7   8   9   10   >