Description of problem: Woke up to both screens displaying sddm login. Obviously, the desktop must've died overnight. I had several oocalc files open. Now, when I try to open oocalc, it fails with: futex(0x56e578, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 0, {tv_sec=1648816046, tv_nsec=984454000}, FUTEX_BITSET_MATCH_ANY (soffice:2854513): dbind-WARNING **: 08:27:26.803: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-htaWsTmFVv: Connection refused ) = 0 Issuing: export NO_AT_BRIDGE=1 gets rid of the message; but oocalc still fails to start. The splash displays for a fraction of a second and exits. strace provides no clue at the moment. Version-Release number of selected component (if applicable): How reproducible: Desktop restart: no idea what caused it. oo{calc,writer,draw,...): always Steps to Reproduce: 1. 2. 3.
Interesting... Was in process of closing applications when I discovered a libreoffice startup window listing 4 files to be re-opened. Clicked Start and got one file not found (see bug 30155). The not found dialog appeared twice then another dialog I dismissed before reading it all. At this point, rather than crashing as in bug 30155, ooffice opened LOTS of windows; guessing one for each time I got dbus error. So it appears that if libreoffice is restarted automatically on login, it: * displays a file recovery dialog; likely hidden behind other window(s) * trying start oo{calc,writer,...} while libreoffice is in this state, it just queues the start requests * once the file recovery dialog is discovered and handled, libreoffice starts and opens multiple windows, one for each of the queued start requests... Rather than queue and silently fail to start, libreoffice should raise the recovery dialog on the current desktop, and/or provide a meaningful message. HTH
Summary: libreoffice fails to start after unscheduled kde desktop restart => libreoffice start dialog hidden during unscheduled kde desktop restart
Did you already search for an upstream bug report or try to report it upstream? Do you believe it is a Mageia package problem?
Did you check your libreoffice user profile (as suggested at libreoffice bugzilla)? https://wiki.documentfoundation.org/UserProfile
I did the work for you and searched libreoffice bugzilla. If you can reproduce, either append the upstream bugreport or create a new one for this LO version. https://bugs.documentfoundation.org/show_bug.cgi?id=131320 Im tempted to mark this bugreport UPSTREAM and close it....
Mark it UPSTREAM; I can't do that.
I have played a little with this, but not under Plasma, nor several windows for the same LO application, nor re-launching specifically the application(s) in question. I started an instance of Writer, Calc & Draw (which has changed so much it caused me a lot of grief). Then killed the desktop Ctrl/Alt/Bksp/Bksp, re-logged in, and fired up generic LibreOffice. It popped the dialogue about restoring each of the interrupted applications, which worked. OK, I can retry this with Plasma, and re-starting spcifically the interrupted applications. But, Pierre, how to get the recovery dialogue hidden beneath another window? You note Dbus problems. We have a Kmail bug where Dbus features also. Are you able to try a different desktop to Plasma?
CC: (none) => lewyssmith
I only have time to report... Very busy. Typically have many spreadsheets open; 9 on current one of 10 desktops at the moment. When I reported this, the system had restarted the session overnight, and I know I didn't hit Ctrl+Alt+Bksp/Bksp in my sleep. I suspect the dialog appears behind other windows because I have many other applications running and most (all?) the open sheets were behind other windows when the desktop restarted. I'm setup to resume applications on restart in case that matters. I did search & see similar dbus issues which may be dbus reporting inaccurately; but that's not conclusive. No dbus error as I just opened oowriter. Was likely temporary as I haven't seen them lately.
> I didn't hit Ctrl+Alt+Bksp/Bksp in my sleep I was not suggesting that you did! I just did that to kill & re-start the GUI, to simulate your automatic system re-start (which might have been due to a power glitch). This is something you could try to re-create the problem you are reporting. > I'm setup to resume applications on restart in case that matters It does for the hidden recovery dialogue window. I will look into trying that too.
LOL Probably needed a smiley... I was just stating a fact, nothing more. Power is possible, though system is on a new UPS backup. That restart was the only one I've experienced. I checked uptime to see if it was a reboot; it was several days, so just a desktop restart. Just killed office to test. Spotted another bug... Hmn.. just noticed we are updating bug on Mageia. FYI: just filed https://bugs.documentfoundation.org/show_bug.cgi?id=148431 Along with bug 30155; looks like LO needs a review of the startup code. (just an observation :)
Well, with all these bugs - just you! LO cannot be that bad. https://bugs.documentfoundation.org/show_bug.cgi?id=148431 is obscure, even though it is theoretically legitimate in that it should not be trying to re-open a file which was not open when it got interrupted. As for bug 30155, Cauldron is always at own risk, non ? Doubtless tv will try it. I have yet to play to re-create your situation - under M8; which as I suggested in comment 8 *you* could try by killing the desktop (Ctrl/Alt/Bksp/Bksp) when it is loaded with several Calc windows hidden by several others.
Just me? What can I say? I have a history of discovering issues earlier than most. :) This is a brand new machine. Unless the manufacturer started Windows at the factory, it has NEVER seen the first Windows instruction. I loaded mga8 twice; but never ran it because there was no video. So I installed Cauldron, still no video; turned out to be due to ownership for sddm. I don't do weird stuff other than pushing it hard. 10 desktops, 33+ firefox windows, 2 claws-mail, make -j20, on average a dozen LO files, streaming, python processing of multi-GB files, and misc other proggies. I understand the "own risk"... I'm only reporting issues that could cause Mageia issues by releasing mga9 too soon. I don't have to report stuff as I can resolve most on my own. Say the word if you'd rather not see reports on Cauldron... :)
> I have a history of discovering issues earlier than most > I don't do weird stuff other than pushing it hard This is the best sort of testing. Weird usage is problematic. > Say the word if you'd rather not see reports on Cauldron. Not at all. Cauldron bugs are valuable for revealing issues before they get out into a [pre]release. Please keep them coming.
Off topic in this thread; but just discovered my /usr/man directory is gone. Python is no longer running right. Can rpm verify and correct all installed packages, or do I have to loop through "rpm -F" on all the packages? Something really weird must've happened last night; woke up to a dead system. Booted and mostly back where I was; but now missing files...
Scratch comment 13... /tmp was full... investigating.
FWIW I have done my best to re-create the problem under M8 Plasma, in vain. The main reason being that I could not get a crashed session restored. I checked System Settings-Startup & Shutdown-Desktop Session-On Login = Restore the previous session. I started and saved 3 Calc files/windows, leaving them open; added a couple of other applications on top of them; killed the whole lot with Ctl/Alt/Bksp/Bksp and re-logged in - to a bare desktop. NO restored sessions, so no way of testing the 'hidden' dialogue. Re-starting Calc specifically correctly showed a dialogue with the 3 files to restore, which it did when asked to. So for the moment, Pierre, when you have got your system back into shape, please try to re-create the problem so that we can too.
>NO restored sessions, so no way of testing the 'hidden' dialogue. 'Restore previous saved session' works great here. You may have to set it, then log{out,in} cleanly for it to be setup as expected... Then, if the session is resumed; try the test... For me, every time the desktop dies, LO has this issue. HTH
I am fed up with chasing this. Having got Plasma to restore sessions, I discover this is very variable: exactly what happens is very application dependant. I tried opening Calc on 3 different desktops, in each case with another application on top of it: Kcalc, Kwrite, K3b. Logging out with them all open did not seem to work; it turned out to be Kwrite complaining about the file not having been saved. Once that was done, logout worked. Re-logging in, I found the three 'in front' applications restored on their original desktops, but no sign of Calc. Starting that explicitly popped its dialogue about restoring the 3 files it was doing before logout; pursuing that showed apparently just one of the spreadsheets on the desktop in use, nothing on the other 2 desktops. But all 3 spreadsheets were in fact re-opened - on top of each other! As with the companion bug 30260 about Konsole, it seems that what happens has some application dependence; but given that everything was restored, that is surely good news, and not worth a bug. Your original complaint was: - "libreoffice is restarted automatically on login" - the LibreOffice restore dialogue was hidden beneath other windows; neither of which can I re-create. Calc was not automatically re-started, other applications were. Explicitly re-launching Calc necessarily showed its restore dialogue on top. This is all too obscure to continue with - unless we can reliably re-produce your complaints. Closing for the moment, you can re-open the bug if you can provide a method which reliably illustrates your problem.
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=30260Resolution: (none) => WORKSFORMEStatus: NEW => RESOLVED