Bug#1075963: x11-xserver-utils: xsetmode, xsetpointer obsolete
On Mon, Jul 08, 2024 at 03:05:16PM +0200, Julien Cristau wrote: > > xsetmode, xsetpointer [..] obsolete > Is there a particular reason to make this bug important? Both are tiny > utilities, basically making a single X request, so from my point of view > while there's likely little to no usage there's also little cost to > keeping them. Right, there's probably no security importance whatsoever there. Chris
Bug#1075963: x11-xserver-utils: xsetmode, xsetpointer obsolete
Source: x11-xserver-utils Severity: important Hi, In https://www.openwall.com/lists/oss-security/2023/05/02/3 upstream pointed out that xsetmode and xsetpointer are obsolete and do not receive any fixes. xsetpointer supposedly is broken since xorg-server 1.4. Please drop them from the package. Chris
Bug#1070350: xorg: diff for NMU version 1:7.7+23.1
Control: tags 1070350 + patch Control: tags 1070350 + pending I've checked the archive and apparently nothing (build-)depends on xorg-dev. Thus it seems safe to remove libdmx-dev from this metapackage. I've uploaded an NMU as 1:7.7+23.1 to DELAYED/10. Feel free to reschedule / supersede / cancel. Best, Chris diff -Nru xorg-7.7+23/debian/changelog xorg-7.7+23.1/debian/changelog --- xorg-7.7+23/debian/changelog 2021-08-18 13:00:51.0 +0200 +++ xorg-7.7+23.1/debian/changelog 2024-07-08 14:45:55.0 +0200 @@ -1,3 +1,10 @@ +xorg (1:7.7+23.1) unstable; urgency=medium + + * Non-maintainer upload. + * Drop libdmx-dev from xorg-dev meta-package. (Closes: #1070350) + + -- Chris Hofstaedtler Mon, 08 Jul 2024 14:45:55 +0200 + xorg (1:7.7+23) unstable; urgency=medium [ Timo Aaltonen ] diff -Nru xorg-7.7+23/debian/control xorg-7.7+23.1/debian/control --- xorg-7.7+23/debian/control 2021-08-18 09:24:40.0 +0200 +++ xorg-7.7+23.1/debian/control 2024-07-08 14:45:44.0 +0200 @@ -125,7 +125,6 @@ Package: xorg-dev Architecture: all Depends: - libdmx-dev, libfontenc-dev, libfs-dev, libice-dev,
Bug#1075858: mesa-vulkan-drivers > 24.1 should include NVK driver on amd64
Package: mesa-vulkan-drivers Version: 24.1.3-2 Severity: wishlist X-Debbugs-Cc: c...@mg8.org Dear Maintainer, * What led up to the situation? I have a GeForce RTX 3070 and I would love to be able to run games on it without NVIDIA's binary driver * What exactly did you do (or not do) that was effective (or ineffective)? I built mesa from source myself and confirmed that the NVK driver builds and installs successfully * What was the outcome of this action? libEGL fatal: DRI driver not from this Mesa build * What outcome did you expect instead? Was really hoping for working 3D accelerated rendering on my RTX 3070 -- Package-specific info: glxinfo: DISPLAY is not set. /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: -- 09:00.0 VGA compatible controller [0300]: NVIDIA Corporation GA104 [GeForce RTX 3070] [10de:2484] (rev a1) 0c:00.0 VGA compatible controller [0300]: Intel Corporation DG2 [Arc A770] [8086:56a0] (rev 08) /etc/X11/xorg.conf does not exist. Contents of /etc/X11/xorg.conf.d: - total 5 -rw-r--r-- 1 root root 61 Feb 10 2021 00-maxclients.conf -rw-r--r-- 1 root root 112 Dec 2 2022 10-intel.conf /etc/modprobe.d contains no KMS configuration files. Kernel version (/proc/version): --- Linux version 6.9.7-amd64 (debian-ker...@lists.debian.org) (x86_64-linux-gnu-gcc-13 (Debian 13.3.0-1) 13.3.0, GNU ld (GNU Binutils for Debian) 2.42.50.20240625) #1 SMP PREEMPT_DYNAMIC Debian 6.9.7-1 (2024-06-27) Xorg X server log files on system: -- -rw-r--r-- 1 clee clee 103008 Aug 15 2020 /home/clee/.local/share/xorg/Xorg.1.log -rw-r--r-- 1 clee clee 30336 May 7 01:58 /home/clee/.local/share/xorg/Xorg.0.log -rw-r--r-- 1 root root 55846 Jul 6 10:05 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [ 193.160] (--) Log file renamed from "/var/log/Xorg.pid-5024.log" to "/var/log/Xorg.0.log" [ 193.160] X.Org X Server 1.21.1.11 X Protocol Version 11, Revision 0 [ 193.160] Current Operating System: Linux ikora 6.9.7-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.9.7-1 (2024-06-27) x86_64 [ 193.160] Kernel command line: initrd=\0ef4ac2994a74d269d2edfcd92e65113\6.9.7-amd64\initrd.img-6.9.7-amd64 root=ZFS=rpool/buster/debian-1 ro quiet clearcpuid=514 amd_iommu=1 iommu=pt nouveau.config=NvGspRm=1 systemd.machine_id=0ef4ac2994a74d269d2edfcd92e65113 [ 193.160] xorg-server 2:21.1.12-1 (https://www.debian.org/support) [ 193.160] Current version of pixman: 0.42.2 [ 193.160]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 193.160] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 193.160] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Jul 6 10:03:25 2024 [ 193.161] (==) Using config directory: "/etc/X11/xorg.conf.d" [ 193.161] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 193.161] (==) No Layout section. Using the first Screen section. [ 193.161] (==) No screen section available. Using defaults. [ 193.161] (**) |-->Screen "Default Screen Section" (0) [ 193.161] (**) | |-->Monitor "" [ 193.161] (==) No device specified for screen "Default Screen Section". Using the first device section listed. [ 193.161] (**) | |-->Device "Intel Arc A770" [ 193.161] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 193.161] (**) Option "MaxClients" "2048" [ 193.161] (**) Allowing byte-swapped clients [ 193.161] (==) Automatically adding devices [ 193.161] (==) Automatically enabling devices [ 193.161] (==) Automatically adding GPU devices [ 193.161] (==) Automatically binding GPU devices [ 193.161] (**) Max clients allowed: 2048, resource mask: 0x3 [ 193.161] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 193.161]Entry deleted from font path. [ 193.161] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [ 193.161] (==) ModulePath set to "/usr/lib/xorg/modules" [ 193.161] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 193.161] (II) Loader magic: 0x55b7963eaf00 [ 193.161] (II) Module ABI versions: [ 193.161]X.Org ANSI C Emulation: 0.4 [ 193.161]X.Org Video Driver: 25.
Bug#1064396: libinput: diff for NMU version 1.25.0-1.1
Control: tags 1064396 + patch Control: tags 1064396 + pending Dear maintainer, I've prepared an NMU for libinput (versioned as 1.25.0-1.1) and uploaded it to DELAYED/10. Please feel free to tell me if I should delay it longer. Regards. diff -Nru libinput-1.25.0/debian/changelog libinput-1.25.0/debian/changelog --- libinput-1.25.0/debian/changelog 2024-02-05 13:20:23.0 +0100 +++ libinput-1.25.0/debian/changelog 2024-06-03 23:45:58.0 +0200 @@ -1,3 +1,12 @@ +libinput (1.25.0-1.1) unstable; urgency=medium + + * Non-maintainer upload. + + [ Michael Biebl ] + * Install udev rules and helpers into /usr. (Closes: #1064396) + + -- Chris Hofstaedtler Mon, 03 Jun 2024 23:45:58 +0200 + libinput (1.25.0-1) unstable; urgency=medium * New upstream release. diff -Nru libinput-1.25.0/debian/libinput10-udeb.install libinput-1.25.0/debian/libinput10-udeb.install --- libinput-1.25.0/debian/libinput10-udeb.install 2024-01-24 16:25:22.0 +0100 +++ libinput-1.25.0/debian/libinput10-udeb.install 2024-06-03 23:45:56.0 +0200 @@ -1,3 +1,3 @@ -lib/udev +usr/lib/udev usr/lib/*/libinput.so.10* usr/share/libinput diff -Nru libinput-1.25.0/debian/libinput-bin.install libinput-1.25.0/debian/libinput-bin.install --- libinput-1.25.0/debian/libinput-bin.install 2024-01-24 16:25:22.0 +0100 +++ libinput-1.25.0/debian/libinput-bin.install 2024-06-03 23:45:56.0 +0200 @@ -1,2 +1,2 @@ -lib/udev +usr/lib/udev usr/share/libinput diff -Nru libinput-1.25.0/debian/rules libinput-1.25.0/debian/rules --- libinput-1.25.0/debian/rules 2024-01-24 16:25:22.0 +0100 +++ libinput-1.25.0/debian/rules 2024-06-03 23:45:56.0 +0200 @@ -7,12 +7,12 @@ override_dh_auto_configure: dh_auto_configure -B build-deb -- \ -Ddocumentation=false \ - -Dudev-dir=/lib/udev + -Dudev-dir=/usr/lib/udev ifeq ($(with_udeb),yes) dh_auto_configure -B build-udeb -- \ -Ddocumentation=false \ - -Dudev-dir=/lib/udev \ + -Dudev-dir=/usr/lib/udev \ -Dlibwacom=false endif
Bug#1072235: xterm: use wtmpdb to write wtmp entries
Source: xterm Severity: important Per the discussion on debian-devel, Debian will switch to wtmpdb for Y2038-safe wtmp recording. If your package writes wtmp entries, please switch to libpam-wtmpdb or libwtmpdb. https://lists.debian.org/debian-devel/2024/04/msg00406.html Chris
Bug#1063693: xdm: diff for NMU version 1:1.1.11-3.1
Control: tags 1063693 + pending
Dear maintainer,
I've prepared an NMU for xdm (versioned as 1:1.1.11-3.1) and
uploaded it to DELAYED/14. Please feel free to tell me if I
should delay it longer.
Regards.
diff -u xdm-1.1.11/debian/changelog xdm-1.1.11/debian/changelog
--- xdm-1.1.11/debian/changelog
+++ xdm-1.1.11/debian/changelog
@@ -1,3 +1,12 @@
+xdm (1:1.1.11-3.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+
+ [ Helmut Grohne ]
+ * Let systemd.pc determine the location of systemd units. (Closes: #1063693)
+
+ -- Chris Hofstaedtler Thu, 30 May 2024 03:12:21 +0200
+
xdm (1:1.1.11-3) unstable; urgency=medium
* Team upload.
diff -u xdm-1.1.11/debian/control xdm-1.1.11/debian/control
--- xdm-1.1.11/debian/control
+++ xdm-1.1.11/debian/control
@@ -5,8 +5,9 @@
Uploaders: Cyril Brulebois
Build-Depends:
debhelper (>= 9),
+ dh-exec,
dpkg-dev (>= 1.16.1),
- pkg-config,
+ pkgconf,
libxmu-dev (>= 1:1.0.1),
libx11-dev (>= 2:1.0.0),
libxau-dev (>= 1:1.0.0),
@@ -18,6 +19,7 @@
quilt,
automake,
libtool,
+ systemd-dev,
xutils-dev,
Standards-Version: 3.9.6
Vcs-Git: git://anonscm.debian.org/pkg-xorg/app/xdm
diff -u xdm-1.1.11/debian/rules xdm-1.1.11/debian/rules
--- xdm-1.1.11/debian/rules
+++ xdm-1.1.11/debian/rules
@@ -13,6 +13,8 @@
include debian/xsfbs/xsfbs.mk
+export deb_systemdsystemunitdir := $(shell pkgconf --variable=systemdsystemunitdir systemd | sed s,^/,,)
+
confflags += \
--prefix=/usr \
--mandir=\$${prefix}/share/man \
@@ -24,7 +26,7 @@
--with-pixmapdir=/usr/share/X11/xdm/pixmaps \
--with-color-pixmap=debian.xpm \
--with-bw-pixmap=debianbw.xpm \
- --with-systemdsystemunitdir=/lib/systemd/system \
+ --with-systemdsystemunitdir \
--disable-xdm-auth \
--with-xft \
--disable-silent-rules \
@@ -126,6 +128,7 @@
dh_testroot
dh_installdocs
+ chmod +x debian/xdm.install
dh_install --sourcedir=debian/tmp --list-missing
dh_installchangelogs ChangeLog
dh_installinit --noscripts
diff -u xdm-1.1.11/debian/xdm.install xdm-1.1.11/debian/xdm.install
--- xdm-1.1.11/debian/xdm.install
+++ xdm-1.1.11/debian/xdm.install
@@ -1,3 +1,4 @@
+#!/usr/bin/dh-exec
etc/X11/app-defaults/Chooser
etc/X11/xdm/Xaccess
etc/X11/xdm/Xreset
@@ -10,7 +11,7 @@
etc/X11/xdm/xdm-config
etc/X11/xdm/xdm.options
etc/insserv.conf.d/xdm
-lib/systemd/system/xdm.service
+${deb_systemdsystemunitdir}/xdm.service
usr/bin/xdm
usr/lib/X11/xdm/chooser
usr/lib/X11/xdm/libXdmGreet.so
Bug#1060796: xserver-xorg-core: i965_dri.so not found
086:191b] (rev 06)
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GM107GLM [Quadro
M1000M] [10de:13b1] (rev a2)
Xorg X server configuration file status:
-rw-r--r-- 1 root root 3307 Dec 6 21:06 /etc/X11/xorg.conf
Contents of /etc/X11/xorg.conf:
---
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice"Mouse0" "CorePointer"
InputDevice"Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/X11/misc"
FontPath "/usr/share/fonts/X11/cyrillic"
FontPath "/usr/share/fonts/X11/100dpi/:unscaled"
FontPath "/usr/share/fonts/X11/75dpi/:unscaled"
FontPath "/usr/share/fonts/X11/Type1"
FontPath "/usr/share/fonts/X11/100dpi"
FontPath "/usr/share/fonts/X11/75dpi"
FontPath "built-ins"
EndSection
Section "Module"
Load "glx"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5 6 7"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName"Monitor Model"
EndSection
Section "Device"
### Available Driver options are:-
### Values: : integer, : float, : "True"/"False",
### : "String", : " Hz/kHz/MHz",
### : "%"
### [arg]: arg optional
#Option "Accel" # []
#Option "AccelMethod" #
#Option "Backlight" #
#Option "CustomEDID"#
#Option "DRI" #
#Option "Present" # []
#Option "ColorKey" #
#Option "VideoKey" #
#Option "Tiling"# []
#Option "LinearFramebuffer" # []
#Option "HWRotation"# []
#Option "VSync" # []
#Option "PageFlip" # []
#Option "SwapbuffersWait" # []
#Option "TripleBuffer" # []
#Option "XvPreferOverlay" # []
#Option "HotPlug" # []
#Option "ReprobeOutputs"# []
#Option "XvMC" # []
#Option "ZaphodHeads" #
#Option "VirtualHeads" #
#Option "TearFree" # []
#Option "PerCrtcPixmaps"# []
#Option "FallbackDebug" # []
#Option "DebugFlushBatches" # []
#Option "DebugFlushCaches" # []
#Option "DebugWait" # []
#Option "BufferCache" # []
Identifier "Card0"
Driver "intel"
BusID "PCI:0:2:0"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor"Monitor0"
SubSection "Display"
Viewport 0 0
Depth 1
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
Contents of /etc/X11/xorg.conf.d:
-
total 0
/etc/modprobe.d contains no
Bug#1059781: xwayland: Xwayland.desktop is broken: it contains Type=Application, but no Exec key/value pair.
Control: reassign -1 i3-wm On Sun, Dec 31, 2023 at 07:18:51PM -0800, Francois Marier wrote: > Whenever I start dmenu, I get the following message in my logs: > > File /usr/share/applications/org.freedesktop.Xwayland.desktop is broken: > it contains Type=Application, but no Exec key/value pair. at > /usr/bin/i3-dmenu-desktop line 256. It would appear dmenu needs to implement better support for .desktop files. Reassigning to the package shipping i3-dmenu-desktop. Chris
Bug#1057945: xorg-server: use udev.pc to place udev rules
Source: xorg-server Version: 21.1.9-1 Severity: normal Tags: patch User: helm...@debian.org Usertags: dep17m2 Dear Maintainer, your package installs files related to udev, into /lib. These files need to be moved to /usr/lib as part of Debian's usr-merge effort [1]. Attached you will find a patch to delegate the exact placement of the udev files to udev.pc (using pkg-config). This works today in unstable and also for bookworm. Once udev.pc in unstable points to /usr/lib your package will benefit automatically after a binNMU or any other upload. If during the trixie cycle your package will undergo structural changes or any other file moves, please see the wiki and upload to experimental first when these changes are done. Later during the trixie cycle I expect this bug class to raise in priority. Thank you for considering, Chris [1] https://wiki.debian.org/UsrMerge diff -u xorg-server-21.1.9/debian/changelog xorg-server-21.1.9/debian/changelog --- xorg-server-21.1.9/debian/changelog +++ xorg-server-21.1.9/debian/changelog @@ -1,3 +1,10 @@ +xorg-server (2:21.1.9-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Use udev.pc to place udev files. (Closes: #-1) + + -- Chris Hofstaedtler Sun, 10 Dec 2023 20:49:20 +0100 + xorg-server (2:21.1.9-1) unstable; urgency=medium * New upstream release. diff -u xorg-server-21.1.9/debian/control xorg-server-21.1.9/debian/control --- xorg-server-21.1.9/debian/control +++ xorg-server-21.1.9/debian/control @@ -73,6 +73,7 @@ libdbus-1-dev (>= 1.0) [linux-any], # systemd-daemon libsystemd-dev [linux-any], + systemd-dev [linux-any], Build-Depends-Indep: xz-utils Standards-Version: 3.9.8 Rules-Requires-Root: binary-targets diff -u xorg-server-21.1.9/debian/rules xorg-server-21.1.9/debian/rules --- xorg-server-21.1.9/debian/rules +++ xorg-server-21.1.9/debian/rules @@ -4,6 +4,10 @@ include /usr/share/dpkg/architecture.mk +ifeq ($(DEB_HOST_ARCH_OS), linux) +deb_udevdir = $(shell pkg-config --variable=udevdir udev) +endif + %: dh $@ --with quilt @@ -129,10 +133,10 @@ install -m 755 -d debian/xserver-xorg-core/usr/share/bug/xserver-xorg-core install -m 755 debian/xserver-xorg-core.bug.script debian/xserver-xorg-core/usr/share/bug/xserver-xorg-core/script ifeq ($(DEB_HOST_ARCH_OS), linux) - install -d debian/xserver-xorg-core/lib/udev/rules.d - install -m 644 debian/local/64-xorg-xkb.rules debian/xserver-xorg-core/lib/udev/rules.d - install -d debian/xserver-xorg-core-udeb/lib/udev/rules.d - install -m 644 debian/local/64-xorg-xkb.rules debian/xserver-xorg-core-udeb/lib/udev/rules.d + install -d debian/xserver-xorg-core$(deb_udevdir)/rules.d + install -m 644 debian/local/64-xorg-xkb.rules debian/xserver-xorg-core$(deb_udevdir)/rules.d + install -d debian/xserver-xorg-core-udeb$(deb_udevdir)/rules.d + install -m 644 debian/local/64-xorg-xkb.rules debian/xserver-xorg-core-udeb$(deb_udevdir)/rules.d endif override_dh_missing-indep:
Bug#1057195: mesa: Colours are too dark due to bad sRGB conversion
Source: mesa Version: 23.2.1-1 Severity: normal Tags: upstream Dear Maintainer, I have been debugging a problem that appears in Kitty, the terminal emulator. It uses OpenGL directly, and its windows/buffers use sRGB colour space. The issue is that colours are too dark; black and white are correct but the colours in between are off. It appears as though the sRGB mapping is applied twice. Please see my upstream bug for some discussion and screenshots that display the problem: https://github.com/kovidgoyal/kitty/issues/6845 The issue is immediately apparent when selecting a colour theme. My enviconrment is: - Debian Testing - Kitty 0.31.0 (from testing) - Wayland - Running in a Parallels VM on macOS (currently 14.2 Beta 23C5055b) with GPU acceleration enabled. If I use an older version of Kitty which doesn't use sRGB, or hack Kitty to not perform the sRGB colour conversion, the display is fine. It's as though the driver doesn't actually do the conversion when it should. The colours are also fine if I disable GPU acceleration, but clearly performance is very poor. Kitty is the only program so far that I've been able to replicate the problem with. It doesn't happen in the desktop, using Chromium or Firefox, or simple tools like glxgears. If you can suggest a program that uses sRGB colourspace output I'd be happy to test with that. Kitty also runs fine under macOS natively, so I don't think it can be a macOS platform/driver bug, but potentially could be something in Parallels I guess. I have tagged this bug 'upstream' and will attempt to create the issue in the Freedesktop GitLab later; I'll update this bug if I succeed. Cheers, Chris -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing') Architecture: arm64 (aarch64) Foreign Architectures: amd64 Kernel: Linux 6.5.0-4-arm64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- glxinfo: name of display: :0 display: :0 screen: 0 direct rendering: Yes server glx vendor string: SGI server glx version string: 1.4 server glx extensions: GLX_ARB_context_flush_control, GLX_ARB_create_context, GLX_ARB_create_context_no_error, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, GLX_EXT_get_drawable_type, GLX_EXT_libglvnd, GLX_EXT_no_config_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_copy_sub_buffer, GLX_OML_swap_method, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read client glx vendor string: Mesa Project and SGI client glx version string: 1.4 client glx extensions: GLX_ARB_context_flush_control, GLX_ARB_create_context, GLX_ARB_create_context_no_error, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_ATI_pixel_format_float, GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_no_config_context, GLX_EXT_swap_control, GLX_EXT_swap_control_tear, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_MESA_query_renderer, GLX_MESA_swap_control, GLX_NV_float_buffer, GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync GLX version: 1.4 GLX extensions: GLX_ARB_context_flush_control, GLX_ARB_create_context, GLX_ARB_create_context_no_error, GLX_ARB_create_context_profile, GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, GLX_EXT_no_config_context, GLX_EXT_swap_control, GLX_EXT_swap_control_tear, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_copy_sub_buffer, GLX_MESA_query_renderer, GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group,
Bug#1039970: xserver-xorg-video-amdgpu debian patch downgrades ChangeLog
Package: xserver-xorg-video-amdgpu Version: 23.0.0-1 Small issue but I noticed that `apt-get source xserver-xorg-video-amdgpu` applies a patch (xserver-xorg-video-amdgpu_23.0.0-1.diff.gz) which downgrades the original ChangeLog from 23.0.0 to 19.1.0, e.g.: +++ xserver-xorg-video-amdgpu-23.0.0/ChangeLog @@ -1,697 +1,3 @@ -commit 7025aefcdf9673665588cf291c5d71beb39cce89 -Author: Shashank Sharma -Date: Wed Feb 22 18:00:23 2023 +0100 - -Bump version for the 23.0.0 release - -This release includes some bug fixes. - -Signed-off-by: Shashank Sharma - ... After the patch, is applied: $ head -n5 ChangeLog commit b467d2569a003da05ad222b0dc095bee5eec450a Author: Michel Dänzer Date: Fri Oct 11 17:10:10 2019 +0200 Bump version for the 19.1.0 release
Bug#1006605: xserver-xorg-video-radeon: on login; any desktop which has screen orientation saved as portrait logs out
Package: xserver-xorg-video-radeon Version: 1:19.1.0-2+b1 Severity: important X-Debbugs-Cc: guiv...@ubuntu.com Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Updates that led to this issue are Start-Date: 2022-02-24 22:36:20 Commandline: apt full-upgrade Requested-By: guiverc (1000) Install: xcvt:amd64 (0.1.1-3, automatic) Upgrade: xserver-xorg-video-nouveau:amd64 (1:1.0.17-1, 1:1.0.17-2), xserver- xorg-video-amdgpu:amd/rad64 (21.0.0-2, 21.0.0-2+b1), xserver-xorg-core:amd64 (2:1.20.14-1, 2:21.1.3-2+b1), xserver-xorg-video-intel:amd64 (2:2.99.917+git20200714-2, 2:2.99.917+git20210115-1), xserver-xorg-video- vesa:amd64 (1:2.5.0-1, 1:2.5.0-1+b1), xserver-xorg-legacy:amd64 (2:1.20.14-1, 2:21.1.3-2+b1), xserver-common:amd64 (2:1.20.14-1, 2:21.1.3-2), xserver-xorg- video-radeon:amd64 (1:19.1.0-2, 1:19.1.0-2+b1), xserver-xorg-video-vmware:amd64 (1:13.3.0-3, 1:13.3.0-3+b1), xserver-xorg-input-libinput:amd64 (1.2.0-1, 1.2.1-1+b1), xserver-xephyr:amd64 (2:1.20.14-1, 2:21.1.3-2+b1), xserver-xorg- video-ati:amd64 (1:19.1.0-2, 1:19.1.0-2+b1), xserver-xorg-video-fbdev:amd64 (1:0.5.0-1, 1:0.5.0-2), xserver-xorg-video-qxl:amd64 (0.1.5+git20200331-1, 0.1.5+git20200331-2) End-Date: 2022-02-24 22:36:41 Issue occurred on next login (the following day) * What exactly did you do (or not do) that was effective (or ineffective)? My system has multiple desktops installed & any that have a default config that matches my setup (landscape+portrait) allow screens to go black, cursor to draw then logout without message; this includes LXQt, Xfce, ... * What was the outcome of this action? Machine cannot be used by any installed desktop that had my screen orientation saved. * What outcome did you expect instead? Normal behavior - login gets my desktop drawn & allows me to use it. I've altered this GNOME to return to defaults so I have one display readable (other is orientated wrongly as it's sideways; setup is landscape as that works but monitor is portrait..) LXDE still logs in, but it didn't have screen orientation configured; however if I run the script xrandr --output HDMI-0 --mode 1280x1024 --pos 1280x0 --rotate left --output DVI-0 --primary --mode 1280x1024 --pos 0x0 --rotate normal --output VGA-0 --off which adjusts display to match my setup - instant logout !! In `sudo journalctl` I see the following when I run the `xrandr` command I just mentioned; I see equivalent on login via Xfce/LXQt/.. too; but I've copy/pasted from a LXDE session where I ran the `xrand` command Feb 28 20:31:48 dc780-deb kernel: [ cut here ] Feb 28 20:31:48 dc780-deb kernel: WARNING: CPU: 0 PID: 833 at drivers/gpu/drm/ttm/ttm_bo.c:411 ttm_bo_release+0x384/0x3b0 [ttm] Feb 28 20:31:48 dc780-deb kernel: Modules linked in: bnep snd_seq_dummy snd_hrtimer snd_seq snd_seq_device nfsv3 nfs_acl rpcsec_gss_krb5 auth_rpcgss nfsv4 dns_resolver nfs lockd grace fscac> Feb 28 20:31:48 dc780-deb kernel: libcrc32c crc32c_generic amdgpu gpu_sched hid_generic usbhid hid sd_mod t10_pi uas crc_t10dif crct10dif_generic usb_storage sr_mod cdrom crct10dif_common > Feb 28 20:31:48 dc780-deb kernel: CPU: 0 PID: 833 Comm: Xorg Not tainted 5.16.0-1-amd64 #1 Debian 5.16.7-2 Feb 28 20:31:48 dc780-deb kernel: Hardware name: Dell Inc. OptiPlex 780 /0200DY, BIOS A03 02/13/2010 Feb 28 20:31:48 dc780-deb kernel: RIP: 0010:ttm_bo_release+0x384/0x3b0 [ttm] Feb 28 20:31:48 dc780-deb kernel: Code: 00 e8 50 ca 8a f2 48 8b 43 e8 eb a8 be 03 00 00 00 e8 f0 51 6c f2 e9 6f fd ff ff e8 c6 a7 8a f2 e9 65 fd ff ff 48 89 e8 eb 8a <0f> 0b e9 af fc ff ff > Feb 28 20:31:48 dc780-deb kernel: RSP: 0018:b47d40dabdf0 EFLAGS: 00010202 Feb 28 20:31:48 dc780-deb kernel: RAX: RBX: 921c063f3dd8 RCX: Feb 28 20:31:48 dc780-deb kernel: RDX: 0002 RSI: b374e32e RDI: 921c063f3dd8 Feb 28 20:31:48 dc780-deb kernel: RBP: 921c00b846f0 R08: 921c063f3dd8 R09: 0064 Feb 28 20:31:48 dc780-deb kernel: R10: 0010 R11: 921c04a98b68 R12: 921c063f3c78 Feb 28 20:31:48 dc780-deb kernel: R13: 921d2ffbf560 R14: 921c04699780 R15: Feb 28 20:31:48 dc780-deb kernel: FS: 7f1b35623ec0() GS:921d2fe0() knlGS: Feb 28 20:31:48 dc780-deb kernel: CS: 0010 DS: ES: CR0: 80050033 Feb 28 20:31:48 dc780-deb kernel: CR2: 7f89dea28a30 CR3: 0001159c CR4: 000406f0 Feb 28 20:31:48 dc780-deb kernel: Call Trace: Feb 28 20:31:48 dc780-deb kernel: Feb 28 20:31:48 dc780-deb kernel: ? __inode_wait_for_writeback+0x7e/0xe0 Feb 28 20:31:48 dc780-deb kernel: ? fsnotify_grab_connector+0x49/0x80 Feb 28 20:31:48 dc780-deb kernel: radeon_bo_unref+0x1a/0x30 [radeon] Feb 28 20:31:48 dc780-deb kernel: radeon_gem_object_free+0x30/0x50 [radeon] Feb 28 20:31:48 dc780-deb kernel: drm_gem_dmabuf_release+0x36/0x50 [drm] Feb 28 20:3
Bug#1004689: Bug #1004689: xterm: CVE-2022-24130
Just curious why this bug is marked high priority for stretch but low priority for buster and bullseye? https://tracker.debian.org/pkg/xterm Is there something different in their builds? Thanks, - Chris
Bug#998386: Bug #998386 Plasma gets very slow when compositor is disabled on bare metal
Mesa 21.2.5-1, today release in debian testing shows the same problem.
Bug#998386: Bug #998386 Plasma gets very slow when compositor is disabled on bare metal
Hi Norbert, > But I guess you had, or some cosmic radiation induced bit switch did it > for you on your hard disk ;-) The default for all installations is being > on. yeah, then lets say "maybe" or "probably" I did that, nevertheless, at least it was a couple of years ago and I cannot remeber ;-) > > In my similar kvm virtualized installtion the switch also is/was off, > > but there it seems to make no problems, even after a couple of changes and > > restartings. > > Hmm, that is indeed strange, though. > > I suggest that *you* create a bug report at upstream (I guess kwin?) > because I cannot reproduce it on my systems (AMD based), and upstream > devs will need detailed informations. Ok, just did that now as suggested, see https://bugs.kde.org/show_bug.cgi?id=444940 Best, Chris
Bug#998386: Bug#996670: libkdecorations2-5v5 migrated to testing too early breaking Plasma
Hi Norbert, thanks to your repsonse! > Can you try/check the following: > * In the Plasma Settings app, go to > Display and Monitor > Compositor > and check whether > Enable compositor on startup > is selected (on). Indeed, turning that switch to on and restarting helps. Great!!! I cannot remeber that I ever turned it on or off. However, if I turn it back to off, then the problems come back (immedeiately). So at least the latter seems to be a bug, right? (Personally I would not need any 3d effects). In my similar kvm virtualized installtion the switch also is/was off, but there it seems to make no problems, even after a couple of changes and restartings. > Also the rendering backend etc is an important information. Same on bare metal and in vm: skaling method: exact redering backend: OpenGL 3.1 latency: Balance of latency and smoothness tearing: automatic holding available window preview images: only for visible windows allow applications to block compositing: enabled > If the above (after logout/login, or better reboot) does not help: > * Is the behaviour reproducible with a **clean** **new** user? Yes, as turning on Enable compositor on startup immediately helped, I did not try that. Chris
Bug#998386: mesa 21.2.4-1 makes graphical desktop (plasma) unusable
Unfortunately, mesa 21.2.4-1 shows the same problem under plasma 5.23 in testing. The latter has finally migrated to testing with all packages yesterday. The combination works fine within my libvirt vm, as I think, it does not use hw accelleration there. However, on bare metal (see above) it stays unusable exactly as described. (OT: As plasma 5.23 depends on mesa >= 21.2.4 it still can't be used and package upgrades are even more difficult regarding the even larger mass of packes now to distiguish). Chris
Bug#998386: mesa 21.2.4-1 makes graphical desktop (plasma) unusable
Package: mesa Version: 20.3.5-1 Severity: critical Justification: breaks graphical system like KDE After updateing mesa from 20.3.5 to 21.2.4 in bookworm (migrated on October 21th to testing) my graphical KDE plasma 5.21 under x11 renders unusable. Note plasma 5.23 is currently unusable in testing, see, e.g., bug #996670. There are many more or less longer horizontal lines flying around, and changes of content, like typing text within a terminal, makes just written characters unreadable. The system is very slow to redraw the characters afterwards. Highlighting of elements like menus is slow and ugly. My System is a Core i7-6700 system with integrated CPU grahics Intel HD Graphics 530 rev 06. The login manager sddm works with both versions as desired, as (I believe) it does not use mesa. Hotfix: dowgrade all installed mesa packages to 21.2.4 Thanks fpr looking into it, Chris
Bug#995809: libinput: please make the build reproducible
Source: libinput
Version: 1.19.1-1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: buildpath
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
Hi,
Whilst working on the Reproducible Builds effort [0] we noticed that
libinput could not be built reproducibly.
This is due to the use of the LIBINPUT_QUIRKS_DIR macro which includes
the absolute build path.
It is not entirely clear (during a very brief look) when/where this
value is even used — the testsuite still passes even if this is set to
a dummy value (see attached dummy patch). And, of course, the build
path cannot be relied upon at runtime.
[0] https://reproducible-builds.org/
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
--- a/debian/patches/0001-reproducible-build.patch 1970-01-01
01:00:00.0 +0100
--- b/debian/patches/0001-reproducible-build.patch 2021-10-06
10:05:03.555141278 +0100
@@ -0,0 +1,15 @@
+Description: Make the build reproducible
+Author: Chris Lamb
+Last-Update: 2021-10-06
+
+--- libinput-1.19.1.orig/meson.build
libinput-1.19.1/meson.build
+@@ -13,7 +13,7 @@ dir_libexec = get_option('prefix') /
+ dir_lib = get_option('prefix') / get_option('libdir')
+ dir_man1= get_option('prefix') / get_option('mandir') / 'man1'
+ dir_system_udev = get_option('prefix') / 'lib' / 'udev'
+-dir_src_quirks = meson.current_source_dir() / 'quirks'
++dir_src_quirks = '/nonexistent'
+ dir_src_test= meson.current_source_dir() / 'test'
+ dir_src = meson.current_source_dir() / 'src'
+
--- a/debian/patches/series 2021-10-06 09:35:40.889907597 +0100
--- b/debian/patches/series 2021-10-06 10:00:57.178902346 +0100
@@ -1 +1,2 @@
#placeholder
+0001-reproducible-build.patch
Bug#992773: spirv-cross: please make the build reproducible
Source: spirv-cross
Version: 2021.01.15-2
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
Hi,
Whilst working on the Reproducible Builds effort [0] we noticed that
spirv-cross could not be built reproducibly.
This is because it embeds a timestamp via CMake. As the timestamp is
not very useful in this particular context (it is positioned next to
an "unknown" Git commit), a patch is attached that simply replaces
the entire thing with a string that denotes that the binary is from
the Debian package.
[0] https://reproducible-builds.org/
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
--- a/debian/patches/0001-reproducible-build.patch 1970-01-01
01:00:00.0 +0100
--- b/debian/patches/0001-reproducible-build.patch 2021-08-23
09:23:00.567312730 +0100
@@ -0,0 +1,14 @@
+Description: Make the build reproducible
+Author: Chris Lamb
+Last-Update: 2021-08-23
+
+--- spirv-cross-2021.01.15.orig/cmake/gitversion.in.h
spirv-cross-2021.01.15/cmake/gitversion.in.h
+@@ -1,6 +1,6 @@
+ #ifndef SPIRV_CROSS_GIT_VERSION_H_
+ #define SPIRV_CROSS_GIT_VERSION_H_
+
+-#define SPIRV_CROSS_GIT_REVISION "Git commit: @spirv-cross-build-version@
Timestamp: @spirv-cross-timestamp@"
++#define SPIRV_CROSS_GIT_REVISION "(Debian package)"
+
+ #endif
--- a/debian/patches/series 1970-01-01 01:00:00.0 +0100
--- b/debian/patches/series 2021-08-23 09:22:59.659300774 +0100
@@ -0,0 +1 @@
+0001-reproducible-build.patch
Bug#951988: libplacebo: FTBFS: (.text+0x8ee): undefined reference to `spvContextCreate'
Hello Timo, * Paul Gevers : > On Thu, 18 Feb 2021 10:26:44 + Simon McVittie wrote: > > On Mon, 18 Jan 2021 at 11:27:35 +, Simon McVittie wrote: > > https://salsa.debian.org/xorg-team/vulkan/glslang/-/merge_requests/4 > > > > (Updated patches attached, if you prefer the BTS.) > > Can we move this issue forward somehow? What are the risks of the > proposed patch? Without having knowledge of how pkg-config works, the > patch looks rather harmless to me if it fixes the issue at stake. You have merged the mentioned MR on salsa. Do you plan on uploading a package with this change (soon)? Chris
Bug#948346: [PATCH] Ensure graceful signal handling when the pid file exists
* Eduard Bloch [210208 00:43]: > > Could you make an upload to DELAYED instead of further waiting? > > I am no longer waiting, today is timeout day. Will use 7-DAY DELAYED > queue, should be appropriate. That upload somehow did not make it into the archive? Chris
Bug#928380: libxcb-xinput-dev: Breaks with libxcb1-dev 1.12-1
On Tue, Feb 2, 2021 at 8:20 PM Julien Cristau wrote: > > Control: tag -1 moreinfo > > On Fri, May 03, 2019 at 08:40:03PM +1000, Chris Angelico wrote: > > Package: libxcb-xinput-dev > > Version: 1.13.1-2 > > Severity: important > > > > Dear Maintainer, > > > > Having the Debian Unstable repository available (even with a low priority) > > causes > > libxcb-xinput-dev to be installable, but leaves the older libxcb1-dev from > > Debian > > Stable. This results in compilation errors from any app that attempts to > > #include > > the xinput headers, due to a version incompatibility. > > > > The solution is to uninstall libxcb-xinput-dev, or to migrate far more > > packages > > to the newer version (including upgrading libc). > > > > The problem appears to be a simple packaging issue, where the dependency is > > shown > > as simply "libxcb1-dev" with no version information attached. If it > > declared that > > it required libxcb1-dev version 1.13.1-2, this would inform apt correctly. > > > Can you provide more details about the errors you were seeing? > >From two years ago? I don't think I have any systems running that, any more. ChrisA
Bug#945105: intel-gpu-tools: please make the build reproducible
Chris Lamb wrote: > [..] Friendly ping on this? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#974208: xserver-xorg-core: Fix crash on XkbSetMap
Package: xserver-xorg-core Version: 2:1.20.4-1+deb10u1 Just reporting an upstream patch for an xserver crash related to xkb: See the patch here: https://gitlab.freedesktop.org/xorg/xserver/-/commit/fabc4219622f3c0b41 It does not appear to be in the debian buster sources yet, nor do I see any reference to it in existing bugs. I noticed it being discussed in the wild, so reporting it here. See: https://unix.stackexchange.com/a/574285 - Chris
Bug#945105: intel-gpu-tools: please make the build reproducible
Dear Maintainer, > Source: intel-gpu-tools > Version: 1.2-1 > Tags: patch There hasn't seem to be any update on this bug in 294 days, in which time the Reproducible Builds effort has come on a long way. Would you consider applying this patch and uploading? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#945105: intel-gpu-tools: please make the build reproducible
Dear Maintainer, > Source: intel-gpu-tools > Version: 1.2-1 > Tags: patch There hasn't seem to be any update on this bug in 294 days, in which time the Reproducible Builds effort has come on a long way. Would you consider applying this patch and uploading? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#909782: libinput: please make the build reproducible
Hi Julien, > The patch doesn't seem quite right, so I don't think we should apply it > as-is. It seems to me LIBINPUT_QUIRKS_SRCDIR shouldn't be in the > shipped packages at all, so a patch that fixes that and can be sent > upstream would be better. I would agree. I blame "2018 lamby" for his shortsightedness. Hopefully someone can step up and write/submit this patch. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org 🍥 chris-lamb.co.uk `-
Bug#909782: libinput: please make the build reproducible
Dear Maintainer, > Source: libinput > Version: 1.12.6-2+deb10u1 > Tags: patch There hasn't seem to be any update on this bug in 703 days, in which time the Reproducible Builds effort has come on a long way. Would you consider applying this patch and uploading? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Re: Bug#966004: bugs.debian.org: .XCompose fails to make long substitutions
Control: reassign -1 libx11-6 XCompose appears to be a libX11 feature, reassigning there. Best, Chris
Bug#945105: intel-gpu-tools: please make the build reproducible
Source: intel-gpu-tools
Version: 1.24-1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: buildpath
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
Hi,
Whilst working on the Reproducible Builds effort [0] we noticed that
intel-gpu-tools could not be built reproducibly.
This is because it embedded the path to the test directory in the
binary. As we don't even build the tests (according to a comments,
they FTBFS...) my attached patch is almost-certainly harmless.
Patch attached.
[0] https://reproducible-builds.org/
Best wishes,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
--- a/debian/patches/0001_Reproducible-builds.patch 1969-12-31
19:00:00.0 -0500
--- b/debian/patches/0001_Reproducible-builds.patch 2019-11-19
12:58:31.782550136 -0500
@@ -0,0 +1,15 @@
+Description: Make the build reproducible
+Author: Chris Lamb
+Last-Update: 2019-11-19
+
+--- intel-gpu-tools-1.24.orig/lib/meson.build
intel-gpu-tools-1.24/lib/meson.build
+@@ -112,7 +112,7 @@ if chamelium.found()
+ lib_sources += 'igt_chamelium_stream.c'
+ endif
+
+-srcdir = join_paths(meson.source_root(), 'tests')
++srcdir = join_paths('.', 'tests')
+
+ lib_version = vcs_tag(input : 'version.h.in', output : 'version.h',
+ fallback : 'NO-GIT',
--- a/debian/patches/series 2019-11-19 10:28:42.584479614 -0500
--- b/debian/patches/series 2019-11-19 12:34:03.769612335 -0500
@@ -1 +1,2 @@
#placeholder
+0001_Reproducible-builds.patch
Bug#928380: libxcb-xinput-dev: Breaks with libxcb1-dev 1.12-1
Package: libxcb-xinput-dev Version: 1.13.1-2 Severity: important Dear Maintainer, Having the Debian Unstable repository available (even with a low priority) causes libxcb-xinput-dev to be installable, but leaves the older libxcb1-dev from Debian Stable. This results in compilation errors from any app that attempts to #include the xinput headers, due to a version incompatibility. The solution is to uninstall libxcb-xinput-dev, or to migrate far more packages to the newer version (including upgrading libc). The problem appears to be a simple packaging issue, where the dependency is shown as simply "libxcb1-dev" with no version information attached. If it declared that it required libxcb1-dev version 1.13.1-2, this would inform apt correctly. -- System Information: Debian Release: 9.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (50, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-8-amd64 (SMP w/8 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en_AU:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libxcb-xinput-dev depends on: pn libxcb-xinput0 ii libxcb1-dev 1.12-1 libxcb-xinput-dev recommends no packages. libxcb-xinput-dev suggests no packages.
Bug#909782: libinput: please make the build reproducible
Source: libinput
Version: 1.12.0-1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: buildpath
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
Hi,
Whilst working on the Reproducible Builds effort [0], we noticed
that libinput could not be built reproducibly.
This is due to the LIBINPUT_QUIRKS_SRCDIR config.h variable including
the absolute build path to find the test-time input file.
Patch attached that uses a relative path instead. I'm not sure upstream
will like this patch, it is provided mostly as a demonstration
ofthe problem. However perhaps it could be modified to take an
environment variable instead? I will leave this with you.
[0] https://reproducible-builds.org/
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
--- a/debian/patches/reproducible-build.patch 1970-01-01 01:00:00.0
+0100
--- b/debian/patches/reproducible-build.patch 2018-09-28 09:19:11.556126306
+0100
@@ -0,0 +1,15 @@
+Description: Make the build reproducible
+Author: Chris Lamb
+Last-Update: 2018-09-28
+
+--- libinput-1.12.0.orig/meson.build
libinput-1.12.0/meson.build
+@@ -12,7 +12,7 @@ dir_libexec = join_paths(get_option(
+ dir_lib = join_paths(get_option('prefix'), get_option('libdir'))
+ dir_man1= join_paths(get_option('prefix'), get_option('mandir'),
'man1')
+ dir_system_udev = join_paths(get_option('prefix'), 'lib', 'udev')
+-dir_src_quirks = join_paths(meson.source_root(), 'quirks')
++dir_src_quirks = '../quirks'
+ dir_src_test= join_paths(meson.source_root(), 'test')
+ dir_src = join_paths(meson.source_root(), 'src')
+
--- a/debian/patches/series 1970-01-01 01:00:00.0 +0100
--- b/debian/patches/series 2018-09-28 09:18:30.095886370 +0100
@@ -0,0 +1 @@
+reproducible-build.patch
Bug#906012: libxcursor: CVE-2015-9262
block 906012 by 906042 thanks Hi, > Looks fine, please upload to security-master: As discussed elsewhere we will not be doing a DSA for this. I've filed an s-p-u request as https://bugs.debian.org/906042. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#906012: libxcursor: CVE-2015-9262
Hi security team,
> libxcursor: CVE-2015-9262
I have prepared an update for stretch:
libxcursor (1:1.1.14-1+deb9u2) stretch-security; urgency=high
* Non-maintainer upload by the Security Team.
* Fix a denial of service or potentially code execution via
a one-byte heap overflow. (CVE-2015-9262) Closes: #906012)
-- Chris Lamb Mon, 13 Aug 2018 09:09:13 +0200
Full debdiff attached. Permission to upload to stretch-security?
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
diffstat for libxcursor_1.1.14-1+deb9u1 libxcursor_1.1.14-1+deb9u2
debian/patches/CVE-2015-9262.patch | 23 +++
libxcursor-1.1.14/debian/changelog |8
libxcursor-1.1.14/debian/patches/series |1 +
3 files changed, 32 insertions(+)
diff -u libxcursor-1.1.14/debian/changelog libxcursor-1.1.14/debian/changelog
--- libxcursor-1.1.14/debian/changelog
+++ libxcursor-1.1.14/debian/changelog
@@ -1,3 +1,11 @@
+libxcursor (1:1.1.14-1+deb9u2) stretch-security; urgency=high
+
+ * Non-maintainer upload by the Security Team.
+ * Fix a denial of service or potentially code execution via
+a one-byte heap overflow. (CVE-2015-9262) Closes: #906012)
+
+ -- Chris Lamb Mon, 13 Aug 2018 09:09:13 +0200
+
libxcursor (1:1.1.14-1+deb9u1) stretch-security; urgency=high
* Non-maintainer upload by the Security Team.
diff -u libxcursor-1.1.14/debian/patches/series
libxcursor-1.1.14/debian/patches/series
--- libxcursor-1.1.14/debian/patches/series
+++ libxcursor-1.1.14/debian/patches/series
@@ -1 +1,2 @@
+CVE-2015-9262.patch
Fix-heap-overflows-when-parsing-malicious-files.-CVE.patch
only in patch2:
unchanged:
--- libxcursor-1.1.14.orig/debian/patches/CVE-2015-9262.patch
+++ libxcursor-1.1.14/debian/patches/CVE-2015-9262.patch
@@ -0,0 +1,23 @@
+commit 897213f36baf6926daf6d192c709cf627aa5fd05
+Author: shubham shrivastav
+Date: Fri Jun 5 13:36:22 2015 -0700
+
+Insufficient memory for terminating null of string in _XcursorThemeInherits
+
+Fix does one byte of memory allocation for null termination of string.
+https://bugs.freedesktop.org/show_bug.cgi?id=90857
+
+Reviewed-by: Keith Packard
+Signed-off-by: Alan Coopersmith
+
+--- libxcursor-1.1.14.orig/src/library.c
libxcursor-1.1.14/src/library.c
+@@ -180,7 +180,7 @@ _XcursorThemeInherits (const char *full)
+ if (*l != '=') continue;
+ l++;
+ while (*l == ' ') l++;
+- result = malloc (strlen (l));
++ result = malloc (strlen (l) + 1);
+ if (result)
+ {
+ r = result;
Bug#906012: libxcursor: CVE-2015-9262
Package: libxcursor
Version: 1:1.1.14-1+deb8u1
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security
Hi,
The following vulnerability was published for libxcursor.
CVE-2015-9262[0]:
| _XcursorThemeInherits in library.c in libXcursor before 1.1.15 allows
| remote attackers to cause denial of service or potentially code
| execution via a one-byte heap overflow.
If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.
For further information see:
[0] https://security-tracker.debian.org/tracker/CVE-2015-9262
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-9262
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
Re: spirv-headers_0+git20180201.ce3092-1_amd64.changes is NEW
Hi Timo, > What's the status of this? It's a very simple package and is still > blocking further work on splitting src:vulkan. Simply was in the queue. I have processed it now (ACCEPTED with an RC bug.) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#899358: weston: please make the build reproducible
Source: weston Version: 3.0.0-1 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: buildpaths X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org Hi, Whilst working on the Reproducible Builds effort [0], we noticed that weston could not be built reproducibly. This is because it uses the build path in the final binary package (which is then broken anyway). Patch attached that uses @libexecdir@, which is where file lives at runtime. :) [0] https://reproducible-builds.org/ Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- --- a/weston.ini.in 2018-05-23 09:48:06.036427787 +0100 --- b/weston.ini.in 2018-05-23 09:59:25.581499358 +0100 @@ -38,7 +38,7 @@ [launcher] icon=/usr/share/icons/gnome/24x24/apps/arts.png -path=@abs_top_builddir@/weston-flower +path=@libexecdir@/weston-flower [input-method] path=@libexecdir@/weston-keyboard
Bug#897362: wayland: Incomplete debian/copyright?
Hi Jeremy, > This bug is blocking other packages (for instance, the webkit2gtk > security update for Testing and backports) and is probably not a new > issue so let's let wayland migrate. WFM, but naturally would be nice to see this addressed soonish :) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#897362: wayland: Incomplete debian/copyright?
Source: wayland Version: 1.15.0-1 Severity: serious Justication: Policy 12.5 X-Debbugs-CC: Timo Aaltonen Hi, I just ACCEPTed wayland from NEW but noticed it was missing attribution in debian/copyright for at least Yong Bakos, Giulio Camuffo, Samsung, Marek Chalupa, etc. This is in no way exhaustive so please check over the entire package carefully and address these on your next upload. :) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#864349: (no subject)
I also ran into this issue quite often with the linux-lts kernel (less so with the latest kernel). Here is some output from journalctl: Apr 25 12:48:08 archamd kernel: nouveau :0a:00.0: fifo: write fault at 068000 engine 07 [HOST0] client 07 [HOST_CPU] reason 02 [PTE] on channel 2 [003fa53000 systemd-logind[397]] Apr 25 12:48:08 archamd kernel: nouveau :0a:00.0: fifo: channel 2: killed Apr 25 12:48:08 archamd kernel: nouveau :0a:00.0: fifo: runlist 0: scheduled for recovery Apr 25 12:48:08 archamd kernel: nouveau :0a:00.0: systemd-logind[397]: channel 2 killed! Apr 25 12:48:39 archamd kernel: WARNING: CPU: 2 PID: 4300 at drivers/gpu/drm/nouveau/nouveau_drm.c:120 nouveau_cli_work_flush+0x130/0x140 [nouveau] Apr 25 12:48:39 archamd kernel: Modules linked in: fuse xt_nat xt_tcpudp veth ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_conntrack> Apr 25 12:48:39 archamd kernel: drm_kms_helper snd_hda_core snd_hwdep aesni_intel snd_pcm drm aes_x86_64 crypto_simd glue_helper cryptd pcspkr agpgart snd_timer syscopyarea sysfillrect sysim> Apr 25 12:48:39 archamd kernel: CPU: 2 PID: 4300 Comm: disk_cache:0 Tainted: G O 4.15.12-1-ARCH #1 Apr 25 12:48:39 archamd kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./AB350M-HDV, BIOS P3.20 08/30/2017 Apr 25 12:48:39 archamd kernel: RIP: 0010:nouveau_cli_work_flush+0x130/0x140 [nouveau] Apr 25 12:48:39 archamd kernel: RSP: 0018:a3638a1b7bd0 EFLAGS: 00010246 Apr 25 12:48:39 archamd kernel: RAX: RBX: 8edbc2d62a20 RCX: Apr 25 12:48:39 archamd kernel: RDX: 8001 RSI: 0282 RDI: Apr 25 12:48:39 archamd kernel: RBP: 8edb94429618 R08: 0d7ba3b4bc00 R09: 8ed9e906bb00 Apr 25 12:48:39 archamd kernel: R10: R11: 000f4240 R12: dead0200 Apr 25 12:48:39 archamd kernel: R13: dead0100 R14: 8edb94429608 R15: 8edb94429628 Apr 25 12:48:39 archamd kernel: FS: 7ff0f2e74700() GS:8edc9ec8() knlGS: Apr 25 12:48:39 archamd kernel: CS: 0010 DS: ES: CR0: 80050033 Apr 25 12:48:39 archamd kernel: CR2: 7f1ba33f8d74 CR3: 00030537e000 CR4: 003406e0 Apr 25 12:48:39 archamd kernel: Call Trace: Apr 25 12:48:39 archamd kernel: nouveau_cli_fini+0x13/0x70 [nouveau] Apr 25 12:48:39 archamd kernel: nouveau_drm_postclose+0xa5/0xe0 [nouveau] Apr 25 12:48:39 archamd kernel: drm_release+0x264/0x380 [drm] Apr 25 12:48:39 archamd kernel: __fput+0x9d/0x1e0 Apr 25 12:48:39 archamd kernel: task_work_run+0x84/0xa0 Apr 25 12:48:39 archamd kernel: do_exit+0x311/0xb90 Apr 25 12:48:39 archamd kernel: ? __update_load_avg_se.isra.4+0x1b6/0x1c0 Apr 25 12:48:39 archamd kernel: do_group_exit+0x33/0xa0 Apr 25 12:48:39 archamd kernel: get_signal+0x203/0x5d0 Apr 25 12:48:39 archamd kernel: do_signal+0x36/0x610 Apr 25 12:48:39 archamd kernel: ? __schedule+0x24b/0x8c0 Apr 25 12:48:39 archamd kernel: ? do_task_dead+0x3d/0x40 Apr 25 12:48:39 archamd kernel: ? SyS_futex+0x12d/0x180 Apr 25 12:48:39 archamd kernel: exit_to_usermode_loop+0x85/0xa0 Apr 25 12:48:39 archamd kernel: do_syscall_64+0x18a/0x190 Apr 25 12:48:39 archamd kernel: entry_SYSCALL_64_after_hwframe+0x3d/0xa2 Apr 25 12:48:39 archamd kernel: RIP: 0033:0x7ff10c9683bd Apr 25 12:48:39 archamd kernel: RSP: 002b:7ff0f2e73b20 EFLAGS: 0246 ORIG_RAX: 00ca Apr 25 12:48:39 archamd kernel: RAX: fe00 RBX: 1363b9da2b68 RCX: 7ff10c9683bd Apr 25 12:48:39 archamd kernel: RDX: RSI: 0080 RDI: 1363b9da2b90 Apr 25 12:48:39 archamd kernel: RBP: R08: R09: Apr 25 12:48:39 archamd kernel: R10: R11: 0246 R12: Apr 25 12:48:39 archamd kernel: R13: 1363b9da2b40 R14: R15: 1363b9da2b90 Apr 25 12:48:39 archamd kernel: Code: d9 e9 54 ff ff ff 48 83 c4 10 4c 89 ff 5b 5d 41 5c 41 5d 41 5e 41 5f e9 ef ac e2 d9 4c 89 cf e8 e7 f7 c4 d9 4c 8b 4c 24 08 eb be <0f> 0b eb ba 66 90 66 2> Apr 25 12:48:39 archamd kernel: ---[ end trace e78ad2c52f037783 ]--- Apr 25 12:50:07 archamd kernel: kernel tried to execute NX-protected page - exploit attempt? (uid: 1000) Apr 25 12:50:07 archamd kernel: BUG: unable to handle kernel paging request at 8edc8cecf920 Apr 25 12:50:07 archamd kernel: IP: 0x8edc8cecf920 Apr 25 12:50:07 archamd kernel: PGD 2e63a067 P4D 2e63a067 PUD 2e63e067 PMD 30fef9063 PTE 80030cecf163 Apr 25 12:50:07 archamd kernel: Oops: 0011 [#1] PREEMPT SMP NOPTI Apr 25 12:50:07 archamd kernel: Modules linked in: fuse xt_nat xt_tcpudp veth ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_conntrack> Apr 25 12:50:07 archamd kernel: drm_kms_helper snd_hda_core snd_hwdep aesni_intel snd_pcm
Re: xorgproto_2018.4-2_amd64.changes REJECTED
> > Did you even bother to look at the *new* package? The dak interface does not make it immediately obvious that the aforementioend notes were written about a superceded version, so these things sometimes happen. Thank you for your patience and re-uploading, I hope it didn't cause too much delay for you. -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
xorgproto_2018.4-2_amd64.changes REJECTED
(I am "merely" forwarding note below; please add waldi@ in any replies) -- Chris Lamb Wed, 21 Mar 2018 23:50:49 + Author: Bastian Blank Version: 2018.4-1 Timestamp: 2018-03-06 19:36:05.059079+00:00 REJECT Takes over more then ten packages but gives not the slightest hint that this is correct Uses a weird mix of package styles: W: xorgproto source: patch-system-but-direct-changes-in-diff attic/bigreqsproto/docbook.am W: xorgproto source: patch-system-but-direct-changes-in-diff attic/bigreqsproto/specs/Makefile.am W: xorgproto source: patch-system-but-direct-changes-in-diff attic/fontsproto/docbook.am W: xorgproto source: patch-system-but-direct-changes-in-diff attic/fontsproto/specs/Makefile.am === Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new files which address our concerns.
xorgproto_2018.4-1_amd64.changes REJECTED
Version: 2018.4-1 Timestamp: 2018-03-06 19:36:05.059079+00:00 Takes over more then ten packages but gives not the slightest hint that this is correct Uses a weird mix of package styles: W: xorgproto source: patch-system-but-direct-changes-in-diff attic/bigreqsproto/docbook.am W: xorgproto source: patch-system-but-direct-changes-in-diff attic/bigreqsproto/specs/Makefile.am W: xorgproto source: patch-system-but-direct-changes-in-diff attic/fontsproto/docbook.am W: xorgproto source: patch-system-but-direct-changes-in-diff attic/fontsproto/specs/Makefile.am (forwarding notes from wa...@debian.org above; please CC him on replies) -- Chris Lamb Fri, 09 Mar 2018 05:56:46 + === Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new files which address our concerns.
Bug#888211: Apparently not kernel related
Reproduced on: Linux cchiappa-lnx 4.13.0-1-amd64 #1 SMP Debian 4.13.13-1 (2017-11-16) x86_64 GNU/Linux Linux cchiappa-lnx 4.12.0-1-amd64 #1 SMP Debian 4.12.6-1 (2017-08-12) x86_64 GNU/Linux so presumably not kernel related, will investigate downgrading xorg components
Bug#888211: 4.14.2 afflicted
Just had the hang on: Linux cchiappa-lnx 4.14.0-1-amd64 #1 SMP Debian 4.14.2-1 (2017-11-30) x86_64 GNU/Linux (now testing 4.13.13-1)
Bug#888211: xserver-xorg-video-intel: Frequent hangs with kernel 4.14.13-1 and i915 chipset
Package: xserver-xorg-video-intel Version: 2:2.99.917+git20171229-1 Severity: normal On Friday I did an upgrade and have been having frequent hangs since: [Tue Jan 23 16:12:23 2018] i915 :00:02.0: Resetting rcs0 after gpu hang [Tue Jan 23 16:12:26 2018] asynchronous wait on fence i915:Xorg[4666]/1:a36f8 timed out [Tue Jan 23 16:12:26 2018] asynchronous wait on fence i915:Xorg[4666]/1:a36f8 timed out [Tue Jan 23 16:12:31 2018] i915 :00:02.0: Resetting rcs0 after gpu hang [Tue Jan 23 16:12:39 2018] i915 :00:02.0: Resetting rcs0 after gpu hang [Tue Jan 23 16:12:51 2018] i915 :00:02.0: Resetting rcs0 after gpu hang [Tue Jan 23 16:13:01 2018] i915 :00:02.0: Resetting rcs0 after gpu hang After this, X eventually dies and I can restart it. The upgrade definitely moved to linux-image-4.14.0-3-amd64 (probably from linux-image-4.14.0-1-amd64, but maybe earlier?) and might also have upgraded me to 2:2.99.917+git20171229-1 . I don't see any new bugs in the bug system which look like this, but I'm not sure if this is the right package to be reporting against. Google turns up random stuff like https://bugs.archlinux.org/task/55629 and https://unix.stackexchange.com/questions/401746/drm-i915-resetting-chip-after-gpu-hang but they don't seem to correspond to the versions which have induced problems for me. -- 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: -- 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) /etc/X11/xorg.conf does not exist. /etc/X11/xorg.conf.d does not exist. /etc/modprobe.d contains no KMS configuration files. Kernel version (/proc/version): --- Linux version 4.14.0-3-amd64 (debian-ker...@lists.debian.org) (gcc version 7.2.0 (Debian 7.2.0-19)) #1 SMP Debian 4.14.13-1 (2018-01-14) Xorg X server log files on system: -- -rw-r--r-- 1 root root 44951 Jan 23 16:18 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [342836.057] X.Org X Server 1.19.5 Release Date: 2017-10-12 [342836.057] X Protocol Version 11, Revision 0 [342836.057] Build Operating System: Linux 4.9.0-4-amd64 x86_64 Debian [342836.057] Current Operating System: Linux cchiappa-lnx 4.14.0-3-amd64 #1 SMP Debian 4.14.13-1 (2018-01-14) x86_64 [342836.057] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.14.0-3-amd64 root=/dev/mapper/ccora2-root ro quiet [342836.057] Build Date: 16 October 2017 12:28:38PM [342836.057] xorg-server 2:1.19.5-1 (https://www.debian.org/support) [342836.057] Current version of pixman: 0.34.0 [342836.057]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [342836.057] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [342836.057] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Jan 23 16:13:00 2018 [342836.063] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [342836.075] (==) No Layout section. Using the first Screen section. [342836.075] (==) No screen section available. Using defaults. [342836.075] (**) |-->Screen "Default Screen Section" (0) [342836.075] (**) | |-->Monitor "" [342836.075] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [342836.075] (==) Automatically adding devices [342836.075] (==) Automatically enabling devices [342836.075] (==) Automatically adding GPU devices [342836.075] (==) Max clients allowed: 256, resource mask: 0x1f [342836.086] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [342836.086]Entry deleted from font path. [342836.099] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [342836.099] (==) ModulePath set to "/usr/lib/xorg/modules" [342836.099] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [342836.099] (II) Loader magic: 0x55fe210f4de0 [342836.099] (II) Module ABI versions: [342836.099]X.Org ANSI C Emulation: 0.4 [342836.099]X.Org Video Driver: 23.0 [342836.099]X.Org XInput driver : 24.1 [342836.099]X.Org Server Extension : 10.0 [342836.099] (++) using VT number 7 [342836.099] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration [342836.099] (II) xfree86: Adding drm device (/dev/dri/ca
Bug#879041: libglvnd0: Nvidia-Installer 384.90: "An incomplete installation of libglvnd was found."
384.98-2 dropped into sid this morning. It installed. This last weekend, I purged nvidia, and reinstalled. What was available in sid was 375.82, and it stalled. Then 378 came into sid, and it was installable. Then this morning, I was able to install 384.98-2. Still having a mesa-related error: root@asus:/home/chris# glxinfo | grep OpenGL libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast X Error of failed request: GLXBadContext Major opcode of failed request: 154 (GLX) Minor opcode of failed request: 6 (X_GLXIsDirect) Serial number of failed request: 48 Current serial number in output stream: 47 root@asus:/home/chris# glxinfo | grep rendering libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast X Error of failed request: GLXBadContext Major opcode of failed request: 154 (GLX) Minor opcode of failed request: 6 (X_GLXIsDirect) Serial number of failed request: 48 Current serial number in output stream: 47 root@asus:/home/chris# But that's another issue that I'm hoping a mesa update will fix. The installation issue is resolved for me.
Bug#879041: libglvnd0: Nvidia-Installer 384.90: "An incomplete installation of libglvnd was found."
Andreas, the experimental 384.98 driver failed. Sid's 375.82 is installable. This all started with the last Xorg and Mesa updates. There's a new Mesa at RC5 in experimental. I guess I'm going to wait for that to drop into sid.
Bug#879041: Follow Up: Maybe more directly related to the 10/18/17 17.2.2-1 Mesa Libs Updates and/or the xserver-xorg-core 2:1.19.5-1 Update
This is the 2nd time in a couple weeks that I have messed with bug
reporting, and now I'm doing through e-mail, and I hope this hits its mark.
This was reported as a libglvnd0 issue, but I do not think that's the
issue. Per a bug complaint on the nvidia forums, I'm thinking this may be
more related to what's listed in the title:
https://devtalk.nvidia.com/default/topic/1024276/linux/-384-90-redundant-installation-error-on-centos-6-9-debian-sid/
"Same error i get on debian sid. But this error was even in the previous
version of the driver after debian has changed / updated mesa libs."
Since this is also happening in CentOS ("derived from the sources of Red
Hat Enterprise Linux") this may be more of an upstream error, that may
eventually impact the non free nvidia-driver, and since it is only
affecting the latest proprietary driver installs, this bug may get ignored.
In case it is addressed at the mesa libs or xserver-xorg-core level, I'm
following up.
There is no problem installing the latest non free nvidia-driver, 375.82-8.
Really the same error as originally reported:
nvidia-installer log file '/var/log/nvidia-installer.log'
> creation time: Sat Nov 18 14:27:26 2017
> installer version: 387.22
>
> PATH: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
>
> nvidia-installer command line:
> ./nvidia-installer
> -s
> -N
> --x-module-path=/usr/lib/xorg/modules
> --x-library-path=/usr/lib
> -k
> 4.13.0-1-amd64
>
> Using built-in stream user interface
> -> Detected 4 CPUs online; setting concurrency level to 4.
> -> License accepted by command line option.
> -> Installing NVIDIA driver version 387.22.
> -> Would you like to register the kernel module sources with DKMS? This
> will allow DKMS to automatically build a new module, if you install a
> different kernel later. (Answer: No)
> -> Not probing for precompiled kernel interfaces.
> -> Performing CC sanity check with CC="/usr/bin/gcc-6".
> -> Kernel source path: '/lib/modules/4.13.0-1-amd64/source'
> -> Kernel output path: '/lib/modules/4.13.0-1-amd64/build'
> -> Performing Compiler check.
> -> Performing Dom0 check.
> -> Performing Xen check.
> -> Performing PREEMPT_RT check.
> -> Cleaning kernel module build directory.
>executing: 'cd ./kernel; /usr/bin/make -k -j4 clean
> NV_EXCLUDE_KERNEL_MODULES="" SYSSRC="/lib/modules/4.13.0-1-amd64/source"
> SYSOUT="/lib/modules/4.13.0-1-amd64/build"'...
>rm -f -r conftest
>make[1]: Entering directory '/usr/src/linux-headers-4.13.0-1-common'
>make[2]: Entering directory '/usr/src/linux-headers-4.13.0-1-amd64'
>make[2]: Leaving directory '/usr/src/linux-headers-4.13.0-1-amd64'
>make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-1-common'
> -> Building kernel modules
>executing: 'cd ./kernel; /usr/bin/make -k -j4
> NV_EXCLUDE_KERNEL_MODULES="" SYSSRC="/lib/modules/4.13.0-1-amd64/source"
> SYSOUT="/lib/modules/4.13.0-1-amd64/build"'...
>make[1]: Entering directory '/usr/src/linux-headers-4.13.0-1-common'
>make[2]: Entering directory '/usr/src/linux-headers-4.13.0-1-amd64'
> SYMLINK
> /usr/src/sgfxi-downloads/NVIDIA-Linux-x86_64-387.22/kernel/nvidia/nv-kernel.o
> SYMLINK
> /usr/src/sgfxi-downloads/NVIDIA-Linux-x86_64-387.22/kernel/nvidia-modeset/nv-modeset-kernel.o
> CONFTEST: remap_pfn_range
> CONFTEST: hash__remap_4k_pfn
> CONFTEST: follow_pfn
> CONFTEST: INIT_WORK
> CONFTEST: vmap
> CONFTEST: set_pages_uc
> CONFTEST: set_memory_uc
> CONFTEST: set_memory_array_uc
> CONFTEST: change_page_attr
> CONFTEST: pci_get_class
> CONFTEST: pci_choose_state
> CONFTEST: vm_insert_page
> CONFTEST: acpi_device_id
> CONFTEST: acquire_console_sem
> CONFTEST: console_lock
> CONFTEST: kmem_cache_create
> CONFTEST: on_each_cpu
> CONFTEST: smp_call_function
> CONFTEST: acpi_evaluate_integer
> CONFTEST: ioremap_cache
> CONFTEST: ioremap_wc
> CONFTEST: acpi_walk_namespace
> CONFTEST: pci_domain_nr
> CONFTEST: pci_dma_mapping_error
> CONFTEST: sg_alloc_table
> CONFTEST: sg_init_table
> CONFTEST: pci_get_domain_bus_and_slot
> CONFTEST: get_num_physpages
> CONFTEST: efi_enabled
> CONFTEST: proc_create_data
> CONFTEST: pde_data
> CONFTEST: proc_remove
> CONFTEST: pm_vt_switch_required
> CONFTEST: xen_ioemu_inject_msi
> CONFTEST: phys_to_dma
> CONFTEST: get_dma_ops
> CONFTEST: write_cr4
> CONFTEST: of_get_property
> CONFTEST: of_find_node_by_phandle
> CONFTEST: of_node_to_nid
> CONFTEST: pnv_pci_get_npu_dev
> CONFTEST: for_each_online_node
> CONFTEST: node_end_pfn
> CONFTEST: pci_bus_address
> CONFTEST: pci_stop_and_remove_bus_device
> CONFTEST: pci_remove_bus_device
> CONFTEST: request_threaded_irq
> CONFTEST: register_cpu_notifier
> CONFTEST: cpuhp_setup_state
> CONFTEST: backlight_device_register
> CONFTEST: remap_page_range
> CONFTEST: addr
Bug#833508: Fwd: Bug#833508: xbacklight reports "No outputs have backlight property"
[Dropping owner@ from CC] Dear Khurram, I'm sorry to hear you are having problems with Debian. I suggest you follow up with the X team; the Project Leader as a rule does not interfere with the technical details of bugs :) You can do this by writing to the bug number: 833...@bugs.debian.org I have CC'd this mail to there, so pressing "Reply All" should do the trick. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
weston_3.0.0-1_amd64.changes REJECTED
Hi, You seem to be missing a large number of attributions for (at least) Samsung, BMW, etc. Please check over your entire package (I stopped looking there). :) -- Chris Lamb Thu, 10 Aug 2017 13:19:59 + === Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new files which address our concerns.
libglvnd_0.2.999+git20170201-2_amd64.changes REJECTED
. === Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new files which address our concerns.
libglvnd_0.2.999+git20170201-3_amd64.changes REJECTED
Hi, Sorry I'm going to have to reject your package as it is missing references for LunarG, Inc,, Khronos Group, Vmware etc. I stopped looking there so please look over your entire package. :) -- Chris Lamb Tue, 01 Aug 2017 11:48:37 + === Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new files which address our concerns.
libglvnd_0.2.999+git20170201-1_amd64.changes REJECTED
. === Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new files which address our concerns.
Bug#868843: xorg-server: please make the BUILD_{DATE,TIME} reproducible
forwarded 868843 https://lists.x.org/pipermail/xorg-devel/2017-July/054127.html thanks Updating URL. Regards, -- ,''`. : :' : Chris Lamb, Debian Project Leader `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#868843: xorg-server: please make the BUILD_{DATE,TIME} reproducible
tags 868843 - moreinfo
forwarded 868843 https://lists.x.org/archives/xorg-devel/2017-July/thread.html
thanks
Hi Julien,
Thanks for the quick followup. :)
> How portable is the change to non-gnu date?
My previous patch was not. The updated attached patch is compatible
with BSD date(1). I am removing the "moreinfo" tag, assuming that was
why you added it.
> Can you send this patch upstream per
> https://www.x.org/wiki/Development/Documentation/SubmittingPatches/?
Done: https://lists.x.org/archives/xorg-devel/2017-July/thread.html
Best wishes,
--
,''`.
: :' : Chris Lamb, Debian Project Leader
`. `'` la...@debian.org / chris-lamb.co.uk
`-
From bb171c65af6ee0c8b48e9108b277b1f9ff21f978 Mon Sep 17 00:00:00 2001
From: Chris Lamb
Date: Thu, 20 Jul 2017 15:42:15 +0100
Subject: [PATCH] configure.ac: Make BUILD_{DATE,TIME} respect
SOURCE_DATE_EPOCH if set
Whilst working on the Reproducible Builds effort [0], we noticed that
xorg-server could not be built reproducibly. One reason is because it
embeds a "current" build and date time.
This should be compatible with both GNU and BSD date(1).
[0] https://reproducible-builds.org/
---
configure.ac | 10 --
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/configure.ac b/configure.ac
index e202770c1..f10a94cb4 100644
--- a/configure.ac
+++ b/configure.ac
@@ -2405,9 +2405,15 @@ AC_DEFINE_DIR(PROJECTROOT, prefix, [Overall prefix])
AC_DEFINE_DIR(SYSCONFDIR, sysconfdir, [sysconfdir])
AC_SUBST([RELEASE_DATE])
-BUILD_DATE="`date +'%Y%m%d'`"
+DATE_FMT="%Y-%m-%d"
+TIME_FMT="1%H%M%S"
+BUILD_DATE="`date "+$DATE_FMT"`"
+BUILD_TIME="`date "+$TIME_FMT"`"
+if test "x$SOURCE_DATE_EPOCH" != "x"; then
+ BUILD_DATE="`date -u -d "@$SOURCE_DATE_EPOCH" "+$DATE_FMT" 2>/dev/null || date -u -r "$SOURCE_DATE_EPOCH" "+$DATE_FMT" 2>/dev/null || date -u "+$DATE_FMT"`"
+ BUILD_TIME="`date -u -d "@$SOURCE_DATE_EPOCH" "+$TIME_FMT" 2>/dev/null || date -u -r "$SOURCE_DATE_EPOCH" "+$TIME_FMT" 2>/dev/null || date -u "+$TIME_FMT"`"
+fi
AC_SUBST([BUILD_DATE])
-BUILD_TIME="`date +'1%H%M%S'`"
AC_SUBST([BUILD_TIME])
DIX_CFLAGS="-DHAVE_DIX_CONFIG_H $XSERVER_CFLAGS"
--
2.13.3
Bug#868843: xorg-server: please make the BUILD_{DATE,TIME} reproducible
Source: xorg-server Version: 2:1.19.3-2 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org Hi, Whilst working on the Reproducible Builds effort [0], we noticed that xorg-server could not be built reproducibly. One reason is because it embeds a build and date time. Patch attached. Thanks to Bernhard M. Wiedemann! [0] https://reproducible-builds.org/ Regards, -- ,''`. : :' : Chris Lamb, Debian Project Leader `. `'` la...@debian.org / chris-lamb.co.uk `- diff --git a/configure.ac b/configure.ac index e6c5b35..cd7ebfe 100644 --- a/configure.ac +++ b/configure.ac @@ -2555,9 +2555,14 @@ AC_DEFINE_DIR(PROJECTROOT, prefix, [Overall prefix]) AC_DEFINE_DIR(SYSCONFDIR, sysconfdir, [sysconfdir]) AC_SUBST([RELEASE_DATE]) -BUILD_DATE="`date +'%Y%m%d'`" +if test "x$SOURCE_DATE_EPOCH" = "x"; then + BUILD_DATE="`date --utc --date="@$SOURCE_DATE_EPOCH" +'%Y%m%d'`" + BUILD_TIME="`date --utc --date="@$SOURCE_DATE_EPOCH" +'1%H%M%S'`" +else + BUILD_DATE="`date +'%Y%m%d'`" + BUILD_TIME="`date +'1%H%M%S'`" +fi AC_SUBST([BUILD_DATE]) -BUILD_TIME="`date +'1%H%M%S'`" AC_SUBST([BUILD_TIME]) DIX_CFLAGS="-DHAVE_DIX_CONFIG_H $XSERVER_CFLAGS"
Wheezy update of xorg-server?
Dear maintainer(s),
The Debian LTS team would like to fix the security issues which are
currently open in the Wheezy version of xorg-server:
https://security-tracker.debian.org/tracker/source-package/xorg-server
Would you like to take care of this yourself?
If yes, please follow the workflow we have defined here:
https://wiki.debian.org/LTS/Development
If that workflow is a burden to you, feel free to just prepare an
updated source package and send it to debian-...@lists.debian.org
(via a debdiff, or with an URL pointing to the source package,
or even with a pointer to your packaging repository), and the members
of the LTS team will take care of the rest. Indicate clearly whether you
have tested the updated package or not.
If you don't want to take care of this update, it's not a problem, we
will do our best with your package. Just let us know whether you would
like to review and/or test the updated package before it gets released.
You can also opt-out from receiving future similar emails in your
answer and then the LTS Team will take care of xorg-server updates
for the LTS releases.
Thank you very much.
Chris Lamb,
on behalf of the Debian LTS team.
PS: A member of the LTS team might start working on this update at
any point in time. You can verify whether someone is registered
on this update in this file:
https://anonscm.debian.org/viewvc/secure-testing/data/dla-needed.txt?view=markup
Regards,
--
,''`.
: :' : Chris Lamb, Debian Project Leader
`. `'` la...@debian.org / chris-lamb.co.uk
`-
Bug#770130: Additional user info
I've just had this problem after installing jessie on an old 32-bit system (Asus A7N8X, AthlonXP2600+, 2GB RAM, NV11 gfx card). Really glad to find this bug (and the associated ones for gdm3). I replaced gdm3 with lightdm and gnome3 with xfce and everything works fine. Props to debian for making the switch completely painless. CC
libdrm_2.4.74-2_amd64.changes REJECTED
Mon 30 23:05 < pochu> please reject libdrm from NEW, it was meant for experimental === Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new files which address our concerns.
libxfont_2.0.1-1_amd64.changes REJECTED
as requested === Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new files which address our concerns.
Bug#831405: xserver-xorg-video-openchrome: please make the build reproducible
Dear Maintainer, > Source: xserver-xorg-video-openchrome > Version: 1:0.2.904+svn842-2+squeeze1 > Tags: patch There hasn't seem to be any update on this bug in 61 days, in which time the Reproducible Builds effort has come on a long way. :) Would you consider applying this patch and uploading? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#831405: xserver-xorg-video-openchrome: please make the build reproducible
Source: xserver-xorg-video-openchrome
Version: 1:0.3.3+git20160310-1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
Hi,
Whilst working on the "reproducible builds" effort [0], we noticed
that xserver-xorg-video-openchrome could not be built reproducibly.
Patch attached. Please send it upstream if possible.
[0] https://wiki.debian.org/ReproducibleBuilds
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
--- a/src/Makefile.am 2016-07-15 17:56:15.066700891 +0200
--- b/src/Makefile.am 2016-07-15 18:22:08.362042386 +0200
@@ -113,6 +113,9 @@
if [ -d .svn ]; then \
echo '#define BUILDCOMMENT "(development build, at revision '\
"`svnversion -nc .. | sed -e s/^[^:]*://`"')"' >
$@.tmp; \
+elif [ "$$SOURCE_DATE_EPOCH" ]; then \
+ printf '#define BUILDCOMMENT "(compiled with SOURCE_DATE_EPOCH:
%s)"' $$SOURCE_DATE_EPOCH \
+ > $@.tmp; \
else \
date +'#define BUILDCOMMENT "(development build, compiled on
%c)"' \
> $@.tmp; \
Comments regarding vulkan_1.0.8.0+dfsg1-1_amd64.changes
Next upload please split out some code copies in debian/copyright (at least loader/cJSON.[ch]), loader/murmurhash.c, etc. Also you are missing the Android, Chromium references (and others; incomplete list).
Bug#815867: libxkbcommon: FTBFS: FAIL: test/x11comp
Source: libxkbcommon Version: 0.5.0-1 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, libxkbcommon fails to build from source in unstable/amd64: [..] make[3]: Leaving directory '/home/lamby/temp/cdt.20160225074617.SVmbtSnzXS/libxkbcommon-0.5.0' make check-TESTS make[3]: Entering directory '/home/lamby/temp/cdt.20160225074617.SVmbtSnzXS/libxkbcommon-0.5.0' make[4]: Entering directory '/home/lamby/temp/cdt.20160225074617.SVmbtSnzXS/libxkbcommon-0.5.0' PASS: test/context PASS: test/utf8 PASS: test/rules-file PASS: test/log PASS: test/atom PASS: test/keysym PASS: test/state PASS: test/filecomp PASS: test/buffercomp PASS: test/stringcomp PASS: test/compose PASS: test/rulescomp PASS: test/keyseq SKIP: test/x11 FAIL: test/x11comp Testsuite summary for libxkbcommon 0.5.0 # TOTAL: 15 # PASS: 13 # SKIP: 1 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 See ./test-suite.log Please report to https://bugs.freedesktop.org/enter_bug.cgi?product=libxkbcommon Makefile:1687: recipe for target 'test-suite.log' failed make[4]: *** [test-suite.log] Error 1 make[4]: Leaving directory '/home/lamby/temp/cdt.20160225074617.SVmbtSnzXS/libxkbcommon-0.5.0' Makefile:1793: recipe for target 'check-TESTS' failed make[3]: *** [check-TESTS] Error 2 make[3]: Leaving directory '/home/lamby/temp/cdt.20160225074617.SVmbtSnzXS/libxkbcommon-0.5.0' Makefile:2102: recipe for target 'check-am' failed make[2]: *** [check-am] Error 2 make[2]: Leaving directory '/home/lamby/temp/cdt.20160225074617.SVmbtSnzXS/libxkbcommon-0.5.0' Makefile:2105: recipe for target 'check' failed make[1]: *** [check] Error 2 make[1]: Leaving directory '/home/lamby/temp/cdt.20160225074617.SVmbtSnzXS/libxkbcommon-0.5.0' dh_auto_test: make -j9 check returned exit code 2 debian/rules:17: recipe for target 'build' failed make: *** [build] Error 2 [..] The full build log is attached. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- libxkbcommon.0.5.0-1.unstable.amd64.log.txt.gz Description: Binary data
Bug#813359: xserver-xorg-input-aiptek: FTBFS: xf86Aiptek.c:296:17: error: too many arguments to function 'xf86PostKeyEvent'
64:36: note: in expansion of macro 'XI_ERASER' rc = xf86AiptekAllocate(pInfo, XI_ERASER, ABSOLUTE_FLAG|ERASER_ID); ^ ../../src/xf86Aiptek.c:1616:1: note: expected 'char *' but argument is of type 'const char *' xf86AiptekAllocate(InputInfoPtr pInfo, ^ ../../src/xf86Aiptek.c: In function 'xf86AiptekInit': ../../src/xf86Aiptek.c:1832:7: warning: assignment discards 'const' qualifier from pointer target type [-Wdiscarded-qualifiers] s = xf86FindOptionValue(pInfo->options, "Type"); ^ ../../src/xf86Aiptek.c:1861:24: warning: assignment discards 'const' qualifier from pointer target type [-Wdiscarded-qualifiers] common->deviceName = xf86FindOptionValue(pInfo->options, "Device"); ^ ../../src/xf86Aiptek.c:1936:7: warning: assignment discards 'const' qualifier from pointer target type [-Wdiscarded-qualifiers] s = xf86FindOptionValue(pInfo->options, "Pressure"); ^ ../../src/xf86Aiptek.c:1956:7: warning: assignment discards 'const' qualifier from pointer target type [-Wdiscarded-qualifiers] s = xf86FindOptionValue(pInfo->options, "Mode"); ^ Makefile:457: recipe for target 'xf86Aiptek.lo' failed make[3]: *** [xf86Aiptek.lo] Error 1 make[3]: Leaving directory '/home/lamby/temp/cdt.20160201084729.aY0PW5Ttii/xserver-xorg-input-aiptek-1.4.1/build/src' Makefile:438: recipe for target 'all-recursive' failed make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory '/home/lamby/temp/cdt.20160201084729.aY0PW5Ttii/xserver-xorg-input-aiptek-1.4.1/build' Makefile:370: recipe for target 'all' failed make[1]: *** [all] Error 2 make[1]: Leaving directory '/home/lamby/temp/cdt.20160201084729.aY0PW5Ttii/xserver-xorg-input-aiptek-1.4.1/build' dh_auto_build: make -j1 returned exit code 2 debian/rules:17: recipe for target 'build' failed make: *** [build] Error 2 [..] The full build log is attached. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- xserver-xorg-input-aiptek.1:1.4.1-1.unstable.amd64.log.txt.gz Description: Binary data
Bug#812882: xserver-xorg-video-intel: FTBFS: src/uxa/intel_driver.c:645:2: error: too many arguments to function 'PixmapSyncDirtyHelper'
Source: xserver-xorg-video-intel Version: 2:2.99.917-2 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, xserver-xorg-video-intel fails to build from source in unstable/amd64: [..] libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../../src/uxa -I../.. -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wpointer-arith -Wmissing-declarations -Wformat=2 -Wstrict-prototypes -Wmissing-prototypes -Wnested-externs -Wbad-function-cast -Wold-style-definition -Wdeclaration-after-statement -Wunused -Wuninitialized -Wshadow -Wmissing-noreturn -Wmissing-format-attribute -Wredundant-decls -Wlogical-op -Werror=implicit -Werror=nonnull -Werror=init-self -Werror=main -Werror=missing-braces -Werror=sequence-point -Werror=return-type -Werror=trigraphs -Werror=array-bounds -Werror=write-strings -Werror=address -Werror=int-to-pointer-cast -Werror=pointer-to-int-cast -fno-strict-aliasing -fvisibility=hidden -I/usr/include/libdrm -I/usr/include/pixman-1 -I/usr/include/xorg -I/usr/include/X11/dri -I/usr/include/libdrm -I/usr/include/libdrm -I/usr/include/libdrm -I../../../xvmc -I../../../src -I../../../src/render_program -I../../../xvmc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -c ../../../src/uxa/intel_driver.c -fPIC -DPIC -o .libs/intel_driver.o ../../../src/uxa/intel_driver.c: In function 'redisplay_dirty': ../../../src/uxa/intel_driver.c:645:2: error: too many arguments to function 'PixmapSyncDirtyHelper' PixmapSyncDirtyHelper(dirty, &pixregion); ^ In file included from /usr/include/xorg/gc.h:54:0, from /usr/include/xorg/dix.h:51, from /usr/include/xorg/privates.h:151, from /usr/include/xorg/cursor.h:53, from /usr/include/xorg/scrnintstr.h:53, from /usr/include/xorg/xf86str.h:39, from /usr/include/xorg/xf86.h:44, from ../../../src/uxa/intel_driver.c:49: /usr/include/xorg/pixmap.h:131:1: note: declared here PixmapSyncDirtyHelper(PixmapDirtyUpdatePtr dirty); ^ Makefile:538: recipe for target 'intel_driver.lo' failed make[4]: *** [intel_driver.lo] Error 1 make[4]: Leaving directory '/home/lamby/temp/cdt.20160127152723.J5ezd6xJap/xserver-xorg-video-intel-2.99.917/build/src/uxa' Makefile:608: recipe for target 'all-recursive' failed make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory '/home/lamby/temp/cdt.20160127152723.J5ezd6xJap/xserver-xorg-video-intel-2.99.917/build/src' Makefile:478: recipe for target 'all-recursive' failed make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory '/home/lamby/temp/cdt.20160127152723.J5ezd6xJap/xserver-xorg-video-intel-2.99.917/build' Makefile:410: recipe for target 'all' failed make[1]: *** [all] Error 2 make[1]: Leaving directory '/home/lamby/temp/cdt.20160127152723.J5ezd6xJap/xserver-xorg-video-intel-2.99.917/build' dh_auto_build: make -j1 returned exit code 2 debian/rules:51: recipe for target 'build' failed make: *** [build] Error 2 [..] The full build log is attached. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- xserver-xorg-video-intel.2:2.99.917-2.unstable.amd64.log.txt.gz Description: Binary data
Bug#809598: x11proto-bigreqs: FTBFS: x11proto-bigreqs-dev missing files (usr/share/doc/bigreqsproto/*.txt), aborting
Source: x11proto-bigreqs Version: 1:1.1.2-1 Severity: serious Justification: fails to build from source Tags: sid stretch User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, The package fails to build: dh_testdir dh_testroot dh_installdocs dh_installman find debian/tmp/usr/share/doc/bigreqsproto -name '*.xml' -delete find debian/tmp/usr/share/doc/bigreqsproto -name '*.db' -delete dh_install --sourcedir=debian/tmp --fail-missing dh_install: x11proto-bigreqs-dev missing files (usr/share/doc/bigreqsproto/*.txt), aborting debian/rules:71: recipe for target 'binary-indep' failed make: *** [binary-indep] Error 255 dpkg-buildpackage: error: debian/rules binary gave error exit status 2 Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/x11proto-bigreqs.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64)
Bug#808694: x11proto-fonts: FTBFS: dh_install: x11proto-fonts-dev missing files (usr/share/doc/fontsproto/*.txt), aborting
Source: x11proto-fonts Version: 2.1.3-1 Severity: serious Justification: fails to build from source Tags: sid stretch User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, The package fails to build: make[1]: Leaving directory '/x11proto-fonts-2.1.3/build' dh_testdir dh_testroot dh_installdocs dh_installman find debian/tmp/usr/share/doc/fontsproto -name '*.xml' -delete dh_install --sourcedir=debian/tmp --fail-missing --exclude .db dh_install: x11proto-fonts-dev missing files (usr/share/doc/fontsproto/*.txt), aborting debian/rules:70: recipe for target 'binary-indep' failed make: *** [binary-indep] Error 255 dpkg-buildpackage: error: debian/rules binary gave error exit status 2 Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/x11proto-fonts.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64)
Bug#807705: xserver-xorg-video-openchrome: FTBFS: /usr/include/xorg/os.h:558:1: error: expected identifier or '(' before '__extension__'
Source: xserver-xorg-video-openchrome
Version: 1:0.3.3-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
Dear Maintainer,
xserver-xorg-video-openchrome fails to build from source in unstable/amd64:
[..]
make[5]: Entering directory
'/home/lamby/temp/cdt.20151211222417.E2Yo35PxGF/xserver-xorg-video-openchrome-0.3.3/build/src'
/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I.
-I../../src -I.. -fvisibility=hidden -I/usr/include/pixman-1
-I/usr/include/libdrm -I/usr/include/xorg -I/usr/include/X11/dri
-fvisibility=hidden -I/usr/include/pixman-1 -I/usr/include/libdrm
-I/usr/include/xorg -I/usr/include/X11/dri -I/usr/include/libdrm
-I/usr/include/X11/dri -g -O2 -c -o via_3d.lo ../../src/via_3d.c
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../src -I..
-fvisibility=hidden -I/usr/include/pixman-1 -I/usr/include/libdrm
-I/usr/include/xorg -I/usr/include/X11/dri -fvisibility=hidden
-I/usr/include/pixman-1 -I/usr/include/libdrm -I/usr/include/xorg
-I/usr/include/X11/dri -I/usr/include/libdrm -I/usr/include/X11/dri -g -O2 -c
../../src/via_3d.c -fPIC -DPIC -o .libs/via_3d.o
In file included from /usr/include/string.h:634:0,
from /usr/include/xorg/os.h:53,
from /usr/include/xorg/misc.h:115,
from /usr/include/xorg/xf86str.h:37,
from /usr/include/xorg/xf86.h:44,
from ../../src/via_3d.h:27,
from ../../src/via_3d.c:24:
/usr/include/xorg/os.h:558:1: error: expected identifier or '(' before
'__extension__'
strndup(const char *str, size_t n);
^
Makefile:596: recipe for target 'via_3d.lo' failed
make[5]: *** [via_3d.lo] Error 1
make[5]: Leaving directory
'/home/lamby/temp/cdt.20151211222417.E2Yo35PxGF/xserver-xorg-video-openchrome-0.3.3/build/src'
Makefile:611: recipe for target 'all-recursive' failed
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory
'/home/lamby/temp/cdt.20151211222417.E2Yo35PxGF/xserver-xorg-video-openchrome-0.3.3/build/src'
Makefile:475: recipe for target 'all' failed
make[3]: *** [all] Error 2
make[3]: Leaving directory
'/home/lamby/temp/cdt.20151211222417.E2Yo35PxGF/xserver-xorg-video-openchrome-0.3.3/build/src'
Makefile:445: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
'/home/lamby/temp/cdt.20151211222417.E2Yo35PxGF/xserver-xorg-video-openchrome-0.3.3/build'
Makefile:377: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory
'/home/lamby/temp/cdt.20151211222417.E2Yo35PxGF/xserver-xorg-video-openchrome-0.3.3/build'
dh_auto_build: make -j1 returned exit code 2
debian/rules:34: recipe for target 'build' failed
make: *** [build] Error 2
[..]
The full build log is attached.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
xserver-xorg-video-openchrome.1:0.3.3-1.unstable.amd64.log.txt.gz
Description: Binary data
Bug#806498: x11proto-core: FTBFS: dh_install: x11proto-core-dev missing files (usr/share/doc/x11proto-core-dev/*.txt), aborting
Source: x11proto-core Version: 7.0.27-1 Severity: serious Justification: fails to build from source Tags: sid User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, The package fails to build: make[2]: Leaving directory '/x11proto-core-7.0.27/build' make[1]: Leaving directory '/x11proto-core-7.0.27' debian/rules override_dh_install make[1]: Entering directory '/x11proto-core-7.0.27' find debian/tmp/usr/share/doc/x11proto-core-dev -name '*.xml' -delete find debian/tmp/usr/share/doc/x11proto-core-dev -name '*.db' -delete find debian/tmp/usr/share/doc/x11proto-core-dev -name '*.ps' -delete dh_install --fail-missing dh_install: x11proto-core-dev missing files (usr/share/doc/x11proto-core-dev/*.txt), aborting debian/rules:17: recipe for target 'override_dh_install' failed make[1]: *** [override_dh_install] Error 255 Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/x11proto-core.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64)
Bug#806471: libxfont: FTBFS: dh_install: libxfont-dev missing files (../../build-main/doc/*.txt), aborting
Source: libxfont Version: 1:1.5.1-1 Severity: serious Justification: fails to build from source Tags: sid User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, The package fails to build: debian/rules override_dh_install make[1]: Entering directory '/libxfont-1.5.1' find debian/tmp-* -name '*.la' -delete dh_install -a -Nlibxfont1-udeb --sourcedir=debian/tmp-main --fail-missing dh_install: libxfont-dev missing files (../../build-main/doc/*.txt), aborting debian/rules:48: recipe for target 'override_dh_install' failed make[1]: *** [override_dh_install] Error 2 Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/libxfont.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64)
Bug#806472: libxi: FTBFS: dh_install: libxi-dev missing files (usr/share/doc/libXi/*.txt), aborting
Source: libxi Version: 2:1.7.5-1 Severity: serious Justification: fails to build from source Tags: sid User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, The package fails to build: debian/rules override_dh_install make[1]: Entering directory '/libxi-1.7.5' dh_install --fail-missing --exclude=libXi.la --exclude .db --exclude .xml dh_install: libxi-dev missing files (usr/share/doc/libXi/*.txt), aborting debian/rules:27: recipe for target 'override_dh_install' failed Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/libxi.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64)
Bug#805213: libxdmcp: FTBFS: dh_install: libxdmcp-dev missing files (usr/share/doc/libXdmcp/*.txt), aborting
Source: libxdmcp Version: 1:1.1.2-1 Severity: serious Justification: fails to build from source Tags: sid User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, The package fails to build: make[1]: Leaving directory '/libxdmcp-1.1.2' debian/rules override_dh_install make[1]: Entering directory '/libxdmcp-1.1.2' dh_install --fail-missing --exclude=libXdmcp.la --exclude .html --exclude .css --exclude .db dh_install: libxdmcp-dev missing files (usr/share/doc/libXdmcp/*.txt), aborting debian/rules:31: recipe for target 'override_dh_install' failed make[1]: *** [override_dh_install] Error 255 Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/libxdmcp.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64)
Bug#803382: xserver-xorg-video-qxl: Missing Build-Depends on libglib2.0-dev and libssl-dev
Source: xserver-xorg-video-qxl Version: 0.1.4-3 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Tags: patch Dear Maintainer, xserver-xorg-video-qxl fails to build from source in unstable/amd64 due to missing Build-Depends on libglib2.0-dev and libssl-dev. The full build log is attached or (an alternate build) can be viewed here: https://reproducible.debian.net/logs/unstable/amd64/xserver-xorg-video-qxl_0.1.4-3.build1.log.gz Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- xserver-xorg-video-qxl.0.1.4-3.unstable.amd64.log.txt.gz Description: application/gzip
Bug#802413: xserver-xorg-video-qxl: FTBFS: Package 'libcacard', required by 'spice-server', not found
Source: xserver-xorg-video-qxl Version: 0.1.4-3 Severity: serious Justification: fails to build from source Tags: sid stretch User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, The package fails to build: checking for inotify_init1... yes checking for SPICE... no configure: error: Package requirements (spice-server >= 0.6.3) were not met: Package 'libcacard', required by 'spice-server', not found Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/xserver-xorg-video-qxl.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64)
Bug#796373: mesa-demos: FTBFS: error: 'EGL_SCREEN_BIT_MESA' undeclared (first use in this function)
Source: mesa-demos Version: 8.2.0-1 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, mesa-demos fails to build from source in testing/amd64: [..] Making all in egl make[3]: Entering directory '/tmp/buildd/mesa-demos-8.2.0/src/egl' Making all in eglut make[4]: Entering directory '/tmp/buildd/mesa-demos-8.2.0/src/egl/eglut' /bin/bash ../../../libtool --tag=CC --mode=compile gcc -DPACKAGE_NAME=\"mesa-demos\" -DPACKAGE_TARNAME=\"mesa-demos\" -DPACKAGE_VERSION=\"8.2.0\" -DPACKAGE_STRING=\"mesa-demos\ 8.2.0\" -DPACKAGE_BUGREPORT=\"https://bugs.freedesktop.org/enter_bug.cgi\?product=Mesa\&component=Demos\"; -DPACKAGE_URL=\"\" -DPACKAGE=\"mesa-demos\" -DVERSION=\"8.2.0\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DDEMOS_DATA_DIR=\"../data/\" -DDEMOS_DATA_DIR=\"../data/\" -I. -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/libdrm -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -c -o eglut.lo eglut.c libtool: compile: gcc -DPACKAGE_NAME=\"mesa-demos\" -DPACKAGE_TARNAME=\"mesa-demos\" -DPACKAGE_VERSION=\"8.2.0\" "-DPACKAGE_STRING=\"mesa-demos 8.2.0\"" "-DPACKAGE_BUGREPORT=\"https://bugs.freedesktop.org/enter_bug.cgi?product=Mesa&component=Demos\""; -DPACKAGE_URL=\"\" -DPACKAGE=\"mesa-demos\" -DVERSION=\"8.2.0\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DDEMOS_DATA_DIR=\"../data/\" -DDEMOS_DATA_DIR=\"../data/\" -I. -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/libdrm -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -c eglut.c -fPIC -DPIC -o .libs/eglut.o eglut.c: In function '_eglutDestroyWindow': eglut.c:80:32: error: 'EGL_SCREEN_BIT_MESA' undeclared (first use in this function) _eglut->surface_type != EGL_SCREEN_BIT_MESA) ^ eglut.c:80:32: note: each undeclared identifier is reported only once for each function it appears in eglut.c: In function '_eglutCreateWindow': eglut.c:178:9: error: 'EGL_SCREEN_BIT_MESA' undeclared (first use in this function) case EGL_SCREEN_BIT_MESA: ^ eglut.c: In function 'eglutDestroyWindow': eglut.c:293:33: error: 'EGL_SCREEN_BIT_MESA' undeclared (first use in this function) if ( _eglut->surface_type != EGL_SCREEN_BIT_MESA) ^ Makefile:488: recipe for target 'eglut.lo' failed make[4]: *** [eglut.lo] Error 1 make[4]: Leaving directory '/tmp/buildd/mesa-demos-8.2.0/src/egl/eglut' Makefile:418: recipe for target 'all-recursive' failed make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory '/tmp/buildd/mesa-demos-8.2.0/src/egl' Makefile:434: recipe for target 'all-recursive' failed make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory '/tmp/buildd/mesa-demos-8.2.0/src' Makefile:441: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/tmp/buildd/mesa-demos-8.2.0' dh_auto_build: make -j1 returned exit code 2 debian/rules:3: recipe for target 'build' failed make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 [..] The full build log is attached or can be viewed here: https://reproducible.debian.net/logs/testing/amd64/mesa-demos_8.2.0-1.build1.log.gz Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- I: using fakeroot in build. I: pbuilder: network access will be disabled during build I: Current time: Sat Aug 15 13:11:14 GMT+12 2015 I: pbuilder-time-stamp: 1439687474 I: Building the build Environment I: extracting base tarball [/var/cache/pbuilder/testing-reproducible-base.tgz] I: creating local configuration I: copying local configuration I: mounting /proc filesystem I: mounting /run/shm filesystem I: mounting /dev/pts filesystem I: Mounting /dev/shm I: Mounting /sys I: policy-rc.d already exists I: Installing the build-deps -> Attempting to satisfy build-dependencies -> Creating pbu
Bug#790911: FTBFS: src/sna/sna_driver.c: error: implicit declaration of function 'fstat'
Source: xserver-xorg-video-intel
Version: 2:2.99.917-1
Severity: serious
Tags: sid
Justification: fails to build from source (but built successfully in the past)
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
Dear Maintainer,
The package fails to build:
.../../../src/sna/sna_driver.c: In function 'sna_handle_uevents':
.../../../src/sna/sna_driver.c:799:2: error: implicit declaration of function
'fstat' [-Werror=implicit-function-declaration]
if (fstat(sna->kgem.fd, &s) || memcmp(&s.st_rdev, &udev_devnum, sizeof
(dev_t))) {
^
.../../../src/sna/sna_driver.c:799:2: warning: nested extern declaration of
'fstat' [-Wnested-externs]
Probably the same cause / fix as https://bugs.debian.org/790631 , but I'm
guessing "missing header".
Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/xserver-xorg-video-intel.html
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.19.0-21-generic (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150702214645.1505.55145.reportbug@sid
Bug#781932:
On 5 April 2015 at 15:32, Julien Cristau wrote: > On Sun, Apr 5, 2015 at 15:29:58 +0100, Chris Bainbridge wrote: > >> On 5 April 2015 at 15:20, Julien Cristau wrote: >> > On Sun, Apr 5, 2015 at 13:54:19 +0100, Chris Bainbridge wrote: >> > >> >> Why was the severity downgraded from 'serious'? >> >> >> >> Isn't the laptop display being non-functional a serious bug? One which >> >> could potentially impact every Debian laptop user with an Intel GPU >> >> and an external monitor? Which, presumably, would be quite a few >> >> people. >> >> >> > No, an issue with the display of a single laptop is not serious. >> >> How do you know the issue is only with the display of a single laptop? >> Have you tested any other (Intel) laptops with an external monitor? >> Particularly where the resolution of the laptop does not match that of >> the external monitor? >> > 1) if this was a general issue we'd have received a dozen reports by now > 2) my laptop works just fine It is unlikely that this kind of bug would impact just one single laptop. It is more likely to impact a broader class, at the least "IvyBridge Macbook", but possibly more broadly just "IvyBridge laptop" or perhaps "SNB/IVB/HSW laptop". Without testing and/or understanding of the cause of the bug, I don't see how you can draw the conclusion that the bug only occurs on a single laptop. -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAP-bSRYYHd8Tg2BT4XkQwViL=-cegwe0c5g7+0y1fcahc8z...@mail.gmail.com
Bug#781932:
On 5 April 2015 at 15:20, Julien Cristau wrote: > On Sun, Apr 5, 2015 at 13:54:19 +0100, Chris Bainbridge wrote: > >> Why was the severity downgraded from 'serious'? >> >> Isn't the laptop display being non-functional a serious bug? One which >> could potentially impact every Debian laptop user with an Intel GPU >> and an external monitor? Which, presumably, would be quite a few >> people. >> > No, an issue with the display of a single laptop is not serious. How do you know the issue is only with the display of a single laptop? Have you tested any other (Intel) laptops with an external monitor? Particularly where the resolution of the laptop does not match that of the external monitor? -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cap-bsryy78o+qe11bknibi2hqygjzlknmsobkawa+-p_8pl...@mail.gmail.com
Bug#781932:
Why was the severity downgraded from 'serious'? Isn't the laptop display being non-functional a serious bug? One which could potentially impact every Debian laptop user with an Intel GPU and an external monitor? Which, presumably, would be quite a few people. -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cap-bsrbx6qyetcrxu7bqgiwsrhysw9rmh7_kp1udgkwvgy2...@mail.gmail.com
Bug#781932: xserver-xorg-video-intel: laptop display unusable (blank) if external monitor is connected
Package: xserver-xorg-video-intel Version: 2:2.21.15-2+b2 Severity: serious Dear Maintainer, Hardware: IvyBridge HD4000 GPU on Macbook Pro 13 To reproduce: - Connect an external monitor on DP - Boot jessie - Log in to Gnome - Laptop display immediately goes blank This bug appears to be fixed in the latest upstream git. It is not known at which point it got fixed. xorg.log with working upstream git: (--) intel(0): Output eDP1 using initial mode 2560x1600 on pipe 0 (--) intel(0): Output DP2 using initial mode 1680x1050 on pipe 1 xorg.log with non-working jessie driver: (II) intel(0): Output eDP1 using initial mode 1680x1050 (II) intel(0): Output DP2 using initial mode 1680x1050 So the issue might be that the driver attempts to use the incorrect external monitor resolution 1680x1050 for the laptop display. Though xrandr reports the laptop display resolution 2560x1600 is in use: Screen 0: minimum 320 x 200, current 4240 x 1600, maximum 8192 x 8192 eDP1 connected primary 2560x1600+0+0 (normal left inverted right x axis y axis) 286mm x 179mm 2560x1600 59.97*+ 2048x1536 60.00 1920x1440 60.00 1856x1392 60.01 1792x1344 60.01 1920x1200 59.95 1920x1080 59.93 1600x1200 60.00 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1280x1024 60.02 1440x900 59.89 1280x960 60.00 1360x768 59.8059.96 1152x864 60.00 1024x768 60.00 800x600 60.3256.25 640x480 59.94 Attempting to manually change the mode with xrandr does nothing (not surprising, as xrandr reports the mode is already correct). -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Feb 20 2014 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 2401376 Feb 11 00:35 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) /etc/X11/xorg.conf does not exist. /etc/X11/xorg.conf.d does not exist. /etc/modprobe.d contains no KMS configuration files. Kernel version (/proc/version): --- Linux version 3.16.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt7-1 (2015-03-01) Xorg X server log files on system: -- -rw-r--r-- 1 root root 31378 Jul 28 2014 /var/log/Xorg.10.log -rw-r--r-- 1 root root 27023 Feb 28 17:54 /var/log/Xorg.3.log -rw-r--r-- 1 root root 27022 Feb 28 18:51 /var/log/Xorg.1.log -rw-r--r-- 1 root root 28596 Mar 1 01:31 /var/log/Xorg.2.log -rw-r--r-- 1 root root 42096 Apr 5 01:31 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [52.259] X.Org X Server 1.16.4 Release Date: 2014-12-20 [52.259] X Protocol Version 11, Revision 0 [52.259] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian [52.259] Current Operating System: Linux debian 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt7-1 (2015-03-01) x86_64 [52.259] Kernel command line: BOOT_IMAGE=/@jessie/boot/vmlinuz-3.16.0-4-amd64 root=UUID=61cc969e-5ba5-4e04-80ad-5e26d2f39c55 ro rootflags=subvol=@jessie quiet [52.259] Build Date: 11 February 2015 12:32:02AM [52.259] xorg-server 2:1.16.4-1 (http://www.debian.org/support) [52.259] Current version of pixman: 0.32.6 [52.259] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [52.259] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [52.259] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Apr 5 01:31:33 2015 [52.259] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [52.260] (==) No Layout section. Using the first Screen section. [52.260] (==) No screen section available. Using defaults. [52.260] (**) |-->Screen "Default Screen Section" (0) [52.260] (**) | |-->Monitor "" [52.260] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [52.260] (==) Automatically adding devices [52.260] (==) Automatically enabling devices [52.260] (==) Automatically adding GPU devices [52.260] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [52.260] Entry deleted from font path. [52.260] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [52.260] (==) ModulePath set to "/usr/lib/xorg/modules" [52.260] (II) The server
Bug#781666: xserver-xorg-video-intel: intel driver option TearFree does not work in Jessie
Package: xserver-xorg-video-intel Version: 2:2.21.15-2+b2 Severity: normal The Intel option TearFree does not work; tearing is still present. Setup is XFCE running on Ivy Bridge HD4000 with three monitors. This is fixed in the latest upstream git. -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAP-bSRbBSST5Ogcf-1X6d+N7_=vGjhJU9OykESw=u6x+++f...@mail.gmail.com
Bug#762047:
> Okay, so I think your original problem is because the Xorg fbdev driver uses > the colour depth from console by default, and I guess the login manager > you're using can't deal with that. You may want to report that against the > login manager package Filed at https://bugs.launchpad.net/lightdm/+bug/1438231 -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAP-bSRbX4kTC=d1g_qm_ev6mm4wf4hi_zv2beito5wq1h2f...@mail.gmail.com
Bug#780990: xserver-xorg-video-intel: hangs startx on logout if xrandr rotate is used in session
Package: xserver-xorg-video-intel Version: 2:2.21.15-2+b2 Severity: important Dear Maintainer, startx hangs on logout if xrandr rotate is used in session. There may be other ways to hang it but xrandr rotate is reliably repeatable. To reproduce: 1. Install minimal Jessie netinst system 2. apt-get install xorg blackbox # (bug does not seem to happen with gnome) 3. log in 4. startx 5. xrandr --output eDP1 --rotate left 6. right-click screen -> exit 7. terminal is hung. Nothing responds - can not change terminal, ctrl-c, or anything. Installing the latest upstream git appears to fix this bug. -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cap-bsrzd0bdco3csut-pjnndko-ec9oq7iuyyvi5z8qyluy...@mail.gmail.com
Bug#780668: libgl1-mesa-dri: WebGL Intel GPU Hang stuck on render ring
Package: libgl1-mesa-dri Version: 10.3.2-1 Severity: normal Dear Maintainer, IvyBridge GPU HD4000 Visit http://www.fishgl.com in Chromium or Iceweasel GPU hangs This was fixed upstream by commit fd31628 commit fd31628 Author: Iago Toral Quiroga Date: Tue Jul 29 12:36:31 2014 +0300 glsl: Optimize min/max expression trees Hang log: Mar 16 13:02:12 debian kernel: [drm] stuck on render ring Mar 16 13:02:12 debian kernel: [drm] GPU HANG: ecode 0:0x85ffeefa, in iceweasel [1818], reason: Ring hung, action: reset Mar 16 13:02:12 debian kernel: [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. Mar 16 13:02:12 debian kernel: [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel Mar 16 13:02:12 debian kernel: [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. Mar 16 13:02:12 debian kernel: [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. Mar 16 13:02:12 debian kernel: [drm] GPU crash dump saved to /sys/class/drm/card0/error Mar 16 13:02:14 debian kernel: [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off Mar 16 13:02:19 debian kernel: [drm] stuck on render ring Mar 16 13:02:19 debian kernel: [drm] GPU HANG: ecode 0:0x85ff7c1a, in iceweasel [1818], reason: Ring hung, action: reset Mar 16 13:02:21 debian kernel: [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off -- Package-specific info: glxinfo: name of display: :0.0 display: :0 screen: 0 direct rendering: Yes server glx vendor string: SGI server glx version string: 1.4 server glx extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_OML_swap_method, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_swap_control client glx vendor string: Mesa Project and SGI client glx version string: 1.4 client glx extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync GLX version: 1.4 GLX extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) Ivybridge Mobile OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.3.2 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: GL_3DFX_texture_compression_FXT1, GL_AMD_conservative_depth, GL_AMD_draw_buffers_blend, GL_AMD_performance_monitor, GL_AMD_seamless_cubemap_per_texture, GL_AMD_shader_trinary_minmax, GL_AMD_vertex_shader_layer, GL_AMD_vertex_shader_viewport_index, GL_ANGLE_texture_compression_dxt3, GL_ANGLE_texture_compression_dxt5, GL_APPLE_object_purgeable, GL_ARB_ES2_compatibility, GL_ARB_ES3_compatibility, GL_ARB_base_instance, GL_ARB_blend_func_extended, GL_ARB_buffer_storage, GL_ARB_clear_buffer_object, GL_ARB_clear_texture, GL_ARB_compressed_texture_pixel_storage, GL_ARB_conditional_render_inverted, GL_ARB_conservative_depth, GL_ARB_copy_buffer, GL_ARB_copy_image, GL_ARB_debug_output, GL_ARB_depth_buffer_float, GL_ARB_depth_clamp, GL_ARB
Bug#529178:
The Dell 2209WA had some DVI hardware glitch that caused these mysterious blackouts. See extended discussion: http://en.community.dell.com/support-forums/peripherals/f/3529/t/19257125 And upstream: https://bugs.freedesktop.org/show_bug.cgi?id=89110 Some users reported that Sapphire fixed the problem with a BIOS update but for other manufacturers it was always an issue. Using an active DisplayPort adaptor was the recommended workaround in the end. Final comment from Dell: "Posted by DELL-Chris I never could find a solid fix, several workarounds for PC, none for Macs. The issue does not occur for everyone and we could never replicate it in our lab."
Bug#757435:
One bug report suggests this is fixed by upgrading to kernel 3.16.5 or later.
Bug#748753:
On 2 October 2014 10:41, Julien Cristau wrote: > On Wed, Oct 1, 2014 at 11:24:41 +0100, Chris Bainbridge wrote: > >> Jessie gets frozen in 35 days. It would be a shame to see it released >> with buggy Intel GPU drivers that are no longer recommended or >> distributed by upstream. >> > Upstream clearly doesn't recommend anything newer, since the only thing > they've put out in the last year is a pile of git snapshots. Intel is now distributing their own drivers on 01.org - the latest version (2014Q3) includes xf86-video-intel 2.99.911. The recommendation to upgrade to at least 2.99.908 for important bug fixes came directly from their GPU developers. -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAP-bSRYFeezFbzTg5Fs4Uc8=Moh024UMp5bXNFtx6WNe=gw...@mail.gmail.com
Bug#748753:
Is there any chance of this being fixed in time for Jessie? Jessie gets frozen in 35 days. It would be a shame to see it released with buggy Intel GPU drivers that are no longer recommended or distributed by upstream. -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cap-bsrbdxgdm22ybm_ew2b-grvuwfrduorn3xazxdravvso...@mail.gmail.com
Bug#758934: Further info
Correction: It's when I set NoAccel to "True", not "False" that the segfault occurs. On Sat, Aug 30, 2014 at 10:03 AM, Chris Tillman wrote: > The segfault results when I set the "NoAccel" option under "Device". to > "False". It does not occur if I set it to "True" or don't set it. So I > guess that must mean it's in acceleration code. > > -- > Chris Tillman > Developer > -- Chris Tillman Developer
Bug#758934: Further info
The segfault results when I set the "NoAccel" option under "Device". to "False". It does not occur if I set it to "True" or don't set it. So I guess that must mean it's in acceleration code. -- Chris Tillman Developer
Bug#758934: xserver-xorg: Segfault with Rage 128 driving VGA monitor on powerpc (works on Wheezy)
Package: xserver-xorg Version: 1:7.7+7 Severity: important Tags: d-i Dear Maintainer, * What led up to the situation? First, I tried booting without creating an xorg.conf. The result was a repeating loop of the last 3 lines: [ 267.863] (==) RandR enabled [ 268.004] (II) SELinux: Disabled on system [ 268.028] (II) AIGLX: Screen 0 is not DRI2 capable [ 268.028] (EE) AIGLX: reverting to software rendering [ 268.085] (II) AIGLX: Loaded and initialized swrast [ 268.086] (II) GLX: Initialized DRISWRAST GL provider for screen 0 [ 268.324] (EE) R128(0): R128CCEWaitForIdle: CCE idle -9 [ 268.324] (EE) R128(0): Idle timed out, resetting engine... [ 268.324] (EE) R128(0): R128CCEWaitForIdle: CCE stop -9 [ 268.325] (EE) R128(0): R128CCEWaitForIdle: CCE start -9 [ 268.325] (EE) R128(0): R128CCEWaitForIdle: CCE idle -9 Next, I tried generating a config with X -configure. Same reult. Finally, I tried substituting the config which works under Wheezy on the same machine. That resulted in the reported segfault. * What exactly did you do (or not do) that was effective (or ineffective)? Nothing was effective to get X started. * What was the outcome of this action? No GUI * What outcome did you expect instead? GUI The segfault (full log attached below by reportbug): [ 127.035] (II) R128(0): Page flipping disabled [ 127.035] (!!) R128(0): For information on using the multimedia capabilities of this adapter, please see http://gatos.sf.net. [ 127.035] (--) Depth 24 pixmap format is 32 bpp [ 127.035] (II) R128(0): Acceleration of RENDER operations will be enabled upon successful loading of DRI and EXA [ 127.041] (WW) R128(0): Acceleration disabled, not initializing the DRI [ 127.042] (II) R128(0): Filling in EXA memory info [ 127.042] (II) R128(0): Acceleration disabled [ 127.042] (EE) [ 127.042] (EE) Backtrace: [ 127.043] (EE) 0: /usr/bin/X (xorg_backtrace+0x60) [0x20437130] [ 127.043] (EE) 1: /usr/bin/X (0x20234000+0x2085c0) [0x2043c5c0] [ 127.043] (EE) 2: linux-vdso32.so.1 (__kernel_sigtramp_rt32+0x0) [0x1003a0] [ 127.043] (EE) 3: /usr/lib/xorg/modules/drivers/r128_drv.so (0x1f508000+0xc718) [0x1f514718] [ 127.044] (EE) 4: /usr/lib/xorg/modules/drivers/r128_drv.so (0x1f508000+0xc700) [0x1f514700] [ 127.044] (EE) 5: /usr/bin/X (AddScreen+0x100) [0x2028bc90] [ 127.044] (EE) 6: /usr/bin/X (InitOutput+0x330) [0x202df880] [ 127.045] (EE) 7: /usr/bin/X (0x20234000+0x5c568) [0x20290568] [ 127.045] (EE) 8: /usr/bin/X (0x20234000+0x425a4) [0x202765a4] [ 127.045] (EE) 9: /lib/powerpc-linux-gnu/libc.so.6 (0x1fc7b000+0x232f4) [0x1fc9e2f4] [ 127.046] (EE) 10: /lib/powerpc-linux-gnu/libc.so.6 (0x1fc7b000+0x234b4) [0x1fc9e4b4] [ 127.046] (EE) [ 127.046] (EE) Segmentation fault at address 0xc [ 127.046] (EE) Fatal server error: [ 127.046] (EE) Caught signal 11 (Segmentation fault). Server aborting [ 127.047] (EE) [ 127.047] (EE) I get the same result using startx with this conf. Here is the conf. Section "ServerLayout" Identifier "X.org Configured" Screen 0 "Screen0" 0 0 # Screen 1 "Screen1" RightOf "Screen0" InputDevice"Mouse0" "CorePointer" InputDevice"Keyboard0" "CoreKeyboard" EndSection Section "Files" ModulePath "/usr/lib/xorg/modules" FontPath "/usr/share/fonts/X11/misc" FontPath "/usr/share/fonts/X11/cyrillic" FontPath "/usr/share/fonts/X11/100dpi/:unscaled" FontPath "/usr/share/fonts/X11/75dpi/:unscaled" FontPath "/usr/share/fonts/X11/Type1" FontPath "/usr/share/fonts/X11/100dpi" FontPath "/usr/share/fonts/X11/75dpi" FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType" FontPath "built-ins" EndSection Section "Module" Load "dbe" Load "dri2" Load "record" Load "glx" Load "dri" Load "extmod" EndSection Section "InputDevice" Identifier "Keyboard0" Driver "kbd" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/input/mice" Option "ZAxisMapping" "4 5 6 7" EndSection Section "Monitor" Identifier "Monitor0" VendorName "Monitor Vendor" ModelName"Monitor Model" Modeline "1024x768x60.0" 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync EndSection #Section "Monitor" # Identifier "Monitor1" # VendorName "Monitor Vendor" # ModelName"Monitor Model" #EndSection Section "Device" ### Available Driver options are:- ### Values: : integer, : float, : "True"/"False", ### : "String", : " Hz/kHz/MHz", ### : "%" ### [arg]: arg optional Option "NoAccel" "True" # [] #Option "SWcursor" # [] #Option
Bug#748753: closed by maximilian attems (Bug#748753: fixed in xserver-xorg-video-intel 2:2.99.911+git20140529-1~exp1)
On 30 May 2014 16:28, maximilian attems wrote: > On Fri, May 30, 2014 at 11:52:39AM +0100, Chris Bainbridge wrote: >> > I’m unsure if we want to upload random snapshot releases to sid, which >> > is why I didn’t do that. Feel free to upload it to experimental, though. >> >> I wasn't actually suggesting making a random snapshot of the git >> source from upstream. > > Whatever you personally wish is fine for your own, but may not be for > a distribution. In any case this is still only an experimental upload. > The chosen version is a Maintainers decision and I didn't see you step up > to such responsibility. Maximilian, firstly thank you for your work. I did not mean to sound unappreciative. If it would help, I would be happy to take responsibility for the decision to release video-intel-2.99.910 (or any other version recommended by upstream) to Debian unstable. The problem with putting an update into experimental is that it does not benefit the vast majority of users, who do not have experimental enabled. I did not open this bug just to fix my own personal problem, I opened this bug so that all Debian users with Intel graphics could get the benefit of a newer stack with significant bug fixes and which is being recommended by upstream. The Debian FAQ defines experimental as "packages and tools which are still being developed, and are still in the alpha testing stage. Users shouldn't be using packages from here, because they can be dangerous and harmful even for the most experienced people." imho this is not the appropriate description of a driver that Intel is already shipping as part of their own enablement stack. > A newer snapshot was deemed to have better hardware support thanks > to all fixes piled up in git, both for Haswell and beyond. Yes, I'm not against having a git snapshot for experimental use but it is not going to fix the issue of the drivers in sid and jessie being 6 months behind what Intel and Ubuntu are both shipping today. -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAP-bSRbghV1Sy9S6rXpmwhOfr-PSCcz1oQJ=jorozwzekzb...@mail.gmail.com
Bug#748753: closed by maximilian attems (Bug#748753: fixed in xserver-xorg-video-intel 2:2.99.911+git20140529-1~exp1)
> I’m unsure if we want to upload random snapshot releases to sid, which > is why I didn’t do that. Feel free to upload it to experimental, though. I wasn't actually suggesting making a random snapshot of the git source from upstream. The latest stable release from Intel is 2014Q1 which includes video-intel-2.99.910. Yes, it is a snapshot, but it is not a random one - it is the same one being used by Intel in the stable 1.0.5 release of their official Intel Graphics Installer. If it is good enough for Intel to use in a stable release of their graphics installer, then imho it ought to be good enough for Debian Unstable/Testing. 2.99.910 is also the version used in Ubuntu 14.04, which means it has already received much wider testing than any possible alternative snapshot. -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cap-bsrysp_npkddqoz4mgb1b7fjnoe_pohqqdoymuqnncrk...@mail.gmail.com
Bug#748753: xserver-xorg-video-intel: please update, jessie/sid version 2.21.15 is 9 months old
Package: xserver-xorg-video-intel Version: 2:2.21.15-2+b1 Severity: normal Dear Maintainer, Please release an updated version of xserver-xorg-video-intel. The latest version in Debian is 2.21.15, which was released by upstream 9 months ago. Since then there have been many bug fixes and performance improvements. (The latest release of the Intel Graphics Stack from 01.org is 2014Q1, which includes video-intel-2.99.910, upstream recommends upgrading to at least 2.99.908 for bug fixes). -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xserver-xorg-video-intel depends on: ii libc6 2.18-5 ii libdrm-intel1 2.4.54-1 ii libdrm22.4.54-1 ii libpciaccess0 0.13.2-1 ii libpixman-1-0 0.32.4-1 ii libudev1 204-8 ii libx11-6 2:1.6.2-1 ii libx11-xcb12:1.6.2-1 ii libxcb-dri2-0 1.10-2 ii libxcb-util0 0.3.8-2 ii libxcb11.10-2 ii libxv1 2:1.0.10-1 ii libxvmc1 2:1.0.8-1 ii xserver-xorg-core [xorg-video-abi-15] 2:1.15.1-1 xserver-xorg-video-intel recommends no packages. xserver-xorg-video-intel suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cap-bsrapes5nj6g83wcpl-vdffpnhcogkrimtytjegsgow6...@mail.gmail.com
Bug#747042: jessie installer errors: fbdev driver didn't call xf86SetGamma / Fatal server error
Package: xserver-xorg-video-fbdev-udeb Version: 1:0.4.4-1+b1 Booting debian-jessie-DI-a1-amd64-netinst.iso or debian-testing-amd64-netinst.iso(20140504) and starting Graphical Install, console shows: (WW) The fbdev driver didn't call xf86SetGamma to initialise the gamma values PLEASE FIX THE 'fbdev' DRIVER! (EE) Fatal server error: (EE) Server is already active for display 0 Despite this, xorg seems to work ok. Reproduced on laptop and VirtualBox. -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAP-bSRYpj=0pn_i1rgwamr-jwt3vx5yzn5shhputgzsxnkm...@mail.gmail.com
Bug#724944: [Intel-gfx] Patch for crashing intel server
On Sun, Nov 03, 2013 at 04:15:18PM +0100, Bas Wijnen wrote: > Hi Chris, > > I got a black screen while using your patch. > /sys/kernel/debug/dri/0/i915_gem_objects contents are shown below. The first > time is while the video is running; the second after stopping it. AFAICS, > there is no difference between them. Indeed, that scuppers my theory about it being an allocation failure to GEM space exhaustion. I am not sure what else to suggest to explain why it spontaneously fails to allocate that BO. You could try drm.debug=7, but searching for the failure would be like hunting for a needle in a haystack - and I'm not sure if we give any information as to how it fails, nor does libdrm_intel have any such debug. You can try disabling the uxa BO cache with Option "BufferCache" "false" and seeing if that makes any difference. -Chris -- Chris Wilson, Intel Open Source Technology Centre -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131104094558.gd15...@nuc-i3427.alporthouse.com
