When unmounting a removable media using Thunar or places-plugin, a popup comes up to tell me that there is some data to be written before I can safely remove the media. This popup window has an ok and a cancel button, but both are only closing the popup. You can't stop unmounting or cd ejection by clicking cancel, so I think the cancel button shouldn't be there at all.
Is this on Ubuntu or Xubuntu? In that case, there is nothing we can do as they modify the way notifications are shown. In particular, they display some notifications as dialogs and those are probably the ones with the cancel button you mentioned.
Created attachment 4236 Screenshot of popup window I'm using Xubuntu. So this means I have to report this bug on launchpad?
Yes, please do. I am not sure what causes the notification dialog to have a cancel button and which product to report this against though (notify-osd perhaps).
On launchpad I was told: Moving the issue to thunar, as this is a thunar bug, as notify OSD in case of notifications with multiple possible actions falls back to dialog boxes. Quoting from the NotifyOSD specifications : "If actions is supplied and/or expire_timeout is set to “0”, the notification should be presented as a fallback alert box". So Thunar should set a non-0 expire timeout and should not supply any possible actions. http://bugs.launchpad.net/thunar/+bug/941023
(fwiw, Xubuntu uses xfce4-notifyd by default) As I wrote on launchpad, it's not really a bug, rather a design decision from notify-osd that conflicts with the current thunar design for eject/unmount notifications. ;-) If you want to play with it, you can still find on launchpad the patch we applied to exo in 2009 when we tried to use notify-osd (http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/karmic/exo/karmic/view/head:/debian/patches/xubuntu-expire-notifications.patch).
> As I wrote on launchpad, it's not really a bug, rather a design decision from notify-osd that conflicts with the current thunar design for eject/unmount notifications. ;-) Only happens with notify-osd due to design decisions. Using xfce4-notifyd solves this. This bug was left untouched for 3 years, so I'm closing it. Feel free to reopen if needed.