Bug#606145: leafpad: Saving in UTF16 encoding truncates file
Package: leafpad Version: 0.8.17-3 Severity: grave Justification: causes non-serious data loss When leafpad saves file in UTF16 encodings like UTF16LE, the resulting file is truncated after first NUL byte. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686-bigmem (SMP w/1 CPU core) Locale: lang=ru_ru.ut...@old, lc_ctype=ru_ru.ut...@old (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages leafpad depends on: ii libatk1.0-0 1.30.0-1The ATK accessibility toolkit ii libc62.11.2-7Embedded GNU C Library: Shared lib ii libcairo21.8.10-6The Cairo 2D vector graphics libra ii libfontconfig1 2.8.0-2.1 generic font configuration library ii libfreetype6 2.4.2-2 FreeType 2 font engine, shared lib ii libglib2.0-0 2.26-0ubuntu1ppa0lucid0 The GLib library of C routines ii libgtk2.0-0 2.20.1-2The GTK+ graphical user interface ii libpango1.0-01.28.3-1Layout and rendering of internatio leafpad recommends no packages. Versions of packages leafpad suggests: pn evince-gtk (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#1026827: xrdp: initially xrdp worked ok, but later it broke, and the problem was /etc/xrdp/startwm.sh that changed
Package: xrdp
Version: 0.9.12-1.1
Severity: critical
Justification: breaks the whole system
X-Debbugs-Cc: alexb...@gmail.com
Dear Maintainer,
* What led up to the situation?
the remmina-rdp and android ms-rdesktop initially worked ok,
but after this change began to show a black screen and close it.
* What exactly did you do (or not do) that was effective (or
ineffective)?
upstream discussion led me to check /etc/xrdp/startwm.sh that not only seemed
broken,
but the version that seemed ok (and later worked indeed) was renamed to
/etc/xrdp/startwm.sh0.
the broken version was also in a file /etc/xrdp/startwm.sh1.
* What was the outcome of this action?
xrdp was initially working until the day before, when it showed a black window
and disconnected.
* What outcome did you expect instead?
after i suspected this file was broken, and replaced it with
/etc/xrdp/startwm.sh0 that was by it's side.
-- System Information:
Debian Release: 11.6
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-20-cloud-amd64 (SMP w/6 CPU threads)
Locale: LANG=C.UTF-8, 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)
LSM: AppArmor: enabled
Versions of packages xrdp depends on:
ii adduser 3.118
ii init-system-helpers 1.60
ii libc62.31-13+deb11u5
ii libfuse2 2.9.9-5
ii libjpeg62-turbo 1:2.0.6-4
ii libopus0 1.3.1-0.1
ii libpam0g 1.4.0-9+deb11u1
ii libssl1.11.1.1n-0+deb11u3
ii libx11-6 2:1.7.2-1
ii libxfixes3 1:5.0.3-2
ii libxrandr2 2:1.5.1-1
ii lsb-base 11.1.0
ii ssl-cert 1.1.0+nmu1
Versions of packages xrdp recommends:
ii fuse3 [fuse] 3.10.3-2
ii xorgxrdp 1:0.2.12-1
Versions of packages xrdp suggests:
pn guacamole
pn xrdp-pulseaudio-installer
Versions of packages xorgxrdp depends on:
ii libc6 2.31-13+deb11u5
ii libepoxy0 1.5.5-1
pn xorg-input-abi-24
ii xserver-xorg-core [xorg-video-abi-24] 2:1.20.11-1+deb11u4
Versions of packages xorgxrdp recommends:
ii xorg 1:7.7+22
Versions of packages xrdp is related to:
pn vnc-server
ii xserver-xorg-legacy 2:1.20.11-1+deb11u4
-- Configuration Files:
/etc/xrdp/startwm.sh changed:
if [ -r /etc/default/locale ]; then
. /etc/default/locale
export LANG LANGUAGE
fi
startxfce4
/etc/xrdp/xrdp.ini changed:
[Globals]
; xrdp.ini file version number
ini_version=1
; fork a new process for each incoming connection
fork=true
; ports to listen on, number alone means listen on all interfaces
; 0.0.0.0 or :: if ipv6 is configured
; space between multiple occurrences
;
; Examples:
; port=3389
; port=unix://./tmp/xrdp.socket
; port=tcp://.:3389 127.0.0.1:3389
; port=tcp://:3389*:3389
; port=tcp://:3389 192.168.1.1:3389
; port=tcp6://.:3389 ::1:3389
; port=tcp6://:3389 *:3389
; port=tcp6://{}:3389 {FC00:0:0:0:0:0:0:1}:3389
; port=vsock://:
port=3389
;port=tcp://.:3389
; 'port' above should be connected to with vsock instead of tcp
; use this only with number alone in port above
; prefer use vsock://: above
use_vsock=false
; regulate if the listening socket use socket option tcp_nodelay
; no buffering will be performed in the TCP stack
tcp_nodelay=true
; regulate if the listening socket use socket option keepalive
; if the network connection disappear without close messages the connection
will be closed
tcp_keepalive=true
; set tcp send/recv buffer (for experts)
; security layer can be 'tls', 'rdp' or 'negotiate'
; for client compatible layer
security_layer=negotiate
; minimum security level allowed for client for classic RDP encryption
; use tls_ciphers to configure TLS encryption
; can be 'none', 'low', 'medium', 'high', 'fips'
crypt_level=high
; X.509 certificate and private key
; openssl req -x509 -newkey rsa:2048 -nodes -keyout key.pem -out cert.pem -days
365
; note this needs the user xrdp to be a member of the ssl-cert group, do with
e.g.
;$ sudo adduser xrdp ssl-cert
certificate=
key_file=
; set SSL protocols
; can be comma separated list of 'SSLv3', 'TLSv1', 'TLSv1.1', 'TLSv1.2',
'TLSv1.3'
ssl_protocols=TLSv1.2, TLSv1.3
;ssl_protocols=TLSv1, TLSv1.1, TLSv1.2, TLSv1.3
; set TLS cipher suites
; Section name to use for automatic login if the client sends username
; and password. If empty, the domain name sent by the client is used.
; If empty and no domain name is given, the first suitable section in
; this file will be used.
autorun=
allow_channels=true
allow_multimon=true
bitmap_cache=true
bitmap_compression=true
bulk_compression=true
max_bpp=32
new_cursors=true
; fastpath - can be '
Bug#943468: php-fpm: CVE-2019-11043: Vulnerability in PHP-FPM Could Lead to Remote Code Execution on nginx
Hi, PHP published a fixed version (7.3.11) before this CVE went public. Can you please package and upload that version? If that is not possible, can you please at least explain in the bug report why fixing this (pretty serious) bug is not possible at the moment? That might attract some assistance if needed. -- mvg, Alex Hermann
Bug#903932: udisks2 breaks sysvinit-core
Package: udisks2 Version: 2.7.6-3 Severity: serious Justification: - Dear Maintainer, udisks2 conflicts with sysvinit-core, which means i.e. that the plasma-desktop environment cannot be installed without replacing init with systemd, because some kde package is depending on udisks2. I believe the problem is in udisks2, as it depends on libpam-systemd which seems to break the things, while it probably should not be necceassy for udisk2, when init is used. with kind regards, Alex -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.16.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages udisks2 depends on: ii dbus 1.12.8-3 ii libacl12.2.52-3+b1 ii libatasmart4 0.19-5 ii libblockdev-fs22.16-2 ii libblockdev-loop2 2.16-2 ii libblockdev-part2 2.16-2 ii libblockdev-swap2 2.16-2 ii libblockdev-utils2 2.16-2 ii libblockdev2 2.16-2 ii libc6 2.27-3 ii libglib2.0-0 2.56.1-2 ii libgudev-1.0-0 232-2 ii libmount1 2.32-0.1 ii libpam-systemd 239-5 ii libpolkit-agent-1-00.105-21 ii libpolkit-gobject-1-0 0.105-21 ii libsystemd0239-5 ii libudisks2-0 2.7.6-3 ii parted 3.2-21+b1 ii udev 239-5 Versions of packages udisks2 recommends: ii dosfstools 4.1-2 ii e2fsprogs1.44.3-1 ii eject2.1.5+deb1+cvs20081104-13.2 ii exfat-utils 1.2.8-1 ii libblockdev-crypto2 2.16-2 ii ntfs-3g 1:2017.3.23-2 ii policykit-1 0.105-21 Versions of packages udisks2 suggests: ii btrfs-progs 4.16.1-2 pn f2fs-tools pn libblockdev-mdraid2 pn mdadm pn nilfs-tools pn reiserfsprogs pn udftools pn udisks2-btrfs pn udisks2-lvm2 ii xfsprogs 4.15.1-1 -- no debconf information
Bug#1074250: ifupdown2 not working with python3.12
On Tue, 25 Jun 2024 03:05:39 -0400 Dave B wrote: > Package: ifupdown2 > Version: 3.0.0-1.1 > Severity: grave > Tags: ipv6 > Justification: renders package unusable > > Dear Maintainer, > >* What led up to the situation? The upgrade to python3.12 which replaced "readfp" with "read_file) Dear maintainer, Please let the package depend on a specific, tested, python version (3.11 for now) instead of the generic python3 package. Python is infamously known for breaking backward compatibility on every occasion they get. For a critical package like ifupdown2, this random breakage is not acceptable. Depending on a specific pyhton verion should alleviate this problem a little bit. -- mvg, Alex Hermann
Bug#535467: [PATCH] use getaddrinfo() instead of gethostbyname()
Hi, I'm a bit concerned about making the option -a not working anymore. Are you sure making -a not working doesn't brake any other programs?. Shouldn't we stick to the standard behavior with base programs like this one? On Mon, Aug 03, 2009 at 10:25:43PM +0200, Michael Stapelberg wrote: > Hi, > > I can confirm this behaviour. While one can work around it using > "options inet6" in /etc/resolv.conf, a better solution is converting hostname > to use getaddrinfo() instead of gethostbyname(). getaddrinfo() is the > preferred function to resolve addresses, see for example this entry from > Ulrich > Drepper: > > http://udrepper.livejournal.com/16116.html > > So, after applying the patch I attached, the new version of hostname correctly > handles my IPv6-only host: > > $ hostname > x200 > $ hostname -f > No address associated with name > $ hostname -i > 192.168.1.42 > $ ./hostname-patched > x200 > $ ./hostname-patched -f > x200.zekjur.net > $ ./hostname-patched -i > 2001:4d88:1008:4242:21f:16ff:fe06:3aab > > Note that using getaddrinfo() removes old cruft, that is, the aliases field > returned by gethostbyname(). Thus, hostname -a will not work anymore. I???ve > documented this in the manpage and left the option available for backwards > compatibility. > > Please apply the attached patch, > > Thanks and best regards, > Michael -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#593374: libncurses.so.5: cannot open shared object file: no such file or directory
Package: cfdisk-udeb Version: 2.17.2-3.1 Severity: grave Tags: d-i Justification: renders package unusable This warning message appears and inhibit me to use cfdisk. I used a debian- testing-amd64-CD-1 iso-file from 16.8.2010. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#578137: [CRASH] Uncaught exception AttributeError in Frontend/Gtk/ui.py:616
Package: update-manager-gnome
Version: 0.200.3-1
Severity: grave
File: /usr/share/pyshared/UpdateManager/Frontend/Gtk/ui.py
Tags: squeeze
Justification: renders package unusable
*** Please type your report below this line *** *** /tmp/update-manager-
bugM3qw6j The information below has been automatically generated. Please do not
remove this from your bug report. - Exception Type: - Exception Value: AttributeError("'GtkUI' object
has no attribute 'treeview_update'",) - Exception Origin:
<_MainThread(MainThread, started)> - Exception Traceback: File "/usr/bin
/update-manager", line 38, in app.main() File
"/usr/lib/pymodules/python2.5/UpdateManager/Application.py", line 421, in main
self._frontend.init_frontend() File
"/usr/lib/pymodules/python2.5/UpdateManager/Frontend/Gtk/__init__.py", line 70,
in init_frontend self._ui = GtkUI(self) File
"/usr/lib/pymodules/python2.5/UpdateManager/Frontend/Gtk/ui.py", line 616, in
__init__ self.update_list = UpdateListControl(self, self.treeview_update)
-- System Information: Debian Release: squeeze/sid APT prefers testing APT
policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux
2.6.32-3-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.UTF-8,
LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash
Versions of packages update-manager-gnome depends on: ii gconf2
2.28.0-1GNOME configuration database syste ii gksu
2.0.2-2+b1 graphical frontend to su ii python 2.5.4-9
An interactive high-level object-o ii python-dbus 0.83.1-1
simple interprocess messaging syst ii python-gconf 2.28.0-2
Python bindings for the GConf conf ii python-gobject 2.20.0-1+b1
Python bindings for the GObject li ii python-gtk2 2.16.0-2
Python bindings for the GTK+ widge ii python-support 1.0.7
automated rebuilding support for P ii python-vte 1:0.22.5-3
Python bindings for the VTE widget ii update-manager-core 0.200.3-1
APT update manager core functional update-manager-gnome recommends no
packages. Versions of packages update-manager-gnome suggests: pn software-
properties-gtk(no description available) ii update-notifier
0.70.7.debian-7 Daemon which notifies about packag
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#774461: Recent upgrade 'broke' sleep & hibernate in KDE Plasma Battery Monitor - now fixed
Hi I have just applied your file "linux-image-3.2.0-4-amd64_3.2.65-1+deb7u1~test_amd64.deb" and it has fixed the problem. Thank you! The advice to run this file came from the debian-u...@lists.debian.org group where the original request for help exists under the same Subject title as above (minus the " - now fixed"). There is some debugging info. there such as excerpts of the relevant sections of:- /var/log/apt/history.log /var/log/pm-suspend.log (pre- and post original [problematic] upgrade) I have included the relevant section of the now working /var/log/pm-suspend.log below for debugging, if needed - I hope this helps. Thanks and regards Alex Excerpt from /var/log/pm-suspend.log (post installation of file "linux-image-3.2.0-4-amd64_3.2.65-1+deb7u1~test_amd64.deb" upgrade - working) starts << Initial commandline parameters: Fri Jan 16 10:09:02 AEDT 2015: Running hooks for suspend. Running hook /usr/lib/pm-utils/sleep.d/00logging suspend suspend: Linux debacer 3.2.0-4-amd64 #1 SMP Debian 3.2.65-1+deb7u1~test x86_64 GNU/Linux Module Size Used by xt_limit 12638 8 xt_tcpudp 12570 7 ipt_LOG12605 8 ipt_MASQUERADE 12594 0 xt_DSCP12643 0 ipt_REJECT 12502 1 nf_conntrack_irc 12427 0 nf_conntrack_ftp 12605 0 xt_state 12503 6 iptable_nat12928 0 nf_nat 18242 2 iptable_nat,ipt_MASQUERADE nf_conntrack_ipv4 14078 9 nf_nat,iptable_nat nf_defrag_ipv4 12483 1 nf_conntrack_ipv4 nf_conntrack 52720 7 nf_conntrack_ipv4,nf_nat,iptable_nat,xt_state,nf_conntrack_ftp,nf_conntrack_irc,ipt_MASQUERADE iptable_mangle 12536 0 iptable_filter 12536 1 ip_tables 22042 3 iptable_filter,iptable_mangle,iptable_nat x_tables 19118 11 ip_tables,iptable_filter,iptable_mangle,iptable_nat,xt_state,ipt_REJECT,xt_DSCP,ipt_MASQUERADE,ipt_LOG,xt_tcpudp,xt_limit parport_pc 22364 0 ppdev 12763 0 lp 17149 0 parport31858 3 lp,ppdev,parport_pc bnep 17567 2 rfcomm 33700 0 bluetooth 119455 10 rfcomm,bnep pci_stub 12429 1 vboxpci19103 0 vboxnetadp 25443 0 binfmt_misc12957 1 vboxnetflt 23608 0 vboxdrv 190105 3 vboxnetflt,vboxnetadp,vboxpci uinput 17440 1 nfsd 216181 2 nfs 308353 0 nfs_acl12511 2 nfs,nfsd auth_rpcgss37143 2 nfs,nfsd fscache36739 1 nfs lockd 67306 2 nfs,nfsd sunrpc173730 6 lockd,auth_rpcgss,nfs_acl,nfs,nfsd ext4 350804 1 crc16 12343 2 ext4,bluetooth jbd2 62115 1 ext4 loop 22641 0 snd_hda_codec_hdmi 30824 1 snd_hda_codec_realtek 188851 1 arc4 12458 2 pl2303 17262 0 uvcvideo 57744 0 usbserial 32061 1 pl2303 videodev 70889 1 uvcvideo v4l2_compat_ioctl3216655 1 videodev media 18148 2 videodev,uvcvideo snd_hda_intel 26259 5 brcmsmac 473905 0 snd_hda_codec 78031 3 snd_hda_intel,snd_hda_codec_realtek,snd_hda_codec_hdmi joydev 17266 0 snd_hwdep 13186 1 snd_hda_codec snd_pcm_oss41081 0 cordic 12352 1 brcmsmac crc8 12426 1 brcmsmac snd_mixer_oss 17916 1 snd_pcm_oss brcmutil 12905 1 brcmsmac snd_pcm68083 4 snd_pcm_oss,snd_hda_codec,snd_hda_intel,snd_hda_codec_hdmi mac80211 192806 1 brcmsmac i915 378651 5 snd_page_alloc 13003 2 snd_pcm,snd_hda_intel coretemp 12898 0 cfg80211 137243 2 mac80211,brcmsmac snd_seq_midi 12848 0 snd_seq_midi_event 13316 1 snd_seq_midi snd_rawmidi23060 1 snd_seq_midi snd_seq45126 2 snd_seq_midi_event,snd_seq_midi snd_seq_device 13176 3 snd_seq,snd_rawmidi,snd_seq_midi snd_timer 22917 2 snd_seq,snd_pcm acer_wmi 26081 0 sparse_keymap 12760 1 acer_wmi iTCO_wdt 17081 0 acpi_cpufreq 12935 1 crc32c_intel 12747 0 ghash_clmulni_intel13130 0 wmi13243 1 acer_wmi psmouse69265 0 snd52893 22 snd_timer,snd_seq_device,snd_seq,snd_rawmidi,snd_pcm,snd_mixer_oss,snd_pcm_oss,snd_hwdep,snd_hda_codec,snd_hda_intel,snd_hda_codec_realtek,snd_hda_codec_hdmi rfkill 19012 5 acer_wmi,cfg80211,bluetooth iTCO_vendor_support12704 1 iTCO_wdt drm_kms_helper 31370 1 i915 video 17683
Bug#826966: libpythonqt-dev: Missing header PythonQtUtils.h
Package: libpythonqt-dev Version: 3.0-1 Severity: grave Justification: renders package unusable Dear Maintainer, /usr/include/PythonQt/PythonQt.h demands PythonQtUtils.h but this header, although present in the source package, is missing. Without this file it is impossible to compile anything against libPythonQt. A possible solution is to add src/PythonQtUtils.h in CMakeLists.txt:145 and rebuild the package. Best, a. -- System Information: Debian Release: 8.4 APT prefers stable APT policy: (1000, 'stable'), (900, 'stable'), (750, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.4.0-0.bpo.1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libpythonqt-dev depends on: ii libpythonqt3.0 3.0-1 libpythonqt-dev recommends no packages. libpythonqt-dev suggests no packages. -- no debconf information
Bug#754251: Version 304.123 is released
The previous comment contained a link to the wrong driver version. NVidia recently released a new legacy 304xx version, which should be compatible with xserver 1.16. https://devtalk.nvidia.com/default/topic/760649/unix-graphics-announcements-and-news/linux-solaris-and-freebsd-driver-304-123-legacy-for-geforce-6-and-7-series-/ -- Alex -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#613572:
On Wednesday 16 February 2011, Jonathan Thomas wrote: > Open up > the "/usr/lib/pymodules/python2.5/openshot/uploads/vimeo/convenience.py" > file, and just remove the entire "def upload()" method, which contains > this incompatible Python 2.6 code. I tried, but it makes no difference. Also tried: - rm /usr/lib/pymodules/python2.5/openshot/uploads/vimeo/convenience.pyc - dpkg-reconfigure -plow to trigger whatever the install process tried to do and failed at. Every attempt resulted in: OpenShot (version 1.3.0) Process no longer exists: 7452. Creating new pid lock file. --- Error: OpenShot has not been installed in the Python path. (Both the site-packages and /usr/share/openshot folders were checked) Use the following command to install OpenShot: $ sudo python setup.py install -- Alex. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#380312: azureus still not installable
Hello, I lost my azureus because dependencies on unstable :-( I have read bugreports and I saw that this is because libswt-gtk-3.2-java that now it is uploaded onto repositories, but this library requires another that's missing [EMAIL PROTECTED]:/home/z0mbie/downloads# apt-get install libswt-gtk-3.2-java Reading package lists... Done Building dependency tree... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. Since you only requested a single operation it is extremely likely that the package is simply not installable and a bug report against that package should be filed. The following information may help to resolve the situation: The following packages have unmet dependencies. libswt-gtk-3.2-java: Depends: libswt-gtk-3.2-jni (= 3.2-1) but it is not going to be installed E: Broken packages [EMAIL PROTECTED]:/home/z0mbie/downloads# While the complete dependencies will not be satisfied, azureus continue broken and will fail to install I am using debian / unstable and I have update/dist-upgaded a few minutes ago... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#334332: clamav: Broken package: fails to install due to unmet dependencies
Package: clamav Severity: grave Justification: renders package unusable apt-get install clamav Reading Package Lists... Done Building Dependency Tree... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. Since you only requested a single operation it is extremely likely that the package is simply not installable and a bug report against that package should be filed. The following information may help to resolve the situation: The following packages have unmet dependencies: clamav: Depends: libclamav1 (>= 0.87) but it is not going to be installed E: Broken packages -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.4.25-1-386 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#464514: wpasupplicant segfaults after successful authentication
Package: wpasupplicant
Version: 0.6.2+git20080202.gde6ccd7-1 0
Severity: critical
Using the configuration (no problems with older wpasupplicant)
network={
[...]
key_mgmt=IEEE8021X
eap=TTLS
phase2="auth=MSCHAPV2"
[...]
}
wpasupplicant dies with:
--
AP-TTLS: Phase 2 MSCHAPV2 authentication succeeded
CTRL-EVENT-EAP-SUCCESS EAP authentication completed successfully
Speicherzugriffsfehler
--
"-dd" shows a massive loop of
--
EAPOL: KEY_RX entering state KEY_RECEIVE
EAPOL: processKey
EAPOL: RX IEEE 802.1X ver=1 type=3 len=57 EAPOL-Key: type=1
key_length=13 key_index=0x2
--
after which wpasupplicant finally segfaults.
I downgraded to the version in testing.
Greetings,
Alex
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#440589: cupsys: Most browsers can't access web interface, but some do fine.
Package: cupsys Version: 1.3.0-3 Severity: grave Justification: renders package unusable When accessing http://localhost:631 cupsys via konqueror or iceweasel (or iceape), cups returns a "404 not found" error message. With links2 it seems to work fine, at least on the main page. A traffic capture with wireshark shows nothing out of ordinary, i.e. the GET / HTTP/1.1 and the Host: localhost:631 are present and identical on both requisitions. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.22-1-k7 (SMP w/1 CPU core) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages cupsys depends on: ii adduser 3.105add and remove users and groups ii cupsys-common 1.3.0-3 Common UNIX Printing System(tm) - ii debconf [debconf-2.0] 1.5.14 Debian configuration management sy ii gs-esp 8.15.3.dfsg.1-1 The Ghostscript PostScript interpr ii libavahi-compat-libdnss 0.6.21-1 Avahi Apple Bonjour compatibility ii libc6 2.6.1-1+b1 GNU C Library: Shared libraries ii libcomerr2 1.40.2-1 common error description library ii libcupsimage2 1.3.0-3 Common UNIX Printing System(tm) - ii libcupsys2 1.3.0-3 Common UNIX Printing System(tm) - ii libdbus-1-3 1.1.1-3 simple interprocess messaging syst ii libgnutls13 1.7.19-1 the GNU TLS library - runtime libr ii libkrb531.6.dfsg.1-6 MIT Kerberos runtime libraries ii libldap22.1.30.dfsg-13.5 OpenLDAP libraries ii libpam0g0.99.7.1-4 Pluggable Authentication Modules l ii libpaper1 1.1.22 library for handling paper charact ii libslp1 1.2.1-7 OpenSLP libraries ii lsb-base3.1-24 Linux Standard Base 3.1 init scrip ii perl-modules5.8.8-7 Core Perl modules ii poppler-utils [xpdf-uti 0.5.4-6.1PDF utilitites (based on libpopple ii procps 1:3.2.7-4/proc file system utilities ii ssl-cert1.0.14 Simple debconf wrapper for openssl ii zlib1g 1:1.2.3.3.dfsg-5 compression library - runtime Versions of packages cupsys recommends: ii cups-pdf 2.4.6-4PDF printer for CUPS ii cupsys-client 1.3.0-3Common UNIX Printing System(tm) - ii foomatic-filters 3.0.2-20061031-1.2 linuxprinting.org printer support pn smbclient (no description available) -- debconf information: * cupsys/raw-print: true * cupsys/backend: ipp, lpd, parallel, scsi, serial, socket, usb, snmp -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#441980: /usr/bin/apt-get: apt-get update segfaults at pkgCacheGenerator::NewFileDesc
Package: apt Version: 0.7.6 Severity: grave File: /usr/bin/apt-get Justification: renders package unusable If I run apt-get update with the attached sources.list, it segfaults. It's backtrace is: (gdb) bt #0 0xb7ec3375 in pkgCacheGenerator::NewFileDesc () from /usr/lib/libapt-pkg-libc6.6-6.so.4.4 #1 0xb7ec479f in pkgCacheGenerator::MergeList () from /usr/lib/libapt-pkg-libc6.6-6.so.4.4 #2 0xb7efee12 in debPackagesIndex::Merge () from /usr/lib/libapt-pkg-libc6.6-6.so.4.4 #3 0xb7ec539a in ?? () from /usr/lib/libapt-pkg-libc6.6-6.so.4.4 #4 0xb7ec7082 in pkgMakeStatusCache () from /usr/lib/libapt-pkg-libc6.6-6.so.4.4 #5 0xb7ebd48a in pkgCacheFile::BuildCaches () from /usr/lib/libapt-pkg-libc6.6-6.so.4.4 #6 0x08057980 in ?? () #7 0xb7e8b9cb in CommandLine::DispatchArg () from /usr/lib/libapt-pkg-libc6.6-6.so.4.4 #8 0x0804e96b in ?? () #9 0xb7c15050 in __libc_start_main () from /lib/i686/cmov/libc.so.6 #10 0x0804ce61 in ?? () I tried supressing many of the repositories and it worked. It's probably triggered by misparsing some erroneous data on one of them, but anyway, it's a bug demanding corretion. -- Package-specific info: -- apt-config dump -- APT ""; APT::Architecture "i386"; APT::Build-Essential ""; APT::Build-Essential:: "build-essential"; APT::Install-Recommends "0"; APT::Install-Suggests "0"; APT::Authentication ""; APT::Authentication::TrustCDROM "true"; APT::NeverAutoRemove ""; APT::NeverAutoRemove:: "^linux-image.*"; APT::NeverAutoRemove:: "^linux-restricted-modules.*"; APT::Acquire ""; APT::Acquire::Translation "environment"; Dir "/"; Dir::State "var/lib/apt/"; Dir::State::lists "lists/"; Dir::State::cdroms "cdroms.list"; Dir::State::userstatus "status.user"; Dir::State::status "/var/lib/dpkg/status"; Dir::Cache "var/cache/apt/"; Dir::Cache::archives "archives/"; Dir::Cache::srcpkgcache "srcpkgcache.bin"; Dir::Cache::pkgcache "pkgcache.bin"; Dir::Etc "etc/apt/"; Dir::Etc::sourcelist "sources.list"; Dir::Etc::sourceparts "sources.list.d"; Dir::Etc::vendorlist "vendors.list"; Dir::Etc::vendorparts "vendors.list.d"; Dir::Etc::main "apt.conf"; Dir::Etc::parts "apt.conf.d"; Dir::Etc::preferences "preferences"; Dir::Bin ""; Dir::Bin::methods "/usr/lib/apt/methods"; Dir::Bin::dpkg "/usr/bin/dpkg"; DPkg ""; DPkg::Pre-Install-Pkgs ""; DPkg::Pre-Install-Pkgs:: "/usr/bin/apt-listchanges --apt || test $? -ne 10"; DPkg::Pre-Install-Pkgs:: "/usr/sbin/dpkg-preconfigure --apt || true"; DPkg::Tools ""; DPkg::Tools::Options ""; DPkg::Tools::Options::/usr/bin/apt-listchanges ""; DPkg::Tools::Options::/usr/bin/apt-listchanges::Version "2"; -- (no /etc/apt/preferences present) -- -- /etc/apt/sources.list -- deb http://ftp.br.debian.org/debian/ unstable main contrib non-free deb-src http://ftp.br.debian.org/debian/ unstable main contrib non-free deb http://linorg.usp.br/debian-marillat/ unstable main deb-src http://linorg.usp.br/debian-marillat/ unstable main deb ftp://ftp.pucpr.br/debian unstable main contrib non-free deb-src ftp://ftp.pucpr.br/debian unstable main contrib non-free deb http://ftp.us.debian.org/debian/ unstable main contrib non-free deb-src http://ftp.us.debian.org/debian/ unstable main contrib non-free deb http://www.debian-multimedia.org unstable main deb-src http://www.debian-multimedia.org unstable main # gammu deb http://debian.cihar.com/ unstable main deb-src http://debian.cihar.com/ unstable main # freenx #deb http://sidux.com/debian/ unstable nx #deb-src http://sidux.com/debian/ unstable nx #skype deb http://download.skype.com/linux/repos/debian/ stable non-free #deb file:/var/cache/apt-build/repository apt-build main #deb-src http://ftp.br.debian.org/ unstable main contrib non-free deb http://ftp.br.debian.org/debian/ stable main contrib deb-src http://ftp.br.debian.org/debian/ stable main contrib deb http://debian.beryl-project.org/ etch main deb-src http://debian.beryl-project.org/ etch main #deb http://gulus.usherbrooke.ca/debian-unofficial/ unstable main non-free restricted -- System Information: Debian Release: lenny/sid Architecture: i386 (i686) Kernel: Linux 2.6.22 (SMP w/1 CPU core) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages apt depends on: ii debian-archive-keyring2007.07.31 GnuPG archive keys of the Debian a ii libc6 2.6.1-1+b1 GNU C Library: Shared libraries ii libgcc1 1:4.2.1-4 GCC support library ii libstdc++64.2.1-4The GNU Standard C++ Library v3 apt recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#502504: hplip: None of the applications will start
On Friday 17 October 2008, Riku Voipio wrote: > Sounds like somthing is wrong with your python installation. Well, i purged and reinstalled every package i could find that was even remotely related to python, and now it works. Thanks for the hint and sorry for the noise. Alex. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#502504: hplip: None of the applications will start
On Saturday 18 October 2008, Henrique de Moraes Holschuh wrote: > Can we close the bug? Yes. Alex. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#505096: ndiswrapper-source: system freezes shortly after loading module
Package: ndiswrapper-source Version: 1.53-1 Severity: critical Justification: breaks the whole system I'm using a TP-LINK WN3222 usb wireless dongle. After loading the module, everything works fine for a few miutes, then the whole system freezes and a 'hard reboot' is required. On a different machine running Lenny with same software, it works fine. I have the same issue for 2 machines running Etch - one freezes, the other is fine - should i create a separate bug for the Etch case? What further information would you like? lspci -v output for the freezing / working machines?? Debian is wonderful, Alex -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages ndiswrapper-source depends on: ii bzip2 1.0.5-1high-quality block-sorting file co ii debhelper 7.0.15 helper programs for debian/rules ii module-assistant 0.10.11.0 tool to make module package creati ndiswrapper-source recommends no packages. Versions of packages ndiswrapper-source suggests: pn kernel-package (no description available) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#505096: Acknowledgement (ndiswrapper-source: system freezes shortly after loading module)
After some fiddling it seems that if i "disable USB2.0" (a bios option - as a result the ehci_hcd driver is not loaded) the freezing problem disappears. This is a 5yr old laptop with 3 usb ports. Usually from lspci -v i see three instances of USB1.1 controllers using ohci_hcd, and a mysterious 4th usb controller USB2.0 using ehci_hcd. Is this normal, or is it a fudge they were doing when usb2.0 was pretty new? Anyway, i hope this extra bit of information helps somebody work out the cause of the problem - obviously disabling USB2.0 is not an ideal 'fix' Alex -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#505096: Acknowledgement (ndiswrapper-source: system freezes shortly after loading module)
On Tue, Nov 11, 2008 at 07:37:50AM +0100, Julian Andres Klode wrote: > On Tue, Nov 11, 2008 at 12:40:52AM +0000, alex wrote: > > After some fiddling it seems that if i "disable USB2.0" (a bios option - as > > a result the ehci_hcd driver is not loaded) the freezing problem disappears. > > This is a 5yr old laptop with 3 usb ports. Usually from lspci -v i see > > three instances of USB1.1 controllers using ohci_hcd, and a mysterious 4th > > usb controller USB2.0 using ehci_hcd. Is this normal, or is it a fudge they > > were doing when usb2.0 was pretty new? > > Anyway, i hope this extra bit of information helps somebody work out the > > cause of the problem - obviously disabling USB2.0 is not an ideal 'fix' > I'll take a closer look at it and forward it to upstream. > > Could you give some more details, eg. > lspci -v, the kernel messages when it freezes? > > > > > Alex > > > > > > -- > Julian Andres Klode - Free Software Developer >Debian Developer - Contributing Member of SPI >Ubuntu Member - Fellow of FSFE > > Website: http://jak-linux.org/ XMPP: [EMAIL PROTECTED] > Debian: http://www.debian.org/ SPI: http://www.spi-inc.org/ > Ubuntu: http://www.ubuntu.com/ FSFE: http://www.fsfe.org/ Output of lspci -v is attached. Kernel messages to follow. Alex 00:00.0 Host bridge: Silicon Integrated Systems [SiS] 650/M650 Host (rev 11) Flags: bus master, medium devsel, latency 32 Memory at d000 (32-bit, non-prefetchable) [size=256M] Capabilities: Kernel driver in use: agpgart-sis Kernel modules: sis-agp 00:01.0 PCI bridge: Silicon Integrated Systems [SiS] Virtual PCI-to-PCI bridge (AGP) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 99 Bus: primary=00, secondary=01, subordinate=01, sec-latency=68 I/O behind bridge: 9000-9fff Memory behind bridge: e010-e01f Prefetchable memory behind bridge: e800-efff Kernel modules: shpchp 00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS962 [MuTIOL Media IO] (rev 04) Flags: bus master, medium devsel, latency 0 00:02.1 SMBus: Silicon Integrated Systems [SiS] SiS961/2 SMBus Controller Flags: medium devsel I/O ports at 8100 [size=32] Kernel driver in use: sis96x_smbus Kernel modules: i2c-sis96x 00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (prog-if 80 [Master]) Subsystem: Silicon Integrated Systems [SiS] SiS5513 EIDE Controller (A,B step) Flags: bus master, medium devsel, latency 128 [virtual] Memory at 01f0 (32-bit, non-prefetchable) [disabled] [size=8] [virtual] Memory at 03f0 (type 3, non-prefetchable) [disabled] [size=1] [virtual] Memory at 0170 (32-bit, non-prefetchable) [disabled] [size=8] [virtual] Memory at 0370 (type 3, non-prefetchable) [disabled] [size=1] I/O ports at 1000 [size=16] Capabilities: Kernel driver in use: SIS_IDE Kernel modules: sis5513 00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] AC'97 Sound Controller (rev a0) Subsystem: FIRST INTERNATIONAL Computer Inc Device 2439 Flags: bus master, medium devsel, latency 173, IRQ 5 I/O ports at 1400 [size=256] I/O ports at 1080 [size=128] Capabilities: Kernel driver in use: Intel ICH Kernel modules: snd-intel8x0 00:03.0 USB Controller: Silicon Integrated Systems [SiS] USB 1.1 Controller (rev 0f) (prog-if 10 [OHCI]) Subsystem: FIRST INTERNATIONAL Computer Inc Device 7001 Flags: bus master, medium devsel, latency 64, IRQ 5 Memory at e000 (32-bit, non-prefetchable) [size=4K] Capabilities: Kernel driver in use: ohci_hcd Kernel modules: ohci-hcd 00:03.1 USB Controller: Silicon Integrated Systems [SiS] USB 1.1 Controller (rev 0f) (prog-if 10 [OHCI]) Subsystem: FIRST INTERNATIONAL Computer Inc Device 7001 Flags: bus master, medium devsel, latency 64, IRQ 5 Memory at e0001000 (32-bit, non-prefetchable) [size=4K] Capabilities: Kernel driver in use: ohci_hcd Kernel modules: ohci-hcd 00:03.2 USB Controller: Silicon Integrated Systems [SiS] USB 1.1 Controller (rev 0f) (prog-if 10 [OHCI]) Subsystem: FIRST INTERNATIONAL Computer Inc Device 7001 Flags: bus master, medium devsel, latency 64, IRQ 5 Memory at e0002000 (32-bit, non-prefetchable) [size=4K] Capabilities: Kernel driver in use: ohci_hcd Kernel modules: ohci-hcd 00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet (rev 90) Subsystem: FIRST INTERNATIONAL Computer Inc Device 2419 Flags: bus master, medi
Bug#531835: audacious 2.0.1: freezes after playing an Ogg or MP3 file
I can provide corroboration to this. It only occurs after Vorbis encoded files
for me thus far, however, but i've not really triaged the bugs too much. Trying
to skip to the next song by bringing the main window into focus and pressing "b"
at this point totally hangs the GUI and I have to kill it manually.
Straceing the audacious process when it's hung at the end of a .ogg shows a
polling loop with these two events:
poll([{fd=5, events=POLLIN}, {fd=4, events=POLLIN}, {fd=8, events=POLLIN}], 3,
0) = 0 (Timeout)
read(4, 0x1dcfc94, 4096)= -1 EAGAIN (Resource temporarily
unavailable)
When it's got into the GUI locked state, strace shows it's hanging on a futex:
futex(0x7f14d0ebb9e0, FUTEX_WAIT, 7084, NULL
I hope this helps in tracking down where it's locked.
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.29-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)
Shell: /bin/sh linked to /bin/bash
Versions of packages audacious depends on:
ii audacious-plugins 2.0.1-1Base plugins for audacious
ii dbus 1.2.14-2 simple interprocess messaging syst
ii gtk2-engines-pixbuf 2.16.2-1 Pixbuf-based theme for GTK+ 2.x
ii libatk1.0-0 1.26.0-1 The ATK accessibility toolkit
ii libaudclient2 2.0.1-1audacious dbus remote control libr
ii libaudcore1 2.0.1-1audacious core engine library
ii libaudid3tag2 2.0.1-1audacious id3 tag manipulation lib
ii libaudutil1 2.0.1-1audacious utility library
ii libc6 2.9-13 GNU C Library: Shared libraries
ii libcairo2 1.8.6-2+b1 The Cairo 2D vector graphics libra
ii libdbus-1-3 1.2.14-2 simple interprocess messaging syst
ii libdbus-glib-1-2 0.80-4 simple interprocess messaging syst
ii libfontconfig12.6.0-3generic font configuration library
ii libfreetype6 2.3.9-5FreeType 2 font engine, shared lib
ii libglib2.0-0 2.20.3-1 The GLib library of C routines
ii libgtk2.0-0 2.16.2-1 The GTK+ graphical user interface
ii libice6 2:1.0.5-1 X11 Inter-Client Exchange library
ii libmcs1 0.7.1-1Abstraction library to store confi
ii libmowgli10.6.1-1a high performance development fra
ii libpango1.0-0 1.24.2-1 Layout and rendering of internatio
ii libsad2 2.0.1-1audacious scale and dither library
ii libsamplerate00.1.7-2audio rate conversion library
ii libsm62:1.1.0-2 X11 Session Management library
Versions of packages audacious recommends:
ii audacious-plugins-extra 2.0.1-1Various extra plugins for audaciou
ii unzip 6.0-1 De-archiver for .zip files
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#507380: kdebase-workspace-data: trying to overwrite .../Norway.colors', which is also in package systemsettings
Package: kdebase-workspace-data Version: 4.1.3-2 Severity: grave Justification: renders package unusable I was trying to follow steps to install kde4 on the debian 'instable' (which involved enabling 'experimental' repository, and running aptitude -t experimental install kde4 kdm kdetoys resulted in following error: dpkg: error processing /var/cache/apt/archives/kdebase-workspace-data_4%3a4.1.3-2_all.deb (--unpack): trying to overwrite `/usr/share/kde4/apps/color-schemes/Norway.colors', which is also in package systemsettings -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages kdebase-workspace-data depends on: ii oxygencursors 0.0.2008-07-07-svn824849-1 Oxygen mouse cursor theme kdebase-workspace-data recommends no packages. kdebase-workspace-data suggests no packages. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#526406: linux-image-2.6.29-1-amd64: Kernel BUG 2.6.29 + cpufreq on heavy load
:50 max kernel: [ 1481.590007] [] ? kthread+0x47/0x73 May 1 07:18:50 max kernel: [ 1481.590011] [] ? child_rip+0xa/0x20 May 1 07:18:50 max kernel: [ 1481.590017] [] ? flat_send_IPI_mask+0x0/0x5 May 1 07:18:50 max kernel: [ 1481.590022] [] ? kthread+0x0/0x73 May 1 07:18:50 max kernel: [ 1481.590026] [] ? child_rip+0x0/0x20 May 1 07:18:50 max kernel: [ 1481.590031] Code: 83 e5 3f 89 ea e8 04 fc ff ff 85 c0 75 10 48 8b 54 24 08 48 8d 84 13 18 02 00 00 0f ab 28 48 63 c5 48 8b 5c c3 18 48 85 db 75 04 <0f> 0b eb fe 41 83 ed 06 41 ff cc 45 85 e4 75 b3 48 85 db 74 19 May 1 07:18:50 max kernel: [ 1481.590077] RIP [] radix_tree_tag_set+0x86/0xc6 May 1 07:18:50 max kernel: [ 1481.590083] RSP May 1 07:18:50 max kernel: [ 1481.590091] ---[ end trace 3231142ad0b59f7b ]--- I have been able to reproduce this a number of times. I even tried booting into single user mode and turning on networking and nfs and I go this problem. when I set the governer to performance I don't see this problem. I original had irqbalance running but I saw this when I had stop it as well. Alex -- Package-specific info: ** Version: Linux version 2.6.29-1-amd64 (Debian 2.6.29-2) (wa...@debian.org) (gcc version 4.3.3 (Debian 4.3.3-5) ) #1 SMP Sat Apr 4 16:54:07 UTC 2009 ** Command line: root=/dev/md1 ro quiet ** Tainted: P (1) ** Kernel log: [ 35.167536] EXT3-fs: mounted filesystem with ordered data mode. [ 35.199976] kjournald starting. Commit interval 5 seconds [ 35.240799] EXT3 FS on dm-21, internal journal [ 35.240801] EXT3-fs: recovery complete. [ 35.240804] EXT3-fs: mounted filesystem with ordered data mode. [ 35.305907] kjournald starting. Commit interval 5 seconds [ 35.306111] EXT3 FS on dm-3, internal journal [ 35.306113] EXT3-fs: recovery complete. [ 35.306285] EXT3-fs: mounted filesystem with ordered data mode. [ 35.416832] kjournald starting. Commit interval 5 seconds [ 35.421339] EXT3 FS on dm-0, internal journal [ 35.421342] EXT3-fs: recovery complete. [ 35.421457] EXT3-fs: mounted filesystem with ordered data mode. [ 38.174896] kjournald starting. Commit interval 5 seconds [ 38.207861] EXT3 FS on dm-13, internal journal [ 38.207865] EXT3-fs: recovery complete. [ 38.210993] EXT3-fs: mounted filesystem with ordered data mode. [ 38.617709] kjournald starting. Commit interval 5 seconds [ 38.618944] EXT3 FS on dm-12, internal journal [ 38.618947] EXT3-fs: recovery complete. [ 38.620523] EXT3-fs: mounted filesystem with ordered data mode. [ 38.684406] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled [ 38.684911] SGI XFS Quota Management subsystem [ 38.685306] Filesystem "dm-4": Disabling barriers, trial barrier write failed [ 38.685443] XFS mounting filesystem dm-4 [ 38.834640] Ending clean XFS mount for filesystem: dm-4 [ 38.999759] kjournald starting. Commit interval 5 seconds [ 39.121989] EXT3 FS on dm-23, internal journal [ 39.121992] EXT3-fs: recovery complete. [ 39.121995] EXT3-fs: mounted filesystem with ordered data mode. [ 39.183573] kjournald starting. Commit interval 5 seconds [ 39.220829] EXT3 FS on dm-15, internal journal [ 39.220831] EXT3-fs: recovery complete. [ 39.220834] EXT3-fs: mounted filesystem with ordered data mode. [ 39.271365] kjournald starting. Commit interval 5 seconds [ 39.301863] EXT3 FS on dm-9, internal journal [ 39.301871] EXT3-fs: recovery complete. [ 39.301874] EXT3-fs: mounted filesystem with ordered data mode. [ 39.350324] kjournald starting. Commit interval 5 seconds [ 39.372488] EXT3 FS on dm-19, internal journal [ 39.372490] EXT3-fs: recovery complete. [ 39.372493] EXT3-fs: mounted filesystem with ordered data mode. [ 39.502634] kjournald starting. Commit interval 5 seconds [ 39.511532] EXT3 FS on dm-17, internal journal [ 39.511534] EXT3-fs: recovery complete. [ 39.512613] EXT3-fs: mounted filesystem with ordered data mode. [ 39.522514] Filesystem "dm-16": Disabling barriers, trial barrier write failed [ 39.522623] XFS mounting filesystem dm-16 [ 39.694025] Ending clean XFS mount for filesystem: dm-16 [ 39.761658] kjournald starting. Commit interval 5 seconds [ 39.779741] EXT3 FS on dm-20, internal journal [ 39.779743] EXT3-fs: recovery complete. [ 39.779746] EXT3-fs: mounted filesystem with ordered data mode. [ 39.780119] Filesystem "dm-1": Disabling barriers, trial barrier write failed [ 39.780249] XFS mounting filesystem dm-1 [ 39.962913] Starting XFS recovery on filesystem: dm-1 (logdev: internal) [ 40.122336] Ending XFS recovery on filesystem: dm-1 (logdev: internal) [ 40.159449] Filesystem "dm-14": Disabling barriers, trial barrier write failed [ 40.159564] XFS mounting filesystem dm-14 [ 40.426223] Ending clean XFS mount for filesystem: dm-14 [ 42.270199] alloc irq_desc for 26 on cpu 0 node 0 [ 42.270202] alloc kstat_irqs on
Bug#980240: Cyrus-common: /etc/cron.daily/cyrus-imapd is not working
Package: cyrus-common Version: 3.0.8-6+deb10u4 Severity: grave Tags: patch Justification: causes non-serious data loss Dear maintainer, during a installation of Cyrus-common id discovered a bug in the file: /etc/cron.daily/cyrus-imapd The script is not executed because the Cyrus version check does not match the cyrus version installed on Debian Buster. Als a result the cyrus mailbox db is not exported, which can cause the loss of mailbox cwconfiguration, if the db gets corrupted. here is the diff relativ to /etc to fix the problem: --- a/cron.daily/cyrus-imapd +++ b/cron.daily/cyrus-imapd @@ -33,7 +33,7 @@ umask 022 && [ -f /usr/lib/cyrus/cyrus-hardwired-config.txt ] \ || exit 0 # Check if Cyrus is installed (vs. removed but not purged) -grep -qE '^PACKAGE_VERSION[[:blank:]]+[30][.][245]' \ +grep -qE '^PACKAGE_VERSION[[:blank:]]+3.0[.][2458]' \ /usr/lib/cyrus/cyrus-hardwired-config.txt >/dev/null 2>&1 || exit 0 # 1. backup mailbox database Cheers /alex -- System Information: Debian Release: 10.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-13-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages cyrus-common depends on: ii adduser 3.118 ii db-upgrade-util 5.3.1+nmu1 ii db-util 5.3.1+nmu1 ii debconf [debconf-2.0] 1.5.71 ii dpkg1.19.7 ii e2fsprogs 1.44.5-1+deb10u3 ii gawk1:4.2.1+dfsg-1 ii init-system-helpers 1.56+nmu1 ii libc6 2.28-10 ii libclamav9 0.102.4+dfsg-0+deb10u1 ii libcom-err2 1.44.5-1+deb10u3 ii libgcc1 1:8.3.0-6 ii libgssapi-krb5-21.17-3+deb10u1 ii libical33.0.4-3 ii libicu6363.1-6+deb10u1 ii libjansson4 2.12-1 ii libk5crypto31.17-3+deb10u1 ii libkrb5-3 1.17-3+deb10u1 ii libkrb5support0 1.17-3+deb10u1 ii libldap-2.4-2 2.4.47+dfsg-3+deb10u4 ii libpcre32:8.39-12 ii libsasl2-2 2.1.27+dfsg-1+deb10u1 ii libsasl2-modules2.1.27+dfsg-1+deb10u1 ii libsnmp30 5.7.3+dfsg-5+deb10u1 ii libsqlite3-03.27.2-3+deb10u1 ii libssl1.1 1.1.1d-0+deb10u4 ii libstdc++6 8.3.0-6 ii libwrap07.6.q-28 ii libxapian30 1.4.11-1 ii libxml2 2.9.4+dfsg1-7+deb10u1 ii libzephyr4 3.1.2-1+b3 ii lsb-base10.2019051400 ii netbase 5.6 ii perl5.28.1-6+deb10u1 ii postfix [mail-transport-agent] 3.4.14-0+deb10u1 ii zlib1g 1:1.2.11.dfsg-1 Versions of packages cyrus-common recommends: ii cyrus-admin 3.0.8-6+deb10u4 ii cyrus-imapd 3.0.8-6+deb10u4 Versions of packages cyrus-common suggests: ii apt-listchanges3.19 ii cyrus-admin3.0.8-6+deb10u4 pn cyrus-caldav pn cyrus-clients pn cyrus-doc ii cyrus-imapd3.0.8-6+deb10u4 pn cyrus-murder pn cyrus-nntpd pn cyrus-pop3d pn cyrus-replication ii sasl2-bin 2.1.27+dfsg-1+deb10u1 -- Configuration Files: /etc/cron.daily/cyrus-imapd changed [not included] /etc/cyrus.conf changed [not included] /etc/default/cyrus-imapd changed [not included] /etc/imapd.conf changed [not included] -- debconf information: * cyrus-common/removespools: true
Bug#602975: procmeter3 (3.5c-1) SEGVs upon startup
Both procmeter3-xaw and procmeter3-gtk2 work on my amd64 sid system, so something might be wrong on your side. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#609230: lighttpd: Lighttpd fails to start after OpenSSL update from Bug 555829
Package: lighttpd Version: 1.4.19-5+lenny1 Severity: grave Justification: renders package unusable Fix for Bug 555829 introduces incompatible changes that prevent Lighttpd from starting. -- System Information: Debian Release: 5.0.7 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages lighttpd depends on: ii libattr1 1:2.4.43-2Extended attribute shared library ii libbz2-1.0 1.0.5-1+lenny1high-quality block-sorting file co ii libc6 2.7-18lenny6 GNU C Library: Shared libraries ii libfam02.7.0-13.3+lenny1 Client library to control the FAM ii libldap-2.4-2 2.4.11-1+lenny2 OpenLDAP libraries ii libpcre3 7.6-2.1 Perl 5 Compatible Regular Expressi ii libssl0.9.80.9.8g-15+lenny9 SSL shared libraries ii libterm-readline-perl- 1.0302-1 Perl implementation of Readline li ii lsb-base 3.2-20Linux Standard Base 3.2 init scrip ii mime-support 3.44-1MIME files 'mime.types' & 'mailcap ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime lighttpd recommends no packages. Versions of packages lighttpd suggests: ii apache2-utils 2.2.9-10+lenny9 utility programs for webservers ii openssl0.9.8g-15+lenny11 Secure Socket Layer (SSL) binary a pn rrdtool(no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#696485: inkscape: CVE-2012-5656
fowarded 696485 https://bugs.launchpad.net/inkscape/+bug/ thanks Note that this issue is fixed upstream in Inkscape 0.48.4 along with many other bugs. It would be a good idea to upgrade the package soon. Package: inkscape Severity: grave Tags: security Justification: user security hole Hi, CVE-2012-5656 was assigned to this security issues: https://bugs.launchpad.net/inkscape/+bug/1025185 Fix: http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/revision/11931 Cheers, Moritz
Bug#683312: Please consider including this patch before wheezy
On 14 January 2013 17:54, gregor herrmann wrote: > On Sun, 13 Jan 2013 19:10:00 +0000, Alex Owen wrote: > >> I have regenerated the patch against uif- 1.0.6 to make it simple to >> review and apply to the package currently in Wheezy. > > Seems you didn't attach this new patch? Oops! Sorry! > > BTW: After looking at your original patch, I have the impression that > you missed "moving" one $not (dport, in the line with two "$not"s). > Good catch... Here (and really attached this time) is an updated patch including Gregor's point also. Regards Alex Owen uif-pling-position-v2.patch Description: Binary data
Bug#683312: Please consider including this patch before wheezy
On 14 January 2013 19:04, gregor herrmann wrote: > I think I found another one ... > > What I did was switching the (-)-$args and $nots with perl, and > comparing the result with your patch there's one difference: > > #v+ > -+ push (@source, "$not -s $1 -m mac --mac-source $not $2"); > ++ push (@source, "$not -s $1 -m mac $not --mac-source $2"); > #v- > > I'm attaching my complete (auto-)patch; could you please double-check? > Hello Gregor, I have used grep and wc -l and looked and re-looked... your patch looks complete to me. Thanks for looking at this issue and fixing my mistakes! Alex Owen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#1022124: libdbd-oracle-perl needs binaries uploaded for the perl 5.36 transitions
Hi Adrian, > libdbd-oracle-perl cannot be built on the buildds, > and it needs binaries uploaded for the perl 5.36 transition. Please, don't hesitate to remove libdbd-oracle-perl from testing for the perl 5.36 transition to proceed. I'll try to have those binaries by next week, but I don't want to stall the transition. Cheers! Alex -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Alex Muntada ⢿⡄⠘⠷⠚⠋ Debian Developer 🍥 log.alexm.org ⠈⠳⣄ signature.asc Description: PGP signature
Bug#1016903: Does this bug affect Bookworm on AMD64?
I’m sorry if this is the wrong place to post this, but I’m still trying to figure everything out. Am I correct in concluding that this bug doesn’t affect packages compiled for Bookworm on AMD64? What about packages on AMD64 (like libpcre2-32-0) with 32-bit runtimes/versions/ABIs or packages (like fdupes) that depend on them?
Bug#930796: spindown_time and force_spindown_time are broken in hdparm 9.58+ds-1
On 6/20/19 8:42 PM, Sébastien Béhuret wrote: > Package: hdparm > Version: 9.58+ds-1 > Severity: serious > > Dear Maintainers, > > In this version of hdparm, a new option 'force_spindown_time' was > introduced to set the spindown time for disks that don't support APM. > This option is supposed to translate to hdparm -S, similarly to the > original option 'spindown_time'. > > hdparm package comes with 3 main scripts: > > 1) /usr/lib/pm-utils/power.d/95hdparm-apm > This script will translate 'force_spindown_time' to hdparm -S and apply > the option even if APM was not detected. > This is the desired behavior. > > 2) /etc/apm/event.d/20hdparm > This script will ignore /etc/hdparm.conf and apply hard-coded defaults > instead. > This behavior is unexpected. > Expected/Desired behavior: Read /etc/hdparm.conf and apply relevant options. > > 3) /lib/hdparm/hdparm-functions (sourced from /lib/udev/hdparm, which is > invoked by udev rule /lib/udev/rules.d/85-hdparm.rules) > - 'force_spindown_time' is buggy because it is not converted back to -S, > which leads to a syntax error during hdparm execution (e.g. hdparm > force_spindown_time$VALUE instead of hdparm -S$VALUE). > - Both options 'spindown_time' and 'force_spindown_time' are processed > even if APM is not supported. From the comments in the configuration > file (/etc/hdparm.conf), it is understood that 'spindown_time' will be > applied for APM disks only and 'force_spindown_time' for all disks (or > possibly for non-APM disks only). > - The scripts will also apply hard-coded defaults for -S and -B if APM > was detected. The hard-coded defaults differ from those used in > /etc/apm/event.d/20hdparm, leading to inconsistent behavior. > > 4) Additional issues with non-APM disks: > - Manually invoking hdparm -S$VALUE /dev/sdx is simply ignored even > though hdparm executes successfully. The disks do not spin down after > the time delay when there was no access. > - Manually invoking hdparm -y /dev/sdx will spin down the disks > immediately. The disks will not wake up unless they are accessed, which > is the expected behavior. > > These were all working fine in hdparm 9.51+ds-1+deb9u1, which is the > current version in stretch. > > In short, it is currently impossible to obtain a consistent and working > configuration for non-APM disks. > > Many thanks and regards, > Sebastien Behuret Hi Sebastien, 2. As APM is almost dead and most likely there are no laptops using APM and buster. I'll drop /etc/apm/event.d/20hdparm in the next release. 3. This is a real issue. In /lib/hdparm/hdparm-functions I've left the "force_spindown_time$VALUE" option intentionally, it need to be translated to "-S" later in scripts using hdparm-functions like it is done in 95hdparm-apm /lib/udev/hdparm is called by udev and need to be fixed. /usr/lib/pm-utils/power.d/95hdparm-apm called by pm-utils events and takes care only about spin_down and apm options for the disks which support apm. To obtain a consistent behavior /lib/udev/hdparm can call /usr/lib/pm-utils/power.d/95hdparm-apm for spindown and apm options and hdparm directly for all other options. 4. I failed to reproduce that. I couldn't put to standby a non-apm disk on a stretch system with hdparm -S (hdparm 9.51) Could you please try to build hdparm 9.51 or just get a binary package and run it to see if 9.51 works for your disks compared to 9.58? Thank you for the detailed report. Alex
Bug#931900: Program crashes with message "free(): double free detected in tcache 2"
Package: projectm-pulseaudio Version: 2.1.0+dfsg-4+b4 Severity: grave Dear Maintainer, First off, I'm new to the BTS so excuse me for not doing this right. projectm-pulseaudio crashes after a few seconds in Buster. Typing "N" to go to the next visualization effect crashes the program instantly. Here is a log: user@debian:~$ projectM-pulseaudio dir:/usr/share/projectM/config.inp reading ~/.projectM/config.inp [projectM] config file: /home/user/.projectM/config.inp No Textures Loaded from "/usr"/share/projectM/textures [projectM] Allocating idle preset... [PresetFactory] path is Geiss & Sperl - Feedback (projectM idle HDR mix).milk [PresetFactory] url is idle://Geiss & Sperl - Feedback (projectM idle HDR mix).milk unconnected: connecting... connectHelper: "alsa_output.pci-_00_1b.0.analog-stereo.monitor" CREATED READY [PresetFactory] path is r/share/projectM/presets/phat_CloseIncounetersV2.milk [PresetFactory] url is /usr/share/projectM/presets/phat_CloseIncounetersV2.milk free(): double free detected in tcache 2 Aborted Not a programmer so I really don't know what "free(): double free detected in tcache 2", but I can only assume that's where the problem lies. Thank you, and have a great day/night. -Alex Relis -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/2 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages projectm-pulseaudio depends on: ii libc6 2.28-10 ii libftgl2 2.4.0-2 ii libgcc11:8.3.0-6 ii libglew2.1 2.1.0-4 ii libprojectm-qt1v5 2.1.0+dfsg-4+b4 ii libprojectm2v5 2.1.0+dfsg-4+b4 ii libpulse0 12.2-4 ii libqt4-opengl 4:4.8.7+dfsg-18 ii libqtcore4 4:4.8.7+dfsg-18 ii libqtgui4 4:4.8.7+dfsg-18 ii libstdc++6 8.3.0-6 ii pulseaudio 12.2-4 projectm-pulseaudio recommends no packages. projectm-pulseaudio suggests no packages. -- no debconf information signature.asc Description: OpenPGP digital signature
Bug#931900: Program crashes with message "free(): double free detected in tcache 2"
Oh, my bad. Weird that I didn't see it. Looks like there is a fix in that other bug report. Good luck. On 7/12/19 1:52 AM, Bernhard Übelacker wrote: > Hello > the issue you observed might be already reported in: > https://bugs.debian.org/924925 > > Kind regards, > Bernhard > signature.asc Description: OpenPGP digital signature
Bug#932257: libdbd-oracle-perl: unsatisfiable dependencies
Hi Héctor, > libdbd-oracle-perl depends on oracle-instantclient12.1-basic | > oracle-instantclient12.1-basiclite, which are not found in > buster|bullseye|unstable, causes the package to be unusable. There's a comment in d/copyright explaining why this package is in contrib: «The upstream Perl distribution is freely licensed by the copyright holders but depends on Oracle Instant Client software, that is not free. Therefore, it belongs to Debian contrib section according to DFSG.» Is there something that has recently changed that maybe I'm missing? Thanks! Alex -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Alex Muntada ⢿⡄⠘⠷⠚⠋ Debian Developer 🍥 log.alexm.org ⠈⠳⣄ signature.asc Description: PGP signature
Bug#932257: libdbd-oracle-perl: unsatisfiable dependencies
Hi Hector, > Where can I find those packages to close the dependency loop, Since those dependencies should be installed before this package, the full package description has a link to the README where you can find where to download them and how to get them into shape for Debian: https://packages.debian.org/buster/libdbd-oracle-perl https://deb.li/dbdoracle I just found out that APT is not showing the full package description anymore, and that makes it more difficult for this package to explain how to proceed with dependencies. Any ideas on improving this are truly appreciated. > checking at non-free those do not seem to be available. Sorry, we can't put them in non-free either because the source is not available. Cheers! Alex -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Alex Muntada ⢿⡄⠘⠷⠚⠋ Debian Developer 🍥 log.alexm.org ⠈⠳⣄ signature.asc Description: PGP signature
Bug#932257: libdbd-oracle-perl: unsatisfiable dependencies
Hi gregor, > I just wanted to propose "Check the README" but it seems like > the friendly README at > https://salsa.debian.org/perl-team/modules/packages/libdbd-oracle-perl/blob/master/debian/README > doesn't get installed in the package anymore … Oops. Ouch! I missed that. Thanks for pointing that out. Cheers, Alex -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Alex Muntada ⢿⡄⠘⠷⠚⠋ Debian Developer 🍥 log.alexm.org ⠈⠳⣄ signature.asc Description: PGP signature
Bug#932257: libdbd-oracle-perl: unsatisfiable dependencies
Hi gregor, > I just wanted to propose "Check the README" but it seems like > the friendly README [...] doesn't get installed in the package > anymore … Oops. I examined the contents of the older versions I have in my computer and none of them installed the README. Maybe it's because package installation will fail unless its depends are met first and hence the link to the README in the full description. I guess we could rename README to README.Debian and install it anyway. What do you think? Cheers! Alex -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Alex Muntada ⢿⡄⠘⠷⠚⠋ Debian Developer 🍥 log.alexm.org ⠈⠳⣄ signature.asc Description: PGP signature
Bug#932872: [libkscreenlocker5] Doesn't lock automatically by timeout
Package: libkscreenlocker5 Version: 5.14.5-1 Severity: grave --- Please enter the report below this line. --- Doesn't lock automatically by timeout, which presents a security issue. Seems to work in a newly created test user setup, and randomly works sometimes in my user, but I have no idea what makes in work. Probably some app "inhibits" the automatic timeout, but I have no idea how to check it with all that "brilliant" dbus crap. Ubuntu has https://wiki.ubuntu.com/ DebuggingScreenLocking, but it's for Gnome, not KDE. --- System information. --- Architecture: Kernel: Linux 4.19.37-bootes0-iommu-p-1000 Debian Release: 10.0 991 stable security.debian.org 991 stable ftp.fi.debian.org 990 buster-backports ftp.debian.org 99 stable www.deb-multimedia.org 500 stable dl.google.com 500 stable deb.torproject.org --- Package information. --- Depends (Version) | Installed =-+- kpackagetool5 | 5.54.0-1 libc6 (>= 2.28) | libkf5configcore5 (>= 5.24.0) | libkf5configgui5 (>= 4.97.0) | libkf5coreaddons5 (>= 4.97.0) | libkf5crash5 (>= 4.96.0) | libkf5declarative5 (>= 5.50.0~) | libkf5globalaccel-bin | libkf5globalaccel5 (>= 5.0.0) | libkf5i18n5 (>= 4.97.0) | libkf5idletime5 (>= 4.96.0) | libkf5notifications5 (>= 4.96.0) | libkf5package5(>= 5.42.0) | libkf5quickaddons5 (>= 5.50.0~) | libkf5waylandclient5 (>= 4:5.5.0) | libkf5waylandserver5 (>= 4:5.6.2) | libkf5windowsystem5 (>= 5.25.0) | libpam0g(>= 0.99.7.1) | libqt5core5a (>= 5.11.0~rc1) | libqt5dbus5 (>= 5.11.0~) | libqt5gui5 (>= 5.11.0~) | libqt5network5 (>= 5.11.0~) | libqt5qml5 (>= 5.0.2) | libqt5quick5 (>= 5.2.0) | libqt5widgets5 (>= 5.11.0~) | libqt5x11extras5 (>= 5.6.0) | libseccomp2 (>= 0.0.0~20120605) | libstdc++6 (>= 4.4.0) | libwayland-client0(>= 1.9.91) | libwayland-server0 (>= 1.3~) | libx11-6 | libxcb-keysyms1(>= 0.4.0) | libxcb1 | libxi6(>= 2:1.2.99.4) | Recommends (Version) | Installed ==-+-=== kde-config-screenlocker| 5.14.5-1 Package's Suggests field is empty.
Bug#932257: libdbd-oracle-perl: unsatisfiable dependencies
Control: owner -1 ! Control: severity -1 minor Hector said: > Thanks for the explanation, I was just checking repository > consistency for buster and came up with this issue. I leave > it up to you to downgrade severity accordingly or close the > bug. Fixing the README installation one way or the other > might be nice. Will fix the README installation. For now, I'm lowering the bug severity to avoid autoremoval from testing. Thanks, Alex -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Alex Muntada ⢿⡄⠘⠷⠚⠋ Debian Developer 🍥 log.alexm.org ⠈⠳⣄ signature.asc Description: PGP signature
Bug#874176: wrk: Fails to run with 'PANIC: unprotected error in call to Lua API'
Package: wrk
Version: 4.0.2-2
Followup-For: Bug #874176
Dear Maintainer,
* What led up to the situation?
I needed to use wrk for some benchmark.
* What exactly did you do (or not do) that was effective (or
ineffective)?
apt install wrk && wrk -c 800 -d 10 -t 24 http://127.0.0.1:8080/
* What was the outcome of this action?
PANIC: unprotected error in call to Lua API (attempt to index a nil value)
* What outcome did you expect instead?
the benchmark to run.
Currently luajit-2.1 is installed but the sources are looking for luajit-2.0,
also luajit-2.1 is missing a define (luaL_reg luaL_Reg) and src/script.c fail
to compile.
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
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 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages wrk depends on:
ii libc62.28-10
ii libluajit-5.1-2 2.1.0~beta3+dfsg-5.1
ii libssl1.11.1.1c-1
wrk recommends no packages.
wrk suggests no packages.
-- no debconf information
Index: wrk-4.0.2/src/script.h
===
--- wrk-4.0.2.orig/src/script.h
+++ wrk-4.0.2/src/script.h
@@ -2,9 +2,9 @@
#define SCRIPT_H
#include
-#include
-#include
-#include
+#include
+#include
+#include
#include
#include "stats.h"
#include "wrk.h"
Index: wrk-4.0.2/src/wrk.h
===
--- wrk-4.0.2.orig/src/wrk.h
+++ wrk-4.0.2/src/wrk.h
@@ -10,7 +10,7 @@
#include
#include
-#include
+#include
#include "stats.h"
#include "ae.h"
Index: wrk-4.0.2/src/script.c
===
--- wrk-4.0.2.orig/src/script.c
+++ wrk-4.0.2/src/script.c
@@ -26,6 +26,8 @@ static void set_fields(lua_State *, int,
static void set_field(lua_State *, int, char *, int);
static int push_url_part(lua_State *, char *, struct http_parser_url *, enum
http_parser_url_fields);
+#define luaL_reg luaL_Reg
+
static const struct luaL_reg addrlib[] = {
{ "__tostring", script_addr_tostring },
{ "__gc", script_addr_gc },
Bug#934600: [Debian-med-packaging] Bug#934600: gffread in cufflinks seems to be the same codebase but older
On 8/20/19 7:16 AM, Andreas Tille wrote: > Hi Alexandre, > > it looks as if the gffread code in cufflinks would be the > same code base but the code in gffread source seems to be > more recent. What do you think? > > Kind regards > > Andreas. > > - Forwarded message from Debian testing autoremoval watch > - > > Date: Tue, 20 Aug 2019 04:39:04 + > From: Debian testing autoremoval watch > To: cuffli...@packages.debian.org > Subject: cufflinks is marked for autoremoval from testing > > cufflinks 2.2.1+dfsg.1-3 is marked for autoremoval from testing on 2019-09-10 > > It is affected by these RC bugs: > 934600: cufflinks,gffread: both ship /usr/bin/gffread > > > ___ > Debian-med-packaging mailing list > debian-med-packag...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging > > - End forwarded message - > Hi Andreas, I wasn't aware of gffread as a separate project. If it is a successor of cufflink's gffread we can stop shipping gffread with cufflinks package and add gffread package into Suggested for cufflinks. I'll wait for some clarifications from the upstream and modify the cufflinks package accordingly. https://github.com/gpertea/gffread/issues/40 Best regards, Alex
Bug#927471: More info on curl regression.
control: tags -1 +more-info Hi Guillem, I'm working on this bug as a part of Toronto BSP. https://wiki.debian.org/BSP/2019/04/ca/Toronto Can you give more details on how to reproduce the bug. For example to which tracker rtorrent is connecting. Does this happen with every torrent connection or just some? Is it possible to reproduce the bug by running curl command on the url? Alex.
Bug#925555: linux-image-4.19.0-4-amd64 causes X regression
ional, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 418.694] (==) Log file: "/home/alex/.local/share/xorg/Xorg.1.log", Time: Mon Apr 29 09:14:51 2019 [ 418.694] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 418.694] (==) No Layout section. Using the first Screen section. [ 418.694] (==) No screen section available. Using defaults. [ 418.694] (**) |-->Screen "Default Screen Section" (0) [ 418.694] (**) | |-->Monitor "" [ 418.695] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 418.695] (==) Automatically adding devices [ 418.695] (==) Automatically enabling devices [ 418.695] (==) Automatically adding GPU devices [ 418.695] (==) Max clients allowed: 256, resource mask: 0x1f [ 418.695] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 418.695]Entry deleted from font path. [ 418.695] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [ 418.695] (==) ModulePath set to "/usr/lib/xorg/modules" [ 418.695] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 418.695] (II) Loader magic: 0x560bdf3a3e20 [ 418.695] (II) Module ABI versions: [ 418.695]X.Org ANSI C Emulation: 0.4 [ 418.695]X.Org Video Driver: 24.0 [ 418.695]X.Org XInput driver : 24.1 [ 418.695]X.Org Server Extension : 10.0 [ 418.696] (++) using VT number 2 [ 418.699] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_35 [ 418.699] (II) xfree86: Adding drm device (/dev/dri/card0) [ 418.700] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 11 paused 0 [ 418.701] (--) PCI:*(0@0:2:0) 8086:0412:1043:8534 rev 6, Mem @ 0xf780/4194304, 0xe000/268435456, I/O @ 0xf000/64, BIOS @ 0x/131072 [ 418.701] (II) LoadModule: "glx" [ 418.701] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [ 418.702] (II) Module glx: vendor="X.Org Foundation" [ 418.702]compiled for 1.20.3, module version = 1.0.0 [ 418.702]ABI class: X.Org Server Extension, version 10.0 [ 418.702] (==) Matched modesetting as autoconfigured driver 0 [ 418.702] (==) Matched fbdev as autoconfigured driver 1 [ 418.702] (==) Matched vesa as autoconfigured driver 2 [ 418.702] (==) Assigned the driver to the xf86ConfigLayout [ 418.702] (II) LoadModule: "modesetting" [ 418.702] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so [ 418.702] (II) Module modesetting: vendor="X.Org Foundation" [ 418.702]compiled for 1.20.3, module version = 1.20.3 [ 418.702]Module class: X.Org Video Driver [ 418.702]ABI class: X.Org Video Driver, version 24.0 [ 418.702] (II) LoadModule: "fbdev" [ 418.702] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so [ 418.702] (II) Module fbdev: vendor="X.Org Foundation" [ 418.702]compiled for 1.20.0, module version = 0.5.0 [ 418.702]Module class: X.Org Video Driver [ 418.702]ABI class: X.Org Video Driver, version 24.0 [ 418.702] (II) LoadModule: "vesa" [ 418.702] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so [ 418.702] (II) Module vesa: vendor="X.Org Foundation" [ 418.702]compiled for 1.20.1, module version = 2.4.0 [ 418.702]Module class: X.Org Video Driver [ 418.702]ABI class: X.Org Video Driver, version 24.0 [ 418.702] (II) modesetting: Driver for Modesetting Kernel Drivers: kms [ 418.702] (II) FBDEV: driver for framebuffer: fbdev [ 418.702] (II) VESA: driver for VESA chipsets: vesa [ 418.702] xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted) [ 418.702] (II) modeset(0): using drv /dev/dri/card0 [ 418.702] (WW) Falling back to old probe method for fbdev [ 418.702] (II) Loading sub module "fbdevhw" [ 418.702] (II) LoadModule: "fbdevhw" [ 418.702] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so [ 418.702] (II) Module fbdevhw: vendor="X.Org Foundation" [ 418.702]compiled for 1.20.3, module version = 0.0.2 [ 418.702]ABI class: X.Org Video Driver, version 24.0 [ 418.702] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support [ 418.702] (II) modeset(0): Creating default Display subsection in Screen section "Default Screen Section" for depth/fbbpp 24/32 [ 418.702] (==) modeset(0): Depth 24, (==) framebuffer bpp 32 [ 418.702] (==) modeset(0): RGB weight 888 [ 418.702] (==) modeset(0): Default visual is TrueCo
Bug#928631:
Exactly the same issue with AMD Vega 56 videocard, also depends on vega10_gpu_info.bin: May 29 11:49:37 debian1 kernel: [4.351872] amdgpu :1a:00.0: firmware: direct-loading firmware amdgpu/vega10_gpu_info.bin <..> May 29 11:49:37 debian1 kernel: [4.352869] amdgpu :1a:00.0: firmware: direct-loading firmware amdgpu/vega10_sos.bin May 29 11:49:37 debian1 kernel: [4.352895] amdgpu :1a:00.0: firmware: direct-loading firmware amdgpu/vega10_asd.bin May 29 11:49:37 debian1 kernel: [4.352971] amdgpu :1a:00.0: firmware: direct-loading firmware amdgpu/vega10_acg_smc.bin May 29 11:49:37 debian1 kernel: [4.352996] amdgpu :1a:00.0: firmware: direct-loading firmware amdgpu/vega10_pfp.bin May 29 11:49:37 debian1 kernel: [4.353008] amdgpu :1a:00.0: firmware: direct-loading firmware amdgpu/vega10_me.bin May 29 11:49:37 debian1 kernel: [4.353019] amdgpu :1a:00.0: firmware: direct-loading firmware amdgpu/vega10_ce.bin May 29 11:49:37 debian1 kernel: [4.353031] amdgpu :1a:00.0: firmware: direct-loading firmware amdgpu/vega10_rlc.bin May 29 11:49:37 debian1 kernel: [4.353109] amdgpu :1a:00.0: firmware: direct-loading firmware amdgpu/vega10_mec.bin May 29 11:49:37 debian1 kernel: [4.353188] amdgpu :1a:00.0: firmware: direct-loading firmware amdgpu/vega10_mec2.bin May 29 11:49:37 debian1 kernel: [4.355194] amdgpu :1a:00.0: firmware: direct-loading firmware amdgpu/vega10_sdma.bin May 29 11:49:37 debian1 kernel: [4.355209] amdgpu :1a:00.0: firmware: direct-loading firmware amdgpu/vega10_sdma1.bin -- -Alex
Bug#945205: Wacom Cintiq 27QHD not working [as it did in Stretch]
Package: bugs.debian.org Severity: grave Dear Maintainer, Please be aware that after installation of the Debian 10.0/10.1 Buster, the Wacom Cintiq 27 QHD did not work as it has been working in Stretch by default, e.g.: * xsetwacom --list shows Pen, Pad, Eraser but not the device itself; * moving the pen over the Wacom surface does not move the pointer at all * attempting to use "xsetwacom set .." does not change its behaviour another user reported the issue is related to the use of XWayLand in Buster: http://burntworld.ca/wacom-debian-buster.html Installed AMD Radeon 580X Sapphire 8GB worked just fine with Wacom Cintiq 27QHD in previous installations of the Debian 9.* Stretch. I am saddened to inform you herewith that this issue stocks up upon a pile of other regression issues rendering Debian to be a too time consuming option for a professional daily use on a Desktop Workstation. I wish that you might take this issue into consideration and improve in the future releases to make Debian a breeze to use "out-of-the-box" after installation without the need of tinkering it for days to make it into a usable state after each major Debian release. Thank you for paying attention. -- System Information: Debian Release: 10.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-6-amd64 (SMP w/32 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#946155: libpam-fscrypt: PAM module config broken
Package: libpam-fscrypt Version: 0.2.4-2 Severity: grave Justification: renders package unusable Hi! Apparently in the latest version (0.2.5-1) the path substitution was broken, resulting in "PAM_INSTALL_PATH" being used instead of the library name "pam_fscrypt.so". This killed decryption triggered by PAM. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (100, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.2.0-2-amd64 (SMP w/6 CPU cores) Kernel taint flags: TAINT_USER Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8), LANGUAGE=de_AT:de (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libpam-fscrypt depends on: ii fscrypt 0.2.4-2 ii libc6 2.29-3 ii libpam0g 1.3.1-5 libpam-fscrypt recommends no packages. libpam-fscrypt suggests no packages. -- no debconf information
Bug#945920: Chromium randomly crashes in the latest version.
Package: chromium Version: 79.0.3945.79-1 Followup-For: Bug #945920 Dear Maintainer, I'm experiencing the same random crashes after upgrading from 78.0.3904.108-1 to 79.0.3945.79-1 Backtrace attached. Regards -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.3.0-3-amd64 (SMP w/8 CPU cores) 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 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages chromium depends on: ii chromium-common79.0.3945.79-1 ii libasound2 1.1.9-1 ii libatk-bridge2.0-0 2.34.1-2 ii libatk1.0-02.34.1-1 ii libatomic1 9.2.1-21 ii libatspi2.0-0 2.34.0-3 ii libavcodec-extra58 [libavcodec58] 7:4.2.1-2 ii libavformat58 7:4.2.1-2 ii libavutil567:4.2.1-2 ii libc6 2.29-6 ii libcairo-gobject2 1.16.0-4 ii libcairo2 1.16.0-4 ii libcups2 2.3.0-7 ii libdbus-1-31.12.16-2 ii libdrm22.4.100-4 ii libevent-2.1-7 2.1.11-stable-1 ii libexpat1 2.2.9-1 ii libflac8 1.3.3-1 ii libfontconfig1 2.13.1-2+b1 ii libfreetype6 2.10.1-2 ii libgcc11:9.2.1-21 ii libgdk-pixbuf2.0-0 2.40.0+dfsg-1 ii libglib2.0-0 2.62.3-2 ii libgtk-3-0 3.24.13-1 ii libharfbuzz0b 2.6.4-1 ii libicu63 63.2-2 ii libjpeg62-turbo1:1.5.2-2+b1 ii libjsoncpp11.7.4-3+b1 ii liblcms2-2 2.9-4 ii libminizip11.1-8+b1 ii libnspr4 2:4.23-1 ii libnss32:3.47.1-1 ii libopenjp2-7 2.3.1-1 ii libopus0 1.3-1+b1 ii libpango-1.0-0 1.42.4-7 ii libpangocairo-1.0-01.42.4-7 ii libpci31:3.6.2-6 ii libpng16-161.6.37-1 ii libpulse0 13.0-3 ii libre2-5 20191101+dfsg-1 ii libsnappy1v5 1.1.7-2 ii libstdc++6 9.2.1-21 ii libva2 2.5.0-2 ii libvpx61.8.1-2 ii libwebp6 0.6.1-2+b1 ii libwebpdemux2 0.6.1-2+b1 ii libwebpmux30.6.1-2+b1 ii libx11-6 2:1.6.8-1 ii libx11-xcb12:1.6.8-1 ii libxcb11.13.1-2 ii libxcomposite1 1:0.4.4-2 ii libxcursor11:1.2.0-2 ii libxdamage11:1.1.5-1 ii libxext6 2:1.3.3-1+b2 ii libxfixes3 1:5.0.3-1 ii libxi6 2:1.7.9-1 ii libxml22.9.4+dfsg1-8 ii libxrandr2 2:1.5.1-1 ii libxrender11:0.9.10-1 ii libxslt1.1 1.1.32-2.2 ii libxss11:1.2.3-1 ii libxtst6 2:1.2.3-1 ii zlib1g 1:1.2.11.dfsg-1+b1 Versions of packages chromium recommends: ii chromium-sandbox 79.0.3945.79-1 Versions of packages chromium suggests: pn chromium-driver pn chromium-l10n pn chromium-shell Versions of packages chromium-common depends on: ii x11-utils 7.7+4 ii xdg-utils 1.1.3-1 Versions of packages chromium-common recommends: ii chromium-sandbox 79.0.3945.79-1 ii dunst [notification-daemon] 1.4.1-1 ii fonts-liberation 1:1.07.4-10 ii libgl1-mesa-dri 19.2.6-1 ii libu2f-udev 1.1.10-1 ii notification-daemon 3.20.0-4 ii system-config-printer1.5.12-1 ii upower 0.99.11-1 Versions of packages chromium-sandbox depends on: ii libatomic1 9.2.1-21 ii libc6 2.29-6 ii libgcc1 1:9.2.1-21 ii libstdc++6 9.2.1-21 -- no debconf information #0 0x5a77cee7 in memory_instrumentation::MemoryInstrumentation::RequestGlobalDump(std::vector, std::allocator >, std::allocator, std::allocator > > > const&, base::OnceCallback >)>) () #1 0x58f8ddb0 in ProcessMemoryMetric
Bug#920835: mlucas FTBFS on !amd64: test failures
Hello Adrian Bunk, The test log is not useful at all. I want to add a patch to enable verbose test log and let it build again to identify the issues. Is it possible for me to get access to porter machine or should I upload to experimental and let buildd to build it? Thanks for your great work in Debian! Cheers, Alex Adrian Bunk writes: > Source: mlucas > Version: 17.1-1 > Severity: serious > Tags: ftbfs > > https://buildd.debian.org/status/package.php?p=mlucas&suite=sid > > ... > FAIL: tests/spot-check > == > > ./tests/..//mlucas: 149: exec: ./tests/../: Permission denied > FAIL tests/spot-check (exit status: 126) > > FAIL: tests/self-test > = > > ./tests/..//mlucas: 149: exec: ./tests/../: Permission denied > FAIL tests/self-test (exit status: 126) > > FAIL: tests/fermat-test > === > > ./tests/..//mlucas: 149: exec: ./tests/../: Permission denied > FAIL tests/fermat-test (exit status: 126) > > > Testsuite summary for Mlucas 17.1 > > # TOTAL: 3 > # PASS: 0 > # SKIP: 0 > # XFAIL: 0 > # FAIL: 3 > # XPASS: 0 > # ERROR: 0 > > See ./test-suite.log > Please report to ewma...@aol.com > > make[3]: *** [Makefile:12510: test-suite.log] Error 1 signature.asc Description: PGP signature
Bug#920834: mlucas: FTBFS and baseline vioiation on i386
Dear Adrian Bunk, Regarding FTBFS, I've commented it at <https://bugs.debian.org/920835>. Regarding baseline vioiation on i386, the autotool build system builds 2 versions of the binary: generic-c and SSE2, and install it to libexecdir. Then the wrapper script selects the right binary at run-time. Does this approach satifies the current policy? Cheers, Alex Adrian Bunk writes: > Source: mlucas > Version: 17.1-1 > Severity: serious > Tags: ftbfs > > https://buildd.debian.org/status/fetch.php?pkg=mlucas&arch=i386&ver=17.1-1&stamp=1548777459&raw=0 > > ... > gcc -pthread -O2 -O3 -Ofast -flto -pipe -ftree-vectorize > -floop-nest-optimize -fomit-frame-pointer -g -g3 > -fstack-protector-strong -fstack-clash-protection -mmitigate-rop > -fwrapv -m32 -msse2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong > -Wformat -Werror=format-security -Wl,-z,relro -Wl,-z,now -o > mlucas-sse2 src/mlucas_sse2-Mlucas.o src/mlucas_sse2-br.o > src/mlucas_sse2-dft_macro.o src/mlucas_sse2-factor.o > src/mlucas_sse2-fermat_mod_square.o src/mlucas_sse2-fgt_m61.o > src/mlucas_sse2-gcd_lehmer.o src/mlucas_sse2-getRealTime.o > src/mlucas_sse2-get_cpuid.o src/mlucas_sse2-get_fft_radices.o > src/mlucas_sse2-get_fp_rnd_const.o > src/mlucas_sse2-get_preferred_fft_radix.o src/mlucas_sse2-imul_macro.o > src/mlucas_sse2-mers_mod_square.o src/mlucas_sse2-mi64.o > src/mlucas_sse2-pairFFT_mul.o src/mlucas_sse2-qfloat.o > src/mlucas_sse2-radix1008_ditN_cy_dif1.o > src/mlucas_sse2-radix1024_ditN_cy_dif1.o > src/mlucas_sse2-radix104_ditN_cy_dif1.o > src/mlucas_sse2-radix10_ditN_cy_dif1.o > src/mlucas_sse2-radix112_ditN_cy_dif1.o > src/mlucas_sse2-radix11_ditN_cy_dif1.o > src/mlucas_sse2-radix120_ditN_cy_dif1.o > src/mlucas_sse2-radix128_ditN_cy_dif1.o > src/mlucas_sse2-radix12_ditN_cy_dif1.o > src/mlucas_sse2-radix13_ditN_cy_dif1.o > src/mlucas_sse2-radix144_ditN_cy_dif1.o > src/mlucas_sse2-radix14_ditN_cy_dif1.o > src/mlucas_sse2-radix15_ditN_cy_dif1.o > src/mlucas_sse2-radix160_ditN_cy_dif1.o > src/mlucas_sse2-radix16_dif_dit_pass.o > src/mlucas_sse2-radix16_ditN_cy_dif1.o > src/mlucas_sse2-radix16_dyadic_square.o > src/mlucas_sse2-radix16_pairFFT_mul.o > src/mlucas_sse2-radix16_wrapper_ini.o > src/mlucas_sse2-radix16_wrapper_square.o > src/mlucas_sse2-radix176_ditN_cy_dif1.o > src/mlucas_sse2-radix18_ditN_cy_dif1.o > src/mlucas_sse2-radix192_ditN_cy_dif1.o > src/mlucas_sse2-radix208_ditN_cy_dif1.o > src/mlucas_sse2-radix20_ditN_cy_dif1.o > src/mlucas_sse2-radix224_ditN_cy_dif1.o > src/mlucas_sse2-radix22_ditN_cy_dif1.o > src/mlucas_sse2-radix240_ditN_cy_dif1.o > src/mlucas_sse2-radix24_ditN_cy_dif1.o > src/mlucas_sse2-radix256_ditN_cy_dif1.o > src/mlucas_sse2-radix26_ditN_cy_dif1.o > src/mlucas_sse2-radix288_ditN_cy_dif1.o > src/mlucas_sse2-radix28_ditN_cy_dif1.o > src/mlucas_sse2-radix30_ditN_cy_dif1.o > src/mlucas_sse2-radix31_ditN_cy_dif1.o > src/mlucas_sse2-radix32_dif_dit_pass.o > src/mlucas_sse2-radix32_ditN_cy_dif1.o > src/mlucas_sse2-radix32_dyadic_square.o > src/mlucas_sse2-radix32_wrapper_ini.o > src/mlucas_sse2-radix32_wrapper_square.o > src/mlucas_sse2-radix36_ditN_cy_dif1.o > src/mlucas_sse2-radix4032_ditN_cy_dif1.o > src/mlucas_sse2-radix40_ditN_cy_dif1.o > src/mlucas_sse2-radix44_ditN_cy_dif1.o > src/mlucas_sse2-radix48_ditN_cy_dif1.o > src/mlucas_sse2-radix512_ditN_cy_dif1.o > src/mlucas_sse2-radix52_ditN_cy_dif1.o > src/mlucas_sse2-radix56_ditN_cy_dif1.o > src/mlucas_sse2-radix5_ditN_cy_dif1.o > src/mlucas_sse2-radix60_ditN_cy_dif1.o > src/mlucas_sse2-radix63_ditN_cy_dif1.o > src/mlucas_sse2-radix64_ditN_cy_dif1.o > src/mlucas_sse2-radix6_ditN_cy_dif1.o > src/mlucas_sse2-radix72_ditN_cy_dif1.o > src/mlucas_sse2-radix768_ditN_cy_dif1.o > src/mlucas_sse2-radix7_ditN_cy_dif1.o > src/mlucas_sse2-radix80_ditN_cy_dif1.o > src/mlucas_sse2-radix88_ditN_cy_dif1.o > src/mlucas_sse2-radix8_dif_dit_pass.o > src/mlucas_sse2-radix8_ditN_cy_dif1.o > src/mlucas_sse2-radix960_ditN_cy_dif1.o > src/mlucas_sse2-radix96_ditN_cy_dif1.o > src/mlucas_sse2-radix992_ditN_cy_dif1.o > src/mlucas_sse2-radix9_ditN_cy_dif1.o src/mlucas_sse2-rng_isaac.o > src/mlucas_sse2-test_fft_radix.o src/mlucas_sse2-threadpool.o > src/mlucas_sse2-twopmodq.o src/mlucas_sse2-twopmodq100.o > src/mlucas_sse2-twopmodq128.o src/mlucas_sse2-twopmodq128_96.o > src/mlucas_sse2-twopmodq160.o src/mlucas_sse2-twopmodq192.o > src/mlucas_sse2-twopmodq256.o src/mlucas_sse2-twopmodq64_test.o > src/mlucas_sse2-twopmodq80.o src/mlucas_sse2-twopmodq96.o > src/mlucas_sse2-types.o src/mlucas_sse2-util.o -lm > /usr/bin/ld: /usr/bin/ld: DWARF error: could not find abbrev number 222 > /tmp/ccxqWoW9.ltrans26.ltrans.o: in function `radix16_dyadic_square': > :(.text+0x1213e): undefined reference to > `SSE2_RADI16_CALC_TWIDDLES_1_2_4_8_13' > collect2: error: ld returned 1 exit status > make[1]: *** [Makefile:3685: mlucas-sse2] Error 1 > > > SSE i not part of the i386 baseline. signature.asc Description: PGP signature
Bug#920834: mlucas: FTBFS and baseline vioiation on i386
Hello Adrian Bunk, I figure out what's the problem. There's a typo in upstream src: s/SSE2_RADI16_CALC_TWIDDLES_1_2_4_8_13/SSE2_RADIX16_CALC_TWIDDLES_1_2_4_8_13/g should fix the problem. I'll upload a new version to mentor, ask for sponsorship again and see how everything goes. Cheers, Alex Alex Vong writes: > Dear Adrian Bunk, > > Regarding FTBFS, I've commented it at <https://bugs.debian.org/920835>. > > Regarding baseline vioiation on i386, the autotool build system builds 2 > versions of the binary: generic-c and SSE2, and install it to > libexecdir. Then the wrapper script selects the right binary at > run-time. Does this approach satifies the current policy? > > Cheers, > Alex > > Adrian Bunk writes: > >> Source: mlucas >> Version: 17.1-1 >> Severity: serious >> Tags: ftbfs >> >> https://buildd.debian.org/status/fetch.php?pkg=mlucas&arch=i386&ver=17.1-1&stamp=1548777459&raw=0 >> >> ... >> gcc -pthread -O2 -O3 -Ofast -flto -pipe -ftree-vectorize >> -floop-nest-optimize -fomit-frame-pointer -g -g3 >> -fstack-protector-strong -fstack-clash-protection -mmitigate-rop >> -fwrapv -m32 -msse2 >> -fdebug-prefix-map=/<>=. -fstack-protector-strong >> -Wformat -Werror=format-security -Wl,-z,relro -Wl,-z,now -o >> mlucas-sse2 src/mlucas_sse2-Mlucas.o src/mlucas_sse2-br.o >> src/mlucas_sse2-dft_macro.o src/mlucas_sse2-factor.o >> src/mlucas_sse2-fermat_mod_square.o src/mlucas_sse2-fgt_m61.o >> src/mlucas_sse2-gcd_lehmer.o src/mlucas_sse2-getRealTime.o >> src/mlucas_sse2-get_cpuid.o src/mlucas_sse2-get_fft_radices.o >> src/mlucas_sse2-get_fp_rnd_const.o >> src/mlucas_sse2-get_preferred_fft_radix.o src/mlucas_sse2-imul_macro.o >> src/mlucas_sse2-mers_mod_square.o src/mlucas_sse2-mi64.o >> src/mlucas_sse2-pairFFT_mul.o src/mlucas_sse2-qfloat.o >> src/mlucas_sse2-radix1008_ditN_cy_dif1.o >> src/mlucas_sse2-radix1024_ditN_cy_dif1.o >> src/mlucas_sse2-radix104_ditN_cy_dif1.o >> src/mlucas_sse2-radix10_ditN_cy_dif1.o >> src/mlucas_sse2-radix112_ditN_cy_dif1.o >> src/mlucas_sse2-radix11_ditN_cy_dif1.o >> src/mlucas_sse2-radix120_ditN_cy_dif1.o >> src/mlucas_sse2-radix128_ditN_cy_dif1.o >> src/mlucas_sse2-radix12_ditN_cy_dif1.o >> src/mlucas_sse2-radix13_ditN_cy_dif1.o >> src/mlucas_sse2-radix144_ditN_cy_dif1.o >> src/mlucas_sse2-radix14_ditN_cy_dif1.o >> src/mlucas_sse2-radix15_ditN_cy_dif1.o >> src/mlucas_sse2-radix160_ditN_cy_dif1.o >> src/mlucas_sse2-radix16_dif_dit_pass.o >> src/mlucas_sse2-radix16_ditN_cy_dif1.o >> src/mlucas_sse2-radix16_dyadic_square.o >> src/mlucas_sse2-radix16_pairFFT_mul.o >> src/mlucas_sse2-radix16_wrapper_ini.o >> src/mlucas_sse2-radix16_wrapper_square.o >> src/mlucas_sse2-radix176_ditN_cy_dif1.o >> src/mlucas_sse2-radix18_ditN_cy_dif1.o >> src/mlucas_sse2-radix192_ditN_cy_dif1.o >> src/mlucas_sse2-radix208_ditN_cy_dif1.o >> src/mlucas_sse2-radix20_ditN_cy_dif1.o >> src/mlucas_sse2-radix224_ditN_cy_dif1.o >> src/mlucas_sse2-radix22_ditN_cy_dif1.o >> src/mlucas_sse2-radix240_ditN_cy_dif1.o >> src/mlucas_sse2-radix24_ditN_cy_dif1.o >> src/mlucas_sse2-radix256_ditN_cy_dif1.o >> src/mlucas_sse2-radix26_ditN_cy_dif1.o >> src/mlucas_sse2-radix288_ditN_cy_dif1.o >> src/mlucas_sse2-radix28_ditN_cy_dif1.o >> src/mlucas_sse2-radix30_ditN_cy_dif1.o >> src/mlucas_sse2-radix31_ditN_cy_dif1.o >> src/mlucas_sse2-radix32_dif_dit_pass.o >> src/mlucas_sse2-radix32_ditN_cy_dif1.o >> src/mlucas_sse2-radix32_dyadic_square.o >> src/mlucas_sse2-radix32_wrapper_ini.o >> src/mlucas_sse2-radix32_wrapper_square.o >> src/mlucas_sse2-radix36_ditN_cy_dif1.o >> src/mlucas_sse2-radix4032_ditN_cy_dif1.o >> src/mlucas_sse2-radix40_ditN_cy_dif1.o >> src/mlucas_sse2-radix44_ditN_cy_dif1.o >> src/mlucas_sse2-radix48_ditN_cy_dif1.o >> src/mlucas_sse2-radix512_ditN_cy_dif1.o >> src/mlucas_sse2-radix52_ditN_cy_dif1.o >> src/mlucas_sse2-radix56_ditN_cy_dif1.o >> src/mlucas_sse2-radix5_ditN_cy_dif1.o >> src/mlucas_sse2-radix60_ditN_cy_dif1.o >> src/mlucas_sse2-radix63_ditN_cy_dif1.o >> src/mlucas_sse2-radix64_ditN_cy_dif1.o >> src/mlucas_sse2-radix6_ditN_cy_dif1.o >> src/mlucas_sse2-radix72_ditN_cy_dif1.o >> src/mlucas_sse2-radix768_ditN_cy_dif1.o >> src/mlucas_sse2-radix7_ditN_cy_dif1.o >> src/mlucas_sse2-radix80_ditN_cy_dif1.o >> src/mlucas_sse2-radix88_ditN_cy_dif1.o >> src/mlucas_sse2-radix8_dif_dit_pass.o >> src/mlucas_sse2-radix8_ditN_cy_dif1.o >> src/mlucas_sse2-radix960_ditN_cy_dif1.o >> src/mlucas_sse2-radix96_ditN_cy_dif1.o
Bug#920834: mlucas: FTBFS on i386
# I am changing the title since I think the i386 baseline is in fact not # violated. retitle 920834 mlucas: FTBFS on i386 thanks Alex Vong writes: > Hello Adrian Bunk, > > I figure out what's the problem. There's a typo in upstream src: > > s/SSE2_RADI16_CALC_TWIDDLES_1_2_4_8_13/SSE2_RADIX16_CALC_TWIDDLES_1_2_4_8_13/g > > should fix the problem. > > I'll upload a new version to mentor, ask for sponsorship again and see > how everything goes. > > Cheers, > Alex > > Alex Vong writes: > >> Dear Adrian Bunk, >> >> Regarding FTBFS, I've commented it at <https://bugs.debian.org/920835>. >> >> Regarding baseline vioiation on i386, the autotool build system builds 2 >> versions of the binary: generic-c and SSE2, and install it to >> libexecdir. Then the wrapper script selects the right binary at >> run-time. Does this approach satifies the current policy? >> >> Cheers, >> Alex >> >> Adrian Bunk writes: >> >>> Source: mlucas >>> Version: 17.1-1 >>> Severity: serious >>> Tags: ftbfs >>> >>> https://buildd.debian.org/status/fetch.php?pkg=mlucas&arch=i386&ver=17.1-1&stamp=1548777459&raw=0 >>> >>> ... >>> gcc -pthread -O2 -O3 -Ofast -flto -pipe -ftree-vectorize >>> -floop-nest-optimize -fomit-frame-pointer -g -g3 >>> -fstack-protector-strong -fstack-clash-protection -mmitigate-rop >>> -fwrapv -m32 -msse2 >>> -fdebug-prefix-map=/<>=. -fstack-protector-strong >>> -Wformat -Werror=format-security -Wl,-z,relro -Wl,-z,now -o >>> mlucas-sse2 src/mlucas_sse2-Mlucas.o src/mlucas_sse2-br.o >>> src/mlucas_sse2-dft_macro.o src/mlucas_sse2-factor.o >>> src/mlucas_sse2-fermat_mod_square.o src/mlucas_sse2-fgt_m61.o >>> src/mlucas_sse2-gcd_lehmer.o src/mlucas_sse2-getRealTime.o >>> src/mlucas_sse2-get_cpuid.o src/mlucas_sse2-get_fft_radices.o >>> src/mlucas_sse2-get_fp_rnd_const.o >>> src/mlucas_sse2-get_preferred_fft_radix.o src/mlucas_sse2-imul_macro.o >>> src/mlucas_sse2-mers_mod_square.o src/mlucas_sse2-mi64.o >>> src/mlucas_sse2-pairFFT_mul.o src/mlucas_sse2-qfloat.o >>> src/mlucas_sse2-radix1008_ditN_cy_dif1.o >>> src/mlucas_sse2-radix1024_ditN_cy_dif1.o >>> src/mlucas_sse2-radix104_ditN_cy_dif1.o >>> src/mlucas_sse2-radix10_ditN_cy_dif1.o >>> src/mlucas_sse2-radix112_ditN_cy_dif1.o >>> src/mlucas_sse2-radix11_ditN_cy_dif1.o >>> src/mlucas_sse2-radix120_ditN_cy_dif1.o >>> src/mlucas_sse2-radix128_ditN_cy_dif1.o >>> src/mlucas_sse2-radix12_ditN_cy_dif1.o >>> src/mlucas_sse2-radix13_ditN_cy_dif1.o >>> src/mlucas_sse2-radix144_ditN_cy_dif1.o >>> src/mlucas_sse2-radix14_ditN_cy_dif1.o >>> src/mlucas_sse2-radix15_ditN_cy_dif1.o >>> src/mlucas_sse2-radix160_ditN_cy_dif1.o >>> src/mlucas_sse2-radix16_dif_dit_pass.o >>> src/mlucas_sse2-radix16_ditN_cy_dif1.o >>> src/mlucas_sse2-radix16_dyadic_square.o >>> src/mlucas_sse2-radix16_pairFFT_mul.o >>> src/mlucas_sse2-radix16_wrapper_ini.o >>> src/mlucas_sse2-radix16_wrapper_square.o >>> src/mlucas_sse2-radix176_ditN_cy_dif1.o >>> src/mlucas_sse2-radix18_ditN_cy_dif1.o >>> src/mlucas_sse2-radix192_ditN_cy_dif1.o >>> src/mlucas_sse2-radix208_ditN_cy_dif1.o >>> src/mlucas_sse2-radix20_ditN_cy_dif1.o >>> src/mlucas_sse2-radix224_ditN_cy_dif1.o >>> src/mlucas_sse2-radix22_ditN_cy_dif1.o >>> src/mlucas_sse2-radix240_ditN_cy_dif1.o >>> src/mlucas_sse2-radix24_ditN_cy_dif1.o >>> src/mlucas_sse2-radix256_ditN_cy_dif1.o >>> src/mlucas_sse2-radix26_ditN_cy_dif1.o >>> src/mlucas_sse2-radix288_ditN_cy_dif1.o >>> src/mlucas_sse2-radix28_ditN_cy_dif1.o >>> src/mlucas_sse2-radix30_ditN_cy_dif1.o >>> src/mlucas_sse2-radix31_ditN_cy_dif1.o >>> src/mlucas_sse2-radix32_dif_dit_pass.o >>> src/mlucas_sse2-radix32_ditN_cy_dif1.o >>> src/mlucas_sse2-radix32_dyadic_square.o >>> src/mlucas_sse2-radix32_wrapper_ini.o >>> src/mlucas_sse2-radix32_wrapper_square.o >>> src/mlucas_sse2-radix36_ditN_cy_dif1.o >>> src/mlucas_sse2-radix4032_ditN_cy_dif1.o >>> src/mlucas_sse2-radix40_ditN_cy_dif1.o >>> src/mlucas_sse2-radix44_ditN_cy_dif1.o >>> src/mlucas_sse2-radix48_ditN_cy_dif1.o >>> src/mlucas_sse2-radix512_ditN_cy_dif1.o >>> src/mlucas_sse2-radix52_ditN_cy_dif1.o >>> src/mlucas_sse2-radix56_ditN_cy_dif1.o >>> src/mlucas_sse2-radix5_ditN_cy_dif1.o >>> src/mlucas_sse2-radix60_ditN_cy_dif1.o >
Bug#920835: mlucas FTBFS on !amd64: test failures
Thank you, people! I will upload a new version to fix this and the undefined macro error in the powerpc build. Now the remaining problems are that the SIMD binary in i386 and arm64 are not working, as hinted by the messages: INFO: CPU supports SSE2 instruction set, but using scalar floating-point build. and INFO: CPU supports ARMv8 advanced-SIMD instruction set, but using scalar floating-point build. I downloaded the built SIMD binaries and indeed they segfault when they run. The build still succeeds because there's a fallback generic c version, but it is slow... Maybe I'll ask upstream to investigate. Cheers, Alex Juhani Numminen writes: > On Wed, 30 Jan 2019 05:27:48 +0800 Alex Vong wrote: >> Hello Adrian Bunk, >> >> The test log is not useful at all. I want to add a patch to enable >> verbose test log and let it build again to identify the issues. > > But the error message does point to a funny line that appears to > try to execute a directory... > >> > ./tests/..//mlucas: 149: exec: ./tests/../: Permission denied >> > FAIL tests/spot-check (exit status: 126) > > https://sources.debian.org/src/mlucas/17.1-2/scripts/mlucas.in/#L149 > > exec "$DIRNAME" "$@" > > Maybe there should be an executable name after DIRNAME? > > > Regards, > Juhani signature.asc Description: PGP signature
Bug#943462: [polkit-kde-agent-1] Fails to start with elogind
Package: polkit-kde-agent-1 Version: 4:5.14.5-1 Severity: serious --- Please enter the report below this line. --- I'm using elogind 239.3+20190131-1+debian1 and the agent fails to start at the kde launch with the following diagnostics: === New PolkitAgentListener 0xbfaf9ca0 Adding new listener PolkitQt1::Agent::Listener(0x7fb730017260) for 0xbfaf9ca0 Listener online "Cannot create unix session: No session for pid 17113" ** (process:17113): CRITICAL **: 06:38:20.880: polkit_agent_listener_register_with_options: assertion 'POLKIT_IS_SUBJECT (subject)' failed "Cannot register authentication agent!" Authentication agent result: false Couldn't register listener! === (This may or may not have connection to bug #850778 in plasma-desktop, which seems to be the issue with polkit not recognizing a logged-in user.) --- System information. --- Architecture: Kernel: Linux 5.2.17-bootes2-iommu-p-1000 Debian Release: 10.1 991 stable security.debian.org 991 stable ftp.fi.debian.org 990 buster-backports ftp.debian.org 99 stable-backports www.deb-multimedia.org 99 stable www.deb-multimedia.org 500 stable dl.google.com 500 stable deb.torproject.org 100 testing ftp.fi.debian.org --- Package information. --- Depends(Version) | Installed -+- policykit-1 | 0.105-26 libc6 (>= 2.4) | libkf5coreaddons5 (>= 4.100.0) | libkf5crash5 (>= 4.96.0) | libkf5dbusaddons5(>= 4.97.0) | libkf5i18n5 (>= 4.97.0) | libkf5iconthemes5(>= 4.96.0) | libkf5widgetsaddons5 (>= 4.96.0) | libkf5windowsystem5 (>= 4.96.0) | libpolkit-qt5-1-1 (>= 0.112.0) | libqt5core5a (>= 5.11.0~rc1) | libqt5dbus5 (>= 5.11.0~) | libqt5gui5 (>= 5.11.0~) | libqt5widgets5 (>= 5.11.0~) | libstdc++6(>= 4.1.1) | Package's Recommends field is empty. Package's Suggests field is empty.
Bug#903793: libgmap1-dev: broken symlink: /usr/lib/x86_64-linux-gnu/libgmap.so -> libgmap.so.1.0.0
Hi Andreas, On 07/17/2018 08:19 AM, Andreas Tille wrote: > Hi Alexandre, > > On Sat, Jul 14, 2018 at 11:41:01PM +0200, Andreas Beckmann wrote: >> Depends: gmap (= 2017-11-15-1) | libgmap1 (= 2017-11-15-1) >> >> which does not sound like a good idea if gmap does not provide the required >> shared library. > > I've fixed this in Git and also updated to the latest upstream version. > Unfortunately the latest upstream does not build the lib any more even > after trying > > override_dh_auto_configure: > - dh_auto_configure -- --enable-shared --with-gmapdb=/var/cache/gmap \ > + dh_auto_configure -- --enable-lib --enable-shared > --with-gmapdb=/var/cache/gmap \ > --bindir=/usr/lib/gmap $(EXTRA_CONFIGURE_ARGS) > > Since you are way more comfortable with this package would you please > have a look? I have no idea whether the idea is needed at all thus > I stop fiddling around here. > > Kind regards > > Andreas. > I plan to drop libgmap1[0], as there is no use cases so far. (also no rdepends). Was about to do it long time ago but failed due to ENOTIME... I'll try to look later today on the package and may be upload the new version. Best regards, Alex [0] https://alioth-lists.debian.net/pipermail/debian-med-packaging/2018-June/063340.html
Bug#902820: [Debian-med-packaging] Bug#902820: gmap: FTBFS on stretch/amd64 if CPU has SSE2 and nothing more
> AFAIK on Debian/amd64 only SSE2 is allowed to be assumed by default. > > I tried to compare my build logs with official ones, but there is none: > > https://buildd.debian.org/status/package.php?p=gmap > > (( Could you please consider source-only uploads? i.e. "dpkg-buildpackage -S" > )). I just uploaded a new version 2018-07-04-1, but forgot to build source only upload. I'll do it for the next upload. Meanwhile could you please try to build the new version? > > In either case, I'm putting my failed build logs here in case you need > them, they were made with sbuild on different virtual machines running > Debian stretch: > > https://people.debian.org/~sanvila/build-logs/gmap/ > > (Note: All the failures seem to be related to detection of CPU features, > but since the machines are diverse, the failures are not always the same). > > Thanks. > > ___ > Debian-med-packaging mailing list > debian-med-packag...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging > Cool, thank you for the details. I'll be away for the next 3 weeks, so CC-ing debian-med, may be somebody else will have time for the package. Best regards, Alex
Bug#900533: chromium 67.0.3396.62-1: youtube video, gif's, html5, and movies no longer work
I confirm this bug in release 67.0.3396.87-1 youtube video worked but html5, and movies no longer work Install the older version from stable (stretch) - all worked fine -- Sincerely Oleksandr Shtalinberg
Bug#871247: alsa-base: Front Panel Jack for play audio not working
Package: alsa-base Version: 1.0.27+1 Severity: serious Tags: newcomer Justification: Unknown Dear Maintainer, Sound from back panel is working. Sound from front panel is not working. * What led up to the situation? Upgrade from debian 8 to 9.1. * What exactly did you do (or not do) that was effective (or ineffective)? alsactl init change in alsamixer * What was the outcome of this action? nothing cat /proc/asound/cards 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xf721 irq 46 1 [NVidia ]: HDA-Intel - HDA NVidia HDA NVidia at 0xf708 irq 17 lspci | grep -i audio 00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 05) 01:00.1 Audio device: NVIDIA Corporation GK107 HDMI Audio Controller (rev a1) -- System Information: Debian Release: 9.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages alsa-base depends on: ii dpkg 1.18.24 ii kmod 23-2 alsa-base recommends no packages. alsa-base suggests no packages. -- no debconf information
Bug#871629: thunderbird UI unusable with many widgets not drawn
Package: thunderbird Version: 1:52.2.1-4+b1 Followup-For: Bug #871629 Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.11.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages thunderbird depends on: ii debianutils 4.8.1.1 ii fontconfig2.12.3-0.2 ii libatk1.0-0 2.24.0-1 ii libc6 2.24-12 ii libcairo-gobject2 1.14.10-1 ii libcairo2 1.14.10-1 ii libdbus-1-3 1.11.16+really1.10.22-1 ii libdbus-glib-1-2 0.108-2 ii libevent-2.1-62.1.8-stable-4 ii libffi6 3.2.1-6 ii libfontconfig12.12.3-0.2 ii libfreetype6 2.8-0.2 ii libgcc1 1:7.1.0-10 ii libgdk-pixbuf2.0-02.36.5-2 ii libglib2.0-0 2.53.4-3 ii libgtk-3-03.22.17-1 ii libhunspell-1.6-0 1.6.1-2 ii libpango-1.0-01.40.6-1 ii libpangocairo-1.0-0 1.40.6-1 ii libpangoft2-1.0-0 1.40.6-1 ii libpixman-1-0 0.34.0-1 ii libstartup-notification0 0.12-4+b2 ii libstdc++67.1.0-10 ii libvpx4 1.6.1-3 ii libx11-6 2:1.6.4-3 ii libx11-xcb1 2:1.6.4-3 ii libxcb-shm0 1.12-1 ii libxcb1 1.12-1 ii libxcomposite11:0.4.4-2 ii libxdamage1 1:1.1.4-2+b3 ii libxext6 2:1.3.3-1+b2 ii libxfixes31:5.0.3-1 ii libxrender1 1:0.9.10-1 ii libxt61:1.1.5-1 ii psmisc23.1-1 ii x11-utils 7.7+3+b1 ii zlib1g1:1.2.8.dfsg-5 Versions of packages thunderbird recommends: ii hunspell-en-gb [hunspell-dictionary] 1:5.2.5-1 ii hunspell-en-us [hunspell-dictionary] 20070829-7 ii lightning 1:52.2.1-4+b1 Versions of packages thunderbird suggests: pn apparmor ii fonts-lyx 2.2.3-1 ii libgssapi-krb5-2 1.15.1-2 Can confirm. Initial rending of windows appear blank but when rolling mouse over it artifacts begin to be drawn. Makes Thunderbird unsable. However when running the official Mozilla build http://download.cdn.mozilla.net/pub/thunderbird/releases/52.2.1/linux-x86_64/en- GB/thunderbird-52.2.1.tar.bz2 on the same system, no such errors occur. Suggest you compare the two builds and discover what has changed.
Bug#1074912: dircproxy build failures
severity 1074912 important stop As far as I can tell, this bug is about a build failure where it builds successfully with a prior version of gcc, but not with a proposed new version. Although that's a concern, I cannot agree that it warrants a serious bug against dircproxy, please correct me if I am wrong. -- Alex Pennace, a...@pennace.org
Bug#1078829: linux-image-amd64: 6.10.3-1 fails to install with Nvidia DKMS build error
Glad to hear, Salwatore! I was wondering which package to report this to but since the Nvidia drivers are actually working while updating this package wasn't I decided to go with this. If the maintainers want to keep this open, I'll try to report back in, when the fix hits testing. Cheers and dove a great weekend On Fri, 16 Aug 2024 at 18:59, Salvatore Bonaccorso wrote: > Hi Alex, > > On Fri, Aug 16, 2024 at 06:39:59PM -0300, Alex Henry wrote: > > Package: linux-image-amd64 > > Version: 6.10.3-1 > > Severity: important > > X-Debbugs-Cc: tuk...@gmail.com > > > > Hello! I ran into some trouble while casually trying to update > `linux-image- > > amd64` and `linux-headers-amd64` during a routine system update. > > > > My current image is `linux-image-6.9.7` (6.9.7-1). There are also some > older > > images and headers marked as "auto" on Aptitude. > > > > My installed `nvidia-driver` package is version 535.183.01-1. I have > tripled- > > checked all installed Nvidia packages are fully up-ta-date in > Debian-testing. > > > > I have also updated all devel- and libdevel-category packages to make > sure this > > isn't an issue related to GCC, make... > > > > Everything is working normally other than the failure to upgrade > `linux-image- > > amd64`. > > > > Logs: > > > > - Aptitude output: > > https://gist.github.com/tukkek/863f4da63d925a50d3c7b49c33a4859f > > - `/var/lib/dkms/nvidia-current/535.183.01/build/make.log`: > > https://gist.github.com/tukkek/d91b07ad7792735381571f387aed13cd > > - Installed packages: > > https://gist.github.com/tukkek/2aa1b4407f9bcf7aa17053bcf43a2d4f > > > > The only error I could find was "implicit declaration of function > ‘follow_pfn’" > > in the DKMS log's line 1371: > > > https://gist.github.com/tukkek/d91b07ad7792735381571f387aed13cd#file-make- > > log-L1371 > > > > I'm not very familiar with kernel stuff and might have easily missed > something > > so I'll let you geniuses take a better look. Let me know if I can > provide any > > further information or help. > > > > Big thanks to all involved in helping maintain the best libre operating > system > > there is! Cheers! > > See #1077841, which is the issue for src:nvidia-graphics-drivers. It > is fixed in 535.183.06-1 in unstable. > > Regards, > Salvatore >
Bug#1079457: cups: Dependencies prevent installation
Package: cups Version: 2.4.10-1 amd64 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? Fresh installation of sid onto clean disk using minimal Bookworm install, altering sources.list, apt update, apt upgrade, tasksel desktop and xfce4 apt install cups fails because of a version conflict: libcupsfilters2-common : Breaks: cups-filters (< 2.0~) but 1.28.17-4.1+b1 is to be installed -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.10.6-amd64 (SMP w/4 CPU threads; PREEMPT) 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 cups depends on: ii cups-client 2.4.10-1 ii cups-common 2.4.10-1 pn cups-core-drivers pn cups-daemon pn cups-filters pn cups-ppdc pn cups-server-common ii debconf [debconf-2.0] 1.5.87 ii ghostscript 10.03.1~dfsg-2 ii libavahi-client3 0.8-13+b2 ii libavahi-common3 0.8-13+b2 ii libc6 2.39-7 ii libcups2t64 2.4.10-1 ii libgcc-s1 14.2.0-3 ii libstdc++6 14.2.0-3 ii libusb-1.0-0 2:1.0.27-1 ii poppler-utils 24.08.0-2 ii procps 2:4.0.4-5 Versions of packages cups recommends: ii avahi-daemon 0.8-13+b2 ii colord 1.4.7-1+b1 Versions of packages cups suggests: pn cups-bsd pn cups-pdf pn foomatic-db-compressed-ppds | foomatic-db pn smbclient ii udev 256.5-1 -- PGP A702C2BE2E96ADE7
Bug#1074912: dircprxy / gcc-14 issue
severity 1074912 important stop Well, when I wrote my message of August 6, I had hoped that someone would actually offer an explanation for why a compiler issue is a dircproxy issue :) I'm not against this being set to serious, but it would be nice if someone could articulate why this is a dircproxy problem when the issue happens with gcc-14, but not with gcc-13. -- Alex Pennace, a...@pennace.org
Bug#942365: libgtk2-perl: Package uninstallable
Source: libgtk2-perl Version: 2:1.24993-1 Followup-For: Bug #942365 Dear Maintainer, * What led up to the situation? I'm trying to run obmenu-generator (for openbox) that requires libgtk2-perl * What exactly did you do (or not do) that was effective (or ineffective)? apt install libgtk2-perl * What was the outcome of this action? libgtk2-perl : Depends: perlapi-5.28.1 but it is not installable apt search perlapi Sorting... Done Full Text Search... Done * What outcome did you expect instead? -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-4-amd64 (SMP w/8 CPU cores) 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 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#952180: marked as pending in libtest-xml-simple-perl
Control: tag -1 pending Hello, Bug #952180 in libtest-xml-simple-perl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/perl-team/modules/packages/libtest-xml-simple-perl/-/commit/6a0264e9dff64fa85a366527ca4362dce4817fe1 Patch t/03valid.t FTBFS bug (Closes: #952180) Thanks: Lucas Nussbaum (this message was generated automatically) -- Greetings https://bugs.debian.org/952180
Bug#982850: duperemove: first run fails errror 13?
Package: duperemove Version: 0.11.2-3 Severity: grave Tags: upstream Justification: renders package unusable X-Debbugs-Cc: de...@roosoft.ltd.uk Dear Maintainer, So running duperemove for the first run. duperemove -r -A -h --skip-zeroes --hashfile=/var/cache/duperemove-home-user /home/user/ At the end this happened. Total files: 2261918 Total extent hashes: 4666300 create_indexes()/45330: Database error 13 while creating database index: database or disk is full the folder is not full df -h /var Filesystem Size Used Avail Use% Mounted on /dev/mapper/pulseforn--vg-var 9.4G 7.4G 1.8G 81% /var ls -lah /var/cache/duperemove-home-user* -rw-r--r-- 1 root root 5.0G Feb 13 17:04 /var/cache/duperemove-home-user -rw-r--r-- 1 root root 4.6K Feb 13 17:03 /var/cache/duperemove-home-user- journal EDIT: For reference. Platform: Debian 10/Testing Kernel: 5.10.0-3-amd64 #1 SMP Debian 5.10.13-1 (2021-02-06) x86_64 GNU/Linux duperemove v0.11.2 btrfs-progs v5.10.1 -- System Information: Debian Release: bullseye/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-3-amd64 (SMP w/16 CPU threads) Kernel taint flags: TAINT_WARN, 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 duperemove depends on: ii libc6 2.31-9 ii libglib2.0-0 2.66.6-2 ii libsqlite3-0 3.34.1-1 duperemove recommends no packages. duperemove suggests no packages. -- debconf-show failed
Bug#917713: [Debian-med-packaging] Bug#917713: pyscanfcs: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 3.7 returned exit code 13
On 12/30/18 3:58 PM, Andreas Tille wrote: > Hi, > > only time for a short notice but that's actually a consequence of > #917353. > > Kind regards > > Andreas. > Hi Andreas, thank you for the update, do you think it will make sense to re-upload pyscanfcs to trigger rebuild? Best, Alex
Bug#855541: purple-matrix: Not ready for release yet
On Mon, 20 Feb 2017 00:12:35 +0100 Kurt Roeckx wrote: > Package: purple-matrix > Version: 0.0.0+git20170105-1 > Severity: serious > > Hi, > > I think this version shouldn't be shipped with the next > release. Like the description says, it's "somewhat alpha". > > It works some times, but then stops working, it crashes, > and so on. I've used the package purple-matrix on Debian 10 since at least 6 months through Pidgin. It's not a perfect tool, have issues but in my opinion it is usable. Sometimes purple-matrix is disconnected or makes Pidgin to crash but it's quite rare. It's sufficient to restart Pidgin to make it working again. I have two points why I think we should have it into next stable: * This is very difficult for a stable user to use purple-matrix. In my case, I have had to rebuilt the package due to dependencies and it's clearly something not easy for all. * As a visual-impaired person, purple-matrix through Pidgin is the most accessible Matrix client I've used. There are still reasons why we would like to keep it in unstable: * There are no commits in 2020 * The project doesn't publish new release and "just" push commits In my humble opinion, the drawbacks of keeping it to unstable are more important. @Kurt: I let you decide if you prefer to keep close or not but since the creation of this issue in 2017 many commits come to the project. Thanks in advance.
Bug#970753: apertium-ind-zlm: Wrong e-mail address in Maintainer field
Package: apertium-ind-zlm Version: 0.1.2-2 Severity: serious Usertags: alioth-lists.debian.org X-Debbugs-Cc: kar...@debian.org, t...@didriksen.cc The Maintainer of this package uses the alioth-lists.debian.org domain, which does not exist. This breaks policy §3.3[1] that requires a working e-mail address. You should be using the alioth-lists.debian.net domain instead. After reporting[2] the issue to debian-science-maintainers list, I'm filing this bug as suggested[3] there. Cheers, Alex [1] https://www.debian.org/doc/debian-policy/ch-binary.html#s-maintainer [2] https://alioth-lists.debian.net/pipermail/debian-science-maintainers/2020-September/085266.html [3] https://alioth-lists.debian.net/pipermail/debian-science-maintainers/2020-September/085350.html -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Alex Muntada ⢿⡄⠘⠷⠚⠋ Debian Developer 🍥 log.alexm.org ⠈⠳⣄ signature.asc Description: PGP signature
Bug#970754: e-antic: Wrong e-mail address in Maintainer field
Package: e-antic Version: 0.1.5+ds-2.1 Severity: serious Usertags: alioth-lists.debian.org X-Debbugs-Cc: plugw...@raspbian.org, calcu...@rezozer.net The Maintainer of this package uses the alioth-lists.debian.org domain, which does not exist. This breaks policy §3.3[1] that requires a working e-mail address. You should be using the alioth-lists.debian.net domain instead. After reporting[2] the issue to debian-science-maintainers list, I'm filing this bug as suggested[3] there. Cheers, Alex [1] https://www.debian.org/doc/debian-policy/ch-binary.html#s-maintainer [2] https://alioth-lists.debian.net/pipermail/debian-science-maintainers/2020-September/085266.html [3] https://alioth-lists.debian.net/pipermail/debian-science-maintainers/2020-September/085350.html -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Alex Muntada ⢿⡄⠘⠷⠚⠋ Debian Developer 🍥 log.alexm.org ⠈⠳⣄ signature.asc Description: PGP signature
Bug#970756: gap-openmath: Wrong e-mail address in Maintainer field
Package: gap-openmath Version: 11.5.0+ds-1 Severity: serious Usertags: alioth-lists.debian.org X-Debbugs-Cc: calcu...@rezozer.net The Maintainer of this package uses the alioth-lists.debian.org domain, which does not exist. This breaks policy §3.3[1] that requires a working e-mail address. You should be using the alioth-lists.debian.net domain instead. After reporting[2] the issue to debian-science-maintainers list, I'm filing this bug as suggested[3] there. Cheers, Alex [1] https://www.debian.org/doc/debian-policy/ch-binary.html#s-maintainer [2] https://alioth-lists.debian.net/pipermail/debian-science-maintainers/2020-September/085266.html [3] https://alioth-lists.debian.net/pipermail/debian-science-maintainers/2020-September/085350.html -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Alex Muntada ⢿⡄⠘⠷⠚⠋ Debian Developer 🍥 log.alexm.org ⠈⠳⣄ signature.asc Description: PGP signature
Bug#970755: gap-guava: Wrong e-mail address in Maintainer field
Package: gap-guava Version: 3.15+ds-2 Severity: serious Usertags: alioth-lists.debian.org X-Debbugs-Cc: calcu...@rezozer.net The Maintainer of this package uses the alioth-lists.debian.org domain, which does not exist. This breaks policy §3.3[1] that requires a working e-mail address. You should be using the alioth-lists.debian.net domain instead. After reporting[2] the issue to debian-science-maintainers list, I'm filing this bug as suggested[3] there. Cheers, Alex [1] https://www.debian.org/doc/debian-policy/ch-binary.html#s-maintainer [2] https://alioth-lists.debian.net/pipermail/debian-science-maintainers/2020-September/085266.html [3] https://alioth-lists.debian.net/pipermail/debian-science-maintainers/2020-September/085350.html -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Alex Muntada ⢿⡄⠘⠷⠚⠋ Debian Developer 🍥 log.alexm.org ⠈⠳⣄ signature.asc Description: PGP signature
Bug#970757: gap-scscp: Wrong e-mail address in Maintainer field
Package: gap-scscp Version: 2.3.1+ds-1 Severity: serious Usertags: alioth-lists.debian.org X-Debbugs-Cc: calcu...@rezozer.net The Maintainer of this package uses the alioth-lists.debian.org domain, which does not exist. This breaks policy §3.3[1] that requires a working e-mail address. You should be using the alioth-lists.debian.net domain instead. After reporting[2] the issue to debian-science-maintainers list, I'm filing this bug as suggested[3] there. Cheers, Alex [1] https://www.debian.org/doc/debian-policy/ch-binary.html#s-maintainer [2] https://alioth-lists.debian.net/pipermail/debian-science-maintainers/2020-September/085266.html [3] https://alioth-lists.debian.net/pipermail/debian-science-maintainers/2020-September/085350.html -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Alex Muntada ⢿⡄⠘⠷⠚⠋ Debian Developer 🍥 log.alexm.org ⠈⠳⣄ signature.asc Description: PGP signature
Bug#970758: mpfi: Wrong e-mail address in Maintainer field
Package: mpfi Version: 1.5.3+ds-4 Severity: serious Usertags: alioth-lists.debian.org X-Debbugs-Cc: calcu...@rezozer.net, lfou...@debian.org The Maintainer of this package uses the alioth-lists.debian.org domain, which does not exist. This breaks policy §3.3[1] that requires a working e-mail address. You should be using the alioth-lists.debian.net domain instead. After reporting[2] the issue to debian-science-maintainers list, I'm filing this bug as suggested[3] there. Cheers, Alex [1] https://www.debian.org/doc/debian-policy/ch-binary.html#s-maintainer [2] https://alioth-lists.debian.net/pipermail/debian-science-maintainers/2020-September/085266.html [3] https://alioth-lists.debian.net/pipermail/debian-science-maintainers/2020-September/085350.html -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Alex Muntada ⢿⡄⠘⠷⠚⠋ Debian Developer 🍥 log.alexm.org ⠈⠳⣄ signature.asc Description: PGP signature
Bug#970759: normaliz: Wrong e-mail address in Maintainer field
Package: normaliz Version: 3.8.5+ds-1 Severity: serious Usertags: alioth-lists.debian.org X-Debbugs-Cc: calcu...@rezozer.net The Maintainer of this package uses the alioth-lists.debian.org domain, which does not exist. This breaks policy §3.3[1] that requires a working e-mail address. You should be using the alioth-lists.debian.net domain instead. After reporting[2] the issue to debian-science-maintainers list, I'm filing this bug as suggested[3] there. Cheers, Alex [1] https://www.debian.org/doc/debian-policy/ch-binary.html#s-maintainer [2] https://alioth-lists.debian.net/pipermail/debian-science-maintainers/2020-September/085266.html [3] https://alioth-lists.debian.net/pipermail/debian-science-maintainers/2020-September/085350.html -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Alex Muntada ⢿⡄⠘⠷⠚⠋ Debian Developer 🍥 log.alexm.org ⠈⠳⣄ signature.asc Description: PGP signature
Bug#902820: gmap: FTBFS on stretch/amd64 if CPU has SSE2 and nothing more
I believe the bug is fixed in just uploaded version 2018-07-04-3 The package is non-free and thus autobuilding is not enabled. I've asked nonf...@release.debian.org to mark gmap as autobuildable, but haven't got an answer so far. Regards Alex
Bug#902132: falcon: FTBFS since python-networkx version 2.1-1; fails in test suite
Hi Andreas, I've pushed some commits and opened upstream issue[0]. Also it seems that falcon depends on python-future >=0.16.0 which is not yet available - #863215. [0] https://github.com/PacificBiosciences/FALCON/issues/672 Best regards, Alex
Bug#902132: [Debian-med-packaging] Bug#902132: falcon: FTBFS since python-networkx version 2.1-1; fails in test suite
Well, according upstream, current repository is not active anymore: Oh, sorry. We are no longer mirroring our internal FALCON repo here. In fact, I think this Issues board will disappear soon too, in favor of pbbioconda. So I think your source-code is way out of date. Unfortunately, my hands are tied. https://github.com/PacificBiosciences/FALCON/issues/672 I am not sure how to get the source from pbbioconda and if this source is suitable for packaging at all. Best regards, Alex
Bug#903580: aegisub still can't be installed on unstable
Package: aegisub Version: 3.2.2+dfsg-3+b6 Followup-For: Bug #903580 Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I'm trying to install aegisub on a sid machine * What exactly did you do (or not do) that was effective (or ineffective)? apt install aegisub * What was the outcome of this action? The following packages have unmet dependencies: aegisub : Depends: libboost-regex1.62.0 but it is not going to be installed apt install libboost-regex1.62.0 libboost-regex1.62.0 is already the newest version (1.62.0+dfsg-10). * What outcome did you expect instead? to install and run? :-) *** End of the template - remove these template lines *** -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages aegisub depends on: ii libasound2 1.1.6-1 ii libass91:0.14.0-2 ii libboost-filesystem1.62.0 1.62.0+dfsg-10 ii libboost-locale1.62.0 1.62.0+dfsg-10 ii libboost-regex1.62.0 1.62.0+dfsg-10 ii libboost-system1.62.0 1.62.0+dfsg-10 ii libboost-thread1.62.0 1.62.0+dfsg-10 ii libc6 2.27-6 ii libffms2-4 2.23-3+b1 ii libfftw3-double3 3.3.8-2 ii libfontconfig1 2.13.0-5 ii libgcc11:8.2.0-6 ii libgl1 1.1.0-1 ii libgl1-mesa-glx18.1.8-1 ii libhunspell-1.6-0 1.6.2-1+b1 ii libicu57 57.1-9 ii libluajit-5.1-22.1.0~beta3+dfsg-5.1 ii libpulse0 12.2-2 ii libstdc++6 8.2.0-6 ii libwxbase3.0-0v5 3.0.4+dfsg-4 ii libwxgtk3.0-0v53.0.4+dfsg-4 ii zlib1g 1:1.2.11.dfsg-1 aegisub recommends no packages. Versions of packages aegisub suggests: pn aegisub-l10n
Bug#911760: lightdm-gtk-greeter segfault, lightdm restart too fast, can't login to desktop
Package: lightdm Version: 1.26.0-3 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? A system upgrade, a list of the packages upgraded should be attached, I don't see any relation with lightdm but I could be missing something * What exactly did you do (or not do) that was effective (or ineffective)? apt update apt upgrade reboot * What was the outcome of this action? lightdm doesn't start, segfault and restart until systemd stop it * What outcome did you expect instead? the usual login dialog Attached there should be the `journal -xe` segfault, the list of the packages installed by the upgrade, the backtrace of a `gdb lighdm --debug` session. Please let me know how/if I can help with more logs. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lightdm depends on: ii adduser3.118 ii dbus 1.12.10-1 ii debconf [debconf-2.0] 1.5.69 ii libaudit1 1:2.8.4-2 ii libc6 2.27-6 ii libgcrypt201.8.3-1 ii libglib2.0-0 2.58.1-2 ii libpam-systemd 239-10 ii libpam0g 1.1.8-3.8 ii libxcb11.13.1-1 ii libxdmcp6 1:1.1.2-3 ii lightdm-gtk-greeter [lightdm-greeter] 2.0.5-1 ii lsb-base 9.20170808 Versions of packages lightdm recommends: ii xserver-xorg 1:7.7+19 Versions of packages lightdm suggests: pn accountsservice ii upower 0.99.8-2 ii xserver-xephyr 2:1.20.1-5 -- Configuration Files: /etc/lightdm/lightdm.conf changed: [LightDM] [Seat:*] [XDMCPServer] [VNCServer] -- debconf information: lightdm/daemon_name: /usr/sbin/lightdm * shared/default-x-display-manager: lightdm Starting program: /usr/sbin/lightdm --debug --test-mode [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log [+0.03s] DEBUG: Starting Light Display Manager 1.26.0, UID=0 PID=2132 [+0.05s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d [+0.07s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/01_debian.conf [+0.10s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d [+0.12s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d [+0.14s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf [+0.16s] DEBUG: Registered seat module local [+0.19s] DEBUG: Registered seat module xremote [+0.21s] DEBUG: Registered seat module unity [+0.23s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager [New Thread 0x76714700 (LWP 2136)] [New Thread 0x75f13700 (LWP 2137)] [New Thread 0x756cc700 (LWP 2138)] [+0.36s] DEBUG: Monitoring logind for seats [+0.38s] DEBUG: New seat added from logind: seat0 [+0.40s] DEBUG: Seat seat0: Loading properties from config section Seat:* [+0.42s] DEBUG: Seat seat0: Starting [+0.44s] DEBUG: Seat seat0: Creating greeter session [+0.46s] DEBUG: Seat seat0: Creating display server of type x [+0.48s] DEBUG: posix_spawn avoided (fd close requested) [+0.49s] DEBUG: Could not run plymouth --ping: Failed to execute child process ?plymouth? (No such file or directory) [+0.51s] DEBUG: Using VT 7 [+0.53s] DEBUG: Seat seat0: Starting local X display on VT 7 [+0.55s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log [+0.57s] DEBUG: XServer 0: Writing X server authority to /var/run/lightdm/root/:0 [+0.59s] DEBUG: XServer 0: Launching X Server [+0.61s] DEBUG: Launching process 2140: /usr/bin/X :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch [+0.63s] DEBUG: XServer 0: Waiting for ready signal from X server :0 [+0.65s] DEBUG: Acquired bus name org.freedesktop.DisplayManager [+0.67s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0 [+0.69s] WARNING: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files [+0.73s] DEBUG: Loading user config from /etc/lightdm/users.conf [+0.76s] WARNING: Failed to read password database: No such file or directory [+0.78s] DEBUG: User alex added [+0.80s] DEBUG: posix_spawn avoided (automatic reaping requested) (fd clos
Bug#911760: lightdm: more info
Package: lightdm Version: 1.26.0-3 Followup-For: Bug #911760 Could have something to do with the systemd/libpam upgrade? I have another issue with a password prompter (see attachment) Oct 24 15:42:45 hellspawn gpg-agent[1931]: failed to unprotect the secret key: Inappropriate ioctl for device Oct 24 15:42:45 hellspawn gpg-agent[1931]: failed to read the secret key Oct 24 15:42:45 hellspawn gpg-agent[1931]: command 'PKDECRYPT' failed: Inappropriate ioctl for device Oct 24 15:42:45 hellspawn dbus-daemon[1485]: [session uid=1000 pid=1485] Activating service name='org.gnome.keyring.SystemPrompter' requested by ':1.22' (uid=1000 pid=1986 comm="pinentry --display :0 ") Oct 24 15:42:45 hellspawn dbus-daemon[1485]: [session uid=1000 pid=1485] Activated service 'org.gnome.keyring.SystemPrompter' failed: Process org.gnome.keyring.SystemPrompter received signal 11 Oct 24 15:42:45 hellspawn gpg-agent[1931]: No Gcr System Prompter available, falling back to curses Oct 24 15:42:45 hellspawn kernel: gcr-prompter[1991]: segfault at 696e6420 ip 7ff4696c5907 sp 7fff5a80b198 error 4 in libc-2.27.so[7ff46958d000+146000] Oct 24 15:42:45 hellspawn kernel: Code: f9 20 77 1f c5 fd 74 0f c5 fd d7 c1 85 c0 0f 85 df 00 00 00 48 83 c7 20 83 e1 1f 48 83 e7 e0 eb 36 66 90 83 e1 1f 48 83 e7 e0 fd 74 0f c5 fd d7 c1 d3 f8 85 c0 74 1b f3 0f bc c0 48 01 f8 48
Bug#911760: lightdm-gtk-greeter segfault, lightdm restart too fast, can't login to desktop (Bug #911760)
Hello Bernhard, thanks for replying and the hints, see the attachment, sorry about the grave flag, feel free to change it (looking at the stack may be something related to the atspi upgrade, I'll try a downgrade, perhaps not a lightdm bug), currently I can login booting at level 3 and then startx manually. Kind regards Alex GNU gdb (Debian 8.1-4+b1) 8.1 Copyright (C) 2018 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/sbin/lightdm-gtk-greeter...Reading symbols from /usr/lib/debug/.build-id/c0/e5308b5094bd6e1bd8fc5473e690244ebf3ec6.debug...done. done. warning: core file may not match specified executable file. [New LWP 1562] [New LWP 1563] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/sbin/lightdm-gtk-greeter'. Program terminated with signal SIGSEGV, Segmentation fault. #0 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:93 93 ../sysdeps/x86_64/multiarch/strlen-avx2.S: No such file or directory. [Current thread is 1 (Thread 0x7f1b938c1a80 (LWP 1562))] (gdb) q PID: 1562 (lightdm-gtk-gre) UID: 110 (lightdm) GID: 116 (lightdm) Signal: 11 (SEGV) Timestamp: Thu 2018-10-25 16:12:05 CEST (4min 22s ago) Command Line: /usr/sbin/lightdm-gtk-greeter Executable: /usr/sbin/lightdm-gtk-greeter Control Group: /user.slice/user-110.slice/session-c1.scope Unit: session-c1.scope Slice: user-110.slice Session: c1 Owner UID: 110 (lightdm) Boot ID: fe8320c4f1fa48389152f7b8a23c1ba8 Machine ID: 6cbd0c550e6a4ab981e041a13ba68e48 Hostname: hellspawn Storage: /var/lib/systemd/coredump/core.lightdm-gtk-gre.110.fe8320c4f1fa48389152f7b8a23c1ba8.1562.154047672500.lz4 Message: Process 1562 (lightdm-gtk-gre) of user 110 dumped core. Stack trace of thread 1562: #0 0x7f1b99a64907 __strlen_avx2 (libc.so.6) #1 0x7f1b99cee3f8 g_string_insert_len (libglib-2.0.so.0) #2 0x7f1b99cd32a5 g_log_writer_format_fields (libglib-2.0.so.0) #3 0x7f1b99cd41ae g_log_writer_standard_streams (libglib-2.0.so.0) #4 0x7f1b99cd42b2 g_log_writer_default (libglib-2.0.so.0) #5 0x7f1b99cd2657 g_log_structured_array (libglib-2.0.so.0) #6 0x7f1b99cd2a9d g_log_default_handler (libglib-2.0.so.0) #7 0x7f1b99cd2cef g_logv (libglib-2.0.so.0) #8 0x7f1b99cd2edf g_log (libglib-2.0.so.0) #9 0x7f1b96b79342 atspi_get_a11y_bus (libatspi.so.0) #10 0x7f1b98de860a atk_bridge_adaptor_init (libatk-bridge-2.0.so.0) #11 0x7f1b9a265664 n/a (libgtk-3.so.0) #12 0x7f1b9a40fd39 n/a (libgtk-3.so.0) #13 0x7f1b99dabb6d g_closure_invoke (libgobject-2.0.so.0) #14 0x7f1b99dbe8f3 n/a (libgobject-2.0.so.0) #15 0x7f1b99dc7882 g_signal_emit_valist (libgobject-2.0.so.0) #16 0x7f1b99dc7ecf g_signal_emit (libgobject-2.0.so.0) #17 0x7f1b99db01d4 n/a (libgobject-2.0.so.0) #18 0x7f1b99db2651 g_object_notify (libgobject-2.0.so.0) #19 0x7f1b9a1119b8 n/a (libgdk-3.so.0) #20 0x7f1b99dabb6d g_closure_invoke (libgobject-2.0.so.0) #21 0x7f1b99dbe124 n/a (libgobject-2.0.so.0) #22 0x7f1b99dc7882 g_signal_emit_valist (libgobject-2.0.so.0) #23 0x7f1b99dc83a4 g_signal_emit_by_name (libgobject-2.0.so.0) #24 0x7f1b9a13cf5a n/a (libgdk-3.so.0) #25 0x7f1b9a11182d gdk_display_manager_open_display (libgdk-3.so.0) #26 0x7f1b9a410f1a gtk_init_check (libgtk-3.so.0) #27 0x7f1b9a410f49 gtk_init (libgtk-3.so.0) #28 0x55d6e0bc2e86 main (lightdm-gtk-greeter) #29 0x7f1b9992cb17 __libc_start_main (libc.so.6) #30 0x55d6e0bc555a _start (lightdm-gtk-greeter) S
Bug#911760: lightdm-gtk-greeter segfault, lightdm restart too fast, can't login to desktop (Bug #911760)
And... with today upgrade is gone, thanks Alexander and Gerhardt, sorry I saw yours mail a bit late, thanks for the support, appreciated. Best regards
Bug#911120: espeakup: Does not fully install
Hello all,
I'm also unable to install espeakup on Debian 9 Stretch with the kernel
from backports.
I've the following output when I'm trying to install espeakup:
invoke-rc.d: initscript espeakup, action "start" failed.
● espeakup.service - Software speech output for Speakup
Loaded: loaded (/lib/systemd/system/espeakup.service; enabled; vendor
preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Thu 2018-11-01
20:25:01 CET; 5ms ago
Docs: man:espeakup(8)
Process: 13834 ExecStart=/usr/bin/espeakup -V ${VOICE} (code=exited, status=2)
nov. 01 20:25:01 hypra-guy systemd[1]: espeakup.service: Unit entered failed
state.
nov. 01 20:25:01 hypra-guy systemd[1]: espeakup.service: Failed with result
'exit-code'.
dpkg: erreur de traitement du paquet espeakup (--configure) :
le sous-processus script post-installation installé a retourné une erreur de
sortie d'état 1
Traitement des actions différées (« triggers ») pour systemd (232-25+deb9u4) ...
Traitement des actions différées (« triggers ») pour man-db (2.7.6.1-2) ...
Des erreurs ont été rencontrées pendant l'exécution :
espeakup
E: Sub-process /usr/bin/dpkg returned an error code (1)
Could it be possible to backport the fix to Stretch release?
Best regards,
Alex.
On Mon, 15 Oct 2018 22:37:56 +0100 Keith Barrett
wrote:
Package: espeakup
Version: 1:0.80-10
Severity: grave
Tags: a11y
Justification: renders package unusable
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Frequent loss of speech in the console, particularly when switching to another
console or from the desktop.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Removed the package with a view to reinstalling.
* What was the outcome of this action?
Package failed to install
* What outcome did you expect instead?
Package to fully install and work.
*** End of the template - remove these template lines ***
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 4.18.0-2-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages espeakup depends on:
ii espeak 1.48.04+dfsg-6
ii libc6 2.27-6
ii libespeak-ng1 1.49.2+dfsg-4
ii lsb-base 9.20170808
espeakup recommends no packages.
espeakup suggests no packages.
-- no debconf information
--
Alex ARNAUD
Visual-Impairment Project Manager
Hypra - "Humanizing technology"
Bug#908162: grub-efi-amd64-signed: cryptdisk support missing
I don't think this is fixed yet. After switching to the signed grub on my system with an encrypted boot partition, I get dropped into the grub command line. From here, the cryptomount command appears to be a no-op. I'm not sure what the problem is, but I noticed that there is also a luks module which is not included. Maybe that's the issue? For now I have switched back to unsigned grub. -- Alex Griffin
Bug#879513: lame will not run at all
Package: lame Version: 3.100-2 Severity: grave Justification: renders package unusable Dear Maintainer, Since upgrading to lame 3.100-1 yesterday it fails to execute with: $ lame lame: symbol lookup error: lame: undefined symbol: lame_get_maximum_number_of_samples Tried upgrading to 3.100-2 today and it is the same. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.11.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1), LANGUAGE=en_GB:en_US:en_GB:en (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages lame depends on: ii libc62.24-17 ii libmp3lame0 1:3.99.5-0.1 ii libsndfile1 1.0.28-4 ii libtinfo56.0+20170902-1 lame recommends no packages. Versions of packages lame suggests: pn lame-doc -- no debconf information
Bug#1054412: cross-toolchain-base-ports: Stable update request to include latest glibc
Package: libc6.1-dev-alpha-cross Severity: serious X-Debbugs-Cc: none Dear Maintainer, The current alpha cross toolchain can't build working static binaries due to missing the fix for bug #1028200. This is fixed in the latest bookworm glibc but this isn't included in cross-toolchain-base-ports-62. See also: https://lists.debian.org/debian-alpha/2023/10/msg5.html -- System Information: Debian Release: 12.2 APT prefers stable APT policy: (900, 'stable'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'proposed-updates-debug') Architecture: amd64 (x86_64) Foreign Architectures: arm64, armhf, i386 Kernel: Linux 6.1.0-13-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 -- Alex Bennée Virtualisation Tech Lead @ Linaro
Bug#1054412: reassign 1054412 cross-toolchain-base-ports
-- Alex Bennée Emulation and Virtualisation Tech Lead @ Linaro
Bug#1071372: [solved] emacs: it hangs saving .gpg files (without using cpu)
gnupg2 (2.2.43-7) has arrived in unstable and gpg has started working again, as far as I'm concerned this report can be closed, thanks. Avoid breakage with epg.el (Closes: #1071552)
Bug#1074222: pycorrfit FTBFS with Python 3.12 as default
Hi All, AFAIK pycorrfit GUI should know about the location of the pdf file. Though it is a minor issue. Please feel free to upload, otherwise I'll try to have a look the next week. Thanks, Alex On 7/5/24 15:27, Bo YU wrote: Hi, On Fri, Jul 5, 2024 at 1:55 PM Andreas Tille wrote: Control: tags -1 pending Am Tue, Jul 02, 2024 at 05:07:08PM +0200 schrieb Andreas Tille: I'm fine with whatever solution you might find and you can perfectly skip me when doing some team upload. Could someone please fix W: pycorrfit: file-in-unusual-dir [usr/pycorrfit_doc/CHANGELOG] W: pycorrfit: file-in-unusual-dir [usr/pycorrfit_doc/PyCorrFit_doc.pdf] W: pycorrfit: non-standard-dir-in-usr [usr/pycorrfit_doc/] before uploading. I have pushed one commit which is trying to fix these warnings. Apparently there is no point in keeping the CHANGELOG in the Debian package, so is it okay to drop it? I have moved the PyCorrFit_doc.pdf file to usr/share/doc, but this will introduce possible-documentation-but-no-doc-base-registration info but we do not have -doc package so just left it there. https://salsa.debian.org/med-team/pycorrfit/-/tree/master/debian?ref_type=heads BR, Bo Sorry, I'm too busy with other things Andreas. -- https://fam-tille.de
Bug#1069844: grub-efi-arm64: grub fails to load Xen hypervisor on arm64 EFI systems (AVA & QEMU)
../grub-core/normal/main.c:356 #21 0x00023bf40ea0 in grub_try_normal (variable=0x23bf4e492 "fw_path") at ../../../grub-core/normal/main.c:407 #22 grub_cmd_normal (cmd=, argc=0, argv=) at ../../../grub-core/normal/main.c:421 #23 grub_cmd_normal (cmd=, argc=, argv=) at ../../../grub-core/normal/main.c:412 #24 0x00023c018fb8 in grub_command_execute (name=0x23c01ec6e ")", argc=0, argv=0x0 <_start>) at ../../../include/grub/command.h:126 #25 grub_load_normal_mode () at ../../../grub-core/kern/main.c:247 #26 grub_main () at ../../../grub-core/kern/main.c:339 #27 0x00023c5c02c8 in ?? () #28 0x00023c62a000 in ?? () #29 0xafafafaf6c617470 in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) While there are different firmwares (QEMU is EDKII targeting -M virt) it looks like the same error. However before writing off the firmware I did build the upstream grub: ➜ git describe grub-2.12-17-g8719cc204 🕙17:25:21 alex@gwenyn:grub.git on master [?] ➜ git show HEAD commit 8719cc2040368d43ab2de0b6e1b850b2c9cfc5b7 (HEAD -> master, origin/master, origin/HEAD) Author: Daniel Kiper Date: Tue Apr 9 19:56:02 2024 +0200 windows: Add _stack_chk_guard/_stack_chk_fail symbols for Windows 64-bit target Otherwise the GRUB cannot start due to missing symbols when stack protector is enabled on EFI platforms. Signed-off-by: Daniel Kiper Reviewed-by: Vladimir Serbinenko And installed it in parallel with the distro grub. This was able to start Xen using the same grub.cfg and get most of the way through the Dom0 boot before that failed for unrelated issues. So it seems there is a bug introduced by the debian customisation of the package or missing a fix from the current state of upstream. -- Alex Bennée Virtualisation Tech Lead @ Linaro
Bug#1069844: More debug info
entry@entry=0x23bd17660, auto_boot=auto_boot@entry=0) at ../../../grub-core/normal/menu.c:306 #7 0x00023bf41e2c in show_menu (autobooted=, nested=, menu=) at ../../../grub-core/normal/menu.c:925 #8 grub_show_menu (menu=menu@entry=0x23bd1a940, nested=nested@entry=1, autoboot=autoboot@entry=0) at ../../../grub-core/normal/menu.c:940 #9 0x00023bf408a8 in grub_normal_execute (config=, nested=nested@entry=1, batch=batch@entry=0) at ../../../grub-core/normal/main.c:291 #10 0x00023bf32260 in grub_cmd_source (cmd=, argc=1, args=0x23bd1fcc8) at ../../../grub-core/commands/configfile.c:48 #11 grub_cmd_source (cmd=, argc=, args=0x23bd1fcc8) at ../../../grub-core/commands/configfile.c:30 #12 0x00023bf48d0c in grub_script_execute_cmdline (cmd=) at ../../../grub-core/script/execute.c:1034 #13 0x00023bf478c0 in grub_script_execute_cmd (cmd=cmd@entry=0x23bd190c8) at ../../../grub-core/script/execute.c:819 #14 0x00023bf4874c in grub_script_execute_cmdlist (list=) at ../../../grub-core/script/execute.c:1079 #15 0x00023bf478c0 in grub_script_execute_cmd (cmd=) at ../../../grub-core/script/execute.c:819 #16 0x00023bf489b4 in grub_script_execute (script=) at ../../../grub-core/script/execute.c:1191 #17 0x00023bf497fc in grub_normal_parse_line (line=line@entry=0x23bd20060 "configfile $prefix/grub.cfg", getline=getline@entry=0x23bf40430 , getline_data=getline_data@entry=0x23bd20380) at ../../../grub-core/script/main.c:36 #18 0x00023bf409a0 in read_config_file (config=0x23bd20780 "(hd0,gpt1)/EFI/debian/grub.cfg") at ../../../grub-core/normal/main.c:179 #19 grub_normal_execute (config=config@entry=0x23bd20780 "(hd0,gpt1)/EFI/debian/grub.cfg", nested=nested@entry=0, batch=batch@entry=0) at ../../../grub-core/normal/main.c:277 #20 0x00023bf40ca4 in grub_enter_normal_mode (config=config@entry=0x23bd20780 "(hd0,gpt1)/EFI/debian/grub.cfg") at ../../../grub-core/normal/main.c:304 #21 0x00023bf40da0 in grub_try_normal_prefix (prefix=0x23bd209a0 "(hd0,gpt1)/EFI/debian") at ../../../grub-core/normal/main.c:356 #22 0x00023bf40ea0 in grub_try_normal (variable=0x23bf4e492 "fw_path") at ../../../grub-core/normal/main.c:407 #23 grub_cmd_normal (cmd=, argc=0, argv=) at ../../../grub-core/normal/main.c:421 #24 grub_cmd_normal (cmd=, argc=, argv=) at ../../../grub-core/normal/main.c:412 #25 0x00023c018fb8 in grub_command_execute (name=0x23c01ec6e ")", argc=0, argv=0x0 <_start>) at ../../../include/grub/command.h:126 #26 grub_load_normal_mode () at ../../../grub-core/kern/main.c:247 #27 grub_main () at ../../../grub-core/kern/main.c:339 #28 0x00023c5c02c8 in ?? () #29 0x00023c62a000 in ?? () #30 0xafafafaf6c617470 in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) Is it possible to override the peloader or does the Xen image need to be prepared a certain way? -- Alex Bennée Virtualisation Tech Lead @ Linaro
Bug#1069844: More debug info
Julian Andres Klode writes: > On Thu, Apr 25, 2024 at 06:30:52PM +0100, Alex Bennée wrote: >> >> Continuing to debug on QEMU it seems there is an incompatibility with >> the images and the peloader (which overrides the normal efi loader): >> >> Thread 1 hit Breakpoint 3.2, grub_load_normal_mode () at >> ../../../grub-core/kern/main.c:241 >> 241 in ../../../grub-core/kern/main.c >> >> >> (grub gdb) hbreak do_load_image >> >> >> Hardware assisted breakpoint 4 at 0x23bdf0e00: do_load_image. (2 >> locations) >> >> (grub gdb) c >> >> >> Continuing. >> >> >> add symbol table from file "bli.module" at >> >> >> .text_addr = 0x23ba772e0 >> >> >> .bss_addr = 0x0 >> >> >> .module_license_addr = 0x23ba7764a >> .data_addr = 0x0 >> >> >> .rodata.str1.1_addr = 0x23ba77560 >> >> >> .rodata_addr = 0x23ba77550 >> >> >> add symbol table from file "xen_boot.module" at >> >> >> .text_addr = 0x23bcef3c0 >> >> >> .bss_addr = 0x23bcf0370 >> >> >> .module_license_addr = 0x23bcf035e >> >> .data_addr = 0x0 >> >> .rodata.str1.1_addr = 0x23bcefff8 >> >> Thread 1 hit Breakpoint 4.1, do_load_image (boot_policy=0 '\000', >> parent_image_handle=0x23e889f18, file_path=0x237d1bce0, >> source_buffer=0x239f0, source_size=1081352, >> image_handle=0x4766c498) at ../../../grub-core/loader/efi/peimage.c:745 >> warning: 745../../../grub-core/loader/efi/peimage.c: No such file or >> directory >> (grub gdb) hbreak grub_error >> Hardware assisted breakpoint 5 at 0x6db0: grub_error. (2 locations) >> (grub gdb) c >> Continuing. >> >> Thread 1 hit Breakpoint 4.2, 0x00023bdf0e4c in do_load_image >> (boot_policy=, parent_image_handle=, >> image_handle=, >> source_size=, source_buffer=, >> file_path=) at ../../../grub-core/loader/efi/peimage.c:751 >> 751 in ../../../grub-core/loader/efi/peimage.c >> (grub gdb) c >> Continuing. >> >> Thread 1 hit Breakpoint 5.2, grub_error (n=GRUB_ERR_BAD_OS, >> fmt=0x23bdf1703 "section inside header") at ../../../grub-core/kern/err.c:41 >> warning: 41 ../../../grub-core/kern/err.c: No such file or directory >> (grub gdb) bt >> #0 grub_error (n=GRUB_ERR_BAD_OS, fmt=0x23bdf1703 "section inside >> header") at ../../../g
Bug#1069844: More debug info
Alex Bennée writes: > Julian Andres Klode writes: > >> On Thu, Apr 25, 2024 at 06:30:52PM +0100, Alex Bennée wrote: >>> >>> Continuing to debug on QEMU it seems there is an incompatibility with >>> the images and the peloader (which overrides the normal efi loader): >>> > >> In the error case you can see though, that one of the section >> addresses in the Xen binary to be relocated points into the (PE) >> header of the binary, which obviously seems wrong. >> >> So go check your PE sections and check which one is wrong? > > Is there any tooling for examining PE sections? Nothing really jumps out from objdump: 1:08:50 [root@debian-arm64:~] # objdump -h /boot/xen /boot/xen: file format pei-aarch64-little Sections: Idx Name Size VMA LMA File off Algn 0 .reloc 2**0 ALLOC, LOAD, READONLY, DATA 1 .text 00107ea8 0160 0160 0160 2**4 CONTENTS, ALLOC, LOAD, CODE 21:08:53 [root@debian-arm64:~] # objdump -h /boot/vmlinuz /boot/vmlinuz: file format pei-aarch64-little Sections: Idx Name Size VMA LMA File off Algn 0 .text 018c 0001 0001 0001 2**2 CONTENTS, ALLOC, LOAD, READONLY, CODE 1 .data 0090a200 018d 018d 018d 2**2 CONTENTS, ALLOC, LOAD, DATA -- Alex Bennée Virtualisation Tech Lead @ Linaro
Bug#1069844: More debug info
On Fri, 26 Apr 2024 at 16:48, Julian Andres Klode <
julian.kl...@canonical.com> wrote:
> On Thu, Apr 25, 2024 at 09:10:08PM +0100, Alex Bennée wrote:
> > Alex Bennée writes:
> >
> > > Julian Andres Klode writes:
> > >
> > >> On Thu, Apr 25, 2024 at 06:30:52PM +0100, Alex Bennée wrote:
> > >>>
> > >>> Continuing to debug on QEMU it seems there is an incompatibility with
> > >>> the images and the peloader (which overrides the normal efi loader):
> > >>>
> >
> > >
> > >> In the error case you can see though, that one of the section
> > >> addresses in the Xen binary to be relocated points into the (PE)
> > >> header of the binary, which obviously seems wrong.
> > >>
> > >> So go check your PE sections and check which one is wrong?
> > >
> > > Is there any tooling for examining PE sections?
> >
> > Nothing really jumps out from objdump:
> >
> > 1:08:50 [root@debian-arm64:~] # objdump -h /boot/xen
> >
> > /boot/xen: file format pei-aarch64-little
> >
> > Sections:
> > Idx Name Size VMA LMA File
> off Algn
> > 0 .reloc
> 2**0
> > ALLOC, LOAD, READONLY, DATA
>
>
> This looks suspicious. Yes it's 0 size but it's address is 0 which
> clearly points into the header, and we don't skip 0 size sections when
> loading the PE binary for later relocation, and we don't use any .reloc
> section.
>
It does get skipped in the reloc code:
if (!info->reloc || !(info->reloc->size))
{
grub_dprintf ("linux", "no relocations\n");
return GRUB_EFI_SUCCESS;
}
Although the x86_64 build of Xen uses reloc sections (which Xen itself
deals with) we don't actually need them for Arm. However the way the PE
binary is built is a little funky:
make
UPD include/xen/compile.h
Xen 4.19-unstable
make[1]: Nothing to be done for 'include'.
make[1]: 'arch/arm/include/asm/asm-offsets.h' is up to date.
CC common/version.o
LD common/built_in.o
CC arch/arm/acpi/domain_build.o
INIT_O arch/arm/acpi/domain_build.init.o
LD arch/arm/acpi/built_in.o
CC arch/arm/domain_build.o
INIT_O arch/arm/domain_build.init.o
CC arch/arm/efi/boot.o
INIT_O arch/arm/efi/boot.init.o
LD arch/arm/efi/built_in.o
CC arch/arm/setup.o
LD arch/arm/built_in.o
LD prelink.o
ld-EL --no-warn-rwx-segments --fix-cortex-a53-843419 -T
arch/arm/xen.lds -N prelink.o \
./common/symbols-dummy.o -o ./.xen-syms.0
nm -pa --format=sysv ./.xen-syms.0 \
| ./tools/symbols --sysv --sort \
> ./.xen-syms.0.S
make -f ./Rules.mk obj=. ./.xen-syms.0.o
CC .xen-syms.0.o
ld-EL --no-warn-rwx-segments --fix-cortex-a53-843419 -T
arch/arm/xen.lds -N prelink.o \
./.xen-syms.0.o -o ./.xen-syms.1
nm -pa --format=sysv ./.xen-syms.1 \
| ./tools/symbols --sysv --sort \
> ./.xen-syms.1.S
make -f ./Rules.mk obj=. ./.xen-syms.1.o
CC .xen-syms.1.o
ld-EL --no-warn-rwx-segments --fix-cortex-a53-843419 -T
arch/arm/xen.lds -N prelink.o --build-id=sha1 \
./.xen-syms.1.o -o xen-syms
nm -pa --format=sysv xen-syms \
| ./tools/symbols --all-symbols --xensyms --sysv --sort \
> xen-syms.map
rm -f ./.xen-syms.[0-9]*
objcopy -O binary -S xen-syms xen
ln -sf xen xen.efi
I can't work out how to build without the reloc section and trying to
remove the .reloc section after the fact results in something where the
file-offset is ahead of the VMA position:
➜ objcopy --remove-section=.reloc -O binary -S xen-syms xen-test
🕙17:03:23 alex@gwenyn:xen.git/xen on testing/new-attempt:new-attempt
[!?]
➜ objdump -h xen-test
xen-test: file format pei-aarch64-little
Sections:
Idx Name Size VMA LMA File off
Algn
0 .reloc
2**0
ALLOC, LOAD, READONLY, DATA
1 .text 00127ea8 0160 0160 0160
2**4
CONTENTS, ALLOC, LOAD, CODE
🕙17:03:25 alex@gwenyn:xen.git/xen on testing/new-attempt:new-attempt
[!?]
➜ objcopy --remove-section=.reloc xen-test
🕙17:03:37 alex@gwenyn:xen.git/xen on testing/new-attempt:new-attempt
[!?]
➜ objdump -h xen-test
xen-test: file format pei-aarch64-little
Sections:
Idx Name Size VMA LMA File off
Algn
0 .text 00127ea8 0160 0160 01b0
2**2
CONTENTS, ALLOC,
Bug#1069101: libdbd-oracle-perl: requires rebuild for time_t transition
Control: owner -1 ! Control: tags -1 upstream help Hi Sebastian, > libdbd-oracle-perl depends on libaio1 It turns out that it's oracle-instantclient-basic that needs libaio.so.1. I'm not sure what could be done to address this issue, since the soname renaming to libaio.so.1t64 is Debian specific. If libdbd-oracle-perl needs to be removed from testing for the transition to proceed, so be it. In fact, there's no need to wait until May 15; feel free to remove it sooner. Cheers! Alex -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Alex Muntada ⢿⡄⠘⠷⠚⠋ Debian Developer 🍥 log.alexm.org ⠈⠳⣄ signature.asc Description: PGP signature
Bug#1069101: libdbd-oracle-perl: requires rebuild for time_t transition
[Cc to debian-perl for feedback] Hi Sebastian, > > > libdbd-oracle-perl depends on libaio1 > > > > It turns out that it's oracle-instantclient-basic that needs > > libaio.so.1. I'm not sure what could be done to address this > > issue, since the soname renaming to libaio.so.1t64 is Debian > > specific. I came up with an easy solution to this: since libaio.so.1 is required by oracle-instantclient-basic (not in Debian), we could add libaio (from Oracle Linux) in Depends and then explain in README.Debian to download it from Oracle, build the .deb with alien and install it, like the other external dependencies. The thing is that maybe a hint on libaio will be needed? Plus, I guess that libaio and libaio1/libaio1t64 are so similar that it could create too much confusion anyway... What do you think? If it's too much, then probably it's the time to say goodbye to libdbd-oracle-perl (popcon number is 52). Cheers! Alex -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Alex Muntada ⢿⡄⠘⠷⠚⠋ Debian Developer 🍥 log.alexm.org ⠈⠳⣄ signature.asc Description: PGP signature
Bug#1069101: libdbd-oracle-perl: requires rebuild for time_t transition
Hi gregor, > > The thing is that maybe a hint on libaio will be needed? > > What do you mean be "hint" here? When I uploaded 1.83-3 the migration to testing was blocked because oracle-instantclient12.1-devel in B-D was replaced by oracle-instantclient-devel, and a force hint was needed: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032142 I'm wondering if the same thing will happen when replacing libaio1 with libaio in Depends, since I don't know britney well enough... Cheers and thanks for the feedback! Alex -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Alex Muntada ⢿⡄⠘⠷⠚⠋ Debian Developer 🍥 log.alexm.org ⠈⠳⣄ signature.asc Description: PGP signature
