|
Bugzilla – Full Text Bug Listing |
| Summary: | disable system-beep for ifplugd by default or supply GUI-functionality to disable it | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Forgotten User --EoyBps8f <forgotten_--EoyBps8f> |
| Component: | Network | Assignee: | Christian Zoz <zoz> |
| Status: | VERIFIED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Enhancement | ||
| Priority: | P5 - None | CC: | aj, kontakt |
| Version: | Beta 1 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | fix. | ||
|
Description
Forgotten User --EoyBps8f
2006-01-25 19:15:01 UTC
(In reply to comment #0) > There are several reasons to disable the beep by default. > > 1. The beep is meant to announce success/activity. Since most people use some > GUI, they get a notification by NetworkManager If they use NetworkManager, they won't use ifplugd => no beep. > or knemo anyway. So it is > redundant. Those that do not use any GUI are certainly not unexperienced and > can easily re-enable it, if they really want to. > > 2. Unexperienced users cannot mute it easily and expect their notebook to be > silent, if they mute it via e.g. kmixer. The option to disable the beep (-b) is > not even documented in the sysconfig-editor short-summary, so people really > have to use the command-line to find out. We can change the short-summary. > I would suggest to either put a checkbox in Yast "Disable beep", or, since > there is NetworkManager now, disable it by default. I like the beep, so i see no reason to disable it. > Who would complain to not hear that horrible beep? ;) Me. Created attachment 65222 [details]
fix.
Christian: please apply and close. Thanks.
added patch to svn. will be in beta3 Unexperienced users are unlikely to use /etc/sysconfig-editor, how do they know how to disable it? Just came across another issue. The beeps for hotplug-events and alike were "removed", so there must have been a valid reason to do so. Hence disabling this one would be consistent with the former decision. They are not. PCMCIA still beeps. PCI hotplug never did. Unexperienced users will use NetworkManager. https://bugzilla.novell.com/show_bug.cgi?id=120736#c8 According to that comment from Christian Zoz, they are supposed to not beep. And as you can see in comment #8 there, it is not a bug :-) We (Christian and me) like it this way. You don't. You have an option to turn it off. If you send a patch to a Yast-Module (or a new Yast module) that implements the setting of this option, it might well be included. *** Bug 120736 has been marked as a duplicate of this bug. *** For all users who like the beep: Yeah it´s your opintion but imagine that some company buys several computers with SuSE linux on it (at least at my university they did that). And they´re all started at the same time. Do you think this sounds good? It only makes the people think "what freaky os from the 90´s is this" *gg Can you imagine Windows or MacOS (or any other mature OS) implementing a beep from the system speaker on startup? So even if you like it IMHO most of your user will not. Starting with 10.1 we will use NetworkManager as default which does not beep. I am not that familiar with NetworkManager, but I understand that it is just a backend. So I guess that it can handle NICs, as ifplugd can, i.e. disabling them when unplugging the cable. So there might be some reason in assuming that unexperienced users will/should use NetworkManager, since they earn the ease and get all the functionality that ifplugd offers. One thing that still seems to force me to use the "traditional" way is that I could not find any functionality in knetworkmanager that can set-up static IPs. Will KDE-users be able to use NetworkManager for setting up a NIC with the same functionality as Yast offers currently, i.e. including a static IP in 10.1 final? My computer has just a NIC in it. So if you use NetworkManager as default why does the installer suggest me to use "the traditional way"? To be decided by product manager. aj, should i disable ifplugd beeps? I have no preferences. - pro beep: ifplugd has no visual feedback - con beep: it is enabled by default, so it beeps at boottime. IMHO it need not to be enabled by default if there is only one NIC and it is no laptop. Make it beep-free. OK. fixed in svn. Beep-free, please. Sometimes I have pcspkr.ko loaded (to get an audible notification for mail), but I was quite puzzled that `rcnetwork restart eth0` made noise the other day and I went to think it was a hardware failure notification (e.g. temperature problem). The "not-connected" beep that you hear when ifplugd starts does not sound like a pure single-frequency square wave and I thought the beep generation was skewed because of busy CPU, whatever (things that can happen when the kernel lags). The problem persists with ifplugd-0.28-31 from factory, I did `rcnetwork restart eth0` at least twice to rule out the "10.1" ifplugd. "grep IFPLUGD_OPTIONS /etc/sysconfig/network/config", please. |