maemo.org Bugzilla – Bug 5142
SDK: Hildon-desktop crashes when displaying a button on a transparent background
Last modified: 2010-09-27 11:54:17 UTC
You need to
before you can comment on or make changes to this bug.
FREMANTLE_X86 using the Maemo 5 Beta 2 SDK
STEPS TO REPRODUCE THE PROBLEM:
Compile and run the "example-label-home-applet" (from
libhildondesktop-2.1.28+0m5) application with the following change:
line 117 was -> label = gtk_label_new ("An example applet");
line 117 becomes -> label = gtk_button_new_with_label ("An example applet");
When added to the desktop, the application shows a GtkButton on a transparent
hildon-desktop displays the text label of the button (but no decoration to
indicate it is a button) then crashes
Always. Sometimes it crashes on load, usually on mouse over or button press
EXTRA SOFTWARE INSTALLED:
Changing the GtkLabel to a GtkImage loaded from stock works fine. I haven't
tested to see if other widget types crash the same way. Here is the console
text at the time of the crash:
hildon-home: GLIB ERROR ** Gdk - The program 'hildon-home' received an X
Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
(Details: serial 462 error_code 8 request_code 70 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
maemo-launcher: child (pid=3219) terminated due to signal=6
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US)
AppleWebKit/532.0 (KHTML, like Gecko) Chrome/22.214.171.124 Safari/532.0
The console text isn't helpful. :-(
Any chance of running this in gdb to get a nice stacktrace?
Andre, if I understand it correctly I would have to run the entire
hildon-desktop process in gdb, since individual desktop widgets share that
process. Is there somewhere that describes this procedure?
Hi Andrew, as far as I know:
Install maemo-debug-scripts and valgrind for SDK tools repo, start application
framework normally under Xephyr, kill hildon desktop process, then re-start it
with run-with-valgrind/memcheck script (which comes from maemo-debug-scripts).
Some more info (though these refer to Diablo):
moreinfo as per last comment
Hi Andrew, is this still an issue in the current SDK?
If not, it's probably good to close this as RESOLVED WORKSFORME.
After an apt-get dist-upgrade in the SDK to update to the latest packages, this
bugs is still present. Same error message as before, and a button in a desktop
widget crashes the entire dekstop.
Is this still reproducible with PR1.2 SDK (coming Wednesday March 24th, 12:00
Andrew, is this still reproducible with PR1.2 SDK?
Closing this bug report as the issue could not be reproduced. Please feel free
to reopen this report if you can still reproduce this.