Suse/NovellThis Forum is for the discussion of Suse Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I've been playing around with a Microsoft Wireless keyboard/mouse, and it basically works well. I created a .Xmodmap directory in my home directory, and mapped as many buttons as I could, then use KDE to assign those buttons to shortcuts for various things. So far, so good.
Then I noticed there was a 'Microsoft Wireless Multimedia Keyboard 1.0A' in Yast/Hardware/Keyboards. That sounds like what I have, so I selected it, and logged out/in again. Much to my suprise, when I hit the mute button, an on screen display popped up that said 'Mute On' or 'Mute Off'. Same thing when I used the vol up/down buttons, I get an on screen slider that shows the volume settings. Very cool!!
The problem is, it doesn't actually change the volume or mute the sound...:-( I went into 'kmix' and configured the Global shortcuts using the new values, but pressing the keys did not change anything in 'kmix'. I know kmix had the new values because the key changed from what I had in my .Xmodmap file to something like 'XfreeAudioMute' or 'XfreeVolDown'.
So it seems I can get the keys to function by using my own .Xmodmap file, but then I don't get the cool OSD that shows Mute on/off or the volume slider. If I don't use my .Xmodmap, I get the cool displays, but it doesn't actually change the volume.
Does anyone have any ideas on how to get both to work? If I could find what triggers those OSD's, I might be able to get it to use my .Xmodmap values, or something like that.
The best bet it to remove the xmodmap file completley, and then reassign. Your probably find its a conflict between what the xmodmap says, and what the xfree stuff is saying. I've quite happily modify the keyboard shortcuts in KDE and not mess with the modmap, in fact I generally alter the inet mapping directly in Xfree so all the mm keys are mapped to the correct key responses I get from xev.
I was sure I had already tried that, but I did it again, just in case.
I renamed my ~/.Xmodmap to something else, then logged out & in again. All my mappings were gone, and I get the OSD's for mute and vol up/down. I've gone into kmix/Global Shortcuts and assigned them to the buttons. They now say things like 'XF86AudioRaiseVolume' or 'XF86AudioMute'. However, I'm back where I started, the volume does not change, nor does the mute work.
It's almost as if whatever program is doing the OSD's is not letting the key pass thru to kmix.