extra dbus timeout error displayed when an unmount error dialog stay on screen
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gvfs |
Expired
|
Medium
|
|||
gnome-mount (Ubuntu) |
Invalid
|
Low
|
Ubuntu Desktop Bugs |
Bug Description
Binary package hint: notify-osd
Normally one message is ok, two message for one action with different names is spam.
If you tray to unmount volume and get one error, there is no need to notify user with one more error about the last error:
1. Message: Cannot unmount volume / An application is preventing the volume "kingstone" from being unmounted.
2. Message come after about 10sec: Unable to unmount kingstone / DBus error org.freedesktop
With other words second message will say "user filed. please restart the user and try again".
lsb_release -rd
Description: Ubuntu jaunty (development branch)
Release: 9.04
affects: | gnome-mount (Ubuntu) → gvfs (Ubuntu) |
Changed in gvfs (Ubuntu): | |
status: | Incomplete → Confirmed |
summary: |
- User spammed with messages: 1. Cannot unmount volume; 2. Unable to - unmount kingstone + extra dbus timeout error displayed when an unmount error dialog say on + screen |
summary: |
- extra dbus timeout error displayed when an unmount error dialog say on + extra dbus timeout error displayed when an unmount error dialog stay on screen |
Changed in gvfs: | |
status: | Unknown → New |
Changed in gvfs: | |
status: | New → Incomplete |
Changed in gvfs: | |
importance: | Unknown → Medium |
Changed in gvfs: | |
status: | Incomplete → Expired |
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?
This will help us to find and resolve the problem.