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. Re: Openmoko Bug #1980: [Location] the tag list is jumping
      too       serious when you scroll it (Openmoko Public Trac)
   2. Re: Openmoko Bug #1716: [Package] add .edj
      decompiler/compiler as a  package (Openmoko Public Trac)
   3. Re: Openmoko Bug #1908: [python bindings] can't start
      settings on       the testing image (Openmoko Public Trac)
   4. Openmoko Bug #1984: [Qt-Contact] edit contact (from SIM card)
      screen will overlop other application (Openmoko Public Trac)
   5. Openmoko Bug #1985: no auto-suspend after some time
      (Openmoko Public Trac)
   6. Openmoko Bug #1986: AUX LED blicks too early at power on
      (Openmoko Public Trac)
   7. Openmoko Bug #1988: addressbook mangles UTF-8 characters when
      importing version 3 vCards (Openmoko Public Trac)
--- Begin Message ---
#1980: [Location] the tag list is jumping too serious when you scroll it
---------------------------+------------------------------------------------
    Reporter:  wendy_hung  |        Owner:  jeremy  
        Type:  defect      |       Status:  new     
    Priority:  normal      |    Milestone:  Om2008.9
   Component:  Locations   |      Version:  Om2008.8
    Severity:  normal      |   Resolution:          
    Keywords:              |    Blockedby:          
Reproducible:  always      |     Blocking:          
---------------------------+------------------------------------------------

Comment(by jeremy):

 One way to solve this is to increase the damper value.
 but I think the key point that makes you confused and not easily to click
 is it will bounce.

 Will,
   Should we disable the bounce function?

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/1980#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac

--- End Message ---
--- Begin Message ---
#1716: [Package] add .edj decompiler/compiler as a package
-----------------------------+----------------------------------------------
    Reporter:  will          |        Owner:  julian    
        Type:  task          |       Status:  in_testing
    Priority:  high          |    Milestone:            
   Component:  Distro        |      Version:            
    Severity:  critical      |   Resolution:            
    Keywords:  edje package  |    Blockedby:            
Reproducible:                |     Blocking:            
-----------------------------+----------------------------------------------

Comment(by marek):

 I checked it today on the testing image and it works! Thanks

 Also, I tried to decompile the exposure.edj but it fails:

 edje_decc exposure.edj
 Output Image: exposure/back_arrow.png
 ERROR: cannot write file exposure/back_arrow.png. Perhaps missing JPEG or
 PNG saver modules for Evas.

 Can you have a look into that ?

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/1716#comment:7>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac

--- End Message ---
--- Begin Message ---
#1908: [python bindings] can't start settings on the testing image
-----------------------+----------------------------------------------------
    Reporter:  marek   |        Owner:  julian_chu
        Type:  defect  |       Status:  closed    
    Priority:  normal  |    Milestone:            
   Component:  Distro  |      Version:            
    Severity:  normal  |   Resolution:  fixed     
    Keywords:          |    Blockedby:            
Reproducible:  always  |     Blocking:            
-----------------------+----------------------------------------------------
Changes (by marek):

  * status:  new => closed
  * resolution:  => fixed


Comment:

 Yes, it does. Thanks

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/1908#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac

--- End Message ---
--- Begin Message ---
#1984: [Qt-Contact] edit contact (from SIM card) screen will overlop other
application
------------------------+---------------------------------------------------
 Reporter:  wendy_hung  |          Owner:  zecke   
     Type:  defect      |         Status:  new     
 Priority:  highest     |      Milestone:  Om2008.9
Component:  Qtopia      |        Version:  Om2008.8
 Severity:  major       |       Keywords:          
Blockedby:              |   Reproducible:  always  
 Blocking:              |  
------------------------+---------------------------------------------------
 Summary:
 edit contact (from SIM card) screen will overlop other application

 kernel:20080903-asu.stable-uImage.bin
 root file system:20080910-asu.stable-rootfs.jffs2

 Steps+current results:
 1) launch Contact and choose one contact from SIM card
 2) press option to show the detail of contact than edit it
 3) you'll see the edit screen overlop original application
 4) go to other app and choose "Edit SIM Contact" in illume bar
 5) please see the attach photos

 Expected:
 don't have this kind of overlop screen

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/1984>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac

--- End Message ---
--- Begin Message ---
#1985: no auto-suspend after some time
----------------------+-----------------------------------------------------
 Reporter:  h.koenig  |          Owner:  openmoko-devel
     Type:  defect    |         Status:  new           
 Priority:  normal    |      Milestone:                
Component:  unknown   |        Version:                
 Severity:  normal    |       Keywords:                
Blockedby:            |   Reproducible:                
 Blocking:            |  
----------------------+-----------------------------------------------------
 Om 20008.8 + updates:  since the last 1 or 2 updates (maybe up to a week
 now ?!) I notice that auto-suspend doesn't work anymore for me.

 I've set "blank screen" and "suspend after blank" both to 60 seconds but
 after a while either only screen blank works, or even neither screen
 blanker nor suspend work. (it's ok just after fresh boot).

 right now when pressing the power button, only screen blanker gets
 activated, no suspend -- but "apm -s" from ssh login still suspends,
 so it's not the "device or resource busy" issue...


 3 ideas what might trigger this problems:

 a) it's triggered by my atd job which rus every 10 minutes to log battery
 data.  if that atd job resumes the suspended FR, then there will be no new
 auto-blank or auto-suspennd anymore.

 b) it's triggered by pressing the power button to suspend

 c) the phone is kept alive because of lots of GSM communication I can see
 in "logread" output:

    logread | grep simyo

 Sep 10 12:43:36 om-gta02 user.notice root: AtChat :  F : "+COPS:
 0,0,"simyo""
 Sep 10 12:43:37 om-gta02 user.notice root: AtChat :  F : "+COPS:
 0,0,"simyo""
 Sep 10 12:45:09 om-gta02 user.notice root: AtChat :  F : "+COPS:
 0,0,"simyo""
 Sep 10 12:45:09 om-gta02 user.notice root: AtChat :  F : "+COPS:
 0,0,"simyo""
 Sep 10 12:46:10 om-gta02 user.notice root: AtChat :  F : "+COPS:
 0,0,"simyo""
 Sep 10 12:46:10 om-gta02 user.notice root: AtChat :  F : "+COPS:
 0,0,"simyo""
 Sep 10 12:46:50 om-gta02 user.notice root: AtChat :  F : "+COPS:
 0,0,"simyo""
 Sep 10 12:46:51 om-gta02 user.notice root: AtChat :  F : "+COPS:
 0,0,"simyo""
 Sep 10 12:46:51 om-gta02 user.notice root: AtChat :  F : "+COPS:
 0,0,"simyo""
 Sep 10 12:47:55 om-gta02 user.notice root: AtChat :  F : "+COPS:
 0,0,"simyo""
 Sep 10 12:47:56 om-gta02 user.notice root: AtChat :  F : "+COPS:
 0,0,"simyo""
 Sep 10 12:48:38 om-gta02 user.notice root: AtChat :  F : "+COPS:
 0,0,"simyo""
 Sep 10 12:48:38 om-gta02 user.notice root: AtChat :  F : "+COPS:
 0,0,"simyo""
 Sep 10 12:49:27 om-gta02 user.notice root: AtChat :  F : "+COPS:
 0,0,"simyo""
 Sep 10 12:49:42 om-gta02 user.notice root: AtChat :  F : "+COPS:
 0,0,"simyo""
 Sep 10 12:51:38 om-gta02 user.notice root: AtChat :  F : "+COPS:
 0,0,"simyo""
 Sep 10 12:51:38 om-gta02 user.notice root: AtChat :  F : "+COPS:
 0,0,"simyo""
 Sep 10 12:52:20 om-gta02 user.notice root: AtChat :  F : "+COPS:
 0,0,"simyo""
 Sep 10 12:52:20 om-gta02 user.notice root: AtChat :  F : "+COPS:
 0,0,"simyo""
 Sep 10 12:52:20 om-gta02 user.notice root: AtChat :  F : "+COPS:
 0,0,"simyo""
 Sep 10 12:53:01 om-gta02 user.notice root: AtChat :  F : "+COPS:
 0,0,"simyo""
 Sep 10 12:53:02 om-gta02 user.notice root: AtChat :  F : "+COPS:
 0,0,"simyo""
 Sep 10 12:53:49 om-gta02 user.notice root: AtChat :  F : "+COPS:
 0,0,"simyo""
 Sep 10 12:53:50 om-gta02 user.notice root: AtChat :  F : "+COPS:
 0,0,"simyo""
 Sep 10 12:54:30 om-gta02 user.notice root: AtChat :  F : "+COPS:
 0,0,"simyo""
 Sep 10 12:54:30 om-gta02 user.notice root: AtChat :  F : "+COPS:
 0,0,"simyo""
 Sep 10 12:55:20 om-gta02 user.notice root: AtChat :  F : "+COPS:
 0,0,"simyo""
 Sep 10 12:55:45 om-gta02 user.notice root: AtChat :  F : "+COPS:
 0,0,"simyo""


 [EMAIL PROTECTED]:~# opkg list_installed kernel
 kernel - 2:2.6.24+git75969+a1e97c611253511ffc2d8c45e3e6d6894fa03fa3-r1.01
 -


 which other information do you need ?

 what can I trace to figure out
 - why suspend doesn't work anymore (what happens when pressing power
 button)
 - what triggers that problem...



 thanks for pointers!

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/1985>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac

