Bug#1033732: linux-image-6.1.0-7-amd64: The Linux 6.1.0-7-amd64 kernel launching crashes with a panic message
Salvatore Bonaccorso writes: > AFAIK there is no commit upstream with fixes tag on that commit. But > Bjorn suspects that might be the suspicious commit introducing the > issue. Yes, I noticed that, so I could very well be wrong... But it stood out as the only change to any x86 IOAPIC stuff since Linux 6.1.0-6-amd64. That's of course not any guarantee. But worth testing. Bjørn
Bug#1033732: linux-image-6.1.0-7-amd64: The Linux 6.1.0-7-amd64 kernel launching crashes with a panic message
Guy Durrieu writes: > > [ 0.117782] Kernel panic — not syncing: timer doesn’t work through > Interrupt- > remapped I0-APIC > [ 0.117848] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.1.0-7-and64 #1 > Debian > 6.1.20-1 > [ 0.117913] Hardware name: Gigabyte Technology Co., Ltd. ABS50M-Gaming > 3/AB350M-Gaming 3-CF, BIOS F50d 07/02/2020 > [ 0.117982] Call Trace: > [ 0.118634] > [ 0.118685] dump_stack_lvl+0x44/0x5c > [ 0.118143] panic+0x118/0x2ed > [ 0.118198] panic_if_irq_remap.cold+0x5/0x5 > [ 0.118256] setup_I0_APIC+0x3db/0x64b > [ 0.118313] ? _raw_spin_unlock_irqrestore+0x23/0x40 > [ 0.118372] ? clear_IO_APIC_pin+0x169/0x240 > [ 0.118429] apic_intr_node_init+0x101/0x106 > [ 0.118485] x86_late_time_init+0x20/0x34 > [ 0.118542] start_kerne1+0x667/0x727 > [ 0.118598] secondary_startup_64_no_verify+0xe5/0xeb > [ 0.118658] > [ 0.118711] ---[ end Kernel panic - not syncing: timer doesn’t work through > Interrupt-remapped IO-APIC J--- > Extremely suspiscious commit in the v6.1.15..v6.1.20 update: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/commit/?id=ce7d894bed1a539a8d6cff42f6f78f9db0c9c26b Bjørn
Bug#1008829: pysrs-bin: envfrom2srs and srs2envtol fails with ModuleNotFoundError: No module named 'ConfigParser'
Package: pysrs-bin Version: 1.0.3-2 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear Maintainer, # envfrom2srs Traceback (most recent call last): File "/usr/bin/envfrom2srs", line 14, in from ConfigParser import ConfigParser, DuplicateSectionError ModuleNotFoundError: No module named 'ConfigParser' # srs2envtol Traceback (most recent call last): File "/usr/bin/srs2envtol", line 14, in from ConfigParser import ConfigParser, DuplicateSectionError ModuleNotFoundError: No module named 'ConfigParser' No need to clutter the archive with broken and untested packages. Please remove - -- System Information: Debian Release: 11.3 APT prefers stable-security APT policy: (700, 'stable-security'), (700, 'stable'), (699, 'stable-updates') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-13-amd64 (SMP w/8 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages pysrs-bin depends on: ii python3 3.9.2-3 ii python3-srs 1.0.3-2 pysrs-bin recommends no packages. pysrs-bin suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- iGwEARECACwWIQR3fjfc8EF8nPbC0aDXSuqSjBsiyQUCYkgktA4cYmpvcm5AbW9y ay5ubwAKCRDXSuqSjBsiyUJdAJ4zvzZBL6hIfzScL01SNMcAQDNSEQCfZZJU9yuy jyC6TtdcMxqBEPpi278= =yarJ -END PGP SIGNATURE-
Bug#1008828: python3-spf-engine: fails with ImportError: cannot import name 'own_socketfile' from 'spf_engine.util'
Package: python3-spf-engine
Version: 2.9.2-1
Severity: grave
Justification: renders package unusable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dear Maintainer,
Installing pyspf-milter with default dependencies and settings results
in
# journalctl -u pyspf-milter
- -- Journal begins at Sat 2022-03-26 15:26:01 CET, ends at Sat 2022-04-02
12:11:13 CEST. --
Apr 02 12:04:07 canardo systemd[1]: Started pySPF Milter.
Apr 02 12:04:07 canardo pyspf-milter[372481]: Traceback (most recent call last):
Apr 02 12:04:07 canardo pyspf-milter[372481]: Traceback (most recent call last):
Apr 02 12:04:07 canardo pyspf-milter[372481]: File "/usr/bin/pyspf-milter",
line 11, in
Apr 02 12:04:07 canardo pyspf-milter[372481]:
load_entry_point('spf-engine==2.9.2', 'console_scripts', 'pyspf-milter')()
Apr 02 12:04:07 canardo pyspf-milter[372481]: File
"/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 474, in
load_entry_point
Apr 02 12:04:07 canardo pyspf-milter[372481]: return
get_distribution(dist).load_entry_point(group, name)
Apr 02 12:04:07 canardo pyspf-milter[372481]: File
"/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2846, in
load_entry_point
Apr 02 12:04:07 canardo pyspf-milter[372481]: return ep.load()
Apr 02 12:04:07 canardo pyspf-milter[372481]: File
"/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2450, in load
Apr 02 12:04:07 canardo pyspf-milter[372481]: return self.resolve()
Apr 02 12:04:07 canardo pyspf-milter[372481]: File
"/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2456, in
resolve
Apr 02 12:04:07 canardo pyspf-milter[372481]: module =
__import__(self.module_name, fromlist=['__name__'], level=0)
Apr 02 12:04:07 canardo pyspf-milter[372481]: File
"/usr/lib/python3/dist-packages/spf_engine/milter_spf.py", line 40, in
Apr 02 12:04:07 canardo pyspf-milter[372481]: from spf_engine.util import
own_socketfile
Apr 02 12:04:07 canardo pyspf-milter[372481]: ImportError: cannot import name
'own_socketfile' from 'spf_engine.util'
(/usr/lib/python3/dist-packages/spf_engine/util.py)
Apr 02 12:04:07 canardo pyspf-milter[372481]: File "/usr/bin/pyspf-milter",
line 11, in
load_entry_point('spf-engine==2.9.2', 'console_scripts', 'pyspf-milter')()
Apr 02 12:04:07 canardo pyspf-milter[372481]: File
"/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 474, in
load_entry_point
return
get_distribution(dist).load_entry_point(group, name)
Apr 02 12:04:07 canardo pyspf-milter[372481]: File
"/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2846, in
load_entry_point
return ep.load()
Apr 02 12:04:07 canardo pyspf-milter[372481]: File
"/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2450, in load
return self.resolve()
Apr 02 12:04:07 canardo pyspf-milter[372481]: File
"/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2456, in
resolve
module =
__import__(self.module_name, fromlist=['__name__'], level=0)
Apr 02 12:04:07 canardo pyspf-milter[372481]: File
"/usr/lib/python3/dist-packages/spf_engine/milter_spf.py", line 40, in
from spf_engine.util import
own_socketfile
Apr 02 12:04:07 canardo pyspf-milter[372481]: ImportError: cannot import name
'own_socketfile' from 'spf_engine.util'
(/usr/lib/python3/dist-packages/spf_engine/util.py)
Apr 02 12:04:07 canardo systemd[1]: pyspf-milter.service: Main process exited,
code=exited, status=1/FAILURE
Apr 02 12:04:07 canardo systemd[1]: pyspf-milter.service: Failed with result
'exit-code'.
No need to clutter the archive with completely broken and untested packages.
- -- System Information:
Debian Release: 11.3
APT prefers stable-security
APT policy: (700, 'stable-security'), (700, 'stable'), (699, 'stable-updates')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-13-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages python3-spf-engine depends on:
ii python3 3.9.2-3
ii python3-authres 1.2.0-2
ii python3-spf 2.0.14-2
python3-spf-engine recommends no packages.
python3-spf-engine suggests no packages.
- -- no debconf information
-BEGIN PGP SIGNATURE-
iGwEARECACwWIQR3fjfc8EF8nPbC0aDXSuqSjBsiyQUCYkgi8Q4cYmpvcm5AbW9y
ay5ubwAKCRDXSuqSjBsiyarCAKCAzlYvQ8KoeYFTwu57/rcZUaVWZgCeJh9IDyHM
qzAsx/mDicjW7tkbafU=
=TY8J
-END PGP SIGNATURE-
Bug#987778: texlive-latex-extra: fails to declare dependency on libspreadsheet-parseexcel-perl
Package: texlive-latex-extra Version: 2020.20210202-3 Severity: serious Justification: Policy 3.5 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 libspreadsheet-parseexcel-perl is required to run the exceltex binary, but is not declared as a dependency. bjorn@miraculix:~$ exceltex Can't locate Spreadsheet/ParseExcel.pm in @INC (you may need to install the Spreadsheet::ParseExcel module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.32.1 /usr/local/share/perl/5.32.1 /usr/lib/x86_64-linux-gnu/perl5/5.32 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.32 /usr/share/perl/5.32 /usr/local/lib/site_perl) at /usr/bin/exceltex line 738. BEGIN failed--compilation aborted at /usr/bin/exceltex line 738. - -- Package-specific info: IMPORTANT INFORMATION: We will only consider bug reports concerning the packaging of TeX Live as relevant. If you have problems with combination of packages in a LaTeX document, please consult your local TeX User Group, the comp.text.tex user group, the author of the original .sty file, or any other help resource. In particular, bugs that are related to up-upstream, i.e., neither Debian nor TeX Live (upstream), but the original package authors, will be closed immediately. *** The Debian TeX Team is *not* a LaTeX Help Desk *** If you report an error when running one of the TeX-related binaries (latex, pdftex, metafont,...), or if the bug is related to bad or wrong output, please include a MINIMAL example input file that produces the error in your report. Please run your example with (pdf)latex -recorder ... (or any other program that supports -recorder) and send us the generated file with the extension .fls, it lists all the files loaded during the run and can easily explain problems induced by outdated files in your home directory. Don't forget to also include minimal examples of other files that are needed, e.g. bibtex databases. Often it also helps to include the logfile. Please, never send included pictures! If your example file isn't short or produces more than one page of output (except when multiple pages are needed to show the problem), you can probably minimize it further. Instructions on how to do that can be found at http://www.minimalbeispiel.de/mini-en.html (english) or http://www.minimalbeispiel.de/mini.html (german) ## minimal input file ## other files ## List of ls-R files lrwxrwxrwx 1 root root 31 Feb 17 21:30 /usr/share/texlive/texmf-dist/ls-R -> /var/lib/texmf/ls-R-TEXLIVEDIST ## Config files - -rw-r--r-- 1 root root 475 Feb 23 16:50 /etc/texmf/web2c/texmf.cnf lrwxrwxrwx 1 root root 33 Feb 17 21:30 /usr/share/texmf/web2c/fmtutil.cnf -> /var/lib/texmf/fmtutil.cnf-DEBIAN lrwxrwxrwx 1 root root 32 Feb 17 21:30 /usr/share/texmf/web2c/updmap.cfg -> /var/lib/texmf/updmap.cfg-DEBIAN - -rw-r--r-- 1 root root 2763 Apr 5 10:45 /var/lib/texmf/tex/generic/config/language.dat ## Files in /etc/texmf/web2c/ total 8 - -rw-r--r-- 1 root root 283 Feb 22 2016 mktex.cnf - -rw-r--r-- 1 root root 475 Feb 23 16:50 texmf.cnf ## md5sums of texmf.d ca40c66f144b4bafc3e59a2dd32ecb9c /etc/texmf/texmf.d/00debian.cnf - -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (700, 'stable'), (600, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386, arm64 Kernel: Linux 5.10.0-6-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_USER Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages texlive-latex-extra depends on: ii libcommons-logging-java1.2-2 ii libpdfbox-java 1:1.8.16-2 ii preview-latex-style12.2-1 ii python33.9.2-3 ii tex-common 6.16 ii texlive-base 2020.20210202-3 ii texlive-binaries 2020.20200327.54578-7 ii texlive-latex-recommended 2020.20210202-3 ii texlive-pictures 2020.20210202-3 Versions of packages texlive-latex-extra recommends: ii texlive-fonts-recommended 2020.20210202-3 ii texlive-plain-generic 2020.20210202-3 Versions of packages texlive-latex-extra suggests: pn icc-profiles ii libfile-which-perl 1.23-1 ii libspreadsheet-parseexcel-perl 0.6500-1.1 ii python3-pygments2.7.1+dfsg-2 pn texlive-latex-extra-doc Versions of packages tex-common depends on: ii dpkg 1.20.9 ii ucf 3.0043 Versions of packages tex-common suggests: ii debhelper 13.3.4 Versions of packages texlive-latex-extra is related to: ii tex-common6.16 ii texlive-binaries 2020.20200327.54578-7 - -- no debconf information
Bug#948257: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_XXXXXXX/lib/modules/5.4.0-1-amd64/modules.builtin.bin'
Pierrick CHANTEUX writes: > This bug resulted in complete system breakage and I couldn't boot > anymore (systemd failing to load Kernel modules). I can guarantee that > this isn't only cosmetic. > > I believe this isn't related to initramfs-tools, because downgrading > kmod and libkmod2 from version 26+20191223-1 to version 26-3 fixes the > issue. Initramfs now build (and run) correctly. IMHO this is probably an unrelated bug in the same kmod upgrade. You should report it as such, which the full log output and a subject decribing the issue instead of the bogus error message. The logspam caused by the lookup_builtin_file() bug makes it hard to spot real errors, but hopefully there is some clue to your problem there too. Bjørn
Bug#768025: systemd-logind: default configuration breaks any existing ACPI button handling
Package: systemd
Version: 215-5+b1
Severity: critical
Justification: breaks unrelated software
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
systemd-logind breaks acpid by default.
Merely installing systemd with default configuration causes it to start
handling the PowerKey, LidSwitch, HibernateKey and SuspendKey without
considering existing acpid configuration. This completely breaks those
events to break due to the double handling (pressing either of these
buttons two times does not give the desired result).
acpid and systemd are unrelated according to dependencies. The breakage
is therefore unexpected.
Note that this bug affects systems using sysvinit as well. systemd is
dragged in by policykit, and systemd-logind will be started by dbus on
request regardless of the init system being used.
Bjørn
- -- Package-specific info:
- -- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (990, 'testing'), (600, 'unstable'), (500, 'testing-updates'),
(1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.18.0-rc3 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages systemd depends on:
ii acl 2.2.52-2
ii adduser 3.113+nmu3
ii initscripts 2.88dsf-53.4
ii libacl1 2.2.52-2
ii libaudit1 1:2.4-1
ii libblkid1 2.25.2-2
ii libc6 2.19-12
ii libcap2 1:2.24-6
ii libcap2-bin 1:2.24-6
ii libcryptsetup4 2:1.6.6-3
ii libgcrypt20 1.6.2-4
ii libkmod218-3
ii liblzma55.1.1alpha+20120614-2
ii libpam0g1.1.8-3.1
ii libselinux1 2.3-2
ii libsystemd0 215-5+b1
ii sysv-rc 2.88dsf-53.4
ii udev215-5+b1
ii util-linux 2.25.2-2
Versions of packages systemd recommends:
ii dbus1.8.8-2
ii libpam-systemd 215-5+b1
Versions of packages systemd suggests:
pn systemd-ui none
- -- Configuration Files:
/etc/systemd/logind.conf changed:
[Login]
HandlePowerKey=ignore
HandleSuspendKey=ignore
HandleHibernateKey=ignore
HandleLidSwitch=ignore
- -- no debconf information
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iEYEARECAAYFAlRYoZYACgkQ10rqkowbIskBEACdGQyrci0zI+0RV4QkbP/5H7M1
wXEAnj7CqasQJWzW+C1BqUwPv+sHJ8e5
=sFS0
-END PGP SIGNATURE-
[OVERRIDDEN] /etc/udev/rules.d/40-usb_modeswitch.rules - /lib/udev/rules.d/40-usb_modeswitch.rules
--- /lib/udev/rules.d/40-usb_modeswitch.rules 2014-06-09 11:21:49.0 +0200
+++ /etc/udev/rules.d/40-usb_modeswitch.rules 2012-11-10 21:18:02.0 +0100
@@ -1,12 +1,13 @@
-# Part of usb-modeswitch-data, version 20140529
+# Part of usb-modeswitch-data, version 20121109
#
-# Works with usb_modeswitch versions = 2.2.0 (introduction of HuaweiNewMode)
+# Recommended use with USB_ModeSwitch = 1.2.5, works with versions = 1.0.3
+# (New style, interface class check moved to dispatcher)
#
ACTION!=add|change, GOTO=modeswitch_rules_end
# Adds a symlink gsmmodem[n] to the lowest ttyUSB port with interrupt
# transfer; checked against a list of known modems, or else no action
-KERNEL==ttyUSB*, ATTRS{bNumConfigurations}==*, PROGRAM=usb_modeswitch --symlink-name %p %s{idVendor} %s{idProduct} %E{PRODUCT}, SYMLINK+=%c
+KERNEL==ttyUSB*, ATTRS{bNumConfigurations}==*, PROGRAM=usb_modeswitch --symlink-name %p %s{idVendor} %s{idProduct} %E{PRODUCT}, SYMLINK=%c
SUBSYSTEM!=usb, GOTO=modeswitch_rules_end
@@ -20,36 +21,18 @@
ACTION!=add, GOTO=modeswitch_rules_end
-# Generic entry for all Huawei devices
-ATTRS{idVendor}==12d1, ATTR{bInterfaceNumber}==00, ATTR{bInterfaceClass}==08, RUN+=usb_modeswitch '%b/%k'
-
# HP LaserJet Professional P1102
ATTR{idVendor}==03f0, ATTR{idProduct}==002a, RUN+=usb_modeswitch '%b/%k'
-# Quanta 1KR / USB-lte 7410
-ATTR{idVendor}==0408, ATTR{idProduct}==ea17, RUN+=usb_modeswitch '%b/%k'
-
-# Quanta 1K3 LTE
-ATTR{idVendor}==0408, ATTR{idProduct}==ea25, RUN+=usb_modeswitch '%b/%k'
-
-# Quanta MobileGenie 4G lte
-ATTR{idVendor}==0408, ATTR{idProduct}==ea43, RUN+=usb_modeswitch '%b/%k'
-
# Yota Router (Quanta 1QDLZZZ0ST2)
ATTR{idVendor}==0408, ATTR{idProduct}==f000, RUN+=usb_modeswitch '%b/%k'
-# SpeedUp SU-8500U
-ATTR{idVendor}==0408, ATTR{idProduct}==f001, RUN+=usb_modeswitch '%b/%k'
-
# Nokia CS-10
ATTR{idVendor}==0421, ATTR{idProduct}==060c, RUN+=usb_modeswitch '%b/%k'
# Nokia CS-15
ATTR{idVendor}==0421, ATTR{idProduct}==0610, RUN+=usb_modeswitch '%b/%k'
-# Nokia CS-12
-ATTR{idVendor}==0421, ATTR{idProduct}==0618, RUN+=usb_modeswitch '%b/%k'
-
# Nokia CS-11
ATTR{idVendor}==0421, ATTR{idProduct}==061d, RUN+=usb_modeswitch '%b/%k'
@@ -68,7 +51,7 @@
# Nokia CS-21M-02
ATTR{idVendor}==0421, ATTR{idProduct}==0637, RUN+=usb_modeswitch '%b/%k'
-# Philips (?), Vodafone MD950 (Wisue Technology)
+# Vodafone MD950 (Wisue Technology), Philips (?)
ATTR{idVendor}==0471, ATTR{idProduct}==1210, RUN+=usb_modeswitch '%b/%k'
# Philips TalkTalk (NXP
Bug#767019: xscreensaver: postinst overwrites /etc/X11/app-defaults/XScreenSaver without asking
Package: xscreensaver Version: 5.30-1+b1 Severity: serious Justification: Policy 10.7.3 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This part of xscreensaver.postinst overwrites any locally modified /etc/X11/app-defaults/XScreenSaver configuration: # Use the correct app defaults cd /etc/X11/app-defaults if [ -f XScreenSaver-gl ]; then ln -sf XScreenSaver-gl XScreenSaver else ln -sf XScreenSaver-nogl XScreenSaver fi You should not do the above if an XScreenSaver file or symlink exists prior to installation Bjørn - -- System Information: Debian Release: 7.7 APT prefers stable APT policy: (700, 'stable'), (600, 'unstable'), (500, 'stable-updates'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.18.0-rc2 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xscreensaver depends on: ii libatk1.0-0 2.14.0-1 ii libc62.19-12 ii libcairo21.14.0-2 ii libfontconfig1 2.11.0-6.1 ii libfreetype6 2.5.2-2 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglade2-0 1:2.6.4-2 ii libglib2.0-0 2.42.0-2 ii libgtk2.0-0 2.24.25-1 ii libice6 2:1.0.9-1 ii libpam0g 1.1.3-7.1 ii libpango-1.0-0 1.36.8-2 ii libpangocairo-1.0-0 1.36.8-2 ii libpangoft2-1.0-01.36.8-2 ii libsm6 2:1.2.1-2 ii libx11-6 2:1.6.2-3 ii libxext6 2:1.3.3-1 ii libxi6 2:1.7.4-1 ii libxinerama1 2:1.1.3-1 ii libxml2 2.9.2+dfsg1-1 ii libxmu6 2:1.1.1-1 ii libxpm4 1:3.5.10-1 ii libxrandr2 2:1.4.2-1 ii libxrender1 1:0.9.8-1 ii libxt6 1:1.1.3-1+deb7u1 ii libxxf86vm1 1:1.1.3-1 ii xscreensaver-data5.15-3 Versions of packages xscreensaver recommends: ii libjpeg-progs 8d-1+deb7u1 ii perl [perl5] 5.20.1-2 ii wamerican [wordlist] 7.1-1 Versions of packages xscreensaver suggests: ii chromium [www-browser] 37.0.2062.120-1~deb7u1 pn fortune none pn gdm3 | kdm-gdmcompat none ii iceweasel [www-browser] 31.2.0esr-2 ii lynx-cur [www-browser] 2.8.8dev.12-2 ii opera [www-browser] 12.16.1860 pn qcam | streamer none ii w3m [www-browser]0.5.3-8 pn xdaliclock none pn xfishtanknone pn xscreensaver-gl none - -- no debconf information - -- debsums errors found: sh: 1: /usr/sbin/dpkg-divert: not found -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlROhA8ACgkQ10rqkowbIsmpZACfXv7OS9DERgkf2AjtuaAhQqL1 /KEAn2eDVbDBZ5sot0O0Mkcjly1xVKPy =R0bh -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#683854: solr-jetty: latest security fix made the symlink bug reappear
Package: solr-jetty Version: 3.6.0+dfsg-1+deb7u1 Followup-For: Bug #683854 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear Maintainer, the fix for bug #683854 seems to be missing in 3.6.0+dfsg-1+deb7u1 Installing this security fix breaks solr: lrwxrwxrwx 1 root root 22 Jun 16 19:51 /var/lib/jetty/webapps/solr - /usr/share/solr/webapp bjorn@canardo:~$ ls -l /usr/share/solr total 8 drwxr-xr-x 2 root root 4096 Jun 23 06:46 bin lrwxrwxrwx 1 root root 14 Jun 21 2012 conf - /etc/solr/conf lrwxrwxrwx 1 root root 18 Jun 21 2012 data - /var/lib/solr/data lrwxrwxrwx 1 root root 13 Jun 21 2012 logs - /var/log/solr lrwxrwxrwx 1 root root3 Jun 21 2012 scripts - bin lrwxrwxrwx 1 root root 18 Jun 16 19:51 solr.xml - /etc/solr/solr.xml drwxr-xr-x 4 root root 4096 Jun 24 12:49 web Bjørn - -- System Information: Debian Release: 7.5 APT prefers stable APT policy: (990, 'stable'), (699, 'proposed-updates'), (600, 'unstable'), (500, 'stable-updates'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-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/bash Versions of packages solr-jetty depends on: ii jetty6.1.26-1 ii libjetty-extra-java 6.1.26-1 ii solr-common 3.6.0+dfsg-1+deb7u1 solr-jetty recommends no packages. solr-jetty suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlOpWvQACgkQ10rqkowbIskgIACfV6JBEMrTVKKYKtOE3KgOtdTx vOYAni83/UU3Wq0mwy45UIFe+Mz5E5pg =Epiu -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#701953: initramfs-tools: Missing modules prevent passphrase entry with usb keyboard
Ben Caradoc-Davies ben.caradoc-dav...@csiro.au writes: Package: initramfs-tools Version: 0.109 Severity: critical Justification: breaks the whole system Others will have to decide on that, but it seems a bit high to me. This is an experimental kernel and you do hopefully not try to install it without keeping a working version as well? I have a usb keyboard attached to a system with an unencrypted /boot and a LUKS-encrypted partition (LVM physical volume) containing the other filesystems. Today I installed linux-image-3.8-trunk-amd64 (3.8-1~experimental.1). initramfs-tools created a corresponding initrd, as expected. Booting this kernel/initrd in grub2 resulted in a plymouth passphrase entry screen, but a usb keyboard that did not work in any port. All keyboard lights were off. The system was thus unbootable without a non-usb keyboard (hence critical severity). Without a non-usb keyboard or backup grub entry (3.7 kernel with working initrd), I would have been unable to access my system without rescue media. This is a regression from the behaviour of initramfs-tools with linux-image-3.7 -trunk-amd64 (3.7.8-1~experimental.1). The failure appears identical to this: http://linux-kernel.2935.n7.nabble.com/PROBLEM-3-8-0-rc4-keyboard-failure-at- boot-tp585937p587518.html Workaround is to add the following modules to /etc/initramfs-tools/modules, as described in the link above: ehci_pci Right. This is quite possibly a result of this bug: http://bugs.debian.org/700572 Bjørn -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#610332: /etc/pm/sleep.d/60aiccu hook may cause unacceptable resume delays
Package: aiccu Version: 20070115-14 Severity: critical Justification: breaks unrelated software -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The /etc/pm/sleep.d/60aiccu pm-utils hook may cause extremely slow resume from sleep. aiccu should not need to touch anything on resume. If it does, then that is just a symptom of a bug in the daemon. The current hook script will try to look up a name in DNS and ping over the aiccu interface, preventing the system from fully resuming while trying. Both actions may take a significant time to finish. Both actions will be attempted even if aiccu has been disabled in /etc/default/aiccu pm-utils is totally unrelated to aiccu. Breaking pm-utils, even if it is done by exploiting hook functionaly missing a proper policy, is unacceptable. Bjørn - -- System Information: Debian Release: 6.0 APT prefers testing APT policy: (990, 'testing'), (600, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 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 aiccu depends on: ii debconf [debconf-2.0] 1.5.36 Debian configuration management sy ii iproute 20100519-3 networking and traffic control too ii iputils-ping3:20100418-3 Tools to test the reachability of ii iputils-tracepath 3:20100418-3 Tools to trace the network path to ii libc6 2.11.2-7 Embedded GNU C Library: Shared lib ii libgnutls26 2.8.6-1 the GNU TLS library - runtime libr ii lsb-base3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip ii ucf 3.0025+nmu1 Update Configuration File: preserv Versions of packages aiccu recommends: ii bind9-host 1:9.7.2.dfsg.P3-1Version of 'host' bundled with BIN ii dnsutils1:9.7.2.dfsg.P3-1Clients provided with BIND ii ntp 1:4.2.6.p2+dfsg-1+b1 Network Time Protocol daemon and u ii ntpdate 1:4.2.6.p2+dfsg-1+b1 client for setting system time fro aiccu suggests no packages. - -- Configuration Files: /etc/aiccu.conf [Errno 13] Permission denied: u'/etc/aiccu.conf' /etc/default/aiccu changed: BACKGROUND=false OPTIONS= AICCU_ENABLED=No - -- debconf information excluded -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAk00e2AACgkQ10rqkowbIsnI8ACfZ1XEXQEPMk2tYk4Hk8+EqMJr 28IAnRPXwFXdaczCLPbnPPRyVcjQdg0r =Ivw0 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#610333: unattended-upgrades: delaying hibernation until crob job finishes is unacceptable
Package: unattended-upgrades Version: 0.62.2 Severity: critical Justification: breaks unrelated software -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The hook /etc/pm/sleep.d/10_unattended-upgrades-hibernate deliberately breaks pm-utils by preventing the system from hibernating while unattended-upgrades is running. There is absolutely *no* relation between unattended-upgrades and pm-utils. Any process running at the time of hibernation could consider itself just as important as unattended-upgrades, thereby preventing the system from ever hibernating. Please refrain from abusing such hook interfaces, even if they lack a proper policy. Thanks. Bjørn - -- System Information: Debian Release: 6.0 APT prefers testing APT policy: (990, 'testing'), (600, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 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 unattended-upgrades depends on: ii apt 0.8.10 Advanced front-end for dpkg ii apt-utils 0.8.10 APT utility programs ii debconf [debconf-2.0] 1.5.36 Debian configuration management sy ii lsb-release 3.2-23.2squeeze1 Linux Standard Base version report ii python 2.6.6-3+squeeze5 interactive high-level object-orie ii python-apt 0.7.100.1Python interface to libapt-pkg ii ucf 3.0025+nmu1 Update Configuration File: preserv unattended-upgrades recommends no packages. Versions of packages unattended-upgrades suggests: ii bsd-mailx 8.1.2-0.20100314cvs-1 simple mail user agent - -- debconf information: unattended-upgrades/enable_auto_updates: false -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAk00fLwACgkQ10rqkowbIsnYswCeJQ+BcL+ELoAYC1Wewj6gmNcH FJwAn2pZMC64WsyEPP1N6EG+Qi5MMJ3i =+cVT -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#607436: totem-coherence: 'Coherence DLNA/UPnP Client' plugin cannot be enabled
Package: totem-coherence Version: 2.30.2-5 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Just installed totem and totem-coherence: The following NEW packages will be installed: totem totem-coherence 0 upgraded, 2 newly installed, 0 to remove and 10 not upgraded. Need to get 800 kB of archives. After this operation, 1,921 kB of additional disk space will be used. Do you want to continue [Y/n]? Get:1 http://ftp.no.debian.org/debian/ squeeze/main totem amd64 2.30.2-5 [696 kB] Get:2 http://ftp.no.debian.org/debian/ squeeze/main totem-coherence all 2.30.2-5 [104 kB] Fetched 800 kB in 2s (324 kB/s) Selecting previously deselected package totem. (Reading database ... 194227 files and directories currently installed.) Unpacking totem (from .../totem_2.30.2-5_amd64.deb) ... Selecting previously deselected package totem-coherence. Unpacking totem-coherence (from .../totem-coherence_2.30.2-5_all.deb) ... Processing triggers for menu ... Processing triggers for gnome-menus ... Processing triggers for desktop-file-utils ... Setting up totem (2.30.2-5) ... Setting up totem-coherence (2.30.2-5) ... Processing triggers for menu ... Started totem and selected Edit-Plugins and tried checking Enabled in front of the listed 'Coherence DLNA/UPnP Client' plugin. This resulted in the following terminal output and a modal popup dialog box stating the same with slightly different wording, and nothing more: (totem:21163): Totem-WARNING **: Could not import Python module 'totem', check your installation ImportError: No module named totem (totem:21163): Totem-WARNING **: Could not load plugin coherence_upnp (totem:21163): Totem-WARNING **: Error, impossible to activate plugin 'Coherence DLNA/UPnP Client' So the plugin does not work at all. Hence the severity. Please fix or remove from squeeze. Thanks Bjørn - -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (600, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 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 totem-coherence depends on: ii python 2.6.6-3+squeeze2 interactive high-level object-orie ii python-coherence0.6.6.2-5Python UPnP framework ii python-gtk2 2.17.0-4 Python bindings for the GTK+ widge ii python-support 1.0.10 automated rebuilding support for P ii totem 2.30.2-5 A simple media player for the GNOM ii totem-common2.30.2-5 Data files for the Totem media pla totem-coherence recommends no packages. totem-coherence suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAk0MswIACgkQ10rqkowbIskChgCbBZ63QxvowTX+6zCaRceyOydI jUEAnjB4rie7owqpJ1T3OXke/2VJYd5+ =7/Rn -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#607436: totem-coherence: should depend on totem-plugins
Installing totem-plugins seems to fix this problem, so it's merely a missing dependency. Allthesame, this needs to be fixed for totem-coherence to be in a releasable state. Bjørn -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#598432: python-apt: upgrade fails
I also faced the same problem as Cameron after modifying
/usr/share/pycentral-data/pyversions.py to allow single digit version
numbers with this patch:
--- /usr/share/pycentral-data/pyversions.py.orig2010-09-29
12:10:27.0 +0200
+++ /usr/share/pycentral-data/pyversions.py 2010-09-29 12:11:04.0
+0200
@@ -54,7 +54,7 @@
vinfo['current'] = field
continue
vinfo.setdefault('versions', set())
-ve = re.compile('(=|=||=)? *(\d\.\d)$')
+ve = re.compile('(=|=||=)? *(\d(?:\.\d)?)$')
m = ve.match(field)
try:
op, v = m.group(1), m.group(2)
The following errors alle seem to be caused by print being changed
from statement to function in python3:
http://docs.python.org/release/3.0.1/whatsnew/3.0.html#print-is-a-function
Setting up python-apt (0.7.98) ...
Compiling /usr/lib/python3/dist-packages/apt/debfile.py ...
SyntaxError: ('invalid syntax',
('/usr/lib/python3/dist-packages/apt/debfile.py', 575, 28, '
print(msg, file=sys.stderr)\n'))
Compiling /usr/lib/python3/dist-packages/apt/progress/gtk2.py ...
SyntaxError: ('invalid syntax',
('/usr/lib/python3/dist-packages/apt/progress/gtk2.py', 510, 47, '
print(Exception happened:, exc, file=sys.stderr)\n'))
Compiling /usr/lib/python3/dist-packages/apt/progress/old.py ...
SyntaxError: ('invalid syntax',
('/usr/lib/python3/dist-packages/apt/progress/old.py', 158, 32, '
print(\\r%s % (s), end=\' \')\n'))
pycentral: pycentral pkginstall: error byte-compiling files (17)
pycentral pkginstall: error byte-compiling files (17)
I have no idea how this should be handled to actually support both
python 2.x and python 3.x, but this patch does at least let me install
python-apt (0.7.98) without errors (but do note that it removes the
progress indicator in old.py):
--- /usr/lib/python3/dist-packages/apt/debfile.py.orig 2010-09-28
16:56:50.0 +0200
+++ /usr/lib/python3/dist-packages/apt/debfile.py 2010-09-29
12:16:14.0 +0200
@@ -572,7 +572,7 @@
def _dbg(self, level, msg):
Write debugging output to sys.stderr.
if level = self.debug:
-print(msg, file=sys.stderr)
+sys.stderr.write(msg)
def install(self, install_progress=None):
Install the package.
--- /usr/lib/python3/dist-packages/apt/progress/gtk2.py.orig2010-09-28
16:56:52.0 +0200
+++ /usr/lib/python3/dist-packages/apt/progress/gtk2.py 2010-09-29
12:16:51.0 +0200
@@ -507,7 +507,7 @@
try:
cache.commit(apt_progress.acquire, apt_progress.install)
except Exception as exc:
-print(Exception happened:, exc, file=sys.stderr)
+sys.stderr.write(Exception happened:, exc)
if len(sys.argv) 1:
deb = DebPackage(sys.argv[1], cache)
deb.install(apt_progress.dpkg_install)
--- /usr/lib/python3/dist-packages/apt/progress/old.py.orig 2010-09-28
16:56:51.0 +0200
+++ /usr/lib/python3/dist-packages/apt/progress/old.py 2010-09-29
12:27:39.0 +0200
@@ -153,9 +153,10 @@
s = [%2.f%%] %sB/s %s % (self.percent,
apt_pkg.size_to_str(int(self.currentCPS)),
apt_pkg.time_to_str(int(self.eta)))
-else:
-s = %2.f%% [Working] % (self.percent)
-print(\r%s % (s), end=' ')
+
+#else:
+#s = %2.f%% [Working] % (self.percent)
+#print(\r%s % (s), end=' ')
sys.stdout.flush()
return True
Bjørn (I have not python clue whatsoever, and I intend to continue like that)
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#595502: closed by Ben Hutchings b...@decadent.org.uk (Re: Bug#595502: linux-image-2.6.32-5-mckinley: panics while loading INIT, IOMMU out of mapping resources)
Thibaut VARENE vare...@debian.org writes: Please find attached the dmesg pertaining to this wonderful disaster. What it doesn't show is the fact that I also saw the endless /sys/devices enumeration during this boot. That's probably an unrelated bug in mdadm: http://bugs.debian.org/594418 Fixed in mdadm/3.1.4-1 Bjørn -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#593250: libcap2-bin: needs versioned dependency on libpam-runtime
Package: libcap2-bin Version: 1:2.19-2 Severity: serious Justification: Policy 3.5 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 During an partial upgrade from lenny to squeeze: Setting up libcap2-bin (1:2.19-2) ... /var/lib/dpkg/info/libcap2-bin.postinst: line 23: pam-auth-update: command not found dpkg: error processing libcap2-bin (--configure): subprocess installed post-installation script returned error exit status 127 A little digging told me that this command is supposed to be provided by libpam-runtime, and that I needed a newer version than the installed lenny version: libpam-runtime: Installed: 1.0.1-5+lenny1 Candidate: 1.0.1-5+lenny1 Version table: 1.1.1-4 0 600 http://ftp.no.debian.org sid/main Packages 1.1.1-3 0 650 http://ftp.no.debian.org squeeze/main Packages *** 1.0.1-5+lenny1 0 700 http://ftp.no.debian.org lenny/main Packages 100 /var/lib/dpkg/status This means that libcap2-bin must declare a versioned dependency on libpam-runtime according to policy 3.5 Bjørn - -- System Information: Debian Release: squeeze/sid APT prefers stable APT policy: (700, 'stable'), (650, 'testing'), (600, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-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/bash Versions of packages libcap2-bin depends on: ii libc6 2.11.2-2 Embedded GNU C Library: Shared lib ii libcap2 2.11-2 support for getting/setting POSIX. ii libpam0g 1.1.1-3Pluggable Authentication Modules l libcap2-bin recommends no packages. Versions of packages libcap2-bin suggests: pn libcap-devnone (no description available) - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkxpbbEACgkQ10rqkowbIsm49ACfbYxXXbANOBoc+v2Q9+m2nUsj ouEAn2v4S7IDA/0kJ+6oFH4RrMOgubpb =m61W -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#588426: [gmane.linux.kernel] Re: [patch 134/149] x86, paravirt: Add a global synchronization point for pvclock
I assume you will pick this up, but I thought I might as well record it
in the bug report as well...
New fix from Linus. For the *real* problem this time, I assume.
Bjørn
---BeginMessage---
On Tue, 13 Jul 2010, Linus Torvalds wrote:
On Tue, Jul 13, 2010 at 10:50 AM, Linus Torvalds
torva...@linux-foundation.org wrote:
No, you didn't back-port it wrong. I just didn't fix the right part. I
thought the PV code used xchg, not cmpxchg, so I only patched that.
But cmpxchg has the exact same issue.
Does this fix it?
It appears to, thanks a lot.
[git|v2.6.32.16] wea...@thelma:/scratch/kernel/2.6.32.16$ nm
arch/x86/kernel/pvclock.o
b last_value
..
And it did boot too.
Btw, this second patch was a bit more aggressive than the first one,
and actually removes the memory clobber entirely, and the fake cast
of the target type.
Without the cast gcc spews a fair amount of warnings. About four every
time it hits the include file.
Just for completeness' sake I attached the patch on top of 2.6.32.16
that I built with.
--
| .''`. ** Debian GNU/Linux **
Peter Palfrader | : :' : The universal
http://www.palfrader.org/ | `. `' Operating System
| `-http://www.debian.org/
diff --git a/arch/x86/include/asm/cmpxchg_64.h
b/arch/x86/include/asm/cmpxchg_64.h
index 52de72e..f0551c5 100644
--- a/arch/x86/include/asm/cmpxchg_64.h
+++ b/arch/x86/include/asm/cmpxchg_64.h
@@ -26,26 +26,26 @@ static inline unsigned long __xchg(unsigned long x,
volatile void *ptr,
switch (size) {
case 1:
asm volatile(xchgb %b0,%1
-: =q (x)
-: m (*__xg(ptr)), 0 (x)
+: =q (x), +m (*__xg(ptr))
+: 0 (x)
: memory);
break;
case 2:
asm volatile(xchgw %w0,%1
-: =r (x)
-: m (*__xg(ptr)), 0 (x)
+: =r (x), +m (*__xg(ptr))
+: 0 (x)
: memory);
break;
case 4:
asm volatile(xchgl %k0,%1
-: =r (x)
-: m (*__xg(ptr)), 0 (x)
+: =r (x), +m (*__xg(ptr))
+: 0 (x)
: memory);
break;
case 8:
asm volatile(xchgq %0,%1
-: =r (x)
-: m (*__xg(ptr)), 0 (x)
+: =r (x), +m (*__xg(ptr))
+: 0 (x)
: memory);
break;
}
@@ -66,28 +66,24 @@ static inline unsigned long __cmpxchg(volatile void *ptr,
unsigned long old,
unsigned long prev;
switch (size) {
case 1:
- asm volatile(LOCK_PREFIX cmpxchgb %b1,%2
-: =a(prev)
-: q(new), m(*__xg(ptr)), 0(old)
-: memory);
+ asm volatile(LOCK_PREFIX cmpxchgb %b2,%1
+: =a(prev), +m (*__xg(ptr))
+: q(new), 0(old));
return prev;
case 2:
- asm volatile(LOCK_PREFIX cmpxchgw %w1,%2
-: =a(prev)
-: r(new), m(*__xg(ptr)), 0(old)
-: memory);
+ asm volatile(LOCK_PREFIX cmpxchgw %w2,%1
+: =a(prev), +m (*__xg(ptr))
+: r(new), 0(old));
return prev;
case 4:
- asm volatile(LOCK_PREFIX cmpxchgl %k1,%2
-: =a(prev)
-: r(new), m(*__xg(ptr)), 0(old)
-: memory);
+ asm volatile(LOCK_PREFIX cmpxchgl %k2,%1
+: =a(prev), +m (*__xg(ptr))
+: r(new), 0(old));
return prev;
case 8:
- asm volatile(LOCK_PREFIX cmpxchgq %1,%2
-: =a(prev)
-: r(new), m(*__xg(ptr)), 0(old)
-: memory);
+ asm volatile(LOCK_PREFIX cmpxchgq %2,%1
+: =a(prev), +m (*__xg(ptr))
+: r(new), 0(old));
return prev;
}
return old;
---End Message---
Bug#588426: linux-image-2.6.32-5-amd64: fail to boot in a kvm virtual machine
Ben Hutchings b...@decadent.org.uk writes:
On Mon, 2010-07-12 at 10:22 +0200, Bjørn Mork wrote:
But I must admit that I was a bit surprised when 2.6.32-17 was uploaded
without a fix for this problem. It makes me wonder if the severity
shouldn't have been higher after all Just to be clear: This bug
does break all KVM based systems, making them completely unbootable, and
requiring console access to fix. I'm pretty sure there are plenty of
KVM based hosting solutions around where this will be a severe problem.
I haven't seen a fix for it yet.
Ah, sorry, I thought the fix was clear from the bug report:
Peter Palfrader has bisected it down to commit 1345126c
x86, paravirt: Add a global synchronization point for pvclock
which sounds very reasonable, IMHO. See
http://lkml.indiana.edu/hypermail/linux/kernel/1007.0/02385.html
To be absolutely sure this is correct, I just built a kernel based on
your 2.6.32-17 with commit 1345126c reverted, and that does indeed boot
under KVM. The revert patch is attached. Please try it.
I do hope this goes into next 2.6.32-stable as well, although the
discussion following Peter Palfrader's bisect seems a bit discouraging.
that patch shouldn't affect anything outside... Right. Well, it
does. So please revert it in stable.
Thanks,
Bjørn
From 5ffe322b5f3a76969525bf2cff3f029297179f27 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Bj=C3=B8rn=20Mork?= bj...@mork.no
Date: Mon, 12 Jul 2010 13:23:57 +0200
Subject: [PATCH] Revert x86, paravirt: Add a global synchronization point for pvclock
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
This reverts commit 1345126c761f0360dc108973bf73281d51945bc1.
Signed-off-by: Bjørn Mork bj...@mork.no
---
arch/x86/kernel/pvclock.c | 24
1 files changed, 0 insertions(+), 24 deletions(-)
diff --git a/arch/x86/kernel/pvclock.c b/arch/x86/kernel/pvclock.c
index dfdfe46..03801f2 100644
--- a/arch/x86/kernel/pvclock.c
+++ b/arch/x86/kernel/pvclock.c
@@ -109,14 +109,11 @@ unsigned long pvclock_tsc_khz(struct pvclock_vcpu_time_info *src)
return pv_tsc_khz;
}
-static atomic64_t last_value = ATOMIC64_INIT(0);
-
cycle_t pvclock_clocksource_read(struct pvclock_vcpu_time_info *src)
{
struct pvclock_shadow_time shadow;
unsigned version;
cycle_t ret, offset;
- u64 last;
do {
version = pvclock_get_time_values(shadow, src);
@@ -126,27 +123,6 @@ cycle_t pvclock_clocksource_read(struct pvclock_vcpu_time_info *src)
barrier();
} while (version != src-version);
- /*
- * Assumption here is that last_value, a global accumulator, always goes
- * forward. If we are less than that, we should not be much smaller.
- * We assume there is an error marging we're inside, and then the correction
- * does not sacrifice accuracy.
- *
- * For reads: global may have changed between test and return,
- * but this means someone else updated poked the clock at a later time.
- * We just need to make sure we are not seeing a backwards event.
- *
- * For updates: last_value = ret is not enough, since two vcpus could be
- * updating at the same time, and one of them could be slightly behind,
- * making the assumption that last_value always go forward fail to hold.
- */
- last = atomic64_read(last_value);
- do {
- if (ret last)
- return last;
- last = atomic64_cmpxchg(last_value, last, ret);
- } while (unlikely(last != ret));
-
return ret;
}
--
1.7.1
Bug#561124: This bug breaks existing user created scripts
severity 561124 grave thanks Justification: renders package mostly unusable I'm currently pulling a few packages from testing and/or unstable into a stable system to get some new features. One of these is lldpd, which now depends on libsnmp15 (= 5.4.2.1~dfsg). Seeing that this could be pulled without any larger dependency problem, I decided to install it. I was really surprised to see that it is actually deliberately broken and has been so for a month, even allowing it to enter testing. Please try to run e.g. perl -MSNMP -e 'new SNMP::Session()' on a system with no MIBs and see the generated noise. Never mind that the change breaks any script the users may have created with symbolic OID names. Can we please agree that this currently is in no way suitable for release? The change should never have made it into testing without snmp-mibs-downloader being available. Too late for that, but let's ensure that it won't be in a Debian release. Hence this message. Bjørn -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#537569: This is most likely fixed in newer KVM versions
There seems to be two problems with -no-shutdown in kvm-85:
1) in qemu mode (-no-kvm), we first hit
if (shutdown_requested) {
ret = EXCP_INTERRUPT;
if (no_shutdown) {
vm_stop(0);
no_shutdown = 0;
}
else
break;
}
while vm_running is true. This resets no_shutdown, but does *not* reset
shutdown_requested. The vm_stop(0) makes us hit the
} else {
if (shutdown_requested) {
ret = EXCP_INTERRUPT;
break;
}
timeout = 5000;
}
on next loop iteration and the loop exits. The obvious fix is to reset
shutdown_requested on test, by e.g. replacing it with
qemu_shutdown_requested()
2) with kvm enabled, there doesn't seem to be any handling of
-no-shutdown at all. the kvm_main_loop will break unconditionally if
qemu_shutdown_requested() is true:
while (1) {
main_loop_wait(1000);
if (qemu_shutdown_requested())
break;
I don't provide any patches for these problems, as the code is
refactored in newer KVM versions and both problems most likely are gone
there. Fixing kvm-85 seems futile. Please upgrade kvm in unstable to the
latest and greatest instead (qemu-kvm-0.11.0-rc1 or newer). It has this
in it's kvm_main_loop():
if (qemu_shutdown_requested()) {
if (qemu_no_shutdown()) {
vm_stop(0);
} else
break;
}
Bjørn
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524858: hal-info puts configuration files in /usr/share
Package: hal-info Version: 20090309-1 Severity: serious Justification: Policy 10.7.2 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 hal-info contains a mix of hardware dependent quirks and system dependent configuration, all of which are placed in /usr/share/hal. The files /usr/share/hal/fdi/information/10freedesktop/30-keymap-* are all examples of files matching the definition of a configuration file in Debian (policy 10.7.1): A file that affects the operation of a program, or provides site- or host-specific information, or otherwise customizes the behavior of a program. Typically, configuration files are intended to be modified by the system administrator (if needed or desired) to conform to local policy or to provide more useful site-specific behavior. Policy require such files to reside in /etc. My suggestion would be to move them to /usr/share/doc/hal-info/examples and only keep strict quirks in /usr/share/hal. Bjørn - -- System Information: Debian Release: 5.0.1 APT prefers stable APT policy: (700, 'stable'), (600, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.29-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAknsXUIACgkQ10rqkowbIsnnzgCeNjo6TlvxqSH7voDKP0+FRJs1 D7wAniwHqpLkBAxUWYVAVQEgWfMsnuAz =mOJ6 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#516734: linux-headers-2.6.28-1-amd64: Dependency on linux-kbuild-2.6.28 cannot be meet
The following message is a courtesy copy of an article that has been posted to gmane.linux.debian.devel.kernel as well. Nikolay A. Panov debian-bugrep...@niksite.ru writes: I cannot install linux-header-2.6.18-1-amd64 package sice it depends on linux-kbuild-2.6.28 package which is not in repository. Any hope of getting this fixed? I'd really like to build a few modules for this kernel. Bjørn -- I couldn't care less about your system call -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#513235: gnome-keyring: selects wrong key when multiple ssh identities are used
Package: gnome-keyring Version: 2.22.3-2 Severity: critical Tags: security Justification: breaks unrelated software -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 /usr/bin/gnome-keyring-daemon breaks ssh as detailed below, justifying critical severity. The breakage may lead to information leakage due to the unexpected behaviour it causes for ssh. I regularily log into a system which uses different ssh keys to select different configurations. This fails if gnome-keyring-daemon is running. It seems to use previously learned keys even if you specify ssh -i keyfile, or use the IdentityFile keyword in ~/.ssh/config. Example ssh session with gnome-keyring-daemon (after already authenticating with the remote server using another key): bj...@nemi:~$ ssh -v rocs2 OpenSSH_5.1p1 Debian-5, OpenSSL 0.9.8g 19 Oct 2007 debug1: Reading configuration data /home/bjorn/.ssh/config debug1: Applying options for rocs2 debug1: Applying options for * debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to login.example.com [10.1.1.82] port 22. debug1: Connection established. debug1: identity file /home/bjorn/.ssh/key2 type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_4.5 debug1: match: OpenSSH_4.5 pat OpenSSH_4* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.1p1 Debian-5 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server-client aes128-cbc hmac-md5 z...@openssh.com debug1: kex: client-server aes128-cbc hmac-md5 z...@openssh.com debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(102410248192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Host 'login.example.com' is known and matches the DSA host key. debug1: Found key in /home/bjorn/.ssh/known_hosts:15 debug1: ssh_dss_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,keyboard-interactive debug1: Next authentication method: publickey debug1: Offering public key: debug1: Server accepts key: pkalg ssh-dss blen 434 debug1: Enabling compression at level 6. debug1: Authentication succeeded (publickey). Notice the difference after stopping gnome-keyring-daemon: bj...@nemi:~$ ssh -v rocs2 OpenSSH_5.1p1 Debian-5, OpenSSL 0.9.8g 19 Oct 2007 debug1: Reading configuration data /home/bjorn/.ssh/config debug1: Applying options for rocs2 debug1: Applying options for * debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to login.example.com [10.1.1.82] port 22. debug1: Connection established. debug1: identity file /home/bjorn/.ssh/key2 type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_4.5 debug1: match: OpenSSH_4.5 pat OpenSSH_4* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.1p1 Debian-5 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server-client aes128-cbc hmac-md5 z...@openssh.com debug1: kex: client-server aes128-cbc hmac-md5 z...@openssh.com debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(102410248192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Host 'login.example.com' is known and matches the DSA host key. debug1: Found key in /home/bjorn/.ssh/known_hosts:115 debug1: ssh_dss_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,keyboard-interactive debug1: Next authentication method: publickey debug1: Trying private key: /home/bjorn/.ssh/key2 debug1: read PEM private key done: type DSA debug1: Remote: Adding to environment: SSH_TARGET=key2 debug1: Enabling compression at level 6. debug1: Authentication succeeded (publickey). Notice how the second example actually uses the key key2, which causes the server to set a specific environment. I don't know if it's necessary to mention this, but the fact that a clean Debian installation will run gnome-keyring-daemon by default, and that the manpage of gnome-keyring-daemon doesn't mention it's ssh-agent behaviour at all, makes it all worse. Trying to find out which part of the system was breaking ssh was quite an adventure, and I guess I would have given up making ssh work again if I didn't know that ssh was working on a lenny system using KDM instead if GDM. Please fix before releasing lenny. Or at least disable gnome-keyring-daemon on default installations. Thanks, Bjorn - -- System Information: Debian Release: 5.0 APT prefers testing
Bug#508259: linux-image-2.6.18-6-k7: Local kernel panic exploit
Kuba Plichcinski [EMAIL PROTECTED] writes: Package: linux-image-2.6.18-6-k7 Version: 2.6.18.dfsg.1-23 Severity: critical Tags: security Justification: breaks the whole system These exploit freezess all my Debian/Ubuntu machines: http://www.milw0rm.com/exploits/7091 See http://security-tracker.debian.net/tracker/CVE-2008-5029 You could consider upgrading to linux-image-2.6.24-etchnhalf.1-686 version 2.6.24-6~etchnhalf.7 or later if you don't want for the fix backport to 2.6.18. Bjørn -- return -ENOCOFFEE; -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#502128: grub-pc: Crashes with 'free magic is broken...' if entries in grub.cfg happens to be a multiple of 64 bytes
Package: grub-pc
Version: 1.96+20080724-10
Severity: grave
Justification: renders package unusable
A system became unbootable after installing a new kernel without making any
other i
changes. grub just reported:
free magic is broken at 0x90c00: 0x2e647362
The reason seems to be as obscure as the length of the kernel image name. This
caused
one of the lines in the new grub.cfg to be exactly 128 bytes (there are two
tab's here):
linux /boot/vmlinuz-2.6.27-git-ahci-1-amd64
root=UUID=0ebb368d-b15e-4796-9029-9adfced061a0 ro console=tty0
console=ttyS0,9600n8
and this again caused grub to crash. Changing the entry by e.g adding a space
will make
the system bootable again, but I still feel this justifies a grave severity
given the
need to boot from some other medium to fix the error. And not to mention the
complete
unexpected side effect of a kernel image name...
Google told me that the bug has been reported to grub-devel with a patch:
http://lists.gnu.org/archive/html/grub-devel/2008-07/msg00601.html
I believe this needs to be fixed before lenny is released. Thanks.
Bjorn
-- Package-specific info:
*** BEGIN /proc/mounts
/dev/disk/by-uuid/0ebb368d-b15e-4796-9029-9adfced061a0 / ext3
rw,errors=remount-ro,data=ordered 0 0
*** END /proc/mounts
*** BEGIN /boot/grub/device.map
(hd0) /dev/sda
(hd0) /dev/hda
*** END /boot/grub/device.map
*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/update-grub using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
insmod serial
set default=0
set timeout=5
serial --unit=0 --speed=9600
terminal serial
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_hurd ###
### END /etc/grub.d/10_hurd ###
### BEGIN /etc/grub.d/10_linux ###
set root=(hd0,1)
search --fs-uuid --set 0ebb368d-b15e-4796-9029-9adfced061a0
menuentry Debian GNU/Linux, linux 2.6.27-git-ahci-1-amd64 {
linux /boot/vmlinuz-2.6.27-git-ahci-1-amd64
root=UUID=0ebb368d-b15e-4796-9029-9adfced061a0 ro console=tty0
console=ttyS0,9600n8
initrd /boot/initrd.img-2.6.27-git-ahci-1-amd64
}
menuentry Debian GNU/Linux, linux 2.6.27-git-ahci-1-amd64 (single-user mode) {
linux /boot/vmlinuz-2.6.27-git-ahci-1-amd64
root=UUID=0ebb368d-b15e-4796-9029-9adfced061a0 ro single console=tty0
console=ttyS0,9600n8
initrd /boot/initrd.img-2.6.27-git-ahci-1-amd64
}
menuentry Debian GNU/Linux, linux 2.6.26-1-amd64 {
linux /boot/vmlinuz-2.6.26-1-amd64
root=UUID=0ebb368d-b15e-4796-9029-9adfced061a0 ro console=tty0
console=ttyS0,9600n8
initrd /boot/initrd.img-2.6.26-1-amd64
}
menuentry Debian GNU/Linux, linux 2.6.26-1-amd64 (single-user mode) {
linux /boot/vmlinuz-2.6.26-1-amd64
root=UUID=0ebb368d-b15e-4796-9029-9adfced061a0 ro single console=tty0
console=ttyS0,9600n8
initrd /boot/initrd.img-2.6.26-1-amd64
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file is an example on how to add custom entries
### END /etc/grub.d/40_custom ###
*** END /boot/grub/grub.cfg
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.27-git-ahci-1-amd64 (SMP w/1 CPU core)
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 grub-pc depends on:
ii debconf [debconf-2.0] 1.5.22 Debian configuration management sy
ii grub-common 1.96+20080724-10 GRand Unified Bootloader, version
ii libc6 2.7-13 GNU C Library: Shared libraries
ii liblzo2-2 2.03-1 data compression library
ii libncurses5 5.6+20080830-1 shared libraries for terminal hand
grub-pc recommends no packages.
Versions of packages grub-pc suggests:
pn desktop-base none (no description available)
pn os-prober none (no description available)
-- debconf information:
* grub-pc/linux_cmdline:
* grub-pc/chainload_from_menu.lst: false
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#493824: inn: purging /var/lib/news on remove
Package: inn
Version: 1:1.7.2q-36
Severity: critical
Justification: causes serious data loss
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
inn.postrm will do
clean_var_lib() {
echo Purging active file and history data...
rm -f /var/lib/news/active* /var/lib/news/history* \
/var/lib/news/newsgroups
if [ -d /var/lib/news/ ]; then
rmdir --ignore-fail-on-non-empty /var/lib/news/
fi
}
on both remove and purge.
This causes the active file and history data to be lost unless the user
manually made a backup prior to removing inn. The files contain valuable
data which cannot easily be reconstructed. Debian users do expect such
important state to be kept unless a package is purged. Deleting the files
on package removal will cause serious data loss for any user who
haven't read inn.postrm
Please do not call clean_var_lib() on remove. It should only be called
on purge.
I also believe the
echo Remove the news spool in /var/spool/news yourself!
is misplaced, but that can't be justified as critical since it doesn't
cause any data loss. But please also consider moving this line with
comments to the purge target.
Bjorn
- -- System Information:
Debian Release: lenny/sid
APT prefers stable
APT policy: (700, 'stable'), (650, 'testing'), (600, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.25-2-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/bash
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkiYAqcACgkQ10rqkowbIskZHwCbByVt/cEIHrlKeDfT+aKpMb2/
jxYAnA4Rem5DjgmQMkbVcmGoxxs7hrj8
=ML2r
-END PGP SIGNATURE-
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#384426: sendmail-bin: uninstallable due to unavailable libsasl2 (= 2.1.19.dfsg1)
And if you just install libsasl2 2.1.19.dfsg1 from DSA 1155-2, you end up with a number of other failing dependecies: canardo:/tmp# apt-get dist-upgrade Reading Package Lists... Done Building Dependency Tree... Done You might want to run `apt-get -f install' to correct these. The following packages have unmet dependencies: libsasl2-modules: Depends: libsasl2 (= 2.1.19-1.5sarge1) but 2.1.19.dfsg1-0sarge2 is installed libsasl2-modules-gssapi-heimdal: Depends: libsasl2 (= 2.1.19-1.5sarge1) but 2.1.19.dfsg1-0sarge2 is installed libsasl2-modules-kerberos-heimdal: Depends: libsasl2 (= 2.1.19-1.5sarge1) but 2.1.19.dfsg1-0sarge2 is installed E: Unmet dependencies. Try using -f. Bjørn pgpC42DoSSvEO.pgp Description: PGP signature
