Theme is sometimes left in an inconsistent state on first start of a new install
Bug #877601 reported by
marmuta
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
onboard (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Oneiric |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Sometimes on first start onboard's theme is partially reset, leaving it in a visually unpleasant state. This corrects itself on the following start, but can be repeated occasionally by resetting onboards gsettings schema with
gsettings reset-recursive apps.onboard.
tags: |
added: verification-done removed: verification-needed |
To post a comment you must log in.
Causing this are unexpected gsettings change events, coming in after onboard's initialization is done. Some events of keys onboard touches are expected on first start, but here each and every one onboard subscribes too is fired.
This happens rather frequently when first-time auto-starting onboard in unity2d, but can be reproduced occasionally when resetting the schema in the user session. Attached is a log that shows this happening in 2 out of 32 tries.
The root cause is unknown, and I have no simple test case yet for a bug report against glib.