[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-user
Subject:    Icon causes grief -- X-Server crashes
From:       Rob <drifter () stratos ! net>
Date:       1998-07-30 21:03:20
[Download RAW message or body]

Hi,
	
	I just thought I should report this bizarre problem with a
Desktop .kdelnk icon that is causing KDE to crash.  Basically, whenever I
click on this one icon, whether with the left button or the right button,
the X-server crashes.  (The middle button has no effect.)
	The icon in question is an FTP URL pointer.  On my desktop, I have
nine icons arranged non-alphabetically downwards along the left of the
desktop.  The first three are the default icons "Trash," "Templates,"
and "Autostart."  Below that are two program .kdelnk icons for "lpr" and
"kmidi."
	Below that are my two FTP icons: "KDE Home" (which points to
ftp://ftp.kde.org/pub/kde, of course) and "Walnut Creek" (which points to
ftp://wcarchive.cdrom.com).  For what it's worth, these two icons are
followed by two program icons for a network connection shell script and a
folder pointer.
	Here's the problem.  If I click on "KDE Home," KDE will attempt to
contact the URL as it should.  If I click on "Walnut Creek," the X-server
immediately crashes.  No other icon has this problem.  It doesn't matter
whether I have a ppp connection established or not, and "KDE Home" won't
crash if I happen to be off-line.
	I checked the permissions on both files and they are exactly the
same: -rw-r--r--.  In fact, further investigation on the contents of the
file show that both are exactly 206 bytes in size, and have almost the same
content.  The only thing that differs is the URL pointers -- otherwise, the
various configuration lines match, though in a different order.
	I did several experiments on the files to determine what was causing
one to crash and not the other.  Eventually, I wound up doing a:

		$ cp "KDE Home" "Walnut Creek"
		
Even though the files were /exactly/ equal, with the same permissions, "Walnut
Creek" still crashed when clicked and "KDE Home" was just fine.
	For what it's worth, "KDE Home" is position six in the column of
icons, while "Walnut Creek" is just below at position seven.
	Finally, I restored "Walnut Creek" back to its original contents,
but changed its name to "KDE Home2."  Amazingly enough, clicking on it
did /not/ cause the X-server to crash.  Even when I repositioned the icon
(at position nine now) back to position seven and launched it from there,
everything went fine.
	The problem, therefore, seems to be that KDE doesn't like the
/name/ of the .kdelnk.  Why would that be?  Does one of the developers
have something against FreeBSD :)  (Which, by the way, I forgot to mention.
I am using FreeBSD 2.2.7).  There are no non-standard characters (except
the space, which appears in both names) used in the icons.
	I also checked the "kde.errors" and "kde.stdout" log files I keep
after X-server crashes, but neither reported anything about the problem.
I specifically checked both.  However, my X-log reported trapping a
Signal 11 (SEGV, I believe) before shutting down the X-server.
	I'm sorry about the excruciatingly specific details I am providing
and the length of this message.  I just can't see any more of a compact way
to explain it.
	I have included two attachments showing the content of these
files if anyone can help.

	Thanks for the help,
	
		-Rob

--
drifter@stratos.nospam.net (remove nospam to send)
	"Am I the only one that cringes every time I hear somebody refer
to a disk drive as a 'solution'? It's bad enough I have to listen to that
marketing hype from vendors, but now it seems to be infiltrating every-day
conversation. I'll decide if that 9GB hard drive is a 'solution' to my
problem or not, thank you very much..."

["KDE Home" (application/x-kdelnk)]
["Walnut Creek" (application/x-kdelnk)]
================================================================================
                     +++ the KDE user mailing list +++
To unsubscribe from this list send mail to kde-user-request@kde.org with the 
                         **Subject** unsubscribe. 
================================================================================


[prev in list] [next in list] [prev in thread] [next in thread]