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 248] New: Buttons disappear under zoom
([EMAIL PROTECTED])
8. [Bug 248] New: Buttons disappear under zoom
([EMAIL PROTECTED])
9. [Bug 237] Fix remaining https urls in bitbake recipes.
([EMAIL PROTECTED])
10. [Bug 237] Fix remaining https urls in bitbake recipes.
([EMAIL PROTECTED])
11. [Bug 248] Buttons disappear under zoom
([EMAIL PROTECTED])
12. [Bug 248] Buttons disappear under zoom
([EMAIL PROTECTED])
13. [Bug 34] Need to decide if lgsm_handle is still valid.
([EMAIL PROTECTED])
14. [Bug 34] Need to decide if lgsm_handle is still valid.
([EMAIL PROTECTED])
15. [Bug 33] incoming call status report causes gsmd to crash.
([EMAIL PROTECTED])
16. [Bug 33] incoming call status report causes gsmd to crash.
([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=212
------- Additional Comments From [EMAIL PROTECTED] 2007-03-08 19:54 -------
I've replicated the problem with my GTA01B_V3. Wehn I received it the battery
was charged and the device booted to Linux fine.
Then I let the battery run down. And since then, if I plug it in, (to either the
wall charger or to my laptop via USB), it goes into a 7 second loop, (giving the
vibrator a quick buzz, and momentarily flashing the openmoko flash image, then
off agin). I left it on the charger overnight and the behavior didn't change.
I'm still trying to find a local shope to purchase a replacement battery, (or
better, an external charger), so I can get started hacking on this little
gadget. :-|
-Carl
------- 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=212
------- Additional Comments From [EMAIL PROTECTED] 2007-03-08 19:54 -------
I've replicated the problem with my GTA01B_V3. Wehn I received it the battery
was charged and the device booted to Linux fine.
Then I let the battery run down. And since then, if I plug it in, (to either the
wall charger or to my laptop via USB), it goes into a 7 second loop, (giving the
vibrator a quick buzz, and momentarily flashing the openmoko flash image, then
off agin). I left it on the charger overnight and the behavior didn't change.
I'm still trying to find a local shope to purchase a replacement battery, (or
better, an external charger), so I can get started hacking on this little
gadget. :-|
-Carl
------- 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
------- Additional Comments From [EMAIL PROTECTED] 2007-03-08 19:54 -------
I've replicated the problem with my GTA01B_V3. Wehn I received it the battery
was charged and the device booted to Linux fine.
Then I let the battery run down. And since then, if I plug it in, (to either the
wall charger or to my laptop via USB), it goes into a 7 second loop, (giving the
vibrator a quick buzz, and momentarily flashing the openmoko flash image, then
off agin). I left it on the charger overnight and the behavior didn't change.
I'm still trying to find a local shope to purchase a replacement battery, (or
better, an external charger), so I can get started hacking on this little
gadget. :-|
-Carl
------- 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
------- Additional Comments From [EMAIL PROTECTED] 2007-03-08 21:03 -------
This is really strange. I have not been able to reproduce this ever with any my
devices and/or batteries. So it might be some bug that only shows up in
particular phones.
Carl [or anyone else who has that problem]: When you insert a charged (original
or replacement) battery into the device, please immediately access the u-boot
prompt and send me [attach to this bug] the output of
1) neo1973 charger state
2) imd 0x08 0x00 0x30
This will enable os to look at the charger registers.
thanks!
------- 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=212
------- Additional Comments From [EMAIL PROTECTED] 2007-03-08 21:03 -------
This is really strange. I have not been able to reproduce this ever with any my
devices and/or batteries. So it might be some bug that only shows up in
particular phones.
Carl [or anyone else who has that problem]: When you insert a charged (original
or replacement) battery into the device, please immediately access the u-boot
prompt and send me [attach to this bug] the output of
1) neo1973 charger state
2) imd 0x08 0x00 0x30
This will enable os to look at the charger registers.
thanks!
------- 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
------- Additional Comments From [EMAIL PROTECTED] 2007-03-08 21:03 -------
This is really strange. I have not been able to reproduce this ever with any my
devices and/or batteries. So it might be some bug that only shows up in
particular phones.
Carl [or anyone else who has that problem]: When you insert a charged (original
or replacement) battery into the device, please immediately access the u-boot
prompt and send me [attach to this bug] the output of
1) neo1973 charger state
2) imd 0x08 0x00 0x30
This will enable os to look at the charger registers.
thanks!
------- 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=248
Summary: Buttons disappear under zoom
Product: Site Infrastructure
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Wiki
AssignedTo: [email protected]
ReportedBy: [EMAIL PROTECTED]
In firefox (2.0.0.1), if I use text-zoom (<Ctrl - +> or Menu -> View -> Text
size -> Increase) the buttons for edit/history/etc become unreachable.
Normal: Without zoom a small fraction of them is visible and the rest pops up,
when the mouse is on that small fraction.
BUT with zoom, this small fraction disappears completely.
------- 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=248
Summary: Buttons disappear under zoom
Product: Site Infrastructure
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Wiki
AssignedTo: [email protected]
ReportedBy: [EMAIL PROTECTED]
In firefox (2.0.0.1), if I use text-zoom (<Ctrl - +> or Menu -> View -> Text
size -> Increase) the buttons for edit/history/etc become unreachable.
Normal: Without zoom a small fraction of them is visible and the rest pops up,
when the mouse is on that small fraction.
BUT with zoom, this small fraction disappears completely.
------- 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=237
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2007-03-08 21:43 -------
Committed revision 1278.
------- 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=237
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2007-03-08 21:43 -------
Committed revision 1278.
------- 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=248
------- Additional Comments From [EMAIL PROTECTED] 2007-03-08 21:57 -------
reproducible in Konqueror 3.5.6 (DKE 3.5.6)
------- 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=248
------- Additional Comments From [EMAIL PROTECTED] 2007-03-08 21:57 -------
reproducible in Konqueror 3.5.6 (DKE 3.5.6)
------- 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=34
------- Additional Comments From [EMAIL PROTECTED] 2007-03-09 00:14 -------
the lgsm_handle is always 'valid', i.e. points to a correctly allocated and
filled data structure.
However, libgsmd calls should return an error in case gsmd cannot be contacted.
There are two options for this problem:
1) have libgsmd automatically do reconnect attempts in the background
2) have libgsmd just return errors to all calls and do the reconnect inside the
application program
I will try to refine the API to include both options as possibility.
In any case, openmoko-dialer should check the return code of libgsmd function
calls and display a dialog box about gsmd not being available.
------- 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=34
------- Additional Comments From [EMAIL PROTECTED] 2007-03-09 00:14 -------
the lgsm_handle is always 'valid', i.e. points to a correctly allocated and
filled data structure.
However, libgsmd calls should return an error in case gsmd cannot be contacted.
There are two options for this problem:
1) have libgsmd automatically do reconnect attempts in the background
2) have libgsmd just return errors to all calls and do the reconnect inside the
application program
I will try to refine the API to include both options as possibility.
In any case, openmoko-dialer should check the return code of libgsmd function
calls and display a dialog box about gsmd not being available.
------- 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=33
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2007-03-09 00:14 -------
this has been fixed long time ago.
------- 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=33
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2007-03-09 00:14 -------
this has been fixed long time ago.
------- 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
