as/like said in the stackeoverflow link, there is no "core dump" log
in syslog, though i had systemd-coredump installed.
i forgot to write:
when i woke up laptop, entered password, {i do not remember, whether i
entered login (username) that time}, and i had come into new desktop
session, instead of saved (suspended) session.
then many these messages were appearing in syslog:
Dec 12 20:51:57 localhost at-spi2-regis
Package: xserver-xorg
Version: 1:7.7+19
Followup-For: Bug #644636
-- Package-specific info:
/etc/X11/X does not exist.
/etc/X11/X is not a symlink.
/etc/X11/X is not executable.
VGA-compatible devices on PCI bus:
--
00:02.0 VGA compatible controller [0300]: Intel
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-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Co
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 to
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, email
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 tempor
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 h
On Fri, Oct 21, 2011 at 23:43:47 +0200, Florian Boelstler wrote:
> 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 sen
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
On Fri, Oct 7, 2011 at 18:57:13 +0200, Florian Boelstler wrote:
> Backtrace:
> 0: /usr/bin/X11/X (xorg_backtrace+0x3b) [0x80adedb]
> 1: /usr/bin/X11/X (0x8048000+0x5aab5) [0x80a2ab5]
> 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xb775740c]
> 3: /usr/bin/X11/X (0x8048000+0x2bec0) [0x8073ec0]
> 4: /usr
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 d
On Fri, Oct 7, 2011 at 18:57:13 +0200, Florian Boelstler wrote:
There seems to be 0 content in your mail other than the logs added by
reportbug. You'll have to do better.
Cheers,
Julien
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Tr
13 matches
Mail list logo
