I cannot start gajim at all, it always crashes in the same way. I have tried with gajim 0.13.3 and 0.13.4 and they crash in the same way and downgrading to python 2.6.4-r1 or 2.6.5-r2 didn't solve the issue either Reproducible: Always Steps to Reproduce: 1. Try to start gajim 2. 3. Actual Results: Crashes with the same error despite gajim version: Traceback (most recent call last): File "gajim.py", line 162, in <module> from ctypes import CDLL File "/usr/lib64/python2.6/ctypes/__init__.py", line 546, in <module> CFUNCTYPE(c_int)(lambda: None) MemoryError Expected Results: Gajim starts and operates like it should
Created attachment 242559 [details] emerge --info
I have checked the logs and dmesg and it does not appear to be an hardened issue, there is nothing in dmesg that say that PaX or Grsec interfered.
@python COuld you comment on that?
https://bugzilla.redhat.com/show_bug.cgi?id=621887
https://bugzilla.gnome.org/show_bug.cgi?id=623965
same here, but i'm sure it's hardened related. after executing sysctrl kernel.pax.softmode=1 gajim starts as expected.
Confirming with iotop-0.4.1 on ia64 running 2.6.32-hardened-r14: Traceback (most recent call last): File "/usr/bin/iotop-2.6", line 9, in <module> from iotop.ui import main File "/usr/lib/python2.6/site-packages/iotop/ui.py", line 31, in <module> from iotop.data import find_uids, TaskStatsNetlink, ProcessList, Stats File "/usr/lib/python2.6/site-packages/iotop/data.py", line 39, in <module> import ctypes File "/usr/lib/python2.6/ctypes/__init__.py", line 546, in <module> CFUNCTYPE(c_int)(lambda: None) MemoryError Suggesting new summary: "Python exits with MemoryError after update"
Daniel: Did you try downgrading your hardened kernel? I think the last version it worked for me was about -r10, but I do not have the time atm to test this. Justin: Are you sure your redhat-bugzilla links are related to this issue? They seem to be about segfaults in gtk and gnome.
No I did not try to downgrade the hardened kernel, could give it a try. uname -r reports: 2.6.34-hardened-r1-UL30VT I'll try an 2.6.32 kernel when I get home and have time and see if that fixes it.
(In reply to comment #9) > 2.6.34-hardened-r1-UL30VT > I'll try an 2.6.32 kernel I'm on 32-r14, which also exposes this problem (but I expect 32-r10 to not show the issue). Just try to undo the last (few) kernel upgrades you did.
(In reply to comment #10) > (In reply to comment #9) > > 2.6.34-hardened-r1-UL30VT > > I'll try an 2.6.32 kernel > I'm on 32-r14, which also exposes this problem (but I expect 32-r10 to not show > the issue). Just try to undo the last (few) kernel upgrades you did. > I'll try -r10 and see what happens
After talking to spender at #grsecurity@OFTC it is apparent that it is an hardened issue. After doing paxctl -m /usr/bin/python2.6 it worked like it should. The reason, that spender gave, was that they recently changed how grsec implements mprotect. Before when a program asked for an RWX memory mapping it would just demote it down to RW but now it rejects it instead. This causes issues for python2.6 it seems :P
*** This bug has been marked as a duplicate of bug 329499 ***
