The Diablo Bug Thread

[Bundyo]

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]

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]

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]

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]

It doesn't enable the hidden secret in the N810... I was hoping it would.

I want my built in coffee maker...

[Texrat]

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]

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]

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]

Ok :p

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

[Mara]

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]

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]

Ok :p

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

dpkg -r osso-email-old-ui

[qwerty12]

i don't want to remove it, just get it with a different name. give me a min...

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


[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]

Why keep it?

[qwerty12]

i want to keep it incase, removing ossoemail package will mess up osso-software-version pkg

[Bundyo]

It won't - the old package doesn't exist in Diablo.

[Mara]

I just realized that my canola does not work. I get this when starting from xterm:
~ $ 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]

My canola works. follow bundyo's instructions to symlink the libeet file.

[Bundyo]

I just realized that my canola does not work. I get this when starting from xterm:
~ $ 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/forums/showpost.php?p=179597&postcount=19

[Bundyo]

Added some bugs in the first post.

[GeneralAntilles]

The MicroB ITT bug has happened to me a few times. Creeps me out. . . .

[Bundyo]

So they did change some things on the engine.

[GeneralAntilles]

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]

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]

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]

1) No, maybe related to the hardware keyboard?
2) N810 specific, no problems with paste with virtual.

[yerga]

the 1 have happened to me only in the text entries here in ITT. It doesn't happen in other sites.

[Texrat]

I will try to reproduce the bugs mentioned so far and report them if so. Thanks guys!

[sjgadsby]

If any of you have a few moments to spare at some point, I'd love to know if bug # 2055 (https://bugs.maemo.org/show_bug.cgi?id=2055) is fixed in Diablo.

[maxilogan]

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]

If any of you have a few moments to spare at some point, I'd love to know if bug # 2055 (https://bugs.maemo.org/show_bug.cgi?id=2055) is fixed in Diablo.

I can't reproduce this, but it doesn't mean it's fixed.


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]

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]

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]

Initfs isn't a problem for me anymore ;)

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

[yerga]

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]

Some cleanup and updates in the first post.

[GeneralAntilles]

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]

Do you want me to put them up with the others?

[Mara]

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]

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...

[GeneralAntilles]

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

We could, but I wouldn't recommend it, as I might explode. :p I had the discussion with timeless a few months ago and it came down to that goddamn sonuva***** UI spec. . . .

Anybody who defines their homepage as about:blank obviously does so intentionally, so warning them about it everytime they open their browser is high stupidity.

[Mara]

Anybody who defines their homepage as about:blank obviously does so intentionally, so warning them about it everytime they open their browser is high stupidity.

That I can agree with you... :)

[GeneralAntilles]

OK, so I alerted timeless to bugs #2405 (https://bugs.maemo.org/buglist.cgi?quicksearch=2405) and #3179 (https://bugs.maemo.org/show_bug.cgi?id=3179) and they've been assigned.

I mentioned the fullscreen and itT bugs, too, so we'll see on those.

Also, bug #3061 (https://bugs.maemo.org/show_bug.cgi?id=3061) has been fixed, so you can file new bugs under the correct version, just be sure to include the build version (should be 3.2008.19-3 for most of you right now, confirm in Control Panel), as that's particularly critical for these frequently-updated pre-release builds.

[Texrat]

Ah, looks like I'm no longer needed.

[GeneralAntilles]

Ah, looks like I'm no longer needed.

Oh, don't get your panties in a bunch. :p ;)

Part of my desire for the 4.1 version now goes back to bug #630 (https://bugs.maemo.org/show_bug.cgi?id=630), in that I'd like to try and provide as little incentive as possible for developers and other Nokians to avoid Bugzilla. ;)

Besides, there are plenty of people who can't or wont use Bugzilla, and their bug reports still need to go to the right places (and Bugzilla bugs might also need some attention to be imported quickly before we hit release).

[tz1]

I still have to spend hours to just get the examples to just rebuild using "dpkg buildpackage" on Chinook (for the ARM target).

Would it be too much to ask to take a clean install of Ubuntu, Redhat, Suse, or whatever, and follow the instructions EXACTLY (or better yet, do a script) with all the apt-get update/upgrade whatevers and make sure all the hello-world applications will build from the .tgz files by just going into the directory and typing dpkg-buildpackage.

For the statusbar: http://maemo.org/development/documentation/how-tos/4-x/writing_hildon_desktop_plug-ins_for_maemo.html, I can't find a single app that will build properly (and worse, the hello-world-(statusbar/home/taskman) seems to want to delete libtool, then complains it can't find it). config.sub and config.guess are there, but I have to delete the symlinks and manually copy the files.

