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 583] create an alsa state file that routes system audio
to bluetooth ([EMAIL PROTECTED])
2. [Bug 588] New: Icon-theme broken since settings-daemon
integration ([EMAIL PROTECTED])
3. [Bug 588] Icon-theme broken since settings-daemon integration
([EMAIL PROTECTED])
4. [Bug 587] Icon-theme broken since settings-daemon integration
([EMAIL PROTECTED])
5. [Bug 480] gsmd should report error if can't connect to modem
([EMAIL PROTECTED])
6. [Bug 322] gsmd phonebook cache and OTA updates to ADN/FDN/SDN
([EMAIL PROTECTED])
7. [Bug 583] create an alsa state file that routes system audio
to bluetooth ([EMAIL PROTECTED])
8. Your Bugzilla buglist needs attention. ([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=583
------- Additional Comments From [EMAIL PROTECTED] 2007-06-02 12:30 -------
just an update to the slightly off-topic thread into which this bug entry has
developed: We've started a discussion with Wolfson now on what the restrictions
actually are, and which codec to use for GTA02 and later models.
------- 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=588
Summary: Icon-theme broken since settings-daemon integration
Product: OpenMoko
Version: current svn head
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Theming
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
After switching from plain gtkrc to settings-daemon the icon-theme is broken.
------- 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=588
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |DUPLICATE
------- Additional Comments From [EMAIL PROTECTED] 2007-06-02 12:53 -------
*** This bug has been marked as a duplicate of 587 ***
------- 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=587
------- Additional Comments From [EMAIL PROTECTED] 2007-06-02 12:53 -------
*** Bug 588 has been marked as a duplicate of this bug. ***
------- 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=480
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2007-06-02 16:02 -------
this has now been implemented.
In svn rev. 2131, gsmd has the following extensions:
1) at startup, we only fork into background (daemonize) after the GSM modem has
responded. We wait for 30 seconds and exit with error level otherwise.
2) every five minutes, we check if the modem is still alive. If we cannot
get any response at all (within 30 seconds), we terminate and write
a "FATAL" log line into the log file.
------- 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=322
------- Additional Comments From [EMAIL PROTECTED] 2007-06-02 16:05 -------
this is related to SIM toolkit, which we actually don't want to support for
security reasons. Anything that happens within the modem we can't
affect/prevent, at least not easily.
Anything that requires host support for STK will most likely not be implemented.
STK is often used to take away user control over the phone and give the operator
access to data owned by the user. this is evil.
------- 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=583
------- Additional Comments From [EMAIL PROTECTED] 2007-06-02 22:03 -------
Graeme, is it possible to make a .state file that routes system audio *out* to
the bluetooth headset? We could at least use this for custom ring tones to the
headset.
For audio input, using the built-in mic would be nice so we at least have an
option to use a voip app. Maybe cranking up the mic gain would make it usable
this way.
------- 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=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=301
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=340
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=412
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=422
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=448
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=470
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=471
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=536
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=540
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=541
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=555
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
