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 1222] New: openmoko-today's launcher is often
      unresponsive ([EMAIL PROTECTED])
   2. [Bug 1193] Severe performance problems with Pulseaudio
      ([EMAIL PROTECTED])
   3. [Bug 1223] New: SD card no longer operational with 2.6.24
      ([EMAIL PROTECTED])
   4. Your Bugzilla buglist needs attention. ([EMAIL PROTECTED])
   5. [Bug 1223] SD card no longer operational with 2.6.24
      ([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1222

           Summary: openmoko-today's launcher is often unresponsive
           Product: OpenMoko
           Version: 2007.2
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: openmoko-today
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]
                CC: [email protected]


Quite often I have to tap an app entry several times in order to launch it. It
is the same, whether I use the finger or the stylus.

However, when I use the mouse (starting the xserver with -ac switch  in
/etc/X11/Xserver and using x2x -east -to 192.168.0.202:0) this problem does not
exist.

Remark: under GTK I have seen bogus mouse events with the first one having a 0,0
coordinate before the correct coordinate comes in in a following event. Maybe
that's the reason for not getting the event through?



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





------- Additional Comments From [EMAIL PROTECTED]  2008-02-08 23:14 -------
I'm lead to assume that this is due to lack of proper atomic ops support on the 
SOC - http://0pointer.de/blog/projects/atomic-rt.html has more on that.

I didn't get around yet to try the suggested workaround, help would be 
appreciated.



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

           Summary: SD card no longer operational with 2.6.24
           Product: OpenMoko
           Version: current svn head
          Platform: Neo1973
        OS/Version: Linux
            Status: NEW
          Severity: critical
          Priority: P1
         Component: kernel
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]
                CC: [email protected]


As described in http://lists.openmoko.org/pipermail/openmoko-kernel/2008-
February/000808.html the SD card does get detected but no valid partition table 
is found. This behavior started after the update to 2.6.24.



------- 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 ---
[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=934
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=935
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1012
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1081
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1107
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1127
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1133
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1136
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1158
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1162
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1189
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1197
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1199
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1200
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1201
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1206



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1223





------- Additional Comments From [EMAIL PROTECTED]  2008-02-09 09:38 -------
Actually neither reading nor writing the card works correctly. When I create a
file system on /dev/mmcblk0 using my notebook's card reader, the Neo cannot read
it. Also, wenn I write some string (e.g. echo "This is a test sentence" >
/dev/mmcblk0) onto the card using a GTA01 with 2.6.24 kernel, it shows up that
only the "T" at the beginning is actually written to the card.

Perhaps there's some timing issue?

I tested using both the shipped 512 MB card as well as another 2 GB Sandisk
micro SD.



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



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

Reply via email to