The usual smooth update to 4.13.1, I noticed again that nepomuk was pulled in
The major issue I have here is when attaching a jpeg to an Email Kmail will
crash. The only way to recover and be able to start Kontact again is to delete
the auto-saved file.
Is anyone else seeing this? I'll go and search kde.bugs and bugzilla later
before I install the debug files.
Fedora 20 - (Heisenbug)
Registered Linux user number #342953
Just wondering if any one wants any help with anything.
I have a reasonable amount of free time.
I just installed a copy of the kde spin and made a image
So I have a fresh copy of kde
I have played around with rpms but that was years ago
This might seem an unusual problem, but...
Long ago (back to FC4), I started using the PwManager program. I kept it
up to, I believe, version 1.2.4 (Lilli) for F11.
Today, at long last, I cannot get it to start. Repeated attempts to
start it have failed.
I have a lot of passwords for a lot of accounts. And if I cannot somehow
resurrect this program, I have lost them all. The only hope is: anything
held in the Thunderbird or Firefox password managers, is still there. I
checked. But sometimes, those passwords get lost and do not propagate to
As it stands, I'm going to be drawing a lot of unwanted attention to
myself by sending password lost/changed requests.
How can I avoid this?
And can anyone recommend a good password-management solution other than
a handwritten Little Black Book of passwords?
I use KDE 4.12.4 on Fedora 20 and I did a system update yesterday and
am currently on Kernel 3.14.3-200.fc20.x86_64. Whenever I log into a
desktop that is not KDE, KDM crashes. I get a black screen for a
second and it goes back to the Login Screen. This is the log of
journalctl -k : http://ur1.ca/hbc9b when I attempt to log into MATE.
You can see on the last couple of lines that there is a segfault. And
this is log from when I log into kde: http://ur1.ca/hbcan.
I did get an SELinux warning about kdm not being allowed write access
to a directory but I'm not sure that's relevant. The problem is that
GDM does work and with GDM I *can* log into to any desktop.
I am using nvidia drivers if that's useful...
Any help would be greatly appreciated.
I have KDE5 installed on my system using dvratil/kde-frameworks COPR repo. I
am having two issues with it.
1. A bunch of package have started complaining about packages being not
2. If I use --nogpgcheck it gives me following error.
file /usr/lib64/libKF5Wallet.so.5 from install of kf5-kwallet-
libs-4.99.0-2.fc20.x86_64 conflicts with file from package kf5-kwallet-
I updated to kde-workspace-4.11.9-4.fc20.1.kde413.x86_64 this morning,
turned the computer off/on and logged in. Kwin crashed immediately. I logged
out and got only a black screen and therewith, vt1 was hung. I logged in to
vt2 and killed gdm, then back to vt1 and logged in again. I noticed that the
active edges no longer worked and then saw that all of the desktop effects
are disabled. I tried to enae and was told that there are 20 effects that
have errors and the desktop effects cannot be enabled.
Prior to this morning's updates, everything was fine.
On 05/03/2014 09:14 AM, Temlakos wrote:
> Well, partly, anyway. After the latest upgrade of Mozilla Firefox, PDF
> files, loaded into a tab, will not print. Nothing comes out of the print
> device except blank pages.
> Where do I file the bug, and against what?
I'd guess against firefox, unless you're using something like kpartsplugin?
I'm having a weird problem (is there any other kind?)
I have a logitech mouse that bluedevil can see and successfully pair. I have
no trouble on any account.
But for some reason, I do not get my mouse to move until after I log into an
account. After I log into an account my mouse works just fine and bluedevil
reports that my mouse is paired and trusted.
When I'm on the kdm the mouse does not move.
When I try to run blutooth-wizard, the program does not see my mouse at all
I've tried googling the problem with no success. I can't help but feel that
I'm missing something very simple, but I'm stumped.
Any advice would be very welcome.
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.