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 #1525: Exposure Crashes (or at least its
      inaccessible) (Openmoko Public Trac)
   2. Re: Openmoko Bug #1508: no signal area still can send message
      and show Alert message ?sending : message? (Openmoko Public Trac)
   3. Re: Openmoko Bug #1508: no signal area still can send message
      and show Alert message ?sending : message? (Openmoko Public Trac)
   4. Re: Openmoko Bug #1525: Exposure Crashes (or at least its
      inaccessible) (Openmoko Public Trac)
   5. Re: Openmoko Bug #1524: unable to uninstall kobodeluxe
      package   through assassin (Openmoko Public Trac)
   6. Re: Openmoko Bug #1454: during call activity,     if third Party
      call disconnecting before answer ,        the screen still display
      incoming call menu (Openmoko Public Trac)
   7. Re: Openmoko Bug #1529: The screen shows one more same number
      short     second then disappear (Openmoko Public Trac)
   8. Re: Openmoko Bug #1464: after changed set time ,  clock and
      illume top bar time still does not changed as set time
      (Openmoko Public Trac)
   9. Re: Openmoko Bug #1464: after changed set time ,  clock and
      illume top bar time still does not changed as set time
      (Openmoko Public Trac)
--- Begin Message ---
#1525: Exposure Crashes (or at least its inaccessible)
----------------------+-----------------------------------------------------
 Reporter:  will      |        Owner:  [EMAIL PROTECTED]
     Type:  defect    |       Status:  assigned          
 Priority:  normal    |    Milestone:  ASU               
Component:  Exposure  |      Version:                    
 Severity:  normal    |   Resolution:                    
 Keywords:            |  
----------------------+-----------------------------------------------------
Changes (by raster):

  * owner:  [EMAIL PROTECTED] => [EMAIL PROTECTED]
  * status:  new => assigned
  * component:  E - Illume => Exposure


Comment:

 this is exposure's window hanging around but exposure not flushing its x
 buffers or running the main loop to handle redraws. (i can see similar
 things right now in front of me). it's not illume here (never run exposure
 and everything else behaves fine).

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

--- End Message ---
--- Begin Message ---
#1508: no signal area still can send message and show Alert message “sending :
message”
------------------------+---------------------------------------------------
 Reporter:  regina_kim  |        Owner:  [EMAIL PROTECTED]
     Type:  defect      |       Status:  assigned          
 Priority:  normal      |    Milestone:  ASU               
Component:  E - Illume  |      Version:                    
 Severity:  normal      |   Resolution:                    
 Keywords:              |  
------------------------+---------------------------------------------------
Changes (by raster):

  * owner:  [EMAIL PROTECTED] => [EMAIL PROTECTED]


Comment:

 remember it may just be rounding down to "1 bar" 1 bar == minimal signal
 it will show (the 1 bar with the little asterisk on top of it). as we have
 only 4 bars, 4 == 75->100, 3 == 50-75, 2 == 25-50, 1 == 0-25, so you could
 have 10% signal and its enough to send messages. i am unsure this is a
 bug? at least not in illume. qpe bug if anything. did the sms actually
 succeed in being sent?

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/1508#comment:3>
docs.openmoko.org <https://docs.openmoko.org/trac>
openmoko trac

--- End Message ---
--- Begin Message ---
#1508: no signal area still can send message and show Alert message “sending :
message”
------------------------+---------------------------------------------------
 Reporter:  regina_kim  |        Owner:  [EMAIL PROTECTED]
     Type:  defect      |       Status:  assigned          
 Priority:  normal      |    Milestone:  ASU               
Component:  Qtopia      |      Version:                    
 Severity:  normal      |   Resolution:                    
 Keywords:              |  
------------------------+---------------------------------------------------
Changes (by raster):

  * component:  E - Illume => Qtopia


-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/1508#comment:4>
docs.openmoko.org <https://docs.openmoko.org/trac>
openmoko trac

--- End Message ---
--- Begin Message ---
#1525: Exposure Crashes (or at least its inaccessible)
------------------------+---------------------------------------------------
 Reporter:  will        |        Owner:  [EMAIL PROTECTED]
     Type:  defect      |       Status:  assigned           
 Priority:  normal      |    Milestone:  ASU                
Component:  E - Illume  |      Version:                     
 Severity:  normal      |   Resolution:                     
 Keywords:              |  
