Summary: | Can't enable system bell | ||
---|---|---|---|
Product: | [Applications] systemsettings | Reporter: | Praveen Srinivasan <popapa> |
Component: | kcm_bell | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | andresbajotierra, kde-2011.08, long, lueck, mnyromyr, ogoffart |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Praveen Srinivasan
2008-04-01 21:42:51 UTC
I can confirm that this problem exists. I'm using KDE 4.1.2 on Mandriva 2009.0 I can confirm that this problem exists. I'm using KDE 4.1.2 on Mandriva 2009.0 Here using: Qt: 4.4.3 KDE: 4.1.85 (KDE 4.1.85 (KDE 4.2 Beta2)) kdelibs svn rev. 899634 / kdebase svn rev. 899635 on ArchLinux x86_64 - Kernel 2.6.27.8 I can confirm this bug Removing the "KConfig::NoGlobals" flag from the KConfig constructor in: kdebase/workspace/kcontrol/bell/bell.cpp:172 seems to solve the issue, however I don't know if this will bring side effects. BTW, the settings is properly saved (SystemBell on/off), however the module doesn't reflect the current status as it can't load the settings properly. I'm adding the KNotify maintainer. @Olivier: I've talking with dfaure in the IRC. It seems that the SystemBell setting is no longer used in KNotify (he couldn't find any file loading the "UseSystemBell" setting from "kdeglobals"). May be it was lost during the KDE4 porting process. (In KDE3: /kdelibs/kdecore/knotifyclient.cpp: 324: d->useSystemBell = config->readBoolEntry("UseSystemBell",false ); ) Do you missed that one or it isn't going to be implemented again ? (and therefore this bug can be closed, and the System Bell KCModule can be deleted) Thanks :) this should be fixed in trunk now. i'll backport when the code proves stable. Can someone confirm that this issue is resolved in KDE 4.4, as per comment #7? Thanks. The issue is resolved here in kubuntu 10.10 kde 4.6.2 Works for me when using KDE SC 4.8. Should this report be closed now? |