Bug#644636: Ping

2014-01-31 Thread Florian Boelstler
Hi, I can't speak for the issue raised by Alexander. Though the original issue I've reported is gone after having moved away from wdm. Still happily using xdm :) Cheers Florian -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Bug#644636: news, wdm seems to be problematic

2012-11-22 Thread Florian Boelstler
I recently switched from wmii to i3 for managing my windows. This didn't cure the problem. Switching from wdm to xdm seems to resolve the problem. It's just a day of testing so far, though looks pretty promising. I'll report back in a few days... Cheers, Florian -- To UNSUBSCRIBE, email

Bug#644636: (no subject)

2012-10-03 Thread Florian Boelstler
The issue still occurs. Maybe this piece of kernel log is pointing to something more useful: plugin-containe[3683]: segfault at b2d025e4 ip b664a4e6 sp b2389034 error 6 in libpthread-2.11.3.so[b664+15000] It's always printed if the problem occurs. Cheers Florian -- To UNSUBSCRIBE,

Bug#644636: xorg: xserver randomly crashes without any clear indication

2011-12-25 Thread Florian Boelstler
Just coincidentally stumbled over .xsession-errors. Shortly after the session start at 12:55 the xserver was restarted. Is this output below of any help? Or just a consequence? Thanks. Xsession: X session started for flo at Sat Dec 24 12:55:57 CET 2011 XIO: fatal IO error 11 (Resource

Bug#644636: xorg: xserver randomly crashes without any clear indication

2011-11-22 Thread Florian Boelstler
Am 26.10.2011 23:47, schrieb Julien Cristau: Is there anything I can do to trap that obscure piece of software sending SIGQUIT? IIRC the times I've seen this it was plymouth or something stealing the console out from under X. Maybe check for things opening /dev/tty[0-9]*. I don't have

Bug#644636: xorg: xserver randomly crashes without any clear indication

2011-10-21 Thread Florian Boelstler
Am 07.10.2011 20:43, schrieb Julien Cristau: Fatal server error: Caught signal 3 (Quit). Server aborting OK, I missed this one the first time. I don't think that's a bug in X, something on your system is sending us SIGQUIT when they shouldn't. Is there anything I can do to trap that obscure

Bug#644636: xorg: xserver randomly crashes without any clear indication

2011-10-07 Thread Florian Boelstler
Am 07.10.2011 19:39, schrieb Julien Cristau: There seems to be 0 content in your mail other than the logs added by reportbug. You'll have to do better. Thanks for your advice. I did enter some information on the first screen presented by reportbug. Unfortunately it got lost for a reason I

Bug#537181: xserver-xorg-dev: Invalid #includes for pixman.h in several headers

2009-07-15 Thread Florian Boelstler
Package: xserver-xorg-dev Version: 2:1.4.2-10.lenny2 Severity: important These headers refer to #include pixman/pixman.h, which should be pixman-1/pixman.h provided by package libpixman-1-dev on Lenny: /usr/include/xorg/fb.h /usr/include/xorg/miscstruct.h /usr/include/xorg/picture.h This

Bug#537183: libpixman-1-dev: Invalid #include for pixman-version.h in pixman.h

2009-07-15 Thread Florian Boelstler
Package: libpixman-1-dev Version: 0.10.0-2 Severity: important This header refers to #include pixman/pixman-version.h, which should be pixman-1/pixman-version.h Other packages depending on this package are unusable, e.g. xserver-xorg-dev. Florian -- System Information: Debian Release:

Bug#537181: xserver-xorg-dev: Invalid #includes for pixman.h in several headers

2009-07-15 Thread Florian Boelstler
Brice Goglin schrieb: Florian Boelstler wrote: Package: xserver-xorg-dev Version: 2:1.4.2-10.lenny2 Severity: important These headers refer to #include pixman/pixman.h, which should be pixman-1/pixman.h provided by package libpixman-1-dev on Lenny: /usr/include/xorg/fb.h /usr/include