Bug 904184
| Summary: | Vim with X support (vimx command) currently crashes | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | John Anderson <sontek> | ||||
| Component: | vim | Assignee: | Karsten Hopp <karsten> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 18 | CC: | karsten, mark.harfouche | ||||
| 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: | 2013-05-14 14:57:19 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: | |||||||
| Attachments: |
|
||||||
I noticed the same thing happens to me after I wake up from sleep. Would be great if someone could look at this. Other people mentioned taht it was linked the to the QT engine. https://code.google.com/p/gtk-qt-engine/issues/detail?id=51 http://lists.bostoncoop.net/pipermail/linux-disciples/2006-January/001771.html https://bbs.archlinux.org/viewtopic.php?id=81948 On a fully updated system the problem has seemed to fix itself. I just checked, my latest update included an update for QT. maybe the problem is that when QT gets update it leaves the system in an weird state. vimx or any part of vim doesn't use QT. It's more likely that one of the X libraries or gnome/gtk/gdk caused this. Mark, can you confirm that the issue is solved with a fully updated system ? I agree that the issue is (most likely) not related to vim but with the gnome/gtk/gdk libraries. Karsten, I don't want to say that the issue is fixed because I don't know a reliable way to reproduce the original issue. It would occasionally happen (maybe after an update) and my fix would be to reboot my laptop (which I might do every 2-4 days). Now that I have rebooted my laptop it is unclear to me what actually might have fixed the issue. I tried putting my laptop to sleep and waking it a couple times and I am still able to open vimx. So sure, this issue is "fixed". closing per comment #5 |
Created attachment 687591 [details] strace of running vimx Install vim, run vimx: $ vimx ICE default IO error handler doing an exit(), pid = 5953, errno = 0