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

Re: xserver-xorg fatal configuration



Tore Ericsson wrote:

>THE problem
>http://lists.debian.org/debian-user/2006/03/msg00604.html
>caused by my stupidness
>http://lists.debian.org/debian-user/2006/03/msg00501.html
>  
>
Okay, I missed this second link, which contains good information, such as:

>The recommendation to run "dpkg-reconfigure xserver-xorg" is not fruitful,
>since such a reconfiguration is not possible:
>root@andromeda:/var/cache/apt/archives# dpkg-reconfigure xserver-xorg
>/usr/sbin/dpkg-reconfigure: xserver-xorg is broken or not fully installed
>DESTROY created new reference to dead object ' Qt::VBoxLayout' during
>global destruction.
>/usr/bin/perl: symbol lookup error: /usr/lib/libkdecore.so.4: undefined
>symbol: _ZN18QMetaObjectCleanUpD1Ev
>
>Another anomaly is that virtually any use of dpkg-reconfigure is
>impossible. This example is "dpkg-reconfigure am-utils":
>(1) from a console:
>root@andromeda:~# dpkg-reconfigure am-utils
>dpkg-reconfigure: cannot connect to X server  # no dialog, nothing done
>(2) from gui terminal:
>root@andromeda:~# dpkg-reconfigure am-utils  # normal configuration dialog
>Stopping automounter: amd . done.
>Starting automounter: amd.
>/usr/bin/perl: symbol lookup error: /usr/lib/libkdecore.so.4: undefined
>symbol: _ZN18QMetaObjectCleanUpD1Ev


Now I see two possible problems: 1) the libkdecore.so.4 file, which I
still suspect, so I really would encourage you to try the things I
suggested earlier which you thought had no bearing on your problem. 2)
Apparently you have your system set up to ask you questions about setup
during installation from an X interface rather than a text interface;
I'd HIGHLY recommend you change that to just using plain old Dialog.
Highly. I would try going into an xterm within X, and as your normal
user who's logged into X, running "sudo dpkg-reconfigure debconf" and
selecting "Dialog". (This assumes you've configured your user to have
sufficient sudo capabilities; if not, you'll have to figure out some
other way to give root access to your X session, such as xhost
<shudder>.) But the more serious problem, from what I can see, is the
libkdecore file.

-- 
Kent



Reply to: