Permissions/Ownership issue? [Solved]

Running KDE 3.5.8, I can open Konqueror, and click any text or openOffice fileand open it. Everything pretty much works as expected.
If I open File Manager - Superuser Mode, and try to open these same files, it fails with errors like <KDEInit could not launch 'kwrite'.> I can open these files with nano from the konsole window, so I can tell that it only happens in KDE.
I did some searching and did not find anything that helped so far. Anyone have an idea where I should look?
Last edited by Wilson Phillips (2008-01-20 13:52:14)

I've had the same problem. Here's what I've found:
Started after upgrading to xorg-xinit-1.0.7-3 today.
I edit a file with vim, get "No protocol specified" message.
I see "... X: client 9 rejected from local host ..." messages ( I boot to level 3, login as a default user, then startx to X and fluxbox, then su - to other users. The message is seen in the default user startx term. )
I can't open the display:
(firefox-bin:8400): Gtk-WARNING **: cannot open display: :0.0
[1]+ Exit 1 /opt/mozilla/bin/firefox
xorg-xinit-1.0.7-3 has a new file: /etc/X11/xinit/xserverrc which has a single line:
exec /usr/bin/X -nolisten tcp
From previous experience I know that with my setup, this will prevent me from opening Firefox, etc.
As broch said, xhost+ will "fix" it. I was using xhost +localhost, but that no longer works.
Overall, this is a better setup, as netstat -tap no longer shows any X listeners. And I have shorewall running on the box. Still I'd like to find something a little less "blunt force" than xhost+.
Snork

Similar Messages

Permissions/ Ownership issues after time machine restore

I moved from one macbook pro to another a few months ago. I opened the brand new one up, and set it up with the same account name as my old one.
I then proceeded to restore my old data from a time machine backup using the migration assistant.
Apparently there were some issues trying to migrate from a backup with the same name as the owner of the new computer, so I had to pick a new one. I then switched back over using the root user.
Even though I'm the only account on the computer besides root, and have admin privileges, some programs won't install or upgrade, I get a system message saying that I have insufficient privileges.
Is there any way to give the one account complete control of my system? I don't like having to use root that much. Thanks for your help!

Similar issues. My iMac had one of the Seagate 1TB drives that was part of the recall program. After I loaded Maverick, I started having issues that seemed to be disk related and I started getting some Time Machine errors...never had any errors until installing Maverick.
Since I was outside my 3 Yr warranty...Apple would only cover 1/2 the costs of replacing my "faulty" drive. Can't believe this was their policy to make me pay 1/2 for a drive they've known to have enough problems to announce a recall? They told me the problem was Seagate...I refuted by telling them...no...it's Apple. Can you believe they would try to pass the buck on Seagate...Apple has their label on my machine and they are the ones that negotiated the recall with Seagate? Whew!
So I took in my Time Machine backup via a 1TB External Seagate drive...and now the fun begins. I've had my system in to the Genius bar for several weeks...many trips. I've learned to not take my machine home without test driving myself as they tend to only fix 1 of the permissions issues at a time. It doesn't seem they really know what's going on...which is pretty scarey.
Anyway...the fix they seemed to use in the store was to rename my user directory and then create a new user directory with my original name...then copy everything in the renamed directory into the new directory. That fixed issues with Mail...but now my mail is totally screwed. Can't believe the work I had to do to get my mail folders all back to somewhat normal. iMovie couldn't find my movies folder. iCloud preview pane wasn't opening. I couldn't save/write to my internal disk on most of my apps. The one app I didn't test before leaving the store was iTunes. It's still screwed up and I'm not sure the chmod command will fix it...I think they tried this as an initial fix at the store. What a nitemare...
Open to any suggestions. Thanks!

OTA Update 4.08.605.2 "Rebooting Now..." Issue - SOLVED!

After so many tries and frustration I finally came across the information below and it worked like a charm
http://forums.androidcentral.com/verizon-droid-incredible/134246-second-gb-update-patch-wont-reboot-issue-solved.html
Can't say this will work for everyone, but it worked for me.
Boot into recovery
Press and hold Power, Choose "Restart" option
When screen turns off, press and hold Volume Down and Power
When the white HBOOT screen appears, use the volume button to move down to “RECOVERY.”
Press the Power button to select “RECOVERY.”
When the triangle and exclamation appears, hold the Volume Up and Power button at the same time.
Using the volume button, scroll down to “Wipe cache partition” and select it.
Select "Reboot system now"
You can now wait for the update to show up again, or try one of the methods in the post: For those who want the second GB update/patch to get the update again. It should reboot this time. Beware, it will stay at the Droid Eye screen after reboot for a while (~5 mins), but eventually, it did get installed. Be sure to make a lot of space for it though...

