Onboard settings and scanning problem

Bug #1699844 reported by Valentina
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Onboard
Fix Committed
High
Unassigned
onboard (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I´ve configured scanning option on onboard.
In Version 0.97 there was a bug that doesn´t open keyboard with such configuration
In this version (1.4.1) i´m trying to open onboard-settings and it gives me the error:

Traceback (most recent call last):
  File "<string>", line 2, in <module>
  File "/usr/lib/python3/dist-packages/Onboard/settings.py", line 311, in __init__
    builder = LoadUI("settings")
  File "/usr/lib/python3/dist-packages/Onboard/settings.py", line 71, in LoadUI
    builder.add_from_file(os.path.join(config.install_dir, filebase+".ui"))
  File "/usr/lib/python3/dist-packages/gi/types.py", line 43, in function
    return info.invoke(*args, **kwargs)
gi._glib.GError: /usr/share/onboard/settings.ui:2126:1 <object> requires attribute "id"

Revision history for this message
marmuta (marmuta) wrote :

Thanks for the bug report. I believe this issue has a fix in trunk, see
https://bazaar.launchpad.net/~onboard/onboard/trunk/revision/2264
and
https://bazaar.launchpad.net/~onboard/onboard/trunk/revision/2265

What Ubuntu version are you running, and did you install Onboard 1.4.1 from our PPA?

Changed in onboard:
importance: Undecided → High
Revision history for this message
Valentina (vparu) wrote :

I´ve tried in Ubuntu 12.04 and ubuntu 14.04.
The installation was made from the ppa.

Revision history for this message
Francesco Fumanti (frafu) wrote :

You did probably install Onboard from our Stable PPA, which does not include the fix yet. Could you please try the Onboard version from our Snapshots PPA, which includes the fixes marmuta cited above?
https://launchpad.net/~onboard/+archive/ubuntu/snapshots

Revision history for this message
Valentina (vparu) wrote :

Francesco is right, installing Onboard with the fix (and not from the stable PPA) works fine!

Thanks you

Revision history for this message
marmuta (marmuta) wrote :

Thank you, for testing.

Changed in onboard:
status: New → Fix Committed
Changed in onboard (Ubuntu):
status: New → Invalid
Revision history for this message
Mattie Daniels (mattiedaniels) wrote :

The error message you're encountering indicates a problem with the settings.ui file of Onboard, specifically related to an attribute "id" that seems to be missing or incorrectly defined on line 2126. This issue typically arises from mismatches or errors in the XML definition of the UI file.

Here are steps you can take to address this problem:

    Check the settings.ui file: Navigate to /usr/share/onboard/ and locate the settings.ui file. Open it using a text editor or an XML editor that supports UI definition files.

    Inspect line 2126: Go to line 2126 in settings.ui and examine the XML code around that line. Look for any <object> elements and ensure they have an id attribute specified correctly.

    Correct the XML syntax: If the id attribute is missing or incorrectly defined, correct it according to the correct syntax for GTK UI files. An example of a properly defined object in GTK XML might look like this:

    xml

<object class="GtkLabel" id="label1">
  <property name="label" translatable="yes">Label Text</property>
</object>

Ensure your id attribute follows similar conventions and is unique within the scope of the UI file.

Validate the XML: After making corrections, validate the XML file to ensure there are no syntax errors. This can be done using an XML validator or simply by checking for any obvious syntax mistakes (unclosed tags, incorrect attribute values, https://nbiclearancesonline.com/ etc.).

Restart Onboard: Once you've saved the corrected settings.ui file, restart the Onboard application to see if the issue is resolved. Sometimes, changes to UI files may require a restart to take effect.

Update or reinstall Onboard: If the problem persists and you suspect a more fundamental issue with the application installation or configuration, consider updating Onboard to the latest version available for your system. Alternatively, reinstalling Onboard can sometimes resolve persistent UI-related issues.

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.