|
Bugzilla – Full Text Bug Listing |
| Summary: | Crash in Banshee from supplementary | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | James Ogley <riggwelter> |
| Component: | GNOME | Assignee: | Aaron Bockover <abockover> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | i686 | ||
| OS: | SuSE Linux 10.0 | ||
| Whiteboard: | |||
| Found By: | Beta-Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
James Ogley
2005-11-10 10:10:47 UTC
Can it be theme engine problem? I have seen similar message with gtk-qt-engine. What gtk is this? This looks similar to a bug that affected gtk 2.8.3 and below I believe. gtk2-2.8.6-7 So thats not the problem. Is the theme the problem? CC'ing banshee developer for comment. cmeadors had some issues yesterday that magically went away after he installed more -devel packages. I think we might be missing a mapping somewhere. obvious ones to try are the -devel packages for cairo, pango, gtk2 From the nature of the exception, it seems like a problem in gtk-sharp-2.0, which most probably means as mentioned above, a missing map. There is no code in Banshee that directly uses Cairo. Is this still an issue on new Banshee/gtk-sharp-2.0? I could never reproduce this. Doesn't seem to be an issue, although I'm now using my own Banshee packages. We've moved on to 0.10.4 and have no similar crash reports and we use almost exactly upstream, so I'm going to close this as fixed. |