Bug#900573: qreator: Proposed patch to fix the crash

2019-03-30 Thread Andreas Boll 
On Thu, Mar 28, 2019 at 10:22:31PM +0800, Chow Loong Jin wrote:
> On Wed, Mar 27, 2019 at 10:31:35PM +0100, Andreas Boll wrote:
> > Control: severity -1 serious
> > Control: tags -1 + patch
> > 
> > Dear maintainer,
> > 
> > I've prepared a patch to fix this issue.
> > Also currently the package qreator isn't useful at all with this issue
> > because it crashes on startup. Thus bumping severity to serious
> > because this package shouldn't end up in Debian Buster without a fix
> > for this issue.
> > 
> > Please let me know if I should upload this fix as NMU or if you like
> > to upload it yourself.
> 
> Please go ahead and upload this fix. Thanks.
> 
> -- 
> Kind regards,
> Loong Jin

Cool, I've uploaded it to sid now.
Attached is the nmudiff.

Thanks,
Andreas
diff -Nru qreator-16.06.1/debian/changelog qreator-16.06.1/debian/changelog
--- qreator-16.06.1/debian/changelog	2018-04-14 14:48:31.0 +0200
+++ qreator-16.06.1/debian/changelog	2019-03-30 20:35:12.0 +0100
@@ -1,3 +1,11 @@
+qreator (16.06.1-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add Fix-python-pil-imports.patch, fixes a program crash due to
+incorrect PIL imports (Closes: #900573).
+
+ -- Andreas Boll   Sat, 30 Mar 2019 20:35:12 +0100
+
 qreator (16.06.1-3) unstable; urgency=medium
 
   * [207e2e1] Port qreator to libnm (Closes: #857227)
diff -Nru qreator-16.06.1/debian/patches/Fix-python-pil-imports.patch qreator-16.06.1/debian/patches/Fix-python-pil-imports.patch
--- qreator-16.06.1/debian/patches/Fix-python-pil-imports.patch	1970-01-01 01:00:00.0 +0100
+++ qreator-16.06.1/debian/patches/Fix-python-pil-imports.patch	2019-03-27 21:45:38.0 +0100
@@ -0,0 +1,22 @@
+Author: Andreas Boll 
+Date:   Wed Mar 27 21:09:41 2019 +0100
+
+Fix python-pil imports
+
+Fixes bug #900573
+
+diff --git a/qreator/QRCode.py b/qreator/QRCode.py
+index d3a0130..930a538 100644
+--- a/qreator/QRCode.py
 b/qreator/QRCode.py
+@@ -20,8 +20,8 @@ try:
+ except ImportError:
+ print "You need to install the python-qrencode package"
+ sys.exit(1)
+-import Image
+-import ImageOps
++from PIL import Image
++from PIL import ImageOps
+ import cairo
+ import array
+
diff -Nru qreator-16.06.1/debian/patches/series qreator-16.06.1/debian/patches/series
--- qreator-16.06.1/debian/patches/series	2018-04-14 14:48:31.0 +0200
+++ qreator-16.06.1/debian/patches/series	2019-03-27 21:45:54.0 +0100
@@ -3,3 +3,4 @@
 Port-to-geoclue-2.0.patch
 Port-to-libnm.patch
 Fix-IndexError-when-a-wifi-network-has-100-strength.patch
+Fix-python-pil-imports.patch


signature.asc
Description: PGP signature

Bug#914267: mesa: [regression] with Mesa 18.2.5-2 the charackter model in Tomb Raider is no longer rendered.

2018-11-22 Thread Andreas Boll 
Control: tag -1 pending

On Thu, Nov 22, 2018 at 05:15:17PM +0100, Michael Biebl wrote:
> Control: severity -1 serious
> 
> Hi mesa maintainers,
> 
> after further contemplating about this, I think this bug is ugly enough
> and hard to diagnose for our users, that the package should not enter
> testing in this state.
> I'm thus raising the severity to RC which will prevent testing migration
> and also make the bug more visible to users.
> 
> Regards,
> Michael

Thank you all for reporting and tracking down this issue!
I'll upload Michael's workaround asap.

Thanks,
Andreas

Bug#904995: xserver-common: black screen with mouse on screen rotate.

2018-08-18 Thread Andreas Boll 
On Thu, Aug 16, 2018 at 10:49:33AM +0200, Michel Dänzer wrote:
> On 2018-08-16 10:27 AM, Simon Polack wrote:
> > The issue seems to be not limited to ATI/AMD graphics, as i face it on
> > intel aswell.
> 
> That's probably a separate bug in the modesetting driver, which might
> indeed be fixed in upstream xserver 1.20.1.

The issue in the modesetting driver has been fixed in xorg-server
2:1.20.1-1 and the issue in xserver-xorg-video-ati will be fixed asap.

Thanks,
Andreas

Bug#882592: Trackpad behaves erratic

2017-12-14 Thread Andreas Boll 
Severity: normal

On Sat, Nov 25, 2017 at 11:15:06AM +0100, Jörg-Volker Peetz wrote:
> Package: libinput10
> Version: 1.9.2-1
> 
> Dear Maintainer(s),
> 
> this is to confirm the regression this version introduces and to describe some
> problems.
> After update from version 1.8.3-1 (also update of libc6 from version 2.24-15)
> the mouse clicks from my Logitech K830 keyboard with built in touchpad
> (appearing like a PS/2 mouse) sometimes make problems.
> Double tapping to maximize a window in openbox doesn't work at all any more.
> Double tapping to select a word in text doesn't work, it needs three taps now.
> Sometimes, after using the emulated middle mouse button the left mouse button
> behaves like the middle button. To recover, I normally have to press the right
> mouse button.
> 
> Regards,
> jvp.
> 

Please report this upstream at
https://bugs.freedesktop.org/enter_bug.cgi?product=wayland=libinput
and let us know the bug number for tracking.

Thanks,
Andreas

Bug#874656: libegl1-mesa: Makes team fortress 2 crash the entire machine

2017-10-13 Thread Andreas Boll 
Control: severity -1 important

(Adding original bug reporter)

On Tue, Oct 03, 2017 at 06:32:25AM +0200, Antoine Le Gonidec wrote:
> On Thu, 28 Sep 2017 23:15:27 +0200 Salvo Tomaselli 
> wrote:
> > I had downgraded my mesa. I wanted to try again but I can't upgrade it
> > because of some llvm breakage at the moment.
> > (…)
> > I seguenti pacchetti hanno dipendenze non soddisfatte:
> > libllvm5.0 : Rompe: libllvm5.0:i386 (!= 1:5.0-2) but 1:5.0-1 is to be 
> > installed
> > libllvm5.0:i386 : Rompe: libllvm5.0 (!= 1:5.0-1) but 1:5.0-2 is installed
> 
> You can still install these packages without waiting for the resolution
> of bug #876752 by forcing the highest common version for these two
> architectures:
> apt install libllvm5.0{,:i386}=1:5.0~+rc2-1
> 
> You need to have the testing repositories in your APT sources or this
> won’t work.
> 

Hi Salvo,

could you try to use llvm from testing?
Does this issue affect other opengl apps (e.g. other (non-)steam games, amd64
games, ...) too?

In the meantime I'm lowering the severity to important to let Mesa
migrate to testing since it blocks lots of packages.

Thanks,
Andreas


signature.asc
Description: PGP signature

Bug#874715: mesa Games like Counter-Strike Global Offensive dont start after upgrading mesa to 17.2.0-2

2017-10-13 Thread Andreas Boll 
Control: severity -1 important

On Mon, Oct 02, 2017 at 09:00:59PM +0200, Dominik Kupschke wrote:
> Hi,
> 
> I was able to start some steam games without steam-runtime.
> Also non Steam Games work properly.
> 
> Regards
> Dominik

Hi,

so it looks like an issue with the steam-runtime. Please report this
issue to Valve on github and let us know the bug number/url for
tracking.

I'm lowering the severity to important to let Mesa migrate to testing
since it blocks lots of packages.

Thanks,
Andreas


signature.asc
Description: PGP signature

Bug#874715: mesa Games like Counter-Strike Global Offensive dont start after upgrading mesa to 17.2.0-2

2017-09-29 Thread Andreas Boll 
On Fri, Sep 29, 2017 at 07:21:42AM +0200, Dominik Kupschke wrote:
> Yes I am fine with changing the severity to important.
> 
> This issue affects all of my steam games (> 100), so the migration of the 
> packet to testing could be bad for a lot of people.
> 
> Regards
> Dominik

So does this issue affect only i386 games or steam games. Could you
try some non-steam i386 games/benchmarks and some amd64
games/benchmarks?

There's currently an issue with llvm not building on i386. Maybe
that's somehow related. Could you attach the list of installed llvm
packages?
dpkg -l | grep llvm

Thanks,
Andreas


signature.asc
Description: PGP signature

Bug#874656: libegl1-mesa: Makes team fortress 2 crash the entire machine

2017-09-28 Thread Andreas Boll 
On Sat, Sep 09, 2017 at 11:16:54PM +0300, Timo Aaltonen wrote:
> On 09.09.2017 02:31, Salvo Tomaselli wrote:
> > Well I had to downgrade to testing since it was making my machine crash.
> 
> Doesn't crash my KBL now that I tested it. Try an older kernel maybe.

Can you reproduce this issue with an older kernel (from snapshot.debian.org) or 
a newer kernel (from experimental)?

Thanks,
Andreas


signature.asc
Description: PGP signature

Bug#874715: mesa: Games like Counter-Strike Global Offensive dont start after upgrading mesa to 17.2.0-2

2017-09-28 Thread Andreas Boll 
(Adding original bug reporter)

Is this still an issue with mesa 17.2.1?
Could the following be related to your issue?

On Fri, Sep 15, 2017 at 08:01:54AM +0200, Gert Wollny wrote:
> Since you are using radeonsi you may have a conflict between the system
>  libstdc++ and the one shipped with the steam runtime (Although this
> usually meant Steam doesn't start at all). 
> 
> cf: https://github.com/ValveSoftware/steam-for-linux/issues/3273


Could you please attach the output from LIBGL_DEBUG=verbose glxinfo
and if possible replace mesa-utils:amd64 with mesa-utils:i386 and run
glxinfo again and attach its output too.

Thanks,
Andreas


signature.asc
Description: PGP signature

Bug#860749: mesa-va-drivers: Critical error in library 'mesa' with i965 video driver

2017-05-09 Thread Andreas Boll 
On Tue, May 09, 2017 at 03:00:34PM +0200, Andreas Boll wrote:
> The following looks like an issue with the kernel graphics driver:

Looks like a known upstream kernel issue:
https://bugs.freedesktop.org/show_bug.cgi?id=93782

Please try the workaround described in comment 40 [1] first, by adding

video=SVIDEO-1:d

to the kernel command line.

Thanks,
Andreas

[1] https://bugs.freedesktop.org/show_bug.cgi?id=93782#c40

> 
> > [   21.472066] [drm:drm_atomic_helper_commit_cleanup_done [drm_kms_helper]] 
> > *ERROR* [CRTC:26:pipe A] flip_done timed out
> > [   21.576017] [ cut here ]
> > [   21.576062] WARNING: CPU: 0 PID: 100 at 
> > /build/linux-9r9Ph5/linux-4.9.18/drivers/gpu/drm/drm_irq.c:1254 
> > drm_wait_one_vblank+0x197/0x1a0 [drm]
> > [   21.576200] vblank wait timed out on crtc 0
> > [   21.576201] Modules linked in: uvcvideo videobuf2_vmalloc arc4 
> > videobuf2_memops iwl3945 videobuf2_v4l2 iwlegacy videobuf2_core 
> > snd_hda_codec_si3054 mac80211 videodev media cfg80211 iTCO_wdt 
> > iTCO_vendor_support joydev evdev r592 memstick snd_hda_codec_realtek 
> > snd_hda_codec_generic rfkill snd_hda_intel pcspkr snd_hda_codec coretemp 
> > serio_raw snd_hda_core snd_hwdep lpc_ich mfd_core snd_pcm snd_timer sg i915 
> > shpchp drm_kms_helper ene_ir rc_core drm i2c_algo_bit battery ac snd 
> > soundcore video wmi button acpi_cpufreq tpm_tis tpm_tis_core tpm parport_pc 
> > ppdev lp parport ip_tables x_tables autofs4 ext4 crc16 jbd2 crc32c_generic 
> > fscrypto ecb glue_helper lrw gf128mul ablk_helper cryptd aes_x86_64 mbcache 
> > sr_mod cdrom sd_mod ata_generic psmouse i2c_i801 i2c_smbus ata_piix libata 
> > scsi_mod tg3 firewire_ohci sdhci_pci
> > [   21.576257]  sdhci mmc_core firewire_core crc_itu_t ptp pps_core libphy 
> > ehci_pci uhci_hcd ehci_hcd usbcore usb_common
> > [   21.576269] CPU: 0 PID: 100 Comm: kworker/u4:3 Not tainted 4.9.0-2-amd64 
> > #1 Debian 4.9.18-1
> > [   21.576270] Hardware name: - N/A 
> >/IFT01 , BIOS 1.18 06/18/2008
> > [   21.576276] Workqueue: events_unbound async_run_entry_fn
> > [   21.576278]   b4928714 a5e440917a60 
> > 
> > [   21.576281]  b4676e9e 9898383c a5e440917ab8 
> > 
> > [   21.576283]  0101 98983a6edc08 9898383f8800 
> > b4676f1f
> > [   21.576286] Call Trace:
> > [   21.576293]  [] ? dump_stack+0x5c/0x78
> > [   21.576296]  [] ? __warn+0xbe/0xe0
> > [   21.576298]  [] ? warn_slowpath_fmt+0x5f/0x80
> > [   21.576301]  [] ? finish_wait+0x3c/0x70
> > [   21.576315]  [] ? drm_wait_one_vblank+0x197/0x1a0 [drm]
> > [   21.576317]  [] ? prepare_to_wait_event+0xf0/0xf0
> > [   21.576389]  [] ? 
> > intel_get_load_detect_pipe+0x624/0x640 [i915]
> > [   21.576425]  [] ? intel_tv_detect+0x155/0x550 [i915]
> > [   21.576440]  [] ? 
> > drm_property_replace_global_blob+0xd8/0x120 [drm]
> > [   21.576458]  [] ? 
> > drm_helper_probe_single_connector_modes+0x3f6/0x4e0 [drm_kms_helper]
> > [   21.576465]  [] ? 
> > drm_fb_helper_initial_config+0xac/0x440 [drm_kms_helper]
> > [   21.576500]  [] ? intel_fbdev_initial_config+0x14/0x30 
> > [i915]
> > [   21.576502]  [] ? async_run_entry_fn+0x34/0x140
> > [   21.576504]  [] ? process_one_work+0x184/0x410
> > [   21.576506]  [] ? worker_thread+0x4d/0x480
> > [   21.576508]  [] ? process_one_work+0x410/0x410
> > [   21.576510]  [] ? kthread+0xce/0xf0
> > [   21.576512]  [] ? __switch_to+0x2c1/0x6c0
> > [   21.576514]  [] ? kthread_park+0x60/0x60
> > [   21.576517]  [] ? ret_from_fork+0x25/0x30
> > [   21.576519] ---[ end trace 872a41b26fe6df4f ]---



signature.asc
Description: Digital signature

Bug#860749: mesa-va-drivers: Critical error in library 'mesa' with i965 video driver

2017-05-09 Thread Andreas Boll 
Hi,

On Wed, Apr 19, 2017 at 03:00:46PM -0300, Carlos Donizete Froes wrote:
> Package: mesa-va-drivers
> Version: 13.0.6-1
> Severity: critical
> Tags: lfs
> Justification: breaks the whole system
> 
> Dear Maintainer,
> 
>* What led up to the situation?
>- After installing Debian Stretch RC-3 in notebook, it does not open the
> graphical environment (gnome, kde, xfce, mate).
> 
>* What exactly did you do (or not do) that was effective (or ineffective)?
>- I accessed the GRUB recovery mode, where was able to open the graphical
> environment, but it was extremely slow.
>- But when you start in normal mode, the system freezes on the dark screen.
> 
>* What was the outcome of this action?
>- I did a search and found on the site official:
> https://www.mesa3d.org/relnotes/17.0.4.html
>- For 'nouveau' and 'i965' is very important when have several fixes that
> have the problem addressed.

Please try mesa 17.0.4 from experimental.

> 
>* What outcome did you expect instead?
>- I hope it corrects this error, in the company where the work has 3
> notebooks with this configuration. It works great without Debian Jessie, but
> testing Debian Stretch RC-3, this giving video driver problems.
> 
> Thanks!
> 
> 
> 
> VGA-compatible devices on PCI bus:
> --
> 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 
> GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c)
> 
> Xorg X server log files on system:
> --
> -rw-r--r-- 1 coringao coringao 24218 Apr 19 13:22 
> /home/coringao/.local/share/xorg/Xorg.0.log
> 
> Contents of most recent Xorg X server log file 
> (/home/coringao/.local/share/xorg/Xorg.0.log):
> -

snip

The following loads the generic modesetting driver with glamor
acceleration. Maybe glamor has issues on your hardware + driver
combination (glamor + OpenGL driver + kernel driver).

> [73.538] (II) LoadModule: "modesetting"
> [73.538] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
> [73.553] (II) Module modesetting: vendor="X.Org Foundation"
> [73.553]  compiled for 1.19.2, module version = 1.19.2
> [73.553]  Module class: X.Org Video Driver
> [73.553]  ABI class: X.Org Video Driver, version 23.0

snip

> [73.594] (II) modeset(0): Creating default Display subsection in Screen 
> section
>   "Default Screen Section" for depth/fbbpp 24/32
> [73.594] (==) modeset(0): Depth 24, (==) framebuffer bpp 32
> [73.594] (==) modeset(0): RGB weight 888
> [73.594] (==) modeset(0): Default visual is TrueColor
> [73.594] (II) Loading sub module "glamoregl"
> [73.594] (II) LoadModule: "glamoregl"
> [73.594] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
> [73.610] (II) Module glamoregl: vendor="X.Org Foundation"
> [73.610]  compiled for 1.19.2, module version = 1.0.0
> [73.610]  ABI class: X.Org ANSI C Emulation, version 0.4
> [73.610] (II) glamor: OpenGL accelerated X.org driver based.
> [73.636] (II) glamor: EGL version 1.4 (DRI2):
> [73.642] (II) modeset(0): glamor initialized
snip

Could you try to use xserver-xorg-video-intel driver by copying the
template xorg.conf to /etc/X11:

cp /usr/share/doc/xserver-xorg-video-intel/xorg.conf /etc/X11


The following looks like an issue with the kernel graphics driver:

> [   21.472066] [drm:drm_atomic_helper_commit_cleanup_done [drm_kms_helper]] 
> *ERROR* [CRTC:26:pipe A] flip_done timed out
> [   21.576017] [ cut here ]
> [   21.576062] WARNING: CPU: 0 PID: 100 at 
> /build/linux-9r9Ph5/linux-4.9.18/drivers/gpu/drm/drm_irq.c:1254 
> drm_wait_one_vblank+0x197/0x1a0 [drm]
> [   21.576200] vblank wait timed out on crtc 0
> [   21.576201] Modules linked in: uvcvideo videobuf2_vmalloc arc4 
> videobuf2_memops iwl3945 videobuf2_v4l2 iwlegacy videobuf2_core 
> snd_hda_codec_si3054 mac80211 videodev media cfg80211 iTCO_wdt 
> iTCO_vendor_support joydev evdev r592 memstick snd_hda_codec_realtek 
> snd_hda_codec_generic rfkill snd_hda_intel pcspkr snd_hda_codec coretemp 
> serio_raw snd_hda_core snd_hwdep lpc_ich mfd_core snd_pcm snd_timer sg i915 
> shpchp drm_kms_helper ene_ir rc_core drm i2c_algo_bit battery ac snd 
> soundcore video wmi button acpi_cpufreq tpm_tis tpm_tis_core tpm parport_pc 
> ppdev lp parport ip_tables x_tables autofs4 ext4 crc16 jbd2 crc32c_generic 
> fscrypto ecb glue_helper lrw gf128mul ablk_helper cryptd aes_x86_64 mbcache 
> sr_mod cdrom sd_mod ata_generic psmouse i2c_i801 i2c_smbus ata_piix libata 
> scsi_mod tg3 firewire_ohci sdhci_pci
> [   21.576257]  sdhci mmc_core firewire_core crc_itu_t ptp pps_core libphy 
> ehci_pci uhci_hcd ehci_hcd usbcore usb_common
> [   21.576269] CPU: 0 PID: 100 Comm: kworker/u4:3 Not tainted 4.9.0-2-amd64 
> #1 Debian 4.9.18-1
> [   21.576270] Hardware name: - N/A

Bug#846698: xserver-xorg-video-sisusb: FTBFS: ../../src/sisusb_driver.c:1670:6: error: too many arguments to function 'pScreen->BlockHandler'

2016-12-15 Thread Andreas Boll 
Control: tags -1 patch fixed-upstream pending

Hi,

thanks much for your work. I've noticed that upstream has already
merged a patch for compatibility with xserver 1.19 [1]. I've gone
ahead and cherry-picked that patch from upstream (the diff is
identical, but it has proper authorship).  Furthermore I've cleaned up
the package a little bit and included your second patch to fix
#745173.

We'll upload the fixed package soon.

Thanks,
Andreas

[1] 
https://cgit.freedesktop.org/xorg/driver/xf86-video-sisusb/commit/?id=6d44eb7a6075b9cc359b44282a7095a8b46c8a38

On Thu, Dec 15, 2016 at 04:41:29PM +0100, Mateusz Łukasik wrote:
> Tags: control + patch
> 
> Hi,
> 
> My NMU debdiff to fix that. Patch is take over from PLD Linux.
> 
> 
> -- 
>  .''`.  Mateusz Łukasik
> : :' :  http://mati75.eu
> `. `'   Debian Member - mat...@linuxmint.pl
>   `-GPG: D93B 0C12 C8D0 4D7A AFBC  FA27 CCD9 1D61 11A0 6851
> 
> 

> diff -u xserver-xorg-video-sisusb-0.9.6/debian/changelog 
> xserver-xorg-video-sisusb-0.9.6/debian/changelog
> --- xserver-xorg-video-sisusb-0.9.6/debian/changelog
> +++ xserver-xorg-video-sisusb-0.9.6/debian/changelog
> @@ -1,3 +1,11 @@
> +xserver-xorg-video-sisusb (1:0.9.6-2.1) unstable; urgency=medium
> +
> +  * Non-maintainer upload.
> +  * Fix FTBFS with xserver 1.19. (Closes: #846698)
> +  * Use arch:linux-any. (Closes: #745173)
> +
> + -- Mateusz Łukasik   Mon, 12 Dec 2016 09:58:58 +0100
> +
>  xserver-xorg-video-sisusb (1:0.9.6-2) unstable; urgency=low
>  
>* Release to unstable.
> diff -u xserver-xorg-video-sisusb-0.9.6/debian/control 
> xserver-xorg-video-sisusb-0.9.6/debian/control
> --- xserver-xorg-video-sisusb-0.9.6/debian/control
> +++ xserver-xorg-video-sisusb-0.9.6/debian/control
> @@ -22,7 +22,7 @@
>  Vcs-Browser: 
> http://git.debian.org/?p=pkg-xorg/driver/xserver-xorg-video-sisusb.git
>  
>  Package: xserver-xorg-video-sisusb
> -Architecture: any
> +Architecture: linux-any
>  Depends:
>   ${shlibs:Depends},
>   ${misc:Depends},
> diff -u xserver-xorg-video-sisusb-0.9.6/debian/patches/series 
> xserver-xorg-video-sisusb-0.9.6/debian/patches/series
> --- xserver-xorg-video-sisusb-0.9.6/debian/patches/series
> +++ xserver-xorg-video-sisusb-0.9.6/debian/patches/series
> @@ -1,0 +2 @@
> +xserver-1.19.patch
> only in patch2:
> unchanged:
> --- xserver-xorg-video-sisusb-0.9.6.orig/debian/patches/xserver-1.19.patch
> +++ xserver-xorg-video-sisusb-0.9.6/debian/patches/xserver-1.19.patch
> @@ -0,0 +1,16 @@
> +--- xf86-video-chips-1.2.6/src/compat-api.h~ 2015-09-26 18:28:01.0 
> +0200
>  xf86-video-chips-1.2.6/src/compat-api.h  2016-11-28 09:12:37.337570460 
> +0100
> +@@ -75,8 +75,13 @@
> + 
> + #define SCREEN_INIT_ARGS_DECL ScreenPtr pScreen, int argc, char **argv
> + 
> ++#if ABI_VIDEODRV_VERSION >= SET_ABI_VERSION(23, 0)
> ++#define BLOCKHANDLER_ARGS_DECL ScreenPtr arg, pointer pTimeout
> ++#define BLOCKHANDLER_ARGS arg, pTimeout
> ++#else
> + #define BLOCKHANDLER_ARGS_DECL ScreenPtr arg, pointer pTimeout, pointer 
> pReadmask
> + #define BLOCKHANDLER_ARGS arg, pTimeout, pReadmask
> ++#endif
> + 
> + #define CLOSE_SCREEN_ARGS_DECL ScreenPtr pScreen
> + #define CLOSE_SCREEN_ARGS pScreen



signature.asc
Description: Digital signature

Bug#845331: xxv-omap still FTBFS against xserver 1.19

2016-11-25 Thread Andreas Boll 
Control: tags -1 + fixed-upstream patch

Upstream has released a new version of xf86-video-omap with support for
xserver 1.19. See also [1].

Thanks,
Andreas

[1] 
https://cgit.freedesktop.org/xorg/driver/xf86-video-omap/log/?id=xf86-video-omap-0.4.5

On Thu, Nov 24, 2016 at 07:47:37PM +0100, Andreas Boll wrote:
> Control: reopen 845331
> 
> Unfortunately it wasn't enough to fix the build against xserver 1.19.
> Apparently xxv-omap needs to be ported to the new NotifyFd API.
> 
> Build log: 
> https://buildd.debian.org/status/fetch.php?pkg=xf86-video-omap=armhf=0.4.4-2=1479924520
> 
> Thanks,
> Andreas


signature.asc
Description: Digital signature

Bug#845637: FTBFS with xserver 1.19

2016-11-25 Thread Andreas Boll 
Source: xf86-video-glamo
Version: 0.0.0+20110719.gitcb9ed170-2
Severity: serious
Control: block 843265 by -1

Dear Maintainer,

your package is part of the ongoing xserver 1.19 transition #843265.
Please make your xorg driver package compatible with xserver 1.19 (i.e.
supporting xorg-video-abi-23).

Build log: 
https://buildd.debian.org/status/fetch.php?pkg=xf86-video-glamo=amd64=0.0.0%2B20110719.gitcb9ed170-2%2Bb3=1480025806


Thanks,
Andreas


signature.asc
Description: Digital signature

Bug#845638: Compatibility with xserver 1.19 / xorg-video-abi-23

2016-11-25 Thread Andreas Boll 
Source: nvidia-graphics-drivers
Version: 367.57-2
Severity: serious
Control: block 843265 by -1

Dear Maintainer,

your package is part of the ongoing xserver 1.19 transition #843265.
Please make your xorg driver package compatible with xserver 1.19 (i.e.
supporting xorg-video-abi-23).


Thanks,
Andreas


signature.asc
Description: Digital signature

Bug#845639: Compatibility with xserver 1.19 / xorg-video-abi-23

2016-11-25 Thread Andreas Boll 
Source: nvidia-graphics-drivers-legacy-304xx
Version: 304.132-1
Severity: serious
Control: block 843265 by -1

Dear Maintainer,

your package is part of the ongoing xserver 1.19 transition #843265.
Please make your xorg driver package compatible with xserver 1.19 (i.e.
supporting xorg-video-abi-23).


Thanks,
Andreas


signature.asc
Description: Digital signature

Bug#845640: Compatibility with xserver 1.19 / xorg-video-abi-23

2016-11-25 Thread Andreas Boll 
Source: nvidia-graphics-drivers-legacy-340xx
Version: 340.98-1
Severity: serious
Control: block 843265 by -1

Dear Maintainer,

your package is part of the ongoing xserver 1.19 transition #843265.
Please make your xorg driver package compatible with xserver 1.19 (i.e.
supporting xorg-video-abi-23).


Thanks,
Andreas


signature.asc
Description: Digital signature

Bug#845635: FTBFS with xserver 1.19

2016-11-25 Thread Andreas Boll 
Source: virtualbox
Version: 5.1.10-dfsg-1
Severity: serious
Control: block 843265 by -1

Dear Maintainer,

your package is part of the ongoing xserver 1.19 transition #843265.
Please make your package compatible with xserver 1.19 (i.e. supporting
xorg-video-abi-23 and/or xorg-input-abi-24).

Build log: 
https://buildd.debian.org/status/fetch.php?pkg=virtualbox=amd64=5.1.10-dfsg-1%2Bb1=1480027319


Thanks,
Andreas


signature.asc
Description: Digital signature

Bug#845331: Reopen Bug#845331, xxv-omap still FTBFS against xserver 1.19 (Bug#845331: fixed in xf86-video-omap 0.4.4-2)

2016-11-24 Thread Andreas Boll 
Control: reopen 845331

Unfortunately it wasn't enough to fix the build against xserver 1.19.
Apparently xxv-omap needs to be ported to the new NotifyFd API.

Build log: 
https://buildd.debian.org/status/fetch.php?pkg=xf86-video-omap=armhf=0.4.4-2=1479924520

Thanks,
Andreas

On Wed, Nov 23, 2016 at 05:24:09PM +, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the xserver-xorg-video-omap package:
> 
> #845331: xserver-xorg-video-omap: Compatibility with xserver 1.19
> 
> It has been closed by Sebastian Reichel <s...@debian.org>.
> 
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Sebastian Reichel 
> <s...@debian.org> by
> replying to this email.
> 
> 
> -- 
> 845331: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845331
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems

> Date: Wed, 23 Nov 2016 17:20:34 +
> From: Sebastian Reichel <s...@debian.org>
> To: 845331-cl...@bugs.debian.org
> Subject: Bug#845331: fixed in xf86-video-omap 0.4.4-2
> 
> Source: xf86-video-omap
> Source-Version: 0.4.4-2
> 
> We believe that the bug you reported is fixed in the latest version of
> xf86-video-omap, which is due to be installed in the Debian FTP archive.
> 
> A summary of the changes between this version and the previous one is
> attached.
> 
> Thank you for reporting the bug, which will now be closed.  If you
> have further comments please address them to 845...@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
> 
> Debian distribution maintenance software
> pp.
> Sebastian Reichel <s...@debian.org> (supplier of updated xf86-video-omap 
> package)
> 
> (This message was generated automatically at their request; if you
> believe that there is a problem with it please contact the archive
> administrators by mailing ftpmas...@ftp-master.debian.org)
> 
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> Format: 1.8
> Date: Wed, 23 Nov 2016 17:09:26 +0100
> Source: xf86-video-omap
> Binary: xserver-xorg-video-omap
> Architecture: source
> Version: 0.4.4-2
> Distribution: unstable
> Urgency: low
> Maintainer: Sebastian Reichel <s...@debian.org>
> Changed-By: Sebastian Reichel <s...@debian.org>
> Description:
>  xserver-xorg-video-omap - X.Org X server -- OMAP display driver
> Closes: 820321 845331
> Changes:
>  xf86-video-omap (0.4.4-2) unstable; urgency=low
>  .
>* Remove staging note from package description (Closes: #820321)
>* Update Debian Standards Version to 3.9.8
>* Add upstream patches for ABI 23 support (Closes: #845331)
>* Switch to compat level 10
>* Enable bindnow hardening
> Checksums-Sha1:
>  87db47be2adb8a456a9943a363e6f337e1fcf376 2117 xf86-video-omap_0.4.4-2.dsc
>  6ec7eb5627df1f0275f765033d276a478c3e7e27 3792 
> xf86-video-omap_0.4.4-2.debian.tar.xz
> Checksums-Sha256:
>  e631ffec3a132839a135baece7995fa038f132e3dff730e097eed6efd1aa7536 2117 
> xf86-video-omap_0.4.4-2.dsc
>  3f310b53d830370d7c5510553278009498e4a552cf73f242b762146cf2afad49 3792 
> xf86-video-omap_0.4.4-2.debian.tar.xz
> Files:
>  4a1c24281550667c823195711e1722fa 2117 x11 optional 
> xf86-video-omap_0.4.4-2.dsc
>  76aa9006c82c39cdcd4bd796a9d71de6 3792 x11 optional 
> xf86-video-omap_0.4.4-2.debian.tar.xz
> 
> -BEGIN PGP SIGNATURE-
> 
> iQJDBAEBCgAtFiEE72YNB0Y/i3JqeVQT2O7X88g7+poFAlg1yiEPHHNyZUBkZWJp
> YW4ub3JnAAoJENju1/PIO/qa/McP+wbAZspOjjXAgyaNCsbwx+WivGb5i/KnP1ug
> ArOCVHWMjQd8RwwyMR0S9e8ISCx4wdzPwyrFg63jel0NEKUm6hJMrNEDn8wJYtQQ
> cINNwQQWYc/GKcOLwpVnFDiu2UkE/aYPHjlWAr2Q8AJ1XCyK097SUnOT/1zKf/wr
> EfOgMKauEC/woj2JZ+1FJBsWw2Wfq2qTnx7YCTk/Fz7BjyU/r3wffAWzl7cCQG7F
> ikf26vbJRaUb2kGVZ9sOrjwOTdKaUIgSYmKl4Ec9oKFbPczvjwM9yxH4kZ/EALPN
> F1KXW72ClRlfMAK78AdDNRw+HU5IblxoSy3EHlc2MrxQ0HpMj2Hd0ORSPr84PCze
> RGuIKHeJV7oGymnyNBxh3CkU4ziJjPiVwwy6cbR5Y8uYbATJMqbE6BUsIK+ZU73t
> 2ViGMZ24XIoY9QT9r4uD8bno6BaBk8exZCSQRHqrt86tgDPIlsy/UuZBkfIqZJPV
> EFc38hU4B2HkIjRPQbmXncNmwS01/GuGvBZpQKNsgnQWXpDM1SvOuYQ3uZH0SB7Q
> XXV9f/+uEiJxnK5zP3aPAG1WozJOX8OzcI6LuemcFdYKxBs1il2kzkcdBMh+/jwq
> +Ovc07LkbVmapkWICwUrTxEmXFD2T7TMtAg11t0Bwwb2pvyeKny7c7iKkukgJzxx
> F3WFZKiu
> =3erl
> -END PGP SIGNATURE-

> Date: Tue, 22 Nov 2016 15:59:15 +0100
> From: Andreas Boll <andreas.boll@gmail.com>
> To: Debian Bug Tracking System <sub...@bugs.debian.org>
> Subject: xserver-xorg-video-omap: Compatibility with xserver 1.19
> User-Agent: Mutt/1.5.23 (2014-03-12)
> 
> Package: xserver-xorg-vide

Bug#844227: FTBFS on mips*, ./.libs/libmutter-cogl.so: undefined reference to `eglQueryString'

2016-11-15 Thread Andreas Boll 
On Mon, Nov 14, 2016 at 06:47:00PM +0100, Michael Biebl wrote:
> Am 13.11.2016 um 19:43 schrieb Michael Biebl:
> > Am 13.11.2016 um 18:37 schrieb Sven Joachim:
> >> The toolchain has also changed quite a bit in the past four weeks, with
> >> gcc having pie enabled by default and binutils at a bleeding edge
> >> snapshot.  Maybe one of those has triggered the build failure.
> > 
> > That might well be it. Currently mutter still builds fine in stretch.
> > The new binutils should migrate to testing soon.
> > I can then retry the build on a mips porter machine with
> > 2.27.51.20161108-1
> 
> binutils 2.27.51.20161108-1 just migrated to stretch. mutter still
> builds fine in stretch with this version. So I'd say we can cross off
> binutils from the list of suspects.

As Sven already mentioned these symbols are still available otherwise
Mesa would FTBFS as we strictly check those symbols in the build with

override_dh_makeshlibs:
dh_makeshlibs -a -- -c4

Furthermore I've manually checked libegl1-mesa_12.0.4-2_mips.deb [1]
with nm that those symbols are still exported.

Mesa could be still affected by a broken binutils. To cross out
binutils or other toolchain bugs we would need to rebuild Mesa
12.0.3-3 (= version in testing) with the current toolchain and build
mutter against this rebuild of Mesa.
Michael, could you check this on a mips porter machine?

If it works with Mesa 12.0.3-3 we need to bisect Mesa. Otherwise it's
not a regression introduced with Mesa 12.0.4.


Thanks,
Andreas

[1] https://packages.debian.org/sid/mips/libegl1-mesa/download


signature.asc
Description: Digital signature

Bug#808694: x11proto-fonts: FTBFS: dh_install: x11proto-fonts-dev missing files (usr/share/doc/fontsproto/*.txt), aborting

2016-01-26 Thread Andreas Boll 
This issue has been fixed in xutils-dev 1:7.7+4. See also #613674.

Thanks,
Andreas

On Mon, Dec 21, 2015 at 08:30:04PM +, Chris West (Faux) wrote:
> Source: x11proto-fonts
> Version: 2.1.3-1
> Severity: serious
> Justification: fails to build from source
> Tags: sid stretch
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: ftbfs
> X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org
> 
> Dear Maintainer,
> 
> The package fails to build:
> 
> make[1]: Leaving directory '/x11proto-fonts-2.1.3/build'
> dh_testdir
> dh_testroot
> dh_installdocs
> dh_installman
> find debian/tmp/usr/share/doc/fontsproto -name '*.xml' -delete
> dh_install --sourcedir=debian/tmp --fail-missing --exclude .db
> dh_install: x11proto-fonts-dev missing files 
> (usr/share/doc/fontsproto/*.txt), aborting
> debian/rules:70: recipe for target 'binary-indep' failed
> make: *** [binary-indep] Error 255
> dpkg-buildpackage: error: debian/rules binary gave error exit status 2
> 
> Full build log:
> https://reproducible.debian.net/rb-pkg/unstable/amd64/x11proto-fonts.html
> 
> -- System Information:
> Debian Release: stretch/sid
> APT prefers unstable
> APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)


signature.asc
Description: Digital signature

Bug#806498: x11proto-core: FTBFS: dh_install: x11proto-core-dev missing files (usr/share/doc/x11proto-core-dev/*.txt), aborting

2016-01-26 Thread Andreas Boll 
This issue has been fixed in xutils-dev 1:7.7+4. See also #613674.

Thanks,
Andreas

On Fri, Nov 27, 2015 at 11:31:12PM +, Chris West (Faux) wrote:
> Source: x11proto-core
> Version: 7.0.27-1
> Severity: serious
> Justification: fails to build from source
> Tags: sid 
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: ftbfs
> X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org
> 
> Dear Maintainer,
> 
> The package fails to build:
> 
> make[2]: Leaving directory '/x11proto-core-7.0.27/build'
> make[1]: Leaving directory '/x11proto-core-7.0.27'
>debian/rules override_dh_install
> make[1]: Entering directory '/x11proto-core-7.0.27'
> find debian/tmp/usr/share/doc/x11proto-core-dev -name '*.xml' -delete
> find debian/tmp/usr/share/doc/x11proto-core-dev -name '*.db' -delete
> find debian/tmp/usr/share/doc/x11proto-core-dev -name '*.ps' -delete
> dh_install --fail-missing
> dh_install: x11proto-core-dev missing files 
> (usr/share/doc/x11proto-core-dev/*.txt), aborting
> debian/rules:17: recipe for target 'override_dh_install' failed
> make[1]: *** [override_dh_install] Error 255
> 
> Full build log:
> https://reproducible.debian.net/rb-pkg/unstable/amd64/x11proto-core.html
> 
> -- System Information:
> Debian Release: stretch/sid
> APT prefers unstable
> APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)


signature.asc
Description: Digital signature

Bug#810885: libelf-dev requires libc >= 2.22

2016-01-13 Thread Andreas Boll 
Package: libelf-dev
Version: 0.165-1
Severity: serious

Dear Maintainer,

the newest upload of libelf-dev doesn't work with libc 2.21-6 and thus breaks
the build of mesa.
I've reproduced the FTBFS with the following minimal testcase:

cat > elf-ftbfs.c << EOF
#include 
EOF

gcc -c elf-ftbfs.c

In file included from /usr/include/gelf.h:32:0,
 from elf-ftbfs.c:1:
/usr/include/libelf.h:280:8: error: unknown type name ‘Elf32_Chdr’
 extern Elf32_Chdr *elf32_getchdr (Elf_Scn *__scn);
^
/usr/include/libelf.h:281:8: error: unknown type name ‘Elf64_Chdr’
 extern Elf64_Chdr *elf64_getchdr (Elf_Scn *__scn);
^
In file included from elf-ftbfs.c:1:0:
/usr/include/gelf.h:89:9: error: unknown type name ‘Elf64_Chdr’
 typedef Elf64_Chdr GElf_Chdr;
 ^

Using libc 2.22 from experimental fixes this issue.

It seems that this implicit dependency on libc 2.22 was introduced in this
upstream change [1].

jcristau found the corresponding libc patch [2].

Please consider reverting the upstream change until we have libc 2.22 in
unstable.

Thanks,
Andreas

[1] 
https://git.fedorahosted.org/cgit/elfutils.git/commit/?id=5ddb50af4a488fdec358570502cbe058acb8ae93
[2] https://sourceware.org/ml/libc-alpha/2015-05/msg00018.html


signature.asc
Description: Digital signature

Bug#801059: libxmu's debian/rules is not safe to execute in parallel

2015-11-13 Thread Andreas Boll 
Does the attached patch also fix your issue?

Thanks,
Andreas

On Mon, Oct 05, 2015 at 09:12:20PM +0200, Matthias Klose wrote:
> Package: src:libxmu
> Version: 2:1.1.2-1
> Severity: serious
> Tags: sid stretch patch
> 
> seen in an Ubuntu test rebuild, however this may happen as well in a Debian 
> build.
> 
> https://launchpadlibrarian.net/219669711/buildlog_ubuntu-wily-amd64.libxmu_2%3A1.1.2-1_BUILDING.txt.gz
> 
> the problem is that -j is added to MAKEFLAGS, and the binary-arch and
> binary-indep targets are executed in parallel.  The Ubuntu build now fails
> 
> dh_builddeb -s
> [...]
> dh_builddeb
> dpkg-deb: building package 'libxmu6' in '../libxmu6_1.1.2-1_amd64.deb'.
> tar: ./usr/lib/x86_64-linux-gnu/libXmu.so.6.2.0: file changed as we read it
> dpkg-deb: error: subprocess tar -cf returned error exit status 1
> [...]
> debian/rules:101: recipe for target 'binary-indep' failed
> make: *** [binary-indep] Error 1
> make: *** Waiting for unfinished jobs
> 
> Every debhelper command for the architecture dependent packages are executed 
> twice.
> 
> patch at
> http://launchpadlibrarian.net/220316375/libxmu_2%3A1.1.2-1_2%3A1.1.2-1ubuntu1.diff.gz
> 
> (together with using dpkg-buildflags, maybe dh_autoreconf could be used as 
> well).
From 0c063344e70e98592b265118ebf00450bb474bc9 Mon Sep 17 00:00:00 2001
From: Andreas Boll <andreas.boll@gmail.com>
Date: Fri, 13 Nov 2015 20:44:11 +0100
Subject: [PATCH] Switch to dh with the autoreconf and quilt addons.

Signed-off-by: Andreas Boll <andreas.boll@gmail.com>
---
 debian/changelog |   6 +++
 debian/compat|   2 +-
 debian/control   |   4 +-
 debian/rules | 117 +--
 4 files changed, 28 insertions(+), 101 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index c65fef4..5d790d1 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+libxmu (2:1.1.2-2) UNRELEASED; urgency=medium
+
+  * Switch to dh with the autoreconf and quilt addons.
+
+ -- Andreas Boll <andreas.boll@gmail.com>  Fri, 13 Nov 2015 20:43:36 +0100
+
 libxmu (2:1.1.2-1) unstable; urgency=low
 
   * New upstream release.
diff --git a/debian/compat b/debian/compat
index 7f8f011..ec63514 100644
--- a/debian/compat
+++ b/debian/compat
@@ -1 +1 @@
-7
+9
diff --git a/debian/control b/debian/control
index 054ff51..1f51029 100644
--- a/debian/control
+++ b/debian/control
@@ -4,8 +4,8 @@ Priority: optional
 Maintainer: Debian X Strike Force <debia...@lists.debian.org>
 Uploaders: Cyril Brulebois <k...@debian.org>
 Build-Depends:
- debhelper (>= 8.1.3),
- dpkg-dev (>= 1.16.0),
+ debhelper (>= 9),
+ dh-autoreconf,
  libx11-dev (>= 1:0.99.2),
  libxt-dev (>= 1:0.99.1),
  libxext-dev (>= 1:0.99.1),
diff --git a/debian/rules b/debian/rules
index 3fe6792..101ab5e 100755
--- a/debian/rules
+++ b/debian/rules
@@ -7,107 +7,28 @@
 # Uncomment this to turn on verbose mode.
 #export DH_VERBOSE=1
 
-include /usr/share/quilt/quilt.make
-
-CFLAGS = -Wall -g
-ifneq (,$(filter noopt,$(DEB_BUILD_OPTIONS)))
-	CFLAGS += -O0
-else
-	CFLAGS += -O2
-endif
-ifneq (,$(filter parallel=%,$(DEB_BUILD_OPTIONS)))
-	NUMJOBS = $(patsubst parallel=%,%,$(filter parallel=%,$(DEB_BUILD_OPTIONS)))
-	MAKEFLAGS += -j$(NUMJOBS)
-endif
-
-DEB_HOST_ARCH  ?= $(shell dpkg-architecture -qDEB_HOST_ARCH)
-DEB_HOST_GNU_TYPE  ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE)
-DEB_BUILD_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE)
-DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH)
-
-ifeq ($(DEB_BUILD_GNU_TYPE), $(DEB_HOST_GNU_TYPE))
-	confflags += --build=$(DEB_HOST_GNU_TYPE)
-else
-	confflags += --build=$(DEB_BUILD_GNU_TYPE) --host=$(DEB_HOST_GNU_TYPE)
-endif
-
-configure: $(QUILT_STAMPFN)
-	dh_testdir
-	autoreconf -vfi
-
-build: build-arch build-indep
-build-indep build-arch: build-stamp
-build-stamp: configure
-	dh_testdir
-
-	mkdir -p build
-	cd build && \
-	../configure --prefix=/usr --mandir=\$${prefix}/share/man \
-	 --libdir=\$${prefix}/lib/$(DEB_HOST_MULTIARCH) \
-	 --infodir=\$${prefix}/share/info $(confflags) \
-	 --docdir=\$${prefix}/share/doc/libxmu-headers \
-	 --with-xmlto --without-fop \
-	 CFLAGS="$(CFLAGS)" 
-	cd build && $(MAKE)
-	>$@
-
-clean: unpatch
-	dh_testdir
-	rm -f build-stamp
-	rm -f config.cache config.log config.status
-	rm -f */config.cache */config.log */config.status
-	rm -f conftest* */conftest*
-	rm -rf autom4te.cache */autom4te.cache
-	rm -rf build
-	rm -f INSTALL aclocal.m4 config.guess config.h.in config.sub configure
-	rm -f depcomp install-sh ltmain.sh missing mkinstalldirs
-	find -name Makefile.in -delete
-	dh_clean
-
-install: build
-	dh_testdir
-	dh_testroot
-	dh_clean -k
-	dh_installdirs
-
-	cd build && $(MAKE) DESTDIR=$(CURDIR)/debi