Hi Guys, Last night my suse8.1came to a halt due to a mysterious 'HD full' condition. Upon reboot things seemed OK but there were a few problems. This one regards OPERA on KDE 3.0.5. After the reboot clicking the OPERA icon yeilded the 'in-process' cursor with the little OPERA flickering icon, but after 30 or so seconds nothing happens; everything is like before clicking the icon. This OPERA is the one shipped with suse8.1. I used YAST2 to un-install, then re-install OPERA from the suse CDs. Same prob = The 'in-process' cursor runs for a while then nothing. Next I used YAST2 to un-install OPERA, then d/l'ed the 6.11 vers of OPERA from the OPERA site, used Konqi to start the YAST2 RPM installer which ran OK. Now here is where it gets strange == When I started the new OPERA it worked fine, but it opened TWO instances, one looking the first start of a newly installed OPERA, the other one opened to the web page I was browsing last night! During my use of SuSE 8.1 since I installed it I have seen a dozen or so instances of an installed app NOT starting as described above; the wait cursor 'spins' the mini icon for the app for 20-30 secs then nothing. I have only remedied this by reinstalling the app. But todays OPERA prob is the first one to not respond to a simple reinstall; it needed installing the newer vers from OPERA home page. Is this problem happening on your systems? Is there a KDE bug reported on this prob? Feeling a bit freaked out .............. PeterB -- -- Proud to be a SuSE Linux User since 5.2 --