Bug 429970
| Summary: | python crashes with assertion | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Bernard Johnson <bjohnson> |
| Component: | gnome-python2 | Assignee: | Matthew Barnes <mbarnes> |
| Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | low | ||
| Version: | 8 | CC: | james.antill, katzj, michel |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2008-11-13 12:08:33 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 428838 | ||
|
Description
Bernard Johnson
2008-01-24 01:15:51 UTC
The only time I've seen this is with external to python .so modules. Unable to reproduce this using the pygobject2 package from Rawhide: python-2.5.1-15.fc8 pygobject2-2.14.1-1.fc9 Is running and quitting conduit after a fresh install sufficient or do I need to configure conduit in some way for this crash to occur? Yes, starting and stopping are enough to trigger it. I removed my ~/.conduit
directory and it didn't change anything.
When I tried to test by upgrading pygobject2, I get this:
[bjohnson@localhost ~]$ conduit
Traceback (most recent call last):
File "/usr/bin/conduit.real", line 21, in <module>
import conduit
File "/usr/lib/python2.5/site-packages/conduit/__init__.py", line 24, in <module>
import gobject
File "/usr/lib/python2.5/site-packages/gtk-2.0/gobject/__init__.py", line 30,
in <module>
from gobject.constants import *
File "/usr/lib/python2.5/site-packages/gtk-2.0/gobject/constants.py", line 22,
in <module>
from _gobject import type_from_name
ImportError: /usr/lib/python2.5/site-packages/gtk-2.0/gobject/_gobject.so:
undefined symbol: g_assertion_message_expr
[bjohnson@localhost ~]$
Are there other packages you upgraded to test with?
This is a different bug, it's because glib2 doesn't have versioned symbols and you need the new version of glib2. See rhbz#428847 for another glib2 casualty I can confirm that updating to rawhide's pygobject2 and glib2 does not fix this problem. Which problem ... the missing g_assertion_* symbol? Or the initial something corrupts python's memory and then it dies? (In reply to comment #7) > Which problem ... the missing g_assertion_* symbol? Or the initial something > corrupts python's memory and then it dies? > The memory corruption. On a Rawhide system, the bug does not occur, though. Perhaps the entire Python stack needs to be updated? Setting to NEEDINFO until Bernard can check whether this bug is still present on a full Rawhide/Fedora 9 system. I've not been able to reproduce it myself. I pushed a conduit for rawhide 17 days ago, and haven't received any feedback on it good or bad. It is also a newer release than what I was working with before, so the bug may have been fixed. Following the thread at http://bugzilla.gnome.org/show_bug.cgi?id=509702#c28 it sounds like conduit was (ab)using gnome-vfs in irregular ways. I'm hoping the never version fixes it. I also have a F-8 version in updates-testing that I've not received any feedback on. Matthew, Can you look at https://bugzilla.redhat.com/show_bug.cgi?id=428838#c18 (and probably the 3 comments preceding) and see if you want to reassign this bug to gnome vfs bindings... It does look like a gnomevfs bug. The crash is coming from Python's garbage collector. Need to refresh my memory on how that algorithm works. Indeed, I can reproduce this with the sample code here: http://bugzilla.gnome.org/show_bug.cgi?id=509702#c28 Does gnome-vfs2 seem like the right place to bump this bug over to? Using the same sample code I mentioned in comment #14, I can't reproduce the crash anymore on Fedora 10. Is anyone still seeing this issue? I believe it only specifically affected F8. Thanks. closing then with the closest resolution to OBSOLETE that we have. |