problems with kdelibs3
I currently am running Libranet 1.90, based on Debian Potato It comes with KDE2.1, and I wanted to upgrade to 2.1.1, but ran into difficulty... With apt-get update and apt-get upgrade, I consistently have a large number of KDE packages held back. So I tried to install them using apt-get install I tried to install kdebase-libs it wanted kdelibs3, which I tried to install : manjushri:/home/michael# apt-get install kdelibs3 Reading Package Lists... Done Building Dependency Tree... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. Since you only requested a single operation it is extremely likely that the package is simply not installable and a bug report against that package should be filed. The following information may help to resolve the situation: Sorry, but the following packages have unmet dependencies: kdelibs3: Depends: libssl096 but it is not installable E: Sorry, broken packages So, i tried to apt-get install libssl096- this is what happened: Package libssl096 has no available version, but exists in the database. This typically means that the package was mentioned in a dependency and never uploaded, has been obsoleted or is not available with the contents of sources.list E: Package libssl096 has no installation candidate I'm a Debian newbie... Does this mean there is a problem with the build of a package - perhaps a typo or something? When I check the database of all Debian packages for libssl* I see: Debian package search results Release Quality Package (size) stable 100% libssl09-dev 0.9.4-5 (542.9k) SSL development libraries testing 46% libssl095a 0.9.5a-6 (391.3k) SSL shared libraries (old version) unstable 46% libssl095a 0.9.5a-6 (391.3k) SSL shared libraries (old version) testing 37% libssl-dev 0.9.6-2 (652.6k) SSL development libraries, header files and documentation unstable 37% libssl-dev 0.9.6a-1 (749.5k) SSL development libraries, header files and documentation stable 12% libssl09 0.9.4-5 (350.2k) SSL shared libraries testing 12% libssl09 0.9.4-6 (350.6k) SSL shared libraries (old version) unstable 12% libssl09 0.9.4-6 (350.6k) SSL shared libraries (old version) testing 5% libssl0.9.6 0.9.6-2 (446.4k) SSL shared libraries unstable 5% libssl0.9.6 0.9.6a-1 (451.5k) SSL shared librariesResponses 1-10 shown, out of total of 10.
Re: libqt2-2.3.0-final-2 not compiled with -xft?
On Wed, 18 Apr 2001, Jens Benecke wrote: > On Tue, Apr 17, 2001 at 03:57:07PM -0600, Ivan E. Moore II wrote: > > Just FYI (I haven't followed all of this), in case you are wondering why AA > fonts are not working and are using the NVIDIA drivers. > > NVIDIA drivers claim they can do RENDER, but they can NOT yet do AA fonts. > They just have every app crash or ignore the settings. (At least here.) > Are you sure about that? I'm using the 0.97 drivers and I *think* I have anti-aliasing working. At least $QT_XFT = 1 and the fonts seem to look somewhat better then they did before to my untrained eye. -- Jaldhar H. Vyas <[EMAIL PROTECTED]>
Re: libqt2-2.3.0-final-2 not compiled with -xft?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday 18 April 2001 14:58, Jens Benecke wrote: > > Just FYI (I haven't followed all of this), in case you are wondering why AA > fonts are not working and are using the NVIDIA drivers. > > NVIDIA drivers claim they can do RENDER, but they can NOT yet do AA fonts. > They just have every app crash or ignore the settings. (At least here.) > > NVIDIA has promised improvements for the next driver version. Well, that 'fixes' MY problem... =( When you say next, could you be more specific? I'm using 0.9-796 right now... Thx! - -- Guillermo Castro[EMAIL PROTECTED] eMonterrey Monterrey NL, Mexico Public key: http://wwwkeys.eu.pgp.net:11371/pks/lookup?op=get&search=0x3E28D3B9 -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE63fxwuvZ3Qj4o07kRAnEYAKCBtUI8tmjCiT5HIze8Zh88QtKJVwCgmyz7 OEFLJ3gkJggKIPwkO2Y6hd0= =2jC5 -END PGP SIGNATURE-
Re: Logout Script
On Wed, Apr 18, 2001 at 05:09:10PM +0200, Burkhard Perkens-Golomb wrote: > How can I start a script to read any input before KDE exits? > > Before KDE 2.1 I had this in .xsession: > > , > | > | # Now start KDE > | startkde > | # KDE has finished, start a xterm with a logout script > | xterm -e path_to_logout_script > ` > > When I quit KDE the xterm opens and starts the logout script. This > script can start a backup and reads user input with the "read" > command. Worked quite well in KDE 2.0 but not in 2.1: Now the xterm > pops up but I can't enter any letters, no input in this xterm > possible. > > Is there a clean way to start a logout script when I exit KDE? do the same thing but to /etc/kde2/kde2.sh Ivan -- Ivan E. Moore II [EMAIL PROTECTED] http://snowcrash.tdyc.com GPG KeyID=90BCE0DD GPG Fingerprint=F2FC 69FD 0DA0 4FB8 225E 27B6 7645 8141 90BC E0DD
Logout Script
How can I start a script to read any input before KDE exits? Before KDE 2.1 I had this in .xsession: , | | # Now start KDE | startkde | # KDE has finished, start a xterm with a logout script | xterm -e path_to_logout_script ` When I quit KDE the xterm opens and starts the logout script. This script can start a backup and reads user input with the "read" command. Worked quite well in KDE 2.0 but not in 2.1: Now the xterm pops up but I can't enter any letters, no input in this xterm possible. Is there a clean way to start a logout script when I exit KDE? TIA, Burkhard
Re: kde2.2 alpha
> I was wondering if, as a boon to the kde developers, all "pre-unstable" > snapshots (of kde 2.2alpha specifically) could be built with debugging > support. I've been trying to be a good end user and file bug reports on > crashes and whatnot, but with the binaries stripped, oftentime I know it's > somewhat useless. Of course, once they are rolled into sid/woody/whatever, > they should be stripped again, but at least at this stage, I'd prefer to give > the dev's all the help they can get. And if someone complains that the > alpha-quality pre-unstable packages are too big, well, tough beans :-) Use > the regular stuff, then. Just a thought, I might be missing something > that is obvious to everyone else. It's happened before :-) I understand the desire to help the developers out more..however I use this as my desktop and speed is important to me. :)The current builds of 2.2alpha have the basic debugging turned on and when there are problems that require anything beyond that it doesn't take me long to rebuild a package with --enable-debug...however running my desktop with that would be crazy. Ivan -- Ivan E. Moore II [EMAIL PROTECTED] http://snowcrash.tdyc.com GPG KeyID=90BCE0DD GPG Fingerprint=F2FC 69FD 0DA0 4FB8 225E 27B6 7645 8141 90BC E0DD
