kde February 2013

kde@lists.fedoraproject.org

34 participants
28 discussions

Start a nNew thread

kde-4.10 planned as f18 update?
by Neal Becker 08 Feb '13

08 Feb '13

Is it planned to have kde-4.10 as an f18 update (i.e, in fedora, not fedora- kde)?

1 0

systemd in unstable repo ?
by Ed Greshko 06 Feb '13

06 Feb '13

-- Don't be bullied by the judgmental grammar and spelling police.

1 0

kde 4.9.98 for F17
by Gilboa Davara 06 Feb '13

06 Feb '13

Hello Rex, Due to anaconda / fedup issues I will most likely have to skip F18 on most of my workstations (neither one seems to be capable of handling LVM+MD+Luks). Any chance of getting 4.9.9x and down the road, 4.10.9x to kde-unstable/f17? Thanks, - Gilboa

4 5

Akonadi/MySQL problem this morning
by Timothy Murphy 04 Feb '13

04 Feb '13

I'm unable to start KMail in Fedora-18, with the error message "The Akonadi personal information service is not operational" Further details are: "MySQL server log contains errors. Akonadi control process not registered at D-Bus. Akonadi server process not registered at D-Bus." I think this happened on updating kdepim last night as part of a general update after installing Fedora-18. (KMail worked find under Fedora-18 before the update.) The error seems to lie in mysql-server, so I have downgraded this, which required downgrading mysql and mysql-libs also: -------------------------------- [tim@blanche ~]$ sudo yum downgrade mysql-server mysql-libs mysql -------------------------------- But this didn't do the trick ... MySQL error log reads: -------------------------------- 130203 12:39:34 [Note] Plugin 'FEDERATED' is disabled. 130203 12:39:34 InnoDB: The InnoDB memory heap is disabled 130203 12:39:34 InnoDB: Mutexes and rw_locks use GCC atomic builtins 130203 12:39:34 InnoDB: Compressed tables use zlib 1.2.7 130203 12:39:34 InnoDB: Using Linux native AIO 130203 12:39:34 InnoDB: Initializing buffer pool, size = 8.0M 130203 12:39:34 InnoDB: Completed initialization of buffer pool 130203 12:39:34 InnoDB: highest supported file format is Barracuda. InnoDB: Log scan progressed past the checkpoint lsn 44067934793 130203 12:39:34 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Error: tried to read 16384 bytes at offset 0 23822336. InnoDB: Was only able to read -1. 130203 12:39:38 InnoDB: Operating system error number 5 in a file operation. InnoDB: Error number 5 means 'Input/output error'. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.5/en/operating-system-error- codes.html InnoDB: File operation call: 'read'. InnoDB: Cannot continue operation. -------------------------------- Any suggestions gratefully received. -- Timothy Murphy e-mail: gayleard /at/ eircom.net tel: +353-86-2336090, +353-1-2842366 s-mail: School of Mathematics, Trinity College Dublin

3 2

Can't set timezone from KDE widget
by Patrick O'Callaghan 04 Feb '13

04 Feb '13

F18, KDE 4.9.5 When I try to set my timezone using the KDE settings widget, I get an error popup: Error setting new time zone. Note that the widget doesn't ask for any authentication. Any thoughts? poc

4 4

Should kscreen "Provides: kde-display-management"?
by Mary Ellen Foster 04 Feb '13

04 Feb '13

Hello all, I have kscreen installed from fedora updates-testing, and I have kde-unstable enabled. Trying to do an update today, I get the following: Processing Conflict: 1:kscreen-0.0.71-2.fc18.x86_64 conflicts kded_randrmonitor --> Finished Dependency Resolution Error: kscreen conflicts with kded_randrmonitor-4.9.98-3.fc18.x86_64 However, I can't just remove kded_randrmonitor, as it provides kde-display-management which is needed by kde-workspace. And I can't exclude kded_randrmonitor from the update because it requires the same version of kde-workspace. If kscreen is meant to conflict with kded_randrmonitor, should it also provde kde-display-management? That would fix the above yum problem, but only if kscreen does actually provide something comparable to the randr thing. All the best, MEF -- Mary Ellen Foster -- http://www.macs.hw.ac.uk/~mef3/ Interaction Lab -- http://www.macs.hw.ac.uk/InteractionLab School of Mathematical and Computer Sciences, Heriot-Watt University Heriot-Watt University is a Scottish charity registered under charity number SC000278

2 1

possible to distro-sync from 4.10 to f18?
by Neal Becker 02 Feb '13

02 Feb '13

After updating to 4.10 from kde-unstable, I want to go back to f18 stock (because DPMS is broken and I don't know how to fix it). But yum distro-sync gives: --> Finished Dependency Resolution Error: Package: nepomuk-widgets-4.10.0-1.fc18.x86_64 (@kde-unstable) Requires: nepomuk-core-libs(x86-64) >= 4.10.0 Removing: nepomuk-core-libs-4.10.0-1.fc18.x86_64 (@kde-unstable) nepomuk-core-libs(x86-64) = 4.10.0-1.fc18 Downgraded By: nepomuk-core-libs-4.9.5-1.fc18.x86_64 (updates) nepomuk-core-libs(x86-64) = 4.9.5-1.fc18 Available: nepomuk-core-libs-4.9.4-2.fc18.x86_64 (fedora) nepomuk-core-libs(x86-64) = 4.9.4-2.fc18 You could try using --skip-broken to work around the problem

3 2

screen lock/power mgmt not working (4.9.98)
by Neal Becker 02 Feb '13

02 Feb '13

kdelibs-4.9.98-1.fc18.x86_64 I have set in screen locker: start auto after 10 min require pw after 60 sec And in battery monitor settings screen energy saver: switch off after 10 min Same as I've always had. But this morning, I see that pw prompt is still sitting on screen, it had not switched off. Can you spell "burn in"?

2 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

kde February 2013