I did some stracing, and found that the following happens on startup
after I have copied in your chrome.rdf:
1) iceape opens chrome.rdf readonly, and reads the contents.
1.5) some other stuff happens including reading of my .gtkrc-2.0 and a lot of
.xpt files.
2) iceape then tries to reopen the file as
O_WRONLY|O_CREAT|O_EXCL|O_TRUNC|O_LARGEFILE.
This fails with EEXIST as the file already exists and O_EXCL was given.
3) iceape instead opens chrome-1.rdf with the same flags (succeeds), and
immediately closes it.
4) The newly created chrome-1.rdf is opened with mode
O_WRONLY|O_CREAT|O_LARGEFILE and
data is written to it.
5) chrome-1.rdf is renamed to chrome.rdf (replacing the old chrome.rdf)
Steps 2-5 are then repeated 6 more times, meaning that a new chrome.rdf is
written 7 times
(probably corresponding to the 7 new elements added) (there seems to be some
room for
optimization here...)
Any suggestions on where to put a gdb breakpoint in order to get some
interresting backtrace?
--
Iceape-Browser: Theme setting reverts on restart
https://bugs.launchpad.net/bugs/124365
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
