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 368] The ???Speaker??? function doesn't work in incall
mode. ([EMAIL PROTECTED])
2. [Bug 385] libmokogsmd should restart gsmd if it went away
during a session ([EMAIL PROTECTED])
3. [Bug 845] Dialer doesn't honour its button in Today
([EMAIL PROTECTED])
4. [Bug 845] Dialer doesn't honour its button in Today
([EMAIL PROTECTED])
5. [Bug 846] New: bugs.openmoko.org should redirect to
bugzilla.openmoko.org ([EMAIL PROTECTED])
6. [Bug 847] New: Shutdown if battery level goes too low
([EMAIL PROTECTED])
7. [Bug 848] New: A charger mode for uboot
([EMAIL PROTECTED])
8. [Bug 842] Whenever possible, Amp Mode should be Off
([EMAIL PROTECTED])
9. [Bug 788] Starting or stopping gsmd completely locks up the
Neo ([EMAIL PROTECTED])
10. Your Bugzilla buglist needs attention. ([EMAIL PROTECTED])
11. [Bug 849] New: bitbake fails because it tries to fetch
openmoko with svn co -r 1 ([EMAIL PROTECTED])
12. [Bug 850] New: Screen capture application uses standard GNOME
file browser dialog which is too large for the display
([EMAIL PROTECTED])
13. [Bug 850] Screen capture application uses standard GNOME file
browser dialog which is too large for the display
([EMAIL PROTECTED])
14. [Bug 850] Screen capture application uses standard GNOME file
browser dialog which is too large for the display
([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=368
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|The âSpeakerâ function |The âSpeakerâ function
|canât work in incall mode.|doesn't work in incall mode.
------- Additional Comments From [EMAIL PROTECTED] 2007-09-13 17:21 -------
Clarifying title. What do we need to do to implement speaker/hands-free mode?
------- 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=385
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|[EMAIL PROTECTED] |[EMAIL PROTECTED]
Component|openmoko-dialer |openmoko-libs
Summary|Openmoko dialer fails after |libmokogsmd should restart
|gsmd restart |gsmd if it went away during
| |a session
------- Additional Comments From [EMAIL PROTECTED] 2007-09-13 17:24 -------
This should probably now be solved in libmokogsmd. libmokogsmd already attempts
to start gsmd if it isn't running when the library is initialised. It should
probably attempt to start gsmd again if it dies during a session.
------- 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=845
------- Additional Comments From [EMAIL PROTECTED] 2007-09-13 17:35 -------
So the issue here is that the main Dialer window does not get presented if it is
already open, but hidden at the time the button is Today is pressed?
------- 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=845
------- Additional Comments From [EMAIL PROTECTED] 2007-09-13 18:56 -------
Yes, that's one part of the issue.
The second part is that if the Dialer window is not open, it often doesn't open
at the time the button in Today is pressed.
------- 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=846
Summary: bugs.openmoko.org should redirect to
bugzilla.openmoko.org
Product: Site Infrastructure
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Bugzilla
AssignedTo: [email protected]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
Currently http://bugs.openmoko.org/ shows the same web site as
http://www.openmoko.org/. I would expect it to redirect to
http://bugzilla.openmoko.org/ instead. bugs is shorter than bugzilla so we might
also consider making that the canonical name.
------- 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=847
Summary: Shutdown if battery level goes too low
Product: OpenMoko
Version: current svn head
Platform: Neo1973
OS/Version: Linux
Status: NEW
Severity: major
Priority: P2
Component: openmoko-panel-battery
AssignedTo: [email protected]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
We should always keep enough charge in the battery for negotiating the 500 mA
fast charge mode when a suitable USB connection becomes available, and
preferably for showing the user some on-screen feedback about charge state. This
means neod or something else should monitor the battery level and trigger a
system shutdown when there's little charge left (5%?). A clean shutdown also
ensures the modem and sound amplifier don't draw current anymore.
(I don't think we have a proper component for this in bugzilla yet.)
------- 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=848
Summary: A charger mode for uboot
Product: OpenMoko
Version: current svn head
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: u-boot
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
Current power management implications are difficult for users to understand as
we don't hide the underlying hardware details. One part we should do is a
special mode in uboot that can be entered for charging the phone when it's off.
One simple part of this is the logic to not boot a kernel while there would be
too little charge (10%?) in the battery to start and shut down the system
cleanly with still some charge left to get back to uboot. We could simply power
off the phone if there is too little charge, but better usability could be
achieved with a mode that shows the charging progress: whether we are currently
charging and the current battery charge percentage.
In the mode, the user could have a menu with these entries:
1. Fully shut down the phone (going back to 100mA charge?)
2. Toggle: Do/don't boot automatically as soon as there's enough charge
3. Boot now (inactive if not enough charge yet)
If there is some trouble in the charging process or the source disappears, we
should show a warning message. If this continues, the message should be stored
for display at the next boot, and the phone should be fully shut down.
------- 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=842
------- Additional Comments From [EMAIL PROTECTED] 2007-09-14 02:37 -------
Sounds reasonable. This will also work out-of-the box with our pulseaudio setup
-- which we have configured to auto-unload its modules (hence releasing the alsa
driver) after some period of inactivity (10 seconds or so).
------- 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=788
------- Additional Comments From [EMAIL PROTECTED] 2007-09-14 02:58 -------
ok, i have applied this stty stuff as a workaround in OE. I really don't like it
though and I sincerely hope this will be a temporary thing.
------- 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=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=742
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=849
Summary: bitbake fails because it tries to fetch openmoko with
svn co -r 1
Product: OpenMoko
Version: 2007.2
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: OE bitbake recipes / build system
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
bitbake fails with an ERROR in fetch on openmoko2 components.
This is because it is explictly trying to svn co -r 1
the revision number comes from classes/openmoko2.bbclass:
SVNREV = "r${SRCREV}"
I think somewhere this SRCREV is not being set and defaults to 1
I changed this to SVNREV = "rHEAD" and also changed the default SRC_URI in that
file to include "...;rev=HEAD"
and then all the HEAD versions of the openmoko apps get downloaded and it works.
------- 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=850
Summary: Screen capture application uses standard GNOME file
browser dialog which is too large for the display
Product: OpenMoko
Version: 2007.2
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Applications & Dependencies
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
The screen capture application (at the least) uses the standard GNOME file
browser dialog box for file selections, e.g. when you click the "browse" button.
The GNOME file browser dialog is too large for the Neo1973 screen and some of
the elements are unusable particularly when "browse for other folders" is
clicked.
Steps to reproduce:
1) run the "Take Screenshot" application
2) click the "browse" button
3) click the "browse for other folders" dropdown
------- 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=850
------- Additional Comments From [EMAIL PROTECTED] 2007-09-14 11:39 -------
Created an attachment (id=297)
-->
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=297&action=view)
Take Screenshot application - file browser
screenshot of file browser dialog
------- 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=850
------- Additional Comments From [EMAIL PROTECTED] 2007-09-14 11:40 -------
Created an attachment (id=298)
-->
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=298&action=view)
File browser expanded
Take Screenshot application with the file browser dialog expanded
------- 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
