Send buglog mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.openmoko.org/mailman/listinfo/buglog
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]
You can reach the person managing the list at
[EMAIL PROTECTED]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of buglog digest..."
Today's Topics:
1. Re: Openmoko Bug #2082: No icons in illume (Openmoko Public Trac)
2. Re: Openmoko Bug #1767: Enlightenment Error (Openmoko Public Trac)
3. Re: Openmoko Bug #1841: white screen of death (WSOD) after
resume (Openmoko Public Trac)
4. Re: Openmoko Bug #1841: white screen of death (WSOD) after
resume (Openmoko Public Trac)
5. Openmoko Bug #2107: [Devellopement] Cross Qt4 devellopement
is difficult to get (Openmoko Public Trac)
6. Openmoko Bug #2108: Update to newer mono version
(Openmoko Public Trac)
7. Re: Openmoko Bug #1841: white screen of death (WSOD) after
resume (Openmoko Public Trac)
--- Begin Message ---
#2082: No icons in illume
---------------------------+------------------------------------------------
Reporter: john_lee | Owner: raster
Type: defect | Status: closed
Priority: highest | Milestone:
Component: E - Illume | Version:
Severity: blocker | Resolution: fixed
Keywords: | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: always |
---------------------------+------------------------------------------------
Comment(by pooze):
I followed the link to the mailinglist above, and now the icons are back.
Thanks.
What I did, however, was to flash
http://downloads.openmoko.org/releases/Om2008.9/Om2008.9.rootfs.jffs2 and
its kernel to the phone. Then I did an opkg update && opkg upgrade, which
didn't give me as many updates as I was hoping for, so I edited the opkg
files to point to the testing repositories. Then another opkg update &&
opkg upgrade which took a while. Then my icons were gone. Apparently
because I'd gotten a combination of illume-themes and illume-configs that
wasn't compatible or something. But force-removing these packages and
installing the ones suggested by the mail seemed to work for me.
But I was surprised to see the bug fixed in the tracker before I got the
error myself only by using opkg updates in the testing repo. Can any of
you reproduce it using the file I pointed to? Or should I try to reproduce
it here once more to see if it's still an issue?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2082#comment:9>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1767: Enlightenment Error
---------------------------+------------------------------------------------
Reporter: ssweeny | Owner: john_lee
Type: defect | Status: assigned
Priority: normal | Milestone:
Component: E - Illume | Version: Om2008.8
Severity: normal | Resolution:
Keywords: | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: |
---------------------------+------------------------------------------------
Comment(by john_lee):
don't run qtopia in Xsession, start illume first, attach gdb, then run
qtopia.
{{{
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x408a6ba0 (LWP 2456)]
0x407db684 in _int_malloc () from /lib/libc.so.6
(gdb) bt
#0 0x407db684 in _int_malloc () from /lib/libc.so.6
#1 0x407dc3ac in malloc () from /lib/libc.so.6
#2 0x4028057c in _evas_common_rgba_image_surface_alloc (ie=<value
optimized out>, w=0, h=1006291193) at evas_image_main.c:164
#3 0x40253290 in _evas_cache_image_entry_surface_alloc (cache=0x156a60,
ie=0x28f9f0, w=<value optimized out>, h=<value optimized out>)
at evas_cache_image.c:250
#4 0x40253484 in evas_cache_image_surface_alloc (im=0x28f9f0,
w=1006632960, h=1076180100) at evas_cache_image.c:795
#5 0x40a590e8 in eng_font_draw (data=<value optimized out>,
context=0x1ac1b8, surface=0x3c97b8, font=0x1b14e8, x=69, y=157, w=98,
h=32, ow=98, oh=32,
text=0x3ca13c "_ignore_") at evas_engine.c:771
#6 0x4023a954 in evas_object_text_render (obj=0x1ade40, output=0x1ac0e8,
context=0x1ac1b8, surface=0x3c97b8, x=0, y=0) at evas_object_text.c:1534
#7 0x4024f3d4 in evas_render_updates_internal (e=0x1abf00, make_updates=1
'\001', do_draw=1 '\001') at evas_render.c:517
#8 0x4024f814 in evas_render_updates (e=0x1abf00) at evas_render.c:626
#9 0x4002f95c in _ecore_evas_x_render (ee=0x1abde0) at ecore_evas_x.c:330
#10 0x40031c14 in _ecore_evas_x_idle_enter (data=<value optimized out>) at
ecore_evas_x.c:1320
#11 0x406422fc in _ecore_idle_enterer_call () at ecore_idle_enterer.c:101
#12 0x406461e0 in _ecore_main_loop_iterate_internal (once_only=0) at
ecore_main.c:693
#13 0x40646260 in ecore_main_loop_begin () at ecore_main.c:87
#14 0x0002a3dc in main ()
}}}
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1767#comment:4>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1841: white screen of death (WSOD) after resume
-------------------------+--------------------------------------------------
Reporter: Rorschach | Owner: openmoko-devel
Type: defect | Status: new
Priority: highest | Milestone:
Component: unknown | Version: GTA02v5
Severity: critical | Resolution:
Keywords: wsod,resume | Blockedby:
Blocking: | Reproducible: always
-------------------------+--------------------------------------------------
Comment(by jurg):
i am an 'in production' neo freerunner user. i have no other phone
anymore. my girlfriend told me i dropped one or two spots on the ladder of
evolution. but i am sticking to it...
but, as a regular user i am very familiar with the WSOD. i have regular
WSODs and lately i have begun to recognize the pattern.
i got my freerunner in the summer. even though in holland, it was
relatively warm. during that period, while not having a truly stable
phone, i did have a phone without WSODs. slowly the year progressed,
flashing my freerunner once every week, at least. and with the change of
seasons i began to see more and more WSODs.
i had to wear my phone in my the pocket of my pants for a day or two and i
had no WSODs these days. i thought about it a lot (it IS very irritating)
but after these couple of days it struck me. i figured it might have to do
with the temperature of the expensive 'brick'. a simple test did the
trick: when going to bed i left the freerunner sleeping on my router. and,
contrary to most other cold mornings, my freerunner woke without the by
then familiar WSOD.
now, with some behaviour changes, i managed to climb back another step up
the ladder again (so i hope.)
(i hope it helps in finding a solution...)
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1841#comment:38>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1841: white screen of death (WSOD) after resume
----------------------------+-----------------------------------------------
Reporter: Rorschach | Owner: openmoko-devel
Type: defect | Status: new
Priority: highest | Milestone:
Component: unknown | Version: GTA02v5
Severity: critical | Resolution:
Keywords: wsod,resume | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: always |
----------------------------+-----------------------------------------------
Changes (by andy):
* haspatch: => 0
Comment:
It's an interesting clue, but usually heat makes trouble since the silicon
slows down, not the other way around?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1841#comment:39>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2107: [Devellopement] Cross Qt4 devellopement is difficult to get
-------------------------+--------------------------------------------------
Reporter: think-free | Owner: openmoko-devel
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: unknown | Version:
Severity: blocker | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-------------------------+--------------------------------------------------
As a Qt develloper i want to devellop some apps for the freerunner.
There are some steps on the wiki but any of them worked fine ...
Yesterday i've compiled during hours with the mokomakefile to get a
devellopement environnement for the freerunner but without succes ( some
code seems to been broken for compiling as describer in the qt/c++ wiki
page ) ...
We need easy to use devellopement environnement for the freerunner as
trolltech did for the non x11 version of qtopia/qtextended. Just working
librairies and compiler easily installable will be a good start ..
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2107>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2108: Update to newer mono version
--------------------------+-------------------------------------------------
Reporter: SabotageAndi | Owner: openmoko-devel
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: unknown | Version:
Severity: normal | Keywords: mono 1.9.1
Haspatch: 1 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
--------------------------+-------------------------------------------------
The attached patches enables mono 1.9.1 and makes it buildable.
mono_1.9.1_enablebuild.patch: has to be applied to the openembedded
folder.
mono-wapi_glob.patch: copy into openembedded/packages/mono/files
Additional the configure.patch from openembedded/packages/mono/mono-1.2.6
has to be copied to openembedded/packages/mono/mono-1.9.1
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2108>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1841: white screen of death (WSOD) after resume
----------------------------+-----------------------------------------------
Reporter: Rorschach | Owner: openmoko-devel
Type: defect | Status: new
Priority: highest | Milestone:
Component: unknown | Version: GTA02v5
Severity: critical | Resolution:
Keywords: wsod,resume | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: always |
----------------------------+-----------------------------------------------
Comment(by m0nt0):
Yesterday i left my Free runner on the desk, powered on, screen locked but
without suspend, this morning i touched the screen and the WSoD come up.
Yes i'm sure the phone is not in suspension, only the screen off. Actual
setup: latest FDOM, kernel daily build 2008-11-03, uboot daily build
2008-11-03, a personalized splash, but i hope that at least the splash is
not related.
So can this be related to the screen and not to the glamo?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1841#comment:40>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
