testdrive UI becomes unresponsive after saving settings

Bug #1252402 reported by Daniel Kessel on 2013-11-18
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
TestDrive
High
Unassigned
testdrive (Ubuntu)
High
Unassigned

Bug Description

Using trusty:

Here's how I can produce the bug:

1. Select an ISO for syncing
2. Then choose Sync.
3. Open Settings.
4. Choose "Save".

Expected result: "Settings" dialog closes, main windows becomes responsive again.

Actual result: "Settings" stays open, save button stays in "pressed" position, main window stays unresponsive. The application is unusable from that point on. The only way to close it is killing it.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: testdrive-gtk 3.24-0ubuntu1
ProcVersionSignature: Ubuntu 3.12.0-2.7-generic 3.12.0
Uname: Linux 3.12.0-2-generic x86_64
ApportVersion: 2.12.6-0ubuntu1
Architecture: amd64
Date: Mon Nov 18 18:31:13 2013
InstallationDate: Installed on 2013-04-26 (205 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MarkForUpload: True
PackageArchitecture: all
SourcePackage: testdrive
UpgradeStatus: Upgraded to trusty on 2013-11-08 (10 days ago)

Daniel Kessel (dkessel) wrote :
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in testdrive (Ubuntu):
status: New → Confirmed
Nicholas Skaggs (nskaggs) wrote :

To reproduce:

Open testdrive
Open preferences menu, select settings
Press save button

Expected result, settings saved, main window reappears
Actual results, UI is frozen

Nicholas Skaggs (nskaggs) wrote :

Removing config files had no change on behavior. I removed /etc/testdriverc, ~/.testdriverc and ~/.config/testdrive/testdriverc

Daniel Kessel (dkessel) wrote :

terminal output:

/usr/bin/testdrive-gtk:190: Warning: /build/buildd/glib2.0-2.38.1/./gobject/gsignal.c:2475: signal 'child-added' is invalid for instance '0x180ac30' of type 'GtkMenu'
<dkessel> self.appindicator.set_menu(self.app_indicator_menu)

C de-Avillez (hggdh2) wrote :

marking Triaged/High -- testdrive becomes unusable until killed.

Changed in testdrive (Ubuntu):
importance: Undecided → High
status: Confirmed → Triaged
Jackson Doak (noskcaj) wrote :

That error appears at startup, i'm not sure if it's related. I can't reproduce the bug

Jackson Doak (noskcaj) on 2013-11-18
Changed in testdrive:
importance: Undecided → High
Jackson Doak (noskcaj) on 2014-01-22
Changed in testdrive:
status: New → Triaged
pawciobiel (pawciobiel) wrote :

I can not reproduce this bug. I tried Lubuntu 14.04 i86 and amd64 with testdrive development version. Chances are that this was fix already either in testdrive itself or gtk/glib/pygtk or it only fails in some certain configuration on Ubuntu.
 If this bug still appears It would be good if someone who came across it could write a bit more about her/his setup.

Daniel Kessel (dkessel) wrote :

I also cannot reproduce it anymore.
If you can recreate it, please report this here. I am marking the bug as incomplete now, so it will eventually disappear if no-one reports it anymore.

Changed in testdrive:
status: Triaged → Incomplete
Changed in testdrive (Ubuntu):
status: Triaged → Incomplete
Launchpad Janitor (janitor) wrote :

[Expired for testdrive (Ubuntu) because there has been no activity for 60 days.]

Changed in testdrive (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers