Summary: | app-text/calibre-0.8.39 - /var/tmp/portage/app-text/calibre-0.8.39/temp/environment: line 1373: 7882 Errore di segmentazione "$(PYTHON)" "${setup_file#*|}" | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Fabio Coatti <fabio.coatti> |
Component: | Current packages | Assignee: | Zac Medico <zmedico> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | aboynes, jfostiguy, kripton |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Fabio Coatti
2012-02-17 13:47:48 UTC
Please attach the environment file to this bug report. I have exactly the same issue. I'm also experiencing this problem. Just after it happens, check the output of `dmesg | tail` for a segfault fault message and post it here. (In reply to comment #4) > Just after it happens, check the output of `dmesg | tail` for a segfault fault > message and post it here. python2.7[24755]: segfault at 0 ip b6cc2b69 sp bfe480d0 error 6 in sip.so[b6cb7000+12000] (In reply to comment #5) > python2.7[24755]: segfault at 0 ip b6cc2b69 sp bfe480d0 error 6 in > sip.so[b6cb7000+12000] It looks like bug 345331, which you can solve by rebuilding PyQt4 and emerge pykde4. indeed. emerge PyQt4 && emerge pykde4 && emerge calibre works just fine. Thanks! (In reply to comment #6) > It looks like bug 345331, which you can solve by rebuilding PyQt4 and emerge > pykde4. Helped me here, too. Would be worth an einfo or something IMHO The steps in bug 345331 didn't work for me. I still get errors when trying to emerge the gentoo package. For now I am using their binary for 0.8.40, which works. (In reply to comment #6) > (In reply to comment #5) > > python2.7[24755]: segfault at 0 ip b6cc2b69 sp bfe480d0 error 6 in > > sip.so[b6cb7000+12000] > > It looks like bug 345331, which you can solve by rebuilding PyQt4 and emerge > pykde4. Yep. Works for me. emerge PyQt4 && emerge pykde4 && emerge calibre Worked for me as well. Should I submit a separate bug report, since my issue seems unrelated, or give information about my situation in this one? (In reply to comment #12) > Should I submit a separate bug report, since my issue seems unrelated, or give > information about my situation in this one? Yes, please file a new bug. (In reply to comment #8) > (In reply to comment #6) > > It looks like bug 345331, which you can solve by rebuilding PyQt4 and emerge > > pykde4. > > Helped me here, too. Would be worth an einfo or something IMHO A message like that is meaningless unless the person is experiencing this particular issue. I suppose we could have it search dmesg output for a message like the one in comment #5, and if that's found then suggest to rebuild PyQt4 and pykde4. Had the same problem with both versions 0.8.39 and .40, which went away after remerging pykde4 (had already remerged PyQt4 after updating sip). Funny thing is that I thought I'd already remerged pykde4 too (am pretty sure about that actually). So for the someone who still has this problem: Check dmesg|tail for a message complaining about sip.so after you have failed to emerge calibre - and if it's there, try to remerge PyQt4 and pykde4 again. Do it in two different statements, don't put them on the same line - that's what I believe didn't work for me. (Does that even make sense?) *** This bug has been marked as a duplicate of bug 345331 *** |