[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#196554: xlibs: todays update causes every app to report "Xlib: connection to ":0.0" refused by server"



* Branden Robinson (branden@debian.org) wrote:

> When I experienced this problem on PowerPC while preparing 4.2.1-7, I
> found that downgrading xserver-xfree86 to 4.2.1-6 but leaving everything
> else at -7 worked, too.
> 
> I don't see why downgrading xlibs-{dev,pic} would help anything at all;
> you should be able to re-upgrade those and not change the way your
> system behaves in this regard.
> 
> Can you confirm these two hypotheses for me?

Well I haven't quit X throughout this process; so I doubt its the
server.

If I do:

apt-get install xlibs=4.2.1-7

I'm back to the situation of being unable to run clients and then if I
do:

apt-get install xlibs=4.2.1-6 xlibs-dev=4.2.1-6 xlibs-pic=4.2.1-6

I can run the clients again.

Note the X server has been running since Saturday morning before I ran
the upgrade that got me 4.2.1-7. Its a kdm session I'm in.

> By the way, the reason this broke is because of GCC 3.3 (read the
> package changelog).  I was hoping they wouldn't get it wrong on i386,
> but I guess I was mistaken.

I guess it could be kdm/the server/the libraries disagreeing and that
its just a matter of the two being the same - so perhaps a new library
would work with a authority file created by a new server/kdm/whatever ?

Dave
 ---------------- Have a happy GNU millennium! ----------------------   
/ Dr. David Alan Gilbert    | Running GNU/Linux on Alpha,68K| Happy  \ 
\ gro.gilbert @ treblig.org | MIPS,x86,ARM,SPARC,PPC & HPPA | In Hex /
 \ _________________________|_____ http://www.treblig.org   |_______/




Reply to: