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 #1755: openmoko-messages segfaults
      (Openmoko Public Trac)
   2. Re: Openmoko Bug #1756: Qtopia GUI (qpe) broken after 'opkg
      upgrade' (Openmoko Public Trac)
   3. Re: Openmoko Bug #1756: Qtopia GUI (qpe) broken after 'opkg
      upgrade' (Openmoko Public Trac)
   4. Re: Openmoko Bug #1756: Qtopia GUI (qpe) broken after 'opkg
      upgrade' (Openmoko Public Trac)
   5. Openmoko Bug #1757: +CMS ERROR: 321 in response to AT+CMGL=4
      (SMS      errors?) (Openmoko Public Trac)
   6. Re: Openmoko Bug #1757: +CMS ERROR: 321 in response to
      AT+CMGL=4 (SMS errors?) (Openmoko Public Trac)
   7. Re: Openmoko Bug #1757: +CMS ERROR: 321 in response to
      AT+CMGL=4 (SMS errors?) (Openmoko Public Trac)
   8. Re: Openmoko Bug #1697: [Battery] No Alert message when
      battery is low (Openmoko Public Trac)
--- Begin Message ---
#1755: openmoko-messages segfaults
---------------------+------------------------------------------------------
 Reporter:  el       |        Owner:  openmoko-devel
     Type:  defect   |       Status:  assigned      
 Priority:  normal   |    Milestone:  OM-2007.2     
Component:  unknown  |      Version:                
 Severity:  normal   |   Resolution:                
 Keywords:           |     Blocking:                
Blockedby:           |  
---------------------+------------------------------------------------------
Changes (by zecke):

  * owner:  julian_chu => openmoko-devel
  * status:  new => assigned
  * version:  GTA02v6 =>
  * component:  Distro => unknown
  * milestone:  => OM-2007.2


Comment:

 Sorry, I have to move this further. It sounds like this is openmoko-
 messages from OM2007.2, so I'm setting the appropriate milestone.

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

--- End Message ---
--- Begin Message ---
#1756: Qtopia GUI (qpe) broken after 'opkg upgrade'
-------------------------+--------------------------------------------------
 Reporter:  aeneby       |        Owner:  zecke  
     Type:  defect       |       Status:  new    
 Priority:  high         |    Milestone:         
Component:  Qtopia       |      Version:  GTA02v5
 Severity:  major        |   Resolution:         
 Keywords:  Qtopia, qpe  |     Blocking:         
Blockedby:               |  
-------------------------+--------------------------------------------------

Comment(by zecke):

 Which image (URL) did you flash? Which feed do you use for upgrades (URL)?
 I don't think that we as in Openmoko distribute Qtopia images or provide a
 feed for them? So it might be best to take this on with the providers of
 the feed?

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

--- End Message ---
--- Begin Message ---
#1756: Qtopia GUI (qpe) broken after 'opkg upgrade'
-------------------------+--------------------------------------------------
 Reporter:  aeneby       |        Owner:  zecke  
     Type:  defect       |       Status:  new    
 Priority:  high         |    Milestone:         
Component:  Qtopia       |      Version:  GTA02v5
 Severity:  major        |   Resolution:         
 Keywords:  Qtopia, qpe  |     Blocking:         
Blockedby:               |  
-------------------------+--------------------------------------------------

