Hi,
I encounter a strange issue. Currently, my qtMoko refuse to start: it
freezes with a SegmentationFault message on the framebuffer.
After some investigation, it seems that the faulty is qpe. But I do
not understand why.
Looking at many many logs, it seems to be related to bluetooth
unavailable when qpe initializing (last messages are around bluez DBus
interfaces unavailable). So, I enabled bluetooth ('om bt power 1') and
then restarted qtMoko ('/etc/init.d/qtmoko restart'), even after some
bluetooth fixes ('/opt/qtmoko/bin/btfix.sh'). But nothing better,
Segmentation Fault always occurs. Nevertheless, something strange
occurs: bluetooth device is powered off, while it was on just before.
So, a new idea: the last-action-before-hanging-system is to disable
bluetooth at startup, because I do not need bluetooth myself. So, I
imagine the following: when initializing, qpe apply my settings and
disable bluetooth, but just after it enters a code that reclaim
bluetooth.
How can I solve this? Is there a way to change the startup settings
without GUI? Is there a way to start enought part of GUI to change
settings?
Also, I'm probably wrong: is there any other way to solve the issue?
Thanks for reading and for any suggestion.
--
Guilhem BONNEFILLE
-=- JID: gu...@im.apinc.org MSN: guilhem_bonnefi...@hotmail.com
-=- mailto:guilhem.bonnefi...@gmail.com
-=- http://nathguil.free.fr/
_______________________________________________
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
