Merge lp:~stgraber/ubiquity/ubiquity-dconf into lp:ubiquity
Status: | Merged |
---|---|
Merged at revision: | 5397 |
Proposed branch: | lp:~stgraber/ubiquity/ubiquity-dconf |
Merge into: | lp:ubiquity |
Diff against target: |
87 lines (+21/-4) (has conflicts) 3 files modified
bin/ubiquity-dm (+8/-1) debian/changelog (+10/-0) ubiquity/gsettings.py (+3/-3) Text conflict in debian/changelog |
To merge this branch: | bzr merge lp:~stgraber/ubiquity/ubiquity-dconf |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Ubuntu Installer Team | Pending | ||
Review via email: mp+102684@code.launchpad.net |
Description of the change
11:38 < stgraber> cjwatson: I'm really not too happy about my last gsettings change (running in dbus-launch), we end up with ~10-15 dbus-daemon + dbus-launch running at the end
11:38 < stgraber> each of them with their own dconf-writer running, even though that "works" (AFAICT), I feel like I need to clean that up a little
11:39 < cjwatson> where was that change?
11:40 < stgraber> I think the root of the gsettings issue is that dconf-writer doesn't get killed properly and so doesn't dump its changes to disk, instead I think we should try
11:40 < stgraber> cjwatson: r5356 in ubiquity/
11:40 < stgraber> essentially a workaround for bug 960096
11:41 < ubot2> Launchpad bug 960096 in libxklavier "Live session started with wrong layout" [Medium,Confirmed] https:/
11:42 < cjwatson> do you think it's RC? I agree it's not particularly elegant, but ...
11:43 < cjwatson> maybe a branch staged for Q
11:43 < stgraber> yeah, I haven't seen any report of it blowing up, though I can't see how 10 dconf-writer running and writing to the same binary DB could be a good thing