Hi,
On a CentOS4 I've updated kdelibs and everything that up2date has signaled me to, and now I get segmentation fault when running xmms (installed from the Centos4 dvd) and also when running gmplayer which is installed from DAG repository for EL4.
Is anyone in my position or it's just me? Do you know why?
Adrian
On 5/21/05, Adrian Coman adi.coman@gmail.com wrote:
Hi,
On a CentOS4 I've updated kdelibs and everything that up2date has signaled me to, and now I get segmentation fault when running xmms (installed from the Centos4 dvd) and also when running gmplayer which is installed from DAG repository for EL4.
Is anyone in my position or it's just me? Do you know why?
It's probably just you. Is the machine a reliable one? That is - has it been in service, in this configuration, for a long time? Or, was it recently added to/modified in some way, particularly with RAM and/or processor?
Also, when you run xmms/gmplayer does it die immediately or does it take a little while? Have you run anything else that his highly memory/cpu intensive?
Have you run any sort of hardware tests?
Greg
I was because my /tmp was mounted with noexec option. After I modified it back to exec, the crash didn't occure anylonger. Is this normal?
On 5/21/05, Greg Knaddison greg.knaddison@gmail.com wrote:
On 5/21/05, Adrian Coman adi.coman@gmail.com wrote:
Hi,
On a CentOS4 I've updated kdelibs and everything that up2date has signaled me to, and now I get segmentation fault when running xmms (installed from the Centos4 dvd) and also when running gmplayer which is installed from DAG repository for EL4.
Is anyone in my position or it's just me? Do you know why?
It's probably just you. Is the machine a reliable one? That is - has it been in service, in this configuration, for a long time? Or, was it recently added to/modified in some way, particularly with RAM and/or processor?
Also, when you run xmms/gmplayer does it die immediately or does it take a little while? Have you run anything else that his highly memory/cpu intensive?
Have you run any sort of hardware tests?
Greg _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Sun, 2005-05-22 at 01:23 +0300, Adrian Coman wrote:
I was because my /tmp was mounted with noexec option. After I modified it back to exec, the crash didn't occure anylonger. Is this normal?
Not sure if it is normal (as in, it should happen) ... but I can verify that it does happen if /tmp is mounted as noexec
and who should know this? my opinion is that there should be no need to execute anything from /tmp, from security reasons.
On 5/22/05, Johnny Hughes mailing-lists@hughesjr.com wrote:
On Sun, 2005-05-22 at 01:23 +0300, Adrian Coman wrote:
I was because my /tmp was mounted with noexec option. After I modified it back to exec, the crash didn't occure anylonger. Is this normal?
Not sure if it is normal (as in, it should happen) ... but I can verify that it does happen if /tmp is mounted as noexec
BodyID:65298394.2.n.logpart (stored separately)
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On 5/22/05, Adrian Coman adi.coman@gmail.com wrote:
and who should know this? my opinion is that there should be no need to execute anything from /tmp, from security reasons.
This is not the first time I've seent his point discussed. Generally the programs that require execution of something in /tmp have that location as a tuneable parameter. I think mailman/spamassasin/something was the last time I saw this.
Greg
On 5/22/05, Greg Knaddison greg.knaddison@gmail.com wrote:
On 5/22/05, Adrian Coman adi.coman@gmail.com wrote:
and who should know this? my opinion is that there should be no need to execute anything from /tmp, from security reasons.
This is not the first time I've seent his point discussed. Generally the programs that require execution of something in /tmp have that location as a tuneable parameter. I think mailman/spamassasin/something was the last time I saw this.
Also not the first time I've heard this, but apparently some products (no time to google) as a standard distribution want to use /tmp for executables. Sad but true apparently.
On Sun, 2005-05-22 at 08:50 -0600, Greg Knaddison wrote:
On 5/22/05, Adrian Coman adi.coman@gmail.com wrote:
and who should know this? my opinion is that there should be no need to execute anything from /tmp, from security reasons.
This is not the first time I've seent his point discussed. Generally the programs that require execution of something in /tmp have that location as a tuneable parameter. I think mailman/spamassasin/something was the last time I saw this.
Greg
Lots of things require executing tmp files ... though you might be able to change it to /var/tmp ... for example
(as Greg said, by changing a config file)
This is an upstream issue ... and I saw some stuff in the redhat bugzilla about some programs that have this issue, xmms is not one of the ones listed though.
We don't normally fix issues like this in CentOS ... because we are supposed to track upstream programs _exactly_ ... including their bugs.
If you want to fix it and maintain your own package, I'll try to help :)
OR ... make an entry in the RH bugzilla for RHEL4 and xmms
We don't normally fix issues like this in CentOS ... because we are supposed to track upstream programs _exactly_ ... including their bugs.
Not really correct: I installed the rpm from xmms.org and it works perfectly with /tmp mounted with noexec option. Seems that the xmms compilation or the included xmms configuration are not the safest ones. I didn't try with mplayer, but I guess it's something similar.
If you want to fix it and maintain your own package, I'll try to help :)
OR ... make an entry in the RH bugzilla for RHEL4 and xmms
this should be done .. where exactly can I do this?
On Sun, 2005-05-22 at 20:44 +0300, Adrian Coman wrote:
We don't normally fix issues like this in CentOS ... because we are supposed to track upstream programs _exactly_ ... including their bugs.
Not really correct: I installed the rpm from xmms.org and it works perfectly with /tmp mounted with noexec option. Seems that the xmms compilation or the included xmms configuration are not the safest ones. I didn't try with mplayer, but I guess it's something similar.
I meant RHEL, not xmms. That one probably plays DVDs and mp3s too :)
If you want to fix it and maintain your own package, I'll try to help :)
OR ... make an entry in the RH bugzilla for RHEL4 and xmms
this should be done .. where exactly can I do this?
If you file a bug at http://bugs.centos.org/ .... I'll file one with RH at http://bugzilla.redhat.com/ .
If you file a bug at http://bugs.centos.org/ .... I'll file one with RH at http://bugzilla.redhat.com/ .
I try to enter a bug on centos but none of the categories from http://bugs.centos.org/bug_report_advanced_page.php is suitable for such a report: I only see DHCP, Missing component, Mysql, anaconda, kernel, mailman, up2date, yum.
What category should I choose?
Adrian Coman wrote:
If you file a bug at http://bugs.centos.org/ .... I'll file one with RH at http://bugzilla.redhat.com/ .
I try to enter a bug on centos but none of the categories from http://bugs.centos.org/bug_report_advanced_page.php is suitable for such a report: I only see DHCP, Missing component, Mysql, anaconda, kernel, mailman, up2date, yum.
What category should I choose?
File it off under Missing Component.
-
Adrian Coman -
Collins Richey -
Greg Knaddison -
Johnny Hughes -
Karanbir Singh