Ticket #597 (closed defect: fixed)
openmoko-dialer segfaults on cancelling an outgoing call
| Reported by: | balrogg@… | Owned by: | tonyguan@… |
|---|---|---|---|
| Priority: | high | Milestone: | |
| Component: | openmoko-dialer | Version: | current svn head |
| Severity: | normal | Keywords: | |
| Cc: | buglog@… | Blocked By: | |
| Blocking: | Estimated Completion (week): | ||
| HasPatchForReview: | PatchReviewResult: | ||
| Reproducible: |
Description
In openmoko-devel-image-fic-gta01-20070606205115.rootfs.jffs2, after choosing a
number to dial and tapping on dial, consequent tapping the Cancel button causes
a segfault in:
Program received signal SIGSEGV, Segmentation fault.
0x40bae8d0 in g_atomic_int_get () from /usr/lib/libglib-2.0.so.0
(gdb) bt
#0 0x40bae8d0 in g_atomic_int_get () from /usr/lib/libglib-2.0.so.0
#1 0x40b2ad1c in g_object_unref () from /usr/lib/libgobject-2.0.so.0
#2 0x40e2f82c in ?? () from /usr/lib/gtk-2.0/2.4.0/engines/libpixmap.so
Cannot access memory at address 0x360
Attachments
Change History
comment:1 Changed 6 years ago by balrogg@…
- Summary changed from openmoko-dialer segfaults on cacelling an outgoing call to openmoko-dialer segfaults on cancelling an outgoing call
comment:2 Changed 6 years ago by njp@…
We have been experiencing this issue with any application that was using the
standard GtkButton?. It seems that the border property in the gtkbutton rc file
was using too large values for the gtkbutton_p.png pixmap, and thus the pixbuf
engine was segfaulting.
I have just committed a fix to the openmoko-standard theme, which works for me,
in that the dialer (or any other applications using GtkButton?), will not crash
anymore.
Could you please check that it works now for you, using the latest
openmoko-standard theme.
openmoko-dialer strace log