Re: anyone having problems with noatun?
Hiya Tim, I just tested it here. First, noatun DOES run now, which it didn't 2 upgrades ago :) I fired up top and then fired up the player. mp3's are using about 12% and mpg files about 30% - which is pretty damned good considering. It doesn't appear to support avi files. Box here is a potato wid 2.2.17 and latest from Ivan for kde. Box is a 450pIII with 128mb. On Monday 19 March 2001 17:42, Tim Kelley wrote: I'm running the ltest KDE2.1 with potato. Lately (I can't remember after which update) whenever I try to play a file accosiated with kde media player (noatun) my cpu goes straight to 100% and nothing else happens. I've tried playing files from the terminal to see if anything useful ... I get this: noatun ./blah.mpg ** Warning ** unix_connect: can't connect to server (unix:/tmp/mcop-tpk/pimp_winkinc_com-0220-3ab69d5d) Launched ok, pid = 1214 ** Warning ** unix_connect: can't connect to server (unix:/tmp/mcop-tpk/pimp_winkinc_com-0220-3ab69d5d) I am running artsd, ps ax gives me this: [EMAIL PROTECTED]:~$ ps ax | grep art 1214 ?R 0:28 artsd -F 5 -S 4096 -d -b 16 ls -l /tmp mcop-tpk/ gives me this (excuse the wrapping): total 6 -rw---1 tpk tpk 206 Mar 19 19:37 Arts_AudioManager -rw---1 tpk tpk 206 Mar 19 19:37 Arts_MidiManager -rw---1 tpk tpk 206 Mar 19 19:37 Arts_PlayObjectFactory -rw---1 tpk tpk 206 Mar 19 19:37 Arts_SimpleSoundServer -rw---1 tpk tpk 206 Mar 19 19:37 Arts_SoundServer srwxr-xr-x1 tpk tpk 0 Mar 19 17:59 pimp_winkinc_com-0220-3ab69d5d srwxr-xr-x1 tpk tpk 0 Mar 19 19:37 pimp_winkinc_com-04be-3ab6b461 -rw---1 tpk tpk32 Mar 19 17:59 secret-cookie is anyone else having problems? All I can do at this point is killall -9 artsd. At some point everything was working fine -- Jaye Inabnit\ARS ke6sls/TELE: USA-707-442-6579\/A GNU-Debian linux user Email: [EMAIL PROTECTED] WEB: http://www.qsl.net/ke6sls ICQ: 12741145 If it's stupid, but works, it ain't stupid. SHOUT JUST FOR FUN. Free software, in a free world, for a free spirit. Support freedom!
Re: stupid, but I have to ask it - how to start it up once installed
On Tuesday 20 March 2001 06:28, Whit wrote: Okay, by going to archives for this list I found the clues on how to run the automated kde install on a fresh potato with no desktop manager set up yet. Really impressed by how smoothly that ran compared to trying to use rpms on Red Hat. (Suggestion: put a short mention of how to invoke the installation in the debian.kde.net Webpages?) Yeah, so then I do a startx and I've got a kde terminal on my otherwise grey screen rather than the default rxvt or whatever it was after getting XFree up. Umm, what's the totally obvious thing to do (if I'd ever set up Debian before) to have the system bring up the full kde screen? (Suggestion: put a short mention of this on the Webpages too and you'll about have the newbie angle covered - providing the newbie has gotten past similar bits of mystery in the initial potato install.) Method one: echo kde2 ~/.wmrc # once startx Method two: apt-get install kdm select 'kde2' instead of 'default' in the login window Achim \/\/ I-I I T Blauvelt [EMAIL PROTECTED] -- To me vi is Zen. To use vi is to practice zen. Every command is a koan. Profound to the user, unintelligible to the uninitiated. You discover truth everytime you use it. -- [EMAIL PROTECTED]
Re: KDE in woody?
I've used Ivan's KDE packages with a Woody/testing system. I know Ivan does not recommend it, but then I'm only using my box for personal use. At the moment everything seems to be quite stable, but I have seen some unstable behaviour on my system. If your woody box is 'mission critical' you probably don't want to try it, but if it's just for regular home use, I've found it to be quite a good combination. Ivan has recommended in the past that if you 'must' have KDE on woody, you should probably use the QT and KDE stuff from unstable rather than his, as it is closer matched WRT lib's and such, but I've only had a few glitches here and there as Ivan has updated and re-built his KDE .deb's. No show stoppers. Of course this is just my personal experiences based on my system. You might want to hear what others have to say about their experiences before jumping in. Cheers, John Gay
Re: KDE in woody?
I was getting the panel resets quite often, but the last updates from Ivan seems to have sorted that. In saying this, though, I'm running Progeny, which is woody-based. I'm not sure what the differences are between Progeny and Debian Woody, so that might be why mine is fine now. Cheers, John Gay
Re: KDE in woody?
On Tue, 20 Mar 2001, Peter Seidler wrote: On the kde.tdyc.com website, there is a note stating that KDE is now part of woody. That was written before package pools. If it was written today it would probably say... KDE is now part of Sid (unstable), and hopefully will make it into Woody (testing) soon. - Bruce
Re: stupid, but I have to ask it - how to start it up once installed
On Tue, Mar 20, 2001 at 07:23:09AM +0100, Achim Bohnet wrote: Method one: echo kde2 ~/.wmrc # once startx Thanks for the advice. However, startx still brings up just a grey screen with konsole in the middle ; Now to the next method ... Whit [EMAIL PROTECTED]
KDevelop missing C++ reference
Hi, I have KDevelop 1.4 (kdevelop_1.4-final-0.potato1_i386.deb), but when I try to look at the C/C++ reference, it gives me an error. I've been trying to find a .deb package holding this reference and no luck. Is anyone succesfully using KDevelop? With all the documentation created? If you could share your insights on how and what packages you used, it would be greatly appreciated. Thanks, Guillermo Castro
Re: stupid, but I have to ask it - how to start it up once installed
On Tue, Mar 20, 2001 at 07:23:09AM +0100, Achim Bohnet wrote: Method two: apt-get install kdm select 'kde2' instead of 'default' in the login window The first step is redundant - but did it anyhow - no change. The second - well, where is that 'login window'? Thanks, Whit [EMAIL PROTECTED]
Re: Konqueror on Alpha
*ALL* of KDE is hosed on alpha currently. It's part of that it builds, but doesn't run group. However..what do you mean it depends on a way-too-old-perl? Depends: kdelibs3 (= 4:2.1.0-0), lesstif1, libc6.1 (= 2.2.1-2), libjpeg62, libkonq3 (= 4:2.1.0-0), libpng2, libqt2 (= 2:2.3.0-final-0) | libqt2-gl (= 2:2.3.0-final-0), libstdc++2.10-glibc2.2, xlibs (= 4.0.1-11), zlib1g (= 1:1.1.3), kdebase-libs (= 4:2.1.0.1-1), libkonq3 (= 4:2.1.0.1-1), debconf Please advise as to where a way-too-old-perl comes into play. I don't seem to have any old versions of perl installed on my box and have konq installed... Ivan On Sun, Mar 18, 2001 at 08:38:54AM +0100, Bart Warmerdam wrote: Hi All, Anyone tried konqueror yet on Alpha? It seems to verified to work since it's in the unstable area, right? But the dependencies are not current (depends on a way-too-old-perl) and the only this it does is showing the crash results on my screen. BTW: has anyone with a SX164 + mga (2064w) been able to run X-4 without suffering severe screen mess-ups and lockup of keyboard or complete system within 5 minutes of use? Cheers, B. -- B. Warmerdam GNU/Debian Linux [EMAIL PROTECTED], [EMAIL PROTECTED] (Keyid: 10A0FDD1) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] ---end quoted text--- -- 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
Re: stupid, but I have to ask it - how to start it up once installed
Or in side your konsole after x starts type $startkde On Tuesday 20 March 2001 13:38, matthschulz wrote: Just say: startx kde2 the it should work. At least it does for me. Matth Am Dienstag, 20. März 2001 14:31 schrieb Achim Bohnet: On Tuesday 20 March 2001 19:27, Whit wrote: On Tue, Mar 20, 2001 at 07:23:09AM +0100, Achim Bohnet wrote: Method one: echo kde2 ~/.wmrc # once startx Thanks for the advice. However, startx still brings up just a grey screen with konsole in the middle ; Now to the next method ... Have a look at ~/.xsession-errors. Looks like your problem is some- where else. What processes are running when you type 'ps x' in the konsole that sits in the middle of the grey desktop? FWIW for now you can try kdeinit_wrapper kdesktop to get a blue background :) Achim Whit [EMAIL PROTECTED]
Re: stupid, but I have to ask it - how to start it up once installed
On Tue, Mar 20, 2001 at 11:59:47AM -0700, David Bishop wrote: If you install kdm, but haven't rebooted, you need to run /etc/init.d/kdm start as root. You will then see the login window he was referring to. Otherwise, just reboot the machine. Yeah, I just discovered that on the next boot. Please tell me how to undo it! I don't want the system to come up in a GUI - guess I should have been clear that what I'm trying to do is get startx or the equivalent to work from a bash tty. I often don't work in a GUI, and don't want to waste time going in to one just to go back out. I'm also curious why the reinstall of kdm set it this way, when the initial one didn't - guess that script modified the install enough to keep this often-undesirable result from happening? Thanks again, Whit [EMAIL PROTECTED]
Re: stupid, but I have to ask it - how to start it up once installed
On Tue, Mar 20, 2001 at 07:03:48PM +, John Gay wrote: If you don't want your system to boot directly into X, I'm not sure what command you can run to get kdm, but once that is up, you can then select kde2 when you login and off you go. Thanks for the details on kdm. Indeed what I'm trying to do is set it so that startx or whatever works from a shell - I don't as a rule want to boot into a GUI. Ah well. Someone must know. As for why Debian, apt-get install xxx is enough reason for me. I've never had any luck using .rpm's. And the new task packages make it that much easier. Unfortunately, the configuration can be more difficult to get your head around for non-UNIX types, but once you get used to it, it is much more powerful and stable than anything I've ever tried. Well, I'm a Unix type trying to get the hang of Debian. Always humbling to become a beginner again. I'm more used to Red Hat, Slackware and Mandrake, with some Solaris experience. I agree the apt-get stuff is a real advance. What's surprising me is how sparse the Debian documentation is. Maybe once a bit further in it will make such obvious sense that less documentation will be needed? Whit [EMAIL PROTECTED]
Re: stupid, but I have to ask it - how to start it up once installed
On Tue, Mar 20, 2001 at 03:38:26PM -0600, matthschulz wrote: Just say: startx kde2 And we have a winner! Thanks, guy. Whit [EMAIL PROTECTED]
Re: stupid, but I have to ask it - how to start it up once installed
To stop it, you can either uninstall kdm (apt-get remove kdm) or manually delete the link in /etc/rc2.d/. Since it seems like you won't ever want it to boot to X (the only function of *dm on a workstation machine) you should probably just remove the package. However, I'm curious as to whether or not that worked (i.e., did it actually start kde when you logged on?) If it did, that points to a problem with you startx routine (type, whatnot). If it didn't, something is seriously wrong with your install and we get to dig deeper :-) HTH, D.A.Bishop On Tuesday 20 March 2001 16:15, Whit wrote: On Tue, Mar 20, 2001 at 11:59:47AM -0700, David Bishop wrote: If you install kdm, but haven't rebooted, you need to run /etc/init.d/kdm start as root. You will then see the login window he was referring to. Otherwise, just reboot the machine. Yeah, I just discovered that on the next boot. Please tell me how to undo it! I don't want the system to come up in a GUI - guess I should have been clear that what I'm trying to do is get startx or the equivalent to work from a bash tty. I often don't work in a GUI, and don't want to waste time going in to one just to go back out. I'm also curious why the reinstall of kdm set it this way, when the initial one didn't - guess that script modified the install enough to keep this often-undesirable result from happening? Thanks again, Whit [EMAIL PROTECTED]
Compiling KwinTV?
I was able to get task-kde-devel installed and tried to compile KwinTV. ./configure seemed to work, all the required directories were found, but make fails at the very end when linking with the following: /bin/sh ../libtool --silent --mode=link g++ -O2 -s -o kwintv -L/usr/lib -L/usr/X11R6/lib wintv.o wintvmain.o wintvscreen.o wintvchannel.o wintvstream.o wintvstreamview.o wintvstreamviewData.o otab.o otabdata.o omixdev.o omixdevdata.o ogeneraldata.o ogeneral.o osnapshotdata.o osnapshot.o ofullscreen.o ofullscreendata.o vtab.o vtabdata.o soptions.o soptionsData.o sframerate.o sframerateData.o dsp.o rcfile.o channel.o mixer.o countries.o avivideoclip.o rawvideoclip.o ppmvideoclip.o c2freq.o c2freqData.o c2opts.o c2optsData.o c2prog.o c2progData.o ctab.o ctabdata.o kirc.o wintvscan.o parsecl.o wizNorm.o wizRegion.o wizScan.o wizNormData.o wizRegionData.o wizScanData.o wizFinish.o wizFinishData.o docking.o v4lxif.o qt_visual.o colorspace.o -lkdeui -lkdecore -lqt -lqt-mt -lXext -ljpeg -lXxf86dga -lXxf86vm /usr/bin/ld: cannot find -lqt-mt collect2: ld returned 1 exit status make[3]: *** [kwintv] Error 1 make[3]: Leaving directory `/home/jgay/kwintv/kwintv-0.8.5/kwintv' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/jgay/kwintv/kwintv-0.8.5/kwintv' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/jgay/kwintv/kwintv-0.8.5' make: *** [all-recursive-am] Error 2 progeny:/home/jgay/kwintv/kwintv-0.8.5# As far as I can tell, everything has compiled but when it tries to link the executable, it can't find the lqt and mt lib's? This is only a WAG, as I'm not that great at compiling. Can someone make out what is failing, and even better, what I need to do about it? I tried running ldconfig, just in case, but it still didn't work. My other question is, once I've got make complete, will make install put everything into the right directories for a Debian-based system or will I need to change anything first? Ideally I'd like to build, test and contribute a .deb for kwintv as I can't seem to find one but I know little enough about just compiling software. I wouldn't know where to start to make a .deb out of it. Cheers, John Gay
Re: Compiling KwinTV?
[...] /usr/bin/ld: cannot find -lqt-mt [...] As far as I can tell, everything has compiled but when it tries to link the executable, it can't find the lqt and mt lib's? This is only a WAG, as I'm not that great at compiling. Can someone make out what is failing, and even better, what I need to do about it? I tried running ldconfig, just in case, but it still didn't work. no...it's not that it can't find the lqt and mt libs, it cant find the lqt-mt libs. It's trying to link to the mt version of qt. apt-get install libqt-mt-dev My other question is, once I've got make complete, will make install put everything into the right directories for a Debian-based system or will I need to change anything first? Ideally I'd like to build, test and contribute a .deb for kwintv as I can't seem to find one but I know little enough about just compiling software. I wouldn't know where to start to make a .deb out of it. dunno...I haven't tried to build/install kwintv for quite some time so I don't know where it wants to put things. If you want to know how to build .deb's, you should look at the packaging manuals and whatnot. 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