The restart option that AmDroid is talking about is not on the regular phone menu. Please read his post carefully. What he is talking about is in an advanced recovery based menu option.
Also, I was on 2.2 and the clear cache set date and time forward trick did not work for me to get the udpate. The clear cache and set date and time forward trick seems to mostly work if you are already on 4.06 software version and want to get the 4.08 software version.
For those on 2.2, patience is warranted! However, if you really cant wait and want to go the 4.06 update manually, you can search Android Forums dot com for manually install gingerbread. And don't worry about the article talking about being rooted. You dont need to be rooted. The instructions will work for a stock phone too. As soon as you do the manual 4.06, the 4.08 update will show up immediately.
Hope this helps!

Hi all ...I would like to add a language that is not available in Photoshop cc2014 .. My computer writes it but backwards .. How can I have this issue solves?

hi all ...I would like to add a language that is not available in Photoshop cc2014 .. My computer writes it but backwards .. How can I have this issue solves?

What language are you talking about? You might need to enable Edit/Preferences/Type/Middle Eastern and South Asian for proper display.

Compact 2013 Interrupt Issue Solved

As flagged as a comment to the post here, "My iST isn't called", there is a solution in the pipeline (as an update) for ARM interrupt issue. The issue is that interrupts that are close to timer ticks get lost. There is a complete discussion
of this on my blog at:
http://embedded101.com/Blogs/David-Jones/entryid/586/Windows-Embedded-Compact-2013-Interrupt-Issue-Solved
Cheers David Jones
Embedded MVP

As flagged as a comment to the post here, "My iST isn't called", there is a solution in the pipeline (as an update) for ARM interrupt issue. The issue is that interrupts that are close to timer ticks get lost. There is a complete discussion
of this on my blog at:
http://embedded101.com/Blogs/David-Jones/entryid/586/Windows-Embedded-Compact-2013-Interrupt-Issue-Solved
Cheers David Jones
Embedded MVP

Front row in Lion 10.7 issue (-70012) and video_ts not playing issue -solved

