Bug#448215: has the transition to playbin2 been done?
In other words, is this still an issue? Martin-Éric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#448215: has the transition to playbin2 been done?
2009/6/15 Sebastian Dröge sl...@circular-chaos.org: Version: 2.27.1-1 Am Montag, den 15.06.2009, 12:50 +0300 schrieb Martin-Éric Racine: In other words, is this still an issue? In 2.27 in experimental: no :) Then please re-open this bug and add a proper Close statement with this bug number in the Debian changelog for your next upload, so that we can track with which upload this was fixed. Thanks! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#487546: [Build-common-hackers] Bug#487546: cdbs: class/langcore.mk should set CC=gcc if CC is not set
On Sun, Jun 14, 2009 at 1:58 PM, Peter Eisentrautpete...@gmx.net wrote: On Sunday 22 June 2008 18:11:39 Martin-Éric Racine wrote: class/langcore.mk sets -g -Wall -O2 without checking whether CC can actualy process these options. For instance, -g produces output that is partially GDB-specific. On most GNU software, autotools perform these check for us and set CC=gcc autogamically. On other software, CC is often left unset. This is mostly okay on a Debian system, because the presumption is that CC=gcc, but we can never be sure of what parallel compilers, etc. someone might run, so it would be desirable for class/langcore.mk to set CC=gcc is it is unset. Do you have a concrete counterexample where the current code does not work? In the case where an upstream tarball comes with a single C file and no Makefile, the only option a maintainer has is to create a manual build target in debian/rules to compile the binary and to include class/langcore.mk to always use the standard Debian build options. However, class/langcore.mk includes GNU-specific options without checking that the compiler supports them (or at least setting CC=gcc to ensure that it does), so the build is not guaranteed to succeed. -- Martin-Éric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#533186: [Pkg-cups-devel] Bug#533186: #533186: cups: Cups not recognising/liking file formats
On Wed, Jun 17, 2009 at 2:29 PM, Christian Hammersc...@lathspell.de wrote: Hello I experienced the same problem and in mine case, too, installing ghostscript-cups and restarting CUPS solved the problem. Please adjust the dependencies! This package already is in Recommends. Is there any compelling reason to promote it to Depends? Martin-Éric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#533186: [Pkg-cups-devel] Bug#533186: #533186: cups: Cups not recognising/liking file formats
On Wed, Jun 17, 2009 at 4:06 PM, Christian Hammersc...@lathspell.de wrote: Am Wed, 17 Jun 2009 14:48:10 +0300 schrieb Martin-Éric Racine q-f...@iki.fi: On Wed, Jun 17, 2009 at 2:29 PM, Christian Hammersc...@lathspell.de wrote: Hello I experienced the same problem and in mine case, too, installing ghostscript-cups and restarting CUPS solved the problem. Please adjust the dependencies! This package already is in Recommends. Is there any compelling reason to promote it to Depends? I could neither print text files with a2ps, documents with OpenOffice nor web pages using Firefox! So this was a real show stopper. My guess is that most apps convert their sources to postscript before sending it to CUPS which would justify a dependency to whatever CUPS needs to be able to print postscript. Actually, as recently pointed out by Till Kamppeter, all Free Software applications are in the process of converting to producing PDF (which is a superset of Postscript) as the default output format. Martin-Éric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#533186: [Pkg-cups-devel] Bug#533186: Bug not fixed, sorry
2009/6/18 Josselin Mouette j...@debian.org: Sorry, but cups depends on ghostscript-cups since it cannot work without it. AFAIK only certain printers depend on ghostscript-cups. Till can correct me if I'm wrong. However, if we indeed depend upon ghostscript-cups because it was split from the main ghostscript package (a bad idea, IMHO), then we'll need to upgrade the Depends and Recommends of both ghostscript-cups and cups. Martin-Éric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#533186: [Pkg-cups-devel] Bug#533186: Bug not fixed, sorry
2009/6/18 Jonas Smedegaard d...@jones.dk: As I see it, this bug is real: It is fixed by either cups depending on ghostscript-cups instead of recommending it (a bad idea IMO) or cups announcing in NEWS file that it now recommends ghostscript-cups and existing installations should strongly consider following that recommendation. As pointed out by Martin Pitt earlier in this bug's thread, APT and Aptitude both pull Recommends in by default so, unless someone explicitly disabled this feature, they will have all the dependencies they need. Martin-Éric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#525822: missing an explicit Depends: ghostscript-cups
The bug is caused by the recent splitting of CUPS-specific components from the ghostscript package. To fix it, splix must explicitly depend upon ghostscript-cups. -- Martin-Éric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#533186: [Pkg-cups-devel] Bug#533186: Bug not fixed, sorry
On Thu, Jun 18, 2009 at 9:30 PM, Till Kamppetertill.kamppe...@gmail.com wrote: Then the bug here is that these dependencies in the driver packages are missing. So assign this bug to splix, gutenprint, hplip, and lsb (and any other CUPS Raster driver package coming with Debian). As it transpired during the discussion of this bug, packages (splix, gutenprint, hplip, lsb) that need CUPS-specific components of Ghostscript must be upgraded to explicitly depend upon the new ghostscript-cups package. Can you please implement this in your next upload and refer to bug #533186 for the rationale, in your changelog? Thanks! Martin-Éric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#487546: [Build-common-hackers] Bug#487546: cdbs: class/langcore.mk should set CC=gcc if CC is not set
2009/6/17 Martin-Éric Racine q-f...@iki.fi: In the case where an upstream tarball comes with a single C file and no Makefile, the only option a maintainer has is to create a manual build target in debian/rules to compile the binary and to include class/langcore.mk to always use the standard Debian build options. PS: this is precisely what I've had to do for CUPS-PDF in Debian, that is, create a compile line in debian/rules and, because langcore.mk doesn't set CC if it's empty, manually specific CC=gcc in debian/rules as a kludge. -- Martin-Éric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#487546: [Build-common-hackers] Bug#487546: Bug#487546: cdbs: class/langcore.mk should set CC=gcc if CC is not set
On Sun, Jun 21, 2009 at 4:57 PM, Peter Eisentrautpet...@debian.org wrote: On Sunday 21 June 2009 13:57:05 Martin-Éric Racine wrote: PS: this is precisely what I've had to do for CUPS-PDF in Debian, that is, create a compile line in debian/rules and, because langcore.mk doesn't set CC if it's empty, manually specific CC=gcc in debian/rules as a kludge. There is still something unusual going on in your environment that you are not telling us about. GNU make sets CC = cc implicitly. Does that not happen for you? Or do you have a non-GCC compiler installed? Setting CC=cc is entirely the wrong thing to do when passing -g as a compiler option. If you pass -g, then you also need to specific CC=gcc. -- Martin-Éric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#487546: [Build-common-hackers] Bug#487546: Bug#487546: Bug#487546: cdbs: class/langcore.mk should set CC=gcc if CC is not set
On Sun, Jun 21, 2009 at 5:19 PM, Peter Eisentrautpet...@debian.org wrote: On Sunday 21 June 2009 17:02:43 Martin-Éric Racine wrote: On Sun, Jun 21, 2009 at 4:57 PM, Peter Eisentrautpet...@debian.org wrote: On Sunday 21 June 2009 13:57:05 Martin-Éric Racine wrote: PS: this is precisely what I've had to do for CUPS-PDF in Debian, that is, create a compile line in debian/rules and, because langcore.mk doesn't set CC if it's empty, manually specific CC=gcc in debian/rules as a kludge. There is still something unusual going on in your environment that you are not telling us about. GNU make sets CC = cc implicitly. Does that not happen for you? Or do you have a non-GCC compiler installed? Setting CC=cc is entirely the wrong thing to do when passing -g as a compiler option. If you pass -g, then you also need to specific CC=gcc. Why? Because -g produces GDB-specific output, which is not available on non-GNU compilers. -- Martin-Éric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#510882: more details needed (about CUPS and LPRng)
2009/6/29 Steve Kostecke st...@debian.org: Martin-Éric Racine said: Why are you running LPRng along with CUPS on the same host? I've been using LPRng for over a decade on both our home and office LANs (including for printing between LANs across a VPN). Over 99% of our printing is via lpr and, due to the volume of print jobs, we have the print job banner pages disabled. It is not possible to disable these banner pages in CUPS. Yes, it is. I don't have banners here at all. Check the printer configuration options. Couple this with the fact that the lpr interface is deprecated by CUPS, It remains available for those who absolutely need lpr, but it's been packaged separately. and with the fact that CUPS actually degrades the print quality of jobs sent to my laser printer, I don't see myself switching entirely to CUPS. A more proactive action would be to file bug reports against the PPD provided with CUPS or Guttenprint for your particular printer. Martin-Éric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#510882: more details needed (about CUPS and LPRng)
On Mon, Jun 29, 2009 at 5:01 PM, Steve Kosteckest...@debian.org wrote: =?UTF-8?Q?Martin=2D=C3=89ric_Racine?= said: 2009/6/29 Steve Kostecke st...@debian.org: Over 99% of our printing is via lpr and, due to the volume of print jobs, we have the print job banner pages disabled. It is not possible to disable these banner pages in CUPS. Yes, it is. I don't have banners here at all. Check the printer configuration options. I _tried_ them. They don't work for me. Then file a bug against CUPS on _that_ particular issue. Martin-Éric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#552389: [Pkg-cups-devel] Bug#552389: cups-pdf: wrong check for 'removing' in postinst script
On Sun, Oct 25, 2009 at 11:50 PM, Eugene V. Lyubimkin jac...@debian.org wrote: Package: cups-pdf Severity: normal From the postinst script: -8- case $1 in configure|removing) -8- Postinst script never get 'removing' as the first argument. From http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html * deconfigured's-postinst abort-deconfigure in-favour failed-install-package version [removing conflicting-package version] 'removing' very much appears there. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#552389: [Pkg-cups-devel] Bug#552389: cups-pdf: wrong check for 'removing' in postinst script
On Mon, Oct 26, 2009 at 10:55 AM, Eugene V. Lyubimkin jac...@debian.org wrote: Martin-Éric Racine wrote: On Sun, Oct 25, 2009 at 11:50 PM, Eugene V. Lyubimkin jac...@debian.org wrote: Package: cups-pdf Severity: normal From the postinst script: -8- case $1 in configure|removing) -8- Postinst script never get 'removing' as the first argument. From http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html * deconfigured's-postinst abort-deconfigure in-favour failed-install-package version [removing conflicting-package version] 'removing' very much appears there. As sixth parameter, so 'case $1' will never match it. Ah, right. Fix pending. They really need to rewrite that section of Policy as an HTML table, showing all the parameters in the right order. The current bulleted list is a PITA to read. :) Martin-Éric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#552578: udev: root partition's UUID not detected
Package: udev Version: 146-5 Severity: important Since about one week, the UUID of the root partition is no longer detected. What we currently see: lrwxrwxrwx 1 root root 10 27.10. 18:56 c9deacb1-177c-454b-a3c0-7398524a8579 - ../../hda5 lrwxrwxrwx 1 root root 10 27.10. 18:56 ffa66b5a-8c8d-40cd-8c8f-aa069ab3d13d - ../../hda6 What we expected: lrwxrwxrwx 1 root root 10 27.10. 18:48 1b48f72f-d146-427b-9e15-9a04b51a57f0 - ../../hda1 lrwxrwxrwx 1 root root 10 27.10. 18:48 c9deacb1-177c-454b-a3c0-7398524a8579 - ../../hda5 lrwxrwxrwx 1 root root 10 27.10. 18:48 ffa66b5a-8c8d-40cd-8c8f-aa069ab3d13d - ../../hda6 -- Package-specific info: -- /etc/udev/rules.d/: /etc/udev/rules.d/: total 40 -rw-r--r-- 1 root root 443 Oct 27 18:16 70-persistent-net.rules -rw-r--r-- 1 root root 25245 Jun 24 12:26 usb_modeswitch.rules -rw-r--r-- 1 root root 7117 Apr 12 2009 z60_xserver-xorg-input-wacom.rules -- /sys/: /sys/dev /sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1/event1/dev /sys/devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input3/event3/dev /sys/devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input2/event2/dev /sys/devices/pci:00/:00:07.1/ide0/0.0/block/hda/dev /sys/devices/pci:00/:00:07.1/ide0/0.0/block/hda/hda1/dev /sys/devices/pci:00/:00:07.1/ide0/0.0/block/hda/hda2/dev /sys/devices/pci:00/:00:07.1/ide0/0.0/block/hda/hda5/dev /sys/devices/pci:00/:00:07.1/ide0/0.0/block/hda/hda6/dev /sys/devices/pci:00/:00:07.2/usb1/1-0:1.0/usb_endpoint/usbdev1.1_ep81/dev /sys/devices/pci:00/:00:07.2/usb1/dev /sys/devices/pci:00/:00:07.2/usb1/usb_device/usbdev1.1/dev /sys/devices/pci:00/:00:07.2/usb1/usb_endpoint/usbdev1.1_ep00/dev /sys/devices/pci:00/:00:0b.0/sound/card0/controlC0/dev /sys/devices/pci:00/:00:0b.0/sound/card0/dmfm/dev /sys/devices/pci:00/:00:0b.0/sound/card0/dmmidi/dev /sys/devices/pci:00/:00:0b.0/sound/card0/hwC0D0/dev /sys/devices/pci:00/:00:0b.0/sound/card0/midi/dev /sys/devices/pci:00/:00:0b.0/sound/card0/midiC0D0/dev /sys/devices/pci:00/:00:0b.0/sound/card0/pcmC0D0c/dev /sys/devices/pci:00/:00:0b.0/sound/card0/pcmC0D0p/dev /sys/devices/platform/floppy.0/block/fd0/dev /sys/devices/platform/i8042/serio0/input/input0/event0/dev /sys/devices/platform/i8042/serio1/input/input4/event4/dev /sys/devices/platform/i8042/serio1/input/input4/mouse0/dev /sys/devices/platform/serial8250/tty/ttyS1/dev /sys/devices/platform/serial8250/tty/ttyS2/dev /sys/devices/platform/serial8250/tty/ttyS3/dev /sys/devices/platform/vesafb.0/graphics/fb0/dev /sys/devices/pnp0/00:02/rtc/rtc0/dev /sys/devices/pnp0/00:08/tty/ttyS0/dev /sys/devices/virtual/block/ram0/dev /sys/devices/virtual/block/ram1/dev /sys/devices/virtual/block/ram10/dev /sys/devices/virtual/block/ram11/dev /sys/devices/virtual/block/ram12/dev /sys/devices/virtual/block/ram13/dev /sys/devices/virtual/block/ram14/dev /sys/devices/virtual/block/ram15/dev /sys/devices/virtual/block/ram2/dev /sys/devices/virtual/block/ram3/dev /sys/devices/virtual/block/ram4/dev /sys/devices/virtual/block/ram5/dev /sys/devices/virtual/block/ram6/dev /sys/devices/virtual/block/ram7/dev /sys/devices/virtual/block/ram8/dev /sys/devices/virtual/block/ram9/dev /sys/devices/virtual/input/mice/dev /sys/devices/virtual/mem/full/dev /sys/devices/virtual/mem/kmem/dev /sys/devices/virtual/mem/kmsg/dev /sys/devices/virtual/mem/mem/dev /sys/devices/virtual/mem/null/dev /sys/devices/virtual/mem/port/dev /sys/devices/virtual/mem/random/dev /sys/devices/virtual/mem/urandom/dev /sys/devices/virtual/mem/zero/dev /sys/devices/virtual/misc/cpu_dma_latency/dev /sys/devices/virtual/misc/hpet/dev /sys/devices/virtual/misc/network_latency/dev /sys/devices/virtual/misc/network_throughput/dev /sys/devices/virtual/misc/psaux/dev /sys/devices/virtual/misc/snapshot/dev /sys/devices/virtual/sound/seq/dev /sys/devices/virtual/sound/timer/dev /sys/devices/virtual/tty/console/dev /sys/devices/virtual/tty/ptmx/dev /sys/devices/virtual/tty/tty/dev /sys/devices/virtual/tty/tty0/dev /sys/devices/virtual/tty/tty1/dev /sys/devices/virtual/tty/tty10/dev /sys/devices/virtual/tty/tty11/dev /sys/devices/virtual/tty/tty12/dev /sys/devices/virtual/tty/tty13/dev /sys/devices/virtual/tty/tty14/dev /sys/devices/virtual/tty/tty15/dev /sys/devices/virtual/tty/tty16/dev /sys/devices/virtual/tty/tty17/dev /sys/devices/virtual/tty/tty18/dev /sys/devices/virtual/tty/tty19/dev /sys/devices/virtual/tty/tty2/dev /sys/devices/virtual/tty/tty20/dev /sys/devices/virtual/tty/tty21/dev /sys/devices/virtual/tty/tty22/dev /sys/devices/virtual/tty/tty23/dev /sys/devices/virtual/tty/tty24/dev /sys/devices/virtual/tty/tty25/dev /sys/devices/virtual/tty/tty26/dev /sys/devices/virtual/tty/tty27/dev /sys/devices/virtual/tty/tty28/dev /sys/devices/virtual/tty/tty29/dev /sys/devices/virtual/tty/tty3/dev /sys/devices/virtual/tty/tty30/dev /sys/devices/virtual/tty/tty31/dev /sys/devices/virtual/tty/tty32/dev
Bug#552578: udev: root partition's UUID not detected
On Wed, Oct 28, 2009 at 1:15 AM, Marco d'Itri m...@linux.it wrote: On Oct 27, Martin-Éric Racine q-f...@iki.fi wrote: Since about one week, the UUID of the root partition is no longer detected. Please report the output of blkid -o udev -p /dev/hda1, for a start. $ sudo blkid -o udev -p /dev/hda1 /dev/hda1: ambivalent result (probably more filesystems on the device) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#552578: udev: root partition's UUID not detected
On Wed, Oct 28, 2009 at 1:32 AM, Marco d'Itri m...@linux.it wrote: On Oct 28, Martin-Éric Racine q-f...@iki.fi wrote: $ sudo blkid -o udev -p /dev/hda1 /dev/hda1: ambivalent result (probably more filesystems on the device) Not my problem then. :-) Searching the net for a solution, I located this somewhat related thread: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/428435 Based on this, I was able to determine that what probably happened is that since this laptop started its life as a Windows machine and was later converted to Debian, a Windows boot block apparently remained on that partition's start: $ sudo BLKID_DEBUG=0x blkid -p /dev/hda1 libblkid: debug mask set to 0x. reseting blkid_probe ready for low-probing, offset=0, size=0 -- starting probing loop [idx=-1] linux_raid_member: call probefunc() ddf_raid_member: call probefunc() isw_raid_member: call probefunc() lsi_mega_raid_member: call probefunc() via_raid_member: call probefunc() silicon_medley_raid_member: call probefunc() nvidia_raid_member: call probefunc() promise_fasttrack_raid_member: call probefunc() highpoint_raid_member: call probefunc() adaptec_raid_member: call probefunc() jmicron_raid_member: call probefunc() vfat: magic sboff=0, kboff=0 vfat: call probefunc() assigning SEC_TYPE assigning UUID assigning VERSION assigning TYPE assigning USAGE -- leaving probing loop (type=vfat) [idx=16] -- starting probing loop [idx=16] ext4dev: magic sboff=56, kboff=1 ext4dev: call probefunc() ext4: magic sboff=56, kboff=1 ext4: call probefunc() ext3: magic sboff=56, kboff=1 ext3: call probefunc() ext2_sb.compat = 0024:0006:0003 assigning LABEL assigning UUID assigning VERSION assigning TYPE assigning USAGE -- leaving probing loop (type=ext3) [idx=22] -- starting probing loop [idx=22] ext2: magic sboff=56, kboff=1 ext2: call probefunc() jbd: magic sboff=56, kboff=1 jbd: call probefunc() ufs: call probefunc() sysv: call probefunc() -- leaving probing loop (failed) [idx=49] ERROR: ambivalent result detected (2 filesystems)! /dev/hda1: ambivalent result (probably more filesystems on the device) $ My best guess is that since GRUB itself was installed on the MBR, the boot block on /dev/hda1 simply wasn't deleted by mke2fs back then and this has suddenly become an issue, with everyone having switched from Ted Tso's e2fstools to the generic linux-utils-ng version of blkid. My question is now, how can I delete this remnant of a VFAT partition without having to reinstall the whole system? Is there any tool that could be used to zero the boot blocks of all partitions, but leave the MBR untouched? The above Launchpad thread offers a small script that can clear ext2/ext3/ext4/swap filesystem signatures and that could be used as a starting point for a more versatile filesystem linting tool. I don't know anything about Python or the tools it calls, but I'm sure that someone on the util-linux maintainer team would be able to figure this one fairly quickly. A secondary question is, what guarantees that debian-installer wouldn't skip such ambiguous filesystem signatures on a fresh install also? -- Martin-Éric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#619461: [Pkg-cups-devel] Bug#619461: cups-pdf: PDFVer and GSCall keys not taken into account
2011/3/24 Volker Behr b...@physik.uni-wuerzburg.de: The log-file you sent me contains the following line: Thu Mar 24 11:05:53 2011 [DEBUG] file already pdf, simply copying it (cp /var/spool/cups-pdf/SPOOL/cups2pdf-12256 /home/jpht/tmp/PDF/Bugs_in_package_cups-pdf_--_Debian_Bug_report_logs.pdf) This option to directly copy PDF instead of reprocessing it was suggested to me some time back and I decided not to implement it since it would disable all options set in cups-pdf.conf on the respective files. This is exactly what happens to you here: the PDF is just passed through instead of getting re-worked with all your desired options by CUPS-PDF. So, speaking for upstream: no fix needed. My advise to the distribution: remove this additional patch on CUPS-PDF since it breaks basic functionality. The patch in question was removed in 2.5.1-1 as far as Debian and Ubuntu are concerned: * Dropped 70_cups-pdf_support-pdf-workflow.patch + This patch has received more criticism than praises from the end-users, because it essentially renders the Ghostscript options in cups-pdf.conf useless, plus it no longer applies cleanly to the upstream code. From this perspective, I'd mark the issue as fixed since that version. Agreed? Martin-Éric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#619461: [Pkg-cups-devel] Bug#619461: Bug#619461: cups-pdf: PDFVer and GSCall keys not taken into account
2011/3/31 Jean-Philippe Thierry jphthierry.pe...@gmail.com: 2011/3/24 Volker Behr b...@physik.uni-wuerzburg.de On Thu, 2011-03-24 at 17:54 +0100, Jean-Philippe Thierry wrote: Le 24 mars 2011 15:44, Martin-Éric Racine martin-eric.rac...@iki.fi a écrit : 2011/3/24 Volker Behr b...@physik.uni-wuerzburg.de: The log-file you sent me contains the following line: Thu Mar 24 11:05:53 2011 [DEBUG] file already pdf, simply copying it (cp /var/spool/cups-pdf/SPOOL/cups2pdf-12256 /home/jpht/tmp/PDF/Bugs_in_package_cups-pdf_--_Debian_Bug_report_logs.pdf) This option to directly copy PDF instead of reprocessing it was suggested to me some time back and I decided not to implement it since it would disable all options set in cups-pdf.conf on the respective files. This is exactly what happens to you here: the PDF is just passed through instead of getting re-worked with all your desired options by CUPS-PDF. So, speaking for upstream: no fix needed. My advise to the distribution: remove this additional patch on CUPS-PDF since it breaks basic functionality. The patch in question was removed in 2.5.1-1 as far as Debian and Ubuntu are concerned: * Dropped 70_cups-pdf_support-pdf-workflow.patch + This patch has received more criticism than praises from the end-users, because it essentially renders the Ghostscript options in cups-pdf.conf useless, plus it no longer applies cleanly to the upstream code. From this perspective, I'd mark the issue as fixed since that version. Agreed? Martin-Éric just tried installing cups-pdf from sid on my squeeze. GSCall and PDFVer are taken into acount but... I am only getting 1 page empty documents; even failling back to the default settings in /etc/cups/cups-pdf.conf. Could it be due to a dependency issue even if not raised by the package? log file attached Just as a note: might be related to issue #617468 I end up recompiling the package from source (squeeze version) removing patch 70_cups-pdf_support-pdf- workflow.patch and it works. Thanks folks for your help. Right, because this was the patch that resulted in Ghostscript options being ignored. I'm just wondering why you get different results with 2.5.1-1 that with a 2.5.0 with that patch removed. Martin-Éric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#618545: [Pkg-cups-devel] Bug#618545: cups-client: upgrade pulls in samba
2011/3/16 Jonathan Nieder jrnie...@gmail.com: [ Martin-Éric Racine ] * Added Recommends:smbclient to cups-client (Closes: #616015). which is about the cupsaddsmb utility using smbclient --- but that does not fulfill the requirement will have to be present in all but unusual installations by a long shot. Would it be possible to downgrade the recommendation to a Suggests? Looking back at the original bug report that prompted this, I guess that yes, a mere Suggests ought to be enough. Martin-Éric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#617468: [Pkg-cups-devel] Bug#617468: My cups-pdf is also producing blank pages, downgraded to 2.5.0-16 works
2011/3/16 Bin Guo gb2...@comcast.net: On Mon, 2011-03-14 at 18:35 +0100, Volker Behr wrote: Just as a hint from upstream: you might want to have a look at /var/log/cups/cups-pdf_log with LogType set to 7 in /etc/cups/cups-pdf.conf. I myself have no current Debian available for testing at the moment. Regards, Volker This is frustrating: while downgraded cups-pdf works, I have another debian system that works fine. No idea what changed, but on my laptop definitely only 2.5.0-16 works. Logs: cups-pdf_log-2.5.0-16-good (downgraded and working on my laptop) cups-pdf_log-2.5.1-1-empty (upgraded but empty on my laptop) cups-pdf_log-2.5.1-1-good (upgraded but working on another debian) This is confusing, because the exact same 2.5.1-1 somehow works on another one of your hosts. I wonder why. Volker: can you spot anything in those logs that I might have missed? Martin-Éric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#627241: opensc: please package OpenSC 0.12.1
Package: opensc Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 It would be immensely appreciated if someone could package OpenSC 0.12.1 and upload it to unstable. Thank you! - -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBCAAGBQJN1EDXAAoJEK4fgnfEtNe2WlUP/1+RF++2hgeHPqBdDtpH1HTa DuSUmL3ec3xi0ZeUAOw6bpj0loHTW5lb6NHnH1IQNKhnPvO+4Wx8/chy3dCuAjSi qeJkuxdCn2LM7YUAVifa+q77D7Dl5AGAYno3z0V1m8oCDi2eyJebsmSIrxijyyc+ CKoUkfPkyZENQ45iB3+uhZzNgaZ/ZF9L0dmjeJW7bNaapRED+Ze2huJCXSTZodvC 7LtIfk1wJtFlNJB8JXSMu3VzsOrLB2uXgJFB4lWMj6BMktBAtuuljVXk4sdxrXhC F4DfU+5J0x+u4LVe6CAxOzKho80uJtCkdz7b9tfwAYsgnJG2C2BK3INBt8c0uENg E09LXgpwIh2RgJn+hQtcVCtvIZ3NQ2i0Z9F7t6khKn3W/C2I7BdUIuIYJjNHRHW1 AYDAcuVTb1v5txaOdk/J5I2mkbMebc1TYEOisiVVsWFFIfLNvdQXHcNboYWcw4L7 /c5dIyHZk5Wgqox3ifHKcqb4+wCsAZYhQp75xVFmvhaL9Vo+rW0Eeqt3B2QrAN+W KQ3YjvjVcOIzc+ORrCcc3P74GopjBf0HJ2k4cUM/HF+kBv+b6lD+Lo1ZzfDHI8c/ OeDBQrPr7Ew3z2VdyPfFsKAzHcm/5zzws/5Mj1aSeGiLyIXuofJKrisVCWQCQpdK oKS+iqMwOue9k43G1FGk =bhoZ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#627242: smartpm: incorrect Python dependencies make DPKG complain loudly
Package: smartpm Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Fetched 7 409 kB in 16s (441 kB/s) Reading changelogs... Done Preconfiguring packages ... dpkg: warning: parsing file '/var/lib/dpkg/available' near line 174738 package 'smartpm': 'Depends' field, reference to 'python': error in version: version number does not start with digit dpkg: warning: parsing file '/var/lib/dpkg/available' near line 174738 package 'smartpm': 'Depends' field, reference to 'python': error in version: version number does not start with digit (Reading database ... 39647 files and directories currently installed.) Preparing to replace debianutils 3.4.5 (using .../debianutils_3.4.6_i386.deb) ... Unpacking replacement debianutils ... Processing triggers for man-db ... Setting up debianutils (3.4.6) ... - -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBCAAGBQJN1EAxAAoJEK4fgnfEtNe2cAgP/0ZIZQHNydPqPZBTzyaILXf9 XD+XVY67cfi+V8/0DCnLFRNkQ+xxddXR7zfZI3Dc8xtDkA0/DOaTCO64d4ayA377 v80FznpHeLdw7OcCe3MIcov9eJkzfU2cDGrB6ZHkJPcG+1tqw+G+Mn5W5I/y4Qkj +4DomGdMHqSbGaetpeeGNnzvg0l2AnUhtgkzdeBjWXEzVi1wHerK4s1DWMWDGQ1d oX0m8xLs1fCaBbZKRkXujPan58G5ZWOZVd4kpAFIfVtU1Qw76NgQ+lY37IhIgij7 yw2cj7t2JLfvxwf6YsQpPP21aexKRu+mTc7NvZivmQz2lNs85D1doPbBi9RUv6P3 1HhJwRJzAWiEnzGH7g/2rN7fmpd3NDHpLXJjZjkL0PiSnw45+u6vI8mBg4eAyciv rt5mowtezVTiRiKk5TaeJC94MXrImBeeq8lwkcQ2Q59tY5pCQEaa1Cxp4RhNJwIv KihlTkzMkMquI4onWx3WcinrAVtACp7QJfWE7uompzXc8CCybv7aa6qGjn5MJxDe 47RasoVVgqKVcaczKx0EWEJ2dJ4wRTOn7+VyH9xTCQYSTnYw3g/KQm2ghfUFVc8h YbPpjrlJSRf8zXSDIGbbkwnFwwh/evMnUsBIaHcx9ou08Z135aIjk5lJU2dbMsiF Vk1gZcwtSpDQE5XuwFWP =xGgO -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#629419: [Pkg-cups-devel] Bug#629419: lpadmin in postinst configure should timeout early
2011/6/6 John Feuerstein j...@feurix.com:
Package: cups-pdf
Version: 2.5.1-3
I've installed cups and the cups-pdf packages using aptitude on current
unstable. There was no previous cups configuration, none of these packages
was installed earlier.
The installation worked out fine in the end, however, the following step
took about 20 minutes without any output:
Setting up cups-pdf (2.5.1-3) ...
Reloading Common Unix Printing System: cupsd.
*hang for about 20 minutes*
I've traced this down to the multiple lpadmin(8) calls in cups-pdf.postinst
configure. Running this on the command-line:
$ sudo lpstat -h localhost -v
while the installation stalled resulted in the same behaviour. Running it
under strace shows that it hangs while connecting:
connect(5, {sa_family=AF_INET, sin_port=htons(631),
sin_addr=inet_addr(127.0.0.1)}, 16^C unfinished ...
This seems to indicate that the problem is with the lpadmin and lpstat
commands themselves and not with CUPS-PDF. Reassigning.
Martin-Éric
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#617468: [Pkg-cups-devel] Bug#617468: My cups-pdf is also producing blank pages, downgraded to 2.5.0-16 works
Another user spotted the same issue on Ubuntu (LP: 600764) and current indications seem to point to changes in our PPD as the possible source of the issue. One user there made various tests and concluded that if he purges the old printer queue from 2.5.0 before upgrading or if he install 2.5.1 on a new CUPS install, he doesn't experience this issue. Another issue might be related to the exact lpadmin syntax used for printer creation/deletion as affecting the result. Martin-Éric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#619461: [Pkg-cups-devel] Bug#619461: Bug#619461: cups-pdf: PDFVer andGSCall keys not taken into account
2011/4/1 jphthierry.pe...@gmail.com: No clue I must admit. Looking at the log file on 2.5.1 everything seems to run smoothly but I end up with a blank file. I can investigate further; I would just need some directions. Can you compare the results between upgrading from 2.5.0 to 2.5.1, verus purging 2.5.0 first and then installing 2.5.1 after? Someone in another bug report seems to have spotted the problem as being possible related to upgrades failing to update the content of our PPD, which might require handling by our package's maintainer script. Martin-Éric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#623743: [Pkg-cups-devel] Bug#623743: cups-pdf: does not properly set supplementary groups when dropping privileges
2011/4/22 Christopher Zimmermann madro...@zakweb.de: Package: cups-pdf Version: 2.5.0-16 Severity: normal Tags: upstream patch When dropping privileges to the user who sent the print job cups-pdf does only set euid and egid, but NOT the supplementary groups. Therefore a common print dump directory only accessible by a print group will only work when all printing users have a primary group of print, but NOT when it is only a supplementary group. Patch is attached. Thanks for this! Upstream reads the Debian bugs against this package, so I'll let him comment and decide whether he wants to merge this. In the meantime, could you check whether this cleanly applies to 2.5.1-2 (currently in unstable, but can easily build for stable, too) and update the patch as necessary? Cheers! Martin-Éric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#539156: [Pkg-cups-devel] Bug#614713: Bug#614713: cups-pdf: installation asks for a password
2011/4/24 Daniel Reichelt deb...@nachtgeist.net: I did some strace'ing of the troubling lpadmin invocation both on the host rootfs and within the chroot and after the connect() call I noticed some numeric named files in /var/run/cups/certs get accessed: So, obviously that has something to do with encryption, which IMO in this case is superfluous since the connection is made to localhost. Sure enough, we had a superfluous -E in our queue creation loop. I just removed it and uploaded the fix as 2.5.1-3. Many, many thanks for figuring this one out! Cheers! Martin-Éric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#578079: [Pkg-cups-devel] Bug#578079: I can see this bug too
2011/4/28 Holger Levsen hol...@layer-acht.org: Hi Tom, did you find a solution for this bug? I see it on one squeeze system, while not on another. Both print to a cups server running squeeze. lpq and lpc status both show the queues nicely to me, yet lpr fails as you described: lpr: Upgrade Required :( I'm starting to suspect that upstream made some backward-incompatible changes to the way queues are handled, because we get a similar problem with CUPS-PDF, but only whenever the package gets upgraded; if it's installed from scratch or purged then re-installed, it works as it should. Either that, or Debian's own choice of using a non-default backend to handle absolutely everything as pure PDF, in a case where upstream defaults to basic Postscript, might be involved. Till Kampetter in fact suggested that this could be a plausible cause for the blank page issue we get with CUPS-PDF upgrades. Martin-Éric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#570637: [Xorg-driver-geode] Still some bitmap corruption
Does Geode 2.11.12-1 solve this issue? Martin-Éric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#570637: [Xorg-driver-geode] Still some bitmap corruption
2011/2/21 Samuel Hym samuel@gmail.com: Does Geode 2.11.12-1 solve this issue? The bug got harder to produce, it seems. Still, by randomly and fast moving a (xterm) window over an (always the same) Evolution window displaying some html message, some corruption appears where the window should have properly been refreshed. Nevertheless, it’s far from clear for me whether X-Geode or Evolution (its html viewer) should bear the blame for this. The shadow of the window is mostly black, with some random glitches sometimes. I attach a partial screenshot. Thank you for these additional infos. Just to verify, under which X server version do you run Geode 2.11.12? On which Debian release? Martin-Éric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#531409: fixed in 2.5.1 - might require purge and reinstallation
As far as other cases indicate, this issue was fixed with the removal of 70_cups-pdf_support-pdf-workflow.patch since 2.5.1-1. Can you please confirm and close the bug if appropriate? Cheers! Martin-Éric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#559685: still valid as of CUPS-PDF 2.5.1 ?
Greetings, I have been unable to reproduce your issue, but I was wondering if it's still valid as of CUPS-PDF package 2.5.1-1 or more recent? Cheers! Martin-Éric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#623743: [cups-pdf] group setting patch
Hello Volker, I was wondering if you had time to examine the patch that is attached to Debian bug #623743 and whether this looks like something that you would merge for CUPS-PDF 2.5.2 or not? Cheers! Martin-Éric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#637778: xorg: Fails to setup AMD Geode gfx card, installing Squeeze on Fit-PC1
2011/8/15 Julien Cristau jcris...@debian.org: reassign 637778 xserver-xorg-video-geode 2.11.9-7 kthxbye On Sun, Aug 14, 2011 at 12:06:37 +0100, Dávur Eyðunsson Sørensen wrote: I'm using Fit-PC1 units (fit-pc.com) as web development pre-prod. One of these requires X installed. Although it is not listed as supported OS, I go with my preference and run Debian instead of recommended Gentoo or Ubuntu. Install worked fine with Lenny but on Squeeze, the graphic card is not setup up correctly anymore. Looks like the X server crashes when the geode driver tries to get the modes, reassigning to the driver. Thank you for re-assigning this bug. That assessment is correct. This being said, we did not know of any commercial product that ships with the DDC pins configured for serial I/O but, apparently, this one does and sadly our driver doesn't know how to fall back to some usable mode or how to bang the GPIO bits back into DDC state before probing. I guess that this something we'll have to get around implementing now. Martin-Éric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#637778: xorg: Fails to setup AMD Geode gfx card, installing Squeeze on Fit-PC1
2011/8/16 Dávur Eyðunsson Sørensen dav...@gmail.com: 2011/8/15 Martin-Éric Racine martin-eric.rac...@iki.fi: 2011/8/15 Julien Cristau jcris...@debian.org: reassign 637778 xserver-xorg-video-geode 2.11.9-7 kthxbye On Sun, Aug 14, 2011 at 12:06:37 +0100, Dávur Eyðunsson Sørensen wrote: I'm using Fit-PC1 units (fit-pc.com) as web development pre-prod. One of these requires X installed. Although it is not listed as supported OS, I go with my preference and run Debian instead of recommended Gentoo or Ubuntu. Install worked fine with Lenny but on Squeeze, the graphic card is not setup up correctly anymore. Looks like the X server crashes when the geode driver tries to get the modes, reassigning to the driver. Thank you for re-assigning this bug. That assessment is correct. This being said, we did not know of any commercial product that ships with the DDC pins configured for serial I/O but, apparently, this one does and sadly our driver doesn't know how to fall back to some usable mode or how to bang the GPIO bits back into DDC state before probing. I guess that this something we'll have to get around implementing now. Martin-Éric Correction: Actually, install does not work neither on any version of Debian nor on Ubuntu, which I've tested on these devices using every version since 8.04, without any luck (bug reports for Ubuntu have been commited to Launchpad bug tracker). On Ubuntu and on Debian, versions prior to Squeeze, it was possible to run graphics in safe mode and get a desktop; also it was possible to concoct some settings in xorg.conf to make things work...but not anymore. One question remains: Is it worth the effort if only to satisfy users of Fit-PC 1, which are no longer in production? Compulab will release a version 3 of the device in fall this year ( see http://www.fit-pc.com/fit-pc3/ ). Dávur Dávur, I'm curious whether the Fit-PC 1 has a BIOS setting to flip the GPIO back into DDC mode. Could you check this? If not, it might be worth placing a support ticket with FIT to produce a corrected BIOS, since putting the DDC pins into serial console mode has very few uses in a production environment. Martin-Éric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#617468: [Pkg-cups-devel] Bug#617468: Hint for the problem
2011/8/28 Karsten Malcher deb...@dct.mine.nu: when i have a look at the CUPS Admin i can see here: http://localhost:631/printers/Kyocera_FS-1010?which_jobs=all For a successfull printing from OOffice: beendet So 28 Aug 2011 18:51:03 CEST For a PDF-Printing: gestoppt /usr/lib/cups/filter/pstopdf failed How can i configure or reinstall this filter? Karsten, I'd be really curious to get a detailed cups.log that shows exactly what was trying to access /usr/lib/cups/filter/pstopdf during the printing attempt. Could you attach this to the bug report? Thanks! Martin-Éric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#617468: [Pkg-cups-devel] Bug#617468: I can confirm
2011/8/29 Denis Linvinus linvi...@gmail.com: I can confirm solution from mesage #55 is working. -*cupsFilter:application/vnd.cups-pdf 0 - -*cupsFilter:application/vnd.cups-postscript 100 - -*% cupsFilter:application/vnd.cups-postscript 100 pstitleiconv +*% cupsFilter:application/vnd.cups-postscript 0 pstitleiconv This basically restores the PPD to its pristine state as shipped. Something else must be modifying it after the installation has taken place. Could you check? Martin-Éric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#617468: solution: purge and re-install to force an upgrade of the PPD
After careful examination, it appears that the 3 superfluous lines in the PPD were added by the PDF Workflow patch that was used for 2.5.0 releases, but has been removed since CUPS-PDF 2.5.1. However, the PPD was not automatically upgraded by our package's maintainer script, which is probably what broke things for people upgrading to some 2.5.1 release. This has been fixed as of CUPS-PDF 2.5.1-4 which entered unstable today, by utilizing a feature of CUPS 1.5.0-3 and more recent to auto-update PPD files whenever a new version gets installed. As a crude test, for older releases, could you try purging and re-installing the package and see if it fixes it? sudo dpkg -P cups-pdf sudo apt-get install cups-pdf Best regards, Martin-Éric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#617468: [Pkg-cups-devel] Bug#617468: Hint for the problem
done 617468 2.5.1-4 thanks 2011/8/30 Karsten Malcher deb...@dct.mine.nu: Hello Martin-Éric, i tried now as root dpkg -P cups-pdf aptitude install cups-pdf The PDF.ppd has been overwritten and PDF printing keeps working. Congratulation - the reason has been found and is fixed! Excellent. Thanks for confirming this! Closing the bug and marking it fixed as of 2.5.1-4. Martin-Éric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#617468: [Pkg-cups-devel] Bug#617468: My cups-pdf is also producing blank pages, downgraded to 2.5.0-16 works
Could anyone still experiencing this issue please follow the instructions at: https://wiki.ubuntu.com/DebuggingPrintingProblems Thanks! Best Regards, Martin-Éric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643790: [Pkg-cups-devel] Bug#643790: /usr/lib/cups/backend/cups-pdf failed when printing via samba to cups pdf
2011/9/29 Ben Whyall b...@whyall-systems.co.uk: Package: cups-pdf Version: 2.5.1-8 Severity: important When trying to print to the cups-pdf printer from windows it reports the above error on the print job and pauses the printer. When printing from local machine it works fine. Could you please attach /var/log/cups/cups-pdf_log and /var/log/cups/error_log to the bug's thread at 643...@bugs.debian.org at your earliest convenience? Thanks! -- Martin-Éric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#643790: [Pkg-cups-devel] Bug#643790: Bug#643790: /usr/lib/cups/backend/cups-pdf failed when printing via samba to cups pdf
2011/9/29 Ben Whyall b...@whyall-systems.co.uk: On 09/29/2011 06:44 PM, Martin-Éric Racine wrote: 2011/9/29 Ben Whyallb...@whyall-systems.co.uk: Package: cups-pdf Version: 2.5.1-8 Severity: important When trying to print to the cups-pdf printer from windows it reports the above error on the print job and pauses the printer. When printing from local machine it works fine. Could you please attach /var/log/cups/cups-pdf_log and /var/log/cups/error_log to the bug's thread at 643...@bugs.debian.org at your earliest convenience? Find attached the two files requested. The CUPS log mentions that the cups-pdf backend crashed with error 11, while the CUPS-PDF log says that it succesfully printed the file. Contradicting. Could you try the following steps: 1. sudo /etc/init.d/cups stop 2. sudo rm -r /var/log/cups/* 3. Uncomment LogType in /etc/cups/cups-pdf.conf and change its value to 7 then save the file. 4. sudo /etc/init.d/cups start 5. Print one sample document locally. (re-enable the PDF backend if necessary, if CUPS disabled it in response to an unexpected situation) 6. Print the exact same document over Samba. 7. sudo /etc/init.d/cups stop 8. e-mail /var/log/cups/cups-pdf_log and /var/log/cups/error_log to 643...@bugs.debian.org again. Thanks! Martin-Éric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#635334: smartpm: incorrect Python dependency version makes dpkg barf
Package: smartpm Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 dpkg: warning: parsing file '/var/lib/dpkg/available' near line 174750 package 'smartpm': 'Depends' field, reference to 'python': error in version: version number does not start with digit - -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.0.0-6-generic (SMP w/1 CPU core) Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBCAAGBQJOLTKvAAoJEK4fgnfEtNe2Wn8QALKs5ShJLHu8cgFpjWy9HTta vNKhCmAX54Pt2ztSqoDdO//+jf0J7JyO9qQ13QsHHV93T2rmTqcpY1GpniXAUZL7 qKc20oSO6PvV5oWL7df9FVi84Z9KlwM/FWMEw0jy4GvYmzl0OcvzKCSOM8ROpZtn 7vrBTXPrJaEtKCIH58KLQ2tsZhdOCJn8yNLBZxf01yMC0tu09orM8/sZNsrhUaba XDmOHf72mdqOiF+1m2eKlr7IjtjRazxsfDt0meiWICbhByjIZLUfecEp3PdG7y9U EcPM7j/b3he2uVwgu0iqhGB+/rB6EKGagboF+mYIdYJSR4DHy7d/1NWXkQgGraKh wJ9LRmritw9RvPVChKU95awjS/56ZVlnZ7BjBvUrG0oCkzbw1O6ZgIoZGMU5k+Mw rJZio4FF8xyxC1Dv2WiUpZNBi7vF+ijrKM76Eg3PAfCICMq1nmYvaPJpBFn/jQsT 0i0fPdVHrY1xSMhgzi8wkxFcWFw6byxaneEKbeg2aiGOlo56l7UlCX8kJh2Pg7tR yCSGGnHDstSPDRPdzS0gE43QboXy51qPrnC3zdvuyZhMkQ4r7jKazbSoolfybOLm LmL1JRXG0ufl18LH9AhMOtryXv/j70SN9QdiqQ9HDXoJT4rCVkeQ4LSrkLgmIoeB skkuw8Njv48F50yzL2Rm =6a7z -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678674: initscripts: upgrade to Wheezy leaves obsolete configs
Package: initscripts Version: 2.88dsf-22.1 Severity: normal Upgrading to Wheezy makes dpkg report the following config files as obsolete: initscripts: /etc/init.d/stop-bootlogd initscripts: /etc/init.d/bootlogd initscripts: /etc/init.d/stop-bootlogd-single They would need to either be moved or removed, as appropriate, using dpkg-maintscript-helper fragments. This is easiest accomplished by populating debian/initscripts.maintscript with suitable mv_conffile or rm_conffile lines, as appropriate. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (1001, 'testing'), (101, 'stable'), (11, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.4-trunk-686-pae (SMP w/2 CPU cores) Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages initscripts depends on: ii coreutils 8.13-3.2 ii debianutils 4.3.1 ii libc6 2.13-33 ii lsb-base4.1+Debian6 ii mount 2.20.1-5 ii sysv-rc 2.88dsf-22.1 ii sysvinit-utils 2.88dsf-22.1 ii ucf 3.0025+nmu3 Versions of packages initscripts recommends: ii e2fsprogs 1.42.4-3 ii psmisc 22.16-1 initscripts 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#678677: grub-common: upgrade to Wheezy leaves obsolete config
Package: grub-common Version: 1.99-22 Severity: normal Upgrading to Wheezy makes dpkg report the following config file as obsolete: grub-common: /etc/grub.d/05_debian_theme It would need to either be moved or removed, as appropriate, using dpkg-maintscript-helper fragments. This is easiest accomplished by populating debian/initscripts.maintscript with suitable mv_conffile or rm_conffile lines, as appropriate. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (1001, 'testing'), (101, 'stable'), (11, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.4-trunk-686-pae (SMP w/2 CPU cores) Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages grub-common depends on: ii gettext-base0.18.1.1-9 ii libc6 2.13-33 ii libdevmapper1.02.1 2:1.02.74-4 ii libfreetype62.4.9-1 ii libfuse22.8.7-2 ii zlib1g 1:1.2.7.dfsg-11 Versions of packages grub-common recommends: ii os-prober 1.53 Versions of packages grub-common suggests: ii desktop-base 6.0.7 pn grub-emu none pn multiboot-doc none pn xorrisonone -- Configuration Files: /etc/grub.d/05_debian_theme [Errno 2] Tiedostoa tai hakemistoa ei ole: u'/etc/grub.d/05_debian_theme' -- 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#678674: initscripts: upgrade to Wheezy leaves obsolete configs
2012/6/23 Petter Reinholdtsen p...@hungry.com: [Roger Leigh] If you do have any ideas about how this can be safely handled, we would of course be very happy to hear them. What about changing them in the bootlogd package, and check if the md5sum of the scripts are the ones from the old initscripts package or the new bootlogd package? It would make it possible to detect if ti is the old ones from initscripts or the new ones from bootlogd. Are you sure they are listed as obsolete by dpkg when both initscripts and bootlogd are installed? I doubt it, but have not tested it. I don't have bootlogd installed. However, I'm starting to feel that we need a proper dpkg-maintscript-helper method to deal with config files that change package ownership, especially in cases when the new package that adopts some config files won't necessarily be pulled in as a Depends or Recommends of the old package. I'd really welcome the feedback of dpkg maintainers on how this could be best handled. Martin-Éric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680639: nautilus: fails to show available SFTP services broadcast by Avahi
Package: nautilus Version: 3.4.2-1 Severity: normal Nautilus stopped showing available SFTP services that are broadcast by Avahi. 'avahi-browse -at' correctly reports all available SFTP services, so this is probably a Nautilus or GVFS issue. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (1001, 'testing'), (101, 'stable'), (11, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/2 CPU cores) Locale: LANG=fi_FI.utf8, LC_CTYPE=fi_FI.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages nautilus depends on: ii desktop-file-utils 0.18-1 ii gsettings-desktop-schemas 3.4.2-1 ii gvfs 1.12.3-1+b1 ii libatk1.0-02.4.0-2 ii libc6 2.13-33 ii libcairo-gobject2 1.12.2-1 ii libcairo2 1.12.2-1 ii libexempi3 2.2.0-1 ii libexif12 0.6.20-2 ii libgail-3-03.4.2-1 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libglib2.0-0 2.32.3-1 ii libglib2.0-data2.32.3-1 ii libgnome-desktop-3-2 3.4.2-1 ii libgtk-3-0 3.4.2-1 ii libnautilus-extension1a3.4.2-1 ii libnotify4 0.7.5-1 ii libpango1.0-0 1.30.0-1 ii libselinux12.1.9-5 ii libtracker-sparql-0.14-0 0.14.1-2 ii libx11-6 2:1.5.0-1 ii libxml22.8.0+dfsg1-4 ii nautilus-data 3.4.2-1 ii shared-mime-info 1.0-1 Versions of packages nautilus recommends: ii brasero 3.2.0-4 ii eject2.1.5+deb1+cvs20081104-10+b1 ii gnome-sushi 0.4.1-3 ii gvfs-backends1.12.3-1+b1 ii librsvg2-common 2.36.1-1 Versions of packages nautilus suggests: ii eog 3.4.2-1 ii evince [pdf-viewer] 3.4.0-2+b1 ii totem3.0.1-8 pn tracker none ii xdg-user-dirs0.14-1 -- 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#677533: video: USB webcam fails since kernel 3.2
2012/6/17 Martin-Éric Racine martin-eric.rac...@iki.fi: pe, 2012-06-15 kello 23:41 -0500, Jonathan Nieder kirjoitti: Martin-Éric Racine wrote: usb 1-7: new high-speed USB device number 3 using ehci_hcd [...] usb 1-7: New USB device found, idVendor=0ac8, idProduct=0321 usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 1-7: Product: USB2.0 Web Camera usb 1-7: Manufacturer: Vimicro Corp. [...] Linux media interface: v0.10 Linux video capture interface: v2.00 gspca_main: v2.14.0 registered gspca_main: vc032x-2.14.0 probing 0ac8:0321 usbcore: registered new interface driver vc032x The device of interest is discovered. gspca_main: ISOC data error: [36] len=0, status=-71 gspca_main: ISOC data error: [65] len=0, status=-71 [...] gspca_main: ISOC data error: [48] len=0, status=-71 video_source:sr[3246]: segfault at 0 ip (null) sp ab36de1c error 14 in cheese[8048000+21000] gspca_main: ISOC data error: [17] len=0, status=-71 (The above data error spew starts around t=121 seconds and continues at a rate of about 15 messages per second. The segfault is around t=154.) The vc032x code hasn't changed since 3.4.1, so please report your symptoms to Jean-François Moine moin...@free.fr, cc-ing linux-me...@vger.kernel.org, linux-ker...@vger.kernel.org, and either me or this bug log so we can track it. Be sure to mention: - steps to reproduce, expected result, actual result, and how the difference indicates a bug (should be simple enough in this case) 1. Ensure that user 'myself' is a member of the 'video' group. 2. Launch the webcam application Cheese from the GNOME desktop. Expected result: Cheese displays whatever this laptop's camera sees. Actual result: Cheese crashes while attempting to access the camera. - how reproducible the bug is (100%?) 100% - which kernel versions you have tested and result with each (what is the newest kernel version that worked?) It probably was 3.1.0 or some earlier 3.2 release (the upcoming Debian will release with 3.2.x; 3.4 was only used here for testing purposes), but I wouldn't know for sure since I don't use my webcam too often. I finally found time to perform further testing, using kernel packages from snapshots.debian.org, and the last one that positively worked (at least using GNOME's webcam application Cheese) was: linux-image-3.1.0-1-686-pae 3.1.8-2 Linux 3.1 for modern PCs This loaded the following video modules: gspca_vc032x gspca_main videodev media Tests using 3.2.1-1 or more recent crashed as described before. This at least gives us a time frame for when the regression started. Martin-Éric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677533: video: USB webcam fails since kernel 3.2
2012/7/8 Hans de Goede hdego...@redhat.com: On 07/08/2012 03:01 PM, Martin-Éric Racine wrote: 2012/6/17 Martin-Éric Racine martin-eric.rac...@iki.fi: pe, 2012-06-15 kello 23:41 -0500, Jonathan Nieder kirjoitti: Martin-Éric Racine wrote: usb 1-7: new high-speed USB device number 3 using ehci_hcd [...] usb 1-7: New USB device found, idVendor=0ac8, idProduct=0321 usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 1-7: Product: USB2.0 Web Camera usb 1-7: Manufacturer: Vimicro Corp. [...] Linux media interface: v0.10 Linux video capture interface: v2.00 gspca_main: v2.14.0 registered gspca_main: vc032x-2.14.0 probing 0ac8:0321 usbcore: registered new interface driver vc032x The device of interest is discovered. gspca_main: ISOC data error: [36] len=0, status=-71 gspca_main: ISOC data error: [65] len=0, status=-71 [...] gspca_main: ISOC data error: [48] len=0, status=-71 video_source:sr[3246]: segfault at 0 ip (null) sp ab36de1c error 14 in cheese[8048000+21000] gspca_main: ISOC data error: [17] len=0, status=-71 (The above data error spew starts around t=121 seconds and continues at a rate of about 15 messages per second. The segfault is around t=154.) The vc032x code hasn't changed since 3.4.1, so please report your symptoms to Jean-François Moine moin...@free.fr, cc-ing linux-me...@vger.kernel.org, linux-ker...@vger.kernel.org, and either me or this bug log so we can track it. Be sure to mention: - steps to reproduce, expected result, actual result, and how the difference indicates a bug (should be simple enough in this case) 1. Ensure that user 'myself' is a member of the 'video' group. 2. Launch the webcam application Cheese from the GNOME desktop. Expected result: Cheese displays whatever this laptop's camera sees. Actual result: Cheese crashes while attempting to access the camera. - how reproducible the bug is (100%?) 100% - which kernel versions you have tested and result with each (what is the newest kernel version that worked?) It probably was 3.1.0 or some earlier 3.2 release (the upcoming Debian will release with 3.2.x; 3.4 was only used here for testing purposes), but I wouldn't know for sure since I don't use my webcam too often. I finally found time to perform further testing, using kernel packages from snapshots.debian.org, and the last one that positively worked (at least using GNOME's webcam application Cheese) was: linux-image-3.1.0-1-686-pae 3.1.8-2 Linux 3.1 for modern PCs This loaded the following video modules: gspca_vc032x gspca_main videodev media Tests using 3.2.1-1 or more recent crashed as described before. This at least gives us a time frame for when the regression started. Hmm, this is then likely caused by the new isoc bandwidth negotiation code in 3.2, unfortunately the vc032x driver is one of the few gspca drivers for which I don't have a cam to test with. Can you try to build your own kernel from source? Boot into your own kernel, and verify the regression is still there, then edit drivers/media/video/gspca/gspca.c and go to the which_bandwidth function, and at the beginning of this function add the following line: return 2000 * 2000 * 120; Then rebuild and re-install the kernel and try again. If that helps, remove the added return 2000 * 2000 * 120; line, and also remove the following lines from which_bandwidth: /* if the image is compressed, estimate its mean size */ if (!gspca_dev-cam.needs_full_bandwidth bandwidth gspca_dev-cam.cam_mode[i].width * gspca_dev-cam.cam_mode[i].height) bandwidth = bandwidth * 3 / 8; /* 0.375 */ And try again if things still work this way. Once you've tested this I can try to write a fix for this. Hans, Thank you for your reply. Just to eliminate the possibility of mistakes on my part while trying to perform the above changes, could you send me a patch against Linux 3.2.21 that I could apply as-is, before building myself a test kernel package? Cheers! Martin-Éric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680947: Recommends: at-spi - at-spi2-core
Package: gdm3 Version: 3.4.1-2 Severity: normal As far as I can tell, the Recommends on at-spi is obsolete (based on deprecated GNOME 2 components) and should be replaced by a Recommends on at-spi2-core. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (1001, 'testing'), (101, 'stable'), (11, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-3-686-pae (SMP w/2 CPU cores) Locale: LANG=fi_FI.utf8, LC_CTYPE=fi_FI.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gdm3 depends on: ii accountsservice 0.6.21-5 ii adduser 3.113+nmu3 ii dconf-gsettings-backend 0.12.1-2 ii dconf-tools 0.12.1-2 ii debconf [debconf-2.0] 1.5.44 ii dpkg1.16.4.3 ii gir1.2-freedesktop 1.32.1-1 ii gir1.2-glib-2.0 1.32.1-1 ii gnome-session [x-session-manager] 3.4.2.1-1 ii gnome-session-bin 3.4.2.1-1 ii gnome-session-fallback [x-session-manager] 3.4.2.1-1 ii gnome-settings-daemon 3.4.2-3 ii gnome-terminal [x-terminal-emulator]3.4.1.1-1 ii gsettings-desktop-schemas 3.4.2-1 ii libaccountsservice0 0.6.21-5 ii libatk1.0-0 2.4.0-2 ii libattr11:2.4.46-8 ii libaudit0 1:1.7.18-1.1 ii libc6 2.13-33 ii libcairo-gobject2 1.12.2-2 ii libcairo2 1.12.2-2 ii libcanberra-gtk3-0 0.28-4 ii libcanberra00.28-4 ii libdbus-1-3 1.6.0-1 ii libdbus-glib-1-20.100-1 ii libfontconfig1 2.9.0-6 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libglib2.0-02.32.3-1 ii libglib2.0-bin 2.32.3-1 ii libgtk-3-0 3.4.2-2 ii libpam-modules 1.1.3-7.1 ii libpam-runtime 1.1.3-7.1 ii libpam0g1.1.3-7.1 ii libpango1.0-0 1.30.0-1 ii librsvg2-common 2.36.1-1 ii libselinux1 2.1.9-5 ii libupower-glib1 0.9.17-1 ii libwrap07.6.q-23 ii libx11-62:1.5.0-1 ii libxau6 1:1.0.7-1 ii libxdmcp6 1:1.1.1-1 ii libxklavier16 5.2.1-1 ii libxrandr2 2:1.3.2-2 ii lsb-base4.1+Debian7 ii metacity [x-window-manager] 1:2.34.3-2 ii mutter [x-window-manager] 3.4.1-4 ii policykit-1-gnome 0.105-2 ii upower 0.9.17-1 ii x11-common 1:7.7+1 ii x11-xserver-utils 7.7~3 ii xterm [x-terminal-emulator] 278-1 Versions of packages gdm3 recommends: pn at-spinone ii desktop-base 7.0.0 ii gnome-icon-theme 3.4.0-2 ii x11-xkb-utils 7.7~1 ii xserver-xephyr2:1.12.1.902-1 ii xserver-xorg 1:7.7+1 ii zenity3.4.0-2 Versions of packages gdm3 suggests: ii gnome-mag 1:0.16.3-1 pn gnome-orcanone ii gnome-shell 3.4.1-8 pn gok none ii libpam-gnome-keyring 3.4.1-4 -- debconf information: * shared/default-x-display-manager: gdm3 gdm3/daemon_name: /usr/sbin/gdm3 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680952: task-finnish-desktop: Recommends mozvoikko - xul-ext-mozvoikko
Package: task-finnish-desktop Version: 3.09 Severity: normal mozvoikko is deprecated and has become a transitional package for xul-ext-mozvoikko. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (1001, 'testing'), (11, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-3-686-pae (SMP w/2 CPU cores) Locale: LANG=fi_FI.utf8, LC_CTYPE=fi_FI.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages task-finnish-desktop depends on: ii tasksel 3.09 Versions of packages task-finnish-desktop recommends: ii iceweasel-l10n-fi1:10.0.5esr-1 ii libreoffice-help-fi 1:3.5.4-5 ii libreoffice-l10n-fi 1:3.5.4-5 ii libreoffice-voikko 3.3-3 ii mozvoikko2.0.1-1 task-finnish-desktop 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#656745: gnome-control-center: Region panel breaks LANG, breaks terminal charset, shows wrong languages
2012/4/14 John Paul Adrian Glaubitz glaub...@physik.fu-berlin.de: Package: gnome-control-center Version: 1:3.2.2-2 Followup-For: Bug #656745 I can confirm the incorrect behavior of the Region panel. For me, it will always list: British English Chinese (simplified) English Spanish This particular issue seems to be the result of a commit by Rodrigo Moya that makes the Region tab always show specific languages if a GDM localisation for them is installed on the system: https://mail.gnome.org/archives/commits-list/2011-October/msg04043.html Here, as a work-around, I installed the Debian package localepurge which at least only leaves as available those localisations that I actually want to see. Regardless, the above code itself would need to be fixed, because it auto-adds specific languages without making it possible to remove them from the list using the Minus button, which is what would be the expected behavior. Also, rather than attempt to auto-add a multitude of languages to the Region tab, the language selector pull-down list should be restored in GDM; whoever recently removed it from there really needs to get their brain checked. Martin-Éric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677533: video: USB webcam fails since kernel 3.2
Hi Jonathan,
Thank you for these detailed instructions. Find the results of my testing below:
2012/7/9 Jonathan Nieder jrnie...@gmail.com:
Hans de Goede wrote:
Erm, that is quite a bit of work from my side for something which you
can easily do yourself, edit gspca.c, search for which_bandwidth
and then under the following lines:
u32 bandwidth;
int i;
Add a line like this:
return 2000 * 2000 * 120;
In case it helps, here are some more complete instructions.
0. Prerequisites:
apt-get install git build-essential
1. Get the kernel history, if you don't already have it:
git clone \
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
Cloned up to the following commit:
commit 2437fccfbfc83bcb868ccc7fdfe2b5310bf07835
Merge: 6c6ee53 d92d95b6
Author: Linus Torvalds torva...@linux-foundation.org
Date: Mon Jul 9 13:43:02 2012 -0700
Merge tag 'regulator-3.5' of
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator
2. Try linus's master:
cd linux
git fetch origin
git reset --hard origin/master
cp /boot/config-$(uname -r) .config; # current configuration
scripts/config --disable DEBUG_INFO
make localmodconfig; # optional: minimize configuration
make deb-pkg; # optionally with -jnum for parallel build
dpkg -i ../name of package; # as root
reboot
... test test test ...
Hopefully it reproduces the bug.
Fails as previously.
3. Try Hans's first suggested change, as described in the quoted text
above:
/* compute the minimum bandwidth for the current transfer */
static u32 which_bandwidth(struct gspca_dev *gspca_dev)
{
u32 bandwidth;
int i;
return 2000 * 2000 * 120;
/* get the (max) image size */
cd linux
vi drivers/media/video/gspca/gspca.c
... make the suggested edits ...
make deb-pkg; # maybe with -j4
dpkg -i ../name of package; # as root
reboot
... test test test ...
The camera works again in Cheese, at least some of the time. Other
times, launching Cheese immediately crashes GNOME, which restarts the
X.org server.
However, with Skype 4.0.0.7, it only shows a green square, instead of
the camera's output.
4. Try Hans's second suggested change, as described in a previous
message:
cd linux
vi drivers/media/video/gspca/gspca.c
... make the suggested edits ...
make deb-pkg; # maybe with -j4
dpkg -i ../name of package; # as root
reboot
... test test test ...
This produces a severely distorted image for a few seconds, then
Cheese crashes; GNOME itself survives.
Meanwhile, Skype 4.0.0.7 shows a black square, instead of the camera's output.
I hope that the above already provides some usable answers.
Martin-Éric
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681177: mlocate: cron.daily job killed with error 137
Package: mlocate Version: 0.23.1-1 Severity: normal As mailed to me by cron: /etc/cron.daily/mlocate: line 36:29683 Killed $IONICE /usr/bin/updatedb.mlocate run-parts: /etc/cron.daily/mlocate exited with return code 137 -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (1001, 'testing') Architecture: i386 (i586) Kernel: Linux 3.2.0-3-486 Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mlocate depends on: ii adduser 3.113+nmu3 ii libc62.13-33 mlocate recommends no packages. mlocate 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#677533: video: USB webcam fails since kernel 3.2
2012/7/10 Jean-Francois Moine moin...@free.fr: So, it would be interesting to know if the (almost) last driver works. Then, you may try the gspca-2.15.18.tar.gz from my web site: wget http://moinejf.free.fr/gspca-2.15.18.tar.gz tar -zxf gspca-2.15.18.tar.gz cd gspca-2.15.18 make $ LC_ALL=C make make -C /lib/modules/3.5.0-rc6+/build M=/home/perkelix/gspca-2.15.18/build modules make: *** /lib/modules/3.5.0-rc6+/build: No such file or directory. Stop. make: *** [modules] Error 2 su make install reboot You may then try cheese. For skype, don't forget to force the use of the v4l library: export LD_PRELOAD=/usr/lib/libv4l/v4l2convert.so skype I don't recall Skype having required this in a long time. As I already said, until recently, the camera just worked. If the problem is still there, I'd be glad to get some traces. For that, as root, do: echo 0x1f /sys/module/gspca_main/parameters/debug then, unplug/replug the webcam, No can do; this is an internal webcam. Martin-Éric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677533: video: USB webcam fails since kernel 3.2
2012/7/11 Jean-Francois Moine moin...@free.fr: On Wed, 11 Jul 2012 10:02:27 +0300 Martin-Éric Racine martin-eric.rac...@iki.fi wrote: [snip] wget http://moinejf.free.fr/gspca-2.15.18.tar.gz tar -zxf gspca-2.15.18.tar.gz cd gspca-2.15.18 make $ LC_ALL=C make make -C /lib/modules/3.5.0-rc6+/build M=/home/perkelix/gspca-2.15.18/build modules make: *** /lib/modules/3.5.0-rc6+/build: No such file or directory. Stop. make: *** [modules] Error 2 You need the linux headers of your running kernel to compile the tarball. I installed them. That still doesn't fix it: $ LC_ALL=C make make -C /lib/modules/3.5.0-rc6+/build M=/home/perkelix/gspca-2.15.18/build modules make[1]: Entering directory `/usr/src/linux-headers-3.5.0-rc6+' /usr/src/linux-headers-3.5.0-rc6+/arch/x86/Makefile:39: /usr/src/linux-headers-3.5.0-rc6+/arch/x86/Makefile_32.cpu: No such file or directory make[1]: *** No rule to make target `/usr/src/linux-headers-3.5.0-rc6+/arch/x86/Makefile_32.cpu'. Stop. make[1]: Leaving directory `/usr/src/linux-headers-3.5.0-rc6+' make: *** [modules] Error 2 -- Martin-Éric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677533: video: USB webcam fails since kernel 3.2
2012/7/11 Jean-Francois Moine moin...@free.fr: On Wed, 11 Jul 2012 13:21:55 +0300 Martin-Éric Racine martin-eric.rac...@iki.fi wrote: I installed them. That still doesn't fix it: $ LC_ALL=C make make -C /lib/modules/3.5.0-rc6+/build M=/home/perkelix/gspca-2.15.18/build modules make[1]: Entering directory `/usr/src/linux-headers-3.5.0-rc6+' /usr/src/linux-headers-3.5.0-rc6+/arch/x86/Makefile:39: /usr/src/linux-headers-3.5.0-rc6+/arch/x86/Makefile_32.cpu: No such file or directory make[1]: *** No rule to make target Strange. The file arch/x86/Makefile_32.cpu is in the linux 3.5.0 tree. It should have been forgotten in the Debian package. You may copy it from any other kernel source/header you have. That would be a bug in upstream GIT's built-in support for producing Debian packages then. Anyhow, after copying the missing file, the build successfully launches then breaks as follow: CC [M] /home/perkelix/gspca-2.15.18/build/ov534_9.o /home/perkelix/gspca-2.15.18/build/ov534_9.c: In function ‘sd_init’: /home/perkelix/gspca-2.15.18/build/ov534_9.c:1353:3: error: implicit declaration of function ‘err’ [-Werror=implicit-function-declaration] cc1: some warnings being treated as errors make[2]: *** [/home/perkelix/gspca-2.15.18/build/ov534_9.o] Virhe 1 make[1]: *** [_module_/home/perkelix/gspca-2.15.18/build] Error 2 make[1]: Leaving directory `/usr/src/linux-headers-3.5.0-rc6+' make: *** [modules] Error 2 -- Martin-Éric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677533: video: USB webcam fails since kernel 3.2
2012/7/11 Jean-Francois Moine moin...@free.fr: On Wed, 11 Jul 2012 14:14:24 +0300 Martin-Éric Racine martin-eric.rac...@iki.fi wrote: CC [M] /home/perkelix/gspca-2.15.18/build/ov534_9.o /home/perkelix/gspca-2.15.18/build/ov534_9.c: In function ‘sd_init’: /home/perkelix/gspca-2.15.18/build/ov534_9.c:1353:3: error: implicit declaration of function ‘err’ [-Werror=implicit-function-declaration] cc1: some warnings being treated as errors make[2]: *** [/home/perkelix/gspca-2.15.18/build/ov534_9.o] Virhe 1 make[1]: *** [_module_/home/perkelix/gspca-2.15.18/build] Error 2 make[1]: Leaving directory `/usr/src/linux-headers-3.5.0-rc6+' make: *** [modules] Error 2 Sorry, I did not compile yet with kernel = 3.4. So, please, edit the file build/ov534_9.c (and possibly other sources), changing the calls to 'err' to 'pr_err'. This was was required for both build/ov534_9.c and build/spca505.c to build agaist 3.5. Sure enough, this seems to fix support for this camera in both Cheese and Skype. Hurray! :-) Now, the only thing that remains is for this to be merged in the 3.5 tree, then backported to the 3.2 tree that is used for Debian's upcoming Wheezy stable release (and for Ubuntu's recently released Precise also). Thanks again to everyone for the hand-holding! Cheers! Martin-Éric PS: Jonathan, do you feel like investigating why arch/x86/Makefile_32.cpu wasn't included in the linux-headers-3.5.0-rc6+_3.5.0-rc6+-1_i386.deb package that was generated by the 'make deb-pkg' target? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#674743: nullmailer: init.d: LSB: Should-Start: network-manager
Package: nullmailer Version: 1:1.10-1 Severity: normal Tags: patch On systems where the network is started by Network-Manager, rather than by ifupdown, mail cannot be forwarded until Network-Manager has established the connection. Therefore, the LSB header in nullmailer needs to have a soft dependency upon network-manager. The attached patch accomplishes this. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (1, 'unstable') Architecture: i386 (i586) Kernel: Linux 3.2.0-2-486 Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages nullmailer depends on: ii debconf [debconf-2.0] 1.5.43 ii libc6 2.13-32 ii libgcc11:4.7.0-8 ii libgnutls262.12.19-1 ii libstdc++6 4.7.0-8 ii lsb-base 4.1+Debian3 Versions of packages nullmailer recommends: ii rsyslog [system-log-daemon] 5.8.11-1 nullmailer suggests no packages. -- debconf information excluded --- /etc/init.d/nullmailer.dpkg-old 2012-05-05 20:13:29.645013990 +0300 +++ /etc/init.d/nullmailer 2012-02-22 23:57:16.0 +0200 @@ -2,7 +2,6 @@ ### BEGIN INIT INFO # Provides: nullmailer -# Should-Start: network-manager # Required-Start:$remote_fs $syslog $network # Required-Stop: $remote_fs $syslog $network # Default-Start: 2 3 4 5
Bug#675827: apt-utils: apt-ftparchive.conf example file incorrect for apt-file friendly output
Package: apt-utils
Version: 0.9.5.1
Severity: normal
Tags: patch
The example at /usr/share/doc/apt-utils/examples/apt-ftparchive.conf
will generate the Contents file to the root of $(DIST) tree. This is
not where 'apt-file update' expects to find it. Instead, it wants it
at the root of $(SECTION). The attached patch fixes it accordingly.
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-24-generic-pae (SMP w/1 CPU core)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages apt-utils depends on:
ii libapt-inst1.5 0.9.5.1
ii libapt-pkg4.12 0.9.5.1
ii libc6 2.13-32
ii libdb5.15.1.29-4
ii libgcc1 1:4.7.0-11
ii libstdc++6 4.7.0-11
apt-utils recommends no packages.
Versions of packages apt-utils suggests:
ii xz-utils 5.1.1alpha+20110809-3
-- no debconf information
--- a/usr/share/doc/apt-utils/examples/apt-ftparchive.conf 2011-06-17 13:10:20.0 +0300
+++ b/usr/share/doc/apt-utils/examples/apt-ftparchive.conf 2012-06-03 17:59:35.330121443 +0300
@@ -21,21 +21,21 @@ Default {
BinDirectory pool/main {
Packages dists/sid/main/binary-i386/Packages;
Sources dists/sid/main/source/Sources;
- Contents dists/sid/Contents-i386;
+ Contents dists/sid/main/Contents-i386;
}
// This is the same for the contrib section
BinDirectory pool/contrib {
Packages dists/sid/contrib/binary-i386/Packages;
Sources dists/sid/contrib/source/Sources;
- Contents dists/sid/Contents-i386;
+ Contents dists/sid/contrib/Contents-i386;
}
// This is the same for the non-free section
BinDirectory pool/non-free {
Packages dists/sid/non-free/binary-i386/Packages;
Sources dists/sid/non-free/source/Sources;
- Contents dists/sid/Contents-i386;
+ Contents dists/sid/non-free/Contents-i386;
};
// By default all Packages should have the extension .deb
Bug#677533: video: USB webcam fails since kernel 3.2
Package: linux-2.6 Version: 3.2.19-1 Severity: normal Since recent kernels, this ASUS W5F's built-in webcam fails to be detected. Gstreamer-based applications (Cheese, gstreamer-properties) immediately crash whenever trying to access the video device. Meanwhile, Skype (version 4.0.0.7-1 from Skype's own Debian non-free repository) shows that a USB 2.0 camera exists at /dev/video0 but video fails to be shown. The user trying to access the device is a member of the video group in /etc/group, so this is definitely not a permission issue. Instructions on how to further debug this are welcome. -- Package-specific info: ** Version: Linux version 3.2.0-2-686-pae (Debian 3.2.19-1) (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-7) ) #1 SMP Fri Jun 1 18:56:14 UTC 2012 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-2-686-pae root=UUID=ac26e79c-a32e-491a-96f7-8c3a48e0db53 ro quiet splash ** Not tainted ** Kernel log: [84111.113791] gspca_main: ISOC data error: [72] len=0, status=-71 [84111.19] gspca_main: ISOC data error: [38] len=0, status=-71 [84111.529797] gspca_main: ISOC data error: [89] len=0, status=-71 [84111.657798] gspca_main: ISOC data error: [20] len=0, status=-71 [84111.705788] gspca_main: ISOC data error: [39] len=0, status=-71 [84111.705799] gspca_main: ISOC data error: [114] len=0, status=-71 [84112.073804] gspca_main: ISOC data error: [37] len=0, status=-71 [84112.185805] gspca_main: ISOC data error: [96] len=0, status=-71 [84112.249807] gspca_main: ISOC data error: [62] len=0, status=-71 [84112.601812] gspca_main: ISOC data error: [113] len=0, status=-71 [84112.729812] gspca_main: ISOC data error: [44] len=0, status=-71 [84112.793819] gspca_main: ISOC data error: [10] len=0, status=-71 [84113.145829] gspca_main: ISOC data error: [61] len=0, status=-71 [84113.321832] gspca_main: ISOC data error: [86] len=0, status=-71 [84236.666090] gspca_main: ISOC data error: [28] len=0, status=-71 [84236.842097] gspca_main: ISOC data error: [53] len=0, status=-71 [84236.954091] gspca_main: ISOC data error: [17] len=0, status=-71 [84237.018103] gspca_main: ISOC data error: [79] len=0, status=-71 [84237.130093] gspca_main: ISOC data error: [34] len=0, status=-71 [84237.194090] gspca_main: ISOC data error: [104] len=0, status=-71 [84237.386101] gspca_main: ISOC data error: [1] len=0, status=-71 [84237.562112] gspca_main: ISOC data error: [27] len=0, status=-71 [84237.802113] gspca_main: ISOC data error: [18] len=0, status=-71 [84237.803686] video_source:sr[4477]: segfault at 4 ip b769768c sp ab2dce20 error 4 in libgstreamer-0.10.so.0.30.0[b7645000+e7000] [84296.145170] gspca_main: ISOC data error: [108] len=0, status=-71 [84296.209173] gspca_main: ISOC data error: [74] len=0, status=-71 [84296.561175] gspca_main: ISOC data error: [125] len=0, status=-71 [84296.689169] gspca_main: ISOC data error: [56] len=0, status=-71 [84296.753185] gspca_main: ISOC data error: [22] len=0, status=-71 [84297.105194] gspca_main: ISOC data error: [73] len=0, status=-71 [84297.217190] gspca_main: ISOC data error: [60] len=0, status=-71 [84297.281190] gspca_main: ISOC data error: [98] len=0, status=-71 [84297.457188] gspca_main: ISOC data error: [123] len=0, status=-71 [84297.633194] gspca_main: ISOC data error: [101] len=0, status=-71 [84297.649204] gspca_main: ISOC data error: [21] len=0, status=-71 [84297.681195] gspca_main: ISOC data error: [88] len=0, status=-71 [84297.825208] gspca_main: ISOC data error: [46] len=0, status=-71 [84297.873207] gspca_main: ISOC data error: [1] len=0, status=-71 [84298.001203] gspca_main: ISOC data error: [71] len=0, status=-71 [84298.177205] gspca_main: ISOC data error: [97] len=0, status=-71 [84298.545219] gspca_main: ISOC data error: [19] len=0, status=-71 [84298.593205] gspca_main: ISOC data error: [113] len=0, status=-71 [84298.961235] gspca_main: ISOC data error: [36] len=0, status=-71 [84299.073211] gspca_main: ISOC data error: [95] len=0, status=-71 [84299.137232] gspca_main: ISOC data error: [61] len=0, status=-71 [84299.361108] gspca_main: ISOC data error: [126] len=0, status=-71 [84299.489234] gspca_main: ISOC data error: [112] len=0, status=-71 [84299.617228] gspca_main: ISOC data error: [43] len=0, status=-71 [84299.681240] gspca_main: ISOC data error: [9] len=0, status=-71 [84299.713236] gspca_main: ISOC data error: [31] len=0, status=-71 [84300.033246] gspca_main: ISOC data error: [60] len=0, status=-71 [84300.145239] gspca_main: ISOC data error: [119] len=0, status=-71 [84300.209236] gspca_main: ISOC data error: [85] len=0, status=-71 [84300.321231] gspca_main: ISOC data error: [102] len=0, status=-71 [84300.577252] gspca_main: ISOC data error: [8] len=0, status=-71 [84300.689244] gspca_main: ISOC data error: [67] len=0, status=-71 [84300.753249] gspca_main: ISOC data error: [33] len=0, status=-71 [84301.089252] gspca_main: ISOC data error: [23] len=0, status=-71 [84301.105266] gspca_main: ISOC data error: [84] len=0, status=-71 [84301.281275]
Bug#677539: rapid-photo-downloader: please package 0.4.4
Package: rapid-photo-downloader Severity: wishlist Upstream has released a bugfix release, numbered 0.4.4. Could you please package it? Thanks! -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/2 CPU cores) Locale: LANG=fi_FI.utf8, LC_CTYPE=fi_FI.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages rapid-photo-downloader depends on: pn exiftrannone pn gnome-icon-theme3.4.0-2 pn libimage-exiftool-perl none pn librsvg2-common 2.36.1-1 pn python 2.7.2-10 pn python-gconf2.28.1+dfsg-1 pn python-glade2 2.24.0-3 pn python-gnome2 2.28.1+dfsg-1 pn python-gtk2 2.24.0-3 pn python-imaging none pn python-notify none pn python-pyexiv2 none Versions of packages rapid-photo-downloader recommends: pn ffmpegthumbnailernone pn python-hachoir-metadata none pn python-kaa-metadata none rapid-photo-downloader suggests no packages. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677637: ltsp-server: nbi.img cannot boot non-BIOS clients anymore
Package: ltsp-server Version: 5.4.0-1 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Having just upgraded to Wheezy, I notice that the nbi.img produced by ltsp-build-client cannot bootstrap x86 clients built with a non-BIOS firmware anymore. This results in several of my terminals no longer being usable. - -- Package-specific info: chroot information: /opt/ltsp/i386 - -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/1 CPU core) Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ltsp-server depends on: ii debconf [debconf-2.0] 1.5.43 ii debconf-utils 1.5.43 ii debootstrap1.0.40 ii gettext-base 0.18.1.1-8 ii iproute20120521-2 ii lsb-release4.1+Debian6 ii openssh-client 1:6.0p1-1 ii python 2.7.2-10 ii tcpd 7.6.q-23 ii update-inetd 4.43 Versions of packages ltsp-server recommends: ii dnsmasq 2.61-1 ii nbd-server1:3.1.1-1 ii nfs-kernel-server 1:1.2.6-2 ii openbsd-inetd [inet-superserver] 0.20091229-2 ii openssh-server1:6.0p1-1 ii squashfs-tools1:4.2-4+b1 Versions of packages ltsp-server suggests: ii audioossnone ii dnsmasq 2.61-1 ii gnome-session [x-session-manager] 3.4.2.1-1 ii gnome-session-fallback [x-session-manager] 3.4.2.1-1 ii ldm-server 2:2.2.10-1 ii libasound2-plugins 1.0.25-2 ii ltsp-docs none ii ltspfs 1.1-2 ii metacity [x-window-manager] 1:2.34.3-2 ii mutter [x-window-manager] 3.4.1-4 ii pulseaudio 2.0-3 ii qemu-user-staticnone ii sdm none ii x11-utils 7.7~1 ii xauth 1:1.0.7-1 - -- debconf information: ltsp-server/build_client: false -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJP21NMAAoJEK4fgnfEtNe2wQoQAI3cOcqlPcPwcJtYHgVncXLg 8s4ZrP+FN7JPAWHEEChO21sJn4d8nlrmPR0mbxIzMyOoUWIj7pHim3PPmN3q5b4D hwGjj5EEw0SVsxJND6/p5++Gu9xPt5u/FgMJL74M/ghDfFaFihFjkjOxxet3XC/P v2+d0nTk3sHQwuV6ytOm+6vuEKwQFMwf2PWEh8naimpbBv/YF6KxWvScDAHJ4Sos y7zRmLs28KF49exHXfMqnVcvMWFiSAJjWvhF/DdlNnR0guojhX97GbcgrX3GQeq1 lwbZdB8Q7oPRhgoXTok2sI6BdgcrjJJvPCjs90EXzSh/nw8uZ4GLhc8yeSAjdCko wP/qg4HFP878l6XTtv8I7buH0+dBLWXl8pek9Z/QaHzi4fSQB27RcSjRv2YOH7Ec n34hE2424W+sUFLY0vVi1rk/FCL688+cJ2ODCsDmXWpoh8cftD+fyauJ5KTF0gSG zco3gAPOxH9lYapSK5j2JV8VitLXOsFI51chx1Ipl1LxLxkYRGBB3FFrUVNZdazR x0R21nl90LbrscbhEXfdITKpdoD++qMzaZwQ7vpk0uUO1goPEtCODgqEB0weru26 fSIL+wioDAFbCjFUVe8D/+TW4+7UHPiaoH7mcUW0j305fn/yoImVu3MItual1hWP aKR3PLPIdcEjLn97E1fD =8BA7 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677655: 3.4-trunk-486: kernel oops: EIP is at __destroy_inode+0x56/0x8d
Package: linux-2.6 Version: 3.4.1-1~experimental.1 Severity: normal I'm not sure if it's too early to report on kernel 3.4 or not, but here it goes: dmesg keeps on reporting spurious kernel oppses involving inode destructions, as seen below, whenever running kernel 3.4-trunk. -- Package-specific info: ** Version: Linux version 3.4-trunk-486 (Debian 3.4.1-1~experimental.1) (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-7) ) #1 Wed Jun 6 14:24:16 UTC 2012 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.4-trunk-486 root=UUID=97b2628b-28a5-49f2-85f7-495728b3bef8 ro panic=15 pnpbios=off quiet splash ** Tainted: D (128) * Kernel has oopsed before. ** Kernel log: [ 29.054891] DR0: DR1: DR2: DR3: [ 29.054909] DR6: 0ff0 DR7: 0400 [ 29.054928] Process mount (pid: 697, ti=f3eee000 task=f4c69c00 task.ti=f3eee000) [ 29.054944] Stack: [ 29.054955] f551f7d8 c10b6cdd f5624138 c10b5104 f5624138 f3eeff20 f3eeff20 c10b5149 [ 29.054998] f5624198 f5817c00 f5817c80 c10b5362 f5624318 f5624218 f5817c00 [ 29.055040] fff3 c10a9dd3 002e 0027 f5812090 [ 29.055081] Call Trace: [ 29.055107] [c10b6cdd] ? destroy_inode+0x1a/0x3e [ 29.055132] [c10b5104] ? dentry_kill+0x7f/0x8c [ 29.055157] [c10b5149] ? shrink_dentry_list+0x38/0x62 [ 29.055183] [c10b5362] ? shrink_dcache_sb+0x40/0x51 [ 29.055209] [c10a9dd3] ? do_remount_sb+0x5b/0x11c [ 29.055236] [c10b9acc] ? do_mount+0x1de/0x5ca [ 29.055265] [c113b3f0] ? _copy_from_user+0x28/0x47 [ 29.055293] [c108b524] ? memdup_user+0x26/0x43 [ 29.055318] [c10b9f21] ? sys_mount+0x67/0x96 [ 29.055349] [c128e6ec] ? syscall_call+0x7/0xb [ 29.055364] Code: 85 c0 75 0f ba ee 00 00 00 b8 58 a4 33 c1 e8 87 6e f6 ff 8b 43 1c ff 88 c4 01 00 00 8b 43 10 8d 50 ff 83 fa fd 77 14 85 c0 74 10 ff 08 0f 94 c2 84 d2 74 07 31 d2 e8 ee be fa ff 8b 43 14 8d 50 [ 29.055607] EIP: [c10b698e] __destroy_inode+0x56/0x8d SS:ESP 0068:f3eefef0 [ 29.055640] CR2: b4ff [ 29.055657] ---[ end trace b7c0a963a9f117a3 ]--- [ 32.438125] 8139too :00:0d.0: eth0: link up, 100Mbps, full-duplex, lpa 0x45E1 [ 43.136054] eth0: no IPv6 routers present [ 44.435375] snd-malloc: invalid device type 0 [ 44.436817] snd-malloc: invalid device type 0 [ 44.551172] snd-malloc: invalid device type 0 [ 44.555444] snd-malloc: invalid device type 0 [ 44.557438] snd-malloc: invalid device type 0 [ 44.558636] snd-malloc: invalid device type 0 [ 44.560411] snd-malloc: invalid device type 0 [ 44.565241] snd-malloc: invalid device type 0 [ 44.566586] snd-malloc: invalid device type 0 [ 44.567750] snd-malloc: invalid device type 0 [ 44.570206] snd-malloc: invalid device type 0 [ 44.574927] snd-malloc: invalid device type 0 [ 44.576796] snd-malloc: invalid device type 0 [ 44.578073] snd-malloc: invalid device type 0 [ 44.579760] snd-malloc: invalid device type 0 [ 44.584799] snd-malloc: invalid device type 0 [ 44.586063] snd-malloc: invalid device type 0 [ 44.587221] snd-malloc: invalid device type 0 [ 44.590101] snd-malloc: invalid device type 0 [ 44.595537] snd-malloc: invalid device type 0 [ 44.717354] snd-malloc: invalid device type 0 [ 44.718582] snd-malloc: invalid device type 0 [ 44.720941] snd-malloc: invalid device type 0 [ 44.725762] snd-malloc: invalid device type 0 [ 49.744081] Bluetooth: Core ver 2.16 [ 49.744207] NET: Registered protocol family 31 [ 49.744223] Bluetooth: HCI device and connection manager initialized [ 49.745567] Bluetooth: HCI socket layer initialized [ 49.745590] Bluetooth: L2CAP socket layer initialized [ 49.745621] Bluetooth: SCO socket layer initialized [ 49.788365] Bluetooth: RFCOMM TTY layer initialized [ 49.788395] Bluetooth: RFCOMM socket layer initialized [ 49.788412] Bluetooth: RFCOMM ver 1.11 [ 50.045149] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 50.045173] Bluetooth: BNEP filters: protocol multicast [ 64.436997] colord[2225]: segfault at 8 ip 08052674 sp bf8a6c00 error 4 in colord[8048000+2] [ 67.658424] BUG: unable to handle kernel paging request at 00ff [ 67.658453] IP: [c10b698e] __destroy_inode+0x56/0x8d [ 67.658494] *pde = 01462067 *pte = [ 67.658516] Oops: [#2] [ 67.658532] Modules linked in: mperf cpufreq_conservative cpufreq_userspace cpufreq_powersave cpufreq_stats bnep rfcomm bluetooth rfkill snd_cs5535audio snd_ac97_codec snd_pcm snd_page_alloc ecb snd_seq scx200_acb i2c_core cryptd aes_i586 snd_seq_device snd_timer aes_generic snd geode_aes geode_rng rng_core cs5535_mfd soundcore ac97_bus processor evdev thermal_sys ac ext4 crc16 jbd2 mbcache msr usbhid hid sd_mod crc_t10dif ata_generic ohci_hcd pata_cs5536 libata ehci_hcd usbcore scsi_mod button 8139too 8139cp usb_common mii [last unloaded: scsi_wait_scan] [ 67.658775] [ 67.658793] Pid: 1946, comm: gnome-session Tainted: G D
Bug#677655: 3.4-trunk-486: kernel oops: EIP is at __destroy_inode+0x56/0x8d
Hi Jonathan, 2012/6/15 Jonathan Nieder jrnie...@gmail.com: Hi Martin-Éric, Martin-Éric Racine wrote: I'm not sure if it's too early to report on kernel 3.4 or not, but here it goes: Any package uploaded to the archive is open for bug reports. :) Could you send the full oops trace, starting at the first BUG line? (It should include the text Not tainted.) Even better would be full dmesg output from booting and reproducing the bug. Here's the dmesg output at bootup, right after the first few oopses have started to appear. Cheers! Martin-Éric 6[0.00] Initializing cgroup subsys cpuset 6[0.00] Initializing cgroup subsys cpu 5[0.00] Linux version 3.4-trunk-486 (Debian 3.4.1-1~experimental.1) (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-7) ) #1 Wed Jun 6 14:24:16 UTC 2012 6[0.00] BIOS-provided physical RAM map: 6[0.00] BIOS-e820: - 0009e800 (usable) 6[0.00] BIOS-e820: 0009e800 - 000a (reserved) 6[0.00] BIOS-e820: 000f - 0010 (reserved) 6[0.00] BIOS-e820: 0010 - 37fb (usable) 6[0.00] BIOS-e820: 37fb - 37fb3000 (ACPI NVS) 6[0.00] BIOS-e820: 37fb3000 - 37fc (ACPI data) 6[0.00] BIOS-e820: - 0001 (reserved) 5[0.00] Notice: NX (Execute Disable) protection missing in CPU! 6[0.00] DMI 2.2 present. 7[0.00] DMI: First International Computer, Inc. ION603/ION603, BIOS 6.00 PG 11/08/2007 7[0.00] e820 update range: - 0001 (usable) == (reserved) 7[0.00] e820 remove range: 000a - 0010 (usable) 6[0.00] last_pfn = 0x37fb0 max_arch_pfn = 0x10 7[0.00] initial memory mapped : 0 - 0180 7[0.00] Base memory trampoline at [c009b000] 9b000 size 12288 6[0.00] init_memory_mapping: -377fe000 7[0.00] 00 - 40 page 4k 7[0.00] 40 - 003740 page 2M 7[0.00] 003740 - 00377fe000 page 4k 7[0.00] kernel direct mapping tables up to 377fe000 @ 17fb000-180 6[0.00] RAMDISK: 35fca000 - 36fdd000 4[0.00] ACPI: RSDP 000f5910 00014 (v00 AMDGX3) 4[0.00] ACPI: RSDT 37fb3000 00028 (v01 AMDGX3 AWRDACPI 42302E31 AWRD ) 4[0.00] ACPI: FACP 37fb3080 00074 (v01 AMDGX3 AWRDACPI 42302E31 AWRD ) 4[0.00] ACPI Warning: Invalid length for Pm2ControlBlock: 16, using default 8 (20120320/tbfadt-629) 4[0.00] ACPI: DSDT 37fb3100 01581 (v01 AMDGX3 AWRDACPI 1017 MSFT 0300) 4[0.00] ACPI: FACS 37fb 00040 5[0.00] 7MB HIGHMEM available. 5[0.00] 887MB LOWMEM available. 6[0.00] mapped low ram: 0 - 377fe000 6[0.00] low ram: 0 - 377fe000 4[0.00] Zone PFN ranges: 4[0.00] DMA 0x0010 - 0x1000 4[0.00] Normal 0x1000 - 0x000377fe 4[0.00] HighMem 0x000377fe - 0x00037fb0 4[0.00] Movable zone start PFN for each node 4[0.00] Early memory PFN ranges 4[0.00] 0: 0x0010 - 0x009e 4[0.00] 0: 0x0100 - 0x00037fb0 7[0.00] On node 0 totalpages: 229182 7[0.00] free_area_init_node: node 0, pgdat c13e6e08, node_mem_map f70fd200 7[0.00] DMA zone: 32 pages used for memmap 7[0.00] DMA zone: 0 pages reserved 7[0.00] DMA zone: 3950 pages, LIFO batch:0 7[0.00] Normal zone: 1744 pages used for memmap 7[0.00] Normal zone: 221486 pages, LIFO batch:31 7[0.00] HighMem zone: 16 pages used for memmap 7[0.00] HighMem zone: 1954 pages, LIFO batch:0 6[0.00] Using APIC driver default 6[0.00] ACPI: PM-Timer IO Port: 0x9c10 6[0.00] No local APIC present or hardware disabled 6[0.00] APIC: disable apic facility 6[0.00] APIC: switched to apic NOOP 7[0.00] nr_irqs_gsi: 16 6[0.00] PM: Registered nosave memory: 0009e000 - 0009f000 6[0.00] PM: Registered nosave memory: 0009f000 - 000a 6[0.00] PM: Registered nosave memory: 000a - 000f 6[0.00] PM: Registered nosave memory: 000f - 0010 6[0.00] Allocating PCI resources starting at 37fc (gap: 37fc:c803) 6[0.00] Booting paravirtualized kernel on bare hardware 7[0.00] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768 7[0.00] pcpu-alloc: [0] 0 4[0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 227390 5[0.00] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.4-trunk-486 root=UUID=97b2628b-28a5-49f2-85f7-495728b3bef8 ro panic=15 pnpbios=off quiet splash 6[0.00] PID hash table entries: 4096 (order: 2, 16384
Bug#677637: ltsp-server: nbi.img cannot boot non-BIOS clients anymore
2012/6/15 Vagrant Cascadian vagr...@debian.org: On Fri, Jun 15, 2012 at 06:22:58PM +0300, Martin-Éric Racine wrote: Having just upgraded to Wheezy, I notice that the nbi.img produced by ltsp-build-client cannot bootstrap x86 clients built with a non-BIOS firmware anymore. This results in several of my terminals no longer being usable. You may need to install mknbi in the chroot and configure your DHCP server to pass legacy-nbi.img instead of nbi.img: ltsp-chroot apt-get install mknbi ltsp-chroot /usr/share/ltsp/update-kernels Alternately, install mknbi in the chroot and and remove mkelfimage, and then maybe the nbi.img files will work for you: ltsp-chroot apt-get install mknbi ltsp-chroot apt-get remove mkelfimage ltsp-chroot /usr/share/ltsp/update-kernels If neither of those work, this is likely a bug in mkelfimage, mkelf-linux, or mknbi-linux (or at least a change in behavior, if not a bug). It appears that mkelfimage DOES produce images that the clients accept, but after the initial loading takes place, nothing happens. Meanwhile, neither mkelf-linux or mknbi-linux seem to produce content that this client likes. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677655: 3.4-trunk-486: kernel oops: EIP is at __destroy_inode+0x56/0x8d
2012/6/16 Jonathan Nieder jrnie...@gmail.com: Jonathan Nieder wrote: By the way, searching for that particular address yields the following interesting result. (Nothing else recent, alas.) Better link: https://bugzilla.kernel.org/show_bug.cgi?id=13941 Yup, this issue returns every now and then on the exact same host (which was recently migrated from Ubuntu to Debian, now that Ubuntu stopped supporting anything older than non-PAE 686 hardware), whenever someone touches the inode code again. The nice thing, this time, is that it has become non-fatal; the kernel simply reports the oops and continues operating. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677655: 3.4-trunk-486: kernel oops: EIP is at __destroy_inode+0x56/0x8d
2012/6/16 Ben Hutchings b...@decadent.org.uk: On Fri, 2012-06-15 at 22:37 +0300, Martin-Éric Racine wrote: Hi Jonathan, 2012/6/15 Jonathan Nieder jrnie...@gmail.com: Hi Martin-Éric, Martin-Éric Racine wrote: I'm not sure if it's too early to report on kernel 3.4 or not, but here it goes: Any package uploaded to the archive is open for bug reports. :) Could you send the full oops trace, starting at the first BUG line? (It should include the text Not tainted.) Even better would be full dmesg output from booting and reproducing the bug. Here's the dmesg output at bootup, right after the first few oopses have started to appear. The kernel is trying to free an inode and using an ACL pointer that should presumably be 0x (special value for ACL not in memory) but is instead 0xb4ff. This memory corruption could be a software bug (e.g. use after free) or a hardware fault. What was the last working kernel version on this system? 3.2.0-19 (or whatever 486 kernel is in Testing) is what's normally running on this one. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677617: dri: nouveau_vieux segfaults when called from gnome-control-center
2012/6/16 Julien Cristau jcris...@debian.org: On Fri, Jun 15, 2012 at 14:12:53 +0300, Martin-?ric Racine wrote: 0xb0527b94 in ?? () from /usr/lib/i386-linux-gnu/dri/nouveau_vieux_dri.so You need debug symbols. Cheers, Julien I installed the following: libgl1-mesa-dri-dbg libcogl9-dbg libcogl-pango0-dbg Here's an updated trace (note: neither Clutter or gnome-control-center seem to offer any -dbg package): Reading symbols from /usr/bin/gnome-control-center...(no debugging symbols found)...done. (gdb) run Starting program: /usr/bin/gnome-control-center [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/i386-linux-gnu/i686/cmov/libthread_db.so.1. (process:3609): Gtk-WARNING **: Locale not supported by C library. Using the fallback 'C' locale. (gnome-control-center:3609): Clutter-WARNING **: Locale not supported by C library. Using the fallback 'C' locale. Program received signal SIGSEGV, Segmentation fault. nv04_context_engine (ctx=0x8203cd0) at nv04_context.c:70 70 nv04_context.c: No such file or directory. (gdb) bt #0 nv04_context_engine (ctx=0x8203cd0) at nv04_context.c:70 #1 0xb06e9568 in nv04_emit_tex_obj (ctx=0x8203cd0, emit=65) at nv04_state_tex.c:64 #2 0xb06e75cd in nv04_channel_flush_notify (chan=0x83ce198) at nv04_context.c:99 #3 0xb06c73b1 in nouveau_pushbuf_flush () from /usr/lib/i386-linux-gnu/libdrm_nouveau.so.1 #4 0xb06c7748 in nouveau_grobj_free () from /usr/lib/i386-linux-gnu/libdrm_nouveau.so.1 #5 0xb06e7538 in nv04_context_destroy (ctx=0x8203cd0) at nv04_context.c:161 #6 0xb06e2788 in nouveau_context_destroy (dri_ctx=0x81f25d8) at nouveau_context.c:187 #7 0xb06df00a in driDestroyContext (pcp=0x81f25d8) at ../common/dri_util.c:277 #8 0xb0be282a in ?? () from /usr/lib/i386-linux-gnu/libGL.so.1 #9 0xb0bb96c2 in glXDestroyContext () from /usr/lib/i386-linux-gnu/libGL.so.1 #10 0xb0e9e63c in _cogl_winsys_display_destroy (display=0x8182d68) at ./winsys/cogl-winsys-glx.c:704 #11 0xb0e56d8c in _cogl_display_free (display=0x8182d68) at ./cogl-display.c:59 #12 _cogl_object_display_indirect_free (obj=0x8182d68) at ./cogl-display.c:43 #13 0xb0e58392 in _cogl_object_default_unref (object=0x8182d68) at ./cogl-object.c:96 #14 0xb0e582ef in cogl_object_unref (obj=0x8182d68) at ./cogl-object.c:104 #15 0xb0e5675a in cogl_renderer_check_onscreen_template (renderer=0x81edcb8, onscreen_template=0x8182d30, error=0xbfffec1c) at ./cogl-renderer.c:231 #16 0xb0f14b94 in ?? () from /usr/lib/i386-linux-gnu/libclutter-1.0.so.0 #17 0xb0f4a8bc in ?? () from /usr/lib/i386-linux-gnu/libclutter-1.0.so.0 #18 0xb0f4af07 in ?? () from /usr/lib/i386-linux-gnu/libclutter-1.0.so.0 #19 0xb0f644f1 in ?? () from /usr/lib/i386-linux-gnu/libclutter-1.0.so.0 #20 0xb0f70f5d in ?? () from /usr/lib/i386-linux-gnu/libclutter-1.0.so.0 #21 0xb0f711ad in ?? () from /usr/lib/i386-linux-gnu/libclutter-1.0.so.0 #22 0xb769127a in g_option_context_parse () from /lib/i386-linux-gnu/libglib-2.0.so.0 #23 0xb0f7152e in clutter_init () from /usr/lib/i386-linux-gnu/libclutter-1.0.so.0 #24 0xb0d94e92 in gtk_clutter_init () from /usr/lib/i386-linux-gnu/libclutter-gtk-1.0.so.0 #25 0xb103aef3 in cheese_gtk_init () from /usr/lib/i386-linux-gnu/libcheese-gtk.so.21 #26 0xb1160dd4 in g_io_module_load () from /usr/lib/control-center-1/panels/libuser-accounts.so #27 0xb77e165e in ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 #28 0xb776d656 in g_type_module_use () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 #29 0xb77e1af9 in g_io_modules_load_all_in_directory_with_scope () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 #30 0xb77e1bb3 in g_io_modules_load_all_in_directory () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 #31 0x08050d42 in ?? () #32 0xb776a507 in g_type_create_instance () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 #33 0xb774ccf1 in ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 #34 0xb774ea19 in g_object_newv () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 #35 0xb774efb8 in g_object_new () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 #36 0x080515f8 in gnome_control_center_new () #37 0x0804ed49 in main () (gdb) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677533: video: USB webcam fails since kernel 3.2
pe, 2012-06-15 kello 23:41 -0500, Jonathan Nieder kirjoitti: Martin-Ãric Racine wrote: usb 1-7: new high-speed USB device number 3 using ehci_hcd [...] usb 1-7: New USB device found, idVendor=0ac8, idProduct=0321 usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 1-7: Product: USB2.0 Web Camera usb 1-7: Manufacturer: Vimicro Corp. [...] Linux media interface: v0.10 Linux video capture interface: v2.00 gspca_main: v2.14.0 registered gspca_main: vc032x-2.14.0 probing 0ac8:0321 usbcore: registered new interface driver vc032x The device of interest is discovered. gspca_main: ISOC data error: [36] len=0, status=-71 gspca_main: ISOC data error: [65] len=0, status=-71 [...] gspca_main: ISOC data error: [48] len=0, status=-71 video_source:sr[3246]: segfault at 0 ip (null) sp ab36de1c error 14 in cheese[8048000+21000] gspca_main: ISOC data error: [17] len=0, status=-71 (The above data error spew starts around t=121 seconds and continues at a rate of about 15 messages per second. The segfault is around t=154.) The vc032x code hasn't changed since 3.4.1, so please report your symptoms to Jean-François Moine moin...@free.fr, cc-ing linux-me...@vger.kernel.org, linux-ker...@vger.kernel.org, and either me or this bug log so we can track it. Be sure to mention: - steps to reproduce, expected result, actual result, and how the difference indicates a bug (should be simple enough in this case) 1. Ensure that user 'myself' is a member of the 'video' group. 2. Launch the webcam application Cheese from the GNOME desktop. Expected result: Cheese displays whatever this laptop's camera sees. Actual result: Cheese crashes while attempting to access the camera. - how reproducible the bug is (100%?) 100% - which kernel versions you have tested and result with each (what is the newest kernel version that worked?) It probably was 3.1.0 or some earlier 3.2 release (the upcoming Debian will release with 3.2.x; 3.4 was only used here for testing purposes), but I wouldn't know for sure since I don't use my webcam too often. - a log from booting and reproducing the bug, or a link to one See http://bugs.debian.org/677533 - any other weird symptoms or observations When testing the camera using the closed-source Skype 4.x compiled for Debian, the video preferences dialog shows that a USB 2.0 camera is found at /dev/video0. However, no image is shown. This would confirm the assumption that the issue lies with the kernel video driver, rather than with the Gstreamer framework that Cheese uses to access the camera. Hopefully someone upstream will have ideas for commands to run or patches to apply to further track down the cause. Let's indeed hope so. Thanks for providing these instructions! Regards, Martin-Ãric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677869: gnome-control-center: please generate -dbg package with full symbols
Package: gnome-control-center Version: 1:3.4.2-2 Severity: normal When trying to debug #677617, it would have been useful to be able to install debug symbols for gnome-control-center. Unfortunately, there doesn't appear to be any -dbg package. Could one be added to the binary targets? Thanks! -- System Information: Debian Release: wheezy/sid APT prefers stable APT policy: (1000, 'stable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.4-trunk-686-pae (SMP w/2 CPU cores) Locale: LANG=fi_FI.utf8, LC_CTYPE=fi_FI.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnome-control-center depends on: ii accountsservice0.6.15-4 ii apg2.2.3.dfsg.1-2 ii desktop-file-utils 0.18-1 ii gnome-control-center-data 1:3.4.2-2 ii gnome-desktop3-data3.4.2-1 ii gnome-icon-theme 3.4.0-2 ii gnome-icon-theme-symbolic 3.4.0-2 ii gnome-menus3.4.2-1 ii gnome-settings-daemon 3.4.2-3 ii gsettings-desktop-schemas 3.4.2-1 ii libatk1.0-02.4.0-2 ii libc6 2.13-33 ii libcairo-gobject2 1.12.2-1 ii libcairo2 1.12.2-1 ii libcanberra-gtk3-0 0.28-4 ii libcanberra0 0.28-4 ii libcheese-gtk213.4.2-1 ii libcheese3 3.4.2-1 ii libclutter-1.0-0 1.10.6-1 ii libcogl-pango0 1.10.2-3 ii libcogl9 1.10.2-3 ii libcolord1 0.1.21-1 ii libcomerr2 1.42.2-2 ii libcups2 1.5.3-1 ii libdbus-1-31.6.0-1 ii libdbus-glib-1-2 0.98-1 ii libfontconfig1 2.9.0-6 ii libgcrypt111.5.0-3 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libglib2.0-0 2.32.3-1 ii libgnome-bluetooth10 3.4.0-2 ii libgnome-desktop-3-2 3.4.2-1 ii libgnome-menu-3-0 3.4.2-1 ii libgnomekbd7 3.4.0.2-1 ii libgnutls262.12.19-1 ii libgoa-1.0-0 3.4.2-1 ii libgssapi-krb5-2 1.10.1+dfsg-1 ii libgstreamer0.10-0 0.10.36-1 ii libgtk-3-0 3.4.2-1 ii libgtop2-7 2.28.4-3 ii libjson-glib-1.0-0 0.14.2-1 ii libk5crypto3 1.10.1+dfsg-1 ii libkrb5-3 1.10.1+dfsg-1 ii libnm-glib40.9.4.0-5 ii libnm-gtk0 0.9.4.1-1+b1 ii libnm-util20.9.4.0-5 ii libnotify4 0.7.5-1 ii libpango1.0-0 1.30.0-1 ii libpolkit-gobject-1-0 0.105-1 ii libpulse-mainloop-glib02.0-3 ii libpulse0 2.0-3 ii libsocialweb-client2 0.25.20-1 ii libupower-glib10.9.16-2 ii libwacom2 0.5-1 ii libx11-6 2:1.4.99.901-2 ii libxcomposite1 1:0.4.3-2 ii libxdamage11:1.1.3-2 ii libxext6 2:1.3.1-2 ii libxfixes3 1:5.0-4 ii libxi6 2:1.6.1-1 ii libxklavier16 5.2.1-1 ii libxml22.8.0+dfsg1-3 ii zlib1g 1:1.2.7.dfsg-11 Versions of packages gnome-control-center recommends: ii cups-pk-helper 0.2.1.2-1 ii gnome-online-accounts 3.4.2-1 ii gnome-session 3.4.2.1-1 ii gnome-user-guide 3.4.2-1 ii iso-codes 3.36-1 ii mesa-utils 8.0.1-2+b3 ii mousetweaks3.4.2-1 ii policykit-1-gnome 0.105-2 Versions of packages gnome-control-center suggests: ii gnome-screensaver 3.4.1-1 ii gstreamer0.10-pulseaudio 0.10.31-3 ii libcanberra-gtk-module0.28-4 ii x11-xserver-utils 7.7~3 -- 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#645970: python-apt: please remove Recommends on python2.6
Package: python-apt Version: 0.8.4 Followup-For: Bug #645970 Wheezy will ship with Python 2.7 as standard and yet python-apt still Recommends python2.6, which needlessly pulls the python2.6 package in. Could this please be removed before the freeze? Thanks! -- System Information: Debian Release: wheezy/sid APT prefers stable APT policy: (1000, 'stable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.4-trunk-686-pae (SMP w/2 CPU cores) Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages python-apt depends on: ii libapt-inst1.5 0.9.6 ii libapt-pkg4.12 0.9.6 ii libc6 2.13-33 ii libgcc11:4.7.0-8 ii libstdc++6 4.7.0-8 ii python 2.7.3~rc2-1 ii python-apt-common 0.8.4 ii python2.6 2.6.7-4 ii python2.7 2.7.3~rc2-2.1 Versions of packages python-apt recommends: ii iso-codes3.36-1 ii lsb-release 4.1+Debian6 ii python2.62.6.7-4 ii xz-lzma 5.1.1alpha+20110809-3 Versions of packages python-apt suggests: pn python-apt-dbg none pn python-apt-doc none ii python-gtk2 2.24.0-3 pn python-vte none -- 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#675827: closed by Michael Vogt m...@debian.org (Bug#675827: fixed in apt 0.9.6)
/apt-ftparchive.cc: - default to putting the Contents-* files below $(SECTION) as apt-file expects them there - thanks Martin-Éric Racine! (Closes: #675827) * apt-pkg/deb/deblistparser.cc: - set pkgCacheGen::Essential to all again (Closes: #675449) * apt-pkg/algorithms.cc: - force install only for one essential package out of a group * apt-pkg/aptconfiguration.cc: - if APT::Languages=none save none in allCodes so that the detected configuration is cached as intended (Closes: #674690, LP: #1004947) * apt-pkg/cacheiterators.h: - add an IsMultiArchImplicit() method for Dep- and PrvIterator . [ Justin B Rye ] * doc/apt-cdrom.8.xml: - replace CDROM with the proper CD-ROM in text - correct disc vs. disk issues * doc/apt-extracttemplates.1.xml: - debconf is not DebConf * doc/apt-get.8.xml: - move dselect-upgrade below dist-upgrade - review and fix spelling issues * doc/apt-ftparchive.8.xml, doc/apt-config.8.xml, doc/apt-key.8.xml, doc/apt-mark.8.xml, doc/apt_preferences.5.xml, doc/apt-secure.8.xml, doc/apt-sortpkgs.1.xml, sources.list.5.xml: - review and fix typo, grammar and style issues * doc/apt.conf.5.xml: - review and fix typo, grammar and style issues - rephrase APT::Immediate-Configuration and many others . [ Sebastian Heinlein ] * cmdline/apt-key: - do not hardcode /etc but use Dir::Etc instead . [ Robert Luberda ] * Polish manpage translation update (Closes: #675603) * doc/apt-mark.8.xml: - in hold, the option name is --file not --filename . [ Christian Perrier ] * French program and manpage translation update * Danish program translation by Joe Hansen. Closes: #675605 . [ Thibaut Girka ] * cmdline/apt-get.cc: - complain correctly about :any build-dep on M-A:none packages * apt-pkg/deb/deblistparser.cc: - add support for arch-specific qualifiers in dependencies Checksums-Sha1: f89342513bbee6e96934a58cd60ce1b31f99e1d3 1683 apt_0.9.6.dsc 50a08b7d405cb095bf4946701816ca9a56e16660 3400870 apt_0.9.6.tar.gz c6e3f9bdf7414b1faf4c9a000fc29a2b4232ce03 257998 apt-doc_0.9.6_all.deb de38ab554efbde8cac64cbc1d7fbd6860eaa5fcb 945284 libapt-pkg-doc_0.9.6_all.deb e2baf85c2cdf88fa6ad1ceac49a3514c7c0a5a0e 871942 libapt-pkg4.12_0.9.6_amd64.deb 14139c3a372250d04dc00d158f6933d60c36f0d5 161472 libapt-inst1.5_0.9.6_amd64.deb adb85459ecaaac1e8f9b07bb488b0e21d3ca6393 1035092 apt_0.9.6_amd64.deb e8436a2b858784f915adbe9afbd736e01c55a2b9 182146 libapt-pkg-dev_0.9.6_amd64.deb daa6140df80209dc4ce5fa0da878dacd2f8f2cdb 369674 apt-utils_0.9.6_amd64.deb a6c5e390f95e8171a5b52cbc61f9fb77064fd8c5 104242 apt-transport-https_0.9.6_amd64.deb Checksums-Sha256: 4901d8a1e3605c56f6647f7e2ab8390ed697072ecff05222f298e204c24043c9 1683 apt_0.9.6.dsc 82697f55b9cf7bd364c6b3e2d2ffadfa44f41a9de6864890bf6ef85af3c6a61e 3400870 apt_0.9.6.tar.gz 0dc87ed8c7e16ee08ccb44dbeaac2b1040b844e898fe8a01391d594fd7692658 257998 apt-doc_0.9.6_all.deb b51939784d892bae45bbc8bf5e98f6bdf3d5f32d0e410d9ee1e58809acd44be7 945284 libapt-pkg-doc_0.9.6_all.deb 942e0ceece166b0aa8791bb32be65af951c7ead48f14fc764a05e1869f38e924 871942 libapt-pkg4.12_0.9.6_amd64.deb 87074a7794d4ae5a962301075111b60478d9ee1342b794f2d500572fd79e58a5 161472 libapt-inst1.5_0.9.6_amd64.deb e4bf4acb4333a010f8e51a491a68a566d68929fd7ce5ee65d8fd0ef9158ad86c 1035092 apt_0.9.6_amd64.deb 726b6ef3f7c378fe3e3834c2c9b47fd5dcef44e577947e825ca6b46d4e45c84e 182146 libapt-pkg-dev_0.9.6_amd64.deb 9d1be87ffb8f05632122c9937ff020fc2873444db288d4b58d4fc5493a779728 369674 apt-utils_0.9.6_amd64.deb 44a2abd2daf64b2233283212dbf467864b3ae097f0812b1529cbf1b50a7aecc1 104242 apt-transport-https_0.9.6_amd64.deb Files: bb8ad57afb174d569af4268c2420b8d2 1683 admin important apt_0.9.6.dsc fd1db8b13b0c03d62abcb1be6638c4ff 3400870 admin important apt_0.9.6.tar.gz a01b1d7c350c8ec0f7d473e4eccdfa90 257998 doc optional apt-doc_0.9.6_all.deb 02d7b149603bc8c2501677b48848e71d 945284 doc optional libapt-pkg-doc_0.9.6_all.deb 8378138f6ca21b9c238804b1a6050fb8 871942 admin important libapt-pkg4.12_0.9.6_amd64.deb 482eca79c95e0de257ef308494a3eefd 161472 admin important libapt-inst1.5_0.9.6_amd64.deb 4dba9aae0b6059de7f8faa93a73748a2 1035092 admin important apt_0.9.6_amd64.deb f343ff0f2cffcf80dd39208b349a8c62 182146 libdevel optional libapt-pkg-dev_0.9.6_amd64.deb 73642a31a5f9630cfe87fcf18d1c8cf8 369674 admin important apt-utils_0.9.6_amd64.deb d8752e0a3c12931616a3d98339bdc56c 104242 admin optional apt-transport-https_0.9.6_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAk/WARMACgkQliSD4VZixzRKwgCdEzRr7Un7e7rrgh+dEIXmSWQz 7jUAnjitquxnPS5V6EIMi2YVulYVitc+ =21oE -END PGP SIGNATURE- -- Edelleenlähetetty viesti -- From: Martin-Éric Racine martin-eric.rac...@iki.fi To: Debian Bug Tracking System sub
Bug#677898: initscripts: motd fails to be generated after upgrade to Wheezy
Package: initscripts Version: 2.88dsf-22.1 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Since upgrading to Wheezy, this host no longer produces /var/run/motd upon bootup, as a result of which only 'lastlog' output is displayed upon login. /etc/motd.tail has the stock content provided by pkg:base-files. Manually executing /etc/init.d/bootlogs as root succeeds, which suggests that the problem is somewhere else. Likewise, the script is linked via /etc/rc2.d/, so this is not it either. Help to find the cause of this issue is welcome. - -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/1 CPU core) Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages initscripts depends on: ii coreutils 8.13-3.2 ii debianutils 4.3.1 ii libc6 2.13-33 ii lsb-base4.1+Debian6 ii mount 2.20.1-5 ii sysv-rc 2.88dsf-22.1 ii sysvinit-utils 2.88dsf-22.1 ii ucf 3.0025+nmu3 Versions of packages initscripts recommends: ii e2fsprogs 1.42.2-2 ii psmisc 22.16-1 initscripts suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJP3gD3AAoJEK4fgnfEtNe2RhIP/0PNwnXgCRl4t+ZcVsYgYBeP jgwpskSgdlH4KsAvjsaLh5COTgj/ftm3cYfDNQBrtA/K/E9C1xwKwJZ/imhr6sEO 49BVyxkCP/FhQU2ljmcaE01RxpmnzBw4TxsO8ELd8tD7jBRVyaRkYUxLUOUDB7RB 5aE5UHPPHjh0GBmY3DDGjGOJ8EFqitheSi/3M4Uz6DPrSuFaxwjrDF717Svderb6 dYZq2LxAHMbaQ/I+MiHVrYXPWJCjZxuYm/ynYiQViojstA9KEYGKtmD3Ho44HbTw pGyNvN0CcaqJMTDx47yvAj/qsYQCA0uaMz/ErsCCwLseqzS4OmrYDDJCSiBT/EBy mcIEq2huDGMnYTxRAQ3tE9HGRsl6f/XNv3AS5TzzxqjJGtHXv4bc29R2ouO3kV8D akiMpRYicWBy0NHL9FEg+i+s5qrO2gMX0/t4tLWYIS2/iVxpeXzbzyWSq18WDp0R p4FDbp+4GlBuwROHwaAzXw2mQLzPvgztJ+NNNA11bRsBesG8zHl8M9qwAZzu2iqh bgIEhk8cYbH5m61Yz5SUHwLnBYfiBSgWO56C/DTLJg+IrKEr1cIW7I+D2CQD0yGQ 1rLNzpL0e22SwkiAHl3s1KJkPmjHdCC7NBRS2u/frylK6hT7opZxv8UoKCTM0Q4G 2X/Kpw4X8JcCSx2ABwj5 =0Q/s -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#675827: closed by Michael Vogt m...@debian.org (Bug#675827: fixed in apt 0.9.6)
2012/6/17 David Kalnischkies kalnischkies+deb...@gmail.com: On Sun, Jun 17, 2012 at 5:36 PM, Martin-Éric Racine martin-eric.rac...@iki.fi wrote: This bug was incorrectly marked as fixed. It is not, since /usr/share/doc/apt-utils/examples/apt-ftparchive.conf still contains incorrect information. Please check the patch I submitted with the original bug report. Thanks! Are you sure? The file on my system reads like you requested… (ensure you really have the apt-utils package in version 0.9.6 installed) I just changed more places (like the one mentioned on in the changelog) so that it is the default for apt-ftparchive and also written in the manpage and just mentioned the change only for the binary as this has an effect for a user in contrast to the change in the example file or the manpage. Argh! Sure enough, this particular host had an older version installed. Sorry about that! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677898: initscripts: motd fails to be generated after upgrade to Wheezy
2012/6/18 Roger Leigh rle...@codelibre.net: On Sun, Jun 17, 2012 at 07:08:27PM +0300, Martin-Éric Racine wrote: Since upgrading to Wheezy, this host no longer produces /var/run/motd upon bootup, as a result of which only 'lastlog' output is displayed upon login. /etc/motd.tail has the stock content provided by pkg:base-files. Manually executing /etc/init.d/bootlogs as root succeeds, which suggests that the problem is somewhere else. Likewise, the script is linked via /etc/rc2.d/, so this is not it either. Help to find the cause of this issue is welcome. It shouldn't be like that in wheezy (yet). But there was a bug in base-files. In unstable, initscripts replaces /etc/init.d/bootlogs with /etc/init.d/motd. Note also the changes to /etc/pam.d/(ssh|login). Which version of base-files fixed what issue exactly? What changes to PAM behavior? How do I investigate this? Martin-Éric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678219: zd1211-firmware: please rename the binary target to firmware-zd1211
Package: zd1211-firmware
Severity: normal
Tags: patch
The attached patch implements the transition to the firmware-(driver)
namespace that is nowadays used in Debian. It also slightly upgrades
the packaging to use a simplified debian/rules. Please feel free to
apply it and then upload the updated package to Debian.
diff -u zd1211-firmware-2.21.0.0/debian/control zd1211-firmware-2.21.0.0/debian/control
--- zd1211-firmware-2.21.0.0/debian/control
+++ zd1211-firmware-2.21.0.0/debian/control
@@ -1,15 +1,16 @@
Source: zd1211-firmware
Section: non-free/misc
-Priority: extra
+Priority: optional
+Homepage: http://zd1211.wiki.sourceforge.net/
Maintainer: Christian Kastner deb...@kvr.at
-Build-Depends: debhelper (= 7)
+Build-Depends: debhelper (= 7.0.0~)
Standards-Version: 3.8.4
-Homepage: http://zd1211.wiki.sourceforge.net/
-Package: zd1211-firmware
+Package: firmware-zd1211
Architecture: all
Depends: ${misc:Depends}
-Description: Firmware images for the zd1211rw wireless driver
+Suggests: initramfs-tools, linux-image
+Description: firmware images for the zd1211rw wireless driver
This package contains the firmware to be used with the zd1211rw Linux kernel
driver for USB wireless dongles based on the following chipsets:
.
@@ -21,0 +23,9 @@
+
+Package: zd1211-firmware
+Section: non-free/oldlibs
+Priority: extra
+Architecture: all
+Depends: firmware-zd1211, ${misc:Depends}
+Description: firmware images for the zd1211rw wireless driver (dummy transitional package)
+ This package contains the firmware to be used with the zd1211rw Linux kernel
+ driver for USB wireless dongles based on the following chipsets:
reverted:
--- zd1211-firmware-2.21.0.0/debian/zd1211-firmware.install
+++ zd1211-firmware-2.21.0.0.orig/debian/zd1211-firmware.install
@@ -1 +0,0 @@
-zd1211* /lib/firmware/zd1211/
reverted:
--- zd1211-firmware-2.21.0.0/debian/zd1211-firmware.docs
+++ zd1211-firmware-2.21.0.0.orig/debian/zd1211-firmware.docs
@@ -1 +0,0 @@
-README
diff -u zd1211-firmware-2.21.0.0/debian/changelog zd1211-firmware-2.21.0.0/debian/changelog
--- zd1211-firmware-2.21.0.0/debian/changelog
+++ zd1211-firmware-2.21.0.0/debian/changelog
@@ -1,3 +1,13 @@
+zd1211-firmware (2.21.0.0-2) unstable; urgency=low
+
+ [ Martin-Éric Racine ]
+ * Renamed the binary target to firmware-zd1211.
++ Renamed debian/*.[dirs|docs|install] to match.
+ * Made zd1211-firmware into a transitional package.
+ * Migrated debian/rules to a single debhelper 7 'dh' command.
+
+ -- Christian Kastner deb...@kvr.at Wed, 20 Jun 2012 02:19:04 +0300
+
zd1211-firmware (2.21.0.0-1) unstable; urgency=low
* New maintainer. Closes: #573468
diff -u zd1211-firmware-2.21.0.0/debian/rules zd1211-firmware-2.21.0.0/debian/rules
--- zd1211-firmware-2.21.0.0/debian/rules
+++ zd1211-firmware-2.21.0.0/debian/rules
@@ -2,37 +2,11 @@
-# -*- makefile -*-
-# Sample debian/rules that uses debhelper.
-# This file was originally written by Joey Hess and Craig Small.
-# As a special exception, when this file is copied by dh-make into a
-# dh-make output file, you may use that output file without restriction.
-# This special exception was added by Craig Small in version 0.37 of dh-make.
-
-# Uncomment this to turn on verbose mode.
-#export DH_VERBOSE=1
-
-build:
-
-clean:
- dh_testdir
- dh_clean
-
-install:
- dh_testdir
- dh_testroot
- dh_installdirs
- dh_install
- dh_installdocs
- dh_installchangelogs
- dh_compress
- dh_fixperms
-# dh_installdeb
- dh_gencontrol
- dh_md5sums
- dh_builddeb
-
-binary-indep: install
-
-binary-arch:
-
-binary: binary-indep binary-arch
-
-.PHONY: build clean binary-indep binary-arch binary install
+#
+# debhelper-7 [debian/rules] for src:zd1211-firmware
+#
+## COPYRIGHT © 2012 Martin-Éric Racine martin-eric.rac...@iki.fi
+#
+## LICENSE
+# GPLv2+: GNU GPL version 2 or later http://gnu.org/licenses/gpl.html
+#
+%:
+ dh $@
+#EOF
reverted:
--- zd1211-firmware-2.21.0.0/debian/zd1211-firmware.dirs
+++ zd1211-firmware-2.21.0.0.orig/debian/zd1211-firmware.dirs
@@ -1 +0,0 @@
-/lib/firmware/zd1211/
only in patch2:
unchanged:
--- zd1211-firmware-2.21.0.0.orig/debian/firmware-zd1211.install
+++ zd1211-firmware-2.21.0.0/debian/firmware-zd1211.install
@@ -0,0 +1 @@
+zd1211* /lib/firmware/zd1211/
only in patch2:
unchanged:
--- zd1211-firmware-2.21.0.0.orig/debian/firmware-zd1211.docs
+++ zd1211-firmware-2.21.0.0/debian/firmware-zd1211.docs
@@ -0,0 +1 @@
+README
only in patch2:
unchanged:
--- zd1211-firmware-2.21.0.0.orig/debian/firmware-zd1211.dirs
+++ zd1211-firmware-2.21.0.0/debian/firmware-zd1211.dirs
@@ -0,0 +1 @@
+/lib/firmware/zd1211/
Bug#559009: Debian #559009 -- paprefs: Only show install buttons when PackageKit is available
Greetings, You submitted a patch to Debian against 'paprefs' to only show install buttons when PackageKit is available. Debian has just packaged a newer upstream release and we need to verify whether the patch still applies. Could you please check whether paprefs 0.9.10-1 still needs this? Thanks! Martin-Ãric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#562527: Debian #562527 -- paprefs: interface confusing, please redesign
Greetings, You previously submitted this bug against package 'paprefs' in Debian. Since Debian is merely packaging the upstream software, asking for such a complete redesign here is unlikely to result in the improvements that you seek. Instead, filing a bug at ( https://bugs.freedesktop.org )for product PulseAudio might produce better results. Best Regards, Martin-Ãric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677533: video: USB webcam fails since kernel 3.2
2012/7/11 Hans de Goede hdego...@redhat.com: On 07/11/2012 02:01 PM, Martin-Éric Racine wrote: 2012/7/11 Jean-Francois Moine moin...@free.fr: On Wed, 11 Jul 2012 14:14:24 +0300 Martin-Éric Racine martin-eric.rac...@iki.fi wrote: CC [M] /home/perkelix/gspca-2.15.18/build/ov534_9.o /home/perkelix/gspca-2.15.18/build/ov534_9.c: In function ‘sd_init’: /home/perkelix/gspca-2.15.18/build/ov534_9.c:1353:3: error: implicit declaration of function ‘err’ [-Werror=implicit-function-declaration] cc1: some warnings being treated as errors make[2]: *** [/home/perkelix/gspca-2.15.18/build/ov534_9.o] Virhe 1 make[1]: *** [_module_/home/perkelix/gspca-2.15.18/build] Error 2 make[1]: Leaving directory `/usr/src/linux-headers-3.5.0-rc6+' make: *** [modules] Error 2 Sorry, I did not compile yet with kernel = 3.4. So, please, edit the file build/ov534_9.c (and possibly other sources), changing the calls to 'err' to 'pr_err'. This was was required for both build/ov534_9.c and build/spca505.c to build agaist 3.5. Sure enough, this seems to fix support for this camera in both Cheese and Skype. Hurray! :-) Ok, so it seems that increasing the bandwidth we claim for the camera (which is what my suggested return 2000 * 2000 * 120; change does, helps a bit, where as the changes to vc032x which are in Jean-Francois Moine's gspca-2.15.18 tarbal fix the problem entirely, correct? As far as I can tell, yes, the modules in Jean-François' tarball work as-is to fix the problem. Now, the only thing that remains is for this to be merged in the 3.5 tree, then backported to the 3.2 tree that is used for Debian's upcoming Wheezy stable release (and for Ubuntu's recently released Precise also). Well we first need to turn the changes made in gspca-2.15.18 into a patch will which apply to the latest gspca tree: http://git.linuxtv.org/hgoede/gspca.git/shortlog/refs/heads/media-for_v3.6 And then apply them there, before the can be backported to older kernels. Unfortunately I'm leaving for a week vacation Friday, and I probably won't get around to this before then. Jean-Francois, can you perhaps make a patch against my latest tree for the po / PO3130 changes in your tarbal? Noted. Hopefully, the Debian kernel team can contribute to the backporting part, since it's needed for the upcoming stable release. Martin-Éric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681221: os-prober: stopped finding Windows XP parition
Package: os-prober Version: 1.54 Severity: normal $ sudo dpkg-reconfigure linux-image-3.5.0-rc6+ update-initramfs: Generating /boot/initrd.img-3.5.0-rc6+ Generating grub.cfg ... Found background image: /usr/share/images/desktop-base/desktop-grub.png Found linux image: /boot/vmlinuz-3.5.0-rc6+ Found initrd image: /boot/initrd.img-3.5.0-rc6+ Found linux image: /boot/vmlinuz-3.2.0-3-686-pae Found initrd image: /boot/initrd.img-3.2.0-3-686-pae Found linux image: /boot/vmlinuz-2.6.32-5-686 Found initrd image: /boot/initrd.img-2.6.32-5-686 Found iPXE image: /boot/ipxe.lkrn Found memtest86+ image: /boot/memtest86+.bin Found memtest86+ multiboot image: /boot/memtest86+_multiboot.bin umount: /var/lib/os-prober/mount: not mounted umount: /var/lib/os-prober/mount: not mounted done Since a few days, os-prober suddenly fails at finding the Windows XP partition on this laptop, which results in GRUB2 missing a menu entry and thus in Windows XP being unaccessible. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (1001, 'testing') Architecture: i386 (i686) Kernel: Linux 3.5.0-rc6+ (SMP w/2 CPU cores) Locale: LANG=fi_FI.utf8, LC_CTYPE=fi_FI.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages os-prober depends on: ii libc6 2.13-33 os-prober recommends no packages. os-prober 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#677533: video: USB webcam fails since kernel 3.2
2012/7/11 Jean-Francois Moine moin...@free.fr: On Wed, 11 Jul 2012 16:43:47 +0300 Martin-Éric Racine martin-eric.rac...@iki.fi wrote: Jean-Francois, can you perhaps make a patch against my latest tree for the po / PO3130 changes in your tarbal? Noted. Hopefully, the Debian kernel team can contribute to the backporting part, since it's needed for the upcoming stable release. I had many problems with the vc032x driver, and the source code is very different from the code in the official kernels. As I have no webcam, Martin-Éric, may I ask you to test the backport I will do? It will be done only in the vc032x driver, so you could keep the working gspca_vc032x.ko file you have and restore it between the tests. I still lack the sensor type of your webcam. May you send me the result of: dmesg | fgrep gspca [ 11.834852] gspca_main: v2.15.18 registered [ 11.844262] gspca_main: vc032x-2.15.18 probing 0ac8:0321 [ 11.844682] gspca_vc032x: vc0321 check sensor header 2c [ 11.850304] gspca_vc032x: Sensor ID 3130 (0) [ 11.850309] gspca_vc032x: Find Sensor PO3130NC [ 11.851809] gspca_main: video0 created Backport would be needed against 3.2.21 as this is what Debian will (probably) release with. Cheers! Martin-Éric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#617299: dpkg-deb: should give a hint when it fails due to filling /tmp
Package: dpkg Version: 1.16.4.3 Followup-For: Bug #617299 I also encounter the same bug when trying to build kernel 3.2.21 from upstream tarball: $ LOCALVERSION=-git-686-pae make deb-pkg [...] dpkg-deb: building package `firmware-linux' in `../firmware-linux_3.2.21-git-686-pae-1_i386.deb'. dpkg-deb: building package `linux-headers-3.2.21-git-686-pae' in `../linux-headers-3.2.21-git-686-pae_3.2.21-git-686-pae-1_i386.deb'. dpkg-deb: building package `linux-libc-dev' in `../linux-libc-dev_3.2.21-git-686-pae-1_i386.deb'. dpkg-deb: building package `linux-image-3.2.21-git-686-pae' in `../linux-image-3.2.21-git-686-pae_3.2.21-git-686-pae-1_i386.deb'. dpkg-deb (subprocess): data member: internal gzip write error: 'File not found' dpkg-deb: error: subprocess compress from tar -cf returned error exit status 2 make[1]: *** [deb-pkg] Error 2 make: *** [deb-pkg] Error 2 -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (1001, 'testing') Architecture: i386 (i686) Kernel: Linux 3.5.0-rc6-686-pae (SMP w/2 CPU cores) Locale: LANG=fi_FI.utf8, LC_CTYPE=fi_FI.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages dpkg depends on: ii libbz2-1.0 1.0.6-3 ii libc62.13-33 ii liblzma5 5.1.1alpha+20120614-1 ii libselinux1 2.1.9-5 ii tar 1.26-4 ii zlib1g 1:1.2.7.dfsg-13 dpkg recommends no packages. Versions of packages dpkg suggests: ii apt 0.9.7.1 -- 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#681953: unattended-upgrades: mailx option -a to add UTF-8 header is incompatible with heirloom-mailx
Package: unattended-upgrades Version: 0.79 Severity: normal unattended-upgrades uses the mailx -a option to append MIME Content-Type. This option is uncompatible with heirloom-mailx and results in this error whenever the upgrade output is mailed via a cron job: Content-type: text/plain; charset=UTF-8: No such file or directory Several bugs filed against package 'apticron' reported a similar issue and might provide inspiration for the solution to this bug. :) -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (1001, 'testing') Architecture: i386 (i586) Kernel: Linux 3.2.0-3-486 Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages unattended-upgrades depends on: ii apt0.9.7.1 ii apt-utils 0.9.7.1 ii debconf [debconf-2.0] 1.5.44 ii lsb-base 4.1+Debian7 ii lsb-release4.1+Debian7 ii python 2.7.3~rc2-1 ii python-apt 0.8.4 ii ucf3.0025+nmu3 unattended-upgrades recommends no packages. Versions of packages unattended-upgrades suggests: ii bsd-mailx 8.1.2-0.2006cvs-1 -- Configuration Files: /etc/apt/apt.conf.d/50unattended-upgrades changed [not included] -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682494: init.d: LSB headers: please Provides: $network
Package: ifupdown Version: 0.7 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Now that /etc/init.d/networking has migrated from netbase, it would be desirable for ifupdown and network-manager to feature the following in their respective init.d script's LSB header: Provides: $network This shall ensure that 'insserv' always sort any network services AFTER the network has been brought up. - -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (1001, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-3-686-pae (SMP w/1 CPU core) Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ifupdown depends on: ii dpkg 1.16.4.3 ii initscripts 2.88dsf-22.1 ii iproute 20120521-3 ii libc62.13-33 ii lsb-base 4.1+Debian7 ifupdown recommends no packages. Versions of packages ifupdown suggests: ii isc-dhcp-client [dhcp-client] 4.2.2.dfsg.1-5 ii net-tools 1.60-24.1 ii ppp2.4.5-5.1+b1 pn rdnssd none - -- debconf information excluded -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJQDTSTAAoJEK4fgnfEtNe2xZgQALZzo8wPy23F8r3iD+yLb3lB ZzH7jrm0CBfETOrdBjOXp0N7ANjS4PbiLe51amoFIqTFTuSVBoC4Gto4q4iO3oW0 HTgHEtrjlbDXsv3Eu+UpYigz9iC30LiezAky+cpRs5eE0z4MsBJBsl1+EKiLyA4y CKwnWWUy3cLcvi1nAMBcfVwpAEB+EnDingJl78ea7H00jqOPBhLZa1pe1mRhRlJc PAFkylp66TUkb47wEeHg+iBtdVNVu3JC09fV1Ufti3vSvG3+WCMJuwolSTdf4Okm FEwIf/hAMfWZn010tfKbHk8lfo3oUTYqFzAbjfZ6oWDzLYbbdsFIFy6zblirMSzd JE1MJMo+Qn3UogTEKnihzEHf/ZbmrxNr3PcpufSrDd+9yY6rQk73AgW511/S3dPZ 69bCTCED2zpdn7sSmMSoYc0BV9L9LEELd1kbLpzNzh9lFUhgIozjNa5JbOiN+T5G 3Ewm2Gr9w4m4eWf2Bo2i7sNCmHGvIVC7SN79ciRKcpjcsH0lmWw9QbjyiEfN7iK5 nCMxPZwztSn27+vyTDUx6RGO+KaCADazOysxujCRo60fwYnvdy7Vr/KgUx2ecHnL LP5UOSDYioaRZMRIRgAm2ODuLtzcHt2Vgk57umEWRYfTdjtnrEWdX1j1PNcfL53a zgouIriqRC5pLHzKKlbR =hMGk -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#667424: xsd: ftbfs with GCC-4.7: please perform NMU
Package: xsdcxx Version: 3.3.0.1-1.2+b1 Followup-For: Bug #667424 The patch for this issue was attached 1 month ago already. Since this FTBFS makes other packages also FTBFS, could someone please proceed with a NMU? Thanks! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671304: pulseaudio: please downgrade pulseaudio-esound-compat to Suggests
Package: pulseaudio Version: 1.1-3+b1 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The pulseaudio daemon Recommends pulseaudio-esound-compat, even though very few applications in the archive use libesd0 anymore. Practically everything was migrated to Gstreamer. I therefore propose that pulseaudio-esound-compat be demoted to Suggests and that libesd0 Depends on pulseaudio-esound-compat | esound. - -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i586) Kernel: Linux 3.2.0-2-486 Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages pulseaudio depends on: ii adduser 3.113+nmu1 ii consolekit 0.4.5-3 ii libasound2 1.0.25-2 ii libasound2-plugins 1.0.25-1 ii libc6 2.13-30 ii libcap2 1:2.22-1 ii libdbus-1-3 1.5.12-1 ii libfftw3-3 3.3-1 ii libice6 2:1.0.8-2 ii libltdl72.4.2-1 ii liborc-0.4-01:0.4.16-1 ii libpulse0 1.1-3+b1 ii libsamplerate0 0.1.8-4 ii libsm6 2:1.2.1-2 ii libsndfile1 1.0.25-4 ii libspeexdsp11.2~rc1-3 ii libtdb1 1.2.9+git20120207-2 ii libudev0175-3.1 ii libx11-62:1.4.4-4 ii libx11-xcb1 2:1.4.4-4 ii libxcb1 1.8.1-1 ii libxtst62:1.2.0-4 ii lsb-base4.1+Debian0 ii udev175-3.1 Versions of packages pulseaudio recommends: ii gstreamer0.10-pulseaudio 0.10.31-2 ii pulseaudio-esound-compat 1.1-3+b1 ii pulseaudio-module-x11 1.1-3+b1 ii rtkit 0.10-2 Versions of packages pulseaudio suggests: ii paman none ii paprefs none ii pavucontrol none ii pavumeter none ii pulseaudio-utils 1.1-3+b1 - -- Configuration Files: /etc/default/pulseaudio changed [not included] /etc/pulse/daemon.conf changed [not included] /etc/pulse/system.pa changed [not included] - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJPokELAAoJEK4fgnfEtNe2LOcP/2s1aj4TiAn1/fkRJdl/Noug yVQe6zV8OosNx9pXaZ8KHknvqNrtft2weXuKvPry83+8cW9PbIHtBcavDZgigNEG psOEfEPRbroQkgvCULb9kedurCQJd9ln3ZEJNVnsCGFuf4rpboXlTCrdEZqrcgDO VmrHaO1RWZNsuvHkXF4lbXB/StAXqtjWSTYqHF0VkeOs+QmtT9xCRvEjZEpTYz+Y 9fos6lMJrm+gNYHsKHFLbxR5sSfpgqewyb9ETWNMOtV0icTjcvpTTfIxSCpsIPxd RrlM4SfzObH4KaqK24hme9mk6yMJgtGr8/n++3eT6MbIHbUPLvcU/AGm2ySvSKY+ TkKxQr/6fKGKSlLNtRJ1gB45YX5gueDk9CdZBOJIYC8c/HScqlT0oxsdE0xxBC0p 80KcQgNb6qsKwhhecppdKC6NiNIA4UE5wqa+gsjf7BRlJIXfZWH9gJ1o2zZLEiI2 5RNLseEhP297XQ8TL6+deSMKfY7C+0z2Jv0hZpNl0MW6zCWnJQorf9C+EeEcZ/B8 s9IKvVLc2v75nVxLziaSkgFFGsbu825CPOmWwOIv+Ljjdx4meo0GTgK7Emov+qKJ ZGUpjMFR8vIjQPX0vm6u/4d4hG/qrJGTF4sSLR9logaezoAKxjv8WqM1psi8AzAP xB/3qf9AvzR7FWgffMgs =1jSs -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671470: pulseaudio: init.d script missing the --disallow-exit option
Package: pulseaudio Version: 1.1-3+b1 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 As reported by syslog whenever running in system mode: May 4 14:04:22 geode pulseaudio[1357]: [pulseaudio] main.c: Running in system mode, but --disallow-exit not set! - -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i586) Kernel: Linux 3.2.0-2-486 Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages pulseaudio depends on: ii adduser 3.113+nmu1 ii consolekit 0.4.5-3 ii libasound2 1.0.25-2 ii libasound2-plugins 1.0.25-1 ii libc6 2.13-30 ii libcap2 1:2.22-1 ii libdbus-1-3 1.5.12-1 ii libfftw3-3 3.3-1 ii libice6 2:1.0.8-2 ii libltdl72.4.2-1 ii liborc-0.4-01:0.4.16-1 ii libpulse0 1.1-3+b1 ii libsamplerate0 0.1.8-4 ii libsm6 2:1.2.1-2 ii libsndfile1 1.0.25-4 ii libspeexdsp11.2~rc1-3 ii libtdb1 1.2.9+git20120207-2 ii libudev0175-3.1 ii libx11-62:1.4.4-4 ii libx11-xcb1 2:1.4.4-4 ii libxcb1 1.8.1-1 ii libxtst62:1.2.0-4 ii lsb-base4.1+Debian0 ii udev175-3.1 Versions of packages pulseaudio recommends: ii gstreamer0.10-pulseaudio 0.10.31-2 ii pulseaudio-esound-compat none ii pulseaudio-module-x11 1.1-3+b1 ii rtkit 0.10-2 Versions of packages pulseaudio suggests: ii paman none ii paprefs none ii pavucontrol none ii pavumeter none ii pulseaudio-utils 1.1-3+b1 - -- Configuration Files: /etc/default/pulseaudio changed [not included] - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJPo7lIAAoJEK4fgnfEtNe2l64QAJe1rQMFJHEg/1AT21RwmUGk P2GPGCn235lbHxcScR1kjU/HT5k5TMb3uprJmOCjKT+CYj6jGktF8rpLJAPQDGgs R1ZLYUPtjkVlMMdYwjkiPVUBpXAG+RDA0OGawK4HL+5QcdfPXVgIneOZsI7rnqH5 evASNKFb+2KIK+ERt7W7d+RyNiNzXlFlUmvbQStgth5zrjWTEcVknl+QAKRMPE2L eW+J+4obhSuVIP/k8u1v9kgKhjHGdnjBTUUUpdq4hvl+ApgA33eZxmYsgGQs4/GN a7IfotpQUqwcUTxGck5TUdaC4oZL7O/n6Fj72Ifg5bcuyJYTK1zYVQZMEgmN+nsx tazOJaP+bfzORBi51LDbcJLzPipNgBFp3AwsekRXxCOgK134JjCgxbvslXNRUKKH drSn0s/Skr6q1ZTyttfjygBhlZr3nWyyt/VanaA3kV1+QwfDTAigki5TmdGCa2QG J3ksq52xbm2rnQinwKa25EATLXjhycj8bmmT5sc8W/vN9E28VVGxOIozTz2GRRcf BbuqFjqInzT2ixGvAsu225OWSF68xgqozVhMHP6DCA2C2h98ZrDqL3DPf0Cpdp0s TtSouoxyB6SAy3Miz4poRlcdGVoEkisdaZVZKcZfzgUkEEbkfwnYDGU7EDILTzRC a7yh0VKAwalOO7R+1kwN =Z44r -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#671471: pulseaudio: /usr/share/alsa/pulse-alsa.conf may be old or corrupted
Package: pulseaudio Version: 1.1-3+b1 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 $ sudo alsamixer -c0 ALSA lib conf.c:1220:(parse_def) show is not a compound ALSA lib conf.c:1686:(snd_config_load1) _toplevel_:24:26:Unexpected char ALSA lib conf.c:3406:(config_file_open) /usr/share/alsa/pulse-alsa.conf may be old or corrupted: consider to remove or fix it $ dpkg -S /usr/share/alsa/pulse-alsa.conf pulseaudio: /usr/share/alsa/pulse-alsa.conf - -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i586) Kernel: Linux 3.2.0-2-486 Locale: LANG=fi_FI.utf8, LC_CTYPE=fi_FI.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages pulseaudio depends on: ii adduser 3.113+nmu1 ii consolekit 0.4.5-3 ii libasound2 1.0.25-2 ii libasound2-plugins 1.0.25-1 ii libc6 2.13-30 ii libcap2 1:2.22-1 ii libdbus-1-3 1.5.12-1 ii libfftw3-3 3.3-1 ii libice6 2:1.0.8-2 ii libltdl72.4.2-1 ii liborc-0.4-01:0.4.16-1 ii libpulse0 1.1-3+b1 ii libsamplerate0 0.1.8-4 ii libsm6 2:1.2.1-2 ii libsndfile1 1.0.25-4 ii libspeexdsp11.2~rc1-3 ii libtdb1 1.2.9+git20120207-2 ii libudev0175-3.1 ii libx11-62:1.4.4-4 ii libx11-xcb1 2:1.4.4-4 ii libxcb1 1.8.1-1 ii libxtst62:1.2.0-4 ii lsb-base4.1+Debian0 ii udev175-3.1 Versions of packages pulseaudio recommends: ii gstreamer0.10-pulseaudio 0.10.31-2 ii pulseaudio-esound-compat none ii pulseaudio-module-x11 1.1-3+b1 ii rtkit 0.10-2 Versions of packages pulseaudio suggests: ii paman none ii paprefs none ii pavucontrol none ii pavumeter none ii pulseaudio-utils 1.1-3+b1 - -- Configuration Files: /etc/default/pulseaudio changed [not included] /etc/init.d/pulseaudio changed [not included] - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJPo7sEAAoJEK4fgnfEtNe2WaIQAIfTcM84SXnO02hIP3aMLtwk tLXKyHqD/TSRlIn9Bcd3hPvxj+JNMtI86/FXw6cOTH44kCpXskxHMMTyDMnEk+RW QH2LhXdr/NsgKqPBNHy+/Ctsmc2pqMZ3Y9JqJw2ws5bQup16HcQ+zgn6r3Xvmpvj uQ/OegECGfqUPySxsdTnWxLPE/07i/5FNh6zMTSHQqBYKbjVhh+eIjEVCbB4xkxe Tbxin5BFRtnazD7sSS1oHuuS5eZwTQnRSZHXCwbnctzvy5qe8eThdNbEMHHCldnL 2uswof66mpPDFfWE0tbOf6QBrhb7sY2XHPO/fSmcI4zwrHjL7fyVdx4sLHzadEiC TXKlitJXcSHcumSZNY8QPxXTCavIDDmmydd35Pbr8gHBZ0JDmVEgDOU7oR7AMMNt wryAjDYHNTuUreigA2skDEd8cO9bHpsd2vpkJiLfKw+SP1882lxKHxP3756ueqp9 ZfhVXIXA0N0H20hFluxF0pQUq294+lfUwgiNiPQvaJmJJ4ceAgKSr2txYWHdPLBa Sx8Ih2VGMrhWWyymxeweAnaa25Zd23oR8l77mANI3LeqOc03GvdaGhR3UCXiWxme cpvUqBSvcdS4HBFNwvAQjsrg2AJ40YAixHaaulpSamlXDk6tVyDxTr2wwsOSpKqP pCiJS2+sW5INFdBbExgh =nZtM -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#644866: maximus: please upgrade source for GTK3 compatibility
Package: maximus Severity: wishlist It would be appreciated to rebuild this package against GTK3. This might require adapting the code for GTK3. This would be highly desirable, now that GTK2-based desktops are being phased out, to allow removing deprecated GTK2 components on a GTK3-based desktop. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.0.0-12-generic (SMP w/1 CPU core) Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages maximus depends on: pn gconf2 none pn libc62.13-21 pn libfakekey0 none pn libgconf2-4 none pn libglib2.0-0 2.28.6-1 pn libgnome2-0 none pn libgnomeui-0 none pn libgtk2.0-0 none pn libunique-1.0-0 none pn libwnck22none pn libx11-6 2:1.4.4-2 pn metacity | x-window-manager none maximus recommends no packages. maximus suggests no packages. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#646113: RM: xserver-xorg-video-amd -- NBS; transitional package
Package: ftp.debian.org Severity: normal Please remove the following transitional packages from unstable: xserver-xorg-video-amd xserver-xorg-video-amd-dbg -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#646114: override: myspell-ru:text/extra
Package: ftp.debian.org Severity: normal rus-ispell (0.99g5-14) unstable; urgency=low * Bumped myspell-ru down to Priority:extra to conform with Policy Section 2.5 Note that optional packages should not conflict with each other. rus-ispell (0.99g5-13) unstable; urgency=low * myspell-ru Conflicts with hunspell-ru (Closes: #644881, #645317). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#647118: override: cupsddk:oldlibs/extra
Package: ftp.debian.org
Severity: normal
Package: cupsddk
Priority: extra
Section: oldlibs
Architecture: all
Depends: ${misc:Depends}, cups-ppdc
Description: Common UNIX Printing System (transitional package)
This is a dummy package to ease transition to new package name.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#653335: buildd.debian.org: [p-a-s] src:xserver-xorg-video-geode from i386 to any-i386
Package: buildd.debian.org Severity: important Since version 2.11.13-1 src:xserver-xorg-video-geode upstream changes should enable the package to build on Architecture: any-i386, thus it is desirable to update P-A-S to enable kfreebsd-i386 and hurd-i386. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#653335: closed by Philipp Kern pk...@debian.org ([p-a-s/sid] xserver-xorg-video-geode: dropped, specifies any-i386 in dsc)
Removing the entry is not what was requested. This package still won't build on anything else than an x86-32. The request was to add non-Linux i386 variants, namely kfreebsd-i386 and hurd-i386, i.e. any-i386. 1. tammikuuta 2012 21.15 Debian Bug Tracking System ow...@bugs.debian.org kirjoitti: This is an automatic notification regarding your Bug report which was filed against the buildd.debian.org package: #653335: buildd.debian.org: [p-a-s] src:xserver-xorg-video-geode from i386 to any-i386 It has been closed by Philipp Kern pk...@debian.org. Their explanation is attached below along with your original report. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact Philipp Kern pk...@debian.org by replying to this email. -- 653335: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=653335 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- Edelleenlähetetty viesti -- From: Philipp Kern pk...@debian.org To: debian-wb-t...@lists.debian.org Cc: Date: Sun, 1 Jan 2012 19:11:35 + Subject: [p-a-s/sid] xserver-xorg-video-geode: dropped, specifies any-i386 in dsc [Debian bug #653335] Signed-off-by: Philipp Kern pk...@debian.org --- Packages-arch-specific | 1 - 1 files changed, 0 insertions(+), 1 deletions(-) diff --git a/Packages-arch-specific b/Packages-arch-specific index 797a947..e4de72f 100644 --- a/Packages-arch-specific +++ b/Packages-arch-specific @@ -307,7 +307,6 @@ zsnes: i386 # Mostly written in i386 assembler %xserver-xorg-video-chips: !s390 !s390x %xserver-xorg-video-cirrus: !s390 !s390x %xserver-xorg-video-fbdev: !s390 !s390x -%xserver-xorg-video-geode: i386 lpia # i386 specific %xserver-xorg-video-glide: !s390 !s390x %xserver-xorg-video-glint: !s390 !s390x %xserver-xorg-video-i128: !s390 !s390x -- 1.7.2.5 -- To UNSUBSCRIBE, email to debian-wb-team-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1rhqpl-0006jh...@grieg.debian.org -- Edelleenlähetetty viesti -- From: Martin-Éric Racine martin-eric.rac...@iki.fi To: Debian Bug Tracking System sub...@bugs.debian.org Cc: Date: Tue, 27 Dec 2011 05:21:45 +0200 Subject: buildd.debian.org: [p-a-s] src:xserver-xorg-video-geode from i386 to any-i386 Package: buildd.debian.org Severity: important Since version 2.11.13-1 src:xserver-xorg-video-geode upstream changes should enable the package to build on Architecture: any-i386, thus it is desirable to update P-A-S to enable kfreebsd-i386 and hurd-i386. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#653335: closed by Philipp Kern pk...@debian.org ([p-a-s/sid] xserver-xorg-video-geode: dropped, specifies any-i386 in dsc)
1. tammikuuta 2012 23.53 Adam D. Barratt a...@adam-barratt.org.uk kirjoitti: On Sun, 2012-01-01 at 23:38 +0200, Martin-Éric Racine wrote: Removing the entry is not what was requested. This package still won't build on anything else than an x86-32. The request was to add non-Linux i386 variants, namely kfreebsd-i386 and hurd-i386, i.e. any-i386. Check the subject of the commit in the closing mail: [p-a-s/sid] xserver-xorg-video-geode: dropped, specifies any-i386 in dsc If the .dsc specifies an accurate architecture list, there's no reason for P-a-s to say anything about the package. In fact, doing so is harmful as it means maintainer changes to the architecture list won't automatically propagate on the buildd side. any-i386 is 1) a policy-compliant architecture specification and 2) not the same as any. Martin-Éric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#653335: closed by Philipp Kern pk...@debian.org ([p-a-s/sid] xserver-xorg-video-geode: dropped, specifies any-i386 in dsc)
1. tammikuuta 2012 23.53 Adam D. Barratt a...@adam-barratt.org.uk kirjoitti: On Sun, 2012-01-01 at 23:38 +0200, Martin-Éric Racine wrote: Removing the entry is not what was requested. This package still won't build on anything else than an x86-32. The request was to add non-Linux i386 variants, namely kfreebsd-i386 and hurd-i386, i.e. any-i386. Check the subject of the commit in the closing mail: [p-a-s/sid] xserver-xorg-video-geode: dropped, specifies any-i386 in dsc If the .dsc specifies an accurate architecture list, there's no reason for P-a-s to say anything about the package. In fact, doing so is harmful as it means maintainer changes to the architecture list won't automatically propagate on the buildd side. Wait... Do you mean that, for as long as the correct architecture is specified in debian/control and, as a result, in the generated .dsc, (in this case, any i386-variant), that no P-A-S entry is needed? Martin-Éric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
