Re: fixed width fonts for konsole
On Mon, Oct 08, 2001 at 11:14:26AM +0100, Giles Constant wrote: > Hi Guys, > > What font is everyone using for konsole when anti-aliased fonts are turned > on? > > The only two that seem to work that I've found are the various forms of > courier and Lucida console, both of which look at best, horrible, and at > worst, unreadable. 'v' and 'V' look rather too similar - I spent nearly 2 > hours trying to debug some python code that was referencing > "cursor.oidValue" instead of "cursor.oidvalue" thanks to that one :-( > > Is there a truetype or type1 equivalent to "fixed/misc" out there? > This may not be exactly what you are looking for but.. Keith Packard has his own web site, www.keithp.com, from there he has various items including some fonts and example Xftconfig's. http://keithp.com/~keithp/fonts If you download the truetype.tar.gz and unpack it to /usr/lib/X11/fonts it will create a subdir truetype, then you can add that to your Xftconfig or $HOME/.xftconfig and XF86Config-4. Then use monotype.com as the fixed width font. Has worked fine for me. -- Gordon Sadler
Re: KDE completely broken?
On Fri, Oct 05, 2001 at 08:03:28PM -0600, David Bishop wrote:
> On Friday 05 October 2001 06:31 pm, Gordon Sadler wrote:
> > On Fri, Oct 05, 2001 at 05:50:25PM -0500, Ben Burton wrote:
> > > So is anyone else finding all of KDE broken after today's upgrade, or is
> > > it just me and my system?
> > >
> > > I'm currently trying to figure out how to use GNOME :) - even from GNOME,
> > > starting kAnything will result in a segfault with no further explanation.
> > >
> > > [EMAIL PROTECTED]:~> konsole
> > > Segmentation fault
> > > [EMAIL PROTECTED]:~> knetload
> > > Segmentation fault
> > > [EMAIL PROTECTED]:~> konqueror
> > > Segmentation fault
> > >
> > > Today's upgrade included the latest X; not sure if that has anything to
> > > do with it.
> > >
> > > Ben.
> >
> > I cannot get startx nor kdm to function correctly.
> >
> > kdm restarts itself after attempting to startkde, and running startx
> > produces the following in my .xsession-errors:
> > /usr/X11R6/lib/X11/xinit/xinitrc: /usr/bin/ssh-agent sh
> > /home/gbsadler/.xsession: No such file or directory
> >
> > ls -la .xsession
> > -rwxr-xr-x1 gbsadler gbsadler 247 Oct 5 19:27 .xsession
> >
> > Hmmm?
>
> Well, kdm broke for me, but startx works. As for your error, it looks like
> it's trying to run something out of your .xsession, not that it can't /find/
> your xsession. Maybe? I dunno, I'm guessing at this point.
>
I've tried chmod -x and +x on .xsession, I put full path to both
executables inside .xsession (/usr/bin/X11/xrdb and
/usr/bin/{startkde,startxfce,wmaker}, and they all return immediately to
console.
However, running xinit followed by startkde in the login screen produced
does work... Ugly but it works for now. Thanks for the help, hope
Branden figures this out soon :)
--
Gordon Sadler
Re: KDE completely broken?
On Fri, Oct 05, 2001 at 05:50:25PM -0500, Ben Burton wrote: > > So is anyone else finding all of KDE broken after today's upgrade, or is > it just me and my system? > > I'm currently trying to figure out how to use GNOME :) - even from GNOME, > starting kAnything will result in a segfault with no further explanation. > > [EMAIL PROTECTED]:~> konsole > Segmentation fault > [EMAIL PROTECTED]:~> knetload > Segmentation fault > [EMAIL PROTECTED]:~> konqueror > Segmentation fault > > Today's upgrade included the latest X; not sure if that has anything to do > with it. > > Ben. > I cannot get startx nor kdm to function correctly. kdm restarts itself after attempting to startkde, and running startx produces the following in my .xsession-errors: /usr/X11R6/lib/X11/xinit/xinitrc: /usr/bin/ssh-agent sh /home/gbsadler/.xsession: No such file or directory ls -la .xsession -rwxr-xr-x1 gbsadler gbsadler 247 Oct 5 19:27 .xsession Hmmm? -- Gordon Sadler
Bug#101055: Simple file segfaults
Package: xlibs
Version: 4.0.3-4
Severity: normal
Compile the attached file with g++ -g -o xft xft.cpp -lqt
Yes, it is involving libqt-dev as such I CC'd debian-kde.
While attempting to determine what was going on, I installed xlibs-dbg,
apt-get source xlibs, pointed gdb at everything, stepped, bt'd, etc..
I even managed to produce a segfault in gdb !!-(
After compiling, this simple file when run produces this BT:
#0 XAddExtension (dpy=0x0) at InitExt.c:80
#1 0x2b2fc048 in _XftDisplayInfoGet (dpy=0x0) at xftdpy.c:75
#2 0x2b2fc0e6 in XftDefaultHasRender (dpy=0x0) at xftdpy.c:99
#3 0x2ac2cf6e in qt_use_xft () from /usr/lib/libqt.so.2
#4 0x804863b in main () at xft.cpp:7
#5 0x2b00b38b in __libc_start_main () from /lib/libc.so.6
After much digging, (I'm new to X source ..), I found it has a problem
with LockDisplay(dpy).
LockDisplay is a macro from xc/lib/X11/Xlibint.h:
#if defined(XTHREADS_WARN) || defined(XTHREADS_FILE_LINE)
#define LockDisplay(d) if ((d)->lock_fns)
(*(d)->lock_fns->lock_display)((d),__FILE__,__LINE__)
...
#else
#define LockDisplay(d) if ((d)->lock_fns)
(*(d)->lock_fns->lock_display)(d)
At this point, I note that dpy is type = struct _XDisplay, and
LockDisplay is called with dpy as the arg from InitExt.c. I used gdb to
(gdb) ptype dpy->lock_fns
type = struct _XLockPtrs {
void (*lock_display)();
void (*unlock_display)();
} *
(gdb) p
Segmentation fault (core dumped)
So there appears to be a problem here... this ^^ is gdb segfaulting..
while trying to debug this simple little program. Anyone have any clues?
*** xft.cpp
#define QT_XFT
#include
#include
int
main ()
{
int x = qt_use_xft ();
return x;
}
-- System Information
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux debian-home 2.2.19 #1 Sat May 19 16:25:04 CDT 2001 i686
Locale: LANG=en_US, LC_CTYPE=en_US
Versions of packages xlibs depends on:
ii libc6 2.2.3-6 GNU C Library: Shared libraries an
ii libfreetype62.0.2.20010514-1 FreeType 2 font engine, shared lib
ii xfree86-common 4.0.3-4 X Window System (XFree86) infrastr
ii xlibs 4.0.3-4 X Window System client libraries
--
Gordon Sadler
Re: apt-get upgrade to KDE 2.1.1 failed for potato-ppc
On Sun, Jun 03, 2001 at 11:29:08PM -0500, Tim Fairbank wrote: > I have a stable Debian 2.2r3 system with KDE 1.1.2 > installed. When I attempted to use the packages from > kde.debian.net to upgrade to KDE 2.1.1, the upgrade failed. > > The issue appears to be a dependency on libmng1, which does > not exist in potato. What's worse, the version of > libmng1 in woody depends on libc6 >= 2.2.2-2, so I > can't just build from source and install by hand. Sure you can. apt-get --build source libmng1 (if you point at unstable) else find libmng sources in the pool pool/main/libm/libmng/libmng_1.0.1-1.diff.gz " " libmng_1.0.1-1.dsc " " libmng_1.0.1.orig.tar.gz download dpkg-source -x libmng_1.0.1-1.dsc cd libmng-1.0.1 fakeroot debian/rules binary cd .. lintian *.deb dpkg -i *.deb > I would need to upgrade the whole system...which I'm > resisting, since it's running perfectly now. > > Here are the details: > Any suggestions? > > -- Gordon Sadler
Re: local KDE programs
On Tue, Jun 05, 2001 at 05:19:18AM +0300, Eray Ozkural (exa) wrote: > Hi Ivan and all, > > Where should we be installing local programs in? I install KDE > programs with --prefix=/usr/local and they don't seem to work > correctly unless I install them under /usr. They will not be > able to access their data files and so forth. How can I install > my local programs under /usr/local and have them work without > such problems? > > The problem so far occured at least with kbiff and ksetiwatch. > They insist on being installed directly in /usr which leaves > a lot of cruft. > Try something like: KDEDIR=/usr:/usr/local prefix=/usr/local or better build/install kde yourself to /usr/local/kde2.x, then just KDEDIR=/usr/local/kde2.x and all of you other kde programs will work fine. -- Gordon Sadler
Re: autoconf2.13 vs. autoconf
On Thu, May 31, 2001 at 07:09:56AM +0800, Debian User wrote: > What's the difference between autoconf2.13 and plain autoconf? The > former is mentioned in the Build-Depends for kdelibs. My version of > plain autoconf is already 2.13. > It's a sid thing. If you are running unstable, autoconf 2.50 recently was released. Due to some changes/compatibility with previous configure.in scripts written for 2.13 there are now two packages for autoconf. If you have autoconf at version 2.13 from potato/woody it should work fine. However, if you have autoconf 2.13 from sid you should upgrade. You'll end up with : autoconf 2.50-6 autoconf2.13 2.13-33 There is a wrapper script so any calls to auto programs invoke the correct version. -- Gordon Sadler
Re: building from CVS
On Tue, May 08, 2001 at 09:44:39PM +0200, Karolina Lindqvist wrote: > When I build from CVS, with the debian rules files, I always get > problems on in debian/rules lines like: > > cp debian/kbm.init.d debian/kdm/etc/init.d/kdm > > The problem is that the destination directory often do > not exists, and thus the cp fails. Do I need a special kind of cp > to build with the debian/rules file, that creates missing > directories, or what is the answer to this riddle? > I don't know what version of debhelper you have, or how current your CVS is, but, above the line that does the cp'ing there is a call to dh_installdirs. There is a debian/kdm.dirs file that will tell dh_installdirs which dirs to create. So it is taken care of. If you have an old debhelper, or maybe you CVS is missing debian/kdm.dirs, this probably won't work correctly. Ivan designs/develops the kde CVS stuff under Sid IIRC. Gordon Sadler
Re: scroll wheel
On Tue, May 08, 2001 at 02:12:33PM -0700, G. L. `Griz' Inabnit wrote: > [...] > And if I don't have a ~/.Xdefaults file?? > Running SID. > [/...] Just make one, simple really. cd vi .Xdefaults [copy/paste resources] save restart X HTH Gordon Sadler
Re: KDE upgrade from potato to Woody
On Mon, May 07, 2001 at 01:34:21AM -0600, Ivan E. Moore II wrote: > Hi, > > > I have potato KDE 2.1.1 and potato X3.3.6. I want AA, an from all > > the posts it seems to me that my best option is to dist-upgrade to > > Woody. > > > > My question is: Do I need to upgrade my KDE as well, and if yes, > > what to put my sources list for this to happen? Here is what i have: > > > > ftp://ftp.linux.ee/pub/kde.tdyc.com/debian potato main crypto > > > > ftp://ftp.uk.debian.org/debian stable main contrib non-free > > > > Do I just have to change potato to woody, and stable to unstable? > > Is this correct? > > If you are planning on completely upgrading to woody then all you have to > do is remove the kde.tdyc.com lines from your sources.list file. KDE is > in woody so the packages will be upgraded as well. > Don't forget to change: ftp://ftp.uk.debian.org/debian stable main contrib non-free to ftp://ftp.uk.debian.org/debian testing main contrib non-free as well. Gordon Sadler
Re: X startup
On Sun, May 06, 2001 at 08:42:26PM -0400, Darkhaven wrote:
> From: Darkhaven <[EMAIL PROTECTED]>
> To:
> Subject: X startup
>
> when i installed debian, i didn't install x on it and it booted just fine into
> the console. however, i installed x about a week later and it automatically
> starts up. obviously the X group, or the X mantainer (or it could be a part of
> kde, but i doubt it) wanted it to have more the look and feel of M$ windows
> when
> X is installed (which isn't really bad by itself) however, i just don't like
> it.
> sometimes i don't want to use X. however, it still starts up and does nothing
> more than take up memory.
>
> my causin's solution to this was to mess with some script and make it so that
> X
> crashed when it was started on startup. then when he wanted to use it just
> type
> startx. however, i was looking to do thist the "debian way". i was wondering
> if
> there was an easy way to do this, or what is the proper way to make X not
> start
> on bootup (without making it crash :-) ).
>
> i have X, kde, twm, and some gnome libraries installed.
>
> any help would be appreciated.
>
Somehow, probably via a task package, you installed one of these: xdm,
gdm, kdm, or another display manager. When installed they cause X to be
started on boot. The best/simplest answer is to find the one you
installed and remove it.
If you want it installed... but not started automatically, you may have
to adjust /etc/inittab or /etc/init.d/{g,k,x}dm to have it only start at
certain run-levels.
Gordon Sadler
Re: scroll wheel
On Sun, May 06, 2001 at 05:29:05PM -0500, James Smith wrote: > From: James Smith <[EMAIL PROTECTED]> > To: debian-kde@lists.debian.org > Subject: scroll wheel > X-Mailer: KMail [version 1.2] > > Does anyone know of a way to get a scroll wheel on a mouse working in KDE > without using an external program like imwheel? > With X4.x.x as long as you use the proper protocol for you mouse, and number of buttons (wheel up/down count as one button each), it works out of the box. That said, some apps require special resources to work, notably netscape. You can find the resources with google.com; sth like 'wheel mouse netscape' If you still have X3.3.x, without imwheel I beleive you have to explicitly set resources for all/most apps. I never got anything besides netscape to scroll with X3.x.x and never ran KDE at all under X3.x.x. HTH Gordon Sadler
Re: AA with potato (strictly)
On Sun, May 06, 2001 at 04:15:24PM +0200, Jens Benecke wrote: > To: debian-user@lists.debian.org, debian-kde@lists.debian.org > Subject: Re: AA with potato (strictly) > Mail-Followup-To: debian-user@lists.debian.org, debian-kde@lists.debian.org > From: Jens Benecke <[EMAIL PROTECTED]> > > On Sun, May 06, 2001 at 01:43:37PM +0100, Viktor Lakics wrote: > > Hi All, > > > I think I need the following steps: > > > > I need to get XFree 4.02 or 4.03 > > I already have the right qt version > > My card is OK (NVIDIA TNT2 M64 - it does the antialiasing under > > Mandrake) > > You can only do antialiasing if you do NOT use the NVIDIA drivers (the > commercial ones). They cannot do it yet. > > XFree86 4.0x should be in woody, so either you point your sources.list to > the unofficial sources, or try upgrading to woody (aka "testing"). > Before you leap in ... X4.0.2 is ok IIRC, but X4.0.3-1 is not. You would need X4.0.3-2 to be safe with X. Also if you are using libqt from kde.tdyc.com for potato, IIRC that won't work as Ivan isn't backporting X for potato -). You'll need libqt from woody/sid. Gordon Sadler
Re: KDE 2.1.1 + XFree86 4.0.3 + Matrox G450
On Sat, Apr 28, 2001 at 12:46:34PM -0700, Frankie Fong wrote: > From: "Frankie Fong" <[EMAIL PROTECTED]> > To: debian-kde@lists.debian.org > Subject: KDE 2.1.1 + XFree86 4.0.3 + Matrox G450 > > Hello everyone, > > I have a situation where I wonder if anybody experienced: > > I have a Debian 2.2r2 distribution installed. > I have XFree86 4.0.3 installed from source (built together with > the latest Matrox G450 driver) > > X works fine with twm as window manager. > > then I installed the KDE2.2.1 binary deb packages: > KDElibs3 > KDEbase > > successfully after I resolved the dependencies which > include the following packages: > XFree86 3.3.6, qt 2.3.0, > libssl096 -> libc6 2.2.2.4 -> libdb2.7.7-7 > > they all installed successfully. > > in order to rebuild my XFree86 4.0.3 after the libc6 update, > i installed libc6-dev 2.2.2.4. > > X worked fine after the upgrade (with twm). > > then I modified my .xinitrc script to run 'startkde' > instead of the 'twm' stuff. > > startx > > after some blinking and flashing of the screen, x dies. > > strangely enough, when i compared the /var/log/XFree86.0.log > of my successful twm start and my failed kde start, they > are both the same. > > I am hoping for someone who could point me to somewhere else > inside the system where i could find some KDE/X error messages. > I had this happen more times than I care to admit.. turns out some of the fonts I copied from another OS (M$) weren't up to snuff. They caused all sorts of problems, from X crashing back to desktop ( on startup, trying to use xfontsel, trying to change fonts in konsole, but not control-center -- I had to pick a certain font or 2 to crash there). Oh, my solution here, remove the other fonts, since then, no problems. As I recall, the ssh problem from another response provides an error message when X fails to start. Something about wrong protocol? I posted it to debian-x the day libssl0.9.6a came out.. Good luck Gordon Sadler
Re: Long application startup time
On Mon, Apr 23, 2001 at 06:31:42PM +0200, Jens Benecke wrote: > Hi, > > I wonder if any of you have the same problem (perhaps on comparable > hardware: AMD K6-2 500, 192 MB RAM, SCSI hard disks, /home via NFS). > > When I run KDE, *every* *single* *applicaion* (be it xterm, konsole, > konqueror, or whatever) needs at least 3-5 seconds MORE time to start up > than with e.g. IceWM. > > I.e. I type Alt-F2 + "xterm". CPU jumps to 100%. 3 seconds nothing happens. > then xterm pops up and CPU goes down. > > I type "alt F2" and e.g. "gg:foobar". Sometimes >10 seconds elapse before a > konqueror window pops up and shows me the results. > > > Does anybody have a similar problem here? > Celeron 300a, 128 MB, mix SCSI/IDE HDs. All local, no NFS.. Bit pokier than your setup. -) You don't say which version KDE you are running or Debian? stable/testing/unstable --- KDE 2.[01].[01]/CVS I've got Ivan's most recent CVS snapshot debs here, with Debian unstable. Over the past few months at various times with local CVS builds and Ivan's FAST updated debs, I've experienced your problem. It always seems to go away with new packages or another CVS pull. Another possibility, maybe NFS is causing your problems? Gordon Sadler
kdelibs-dev uninstallable ... docbook-utils
Since you added this dependency in CVS to Build-Depend.. and now it shows up as a Depend for kdelibs-dev, I've been looking for it in incoming. It's not to be found. Did you make a local package of this? Do we really need it ? It's the kde-docbook stuff I assume, the 'jw' wrapper script? I thought I recall seeing on kde-devel that it was deprecated with the xml helpslave? Of course, I can't get that to work either.. but it is alpha -). Gordon Sadler
khelpcenter and docbook
To anyone using Ivan's 2.2alpha debs or self-compiling... Has anyone anywhere been able to get khelpcenter to read the docbook documentation? There is one person who brought this up on kde-devel, I believe S. Kulow responded saying first it was a known issue.. but that was a while back. No amount of debugging this kio_helpslave gets me anywhere. I've self-compiled with --enable-debug , produces 0 extra info inside .xsession-errors. My system is updated daily from Debian unstable, with Branden's X4.0.3pre debs, and Ivan's kde 2.2alpha. Gordon Sadler
Re: KDESupport Debian Package
On Thu, Apr 19, 2001 at 03:11:40PM +0200, Daniel @ E-TREE wrote: > Excuse my simple (or probably stupid) question. > > In the "Installation Istructions" of KDE is explained that the KDESupport > Package is required for Debian distribution. > > But I can't find the package with that name. Is it a common name to call a > group of base (gif, jpg, mime..etc) libraries? Or it exist? > > Btw I did an installation of KDE tryin' every package module dependecies > specify, but it doesn't sound as linear as explained in the istructions. > Debian's package of kdesuport results in two debs. libmimelib1 and libmimelib-dev. grep-available kdesupport shows them as kdesupport is the Source name. Don't try to follow kde.org directions if you are installing debs. If you really don't know which packages you want, try task-kde... If you use dselect, after choosing the task you can then resolve dependencies, by removing the task and any unwanted depends of the task. Gordon Sadler
Re: problems with kdelibs3
On Wed, Apr 18, 2001 at 11:00:29PM -0500, Michael Sullivan wrote: > 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 > Here's your main problem... kdelibs3 from Ivan (Debian maintainer) is not and will not depend on libssl. libssl is non-US, to provide that he packages kdelibs3-crypto and kdebase-crypto. Something must be off with your /etc/apt/sources.list. The kdelibs3 you are trying to install here is not from Debian. > > > 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 > HTH Gordon Sadler
Re: kde man pages
On Sun, Apr 15, 2001 at 10:29:57PM -0600, David Bishop wrote: > Okay, so I've got artsc-config, artsd, artscat, and artsdsp done. However, > I'm stuck on artsplay. What does it do, exactly? There is no documentation > on it (duh) and afaict, it doesn't support any sort of commandline help > switch (--help, -h, -?, and --h don't work). Using a google search, I > figured out that it can play wav files, however, is that all it does? I.e., > is it just a drop-in replacement for the "play" command? If so, I can whip > up a man page saying so, but if it supports multlpe input formats, I'd like > to know :-) Probably the best thing would be a link to any existing > documentation, or a definitive answer. Any help appreciated! Thanks! > According to kdelibs/arts/soundserver/*: artsplay creates a SimpleSoundServer, which has a plugin? architecture. Currently there is a WavPlayObject.mcopclass to allow for playing wav files. Other file extensions can be added to the architecture by creating the appropriate mcopclasses? That's my quick understanding from the code... [EMAIL PROTECTED] would most likely be a really good source for some of this as well. After all the implementers/maintainers spend a good deal of online time there. Gordon Sadler
Re: KDE 2.2 pre-alpha1 test packages available for sid/unstable
On Thu, Apr 12, 2001 at 08:46:32PM -0500, Gordon Sadler wrote: > On Thu, Apr 12, 2001 at 05:53:14PM -0600, Ivan E. Moore II wrote: > > Ok folks... > I currently don't run any databases on my local machine, not too keen on > having to install 2 different db libs. > Rather not respond to self but... Those 2 db libs, postgresql and mysql, would be in addition to libdb2 libdb3 and gdbm that I already have for various other packages... OT: Wouldn't it be nice if more packages could be made available/use different database formats so we wouldn't have to have so many different ones installed? -) Gordon Sadler
Re: KDE 2.2 pre-alpha1 test packages available for sid/unstable
On Thu, Apr 12, 2001 at 05:53:14PM -0600, Ivan E. Moore II wrote: > Ok folks... > > I have prepared a set of test pacakges for the upcomming KDE 2.2-alpha1 > release. You can add the following apt line: > > deb http://people.debian.org/%7Erkrusty/ kde2.2/$(ARCH)/ > > you *must* be using Branden's new X4.0.3 packages which you can get from: > > deb http://people.debian.org/%7Ebranden/ woody/$(ARCH)/ > > The new qt packages I built with the new X4.0.3 packages are also in the > above url... Report bugs to the debian-kde@lists.debian.org mailing list > and *NOT* to the Debian BTS. > > Again, these are test packages... KDE 2.2-alpha1 has not been released yet and > these do not reflect the final state of 2.2-alpha1. The main purpose of these > packages are to work out packaging issues, allow for other packagers to test > build their packages against the new libs, testers to test the new features, > bug squashers to find and help fix bugs, and for the criminally insane who > like > to run pre-alpha software. > > There is no guarentee that these will even work...and my response will most > likely be "It works for me..." :) > [EMAIL PROTECTED]:~/cvs/kdelibs$ sudo apt-get install kdebase Reading Package Lists... Done Building Dependency Tree... Done The following extra packages will be installed: kdebase-libs libcdparanoia0 libkonq-dev libkonq3 libogg0 libvorbis0 The following NEW packages will be installed: libcdparanoia0 libogg0 libvorbis0 4 packages upgraded, 3 newly installed, 0 to remove and 15 not upgraded. Need to get 8281kB of archives. After unpacking 893kB will be freed. Do you want to continue? [Y/n] n Abort. [EMAIL PROTECTED]:~/cvs/kdelibs$ sudo apt-get install kdelibs3 Reading Package Lists... Done Building Dependency Tree... Done The following extra packages will be installed: libmysqlclient10 libpgsql2.1 mysql-common The following NEW packages will be installed: libmysqlclient10 libpgsql2.1 mysql-common 1 packages upgraded, 3 newly installed, 0 to remove and 18 not upgraded. Need to get 6679kB of archives. After unpacking 2179kB will be used. Do you want to continue? [Y/n] n Abort. As the cd,ogg,vorbis libs are fairly small, I probably won't/shouldn't grip about them... However, can you either Suggest/Recommend the 2 different database libs, or split out the offending plugins? I currently don't run any databases on my local machine, not too keen on having to install 2 different db libs. Gordon Sadler
Re: call for help with man pages
On Thu, Apr 12, 2001 at 03:50:48PM -0600, Ivan E. Moore II wrote: > Ok...so as I work on these 2.2 packages one of the policy bits that is still > yet to be dealt with is man pages. According to policy every binary must > have a manpage. (even if there is a common one which others link to) Well > KDE doesn't do man pages...they do docbook...so I need help. > > soo... anyone willing to help create a man page for every binary even some > common man pages. IMO all that is really needed in these are: > >1: basic description >2: pointers to full documentation >3: copyright info (basic..it's GPL'd and the authors are... type of info) >4: command line info if available > > I'm looking at this for the 2.2 release so we will need to work off the > 2.2 packages and binaries. There are several tools which can help with > this... > take a look at all the docbook* packages and there are also man page editors > now. > I started to do something with this a couple of months ago. Basically I used help2man, slightly modified as it wants --help but the kde binaries respond to -help... Hmm... maybe one? common manpage for each upstream source package, ie kdelibs, kdebase, kdegraphics, list the binaries provided by the source package and point to /usr/share/doc/kde/HTML/$pkg? Then use 100's of symlinks? Or do you think more fine-grained detail? Gordon Sadler
KDE2.2 - was version of QT - was OpenSSL 0.9.6a breaks X?
Ivan just a small notice. In CVS (HEAD) kdelibs/debian/control, I believe you should add flex to Build-Depends. In CVS (HEAD) kdebase/debian/control, I believe you should add binutils-dev to Build-Depends. Unless .. one of the changes was using ansidecl.h from binutils-dev, but I think I saw a commit that may have removed it. I can't seem to find the file now, this may be not needed. Also kdebase, or wherever you put the new kioslave/help stuff should depend on python(-base?). Gordon Sadler
Re: kdebase: please remove dependency on klisa
On Mon, Apr 09, 2001 at 01:10:34PM -0600, Ivan E. Moore II wrote: > On Mon, Apr 09, 2001 at 08:55:59PM +0200, Tomas Pospisek wrote: > > Package: kdebase > > Version: 4:2.1.1-0.potato3.1 > > Severity: wishlist > > > > I *don't* want to run any service as klisa on my machine, so I am asking > > to please change the dependency from recommends to suggests, so that > > dselect is not bugging me all the time. > > In future releases it will be a suggests...tho I really hate that idea. > > I think it's STUPID that I have to remove a recommend when my intention > is to recommend.WTF do we have recommends for if users just want them > removed all the time. > I would say, leave recommends as is. If a user is using dselect, either they know how to resolve dependencies by hand... or they are the type who just wants it to work out-of-the-box. If they are using apt from the commandline, they might be prepared to deal with suggests/recommends by hand. > > PS: Is this the right place for sending in kde-*potato* bugreports? > > yes > > > PS: I originaly thought theses packages were coming from KDE, but the > > bugreport was bounced there. Does anybody know whether there was an > > agreement on the package origin field in the control file? I keep > > mixing up the respective bugtracking sites/systems... > > dunno > Gordon Sadler
Re: Yet Another Font Problem...
On Sat, Apr 07, 2001 at 01:25:53AM +0200, Joe Blow wrote:
> I've got a problem with KDE 2.1.1 on Sid (surprise ! :-) Judging from
> the number of font-related messages on this list, I'm not the first...
> Anyway, I crafted through the January to April archive without finding
> something that looks like my problem. So I subscribed and here I am,
> with a new hope ;-)
>
> Here's the problem: KDE displays all my fonts (at least it displays
> their _names_ in the font selection widgets), but they are all rendered
> identically (they look as Helvetica, with the rare exception of
> misc-fixed, which is rendered correctly). No matter which font I
> choose, I end up with helvetica! I tried turning off AA in the Control
> Center, switching from xfs to xfs-xtt, disabling the font server and
> using the FontPath directives, rebuilding the fonts.(dir|alias) files,
> using that good ol' `xset fp rehash', removing my ~/.kde, etc., to no
> avail :(
>
> I did found a bug like this one in the KDE bug database (bug #18876),
> but it has been closed by the maintainer, because it was caused by a
> misconfigured X, according to him. But only KDE applications are
> affected by this problem. Firing up The GIMP or Mozilla shows that the
> fonts are indeed correctly displayed. I can't figure out the source of
> the problem. For reference, here is my font catalogue:
>
> catalogue = /usr/lib/X11/fonts/75dpi,
> /usr/lib/X11/fonts/100dpi,
> /usr/lib/X11/fonts/misc,
> /usr/lib/X11/fonts/Speedo,
> /usr/lib/X11/fonts/TrueType,
> /usr/lib/X11/fonts/Type1,
> /usr/share/fonts/truetype
>
> If someone had an idea about what I should do, where I should search,
> or even a `` You suck, the solution is explained in that file or at
> that URL '', I would be very happy. BTW, my mileage did vary with the
> different upgrades, one of them worked perfectly (it's a pity I cannot
> remember what version it was :( except for Konqueror that seems so
> broken it cannot display anything but helvetica. Too bad because KDE is
> great but in such conditions, it's unusable...
>
> Hope someone has the solution.
>
qt-fonts-HOWTO.html
XftConfig.example
both files should have come installed with either konsole or konqueror
or kdebase itself. (ie /usr/share/doc/{kdebase,konsole,konqueror})
The important thing to remember, font servers play 0 role in this, it is
all controlled by /etc/X11/XftConfig and ~/.xftconfig, as far as AA
fonts go.
HTH
Gordon Sadler
Re: Help! kdm loops
On Tue, Apr 03, 2001 at 09:31:27PM +, Victor wrote:
> Both the daemon.log and syslog reports the same poor message when I start kdm
> (kdm start -debug 1):
> kdm[683]: Display :0 is being disabled (exit frequency too high)
>
In your original message you state, you copied a working config from a
laptop to your desktop.
That along with the above error, implies you did not configure it for
you desktop, you need to ensure your video card/monitor are set properly
in /etc/X11/XF86Config{-4}.
I don't recall you mentioning if this is X3.3.xx or X4.x.x?
Gordon Sadler
Re: KDE install from a directory
On Sat, Mar 31, 2001 at 11:20:21PM +, Viktor Lakics wrote: > I am new to Debian. Just installed potato, and want to put KDE2.1. I > have all the KDE deb packages from kde.debian.net in a directory > /data/KDE. > > How should I put this path into my /etc/apt/sources.list for > installing KDE from there (and not directly from the internet)? > > I want to do "apt-get install kdebase task-kde" to do this... > > Thanks in advance. -- Viktor > Apparently you have root, so... don't mess with apt if you already have them downloaded, and don't intend to setup a private mirror. Simple answer, use dpkg -i $PATH_TO_DEBS/$DEB_NAME_IN_FULL HTH Gordon Sadler
Re: kdeinit shared libraries
On Sun, Mar 25, 2001 at 12:39:30AM +0100, Michal Kulakowski wrote: > On friday, 23 March I downloaded the most fresh release from tdyc, installed > it and everything was OK till the first reboot. KDE isn't starting up no more. > I've traced the problem and got : > > undefined symbol : lt_dlopen_flag (/usr/bin/kdeinit) > > from kdeinit included in kdelibs3_2.1.0.1-0.potato5_i386.deb > > My ld.so isn't pure Debian, as I remember i compiled the latest release from > freshmeat, I use libc6_2.2.2-1_i386.deb. The other stuff that may be related > is left unchanged (potato) > > What's the problem ? > What have I screwed up ? > What libs should I get to make it finally working ? > Not running potato myself, but I notice you say libc6_2.2.2-1? From unstable? Ivan has mentioned a few times that the official/sid debs of kde should actually be more stable than the backports for potato. So... if you are already running libc6 from unstable, maybe you could just point at sid for your kde debs as well? Gordon Sadler
Re: [lars@trolltech.com: fonts HOWTO for Qt/X11]
On a related note, to those interested in this topic... I've seen some question if/where .xftconfig and /etc/X11/Xftconfig is documented. If you have xlibs-dev installed it's Xft(3x). HTH Gordon Sadler
[lars@trolltech.com: fonts HOWTO for Qt/X11]
Seeing as I track both kde-devel and debian-kde, this might interest quite a few debainers as well. Ivan, maybe you could add this URI to ... kdelibs3/README.Debian? or maybe seeing as how konsole seems to be a major culprit, make a new konsole/README.Debian with this URI at least as a where to look for more info re: AA fonts, KDE, QT, and/or konsole? - Forwarded message from Lars Knoll <[EMAIL PROTECTED]> - Resent-Date: 9 Mar 2001 19:45:21 - Resent-Message-ID: <[EMAIL PROTECTED]> Resent-Cc: recipient list not shown: ; Delivered-To: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] From: Lars Knoll <[EMAIL PROTECTED]> Organization: Troll Tech AS To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: fonts HOWTO for Qt/X11 Date: Fri, 9 Mar 2001 20:42:04 +0100 X-Mailer: KMail [version 1.2] X-Spam-Rating: max.tat.physik.uni-tuebingen.de 0/1000/N Resent-Sender: [EMAIL PROTECTED] Resent-From: [EMAIL PROTECTED] X-Mailing-List: <[EMAIL PROTECTED]> Errors-To: [EMAIL PROTECTED] X-BeenThere: [EMAIL PROTECTED] X-Mailman-Version: 2.0beta4 Precedence: bulk Reply-To: [EMAIL PROTECTED] List-Id: KDE's core development crew X-RCPT-TO: <[EMAIL PROTECTED]> X-UIDL: 279714470 Hi, due to the vast amounts of questions I got lately, I finally took myself an hour and tried to write a small HOWTO covering the most important aspects of how to install and use good looking fonts on X11 with Qt. It is still not 100% complete, but should be a good start for the poeple asking themselves on how to get Xft working, how to get the nice screen fonts they have embedded into the postscript Qt generates or just how to get good looking fonts at all from the web and how to install them. You can find the howto at http://trolls.troll.no/~lars/fonts/qt-fonts-HOWTO.html Enjoy, Lars - End forwarded message -
Re: Which KDE source
Questions which source for kde development should be used, kde tarballs, Ivan's tarballs or something else? Complains about two specific packages, namely kvirc and kwintv. No expert here, but your best bet IMO is to stick with Ivan's sources. The release that just occurred of KDE 2.1 had a few 'packaging' problems initially. They had to tag and retag and branch the CVS tree a few times. Ivan stays pretty much on top of things. Of course, if you really want the whole truth and nothing but, you can track CVS too. On to the packages. I have no idea how either on works or was developed, I just went to their respective webpages after reading your post. 1. kvirc, something amiss with it's tarball. It is missing admin/macros/find-dl.m4.in. Which leads to it not having a proper check for dlopen, which leads to no support for plugins, which leads to ... kvi_dlgoptions.cpp includes kvi_frame.h for the proper definition of kvi_frame, HOWEVER, it is surrounded by #ifdef PLUGIN_SUPPORT #endif. Follow? As a work around either define the appropriate pre-processor symbol (ie HAVE_SS_PLUGIN_SUPPORT or something close) or remove the #ifdef #endif so it will unconditionally include kvi_frame.h. That MAY lead to other problems, but this is a problem with kvirc, not Ivan or KDE or Debian... 2. kwintv, I downloaded as well, sorry didn't spend the time here. Could be a very similar problem. Suggest you look at the source. Good Luck Gordon Sadler
Re: problem starting kde
On Sun, Feb 25, 2001 at 07:01:31PM +0100, Etienne Gos wrote: > Bonjour > I have a problem starting kde. > I installed task-kde with dselect from http://kde.tdyc.com/debian potato > main crypto optional > Everything seems to be ok. > But once I start (debian panel with blue background), login user, chose > kde2, password, there is a problem: the kde2 window doesn't open > correctly, just a blue window with a little window where I can tape > orders. > > I looked around, and found out that: > task-kde ist not correctly installed: > # dpkg -s task-kde > Package: task-kde > Status: install ok not-installed > > # apt-get install task-kde > Sorry but the following packages have unmet dependencies > task-kde: Depends: kdebase but it is not going to be installed > Depends: kivio but it is not going to be installed > E: Sorry, broken packages > > # apt-get install kdebase > Sorry but the following packages have unmet dependencies > kdebase: Depends: libgl1 but it is not installable > E: Sorry, broken packages > Here's a good place for a problem. libgl1 is a virtual package, it is declared 'Provides: libgl1' by others, xlibmesa mesag3 to name a couple. Try something like: apt-cache search libgl1, or grep-available -F Provides libgl1 -s Package Then determine which you want/need apt-get install it then apt-get upgrade. > # apt-get install kivio > Sorry but the following packages have unmet dependencies > kivio: Depends: libggi2 (> 1:1.99.2.0b2.1) but it is not installable > Depends: libgii0 (> 1:0.6) but it is not installable > Depends: libgl1 but it is not installable > E: Sorry, broken packages > > I tried to reinstall with dselect, but it did not change anything. > > Is there a link between my problem to start kde2 and this broken > packages? And what can I do? > Thanks in advance > Etienne Gos > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > >
Re: alittle help...
On Sun, Feb 11, 2001 at 01:10:06PM -0500, Dale Kosan wrote: > Hello, I want to install KDE2.1 on my Potato box, I know what to add to my > source list, could some one be nice enough to tell me what commands to use to > upgrade? Thanks in advance. > Try the following : apt-get update apt-get upgrade (might need apt-get dist-upgrade) This is all after adding appropriate lines to your sources.list. During the upgrade command, carefully read what it says, it might want to remove or have problems adding some things. If so that is probably a bug.. but watch it just in case. Gordon Sadler
Re: HOWTO make debs out of kde source packages
On Fri, Feb 09, 2001 at 05:50:34PM +0100, Daniel de los Reyes wrote: > So, today I came across this nice app, called Cervisia which buids against qt > 2 and kde2. No deb packages avaliable, neither in stable, testing or unstable > (anybody know why? No one is interested ? It looks like a very nice app.. Any > licence problem? ). > So here I go to make a deb package out of 1.0 version of Cervisia. > I have had a little experience using dh_make but that doesn't seem to be > enough to build a kde package. I remember reading something in this list > about some scripts beeing developed to ease the making of such packages. > Sorry for my ignorance about all this. > Could someone give me some gidelines on how to get going with this? is there > a HOWTO anywhere? > Ivan, I know a little push from you will get me going a long way ahead ;-) Cervisia contains a deb directory in the CVS tree. It works 'almost' flawlessly. The original parts appear to be from Ivan, then the upstream asked for Ivan's debian dir files, incorporated them into CVS and makes some updates to them at times. I think I only needed to make small adjustments to debian/kderules and debian/rules to build a lintian clean package. HTH Gordon Sadler
Re: Might need to adjust libqt2.2 2.2.4
On Thu, Feb 08, 2001 at 12:24:08PM -0700, Ivan E. Moore II wrote: > this is very strange. qlistview.h is (first off) in the -dev package...and > (secondly) wasn't in /usr/lib/qt2/ . > > > Maybe libqt2.2 2.2.4 should conflict with all the kapps compiled with > > libqt2.2 << 2.2.4? > > > > Just a thought/observance from here. > > Here's the thing...all of the files that were in libqt2.2 before are in > the same location ( minus also being in /usr/lib/qt2/lib) So the only > problems > that the difference in packaging would cause is if the application hardcoded > it's link to /usr/lib/qt2/lib/libqt.so.2 which is against policy. Sorry about that, I might have been jumping to false conclusions. But note I didn't say it was a 'bug' -) I wasn't positive what all I had running. Turns out I had qt2.2.4 with mismatched kdelibs kdebase. kdelibs were local builds from very recent, while kdebase was from official Debian sid. Most likely it was something I messed with in the build. I reverted back to 'official' debs from sid, all working just great with qt2.2.4. My mistake. Gordon Sadler
Re: [Q:] KDE 2.1 on testing
On Thu, Feb 08, 2001 at 09:43:58AM +0100, Rainer Dorsch wrote: > Hello, > > can anybody comment on what will be the best way to install KDE 2.1 (when it > is released) on a testing (=woody) system. Is it likely that the .debs from > sid migrate within a relatively short time to woody? > Your best bet is probably to use Ivan's (KDE debian maintainer) debs that are built for stable. Try http://kde.tdyc.com for apt.sources lines and related info. Or check the archives here on this list. Gordon Sadler
Might need to adjust libqt2.2 2.2.4
Odd experiment: Install libqt2.2 2.2.4 from deb, now QTDIR is /usr/share/qt... All's well, now try running an application that was compiled against libqt2.2 while QTDIR was /usr/lib/qt2 ... I haven't tried too many yet, but.. kde has some odd problems. Lots of messages scroll on the console where it wants to fine /usr/lib/qt2/qlistview.h and konqueror looks rather odd. Some of the menu buttons across the top are duplicated, the fonts are horrible and cannot be changed with configure->konqueror->appearance. Maybe libqt2.2 2.2.4 should conflict with all the kapps compiled with libqt2.2 << 2.2.4? Just a thought/observance from here. Gordon Sadler
Build-deps libqt2.2.x
Should have seen this before myself. Noticed you list libpng2-dev in the build depends, and qt does indeed need/want png support. However, you use -qt-libpng when configuring. IMO that's the correct one anyhow. They are fixing leaks and image loading by making modifications to png. But most likely libpng2-dev is spurious as far as external build-depends. Gordon Sadler
Re: qt-copy debian stuff
On Fri, Feb 02, 2001 at 07:09:50PM -0700, Ivan E. Moore II wrote: > okies...it's there. for those of you who build from cvs, let me know if > anything brokt...I just basically took what I'm working on for the 2.2.4 > packages and tweaked it a tad for building from CVS > > some notes: > >1: I have't tested the CVS build bits yet >2: I haven't tested the resulting 2.2.4 debs yet. (as I moved things > around) >3: The Mesa stuff is not removed. I normally hack out the Mesa GL specific > stuff so that we don't have conflicts for non-mesa users. However since > I can't do this to the qt-copy tree, your stuck. But I can only assume > that if your building from cvs your building for yourself..so if you > have mesa installed then it won't hurt you. > THANKS , especially for the heads up, that change in location for qt headers you added to admin/debianrules probably would have taken me a while to find without you pointing it out here -). Doing cvs update right now, hopefully can build some of this tonight, see if I see anything, and let you know tomorrow. Gordon Sadler
Re: A dead key problem fixed in qt 2.2.4.
On Fri, Feb 02, 2001 at 04:27:34PM -0700, Ivan E. Moore II wrote: > > " > > On X11, popup menus do not grab the keyboard anymore, but rely on and > > enforce the application to have focus. This > > works around an X11 bug where deadkeys do not work while the keyboard > > is grabbed. > > " > > actually I think this might have been included in the patches to the 2.2.3 > tree I aplied...not sure.. > > > Hope this is good news for some people on the list. > > Just wait two seconds and Ivan will have packaged it ;-). > > a little longer...I'm doing some cleanup and re-arranging...which will need > testing. > If you can manage to get the debian dir added to kde/qt-copy on CVS... I have been keeping fairly current with kdelibs, kdebase and qt-copy, I imagine some others are as well. With the debian dir in qt-copy, maybe we can assist a bit? I know there are two? debian dirs (kde,qt designer), but at least the main (qt) one might be added? Gordon Sadler pgpagbKPNxjUD.pgp Description: PGP signature
{kde,qt}-designer templates
This applies to both packages, I could submit 2 bugs and/or post here. So far, Ivan has been real good at keeping this whole ball of wax together, so I'll post here. If you want bugs submitted as well just let me know. According to the source for designer, qt-copy/tools/designer/designer/mainwindow.cpp : 3147 It expects to find the templates for various widgets/dialogs in $(QTDIR)/tools/designer/templates/*.ui I have copied them into that location on my machine, so I can claim it works here. Problem: qt doesn't install templates by default? Solution: copy them into place from debian/rules? I looked at your rules file from qt2.2 source, it's a bit hairy -), but looks like you handle moving some qt-designer stuff around line 162. Suggest adding cp tools/designer/templates/*.ui $(p_designer)/usr/lib/qt2/tools/deigner/templates/ Also add the above dir to debian/qt-designer.dirs. I didn't look at kde specific designer stuff, I imagine very similar. Gordon Sadler
Kghostview might need gs
With kghostview installed and no longer requiring gs, I removed gs from my system. I don't use pdf/ps all that often anyway. Today I notice a reproducible segfault trying to view pdf files. I filed a bug with bt to bugs.kde.org. Now I went lurking through the source for kghostview, and it most definitely has routines to call gs by name. Makes me think maybe kghostview cannot provide postscript-viewer, but instead should rely on gs or another viewer? Hope I'm wrong, like all the options debian gives, but I like to keep the number of packages installed to a minimum. Gordon Sadler
Depends for libqt2.2-dev
Version: 2:2.2.3-10 I noticed today during apt-get upgrade that libqt2.2-dev now depends on libpth-dev. However libqt2.2/libqt2.2-mt do not depend on libpth13. Am I missing something, is this maybe a typo? Gordon Sadler pgpb9f1PQ2yrn.pgp Description: PGP signature
Kdevelop 1.4beta
This is just FYI. Raphael Bossek has already submitted an ITP for Kdevelop. I just wanted to let others know, as of approximately 2 days ago, kdevelop 1.4 will now build/run/install on debian. Built against kde2.1beta and qt2.2.3, all from debian/unstable. Be advised, you may have to fiddle with the debian/rules file and/or the debian/kderules. There also might be a problem when checking out CVS with the $(top_srcdir)/admin directory. Set CVSROOT to kde cvs site of your choice then cvs co -rKDEVELOP_1_4 kdevelop. You might also want to go to kdevelop.org and check into getting the c-c++-reference package. It all interoperates very nicely, with Doc-Base support even for all your other properly installed documentation under Debian. Good Luck Gordon Sadler pgpIrliNIVmvp.pgp Description: PGP signature
Re: kicq
On Sat, Jan 13, 2001 at 10:00:54PM +0100, Uli Schinz wrote: > i tried to install kicq. the problem is that at configureing-time i get this > message: > checking for KDE... configure: error: > in the prefix, you've chosen, are no KDE headers installed. This will fail. > So, check this please and use another prefix! > I don't which prefix ishoult try > anybody knows what to do? > ULI If you don't have any other kde packages in source format, you really should get familiar with the locations of KDE and/or QT for building packages. Most packages will need --includedir=/usr/include/kde --with-qt-dir= /usr/lib/qt2 and so on. Best suggestion, install kdelibs3-dev and libqt2.2-dev. Then download the source for some smaller package, maybe kmail or some other suggestion. Then look at the build system, specifically $(top_srcdir)/admin/debianrules. Good luck
Re: KDevelop packages?
Raphael Bossek has declared an intent to package it see http://lists.debian.org/debian-devel-0010/msg01931.html The 1.4beta branch of CVS is somewhat usable right now IMO, still lots of things that don't quite work and one problem that makes it impossible to compile using debian-docbase support. I fixed that locally on my copy but have yet to send it upstream. They don't appear to 'test' their debian support much. Keep in mind 1.4 is strictly for people who can't or won't install libqt1.x and 'need' kdevelop according to the developers. It isn't really meant to be packaged by distros yet IMO. Gordon Sadler On Tue, Jan 09, 2001 at 09:45:10PM +0330, [EMAIL PROTECTED] wrote: > Are there, or will there be, any packages of KDevelop 1.4? > > If not, then I'll have to download it as .tgz but I prefer to keep everything > Debianized! :-)
Re: Problems building kdebase from source using Potato
On Sat, Dec 30, 2000 at 08:57:56PM +, David Morgan wrote: > I haven't built any debian packages from source before so this may be > something I'm doing wrong, but I've checked the Debian FAQ on buidling from > source and I've built the test package "hello" successfully so I think I've > got the basics all in place. > > Now I want to build kdebase from source as I want to get a version with the > Kamera patch applied (see http://www.thekompany.com/projects/gphoto/ for > details). I used apt to get the source files and unpack them. But I couldn't > build the binary deb from this cleanly as after the long compile phase I got > the following errors: > dh_movefiles -pkonqueror > find: usr/bin/nspluginviewer: No such file or directory > find: usr/bin/nspluginscan: No such file or directory > find: usr/bin/nspluginviewer: No such file or directory > find: usr/bin/nspluginscan: No such file or directory > make: *** [binary-arch] Error 1 > Not positive here why this happened, but make sure you have kdelibs3-dev installed prior to even attempting to build kdebase from source. Also ensure you use $(OPTION TO GETROOT) debian/rules binary. > I'm running Potato with the latest updates applied. > I have Sid/unstable here, but am tracking CVS for kde somewhat. > I edited debian/konqueror.files and removed the four lines for nspluginviewer > and nspluginscan and their associated info files. Then I tried to build the > binary deb with: > debian/rules binary > > This seemed to work but I ended up with twelve deb files not the one I was > expecting: > kdebase-dev_2.0.1-0.potato5_i386.deb > kdebase-doc_2.0.1-0.potato5_all.deb > kdebase-libs_2.0.1-0.potato5_i386.deb > kdebase_2.0.1-0.potato5_i386.deb > kdewallpapers_2.0.1-0.potato5_all.deb > kdm_2.0.1-0.potato5_i386.deb > konqueror_2.0.1-0.potato5_i386.deb > konsole_2.0.1-0.potato5_i386.deb > libkonq-dev_2.0.1-0.potato5_i386.deb > libkonq3_2.0.1-0.potato5_i386.deb > task-kde-devel_2.0.1-0.potato5_all.deb > task-kde_2.0.1-0.potato5_all.deb > > So although I only downloaded one source package I seem to have got twelve > binaries. I wasn't expecting this. What is happening here? > This is expected, when you download the source you got kdebase, which is the source for a multi-binary package. One of the binaries it will produce is konqueror. Right now it isn't very feasible to try to break konqueror out of the and build it by itself. > Am I going about things in the right way? The Kamera build instructions just > say to apply over clean kdebase source and ./configure && make && make > install but this doesn't seem right for debian packaged source. > Make sure you use the debian/rules binary target, if not you will not have the proper environment set prior to build. As far as patching the source goes, I haven't tried myself, but if it continues to give you problems I suggest you attempt to build it without patching first. If that works then debian/rules clean, patch, debian/rules binary again. Good luck Gordon Sadler
Re: AA support
AA = Anti-aliasing There was a news byte at kde.org regarding it. I didn't look too deeply myself but most of the comments seemed to applaud the efforts as being great for the visuals. On Sun, Dec 17, 2000 at 05:08:00PM -0200, Rogerio Brito wrote: > On Dec 17 2000, Christian Mayrhuber wrote: > > Am Sunday 17 December 2000 18:31 schrieb Ivan E. Moore II: > > > FYI - I'm building a new QT 2.2.3 package with the Xft extension support. > > > This is of course just for woody as it requires the latest X4. So > > > hopefully we'll be able to see AA support functional soon for KDE and > > > other's... > > > > Whoooha! > > This would be a true christmas present :)) > > What is this AA support? I'm curious about it after these > comments. :-) Really. Please enlighten me. :-) > > > Thank you very much, Roger...
Re: Dependecy problems installing quanta deb
It means kdelibs3 has some new dependencies, libmimelib1 I believe.
Apt will not upgrade packages that have new dependencies if you don't
have those dependents already installed.
To fix try this:
apt-get install kdelibs3-dev
That will get kdelibs3 and kdelibs3-dev and the new dependent.
Follow up with apt-get {dist-,dselect-}upgrade to finish getting any
other updated packages.
Good luck
On Sat, Dec 16, 2000 at 10:47:04AM +0100, Daniel de los Reyes wrote:
> When I try to install the quanta deb on kde.tdyc.com I get a dependecy error :
>
> dpkg: problemas de dependencias impiden la configuración de quanta:
> quanta depende de kdelibs3 (>= 4:2.0.1-0.potato4); sin embargo:
>Versión de kdelibs3 en el sistema es 4:2.0.1-0.potato2.
>dpkg: error al procesar quanta (--install):
> problemas de dependencias - se deja sin configurar
>
> I keep my kde installation up to date but after this when I did an apt-get
> upgrade I got this:
>
> Building Dependency Tree... Done
> The following packages have been kept back
> kdelibs3 kdelibs3-dev
> 0 packages upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
>
> What does it mean that a package has been kept back? How do I fix this?
Re: kdebase and kfind conflict
You can install two or more debs that contain same files with the following: dpkg -i --force-overwrite kfind_2.0.1-2.deb Assuming you have downloaded it, it will be in /var/cache/apt/archives if you used apt-get, if not just cd to where you have the deb. You might try this as well dpkg --force-help to get an idea, of course man dpkg explains it as well. Multiple packages containing same files has been noted as a packaging bug, so you shouldn't need --force-overwrite normally, but it allows you to get around the problem for now. Good luck Gordon Sadler On Tue, Dec 12, 2000 at 04:34:28PM +0100, Tormod Ravnanger Landet wrote: > When upgrading from the kde2.0.1 woody to kde2.1 I got a broken pipe, kdebase > wouldn't install. This was because it had an icon also contained in kfind. I > removed kfind, and then kdebase installed just fine. > > The error I get when trying to reinstall kfind is something like this: > /usr/share/kfind/icons/locolor/22x22/actions/archive.png > also in package kdebase > Subprocess paste killed by signal (Broken pipe) > > I have tried as best I can to force the package onto my system, but to no > avail. Is this a problem many people are experiencing or is my system special > in some way? (I use low color X windows (16bit) but that doesn't get probed, > does it?) > > -- > Tormod Ravnanger Landet
Debian menus
Ivan this might be a bug, or might not -) Under gnome, if I added a package or removed one, the Debian menus would update right away, under WM only desktops as well. Currently under KDE my Debian menus seem 'frozen' I have even run update-menus manually. Packages that I have removed and/or added recently are not showing up. I have checked their postints for calls to update-menus, but I haven't their prerms for removal. Does anyone else observe this, or is it my 'fault'? Thanks
Re: reports
On Wed, Nov 29, 2000 at 03:41:36PM -0700, Ivan E. Moore II wrote: > Those of you running the latest versions of either potato or woody KDE 2 > packages (that meet the following versions)...let's go over all current > problems... > > Package: kdelibs3 4:2.0-final-13 > Package: kdebase-libs,kdebase,kdm,konqueror,konsole,libkonq3 4:2.0-final-13 > > are there any of the html problems or other odd behaviours as with the > previous versions of late? > > Ivan Thanks for all your work. As you may have noticed for the bugs I but have since closed, kdelibs3 4:2.0-final-13 fixed all my problems with helpcenter and konqueror being able to open/open html. As of now 1700 CST 29Nov00 my apt sites have not made any of the other -13 packages available. So IF there are problems in the future I suggest kdelibs3 be looked at as the cause. All of the rest of my kde2 packages under woody are still -12. Thanks again
Re: Not a bug per se
On Sun, Nov 19, 2000 at 10:09:41PM -0700, Ivan E. Moore II wrote: > *If* there are upstream changelogs. For example..the Changelog for > kdelibs was last touched (or the last entry is dated) 1999-02-11. > > there's no point in it being there if it's useless. > > kdenetwork's is even worse... 1998-12-05. > > > Maybe not too important but I am using knode for news, and > > the changelog refers to kdenetwork, so... I really have no > > idea of the status of the package itself. > > All I can say is that I have not see (hardly) any changelog entries (todo's, > news, etc..) made in a LONG time. (years)... It seems that this stuff is > either being discussed across the mailing lists or via web pages somewhere. > > Ivan > Thanks for the quick response. I do want to say that I appreciate what you and all the other package maintainers do, the message was in no way aimed at slighting you or your work. I suppose the KDE web pages might have info on the individual packages? I should look around there some for specifics, or maybe mailing lists? Thanks again. pgpG4UxIajguB.pgp Description: PGP signature
Not a bug per se
Ivan or others, I do not have a full KDE setup here, I was trying it out before it was added to Debian and I had various problems with the 2.0 etc... debs at that time. However, I have noticed that most programs seem to run much smoother as far as graphically and maybe context switching between GNOME and KDE, when I can get KDE running. Long story short, I recently took GNOME off my system and went to a straight window manager, windowmaker, for when I do run X. Now I do have some k apps installed, which of course causes kdelibs3 etc.. to be on my system. I have noticed that most, if not all, of my k related debs have only one changelog (the changelog.Debian.gz one). My under- standing is that there should be two, one for upstream and one for the package itself, unless it is a native Debian package. Maybe not too important but I am using knode for news, and the changelog refers to kdenetwork, so... I really have no idea of the status of the package itself. Thanks pgpFk3PM63WZc.pgp Description: PGP signature
