Hide Forgot
Created attachment 490823 [details] screenshot See the screenshot attached. How to see what else was installed during the transaction selected? Version-Release number of selected component (if applicable): PackageKit-0.6.12-2.fc14.x86_64 How reproducible: often Actual results: Some rows are too narrow to show their contents. Expected results: Rows resized according to the amount of text contained.
Looks like a GTK+ bug to me.
$ rpm -qa | grep gtk webkitgtk-devel-1.3.10-1.fc14.x86_64 gtk2-debuginfo-2.22.0-1.fc14.1.x86_64 PackageKit-gtk-module-0.6.12-2.fc14.x86_64 gtk3-immodule-xim-2.90.5-1.fc14.x86_64 gtk2-engines-2.20.1-2.fc14.x86_64 gtk-doc-1.15-1.fc14.noarch gtk+-1.2.10-70.fc13.x86_64 pygtk2-2.17.0-7.fc14.x86_64 pywebkitgtk-1.1.6-5.fc14.x86_64 gtkspell-2.0.16-1.fc13.x86_64 gtk-sharp2-devel-2.12.10-3.fc14.x86_64 gtkglext-libs-1.2.0-10.fc12.x86_64 report-gtk-0.20-1.fc14.x86_64 pinentry-gtk-0.8.1-3.fc14.x86_64 gtk-murrine-engine-0.98.1.1-1.fc14.x86_64 pygtksourceview-2.10.1-2.fc14.x86_64 webkitgtk3-1.3.3-1.fc14.x86_64 gtk-recordmydesktop-0.3.8-3.fc14.noarch gtkhtml2-2.11.1-8.fc14.x86_64 webkitgtk-1.3.10-1.fc14.x86_64 gtk-sharp-beans-devel-2.14.0-2.fc14.x86_64 gtk-sharp2-gapi-2.12.10-3.fc14.x86_64 gtk3-devel-2.90.5-1.fc14.x86_64 libcanberra-gtk3-0.25-4.fc14.x86_64 gtk-vnc-0.4.2-4.fc14.x86_64 GConf2-gtk-2.31.91-1.fc14.x86_64 gtkimageview-1.6.4-2.fc14.x86_64 usermode-gtk-1.106.1-1.fc14.1.x86_64 deluge-gtk-1.3.1-2.fc14.noarch gtk2-immodule-xim-2.22.0-1.fc14.1.x86_64 gtkhtml3-3.32.2-1.fc14.x86_64 ibus-gtk3-1.3.9-3.fc14.x86_64 pygtkglext-1.1.0-9.fc14.x86_64 xdg-user-dirs-gtk-0.8-5.fc13.x86_64 gtk2-2.22.0-1.fc14.1.x86_64 pygtk2-libglade-2.17.0-7.fc14.x86_64 gtksourceview2-2.11.2-3.fc14.x86_64 authconfig-gtk-6.1.11-1.fc14.x86_64 gtkmm24-2.22.0-1.fc14.x86_64 python-slip-gtk-0.2.13-1.fc14.noarch gnome-python2-gtkhtml2-2.25.3-29.fc14.1.x86_64 gtk-sharp2-2.12.10-3.fc14.x86_64 clutter-gtk-0.10.8-2.fc14.x86_64 gtk3-2.90.5-1.fc14.x86_64 ibus-gtk2-1.3.9-3.fc14.x86_64 gtk2-devel-2.22.0-1.fc14.1.x86_64 gtk-sharp-beans-2.14.0-2.fc14.x86_64 gtk3-engines-2.90.3.1-4.fc14.x86_64 libcanberra-gtk2-0.25-4.fc14.x86_64
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.