gnome-clocks crashed with NameError in <lambda>(): free variable 'about' referenced before assignment in enclosing scope

Bug #1049921 reported by mastaiza
24
This bug affects 3 people
Affects Status Importance Assigned to Milestone
gnome-clocks (Ubuntu)
Expired
Medium
Unassigned

Bug Description

ups

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: gnome-clocks 0.1.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-14.16-generic 3.5.3
Uname: Linux 3.5.0-14-generic i686
ApportVersion: 2.5.1-0ubuntu7
Architecture: i386
Date: Wed Sep 12 22:52:41 2012
ExecutablePath: /usr/bin/gnome-clocks
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120724.2)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gnome-clocks
ProcEnviron:
 PATH=(custom, no user)
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/gnome-clocks']
SourcePackage: gnome-clocks
Title: gnome-clocks crashed with NameError in <lambda>(): free variable 'about' referenced before assignment in enclosing scope
Traceback:
 Traceback (most recent call last):
   File "/usr/lib/python2.7/dist-packages/gnomeclocks/app.py", line 148, in <lambda>
     about.connect("response", lambda w, r: about.destroy())
 NameError: free variable 'about' referenced before assignment in enclosing scope
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
mastaiza (mastaiza) wrote :
tags: removed: need-duplicate-check
Changed in gnome-clocks (Ubuntu):
importance: Undecided → Medium
visibility: private → public
Revision history for this message
Sasa Paporovic (melchiaros) wrote :

Hi mastaiza,

please give a step by step description like pushing this button, choosing that, waiting for, and so on). Give a good algorithmic description, that is complete and can guide a beginner in <Program> to the point where the problem happends.

(step1,
 step2,
.
.
.
finished)

After that set the status of this report back to new.

Thanks

-------------------------------------------

A stacktrace alone is unfortunally not enough. gnome-clock is in universe repositories and with this we need to bring it upstream to the original developers. In commen they reject reports without a reproducing procedure, so ... give your best.

greetings

melchiaros

Changed in gnome-clocks (Ubuntu):
status: New → Incomplete
Revision history for this message
Anton (tosha-korneev) wrote :

Hi melchiaros,

to reproduce the crash:
1. open "About Clocks" dialog
2. click "Close" button

Cheers,
Anton

Changed in gnome-clocks (Ubuntu):
status: Incomplete → New
Revision history for this message
Paul White (paulw2u) wrote :

We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.

Ubuntu 12.10 (quantal) reached end-of-life on May 16, 2014.

This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue using a maintained version of Ubuntu then please let us know otherwise this report can be left to expire in approximately 60 days time.

Paul White
[Ubuntu Bug Squad]

Changed in gnome-clocks (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in gnome-clocks (Ubuntu):
status: Incomplete → Expired
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.