Download your favorite Linux distribution at LQ ISO.
Go Back > Forums > Linux Forums > Linux - Software
User Name
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.


  Search this Thread
Old 10-28-2008, 12:08 PM   #1
Registered: May 2007
Posts: 33

Rep: Reputation: 15
ICE default IO error handler doring an exit (), pid = [knotify], errono = 0

I log in as a regular user. I click "yes" to my (recently added)kdialog 'monitoring' warning. I open an xterm window. I'm golden.

Then I su - so I can do some admin work. Sometimes I get kbuildsycom is cleaning dead connections., sometimes not. Then within 10 seconds of becoming root I get this ICE default error.

I have searched high and low for the correction for this error. I have seen it listed many times on google but there does not seem to be any solutions. The pid in the ICE error turns out to be "knotify" which I can only assume is part of kde. I am a Solaris and HP unix person. Red Hat Linux Enterprise WS 4.6 and ES 4.5 are what we use.

Our preferred desktop=kde. I just installed the only 2 kde packages not installed from our cd, which were kdeaddons and kdeartwork, which did nothing (as expected) to solve this.

Thinking that it might be related to .ICE-unix in /tmp, I checked the owner, group and perms. Sticky bit is set on the .ICE-unix directory. I read a google post about maybe .ICE-unix sockets were not setup correctly. So I followed the post's advice and as root, I deleted the /tmp/.ICE-unix directory (-Rf), logged out and logged back in as root so root would create the /tmp/.ICE-unix directory.

I logged out and logged back in as a regular user and su -. Within a few seconds I get that annoying ICE default error. So the delete /tmp/.ICE-unix directory did not work for me.

We added that kdialog to satisfy government requirements to tell folks that they are being monitored when they login or su. We considered/tried zenity and xdialog for this process but found them clunky. Since our desktop is kde, we wanted to stay with kdialog. Not even sure that this kdialog has anything to do with the problem but I don't recall seeing this error until after we started using kdialog.

we are running a fully patched kde 3.3.

Has anybody else had this problem? I appreciate your opinions and advice.

Last edited by legcard; 10-28-2008 at 12:19 PM. Reason: more troubleshooting
Old 10-28-2008, 12:25 PM   #2
Registered: May 2007
Posts: 33

Original Poster
Rep: Reputation: 15
It is the kdialog

I don't know why I didn't try this before posting but I deleted those lines associated with the kdialog in the /etc/profile file and the problem not longer exists. Well, no exactly. Now I have to figure out what I did wrong in the kdialog portion of the /etc/profile that causes the ICE default error. I have included the /etc/profile so you can see the portion that has the kdialog.

Is there anything glaringly wrong?

Thanks again.

# /etc/profile

# System wide environment and startup programs, for login setup
# Functions and aliases go in /etc/bashrc

pathmunge () {
if ! echo $PATH | /bin/egrep -q "(^|$1($|" ; then
if [ "$2" = "after" ] ; then

# Path manipulation
if [ `id -u` = 0 ]; then
pathmunge /sbin
pathmunge /usr/sbin
pathmunge /usr/local/sbin

pathmunge /usr/X11R6/bin after

# No core files by default
ulimit -S -c 0 > /dev/null 2>&1

USER="`id -un`"


if [ -z "$INPUTRC" -a ! -f "$HOME/.inputrc" ]; then


if [ "$DISPLAY" != "" ]; then

/usr/bin/kdialog --title "Consent Banner and User agreement" --yesno \
"######################################################################### \n
# You are accessing a U.S. Government (USG) information system \n
# (IS) that is provided for USG-authorized use only. \n
# \n
# By using this IS (which includes any device attached to this IS), \n
# you consent to the following conditions: \n
# \n
# - The USG routinely intercepts and monitors communications on this IS \n
# for purposes including, but not limited to, penetration testing, \n
# COMSEC monitoring, network operations and defense, personnel \n
# misconduct (PM), law enforcement (LE), and counterintelligence \n
# (CI) investigations.\n
# \n
# - At any time, the USG may inspect and seize data stored on this IS \n
# \n
# - Communications using, or data stored on, this IS are not private, \n
# are subject to routine monitoring, interception, and search, and \n
# any device attached to this IS, may be disclosed or used fo \n
# any USG-authorized purpose. \n
# \n
# - This IS includes security measures (e.g., authentication and access \n
# controls) to protect USG interests -- not for your personal benefit or \n
# privacy. \n
Do you accept this login policy? "

if [ "$?" != "0" ]; then

for i in /etc/profile.d/*.sh ; do
if [ -r "$i" ]; then
. $i

unset i
unset pathmunge


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
ICE default IO error handler doing an exit(), pid = 15179, errno = 0 FirstBorn Linux - General 2 11-20-2014 11:38 AM
signal SIGINT handler SOMETIMES doesn't exit Peterius Programming 3 05-25-2008 11:55 PM
Postfix error: /usr/lib/postfix/smtpd pid 7529 exit status 1 Chiragrs Linux - Networking 7 05-16-2008 12:42 AM
ICE default IO error handler - mythfilldatabase Sfpiano Linux - Software 1 01-19-2007 12:02 AM
Mutex Destroy Failure / ICE default IO error SirSlappy Linux - General 0 02-01-2005 07:55 PM > Forums > Linux Forums > Linux - Software

All times are GMT -5. The time now is 11:50 PM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration