["Help" request] Strange and serious software'ish problem with Maemo's call/messaging system (?)
I got quite a serious, software-side (cross-checked) with my main N900 - it's quite complicated thing that I've never seen before, so, please, bear with me.
It started when, one day, device turned off due to discharged battery, while my son was gaming on it. Device was connected to WiFi at the time, and SIP account was registered (why it may be important, later on). fsck at the boot time found some minor problems, but none if it seemed serious (some thumbnail or temporary files of browser were damaged, some got connected to lost+found). FSCK ended up successfully, and marked filesystem as clean. Hoever, after boot, strange things manifested themselves. I'll list them in points, cause there is plethora of them (and all of them seems inter-connected, like coming on from the same issue): 1. I can open phone-ui or adressbook, but I can't make any calls, despite having GSM/3G connection working all-right. When i try to call any (normal, cellular) number, either from dialpad, recent calls or addressbook, a "account not in use" message appears. 2. On random intervals (between 30 seconds and 2 minutes, at most), notification bar about "Phone application shut down, internal error" appears. If I have phone-ui open at the time, it closes itself. 3. If someone calls me, call prompt doesn't appear, and no ringtone is played. I know that phone is "processing" the incoming call, due to sudden slowness and characteristic cellular "noise" in speakers. Also, immediately when I'm called, message about phone application shutting down (internal error) from point #2 appears. The other side sees it as if I've rejected call instantly. Immediately afterwards, I get a Maemo notification about failing to pick up a call. 4. I can receive SMS all right, but I can't send them - if I try to open conversations (either from menu or addressbook), I get the "phone application closed, internal error" message and nothing happens. If I try to reply after receiving and reading message, I can hit the "send" button, but it just becomes grayed out. There is no "processing" circle, or any other reaction. 5. I can receive e-mails, but can't send them - modest open fine, but just like with SMS, if I hit "send", it gets grayed out and nothing else happens (message doesn't even "close" itself, it just stay open, with "send" grayed out, infinitely). 6. I don't see "green circle" in status bar menu indicating that I'm connected to SIP proxy account, not I have any accounts visible, when I try to edit them. Hoever, I AM logged in to my SIP proxy - I'm visible from the proxy's side, and I can get calls from SIP (ending just like normal calls - like immediately rejected, no call prompt, and Maemo's message about missed call). 7. If I try to add some SIP account, I can fill the details and hit "add" button, but it just get grayed out, and nothing happens. --- Dmesg doesn't show anything unusual. Only interesting lines in syslog (after I try to do anything with calling/messaging) is: Code:
BloodRose rtcom-call-ui[5086]: GLIB MESSAGE default - Plugin registered: CALL. After trying to pinpoint the cause for a week, I must admit that I have no idea how to fix it. tried --purge reinstalling every package that I thought might have something to do with non-working functions: Code:
apt-get install --reinstall --purge phonet-at phonet-utils csd-info libphinfo0 libtelcommon0 rtcom-accounts-plugin-sip rtcom-accounts-voip-support rtcom-messaging-ui rtcom-presence-ui rtcom-accounts-ui librtcom-accounts-widgets0 rtcom-call-ui librtcom-call-ui0 librtcom-eventlogger-ui1 librtcom-eventlogger-plugins1 librtcom-eventlogger1 librtcom-accounts-ui-client0 connui-conndlgs telepathy-ring libnice0 libconnui libconnui-cellular libconic0 libtelepathy-glib0 telepathy-sofiasip telepathy-stream-engine libtelepathy-farsight0 libtelcommon0 So, anyone got idea what could be related to issues that I'm experiencing? Maybe some other package that I could reinstall? There MUST be some file(s) that got damaged due to sudden shutdown resulting in this mess. At this point, I'm close to do a painful (and first time ever, honestly) full-reflash with installing everything from scratch. But, before I do so, I would really like to try everything that I could to solve the mystery - in case such weirdo ever happens again. Thanks in advance for any help. /Estel // Edit If it isn't obvious from the description - it is NOT hardware issue. |
Re: ["Help" request] Strange and serious software'ish problem with Maemo's call/messaging system (?)
Do you have strace/ltrace/latrace installed? I would recommend installing those and running those programs that are malfunctioning through those tools, to see what libraries/system calls it makes, and probably see something about what/where it fails. (You can either launch those processes from the command line under {s/l/la}trace, or attach {s/l/la}trace to existing processes if you know their PIDs.) If the file corrupted is some low-end library, you may need to get statically compiled versions of the aforementioned to have them work right...
|
Re: ["Help" request] Strange and serious software'ish problem with Maemo's call/messaging system (?)
Thanks for the tip - here is strace output, from the start of rtcom-call-ui, to the moment it closes itself with "yellow bar" internal error message:
http://pastebin.aquilenet.fr/?01c721...gJt0XTkyaWuHI= What caught my (ignorant, I'm using those tools for the very first time :o ) eye is the line: Code:
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory) latrace output (rtcom-call-ui): http://pastebin.aquilenet.fr/?349a69...Svg4QkClW5kOo= the interesting line might be: Code:
7472 __errno_location [/lib/libc.so.6] ltrace output: http://pastebin.aquilenet.fr/?94144d...40vOmJUXbhn3g= Again, the interesting bit might be: Code:
__errno_location() = 0x4001fd70 Thanks again, /Estel |
Re: ["Help" request] Strange and serious software'ish problem with Maemo's call/messaging system (?)
I have /etc/ld.so.cache and /etc/ld.so.conf, but no /etc/ld.so.preload
/lib/libc.so.6 is link to libc-2.5.so Not read the logs, yet. Best wishes. |
Re: ["Help" request] Strange and serious software'ish problem with Maemo's call/messaging system (?)
Quote:
Here's a longer but still quick-ish explanation: https://minipli.wordpress.com/2009/0...ld-so-preload/ That's all I got for now, sadly I have only limited experience reading those traces, and at any rate I have to go for the evening. |
Re: ["Help" request] Strange and serious software'ish problem with Maemo's call/messaging system (?)
@Estel,
That looks weird. My guess is that it's something related to the "org.freedesktop.Telepathy.AccountManager" dbus service. To start with I'd ask you to post the output of "ps ax | grep dbus". I have: Code:
dbus-daemon --system --nofork You could also check the contents of /etc/dbus-1/system.d Another guess (as I'm only guessing) would be to check/reinstall librtcom-accounts-* Also check/reinstall libosso-dbus-conf Good luck! |
Re: ["Help" request] Strange and serious software'ish problem with Maemo's call/messaging system (?)
Thanks for all the input, guys.
ps ax | grep dbus output is: Code:
BloodRose:~# ps ax | grep dbus Code:
BloodRose:~# ls -lh /etc/dbus-1/system.d/ Trying to reinstall packages that you've suggested, now. /Estel |
Re: ["Help" request] Strange and serious software'ish problem with Maemo's call/messaging system (?)
Reinstalled those (and other dbus-related) packages, to no avail :(
It's worth to mention, that - with almost 100% probability - it must be something on /dev/mmcblk0p2 (home, opt) damaged, not a thing that resides on ubifs root. Having the latter filesystem damaged is highly unlikely/impossible. Not that the above gives me any idea where to look next, though... Maybe device gets confused by not having SIP accounts set, while at the same time being connected to them? It's a shoot in the dark, but it COULD be trying to ask me if I want to send/call via GSM or VOIP, then get confused somehow... Where VoIP accounts data is stored, exactly? I could try purging it. /Estel |
Re: ["Help" request] Strange and serious software'ish problem with Maemo's call/messaging system (?)
Random thought: maybe one of the osso-abook files is corrupt. I suspect you can move/back up ~/.osso-abook and reboot to reset it .. I'd probably back up all of ~/ anyway. I've noticed similarly weird stuff happening with a corrupt conversations database (though that's sqlite3 while osso-abook appears to be Berkley DB).
|
Re: ["Help" request] Strange and serious software'ish problem with Maemo's call/messaging system (?)
Thought of a moment something like that.
But does not match your other probs. Especially modest??? Which let me think of a more global FS prob? But, sorry, I have no idea :confused:. So maybe maxdamantus hint is better? |
All times are GMT. The time now is 11:30. |
vBulletin® Version 3.8.8