popper.py: Fatal IO error 11 on Ubuntu Natty

Bug #793152 reported by Jean Thusek
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Popper
Invalid
Undecided
Unassigned

Bug Description

After installing popper 0.28 from PPA, popper does not automatically start on login though it has added an autostart entry.
The log-file shows the following line:
popper.py: Fatal IO error 11 (Die Ressource ist zur Zeit nicht verfügbar) on X server :0.

When starting the Configurator, the autostart checkbox is also active and clicking "save+exit" starts popper correctly.

---------------- UPDATE ----------------
When I comment out lines 11-21 of the /usr/share/popper/popper.sh it starts correctly after logging in. So my script looks like this:

#!/bin/bash
main()
{
if [ -f ~/.popper/popper.log ]; then
 rm ~/.popper/popper.log
fi
cd `dirname $0`
python popper.py autostarted >> ~/.popper/popper.log 2>&1 &
}

#connection()
#{
#trap "exit 1" SIGTERM
#while ! ping -c1 www.google.com 2>/dev/null 1>&2
# do
# sleep 4.2 # The answer to life, the universe and everything :-)
# done
#kill %-
#}
#
#connection
main

description: updated
description: updated
Revision history for this message
Ralf Hersel (ralf.hersel) wrote :

Hi Jean
The part of the popper.sh that you commented out, checks if you are online before Popper is started. This is no magic and should not provoke this error. If you google for "Fatal IO error 11" you will maybe find the reason why this happens. This has nothing to do with Popper.

Changed in popper:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.