Awn

New docks added via awn-settings are unable to be moved to separate screen area without moving primary dock with it

Bug #1247772 reported by Ifeoluwapo Eleyinafe on 2013-11-04
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Awn
High
Unassigned

Bug Description

Youtube link showing error: http://youtu.be/7n_tGwJHYl8

awn-settings 0.4.1~git20131104-ppa2 with requisite avant-window-navigator and avant-window-navigator-data.

I've repeated tried adding a new dock via awn-settings. Upon running awn-settings from terminal the following appears:

** (awn-settings:25662): CRITICAL **: desktop_agnostic_config_schema_get_metadata_option: assertion 'self != NULL' failed

** (awn-settings:25662): CRITICAL **: desktop_agnostic_config_new_for_instance: assertion 'schema != NULL' failed

Making a new panel repeats the error:

** (awn-settings:25662): CRITICAL **: desktop_agnostic_config_schema_get_metadata_option: assertion 'self != NULL' failed

** (awn-settings:25662): CRITICAL **: desktop_agnostic_config_new_for_instance: assertion 'schema != NULL' failed

Attempting to move the new dock to a different position on the screen moves the old dock with it. Hence both the old and new dock are recognized as the same dock. Please let me know if further clarification is required.

Creation of new dock via gconf-editor results in similar error.

Povilas Kanapickas (p12) on 2013-11-04
Changed in awn:
importance: Undecided → High
status: New → Confirmed
status: Confirmed → Triaged
Povilas Kanapickas (p12) on 2013-11-05
tags: added: multiple-docks
summary: - New panels added via awn-settings are unable to be moved to separate
- screen area without moving primary panel with it
+ New docks added via awn-settings are unable to be moved to separate
+ screen area without moving primary dock with it
description: updated
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers