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. [Bug 421] systray applet only shows white rectangles
([EMAIL PROTECTED])
2. [Bug 414] Verify that auto open/close inputmethods works
correctly ([EMAIL PROTECTED])
3. [Bug 414] Verify that auto open/close inputmethods works
correctly ([EMAIL PROTECTED])
4. [Bug 748] Stylus keyboard cannot use square brackets
([EMAIL PROTECTED])
5. [Bug 793] No package 'matchbox-panel' found
([EMAIL PROTECTED])
6. [Bug 775] bluetooth can not be enabled (kernel
2.6.22.5-moko11 / 20070829) ([EMAIL PROTECTED])
7. [Bug 791] webkit-gtk won't link
([EMAIL PROTECTED])
8. Re: [Bug 791] webkit-gtk won't link (Lon Lentz)
9. Re: [Bug 791] webkit-gtk won't link (Stefan Schmidt)
10. [Bug 791] webkit-gtk won't link
([EMAIL PROTECTED])
11. [Bug 801] New: qemu-native fails to build on gentoo/gcc-3.4.6
([EMAIL PROTECTED])
12. [Bug 781] LM4857 should be turned off on a reboot notifier
([EMAIL PROTECTED])
13. [Bug 781] LM4857 should be turned off on a reboot notifier
([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=421
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2007-09-05 14:55 -------
I just added a patch for a matchbox-keyboard to OE.dev and sent it upstream for
discussion and hopefully inclusion.
With this the white rectangle is no more needed to enable/disable the keyboard
if autopopup fails.
We still need a real Inputmethod API. But this is discussed in Bug #44
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=414
------- Additional Comments From [EMAIL PROTECTED] 2007-09-05 15:40 -------
Besides not using mbinputmgr we have this now. We use the gtk-im from
matchbox-keyboard which opens up when a text input field gets the focus.
For non-gtk applications we have a small applet to toggle keyboard presence.
anything else missing or is this isue fixed?
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=414
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2007-09-05 15:51 -------
Verified with mickey that this bug can be closed. It's more a CLOSED then a real
FIXED.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=748
------- Additional Comments From [EMAIL PROTECTED] 2007-09-05 16:09 -------
This is due to mb_kbd_ui_send_press passing the modifiers to fakekey_press.
This is okay for a "default" layout, but breaks when we deviate from that.
The problem is also obvious if you reverse the capitalization on a letter:
<key obey-caps='true'>
<default display="A" />
<shifted display="a" />
</key>
Will both yield 'A', since a + shift results in 'A'
I'm not sure how we should fix this, I'll inquire on the matchbox ml.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=793
------- Additional Comments From [EMAIL PROTECTED] 2007-09-05 16:10 -------
A build from scratch over at the last night showed no errors for me. Is this
still a problem for you?
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=775
------- Additional Comments From [EMAIL PROTECTED] 2007-09-05 16:10 -------
So it works again for you and the bug can be closed?
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=791
------- Additional Comments From [EMAIL PROTECTED] 2007-09-05 16:11 -------
The new build after gcc upgrade works for all of you and the bug can be closed?
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
I don't know if this is the right place for this, but after clobbering it
last night the update succeeded for me.
On 9/5/07, [EMAIL PROTECTED] <
[EMAIL PROTECTED]> wrote:
>
> http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=791
>
>
>
>
>
> ------- Additional Comments From [EMAIL PROTECTED] 2007-09-05 16:11
> -------
> The new build after gcc upgrade works for all of you and the bug can be
> closed?
>
>
--- End Message ---
--- Begin Message ---
Hello.
On Wed, 2007-09-05 at 10:12, Lon Lentz wrote:
> I don't know if this is the right place for this,
The right place is to add it to the entry on the bugtracker website.
I'll do this for you now.
> but after clobbering it last night the update succeeded for me.
So it can be closed. I'll do that.
regards
Stefan Schmidt
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=791
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2007-09-05 16:30 -------
Comment from Lon Lentz <[EMAIL PROTECTED]> on the buglist:
I don't know if this is the right place for this, but after clobbering it
last night the update succeeded for me.
It also works fine for me so I close this bug. If somebody still have the
problem after a build from scratch please reopen.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=801
Summary: qemu-native fails to build on gentoo/gcc-3.4.6
Product: OpenMoko
Version: 2007.2
Platform: PC
URL: http://lists.openmoko.org/pipermail/openmoko-devel/2007-
August/001359.html
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: qemu-neo1973
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
make openmoko-devel-image fails at qemu-native:
( cd build && . ../setup-env && \
bitbake openmoko-devel-image )
NOTE: Handling BitBake files: | (4648/4648) [100 %]
NOTE: Parsing finished. 4421 cached, 0 parsed, 227 skipped, 0 masked.
NOTE: build 200709051611: started
OE Build Configuration:
BB_VERSION = "1.8.8"
OE_REVISION = "f187242e911a395651f8c0b903c471eaa5944ab9"
TARGET_ARCH = "arm"
TARGET_OS = "linux-gnueabi"
MACHINE = "fic-gta01"
DISTRO = "openmoko"
DISTRO_VERSION = "P1-August-Snapshot-20070905"
TARGET_FPU = "soft"
NOTE: Resolving missing task queue dependencies
NOTE: preferred version 2.5 of glibc not available (for item
virtual/arm-angstrom-linux-gnueabi-libc-for-gcc)
NOTE: Preparing runqueue
NOTE: Executing runqueue
NOTE: Running task 133 of 3321 (ID: 1144,
/home/fr33z3/openmoko/openembedded/packages/qemu/qemu-native_20070613.bb,
do_compile)
NOTE: package qemu-native-0.9.0+cvs20070613: started
NOTE: package qemu-native-0.9.0+cvs20070613-r5: task do_compile: started
ERROR: function do_compile failed
ERROR: log data follows
(/home/fr33z3/openmoko/build/tmp/work/i686-linux/qemu-native-0.9.0+cvs20070613-r5/temp/log.do_compile.28368)
| NOTE: make
| make[1]: Entering directory
`/home/fr33z3/openmoko/build/tmp/work/i686-linux/qemu-native-0.9.0+cvs20070613-r5/qemu'
| make -C i386-linux-user all
| make[2]: Entering directory
`/home/fr33z3/openmoko/build/tmp/work/i686-linux/qemu-native-0.9.0+cvs20070613-r5/qemu/i386-linux-user'
| gcc-3.4.6 -Wall -O2 -g -fno-strict-aliasing -fno-reorder-blocks -fno-gcse
-fno-optimize-sibling-calls -fno-crossjumping -fno-align-labels
-fno-align-jumps -fno-align-functions -mpreferred-stack-boundary=2
-fomit-frame-pointer -I. -I..
-I/home/fr33z3/openmoko/build/tmp/work/i686-linux/qemu-native-0.9.0+cvs20070613-r5/qemu/target-i386
-I/home/fr33z3/openmoko/build/tmp/work/i686-linux/qemu-native-0.9.0+cvs20070613-r5/qemu
-I/home/fr33z3/openmoko/build/tmp/work/i686-linux/qemu-native-0.9.0+cvs20070613-r5/qemu/linux-user
-I/home/fr33z3/openmoko/build/tmp/work/i686-linux/qemu-native-0.9.0+cvs20070613-r5/qemu/linux-user/i386
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
-I/home/fr33z3/openmoko/build/tmp/work/i686-linux/qemu-native-0.9.0+cvs20070613-r5/qemu/fpu
-DHAS_AUDIO -DHAS_AUDIO_CHOICE
-I/home/fr33z3/openmoko/build/tmp/work/i686-linux/qemu-native-0.9.0+cvs20070613-r5/qemu/slirp
-c -o op.o
/home/fr33z3/openmoko/build/tmp/work/i686-linux/qemu-native-0.9.0+cvs20070613-r5/qemu/target-i386/op.c
|
/home/fr33z3/openmoko/build/tmp/work/i686-linux/qemu-native-0.9.0+cvs20070613-r5/qemu/target-i386/ops_sse.h:
In function `op_psrlq_mmx':
|
/home/fr33z3/openmoko/build/tmp/work/i686-linux/qemu-native-0.9.0+cvs20070613-r5/qemu/target-i386/ops_sse.h:213:
error: unable to find a register to spill in class `GENERAL_REGS'
|
/home/fr33z3/openmoko/build/tmp/work/i686-linux/qemu-native-0.9.0+cvs20070613-r5/qemu/target-i386/ops_sse.h:213:
error: this is the insn:
| (insn:HI 36 35 37 3
/home/fr33z3/openmoko/build/tmp/work/i686-linux/qemu-native-0.9.0+cvs20070613-r5/qemu/target-i386/ops_sse.h:207
(parallel [
| (set (reg:DI 63 [ <variable>.q ])
| (lshiftrt:DI (reg:DI 63 [ <variable>.q ])
| (subreg:QI (reg/v:SI 60 [ shift ]) 0)))
| (clobber (scratch:SI))
| (clobber (reg:CC 17 flags))
| ]) 309 {lshrdi3_1} (insn_list 33 (insn_list 35 (nil)))
| (expr_list:REG_DEAD (reg/v:SI 60 [ shift ])
| (expr_list:REG_UNUSED (reg:CC 17 flags)
| (expr_list:REG_UNUSED (scratch:SI)
| (nil)))))
|
/home/fr33z3/openmoko/build/tmp/work/i686-linux/qemu-native-0.9.0+cvs20070613-r5/qemu/target-i386/ops_sse.h:213:
confused by earlier errors, bailing out
| make[2]: *** [op.o] Error 1
| make[2]: Leaving directory
`/home/fr33z3/openmoko/build/tmp/work/i686-linux/qemu-native-0.9.0+cvs20070613-r5/qemu/i386-linux-user'
| make[1]: *** [subdir-i386-linux-user] Error 2
| make[1]: Leaving directory
`/home/fr33z3/openmoko/build/tmp/work/i686-linux/qemu-native-0.9.0+cvs20070613-r5/qemu'
| FATAL: oe_runmake failed
NOTE: Task failed:
/home/fr33z3/openmoko/build/tmp/work/i686-linux/qemu-native-0.9.0+cvs20070613-r5/temp/log.do_compile.28368
NOTE: package qemu-native-0.9.0+cvs20070613-r5: task do_compile: failed
ERROR: TaskFailed event exception, aborting
NOTE: package qemu-native-0.9.0+cvs20070613: failed
ERROR: Build of
/home/fr33z3/openmoko/openembedded/packages/qemu/qemu-native_20070613.bb
do_compile failed
ERROR: Task 1144
(/home/fr33z3/openmoko/openembedded/packages/qemu/qemu-native_20070613.bb,
do_compile) failed
NOTE: Tasks Summary: Attempted 132 tasks of which 132 didn't need to be rerun
and 1 failed.
ERROR:
'/home/fr33z3/openmoko/openembedded/packages/qemu/qemu-native_20070613.bb'
failed
make: *** [openmoko-devel-image] Error 1
Searching google brings up loads of people with problems compiling with gcc-4,
but this is gcc-3.4.6 failing!
There was a post on openmoko-devel by Jeff about the exact same problem:
http://lists.openmoko.org/pipermail/openmoko-devel/2007-August/001359.html
Is this a gcc bug?
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=781
------- Additional Comments From [EMAIL PROTECTED] 2007-09-05 17:02 -------
Hi Alex,
I have tested your patch. Currently, The lm4857 driver didn't receive
suspend/shutdown message when neo1973 suspended/powered off. So far, I still
trace the relation between lm4857 and power manager. :(
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=781
------- Additional Comments From [EMAIL PROTECTED] 2007-09-05 17:12 -------
My patch is in fact doing the same actual processing that is done when the Amp
Mode is set to 'Off', if the suspend message is not issued the same way, then
this is expected.
Do you know the actual command in order to suspend the chip so I can modify the
patch accordingly ?
meanwhile, I'll check on the chip datasheet to validate the way I did it.
Thanks for testing it anyway.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
