Flash 8 Pro: Publish Preview & Keyboard Layout Problems

Hi,
Hoping someone can help. I am a NEW Flash 8 Pro user and have
discovered two problems I cant seem to resolve:
1. When I press F12 (or select Publish Preview | Default
(HTML) in the menu), although my project publishes correctly,
producing all the correct files (including a working HTML file), my
browser does not open and display the swf. I tried changing my
default browser and on several projects, but the problem persists
2. For some reason, my keyboard is set to the US layout
instead of the British layout...this is the only application that
is doing this and it doesnt appear to be an option that I can
change inside Flash.
Can anyone help me with these issues? It would be grately
appreciated.
PS: I am on a high-spec Windows XP SP2 PC (if that is of any
assistance)

Did you ever get your issue with the F12, publish preview,
not loading your browser? I have just upgraded from MX 2004 to 8
and now have this issue.
T Peluso
[email protected]

Similar Messages

Digital Cinema Desktop Preview, keyboard layout and other bugs - Leopard

I just reinstalled my Mac Pro because I hoped it would fix some bugs... but no luck. Digital cinema desktop preview (dcdp) was working just fine until I installed the Aja Kona Lhe software, afterwards only dcdp for the main display was working, both dcdp and dcdp "full screen" have disappeared. The other things I was hoping 10.5.2 would fix are the problem FCP cannot remember the keyboard layout I use (azerty-belgium) - every time I start the program I have to choose the layout again - and the fact I cannot export using compressor straight from FCP using qmaster: Final cut pro generated an error! (this has never worked)
If you are having the same problems as I do, maybe we should compare hardware to see what we have in common that could be causing this problem. As I have found during my searches, some computers have similar problems, others don't, sometimes it also matters if you've upgraded from Tiger of did a clean install, where upgrading it seems (yes really!!) gives the least problems...
I really hope there will be a bugfix soon, because I'm sure I'm not the only one having these problems... or maybe I should just install Tiger and upgrade...???

I vote for going back to Tiger. That is known to be stable. Leopard and FCP is unpredictable at the moment.
Shane

Keyboard layout problem

My wife has an old iBook running Mac OS X Tiger and it's been working just fine. Never any trouble at all with this sturdy old thing but today, for some odd reason, the keyboard layout got messed up out of nowhere. We're Swedish and need the Swedish layout ( åäö ) but it suddenly stopped working. The layout has changed and the @-character is now accessible while pressing Shift+2 instead of Alt+2. I have no idea why this happened and I have no clue as to how to change/restore the default layout. I've looked around in the International preference pane but nothing I did there changed a thing. Anyone else bumped into this particular problem?

