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. Openmoko Bug #1722: [GSM] taking signal is too slow
(Openmoko Public Trac)
2. Re: Openmoko Bug #1714: Mediaplayer sometimes does not start
up. (Openmoko Public Trac)
3. Re: Openmoko Bug #1682: Neo turns off before reaching X
(Openmoko Public Trac)
4. Re: Openmoko Bug #1714: Mediaplayer sometimes does not start
up. (Openmoko Public Trac)
5. Re: Openmoko Bug #1714: Mediaplayer sometimes does not start
up. (Openmoko Public Trac)
6. Openmoko Bug #1723: Hanging up with power button causes
issues (Openmoko Public Trac)
7. Openmoko Bug #1724: [FSO] cannot input number or * or # while
in communication (Openmoko Public Trac)
8. Re: Openmoko Bug #1650: Mokomakefile: gtk+/gtk+-fastscaling
conflicts (Openmoko Public Trac)
--- Begin Message ---
#1722: [GSM] taking signal is too slow
-----------------------------+----------------------------------------------
Reporter: wendy_hung | Owner: zecke
Type: defect | Status: new
Priority: highest | Milestone: ASU
Component: System Software | Version:
Severity: blocker | Keywords:
Blocking: | Blockedby:
-----------------------------+----------------------------------------------
description:
after boot the device (turn on the device), it can not get the signal
fast, usually need one or two more minutes to get signal.(total need more
than 5 minutes since you press the power button)
During this time you can use the other applications, only making phone
calls will have error message to warning you "Can not make a phone call"
latest image that we use is:
kernel:20080723-asu.stable-uImage.bin
root file system:20080801-asu.stable-rootfs.jffs2
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1722>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1714: Mediaplayer sometimes does not start up.
---------------------+------------------------------------------------------
Reporter: hedora | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version:
Severity: major | Resolution:
Keywords: | Blocking:
Blockedby: |
---------------------+------------------------------------------------------
Comment(by hedora):
The patch doesn't work after all. The locking code is OK, but the lock is
set before the sigusr1 signal handler is installed.
Other processes see the lock, signal us with sigusr1 to tell us to raise
our window. Then we crash. The fix is to install a signal handler before
setting the lock.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1714#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1682: Neo turns off before reaching X
-----------------------------+----------------------------------------------
Reporter: queen6 | Owner: openmoko-kernel
Type: defect | Status: new
Priority: high | Milestone: ASU
Component: System Software | Version: GTA02v5
Severity: normal | Resolution:
Keywords: | Blocking:
Blockedby: |
-----------------------------+----------------------------------------------
Comment(by queen6):
Hi Werner,
Interesting theory, but doesn't really explain why it worked before. It
also work fine on different image (tested on FSO Milestone2), so I dont
think this is the case here. On FSO image I can remove battery at any
point (just after u-boot phase, during boot on X).
I've built ASU image myself (from org.openmoko.dev repo) and I could
reproduce this issue.
All tests were done in the same hardware (laptop+FR+cable).
Could any of you please answer my previous question about charging? I
would like to know when FR is actually charging.
Thanks!
Rob
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1682#comment:7>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1714: Mediaplayer sometimes does not start up.
---------------------+------------------------------------------------------
Reporter: hedora | Owner: Abraxa
Type: defect | Status: accepted
Priority: normal | Milestone:
Component: unknown | Version:
Severity: major | Resolution:
Keywords: | Blocking:
Blockedby: |
---------------------+------------------------------------------------------
Changes (by Abraxa):
* owner: openmoko-devel => Abraxa
* status: new => accepted
Comment:
Thanks for the patch, I'll include it in the SHR fork as 2007.2 itself is
unmaintained.
Out of curiosity I would be grateful however if you'd let me know in some
way (mail, IRC, trac, whatever) how the old locking code had "other bugs"
aside from the racing condition you mentioned. I wrote it without knowing
any better so I'd be happy to learn why my code was suboptimal so I can
avoid these kinds of mistakes in the future.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1714#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1714: Mediaplayer sometimes does not start up.
---------------------+------------------------------------------------------
Reporter: hedora | Owner: Abraxa
Type: defect | Status: accepted
Priority: normal | Milestone:
Component: unknown | Version:
Severity: major | Resolution:
Keywords: | Blocking:
Blockedby: |
---------------------+------------------------------------------------------
Comment(by hedora):
Here's a patch that (might) actually work.
Here are two bugs that I found:
- sigusr1 sent before signal handler installed
- can spuriously send sigusr1 to unsuspecting programs that reused a
stale pid, inadvertently killing them.
You could probably backport both those fixes to your locking code and
produce a much smaller patch. (I'm considering doing this myself...)
I didn't look very carefully at the code; I'm not too familiar with
flock(), and there was a comment suggesting it needed to be revamped. So,
I blamed it, reimplemented it, and then found the real bug.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1714#comment:3>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1723: Hanging up with power button causes issues
-----------------------+----------------------------------------------------
Reporter: reaper527 | Owner: openmoko-devel
Type: defect | Status: new
Priority: high | Milestone: OM-2007.2
Component: unknown | Version: unspecified
Severity: normal | Keywords:
Blocking: | Blockedby:
-----------------------+----------------------------------------------------
If I am in a call, and i hang up by pushing the power button (instead of
the hang up button on the touch screen), the following happens.
1. the call shows up as a missed call in the call log
2. the call closes, then the phone is left in a state that it is unable to
lock.
at first, i wasn't sure what was causing the openmoko to not be able to
lock, but i'm 90% sure this will reproduce the symptom every time.
once that happens, if i hold the power button and say lock, it goes to the
wallpaper and nothing happens. if i let the phone sit for a little while
(its set to dim and lock), it dims but doesn't lock.
if i do /etc/init.d/xserver-nodm restart, it drops to the text screen, and
hangs there.
doing a full reboot of the phone fixes the problem.
i'm running the current dailybuild (i do opkg update/opkg upgrade every
day.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1723>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1724: [FSO] cannot input number or * or # while in communication
----------------------+-----------------------------------------------------
Reporter: feydreva | Owner: openmoko-devel
Type: defect | Status: new
Priority: high | Milestone: FSO
Component: unknown | Version:
Severity: major | Keywords: dialer
Blocking: | Blockedby:
----------------------+-----------------------------------------------------
Hello,
for example, when I access my voice-mail, i need to enter 4 numbers + #,
and with the current dialer, I cannot do it, and so, i cannot access my
voice-mail.
I try with the keyboard, but it doesn't seems to sent the data...
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1724>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1650: Mokomakefile: gtk+/gtk+-fastscaling conflicts
--------------------+-------------------------------------------------------
Reporter: gcasse | Owner: julian_chu
Type: defect | Status: new
Priority: high | Milestone:
Component: Distro | Version:
Severity: normal | Resolution:
Keywords: | Blocking:
Blockedby: |
--------------------+-------------------------------------------------------
Changes (by olberger):
* priority: normal => high
Comment:
Doing an opkg update; opkg upgrade tonight, I get the same errors :
Collected errors:
* Package gtk+ wants to install file /usr/lib/libgtk-x11-2.0.so.0
But that file is already provided by package * gtk+-fastscaling
* Package gtk+ wants to install file /usr/lib/libgdk_pixbuf_xlib-2.0.so.0
But that file is already provided by package * gtk+-fastscaling
* Package gtk+ wants to install file /usr/lib/libgdk_pixbuf-2.0.so.0
But that file is already provided by package * gtk+-fastscaling
* Package gtk+ wants to install file
/usr/lib/gtk-2.0/2.10.0/engines/libpixmap.so
But that file is already provided by package * gtk+-fastscaling
* Package gtk+ wants to install file /usr/lib/libgdk-x11-2.0.so.0
But that file is already provided by package * gtk+-fastscaling
* Package gtk+ wants to install file /usr/bin/gdk-pixbuf-query-loaders
But that file is already provided by package * gtk+-fastscaling
etc.
As this looked like some dev/building problem, it may have not been
noticed... but looks like it happpens not only on dev side but will annoy
users too.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1650#comment:3>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
