community Digest, Vol 238, Issue 9

[giacomo 'giotti' mariani]

On 06/05/2011 11:41 PM, community-request at lists.openmoko.org wrote:
>> Guilhem Bonnefille wrote:
>> >
>>> >>  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.
>> >
>> >  Hi,
>> >  i am not quite sure if it's really bluetooth. I'd rather try remove and
>> >  install again qtmoko package with apt-get - maybe the executable got somehow
>> >  corrupted.
>> >
>> >  Another option is to ssh to the FR, install gdb and check the backtrace:
>> >
>> >  apt-get install gdb
>> >  /etc/init.d/qtmoko stop
>> >  source /opt/qtmoko/qpe.env
>> >  gdb qpe
> Here is the backtrace.
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x40a3c414 in QDBusAbstractInterface::isValid() const () from
> /opt/qtmoko/lib/libQtDBus.so.4
> (gdb) where
> #0  0x40a3c414 in QDBusAbstractInterface::isValid() const () from
> /opt/qtmoko/lib/libQtDBus.so.4
> #1  0x403e16b8 in bool QBluetoothDbusIface::btcall<void>(QString
> const&, QDBusReply<void>&, QList<QVariant>, bool, QObject*, char
> const*, char const*) () from /opt/qtmoko/lib/libqtopiacomm.so.4
> #2  0x403eb1e0 in ?? () from /opt/qtmoko/lib/libqtopiacomm.so.4
> #3  0x403eb1e0 in ?? () from /opt/qtmoko/lib/libqtopiacomm.so.4
> Backtrace stopped: previous frame identical to this frame (corrupt stack?)
>
>
> Any suggestion to restore functional qtMoko is welcome.
Hi Guilhem,
    I had a similar problem some time ago... it was probably related to 
UBIFS corruption. Is your QtMoko installed in NAND? If yes, conside 
following gena2x suggestion [1].

Anyway, here is what happened to me with QtMoko v33:
>
> root at neo:~# cat /etc/init.d/qpe.sh
> #!/bin/sh
> [...]
> . /opt/qtmoko/qpe.env
> [...]
> root at neo:~# . /opt/qtmoko/qpe.env
> root at neo:/root#
> root at neo:/root# qpe
> qpe: error while loading shared libraries: 
> /opt/qtmoko/lib/libopenobex.so.1: cannot read file data: Input/output 
> error
> root at neo:/root# head -1 /opt/qtmoko/lib/lib* > cose
> head: error reading `/opt/qtmoko/lib/libdissipate2.so.1': Input/output 
> error
> head: error reading `/opt/qtmoko/lib/libopenobex.so.1': Input/output error
> head: error reading `/opt/qtmoko/lib/libqtopiatheming.so.4': 
> Input/output error
> root at neo:/root# wc -l cose
> 107 cose
> root at neo:~# dpkg -S /opt/qtmoko/lib/libdissipate2.so.1
> qtmoko: /opt/qtmoko/lib/libdissipate2.so.1
> root at neo:~# dpkg -S /opt/qtmoko/lib/libopenobex.so.1
> qtmoko: /opt/qtmoko/lib/libopenobex.so.1
> root at neo:~# dpkg -S /opt/qtmoko/lib/libqtopiatheming.so.4
> qtmoko: /opt/qtmoko/lib/libqtopiatheming.so.4
> root at neo:~# apt-get remove qtmoko
> [...]
> root at neo:~# apt-get install qtmoko
> [...]
and everything turned OK.

Regards
      Giacomo


[1] http://lists.openmoko.org/pipermail/community/2011-April/064775.html