Bug#1039951: libreoffice-writer: First and last inner vertical borders in tables are invisible across all rows in Hebrew locale
Package: libreoffice-writer
Version: 4:7.4.5-3
Severity: normal
X-Debbugs-Cc: dhpe...@mailbox.org
Dear Maintainer,
This issue occures only when Formats -> Lacale setting is set to Hebrew, and
the app is restarted for the setting to take affect.
On other tested locale (English) it doesn't happen.
Simply adding a table will create one with fully visible border lines except
first and last inner vertical borders.
Trying to make them visible doesn't work. It applies to both rendered table and
printed file or exported PDF.
The visibility issue is dynamic. If you delete cells with problematic border,
it will switch to the new first/last inner border.
Tested current flatpak version 7.5.4.2. seems to fixed in it.
steps to reproduce: Change locale setting to Hebrew and restart. Simply add a
table.
-- Package-specific info:
Configuration filePackage Exists Changed
/etc/libreoffice/registry/writer.xcd libreoffice-writer Yes No
All deployed bundled extensions:
Identifier: com.sun.star.comp.Calc.NLPSolver
Version: 0.9
URL: vnd.sun.star.expand:$BUNDLED_EXTENSIONS/nlpsolver
is registered: yes
Media-Type: application/vnd.sun.star.package-bundle
Description: This extension integrates into Calc and offers new Solver
engines to use for optimizing nonlinear programming models.
bundled Packages: {
URL: vnd.sun.star.expand:$BUNDLED_EXTENSIONS/nlpsolver/help
is registered: yes
Media-Type: application/vnd.sun.star.help
Description:
URL: vnd.sun.star.expand:$BUNDLED_EXTENSIONS/nlpsolver/components.rdb
is registered: yes
Media-Type: application/vnd.sun.star.uno-components
Description:
}
Identifier: com.sun.wiki-publisher
Version: 1.2.0
URL: vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher
is registered: yes
Media-Type: application/vnd.sun.star.package-bundle
Description: The Wiki Publisher enables you to create Wiki articles on
MediaWiki servers without having to know the syntax of the MediaWiki markup
language. Publish your new and existing documents transparently with the Writer
to a wiki page.
bundled Packages: {
URL: vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher/help
is registered: yes
Media-Type: application/vnd.sun.star.help
Description:
URL:
vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher/WikiExtension.xcs
is registered: yes
Media-Type: application/vnd.sun.star.configuration-schema
Description:
URL: vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher/WikiEditor/
is registered: yes
Media-Type: application/vnd.sun.star.basic-library
Description:
URL: vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher/components.rdb
is registered: yes
Media-Type: application/vnd.sun.star.uno-components
Description:
URL: vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher/Addons.xcu
is registered: yes
Media-Type: application/vnd.sun.star.configuration-data
Description:
URL:
vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher/ProtocolHandler.xcu
is registered: yes
Media-Type: application/vnd.sun.star.configuration-data
Description:
URL:
vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher/WikiExtension.xcu
is registered: yes
Media-Type: application/vnd.sun.star.configuration-data
Description:
URL:
vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher/OptionsDialog.xcu
is registered: yes
Media-Type: application/vnd.sun.star.configuration-data
Description:
URL: vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher/Filter.xcu
is registered: yes
Media-Type: application/vnd.sun.star.configuration-data
Description:
URL: vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher/Types.xcu
is registered: yes
Media-Type: application/vnd.sun.star.configuration-data
Description:
URL: vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher/Paths.xcu
is registered: yes
Media-Type: application/vnd.sun.star.configuration-data
Description:
}
All deployed shared extensions:
All deployed user extensions:
Experimental features enabled:
Installed VCLplugs:
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++----=
un libreoffice-gtk3 (no description available)
ii libreoffice-kf5 4:7.4.5-3amd64office productivity suite -- KDE
Frameworks 5 integration
ii libreoffice-qt5 4:7.4.5-3amd64office productivity suite -- Qt
5 integration
Java (javaldx):
Bug#985543: Problem resolved, details below
I'd like to report that after an update I did just now the problem is resolved. I don't know what really caused it but I'm adding a list of the updated packages: Start-Date: 2021-03-22 19:17:34 Commandline: packagekit role='update-packages' Upgrade: udev:amd64 (247.3-1, 247.3-3), libnss-myhostname:amd64 (247.3-1, 247.3-3), systemd-timesyncd:amd64 (247.3-1, 247.3-3), libpam-systemd:amd64 (247.3-1, 247.3-3), libsystemd0:amd64 (247.3-1, 247.3-3), libnss-systemd:amd64 (247.3-1, 247.3-3), systemd:amd64 (247.3-1, 247.3-3), libudev1:amd64 (247.3-1, 247.3-3), systemd-sysv:amd64 (247.3-1, 247.3-3) End-Date: 2021-03-22 19:17:53 so maybe it was a udev rule? I don't really know how to check, if it even necessary. but I guess this bug can be closed? Thank you for your affords and attention! Daniel OpenPGP_signature Description: OpenPGP digital signature
Bug#985543: yubikey-luks: after upgrade and reboot - yubikey "not detected" (but blinking)
> Could you share a few details? > > * dpkg -l "*yubi*" > * dpkg -l "*cryptsetup*" > * cat /etc/crypttab > * Screenshots of the prompt, error messages, maybe boot in recovery mode * dpkg -l "*yubi*" | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-===-===--=== ii libyubikey-udev 1.20.0-3 all udev rules for unprivileged access to YubiKeys ii libyubikey0 1.13-6 amd64 Yubikey OTP handling library runtime ii python3-yubikey-manager 4.0.0~a1-2 all Python 3 library for configuring a YubiKey — transitional package ii yubikey-luks 0.5.1+29.g5df2b95-6 all YubiKey two factor authentication for LUKS disks ii yubikey-personalization 1.20.0-3 amd64 Personalization tool for Yubikey OTP tokens ii yubioath-desktop 5.0.4+post1-1 amd64 Graphical interface for displaying OATH codes with a Yubikey * dpkg -l "*cryptsetup*" | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=---=== ii cryptsetup 2:2.3.4-2 amd64 disk encryption support - startup scripts ii cryptsetup-bin 2:2.3.4-2 amd64 disk encryption support - command line tools ii cryptsetup-initramfs 2:2.3.4-2 all disk encryption support - initramfs integration ii cryptsetup-run 2:2.3.4-2 all transitional dummy package for cryptsetup ii libcryptsetup12:amd64 2:2.3.4-2 amd64 disk encryption support - shared library * cat /etc/crypttab sda3_crypt UUID=18a87353-c256-4da6-88ab-6ac75b0d84ce none luks,discard,keyscript=/usr/share/yubikey-luks/ykluks-keyscript thank you! Daniel OpenPGP_signature Description: OpenPGP digital signature
Bug#985543: yubikey-luks: after upgrade and reboot - yubikey "not detected" (but blinking)
On Sat, 20 Mar 2021 12:29:56 -0400 Jerome Charaoui wrote: > user debian-rele...@lists.debian.org > usertags 985543 + bsp-2021-03-ca-montreal > tag 985543 + unreproducible moreinfo > thank you > > Hello, > > I've attempted, but was unable, to reproduce this bug. > > I set up the yubikey-luks challenge-response on a fresh stretch system, > and after upgrading to bullseye, it was working as before, which > suggests the package is working as intended even after a release upgrade. > > I'm wondering if your bug could actually be related to an update in the > kernel or usb subsystem itself, rather than the yubikey-luks package? > > Did you try booting up using a live system such as Grml and trying to > unlock your luks filesystem manually in that environment? > > Thanks. > > Hi, First of all thank you for your afford! I successfully managed to unlock my LUKS partition by generating the response on a different machine (with package 'ykpersonalize' using the command 'ykchalresp') and typing it manually. the system was updated as I thought. My system recognized my yubikey when it was unlocked and I could do the usual operation I'm using it for. the chalresp OTP slot works as usual as well for other oprations. Tried to do another update and rebooted the system, still no luck with the yubikey itself. As for your suggestion, I'll try to unlock it with the yubikey-luks package on a live system and report back. thank you very much, Daniel OpenPGP_signature Description: OpenPGP digital signature
Bug#985543: yubikey-luks: after upgrade and reboot - yubikey "not detected" (but blinking)
Hi, First of all thank you for your afford! I successfully managed to unlock my LUKS partition by generating the response on a different machine (with package 'ykpersonalize' using the command 'ykchalresp') and typing it manually. the system was updated as I thought. My system recognized my yubikey when it was unlocked and I could do the usual operation I'm using it for. the chalresp OTP slot works as usual as well for other oprations. Tried to do another update and rebooted the system, still no luck with the yubikey itself. As for your suggestion, I'll try to unlock it with the yubikey-luks package on a live system and report back. thank you very much, Daniel OpenPGP_signature Description: OpenPGP digital signature
Bug#985543: yubikey-luks: after upgrade and reboot - yubikey "not detected" (but blinking)
Package: yubikey-luks Version: 0.5.1+29.g5df2b95-6 Severity: grave Justification: causes non-serious data loss X-Debbugs-Cc: dhpe...@mailbox.org Dear Maintainer, Yesterday I (mostly sure, cannot verify as I'm locked out of my system) upgraded the package on a debian bullseye machine. I booted up my machine after that but my yubikey isn't detected. the Yubikey flashes when I connect it to indicate that it's on. I tried different USB ports. tried booting with it connected beforehand and tried connecting after promped to. nothing changed. in summary, i'm promped to enter yubikey and chalenge, im typing my challenge and press enter, yet it says no Yubikey found. this bug report is sent from another machine! -- System Information: Debian Release: bullseye/sid APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-4-amd64 (SMP w/2 CPU threads) Locale: LANG=en_IL, LC_CTYPE=en_IL (charmap=UTF-8), LANGUAGE=en_IL:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages yubikey-luks depends on: pn cryptsetup-run ii initramfs-tools 0.139 ii yubikey-personalization 1.20.0-3 Versions of packages yubikey-luks recommends: pn cryptsetup-initramfs pn expect yubikey-luks suggests no packages.
