After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 677285 - Unable to dismiss "Open with Files or Eject" notification
Unable to dismiss "Open with Files or Eject" notification
Status: RESOLVED DUPLICATE of bug 660609
Product: gnome-shell
Classification: Core
Component: general
unspecified
Other Linux
: Normal minor
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2012-06-01 15:03 UTC by yurividal
Modified: 2012-07-10 20:30 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description yurividal 2012-06-01 15:03:55 UTC
Im not sure if this is realy from notification-daemon. But, here it goes:

When I plug my external hard drive in, at the bottom of the screen I receive an option to either; Open with Files or Eject. 
How do I get rid of this? As if I choose to open with files, it opens the already opened windows, but if I choose eject it removes the that partition of the hard drive, and there is no option to ignore.

There is no way of getting rid of the notification without unmounting the drive or opening a nautilus window. There shoould be a "do nothing" or "ignore" option.
Thanking you!
Comment 1 André Klapper 2012-06-02 08:14:02 UTC
Please provide information about versions, distribution, etc... Thanks!
Comment 2 malacusp 2012-07-09 09:23:20 UTC
I, too, would like a dismiss button on this notification dialog.
It does time out eventually but it is very annoying having it hanging around the bottom of the screen until it does.

Ubuntu Release 12.04 (precise) 32-bit
Kernel Linux 3.2.0-26-generic
GNOME 3.4.1
Comment 3 Florian Müllner 2012-07-10 20:30:17 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 660609 ***