Bug#325689: looking at it
i don't have debian but if those who do help then i'm sure we can figure this out. it's a high priority for me that the linux client runs great. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#843589: Change severity
Hi, I don't really know if this should be an RC bug, but this package has entered testing. And as such, migration is not possible without fetching source package. Adrien
Bug#830683: Missing dependency on module-udev?
On Sun, 10 Jul 2016 23:37:01 -0300 Felipe Sateler wrote: > > Do you have disabled installation of Recommends? > Hi, I guess he did, just like me, because installing recommends often leads to a workload of useless packages. Even if I totally understand that the packager is not expected to support every configuration, maybe a line or two in NEWS.Debian should be enough. I read each Changelog.Debian, I saw the split announcement, but I totally missed the fact that it will render my system soundless. Adrien
Bug#830683: Missing dependency on module-udev?
Le 14/07/2016 à 13:51, Scott Leggett a écrit : > > If a package really does recommend other packages which are useless, you > should file a bug on that package, not just start blindly using > --no-install-recommends everywhere. It is a never ending debate. If installing recommended packages is the default, then it is more like a dependency, since the package will get installed anyway. That's why APT::Install-Recommends "false" is in my apt.conf. When I install a package, I read the summary, and decide by myself to install or not some or all recommended packages. There should be an "ask" value by the way. However, when a builtin code is moved to a recommended package, it can broke some systems. So the changelog should clearly mentionned that the split is done in a recommended package, because apt does not do that. > The relationship between pulseaudio and pulseaudio-module-udev matches > the Policy description of the Recommends field. I totally trust you on this point. However, the arguable issue we have here is when a new recommended package is created with some previously builtin features. Adrien
Bug#830074: fixed in iodine 0.7.0-5
Sorry for being late on all of this, but I have a few remarks on this. First, thanks for the service file, and the long explanation. Regarding socket activation, I currently have this (custom) socket unit: [Unit] Description=Iodine socket [Socket] # For now, listen only in IPv4 ListenDatagram=0.0.0.0:5354 BindIPv6Only=both [Install] WantedBy=sockets.target This is fine. It does not solve the case where "-i" exit too quickly, but I have not experienced this. Do you have a bug report for this incorrect behavior? Since iodine is a pure network service, it should be protected as much as possible with systemd's own mechanism like: PrivateTmp=true ProtectSystem=full ProtectHome=true NoNewPrivileges=true I understand that chroot can offer some protection, so I'll be glad to here that those directive are useless with it. In the same way, I may have missed new containement directives that can be used to restrict the attack surface further. Adrien
Bug#564936: grub-pc: reproducable
Package: grub-pc
Severity: normal
I can also reproduce this problem with grub 1.98~20100115-1. Removing grub.cfg
lets grub
go into it's recovery prompt.
Reinstalling grub does not fix anything.
Downgrading to 1.98~20100107-1 makes everyting work again.
-- Package-specific info:
*** BEGIN /proc/mounts
/dev/root / ext3 rw,relatime,errors=remount-ro,data=ordered 0 0
/dev/hda4 /home ext3 rw,relatime,errors=continue,data=ordered 0 0
/dev/hda1 /mnt/windows vfat
rw,noexec,relatime,fmask=0111,dmask=,allow_utime=0022,codepage=cp850,iocharset=iso8859-15,errors=remount-ro
0 0
*** END /proc/mounts
*** BEGIN /boot/grub/device.map
(hd0) /dev/hda
*** END /boot/grub/device.map
*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
set default=0
insmod ext2
set root=(hd0,3)
search --no-floppy --fs-uuid --set 8bb75fa5-df36-459f-9f26-907e713477b4
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=640x480
insmod gfxterm
insmod vbe
if terminal_output gfxterm ; then true ; else
# For backward compatibility with versions of terminal.mod that don't
# understand terminal_output
terminal gfxterm
fi
fi
set locale_dir=/boot/grub/locale
set lang=
insmod gettext
set timeout=5
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
menuentry "Debian GNU/Linux, with Linux 2.6.31.11" {
insmod ext2
set root=(hd0,3)
search --no-floppy --fs-uuid --set 8bb75fa5-df36-459f-9f26-907e713477b4
linux /boot/vmlinuz-2.6.31.11 root=/dev/hda3 ro
}
menuentry "Debian GNU/Linux, with Linux 2.6.31.6" {
insmod ext2
set root=(hd0,3)
search --no-floppy --fs-uuid --set 8bb75fa5-df36-459f-9f26-907e713477b4
linux /boot/vmlinuz-2.6.31.6 root=/dev/hda3 ro
}
menuentry "Debian GNU/Linux, with Linux 2.6.31.4" {
insmod ext2
set root=(hd0,3)
search --no-floppy --fs-uuid --set 8bb75fa5-df36-459f-9f26-907e713477b4
linux /boot/vmlinuz-2.6.31.4 root=/dev/hda3 ro
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/30_os-prober ###
menuentry "Microsoft Windows XP Professional (on /dev/hda1)" {
insmod fat
set root=(hd0,1)
search --no-floppy --fs-uuid --set 4331-703f
drivemap -s (hd0) ${root}
chainloader +1
}
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
*** END /boot/grub/grub.cfg
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.31.11 (PREEMPT)
Locale: LANG=en_GB, LC_CTYPE=es_ES (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash
Versions of packages grub-pc depends on:
ii debconf [debconf-2.0]1.5.28 Debian configuration management sy
ii grub-common 1.98~20100101-1 GRand Unified Bootloader, version
ii libc62.10.2-2GNU C Library: Shared libraries
ii ucf 3.0025 Update Configuration File: preserv
grub-pc recommends no packages.
Versions of packages grub-pc suggests:
ii desktop-base 5.0.5 common files for the Debian Deskto
-- debconf information:
grub2/kfreebsd_cmdline:
* grub2/linux_cmdline:
* grub-pc/chainload_from_menu.lst: true
grub-pc/kopt_extracted: true
* grub-pc/install_devices: /dev/hda
grub-pc/postrm_purge_boot_grub: false
grub2/kfreebsd_cmdline_default: quiet
* grub2/linux_cmdline_default:
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#520967: SCSI HDD Issues with 2009.03.22 Nightly
Package: installation-reports Boot method: Minimal Netinst from CD-R Image version: http://laotzu.acc.umu.se/cdimage/daily-builds/daily/arch-latest/i386/iso-cd/debian-testing-i386-businesscard.iso Date: 2009.03.22 Machine: Dell Precision 670 Processor: 2x Xeon 3.6 w/hyperthreading enabled Memory: 2GB Partitions: Blank Output of lspci -knn (or lspci -nn): Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [E] Detect CD: [O] Load installer modules: [O] Detect hard drives: [E] Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: Loved the graphical installer, very slick. Anyway, to business. Ages ago I reported that DHCP didn't work from the netinst (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=479473) I suspect that issue still exists as DHCP still fails. Moving on with static settings, I got to the point of setting up the disks. The mobo has an Adaptec U320 SCSI controller (aic79xx), and I have several drives connected (with various old partitions on each that are all going to be wiped). The installer reports no drives were detected. I fired up the console, and ls /dev/sd* shows all of the drives are there; /dev/sda-d (plus all the usual partition devices) fdisk lets me examine them, and all have their expected partition tables, showing the drives are accessible just fine. I have no idea why the installer does not detect them. signature.asc Description: OpenPGP digital signature
Bug#893972: [borgbackup] msgpack-python>=0.4.6 distribution was not found
After another apt update; apt upgrade, everything is working fine… I don't know if it was linked, but there was an update for: python3-pkg-resources (38.5.2-1 => 39.0.1-1) python3-setuptools (38.5.2-1 => 39.0.1-1) Anyway, this can be closed for me. Sorry for the disturbance. Adrien
Bug#942562: Use opencv.pc
Hi, Is there any reason to use opencv4.pc as filename? Previously, it was opencv.pc, so now, we need to modify all references to it. Since pkg-config already provides a way to check version, I think it's better to keep the old unversioned name. Have a nice day, Adrien
Bug#903491: [marble]
Package: marble
Version: 4:17.08.3-3
--- Please enter the report below this line. ---
Upstream bug: https://bugs.kde.org/show_bug.cgi?id=394517
So nobody has proposed something yet. Since contributing to Marble is a
bit complicated (I don't have any account for now), here is a small patch.
Adrien
--- System information. ---
Architecture:
Kernel: Linux 4.16.0-2-amd64
Debian Release: buster/sid
500 unstable ftp.fr.debian.org
500 testing download.jitsi.org
1 experimental ftp.fr.debian.org
--- Package information. ---
Depends (Version) | Installed
===-+-=
marble-data (>= 4:17.08.3-3) | 4:17.08.3-3
marble-plugins (= 4:17.08.3-3) | 4:17.08.3-3
kio | 5.47.0-1
libc6 (>= 2.14) | 2.27-4
libgcc1 (>= 1:3.0) | 1:8.1.0-9
libkf5configcore5 (>= 4.98.0) | 5.47.0-1
libkf5configgui5 (>= 4.97.0) | 5.47.0-1
libkf5configwidgets5 (>= 4.96.0) | 5.47.0-1
libkf5coreaddons5 (>= 4.100.0) | 5.47.0-1
libkf5crash5 (>= 4.96.0) | 5.47.0-1
libkf5i18n5 (>= 4.97.0) | 5.47.0-1
libkf5kiowidgets5 (>= 4.99.0) | 5.47.0-1
libkf5newstuff5 (>= 4.95.0) | 5.47.0-1
libkf5parts5 (>= 4.96.0) | 5.47.0-1
libkf5widgetsaddons5 (>= 4.96.0) | 5.47.0-1
libkf5xmlgui5 (>= 4.98.0) | 5.47.0-1
libmarblewidget-qt5-28 (= 4:17.08.3-3) | 4:17.08.3-3
libqt5core5a (>= 5.9.0~beta) | 5.10.1+dfsg-7
libqt5dbus5 (>= 5.4) | 5.10.1+dfsg-7
libqt5gui5 (>= 5.7.0) | 5.10.1+dfsg-7
libqt5network5 (>= 5.4) | 5.10.1+dfsg-7
libqt5printsupport5 (>= 5.4) | 5.10.1+dfsg-7
libqt5widgets5 (>= 5.4) | 5.10.1+dfsg-7
libqt5xml5 (>= 5.4) | 5.10.1+dfsg-7
libstdc++6 (>= 4.1.1) | 8.1.0-9
Package's Recommends field is empty.
Suggests (Version) | Installed
===-+-===
gosmore |
monav-routing-daemon |
routino |
Index: marble-17.08.3/src/plugins/runner/nominatim-reversegeocoding/OsmNominatimReverseGeocodingRunner.cpp
===
--- marble-17.08.3.orig/src/plugins/runner/nominatim-reversegeocoding/OsmNominatimReverseGeocodingRunner.cpp
+++ marble-17.08.3/src/plugins/runner/nominatim-reversegeocoding/OsmNominatimReverseGeocodingRunner.cpp
@@ -49,7 +49,7 @@ void OsmNominatimRunner::returnNoReverse
void OsmNominatimRunner::reverseGeocoding( const GeoDataCoordinates &coordinates )
{
m_coordinates = coordinates;
-QString base = "http://nominatim.openstreetmap.org/reverse?format=xml&addressdetails=1";;
+QString base = "https://nominatim.openstreetmap.org/reverse?format=xml&addressdetails=1";;
// @todo: Alternative URI with addressdetails=1 could be used for shorther placemark name
QString query = "&lon=%1&lat=%2&accept-language=%3";
double lon = coordinates.longitude( GeoDataCoordinates::Degree );
Index: marble-17.08.3/src/plugins/runner/nominatim-search/OsmNominatimSearchRunner.cpp
===
--- marble-17.08.3.orig/src/plugins/runner/nominatim-search/OsmNominatimSearchRunner.cpp
+++ marble-17.08.3/src/plugins/runner/nominatim-search/OsmNominatimSearchRunner.cpp
@@ -50,7 +50,7 @@ void OsmNominatimRunner::returnNoResults
void OsmNominatimRunner::search( const QString &searchTerm, const GeoDataLatLonBox &preferred )
{
-QString base = "http://nominatim.openstreetmap.org/search?";;
+QString base = "https://nominatim.openstreetmap.org/search?";;
QString query = "q=%1&format=xml&addressdetails=1&accept-language=%2";
QString url = QString(base + query).arg(searchTerm).arg(MarbleLocale::languageCode());
if( !preferred.isEmpty() ) {
Bug#903815: ITP: pw -- A simple command-line password manager
> This is called proof by counter-example. > If you cannot do this, and if nobody else can do this, then you cannot > claim that it is not safe to use this script. This is not a valid argument. Nobody can yet prove (by example) that it is not safe to go near a black hole. But it is not safe. The non existence of a counter-example does not mean that the theory is valid. Nonetheless, I don't have any opinion about pw. I use pass, and I think that forks are welcomed. Adrien
Bug#955779: [miniupnpd] iptables-init.sh does not create POSTROUTING
Package: miniupnpd Version: 2.1-6.1 Severity: normal --- Please enter the report below this line. --- Hi, According to https://github.com/miniupnp/miniupnp/issues/334 some initialization logic was lost in iptables-init.sh. It was reinstated in https://github.com/miniupnp/miniupnp/commit/c3f752db4a8286be00ad1d8b2a9fab37dc8d116d It should be integrated, since for now, it's not possible to add redirection port, as the postrouting chain doesn't exist. Adrien --- System information. --- Architecture: Kernel: Linux 5.4.0-4-amd64 Debian Release: bullseye/sid 500 unstable-debug debug.mirrors.debian.org 500 unstable ftp.debian.org 500 testing download.jitsi.org 1 experimental ftp.fr.debian.org --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty.
Bug#955811: [pgbackrest] Binary moved from /usr/bin to /bin
Package: pgbackrest Version: 2.25-2 Severity: normal --- Please enter the report below this line. --- Hi, >From 2.14-1 to 2.25-2, the main binary moved from /usr/bin to /bin. I know that we should have merged /usr but it should either be mentioned in the changelog, or revert the change. For now, I'll change my cron jobs. Adrien --- System information. --- Architecture: Kernel: Linux 5.4.0-4-amd64 Debian Release: bullseye/sid 500 unstable-debug debug.mirrors.debian.org 500 unstable ftp.debian.org 500 testing download.jitsi.org 1 experimental ftp.fr.debian.org --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty.
Bug#825748: (no subject)
Additionnal informations:
python
Python 2.7.11+ (default, May 9 2016, 15:54:33)
[GCC 5.3.1 20160429] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import requests; requests.__version__.split('.')
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python2.7/dist-packages/requests/__init__.py", line
61, in
from .packages.urllib3.exceptions import DependencyWarning
ImportError: cannot import name DependencyWarning
Bug#323032: Same problem two years later with the last upgrade
Hello, right after this morning last upgrade, my proftp server and my webmin stopped to work throwing out these errors : /var/log/webmin/miniserv.error:/usr/bin/perl: relocation error: /lib/libresolv.so.2: symbol __res_iclose, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference And (accepting connections): relocation error: /lib/libresolv.so.2: symbol __res_iclose, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference I just had to restart those services then everything worked well... Perhaps the upgrade script for libc6 should look which running services are using libc6 and restart them ;) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#938987: Overly restrictive CapabilityBoundingSet
Thank you very much! Adding CAP_DAC_OVERRIDE solved it for me as well. Not sure how many hours it would have taken for me to figure it out. Does systemd or the linux kernel log capability violations somewhere? (is it even possible) smime.p7s Description: S/MIME Cryptographic Signature
Bug#1100878: (No Subject)
I bumped into the same issue as Nolan. I didn't try installing bookworm, but same outcome with the live CD (works) and via the Calamares installer (does not work). I noticed that the system installed via Calamares comes only with a handful of firmware files. I couldn't get systemd to open a resuce terminal, perhaps because of this same issue, so I booted a console via the installation CD and then installed the firmware-intel-graphics package on the target chroot and updated the initarmfs image: # apt install firmware-intel-graphics # update-initramfs -u -k all The culprit seemed to be that the firmware files for the Xe iGPU for Lunar Lake were missing (/lib/firmware/xe/lnl_gsc_1.bin , /lib/firmware/xe/lnl_guc_70.bin, /lib/firmware/xe/lnl_huc.bin). I tested this by manually copying these three files instead of installing the Debian package, and the system booted up fine afterwards. In the end I also installed live-task-non-free-firmware-pc, so that sound and other things worked.
Bug#1057385: lighttpd FTCBFS: host CFLAGS leak into build compiler invocation
On Mon, Dec 04, 2023 at 11:49:30AM +0100, Emanuele Rocca wrote: > With the attached patch lighttpd cleanly cross-builds from source. Thanks, Emanuele. A slightly different patch: https://salsa.debian.org/debian/lighttpd/-/commit/a7d695d59c9a8bffe154aae29e335102beaaf3f2 was committed a few weeks ago to salsa.debian.org, which I based off comments in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021292? Is your suggested approach (above) preferred to this patch (below)? @@ -50,9 +50,9 @@ override_dh_auto_configure: --with-xxhash \ --with-zstd \ $(if $(filter pkg.lighttpd.libunwind,$(DEB_BUILD_PROFILES)),--with-libunwind) \ - CFLAGS_FOR_BUILD="$(shell dpkg-buildflags --get CFLAGS)" \ - LDFLAGS_FOR_BUILD="$(shell dpkg-buildflags --get LDFLAGS)" \ - CPPFLAGS_FOR_BUILD="$(shell dpkg-buildflags --get CPPFLAGS)" \ + CFLAGS_FOR_BUILD="$$(dpkg-architecture -a$(DEB_BUILD_ARCH) -f -c dpkg-buildflags --get CFLAGS)" \ + LDFLAGS_FOR_BUILD="$$(dpkg-architecture -a$(DEB_BUILD_ARCH) -f -c dpkg-buildflags --get LDFLAGS)" \ + CPPFLAGS_FOR_BUILD="$$(dpkg-architecture -a$(DEB_BUILD_ARCH) -f -c dpkg-buildflags --get CPPFLAGS)" \ override_dh_install: cp NEWS debian/tmp/changelog
Bug#1067126: RFS: lighttpd/1.4.76-3 -- light, fast, functional web server
Gianfranco, thank you for sponsoring this upload. > Please some nitpicks for a future upload > 1) wait for the sponsor upload before tagging, >many of your entries were never uploaded ack. Still, this seems like unnecessary latency between humans once a Debian developer volunteer picks up the sponsorship-request. This sponsorship-request bug was filed March 19 and as I write this, today is May 29, over two months later. > 2) don't create new entries if the previous ones are not yet in the archive Should the now-incorrect tags in the repository be deleted and re-tagged? I prefer not to move tags once the tag matches code on the master branch, hence why I created new entries in the changelog and new tags. Also, this sounds like a fragile limitation for which a bug should be filed. When uploading, it should be possible to programmatically query the current version in the archive, find that changelog entry, and then process the newer entries with versions between the current version in the archive and the new version being submitted. Cheers, Glenn
Bug#1065247: new lighttpd servers mangled file names
FYI, I submitted a patch to Debian on 19 March, over two months ago. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067126 It has taken Debian developers (volunteers) over 10 weeks (!!!) to pick up a simple patch that I packaged for them and signed on salsa.debian.org. :(
Bug#1067126: RFS: lighttpd/1.4.75-1 -- light, fast, functional web server
Package: sponsorship-requests Severity: normal X-Debbugs-Cc: gs-bugs.debian@gluelogic.com Dear mentors, I am looking for a DD sponsor for my package "lighttpd": https://salsa.debian.org/debian/lighttpd/ I am an upstream lighttpd developer and have participated in maintaining lighttpd on Debian for a number of years. I am listed as an uploader on https://tracker.debian.org/pkg/lighttpd lighttpd-1.4.75-1 passes autopkgtests and expected CI tests, and is tagged. (This is a non-DD maintainer upload.) * Package name : lighttpd Version : 1.4.75-1 Upstream contact : team+light...@tracker.debian.org * URL : https://lighttpd.net/ * License : BSD-3-Clause * Vcs : https://git.lighttpd.net/lighttpd/lighttpd1.4 Thank you. Glenn P.S. There is a regression in lighttpd 1.4.74 that is fixed with a patch in tag lighttpd-1.4.74-3 on salsa.d.o. Does that need to go through the release process for the changelog entries to automatically close bugs? If so, please upload 1.4.74-3 to Unstable, and in a few days 1.4.75-1. With the time64 migration, everything is stuck in Unstable, anyway. Note: with lighttpd 1.4.74-3, lighttpd is time64 agnostic and so this package could safely go to Testing, and will work properly (with 64-bit time_t) on 32-bit platforms even without the rest of the time64 libs.
Bug#1067126: RFS: lighttpd/1.4.76-3 -- light, fast, functional web server
lighttpd-1.4.76-3 passes autopkgtests and expected CI tests, and is tagged. (This is a non-DD maintainer upload.) * Package name : lighttpd Version : 1.4.76-3 Upstream contact : team+light...@tracker.debian.org * URL : https://lighttpd.net/ * License : BSD-3-Clause * Vcs : https://git.lighttpd.net/lighttpd/lighttpd1.4 lighttpd (1.4.76-3) unstable; urgency=medium * Patch to fix graceful shutdown timeout
Bug#1067126: RFS: lighttpd/1.4.76-2 -- light, fast, functional web server
lighttpd-1.4.76-2 passes autopkgtests and expected CI tests, and is tagged. (This is a non-DD maintainer upload.) * Package name : lighttpd Version : 1.4.76-2 Upstream contact : team+light...@tracker.debian.org * URL : https://lighttpd.net/ * License : BSD-3-Clause * Vcs : https://git.lighttpd.net/lighttpd/lighttpd1.4 lighttpd (1.4.76-2) unstable; urgency=medium * Fix FTBFS Linux on SPARC * Declare compliance with policy 4.7.0 - no changes needed.
Bug#1067126: RFS: lighttpd/1.4.76-1 -- light, fast, functional web server
lighttpd-1.4.76-1 passes autopkgtests and expected CI tests, and is tagged. (This is a non-DD maintainer upload.) * Package name : lighttpd Version : 1.4.76-1 Upstream contact : team+light...@tracker.debian.org * URL : https://lighttpd.net/ * License : BSD-3-Clause * Vcs : https://git.lighttpd.net/lighttpd/lighttpd1.4 lighttpd (1.4.76-1) unstable; urgency=medium * New upstream version 1.4.76 * Detect VU#421644 HTTP/2 CONTINUATION Flood * Avoid CVE-2024-3094 xz supply chain attack
Bug#1021021: wolfssl: CVE-2022-38152 CVE-2022-38153 CVE-2022-39173
> I plan to upload version 5.5.1 in the near future. Felix, a month has passed and we are still waiting for an upload. Failure to upload a version with security fixes within the next few days will result in wolfssl and packages which depend on wolfssl to be removed from Debian Testing. Please act accordingly and please look to engage others to help you to maintain wolfssl in Debian. Security fixes should not be unduly delayed. Thank you. Glenn
Bug#1040525: Lighttpd disregards ssl.dh-file setting
On Fri, Jul 07, 2023 at 09:28:24AM +, Alain Knaff wrote: > Package: lighttpd > Version: 1.4.69-1 > > Since our upgrade to Debian 12, lighttpd now uses insecure > Diffie-Hellman parameters > c90fdaa22168c234c4c6628b80dc1cd129024e088a67cc74020bbea63 > b139b22514a08798e3404ddef9519b3cd3a431b302b0a6df25f14374fe1356d6d5 > 1c245e485b576625e7ec6f44c42e9a637ed6b0bff5cb6f406b7edee386bfb5a899f > a5ae9f24117c4b1fe649286651ece45b3dc2007cb8a163bf0598da48361c55d39 > a69163fa8fd24cf5f83655d23dca3ad961c62f356208552bb9ed529077096966d6 > 70c354e4abc9804f1746c08ca18217c32905e462e36ce3be39e772c180e86039b > 2783a2ec07a28fb5c55df06f4c52c9de2bcbf6955817183995497cea956ae515d2 > 261898fa051015728e5a8aaac42dad33170d04507a33a85521abdf1cba64ecfb8 > 50458dbef0a8aea71575d060c7db3970f85a6e1e4c7abf5ae8cdb0933d71e8c94 > e04a25619dcee3d2261ad2ee6bf12ffa06d98a0864d87602733ec86a64521f2b18 > 177b200cbbe117577a615d6c770988c0bad946e208e24fa074e5ab3143db5bfce > 0fd108e4b82d120a92108011a723c12a787e6d788719a10bdba5b2699c327186 > af4e23c1a946834b6150bda2583e9ca2ad44ce8dbbbc2db04de8ef92e8efc141fb > ecaa6287c59474e6bc05d99b2964fa090c3a2233ba186515be7ed1f612970cee2 > d7afb81bdd762170481cd0069127d5b05aa993b4ea988d8fddc186ffb7dc90a6c0 > 8f4df435c934063199 What are you sharing? What command did you use to obtain this info? Please clarify why you think this is insecure. This does not look like lighttpd mod_openssl default DH parameters used since lighttpd 1.4.56. Since lighttpd 1.4.56, lighttpd mod_openssl configures default DH parameters to use RFC 7919 FFDHE2048 2048-bit group https://git.lighttpd.net/lighttpd/lighttpd1.4/commit/10c65e88f773d361db48e0135e1f4be3a932bf83 RFC 7919: https://datatracker.ietf.org/doc/html/rfc7919#appendix-A.1 Nowadays, FFDHE3072 is preferred, and a future version of lighttpd may change lighttpd mod_openssl to use FFDHE3072 by default in the future. Please note: if using GnuTLS (with lighttpd mod_gnutls) or using mbedTLS (with lighttpd mod_mbedtls), the Diffie-Hellman group is chosen to be secure according to RFC7919 DH parameter negotiation, and there is no default set by lighttpd. > And this despite having pointed ssl.dh-file to a self generated dh param > file, as described in https://weakdh.org/sysadmin.html That page is out-dated, at least for lighttpd. Since lighttpd 1.4.68, if you are using ssl.cipher-list specified in https://weakdh.org/sysadmin.html, then you are WEAKENING the cipher list now used by default since lighttpd 1.4.68. https://redmine.lighttpd.net/projects/lighttpd/wiki/release-1_4_68 > In Debian 11, an identical configuration was using our locally generated > secure dh parameters. Since lighttpd 1.4.65 (released Jun 2022), lighttpd has been announcing the future scheduled removal of ssl.dh-file. https://redmine.lighttpd.net/projects/lighttpd/wiki/release-1_4_65 https://redmine.lighttpd.net/projects/lighttpd/wiki/release-1_4_66 https://redmine.lighttpd.net/projects/lighttpd/wiki/release-1_4_67 The removal of ssl.dh-file occurred in lighttpd 1.4.68 (Jan 2023) https://redmine.lighttpd.net/projects/lighttpd/wiki/release-1_4_68 As linked in the lighttpd release notes: See https://wiki.lighttpd.net/Docs_SSL for replacements with `ssl.openssl.ssl-conf-cmd`, but prefer lighttpd defaults instead. Since lighttpd 1.4.68, use ssl.openssl.ssl-conf-cmd "DHParameters" to specify your own DH parameters file, as ssl.dh-file has been removed. If you have custom DH parameters, then please review RFC7919 and modern security papers to make sure what you think is secure is still considered secure by experts, as the use of parameters derived from "safe" primes is strongly recommended. It is my understanding that FFDHE3072 is the current recommendation if you are going to set explicit DH parameters. Cheers, Glenn
Bug#979308: This Bug is already fixed in Ubuntu
Ubuntu fixed this bug with jq (1.6-2.1ubuntu1) hirsute; urgency=medium [ Alex Murray ] * Fix fromdate when local time is during daylight savings (LP: #1910162) - d/p/fix-ftbfs-when-localtime-is-dst.patch: Backport upstream patch which ensures fromdate uses the correct time during daylight savings -- Christian Ehrhardt Tue, 05 Jan 2021 08:03:50 +0100
Bug#1023697: can wolfssl bug be closed?
Can this be closed? Are there any action items remaining for this bug? I am still getting messages that packages depending on wolfssl are "marked for autoremoval from testing on 2023-01-27" Thank you. Glenn
Bug#1034586: always reports inactive/expired certificate on armhf
Marco, please review my previous messages and try to help provide additional information. Thank you. Glenn
Bug#1040525: Lighttpd disregards ssl.dh-file setting
Repeating: lighttpd TLS configuration recommendations supercede the issue reported here. (https://wiki.lighttpd.net/Docs_SSL) > I now removed that cipher list (falling back to the default), and this > disabled the 2 remaining ciphers (DHE-RSA-AES256-GCM-SHA384 and > DHE-RSA-AES128-GCM-SHA256) that used Diffie Hellman :-) As you noticed, using the lighttpd TLS configuration recommendations does not include the ciphers using the finite field Diffie-Hellman parameters which caused Nexpose to generate warnings. --- Regarding the DH parameters used by default by lighttpd when finite field Diffie-Hellman parameters are used: > > Please clarify why you think this is insecure. > I trust Nexpose on this one. The theory goes that any "standard" > parameter is insecure, as a would be attacker would only need to "crack" > it once, and then be able to use it against a huge number of sites. I trust the published RFCs by experts more than I trust Nexpose. > I'm not really sure that it is a good idea to rely on *any* standard > Diffie-Hellman parameters :-( I'm not familiar with your expertise in this security area. What are your credentials that would give weight to your opinion? On the contrary: While there is the theoretical possibility of the well-known standard parameters being cracked, there are different potential pitfalls for generating custom parameters and then not cryptographically analyzing those custom parameters for weaknesses. It does not appear that you are performing that analysis on your custom parameters, and so my recommendation is to use the standard parameters which have been analyzed by experts for weaknesses. That does not guarantee safety, but does add more confidence to safety of the standard parameters when compared to custom parameters lacking expert analysis for weaknesses. As you have outsourced your security analysis to Nexpose, I recommend you follow up with Nexpose for more detailed guidance. I suggest that removing those ciphers is best practices at this point, unless you must support older clients which do not support more modern ciphers. If you still trust Nexpose more than other experts, I urge you to reconsider. Do you think Nexpose knows better than the OpenSSL developers? `man SSL_CTX_set_dh_auto` ``` Typically applications should use well know DH parameters that have built-in support in OpenSSL. The macros SSL_CTX_set_dh_auto() and SSL_set_dh_auto() configure OpenSSL to use the default built-in DH parameters for the SSL_CTX and SSL objects respectively. Passing a value of 1 in the onoff parameter switches the feature on, and passing a value of 0 switches it off. The default setting is off. If "auto" DH parameters are switched on then the parameters will be selected to be consistent with the size of the key associated with the server's certificate. If there is no certificate (e.g. for PSK ciphersuites), then it it will be consistent with the size of the negotiated symmetric cipher key. Applications may supply their own DH parameters instead of using the built-in values. This approach is discouraged and applications should in preference use the built-in parameter support described above. ``` Note: other TLS libraries such as GnuTLS use the expert-recommended standard parameters and no longer provide an option to set custom DH parameters. ``` Prior to GnuTLS 3.6.0 for the ephemeral or anonymous Diffie-Hellman (DH) TLS ciphersuites the application was required to generate or provide DH parameters. That is no longer necessary as GnuTLS utilizes DH parameters and negotiation from [RFC7919]. ``` --- Issue resolution: Since lighttpd 1.4.60, lighttpd switches on SSL_CTX_set_dh_auto() in lighttpd mod_openssl, and this causes openssl to ignore "DHParameters" even when explicitly set. This will be fixed in lighttpd 1.4.72. In lighttpd 1.4.72, if you explicitly set "DHParameters", lighttpd will switch off SSL_CTX_set_dh_auto() so that openssl will honor the user-supplied parameters. Even so, the expert recommendation is to allow openssl 3.0.0 and later to select the DH parameters (which lighttpd does by enabling SSL_CTX_set_dh_auto()).
Bug#1055131: RFS: lighttpd/1.4.73-1 -- light, fast, functional web server
Package: sponsorship-requests Severity: normal X-Debbugs-Cc: gs-bugs.debian@gluelogic.com Dear mentors, I am looking for a DD sponsor for my package "lighttpd": https://salsa.debian.org/debian/lighttpd/ I am an upstream lighttpd developer and have participated in maintaining lighttpd on Debian for a number of years. I am listed as an uploader on https://tracker.debian.org/pkg/lighttpd lighttpd-1.4.73-1 passes autopkgtests and expected CI tests, and is tagged. (This is a non-DD maintainer upload.) * Package name : lighttpd Version : 1.4.73-1 Upstream contact : team+light...@tracker.debian.org * URL : https://lighttpd.net/ * License : BSD-3-Clause * Vcs : https://git.lighttpd.net/lighttpd/lighttpd1.4 Important changes in lighttpd 1.4.73: * HTTP/2 detect and log rapid reset attack While lighttpd is not affected by HTTP/2 rapid reset attacks any more than by other DoS attacks, changes have been made to lighttpd to detect and log when a rapid reset attack occurs, and to close the HTTP/2 connection. Log watchers might subsequently use the trace to block IPs. The goal is to make lightpd 1.4.73 available in unstable, testing, and then backports (or sloppy-backports) to maintained Debian versions. Please advise next steps. Thank you. Glenn P.S. The version of lighttpd in Debian Experimental is 1.4.71-1+exp1 and can be retired.
Bug#1035926: lighttpd conf-enabled files cannot override IPV6 port number
On Thu, May 11, 2023 at 11:49:21AM +0200, Michael Moore wrote: ... > Issue and suggested fix: > === > In lighttpd.conf the includes for conf-enabled/*.conf happens after passing > server.port to the use-ipv6.pl script. Re-ordering these lines so that the > conf files are included first allows the server.port value to be > overridden. > > include_shell "/usr/share/lighttpd/use-ipv6.pl " + server.port > include_shell "/usr/share/lighttpd/create-mime.conf.pl" > include "/etc/lighttpd/conf-enabled/*.conf" Thank you for the thorough description. Yes, I agree with your suggestion. use-ipv6.pl is simple and its output can be placed anywhere in lighttpd.conf. Therefore, it should be safe to move to follow conf-enabled/*.conf I'll mark this fixed once the change is included in a release. Cheers, Glenn
Bug#1034586: always reports inactive/expired certificate on armhf
Macro, please review my previous messages and try to help provide additional information. Thank you. Glenn
Bug#1037099: RFS: lighttpd/1.4.71-1 -- light, fast, functional web server
Package: sponsorship-requests Severity: normal X-Debbugs-Cc: gs-bugs.debian@gluelogic.com Dear mentors, I am looking for a DD sponsor for my package "lighttpd": https://salsa.debian.org/debian/lighttpd/ I am an upstream lighttpd developer and have participated in maintaining lighttpd on Debian for a number of years. I am listed as an uploader on https://tracker.debian.org/pkg/lighttpd lighttpd-1.4.71-1 passes autopkgtests and expected CI tests, and is tagged. (This is a non-DD maintainer upload.) * Package name : lighttpd Version : 1.4.71-1 Upstream contact : team+light...@tracker.debian.org * URL : https://lighttpd.net/ * License : BSD-3-Clause * Vcs : https://git.lighttpd.net/lighttpd/lighttpd1.4 Similar to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036020 for lighttpd 1.4.70, this currently targets experimental, though I would like to get this into testing and into Bookworm in due time. Please advise. Thank you. Glenn
Bug#592834: grub-efi-amd64: File descriptor leaked on lvs invocation
Hey there, got this warning, dunno why, never read this before. Here's what I did before I got this warning. Be aware that I use parrot 4.6, which is based on debian but is a rolling distribution. The not upgraded (helt back) packages are some nvidia packages, not needed on my system (no nvidia card installed). They has nothing to do with grub. Maybe this helps you to recreate this issue. grub-efi-amd64 2.04-1parrot1 ┌─[anonymous@parrot]─[~] └──╼$ apt search grub | grep installed WARNING: apt does not have a stable CLI interface. Use with caution in scripts. grub-common/rolling,now 2.04-1parrot1 amd64 [installed] grub-efi-amd64/rolling,now 2.04-1parrot1 amd64 [installed] grub-efi-amd64-bin/rolling,now 2.04-1parrot1 amd64 [installed,automatic] grub-imageboot/rolling,rolling,now 0.6 all [installed] grub2-common/rolling,now 2.04-1parrot1 amd64 [installed,automatic] hashcat/rolling,now 5.1.0+ds1-1 amd64 [installed,automatic] ┌─[anonymous@parrot]─[~] └──╼$ sudo apt install grub-imageboot [sudo] password for anonymous: Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: syslinux-common The following NEW packages will be installed: grub-imageboot syslinux-common 0 upgraded, 2 newly installed, 0 to remove and 16 not upgraded. Need to get 1,242 kB of archives. After this operation, 3,619 kB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 https://ftp.halifax.rwth-aachen.de/parrotsec rolling/main amd64 syslinux-common all 3:6.04~git20190206.bf6db5b4+dfsg1-1 [1,237 kB] Get:2 https://ftp.halifax.rwth-aachen.de/parrotsec rolling/main amd64 grub-imageboot all 0.6 [4,354 B] Fetched 1,242 kB in 2s (710 kB/s) Selecting previously unselected package syslinux-common. (Reading database ... 333752 files and directories currently installed.) Preparing to unpack .../syslinux-common_3%3a6.04~git20190206.bf6db5b4+dfsg1-1_all.deb ... Unpacking syslinux-common (3:6.04~git20190206.bf6db5b4+dfsg1-1) ... Selecting previously unselected package grub-imageboot. Preparing to unpack .../grub-imageboot_0.6_all.deb ... Unpacking grub-imageboot (0.6) ... Setting up syslinux-common (3:6.04~git20190206.bf6db5b4+dfsg1-1) ... Setting up grub-imageboot (0.6) ... Copy syslinux memdisk to /boot/memdisk Scanning application launchers Updating active launchers Done ┌─[anonymous@parrot]─[~] └──╼$ sudo apt purge memtest86+ Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: memtest86+* 0 upgraded, 0 newly installed, 1 to remove and 16 not upgraded. After this operation, 2,449 kB disk space will be freed. Do you want to continue? [Y/n] (Reading database ... 333972 files and directories currently installed.) Removing memtest86+ (5.01-3+b1) ... Generating grub configuration file ... Found background image: /usr/share/images/desktop-base/desktop-grub.png Found linux image: /boot/vmlinuz-5.1.0-parrot1-3t-amd64 Found initrd image: /boot/initrd.img-5.1.0-parrot1-3t-amd64 Found linux image: /boot/vmlinuz-4.19.37-6parrot2-amd64 Found initrd image: /boot/initrd.img-4.19.37-6parrot2-amd64 Adding boot menu entry for EFI firmware configuration Found memdisk: /memdisk Imagepath /boot/images not found done (Reading database ... 333955 files and directories currently installed.) Purging configuration files for memtest86+ (5.01-3+b1) ... Generating grub configuration file ... Found background image: /usr/share/images/desktop-base/desktop-grub.png Found linux image: /boot/vmlinuz-5.1.0-parrot1-3t-amd64 Found initrd image: /boot/initrd.img-5.1.0-parrot1-3t-amd64 Found linux image: /boot/vmlinuz-4.19.37-6parrot2-amd64 Found initrd image: /boot/initrd.img-4.19.37-6parrot2-amd64 Adding boot menu entry for EFI firmware configuration Found memdisk: /memdisk Imagepath /boot/images not found done Generating grub configuration file ... Found background image: /usr/share/images/desktop-base/desktop-grub.png Found linux image: /boot/vmlinuz-5.1.0-parrot1-3t-amd64 Found initrd image: /boot/initrd.img-5.1.0-parrot1-3t-amd64 Found linux image: /boot/vmlinuz-4.19.37-6parrot2-amd64 Found initrd image: /boot/initrd.img-4.19.37-6parrot2-amd64 Adding boot menu entry for EFI firmware configuration Found memdisk: /memdisk Imagepath /boot/images not found done Scanning application launchers Updating active launchers Done ┌─[✗]─[anonymous@parrot]─[~] └──╼$ sudo apt install memtest86+ Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: hwtools memtester kernel-patch-badram memtest86 grub-pc | grub-legacy The following NEW packages will be installed: memtest86+ 0 upgraded, 1 newly installed, 0 to remove and 16 not upgraded. Need to get 78.1 kB of archives. After this operation, 2,449 kB of additional disk space will be used. Get:1 https://mirror.yandex.ru/mirrors/parrot rolling/main amd64 memtest86+ amd64 5.01-3+b1 [78.1 kB]
Bug#1064572: RFS: lighttpd/1.4.74-1 -- light, fast, functional web server
Package: sponsorship-requests Severity: normal X-Debbugs-Cc: gs-bugs.debian@gluelogic.com Dear mentors, I am looking for a DD sponsor for my package "lighttpd": https://salsa.debian.org/debian/lighttpd/ I am an upstream lighttpd developer and have participated in maintaining lighttpd on Debian for a number of years. I am listed as an uploader on https://tracker.debian.org/pkg/lighttpd lighttpd-1.4.74-1 passes autopkgtests and expected CI tests, and is tagged. (This is a non-DD maintainer upload.) * Package name : lighttpd Version : 1.4.74-1 Upstream contact : team+light...@tracker.debian.org * URL : https://lighttpd.net/ * License : BSD-3-Clause * Vcs : https://git.lighttpd.net/lighttpd/lighttpd1.4 Thank you. Glenn
Bug#1089215: incron: Incron crashes with segfault when creating or moving a directory with nfs-client
Package: incron Version: incron Severity: normal Dear Maintainer, I run a server with NFS-exports. And i want to run some actions when files and dirs are changing in these exports. For better explanation, its the filespace for a nextcloud i want to export also as nfs, because it's much faster on the clients than the webdav-export. But handling files and dirs in the filesystem directly causes nextcloud not to recognize this changes. So i want to run a files-scan only on changed files and directories periodically for nextcloud. When i create a new directory, incron crashes on every IN_CREATE,IN_ISDIR event. ``` Dez 07 08:45:33 nas incrond[2309706]: PATH (/exports/nextcloud-data/username/files/temp) FILE (subdir10) EVENT (IN_CREATE,IN_ISDIR) Dez 07 08:45:35 nas systemd[1]: incron.service: Main process exited, code=killed, status=11/SEGV Dez 07 08:45:35 nas systemd[1]: incron.service: Failed with result 'signal'. ``` When i move a directory directly on the nfs-server, i works. ``` Dez 07 08:47:22 nas incrond[2320081]: PATH (/exports/nextcloud-data/username/files/temp) FILE (subdir12) EVENT (IN_MOVED_FROM,IN_ISDIR) Dez 07 08:47:22 nas incrond[2320081]: (root) CMD ( /usr/local/bin/nc-incron-filehandle IN_MOVED_FROM,IN_ISDIR "/exports/nextcloud-data/username/files/temp/subdir12") Dez 07 08:47:22 nas incrond[2320081]: PATH (/exports/nextcloud-data/username/files/temp/subdir11) FILE (subdir12) EVENT (IN_MOVED_TO,IN_ISDIR) Dez 07 08:47:22 nas incrond[2320081]: (root) CMD ( /usr/local/bin/nc-incron-filehandle IN_MOVED_TO,IN_ISDIR "/exports/nextcloud-data/username/files/temp/subdir11/subdir12") ``` But when i move the dir via nfs-client, incron crashes ``` Dez 07 08:48:40 nas incrond[2320081]: PATH (/exports/nextcloud-data/username/files/temp) FILE (subdir11) EVENT (IN_MOVED_FROM,IN_ISDIR) Dez 07 08:48:40 nas incrond[2320081]: (root) CMD ( /usr/local/bin/nc-incron-filehandle IN_MOVED_FROM,IN_ISDIR "/exports/nextcloud-data/username/files/temp/subdir11") Dez 07 08:48:40 nas incrond[2320081]: PATH (/exports/nextcloud-data/username/files/temp/subdir10) FILE (subdir11) EVENT (IN_MOVED_TO,IN_ISDIR) Dez 07 08:48:41 nas systemd[1]: incron.service: Main process exited, code=killed, status=11/SEGV Dez 07 08:48:41 nas systemd[1]: incron.service: Failed with result 'signal'. ``` From dmesg when incron crashes: ``` [1228748.744632] incrond[1994543]: segfault at 5918e7a57000 ip 73dbcdec160a sp 7fff4f3c7838 error 4 in libc.so.6[73dbcde45000+155000] likely on CPU 1 (core 1, socket 0) [1228748.744666] Code: d9 66 0f d7 c3 48 83 c7 40 85 c0 0f 85 2f 01 00 00 48 89 f9 48 83 e7 c0 83 e1 3f 48 01 ca 66 90 48 83 ea 40 0f 86 86 00 00 00 <66> 0f 6f 07 66 0f 6f 57 10 66 0f 6f 5f 20 66 0f 6f 67 30 66 0f 74 [1228924.757155] incrond[1994841]: segfault at 4d ip 7f937aac14a4 sp 7ffc1e2ec918 error 4 in libc.so.6[7f937aa45000+155000] likely on CPU 2 (core 2, socket 0) [1228924.757212] Code: 5d 41 5c 41 5d c3 66 0f 6e ce 89 f9 66 0f 60 c9 48 85 d2 0f 84 0d 03 00 00 66 0f 60 c9 83 e1 3f 66 0f 70 c9 00 83 f9 30 77 3c 0f 6f 07 66 0f 74 c1 66 0f d7 c0 85 c0 0f 85 a8 02 00 00 48 83 [1229202.557510] traps: incrond[1996192] general protection fault ip:7e99e4cc14a4 sp:7ffe7c454d48 error:0 in libc.so.6[7e99e4c45000+155000] [1229712.176636] incrond[1998227]: segfault at 5cf9e8936000 ip 714b478c160a sp 7ffcef21ce98 error 4 in libc.so.6[714b47845000+155000] likely on CPU 3 (core 3, socket 0) [1229712.176671] Code: d9 66 0f d7 c3 48 83 c7 40 85 c0 0f 85 2f 01 00 00 48 89 f9 48 83 e7 c0 83 e1 3f 48 01 ca 66 90 48 83 ea 40 0f 86 86 00 00 00 <66> 0f 6f 07 66 0f 6f 57 10 66 0f 6f 5f 20 66 0f 6f 67 30 66 0f 74 [1230822.107785] incrond[2002094]: segfault at 51 ip 7e1bbdcc14a4 sp 7ffdbab94b58 error 4 in libc.so.6[7e1bbdc45000+155000] likely on CPU 0 (core 0, socket 0) [1230822.107832] Code: 5d 41 5c 41 5d c3 66 0f 6e ce 89 f9 66 0f 60 c9 48 85 d2 0f 84 0d 03 00 00 66 0f 60 c9 83 e1 3f 66 0f 70 c9 00 83 f9 30 77 3c 0f 6f 07 66 0f 74 c1 66 0f d7 c0 85 c0 0f 85 a8 02 00 00 48 83 [1230897.133791] traps: incrond[2010468] general protection fault ip:7fcc6fec14a4 sp:7fff7299f518 error:0 in libc.so.6[7fcc6fe45000+155000] [1230924.816670] incrond[2011036]: segfault at 61e77844d000 ip 73e0948c160a sp 7ffd1be19198 error 4 in libc.so.6[73e094845000+155000] likely on CPU 0 (core 0, socket 0) [1230924.816706] Code: d9 66 0f d7 c3 48 83 c7 40 85 c0 0f 85 2f 01 00 00 48 89 f9 48 83 e7 c0 83 e1 3f 48 01 ca 66 90 48 83 ea 40 0f 86 86 00 00 00 <66> 0f 6f 07 66 0f 6f 57 10 66 0f 6f 5f 20 66 0f 6f 67 30 66 0f 74 [123.008226] incrond[2011260]: segfault at 0 ip 7707632c14a4 sp 7ffd8ba638a8 error 4 in libc.so.6[770763245000+155000] likely on CPU 3 (core 3, socket 0) [123.008268] Code: 5d 41 5c 41 5d c3 66 0f 6e ce 89 f9 66 0f 60 c9 48 85 d2 0f 84 0d 03 00 00 66 0f 60 c9 83 e1 3f 66 0f 70 c9 00 83 f9 30 77 3c 0f 6f 07 66 0f 74 c1 66 0f d7 c0 85 c0 0f 85 a8 02 00 00 48 83 [1231117
Bug#1059773: After disabling internet connection, I could start the calculator again
It seems to be a issue with the currency exchange rate update with HTTP: ~$ gnome-calculator ** (gnome-calculator:15095): WARNING **: 17:02:15.089: currency-provider.vala:161: Couldn't download IMF currency rate file: HTTP/2 Error: INTERNAL_ERROR (gnome-calculator:15095): libsoup-WARNING **: 17:02:15.089: (../libsoup/soup-session.c:334):soup_session_dispose: runtime check failed: (soup_connection_manager_get_num_conns (priv->conn_manager) == 0) (gnome-calculator:15095): libsoup-WARNING **: 17:02:15.089: (../libsoup/soup-connection-manager.c:78):soup_host_free: runtime check failed: (host->conns == NULL) Killed *After disabling internet connection, I could start the calculator again.* After disabling the weekly/daily currency updates in the settings, the program starts without freezing also with enabled internet connection. Upstream bug report: https://gitlab.gnome.org/GNOME/gnome-calculator/-/issues/359
