Bug#1070736: Compose key broken in gnome-terminal (and others)

Another thing that might well be the same underlying problem: Using version 2.74.6-2+deb12u1, a Compose sequence like 'Compose " a' enters nothing in gnome-terminal and emacs. Using version 2.74.6-2, the same sequence enters an "ä". Arne

Bug#1070743: glib2.0: Can't type special characters in most applications

Source: glib2.0 Version: 2.80.0-10 Severity: critical Justification: breaks unrelated software X-Debbugs-Cc: ft.alban.hun...@mail.com After update do 2.80.0-10, I cannot type special (e.g. german umlaut letters) characters or dead keys in all gtk applications and most applications installed via

Bug#1070742: firefox: No characters after ~ (0x7f) in text zones

Package: firefox Version: 125.0.3-1 Severity: important Tags: upstream l10n Dear Maintainer, I restarted Firefox after a crash and now, in Firefox, I can’t write characters whose code are > 127. I suspect a third party library bug but as only Firefox is concerned… Yours, nicolas patrois P.S.:

Bug#1069256: Fwd: Bug#1069256: debian-policy: clarify requirement for use of Static-Built-Using

Hi all, I would greatly appreciate it if you could have a look at the proposal attached below to add a new section to the Debian Policy detailing the use of the Static- Built-Using and differentiating it from the Built-Using field. Could you please ensure that it aligns with your goals in the

Bug#1070699: workaround

gdb-minimal does not depend on libpython3.11.so.1.0 OpenPGP_signature.asc Description: OpenPGP digital signature

Bug#1070741: RM: python-karborclient -- ROM; unmaintained upstream, leaf package

Package: ftp.debian.org Severity: normal User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: python-karborcli...@packages.debian.org Control: affects -1 + src:python-karborclient Hi, Please remove python-karborclient from Debian. The upstream project has been dead for a long

Bug#1070740: autpkgtest failures for jtreg7 7.3.1+1-1

Package: jtreg7 Version: 7.3.1+1-1 Severity: normal Failures are reported for jtreg7 autopkgtest runs on Ubuntu [1]: 1066s warning: [path] bad path element "/usr/share/java/junit-platform-console-standalone.jar": no such file or directory 1066s error: warnings found and -Werror specified 1066s 1

Bug#1070739: bookworm-pu: package python-glance-store/4.1.0-4

Package: release.debian.org Severity: normal Tags: bookworm User: release.debian@packages.debian.org Usertags: pu X-Debbugs-Cc: python-glance-st...@packages.debian.org Control: affects -1 + src:python-glance-store [ Reason ] I would like to update python-glance-store/4.1.0-4 to

Bug#1070730: libglib2.0-0t64: also problems with Japanese input in chromium, firefox, discord

Package: libglib2.0-0t64 Version: 2.80.0-10 Followup-For: Bug #1070730 Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? upgrading libglib2.0-0t64 from 2.80.0-9 to 2.80.0-10 broke Japanese input with mozc to

Bug#1070738: ibus: mozc Japanese input fails in chromium, firefox, discord with libglib2.0 2.80.0-10 packages

Package: ibus Version: 1.5.29-2 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? upgrading libglib2.0 related packages from 2.80.0-9 to 2.80.0-10 chromium, firefox and discord refused to

Bug#1070724: tmux: take flock on socket file/dir in /tmp/

Hi Luca, Thanks for the heads up! Appreciate it. On Wed, May 8, 2024 at 1:33 AM Luca Boccassi wrote: > In order to avoid the /tmp/tmux-UID/default socket being deleted while > in use (e.g.: long term session), please patch tmux to take a flock(2) > on the directory while it's running, as per

Bug#1070730: ibus generally broken

I have the same issue with German and Finnish keyboard layouts via ibus (umlauts and other non-ASCII characters don't work) and ibus-anthy after the update from 2.80.0-9 to 2.80.0-10, downgrading fixes it. So it looks like that security fix breaks ibus with GTK applications in general. :-(

Bug#1070737: gr-gsm: FTBFS: 0xffff9e97794c: (std::vector >* std::__do_uninit_fill_n >*, unsigned long, std::vector

Source: gr-gsm Version: 1.0.0~20220727-1 Severity: serious Tags: ftbfs sid trixie X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=gr-gsm=arm64=1.0.0%7E20220727-1%2Bb11=1715152129=0 cd "/<>/obj-aarch64-linux-gnu/apps" && /usr/bin/cmake -E env

Bug#1070667: libssl3: Cannot remove system package:

I still cannot update. I have installed hyprland as a wm along with kde if that helps. All this is in a virtual machine so it is of no importance to me. I reported the issue for the general interest Odysseus Στάλθηκε από το iPhone μου > 8 Μαΐ 2024, 09:19, ο χρήστης «Sebastian Andrzej

Bug#1070736: libglib2.0-0: I could type in English, but I can't type in Russian, it works in the terminal if I press alt and the desired character, but if I don't press it the cursor stays still and

Package: libglib2.0-0 Version: 2.74.6-2 Severity: important X-Debbugs-Cc: mittw...@duck.com Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? updating * What exactly did you do (or not do) that was

Bug#1070735: micro-httpd: debian/copyright update attached

Source: micro-httpd Version: 20140814-3 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Authors for the Debian folder content are updated. See attachment. Martin-Éric - -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (900, 'unstable')

Bug#1070734: micro-httpd: Lintian-brush fixes attached

Source: micro-httpd Version: 20140814-3 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Please find attached some minor fixes performed by Lintian-brish. Martin-Éric -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmY7Gj0ACgkQrh+Cd8S0

Bug#1070667: libssl3: Cannot remove system package:

On 2024-05-07 12:20:51 [+0300], Odysseas Romanos wrote: > Old Trixie —> new trixie. Bug 1065135 seems unrelated to me. I am noob > to this so I apologize if I am not clear on my reporting That is okay. Just make sure you don't lose the Cc: so we have a public record. Now. We did (still do) have a

<    1   2