udev-notify

Crash on resume from suspend

Bug #785773 reported by nerdy_kid on 2011-05-20

38

This bug affects 6 people

Affects		Status	Importance	Assigned to	Milestone
	udev-notify	Confirmed	Medium	lokster

Bug Description

to reproduce: Run udev-notify from a terminal. Suspend the computer, and upon resume you are met with:

Traceback (most recent call last):
  File "./udev-notify.py", line 303, in <module>
    for action, device in monitor:
  File "/usr/share/udev-notify/pyudev/monitor.py", line 250, in __iter__
    events = notifier.poll()
IOError: [Errno 4] Interrupted system call

lokster (lokiisyourmaster) on 2011-05-20

Changed in udev-notify:
importance:	Undecided → Medium
status:	New → Confirmed
assignee:	nobody → lokster (lokiisyourmaster)

Revision history for this message

Alekseev Konstantin (bojak91) wrote on 2012-02-03:

#1

_usr_share_udev-notify_udev-notify.py.1000.crash Edit (47.6 KiB, text/plain)

I have this problem too

Changed in udev-notify:
status:	Confirmed → Incomplete
status:	Incomplete → Confirmed

Revision history for this message

mtvoid (mtvoid) wrote on 2012-07-12:

#2

Handle IOError exception on resume from suspend in __iter__ method in monitor.py Edit (785 bytes, text/plain)

Adding code to handle the IOError exception, as in my attached patch, should take care of the problem.

Report a bug

This report contains Public information

Everyone can see this information.

Duplicates of this bug

You are

Subscribing...

Edit bug mail

Other bug subscribers

Patches

Handle IOError exception on resume from suspend in __iter__ method in monitor.py Edit

Add patch

Bug attachments

_usr_share_udev-notify_udev-notify.py.1000.crash Edit

Add attachment

Remote bug watches

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