Bug 113199 - Crash if I try to edit the actual master slide
Summary: Crash if I try to edit the actual master slide
Status: RESOLVED DUPLICATE of bug 106757
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
5.4.1.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-10-17 19:21 UTC by umg
Modified: 2017-10-17 20:37 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description umg 2017-10-17 19:21:12 UTC
Description:
Everytime when I start to use the application and want to edit the master slide, libreoffice crashes with the following dialogue in the terminal:

Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.


I use Arch Linux (manjaro) and the libreoffice-fresh Also erst 

Steps to Reproduce:
1. Open Impress
2. Choose the master slides Tab on the right panel
3. right click on the actual master slide
4. Choose: Edit Master Slide
5. Crash

Actual Results:  
A tiny window with LibreOffice as title and just an OK as button appears. After clicking the OK button libreoffice crashes.
On the terminal (in case you start libreoffice impress via a terminal just with the command libreoffice --impress) you get the dialouge:

Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.



Expected Results:
Normally I expect that the master slide editor appears to edit the master slide


Reproducible: Always

User Profile Reset: No

Additional Info:
I use manjaro with XFCE


About Dialouge:
Version: 5.4.1.2.0+
Build-ID: 5.4.1-2
CPU-Threads: 4; Betriebssystem:Linux 4.9; UI-Render: Standard; VCL: gtk3; 
Gebietsschema: de-DE (de_DE.utf8); Calc: group


User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0
Comment 1 Xisco Faulí 2017-10-17 20:37:39 UTC

*** This bug has been marked as a duplicate of bug 106757 ***