Scroll Pen brush problem

I have a problem when applying the scroll pen brush to a path I drew with the pen tool, I get the desired effect but I get a total of six lines instead of just the one. Is there any way to not get this many? I am using CS3.
Kindes regards,
Oskar

Certainly.

Similar Messages

CS2 - 6D art pen brushes rotate the wrong way

I'm wondering if this is the normal behaviour of the 6d art pen brushes that come with Illustrator CS2. When I use them with my 6d art pen, they rotate in the opposite direction as I rotate my pen. Does anyone know a way around this? The pen works fine in Painter and Photoshop.
My setup is Macbook Santa Rosa 2.2 Ghz, 4 gb ram, windows xp home sp2 (up to date), Cintiq 12 WX with the 6D art pen (art marker).

Dear CS3 and CS4 photoshop users,
I hope I can straighten out the whole confusion with the 6D art pen ROTATION feature not working. (not a solution but clarify)
Although we appreciate all forms of opinions, I have a message for people saying that rotation feature will work when you set the brush settings correctly. WE_ARE_NOT_NEW at this. Many of us have been using the rotation feature with CS3 perfectly fine, and yes, we know how to set it up. Thank you for your tips but IT IS NOT working as it should. I don't know whether it is defendant with: x64 or x32 syst on our part, driver problem with wacom, or in fact with the CS4. I will tell you what I did and what I got however.
X64 Vista Ult. 6G RAM, Quad core, both Intuos 3 and Cintiq 20wsx.(Cintiq is my primary and the only one I use now a days and I don't have both plugged at the same time. However, I have tried with Intuos3 separately, and it won't work) I uninstalled old wacom driver and updated to the latest (5days old), remade brush settings fresh with rotation setting (not just using my own saved preset from CS3) and it still WON"T WORK... so there it is. Hope this clarifies the issue so that the TECH can help us (please) and not think that we are all confused.

Lightroom 5 Adjustment Brush Problem?

When I want to use my adjustment brush, I do not have the second circle show up to show where it has taken the adjustment from the photo. Is there a way to fix this? I was able to use it before and didn't have a problem. But I haven't used the program in a while. If anyone can help me with this that would be awesome.

When I am advising on weird adjustment brush problems I always say - Update your Mouse and Tablet drivers to the latest version. Update your video card to the latest driver. If neither of those fix it, then try resetting the preference file: Resetting (or 'Trashing') the Lightroom Preferences file - Lightroom Forums

Strange Brush Problem

I originally had CS3 Extended on my iMac (OS 10.5.8). The brushes and clone tool worked normally.
When I upgraded, I got CS4 (not Extended). The brush and clone tool problem I've had with CS4 is that the the stroke
only comes from the center where the cross is. The whole width of the brush is not active. I upgraded to CS5 and have
had the exact same problem.
I spoke to a friend who is Adobe-certified and who teaches Photoshop. She said she has seen this problem one other time
and that she tried changing every setting in every relevant part of the program, yet nothing fixed it.
I freelance for an agency that recently put the entire CS4 Creative Suite on my laptop so that I could work for them in InDesign.
I already had my copy of CS4 on the laptop, but the new installation overwrote it. In THIS copy of Photoshop, I DO NOT have the
brush problem. I installed my copy of Photoshop CS5 onto the laptop and in the upgrade I DO have the brush problem. But the
agency's copy of CS4 on my laptop is still problem-free.
Any clues whatsoever? I haven't called Adobe yet.
Thank you,
avebon

Below is a replica of the problem I'm having with the Clone Tool.
As you can see from my original post, this problem occurs with my copy of CS4 that was upgraded from CS3 Extended. It does not occur with a completely different copy of CS4 that came with a full version of CS4 (including InDesign and Illustrator).

Problem with pen & brush tools

Hi,
I've been at this for all day. I reset preferences and reinstalled but it didn't help.
I select either pen or brush tool, set the brush size to lets say 16pt, choose a default width profile and set the brush as basic. As i draw the line/make the anchor point the settings are reset to 1pt, normal width profile and sometimes 2pt oval. I can reselect the line and apply the settings then, as i click on the artboard the settings remain and if i try to draw a new line the settings are reset again.
I'm using cs5 on mac.
Any ideas?

You can't.
You can not have an oval caligraphy brush with a width profile assigned.
There's no workaround for that. It simply can not be done. If you want a profile, you can't use a caligraphy brush. If you want an oval, you can't assign a profile.
There is no way to set up a specific brush how you are asking. The two features are conflicting. The purpose of an oval brush (or any caligraphy brush) is to allow you to alter the width of the brush stroke as you draw. The purpose of a profile is to alter the width of a stroke as well. You can not have two items trying to fight for the same appearance. It's like asking how can I draw a rectangle with no fill but looks green in the middle. You can't.
I believe what you need to do to achieve the appearance you want is to simply draw a path, set a profile, then manually adjust the profile with the width tool if needed. You can get this to look almost identical to an oval caligraphy brush if desired. Which is why you can't do both at the same time.

