Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 549784 - notifications for new global shortcuts should be silenced
Summary: notifications for new global shortcuts should be silenced
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: kdebase-runtime
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: kde-4.4
TreeView+ depends on / blocked
 
Reported: 2009-12-22 16:53 UTC by Sebastian Vahl
Modified: 2010-02-01 02:50 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-02-01 02:50:21 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Screenshot (deleted)
2009-12-22 16:53 UTC, Sebastian Vahl
no flags Details
xsession-errors after login (deleted)
2009-12-22 16:54 UTC, Sebastian Vahl
no flags Details

Description Sebastian Vahl 2009-12-22 16:53:35 UTC
Created attachment 379863 [details]
Screenshot

Description of problem:
After a login into KDE 4.4 many notifications for registering new global shortcuts appear. They should be silenced.


Version-Release number of selected component (if applicable):
kdebase-runtime-4.3.85-1

Comment 1 Sebastian Vahl 2009-12-22 16:54:33 UTC
Created attachment 379864 [details]
xsession-errors after login

I've attached .xsession-errors if that helps.

Comment 2 Steven M. Parrish 2010-01-12 14:49:50 UTC
This bug has been triaged

Steven M. Parrish
KDE & Packagekit Triager 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 3 Rex Dieter 2010-02-01 02:50:21 UTC
Should get squashed when kdebase-runtime-4.3.98-1 lands (tomorrowish)


Note You need to log in before you can comment on or make changes to this bug.