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 579873 - Need a way to disable notifications
Need a way to disable notifications
Status: RESOLVED OBSOLETE
Product: gnome-disk-utility
Classification: Core
Component: notifications
unspecified
Other Linux
: Normal enhancement
: ---
Assigned To: gnome-disk-utility-maint
gnome-disk-utility-maint
: 587459 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-04-22 19:00 UTC by David Zeuthen (not reading bugmail)
Modified: 2012-11-12 20:45 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description David Zeuthen (not reading bugmail) 2009-04-22 19:00:43 UTC
We need a way to disable notifications on a per-disk basis. There are some thoughts about it here

 https://bugzilla.redhat.com/show_bug.cgi?id=495956#c1
 https://bugzilla.redhat.com/show_bug.cgi?id=495956#c2

Would also need UI in Palimpsest to turn it back on.
Comment 1 David Zeuthen (not reading bugmail) 2009-06-09 13:23:39 UTC
Also, the disable notification UI should be something like

 [ ] Don't warn me about this disk unless things gets worse

with better wording.
Comment 2 Michael Wiktowy 2009-06-10 02:13:31 UTC
I think that the "unless things get worse" is important. If people just want to disable this check permanently, they can remove the Disk Notifications from the Startup Applications.

In my case, this popup is annoying since I have a non-zero-but-small "reallocated sector count" causing the error. It is not growing and the official Seagate diagnostic utility does not show any issues (making it difficult to get an RMA from Seagate to get it replaced) so I am figuring that the disk is still OK to use.

However, should this start growing, I want to know right away as it would give me more leverage with Seagate support and also give me enough notice to migrate away from this disk.
Comment 3 Chris Hubick 2009-06-15 07:59:09 UTC
My fresh install of Fedora 11 now greets me with this popup due to a single reallocated sector on one disk in my RAID 1 array.

I think it would be good to have the ability to manually enter a per device (global would be an extra bonus) threshold setting for each type of error - so I could set it to the current number of failures + 1, and then be notified if the value increases at all, and then further bump the threshold or make a decision on how to deal with it.  A "reset threshold to default (Y)" option would be nice as well.

Lacking such an interface, does anyone know if one can modify the default threshold values using GConf or something?
Comment 4 Mikel Ward 2009-09-03 04:45:28 UTC
Agree with the comment about "Don't warn me about this disk unless things get worse".

I have a disk with 14 relocated sectors, well under the threshold.

It's annoying that I see the palimpsest notification all the time, and there is no way to acknowledge it.
Comment 5 aaqqwqw 2009-11-24 16:18:22 UTC
I have the same problem. My new hard disc has also a few relocated sectors and works fine anyway. I want Palimpsest to look at the device, but the error message every start is not necessary. Please make a possibility to warn the user if the value that produced the warning gets higher. I don't want to disable Palimpsest completely. Thanks.
Comment 6 Mikel Ward 2009-12-29 03:52:30 UTC
FWIW, the drive died.  Still unsure about the probability of failure after
seeing a bad sector/relocated sector, but if you're confident, and can provide
rationale, then please feel free to WONTFIX/INVALID.
Comment 7 David Zeuthen (not reading bugmail) 2012-11-12 20:43:04 UTC
Today (master and what will be 3.8) we only show notifications if the disk is actually failing (we're not looking at bad sectors or anything else right now) and this can be disabled by

 gsettings set org.gnome.settings-daemon.plugins.gdu-sd active false

which I think is good enough so closing for now. In the future we may want more fancy stuff - which may include "disable until it gets worse" - but that's for another bug.
Comment 8 David Zeuthen (not reading bugmail) 2012-11-12 20:45:17 UTC
*** Bug 587459 has been marked as a duplicate of this bug. ***