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 #1862: stop boot (Openmoko Public Trac)
2. Re: Openmoko Bug #1864: Keyboard needs to have a
non-predictive mode (Openmoko Public Trac)
3. Re: Openmoko Bug #1864: Keyboard needs to have a
non-predictive mode (Openmoko Public Trac)
4. Re: Openmoko Bug #1861: Installer administrative lock
(Openmoko Public Trac)
5. Openmoko Bug #1867: Dhclient is not working (Openmoko Public Trac)
6. Re: Openmoko Bug #1635: [Dialer] An outgoing call is not
established (connected) but goes from the dialing state directly
to disconnected (Openmoko Public Trac)
7. Re: Openmoko Bug #1863: illume-config package does not
provide the spanner/wrench (Openmoko Public Trac)
8. Re: Openmoko Bug #1864: Keyboard needs to have a
non-predictive mode (Openmoko Public Trac)
--- Begin Message ---
#1862: stop boot
----------------------------+-----------------------------------------------
Reporter: therippo | Owner: openmoko-devel
Type: defect | Status: new
Priority: high | Milestone:
Component: unknown | Version: GTA02v6
Severity: critical | Resolution:
Keywords: boot freeze | Blockedby:
Reproducible: | Blocking:
----------------------------+-----------------------------------------------
Comment(by therippo):
Replying to [comment:1 wendy_hung]:
> Did you use Om 2008.8 image?
sorry did not even have chance to apply anything to it..... :((
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1862#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1864: Keyboard needs to have a non-predictive mode
---------------------------------------------+------------------------------
Reporter: iknowjoseph | Owner: openmoko-devel
Type: defect | Status: closed
Priority: normal | Milestone:
Component: unknown | Version: Om2008.8
Severity: normal | Resolution: duplicate
Keywords: 2008.8, keyboard, predictive | Blockedby:
Reproducible: always | Blocking:
---------------------------------------------+------------------------------
Comment(by zecke):
Replying to [comment:10 iknowjoseph]:
> I am reluctant to reopen the bug if it's simply going to become another
"works for me" issue.
Well, we will have to find that out.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1864#comment:12>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1864: Keyboard needs to have a non-predictive mode
---------------------------------------------+------------------------------
Reporter: iknowjoseph | Owner: openmoko-devel
Type: defect | Status: closed
Priority: normal | Milestone:
Component: unknown | Version: Om2008.8
Severity: normal | Resolution: duplicate
Keywords: 2008.8, keyboard, predictive | Blockedby:
Reproducible: always | Blocking:
---------------------------------------------+------------------------------
Comment(by zecke):
Replying to [comment:11 Yorick]:
> Replying to [comment:9 zecke]:
> Are you sure it would not be usable Zecke? I used raster's Full Qwerty
keyboard, with my fingers and it works great! The keys are much closer
together on that keboard than on the predictive one...
No, I'm not. I'm just confident that we will get a new wave of reports if
we turn off the prediction. So the question is what is the issue and why
is someone asking to turn off prediction.
My answers to that are:
a) He is entering IP addresses, passwords and such. In that case
turning off prediction can make a lot sense. This would need solving in
two ways. Be able to set proper hints on the input (password, ip, no
prediction) and then the inputmethod can honor that. But that is a lot
more than just turning off prediction in the keyboard.
b) The prediction is not good enough. This is the case for non us
languages (as there are no wordbooks) and even the US dictionary does not
contain important words. The source of our dictionary is gutenberg (IIRC)
so stuff like www, yahoo, msn, or 4u (for you) and other SMS shortcuts do
not show up. In that case it is a matter of providing dictionaries for
other languages or that contain the word. E.g. you can install the
wordbook app and "train" www and your issue should be solved.
c) What do I forget? To ask why do we need to have a non-predictive
mode?
I'm still in the process of trying to understand why you want to disable
predictive mode and that disabling it is the best thing we can do.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1864#comment:13>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1861: Installer administrative lock
--------------------------+-------------------------------------------------
Reporter: Zoup | Owner: tick
Type: defect | Status: accepted
Priority: low | Milestone:
Component: Installer | Version: Om2008.8
Severity: minor | Resolution:
Keywords: | Blockedby:
Reproducible: always | Blocking:
--------------------------+-------------------------------------------------
Comment(by Zoup):
its as easy as :
opkg update on shell
and when its updating ,start installer , installer exist with 'wrong'
error message ( 'check your network' besides 'packages management locked'
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1861#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1867: Dhclient is not working
-----------------------------+----------------------------------------------
Reporter: Zoup | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version: Om2008.8
Severity: normal | Keywords: dhclient dhcp-client
Blockedby: | Reproducible:
Blocking: |
-----------------------------+----------------------------------------------
Dhclient Declines are Offers
Listening on LPF/eth0/00:12:cf:8e:fd:9d
Sending on LPF/eth0/00:12:cf:8e:fd:9d
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
DHCPOFFER from 192.168.0.110
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPACK from 192.168.0.110
DHCPDECLINE on eth0 to 255.255.255.255 port 67
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
DHCPOFFER from 192.168.0.110
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPACK from 192.168.0.110
...
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1867>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1635: [Dialer] An outgoing call is not established (connected) but goes from
the
dialing state directly to disconnected
------------------------+---------------------------------------------------
Reporter: regina_kim | Owner: zecke
Type: defect | Status: new
Priority: high | Milestone: Om2008.8
Component: Qtopia | Version:
Severity: critical | Resolution:
Keywords: must have | Blockedby:
Blocking: |
------------------------+---------------------------------------------------
Comment(by jmtorres):
Replying to [comment:9 jmtorres]:
> I have the same problem. Can I do some test or something to help?
Ups, I solved this problem chaging my SIM for a new one. It was more
related to ticket #666.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1635#comment:11>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1863: illume-config package does not provide the spanner/wrench
---------------------------+------------------------------------------------
Reporter: Yorick | Owner: raster
Type: defect | Status: closed
Priority: normal | Milestone: Om2008.8
Component: E - Illume | Version: GTA02v5
Severity: normal | Resolution: invalid
Keywords: | Blockedby:
Reproducible: always | Blocking:
---------------------------+------------------------------------------------
Comment(by Yorick):
Replying to [comment:1 raster]:
> the config in the updates removes the gadget as that is what was always
requested by om's design department. the spanner was never meant to be
available to the public and the whole config theme hack is just that - a
nasty hack on top of a release of code that was not ready (an earlier
release of illume was let out rather than the one i prepared), so you
won't be getting the spanner back, UNLESS you literally rm -rf ~/.e/ and
set up a new config of your own. right now asu.dev ships with 2 config
profiles - asu and illume. illume will get you what you want - edit
/etc/enlightenment/default_profile to change that (even this is a hack and
i will eventually make this redundant - but i suspect ASU (2008.08) will
keep using it. FSO should continue with the cleaner mechanism when i get
to fixing it all up.
>
> so as such - that spanner was not meant to be in the release and it's
simply a back door hack that doesn't work anymore. so i will have to close
this.
hmmmm...
so they removed some functionallity withouth giving us a way to get that
functionality back? What is the philosophy behind this?
And are you guys planning to add the double-click/top bar size/icon
size/framerate... conrig to the the settings app?
If not: why not?
If yes: why not wait with removing the spanner till it is implemented
somewhere else?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1863#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1864: Keyboard needs to have a non-predictive mode
---------------------------------------------+------------------------------
Reporter: iknowjoseph | Owner: openmoko-devel
Type: defect | Status: closed
Priority: normal | Milestone:
Component: unknown | Version: Om2008.8
Severity: normal | Resolution: duplicate
Keywords: 2008.8, keyboard, predictive | Blockedby:
Reproducible: always | Blocking:
---------------------------------------------+------------------------------
Comment(by Yorick):
Replying to [comment:13 zecke]:
> Replying to [comment:11 Yorick]:
> > Replying to [comment:9 zecke]:
>
> > Are you sure it would not be usable Zecke? I used raster's Full Qwerty
keyboard, with my fingers and it works great! The keys are much closer
together on that keboard than on the predictive one...
>
> No, I'm not. I'm just confident that we will get a new wave of reports
if we turn off the prediction. So the question is what is the issue and
why is someone asking to turn off prediction.
>
> My answers to that are:
> a) He is entering IP addresses, passwords and such. In that case
turning off prediction can make a lot sense. This would need solving in
two ways. Be able to set proper hints on the input (password, ip, no
prediction) and then the inputmethod can honor that. But that is a lot
more than just turning off prediction in the keyboard.
>
> b) The prediction is not good enough. This is the case for non us
languages (as there are no wordbooks) and even the US dictionary does not
contain important words. The source of our dictionary is gutenberg (IIRC)
so stuff like www, yahoo, msn, or 4u (for you) and other SMS shortcuts do
not show up. In that case it is a matter of providing dictionaries for
other languages or that contain the word. E.g. you can install the
wordbook app and "train" www and your issue should be solved.
>
> c) What do I forget? To ask why do we need to have a non-predictive
mode?
>
>
> I'm still in the process of trying to understand why you want to disable
predictive mode and that disabling it is the best thing we can do.
I understand what you are trying to say, but:
a) The question is not about turning prediction off, but _providing_ a way
to turn it off and on. Because I don't think it will be possible to use
those "hints on the input", because even under normal circumstances (like
in an SMS) where English-speaking people would like the predictive input
you will sometimes type names of people/places
b)in rasters keyboard one can already add his own wordbook
One of the *current* big flaws also is that there is no button to add a
word to the dictionary, so at this stage the predictive keyboard is not
really user-friendly.
We're not asking that you throw away predictive mode, but that we can
disable it and enable it whenever we want (just like on every other phone
I have ever used...). Especially since there is not yet a way to change
dictionaries (on this keyboard, on the one from raster there is) and no
way to let it learn new words.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1864#comment:14>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
