Bug#924271: openarena: crashes at launch with "Couldn't compile shader" message.

2019-03-10 Thread Matthew Hoare
Yes, that fixes the problem.

Thanks!

On Sun, 10 Mar 2019, 19:57 Simon McVittie,  wrote:

> Control: reassign -1 ioquake3 1.36+u20181222.e5da13f~dfsg-1
> Control: tags -1 + moreinfo
> Control: affects -1 openarena quake3
> Control: affects 923226 + openarena quake3
>
> On Sun, 10 Mar 2019 at 19:42:20 +0000, Matthew Hoare wrote:
> >Program failed to launch with a lengthy error message (attached).
>
> Please upgrade ioquake3 to 1.36+u20181222.e5da13f~dfsg-2 (in unstable)
> and try again: it should be fixed in that version. This looks very similar
> to #923226, and indeed you seem to have the same older Intel GPU as the
> reporter of #923226.
>
> smcv
>


Bug#924271: openarena: crashes at launch with "Couldn't compile shader" message.

2019-03-10 Thread Matthew Hoare
Package: openarena
Version: 0.8.8+dfsg-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

   * What led up to the situation?
   I attempted to launch the program.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   Ran `openarena` from a terminal.

   * What was the outcome of this action?
   Program failed to launch with a lengthy error message (attached).

   * What outcome did you expect instead?
   I expected the program to launch normally.


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages openarena depends on:
ii  ioquake3  1.36+u20181222.e5da13f~dfsg-1
ii  libc6 2.28-7
ii  openarena-081-maps0.8.5split-11
ii  openarena-081-misc0.8.5split-11
ii  openarena-081-players 0.8.5split-11
ii  openarena-081-players-mature  0.8.5split-11
ii  openarena-081-textures0.8.5split-11
ii  openarena-085-data0.8.5split-11
ii  openarena-088-data0.8.8-9
ii  openarena-data0.8.5split-11

Versions of packages openarena recommends:
ii  openarena-oacmp1  3-4

openarena suggests no packages.

Versions of packages ioquake3 depends on:
ii  ioquake3-server  1.36+u20181222.e5da13f~dfsg-1
ii  libc62.28-7
ii  libcurl3-gnutls  7.64.0-1
ii  libgl1   1.1.0-1
ii  libjpeg62-turbo  1:1.5.2-2+b1
ii  libogg0  1.3.2-1+b1
ii  libopenal1   1:1.19.1-1
ii  libopus0 1.3-1
ii  libopusfile0 0.9+20170913-1
ii  libsdl2-2.0-02.0.9+dfsg1-1
ii  libvorbis0a  1.3.6-2
ii  libvorbisfile3   1.3.6-2
ii  zlib1g   1:1.2.11.dfsg-1

Versions of packages ioquake3 recommends:
ii  x11-utils  7.7+4

-- no debconf information
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
tty]    ioq3 1.36+u20181222.e5da13f~dfsg-1/Debian linux-x86_64 Jan 14 
2019
tty]    SSE instruction set enabled
tty]    - FS_Startup -
tty]    We are looking in the current search path:
tty]    /home/empty/.openarena/baseoa
tty]    /usr/lib/openarena/baseoa
tty]    /usr/lib/openarena/baseoa/z_oacmp-volume1-v3.pk3 (370 files)
tty]    /usr/lib/openarena/baseoa/pak6-patch088.pk3 (711 files)
tty]    /usr/lib/openarena/baseoa/pak6-patch085.pk3 (559 files)
tty]    /usr/lib/openarena/baseoa/pak6-misc.pk3 (229 files)
tty]    /usr/lib/openarena/baseoa/pak5-TA.pk3 (139 files)
tty]    /usr/lib/openarena/baseoa/pak4-textures.pk3 (1753 files)
tty]    /usr/lib/openarena/baseoa/pak2-players.pk3 (669 files)
tty]    /usr/lib/openarena/baseoa/pak2-players-mature.pk3 (231 files)
tty]    /usr/lib/openarena/baseoa/pak1-maps.pk3 (100 files)
tty]    /usr/lib/openarena/baseoa/pak0.pk3 (1042 files)
tty]    
tty]    --
tty]    5803 files in pk3 files
tty]    execing default.cfg
tty]    couldn't exec q3config.cfg
tty]    couldn't exec autoexec.cfg
tty]    Hunk_Clear: reset the hunk ok
tty][Detaching after fork from child process 7475]
    - Client Initialization -
tty]    Couldn't read q3history.
tty]    - Initializing Renderer 
tty]    Trying to load "renderer_opengl2_x86_64.so" from 
"/usr/lib/ioquake3"...
tty]    ---
tty]    QKEY found.
tty]    - Client Initialization Complete -
tty]    tty]
tty]q     - R_Init -
tty]q[Detaching after fork from child process 7485]
[New Thread 0x7f89daf18700 (LWP 7486)]
     SDL using driver "x11"
tty]q     Initializing OpenGL display
tty]q     Display aspect: 1.600
tty]q     ...setting mode 3: 640 480
tty]q     Trying to get an OpenGL 3.2 core context
tty]q     SDL_GL_CreateContext failed: Could not create GL context: 
GLXBadFBConfig
tty]q     Reverting to default context
tty]q     Using 24 color bits, 24 depth, 8 stencil display.
tty]q     Available modes: '640x400 1280x800 640x360 720x405 864x486 
960x540 1024x576 1280x720 640x480 800x600 1024x768'
tty]q     GL_RENDERER: Mesa DRI Intel(R) Ironlake Mobile 
tty]q     Initializing OpenGL extensions
tty]q     ...ignoring GL_EXT_texture_compression_s3tc
tty]q     ...ignoring GL_S3_s3tc
tty]q     ...ignoring GL_EXT_texture_filter_anisotropic
tty]q     ...using GL_ARB_framebuffer_obje

Bug#861536: runit-init: Cannot reboot or shutdown after installing (or removing) the package.

2017-05-28 Thread Matthew Hoare
I can confirm that this issue also occurs with a fresh (debootstrap)
installation of pure Debian stretch.

I can also confirm that these four commands will reboot into the new
init system without damaging the mounted filesystems:

`echo 1 > /proc/sys/kernel/sysrq`

`echo s > /proc/sysrq-trigger`

`echo u > /proc/sysrq-trigger`

`echo b > /proc/sysrq-trigger`

Would it be appropriate to provide these commands for temporary use
after switching init?

I can attempt an NMU but I am relatively unskilled with Debian
packaging so it may take a while.

-- 
Matthew T. Hoare



Bug#861536: runit-init: Cannot reboot or shutdown after installing (or removing) the package.

2017-05-23 Thread Matthew Hoare
On 23/05/2017, John Paul Adrian Glaubitz  wrote:
> I'm not sure why you are reporting this
> bug to Debian in the first place.
>

I am one of the BunsenLabs developers, the distribution is a theming
and configuration set applied to a Debian base.

The system from which the report was sent was installed as a Debian
stretch system using `debootstrap` with a post-installation
configuration script [1] applied afterwards.

I can reproduce this issue in a fresh Debian stretch system if
required but I was presuming that an upstream bug report was
appropriate in this case, apologies if I was mistaken.

Regards,

Matthew.

[1] https://github.com/BunsenLabs/bunsen-netinstall/tree/helium-dev