Nokia might complain about lack of interest, but I don't have weeks to devote to figuring out how to set up the build environment - which with the build system - autogen, automake, config*, then with the includes and libs for osso, hildon, dbus, gtk and all the other stuff is dependent on so many things EVERY ONE OF WHICH MUST BE CORRECT. And it never seems to be correct "out of the box". There is some hidden step, command, process, whatever. Some library or archive that needs a -dev which isn't obvious and requires a lot of searching, just to get to the next missing piece.

I don't have this problem with Ubuntu, or Fedora or most other distributions. There is usually a package manager with search that will show that an XYZ-dev exists.

If in order to build target binaries with osso, hildon, etc, I need to do apt-get install on a lot of files, or add archives, or whatever, please document it.

There isn't an official "on system" build, but I might go to that (I had to for my Zaurus).

Most here probably already have everything all set up correctly so it just works for you. But I can't read your mind, nor do I have your /scratchbox directory with everything perfectly configured. I can only follow instructions.

So PLEASE PLEASE PLEASE write up a HOWTO to set up the build environment for Diablo when it comes out. And I don't mind patching or hacking the hello world programs or doing post install updates or anything else as long as I know what is required and that at the end I can just download the tarball, unpack it, and type dpkg buildpackage and have it just work for all the examples at http://maemo.org/development/documentation/how-tos/4-x/ that link to tarballs? Even if there is a 4.1 howto full of patches it would make things so much easier.

[Benson]

I haven't done it yet, but you mentioned an on-tablet build environment, and that's the way I'm going. (I sorta had one, back in my broken Chinook install, but I didn't have room to install headers for many libraries.) I think it's the most suitable way, for light work. You might not want to compile KDE that way, but apps will probably do fine.

[Bundyo]

20-4: New additions are underlined.

[Mythic]

20-4: New additions are underlined.

I believe, it would be more readable if you created a new entry for new bugs and just edited the original post when a bug is fixed

[Mythic]

I have encountered an issue in backup/restore utility. (You are asked to create a backup before you perform an os update. This is a nice touch. And needed :-) as my n810 does not want to boot after update )

When you start creating a backup, there is a progress dialog which allows you to cancel the action. I clicked on the cancel: I got a confirmation window "blah blah was canceled blah blah", new a NEW backup file appeared in the list. It was quite a small file, so I believe it was incomple, likely corrupted. (Did not dare to do back up from it)

[gnuite]

Did anyone else have issues with "missing packages" during the OS update? It still let me continue, but I guess a lot of updates were left undone....

And it didn't ask me to back up.... ? (EDIT: Never mind, it asked me at the end of the update - wasn't expecting that.)

EDIT 2: The update "semi-bricked" my N810. I think I have to re-flash the old, pre-diablo kernel. Looks like the new kernel is still causing problems for the N810....

[qwerty12]

I had that problem, I canceled and tried again and it worked fine.

[Mythic]

Another small issue regarding application installer/application installation:
- when you click on a deb file in the web browser, the download dialog provide only option to save the deb file. It won't allow you to install the file right away. (The download dialog claims, that there is no associated application) However, when you click on the deb file in file manager, it will install just fine. I believe installation from webbrwoser was working before
-when you restore a back up and you had application list archived, it will start application installer and provide you a dialog "do you want to install all these applications", there is a status field in this dialog, where it claimed "will install 200MB" of applications. WTF? But explanation was simple, it summed size of all shown packages: canola ~24MB, canola-tuning ~24MB,... I found it fairly confusing at the first look

[disq]

Mythic: the first one is probably about web server mime types and not diablo itself.

[Mythic]

Mythic: the first one is probably about web server mime types and not diablo itself.

Then... garage download page has a bug :)

[Benson]

Here's one:

glibc6-dev is not installable, because it's newer than glibc6...

I think this relates to the SDK repos, actually, which I'm not supposed to use on the device; but I think it would cause the same problem in the SDK? Alas, I haven't the time to set up the SDK, and I have only a vague knowledge of the Debian repository & apt system, so I'm not entirely sure it is a bug. But it sure looks like it from here.

[qwerty12]

Well,

[sbox-CHINOOK_ARMEL08: ~/fvwm-2.5.26] > apt-get install libc6-dev
Reading package lists... Done
Building dependency tree... Done
libc6-dev is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

(I cant see no glibc6-dev so I used libc6-dev instead)

