Bug 10627

Summary:	expected keysym, got XF86AudioEject: line 2232 of inet
Product:	xkeyboard-config	Reporter:	Zbigniew Luszpinski <zbiggy>
Component:	General	Assignee:	xkb
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	minor
Priority:	lowest
Version:	unspecified
Hardware:	x86 (IA32)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:

Description Zbigniew Luszpinski 2007-04-12 02:41:24 UTC

During x.org 7.2 startup I see such error:
expected keysym, got XF86AudioEject: line 2232 of inet

I have just migrated from xkbdata to xkeyboard-config 0.9

xorg.conf
Option "XkbRules" "base"
Option "XkbLayout" "pl"
Option "XkbVariant" "basic"
Option "XkbOptions" "lv3:ralt_switch"
Option "XkbModel" "acpi" 

x.org startup log:
X Window System Version 7.2.0
Release Date: 22 January 2007
X Protocol Version 11, Revision 0, Release 7.2
Build Operating System: Linux 2.6.20.4 i686 
Current Operating System: Linux x-power 2.6.20.6 #1 Tue Apr 10 18:11:57 CEST 2007 i686
Build Date: 06 April 2007
	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Thu Apr 12 11:20:24 2007
(==) Using config file: "/etc/X11/xorg.conf"

expected keysym, got XF86AudioEject: line 2232 of inet
xset:  bad font path element (#341), possible causes are:
    Directory does not exist or has wrong permissions
    Directory missing fonts.dir
    Incorrect font server address or syntax

Comment 1 Sergey V. Udaltsov 2007-04-12 03:10:41 UTC

Thanks for reporting the bug. It is already fixed:

http://webcvs.freedesktop.org/xkeyboard-config/xkeyboard-config/symbols/inet?r1=1.50&r2=1.51

*** This bug has been marked as a duplicate of bug 10103 ***

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.