The comments in https://bugs.kde.org/show_bug.cgi?id=152030 imply that
the end-user is free to simply use/install a different theme which
actually does honor the active/inactive color settings. However, it
doesn't seem like any of the 9 schemes that ship with Ubuntu 12.10
actually do honor those se
Upstream has determined that this has been fixed in the latest version
of digikam (or at least, they cannot reproduce the bug). Unfortunately,
they're not interested in fixing the version that people actually use.
Hopefully somebody involved with Ubuntu can identify and backport a fix.
--
digikam
I attempted to report this upstream and have this bug track that, but
bugs.kde.org is broken right now, at least for reporting bugs.
** Bug watch added: KDE Bug Tracking System #233691
http://bugs.kde.org/show_bug.cgi?id=233691
** Also affects: digikam via
http://bugs.kde.org/show_bug.cgi?i
Public bug reported:
Binary package hint: digikam
Application: digikam (1.1.0)
KDE Platform Version: 4.4.2 (KDE 4.4.2)
Qt Version: 4.6.2
Operating System: Linux 2.6.32-19-generic i686
Distribution: Ubuntu lucid (development branch)
Steps: Select the "Albums" view/tab, navigate to an album which
In the words of a friend "It's too buggy in the current release, so we
can't upgrade to the version that works". This is absolutely ridiculous
from an end-user perspective. While I can understand the rule in
general, in this case, it's the *exact* opposite of what would be best
for users.
Just to
So I have to enable a non-default repository whose name is
"**Unsupported** updates"?
Why not just ship this as a regular update; almost every single Ubuntu
user who uses digikam is going to be exposed to this bug, and if not
then by the sound of it probably some other known/fixed bug. Shipping
th
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/38006572/Dependencies.txt
** Attachment added: "XsessionErrors.txt"
http://launchpadlibrarian.net/38006573/XsessionErrors.txt
** Bug watch added: KDE Bug Tracking System #223059
http://bugs.kde.org/show_bug.cgi?id=223
Public bug reported:
Binary package hint: digikam
Please see here for background:
https://bugs.kde.org/show_bug.cgi?id=223059
The digikam in Ubuntu Karmic is a beta version with a huge number of
known bugs (>200). It needs to be upgraded to the 1.0.0 release to solve
them all. In particular, I'm
For me, on a Wind U100, the BIOS upgrade DOES solve the problem, when I
upgrade correctly.
* Upgrading using the method in comment 264 did NOT solve the problem
for me. The BIOS setup screens claimed the new BIOS was installed, but I
still had the problem.
* Upgrading the BIOS using FreeDOS on a
