Bug 505970 - gnome-session keeps spawning /usr/libexec/vino-server over and over and over again
Summary: gnome-session keeps spawning /usr/libexec/vino-server over and over and over ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-session
Version: 12
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-06-15 01:16 UTC by Jonathan Kamens
Modified: 2010-12-05 06:51 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-12-05 06:51:08 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jonathan Kamens 2009-06-15 01:16:01 UTC
/usr/libexec/vino-server was crashing reliably on startup (see the other bug I just failed about that).  Each time it crashed, I'd get a bug buddy dialog asking if I wanted to save the report somewhere, and then I'd either save the report or cancel, and then gnome-session would try again to launch vino-server.  This continued for quite a few rounds.  I didn't keep doing it to find out whether gnome-session would ever give up on trying to successfully launch vino-server, but I can't help but suspect that it would have gone on forever.  Perhaps gnome-session should have detected that vino-server was failing and/or just detected that it was launching it repeatedly and eventually stopped trying?

Comment 1 Matthias Clasen 2009-06-18 05:10:26 UTC
This was caused by a gcc bug, causing miscompliation of vino-server. 
Fixed in vino-2.26.1-4.fc12

Comment 2 Jonathan Kamens 2009-06-18 14:05:16 UTC
The vino bug is not what I'm reporting here.  The problem is that when vino was crashing, gnome-session kept on spawning it over and over again.  That shouldn't happen.  There needs to be a failsafe so that when something that gnome-session is trying to spawn keeps crashing, it eventually stops trying to spawn it.

Comment 3 Bug Zapper 2009-11-16 10:12:06 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Bug Zapper 2010-11-04 11:06:40 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  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 '12'.

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 12'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 12 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: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Bug Zapper 2010-12-05 06:51:08 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.


Note You need to log in before you can comment on or make changes to this bug.