Two Sudden Brush Problems...

Hello All,
Maybe someone knows the answer. I'm using Ps CS5 on a Mac Pro.
Suddenly today....
(1) Using my Wacom-tablet pen for the brush, I can't achieve pure full opacity even when the opacity-pressure-override button is off and opacity is set to 100%. It's as if that button is always depressed, and so I get the same pressure-sensitive degrees of opacity <100% whether the button is depressed or not.
(2) To get-around problem (1) I used my Mac Trackpad to get 100% brush opacity. But then it suddenly stopped working. Now when I click down and move my finger to apply strokes, while History registers that the brush was used, no stroke appears even with opacity at 100%. I can use the track pad to scroll, zoom, and anything except apply any effects to the image (and there's only one layer) including healing brush or eraser. And yet History registers and these effects were made.
After rebooting the Trackpad works for about a minute and then stops again. There's no effect of rebooting on problem (1). If I save the file upon which History registered brush effects, upon reopening there are no brush strokes, nor when viewed with Preview, proving that it's not a failure to display effects to the image upon.
I'm at a loss. Any ideas?
Thanks for any help!!!

Are Photoshop and OS fully updated?
Is the tablet driver up-to-date, too?
And just to make sure: What is the Brush’s Flow setting and what are the Brush Panel settings (Transfer, Color Dynamics, Shape Dynamics, …)?
Boilerplate-text:
As with all unexplainable Photoshop-problems you might try trashing the prefs (after making sure all customized presets like Actions, Patterns, Brushes etc. have been saved and making a note of the Preferences you’ve changed) by pressing command-alt-shift on starting the program or starting from a new user-account.
System Maintenance (repairing permissions, purging PRAM, running cron-scripts, cleaning caches, etc.) might also be beneficial, Onyx has been recommended for such tasks.
http://www.apple.com/downloads/macosx/system_disk_utilities/onyx.html
Weeding out bad fonts never seems to be a bad idea, either. (Validate your fonts in Font Book and remove the bad ones.)
If 3rd party plug-ins are installed try disabling them to verify if one of those may be responsible for the problem.

Brush Problems with Illustrator CS4... the line does not draw with my mouse movement

When I use any other brush besides the Calligraphic Brushes from the "Artistic Ink" brush library, I press down with either my Wacom Tablet or mouse, and the line does not appear to draw. Then I release the button on the mouse or lift my pen tablet up, the lines appears. Sometimes, a little "dot dot dot" line appears when the brush stroke it going to appear. But most of the time, it's just nothing, and then the line appears after I've drawn it.
However, with the preselected brushed at the top, and the Calligraphic Artistic Brushes, the line appears as I am drawing it. This is what I want for the other brushes.
Is this normal?! I just recently upgraded to Windows 7, and reinstalled the Adobe Suite. I can't remember if Illustrator did this before I reinstalled it, but I'm not sure it did otherwise it would have annoyed me as much as it does now. Can anybody help me?

Hi!
Hope I'm not hijacking this thread.
First time posting to a forum.
I'm having the same problem and followed the advice for changing the file name in the Illustrator CS# Settings folder.
This solved the problem of seeing predicted brush paths for very basic brushs, but I still can't get a preview path for any of the ink brushs.
I've seen video tutorials which demonstrate inking techniques and the ink brush predicted path was clearly working in those tutorials.
I'm assuming therefore that I should be able to see some type of preview when using the ink brushs.
Any advice would be great!
Cheers!

CS4 and pen pressure problem

When drawing with the brush or the clone stamp brush now and then strokes are drawn at full pressure even though that is not the case. The next strokes are ok again for a while and then again... a few strokes like they there was no pen pressure. Very annoying when retouching masks.
I already installed the latest Wacom driver but no joy.
What else could I try?
My graphics card doesn't have OpenGL capacities so I don't think that's the problem or could it?
Also CS4 is much slower than CS3 in updating the screen. Related?
Tips welcome...
I am a long time user of Photoshop (since 2.5) but I think CS4 will be the first upgrade I will skip although I love the new adjustments and masks panels...
Windows XP Pro, 4 Gigs of Ram, Matrox Millenium card, plenty of sratch disk space.

I had exactly the same problem with my Wacom Intuos 3 tablet.
The solution is to go into Control Panel>Administrative Tools>Computer Management>Device Manager>Human Interface Devices and disable Wacom Virtual Hid Driver.
I found that somewhere on the Wacom site and it does it for me.
I'm not sure but I think it started when I updated the Wacom drivers to try and solve another problem.
Can I ask, if you press CNTRL-ALT-DEL to start task manager, does that disable your pen until you select the Task Manager button? That came with the latest driver too.
Brian

PSE 11 - Scrolling through Brushes, Effects, etc

I've recently had to uninstall and re-install PSE 11 after some virus problems on my Windows 7 premium computer. I have a lot of brushes and styles loaded directly into the program. I like to see all my options at one time. I used to be able to scroll up and down through all of choices. Now I can only page through them in a downward direction. To get back to the top of my selections I have to "reset brushes" or "reset styles". This is a real pain and slows me down. How to I fix this. I've looked at Preferences, but don't see anything to correct this. I can use my scroll wheel, but only on the choices available. Help!

Besides making the effect using a gradient fill layer set to saturation blend mode with a foreground (black) to transparent gradient (reversed), you could load the actions (effects)
into the actions panel (Window>Actions) and run them from the actions panel. Then step back in the history panel (Window>History) to the New Gradient Fill Layer
step and double click on the Gradient Fill icon in the layers panel to adjust the effect.
On a windows system the actions (effects) are in:
C:\ProgramData\Adobe\Photoshop Elements\11.0\Photo Creations\photo effects
(you need to enable show Hidden files and folders from the Control Panel>Appearance and Personalization>Folder Options)
Also, you can change the position of the gradient with the gradient fill dialog open by dragging insde the document area.
Message was edited by: R_Kelly

Photoshop CC on Sony's Vaoi Fit15A (pen pressure problems)

This question is very specific. I just downloaded the trial version of Photoshop CC on a new Vaoi Fit15A. It's like a hybrid between a tablet so I can supposedly draw on the screen directly. (So I don't have a pen tablet.) My problem is it doesn't register the pen pressure. I also tried borrowing a wacom bamboo to see if it can feel that, but nope, PS CC still won't recognize the pen pressure even from a pen tab. What should I do? Thanks to anyone who can help!

