doesn't yield thread-control to gtk.mainloop()

Bug #819820 reported by mokrates on 2011-08-02
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
inotifyx (Ubuntu)
Undecided
Unassigned

Bug Description

I wrote a small indicator program for my own use, which in the main-thread starts the gtk.main() (yes, after calling gtk.gdk.threads_init())
In another thread, i watch a directory for changes using inotifyx.get_events(), which doesn't seem to yield the thread-control back to the mainloop, which i infer by the fact, that the mainloop doesn't come to paint the UI, or only partly. When I switched from inotifyx to polling and time.sleep() everything worked. But polling is not as nice.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: python-inotifyx 0.1.1-1build1
ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7
Uname: Linux 2.6.38-10-generic i686
NonfreeKernelModules: wl
Architecture: i386
Date: Tue Aug 2 15:32:55 2011
InstallationMedia: Ubuntu-Netbook-Remix 9.10 "Karmic Koala" - Release i386 (20091028.4)
ProcEnviron:
 LC_TIME=de_DE.UTF-8
 LANGUAGE=en_US:en
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: inotifyx
UpgradeStatus: Upgraded to natty on 2011-04-28 (95 days ago)

mokrates (mmolle) wrote :
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in inotifyx (Ubuntu):
status: New → Confirmed
ejvos (ejvos) wrote :

I experienced similar behaviour (Debian Squeeze, same package version 0.1.1), get_events() blocking entire Python process, this seems to be fixed in v0.1.2 and up (Oneiric, Precise).

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers