Qt5 plan
by Sonic
Hi.
Just asking out of curiosity. When Qt5 is released, what will be our
packaging plan? Will Qt4 and Qt5 co-exist as Qt3/Qt4 do now?
regards,
Syam
7 years, 2 months
KDE 4.9.1 -> bug in konqueror after open a new tab
by Reindl Harald
4.9.1 is working really smooth - thank you!
only one bug in konqueror makes me crazy sice 4.9.0 builds
* CTRL+T -> New Tab
* address bar doe snot get the focus
* typing / opens the useless "quick search" at the bottom
7 years, 2 months
KDE 4.9.1 rocks.
by linux guy
Subject says it all.
I love the Dolphin enhancements.
Keep up the good work !
7 years, 2 months
Akonadi fails to start: Unable to add column 'version' to table 'SchemaVersionTable'
by Garry Williams
I recently updated from updates-testing to get:
akonadi-1.8.0-1.fc17.x86_64
kdepimlibs-4.9.1-3.fc17.x86_64
kdepimlibs-akonadi-4.9.1-3.fc17.x86_64
kdepim-libs-4.9.1-1.fc17.x86_64
kdepim-4.9.1-1.fc17.x86_64
kdepim-runtime-libs-4.9.1-1.fc17.x86_64
kdepim-runtime-4.9.1-1.fc17.x86_64
and others.
This didn't go as expected.
The first problem was that yum wanted to remove mysql for
dependencies. I added --setopt=clean_requirements_on_remove=0 to fix
that. This was the first hint that I did something wrong. :-(
Next, after restarting the desktop, I got this:
Test 6: ERROR
--------
MySQL server default configuration not found.
Details: The default configuration for the MySQL server was not
found or was not readable. Check your Akonadi installation is complete
and you have all required access rights.
Another hint.
I found a copy of the missing file in
/usr/share/kde4/apps/digikam/database/mysql-global.conf
and copied it to /etc/akonadi .
Now I'm stuck on this error:
"Unable to add column 'version' to table 'SchemaVersionTable'.
Query error: 'Table 'akonadi.SchemaVersionTable' doesn't exist
QMYSQL: Unable to execute query'"
Unable to initialize database.
What am I doing wrong?
(Incidentally, sqlite is hopeless. I tried that after the first error
and akonadi consumes all of the CPU resource without any hint that it
will subside.)
--
Garry Williams
7 years, 2 months
laptop external monitor change in F17
by Zebee Johnstone
I upgraded to Fedora 17 using a new install of / but keeping my old
/home on a different partition.
My laptop is usually attached to a dock, and f16 handled that fine. I
had the 2 displays one on top of the other and the higher resolution
external display had its high resolution and the lower resolution
laptop one kept its. I usually have the laptop closed and don't use
it.
But now there's a "unify" checkbox in system settings and if I use
that then the external display is forced to the low laptop resolution
but if I don't unify then the "main" display is the laptop and various
saved windows are not on the external monitor. I can't work just
using the external monitor but have to have both open.
So I have to disable the laptop display which is annoying. (and what
effect would saving that have if I boot up without the external
monitor?)
is there a way to get back to the previous behaviour?
Zebee
7 years, 2 months
Version discrepancy
by Eli Wapniarski
Hi all
I just noticed a versioning discrepancy.... I am assuming that there is no
impact by the discrepancy, but I just wanted to make sure.
kde-settings(*) noarch 4.8-19.fc17 updates
kde(*) 4.9.1-5.fc17 kde-redhat-testing
kdm 4.9.1-5.fc17 kde-redhat-testing
... etc
Thanks for any insight
Eli
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
7 years, 2 months
Re: yum update error with kde-unstable
by Rex Dieter
Enable kde-testing
-- rex
----- Reply message -----
From: "Sonic" <get.sonic(a)gmail.com>
Date: Sat, Sep 22, 2012 7:54 pm
Subject: yum update error with kde-unstable
To: "KDE on Fedora" <kde(a)lists.fedoraproject.org>
It's been like this for a couple of days now:
--> Finished Dependency Resolution
Error: Package: calligra-reports-map-element-2.5.1-1.fc17.x86_64 (updates)
Requires: libmarblewidget.so.13()(64bit)
Available: 1:marble-libs-4.8.3-1.fc17.x86_64 (fedora)
libmarblewidget.so.13()(64bit)
Available: 1:marble-libs-4.8.5-1.fc17.x86_64 (kde)
libmarblewidget.so.13()(64bit)
Installed: 1:marble-libs-4.9.0-1.fc17.x86_64 (@kde-unstable)
Not found
Error: Package: calligra-krita-2.5.1-1.fc17.x86_64 (updates)
Requires: libkdcraw.so.20()(64bit)
Available: libkdcraw-4.8.3-1.fc17.x86_64 (fedora)
libkdcraw.so.20()(64bit)
Available: libkdcraw-4.8.5-1.fc17.x86_64 (kde)
libkdcraw.so.20()(64bit)
Installed: libkdcraw-4.9.0-1.fc17.x86_64 (@kde-unstable)
Not found
Error: Package: calligra-kexi-map-form-widget-2.5.1-1.fc17.x86_64 (updates)
Requires: libmarblewidget.so.13()(64bit)
Available: 1:marble-libs-4.8.3-1.fc17.x86_64 (fedora)
libmarblewidget.so.13()(64bit)
Available: 1:marble-libs-4.8.5-1.fc17.x86_64 (kde)
libmarblewidget.so.13()(64bit)
Installed: 1:marble-libs-4.9.0-1.fc17.x86_64 (@kde-unstable)
Not found
regards,
Syam
_______________________________________________
kde mailing list
kde(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/kde
New to KDE4? - get help from http://userbase.kde.org
7 years, 2 months
yum update error with kde-unstable
by Sonic
It's been like this for a couple of days now:
--> Finished Dependency Resolution
Error: Package: calligra-reports-map-element-2.5.1-1.fc17.x86_64 (updates)
Requires: libmarblewidget.so.13()(64bit)
Available: 1:marble-libs-4.8.3-1.fc17.x86_64 (fedora)
libmarblewidget.so.13()(64bit)
Available: 1:marble-libs-4.8.5-1.fc17.x86_64 (kde)
libmarblewidget.so.13()(64bit)
Installed: 1:marble-libs-4.9.0-1.fc17.x86_64 (@kde-unstable)
Not found
Error: Package: calligra-krita-2.5.1-1.fc17.x86_64 (updates)
Requires: libkdcraw.so.20()(64bit)
Available: libkdcraw-4.8.3-1.fc17.x86_64 (fedora)
libkdcraw.so.20()(64bit)
Available: libkdcraw-4.8.5-1.fc17.x86_64 (kde)
libkdcraw.so.20()(64bit)
Installed: libkdcraw-4.9.0-1.fc17.x86_64 (@kde-unstable)
Not found
Error: Package: calligra-kexi-map-form-widget-2.5.1-1.fc17.x86_64 (updates)
Requires: libmarblewidget.so.13()(64bit)
Available: 1:marble-libs-4.8.3-1.fc17.x86_64 (fedora)
libmarblewidget.so.13()(64bit)
Available: 1:marble-libs-4.8.5-1.fc17.x86_64 (kde)
libmarblewidget.so.13()(64bit)
Installed: 1:marble-libs-4.9.0-1.fc17.x86_64 (@kde-unstable)
Not found
regards,
Syam
7 years, 2 months
no zoom in korganizer?
by George Avrunin
I posted this on the general Fedora list a week or so ago and haven't
any response, so I'm asking again here.
On a fully-updated F17 x86_64, I decided to try korganizer again after
not using it for a couple of years. I would like to zoom vertically in
the calendar section to increase the vertical space per hour (mostly in
the work week view, but also in the day view). From the documentation
I can find, I should be able to go to Views -> Zoom -> In Vertically,
but all the options in Views -> Zoom are grayed out (in/out x
horizontal/vertical).
I tried with a scratch user account and got the same result, so it's at
least not obviously an issue with my configuration. Is the zoom
disabled on F17 or do I have a more subtle problem?
George
7 years, 2 months
Menu editor
by Emmett Culley
For the last few Fedora releases I've noticed that the menu editor does not work very well. The biggest problem is that it is nearly impossible to drag and drop menu entries to get them ordered how I want them. Mostly I have to delete and recreate an entry to move it. And that doesn't work much of the time either.
A good example is creating a submenu. Using add submenu create a submenu in the menu that was highlighted (good), but it cannot be moved (bad). The only way to move it is to drag it outside any menu, then drop it back into the menu you want it in, but then it goes to the bottom of the list and is still not movable. To make matters worse, much of the time the newly created submenu disappears, along with all of the items under that submenu. Then I have to reset the entire menu to get those items back, which of course, removes all of the changes I made to the menu.
I'd like to drop all seldom used items in to a submenu called "More..." in order to keep the the "everyday" menu uncluttered. I've given up on that.
Is there a file that contains the menu info, both the currently active and the default? Perhaps I can get what I need by editing those files.
Emmett
7 years, 2 months