FS#43721 - [gmrun] gmrun hangs when history contains long string

Attached to Project: Community Packages
Opened by Juan Luis Cano (Juanlu001) - Friday, 06 February 2015, 16:05 GMT
Last edited by Balló György (City-busz) - Monday, 29 January 2018, 12:50 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Florian Pritz (bluewind)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

gmrun 0.9.2 hangs when history contains long string.

Additional info:

This corresponds to upstream bug #518529 which was fixed in 2009, but apparently the SourceForge source is been frozen since 2003, and therefore still contains the buggy code.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=518529

There is evidence this bug still affects Arch:

https://bbs.archlinux.org/viewtopic.php?id=82629

Steps to reproduce:
1. Execute long command via gmrun. For example,
echo 1234567890123456789012345123456789012345678901234512345678901234567890123451234567890123456789012345123456789012345678901234512345678901234567890123451234567890123456789012345123456789012345678901234512345678901234567890123451234567890123456789012345a
2. Run gmrun again. It hangs with 100% CPU usage.
This task depends upon

Closed by  Balló György (City-busz)
Monday, 29 January 2018, 12:50 GMT
Reason for closing:  Fixed
Additional comments about closing:  gmrun 0.9.2-7
Comment by Florian Pritz (bluewind) - Friday, 06 February 2015, 18:30 GMT
Debian applies 10 patches and there is a fork on github[1] that also has some, but the history patch is not included. If you really care about gmrun I'd ask you to fork gmrun and gather all the patches and maintain that repository.

[1] https://github.com/rtyler/gmrun

If I were to apply all those patches in the Arch Linux package I'd have to keep track of where else patches pop up, verify them and fix resulting issues and every other distro maintainer has to do exactly the same. That's a lot of wasted manpower and it would really benefit everyone if there is a central repository with releases. In other words a maintained fork would be the best solution.

You mentioned "upstream bug #518529" which is wrong since this is a debian bug and debian is not upstream for this software. The project on sourceforge is upstream, but sadly it's dead. This is another reason why I dislike distros patching software, but doing so is debian's decision.

I'm not interested in doing that work (forking gmrun) and it's our policy to patch as little as possible for the reasons outlined above so this bug won't be patched by me, sorry. I will fix it by switching to a maintained fork if one is created however.

I'll keep this open for someone to find and work on, but it won't be fixed until there is a maintained fork.
Comment by Balló György (City-busz) - Monday, 29 January 2018, 12:50 GMT
Still no upstream activity in the recent years, so I applied the fix.

Loading...