Forget this question, I found out what was wrong. My father-in-law ( who isn't too good at computers ) changed the layout by mistake by clicking the little flag and so switched the layout from Swedish Pro to US English. Problem solved.

Keyboard layout problems in Gnome

I'm not sure if it was a recent upgrade that did it or not, but in gnome my keyboard layout is only half right. I checked the keyboard manager in the gnome menu and it was set to Generic 105 key (INTEL).
In xorg.conf the keyboard is listed as pc105. In KDE the keyboard works normally.

bgodea wrote:I changed the Gnome keyboard layout to "104 key PC" and also tried changing my xorg.conf, but I still have the same problem. In non-graphical and KDE it works fine
You also have to setup a valid layout for this kind of keyboard. That is done in the same dialog field. Then, what do you mean with "tried"? First off, if Gnome and X disagree about keyboard layout, Gnome complains loudly. Thus KDE is unilaterally setting the layout to something it likes. Check your Kconfig to find out what it is. Then find the section named InputDevice in /etc/X11/xorg.conf that looks something like this:
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbLayout" "us"
Option "XkbRules" "xorg"
Option "XkbModel" "pc104"
EndSection
Change it to resemble this example, if it doesn't. Check if your ServerLayout actually uses this InputDevice. Finally, is there anything else we should know about your keyboard? Do you run XGL/AIGLX?
Last edited by Captain Spaulding (2007-04-03 16:50:46)

Dwm and non-english keyboard layouts problem

Hi all,
I am using dwm 5.5. I'm Greek so I change between keyboard layouts all the time,
see the relevant xorg.conf section:
Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "us,gr"
Option "XkbVariant" ","
Option "XkbOptions" "grp:alt_shift_toggle,grp_led:scroll"
EndSection
Now the thing is that whenever I switch to Greek (by pressing Alt+Shift) the
dwm tags (1,2,...,9) are not clickable (keyboard shortcuts do work
though, so it's not a very big problem).
Do you have any ideas about how to fix that behavior? I'd go to the dwm irc
channel and ask them, but I'll be a "newbie asking stupid questions" so I
preferred to ask here
Thanks in advance
Last edited by geo909 (2010-01-08 17:23:29)

thayer wrote:Your best bet would be to post your problem to the dwm mailing list:
[email protected]
Will do...
Thanks!

[E17] lock and keyboard layout problems when suspend

Hello,
I just installed E17 on my Dell Vostro laptop. The main problem I have is related to the suspend mode.
In settings > screen > screen lock, I enabled the option "lock on suspend" and the keyboard layout is selected to "be (default, basic)" (I have a belgian keyboard).
When I use the menu system > suspend, the screen is locked. But when I suspend my laptop by closing the lid (I see the power light indicator blinking on the side, so it's suspended) the screen is not locked when I open it.
Also related to the suspend mode. The layout is set to belgian (in the screen config as explained above but also in vconsole.conf and in /etc/X11/xorg.conf.d/10-keyboard.conf). When I put the luks decryption key or when E17 starts at boot, I have the right layout. However when I resume the laptop after being suspended, the layout is switched to qwerty (en_us I guess).
Any idea why ?
Thank you
PS: this problem is maybe more related to E17 than to Archlinux but I haven't found any forum about enlightenment. If you think I have better chances somewhere else, let me know.

I was having problems with E17 after a fresh install (mixer problem, key bindings, etc), and I fixed it by deleting the configuration files at
~/.e
as the wiki says.

[SOLVED] Keyboard layout problems

Hi community,
I fresh installed arch linux and I rly like it. After playing a little around and installing the awesome wm I can't set the croatian keyboard layout.
My xorg.config file:
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
Option "Xinerama" "0"
EndSection
Section "Files"
EndSection
Section "InputDevice"
# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection
Section "InputDevice"
# generated from default
Identifier "Keyboard0"
Driver "kbd"
Option "XkbModel" "logicd"
Option "XkbLayout" "hr"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Arnos Instruments F-417"
HorizSync 24.0 - 80.0
VertRefresh 49.0 - 75.0
Option "DPMS"
EndSection
Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce 6600 GT"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
Option "TwinView" "1"
Option "TwinViewXineramaInfoOrder" "DFP-0"
Option "metamodes" "CRT: nvidia-auto-select +1920+0, DFP: nvidia-auto-select +0+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection
My Xorg.0.log file:
[ 2186.778]
This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.
[ 2186.778]
X.Org X Server 1.8.1.902 (1.8.2 RC 2)
Release Date: 2010-06-21
[ 2186.778] X Protocol Version 11, Revision 0
[ 2186.778] Build Operating System: Linux 2.6.34-ARCH x86_64
[ 2186.778] Current Operating System: Linux arch 2.6.34-ARCH #1 SMP PREEMPT Mon Jul 5 22:12:11 CEST 2010 x86_64
[ 2186.778] Kernel command line: root=/dev/sda5 ro
[ 2186.778] Build Date: 21 June 2010 12:01:49PM
[ 2186.778]
[ 2186.779] Current version of pixman: 0.18.2
[ 2186.779] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 2186.779] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 2186.779] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Jul 22 13:23:50 2010
[ 2186.779] (==) Using config file: "/etc/X11/xorg.conf"
[ 2186.779] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 2186.779] (==) ServerLayout "Layout0"
[ 2186.779] (**) |-->Screen "Screen0" (0)
[ 2186.779] (**) | |-->Monitor "Monitor0"
[ 2186.779] (**) | |-->Device "Device0"
[ 2186.779] (**) |-->Input Device "Keyboard0"
[ 2186.779] (**) |-->Input Device "Mouse0"
[ 2186.780] (**) Option "Xinerama" "0"
[ 2186.780] (==) Automatically adding devices
[ 2186.780] (==) Automatically enabling devices
[ 2186.780] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 2186.780] Entry deleted from font path.
[ 2186.780] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[ 2186.780] Entry deleted from font path.
[ 2186.780] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/100dpi/,
/usr/share/fonts/75dpi/
[ 2186.780] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 2186.780] (WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[ 2186.780] (WW) Disabling Keyboard0
[ 2186.780] (WW) Disabling Mouse0
[ 2186.780] (II) Loader magic: 0x7ce880
[ 2186.780] (II) Module ABI versions:
[ 2186.780] X.Org ANSI C Emulation: 0.4
[ 2186.780] X.Org Video Driver: 7.0
[ 2186.780] X.Org XInput driver : 9.0
[ 2186.780] X.Org Server Extension : 3.0
[ 2186.786] (--) PCI:*(0:1:0:0) 10de:00f1:0000:0000 nVidia Corporation NV43 [GeForce 6600 GT] rev 162, Mem @ 0xf8000000/16777216, 0xe0000000/268435456, 0xf9000000/16777216, BIOS @ 0x????????/131072
[ 2186.787] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 2186.787] (II) LoadModule: "extmod"
[ 2186.787] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
[ 2186.787] (II) Module extmod: vendor="X.Org Foundation"
[ 2186.787] compiled for 1.8.1.902, module version = 1.0.0
[ 2186.787] Module class: X.Org Server Extension
[ 2186.787] ABI class: X.Org Server Extension, version 3.0
[ 2186.787] (II) Loading extension MIT-SCREEN-SAVER
[ 2186.787] (II) Loading extension XFree86-VidModeExtension
[ 2186.787] (II) Loading extension XFree86-DGA
[ 2186.787] (II) Loading extension DPMS
[ 2186.787] (II) Loading extension XVideo
[ 2186.787] (II) Loading extension XVideo-MotionCompensation
[ 2186.787] (II) Loading extension X-Resource
[ 2186.787] (II) LoadModule: "dbe"
[ 2186.787] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
[ 2186.787] (II) Module dbe: vendor="X.Org Foundation"
[ 2186.787] compiled for 1.8.1.902, module version = 1.0.0
[ 2186.788] Module class: X.Org Server Extension
[ 2186.788] ABI class: X.Org Server Extension, version 3.0
[ 2186.788] (II) Loading extension DOUBLE-BUFFER
[ 2186.788] (II) LoadModule: "glx"
[ 2186.788] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 2186.813] (II) Module glx: vendor="NVIDIA Corporation"
[ 2186.813] compiled for 4.0.2, module version = 1.0.0
[ 2186.813] Module class: X.Org Server Extension
[ 2186.813] (II) NVIDIA GLX Module 256.35 Wed Jun 16 19:10:31 PDT 2010
[ 2186.813] (II) Loading extension GLX
[ 2186.813] (II) LoadModule: "record"
[ 2186.814] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
[ 2186.814] (II) Module record: vendor="X.Org Foundation"
[ 2186.814] compiled for 1.8.1.902, module version = 1.13.0
[ 2186.814] Module class: X.Org Server Extension
[ 2186.814] ABI class: X.Org Server Extension, version 3.0
[ 2186.814] (II) Loading extension RECORD
[ 2186.814] (II) LoadModule: "dri"
[ 2186.814] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
[ 2186.814] (II) Module dri: vendor="X.Org Foundation"
[ 2186.814] compiled for 1.8.1.902, module version = 1.0.0
[ 2186.814] ABI class: X.Org Server Extension, version 3.0
[ 2186.814] (II) Loading extension XFree86-DRI
[ 2186.814] (II) LoadModule: "dri2"
[ 2186.814] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[ 2186.814] (II) Module dri2: vendor="X.Org Foundation"
[ 2186.814] compiled for 1.8.1.902, module version = 1.2.0
[ 2186.815] ABI class: X.Org Server Extension, version 3.0
[ 2186.815] (II) Loading extension DRI2
[ 2186.815] (II) LoadModule: "nvidia"
[ 2186.815] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 2186.816] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 2186.816] compiled for 4.0.2, module version = 1.0.0
[ 2186.816] Module class: X.Org Video Driver
[ 2186.816] (II) NVIDIA dlloader X Driver 256.35 Wed Jun 16 18:45:02 PDT 2010
[ 2186.816] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 2186.816] (++) using VT number 7
[ 2186.820] (II) Primary Device is: PCI 01@00:00:0
[ 2186.820] (II) Loading sub module "fb"
[ 2186.820] (II) LoadModule: "fb"
[ 2186.820] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 2186.821] (II) Module fb: vendor="X.Org Foundation"
[ 2186.821] compiled for 1.8.1.902, module version = 1.0.0
[ 2186.821] ABI class: X.Org ANSI C Emulation, version 0.4
[ 2186.821] (II) Loading sub module "wfb"
[ 2186.821] (II) LoadModule: "wfb"
[ 2186.821] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 2186.821] (II) Module wfb: vendor="X.Org Foundation"
[ 2186.821] compiled for 1.8.1.902, module version = 1.0.0
[ 2186.821] ABI class: X.Org ANSI C Emulation, version 0.4
[ 2186.821] (II) Loading sub module "ramdac"
[ 2186.821] (II) LoadModule: "ramdac"
[ 2186.821] (II) Module "ramdac" already built-in
[ 2186.821] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
[ 2186.821] (==) NVIDIA(0): RGB weight 888
[ 2186.821] (==) NVIDIA(0): Default visual is TrueColor
[ 2186.821] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 2186.821] (**) NVIDIA(0): Option "TwinView" "1"
[ 2186.822] (**) NVIDIA(0): Option "MetaModes" "CRT: nvidia-auto-select +1920+0, DFP: nvidia-auto-select +0+0"
[ 2186.822] (**) NVIDIA(0): Option "TwinViewXineramaInfoOrder" "DFP-0"
[ 2186.822] (**) NVIDIA(0): Enabling RENDER acceleration
[ 2186.822] (II) NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
[ 2186.822] (II) NVIDIA(0): enabled.
[ 2188.363] (II) NVIDIA(0): NVIDIA GPU GeForce 6600 GT (NV43) at PCI:1:0:0 (GPU-0)
[ 2188.363] (--) NVIDIA(0): Memory: 131072 kBytes
[ 2188.363] (--) NVIDIA(0): VideoBIOS: 05.43.02.39.00
[ 2188.363] (II) NVIDIA(0): Detected AGP rate: 8X
[ 2188.363] (--) NVIDIA(0): Interlaced video modes are supported on this GPU
[ 2188.363] (--) NVIDIA(0): Connected display device(s) on GeForce 6600 GT at PCI:1:0:0:
[ 2188.363] (--) NVIDIA(0): Arnos Instruments F-417 (CRT-0)
[ 2188.363] (--) NVIDIA(0): ViewSonic VX2433wm (DFP-0)
[ 2188.363] (--) NVIDIA(0): Arnos Instruments F-417 (CRT-0): 400.0 MHz maximum pixel
[ 2188.363] (--) NVIDIA(0): clock
[ 2188.363] (--) NVIDIA(0): ViewSonic VX2433wm (DFP-0): 155.0 MHz maximum pixel clock
[ 2188.363] (--) NVIDIA(0): ViewSonic VX2433wm (DFP-0): Internal Single Link TMDS
[ 2188.363] (**) NVIDIA(0): TwinView enabled
[ 2188.363] (II) NVIDIA(0): Display Devices found referenced in MetaMode: CRT-0, DFP-0
[ 2188.364] (II) NVIDIA(0): Assigned Display Devices: CRT-0, DFP-0
[ 2188.364] (II) NVIDIA(0): Validated modes:
[ 2188.364] (II) NVIDIA(0):
[ 2188.364] (II) NVIDIA(0): "CRT:nvidia-auto-select+1920+0,DFP:nvidia-auto-select+0+0"
[ 2188.364] (II) NVIDIA(0): Virtual screen size determined to be 3200 x 1080
[ 2188.364] (--) NVIDIA(0): DPI set to (95, 96); computed from "UseEdidDpi" X config
[ 2188.364] (--) NVIDIA(0): option
[ 2188.364] (==) NVIDIA(0): Enabling 32-bit ARGB GLX visuals.
[ 2188.364] (--) Depth 24 pixmap format is 32 bpp
[ 2188.365] (II) NVIDIA(0): Initialized AGP GART.
[ 2188.373] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 2188.373] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
[ 2188.373] (II) NVIDIA(0): configuration option may not be set correctly. When the
[ 2188.373] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
[ 2188.373] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
[ 2188.373] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
[ 2188.373] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
[ 2188.373] (II) NVIDIA(0): Config Options in the README.
[ 2188.373] (II) NVIDIA(0): Setting mode
[ 2188.373] (II) NVIDIA(0): "CRT:nvidia-auto-select+1920+0,DFP:nvidia-auto-select+0+0"
[ 2188.613] (II) Loading extension NV-GLX
[ 2188.657] (II) NVIDIA(0): Initialized OpenGL Acceleration
[ 2188.659] (==) NVIDIA(0): Disabling shared memory pixmaps
[ 2188.659] (II) NVIDIA(0): Initialized X Rendering Acceleration
[ 2188.659] (==) NVIDIA(0): Backing store disabled
[ 2188.659] (==) NVIDIA(0): Silken mouse enabled
[ 2188.660] (**) NVIDIA(0): DPMS enabled
[ 2188.660] (II) Loading extension NV-CONTROL
[ 2188.661] (II) Loading extension XINERAMA
[ 2188.661] (II) Loading sub module "dri2"
[ 2188.661] (II) LoadModule: "dri2"
[ 2188.661] (II) Reloading /usr/lib/xorg/modules/extensions/libdri2.so
[ 2188.661] (II) NVIDIA(0): [DRI2] Setup complete
[ 2188.661] (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia
[ 2188.661] (==) RandR enabled
[ 2188.661] (II) Initializing built-in extension Generic Event Extension
[ 2188.661] (II) Initializing built-in extension SHAPE
[ 2188.661] (II) Initializing built-in extension MIT-SHM
[ 2188.661] (II) Initializing built-in extension XInputExtension
[ 2188.661] (II) Initializing built-in extension XTEST
[ 2188.661] (II) Initializing built-in extension BIG-REQUESTS
[ 2188.661] (II) Initializing built-in extension SYNC
[ 2188.661] (II) Initializing built-in extension XKEYBOARD
[ 2188.661] (II) Initializing built-in extension XC-MISC
[ 2188.661] (II) Initializing built-in extension SECURITY
[ 2188.661] (II) Initializing built-in extension XINERAMA
[ 2188.661] (II) Initializing built-in extension XFIXES
[ 2188.661] (II) Initializing built-in extension RENDER
[ 2188.661] (II) Initializing built-in extension RANDR
[ 2188.661] (II) Initializing built-in extension COMPOSITE
[ 2188.661] (II) Initializing built-in extension DAMAGE
[ 2188.664] (II) Initializing extension GLX
[ 2188.842] (II) config/udev: Adding input device Power Button (/dev/input/event2)
[ 2188.842] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 2188.842] (II) LoadModule: "evdev"
[ 2188.842] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 2188.842] (II) Module evdev: vendor="X.Org Foundation"
[ 2188.842] compiled for 1.8.0, module version = 2.4.0
[ 2188.842] Module class: X.Org XInput Driver
[ 2188.842] ABI class: X.Org XInput driver, version 9.0
[ 2188.842] (**) Power Button: always reports core events
[ 2188.842] (**) Power Button: Device: "/dev/input/event2"
[ 2188.842] (II) Power Button: Found keys
[ 2188.842] (II) Power Button: Configuring as keyboard
[ 2188.842] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
[ 2188.842] (**) Option "xkb_rules" "evdev"
[ 2188.843] (**) Option "xkb_model" "evdev"
[ 2188.843] (**) Option "xkb_layout" "us"
[ 2188.883] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[ 2188.883] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 2188.883] (**) Power Button: always reports core events
[ 2188.883] (**) Power Button: Device: "/dev/input/event1"
[ 2188.883] (II) Power Button: Found keys
[ 2188.883] (II) Power Button: Configuring as keyboard
[ 2188.883] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
[ 2188.883] (**) Option "xkb_rules" "evdev"
[ 2188.883] (**) Option "xkb_model" "evdev"
[ 2188.883] (**) Option "xkb_layout" "us"
[ 2188.887] (II) config/udev: Adding input device Logitech USB-PS/2 Optical Mouse (/dev/input/event3)
[ 2188.887] (**) Logitech USB-PS/2 Optical Mouse: Applying InputClass "evdev pointer catchall"
[ 2188.887] (**) Logitech USB-PS/2 Optical Mouse: always reports core events
[ 2188.887] (**) Logitech USB-PS/2 Optical Mouse: Device: "/dev/input/event3"
[ 2188.887] (II) Logitech USB-PS/2 Optical Mouse: Found 3 mouse buttons
[ 2188.887] (II) Logitech USB-PS/2 Optical Mouse: Found scroll wheel(s)
[ 2188.887] (II) Logitech USB-PS/2 Optical Mouse: Found relative axes
[ 2188.887] (II) Logitech USB-PS/2 Optical Mouse: Found x and y relative axes
[ 2188.887] (II) Logitech USB-PS/2 Optical Mouse: Configuring as mouse
[ 2188.887] (**) Logitech USB-PS/2 Optical Mouse: YAxisMapping: buttons 4 and 5
[ 2188.887] (**) Logitech USB-PS/2 Optical Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 2188.887] (II) XINPUT: Adding extended input device "Logitech USB-PS/2 Optical Mouse" (type: MOUSE)
[ 2188.887] (**) Logitech USB-PS/2 Optical Mouse: (accel) keeping acceleration scheme 1
[ 2188.887] (**) Logitech USB-PS/2 Optical Mouse: (accel) acceleration profile 0
[ 2188.887] (**) Logitech USB-PS/2 Optical Mouse: (accel) acceleration factor: 2.000
[ 2188.887] (**) Logitech USB-PS/2 Optical Mouse: (accel) acceleration threshold: 4
[ 2188.887] (II) Logitech USB-PS/2 Optical Mouse: initialized for relative axes.
[ 2188.887] (II) config/udev: Adding input device Logitech USB-PS/2 Optical Mouse (/dev/input/mouse0)
[ 2188.887] (II) No input driver/identifier specified (ignoring)
[ 2188.888] (II) config/udev: Adding input device Logitech USB Multimedia Keyboard (/dev/input/event4)
[ 2188.888] (**) Logitech USB Multimedia Keyboard: Applying InputClass "evdev keyboard catchall"
[ 2188.888] (**) Logitech USB Multimedia Keyboard: always reports core events
[ 2188.888] (**) Logitech USB Multimedia Keyboard: Device: "/dev/input/event4"
[ 2188.888] (II) Logitech USB Multimedia Keyboard: Found keys
[ 2188.888] (II) Logitech USB Multimedia Keyboard: Configuring as keyboard
[ 2188.888] (II) XINPUT: Adding extended input device "Logitech USB Multimedia Keyboard" (type: KEYBOARD)
[ 2188.888] (**) Option "xkb_rules" "evdev"
[ 2188.888] (**) Option "xkb_model" "evdev"
[ 2188.888] (**) Option "xkb_layout" "us"
[ 2188.888] (II) config/udev: Adding input device Logitech USB Multimedia Keyboard (/dev/input/event5)
[ 2188.889] (**) Logitech USB Multimedia Keyboard: Applying InputClass "evdev keyboard catchall"
[ 2188.889] (**) Logitech USB Multimedia Keyboard: always reports core events
[ 2188.889] (**) Logitech USB Multimedia Keyboard: Device: "/dev/input/event5"
[ 2188.889] (II) Logitech USB Multimedia Keyboard: Found keys
[ 2188.889] (II) Logitech USB Multimedia Keyboard: Configuring as keyboard
[ 2188.889] (II) XINPUT: Adding extended input device "Logitech USB Multimedia Keyboard" (type: KEYBOARD)
[ 2188.889] (**) Option "xkb_rules" "evdev"
[ 2188.889] (**) Option "xkb_model" "evdev"
[ 2188.889] (**) Option "xkb_layout" "us"
[ 2188.891] (II) config/udev: Adding input device PC Speaker (/dev/input/event0)
[ 2188.891] (II) No input driver/identifier specified (ignoring)
Xorg.0.log important (I think):
[ 2188.888] (II) config/udev: Adding input device Logitech USB Multimedia Keyboard (/dev/input/event4)
[ 2188.888] (**) Logitech USB Multimedia Keyboard: Applying InputClass "evdev keyboard catchall"
[ 2188.888] (**) Logitech USB Multimedia Keyboard: always reports core events
[ 2188.888] (**) Logitech USB Multimedia Keyboard: Device: "/dev/input/event4"
[ 2188.888] (II) Logitech USB Multimedia Keyboard: Found keys
[ 2188.888] (II) Logitech USB Multimedia Keyboard: Configuring as keyboard
[ 2188.888] (II) XINPUT: Adding extended input device "Logitech USB Multimedia Keyboard" (type: KEYBOARD)
[ 2188.888] (**) Option "xkb_rules" "evdev"
[ 2188.888] (**) Option "xkb_model" "evdev"
[ 2188.888] (**) Option "xkb_layout" "us"
[ 2188.888] (II) config/udev: Adding input device Logitech USB Multimedia Keyboard (/dev/input/event5)
[ 2188.889] (**) Logitech USB Multimedia Keyboard: Applying InputClass "evdev keyboard catchall"
[ 2188.889] (**) Logitech USB Multimedia Keyboard: always reports core events
[ 2188.889] (**) Logitech USB Multimedia Keyboard: Device: "/dev/input/event5"
[ 2188.889] (II) Logitech USB Multimedia Keyboard: Found keys
[ 2188.889] (II) Logitech USB Multimedia Keyboard: Configuring as keyboard
[ 2188.889] (II) XINPUT: Adding extended input device "Logitech USB Multimedia Keyboard" (type: KEYBOARD)
[ 2188.889] (**) Option "xkb_rules" "evdev"
[ 2188.889] (**) Option "xkb_model" "evdev"
[ 2188.889] (**) Option "xkb_layout" "us"
Why is he adding the keyboard 2 times, and why "xkb_layout" "us"? I need hr (croatian).
My first post Sorry, for the bad english.
Last edited by b3no (2010-07-22 23:45:29)

