t I thought...
Regards,
Felix
Romain Beauxis wrote:
severity 501820 normal
tag 501820 wontfix
thanks
Le Friday 10 October 2008 19:57:50 Felix Homann, vous avez écrit :
Hi,
Hi !
when fglrx-driver is installed DRI is broken for the open source radeon/ati
driver. Here's an exce
Package: fglrx-driver
Version: 1:8-7-2
Severity: critical
Justification: breaks unrelated software
Hi,
when fglrx-driver is installed DRI is broken for the open source radeon/ati
driver. Here's
an excerpt of glxinfo:
~$ LIBGL_DEBUG=verbose glxinfo
name of display: :0.0
lib
Package: qtiplot
Version: 0.9.4-1
Severity: grave
Justification: renders package unusable
qtiplot currently crashes when trying to plot.
On start, it spits out two warnings:
qtiplot: Symbol `_ZTV9QwtSymbol' has different size in shared
object, consider re-linking
qtiplot:
Package: libginac1.4
Version: 1.4.1-1+b2
Severity: grave
Justification: renders package unusable
Hi,
libcln5 1.2.1-1 renders libginac1.4.1-1+b2 unusable. Linking is not
possible as ld returns:
/usr/lib/gcc/x86_64-linux-gnu/4.2.3/../../../../lib64/libginac.so: undefined
reference to `cln::cl_do
Pierre Habouzit wrote:
it doesn't show changelogs for a package it considers new (as it would
else show YEARS of useless changelogs since it's not really "changes").
So you won't see changelogs for upgrades on your _next_ upgrade of those
packages, only for the one after that.
Thank you very
Pierre Habouzit wrote:
Everything seems to be fine afterwards again.
of course, and you just trashed your whole history with it, nice... or
not.
Well, without knowledge of the intrinsics, I was faced with only 3 options:
1. continue using apt-listchanges but trashing the history
2. remove
Package: apt-listchanges
Version: 2.82
Followup-For: Bug #469221
OK, while you're all apparently busy debating responsibilities, here's
something for those bothered by 'bsddb.db.DBRunRecoveryError' messages:
sudo aptitude purge apt-listchanges
sudo aptitude install apt-listchange
Hi,
searching the web I've found an interesting link with a solution to my
problem:
http://pastebin.ca/644793
The solution is simple but not easy to guess:
Remove all lines containing containing PairModes in /etc/ati/amdpcsdb
and /etc/X11/xorg.conf.
Could you please add a line in
Package: fglrx-driver
Version: 8.38.6-2
Followup-For: Bug #420814
Hi,
although the fglrx-driver issues related to newer versions of
xserver-xorg-core are supposed to be resolved since fglrx-driver 8.37.6-1
it never worked on my system.
I've even already tried version 8.40.4-2 from experimental
ce an email client that can't send or receive emails is completely
useless, I've put severity to grave.
Kind regards,
Felix Homann
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'testing'), (500, 's
Package: powersaved
Version: 0.14.0-6
Severity: critical
Justification: causes serious data loss
On my laptop, when the AC adaptor is unplugged 'powersave -B' reports a
constant battery state (75% charged, 180 minutes left) no matter what the
state according to 'acpi -V' is, it doesn't change a
Package: gnue-appserver
Version: 0.4.3-1
Severity: grave
Justification: renders package unusable
After a fresh install I get this:
Starting gnue-appserver: gnue-appserverTraceback (most recent call
last):
File "/usr/bin/gnue-appserver", line 30, in ?
from gnue.appserver import geasRpcSer
On Tuesday 08 August 2006 04:15, Adeodato Simó wrote:
> * Felix Homann [Wed, 26 Jul 2006 10:12:11 +0200]:
> > On Tuesday 25 July 2006 16:23, Filippo Giunchedi wrote:
> > > okay, I've updated bluetooth.sh and bluez-pcmcia-support.udev again, do
> > > you min
On Tuesday 25 July 2006 16:23, Filippo Giunchedi wrote:
> okay, I've updated bluetooth.sh and bluez-pcmcia-support.udev again, do you
> mind trying if it works as expected?
It works as expected.
> Also can you paste the relevant udev
> database entry for your card?
Here you go:
P: /class/tty
On Tuesday 25 July 2006 17:12, Marcel Holtmann wrote:
> this is nice, but there is no need to run bluetooth.sh on non-serial
> based Bluetooth cards like the Nokia DTL1 for example. They work
> perfectly fine without any additional udev rule.
The rules are essentially taken from SuSE, I don't know
On Tuesday 25 July 2006 13:18, Kay Sievers wrote:
> PHYSDEVPATH and the 'device' link are both deprecated and will go away
> some day in the future, you better pass the values you want to use in
> your script down from udev with $sysfs{}. That is not dependent on a
> specific order of devices in sy
On Tuesday 25 July 2006 11:12, Filippo Giunchedi wrote:
> what about the change from DEVPATH to PHYSDEVPATH Felix proposed in
> bluetooth.sh?
Hi again,
MANFID=`cat /sys/$PHYSDEVPATH/manf_id`","`cat /sys/$PHYSDEVPATH/card_id`
and
MANFID=`cat /sys/$DEVPATH/device/manf_id`","`cat /sys/$DEVPATH/dev
On Tuesday 25 July 2006 11:12, Filippo Giunchedi wrote:
> I've modified the rules file, it is available at
> http://svn.debian.org/wsvn/pkg-bluetooth/bluez-utils/trunk/debian/bluez-pcm
>cia-support.udev?op=file&rev=0&sc=0
>
> and the bluetooth.sh invoked on RUN available at
> http://svn.debian.org/
On Wednesday 19 July 2006 12:00, Filippo Giunchedi wrote:
> [I'm CCing udev maintainer to have some comments (if any)]
>
> On Wed, Jul 19, 2006 at 10:57:04AM +0200, [EMAIL PROTECTED] wrote:
> > The udev rules supplied by the package don't work. At least on my
> > system tested with a SPHINX and a S
Package: wpasupplicant
Version: 0.4.8-4
Severity: critical
Justification: breaks the whole system
I tried upgrading wpasupplicant from 0.4.7-4 to 0.4.8-4 on a remote system
that is connected to the network via a WPA connection using wpa_supplicant.
The system is a "server only" system: It does
20 matches
Mail list logo
