Bug 4570 - Xephyr segmentation fault when clicking text field in Maemo 5 Beta SDK
: Xephyr segmentation fault when clicking text field in Maemo 5 Beta SDK
Status: RESOLVED FIXED
Product: Development platform
SDK
: 5.0-beta
: x86 Ubuntu
: Medium critical (vote)
: ---
Assigned To: Soumya
: sdk-bugs
: http://maemo.org/development/sdks/mae...
: upstream
:
:
  Show dependency tree
 
Reported: 2009-05-21 13:14 UTC by Esa Törmikoski
Modified: 2009-05-30 15:01 UTC (History)
3 users (show)

See Also:


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description Esa Törmikoski (reporter) 2009-05-21 13:14:07 UTC
SOFTWARE VERSION:
- Maemo 5 Beta SDK
- Kubuntu 9.04
- xserver-xephyr 2:1.6.0-0ubuntu14

STEPS TO REPRODUCE THE PROBLEM:
1) Compile and run example_findtoolbar from
https://garage.maemo.org/svn/maemoexamples/branches/fremantle-sdk-testing/maemo-examples/
2) Click search button
3) Click text field

EXPECTED OUTCOME:
Should be able to write text to the field

ACTUAL OUTCOME:
Xephyr crashes, output:
% Xephyr :2 -host-cursor -screen 800x480x16 -dpi 96 -ac
[dix] Could not init font path element /usr/share/fonts/X11/cyrillic, removing
from list!
[config/dbus] couldn't take over org.x.config:
org.freedesktop.DBus.Error.AccessDenied (Connection ":1.156257" is not allowed
to own the service "org.x.config.display2" due to security policies in the
configuration file)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
[and 6 times more]
[Startup output ends, running ./example_findtoolbar]
Backtrace (10 deep):
0: Xephyr(KdBacktrace+0x35) [0x80c1595]
1: /lib/tls/i686/cmov/libc.so.6 [0xb79a7778]
2: Xephyr(DeliverDeviceEvents+0x20f) [0x808fabf]
3: Xephyr(ProcessOtherEvent+0x36c) [0x81910cc]
4: Xephyr(mieqProcessInputEvents+0x372) [0x80f0da2]
5: Xephyr(ProcessInputEvents+0xd) [0x80c620d]
6: Xephyr(Dispatch+0x6e) [0x80b329e]
7: Xephyr(main+0x3bd) [0x809869d]
8: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7992775]
9: Xephyr [0x8070741]

Fatal server error:
Segmentation fault caught

zsh: segmentation fault  Xephyr :2 -host-cursor -screen 800x480x16 -dpi 96 -ac


Output in scratchbox:
[sbox-FREMANTLE_X86:
~/maemoexamples/branches/fremantle-sdk-testing/maemo-examples] >
run-standalone.sh ./example_findtoolbar
AF Warning: '/etc/osso-af-init/matchbox.defs' not found
hildon-desktop[32444]: GLIB WARNING ** ClutterGLX - Pixmap with depth bellow 24
are not supported
[Xephyr crash]
sapwood-server: Fatal IO error 11 (Resource temporarily unavailable) on X
server :2.0.
hildon-home: Fatal IO error 11 (Resource temporarily unavailable) on X server
:2.0.
example_findtoolbar: Fatal IO error 11 (Resource temporarily unavailable) on X
server :2.0.
/usr/bin/hildon-desktop: Fatal IO error 11 (Resource temporarily unavailable)
on X server :2.0.
hildon-input-method: Fatal IO error 11 (Resource temporarily unavailable) on X
server :2.0.
maemo-launcher: child (pid=32461) terminated due to exit()=1
maemo-launcher: child (pid=32446) terminated due to exit()=1


REPRODUCIBILITY:
Always

EXTRA SOFTWARE INSTALLED:

OTHER COMMENTS:
- Bug is already listed in Known issues:
http://maemo.org/development/sdks/maemo_5-0_installation/#sdkissue
- SDK is installed like described in installation guide

No crash:
 - Xubuntu 8.04 running in Virtualbox + Maemo 5 Beta SDK+ xserver-xephyr
2:1.4.1~git20080131-1ubuntu9.2
 - Ubuntu 8.04 LTS + Maemo 5 Beta SDK, no info about xserver-xephyr

User-Agent:       Opera/9.64 (X11; Linux i686; U; en) Presto/2.1.1
Comment 1 Soumya nokia 2009-05-22 13:36:19 UTC
This is because of a bug in xorg-xserver in 9.04 Jaunty. One of our testers has
raised a bug about this and a patch is already available. Please have a look
into this bug:
http://bugs.freedesktop.org/show_bug.cgi?id=21591
Comment 2 Andre Klapper maemo.org 2009-05-25 10:59:18 UTC
(In reply to comment #0)
> OTHER COMMENTS:
> - Bug is already listed in Known issues:

...which is a good reason to not file another ticket if it's already a known
issue. ;-)