So I can cure your fears about scratchbox.
Also you are installing something in Diablo that is from a Chinook repo. If the libc6 is upgraded in diablo and you are installing from chinook repo, I can hardly say it's a Diablo bug.

I'd say just compile the same version of libc6 from source on the device. Running make and make install will get you the headers you need and be the same as a -dev package.

[Bundyo]

Looks like the MicroB big text bug is fixed in 21-4.

[Benson]

Well,
(I cant see no glibc6-dev so I used libc6-dev instead)Oops... Yes, it's libc. Evil gremlins...

Also you are installing something in Diablo that is from a Chinook repo. If the libc6 is upgraded in diablo and you are installing from chinook repo, I can hardly say it's a Diablo bug.You're right... That's it; the SDK is Chinook level. Thanks!

I'd say just compile the same version of libc6 from source on the device. Running make and make install will get you the headers you need and be the same as a -dev package.Probably a good solution, but I got things going on one of my Chinook versions... now I just chroot there to build stuff.

[Bundyo]

Looks like the MicroB big text bug is fixed in 21-4.

I spoke too soon - happened twice. Seems like happens only from time to time.

[Mythic]

I have enconutered two flash related problems:
- on http://www.novinky.cz there is a flash commercial. It dynamically flows as you scroll on the page. On the x axis it starts somewhere around 790 and it renders itself OVER the scrollbar. It makes the scrollbar almost impossible to use.
- On top of flash, there is a programming environment called Flex, which provides user interface elements like editboxes, listboxes, tab navigators etc. (Actually it is nice it works under diablo :-)) Flex provides an option for "password editbox". The password is remembered by hildon autocomplete like usual text.

[Bundyo]

I can't reproduce your scrollbar problem... in 22-8.

[Mythic]

I can't reproduce your scrollbar problem... in 22-8.

I run that one too. I did small testing on this problem, you have to have the browser full screen when you load the page (it renders somewhere from pixel 790) and you may need to scroll down little bit (by clicking on the scrollbar, I guess that what triggers java script which repositions the flash object)

And of course no-addblock and flash component enabled :)

[yerga]

The worst bug that I have found:

Sometimes opening pages in microb with 'open page in new window ', it opens a new 'blank' window. This window doesn't show anything. Whereas the page requested is showed in the first window.

If you press the back button in the browser (in the first window, the new window doesn't respond to anything), the browser generally is closed.

It doesn't happen often, but I always use the 'open in new window ' function, so it happens to me at least once a day.


And the bug (or feature; it could be a feature) that bothers me most:

Open a new window in microb, return to the previous window with the 'window selector' and in a few seconds the opened page recovers the focus and is showed.

I think that the last one already was happening in chinook but it was in lesser extent.

[Bundyo]

These probably are related to the controlling browserd daemon, which should be helping with the browser crashing (to not close all browser windows at once), but is also introducing some new weird behavior.

[Bundyo]

This one is fixed in 23-14:
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).

This one is introduced instead /#3248 (https://bugs.maemo.org/show_bug.cgi?id=3248)/:
Clicking on the address bar right after stylus/finger scroll opens the keyboard, then immediately closes it.

[Bundyo]

I'm struggling with a problem on my Diablo and i'm not sure if it is a bug or something i did...

I can use some help - please if you have Diablo installed tell me if you see the DUMMY connections in the connection manager select connection dialog?

Thank you in advance.

[Bundyo]

Ping...

Or everyone uninstalled Diablo already...?

[qwerty12]

I'm struggling with a problem on my Diablo and i'm not sure if it is a bug or something i did...

I can use some help - please if you have Diablo installed tell me if you see the DUMMY connections in the connection manager select connection dialog?

Thank you in advance.

I don't have one. These are usually added by you or 3rd party connection things (Bluetooth-pan, usblan etc) to trick ICD into thinking it's connected.

(you can add one manually with gconftool -s -t string /system/osso/connectivity/IAP/DEFAULT/type DUMMY)

[Benson]

Clarify what you mean...

Do you have a dummy connection established, and it's failing to show up?
Or are you seeing one you didn't expect?

I'm running Diablo; there's now a USB-networking Control-panel-applet; I only tried it once, as it pretty much doesn't work with XP (AFAICT), and that's the main place I'd be interested. So I either use WiFi -> Internet (I don't think it actually leaves campus, but it is directly connected) -> Ethernet -> Desktop, or copy files onto the SD and plug in for file transfer. But if I remember right, it added a dummy connection named USB or some such, which seemed not to work (by reason of XP).

