Description: Libre Office friert im Serienbrief Manager ein, nachdem ich die Adressenliste auswählen wollte. Dies unter Linux CentOS 7.4.1708 wir greifen mit einem Thinclient per XDMCP drauf. Steps to Reproduce: -> Openoffice Writer starten -> Extras -> Serienbrief-Assistent -> Ausgangsdokument wählen -> Aktuelles Dokument verwenden -> Weiter >> -> Dokumenttyp wählen -> Brief -> Weiter >> -> Adressblock einfügen - > Adressenliste auswählen... -> PROGRAMM ABSTURZ!! Actual Results: Libre Office friert ein, nur das Serienbrief-Assistent fenster lässt sich noch bewegen. Dies wird aber wie man es aus Windows kennt immer so dupliziert Expected Results: Ein Fenster öffnen indem man die Adressenliste auswählen kann... Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info:
Could you give a try to 6.0.5 (and respond in English please)?
(In reply to Julien Nabet from comment #1) > Could you give a try to 6.0.5 (and respond in English please)? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version. Change to RESOLVED WORKSFORME, if the problem went away.
Now the program crashes immediately, when i open the "Mail Merge Wizard" Without any Error.
Thank you for reporting the bug. To be certain the reported issue is not related to corruption in the user profile, could you please reset your Libreoffice profile ( https://wiki.documentfoundation.org/UserProfile ) and re-test? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the issue is still present
It doesnt work. I still have the same problems with the "Mail Merge Wizard"
Does it crash if you go to File - Wizards - Fax/Letter? OTOH, would you mind sharing the database use in the Mail merge wizards that make LibreOffice crash?
The problem with newer versions upward version 5.4.5.1(english language pack) is when I select the Mail Merge Wizard it immediately crashes. It doesnt open any window. If I choose the German language pack, I can at least get to the subwindow "Address List". There I select "Add Adress list" and as soon as I press the button, it instantly frozed in place. All of this is 100% reproducable.
Its also reproducable under ArchLinux, CentOS and manjaro.
(In reply to support from comment #7) > If I choose the German language pack, I can at least get to the subwindow > "Address List". There I select "Add Adress list" and as soon as I press the > button, it instantly frozed in place. All of this is 100% reproducable. I can't reproduce it with German language pack under Windows: Version: 6.0.5.2 (x64) Build-ID: 54c8cbb85f300ac59db32fe8a675ff7683cd5a16 CPU-Threads: 4; BS: Windows 10.0; UI-Render: Standard; Gebietsschema: de-DE (de_DE); Calc: group
Would it be possible you retrieve a backtrace? (see https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace) It could help us to investigate.
Created attachment 143190 [details] The gdbtrace.log Here is the log.
(In reply to Dieter Praas from comment #9) > (In reply to support from comment #7) > > > If I choose the German language pack, I can at least get to the subwindow > > "Address List". There I select "Add Adress list" and as soon as I press the > > button, it instantly frozed in place. All of this is 100% reproducable. > > I can't reproduce it with German language pack under Windows: > > Version: 6.0.5.2 (x64) > Build-ID: 54c8cbb85f300ac59db32fe8a675ff7683cd5a16 > CPU-Threads: 4; BS: Windows 10.0; UI-Render: Standard; > Gebietsschema: de-DE (de_DE); Calc: group
We are only using Linux CentOS 7.0
Thank you for your feedback, I noticed this: #2 0x00007fffad895f63 in e_flag_wait () at /lib64/libedataserver-1.2.so.22 #3 0x00007fffad892300 in e_client_wait_for_connected_sync () at /lib64/libedataserver-1.2.so.22 #4 0x00007fffae1c9d9b in e_book_client_connect_sync () at /lib64/libebook-1.2.so.16 #5 0x00007fffae1c9f9a in e_book_client_connect_direct_sync () at /lib64/libebook-1.2.so.16 ... #10 0x00007fffae6dcc53 in () at /opt/libreoffice6.0/program/../program/libevoablo.so #11 0x00007fffb4464e25 in () at /opt/libreoffice6.0/program/../program/libdbalo.so So it seems related to the management of an Evolution database.
Ok thanks for your feedback! Can i solve the problem by myself or can this only be done by libreoffice?
I tried to reproduce this with LO Debian package 6.0.5 or with master sources updated yesterday, I don't reproduce this. In Debian, there's a specific LO Evolution package, I checked it was installed. For the moment, I can't tell how it can be fixed, on LO or specifically on your machine.
On pc Debian x86-64 with master sources updated yesterday, I can't succeed in reproducing the crash with English or German UI. Does the bt correspond to the crash you get when just selecting MailMerge wizard? If not, could you attach a bt corresponding at this precise moment?
When clicking "Select Address List", I noticed this log on console: warn:legacy.osl:2578:2578:sw/source/ui/dbui/addresslistdialog.cxx:615: exception caught in SwAddressListDialog::DetectTablesAndQueries Then I see: EvolutionLocal Personal But clicking on button "Change Table..." does nothing (except displaying again the quoted log)
I have a similar result when I try to start a wizard from within LibrOffice Base : For a new database, the LO Base starts with creating forms, and asks if you want to do it in view mode or by means of the form creating wizard . When I choose the wizard, the whole program flashes away and is no more active !!!
Need steps in english to reproduce this bug.
Putting it back to UNCONFIRMED
It looks like the bug has been fixed in the latest 6.1. I can successfully import the address list and LibreOffice no longer crashes.
Since there's no specific fix, let's put this one to WFM.
for those that stuble(d) over this issue: we had a similar situation in a CentOS installation. I turned out to be triggered by an Evolution address book. That however was not in use, but installed by LibreOffice: ../4/user/database/evolocal.odb I could be resolved by installing Evolution and a simple linked odb, or by removing that entry in the user profile.