thanks for the ideas. I don't think this is a problem with the systems, or picasa for that matter - but rather an issue how pacasa runs. We have 20 other software that work OK... Mathematica, Matlab etc... All users belong to the group "domain users".
for instance this is a user home dir: drwx------ 49 dem1 domain users 4096 2011-05-20 15:07 dem1 My guess is that the user you are running as belongs to the "linux video" group on your system. i do not know how to add a domain group to the local video group... which I think will fix the problem. The fix suggested by the error pop up when you start pacasa "chmod 666 /dev/nvidia0 /dev/nvidia1": Works when run as root and lets the logged in user run pacasa - but a simple log out and back in changes the them back to 660. Thanks for the help thinking about my problem. Dave/ On Mon, May 23, 2011 at 2:51 PM, Patrick Shanahan <[email protected]> wrote: > * David E. Marshall <[email protected]> [05-23-11 16:28]: >> We find that two files in /dev: >> >> crw-rw---- 1 root video 195, 0 May 19 14:08 nvidia0 >> crw-rw---- 1 root video 195, 255 May 19 14:08 nvidiactl >> >> are causing the picasa error: > > which you mentioned, but out of context :^) > > you *do* have a problem, > ll /dev/nvid* > crw-rw-rw- 1 root root 195, 0 May 23 09:22 /dev/nvidia0 > crw-rw-rw- 1 root root 195, 255 May 23 09:22 /dev/nvidiactl > >> "/dev/nvidia0 pr /dev/nvidiact1 are not accessible. Picasa will crash >> if these files are not accessible. To fix this, as root, please run: >> chmod 666 /dev/nvidia0 /dev/nvidia1" >> >> If you su to root and make the change as suggested - picasa will start >> and run without error. >> >> If you log out and back in (as the same or a different user) the >> files revert to 660 and we get the above error when picasa starts. >> >> All the suggested fixes that I can find we are unable to do. Ether >> because the suggested file we should modify is no-existent in suse >> 11.4 or because the fix did not fix the problem. > > well, something is amiss. > > Log in as a user and w/o running anything, check the perms > > then run: > sudo SuSEconfig > > this should set system file perms to the correct values. > > you have set system file perms to: easy > chk: yast2 -> security and users -> security center and hardening > > past that, I can only thing of two possibilities: > win domain problem > system is rooted. > > if *all* of your system exhibit this behavour, I would believe it is a > "win domain problem". > > FLASH; I changed perms on my system to match yours and ran picasa as a > normal user w/o a problem. Something else is causing your problems > besides the perms (in addition to). I would guess your problem lies in > the "win domain" access. > >> Computer are part of a win domain - we use winbind to authenticate. If >> I could figure out how to add a win domain group to the linux "video" >> group I think that would fix the problem - but as yet I don't see >> how... > > I know neither ??? > > If I can help further... I am around :^) > > -- > (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 > http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 > http://en.opensuse.org openSUSE Community Member > Registered Linux User #207535 @ http://counter.li.org > > -- > You received this message because you are subscribed to the Google Groups > "Google-Labs-Picasa-for-Linux" group. > To post to this group, send email to > [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-labs-picasa-for-linux?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google-Labs-Picasa-for-Linux" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-labs-picasa-for-linux?hl=en.