Hi! Thanks so much for replying
I tried attaching a bamboo create to see if it could sense the pen pressure. Alas, it still couldn't. I already installed the drivers but it still wouldn't.
So um, just letting you know that I did take it to the store where I bought it. They told me that Adobe wasn't keeping up with something something industry-wise. Sorry I'm in Japan and my Japanese isn't that good but basically they told me that I have to wait for Adobe elements 12 (which isn't out yet) before I can hope that my Vaoi recognizes the pen pressure. So they basically told me that Vaoi fit15A, using PS CC, isn't compatible. There's no way I can get pen pressure using that program.
But is this true? Adobe is late that's why I can't get it to work in Vaoi Fit 15A ? They just didn't tell me this because they couldn't get it to work right? When is this "Adobe elements 12" suppose to come out anyway? If I can't get it to work I'll have to return the Vaoi itself since I need my pen pressure working in PS.
Thanks for your time!!!

Scrolling Synaptic Touchpad Problem (Arch Wiki didn't solve it)

Good to the whole Arch's community.
First of all to appear, I am codebuster and am new in this community and in this magnificent distro that I have been charmed with for his simplicity and performance. Always I had begun for behind the topic of the configuration of Arch's installation, but consulting his magnificent tips and coming to the official information it me has been possible. I have everything working of correct form except the function of scroll of my touchpad Synaptic (function that I use always and that really I throw enough in lack). I have followed the steps indicated so much in the Wiki (http://wiki.archlinux.org/index.php/Touchpad_Synaptics) as in numerous forums of linux in inet but I have not managed to make it work, for what I resort to you to seeing if someone can throw something of light.
Let's begin.
PC: Acer Aspire 5610
Distribution: ArchLinux updated a today.
Desktop: XFCE
Graphics: NVIDIA Geforce GO 7300 (proprietary Drivers: NVIDIA Driver Version:256.35)
Driver: xf86-input-synaptics-1.2.2-2
hardinfo
Name PS/2 Synaptics TouchPad
Type Mouse
Bus 0x11
Vendor 2
Product 0x1
Version 0x0
Connected to isa0060/serio/input0
cat /proc/bus/input/devices
I: Bus=0011 Vendor=0002 Product=0001 Version=0000
N: Name="PS/2 Synaptics TouchPad"
P: Phys=isa0060/serio4/input0
S: Sysfs=/devices/platform/i8042/serio4/input/input5
U: Uniq=
H: Handlers=mouse0 event5
B: EV=7
B: KEY=70000 0 0 0 0 0 0 0 0
B: REL=3
xorg.conf
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 256.35 (buildmeister@builder101) Wed Jun 16 19:25:59 PDT 2010
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/misc/"
FontPath "/usr/share/fonts/TTF/"
FontPath "/usr/share/fonts/OTF/"
FontPath "/usr/share/fonts/Type1/"
FontPath "/usr/share/fonts/100dpi/"
FontPath "/usr/share/fonts/75dpi/"
EndSection
Section "Module"
Load "dri2"
Load "dbe"
Load "record"
Load "glx"
Load "extmod"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mouse0"
Option "ZAxisMapping" "4 5 6 7"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
EndSection
Section "Device"
Identifier "Card0"
Driver "nvidia"
VendorName "nVidia Corporation"
BoardName "G72M [Quadro NVS 110M/GeForce Go 7300]"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
SubSection "Display"
Viewport 0 0
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
Xorg.0.log
[ 18.827]
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.
[ 18.828]
X.Org X Server 1.8.1.902 (1.8.2 RC 2)
Release Date: 2010-06-21
[ 18.828] X Protocol Version 11, Revision 0
[ 18.828] Build Operating System: Linux 2.6.34-ARCH i686
[ 18.828] Current Operating System: Linux arch-live 2.6.34-ARCH #1 SMP PREEMPT Mon Jul 5 21:03:38 UTC 2010 i686
[ 18.828] Kernel command line: root=/dev/disk/by-uuid/2cf26781-3ca3-4654-8b83-37ea60864aab ro
[ 18.828] Build Date: 21 June 2010 11:54:27AM
[ 18.828]
[ 18.829] Current version of pixman: 0.18.2
[ 18.830] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 18.830] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 18.830] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Jul 26 15:21:50 2010
[ 18.909] (==) Using config file: "/etc/X11/xorg.conf"
[ 18.909] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 18.962] (==) ServerLayout "X.org Configured"
[ 18.962] (**) |-->Screen "Screen0" (0)
[ 18.962] (**) | |-->Monitor "Monitor0"
[ 18.963] (**) | |-->Device "Card0"
[ 18.963] (**) |-->Input Device "Mouse0"
[ 18.963] (**) |-->Input Device "Keyboard0"
[ 18.963] (==) Automatically adding devices
[ 18.963] (==) Automatically enabling devices
[ 19.052] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 19.052] Entry deleted from font path.
[ 19.063] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 19.063] Entry deleted from font path.
[ 19.063] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 19.064] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 19.064] Entry deleted from font path.
[ 19.064] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 19.064] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 19.064] Entry deleted from font path.
[ 19.064] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 19.064] Entry deleted from font path.
[ 19.064] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 19.064] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 19.064] Entry deleted from font path.
[ 19.064] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 19.064] (**) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/Type1/,
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/Type1/
[ 19.064] (**) ModulePath set to "/usr/lib/xorg/modules"
[ 19.064] (WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[ 19.064] (WW) Disabling Mouse0
[ 19.064] (WW) Disabling Keyboard0
[ 19.064] (II) Loader magic: 0x81e9d00
[ 19.064] (II) Module ABI versions:
[ 19.064] X.Org ANSI C Emulation: 0.4
[ 19.064] X.Org Video Driver: 7.0
[ 19.064] X.Org XInput driver : 9.0
[ 19.064] X.Org Server Extension : 3.0
[ 19.088] (--) PCI:*(0:1:0:0) 10de:01d7:1025:0090 nVidia Corporation G72M [Quadro NVS 110M/GeForce Go 7300] rev 161, Mem @ 0xd1000000/16777216, 0xc0000000/268435456, 0xd0000000/16777216
[ 19.088] (II) Open ACPI successful (/var/run/acpid.socket)
[ 19.088] (II) "extmod" will be loaded. This was enabled by default and also specified in the config file.
[ 19.088] (II) "dbe" will be loaded. This was enabled by default and also specified in the config file.
[ 19.088] (II) "glx" will be loaded. This was enabled by default and also specified in the config file.
[ 19.088] (II) "record" will be loaded. This was enabled by default and also specified in the config file.
[ 19.088] (II) "dri" will be loaded by default.
[ 19.088] (II) "dri2" will be loaded. This was enabled by default and also specified in the config file.
[ 19.088] (II) LoadModule: "dri2"
[ 19.141] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[ 19.175] (II) Module dri2: vendor="X.Org Foundation"
[ 19.175] compiled for 1.8.1.902, module version = 1.2.0
[ 19.175] ABI class: X.Org Server Extension, version 3.0
[ 19.176] (II) Loading extension DRI2
[ 19.176] (II) LoadModule: "dbe"
[ 19.176] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
[ 19.187] (II) Module dbe: vendor="X.Org Foundation"
[ 19.187] compiled for 1.8.1.902, module version = 1.0.0
[ 19.187] Module class: X.Org Server Extension
[ 19.187] ABI class: X.Org Server Extension, version 3.0
[ 19.187] (II) Loading extension DOUBLE-BUFFER
[ 19.187] (II) LoadModule: "record"
[ 19.187] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
[ 19.188] (II) Module record: vendor="X.Org Foundation"
[ 19.188] compiled for 1.8.1.902, module version = 1.13.0
[ 19.188] Module class: X.Org Server Extension
[ 19.188] ABI class: X.Org Server Extension, version 3.0
[ 19.188] (II) Loading extension RECORD
[ 19.188] (II) LoadModule: "glx"
[ 19.189] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 20.431] (II) Module glx: vendor="NVIDIA Corporation"
[ 20.431] compiled for 4.0.2, module version = 1.0.0
[ 20.431] Module class: X.Org Server Extension
[ 20.431] (II) NVIDIA GLX Module 256.35 Wed Jun 16 19:21:24 PDT 2010
[ 20.431] (II) Loading extension GLX
[ 20.431] (II) LoadModule: "extmod"
[ 20.432] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
[ 20.441] (II) Module extmod: vendor="X.Org Foundation"
[ 20.441] compiled for 1.8.1.902, module version = 1.0.0
[ 20.441] Module class: X.Org Server Extension
[ 20.441] ABI class: X.Org Server Extension, version 3.0
[ 20.441] (II) Loading extension MIT-SCREEN-SAVER
[ 20.441] (II) Loading extension XFree86-VidModeExtension
[ 20.441] (II) Loading extension XFree86-DGA
[ 20.441] (II) Loading extension DPMS
[ 20.441] (II) Loading extension XVideo
[ 20.441] (II) Loading extension XVideo-MotionCompensation
[ 20.441] (II) Loading extension X-Resource
[ 20.441] (II) LoadModule: "dri"
[ 20.442] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
[ 20.451] (II) Module dri: vendor="X.Org Foundation"
[ 20.451] compiled for 1.8.1.902, module version = 1.0.0
[ 20.451] ABI class: X.Org Server Extension, version 3.0
[ 20.451] (II) Loading extension XFree86-DRI
[ 20.451] (II) LoadModule: "nvidia"
[ 20.452] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 20.560] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 20.560] compiled for 4.0.2, module version = 1.0.0
[ 20.560] Module class: X.Org Video Driver
[ 20.620] (II) NVIDIA dlloader X Driver 256.35 Wed Jun 16 18:59:34 PDT 2010
[ 20.625] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 20.625] (++) using VT number 7
[ 20.629] (II) Primary Device is: PCI 01@00:00:0
[ 20.645] (II) Loading sub module "fb"
[ 20.646] (II) LoadModule: "fb"
[ 20.654] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 20.675] (II) Module fb: vendor="X.Org Foundation"
[ 20.675] compiled for 1.8.1.902, module version = 1.0.0
[ 20.675] ABI class: X.Org ANSI C Emulation, version 0.4
[ 20.675] (II) Loading sub module "wfb"
[ 20.675] (II) LoadModule: "wfb"
[ 20.676] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 20.694] (II) Module wfb: vendor="X.Org Foundation"
[ 20.694] compiled for 1.8.1.902, module version = 1.0.0
[ 20.694] ABI class: X.Org ANSI C Emulation, version 0.4
[ 20.694] (II) Loading sub module "ramdac"
[ 20.694] (II) LoadModule: "ramdac"
[ 20.694] (II) Module "ramdac" already built-in
[ 20.744] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
[ 20.744] (==) NVIDIA(0): RGB weight 888
[ 20.744] (==) NVIDIA(0): Default visual is TrueColor
[ 20.744] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 20.744] (**) NVIDIA(0): Enabling RENDER acceleration
[ 20.744] (II) NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
[ 20.744] (II) NVIDIA(0): enabled.
[ 22.341] (II) NVIDIA(0): NVIDIA GPU GeForce Go 7300 (G72) at PCI:1:0:0 (GPU-0)
[ 22.341] (--) NVIDIA(0): Memory: 262144 kBytes
[ 22.341] (--) NVIDIA(0): VideoBIOS: 05.72.22.58.30
[ 22.341] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[ 22.341] (--) NVIDIA(0): Interlaced video modes are supported on this GPU
[ 22.341] (--) NVIDIA(0): Connected display device(s) on GeForce Go 7300 at PCI:1:0:0:
[ 22.341] (--) NVIDIA(0): LPL (DFP-0)
[ 22.341] (--) NVIDIA(0): LPL (DFP-0): 330.0 MHz maximum pixel clock
[ 22.341] (--) NVIDIA(0): LPL (DFP-0): Internal Dual Link LVDS
[ 22.355] (II) NVIDIA(0): Assigned Display Device: DFP-0
[ 22.355] (==) NVIDIA(0):
[ 22.355] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
[ 22.355] (==) NVIDIA(0): will be used as the requested mode.
[ 22.355] (==) NVIDIA(0):
[ 22.355] (II) NVIDIA(0): Validated modes:
[ 22.355] (II) NVIDIA(0): "nvidia-auto-select"
[ 22.356] (II) NVIDIA(0): Virtual screen size determined to be 1280 x 800
[ 22.356] (--) NVIDIA(0): DPI set to (98, 96); computed from "UseEdidDpi" X config
[ 22.356] (--) NVIDIA(0): option
[ 22.356] (==) NVIDIA(0): Enabling 32-bit ARGB GLX visuals.
[ 22.356] (--) Depth 24 pixmap format is 32 bpp
[ 22.358] (II) NVIDIA(0): Initialized GPU GART.
[ 22.371] (II) NVIDIA(0): ACPI display change hotkey events enabled: the X server is new
[ 22.371] (II) NVIDIA(0): enough to receive ACPI hotkey events.
[ 22.371] (WW) NVIDIA(0): ACPI: Error: Unable to find the brightness file path under
[ 22.372] (WW) NVIDIA(0): /proc/acpi/video. The NVIDIA X driver will not be able to
[ 22.372] (WW) NVIDIA(0): respond to ACPI brightness change hotkey events.
[ 22.372] (II) NVIDIA(0): Setting mode "nvidia-auto-select"
[ 23.783] (II) Loading extension NV-GLX
[ 23.817] (II) NVIDIA(0): Initialized OpenGL Acceleration
[ 23.831] (==) NVIDIA(0): Disabling shared memory pixmaps
[ 23.831] (II) NVIDIA(0): Initialized X Rendering Acceleration
[ 23.851] (==) NVIDIA(0): Backing store disabled
[ 23.851] (==) NVIDIA(0): Silken mouse enabled
[ 23.858] (==) NVIDIA(0): DPMS enabled
[ 23.858] (II) Loading extension NV-CONTROL
[ 23.859] (II) Loading extension XINERAMA
[ 23.859] (II) Loading sub module "dri2"
[ 23.859] (II) LoadModule: "dri2"
[ 23.860] (II) Reloading /usr/lib/xorg/modules/extensions/libdri2.so
[ 23.860] (II) NVIDIA(0): [DRI2] Setup complete
[ 23.860] (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia
[ 23.860] (==) RandR enabled
[ 23.860] (II) Initializing built-in extension Generic Event Extension
[ 23.860] (II) Initializing built-in extension SHAPE
[ 23.860] (II) Initializing built-in extension MIT-SHM
[ 23.860] (II) Initializing built-in extension XInputExtension
[ 23.860] (II) Initializing built-in extension XTEST
[ 23.860] (II) Initializing built-in extension BIG-REQUESTS
[ 23.860] (II) Initializing built-in extension SYNC
[ 23.860] (II) Initializing built-in extension XKEYBOARD
[ 23.860] (II) Initializing built-in extension XC-MISC
[ 23.860] (II) Initializing built-in extension SECURITY
[ 23.860] (II) Initializing built-in extension XINERAMA
[ 23.860] (II) Initializing built-in extension XFIXES
[ 23.860] (II) Initializing built-in extension RENDER
[ 23.860] (II) Initializing built-in extension RANDR
[ 23.860] (II) Initializing built-in extension COMPOSITE
[ 23.860] (II) Initializing built-in extension DAMAGE
[ 23.864] (II) Initializing extension GLX
[ 24.465] (II) config/udev: Adding input device Power Button (/dev/input/event4)
[ 24.465] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 24.465] (II) LoadModule: "evdev"
[ 24.466] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 24.483] (II) Module evdev: vendor="X.Org Foundation"
[ 24.483] compiled for 1.8.0, module version = 2.4.0
[ 24.483] Module class: X.Org XInput Driver
[ 24.483] ABI class: X.Org XInput driver, version 9.0
[ 24.483] (**) Power Button: always reports core events
[ 24.483] (**) Power Button: Device: "/dev/input/event4"
[ 24.491] (II) Power Button: Found keys
[ 24.491] (II) Power Button: Configuring as keyboard
[ 24.491] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
[ 24.491] (**) Option "xkb_rules" "evdev"
[ 24.491] (**) Option "xkb_model" "evdev"
[ 24.491] (**) Option "xkb_layout" "us"
[ 24.579] (II) config/udev: Adding input device Video Bus (/dev/input/event5)
[ 24.580] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 24.580] (**) Video Bus: always reports core events
[ 24.580] (**) Video Bus: Device: "/dev/input/event5"
[ 24.587] (II) Video Bus: Found keys
[ 24.587] (II) Video Bus: Configuring as keyboard
[ 24.587] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD)
[ 24.587] (**) Option "xkb_rules" "evdev"
[ 24.587] (**) Option "xkb_model" "evdev"
[ 24.587] (**) Option "xkb_layout" "us"
[ 24.593] (II) config/udev: Adding input device Power Button (/dev/input/event3)
[ 24.594] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 24.594] (**) Power Button: always reports core events
[ 24.594] (**) Power Button: Device: "/dev/input/event3"
[ 24.600] (II) Power Button: Found keys
[ 24.600] (II) Power Button: Configuring as keyboard
[ 24.600] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
[ 24.600] (**) Option "xkb_rules" "evdev"
[ 24.601] (**) Option "xkb_model" "evdev"
[ 24.601] (**) Option "xkb_layout" "us"
[ 24.602] (II) config/udev: Adding input device Lid Switch (/dev/input/event1)
[ 24.602] (II) No input driver/identifier specified (ignoring)
[ 24.602] (II) config/udev: Adding input device Sleep Button (/dev/input/event2)
[ 24.602] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
[ 24.602] (**) Sleep Button: always reports core events
[ 24.602] (**) Sleep Button: Device: "/dev/input/event2"
[ 24.611] (II) Sleep Button: Found keys
[ 24.611] (II) Sleep Button: Configuring as keyboard
[ 24.611] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD)
[ 24.611] (**) Option "xkb_rules" "evdev"
[ 24.611] (**) Option "xkb_model" "evdev"
[ 24.611] (**) Option "xkb_layout" "us"
[ 24.613] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event8)
[ 24.613] (II) No input driver/identifier specified (ignoring)
[ 24.619] (II) config/udev: Adding input device MosArt Optical Mouse (/dev/input/event7)
[ 24.619] (**) MosArt Optical Mouse: Applying InputClass "evdev pointer catchall"
[ 24.619] (**) MosArt Optical Mouse: always reports core events
[ 24.619] (**) MosArt Optical Mouse: Device: "/dev/input/event7"
[ 24.631] (II) MosArt Optical Mouse: Found 3 mouse buttons
[ 24.631] (II) MosArt Optical Mouse: Found scroll wheel(s)
[ 24.631] (II) MosArt Optical Mouse: Found relative axes
[ 24.631] (II) MosArt Optical Mouse: Found x and y relative axes
[ 24.631] (II) MosArt Optical Mouse: Configuring as mouse
[ 24.631] (**) MosArt Optical Mouse: YAxisMapping: buttons 4 and 5
[ 24.631] (**) MosArt Optical Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 24.631] (II) XINPUT: Adding extended input device "MosArt Optical Mouse" (type: MOUSE)
[ 24.631] (**) MosArt Optical Mouse: (accel) keeping acceleration scheme 1
[ 24.631] (**) MosArt Optical Mouse: (accel) acceleration profile 0
[ 24.631] (**) MosArt Optical Mouse: (accel) acceleration factor: 2.000
[ 24.631] (**) MosArt Optical Mouse: (accel) acceleration threshold: 4
[ 24.631] (II) MosArt Optical Mouse: initialized for relative axes.
[ 24.632] (II) config/udev: Adding input device MosArt Optical Mouse (/dev/input/mouse1)
[ 24.632] (II) No input driver/identifier specified (ignoring)
[ 24.638] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[ 24.638] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[ 24.638] (**) AT Translated Set 2 keyboard: always reports core events
[ 24.638] (**) AT Translated Set 2 keyboard: Device: "/dev/input/event0"
[ 24.651] (II) AT Translated Set 2 keyboard: Found keys
[ 24.651] (II) AT Translated Set 2 keyboard: Configuring as keyboard
[ 24.651] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD)
[ 24.651] (**) Option "xkb_rules" "evdev"
[ 24.651] (**) Option "xkb_model" "evdev"
[ 24.651] (**) Option "xkb_layout" "us"
[ 24.652] (II) config/udev: Adding input device PS/2 Synaptics TouchPad (/dev/input/event6)
[ 24.652] (**) PS/2 Synaptics TouchPad: Applying InputClass "evdev pointer catchall"
[ 24.652] (**) PS/2 Synaptics TouchPad: always reports core events
[ 24.652] (**) PS/2 Synaptics TouchPad: Device: "/dev/input/event6"
[ 24.664] (II) PS/2 Synaptics TouchPad: Found 3 mouse buttons
[ 24.664] (II) PS/2 Synaptics TouchPad: Found relative axes
[ 24.664] (II) PS/2 Synaptics TouchPad: Found x and y relative axes
[ 24.664] (II) PS/2 Synaptics TouchPad: Configuring as mouse
[ 24.664] (**) PS/2 Synaptics TouchPad: YAxisMapping: buttons 4 and 5
[ 24.664] (**) PS/2 Synaptics TouchPad: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 24.664] (II) XINPUT: Adding extended input device "PS/2 Synaptics TouchPad" (type: MOUSE)
[ 24.664] (**) PS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
[ 24.664] (**) PS/2 Synaptics TouchPad: (accel) acceleration profile 0
[ 24.664] (**) PS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
[ 24.664] (**) PS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
[ 24.664] (II) PS/2 Synaptics TouchPad: initialized for relative axes.
[ 24.665] (II) config/udev: Adding input device PS/2 Synaptics TouchPad (/dev/input/mouse0)
[ 24.665] (II) No input driver/identifier specified (ignoring)
10-evdev.conf
# Catchall classes for input devices
# We don't simply match on any device since that also adds accelerometers
# and other devices that we don't really want to use. The list below
# matches everything but joysticks.
Section "InputClass"
Identifier "evdev pointer catchall"
MatchIsPointer "on"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
EndSection
Section "InputClass"
Identifier "evdev keyboard catchall"
MatchIsKeyboard "on"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
EndSection
Section "InputClass"
Identifier "evdev touchpad catchall"
MatchIsTouchpad "on"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
Option "VertEdgeScroll" "true"
Option "VertScrollDelta" "100"
EndSection
Section "InputClass"
Identifier "evdev tablet catchall"
MatchIsTablet "on"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
EndSection
Section "InputClass"
Identifier "evdev touchscreen catchall"
MatchIsTouchscreen "on"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
EndSection
10-synaptics.conf
Section "InputClass"
Identifier "touchpad catchall"
Driver "synaptics"
MatchIsTouchpad "on"
Option "TapButton1" "1"
Option "TapButton2" "2"
Option "TapButton3" "3"
Option "VertEdgeScroll" "true"
Option "VertScrollDelta" "100"
EndSection
Good, I believe that this is quite, if you need more information tell to me and it will make it come near.
Excuse me for my poor english,Thanks in advance and best regards.
codebuster.
Last edited by codebuster (2010-07-26 14:44:07)

