Bug 480697

Summary: irssi crashed when moved splitted window down (up)
Product: [Fedora] Fedora Reporter: Michal Nowak <mnowak>
Component: irssiAssignee: Marek Mahut <mmahut>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: 10CC: lkundrak, mfabry, mmahut, ohudlick
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: 2009-11-18 13:42:09 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
BT from irssi none

Description Michal Nowak 2009-01-19 22:27:21 UTC
Created attachment 329401 [details]
BT from irssi

Description of problem:

Open `irssi' join some fancy channels

/Q newman
/window show 3
/window move down

Moving the "selected" splitted sub-window down/up (where applicable) causes crash. 

Attaching raw BT, some -debuginfos are missing but seems to me easy to reproduce anyway.

Version-Release number of selected component (if applicable):

irssi-0.8.12-11.fc10.i386
irssi-debuginfo-0.8.12-11.fc10.i386

How reproducible:
always

Comment 1 Marek Mahut 2009-01-20 07:11:57 UTC
Thanks - I'll check it with upsteam later today.

Comment 2 Michal Fabry 2009-03-31 10:08:49 UTC
I wasn't able to reproduce this under x86_64.

irssi-0.8.12-11.fc10.x86_64

Comment 3 Michal Nowak 2009-03-31 10:35:58 UTC
What it does with irssi-0.8.12-13.fc11.x86_64 is that it "hides" the bottom split-window but not crashing. 

What does upstream said on this?

Comment 4 Marek Mahut 2009-03-31 10:57:36 UTC
Nothing yet - but release candidate 1 for 0.8.13 is out, let me try to build it.

Comment 5 Marek Mahut 2009-03-31 13:05:08 UTC
http://koji.fedoraproject.org/koji/taskinfo?taskID=1267720

0.8.13-rc1 scratch build - can you test it?

Comment 6 Michal Fabry 2009-03-31 13:09:40 UTC
Same results under x86_64 for me (irssi hides bottom split-window).

Comment 7 Michal Nowak 2009-04-01 18:52:43 UTC
F10, i386, new pkgs: the sub-window is closed as was reported on F11-x86, comment #3.

Can anyone confirm this is OK behavior? (Not much expected for me...)

Comment 8 Michal Nowak 2009-06-24 15:31:46 UTC
irssi-0.8.12-13.fc11.i586

Core was generated by `irssi'.
Program terminated with signal 11, Segmentation fault.
#0  0x0806777b in ?? ()

Thread 1 (Thread 15655):
#0  0x0806777b in ?? ()
No symbol table info available.
#1  0x080e175e in ?? ()
No symbol table info available.
#2  0x080e1ca0 in signal_emit_id ()
No symbol table info available.
#3  0x0809a17b in ?? ()
No symbol table info available.
#4  0x080e175e in ?? ()
No symbol table info available.
#5  0x080e1ca0 in signal_emit_id ()
No symbol table info available.
#6  0x0809a43b in ?? ()
No symbol table info available.
#7  0x0809a5e3 in printformat_module_dest_args ()
No symbol table info available.
#8  0x0809a73c in printformat_module_args ()
No symbol table info available.
#9  0x0809a784 in printformat_module ()
No symbol table info available.
#10 0x080f3df3 in ?? ()
No symbol table info available.
#11 0x080e175e in ?? ()
No symbol table info available.
#12 0x080e1d4c in signal_emit ()
No symbol table info available.
#13 0x003db8af in ?? ()
   from /usr/lib/perl5/vendor_perl/5.10.0/i386-linux-thread-multi/auto/Irssi/TextUI/TextUI.so
