Ubuntu
entangle package

/usr/bin/entangle:11:do_refresh_control_entry_idle:g_main_dispatch:g_main_context_dispatch:g_main_context_iterate:g_main_context_iteration

  1. Bionic (18.04)
  2. Bug #1739503
Bug #1739503 reported by errors.ubuntu.com bug bridge
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
entangle (Ubuntu)
Invalid
Undecided
Unassigned
Bionic
Triaged
Undecided
Unassigned
Focal
Invalid
Undecided
Unassigned
Impish
Invalid
Undecided
Unassigned
Jammy
Invalid
Undecided
Unassigned

Bug Description

The Ubuntu Error Tracker has been receiving reports about a problem regarding entangle. This problem was most recently seen with package version 0.7.1-1build1, the problem page at https://errors.ubuntu.com/problem/d7e01aa7ed812d6ff01ca5d17f53f9fff78b2f2d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/.

Revision history for this message
Erich Eickmeyer (eeickmeyer) wrote :

Users still experiencing this should consider upgrading to 20.04 LTS at minimum since it contains a newer version of entangle that does not experience this issue.

Changed in entangle (Ubuntu Bionic):
status: New → Triaged
Changed in entangle (Ubuntu Focal):
status: New → Invalid
Changed in entangle (Ubuntu Impish):
status: New → Invalid
Changed in entangle (Ubuntu Jammy):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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