Re: Upgrade to PR 1.2 gone wrong
Alejandro López listas@googlemail.com writes: operation). When the moment for the reboot came, the problems started: my N900 would start booting never asking for the security code, and when starting to show the desktop, it would reboot; and the loop started again. It was impossible to power it off except by removing the battery. I had the same experience, with the reboot loop at the same point, after doing apt-get dist-upgrade (which I did because the app manager was telling me I needed to use the proprietary Windows Nokia software suite). I ended up flashing it, and restoring my settings/apps from backup, and it seems to be working fine now. -- -John Sullivan -http://wjsullivan.net -GPG Key: AE8600B6 ___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users
Re: Upgrade to PR 1.2 gone wrong
Hi, ext John Sullivan wrote: Alejandro López listas@googlemail.com writes: operation). When the moment for the reboot came, the problems started: my N900 would start booting never asking for the security code, and when starting to show the desktop, it would reboot; and the loop started again. It was impossible to power it off except by removing the battery. I had the same experience, with the reboot loop at the same point, after doing apt-get dist-upgrade (which I did because the app manager was telling me I needed to use the proprietary Windows Nokia software suite). Did you have any packages installed which stupidly declare exact version dependencies to other packages? For example several of the games in Extras seem to be declaring exact version dependency to SGX driver. Which of course causes a conflict on SSU which contains a new improved SGX driver. IMHO packages with exact version dependencies to anything that doesn't come from the same source package should just be rejected from Extras. Could somebody looking after Extras fix this so that we don't get such bad packages at least for PR1.2? I ended up flashing it, and restoring my settings/apps from backup, and it seems to be working fine now. - Eero ___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users
Re: PR 1.2 update and messaging
ext Aldon Hynes aldon.hy...@orient-lodge.com writes: Okay... I've finally gotten PR 1.2 running and just about everything seems to be working, with one exception. My SMS messages are not showing up in Converstations. I can send and receive new SMS messages, but they do not show up in conversations. I have the same problem and will try to get to the bottom of this today. For me, incoming text messages are displayed, but they are not stored permanently. Also, the Recent calls list remains empty. Checking the database /home/user/.rtcom-eventlogger/el-v1.db or el.db with sqlite3 shows the old messages in the database. Yes, and el-v1.db and el.db are _exactly_ the same size for me, so maybe some schema conversion failed and el.db is now in the wrong format or something and rtcom refuses to both read and write it. That's a very very uneducated guess of course. I guess I have to read the rtcom sources or hunt down the developers here... :) ___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users
Re: PR 1.2 update over the air
Hi, ext Ove Nordstrom wrote: 2010/5/26 Xavier Bestel xavier.bes...@free.frmailto:xavier.bes...@free.fr On Wed, 2010-05-26 at 17:59 +0300, Marius Gedminas wrote: As usual, I didn't have enough free space on the rootfs, but the old trick of disabling all application catalogues to free up the space normally taken by apt package list caches worked fine. The update felt rather slow (maybe ~30 minutes) One of the slow things on SSU is optifying of the rootfs content. If one instead flashes the rootfs, optifying happens on bootup. and a bit scary (I was afraid to plug in the USB cable to recharge during the process, probably without any good reason). All my contact icons on the desktop had disappeared after the first reboot into the new OS. They reappeared after the second boot. Many of my contacts are duplicated now (apparently this has something to do with Facebook chat support; I remember seeing a blog post about it). The Extras Devel repository didn't work (404 not found errors) after I reenabled it, until I changed the Distribution field to fremantle (it was blank before). AFAICS everything else works fine. Did the same. It went rather well, but curiously when the device decided to reboot by itself, when showing the blue-on-white Nokia logo, there was also a sentence like Device malfunction, will stop in 10s in green letters. MALF sounds serious, it shouldn't happen with properly working device HW (unless you had an issue on updating the bootloader/kernel/CMT or there was some extraordinary condition like too hot device temperature, badly connnected battery etc). I re-powered it on and it seems it's all OK now. Battery life hasn't improved much, it seems. If you get MALF again on boot, I would suggest reflashing the device. - Eero ___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users
Re: PR 1.2 update over the air
Hi, On Thu, 2010-05-27 at 10:32 +0300, Eero Tamminen wrote: Did the same. It went rather well, but curiously when the device decided to reboot by itself, when showing the blue-on-white Nokia logo, there was also a sentence like Device malfunction, will stop in 10s in green letters. MALF sounds serious, it shouldn't happen with properly working device HW (unless you had an issue on updating the bootloader/kernel/CMT or there was some extraordinary condition like too hot device temperature, badly connnected battery etc). Nothing special here, the device was on battery when doing the update, not specially hot. I re-powered it on and it seems it's all OK now. Battery life hasn't improved much, it seems. If you get MALF again on boot, I would suggest reflashing the device. I didn't get MALF again, but something strange instead: yesterday the device went dead (flat battery after 9 hours, as usual), and it didn't want to charge with the cheap USB cable I have at work (again as usual, it seems it only charges when the battery is as at least half-full). But at home with a wall-charger I had to charge it for a veery long time (hours) before I could power it on (otherwise it would shut down). Looking at Battery-Eye's result, it looks like the battery was discharged way below zero (see attached screenshot, device powered on around 04:45). That behavior is new with PR1.2. Xav inline: screenshot00.png___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users
Eduroam (EAP + TTLS + PAP) in pr1.2
Hello, I think this bug was solved in pr1.2 https://bugs.maemo.org/show_bug.cgi?id=1635 But after having installed the new firmware I am not able to connect to the eduroam network at my Institution. The PAP option does not appear in the configuration of the network. Have I to do something special? Luis. ___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users
Re: Eduroam (EAP + TTLS + PAP) in pr1.2
Am Donnerstag, den 27.05.2010, 10:32 +0200 schrieb Luis Llana: I think this bug was solved in pr1.2 https://bugs.maemo.org/show_bug.cgi?id=1635 But after having installed the new firmware I am not able to connect to the eduroam network at my Institution. The PAP option does not appear in the configuration of the network. Have I to do something special? Did you read https://bugs.maemo.org/show_bug.cgi?id=1635#c91 ? andre -- Andre Klapper (maemo.org bugmaster) ___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users
Re: PR 1.2 update and messaging
Vollmer Marius (Nokia-D/Helsinki) marius.voll...@nokia.com writes: Checking the database /home/user/.rtcom-eventlogger/el-v1.db or el.db with sqlite3 shows the old messages in the database. Yes, and el-v1.db and el.db are _exactly_ the same size for me, so maybe some schema conversion failed and el.db is now in the wrong format or something and rtcom refuses to both read and write it. That's a very very uneducated guess of course. Ok, turns out I was right again. :-( el-v1.db is created by making a copy of el.db and then modifying its schema in place. If that fails for any reason, el-v1.db is left in place in the old format but assumed to have been converted and apparently is then considered broken and rtcom refuses to use it. All future call events and incoming text messages are lost. rant That's very very very bad, of course. At the least, rtcom should move the 'corrupted' database to the side and create a new one so that new events aren't lost. Plus a little dialog telling the user that the impossible has happened. (There is a ton of code in rtcom-messsagin-ui to deal with messages that couldn't be saved, such as retrying to save them later, but that is all in vain if the reason for failure doesn't go away. There is also code to show an error dialog, but I haven't seen it.) /rant Anyway, removing el-v1.db and el-v1.db-journal and then rebooting fixed this for me. The database got correctly converted during boot and I have all my conversations back (minus the one that got lost while the database was in the wrong format). Be sure to make a backup before removing el-v1.db, of course. You can check whether el-v1.db is in the right format like this: $ sqlite3 ~/.rtcom-eventlogger/el-v1.db sqlite .schema Events If the Events table contains the outgoing column like this CREATE TABLE Events (..., outgoing BOOL DEFAULT 0, ... ); then you have the right format. ___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users
RE: PR 1.2 update and messaging
-Original Message- Anyway, removing el-v1.db and el-v1.db-journal and then rebooting fixed this for me. The database got correctly converted during boot and I have all my conversations back (minus the one that got lost while the database was in the wrong format). Be sure to make a backup before removing el-v1.db, of course. You can check whether el-v1.db is in the right format like this: $ sqlite3 ~/.rtcom-eventlogger/el-v1.db sqlite .schema Events If the Events table contains the outgoing column like this CREATE TABLE Events (..., outgoing BOOL DEFAULT 0, ... ); then you have the right format. I moved el-v1.db and el-v1.db-journal to a different directory, rebooted, and everything is working. Thanks for helping with this. Aldon ___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users
Re: Upgrade to PR 1.2 gone wrong
On Thursday 27 May 2010 08:24:30 Eero Tamminen wrote: IMHO packages with exact version dependencies to anything that doesn't come from the same source package should just be rejected from Extras. Possibly. It is certainly worth discussing, on the -developers list. Could somebody looking after Extras fix this so that we don't get such bad packages at least for PR1.2? In the meantime, as you understand what is going on, could you please log a bug report? Clearly the SSU needs to handle this case and not get into a reboot loop! Graham ___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users
Wifi messages in dmesg on N900 since PR1.2
Hi, since PR1.2 I've noticed my dmesg on my N900 is flooded with this message every few seconds (but not exact intervals) when I'm connected to my home wi-fi: [31600.605926] wlan0: roaming signal from driver, sending HIGHSIGNAL [31601.731414] wlan0: roaming signal from driver, sending LOWSIGNAL [31607.875396] wlan0: roaming signal from driver, sending HIGHSIGNAL [31616.579620] wlan0: roaming signal from driver, sending LOWSIGNAL [31624.567291] wlan0: roaming signal from driver, sending HIGHSIGNAL [31633.783843] wlan0: roaming signal from driver, sending LOWSIGNAL I also got this exactly every 900 seconds while I slept last night: [21999.580230] wlan0: deauthenticated [22000.235076] wlan0: authenticate with AP 00:16:01:b8:49:c1 [22000.239044] wlan0: authenticated [22000.239074] wlan0: associate with AP 00:16:01:b8:49:c1 [22000.244384] wlan0: RX AssocResp from 00:16:01:b8:49:c1 (capab=0x411 status=0 aid=2) [22000.25] wlan0: associated My internet settings are: Connect automatically: Any connection Search interval: 10 minutes Switch to wi-fi when available: yes Wi-Fi transmission power: 100mW WPA2-only mode: yes Power Saving: On (Maximum) Are these messages normal? I'm concerned that battery life could be affected if it's doing some kind of constant wifi activity... Thanks, Paul ___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users
Re: Wifi messages in dmesg on N900 since PR1.2
Paul Hartman wrote: Hi, since PR1.2 I've noticed my dmesg on my N900 is flooded with this message every few seconds (but not exact intervals) when I'm connected to my home wi-fi: [31600.605926] wlan0: roaming signal from driver, sending HIGHSIGNAL [31601.731414] wlan0: roaming signal from driver, sending LOWSIGNAL [31607.875396] wlan0: roaming signal from driver, sending HIGHSIGNAL [31616.579620] wlan0: roaming signal from driver, sending LOWSIGNAL [31624.567291] wlan0: roaming signal from driver, sending HIGHSIGNAL [31633.783843] wlan0: roaming signal from driver, sending LOWSIGNAL I also got this exactly every 900 seconds while I slept last night: [21999.580230] wlan0: deauthenticated [22000.235076] wlan0: authenticate with AP 00:16:01:b8:49:c1 [22000.239044] wlan0: authenticated [22000.239074] wlan0: associate with AP 00:16:01:b8:49:c1 [22000.244384] wlan0: RX AssocResp from 00:16:01:b8:49:c1 (capab=0x411 status=0 aid=2) [22000.25] wlan0: associated My internet settings are: Connect automatically: Any connection Search interval: 10 minutes Switch to wi-fi when available: yes Wi-Fi transmission power: 100mW WPA2-only mode: yes Power Saving: On (Maximum) Are these messages normal? I'm concerned that battery life could be affected if it's doing some kind of constant wifi activity... Thanks, Paul I noticed that my battery is being drawn since I installed PR1.2 yesterday. So when I saw your mail I checked my device and found the same messages, except for the deauthentication/authentication every 900 seconds. What is more important, I also have some message like this: [56910.552368] w11251: ERROR Power save entry failed, giving up [56994.833557] w11251: ERROR Power save entry failed, giving up [57034.021118] w11251: ERROR Power save entry failed, giving up Which could explain the battery being drawn, but I have no clue about what it is. My wifi configuration is the same as yours except that at this precise comment I'm using WEP. At home I use WPA and I'll check whether I have the deauthentication/authentication loop. Alejandro. ___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users
How to restore multimedia files back to N900 after updating PR1.2
Yesterday I received OTA ! for Maemo 5 from Nokia, It deemed to look like an over the air update but actually it asked me to connect via USB to PC having Nokia Software Updater After I updated my N900 from version 3 to new firmware 10.2010.19-1.003 the ussd is working fine also the gtalk video calls are quite good. But Unfortunately my multimedia (video,photos,songs) are not showing up even though it is already in there in respective folder path (video folder,songs folder photos folder) I can watch video if i go through the whole path that is Device memory-Video folder - Respective File same way to photos songs. So Is this an bug from PR1.2 update or there is no option provided user needs to store back freshly all the files to show up in the multimedia. Please help guys. Thanks -- Khalid Khan ___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users
Re: How to restore multimedia files back to N900 after updating PR1.2
Yo, Am Donnerstag, den 27.05.2010, 19:35 +0400 schrieb khalid khan: But Unfortunately my multimedia (video,photos,songs) are not showing up even though it is already in there in respective folder path (video folder,songs folder photos folder) I can watch video if i go through the whole path that is Device memory-Video folder - Respective File same way to photos songs. You could try to reindex the file database of tracker (the software running in the background): tracker-processes -r Might take a few minutes. andre -- Andre Klapper (maemo.org bugmaster) ___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users
Re: How to restore multimedia files back to N900 after updating PR1.2
On Thu, May 27, 2010 at 10:35 AM, khalid khan khalidre...@rcg.tv wrote: Yesterday I received OTA ! for Maemo 5 from Nokia, It deemed to look like an over the air update but actually it asked me to connect via USB to PC having Nokia Software Updater After I updated my N900 from version 3 to new firmware 10.2010.19-1.003 the ussd is working fine also the gtalk video calls are quite good. But Unfortunately my multimedia (video,photos,songs) are not showing up even though it is already in there in respective folder path (video folder,songs folder photos folder) I can watch video if i go through the whole path that is Device memory-Video folder - Respective File same way to photos songs. So Is this an bug from PR1.2 update or there is no option provided user needs to store back freshly all the files to show up in the multimedia. Same thing happened to me. I had to force it to rebuild the tracker database and then everything showed up again. You can open xterm and run tracker-processes -r or install tracker-cfg from extras-devel which has GUI to edit tracker options as well as restart/rebuild etc. ___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users
Problems creating file association
Hello, I want to read my openPGP (GPG) encrypted emails on my N900. I tried clawsmail without success, I tried Icedove without success. If someone got these running with GPG support I would be glad to discuss further details. As a third alternative I use modest, save the encrypted email and decrypt it using GPG at the xterm command line. This works as expected. To get a bit more comfort into this cumbersome process I wrote a small shell script that decrypts and displays the file, which is given by a command line parameter (decdisp). Now I want to associate this shell script with files having a .gpg file extension as well as those with an .asc extension (since encrypted.asc is what you get as attachment for GPG encrypted emails). I tried to follow the manual at http://wiki.maemo.org/Mime_Types/Open: - I created the file /usr/share/applications/hildon/gpgdisplay.desktop: [Desktop Entry] Encoding=UTF-8 Version=0.1 Type=Application Name=GPGDecrypt Comment=GPG decryption Exec=/usr/local/bin/decdisp Icon=connectivity_wlan_securitylevel3 X-Window-Icon=connectivity_wlan_securitylevel3 Categories=Utility X-Osso-Service=org.maemo.example_libosso MimeType=application/gpg-encryption; - I created the file /usr/share/mime/packages/gpg-encryption.xml: ?xml version=1.0 encoding=UTF-8? mime-info xmlns=http://www.freedesktop.org/standards/shared-mime-info; xmlns:osso=http://nokia.com/osso/mime-categories; mime-type type=application/gpg-encryption commentGPG encrypted file/comment osso:category name=documents/ magic priority=50 match type=string value=GPGENCRYPTION offset=0/ /magic glob pattern=*.gpg/ glob pattern=*.asc/ /mime-type /mime-info - I executed update-mime-database /usr/share/mime update-desktop-database /usr/share/applications hildon-update-category-database /usr/share/mime - I added the following line to /usr/share/applications/defaults.list: application/gpg-encryption=gpgdisplay.desktop It seems that I missed some basic steps because the above actions seem like having no influence. In modest I still get No viewer found for this file type. Also in the file manager I cannot open a file with a .gpg extension. Thanks a lot for your support, regards, Roman ___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users
Dmesg timestamt format
Hi, Which format is dmesg's timestamp printed in? I currently have values like 68993.598785 and I can't really figure out how to transform it into a date/time. Thanks. Alejandro. ___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users
Re: Dmesg timestamt format
Hi, these are seconds since system start. Regards, Martin 2010/5/27, Alejandro López listas@googlemail.com: Hi, Which format is dmesg's timestamp printed in? I currently have values like 68993.598785 and I can't really figure out how to transform it into a date/time. Thanks. Alejandro. ___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users ___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users
Re: Dmesg timestamt format
2010/5/27 Alejandro López listas@googlemail.com: Hi, Which format is dmesg's timestamp printed in? I currently have values like 68993.598785 and I can't really figure out how to transform it into a date/time. In Linux systems in general, it is typically the number of seconds since the device was powered on. It is really not useful for finding out when something happened; it's basically there to find out how much time passed between messages. If you want real timestamps, install syslog. You may be able to look at /proc/uptime, subtract that many seconds from current time and approximate the dmesg times based on that. That is, of course, assuming it started at 0. In the case of N900 I don't think it necessarily always does. Maybe it depends on the presence of a charging cable, etc. ___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users
Re: Dmesg timestamt format
2010/5/27 Alejandro López listas@googlemail.com Hi, Which format is dmesg's timestamp printed in? I currently have values like 68993.598785 and I can't really figure out how to transform it into a date/time. It's printk() times, more info here: http://elinux.org/Printk_Times Best regards, -- Cláudio Patola Sampaio IRC: ptl - Yahoo: patolaaa Campinas, SP - Brazil. ___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users
