On Jan 19, 2010, at 10:15 AM, Gerfried Fuchs wrote:
Just a special side note: When you use unstable you are expected to
figure out such things because that's what happens regularly in
unstable and you are expected to be able to track down the issue on
your
own. Digging through the buildd log
On Tue, Jan 19, 2010 at 04:15:10PM +0100, Gerfried Fuchs wrote:
> Hi!
>
> * Rick Thomas [2010-01-19 15:00:11 CET]:
> > Interesting... The culprit turned out to be the xserver-xorg-input-wacom
> > driver. At first I removed all the video drivers that weren't mentioned
> > in Xorg.0.log.
Hi!
* Rick Thomas [2010-01-19 15:00:11 CET]:
> Interesting... The culprit turned out to be the xserver-xorg-input-wacom
> driver. At first I removed all the video drivers that weren't mentioned
> in Xorg.0.log. That didn't solve the problem, but made it clear that
> there were still
Michel Dänzer wrote:
On Mon, 2010-01-18 at 23:44 -0500, Rick Thomas wrote:
My question is: How do I know which packages I'm likely to need, so I
can remove the rest?
Something like
grep _drv /var/log/Xorg.0.log|grep -v input
should show you which video driver your X server is using.
Inte
On Jan 19, 2010, at 4:36 AM, Michel Dänzer wrote:
On Mon, 2010-01-18 at 23:44 -0500, Rick Thomas wrote:
My question is: How do I know which packages I'm likely to need,
so I
can remove the rest?
Something like
grep _drv /var/log/Xorg.0.log|grep -v input
should show you which video dri
On Mon, 2010-01-18 at 23:44 -0500, Rick Thomas wrote:
>
> My question is: How do I know which packages I'm likely to need, so I
> can remove the rest?
Something like
grep _drv /var/log/Xorg.0.log|grep -v input
should show you which video driver your X server is using.
--
Earthling Michel
On Jan 18, 2010, at 11:55 AM, Michel Dänzer wrote:
The following packages have unmet dependencies:
xserver-xorg-core: Conflicts: xserver-xorg-input-4 which is a
virtual package.
This means at least one of the xserver-xorg-video-* packages to be
installed hasn't been rebuilt against the new
On Mon, 2010-01-18 at 01:11 -0500, Rick Thomas wrote:
> Does anybody know what's causing this?
>
> Is there anything I can do? It's been a couple of weeks like this.
>
> I understand "Normal Sid churn": Something like this happened on i386
> a while ago and it took over a month to resolve th
Does anybody know what's causing this?
Is there anything I can do? It's been a couple of weeks like this.
I understand "Normal Sid churn": Something like this happened on i386
a while ago and it took over a month to resolve there (I don't know
what happened, but one day it just went away.
9 matches
Mail list logo
