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 256] GSM Modem doesn't seem to work on some devices
([EMAIL PROTECTED])
2. [Bug 256] GSM Modem doesn't seem to work on some devices
([EMAIL PROTECTED])
3. [Bug 267] New: internal function duplicates strstr(3)
([EMAIL PROTECTED])
4. [Bug 267] New: internal function duplicates strstr(3)
([EMAIL PROTECTED])
5. [Bug 267] internal function duplicates strstr(3)
([EMAIL PROTECTED])
6. [Bug 267] internal function duplicates strstr(3)
([EMAIL PROTECTED])
7. [Bug 268] New: openmoko-today crashes when one of the buttons
is pressed ([EMAIL PROTECTED])
8. [Bug 268] openmoko-today crashes when one of the buttons is
pressed ([EMAIL PROTECTED])
9. [Bug 263] gsmd doesn't receive AT reply from the modem
properly. ([EMAIL PROTECTED])
10. [Bug 175] MOKO_FINGER_WINDOW has to show_all and then hide to
initialize ([EMAIL PROTECTED])
11. [Bug 175] MOKO_FINGER_WINDOW has to show_all and then hide to
initialize ([EMAIL PROTECTED])
12. [Bug 194] s3c2410fb 8bit mode corrupt
([EMAIL PROTECTED])
13. [Bug 194] s3c2410fb 8bit mode corrupt
([EMAIL PROTECTED])
14. [Bug 194] s3c2410fb 8bit mode corrupt
([EMAIL PROTECTED])
15. [Bug 194] s3c2410fb 8bit mode corrupt
([EMAIL PROTECTED])
16. [Bug 34] Need to decide if lgsm_handle is still valid.
([EMAIL PROTECTED])
17. Your Bugzilla buglist needs attention. ([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=256
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |critical
------- 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=256
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |critical
------- 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=267
Summary: internal function duplicates strstr(3)
Product: OpenMoko
Version: current svn head
Platform: PC
OS/Version: Linux
Status: NEW
Severity: enhancement
Priority: P4
Component: openmoko-messages
AssignedTo: [email protected]
ReportedBy: [EMAIL PROTECTED]
In openmoko-messages' src/main.c, it seems to me that the function in_string
duplicates the libc builtin function strstr(3).
Unless these functions are not available on the embedded system (special libc?),
maybe it could be replaced. Furthermore, in the attached patch, I replaced it by
strcasestr(3) which allow case-insensitive search.
------- 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=267
Summary: internal function duplicates strstr(3)
Product: OpenMoko
Version: current svn head
Platform: PC
OS/Version: Linux
Status: NEW
Severity: enhancement
Priority: P4
Component: openmoko-messages
AssignedTo: [email protected]
ReportedBy: [EMAIL PROTECTED]
In openmoko-messages' src/main.c, it seems to me that the function in_string
duplicates the libc builtin function strstr(3).
Unless these functions are not available on the embedded system (special libc?),
maybe it could be replaced. Furthermore, in the attached patch, I replaced it by
strcasestr(3) which allow case-insensitive search.
------- 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=267
------- Additional Comments From [EMAIL PROTECTED] 2007-03-14 22:34 -------
Created an attachment (id=29)
-->
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=29&action=view)
in_string replace by strcasestr
Opportunity to experiment with Bugzilla patch submission too...
------- 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=267
------- Additional Comments From [EMAIL PROTECTED] 2007-03-14 22:34 -------
Created an attachment (id=29)
-->
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=29&action=view)
in_string replace by strcasestr
Opportunity to experiment with Bugzilla patch submission too...
------- 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=268
Summary: openmoko-today crashes when one of the buttons is
pressed
Product: OpenMoko
Version: current svn head
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: openmoko-today
AssignedTo: [email protected]
ReportedBy: [EMAIL PROTECTED]
This is what I get:
[EMAIL PROTECTED]
~/dev/openmoko/svn/openmoko/trunk/src/target/OM-2007/applications/openmoko-today
$ ../../bin/today
(today:24339): Gtk-WARNING **: Unable to locate theme engine in
module_path: "clearlooks",
(today:24339): Gtk-WARNING **: Unable to locate theme engine in
module_path: "clearlooks",
(today:24339): GLib-WARNING **: GError set over the top of a previous
GError or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL
before it's set.
The overwriting error message was: Failed to execute child process "contacts"
(No such file or directory)
**
(today:24339): WARNING **: Got error 'contacts', code '-1224880124'
Segmentation fault
------- 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=268
------- Additional Comments From [EMAIL PROTECTED] 2007-03-15 01:19 -------
Created an attachment (id=30)
-->
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=30&action=view)
Initialize GError to NULL
This patch initializes GError to NULL in today_launcher_clicked_cb
------- 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=263
------- Additional Comments From [EMAIL PROTECTED] 2007-03-15 02:08 -------
Yes, I have done all of these. Otherwise the "cu -l /dev/ttySAC0" will not
work at all.
Please have somebody else to test the gsmd on real phone. I really began to
wonder it's only me who just cannot make it work.
------- 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=175
------- Additional Comments From [EMAIL PROTECTED] 2007-03-15 02:11 -------
The problem is that MOKO_FINGER_WINDOW will not display well when you don't
use gtk_widget_show_all, especially when there are wheel & toolbox attached to
the window.
You can test every window by modifying the main() temporarily.
I guess some modification has to be done to the libmokoui.
------- 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=175
------- Additional Comments From [EMAIL PROTECTED] 2007-03-15 02:11 -------
The problem is that MOKO_FINGER_WINDOW will not display well when you don't
use gtk_widget_show_all, especially when there are wheel & toolbox attached to
the window.
You can test every window by modifying the main() temporarily.
I guess some modification has to be done to the libmokoui.
------- 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=194
------- Additional Comments From [EMAIL PROTECTED] 2007-03-15 02:36 -------
I enabled the bootup logo to test the colors on the textconsole.
Using BSWP on 16BPP has a tint. HWSWP is the right choice for 16BPP. It gives
perfect textconsole and X.
For 8BPP BSWP is the right choice for the textconsole. The Tux has the right
color s. The problem with 8BPP start with the Xserver. When starting the xserver
the following appears:
can't get colormap: Invalid argument
alloc color failed
alloc color failed
...
------- 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=194
------- Additional Comments From [EMAIL PROTECTED] 2007-03-15 02:36 -------
I enabled the bootup logo to test the colors on the textconsole.
Using BSWP on 16BPP has a tint. HWSWP is the right choice for 16BPP. It gives
perfect textconsole and X.
For 8BPP BSWP is the right choice for the textconsole. The Tux has the right
color s. The problem with 8BPP start with the Xserver. When starting the xserver
the following appears:
can't get colormap: Invalid argument
alloc color failed
alloc color failed
...
------- 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=194
------- Additional Comments From [EMAIL PROTECTED] 2007-03-15 02:40 -------
Funny observation: rxvt has the right colors, but only grey, white and black.
Same for other apps with disabled openmoko theme.
Icons are still broken
------- 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=194
------- Additional Comments From [EMAIL PROTECTED] 2007-03-15 02:40 -------
Funny observation: rxvt has the right colors, but only grey, white and black.
Same for other apps with disabled openmoko theme.
Icons are still broken
------- 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-15 03:04 -------
another scenario: when the dialer calls lgsm_pin() to submit the pin code,
besides the bytes that submitted, dialer will be more concerned about whether
the pin code is acceptable or not.
For such similar cases, how to make a synch command to modem?
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
--- 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 ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
