Bug#1080475: mesa: please re-enable softpipe, at least on architectures where llvmpipe is not yet mature

[David Heidelberg]

On Wed, 4 Sep 2024 18:25:17 +0100 Simon McVittie  wrote:

Source: mesa
Severity: important
Justification: causes FTBFS in at least src:gtk4
Tags: ftbfs
X-Debbugs-Cc: g...@packages.debian.org, debian-ri...@packages.debian.org, 
debian-loonga...@packages.debian.org, debian-m...@packages.debian.org
User: debian-m...@packages.debian.org
Usertags: mips64el
User: debian-ri...@packages.debian.org
Usertags: riscv64

Historically, Mesa's llvmpipe used LLVM MCJIT, which supports a limited
range of architectures and will not add more, and this resulted in
several architectures having either a broken llvmpipe or no llvmpipe
support at all.

With the recent upload of Mesa 24.2.x to unstable, llvmpipe now uses
ORCJIT for architectures where MCJIT is unavailable. However, the ORCJIT
version of llvmpipe doesn't seem to be particularly mature yet (perhaps
unsurprisingly, it's very new!) and is crashing under some circumstances
on at least riscv64: #1080435.


Hello Simon,

Well, riscv64 wasn't well supported by MCJIT what I understood [1].



If softpipe was still enabled on at least the affected architectures,
then packages' test suites would be able to force its use via
GALLIUM_DRIVER=softpipe in the environment if necessary. At the
moment src:gtk4 does this on mips*, plus the powerpc and sparc* -ports
architectures, to avoid #1010838; the removal of the softpipe driver
means that this makes GL initialization fail, causing test failures and
a FTBFS (I'll report this as a separate RC bug in src:gtk4). I had hoped
to do the same for riscv64 to work around #1080435, but in fact this is
not possible for the same reason.


For slightly less supported architectures it definitely make it sense to 
keep softpipe around.


For the MIPS bug, I haven't found any report in upstream issues [2], is 
it reported?




While it's more important on the ORCJIT architectures, also enabling
softpipe on more mainstream architectures like x86 would make it easier
for maintainers to compare llvmpipe with softpipe (without having to
build their package on porterboxes that are often very slow), and easier
to get a consistent test result for all architectures.


On mainstream architectures, regular users won't likely need run against 
softpipe and for developers building Mesa isn't very hard task.
My argument here, is softpipe is unused in 99.99% scenarios and just 
occupy space.




For what it's worth, the upstream default (with -Dgallium-drivers=auto)
is to enable softpipe on all architectures. In the Debian
packaging, I believe this would be most easily done by reverting
1ba4b2499e875266f6fbd7ba20068fb569986286 "rules: Build softpipe or
llvmpipe depending on the arch, not both.".


Sure, the change is new in 24.2, so the default is conservative.

I would like to propose then to drop softpipe on 1st tier archs (at 
least x86, aarch64). At least with 24.3 release.


What do you think?

David

[1] 
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30343/diffs?commit_id=62143a4b21ddf9399031feab4898420ed53154f8

[2] https://gitlab.freedesktop.org/mesa/mesa/-/issues


Thanks,
smcv




--
David Heidelberg

Bug#1035848: xutils-dev: Please add support for riscv64 especially for imake

[David Doubrava]

Package: xutils-dev
Version: 1:7.7+6+b1
Severity: important
X-Debbugs-Cc: hpfou...@gmail.com

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
merged-usr: no
Architecture: riscv64

Kernel: Linux 5.15.0-starfive (SMP w/4 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages xutils-dev depends on:
ii  cpp4:12.2.0-1
ii  libc6  2.36-6

xutils-dev recommends no packages.

xutils-dev suggests no packages.

-- no debconf information

Bug#1000887: Info received ([Bug#1000887] xorg: X server segfaults when using xpdf)

[David Haworth]

Some more information:

* A colleague who owns a more modern Radeon GPU than mine (using
 the radeonsi drivers) doesn't have the same problem.

* If I start the X server with color depth 16 the problem goes away,
  but occurs with both 24 and 32 color depths.

>From these observations, I conclude that the problem lies in the full-color
handling of the standard radeon driver.

Bug#1001674: x11-common: Multiple monitors and starting app with window maximized

[David Lehrian]

Package: x11-common
Version: 1:7.7+22
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where 
appropriate ***


   * What led up to the situation?
I have a windows computer with multiple monitors. I typically run 
applications on Raspbian via X windows. I recently installed Raspbian 
Bullseye on a Pi 4 and launched Libreoffice Calc via X windows. It 
launched but it kept flickering on the screen. It would go full screen 
and then get smaller and then go full screen and then get smaller. It 
flashed back and forth between these two sizes and I had to kill it.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
I booted to the Raspbian desktop with a directly connected single 
monitor and launched Calc and it worked fine but I noticed it was full 
screen. I made it not full screen and closed it. I then launched it via 
X windows and it ran just fine when not full screen. I went back to the 
directly connected monitor and launched it and made it full screen and 
closed it.  Again I launched it via X windows and experienced the same 
flashing behavior. I tested this scenario on Raspbian Buster and it 
worked fine regardless if it was full screen or not.

   * What was the outcome of this action?
   * What outcome did you expect instead?

-- System Information:
Distributor ID: Raspbian
Description:    Raspbian GNU/Linux 11 (bullseye)
Release:    11
Codename:   bullseye
Architecture: armv7l

Kernel: Linux 5.10.63-v7l+ (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: 
LC_ALL set to en_US.UTF-8), LANGUAGE=en_US.UTF-8

Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages x11-common depends on:
ii  lsb-base  11.1.0+rpi1

Bug#1000887: [Bug#1000887] xorg: X server segfaults when using xpdf

[David Haworth]

Hi,

I used a remote ssh session to attach the Xorg process in gdb.

Judging by entry #1 of the stack trace, it might be a stack corruption.

Here's the session log:

GNU gdb (Debian 10.1-2) 10.1.90.20210103-git
Copyright (C) 2021 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/lib/xorg/Xorg...
(No debugging symbols found in /usr/lib/xorg/Xorg)
[?2004h(gdb) attach 3158
[?2004l
Attaching to program: /usr/lib/xorg/Xorg, process 3158
[New LWP 3160]
[New LWP 3161]
[New LWP 3164]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7f1adb4cdc96 in epoll_wait (epfd=4, events=0x7ffc2ba7bdd0, maxevents=256, 
timeout=275496) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
30  ../sysdeps/unix/sysv/linux/epoll_wait.c: No such file or directory.
[?2004h[?2004l
[?2004h(gdb) c
[?2004l
Continuing.

Thread 1 "Xorg" received signal SIGSEGV, Segmentation fault.
0x7f1accd8a03a in ?? ()
[?2004h[?2004l
[?2004h(gdb) info stack
[?2004l
#0  0x7f1accd8a03a in ?? ()
#1  0x0001 in ?? ()
#2  0x559ee4a86ab0 in ?? ()
#3  0x7f1ad9752ec8 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#4  0x7f1ad9754754 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#5  0x7f1ad96f857f in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#6  0x7f1ad9318f8a in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#7  0x7f1ace8f5af0 in ?? () from /usr/lib/xorg/modules/libglamoregl.so
#8  0x7f1ace8f6370 in ?? () from /usr/lib/xorg/modules/libglamoregl.so
#9  0x7f1ace8f8f30 in ?? () from /usr/lib/xorg/modules/libglamoregl.so
#10 0x559ee3522ed7 in ?? ()
#11 0x559ee343958f in ?? ()
#12 0x559ee343d41e in ?? ()
#13 0x559ee3441395 in ?? ()
#14 0x7f1adb3f7e4a in __libc_start_main (main=0x559ee342aba0, argc=6, 
argv=0x7ffc2ba7cc08, init=, fini=, 
rtld_fini=, stack_end=0x7ffc2ba7cbf8)
at ../csu/libc-start.c:314
#15 0x559ee342abda in _start ()
[?2004h(gdb) quit
[?2004l
[?2004hA debugging session is active.

Inferior 1 [process 3158] will be detached.

Quit anyway? (y or n) y
[?2004l
Detaching from program: /usr/lib/xorg/Xorg, process 3158
[Inferior 1 (process 3158) detached]

All the best,
Dave

Bug#1000887: xorg: X server segfaults when using xpdf

[David Haworth]

Package: xorg
Version: 1:7.7+23
Severity: normal

Dear Maintainer,

I'm running devuan (latest unstable). I reported this problem to the devuan
bug list, but they tell me that the xorg packages in devuan come from debian
without recompilation.

The X server crashes when I view one particular PDF file in xpdf. The file
is https://datasheets.raspberrypi.com/rp2040/rp2040-datasheet.pdf

There may be other PDF files that trigger the crash too, but there are many
that don't.

The crash is 100% repeatable by scrolling the table of contents in the
left-hand pane, either with the mouse scroll-wheel or with the thumb slider.

I've changed the generated content from reportbug to show the Xorg log file
after the crash. There's a backtrace at the end.

All the best,
Dave


-- Package-specific info:
X server symlink status:

lrwxrwxrwx 1 root root 13 Feb  9  2017 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 274 Nov 27 12:03 /usr/bin/Xorg

VGA-compatible devices on PCI bus:
--
01:05.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] RS780L [Radeon 3000] [1002:9616]

/etc/X11/xorg.conf does not exist.

Contents of /etc/X11/xorg.conf.d:
-
total 0

/etc/modprobe.d contains no KMS configuration files.

Kernel version (/proc/version):
---
Linux version 5.15.0-2-amd64 (debian-ker...@lists.debian.org) (gcc-11 (Debian 
11.2.0-12) 11.2.0, GNU ld (GNU Binutils for Debian) 2.37) #1 SMP Debian 
5.15.5-1 (2021-11-26)

Xorg X server log files on system:
--
-rw-r--r-- 1 root root 41033 Nov 30 17:17 /var/log/Xorg.0.log.xpdf-crash

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[27.495] 
X.Org X Server 1.20.13
X Protocol Version 11, Revision 0
[27.495] Build Operating System: linux Debian
[27.495] Current Operating System: Linux fionn 5.15.0-2-amd64 #1 SMP Debian 
5.15.5-1 (2021-11-26) x86_64
[27.495] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.15.0-2-amd64 
root=UUID=f5d906ea-6dd9-40c1-8977-16fc1cc37d60 ro quiet
[27.496] Build Date: 27 November 2021  11:03:35AM
[27.496] xorg-server 2:1.20.13-2 (https://www.debian.org/support) 
[27.496] Current version of pixman: 0.40.0
[27.496]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[27.496] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[27.496] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Nov 30 05:22:08 
2021
[27.754] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[27.811] (==) No Layout section.  Using the first Screen section.
[27.811] (==) No screen section available. Using defaults.
[27.811] (**) |-->Screen "Default Screen Section" (0)
[27.811] (**) |   |-->Monitor ""
[27.813] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[27.813] (==) Automatically adding devices
[27.813] (==) Automatically enabling devices
[27.813] (==) Automatically adding GPU devices
[27.813] (==) Max clients allowed: 256, resource mask: 0x1f
[27.976] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[27.976]Entry deleted from font path.
[28.123] (==) 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
[28.123] (==) ModulePath set to "/usr/lib/xorg/modules"
[28.123] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[28.123] (II) Loader magic: 0x55662f444e40
[28.123] (II) Module ABI versions:
[28.123]X.Org ANSI C Emulation: 0.4
[28.123]X.Org Video Driver: 24.1
[28.123]X.Org XInput driver : 24.1
[28.123]X.Org Server Extension : 10.0
[28.124] (++) using VT number 7

[28.124] (II) systemd-logind: logind integration requires -keeptty and 
-keeptty was not provided, disabling logind integration
[28.125] (II) xfree86: Adding drm device (/dev/dri/card0)
[28.133] (--) PCI:*(1@0:5:0) 1002:9616:1458:d000 rev 0, Mem @ 
0xd000/268435456, 0xfdee/65536, 0xfdd0/1048576, I/O @ 
0xee00/256, BIOS @ 0x/131072
[28.133] (II) LoadModule: "glx"
[28.192] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[28.507] (II) Module glx: vendor="X.Org Foundation"
[28.507]compiled for 1.20.13, module version = 1.0.0
[28.507]ABI clas

Re: [Pkg-phototools-devel] upcoming transition for webp package

[David Bremner]

Jeff Breidenbach  writes:

> Dear Debian colleagues,
>
> I'm writing because you maintain a package with a direct dependency in
> libwebp6. I'm planning to transition it to libweb8. Although I am not
> expecting any compatibility trouble, previous transitions have not always
> gone smoothly. So I'm sending this email as a heads up, and I've also just
> uploaded libweb8 to experimental. Thank you very much.
>
> Jeff

If you have not already done so, I recommend you discuss this with the
release team ASAP as we are in the transition freeze for bullseye.

d

Bug#972805: xserver-xorg-core: XWarpPointer() corrupts pointer position when mouse accelerated

[David Kuehling]

Package: xserver-xorg-core
Version: 2:1.20.4-1+deb10u1
Severity: normal
File: /usr/bin/X

Dear Maintainer,

I have been pulling my hair out about this problem.  Programs that make
heavy use of XWarpPointer() (like 'Kicad') were totally broken on my
system.  Turns out that speeding up the mouse using 'xset m' or ' xinput
set-prop xx 147' causes pointer position to become corrupt on the first
mouse-movement, after XWarpPointer() was called.

Below I attached an example program that invokes XWarpPointer() when a
key is pressed inside the window.  Bug consistently reproducable via:

 * compile test

   gcc -lX11 -Wall testwrap.c -o testwrap

 * configure your mouse to high speed.

   - find out the ID of your mouse via 'xinput list'.  I.e. for me it
 lists:
   
 Kensington Computer [..] Trackball id=19   [slave  pointer  (2)]

   - Use that ID to configure a higher speed
   
 input set-prop 19 147 3, 0, 0, 0, 3, 0, 0, 0, 1 

   - ('xset mouse 3 0' also sometimes triggers the bug, however it only
  seems to act on the first connected mouse and none of the
  hot-plugged mice.)

 * invoke ./testwrap, place mouse cursor inside black window

 * Make sure the mouse is steady and press any key.  Observe the mouse
   pointer jumping to the top-left of the window.  That's what it should
   do.

 * now move the mouse just a little.

   - I expect: mouse moves just a little
   
   - What happens: mouse jumps to the bottom-right-most corner of the
 screen
   
 * without accelerating the mouse, this does not happen.  Exactly same
   mis-behaviour happening in Kicad on most GUI operations.  Makes Kicad
   mostly unusable.

The only workaround (other than giving up on accelerating the mouse) for
me currently is to use LD_PRELOAD to fully disable XWarpPointer() for
e.g. Kicad.

cheers,

David

/* derived from examples found here:
 * http://xopendisplay.hilltopia.ca/index.html */
#include 
#include 

int main(int argc, char ** argv){
	int screen_num, width, height;
	unsigned long background, border;
	Window win;
	XEvent ev;
	Display *dpy;

	/* First connect to the display server */
	dpy = XOpenDisplay(NULL);
	if (!dpy) {fprintf(stderr, "unable to connect to display\n");return 7;}

	screen_num = DefaultScreen(dpy);
	background = BlackPixel(dpy, screen_num);
	border = WhitePixel(dpy, screen_num);

	width = 320;
	height = 200;

	win = XCreateSimpleWindow(dpy, DefaultRootWindow(dpy), /* display, parent */
		0,0, /* x, y: the window manager will place the window elsewhere */
		width, height, /* width, height */
		2, border, /* border width & colour, unless you have a window manager */
		background); /* background colour */

	/* tell the display server what kind of events we would like to see */
	XSelectInput(dpy, win, ButtonPressMask|StructureNotifyMask|KeyPressMask|KeyReleaseMask|KeymapStateMask);

	/* okay, put the window on the screen, please */
	XMapWindow(dpy, win);

	/* as each event that we asked about occurs, we respond.  In this
	 * case we note if the window's shape changed, and exit if a button
	 * is pressed inside the window */
	while(1){
		XNextEvent(dpy, &ev);
		switch(ev.type){
		case KeymapNotify:
			XRefreshKeyboardMapping(&ev.xmapping);
			break;
		case KeyPress: break; /* ignore these */
		case KeyRelease:
   XWarpPointer(dpy, None, win, 0, 0, 0, 0, 5, 5);
			break;
		case ButtonPress:
			XCloseDisplay(dpy);
			return 0;
		}
	}
}

Bug#963824: libgl1-mesa-dri: Segfault in iris_dri.so breaks several programs

[David Headland]

Package: libgl1-mesa-dri
Version: 20.1.1-1
Followup-For: Bug #963824

Hello all,

I've also seen what I think is the same issue myself, but I'm using version 
20.1.1-1 from testing rather than 20.1.2-1 from unstable. I can also add 
mythfrontend to the list of affected programs.

Given that this seems to affect multiple versions, I'm wondering if a change in 
another package is either the root cause, or has shown up an issue here that 
wasn't seen previously. I'm not great at tracing such things, but if I can 
provide any further information, please do let me know.

All the best,
-DH.

-- Package-specific info:
glxinfo:

name of display: localhost:10.0
display: localhost:10  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_no_error, 
GLX_ARB_create_context_profile, 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_import_context, GLX_EXT_libglvnd, GLX_EXT_no_config_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_make_current_read, 
GLX_SGI_swap_control
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_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_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_fbconfig_float, GLX_ARB_framebuffer_sRGB, 
GLX_ARB_get_proc_address, 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_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, 
GLX_EXT_visual_rating, GLX_MESA_copy_sub_buffer, GLX_MESA_query_renderer, 
GLX_OML_swap_method, GLX_SGIS_multisample, GLX_SGIX_fbconfig, 
GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read
Extended renderer info (GLX_MESA_query_renderer):
Vendor: VMware, Inc. (0x)
Device: llvmpipe (LLVM 10.0.0, 256 bits) (0x)
Version: 20.1.1
Accelerated: no
Video memory: 31046MB
Unified memory: no
Preferred profile: core (0x1)
Max core profile version: 3.3
Max compat profile version: 3.1
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.1
OpenGL vendor string: VMware, Inc.
OpenGL renderer string: llvmpipe (LLVM 10.0.0, 256 bits)
OpenGL core profile version string: 3.3 (Core Profile) Mesa 20.1.1
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_AMD_conservative_depth, GL_AMD_draw_buffers_blend, 
GL_AMD_gpu_shader_int64, GL_AMD_multi_draw_indirect, 
GL_AMD_query_buffer_object, GL_AMD_seamless_cubemap_per_texture, 
GL_AMD_shader_stencil_export, GL_AMD_shader_trinary_minmax, 
GL_AMD_texture_texture4, GL_AMD_vertex_shader_layer, 
GL_AMD_vertex_shader_viewport_index, GL_ANGLE_texture_compression_dxt3, 
GL_ANGLE_texture_compression_dxt5, GL_ARB_ES2_compatibility, 
GL_ARB_ES3_compatibility, GL_ARB_arrays_of_arrays, GL_ARB_base_instance, 
GL_ARB_blend_func_extended, GL_ARB_buffer_storage, 
GL_ARB_clear_buffer_object, GL_ARB_clear_texture, GL_ARB_clip_control, 
GL_ARB_compressed_texture_pixel_storage, GL_ARB_compute_shader, 
GL_ARB_conditional_render_inverted, GL_ARB_conservative_depth, 
GL_ARB_copy_buffer, GL_ARB_copy_image, GL_ARB_cull_distance, 
GL_ARB_debug_output, GL_ARB_depth_buffer_float, GL_ARB_depth_clamp, 
GL_ARB_derivative_control, GL_ARB_direct_state_access, 
GL_ARB_draw_buffers, GL_ARB_draw_buffers_blend, 
GL_ARB_draw_elements_base_vertex, GL_ARB_draw_indirect, 

Bug#945971: pull latest upstream version

[David Mandelberg]

Package: xkb-data
Version: 2.26-2
Severity: wishlist

Hi,

The latest upstream release is currently 2.28. Could you update this 
package please?


Upstream releases: 
https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/-/tags

Bug#944880: libgl1-mesa-dri: Civilization6 regression with mesa 19.2.3-1 and Radeon RX580

[David Härdeman]

Hi,

it's not just Civ6, but all OpenGL drivers/apps which are affected.

Known issue, and fixed in the Mesa 19.2.4 emergency release:

https://lists.freedesktop.org/archives/mesa-dev/2019-November/223773.html
https://gitlab.freedesktop.org/mesa/mesa/issues/2072
https://www.phoronix.com/scan.php?page=news_item&px=Mesa-19.2.4-Released

Regards,
David

Bug#675433: xterm: terminal bell randomly stops and requires a reboot to get back

[David Griffith]

My reply is at the bottom.  Please put your reply there too.
On Thu, 10 Oct 2019, Sven Joachim wrote:

Control: tags -1 + moreinfo

On 2012-08-19 19:22 +0700, Ivan Shmakov wrote:


Thomas Dickey  writes:
On Thu, May 31, 2012 at 11:53:05PM -0700, David Griffith wrote:


>> Package: xterm
>> Version: 278-1
>> Severity: normal

>> After a normal bootup, the terminal bell with Xterm works as
>> expected.  After some time it stops.  This happens with RXVT, Gnome
>> Terminal, and XFCE Terminal.

[…]

> If it happens with all of those, it's not xterm-specific (nor
> specific to xlibs).  Sounds more like a problem with the desktop or
> window manager.

… or the kernel.  Could you please check whether reloading the
pcspkr kernel module helps or not?  Like:

$ sudo rmmod pcspkr ; sudo modprobe pcspkr ;


Dave, do you still experience this problem?  If so, does reloading the
pcspkr module help?


I do, but it seems like the problem is coming from pulseaudio and/or 
systemd.



--
David Griffith
d...@661.org

A: Because it fouls the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

Bug#919796: mesa: Segmentation fault in dri2_query_wayland_buffer_wl

[John David Anglin]

Source: mesa
Version: 18.3.2-1
Severity: normal
Tags: patch

Dear Maintainer,

The qtwayland-opensource-src package fails to build from source on hppa
due a segmentation fault in dri2_query_wayland_buffer_wl running the
qtwayland-opensource-src testsuite.  See bug 919197 for details:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919197

The fault occurs because dri2_dpy is NULL and dri2_query_wayland_buffer_wl
fails to check for this circumstance.

The attached patch add NULL pointer checks to dri2_query_wayland_buffer_wl
and dri2_create_image_wayland_wl_buffer.  This fixes the build of
qtwayland-opensource-src.

Please apply or fix the code so NULL display pointers are not used.

Regards,
Dave Anglin

-- System Information:
Debian Release: buster/sid
  APT prefers buildd-unstable
  APT policy: (500, 'buildd-unstable'), (500, 'unstable')
Architecture: hppa (parisc64)

Kernel: Linux 4.14.94+ (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- ./src/egl/drivers/dri2/egl_dri2.c.save  2019-01-15 20:35:09.752730367 
-0500
+++ ./src/egl/drivers/dri2/egl_dri2.c   2019-01-15 20:37:32.753145310 -0500
@@ -1931,10 +1931,13 @@
_EGLImageAttribs attrs;
int32_t plane;
 
+   if (!dri2_dpy)
+  return NULL;
+ 
buffer = wayland_drm_buffer_get(dri2_dpy->wl_server_drm,
(struct wl_resource *) _buffer);
if (!buffer)
-   return NULL;
+  return NULL;
 
if (!_eglParseImageAttribList(&attrs, disp, attr_list))
   return NULL;
@@ -2849,6 +2852,9 @@
struct wl_drm_buffer *buffer;
const struct wl_drm_components_descriptor *format;
 
+   if (!dri2_dpy)
+  return EGL_FALSE;
+ 
buffer = wayland_drm_buffer_get(dri2_dpy->wl_server_drm, buffer_resource);
if (!buffer)
   return EGL_FALSE;

Bug#591430: xserver-xorg-core: "Maximum number of clients reached" hardcoded

[David Fries]

xserver-xorg-core 1.19 in stretch does have the option to increase the
client limit to 512, any chance of have this the default option?  I
only stumbled on this when I was looking for a different bug.

Section "ServerFlags"
Option "MaxClients"  "512"

I also think this bug report should be closed now that it is fixed
upstream and is in a Debian stable release.

-- 
David Fries 

Bug#909741: Acknowledgement (mesa-opencl-icd: Memory leak in clEnqueueNDRangeKernel())

[David Kuehling]

Also reported the issue to upstream:

https://bugs.freedesktop.org/show_bug.cgi?id=108087

Bug#909741: mesa-opencl-icd: Memory leak in clEnqueueNDRangeKernel()

[David Kuehling]

Note that this bug seems to be present in all versions of mesa 18.1.x [1]
but is fixed in mesa 18.2 [2].

[1] 
https://gitlab.freedesktop.org/mesa/mesa/blob/18.1/src/gallium/state_trackers/clover/core/kernel.hpp
[2] 
https://gitlab.freedesktop.org/mesa/mesa/blob/18.2/src/gallium/state_trackers/clover/core/kernel.hpp

Bug#909741: mesa-opencl-icd: Memory leak in clEnqueueNDRangeKernel()

[David Kuehling]

Package: mesa-opencl-icd
Version: 18.1.6-1~bpo9+1
Severity: normal

Dear Maintainer,

the mesa 18.1.6 version that is provided via debian-backports has a
memory leak in the functions that implement clEnqueueNDRangeKernel().

The root cause is that destructor
clover::kernel::scalar_argument::~scalar_argument() is never called, as
life-time is managed via a unique_ptr<> to the parent class 'argument'
which does not have a virtual destructor.  This leads to memory
allocated by member vector<> kernel::scalar_argument::_v to leak.

For me adding a virtual destructor fixes this specific leak:

--- src.orig/mesa-18.1.6/src/gallium/state_trackers/clover/core/kernel.hpp  
2018-08-13 18:42:38.0 +0200
+++ mesa-18.1.6/src/gallium/state_trackers/clover/core/kernel.hpp   
2018-09-27 10:17:16.689585453 +0200
@@ -75,6 +75,7 @@
  argument(const argument &arg) = delete;
  argument &
  operator=(const argument &arg) = delete;
+ virtual ~argument() = default;
 
  /// \a true if the argument has been set.
  bool set() const;

Maybe somebody more familiar with the sources could look through GCC
warnings or sanitizer output for whether more problems of that sort are
present throughout the Mesa sources?

This bug currently causes leela zero [1] to consume many gigabytes of
memory over time, making it impractical to run, see the corresponding
leela zero bug [2] ([2] also has more details like valgrind backtraces
of the leak in question).

cheers,

David

[1] http://zero.sjeng.org/
[2] https://github.com/gcp/leela-zero/issues/1823

-- Package-specific info:
glxinfo:

DISPLAY is not set.

X server symlink status:

lrwxrwxrwx 1 root root 13 Mar 22  2016 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 274 Oct 14  2017 /usr/bin/Xorg

VGA-compatible devices on PCI bus:
--
00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Carrizo [1002:9874] (rev e3)

/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.17.0-0.bpo.3-amd64 (debian-ker...@lists.debian.org) (gcc 
version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1)) #1 SMP Debian 4.17.17-1~bpo9+1 
(2018-08-27)

Xorg X server log files on system:
--
-rw-r--r-- 1 root root 32159 Mar 22  2016 /var/log/Xorg.1.log
-rw-r--r-- 1 root root 36921 Sep  5 21:54 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[   641.716] 
X.Org X Server 1.19.2
Release Date: 2017-03-02
[   641.716] X Protocol Version 11, Revision 0
[   641.716] Build Operating System: Linux 4.9.0-4-amd64 x86_64 Debian
[   641.716] Current Operating System: Linux mosquito2 4.17.0-0.bpo.3-amd64 #1 
SMP Debian 4.17.17-1~bpo9+1 (2018-08-27) x86_64
[   641.716] Kernel command line: BOOT_IMAGE=/vmlinuz-4.17.0-0.bpo.3-amd64 
root=/dev/mapper/yami-root ro quiet
[   641.716] Build Date: 16 October 2017  08:19:45AM
[   641.716] xorg-server 2:1.19.2-1+deb9u2 (https://www.debian.org/support) 
[   641.716] Current version of pixman: 0.34.0
[   641.716]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[   641.716] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   641.716] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Sep  1 06:24:09 
2018
[   641.807] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[   641.973] (==) No Layout section.  Using the first Screen section.
[   641.973] (==) No screen section available. Using defaults.
[   641.973] (**) |-->Screen "Default Screen Section" (0)
[   641.973] (**) |   |-->Monitor ""
[   641.977] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[   641.977] (==) Automatically adding devices
[   641.977] (==) Automatically enabling devices
[   641.977] (==) Automatically adding GPU devices
[   641.977] (==) Max clients allowed: 256, resource mask: 0x1f
[   642.044] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[   642.044]Entry deleted from font path.
[   642.231] (==) 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
[   642.231] (==) ModulePath set to "/usr/lib/xorg/modules"
[   642.231] (II) The server relies o

Bug#864998: Acknowledgement (xserver-xorg-video-qxl: Segault at login (at res change?))

[Dr. David Alan Gilbert]

I installed the debug symbols for the X server and captured with gdb:

Thread 1 "Xorg" received signal SIGSEGV, Segmentation fault.
0x7f3493990c13 in drmmode_show_cursor (crtc=0x557e0c384560)
at ../../src/qxl_drmmode.c:288
288 ../../src/qxl_drmmode.c: No such file or directory.
(gdb) bt full
#0  0x7f3493990c13 in drmmode_show_cursor (crtc=0x557e0c384560) at 
../../src/qxl_drmmode.c:288
xf86_config = 
cursor = 
ret = 
drmmode_crtc = 0x557e0c385030
drmmode = 0x557e0c3824b8
handle = 1
use_set_cursor2 = 1
#1  0x7f34939919f1 in drmmode_set_mode_major (crtc=0x557e0c384560, 
mode=0x557e0c384578, 
rotation=, x=, y=) at 
../../src/qxl_drmmode.c:256
pScrn = 
cursor = 
xf86_config = 0x557e0c3843d0
drmmode_crtc = 0x557e0c385030
drmmode = 
saved_x = 
saved_y = 0
saved_rotation = 1
saved_mode = {prev = 0x0, next = 0x0, name = 0x0, status = MODE_OK, 
type = 8, Clock = 63500, 
  HDisplay = 1024, HSyncStart = 1072, HSyncEnd = 1176, HTotal = 1328, 
HSkew = 0, VDisplay = 768, 
  VSyncStart = 771, VSyncEnd = 775, VTotal = 798, VScan = 0, Flags = 6, 
ClockIndex = 0, SynthClock = 0, 
  CrtcHDisplay = 1024, CrtcHBlankStart = 1024, CrtcHSyncStart = 1072, 
CrtcHSyncEnd = 1176, 
  CrtcHBlankEnd = 1328, CrtcHTotal = 1328, CrtcHSkew = 0, CrtcVDisplay 
= 768, CrtcVBlankStart = 768, 
  CrtcVSyncStart = 771, CrtcVSyncEnd = 775, CrtcVBlankEnd = 798, 
CrtcVTotal = 798, CrtcHAdjusted = 0, 
  CrtcVAdjusted = 0, PrivSize = 0, Private = 0x0, PrivFlags = 0, HSync 
= 47.8162651, VRefresh = 59.9201317}
output_ids = 
output_count = 
ret = 
i = 
fb_id = 
kmode = {clock = 63500, hdisplay = 1024, hsync_start = 1072, hsync_end 
= 1176, htotal = 1328, hskew = 0, 
  vdisplay = 768, vsync_start = 771, vsync_end = 775, vtotal = 798, 
vscan = 0, vrefresh = 0, flags = 6, 
  type = 0, name = '\000' }
pitch = 
height = 
qxl = 
#2  0x7f3493991d16 in drmmode_xf86crtc_resize (scrn=0x557e0c381830, 
width=1440, height=900)
at ../../src/qxl_drmmode.c:875
crtc = 
xf86_config = 0x557e0c3843d0
drmmode_crtc = 
drmmode = 0x557e0c3824b8
old_front = 0x557e0c3a1c70
front_bo = 0x557e0c3a1c70
qxl = 0x557e0c381e70
cpp = 
pitch = 5760
old_pitch = 1024
ret = 
i = 0
old_width = 1024
old_height = 768
old_fb_id = 61
#3  0x557e0a3b6e7e in xf86RandR12ScreenSetSize (pScreen=0x557e0c383550, 
width=1440, height=900, mmWidth=380, 
mmHeight=237) at ../../../../../../hw/xfree86/modes/xf86RandR12.c:702
pScrn = 0x557e0c381830
config = 0x557e0c3843d0
pRoot = 0x557e0c42ab10
pScrnPix = 
ret = 0
c = 
#4  0x557e0a408ab8 in ProcRRSetScreenSize (client=0x557e0c7336b0) at 
../../../../randr/rrscreen.c:289
stuff = 
pWin = 0x557e0c42ab10
pScreen = 
i = 
---Type  to continue, or q  to quit---
rc = 0
#5  0x557e0a3375e5 in Dispatch () at ../../../../dix/dispatch.c:479
result = 
start_tick = 740
#6  0x557e0a33b568 in dix_main (argc=11, argv=0x7ffed2bfc958, 
envp=)
at ../../../../dix/main.c:287
i = 
alwaysCheckForInput = {0, 1}
#7  0x7f349788c2b1 in __libc_start_main (main=0x557e0a3251e0 , 
argc=11, argv=0x7ffed2bfc958, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffed2bfc948)
at ../csu/libc-start.c:291
result = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {0, 5272008524909249332, 
93999825310192, 140732434205008, 0, 0, 
2028975241810412340, 2142820986808828724}, mask_was_saved = 
0}}, priv = {pad = {0x0, 0x0, 
  0x7ffed2bfc9b8, 0x7f349a015170}, data = {prev = 0x0, cleanup = 
0x0, canceltype = -759182920}}}
not_first_call = 
#8  0x557e0a32521a in _start ()

-- 
 -Open up your eyes, open up your mind, open up your code ---   
/ Dr. David Alan Gilbert|   Running GNU/Linux   | Happy  \ 
\dave @ treblig.org |   | In Hex /
 \ _|_ http://www.treblig.org   |___/

Bug#864998: xserver-xorg-video-qxl: Segault at login (at res change?)

[Dr. David Alan Gilbert]

Package: xserver-xorg-video-qxl
Version: 0.1.4+20161126git4d7160c-1
Severity: normal

Dear Maintainer,


   * What led up to the situation?
  Debian 9 fresh install in QEMU, qxl video; KDE desktop
  It worked on first boot, but crashed on 2nd login.
  I suspect the difference is that I switched screen res,
  which worked fine during the session; doesn't seem to want to 
  afterwards though

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
  See the x log below

   * What was the outcome of this action?
  Can't log back into my KDE session
   * What outcome did you expect instead?
  A happy KDE session

This qemu is running on Fedora 26; other guests are working so I think the bug 
here
is in the X qxl driver.

Dave

-- 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]: Red Hat, Inc. QXL paravirtual graphic 
card [1b36:0100] (rev 04)

/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.9.0-3-amd64 (debian-ker...@lists.debian.org) (gcc version 6.3.0 
20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.9.30-2 (2017-06-12)

Xorg X server log files on system:
--
-rw-r--r-- 1 root root 17217 Jun 18 14:34 /var/log/Xorg.0.log

Contents of last Xorg X server log file (/var/log/Xorg.0.log.old):
-
[   375.321] (--) Log file renamed from "/var/log/Xorg.pid-1532.log" to 
"/var/log/Xorg.0.log"
[   375.321] 
X.Org X Server 1.19.2
Release Date: 2017-03-02
[   375.321] X Protocol Version 11, Revision 0
[   375.321] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
[   375.321] Current Operating System: Linux debian9vm 4.9.0-3-amd64 #1 SMP 
Debian 4.9.30-2 (2017-06-12) x86_64
[   375.321] Kernel command line: BOOT_IMAGE=/vmlinuz-4.9.0-3-amd64 
root=/dev/mapper/debian9vm--vg-root ro quiet
[   375.321] Build Date: 03 March 2017  03:14:41PM
[   375.321] xorg-server 2:1.19.2-1 (https://www.debian.org/support) 
[   375.321] Current version of pixman: 0.34.0
[   375.321]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[   375.321] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   375.321] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Jun 18 14:34:33 
2017
[   375.321] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[   375.322] (==) No Layout section.  Using the first Screen section.
[   375.322] (==) No screen section available. Using defaults.
[   375.322] (**) |-->Screen "Default Screen Section" (0)
[   375.322] (**) |   |-->Monitor ""
[   375.322] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[   375.322] (==) Automatically adding devices
[   375.322] (==) Automatically enabling devices
[   375.322] (==) Automatically adding GPU devices
[   375.322] (==) Max clients allowed: 256, resource mask: 0x1f
[   375.322] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[   375.322]Entry deleted from font path.
[   375.322] (==) 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
[   375.322] (==) ModulePath set to "/usr/lib/xorg/modules"
[   375.322] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[   375.322] (II) Loader magic: 0x5619ecc04e00
[   375.322] (II) Module ABI versions:
[   375.322]X.Org ANSI C Emulation: 0.4
[   375.322]X.Org Video Driver: 23.0
[   375.322]X.Org XInput driver : 24.1
[   375.322]X.Org Server Extension : 10.0
[   375.323] (++) using VT number 7

[   375.323] (II) systemd-logind: logind integration requires -keeptty and 
-keeptty was not provided, disabling logind integration
[   375.323] (II) xfree86: Adding drm device (/dev/dri/card0)
[   375.328] (--) PCI:*(0:0:2:0) 1b36:0100:1af4:1100 rev 4, Mem @ 
0xf400/67108864, 0xf800/67108864, 0xfc054000/8192, I/O @ 0xc0c0/32, 
BIOS @ 0x/131072
[   375.328] (II) LoadModule: "glx"
[   375.328] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[   375.329] (II) Module glx: vendor="X.Org Foundation"
[   375.329]compiled for 1.19.2, module version = 1.0.0
[   375.329]ABI class: X.Org Server Exten

Bug#792223: mesa-utils: looking for a way to have glxinfo (end friends) installed for both amd64 and i386 at the same time

[David Smith]

I agree. I am constantly flipping back and forth between mesa-utils and
mesa-utils:i386.  I run a combination of games that are i386 and AMD64.
Sometimes when I upgrade for one reason or another, I lose GL acceleration
on either i386 or AMD64 due to a package conflict or some random package
problem in testing, or for some reason aptitude or apt-get choosing a
strange upgrade path that leaves me without hardware acceleration on one or
the other.  I need both a 64 bit and a 32 bit Mesa-utils so I can verify
hardware acceleration on both GL libraries.   Currently, mesa-utils
conflicts with itself on a different architecture which doesn't make much
sense to me.

Bug#863452: xterm fonts too small

[David Lawyer]

Package: xterm
Version: 327-2

I set the font to "huge" by pressing ctrl-rt-click.  While it's much larger
than before, it's still small.  I've used a real VT100 terminal a lot in
the past and the built in fonts were normally significantly larger than
what xterm calls "huge".  Of course the reason is likely that old bitmaps,
intended for the obsolete low resolution terminals of the early 1980's,
are being used for xterm..

So "huge" needs to be relabelled "small" (or perhaps "medium", etc.) and
larger fonts obtained.  On my console I use 16x32 font which is large.
Should xterm give the option of using the same fonts as for the console?
This would be of value if one has already set up the fonts for the
console, (as I have) since the default console fonts seem to also be way
too small.

David Lawyer

Bug#801401: xorg: xinit Mate desktop fails: "Cannot open /dev/tty0"

[David Branner]

Package: xorg
Followup-For: Bug #801401

Dear Maintainer,

Under version 1:7.7+18 this issue does not exist; when I upgrade to xorg
and xserver-xorg v. 1:7.7+19, I am no longer able to start the Mate
desktop using xinit. The error is

parse_vt_settings: Cannot open /dev/tty0 (No such file or directory)

Below I report first the full output including the error line (v.
1:7.7+18) and (after a line of ===) the output when I start the desktop
under v. 1:7.7.+19).

```
$ xinit

_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root

X.Org X Server 1.19.2
Release Date: 2017-03-02
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
Current Operating System: Linux localhost 3.18.0-13985-g8bf2eb2 #1 SMP PREEMPT 
Wed May 10 18:47:50 PDT 2017 x86_64
Kernel command line: cros_secure console= loglevel=7 init=/sbin/init 
cros_secure oops=panic panic=-1 root=/dev/dm-0 rootwait ro 
dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=1 dm="1 
vroot none ro 1,0 3584000 verity 
payload=PARTUUID=ced5a43b-0938-474f-a512-e31a5c04d43f/PARTNROFF=1 
hashtree=PARTUUID=ced5a43b-0938-474f-a512-e31a5c04d43f/PARTNROFF=1 
hashstart=3584000 alg=sha1 
root_hexdigest=acba5490b0c9fdc4f630ae704141e67910d16dc8 
salt=d06ac551a951f2ac038486c9ca001398ea49f33918501caf0fdb3b343389d507" noinitrd 
vt.global_cursor_default=0 kern_guid=ced5a43b-0938-474f-a512-e31a5c04d43f 
add_efi_memmap boot=local noresume noswap i915.modeset=1 tpm_tis.force=1 
tpm_tis.interrupts=0 nmi_watchdog=panic,lapic intel_idle.max_cstate=7  
Build Date: 03 March 2017  03:14:41PM
xorg-server 2:1.19.2-1 (https://www.debian.org/support) 
Current version of pixman: 0.34.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(++) Log file: "/tmp/Xorg.crouton.1.log", Time: Mon May 22 20:31:01 2017
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(EE) 
Fatal server error:
(EE) parse_vt_settings: Cannot open /dev/tty0 (No such file or directory)
(EE) 
(EE) 
Please consult the The X.Org Foundation support 
 at http://wiki.x.org
 for help. 
(EE) Please also check the log file at "/tmp/Xorg.crouton.1.log" for additional 
information.
(EE) 
(EE) Server terminated with error (1). Closing log file.
/usr/bin/xinit: giving up
/usr/bin/xinit: unable to connect to X server: Connection refused
/usr/bin/xinit: server error
```

==

Normally, the output from running xinit looks like this:

```
$ xinit

_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root

X.Org X Server 1.19.2
Release Date: 2017-03-02
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
Current Operating System: Linux localhost 3.18.0-13985-g8bf2eb2 #1 SMP PREEMPT 
Wed May 10 18:47:50 PDT 2017 x86_64
Kernel command line: cros_secure console= loglevel=7 init=/sbin/init 
cros_secure oops=panic panic=-1 root=/dev/dm-0 rootwait ro 
dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=1 dm="1 
vroot none ro 1,0 3584000 verity 
payload=PARTUUID=ced5a43b-0938-474f-a512-e31a5c04d43f/PARTNROFF=1 
hashtree=PARTUUID=ced5a43b-0938-474f-a512-e31a5c04d43f/PARTNROFF=1 
hashstart=3584000 alg=sha1 
root_hexdigest=acba5490b0c9fdc4f630ae704141e67910d16dc8 
salt=d06ac551a951f2ac038486c9ca001398ea49f33918501caf0fdb3b343389d507" noinitrd 
vt.global_cursor_default=0 kern_guid=ced5a43b-0938-474f-a512-e31a5c04d43f 
add_efi_memmap boot=local noresume noswap i915.modeset=1 tpm_tis.force=1 
tpm_tis.interrupts=0 nmi_watchdog=panic,lapic intel_idle.max_cstate=7  
Build Date: 03 March 2017  03:14:41PM
xorg-server 2:1.19.2-1 (https://www.debian.org/support) 
Current version of pixman: 0.34.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(++) Log file: "/tmp/Xorg.crouton.1.log", Time: Mon May 22 20:50:19 2017
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
method return time=1495500620.273049 sender=:1.13 -> destination=:1.299 
serial=3917 reply_serial=2
   boolean true
crouton: version 1-20170315143304~master:95589555
release: stretch
architecture: amd64
xmethod: xorg
targets: x11,extension,keyboard,cli-extra,gtk-extra
host: version 9334.69.0 (Official Build) stable-channel lars 
kernel: Linux localhost 3.18.0-13985-g8bf2eb2 #1 SMP PREEMPT Wed May 10 
18:47:50 PDT 2017 x86_64 GNU/Linux
freon: yes

(process:22673): Gtk-WARNING **: Locale not supported by C library.
Using the fallback 'C' locale.
_IceTransmkdir: Owner of /tmp/.ICE-unix should be set 

Bug#862160: xorg: Unable to set background image

[David Griffith]

Source: xorg
Version: 1:7.7+19
Severity: normal

Dear Maintainer,

I just now updated xorg to version 1:7.7+19 and upon logging out and 
restarting X11, I found that my wallpaper was set to the default blue 
swirl.  None of the usual methods for setting the wallpaper appear to 
work anymore.


-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64
 (x86_64)

Kernel: Linux 4.9.7-x86_64-linode80 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Bug#858142: xterm: 'xrdb -merge .Xresources' vs 'xrdb .Xresources'

[David Griffith]

This bug is also triggered if a face size of 12 is used.

After playing around with xrdb(1), I came to suspect there might be 
trouble in that program.  This is what I did:


Move .Xresources to .Xresources-foo, then log out and in again.  This 
ensures that your .Xresources file won't load.  When xterm is started, 
you'll get a much-too-small window and a visible underscore.


Then type "xrdb -merge .Xresources-foo".  I got an xterm with all my 
settings but now the underscore is invisible -- the buggy state.


Log out and in again.  Start an xterm and note that it's back to the 
much-too-small default.  Now type "xrdb .Xresources-foo" making sure not 
to use any flags, particularly "-merge".  This will cause xterm to have 
the desired settings.  Underscores are now visible.


Here's my .Xresources file:

xterm*faceName: DejaVu Sans Mono :antialias=true
xterm*faceSize: 12
XTerm*renderFont: true
XTerm*utf8: 1
xterm*vt100.initialFont: 3
xterm*loginShell: true
xterm*vt100*geometry: 80x24
xterm*saveLines: 2000
xterm*charClass: 33:48,35:48,37:48,43:48,45-47:48,64:48,95:48,126:48
xterm*foreground: rgb:ee/ee/ee
xterm*background: rgb:00/00/00


--
David Griffith
d...@661.org

A: Because it fouls the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

Bug#819877: xserver-xorg-video-intel: mixxx application crashes with error "i915BindProgram: Assertion `p->on_hardware == 0' failed"

[David Nadasi]

serio-1
E: ID_PATH_TAG=platform-i8042-serio-1
E: ID_SERIAL=noserial
E: MAJOR=13
E: MINOR=32
E: SUBSYSTEM=input
E: USEC_INITIALIZED=48197

P: /devices/platform/pcspkr/input/input6
E: DEVPATH=/devices/platform/pcspkr/input/input6
E: EV=40001
E: ID_FOR_SEAT=input-platform-pcspkr
E: ID_INPUT=1
E: ID_PATH=platform-pcspkr
E: ID_PATH_TAG=platform-pcspkr
E: ID_SERIAL=noserial
E: MODALIAS=input:b0010v001Fp0001e0100-e0,12,kramls1,2,fw
E: NAME="PC Speaker"
E: PHYS="isa0061/input0"
E: PRODUCT=10/1f/1/100
E: PROP=0
E: SND=6
E: SUBSYSTEM=input
E: TAGS=:seat:
E: USEC_INITIALIZED=202983

P: /devices/platform/pcspkr/input/input6/event5
N: input/event5
S: input/by-path/platform-pcspkr-event-spkr
E: DEVLINKS=/dev/input/by-path/platform-pcspkr-event-spkr
E: DEVNAME=/dev/input/event5
E: DEVPATH=/devices/platform/pcspkr/input/input6/event5
E: ID_INPUT=1
E: ID_PATH=platform-pcspkr
E: ID_PATH_TAG=platform-pcspkr
E: ID_SERIAL=noserial
E: MAJOR=13
E: MINOR=69
E: SUBSYSTEM=input
E: USEC_INITIALIZED=344147

P: /devices/virtual/input/input7
E: DEVPATH=/devices/virtual/input/input7
E: EV=33
E: ID_INPUT=1
E: ID_INPUT_KEY=1
E: KEY=40 0 10007 2102400 0 0
E:
MODALIAS=input:b0019vpe-e0,1,4,5,k8A,8D,94,99,E0,E1,E2,F0,166,ram4,lsfw1,5,
E: MSC=10
E: NAME="HP WMI hotkeys"
E: PHYS="wmi/input0"
E: PRODUCT=19/0/0/0
E: PROP=0
E: SUBSYSTEM=input
E: SW=22
E: TAGS=:seat:
E: USEC_INITIALIZED=744946

P: /devices/virtual/input/input7/event6
N: input/event6
E: BACKSPACE=guess
E: DEVNAME=/dev/input/event6
E: DEVPATH=/devices/virtual/input/input7/event6
E: ID_INPUT=1
E: ID_INPUT_KEY=1
E: MAJOR=13
E: MINOR=70
E: SUBSYSTEM=input
E: USEC_INITIALIZED=745245
E: XKBLAYOUT=fr
E: XKBMODEL=pc105
E: XKBVARIANT=latin9


DRM Information from dmesg:
---
[0.00] AGP: No AGP bridge found
[0.00] AGP: Checking aperture...
[0.00] AGP: No AGP bridge found
[1.752208] Linux agpgart interface v0.103
[1.752432] agpgart-intel :00:00.0: Intel GMA3150 Chipset
[1.752491] agpgart-intel :00:00.0: detected gtt size: 524288K
total, 262144K mappable
[1.752661] agpgart-intel :00:00.0: detected 8192K stolen memory
[1.753085] agpgart-intel :00:00.0: AGP aperture is 256M @ 0x4000
[   11.115135] [drm] Initialized drm 1.1.0 20060810
[   11.198304] [drm] Memory usable by graphics device = 512M
[   11.198316] [drm] Replacing VGA console driver
[   11.224254] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[   11.224260] [drm] Driver supports precise vblank timestamp query.
[   11.311201] [drm] initialized overlay support
[   11.333932] fbcon: inteldrmfb (fb0) is primary device
[   12.019851] i915 :00:02.0: fb0: inteldrmfb frame buffer device
[   12.067672] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on
minor 0


-- System Information:
Debian Release: 8.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages xserver-xorg-video-intel depends on:
ii  libc6  2.19-18+deb8u4
ii  libdrm-intel1  2.4.58-2
ii  libdrm22.4.58-2
ii  libpciaccess0  0.13.2-3+b1
ii  libpixman-1-0  0.32.6-3
ii  libudev1   215-17+deb8u4
ii  libx11-6   2:1.6.2-3
ii  libx11-xcb12:1.6.2-3
ii  libxcb-dri2-0  1.10-3+b1
ii  libxcb-dri3-0  1.10-3+b1
ii  libxcb-sync1   1.10-3+b1
ii  libxcb-util0   0.3.8-3
ii  libxcb11.10-3+b1
ii  libxcursor11:1.1.14-1+b1
ii  libxdamage11:1.1.4-2+b1
ii  libxext6   2:1.3.3-1
ii  libxfixes3 1:5.0.1-2+b2
ii  libxinerama1   2:1.1.3-1+b1
ii  libxrandr2 2:1.4.2-1+b1
ii  libxrender11:0.9.8-1+b1
ii  libxshmfence1  1.1-4
ii  libxtst6   2:1.2.2-1+b1
ii  libxv1 2:1.0.10-1+b1
ii  libxvmc1   2:1.0.8-2+b1
ii  xserver-xorg-core [xorg-video-abi-18]  2:1.16.4-1

xserver-xorg-video-intel recommends no packages.

xserver-xorg-video-intel suggests no packages.

-- no debconf information


-- 
David

Bug#814982: [xwayland] Reproducible segmentation fault when pluggin new screen

[David Schiller]

Hi,

I experience the same problem.
I temporarily fixed it by uncommenting "WaylandEnable=false" in
/etc/gdm3/daemon.conf. This prevents the problematic xwayland from even
loading up. It hasn't crashed since. Neither have I experienced side
effects from using gdm in this "legacy" xserver only mode.

So until there is a proper fix this might be more convenient than
downgrading the package and putting it on hold.

Dave

Bug#799686: This is now working

[David Creelman]

Hi,
I am now able to run glx apps. My screensavers work, freecad, etc.
I'm not exactly sure when the fix happened, but it is now no longer an
issue. Please feel free to close the log.
Regards,
David

Bug#810548: xserver-xorg-video-radeon: gpu lockup and black screen

[David G. Starkweather]

Package: xserver-xorg-video-radeon
Version: 1:7.6.1-1
Severity: important

Dear Maintainer,


The gpu occasionally locks up at random. Sometimes it can recover, other times 
it requires a restart.  GPU is radeon HD6850.

uname -a gives the following:

Linux debian 4.3.0-1-amd64 #1 SMP Debian 4.3.3-5 (2016-01-04) x86_64 GNU/Linux



-- Package-specific info:
X server symlink status:

lrwxrwxrwx 1 root root 13 Dec 15 21:53 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 274 Oct 27 19:43 /usr/bin/Xorg

VGA-compatible devices on PCI bus:
--
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Barts PRO [Radeon HD 6850] [1002:6739]

/etc/X11/xorg.conf does not exist.

/etc/X11/xorg.conf.d does not exist.

KMS configuration files:

/etc/modprobe.d/radeon-kms.conf:
  options radeon modeset=1

Kernel version (/proc/version):
---
Linux version 4.3.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 5.3.1 
20160101 (Debian 5.3.1-5) ) #1 SMP Debian 4.3.3-5 (2016-01-04)

Xorg X server log files on system:
--
-rw-r--r-- 1 root root 77056 Jan  8 18:40 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[26.061] 
X.Org X Server 1.17.3
Release Date: 2015-10-26
[26.061] X Protocol Version 11, Revision 0
[26.061] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
[26.061] Current Operating System: Linux debian 3.16.0-4-amd64 #1 SMP 
Debian 3.16.7-ckt20-1+deb8u2 (2016-01-02) x86_64
[26.061] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 
root=UUID=3deb7a19-abb9-4d82-9e7c-88e75229d5f2 ro quiet
[26.061] Build Date: 27 October 2015  11:41:02PM
[26.061] xorg-server 2:1.17.3-2 (http://www.debian.org/support) 
[26.062] Current version of pixman: 0.33.4
[26.062]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[26.062] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[26.062] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Jan  8 17:25:03 
2016
[26.387] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[26.596] (==) No Layout section.  Using the first Screen section.
[26.596] (==) No screen section available. Using defaults.
[26.596] (**) |-->Screen "Default Screen Section" (0)
[26.596] (**) |   |-->Monitor ""
[26.614] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[26.614] (==) Automatically adding devices
[26.614] (==) Automatically enabling devices
[26.614] (==) Automatically adding GPU devices
[26.888] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[26.888]Entry deleted from font path.
[27.285] (==) 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
[27.285] (==) ModulePath set to "/usr/lib/xorg/modules"
[27.285] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[27.285] (II) Loader magic: 0x7f345df1fde0
[27.285] (II) Module ABI versions:
[27.285]X.Org ANSI C Emulation: 0.4
[27.285]X.Org Video Driver: 19.0
[27.285]X.Org XInput driver : 21.0
[27.285]X.Org Server Extension : 9.0
[27.288] (EE) systemd-logind: failed to get session: PID 684 does not 
belong to any known session
[27.289] (II) xfree86: Adding drm device (/dev/dri/card0)
[27.292] (--) PCI:*(0:1:0:0) 1002:6739:174b:e174 rev 0, Mem @ 
0xd000/268435456, 0xfdde/131072, I/O @ 0xc000/256, BIOS @ 
0x/131072
[27.331] (II) LoadModule: "glx"
[27.420] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[27.800] (II) Module glx: vendor="X.Org Foundation"
[27.800]compiled for 1.17.3, module version = 1.0.0
[27.800]ABI class: X.Org Server Extension, version 9.0
[27.800] (==) AIGLX enabled
[27.800] (==) Matched ati as autoconfigured driver 0
[27.800] (==) Matched ati as autoconfigured driver 1
[27.800] (==) Matched modesetting as autoconfigured driver 2
[27.800] (==) Matched fbdev as autoconfigured driver 3
[27.800] (==) Matched vesa as autoconfigured driver 4
[27.800] (==) Assigned the driver to the xf86ConfigLayout
[27.800] (II) LoadModule: "ati"
[27.801] (II) Loading /usr/lib/xorg/modules/drivers/ati_drv.so
[27.

Bug#804110: xserver-xorg-video-nouveau: fresh install debian-8.2.0-amd64, Xfce yields black screen at login

[David Christensen]

On 11/13/2015 11:42 AM, David Christensen wrote:

Let me try again, using a stopwatch:

 0:00 push power button
 0:07 POST displayed
 0:12 GRUB menu displayed
 0:17 GRUB runs
 0:23 LUKS prompt displayed
 1:00 LUKS passphrase entered
 1:08 login screen displayed
 2:00 login as toor
 2:02 desktop displayed


Oops -- I pasted from the original dmesg.out file, not the new one. 
Here is dmesg output for the above via SSH (so I can't screw it up):


root@i72720qm:~# dmesg
[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Initializing cgroup subsys cpuacct
[0.00] 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-ckt11-1+deb8u5 (2015-10-09)
[0.00] Command line: BOOT_IMAGE=/vmlinuz-3.16.0-4-amd64 
root=/dev/mapper/sda3_crypt ro quiet

...
[4.980369] sd 0:0:0:0: [sda] 117231408 512-byte logical blocks: 
(60.0 GB/55.

8 GiB)
[4.980465] sd 0:0:0:0: [sda] Write Protect is off
[4.980471] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[4.980502] sd 0:0:0:0: [sda] Write cache: enabled, read cache: 
enabled, does

n't support DPO or FUA
[4.982171]  sda: sda1 sda2 sda3
[4.983005] sd 0:0:0:0: [sda] Attached SCSI disk
[4.990650] sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw 
xa/form2 cdda

tray
[4.990659] cdrom: Uniform CD-ROM driver Revision: 3.20
[4.991092] sr 1:0:0:0: Attached scsi CD-ROM sr0
[4.991593] sd 0:0:0:0: Attached scsi generic sg0 type 0
[4.991629] sr 1:0:0:0: Attached scsi generic sg1 type 5
[5.089918] device-mapper: uevent: version 1.0.3
[5.090119] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) 
initialised: dm-d

e...@redhat.com
[   23.499859] random: nonblocking pool is initialized
[   44.129909] NET: Registered protocol family 38
[   44.360169] raid6: sse2x15295 MB/s
[   44.428098] raid6: sse2x28011 MB/s
[   44.496017] raid6: sse2x4   10909 MB/s
[   44.496018] raid6: using algorithm sse2x4 (10909 MB/s)
[   44.496019] raid6: using ssse3x2 recovery algorithm
[   44.496292] xor: automatically using best checksumming function:
[   44.535972]avx   : 22491.000 MB/sec
[   44.538894] Btrfs loaded
...
[   48.495838] e1000e :00:19.0: irq 42 for MSI/MSI-X
[   48.599608] e1000e :00:19.0: irq 42 for MSI/MSI-X
[   48.599726] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   51.534416] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: Rx/Tx

[   51.534470] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   56.574118] dell_wmi: Received unknown WMI event (0x0)

So, a couple of delays.


David

Bug#804110: xserver-xorg-video-nouveau: fresh install debian-8.2.0-amd64, Xfce yields black screen at login

[David Christensen]

On 11/13/2015 10:26 AM, Sven Joachim wrote:

I see two notable things here:

- There is no sign of the i915 module being loaded, I guess the on-board
   graphics is disabled in the BIOS/UEFI?


These are the only things I see in CMOS setup that seem to be related to 
graphics:


  Settings ->
General ->
  System Information ->
Processor Information ->
  shows nothing about graphics
Device Information ->
  Video Controller   = NVIDIA N12P-NS2
  Video BIOS Version = 75.19.6A.01.02
  Video Memory   = 512 MB
  Panel Type = 15.6" FHD
  Native Resolution  = 1920 by 1080
Video ->
  Optimus ->
Enable Optimus   = disabled



- The boot seems to stall for 27 seconds.  That is probably unrelated to
   this bug, but if you want to find out why, systemd-analyze(1) is your
   friend.


Let me try again, using a stopwatch:

0:00 push power button
0:07 POST displayed
0:12 GRUB menu displayed
0:17 GRUB runs
0:23 LUKS prompt displayed
1:00 LUKS passphrase entered
1:08 login screen displayed
2:00 login as toor
2:02 desktop displayed

It looks repeatable:

[4.966532]  sda: sda1 sda2 sda3
[4.967006] sd 0:0:0:0: [sda] Attached SCSI disk
[4.974416] sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw 
xa/form2 cdda tray

[4.974419] cdrom: Uniform CD-ROM driver Revision: 3.20
[4.974609] sr 1:0:0:0: Attached scsi CD-ROM sr0
[4.975611] sd 0:0:0:0: Attached scsi generic sg0 type 0
[4.975702] sr 1:0:0:0: Attached scsi generic sg1 type 5
[5.067157] device-mapper: uevent: version 1.0.3
[5.067287] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) 
initialised: dm-de...@redhat.com

[   32.778218] random: nonblocking pool is initialized
[   34.848447] NET: Registered protocol family 38
[   35.074219] raid6: sse2x14711 MB/s
[   35.142138] raid6: sse2x27738 MB/s
[   35.210066] raid6: sse2x4   11132 MB/s
[   35.210067] raid6: using algorithm sse2x4 (11132 MB/s)
[   35.210068] raid6: using ssse3x2 recovery algorithm
[   35.210364] xor: automatically using best checksumming function:
[   35.250018]avx   : 22887.000 MB/sec
[   35.252889] Btrfs loaded


Perhaps it is related to LUKS (?).



I don't think I'll be able to solve the problem, but at least you
have an easy workaround.


You solved the original problem -- the graphical login manager now 
works.  Thank you.



David

Bug#804110: xserver-xorg-video-nouveau: fresh install debian-8.2.0-amd64, Xfce yields black screen at login

[David Christensen]

On 11/13/2015 08:42 AM, Sven Joachim wrote:

Can you please send the complete dmesg output?


Attached.



Probably something like this would work (see modules-load.d(5)):

# echo nouveau > /etc/modules-load.d/nouveau.conf

This would hopefully load the nouveau kernel module early enough.
However, I still don't understand why this apparently isn't done by
udev.


That worked -- now it boots to the graphical login manager.


Anything else?


David



dmesg.out.gz
Description: GNU Zip compressed data

Bug#804110: xserver-xorg-video-nouveau: fresh install debian-8.2.0-amd64, Xfce yields black screen at login

[David Christensen]

On 11/12/2015 02:05 PM, Sven Joachim wrote:

Please press 'e' rather than 'c' in the grub
menu and edit the line starting with "linux".


Okay:

linux   /vmlinuz-3.16.0-4-amd64 root=/dev/mapper/sda3_crypt\
 ro  quiet systemd.unit=multi-user.target


Then press Ctrl+x to boot.  I arrive at a text console.  Login as root:

root@i72720qm:~# lsmod | grep ^nouveau
nouveau  1122419  1


So, it appears that the nouveau kernel module is loaded.  Logout.  Login 
as unprivileged user.  Start X Windows:


toor@i72720qm:~$ startx


I arrive at the Xfce desktop.


When I log out, I arrive back at the text console where I left off.


So, now I have a work-around (that reminds me of ~10 years ago).


I would still like to get the graphical login manager working.


Please advise.


David

Bug#804110: xserver-xorg-video-nouveau: fresh install debian-8.2.0-amd64, Xfce yields black screen at login

[David Christensen]

On 11/12/2015 10:13 AM, Sven Joachim wrote:

Could you please start your system without X? On a standard Jessie
installation with systemd as init and gmd3 as display-manager, you can
add "systemd.unit=multi-user.target" to the kernel command line to
achieve that.


When I power-up, 'Debian GNU/Linux' is highlighted in the GRUB menu.  I 
press 'c', get a prompt, and enter:


grub> systemd.unit=multi-user.target

When I press , GRUB gives me another prompt:

grub>

When press  again, same as above.



Log in at the console and see if the nouveau kernel
module is loaded ("lsmod | grep ^nouveau").


If I let the machine boot by itself and then log in via SSH from another 
machine:


root@i72720qm:~# lsmod | grep ^nouveau
nouveau  1122419  2


It appears that the nouveau kernel module is already loaded.


Please advise.


David

Bug#804110: xserver-xorg-video-nouveau: fresh install debian-8.2.0-amd64, Xfce yields black screen at login

[David Christensen]

On 11/07/2015 12:32 AM, Sven Joachim wrote:

Fair enough, I won't bother you again then.  My apologies for
mistakenly thinking you would appreciate help.


First, I apologize for my earlier complaint about shipping product with 
known bugs.  Companies that refuse to disclose relevant technical 
information needed for open-source software development inflict the 
problem upon all of us.  And, Dell Latitude E6520 laptop computers like 
mine have both Intel HD Graphics and an Nvidia graphics card, which is a 
corner case:


https://en.wikipedia.org/wiki/Nvidia_Optimus


I *do* appreciate help.  But, I do not have the knowledge, skills, time, 
or interest to "figure out why [the nouveau kernel module] is not loaded 
earlier by udev".  If you would like to work together on this, I can run 
commands for you, post files, etc., so you can debug it remotely.  Tell 
me what you need.



David


p.s. Bumblebee is "a project aiming to support NVIDIA Optimus technology 
under Linux":


http://www.bumblebee-project.org/


p.p.s. debian-7.9.0-amd64-xfce-CD1 works OOTB

Bug#804110: xserver-xorg-video-nouveau: fresh install debian-8.2.0-amd64, Xfce yields black screen at login

[David Christensen]

On 11/05/2015 11:51 AM, Sven Joachim wrote:

On 11/05/2015 10:11 AM, Sven Joachim wrote:

Your logs show that the nouveau kernel module loads too late,

You need to figure out why it's not loaded earlier by udev then.


No, thanks.


David

Bug#804110: xserver-xorg-video-nouveau: fresh install debian-8.2.0-amd64, Xfce yields black screen at login

[David Christensen]

On 11/05/2015 10:11 AM, Sven Joachim wrote:

Thank you for your reply. :-)



Your logs show that the nouveau kernel module loads too late, did you
blacklist it?


No.



This is not going to work,


Correct.



see #700946.


So, the Debian project is shipping "stable" product with known Nvidia 
DOA bugs OOTB?  That's going to affect a *lot* of computers.




In your setup the situation is especially bad, since the Xorg vesa
driver and the nouveau kernel driver both get loaded and fight over the
card.


Is there a Debian amd64 version that works OOTB on Nvidia?


David

Bug#804110: xserver-xorg-video-nouveau: fresh install debian-8.2.0-amd64, Xfce yields black screen at login

[David Christensen]

Package: xserver-xorg-video-nouveau
Version: 1:1.0.11-1
Severity: important

Dear Maintainer,

Today I did a fresh install of debian-8.2.0-amd64 on a Dell Latitude E6520
with an Nvidia NVS-4200M (N12P-NS2) graphics adapter.

After rebooting, the login screen briefly flashes on the screen and then the
 screen goes black.

STFW I see various similar bugs/issues, but not an exact match.

David



-- Package-specific info:
X server symlink status:

lrwxrwxrwx 1 root root 13 Nov  4 12:57 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 2401376 Feb 10  2015 /usr/bin/Xorg

VGA-compatible devices on PCI bus:
--
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF119M [NVS 4200M] 
[10de:1056] (rev a1)

/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-ckt11-1+deb8u5 (2015-10-09)

Xorg X server log files on system:
--
-rw-r--r-- 1 root root 79357 Nov  4 18:31 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[45.976] 
X.Org X Server 1.16.4
Release Date: 2014-12-20
[45.976] X Protocol Version 11, Revision 0
[45.976] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
[45.976] Current Operating System: Linux i72720qm 3.16.0-4-amd64 #1 SMP 
Debian 3.16.7-ckt11-1+deb8u5 (2015-10-09) x86_64
[45.976] Kernel command line: BOOT_IMAGE=/vmlinuz-3.16.0-4-amd64 
root=/dev/mapper/sda3_crypt ro quiet
[45.977] Build Date: 11 February 2015  12:32:02AM
[45.977] xorg-server 2:1.16.4-1 (http://www.debian.org/support) 
[45.977] Current version of pixman: 0.32.6
[45.977]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[45.977] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[45.977] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Nov  4 18:31:19 
2015
[45.978] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[45.980] (==) No Layout section.  Using the first Screen section.
[45.980] (==) No screen section available. Using defaults.
[45.980] (**) |-->Screen "Default Screen Section" (0)
[45.980] (**) |   |-->Monitor ""
[45.980] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[45.980] (==) Automatically adding devices
[45.980] (==) Automatically enabling devices
[45.980] (==) Automatically adding GPU devices
[45.981] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[45.981]Entry deleted from font path.
[45.983] (==) 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
[45.983] (==) ModulePath set to "/usr/lib/xorg/modules"
[45.983] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[45.983] (II) Loader magic: 0x7f9c03639d80
[45.983] (II) Module ABI versions:
[45.983]X.Org ANSI C Emulation: 0.4
[45.983]X.Org Video Driver: 18.0
[45.983]X.Org XInput driver : 21.0
[45.983]X.Org Server Extension : 8.0
[45.985] (--) PCI:*(0:1:0:0) 10de:1056:1028:0494 rev 161, Mem @ 
0xe300/16777216, 0xd000/268435456, 0xe000/33554432, I/O @ 
0x3000/128, BIOS @ 0x/524288
[45.985] (II) LoadModule: "glx"
[45.985] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[46.000] (II) Module glx: vendor="X.Org Foundation"
[46.000]compiled for 1.16.4, module version = 1.0.0
[46.000]ABI class: X.Org Server Extension, version 8.0
[46.000] (==) AIGLX enabled
[46.000] (==) Matched nouveau as autoconfigured driver 0
[46.000] (==) Matched nv as autoconfigured driver 1
[46.000] (==) Matched modesetting as autoconfigured driver 2
[46.000] (==) Matched fbdev as autoconfigured driver 3
[46.000] (==) Matched vesa as autoconfigured driver 4
[46.000] (==) Assigned the driver to the xf86ConfigLayout
[46.000] (II) LoadModule: "nouveau"
[46.002] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
[46.005] (II) Module nouveau: vendor="

Bug#799686: nouveau: Unable to launch any glx based exes

[David Creelman]

Hi Sven,
Thanks for the info. Nice to know it's not a module bug.
Any idea when llvm3.5v5 will come to testing?
Regards
David

On Tue, 22 Sep 2015 3:10 AM Sven Joachim  wrote:

> Control: reassign -1 libgl1-mesa-dri 10.6.3-1
> Control: tags -1 + moreinfo
>
> On 2015-09-21 16:11 +0200, David Creelman wrote:
>
> > Package: xserver-xorg-video-nouveau
> > Version: 1:1.0.11-1+b1
> > Severity: important
> > File: nouveau
> >
> > Dear Maintainer,
> >
> > This started happening about a month ago. May be because of nouveau, may
> be a glx bug?
> > Please forgive if it's not nouveau. Any idea how I can find out more
> about what is not working ?
> > Happy to help if you need more information.
> >
> > I run apt-get update; apt-get dist-upgrade several times a week,
> something must have been updated.. Not sure when.
> > Discovered it first when trying to run a gl based screen saver. Needed
> to restart my machine
> > Once I worked out it was xscreensaver failing, I ran the xscreensaver
> exe in  a window rather than fullscreen
> > and noticed that it started up black and was kind of locked, ie. even if
> I did ctrl-c, the window wouldn't die
> > without xkill.
> > A screensaver to show this issue is voronoi under xscreensaver.
> >
> > Have tried reinstalling (via apt-get purge xserver-xorg, xfce4 and then
> apt-get install of same).
> >
> > Still getting the same error when starting anything that uses glx
>
> That's a bug in the 3D driver, reassigning to that package.
>
> > I had hoped that I'd get glx apps working again, but no luck I'm afraid.
>
> You could try libgl1-mesa-dri from unstable.  It depends on libllvm3.5v5
> which conflicts with the libllvm3.5 package though, so you might only
> want to try that if you don't have other packages depending on
> libllvm3.5.
>
> Good luck,
> Sven
>

Bug#799686: nouveau: Unable to launch any glx based exes

[David Creelman]

Package: xserver-xorg-video-nouveau
Version: 1:1.0.11-1+b1
Severity: important
File: nouveau

Dear Maintainer,

This started happening about a month ago. May be because of nouveau, may be a 
glx bug?
Please forgive if it's not nouveau. Any idea how I can find out more about what 
is not working ?
Happy to help if you need more information.

I run apt-get update; apt-get dist-upgrade several times a week, something must 
have been updated.. Not sure when.
Discovered it first when trying to run a gl based screen saver. Needed to 
restart my machine
Once I worked out it was xscreensaver failing, I ran the xscreensaver exe in  a 
window rather than fullscreen
and noticed that it started up black and was kind of locked, ie. even if I did 
ctrl-c, the window wouldn't die
without xkill.
A screensaver to show this issue is voronoi under xscreensaver.

Have tried reinstalling (via apt-get purge xserver-xorg, xfce4 and then apt-get 
install of same).

Still getting the same error when starting anything that uses glx

I had hoped that I'd get glx apps working again, but no luck I'm afraid.


-- 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:
--
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G72M [GeForce Go 
7400] [10de:01d8] (rev a1)

/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.1.0-2-686-pae (debian-ker...@lists.debian.org) (gcc version 
4.9.3 (Debian 4.9.3-3) ) #1 SMP Debian 4.1.6-1 (2015-08-23)

Xorg X server log files on system:
--
-rw-r--r-- 1 root root 32768 Mar 18  2014 /var/log/Xorg.1.log
-rw-r--r-- 1 root root 41163 Sep 21 22:47 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[93.830] 
X.Org X Server 1.17.2
Release Date: 2015-06-16
[93.830] X Protocol Version 11, Revision 0
[93.830] Build Operating System: Linux 3.16.0-4-amd64 i686 Debian
[93.830] Current Operating System: Linux laplace 4.1.0-2-686-pae #1 SMP 
Debian 4.1.6-1 (2015-08-23) i686
[93.830] Kernel command line: BOOT_IMAGE=/vmlinuz-4.1.0-2-686-pae 
root=/dev/mapper/laplace-root ro quiet
[93.830] Build Date: 11 August 2015  10:03:42AM
[93.830] xorg-server 2:1.17.2-1.1 (http://www.debian.org/support) 
[93.830] Current version of pixman: 0.33.2
[93.830]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[93.830] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[93.830] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Sep 21 16:15:43 
2015
[94.069] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[94.183] (==) No Layout section.  Using the first Screen section.
[94.183] (==) No screen section available. Using defaults.
[94.183] (**) |-->Screen "Default Screen Section" (0)
[94.183] (**) |   |-->Monitor ""
[94.185] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[94.185] (==) Automatically adding devices
[94.185] (==) Automatically enabling devices
[94.185] (==) Automatically adding GPU devices
[94.405] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[94.405]Entry deleted from font path.
[94.923] (==) 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
[94.923] (==) ModulePath set to "/usr/lib/xorg/modules"
[94.923] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[94.923] (II) Loader magic: 0x802d76c0
[94.923] (II) Module ABI versions:
[94.923]X.Org ANSI C Emulation: 0.4
[94.923]X.Org Video Driver: 19.0
[94.923]X.Org XInput driver : 21.0
[94.923]X.Org Server Extension : 9.0
[94.924] (II) xfree86: Adding drm device (/dev/dri/card0)
[94.926] (--) PCI:*(0:1:0:0) 10de:01d8:1028:01cc rev 161, Mem @ 
0xed00/16777216, 0xd000/268435456, 0xee00/16777216, BIOS @ 
0x/131072
[94.974] (II) LoadModule: "glx"
[95.091] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[95.971] (II) Module glx: vendor="X.Org Foundation"
[95.972]compiled for 1.17.2, module version = 1.0.0
[95.972]ABI class: X.Org Serve

Bug#734154: (no subject)

[David Demelier]

I have the same issue with my HP Probook 4510s and the Debian 8 
graphical installer.


--
David Demelier


--
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/556dd1fa.5040...@gmail.com

Bug#787538: New compose sequences for Esperanto

[David Starner]

Package: libx11-data
Version: 2:1.6.3-1
Severity: wishlist

Is there way we could get

   : "Ĉ"   U0108 # LATIN CAPITAL LETTER C WITH
CIRCUMFLEX
   : "Ĉ"   U0108 # LATIN CAPITAL LETTER C WITH
CIRCUMFLEX
   : "ĉ"   U0109 # LATIN SMALL LETTER C WITH CIRCUMFLEX
   : "Ĝ"   U011C # LATIN CAPITAL LETTER G WITH
CIRCUMFLEX
   : "Ĝ"   U011C # LATIN CAPITAL LETTER G WITH
CIRCUMFLEX
   : "ĝ"   U011D # LATIN SMALL LETTER G WITH CIRCUMFLEX
   : "Ĥ"   U0124 # LATIN CAPITAL LETTER H WITH
CIRCUMFLEX
   : "Ĥ"   U0124 # LATIN CAPITAL LETTER H WITH
CIRCUMFLEX
   : "ĥ"   U0125 # LATIN SMALL LETTER H WITH CIRCUMFLEX
   : "Ĵ"   U0134 # LATIN CAPITAL LETTER J WITH
CIRCUMFLEX
   : "Ĵ"   U0134 # LATIN CAPITAL LETTER J WITH
CIRCUMFLEX
   : "ĵ"   U0135 # LATIN SMALL LETTER J WITH CIRCUMFLEX
   : "Ŝ"   U015C # LATIN CAPITAL LETTER S WITH
CIRCUMFLEX
   : "Ŝ"   U015C # LATIN CAPITAL LETTER S WITH
CIRCUMFLEX
   : "ŝ"   U015D # LATIN SMALL LETTER S WITH CIRCUMFLEX
   : "Ŭ"   U016C # LATIN CAPITAL LETTER U WITH BREVE
   : "Ŭ"   U016C # LATIN CAPITAL LETTER U WITH BREVE
   : "ŭ"   U016D # LATIN SMALL LETTER U WITH BREVE

added to /usr/share/X11/locale/en_US.UTF-8/Compose ? They correspond to
standard ASCIIizations of Esperanto, and they're a lot easier then
Multi_key Shift 9. They don't conflict with anything else in the compose
file.

Bug#784626: x11-common: Hi,

[David John Summers]

On 07/05/15 16:38, Julien Cristau wrote:

On Thu, May  7, 2015 at 16:02:35 +0100, David John Summers wrote:


On 07/05/15 14:42, Julien Cristau wrote:

On Thu, May  7, 2015 at 10:22:29 +0100, David Summers wrote:


Package: x11-common
Version: 1:7.7+8
Severity: normal

Dear Maintainer,

With the latest update to sid x11 released a day or so ago (1:7.7+8) x
fails to start.

This has be traced to /usr/bin/X (wrapper for X) is not configured, and
/etc/X11/xinit/xserverrc refers to this.


"Not configured" meaning?

Cheers,
Julien

Not configured meaning:

# ls -l /usr/bin/X
ls: cannot access /usr/bin/X: No such file or directory


That file is part of the xserver-xorg package.  Do you have that
installed?  If yes, does "dpkg-divert --list /usr/bin/X" output
anything?  If not, why not?

Cheers,
Julien

Bingo.

For some reason I had xserver-xorg-core installed, but not xserver-xorg. 
Whats strange is it was fine before the recent upgrade.


Anyway all fixed now, thanks for your help. I should have picked up on 
this one myself (or rather I had checked which package /usr/bin/X lived 
in - and for some reason identified x11-common ; mea culpa).


Thanks,

David.


--
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/554b941e.2090...@summers5913.freeserve.co.uk

Bug#784626: x11-common: Hi,

[David John Summers]

On 07/05/15 14:42, Julien Cristau wrote:

On Thu, May  7, 2015 at 10:22:29 +0100, David Summers wrote:


Package: x11-common
Version: 1:7.7+8
Severity: normal

Dear Maintainer,

With the latest update to sid x11 released a day or so ago (1:7.7+8) x
fails to start.

This has be traced to /usr/bin/X (wrapper for X) is not configured, and
/etc/X11/xinit/xserverrc refers to this.


"Not configured" meaning?

Cheers,
Julien

Not configured meaning:

# ls -l /usr/bin/X
ls: cannot access /usr/bin/X: No such file or directory


--
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/554b7e8b.9080...@summers5913.freeserve.co.uk

Bug#784626: x11-common: Hi,

[David Summers]

Package: x11-common
Version: 1:7.7+8
Severity: normal

Dear Maintainer,

With the latest update to sid x11 released a day or so ago (1:7.7+8) x 
fails to start.

This has be traced to /usr/bin/X (wrapper for X) is not configured, and 
/etc/X11/xinit/xserverrc refers to this.

Now I've hacked /etc/X11/xinit/xserverrc to point to /usr/bin/Xorg

This means I can start X - but only as root, as not surprising permissions
to start X where in the /usr/bin/X wrapper.

Any ideas of a better fix? I could just create a link with the right 
sticky bit set - but seems better to fix at source.

Thanks,

David 

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 4.0.0 (SMP w/4 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)

Versions of packages x11-common depends on:
ii  debconf [debconf-2.0]  1.5.56
ii  lsb-base   4.1+Debian13+nmu1

x11-common recommends no packages.

x11-common suggests no packages.

-- debconf information:
* x11-common/xwrapper/allowed_users: Console Users Only
  x11-common/xwrapper/actual_allowed_users: console


-- 
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/20150507092229.6268.95395.report...@summers.lan

Bug#781393: xserver-xorg-video-intel: double free or corruption (!prev) during xrandr from mobile to docked (Configure crtc 0 failed)

[David Sheets]

On Sat, Mar 28, 2015 at 2:07 PM, David Sheets  wrote:
> Package: xserver-xorg-video-intel
> Version: 2:2.21.15-2+b2
> Severity: important
>
> Dear Maintainer,
>
> On a ThinkPad T430, when performing a mobile suspend with all but LVDS1
> disconnected and resuming in a dual-head dock, executing
>
> ['xrandr', '--output', 'LVDS1', '--off', '--output', 'HDMI2', '--gamma',
> '1.0:1.0:1.0', '--mode', '1920x1200', '--pos', '0x0', '--rate', '59.95',
> '--reflect', 'normal', '--rotate', 'left', '--transform',
> '1,0,0,0,1,0,0,0,1']
>
> results in
>
> "xrandr: Configure crtc 0 failed"
>
> printed to stderr and exit code 1. On VT 8, the message
>
> *** Error in `/usr/bin/X': double free or corruption (!prev): 
> 0x7f65b0f02340 ***
>
> is printed. When using
> xserver-xorg-video-intel_2.99.917-1~exp1_amd64.deb, the problem does not
> occur.
>
> After first occurrence, X seems to still be stable (ha!). At second
> occurrence (with a duplicated VT 8 message), X does not come back on any
> displays but machine appears stable, console is usable, and ACPI
> shutdown fine. (I think this is true but I haven't ruthlessly checked the 
> failure
> mode.) I have an (maybe unrelated) issue with the external displays
> appearing disconnected but still with resolutions and an odd trailing
> resolution record when using xrandr -q after dock -> mobile. I've not
> yet checked whether this influences the failure mode.

It appears to only happen after I have explicitly turned off the
mapped/in use displays and then redocked. I occasionally also see:

X Error of failed request:  BadMatch (invalid parameter attributes)
  Major opcode of failed request:  140 (RANDR)
  Minor opcode of failed request:  7 (RRSetScreenSize)
  Serial number of failed request:  43
  Current serial number in output stream:  45

in the logs and one of the docked monitors fails to get mapped.
Running xrandr to map the truant display once the system is awake
appears to always work, though.

Sometimes other, potentially related things are also printed to the
error console:

^@^@^@

and

usb 2-1.5.3: set resolution quirk: cval->res = 384

I don't know how relevant these messages are and I can't seem to
reproduce the issue 100% of the time any more. :-( Maybe the severity
should be 'normal'?

I'll keep this issue updated with other potentially relevant info.

Thank you!

> Please let me know if you need more info, would like me to do debugging,
> or need package version bisection (if you can point me to some info
> about how to build and test this stuff... I'm semi-competent but not familiar
> with this subsystem).
>
> Thank you,
>
> David Sheets
>
> -- Package-specific info:
> X server symlink status:
> 
> lrwxrwxrwx 1 root root 13 Oct 10  2012 /etc/X11/X -> /usr/bin/Xorg
> -rwxr-xr-x 1 root root 2401376 Feb 11 00:35 /usr/bin/Xorg
>
> Diversions concerning libGL are in place
> 
> diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.2.0 to 
> /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.2.0 by glx-diversions
> diversion of /usr/lib/libGL.so.1 to /usr/lib/mesa-diverted/libGL.so.1 by 
> glx-diversions
> diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2.0.0 to 
> /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so.2.0.0 by 
> glx-diversions
> diversion of /usr/lib/libGLESv2.so.2 to /usr/lib/mesa-diverted/libGLESv2.so.2 
> by glx-diversions
> diversion of /usr/lib/arm-linux-gnueabihf/libGL.so to 
> /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so by glx-diversions
> diversion of /usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1.1.0 to 
> /usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv1_CM.so.1.1.0 by 
> glx-diversions
> diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so to 
> /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so by glx-diversions
> diversion of /usr/lib/i386-linux-gnu/libGLESv2.so.2 to 
> /usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so.2 by glx-diversions
> diversion of /usr/lib/x86_64-linux-gnu/libGLESv2.so.2 to 
> /usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so.2 by glx-diversions
> diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.2 to 
> /usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.2 by glx-diversions
> diversion of /usr/lib/libGLESv1_CM.so.1.1.0 to 
> /usr/lib/mesa-diverted/libGLESv1_CM.so.1.1.0 by glx-diversions
> diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so.1 to 
> /usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so.1 by glx-di

Bug#781393: xserver-xorg-video-intel: double free or corruption (!prev) during xrandr from mobile to docked (Configure crtc 0 failed)

[David Sheets]

Package: xserver-xorg-video-intel
Version: 2:2.21.15-2+b2
Severity: important

Dear Maintainer,

On a ThinkPad T430, when performing a mobile suspend with all but LVDS1
disconnected and resuming in a dual-head dock, executing

['xrandr', '--output', 'LVDS1', '--off', '--output', 'HDMI2', '--gamma',
'1.0:1.0:1.0', '--mode', '1920x1200', '--pos', '0x0', '--rate', '59.95',
'--reflect', 'normal', '--rotate', 'left', '--transform',
'1,0,0,0,1,0,0,0,1']

results in

"xrandr: Configure crtc 0 failed"

printed to stderr and exit code 1. On VT 8, the message

*** Error in `/usr/bin/X': double free or corruption (!prev): 
0x7f65b0f02340 ***

is printed. When using
xserver-xorg-video-intel_2.99.917-1~exp1_amd64.deb, the problem does not
occur.

After first occurrence, X seems to still be stable (ha!). At second
occurrence (with a duplicated VT 8 message), X does not come back on any
displays but machine appears stable, console is usable, and ACPI
shutdown fine. (I think this is true but I haven't ruthlessly checked the 
failure
mode.) I have an (maybe unrelated) issue with the external displays
appearing disconnected but still with resolutions and an odd trailing
resolution record when using xrandr -q after dock -> mobile. I've not
yet checked whether this influences the failure mode.

Please let me know if you need more info, would like me to do debugging,
or need package version bisection (if you can point me to some info
about how to build and test this stuff... I'm semi-competent but not familiar
with this subsystem).

Thank you,

David Sheets

-- Package-specific info:
X server symlink status:

lrwxrwxrwx 1 root root 13 Oct 10  2012 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 2401376 Feb 11 00:35 /usr/bin/Xorg

Diversions concerning libGL are in place

diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.2.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.2.0 by glx-diversions
diversion of /usr/lib/libGL.so.1 to /usr/lib/mesa-diverted/libGL.so.1 by 
glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2.0.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so.2.0.0 by glx-diversions
diversion of /usr/lib/libGLESv2.so.2 to /usr/lib/mesa-diverted/libGLESv2.so.2 
by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so by glx-diversions
diversion of /usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1.1.0 to 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv1_CM.so.1.1.0 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv2.so.2 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so.2 by glx-diversions
diversion of /usr/lib/x86_64-linux-gnu/libGLESv2.so.2 to 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so.2 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.2 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.2 by glx-diversions
diversion of /usr/lib/libGLESv1_CM.so.1.1.0 to 
/usr/lib/mesa-diverted/libGLESv1_CM.so.1.1.0 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so.1 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so.1 by glx-diversions
diversion of /usr/lib/x86_64-linux-gnu/libGLESv1_CM.so to 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv1_CM.so by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so.1.1.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so.1.1.0 by 
glx-diversions
diversion of /usr/lib/libGL.so.1.2.0 to /usr/lib/mesa-diverted/libGL.so.1.2.0 
by glx-diversions
diversion of /usr/lib/libGLESv2.so to /usr/lib/mesa-diverted/libGLESv2.so by 
glx-diversions
diversion of /usr/lib/libGL.so.1.2 to /usr/lib/mesa-diverted/libGL.so.1.2 by 
glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so.1.1.0 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so.1.1.0 by glx-diversions
diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1.2.0 to 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1.2.0 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so by glx-diversions
diversion of /usr/lib/libGL.so to /usr/lib/mesa-diverted/libGL.so by 
glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so.2 by glx-diversions
diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1.2 to 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1.2 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv2.so to 
/usr/lib/mesa-diverte

Bug#764528: Asus EeePC 1015PEM hangs at boot (Intel graphics)

[David Carvalho]

This bug also affects me

Bug#753192: mesa-demos: FTBFS: drawtex.c:34: undefined reference to `glDrawTexfOES'

[David Suárez]

Source: mesa-demos
Version: 8.1.0-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140628 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> gcc -DPACKAGE_NAME=\"mesa-demos\" -DPACKAGE_TARNAME=\"mesa-demos\" 
> -DPACKAGE_VERSION=\"8.1.0\" -DPACKAGE_STRING=\"mesa-demos\ 8.1.0\" 
> -DPACKAGE_BUGREPORT=\"https://bugs.freedesktop.org/enter_bug.cgi\?product=Mesa\&component=Demos\";
>  -DPACKAGE_URL=\"\" -DPACKAGE=\"mesa-demos\" -DVERSION=\"8.1.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.   
> -D_FORTIFY_SOURCE=2  -I/usr/include/libdrm   -I../../../src/egl/eglut -g -O2 
> -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security 
> -c -o drawtex.o drawtex.c
> /bin/bash ../../../libtool  --tag=CC   --mode=link gcc  -I/usr/include/libdrm 
>   -I../../../src/egl/eglut -g -O2 -fstack-protector --param=ssp-buffer-size=4 
> -Wformat -Werror=format-security -lGLESv1_CM  -lEGL  -lm -Wl,-z,relro -o 
> drawtex_screen drawtex.o ../eglut/libeglut_screen.la 
> libtool: link: gcc -I/usr/include/libdrm -I../../../src/egl/eglut -g -O2 
> -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security 
> -Wl,-z -Wl,relro -o drawtex_screen drawtex.o  -lGLESv1_CM -lm 
> ../eglut/.libs/libeglut_screen.a -lEGL
> drawtex.o: In function `draw':
> /«PKGBUILDDIR»/src/egl/opengles1/drawtex.c:34: undefined reference to 
> `glDrawTexfOES'
> collect2: error: ld returned 1 exit status

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/06/28/mesa-demos_8.1.0-2_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.


-- 
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/20140629164052.GA11268@Sephirot.MIDGAR

Bug#739537: /usr/share/X11/xorg.conf.d/10-quirks.conf: Quirk for "Evoluent VerticalMouse 3" might not be needed...

[David Sharp]

Hello,

This quirk was reverted upstream:

http://cgit.freedesktop.org/xorg/xserver/commit/?id=d5587cf3acb7ad6f81e1c095f1b88f8fb25ee953

Thanks!


-- 
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/cajztdeurvw3z58k6cyw+4+mjda2gi9m2kvhiafrdzpubsft...@mail.gmail.com

Bug#750265: xserver-xorg-video-vmware: FTBFS: debian/rules:22: *** mixed implicit and normal rules: deprecated syntax

[David Suárez]

Source: xserver-xorg-video-vmware
Version: 1:13.0.2-2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140601 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>  fakeroot debian/rules clean
> debian/rules:22: *** mixed implicit and normal rules: deprecated syntax
> make: *** No rule to make target 'clean'.  Stop.
> dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2
> 
> Build finished at 20140601-2306

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/06/01/xserver-xorg-video-vmware_13.0.2-2_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.


-- 
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/20140602191802.GA13118@Sephirot.MIDGAR

Bug#748734: More details on bug

[Erwan David]

I also checked : this breaks the unicity of configuration
between text console and X11, since with this version I get a
dot on text console and a comma in X11. We could say this breaks the 
keyboard-configuration package


-- 
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/20140521054659.gj5...@rail.eu.org

Bug#748734: Latest upgrades breaks french keyboard

[Erwan David]

Package: xkb-data
Version: 2.11-1
Severity: normal

Since latest upgrade, numeric keypad dot key does not produce a dot
anymore but a comma. Thus it does not produce what is written on the
key

Here is /etc/default/keyboard

# If you change any of the following variables and X is configured to
# use this file, then the changes will become visible to X only if udev
# is restarted.  You may need to reboot the system.

# The following variables describe your keyboard and can have the same
# values as the XkbModel, XkbLayout, XkbVariant and XkbOptions options
# in /etc/X11/xorg.conf.

XKBMODEL="pc105"
XKBLAYOUT="fr"
XKBVARIANT=""
XKBOPTIONS="lv3:ralt_switch,compose:menu,terminate:ctrl_alt_bksp,altwin:meta_win"

# If you don't want to use the XKB layout on the console, you can
# specify an alternative keymap.  Make sure it will be accessible
# before /usr is mounted.
# KMAP=/etc/console-setup/defkeymap.kmap.gz
BACKSPACE="guess"



-- System Information:
Debian Release: jessie/sid
  APT prefers testing-proposed-updates
  APT policy: (900, 'testing-proposed-updates'), (900, 'testing'), (600, 
'stable'), (500, 'proposed-updates'), (400, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

-- 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/20140520082200.5401.38088.report...@nux28622.fr.nds.com

Bug#746052: libxfont: FTBFS: ../../../src/util/patcache.c:130:1: error: conflicting types for 'CacheFontPattern'

[David Suárez]

Source: libxfont
Version: 1:1.4.7-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140426 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> /bin/bash ../../libtool  --tag=CC   --mode=compile gcc -std=gnu99 
> -DHAVE_CONFIG_H -I. -I../../../src/util -I../.. -I../../include/X11/fonts  
> -I../../../include -I../../../src/stubs -D_FORTIFY_SOURCE=2 -D_DEFAULT_SOURCE 
> -D_BSD_SOURCE -DHAS_FCHOWN -DHAS_STICKY_DIR_BIT  -D_XOPEN_SOURCE -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 
> -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 
> -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat 
> -Werror=format-security -Wall -c -o patcache.lo ../../../src/util/patcache.c
> libtool: compile:  gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../../../src/util 
> -I../.. -I../../include/X11/fonts -I../../../include -I../../../src/stubs 
> -D_FORTIFY_SOURCE=2 -D_DEFAULT_SOURCE -D_BSD_SOURCE -DHAS_FCHOWN 
> -DHAS_STICKY_DIR_BIT -D_XOPEN_SOURCE -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 
> -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 
> -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat 
> -Werror=format-security -Wall -c ../../../src/util/patcache.c  -fPIC -DPIC -o 
> .libs/patcache.o
> ../../../src/util/patcache.c:130:1: error: conflicting types for 
> 'CacheFontPattern'
>  CacheFontPattern (FontPatternCachePtr cache,
>  ^
> In file included from /usr/include/X11/fonts/fontstruct.h:28:0,
>  from ../../../src/util/patcache.c:35:
> /usr/include/X11/fonts/font.h:141:18: note: previous declaration of 
> 'CacheFontPattern' was here
>  extern void  CacheFontPattern (
>   ^
> ../../../src/util/patcache.c:176:1: error: conflicting types for 
> 'FindCachedFontPattern'
>  FindCachedFontPattern (FontPatternCachePtr cache,
>  ^
> In file included from /usr/include/X11/fonts/fontstruct.h:28:0,
>  from ../../../src/util/patcache.c:35:
> /usr/include/X11/fonts/font.h:151:21: note: previous declaration of 
> 'FindCachedFontPattern' was here
>  extern FontPtr  FindCachedFontPattern (
>  ^
> make[5]: *** [patcache.lo] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/04/26/libxfont_1.4.7-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.


--
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/20140427120836.GA12988@Aeris.MIDGAR

Bug#733385: xft: FTBFS: ../../src/xftglyphs.c:24:30: fatal error: freetype/ftoutln.h: No such file or directory

[David Suárez]

Source: xft
Version: 2.3.1-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20131226 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

On the new 2.5 version the headers are located at
'/usr/include/freetype2/ftglyph.h' instead of
'/usr/include/freetype2/freetype/ftglyph.h' like in previous versions.

Relevant part (hopefully):
> make[3]: Entering directory `/«PKGBUILDDIR»/build/src'
>   CC   xftcolor.lo
>   CC   xftcore.lo
>   CC   xftdbg.lo
>   CC   xftdpy.lo
>   CC   xftdraw.lo
> ../../src/xftdraw.c: In function 'XftDrawSrcPicture':
> ../../src/xftdraw.c:327:15: warning: cast discards '__attribute__((const))' 
> qualifier from pointer target type [-Wcast-qual]
>   !memcmp ((void *) &color->color,
>^
>   CC   xftextent.lo
>   CC   xftfont.lo
> ../../src/xftfont.c: In function 'XftFontOpenName':
> ../../src/xftfont.c:123:24: warning: cast discards '__attribute__((const))' 
> qualifier from pointer target type [-Wcast-qual]
>  pat = FcNameParse ((FcChar8 *) name);
> ^
>   CC   xftfreetype.lo
> In file included from /usr/include/string.h:633:0,
>  from ../../src/xftint.h:46,
>  from ../../src/xftfreetype.c:23:
> ../../src/xftfreetype.c: In function '_XftGetFile':
> ../../src/xftfreetype.c:48:24: warning: cast discards 
> '__attribute__((const))' qualifier from pointer target type [-Wcast-qual]
>   if (!strcmp (f->file, (char *) file) && f->id == id)
> ^
> ../../src/xftfreetype.c:48:24: warning: cast discards 
> '__attribute__((const))' qualifier from pointer target type [-Wcast-qual]
>   if (!strcmp (f->file, (char *) file) && f->id == id)
> ^
> ../../src/xftfreetype.c:48:24: warning: cast discards 
> '__attribute__((const))' qualifier from pointer target type [-Wcast-qual]
>   if (!strcmp (f->file, (char *) file) && f->id == id)
> ^
> ../../src/xftfreetype.c:48:24: warning: cast discards 
> '__attribute__((const))' qualifier from pointer target type [-Wcast-qual]
>   if (!strcmp (f->file, (char *) file) && f->id == id)
> ^
> ../../src/xftfreetype.c:48:24: warning: cast discards 
> '__attribute__((const))' qualifier from pointer target type [-Wcast-qual]
>   if (!strcmp (f->file, (char *) file) && f->id == id)
> ^
> ../../src/xftfreetype.c:48:24: warning: cast discards 
> '__attribute__((const))' qualifier from pointer target type [-Wcast-qual]
>   if (!strcmp (f->file, (char *) file) && f->id == id)
> ^
> ../../src/xftfreetype.c:48:24: warning: cast discards 
> '__attribute__((const))' qualifier from pointer target type [-Wcast-qual]
>   if (!strcmp (f->file, (char *) file) && f->id == id)
> ^
> ../../src/xftfreetype.c:48:24: warning: cast discards 
> '__attribute__((const))' qualifier from pointer target type [-Wcast-qual]
>   if (!strcmp (f->file, (char *) file) && f->id == id)
> ^
> ../../src/xftfreetype.c:48:24: warning: cast discards 
> '__attribute__((const))' qualifier from pointer target type [-Wcast-qual]
>   if (!strcmp (f->file, (char *) file) && f->id == id)
> ^
> ../../src/xftfreetype.c:48:24: warning: cast discards 
> '__attribute__((const))' qualifier from pointer target type [-Wcast-qual]
>   if (!strcmp (f->file, (char *) file) && f->id == id)
> ^
> ../../src/xftfreetype.c:48:24: warning: cast discards 
> '__attribute__((const))' qualifier from pointer target type [-Wcast-qual]
>   if (!strcmp (f->file, (char *) file) && f->id == id)
> ^
> ../../src/xftfreetype.c:48:24: warning: cast discards 
> '__attribute__((const))' qualifier from pointer target type [-Wcast-qual]
>   if (!strcmp (f->file, (char *) file) && f->id == id)
> ^
> ../../src/xftfreetype.c:48:24: warning: cast discards 
> '__attribute__((const))' qualifier from pointer target type [-Wcast-qual]
>   if (!strcmp (f->file, (char *) file) && f->id == id)
> ^
> ../../src/xftfreetype.c:48:24: warning: cast discards 
> '__attribute__((const))' qualifier from pointer target type [-Wcast-qual]
>   if (!strcmp (f->file, (char *) file) && f->id == id)
> ^
> ../../src/xftfreetype.c:48:24: warning: cast discards 
> '__attribute__((const))' qualifier from pointer target type [-Wcast-qual]
>   if (!strcmp (f->file, (char *) file) && f->id == id)
> ^
> ../../src/xftfreetype.c:48:24: warning: cast discards 
> '__attribute__((const))' qualifier from pointer target type [-Wcast-qual]
>   if (!strcmp (f->file, (char *) file) && f->id == id)
> ^
> ../../src/xftfreetype.c:48:24: warning: cast discards 
> '__attribute__((const))' qualifier from poi

Bug#724546: Acknowledgement (xserver-xorg-video-chips: FTBFS on hppa: ct_driver.h:30:17: fatal error: xaa.h: No such file or directory)

[John David Anglin]

Same error building xserver-xorg-video-r128.

Dave
--
John David Anglin   dave.ang...@bell.net


--
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/blu0-smtp112e595f563d1c0ca7602597...@phx.gbl

Bug#724546: xserver-xorg-video-chips: FTBFS on hppa: ct_driver.h:30:17: fatal error: xaa.h: No such file or directory

[John David Anglin]

Package: xserver-xorg-video-chips
Version: 1.2.4-2
Severity: normal

make[3]: Entering directory 
`/home/dave/debian/xserver-xorg-video-chips/xserver-xorg-video-chips-1.2.4/build/src'
  CC   ct_accel.lo
In file included from ../../src/ct_accel.c:50:0:
/usr/include/xorg/xf86PciInfo.h:50:2: warning: #warning "xf86PciInfo.h is 
deprecated.  For greater compatibility, drivers should include necessary PCI 
IDs locally rather than relying on this file from xorg-server." [-Wcpp]
In file included from ../../src/ct_accel.c:56:0:
../../src/ct_driver.h:30:17: fatal error: xaa.h: No such file or directory
compilation terminated.
make[3]: *** [ct_accel.lo] Error 1
make[3]: Leaving directory 
`/home/dave/debian/xserver-xorg-video-chips/xserver-xorg-video-chips-1.2.4/build/src'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory 
`/home/dave/debian/xserver-xorg-video-chips/xserver-xorg-video-chips-1.2.4/build'
make[1]: *** [all] Error 2
make[1]: Leaving directory 
`/home/dave/debian/xserver-xorg-video-chips/xserver-xorg-video-chips-1.2.4/build'
dh_auto_build: make -j1 returned exit code 2
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2

File is no longer in xserver-xorg-dev.

-- System Information:
Debian Release: 7.0
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: hppa (parisc64)

Kernel: Linux 3.12.0-rc1+ (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
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/blu0-smtp90f3a1a80b7a8c1672ad7c97...@phx.gbl

Bug#724187: xorg-server: FTBFS: Tests failed

[David Suárez]

Source: xorg-server
Version: 2:1.12.4-6.2
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130922 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[7]: Entering directory `/«PKGBUILDDIR»/build-udeb/test/xi2'
> make[7]: Nothing to be done for `all'.
> make[7]: Leaving directory `/«PKGBUILDDIR»/build-udeb/test/xi2'
> make[6]: Leaving directory `/«PKGBUILDDIR»/build-udeb/test'
> 
> Testsuite summary for xorg-server 1.12.4
> 
> # TOTAL: 9
> # PASS:  8
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> See test/test-suite.log
> Please report to https://bugs.freedesktop.org/enter_bug.cgi?product=xorg
> 
> make[5]: *** [test-suite.log] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/09/22/xorg-server_1.12.4-6.2_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.


-- 
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/20130922192445.GA29850@Aeris.MIDGAR

Bug#712514: Some more debug

[Dr. David Alan Gilbert]

I've rebuilt xorg-server withnostrip nocheck noopt
and added a load of debug, with that the backtrace shows

Program received signal SIGSEGV, Segmentation fault.
0x0020 in ?? ()
(gdb) where
#0  0x0020 in ?? ()
#1  0x2a09b5f0 in xf86SIGIO (sig=707031856)
at ../../../../../hw/xfree86/os-support/linux/../shared/sigio.c:121
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
(gdb) q

which seems to make sense, because it's happening as I touch and
the sigio seems to be bubbling touch events through evdev.

I've added a load of debug and it does seem to be getting to the end
of the sigio routine, just not returning properly (that line 121 is
the resteration of the errno); I've also added loads of debug to
Evdev, again it seems to be going through the motions ok.

here is my (rather cryptic) debug I've added for the last of the
events that happened before it died.

xf86SIGIO for 29
xf86SIGIO found i=0 r=1 func=0x2a078999
xf86SigioReadInput: closure=0x2a26a5f0 read_info=0x40526629
EvdevReadInput: pInfo=0x2a26a5f0
EvdevReadInput: pInfo=0x2a26a5f0 looptop
EvdevReadInput: post read len=32 (bufsize=256)
EvdevReadInput: process 0
EvdevReadInput: process 1
xf86SIGIO exit for 29

Program received signal SIGSEGV, Segmentation fault.
0x0020 in ?? ()
(gdb) where
#0  0x0020 in ?? ()
#1  0x2a09b5f0 in xf86SIGIO (sig=707031856)
at ../../../../../hw/xfree86/os-support/linux/../shared/sigio.c:121
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
(gdb) q

Given that's in a signal handler perhaps the rest of the stack is fine;
it's just the return data that's had it.

-- 
 -Open up your eyes, open up your mind, open up your code ---   
/ Dr. David Alan Gilbert|   Running GNU/Linux   | Happy  \ 
\ gro.gilbert @ treblig.org |   | In Hex /
 \ _|_ http://www.treblig.org   |___/


-- 
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/20130719010937.GA25902@gallifrey

Bug#713608: libxp: FTBFS: ../../src/XpExtUtil.h:55:20: error: static declaration of '_XEatDataWords' follows non-static declaration

[David Suárez]

Source: libxp
Version: 1:1.0.1-2+deb7u1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130620 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
>  gcc -DHAVE_CONFIG_H -I. -I../../src -I.. -I../../include/X11/extensions 
> -DMALLOC_0_RETURNS_NULL -Wall -g -O2 -MT XpAttr.lo -MD -MP -MF 
> .deps/XpAttr.Tpo -c ../../src/XpAttr.c  -fPIC -DPIC -o .libs/XpAttr.o
> In file included from ../../src/XpAttr.c:44:0:
> ../../src/XpExtUtil.h:55:20: error: static declaration of '_XEatDataWords' 
> follows non-static declaration
>  static inline void _XEatDataWords(Display *dpy, unsigned long n)
> ^
> In file included from ../../src/XpAttr.c:43:0:
> /usr/include/X11/Xlibint.h:867:13: note: previous declaration of 
> '_XEatDataWords' was here
>  extern void _XEatDataWords(
>  ^
> make[3]: *** [XpAttr.lo] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2013/06/20/libxp_1.0.1-2+deb7u1_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.


-- 
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/20130622133837.GA13504@Aeris.MIDGAR

Bug#712514: fb xserver crash in valuator_mask_zero

[Dr. David Alan Gilbert]

pio-keys: Device: "/dev/input/event0"
[  4553.977] (--) evdev: gpio-keys: Vendor 0x1 Product 0x1
[  4553.977] (--) evdev: gpio-keys: Found keys
[  4553.977] (II) evdev: gpio-keys: Configuring as keyboard
[  4553.977] (II) XINPUT: Adding extended input device "gpio-keys" (type: 
KEYBOARD, id 7)
[  4553.977] (**) Option "xkb_rules" "evdev"
[  4553.977] (**) Option "xkb_model" "evdev"
[  4553.977] (**) Option "xkb_layout" "us"
[  4554.106] (II) Using input driver 'evdev' for 'twl4030-keypad'
[  4554.107] (**) Option "CoreKeyboard"
[  4554.107] (**) twl4030-keypad: always reports core events
[  4554.107] (**) evdev: twl4030-keypad: Device: "/dev/input/event1"
[  4554.107] (--) evdev: twl4030-keypad: Vendor 0x1 Product 0x1
[  4554.107] (--) evdev: twl4030-keypad: Found keys
[  4554.107] (II) evdev: twl4030-keypad: Configuring as keyboard
[  4554.107] (II) XINPUT: Adding extended input device "twl4030-keypad" (type: 
KEYBOARD, id 8)
[  4554.107] (**) Option "xkb_rules" "evdev"
[  4554.107] (**) Option "xkb_model" "evdev"
[  4554.108] (**) Option "xkb_layout" "us"
[  4554.109] (II) Using input driver 'evdev' for 'usbkbd'
[  4554.109] (**) Option "CoreKeyboard"
[  4554.109] (**) usbkbd: always reports core events
[  4554.109] (**) evdev: usbkbd: Device: "/dev/input/event4"
[  4554.110] (EE) evdev: usbkbd: Unable to open evdev device 
"/dev/input/event4".
[  4554.110] (EE) PreInit returned 2 for "usbkbd"
[  4554.110] (II) UnloadModule: "evdev"
[  4554.110] (II) Using input driver 'evdev' for 'usbkbd2'
[  4554.110] (**) Option "CoreKeyboard"
[  4554.110] (**) usbkbd2: always reports core events
[  4554.110] (**) evdev: usbkbd2: Device: "/dev/input/event5"
[  4554.110] (EE) evdev: usbkbd2: Unable to open evdev device 
"/dev/input/event5".
[  4554.110] (EE) PreInit returned 2 for "usbkbd2"
[  4554.110] (II) UnloadModule: "evdev"
[  4554.110] (II) Using input driver 'evdev' for 'usbmouse'
[  4554.110] (**) Option "CorePointer"
[  4554.110] (**) usbmouse: always reports core events
[  4554.111] (**) evdev: usbmouse: Device: "/dev/input/event3"
[  4554.111] (EE) evdev: usbmouse: Unable to open evdev device 
"/dev/input/event3".
[  4554.111] (EE) PreInit returned 2 for "usbmouse"
[  4554.111] (II) UnloadModule: "evdev"

udev information:
-

DRM Information from dmesg:
---
[ 7571.660949] init: no such service 'drm'

(deb-armhf)root@localhost:/root# g_dbus_connection_real_closed: Remote peer 
vanished with error: Underlying GIOStream returned 0 bytes on an async read 
(g-io-error-quark, 0). Exiting.
xinit: connection to X server lost

waiting for X server to shut down XIO:  fatal IO error 11 (Resource temporarily 
unavailable) on X server ":0"
  after 1983 requests (1983 known processed) with 0 events remaining.
XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
  after 187 requests (170 known processed) with 0 events remaining.

-- 
-Open up your eyes, open up your mind, open up your code ---   
/ Dr. David Alan Gilbert|   Running GNU/Linux   | Happy  \ 
\ gro.gilbert @ treblig.org |   | In Hex /
 \ _|_ http://www.treblig.org   |___/


-- 
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/20130616165034.GA19548@gallifrey

Bug#712320: xserver-xorg-video-nouveau: FTBFS: configure: error: Package requirements (libdrm_nouveau = 0.6) were not met:

[David Suárez]

Source: xserver-xorg-video-nouveau
Version: 1:1.0.1-5
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130609 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[1]: Entering directory `/«PKGBUILDDIR»'
> dh_auto_configure -- CURDIR="/«PKGBUILDDIR»"
> configure: WARNING: unrecognized options: --disable-maintainer-mode
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for a thread-safe mkdir -p... /bin/mkdir -p
> checking for gawk... no
> checking for mawk... mawk
> checking whether make sets $(MAKE)... yes
> checking whether make supports nested variables... yes
> checking whether make supports nested variables... (cached) yes
> checking build system type... x86_64-pc-linux-gnu
> checking host system type... x86_64-pc-linux-gnu
> checking how to print strings... printf
> checking for style of include used by make... GNU
> checking for gcc... gcc
> checking whether the C compiler works... yes
> checking for C compiler default output file name... a.out
> checking for suffix of executables... 
> checking whether we are cross compiling... no
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ISO C89... none needed
> checking dependency style of gcc... none
> checking for a sed that does not truncate output... /bin/sed
> checking for grep that handles long lines and -e... /bin/grep
> checking for egrep... /bin/grep -E
> checking for fgrep... /bin/grep -F
> checking for ld used by gcc... /usr/bin/ld
> checking if the linker (/usr/bin/ld) is GNU ld... yes
> checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
> checking the name lister (/usr/bin/nm -B) interface... BSD nm
> checking whether ln -s works... yes
> checking the maximum length of command line arguments... 3458764513820540925
> checking whether the shell understands some XSI constructs... yes
> checking whether the shell understands "+="... yes
> checking how to convert x86_64-pc-linux-gnu file names to x86_64-pc-linux-gnu 
> format... func_convert_file_noop
> checking how to convert x86_64-pc-linux-gnu file names to toolchain format... 
> func_convert_file_noop
> checking for /usr/bin/ld option to reload object files... -r
> checking for objdump... objdump
> checking how to recognize dependent libraries... pass_all
> checking for dlltool... no
> checking how to associate runtime and link libraries... printf %s\n
> checking for ar... ar
> checking for archiver @FILE support... @
> checking for strip... strip
> checking for ranlib... ranlib
> checking command to parse /usr/bin/nm -B output from gcc object... ok
> checking for sysroot... no
> checking for mt... no
> checking if : is a manifest tool... no
> checking how to run the C preprocessor... gcc -E
> checking for ANSI C header files... yes
> checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for memory.h... yes
> checking for strings.h... yes
> checking for inttypes.h... yes
> checking for stdint.h... yes
> checking for unistd.h... yes
> checking for dlfcn.h... yes
> checking for objdir... .libs
> checking if gcc supports -fno-rtti -fno-exceptions... no
> checking for gcc option to produce PIC... -fPIC -DPIC
> checking if gcc PIC flag -fPIC -DPIC works... yes
> checking if gcc static flag -static works... yes
> checking if gcc supports -c -o file.o... yes
> checking if gcc supports -c -o file.o... (cached) yes
> checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared 
> libraries... yes
> checking whether -lc should be explicitly linked in... no
> checking dynamic linker characteristics... GNU/Linux ld.so
> checking how to hardcode library paths into programs... immediate
> checking whether stripping libraries is possible... yes
> checking if libtool supports shared libraries... yes
> checking whether to build shared libraries... yes
> checking whether to build static libraries... no
> checking for gcc... (cached) gcc
> checking whether we are using the GNU C compiler... (cached) yes
> checking whether gcc accepts -g... (cached) yes
> checking for gcc option to accept ISO C89... (cached) none needed
> checking dependency style of gcc... (cached) none
> checking for special C compiler options needed for large files... no
> checking for _FILE_OFFSET_BITS value needed for large files... no
> checking for pkg-config... /usr/bin/pkg-config
> checking pkg-config is at least version 0.9.0... yes
> checking if RANDR is defined... yes
> checking if RENDER is defined... yes
> checking if XV is defined... yes
> checking if DPMSExtension is defined... yes
> checking for LIBDRM_NOUVEAU_DUMMY... no
> configure: error: Package requirements (libdrm_nouveau = 0.

Bug#680371: xserver-xorg-video-intel does not wedge GPU on EQ hang

[David Tomaschik]

Maybe this is the wrong bug for this, but I'm running into the same
problem, but no i915 options on the cmdline, and this is causing my X
session to lock up multiple times a day.

I have xserver-xorg-video-intel 2:2.19.0-6 installed.

What information can I provide that adds additional information to this
issue?

-- 
David Tomaschik
OpenPGP: 0x5DEA789B
http://systemoverlord.com
da...@systemoverlord.com

Bug#702938: Xwindow crashes due to vgahw

[David Lawyer]

Package: xserver-xorg-core
Version: 1.12.4-5_i386

When I type startx, the xserver crashes.  I found on the internet that
others report a crash due to the vgahw module (actually libvgahw.so).  Note
that this module is part of the core package.  Heres the log:
[ 13059.599] 
X.Org X Server 1.12.4
Release Date: 2012-08-27
[ 13059.604] X Protocol Version 11, Revision 0
[ 13059.606] Build Operating System: Linux 2.6.32-5-amd64 i686 Debian
[ 13059.607] Current Operating System: Linux davespc 3.2.0-3-486 #1 Thu Jun 28 
08:08:24 UTC 2012 i586
[ 13059.609] Kernel command line: auto BOOT_IMAGE=kernel-3.2... ro 
root=LABEL=6GB-Maxtor nousb
[ 13059.612] Build Date: 23 February 2013  06:25:22PM
[ 13059.613] xorg-server 2:1.12.4-5 (Julien Cristau ) 
[ 13059.614] Current version of pixman: 0.26.0
[ 13059.616]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 13059.618] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 13059.629] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Mar 10 14:50:14 
2013
[ 13059.634] (==) Using config file: "/etc/X11/xorg.conf"
[ 13059.636] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 13059.641] (==) No Layout section.  Using the first Screen section.
[ 13059.642] (**) |-->Screen "Screen" (0)
[ 13059.642] (**) |   |-->Monitor "Dell Monitor"
[ 13059.662] (==) No device specified for screen "Screen".
Using the first device section listed.
[ 13059.663] (**) |   |-->Device "Video Card S3"
[ 13059.663] (==) Automatically adding devices
[ 13059.664] (==) Automatically enabling devices
[ 13059.666] (WW) The directory 
"/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType" does not exist.
[ 13059.667]Entry deleted from font path.
[ 13059.667] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/cyrillic,
/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
[ 13059.668] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 13059.668] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[ 13059.682] (II) Loader magic: 0xb77bf5a0
[ 13059.682] (II) Module ABI versions:
[ 13059.682]X.Org ANSI C Emulation: 0.4
[ 13059.683]X.Org Video Driver: 12.1
[ 13059.683]X.Org XInput driver : 16.0
[ 13059.684]X.Org Server Extension : 6.0
[ 13059.690] (--) PCI:*(0:0:19:0) 5333:8811:: rev 0, Mem @ 
0xe000/8388608, BIOS @ 0x/65536
[ 13059.692] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or 
directory)
[ 13059.693] (II) LoadModule: "extmod"
[ 13059.701] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
[ 13059.707] (II) Module extmod: vendor="X.Org Foundation"
[ 13059.708]compiled for 1.12.4, module version = 1.0.0
[ 13059.708]Module class: X.Org Server Extension
[ 13059.709]ABI class: X.Org Server Extension, version 6.0
[ 13059.709] (II) Loading extension SELinux
[ 13059.709] (II) Loading extension MIT-SCREEN-SAVER
[ 13059.710] (II) Loading extension XFree86-VidModeExtension
[ 13059.710] (II) Loading extension XFree86-DGA
[ 13059.711] (II) Loading extension DPMS
[ 13059.711] (II) Loading extension XVideo
[ 13059.711] (II) Loading extension XVideo-MotionCompensation
[ 13059.712] (II) Loading extension X-Resource
[ 13059.712] (II) LoadModule: "dbe"
[ 13059.717] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
[ 13059.719] (II) Module dbe: vendor="X.Org Foundation"
[ 13059.719]compiled for 1.12.4, module version = 1.0.0
[ 13059.720]Module class: X.Org Server Extension
[ 13059.720]ABI class: X.Org Server Extension, version 6.0
[ 13059.721] (II) Loading extension DOUBLE-BUFFER
[ 13059.721] (II) LoadModule: "glx"
[ 13059.725] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 13059.728] (II) Module glx: vendor="X.Org Foundation"
[ 13059.729]compiled for 1.12.4, module version = 1.0.0
[ 13059.729]ABI class: X.Org Server Extension, version 6.0
[ 13059.730] (==) AIGLX enabled
[ 13059.731] (II) Loading extension GLX
[ 13059.731] (II) LoadModule: "record"
[ 13059.735] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
[ 13059.738] (II) Module record: vendor="X.Org Foundation"
[ 13059.738]compiled for 1.12.4, module version = 1.13.0
[ 13059.739]Module class: X.Org Server Extension
[ 13059.739]ABI class: X.Org Server Extension, version 6.0
[ 13059.740] (II) Loading extension RECORD
[ 13059.740] (II) LoadModule: "dri"
[ 13059.744] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
[ 13059.762] (II) Module dri: vendor="X.Org Foundation"
[ 13059.763]compiled for 1.12.4, modul

Bug#683723: please include in Wheezy

[David Fries]

Package: xserver-xorg-input-evdev
Version: 1:2.7.0-1+b1
Followup-For: Bug #683723

Dear Maintainer,

> Source: xserver-xorg-input-evdev
> Source-Version: 1:2.7.1-1
> 
> We believe that the bug you reported is fixed in the latest version of
> xserver-xorg-input-evdev, which is due to be installed in the Debian
> FTP archive.

That was August 2012, and now six months later it hasn't been promoted
to wheezy or sid.  I'm concerned if it isn't promoted it will miss
Wheezy entirely and people needing multitouch will need to go to a
different distribution entirely.

-- System Information:
Debian Release: 7.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.8.0+ (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/dash

Versions of packages xserver-xorg-input-evdev depends on:
ii  libc6  2.13-38
ii  xserver-xorg-core [xorg-input-abi-16]  2:1.12.4-5

xserver-xorg-input-evdev recommends no packages.

xserver-xorg-input-evdev 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: 
http://lists.debian.org/20130309180904.16691.15203.report...@spacedout.fries.net

Bug#702662: xserver-xorg-core: multitouch stuck button, apply upstream patch

[David Fries]

Package: xserver-xorg-core
Version: 2:1.12.4-5
Severity: important

Dear Maintainer,

Please apply the following two multitouch bug fixes to
xserver-xorg-core for Wheezy.  Currently an event from a multitouch
device will be translated into a pointer event including simulating
pressing the first mouse button, the problem is the button down state
is never released, meaning from then on all mouse events will have a
state of button one held, causing programs to misbehave in important
ways.  This persists until X is restarted, even unplugging the
touchscreen device doesn't clear it.

3e6358ee6c33979329b78fe2097a1fdf76fb69cd
'Xi: Don't check for TOUCH_END, it's never set'

863f32c930d71073ee5f78452b78bd459d024867
'Xi: Update the device after delivering the emulated pointer event(#56558)'

Interestingly enough when the synaptics driver gets an input from a
touch pad it will reset the held button state, otherwise the only
option is to restart X and not touch the touch pad.

-- System Information:
Debian Release: 7.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.8.0+ (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/dash

Versions of packages xserver-xorg-core depends on:
ii  keyboard-configuration  1.88
ii  libaudit0   1:1.7.18-1.1
ii  libc6   2.13-38
ii  libdrm2 2.4.40-1~deb7u2
ii  libgcrypt11 1.5.0-3
ii  libpciaccess0   0.13.1-2
ii  libpixman-1-0   0.26.0-4
ii  libselinux1 2.1.9-5
ii  libudev0175-7.1
ii  libxau6 1:1.0.7-1
ii  libxdmcp6   1:1.1.1-1
ii  libxfont1   1:1.4.5-2
ii  udev175-7.1
ii  xserver-common  2:1.12.4-5

Versions of packages xserver-xorg-core recommends:
ii  libgl1-mesa-dri  8.0.5-3

Versions of packages xserver-xorg-core suggests:
ii  xfonts-100dpi1:1.0.3
ii  xfonts-75dpi 1:1.0.3
ii  xfonts-scalable  1:1.0.3-1

-- 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: 
http://lists.debian.org/20130309181107.16484.98040.report...@spacedout.fries.net

Mesa 9 for wheezy-backports?

[David Smith]

Is anybody working on packaging / documenting installation of Mesa 9.X 
on Wheezy?  I want to help out if I can for documenting Mesa 9 in Wheezy.


I noticed this guide: http://x.debian.net/howto/build-mesa.html   Does 
not seem to work anymore because of new versions of Mesa upstream.. You 
now need to compile drm as well. Some of the ./configure flags in that 
guide for mesa don't exist anymore.


I was able to successfully compile drm + mesa 9 (32-bit) in Debian 
Wheezy (64-bit/multiarch) in order to run Steam (32-bit proprietary 
binary) software well on Intel Ivy Bridge hardware.


 * Many users of the radeon open source drivers get significant
   performance gains when running Mesa 9.X.
 * People running Intel graphics on Ivy Bridge or Sandy Bridge graphics
   chips /need/ to run Mesa 9.X or they will get severe graphical
   glitches in Team Fortress 2 and some other very popular Steam games
   to the point where they aren't playable.


In case anybody is interested, I started using this guide here:
http://x.debian.net/howto/build-mesa.html.  I followed those directions 
until I started compiling Mesa and it failed because the drm version was 
too old.


So then I started following this guide here:
http://dri.freedesktop.org/wiki/Building#Building_libdrm


Which worked great for building a 64-bit mesa on my 64-bit Wheezy, but 
that wasn't what I needed..  So I got some help from some forums and 
installed the following build dependencies...


libudev:i386 libxcb-dri2-0-dev:i386 libxcb-glx0-dev:i386 
libxdamage-dev:i386 libxfixes-dev:i386 libx11-xcb-dev:i386 
libxext-dev:i386 libcairo2-dev:i386 libfontconfig1-dev:i386 
pkg-config:i386 libpciaccess-dev:i386 libc6-dev:i386 gcc-multilib 
g++-multilib gcc:i386 c-compiler:i386



Then changed the compile flags..


export CFLAGS="-m32"
export CXXFLAGS="-m32"
./autogen.sh   \
--enable-driglx-direct \
--enable-gles-overlay \
--enable-gles1 \
--enable-gles2 \
--enable-glx-tls \
--with-driver=dri \
--with-dri-driverdir=/usr/lib/dri \
--with-egl-platforms='drm x11' \
--with-state-trackers=egl,glx,dri,vega \
--with-dri-drivers=i965 \
--enable-32-bit \
--disable-64-bit  \
--enable-gallium-llvm=disabled \
--enable-gallium-gbm=disabled \
--enable-gallium-egl=disabled \
--with-gallium-drivers= \
--build=i686-pc-linux-gnu \

After that, I was able to build Mesa 9 (32-bit) for Intel Ivy Bridge 
graphics, no problem.


Not sure if that's useful to anybody, but I hope that it is.   Running 
Ivy Bridge graphics, previously Team Fortress 2 (32-bit proprietary 
binary) would have a big green square from the introduction movie and 
then go to a black screen with graphical glitches for the menu.. Now the 
game runs perfectly fine and smooth at 1920x1080 resolution and medium 
graphics settings with Mesa 9 from git using open source Intel graphics!


Cheers and thanks for your time.

-David Smith

Bug#688067: xserver-xorg: X server maintains incorrect data on black background after Flash crash

[Noel David Torres Taño]

Package: xserver-xorg
Version: 1:7.5+8
Severity: normal

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

   * What led up to the situation?
I killed xulrunner process that was showing a flash animation for Blogger
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
Process exited normally, but its phantom can still be seen on the background of 
my terminal emulator. I have checked and it shows on every black background 
(tested with xscreensaver and GIMP). Photograph will be attached in next 
e-mail. Phantom image does not show on screenshots.
   * What outcome did you expect instead?
I expect black to be black.

*** End of the template - remove these lines ***


-- Package-specific info:
X server symlink status:

lrwxrwxrwx 1 root root 13 Nov 18  2010 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 1889472 Feb 18  2011 /usr/bin/Xorg

Diversions concerning libGL are in place

diversion of /usr/lib/libGL.so to /usr/lib/mesa-diverted/libGL.so by 
glx-diversions
diversion of /usr/lib/libGL.so.1 to /usr/lib/mesa-diverted/libGL.so.1 by 
glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1 by glx-diversions
diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1.2 to 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1.2 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1.2 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.2 by glx-diversions
diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1 to 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1 by glx-diversions
diversion of /usr/lib/libGL.so.1.2 to /usr/lib/mesa-diverted/libGL.so.1.2 by 
glx-diversions
diversion of /usr/lib/x86_64-linux-gnu/libGL.so to 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so by glx-diversions

VGA-compatible devices on PCI bus:
--
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G92 [GeForce 9800 
GT] [10de:0614] (rev a2)

Xorg X server configuration file status:

-rw-r--r-- 1 root root 1085 Nov  2  2010 /etc/X11/xorg.conf

Contents of /etc/X11/xorg.conf:
---
# /etc/X11/xorg.conf (xorg X Window System server configuration file)

Section "Module"
Load"dri"
Load"glx"
EndSection

Section "InputDevice"
Identifier  "Generic Keyboard"
Driver  "kbd"
Option  "CoreKeyboard"
Option  "XkbRules"  "xorg"
Option  "XkbModel"  "pc105"
Option  "XkbLayout" "es"
EndSection

Section "InputDevice"
Identifier  "Configured Mouse"
Driver  "mouse"
Option  "CorePointer"
Option  "Device""/dev/input/mice"
Option  "Protocol"  "ImPS/2"
Option  "Emulate3Buttons"   "true"
EndSection

Section "Device"
Identifier  "nVidia Corporation G92 [GeForce 9800 GT] (rev a2)"
#Driver  "nv"
Driver  "nvidia"
EndSection

Section "Screen"
Identifier  "Default Screen"
Device  "nVidia Corporation G92 [GeForce 9800 GT] (rev a2)"
Monitor "Default Monitor"
DefaultDepth24
Option  "NoPowerConnectorCheck"
EndSection

Section "ServerLayout"
Identifier  "Default Layout"
Screen  "Default Screen"
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
EndSection

Section "DRI"
Mode0666
EndSection

/etc/X11/xorg.conf.d does not exist.

KMS configuration files:

/etc/modprobe.d/i915-kms.conf:
  options i915 modeset=1
/etc/modprobe.d/radeon-kms.conf:
  options radeon modeset=1

Kernel version (/proc/version):
---
Linux version 3.2.0-2-amd64 (Debian 3.2.17-1) (debian-ker...@lists.debian.org) 
(gcc version 4.6.3 (Debian 4.6.3-5) ) #1 SMP Sat May 12 23:08:28 UTC 2012

Xorg X server log files on system:
--
-rw-r--r-- 1 root root  2509 Sep  5 19:00 /var/log/Xorg.192.log
-rw-r--r-- 1 root root  2509 Sep  5 19:00 /var/log/Xorg.191.log
-rw-r--r-- 1 root root  2509 Sep  5 19:00 /var/log/Xorg.190.log
-rw-r--r-- 1 root root  2509 Sep  5 19:00 /var/log/Xorg.189.log
-rw-r--r-- 1 root root  2509 Sep  5 19:00 /var/log/Xorg.188.log
-rw-r--r-- 1 root root  2509 Sep  5 19:00 /var/log/Xorg.187.log
-rw-r--r-- 1 root root  2509 Sep  5 19:00 /var/log/Xorg.186.log
-rw-r--r-- 1 root root  2509 Sep  5 19:00 /var/log/Xorg.147.log
-rw-r--r-- 1 root root  2509 Sep  5 19:00 /var/log/Xorg.145.log
-rw-r--r-- 1 root root  2509 Sep  5 19:00 /var/l

Bug#679232: libxft2: update from 2.2.0-3 -> 2.3.1-1 breaks font in rxvt-unicode

[David Jansen]

Package: libxft2
Version: 2.3.1-1
Severity: normal

Dear X Strike Force,

   * What led up to the situation?
 [UPGRADE] libxft2:amd64 2.2.0-3 -> 2.3.1-1

   i'm using the font "envy code r" for rxvt-unicode,
   after the upgrade of libxft2 rxvt-unicode falls back to the default 
monospace font.
   Downgrading to libxft2 2.2.0-3 fixes the problem and the configured
   font is used again.

   Here is the relevant part of my .Xdefaults:

   ---
   Xft.dpi: 96
   Xft.antialias: true
   Xft.rgba: rgb
   Xft.hinting: true
   Xft.hinstyle: hintslight
   URxvt.font: xft:envy code r:medium:pixelsize=14
   ---

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing-proposed-updates
  APT policy: (500, 'testing-proposed-updates'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.1.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libxft2 depends on:
ii  libc6  2.13-33
ii  libfontconfig1 2.9.0-6
ii  libfreetype6   2.4.9-1
ii  libx11-6   2:1.5.0-1
ii  libxrender11:0.9.7-1
ii  multiarch-support  2.13-33

libxft2 recommends no packages.

libxft2 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: http://lists.debian.org/20120627103648.22806.97141.reportbug@river

Bug#673669: Sorry

[DAVID HAND]

I'm honestly way out of my depth here.

Does the bug need to be re-submitted? Cannot some of you notify the
relevant people, or alter the package that it refers to?

Bug#673669: Any ideas?

[DAVID HAND]

Would love to get to the bottom of this. Do you need any more information?

Bug#675433: xterm: terminal bell randomly stops and requires a reboot to get back

[David Griffith]

Package: xterm
Version: 278-1
Severity: normal

After a normal bootup, the terminal bell with Xterm works as expected.  
After some time it stops.  This happens with RXVT, Gnome Terminal, and 
XFCE Terminal.  The problem does not appear to be related to starting or 
stopping any sort of audio-using program.  While this isn't a 
showstopping bug, I feel it must definitely be cured before declaring 
Wheezy ready for promotion to Stable.


-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-2-486
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages xterm depends on:
ii  libc6   2.13-32
ii  libfontconfig1  2.9.0-5
ii  libice6 2:1.0.8-2
ii  libtinfo5   5.9-7
ii  libutempter01.1.5-4
ii  libx11-62:1.4.99.901-2
ii  libxaw7 2:1.0.10-2
ii  libxft2 2.2.0-3
ii  libxmu6 2:1.1.1-1
ii  libxt6  1:1.1.3-1
ii  xbitmaps1.1.1-1

Versions of packages xterm recommends:
ii  x11-utils  7.7~1

Versions of packages xterm suggests:
pn  xfonts-cyrillic  

-- 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: 
http://lists.debian.org/20120601065305.4913.63028.report...@marvin.661.org

Bug#675432: xterm scrolling is very slow

[David Griffith]

Package: xterm
Version: 278-1
Severity: normal

Compared to Xterm in Squeeze, Xterm in Wheezy is very slow to scroll and 
update.  This leads to distracting flashes and empty blocks when 
scrolling or refreshing the screen.  What changed between Squeeze and 
Wheezy that would have caused this?


-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-2-486
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages xterm depends on:
ii  libc6   2.13-32
ii  libfontconfig1  2.9.0-5
ii  libice6 2:1.0.8-2
ii  libtinfo5   5.9-7
ii  libutempter01.1.5-4
ii  libx11-62:1.4.99.901-2
ii  libxaw7 2:1.0.10-2
ii  libxft2 2.2.0-3
ii  libxmu6 2:1.1.1-1
ii  libxt6  1:1.1.3-1
ii  xbitmaps1.1.1-1

Versions of packages xterm recommends:
ii  x11-utils  7.7~1

Versions of packages xterm suggests:
pn  xfonts-cyrillic  

-- 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: 
http://lists.debian.org/20120601064803.4544.82868.report...@marvin.661.org

Bug#673669: EDID extracted from proprietary nvidia driver from laptop

[DAVID HAND]

(via ubuntu 10.04) is the same as in Xorg.0.log (from debian live cd on
laptop) - yet gives accurate resolution choices.

I'm really confused.

Bug#673669: Additional info

[DAVID HAND]

Forgot to say I have a laptop with VGA out - with an nvidia go 7600 with
which I could test the monitor bypassing the DVI>VGA adapter, though my
hunch is that the adapter is not the problem. Not only does windows work
with the same hardware configuration, but I remember having resolution
issues since 2006, when the monitor was being used with a different machine
using an ATI video card.

Bug#673669: xrandr output - appears to be set to a widescreen ratio, with LCD refresh rates

[DAVID HAND]

xrandr: Failed to get size of gamma for output default
Screen 0: minimum 320 x 240, current 1280 x 800, maximum 1280 x 800
default connected 1280x800+0+0 0mm x 0mm
   1280x800   50.0*
   1024x768   51.0
   960x54052.0
   840x52553.0
   800x60054.0
   800x51255.0
   720x45056.0
   680x38457.0 58.0
   640x51259.0
   640x48060.0 61.0
   576x43262.0
   512x38463.0
   400x30064.0
   320x24065.0

Bug#671172: [xserver-xorg-video-nouveau] Flightgear buffer flush fails, freezing system

[David Baron]

On Wednesday 02 May 2012 17:37:50 Sven Joachim wrote:
> On 2012-05-02 12:51 +0200, David Baron wrote:
> > VGA-compatible devices on PCI bus:
> > --
> > 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation NV44
> > [GeForce 6200 TurboCache(TM)] [10de:0161] (rev a1)
> 
> The 3D driver for this card is known to have many problems and is
> unsupported upstream.  In Mesa git master it has been replaced by a
> different driver that will hopefully be better.  For now it is
> recommended to use Nvidia's 173xx legacy driver if you want to play 3D
> games.

The card does work perfectly with the regular nvidia package on Sid, not the 
173 legacy. I manually reconfigured for Nouveau mostly to check out a possible 
kde4.7-nvidia problem which was not the case. Nouveau is also necessary for 
the real-time preemptive kernel images on Sid because of non gnu variable 
names being used.

What I would really like to do is choose the nvidia or nouveau at boot time. 
Would involve copying xorg.conf versions, a modprob.d blacklist, and setting 
alternatives for glx and libGL.

Bug#671172: [xserver-xorg-video-nouveau] Flightgear buffer flush fails, freezing system

[David Baron]

On Wednesday 02 May 2012 13:24:21 Sven Joachim wrote:
> tags 671172 + moreinfo
> thanks
> 
> On 2012-05-02 11:35 +0200, David Baron wrote:
> > Latest and greatest improved extreme penguin racer--large scale artifacts
> > gone (nice work!). So dared to try flightgear.
> > 
> > I know that Nouveau is not yet up to this most demanding hw-accelerated
> > app,
> > 
> > However, before the upgrade, the app would eventually appear, had similar
> > artifacts as penguin racer and refresh was intermitant at best. Not
> > playable but I was not expecting it to be.
> > 
> > After upgrade, there is a buffer flush failure which freezes the system
> > which must then be reset. No way out to kill fgfs or restart X.
> 
> That's more likely a problem of the 3D driver (in the libgl1-mesa-dri
> package) that was updated as well.
Reassign if appropriate

> 
> > No trace of message in logs. Can get text by repeating the failure if
> > needed (but resets and be dangerous to filesystems).
> 
> If you have a second computer you can try to log in via ssh or capture
> kernel logs with netconsole.
> 
> > Please attach the file:
> >   /tmp/reportbug-ng-xserver-xorg-video-nouveau-UPP5TJ.txt

Here it is.
--- Output from package bug script ---
X server symlink status:

lrwxrwxrwx 1 root root 13 Oct 17  2008 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 2072872 May  1 04:12 /usr/bin/Xorg

Diversions concerning libGL are in place

diversion of /usr/lib/libGL.so to /usr/lib/mesa-diverted/libGL.so by 
glx-diversions
diversion of /usr/lib/libGL.so.1 to /usr/lib/mesa-diverted/libGL.so.1 by 
glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1 by glx-diversions
diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1.2 to 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1.2 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1.2 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.2 by glx-diversions
diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1 to 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1 by glx-diversions
diversion of /usr/lib/libGL.so.1.2 to /usr/lib/mesa-diverted/libGL.so.1.2 by 
glx-diversions
diversion of /usr/lib/x86_64-linux-gnu/libGL.so to 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so by glx-diversions

VGA-compatible devices on PCI bus:
--
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation NV44 [GeForce 6200 
TurboCache(TM)] [10de:0161] (rev a1)

Xorg X server configuration file status:

-rw-r--r-- 1 root root 4805 Apr 30 21:59 /etc/X11/xorg.conf

Contents of /etc/X11/xorg.conf:
---
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig:  version 260.19.12  (buildmeister@builder101)  Fri Oct  8 
13:54:10 PDT 2010

Section "ServerLayout"
Identifier "X.org Configured"
Screen  0  "Screen0" 0 0
InputDevice"Mouse0" "CorePointer"
InputDevice"Keyboard0" "CoreKeyboard"
EndSection

Section "ServerFlags"
 Option "AutoAddDevices" "False"
 Option "AllowEmptyInput" "False"
# Option "IgnoreABI""True"
EndSection

Section "Files"
#RgbPath "/etc/X11/rgb"
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"
EndSection

Section "Module"
Load   "record"
Load   "glx"
Load   "dbe"
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"

#DisplaySize  

Bug#671172: [xserver-xorg-video-nouveau] Flightgear buffer flush fails, freezing system

[David Baron]

Package: xserver-xorg-video-nouveau
Version: 1:0.0.16+git20120322+ab7291d-1
Severity: normal

--- Please enter the report below this line. ---
Latest and greatest improved extreme penguin racer--large scale artifacts gone 
(nice work!). So dared to try flightgear.

I know that Nouveau is not yet up to this most demanding hw-accelerated app,

However, before the upgrade, the app would eventually appear, had similar 
artifacts as penguin racer and refresh was intermitant at best. Not playable 
but I was not expecting it to be.

After upgrade, there is a buffer flush failure which freezes the system which 
must then be reset. No way out to kill fgfs or restart X.

No trace of message in logs. Can get text by repeating the failure if needed 
(but resets and be dangerous to filesystems).


--- System information. ---
Architecture: i386
Kernel:   Linux 3.1.0-1-686-pae

Debian Release: wheezy/sid
  500 unstableftp.us.debian.org 
  500 testing ftp.us.debian.org 
1 experimentalftp.us.debian.org 

--- Package information. ---
Depends(Version) | Installed
-+-===
libc6   (>= 2.4) | 2.13-31
libdrm-nouveau1a (>= 2.4.23) | 2.4.33-1
libudev0(>= 146) | 175-3.1
xorg-video-abi-12| 
xserver-xorg-core (>= 2:1.11.99.901) | 2:1.12.1-1


Recommends(Version) | Installed
===-+-
libgl1-mesa-dri (>= 7.11.1) | 8.0.2-2


Package's Suggests field is empty.



-8<---8<---8<---8<---8<---8<---8<---8<---8<--
Please attach the file: 
  /tmp/reportbug-ng-xserver-xorg-video-nouveau-UPP5TJ.txt 
to the mail. I'd do it myself if the output wasn't too long to handle.

  Thank you!
->8--->8--->8--->8--->8--->8--->8--->8--->8--

Bug#651370: libgl1-mesa-glx: need close on exec for dri device

[David Fries]

Updating the Debian bug report log:
The patch is now in master git://anongit.freedesktop.org/git/mesa/mesa
b60120608f6ddf4098bc324363197c979ee04cb7
Author: David Fries   2011-12-10 11:28:45
Committer: Dave Airlie   2012-03-11 14:05:50



-- 
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/20120311214724.ga4...@spacedout.fries.net

Bug#653018: xorg: X segfaults when I launch Emacs

[David Caldwell]

Package: xorg
Version: 1:7.6+10
Severity: important

Dear Maintainer,

Everytime I launch Emacs, X segfaults. I tried to grab a stack trace
with GDB but there were no symbols so all I got was:

Program received signal SIGSEGV, Segmentation fault.
0x7f8e125493f1 in ?? ()
(gdb) where
#0  0x7f8e125493f1 in ?? ()
#1  0x7f8e14f88440 in ?? ()
#2  0x7f8e1254a065 in ?? ()
#3  0x0055 in ?? ()
#4  0x7f8e1254d286 in ?? ()
#5  0x7f8e14fab110 in ?? ()
#6  0x in ?? ()

I still get no symbols even after installing xserver-xorg-core-dbg. I'd
love to get a better stack trace for you--Is there something else I
need to do to get symbols out of it?

I'm using the nvidia binary driver version 290.10-1 built with
module-assistant for the Debian 2.6.38-5 kernel.

-David

-- Package-specific info:
X server symlink status:

lrwxrwxrwx 1 root root 13 Jul  6  2006 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 2056592 Dec 10 13:57 /usr/bin/Xorg

Diversions concerning libGL are in place

diversion of /usr/lib/libGL.so to /usr/lib/mesa-diverted/libGL.so by 
glx-diversions
diversion of /usr/lib/libGL.so.1 to /usr/lib/mesa-diverted/libGL.so.1 by 
glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1 by glx-diversions
diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1.2 to 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1.2 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1.2 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.2 by glx-diversions
diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1 to 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1 by glx-diversions
diversion of /usr/lib/libGL.so.1.2 to /usr/lib/mesa-diverted/libGL.so.1.2 by 
glx-diversions
diversion of /usr/lib/x86_64-linux-gnu/libGL.so to 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so by glx-diversions

VGA-compatible devices on PCI bus:
--
02:00.0 VGA compatible controller [0300]: nVidia Corporation G96 [GeForce 9400 
GT] [10de:0641] (rev a1)

Xorg X server configuration file status:

-rw-r--r-- 1 root root 8153 Mar  4  2010 /etc/X11/xorg.conf

Contents of /etc/X11/xorg.conf:
---
# XF86Config-4 (XFree86 X server configuration file) generated by dexconf, the
# Debian X Configuration tool, using values from the debconf database.
#
# Edit this file with caution, and see the XF86Config-4 manual page.
# (Type "man XF86Config-4" at the shell prompt.)
#
# This file is automatically updated on xserver-xfree86 package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xfree86
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following commands as root:
#
#   cp /etc/X11/XF86Config-4 /etc/X11/XF86Config-4.custom
#   md5sum /etc/X11/XF86Config-4 > /var/lib/xfree86/XF86Config-4.md5sum
#   dpkg-reconfigure xserver-xfree86

Section "Files"
FontPath"unix/:7100"# local font server
FontPath"unix/:7101"# local font server
# if the local font server has problems, we can fall back on these
FontPath"/usr/share/fonts/X11/Type1"
FontPath"/usr/share/fonts/X11/CID"
FontPath"/usr/share/fonts/X11/misc"
FontPath"/usr/share/fonts/X11/cyrillic"
FontPath"/usr/share/fonts/X11/100dpi"
FontPath"/usr/share/fonts/X11/75dpi"
#   FontPath"/usr/lib/fonts/X11/Type1"
#   FontPath"/usr/lib/fonts/X11/CID"
#   FontPath"/usr/lib/fonts/X11/Speedo"
#   FontPath"/usr/lib/fonts/X11/misc"
#   FontPath"/usr/lib/fonts/X11/cyrillic"
#   FontPath"/usr/lib/fonts/X11/100dpi"
#   FontPath"/usr/lib/fonts/X11/75dpi"
EndSection

Section "Module"
Load"bitmap"
Load"dbe"
Load"ddc"
Load"dri"
Load"extmod"
Load"freetype"
Load"glx"
Load"int10"
Load"record"
#   Load"speedo"
Load"type1"
Load"vbe"
EndSection

Section "Extensions"
# fglrx fix: Trying to enable Compositing disables dri!
#   Option "Composite" "Enable"
EndSection

Section "InputDevice"
Identifier  &qu

Bug#651316: First version with issues

[David Weinehall]

At least I did not experience any trouble with 2.4.27-1; after upgrading
to 2.4.28-1 I've seen the screen corruption and/or X-server crashes
several times when attempting to play videos.  After downgrading back to
2.4.27-1 everything seems to work fine again (including video playback).


Regards: David
-- 
 /) David Weinehall  /) Rime on my window   (\
//  ~   //  Diamond-white roses of fire //
\)  http://www.acc.umu.se/~tao/(/   Beautiful hoar-frost   (/



-- 
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/20111211141415.gb24...@suiko.acc.umu.se

Bug#651370: libgl1-mesa-glx: need close on exec for dri device

[David Fries]

;fd == -1 && errno == EINVAL)
+#endif
+   {
+  drmdpy->fd = open(drmdpy->device_name, O_RDWR);
+  if (drmdpy->fd != -1)
+ fcntl(drmdpy->fd, F_SETFD, fcntl(drmdpy->fd, F_GETFD) | FD_CLOEXEC);
+   }
if (drmdpy->fd == -1) {
   _eglLog(_EGL_WARNING, "wayland-egl: could not open %s (%s)",
   drmdpy->device_name, strerror(errno));
diff --git a/src/gallium/state_trackers/egl/x11/x11_screen.c 
b/src/gallium/state_trackers/egl/x11/x11_screen.c
index 6155b4d..140668f 100644
--- a/src/gallium/state_trackers/egl/x11/x11_screen.c
+++ b/src/gallium/state_trackers/egl/x11/x11_screen.c
@@ -265,7 +265,15 @@ x11_screen_enable_dri2(struct x11_screen *xscr,
   if (!x11_screen_probe_dri2(xscr, NULL, NULL))
  return -1;
 
-  fd = open(xscr->dri_device, O_RDWR);
+#ifdef O_CLOEXEC
+  fd = open(xscr->dri_device, O_RDWR | O_CLOEXEC);
+  if (fd == -1 && errno == EINVAL)
+#endif
+  {
+ fd = open(xscr->dri_device, O_RDWR);
+ if (fd != -1)
+fcntl(fd, F_SETFD, fcntl(fd, F_GETFD) | FD_CLOEXEC);
+  }
   if (fd < 0) {
  _eglLog(_EGL_WARNING, "failed to open %s", xscr->dri_device);
  return -1;
diff --git a/src/glx/dri2_glx.c b/src/glx/dri2_glx.c
index 553869a..b931a7b 100644
--- a/src/glx/dri2_glx.c
+++ b/src/glx/dri2_glx.c
@@ -914,7 +914,15 @@ dri2CreateScreen(int screen, struct glx_display * priv)
   goto handle_error;
}
 
-   psc->fd = open(deviceName, O_RDWR);
+#ifdef O_CLOEXEC
+   psc->fd = open(deviceName, O_RDWR | O_CLOEXEC);
+   if (psc->fd == -1 && errno == EINVAL)
+#endif
+   {
+  psc->fd = open(deviceName, O_RDWR);
+  if (psc->fd != -1)
+ fcntl(psc->fd, F_SETFD, fcntl(psc->fd, F_GETFD) | FD_CLOEXEC);
+   }
if (psc->fd < 0) {
   ErrorMessageF("failed to open drm device: %s\n", strerror(errno));
   goto handle_error;
-- 
1.7.7.1


On Thu, Dec 08, 2011 at 08:37:46PM +0100, Julien Cristau wrote:
> On Wed, Dec  7, 2011 at 23:43:13 -0600, David Fries wrote:
> 
> > diff -upr /tmp/mesa-7.11/src/egl/drivers/dri2/platform_wayland.c 
> > mesa-7.11/src/egl/drivers/dri2/platform_wayland.c
> > --- /tmp/mesa-7.11/src/egl/drivers/dri2/platform_wayland.c  2011-07-08 
> > 20:37:09.0 -0500
> > +++ mesa-7.11/src/egl/drivers/dri2/platform_wayland.c   2011-12-07 
> > 21:28:10.0 -0600
> > @@ -734,17 +734,25 @@ drm_handle_device(void *data, struct wl_
> >  {
> > struct dri2_egl_display *dri2_dpy = data;
> > drm_magic_t magic;
> > +#ifdef O_CLOEXEC
> > +   int flags = O_RDWR | O_CLOEXEC;
> > +#else
> > +   int flags = O_RDWR;
> > +#endif
> >  
> > dri2_dpy->device_name = strdup(device);
> > if (!dri2_dpy->device_name)
> >return;
> >  
> > -   dri2_dpy->fd = open(dri2_dpy->device_name, O_RDWR);
> > +   dri2_dpy->fd = open(dri2_dpy->device_name, flags);
> > if (dri2_dpy->fd == -1) {
> >_eglLog(_EGL_WARNING, "wayland-egl: could not open %s (%s)",
> >   dri2_dpy->device_name, strerror(errno));
> >return;
> > }
> > +#ifndef O_CLOEXEC
> > +   fcntl(dri2_dpy->fd, F_SETFD, fcntl(dri2_dpy->fd, F_GETFD) | FD_CLOEXEC);
> > +#endif
> >  
> 
> I'd do something like
> 
> #ifdef O_CLOEXEC
>dri2_dpy->fd = open(dri2_dpy->device_name, O_RDWR | O_CLOEXEC);
>if (dri2_dpy->fd == -1 && errno == EINVAL)
> #endif
>{
>   dri2_dpy->fd = open(dri2_dpy->device_name, O_RDWR);
>   if (dri2_dpy->fd >= 0)
>   fcntl(dri2_dpy->fd, F_SETFD, fcntl(dri2_dpy->fd, F_GETFD) | 
> FD_CLOEXEC);
>}
>if (dri2_dpy->fd == -1) {
>_eglLog(...);
>return;
> 
> so it still works if the build environment has O_CLOEXEC but the kernel
> doesn't support it at runtime.
> 
> Cheers,
> Julien


mesa_cloexec_retry.bundle
Description: Binary data

Bug#649002: iBook touchpad stopped working

[David A. Greene]

Evgeni Golov  writes:

> Wheezy still has 1.4.1-1, which works just fine for me. Are you sure you
> aren't running sid? If you are, and you have 1.4.1-1 installed, it may
> be a different bug.

Quite right.  I had indeed upgraded to sid.  Downgrading to 1.4.1-1
fixed the problem.  So there definitely is a regression in the new
version.

Thanks for the heads-up.



-- 
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/8739ded2rd@smith.obbligato.org

Bug#649002: iBook touchpad stopped working

[David A. Greene]

I am also seeing this on a PowerBook G4 (PowerPC).  It worked when I
installed squeeze but stopped working on upgrade to wheezy.

Thanks,
David



-- 
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/8762ibsu2n@smith.obbligato.org

Bug#649002: after upgrading to latest version, iBook touchpad stopped working

[David A. Greene]

I also see this on a PowerBook G4.

processor   : 0
cpu : 7447A, altivec supported
clock   : 1666.666000MHz
revision: 1.2 (pvr 8003 0102)
bogomips: 73.72
timebase: 18432000
platform: PowerMac
model   : PowerBook5,6
machine : PowerBook5,6
motherboard : PowerBook5,6 MacRISC3 Power Macintosh 
detected as : 287 (PowerBook G4 15")
pmac flags  : 001b
L2 cache: 512K unified
pmac-generation : NewWorld
Memory  : 1536 MB

It worked with the initial squeeze install and stopped working upon
upgrading to wheezy.



-- 
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/871uszsksj@smith.obbligato.org

Q about modules and driver

[David Roguin]

Hi,

I don't really know if this is the correct list to ask this kind of
question, if not, could you please point me the right one?

I've recenty installed debian wheezy (with kernel 3.0) on a macbook pro
(8,1) . I got it up and running, but I'm struggling with the multitouch
trackpad that came with the mac.
The thing is, I'm trying to use the X module 'mtrack', but it's not even
loading. I've asked to several people and everything is where it should be
(but still is not working) so i'm wondering how is the flow between the
kernel and X, who should identify the trackpad? How does the kernel tell the
X which device to listen for input?
I was reading the example of how make a simple X module that reads from
random, but looking in this mtrack module i could't find anything that point
to the right input device; I'm asumming the kernel or X should do some
discovery of their own.

Tthanks for reading :)

-- 
David

Bug#640502: glxinfo

[David Goodenough]

I am running on a laptop, and have the modern X self configuration, i.e.  I 
have no X configuration file.

My guess is that this card is so primitive that it does not support GLX itself
and so Mesa picks it up.

BTW, sorry about not replying earlier, but for some reason the bug system did 
not subscribe me so I did not see that there had been any activity.

David

glxinfo reports:-

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_multisample, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, 
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_copy_sub_buffer, 
GLX_OML_swap_method, GLX_SGI_make_current_read, GLX_SGI_swap_control, 
GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, 
GLX_SGIX_visual_select_group, GLX_INTEL_swap_event
client glx vendor string: Mesa Project and SGI
client glx version string: 1.4
client glx extensions:
GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context, 
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_framebuffer_sRGB, 
GLX_MESA_copy_sub_buffer, GLX_MESA_multithread_makecurrent, 
GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, 
GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync, 
GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, 
GLX_SGIX_visual_select_group, GLX_EXT_texture_from_pixmap, 
GLX_INTEL_swap_event
GLX version: 1.4
GLX extensions:
GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context, 
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_copy_sub_buffer, 
GLX_MESA_multithread_makecurrent, GLX_MESA_swap_control, 
GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGI_make_current_read, 
GLX_SGI_swap_control, GLX_SGI_video_sync, GLX_SGIS_multisample, 
GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, 
GLX_EXT_texture_from_pixmap, GLX_INTEL_swap_event
OpenGL vendor string: Tungsten Graphics, Inc
OpenGL renderer string: Mesa DRI Intel(R) 852GM/855GM x86/MMX/SSE2
OpenGL version string: 1.3 Mesa 7.11
OpenGL extensions:
GL_ARB_multisample, GL_EXT_abgr, GL_EXT_bgra, GL_EXT_blend_color, 
GL_EXT_blend_logic_op, GL_EXT_blend_minmax, GL_EXT_blend_subtract, 
GL_EXT_copy_texture, GL_EXT_polygon_offset, GL_EXT_subtexture, 
GL_EXT_texture_object, GL_EXT_vertex_array, GL_EXT_compiled_vertex_array, 
GL_EXT_texture, GL_EXT_texture3D, GL_IBM_rasterpos_clip,
   
GL_ARB_point_parameters, GL_EXT_draw_range_elements, GL_EXT_packed_pixels,  
   
GL_EXT_point_parameters, GL_EXT_rescale_normal, 
   
GL_EXT_separate_specular_color, GL_EXT_texture_edge_clamp,  
   
GL_SGIS_generate_mipmap, GL_SGIS_texture_border_clamp,  
   
GL_SGIS_texture_edge_clamp, GL_SGIS_texture_lod, GL_ARB_multitexture,   
   
GL_IBM_multimode_draw_arrays, GL_IBM_texture_mirrored_repeat,   
   
GL_3DFX_texture_compression_FXT1, GL_ARB_texture_cube_map, 
GL_ARB_texture_env_add, GL_ARB_transpose_matrix, 
GL_EXT_blend_func_separate, GL_EXT_fog_coord, GL_EXT_multi_draw_arrays, 
GL_EXT_secondary_color, GL_EXT_texture_env_add, 
GL_EXT_texture_filter_anisotropic, GL_EXT_texture_lod_bias, 
GL_INGR_blend_func_separate, GL_NV_blend_square, GL_NV_light_max_exponent, 
GL_NV_texgen_reflection, GL_SUN_multi_draw_arrays, 
GL_ARB_texture_border_clamp, GL_ARB_texture_compression, 
GL_EXT_framebuffer_object, GL_EXT_texture_env_dot3, GL_MESA_window_pos, 
GL_NV_packed_depth_stencil, GL_NV_texture_rectangle, GL_NV_vertex_program, 
GL_ARB_texture_env_combine, GL_ARB_texture_env_crossbar, 
GL_ARB_texture_env_dot3, GL_ARB_texture_mirrored_repeat, 
GL_ARB_window_pos, GL_EXT_texture_cube_map, GL_NV_vertex_program1_1, 
GL_APPLE_client_storage, GL_APPLE_packed_pixels, 
GL_APPLE_vertex_array_object, GL_ARB_draw_buffers, GL_ARB_shader_objects, 
GL_ARB_vertex_program, GL_ARB_vertex_shader, GL_ATI_draw_buffers, 
GL_EXT_stencil_wrap, GL_MESA_pack_invert, GL_MESA_ycbcr_texture, 
GL_ARB_half_float_pixel, GL_ARB_point_sprite, GL_ARB_shading_language_100, 
GL_ARB_sync, GL_ARB_vertex_buffer_object, GL_ATI_blend_equation_separate, 
GL_EXT_blend_equation_separate, GL_OES_read_format, 
GL_ARB_pixel_buffer_object, GL_ARB_texture_rectangle, 
GL_EXT_pixel_buffer_object, GL_EXT_texture_rectangle, 
GL_ARB_framebuffer_object

Bug#634289: radeon: Temporary semi-freeze when running Ryzom-client and gnash

[David H]

Package: libgl1-mesa-dri
Version: 7.7.1-4
Severity: normal
File: radeon


Running the current version of the Ryzom game client (version FV 1.10.2 (Nov  9 
2010 10:13:38)) yields a semi freeze when passing the login screen and
entering character generation / selection screen. Mouse movement stops for a 
few seconds then for a fraction of a second mouse input is applied normally.

This behavior is existant also if the login screen window is just minimized.

Recently i noticed that the very same behavior is exhibited by gnash (0.8.8-5) 
as in conjunction of a specific flash file too. This leads to my belief
that its not an application failure but a problem with the r300 dri renderer 
(classic).

I'm trying to obtain the specific flash file for further examination and will 
add this later on.

HW used: R430-based radeon card, using the non-free microcode, the oss radeon 
driver and KMS set to active.

-- System Information:
Debian Release: 6.0.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'oldstable'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libgl1-mesa-dri depends on:
ii  libc6 2.11.2-10  Embedded GNU C Library: Shared lib
ii  libdrm-intel1 2.4.23-0.0 Userspace interface to intel-speci
ii  libdrm-radeon12.4.23-0.0 Userspace interface to radeon-spec
ii  libdrm2   2.4.23-0.0 Userspace interface to kernel DRM 
ii  libexpat1 2.0.1-7XML parsing C library - runtime li

libgl1-mesa-dri recommends no packages.

Versions of packages libgl1-mesa-dri suggests:
pn  libglide3  (no description available)

-- 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: http://lists.debian.org/20110718133911.30840.20560.reportbug@bunker

Bug#405859: radeon: Hardware incompatibility?

[David H]

Package: libgl1-mesa-dri
Severity: normal
File: radeon


Afaik Matrox graphics used a 24bit framebuffer internally. And thereby lacking 
true RGBA support (and used instead a plain RGB888 structure).

Handling transparency is probably limited to textures only. Surfaces do not per 
se support transparency.

-- System Information:
Debian Release: 6.0.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'oldstable'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libgl1-mesa-dri depends on:
ii  libc6 2.11.2-10  Embedded GNU C Library: Shared lib
ii  libdrm-intel1 2.4.23-0.0 Userspace interface to intel-speci
ii  libdrm-radeon12.4.23-0.0 Userspace interface to radeon-spec
ii  libdrm2   2.4.23-0.0 Userspace interface to kernel DRM 
ii  libexpat1 2.0.1-7XML parsing C library - runtime li

libgl1-mesa-dri recommends no packages.

Versions of packages libgl1-mesa-dri suggests:
pn  libglide3  (no description available)

-- 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: http://lists.debian.org/20110718130607.30645.54460.reportbug@bunker

Bug#598390: workaround

[Dr. David Alan Gilbert]

Hi,
  A fairly grim workaround is to disable hardware acceleration in
Flash; right click on it and using the settings pane click on the
tick next to 'Enable hardware acceleration'.

That gets me working full screen - it's faster than what I get
with nomodesetting but still somewhat grim.

Dave
-- 
 -Open up your eyes, open up your mind, open up your code ---   
/ Dr. David Alan Gilbert|   Running GNU/Linux   | Happy  \ 
\ gro.gilbert @ treblig.org |   | In Hex /
 \ _|_ http://www.treblig.org   |___/



-- 
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/20110619164203.GG2031@gallifrey

Bug#613212: xserver-xorg-video-intel: X freezes, gdm can't be restarted until reboot

[David Lee Lambert]

Package: xserver-xorg-video-intel
Version: 2:2.3.2-2+lenny8
Followup-For: Bug #613212

Happened to me on newly installed Debian 5.0 on an IBM ThinkCentre
using the on-board graphics adapter.  Twice I've been looking at webpages
with Epiphany (first time clicked a button, second time used a scroll-bar),
and the system locked up.  Apparently I won't be able to use the "intel"
driver until I reboot.  "vesa" driver seems to be an OK workaround, except
that I'm having trouble setting the monitor resolution ("intel" detected
it fine)...

-- Package-specific info:
Contents of /var/lib/x11/X.roster:
xserver-xorg

/var/lib/x11/X.md5sum does not exist.

X server symlink status:
lrwxrwxrwx 1 root root 13 2011-04-30 08:20 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 1718548 2010-09-25 08:23 /usr/bin/Xorg

Contents of /var/lib/x11/xorg.conf.roster:
xserver-xorg

VGA-compatible devices on PCI bus:
00:02.0 VGA compatible controller: Intel Corporation 82945G/GZ Integrated 
Graphics Controller (rev 02)

/etc/X11/xorg.conf does not match checksum in /var/lib/x11/xorg.conf.md5sum.

Xorg X server configuration file status:
-rw-r--r-- 1 root root 1410 2011-05-02 07:49 /etc/X11/xorg.conf

Contents of /etc/X11/xorg.conf:
# xorg.conf (X.Org X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the xorg.conf manual page.
# (Type "man xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
#   sudo dpkg-reconfigure -phigh xserver-xorg

Section "InputDevice"
Identifier  "Generic Keyboard"
Driver  "kbd"
Option  "XkbRules"  "xorg"
Option  "XkbModel"  "pc104"
Option  "XkbLayout" "us"
EndSection

Section "InputDevice"
Identifier  "Configured Mouse"
Driver  "mouse"
EndSection

Section "Device"
Identifier  "Configured Video Device"
Driver "intel"
##  Option  "UseFBDev"  "true"
##Driver "vesa"
EndSection

Section "Monitor"
Identifier  "Configured Monitor"
VendorName "Samsung"
ModelName "SyncMaster 172N"
HorizSync 30-81
VertRefresh 56-75
EndSection

Section "Screen"
Identifier  "Default Screen"
Monitor "Configured Monitor"
Subsection "Display"
  Viewport 0 0
  Depth 24
  Modes "1280x1024" "720x400" "640x480"
EndSubSection
EndSection


Xorg X server log files on system:
-rw-r--r-- 1 root root 32806 2011-05-02 07:49 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file
/var/log/Xorg.0.log:

X.Org X Server 1.4.2
Release Date: 11 June 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux Debian (xorg-server 2:1.4.2-10.lenny3)
Current Operating System: Linux huitzil 2.6.26-2-686 #1 SMP Thu Jan 27 00:28:05 
UTC 2011 i686
Build Date: 25 September 2010  12:05:44PM
 
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon May  2 07:49:38 2011
(==) Using config file: "/etc/X11/xorg.conf"
(==) No Layout section.  Using the first Screen section.
(**) |-->Screen "Default Screen" (0)
(**) |   |-->Monitor "Configured Monitor"
(==) No device specified for screen "Default Screen".
Using the first device section listed.
(**) |   |-->Device "Configured Video Device"
(==) |-->Input Device "Configured Mouse"
(==) |-->Input Device "Generic Keyboard"
(==) The core pointer device wasn't specified explicitly in the layout.
Using the first mouse device.
(==) The core keyboard device wasn't specified explicitly in the layout.
Using the first keyboard device.
(==) Automatically adding devices
(==) Automatically enabling devices
(==) No FontPath specified.  Using compiled-in default.
(WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
Entry deleted from font path.
(WW) The directory "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType" does not 
exist.
Entry deleted from font path.
(==) 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
(==) RgbPath set to "/etc/X11/rgb"
(==) ModulePath set to "

Bug#624553: xserver-xorg-video-nouveau: Monitor is not detected by driver: no EDID information is retrived

[David Westberg]

On Fri, Apr 29, 2011 at 06:23:18PM +0200, Sven Joachim wrote:
> On 2011-04-29 17:00 +0200, David Westberg wrote:
> 
> > Package: xserver-xorg-video-nouveau
> > Version: 1:0.0.15+git20100329+7858345-5
> > Severity: normal
> >
> > EDID is not retrived using the nouveau driver. Thus driver does not use the
> > monitor at default resolution, 1280x1024.
> 
> The nouveau driver gets EDID information from the kernel, so the
> question is whether the kernel has it.  Do you have something in
> /sys/class/drm/card0-VGA-1/edid or /sys/class/drm/card0-DVI-I-1/edid ?
They are empty as far as I can see.

I switched to the nvidia driver to see what is displayed for the same files.
They are however not to be found. Nvidia must have adifferent way of accessing 
the
monitor information.
 
> Strange that this succeeds if nvidia is loaded and fails otherwise.
> 
> Regards,
> Sven
Depends I guess on the interaction between the driver and monitor and the
get-edid command. could be some context that are not properly setup for
the command to succed. Don't know the relationship between monitor information
and the kernel and the driver.
Is it something the driver has todo and provide to the kernel?

/david



-- 
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/20110501113836.ga5...@uarda.dlinkddns.com

Bug#422430: xserver-xorg: No keyboard input except for

[John David Anglin]

> > After starting X using any of gdm, kdm or xstart, keyboard wasn't
> > accepted. [=E2=80=A6]
> 
> is that still happening in an up-to-date squeeze (or higher) system?

No.  This issue was an upgrade problem (old X version).

Dave
-- 
J. David Anglin  dave.ang...@nrc-cnrc.gc.ca
National Research Council of Canada  (613) 990-0752 (FAX: 952-6602)



-- 
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/20110228014754.791635...@hiauly1.hia.nrc.ca

Bug#614512: FTBFS in version 8.0.1-2

[David Witbrodt]

> From: Cyril Brulebois 

> Sent: Tue, February 22, 2011 7:02:55 AM
> Subject: Re: Bug#614512: FTBFS in version 8.0.1-2
> 
> Dave Witbrodt   (21/02/2011):
[...]
> > I was able  to resolve the problem after doing a bit of research.  I
> > found that  'xeglgears.c' and 'xeglthreads.c' (in 'src/egl/opengl')
> > both depend on  libX11, and 'xeglthreads.c' also depends on
> > libpthreads.
> 
> Thanks  for the patch; it should be checked (not sure hardcoding
> -lpthreads is the  right thing to do) and then sent upstream.

I was not sure about that either.  I got the idea from my Google search
and from looking around at the 'git log' in 'mesa-demos' around the
time frame of March 2010:


dawitbro@fileserver:~/sandbox/git/mesa-demos-git$ git show 
83580b776832d22d0039d820c637fe0be0855467
commit 83580b776832d22d0039d820c637fe0be0855467
Author: Chia-I Wu 
Date:   Wed Mar 24 08:34:39 2010 +0800

progs/egl: Link xeglthreads to libpthread.

This should hopefully fix a build failure reported by Chris Ball when
binutils-gold is used.

diff --git a/src/egl/Makefile b/src/egl/Makefile
index 8dfcb4e..890240f 100644
--- a/src/egl/Makefile
+++ b/src/egl/Makefile
@@ -60,7 +60,7 @@ xeglgears: xeglgears.o $(HEADERS) $(LIB_DEP)
$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $< $(LIBS) -lm $(X11_LIBS)
 
 xeglthreads: xeglthreads.o $(HEADERS) $(LIB_DEP)
-   $(CC) $(CFLAGS) $(LDFLAGS) -o $@ $< $(LIBS) -lm $(X11_LIBS)
+   $(CC) $(CFLAGS) $(LDFLAGS) -o $@ $< $(LIBS) -lpthread -lm $(X11_LIBS)
 
 xegl_tri: xegl_tri.o $(HEADERS) $(LIB_DEP)
$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $< $(LIBS) -lm $(X11_LIBS)


Apparently, the build system for 'mesa-demos' was reworked when they
ripped it out of 'mesa', and it had been working fine until now.  I see
this in the 'gcc-4.4' changelog (Feb. 15):

  * Pass --no-add-needed by default to the linker. See
http://wiki.debian.org/ToolChain/DSOLinking, section "Not resolving symbols
in indirect dependent shared libraries" for more information.

Is that the culprit?

By "checked" and "sent upstream," did you mean one of you XSF folks will
do that, or were you asking me to do that?


Thanks for your rapid response,
Dave W.



-- 
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/678556.26591...@web82107.mail.mud.yahoo.com

Bug#612241: compiz-plugins: Desktop Wall plugin disables some clicks

[david roguin]

Package: compiz-plugins
Version: 0.8.4-4
Severity: normal

Whenever I activate the wall plugin clicks clicked on the lowest part of
the screen aren't working correctly.
If i want to open a window by clicking on the gnome panel i have to
click a few pixels above the bottom of the screen.
The same thing happens on the very top of the screen, trying to click on
the gnome menu.


-- System Information:
Debian Release: 6.0
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
Locale: LANG=es_AR.utf8, LC_CTYPE=es_AR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages compiz-plugins depends on:
ii  compiz-core 0.8.4-4  
ii  gconf2  2.28.1-6 
ii  libc6   2.11.2-10
ii  libcairo2   1.8.10-6 
ii  libdbus-1-3 1.2.24-4 
ii  libdecoration0  0.8.4-4  
ii  libglib2.0-02.24.2-1 
ii  libglu1-mesa [libglu1]  7.7.1-4  
ii  libgtk2.0-0 2.20.1-2 
ii  libpng12-0  1.2.44-1 
ii  librsvg2-2  2.26.3-1 
ii  libx11-62:1.3.3-4
ii  libxml2 2.7.8.dfsg-2 
ii  libxrender1 1:0.9.6-1

compiz-plugins recommends no packages.

compiz-plugins suggests no packages.

-- no debconf information

-- 
David




-- 
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/1297044513.16139.2.camel@localhost

Bug#609222: x11-apps: [xeyes] New xeyes produces RenderBadPicture error

[Jonathan David Amery]

Package: x11-apps
Version: 7.5+5
Severity: normal

*** Please type your report below this line ***
Hi,

 I've just upgraded to squeeze and xeyes is now giving me the following
error:

X Error of failed request:  RenderBadPicture (invalid Picture parameter)
  Major opcode of failed request:  152 (RENDER)
  Minor opcode of failed request:  10 (RenderTrapezoids)
  Picture id in failed request: 0x268
  Serial number of failed request:  60
  Current serial number in output stream:  64

 The old xeyes from lenny still works.

J.

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages x11-apps depends on:
ii  cpp   4:4.4.5-1  The GNU C preprocessor (cpp)
ii  libc6 2.11.2-7   Embedded GNU C Library: Shared lib
ii  libpng12-01.2.44-1   PNG library - runtime
ii  libsm62:1.1.1-1  X11 Session Management library
ii  libx11-6  2:1.3.3-4  X11 client-side library
ii  libxaw7   2:1.0.7-1  X11 Athena Widget library
ii  libxcursor1   1:1.1.10-2 X cursor management library
ii  libxext6  2:1.1.2-1  X11 miscellaneous extension librar
ii  libxft2   2.1.14-2   FreeType-based font drawing librar
ii  libxkbfile1   1:1.0.6-2  X11 keyboard file manipulation lib
ii  libxmu6   2:1.0.5-2  X11 miscellaneous utility library
ii  libxmuu1  2:1.0.5-2  X11 miscellaneous micro-utility li
ii  libxrender1   1:0.9.6-1  X Rendering Extension client libra
ii  libxt61:1.0.7-1  X11 toolkit intrinsics library
ii  x11-common1:7.5+8X Window System (X.Org) infrastruc

x11-apps recommends no packages.

Versions of packages x11-apps suggests:
ii  mesa-utils7.7.1-4Miscellaneous Mesa GL
utilities

-- debconf-show failed



-- 
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/e1pbdsc-0005iw...@cleopatra.thy.me.uk

Bug#511910: xserver-xorg-input-evtouch 0.8.7-3 does not work with HAL

[David Hagood]

Since evdev now supports the touchscreen interfaces, we've moved to it,
and so I have no information on the current status of evtouch.

You can close this out if you wish.

Notice: This e-mail is intended solely for use of the individual or entity to 
which it is
addressed and may contain information that is proprietary, privileged, company 
confidential
and/or exempt from disclosure under applicable law. If the reader is not the 
intended
recipient or agent responsible for delivering the message to the intended 
recipient, you are
hereby notified that any dissemination, distribution or copying of this 
communication is
strictly prohibited. If this communication has been transmitted from a U.S. 
location it may
also contain data subject to the International Traffic in Arms Regulations or 
U.S. Export
Administration Regulations and cannot be disseminated, distributed or copied to 
foreign
nationals, residing in the U.S. or abroad, without the prior approval of the 
U.S. Department
of State or appropriate export licensing authority. If you have received this 
communication
in error, please notify the sender by reply e-mail or collect telephone call 
and delete or
destroy all copies of this e-mail message, any physical copies made of this 
e-mail message
and/or any file attachment(s).




--
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/1294068152.5496.5.ca...@wic-102362.wic.aeroflex.com

Re: Bug#606720: xserver-xorg-video-intel: Resolution is limited to 1280x1024 on vaio z13 instead of 1920x1080

[Louis-David Mitterrand]

On Sat, Dec 11, 2010 at 01:33:17PM +0100, Laurent CARON wrote:
> On 11/12/2010 10:03, Julien Cristau wrote:
> >On Sat, Dec 11, 2010 at 08:08:41 +0100, Laurent CARON wrote:
> >
> >>Package: xserver-xorg-video-intel
> >>Version: 2:2.13.0-4
> >>Severity: important
> >>
> >>
> >>
> >>Hi,
> >>
> >>After upgrading from
> >>2:2.13.0-4
> >>to
> >>2:2.13.0-2
> >>
> >>the screen resolution doesn't go to 1920x1080 anymore.
> >>
> >You need to set CONFIG_DRM_I915_KMS=y in your kernel configuration.
> 
> If I set it once the kernel is loaded, the screen is just black. The
> laptop is however accessible over SSH.

Did you disable any framebuffer device in your kernel configuration?


-- 
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/20101211124529.ga1...@apartia.fr

Bug#601558: Blnak screen

[Robert David]

I can confirm this bug. I halve intel GMA945 and resolution 1024x600. Display 
turn black when KMS start. I can login (blindly) and than suspend (hotkey), 
after resume the screen is ok. I dont think disabling KMS is the solution, I 
use KMS for a long time and had this problem since the last few kernel updates 
2.6.32-5-686. When I plugin VGA display in and boot, I can see the login 
screen on both displays with resolution 800x600. So it may be something with 
startup mode selection.

Robert David.


signature.asc
Description: This is a digitally signed message part.

Bug#600979: xserver-xorg-video-radeon: with a secondary user login via a new gdm session video playing colour is too dark

[david b]

Package: xserver-xorg-video-radeon
Version: 1:6.13.1-2
Severity: normal

Story: watch a video on secondary x session.
As An admin
I want to let other users use my system and let them watch videos
So that they won't get too bored ;) 

When I start a new session as another user via gdm
And I try play a video using vlc. 
Then I see a dark version of the video shown.

The above should be:
When I start a new session as another user via gdm
And I try play a video using vlc. 
Then I see the video.

It doesn't matter which video player I use.

-- System Information:
Debian Release: 5.0.6
  APT prefers stable
  APT policy: (900, 'stable'), (600, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.36 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash



-- 
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/20101022034556.9289.9164.report...@linode.d1b.org