------------------------+---------------------------------------------------
Changes (by raster):

  * owner:  [EMAIL PROTECTED] => [EMAIL PROTECTED]
  * component:  Exposure => E - Illume


Comment:

 actually no - i found it's a "ghost window" bug. that damn ghost window
 bug rears its head again, but this time in a nice repeatable way.

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

--- End Message ---
--- Begin Message ---
#1524: unable to uninstall kobodeluxe package through assassin
------------------------+---------------------------------------------------
 Reporter:  wendy_hung  |        Owner:  [EMAIL PROTECTED]
     Type:  defect      |       Status:  closed           
 Priority:  normal      |    Milestone:  ASU              
Component:  Assassin    |      Version:                   
 Severity:  normal      |   Resolution:  worksforme       
 Keywords:              |  
------------------------+---------------------------------------------------
Changes (by raster):

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


Comment:

 I can't reproduce (i'm not using assassin but opkg directly to test -
 assassin takes a lot more setup), but kobodeluxue icon disappears when
 uninstalled, and is there when installed. the icon is blank - the .desktop
 file doesn't provide an icon in a standard xdg search path, but it
 works... for me - on my desktop and on the freerunner. please re-open if
 you can still reproduce.

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

--- End Message ---
--- Begin Message ---
#1454: during call activity, if third Party call disconnecting before answer 
,the
screen still display incoming call menu
------------------------+---------------------------------------------------
 Reporter:  regina_kim  |        Owner:  [EMAIL PROTECTED]
     Type:  defect      |       Status:  in_testing        
 Priority:  highest     |    Milestone:  ASU               
Component:  Qtopia      |      Version:                    
 Severity:  critical    |   Resolution:                    
 Keywords:              |  
------------------------+---------------------------------------------------
Changes (by zecke):

  * status:  new => in_testing


Comment:

 Could you please check if that is still the case?

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/1454#comment:3>
docs.openmoko.org <https://docs.openmoko.org/trac>
openmoko trac

--- End Message ---
--- Begin Message ---
#1529: The screen shows one more same number short second then disappear
------------------------+---------------------------------------------------
 Reporter:  regina_kim  |        Owner:  [EMAIL PROTECTED]
     Type:  defect      |       Status:  in_testing        
 Priority:  high        |    Milestone:  ASU               
Component:  Qtopia      |      Version:                    
 Severity:  major       |   Resolution:                    
 Keywords:              |  
------------------------+---------------------------------------------------
Changes (by zecke):

  * status:  new => in_testing


Comment:

 Could you please elaborate on this? Do we talk about the callscreen? Is it
 showing the same number twice? Is it showing an old number?

 Anyway I have made important changes to the callhandling so please retry.
 It should be in any recent image.

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

--- End Message ---
--- Begin Message ---
#1464: after changed set time , clock and illume top bar time still does not
changed as set time
------------------------+---------------------------------------------------
 Reporter:  regina_kim  |        Owner:  [EMAIL PROTECTED]
     Type:  defect      |       Status:  in_testing        
 Priority:  highest     |    Milestone:  ASU               
Component:  Qtopia      |      Version:                    
 Severity:  critical    |   Resolution:                    
 Keywords:              |  
------------------------+---------------------------------------------------
Changes (by zecke):

  * status:  new => in_testing


Comment:

 Okay two things:
 1) File a separate bug report for illume 12/24 hour setting not being
 synchronized and put a PM as keyword there. will has to decide what to
 do.. remove this option from Qtopia or make illume honor it?

 2.) Can you please verify that setting timezone + time is working (with up
 to 60 seconds delay?)

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/1464#comment:5>
docs.openmoko.org <https://docs.openmoko.org/trac>
openmoko trac

--- End Message ---
--- Begin Message ---
#1464: after changed set time , clock and illume top bar time still does not
changed as set time
------------------------+---------------------------------------------------
 Reporter:  regina_kim  |        Owner:  [EMAIL PROTECTED]
     Type:  defect      |       Status:  in_testing        
 Priority:  highest     |    Milestone:  ASU               
Component:  Qtopia      |      Version:                    
 Severity:  critical    |   Resolution:                    
 Keywords:              |  
------------------------+---------------------------------------------------

Comment(by will):

 Is there an issue with 12/24 hour settings?
 I set my time today at 18:36 and had no problems.

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/1464#comment:6>
docs.openmoko.org <https://docs.openmoko.org/trac>
openmoko trac

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

Reply via email to