File emblems don't display correct sync status
Bug #479475 reported by
Joshua Hoover
This bug affects 12 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu One Client |
Fix Released
|
Medium
|
Roman Yepishev | ||
ubuntuone-client (Ubuntu) |
Triaged
|
Medium
|
Unassigned | ||
Bug Description
Copying a 50 MB file to ~/Ubuntu One results in the file getting an immediate emblem of a green check mark, which is meant to represent files that are synchronized. Another test is copying a folder with five mp3 files (folder size of 26 MB) to ~/Ubuntu One and the folder and files all have the green check mark right away. This is happening on Karmic as well as Jaunty (r273)
Related branches
lp://staging/~rye/ubuntuone-client/add-marshallers
- dobey (community): Approve
-
Diff: 73 lines (+35/-0)3 files modifiednautilus/Makefile.am (+10/-0)
nautilus/ubuntuone-marshallers.list (+4/-0)
nautilus/ubuntuone-nautilus.c (+21/-0)
lp://staging/~rye/ubuntuone-client/bring-emblems-back
- John O'Brien (community): Approve
- dobey (community): Approve
-
Diff: 33 lines (+8/-1)1 file modifiednautilus/ubuntuone-nautilus.c (+8/-1)
Changed in ubuntuone-client (Ubuntu): | |
status: | New → Triaged |
assignee: | nobody → Rodney Dawes (dobey) |
tags: | added: nautilus-emblems |
Changed in ubuntuone-client (Ubuntu): | |
importance: | Undecided → Medium |
Changed in ubuntuone-client: | |
assignee: | Rodney Dawes (dobey) → Roman Yepishev (rye) |
status: | Triaged → Fix Released |
Changed in ubuntuone-client (Ubuntu): | |
assignee: | Rodney Dawes (dobey) → nobody |
To post a comment you must log in.
The 'synchronized' emblem is added immediately and not updated later.
Here are the messages from Nautilus when an attempt is made to browse Ubuntu One directory.
UbuntuOne- Nautilus- Message: rtg: Add the synchronized emblem anyway
(nautilus:20793): GLib-GObject- CRITICAL **: g_type_ instance_ get_private: assertion `instance != NULL && instance->g_class != NULL' failed
** (nautilus:20793): CRITICAL **: dbus_g_ proxy_begin_ call: assertion `DBUS_IS_G_PROXY (proxy)' failed