Bug#1072211: texlive-base: pdflatex very slow after upgrading to texlive 2024.20240401-2
El jue, 30 may 2024 a las 17:04, Norbert Preining () escribió: > > On Thu, 30 May 2024, J.L.G. Pallero wrote: > > After the last upgrade of texlive packages in Sid, from 2023.20240207-1 to > > 2024.20240401-2, I found pdflatex very slow in the compilation. The same > > documents > > compiled with the 2023.20240207-1 version were bult quicker. Is it a > > problem on my side or is a generalbehavior? > > Do you have a test document that you can share? I'm working on a voluminous book and it is not practical to share > > Also, the output of running the compile command with > pdflatex -kpathsea-debug= > might help, but that can get considerably volominous. I can't understand exactly the use of -kpathsea-debug=. What means ? Is a path for a file? If I put a path for a file it isn't created anything and the log file created after the compilation is the same as without -kpathsea-debug. Note also that the problem is not that Texlive 2024 is slow, but that 2024.20240401-2 is slower than 2023.20240207-1 Thanks > > Best regards > > Norbert > > -- > PREINING Norbert https://www.preining.info > arXiv / Cornell University + IFMGA Guide + TU Wien + TeX Live > GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13 -- * José Luis García Pallero jgpall...@gmail.com (o< / / \ V_/_ Use Debian GNU/Linux and enjoy! *
Bug#1070978: firefox: Spanish keyboard layout not working properly
Package: firefox Version: 125.0.3-1+b1 Severity: minor Tags: l10n X-Debbugs-Cc: josel.seg...@gmx.es Dear Maintainer, In a Gnome environment, when using the Spanish layout, the "ñ" letter and some of the accents that usually works as dead-keys are not working, just being ignored. I tried with other applications like nautilus, Tilix terminal or Telegram and it works correctly, so I discarded a system configuration issue. If this can help, I found the exactly same behaviour in other Mozilla software, Thunderbird, so maybe it's related to some dependency used by both, but I cannot figure which one. * What led up to the situation? Just a normal upgrade on my system. -- Package-specific info: -- Addons package information -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.12-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages firefox depends on: ii debianutils 5.17 ii fontconfig 2.15.0-1.1 ii libasound2t641.2.11-1+b1 ii libatk1.0-0t64 2.52.0-1 ii libc62.38-11 ii libcairo-gobject21.18.0-3+b1 ii libcairo21.18.0-3+b1 ii libdbus-1-3 1.14.10-4+b1 ii libevent-2.1-7t642.1.12-stable-8.1+b3 ii libffi8 3.4.6-1 ii libfontconfig1 2.15.0-1.1 ii libfreetype6 2.13.2+dfsg-1+b4 ii libgcc-s114-20240429-1 ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-3+b3 ii libglib2.0-0t64 2.80.2-1 ii libgtk-3-0t643.24.41-4 ii libnspr4 2:4.35-1.1+b1 ii libnss3 2:3.99-1 ii libpango-1.0-0 1.52.2+ds-1 ii libstdc++6 14-20240429-1 ii libvpx9 1.14.0-2 ii libx11-6 2:1.8.7-1+b1 ii libx11-xcb1 2:1.8.7-1+b1 ii libxcb-shm0 1.17.0-1 ii libxcb1 1.17.0-1 ii libxcomposite1 1:0.4.5-1+b1 ii libxdamage1 1:1.1.6-1+b1 ii libxext6 2:1.3.4-1+b1 ii libxfixes3 1:6.0.0-2+b1 ii libxrandr2 2:1.5.4-1 ii procps 2:4.0.4-4 ii zlib1g 1:1.3.dfsg+really1.3.1-1 Versions of packages firefox recommends: ii libavcodec58 7:4.4.2-1+b3 ii libavcodec60 7:6.1.1-4+b1 Versions of packages firefox suggests: ii fonts-lmodern 2.005-1 ii fonts-stix [otf-stix] 1.1.1-5 ii libcanberra0 0.30-17 ii libgssapi-krb5-2 1.20.1-6+b1 pn pulseaudio -- no debconf information
Bug#1068597: quodlibet: most Explore options are brain damaged
Package: quodlibet Version: 4.5.0-2 Severity: important Most Explore options are unsuitable for a collection or records that is larger than just infimal. Browsing just by album, which is essentially the view available besides filesystem, is unmanageable with a regular collection. A tree interface is mandatory for music, including the regular views: Genre, Album artist, Artist, Album, File, etc.. Obviously only the Album and File views are the ones that should be flat, otherwise Artist views have a second level of Albums, and Genre has a second view of Album artist, Artist, Album, or File views, etc. Important severity because the program is unmanageable with more than just a beginner collection.
Bug#1068596: less: word line wrap missing
Package: less Version: 590-2 Severity: important The option to wrap lines by words, not characters, is missing from v 12 less. This must has been in less, at least, at some point. If not feel free to lower severity to whishlist.
Bug#1068595: libreoffice-writer: insert space missing
Package: libreoffice-writer Version: 4:7.4.7-1+deb12u1 Severity: important Hi, Space insertion is missing in the insert menu. Best regards, JL
Bug#1068479: libreoffice-writer: space between paragraphs missing in spacing and indentation
Package: libreoffice-writer Version: 4:7.4.7-1+deb12u1 Severity: serious The setting for spacing between paragraphs is missing in the spacing and indentation tab of the paragraph dialog. Serious severity because the bug has a major effect on the usability of the package, without rendering it completely unusable, considering paragraphs are a key feature in a word processor, and spacing is something very very basic for them and incredibly necessary.
Bug#1067715: closed by yokota (Re: Bug#1067715: calibre: doesn't install DeACSM plugin)
reopen 1067715 tags 1067715 + fixed-upstream thanks On Thu, 28 Mar 2024 15:15:05 + "Debian Bug Tracking System" wrote: > This is an automatic notification regarding your Bug report > which was filed against the calibre package: > > #1067715: calibre: doesn't install DeACSM plugin > > It has been closed by yokota . > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact yokota > by > replying to this email. > «This bug is now closed because it was already fixed on upstream development code.» Yokota, Please, don't close bugs just because they are fixed upstream, the fixed-upstream exists exactly for this. The report shall remain open until the bug is fixed on all currently published Debian releases. I don't know yet whether the fix is already on an official Calibre release, or just on their development repository. What I have no doubt is the bug is still present on stable (bookworm), so until it gets fixed there this report shall remain open. Feel free to tag it for bookworkm, bullseye and buster appropriately if the fix is already into testing and unstable. Thanks a lot for your understanding and your effort at maintaining the package. Best regards, José Luis
Bug#1067715: calibre: doesn't install DeACSM plugin
On Wed, 27 Mar 2024 08:28:34 +0900 yokota wrote: > Hello, José. Hi, > > oscrypto.errors.LibraryNotFoundError: Error detecting the version of > > libcrypto > > This bug was already fixed on DeACSM upstream development code. > Try it from DeACSM plugin forum. > https://www.mobileread.com/forums/showpost.php?p=4157570=2 > https://www.mobileread.com/forums/showthread.php?t=341975 > > FYI: DeACSM plugin was renamed to ACSMInput plugin. > > Use "calibre-customize --add-plugin FILE_PATH" to install plugins from > local path. > https://manual.calibre-ebook.com/generated/en/calibre-customize.html Thanks a lot for the information, really. I will try it when I have the time. Cheers!
Bug#1067719: RFP: libgourou and utils -- free implementation of Adobe's ADEPT protocol used to add DRM on ePub/PDF files
Package: wnpp Version: unspecified Severity: wishlist Upstream Author: Grégory Soutadé URL: https://forge.soutade.fr/soutade/libgourou/ License: LGPL3 / BSD X-Debbugs-CC: debian-de...@lists.debian.org Description: libgourou is a free implementation of Adobe's ADEPT protocol used to add DRM on ePub/PDF files. It overcame the lack of Adobe support for Linux platforms. It's the first tool for free systems to be able to read Adobe DRM protected ebooks (the industry standard for purchases and library loans), and add them to your ereader. It permits: - Downloading an ePub/PDF from ACSM file - Exporting your private key (for DeDRM software) - Removing ADEPT DRM - List loaned books - Return a loaned book
Bug#1067715: calibre: doesn't install DeACSM plugin
Package: calibre
Version: 6.13.0+repack-2+deb12u3
Severity: important
I am unable to install the DeACSM plugin. It gives the following errors:
calibre, version 6.13.0
ERROR: Fallo en la instalación del complemento: Ha ocurrido un error al
instalar este complemento y a continuación se desinstalará. Por favor, publique
el mensaje de error que aparece en los detalles de más abajo en la conversación
del foro para este complemento y reinicie calibre.
Traceback (most recent call last):
File "/usr/lib/calibre/calibre/customize/ui.py", line 677, in
initialize_plugin
p.initialize()
File "calibre_plugins.deacsm.__init__", line 226, in initialize
from libadobe import createDeviceKeyFile, update_account_path,
sendHTTPRequest
File "/tmp/calibre_6.13.0_tmp_bazwlmj0/szujnx8a.zip/libadobe.py", line 59, in
from oscrypto import keys
File
"/home/jlg/.config/calibre/plugins/DeACSM/modules/oscrypto/oscrypto/keys.py",
line 5, in
from ._asymmetric import parse_certificate, parse_private, parse_public
File
"/home/jlg/.config/calibre/plugins/DeACSM/modules/oscrypto/oscrypto/_asymmetric.py",
line 27, in
from .kdf import pbkdf1, pbkdf2, pkcs12_kdf
File
"/home/jlg/.config/calibre/plugins/DeACSM/modules/oscrypto/oscrypto/kdf.py",
line 9, in
from .util import rand_bytes
File
"/home/jlg/.config/calibre/plugins/DeACSM/modules/oscrypto/oscrypto/util.py",
line 14, in
from ._openssl.util import rand_bytes
File
"/home/jlg/.config/calibre/plugins/DeACSM/modules/oscrypto/oscrypto/_openssl/util.py",
line 6, in
from ._libcrypto import libcrypto, libcrypto_version_info,
handle_openssl_error
File
"/home/jlg/.config/calibre/plugins/DeACSM/modules/oscrypto/oscrypto/_openssl/_libcrypto.py",
line 24, in
from ._libcrypto_ctypes import (
File
"/home/jlg/.config/calibre/plugins/DeACSM/modules/oscrypto/oscrypto/_openssl/_libcrypto_ctypes.py",
line 47, in
raise LibraryNotFoundError('Error detecting the version of libcrypto')
oscrypto.errors.LibraryNotFoundError: Error detecting the version of libcrypto
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/calibre/calibre/gui2/dialogs/plugin_updater.py", line 710, in
_install_clicked
plugin = add_plugin(zip_path)
File "/usr/lib/calibre/calibre/customize/ui.py", line 487, in add_plugin
plugin = initialize_plugin(plugin, path_to_zip_file,
PluginInstallationType.EXTERNAL)
File "/usr/lib/calibre/calibre/customize/ui.py", line 682, in
initialize_plugin
raise InvalidPlugin((_('Initialization of plugin %s failed with traceback:')
calibre.customize.InvalidPlugin: La inicialización del complemento Traceback
(most recent call last):
File "/usr/lib/calibre/calibre/customize/ui.py", line 677, in
initialize_plugin
p.initialize()
File "calibre_plugins.deacsm.__init__", line 226, in initialize
from libadobe import createDeviceKeyFile, update_account_path,
sendHTTPRequest
File "/tmp/calibre_6.13.0_tmp_bazwlmj0/szujnx8a.zip/libadobe.py", line 59, in
from oscrypto import keys
File
"/home/jlg/.config/calibre/plugins/DeACSM/modules/oscrypto/oscrypto/keys.py",
line 5, in
from ._asymmetric import parse_certificate, parse_private, parse_public
File
"/home/jlg/.config/calibre/plugins/DeACSM/modules/oscrypto/oscrypto/_asymmetric.py",
line 27, in
from .kdf import pbkdf1, pbkdf2, pkcs12_kdf
File
"/home/jlg/.config/calibre/plugins/DeACSM/modules/oscrypto/oscrypto/kdf.py",
line 9, in
from .util import rand_bytes
File
"/home/jlg/.config/calibre/plugins/DeACSM/modules/oscrypto/oscrypto/util.py",
line 14, in
from ._openssl.util import rand_bytes
File
"/home/jlg/.config/calibre/plugins/DeACSM/modules/oscrypto/oscrypto/_openssl/util.py",
line 6, in
from ._libcrypto import libcrypto, libcrypto_version_info,
handle_openssl_error
File
"/home/jlg/.config/calibre/plugins/DeACSM/modules/oscrypto/oscrypto/_openssl/_libcrypto.py",
line 24, in
from ._libcrypto_ctypes import (
File
"/home/jlg/.config/calibre/plugins/DeACSM/modules/oscrypto/oscrypto/_openssl/_libcrypto_ctypes.py",
line 47, in
raise LibraryNotFoundError('Error detecting the version of libcrypto')
oscrypto.errors.LibraryNotFoundError: Error detecting the version of libcrypto
falló y generó la siguiente traza:
Traceback (most recent call last):
File "/usr/lib/calibre/calibre/customize/ui.py", line 677, in
initialize_plugin
p.initialize()
File "calibre_plugins.deacsm.__init__", line 226, in initialize
from libadobe import createDeviceKeyFile, update_account_path,
sendHTTPRequest
File "/tmp/calibre_6.13.0_tmp_bazwlmj0/szujnx8a.zip/libadobe.py", line 59, in
from oscrypto import keys
File
"/home/jlg/.config/calibre/plugins/DeACSM/modules/oscrypto/oscrypto/keys.py",
line 5, in
Bug#1066040: gFTP doesn't set columns width automatically, wasting space
Package: gftp-gtk Version: 2.9.1~beta-1+b1 gFTP sets its connection columns to widths that don't adjust to the column contents and have arbitrary unnecessary space, forcing the user to set them manually. Usability bug, most likely in upstream. Best regards
Bug#1066037: gFTP doesn't honour Overwrite by omission in bookmarks
Package: gftp-gtk Version: 2.9.1~beta-1+b1 I have "Overwrite by omission" set in a bookmark's preferences, but it gets ignored all the time by gFTP in this very bookmark, setting Resume instead.
Bug#1064188: mrpt: NMU diff for 64-bit time_t transition
Hi Steve, As package and upstream's maintainer, what should I do to ensure the library is change safe? Would it help to totally remove references to time_t in all public headers? El dom, 18 feb 2024, 9:00, Steve Langasek escribió: > Source: mrpt > Version: 1:2.11.9+ds-1 > Severity: important > Tags: patch pending sid trixie > User: debian-...@lists.debian.org > Usertags: time-t > > NOTICE: these changes must not be uploaded to unstable yet! > > Dear maintainer, > > As part of the 64-bit time_t transition required to support 32-bit > architectures in 2038 and beyond > (https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified > mrpt as a source package shipping runtime libraries whose ABI > either is affected by the change in size of time_t, or could not be > analyzed via abi-compliance-checker (and therefore to be on the safe > side we assume is affected). > > To ensure that inconsistent combinations of libraries with their > reverse-dependencies are never installed together, it is necessary to > have a library transition, which is most easily done by renaming the > runtime library package. > > Since turning on 64-bit time_t is being handled centrally through a change > to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is > important that libraries affected by this ABI change all be uploaded close > together in time. Therefore I have prepared a 0-day NMU for mrpt > which will initially be uploaded to experimental if possible, then to > unstable after packages have cleared binary NEW. > > Please find the patch for this NMU attached. > > If you have any concerns about this patch, please reach out ASAP. Although > this package will be uploaded to experimental immediately, there will be a > period of several days before we begin uploads to unstable; so if > information > becomes available that your package should not be included in the > transition, > there is time for us to amend the planned uploads. > > > > -- System Information: > Debian Release: trixie/sid > APT prefers unstable > APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, > 'experimental') > Architecture: amd64 (x86_64) > > Kernel: Linux 6.5.0-14-generic (SMP w/12 CPU threads; PREEMPT) > Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE > Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) >
Bug#1065010: libkf5kdelibs4support-data: Install and uninstall packages
Package: libkf5kdelibs4support-data Version: 5.107.0-1 Severity: normal Dear Maintainer, The problem now is that, apparently, having this update, I have been forced to uninstall packages that have unfulfilled dependencies on this package. And the packages that I had to uninstall (for the moment), are these: kaddressbook; kmail; knotes; libkf5akonadisearch-bin; libkf5akonadisearch- plugins; libkf5akonadisearchcore5; libkf5akonadisearchxapian5. So I know that I can wait a little while for new packages to come out to fix these problems. On the other hand, of the packages mentioned above, others are 'almost done', because I get new packages with t64, but it turns out that they are not complete. I know I can wait for them to appear in full. I'm afraid I'll have to reinstall from scratch with all the packages I have so far. I have faith that the full fixed packages will arrive between this week and next week. I don't need KMail, because I use another email client. I am aware that you are making the transition as painless as possible for everyone. Thank you very much, and with that, I wait patiently. -- System Information: Debian Release: trixie/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.6.15-amd64 (SMP w/12 CPU threads; PREEMPT) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE=es Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- no debconf information -- debsums errors found: debsums: missing file /usr/share/locale/af/LC_MESSAGES/kdelibs4support.mo (from libkf5kdelibs4support-data package) debsums: missing file /usr/share/locale/ar/LC_MESSAGES/kdelibs4support.mo (from libkf5kdelibs4support-data package) debsums: missing file /usr/share/locale/as/LC_MESSAGES/kdelibs4support.mo (from libkf5kdelibs4support-data package) debsums: missing file /usr/share/locale/az/LC_MESSAGES/kdelibs4support.mo (from libkf5kdelibs4support-data package) debsums: missing file /usr/share/locale/be/LC_MESSAGES/kdelibs4support.mo (from libkf5kdelibs4support-data package) debsums: missing file /usr/share/locale/be@latin/LC_MESSAGES/kdelibs4support.mo (from libkf5kdelibs4support-data package) debsums: missing file /usr/share/locale/bg/LC_MESSAGES/kdelibs4support.mo (from libkf5kdelibs4support-data package) debsums: missing file /usr/share/locale/bn/LC_MESSAGES/kdelibs4support.mo (from libkf5kdelibs4support-data package) debsums: missing file /usr/share/locale/bn_IN/LC_MESSAGES/kdelibs4support.mo (from libkf5kdelibs4support-data package) debsums: missing file /usr/share/locale/br/LC_MESSAGES/kdelibs4support.mo (from libkf5kdelibs4support-data package) debsums: missing file /usr/share/locale/bs/LC_MESSAGES/kdelibs4support.mo (from libkf5kdelibs4support-data package) debsums: missing file /usr/share/locale/ca/LC_MESSAGES/kdelibs4support.mo (from libkf5kdelibs4support-data package) debsums: missing file /usr/share/locale/ca@valencia/LC_MESSAGES/kdelibs4support.mo (from libkf5kdelibs4support-data package) debsums: missing file /usr/share/locale/crh/LC_MESSAGES/kdelibs4support.mo (from libkf5kdelibs4support-data package) debsums: missing file /usr/share/locale/cs/LC_MESSAGES/kdelibs4support.mo (from libkf5kdelibs4support-data package) debsums: missing file /usr/share/locale/csb/LC_MESSAGES/kdelibs4support.mo (from libkf5kdelibs4support-data package) debsums: missing file /usr/share/locale/cy/LC_MESSAGES/kdelibs4support.mo (from libkf5kdelibs4support-data package) debsums: missing file /usr/share/locale/da/LC_MESSAGES/kdelibs4support.mo (from libkf5kdelibs4support-data package) debsums: missing file /usr/share/locale/de/LC_MESSAGES/kdelibs4support.mo (from libkf5kdelibs4support-data package) debsums: missing file /usr/share/locale/el/LC_MESSAGES/kdelibs4support.mo (from libkf5kdelibs4support-data package) debsums: missing file /usr/share/locale/en_GB/LC_MESSAGES/kdelibs4support.mo (from libkf5kdelibs4support-data package) debsums: missing file /usr/share/locale/eo/LC_MESSAGES/kdelibs4support.mo (from libkf5kdelibs4support-data package) debsums: missing file /usr/share/locale/et/LC_MESSAGES/kdelibs4support.mo (from libkf5kdelibs4support-data package) debsums: missing file /usr/share/locale/eu/LC_MESSAGES/kdelibs4support.mo (from libkf5kdelibs4support-data package) debsums: missing file /usr/share/locale/fa/LC_MESSAGES/kdelibs4support.mo (from libkf5kdelibs4support-data package) debsums: missing file /usr/share/locale/fi/LC_MESSAGES/kdelibs4support.mo (from libkf5kdelibs4support-data package) debsums: missing file /usr/share/locale/fr/LC_MESSAGES/kdelibs4support.mo (from libkf5kdelibs4support-data package) debsums: missing file /usr/share/locale/fy/LC_MESSAGES/kdelibs4support.mo (from libkf5kdelibs4support-data package) debsums: missing file /usr/share/locale/ga/LC_MESSAGES/kdelibs4support.mo (from libkf5kdelibs4support-data package)
Bug#1043571: Bugs related to #1062189
Hello, After further investigations, my report is related to this : #1062189 Thank you.
Bug#1043571: simple-cdd: Same problem.
Package: simple-cdd Version: 0.6.9 Followup-For: Bug #1043571 Dear Maintainer, I get the same issue with simple-cdd. Once the ISO image is generated, it will fails at the beginning of the installation process. The log in the installer says : no packages matching running kernel 6.1.0-15-amd64 I tried to run simple-cdd on the same kernel version mentionned in the log but didn't change the outcome. This worked well in previous debian release. -- System Information: Debian Release: 12.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-15-amd64 (SMP w/1 CPU thread; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages simple-cdd depends on: ii dctrl-tools 2.24-3+b1 ii debian-cd 3.2.1 ii lsb-release 12.0-1 ii python3 3.11.2-1+b1 ii python3-simple-cdd 0.6.9 ii reprepro5.3.1-1+deb12u1 ii rsync 3.2.7-1 ii wget1.21.3-1+b2 Versions of packages simple-cdd recommends: ii dose-distcheck 7.0.0-1+b2 Versions of packages simple-cdd suggests: pn qemu-system | qemu-kvm -- no debconf information
Bug#1043549: Valid also for my bluetooth ID 05ac:821a on my 3 x MBP 9,1 mid 2012
Hello, I also have 3 Macbook Pro 9,1 mid 2012 but my bluetooth ID is 05ac:821a instead od 821d, can't explain why. I too felt that BT was working with kernels 5.10 and 6.1 but doesn't work with 6.4. So I replicated the proceeding reported here and it started working, just as in the report.
Bug#1036799: sylpheed: unable to send or read email after upgrading to Debian 12
control: severity -1 grave Hi Ricardo, > Right, but that doesn't deserve a 'grave' severity as only gsmtp users > are affected and no data is lost or security hole is introduced. I've > adjusted this accordingly. The definition of grave severity is: grave makes the package in question unusable or mostly so, or causes data loss, or introduces a security hole allowing access to the accounts of users who use the package. This bug renders sylpheed unusuable or mostly so for me, so it is indeed a grave bug. I am restoring severity accordingly. > That has been reported on the list that downgrading to 3.7.0 fixes the > problem: https://www.sraoss.jp/pipermail/sylpheed/2023-May/007129.html > Can you check if downgrading fixes it? I wish I could check it but so far the only way I have to do so is installing from source. What I can confirm is the bug appeared when upgrading from version 3.7.0 to version 3.8.0~beta1-1. I hope you understand this bug is preventing me from using sylpheed and so from reading and writing email, unless from gmail's web interface. I find of great concern that the bug is in Debian's new stable distribution: bookworm. If you know the bug is in version 3.8.0~beta1-1 I would suggest downgrading stable to 3.7.0 if you can manage to do so. Best regards, José Luis
Bug#1037437: From fresh bookworm install default sshd jail in fail2ban won’t work
Hi Jeremy, On 13/07/23 23:01, Jeremy Davis wrote: Can you confirm that the current default bookworm fail2ban config/regex works with sshd with just this change (to 'backend' in /etc/fail2ban/jail.conf)? Or are further adjustments required? Yes, I can confirm that fail2ban sshd jail works fine using the default config and just changing the 'backend' to 'systemd'. Best regards, José Gonçalves
Bug#1037437: From fresh bookworm install default sshd jail in fail2ban won’t work
Hi, As Debian opted by systemd journal as the default logging mechanism for bookworm, maybe a better option would be to change the default configuration in '/etc/fail2ban/jail.conf' to select journal as the logging source, i.e., instead of setting 'backend = auto', set 'backend = systemd'. Best regards, José Gonçalves
Bug#1037783:
Thanks, Matthias for reporting. The issue is now fixed upstream [1]. We'll make a new Debian release of the package soon to close this bug. Cheers, JL [1] Branch "develop" of http://github.com/MRPT/mrpt/ as of today's version, commit hash 3b01ad11af786acd129f05152fdbfb505086509c
Bug#1037220: localechooser: Support for No localization with UTF-8 charset
Package: debian-installer Severity: wishlist Tags: d-i X-Debbugs-Cc: japp.deb...@gmail.com Dear Debian-Installer Team, I am choosing "No localization" option in the localechooser menu because I am not interested in using any locale options. However, this option also implies the ASCII charset. Some applications print empty or incorrect characters due to the ASCII charset, such as when opening UTF-8 files with nano. Actually, to enable UTF-8 support system-wide, I am manually changing my locale settings to C.UTF-8 after the installation process. I would like to suggest adding an option called "No localization with UTF-8 charset" to localechooser, in addition to the existing "No localization" option [1]. Regards, José Ángel Pastrana [1] https://salsa.debian.org/installer- team/localechooser/-/blob/master/languagelist#L17 -- System Information: Debian Release: 12.0 APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing-proposed-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-9-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system)
Bug#1036810: default window size no longer correct when document contains a TOC
Package: xpdf Version: 3.04+git20220601-1+b2 Severity: important Before Debian 12, if the document contained a Table of contents, which is and should be quite often, the Table of contents was displayed since opening the document, xpdf's window sized accordingly to let show it. Not anymore after I upgraded. -- System Information: Debian Release: 12.0 APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-9-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages xpdf depends on: ii libc6 2.36-9 ii libgcc-s1 12.2.0-14 ii libpaper1 1.1.29 ii libpoppler126 22.12.0-2+b1 ii libstdc++6 12.2.0-14 ii libx11-6 2:1.8.4-2 ii libxm4 2.3.8-3 ii libxt6 1:1.2.1-1.1 Versions of packages xpdf recommends: ii cups-bsd2.4.2-3 ii gsfonts-x11 2:20200910-7 ii poppler-data0.4.12-1 ii poppler-utils 22.12.0-2+b1 ii sensible-utils 0.0.17+nmu1 xpdf suggests no packages. -- no debconf information
Bug#1036808: no longer remembers window size
Package: xpdf Version: 3.04+git20220601-1+b2 Severity: important Window size needs to get saved. Otherwise you have to resize it every time you open the program in case the default one doesn't suit your needs. This is happening to me now after upgrading to Debian 12. It's actually taller than my desktop's available vertical space. -- System Information: Debian Release: 12.0 APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-9-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages xpdf depends on: ii libc6 2.36-9 ii libgcc-s1 12.2.0-14 ii libpaper1 1.1.29 ii libpoppler126 22.12.0-2+b1 ii libstdc++6 12.2.0-14 ii libx11-6 2:1.8.4-2 ii libxm4 2.3.8-3 ii libxt6 1:1.2.1-1.1 Versions of packages xpdf recommends: ii cups-bsd2.4.2-3 ii gsfonts-x11 2:20200910-7 ii poppler-data0.4.12-1 ii poppler-utils 22.12.0-2+b1 ii sensible-utils 0.0.17+nmu1 xpdf suggests no packages. -- no debconf information
Bug#1036807: Update style to selection doesn't save the style's typefont
Package: libreoffice-writer Version: 4:7.4.5-2 Severity: important If I update say Title 2's style to selection the selection's typefont doesn't get saved, appearing as Liberation Sans instead when the style gets applied. -- Package-specific info: Configuration filePackage Exists Changed /etc/libreoffice/registry/writer.xcd libreoffice-writer Yes No All deployed bundled extensions: 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 +++----=== ii libreoffice-gtk3 4:7.4.5-2amd64office productivity suite -- GTK+ 3 integration un libreoffice-kf5(no description available) un libreoffice-qt5(no description available) Java (javaldx): /usr/lib/jvm/java-17-openjdk-amd64/lib/amd64/client:/usr/lib/jvm/java-17-openjdk-amd64/lib/amd64/server:/usr/lib/jvm/java-17-openjdk-amd64/lib/amd64/native_threads:/usr/lib/jvm/java-17-openjdk-amd64/lib/amd64 Java: http://openoffice.org/2004/java/framework/1.0; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;> file:///usr/lib/jvm/java-11-openjdk-amd64 -- System Information: Debian Release: 12.0 APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-9-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libreoffice-writer depends on: ii libabw-0.1-1 0.1.3-1 ii libc62.36-9 ii libe-book-0.1-1 0.1.3-2+b2 ii libepubgen-0.1-1 0.1.1-1 ii libetonyek-0.1-1 0.1.10-3+b1 ii libgcc-s112.2.0-14 ii libicu72 72.1-3 ii libmwaw-0.3-30.3.21-1 ii libodfgen-0.1-1 0.1.8-2 ii libreoffice-base-core4:7.4.5-2 ii libreoffice-common 4:7.4.5-2 ii libreoffice-core 4:7.4.5-2 ii librevenge-0.0-0 0.0.5-3 ii libstaroffice-0.0-0 0.0.7-1 ii libstdc++6 12.2.0-14 ii libuno-cppu3 4:7.4.5-2 ii libuno-cppuhelpergcc3-3 4:7.4.5-2 ii libuno-sal3 4:7.4.5-2 ii libuno-salhelpergcc3-3 4:7.4.5-2 ii libwpd-0.10-10 0.10.3-2+b1 ii libwpg-0.3-3 0.3.3-1 ii libwps-0.4-4 0.4.13-1 ii libxml2 2.9.14+dfsg-1.2 ii ucf 3.0043+nmu1 ii uno-libs-private 4:7.4.5-2 ii zlib1g 1:1.2.13.dfsg-1 Versions of packages libreoffice-writer recommends: ii libreoffice-math 4:7.4.5-2 Versions of packages libreoffice-writer suggests: ii default-jre [java8-runtime] 2:1.17-74 ii fonts-crosextra-caladea 20200211-1 ii fonts-crosextra-carlito 20220224-1 ii libreoffice-base4:7.4.5-2 ii libreoffice-java-common 4:7.4.5-2 ii openjdk-11-jre [java8-runtime] 11.0.18+10-1~deb11u1 ii openjdk-17-jre [java8-runtime] 17.0.6+10-1 Versions of packages libreoffice-core depends on: ii fontconfig 2.14.1-4 ii fonts-opensymbol4:102.12+LibO7.4.5-2 ii libabsl20220623 20220623.1-1 ii libboost-locale1.74.0 1.74.0+ds1-20 ii libc6 2.36-9 ii libcairo2 1.16.0-7 ii libclucene-contribs1v5 2.3.3.4+dfsg-1.1 ii libclucene-core1v5 2.3.3.4+dfsg-1.1 ii libcups22.4.2-3 ii libcurl3-gnutls 7.88.1-9 ii libdbus-1-3 1.14.6-1 ii libdconf1 0.40.0-4 ii libeot0 0.01-5+b1 ii libepoxy0 1.5.10-1 ii libexpat1 2.5.0-1 ii libexttextcat-2.0-0 3.4.5-1 ii libfontconfig1 2.14.1-4 ii libfreetype62.12.1+dfsg-5 ii libgcc-s1 12.2.0-14 ii libglib2.0-02.74.6-2 ii libgpgmepp6 1.18.0-3+b1 ii libgraphite2-3 1.3.14-1 ii libgstreamer-plugins-base1.0-0 1.22.0-3 ii libgstreamer1.0-0 1.22.0-2 ii libharfbuzz-icu06.0.0+dfsg-3 ii libharfbuzz0b 6.0.0+dfsg-3 ii libhunspell-1.7-0 1.7.1-1 ii libhyphen0 2.8.8-7 ii libice6 2:1.0.10-1 ii libicu7272.1-3 ii libjpeg62-turbo 1:2.1.5-2 ii liblcms2-2 2.14-2 ii libldap-2.5-0
Bug#1036805: libreoffice's toolbar buttons became hard to see after upgrading to Debian 12
Package: libreoffice-writer Version: 4:7.4.5-2 Severity: important After upgrading to Debian 12, writer's toolbar buttons became hard to see, looking liquid. I have checked with the other components and it's happening with all. Please, reassign if appropriate. -- Package-specific info: Configuration filePackage Exists Changed /etc/libreoffice/registry/writer.xcd libreoffice-writer Yes No All deployed bundled extensions: 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 +++----=== ii libreoffice-gtk3 4:7.4.5-2amd64office productivity suite -- GTK+ 3 integration un libreoffice-kf5(no description available) un libreoffice-qt5(no description available) Java (javaldx): /usr/lib/jvm/java-17-openjdk-amd64/lib/amd64/client:/usr/lib/jvm/java-17-openjdk-amd64/lib/amd64/server:/usr/lib/jvm/java-17-openjdk-amd64/lib/amd64/native_threads:/usr/lib/jvm/java-17-openjdk-amd64/lib/amd64 Java: http://openoffice.org/2004/java/framework/1.0; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;> file:///usr/lib/jvm/java-11-openjdk-amd64 -- System Information: Debian Release: 12.0 APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-9-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libreoffice-writer depends on: ii libabw-0.1-1 0.1.3-1 ii libc62.36-9 ii libe-book-0.1-1 0.1.3-2+b2 ii libepubgen-0.1-1 0.1.1-1 ii libetonyek-0.1-1 0.1.10-3+b1 ii libgcc-s112.2.0-14 ii libicu72 72.1-3 ii libmwaw-0.3-30.3.21-1 ii libodfgen-0.1-1 0.1.8-2 ii libreoffice-base-core4:7.4.5-2 ii libreoffice-common 4:7.4.5-2 ii libreoffice-core 4:7.4.5-2 ii librevenge-0.0-0 0.0.5-3 ii libstaroffice-0.0-0 0.0.7-1 ii libstdc++6 12.2.0-14 ii libuno-cppu3 4:7.4.5-2 ii libuno-cppuhelpergcc3-3 4:7.4.5-2 ii libuno-sal3 4:7.4.5-2 ii libuno-salhelpergcc3-3 4:7.4.5-2 ii libwpd-0.10-10 0.10.3-2+b1 ii libwpg-0.3-3 0.3.3-1 ii libwps-0.4-4 0.4.13-1 ii libxml2 2.9.14+dfsg-1.2 ii ucf 3.0043+nmu1 ii uno-libs-private 4:7.4.5-2 ii zlib1g 1:1.2.13.dfsg-1 Versions of packages libreoffice-writer recommends: ii libreoffice-math 4:7.4.5-2 Versions of packages libreoffice-writer suggests: ii default-jre [java8-runtime] 2:1.17-74 ii fonts-crosextra-caladea 20200211-1 ii fonts-crosextra-carlito 20220224-1 ii libreoffice-base4:7.4.5-2 ii libreoffice-java-common 4:7.4.5-2 ii openjdk-11-jre [java8-runtime] 11.0.18+10-1~deb11u1 ii openjdk-17-jre [java8-runtime] 17.0.6+10-1 Versions of packages libreoffice-core depends on: ii fontconfig 2.14.1-4 ii fonts-opensymbol4:102.12+LibO7.4.5-2 ii libabsl20220623 20220623.1-1 ii libboost-locale1.74.0 1.74.0+ds1-20 ii libc6 2.36-9 ii libcairo2 1.16.0-7 ii libclucene-contribs1v5 2.3.3.4+dfsg-1.1 ii libclucene-core1v5 2.3.3.4+dfsg-1.1 ii libcups22.4.2-3 ii libcurl3-gnutls 7.88.1-9 ii libdbus-1-3 1.14.6-1 ii libdconf1 0.40.0-4 ii libeot0 0.01-5+b1 ii libepoxy0 1.5.10-1 ii libexpat1 2.5.0-1 ii libexttextcat-2.0-0 3.4.5-1 ii libfontconfig1 2.14.1-4 ii libfreetype62.12.1+dfsg-5 ii libgcc-s1 12.2.0-14 ii libglib2.0-02.74.6-2 ii libgpgmepp6 1.18.0-3+b1 ii libgraphite2-3 1.3.14-1 ii libgstreamer-plugins-base1.0-0 1.22.0-3 ii libgstreamer1.0-0 1.22.0-2 ii libharfbuzz-icu06.0.0+dfsg-3 ii libharfbuzz0b 6.0.0+dfsg-3 ii libhunspell-1.7-0 1.7.1-1 ii libhyphen0 2.8.8-7 ii libice6 2:1.0.10-1 ii libicu7272.1-3 ii libjpeg62-turbo 1:2.1.5-2 ii liblcms2-2
Bug#1036800: sylpheed: unable to send or read email after upgrading to Debian 12
Package: sylpheed Version: 3.8.0~beta1-1 Severity: grave After upgrading to Debian 12 and booting again the computer I am unable to use sylpheed to neither send email with both accounts I have set up, nor read new messages, just with the IMAP one in this case. Both accounts are from Gmail. The error message I get trying to send with the POP3 is Error Hubo un error enviando el mensaje: 501 5.5.2 Cannot Decode response r11-20020a5d494b00b00300aee6c9cesm5425569wrs.20 - gsmtp while with the IMAP one is Hubo un error enviando el mensaje: 501 5.5.2 Cannot Decode response j13-20020a5d604d00b00306344eaebfsm5456150wrt.28 - gsmtp Whereas, trying to open the inbox of the IMAP one, or any other folder, gets this: Error No se pudo establecer una conexión con el servidor. making it impossible to read or query new mail.
Bug#1036799: sylpheed: unable to send or read email after upgrading to Debian 12
Package: sylpheed Version: 3.8.0~beta1-1 Severity: grave After upgrading to Debian 12 and booting again the computer I am unable to use sylpheed to neither send email with both accounts I have set up, nor read new messages, just with the IMAP one in this case. Both accounts are from Gmail. The error message I get trying to send with the POP3 is Error Hubo un error enviando el mensaje: 501 5.5.2 Cannot Decode response r11-20020a5d494b00b00300aee6c9cesm5425569wrs.20 - gsmtp while with the IMAP one is Hubo un error enviando el mensaje: 501 5.5.2 Cannot Decode response j13-20020a5d604d00b00306344eaebfsm5456150wrt.28 - gsmtp Whereas, trying to open the inbox of the IMAP one, or any other folder, gets this: Error No se pudo establecer una conexión con el servidor. making it impossible to read or query new mail.
Bug#1021962: xfce4-notes-plugin not in sid nor testing since before April 2021
severity 1021962 grave retitle 1021962 xfce4-notes-plugin: Missing from sid, testing and stable since before bullseye was even released thanks > Control: severity -1 wishlist This is preventing the use of the package to all except those using /experimental/, making it therefore unusable to most. Right severity is therefore grave. Setting it accordingly. I remind that the right version for regular users is stable, and unstable for developers. The package is missing from both and from testing, and has been since before version 11.0 was released, which was already released in August 2021, a really long time ago. Next stable release (bookworm) is planned for 10th of June this year, and we are, as of today, in Full freeze already, so this package won't even get into it. It has not received enough care nor attention because of the severity. This is serious. > The reason it's not available is that it was not uploaded to bullseye, > though it's there in experimental. You can find it in other suites > here: https://packages.debian.org/search?keywords=xfce4-notes-plugin May I know the reason it's only in experimental, and has been for so long? As far as I remember it was dropped from bullseye before it was released because of RC bugs, but there is not a single archived or unarchived bug about this.
Bug#1036544: thunar: sftp doesn't work even with required gvfs packages installed
Package: thunar Version: 4.16.8-1 Severity: important Hi, Connecting through SFTP doesn't work for me in Thunar despite I have the gvfs-fuse and gvfs-backends packages installed, which are the only requirements according to https://wiki.debian.org/Thunar#FTP_.2F_SFTP_etc.
Bug#1036444: Fixing last control mail mixing mistakenly #1036445 issues with #1036444
On Sun, 21 May 2023 11:06:26 +0200 José Luis González wrote: > > forwarded 1036444 https://github.com/rkd77/elinks/issues/233 > > Thanks a lot for this, and sorry for the last control message mess. It would have been more useful if you pointed to the bug report, as well as making a brief summary as you did. Just the URL would have been enough. Regards, JL
Bug#1036445: Clearing up mistaking you for #1036382 maintainer
Hi again أحمد المحمودي, It seems this night with sleep deprivation I became sloppy. This went to #1036444: > As I explained you in #1036382, Sorry that I mistook you for the maintainer of that bug. Conversely this went to #1036445: > As in #1036382, all you have to do is confirm you can reproduce it with > the same package version, confirm the bug is not caused by a Debian > patch, and forward the report to upstream. Also try to reproduce > through network, if you can. > I provided one also to you in #1036382, named hello-world.xhtml. Ditto. My most sincere apologies for the confusion.
Bug#1036382: dillo: doesn't recognize XHTML 1.1 as HTML
On Sun, 21 May 2023 05:34:16 +0200 José Luis González wrote: > All I ask you is to confirm the bug was not coming from a > Debian patch and forward the full report to upstream. That's all. Sorry Andrey, I mistook you for the maintainer. You can overlook this, obviously :)
Bug#1036445: Fixing last control mail not reaching #1036445 report and setting grave severity mistakenly going to #1036444 instead
severity 1036444 important severity 1036445 grave thanks > > Version: 0.13.2-1+b1 > > Could you test the version in experimental (0.16.1.1) /? No, I have no box available with experimental at this time, sorry. But it makes little difference. The bug was filed for version 0.13.2-1+b1 so it's in all supported releases this version exists where you have to test it, besides sid. Please, also note experimental is not the right release for development usually, that would be sid (unstable). > > Tags: upstream, patch > > No patch attaxhed, removing patch tag. Patch tag does not mean necessarily that a patch is attached. A simple description for fixing it is enough: patch A patch or some other easy procedure for fixing the bug is included in the bug logs. [...] In this case my procedure was at the bottom of my report. It should be easy enough for the developers. As in #1036382, all you have to do is confirm you can reproduce it with the same package version, confirm the bug is not caused by a Debian patch, and forward the report to upstream. Also try to reproduce through network, if you can. > > Severity: grave > Quoting https://www.debian.org/Bugs/Developer : > " > grave > makes the package in question unusable or mostly so, or causes data > loss, or introduces a security hole allowing access to the accounts of > users who use the package. > " > > hence severity is either normal or important. I wonder why you think severity is normal or important, and more so why you don't even seem to know which of these is supposedly. Quoting the severity's description doesn't provide your reason :) My reasoning is analogue to the one I had for #1036382 initially, which is provided there and in this report. > > ELinks is not recognizing MIME type text/xml+xhtml nor text/xml, which > > are the recommended types for XHTML, on added file extensions. This > > means that, despite XHTML 1.0 and XHTML 1.1 documents are valid HTML 4 > > they are not recognized unless you use text/html type. > > Please attach a file that I can use to test the issue. Considering you are maintaining a web browser you should be able to make up an elementary XHTML 1.1 test file yourself. Anyway, as I said, I provided one also to you in #1036382, named hello-world.xhtml. Just rename to hello-world.xhtml.en
Bug#1036384: dillo: Open file dialog pops up in /tmp
severity 1036384 important retitle 1036384 dillo: Open file dialog pops up in /tmp and forgets opened file's dir when changing page thanks On Sun, 21 May 2023 06:22:17 +0200 Axel Beckert wrote: > Control: severity -1 minor > Control: tag -1 upstream Please, when you modify a submitter's settings make sure beforehand you have supported your decision with objective reasons, you are right, and the submitter agrees. In this case you say nothing about why you consider this is not an upstream bug, and you didn't support your claim that the severity is minor on anything besides asserting it, which obviously is no reasoning. > José Luis González wrote: > > When I pop up the Open file dialog it always opens in /tmp, forcing you > > to change to home, which is where it should open. > > Where it should open is actually very subjective. I hope you are not serious. > And most open > dialogs don't open in $HOME either but usually where you opened a file > the last time. Absolutely agreed. But that can only happen when you have already opened a file. Otherwise it's impossible, since you wouldn't known where to chdir() to. I'm puzzled though, since 1. This is also what I was arguing for. You seemed to understand something else and argue here that I was wrong and right behaviour is precisely what I reported as desired right behaviour: [...] The only exception is when you have already opened a file and are still displaying it, then it rightly opens in the same dir, but if you go back to another page and return it forgets. [...] This was part of the description of Dillo's current behaviour. Since the report communicated two related issues and it seems this one wasn't correctly understood nor it was featured on the subject, I have updated its title to reflect it. 2. You seem to imply the Open file dialog should open most of the time where you opened a file last time, which is only right when you are in a context where that directory still applies, which obviously requires that the program's current state hasn't moved to something else. 3. You don't acknowledge that I was reporting that when you return to the page where you had opened from a file, Dillo shall remember that file's directory and start the Open File dialog on it, which is not what it currently does, and which further aligns with what you are trying to defend. 4. You are supporting your claims on supposed common behaviour, and not solid reasons. > Which dillo does btw. to. (Ok, maybe not after it has > been closed and started again.) Well, it actually doesn't sometimes when it should, and this was precisely on my report. See the quote above and the new title. Furthermore, it makes no sense to start the Open file dialog where you opened a page that are no longer displaying, as I already explained in this email. In this case, if the current page doesn't come from a file, common sense dictates not to start the dialog on a directory that is not relevant anymore but on the default directory, which in Dillo's case should be HOME (the other option would have been Desktop, but it's a plain FLTK program, and knows nothing so far about the desktop). > /tmp/ is not the best choice but IMHO a valid one. If, by your own admission, it's not the best choice, why do you argue for that on a report that is precisely about the open file dialog incorrectly popping up by default there? > At least I manually > open HTML files in a browser most times in /tmp/ and not in $HOME. Well, all the better for you, but this is not the usual case, as I think you admit. :) $HOME was created for something. This is where user's life usually begins. Negating this is ignoring how Unix works. > (And not, the fact that dillo does that is not a patch of mine, just > coincidence. And probably the reason why I never noticed it.) 1. May we know when I claimed this behaviour came from a patch of yours? 2. You seem to be trying to argue for this being an upstream bug, but you precisely removed the upstream tag that I had added, which means exactly the opposite, so I'm mystified. > Additionally there is the short cut Alt-H to directly jump to your > home directory. Moot point as well. The fact that the shortcut exists doesn't mean it's the right place to begin at. If anything just the opposite: (1) it's accessing precisely ome, with what this means on English, and (2) if it exists it's obvious it's a frequent point the user may need to go to, which further supports my point. > > Besides, if I click on FLTK's shortcut for /, right up the Filename > > text entry, it only displays kernel fs dirs: sys, proc, dev, run, and > > subdirs of these. > > Indeed. But it actually shows all mount points (including /home/ for > me). I'm frankly having a hard time understanding why 1. dillo's open file dialog should pop
Bug#1036451: sylpheed: search and replace missing from Edit menu in compose window
Package: sylpheed Version: 3.7.0-8 Tags: upstream Search and replace operations are very basic, but they are missing from Edit menu in compose window, which makes no sense in a featureful email client at version 3.7.
Bug#1036444: closed by أحمد المحمودي (Re: Bug#1036444: elinks: relies on file extension for files instead of content)
reopen 1036444 severity 1036444 grave tags 1036445 patch thanks > #1036444: elinks: relies on file extension for files instead of content > > It has been closed by أحمد المحمودي . Please, don't close bug reports until you are sure the bug is fixed. > > > para1 > para2 > > This file is not conforming XHTML 1. It's just HTML. As I explained you in #1036382, XHTML 1 is a subset of HTML 4 that is also XML conformant. So there are additional elements to add in this file, namely the opening XML version line, the XHTML 1 DOCTYPE, the xmlns and xml:lang attributes to the html tag, and closing tags for the paragraphs, since it's mandatory to close all tags. You have the simplest you example of a valid XHTML 1.1 document you can find on the hello-world.xhtml file I attached you on #1036382, in case you want to see a whole and save it for testing. > I tested the version in experimental using the attached file, and it > worked correctly. Please, don't close bugs that you think are fixed on experimental until the fix is already on all supported releases containing the bug and you are sure the bug is fixed. In this case your test file wasn't conforming XHTML 1.1, as I explained, so it's not good to reproduce it. > > Version: 0.13.2-1+b1 > > Could you test the version in experimental (0.16.1.1) /? No, I have no box available with experimental at this time, sorry. But it makes little difference. The bug was filed for version 0.13.2-1+b1 so it's in all supported releases this version exists where you have to test it, besides sid. Please, also note experimental is not the right release for development usually, that would be sid (unstable). > > Tags: upstream, patch > > No patch attaxhed, removing patch tag. Patch tag does not mean necessarily that a patch is attached. A simple description for fixing it is enough: patch A patch or some other easy procedure for fixing the bug is included in the bug logs. [...] In this case my procedure was at the bottom of my report. It should be easy enough for the developers. As in #1036382, all you have to do is confirm you can reproduce it with the same package version, confirm the bug is not caused by a Debian patch, and forward the report to upstream. Also try to reproduce through network, if you can. > > Severity: grave > Quoting https://www.debian.org/Bugs/Developer : > " > grave > makes the package in question unusable or mostly so, or causes data > loss, or introduces a security hole allowing access to the accounts of > users who use the package. > " > > hence severity is either normal or important. I wonder why you think severity is normal or important, and more so why you don't even seem to know which of these is supposedly. Quoting the severity's description doesn't provide your reason :) My reasoning is analogue to the one I had for #1036382 initially, which is provided there and in this report. > > ELinks is not recognizing MIME type text/xml+xhtml nor text/xml, which > > are the recommended types for XHTML, on added file extensions. This > > means that, despite XHTML 1.0 and XHTML 1.1 documents are valid HTML 4 > > they are not recognized unless you use text/html type. > > Please attach a file that I can use to test the issue. Considering you are maintaining a web browser you should be able to make up an elementary XHTML 1.1 test file yourself. Anyway, as I said, I provided one also to you in #1036382, named hello-world.xhtml. Just rename to hello-world.xhtml.en
Bug#1036382: dillo: doesn't recognize XHTML 1.1 as HTML
retitle 1036382 dillo: meta http-equiv makes .xhtml files not be recognized severity 1036382 important thanks On Sat, 20 May 2023 21:39:29 +0400 Andrey Rakhmatullin wrote: > Control: tags -1 + unreproducible > > On Sat, May 20, 2023 at 11:23:19AM +0200, José Luis González wrote: > > When I open an XHTML 1.1 file dillo doesn't recognize it as HTML, > > displaying it as plain text, despite the file being correct XHTML. It > > happens with any extension, including .html and .xhtml. > I can't reproduce this. I took the time to nail it down: - hello-world.html works, but hello-world.xhtml doesn't, for the same content. .xhtml extension just makes dillo not recognize the file as HTML, for any content. This is not the bug I had reported, though but a new one. I will let you file it. - The offending line that made my two .xhtml files not be recognized was which is perfectly valid XHTML 1 as well as HTML, and works in all .html files I have tried, including "hello-world plus http-equiv.html. I attach these new, simplified, test files. You should be able to reproduce it with them. They are as simple as a conforming XHTML 1 document can get, except the one with the added http-equiv, obviously. Please, unmark the report as unreproduceable then. On a personal side, I would have appreciated if you had told me you hadn't tried .xhtml extension. You would have saved me test time. > > Considering XHTML 1.1 is valid HTML 4, which dillo supports, and XHTML > > is nowadays and shall be widely supported, this makes the package > > mostly unusable. > I don't think not supporting XHTML would make it "mostly unusable" but > *shrug*. XHTML 1 is just a subset of HTML 4 that is XML conformant, so it has been basically supported by dillo since its very first release, back in 1999. XHTML 1.0 became a W3C recommendation on 26 January 2000, when dillo was just at version 0.0.4, and a lot of things have happened ever since. XHTML is mentioned in the ChangeLog for version 0.8.4, which was released on the 11 of January 2005, but that was so far as to the validation feature, so it doesn't mean it wasn't supported beforehand. application/xhtml+xml was finally accepted in version 2.2.1 (July 2011), so since then XHTML 1 should have worked flawlessly. My reasoning for the severity is XHTML 1 has been there for ages and is trivial to implement. There are tons of documents tagged as such around on the web, so not supporting it makes it impossible to use dillo nowadays as a general browser, which renders the package unusable except for particular cases, hence mostly unusable. Having found out the bug was just in accepting the http-equiv, and not in any XHTML I document I am lowering severity to important. If I had the time I would volunteer to provide a proper patch, but I don't know this browser's code as well as ELinks', so can't promise anything at this time. It should be trivial for the developers, though. All I ask you is to confirm the bug was not coming from a Debian patch and forward the full report to upstream. That's all. Title: Hello, world! foo hello-world.xhtml Description: application/xhtml Title: Hello, world! foo
Bug#1036445: elinks: doesn't recognize recommended XHTML 1.0/1.1 MIME type on files
Package: elinks Version: 0.13.2-1+b1 Tags: upstream, patch Severity: grave ELinks is not recognizing MIME type text/xml+xhtml nor text/xml, which are the recommended types for XHTML, on added file extensions. This means that, despite XHTML 1.0 and XHTML 1.1 documents are valid HTML 4 they are not recognized unless you use text/html type. I haven't been able to test through HTTP yet, though. Severity is assuming the bug happens also on network, so lower to important if it isn't the case. The solution depends on whether the problem is just a file handling issue or general, but it's trivial in both cases: - If it's a file handling issue (it works on HTTP) it's just a matter of finding out why only text/html is accepted in the case of files. I'm sure it is straightforward, and can volunteer for a patch in this case. - If it's general all necessary is accepting both types and assuming they are valid HTML. Parts of XHTML 2 might not display correctly yet, but this has ever happened with all newer versions of HTML on legacy browsers, and is not a problem until it gets supported. I have no doubt XHTML 1 is fully supported, though, and has ever been, except for this MIME type issue.
Bug#1036444: elinks: relies on file extension for files instead of content
Package: elinks Version: 0.13.2-1+b1 Severity: important I have all my personal web pages ending in the their ISO language code as extension, so the Apache server chooses the appropriate one according to the Accepted-Language HTTP header from the browser. This means all my files are named like foo.xhtml.en foo.xhtml.es This is necessary in my case, and common practice. ELinks chokes at this, though, because it relies on extension rather than content for identifying HTML and the extension isn't .xhtml nor .html. The consequence is they aren't recognized as HTML, but as application/something, forcing you to open the file as binary and parse it afterwards as HTML with ^\. As soon as I link any of these files to .xhtml extension and open them from that name they are recognized immediately. It's the same with .html. I think there are two possible solutions to this: 1. Adapting to Apache's naming convention and so recognizing all ISO language codes as extension. 2. Relying on content instead of extension, which means just making Elusive try to parse the file, and is, IMHO, the correct solution.
Bug#1036436: sylpheed: Select all and Select thread belong to Message menu, not Edit
Package: sylpheed Version: 3.7.0-8 Tags: upstream Severity: normal Select all and Select thread are message operations, not edition operations. Therefore they belong to Message menu, not Edit.
Bug#1036435: xpdf: belongs to Office menu category, not Graphics
Package: xpdf Version: 3.04+git20210103-3 Severity: important PDF is a document format. As such, xpdf is a document viewer, so it belongs to the Office menu, not Graphics, as it currently is in.
Bug#1036434: sylpheed: main window isn't sized adapting to messages container
Package: sylpheed Version: 3.7.0-8 Severity: important Tags: upstream Sylpheed's main window isn't automatically sized to adapt to the messages container width. A horizontal scrollbar is used instead, which is not the right solution, since in this case you need to see all the columns almost all the time, so scrolling makes no sense.
Bug#1036433: sylpheed: main window size not remembered when disabling separating folders tree
Package: sylpheed Version: 3.7.0-8 Tags: upstream If you separate the folders tree, resize Sylpheed's window, and disable separate folders tree back, the size of Sylpheed's window is not remembered.
Bug#1036431: sylpheed: + button in search messages dialog misplaced
Package: sylpheed Version: 3.7.0-8 Tags: upstream Severity: normal The button to add additional conditions to the search messages dialog is wrongly placed at right of each condition. This is complete nonsense, since it's something that belongs logically to the conditions, not to each condition, so it shall be before all the conditions, and there shall be only one. Remaining consistent with the interface this should also be a text button with an icon, not just an icon. This important for two reasons. First and foremost because otherwise the interface wouldn't be intuitive. You wonder where to add more conditions until you figure out, and when you do it doesn't stay in memory for long. Secondly, because it wastes space horizontally on this place.
Bug#1036429: sylpheed: messages search dialog and other of its elements not sized correctly
Package: sylpheed Version: 3.7.0-8 Tags: upstream Several things in the search message dialog are not sized correctly. Firstly, the search messages dialog window is too small. A container would be mandatory here. Its width shall be at least that of the conditions container, otherwise they don't fit. Additionally, height is not enough to show more than three conditions, and considering fast search is available, I would expect four, so bigger sizing is required in this case. Also, it is not enough as well to show more than five messages, as it's fairly common to look for more, so it becomes uncomfortable to scroll; another place which requires bigger sizing. Finally, the width of the message columns is too small for all but date to fit what usually is there.
Bug#1036425: sylpheed: to not set automatically for sent messages
Package: sylpheed Version: 3.7.0-8 Tags: upstream Severity: important If I reply to a message I sent, the To is not set to the addressee, which is what would be expected, but to yourself. The only reason I can think of replying a message you sent to yourself would be a test or a note, which is way by far not the usual thing. On such a case a follow-up to the addressee is usually what is intended, and the common practice by MUAs. Best, JL
Bug#1036424: sylpheed: replying to an email you sent doesn't set account accordingly
Package: sylpheed Version: 3.7.0-8 Severity: grave Tags: upstream If I reply to an email I sent the From account is not set to the account I used to send it but to my default account. See #1036388 for an explanation for severity. Regards, JL
Bug#563096: sylpheed: Hide update menu item
Hi Ricardo, > You can disable checking in configuration, no more spamming. > To me removing the option for checking is like self-cheating and > trusting the Debian version is always the latest. > As a user why should I trust the debian maintainer about that? :) > And as the debian maintainer I'd like to be notified by the users if > I miss some release [0], so really don't see the point of removing > the option. There's a mailing list of release announcements: There is also the sylpheed-announce ML (sylpheed-annou...@sraoss.jp) which deals only with release announcements. I suppose this has been added after the bug got reported. In any case now you can disable it in configure, since I think makes little sense in Debian, and close the bug. Best regards, José Luis
Bug#1036415: sylpheed: all keymappings missing except Select all in searched messages list
retitle 1036415 sylpheed: all keymappings missing except Select all in search messages list thanks Hi again, It seems all keyboard mappings are missing in this list except Select all. Retitling accordingly.
Bug#1036415: sylpheed: delete key doesn't work on esarch messages dialog
Package: sylpheed Version: 3.7.0-8 Tags: upstream Severity: important Hi, Delete key isn't mapped in the list of searched messages, so it just doesn't work. This is most important in Thrash messages since you can't use the workaround of moving them to the Thrash folder, and the context menu entry is missing (recently reported), which makes them impossible to delete. Regards, JL
Bug#1036414: sylpheed: Select all and Delete missing from Searched messages context menu
Package: sylpheed Version: 3.7.0-8 Tags: upstream The follwing entries are missing from search messages dialog on the results context menu: - Select all - Delete Delete is most important, since in this case the keyboard shorcut is also missing (I'm reporting this as well), and you can't just move out searched messages in Thrash to nowhere, which makes them impossible to delete.
Bug#1036411: sylpheed: no option for getting thrash emptied on messages older than X days
retitle 1036411 sylpheed: no option for getting messages deleted from thrash after X days of being deleted thanks On Sat, 20 May 2023 17:17:57 +0200 José Luis González wrote: > I find no option for getting messages older than X days deleted from > Thrash, only on Sypheed's exit. Sorry, I meant the messages from Thrash that had been deleted X days ago or more, not the messages that were sent that days ago, obviously :) Retitling consequently.
Bug#1036411: sylpheed: no option for getting thrash emptied on messages older than X days
Package: sylpheed Version: 3.7.0-8 Severity: important Tags: upstream I find no option for getting messages older than X days deleted from Thrash, only on Sypheed's exit. Like my recent save message report, this is something elementary that should have been there since about version 1, and has a major effect on the usability of the program, so marking as important. Sorry Ricardo that I'm filing all these upstream bugs on Debian, but as far as I know Sylpheed doesn't have a BTS.
Bug#1036398: sylpheed: Messages menu entries don't belong logically to Tools
Hi again, I mistakenly asked for a Messages menu to be added for this. Upon review, I think it makes sense on the existing Message menu. Sorry for the confusion.
Bug#1036410: sylpheed: save message missing from the interface
Package: sylpheed Version: 3.7.0-8 Severity: important Tags: upstream Hi, Save message is missing from the interface. It's only possible to do this with "File" -> "Export mail", and you would have to mark "Export only selected messages". This is something quite usual, and it's not that intuitive to do it in the existing way, so it makes a lot of sense that it exists both in the Message menu and messages context menu. With the number of features of Sylpheed, and at version 3.7, this is something that shall have been there a long time ago, before version 1 IMHO. Marking it as an important bug for that reason.
Bug#1036409: sylpheed: spell check language detection badly missing
Package: sylpheed Version: 3.7.0-8 Severity: wishlist Tags: upstream Hi, I find it terribly cumbersome to have to choose the spelling language of each email message I compose. Auto detection would be trivial to implement. All is needed is to measure the number of spelling "errors" in each language, choosing the one with least "mistakes". I would appreciate if this is implemented. Thank you so much in advance.
Bug#1036408: sylpheed: wrap paragraph doesn't format the paragraph on compose
Package: sylpheed Version: 3.7.0-8 Severity: important Tags: upstream Format paragraph (Control + L & Control + Alt + L) on compose window doesn't actually format paragraphs, which is what is needed most often, and rather trivial to implement. The need for formatting is, actually, rather common. I will elaborate. I think this "feature", as it stands, is badly posed. It makes no sense in a program to force the user to format manually with a ruler, which by the way, doesn't extend for the whole editing window, and expecting mails to be sent with no formatting would be a complete no sense as well since line length is limited in the standard to 1023 characters, and auto-formatting them on display is actually made with MIME-HTML, which Sylpheed doesn't support. Besides, a paragraph isn't usually "wrapped", but formatted. Wrapping the last line is, basically, the unusual case. When you edit you basically need to reformat the whole thing. And turning on auto-wrap isn't the solution either, as it breaks lines that need to be left longer, which happens often in the internet (a URL, for instance). Turning it on by default is usually not an option.
Bug#1036407: sylpheed: compose mail shortcut doesn't work in compose window
Package: sylpheed Version: 3.7.0-8 Severity: important Tags: upstream Control + M shortcut doesn't work in compose windows, effectively preventing from opening a new compose message window while composing a current one. This is something that happens often so such a restriction only makes it difficult and tiresome to use Sylpheed, as it forces you to open Sylpheed's window to be able to create it, and locate the existing compose window afterwards, as Sylpheed window is likely to have concealed the already existing compose window.
Bug#1036406: xfwm4: Working area list width artificially limited
Package: xfwm4 Version: 4.16.1-1 Severity: important Tags: upstream The width of the Working Area list displayed middle-clicking on desktop is severely limited for no reason, preventing enough of the window titles to be seen when they are long enough, which has a very major effect on the usability of the feature. This is a bit variable, since this list is displayed with a variable width font, but it more or less displays only 22 characters from the title. This is clipping 5 out of 10 windows on my desktop at this time. It makes no sense to place a width limit on this list, since the space needed is variable, can be actually a lot, and it's not known in advance how much is needed. If anything only preventing the window from being larger than the screen is necessary.
Bug#1036405: sylpheed: message subject in compose windows get clipped in some window managers' list
Package: sylpheed Version: 3.7.0-8 Tags: upstream Compose windows feature the string "Compose *" after the subject in the window's title. This string effectively clips the message's subject, which is more important, in my Window's manager (xfwm4) working areas list, which includes windows, because the width of the window list is limited. I'm going to file another bug to xfwm because of the artificial width limit, but I suspect the clipping is a Sylpheed bug.
Bug#1036402: doc-debian: forwarded missing from tags lists
Package: doc-debian Version: 6.5 Severity: important Hi, forwarded tag is missing from - tags list on tags command on bug-maint-mailcontrol.txt.gz - the tags definition list from bug-maint-info.txt.gz Regards, JL
Bug#1036388: sylpheed: account is reset when mail is checked
retitle 1036388 account reset when mail is checked tags 1036388 upstream thanks Hi again, It turns out the bug doesn't happen when email is received, but rather when it was checked by sylpheed, which makes it even more grave, since it's resetting it every X minutes, 10 in my case.
Bug#1036398: sylpheed: Messages menu entries don't belong logically to Tools
Package: sylpheed Version: 3.7.0-8 Severity: important Tags: upstream There are six Tools menu entries that are not intrinsically tools actions but Messages', and most are verbosely tagged as such in their names instead of moving them their own menu, making Sylpheed hard to use and inconvenient. A Messages menu would be necessary and expected. This seriously affects usability, so marking it as important.
Bug#1036389: sylpheed: notification window displayed as system dialog, not actually not displayed
Hi again, The problem seems to be that it's not displayed as a window, as the setting claims, but as a system dialog. Either an additional setting is added to choose a system dialog/notification or the behaviour is changed to a window, as the name implies. I would suggest a separate tickbox for both if retaining the sytem dialog is wanted. Best regards, JL
Bug#63995: bugs.debian.org reveals e-mail addresses to spammers
severity 63995 grave thanks A solution is available and it's trivial. Just conceal the addresses from the public web interface and mailing list archives, requiring authentication to access the full report. This is what's done in Ubuntu, Red Hat, XFCE, and about just any sensible project I know of. And requiring another account or manually reporting each spam is not a solution. Firstly, another account is unnecessary and cumbersome, and secondly, reporting spam is not always possible nor effective to a regular user, and in some cases this "solution" takes just too much time and effort to be feasible. It's just common sense that you don't reveal email addresses publicly nor to spammers. This makes the BTS unusable to anyone who doesn't set up and use an email account separately and purposefully for that, and which handles spam effectively. Additionally, this goes against point 4. of the Debian Social Contract. Raising severity to grave accordingly.
Bug#1016823: Thunar: add Lens Model to Image tab [patch attached]
> Control: forwarded -1 https://gitlab.xfce.org/xfce/thunar/-/issues/829 > Control: tags -1 upstream > > It looks like you already created an issue upstream. You can ask for > fork and MR permissions by contacting the mailing list. See the > instructions here: > https://docs.xfce.org/contribute/dev/git/start#gitlab_forks_and_merge_requests Thanks for the pointer, but the problem is I couldn't send the patch to the person who assisted me because the sender he used accepted no messages. Did you forward the patch, or made it explicity at least that a patch was available? The person who attended me was Alexander Schwinn. Thanks a lot in advance.
Bug#1036388: sylpheed: account unadvertingly and unwantingly changed when email is received
Hi again, I have observed this happens with new coming from any account, including the current one. So if I have an email account that is private@gmail and I get new mail on my current one, it also switches unwantingly and unadvertedly to private@gmail. The problem is really serious and obnoxious.
Bug#1036392: sylpheed: check new mail features should be an account preference, not a general
Package: sylpheed Version: 3.7.0-8 Severity: normal "Check new mail every X minutes" and "Check new mail on start" are preferences that make sense and may be necessary to be account options, not just common to all accounts, as it currently stands.
Bug#1036391: sylpheed: Toggling edit search bar doesn't hide it
Package: sylpheed Version: 3.7.0-8 Severity: important "Edit -> Fast search" and "Ctrl + Shift + S" don't toggle the search bar off when it is already displayed. This, together with #1036390, is a major usability issue, since it is inconvenient to turn it off and the feature can be needed very often.
Bug#1036390: sylpheed: search bar has no close button
Package: sylpheed Version: 3.7.0-8 Severity: important Sylpheed's fast search bar has no close button, making it inconvenient to close it, since the only way is through the View -> Show and hide submenu, especially considering it is not meant to be open all the time and consumes screen space.
Bug#1036389: sylpheed: new mail notification not working
Package: sylpheed Version: 3.7.0-8 Severity: important The new mail notification feature doesn't work for me at all. I have set it to display a window for 10 seconds on new mail received and the window does not pop up at all.
Bug#1036388: sylpheed: account unadvertingly and unwantingly changed when email is received
Package: sylpheed Version: 3.7.0-8 Severity: grave If a new mail arrives to an account other than the current one it is changed without permission nor warning to the one receiving the email, which means all activity from then on is done unadvertingly on the switched-to account. Considering the consequences of sending email from an account different from the one intended, like sending from a private one to a public forum (like a mailing list available on the web, or the DBTS), or using an account that is not permitted for what was unwantedly done, this makes the package mostly unusable since the consequences of can't be usually undone and can be very grave, which renders the program unusable for any serious user.
Bug#1036384: dillo: Open file dialog pops up in /tmp
Package: dillo Version: 3.0.5-7 Severity: important When I pop up the Open file dialog it always opens in /tmp, forcing you to change to home, which is where it should open. The only exception is when you have already opened a file and are still displaying it, then it rightly opens in the same dir, but if you go back to another page and return it forgets. Besides, if I click on FLTK's shortcut for /, right up the Filename text entry, it only displays kernel fs dirs: sys, proc, dev, run, and subdirs of these. The whole issue is a very serious usability issue.
Bug#1036382: dillo: doesn't recognize XHTML 1.1 as HTML
Package: dillo Version: 3.0.5-7 Severity: grave When I open an XHTML 1.1 file dillo doesn't recognize it as HTML, displaying it as plain text, despite the file being correct XHTML. It happens with any extension, including .html and .xhtml. Considering XHTML 1.1 is valid HTML 4, which dillo supports, and XHTML is nowadays and shall be widely supported, this makes the package mostly unusable. Best regards, José Luis
Bug#1035446: libmrpt-vision-lgpl-dev: missing Depends: libmrpt-vision-lgpl2.5 (= ${binary:Version})
Thanks, Andreas! Fixed on salsa: https://salsa.debian.org/robotics-team/mrpt/-/commit/37b6bbda747e7dc540cb61a001ed0026cd5be7f9 However, I think we can't make any release to Debian/sid at the moment due to the freeze, right? Cheers, JL On Wed, May 3, 2023 at 3:51 PM Andreas Beckmann wrote: > > Package: libmrpt-vision-lgpl-dev > Version: 1:2.5.8+ds-1 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > > Hi, > > during a test with piuparts I noticed your package ships (or creates) > a broken symlink. > > 0m49.8s ERROR: FAIL: Broken symlinks: > /usr/lib/x86_64-linux-gnu/libmrpt-vision-lgpl.so -> > libmrpt-vision-lgpl.so.2.5 (libmrpt-vision-lgpl-dev:amd64) > > There is a > Depends: libmrpt-vision2.5 (= 1:2.5.8+ds-1+b1) > which probably only mentions the wrong package name. > > > cheers, > > Andreas -- /** * Jose Luis Blanco-Claraco * Universidad de Almería - Departamento de Ingeniería * [Homepage]( https://w3.ual.es/~jlblanco/ ) * [GH profile]( https://github.com/jlblancoc ) */
Bug#1025324: libc6: Xserver with nouveau not workiing.
El 3/12/22 a las 12:07, Aurelien Jarno escribió: control: reassign -1 libgl1-mesa-dri control: forcemerge 1025312 -1 control: affects 1025312 src:glibc Hi, On 2022-12-03 07:25, Agustin Martin wrote: Hi all, Also hit by this problem (intel i5 box). Noticed that Xorg log showing the error is very similar to what is seen in #1025312 [libgl1-mesa-dri: multiple packages FTBFS and have autopkgtest regressions running test programs under Xvfb] Thanks for the pointer, it indeed looks the real issue. Basically mesa calls dlclose(NULL), that's why libc6 appears in the backtrace. I am therefore reassigning the bug. Regards Aurelien Yes. Is correct. Thanks. -- Enviando desde Mozilla Thunderbird. OpenPGP_signature Description: OpenPGP digital signature
Bug#1025324: libc6: Xserver with nouveau not workiing.
El 2/12/22 a las 20:13, Aurelien Jarno escribió: Hi: Can you please give more details, especially which previous version of libc6 were you using? Also can you please try to downgrade your system to this version to confirm that the issue is linked to libc6? I think I know what it is. Although it jumps in libc6, as far as I can see it's a glx libraries issue (from the new version). I had 2.36.5 before. But I see it's not the problem. I rule it out entirely as libc6. I have tested it. I will look and do another way to report this bug. Unless it's libc6, because I've already ruled it out (tried and tested). I'll do it with more time, but as I said before, I'm using the generic graphics card driver. I will solve it. -- Enviando desde Mozilla Thunderbird. OpenPGP_signature Description: OpenPGP digital signature
Bug#1025324: libc6: Xserver with nouveau not workiing.
Package: libc6 Version: 2.36-6 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** It crashes only when I restart the graphical environment and gives me errors on several sides when I have the module. I am loading through the generic graphics card module. The failure is the following when booting Xorg. Attached is the Xorg file, where the libc6 bug is specified. In the previous version of libc6 it didn't crash for a moment. It is only in the new version of libc6. Thanks. -- System Information: Debian Release: bookworm/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-5-amd64 (SMP w/12 CPU threads; PREEMPT) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE=es Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libc6 depends on: ii libgcc-s1 12.2.0-9 Versions of packages libc6 recommends: ii libidn2-0 2.3.3-1+b1 Versions of packages libc6 suggests: ii debconf [debconf-2.0] 1.5.80 pn glibc-doc ii libc-l10n 2.36-6 ii libnss-nis 3.1-4 ii libnss-nisplus 1.3-4 ii locales2.36-6 -- debconf information: glibc/restart-services: glibc/disable-screensaver: * glibc/upgrade: true * libraries/restart-without-asking: true glibc/restart-failed: glibc/kernel-too-old: glibc/kernel-not-supported: Xorg.0.log.old Description: application/json
Bug#1017355: quodlibet: hierarchical browsing
Package: quodlibet Version: 4.3.0-1 Severity: wishlist Hi, Please, forward this to upstream. I find it inconvenient to browse in large music collections. Would it be possible to have hierarchical browsing added? First level would be: Album artist / Artist / Genre Second level would be the albums for Album artist or Artist. And it would be Album Artist / Artist for Genre. Thanks a lot in advance. Regards, JL
Bug#1016823: Thunar: add Lens Model to Image tab [patch attached]
Package: thunar
Version: 4.16.8-1
Severity: wishlist
Tags: patch
Hi,
Patch for including Lens ("Lens Model" is the actual EXIF tag name) in
Image tab, just after camera model is included at the bottom. A Spanish
translation for the field text is also included in the patch.
Please, forward to upstream and include as a patch in the meantime for
sid.
Thanks in advance.
Regards,
José Luis
--- thunar-4.16.8/po/es.po 2021-05-07 15:29:31.0 +0200
+++ thunar-4.16.8.new/po/es.po 2022-08-08 04:19:37.690410704 +0200
@@ -3322,2 +3322,5 @@ msgstr "Modelo de la cámara:"
+msgid "Lens Model:"
+msgstr "Modelo del objetivo:"
+
#: ../plugins/thunar-apr/thunar-apr-image-page.c:50
--- thunar-4.16.8/plugins/thunar-apr/thunar-apr-image-page.c2021-05-07
13:50:34.0 +0200
+++ thunar-4.16.8.new/plugins/thunar-apr/thunar-apr-image-page.c
2022-08-08 04:03:43.126388054 +0200
@@ -49,2 +49,3 @@ static const struct
{ N_ ("Camera Model:"), EXIF_TAG_MODEL, },
+ { N_ ("Lens Model:"),EXIF_TAG_LENS_MODEL, },
{ N_ ("Exposure Time:"), EXIF_TAG_EXPOSURE_TIME, },
Bug#1016729: abcde: ignores -j option
Package: abcde Version: 2.9.3-1 Hi, It seems abcde is ignoring the MAXPROCS abcde.conf variable and corresponding -j option. I have set 4 processes and get no concurrent enconding in a 4 CPUs machine. This is a recent issue. abcde used to work well with this. Regards, José Luis
Bug#1006740: xfce4-popup-applicationsmenu doesn't pop up the applications menu
Package: xfce4-panel Version: 4.16.2-1 Severity: important Hi, xfce4-popup-applicationsmenu doesn't show the applications menu since I upgraded to Debian 11. It's the command tied to ALT-F1 shortcut, so it makes that key shortcut unusable. I used it quite a lot, hence the important severity. Cheers, José Luis
Bug#989319: Sylpheed: inbox messages missing
Ricardo Mones escribió: control: severity -1 normal control: tags -1 = unreproducible moreinfo Hi José, Hi Ricardo, Sorry for my late reply. I have been unable to read email for a hell of time. On Tue, Jun 01, 2021 at 04:01:01AM +0200, José Luis González wrote: Package: sylpheed Version: 3.7.0-4 Severity: critical Tags: upstream Since about a month or two Sylpheed isn't showing me my inbox messages. However it's printed 0/n total, with n > 0. Sorry, but don't really understand what you mean here. Firstly, what type of account are you using? An IMAP Google account. Can you please also detail the steps you're taking since opening the application up to the point you call "show my inbox", what would you expect and what you currently see? (feel free to send some screenshot) Just opening the inbox folder for that account. I expect to see the email messages I have in that folder, but instead I see as if there were no messages on inbox. The messages list panel shows no messages. The status bar of the folder shows correct stats, though (0/4, if there were 4 messages in the inbox, 0 I understand is for the number of message displayed, which since is none 0 is printed). I am unable to send you a screenshot at thie time, but surely will when I can, make no mistake. BTW, I marked it as critical since this renders the program practically unusuable for me. Regard, and all the best, José Luis
Bug#998728: gnupg: gpg-agent ssh refuses smartcad operation
Package: gnupg Version: 2.2.27-2 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Using gpg agent for ssh returns refused operation when using smartcard. * What exactly did you do (or not do) that was effective (or ineffective)? I configured the gpg agent by adding enable-ssh-support to ~/.gnupg/gpg-agent.conf, I added also my key grip to .gnupg/sshcontrol and I added the following lines to my .bashrc: export GPG_TTY=$(tty) export SSH_AUTH_SOCK=$(gpgconf --list-dirs agent-ssh-socket) Since then I can see: $ ssh-add -l 4096 SHA256:QXx1d/USG3KeT3UqD74YXHnTM5SEbzZ0t3HREUcpEjI cardno:000609023428 (RSA) And: ● gpg-agent-ssh.socket - GnuPG cryptographic agent (ssh-agent emulation) Loaded: loaded (/usr/lib/systemd/user/gpg-agent-ssh.socket; enabled; vendor preset: enabled) Active: active (running) since Sun 2021-11-07 10:27:36 EET; 42min ago Triggers: ● gpg-agent.service Docs: man:gpg-agent(1) man:ssh-add(1) man:ssh-agent(1) man:ssh(1) Listen: /run/user/1000/gnupg/S.gpg-agent.ssh (Stream) CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/gpg-agent-ssh.socket However, when I do a git clone over ssh, I see: sign_and_send_pubkey: signing failed for RSA "cardno:000609023428" from agent: agent refused operation * What was the outcome of this action? sign_and_send_pubkey: signing failed for RSA "cardno:000609023428" from agent: agent refused operation * What outcome did you expect instead? Doing the git clone. *** End of the template - remove these template lines *** -- System Information: Debian Release: 11.1 APT prefers stable APT policy: (700, 'stable'), (650, 'testing'), (500, 'stable-updates'), (500, 'stable-security') Architecture: amd64 (x86_64) Kernel: Linux 5.14.9 (SMP w/8 CPU threads) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnupg depends on: ii dirmngr 2.2.27-2 ii gnupg-l10n 2.2.27-2 ii gnupg-utils 2.2.27-2 ii gpg 2.2.27-2 ii gpg-agent 2.2.27-2 ii gpg-wks-client 2.2.27-2 ii gpg-wks-server 2.2.27-2 ii gpgsm 2.2.27-2 ii gpgv2.2.27-2 gnupg recommends no packages. Versions of packages gnupg suggests: pn parcimonie pn xloadimage -- no debconf information
Bug#998008: libc-bin: postinst makes a working NIS system not to work anymore at every point release
Para evitar que pille de improviso a alguien, he actualizado todos los equipos (de salma) a 11.1 copiados en todos el archivo nsswitch.conf ya modificado de salma1 Mañana lo haré con Estadística. salma ya son 21, puedes cambiarlo donde convenga para que ansible funcione. Ahora voy a avisar a Juan Ma Gracias. Un saludo. El 28/10/21 a las 15:18, Santiago Vila escribió: Package: libc-bin Version: 2.31-13+deb11u2 Severity: serious Tags: patch Dear libc-bin maintainers: In Debian 11, the default /etc/nsswitch.conf file has now "files" instead of the traditional "compat". So far, so good. This is documented in Release Notes, and those who need NIS may change /etc/nsswitch.conf if they need it. But there is a problem: The postinst updates the file every time it is detected that it matches *any* old default (via md5sum). This is a functionality which was part of base-files in the past and it was useful when there was a default /etc/nsswitch.conf which would work for almost everybody. But this is not the case anymore, because the default file is not good for those using NIS. As a result, not only upgrading a Debian 10 system to Debian 11 makes NIS to require an adjustment (i.e. putting compat again after postinst modifies the file), but also each and every upgrade from Debian 11 point x to Debian 11 point x+1. Patch attached. I hope this may be fixed for Debian 11.2. Thanks.
Bug#997530:
Hi Lucas, Thanks for reporting! I've investigated this and found that the error comes from building against a version of the package "cv_bridge" (libcv-bridge-dev) which wasn't yet rebuilt against the latest opencv 4.5.4, but for the older 4.5.3. Does this still qualify as a FTBFS error in mrpt? "libcv-bridge-dev" is already listed in d/control... (?). Best, JL
Bug#996761: kwin-x11: KWin crashes and doesn't start
Hello Bernhard, yes it is same issue mentioned in #996726, not related to nvidia-driver. Thanks a lot. El lun., 18 oct. 2021 23:16, Bernhard Übelacker escribió: > Hello Francisco, hello Albert, > this might be the same as in bug #996726 > and not directly related to the nvidia driver. > > I hit a crash in kwin_x11 with an AMD graphics card > and could workaround by installing > libkdecorations2-5v5_5.21.5-2_amd64.deb like > mentioned in #996726. > > Kind regards, > Bernhard > > https://bugs.debian.org/996726 >
Bug#996761: kwin-x11: KWin crashes and doesn't start
Thank you so much Patrick, yes I'm using testing. I downgraded libkdecorations2-5v5 and now it works fine. Kind regards. On Mon, 18 Oct 2021 22:45:17 +0200 Patrick Franz wrote: > Hi, > > I assume you're using testing. Unfortunately, Plasma is broken in > testing at the moment if you have upgraded libkdecorations2-5v5 to 5.23. > Could you check that ? > > If this is the case, I wrote about a possible solution here: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996726#10 > > > -- > Med vänliga hälsningar > > Patrick Franz > > > >
Bug#996761: kwin crash on startup
Hi, yes, I confirm sobre behaviour as Albert, other environments are working with no issues, such as LXDE or xfce...but KDE/Plasma available in testing is currently unusable with latest nvidia-driver. Thanks. On Mon, 18 Oct 2021 21:57:43 +0200 Albert Netymk wrote: > I had the same problem as Francisco reported. > > My Nvidia card is NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] > > kwin-x11: 4:5.21.5-2 > nvidia-driver: 470.74-1 > linux-image-amd64: 5.14.9-2 > > I tried to downgrade nvidia-driver, but had problems while installing > the package from stable release, so I went to install LXDE instead, > which seems to work fine with the latest nvidia-driver. > > /Albert > >
Bug#995693: cockpit-machines: Request to build for bullseye-backports
Package: cockpit-machines Version: 239-1 Severity: wishlist I would like to try cockpit-machines v251 in bullseye but that is currently not possible because, while cockpit v251 package is released in bullseye-backports, cockpit-machines is not. Please build cockpit-machines v251 for bullseye-backports. Best regards, José Miguel Gonçalves -- System Information: Debian Release: 11.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-8-amd64 (SMP w/40 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages cockpit-machines depends on: ii libvirt-clients7.0.0-3 ii libvirt-daemon-system 7.0.0-3 ii libvirt-dbus 1.4.0-2 Versions of packages cockpit-machines recommends: ii gir1.2-libosinfo-1.0 1.8.0-1 ii python3-gi3.38.0-2 ii qemu-block-extra 1:5.2+dfsg-11+deb11u1 ii virtinst 1:3.2.0-3 cockpit-machines suggests no packages. -- no debconf information
Bug#930751: wpasupplicant: Please enable support for 802.11s (mesh)
Any chance to enable this support soon (in bullseye or bullseye-backports)? Best regards, José Gonçalves
Bug#993636: printer-driver-pnm2ppa: Problem installation this version.
Package: printer-driver-pnm2ppa Version: 1.13-11 Severity: important Dear Maintainer, Fail installation only this error script: Preparando para desempaquetar printer-driver-pnm2ppa_1.13-11_amd64.deb ... Desempaquetando printer-driver-pnm2ppa (1.13-11) sobre (1.13-11) ... Configurando printer-driver-pnm2ppa (1.13-11) ... /var/lib/dpkg/info/printer-driver-pnm2ppa.postinst: 1: tempfile: not found dpkg: error al procesar el paquete printer-driver-pnm2ppa (--install): el subproceso instalado paquete printer-driver-pnm2ppa script post-installation devolvió el código de salida de error 127 Procesando disparadores para doc-base (0.11.1) ... Processing 3 changed doc-base files... Procesando disparadores para man-db (2.9.4-2) ... Se encontraron errores al procesar: printer-driver-pnm2ppa This fail is only package. Others packages is not necessary. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-8-amd64 (SMP w/12 CPU threads) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE=es Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages printer-driver-pnm2ppa depends on: ii debconf [debconf-2.0] 1.5.77 ii ghostscript9.53.3~dfsg-7+b1 ii libc6 2.31-17 printer-driver-pnm2ppa recommends no packages. Versions of packages printer-driver-pnm2ppa suggests: pn magicfilter | apsfilter -- debconf information: pnm2ppa/use_debconf: true pnm2ppa/create_magicfilter: false pnm2ppa/printer_model: 710
Bug#982857: Still present in imagemagick-6-doc 8:6.9.11.60+dfsg-1.3
I am still experiencing this bug with the most recent version from testing: - Self-closing iframe tag prevents page content to be rendered in both Firefox and Chrome - Missing magick.css (seems to be in the wrong place under api/assets and referenced under www/magick.css) As a workaround, I managed to view the documentation using Konqueror browser in the KHTML rendering mode. I had to use a custom stylesheet too because of my dark theme. Does it help if I try to send a patch for this fix somehow? Would a sed/ command during package time works to avoid a full source version update? -- Ronoaldo Pereira Ronoaldo Consulting +55 11 98703 0927 ronoa...@ronoaldo.com www.ronoaldo.com
Bug#966294: Processed: Re: #966294: asterisk: memory leak with PJSIP channel
On 13/07/21 14:04, Chris Hofstaedtler wrote: Control: tags -1 - confirmed Hi Bernhard, * Bernhard Schmidt [210428 15:41]: hrm, Jose reported this issue appearing with the stable release only (16.16.1 from his (back then) private backport fixing it), you tagged the bug as still found in 16.16.1, and I cannot see this issue at all. Unfortunately I don't know what to do with this bug. I must say I'm also at a loss with this bug. The memory leak has "vanished" after restarting enough or something. :-( Chris I confirm that this bug only happens with the buster release (16.2.1). I'm currently using the version from buster-backports (16.16.1) without any problem. Best regards, José Gonçalves
Bug#990717: [Pkg-xen-devel] Bug#990717: xen-system-amd64: Microcode isn't loaded when booting in xen mode
OMG, I supposed it will enough to put a line like: ucode=scan As soon as I tried a line like: GRUB_CMDLINE_XEN="ucode=scan" The system behaviour changed I still have a couple de lines in /var/log/kern.log saying: Jul 5 19:38:19 xuxa3 kernel: [ 22.487806] VPMU disabled by hypervisor. | Jul 5 19:38:19 xuxa3 kernel: [ 22.488166] Performance Events: unsupported p6 CPU model 79 no PMU driver, software events only. But this seems another problem because while booting with standard kernel I got: Jul 5 14:05:17 xuxa3 kernel: [0.837414] Performance Events: PEBS fmt2+, Broadwell events, full-width counters, Broken BIOS detected, complain to your hardware vendor. Jul 5 14:05:17 xuxa3 kernel: [0.837427] [Firmware Bug]: the BIOS has corrupted hw-PMU resources (MSR 38d is 330) Jul 5 14:05:17 xuxa3 kernel: [0.837504] Intel PMU driver. Jul 5 14:05:17 xuxa3 kernel: [0.837508] ... version:3 Jul 5 14:05:17 xuxa3 kernel: [0.837509] ... bit width: 48 Jul 5 14:05:17 xuxa3 kernel: [0.837510] ... generic registers: 8 Jul 5 14:05:17 xuxa3 kernel: [0.837511] ... value mask: Jul 5 14:05:17 xuxa3 kernel: [0.837512] ... max period: 7fff Jul 5 14:05:17 xuxa3 kernel: [0.837513] ... fixed-purpose events: 3 Jul 5 14:05:17 xuxa3 kernel: [0.837514] ... event mask: 000700ff I don't know if you could help me with this, but as long I see the microcode has been loaded and this bugs can be closed Thanks very much,El lun, 05-07-2021 a las 14:35 +, Andy Smith escribió: > Hello, > > On Mon, Jul 05, 2021 at 03:13:17PM +0200, José L. Fernández Jambrina> wrote: > > When booting in Xen mode my system doen't load microcode, > > It is my understanding that when booting the hypervisor it is the > hypervisor's job to load microcode, and it won't do so unless you > have something like: > > ucode=scan > > in your hypervisor command line, e.g. by putting: > > GRUB_CMDLINE_XEN="ucode=scan" > > in /etc/default/grub. > > Do you have something like that? > > That will cause the hypervisor to scan the other boot files (kernel > and initramfs) for microcode to apply, like the kernel itself would > otherwise do. > > It works for me, anyway. > > Cheers, > Andy
Bug#990717: xen-system-amd64: Microcode isn't loaded when booting in xen mode
Package: xen-system-amd64 Version: 4.11.4+107-gef32c7afa2-1 Severity: important Dear Maintainer, When booting in Xen mode my system doen't load microcode, I suposse this is the reason I have a line in /var/log/kern.log saying: |Jun 28 17:09:28 xuxa3 kernel: [3.013020] Performance Events: unsupported p6 CPU model 79 no PMU driver, software events only And perfomamce is degraded: When booting the system in normal mode, no xen mode, the first two lines written in /var/log/kern.log say: | Jul 5 14:05:17 xuxa3 kernel: [0.00] microcode: microcode updated early to revision 0xb3e, date = 202 1-02-06 | Jul 5 14:05:17 xuxa3 kernel: [0.00] Linux version 4.19.0-17-amd64 (debian-ker...@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.194-1 (2021-06-10) In xen mode the first line insn't written at all. I can't remenber if the first time I installed xen the microcode was loaded or not, but as long as I can check the microcode isn't loaded and the system performance is clearly degraded. Yours, Jose L. -- System Information: Debian Release: 10.10 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-17-amd64 (SMP w/8 CPU cores) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE=es_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages xen-system-amd64 depends on: ii xen-hypervisor-4.11-amd64 4.11.4+107-gef32c7afa2-1 ii xen-hypervisor-common 4.11.4+107-gef32c7afa2-1 ii xen-utils-4.11 4.11.4+107-gef32c7afa2-1 xen-system-amd64 recommends no packages. xen-system-amd64 suggests no packages. -- no debconf information
Bug#989319: Sylpheed: inbox messages missing
Package: sylpheed Version: 3.7.0-4 Severity: critical Tags: upstream Since about a month or two Sylpheed isn't showing me my inbox messages. However it's printed 0/n total, with n > 0.
Bug#989318: GNOME network manager: security hole
Package: gnome-network-manager Version: 1.14.6-2+deb10u1 Severity: critical GNOME Network Manager takes too long to update its status in the system tray sometimes.
Bug#966294: Fwd: Processed: Re: #966294: asterisk: memory leak with PJSIP channel
Hi, I'm currently using the asterisk build from buster-backports (16.16.1) and the leak does not happen on it. Best regards, José Gonçalves
