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 212] Charging seems completely broken
([EMAIL PROTECTED])
2. [Bug 212] Charging seems completely broken
([EMAIL PROTECTED])
3. [Bug 212] Charging seems completely broken
([EMAIL PROTECTED])
4. [Bug 212] Charging seems completely broken
([EMAIL PROTECTED])
5. [Bug 212] Charging seems completely broken
([EMAIL PROTECTED])
6. [Bug 212] Charging seems completely broken
([EMAIL PROTECTED])
7. [Bug 291] Signal Strength reading always delivered as '0'
([EMAIL PROTECTED])
8. [Bug 291] Signal Strength reading always delivered as '0'
([EMAIL PROTECTED])
9. Your Bugzilla buglist needs attention. ([EMAIL PROTECTED])
10. [Bug 320] New: Panel and applets debug spew kills
powermanagements ([EMAIL PROTECTED])
11. [Bug 320] New: Panel and applets debug spew kills
powermanagements ([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=212
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2007-03-28 01:56 -------
I can confirm that the latest version of u-boot resolves this issue.
When charging a completely drained battery you have to be patient, though. It
took me more than 3 hours to charge the phone far enough that u-boot would allow
it to turn on again (You will have to press the power button). But then all was
fine.
------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=212
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2007-03-28 01:56 -------
I can confirm that the latest version of u-boot resolves this issue.
When charging a completely drained battery you have to be patient, though. It
took me more than 3 hours to charge the phone far enough that u-boot would allow
it to turn on again (You will have to press the power button). But then all was
fine.
------- 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=212
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2007-03-28 01:56 -------
I can confirm that the latest version of u-boot resolves this issue.
When charging a completely drained battery you have to be patient, though. It
took me more than 3 hours to charge the phone far enough that u-boot would allow
it to turn on again (You will have to press the power button). But then all was
fine.
------- 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=212
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2007-03-28 01:56 -------
I can confirm that the latest version of u-boot resolves this issue.
When charging a completely drained battery you have to be patient, though. It
took me more than 3 hours to charge the phone far enough that u-boot would allow
it to turn on again (You will have to press the power button). But then all was
fine.
------- 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=212
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2007-03-28 01:56 -------
I can confirm that the latest version of u-boot resolves this issue.
When charging a completely drained battery you have to be patient, though. It
took me more than 3 hours to charge the phone far enough that u-boot would allow
it to turn on again (You will have to press the power button). But then all was
fine.
------- 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=212
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2007-03-28 01:56 -------
I can confirm that the latest version of u-boot resolves this issue.
When charging a completely drained battery you have to be patient, though. It
took me more than 3 hours to charge the phone far enough that u-boot would allow
it to turn on again (You will have to press the power button). But then all was
fine.
------- 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=291
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2007-03-28 02:21 -------
fixed in svn rev. 1520
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=291
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2007-03-28 02:21 -------
fixed in svn rev. 1520
------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.
--- 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=69
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=70
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=137
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=192
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=204
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=232
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=320
Summary: Panel and applets debug spew kills powermanagements
Product: OpenMoko
Version: current svn head
Platform: Macintosh
OS/Version: MacOS X
Status: NEW
Severity: normal
Priority: P2
Component: openmoko-panel
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
This happens a few times every second:
** (matchbox-panel:4150): DEBUG: update battery applet
** (matchbox-panel:4150): DEBUG: moko gsm quality = 0
** (matchbox-panel:4150): DEBUG: update battery applet
** (matchbox-panel:4150): DEBUG: update battery applet
** (matchbox-panel:4150): DEBUG: moko gsm quality = 0
** (matchbox-panel:4150): DEBUG: update battery applet
** (matchbox-panel:4150): DEBUG: update battery applet
** (matchbox-panel:4150): DEBUG: moko gsm quality = 0
** (matchbox-panel:4150): DEBUG: update battery applet
** (matchbox-panel:4150): DEBUG: update battery applet
** (matchbox-panel:4150): DEBUG: moko gsm quality = 0
** (matchbox-panel:4150): DEBUG: update battery applet
Which is also written to a log file. This keeps the kernel busy and fills up
space with the logfile
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=320
Summary: Panel and applets debug spew kills powermanagements
Product: OpenMoko
Version: current svn head
Platform: Macintosh
OS/Version: MacOS X
Status: NEW
Severity: normal
Priority: P2
Component: openmoko-panel
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
This happens a few times every second:
** (matchbox-panel:4150): DEBUG: update battery applet
** (matchbox-panel:4150): DEBUG: moko gsm quality = 0
** (matchbox-panel:4150): DEBUG: update battery applet
** (matchbox-panel:4150): DEBUG: update battery applet
** (matchbox-panel:4150): DEBUG: moko gsm quality = 0
** (matchbox-panel:4150): DEBUG: update battery applet
** (matchbox-panel:4150): DEBUG: update battery applet
** (matchbox-panel:4150): DEBUG: moko gsm quality = 0
** (matchbox-panel:4150): DEBUG: update battery applet
** (matchbox-panel:4150): DEBUG: update battery applet
** (matchbox-panel:4150): DEBUG: moko gsm quality = 0
** (matchbox-panel:4150): DEBUG: update battery applet
Which is also written to a log file. This keeps the kernel busy and fills up
space with the logfile
------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
