Bug 580115

Summary:

g_assert failure inside "gnome_program_module_addtolist" running "./session-emacs-daemon"

Product:

[Fedora] Fedora

Reporter:

Ben Liblit <liblit>

Component:

gnome-python2

Assignee:

Colin Walters <walters>

Status:

CLOSED INSUFFICIENT_DATA

QA Contact:

Fedora Extras Quality Assurance <extras-qa>

Severity:

medium

Docs Contact:

Priority:

low

Version:

CC:

dmalcolm, ivazqueznet, james.antill, jonathansteffan, walters

Target Milestone:

---

Target Release:

---

Hardware:

i686

OS:

Linux

Whiteboard:

abrt_hash:c34cc3d9cacb83c630fab865b93c06579c55b05b

Fixed In Version:

Doc Type:

Bug Fix

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2010-04-08 15:34:26 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:

Attachments:

Description	Flags
File: backtrace	none

Description Ben Liblit 2010-04-07 14:10:50 UTC

abrt 1.0.8 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/bin/python ./session-emacs-daemon -n
component: python
executable: /usr/bin/python
kernel: 2.6.32.9-70.fc12.i686
package: python-2.6.2-4.fc12
rating: 4
reason: Process /usr/bin/python was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)

Comment 1 Ben Liblit 2010-04-07 14:10:52 UTC

Created attachment 404964 [details]
File: backtrace

Comment 2 Dave Malcolm 2010-04-07 20:26:07 UTC

Thank you for reporting this bug.

How reproducible is this problem?  If you run the program from a terminal, is an error message printed?

What is the output of running the following command?
  rpm -q libgnome gnome-python2-gnome

Looking at the backtrace, it looks like the problem occurred in the program's single thread in frame #5 in gnome_program_module_addtolist, as called in frame #9 by the Python bindings to libgnome (in the gnome-python2-gnome RPM).

Reassigning component from "python" to "gnome-python2";  hopefully the gnome-python2 maintainer will be able to figure this out further or reassign as necessary.

It may be a bug in libgnome, or in the script.  (Arguably if the script is calling into libgnome in an unexpected way, the bindings should protect against that, though I'm not sure if that's what's happening)

Comment 3 Ben Liblit 2010-04-08 01:58:13 UTC

I regret to say that I do not know how to reproduce the problem.  The Python script that was running when it happened has even changed since then, so I am just not able to give more information than what appeared in the original failure report.  :-(

Comment 4 Dave Malcolm 2010-04-08 15:34:26 UTC

Thanks for responding.

I'm glad it's no longer crashing, but without a reproducer, it's going to be hard to address this further, so I'm going to close this report out with the "not enough info" status.

If it happens again, feel free to reopen this bug.

Thanks again for the information.