Summary: | Bluefish segfaults after gentoo upgrade | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Lindsay Haisley <fmouse-gentoo> |
Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED INVALID | ||
Severity: | critical | CC: | solomarv |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Lindsay Haisley
2005-07-02 08:11:03 UTC
Thanks for taking the time to report this bug. Without a stack trace from the crash it's very hard to determine what caused it. Can you provide us with one? Please see http://live.gnome.org/GettingTraces for more information on how to do so. OK, thanks. gdb showed me that in fact the problem was with a relatively ancient version of Bluefish in /usr/local/bin, and when I accessed /usr/bin/bluefish everything works OK. Sorry for the noise! It looks as if perhaps a recent gentoo system upgrade changed the default $PATH order, putting /usr/local/bin ahead of /usr/bin, or else, more likely, I've been using bluefish in /usr/local/bin for some time and it finally hit the wall on library issues, and my re-emerges, of course, didn't affect this version. Again, sorry for the false report here, but I'm happy to have the problem solved. I"ve marked the bug INVALID. |