nicotine crashed with TypeError in OnNetworkEvent()

Bug #440094 reported by Apteryx
This bug report is a duplicate of:  Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nicotine (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: nicotine

1) Ubuntu 9.10 karmic
2) 1.2.12+dfsg-1ubuntu1
3) Expect it to return the results of the query without crashing.
4) Crashed after doing a query.

This bug is reproducible. Just open Nicotine and search for a popular term.
The apport-bug pops-up saying nicotine had a problem, but after clicking close, Nicotine is still there, unaffected, as it seems.

Was marked to a bug which I don't have access to the page, so I am reporting this here.

ProblemType: Crash
Architecture: amd64
Date: Thu Oct 1 12:25:24 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nicotine
InterpreterPath: /usr/bin/python2.6
NonfreeKernelModules: nvidia
Package: nicotine 1.2.12+dfsg-1ubuntu1
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/nicotine
ProcEnviron:
 LANGUAGE=fr_CA.UTF-8
 LANG=fr_CA.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
PythonArgs: ['/usr/bin/nicotine']
SourcePackage: nicotine
Title: nicotine crashed with TypeError in OnNetworkEvent()
Traceback:
 Traceback (most recent call last):
   File "/usr/lib/pymodules/python2.6/pynicotine/gtkgui/frame.py", line 1539, in OnNetworkEvent
     self.logMessage("No handler for class %s %s" % (i.__class__, vars(i)))
 TypeError: vars() argument must have __dict__ attribute
Uname: Linux 2.6.31-11-generic x86_64
UserGroups: adm admin cdrom fax fuse lp lpadmin plugdev sambashare sshlogin vboxusers

Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #231401, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

tags: removed: need-duplicate-check
visibility: private → public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
  • Duplicate of a private bug Remove

Other bug subscribers

Remote bug watches

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