Created attachment 319161 [details]
output from running tomboy-panel in terminal
After upgrading to F10b, tomboy crashes at startup. Some digging reveals that tomboy works but tomboy-panel crashes. I've included the output in an attachment.
I see exactly the same thing. Running tomboy manually works fine.
It's trying to dlopen "libpanel-applet-2.so" (as opposed to, say, libpanel-applet-2.so.0.2.45), so it fails and crashes if you don't have gnome-panel-devel installed.
I don't remember why this happens/how to fix it.
I think the problem is that libpanel-applet-2 is missing from
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.
More information and reason for this action is here:
Created attachment 328490 [details]
debug output of tomboy
I’m using Fedora 10 with all updates. Tomboy-Panel crashes when I start it. But I receive different errors than mentioned above. A file seems missing:
Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'Mono.Addins
(see attached file)
After installing the package mono-addins.x86_64 I was able to start Tomboy without any error.
So I think mono.addins should be a dependency of tomboy.
Can you please fix this and then finally please close this bug? Would be nice.
mono-addins is a dependency
unfortunately, f-spot is listed as providing the dependency
See bug 442373
It was closed, and if I could figure out how to repoen it I would...
# yum install tomboy
pulls in f-spot (which it should not)
and does not pull in mono-addins (which it should)
# yum install mono-addins
makes tomboy run properly again
I'm seeing the same thing on a Freshly installed F-10 system. "rpm -q --provides f-spot | grep Mono.Addins":
[root@pc21224 ~]# rpm -q --provides f-spot | grep Mono.Addins
mono(Mono.Addins) = 0.3.0.0
mono(Mono.Addins.Gui) = 0.3.0.0
mono(Mono.Addins.Setup) = 0.3.0.0
My problems with tomboy were solved (eventually) with a "yum install mono-addins".
However, I found the package "tasque", which I installed because I could no longer use tomboy, conflicts with mono-addins/tomboy. I could not get tomboy to start until I did a "yum erase tasque".
*** Bug 480958 has been marked as a duplicate of this bug. ***
I can confirm this. Tomboy indeed does not install mono-addins, hence fails to start.
https://bugzilla.redhat.com/show_bug.cgi?id=492200 is a dupe of this btw. And perhaps changing the title makes sense.
I can confirm this and the sollution to install mono-addins too. What is the status? It shouldn't be that hard to update the RPM dependencies for this package...
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '10'.
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 prior to Fedora 10's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 10 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 please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
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.
The process we are following is described here:
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 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.
Thank you for reporting this bug and we are sorry it could not be fixed.