Re: Kbear crashes in KDE3.1beta on Debian unstable
torsdagen den 5 september 2002 12.08 skrev Ben Burton: > So one suggestion would be to get the debian kbear sources (apt-get source > kbear) and rebuild the package yourself on your 3.1 system and see if this > helps; otherwise you could perhaps ask Karolina for help since I understand > she's providing the core 3.1 stuff. I have done that. I did nothing more than just rebuild it on kde 3.1. The package I made is on http://cgi.algonet.se/htbin/cgiwrap/pgd/debian/kde3.1-apps/kbear_2.0beta2.kde31-1_i386.deb -- Karolina
Re: Kbear crashes in KDE3.1beta on Debian unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Karolina, I downloaded this deb and kbear loads fine now. So this issue is fixed ;) Just so you know, dpkg believes that I was DOWNGRADING kbear: [EMAIL PROTECTED]:~/src/debs$ sudo dpkg -i kbear_2.0beta2.kde31-1_i386.deb dpkg - warning: downgrading kbear from 2.0-beta2-1 to 2.0beta2.kde31-1. (Reading database ... 75273 files and directories currently installed.) Preparing to replace kbear 2.0-beta2-1 (using kbear_2.0beta2.kde31-1_i386.deb) ... Unpacking replacement kbear ... Setting up kbear (2.0beta2.kde31-1) ... [EMAIL PROTECTED]:~/src/debs$ Thanks for the fix! If there is a better way to report bugfixes in these packages in the future, let me know. Ravenhall On Friday 06 September 2002 12:15 am, Karolina Lindqvist wrote: > torsdagen den 5 september 2002 12.08 skrev Ben Burton: > > So one suggestion would be to get the debian kbear sources (apt-get > > source kbear) and rebuild the package yourself on your 3.1 system and see > > if this helps; otherwise you could perhaps ask Karolina for help since I > > understand she's providing the core 3.1 stuff. > > I have done that. > I did nothing more than just rebuild it on kde 3.1. The package I made is > on > http://cgi.algonet.se/htbin/cgiwrap/pgd/debian/kde3.1-apps/kbear_2.0beta2.k >de31-1_i386.deb > > -- Karolina - -- 12413AEB2ED4FA5E6F7D78E78BEDE820945092OF923A40EElOE5IOCC98D444AA08E324 -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9eEWl4e9YdOpQYMsRAia5AJ9tRWs5CDdgs+AeEjoc/s1IZPheawCgmGgy q29liKy9osFx2Y7pPrcbU5Y= =k4/n -END PGP SIGNATURE-
Re: kde programs and environment
> How do I forward environment variables to kde program? > I am using ktexmaker2 and it does not see my TEXINPUTS > environment variable when I click a TeX file. When I start > ktexmaker2 from a shell it is fine but then I have to use the > open button to get to the file. Direct clicking is more convenient. > > Any ideas? You seem to be one more person hit by this problem... The traditional way to set up user's environment is the login shell startup script (~/.bash_login for bash). You set environment variables there and export them, and later all processes you start have the correct environment. The problem is that in the current setup, when you login via XDM (or KDM), you have no login shell and no way to set up local environment. KDM executes /etc/kde2/kdm/Xsession - a normat shell script, it is run by non-login shell, and as long as shell process that executes it is not interactive, it does not read ~/.bashrc. /etc/kde2/kdm/Xsessions starts /etc/X11/Xsession. Same story. /etc/X11/Xsession starts your desktop. So the desktop processes are started without environment set. When you later start applications from menu (or Alt+F2), they are also started without environment set. But if you start xterm (or konsole or other X shell), bash started there is interactive and sources .bashrc. So if environment variables are set in .bashrc, you will see tham set in xterm window. And processes start from there will get them set. This may become really confusing for a user. And it is wrong thing to do. Non-login interactive shell startup script (.bashrc) is NOT the correct place to set up environment, because (as explained above) it will make the environment inconsistent - one processes wil get it set, others won't. And because this makes hard to work with local environment changes. E.g. you change a var (e.g. $PATH), then start mc and not see your change there. Environment should be set ONCE PER SESSION in such place that ALL session process may see it. For system-wide environment, there is /etc/environment that is read by pam_env. Vars set in /etc/environment will be visible to ALL user's processes, regardless of login method (text console or xdm/kdm or ssh). Seems that currently there is NO WAY to set up user's own environment corectly (unless pam_env can read some per-user configuration which I am not aware of). A possible workaround is to make /etc/kde2/kdm/Xsession run by login shell, and set up your environment to ~/.bash_login. This will end to consistent environment. To do so, edit /etc/kde2/kdm/Xsession and replace #!/bin/sh by #!/bin/bash --login Note that doing so in /etc/X11/Xsession is not correct, because this script may be also run when X is started from command line, when environment is also set and possibly modified by user for the current session. Note also that if your shell is not bash, you will have to duplicate settings in ~/.bash_login and in your shell's login startup script. That's why a better solution it to use per-user files loaded by pam_env. But I don't know if they are supported.
Re: Kbear crashes in KDE3.1beta on Debian unstable
fredagen den 6 september 2002 08.05 skrev Nathan Waddell: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Karolina, > I downloaded this deb and kbear loads fine now. So this issue is fixed ;) > Just so you know, dpkg believes that I was DOWNGRADING kbear: > > [EMAIL PROTECTED]:~/src/debs$ sudo dpkg -i kbear_2.0beta2.kde31-1_i386.deb > dpkg - warning: downgrading kbear from 2.0-beta2-1 to 2.0beta2.kde31-1. I didn't have the debian files for 2.0-beta2-1. I have a kind of feeling that the problem with kbear might be a possible problem for every package built separately for kde 3.0, when kde 3.1 is coming. Maybe the officiall kde 3.1 packager is solving that problem somehow? I am not sure exactly how to build the beta so that all packages that depend on older versions of kde will be automatically rejected, at the same time as packages built with kde 3.1- beta should be compatible with the future kde 3.1 official packages. If anyone have an idea, I would be grateful, since I will rebuild for kde 3.1-beta2 when it is official. -- Karolina
kde 3.1 and kaddressbook
I have instaled kde 3.1 from Karolina Lindquist debs (thank for your work). I try to start kaddressbook which is rather important small program in my work. But it didn't start with comment: "kaddressbook: error while loading shared libraries: libkaddressbookpart.so: cannot open shared object file: No such file or directory" I can't find it in any deb package. How to solve that? zdzislaw a. kaleta
Re: kde 3.1 and kaddressbook
fredagen den 6 september 2002 10.30 skrev Zdzislaw A. Kaleta: > I have instaled kde 3.1 from Karolina Lindquist debs (thank for your work). > I try to start kaddressbook which is rather important small program in my > work. But it didn't start with comment: > "kaddressbook: error while loading shared libraries: > libkaddressbookpart.so: cannot open shared object file: No such file or > directory" > I can't find it in any deb package. How to solve that? That library is by mistake in kpilot. Just install kpilot and it should work. -- Karolina
koncd
hi there! is there a package for koncd available??? i need it for kde3. compiling the sources returns following error: - ripcd.cpp: In method `void RipCD::slot_NewItemsData(const KFileItemList &)': ripcd.cpp:134: call of overloaded `setNum(long long unsigned int)' is ambiguous /usr/include/qt/qstring.h:782: candidates are: class QString & QString::setNum(short int, int = 10) /usr/include/qt/qstring.h:785: class QString & QString::setNum(short unsigned int, int = 10) /usr/include/qt/qstring.h:788: class QString & QString::setNum(int, int = 10) /usr/include/qt/qstring.h:791: class QString & QString::setNum(unsigned int, int = 10) /usr/include/qt/qstring.h:519: class QString & QString::setNum(long int, int = 10) /usr/include/qt/qstring.h:520: class QString & QString::setNum(long unsigned int, int = 10) /usr/include/qt/qstring.h:794: class QString & QString::setNum(float, char = 'g', int = 6) /usr/include/qt/qstring.h:522: class QString & QString::setNum(double, char = 'g', int = 6) ripcd.cpp:145: call of overloaded `setNum(long long unsigned int)' is ambiguous /usr/include/qt/qstring.h:782: candidates are: class QString & QString::setNum(short int, int = 10) /usr/include/qt/qstring.h:785: class QString & QString::setNum(short unsigned int, int = 10) /usr/include/qt/qstring.h:788: class QString & QString::setNum(int, int = 10) /usr/include/qt/qstring.h:791: class QString & QString::setNum(unsigned int, int = 10) /usr/include/qt/qstring.h:519: class QString & QString::setNum(long int, int = 10) /usr/include/qt/qstring.h:520: class QString & QString::setNum(long unsigned int, int = 10) /usr/include/qt/qstring.h:794: class QString & QString::setNum(float, char = 'g', int = 6) /usr/include/qt/qstring.h:522: class QString & QString::setNum(double, char = 'g', int = 6) make[2]: *** [ripcd.o] Fehler 1 make[2]: Leaving directory `/usr/local/src/koncd-1.0rc2/koncd' make[1]: *** [all-recursive] Fehler 1 make[1]: Leaving directory `/usr/local/src/koncd-1.0rc2' make: *** [all-recursive-am] Fehler 2 - mayby someone knows where the problem is? regards uli
kde 3.1 and kcontrol
Thanks very much to Karolina Lindquist - the 3.1 debs are much appreciated and quite stable too! One problem I have is with kcontrol, that Look&Feel Desktop (libkcm_kong.la not found) and Window Behaviour (libkcm_kwinoptions.la not found) do not work. Have I missed downloading something? Thanks. Michael -- Michael Hoodes http://www.hoodes.comSeattle, WA
kppp & non root users
Hi All, I need a bit of help here, I am trying to get kppp to work with a normal user. The user is a member of dialup and dip. Every time the user dials up I get the following output to the console (I started kppp from command line): [EMAIL PROTECTED]:/usr/share/doc/kppp$ kppp Opener: received SetSecret Opener: received OpenLock Opener: received OpenDevice Opener: received ExecPPPDaemon In parent: pppd pid 2040 Kernel supports ppp alright. Couldn't find interface ppp0: No such device Couldn't find interface ppp0: No such device It was pppd that died pppd exited with return value 19 Sending 2036 a SIGUSR1 Opener: received RemoveSecret Opener: received RemoveSecret Opener: received OpenResolv Opener: received OpenResolv error opening resolv.conf! Opener: received RemoveLock Opener: received PPPDExitStatus Opener: received OpenSysLog According to man pppd, exit code 19 is failure to authenticate to peer. I have checked the username and passwords and they are correct. If I run kppp as root with the same settings, it dials up fine without problems. I am convinced it has something to do with permissions, but don't know what more to check. I'm running sid & KDE3. TIA Craig -- Craig Main RHCE ST Solutions Cell: 082-323-4670 Home Tel: 011-760-1900
Re: Kbear crashes in KDE3.1beta on Debian unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I got the deb I am referring to from the source in your email: >I have done that. >I did nothing more than just rebuild it on kde 3.1. The package I made is on >http://cgi.algonet.se/htbin/cgiwrap/pgd/debian/kde3.1-apps/kbear_2.0beta2.kde31-1_i386.deb > >-- Karolina either a) Kbear was never upgraded from my KDE 3.0 version because of the name of the package (kbear_2.0beta2.kde31-1_i386.deb, which dpkg believed was a downgrade) and I never noticed because I use apt-get dist-upgrade or aptitude, or b) the Kbear that I had was never upgraded from the KDE 2.2 version. Either one is likely, as I don't remember when it was upgraded before this. If that kbear package is the same package you provided with the 3.1 packages, and you didn't rebuild it because of my original email, then one of these two things must have occured. The package probably needs to be renamed in such a way that dpkg does not interpret it as a downgrade. Nathan On Friday 06 September 2002 02:05 am, Karolina Lindqvist wrote: > I didn't have the debian files for 2.0-beta2-1. > > I have a kind of feeling that the problem with kbear might be a possible > problem for every package built separately for kde 3.0, when kde 3.1 is > coming. Maybe the officiall kde 3.1 packager is solving that problem > somehow? > > I am not sure exactly how to build the beta so that all packages that > depend on older versions of kde will be automatically rejected, at the same > time as packages built with kde 3.1- beta should be compatible with the > future kde 3.1 official packages. If anyone have an idea, I would be > grateful, since I will rebuild for kde 3.1-beta2 when it is official. > > -- Karolina - -- 12413AEB2ED4FA5E6F7D78E78BEDE820945092OF923A40EElOE5IOCC98D444AA08E324 -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD4DBQE9eMuD4e9YdOpQYMsRAqEXAJwIUH9SEAwBh5TPaHumi9SYTg01CQCXWwko GsN/EJl/PizMyGtfhuS5vg== =vBkh -END PGP SIGNATURE-
Re: kde programs and environment
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 It seems as though there is a void to be filled here. Someone with a good understanding of KDE and this problem should create a fix, perhaps reading in all of the aforementioned files or something. What would also be very cool to have would be a gui program that checks defined environment settings and reports them, as well as allowing you to click on them and change/set their values within KDE. Wish I understood KDE well enough, but alas not yet. Nathan On Friday 06 September 2002 12:54 am, Nikita V. Youshchenko wrote: > > How do I forward environment variables to kde program? > > I am using ktexmaker2 and it does not see my TEXINPUTS > > environment variable when I click a TeX file. When I start > > ktexmaker2 from a shell it is fine but then I have to use the > > open button to get to the file. Direct clicking is more convenient. >> > Seems that currently there is NO WAY to set up user's own environment > corectly (unless pam_env can read some per-user configuration which I am > not aware of). -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9eMyb4e9YdOpQYMsRAnozAJ4nzL7qL/Z5u7cris2lZ7dan5m0kACeJKrL 5Pp0yW9pupShE+8V8O3x7L4= =JqhI -END PGP SIGNATURE-
problem with debs for kde3.1 dependencies
Hope this helps in identifying the problem. I'm running KDE3.1 beta on Debian Sid. "Sorry, but the following packages have unmet dependencies: renamedlg-plugins: Depends: atlantik but it is not installable" zdzislaw a. kaleta
Konqueror 3.07 crashing upon sending mail to OWA
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi. I'm using Debian unstable on KDE3.1-beta1, and Konqueror 3.07. At work, I routinely use OWA (Outlook Web Access) to email via our corporate exchange server. All functions work fine except sending mail. Every time I send an email, Konqueror crashes, and produces a KDE crash handler. Not that my email DOES get sent every time. Here is the debugging information from the crash handler: (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...[New Thread 1024 (LWP 3375)] (no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... 0x40e35609 in wait4 () from /lib/libc.so.6 #0 0x40e35609 in wait4 () from /lib/libc.so.6 #1 0x40eaadd0 in __check_rhosts_file () from /lib/libc.so.6 #2 0x40ce0eeb in waitpid () from /lib/libpthread.so.0 #3 0x405986ac in KCrash::defaultCrashHandler () from /usr/lib/libkdecore.so.4 #4 0x40cdea44 in pthread_sighandler () from /lib/libpthread.so.0 #5 0x40dbe518 in sigaction () from /lib/libc.so.6 #6 0x413d014a in KHTMLPart::qt_invoke () from /usr/lib/libkhtml.so.4 #7 0x4086db26 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #8 0x4086da7e in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #9 0x413e84f8 in DOM::DocumentImpl::finishedParsing () from /usr/lib/libkhtml.so.4 #10 0x413e8569 in DOM::DocumentImpl::qt_emit () from /usr/lib/libkhtml.so.4 #11 0x4140c3e0 in DOM::HTMLDocumentImpl::qt_emit () from /usr/lib/libkhtml.so.4 #12 0x4086db0e in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #13 0x4086da7e in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #14 0x413f87a8 in Tokenizer::finishedParsing () from /usr/lib/libkhtml.so.4 #15 0x4140466a in HTMLTokenizer::end () from /usr/lib/libkhtml.so.4 #16 0x414048cb in HTMLTokenizer::finish () from /usr/lib/libkhtml.so.4 #17 0x413e4dcd in DOM::DocumentImpl::finishParsing () from /usr/lib/libkhtml.so.4 #18 0x413bdcc1 in KHTMLPart::end () from /usr/lib/libkhtml.so.4 #19 0x413bd229 in KHTMLPart::slotFinished () from /usr/lib/libkhtml.so.4 #20 0x413d013c in KHTMLPart::qt_invoke () from /usr/lib/libkhtml.so.4 #21 0x4086db83 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #22 0x40143493 in KIO::Job::result () from /usr/lib/libkio.so.4 #23 0x401348f8 in KIO::Job::emitResult () from /usr/lib/libkio.so.4 #24 0x40135955 in KIO::SimpleJob::slotFinished () from /usr/lib/libkio.so.4 #25 0x40136e20 in KIO::TransferJob::slotFinished () from /usr/lib/libkio.so.4 #26 0x4014470c in KIO::TransferJob::qt_invoke () from /usr/lib/libkio.so.4 #27 0x4086db26 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #28 0x4086da7e in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #29 0x4012a79c in KIO::SlaveInterface::finished () from /usr/lib/libkio.so.4 #30 0x40129334 in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.4 #31 0x40128e88 in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.4 #32 0x40126d58 in KIO::Slave::gotInput () from /usr/lib/libkio.so.4 #33 0x40128549 in KIO::Slave::qt_invoke () from /usr/lib/libkio.so.4 #34 0x4086db26 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #35 0x4086dc34 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #36 0x40aa940b in QS
Re: kppp & non root users
On Fri, 2002-09-06 at 07:20, Craig Main wrote: > Hi All, > > I need a bit of help here, I am trying to get kppp to work with a normal > user. The user is a member of dialup and dip. Every time the user dials > up I get the following output to the console (I started kppp from > command line): > > [EMAIL PROTECTED]:/usr/share/doc/kppp$ kppp > Opener: received SetSecret > Opener: received OpenLock > > Opener: received OpenDevice > Opener: received ExecPPPDaemon > In parent: pppd pid 2040 > Kernel supports ppp alright. > Couldn't find interface ppp0: No such device > Couldn't find interface ppp0: No such device > It was pppd that died > pppd exited with return value 19 > Sending 2036 a SIGUSR1 > Opener: received RemoveSecret > Opener: received RemoveSecret > Opener: received OpenResolv > Opener: received OpenResolv > error opening resolv.conf! > Opener: received RemoveLock > Opener: received PPPDExitStatus > Opener: received OpenSysLog > > According to man pppd, exit code 19 is failure to authenticate to peer. > I have checked the username and passwords and they are correct. > > If I run kppp as root with the same settings, it dials up fine without > problems. > > I am convinced it has something to do with permissions, but don't know > what more to check. I'm running sid & KDE3. > > TIA > > Craig I think it has to do with the 'auth' option in the /etc/ppp/options file.You can test by changing the line to 'noauth'. # Require the peer to authenticate itself before allowing network # packets to be sent or received. # Please do not disable this setting. It is expected to be standard in # future releases of pppd. Use the call option (see manpage) to disable # authentication for specific peers. auth -- Greg C. Madden Debian GNU/Linux signature.asc Description: This is a digitally signed message part
Re: Wanted: text editor where word wrap does not insert newline
On Wed, 4 Sep 2002 13:51:18 -0400 Bruce Miller <[EMAIL PROTECTED]> wrote: > The KDE text editors (kedit/kate/kwrite) have a familiar command set > and interface for ex-Windows users. My problem with them is that the > word wrap feature inserts a newline at each word wrap whereas I am > used to editors that wrap only on screen but not "to disk". Newlines > are inserted only by a user's explicit keystroke. apt-get install gedit
Re: Wanted: text editor where word wrap does not insert newline
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Have you submitted this patch to the Kate team? Nathan On Wednesday 04 September 2002 06:14 pm, Jarno Elonen wrote: > Hi, > > I just made a KDE 3.0.3 patch that fixes virtual wrapping in kedit. > The patch, and also a binary .deb for the impatient, are available at: > > http://koti.welho.com/jelonen/code/unofficial-debs/kedit-wordwrap/ > > Choose "Virtual (visible but not saved)" as Word Wrap from options. It > replaces the "Let editor width decide" option. > > - Jarno - -- 12413AEB2ED4FA5E6F7D78E78BEDE820945092OF923A40EElOE5IOCC98D444AA08E324 -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9ePjK4e9YdOpQYMsRAhWKAJ9nnuM/pQcNvU6nvA9zeuVC9Q1nBwCfcbrZ h6UpU/W7TXSrVF//64/F6DE= =Bh92 -END PGP SIGNATURE-
konqueror will not start
I'm using kde from woody. Konqueror and Kate will not start up. If I try to start them from the menu or in a konsole they don't start. This started a few days ago after I did an update from security.debian.org. Things I've tried. If I delete all of ~/.kde and the ~/.dcop stuff from ~/ and restart kde the problem goes away till the first time konqueror crashes (once when I told it to show previews of pictures. once when I went to a flash page, once I'm not sure why.) or hangs. Right after one of two problems happen. 1) Kate and konqueror show there icon next to the cursor like they are starting then after about 15 secs the icon goes away but nothing starts. Kimage and Advanced editor are not able to open a file but knode is able to save a file just fine. 2) I get errors the klauncher can't be found. #1 happens more often than number 2. Looking at ~/.xsessionerrors I don't see anything being added to the file from the crashes. Any suggestions? -- Earl F Hampton http://hamiii.sytes.net/index.phtml
Re: kmix in kde3.0.3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The solution was to exit kmix and start it again. Rather embarrasing, although it should have seen the mixer without restarting. Cheers, James On Thursday 05 September 2002 01:05 pm, James Hirschorn wrote: > Greetings, > > Am I the only one who has noticed this problem: kmix does not see any mixer > devices except when run as root? Alsamixer works fine for all users. > > James - -- James Hirschorn Fields Institute Toronto, Canada http://www.logic.univie.ac.at/~hirschor/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD4DBQE9eQPkQRMwEXZtsSARAiORAJjVHy4ydAHYIbjffgfndenl/+SIAJwOy+0W 6cgzndvNlC2CMBDGPPds1w== =bbM4 -END PGP SIGNATURE-
krusader with KDE3
Hi all, I'm using sid, and i installed kde3 from different sources. No problems but one: I can't install krusader. Using apt-get install krusader, apt-get wants to remove kde3 and replace it with kde2. So i got the sources and wanted to compile it, but configure complains about a missing qt-mt, at least version 3.0.3. I think what is needed is libqt-mt-dev. Installed is 2.3.xxx. apt-get gets no newer version. Where can i get the required qt-mt OR a deb-package of krusader fitting kde3? TIA Chris pgpnyRmBbwCfK.pgp Description: PGP signature
Re: krusader with KDE3
On Fri, 2002-09-06 at 22:17, Christian H. Kuhn wrote: > Hi all, > > I'm using sid, and i installed kde3 from different sources. No > problems but one: I can't install krusader. Using apt-get install > krusader, apt-get wants to remove kde3 and replace it with kde2. So i > got the sources and wanted to compile it, but configure complains > about a missing qt-mt, at least version 3.0.3. > > I think what is needed is libqt-mt-dev. Installed is 2.3.xxx. apt-get > gets no newer version. Where can i get the required qt-mt OR a > deb-package of krusader fitting kde3? > > TIA > Chris Several days ago I had the same problem. After several days of playing with qt-mt paths I was told to check if I have g++ installed. Did not. Installing g++ and g++ 2.95 dramatically changed situation. Are you sure, you have g++ installed? Cheerio Vlada
compatability and compilers
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 As it might have some bearing on a problem I'm having, what *exact* compiler were the current 3.0.3 packages compiled with? - -- A mouse is a device used to point at the xterm you want to type in. --Kim Alm, a.s.r -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9eRxPEHLN/FXAbC0RAm6LAJwI376WlwkZOxFQNYTAt56CqxxWxACeJIvH 8UnDEftcDjBhNZjwJDzT3O4= =g91o -END PGP SIGNATURE-
KDM 3.0.3 7 minute startup
I'm trying to help a friend of mine install KDE 3.0.3. I added the kde.org apt lines and installed arts, kdebase and kdelibs. KDM starts up fine. However, when he logs in it literally takes about 5 min for him to see a desktop. The little splash screen pops up and it gets to "starting system services" and goes no further. Then the splash screen disappears after a couple minutes. And it sits there looking at the background image. And then after a bit more time the desktop comes up. I can only guess that it's waiting on some device to time out or something. I see nothing strange in the .xsession_errors file. Anyone have any ideas? Saadiq
Re: KDM 3.0.3 7 minute startup
> I'm trying to help a friend of mine install KDE 3.0.3. I added the > kde.org apt lines and installed arts, kdebase and kdelibs. KDM starts > up fine. However, when he logs in it literally takes about 5 min for > him to see a desktop. The little splash screen pops up and it gets to This does seem like it takes way too long. However, what kind of computer does he have? I'm guessing that it's fast. :( Fred
Re: krusader with KDE3
Hallo Vlada, "Ing. Vladimir M. Kerka" <[EMAIL PROTECTED]> on Fri, Sep 06, 2002 at 10:35:08PM +0200: > > I'm using sid, and i installed kde3 from different sources. No > > problems but one: I can't install krusader. Using apt-get install > > krusader, apt-get wants to remove kde3 and replace it with kde2. So i > > got the sources and wanted to compile it, but configure complains > > about a missing qt-mt, at least version 3.0.3. > > > > I think what is needed is libqt-mt-dev. Installed is 2.3.xxx. apt-get > > gets no newer version. Where can i get the required qt-mt OR a > > deb-package of krusader fitting kde3? > > > Several days ago I had the same problem. After several days of playing > with qt-mt paths I was told to check if I have g++ installed. Did not. > Installing g++ and g++ 2.95 dramatically changed situation. Are you > sure, you have g++ installed? home:/home/qno# dpkg -l|grep g++ ii g++2.95.4-16 The GNU C++ compiler. ii g++-2.95 2.95.4-11 The GNU C++ compiler. ii g++-3.23.2.1-0pre1The GNU C++ compiler. home:/home/qno# which g++ /usr/bin/g++ home:/home/qno# ll /usr/bin/g++ lrwxrwxrwx1 root root8 2002-08-03 16:50 /usr/bin/g++ -> g++-2.95 kr chris pgpKtns4gs1V6.pgp Description: PGP signature
Re: Wanted: text editor where word wrap does not insert newline
> Have you submitted this patch to the Kate team? Yes, or Kedit team, actually: http://bugs.kde.org/db/29/29994.html - Jarno
Re: krusader with KDE3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Friday 06 September 2002 21:17, Christian H. Kuhn wrote: > Hi all, > > I'm using sid, and i installed kde3 from different sources. No > problems but one: I can't install krusader. Using apt-get install > krusader, apt-get wants to remove kde3 and replace it with kde2. So i > got the sources and wanted to compile it, but configure complains > about a missing qt-mt, at least version 3.0.3. > > I think what is needed is libqt-mt-dev. Installed is 2.3.xxx. apt-get > gets no newer version. Where can i get the required qt-mt OR a > deb-package of krusader fitting kde3? apt-get install libqt3-mt-dev Paul Cupis - -- [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9eTP4IzuKV+SHX/kRAk/uAJ46RnBXyozEtyK6X9OV9C+qRdfEUgCaA03J sIKQotre0aFbvimKYMx334k= =xB49 -END PGP SIGNATURE-
Re: KDM 3.0.3 7 minute startup
Thinkpad A21m... PIII I have the same laptop and it's not even remotely as slow. Not even in the same neighborhood. On Fri, Sep 06, 2002 at 05:51:18PM -0400, Fred K Ollinger scribbled: > > I'm trying to help a friend of mine install KDE 3.0.3. I added the > > kde.org apt lines and installed arts, kdebase and kdelibs. KDM starts > > up fine. However, when he logs in it literally takes about 5 min for > > him to see a desktop. The little splash screen pops up and it gets to > > This does seem like it takes way too long. However, what kind of computer > does he have? I'm guessing that it's fast. :( > > Fred
