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 829] Filtering view does not give information that it is
      filtered ([EMAIL PROTECTED])
   2. [Bug 832] Requester with list of phone number lack types
      ([EMAIL PROTECTED])
   3. [Bug 818] Closing other apps does not ask for confirmation
      ([EMAIL PROTECTED])
   4. [Bug 832] Requester with list of phone number lack types
      ([EMAIL PROTECTED])
   5. [Bug 894] gsmd crashes libgsmd-tool disconnects too quickly
      ([EMAIL PROTECTED])
   6. [Bug 76] Implement PWM control for vibrator
      ([EMAIL PROTECTED])
   7. [Bug 914] File upload to wiki not working
      ([EMAIL PROTECTED])
   8. [Bug 914] File upload to wiki not working
      ([EMAIL PROTECTED])
   9. [Bug 914] File upload to wiki not working
      ([EMAIL PROTECTED])
  10. [Bug 914] File upload to wiki not working
      ([EMAIL PROTECTED])
  11. [Bug 693] Invalid timeval passed to setitmer()
      ([EMAIL PROTECTED])
  12. [Bug 705] gsmd does not process responses from the modem
      ([EMAIL PROTECTED])
  13. [Bug 705] gsmd does not process responses from the modem
      ([EMAIL PROTECTED])
  14. [Bug 693] Invalid timeval passed to setitmer()
      ([EMAIL PROTECTED])
  15. [Bug 914] File upload to wiki not working
      ([EMAIL PROTECTED])
  16. Your Bugzilla buglist needs attention. ([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=829

[EMAIL PROTECTED] changed:

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



------- Additional Comments From [EMAIL PROTECTED]  2007-10-09 15:42 -------
I've now implemented the behaviour described by Chris.



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





------- Additional Comments From [EMAIL PROTECTED]  2007-10-09 16:02 -------
Exactly.



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

[EMAIL PROTECTED] changed:

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



------- Additional Comments From [EMAIL PROTECTED]  2007-10-09 16:15 -------
Changed button order in r3124



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

[EMAIL PROTECTED] changed:

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



------- Additional Comments From [EMAIL PROTECTED]  2007-10-09 17:00 -------
Fixed in SVN.



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





------- Additional Comments From [EMAIL PROTECTED]  2007-10-09 17:43 -------
Would you please post the log of how you confuse gsmd? 
(better contains both gsmd and libgsmd-tool message )
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=76

[EMAIL PROTECTED] changed:

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



------- Additional Comments From [EMAIL PROTECTED]  2007-10-09 19:31 -------
this has been committed as of svn rev. 3137



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





------- Additional Comments From [EMAIL PROTECTED]  2007-10-10 00:12 -------
Created an attachment (id=340)
 --> 
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=340&action=view)
NetBSD/evbarm 3.1 NEO1973 syssrc

an actual upload now not uploadable ;) to the wiki.



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





------- Additional Comments From [EMAIL PROTECTED]  2007-10-10 00:58 -------
Created an attachment (id=341)
 --> 
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=341&action=view)
NetBSD/evbarm 3.1 NEO1973 kernel




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

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
    Attachment #341|NetBSD/evbarm 3.1 NEO1973   |NetBSD/evbarm 3.1 NEO1973
        description|kernel                      |kernel 20071010





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

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
    Attachment #340|NetBSD/evbarm 3.1 NEO1973   |NetBSD/evbarm 3.1 NEO1973
        description|syssrc                      |syssrc 20071010





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





------- Additional Comments From [EMAIL PROTECTED]  2007-10-10 01:57 -------
 When calculating the next expiration, the timer should not be expired already.
But if so, we may need to figure why and what should we do to deal with this.
In this case, we see the system is changed forward and so that the expired time
in timer is expired.
In other case, we may found that if a system is too busy and context switch
quickly, this may also happened.

In my patch (id=339),  when calculating the next expiration and found that the
oldest one has been expired, I give it a second try.  That is, pretending this
timer is registering at this moment, and setting timer with the interval that
user set.

The first thing we should figure out is "what should we do when timer is 
expired?"
In my opinion, this is an abnormal condition, and we should try to set another
alarm to call those expired timer.
In the case of changing system time, gsmd should wait for a moment and so that
reset the timer is suit for this case.
However, in the case of system too busy, it may need to send SIGALRM 
immediately.

In order to make gsmd robust, these two conditions should be considered well.
In that patch id=339, there is a weakness:
If timer A registered at 00:00 and interval is 15 sec, and timer B registered at
00:13 and interval is 3 sec.
If the system time changed at 00:14 from 00:14 to 00:20, both timer A and B are
expired.
In this patch, A will be selected and another 15 sec will be waited. That is B
will wait for extra 13 sec.

Therefore, I have to reject my patch (id=339)

A better way to handle this abnormal condition is to find out the latest
registering time, and recalculate all the expired timer. Pretending the current
time is the latest registering time, and recalculate all the expiration of
expired timer.




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





------- Additional Comments From [EMAIL PROTECTED]  2007-10-10 01:59 -------
Created an attachment (id=342)
 --> 
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=342&action=view)
give expired timer a second chance with recalculate expiration

recalculate the expiration with the latest registering time



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





------- Additional Comments From [EMAIL PROTECTED]  2007-10-10 02:02 -------
(From update of attachment 342)
This is a patch for BUG 693. 
Sorry for the miss post. 
Please remove 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=693





------- Additional Comments From [EMAIL PROTECTED]  2007-10-10 02:05 -------
Created an attachment (id=343)
 --> 
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=343&action=view)
give expired timer a second chance with recalculate expiration

recalculate the expiration of expired timers, using the latest registering time
as the current time.



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

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|[email protected]   |[EMAIL PROTECTED]





------- 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 ---
[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=41
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=69
  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=129
  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=276
  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=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=661
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=675
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=696
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=714
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=727
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=742
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=800
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=808
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=835
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=846
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=847
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=862
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=865
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=870
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=881
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=882
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=888



--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog

Reply via email to