I've reported this problem, but the developers don't seem to care about it --
I regularly receive HTML messages and if I click on the link to render the
HTML and/or load external pictures, it will often cause KMail (Kmail 2) to
crash. Of course, since I don't have the debugging symbols loaded, it doesn't
do a darn bit of good to click on "report" especially as it seems to not want
to interface with bugs.kde.org. :(
IIRC someone said it has to do with the app that is being used to render the
HTML, but that it was hard-coded so couldn't be changed. Anyone know if this
is the case or if there's a "fix" in the works?
Anyone else getting messages like these?
"Unknown error. (Unable to fetch item from backend)"
When starting plasma-desktop or kontact such entries show up in
> Akonadi::EntityTreeModelPrivate::fetchJobDone: Job error: "Unknown error.
> (Unable to fetch item from backend)" for collection: 161
They started showing up after the 4.8.1 update. Was ok with 4.8.0.
:: Christos Lazaridis +41 76 26 82453 ( cell ) ::
:: CERN/EN-MEF-LE (530 R-014) +41 22 76 62789 ( office ) ::
:: Machines & Experimental Facilities Group ::
:: http://chrislaz.net ::
:: There is still something in everything I do that defeats me, ::
:: makes me dissatisfied, challenges me to further effort. ::
:: Sometimes I rise above my level, sometimes I fall below it, ::
:: but always I fall short of the things I dream. ::
:: ~ H.G. Wells, The Island of Dr. Moreau ::
After upgrading from 4.8 to 4.8.1 smooth-tasks crashes plasma
Bug reported upstream:
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
If I put the analog clock widget on my desktop, then I get a series of
errors when KDE starts, viz:
Mar 8 08:22:20 rghquad pulseaudio: module-udev-detect.c:
inotify_init1() failed: Too many open files
Mar 8 08:22:20 rghquad pulseaudio: module.c: Failed to load
module "module-udev-detect" (argument: ""): initialization failed.
Mar 8 08:22:20 rghquad pulseaudio: main.c: Module load failed.
Mar 8 08:22:20 rghquad pulseaudio: main.c: Failed to initialize
Mar 8 08:22:20 rghquad pulseaudio: main.c: Daemon startup failed.
repeating several times. I know this sounds crazy, but it is absolutely
reproducible. Even if the clock is the only widget on the desktop, I get
these errors, plus a dialog box asking me if certain sound devices
should be removed since they weren't found. This is with KDE 4.7.4 on an
The issue has been around since about 23 February, when I reported the
problem on the Fedora list
though I didn't know its cause then. So it must have been caused by some
update around that time.
I'm seeing an odd issue with KDE and screen backlight control. I'm
running Thinkpad T60, with KDE 4.7 (from updates) and unfortunately
the backlight control does not work. Pressing Fn+Home/Fn+End does not
seem to have any effect. I normally have to tweak hotkey mask to
something like 0xffffff in order to have the proper key events appear,
and it does work but only in Gnome and Xfce.
Before anyone suggests reinstalling bash, I've already done it
(otherwise it wouldn't work in Xfce).
Looking at the logs:
- kded debugs:
kded(2495) PowerDevil::BackendLoader::loadBackend: Loading UPower backend...
kded(2495) PowerDevil::BackendLoader::loadBackend: Success!
kded(2495) KDEDPowerDevil::init: Backend loaded, loading core
kded(2495) PowerDevil::Core::loadCore: Core loaded, initializing backend
kded(2495) PowerDevilUPowerBackend::brightness: Screen brightness: 0
<---- why is current brightness 0?
kded(2495) PowerDevilUPowerBackend::init: current screen brightness: 0
kded(2495) PowerDevilUPowerBackend::init: Can suspend
kded(2495) PowerDevilUPowerBackend::init: Can hibernate
kded(2495) PowerDevil::Core::onBackendReady: Backend is ready, KDE
Power Management system initialized
- messages - nothing about backlight helper being activated
- .xsession-errors - nothing related
Since it does not work with 4.7 from updates, I updated to 4.8 from
kde48 repo. Unfortunately, with similar results.
As a last resort I checked with KDE live spin, and amazingly,
backlight control works. So something between the current version of
packages and the one from live KDE spin, things got broken.
Correct me if I'm wrong, but looking at the code, I see that in order
to control the backlight, there's a helper program
(/usr/libexec/kde4/backlighthelper) which starts through dbus
activation, and exposes brigthness, setbrigthness methods. I take that
once started the demon should remain running at lest for some time.
Now in KDE spin, that happens to be the case, I can clearly see
backlighthelper process listed in ps output (there are also logs in
messages, that activation of backlighthelper was successful).
However, right now, no such log is to be found, as if for some reason
backlight helper does not get started.
Any ideas on how to proceed with debugging this?
Did ksysguard get dropped from the F17 live image on purpose? (Hard
to believe since it's only 354K.) Or was it never there to begin with
and I just don't remember installing it manually before?
I ask mainly because I recall something else accidentally got lost due
to the recent packaging split. ksysguard isn't strictly needed on the
live image IMHO because the process viewer in krunner suits most
people just fine.
Yesterday I upgraded from F15 to F16. This went smoothly (almost) but
after the restart there were ugly processes running and tacking much of
the CPU power: tracker-*
AFAIK these processes are the "nepomuk" part of gnome and I don't need
them. Why are the tracker processes activated in a typical KDE environment?
This is a report of the weekly KDE-SIG-Meeting with a summary of the
topics that were discussed. If you want to add a comment please reply
to this email or add it to the related meeting page.
= Weekly KDE Summary =
Time: 2012-02-28 15:00 UTC
Meeting page: https://fedoraproject.org/wiki/SIGs/KDE/Meetings/2012-02-28
Meeting minutes: http://bit.ly/xldRuU
Meeting log: http://bit.ly/AetIRK
= Participants =
= Agenda =
* topics to discuss:
** Fedora 17 alpha post-mortem
** touch interfaces, Fedora Active
* recent bugs:
** #796969, f17 kde reboot does not work, leads back to kdm 
== Summary ==
Fedora 17 Alpha post-mortem
* KDM shutdown/restart issue present in Fedora 17 alpha, we are waiting for more feedback after f17 spread enough
* ACTION: Kevin_Kofler to take a look on systemd support as original author of CK code, jreznik to help with
* KDM also supports non-root session for greeter
* ACTION: to check the possibility of setting it up
f17 kde reboot does not work, leads back to kdm
* kudos to Michal Schmidt for figuring it out
*  update to be tested
touch interfaces, Fedora Active
* first try kickstart for Fedora Active
* we will need package splits for touch interfaces (-mobile subpackages, kdepim, calligra...)
* we need the separate kde-settings profile set up
* ACTION: to check if the plasma-mobile patches are still needed
* ACTION: rdieter to prepare f17-kde koji target/tag
* ACTION: jreznik to start updates when tarballs hits packagers ftp
* AGREED: to backport kio_tar bugfix to f15
* ACTION: Kevin_Kofler to take care about backport
= Next Meeting =
= Links =
Jaroslav Řezník <jreznik(a)redhat.com>
Software Engineer - Base Operating Systems Brno
Office: +420 532 294 275
Mobile: +420 602 797 774
Red Hat, Inc. http://cz.redhat.com/
If so, are the last few pixels of the last character of the hostname cut
Ian Pilcher arequipeno(a)gmail.com
"If you're going to shift my paradigm ... at least buy me dinner first."