Mosfet Liquid KDE
Just our of curiosity, today I decided that I would like to give the Mosfet liquid engine a looksie. I am currently running KDE 2.2.2 (woody) and I found that tracking down the actual tarballs for this release to be quite difficult so basically I am just asking the list if anybody can give me a URL to grab the latest and greatest mosfet engine. Yes and please dont flame me for not "looking hard enough" because my endeavours to find it just led me to complaints of other people who couldn't seem to find it. Any help would be much appreciated. Markos.
Re: Screensaver Timeout Suggestion - Comments ?
On Thu, 21 Mar 2002 04:25:29 +, I wrote: >I kind of like the Windows [gulp] NT >feature where, when the screensaver timeout is reached and the >screensaver leaps into life, you get about 10 seconds to hit a key (or >move the mouse) to cancel the screensaver again *without* having to >enter the password - if you miss that 10-second window then the >password becomes required. [...] >What does anybody else on this list think ? OK - thanks for the feedback folks. I didn't know about the KDE-usability mailing list (thanks Rene), and will now repost the suggestion there for more comment before submitting the wishlist bug (but I'll probably submit the bug anyway). Cheers, Nick Boyce Bristol, UK -- Allen's Axiom: When all else fails, read the instructions.
Re: kde & update-alternatives
Oops, sorry for posting this twice. When it didn't show up after about an hour I re-sent it. I didn't realize how slow this listserver is. Please respond to the second one as I think it is more well thought out. -Colin
Re: kde & update-alternatives
Colin Andrews wrote: > I don't think, realistically, that I will ever really upgrade this > system($20 garage sale 486 laptop) to woody. I don't think, realistically, that you will ever get kde 2.1/2.2 to run at a useable speed on such a machine. Time to upgrade. Sorry. Simon Hepburn.
kde & update-alternatives
>From scanning the archives of this list and debian-user, this seems to be a >problem that other people have had in the past, but the *right* way to solve this still isn't clear to me. First, I'm using Potato (2.2r5). I already had XDM & WinowMaker installed & working (if you can call it that) after my initial install. I got the kde packages from kde.debian.net. After a seemingly succesful install with dselect, I come up in KDM at boot/login but I still go into WindowMaker after login. When I run: update-alternatives --config x-window-manager I have no choice there for anything related to KDE. Reading /usr/doc/kdebase/README.Debian suggests that there should be something there. Now, the discussion on this list in the past has seemed to suggest there may just be some inherent incompatabilities between the way kde treets it's environment and the assumptions about X made by the update- alternatives system, at least in potato anyway, and the only way to deal with it is to hack around it. (Is that right?) Hack or not, here's the options that I see. Some from this list some from my own pondering... 1) edit file /etc/kde2/kdrmc, an add kde2 to line saying SessionTypes=default,failsafe, so that it looks like SessionTypes=kde2,default,failsafe or the same idea but through kcontrol This seems to bypass the update alternatives mechanism and connect the KDE session directly from KDM. 2) either cd /etc/alternatives ln -s /usr/bin/startkde x-window-manager (ouch) or update-alternatives --install /usr/bin/x-window-manager x-window-manager /usr/bin/startkde or update-alternatives --install /usr/bin/x-window-manager x-window-manager /usr/bin/kde2 Will either of these even work? 3) update-alternatives --install /usr/bin/x-session-manager x-session-manager /usr/bin/startkde I belive that KDM is showing up as my x-session-manager & it seems to me that this is what I want. 4) ~/.xsession == exec startkde or ~/.xsession == exec kde2 (Do either of these work? If so are there any drawbacks to this approach?) 5) Use woody instead. It's not clear that this solves the problem though. It sounds like it's not exactly airtight in woody either. So... I just want to know if there is an accepted "best", or *safest*, or at least *conventional* way to solve this problem. It seems like #1 is the way KDM wants you to solve the problem. It sounds like this works too. Is this what most people do? Do any of the methods using the update-alternatives mechanism even work? Is there anyone, developers maybe, out there who can comment about the apparent disconnect between the altenatives system and KDE? Is it a never the twain shall meet kinda thing? Is there a FAQ that I missed?
Re: kmail gettings slower and big cpu usage on exit
On Thursday 21 March 2002 23:25, Russell Coker wrote: > On Thu, 21 Mar 2002 21:16, Achim Bohnet wrote: > > For some weeks I (again) notice kmail (woody + kde from sid) > > working slower and slower. Too slow after ~ 2 days. > > Only thing that helps is to exit kmail > > and start it again. Further, even after empty trash, compacting > > all folders and then exiting kmail, kmail runs in the background > > for several minutes comsuming as much CPU time as it can get. > > If you have it set to compact folders on exit then that can explain the disk > access on exit. Hmm, I did an compact all folders by hand before the exit and a second compat all folders takes almost no time. But when I exit I still see these minutes of full CPU usage and the HD led is not flashing.Nevertheless just to be sure I switched off compact all folders on exit and will exit kmail in two days ;) > I have noticed that kmail seems to slowly increase memory use over time and > suspect a memory leak. Same here but I have enough of mem ;) > > Also when reading a large message the amount of time taken to display it is > excessive (sometimes 30+ seconds for a very large message). Let me elaborate what I mean with 'slower'. After one or two days when I switch from one very little message to another (e.g. in the folder of this list) I can watch the folder and message window being redraw. E.g. 1 s for the msg list window redraw and 1 s for the message window :( That makes kmail unusable and it's time to exit. After compact all folders manually I exit kmail. kmail window vanishes almost immediately but top shows that kmail continues to run for some minutes in the background comsuing CPU time. Achim > > -- > If you send email to me or to a mailing list that I use which has >4 lines > of legalistic junk at the end then you are specifically authorizing me to do > whatever I wish with the message and all other messages from your domain, by > posting the message you agree that your long legalistic sig is void. > > > -- 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]
kde & update-alternatives
>From scanning the archives of this list, this seems to be a problem that other >people have had in the past, but the *right* way to solve this still isn't clear to me. First, I'm using Potato (2.2r5). I already had XDM & WinowMaker installed & working (if you can call it that). I got the kde packages from kde.debian.net. After a seemingly succesful install with dselect, I come up in kdm at boot/login but I still go into WindowMaker after login. When I run: update-alternatives --config x-window-manager I have no choice there for anything related to KDE. Reading /usr/doc/kdebase/README.Debian suggests that there should be something there. Now, the discussion on this list in the past has seemed to suggest there may just be some inherent incompatabilities between the way kde treets it's environment and the assumptions about X made by the update-alternatives system, at least in potato anyway, and the only way to deal with it is to hack around it. (Is that right?) Hack or not, here's the options that I see. Some from this list some from my own pondering... 1) edit file /etc/kde2/kdrmc, an add kde2 to line saying SessionTypes=default,failsafe, so that it looks like SessionTypes=kde2,default,failsafe or similar but through kcontrol This seems to bypass the update alternatives mechanism and connect the KDE session into KDM. 2) either cd /etc/alternatives ln -s /usr/bin/startkde x-window-manager (ouch) or update-alternatives --install /usr/bin/x-window-manager x-window-manager /usr/bin/startkde or update-alternatives --install /usr/bin/x-window-manager x-window-manager /usr/bin/kde2 Will either of these even work? 3) update-alternatives --install /usr/bin/x-session-manager x-session-manager /usr/bin/startkde I belive that KDM is showing up as x-session-manager & it seems to me that this is what I want. 4) ~/.xsession == exec startkde or ~/.xsession == exec kde2 (Do either of these work? If so are there any drawbacks to this approach?) 5) Use woody instead. It's not clear that this solves the problem though. It sounds like it's not exactly airtight in woody either. So... I just want to know if there is an accepted "best", or *safest*, or at least *conventional* way to solve this problem. I'm sure that there's varying opinions about whats the "best" way to do anything. I can live with "This is how *most* people solve this problem..." I don't think, realistically, that I will ever really upgrade this system($20 garage sale 486 laptop) to woody. Philisophically, I would like to do things in the *cleanest* possible way. As a professional software engineer, I know that sometimes the cleanest way to do something is just a big hack. Any takers?
Re: kmail gettings slower and big cpu usage on exit
On Thu, 21 Mar 2002 21:16, Achim Bohnet wrote: > For some weeks I (again) notice kmail (woody + kde from sid) > working slower and slower. Too slow after ~ 2 days. > Only thing that helps is to exit kmail > and start it again. Further, even after empty trash, compacting > all folders and then exiting kmail, kmail runs in the background > for several minutes comsuming as much CPU time as it can get. If you have it set to compact folders on exit then that can explain the disk access on exit. I have noticed that kmail seems to slowly increase memory use over time and suspect a memory leak. Also when reading a large message the amount of time taken to display it is excessive (sometimes 30+ seconds for a very large message). -- If you send email to me or to a mailing list that I use which has >4 lines of legalistic junk at the end then you are specifically authorizing me to do whatever I wish with the message and all other messages from your domain, by posting the message you agree that your long legalistic sig is void.
Re: kmail gettings slower and big cpu usage on exit
On Thursday 21 March 2002 21:16, Achim Bohnet wrote: > Hi, > > For some weeks I (again) notice kmail (woody + kde from sid) > working slower and slower. Too slow after ~ 2 days. > Only thing that helps is to exit kmail > and start it again. Further, even after empty trash, compacting > all folders and then exiting kmail, kmail runs in the background > for several minutes comsuming as much CPU time as it can get. > > Any me-toos? Anyone heavily using KDE 3s kmail already? > Is it fixed in KDE 3? > I've encountered it as well; I guess it's due to the "compact all folders on exit" setting, which takes quite a lot of time if your folders are really big. (executing it manually for my "linux-kernel" folder which has ~2 mails, takes almost 20 seconds on my Athlon 700) cheers, Yven -- Yven Johannes Leist - [EMAIL PROTECTED] http://www.leist.beldesign.de
kmail gettings slower and big cpu usage on exit
Hi, For some weeks I (again) notice kmail (woody + kde from sid) working slower and slower. Too slow after ~ 2 days. Only thing that helps is to exit kmail and start it again. Further, even after empty trash, compacting all folders and then exiting kmail, kmail runs in the background for several minutes comsuming as much CPU time as it can get. Any me-toos? Anyone heavily using KDE 3s kmail already? Is it fixed in KDE 3? Thx, Achim -- 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: location of kde:s configuration and migration to Debian
- Original Message - From: "Hendrik Naumann" <[EMAIL PROTECTED]> > > Anyway, I am moving old my home directory to the new installation, > > and I was pretty much under the impression that moving my KDE > > settings from SuSE's KDE 2.2.2 to the Debian's KDE 2.2.2 could be > > done by simply copying the .kde-directory from one place to > > another. Unfortunately, the KDE on Debian did not accept the old > > settings and just wrote over the old ones. But, it seems, that if > > you afterwards move single files, like the bookmark.xml, they get > > accepted by the reciving KDE. > > I remember that SuSE stores kde-2.x settings in ~/.kde2. Did you copy > this to ~/.kde in the debian-home? Well yes, I did notice that :) My question may be simple, but not that simple. > > SuSE, which I use now (debian should really have something like > > sax2 for configuring X) > I also used to use sax. I think except its not graphical > dpkg-reconfigure xserver-xfree86 > (for woody) is as good as sax2. I found a tool named 'dexconf' in Sid (I'm running Woody), and it seems to somehow autoprobe my settings, since it does not ask anything - just writes automatically a new X-configuration file -- which worked fine! Can it get more easy? :) There is a lot of discussion wheter Linux is ready for the desktop or not. Back in the middle of 1990's, Microsoft made it breakthrough by having Windows pre-installed on PCs. A installed Linux with KDE2/3 is just as easy to use as any Windows, so I am sure that Linux is as ready for the desktop. Actually, KDE even easier to use since it has less bugs that confuse the user than what there are in Windows :) If Linux would be pre-installed, then installing it will not be the issue, since once installed, it is there (unlike Windows, which you have to install every now and then since its registry gets corrupted). Tools like dexconf makes Linux possible even for people who just wants to get their work done. (sorry for being far from the topic, but I am just happy that not all development in this world goes backwards)
Re: starting windows without decoration
On Thursday 21 March 2002 01:24, G. L. `Griz' Inabnit wrote:
> -BEGIN PGP SIGNED MESSAGE-
>
> On Tuesday 19 March 2002 10:44 am, Jarno Elonen wrote:
> > On Tuesday 19 March 2002 18:25, [EMAIL PROTECTED] wrote:
> > > hello, i am wondering if there is a way to open a new window in kde
> > > without window-decoration? i've looked at kstart, but that doesn't seem
> > > to be able to do that.
> >
> > In KDE 2, you can start an application (window) without borders like this:
> >
> > kstart --type Override
> >
> > So for example, to start a transparent Konsole without borders eterm-style,
> > you could say...
> >
> > kstart --skiptaskbar --skippager --alldesktops --type Override
> > konsole
> >
> > ...then remove Menubar, Toolbar, Frame and Scrollbar, and finally make it
> > transparent by choosing "Transparent Konsole" from Schema-menu.
> >
> > - Jarno
>
> This is helpfull! Thank You. A follow-up question that still haunts me
> is:
>
> How can I make konsole always open a 'login shell' {xterm -ls}?
That's easy ;)
konsole --help | grep login
but IMHO the wrong way. Everything that's inherited to child process should
be in .bash_profile (or .profile). At least as long as you use kdm
ln -s .bash_profile ~/.xprofile
and login again, there's no need to use --ls.
FMI about this search for the string xprofile in the list archive of
kde-devel (or was it kde-core-devel?) on lists.kde.org. There was a long
thread some days ago.
Achim
--
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]
kio_fish (another question)
-BEGIN PGP SIGNED MESSAGE- Hey All, Quickly; Recursive.Copy or Drag-n-Drop'ing of folders By this I mean that I attempted to drag-n-drop a folder from a buddies machine (via konq [fish://[EMAIL PROTECTED] I get the error message below: "Could not write to /home/arch/debs/licq-ssl/licq-ssl.test6.deb" Upon checking, the /home/arch/deb/licq-ssl directory has NOT even been created on my local machine. Subsequently, NO it can't write to that folder. Is it possible at all? Am I missing a switch somewhere? Regards, Griz p.s. [teancom, shaddup! i'm at least using konq now!! :--) ] - -- __ OutCast Computer Consultants of Central Oregon http://outcast-consultants.redmond.or.us [EMAIL PROTECTED] (541) 504-1388 /\IRC: 205.227.115.251:6667:#OutCasts /\ICQ: UIN 138930
Re: location of kde:s configuration
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi > Anyway, I am moving old my home directory to the new installation, > and I was pretty much under the impression that moving my KDE > settings from SuSE's KDE 2.2.2 to the Debian's KDE 2.2.2 could be > done by simply copying the .kde-directory from one place to > another. Unfortunately, the KDE on Debian did not accept the old > settings and just wrote over the old ones. But, it seems, that if > you afterwards move single files, like the bookmark.xml, they get > accepted by the reciving KDE. I remember that SuSE stores kde-2.x settings in ~/.kde2. Did you copy this to ~/.kde in the debian-home? I also did the suse->debian transission. There where also differences for other programms like xemacs. Also .bashrc and friends have differences. You may have to look at them too. > I installed Debian on one of my hard disks and I found it be great, > though the process of installation was difficult compared with > SuSE, which I use now (debian should really have something like > sax2 for configuring X) I also used to use sax. I think except its not graphical dpkg-reconfigure xserver-xfree86 (for woody) is as good as sax2. Did you try it? Hendrik PS. By the way. On my laptop suse 7.0 failed completely because it didn't know the ati mobility chip. But xf86config for Xfree86-3.x did the job. - -- PGP ID 21F0AC0265C92061 -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.3 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8mhsYIfCsAmXJIGERArJTAJ9/5J+u/fk1A8g3tTFvXMvOx+K5iACggOqV ml0Q3ZJMMG/xK7k+0OmQgA8= =AG3v -END PGP SIGNATURE-
Re: AutoLogout Screen Saver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Mittwoch, 20. März 2002 16:44 schrieb Jay Kline: > Is there a screen saver or something that will automaticly log a > user out if left idle for too long? This is for a lab environment, > so after 5 min of inactivity the screen saver should come up > (password protected) and after 30 min the user should be logged out > to free the terminal up. I think autolog is the tool you are searching for. Hendrik - -- PGP ID 21F0AC0265C92061 -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.3 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8mhz5IfCsAmXJIGERAm2uAJ9KJXRNQr4EsQWSuqhXtkLgVFRDWgCcCXnv u0ZvMIcnP/EVplyMHcCKMdM= =ShkZ -END PGP SIGNATURE-
Re: confusing behavior from kwin on potato
On Thursday 21 March 2002 14:29, [EMAIL PROTECTED] wrote: > Ok, I've got the 'rkrusty' line in my sources.list... > > earlier last week I do an 'update' in dselect 'cause I'm looking for > something > else and I suddenly get a bunch of packages selected looks like there was > a > change from KDE 1.1.1 to 2.1.1 sometime since the last time I updated (yeah, > I don't do it _that_ often) > > when I first tried running startx after that I suddenly had no window > manager... ick... > [ snip long desc] > > hmmm, ok, something's definitely missing... or still sprocked. any > suggestions on where to continue looking? Relevant FAQ's? Manuals? email > addresses? > > or should I just comment out the rkrusty line, move the old kde .debs to a > directory somewhere, put that in my sources.list and see if I can talk > dselect > into putting things back the way they were? > > anyways any suggestions or pointers to FM's to R would be appreciated Try starting kde with startx or via kdm. Then o check ~/.xsession. Any useful error msgs? o start a terminal emulator and from there start kwin. Error msgs? (Try Alt-F2 and start you favorite term emulator or on console login as same user and use DISPLAY=0:0 konsole # or xterm) Achim > :)Alice M. Pinard > Casco Indemnity Company > [EMAIL PROTECTED] > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [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: Screensaver Timeout Suggestion - Comments ?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Said Nick Boyce on Thu, Mar 21, 2002 at 04:25:29AM +: > What does anybody else on this list think ? Yeah, that sounds cool, I wouldn't mind playing with it, and I think it would be fine as an /option/ in kcontrol. Good idea! - -- [!] Justin R. Miller <[EMAIL PROTECTED]> PGP 0xC9C40C31 -=- http://codesorcery.net http://www.gnu.org/philosophy/amazon.html -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8mfNi94d6K8nEDDERAvYZAJ0bBmsjo0VtFRXC1xMupSptMya/9wCeOxeU rlexuavKeiML/8Tj9RW+6G8= =yKCH -END PGP SIGNATURE-
confusing behavior from kwin on potato
Ok, I've got the 'rkrusty' line in my sources.list... earlier last week I do an 'update' in dselect 'cause I'm looking for something else and I suddenly get a bunch of packages selected looks like there was a change from KDE 1.1.1 to 2.1.1 sometime since the last time I updated (yeah, I don't do it _that_ often) when I first tried running startx after that I suddenly had no window manager... ick... I installed fvwm just to have _something_ and while that's running I can select 'kde' from the window manager menu option, but the next time I use xwindows I get fvwm again... so various things I tried tried using dpkg to reinstall the old kdebase... run startx, get a blank screen (well, blank fuzzy screen, that grey 'I'm gonna put something on the screen as soon as I figure out what... oh... I don't know what' that x window sometimes does) put the 'new' kdebase back... tried pointing etc/alternatives/x-window-manager to /usr/bin/kwin ok now I get kdesktop, a lovely blue but nothing else no menus, I click I get no menus... hrm installed kdm... I hate my computer automatically going into xwindows but hey, for now it would be a start ok... brings up the login... I login... and I get the kdesktop but again no 'desktop' just pretty blue shading hrm ok, kill the manager and it pops the login up again this time I go in as failsafe, run startkde from the bash console... get some "I'm not happy this isn't how you do it" messages (more details if interested :) from the console but kwin starts up... hmmm, ok, something's definitely missing... or still sprocked. any suggestions on where to continue looking? Relevant FAQ's? Manuals? email addresses? or should I just comment out the rkrusty line, move the old kde .debs to a directory somewhere, put that in my sources.list and see if I can talk dselect into putting things back the way they were? anyways any suggestions or pointers to FM's to R would be appreciated :)Alice M. Pinard Casco Indemnity Company [EMAIL PROTECTED]
Re: Screensaver Timeout Suggestion - Comments ?
3/20/02 10:25:29 PM, Nick Boyce <[EMAIL PROTECTED]> wrote: >What does anybody else on this list think ? >Is this suggestion worth making ? (It's just a convenience feature.) >If so, do I do that by submitting a KDE bug report with severity level >= "wishlist" ? I like the idea. You could also try sending it to [EMAIL PROTECTED] as well. NB that this is a mailing list.
