From: stryder@telenet.be.invalid   
      
   On Tuesday 05 February 2013 08:28, unruh conveyed the following to   
   alt.os.linux.mandriva...   
      
   > I am running Madriva 2010.0 on one of my machines (and no I do not   
   > have the time to upgrade it). I made the mistake of updating it to the   
   > install all of the updates.   
   > Now firefox returns with an error message of something like   
   > .... libx...: unsatisfied reference to   
   > "cairo_surface_get_reference_count" (the dots are what I cannot   
   > remember) It however works if I su to root and run firefox from the   
   > command line. So it really sounds like a permission problem, but I   
   > have no idea where-- all the files in /usr/lib are rx permission for   
   > all.   
   >   
   > If I run firefox on that machine with X11 forwarding  from another   
   > machine   
   >  everything works fine.   
   > (Ie, I do   
   > ssh florid   
   > (florid is the name of the problematic machine)   
   > firefox   
   > so it is running on florid, but displaying on my local machine's X.)   
   >   
   > It is really really annoying when stuff like this happens.   
   >   
   > texmakerx worked before I did the update but now it says it cannot get   
   > a lock   
   > QtLockedFile::lock(): fcntl: No locks available   
   >   
   > Again I have no idea what the problem is. Again, it runs fine as root.   
   > (But in this case I get the same error from a remote machine)   
      
   Bill, I may be out on a limb here - okay, I /am/ - but here's a couple   
   of questions for you...:   
      
     1) Did the update also pull in a newer kernel?   
      
     2) If so, have you rebooted the machine?   
      
   The reason I am asking is because as it turned out in the Gentoo mailing   
   lists the other day, some device special files may not have been created   
   in the newest release of udev when the kernel is built without support   
   for (and automatic kernel-level mounting of) devtmpfs, leading to   
   similar problems - I can't really recall what they were, but they were   
   also suspect of permissions issues.   
      
   The problem could of course also be related to dbus.  As I understand   
   it, dbus too has changed quite a lot in the meantime.   
      
   --   
   = Aragorn =   
   (registered GNU/Linux user #223157)   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)