Since upgrading from FC14 to FC16, I've had several Plasma Desktop
crashes that occurred when I was switching between desktops. The crash
traceback appears to match the one associated with this KDE bug ticket:
A fix has been committed for this bug. Any word on when this fix will find
its way into the FC16 fedora-updates repository?
I am using Fedora 16(x86_64) version,with the Default Desktop being "KDE
PLasma Workspace 4.7".
Everything is functional and running smoothly,except such messages:
google-chrome-stable Process /opt/google/chrome/chrome was killed by signal
11(SIGSEGV) 2012-01-29 22:25
is popping up in "Automatic Bug Reporting Tool".
Please,Help me regarding this.
KMail on my Fedora-16 laptop still has several problems,
when used with email on my CentOS-6.2 server.
1. The Tools=>Find Messages facility seems to be failing completely.
(As far as I can see it has been getting worse, not better.)
I cannot get any response,
eg when searching for "the" in 2000 messages ...
Is there some trick I'm overlooking?
Or is some plugin or additional program required?
2. It seems to be impossible to create a new top-level folder,
under a specific account.
3. The whole folder arrangement seems to have got screwed up
after moving from KMail to KMail2.
Eg the Search folder seems to have a whole collection of subfolders.
e-mail: gayleard /at/ eircom.net
tel: +353-86-2336090, +353-1-2842366
s-mail: School of Mathematics, Trinity College Dublin
Fedora 15 x86_64, konqueror 4.6.5
I have a 500Gb folder of video files and snapshots, foo.mpg and
foo.mpg.png. During processing I rename to foo.mpg.old and create a
new foo.mpg file; if the process seems to have worked I usually then
Until recently 'konqueror sort by file type' always put the file to be
deleted at the top of the window. Now it may be at the top, the middle
or the bottom. This is only mildly inconvenient, but it _is_ a change
and I suppose it could have other consequences. I haven't seen it
I've reported this problem 2 years ago:
The problem is still present in F15 KDE Spin. ¿Could we please find some
kind of solution? Again, I'm willing to help in any way, but I think that
this problem must be priorized by the KDE SIG, especially since Anaconda
devs have stated that they will not fix the problem (see comment 6).
Kevin Kofler suggested to create a kdialog wrapper. Is it possible? I think
even I can help with that part of the solution.
Christian González G.
I was so happy to see, maybe 1 year back, that fedora/kde had finally progressed
to the point that when I tried to add my home printer it was autodetected, and I
didn't have to specify the make, model, etc.
Not any more. Seems pretty broken now.
I seem to have 3 ways to try to add a printer. I can use system settings (kde).
This, unlike the other ways, actually works. But it doesn't detect my printer,
and I do need to select make/model etc.
The other two ways I find by opening application launcher and search for 'print'
which shows 2 items, 1 called 'printer configuration' and 1 called 'printing'.
Neither of them work at all. The first gives me 'cups-authorization-cancelled'
when I try to add a new printer, without having ever asked for any
authorization. (This seems to be just another way to get to the kde printer
config dialog, but a broken one). The other seems like a gnome version. IIRC
this one also fails but later in the process.
For some reason whenever I start okular it always start fully maximized, i.e.
it doesn't remember its last state of windows size(e.g. resized, not
maximized). It doesn't matter how I open it, it cant be from command-line or
from clicking PDF file.
Is anyone else seeing this ?
Okular 0.13.3, KDE 4.7.4, fully updated F16.
Since moving to f16 (from f14) sometimes my screen goes blanks for no
apparent reason. KDE power setting and screen saver settings seem OK.
Also, it doesn't happen on every KDE login but when it does its like the
computer has turned off and there is no video signal and the monitor
goes to sleep until I move the mouse or press a key. Then monitor might
only stays on a few seconds until it goes off again.
Sometimes logging off and back on fixes it. Today it seems to be OK. Not
sure if this is h/w or s/w caused.
I recently upgraded from f14 to f16. Some of the kslideshow transitions
are now painfully slow, especially ones where one pictures fades into
another. These were fine on f14. Any idea what would cause this?
I removed the configuration file ~/.kde/share/config/kslideshow.kssrc
and re-entered my configuration (after logout/in) and it didnt' help.
Otherwise, graphically, the system seems fine.
(Seems like I remember seeing this same problem many KDE versions back
it it eventually went away.)