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 890] New: add --enable-gadgetfs option to configure
([EMAIL PROTECTED])
2. [Bug 890] add --enable-gadgetfs option to configure
([EMAIL PROTECTED])
3. [Bug 891] New: Don't power anything up if battery is critical
and charger is inserted ([EMAIL PROTECTED])
4. [Bug 891] Don't power anything up if battery is critical and
charger is inserted ([EMAIL PROTECTED])
5. [Bug 891] Don't power anything up if battery is critical and
charger is inserted ([EMAIL PROTECTED])
6. Your Bugzilla buglist needs attention. ([EMAIL PROTECTED])
7. [Bug 892] New: libmokoui2 segfaults since r3023 when loading
stock icons ([EMAIL PROTECTED])
8. [Bug 892] libmokoui2 segfaults since r3023 when loading stock
icons ([EMAIL PROTECTED])
9. [Bug 21] sms function missing
([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=890
Summary: add --enable-gadgetfs option to configure
Product: OpenMoko
Version: current svn head
Platform: PC
OS/Version: Linux
Status: NEW
Severity: wishlist
Priority: P2
Component: qemu-neo1973
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
Index: configure
===================================================================
--- configure (revision 3039)
+++ configure (working copy)
@@ -304,6 +304,8 @@
*) echo "undefined SPARC architecture. Exiting";exit 1;;
esac
;;
+ --enable-gadgetfs) gadgetfs="yes"
+ ;;
esac
done
------- 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=890
------- Additional Comments From [EMAIL PROTECTED] 2007-09-25 17:01 -------
Created an attachment (id=318)
-->
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=318&action=view)
patch for configure
------- 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=891
Summary: Don't power anything up if battery is critical and
charger is inserted
Product: OpenMoko
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: critical
Priority: P2
Component: u-boot
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
If the battery charge is too low, doing things like powering up the backlight is
counterproductive (if things are really critical, it could make the voltage sag
enough that the CPU loses power, causing a reset cycle). This could be the cause
for reports of repeated backlight flashing when trying to recharge dead
batteries.
If the powerup cause is reset or charger insert, AND the battery level is too
low (below some threshold voltage), u-boot should detect the situation at the
earliest possible time (perhaps even before powering up the SDRAM) and refrain
from powering up anything else (perhaps even powering down the CPU, or making it
use the least possible amount of power while slowly polling the battery status).
This would give the charger time to bring the battery voltage back to a
comfortable level.
------- 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=891
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|unspecified |2007.2
------- 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=891
------- Additional Comments From [EMAIL PROTECTED] 2007-09-26 03:19 -------
Related bugs: bug 293 (don't boot the linux kernel in this situation), bug 848
(charger UI for u-boot)
------- 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=41
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=69
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=112
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=114
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=129
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=141
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=181
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=276
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=301
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=340
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=448
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=466
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=555
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=572
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=589
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=624
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=630
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=661
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=675
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=696
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=714
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=727
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=800
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=808
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=835
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=846
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=847
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=862
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=864
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=865
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=870
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=881
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=882
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=892
Summary: libmokoui2 segfaults since r3023 when loading stock
icons
Product: OpenMoko
Version: current svn head
Platform: PC
OS/Version: Linux
Status: NEW
Severity: blocker
Priority: P1
Component: openmoko-libs
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected],[EMAIL PROTECTED]
On systems where one or more icons are missing, libmokoui2 can segfault because
it'll try to unref a pixbuf that might be NULL. As a result, all applications
using libmokoui2 crash on current OpenMoko images since r3023.
Proposed bugfix is attached.
-Soeren
------- 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=892
------- Additional Comments From [EMAIL PROTECTED] 2007-09-26 06:37 -------
Created an attachment (id=319)
-->
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=319&action=view)
Proposed patch
------- 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=21
------- Additional Comments From [EMAIL PROTECTED] 2007-09-26 11:33 -------
Created an attachment (id=320)
-->
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=320&action=view)
add an event 'SMS memory full'
I made a patch for SMS memory full. It will create an event
'GSMD_EVT_SMS_IND', when we receive
"+CMS ERROR: 322". The error code 322 means 'memory full' based on 3GPP
TS 27005 sec 3.2.5 Message Service Failure Result Code +CMS ERROR.
------- 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