I don't have one showing up right now, and I'm not having a ton of success with my USB-ethernet adapter -- it connects to ethernet, but the dummy connection doesn't show up. I haven't had a chance to investigate, or even to try it in Chinook (yet).

HTH.

[Bundyo]

Clarifying:

I have half a dozen DUMMY connections - at least 4 i did on purpose myself :) The other ones are USB and Maemo-PAN. I noticed the problem after i got to my home town and here i can only use BT connection to a PC and that's about the time when i discovered that my dummy connections are not showing up. Of course i can use an ad-hoc one for the purpose but it is eating through my battery like a hot knife through butter...

I've been here with chinook and i'm pretty sure that i've seen my share of DUMMY connections :)

[Benson]

Hmmm... Could be the same thing I'm experiencing with usb-ethernet; not sure yet.

[darethehair]

Another small issue regarding application installer/application installation:
- when you click on a deb file in the web browser, the download dialog provide only option to save the deb file. It won't allow you to install the file right away. (The download dialog claims, that there is no associated application) However, when you click on the deb file in file manager, it will install just fine. I believe installation from webbrwoser was working before


In fact, I distinctly recall in Chinook that I was able to simply 'click' on my 'deb' file links for software that I had created (in the browser), and the application manager would automatically open for an install i.e. I never had to 'pre-save' the file and re-open it with the file manager.

Also, now that I have to do a 'save-as' first, I noticed that the full file names are not being suggested as the 'save' name i.e. 'xxx.all.deb' is being prompted for a 'save name' of 'xxx.all'. :confused:

[bunanson]

omweather 0.20.4 crashed Diablo and the desktop failed to return, resulted in a reboot.


bun

[Bundyo]

omweather crashes Diablo every time on settings :)

[XL1200c]

The camera on my N800 does not flip to righ side up when rotated.

Where is the offical place to report bugs?

[Mara]

The camera on my N800 does not flip to righ side up when rotated.

Where is the offical place to report bugs?

You should go to http://bugs.maemo.org

Currently I do not have N800 (gave it to my sister in law...), but last time I checked it with Diablo it worked. However, it was few weeks ago with earlier Diablo beta, and fresh flash without restoring backup. Maybe try rebooting the tablet if that helps?

[jaiotu]

Also, now that I have to do a 'save-as' first, I noticed that the full file names are not being suggested as the 'save' name i.e. 'xxx.all.deb' is being prompted for a 'save name' of 'xxx.all'. :confused:

The only time I've ever had this problem, under Chinook, was when I was running low on disk space. Changing to Boot from SD fixed that problem. I haven't switched to Diablo yet... I'm waiting until everyone else tests it for me. :)

[Bundyo]

Can someone confirm this: when selecting a connection to connect and then cancel the connecting, the whole list of connections seems to persist in my select connection dialog and is not updated until i reboot the device?

EDIT: This happened to me only twice, not sure if these instructions are enough to recreate it.

[Matan]

This (wireless scanning not working, instead showing a constant list of "available networks", even while traveling over 100 Km) happened to me once. I don't think it was connected to selecting a connection to connect and then canceling while connecting. I don't know how to reproduce it.

[Bundyo]

To me it happened twice while searching for free wifi - connect, error, connect, error, cancel... Not easily reproducible though, but a quite nasty bug.

[qwerty12]

Can someone confirm this: when selecting a connection to connect and then cancel the connecting, the whole list of connections seems to persist in my select connection dialog and is not updated until i reboot the device?

EDIT: This happened to me only twice, not sure if these instructions are enough to recreate it.

Confirmed. Happens to me a lot.

[Benson]

I've seen the last-scanned network list persist (sometimes at least; perhaps always?) until the initial scan finishes. Presumably if some error during the initial scan was not handled right, it would stay indefinitely, but I haven't seen that yet. I assume you did wait for the initial scan to complete, which seems to take a while when there are no APs...

[Bundyo]

When do you get it qwerty?

@Benson: not waiting for it to complete every time, takes too long :)

[qwerty12]

When do you get it qwerty?

When I take my tablet out of offline mode using the select connection on the status bar, it can lag for a while so I go select connection and it's like I see "cached" wifi results.

[sungrove]

My home applets keep disappearing from my desktop. I have to keep going back and enabling them.

Neil

[Benson]

OK, if it only shows until the scan ends, then I'd say it's not a bug; it's a feature.

It allows you to immediately attempt to reconnect to any network that was there last time, without waiting for it to find that one.

[Bundyo]

You misunderstood. After the bug manifests itself, the cached connections are the only ones you get until you restart.

[daperl]

