Ubuntu One crashes nautilus window when sharing folder
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntuone-client (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: ubuntuone-client
On my x64 Karmic install Ubuntu One randomly crashes when attempting to share folder to someone. To reproduce:
1. Navigate to Ubuntu One folder (Places -> Ubuntu One). Create a folder there. Close Ubuntu One folder. You may also wish to drop a file into newly created subfolder.
2. Go to Places -> Ubuntu One
3. Right-click on the folder you have created in step 1 and select "share on Ubuntu One". If the window does not crash right away you will be presented with the dialogue box prompting you for email and share name. If the share name field is filled out with the name of the folder you are sharing, then click cancel, close Ubuntu One window and repeat from step 2 until you get blank share name field or it is filled out with something different from the folder name that you are sharing. Once this is the case, click "Share" and the nautilus window will crash and Ubuntu One will stay disconnected.
There is also no indication on the folder icon that it is shared, and no way to know to whom it is shared with on Ubuntu One from within nautilus.
ProblemType: Bug
.home.onair24.
2009-12-03 17:41:17,966 - ubuntuone.
2009-12-04 11:06:42,061 - ubuntuone.
.home.onair24.
[ubuntuone]
connected = True
connect = 0
show_applet = 1
bookmarked = True
Architecture: amd64
CheckboxSubmission: 84636f17fa3181c
CheckboxSystem: b8f3ec504801f13
Date: Fri Dec 4 11:14:40 2009
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1)
NonfreeKernelMo
Package: ubuntuone-
ProcEnviron:
LANG=ru_RU.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: ubuntuone-client
Uname: Linux 2.6.31-15-generic x86_64
Hi Lex,
I'm sorry to hear Ubuntu One is crashing Nautilus for you. I'm running the same version of Ubuntu One (1.0.2-0ubuntu2) on Karmic and was not able to reproduce the bug following the steps you provided. I tried repeating the steps at least ten times without seeing the results you described. Are you able to do this consistently?
Thank you,
Joshua