In dmesg: > You have old & broken userspace please consider updating mesa [ebuild R ] media-libs/mesa-7.8.2 USE="motif nptl xcb -debug (-gallium) -pic (-selinux)" VIDEO_CARDS="radeon radeonhd -intel -mach64 -mga -none -nouveau -r128 -savage -sis -svga -tdfx -via" 0 kB [ebuild R ] sys-kernel/xen-sources-2.6.34 USE="symlink -build -deblob" 0 kB [ebuild R ] x11-apps/mesa-progs-7.7 0 kB are all latest available versions for me. My kernel is out since end of june. I updated portage this morning. So, for me, something in gentoo is at least one month "too old", or not updated yet. Or could be a kernel misconf ? then the message is not clear.
Which python version do you use?
[ebuild R ] dev-lang/python-3.1.2-r3 USE="doc examples gdbm ipv6 ncurses readline ssl threads tk (wide-unicode) xml -build -sqlite -wininst" 0 kB uranus ~ # eselect python list Available Python interpreters: [1] python2.6 * [2] python3.1 uranus ~ # grrrr ... Python API changed again ? python-updater did not the job ? I read all my ewarns messages; maybe the update informations were given in einfo ?
Try to downgrade to python 2.x.x.
(In reply to comment #3) > Try to downgrade to python 2.x.x. > hmm, yes you have 2.6.
dhp@uranus ~ $ eix dev-lang/python [I] dev-lang/python Available versions: (2.4) 2.4.6 (2.5) 2.5.4-r4 (2.6) 2.6.4-r1{tbz2} 2.6.5-r2{tbz2} ~2.6.5-r3 (2.7) [M]~2.7 (3.1) 3.1.2-r3{tbz2} ~3.1.2-r4 {-berkdb bootstrap build +cxx doc elibc_uclibc examples gdbm ipv6 +ncurses +readline sqlite +ssl +threads tk +wide-unicode wininst +xml} Installed versions: 2.6.5-r2(2.6){tbz2}(00:15:41 29/05/10)(berkdb doc examples gdbm ipv6 ncurses readline ssl threads tk wide-unicode xml -build -elibc_uclibc -sqlite -wininst) 3.1.2-r3(3.1){tbz2}(15:49:31 30/05/10)(doc examples gdbm ipv6 ncurses readline ssl threads tk wide-unicode xml -build -elibc_uclibc -sqlite -wininst) Homepage: http://www.python.org/ Description: Python is an interpreted, interactive, object-oriented programming language. dhp@uranus ~ $
I would think that it will not work with python 3.1. But you can try. I will believe it may be beneficial to ask the python, but I'm not sure.
(In reply to comment #6) > I would think that it will not work with python 3.1. But you can try. > I will believe it may be beneficial to ask the python, but I'm not sure. > :) ask them about this error if you can python...
ask who about what ?
(In reply to comment #8) > ask who about what ? > userspace
I have read a small about this error and i look like it's a harmless warning.
I did not understand any of your message. Harmless messages always become fatal errors one day or an other.
(In reply to comment #11) > I did not understand any of your message. > > Harmless messages always become fatal errors one day or an other. > You are using python 2.6 by default, so there is not a problem here. If you have problems with the mesa, it is not this warning is the problem.
Would you mind telling what program exactly in what circumstances produces those messages ? To the other party: why should python have anything to do with this message ?
(In reply to comment #13) > To the other party: why should python have anything to do with this message ? > Absolutely unrelated to python, of course. Seems purely mesa-related: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=569663 Henrik: Please don't comment unless you really know what you are talking about. Thanks in advance.
(In reply to comment #13) > Would you mind telling what program exactly in what circumstances > produces those messages ? It's the last line of dmesg. Ah, I find it in /var/log/messages just after some other X error ... and now, I understand which app causes this: Jul 24 19:11:14 uranus -bash: HISTORY: PID=10161 UID=1000 glxinfo | grep rend Jul 24 19:11:21 uranus -bash: HISTORY: PID=10161 UID=1000 glxgears Jul 24 19:11:21 uranus kernel: You have old & broken userspace please consider updating mesa Jul 24 19:11:38 uranus -bash: HISTORY: PID=11513 UID=1000 M If i run glxgears a second time, there is no second warning. (once more, bash_history is saving us) Notes: - I run Xinerama - I did not use LIBGL_ALWAYS_SOFTWARE=1 - glxinfo | grep rend => Mesa DRI R600 (RS880 9710) 20090101 TCL DRI2 - glxgears show nicely on one monitor out of 6 (it shows on all 6 when I do use LIBGL_ALWAYS_SOFTWARE=1 - thus, I don't have xrandr activated - I wonder why I have DRI at all ... (discussion on way in Xorg Guzilla) Any way, all this should not impact: kernel says that Gentoo Mesa is deprecated. Since I am using latest unstable Mesa, either we need a Mesa update, or the kernel is wrong about something. > To the other party: why should python have anything to do with this message ? No clue. Ask Henrik.
(In reply to comment #14) > Henrik: > Please don't comment unless you really know what you are talking about. Thanks > in advance. +1 Also stop using our bug tracker as a support forum.
(In reply to comment #0) > In dmesg: > > You have old & broken userspace please consider updating mesa /var/tmp/portage/sys-kernel/vanilla-sources-2.6.35_rc6/work/linux-2.6.35-rc6/drivers/gpu/drm/radeon/r600_cs.c: printk_once(KERN_WARNING "You have old & broken userspace please consider updating mesa\n");
From what I understand there are some changes in mesa git that is not released yet that provide some kind of acceleration. You can ignore this warning.
