You are not logged in.
Pages: 1
.
Last edited by benplaut (2021-06-25 12:41:13)
Offline
Hm, maybe you have to rebuild your mime-database. But I don't know how you can do that.
Offline
.
Last edited by benplaut (2021-06-25 12:40:22)
Offline
.
Last edited by benplaut (2021-06-25 12:36:52)
Offline
I have the same probleme if anyone find the solution could he say it?
Offline
Is your localhost set up and running?
Offline
my /etc/hosts is well set. How do I see if localhost is running?
Offline
Run ifconfig. If you get something like:
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:44 errors:0 dropped:0 overruns:0 frame:0
TX packets:44 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2200 (2.1 Kb) TX bytes:2200 (2.1 Kb)then it's running.
Offline
.
Last edited by benplaut (2021-06-25 12:35:46)
Offline
this the answer of ifconfig after having launched kile :
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:40 errors:0 dropped:0 overruns:0 frame:0
TX packets:40 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2440 (2.3 Kb) TX bytes:2440 (2.3 Kb)so it seems to work isn't it?
Offline
this the answer of ifconfig after having launched kile :
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:40 errors:0 dropped:0 overruns:0 frame:0 TX packets:40 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2440 (2.3 Kb) TX bytes:2440 (2.3 Kb)so it seems to work isn't it?
Yes, it's basically the same as mine so it should be working.
Offline
No other ideas for my problem?
Offline
I had the same problem for at least couple of weeks, and I solved it yesteday. The culprit was fam.
Certain programs took 2-3 minutes to start and kmail was crashing and freezing all the time. I noticed yesterday that fam was using 100% processor after I tried to start some KDE program and turned it off. Everything started to work normally after that. I had just been lazy for the last couple of weeks and didn't feel like digging around what the problem was. I am so glad I found the reason *phew*, it was starting to be really annoying. The problem only affected KDE programs though. For example firefox and thunderbird worked normally.
Offline
Offline
Pages: 1