kgas wrote:
there is no need to include the synaptics option. here is mine and works fine (Acer Aspire 5738G)
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/100dpi:unscaled"
FontPath "/usr/share/fonts/75dpi:unscaled"
FontPath "/usr/share/fonts/TTF"
FontPath "/usr/share/fonts/Type1"
EndSection
Section "Module"
Load "dbe"
Load "glx"
Load "dri"
Load "dri2"
Load "extmod"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5 6 7"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
EndSection
Section "Device"
Identifier "Card0"
Driver "nvidia"
VendorName "nVidia Corporation"
BoardName "G98M [GeForce G 105M]"
BusID "PCI:1:0:0"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
¡¡¡¡ Thanks a lot for the info !!!
I remove all the Synaptics entries in the xorg.conf and worked fine with the /dev/input/mice option (in the Arch Wiki was # commented, the device, was /dev/psaux, and my mouse in hardinfo was recognized as PS/2 Synaptic for that I thought that it was the correct option ).
Only one question, now I have set the scrolling mode with two fingers, ¿do you know how to activate one finger scrolling? I tried with these options in Mouse section but doesn't work for me:
Option "VertEdgeScroll" "true" # enable vertical scroll zone
Option "HorizEdgeScroll" "false" # enable horizontal scroll zone
Option "VertTwoFingerScroll" "false" # vertical scroll anywhere with two fingers
Option "HorizTwoFingerScroll" "false" # horizontal scroll anywhere with two fingers
¡ Many, many thanks and my best regards !
codebuster.
Last edited by codebuster (2010-07-26 08:26:55)

Camera Raw v8.7.1 Adjustment Brush Problem

I’m using Adobe Bridge and my problem is in Adobe Camera Raw 8.7 and 8.7.1 itself. The Adjustment Brush cursor clicked position and the actual area that will be painted is not in the same area. As you can see the picture shown below, the actual painted area is being offset about one cm away from the cursor clicked position. Only the Adjustment Brush is affected. What's more, the cursor is larger than usual and the color changes to black instead of white. Hope someone can help to give a solution or hopefully Adobe can fix the problem.

Another user has the same issue, I recommend submitting a bug report. Re: Is this a bug or a flaw in my install?
You might try rolling back to 8.6 an see if that helps: Adobe - Adobe Camera Raw and DNG Converter : For Windows : Adobe DNG Converter 8.6
Adobe - Adobe Camera Raw and DNG Converter : For Macintosh : Adobe DNG Converter 8.6
Adobe - Feature Request/Bug Report Form
Benjamin

Web Gallery Scroll Bar Slider Problem

Hi,
I'm running Windows XP Professional and Lightroom 1.3.1. I seem to have a problem with the functionality of the sliders in the scroll bars of the web galleries that I make. I use the Flash templates.
I can drag the slider to move through the thumbnails. But when I click in the open area of the scroll bar to scroll forward or backward a page at a time, nothing happens. That functionality seems to be missing. My cursor will change to a pointed finger when it moves across the slider bar, and the up and down arrows at the ends of the scroll bar. It will not change when I place it in the open area of the scroll bar, indicating that the functionality does not exist.
This seems very odd and contrary to the global behavior of slider bars in all other applications, including within Lightroom.
Any idea what's going on and any solutions?
Thanks,
Steve

Hi...
Please check in your application parameters. Did you declare wdtablenavigation parameter?
and check table properties like scrollbarvisible always or none...
Check this link for application parameters.
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/7b/fb57412df8091de10000000a155106/content.htm
Regards
Srinivas

HP 8GB pen drive problem

sir,
i have HP 8gb pen drive when insuret XXXXXXXX drivers is instuled Removebal Disk. whine opean insuret disk error come
i have very importent Data as thier please satout this problem
Thank you
Pradeep

Hello Pradeep,
I do not understand your English, sorry. Perhaps you can use Google Translate instead. Type in your native language and copy/paste in English into the reply here.
I will try to help you then.
Thanks.

Adjustment Brush Problem

Dear all,
I have problem with my lightroom application. The edited point after using adjustment brush didn't appeared after i locked the editing. Its hard to change the editing because the point not apeared and i cant controlmy editing after dat because of the point is not show in the image. Howevwer the problem is not appeared in the graduating filter or spot adjustment.How can i solved this..
Thanks for your help

When brushing, holding down the Alt key will allow you to erase instead of adding to your brush selection. Holding down the Ctrl/Cmd key will put you in AutoMask mode if it’s not selected, or turn it off temporarily if it is. The two keys can be used together.
Also, to the right of the Effect selection (under Edit) is a little rectangle (two squares side by side) that switch between ‘basic’ and ‘advanced’ mode. By switching to advanced mode more than one effect (Exposure, Brightness, Saturation, etc.) can be added to the same selection. Having done multiple effects, switching back to basic mode will allow proportional adjustment of all of the effects made.

Scroll Pen brush problem

Similar Messages

Maybe you are looking for