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 939] Can't add contact phone number when not connected
to GSM network ([EMAIL PROTECTED])
2. [Bug 926] Project mailing lists are broken.
([EMAIL PROTECTED])
3. [Bug 176] libgsmd need a mechanism to avoid dead waiting.
([EMAIL PROTECTED])
4. [Bug 943] New: openmoko-browser2 segfaults when trying to
open an url ([EMAIL PROTECTED])
5. [Bug 894] gsmd locks-up if libgsmd-tool disconnects too
quickly ([EMAIL PROTECTED])
6. [Bug 894] gsmd locks-up if libgsmd-tool disconnects too
quickly ([EMAIL PROTECTED])
7. [Bug 894] gsmd locks-up if libgsmd-tool disconnects too
quickly ([EMAIL PROTECTED])
8. [Bug 812] "neo1973 gsm version" command does not respond
([EMAIL PROTECTED])
9. Your Bugzilla buglist needs attention. ([EMAIL PROTECTED])
10. [Bug 834] [patch] libgsmd-tool does not allow sms with more
than one word ([EMAIL PROTECTED])
11. [Bug 941] Kinetic scrolling is hard to use with fingers
([EMAIL PROTECTED])
12. [Bug 940] Dialer cursor positioning is confusing
([EMAIL PROTECTED])
13. [Bug 166] u-boot cdc_acm hot un-plug/replug hang
([EMAIL PROTECTED])
14. [Bug 805] lgsm_get_signal_quality() defined but not
implemented ([EMAIL PROTECTED])
15. [Bug 812] "neo1973 gsm version" command does not respond
([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=939
------- Additional Comments From [EMAIL PROTECTED] 2007-10-16 18:45 -------
There shouldn't be any link between GSM connectivity and adding contact
attributes. Could you let us know what version of the software you have and is
there anything relevant output in ~/.xsession-errors.
------- 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=926
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2007-10-16 18:51 -------
Hi,
I have fixed this bug. A test is performed by subscribing your user mail list.
Everything seems fine. Please try again. Any problem just let me know.
CH
------- 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=176
------- Additional Comments From [EMAIL PROTECTED] 2007-10-16 21:00 -------
Could you confirm whether this modem sleep mode may be the one that causes gsmd
to periodically (haven't got the impression that it happens after a constant
time, though) assess that the modem is dead, when otherwise connected correctly
to network:
Sat Oct 13 10:06:20 2007 <1> gsmd.c:78:alive_tmr_cb() gsmd_alive timer expired
Sat Oct 13 10:06:20 2007 <8> gsmd.c:81:alive_tmr_cb() modem dead!
This happens even though unsolicited messages (signal strength and LAC/CI) keep
beeing received and parsed correctly. I can see that, when this occurs, every at
command sent to the modem is unanswered at gsmd/libgsmd level.
Does the patch cover this case? Or isn't the modem in sleep mode in this
situation?
------- 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=943
Summary: openmoko-browser2 segfaults when trying to open an url
Product: OpenMoko
Version: 2007.2
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: openmoko-webbrowser
AssignedTo: [email protected]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
Starting the latest openmoko-browser2, typing in www.google.com and pressing
Open URL in new window results in crash. Says:
openmoko-browser2: symbol lookup error: openmoko-browser2 undefined symbol:
webkit_gtk_frame_get_title
This is with a rootfs built Oct 16 with the MokoMakefile, no modifications.
------- 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=894
------- Additional Comments From [EMAIL PROTECTED] 2007-10-16 22:46 -------
Created an attachment (id=359)
-->
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=359&action=view)
Primitive patch to fix gsmd client disconnection
This makes gsmd make sure that no references to the gsmd_user struct are left
in the AT commands queues before destroying the struct when a user disconnects.
It could be done in a cleaner way. This fixes the above bug for me, please
test.
------- 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=894
------- Additional Comments From [EMAIL PROTECTED] 2007-10-16 22:57 -------
Created an attachment (id=360)
-->
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=360&action=view)
Add libgsmd-tool -m shell -w switch.
This adds a -w/--wait switch that will make libgsmd-tool -m shell execute some
of the commands "synchronously" i.e. wait for the final response for each of
the commands before exiting. This is in order to allow libgsmd-tool -m shell
to be used in scripts or with a commandline like the one given by Pavel for
quick hacks (*). Note that it will wait infinitely if the modem is not
responding. I added this functionality only for shell commands that I knew how
to determine the final response for.
(*) Quick hack, because this is definitely not the proper way to use
libgsmd-tool. As I understand libgsmd-tool is only a test tool for developers
and this is why we don't care much about it segfaulting on illegal input etc.
The proper way to use gsmd is through normal libgsmd calls, e.g. using the
python bindings if you must.
Both patches apply on top the patches from OE plus attachment #355. This one
goes on top of attachment #358.
------- 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=894
------- Additional Comments From [EMAIL PROTECTED] 2007-10-16 22:59 -------
err, #59
------- 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=812
------- Additional Comments From [EMAIL PROTECTED] 2007-10-17 03:27 -------
Using u-boot-gta01bv4-1.2.0+git20070917+svnr2943-r0.bin this bug still shows up.
I have a GTA01Bv4.
------- 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=129
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=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=727
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=742
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=808
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=835
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=847
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=862
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=864
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=865
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=870
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=882
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=888
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=908
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=834
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2007-10-17 06:33 -------
Checked-in rev 3199. 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=941
------- Additional Comments From [EMAIL PROTECTED] 2007-10-17 09:32 -------
In my experience this comes from your finger "bouncing", i.e. you put your
finger on the touch screen and tslib registers a press but right after that your
pressure releases and tslib thinks that you in fact have just clicked on the
touch screen.
With a stylus it would be less likely to happen since the pressure there is
larger.
Using double clicks on a touch screen is quite cumbersome and in our GUI style
guidelines the double click is "strongly discouraged" (see
http://wiki.openmoko.org/wiki/GUI_Style_Guidelines#Touch_Screen).
We would need some kind of pressure detection/hysteresis for the touch screen,
but I'm not quite sure if/how we can do this.
------- 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=940
------- Additional Comments From [EMAIL PROTECTED] 2007-10-17 09:39 -------
Actually the digit before the cursor position is shown in bold, but that is not
updated if position it somewhere in the number. If you then delete/add a digit
the correct position is indicated.
I say we just continue to use that indication and update the entry field when
the cusor moves.
------- 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=166
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2007-10-17 10:04 -------
I just tested this repeatedly with issuing "help", then unplugging the device
and reconnecting through
screen /dev/ttyACM0
It worked every time so far (out of ~15 times) and the output that didn't make
it out in time was printed on a reconnect.
Closing this now.
------- 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=805
------- Additional Comments From [EMAIL PROTECTED] 2007-10-17 10:28 -------
Clarify in rev 3204.
lgsm_get_signal_quality() was replaced by 'lgsm_signal_quality()'.
------- 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=812
------- Additional Comments From [EMAIL PROTECTED] 2007-10-17 10:42 -------
Thanks for the feedbacks. The primary reason might result from new GSM firmware
our internal S/W team members are using. I'll roll back to the very old one in
order to clarify.
------- 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