Hi all,
thought I just post my solution to the front row issues in 10.7. I looked for a solution for days, and when I found it, I thought it would make other peoples live easier if I combine everything in one post.
I actually had a couple of issues:
PROBLEM:
first front row stopped playing VIDEO_TS files in 10.6.
the second issue occurred when I thought upgrading to 10.7 would solve the issue; Front row still couldn't play the VIDEO_TS, because FRONT ROW was gone...
SYMPTOMS:
both issues always showed the same symptoms:
when a dvd-back folder was selected, front row would show a black screen, and then, caused by my frantic pushing the ESC button, front row would give me the dvd player not valid -70012 error.
CAUSE:
so what happened? I chose to buy my MBP 17" with the smallest HDD (yep sorry, was cheap-s-ing). Then later that year, I decided to buy the HDD caddy and switch my internal superdrive for a SSD. I ended up placing the original HDD in the hdd caddy, which I then put in the Superdrive's slot, and I placed the SSD in the slot where the original HDD was residing first. I now had a MBP 17" late 2011, with vertex3 SSD. I forgot, I also put in 16 GB, replacing the 8 GB.
So, when I back-upped all my favorite DVDs as VIDEO_TS files, (no I did not download dvds through usenet), grabbed the popcorn, and started Front Row, the disappointment began. No VIDEO_TS file would play, always the same -70012 error message. So after a lot of internet research I stumbled upon a guy who said: yeah, you have to upgrade to 10.7. After the upgrade my FRONT ROW was gone.
SOLUTIONS:
In 10.6:
As Apple's DVD player is always looking for the internal dvd player as a prerequisite to start, Front Row, which uses Apple's DVD player as video player, will throw up the -70012 error. 'Cause it finds the HDD in the HDD Caddy instead of the SuperDrive. So in 10.6 (and in 10.7 also) you can use the following solution:
(I got this solution partial from http://reviews.cnet.com/8301-13727_7-20070591-263.html)
1: modify the DVDPlayback framework that the DVD Player uses so that it will recognize external drive as a valid DVD playback device. (The HDD Caddy came with an external casing for the SuperDrive)
2: download a hex editor (I used Hexedit 220 from http://hexedit.sourceforge.net/ )
3: Go to the folder /System/Library/Frameworks/ and back up the file "DVDPlayback.framework."
4: Open Hexedit_220 and use it to open the following file:/System/Library/Frameworks/DVDPlayback.framework/Versions/A/DVDPlayback.
5: Using the editor's find&replace through COMMAND-F, replace "Internal" with the text "External" and save the file. Note that Hexedit also saves a backup automatically.
6: Close the file once saved, and then run a permissions fix on the boot drive using Disk Utility. Then restart the system and you should now be able to play DVDs off the external drive using DVD Player. That is, If you use an external dvd player (which I don't use).
7: I inserted a very small USB stick in the MBP with no data on it, and Front Row and Apple DVD Player accepted this. I could now play my backupped DVDs.
ofcourse, I still wanted to upgrade to 10.7, so here's the solution to 10.7
10.7:
upgrading was a simple click with the mouse, worked like a charm, Office still worked, and some minor updates installed through software.
Front Row however, gone...
I used the steps outlined in http://osxdaily.com/2011/07/21/front-row-for-mac-os-x-lion/ to get Front Row back:
- first get the package from Madhatter: Download the free package installer by MacHatter
- install, or customize the install
- all done.
Then I used the steps from step 3 through 7 outlined above in solution 10.6.
Catch:
So I did not find a solution to fooling the DVD Player / Front Row with the USB stick. So everytime I watch VIDEO_TS in Front Row the USB stick must be inserted. But, the good news, I can still use my remote control for something.
Hope I helped some guys out there with this solution.
Regards,
Johnno

The issue has previously hit Apple TV owners. I think people came to the conclusion that it was a HDMI handshake problem. Basically the process where the device and TV greet each other, make up some rules about communicationg and what their secret key is and so on.
I haven't tried this yet, but my local service center says that basically I can do one of two things:
- Downgrade to 10.7 and then download the 10.7.1 update from Apples website. To do this without having a Mac OS X Lion disc, you can hold down CMD + R when the computer boots to be able to access the recovery partition on newer Macs that come without the OS disc.
or..
- Put something in between the computer and TV. For example, if you're using an amplifier as a part of your home theather set up, this will probably work. The service guy said he has his Mini connected to the amplifier, which in turn is connected to speakers and a projector. The inverted colors still appear, but only once per night (i.e. after the first problem is reset by resetting the link then it's fine).
For now, I'll do my little dance of changing the source on the TV from HDMI 1 to HDMI 2 and then back again to reset the link... But, I'll probably try downgrading in a few days.

Ownership issues on a 10.4.7 network volume

I am having an issue with ownership on certain files stored on our file server.
The artworkers all copy files (Quark, Illustrator, Photoshop and InDesign) to their desktop before working, as quite often they are graphically heavy and we recommend they work local saving updates to the server through the day to avoid potential crashes. Now, the problem is that once a file has been worked on locally, it changes the ownership to that of the person who was working on that file, and consequently can cause an issue if someone else comes to work on the job.
Is there any way that I can make sure that all files uploaded to the server instantly inherit the permissions of their parent folders, so as to avoid issues with ownership? The only soultion I can come up with is generic log ins, which is not suitable for this particular environment.
XServe running 10.4.7. with Apple RAID serving as file storgae.

If ACLs are enabled on the volume, the posix inherit option will be greyed out.
If you are not using ACLs (you would know if you were), then you could turn ACLs off and the option to inherit will be available.
To turn ACLs off:
In WorkGroupManager, click Sharing.
Click the 'All' tab, then scroll the box below it all the way to the left.
You should now see your volumes (hard drives).
Select the volume where the share points are, and in the General section you'll see a checkbox to enable/disable ACLs.
Jeff

Issues solved after a second install of Belle

Hi.
I have been advised to reinstall Belle on my Nokia E7.
I've been told that after a second install of Belle most issues are gone.
Do you know what specific issues are solved after that reinstall?
I'm curious because I want to know if it is worthy to reinstall Belle.
Greetings from Paraguay.
Claudio Bogado Pompa.
Greetings from Paraguay.
Claudio Bogado Pompa.
Solved!
Go to Solution.

Claudio,
I upgraded from Anna to Belle on the first day that Belle was available. Yesterday I re-installed Belle.
Since updating my E7 from Anna to Belle I have had mixed opinions as to whether that was wise to do.
Though Belle has a lot to like about it in features and speed, there are many things that were really good in Anna but have been degraded or are even missing in Belle. See this list which many people have contributed to:
/t5/Software-Updates/List-of-Belle-additions-corrections-needed/td-p/1328167/page/3
I have customized the home screens (use three) quite a bit and have added a number of free apps for more convenience in use of the phone.
Before I tell you my experiences and give you my reasoning I should give some background about myself and my Nokia E7-00. Note that though I am very competent with computer hardware and software I have much less knowledge and skill with cell phones.
My E7-00 is my second Nokia phone experience. I also bought an E6-00 for my wife. I got the E7 for myself because I need the large keyboard for my large fingers and I like the GPS/maps capability. I got the E6 for my wife because she was unhappy with the touch screen on her Nokia 5230 and is more comfortable with a keyboard.
I have owned my E7 for less than a year, use it primarily for my small business, and upgraded to Anna immediately after purchasing it. Though I tested using a data connection for WEB browsing for a couple of months I don't subscribe to a data service now because I found little use for it and it is (in my opinion) very expensive here in Canada. I do connect my E7 to the Internet often using WIFI through my home or business routers, and occasionally through WIFI connections at hotels and other locations when I travel.
Since upgrading to Belle I have had many occasions when my phone would freeze either momentarily or permanently (necessitating powering it off) and a few times it has completely shut off for no reason. I have had a number of occasions when I have been unable to answer an incoming call because the touch screen was unresponsive.
In trying to determine the cause of the problems with the phone I have removed apps and done soft resets of the phone.
I thought about re-installing Belle but was loath to do it because of the bad experience I had when I first upgraded from Anna to Belle. At that time I did a backup of my phone using the latest version of Nokia Suite. The download and install of the Belle update went very smoothly. But once the phone was functional again I found that I lost many things including all my customizations, my WIFI settings, and all the many map favorites (GPS coordinates) I had collected when traveling and calling on customers. The backup that the Belle installation software performed did not restore these things, and the same was true of the backup I did with Nokia Suite.
Yesterday my frustration level with the phone was such that I decided I had to try a re-install of Belle. I did another backup up the phone with Nokia Suite and synced the map favorites with Nokia's on-line service. But I also had the inspiration to download the latest version of Nokia PC Suite and do a backup with that too - a good thing I did!
I used Nokia Suite to re-install Belle. After the reinstall I again had lost all my customization, some installed apps, and all map favorites. I tried to restore things by using the backup I had done with Nokia Suite, but that did not work.
Then I restored the backup I made with Nokia PC Suite and EVERYTHING was back. I could hardly believe my good fortune. Even my map favorites were back.
Since it is little more than 24 hours since my re-install of Belle I cannot say whether it was really worth the effort. But so far the phone does seem to be behaving itself. It is a little smoother in operation with less delay and I have not had any freezing. On the other hand it has been a quiet day and the phone has not had a good workout. Still, I am hopeful.
This most recent experience makes me wonder if Nokia is making improvements in Belle without giving notification. I am wondering if the version of Belle that was used for the re-install is different from the original version I installed about a month ago.
I will not upgrade my wife's E6 to Belle until I know that the problems with Belle have been fixed.
I hope you find this information useful.

Migration Tip - File Loading Issues solved by Disk Permission Repair

Had a huge problem with Excel files after migrating old iMac to new iMac via migration assistant using time machine backup of old iMac (external drive). After migration, old excel version did not work but we had alread purchased a new 2011 home version. Installed Excel 2011 after migrating and none of the Excel files would load on new iMac, from either machine - a pop up message said it could be a bunch of things, read only, etc... Numbers would access the Excel files, and could export to xls file type, but still the Excel file would not load in Excel.
From a thread suggestion, I ran the Disk Utility First Aid tab Verify Disk Permissions - holy cow, must have been two gazillion permission issues on a brand new machine - selected Repair Disk Permissions once the Verify list came up, and voila, all good on the Excel files now - they load fine.
(I assume that some of you actually know what happens and can explain it - something maybe about "cloning" the account from the Time Machine backup of my old iMac and not using a new account on the new machine, or something. Whatever, it seems that a new disk should not have two gazillion permission errors and that my migration from the Time Machine backup created them, and Disk Utility fixed them - all except two permissions that did not fix properly: itunes..../iPodUpdater and usr/lib/ruby - I assume those must be managed manually somehow if Disk Utility will not repair.)

Nice tip/report thanks!
Likely a different User UID owned those files, first user generally gets 501, second gets 502, etc., so as a rule, only one of them would have rights to the files.

Photoshop CS6 - 64 bit Optimus issue - SOLVED!

Photoshop CS6 64-bit will not run when Optimus is enabled on my W520 system The program works fine if I have discrete only set in the BIOS. Setting the default graphics adapter to NVIDIA GPU when using Optimus still has the problem. Anyone seen this issue before? CS6 Photoshop 32-bit runs OK under Optimus with the NVIDIA GPU set as default. I'm stumped so far. I searched the Adobe Support site and found nothing concerning this issue.
Update_1: I initially installed the latest NVIDIA driver from the W520 Driver Matrix. The NVIDIA level downleveled from 296.88 to 296.20, but CS6 started working properly. I then downloaded the latest NVIDIA driver 301.42 which was the level recommended by several graphics sites. The system is working smoothly now. CS6 will now use the OpenGL and acceleration features of the 2000M. BTW, my WEI changed from 6.5 to 6.6 with this driver. The 3D graphics still remains at 6.9.
Update_2: I encountered yet another anomaly with the display driver. I placed the system into Discrete Graphics and updated the display driver to 301.42. When I set the system back to Optimus, the CS6 programs could no longer access the NVIDIA GPU. I had to reinstall the 301.42 drivers again in Optimus mode to have everything back to full function. I switched back to Discrete mode to check if things were still working (they were) and then I returned to Optimus mode and the programs continued to function properly. There must be a sequence that requires Discrete updates first, and them=n Optimus, but I've never seen it documented.
W520, i7-2820QM, BIOS 1.42, 1920x1080 FHD, 32 GB RAM, 2000M NVIDIA GPU, Samsung 850 Pro 1TB SSD, Crucial M550 mSata 512GB, WD 2TB USB 3.0, eSata Plextor PX-LB950UE BluRay
W520, i7-2760QM, BIOS 1.42 1920x1080 FHD, 32 GB RAM, 1000M NVIDIA GPU, Crucial M500 480GB mSata SSD, Hitachi 500GB HDD, WD 2TB USB 3.0
Solved!
Go to Solution.

Thanks for tip!!!
Community Advocate Program Manager
English Community Deutsche Community Comunidad en Español Русскоязычное Сообщество

Macbook Pro w/ 30 inch Dell monitor issue SOLVED

I was amazed at the huge problems Apple apparently had with the bizarre $99 adapter that enables 30 inch dual channel display for the new Mini Displayport machines, including the current Macbook Pros. The reports of problems here were terrible, and I frankly waited six months or more to buy my next machine because of these problems -- Apple should be more careful about products like this.
I'm happy to report that the Mini Displayport to Displayport cable from Monoprice works GREAT with my Dell 30 inch monitor (the current one, I can't find the number since it's hidden on the back but it's the current model they sell). Fully compatible in both Mac and Windows, video seems fine, and no issues that affect display quality. The only issue I have noticed is, when the monitor goes to sleep and I wake it up again on the Mac side, it displays strange lines. Any change in monitor color or resolution causes this to go away, so all I have to do is go to 16 bit color and back again. On top of everything, the cable is dirt cheap.
Here it is:
http://www.monoprice.com/products/product.asp?cid=102&cp_id=10246&cs_id=1024606&pid=6007&seq=1&format=2

Peter Payne wrote:
feel free to comment with your own experiences.
Ok. But, what have you solved?
First off, the 'huge problems' that you mention pertain to the Apple mini-DisplayPort to Dual Link DVI adapter. There's nothing 'bizarre' about that adapter - it allows you to connect a display requiring a dual-link DVI (i.e. up to 2560x1600) to your MBP. Those issues were not really that common (judging frequency of problems by reading these forums is like judging human health by visiting an Emergency Room - you'd think most of the population was sick or injured). If you went by forum problem reports, you'd never buy any product.
More importantly, the _cable you linked above is an entirely different product_, a mini-DisplayPort to DisplayPort cable. It has nothing to do with DVI (note that Apple doesn't even make a mini-Dp to DP cable). If your display has a DisplayPort input (as the Dell 30" does) then it's fine. If your display has only DVI input (such as the Apple 30" Cinema Display), the cable you link is useless.
But, although I find it utterly unsurprising that a mini-DP to DP cable will allow one to connect a mini-DP port on a computer to a DP port on a display, good to know that in that instance, the dirt cheap cable from Monoprice does the job.

Repair disk permissions.SUID issue- Unable to get some applications to load

I need some help in repairing disk permissions ...It is affecting an application I am trying to install (1Password) in which I cannot due to applications being run by user = root.
Below is my disk verification log:
I would appreciate someone walking me through this SUID issue.
I cannot install 1Password app as it is my understanding that the user Root will not allow these permissions.
here is my Disk Verification Log;
Verify permissions for “Hard Disk”
Warning: SUID file "usr/libexec/load_hdi" has been modified and will not be repaired.
Warning: SUID file "System/Library/PrivateFrameworks/DiskManagement.framework/Versions/A/Resources /DiskManagementTool" has been modified and will not be repaired.
Warning: SUID file "System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/Reso urces/Locum" has been modified and will not be repaired.
Warning: SUID file "System/Library/PrivateFrameworks/Install.framework/Versions/A/Resources/runner " has been modified and will not be repaired.
Permissions differ on "private/var/log/secure.log", should be -rw------- , they are -rw-r----- .
Warning: SUID file "System/Library/PrivateFrameworks/Admin.framework/Versions/A/Resources/readconf ig" has been modified and will not be repaired.
Warning: SUID file "System/Library/PrivateFrameworks/Admin.framework/Versions/A/Resources/writecon fig" has been modified and will not be repaired.
Warning: SUID file "usr/libexec/authopen" has been modified and will not be repaired.
Warning: SUID file "System/Library/CoreServices/Finder.app/Contents/Resources/OwnerGroupTool" has been modified and will not be repaired.
Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repaired.
Group differs on "Library/PreferencePanes", should be 0, group is 80.
Permissions differ on "Library/PreferencePanes", should be drwxr-xr-x , they are drwxrwxr-x .
ACL found but not expected on "Applications/Utilities".
ACL found but not expected on "Applications".
ACL found but not expected on "Library".
ACL found but not expected on "Library".
Permissions verification complete

Hi gmckay,
The "Waring:SUID file..." messages are only warning message and are not a concern. The SUID bit is supposed to be set on those file. This is a glitch in the installer program- that does not update the installer database with the correct SHA1 digest for those files. The secure.log entry is a glitch in the newsyslog.conf file that sets the permissions on the secure.log less permissive than those recorded in the installer database. The ACL warning messages are caused by another glitch in the installer database. What concerns me are the double ACL messages for "LIbrary". Is this a typo?

[xorg7] international keyboard issues [SOLVED]

note that i've read the wiki as well as most of the related posts here in the bbs
thereafter i edited :etc:x11:xorg;conf (sorry, keyboard is lost)
got xf86-input-keyboard and xf86-input-mouse and xf86-video-nv installed, as well as xorg-fonts-100dpi;
since it didn't do what i wanted, killed x and launched xorgcfg -textmode to reconfigure it, with no difference; shoud i try hwd -x ,
xorg7 starts in this location, but have issues left :
- keyboard configuration is lost in x : capital, accentuated are lost; i'm on a international (105) fr keyboard
- mouse scroll is gone
- the shift keys do not allow me to select any string (but the middle mouse button does)
cannot find yet a related topic that would give me some hint on how to solve this;
can someone give a hand on this issue please ,
/etc/X11/xorg;conf :
Section "ServerLayout"
Identifier "XFree86 Configured"
Screen 0 "Screen0" 0 0
Section "Files"
RgbPath "/usr/share/X11/rgb"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/misc:unscaled"
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/100dpi:unscaled"
Section "Module"
#Load "glx" Unsupported with Composite extension
Load "ddc" # ddc probing of monitor
Load "dbe"
Load "extmod"
Load "bitmap" # bitmap-fonts
Load "type1"
Load "freetype"
Load "record"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "keyboard"
Option "CoreKeyboard"
Option "XkbRules" "xfree86"
Option "XkbModel" "pc105"
Option "XkbLayout" "fr"
Option "XkbOptions" "compose:rwin"
#Option "XkbVariant" "nodeadkeys" ## accents ds les consoles, mais empeche les accents circonflexes dans les applis X
EndSection
Section "InputDevice"
Identifier "PS/2 Mouse"
Driver "mouse"
Option "Protocol" "auto"
Option "ZAxisMapping" "4 5"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "false"
Option "Emulate3Timeout" "70"
Option "SendCoreEvents" "true"
EndSection
Section "Monitor"
Identifier "Monitor0"
### Comment all HorizSync and VertSync values to use DDC:
HorizSync 30.0 - 97.0
VertRefresh 50.0 - 180.0
Section "Device"
#Driver "vesa"
#Driver "nvidia"
Identifier "Card0"
Driver "nv"
VendorName "All"
BoardName "All"
Card "NVIDIA GeForce"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultDepth 24
Option "DPMS"
Option "nvagp" "1"
# should be switched off *if* the system crash:
Option "RenderAccel" "true"
#Option "AllowGLXWithComposite"
SubSection "Display"
Depth 1
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection

Trying out ...
is this writen somewhere and i missed it ?
It seems to solve all of my keyboard & mouse issues.
Only is the cursor quite bizarre ; when i go left with the [left arrow],the cursor shows in every position it goes (dunno if one can visualize this!), and doesn't blink anymore. Anyway that's just a detail that I'l cope with later.
Thanks a lot Cerebral

FIX: FireWire communication issue solved - What worked for me

After installing the iPod Updater 2006-01-10, I found that my FireWire devices (not just my iPod) no longer worked. After much messing about with all the suggestions I found online (none of which worked) I've managed to sort out the FireWire communication issues I had.
you can read about the exact issues I had here:
http://forums.kustompcs.co.uk/showthread.php?t=35034
and here:
http://discussions.apple.com/message.jspa?messageID=1562072
Unfortunately those looking for a quick fix will be disappointed, I had to:
a) Send my iPod Mini back to Apple, which was promptly replaced
b) Totally re-install Windows (including drive format)
c) Borrow the install CD that came with my friends iPod, which had a later version of iPod Updater (2005-10-12) than the one I had on my install CD, but earlier than the dreaded 2006-01-10
If anyone needs this updater (as it's impossible to find an earlier one on Apple's website) drop me your email in here and I'll send you the web address to download it. This is basically a ZIP of the original CD, totally virus free (for those that are worried) and appears to work fine.
If Apple have an issue with this, then why don't you fix the link on your site to this updater; this is simply my response to the complete lack of response from Apple on this matter.
A quick note about the: 'connection rate=S100 ERROR'.
If you discover you have this error when you test your iPod in diagnostic mode; find out how to do this here:
http://www.methodshop.com/mp3/ipodsupport/diagnosticmode/index.shtml
Then it appears there is nothing you can do to fix this other than sending it back to Apple. No amount of restoring will solve it.
I hope this helps someone out there! I've yet to fix the issue with my LaCie drive (basically it needs sending back) which if anything proves that whatever screwed my system did something to the hardware on a low level, it wasn't a Windows software issue, because after re-installing it, I download SP2 and ALL the latest hotfixes, if that was the cause, it would have done it again.
This leaves one culprit - the iPod Updater 2006-01-10, as this was the only software I installed at the time both of my FireWire devices went down, avoid it like the plaque.
Regards
Matt

