Ubuntu
ufw package

kontact crashed and then ufw

Bug #333104 reported by rottex on 2009-02-23

This bug report is a duplicate of: Bug #337705: ufw crashes in trigger on intrepid->jaunty upgrade. Edit Remove

Affects		Status	Importance	Assigned to	Milestone
	ufw (Ubuntu)	Incomplete	Undecided	Jamie Strandboge

Bug Description

Binary package hint: ufw

hm, just changed to ubuntu (former gentoo) and due to this bug I am aware now that ufw even exists :-) sorry no additional infos, it happened while configuring Kontact...

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/sbin/ufw
InterpreterPath: /usr/bin/python2.5
NonfreeKernelModules: nvidia
Package: ufw 0.27~r416-0ubuntu1
PackageArchitecture: all
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/python /usr/sbin/ufw allow 22/tcp
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, no user)
LANG=en_US.utf8
LANGUAGE=en_US.utf8
PythonArgs: ['/usr/sbin/ufw', 'allow', '22/tcp']
SourcePackage: ufw
Title: ufw crashed with ImportError in <module>()
Traceback:
Traceback (most recent call last):
File "/usr/sbin/ufw", line 25, in <module>
import ufw.frontend
ImportError: No module named ufw.frontend
Uname: Linux 2.6.28-7-generic x86_64
UserGroups:

Tags:

Revision history for this message

rottex (mro-rocam) wrote on 2009-02-23:

Dependencies.txt Edit (891 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (13.9 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (723 bytes, text/plain; charset="utf-8")

Revision history for this message

Jamie Strandboge (jdstrand) wrote on 2009-02-27:

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures . At a minimum, we need: 1. the specific steps or actions you took that caused you to encounter the problem, 2. the behavior you expected, and 3. the behavior you actually encountered (in as much detail as possible). Thanks!