Bug 175633 - irssi segfaults on startup in theme_init_module
Summary: irssi segfaults on startup in theme_init_module
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: irssi
Version: rawhide
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Dams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: FE5Target
TreeView+ depends on / blocked
 
Reported: 2005-12-13 16:36 UTC by David Cantrell
Modified: 2007-11-30 22:11 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-08-28 14:22:37 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
strace irssi > strace.log 2>&1 (19.12 KB, text/plain)
2006-01-26 19:40 UTC, Jasper O. Hartline
no flags Details

Description David Cantrell 2005-12-13 16:36:19 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20051211 Fedora/1.5-1.1 Firefox/1.5

Description of problem:
When I try to start irssi, it fails:

dcantrel@mortise:~$ irssi

** (process:12826): CRITICAL **: theme_init_module: assertion `formats != NULL' failed
Segmentation fault (core dumped)


Version-Release number of selected component (if applicable):
0.8.10-0.2.rc8.fc5

How reproducible:
Always

Steps to Reproduce:
1. Open terminal
2. Type irssi
3. See irssi crash
  

Actual Results:  segfault

Expected Results:  irssi should have run

Additional info:

Comment 1 Dams 2005-12-13 20:04:56 UTC
I'll update to final 0.8.10 release in a few days, I dont see this problem on
fc4. Any specific stuff in irssi configuration ? Modules, scripts, etc.

Comment 2 David Cantrell 2005-12-13 21:33:26 UTC
I have no modules or scripts or anything beyond the default configuration.  I
moved my config file out of the way and tried running it again and it segfaulted
immediately.

theme_init_module() seems to be the place where it's failing
(src/fe-common/core/themes.c) on a hash table lookup, which is implemented using
glib.  Irssi was working fine on rawhide for me up until a day or so ago and I
think there is a new glib.

Comment 3 Nalin Dahyabhai 2006-01-06 20:53:07 UTC
The crash David describes occurs dependably with glib 2.9.*, but it works again
if you downgrade to 2.8.4-1.  Rebuilding without garbage collection enabled
seems to keep it from crashing at that point (there's a crash at exit, but I
haven't chased that down yet).

Comment 4 Nalin Dahyabhai 2006-01-06 21:06:53 UTC
The crash at exit is already reported as #355 in the upstream bug tracker
(http://bugs.irssi.org/index.php?do=details&id=355).

Comment 5 David Cantrell 2006-01-23 21:51:21 UTC
The 27-Dec-2005 build of irssi in extras-development is still broken.  Can we
get that package built without garbage collection enabled as Nalin indicated and
with the patch included on this page:

(<a
href="http://bugs.irssi.org/index.php?do=details&id=355&area=attachments#tabs">http://bugs.irssi.org/index.php?do=details&id=355&area=attachments#tabs</a>).

Comment 6 David Cantrell 2006-01-23 21:52:22 UTC
I guess I don't need to use HTML markup in followups.  I learn something new
about Bugzilla each day.

Comment 7 Jasper O. Hartline 2006-01-26 19:37:47 UTC
An installed irssi from today Jan 26th, 2006 also Segfaults.
I'll attach an strace output if it will help at all.

-------------------------------------------------------------------------------
[root@SMP-NODE-0 ~]# irssi
Segmentation fault (core dumped)
[root@SMP-NODE-0 ~]# rpm -q irssi
irssi-0.8.10-1.fc5
[root@SMP-NODE-0 ~]#
-------------------------------------------------------------------------------

Comment 8 Jasper O. Hartline 2006-01-26 19:40:39 UTC
Created attachment 123733 [details]
strace irssi > strace.log 2>&1

Comment 9 Till Maas 2006-08-26 20:53:17 UTC
the patch seems to be included and irsii does not segfault on fc-5

Can this bug be closed?

Comment 10 David Cantrell 2006-08-28 14:22:37 UTC
I don't see why not.  I stopped using irssi since it was never fixed for the
longest time.  If you say it works, let's close this bug because I've stopped
caring about it.


Note You need to log in before you can comment on or make changes to this bug.