After installing the iPod Updater 2006-01-10, I found that my FireWire devices (not just my iPod) no longer worked. After much messing about with all the suggestions I found online (none of which worked) I've managed to sort out the FireWire communication issues I had.
you can read about the exact issues I had here:
http://forums.kustompcs.co.uk/showthread.php?t=35034
and here:
http://discussions.apple.com/message.jspa?messageID=1562072
Unfortunately those looking for a quick fix will be disappointed, I had to:
a) Send my iPod Mini back to Apple, which was promptly replaced
b) Totally re-install Windows (including drive format)
c) Borrow the install CD that came with my friends iPod, which had a later version of iPod Updater (2005-10-12) than the one I had on my install CD, but earlier than the dreaded 2006-01-10
If anyone needs this updater (as it's impossible to find an earlier one on Apple's website) drop me your email in here and I'll send you the web address to download it. This is basically a ZIP of the original CD, totally virus free (for those that are worried) and appears to work fine.
If Apple have an issue with this, then why don't you fix the link on your site to this updater; this is simply my response to the complete lack of response from Apple on this matter.
A quick note about the: 'connection rate=S100 ERROR'.
If you discover you have this error when you test your iPod in diagnostic mode; find out how to do this here:
http://www.methodshop.com/mp3/ipodsupport/diagnosticmode/index.shtml
Then it appears there is nothing you can do to fix this other than sending it back to Apple. No amount of restoring will solve it.
I hope this helps someone out there! I've yet to fix the issue with my LaCie drive (basically it needs sending back) which if anything proves that whatever screwed my system did something to the hardware on a low level, it wasn't a Windows software issue, because after re-installing it, I download SP2 and ALL the latest hotfixes, if that was the cause, it would have done it again.
This leaves one culprit - the iPod Updater 2006-01-10, as this was the only software I installed at the time both of my FireWire devices went down, avoid it like the plaque.
Regards
Matt

