Bug 1263863

Summary: Plugin Join Lines hangs gedit when joining with empty last line in buffer
Product: [Fedora] Fedora Reporter: Štefan Gurský <scorpy_sk>
Component: gedit-pluginsAssignee: Ignacio Casal Quinteiro (nacho) <icq>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: icq
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 17:54:57 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Štefan Gurský 2015-09-16 22:11:29 UTC
Description of problem:
When using Join Lines plugin using its keyboard shortcut (Ctrl+J) on the second last line of file with the last line being empty, gedit hangs.


Version-Release number of selected component (if applicable):
Name        : gedit-plugins
Version     : 3.16.0
Release     : 1.fc22
Architecture: x86_64


Steps to Reproduce:
1. Start gedit with line joining plugin enabled
2. In the empty buffer write some text on the first line (for example “foo”)
3. Press enter so that new line is inserted
4. press up arrow to go to the first line
5. Press Ctrl+J to invoke line joining.
6. Observe that gedit stops responding.

Actual results:
gedit stops responding

Expected results:
lines are joined (empty last line in the file is removed)

Additional info:
I disabled other plugins when testing this.

Comment 1 Fedora End Of Life 2016-07-19 17:54:57 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.