Hello,
After having successfully completed 'yum update', empathy stop working well.
Specifically, once executed, it does not show in the Gnome notification area even it appears in the process list.
I attach a log file created with empathy-debugger.
Note: I use empathy for chatting with gtalk.
Hope this help.
Thank you very much.
Best,
-- Marco
On 07/21/2010 05:31 PM, Marco Guazzone wrote:
Hello,
After having successfully completed 'yum update', empathy stop working well.
Specifically, once executed, it does not show in the Gnome notification area even it appears in the process list.
I attach a log file created with empathy-debugger.
Note: I use empathy for chatting with gtalk.
https://bugzilla.redhat.com/show_bug.cgi?id=616506
Try, yum downgrade empathy
Rahul
On Wed, Jul 21, 2010 at 2:05 PM, Rahul Sundaram metherid@gmail.com wrote:
On 07/21/2010 05:31 PM, Marco Guazzone wrote:
Hello,
After having successfully completed 'yum update', empathy stop working well.
Specifically, once executed, it does not show in the Gnome notification area even it appears in the process list.
I attach a log file created with empathy-debugger.
Note: I use empathy for chatting with gtalk.
https://bugzilla.redhat.com/show_bug.cgi?id=616506
Try, yum downgrade empathy
Thanks!
By simply executing 'yum downgrade empathy' I get a dependency resolution error:
--- [error] --- $ sudo yum downgrade empathy Loaded plugins: presto, refresh-packagekit Setting up Downgrade Process Resolving Dependencies --> Running transaction check ---> Package empathy.x86_64 0:2.30.1-2.fc13 set to be updated --> Processing Dependency: libedataserver-1.2.so.11()(64bit) for package: empathy-2.30.1-2.fc13.x86_64 ---> Package empathy.x86_64 0:2.30.2-3.fc13 set to be erased --> Finished Dependency Resolution Error: Package: empathy-2.30.1-2.fc13.x86_64 (fedora) Requires: libedataserver-1.2.so.11()(64bit) Available: evolution-data-server-2.30.1-2.fc13.x86_64 (fedora) You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest --- [/error] ---
Instead, by adding the "--skip-broken" flag, the empathy app is completely removed from my system :(
--- [msg] --- $ sudo yum --skip-broken downgrade empathy Loaded plugins: presto, refresh-packagekit Setting up Downgrade Process Resolving Dependencies --> Running transaction check ---> Package empathy.x86_64 0:2.30.1-2.fc13 set to be updated --> Processing Dependency: libedataserver-1.2.so.11()(64bit) for package: empathy-2.30.1-2.fc13.x86_64 ---> Package empathy.x86_64 0:2.30.2-3.fc13 set to be erased --> Finished Dependency Resolution --> Running transaction check ---> Package empathy.x86_64 0:2.30.1-2.fc13 set to be updated --> Finished Dependency Resolution --> Running transaction check ---> Package empathy.x86_64 0:2.30.2-3.fc13 set to be erased --> Finished Dependency Resolution
Packages skipped because of dependency problems: empathy-2.30.1-2.fc13.x86_64 from fedora
Dependencies Resolved --- [/msg] ---
-- Marco
On Wed, Jul 21, 2010 at 7:28 AM, Marco Guazzone marco.guazzone@gmail.com wrote:
On Wed, Jul 21, 2010 at 2:05 PM, Rahul Sundaram metherid@gmail.com wrote:
On 07/21/2010 05:31 PM, Marco Guazzone wrote:
Hello,
After having successfully completed 'yum update', empathy stop working well.
Specifically, once executed, it does not show in the Gnome notification area even it appears in the process list.
I attach a log file created with empathy-debugger.
Note: I use empathy for chatting with gtalk.
https://bugzilla.redhat.com/show_bug.cgi?id=616506
Try, yum downgrade empathy
Thanks!
There is now a working temporary solution in the bug report Rahul indicated. You can run this command:
chcon -t bin_t /usr/libexec/mission-control* /usr/libexec/telepathy*
To get the software working again (this fixed it for me, as well). There is an SE Linux policy fix now in updates pending. https://admin.fedoraproject.org/updates/selinux-policy-3.7.19-39.fc13
I'm interested, however, in the last question asked in that bug report:
Dawid Zamirski 2010-07-21 16:08:13 EDT
Hi,
I'm just wondering one thing - how come I was affected by this selinux issue when I have selinux set to permissive mode? Shouldn't it be just logged by the setrobleshooter and keep empathy running? Is selinux still blocking some stuff even when in permissive mode?
Regards
Does anyone here have some insight with regards that question?
-- Chris