Red Hat Bugzilla – Bug 176095
switching between KDE and Gnome creates confused desktops
Last modified: 2007-11-30 17:11:19 EST
Description of problem:
Use Gnome. Add battery status (this is a laptop in the end!) to panel. Use KDE
for the next login. Add battery status to panel. Use Gnome again in the next
session. Suddenly there are 2 battery status displays on the panel and a second
trash can (this one apparently with deleted files although I am sure I did not
delete anything) appears on the Desktop.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Use Gnome
2. Use KDE
3. Use Gnome
This report targets the FC3 or FC4 products, which have now been EOL'd.
Could you please check that it still applies to a current Fedora release, and
either update the target product or close it ?
Adding componenets to the KDE panel no longer seems to confuse the Gnome panel
(I didn't test with the battery status as in the original message as this
appears now automatically for my laptop in FC6). But Gnome still shows a second
Trash can after a switch to KDE. I assume this is because KDE creates a
~/Desktop/trash.desktop file - which contains as the last line
Component: Software Updater
Summary: TBc3704fb6 config.py:656:_getsysver:TypeError: rpmdb open failed
Traceback (most recent call last):
File "/usr/sbin/pup", line 573, in ?
File "/usr/sbin/pup", line 566, in main
pup = PackageUpdater()
File "/usr/sbin/pup", line 87, in __init__
File "/usr/lib/python2.4/site-packages/pirut/__init__.py", line 124, in __init__
File "/usr/lib/python2.4/site-packages/yum/__init__.py", line 125, in
self.conf = config.readMainConfig(startupconf)
File "/usr/lib/python2.4/site-packages/yum/config.py", line 597, in readMainConfig
vars['releasever'] = _getsysver(startupconf.installroot,
File "/usr/lib/python2.4/site-packages/yum/config.py", line 656, in _getsysver
idx = ts.dbMatch('provides', distroverpkg)
TypeError: rpmdb open failed
Local variables in innermost frame:
ts: <rpmUtils.transaction.TransactionWrapper instance at 0x95a3e6c>
The information we've requested above is required in order
to review this problem report further and diagnose/fix the
issue if it is still present. Since there haven't been any
updates to the report in quite a long time now after we've
requested additional information, we're assuming the problem
is either no longer present in our current OS release, or
that there is no longer any interest in tracking the problem.
Setting status to CANTFIX, however if you still
experience this problem after updating to our latest Fedora
Core release and are still interested in Red Hat tracking
the issue, and assisting in troubleshooting the problem,
please feel free to provide the information requested above,
and reopen the report.
Thank you in advance.
(this message is mass message)