Bug#643336: libgcrypt11: New 1.5.0 version segfaults with NSS/PAM LDAP
Package: libgcrypt11 Version: 1.5.0-5+deb7u2 Followup-For: Bug #643336 Dear Maintainer, Reporting the problem from a different machine since the one encountering the problem is not available right now. This one is similar though (same versions). We are in the process of moving from a LDAP server to a new one. The new one only accepts ldaps:// connections, while the previous one only accepted ldap:// ones Since we've modified libnss-ldap.conf and pam-ldap.conf to point to the new LDAP server and use ldaps:// instead of ldap, we've got segfaults everywhere : dbus, nscd, login, and so on... No other file was modified, excepted libnss-ldap.secret to contain the LDAP admin password. Of course the old and new LDAP servers differ by their content. In particular the new one contains user groups, and some of them are very huge : there are >3000 members in some groups, although the usernames tested so far are in much smaller groups, like 200 members only. These segfaults appear to be random, for example just after booting I'll be able to do "getent passwd username" a few times which will work, and then it will segfault and will never work again. When getent segfaults, if nscd is active, then nscd will segfault at the very same time (or the other way around). Here are some logs from syslog : Dec 17 11:14:12 10.10.11.128 kernel: [ 33.292821] dbus-daemon[2807] general protection ip:b71c20ea sp:bfd4a360 error:0 in libgcrypt.so.11.7.0[b7198000+81000] Dec 17 11:14:29 10.10.11.128 kernel: [ 50.388001] nscd[3211] general protection ip:aeaab0ea sp:af5bf92c error:0 in libgcrypt.so.11.7.0[aea81000+81000] Dec 17 11:14:31 10.10.11.128 kernel: [ 52.726956] login[4215] general protection ip:b73920ea sp:bfb4149c error:0 in libgcrypt.so.11.7.0[b7368000+81000] Dec 17 11:14:46 10.10.11.128 kernel: [ 67.053518] login[4248] general protection ip:b73d00ea sp:bfc1f8cc error:0 in libgcrypt.so.11.7.0[b73a6000+81000] Dec 17 11:14:52 10.10.11.128 kernel: [ 73.002957] login[4286] general protection ip:b73020ea sp:bfd4095c error:0 in libgcrypt.so.11.7.0[b72d8000+81000] Dec 17 11:14:54 10.10.11.128 kernel: [ 75.095612] login[4310] general protection ip:b731e0ea sp:bf9cce1c error:0 in libgcrypt.so.11.7.0[b72f4000+81000] Dec 17 11:14:59 10.10.11.128 kernel: [ 80.519214] login[4312] general protection ip:b73480ea sp:bfaa89fc error:0 in libgcrypt.so.11.7.0[b731e000+81000] Dec 17 11:17:01 10.10.11.128 kernel: [ 202.333460] cron[4698] general protection ip:b720e0ea sp:bff20a9c error:0 in libgcrypt.so.11.7.0[b71e4000+81000] Even doing "su - username" segfaults. I won't be able to make our new LDAP server accept ldap:// connections until the last week of December, unfortunately. Is there anything else which could be done ? Thanks in advance -- System Information: Debian Release: 7.7 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libgcrypt11 depends on: ii libc6 2.13-38+deb7u6 ii libgpg-error0 1.10-3.1 ii multiarch-support 2.13-38+deb7u6 libgcrypt11 recommends no packages. Versions of packages libgcrypt11 suggests: pn rng-tools -- no debconf information -- Jerome Alet -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#644444: pkpgcounter does not properly handle all postscript documents with copies or n-up options
Hi, On Wed, Oct 05, 2011 at 06:05:48PM -0500, Brian Paul Kroth wrote: > > I attempted to pass this info to the original dev, but haven't gotten > any response. I'm sorry for this. I'm slowly recovering from an accident and I'll try to be back at work on this and several other issues in this software and other related projects as soon as possible. bye Jerome Alet -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#613836: Unable to run pkpgcounter on Squeeze
On Thu, Feb 17, 2011 at 05:10:13PM +0100, Sébastien ERMACORE wrote: > Package: pkpgcounter > Version: 3.50-7 > Severity: important > > > When running the following command : pkpgcounter --colorspace=cmy > --resolution=300 file.pdf > console returns : > > Traceback (most recent call last): > File "/usr/bin/pkpgcounter", line 109, in > analyzer.main() > File "/usr/lib/pymodules/python2.6/pkpgpdls/analyzer.py", line 235, in main > (cspace, pages) = parser.getInkCoverage() > File "/usr/lib/pymodules/python2.6/pkpgpdls/analyzer.py", line 88, > in getInkCoverage > result = inkcoverage.getInkCoverage(filename, cspace) > File "/usr/lib/pymodules/python2.6/pkpgpdls/inkcoverage.py", line > 124, in getInkCoverage > result.append(computation(image, nbpixels)) > File "/usr/lib/pymodules/python2.6/pkpgpdls/inkcoverage.py", line > 93, in getPercentCMY > result = getPercentRGB(img, nbpix) > File "/usr/lib/pymodules/python2.6/pkpgpdls/inkcoverage.py", line > 89, in getPercentRGB > return getPercent(img, nbpix) > File "/usr/lib/pymodules/python2.6/pkpgpdls/inkcoverage.py", line > 41, in getPercent > bands = img.split() > File "/usr/lib/python2.6/dist-packages/PIL/Image.py", line 1497, in split > if self.im.bands == 1: > AttributeError: 'NoneType' object has no attribute 'bands' I can confirm the problem. To me it looks like a bug in the Python Imaging Library, unless its API has changed. I'll look into this ASAP. bye Jerome Alet -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#543772: xl2tpd should create /var/run/xl2tpd/ on startup
Package: xl2tpd Version: 1.2.0+dfsg-1 Severity: normal With /var/run mounted as a tmpfs filesystem (untested with a regular filesystem), the directory /var/run/xl2tpd/ doesn't exist after a reboot and xl2tpd can't create its control pipe, so when starting xl2tpd we've got this in /var/log/daemon.log : xl2tpd[4363]: open_controlfd: Unable to open /var/run/xl2tpd/l2tp-control for reading. The startup script, or xl2tpd itself, should ensure the /var/run/xl2tpd/ directory exists and create it if needed. hth Jerome Alet -- System Information: Debian Release: 5.0.2 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages xl2tpd depends on: ii libc6 2.7-18GNU C Library: Shared libraries ii ppp2.4.4rel-10.1 Point-to-Point Protocol (PPP) - da xl2tpd recommends no packages. xl2tpd suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#532567: Missing dependency: python-imaging
On Wed, Jun 10, 2009 at 09:45:24AM +0100, Klaus Ethgen wrote: > Package: pkpgcounter > Version: 3.50-4 > Severity: serious > > The package misses the dependency to python-imaging: > ERROR: You MUST install the Python Imaging Library (python-imaging) for > pkpgcounter to work. >Traceback (most recent call last): > File "/usr/bin/pkpgcounter", line 27, in >from pkpgpdls import analyzer > File "/usr/lib/python2.5/site-packages/pkpgpdls/analyzer.py", line 30, > in >import version, pdlparser, postscript, pdf, pcl345, pclxl, hbp, \ > File "/usr/lib/python2.5/site-packages/pkpgpdls/postscript.py", line 29, > in >import inkcoverage > File "/usr/lib/python2.5/site-packages/pkpgpdls/inkcoverage.py", line > 33, in >raise pdlparser.PDLParserError, "The Python Imaging Library is > missing." >pkpgpdls.pdlparser.PDLParserError: The Python Imaging Library is missing. > > -- System Information: > Debian Release: 5.0.1 > APT prefers stable > APT policy: (800, 'stable'), (700, 'oldstable'), (600, 'unstable'), (60, > 'experimental') > Architecture: i386 (i686) > > Kernel: Linux 2.6.28.7 > Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) (ignored: LC_ALL set > to de_DE) > Shell: /bin/sh linked to /bin/dash > > Versions of packages pkpgcounter depends on: > ii ghostscript8.62.dfsg.1-3.2lenny1 The GPL Ghostscript > PostScript/PDF > ii python 2.5.2-3 An interactive high-level > object-o > ii python-central 0.6.8 register and build utility for > Pyt > ii python-imaging 1.1.6-3 Python Imaging Library As you can see right above, pkpgcounter depends on python-imaging already. Are you sure there's no permission problem in /usr/lib/python2.?/site-packages/PIL ? bye Jerome Alet signature.asc Description: Digital signature
Bug#525839: Abnormal recommandations (abiword ...) for pkpgcounter package in case of server environment
On Mon, Apr 27, 2009 at 02:47:49PM +0200, FERRAND Adrien wrote: > Package: pkpgcounter > Version: 3.50-4 > Severity: wishlist > > Hello. > > As you can see below, pkpgcounter recommends some packages like abiword. For > a desktop usage, it seems normal to recommend a > text editor. But for a server usage, theses recommendations can make aptitude > install all X libraries if the user is not > careful ( as aptitude install recommended packages by default ). > > Indeed pkpgcounter can be used for printing quotas ( like pykota ) with cups. > > It's just a suggestion, but you could remove theses recommendations for > pkpgcounter, in order to avoid useless overcharge for > careless user. pkpgcounter depends on abiword only to do correct accounting of Microsoft Word documents. This never happens when pkpgcounter is used as part of PyKota, since in this case pkpgcounter only deals with printers page description languages like PCL or PostScript. However pkpgcounter can also be used directly on several file formats, including .DOC, and for this particular format it first converts the document through abiword, because wvware (iirc), though a command line software, didn't always do the job as expected. not sure how to deal with this, besides explaining why each dependency is needed (or not). bye Jerome Alet -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#515184: pkpgcounter failes to read PJL-wrapped postscript
On Tue, Feb 24, 2009 at 11:02:10AM +0100, Joachim Breitner wrote: > > The .ppd file is the one downloaded from > http://kyoceramita.com/download/ > for Kyocera_FS-C5300DN (German, that is at > http://www.kyoceramita.eu/index/service/dlc.false.driver.FSC5300DN._.EN.html > the very bottom. > > I have little hope to get them change their .ppd, especially as it does > the job (provide printing). Of course. > > As an alternative just create a new ticket on http://trac.pykota.com, > > and I'll try to add some filtering facility to pkpgcounter. > > I’d do that, but http://trac.pykota.com/register does not seem to > work... It should work, but there's probably some caching issue between your web browser and the server. Try to force reload. bye, and thx again for your feedback. Jerome Alet signature.asc Description: Digital signature
Bug#515184: pkpgcounter failes to read PJL-wrapped postscript
Hi, On Mon, Feb 16, 2009 at 06:43:26PM +0100, Joachim Breitner wrote: > > Am Montag, den 16.02.2009, 18:39 +0100 schrieb a...@librelogiciel.com: > > On Mon, Feb 16, 2009 at 06:23:56PM +0100, Joachim Breitner wrote: > > > > > > I’d expect them so see the latter case (PS interpreter), but from a user > > > point of view, it doesn’t matter much :-) > > > > It seems the bug report was accepted by GhostScript's upstream > > developers, and there's a patch, please see : > > > > http://bugs.ghostscript.com/show_bug.cgi?id=690291 > > > > Hoping this fixes your problem. > > ok, even better, thanks for taking care of this! Unfortunately they've decided against fixing this problem upstream finally, see their BTS link above. If you know for sure these datas were produced with foomatic maybe you could see if its authors would mind putting their Kyocera Prescribe code sequence as part of a @PJL COMMENT as proposed, and if Kyocera printers would still support such a construct (I don't have such a printer so I can't tell) As an alternative just create a new ticket on http://trac.pykota.com, and I'll try to add some filtering facility to pkpgcounter. (you can do both if you want) bye Jerome Alet signature.asc Description: Digital signature
Bug#515184: pkpgcounter failes to read PJL[well, it's not PJL]-wrapped postscript
Hi, On Wed, Feb 18, 2009 at 05:22:11PM +0200, SaGS wrote: > > I’m not a Debian user, but noticed the bug filed against Ghostscript and > would like to make a comment and suggest another thing to try. > > First, the sample file is *not* valid PJL+PostScript. The "!R! ... etc ... > EXIT;" part is Kyocera's Prescribe. That's where the error comes from, as > GS does not intrepret PRESCRIBE - as it does not interpret Epson's ESC/P > and others. > > Second, what I would like to suggest is to consider replacing the "!R! ... > etc" with "@PJL COMMENT !R! ... etc". Then the file will be valid > PJL+PostSCript, and there won't be any problems anymore. From what I > understad from Kyocera's documentation, the "!R!" is recognized in any > context, so I expect it has the desired effect even if "cloaked" inside a > "@PJL COMMENT". Unfortunately, I don't have such a printer to check. And, > where does this "!R!..." come from in the first place? Is it from a PPD? If > yes, and my idea works, then this bug is very easy to fix by changing the > PPD, without the need for an ugly workaround in Ghostscript. I think the test file was produced through foomatic, but only the original submitter could confirm this. Your idea seems excellent to me, but just like you I can't test it. bye Jerome Alet -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#515184: pkpgcounter failes to read PJL-wrapped postscript
On Mon, Feb 16, 2009 at 06:23:56PM +0100, Joachim Breitner wrote: > > I’d expect them so see the latter case (PS interpreter), but from a user > point of view, it doesn’t matter much :-) It seems the bug report was accepted by GhostScript's upstream developers, and there's a patch, please see : http://bugs.ghostscript.com/show_bug.cgi?id=690291 Hoping this fixes your problem. bye Jerome Alet signature.asc Description: Digital signature
Bug#515184: pkpgcounter failes to read PJL-wrapped postscript
On Sun, Feb 15, 2009 at 03:05:04PM +0100, Joachim Breitner wrote: > > I’m not sure if I can follow this argument. The attached print file was > not valid postscript, but rather postscript wrapped in an PJL print job, > if I understand it correctly. Therefore, it can not be a bug in > ghostscript. You may be correct. However, simply take pykota and pkpgcounter out of the equation, and use instead the cups-pdf backend for CUPS, written by Volker C. Behr. I bet you'll have the very same problem (untested, but from reading its source code it launches gs and doesn't strip out any PJL). This means this bug should be reported to any similar software, duplicating efforts needlessly. Really it depends if we consider gs is emulating a printer or is only a PS interpreter. In the first case it should recognize PJL's Universal Exit Language (%-12345X) because the document, as seen from a printer supporting PJL and PostScript, is perfectly correct. In the latter case it doesn't need to. Not sure what GhostScript developers think about this problem. > OTOH, pkpgcounter tries to handle data as sent to the printer, therefore > passing this file to pkpgycounter (as done by pykota in my case) is > correct. > > It seems that the included simple postscript parser is liberal enough to > skip the PJL header, but I think it’s still pkpgcounter’s responsibility > to make sure ghostscript understands the data it passes to it. > > Also, it seems there might be PJL SET COPIES command that needs to be > taken in account (but this is probably a different issue, and I’m not > sure if it should be handled by pykota or pkpgcounter). pkpgcounter should handle number of copies specified as PJL, but there's currently a bug in it, preventing such PJL statements inserted before the very first page to be taken into account (see http://trac.pykota.com/ticket/2) But as you said this is an entirely different problem. It seems someone reported the same problem in 2004 : https://lists.linux-foundation.org/pipermail/printing-foomatic/2004/001983.html I'm not 100% against implementing a workaround for this problem, but I'd prefer that ghostscript developers handle this situation, otherwise other developers would have to create similar workarounds for their own software. Is it possible with Debian's BTS to have them involved in this discussion ? bye Jerome Alet signature.asc Description: Digital signature
Bug#515184: pkpgcounter failes to read PJL-wrapped postscript
On Sat, Feb 14, 2009 at 04:13:12PM +0100, a...@librelogiciel.com wrote: > > This is a bug in GhotScript, not in pkpgcounter as can be seen below : In any case, if you want a workaround to be considered for a future release, please create a ticket asking so on http://trac.pykota.com thx in davance Jerome Alet -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#515184: pkpgcounter failes to read PJL-wrapped postscript
On Sat, Feb 14, 2009 at 03:21:00PM +0100, Joachim Breitner wrote: > Package: pkpgcounter > Version: 3.50-4 > Severity: normal > Tags: patch > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi, > > when trying to get ink accounting working here, it failed because the > file that CUPS sent to pkpgcounter (via pykota) contained a PJL header: > > $ pkpgcounter -cGC /var/spool/cups/tmp/cupspykota-Insterdrucker-nomeata-21 > Error: /undefined in > !R!CRES;SCRN0;RGBL0,0;RGBL1,0;RGBL2,0;HUE0,0;HUE1,0;HUE2,0;HUE3,0;HUE4,0;HUE5,0;HUE6,0;LGHT0,0;LGHT1,0;SATU0;EXIT; > perand stack: > > Execution stack: >%interp_exit .runexec2 --nostringval-- --nostringval-- > --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- > --nostringval-- false 1 %stopped_push 1905 1 3 %oparray_pop > 1904 1 3 %oparray_pop 1888 1 3 %oparray_pop 1771 1 3 > %oparray_pop --nostringval-- %errorexec_pop .runexec2 --nostringval-- > --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- > Dictionary stack: >--dict:1156/1684(ro)(G)-- --dict:0/20(G)-- --dict:92/200(L)-- > Current allocation mode is local > Current file position is 262 > GPL Ghostscript 8.62: Unrecoverable error, exit code 1 > Command failed : 'gs -sDEVICE=tiff24nc -dPARANOIDSAFER -dNOPAUSE -dBATCH > -dQUIET -r"72" -sOutputFile="/tmp/tmp1TpTnP" > "/var/spool/cups/tmp/cupspykota-Insterdrucker-nomeata-21"' > > A test file is appended. > > I could work around by adding a PJL-removing script to the package and adding > a second totiffcommand that tries it with that, but I assume that is not the > proper solution. This is a bug in GhotScript, not in pkpgcounter as can be seen below : jer...@lafrime:~$ gs testprintfile GPL Ghostscript 8.62 (2008-02-29) Copyright (C) 2008 Artifex Software, Inc. All rights reserved. This software comes with NO WARRANTY: see the file PUBLIC for details. Error: /undefined in !R!CRES;SCRN0;RGBL0,0;RGBL1,0;RGBL2,0;HUE0,0;HUE1,0;HUE2,0;HUE3,0;HUE4,0;HUE5,0;HUE6,0;LGHT0,0;LGHT1,0;SATU0;EXIT; perand stack: Execution stack: %interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 1905 1 3 %oparray_pop 1904 1 3 %oparray_pop 1888 1 3 %oparray_pop 1771 1 3 %oparray_pop --nostringval-- %errorexec_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- Dictionary stack: --dict:1151/1684(ro)(G)-- --dict:0/20(G)-- --dict:92/200(L)-- Current allocation mode is local Current file position is 262 GPL Ghostscript 8.62: Unrecoverable error, exit code 1 jer...@lafrime:~$ pkpgcounter itself correctly parses the file with its internal parser, which doesn't try to interpret postscript (and so is limited of course) : jer...@lafrime:~$ pkpgcounter --debug testprintfile Input file is in the 'PostScript' file format. 1 * page #1 1 * page #2 Internal parser said : 2 pages 2 jer...@lafrime:~$ but when pkpgcounter wants to convert this file to TIFF to do ink usage based print accounting, it uses GhostScript (because it was easier ;-) and so it fails because of GhostScript's own failure to read this file. not sure how to reassign this bug to ghostscript, but this is what to do. in any case, thanks a lot for your feedback. hth Jerome Alet -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#507770: [Python-apps-team] Bug#507770: pkpgcounter: temporary files are not removed
On Thu, Dec 04, 2008 at 11:29:50AM -0600, Kumar Appaiah wrote: > On Thu, Dec 4, 2008 at 11:20 AM, wrote: 5B> >> The pkpgcounter currently in lenny doesn't seem to remove temporary > >> files from /tmp and /var/tmp if /tmp gets full. It also doesn't honnor > >> the directory setting from pykota.conf. > >> > >> Also reported here: > >> > >> http://article.gmane.org/gmane.comp.printing.pykota.user/5747 > >> > >> This appears to be fixed in svn: > >> > >> r3460 | jerome | 2008-11-25 00:54:51 +0100 (Tue, 25 Nov 2008) | 3 lines > > > > Upstream here : code not yet ready for a stable release, probably during > > December or January. > > No problem. For now, I have backported the patch, and will be checking > an uploading a minimal changed version to fix this bug alone. Thanks for your help on this, I can't really work on finalizing an upstream release right now. bye Jerome Alet -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#507770: pkpgcounter: temporary files are not removed
On Thu, Dec 04, 2008 at 12:05:56PM +0100, Rik Theys wrote: > Package: pkpgcounter > Version: 3.50-2 > Severity: important > > *** Please type your report below this line *** > > The pkpgcounter currently in lenny doesn't seem to remove temporary > files from /tmp and /var/tmp if /tmp gets full. It also doesn't honnor > the directory setting from pykota.conf. > > Also reported here: > > http://article.gmane.org/gmane.comp.printing.pykota.user/5747 > > This appears to be fixed in svn: > > r3460 | jerome | 2008-11-25 00:54:51 +0100 (Tue, 25 Nov 2008) | 3 lines Upstream here : code not yet ready for a stable release, probably during December or January. bye Jerome Alet -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#504007: today message changed
In case it helps, I've tried again to boot this faulty kernel today, and I've received a message like "EBDA too big, overlapping LILO second stage" or something like that. Just like Walter I use LILO and all my partitions are XFS (a single one in fact on this particular laptop) Since using GRUB with XFS partitions has left a bitter taste in my mouth a few years back, I'm not really sure if this is a LILO or kernel problem, nor how to fix it... bye Jerome Alet -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#504007: linux-image-2.6.26-1-686: My laptop doesn't boot anymore with this kernel
Package: linux-image-2.6.26-1-686 Version: 2.6.26-8 Severity: critical Justification: breaks the whole system My Acer Aspire 7720G laptop doesn't boot with this kernel image, since I did an apt-get dist-upgrade yesterday evening. Before that, i.e. until minutes before the apt-get dist-upgrade, the previous release of 2.6.26-1 which was active on this laptop worked fine. The kernel loads from disk (through LILO) and displays its usual lines of ... then goes to a new line with the blinking cursor, but never starts. Then just before the "BIOS data check complete" message (IIRC) it hangs, without displaying anything else, especially not this particular message. My CPU info : [EMAIL PROTECTED]:~$ cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Core(TM)2 Duo CPU T5250 @ 1.50GHz stepping: 13 cpu MHz : 1500.000 cache size : 2048 KB physical id : 0 siblings: 2 core id : 0 cpu cores : 2 fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe lm constant_tsc arch_perfmon pebs bts pni monitor ds_cpl est tm2 ssse3 cx16 xtpr lahf_lm bogomips: 2996.48 clflush size: 64 processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Core(TM)2 Duo CPU T5250 @ 1.50GHz stepping: 13 cpu MHz : 1500.000 cache size : 2048 KB physical id : 0 siblings: 2 core id : 1 cpu cores : 2 fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe lm constant_tsc arch_perfmon pebs bts pni monitor ds_cpl est tm2 ssse3 cx16 xtpr lahf_lm bogomips: 2992.54 clflush size: 64 -- Package-specific info: -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.25-2-686 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.26-1-686 depends on: ii debconf [debconf-2.0] 1.5.22 Debian configuration management sy ii initramfs-tools [linux-initra 0.92j tools for generating an initramfs ii module-init-tools 3.4-1 tools for managing Linux kernel mo Versions of packages linux-image-2.6.26-1-686 recommends: ii libc6-i6862.7-14 GNU C Library: Shared libraries [i Versions of packages linux-image-2.6.26-1-686 suggests: ii lilo 1:22.8-6 LInux LOader - The Classic OS load pn linux-doc-2.6.26 (no description available) -- debconf information: linux-image-2.6.26-1-686/preinst/abort-overwrite-2.6.26-1-686: linux-image-2.6.26-1-686/postinst/bootloader-error-2.6.26-1-686: linux-image-2.6.26-1-686/postinst/depmod-error-initrd-2.6.26-1-686: false linux-image-2.6.26-1-686/postinst/old-system-map-link-2.6.26-1-686: true linux-image-2.6.26-1-686/prerm/would-invalidate-boot-loader-2.6.26-1-686: true linux-image-2.6.26-1-686/preinst/elilo-initrd-2.6.26-1-686: true linux-image-2.6.26-1-686/postinst/old-dir-initrd-link-2.6.26-1-686: true linux-image-2.6.26-1-686/postinst/kimage-is-a-directory: linux-image-2.6.26-1-686/postinst/create-kimage-link-2.6.26-1-686: true linux-image-2.6.26-1-686/preinst/overwriting-modules-2.6.26-1-686: true linux-image-2.6.26-1-686/postinst/depmod-error-2.6.26-1-686: false shared/kernel-image/really-run-bootloader: true linux-image-2.6.26-1-686/prerm/removing-running-kernel-2.6.26-1-686: true linux-image-2.6.26-1-686/preinst/abort-install-2.6.26-1-686: linux-image-2.6.26-1-686/preinst/lilo-has-ramdisk: linux-image-2.6.26-1-686/preinst/bootloader-initrd-2.6.26-1-686: true linux-image-2.6.26-1-686/preinst/lilo-initrd-2.6.26-1-686: true linux-image-2.6.26-1-686/postinst/old-initrd-link-2.6.26-1-686: true linux-image-2.6.26-1-686/postinst/bootloader-test-error-2.6.26-1-686: linux-image-2.6.26-1-686/preinst/failed-to-move-modules-2.6.26-1-686: linux-image-2.6.26-1-686/preinst/initrd-2.6.26-1-686: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#491387: segfault in dspam_merge
Package: dspam Version: 3.6.8-5etch1 Severity: important When launching dspam_merge without any argument, there's a segfault : vazy:~# dspam_merge syntax: dspam_merge [user1] [user2] ... [userN] [-o user] *** glibc detected *** double free or corruption (out): 0xb7f1e4f8 *** Aborted vazy:~# hth Jerome Alet -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-xenU Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Versions of packages dspam depends on: ii libc6 2.3.6.ds1-13etch5 GNU C Library: Shared libraries ii libdspam7 3.6.8-5etch1 DSPAM is a scalable and statistica ii libldap2 2.1.30-13.3 OpenLDAP libraries ii procmail 3.22-16 Versatile e-mail processor Versions of packages dspam recommends: pn clamav-daemon (no description available) ii dspam-doc 3.6.8-5etch1 Documentation for dspam -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#479015: ntp: Impossible to activage debug mode
Package: ntp Version: 1:4.2.4p4+dfsg-3 Severity: important Either ntpd's manual page is incorrect, or ntpd is buggy. When specifying either -D or -d on ntpd's command line, the help is displayed and neither -d nor -D is shown to be part of the help message. It's just like if the manual page didn't match the executable. hth Jerome Alet -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages ntp depends on: ii adduser 3.107 add and remove users and groups ii libc6 2.7-10 GNU C Library: Shared libraries ii libcap1 1:1.10-14 support for getting/setting POSIX. ii libreadline5 5.2-3 GNU readline and history libraries ii libssl0.9.8 0.9.8g-8 SSL shared libraries ii lsb-base 3.2-11 Linux Standard Base 3.2 init scrip ii netbase 4.32 Basic TCP/IP networking system Versions of packages ntp recommends: ii perl 5.8.8-12 Larry Wall's Practical Extraction -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#472986: [SPAM?] Re: Bug#472986: /bin/su: su segfaults with libpam-p11 activated in /etc/pam.d/common-auth
Nicolas François wrote: Hello, On Fri, Apr 11, 2008 at 09:57:40AM +0200, [EMAIL PROTECTED] wrote: Nicolas François wrote: Could you also test if the bug is fixed in the new version 1:4.1.1-1? No it's not fixed in 1:4.1.1-1. Thanks for checking. With SYSLOG_SU_ENAB set to yes and the SULOG_FILE defined, nothing gets written to the file : the segfault occurs before. When deactivating the pkcs11 stuff, I've checked that this file gets correctly written to when using su. Commenting the SULOG_FILE line might fix this bug. Could you check this? I've checked again, because I think SULOG_FILE commented out with SYSLOG_SU_ENAB set to yes is the default : still segfaults. If it still fails, could you check disabling SYSLOG_SU_ENAB? same result : segfault. Are there also some lines related to su? I'm looking for messages like: su[...]: FAILED su for foo by bar None. Thanks for your time. hth Jerome Alet
Bug#472986: /bin/su: su segfaults with libpam-p11 activated in /etc/pam.d/common-auth
Here's an strace log attached to this message. hth Jerome Alet execve("/bin/su", ["su"], [/* 36 vars */]) = 0 brk(0) = 0x8053000 fcntl64(0, F_GETFD) = 0 fcntl64(1, F_GETFD) = 0 fcntl64(2, F_GETFD) = 0 access("/etc/suid-debug", F_OK) = -1 ENOENT (No such file or directory) access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory) mmap2(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb7f1f000 access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory) open("/etc/ld.so.cache", O_RDONLY) = 3 fstat64(3, {st_mode=S_IFREG|0644, st_size=77027, ...}) = 0 mmap2(NULL, 77027, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb7f0c000 close(3)= 0 access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory) open("/lib/libpam.so.0", O_RDONLY) = 3 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0p\31\0\000"..., 512) = 512 fstat64(3, {st_mode=S_IFREG|0644, st_size=37600, ...}) = 0 mmap2(NULL, 40460, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xb7f02000 mmap2(0xb7f0b000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x8) = 0xb7f0b000 close(3)= 0 access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory) open("/lib/libpam_misc.so.0", O_RDONLY) = 3 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\300\v\0"..., 512) = 512 fstat64(3, {st_mode=S_IFREG|0644, st_size=8176, ...}) = 0 mmap2(NULL, 11108, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xb7eff000 mmap2(0xb7f01000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1) = 0xb7f01000 close(3)= 0 access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory) open("/lib/i686/cmov/libc.so.6", O_RDONLY) = 3 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\260e\1"..., 512) = 512 fstat64(3, {st_mode=S_IFREG|0755, st_size=1360292, ...}) = 0 mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb7efe000 mmap2(NULL, 1365616, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xb7db mmap2(0xb7ef8000, 12288, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x148) = 0xb7ef8000 mmap2(0xb7efb000, 9840, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xb7efb000 close(3)= 0 access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory) open("/lib/i686/cmov/libdl.so.2", O_RDONLY) = 3 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0p\n\0\000"..., 512) = 512 fstat64(3, {st_mode=S_IFREG|0644, st_size=9684, ...}) = 0 mmap2(NULL, 12412, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xb7dac000 mmap2(0xb7dae000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1) = 0xb7dae000 close(3)= 0 mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb7dab000 set_thread_area({entry_number:-1 -> 6, base_addr:0xb7dab6b0, limit:1048575, seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1, seg_not_present:0, useable:1}) = 0 mprotect(0xb7ef8000, 4096, PROT_READ) = 0 munmap(0xb7f0c000, 77027) = 0 brk(0) = 0x8053000 brk(0x8074000) = 0x8074000 open("/usr/lib/locale/locale-archive", O_RDONLY|O_LARGEFILE) = 3 fstat64(3, {st_mode=S_IFREG|0644, st_size=1535488, ...}) = 0 mmap2(NULL, 1535488, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb7c34000 close(3)= 0 getuid32() = 1000 ioctl(0, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig icanon echo ...}) = 0 ioctl(0, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig icanon echo ...}) = 0 readlink("/proc/self/fd/0", "/dev/pts/4", 4095) = 10 socket(PF_FILE, SOCK_STREAM, 0) = 3 fcntl64(3, F_SETFL, O_RDWR|O_NONBLOCK) = 0 connect(3, {sa_family=AF_FILE, path="/var/run/nscd/socket"}, 110) = -1 ENOENT (No such file or directory) close(3)= 0 socket(PF_FILE, SOCK_STREAM, 0) = 3 fcntl64(3, F_SETFL, O_RDWR|O_NONBLOCK) = 0 connect(3, {sa_family=AF_FILE, path="/var/run/nscd/socket"}, 110) = -1 ENOENT (No such file or directory) close(3)= 0 open("/etc/nsswitch.conf", O_RDONLY)= 3 fstat64(3, {st_mode=S_IFREG|0644, st_size=513, ...}) = 0 mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb7f1e000 read(3, "# /etc/nsswitch.conf\n#\n# Example"..., 4096) = 513 read(3, "&quo
Bug#472986: /bin/su: su segfaults with libpam-p11 activated in /etc/pam.d/common-auth
Nicolas François wrote: Hello Jérôme, Do you have some news regarding http://bugs.debian.org/472986? Could you check your log at the time it appeared? Could you also test if the bug is fixed in the new version 1:4.1.1-1? No it's not fixed in 1:4.1.1-1. With SYSLOG_SU_ENAB set to yes and the SULOG_FILE defined, nothing gets written to the file : the segfault occurs before. When deactivating the pkcs11 stuff, I've checked that this file gets correctly written to when using su. /var/log/auth.log contains : --- CUT --- Apr 11 09:49:19 houlala pam_p11[17848]: fatal: pkcs11_sign failed Apr 11 09:49:19 houlala pam_p11[17848]: pam_authenticate: Authentication service cannot retrieve authentication info --- CUT --- I think pkcs11_sign fails probably because of the incorrect way my token was created. In fact I don't even expect this token to allow me to login, I'm just doing some testing... Anyway su should probably handle that failure more gracefully than by segfaulting. In kern.log I've got : --- CUT --- Apr 11 09:49:20 houlala kernel: su[17848]: segfault at b7f879c0 eip b7e970f3 esp bfb25738 error 4 --- CUT --- hth Jerome Alet
Bug#472986: /bin/su: su segfaults with libpam-p11 activated in /etc/pam.d/common-auth
Nicolas François wrote: Hello Jérôme, Do you have some news regarding http://bugs.debian.org/472986? Could you check your log at the time it appeared? Could you also test if the bug is fixed in the new version 1:4.1.1-1? Best Regards, Sorry, I didn't have the time to test this. I'll try to do it by the end of next week. bye Jerome
Bug#472986: /bin/su: su segfaults with libpam-p11 activated in /etc/pam.d/common-auth
Package: login Version: 1:4.1.0-2 Severity: important File: /bin/su When trying to activate libpam-p11 (v0.1.3-1) for login, I've modified /etc/pam.d/common-auth to contain : --- CUT --- authrequiredpam_p11_opensc.so /usr/lib/opensc-pkcs11.so #auth requiredpam_unix.so nullok_secure --- CUT --- Then when doing an su, there's a segfault : --- CUT --- [EMAIL PROTECTED]:~$ su su: Authentication service cannot retrieve authentication info Erreur de segmentation [EMAIL PROTECTED]:~$ --- CUT --- I can't login either but probably for other reasons. I'm using a Rainbow iKey3000 USB token with opensc and openct (stock Debian packages) and pkcs11-tool and pkcs15-tool both work fine. The segfault appears even if I copy ~jerome/.eid/authorized_certificates into ~root/.eid/authorized_certificates, although in this case the token's password is asked. hth Jerome Alet -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages login depends on: ii libc6 2.7-9 GNU C Library: Shared libraries ii libpam-modules0.99.7.1-6 Pluggable Authentication Modules f ii libpam-runtime0.99.7.1-6 Runtime support for the PAM librar ii libpam0g 0.99.7.1-6 Pluggable Authentication Modules l login recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#462058: [SPAM?] Bug#462058: Acknowledgement (python-django: problem when extracting PostgreSQL's version number)
Debian Bug Tracking System wrote: Thank you for the problem report you have sent regarding Debian. This is an automatically generated reply, to let you know your message has been received. It is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. The attached patch fixes the problem for me. hth Jerome Alet --- base.py 2007-10-26 21:21:35.0 +0200 +++ base.py.new 2008-01-22 09:27:17.995217070 +0100 @@ -54,7 +54,13 @@ global postgres_version if not postgres_version: cursor.execute("SELECT version()") -postgres_version = [int(val) for val in cursor.fetchone()[0].split()[1].split('.')] + postgres_version = [] + raw_version = cursor.fetchone()[0] + for c in raw_version : + if c.isdigit() : + postgres_version.append(int(c)) + elif c != "." : + break if settings.DEBUG: return util.CursorDebugWrapper(cursor, self) return cursor
Bug#462058: python-django: problem when extracting PostgreSQL's version number
Package: python-django Version: 0.96.1-1 Severity: grave Justification: renders package unusable When using postgresql-8.3 I've got the following version number : [EMAIL PROTECTED]:~$ psql --version psql (PostgreSQL) 8.3RC2 Now when trying to syncdb in Django : python manage.py syncdb Traceback (most recent call last): File "manage.py", line 11, in ? execute_manager(settings) File "/var/lib/python-support/python2.4/django/core/management.py", line 1672, in execute_manager execute_from_command_line(action_mapping, argv) File "/var/lib/python-support/python2.4/django/core/management.py", line 1571, in execute_from_command_line action_mapping[action](int(options.verbosity), options.interactive) File "/var/lib/python-support/python2.4/django/core/management.py", line 504, in syncdb cursor = connection.cursor() File "/var/lib/python-support/python2.4/django/db/backends/postgresql_psycopg2 /base.py", line 57, in cursor postgres_version = [int(val) for val in cursor.fetchone()[0].split()[1].split('.')] ValueError: invalid literal for int(): 3RC2 The exact same problem is present both in Django's db/backends/postgresql_psycopg2/ and db/backends/postgresql/ Should probably be reported upstream. hth Jerome -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.22-3-686 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages python-django depends on: ii python2.4.4-6An interactive high-level object-o ii python-support0.7.6 automated rebuilding support for p Versions of packages python-django recommends: pn python-pysqlite2 (no description available) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#455497: additional information
/usr/share/planner/sql/database.sql seems to be older than /usr/share/planner/sql/database-0.13.sql if you look at the file's contents, so which one is the correct one to use with planner 0.14.2 ? thx for your help Jerome Alet -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#445106: zope-ploneformgen: dependency missing
Package: zope-ploneformgen Version: 1.0.3-1 Severity: normal zope-ploneformgen should probably depend on zope-scriptablefields, it doesn't seem to be the case. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.18-4-686 (SMP w/4 CPU cores) Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash Versions of packages zope-ploneformgen depends on: ii zope-common 0.5.37 common settings and scripts for zo ii zope2.9 2.9.7-3Open Source Web Application Server zope-ploneformgen recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#427559: problems with your proposal of suid root backend runner
Martin, you suggest a suid root backend to launch other CUPS backends as root. This is not really possible as far as I know, for several reasons : - Your suid backend MUST be present in /usr/lib/cups/backend for CUPS to accept to launch it. (unless you modify CUPS heavily) - This suid wrapper would need to obey the backend arguments handling (man backend), and so would probably have to autodetect existing backends, the way PyKota, Tea4CUPS, or Jasmine do. As an alternative you could do as accsnmp does, (no autodetection) and rely to the end user to manually specify the Device URIs. So your suid wrapper would have to output, for example, a list of Device uris like : yourwrapper://cups-pdf:// for each backend in /usr/lib/cups/backend/ otherwise you wouldn't have any way to tell your wrapper which real backend to run (the number and value of a backend's arguments is fixed and defined in CUPS' documentation). - There's a 30 seconds timeout during the launch of a backend in autodetection mode. When a lot of backends exist in /usr/lib/cups/backend, this may not be sufficient to autodetect them all (let's say cupspykota://tea4cups://ipp:// and the like, and the other way around tea4cups://cupspykota://ipp// and for each backend). the easiest way was certainely to chown root.root mybackend chmod 700 mybackend as specified in CUPS' documentation. don't forget that many CUPS backends are written in scripting languages, and won't support being suid root. hoping this helps the discussion bye Jerome Alet -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#427559: CUPS 1.2.11 sucks
Hi people, As the main author of two of the software listed by Kurt, namely PyKota and Tea4CUPS, I think I'm allowed to add something to this thread. First some name calling : let me tell that you, Martin-Eric, clearly don't understand the problem. The way you answered to Kurt, there's no need for you to EVEN answer to me, I'll delete your eventual message immediately. You seem to be the exact portrait of what I thought a lot of Debian developers are : a complete elitist ass-hole. IMPORTANT (just in case) : I only use Debian on both my desktops and servers since 1999. And I know MOST of Debian developers are not like you, but unfortunately the most vocal ones are... What is the use of a bug reporting system if you are only allowed to use it to report bugs on the stable release ? Wouldn't it be more helpful to be able to report bugs (you may label them 'problems' instead) on the development release as well, so they don't impact too much people when they'll eventually upgrade their system to the future stable release and they'll learn but too late that it's entirely broken ? Now for the problem itself, which is the important part of my message : Personally I've noticed the problem when upgrading my development machine and immediately announced the problem and ways to mitigate it to all users of my own software : http://cgi.librelogiciel.com/pipermail/pykota/2007-June/004888.html http://cgi.librelogiciel.com/pipermail/tea4cups/2007-June/000129.html If I didn't upgrade my own laptop, I wouldn't have noticed and would have been stuck as to why my software wouldn't work on my clients machines ? All these people would have called me and expected quick answers. What did I, or all these people, do to you to merit wasting our time because of you ? The answer : nothing. You deliberately chose to break things without telling anyone beforehand. I used to recommend Debian to the people who use my software, and I'm now considering recomending an alternative which don't do things the opposite way upstream requests. I've also seen it the message displayed (or sent) when upgrading that cups-pdf was broken by the upgrade. So I think in a single shot you broke three of the most used CUPS backends in the world (from my own statistics which certainely suck, but anyway), without even trying to contact upstream about these software (I can't speak for cups-pdf author though). As you've probably noticed by now, you've also broken the way people EXPECT cups to run, since this is the way upstream expects it too... None of these software being proprietary, it would be reasonable for us to maybe, just maybe, expect some sort of cooperation from Debian packagers... As the author of several other software included in Debian, I can tell for sure that this non-cooperation with upstream problem is not specific to CUPS or the software which depends on it. BTW, before you try to play the "PyKota and Tea4CUPS are not really free so we don't care because..." game with me, read this before : http://www.mailarchives.org/list/debian-user/msg/2005/45012 In conclusion : you broke things, I noticed (almost) in time, workarounds exist for my own software, I should be happy. I'AM NOT ! bye Jerome Alet -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#398428: samba: when changing password with smbpasswd, the passdb.tdb file becomes rotten
Package: samba Version: smbpasswd breaks passwd.tdb Severity: critical Justification: breaks the whole system While trying to change my daughter's password from Windows 2K (Ctrl+Alt+Suppr) she lost her connection to the Samba server. I was able to connect as domain admin from the same box, but once disconnected I was unable to login again. >From the Samba server, I tried to change password again and I was told a problem about password database version problem. I restored yesterday's backup of passdb.tdb, verified all was fine, then changed password again with smbpasswd The file was rotten again. Upon starting nmbd refuses to open the file but the file is present. I restored the backup again, all is fine, but I won't touch smbpasswd again... bye Jerome Alet -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-686-smp Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) (ignored: LC_ALL set to [EMAIL PROTECTED]) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#391007: linux-image-2.6-686: ieee1394 problems width dvgrab
Package: linux-image-2.6-686 Version: 2.6.17+2 Severity: important When I went back from holidays, around mid-August, I grabbed my videos from my Panasonic NV-GS17 mini-DV camera with dvgrab with no problem at all, on my Dell Latitude D800 with a Pentium M 1.70 Ghz, 2Mb cache and 1 Gb of RAM. Now whenever I use dvgrab even for live capture, I've got hundreds of lines identical to the following one in the kernel logs : --- CUT --- ohci1394: gw-host0: Waking dma ctx=1 ... processing is probably too slow --- CUT --- The resulting files show fine in mplayer or videolan but are accelerated, making audio almost inaudible and people run instead of walk. Since August I ran several system upgrades, and I don't remember the kernel version which worked at that time. Following some instructions I found on the web I used hdparm to enable DMA, 32 bit I/O, Multiple sectors, and Interrupt unmask on my hard disk, and also set dma, interrupt_unmask and 32 bits I/O on the internal DVD burner. Still no luck. Any idea of what could be wrong ? TIA Jerome Alet -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages linux-image-2.6-686 depends on: ii linux-image-2.6.17-2-686 2.6.17-9 Linux 2.6.17 image on PPro/Celeron linux-image-2.6-686 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#388132: freej doesn't support image layers
Package: freej Version: 0.8.1-3+b1 Severity: grave Justification: renders package unusable freej can't be used at least with ImageLayer objects created from a .js file. The examples available from the upstream website, in particular pan.js with its picture 1steps063.jpg doesn't work at all. Talked today with upstream author Jaromil on IRC, who confirmed that the examples should work just fine. In the log below the error is at "ReferenceError: ImageLayer is not defined" This causes the script to abort without any explanation. Here's the session log : --- CUT --- [EMAIL PROTECTED]:~/freej$ freej -D 3 -n -j pan.js [*] starting FreeJ 0.8.1 engine [*] FreeJ version 0.8.1 RASTA SOFTWARE . (c)2001-2005 Jaromil & Kysucix @ dyne.org . -- . your screen does'nt support 32bpp . doing video surface software conversion . emulated surface geometry 400x300 32bpp [*] SDL Viewport is x11 400x300 32bpp [*] JavaScript parser initialized [F] VideoEncoder:_init::filename freej.ogg saved [F] Pipe::Pipe(16384) [F] OggTheoraEncoder::OggTheoraEncoder::OggTheoraEncoder object created [F] Finding best memory copy function [F] glibc memcpy() : time 10.80 [F] linux kernel memcpy() : time 24.03 [F] agp optimized memcpy() : time 10.53 [F] MMX optimized memcpy() : time 18446272519762.42 [F] MMXEXT optimized memcpy() : time 11.33 [F] SSE optimized memcpy() : time 13.32 [*] Using memory-to-memory copy method : agp optimized memcpy() [F] Plugger::_delete [*] loading available plugins [F] Opened plugin Water from /usr/lib/freej/water.so with handle 0x844f4e8 . plugged: Water filter v1 by jaromil [F] Opened plugin Vertigo from /usr/lib/freej/vertigo.so with handle 0x844f960 . plugged: Vertigo filter v1 by Fukuchi Kentarou [F] Opened plugin SquareTrans from /usr/lib/freej/squaretrans.so with handle 0x844fde8 . plugged: SquareTrans filter v2 by Clifford Smith [F] Opened plugin Simura from /usr/lib/freej/simura.so with handle 0x8450610 . plugged: Simura filter v1 by Fukuchi Kentarou [F] Opened plugin Rotozoom from /usr/lib/freej/rotozoom.so with handle 0x84509c8 . plugged: Rotozoom filter v1 by van Paassen, Ellacott [F] Opened plugin Ripple from /usr/lib/freej/ripple.so with handle 0x8450dc0 . plugged: Ripple filter v1 by Fukuchi Kentarou [F] Opened plugin RandTrans from /usr/lib/freej/randtrans.so with handle 0x8451240 . plugged: RandTrans filter v1 by Clifford Smith [F] Opened plugin QuadTrans from /usr/lib/freej/quadtrans.so with handle 0x84516c0 . plugged: QuadTrans filter v2 by jaromil [F] Opened plugin Nervous from /usr/lib/freej/nervous.so with handle 0x8451b40 . plugged: Nervous filter v1 by Edo Tannenbaum [F] Opened plugin Edge from /usr/lib/freej/edge.so with handle 0x8451fc0 . plugged: Edge filter v1 by Fukuchi Kentarou [F] Opened plugin Delaymap from /usr/lib/freej/delaygrab.so with handle 0x8452438 . plugged: Delaymap filter v2 by Andreas Schiffler [F] Opened plugin Cartoon from /usr/lib/freej/cartoon.so with handle 0x84528b8 . plugged: Cartoon filter v1 by Dries Pruimboom [F] Opened plugin Blur from /usr/lib/freej/blur.so with handle 0x8452d38 . plugged: Blur filter v1 by jaromil [F] Opened plugin Baltan from /usr/lib/freej/baltan.so with handle 0x84531b0 . plugged: Baltan filter v1 by Fukuchi Kentarou [F] Opened plugin BackLight from /usr/lib/freej/backlight.so with handle 0x8453630 . plugged: BackLight filter v1 by Pete Warden [F] JsParser reading from file pan.js [F] JsParser allocated 721 bytes [!] script error in pan.js: [!] ReferenceError: ImageLayer is not defined [!] execution of script aborted [M] allocated memory at 0xb7331008 sized 48 bytes [F] ImageLayer::close() [F] Layer :: run :: end thread -1222354000 [F] Plugger::_delete [M] freeing memory at address 0x844f7d8 [M] freeing memory at address 0x844fc58 [M] freeing memory at address 0x84500e8 [M] freeing memory at address 0x8450300 [M] freeing memory at address 0x8450c38 [M] freeing memory at address 0x84510b8 [M] freeing memory at address 0x8451538 [M] freeing memory at address 0x84519b8 [M] freeing memory at address 0x8451e38 [M] freeing memory at address 0x84522b0 [M] freeing memory at address 0x8452730 [M] freeing memory at address 0x8452bb0 [M] freeing memory at address 0x8453028 [M] freeing memory at address 0x84534a8 [M] freeing memory at address 0x8453928 [*] JsParser::close() [*] cu on http://freej.dyne.org [EMAIL PROTECTED]:~/freej$ --- CUT --- The application also segfaults from time to time, but this is probably not related since it also happens with js scripts which don't reference any ImageLayer. Thanks in advance for your time Jerome Alet -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-686-smp Locale:
Bug#388069: libfreetype6-dev: missing subdirectory in headers
Package: libfreetype6-dev Version: 2.2.1-5 Severity: critical Justification: breaks unrelated software The installed libfreetype6-dev files lack the freetype/internal/ subdirectory, making the compilation of other software which rely on it to be present (e.g. freej) impossible. Please fix this. bye Jerome Alet -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages libfreetype6-dev depends on: ii libc6-dev [libc-dev] 2.3.6.ds1-4 GNU C Library: Development Librari ii libfreetype6 2.2.1-5 FreeType 2 font engine, shared lib ii zlib1g-dev [libz-dev]1:1.2.3-13 compression library - development libfreetype6-dev recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#380848: Renaming jaxml to python-jaxml
Hi, On Tue, Aug 01, 2006 at 11:45:49PM +0200, Matej Vela wrote: > Pierre Habouzit <[EMAIL PROTECTED]> writes: > > > Le mar 1 août 2006 22:42, Matej Vela a écrit : > >[...] > >> Victor, as the maintainer of scanerrlog, would you like to adopt > >> jaxml? > >> > >> And QA folks: can we go ahead and remove jaxml immediately? If it's > >> adopted and renamed, it'll have to go through NEW anyway. > > > > I just did an upload that addressed that, and the package should hit NEW > > soon. > > Well, my gut feeling is that jaxml is dead upstream and not likely to > be adopted (I've never had much luck contacting Victor, cf. #305460, > #312834, #317408). I'll be glad to be proven wrong of course. Your feeling was incorrect. The fact that there's no new upstream release doesn't mean that the project is dead. Being the original author, I can confirm it is not. I'm just back from holidays and seeing a lot of debian messages about this software. I'm currently trying to read the 1500 messages which waited for me to be back, when this is done, if something has to be changed to jaxml I'll do it. bye Jerome Alet
Bug#367636: gnugk: random problem at boot time because of initscripts numbering
Package: gnugk Version: 2:2.2.3-2-2 Severity: important By default, the numbering for startup and shutdown scripts for gnugk and postgresql is the same, so the alphabetical order makes gnugk start before postgresql. If you use a PostgreSQL database from gnugk, you're stuck with gnugk which fails to start, since the database is not ready yet. If you start gnugk manually, once postgresql is ready, it's OK. Similarly, when shutting down, gnugk should be stopped before PostgreSQL and not after. I've seen this problem on these two software, but it probably exists with several other interdependant software. For example we know that gnugk can depend on postgresql being ready, but we know for sure that postgresql will never care to see if gnugk has to be ready before being able to start with no problem. More generally, database servers (Bind, MySQL, Slapd, PostgreSQL, etc...) should be started **before** any other service which can depend on them (e.g. Apache), and stopped **after** all services which can depend on them have been stopped. Or did I do something wrong ? Thx. Jerome Alet System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory ANSI_X3.4-1968) (ignored: LC_ALL set to [EMAIL PROTECTED]) Versions of packages gnugk depends on: ii adduser 3.85 Add and remove users and groups ii libc6 2.3.6-3GNU C Library: Shared libraries an ii libexpat1 1.95.8-3 XML parsing C library - runtime li ii libgcc1 1:4.0.3-1 GCC support library ii libldap2 2.1.30-13 OpenLDAP libraries ii libmysqlclient14 4.1.15-1 mysql database client library ii libopenh323-1.15.61.15.6-3 H.323 aka VoIP library ii libpq48.1.0-3PostgreSQL C client library ii libpt-1.8.7 1.8.7-2Portable Windows Library ii libsasl2 2.1.19-1.9 Authentication abstraction library ii libsdl1.2debian 1.2.9-4Simple DirectMedia Layer ii libssl0.9.8 0.9.8a-7 SSL shared libraries ii libstdc++64.0.3-1The GNU Standard C++ Library v3 ii zlib1g1:1.2.3-11 compression library - runtime gnugk recommends no packages. -- debconf information: perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LANGUAGE = (unset), LC_ALL = "[EMAIL PROTECTED]", LANG = "[EMAIL PROTECTED]" are supported and installed on your system. perl: warning: Falling back to the standard locale ("C"). locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#263417: was Re: Bug#263417: ITP: pysnmp -- Python implementation of SNMP v.1/v.2c engine
Hi there, FYI the latest development versions of PyKota now transparently support both PySNMP v3.4.x and v4.x I was made really easy thanks to the "oneliner" stuff Ilya added to 4.x : I mostly had to add only 30 lines of code. bye Jerome Alet -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#362431: xorg: missing modules
On Mon, Apr 17, 2006 at 06:50:39PM +0100, Joshua Kite wrote: > unnecessarily abrasive. I don't really understand what you mean by > saying that it's not working BECAUSE I have been trying to use the > Nvidia driver. I know that in the past, Debian did not support the > nvidia binary drivers and I can well understand this, since they have no > 'control' over them. It is important to mention that the problem we encountered has NOTHING o do with the NVidia driver, proprietary or not. My laptop uses the free ATI driver which comes bundled with the default X server included in Debian, and I experienced the very same problem. hth Jerome Alet -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#362431: xorg: missing modules
Hi, On Fri, Apr 14, 2006 at 11:59:13PM +0100, Joshua Kite wrote: > I have just done a dist-upgrade on i386 to attempt to > resolve this bug and it is certainly not fixed. even > after upgrading to xserver-xorg-core_1.0.2-4. I still > get the mesage re missing modules for bitmap and > pcidata although only bitmap was specified in > /etc/X11/xorg.conf. commenting out this line made no > difference. I tried copying /etc/X11/xorg.conf to my > Ubuntu AMD64 partition and X comes up although it > loads (but refuses to use) the Nvidia module (splash > screen appears and lsmod shows 'nvidia' present). When I got back to my laptop who showed the problem, I just commented out the ModulePath configuration line and the X server started flawlessly. So all I can say is that it worked for me. bye Jerome Alet -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#362431: xorg: missing modules
Hi gain, On Thu, Apr 13, 2006 at 02:59:11PM +0200, Michel Dänzer wrote: > On Thu, 2006-04-13 at 14:20 +0200, [EMAIL PROTECTED] wrote: > > Package: xorg > > Version: 1:7.0.10 > > Severity: grave > > Justification: renders package unusable > > > > > > The X server doesn't start complaining about bitmap and pcidata modules, > > despite none of these lines being present in the list of modules to > > load in /etc/X11/xorg.conf > > These modules are required and thus loaded automatically by the X > server. > > Most likely, you have a superfluous ModulePath line This is the case. > in /etc/X11/xorg.conf. If not, please post that file as well > as /var/log/Xorg.0.log. I'll test to remove the superfluous lines from the modulepath tomorrow when I'm in front of the machine again, then I'll post a followup to tell you what happened and I'll include these files if necessary. Thanks for your help ! bye, and thanks for your help Jerome Alet
Bug#362431: xorg: missing modules
Package: xorg Version: 1:7.0.10 Severity: grave Justification: renders package unusable The X server doesn't start complaining about bitmap and pcidata modules, despite none of these lines being present in the list of modules to load in /etc/X11/xorg.conf Any idea ? -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-grml Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages xorg depends on: ii libgl1-mesa-dri 6.4.1-0.4 A free implementation of the OpenG ii libgl1-mesa-glx [libgl1-mesa- 6.4.1-0.4 A free implementation of the OpenG ii libglu1-mesa 6.4.1-0.4 The OpenGL utility library (GLU) ii xbase-clients 1:7.0.0-2 miscellaneous X clients ii xfonts-100dpi 1:1.0.0-2 100 dpi fonts for X ii xfonts-75dpi 1:1.0.0-2 100 dpi fonts for X ii xfonts-base 1:1.0.0-3 standard fonts for X ii xfonts-scalable 1:1.0.0-3 scalable fonts for X ii xkb-data 0.8-4 X Keyboard Extension (XKB) configu ii xserver-xorg 1:7.0.10 the X.Org X server ii xterm 210-2 X terminal emulator ii xutils1:7.0.0-3 X Window System utility programs xorg recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#358691: never mind
Hi, I've just deleted python2.3-pam entirely and reinstalled it and I can't reproduce the problem anymore... Sorry for this. Jerome Alet -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#358691: more info
More info about this problem : in fact python-wxgtk is not involved at all because it's not used in this program. Sorry for the mistake. bye Jerome Alet -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#358691: python2.3-pam: double free causing program to crash
Package: python2.3-pam Version: 0.4.2-10.1 Severity: grave Justification: renders package unusable I'm currently developping a Python program which uses both python-wxgtk2.6 and python-pam If I make a very small program using only python-pam I can't reproduce the problem below, but with the complete program here's what I've got (no line seems to imply that python-wxgtk is the problem though) : Launched from gdb : --- CUT --- (gdb) file /usr/bin/python2.3 Reading symbols from /usr/bin/python2.3...(no debugging symbols found)...done. Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (gdb) set args /usr/bin/pknotify --checkauth --destination localhost:7654 --ask "Username:username:jerome" "Pass:password:kiki" (gdb) run Starting program: /usr/bin/python2.3 /usr/bin/pknotify --checkauth --destination localhost:7654 --ask "Username:username:jerome" "Pa ss:password:kiki" (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1210177856 (LWP 19502)] (no debugging symbols found) ... many similar lines (no debugging symbols found) *** glibc detected *** double free or corruption (fasttop): 0x08264d00 *** Program received signal SIGABRT, Aborted. [Switching to Thread -1210177856 (LWP 19502)] 0xe410 in __kernel_vsyscall () (gdb) bt #0 0xe410 in __kernel_vsyscall () #1 0xb7e0d6d1 in raise () from /lib/tls/i686/cmov/libc.so.6 #2 0xb7e0ef9b in abort () from /lib/tls/i686/cmov/libc.so.6 #3 0xb7e44127 in __fsetlocking () from /lib/tls/i686/cmov/libc.so.6 #4 0xb7e4a6f7 in malloc_usable_size () from /lib/tls/i686/cmov/libc.so.6 #5 0xb7e4ab92 in free () from /lib/tls/i686/cmov/libc.so.6 #6 0xb773902c in _unix_read_password () from /lib/security/pam_unix.so #7 0xb7734a90 in pam_sm_authenticate () from /lib/security/pam_unix.so #8 0xb791da9a in _pam_dispatch () from /lib/libpam.so.0 #9 0xb791fd9e in pam_authenticate () from /lib/libpam.so.0 #10 0xb7942856 in initPAM () from /usr/lib/python2.3/site-packages/PAMmodule.so #11 0x080b6ae3 in PyEval_GetFuncName () #12 0x080b6ff2 in PyEval_GetFuncName () #13 0x080b6ff2 in PyEval_GetFuncName () #14 0x080b7835 in PyEval_EvalCodeEx () #15 0x080b79a9 in PyEval_EvalCode () #16 0x080d7ef7 in PyRun_FileExFlags () #17 0x080d81b4 in PyRun_SimpleFileExFlags () #18 0x08054f87 in Py_Main () #19 0xb7df8eb0 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6 #20 0x080548e1 in _start () (gdb) --- CUT --- -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-686-smp Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) (ignored: LC_ALL set to [EMAIL PROTECTED]) Versions of packages python2.3-pam depends on: ii libc6 2.3.6-3GNU C Library: Shared libraries an ii libpam0g 0.79-3.1 Pluggable Authentication Modules l ii python2.3 2.3.5-9.1 An interactive high-level object-o python2.3-pam recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#353376: update
In fact the pre-filled answer was correctly sent back, but the error appeared in the web browser, so the problem probably happens after the reply has been sent. hth Jerome Alet -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#353376: after upgrade, otrs doesn't seem to work correctly
Package: otrs Version: 1.3.2p01-6 Severity: grave Justification: renders package unusable I decided to test OTRS after I did an apt-get dist-upgrade, and it seems to not work anymore when I click on a pre-filled answer to reply to a ticket (which was created successfully and notified correctly). Here's the error I've got in the browser : Can't locate object method "EncodeOutput" via package "Kernel::System::Encode" at /usr/share/otrs/bin/cgi-bin/../../Kernel/System/Ticket/ArticleStorageDB.pm line 188. Hoping this helps bye Jerome Alet -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.4.27-2-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) (ignored: LC_ALL set to [EMAIL PROTECTED]) Versions of packages otrs depends on: ii apache1.3.33-6sarge1 versatile, high-performance HTTP s ii libauthen-sasl-perl 2.08-2 Authen::SASL - SASL Authentication ii libdate-pcalc-perl1.2-2 Perl module for Gregorian calendar ii libdbi-perl 1.48-1 Perl5 database interface by Tim Bu ii libemail-valid-perl 0.15-2 Check validity of Internet email a ii libio-stringy-perl2.110-1Perl5 modules for IO from scalars ii libmailtools-perl 1.62-1 Manipulate email in perl programs ii libmime-perl 5.417-1Perl5 modules for MIME-compliant m ii perl 5.8.4-8sarge3 Larry Wall's Practical Extraction -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#350553: gs-esp extremely slow in Sid compared to Sarge
Package: gs-esp Version: 8.15.1.dfsg.1-1 Severity: important When doing exactly the same action, gs-esp 8.15 included in Sid is more than ten times slower than gs-esp 7.07 included in Sarge : $ cd /tmp $ wget http://cortex.unice.fr/~jerome/d00195-001.ps $ cat d00195-001.ps | /usr/bin/gs-esp -sDEVICE=bbox -dPARANOIDSAFER -dNOPAUSE \ -dBATCH -dQUIET - Any idea ? -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.14-2-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages gs-esp depends on: ii gs-common 0.3.9 Common files for different Ghostsc ii libc6 2.3.5-12 GNU C Library: Shared libraries an ii libcupsimage2 1.1.23-15 Common UNIX Printing System(tm) - ii libcupsys21.1.23-15 Common UNIX Printing System(tm) - ii libice6 6.9.0.dfsg.1-4 Inter-Client Exchange library ii libjpeg62 6b-11 The Independent JPEG Group's JPEG ii libpaper1 1.1.14-5 Library for handling paper charact ii libpng12-01.2.8rel-5 PNG library - runtime ii libsm66.9.0.dfsg.1-4 X Window System Session Management ii libstdc++64.0.2-8The GNU Standard C++ Library v3 ii libtiff4 3.8.0-1Tag Image File Format (TIFF) libra ii libx11-6 6.9.0.dfsg.1-4 X Window System protocol client li ii libxext6 6.9.0.dfsg.1-4 X Window System miscellaneous exte ii libxt66.9.0.dfsg.1-4 X Toolkit Intrinsics ii xlibs 6.9.0.dfsg.1-4 X Window System client libraries m ii zlib1g1:1.2.3-9 compression library - runtime Versions of packages gs-esp recommends: ii gsfonts 8.14+v8.11+urw-0.2 Fonts for the Ghostscript interpre ii psfontmgr 0.11.8-0.1 PostScript font manager -- part of -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#337433: Intention to NMU zope-zshell
On Fri, Jan 20, 2006 at 04:49:38PM +0100, Luk Claes wrote: > > Attached the patch for the version I intend to upload. Please respond if > you don't want this NMU to happen, if you are working yourself on a > patch or if you think that the attached patch won't work. I've personally NOT tested ZShell with any release of Zope > 2.5. I think that at least some commands of it work, but I don't guarantee this with Zope 2.7 and above. Use at your own risk (worst case it will not work, but you won't lose any data) bye Jerome Alet signature.asc Description: Digital signature
Bug#327212: [Pkg-nagios-devel] Bug#327212: nagios-common: locale problem breaks ping plugin
Hi again, On Thu, Sep 08, 2005 at 10:55:17AM -0400, sean finney wrote: > > so LC_ALL trumps all other settings, then the individual settings like > LC_NUMERIC etc, then LANG. i don't know much about how the default > locale is set up for debian boxes when you use a different locale... are > both environemnt variables LC_ALL and LANG set to the same value, or is > only LC_ALL set? > > if they're both set then simply unsetting LC_ALL before setting LC_NUMERIC > etc would work afaict. otherwise we'd have to do something like fetch > LC_ALL, unset it, set LC_NUMERIC etc, and then put the original value > of LC_ALL into LANG. On **MY** system, the /etc/environment file contains the setting of both LANG and LC_ALL to identical values. However, I don't remember if I did this myself, or if some system tool or library setup did it for me, so I don't know how it is on a "clean" Debian box. Also I don't know exactly if or when this file is used. bye Jerome Alet signature.asc Description: Digital signature
Bug#327212: [Pkg-nagios-devel] Bug#327212: nagios-common: locale problem breaks ping plugin
Hi again, On Thu, Sep 08, 2005 at 10:21:58AM -0400, sean finney wrote: > > On Thu, Sep 08, 2005 at 03:50:49PM +0200, [EMAIL PROTECTED] wrote: > > --- CUT --- > > servmediup:~# printenv |grep LC_ > > [EMAIL PROTECTED] > > servmediup:~# /usr/lib/nagios/plugins/check_ping -H 134.59.53.14 -w 10,15% > > -c 15,20% > > /bin/ping -n -U -w 10 -c 5 134.59.53.14 > > CRITIQUE - Impossible d'interpréter le réponse de la commande ping > > servmediup:~# export LC_NUMERIC=POSIX > > servmediup:~# /usr/lib/nagios/plugins/check_ping -H 134.59.53.14 -w 10,15% > > -c 15,20% > > /bin/ping -n -U -w 10 -c 5 134.59.53.14 > > CRITIQUE - Impossible d'interpréter le réponse de la commande ping > > servmediup:~# export LC_ALL=POSIX > > servmediup:~# /usr/lib/nagios/plugins/check_ping -H 134.59.53.14 -w 10,15% > > -c 15,20% > > PING OK - Packet loss = 0%, RTA = 0.29 ms > > servmediup:~# > > --- CUT --- > > okay, looks like it's LC_TIME that's doing it. try > > export LC_NUMERIC > export LC_TIME > LC_NUMERIC=POSIX > LC_TIME=POSIX > /usr/lib/nagios/plugins/check_ping -H 134.59.53.14 -w 10,15% -c 15,20% doesn't work. > je pense que oui--je voudrais bien savoir ci ça marche :) cela ne marche pas :-) en fait, LC_NUMERIC seems to be sufficient, as long as LC_ALL is unset. If I do : $ export LC_NUMERIC=POSIX $ /usr/lib/nagios/plugins/check_ping -H 134.59.53.14 -w 10,15% -c 15,20% it fails. but then : $ unset LC_ALL (here LC_NUMERIC is still defined to be POSIX since we're in the same session) $ /usr/lib/nagios/plugins/check_ping -H 134.59.53.14 -w 10,15% -c 15,20% it works hth Jerome Alet signature.asc Description: Digital signature
Bug#327212: [Pkg-nagios-devel] Bug#327212: nagios-common: locale problem breaks ping plugin
Hi again, On Thu, Sep 08, 2005 at 09:40:03AM -0400, sean finney wrote: > > Justification: renders package unusable > > i'm readjusting the severity of this, as the nagios is still quite > installable for everyone and useable for most people. i'm also > pondering reassigning it to nagios-plugins, as i believe it is > specific plugins failing and not the nagios subsystem, but i'll > hold off on that until we get all the information necessary. OK. > > It seems that Nagios can't parse the output of some plugins when > > the decimal point is ',' instead of '.', that's probably why > > /etc/init.d/nagios contains LC_NUMERIC=POSIX. > > hmm.. strange. i would think that exporting the above would be all > that we needed, i guess not. can you give me a specific example? > > > However, this doesn't seem to be sufficient if the system has > > started in a non-default locale. > > > > By modifying /etc/init.d/nagios and setting : > > > > export LC_ALL=POSIX > > it'd be nice if there were some medium ground where non-relevant > locale settings could remain at what they were, so error messages etc > could remain in the right locale. > > really, i'm suspecting the real fix should be in the individual plugins > (which i've actually fixed upstream in later versions), but i'll need > to see an example before i can be sure of that. I too think the fix should be done once and for all in the plugins, however the LC_ALL solution fixed the problem for me. Here's what I've got : --- CUT --- servmediup:~# printenv |grep LC_ [EMAIL PROTECTED] servmediup:~# /usr/lib/nagios/plugins/check_ping -H 134.59.53.14 -w 10,15% -c 15,20% /bin/ping -n -U -w 10 -c 5 134.59.53.14 CRITIQUE - Impossible d'interpréter le réponse de la commande ping servmediup:~# export LC_NUMERIC=POSIX servmediup:~# /usr/lib/nagios/plugins/check_ping -H 134.59.53.14 -w 10,15% -c 15,20% /bin/ping -n -U -w 10 -c 5 134.59.53.14 CRITIQUE - Impossible d'interpréter le réponse de la commande ping servmediup:~# export LC_ALL=POSIX servmediup:~# /usr/lib/nagios/plugins/check_ping -H 134.59.53.14 -w 10,15% -c 15,20% PING OK - Packet loss = 0%, RTA = 0.29 ms servmediup:~# --- CUT --- the lines beginning with "CRITIQUE" are the error message translated into French. I guess the original is something like : "CRITICAL - Impossible to parse the answer of the ping command" hoping this helps bye Jerome Alet signature.asc Description: Digital signature
Bug#327212: nagios-common: locale problem breaks ping plugin
Package: nagios-common Version: 2:1.3-cvs.20050402-2.sarge.1 Severity: grave Justification: renders package unusable It seems that Nagios can't parse the output of some plugins when the decimal point is ',' instead of '.', that's probably why /etc/init.d/nagios contains LC_NUMERIC=POSIX. However, this doesn't seem to be sufficient if the system has started in a non-default locale. By modifying /etc/init.d/nagios and setting : export LC_ALL=POSIX it seems to work fine. hoping this helps. bye Jerome Alet -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.4.27-2-686-smp Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to POSIX) Versions of packages nagios-common depends on: ii adduser 3.63 Add and remove users and groups ii apache [htt 1.3.33-6 versatile, high-performance HTTP s ii coreutils [ 5.2.1-2 The GNU core utilities ii debconf [de 1.4.30.13Debian configuration management sy ii fileutils 5.2.1-2 The GNU file management utilities ii mailx 1:8.1.2-0.20040524cvs-4 A simple mail user agent ii nagios-pgsq 2:1.3-cvs.20050402-2.sarge.1 A host/service/network monitoring ii nagios-plug 1.4-6Plugins for the nagios network mon -- debconf information: nagios/adminpassword: (password omitted) nagios/wwwsuid: true nagios/upgradefromnetsaint: * nagios/configapache: None -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#311469: otrs: database queries escaping problem
Package: otrs Version: 1.3.2p01-5 Severity: important Hello, When creating FAQ entries, it seems that the text entered, especially in the title of the FAQ entry, is not escaped correctly before being saved into the database. This makes the saving of some newly created FAQ entries impossible : Consider these two FAQ entries' titles : How can I read the mailing list's archives ? How can I tell if my setup is correct ? The first title will cause the saving to fail, while the second one will work perfectly. NB : It seems to be a combination of ' and ? Also if I enter such a title : Why do I have "File not found" ? This time the part between double quotes is not saved at all, but the rest of the entry is saved correctly. hth Jerome Alet -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.4.27-2-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) (ignored: LC_ALL set to [EMAIL PROTECTED]) Versions of packages otrs depends on: ii apache1.3.33-6 versatile, high-performance HTTP s ii libauthen-sasl-perl 2.08-2 Authen::SASL - SASL Authentication ii libdate-pcalc-perl1.2-2 Perl module for Gregorian calendar ii libdbi-perl 1.46-6 Perl5 database interface by Tim Bu ii libemail-valid-perl 0.15-1 Check validity of Internet email a ii libio-stringy-perl2.110-1Perl5 modules for IO from scalars ii libmailtools-perl 1.62-1 Manipulate email in perl programs ii libmime-perl 5.417-1Perl5 modules for MIME-compliant m ii perl 5.8.4-8Larry Wall's Practical Extraction -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#305807: zope2.7: KeyError in ZRDB.DA
Package: zope2.7 Version: 2.7.5-1 Severity: normal There's a bug which occurs when BOTH of the following conditions are met : - Create a ZSQL method of the SELECT type, with NO ARGUMENT. e.g. : SELECT * FROM mytable; - Have an SQL database (I use PostgreSQL) in which THERE ARE SOME DATAS which match the SQL SELECT query defined above. - Click on the Test tab for the ZSQL query, then on the submit button. The error is in the result rendering code, around line 337 of Shared/DC/ZRDB/DA.py Traceback : Traceback (innermost last): Module ZPublisher.Publish, line 101, in publish Module ZPublisher.mapply, line 88, in mapply Module ZPublisher.Publish, line 39, in call_object Module Shared.DC.ZRDB.DA, line 337, in manage_test Module DocumentTemplate.DT_String, line 474, in __call__ Module DocumentTemplate.DT_In, line 602, in renderwb Module DocumentTemplate.DT_Var, line 219, in render KeyError: 'query' The error seems to occur because the query has no parameter (argument) defined, then the rendering doesn't find the 'query' field. The error doesn't occur if there's no data which match the SELECT query, for example with an empty table it works fine. I wasn't able to exactly understand where to add an hidden and empty 'query' field to the rendered template to quickly fix the problem, so I can't send a patch. Sorry. hoping this helps bye Jerome Alet -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.4.27-2-686-smp Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages zope2.7 depends on: ii adduser 3.63 Add and remove users and groups ii debconf 1.4.48 Debian configuration management sy ii dpkg1.10.27 Package maintenance system for Deb ii libc6 2.3.2.ds1-21 GNU C Library: Shared libraries an ii python2.3 2.3.5-2 An interactive high-level object-o ii python2.3-xml 0.8.4-1 XML tools for Python (2.3.x) -- debconf information: zope/upgrade/2.7: * zope/tips/2.7: * zope/tips/standalone_install: zope/instance_home/move: true * shared/zope/restart: end -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#296478: exim: incomplete initialization of groups when running commands in system_aliases
On Tue, Feb 22, 2005 at 08:30:59PM +0100, Andreas Metzler wrote: > > but only the primary group for this user is initialized, not the > > additionnal groups this user is a member of. > [...] > > This is deliberate, documented and configurable. Ooops !!! I'm sorry. I think you can close this... Jerome Alet -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#296478: exim: incomplete initialization of groups when running commands in system_aliases
Package: exim Version: 3.36-13 Severity: important Hi, this problem MAY be a voluntary decision of the exim coders, I don't know, but anyway it's disturbing : if you define an alias in /etc/aliases like for example myalias: "|/usr/bin/somecommand" then run newaliases, every time you send an email to 'myalias', the email message you sent is piped into /usr/bin/somecommand somecommand is run as the user defined in the 'system_aliases' directive in exim.conf but only the primary group for this user is initialized, not the additionnal groups this user is a member of. maybe a setgroups() function call is missing somewhere in the code, or something like that. you can verify this easily, just define such an alias : myalias: "|/usr/bin/id -Gn" the error message you'll receive (normal) will anyway list only the primary group of the user the command is run as, instead of all the gorups this user is a member of, as can be seen by launching the same command from the shell (as the very same user) hoping this helps bye Jerome Alet -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.4.27-2-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) (ignored: LC_ALL set to [EMAIL PROTECTED]) Versions of packages exim depends on: ii cron3.0pl1-87management of regular background p ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an ii libdb3 3.2.9-22 Berkeley v3 Database Libraries [ru ii libident0.22-2.2 simple RFC1413 client library - ru ii libldap22.1.30-3 OpenLDAP libraries ii libpam0g0.76-22 Pluggable Authentication Modules l ii libpcre35.0-1Perl 5 Compatible Regular Expressi -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#285761: galeon: Galeon eats memory
Hi, On Fri, Jan 14, 2005 at 11:18:10AM +0100, Loïc Minier wrote: > Hi, > > Jerome Alet <[EMAIL PROTECTED]> - Wed, Dec 15, 2004: > > > very often, galeon eats most if not all of the available memory causing > > the system to swap > > Does it happen in 1.3.18-2? not sure yet let me check for a few days. > Did it happen with previous versions? definitely yes > Is it happening on certain pages/URL? not sure, as far as I've noticed it appears randomly > Do you have the problem with the Mozilla browser as well? Or maybe > with other apps (it might be a problem with your X drivers for > example)? I don't use mozilla, but I haven't noticed the problem with other apps > Could you paste the output of the following command in this bug report: > ps -C x-www-browser -o pid,size,sz,rss,vsize,pmem here it is (but currently galeon IS NOT eating my memory so not sure this will help). I'm currently viewing the #285761 bug report with no other tab opened : PID SZ SZ RSS VSZ %MEM 244959172 24926 32140 99704 14.3 bye Jerome Alet