Bug#858794: gmime: Tests contain a MIME message with a (presumably non-free) Playboy/Hustler/something photo
Source: gmime
Version: 2.6.22-2
Severity: serious
With package 'ripmime' installed:
$ apt-get source gmime-bin
$ cd gmime-2.6.22/tests/
$ mkdir attachments
$ cd attachments
$ cat ../message-partial.* ../*.eml |ripmime -i -
$ ls -l *.jpg
-rw--- 1 sliedes sliedes 115113 Mar 26 22:45 2377h003.jpg
-rw--- 1 sliedes sliedes 17527 Mar 26 22:45 leonc.jpg
-rw--- 1 sliedes sliedes 45064 Mar 26 22:45 SkipStone-Banner.jpg
The file 2377h003.jpg is a photograph of a scantily clad model
apparently taken by a pornographer named Suze Randall. The photograph,
which "ripmime" unfortunately does not extract fully from the
multipart message (you can build gmime and use tests/test-partial
message-partial.* to combine the parts; the size should be 117415
bytes), contains the copyright notice "(c) 2001 Suze Randall" in the
lower right corner.
The file leonc.jpg is apparently part of a movie poster of the movie
Leon: The Professional and depicts the character "Mathilda", a 12-year
old girl played by Natalie Portman, with a huge gun in her hand.
SkipStone-Banner appears to be a partial banner of an old web browser
("Gtk+ only browser"; I did not inspect what its license is, but did
find a source download link).
Sami
-- System Information:
Debian Release: 9.0
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.10.4 (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
signature.asc
Description: PGP signature
Bug#787956: raising the severity, prevents usage of the multilib packages
On Sat, Nov 26, 2016 at 08:59:34PM +0100, Matthias Klose wrote: > > Can you please provide a clear, from first steps description of what's > > needed and why? > > again, here is the example which you removed: > [...] >^ > compilation terminated. > > The example fails because the zconf.h header is not found. You can see the > list > of the standard include paths when calling gcc with the -v option. It seems to me that Mark is saying that this is not even supposed to work with lib32z1-dev installed, but rather you should have zlib1g-dev:i386 installed (and not doing so is user error). I found this surprising (and wonder what lib32z1-dev is actually for then), but as I don't know how these packages are supposed to work, I won't take a position. I am happy enough that I got things working by installing zlib1g-dev:i386. Sami
Bug#824137: texlive-fonts-extra-doc: trying to overwrite '/usr/share/doc/texlive-doc/latex/mweights/README' from texlive-latex-extra-doc 2015.20160320-1
Package: texlive-fonts-extra-doc Version: 2016.20160512-1 Severity: serious When upgrading texlive-fonts-extra-doc: Preparing to unpack .../texlive-fonts-extra-doc_2016.20160512-1_all.deb ... Unpacking texlive-fonts-extra-doc (2016.20160512-1) over (2015.20160320-1) ... dpkg: error processing archive /var/cache/apt/archives/texlive-fonts-extra-doc_2016.20160512-1_all.deb (--unpack): trying to overwrite '/usr/share/doc/texlive-doc/latex/mweights/README', which is also in package texlive-latex-extra-doc 2015.20160320-1 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Sami -- 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 Mar 20 07:32 /usr/share/texlive/texmf-dist/ls-R -> /var/lib/texmf/ls-R-TEXLIVEDIST ## Config files Warning: texmf.cnf cannot be found with kpsewhich! Warning: fmtutil.cnf cannot be found with kpsewhich! Warning: updmap.cfg cannot be found with kpsewhich! Warning: language.dat cannot be found with kpsewhich! ## Files in /etc/texmf/web2c/ total 8 -rw-r--r-- 1 root root 283 Jun 9 2009 mktex.cnf -rw-r--r-- 1 root root 1464 Apr 26 23:39 texmf.cnf ## md5sums of texmf.d ca40c66f144b4bafc3e59a2dd32ecb9c /etc/texmf/texmf.d/00debian.cnf 055e06548bac99958d8ab2dd1248f2b4 /etc/texmf/texmf.d/80tex4ht.cnf 1df66bc319cec731e202eaf39f5d85e1 /etc/texmf/texmf.d/96JadeTeX.cnf -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.5.2 (SMP w/8 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages texlive-fonts-extra-doc depends on: ii tex-common6.05 ii texlive-base 2015.20160320-1 texlive-fonts-extra-doc recommends no packages. texlive-fonts-extra-doc suggests no packages. Versions of packages tex-common depends on: ii dpkg 1.18.7 ii ucf 3.0036 Versions of packages tex-common suggests: ii debhelper 9.20160403 Versions of packages texlive-fonts-extra-doc is related to: ii tex-common6.05 pn texlive-binaries -- debconf information: tex-common/check_texmf_wrong: tex-common/check_texmf_missing:
Bug#764818: sudo: Silently fails to execute any commands if kernel compiled with !AUDIT
On Sat, Oct 11, 2014 at 04:13:16PM +0300, Sami Liedes wrote:
--- sudo-1.8.11p1.orig/plugins/sudoers/linux_audit.c
+++ sudo-1.8.11p1/plugins/sudoers/linux_audit.c
@@ -57,7 +57,7 @@ linux_audit_open(void)
au_fd = audit_open();
if (au_fd == -1) {
/* Kernel may not have audit support. */
- if (errno != EINVAL errno != EPROTONOSUPPORT errno !=
EAFNOSUPPORT) {
+ if (errno != EINVAL || errno != EPROTONOSUPPORT || errno !=
EAFNOSUPPORT) {
sudo_warn(U_(unable to open audit system));
au_fd = AUDIT_NOT_CONFIGURED;
}
Argh, and my patch is probably wrong too...
Sami
signature.asc
Description: Digital signature
Bug#748618: syslinux-themes-debian: Fails to uninstall: extlinux-update: not found
Package: syslinux-themes-debian Version: 12-3 Severity: serious Uninstalling syslinux-themes-debian fails: Removing syslinux-themes-debian (12-3) ... /var/lib/dpkg/info/syslinux-themes-debian.postrm: 15: /var/lib/dpkg/info/syslinux-themes-debian.postrm: extlinux-update: not found dpkg: error processing package syslinux-themes-debian (--remove): subprocess installed post-removal script returned error exit status 127 It seems that the extlinux package no longer (as of 3:6.03~pre1+dfsg-4) contains /usr/sbin/extlinux-update. Sami -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14.4 (SMP w/8 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages syslinux-themes-debian depends on: pn syslinux-themes-debian-wheezy none syslinux-themes-debian recommends no packages. syslinux-themes-debian suggests no packages. -- no debconf information signature.asc Description: Digital signature
Bug#741758: Patch to make gnu-fdisk build again
tags 741758 + patch thanks Here's a patch to make gnu-fdisk build again against recent readline. Sami --- gnu-fdisk-1.2.5.orig/src/ui.c +++ gnu-fdisk-1.2.5/src/ui.c @@ -1465,7 +1465,7 @@ fdisk_init_ui () #if HAVE_LIBREADLINE rl_initialize (); - rl_attempted_completion_function = (CPPFunction*) fdisk_complete_function; + rl_attempted_completion_function = (rl_completion_func_t *) fdisk_complete_function; #endif /* HAVE_LIBREADLINE */ readline_state.in_readline = 0; signature.asc Description: Digital signature
Bug#721386: blt-dev: trying to overwrite '/usr/share/man/man3/tree.3.gz', which is also in package libbsd-dev 0.6.0-1
Package: blt-dev Version: 2.4z-6 Severity: serious Package does not install: Preparing to replace blt-dev 2.4z-5 (using .../blt-dev_2.4z-6_amd64.deb) ... Unpacking replacement blt-dev ... dpkg: error processing /var/cache/apt/archives/blt-dev_2.4z-6_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man3/tree.3.gz', which is also in package libbsd-dev 0.6.0-1 Sami -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10.9 (SMP w/8 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages blt-dev depends on: iu blt 2.4z-6 ii tcl8.5-dev 8.5.14-2 ii tk8.5-dev 8.5.14-2 blt-dev recommends no packages. Versions of packages blt-dev suggests: pn blt-demo none -- no debconf information signature.asc Description: Digital signature
Bug#630917: qt4-linguist-tools: trying to overwrite '/usr/bin/lupdate-qt4', which is also in package libqt4-dev 4:4.7.3-1
[Cc: to cupt maintainer jackyf, see below] On Mon, Jun 20, 2011 at 12:23:42PM +, Fathi Boudra wrote: Hi, On Sat, Jun 18, 2011 at 6:30 PM, Sami Liedes slie...@cc.hut.fi wrote: Package: qt4-linguist-tools Version: 4:4.7.3-2 Severity: serious It seems qt4-linguist-tools needs a Conflicts: against older libqt4-dev: The upgrade happened smoothly for me. Conflicts isn't needed. See Debian Policy 7.6.1 paragraph and current control: Breaks: libqt4-dev ( 4.7.3-2) Replaces: libqt4-dev ( 4.7.3-2) Interesting (and I'm sorry for wasting your time). I guess this must be a bug in whatever I used to update then. I suspect that was cupt (jackyf: Does cupt handle this Breaks+Replaces case somehow?), but since I'm not sure, I guess it's safest that I just Cc: cupt maintainer, and I guess this bug can be closed. Agreed? Sami signature.asc Description: Digital signature
Bug#630917: qt4-linguist-tools: trying to overwrite '/usr/bin/lupdate-qt4', which is also in package libqt4-dev 4:4.7.3-1
Package: qt4-linguist-tools Version: 4:4.7.3-2 Severity: serious It seems qt4-linguist-tools needs a Conflicts: against older libqt4-dev: Unpacking qt4-linguist-tools (from .../qt4-linguist-tools_4:4.7.3-2_amd64.deb) ... dpkg: error processing //var/cache/apt/archives/qt4-linguist-tools_4:4.7.3-2_amd64.deb (--unpack): trying to overwrite '/usr/bin/lupdate-qt4', which is also in package libqt4-dev 4:4.7.3-1 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Errors were encountered while processing: //var/cache/apt/archives/qt4-linguist-tools_4:4.7.3-2_amd64.deb Sami -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.39.1 (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/dash signature.asc Description: Digital signature
Bug#623470: Configuring kdump-tools fails when there is no crashkernel= in the kernel cmdline
Package: kdump-tools Version: 1.3.7-1 Severity: serious Hi, kdump-tools fails to configure on my laptop: Setting up kdump-tools (1.3.7-1) ... Starting kdump-tools: no crashkernel= parameter in the kernel cmdline ... failed! invoke-rc.d: initscript kdump-tools, action start failed. dpkg: error processing kdump-tools (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: kdump-tools I don't think the command line I used to boot the kernel should prevent a package from configuring. The command line: $ cat /proc/cmdline BOOT_IMAGE=/vmlinuz-2.6.38.3 root=/dev/mapper/rootvg-root ro Sami signature.asc Description: Digital signature
Bug#557091: Still seeing failure after workaround -- bug in latex-cjk-chinese
[Cc:d to #562198 maintainer since talking about that bug too; please
see #557091 for context.]
Hi,
Just to save some debugging time for others who read this bug report
and to keep you informed of this, I still see a somewhat similar
package configuration failure in 2009-6 (the same command failing,
although with a more TeXish and cryptic error message).
Removing the package latex-cjk-chinese resolved the problem and let
latex configure properly.
There already is a bug report (#562198) against latex-cjk-chinese
which I suspect (but am not sure) is this same bug, but this #557091
bug report is generally what you (or at least I) would find when
encountering this problem, so thought the info would be nice here too.
Setting up texlive-base (2009-6) ...
Running mktexlsr. This may take some time... done.
Building format(s) --all --cnffile /etc/texmf/fmt.d/10texlive-base.cnf.
This may take some time...
fmtutil-sys failed. Output has been stored in
/tmp/fmtutil.BBjQ7eFP
Please include this file if you report a bug.
Relevant portions from the log file:
fmtutil: running `luatex -ini -jobname=luatex -progname=luatex luatex.ini' ...
This is LuaTeX, Version beta-0.50.0-2009122509 (INITEX)
[...]
Using a TeX engine with native UTF-8 support.
[...]
(/usr/share/texmf-texlive/tex/generic/hyph-utf8/patterns/hyph-en-gb.tex))
(/usr/share/texmf-texlive/tex/generic/hyph-utf8/loadhyph/loadhyph-en-gb.tex
ASCII Hyphenation Patterns for British English
(/usr/share/texmf-texlive/tex/generic/hyph-utf8/patterns/hyph-en-gb.tex))
! Missing number, treated as zero.
to be read again
\chardef
to be read again
\...@pinyin
\addlanguage ...\chardef \csname r...@#1\endcsname
=#5 \uselanguage {#1}\inpu...
l.311 \addlanguage{pinyin}{pyhyph.tex}{}{}{}
%%% End of file: /etc/texmf/hyph...
?
! Emergency stop.
to be read again
\chardef
to be read again
\...@pinyin
\addlanguage ...\chardef \csname r...@#1\endcsname
=#5 \uselanguage {#1}\inpu...
l.311 \addlanguage{pinyin}{pyhyph.tex}{}{}{}
%%% End of file: /etc/texmf/hyph...
! == Fatal error occurred, no output PDF file produced!
Transcript written on luatex.log.
Error: `luatex -ini -jobname=luatex -progname=luatex luatex.ini' failed
fmtutil: running `luatex -ini -jobname=dviluatex -progname=dviluatex
dviluatex.ini' ...
[... similar messages for other commands]
This is a summary of all `failed' messages:
`luatex -ini -jobname=luatex -progname=luatex luatex.ini' failed
`luatex -ini -jobname=dviluatex -progname=dviluatex dviluatex.ini' failed
`pdftex -ini -jobname=pdftex -progname=pdftex -translate-file=cp227.tcx
*pdfetex.ini' failed
Sami
signature.asc
Description: Digital signature
Bug#557091: Bug#562198: Still seeing failure after workaround -- bug in latex-cjk-chinese
[Switching to -maintonly for #557091 too.] On Sun, Dec 27, 2009 at 12:20:58AM +0100, Norbert Preining wrote: I don't know what you are talking about. I think that's because you misunderstood me. There already is a bug report (#562198) against latex-cjk-chinese which I suspect (but am not sure) is this same bug, but this #557091 bug report is generally what you (or at least I) would find when encountering this problem, so thought the info would be nice here too. Wrong. How do you come to the conclusion? If you would have read the bug report you would have seen my email: Sorry, I was unclear (if I guess right how you interpreted my words). I didn't mean to claim that #562198 is the same bug as #557091, but that #562198 is the same bug I was seeing. My bad. My rationale was, however, that if I had come to #557091 looking for clues, I probably am not the only one doing so, so having this information in that bug report would do good for others. Why? Well, I'm talking about configuring the package failing in exactly the same way, modulo some obscure log file which it says it produced under /tmp. I did read both reports, thank you for asking, found #557091 when looking for solution and thought for a good while it was the same bug, since it manifested so similarly. I guess seeing it from a package maintainer POV might be different, but to me, and I believe to many other normal users, bugs that manifest themselves with the _exact_same_output_ when configuring the package do indeed seem quite similar. I could tell after investigating for half an hour that they aren't the same, and thought I should save other people from having to spend that time (if they have the skills) by having that info in the #557091 bug. Well, anyway, useless time spent. All has been dealt with already, and reading bug reports is not too much asked for. Best wishes Norbert Sami signature.asc Description: Digital signature
Bug#557091: Bug#562198: Still seeing failure after workaround -- bug in latex-cjk-chinese
On Sun, Dec 27, 2009 at 12:52:12AM +0100, Norbert Preining wrote: On So, 27 Dez 2009, Sami Liedes wrote: that #562198 is the same bug I was seeing. My bad. My rationale was, however, that if I had come to #557091 looking for clues, I probably am not the only one doing so, so having this information in that bug report would do good for others. Ok, now I see your point ... well, so thanks. No problem, and really, sorry for being unclear and wasting your time :) manifest themselves with the _exact_same_output_ when configuring the package do indeed seem quite similar. I could tell after investigating Well, we *COULD* echo out the whole bunch at configuration time, but nobody actually wants to see it. But as the output states clearly, the important information is in the /tmp/fmtutil* file. Unfortunately it is long. I agree the way you are doing it is better than outputting it all (at least unless you could show only the errors, but there are probably better ways to spend precious volunteer time, for which I'm BTW thankful :) Sami signature.asc Description: Digital signature
Bug#523044: openoffice.org-common has a config file under /usr
Package: openoffice.org-common Version: 1:3.0.1-9 Severity: serious Something, presumably in openoffice.org or in pre/postinstall, modifies the file /usr/lib/openoffice/basis3.0/share/config/javasettingsunopkginstall.xml . Sorry, I don't know what modifies it and when, but I can deduce that it's not modified only on my system by googling for the file name: There are several Ubuntu bug reports against openoffice.org that happen to mention (as a feature of reportbug) that the file has been modified. I know I have not modified it by hand. Also judging from the path (.../config/...), I presume it's some kind of a config file. This causes, for example, debsums and reportbug to complain. Sami -- System Information: Debian Release: squeeze/sid APT prefers oldstable APT policy: (500, 'oldstable'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.29.1-tuxonice (SMP w/1 CPU core; PREEMPT) 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 openoffice.org-common depends on: ii openoffice.org-style-galaxy 1:3.0.1-9 full-featured office productivity Versions of packages openoffice.org-common recommends: ii openoffice.org-style-crystal 1:3.0.1-9 full-featured office productivity pn openoffice.org-style-tangonone (no description available) Versions of packages openoffice.org-common suggests: pn openoffice.org-style-hicontra none (no description available) pn openoffice.org-style-industri none (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#515734: Another symptom
Hi, I think this is a different manifestation of the same bug (and the same remedy, downgrading to libxi6 from testing, works). I have the keyboard switching applet enabled in KDE. When I try to use it in the sid version to change the layout from my default (se -variant dvorak), nothing happens (the flag in the applet changes, but the layout stays the same). Additionally, and weirdly, both global shortcuts and the Run command dialog seem to use 'us' layout, no matter what. Sami -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#514193: ia32-apt-get breaks apt-get update
Package: ia32-apt-get Version: 11 Severity: grave Running `apt-get update' after installing ia32-apt-get fails with an assertion failure. I suspect this is bad enough to be RC (apt-get update being such a central thing to do); downgrade if you disagree. $ sudo apt-get update apt-get: update Get:1 http://ftp.se.debian.org unstable Release.gpg [189B] Ign http://ftp.se.debian.org unstable/main Translation-en_US Ign http://ftp.se.debian.org unstable/non-free Translation-en_US Ign http://ftp.se.debian.org unstable/contrib Translation-en_US Get:2 http://ftp.se.debian.org unstable Release [80.6kB] Get:3 http://security.debian.org etch/updates Release.gpg [189B] Ign http://security.debian.org etch/updates/main Translation-en_US Get:4 http://volatile.debian.org etch/volatile Release.gpg [189B] Ign http://volatile.debian.org etch/volatile/main Translation-en_US Ign http://security.debian.org etch/updates/contrib Translation-en_US Ign http://security.debian.org etch/updates/non-free Translation-en_US Get:5 http://security.debian.org etch/updates Release [37.6kB] Ign http://volatile.debian.org etch/volatile/contrib Translation-en_US Ign http://volatile.debian.org etch/volatile/non-free Translation-en_US Get:6 http://volatile.debian.org etch/volatile Release [40.7kB] Get:7 http://ftp.se.debian.org unstable/main Packages [5726kB] Get:8 http://security.debian.org etch/updates/main Packages [313kB] Get:9 http://volatile.debian.org etch/volatile/main Packages [6996B] Get:10 http://volatile.debian.org etch/volatile/contrib Packages [574B] Get:11 http://volatile.debian.org etch/volatile/non-free Packages [14B] Get:12 http://security.debian.org etch/updates/contrib Packages [7805B] Get:13 http://security.debian.org etch/updates/non-free Packages [3614B] Get:14 http://security.debian.org etch/updates/main Sources [49.8kB] Get:15 http://ftp.se.debian.org unstable/non-free Packages [111kB] Get:16 http://ftp.se.debian.org unstable/contrib Packages [66.5kB] Get:17 http://ftp.se.debian.org unstable/main Sources [2652kB] Get:18 http://security.debian.org etch/updates/contrib Sources [1168B] Get:19 http://security.debian.org etch/updates/non-free Sources [1176B] Get:20 http://ftp.se.debian.org unstable/non-free Sources [59.6kB] Get:21 http://ftp.se.debian.org unstable/contrib Sources [34.6kB] Fetched 9193kB in 8s (1040kB/s) Reading package lists... Done Get:1 http://security.debian.org etch/updates Release.gpg [189B] Ign http://security.debian.org etch/updates/main Translation-en_US Get:2 http://volatile.debian.org etch/volatile Release.gpg [189B] Ign http://volatile.debian.org etch/volatile/main Translation-en_US Ign http://volatile.debian.org etch/volatile/contrib Translation-en_US Ign http://security.debian.org etch/updates/contrib Translation-en_US Ign http://security.debian.org etch/updates/non-free Translation-en_US Get:3 http://security.debian.org etch/updates Release [37.6kB] Get:4 http://ftp.se.debian.org unstable Release.gpg [189B] Ign http://ftp.se.debian.org unstable/main Translation-en_US Ign http://ftp.se.debian.org unstable/non-free Translation-en_US Ign http://volatile.debian.org etch/volatile/non-free Translation-en_US Get:5 http://volatile.debian.org etch/volatile Release [40.7kB] Ign http://ftp.se.debian.org unstable/contrib Translation-en_US Get:6 http://ftp.se.debian.org unstable Release [80.6kB] Get:7 http://security.debian.org etch/updates/main Packages [298kB] Get:8 http://volatile.debian.org etch/volatile/main Packages [6988B] Get:9 http://ftp.se.debian.org unstable/main Packages [5670kB] Get:10 http://volatile.debian.org etch/volatile/contrib Packages [570B] Get:11 http://volatile.debian.org etch/volatile/non-free Packages [14B] Get:12 http://security.debian.org etch/updates/contrib Packages [3926B] Get:13 http://security.debian.org etch/updates/non-free Packages [1420B] Get:14 http://security.debian.org etch/updates/main Sources [49.8kB] Get:15 http://security.debian.org etch/updates/contrib Sources [1168B] Get:16 http://security.debian.org etch/updates/non-free Sources [1176B] Get:17 http://ftp.se.debian.org unstable/non-free Packages [98.1kB] Get:18 http://ftp.se.debian.org unstable/contrib Packages [60.2kB] Get:19 http://ftp.se.debian.org unstable/main Sources [2652kB] Get:20 http://ftp.se.debian.org unstable/non-free Sources [59.6kB] Get:21 http://ftp.se.debian.org unstable/contrib Sources [34.6kB] Fetched 9097kB in 8s (1075kB/s) Reading package lists... Done Ignoring ftp.se.debian.org_debian_dists_unstable_contrib_source_Sources arch_all.list: adding amarok-engines all arch_all.list: deleting asterisk amd64 arch_all.list: adding cupsys all arch_all.list: adding cupsys-bsd all arch_all.list: adding cupsys-client all arch_all.list: adding cupsys-dbg all arch_all.list: adding dhcp-client all arch_all.list: adding dnsmasq all arch_all.list: adding gaim all arch_all.list: adding gaim-dbg all arch_all.list: adding gs-esp all arch_all.list:
Bug#499201: libidn11-dev: Package fails to configure
Package: libidn11-dev Version: 1.10-1 Severity: serious The package fails to configure: Setting up libidn11-dev (1.10-1) ... Usage: install-info [options ...] [--] filename Options: --section regexp title put the new entry in the regex matched section or create a new one with title if non-existent. --menuentry=text set the menu entry. --description=text set the description to be used in the menu entry. --info-file=path specify info file to install in the directory. --dir-file=pathspecify file name of info directory file. --infodir=directorysame as '--dir-file=directory/dir'. --info-dir=directory likewise. --keep-old do not replace entries nor remove empty ones. --remove remove the entry specified by filename basename. --remove-exactly remove the exact filename entry. --test enables test mode (no actions taken). --debug enables debug mode (show more information). --quiet do not show output messages. --help show this help message. --versionshow the version. dpkg: error processing libidn11-dev (--configure): subprocess post-installation script returned error exit status 1 Sami -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26.3 (SMP w/4 CPU cores; PREEMPT) 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 libidn11-dev depends on: ii libidn11 1.10-1 GNU libidn library, implementation ii pkg-config0.22-1 manage compile and link flags for libidn11-dev recommends no packages. libidn11-dev suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#497117: tangogps: Contains glade-generated files without source
Package: tangogps Version: 0.9.2-2 Severity: serious Justification: Policy 2.2.1 [Cc: debian-legal] Hi, The files src/interface.c src/interface.h src/support.h src/support.c appear to be generated using the Glade user interface builder. However the source code for them (i.e. the modifiable glade project) seems to be missing from the source tarball. Sorry if I'm mistaken, I just couldn't find it there. I believe the generated files are not source code as defined by GPL (i.e. in preferred form of modification). Hence without distributing the Glade projects along with the files they cannot be distributed under the GPL. Furthermore, I believe this fails DFSG #2. Sami -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26.3 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#496001: python-coverage: Missing Depends: python-pkg-resources
Package: python-coverage Version: 2.80-1 Severity: serious It appears python-coverage should depend on python-pkg-resources: $ python-coverage Traceback (most recent call last): File /usr/bin/python-coverage, line 5, in module from pkg_resources import load_entry_point ImportError: No module named pkg_resources $ python-coverage -e Traceback (most recent call last): File /usr/bin/python-coverage, line 5, in module from pkg_resources import load_entry_point ImportError: No module named pkg_resources $ apt-file search pkg_resources python-pkg-resources: /usr/share/doc/python-pkg-resources/pkg_resources.txt.gz python-pkg-resources: /usr/share/pyshared/pkg_resources.py python-wxgtk2.8: /usr/lib/python2.4/site-packages/wx-2.8-gtk2-unicode/wx/tools/Editra/src/extern/pkg_resources.py python-wxgtk2.8: /usr/lib/python2.5/site-packages/wx-2.8-gtk2-unicode/wx/tools/Editra/src/extern/pkg_resources.py After installing python-pkg-resoures, I get no error message at least running the above commands. Sami -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26.2 (SMP w/4 CPU cores; PREEMPT) 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 python-coverage depends on: ii python2.5.2-2An interactive high-level object-o ii python-central0.6.8 register and build utility for Pyt python-coverage recommends no packages. python-coverage suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#482140: [xml/sgml-pkgs] Bug#482140: The error is when update-xmlcatalog is run entity already registered
On Sat, May 24, 2008 at 04:47:14PM +0200, Daniel Leidert wrote: Am Samstag, den 24.05.2008, 02:56 -0500 schrieb Christofer C. Bell: The error that update-xmlcatalog seems to give is the following: update-xmlcatalog: error: entity already registered [snip] Yes, two entities cannot be registered for different packages. In this case, update-xmlcatalog will error out. Can you send me your /etc/xml/catalog file from *Etch*? Sorry, I don't have it any more. I tried if removing the package and reinstalling it helps (it did). It was a fairly standard etch installation with the desktop components chosen by installer. Sami -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#482140: docbook-xml: Package does not install: update-xmlcatalog: error: entity already registered
Package: docbook-xml Version: 4.5-5 Severity: serious When configuring docbook-xml after installation, I get the error -- update-xmlcatalog: error: entity already registered dpkg: error processing docbook-xml (--configure): subprocess post-installation script returned error exit status 1 -- This happened on a just installed box, upgrading from stable - testing - unstable. Sami -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.18-6-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 docbook-xml depends on: ii sgml-base 1.26 SGML infrastructure and SGML catal ii sgml-data 2.0.3 common SGML and XML data ii xml-core 0.11 XML infrastructure and XML catalog docbook-xml recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#481288: sane-utils: Package fails to configure
Package: sane-utils Version: 1.0.19-8 Severity: serious Hi, When upgrading sane-utils, I get the following error: Setting up sane-utils (1.0.19-8) ... /usr/sbin/deluser: The user `saned' is not a member of group `scanner'. dpkg: error processing sane-utils (--configure): subprocess post-installation script returned error exit status 6 Sami -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.25.2 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=C, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages sane-utils depends on: ii adduser 3.107 add and remove users and groups ii debconf [debconf-2.0]1.5.21 Debian configuration management sy ii libavahi-client3 0.6.22-3Avahi client library ii libavahi-common3 0.6.22-3Avahi common library ii libc62.7-11 GNU C Library: Shared libraries ii libieee1284-30.2.11-4cross-platform library for paralle ii libsane 1.0.19-8API library for scanners ii libusb-0.1-4 2:0.1.12-11 userspace USB programming library ii update-inetd 4.30inetd configuration file updater Versions of packages sane-utils recommends: ii avahi-daemon 0.6.22-3 Avahi mDNS/DNS-SD daemon -- debconf information: * sane-utils/saned_run: false * sane-utils/saned_scanner_group: false signature.asc Description: Digital signature
Bug#480052: The offending test is test_first() in test_funcptr.py
Hi, I did some digging, the test that segfaults is test_first() in test_funcptr.py. Before that all the tests seem to work nice. Sami signature.asc Description: Digital signature
Bug#477381: statcvs: No source tarball in archive - needs rebuild
Package: statcvs Version: 0.3.dfsg-4 Severity: serious Hi, The statcvs package lacks a source tarball in the archive since April 10. From ftp.debian.org: ls -l -rw-rw-r--1 1176 1176 5959 Apr 10 22:17 statcvs_0.3.dfsg-4.diff.gz -rw-rw-r--1 1176 1176 960 Apr 10 22:17 statcvs_0.3.dfsg-4.dsc -rw-rw-r--1 1176 1176 382608 Apr 10 22:17 statcvs_0.3.dfsg-4_all.deb I discussed this on #debian-devel and was told that I should file a bug against this package, Debbugs-Cc: to ftpmaster. Here's some relevant lines from IRC (removed a lot of noise and hopefully nothing too relevant): SLi Hi. There's a package without source in ftp.debian.org since April 10 (see debian/pool/main/s/statcvs/, the source tarball is missing). Should I file a bug against statcvs or ftp.debian.org? Ganneff did it move, the wrong way, from contrib/non-free to main? azeem Ganneff: yes Ganneff file a bug against the package, high severity, to upload a new upstream version SLi No bug against ftp.debian.org? Ganneff no. they can fix it pretty fast if they just upload a new upstream Ganneff rename the tarball to some +dfsg one astronut Ganneff: how did it happen? Ganneff astronut: bug in dak if you do the move wrongly azeem it's 0.3.dfsg anyway astronut ah Ganneff make it 0.3.dfsg1 Ganneff it only happens if the maintainer doesnt use -sa... (well. dak needs a fix, we know that) Sami -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.25 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=C, [EMAIL PROTECTED] (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash signature.asc Description: Digital signature
Bug#474343: More info
I have the same problem and inspected it, here's a copy of the
relevant portion of my mail to #473209:
- Forwarded message from Sami Liedes [EMAIL PROTECTED] -
Date: Sat, 5 Apr 2008 16:39:22 +0300
From: Sami Liedes [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: More info
[...]
If I remove or comment out the (fd0) line in device.map, after that
update-grub silently fails (no error printed, but exit code is 139 -
the culprit is grub-probe *segfaulting*). Kernel logs show no oops, so
I guess it's a user space thing, not the kernel crashing. (This might
be another bug, but since I hit it when inspecting this one, I'll
describe it here.)
I rebuilt grub-common with debug syms and got a backtrace. The crash
occurs in the LVM code. Curiously the crash happens when calling
grub_lvm_scan_device(hd0,3), not while probing for the floppy disk.
Also attached further below the information you requested previously
in this bug report (inspecting p at a breakpoint).
# gdb --args grub-probe -t device fd0
GNU gdb 6.8-debian
Copyright (C) 2008 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...
(gdb) r
Starting program: /usr/sbin/grub-probe -t device fd0
Program received signal SIGSEGV, Segmentation fault.
0x0040589d in grub_memmove (dest=0x7fff8774e2c0, src=0x6, n=37) at
/home/sliedes/rec/grub2-1.96+20080228/kern/misc.c:43
43 *--d = *--s;
(gdb) bt
#0 0x0040589d in grub_memmove (dest=0x7fff8774e2c0, src=0x6, n=37) at
/home/sliedes/rec/grub2-1.96+20080228/kern/misc.c:43
#1 0x0041f3d0 in grub_lvm_scan_device (name=0x6350c0 hd0,3) at
/home/sliedes/rec/grub2-1.96+20080228/disk/lvm.c:310
#2 0x004044a1 in iterate_partition (disk=0x635010,
partition=0x7fff8774e9d0) at
/home/sliedes/rec/grub2-1.96+20080228/kern/device.c:132
#3 0x0041c551 in pc_partition_map_iterate (disk=0x635010,
hook=0x7fff8774eb8f) at /home/sliedes/rec/grub2-1.96+20080228/partmap/pc.c:153
#4 0x0040808f in grub_partition_iterate (hook=0x7fff8774eb8f) at
/home/sliedes/rec/grub2-1.96+20080228/kern/partition.c:126
#5 0x00404535 in iterate_disk (disk_name=0x7fff8774eae0 hd0) at
/home/sliedes/rec/grub2-1.96+20080228/kern/device.c:101
#6 0x00401e37 in call_hook (hook=0x7fff8774eb78, drive=128) at
/home/sliedes/rec/grub2-1.96+20080228/util/biosdisk.c:131
#7 0x00401e6c in grub_util_biosdisk_iterate (hook=0x7fff8774eb78) at
/home/sliedes/rec/grub2-1.96+20080228/util/biosdisk.c:140
#8 0x00404985 in grub_disk_dev_iterate (hook=0x7fff8774eb78) at
/home/sliedes/rec/grub2-1.96+20080228/kern/disk.c:205
#9 0x004043f4 in grub_device_iterate (hook=0x41f080
grub_lvm_scan_device) at
/home/sliedes/rec/grub2-1.96+20080228/kern/device.c:138
#10 0x0041faeb in grub_mod_init (mod=0x0) at
/home/sliedes/rec/grub2-1.96+20080228/disk/lvm.c:511
#11 0x0041fad3 in grub_lvm_init () at
/home/sliedes/rec/grub2-1.96+20080228/disk/lvm.c:509
#12 0x00420ca0 in grub_init_all () at grub_probe_init.c:44
#13 0x00401cc1 in main (argc=4, argv=0x7fff8774ed38) at
/home/sliedes/rec/grub2-1.96+20080228/util/grub-probe.c:355
There's something hairy going on with the metadata buffer, and at
least it seems the grub_strstr() return value should be checked:
(gdb) up
#1 0x0041f3d0 in grub_lvm_scan_device (name=0x6350c0 hd0,3) at
/home/sliedes/rec/grub2-1.96+20080228/disk/lvm.c:310
310 grub_memcpy (vg_id, p, GRUB_LVM_ID_STRLEN);
(gdb) print p
$1 = 0x6 Address 0x6 out of bounds
(gdb) l
305
306 grub_memcpy (vgname, p, vgname_len);
307 vgname[vgname_len] = '\0';
308
309 p = grub_strstr (q, id = \) + sizeof (id = \) - 1;
310 grub_memcpy (vg_id, p, GRUB_LVM_ID_STRLEN);
311 vg_id[GRUB_LVM_ID_STRLEN] = '\0';
312
313 for (vg = vg_list; vg; vg = vg-next)
314 {
(gdb) print q
$2 = 0x66b5b4 LVM2 x[5A%r0N*\001
(gdb) print metadatabuf
$3 = 0x66b5b0 \033Ç5` LVM2 x[5A%r0N*\001
(gdb) info locals
err = GRUB_ERR_NONE
disk = (grub_disk_t) 0x6350e0
da_offset = 196608
da_size = 0
mda_offset = 4096
mda_size = 192512
buf = LABELONE\001\000\000\000\000\000\000\000\226°ÐË \000\000\000LVM2
001Tuf1htoXt6rUT4rRoUEhfsX0hI0vYetY\000\000öø\r\000\000\000\000\000\003, '\0'
repeats 30 times, \020\000\000\000\000\000\000\000ð\002, '\0' repeats 396
times
vg_id = [EMAIL PROTECTED]
pv_id = Tuf1ht-oXt6-rUT4-rRoU-Ehfs-X0hI-0vYetY
metadatabuf = 0x66b5b0 \033Ç5` LVM2 x[5A%r0N*\001
p = 0x6 Address 0x6 out of bounds
q = 0x66b5b4 LVM2 x[5A%r0N*\001
vgname = 0x6387d0 \033Ç5`
lh
Bug#473209: More info
On Mon, Apr 07, 2008 at 05:10:40PM +0200, Robert Millan wrote: On Sat, Apr 05, 2008 at 04:39:22PM +0300, Sami Liedes wrote: I initially had the same problem with Cannot get the real path of /dev/hda. This is fixed now (will be in next upload). Thanks. However now update-grub hangs pretty much forever, and I get messages like this on my kernel log: [4520359.961987] end_request: I/O error, dev fd0, sector 0 [4520372.128819] end_request: I/O error, dev fd0, sector 0 [4520384.295621] end_request: I/O error, dev fd0, sector 0 [4520384.295633] Buffer I/O error on device fd0, logical block 0 [4520396.461384] end_request: I/O error, dev fd0, sector 0 [4520396.461396] Buffer I/O error on device fd0, logical block 0 [4520408.628195] end_request: I/O error, dev fd0, sector 0 [4520420.797716] end_request: I/O error, dev fd0, sector 0 [4520420.797722] Buffer I/O error on device fd0, logical block 0 [4520432.972089] end_request: I/O error, dev fd0, sector 0 [4520432.972102] Buffer I/O error on device fd0, logical block 0 [4520467.706750] end_request: I/O error, dev fd0, sector 0 [4520479.878390] end_request: I/O error, dev fd0, sector 0 [4520492.048230] end_request: I/O error, dev fd0, sector 0 [4520492.048236] Buffer I/O error on device fd0, logical block 0 ... Please could you file a separate bug for this? On further inspection, this is probably the same as the 3 1/2 years old #282063. I rebuilt grub-common with debug syms and got a backtrace. The crash occurs in the LVM code. Curiously the crash happens when calling grub_lvm_scan_device(hd0,3), not while probing for the floppy disk. Same here. This is #474343, also analyzed there (although with little less depth). I'll forward the relevant parts of my original report to that bug. Sami signature.asc Description: Digital signature
Bug#474343: Sorry, might not be the same
Hi, and sorry about noise, Just for the record, and to alleviate confusion, it turns out what I have might not be the same bug after all. I just submitted a new bug report with the same (and more) info. Sami signature.asc Description: Digital signature
Bug#473209: More info
I initially had the same problem with Cannot get the real path of /dev/hda. My device.map was from 2006, so I recreated it with rm /boot/grub/device.map grub --device-map and got the device paths corrected to /dev/sd?. However now update-grub hangs pretty much forever, and I get messages like this on my kernel log: [4520359.961987] end_request: I/O error, dev fd0, sector 0 [4520372.128819] end_request: I/O error, dev fd0, sector 0 [4520384.295621] end_request: I/O error, dev fd0, sector 0 [4520384.295633] Buffer I/O error on device fd0, logical block 0 [4520396.461384] end_request: I/O error, dev fd0, sector 0 [4520396.461396] Buffer I/O error on device fd0, logical block 0 [4520408.628195] end_request: I/O error, dev fd0, sector 0 [4520420.797716] end_request: I/O error, dev fd0, sector 0 [4520420.797722] Buffer I/O error on device fd0, logical block 0 [4520432.972089] end_request: I/O error, dev fd0, sector 0 [4520432.972102] Buffer I/O error on device fd0, logical block 0 [4520467.706750] end_request: I/O error, dev fd0, sector 0 [4520479.878390] end_request: I/O error, dev fd0, sector 0 [4520492.048230] end_request: I/O error, dev fd0, sector 0 [4520492.048236] Buffer I/O error on device fd0, logical block 0 ... I rmmod'd the floppy module and recreated device.map. /dev/fd0 is still added to the map, and after that update-grub fails with grub-probe: error: Cannot get the real path of `/dev/fd0' . If I remove or comment out the (fd0) line in device.map, after that update-grub silently fails (no error printed, but exit code is 139 - the culprit is grub-probe *segfaulting*). Kernel logs show no oops, so I guess it's a user space thing, not the kernel crashing. (This might be another bug, but since I hit it when inspecting this one, I'll describe it here.) I rebuilt grub-common with debug syms and got a backtrace. The crash occurs in the LVM code. Curiously the crash happens when calling grub_lvm_scan_device(hd0,3), not while probing for the floppy disk. # gdb --args grub-probe -t device fd0 GNU gdb 6.8-debian Copyright (C) 2008 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... (gdb) r Starting program: /usr/sbin/grub-probe -t device fd0 Program received signal SIGSEGV, Segmentation fault. 0x0040589d in grub_memmove (dest=0x7fff8774e2c0, src=0x6, n=37) at /home/sliedes/rec/grub2-1.96+20080228/kern/misc.c:43 43 *--d = *--s; (gdb) bt #0 0x0040589d in grub_memmove (dest=0x7fff8774e2c0, src=0x6, n=37) at /home/sliedes/rec/grub2-1.96+20080228/kern/misc.c:43 #1 0x0041f3d0 in grub_lvm_scan_device (name=0x6350c0 hd0,3) at /home/sliedes/rec/grub2-1.96+20080228/disk/lvm.c:310 #2 0x004044a1 in iterate_partition (disk=0x635010, partition=0x7fff8774e9d0) at /home/sliedes/rec/grub2-1.96+20080228/kern/device.c:132 #3 0x0041c551 in pc_partition_map_iterate (disk=0x635010, hook=0x7fff8774eb8f) at /home/sliedes/rec/grub2-1.96+20080228/partmap/pc.c:153 #4 0x0040808f in grub_partition_iterate (hook=0x7fff8774eb8f) at /home/sliedes/rec/grub2-1.96+20080228/kern/partition.c:126 #5 0x00404535 in iterate_disk (disk_name=0x7fff8774eae0 hd0) at /home/sliedes/rec/grub2-1.96+20080228/kern/device.c:101 #6 0x00401e37 in call_hook (hook=0x7fff8774eb78, drive=128) at /home/sliedes/rec/grub2-1.96+20080228/util/biosdisk.c:131 #7 0x00401e6c in grub_util_biosdisk_iterate (hook=0x7fff8774eb78) at /home/sliedes/rec/grub2-1.96+20080228/util/biosdisk.c:140 #8 0x00404985 in grub_disk_dev_iterate (hook=0x7fff8774eb78) at /home/sliedes/rec/grub2-1.96+20080228/kern/disk.c:205 #9 0x004043f4 in grub_device_iterate (hook=0x41f080 grub_lvm_scan_device) at /home/sliedes/rec/grub2-1.96+20080228/kern/device.c:138 #10 0x0041faeb in grub_mod_init (mod=0x0) at /home/sliedes/rec/grub2-1.96+20080228/disk/lvm.c:511 #11 0x0041fad3 in grub_lvm_init () at /home/sliedes/rec/grub2-1.96+20080228/disk/lvm.c:509 #12 0x00420ca0 in grub_init_all () at grub_probe_init.c:44 #13 0x00401cc1 in main (argc=4, argv=0x7fff8774ed38) at /home/sliedes/rec/grub2-1.96+20080228/util/grub-probe.c:355 There's something hairy going on with the metadata buffer, and at least it seems the grub_strstr() return value should be checked: (gdb) up #1 0x0041f3d0 in grub_lvm_scan_device (name=0x6350c0 hd0,3) at
Bug#472275: xfonts-mathml: recommends: a package outside main
Package: xfonts-mathml Version: 1 Severity: serious Justification: Policy 2.2.1 Hi, The xfonts-mathml package Recommends: ttf-mathematica4.1, which is in section contrib (and automatically installs non-free software). Here's the relevant text from the Policy 2.2.1: Every package in main must comply with the DFSG (Debian Free Software Guidelines). In addition, the packages in main * must not require a package outside of main for compilation or execution (thus, the package must not declare a Depends, Recommends, or Build-Depends relationship on a non-main package), -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.24.2 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=C, [EMAIL PROTECTED] (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash signature.asc Description: Digital signature
Bug#439642: Probably something debian buildd specific
Hi, When I build snort on my sid amd64 box, the .so files get built as 64 bit as they should. So this is probably something debian buildd specific. Sami signature.asc Description: Digital signature
Bug#382175: Ping
On Tue, Sep 11, 2007 at 05:41:52AM +, brian m. carlson wrote: I think I could help with this, either the reverse engineering or reimplementation effort, if that's needed. I don't have very much experience with RPC though. Due to school and just life in general, I have had almost no time to reverse-engineer the code. I got through only a handful of functions. So if you'd like to do this, please do. I might be able to help to some extent; in that case, please let me know (by CC'ing me). I don't think you really need that much experience with RPC. All you need to do is describe what each external function does. Basically, document how each function manipulates input, output, and global state. That's it. I read through the bug archive. Has anyone still asked Sun about relicensing? And has FSF been consulted? I'd think they are picky about freedom issues, even if they disagree with Debian on them somewhat :) Sami signature.asc Description: Digital signature
Bug#440841: dpkg-dev: source package gpg verification doesn't restrict valid keys to debian-keyring
Package: dpkg-dev
Version: 1.14.5
Severity: grave
Tags: security
Justification: root security hole
From /usr/bin/dpkg-source:
if (-x '/usr/bin/gpg') {
my $gpg_command = 'gpg -q --verify ';
if (-r '/usr/share/keyrings/debian-keyring.gpg') {
$gpg_command = $gpg_command.'--keyring
/usr/share/keyrings/debian-keyring.gpg ';
}
$gpg_command = $gpg_command.quotemeta($dsc).' 21';
my @gpg_output = `$gpg_command`;
my $gpg_status = $? 8;
if ($gpg_status) {
print STDERR join(,@gpg_output);
error(sprintf(_g(failed to verify signature on %s), $dsc))
if ($gpg_status == 1);
}
This is bad: It silently accepts any package signed by any key in the
running user's keyring.
Steps to reproduce:
1. Download the public key of Adam Attacker.
2. Manually download the source (.dsc, orig.tar.gz and diff) of the
package `frobulator' from the official Debian archive. (For example,
if it's impossible to use apt-get as a normal user since the archive
is not in /etc/apt/sources.list.)
3. Run dpkg-source -x frobulator_1.0-1.dsc.
4. cd frobulator-1.0 dpkg-buildpackage -rfakeroot
Expected results:
In step 3, dpkg-source verifies that the package is signed with a key
that is in the debian-keyring, and refuses to extract it if something
is wrong.
Actual results:
dpkg-source accepts the package silently (without printing any error
or warning at all) if the package is signed by the public key of Adam
Attacker, which is in the user's keyring.
In step 4, this leads to arbitrary code execution.
More information:
1. If debian-keyring does not exist, gpg is not given any --keyring
argument. This causes the user's default keyring to be used.
2. If debian-keyring exists, the --keyring option merely ADDS
debian-keyring to the keyrings used, hence the situation is as bad.
Also:
Suppose Adam Attacker has installed a rogue WLAN access point in my
university which I use when I download the sources and supplies me
with a hacked version of frobulator. I trust those sources anyway
because dpkg-source is supposed to verify that the package is signed
by a Debian Developer. Hence I go on to build the package (running
malicious code as normal user) and install it (running the code as
root).
Also notice that if the signature check fails with exit code 2, which
happens if the public key is not known, dpkg-deb happily extracts the
package. In this case the user sees the warning produced by gpg,
however.
Sami
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.22.3-sli (PREEMPT)
Locale: LANG=C, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages dpkg-dev depends on:
ii binutils 2.18-1 The GNU assembler, linker and bina
ii cpio 2.9-3 GNU cpio -- a program to manage ar
ii dpkg 1.14.5 package maintenance system for Deb
ii make 3.81-3 The GNU version of the make util
ii patch 2.5.9-4Apply a diff file to an original
ii perl [perl5] 5.8.8-7Larry Wall's Practical Extraction
ii perl-modules 5.8.8-7Core Perl modules
Versions of packages dpkg-dev recommends:
ii bzip2 1.0.3-7high-quality block-sorting file co
ii gcc [c-compiler] 4:4.2.1-5 The GNU C compiler
ii gcc-3.4 [c-compiler] 3.4.6-6The GNU C compiler
ii gcc-4.1 [c-compiler] 4.1.2-16 The GNU C compiler
ii gcc-4.2 [c-compiler] 4.2.1-5The GNU C compiler
-- no debconf information
signature.asc
Description: Digital signature
Bug#431706: Blocks all other package upgrades
package gnokii severity 431706 critical thanks Hi, gnokii in its current state can (possibly due to a limitation in apt/aptitude) block all other packages in the system from upgrading. See #435403. Hence I guess makes unrelated software on the system (or the whole system) break. Downgrade if I'm wrong, but as I haven't fixed this by hand, I haven't been able to upgrade anything for days. Sami signature.asc Description: Digital signature
Bug#431706: Still broken?
I'm not sure things still work the way intended. Trying to upgrade from 0.6.17-1: Preparing to replace gnokii 0.6.17-1 (using .../gnokii_0.6.18-1_amd64.deb) ... Adding group `gnokii' (GID 120) ... Done. Unpacking replacement gnokii ... Unknown database: user Try `getent --help' or `getent --usage' for more information. gnokii:x:120: No override present. dpkg: warning - old post-removal script returned error exit status 2 dpkg - trying script from the new package instead ... Group 'gnokii' not found, not deleting... No override present. dpkg: error processing /var/cache/apt/archives/gnokii_0.6.18-1_amd64.deb (--unpack): subprocess new post-removal script returned error exit status 2 Adding group `gnokii' (GID 120) ... Done. gnokii:x:120: No override present. dpkg: error while cleaning up: subprocess post-removal script returned error exit status 2 Errors were encountered while processing: /var/cache/apt/archives/gnokii_0.6.18-1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Also I cannot --remove the package: dpkg: error processing gnokii (--remove): Package is in a very bad inconsistent state - you should reinstall it before attempting a removal. Sami signature.asc Description: Digital signature
Bug#421341: FTBFS: Something wrong with gcjh/classpath/something
Package: pdftk
Version: 1.40-2
Severity: serious
Justification: no longer builds from source
Hi,
I don't know whose bug this is, pdftk's (by possibly setting wrong
classpath? I don't know) or gcj's or what, but anyway, for me pdftk
doesn't build:
$ dpkg-buildpackage -rfakeroot
[...]
make[3]: Entering directory
`/home/sliedes/sij/vero/pdftk/o/pdftk-1.40/java_libs/gnu_local/java/security'
gcj-4.1 -O2 --encoding=UTF-8
--classpath=/home/sliedes/sij/vero/pdftk/o/pdftk-1.40/java_libs -c
Engine.java -o Engine.o
Engine.java:226: warning: Type safety: The method isAssignableFrom(Class)
belongs to the raw type Class. References to generic type ClassT should be
parameterized
!argTypes[j].isAssignableFrom(initArgs[j].getClass()))
1 problem (1 warning)
ar rs security.a Engine.o;
ar: creating security.a
gcj-4.1 -O2 --encoding=UTF-8
--classpath=/home/sliedes/sij/vero/pdftk/o/pdftk-1.40/java_libs -C Engine.java
Engine.java:226: warning: Type safety: The method isAssignableFrom(Class)
belongs to the raw type Class. References to generic type ClassT should be
parameterized
!argTypes[j].isAssignableFrom(initArgs[j].getClass()))
1 problem (1 warning)
gcjh-4.1 --classpath=. Engine;
Exception in thread main java.io.IOException: can't find class file
java/lang/Object.class in
java.net.URLClassLoader{urls=[file:/home/sliedes/sij/vero/pdftk/o/pdftk-1.40/java_libs/gnu_local/java/security/./,file:/usr/lib/jvm/java-1.5.0-gcj-4.1-1.5.0.0/jre/lib/rt.jar],
parent=gnu.gcj.runtime.SystemClassLoader{urls=[file:./],
parent=gnu.gcj.runtime.ExtensionClassLoader{urls=[], parent=null}}}
at gnu.classpath.tools.javah.Main.getClass(libgcj-tools.so.71)
at gnu.classpath.tools.javah.ClassWrapper.linkSupers(libgcj-tools.so.71)
at gnu.classpath.tools.javah.ClassWrapper.printFully(libgcj-tools.so.71)
at gnu.classpath.tools.javah.CniIncludePrinter.printClass(libgcj-tools.so.71)
at gnu.classpath.tools.javah.Main.writeHeaders(libgcj-tools.so.71)
at gnu.classpath.tools.javah.Main.run(libgcj-tools.so.71)
at gnu.classpath.tools.javah.GcjhMain.main(libgcj-tools.so.71)
make[3]: *** [Engine.h] Error 1
rm Engine.class
make[3]: Leaving directory
`/home/sliedes/sij/vero/pdftk/o/pdftk-1.40/java_libs/gnu_local/java/security'
make[2]: *** [libgcj_local] Error 2
make[2]: Leaving directory `/home/sliedes/sij/vero/pdftk/o/pdftk-1.40/java_libs'
make[1]: *** [java_libs] Error 2
make[1]: Leaving directory `/home/sliedes/sij/vero/pdftk/o/pdftk-1.40/pdftk'
make: *** [build-stamp] Error 2
$ dpkg -l debhelper gcj-4.1 g++-4.1 gcc-4.1 libgcj7-jar ecj java-common \
libgcj-bc
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name VersionDescription
+++-==-==-
ii debhelper 5.0.49 helper programs for debian/rules
ii ecj3.2.2-1standalone version of the Eclipse Java compi
ii g++-4.14.1.2-4The GNU C++ compiler
ii gcc-4.14.1.2-4The GNU C compiler
ii gcj-4.14.1.2-4The GNU compiler for Java(TM)
ii java-common0.25 Base of all Java packages
ii libgcj-bc 4.1.2-2Link time only library for use with gcj
ii libgcj7-jar4.1.2-4Java runtime library for use with gcj (jar f
Sami
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.20.4-grsec-sli
Locale: LANG=C, [EMAIL PROTECTED] (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash
Versions of packages pdftk depends on:
ii libc6 2.5-4 GNU C Library: Shared libraries
ii libgcc1 1:4.1.2-4 GCC support library
ii libgcj7-0 4.1.1-20 Java runtime library for use with
ii libstdc++64.1.2-4The GNU Standard C++ Library v3
pdftk recommends no packages.
-- no debconf information
signature.asc
Description: Digital signature
Bug#382175: Ping
Hi, Anything new about this bug? I think I could help with this, either the reverse engineering or reimplementation effort, if that's needed. I don't have very much experience with RPC though. Sami signature.asc Description: Digital signature
Bug#420686: It's not obvious esniper is legal (violation of eBay ToS)
Package: esniper Severity: serious Justification: Policy 2.2.3 [Cc:d to debian-legal] Hi, It's not obvious it is legal to distribute this software at all (probably it either is fit for main or unfit for non-free too). I suggest a review on debian-legal, since I'm not well versed in (at least this area of) law. I found nothing about this in debian-legal archives, so I assume it has not been discussed. 2.2.3 says Packages must be placed in _non-free_ if they are not compliant with the DFSG or are encumbered by patents or other legal issues that make their distribution problematic. (I expected to find something saying something about software that cannot be distributed at all, but apparently it's not there, and all the language in other sections seems very copyright and patent centric.) eBay TOS (or User Agreement in eBay terms) says[1]: _Access and Interference_ The Sites contains robot exclusion headers. Much of the information on the Sites is updated on a real-time basis and is proprietary or is licensed to eBay by our users or third parties. You agree that you will not use any robot, spider, scraper or other automated means to access the Sites for any purpose without our express written permission. Additionally, you agree that you will not: [...] - bypass our robot exclusion headers or other measures we may use to prevent or restrict access to the Sites. Sami [1] http://pages.ebay.com/help/policies/user-agreement.html -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.20.4-grsec-sli Locale: LANG=C, [EMAIL PROTECTED] (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash signature.asc Description: Digital signature
Bug#416096: Bug#414370: Summary of test cases that still break gm
On Sun, Mar 25, 2007 at 06:20:43PM +0200, Daniel Kobras wrote:
Oops. Next try.
Ok.
segv2.viff still gives heap corruption with that patch applied
(segv.viff is fixed). Might have something to do with realloc()ing to
0 bytes in AllocateImageColormap with colors=0, but obviously there's
some corruption somewhere already before that realloc() (otherwise
it's equivalent to just a free()).
$ gdb --args gm identify samples/segv2.viff
GNU gdb 6.6-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type show copying to see the conditions.
There is absolutely no warranty for GDB. Type show warranty for details.
This GDB was configured as x86_64-linux-gnu...
Using host libthread_db library /lib/libthread_db.so.1.
(gdb) r
Starting program: /usr/bin/gm identify samples/segv2.viff
[Thread debugging using libthread_db enabled]
[New Thread 47538893661280 (LWP 1804)]
*** glibc detected *** double free or corruption (fasttop): 0x00533970
***
Program received signal SIGABRT, Aborted.
[Switching to Thread 47538893661280 (LWP 1804)]
0x2b3c8166607b in raise () from /lib/libc.so.6
(gdb) bt
#0 0x2b3c8166607b in raise () from /lib/libc.so.6
#1 0x2b3c8166784e in abort () from /lib/libc.so.6
#2 0x2b3c8169c629 in __libc_message () from /lib/libc.so.6
#3 0x2b3c816a3193 in _int_free () from /lib/libc.so.6
#4 0x2b3c816a321e in free () from /lib/libc.so.6
#5 0x2b3c8103b722 in AllocateImageColormap (image=0x531a70, colors=0) at
image.c:395
#6 0x2b3c8105f7de in AssignImageColors (cube_info=0x565990,
image=0x531a70) at quantize.c:383
#7 0x2b3c81062ec8 in QuantizeImage (quantize_info=0x7fff29c86bd0,
image=0x531a70) at quantize.c:2156
#8 0x2b3c8104ca52 in SetImageType (image=0x531a70, image_type=BilevelType)
at image.c:6492
#9 0x2b3c8119dd20 in ReadVIFFImage (image_info=0x5163d0,
exception=0x7fff29c89590) at viff.c:601
#10 0x2b3c80ff17e1 in ReadImage (image_info=0x5131b0,
exception=0x7fff29c89590) at constitute.c:2748
#11 0x2b3c8108b602 in ReadStream (image_info=0x511060,
stream=0x2b3c80fec38e PingStream, exception=0x7fff29c89590) at stream.c:488
#12 0x2b3c80fec472 in PingImage (image_info=0x50aed0,
exception=0x7fff29c89590) at constitute.c:1060
#13 0x2b3c80fc9053 in IdentifyImageCommand (image_info=0x50aed0, argc=2,
argv=0x50d020, metadata=0x7fff29c895d8, exception=0x7fff29c89590)
at command.c:6791
#14 0x2b3c80fcae79 in MagickCommand (image_info=0x50aed0, argc=2,
argv=0x7fff29c89ee0, metadata=0x7fff29c895d8, exception=0x7fff29c89590)
at command.c:7210
#15 0x00400f71 in main (argc=2, argv=0x7fff29c89ee0) at gm.c:150
(gdb) bt full
#0 0x2b3c8166607b in raise () from /lib/libc.so.6
No symbol table info available.
#1 0x2b3c8166784e in abort () from /lib/libc.so.6
No symbol table info available.
#2 0x2b3c8169c629 in __libc_message () from /lib/libc.so.6
No symbol table info available.
#3 0x2b3c816a3193 in _int_free () from /lib/libc.so.6
No symbol table info available.
#4 0x2b3c816a321e in free () from /lib/libc.so.6
No symbol table info available.
#5 0x2b3c8103b722 in AllocateImageColormap (image=0x531a70, colors=0) at
image.c:395
_magick_mp = (void *) 0x0
i = 0
length = 0
quantum = 0 '\0'
__PRETTY_FUNCTION__ = AllocateImageColormap
#6 0x2b3c8105f7de in AssignImageColors (cube_info=0x565990,
image=0x531a70) at quantize.c:383
index = 0 '\0'
count = 8
y = 5452912
indexes = (IndexPacket *) 0x3fd7a8cffee8c654 Address
0x3fd7a8cffee8c654 out of bounds
i = 47538860422536
x = 47538864118919
node_info = (const NodeInfo *) 0x2b3c81061a0d
q = (PixelPacket *) 0xb29c86ba0
dither = 0
id = 5659024
is_grayscale = 0
is_monochrome = 4294967295
__func__ = AssignImageColors
#7 0x2b3c81062ec8 in QuantizeImage (quantize_info=0x7fff29c86bd0,
image=0x531a70) at quantize.c:2156
cube_info = (CubeInfo *) 0x565990
status = 1
depth = 8
number_colors = 2
__PRETTY_FUNCTION__ = QuantizeImage
__func__ = QuantizeImage
#8 0x2b3c8104ca52 in SetImageType (image=0x531a70, image_type=BilevelType)
at image.c:6492
quantize_info = {number_colors = 2, tree_depth = 8, dither = 1,
colorspace = GRAYColorspace, measure_error = 0, signature = 2880220587}
status = 1
__PRETTY_FUNCTION__ = SetImageType
#9 0x2b3c8119dd20 in ReadVIFFImage (image_info=0x5163d0,
exception=0x7fff29c89590) at viff.c:601
polarity = 0
min_value = 0
scale_factor = 1.0897435897435896
value = 158.0128205128205
image = (Image *) 0x531a70
bit = 0
y = 14073389439
Bug#412618: apg generates incredibly low-quality passwords on amd64
Package: apg Version: 2.2.3.dfsg.1-1 Severity: grave Tags: security Justification: user security hole On amd64, here's the number of identical passwords generated when generating 1000 passwords using apg: $ (while true; do apg -a 1 -M l -n 1000 -x 8 -m 8 |sort |uniq -D |uniq |wc -l; done) |uniq -c 8 0 1 12 4 0 1 29 2 0 1 336 4 0 1 108 1 0 1 34 1 0 1 43 1 0 1 72 2 0 1 48 1 183 (read: on the first 8 runs it generated 0 collisions, on next one 12 collisions, on the next 4 again 0 collisions, after that 29 collisions, and so on). Given these options apg claims to generate 1000 (-n 1000) entirely random (-a 1) passwords consisting of 8 (-x 8 -m 8) lowercase (-m l) letters. There should be 26^8 = approx. 2.1*10^11 different such passwords. According to the birthday paradox[1], the expected number of collisions given 1000 entirely random passwords out of 26^8 possible should be n-d+d*((d-1)/d)^n, n=1000, d=26^8 = 2.4*10^-6. The high number of collisions on some runs seems to imply a bug in the implementation. This bug does not seem to exist on i386 and appears to only affect totally random (i.e. not pronounceable) password generation (-a 0). Sami [1] http://en.wikipedia.org/wiki/Birthday_paradox#Collision_counting -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-amd64 Locale: LANG=C, [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages apg depends on: ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries apg recommends no packages. -- no debconf information signature.asc Description: Digital signature
Bug#412618: apg generates incredibly low-quality passwords on amd64
On Tue, Feb 27, 2007 at 04:19:30AM +0200, Sami Liedes wrote: This bug does not seem to exist on i386 and appears to only affect totally random (i.e. not pronounceable) password generation (-a 0). There's also something wrong with -a 0. When generating a very large number (3M) of passwords I get repeated sequences, including one password being generated 644 times in row. Again this doesn't seem to happen on i386. I suspect the culprit is this line in owntypes.h: typedef unsigned long int UINT32; Sami signature.asc Description: Digital signature
Bug#410204: linux-image-2.6.18-4-amd64: Data corruption on dm-crypt+XFS
On Fri, Feb 16, 2007 at 05:31:34PM -0800, Steve Langasek wrote: I'm told that dmcrypt+XFS has never worked in the upstream kernel or in Debian, so this is essentially an unsupported configuration. But you've filed this bug as critical with the justification that it causes serious data loss. Did you lose data as a result of this bug? Could you explain the process by which that happened? It's my impression that this combination is so unreliable that it will oops before you really have a chance to try to use it for storing data, so you can't really lose any data if you can't put it there in the first place. Yes, I did lose data (though fortunately only test data). But you are correct in that this happened quite early, before I really had a chance to start to use it seriously. I copied data to an XFS filesystem in a crypted partition, and I think I got a few gigabytes copied before the oops. After that I googled and figured out the rest, I didn't test if there really was some data loss (didn't ever mount the partition again). Based on the status as a known-buggy and unsupported config I think this bug should be downgraded to non-RC status for etch, but I'd like to be sure first that I understand the impact of any real-world risk of data loss. No objection to that. Though it of course would have been be very helpful if something somewhere (eg. the kernel at mount time) notified me that the config is unsupported. Sami signature.asc Description: Digital signature
Bug#410204: linux-image-2.6.18-4-amd64: Data corruption on dm-crypt+XFS
Package: linux-image-2.6.18-4-amd64 Version: 2.6.18.dfsg.1-10 Severity: critical Tags: patch Justification: causes serious data loss The current latest 2.6 kernel in unstable causes serious data loss when using XFS over dm-crypt due to a bug or a number of bugs in dm-crypt. Generally XFS metadata corruption sooner or later causes an oops. It's not clear if this will be triggered by anything else than XFS, but that triggers it easily and often. A fix was merged upstream in 2.6.18.6 ([PATCH] dm crypt: Fix data corruption with dm-crypt over RAID5), but is not apparently included in the Debian kernel (or at least I ran into this with a very similar backtrace). See: 1. http://bugzilla.kernel.org/show_bug.cgi?id=7258 (There's some kind of patch referenced in comment #4 and available at http://marc.theaimsgroup.com/?l=linux-kernelm=116503133222152w=2) Also note 2. http://bugzilla.kernel.org/show_bug.cgi?id=7799 (esp. the last comment: Bug in dmcrypt. There's been several bugs in dmcrypt that only XFS has triggered and the last of these that I know about was fixed in 2.6.19.) Sami -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-amd64 Locale: LANG=C, [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages linux-image-2.6.18-4-amd64 depends on: ii coreutil 5.97-5.3The GNU core utilities ii debconf 1.5.11 Debian configuration management sy ii e2fsprog 1.39+1.40-WIP-2006.11.14+dfsg-1 ext2 file system utilities and lib ii initramf 0.85e tools for generating an initramfs ii module-i 3.3-pre4-1 tools for managing Linux kernel mo ii yaird [l 0.0.12-18 Yet Another mkInitRD linux-image-2.6.18-4-amd64 recommends no packages. -- debconf information: linux-image-2.6.18-4-amd64/postinst/kimage-is-a-directory: linux-image-2.6.18-4-amd64/postinst/bootloader-test-error-2.6.18-4-amd64: linux-image-2.6.18-4-amd64/preinst/lilo-initrd-2.6.18-4-amd64: true linux-image-2.6.18-4-amd64/preinst/initrd-2.6.18-4-amd64: linux-image-2.6.18-4-amd64/preinst/failed-to-move-modules-2.6.18-4-amd64: linux-image-2.6.18-4-amd64/postinst/old-initrd-link-2.6.18-4-amd64: true linux-image-2.6.18-4-amd64/preinst/lilo-has-ramdisk: linux-image-2.6.18-4-amd64/postinst/old-dir-initrd-link-2.6.18-4-amd64: true linux-image-2.6.18-4-amd64/prerm/removing-running-kernel-2.6.18-4-amd64: true linux-image-2.6.18-4-amd64/preinst/already-running-this-2.6.18-4-amd64: linux-image-2.6.18-4-amd64/preinst/abort-install-2.6.18-4-amd64: shared/kernel-image/really-run-bootloader: true linux-image-2.6.18-4-amd64/preinst/abort-overwrite-2.6.18-4-amd64: linux-image-2.6.18-4-amd64/postinst/depmod-error-initrd-2.6.18-4-amd64: false linux-image-2.6.18-4-amd64/postinst/create-kimage-link-2.6.18-4-amd64: true linux-image-2.6.18-4-amd64/postinst/depmod-error-2.6.18-4-amd64: false linux-image-2.6.18-4-amd64/postinst/bootloader-error-2.6.18-4-amd64: linux-image-2.6.18-4-amd64/postinst/old-system-map-link-2.6.18-4-amd64: true linux-image-2.6.18-4-amd64/preinst/bootloader-initrd-2.6.18-4-amd64: true linux-image-2.6.18-4-amd64/preinst/overwriting-modules-2.6.18-4-amd64: true linux-image-2.6.18-4-amd64/preinst/elilo-initrd-2.6.18-4-amd64: true linux-image-2.6.18-4-amd64/prerm/would-invalidate-boot-loader-2.6.18-4-amd64: true signature.asc Description: Digital signature
Bug#410204: linux-image-2.6.18-4-amd64: Data corruption on dm-crypt+XFS
On Thu, Feb 08, 2007 at 05:11:32PM +0200, Sami Liedes wrote: XFS, but that triggers it easily and often. A fix was merged upstream in 2.6.18.6 ([PATCH] dm crypt: Fix data corruption with dm-crypt over RAID5), but is not apparently included in the Debian kernel (or at least I ran into this with a very similar backtrace). See: Hmm, seems it (the entire 2.6.18.6) IS included in the Debian kernel. I wonder which fix is missing then, or if the bug is still in the vanilla kernel tree. Here's the oops: Feb 8 04:43:08 lh kernel: Filesystem dm-7: Disabling barriers, not supported by the underlying device Feb 8 04:43:08 lh kernel: XFS mounting filesystem dm-7 Feb 8 04:43:08 lh kernel: Ending clean XFS mount for filesystem: dm-7 Feb 8 04:46:10 lh kernel: Unable to handle kernel NULL pointer dereference at RIP: Feb 8 04:46:10 lh kernel: [802a749a] page_to_pfn+0x0/0x33 Feb 8 04:46:10 lh kernel: PGD 24a6c067 PUD 1da31067 PMD 0 Feb 8 04:46:10 lh kernel: Oops: [1] SMP Feb 8 04:46:10 lh kernel: CPU 0 Feb 8 04:46:10 lh kernel: Modules linked in: sha256 aes dm_crypt snd_intel8x0 xfs ipt_owner ipt_REJECT xt_state xt_tcpudp iptable_filter ipt_MASQUERADE iptable_nat ip_nat ip_conntrack nfnetlink ip_tables x_tables radeon drm binfmt_misc freq_table ppdev lp button ac battery ipv6 nls_iso8859_1 nls_cp437 vfat fat ext2it87 hwmon_vid i2c_isa eeprom usbmouse ide_cd cdrom tsdev snd_ac97_codec snd_ac97_bus snd_opl3_lib snd_pcm_oss snd_mixer_oss snd_hwdep snd_mpu401 snd_mpu401_uart i2c_nforce2 snd_rawmidi snd_seq_device analog i2c_core parport_pc parport snd_pcm snd_timer psmouse serio_raw snd snd_page_alloc gameport evdev floppy soundcore pcspkr ext3 jbd mbcache dm_mirror dm_snapshot dm_mod ide_generic sd_mod ide_disk sata_nv libata scsi_mod 3c59x mii forcedeth generic amd74xx ide_core ehci_hcd ohci_hcd thermal processor fan Feb 8 04:46:10 lh kernel: Pid: 198, comm: pdflush Not tainted 2.6.18-4-amd64 #1 Feb 8 04:46:10 lh kernel: RIP: 0010:[802a749a] [802a749a] page_to_pfn+0x0/0x33 Feb 8 04:46:10 lh kernel: RSP: 0018:81003e7e97d8 EFLAGS: 00010297 Feb 8 04:46:10 lh kernel: RAX: RBX: 81000bce2640 RCX: Feb 8 04:46:10 lh kernel: RDX: 0056 RSI: 81000bce2640 RDI: Feb 8 04:46:10 lh kernel: RBP: 81003b3c8000 R08: R09: 810037ade870 Feb 8 04:46:10 lh kernel: R10: R11: 81000c1a1ec0 R12: 81000bce2640 Feb 8 04:46:10 lh kernel: R13: R14: R15: 81003e8f8088 Feb 8 04:46:10 lh kernel: FS: 2b4d40df3d20() GS:80521000() knlGS:f7b446c0 Feb 8 04:46:10 lh kernel: CS: 0010 DS: 0018 ES: 0018 CR0: 8005003b Feb 8 04:46:10 lh kernel: CR2: CR3: 1e0c6000 CR4: 06e0 Feb 8 04:46:10 lh kernel: Process pdflush (pid: 198, threadinfo 81003e7e8000, task 810037ade870) Feb 8 04:46:10 lh kernel: Stack: 8022bf96 810037ade870 d400 Feb 8 04:46:10 lh kernel: 8101 0001 81000bce2640 81003e8f8088 Feb 8 04:46:10 lh kernel: 8100192517c0 810007f997a8 0056 0002a000 Feb 8 04:46:10 lh kernel: Call Trace: Feb 8 04:46:10 lh kernel: [8022bf96] blk_recount_segments+0x7e/0x21b Feb 8 04:46:10 lh kernel: [802bb9ae] __bio_clone+0x71/0x8a Feb 8 04:46:10 lh kernel: [802bb9fc] bio_clone+0x35/0x3d Feb 8 04:46:10 lh kernel: [8822776a] :dm_crypt:crypt_map+0xcd/0x304 Feb 8 04:46:10 lh kernel: [880d92bf] :dm_mod:__map_bio+0x47/0x9b Feb 8 04:46:10 lh kernel: [880d9c1f] :dm_mod:__split_bio+0x172/0x37d Feb 8 04:46:10 lh kernel: [880da432] :dm_mod:dm_request+0x101/0x110 Feb 8 04:46:10 lh kernel: [80219f55] generic_make_request+0x13a/0x14d Feb 8 04:46:10 lh kernel: [80231028] submit_bio+0xcb/0xd2 Feb 8 04:46:10 lh kernel: [8022aaa5] __bio_add_page+0x188/0x1ce Feb 8 04:46:10 lh kernel: [883ccd8b] :xfs:xfs_submit_ioend_bio+0x1e/0x27 Feb 8 04:46:10 lh kernel: [883cd7c3] :xfs:xfs_page_state_convert+0xa2f/0xb6e Feb 8 04:46:10 lh kernel: [883cdb30] :xfs:xfs_vm_writepage+0xa7/0xdd Feb 8 04:46:10 lh kernel: [8021ac61] mpage_writepages+0x1a6/0x34d Feb 8 04:46:10 lh kernel: [883cda89] :xfs:xfs_vm_writepage+0x0/0xdd Feb 8 04:46:10 lh kernel: [80256d07] do_writepages+0x20/0x2f Feb 8 04:46:10 lh kernel: [8022dbd7] __writeback_single_inode+0x1b4/0x38b Feb 8 04:46:10 lh kernel: [880d9a46] :dm_mod:dm_any_congested+0x38/0x3f Feb 8 04:46:10 lh kernel: [880db58a] :dm_mod:dm_table_any_congested+0x46/0x63 Feb 8 04:46:10 lh kernel: [8021edb1] sync_sb_inodes+0x1d1/0x2b5 Feb 8 04:46:10 lh kernel: [802901be
Bug#314923: Broken in 5.99.1+dev4-3
package grace6 found 314923 5.99.1+dev4-3 thanks Hello, I get this exact error message after installing grace6 on my system. strace output suggests the reason is that it fails to open /usr/share/grace6/fonts/type1/LinLibertine-2.1.0.pfb, which is a broken symlink to /usr/share/fonts/type1/linux-libertine/LinLibertine-2.1.0.pfb. All the other LinLibertine*-2.1.0.pfb symlinks are broken as well (but symlinks to newer versions are not). If it matters, the other broken symlinks in the directory are tip*.pfb and xip*.pfb (but not the corresponding .afm files). Sami signature.asc Description: Digital signature
Bug#405510: Build process sets the eog-$VER directory perms to 777
Package: eog Version: 2.16.2-1 Severity: grave Tags: security Justification: user security hole This is a user security hole only on systems where the package is built. Sorry if this doesn't qualify it for the grave severity. The build process of eog sets the perms of the entire eog-$VERSION subdirectory and all its subdirectories to 777 before compilation. This allows a local attacker to do any nastiness to the source files or scripts that subsequently get packaged in a .deb. The attacker can also choose to run any code as the user building the package. Sami -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-amd64 Locale: LANG=C, [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages eog depends on: ii gconf2 2.16.0-3GNOME configuration database syste ii libart-2.0-2 2.3.17-1Library of functions for 2D graphi ii libc62.3.6.ds1-9 GNU C Library: Shared libraries ii libexif120.6.13-5library to parse EXIF files ii libgconf2-4 2.16.0-3GNOME configuration database syste ii libglade2-0 1:2.6.0-4 library to load .glade files at ru ii libglib2.0-0 2.12.6-2The GLib library of C routines ii libgnome-desktop-2 2.14.3-1Utility library for loading .deskt ii libgnome2-0 2.16.0-2The GNOME 2 library - runtime file ii libgnomecanvas2-02.14.0-2A powerful object-oriented display ii libgnomeprint2.2-0 2.12.1-7The GNOME 2.2 print architecture - ii libgnomeprintui2.2-0 2.12.1-4GNOME 2.2 print architecture User ii libgnomeui-0 2.14.1-2+b1 The GNOME 2 libraries (User Interf ii libgnomevfs2-0 2.14.2-4GNOME virtual file-system (runtime ii libgtk2.0-0 2.8.20-3The GTK+ graphical user interface ii libjpeg626b-13 The Independent JPEG Group's JPEG ii liblcms1 1.15-1 Color management library ii libpango1.0-01.14.8-4Layout and rendering of internatio ii libx11-6 2:1.0.3-4 X11 client-side library Versions of packages eog recommends: ii librsvg2-common 2.14.4-2 SAX-based renderer library for SVG -- no debconf information signature.asc Description: Digital signature
Bug#345384: Fix
tag 345384 + patch
thanks
Having the same problem, I tracked it down. BTW getting a good
backtrace wasn't easy, what I ended up doing was grepping the source
for string replaces (which weren't that numerous) and setting
breakpoints.
The attached patch fixes this problem at least for me. The problem was
that std::string:npos is negative. Carefully reading compiler output
would also have caught this (warning about a comparison being always
false due to a limited data type). Maybe I'll take some time and read
the build log later today to see if there's more such warnings.
Sami
--- widelands-build9half/src/text_parser.cc 2005-11-25 14:16:31.0
+0200
+++ widelands-fixed/src/text_parser.cc 2006-01-07 10:38:35.0 +0200
@@ -39,7 +39,7 @@
}
text.erase(0,2);
- uint format_end = text.find();
+ int format_end = text.find();
if (format_end == std::string::npos) {
log(WARNING: Formatdefinition of block '%s' not
closed\n,(text.substr(0,30)+...).c_str());
return;
@@ -48,7 +48,7 @@
std::string block_format = text.substr(0,format_end);
text.erase(0,format_end+1);
- uint block_end = text.find(/p);
+ int block_end = text.find(/p);
if (block_end == std::string::npos) {
log(WARNING: Block '%s' not
closed!\n,(text.substr(0,30)+...).c_str());
@@ -63,14 +63,14 @@
// Replace br in text block through newlines. This is needed for
// Texts which may not contain newlines ( for example from conf files )
- uint newline;
+ int newline;
while( (newline = block_text.find(br)) != std::string::npos ) {
block_text.replace( newline, 4, \n );
}
// Serch for map variables
- uint offset;
+ int offset;
while( (offset = block_text.find(variable name=)) !=
std::string::npos) {
- uint end = block_text.find();
+ int end = block_text.find();
if( end == std::string::npos ) {
log(WARNING: variable tag not closed!\n);
} else {
@@ -106,13 +106,13 @@
format.erase(0,1);
while (format.size()) {
- uint key_end = format.find(=);
+ int key_end = format.find(=);
if (key_end == std::string::npos)
return;
else {
std::string key = format.substr(0,key_end);
format.erase(0,key_end+1);
- uint val_end = format.find( );
+ int val_end = format.find( );
if (val_end == std::string::npos)
val_end = format.size();
std::string val = format.substr(0,val_end);
signature.asc
Description: Digital signature
