| 1   2     3   | Next
maemo.org - Talk
Page 1 of 3
Show 40 post(s) from this thread on one page

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Development (https://talk.maemo.org/forumdisplay.php?f=13)
-   -   The Diablo Bug Thread (https://talk.maemo.org/showthread.php?t=19979)

Bundyo 2008-05-11 18:28
The Diablo Bug Thread
 
Who will be first?

Mine:

Bugs:

Desktop:
- Google is missing in the search bar /fixed/
MicroB:
- Also present in Chinook - pressing the back/forward button not always go back (no indication that any command was issued too), it even happens on long-press after choosing even older page (managed to pin down this one - it can always be reproduced right after scrolling with stylus/finger) - /fixed in 23-14, however, look at the next/.
- Clicking on the address bar right after stylus/finger scroll opens the keyboard, then immediately closes it /introduced in 23-14/.
- Fullscreen change doesn't work while the page is loading. Looks like MicroB loses focus. If you first click somewhere in the window - then it works - /i believe this one is fixed - it is hard to reproduce, so i'm not sure/.
- Sometimes, when opening ITT in Diablo MicroB, i get this screen:

http://bundyo.org/maemo/microb_broken.png

After some reloads, i get this screen:

http://bundyo.org/maemo/microb_normal.png

Never happened before Diablo. /Not fixed in 21-4/
- New one as of 20-4: hard to describe (maybe ITT bug):
* Behavior in Chinook: Simple search in ITT (shown with js div with editbox and button) doesn't correctly bring up the virtual keyboard, only fullscreen keyboard can be used.
* Behavior in Diablo 20-4: The virtual keyboard is correctly brought up, but the js shown div closes as if loses focus. Fullscreen keyboard is also unusable due to this behavioir.

Modest /all messaging/:
- When the new message icon and the led are blinking, CPU usage is 30%. Seems too much for something possibly working for hours (don't know if it takes so much while sleeping)
PDF Viewer:
- In fullscreen mode, the buttons for page change are too close to the borders and harder to press, maybe the image viewer button margins will be more appropriate.
RCCOM:
- Invisible state is still not working, goes to Away. /old Chinook one/

Feature Requests:

Application Manager:
- The refresh button to be enabled on the main screen, not just in update and install.
Calculator:
- Fullscreen mode.
- Other calculator modes: Scientific at least.
Contacts:
- Some way to update contact info of a single or multiple contacts. Preferably on right click.

qwerty12 2008-05-11 18:31
Re: The Diablo Bug Thread
 
Initfs provided in diablo is too big to flash on n800 and once stripped of crap, using it sends n800 into reboot loop- Hence me creating my own off chinook one.

Texrat 2008-05-11 18:38
Re: The Diablo Bug Thread
 
Quote:
Originally Posted by qwerty12 (Post 180450)
Initfs provided in diablo is too big to flash on n800 and once stripped of crap, using it sends n800 into reboot loop- Hence me creating my own off chinook one.
FYI, that won't be one I'll be reporting-- there will be release packages supporting N800, N810 and N810W without need for modification.

qwerty12 2008-05-11 18:45
Re: The Diablo Bug Thread
 
Quote:
Originally Posted by Texrat (Post 180454)
FYI, that won't be one I'll be reporting-- there will be release packages supporting N800, N810 and N810W without need for modification.
cool, any idea why nokia made it impossible to flash in this version?

From what I see, n810w has bigger initfs but nokia should have thought it wouldn't flash on n800 and n810 :/

Aisu 2008-05-11 18:45
Re: The Diablo Bug Thread
 
It doesn't enable the hidden secret in the N810... I was hoping it would.

I want my built in coffee maker...

Texrat 2008-05-11 18:56
Re: The Diablo Bug Thread
 
Quote:
Originally Posted by qwerty12 (Post 180460)
cool, any idea why nokia made it impossible to flash in this version?

From what I see, n810w has bigger initfs but nokia should have thought it wouldn't flash on n800 and n810 :/
You guys are scraping up stuff that isn't formally released.

Bundyo 2008-05-11 18:58
Re: The Diablo Bug Thread
 
Quote:
Originally Posted by Texrat (Post 180463)
You guys are scraping up stuff that isn't formally released.
Yes, we don't even know if this initfs was intended for N800.

Benson 2008-05-11 18:59
Re: The Diablo Bug Thread
 
Quote:
Originally Posted by qwerty12 (Post 180460)
cool, any idea why nokia made it impossible to flash in this version?

From what I see, n810w has bigger initfs but nokia should have thought it wouldn't flash on n800 and n810 :/
They probably have thought of that; but why maintain two versions the whole way through development, when you know you can just rip the extra stuff out after you've gotting it working right?

qwerty12 2008-05-11 19:04
Re: The Diablo Bug Thread
 
Ok :p

Here's an annoyance, we have 2 E-Mail's in the menu, call one modest :p

Mara 2008-05-11 19:07
Re: The Diablo Bug Thread
 
Quote:
Originally Posted by qwerty12 (Post 180469)
Ok :p

Here's an annoyance, we have 2 E-Mail's in the menu, call one modest :p
We? Who we? I do not have... :p

(But then again I did flash to Diablo with the way it supposed to happen once Diablo is released.)

qwerty12 2008-05-11 19:11
Re: The Diablo Bug Thread
 
Quote:
Originally Posted by Mara (Post 180473)
We? Who we? I do not have... :p

(But then again I did flash to Diablo with the way it supposed to happen once Diablo is released.)
:P

Hehe I checked the .application file, it seems to be pointing to the same locale file as ossoemail.

Bundyo 2008-05-11 19:14
Re: The Diablo Bug Thread
 
Quote:
Originally Posted by qwerty12 (Post 180469)
Ok :p

Here's an annoyance, we have 2 E-Mail's in the menu, call one modest :p
Code:
dpkg -r osso-email-old-ui

qwerty12 2008-05-11 19:17
Re: The Diablo Bug Thread
 
i don't want to remove it, just get it with a different name. give me a min...

/usr/share/applications/hildon/modest.desktop

Code:
[Desktop Entry]
Encoding=UTF-8
Version=1.0
Type=Application
Name=Modest
Comment=mcen_ap_name_thumb
Exec=/usr/bin/modest

X-Osso-Service=com.nokia.modest
X-Osso-Type=application/x-executable

Icon=qgn_list_messagin
X-Window-Icon=qgn_list_messagin
X-Window-Icon-Dimmed=qgn_list_messagin

StartupWMClass=modest

MimeType=application/x-executable;

#
# below to be activated when dbus/send to functionality works
#
X-Osso-URI-Actions=mailto;
[X-Osso-URI-Action Handler mailto]
Method=MailTo
Name=uri_link_compose_email
TranslationDomain=osso-uri

Benson 2008-05-11 19:18
Re: The Diablo Bug Thread
 
Why keep it?

qwerty12 2008-05-11 19:23
Re: The Diablo Bug Thread
 
i want to keep it incase, removing ossoemail package will mess up osso-software-version pkg

Bundyo 2008-05-11 19:31
Re: The Diablo Bug Thread
 
It won't - the old package doesn't exist in Diablo.

Mara 2008-05-11 19:56
Re: The Diablo Bug Thread
 
I just realized that my canola does not work. I get this when starting from xterm:
Code:
~ $ canola
Traceback (most recent call last):
  File "/usr/bin/canola", line 19, in <module>
    import ecore.evas
  File "/usr/lib/python2.5/site-packages/ecore/evas/__init__.py", line 3, in <module>
ImportError: libeet.so.0: cannot open shared object file: No such file or directory
~ $
EDIT: Corrected according to the two posts below. Thanks guys! :)

qwerty12 2008-05-11 20:01
Re: The Diablo Bug Thread
 
My canola works. follow bundyo's instructions to symlink the libeet file.

Bundyo 2008-05-11 20:03
Re: The Diablo Bug Thread
 
Quote:
Originally Posted by Mara (Post 180491)
I just realized that my canola does not work. I get this when starting from xterm:
Code:
~ $ canola
Traceback (most recent call last):
  File "/usr/bin/canola", line 19, in <module>
    import ecore.evas
  File "/usr/lib/python2.5/site-packages/ecore/evas/__init__.py", line 3, in <module>
ImportError: libeet.so.0: cannot open shared object file: No such file or directory
~ $
http://www.internettablettalk.com/fo...7&postcount=19

Bundyo 2008-05-11 20:16
Re: The Diablo Bug Thread
 
Added some bugs in the first post.

GeneralAntilles 2008-05-11 20:23
Re: The Diablo Bug Thread
 
The MicroB ITT bug has happened to me a few times. Creeps me out. . . .

Bundyo 2008-05-11 20:23
Re: The Diablo Bug Thread
 
So they did change some things on the engine.

GeneralAntilles 2008-05-11 20:27
Re: The Diablo Bug Thread
 
Quote:
Originally Posted by Bundyo (Post 180508)
So they did change some things on the engine.
Of course, konttori's js benchmarks should've indicated as much. ;) Just because it hasn't merged with the most recent trunk doesn't mean they haven't done any work on it.

yerga 2008-05-11 20:50
Re: The Diablo Bug Thread
 
I have found two bugs:

1) In microb writing with the virtual keyboard, when pressing the back key, it delete the last character (as it should) but it also hide the virtual keyboard. It happen in ITT.

