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. Openmoko Bug #1735: [u-boot] get different screen.
      (Openmoko Public Trac)
   2. Re: Openmoko Bug #1735: [u-boot] get different screen.
      (Openmoko Public Trac)
   3. Re: Openmoko Bug #1730: SELinux Kernel Support
      (Openmoko Public Trac)
   4. Openmoko Bug #1736: [Boot screen] it goes into sleep and
      never wake        up if not touch during booting (Openmoko Public Trac)
   5. Re: Openmoko Bug #1730: SELinux Kernel Support
      (Openmoko Public Trac)
   6. Openmoko Bug #1737: [e-illume icon] it shows no signal icon
      and       signal strength is low too often. (Openmoko Public Trac)
   7. Openmoko Bug #1738: [Alert message in home screen] Crashed
      Alert     message with vibration (Openmoko Public Trac)
   8. Openmoko Bug #1739: [Exposure] Sometimes Profile will show up
      "unknow" message (Openmoko Public Trac)
   9. Openmoko Bug #1740: [Exposure] Change "Date/Time" as "Clock"
      (Openmoko Public Trac)
--- Begin Message ---
#1735: [u-boot] get different screen.
------------------------+---------------------------------------------------
 Reporter:  regina_kim  |       Owner:  [EMAIL PROTECTED]
     Type:  defect      |      Status:  new                
 Priority:  normal      |   Milestone:  ASU                
Component:  unknown     |     Version:  GTA02v5            
 Severity:  normal      |    Keywords:  boot screen        
 Blocking:              |   Blockedby:                     
------------------------+---------------------------------------------------
 kernel : 20080723-asu.stable-uImage.bin
 rootfs : 20080804-asu.stable-rootfs.jffs2

 step + summary : [u-boot] get different screen.
 it shows boot menu when press power button and the other one direct
 booting up after flash new image.

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

--- End Message ---
--- Begin Message ---
#1735: [u-boot] get different screen.
-----------------------------+----------------------------------------------
 Reporter:  regina_kim       |        Owner:  [EMAIL PROTECTED]
     Type:  defect           |       Status:  new                
 Priority:  normal           |    Milestone:  ASU                
Component:  System Software  |      Version:  GTA02v5            
 Severity:  normal           |   Resolution:                     
 Keywords:  boot screen      |     Blocking:                     
Blockedby:                   |  
-----------------------------+----------------------------------------------
Changes (by regina_kim):

  * component:  unknown => System Software


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

--- End Message ---
--- Begin Message ---
#1730: SELinux Kernel Support
-----------------------------+----------------------------------------------
 Reporter:  willis           |        Owner:  openmoko-kernel
     Type:  enhancement      |       Status:  new            
 Priority:  normal           |    Milestone:                 
Component:  System Software  |      Version:                 
 Severity:  normal           |   Resolution:                 
 Keywords:  selinux, kernel  |     Blocking:                 
Blockedby:                   |  
-----------------------------+----------------------------------------------

Comment(by alphaone):

 We are currently investigating how to secure the dbus communication. See
 the SELinux section in http://linux.die.net/man/1/dbus-daemon-1 for more
 details. I think SELinux support will become default once that is
 implemented correctly. After all you don't want a browser exploit to send
 masses of SMS.

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

--- End Message ---
--- Begin Message ---
#1736: [Boot screen] it goes into sleep and never wake up if not touch during
booting
-----------------------------+----------------------------------------------
 Reporter:  regina_kim       |       Owner:  [EMAIL PROTECTED]
     Type:  defect           |      Status:  new              
 Priority:  high             |   Milestone:  ASU              
Component:  System Software  |     Version:  GTA02v5          
 Severity:  normal           |    Keywords:                   
 Blocking:                   |   Blockedby:                   
-----------------------------+----------------------------------------------
 kernel : 20080723-asu.stable-uImage.bin
 rootfs : 20080804-asu.stable-rootfs.jffs2

 step + summary : sometimes it goes into sleep on boot progress screen
 after press power button then it never wake up if not press power.

 reproducible: 1out of 10 tries.

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

