apturl-gtk crashed with TypeError in __init__(): __init__() takes exactly 3 arguments (2 given)
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| apturl (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Attempted to install Folder sharing services by going through the nautilus/gnome gui.
Steps to reproduce:
1. In Nautilus: right-click a folder icon
2. Select 'Sharing Options'
3. Check 'Share this Folder'
4. See "sharing services not install dialog"
5. Click "Install Service"
Result:
Fault occurs, both "sharing service failed to install" and "Sorry Ubuntu has experiences and internal error" dialogs display...
Expected:
Service must install and user must be able to share folder(s) over network.
Thanks in advance.
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: apturl 0.5.1ubuntu5
ProcVersionSign
Uname: Linux 3.5.0-4-generic x86_64
ApportVersion: 2.3-0ubuntu4
Architecture: amd64
Date: Wed Jul 11 12:52:42 2012
ExecutablePath: /usr/bin/apturl-gtk
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120627)
InterpreterPath: /usr/bin/
ProcCmdline: /usr/bin/python3 /usr/bin/apturl-gtk apt:samba,
ProcEnviron:
LANGUAGE=en_NZ:en
PATH=(custom, no user)
LANG=en_NZ.UTF-8
SHELL=/bin/bash
PythonArgs: ['/usr/
SourcePackage: apturl
Title: apturl-gtk crashed with TypeError in __init__(): __init__() takes exactly 3 arguments (2 given)
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
| Matthew McGowan (mmcg069) wrote | #1 |
| description: | updated |
| description: | updated |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| tags: | removed: need-duplicate-check |
| visibility: | private → public |
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1020980, 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.