--- End Message ---
--- Begin Message ---
#1986: AUX LED blicks too early at power on
----------------------+-----------------------------------------------------
 Reporter:  h.koenig  |          Owner:  openmoko-devel
     Type:  defect    |         Status:  new           
 Priority:  normal    |      Milestone:                
Component:  unknown   |        Version:                
 Severity:  normal    |       Keywords:                
Blockedby:            |   Reproducible:                
 Blocking:            |  
----------------------+-----------------------------------------------------
 when booting the FR with 8-second-pwr-button the AUX LED flashes too
 early, because this often triggers me to release the pwr button ("hey,
 it's alive") which is just too early for startup -- the FR won't start and
 I have to press pwr for another 8 seconds (and close my eyes;)

 it would be nice if the LED only flashes _after_ the pwr up signal got
 accepted and the FR really starts up...

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/1986>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac

--- End Message ---
--- Begin Message ---
#1988: addressbook mangles UTF-8 characters when importing version 3 vCards
---------------------+------------------------------------------------------
 Reporter:  kavol    |          Owner:  zecke       
     Type:  defect   |         Status:  new         
 Priority:  normal   |      Milestone:  Om2008.9    
Component:  Qtopia   |        Version:  Om2008.9-dev
 Severity:  blocker  |       Keywords:              
Blockedby:           |   Reproducible:  always      
 Blocking:           |  
---------------------+------------------------------------------------------
 Hi.

 This looks like a pure Qtopia bug, but reading
 http://lists.openmoko.org/pipermail/openmoko-devel/2008-June/003034.html
 it looks like I should report it here (and then it potentially goes
 upstream ...)

 I've exported my contacts from kaddressbook using vCard 3.0 into a single
 file. I've copied the file onto Freerunner and run "DISPLAY=:0 addressbook
 addressbook.vcf" from the console.

 The contacts got imported, however the characters outside the 7bit ASCII
 range were wrong. The single byte characters were swapped with others, the
 two byte characters were replaced with two (wrong) characters.

 The vcf file was encoded in UTF-8, and as far as I understand the
 corresponding RFCs, this should be the default unless specified otherwise
 (which is done by specifying Content-Type, which is not available inside
 of the file ...), so that I consider this behaviour a bug.

 Using vCard 2.1, where the encoding is stated explicitly for each non-
 ASCII record, the characters are imported properly.

 I am using packages from testing:
 Package: qtopia-phone-x11-addressbook
 Version: 1:4.3.2+gitr3+906a00fdcb89fdcc8252f84a76625eb42c8fe302-r41

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/1988>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac

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

Reply via email to