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. Re: Openmoko Bug #1158: Charging stops even while connected
(Openmoko Public Trac)
2. Openmoko Bug #1646: $PATH not correctly honoured by the
shell? (Openmoko Public Trac)
3. Re: Openmoko Bug #1158: Charging stops even while connected
(Openmoko Public Trac)
4. Re: Openmoko Bug #1605: "Messages": The application is badly
resized on start and does not show properly. (Openmoko Public Trac)
5. Re: Openmoko Bug #1549: [exposure] want to launch exposure
again while it is in the e-illume bar, need 5~10 sec
(Openmoko Public Trac)
6. Re: Openmoko Bug #1443: Dialing Through Speaker makes serious
noise (Openmoko Public Trac)
7. Re: Openmoko Bug #1568: Log in U-Boot through NOR Flash not
working (Openmoko Public Trac)
8. Openmoko Bug #1647: Dialer in ASU exits without actually
dialing the number (Openmoko Public Trac)
--- Begin Message ---
#1158: Charging stops even while connected
------------------------------------+---------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: openmoko-devel
Type: defect | Status: new
Priority: high | Milestone:
Component: openmoko-panel-battery | Version: unspecified
Severity: normal | Resolution:
Keywords: | Blocking:
Blockedby: |
------------------------------------+---------------------------------------
Comment(by thomasb):
I can confirm this. It happened to me several times in the last days while
leaving my FR plugged in over the night, with both current 2007.2 and
Qtopia images. U-Boot version is the originally installed "1.3.2-rc2
-dirty-moko12 (Apr 2 2008 - 09:31:05)".
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1158#comment:3>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1646: $PATH not correctly honoured by the shell?
---------------------+------------------------------------------------------
Reporter: Strolls | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version:
Severity: blocker | Keywords:
Blocking: | Blockedby:
---------------------+------------------------------------------------------
Using 2007.2 (default factory image, then `opkg update && opkg upgrade`)
$PATH does not seem to be honoured by the shell.
{{{
[EMAIL PROTECTED]:~# shutdown -fh now
-sh: shutdown: not found
[EMAIL PROTECTED]:~# find / -name shutdown
/usr/lib/opkg/alternatives/shutdown
/sbin/shutdown
[EMAIL PROTECTED]:~# echo $PATH
/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:
[EMAIL PROTECTED]:~# /sbin/shutdown -fh now
Broadcast message from root (pts/0) (Sun Jul 20 12:21:16 2008):
The system is going down for system halt NOW!
[EMAIL PROTECTED]:~# Connection to 192.168.0.202 closed by remote host.
Connection to 192.168.0.202 closed.
$
}}}
Maybe I'm doing something wrong here. I first noticed this running
/usr/bin/screen, and because that wipes the terminal when it starts it's a
bit difficult to copy & paste the output to document it. ;) The weird
thing is that screen seems to *intermittently* give this "-sh: screen: not
found" error - it seems like when my Freerunner is first powered up it
works fine (typing only `screen` or `screen -Rd`), then if I log out and
connect again after a day or so, I have to use the full path to screen.
This behaviour with `shutdown` seems consistent, however.
`
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1646>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1158: Charging stops even while connected
-----------------------------+----------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: openmoko-devel
Type: defect | Status: new
Priority: high | Milestone:
Component: System Software | Version: unspecified
Severity: normal | Resolution:
Keywords: | Blocking:
Blockedby: |
-----------------------------+----------------------------------------------
Changes (by zecke):
* component: openmoko-panel-battery => System Software
Comment:
Please try a more recent kernel.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1158#comment:4>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1605: "Messages": The application is badly resized on start and does not show
properly.
------------------------+---------------------------------------------------
Reporter: wendy_hung | Owner: zecke
Type: defect | Status: accepted
Priority: highest | Milestone: ASU
Component: Qtopia | Version:
Severity: blocker | Resolution:
Keywords: Messages | Blocking:
Blockedby: |
------------------------+---------------------------------------------------
Changes (by zecke):
* status: new => accepted
Comment:
I can reproduce this.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1605#comment:3>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1549: [exposure] want to launch exposure again while it is in the e-illume bar,
need 5~10 sec
------------------------+---------------------------------------------------
Reporter: wendy_hung | Owner: marek
Type: defect | Status: assigned
Priority: normal | Milestone: ASU
Component: E - Illume | Version:
Severity: normal | Resolution:
Keywords: must have | Blocking:
Blockedby: |
------------------------+---------------------------------------------------
Comment(by raster):
1. the bar. that is not in exposure's control. it is the same as a
"Taskbar" - it's a window manager list and it lists all windows - u select
one and e show/brings to the front and focuses the window. that works
reliably all the time for all apps. (it could be that exposure is not
RESPONDING and not REDRAWING its UI). you know that the window is up but
not responding by doing this:
1. start from home
2. select "Exposure" from the illume bar
3. try click on the visible "icons". if they dont respond - it's just
framebuffer garbage you have and exposure is up, but not responding.
2. as for activate() every time i try run exposure while it's already
running (ie run from launcher), it NEVER comes oup. it's a 100% failure
rate for me. i wrote a test app in c that uses the ecore_evas_activate()
call and it works - 100% of the time.
i think it's python and/or the way you use it. first - threads. i have no
idea how python does this, but i'd say remove the threads. EFL is NOT
threadsafe. even if its not real "pthreads" under python's threads , you
are asking for trouble and "bizarre bugs" that some can reproduce, others
can not and only happen sometimes or are erratic. from what i see in app-
launcherd.py your problem probably is that the client thread is running
the main loop, BUT yu call the focus() call FROM the app-launcherd main
thread/loop. this alone would explain it as you are just lucky you don't
crash. that call will write data to the FD that is your unix socket
connection to X - and X buffers these - xlib does, and until the mainloop
of the client thread does something to somehow force the buffer to flush -
which it may never do if no timers or anything are active, the command
will never be sent to X.
so as such... you'll fix the problem if you remove threading.
:)
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1549#comment:8>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1443: Dialing Through Speaker makes serious noise
------------------------+---------------------------------------------------
Reporter: regina_kim | Owner: graeme
Type: defect | Status: assigned
Priority: high | Milestone: ASU
Component: Qtopia | Version: GTA02v5
Severity: major | Resolution:
Keywords: | Blocking: 1640
Blockedby: |
------------------------+---------------------------------------------------
Comment(by zecke):
Thanks, I added the AT command to Qtopia. Let us see if that makes a
difference.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1443#comment:8>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1568: Log in U-Boot through NOR Flash not working
---------------------+------------------------------------------------------
Reporter: gen | Owner: openmoko-devel
Type: defect | Status: in_testing
Priority: normal | Milestone:
Component: unknown | Version:
Severity: normal | Resolution:
Keywords: | Blocking:
Blockedby: |
---------------------+------------------------------------------------------
Comment(by werner):
An update: we found a flaw in the production testing process that can let
devices with an incorrect NOR content pass. Don't know yet what caused the
NOR to be incorrect in the first place, though.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1568#comment:5>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1647: Dialer in ASU exits without actually dialing the number
------------------------+---------------------------------------------------
Reporter: kenrestivo | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version:
Severity: normal | Keywords:
Blocking: | Blockedby:
------------------------+---------------------------------------------------
In the latest ASU (I opkg update; opkg upgraded yesterday), the dialer
exits before dialing a number.
I type in the number or pick it from the contacts db, it says dialing,
puts up the "End Call" and other status buttons, then it just exits before
actually making the call.
This is, unfortunately, intermittent. I've noticed that it happens when
the phone is running really really slow (like, several seconds to update
the display), so it's possible there's something racy going on. It only
seems to exhibit this problem when the phone is running very slowly.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1647>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
