Your message dated Wed, 8 Nov 2017 15:42:10 +0100 with message-id <20171108144100.oi3xwvyhgxfdkp6j@localhost.localdomain> and subject line Re: Bug#876501: Fixed in buster has caused the Debian Bug report #876501, regarding Xdmx segfault on start to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 876501: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876501 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: Xdmx segfault on start
- From: Alex <allo@laxu.de>
- Date: Fri, 22 Sep 2017 21:52:02 +0200
- Message-id: <150610992265.8512.6893707920568279260.reportbug@nemesis.laxu.de>
Package: Xdmx Version: 1.19.3-2 Severity: important Dear Maintainer, Xdmx segfaults when starting it with Xdmx -display 192.168.102.57:0 -norender :1 I am not sure if the parameters are correct as I was setting it up, but it should not segfault anyway. The trace is: (II) dmx[o0/192.168.102.57:0]: 0x259 DirectColor 24b 8b/rgb 256 0xff0000 0xff00 0x00ff (II) dmx[o0/192.168.102.57:0]: 0x25a DirectColor 24b 8b/rgb 256 0xff0000 0xff00 0x00ff (II) dmx[o0/192.168.102.57:0]: 0x25b DirectColor 24b 8b/rgb 256 0xff0000 0xff00 0x00ff (II) dmx[o0/192.168.102.57:0]: 0x41 TrueColor 32b 8b/rgb 256 0xff0000 0xff00 0x00ff (II) dmx[o0/192.168.102.57:0]: DPMS 1.1 (on, enabled, 0 0 0) (EE) (EE) Backtrace: (EE) 0: Xdmx (xorg_backtrace+0x4a) [0x55892085c8ba] (EE) 1: Xdmx (0x5589206f0000+0x170669) [0x558920860669] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f95824e2000+0x110c0) [0x7f95824f30c0] (EE) 3: Xdmx (TimerForce+0x10) [0x55892085a360] (EE) 4: Xdmx (0x5589206f0000+0x41bf1) [0x558920731bf1] (EE) 5: Xdmx (0x5589206f0000+0x337b5) [0x5589207237b5] (EE) 6: Xdmx (0x5589206f0000+0x40b17) [0x558920730b17] (EE) 7: Xdmx (0x5589206f0000+0x40f85) [0x558920730f85] (EE) 8: Xdmx (AddScreen+0xd7) [0x558920825fc7] (EE) 9: Xdmx (InitOutput+0x40f) [0x55892072b4ef] (EE) 10: Xdmx (0x5589206f0000+0x139b26) [0x558920829b26] (EE) 11: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf1) [0x7f95821652e1] (EE) 12: Xdmx (_start+0x2a) [0x55892071f1ba] (EE) (EE) Segmentation fault at address 0x0 (EE) Fatal server error: (EE) Caught signal 11 (Segmentation fault). Server aborting (EE) with a lot of the DirectColor and TrueColor messages before. -- System Information: Debian Release: 9.1 APT prefers testing APT policy: (900, 'testing') Architecture: amd64 (x86_64) Init: sysvinit (via /sbin/init)
--- End Message ---
--- Begin Message ---
- To: Eric Van Buggenhaut <ericvb69@gmail.com>, 876501-done@bugs.debian.org
- Subject: Re: Bug#876501: Fixed in buster
- From: Andreas Boll <andreas.boll.dev@gmail.com>
- Date: Wed, 8 Nov 2017 15:42:10 +0100
- Message-id: <20171108144100.oi3xwvyhgxfdkp6j@localhost.localdomain>
- In-reply-to: <[🔎] CALQVJpYNrHVdBrJfmyV0EL3jo3fqf+dvE4fn2zvVvnOpFT1=2A@mail.gmail.com>
- References: <150610992265.8512.6893707920568279260.reportbug@nemesis.laxu.de> <[🔎] CALQVJpYNrHVdBrJfmyV0EL3jo3fqf+dvE4fn2zvVvnOpFT1=2A@mail.gmail.com>
Version: 2:1.19.4-1 On Tue, Nov 07, 2017 at 12:12:26PM +0100, Eric Van Buggenhaut wrote: > After testing I can confirm the patch I mentioned before has been > applied and the bug fixed in version 2:1.19.5-1 > -- > Eric Thanks Eric for confirming. That patch has been included since 2:1.19.4-1. Closing. Thanks, AndreasAttachment: signature.asc
Description: PGP signature
--- End Message ---