No symbol table info available.
#14 0x08064ae3 in statusbar_redraw ()
No symbol table info available.
#15 0x0806579c in statusbar_item_redraw ()
No symbol table info available.
#16 0x08065962 in ?? ()
No symbol table info available.
#17 0x080e175e in ?? ()
No symbol table info available.
#18 0x080e1d4c in signal_emit ()
No symbol table info available.
#19 0x080a407f in window_set_active ()
No symbol table info available.
#20 0x08062a34 in mainwindow_change_active ()
No symbol table info available.
#21 0x08062aec in ?? ()
No symbol table info available.
#22 0x080e175e in ?? ()
No symbol table info available.
#23 0x080e1d4c in signal_emit ()
No symbol table info available.
#24 0x080ccb3b in command_runsub ()
No symbol table info available.
#25 0x0809ff20 in ?? ()
No symbol table info available.
#26 0x080e175e in ?? ()
No symbol table info available.
#27 0x080e1d4c in signal_emit ()
No symbol table info available.
#28 0x080ccb3b in command_runsub ()
No symbol table info available.
#29 0x080a0e4a in ?? ()
No symbol table info available.
#30 0x080e175e in ?? ()
No symbol table info available.
#31 0x080e1d4c in signal_emit ()
No symbol table info available.
#32 0x080cb848 in ?? ()
No symbol table info available.
#33 0x080e175e in ?? ()
No symbol table info available.
#34 0x080e1d4c in signal_emit ()
No symbol table info available.
#35 0x0805d16b in ?? ()
No symbol table info available.
#36 0x080e175e in ?? ()
No symbol table info available.
#37 0x080e1d4c in signal_emit ()
No symbol table info available.
#38 0x0809891d in ?? ()
No symbol table info available.
#39 0x080e175e in ?? ()
No symbol table info available.
#40 0x080e1d4c in signal_emit ()
No symbol table info available.
#41 0x080987e3 in key_pressed ()
No symbol table info available.
#42 0x0805f9a4 in ?? ()
No symbol table info available.
#43 0x080e175e in ?? ()
No symbol table info available.
#44 0x080e1d4c in signal_emit ()
No symbol table info available.
#45 0x0805ed8e in ?? ()
No symbol table info available.
#46 0x080d30ae in ?? ()
No symbol table info available.
#47 0x0083172b in g_io_unix_dispatch (source=0x90c1380, callback=0x80d3070, 
    user_data=0x90c25e8) at giounix.c:162
        buffer_condition = <value optimized out>
#48 0x007fad78 in g_main_dispatch (context=<value optimized out>)
    at gmain.c:1814
        dispatch = 0x8316e0 <g_io_unix_dispatch>
        user_data = 0x90c25e8
        callback = 0x80d3070
        cb_funcs = 0x8a34bc
        cb_data = 0x90b5a78
        current_source_link = {data = 0x90c1380, next = 0x0}
        source = 0x90c1380
        current = 0x924da10
        i = 0
#49 IA__g_main_context_dispatch (context=<value optimized out>) at gmain.c:2367
No locals.
#50 0x007fe310 in g_main_context_iterate (context=0x908c6d0, 
    block=<value optimized out>, dispatch=1, self=0x90f5658) at gmain.c:2445
        max_priority = 2147483647
        timeout = 454
        some_ready = 1
        nfds = <value optimized out>
        allocated_nfds = <value optimized out>
        fds = <value optimized out>
        __PRETTY_FUNCTION__ = "g_main_context_iterate"
#51 0x007fe443 in IA__g_main_context_iteration (context=0x908c6d0, may_block=1)
    at gmain.c:2508
        retval = <value optimized out>
#52 0x080707a4 in main ()
No symbol table info available.


Still segfaulting.

What's the info from upstream?

Comment 9 Marek Mahut 2009-06-25 08:09:01 UTC
Please try the latest from the testing repository. I did not check with upstream yet - I can't reproduce it.

http://koji.fedoraproject.org/koji/buildinfo?buildID=111560

Comment 10 Michal Nowak 2009-06-30 11:33:49 UTC
irssi-0.8.13-3.fc11.i586 still crashing.

Upstream bug: http://bugs.irssi.org/index.php?do=details&task_id=661

Comment 11 Marek Mahut 2009-08-04 15:51:56 UTC
https://admin.fedoraproject.org/updates/F11/FEDORA-2009-8243

Can you try the new version?

Comment 12 Bug Zapper 2009-11-18 09:09:10 UTC
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '10'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 10 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping