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
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,
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
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
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
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
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.
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
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
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
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.
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.
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
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
14 matches
Mail list logo
