Bug 1186676 - Crash when staging a chunk
Summary: Crash when staging a chunk
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: tig
Version: 21
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: jbowes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1186679 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-01-28 09:58 UTC by Tomas Popela
Modified: 2015-03-23 07:16 UTC (History)
3 users (show)

Fixed In Version: tig-2.1-1.fc20
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-21 05:01:45 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Tomas Popela 2015-01-28 09:58:12 UTC
Description of problem:
Tig crashes when trying to stage a chunk.

Version-Release number of selected component (if applicable):
$ rpm -qa tig
tig-2.0.3-1.fc21.x86_64

How reproducible:
Everytime

Steps to Reproduce:
1. open tig
2. go to Unstaged changes
3. press d
4. navigate to some chunk
5. press u

Actual results:
tig crashes

Additional info:

Core was generated by `tig'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  view_no_refresh (view=view@entry=0x0, flags=flags@entry=OPEN_REFRESH) at src/view.c:559
559                    ((flags & OPEN_REFRESH) && !view_can_refresh(view));
(gdb) bt full
#0  view_no_refresh (view=view@entry=0x0, flags=flags@entry=OPEN_REFRESH) at src/view.c:559
No locals.
#1  0x00000000004155b8 in load_view (view=0x0, prev=prev@entry=0x0, flags=flags@entry=OPEN_REFRESH) at src/view.c:770
        refresh = <optimized out>
#2  0x000000000041f30d in stage_request (view=0x63bb40 <stage_view>, request=<optimized out>, line=<optimized out>) at src/stage.c:442
No locals.
#3  0x000000000040340c in view_driver (request=REQ_STATUS_UPDATE, view=0x63bb40 <stage_view>) at src/tig.c:206
        i = <optimized out>
#4  main (argc=<optimized out>, argv=<optimized out>) at src/tig.c:697
        codeset = <optimized out>
        pager_mode = false
        request = <optimized out>
        view = <optimized out>

Comment 1 Jason Tibbitts 2015-01-28 16:29:21 UTC
*** Bug 1186679 has been marked as a duplicate of this bug. ***

Comment 2 Jason Tibbitts 2015-02-19 18:56:43 UTC
Reported upstream as https://github.com/jonas/tig/issues/376

If I build a package from current git head, would you be willing to test it just to make sure it hasn't been fixed in the meantime?

Comment 3 Tomas Popela 2015-02-20 06:12:04 UTC
I can confirm that it is fixed with the commit you mentioned. Thanks.

Comment 4 Fedora Update System 2015-03-13 21:48:05 UTC
tig-2.1-1.fc22 has been submitted as an update for Fedora 22.
https://admin.fedoraproject.org/updates/tig-2.1-1.fc22

Comment 5 Fedora Update System 2015-03-13 22:21:16 UTC
tig-2.1-1.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/tig-2.1-1.fc21

Comment 6 Fedora Update System 2015-03-13 22:21:49 UTC
tig-2.1-1.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/tig-2.1-1.fc20

Comment 7 Fedora Update System 2015-03-15 10:53:38 UTC
Package tig-2.1-1.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing tig-2.1-1.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2015-3904/tig-2.1-1.fc20
then log in and leave karma (feedback).

Comment 8 Fedora Update System 2015-03-21 05:01:45 UTC
tig-2.1-1.fc22 has been pushed to the Fedora 22 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 9 Fedora Update System 2015-03-23 07:13:01 UTC
tig-2.1-1.fc21 has been pushed to the Fedora 21 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 10 Fedora Update System 2015-03-23 07:16:56 UTC
tig-2.1-1.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.


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