Bug#1076248: Please package 1.23.0

[Guido Günther]

Source: wayland
Version: 1.22.0-2.1
Severity: wishlist

Hi,
wayland 1.23 is out:

   https://gitlab.freedesktop.org/wayland/wayland/-/tags/1.23.0

Would be nice to have it in Debian (it's needed for wlroots 0.18.0).
Cheers,
 -- Guido


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: arm64

Kernel: Linux 6.8.12-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#1061616: New upstream version 0.43.0

[Guido Günther]

Source: pixman
Version: 0.42.2-1
Severity: wishlist

There's a new upstream version. It seems pixman gave up on the odd/even split:

   https://gitlab.freedesktop.org/pixman/pixman/-/issues/87#note_2243045

It seems there's some details to be sorted out but e.g. having it in
expermental would be awesome as wlroots is about to bump it's dependency.
Cheers,
 -- Guido


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: arm64

Kernel: Linux 6.5.0-5-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#1035563: New upstream version 1.22.0

[Guido Günther]

Source: wayland
Version: 1.21.0-1
Severity: wishlist


Hi,
wayland 1.22.0 has been released:

   https://gitlab.freedesktop.org/wayland/wayland/-/tags/1.22.0

Would be great to have that in experimental. I've made an MR to update
here:

   https://salsa.debian.org/xorg-team/wayland/wayland/-/merge_requests/5

Happy to NMU if that looks o.k.

Cheers,
 -- Guido


-- System Information:
Debian Release: 12.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-updates'), (500, 'stable-debug'), (500, 
'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental-debug'), 
(1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: arm64

Kernel: Linux 6.1.0-7-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#1001965: Fails to build from source due to outdated symbols file

[Guido Günther]

Source: libdrm
Version: 2.4.109-1
Severity: serious
Tags: patch

Hi,
2.4.109-1 fails to build like:

dpkg-gensymbols: warning: debian/libdrm-amdgpu1/DEBIAN/symbols doesn't match 
completely debian/libdrm-amdgpu1.symbols
--- debian/libdrm-amdgpu1.symbols (libdrm-amdgpu1_2.4.109-1_amd64)
+++ dpkg-gensymbolsRbfBrW   2021-12-18 17:31:37.021023907 +
@@ -53,6 +53,7 @@
  amdgpu_cs_wait_fences@Base 2.4.81
  amdgpu_cs_wait_semaphore@Base 2.4.67
  amdgpu_device_deinitialize@Base 2.4.63
+ amdgpu_device_get_fd@Base 2.4.109-1
  amdgpu_device_initialize@Base 2.4.63
  amdgpu_find_bo_by_cpu_mapping@Base 2.4.94
  amdgpu_get_marketing_name@Base 2.4.73
dh_makeshlibs: error: failing due to earlier errors
make[1]: *** [debian/rules:121: override_dh_makeshlibs] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:141: binary-arch] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned 
exit status 2

Full log: 
https://buildd.debian.org/status/fetch.php?pkg=libdrm=amd64=2.4.109-1=1639848700=0

Attached patch fixes that for me and I'm happy to NMU if that looks
correct. The symbol got added in
f70e8ae83590d2a1fb1972dc7e875dd6a9355b77 upstream and looks like a valid new
public symbol.

Cheers,
 -- Guido
 

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'stable-updates'), (500, 'stable-debug'), (500, 'unstable'), (500, 'testing'), 
(500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.15.0-2-amd64 (SMP w/4 CPU threads)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
>From 0ecc96a5514e030a91be47d62febf7e656170fff Mon Sep 17 00:00:00 2001
Message-Id: <0ecc96a5514e030a91be47d62febf7e656170fff.1639931516.git@sigxcpu.org>
From: =?UTF-8?q?Guido=20G=C3=BCnther?= 
Date: Sun, 19 Dec 2021 17:22:10 +0100
Subject: [PATCH] Update symbols file

---
 debian/libdrm-amdgpu1.symbols | 1 +
 1 file changed, 1 insertion(+)

diff --git a/debian/libdrm-amdgpu1.symbols b/debian/libdrm-amdgpu1.symbols
index 6ce3d569..d04300e8 100644
--- a/debian/libdrm-amdgpu1.symbols
+++ b/debian/libdrm-amdgpu1.symbols
@@ -53,6 +53,7 @@ libdrm_amdgpu.so.1 libdrm-amdgpu1 #MINVER#
  amdgpu_cs_wait_fences@Base 2.4.81
  amdgpu_cs_wait_semaphore@Base 2.4.67
  amdgpu_device_deinitialize@Base 2.4.63
+ amdgpu_device_get_fd@Base 2.4.109
  amdgpu_device_initialize@Base 2.4.63
  amdgpu_find_bo_by_cpu_mapping@Base 2.4.94
  amdgpu_get_marketing_name@Base 2.4.73
-- 
2.33.0

Bug#1001840: closed by Debian FTP Masters (reply to Timo Aaltonen ) (Bug#1001840: fixed in libdrm 2.4.109-1)

[Guido Günther]

Hi Timo,
[..snip..]
 
> Source: libdrm
> Source-Version: 2.4.109-1
> Done: Timo Aaltonen 

Thanks a lot for the prompt update!
Cheers,
 -- Guido

Bug#1001828: eglQueryDevicesEXT doesn't update as new devices are added

[Guido Günther]

Hi,
On Fri, Dec 17, 2021 at 09:15:34AM +0100, Guido Günther wrote:
> and I also asked for a new release to make this simpler for
> distributions to ship
> 
> https://gitlab.freedesktop.org/glvnd/libglvnd/-/issues/226

There's a 1.4.0 upstream version now having all the patches:

https://gitlab.freedesktop.org/glvnd/libglvnd/-/tags/v1.4.0

Cheers,
 -- Guido

Bug#1001840: New upstream version 2.4.109

[Guido Günther]

Source: libdrm
Version: 2.4.108-1
Severity: wishlist

Hi,
It would be great to have libdrm2 2.4.109 in sid or
experimental. wlroots 0.15.0 (just released) depends on it for dmabuf
feedback support.

Cheers and thanks a lot for keeping libdrm in shape all the time!
 -- Guido



-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'stable-updates'), (500, 'stable-debug'), (500, 'unstable'), (500, 'testing'), 
(500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.15.0-2-amd64 (SMP w/4 CPU threads)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#1001839: New upstream version 1.20.0

[Guido Günther]

Source: wayland
Version: 1.19.0-2
Severity: wishlist

Hi,

it would be great to have wayland 1.20.0¹ (only released a week ago) in
sid or experimental since wlroots 0.15.0 depends on it.

Cheers,
 -- Guido


1) https://gitlab.freedesktop.org/wayland/wayland/-/tags/1.20.0

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'stable-updates'), (500, 'stable-debug'), (500, 'unstable'), (500, 'testing'), 
(500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.15.0-2-amd64 (SMP w/4 CPU threads)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#1001828: eglQueryDevicesEXT doesn't update as new devices are added

[Guido Günther]

Package: libglvnd0
Version: 1.3.4-2+b1
Severity: normal

Hi,
Current glvnd's static device list is problematic when a display
controller is probed at a later point. For an example see

https://gitlab.freedesktop.org/glvnd/libglvnd/-/issues/215

This also happens on e.g. imx8 devices where the 2nd display controller
is brought up at a later point making rendering with e.g. wlroots based
compositor fail (and it works when taking glvnd out of the mix). This
wasn't an issue until wlroots 0.14.1 entered unstable since older
wlroots used another way to figure out display devices.

There's an upstream MR 

https://gitlab.freedesktop.org/glvnd/libglvnd/-/merge_requests/239

and I also asked for a new release to make this simpler for
distributions to ship

https://gitlab.freedesktop.org/glvnd/libglvnd/-/issues/226

Cheers,
 -- Guido

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'stable-updates'), (500, 'stable-debug'), (500, 'unstable'), (500, 'testing'), 
(500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.15.0-2-amd64 (SMP w/4 CPU threads)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libglvnd0 depends on:
ii  libc6  2.33-1

libglvnd0 recommends no packages.

libglvnd0 suggests no packages.

Versions of packages libglvnd0 is related to:
pn  libgl1-nvidia-glx-any  

-- no debconf information

Bug#930514: libgles2-mesa-dev: glesv2.pc missing

[Guido Günther]

Hi,
On Fri, Jun 14, 2019 at 10:32:11PM +0300, Timo Aaltonen wrote:
> 
> Hi,
> 
> On 14.6.2019 12.34, Guido Günther wrote:
> > Package: libgles2-mesa-dev
> > Version: 19.1.0-1
> > Severity: normal
> > 
> > Hi,
> > The package config file went missing in 19.1.0-1:
> > 
> >https://packages.debian.org/experimental/arm64/libgles2-mesa-dev/filelist
> > 
> > I noticed when rebuilding wlroots against that version.

Thanks. So is the plan to pull this into glvnd in Debian?
Cheers,
 -- Guido

> 
> it's not generated anymore when built with GLVND
> 
> https://bugs.freedesktop.org/show_bug.cgi?id=110141
> https://github.com/NVIDIA/libglvnd/pull/

Bug#930514: libgles2-mesa-dev: glesv2.pc missing

[Guido Günther]

Package: libgles2-mesa-dev
Version: 19.1.0-1
Severity: normal

Hi,
The package config file went missing in 19.1.0-1:

   https://packages.debian.org/experimental/arm64/libgles2-mesa-dev/filelist

I noticed when rebuilding wlroots against that version.

Cheers and thanks for keeping up so quickly with mesa releases,
 -- Guido

Bug#930513: libgles2-mesa-dev: libglesv2.pc went missing

[Guido Günther]

Package: libgles2-mesa-dev
Version: 18.3.4-2
Severity: normal



-- Package-specific info:
glxinfo:

name of display: :0
display: :0  screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
server glx extensions:
GLX_ARB_context_flush_control, GLX_ARB_create_context, 
GLX_ARB_create_context_no_error, GLX_ARB_create_context_profile, 
GLX_ARB_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_MESA_copy_sub_buffer, GLX_OML_swap_method, GLX_SGIS_multisample, 
GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, 
GLX_SGI_make_current_read
client glx vendor string: Mesa Project and SGI
client glx version string: 1.4
client glx extensions:
GLX_ARB_context_flush_control, GLX_ARB_create_context, 
GLX_ARB_create_context_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_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_MESA_copy_sub_buffer, GLX_MESA_query_renderer, 
GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, 
GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, 
GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, 
GLX_SGI_video_sync
Extended renderer info (GLX_MESA_query_renderer):
Vendor: Intel Open Source Technology Center (0x8086)
Device: Mesa DRI Intel(R) Haswell Mobile  (0xa16)
Version: 18.3.4
Accelerated: yes
Video memory: 1536MB
Unified memory: yes
Preferred profile: core (0x1)
Max core profile version: 4.5
Max compat profile version: 3.0
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.1
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Haswell Mobile 
OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.3.4
OpenGL core profile shading language version string: 4.50
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
GL_3DFX_texture_compression_FXT1, GL_AMD_conservative_depth, 
GL_AMD_draw_buffers_blend, GL_AMD_multi_draw_indirect, 
GL_AMD_query_buffer_object, GL_AMD_seamless_cubemap_per_texture, 
GL_AMD_shader_trinary_minmax, GL_AMD_vertex_shader_layer, 
GL_AMD_vertex_shader_viewport_index, GL_ANGLE_texture_compression_dxt3, 
GL_ANGLE_texture_compression_dxt5, GL_APPLE_object_purgeable, 
GL_ARB_ES2_compatibility, GL_ARB_ES3_1_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, 
GL_ARB_draw_instanced, GL_ARB_enhanced_layouts, 
GL_ARB_explicit_attrib_location, GL_ARB_explicit_uniform_location, 
GL_ARB_fragment_coord_conventions, GL_ARB_fragment_layer_viewport, 
GL_ARB_fragment_shader, GL_ARB_fragment_shader_interlock, 
GL_ARB_framebuffer_no_attachments, GL_ARB_framebuffer_object, 
GL_ARB_framebuffer_sRGB, GL_ARB_get_program_binary, 
GL_ARB_get_texture_sub_image, GL_ARB_gpu_shader5, 

Bug#911146: xwayland spurious crashes

[Guido Günther]

Hi,
On Tue, Oct 16, 2018 at 06:59:35PM +0200, Guido Günther wrote:
> control: -1 tags +patch
> 
> Hi,
> On Tue, Oct 16, 2018 at 01:26:41PM +0200, Guido Günther wrote:
> > Package: xwayland
> > Version: 2:1.20.1-5
> > Severity: normal
> > 
> > Hi,
> > since a couple of days I'm seeing spurious xwayland crashes like
> > 
> > Core was generated by `Xwayland :0 -rootless -terminate -listen 12 -listen 
> > 13 -wm 53'.
> > Program terminated with signal SIGABRT, Aborted.
> > #0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
> > #1  0x7f367b3f32f1 in __GI_abort () at abort.c:79
> > #2  0x5647cc51258a in OsAbort () at ../../../../os/utils.c:1350
> > #3  0x5647cc518093 in AbortServer () at ../../../../os/log.c:877
> > #4  0x5647cc518ef9 in FatalError (f=f@entry=0x5647cc53c050 "Caught 
> > signal %d (%s). Server aborting\n") at ../../../../os/log.c:1015
> > #5  0x5647cc50f9a1 in OsSigHandler (signo=11, sip=, 
> > unused=) at ../../../../os/osinit.c:156
> > #6  
> > #7  0x5647cc476c3e in present_vblank_notify 
> > (vblank=vblank@entry=0x5647cd3455f0, kind=kind@entry=0 '\000', 
> > mode=mode@entry=1 '\001', ust=ust@entry=15726925190, crtc_msc=1)
> > at ../../../../present/present_vblank.c:37
> > #8  0x5647cc47844c in present_wnmd_flip_notify (crtc_msc= > out>, ust=15726925190, vblank=0x5647cd3455f0) at 
> > ../../../../present/present_wnmd.c:194
> > #9  present_wnmd_event_notify (window=, event_id= > out>, ust=15726925190, msc=) at 
> > ../../../../present/present_wnmd.c:228
> > #10 0x5647cc3ba2c7 in xwl_present_sync_callback (data=0x5647cd67f840, 
> > callback=, time=) at 
> > ../../../../../hw/xwayland/xwayland-present.c:282
> > #11 0x7f367aee0fce in ffi_call_unix64 () from 
> > /usr/lib/x86_64-linux-gnu/libffi.so.6
> > #12 0x7f367aee093f in ffi_call () from 
> > /usr/lib/x86_64-linux-gnu/libffi.so.6
> > #13 0x7f367c6e928d in wl_closure_invoke 
> > (closure=closure@entry=0x5647cd685990, flags=flags@entry=1, 
> > target=, target@entry=0x5647cd3456b0, opcode=opcode@entry=0, 
> > data=)
> > at ../src/connection.c:1006
> > #14 0x7f367c6e5ac9 in dispatch_event 
> > (display=display@entry=0x5647cccfc680, queue=) at 
> > ../src/wayland-client.c:1427
> > #15 0x7f367c6e6f94 in dispatch_queue (queue=0x5647cccfc748, 
> > display=0x5647cccfc680) at ../src/wayland-client.c:1573
> > #16 wl_display_dispatch_queue_pending (display=0x5647cccfc680, 
> > queue=0x5647cccfc748) at ../src/wayland-client.c:1815
> > #17 0x7f367c6e6fec in wl_display_dispatch_pending (display= > out>) at ../src/wayland-client.c:1878
> > #18 0x5647cc3afd2b in xwl_read_events (xwl_screen=0x5647cccf88c0) at 
> > ../../../../../hw/xwayland/xwayland.c:814
> > #19 0x5647cc510351 in ospoll_wait (ospoll=0x5647cccedf90, 
> > timeout=) at ../../../../os/ospoll.c:651
> > #20 0x5647cc5093d3 in WaitForSomething (are_ready=0) at 
> > ../../../../os/WaitFor.c:208
> > #21 0x5647cc4d97fc in Dispatch () at ../../../../include/list.h:220
> > #22 0x5647cc4dd9f6 in dix_main (argc=10, argv=0x7fff86573498, 
> > envp=) at ../../../../dix/main.c:276
> > #23 0x7f367b3deb17 in __libc_start_main (main=0x5647cc3af1b0 , 
> > argc=10, argv=0x7fff86573498, init=, fini=, 
> > rtld_fini=, stack_end=0x7fff86573488)
> > at ../csu/libc-start.c:310
> > 
> > I'm usually running emacs, firefox and pidgin at that time and often it
> > happens when I'm not using these applications at all. The wayland
> > compositor used is rootston contained in
> > https://packages.debian.org/experimental/libwlroots-examples
> 
> This should (according to upstream) the patch to fix it:
> 
> 
> https://cgit.freedesktop.org/xorg/xserver/commit/present/present_wnmd.c?id=ce271535adb6974e0a43bb64c8ed7a5dcaff67a2
> 
> I don't have the available bandwidth to rebuild xorg here atm though.

Got enough bandwidth to build: no crashes since rebuiding and running 1.20.1-5 
with
this patch applied.
Cheers,
 -- Guido

Bug#911146: xwayland spurious crashes

[Guido Günther]

control: -1 tags +patch

Hi,
On Tue, Oct 16, 2018 at 01:26:41PM +0200, Guido Günther wrote:
> Package: xwayland
> Version: 2:1.20.1-5
> Severity: normal
> 
> Hi,
> since a couple of days I'm seeing spurious xwayland crashes like
> 
> Core was generated by `Xwayland :0 -rootless -terminate -listen 12 -listen 13 
> -wm 53'.
> Program terminated with signal SIGABRT, Aborted.
> #0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
> #1  0x7f367b3f32f1 in __GI_abort () at abort.c:79
> #2  0x5647cc51258a in OsAbort () at ../../../../os/utils.c:1350
> #3  0x5647cc518093 in AbortServer () at ../../../../os/log.c:877
> #4  0x5647cc518ef9 in FatalError (f=f@entry=0x5647cc53c050 "Caught signal 
> %d (%s). Server aborting\n") at ../../../../os/log.c:1015
> #5  0x5647cc50f9a1 in OsSigHandler (signo=11, sip=, 
> unused=) at ../../../../os/osinit.c:156
> #6  
> #7  0x5647cc476c3e in present_vblank_notify 
> (vblank=vblank@entry=0x5647cd3455f0, kind=kind@entry=0 '\000', 
> mode=mode@entry=1 '\001', ust=ust@entry=15726925190, crtc_msc=1)
> at ../../../../present/present_vblank.c:37
> #8  0x5647cc47844c in present_wnmd_flip_notify (crtc_msc=, 
> ust=15726925190, vblank=0x5647cd3455f0) at 
> ../../../../present/present_wnmd.c:194
> #9  present_wnmd_event_notify (window=, event_id= out>, ust=15726925190, msc=) at 
> ../../../../present/present_wnmd.c:228
> #10 0x5647cc3ba2c7 in xwl_present_sync_callback (data=0x5647cd67f840, 
> callback=, time=) at 
> ../../../../../hw/xwayland/xwayland-present.c:282
> #11 0x7f367aee0fce in ffi_call_unix64 () from 
> /usr/lib/x86_64-linux-gnu/libffi.so.6
> #12 0x7f367aee093f in ffi_call () from 
> /usr/lib/x86_64-linux-gnu/libffi.so.6
> #13 0x7f367c6e928d in wl_closure_invoke 
> (closure=closure@entry=0x5647cd685990, flags=flags@entry=1, target= out>, target@entry=0x5647cd3456b0, opcode=opcode@entry=0, data= out>)
> at ../src/connection.c:1006
> #14 0x7f367c6e5ac9 in dispatch_event 
> (display=display@entry=0x5647cccfc680, queue=) at 
> ../src/wayland-client.c:1427
> #15 0x7f367c6e6f94 in dispatch_queue (queue=0x5647cccfc748, 
> display=0x5647cccfc680) at ../src/wayland-client.c:1573
> #16 wl_display_dispatch_queue_pending (display=0x5647cccfc680, 
> queue=0x5647cccfc748) at ../src/wayland-client.c:1815
> #17 0x7f367c6e6fec in wl_display_dispatch_pending (display= out>) at ../src/wayland-client.c:1878
> #18 0x5647cc3afd2b in xwl_read_events (xwl_screen=0x5647cccf88c0) at 
> ../../../../../hw/xwayland/xwayland.c:814
> #19 0x5647cc510351 in ospoll_wait (ospoll=0x5647cccedf90, 
> timeout=) at ../../../../os/ospoll.c:651
> #20 0x5647cc5093d3 in WaitForSomething (are_ready=0) at 
> ../../../../os/WaitFor.c:208
> #21 0x5647cc4d97fc in Dispatch () at ../../../../include/list.h:220
> #22 0x5647cc4dd9f6 in dix_main (argc=10, argv=0x7fff86573498, 
> envp=) at ../../../../dix/main.c:276
> #23 0x7f367b3deb17 in __libc_start_main (main=0x5647cc3af1b0 , 
> argc=10, argv=0x7fff86573498, init=, fini=, 
> rtld_fini=, stack_end=0x7fff86573488)
> at ../csu/libc-start.c:310
> 
> I'm usually running emacs, firefox and pidgin at that time and often it
> happens when I'm not using these applications at all. The wayland
> compositor used is rootston contained in
> https://packages.debian.org/experimental/libwlroots-examples