[ 2186.780] (WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
Add this
Section "ServerFlags"
Option "AllowEmptyInput" "no"
EndSection
EditL If the above didn't help, read this http://wiki.archlinux.org/index.php/Xor … d_settings
Last edited by karol (2010-07-22 12:06:04)

Keyboard layout problem at the login screen

Hi there!
I'm having a huge problem at the login screen just after installing OS X Lion 10.7. It seems like the keyboard layout has changed, and I need to enter some numbers in my password. I can't find the digit 9, and I really don't know if the other numbers are in the right place either. Maybe it's changed to a us layout.. What to do?

stoneheart,
the numbers are in the same position on a US English keyboard as they are on a Norwegian keyboard.
If you select the Users & Groups pane of System Preferences, and select its Login Options, do you have the “Show Input menu in login window” checkbox checked? (That’s where the checkbox’s location is in Mavericks; I don’t have Lion, so I don’t know if it’s in the same location there.)

E70 Keyboard layout problems

I have a brand-new E70 bought from Expansys a week ago. I have the same problem reported by other here regarding incorrect keyboard layout (e.g. "(" key produces ")" and "/" produces ","). I have not upgraded the firmware, this is the way the phone was shipped.
I haven't found any solution in this forum or on the web yet. Any advice is appreciated. Thanks,
-- Terrence

bgodea wrote:I changed the Gnome keyboard layout to "104 key PC" and also tried changing my xorg.conf, but I still have the same problem. In non-graphical and KDE it works fine
You also have to setup a valid layout for this kind of keyboard. That is done in the same dialog field. Then, what do you mean with "tried"? First off, if Gnome and X disagree about keyboard layout, Gnome complains loudly. Thus KDE is unilaterally setting the layout to something it likes. Check your Kconfig to find out what it is. Then find the section named InputDevice in /etc/X11/xorg.conf that looks something like this:
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbLayout" "us"
Option "XkbRules" "xorg"
Option "XkbModel" "pc104"
EndSection
Change it to resemble this example, if it doesn't. Check if your ServerLayout actually uses this InputDevice. Finally, is there anything else we should know about your keyboard? Do you run XGL/AIGLX?
Last edited by Captain Spaulding (2007-04-03 16:50:46)

What sort of computer specs do I need to get Flash Pro publishing super fast?

I'm typing this after pressing ctrl enter and waiting for the swf to be created. The laptop I'm using has the specs below.
I'd tired of waiting so if I can afford it I'm going to buy a decent desktop pc (Mac out of my price range I think). I do use various other programs, but primarily I use Flash Pro CS5.5 (soon CS6).
I know very little about all the numbers you see when looking at computer specs and which ones need to be bigger to get Flash to compile faster. Can anyone help me?
Cheers
Chris
My Current (slow publishing) Laptop specs (or meaningless numbers to me)
Windows 7 Home Premium
Manufacturer:      Dell
Model:                Studio 1555
Rating:                5.0 Windows Experience Index
Processor:          Pentium(R) Dual-Core CPU T4300 @ 2.10Ghz 2.10GHz
Installed memory (RAM)     4.00 GB
System type:     64-bit Operating System

It's all about the speed of your CPU and RAM. Laptops have the premium tax applied to them. To get a really fast laptop, you'll need to pay the price. They design laptops to be used via battery so the type of laptop you're targeting, which would have a modern i7+ processor, would be very expensive. At least $2k. They're designed to be as close to a desktop as possible and will drain battery considerably faster than what you're probably used to.
That isn't to say you can't get something much faster than you have.
What is your budget and must it be a laptop or are you open to using a desktop despite it being less convenient? A good way to think about it is you'll get double or more speed out of a desktop than a laptop for the same price so the question is relevant.
I have a modern i7 laptop and my i5 desktop literally beats it by double and cost half the price and has WAY more features.

Flash CS5 Publish Preview not working

I am working on Flash CS5 Professional. I have created a simple fla file but not able to Publish->preview the swf file in Google Chrome.
When I click on Publish Preview it opens a new browser window but nothing happens.What am I doing wrong?

I'm having the same issue. Flash runs fine in Chrome, except for when I choose File->Publish Preview->Default - HTML in Flash CS5. When I try to Publish Preview, Chrome, my default browser, opens a new tab that is blank. Repeatedly pressing Refresh doesn't do anything for me (it still loads a blank page).
I just played with it a bit. I think I've got it figured out.
Flash CS5 loads Chrome with the file address in the address bar, but it doesn't Go. If I copy the address, open a new tab, right-click in the address bar and choose "Paste and go", the Flash file loads. Going back to the original tab (the one opened by Flash when I selected Publish Preview, I pressed Enter in the address bar and the Flash file loaded.

Flash Pro publish to 11. When?

I would have expected, with all the announcements about AIR 3 and Flash Player 11, that there would be some mention about when Flash Pro will be able to publish to 11.
Doesn't appear to be covered anywhere, so I'm asking here.
When will Flash Pro users be able to publish to Flash 11?
Is Adobe going to make this possible. I can see that you can use Flash Builder, but there are still many development houses that work in Flash Pro.
Is Adobe putting the Flash Pro platform on the ice flow, like Director?
SHould I be migrating my team over to using Flash Builder?
Why can't I find information about this?

Well I found this on the Flash Player debug download page (http://www.adobe.com/support/flashplayer/downloads.html):
"10/3/11 - Updated debugger (aka debug players or content debuggers) and standalone (aka projector) versions of Flash Player 11.0 are available for Flash Builder 4, Flash Catalyst, Flash Professional CS4, and Flash Professional CS5 users"
I tried installing the standalone player available there, but after placing it in the proper Flash Pro CS5 directory at C:\Program Files\Adobe\Adobe Flash CS5\Players, the standalone player launched by Flash Professional CS5 still won't work with FP11 Stage 3D content. I still get the VerifyError:
"Error #1014: Class flash.display3D.textures::Texture could not be found."
I am using Away3D 4.0.
Oh well. Guess I'll just have to keep viewing it in the browser for now :-(

Non-US keyboard layout problem with VNC

Hi everyone,
I've got an arch box at work running tigervnc through an ssh tunnel so that I can work from home when I need to.
Everything is great, as long as I'm using and ASCII keyboard layout.
When I switch layouts, the keystrokes just don't get through to the server.
Here's what I use to switch layouts:
setxkbmap -layout us,ru -option 'grp:alt_shift_toggle'
So I need to type in russian, and I hit alt-shift, as usual, and start typing, but nothing is echoed back to me. I can tell that the keystrokes are just not getting to the destination because if I'm at a terminal and I'm switched to the ru layout and I type something and hit enter, I just get a newline, as if there was nothing typed at all.
Any ideas?

Hi,
Why are the characters mixed up in the session?
This issue can occur if the keyboard language has been switched on the remote PC while running a remote desktop session. In the case you would like to switch to a different keyboard
language follow these instructions.
Important:
The remote PC selects the system language of the device running the remote desktop client and not the keyboard language. When switching the keyboard language on your device,
you need to manually switch the keyboard language on the remote PC.
1. Open settings on your device.
2. Tap General and then tap International.
3. Tap Language and select the language running on the remote PC.
4. Open the RD Client and connect to the remote PC and check if the Windows keyboard language matches the language that you selected.
Quote from
Remote Desktop Client on Mac: FAQ
Thanks.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Flash Pro CS6 iOS Native Extension Problem

I am trying out flash pro CS6 new features.
The most important one being ANEs [native extensions].
in flash builder 4.6, when using an ANE for ios, it is sometimes required to put the ios5 SDK location [ -platformsdk in ADT].
This is completely missing in Flash Pro CS6 IDE, any way around that?
[for the info on including the ios5 sdk check:
http://help.adobe.com/en_US/flex/mobileapps/WSe4e4b720da9dedb5-4aefe03513238d8a1b8-8000.ht ml]
Thanks.

Uhmm, i'm doing a kind-of-360º-panorama-app and we need Gyroscope and Ad-hoc / AppStore distribution. And i've tried to get an answer of any kind from guys on Adobe on their AIR facebook fan page and here.
SHould we write our own gyroscope ANE?, have any of you succesfully compiled ad-hoc or app-store with Ketzler Euler Gyroscope ANE?
http://www.ketzler.de/2011/11/adobe-air-gyroscope-native-extension-with-euler-angles-roll- pitch-yaw-for-ios/
regards.

Keyboard Layout Problems with OS X Mavericks on MacBook

My brother and I have a Early 2009 MacBook that received succesive updates on OS X over the past four years: it went from Leopard to Snow Leopard to Lion to Mountain Lion. But this year, we decided to upgrade it from a clean install of Mavericks.
It went fine, but... the keyboard is acting in a terrible way. The layout is bugged! The left shift key enters the "Y" letter, while return enters the "/" key... I've just tried everything to fix this resetting NVRAM and SMC, but nothing has worked.
Somebody else is having this problem? Could a software update fix it?

See if a Safe Mode boot helps...
Startup your Mac in Safe Mode
A Safe Mode boot takes much longer than a normal boot so be patient.
Once you are in Safe Mode, click Restart from the Apple () menu.

Flash 8 Pro: Publish Preview & Keyboard Layout Problems

Similar Messages

Maybe you are looking for