2) Copying a text in Notes app with the copy menu or with Ctrl+C, and pasting it in microb with the physical keyboard (Ctrl+V), the pasted text is doubled.

Can you reproduce these?

Mara 2008-05-11 20:54
Re: The Diablo Bug Thread
 
Quote:
Originally Posted by yerga (Post 180518)
I have found two bugs:

1) In microb writing with the virtual keyboard, when pressing the back key, it delete the last character (as it should) but it also hide the virtual keyboard. It happen in ITT.

2) Copying a text in Notes app with the copy menu or with Ctrl+C, and pasting it in microb with the physical keyboard (Ctrl+V), the pasted text is doubled.

Can you reproduce these?
Looks like I did the 2).

Just few posts before I cut from Xterm and pasted into Microb browser using Ctrl+V, and was puzzled that why my selected text was pasted twice... :confused: Now I know it was a bug and not me... :)

Bundyo 2008-05-11 20:56
Re: The Diablo Bug Thread
 
1) No, maybe related to the hardware keyboard?
2) N810 specific, no problems with paste with virtual.

yerga 2008-05-11 21:01
Re: The Diablo Bug Thread
 
the 1 have happened to me only in the text entries here in ITT. It doesn't happen in other sites.

Texrat 2008-05-12 12:33
Re: The Diablo Bug Thread
 
