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 367] openmoko-today does not show the operator name
([EMAIL PROTECTED])
2. [Bug 969] openmoko-today taskmanager application icons
([EMAIL PROTECTED])
3. [Bug 837] Lack of / small icons in list of running tasks
([EMAIL PROTECTED])
4. [Bug 1017] Xglamo stalls after some time
([EMAIL PROTECTED])
5. [Bug 367] openmoko-today does not show the operator name
([EMAIL PROTECTED])
6. [Bug 788] Starting or stopping gsmd completely locks up the
Neo ([EMAIL PROTECTED])
7. [Bug 837] Lack of / small icons in list of running tasks
([EMAIL PROTECTED])
8. [Bug 1017] Xglamo stalls after some time
([EMAIL PROTECTED])
9. [Bug 986] [Dates] creating new event not intuitive
([EMAIL PROTECTED])
10. [Bug 965] Clock Placement ([EMAIL PROTECTED])
11. [Bug 1037] Clock redrawing is ugly
([EMAIL PROTECTED])
12. [Bug 945] moko-gtk-engine throws errors
([EMAIL PROTECTED])
13. [Bug 1037] Clock redrawing is ugly
([EMAIL PROTECTED])
14. [Bug 931] matchbox-panel-2 segfault in
pango_font_get_coverage() ([EMAIL PROTECTED])
15. [Bug 1037] Clock redrawing is ugly
([EMAIL PROTECTED])
16. [Bug 908] Unexpected onscreen keyboard expose/collapse
behavior in openmoko-terminal2 ([EMAIL PROTECTED])
17. [Bug 965] Clock Placement ([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=367
------- Additional Comments From [EMAIL PROTECTED] 2007-12-06 12:30 -------
This is in phone-kit now, so I'll fix this
------- 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=969
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |DUPLICATE
------- Additional Comments From [EMAIL PROTECTED] 2007-12-06 12:45 -------
*** This bug has been marked as a duplicate of 837 ***
------- 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=837
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[EMAIL PROTECTED]
------- Additional Comments From [EMAIL PROTECTED] 2007-12-06 12:45 -------
*** Bug 969 has been marked as a duplicate of this 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=1017
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #405 is|0 |1
obsolete| |
------- Additional Comments From [EMAIL PROTECTED] 2007-12-06 13:03 -------
Created an attachment (id=416)
-->
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=416&action=view)
use more logical values
On page 21 of Glamo 3365 Application Note, a set of reference only values is
given. Quoted from the spec:
1. Address bus ready and CS pin falling.
2. Setup time 30nS.
3. Write pin falling and wait pin output falling.
4. Write active time = 150nS. (If CPU supports wait function, you can skip this
setting and CPU will take it automatic.)
5. Hold time 30nS.
6. Turnaround 30nS for next read/write.
Another set of values for reading is also given, which is the same except that
it needs 280ns of active time.
s3c2442 supports wait function. We don't really care about the active time.
The s3c2442 manual says Tacc should be equal to or larger than 4 clocks when
nWAIT is enabled. We choose 4 clocks here.
As for Tcos and Tcoh, the HCLK runs at 100~125MHz, which is equal to
8~10ns/clock. To satisfy the (minimal) 30ns setup time, Tcos and Tcoh are set
to 4 clocks.
(I am pretending logical. Correct me if I am wrong :-)
------- 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=367
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2007-12-06 14:25 -------
Fixed in r3605
------- 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=788
------- Additional Comments From [EMAIL PROTECTED] 2007-12-06 15:06 -------
Hehe! The classic developer vs support clash develops!
So the developer mindset says it's better to leave it broken until someone
rewrites the serial driver to correct its behavior. The support mindset says
that the users need something to keep this horrible crash from occurring, even
if that fix is less than technically pure and elegant.
May I suggest that *SOMEBODY* pick up the task of (at least) providing guidance
on the "Non-Questionable" solution so that said solution can be at least
investigated, and in the meantime, perhaps it might be possible to incorporate
one of these patches so that these crashes cease?
Just FYI, as "Questionable" as these patches might be, one of them is applied to
all 2.6.22.5 kernels built with OE, and as "Questionable" as it might be it has
nicely resolved the problem with nary an issue or side-effect reported. I fully
realize that does not qualify the fix as "elegant" or "correct", it merely
points out that for those who are "support-minded", the fix qualifies as a
solution that keeps the device running. :-)
C'mon folks -- we have a phone to build. If we let ourselves be distracted into
re-writing stock parts of the Linux kernel to *elegantly* support the inelegant
GTA01 hardware hackery, we'll never get anything done. One vote here for
pragmatism.
------- 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=837
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2007-12-06 15:42 -------
Icon size is fixed in r3607.
In the case where there isn't an icon, it's because the applications aren't
setting window icons - this needs to be fixed for each individual application.
If we want to match a running application to its launcher file, we need to set a
custom window property so that we can match (for example, the argv[0] of the
application would do) - but again, this is something that needs to be fixed for
each individual application first.
------- 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=1017
------- Additional Comments From [EMAIL PROTECTED] 2007-12-06 15:54 -------
s/Quoted from the spec/To my understanding/
bugzilla should allow people to edit their own 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=986
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2007-12-06 16:22 -------
Fixed in r672
------- 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=965
------- Additional Comments From [EMAIL PROTECTED] 2007-12-06 17:00 -------
We had the clock at the top of the screen previously, but it takes up quite a
bit of valuable space if the window has a long title or there are a lot of
icons.
I would add a preference to allow disabling the big clock from the home screen,
and adding one next to the date instead, as in your second suggestion.
------- 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=1037
------- Additional Comments From [EMAIL PROTECTED] 2007-12-06 17:04 -------
I think I would prefer not drawing anything until the entire clock is ready.
This would also eliminate the need for multiple buffers.
------- 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=945
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WORKSFORME
------- Additional Comments From [EMAIL PROTECTED] 2007-12-06 17:05 -------
Resolving as WORKSFORME since I can't reproduce and no further information has
been given.
------- 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=1037
------- Additional Comments From [EMAIL PROTECTED] 2007-12-06 17:07 -------
Well no, you'd still need multiple buffers, otherwise you'd have to redraw the
entire clock when the time changes (which is slow) - but will implement this
then
------- 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=931
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
------- Additional Comments From [EMAIL PROTECTED] 2007-12-06 17:08 -------
Marking as INVALID since this is not a bug in any OpenMoko authored code (as
comment #1 says). If you can reproduce this with debugging symbols, please
re-open and add the upstream bug number to a comment on this 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=1037
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2007-12-06 17:18 -------
This is fixed in libjana r698
------- 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=908
------- Additional Comments From [EMAIL PROTECTED] 2007-12-06 17:49 -------
I can reproduce this bug on the device, but not in my developer environment on
the PC.
In summary, when the VTE widget expands, extra space is added below the cursor.
When the widget shrinks, the extra space is not removed (as expected), so the
content is pushed up the screen.
------- 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=965
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2007-12-06 18:00 -------
Fixed in r3608 - To put the clock in the date button, set the gconf key
"/desktop/poky/interface/small_clock" to true (boolean)
------- 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
