Red Hat Bugzilla – Bug 222104
invalid name: "0x92c1250/bonobo_iid"
Last modified: 2008-04-08 10:21:15 EDT
Description of problem:
On gnome session starting (just after login) I get error notifications.
The locale is russion and the messages actually appear in russian,
so this is back translated to english (may differ from the original):
An error has occured during loading or saving configuration information for
Null-Applet. Some settings (?) can mailfunction.
Key (switch?) or directory name is invalid: "0x92c1250/bonobo_iid": Must begin
with "/" character.
The latter line is repeated many times with different hex numbers.
I have tried to find those strings (hex numbers and "bonobo_iid") in files
in my ~/ recursively, but have found none.
After closing those error notification windows the gnome session appears
to go on rather well.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Just login to gnome session.
Strange error notifications come out.
Null-Applet should not suffer from such problems.
Actually I don't know what system part is in response for this problem.
This is the list of (maybe) relevant packages installed on the system:
I've run into this before. There is a %p instead of a %s somewhere in the null
applet code. Let me see if I can find the report, and figure out where the fix
went (it obviously missed the fc6 tree if you're hitting the issue)
bug 219807 is a RHEL bug.
It doesn't have an upstream report attached to it, and I can't find a
corresponding fedora report. It looks like I dropped the ball on this one.
Can you try gnome-applets-188.8.131.52-13.fc6 when it lands in -updates-testing ?
It's building now.
I don't see it in
Would you be so kind as to tell me where should I look for the rpm package?
that will be the place. Release engineering hasn't pushed it yet.
gnome-applets-184.108.40.206-13.fc6 has been pushed for fc6, which should resolve this issue. If these problems are still present in this version, then please make note of it in this bug report.
We no longer support Fedora Core 6 and I am currently trying to get my open bug
count down to a more manageable state. I'm going to close this bug as WONTFIX.
If this issue is still a concern for you, would you mind trying to reproduce on
a supported version of Fedora and reopening?
(this is a mass message)
> We no longer support Fedora Core 6 ... would you mind trying
> to reproduce on a supported version of Fedora and reopening?
To my regret I cannot upgrade to a later Fedora release
as since Fedora 7 PATA disks are always treated as SCSI disks
and SCSI disks cannot contain more than 15 partitions,
while I do have more than twenty of them.
It seems I should have to switch to some other Linux distribution.
Out of curiosity, did you file a bug about your "Can't have more than 15
I don't know if it would help, but might be worth a shot.
No, I haven't submitted such a report.
If I'd tried to, then what subsystem/package/category should it go to?
It's more ideological issue than a real technical one.
Moreover, I am quite sure what would they answer me,
they would suggest me to use LVM and close the bug.
Well I have tried using LVM as a replacement for partitioning,
but it turned out to be much harder to manage and maintain
especially if one wants to create a copy of the system,
or to move a disk from one machine to another.
Not mentioning performance and resource penalties of LVM.
IMHO Fedora has got a wrong turn and is moving off from the right way. :(
If you file it against kernel, the bug report should get directed to the right