This should (according to upstream) the patch to fix it:


https://cgit.freedesktop.org/xorg/xserver/commit/present/present_wnmd.c?id=ce271535adb6974e0a43bb64c8ed7a5dcaff67a2

I don't have the available bandwidth to rebuild xorg here atm though.

Cheers,
 -- Guido

Bug#911146: xwayland spurious crashes

[Guido Günther]

Package: xwayland
Version: 2:1.20.1-5
Severity: normal

Hi,
since a couple of days I'm seeing spurious xwayland crashes like

Core was generated by `Xwayland :0 -rootless -terminate -listen 12 -listen 13 
-wm 53'.
Program terminated with signal SIGABRT, Aborted.
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#1  0x7f367b3f32f1 in __GI_abort () at abort.c:79
#2  0x5647cc51258a in OsAbort () at ../../../../os/utils.c:1350
#3  0x5647cc518093 in AbortServer () at ../../../../os/log.c:877
#4  0x5647cc518ef9 in FatalError (f=f@entry=0x5647cc53c050 "Caught signal 
%d (%s). Server aborting\n") at ../../../../os/log.c:1015
#5  0x5647cc50f9a1 in OsSigHandler (signo=11, sip=, 
unused=) at ../../../../os/osinit.c:156
#6  
#7  0x5647cc476c3e in present_vblank_notify 
(vblank=vblank@entry=0x5647cd3455f0, kind=kind@entry=0 '\000', 
mode=mode@entry=1 '\001', ust=ust@entry=15726925190, crtc_msc=1)
at ../../../../present/present_vblank.c:37
#8  0x5647cc47844c in present_wnmd_flip_notify (crtc_msc=, 
ust=15726925190, vblank=0x5647cd3455f0) at 
../../../../present/present_wnmd.c:194
#9  present_wnmd_event_notify (window=, event_id=, ust=15726925190, msc=) at 
../../../../present/present_wnmd.c:228
#10 0x5647cc3ba2c7 in xwl_present_sync_callback (data=0x5647cd67f840, 
callback=, time=) at 
../../../../../hw/xwayland/xwayland-present.c:282
#11 0x7f367aee0fce in ffi_call_unix64 () from 
/usr/lib/x86_64-linux-gnu/libffi.so.6
#12 0x7f367aee093f in ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
#13 0x7f367c6e928d in wl_closure_invoke 
(closure=closure@entry=0x5647cd685990, flags=flags@entry=1, target=, target@entry=0x5647cd3456b0, opcode=opcode@entry=0, data=)
at ../src/connection.c:1006
#14 0x7f367c6e5ac9 in dispatch_event (display=display@entry=0x5647cccfc680, 
queue=) at ../src/wayland-client.c:1427
#15 0x7f367c6e6f94 in dispatch_queue (queue=0x5647cccfc748, 
display=0x5647cccfc680) at ../src/wayland-client.c:1573
#16 wl_display_dispatch_queue_pending (display=0x5647cccfc680, 
queue=0x5647cccfc748) at ../src/wayland-client.c:1815
#17 0x7f367c6e6fec in wl_display_dispatch_pending (display=) 
at ../src/wayland-client.c:1878
#18 0x5647cc3afd2b in xwl_read_events (xwl_screen=0x5647cccf88c0) at 
../../../../../hw/xwayland/xwayland.c:814
#19 0x5647cc510351 in ospoll_wait (ospoll=0x5647cccedf90, 
timeout=) at ../../../../os/ospoll.c:651
#20 0x5647cc5093d3 in WaitForSomething (are_ready=0) at 
../../../../os/WaitFor.c:208
#21 0x5647cc4d97fc in Dispatch () at ../../../../include/list.h:220
#22 0x5647cc4dd9f6 in dix_main (argc=10, argv=0x7fff86573498, 
envp=) at ../../../../dix/main.c:276
#23 0x7f367b3deb17 in __libc_start_main (main=0x5647cc3af1b0 , 
argc=10, argv=0x7fff86573498, init=, fini=, 
rtld_fini=, stack_end=0x7fff86573488)
at ../csu/libc-start.c:310

I'm usually running emacs, firefox and pidgin at that time and often it
happens when I'm not using these applications at all. The wayland
compositor used is rootston contained in
https://packages.debian.org/experimental/libwlroots-examples

I'd be thankful for any pointers to track that down.

Cheers,
 -- Guido

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'stable'), 
(1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 4.18.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages xwayland depends on:
ii  libaudit1   1:2.8.4-2
ii  libbsd0 0.9.1-1
ii  libc6   2.27-6
ii  libdrm2 2.4.94-1
ii  libegl1 1.1.0-1
ii  libepoxy0   1.5.2-0.3
ii  libgbm1 18.1.7-1
ii  libgcrypt20 1.8.3-1
ii  libgl1  1.1.0-1
ii  libpixman-1-0   0.34.0-2
ii  libselinux1 2.8-1+b1
ii  libsystemd0 239-10
ii  libunwind8  1.2.1-8
ii  libwayland-client0  1.16.0-1
ii  libxau6 1:1.0.8-1+b2
ii  libxdmcp6   1:1.1.2-3
ii  libxfont2   1:2.0.3-1
ii  libxshmfence1   1.3-1
ii  xserver-common  2:1.20.1-5

xwayland recommends no packages.

xwayland suggests no packages.

-- no debconf information

Bug#907136: Please consider enabling etnaviv on arm64 after 18.2.0

[Guido Günther]

Source: mesa
Version: 26
Severity: wishlist
Version: 

Hi,
with etnaviv kernel driver and libdrm shaping up on arm64 it would be
great to have this enabled as well. Not all patches for GC7000 (imx8)
are mainline yet:

https://github.com/laanwj/mesa/tree/gc7000

but most of them are and it would be nice to have this enabled for early
experiments.

Cheers,
 -- Guido


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'stable'), 
(1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#906915: Please enable etnaviv on arm64

[Guido Günther]

control: tag -1 +patch

On Wed, Aug 22, 2018 at 10:18:53AM +0200, Guido Günther wrote:
> MR forthcoming.

https://salsa.debian.org/xorg-team/lib/libdrm/merge_requests/1/diffs

I've also attached it to the bts since it's hard to tell if a project
prefers MRs over patches.

The mesa bits for etnaviv aren't in place yet and there will likely also
be kernel changes but shipping the drm module to make this easier to use
would already be great.

Cheers,
 -- Guido
>From 7a5df1682428a7cbfb52c2b4334539c488945fcf Mon Sep 17 00:00:00 2001
Message-Id: <7a5df1682428a7cbfb52c2b4334539c488945fcf.1534926381.git@sigxcpu.org>
From: =?UTF-8?q?Guido=20G=C3=BCnther?= 
Date: Mon, 13 Aug 2018 09:51:05 +
Subject: [PATCH] Enable etnaviv on arm64

There are 64 bit CPUs supporting etnaviv like the i.MX8.

Closes: #906915
---
 debian/changelog | 6 ++
 debian/control   | 4 ++--
 debian/rules | 4 ++--
 3 files changed, 10 insertions(+), 4 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index e12943c6..01c8e14b 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+libdrm (2.4.93-2) UNRELEASED; urgency=medium
+
+  * Enable etnaviv on arm64 (Closes: #906915)
+
+ -- Guido Günther   Wed, 22 Aug 2018 10:18:09 +0200
+
 libdrm (2.4.93-1) unstable; urgency=medium
 
   * New upstream release.
diff --git a/debian/control b/debian/control
index 24342cc5..f8c57ca9 100644
--- a/debian/control
+++ b/debian/control
@@ -33,7 +33,7 @@ Depends:
  libdrm-freedreno1 (= ${binary:Version}) [any-arm arm64],
  libdrm-exynos1 (= ${binary:Version}) [any-arm],
  libdrm-tegra0 (= ${binary:Version}) [any-arm arm64],
- libdrm-etnaviv1 (= ${binary:Version}) [armhf],
+ libdrm-etnaviv1 (= ${binary:Version}) [armhf arm64],
  ${misc:Depends},
 Multi-Arch: same
 Description: Userspace interface to kernel DRM services -- development files
@@ -199,7 +199,7 @@ Description: Userspace interface to amdgpu-specific kernel DRM services -- runti
  OpenGL drivers.
 
 Package: libdrm-etnaviv1
-Architecture: armhf
+Architecture: armhf arm64
 Depends:
  ${shlibs:Depends},
  ${misc:Depends},
diff --git a/debian/rules b/debian/rules
index 5d3b2594..e01cfa47 100755
--- a/debian/rules
+++ b/debian/rules
@@ -55,8 +55,8 @@ else
 	confflags += --disable-omap-experimental-api
 endif
 
-# Etnaviv is on armhf
-ifneq (,$(filter armhf,$(DEB_HOST_ARCH)))
+# Etnaviv is on armhf and arm64
+ifneq (,$(filter armhf arm64,$(DEB_HOST_ARCH)))
 	ETNAVIV = yes
 endif
 ifeq ($(ETNAVIV), yes)
-- 
2.18.0

Bug#906915: Please enable etnaviv on arm64

[Guido Günther]

Source: libdrm
Version: 2.4.93-1
Severity: wishlist

With etnaviv support coming into shape on arm64 it would be great to
have this enabled in Debian as well.

MR forthcoming.

Cheers,
 -- Guido

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'stable'), 
(1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#898988: New upstream version 1.14

[Guido Günther]

Package: wayland-protocols
Version: 1.13-1
Severity: wishlist

Hi,
there's a new upstream version 1.14 out:

  https://github.com/wayland-project/wayland-protocols/releases/tag/1.14

An update would be great since it's required by newer wlroots.
Cheers,
 -- Guido

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-updates'), (500, 'oldoldstable'), (500, 
'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 4.16.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- no debconf information

Bug#890795: New upstream versions 1.12 and 1.13

[Guido Günther]

Package: wayland-protocols
Version: 1.11-1
Severity: wishlist

Hi,
version 1.12 was tagged in december

  https://cgit.freedesktop.org/wayland/wayland-protocols/tag/?h=1.12

and 1.13 just recently. Let me know if I can help e.g. by a NMU to
experimental.
Cheers,
 -- Guido


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-updates'), (500, 'oldoldstable'), (500, 
'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- no debconf information

Re: Bug#888313: please allow git remote configuration (e.g. for upstream remote)

[Guido Günther]

Hi,
Thanks for having a look.

On Tue, Feb 13, 2018 at 09:59:02AM +0100, Michael Stapelberg wrote:
> See the attached work-in-progress patch for how far I got at this point.
> Before I continue, here are two questions:
> 
> AFAICT, the control package doesn’t allow me to do case-insensitive
> lookups. Should we extend it to do that, or do we really want to insist on
> users capitalizing the directives correctly?

Policy says:

| Field names are not case-sensitive, but it is usual to capitalize the
| field names using mixed case as shown below. Field values are case-
| sensitive unless the description of the field says otherwise.

so we should capitalize them. We can likely do with a single control
file entry like:

X-Vcs-Upstream-Git:  -b 

which would match the existing Vcs-* syntax.

> Also, I’m wondering whether we should set up a branch automatically (e.g.
> “upstream” tracking “upstream/master”), not at all, or behind another
> option. This ties into our branch naming and import workflow discussion.
> Thoughts?

I would start out with naming the remote 'upstream'. I'm not sure
whether we need tracking branches. When I track remote git I usually
don't track upstream but rather only fetch from the remote. Different
people might have different expectations here so we likely need to come
up with an option to configure this.

Cheers,
 -- Guido

Re: Bug#888313: please allow git remote configuration (e.g. for upstream remote)

[Guido Günther]

On Sun, Feb 11, 2018 at 02:20:55PM +0100, Michael Stapelberg wrote:
> Given that it has been two weeks, I don’t think we’re going to get a reply
> from debian-x :)

Agreed.

> 
> I’d suggest to just go ahead — I can’t see why the suggested approach
> wouldn’t work for debian-x, and even if they need something on top, it’d be
> easy to add that later.
> 
> Guido, how do we proceed? Do you want to take care of this, or would you
> rely on an external patch for this feature?
> Thanks!

A patch (including tests and docs) would be welcome since my time to
work in gbp is currently quiet limited and I have some other bugs I
need to look at first.

Cheers,
 -- Guido

Bug#886919: Please enable system notify support

[Guido Günther]

Hi,
On Sat, Jan 13, 2018 at 01:36:06PM +0100, Julien Cristau wrote:
> On Thu, Jan 11, 2018 at 11:12:49 +0100, Guido Günther wrote:
> 
> > Package: weston
> > Version: 3.0.0-1
> > Severity: wishlist
> > Tags: patch
> > 
> > Hi,
> > possible patch attached.
> 
> You may want to explain more.  What are the benefits, costs, risks,
> anything else?

It's can be used when starting weston as a systemd unit. 

 - notify systemd about startup via sd_notify (READY=1)
 - notify systemd that it's still alive via WATCHDOG=1
 - notify systemd about shutdow using STOPPING=1

An example unit file is being prepared upsteam:


https://lists.freedesktop.org/archives/wayland-devel/2017-November/035973.html

Since we already link against libsystemd no new dependencies are
introduced and the module needs to be loaded explicitly so no risk for
running installations.
Cheers,
 -- Guido

Bug#886919: Please enable system notify support

[Guido Günther]

Package: weston
Version: 3.0.0-1
Severity: wishlist
Tags: patch

Hi,
possible patch attached.
Cheers,
 -- Guido


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-updates'), (500, 'oldoldstable'), (500, 
'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages weston depends on:
ii  adduser 3.116
ii  libc6   2.25-5
ii  libcairo2   1.15.8-3
ii  libcolord2  1.3.3-2
ii  libdrm2 2.4.89-1
ii  libegl1 1.0.0-1
ii  libegl1-mesa17.2.5-1
ii  libgles21.0.0-1
ii  libglib2.0-02.54.2-5
ii  libinput10  1.9.4-2
ii  libjpeg62-turbo 1:1.5.2-2+b1
ii  liblcms2-2  2.9-1
ii  libpam0g1.1.8-3.6
ii  libpango-1.0-0  1.40.14-1
ii  libpangocairo-1.0-0 1.40.14-1
ii  libpixman-1-0   0.34.0-2
ii  libpng16-16 1.6.34-1
ii  libsystemd0 236-2
ii  libwayland-client0  1.14.0-1+b1
ii  libwayland-cursor0  1.14.0-1+b1
ii  libwayland-egl1-mesa [libwayland-egl1]  17.2.5-1
ii  libwayland-server0  1.14.0-1+b1
ii  libweston-3-0   3.0.0-1
ii  libxkbcommon0   0.7.1-2
ii  zlib1g  1:1.2.8.dfsg-5

Versions of packages weston recommends:
ii  libgl1-mesa-dri  17.2.5-1

weston suggests no packages.

-- no debconf information
>From 7b58684c5a6a716c4528117964883c9d08030a07 Mon Sep 17 00:00:00 2001
Message-Id: <7b58684c5a6a716c4528117964883c9d08030a07.1515665438.git@sigxcpu.org>
From: =?UTF-8?q?Guido=20G=C3=BCnther?= 
Date: Thu, 11 Jan 2018 09:59:32 +0100
Subject: [PATCH] Enable systemd notify support

---
 debian/rules  | 2 +-
 debian/weston.install | 1 +
 2 files changed, 2 insertions(+), 1 deletion(-)

diff --git a/debian/rules b/debian/rules
index 73dd73d..8c24b2a 100755
--- a/debian/rules
+++ b/debian/rules
@@ -2,7 +2,7 @@
 
 override_dh_auto_configure:
 	dh_auto_configure -- --disable-libunwind --libexec=/usr/lib/weston \
-		--with-cairo=image --enable-screen-sharing
+		--with-cairo=image --enable-screen-sharing --enable-systemd-notify
 
 override_dh_auto_test:
 	# the test suite does not 100% pass in headless mode
diff --git a/debian/weston.install b/debian/weston.install
index 7c6faa3..00e335c 100644
--- a/debian/weston.install
+++ b/debian/weston.install
@@ -17,6 +17,7 @@ usr/lib/*/weston/fullscreen-shell.so
 usr/lib/*/weston/hmi-controller.so
 usr/lib/*/weston/ivi-shell.so
 usr/lib/*/weston/screen-share.so
+usr/lib/*/weston/systemd-notify.so
 usr/share/man/man1/weston.1
 usr/share/man/man5/weston.ini.5
 usr/share/man/man7/weston-drm.7
-- 
2.15.1

Bug#586693: Improve resolution for QEMU

[Guido Günther]

Hi,
On Mon, Jun 21, 2010 at 07:59:28PM +0200, Guido Günther wrote:
 Package: xserver-xorg-video-cirrus
 Severity: wishlist
 Tags: +patch
 
 Hi,
 Fedora has this nice path to allow QEMU to use 1024x800 for virtual
 machines:
 
 http://cvs.fedoraproject.org/viewvc/rpms/xorg-x11-drv-cirrus/F-13/cirrus-1.2.0-qemu.patch?revision=1.2view=co
 
 This makes kvm/qemu much more useful for desktop virtualization so it'd
 be nice to have this in squeeze. Since it checks for the subvendor_id it
 has little potential of breaking anything else. Please apply and let me
 know if I should NMU.
Any chance we get this fixed for Squeeze? It would make Debian a much
more usable graphical guest in KVM/Qemu. I'd be happy to NMU.
Cheers,
 -- Guido



--
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/20100906112239.ga23...@bogon.sigxcpu.org

Bug#586693: Improve resolution for QEMU

[Guido Günther]

On Mon, Sep 06, 2010 at 01:50:24PM +0200, Julien Cristau wrote:
 On Mon, Sep  6, 2010 at 13:22:39 +0200, Guido Günther wrote:
 
  Hi,
  On Mon, Jun 21, 2010 at 07:59:28PM +0200, Guido Günther wrote:
   Package: xserver-xorg-video-cirrus
   Severity: wishlist
   Tags: +patch
   
   Hi,
   Fedora has this nice path to allow QEMU to use 1024x800 for virtual
   machines:
   
   http://cvs.fedoraproject.org/viewvc/rpms/xorg-x11-drv-cirrus/F-13/cirrus-1.2.0-qemu.patch?revision=1.2view=co
   
   This makes kvm/qemu much more useful for desktop virtualization so it'd
   be nice to have this in squeeze. Since it checks for the subvendor_id it
   has little potential of breaking anything else. Please apply and let me
   know if I should NMU.
  Any chance we get this fixed for Squeeze? It would make Debian a much
  more usable graphical guest in KVM/Qemu. I'd be happy to NMU.
 
 The above URL is a 404 (I suppose because fedora moved to git).
Attached now a version for 1.3.2.
Cheers,
 -- Guido
diff -up xf86-video-cirrus-1.2.0/src/alp_driver.c.jx xf86-video-cirrus-1.2.0/src/alp_driver.c
--- xf86-video-cirrus-1.2.0/src/alp_driver.c.jx	2008-03-19 10:29:23.0 -0400
+++ xf86-video-cirrus-1.2.0/src/alp_driver.c	2009-02-27 10:59:27.0 -0500
@@ -812,6 +812,20 @@ AlpPreInit(ScrnInfoPtr pScrn, int flags)
  else
  	xf86SetDDCproperties(pScrn,xf86PrintEDID(
  	xf86DoEDID_DDC2(pScrn-scrnIndex,pCir-I2CPtr1)));
+#ifdef XSERVER_LIBPCIACCESS
+ if (!pScrn-monitor-DDC 
+	 ((pCir-PciInfo-subvendor_id  0x) == 0x1af4)) {
+	xf86DrvMsg(pScrn-scrnIndex, X_INFO,
+		   Defaulting to 1024x768 for QEMU\n);
+	pScrn-monitor-nHsync = 1;
+	pScrn-monitor-hsync[0].lo = 31.5;
+	pScrn-monitor-hsync[0].hi = 48.0;
+	pScrn-monitor-nVrefresh = 1;
+	pScrn-monitor-vrefresh[0].lo = 56.0;
+	pScrn-monitor-vrefresh[0].hi = 60.1;
+	pScrn-monitor-maxPixClock = 65000;
+ }
+#endif
  
  /* Probe the possible LCD display */
  AlpProbeLCD(pScrn);

Bug#586693: Improve resolution for QEMU

[Guido Günther]

On Mon, Sep 06, 2010 at 03:33:25PM +0200, Julien Cristau wrote:
 On Mon, Sep  6, 2010 at 15:25:33 +0200, Guido Günther wrote:
 
  Attached now a version for 1.3.2.
 
 That's a pretty ugly hack...
Yes indeed but without it you're only at 800x600 which makes qemu/kvm
pretty much unusable for desktop virtualization. Fedora is carrying it
since ages.
Cheers,
 -- Guido



--
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/20100906133504.ga19...@bogon.sigxcpu.org

Bug#586693: Improve resolution for QEMU

[Guido Günther]

Package: xserver-xorg-video-cirrus
Severity: wishlist
Tags: +patch

Hi,
Fedora has this nice path to allow QEMU to use 1024x800 for virtual
machines:

http://cvs.fedoraproject.org/viewvc/rpms/xorg-x11-drv-cirrus/F-13/cirrus-1.2.0-qemu.patch?revision=1.2view=co

This makes kvm/qemu much more useful for desktop virtualization so it'd
be nice to have this in squeeze. Since it checks for the subvendor_id it
has little potential of breaking anything else. Please apply and let me
know if I should NMU.
Cheers,
 -- Guido


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

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

Versions of packages xserver-xorg-video-cirrus depends on:
ii  libc6 2.11.2-1   Embedded GNU C Library: Shared lib
ii  xserver-xorg-core 2:1.7.7-2  Xorg X server - core server

xserver-xorg-video-cirrus recommends no packages.

xserver-xorg-video-cirrus suggests no packages.



-- 
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/20100621175928.ga32...@bogon.sigxcpu.org

Bug#494321: [xserver-xorg-video-intel] Error in I830WaitLpRing(), timeout for 2 seconds - reboot needed

[Guido Günther]

On Sat, Jun 13, 2009 at 08:36:24AM +0200, Brice Goglin wrote:
 On Fri, Aug 08, 2008 at 04:23:20PM +0200, Guido Guenther wrote:
  Package: xserver-xorg-video-intel
  Version: 2:2.3.2-2
  Severity: serious
  
  X crashed with the attached output in Xorg.0.log when minimizing a
  Window with Compiz. Afterwards the monitor kind of blinked until I
  stopped gdm. Restarting gdm brought the blinking back but no solid
  picture. I had to reboot. Not nice for a upcoming stable release. (I
  didn't try to unload/reload the kernel module). Kernel is
  linux-image-2.6.25-2-686 in case that matters for the drm module.
 
 Does this still happen with latest intel driver in unstable or 
 experimental?
Unfortunately I can't easily check right now since this is not my system
and it's running stable. I'll recheck once upgraded.
 -- Guido



-- 
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#507898: typo in VCS-Browser fiels

[Guido Günther]

Package: drm-snapshot
Severity: minor

Hi,
while adding support for the way you specify commit ids in the changelog
to https://honk.sigxcpu.org/cl2vcs/ in noticed there's a typo in the
VCS-Browser field:

- Vcs-Browser: http://git.debian.org/?=pkg-xorg/lib/drm-snapshot.git
+ Vcs-Browser: http://git.debian.org/?p=pkg-xorg/lib/drm-snapshot.git
  ^
Cheers,
 -- Guido



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#494321: [xserver-xorg-video-intel] Error in I830WaitLpRing(), timeout for 2 seconds - reboot needed

[Guido Günther]

On Fri, Aug 08, 2008 at 05:25:06PM +0200, Brice Goglin wrote:
 Switching to XAA is usually a good workaround for this kind of problem.
 Option AccelMethod XAA
 in the Device section.
Since this also helps with the ugly scrolling in firefox3 (which I
checked actually helps a lot):
 http://ubuntuforums.org/showthread.php?t=708928page=2
should we make this the default for lenny?

 I am downgrading severity to important to match many other Xorg
 crash/lockup reports.
I'd fully agree here with the XAA workaround in place. It's a little bit
strange to mark these things only as important otherwise - what would be
grave then? Anyway, it's your call.
Cheers,
 -- Guido



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#494321: [xserver-xorg-video-intel] Error in I830WaitLpRing(), timeout for 2 seconds - reboot needed

[Guido Günther]

On Fri, Aug 08, 2008 at 04:37:25PM +0200, Julien Cristau wrote:
 On Fri, Aug  8, 2008 at 16:23:20 +0200, Guido Guenther wrote:
 
  Not nice for a upcoming stable release.
 
 You're welcome to send a patch.
I'd love to, if you point me in the right direction. This was not meant
as criticism on your maintainership - I just wanted to point out that
there are worrysome issues in the driver. Let me know if I can be of any
help to debug this.
Cheers,
 -- Guido



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]