You are not logged in.

Dear visitor, welcome to KDE-Forum.org. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

bizshop

Beginner

  • "bizshop" started this thread

Posts: 5

Location: Port Angeles

Occupation: Webmaster

  • Send private message

1

Friday, December 2nd 2005, 7:13am

klipper crashing

My klipper crashes as soon as I try to launch it. I remember some kind of mime problem when it first did it, but now it won't even launch before crashing. I haven't been able to find where the info Klipper keeps is stored, or I'd go in and see if there was something in there strange. Any ideas on how to get this working again?
For mutual success, Steve Veltkamp, BizShop President
1713 E 3rd St, Pt Angeles, WA 98362
Ph: 360-452-2418 Sales: 800-949-8029 Fax: 206.350.7122
http://bizshop.com http://webmasterbiz.com http://pilers.com
Your success shop!

2

Thursday, December 15th 2005, 9:45am

Probably there's something broken in your klipper configuration. The easiest way to restore a working profile is to delete the old one. Look for your klipperrc file, somewhere in your /home/<me>/.kde3.x/share/config directory. You simply delete the file. Then you restart your kde session, a brand new klipperrc will be created automatically if it does not exist. This will probably fix the problem.

This post has been edited 1 times, last edit by "coco-loco" (Dec 15th 2005, 9:46am)


bram85

Professional

Posts: 948

Location: Eindhoven

Occupation: Software Engineer

  • Send private message

3

Friday, December 16th 2005, 11:22am

RE: klipper crashing

Can you produce a backtrace and look at http://bugs.kde.org if this bug is already known? If not, you could submit a new bug then.
An application should never crash, even when the configuration is messed up. So it should be fixed.
Bram Schoenmakers
KDE Netherlands (www.kde.nl)