I will try to reproduce the bugs mentioned so far and report them if so. Thanks guys!

sjgadsby 2008-05-12 12:46
Re: The Diablo Bug Thread
 
If any of you have a few moments to spare at some point, I'd love to know if bug # 2055 is fixed in Diablo.

maxilogan 2008-05-12 12:53
Re: The Diablo Bug Thread
 
No one's talking about one of the most annoying bugs of Chinook (for me at least..): double and gost taps.

Has this been resolved?! :confused:

yerga 2008-05-12 14:14
Re: The Diablo Bug Thread
 
Quote:
Originally Posted by sjgadsby (Post 180729)
If any of you have a few moments to spare at some point, I'd love to know if bug # 2055 is fixed in Diablo.
I can't reproduce this, but it doesn't mean it's fixed.

Quote:
Originally Posted by maxilogan
No one's talking about one of the most annoying bugs of Chinook (for me at least..): double and gost taps.
In two days of use, I haven't seen the double taps bug, so it could be fixed.

Benson 2008-05-12 14:19
Re: The Diablo Bug Thread
 
If you can't reproduce it, I bet it's fixed. At least in my experience, it always happens. (sjgadsby refers to having to click somewhere else, but in my experience, it doesn't matter.)

Bundyo 2008-05-12 15:29
Re: The Diablo Bug Thread
 
However the random click bug is still there, good news is that it has happened only once in two days which i say is a much lesser rate :)

qwerty12 2008-05-12 17:04
Re: The Diablo Bug Thread
 
Initfs isn't a problem for me anymore ;)

I made working image. One thing though, mediastreamer is not installable from diablo maemo repo.

yerga 2008-05-12 19:11
Re: The Diablo Bug Thread
 
Quote:
Originally Posted by qwerty12 (Post 180805)
One thing though, mediastreamer is not installable from diablo maemo repo.
Yes, I noted it too. I unpacked the package to / and it works well.

Bundyo 2008-05-13 15:19
Re: The Diablo Bug Thread
 
Some cleanup and updates in the first post.

GeneralAntilles 2008-05-13 23:33
Re: The Diablo Bug Thread
 
How about the fact that pressing the dpad on the default homepage takes you to google.com instead of bring up the fullscreen keyboard, then continues to take you to google.com again after you press center dpad with the search box highlighted on google.com. *sigh* This one has gotten worse since Chinook in this build. . . .

Or, what about the browser warning you that "No homepage is defined" when the homepage is defined as about:blank.

Bundyo 2008-05-13 23:43
Re: The Diablo Bug Thread
 
Do you want me to put them up with the others?

Mara 2008-05-13 23:52
Re: The Diablo Bug Thread
 
Quote:
Originally Posted by GeneralAntilles (Post 181297)
How about the fact that pressing the dpad on the default homepage takes you to google.com instead of bring up the fullscreen keyboard, then continues to take you to google.com again after you press center dpad with the search box highlighted on google.com. *sigh* This one has gotten worse since Chinook in this build. . . .

Or, what about the browser warning you that "No homepage is defined" when the homepage is defined as about:blank.
The first one seem to affect only N800. On N810 the center key behaves like <enter>, as it should.

Second one I confirmed too. (But about:blank is not really any web page... so we could arque about that... :rolleyes:)

Benson 2008-05-13 23:56
Re: The Diablo Bug Thread
 
Sounds like work on a fix from here; Enter should be Enter, not bring-up-keyboard. IDK, but it sounds like they changed what brings up the keyboard to something else, but didn't get the hardware mapping done yet? Maybe...


| 1   2     3   | Next
All times are GMT. The time now is 06:57.
Page 1 of 3
Show 40 post(s) from this thread on one page

vBulletin® Version 3.8.8