Bug 704880 - System unresponsive with 100% cpu after attempting vncserver stop
System unresponsive with 100% cpu after attempting vncserver stop
Product: Fedora
Classification: Fedora
Component: tigervnc (Show other bugs)
x86_64 Linux
unspecified Severity high
: ---
: ---
Assigned To: Adam Tkac
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2011-05-15 12:51 EDT by Bob Gustafson
Modified: 2013-04-30 19:49 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-08-16 08:09:17 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Bob Gustafson 2011-05-15 12:51:01 EDT
Description of problem:

  When I try to stop my vncserver, system hangs with 100% cpu

Version-Release number of selected component (if applicable):

 Whatever is in uptodate f14. It does not respond to vncserver -v

How reproducible:


Steps to Reproduce:
1. Notice that screen has become unresponsive (except for mouse)
2. Notice processor utilization has jumped to 100% (on a 4 core Intel)
3. From another machine, log in using ssh and reboot machine /sbin/shutdown -r now
4. After reboot completes, log in as user.
5. Think about last thing done previously.
6. System-> Administration->Services
7. Select vncserver and click on Stop button
8. Go to step 1 here
Actual results:

  As given above in 'Steps to Reproduce'

Expected results:

  VNCserver should quit, Services dialog box should show vncserver stopped

Additional info:

The last Software Update (about a day ago) included new kernel from System Monitor->System

I think other actions besides System->Administration->Services will also trigger problem, but S->A->S was easiest to find.
Comment 1 Fedora End Of Life 2012-08-16 08:09:20 EDT
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached 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, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

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: 

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