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 737] Dialer crashes on startup
      ([EMAIL PROTECTED])
   2. [Bug 735] Network Status bar quits
      ([EMAIL PROTECTED])
   3. [Bug 639] bluetooth panel can't power up radio
      ([EMAIL PROTECTED])
   4. [Bug 642] The cgi script for ordering the neo1973 never gets
      to        step 2 ([EMAIL PROTECTED])
   5. [Bug 740] New: openmoko-devel-image do_rootfs fails in
      makedevs ([EMAIL PROTECTED])
   6. [Bug 740] openmoko-devel-image do_rootfs fails in makedevs
      ([EMAIL PROTECTED])
   7. [Bug 527] The BlueTooth broadcast ID is set wrong (patch)
      ([EMAIL PROTECTED])
   8. [Bug 741] New: Image of Neo hardware shows debug board
      ([EMAIL PROTECTED])
   9. Your Bugzilla buglist needs attention. ([EMAIL PROTECTED])
  10. [Bug 736] the 2007.2 software doesn't let you calibrate your
      screen ([EMAIL PROTECTED])
  11. [Bug 736] the 2007.2 software doesn't let you calibrate your
      screen ([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=737

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED



------- Additional Comments From [EMAIL PROTECTED]  2007-08-22 00:55 -------
Great. Dialer works and I could even call _once_.

Closing.



------- 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=735

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Platform|PC                          |Neo1973





------- 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=639





------- Additional Comments From [EMAIL PROTECTED]  2007-08-22 01:16 -------
Created an attachment (id=258)
 --> 
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=258&action=view)
This enables power on/off the bluetooth radio

This is my first try to make the bt panel functional. Now additional settings
like name and discoverable will come later... hope it'll be useful :)



------- 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=642





------- Additional Comments From [EMAIL PROTECTED]  2007-08-22 01:19 -------
I just ran into this myself and kept getting an error from Net::UPS on line 240
returning an ARRAY when it wasn't expecting it.

After much digging through the mailing list archives, I found the 2-letter state
limitation, changed "California" to "CA" and what'dya know, it worked just fine.

I concur that a 2-letter limit on the field is needed; maxlength="2" size="5"
should be plenty. Having an extra-long text input field gave me the impression
that I should maybe type in the whole state name. If I'd seen a shorter text
field, I might have just tried CA.

Looking back, this was the only thing holding up me ordering a Neo1973 back in
July when they were first released ... argh!



------- 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=740

           Summary: openmoko-devel-image do_rootfs fails in makedevs
           Product: OpenMoko
           Version: 2007.2
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: major
          Priority: P2
         Component: OE bitbake recipes  / build system
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]
                CC: [email protected]


This task first erases the old rootfs, creates rootfs/dev then calls makedevs.

However, the input file to makedevs also specifies three files in rootfs/bin
which it is unable to write because of the missing directory.

openembedded/classes/image.bbclass needs to create rootfs/bin before calling
makedevs

Error is shown below:

/home/moko2$ make openmoko-devel-image
( cd build && . ../setup-env && \
          bitbake openmoko-devel-image )
NOTE: Handling BitBake files: / (4566/4566) [100 %]
NOTE: Parsing finished. 4342 cached, 0 parsed, 224 skipped, 0 masked.
NOTE: build 200708211515: started

OE Build Configuration:
BB_VERSION     = "1.8.6"
OE_REVISION    = "ea002ef2dfcdc37b8ecca56a22b29c5104e27f75"
TARGET_ARCH    = "arm"
TARGET_OS      = "linux-gnueabi"
MACHINE        = "fic-gta01"
DISTRO         = "openmoko"
DISTRO_VERSION = "P1-August-Snapshot-20070821"
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 3391 of 3392 (ID: 10,
/home/moko2/org.openembedded.dev/packages/images/openmoko-devel-image.bb, 
do_rootfs)
NOTE: package openmoko-devel-image-1.0: started
NOTE: package openmoko-devel-image-1.0-r0: task do_rootfs: started
ERROR: function do_rootfs failed
ERROR: log data follows
(/home/moko2/build/tmp/work/fic-gta01-angstrom-linux-gnueabi/openmoko-devel-image-1.0-r0/temp/log.do_rootfs.9549)
| + rm -rf /home/moko2/build/tmp/rootfs
| + '[' 0 '!=' 1 ']'
| + mkdir -p /home/moko2/build/tmp/rootfs/dev
| + for devtable in /home/moko2/openembedded/files/device_table-minimal.txt
| + makedevs -r /home/moko2/build/tmp/rootfs -D
/home/moko2/openembedded/files/device_table-minimal.txt
| makedevs: /home/moko2/build/tmp/rootfs/bin/tinylogin: file can not be created!
NOTE: Task failed:
/home/moko2/build/tmp/work/fic-gta01-angstrom-linux-gnueabi/openmoko-devel-image-1.0-r0/temp/log.do_rootfs.9549
NOTE: package openmoko-devel-image-1.0-r0: task do_rootfs: failed
ERROR: TaskFailed event exception, aborting
NOTE: package openmoko-devel-image-1.0: failed
ERROR: Build of
/home/moko2/org.openembedded.dev/packages/images/openmoko-devel-image.bb
do_rootfs failed
ERROR: Task 10
(/home/moko2/org.openembedded.dev/packages/images/openmoko-devel-image.bb,
do_rootfs) failed
NOTE: Tasks Summary: Attempted 3390 tasks of which 3390 didn't need to be rerun
and 1 failed.
ERROR:
'/home/moko2/org.openembedded.dev/packages/images/openmoko-devel-image.bb' 
failed
make: *** [openmoko-devel-image] Error 1



------- 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=740





------- Additional Comments From [EMAIL PROTECTED]  2007-08-22 01:43 -------
Patch to fix/work around problem:
Index: moko2/openembedded/classes/image.bbclass
===================================================================
--- moko2.orig/openembedded/classes/image.bbclass       2007-08-21
16:37:48.000000000 -0700
+++ moko2/openembedded/classes/image.bbclass    2007-08-21 16:37:56.000000000 
-0700
@@ -72,6 +72,7 @@
 
        if [ "${USE_DEVFS}" != "1" ]; then
                mkdir -p ${IMAGE_ROOTFS}/dev
+               mkdir -p ${IMAGE_ROOTFS}/bin
                for devtable in [EMAIL PROTECTED](d)}; do
                        makedevs -r ${IMAGE_ROOTFS} -D $devtable
                done




------- 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=527





------- Additional Comments From [EMAIL PROTECTED]  2007-08-22 04:16 -------
Actually the friendly name should be set by a first usage/boot device wizard.
Check the Nokia 770 and N800 and how they handle it.




------- 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=741

           Summary: Image of Neo hardware shows debug board
           Product: Site Infrastructure
           Version: unspecified
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: minor
          Priority: P3
         Component: OpenMoko.Com
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]
                CC: [email protected]


The image under the "Hardware" tab at the following URL...

http://www.openmoko.com/products-neo-base-03-hardware.html

...shows a debug board. I expected an image of a Neo board like the ones in the
wiki.



------- 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 ---
[This e-mail has been automatically generated.]

You have one or more bugs assigned to you in the Bugzilla 
bugsystem (http://bugzilla.openmoko.org/cgi-bin/bugzilla/) that require
attention.

All of these bugs are in the NEW state, and have not been touched
in 7 days or more.  You need to take a look at them, and 
decide on an initial action.

Generally, this means one of three things:

(1) You decide this bug is really quick to deal with (like, it's INVALID),
    and so you get rid of it immediately.
(2) You decide the bug doesn't belong to you, and you reassign it to someone
    else.  (Hint: if you don't know who to reassign it to, make sure that
    the Component field seems reasonable, and then use the "Reassign bug to
    owner of selected component" option.)
(3) You decide the bug belongs to you, but you can't solve it this moment.
    Just use the "Accept bug" command.

To get a list of all NEW bugs, you can use this URL (bookmark it if you like!):

    
http://bugzilla.openmoko.org/cgi-bin/bugzilla/buglist.cgi?bug_status=NEW&[EMAIL 
PROTECTED]

Or, you can use the general query page, at
http://bugzilla.openmoko.org/cgi-bin/bugzilla/query.cgi.

Appended below are the individual URLs to get to all of your NEW bugs that 
haven't been touched for a week or more.

You will get this message once a day until you've dealt with these bugs!

  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=112
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=114
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=141
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=181
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=301
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=340
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=412
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=448
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=466
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=555
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=572
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=589
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=624
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=630
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=696
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=700



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=736

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[EMAIL PROTECTED]



------- Additional Comments From [EMAIL PROTECTED]  2007-08-22 10:26 -------
I can confirm this, it's quite annoying. You have this new snapshot up and 
running, but all you can do is to see some of the new screens which you 
accidentally hit while trying to click somewhere else.
This renders the snapshot unusable in qemu at the moment.
In the earlier snapshots you had to calibrate the screen on first boot, but 
this is now removed. It should be enabled again.

I'm using
OpenMoko-openmoko-devel-image-glibc-P1-August-Snapshot-20070819-fic-
gta01.rootfs.jffs2
uImage-2.6.21.5-r3-fic-gta01.bin
u-boot-gta01bv4-1.2.0+git8993e54b6f397973794f3d6f47d3b3c0c98dd4f6+svn20070819-
r0.bin
on qemu-neo1973, svn-Revision 2771.



------- 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=736





------- Additional Comments From [EMAIL PROTECTED]  2007-08-22 11:11 -------
I disagree. For the actual device owners, not needing to calibrate is actually a
good thing. I understand that for QEmu it doesn't work though.

As an interrim solution, how about removing /etc/pointercal from the image. On
the next start of kdrive, you should be presented the calibration dialog again.




------- 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

Reply via email to