Comment(by aeneby):

 The image is the one available from
 [http://www.qtopia.net/modules/mydownloads/viewcat.php?cid=6] (bottom of
 the page) which contains the GTA02 kernel and rootfs images. The feeds
 were the standard [http://buildhost.openmoko.org/daily-feed/] sources.

 I have also alerted Trolltech to this issue and you're right, strictly it
 is a Trolltech issue - however the reason I posted here as well is because
 it's something that has changed in the past few Openmoko builds which is
 causing this error. I could previously run 'opkg upgrade' on Qtopia with
 no problems and I thought someone might know what had changed to cause
 this.

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

--- End Message ---
--- Begin Message ---
#1756: Qtopia GUI (qpe) broken after 'opkg upgrade'
-------------------------+--------------------------------------------------
 Reporter:  aeneby       |        Owner:  openmoko-devel
     Type:  defect       |       Status:  assigned      
 Priority:  high         |    Milestone:                
Component:  Qtopia       |      Version:  GTA02v5       
 Severity:  major        |   Resolution:                
 Keywords:  Qtopia, qpe  |     Blocking:                
Blockedby:               |  
-------------------------+--------------------------------------------------
Changes (by zecke):

  * owner:  zecke => openmoko-devel
  * status:  new => assigned


Comment:

 I just wonder how Openmoko can help. I had a look at the feed and can't
 find anything that would explain a partial upgrade of Qtopia base
 libraries resulting in the breakage you see. I think the only bet is to
 take it on with Nokia/Trolltech.

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

--- End Message ---
--- Begin Message ---
#1757: +CMS ERROR: 321 in response to AT+CMGL=4 (SMS errors?)
---------------------+------------------------------------------------------
 Reporter:  Mercury  |       Owner:  openmoko-devel
     Type:  defect   |      Status:  new           
 Priority:  normal   |   Milestone:  ASU           
Component:  unknown  |     Version:  unspecified   
 Severity:  normal   |    Keywords:                
 Blocking:           |   Blockedby:                
---------------------+------------------------------------------------------
 I don't appear to be able to receive SMS messages, and I'm getting strange
 messages in the log.

 ----
 Aug  7 18:54:30 lisa user.notice root: AtChat :  T : "AT+CMGL=4"
 Aug  7 18:54:30 lisa user.notice root: AtChat :  F : "+CMS ERROR: 321"
 Aug  7 18:54:30 lisa user.notice root: AtChat :  T : "AT+CMGL=4"
 Aug  7 18:54:30 lisa user.notice root: AtChat :  F : "+CMS ERROR: 321"
 Aug  7 18:54:31 lisa user.notice root: AtChat :  T : "AT+CMGL=4"
 Aug  7 18:54:31 lisa user.notice root: AtChat :  F : "+CMS ERROR: 321"
 Aug  7 18:54:31 lisa user.notice root: AtChat :  T : "AT+CMGL=4"
 Aug  7 18:54:31 lisa user.notice root: AtChat :  F : "+CMS ERROR: 321"
 Aug  7 18:54:32 lisa user.notice root: AtChat :  T : "AT+CMGL=4"
 Aug  7 18:54:32 lisa user.notice root: AtChat :  F : "+CMS ERROR: 321"
 Aug  7 18:54:32 lisa user.notice root: AtChat :  T : "AT+CMGL=4"
 Aug  7 18:54:32 lisa user.notice root: AtChat :  F : "+CMS ERROR: 321"
 Aug  7 18:54:33 lisa user.notice root: AtChat :  T : "AT+CMGL=4"
 Aug  7 18:54:33 lisa user.notice root: AtChat :  F : "+CMS ERROR: 321"
 Aug  7 18:54:33 lisa user.notice root: AtChat :  T : "AT+CMGL=4"
 Aug  7 18:54:33 lisa user.notice root: AtChat :  F : "+CMS ERROR: 321"
 Aug  7 18:54:34 lisa user.notice root: AtChat :  T : "AT+CMGL=4"
 Aug  7 18:54:34 lisa user.notice root: AtChat :  F : "+CMS ERROR: 321"
 Aug  7 18:54:34 lisa user.notice root: AtChat :  T : "AT+CMGL=4"
 Aug  7 18:54:34 lisa user.notice root: AtChat :  F : "+CMS ERROR: 321"
 Aug  7 18:54:35 lisa user.notice root: AtChat :  T : "AT+CMGL=4"
 Aug  7 18:54:35 lisa user.notice root: AtChat :  F : "+CMS ERROR: 321"
 Aug  7 18:54:35 lisa user.notice root: AtChat :  T : "AT+CMGL=4"
 Aug  7 18:54:35 lisa user.notice root: AtChat :  F : "+CMS ERROR: 321"
 Aug  7 18:54:36 lisa user.notice root: AtChat :  T : "AT+CMGL=4"
 Aug  7 18:54:36 lisa user.notice root: AtChat :  F : "+CMS ERROR: 321"
 ----

 Some things I've done recently.  I got my first 3 SMS messages.  I deleted
 2 of them (Because they were all the same), and then I sent two more to
 myself, and neither showed up, and now I see that error.

 Maybe it's trying to get message #4 even though it's message #2 now?
 (Wild guess)

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

--- End Message ---
--- Begin Message ---
#1757: +CMS ERROR: 321 in response to AT+CMGL=4 (SMS errors?)
---------------------+------------------------------------------------------
 Reporter:  Mercury  |        Owner:  openmoko-devel
     Type:  defect   |       Status:  new           
 Priority:  normal   |    Milestone:  ASU           
Component:  unknown  |      Version:  unspecified   
 Severity:  normal   |   Resolution:                
 Keywords:           |     Blocking:                
Blockedby:           |  
---------------------+------------------------------------------------------

Comment(by balrog):

 Nope, it's trying to list all messages (+CMGL=4 in PDU mode is same as
 +CMGL="ALL" in text mode).
 Error 321 is "Invalid Memory Index", which means that there are no
 messages in the inbox.  (Fully 3GPP compliant modems would just list zero
 messages and print OK but the TI Calypso is known to be special and give
 INVALID_MEMORY_INDEX).

 There must be another issue with receiving messages that you're seeing.

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

--- End Message ---
--- Begin Message ---
#1757: +CMS ERROR: 321 in response to AT+CMGL=4 (SMS errors?)
---------------------+------------------------------------------------------
 Reporter:  Mercury  |        Owner:  openmoko-devel
     Type:  defect   |       Status:  closed        
 Priority:  normal   |    Milestone:  ASU           
Component:  unknown  |      Version:  unspecified   
 Severity:  normal   |   Resolution:  invalid       
 Keywords:           |     Blocking:                
Blockedby:           |  
---------------------+------------------------------------------------------
Changes (by Mercury):

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


Comment:

 Oh!  Okay great then!  My bad.  I'll set this to closed for now then.
 Thanks.

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

--- End Message ---
--- Begin Message ---
#1697: [Battery] No Alert message when battery is low
-------------------------+--------------------------------------------------
 Reporter:  regina_kim   |        Owner:  raster  
     Type:  enhancement  |       Status:  assigned
 Priority:  high         |    Milestone:  ASU     
Component:  E - Illume   |      Version:          
 Severity:  minor        |   Resolution:          
 Keywords:  pm           |     Blocking:          
Blockedby:               |  
-------------------------+--------------------------------------------------
Changes (by raster):

  * type:  defect => enhancement
  * severity:  critical => minor


Comment:

 not for asu... :) e's battery meter can already do this - just its not
 configured to do it, nor is there any way to access the config to do this
 (as all means of accessing e's config have been removed by design from
 asu), and e's dialogs are not themed to match asu - still inherit default
 e theme... :)

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/1697#comment:7>
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