Bug 904184 - Vim with X support (vimx command) currently crashes
Summary: Vim with X support (vimx command) currently crashes
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: vim
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Karsten Hopp
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-25 17:17 UTC by John Anderson
Modified: 2013-05-14 14:57 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-05-14 14:57:19 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
strace of running vimx (58.50 KB, text/plain)
2013-01-25 17:17 UTC, John Anderson
no flags Details

Description John Anderson 2013-01-25 17:17:08 UTC
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

Comment 1 Mark Harfouche 2013-02-15 18:56:05 UTC
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

Comment 2 John Anderson 2013-02-15 19:03:30 UTC
On a fully updated system the problem has seemed to fix itself.

Comment 3 Mark Harfouche 2013-02-15 19:06:44 UTC
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.

Comment 4 Karsten Hopp 2013-02-15 19:51:44 UTC
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 ?

Comment 5 Mark Harfouche 2013-02-15 23:10:51 UTC
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".

Comment 6 Karsten Hopp 2013-05-14 14:57:19 UTC
closing per comment #5


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