Cinelerra_don't_play_in_feisty

Bug #102249 reported by pablopedro
6
Affects Status Importance Assigned to Milestone
linux-source-2.6.20 (Ubuntu)
Won't Fix
Undecided
Unassigned
linux-source-2.6.22 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

void MWindow::init shm (): warning: /proc/sys/kernel/shmmax is 0*2000000, wich is too low

ProblemType: Bug
Architecture: i386
Date: Tue Apr 3 09:12:31 2007
DistroRelease: Ubuntu 7.04
Uname: Linux pedra-laptop 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686 GNU/Linux

Revision history for this message
Cruncher (ubuntu-wkresse) wrote :

Bug #105907 has a link to a (French) page that describes how to fix this (although I haven't tried it): http://fr.lprod.org/wiki/doku.php?id=video:cinelerra:erreur_lancement
In essence, you need to edit /etc/sysctl.conf , add the line "kernel.shmmax = 0x7fffffff", and run "sysctl -p".

HTH

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Now that the 7.10 Gutsy Gibbon release of Ubuntu is out, we were wondering if you can still reproduce this issue. Could you please download and try the new version of Ubuntu from http://www.ubuntu.com/getubuntu/download and report back your results. For more information regarding the kernel team bug policy, please refer to https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks again and we appreciate your help and feedback.

Changed in linux-source-2.6.20:
status: New → Incomplete
Revision history for this message
Cruncher (ubuntu-wkresse) wrote :

Starting the same Cinelerra version under 7.10 yields the same problem. I still haven't tried messing with /etc/sysctl.conf yet.
http://cvs.cinelerra.org/getting_cinelerra.php doesn't seem to have a Gutsy version yet.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

I'm not convinced this is an actual bug in the kernel. /proc/sys/kernel/shmmax controls the maximum amount of memory to be allocated for shared memory. The default is 32Mb. You can adjust this value by echoing whatever new value you want to this file. Can you 'cat /proc/sys/kernel/shmmax/' and let me know what your current value is? I assume it should be 33554432. If not, it suggests that you've modified this value which is beyond our control. Please get back to us with your findings. Thanks.

Changed in linux-source-2.6.22:
status: New → Incomplete
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Against linux-source-2.6.20 this bug does not meet the criteria for a stable release update and is being marked as Won't Fix. This is however still being monitored against linux-source-2.6.22. You can learn more about the stable release update process at https://wiki.ubuntu.com/StableReleaseUpdates . Thanks!

Changed in linux-source-2.6.20:
status: Incomplete → Won't Fix
Revision history for this message
Cruncher (ubuntu-wkresse) wrote :

My setting is still at the default, 33554432.
It seems there are a bunch of cinelerra packages for Gutsy out there now, but I couldn't get any of them to work on my AMD K7 with an older nvidia card, due to some OpenGL problem (glDeleteShader undefined).

However, from what I gathered from various forums is, that the kernel.shmmax = 0x7fffffff is still requested by the program.
http://ubuntuforums.org/showthread.php?t=596160
http://ubuntuforums.org/showthread.php?t=623589
http://cv.cinelerra.org/docs/wiki/doku.php?id=english_manual:cinelerra_cv_en_2#ubuntu

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

This is not a bug in the kernel but rather a feature required by cinelerra. The following links provide some information as well as workarounds. Thanks.

http://cv.cinelerra.org/docs/wiki/doku.php?id=english_manual:cinelerra_cv_en_2#running_cinelerra
http://cv.cinelerra.org/docs/wiki/doku.php?id=english_manual:cinelerra_cv_en_21#freeing_more_shared_memory

Changed in linux-source-2.6.22:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.