So PLEASE PLEASE PLEASE write up a HOWTO to set up the build environment for Diablo when it comes out. And I don't mind patching or hacking the hello world programs or doing post install updates or anything else as long as I know what is required and that at the end I can just download the tarball, unpack it, and type dpkg buildpackage and have it just work for all the examples at http://maemo.org/development/documentation/how-tos/4-x/ that link to tarballs? Even if there is a 4.1 howto full of patches it would make things so much easier.

I feel your pain, but there is hope. After a few hours of failing to properly incorporate the DIABLO targets into my CHINOOK scratchbox (more about that below), I decided to create a clean environment into /diablo/scratchbox. It's working fine but not perfect. Hello-world compiles out of the box, but the statusbar app didn't appear in the scratchbox statusbar. It does, however, appear in my tablet's statusbar after a package-and-install. I'm hacking away on it as we speak.

As for my hours waisted, the first indication that something was wrong with the use-the-old-scratchbox method was that af-sb-init.sh WASN'T EVEN IN THE DIABLO_ARMEL TARGET! It was in the DIABLO_X86 target. Huh!?...What!?..."I must have done something wrong". Nope. Well, maybe. But after clearing out both DIABLO targets and trying again I got the same result. And yeah, like I don't have my own sh*t to debug. Thus, I have a shiny new 2.6G /diablo/scratchbox.

Anyway, I followed the "strongly advised" method of http://repository.maemo.org/stable/diablo/INSTALL.txt and it didn't work. Fun.

[46jimbo]

My home applets keep disappearing from my desktop. I have to keep going back and enabling them.

Yes, this just happened to me today too!

[Bundyo]

@46jimbo: this is a hildon-desktop crash. Happens from bad plugins, low memory and such. OMWeather settings was a possible 'cause before the yesterday update.

Simple restart fixes it.

[silvermain]

The rss feed reader applet is showing duplicate article titles where the second one is actually a different article.

[anidel]

It would be cool if these bugs (at least the "confirmed" ones) would appear on the bugzilla and later posted back here (bugzilla #) so we can vote for them.

[Bundyo]

Yes, but we need to confirm them first. :) It is easier to confirm them here, since more people are reading.

[anidel]

Sure. After they have been confirmed by, say, two people, it should definitely go to bugzilla.

[Bundyo]

Yes, it will, but i can't say if the connections bug is confirm or possible to reproduce. And hildon-desktop crash isn't exactly the hildon-desktop's fault.

[Matan]

Wifi bug happened to me again.

This time I tried:

rmmod and insmod of the two wifi modules - did not change.

killall wlancond - did not change.

killall icd2 - scanning works, but could not connect to WPA network. Maybe if I tried only killing icd2, without the others it might work. Or maybe some other daemon (udhcpc, for example) needs also to be restarted.

[Bundyo]

Any thoughts how to reproduce it?

[cache]

Hello all,

Could somebody tell me how to show up DUMMY device in my connection manager? I've added it manually with:
gconftool -s -t string /system/osso/connectivity/IAP/DEFAULT/type DUMMY
but device doesn't show up :(
In connectivity settings > connections i see them, but cant connect to it

Any suggestions how to solve that ?

Thank you

[cache]

I forgot...

I am updating my IT (n810) to new Diablo OS

[Bundyo]

@cache:

https://bugs.maemo.org/show_bug.cgi?id=3306

[cache]

Thanks Bundyo,

Is it possible to connect to DUMMY interface without connection manager - through command line for example?

[Bundyo]

You can use WiFi Ad-Hoc, then drop the wlan, look here:

http://www.internettablettalk.com/forums/showthread.php?t=21263

[raulfcof]

I've a problem with "hildon-libs-|10n-public-engb", I intented install from de Aplication Manager in mode "red pill" and send me a error. And this is a package that is needed to install a lot of aplications, like a Pidgin, Vagalume, etc.

This problem starts when I upgrade to Diablo, in Chinook all was fine

Somebody help me ??? Please :(

I've a N810

[Texrat]

The rss feed reader applet is showing duplicate article titles where the second one is actually a different article.

Is that the BBC feed? I'm not seeing that problem on a newer, unreleased version of Diablo, so maybe the problem has been fixed.

[Texrat]

omweather 0.20.4 crashed Diablo and the desktop failed to return, resulted in a reboot.

bun

omweather 0.20.6 is working with the latest unreleased build.

[briand]

...and both of you should be a bit more adventurous and enable the testing repo long enough to install 0.21 -- you will be pleased. :)

[Texrat]

Thanks, Brian, I might just do that.