_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
Versions of packages conky depends on:
ii conky-all 1.10.6-1
conky recommends no packages.
conky suggests no packages.
-- no debconf information
From d3065426868cdf63ccbbaf6afd917de64403
Package: googlecl
Version: 0.9.13-2
Severity: grave
Justification: renders package unusable
Package needs to be updated to use OAuth 2.0...
-- System Information:
Debian Release: 8.0
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Package: udev
Version: 0.125-7
Followup-For: Bug #504928
This bug just bit me on upgraded my laptop to Lenny (snd-maestro3.ko).
It sounded like Marco was going to roll out a fixed version at the end of
December 2008. Is there a problem with the proposed addition of
/lib/firmware/`/bin/uname -r`
Package: recoll
Version: 1.9.0-1
Severity: serious
Justification: no longer builds from source
I was backporting recoll 1.11.0 from sid to etch and found that I needed to
upgrade libxapian to 1.0.7-4 (from backports) to have it build successfully.
Version 0.9.9-1 does not have the
Package: kernel-package
Version: 10.067
Followup-For: Bug #505661
Version 11.0011 of kernel-package needs a build-dep added for po4a 0.31-1.
(Based on a cursory look through po4a's changelog, that looks like the
first version to correctly support the --previous flag.)
FWIW, its possible to
On Fri, 25 Jul 2008, Julien BLACHE wrote:
Glad you narrowed it down. I've been on vacation the last couple of weeks
and had to put it on hold.
Bad:
- I think your patch may be the best option to fix this issue...
- ... but I'm afraid it may be leaking memory
[ . . . ]
Could you rework
On Thu, 10 Jul 2008, Julien BLACHE wrote:
Brad Sawatzky [EMAIL PROTECTED] wrote:
What is the intent of duplicating s-opt into s-local_opt? If it is to
provide a stable local version of the scanner descriptors then shouldn't
Per the SANE standard, the descriptors have to remain
On Thu, 10 Jul 2008, Julien BLACHE wrote:
Brad Sawatzky [EMAIL PROTECTED] wrote:
b) The pointer in the menu.label for the active source menu (in this case)
is not being kept current.
- FIX: Recreate/update the gtk menu and do a panel_rebuild every time
the net backend
On Sun, 22 Jun 2008, Julien BLACHE wrote:
[ . . . ]
Anything in the option descriptor can change after the backend tells
the frontend to reload the options, and I think that's what you're
seeing with gdb when the net backend refreshes the option
descriptors. But the memory allocated by
On Wed, 25 Jun 2008, Julien BLACHE wrote:
Brad Sawatzky [EMAIL PROTECTED] wrote:
Up to that point, you're seeing the preferences loading code setting
options in a loop, resetting the options each time a reload is called
for by the backend, except for the options that caused a reload
On Mon, 30 Jun 2008, Olaf Meeuwissen wrote:
brad sawatzky [EMAIL PROTECTED] writes:
[ . . . ]
Are there technical reasons why the above patches shouldn't be applied?
The fact that these features will be fixed/supported in a future iscan
release is great, but it shouldn't preclude
I took the liberty of CC'ing Carl in this message in case he's interested.
Carl, you can find the rest of the thread at
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=487462
On Fri, 27 Jun 2008, Olaf Meeuwissen wrote:
I'm definitely not in favour of applying the epson4490-fixup.patch.
As
On Sun, 22 Jun 2008, Julien BLACHE wrote:
However I am a bit doubtful as to the origin of the bug. I'd expect
the problem would manifest itself with other backends too.
Yeah, I had though so too...
AFAICT the opt pointer that xsane used was directed into a generic buffer
that sanei_* used for
OK, here's a summarized gdb session. Sorry about the length, I hope it's
useful...
I set a breakpoint on xsane_option_menu_new() and wait for my menu-item of
interest (the source menu which should eventually contain Flatbed and
Transparency Unit) to trigger. When the Flatbed menu item is
Package: xsane
Version: 0.995-3
Severity: normal
Tags: patch
The problem occurs in xsane when accessing an epson/epkowa driver through
the network backend. Trying to change options like binary/gray/color,
resolutions, etc., in xsane results in a dialog box with 'Failed to set
value of option
Package: quiteinsane
Version: 0.10-14
Severity: normal
Epkowa and other Epson scanner backends report a 'Short Resolution list'
option. Quiteinsane displays the option in its 'Advanced Settings' but
does not update the 'Scan resolution' list when it is checked.
-- Brad
-- System Information:
I ran valgrind against the epson.c backend from 1.0.19~cvs20070505-2 and
can confirm that the errors in get_identity_information() are fixed.
-- Brad
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
On Sun, 22 Apr 2007, Julien BLACHE wrote:
Brad Sawatzky [EMAIL PROTECTED] wrote:
[ ... ]
Is it possible for the autoprobed scanner device to be indeterminate? The
I'm not sure what you mean here, could you elaborate ?
See below.
CX6600 is a multifunction printer/scanner unit
On Sat, 21 Apr 2007, Julien BLACHE wrote:
Brad Sawatzky [EMAIL PROTECTED] wrote:
Changing the line to
SUBSYSTEM!=usb_endpoint, GOTO=libsane_rules_end
allows the rule to match and fixes the problem for me.
I assume that this is a change in how kernel 2.6.20.7 reports this device
Package: libsane
Version: 1.0.18-6
Followup-For: Bug #359797
The patch suggested by Henrique causes libsane.rules to fail to match my
scanner (an Epson CX6600). The problem is that udev sees a subsystem class
of usb_endpoint not usb_device so the following line causes the bulk of
libsane.rules
Package: libsane
Version: 1.0.18-6
Severity: normal
Tags: patch
The Epson CX6600 does not share the same idProduct as the CX6400 so the
udev rule that is supposed to match the Epson CX6600 fails.
The information reported by my CX6600 is
idVendor 0x04b8
idProduct
Package: libpam-opie
Version: 0.21-8
Severity: normal
Tags: patch
According to the preamble to opiechallenge() in the libopie source you
MUST call opieverify() to clear the lock and any internal state even if
the challenge fails. This is not done in libpam-opie.
The attached patch fixes this
Package: libpam-opie
Version: 0.21-8
Followup-For: Bug #414015
'libopie/accessfile.c' is not compiled into the pam module so this bug does
not apply here.
The clean target in debian/rules actually does 'rm -rf libopie' before
building libpam_opie.so.
Strange packaging decision.
Note that this
Package: elog
Version: 2.6.3+r1764-1
Severity: minor
Many of the shell variables used in /etc/ini.d/elog are neither unset, nor
initialized to safe/reasonable defaults. At best this is not very robust
and could lead to unintended consequences.
I'd recommend creating '/etc/default/elog' with the
*** Please type your report below this line ***
The chargeStatus flag was being extracted from the APM batteryStatus field
instead of the batteryFlag field. The two fields have virtually the same
structure and the first 4 bits _should_ report the same information, but
they do not.
My bios
On Wed, 14 Feb 2007, Yves-Alexis Perez wrote:
On mer, 2007-02-14 at 16:18 -0500, Brad Sawatzky wrote:
Can the dependence on 'mousepad' (see description below) be removed?
It seems odd that a panel manager would actually require a graphical
text editor...
Well, the dependency (you may
Package: xfce4-panel
Version: 4.3.99.2-2
Severity: minor
Can the dependence on 'mousepad' (see description below) be removed? It
seems odd that a panel manager would actually require a graphical text
editor...
Package: mousepad
Description: simple Xfce oriented text editor
Mousepad
Package: firestarter
Version: 1.0.3-1.3
Severity: normal
The 89.0.0.0/8 net block appears to have been assigned and should be
removed from the '/etc/firestarter/non-routables' table.
(I only noticed this because there appears to be an ntp server on the
debian ntp round-robin in that netblock.)
On Tue, 17 Oct 2006, Kel Modderman wrote:
On Tuesday 17 October 2006 05:23, Moritz Muehlenhoff wrote:
severity 386227 grave
thanks
Package: spca5xx-source
Version: 20060501-1
Severity: important
Tags: patch
[ . . . ]
spca5xx-source has been integrated in
Package: spca5xx-source
Version: 20060501-1
Severity: important
Tags: patch
Some v4l header information got shuffled around in kernel 2.6.18. The
attached patch updates spca5xx.h to include media/v4l2-common.h. Seems
to work after that.
You may want to check to see if the v4l changes came in
Package: shfs-source
Version: 0.35-6
Severity: important
Tags: patch
The module source fails to build with kernel 2.6.18 due to a change in the
get_sb_nodev() calling arguments. The attached patch updates inode.c with
the minor change.
NOTE: The patch doesn't have any kernel-version ifdefs...
Package: python-apt
Followup-For: Bug #381520
Just stumbled across this bug while configuring my new AMD64 machine.
Using several of the 'wajig' commands will trigger the segfault in
TAgFileFree() as Devin reported. (wajig is another debian package
that written in python that integrates many of
Package: python-apt
Followup-For: Bug #381520
Just stumbled across this bug while configuring my new AMD64 machine.
Using several of the 'wajig' commands will trigger the segfault in
TAgFileFree() as Devin reported. (wajig is another debian package
that written in python that integrates many of
On Fri, 13 Jan 2006, Kel Modderman wrote:
michel Xhaard wrote:
Le Vendredi 13 Janvier 2006 05:35, Brad Sawatzky a écrit :
Strange my original spca5xx-20051212 include linux/version.h on top of
the spca50x.h file ?
#ifdef __KERNEL__
#include asm/uaccess.h
#include linux/videodev.h
\
KMAINT=Brad Sawatzky KEMAIL=[EMAIL PROTECTED]
\
KPKG_DEST_DIR=/usr/src/linux-2.6.14.6/.. \
KPKG_MAINTAINER=Brad Sawatzky\
KPKG_EXTRAV_ARG
Package: imms
Version: 2.0.3-2
Severity: grave
Tags: patch,sid
Justification: renders package unusable
immsd will repeatedly segfault as soon as XMMS connects to its socket. The
underlying problem is a bug (feature?) with initstate_r() from
libc6(2.3.5). See also a
36 matches
Mail list logo