--- End Message ---
--- Begin Message ---
#1730: SELinux Kernel Support
-----------------------------+----------------------------------------------
 Reporter:  willis           |        Owner:  openmoko-kernel
     Type:  enhancement      |       Status:  new            
 Priority:  normal           |    Milestone:                 
Component:  System Software  |      Version:                 
 Severity:  normal           |   Resolution:                 
 Keywords:  selinux, kernel  |     Blocking:                 
Blockedby:                   |  
-----------------------------+----------------------------------------------

Comment(by andy):

 It sounds like something that's useful, but shouldn't we first make some
 users and groups for everything?  I'm pretty sure the two layers of
 security together will work better than just depending on one.

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

--- End Message ---
--- Begin Message ---
#1737: [e-illume icon] it shows no signal icon and signal strength is low too
often.
------------------------+---------------------------------------------------
 Reporter:  regina_kim  |       Owner:  Raster        
     Type:  defect      |      Status:  new           
 Priority:  high        |   Milestone:  ASU           
Component:  E - Illume  |     Version:  GTA02v5       
 Severity:  critical    |    Keywords:  no signal icon
 Blocking:              |   Blockedby:                
------------------------+---------------------------------------------------
 kernel : 20080723-asu.stable-uImage.bin
 rootfs : 20080804-asu.stable-rootfs.jffs2

 step + summary : it shows no signal icon and signal strength is low too
 often.
 so sometimes can not receive call and can not make a call as well.
 refer picture

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

--- End Message ---
--- Begin Message ---
#1738: [Alert message in home screen] Crashed Alert message with vibration
------------------------+---------------------------------------------------
 Reporter:  regina_kim  |       Owner:  [EMAIL PROTECTED]
     Type:  defect      |      Status:  new               
 Priority:  normal      |   Milestone:  ASU               
Component:  Qtopia      |     Version:  GTA02v5           
 Severity:  normal      |    Keywords:                    
 Blocking:              |   Blockedby:                    
------------------------+---------------------------------------------------
 kernel : 20080723-asu.stable-uImage.bin
 rootfs : 20080804-asu.stable-rootfs.jffs2

 step + summary :it shows Alert message " The firmware of modem appears to
 have crashed.No Further interaction with the modem will be possible.please
 restart the device"with vibration when press power button to avoid suspend
 after flash new image.then vibration will keep working till press "OK"
 softmenu.

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

--- End Message ---
--- Begin Message ---
#1739: [Exposure] Sometimes Profile will show up "unknow" message
------------------------+---------------------------------------------------
 Reporter:  wendy_hung  |       Owner:  Marek
     Type:  defect      |      Status:  new  
 Priority:  normal      |   Milestone:  ASU  
Component:  Exposure    |     Version:       
 Severity:  normal      |    Keywords:       
 Blocking:              |   Blockedby:       
------------------------+---------------------------------------------------
 kernel:20080723-asu.stable-uImage.bin
 root file system:20080804-asu.stable-rootfs.jffs2

 Summary:
 Sometimes Profile will show up "unknow" message

 Description:
 Not too many steps, boot the device and click Exposure (right away) you'll
 see the "unknown" show up. Happened on device No.68 still can use the
 dialer or other Qt apps.

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

--- End Message ---
--- Begin Message ---
#1740: [Exposure] Change "Date/Time" as "Clock"
------------------------+---------------------------------------------------
 Reporter:  wendy_hung  |       Owner:  Marek
     Type:  defect      |      Status:  new  
 Priority:  normal      |   Milestone:  ASU  
Component:  Exposure    |     Version:       
 Severity:  normal      |    Keywords:       
 Blocking:              |   Blockedby:       
------------------------+---------------------------------------------------
 Please change "Date/Time" as "Clock" in Exposure.

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