Ubuntu
lptools package

review-notifier crashed with TypeError in init(): init() takes at least 4 arguments (3 given)

Bug #734816 reported by madw0lf on 2011-03-14

This bug report is a duplicate of: Bug #730116: review-notifier crashed with TypeError in __init__(): __init__() takes at least 4 arguments (3 given). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	lptools (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: lptools

При старте системы многократно открывается nautilus, процесс не удается остановить и в это время появляются ошибки с апплетами и различными пакетами(в данном случае lptools). система была установлена 2 часа назад, примерно 1 час назад обновил и началось...

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: lptools 0.0.1~bzr9-1.1
ProcVersionSignature: Ubuntu 2.6.38-6.34-generic 2.6.38-rc7
Uname: Linux 2.6.38-6-generic i686
Architecture: i386
Date: Mon Mar 14 15:36:39 2011
ExecutablePath: /usr/bin/review-notifier
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110302)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/review-notifier
ProcEnviron:
LANGUAGE=ru_RU:en
LANG=ru_RU.UTF-8
SHELL=/bin/bash
PythonArgs: ['/usr/bin/review-notifier']
SourcePackage: lptools
Title: review-notifier crashed with TypeError in __init__(): __init__() takes at least 4 arguments (3 given)
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags:

Revision history for this message

madw0lf (madw0lf) wrote on 2011-03-14:

Traceback.txt Edit (281 bytes, text/plain; charset="utf-8")

Revision history for this message

madw0lf (madw0lf) wrote on 2011-03-14:

попытки запустить наутилус в консоли и остановить его привели только к торможению процесса, но он всё равно продолжает постоянно запускаться
madw0lf@madw0lf-testlab:~$ nautilus

(nautilus:2343): Unique-DBus-WARNING **: Error while sending message: Message did not receive a reply (timeout by message bus)

(nautilus:2343): Unique-DBus-WARNING **: Error while sending message: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(nautilus:2343): GLib-GIO-CRITICAL **: g_bus_unwatch_name: assertion `watcher_id > 0' failed
madw0lf@madw0lf-testlab:~$ nautilus

(nautilus:3273): Unique-DBus-WARNING **: Error while sending message: Message did not receive a reply (timeout by message bus)
^Z
[1]+ Остановлено nautilus
madw0lf@madw0lf-testlab:~$ nautilus

(nautilus:3355): Unique-DBus-WARNING **: Error while sending message: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(nautilus:3355): GLib-GIO-CRITICAL **: g_bus_unwatch_name: assertion `watcher_id > 0' failed
madw0lf@madw0lf-testlab:~$ nautilus
^Z
[2]+ Остановлено nautilus
madw0lf@madw0lf-testlab:~$

Revision history for this message

Apport retracing service (apport) wrote on 2011-03-17: 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 #730116, 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.