109626 – xscreensaver-4.22-r4 causes fatal IO error on exit

Bug 109626 - xscreensaver-4.22-r4 causes fatal IO error on exit

Summary: xscreensaver-4.22-r4 causes fatal IO error on exit

Status:	RESOLVED INVALID

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	[OLD] Unspecified (show other bugs)
Hardware:	x86 Linux

Importance:	High normal
Assignee:	Desktop Misc. Team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2005-10-17 13:51 UTC by Bharath Ramesh
Modified:	2005-10-25 04:43 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Bharath Ramesh 2005-10-17 13:51:04 UTC

I am running Xorg 6.8.2 (xorg-x11-6.8.2-r4) on a freshly installed gentoo
2005.1. I keep getting this error whenever I quit X with xscreensaver running.

XIO: fatal error 104 (Connection reset by peer) on X xerver: ":0.0"
     after 0 requests (0 known processed) with 0 events remaining.

My .xinitrc looks like:

xmodmap $HOME/.Xmodmap

gkrellm2 &
xscreensaver &

exec enlightenment

Reproducible: Always
Steps to Reproduce:
1. Use the xinitrc specified.
2. startx
3. quit enlightenment.

Actual Results:  
xscreensaver causes fatal IO error

Expected Results:  
xscreensaver should terminate correctly.

Portage 2.0.51.22-r3 (default-linux/x86/2005.1, gcc-3.4.4, glibc-2.3.5-r2,
2.6.12-gentoo-r10 i686)
=================================================================
System uname: 2.6.12-gentoo-r10 i686 Intel(R) Pentium(R) M processor 1.86GHz
Gentoo Base System version 1.6.13
ccache version 2.3 [enabled]
dev-lang/python:     2.4.2
sys-apps/sandbox:    1.2.12
sys-devel/autoconf:  2.13, 2.59-r6
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1
sys-devel/binutils:  2.15.92.0.2-r10
sys-devel/libtool:   1.5.20
virtual/os-headers:  2.6.11-r2
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-O2 -march=pentium-m -fomit-frame-pointer -mfpmath=sse -mmmx -msse
-msse2 -pipe"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config
/usr/lib/X11/xkb /usr/share/config /usr/share/texmf/dvipdfm/config/
/usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/
/usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -march=pentium-m -fomit-frame-pointer -mfpmath=sse -mmmx -msse
-msse2 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig candy ccache distlocks sandbox sfperms strict userpriv
usersandbox"
GENTOO_MIRRORS="http://mirror.datapipe.net/gentoo"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="x86 userland_GNU kernel_linux elibc_glibc"
Unset:  ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY

Comment 1 Krzysztof Pawlik (RETIRED) gentoo-dev

2005-10-25 04:43:00 UTC

(In reply to comment #0)
> XIO: fatal error 104 (Connection reset by peer) on X xerver: ":0.0"
>      after 0 requests (0 known processed) with 0 events remaining.

> Actual Results:  
> xscreensaver causes fatal IO error
> 
> Expected Results:  
> xscreensaver should terminate correctly.

Try: `killall xscreensaver` then exit. That 'fatal error' is harmless.
xscreensaver just loses it's connection to X server.
For example:

xmodmap $HOME/.Xmodmap

#v+
gkrellm2 &
xscreensaver &

enlightenment

killall xcsreensaver
#v-