Discussion:
Pleasant Surprise in finding 4.0.83
kwhiskerz
2008-06-21 05:18:36 UTC
Permalink
How unexpected, so soon after 4.0.82! Hope the updates come more frequently,
to keep on partaking of the repairs.


A question: kdebindings is still in 4.0.80? Is it no longer part of the latest
kde or do I still keep it?


In order to install 4.0.83, it was sadly necessary to rpm -e digikam libkipi
libkdcraw kipi-plugins. Digikam is the program I use to look at photos. I will
have to content myself with gwenview, which has never appealed, but perhaps in
kde4 it is better.


I don't know if this list is the place to report bugs, but here goes:


- when korganizer/kontakt signals a number of reminders that occur at the same
time, selectin nend dismissing it dismisses the whole list. Don't know whether
the reboot or power off problem with forgetting reminders still exists.


- korganizer still does not put itself into the system tray. Supposedly, the
reminder daemon is still supposed to be running, but that wasn't the case in
4.0.82 and earlier. I will know in a day or so.


- networkmanager is not in the system tray.


- the picture frame plasmoid still jumps around on the screen instead of
staying in one place and resizing itself appropriately, like was the case in
4.0.4 with the extragear package.


Other than that, I cannot tell if anything is different yet.
kwhiskerz
2008-06-21 05:25:56 UTC
Permalink
As you just saw, the kmail editing problem still remains. I was unable to edit
"selecting and dismissing" in my previous posting. What is new, and worse, was
that now the delete button made the text before the cursor get erased and
there was no way to instert text like it is supposed to work. A work in
progress, this is, but from a 'mere user' perspective, I do not understand how
things that used to work don't anymore. Is the wheel being reinvented? I am
not complaining, however. In one month... things should be much better.
Despite blemishes, it is usable.
José Matos
2008-06-21 09:39:56 UTC
Permalink
Post by kwhiskerz
How unexpected, so soon after 4.0.82! Hope the updates come more
frequently, to keep on partaking of the repairs.
In order to install 4.0.83, it was sadly necessary to rpm -e digikam
libkipi libkdcraw kipi-plugins. Digikam is the program I use to look at
photos. I will have to content myself with gwenview, which has never
appealed, but perhaps in kde4 it is better.
The problem is simple:
Transaction Check Error:
file /usr/share/icons/hicolor/128x128/apps/kdcraw.png from install of
kdegraphics-4.0.83-1.fc9.i386 conflicts with file from package
libkdcraw-0.1.3-2.fc9.i386
file /usr/share/icons/hicolor/32x32/apps/kdcraw.png from install of
kdegraphics-4.0.83-1.fc9.i386 conflicts with file from package
libkdcraw-0.1.3-2.fc9.i386
file /usr/share/icons/hicolor/48x48/apps/kdcraw.png from install of
kdegraphics-4.0.83-1.fc9.i386 conflicts with file from package
libkdcraw-0.1.3-2.fc9.i386
file /usr/share/icons/hicolor/64x64/apps/kdcraw.png from install of
kdegraphics-4.0.83-1.fc9.i386 conflicts with file from package
libkdcraw-0.1.3-2.fc9.i386
file /usr/share/icons/hicolor/16x16/apps/kipi.png from install of
kdegraphics-4.0.83-1.fc9.i386 conflicts with file from package
libkipi-0.1.5-4.fc9.i386
file /usr/share/icons/hicolor/22x22/apps/kipi.png from install of
kdegraphics-4.0.83-1.fc9.i386 conflicts with file from package
libkipi-0.1.5-4.fc9.i386
file /usr/share/icons/hicolor/32x32/apps/kipi.png from install of
kdegraphics-4.0.83-1.fc9.i386 conflicts with file from package
libkipi-0.1.5-4.fc9.i386
file /usr/share/icons/hicolor/48x48/apps/kipi.png from install of
kdegraphics-4.0.83-1.fc9.i386 conflicts with file from package
libkipi-0.1.5-4.fc9.i386

Forcing the install using rpm by hand shortcircuited the problem. :-)
--
José Abílio

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
kwhiskerz
2008-06-21 15:42:03 UTC
Permalink
Post by José Matos
file /usr/share/icons/hicolor/128x128/apps/kdcraw.png from install of
kdegraphics-4.0.83-1.fc9.i386 conflicts with file from package
libkdcraw-0.1.3-2.fc9.i386
file /usr/share/icons/hicolor/32x32/apps/kdcraw.png from install of
kdegraphics-4.0.83-1.fc9.i386 conflicts with file from package
libkdcraw-0.1.3-2.fc9.i386
file /usr/share/icons/hicolor/48x48/apps/kdcraw.png from install of
kdegraphics-4.0.83-1.fc9.i386 conflicts with file from package
libkdcraw-0.1.3-2.fc9.i386
file /usr/share/icons/hicolor/64x64/apps/kdcraw.png from install of
kdegraphics-4.0.83-1.fc9.i386 conflicts with file from package
libkdcraw-0.1.3-2.fc9.i386
file /usr/share/icons/hicolor/16x16/apps/kipi.png from install of
kdegraphics-4.0.83-1.fc9.i386 conflicts with file from package
libkipi-0.1.5-4.fc9.i386
file /usr/share/icons/hicolor/22x22/apps/kipi.png from install of
kdegraphics-4.0.83-1.fc9.i386 conflicts with file from package
libkipi-0.1.5-4.fc9.i386
file /usr/share/icons/hicolor/32x32/apps/kipi.png from install of
kdegraphics-4.0.83-1.fc9.i386 conflicts with file from package
libkipi-0.1.5-4.fc9.i386
file /usr/share/icons/hicolor/48x48/apps/kipi.png from install of
kdegraphics-4.0.83-1.fc9.i386 conflicts with file from package
libkipi-0.1.5-4.fc9.i386
Forcing the install using rpm by hand shortcircuited the problem. :-)
I thought of that, but I thought that it was possible that these libraries
might now be included in kde itself, so I didn't want to force anything. As
per your method: what would happen when libkipi gets updated? Would you have
to force update to avoid conflict with kdegraphics?
José Matos
2008-06-22 07:48:44 UTC
Permalink
Post by kwhiskerz
I thought of that, but I thought that it was possible that these libraries
might now be included in kde itself, so I didn't want to force anything. As
per your method: what would happen when libkipi gets updated? Would you
have to force update to avoid conflict with kdegraphics?
Based on the error above the only problem is that the icons are duplicated.
This is work in progress and it is normal for icons to change package.

Regarding the update, if the conflict remains then the update process is
broken in the same way it was here. Usually this kind of problems are easy to
fix and most of the time in the next update the problem is gone.

Notice though that by using rpm by hand you should be prepared to grab the
broken pieces if something goes terribly wrong. :-)
--
José Abílio

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
Loading...