Re: [qtMoko] Request needed to restore bluetooth
Hello everyone and sorry for this re-posting, but I miss the subject last time. Guilhem Bonnefille wrote: [...] 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@neo:~# cat /etc/init.d/qpe.sh #!/bin/sh [...] . /opt/qtmoko/qpe.env [...] root@neo:~# . /opt/qtmoko/qpe.env root@neo:/root# root@neo:/root# qpe qpe: error while loading shared libraries: /opt/qtmoko/lib/libopenobex.so.1: cannot read file data: Input/output error root@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@neo:/root# wc -l cose 107 cose root@neo:~# dpkg -S /opt/qtmoko/lib/libdissipate2.so.1 qtmoko: /opt/qtmoko/lib/libdissipate2.so.1 root@neo:~# dpkg -S /opt/qtmoko/lib/libopenobex.so.1 qtmoko: /opt/qtmoko/lib/libopenobex.so.1 root@neo:~# dpkg -S /opt/qtmoko/lib/libqtopiatheming.so.4 qtmoko: /opt/qtmoko/lib/libqtopiatheming.so.4 root@neo:~# apt-get remove qtmoko [...] root@neo:~# apt-get install qtmoko [...] and everything turned OK. Regards Giacomo [1] http://lists.openmoko.org/pipermail/community/2011-April/064775.html -- ## giacomo 'giotti' mariani gpg --keyserver pool.sks-keyservers.net --recv-key 0x99bfa859 O ASCII ribbon campaign: stop HTML mail www.asciiribbon.org ## ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [qtMoko] Request needed to restore bluetooth
2011/6/7 Giacomo 'giotti' Mariani giacomomari...@yahoo.it: Guilhem Bonnefille wrote: [...] 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]. [...] Thanks for your attention. But as you can see, I reproduced, bypass the problem and identify a possible origin. Conclusion: in my case, it is not I/O error but a simple bug, hidden and waiting for a new user. :-) -- 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
Re: [qtMoko] Request needed to restore bluetooth
On Monday 06 June 2011 22:16:38 Guilhem Bonnefille wrote: With the patch, now. (sorry) For me it seems to work nice. It's not commited https://github.com/radekp/qtmoko/commit/aa1b3efffa15c8bd61befd8a7aa4f65fec2fef6d Thanks! Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [qtMoko] Request needed to restore bluetooth
On Tuesday 07 June 2011 12:58:22 Radek Polak wrote: For me it seems to work nice. It's not commited erm it's now commited of course ;-) Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [qtMoko] Request needed to restore bluetooth
2011/6/5 Radek Polak pson...@seznam.cz: Guilhem Bonnefille wrote: 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::btcallvoid(QString const, QDBusReplyvoid, QListQVariant, 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?) Hmm this looks quite strange since it segfaults in the Qt call (QDBusAbstractInterface). I cant tell more just from the stacktrace. It would be best if i could debug this locally. Hmm and i will probably rework the whole bluetooth library after experience with FSO, e.g. so that the BT dbus bindings are autogenerated. Reading traces and code, I think I found at least one aspect of the bug. Here is a small patch. As I'm not yet able to compile and test my modifications, this is a blind patch. Can you give me feedback, please? -- 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
Re: [qtMoko] Request needed to restore bluetooth
With the patch, now. (sorry) 2011/6/6 Guilhem Bonnefille guilhem.bonnefi...@gmail.com: 2011/6/5 Radek Polak pson...@seznam.cz: Guilhem Bonnefille wrote: 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::btcallvoid(QString const, QDBusReplyvoid, QListQVariant, 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?) Hmm this looks quite strange since it segfaults in the Qt call (QDBusAbstractInterface). I cant tell more just from the stacktrace. It would be best if i could debug this locally. Hmm and i will probably rework the whole bluetooth library after experience with FSO, e.g. so that the BT dbus bindings are autogenerated. Reading traces and code, I think I found at least one aspect of the bug. Here is a small patch. As I'm not yet able to compile and test my modifications, this is a blind patch. Can you give me feedback, please? -- Guilhem BONNEFILLE -=- JID: gu...@im.apinc.org MSN: guilhem_bonnefi...@hotmail.com -=- mailto:guilhem.bonnefi...@gmail.com -=- http://nathguil.free.fr/ -- Guilhem BONNEFILLE -=- JID: gu...@im.apinc.org MSN: guilhem_bonnefi...@hotmail.com -=- mailto:guilhem.bonnefi...@gmail.com -=- http://nathguil.free.fr/ fix-bluetooth.patch Description: Binary data ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [qtMoko] Request needed to restore bluetooth
2011/6/2 Radek Polak pson...@seznam.cz:
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::btcallvoid(QString
const, QDBusReplyvoid, QListQVariant, 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.
--
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
Re: [qtMoko] Request needed to restore bluetooth
FIXED. At least, my Neo runs again ;-)
2011/6/2 Guilhem Bonnefille guilhem.bonnefi...@gmail.com:
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.
I found the configuration file containing the disabling of bluetooth:
/home/root/Settings/Trolltech/Launcher.conf
Contained:
[AppLoading]
PreloadApps=bt-poweroff.sh
Once commented, qpe runs correctly. But there is still a bug in the
code when bluetooth is disabled.
--
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
Re: [qtMoko] Request needed to restore bluetooth
You wrote: Thanks for adding my name as author of the related change. But, I also noted that two scripts have the kill list: /etc/init.d/qtmoko and /etc/init.d/qpe.sh /etc/init.d/qtmoko is the patched one - debian intaller copies it there. /etc/init.d/qpe.sh is now obsolete - it was renamed to the one above ^^ Other question: it seems that qtMoko exists on two public sites: SourceForge and Github. What is the official one? I like github for source code, so the latest code is there. For everything other there is sourceforge. I sometimes also update the git on sourceforge, because of ohloh statistics. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [qtMoko] Request needed to restore bluetooth
Guilhem Bonnefille wrote: 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::btcallvoid(QString const, QDBusReplyvoid, QListQVariant, 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?) Hmm this looks quite strange since it segfaults in the Qt call (QDBusAbstractInterface). I cant tell more just from the stacktrace. It would be best if i could debug this locally. Hmm and i will probably rework the whole bluetooth library after experience with FSO, e.g. so that the BT dbus bindings are autogenerated. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [qtMoko] Request needed to restore bluetooth
2011/6/5 Radek Polak pson...@seznam.cz: You wrote: Thanks for adding my name as author of the related change. But, I also noted that two scripts have the kill list: /etc/init.d/qtmoko and /etc/init.d/qpe.sh /etc/init.d/qtmoko is the patched one - debian intaller copies it there. /etc/init.d/qpe.sh is now obsolete - it was renamed to the one above ^^ OK. It is certainly normal as I updated qtMoko with tarball. I will delete this file. Other question: it seems that qtMoko exists on two public sites: SourceForge and Github. What is the official one? I like github for source code, so the latest code is there. For everything other there is sourceforge. I sometimes also update the git on sourceforge, because of ohloh statistics. I suggest to update sourceforge's Git repo regularly with all official stuff. We do that on the viking project: sourceforge is the official repo and github (or others) contains the private repo of contributors, with experimental works. -- 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
Re: [qtMoko] Request needed to restore bluetooth
2011/6/2 Radek Polak pson...@seznam.cz:
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
r
I did not find time to start debugger yet. But please, find the qpe's
output attached.
Best regards,
--
Guilhem BONNEFILLE
-=- JID: gu...@im.apinc.org MSN: guilhem_bonnefi...@hotmail.com
-=- mailto:guilhem.bonnefi...@gmail.com
-=- http://nathguil.free.fr/
qpe.traces
Description: Binary data
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
[qtMoko] Request needed to restore bluetooth
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
Re: [qtMoko] Request needed to restore bluetooth
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
r
Regards
Radek
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
