Nifty.
Does glxgears work, or error out with a similar error? [e.g. is this a
problem with fretsonfire on amd64's library path]
- Rich
--
Function reject.
I think libgl1 is the virtual package you want to check the status of.
dpkg -s libgl1
- Rich
--
It is much easier to suggest solutions when you know nothing about the
problem.
Well, I'm on an Ubuntu amd64 system (I'll install a Debian amd64 system if
necessary to poke at this), but I grabbed the Debian FoF package and the
Ubuntu FoF package, and neither of them gave me this error.
A quick round of searching informs me that this error crops up when your
libGL isn't where
Another ping - please?
- Rich
--
Booker's Law: An ounce of application is worth a ton of abstraction.
As far as I can tell, this bug should be closed - lenny currently has
2.6.7.1-1 for all architectures.
Am I missing something? I don't think we're actually waiting on upstream any
more.
- Rich
1.8.6 has been out for some time - is there anything blocking a new package?
:)
- Rich
On Tue, Aug 12, 2008 at 2:47 AM, Luca Bruno <[EMAIL PROTECTED]> wrote:
> Rince scrisse:
>
>> I'll submit the 0.7.0 version of the package for inspection "shortly".
>
> Any news on this? I've seen no change in our repo recently.
> I you don't proceed
On Sun, Jul 20, 2008 at 6:10 PM, David Prévot <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Package: ext3grep
> Version: 0.6.0-1
> Severity: grave
>
> - --- Please enter the report below this line. ---
>
> Hi,
>
> I tried to use ext3grep but I have always the same
Hi,
Rob Weir schrieb am 29. October 2005:
> Do you you think you'll have time to upload this fix soon, or would you
> prefer to have someone NMU it?
Please do an NMU (especially since I thought I orphaned that package
two years ago or longer...
Ciao, Hanno
--
| Hanno Wagner | Member of the H
Package: dvgrab
Version: 1.7-1
Severity: grave
Justification: renders package unusable
When I try to use dvgrab on my amd64-system, I get the following:
[EMAIL PROTECTED](577):~$ dvgrab
Speicherzugriffsfehler
(means Segfault)
with dmesg; I see the following:
ieee1394: Current remote IRM is no
Hi,
Lionel Elie Mamane schrieb am 11. September 2005:
> On Fri, Sep 09, 2005 at 09:53:46PM +0200, Carsten Menke wrote:
>
> > I tested the newer versions today and it seems that problems have
> > gone with the provided versions.
>
> OK, closing bug then. I'd still like a confirmation by Hanno on
Hi,
Steve Langasek schrieb am 25. August 2005:
> Well, it appears to have debugging symbols (i.e., line numbers) for the
> capi4hylafax functions, but it doesn't actually look like it's related
> to the c2faxrecv bug you were reporting...
Better traceback:
(gdb) run
Starting program: /usr/bin/c
Hi,
Steve Langasek schrieb am 24. August 2005:
> > I fear I need the debug-Version of libc, not hylafax.
>
> Why? The backtrace you provided shows the segfault happens in hylafax code,
> not in glibc code.
Okay. I am not good in reading backtraces, but there are a lot of
"empty" lines which I
Hi Steve,
Steve Langasek schrieb am 23. August 2005:
> Could you try rebuilding capi4hylafax with debugging symbols as well
> (setting CXXFLAGS to "-g")? The backtrace you provided is missing the
> information that's needed to pinpoint the bug without being able to
> reproduce it.
I fear I need
Package: capi4hylafax
Version: 1:01.02.03-10
Severity: grave
Justification: renders package unusable
c2faxrecv segfaults when a fax transmission comes in. I use a AVM B1
PCI V4.0-Card. Here are the interesting error messages:
luggage:/var/log# dmesg|grep B1
b1pci: PCI BIOS reports AVM-B1 V4 at i/
15 matches
Mail list logo
