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 907] Application list sort order should be
case-INsensitive ([EMAIL PROTECTED])
2. [Bug 851] Tapping a task doesn't start Tasks
([EMAIL PROTECTED])
3. [Bug 901] openmoko-today is displaying wrong count of missed
calls ([EMAIL PROTECTED])
4. [Bug 905] media player should not try to play non-media files
([EMAIL PROTECTED])
5. [Bug 904] volume has poor range when headphones are plugged
in. ([EMAIL PROTECTED])
6. [Bug 863] Today should not close itself with all applications
([EMAIL PROTECTED])
7. [Bug 802] openmoko-dialer2 segfaults when first digit entered
is '#' ([EMAIL PROTECTED])
8. [Bug 863] Today should not close itself with all applications
([EMAIL PROTECTED])
9. [Bug 863] Today should not close itself with all applications
([EMAIL PROTECTED])
10. [Bug 863] Today should not close itself with all applications
([EMAIL PROTECTED])
11. [Bug 908] New: Unexpected onscreen keyboard expose/collapse
behavior in openmoko-terminal2 ([EMAIL PROTECTED])
12. [Bug 909] New: After accepting PIN the dialer is not closed.
([EMAIL PROTECTED])
13. [Bug 910] New: When a kernel ipkg is released, "ipkg upgrade"
breaks kernel modules ([EMAIL PROTECTED])
14. [Bug 884] System doesn't support vfat filesystems on microSD
cards ([EMAIL PROTECTED])
15. [Bug 666] 3G SIM capability
([EMAIL PROTECTED])
16. Your Bugzilla buglist needs attention. ([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=907
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2007-10-04 12:01 -------
Fixed in libtaku r1725 - openmoko-today will need to be re-fetched to show the
fix.
------- 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=851
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2007-10-04 12:04 -------
Fixed in r3076
------- 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=901
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2007-10-04 12:17 -------
Fixed in r3077 using guidance from patch, 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=905
------- Additional Comments From [EMAIL PROTECTED] 2007-10-04 12:28 -------
This issue will be fixed, just need to think of a clean (= fast and extensible)
approach to this. It's on my to-do list :)
-Soeren
------- 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=904
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
------- Additional Comments From [EMAIL PROTECTED] 2007-10-04 12:33 -------
> I have volume set to 7% and it is still quite loud in headphones, while it is
pretty quiet on speaker.
To my regret that's not within the Player's scope - after all, the Media Player
isn't aware of which output is used (at least as of now).
> Changing volume makes audio stop for few second...
That's a gstreamer/PulseAudio issue that was fixed in SVN already - it happens
because CPU load is way too high.
> I also get some funny effects whenever I touch the connector.
That's outside the scope of the Media Player as well, so it might be a good
idea to file a separate bug report for that :)
-Soeren
------- 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=863
------- Additional Comments From [EMAIL PROTECTED] 2007-10-04 17:17 -------
Today doesn't close itself, it crashes due to an X error - Unfortunately, I
don't know why this is yet, but it's on my TODO list to investigate and fix.
------- 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=802
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2007-10-04 18:17 -------
Patch comitted (r3085), 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=863
------- Additional Comments From [EMAIL PROTECTED] 2007-10-04 18:44 -------
This is caused by a race condition that occurs when an application has already
received a close request and still gets enumerated in
today_task_manager_populate_tasks() to update the task list. When the function
then iterates over the enumerated windows the application might already have
finished shutting down, thereby making the window handle invalid.
For this reason, X reports a BadWindow error on the gdk_window_get_type_hint()
call for such a window.
Proposed bugfix follows :)
-Soeren
------- 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=863
------- Additional Comments From [EMAIL PROTECTED] 2007-10-04 18:46 -------
Created an attachment (id=337)
-->
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=337&action=view)
Proposed bugfix
------- 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=863
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2007-10-04 19:00 -------
Well done and thanks for the patch, committed in r3088
------- 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=908
Summary: Unexpected onscreen keyboard expose/collapse behavior in
openmoko-terminal2
Product: OpenMoko
Version: 2007.2
Platform: PC
OS/Version: All
Status: NEW
Severity: minor
Priority: P2
Component: openmoko-terminal
AssignedTo: [email protected]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
In the new openmoko-terminal2, exposing/collapsing the onscreen virtual keyboard
moves you around in the scrollback buffer.
Expected behavior: If your cursor is at the bottom of the screen with the
keyboard exposed, then collapsing the keyboard will expose more of the
scrollback buffer, the content will "slide" down to fill the space, and your
cursor will still be at the (new) bottom of the screen. Re-exposing the
keyboard will "slide" the content back up.
Observed behavior: Exposing the keyboard acts correctly, and causes everything
to move up the screen. But collapsing the keyboard does not -- the active
cursor position stays where it is, and blank space opens up in the window
underneath. Accordingly, repeatedly collapsing and exposing the keyboard will
push your prompt up the screen to the top.
This doesn't impair functionality as far as I can tell, but it's a user
interface quirk. For the record, the old (mrxvt) terminal behaves correctly.
------- 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=909
Summary: After accepting PIN the dialer is not closed.
Product: OpenMoko
Version: 2007.2
Platform: Neo1973
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: openmoko-dialer
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
------- 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=910
Summary: When a kernel ipkg is released, "ipkg upgrade" breaks
kernel modules
Product: OpenMoko
Version: 2007.2
Platform: Neo1973
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: kernel
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
Ipkg can't upgrade a kernel (it sits in its own partition), but it can upgrade
kernel modules (which are in the normal filesystem). So when somebody releases
a new kernel and modules, the new modules get loaded by "ipkg upgrade" and then
they don't work with the old kernel.
I flashed the 2007.2 release, then after getting my USB networking gatewayed
properly, did "ipkg update && ipkg upgrade". This installed new kernel modules
(and maybe tried to install a new kernel into the ordinary filesystem). This
broke my kernel modules (e.g. mounting vfat filesystems didn't work; the sound
stopped playing at reboot; etc) until I was able to figure out where to find the
new kernel and manually flash it into the kernel partition.
How to fix this? An obvious way would be to make the kernel ipkg install the
new kernel into the kernel's proper partition. Failing that, it may be possible
to circumvent the problem by administratively never releasing new incompatible
modules into a repository where "ipkg update" will install them for ordinary
naive users.
------- 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=884
------- Additional Comments From [EMAIL PROTECTED] 2007-10-04 21:32 -------
At Harald's request, I've logged the "kernel upgrade breaks modules" bug as
#910.
------- 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=666
------- Additional Comments From [EMAIL PROTECTED] 2007-10-05 03:46 -------
I assume that thanks to complicated legal/regulatory issues, a user-loadable GSM
modem firmware update is unlikely or difficult unless the modem has some kind of
cryptographic verification process or similar 'feature' for new images.
What's the story on the currently shipping GTA01 units? Is an eventual means to
upgrade them and fix this pretty serious bug likely?
------- 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=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=727
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=742
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=800
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=846
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=865
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=870
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=881
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=882
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=888
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
