| Summary: | app-crypt/seahorse-0.7.9 build fails with gnome 2.12 (gedit problem) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Surakshan Mendis <bug.tracker> |
| Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | reto.gantenbein |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | seahorse 0.7.9 config log | ||
|
Description
Surakshan Mendis
2005-09-15 20:51:21 UTC
Created attachment 68554 [details]
seahorse 0.7.9 config log
seahorse 0.7.9 config log
Even more info.
In capplets/background/gnome-wp-item.c at line 221 there is an:
if (pixbuf != NULL) {
...
}
Right after that block there is a:
pw = gdk_pixbuf_get_width (pixbuf);
ph = gdk_pixbuf_get_height (pixbuf);
Those generates the warnings, since pixbuf obviously is NULL. Looks like they
handle that. But the "g_object_unref (pixbuf)" does not it makes the capplet
segfault.
Now, I wonder: why is pixbuf NULL at all? Should there be a
if (pixbuf == NULL) return;
statement somewhere before?
I have no experience of gtk/gnome programming, but it looks like there is a
missing check if the pixbuf is created sucessully or not somwhere.
I also suspect that this only happens to a certain types of files and not all.
(In reply to comment #2) > Even more info. Oups... This was in the wrong bug... My comment is not related to this at all. I'm sorry. Seahorse seems to require gedit 2.10, while gnome 2.12 has gedit 2.12. Upstream will need to update it to make it work with 2.12. I've patched it and added to CVS. *** Bug 108195 has been marked as a duplicate of this bug. *** |