Hide Forgot
abrt version: 2.0.1 architecture: i686 cmdline: component: guake executable: /usr/lib/guake/guake.py kernel: 2.6.38.8-32.fc15.i686.PAE os_release: Fedora release 15 (Lovelock) package: guake-0.4.2-3.fc15 reason: guake.py:27:<module>:ImportError: /lib/libncurses.so.5: undefined symbol: _nc_screen_of time: Thu Jun 30 12:00:31 2011 uid: 500 username: iwar backtrace: :guake.py:27:<module>:ImportError: /lib/libncurses.so.5: undefined symbol: _nc_screen_of : :Traceback (most recent call last): : File "/usr/lib/guake/guake.py", line 27, in <module> : import vte :ImportError: /lib/libncurses.so.5: undefined symbol: _nc_screen_of : :Local variables in innermost frame: :__builtins__: <module '__builtin__' (built-in)> :__file__: '/usr/lib/guake/guake.py' :gtk: <module 'gtk' from '/usr/lib/python2.7/site-packages/gtk-2.0/gtk/__init__.pyo'> :pygtk: <module 'pygtk' from '/usr/lib/python2.7/site-packages/pygtk.pyo'> :__package__: None :GPollableInputStream: <class 'gio.__main__.GPollableInputStream'> :gobject: <module 'gobject' from '/usr/lib/python2.7/site-packages/gobject/__init__.pyo'> :GInitiallyUnowned: <class 'gtk.__main__.GInitiallyUnowned'> :__name__: '__main__' :GPollableOutputStream: <class 'gio.__main__.GPollableOutputStream'> :__doc__: None comment: :Ejecute la aplicacin y marco este error : run guake and show error
Could you provide some information on how to reproduce this bug ?
Possibly related, I had a patch from Miroslav Lichvar which I added in 20100123 (no bugzilla number) which addressed this symbol in conjunction with the normal/wide libtinfo's.
I am a little bit confused about your comment Thomas. Could you give a bit more info/context ?
I added _nc_screen_of in 20080531 (between 5.6 and 5.7) as part of some changes to allow improved reentrancy. That happens to be associated with the lower-level terminfo functions. At some point (I don't recall) Red Hat started packaging ncurses using the --with-termlib option, which provides the low-level terminfo functions as a separate library (typically referred to as libtinfo). An application can have problems loading libtinfo automatically as part of loading libncurses / libncursesw for several reasons. One (the fix mentioned in Comment #2) was that the binary compatibility between the copies of libtinfo built as part of building libncurses differed from the libncursesw. However, Red Hat was delivering one copy of libtinfo to satisfy dependencies from both libraries. My comment was suggesting that perhaps some similar issue had crept in, and that it might require getting more information. (My own builds use libtinfo in some platforms, but usually use rpath so that I can install/use these separately from whatever the different distributors provide as system libraries - so I'm testing it in a different configuration, and can overlook things).
So the problem is from ncurses. I am reassigning the bug to the ncurses component. Thanks for the information.
This is odd. The symbol is in libtinfo.so.5. If it wasn't all ncurses applications would probably fail. The "import vte" command also works here.
I'm puzzled, too. I don't see any likely conflicting library paths in the log (such as /usr/local/lib). I guess starting by asking the reporter if it can still be reproduced is where to start.
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping