Hi, many thanks for the quick replies
Am Mittwoch, 9. November 2022, 07:05:42 CET schrieben Sie: > Hi, > > Am 08.11.22 um 21:32 schrieb Rainer Dorsch: > > So far I confirmed that it does not happen in safe mode. I assume that > > at least > > some Debian users upgrading to bookworm will run into this issue. > > Well, people either use stable and has 7.0.4 and skip the broken 7.4.1 > when upgrading since bookworm will contain 7.4.2+ (the sign that it does > is that it appeared in bullseye-backports now) nad already had 7.4.1 > installed in bullseye/bullseye-backports and are already affected. I was not aware that this issue is only showing up, if 7.4.1 or 7.4.0 were ever installed. > > I think the users should be notified during the upgrade. > > Maybe, yes. > > The question is where? libreoffice-core would be the correct place but > then people not using KDE will also get it. -kf5/-qt5 might do it as > they seem somehow to be the only affected but then it might be shown > twice and is on the package which doesn't have the actual fix/file > affected... If users upgrading to 7.4.2+ from 7.0.4 are not affected, I think documentation for this issue underlines that your libreoffice packages are the gold standard for excellent Debian packages :-) > > If anybody is interested in defining some experiments to narrow down the > > issue and try to avoid the complete user profile resetting requirement > > after the upgrade to bookworm, please let me know. Otherwise I would just > > reset my user profile and assume that this will work fine for me. > > Well, if the bug report title is right you probably can just remove the > affected key? > > rene@frodo:~/.config/libreoffice$ grep -r ooSetupFactoryWindowAttributes * > 4/user/registrymodifications.xcu:<item > oor:path="/org.openoffice.Setup/Office/Factories/org.openoffice.Setup:Factor > y['com.sun.star.drawing.DrawingDocument']"><prop > oor:name="ooSetupFactoryWindowAttributes" > oor:op="fuse"><value>0,71,5,5;5;0,71,1921,1010;</value></prop></item> > 4/user/registrymodifications.xcu:<item > oor:path="/org.openoffice.Setup/Office/Factories/org.openoffice.Setup:Factor > y['com.sun.star.frame.StartModule']"><prop > oor:name="ooSetupFactoryWindowAttributes" > oor:op="fuse"><value>0,71,37,33;5;0,71,1600,788;</value></prop></item> > 4/user/registrymodifications.xcu:<item > oor:path="/org.openoffice.Setup/Office/Factories/org.openoffice.Setup:Factor > y['com.sun.star.presentation.PresentationDocument']"><prop > oor:name="ooSetupFactoryWindowAttributes" > oor:op="fuse"><value>0,0,208,2;5;0,0,1920,1009;</value></prop></item> > 4/user/registrymodifications.xcu:<item > oor:path="/org.openoffice.Setup/Office/Factories/org.openoffice.Setup:Factor > y['com.sun.star.sheet.SpreadsheetDocument']"><prop > oor:name="ooSetupFactoryWindowAttributes" > oor:op="fuse"><value>0,71,3,3;5;0,71,1921,1010;</value></prop></item> > 4/user/registrymodifications.xcu:<item > oor:path="/org.openoffice.Setup/Office/Factories/org.openoffice.Setup:Factor > y['com.sun.star.text.TextDocument']"><prop > oor:name="ooSetupFactoryWindowAttributes" > oor:op="fuse"><value>0,71,1921,1010;5;0,71,1920,1009;</value></prop></item> > > Worth a try at least. Would also be a senseful information for .NEWS. I did a test and grepped for all occurrences of rd@h370:~/.config/libreoffice$ grep -r ooSetupFactoryWindowAttributes * and for each file with a match I did $ grep -v ooSetupFactoryWindowAttributes registrymodifications.xcu > registrymodifications.xcu.new $ mv registrymodifications.xcu.new registrymodifications.xcu This seems to resolve the problem for me. Many thanks Rainer -- Rainer Dorsch http://bokomoko.de/