Color Management Issues Solved in LR 1.1?

Long tempted to switch from Elements 5.0 to LR (or to integrate the two), I have held off because I've read on this forum dozens, probably hundreds, of complaints about LR 1.0 and color management. Some of these questions were clearly from ignorance, I know (such as not understanding the difference between the color space used by monitors and that used by printers). But many other were from sophisticated users all of whom began their comments or questions with "Works perfectly in Photoshop, but in LR ..." See, for example, http://adobeforums.com/cgi-bin/webx/.3bc41850/39 , which describes difficulty in getting LR to produce acceptable prints. To my mind, LR 1.0 had color management problems even if the highest end users managed to work around them. I don't want to buy into problems, not being a sophisticated user yet myself. So here is my queston: Does LR 1.1 solve these problems? That is, does LR 1.1 work as easily, or almost as easily, as Photoshop (say with the HP b9180, which has a PS plugin)? Thanks in advance.

The problem is that lightroom is somehow throwing the default profile that is set in colorsync into the mix. Which is something that Photoshop is not doing. So any printer profiles built by printing a target with PS is not going to be accurate when printed through Lightroom unless the default profile for you printer is Generic RGB Profile or something close.
Here is what I have posted elsewhere about my discovery of this issue.
I discovered something today that just might be the answer to the color printing problems from Lightroom.
First of all, all prints from PS and Lightroom was done with the same color management workflow with the profiles set in the application and color management turned off in the printer driver. This was to a Canon iPF9000.
Started when I tried to print from a new MacPro with Lightroom. Colors were not right.
Went to the G5 and printed from lightroom same file same settings same profile, color was correct.
Printed same file same setting same profile from PS on the MacPro. Color was correct.
So started printing and saving as PDF from the print dialog. Open the PDF files in Acrobat and checking embedded profile with Pitstop.
Here are the results.
Lightroom on Macpro: iPF9000 Paper profile. This was much darker with way to much yellow.
Photoshop of Macpro: Generic RGB
Lightroom on G5: sRGB v1.20 (Canon)
I had uninstall the sRGB v1.20 (Canon) profile from the colorsync folder on the MacPro. Added sRGB v1.20 (Canon) back in and guess what. sRGB v1.20 (Canon) in the PDF now generated from Lightroom. Print to the printer from Lightroom on the MacPro and it now printed correct.
Now got to thinking were does Lightroom get this (sRGB v1.20 (Canon) profile from. So checked in the Colorsync utility to see what the default profile for the iPF9000 is and sure enough it was sRGB v1.20 (Canon). Ok so what happens if I change the default profile in the Colorsync utility to Adobe RGB. Now guess what the Lightroom generated PDF now shows Adobe RGB as the embedded profile.
PS printed to PDF showed Generic RGB profile no matter what I set as the default profile in the Colorsync Utility.
Clearly Lightroom behaves differently when printing when a different default profile is selected for a printer. On Windows this could be the same as one can set in the printer properties (at least for the iPF9000) the default profile to automatic or set a different default profile manually.
This raises an interesting question as to what is really going on with print files set to a printer. Especially printers with much larger gamuts than sRGB.
Could this be the source of the strange Lightroom printing problems?
I do know when I have tried to make a profile from a printed target in LR I could not get accurate color. But the profile generated for a target printed in PS works fine in LR.

Permissions/Ownership issue? [Solved]

Similar Messages

Maybe you are looking for