OneConf synchronous networking delays USC launching
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
oneconf (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Binary package hint: oneconf
oneconf 0.1.1, software-center 2.1.19, Ubuntu Maverick
1. With oneconf installed, enter the terminal command "trickle -d 1 software-center".
What should happen: Ubuntu Software Center launches.
What actually happens: Nothing.
The problem occurs only if oneconf is installed.
Pressing Ctrl C produces this traceback:
^CTraceback (most recent call last):
File "/usr/bin/
app = SoftwareCenterA
File "/usr/share/
self.
File "/usr/share/
module = self._load_
File "/usr/share/
(".py", "r", imp.PY_SOURCE))
File "/usr/share/
from oneconf.dbusconnect import DbusConnect
File "/usr/share/
from oneconf.hosts import Hosts, HostError
File "/usr/share/
from desktopcouch.
File "/usr/lib/
from desktopcouch.
File "/usr/lib/
from desktopcouch import local_files
File "/usr/lib/
xdg_
File "/usr/lib/
self.
File "/usr/lib/
line = process.
KeyboardInterrupt
right, OneConf is starting async apart from the first critical part when the main pluging load. So, when it's import DbusConnect, it's starting, it's starting beam.smp as well, which can takes time.
So, this import should just be delayed in a thread so that beam.smp intialize in non blocking mode. Tricky and not maverick, but worth investigating it.
An another solution is that desktopcouch initialize in non blocking mode and give a callback once ready…