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 435] In Dialer Mode/Tag on the ???History??? button/The
Application Title bar wording-???History-All??? is different from
WiKi-???Call History - All???. ([EMAIL PROTECTED])
2. [Bug 436] In Dialer Mode/Tag on the ???History??? button/List
Scroll Area is different from WiKi(No up and down arrow).
([EMAIL PROTECTED])
3. [Bug 366] In Dialer Mode, it unable to input ???+, p, w ???.
([EMAIL PROTECTED])
4. [Bug 442] In Dialer Mode or In Call Mode/The input numbers
area will be cover from top part when we input more than one
line. ([EMAIL PROTECTED])
5. [Bug 600] openmoko-dialer hardcodes widget sizes
([EMAIL PROTECTED])
6. [Bug 532] openmoko-dialer: make distcheck and
autotools-related improvements ([EMAIL PROTECTED])
7. [Bug 567] I/O errors on flash and frozen fs
([EMAIL PROTECTED])
8. [Bug 603] New: timeout at boot menu while typing ?
([EMAIL PROTECTED])
9. [Bug 604] New: DFU at bootdelay conflicts with normal boot
nand read ([EMAIL PROTECTED])
10. [Bug 170] usbtty: sometimes input/output oddities
([EMAIL PROTECTED])
11. Your Bugzilla buglist needs attention. ([EMAIL PROTECTED])
12. [Bug 350] OpenMoko keyboard usability issues
([EMAIL PROTECTED])
13. [Bug 350] OpenMoko keyboard usability issues
([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=435
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2007-06-12 15:13 -------
Changed the text from "History-" to "Call History = - ", as of rev 2224
------- 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=436
------- Additional Comments From [EMAIL PROTECTED] 2007-06-12 15:16 -------
This is not dialer specific? I believe this needs to be fixed at the theme
level. Any comments?
------- 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=366
------- Additional Comments From [EMAIL PROTECTED] 2007-06-12 16:01 -------
I know that there is an intention to make tap-and-hold work on toolkit-level but
until then, I can add a simple tap-and-hold (~5 lines of code) to the dialer,
which would at least allow users to enter these symbols for now.
The original 'button 3' code would still be there, and my code can be removed
when we get tap-and-hold in the tool-kit level.
What do you think?
------- 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=442
------- Additional Comments From [EMAIL PROTECTED] 2007-06-12 16:16 -------
Can you please confirm if this still happens. In my tests, numbers will only
scroll up when you have entered more than 2 lines of numbers, which is the same
for the full-sized dialer.
------- 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=600
------- Additional Comments From [EMAIL PROTECTED] 2007-06-12 17:10 -------
I've committed a fix to the font sizes in the dial pad. Could you let me know
how this looks in QVGA?
------- 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=532
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2007-06-12 17:40 -------
Patch applied in r2227. Thanks.
------- 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=567
------- Additional Comments From [EMAIL PROTECTED] 2007-06-12 19:50 -------
I got this issue a few days ago again.
I have now updated the kernel (2.6.21.3, rev 2xxx; I'll post the precise
revision, when needed). I'll see, if this is now better.
I have some ideas on how to reproduce it, so I hope to either give this bug more
info or close it on my own within a few weeks.
------- 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=603
Summary: timeout at boot menu while typing ?
Product: OpenMoko
Version: current svn head
Platform: Neo1973
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: u-boot
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected],[EMAIL PROTECTED]
Mickey,
you recently mentioned on IRC that you had the Neo power itself
off while at the boot menu and typing over usbtty.
I've tried to reproduce this without success. Could you please
send a more detailed description of what exactly you did ?
Thanks,
- Werner
------- 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=604
Summary: DFU at bootdelay conflicts with normal boot nand read
Product: OpenMoko
Version: unspecified
Platform: Neo1973
URL: http://www.flickr.com/photos/elrond/523490352/
OS/Version: Linux
Status: NEW
Severity: minor
Priority: P3
Component: u-boot
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
I've set bootdelay to something like 7 or 8 seconds, so I don't have to use the
AUX button every time I want to get into u-boot.
This time also allows to fire up dfu and load a new kernel into RAM and boot it
there from u-boot.
Procedures:
1)
* power Neo on (or reboot)
* Use dfu-util to download other kernel into RAM, while bootdelay...
* picocom into u-boot to boot the kernel
(will fail, as the memory is half overwirrten by the nand read)
2)
* power Neo on
* picocom into u-boot to interrupt bootdelay
* dfu-util
* picocom again into u-boot
* boot kernel
(1) gives the error as shown in the pic.
(2) works nicely.
Note1: this bug is a bit related to bug #207.
Note2: I set this bug to minor and lower prio, as a documented (in this bug)
workaround exists.
------- 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=170
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|usbtty: sometimes bogus |usbtty: sometimes
|characters arrive |input/output oddities
------- Additional Comments From [EMAIL PROTECTED] 2007-06-13 03:00 -------
I can still see all these issues on r2040.
u-boot -> host:
I usually get replicated chars from other (previous) parts of the output.
My current best way to reproduce this: "help", then "date".
host -> u-boot:
Just tested:
If I paste 20 chars into u-boot, I only get the first 18 of them in return.
Note: I have retitled this bug to show more clearly, that it is about both
directions. If someone thinks, that these are unrelated, we can still file a
seperate 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 ---
[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=69
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=70
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=137
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=412
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=422
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=448
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=470
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=471
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=536
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=540
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=541
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
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=350
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[EMAIL PROTECTED]
------- Additional Comments From [EMAIL PROTECTED] 2007-06-13 10:32 -------
What method is currently used to make the keyboard? If it's a compiled X or GTK
program this will not work well for graphic designers (I know my wife is one),
unless it loads a humanly readable file to determine the layout.
If you go with Matchbox, layouts are made with simple XML. XML is structured &
well understood by designers (or they have tools that do). A number of layouts
can be defined ( though currently only 1 is supported ) each with any number of
rows of keys, defining the keyboard from top to bottom.
If you go this route let me know. I'd be willing to create some of the layouts I
made for the wishlist (after I get matchbox-keyboard installed or script
something to test it in a browser).
------- 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=350
------- Additional Comments From [EMAIL PROTECTED] 2007-06-13 11:38 -------
openmoko-keyboard actually is a fork of matchbox-keyboard and there is no real
reason why we're maintaining a fork of our own. I'm working on pushing the
additions we made upstream so we can use matchbox-keyboard with a different
layout.
------- 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
