(In reply to comment #0)
Oops, seems like I forgot to add About product section. Since there's no button
to Edit, I'm adding it as another comment:

Version: 20.2010.36-2.002 

I hope to find someone still taking care of Maemo 5.

Created an attachment (id=3166) [details]
strace output of browserd

Comment 3 Andre Klapper 2010-11-10 13:38:31 UTC

(In reply to comment #0)
> EXTRA SOFTWARE INSTALLED:
> 

That section is missing...

Also, can you please provide a syslog covering this happening? See
http://wiki.maemo.org/Documentation/devtools/maemo5/syslog and
http://wiki.maemo.org/Documentation/devtools/maemo5#Installation for more
information.
If you are not used to Linux, after creating the syslog file you can copy the
syslog file to those folders that are visible in the Maemo File Manager by:
  * Starting X Terminal
  * cp /var/log/syslog /home/user/MyDocs/.documents/
After that you can find the file in the Maemo File Manager by going to Nokia
N900 > Documents.

Created an attachment (id=3173) [details]
dpkg --list output (Extra Apps)

Created an attachment (id=3174) [details]
Syslog output

Steps I did:

* Installed sysklogd and started it properly
* Rebooted
* Started Conversations and looked at some chats. 
* Uploaded /var/log/syslog

FYI: IMEI and BSSID numbers changed with CEN:SO:RED, If you're a Nokia
employee, or you need those numbers about this issue, please ask for it and
explain your intentions properly.

(In reply to comment #5)
> Created an attachment (id=3174) [details] [details]
> Syslog output
> 
> Steps I did:
> 
> * Installed sysklogd and started it properly
> * Rebooted
> * Started Conversations and looked at some chats. 
> * Uploaded /var/log/syslog
> 
> FYI: IMEI and BSSID numbers changed with CEN:SO:RED, If you're a Nokia
> employee, or you need those numbers about this issue, please ask for it and
> explain your intentions properly.
> 

[Sorry for bugmail noise]

I noticed an entry in syslog file:

Nov 10 20:35:05 Nokia-N900-42-11 rtcom-messaging-ui[1732]: GLIB WARNING **
default - Failed to load plugin
/usr/lib/rtcom-eventlogger/plugins/libstatus.so: librtcom-eventlogger-ui.so.0:
cannot open shared object file: No such file or directory.


Well, I'm not sure if it's relevant or not, since I don't have that file (I
have librtcom-eventlogger-ui.so.1.2.0, not so.0) I can't try copying that file
to /usr/lib.

Created an attachment (id=3175) [details]
Screenshot of the bugged UI

It's the same screenshot already included in original report, I just wanted to
attaching it seperately to prevent future broken link issues.

I wonder if anyone assigned to/cares about this issue and what are the odds of
getting a solution?  

Thanks,

I'm not sure if this is related; at least with me besides the scrollbar, the
first time the window opens the whole convo isn't loaded just a part, and with
each new msg sent or received more of the history loads, but when a msg is
being received the scrolling goes crazy, insted of autoscrolling to the bottom
it goes to some randon spot usually far from the bottom.

When the browser is loading a heavy page, somtimes for a few moments the page
got a plain scrollbar and can't be scrolled the regular way just like what
happens with Conversations, except that with microB the glitch quickly goes
away; does this help?

Thank you for the input, I think It may be related to this issue since this
scrollbar is also generated by an application named "browserd".

By the way, I still need help about this problem and it gets more frustrating
every day. :(

Maemo Talk Threads by other users about this issue:
http://talk.maemo.org/showthread.php?t=68579
http://talk.maemo.org/showthread.php?t=67473
http://talk.maemo.org/showthread.php?t=68307

On one of those threads, someone said that it's related to ~/.mozilla/rtcom
folder and offered removing it as a solution. I tried it myself with countless
different approaches (kill rtcom&browserd, remove, kill rtcom, remove, remove
first, then kill rtcom..) without any success. There is a file named prefs.js
in that folder with some configurable keys but I don't have any idea about
which one is related to this issue or even if any of them is related or not.

By the way, can someone change this report to confirmed? It's already confirmed
by three other people, looks pretty legitimate to me.

I contacted Pali Rohar (OP of the thread) to ask how he managed to find a
solution. He said he removed .mozilla and SIGKILL'ed rtcom-messaging-ui more
than once, rebooted and It's fixed. I tried this method countless times without
any success, anyway, it's worth mentioning I think.

Also downloaded rtcom-messaging-ui binary debian file and extracted it on my PC
to see it's contents and checked the package and gconf entries, there was
nothing about scrollbars. Now I got a stock .mozilla folder from a friend to
compare it with mine to see if there's any major difference. (prefs.js was
same, I don't know about others)

I don't feel like doing away with my history needlessly, could someone that is
not so attached to their history try clearing all the Conversations histories
and check if that helps please?

There's no need to clear conversations history, you can just move it away to
make system believe it's lost/clear. (mv /home/user/.rtcom-eventlogger/el-v1.db
/home/user/.rtcom-eventlogger/el-v1.db.backup) 

Tried it without any success. scrollbar doesn't disappear on mine.