RE: klisa
"Ivan E. Moore II" <[EMAIL PROTECTED]> wrote: > ok..klisa should be fixed now... lisarc should be only looked for in > /etc/kde2 now. > -- > > Ivan E. Moore II Confirmed! It now reads and WRITES lisarc to /etc/kde2/lisarc with klisa 2.2.2-3. Thanks! The "problem" with clicking on the + beside the "Local Network" icon remains. You still get the error message unless you modify the lan.desktop file's URL setting. This seems to be the more "generic" KDE problem with other distros that I saw on the KDE bug list. It worked fine in KDE 2.1.2 with the "URL=lan:/" setting. Something changed in the KDE config files somewhere, I suspect. Cheers, -Don Spoon-
Re: klisa
On Sat, Dec 01, 2001 at 12:43:53AM -0600, Donald R. Spoon wrote: > "Ivan E. Moore II" <[EMAIL PROTECTED]> wrote: > > > ok..klisa should be fixed now... lisarc should be only looked for in > > /etc/kde2 now. > > -- > > > > Ivan E. Moore II > > Confirmed! It now reads and WRITES lisarc to /etc/kde2/lisarc with > klisa 2.2.2-3. Thanks! > > The "problem" with clicking on the + beside the "Local Network" icon > remains. You still get the error message unless you modify the > lan.desktop file's URL setting. This seems to be the more "generic" KDE > problem with other distros that I saw on the KDE bug list. It worked > fine in KDE 2.1.2 with the "URL=lan:/" setting. Something changed in > the KDE config files somewhere, I suspect. I did modify it. from lan:/ to lan://localhost/ 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
Minor but annoying bug in KDE
I don't think this has to do with how it's being packaged for Debian, but whenever you close a window by double-clicking the top-left titlebar button and there's a desktop icon behind the button, a single click event is triggered for that icon. For anyone used to using this close method, the accidental opens are a bit of a nuisance. Chris
Re: Minor but annoying bug in KDE
On Sat, Dec 01, 2001 at 03:23:39AM -0500, Chris wrote: > I don't think this has to do with how it's being > packaged for Debian, but whenever you close a window by > double-clicking the top-left titlebar button and there's a > desktop icon behind the button, a single click event is > triggered for that icon. For anyone used to using this > close method, the accidental opens are a bit of a nuisance. reproducible and bug filed upstream. Bug #35620 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
Re: 2.2.1: logout problems
> I know that this problem has been posted here before, but the solution > posted (uncheck "Automatically log in after X server crash") does not > work for me. I do have this option unchecked. > > Any help will be greatly appreciated. > please run "kdm -debug 15" and send me the daemon syslog. btw, does 2.2.2 yield the same effect? greetings -- Hi! I'm a .signature virus! Copy me into your ~/.signature, please! -- Nothing is fool-proof to a sufficiently talented fool.
Re: klisa
-BEGIN PGP SIGNED MESSAGE- On Friday 30 November 2001 11:33 pm, Ivan E. Moore II wrote: > On Sat, Dec 01, 2001 at 12:43:53AM -0600, Donald R. Spoon wrote: > > "Ivan E. Moore II" <[EMAIL PROTECTED]> wrote: > > > ok..klisa should be fixed now... lisarc should be only looked for in > > > /etc/kde2 now. > > > -- > > > > > > Ivan E. Moore II > > > > Confirmed! It now reads and WRITES lisarc to /etc/kde2/lisarc with > > klisa 2.2.2-3. Thanks! > > > > The "problem" with clicking on the + beside the "Local Network" icon > > remains. You still get the error message unless you modify the > > lan.desktop file's URL setting. This seems to be the more "generic" KDE > > problem with other distros that I saw on the KDE bug list. It worked > > fine in KDE 2.1.2 with the "URL=lan:/" setting. Something changed in > > the KDE config files somewhere, I suspect. > > I did modify it. from lan:/ to lan://localhost/ > > Ivan Uh, damn. :--( I got ALL excited about seeing the above, jumped into Konq, clicked the + and damned if it didn't open, just like it's supposed to! Then I clicked on the + by LOCAL NETWORK and one of those annoying little boxes jumped open and told me: Can't find parent item lan://localhost/ in the tree. Internal error. Localhost IS in /etc/hosts, SID is up2date (it's midnight:42 PST), any thoughts? Or is this a configuration error on MY behalf? - -- __ OutCast Computer Consultants of Central Oregon http://outcast-consultants.redmond.or.us [EMAIL PROTECTED] (541) 504-1388 Toll Free (866) 562-7160 Via IRC at; 205.227.115.251:6667:#OutCasts Via ICQ: UIN 138930 "Failure is not an option...it's bundled with Microsoft" -anonymous- Hi! I'm a .signature virus! Copy me into your ~/.signature, please! "Software is like sex. They're both better when they're free!!" - Linus Torvalds "As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product."
Re: klisa
On Sat, Dec 01, 2001 at 01:51:06AM -0800, G. L. `Griz' Inabnit wrote: > -BEGIN PGP SIGNED MESSAGE- > > On Friday 30 November 2001 11:33 pm, Ivan E. Moore II wrote: > > On Sat, Dec 01, 2001 at 12:43:53AM -0600, Donald R. Spoon wrote: > > > "Ivan E. Moore II" <[EMAIL PROTECTED]> wrote: > > > > ok..klisa should be fixed now... lisarc should be only looked for in > > > > /etc/kde2 now. > > > > -- > > > > > > > > Ivan E. Moore II > > > > > > Confirmed! It now reads and WRITES lisarc to /etc/kde2/lisarc with > > > klisa 2.2.2-3. Thanks! > > > > > > The "problem" with clicking on the + beside the "Local Network" icon > > > remains. You still get the error message unless you modify the > > > lan.desktop file's URL setting. This seems to be the more "generic" KDE > > > problem with other distros that I saw on the KDE bug list. It worked > > > fine in KDE 2.1.2 with the "URL=lan:/" setting. Something changed in > > > the KDE config files somewhere, I suspect. > > > > I did modify it. from lan:/ to lan://localhost/ > > > > Ivan > > Uh, damn. :--( I got ALL excited about seeing the above, jumped into > Konq, > clicked the + and damned if it didn't open, just like it's supposed to! Then > I clicked on the + by LOCAL NETWORK and one of those annoying little boxes > jumped open and told me: > > Can't find parent item lan://localhost/ in the tree. Internal error. > > Localhost IS in /etc/hosts, SID is up2date (it's midnight:42 PST), any > thoughts? Or is this a configuration error on MY behalf? on my system I was able to follow it all the way down to SMB...however when clicking on the + next to SMB it crashes...clicking on SMB does not.. just the + piece of it...which has been reported upstream by myself. 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
Re: klisa
-BEGIN PGP SIGNED MESSAGE- On Saturday 01 December 2001 02:48 am, Ivan E. Moore II wrote: > On Sat, Dec 01, 2001 at 01:51:06AM -0800, G. L. `Griz' Inabnit wrote: > > -BEGIN PGP SIGNED MESSAGE- > > > > On Friday 30 November 2001 11:33 pm, Ivan E. Moore II wrote: > > > On Sat, Dec 01, 2001 at 12:43:53AM -0600, Donald R. Spoon wrote: > > > > "Ivan E. Moore II" <[EMAIL PROTECTED]> wrote: > > > > > ok..klisa should be fixed now... lisarc should be only looked for > > > > > in /etc/kde2 now. > > > > > -- > > > > > > > > > > Ivan E. Moore II > > > > > > > > Confirmed! It now reads and WRITES lisarc to /etc/kde2/lisarc with > > > > klisa 2.2.2-3. Thanks! > > > > > > > > The "problem" with clicking on the + beside the "Local Network" icon > > > > remains. You still get the error message unless you modify the > > > > lan.desktop file's URL setting. This seems to be the more "generic" > > > > KDE problem with other distros that I saw on the KDE bug list. It > > > > worked fine in KDE 2.1.2 with the "URL=lan:/" setting. Something > > > > changed in the KDE config files somewhere, I suspect. > > > > > > I did modify it. from lan:/ to lan://localhost/ > > > > > > Ivan > > > > Uh, damn. :--( I got ALL excited about seeing the above, jumped into > > Konq, clicked the + and damned if it didn't open, just like it's supposed > > to! Then I clicked on the + by LOCAL NETWORK and one of those annoying > > little boxes jumped open and told me: > > > > Can't find parent item lan://localhost/ in the tree. Internal error. > > > > Localhost IS in /etc/hosts, SID is up2date (it's midnight:42 PST), any > > thoughts? Or is this a configuration error on MY behalf? > > on my system I was able to follow it all the way down to SMB...however > when clicking on the + next to SMB it crashes...clicking on SMB does not.. > just the + piece of it...which has been reported upstream by myself. > > Ivan Damn Me! I found another glitch. :--( Instead of updating the systems that are connected to my network, it shows the machines that were on the network when I 'originally' configured klisa. :--( Too strange. No amount of RELOADing helps either. But here's the fun part.. If I click on 'dualie' (which is no longer on my network) it shows the shared dirs on one of the client machines that is currently connected to the network!! (Wasn't the lyrics "Strange Dayz Indeed"?) Want/need more info? - -- __ OutCast Computer Consultants of Central Oregon http://outcast-consultants.redmond.or.us [EMAIL PROTECTED] (541) 504-1388 Toll Free (866) 562-7160 Via IRC at; 205.227.115.251:6667:#OutCasts Via ICQ: UIN 138930 "Failure is not an option...it's bundled with Microsoft" -anonymous- Hi! I'm a .signature virus! Copy me into your ~/.signature, please! "Software is like sex. They're both better when they're free!!" - Linus Torvalds "As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product."
kdf crash and kdm weirdness
Another thing that's not exactly well-working, although probably not a packaging issue, is that kdf always crashes when LANG is set to something else than English/C. For example, --- [EMAIL PROTECTED]:~$ locale LANG=de_DE LC_CTYPE="de_DE" [...] LC_IDENTIFICATION="de_DE" LC_ALL= [EMAIL PROTECTED]:~$ kdf Error running df command... got [DateisystemTyp 1k-Blöcke Benutzt Verfügbar Ben% montiert auf] KCrash: crashing crashRecursionCounter = 2 KCrash: Application Name = kdf path = pid = 2764 [EMAIL PROTECTED]:~$ unset LANG [EMAIL PROTECTED]:~$ kdf (now works until closed) [EMAIL PROTECTED]:~$ --- Another issue can be experienced when you start the kdm control center module and become root, go to the "Users" tab and click on the icon button to open a user-defined icon. Whichever icon I select gets scaled down to 32x32 automagically, which is way to small (I think the default size is 64x64). Copying the .png manually to the appropriate config directory works as expected (the image file has the original size) If further information is necessary, feel free to contact me. Yours Malte #8-)
Re: kdf crash and kdm weirdness
On Sat, Dec 01, 2001 at 12:59:27PM +0100, Malte Cornils wrote: > Another thing that's not exactly well-working, although probably not > a packaging issue, is that kdf always crashes when LANG is set to > something else than English/C. For example, yes..this is a known problem which has existed for quite some time and was reported to KDE several months ago. > Another issue can be experienced when you start the kdm control > center module and become root, go to the "Users" tab and click on > the icon button to open a user-defined icon. Whichever icon I select > gets scaled down to 32x32 automagically, which is way to small (I > think the default size is 64x64). Copying the .png manually to the > appropriate config directory works as expected (the image file has > the original size) didn't know about this one... -- 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: kdf crash and kdm weirdness
"Ivan E. Moore II" wrote: > [kdf crashing if locale != English] > yes..this is a known problem which has existed for quite some time and > was reported to KDE several months ago. oops... now that you say it, I dimly recall having looked at this bug report in the KDE bugtracking system myself a while ago... don't know why I forgot and reported it *again*. Sorry! -Malte #8-)
Re: kdf crash and kdm weirdness
> Another issue can be experienced when you start the kdm control > center module and become root, go to the "Users" tab and click on > the icon button to open a user-defined icon. Whichever icon I select > gets scaled down to 32x32 automagically, which is way to small (I > think the default size is 64x64). > well, that's the expected behaviour. once i manage to implement kdm's new look, this constraint will be even more required. one idea to show full-size icons is the use of .face files in user's home dirs. if a user with a face is selected, it is displayed in the logo area (replacing the logo; the clock should move to some corner of the desktop anyway); the logo area is planned to become 200x200 or something like that. greetings -- Hi! I'm a .signature virus! Copy me into your ~/.signature, please! -- Nothing is fool-proof to a sufficiently talented fool.
Re: kdf crash and kdm weirdness
Oswald Buddenhagen wrote: > > Another issue can be experienced when you start the kdm control > > center module and become root, go to the "Users" tab and click on > > the icon button to open a user-defined icon. Whichever icon I select > > gets scaled down to 32x32 automagically, which is way to small (I > > think the default size is 64x64). > > > well, that's the expected behaviour. once i manage to implement kdm's > new look, this constraint will be even more required. Autoscaling is certainly useful most of the time, but shouldn't it scale to the *right* dimensions? Now, the default icons are 64x64 and any user-supplied icons are 32x32, which looks very weird at the kdm login screen... CU, Yours Malte #8-)
Re: kdf crash and kdm weirdness
"Ivan E. Moore II" wrote:
> On Sat, Dec 01, 2001 at 12:59:27PM +0100, Malte Cornils wrote:
> > Another thing that's not exactly well-working, although probably not
> > a packaging issue, is that kdf always crashes when LANG is set to
> > something else than English/C. For example,
>
> yes..this is a known problem which has existed for quite some time and
> was reported to KDE several months ago.
Well, it rather bothers me so I had to try to create a patch for the
problem. I'm probably doing a million things wrong but it works for
me (tm). Can anyone have a look at it, fix it up so it's non-ugly (I
don't really know C++, and it shows) and apply it in the Debian
packages and/or upstream?
Yours Malte #8-)diff -Naur kdeutils-2.2.2.old/kdf/disklist.cpp kdeutils-2.2.2/kdf/disklist.cpp
--- kdeutils-2.2.2.old/kdf/disklist.cpp Tue Dec 26 16:47:54 2000
+++ kdeutils-2.2.2/kdf/disklist.cpp Sat Dec 1 16:01:50 2001
@@ -24,6 +24,7 @@
*/
#include
+#include
#include
#include
@@ -73,6 +74,10 @@
if (NO_FS_TYPE)
kdDebug() << "df gives no FS_TYPE" << endl;
+
+ // to prevent crashes, set LC_ALL so that df gives parseable
+ // English output
+ setenv("LC_ALL", "C", 1);
disks = new Disks;
disks->setAutoDelete(TRUE);
kmail - local mailbox - feeling dumb
OK, so I use Mutt anyway, but I'm trying to setup kmail for my Mom of all folks and I can't get it to see the local mailbox -- I didn't find anything productive in an archive search so I figured I'd ask here. This is an unstable box, brand new user, no garbage or baggage to mung things up -- fire up kmail, it does it's configuration for first time use -- fine, now there's an address book and Mail directory. I went to Configure KMail -> Network "added" the local mailbox as /var/mail/$user told it to use mutt dotlocks, turned on interval checking and saved ... Tell it to check mail, nothing ... pull down the menu for "Check mail here" and select the local name... nothing. There is mail, I've sent it, I get the shell 'New mail in /var/mail/$user' on shell login. Logged out, tried again ... nothing. What the heck am I missing? -- Hank Marquardt <[EMAIL PROTECTED]> http://web.yerpso.net GPG Id: 2BB5E60C Fingerprint: D807 61BC FD18 370A AC1D 3EDF 2BF9 8A2D 2BB5 E60C
Preferred e-mail client
Hi, is there a way to specify the To: address in `kcmshell email`? I currently have the string konsole --notoolbar --workdir ~/Mail -T [mutt] -e mutt which works pretty well, but doesn't copy the address when I click on an e-mail link. Also, is there a way to encode spaces in that string? TIA, Viktor -- Viktor Rosenfeld WWW: http://www.informatik.hu-berlin.de/~rosenfel/ pgptNT6caohxT.pgp Description: PGP signature
Re: kmail - local mailbox - feeling dumb
On Saturday 01 December 2001 09:50 am, Hank Marquardt wrote: > This is an unstable box, brand new user, no garbage or baggage to mung > things up -- fire up kmail, it does it's configuration for first time > use -- fine, now there's an address book and Mail directory. I went to > Configure KMail -> Network "added" the local mailbox as /var/mail/$user > told it to use mutt dotlocks, turned on interval checking and saved ... > > Tell it to check mail, nothing ... pull down the menu for "Check mail > here" and select the local name... nothing. There is mail, I've sent > it, I get the shell 'New mail in /var/mail/$user' on shell login. > Hank: I also had issues with local mail, and my own experience is lame so I checked each one individually. Firstly, my mail lives in: /var/spool/mail/jaye That might be an issue for you too. Next, all the mail chks failed except: Mutt dotlock (privileged) The (recommended) didn't work here on my Testing Woody box. hth tatah -- Jaye Inabnit\ARS ke6sls\/A GNU-Debian linux user\/ http://www.qsl.net/ke6sls If it's stupid, but works, it ain't stupid. I SHOUT JUST FOR FUN. Free software, in a free world, for a free spirit. Please Support freedom!
Re: klisa
"Ivan E. Moore II" <[EMAIL PROTECTED]> wrote: > --snip-- < > > I did modify it. from lan:/ to lan://localhost/ > > Ivan My appologies, Ivan! I spoke without checking it out fully. I just removed and re-installed the new version, and indeed the change IS in the /usr/share/apps/konqueror/dirtree/remote/lan.desktop file. I guess I got caught in the trap that these sort of changes don't propagate to the "user" .kde files until you re-generate the .kde files, or change it manually. I just fired it up the first time and got the error and wrote the note without looking too deeply. My bad [ Carefully extracting foot from mouth again. ] Thanks again! Cheers, -Don Spoon-
Whereis Ksysctrl?
Seems to be not avalaible in sid and testing.
Debian Updates and X Madness
I am running unstable and after my latest apt-get update session discovered that my mouse did not function, absolutely non-responsive. And now, after bootup my machine displays the line "Debian 3.0". I'm running XFree86 4.1. Under 3.3.6, I could use XF86Setup to set my mouse to PS/2 off of /dev/psaux to regain mouse function. Does anyone have any ideas for under 4.1??? Robert (off my wife's computer running Windows) P.S. If you can't guess, I can't access X at all -- major config file problems!
Re: Debian Updates and X Madness
-BEGIN PGP SIGNED MESSAGE- On Saturday 01 December 2001 05:13 pm, Nancy Tilley wrote: > I am running unstable and after my latest apt-get update session discovered > that my mouse did not function, absolutely non-responsive. And now, after > bootup my machine displays the line "Debian 3.0". > > I'm running XFree86 4.1. Under 3.3.6, I could use XF86Setup to set my > mouse to PS/2 off of /dev/psaux to regain mouse function. > > Does anyone have any ideas for under 4.1??? > > Robert (off my wife's computer running Windows) > > P.S. If you can't guess, I can't access X at all -- major config file > problems! Hey Mr. T. Sure. Simple. Different, but simple. And a couple of ways too. 1. dpkg-reconfigure xserver-xfree86 this will walk you thru a dialog (via dpkg) to reconfigure (rewite XF86Config-4) the xserver. if you're NOT running the xserver-xfree86, I need to ask why/why not 2. vi /etc/X11/XF86Config-4 and find the lines concerning your mouse and correct them. [snip'd from my XF86Config-4 for my USB intelli mouse) Section "InputDevice" Identifier "Generic Mouse" Driver "mouse" Option "CorePointer" Option "Protocol" "ImPS/2" Option "Device""/dev/input/mouse0" # Option "Emulate3Buttons" "true" Option "ZAxisMapping" "4 5" EndSection If you're unsure of what device/mouse type, send me a private mail and we'll get you squared away. 3. xf86cfg which I haven't truely played with (GUI) but is praported to werk well. 4. xf86configwhich is the good old trusty standby for all of us older (give me TEXT) users. :--) Well, hope this helps! p.s. Hello Mrs. T. (seeing how this IS on YOUR account.) - -- __ OutCast Computer Consultants of Central Oregon http://outcast-consultants.redmond.or.us [EMAIL PROTECTED] (541) 504-1388 Toll Free (866) 562-7160 Via IRC at; 205.227.115.251:6667:#OutCasts Via ICQ: UIN 138930 "Failure is not an option...it's bundled with Microsoft" -anonymous- Hi! I'm a .signature virus! Copy me into your ~/.signature, please! "Software is like sex. They're both better when they're free!!" - Linus Torvalds "As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product."
