FWIW, started using phosphor again recently and I'm seeing the same
problem. I'm running phosphor from KDE 3.5 with fortune as source
for text (had to edit /usr/share/xscreensaver/config/phosphor.xml
to be able to use that).
Mar 6 19:07:17 aragorn kernel: phosphor[31384]: segfault at 0
ip
On Tue, Dec 2, 2008 at 12:39 PM, Elmar Hoffmann <[EMAIL PROTECTED]> wrote:
> GLX does work fine on the second server and glxinfo sais "direct
> rendering: Yes", so it seems I do get DRI on multiple servers.
> The /var/log/Xorg.[01].log files of both servers also only differ with
> regard to unrelat
Hi Tormod,
on Tue, Dec 02, 2008 at 00:09:17 +0100, you wrote:
> Usually you will only get DRI on the first X server, so if phosphor is
> running without DRI it's probably why it's so stable. Do you notice it
> is slower, or uses more CPU?
GLX does work fine on the second server and glxinfo sais
On Mon, Dec 1, 2008 at 10:35 PM, Elmar Hoffmann <[EMAIL PROTECTED]> wrote:
> I have it running with that commandline in a separate X server via
> startx for a couple of days now. it still runs fine, whereas I had two
> or three crashes of the phosphor run by xscreensaver in my usual X
> session dur
Hi,
on Tue, Nov 25, 2008 at 01:19:45 +0100, I wrote:
> > Do you run it fullscreen? You can use the -root option in a bare X
> > session (failsafe xterm session), i.e. without desktop backgrounds etc
> > hiding the root window.
>
> With gdb I did use the same options as configured in xscreensaver
Hi Tormod,
on Mon, Nov 24, 2008 at 10:04:47 +0100, you wrote:
> Thanks for your bug report. Please attach your /var/log/Xorg.0.log and
> /etc/X11/xorg.conf.
Done.
> gdb slows down execution a bit, so it sometimes helps against timing
> issues and races. [...]
Yeah, that would be an explanation
Thanks for your bug report. Please attach your /var/log/Xorg.0.log and
/etc/X11/xorg.conf.
gdb slows down execution a bit, so it sometimes helps against timing
issues and races. Can you make phosphor crash standalone without gdb?
Do you run it fullscreen? You can use the -root option in a bare X
s
Package: xscreensaver-data-extra
Version: 5.05-3
Severity: normal
phosphor, when used in xscreensaver, segfaults regularly after a while,
leading to a black screen remaining and syslog showing:
kernel: phosphor[27671]: segfault at 0 ip b7dab351 sp bf87a5d8 error 4 in
libc-2.7.so[b7d45000+155000]
8 matches
Mail list logo
