Diederik de Haas wrote on 15/01/16 11:13:
On Friday 15 January 2016 11:02:45 Arthur Marsh wrote:
I've used a stock Debian kernel and removed oldstable packages and still
seeing the same thing happening.
I think your last report was way better then (all) your other reports.
I don't know whether that will give ppl with relevant knowledge enough to go
on, because so far it is unreproducable for others. It's working fine here.
Have you tried creating a new user and can you confirm whether the issue then
still occurs?
This is where it gets really mystifying.
I copied my iceweasel profile (~/.mozilla/firefox/profiles.ini and
~/.mozilla/firefox/vl23iilx.default directory tree) to a new account,
and started iceweasel in KDE plasma without issue.
I then went to my original account:
cd
cd .mozilla
ls -al
drwxr-xr-x 7 amarsh04 amarsh04 4096 Jan 15 16:34 .
drwxr-xr-x 342 amarsh04 amarsh04 204800 Jan 15 16:34 ..
-rw-r--r-- 1 amarsh04 amarsh04 335 Nov 9 2008 appreg
drwxr-xr-x 3 amarsh04 amarsh04 4096 Apr 10 2009 default
drwx------ 3 amarsh04 amarsh04 4096 Sep 14 2009 extensions
drwxr-xr-x 5 amarsh04 amarsh04 4096 Apr 9 2015 firefox
drwxr-xr-x 3 amarsh04 amarsh04 4096 Apr 10 2009 fonts
drwxr-xr-x 3 amarsh04 amarsh04 4096 Apr 10 2009 iceweasel
-rw-r--r-- 1 amarsh04 amarsh04 1375 Mar 20 2006 mozver.dat
-rw------- 1 amarsh04 amarsh04 6526 Sep 4 2008 oldpluginreg.dat
I moved everything except the empty fonts directory and firefox
directory out the way, then restarted iceweasel under KDE plasma without
problems.
I then quit iceweasel, moved the old directories and mozver.dat and
oldpluginreg.dat back and was able to start iceweasel under KDE plasma
without problems.
Even if iceweasel had completely locked up, should it lock up the rest
of the plasma desktop with it?
Arthur.
