| Summary: | libgsf 1.8.2 breaks nautilus | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | André Lemos <tux> |
| Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | CC: | tux |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
André Lemos
2003-09-19 06:30:24 UTC
rule 1 of gentoo bugreporting, lower your CFLAGS afaik nautilus shouldn't even link to libgsf, it is only used by gnumeric. I did lowered my flags to rebuild nautilus down to "-O2 -march=pentium3 -pipe" .... AFAIK, gdb told me that nautilus does use libgsf, as you can see. And if I don't even use gnumeric, what is it doing on my system? ;) and what flags did you build libgsf with? 'only used' was 'only used that i know of', but it still isn't used by nautilus. There are other things that may pull it in. But i found your probably dep, you use librsvg which can use it and librsvg is used by nautilus if you use svg icons. Try switching to a non-svg theme. If you do backtraces, why don't you include them ? Still i don't see this problem and your pretty high mad-o-meter level of CFLAGS makes me suspect that in some way it is related. lowering CFLAGS on 1 build only may not be enough To be honest, I haven't striped down the flags for libgsf for neither version. So maybe 1.8.2 has issues with this flags. I'll give it a go, and then I'll let you know what the outcome was. I've rebuild libgsf with "-O2 -march=pentium3 -pipe" and did a kill -HUP on nautilus, everything looks fine. So I guess this particular version doesn't handle quite well this flags (I know they aren't very ortodox). This is the open_path() bug I've been chasing down the last 24 hours. It has been extensively documented in bug #29208. If you're interested, please have a look: http://bugs.gentoo.org/show_bug.cgi?id=29208 A rebuild of the defect library will fix those segfault issues in open_path(), as the reporter correctly stated previously. closing, non-reproducable as far as the comment in #7 goes, it looks like the same problem only there is no answer to why this happens. Just fixing symptoms is not really solving the bug. |