When editing a presentation and inserting a GIF image containing a * inside the name the open file dialog wipes out all other files and refuses to load the GIF. Removing the * from the filename is a valid work around for this bug How to reproduce: Open a presentation->Insert->Image->Select a GIF file containing an asterisk in its name->Try to open it
No repro with Version: 6.3.0.0.alpha0+ Build ID: c7ad7849d54fd3dad67e7779102f65b8b2f04881 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; filename G*MARBLES.GIF Please specify LO version and your operating system.
(In reply to raal from comment #1) > No repro with Version: 6.3.0.0.alpha0+ > Build ID: c7ad7849d54fd3dad67e7779102f65b8b2f04881 > CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; > > filename G*MARBLES.GIF > > Please specify LO version and your operating system. Version: 6.0.7.3.0+ Build ID: FreeBSD ports 6.0.7_6 CPU threads: 4; OS: FreeBSD 12.0; UI render: default; VCL: gtk2;
No repro. Tried with gtk2 as an attempt to match reporter's system. Leon: are you able to try with version 6.2.x? Otherwise it seems like some quirk specific to the FreeBSD build. Arch Linux 64-bit Version: 6.4.0.0.alpha0+ Build ID: 4bd1b38633d6cb288eb559afc0ac6b961538ae60 CPU threads: 8; OS: Linux 5.2; UI render: default; VCL: gtk2; Locale: fi-FI (fi_FI.UTF-8); UI-Language: en-US Calc: threaded Built on 24 July 2019
(In reply to Buovjaga from comment #3) > No repro. Tried with gtk2 as an attempt to match reporter's system. > > Leon: are you able to try with version 6.2.x? > > Otherwise it seems like some quirk specific to the FreeBSD build. > > Arch Linux 64-bit > Version: 6.4.0.0.alpha0+ > Build ID: 4bd1b38633d6cb288eb559afc0ac6b961538ae60 > CPU threads: 8; OS: Linux 5.2; UI render: default; VCL: gtk2; > Locale: fi-FI (fi_FI.UTF-8); UI-Language: en-US > Calc: threaded > Built on 24 July 2019 Running ➜ libreoffice --version LibreOffice 6.2.5.2 20(Build:2) The bug is unfortunately still persistent.
I asked on #freebsd @ freenode and a user with 6.2.5 agreed to test. There was no problem. They were running LibreOffice under Lumina desktop (Project Trident distro). Info from Help - About was build freebsd ports 6.2.5 cpu threads: 4; os: freebsd 13.0; ui render: default; vcl: gtk2 Leon: which desktop environment are you running?
(In reply to Buovjaga from comment #5) > I asked on #freebsd @ freenode and a user with 6.2.5 agreed to test. There > was no problem. They were running LibreOffice under Lumina desktop (Project > Trident distro). > > Info from Help - About was > build freebsd ports 6.2.5 > cpu threads: 4; os: freebsd 13.0; ui render: default; vcl: gtk2 > > Leon: which desktop environment are you running? I'm running i3. Shall I upload a video demonstrating the bug somewhere?
(In reply to Leon Dietrich from comment #6) > (In reply to Buovjaga from comment #5) > > Leon: which desktop environment are you running? > > I'm running i3. Shall I upload a video demonstrating the bug somewhere? If you can keep it under 30MB, you can upload it as an attachment to this bug report.
no repro here with Version: 6.3.4.2.0+ on Debian 10 bullseye-backports Build-ID: 1:6.3.4-2 CPU-Threads: 2; BS: Linux 5.3; UI-Render: Standard; VCL: kde5; Gebietsschema: de-DE (de_DE.UTF-8); UI-Sprache: de-DE Calc: threaded file system is ext4
Hello Leon, Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? 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.
(In reply to Xisco Faulí from comment #9) > Hello Leon, > Could you please try to reproduce it with the latest version of LibreOffice > from https://www.libreoffice.org/download/libreoffice-fresh/ ? > 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. Hi, I cannot reproduce this bug with the new version anymore. Since then I migrated from i3/xorg to sway/wayland though. So I also tested it with a virtual machine still running xorg. I couldn't reproduce it there either anymore so I guess it has been fixed.
(In reply to Leon Dietrich from comment #10) > (In reply to Xisco Faulí from comment #9) > > Hello Leon, > > Could you please try to reproduce it with the latest version of LibreOffice > > from https://www.libreoffice.org/download/libreoffice-fresh/ ? > > 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. > > Hi, > I cannot reproduce this bug with the new version anymore. Since then I > migrated from i3/xorg to sway/wayland though. So I also tested it with a > virtual machine still running xorg. I couldn't reproduce it there either > anymore so I guess it has been fixed. Thanks for retesting the issue with the latest version. Setting to RESOLVED WORKSFORME since the commit fixing this issue hasn't been identified.