Your message dated Mon, 23 Jul 2018 17:50:15 +0200 with message-id <20180723155015.ga1...@rene-engelhard.de> and subject line Re: Bug#894153: the bugs seems to be fixed now has caused the Debian Bug report #894153, regarding libreoffice-common: crash on writer, calc and impress when entering unicode codes with Ctrl-U, even for ASCII characters to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 894153: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894153 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: libreoffice-common Version: 1:6.0.2-1 Severity: normal Dear Maintainer, Since version 6, all libreoffice programs crash immediately when trying to enter characters using their unicode encoding with a Ctrl-U sequence. I used this a lot for entering greek letters in scientific documents (Ctrl-U 0 3 B 1 gives alpha: α for example) or for some typesettings characters (Ctrl-U 2 0 2 6 gives the ellipsis …). The Ctrl-U encoding still works on all applications, like terminal or event reportbug as I just used it above), but now it crashes libreoffice immediately. How to reproduce: 1) from the command line, run "libreoffice" 2) in the window, select "Create: writer document" 3) in the body of the empty "Untitled 1" document, type Ctrl-U 6 1 4) libreoffice crashes and propose to attempt recovery of the untitled document 5) after recovery, the document is still empty The hexadecimal code given in the procedure above 0x61, represents the ASCII character 'a', so it is not a problem of encoding or fonts or anything like this. The crash occurs for all characters I tried. I tried to see if it was linked to the non-ASCII characters, but this is not the case. If I type the codes above, even for greek or typesettings characters in a terminal window and then copy-paste the character in Libreoffice, the character is displayed correctly. The crash seems related to the fact I enter them from keyboard with the Ctrl-U prefix, which is pretty much standard nowadays for other Debian applications. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libreoffice-common depends on: ii libreoffice-style-tango 1:6.0.2-1 ii ure 6.0.2-1+b1 Versions of packages libreoffice-common recommends: ii fonts-liberation2 2.00.1-5 ii libexttextcat-data 3.4.5-1 ii python3-uno 1:6.0.2-1+b1 ii xdg-utils 1.1.2-2 Versions of packages libreoffice-common suggests: ii libreoffice-style-galaxy [libreoffice-style] 1:6.0.2-1 ii libreoffice-style-tango [libreoffice-style] 1:6.0.2-1 Versions of packages python3-uno depends on: ii libc6 2.27-2 ii libgcc1 1:8-20180312-2 ii libpython3.6 3.6.5~rc1-1 ii libreoffice-core 1:6.0.2-1+b1 ii libstdc++6 8-20180312-2 ii python3 3.6.4-1 ii python3.6 3.6.5~rc1-1 ii uno-libs3 6.0.2-1+b1 ii ure 6.0.2-1+b1 -- no debconf information
--- End Message ---
--- Begin Message ---Version: 1:6.1.0~rc2-1 On Mon, Jul 23, 2018 at 04:40:58PM +0200, Luc Maisonobe wrote: > Le 23/07/2018 ?? 15:23, Rene Engelhard a ??crit??: > > On Fri, Jul 20, 2018 at 11:07:40AM +0200, Rene Engelhard wrote: > > > close 89153 1:6.0.6~rc1-1 > > > thanks > > [...] > > > What about the 6.1.0 rc1 in experimental? Is it fixed there, too? > > I didn't find 6.1.0 in the experimental repository for the amd64 > architecture, it was still 1:6.0.6~rc1-1 (6.1.0 was there only > for ppc64 and alpha architectures). Nope. It's there for amd64 since the beginning. Definitely at the time of writing otherwise I wouldn't have written that. > > > > (or only in rc2 - which isn't officially released yet). Since > > [...] > > > (I plan to upload said 6.1.0 rc2 to unstable soonish after it "survived" > > > a test build in experimenal when it's there and uploaded.) > > > > Ping? :) > > > > That now happened. > > OK, I have tried this 6.1.0~rc2-2 from unstable. The unicode > input shortcut works. OK, thanks. > > Would try myself, but apparently I am not skkilled anpough to actually > > make Ctrl-U 61 print anything else than a "61". How are you supposed to > > do that? > > Maybe you forgot the "shift"? I used uppercase U in the description > of the shortcut to denote that, it was probably not explicit, sorry. > I should probably have written it as Ctrl-Shift-U. See > <https://en.wikipedia.org/wiki/Unicode_input#In_X11_(Linux_and_Unix_variants)> > or > <https://help.gnome.org/users/gnome-help/stable/tips-specialchars.html.en#ctrlshiftu>. > Once you have entered the prefix > Ctrl-shift-u, an underlined 'u' should appear to show that the > next character will be a unicode code point, and this undelined u should > disappear when you enter the code point (in hexadecimal) and end b .. and keep Ctrl-Shift pressed... Yeah.. Anyway, fixed -> closing. Regards, Rene
--- End Message ---
