Login
[x]
Log in using an account from:
Fedora Account System
Red Hat Associate
Red Hat Customer
Or login using a Red Hat Bugzilla account
Forgot Password
Login:
Hide Forgot
Create an Account
Red Hat Bugzilla – Attachment 1455053 Details for
Bug 1595712
high CPU usage of vnc gnome-shell and corrupted vnc screen after resizing vncviewer window to very small
[?]
New
Simple Search
Advanced Search
My Links
Browse
Requests
Reports
Current State
Search
Tabular reports
Graphical reports
Duplicates
Other Reports
User Changes
Plotly Reports
Bug Status
Bug Severity
Non-Defaults
|
Product Dashboard
Help
Page Help!
Bug Writing Guidelines
What's new
Browser Support Policy
5.0.4.rh83 Release notes
FAQ
Guides index
User guide
Web Services
Contact
Legal
This site requires JavaScript to be enabled to function correctly, please enable it.
vnc log
vnc.log (text/plain), 3.11 KB, created by
Tomas Hudziec
on 2018-06-27 14:01:07 UTC
(
hide
)
Description:
vnc log
Filename:
MIME Type:
Creator:
Tomas Hudziec
Created:
2018-06-27 14:01:07 UTC
Size:
3.11 KB
patch
obsolete
> >Xvnc TigerVNC 1.8.0 - built Jun 27 2018 04:35:29 >Copyright (C) 1999-2017 TigerVNC Team and many others (see README.txt) >See http://www.tigervnc.org for information on TigerVNC. >Underlying X server release 12000000, The X.Org Foundation > > >Wed Jun 27 15:48:48 2018 > vncext: VNC extension running! > vncext: Listening for VNC connections on all interface(s), port 5901 > vncext: created VNC server for screen 0 >The XKEYBOARD keymap compiler (xkbcomp) reports: >> Internal error: Could not resolve keysym XF86WWAN >> Internal error: Could not resolve keysym XF86RFKill >Errors from xkbcomp are not fatal to the X server > >Wed Jun 27 15:48:51 2018 > ComparingUpdateTracker: 0 pixels in / 0 pixels out > ComparingUpdateTracker: (1:-nan ratio) >The XKEYBOARD keymap compiler (xkbcomp) reports: >> Internal error: Could not resolve keysym XF86WWAN >> Internal error: Could not resolve keysym XF86RFKill >Errors from xkbcomp are not fatal to the X server > >Wed Jun 27 15:49:48 2018 > Connections: accepted: [::1]::41636 > SConnection: Client needs protocol version 3.8 > SConnection: Client requests security type VeNCrypt(19) > SVeNCrypt: Client requests security type TLSVnc (258) > VNCSConnST: Server default pixel format depth 24 (32bpp) little-endian rgb888 > VNCSConnST: Client pixel format depth 24 (32bpp) little-endian rgb888 > ComparingUpdateTracker: 0 pixels in / 0 pixels out > ComparingUpdateTracker: (1:-nan ratio) > VNCSConnST: FramebufferUpdateRequest 1920x1200 at 0,0 exceeds framebuffer > 960x909 > >Wed Jun 27 15:50:09 2018 > ComparingUpdateTracker: 1.79975 Mpixels in / 1.7584 Mpixels out > ComparingUpdateTracker: (1:1.02351 ratio) > >Wed Jun 27 15:50:23 2018 > ComparingUpdateTracker: 1.0115 Mpixels in / 495.902 kpixels out > ComparingUpdateTracker: (1:2.03972 ratio) > >Wed Jun 27 15:50:28 2018 > ComparingUpdateTracker: 858.575 kpixels in / 433.748 kpixels out > ComparingUpdateTracker: (1:1.97943 ratio) > >Wed Jun 27 15:50:33 2018 > ComparingUpdateTracker: 1.04949 Mpixels in / 694.958 kpixels out > ComparingUpdateTracker: (1:1.51015 ratio) > >Wed Jun 27 15:50:38 2018 > ComparingUpdateTracker: 0 pixels in / 0 pixels out > ComparingUpdateTracker: (1:-nan ratio) > >Wed Jun 27 15:50:45 2018 > ComparingUpdateTracker: 0 pixels in / 0 pixels out > ComparingUpdateTracker: (1:-nan ratio) > >Wed Jun 27 15:50:57 2018 > Connections: closed: [::1]::41636 (Clean disconnection) > EncodeManager: Framebuffer updates: 66 > EncodeManager: Tight: > EncodeManager: Solid: 16 rects, 1.04712 Mpixels > EncodeManager: 256 B (1:16361.9 ratio) > EncodeManager: Bitmap RLE: 1 rects, 16 pixels > EncodeManager: 39 B (1:1.94872 ratio) > EncodeManager: Indexed RLE: 11 rects, 6.77 kpixels > EncodeManager: 4.80273 KiB (1:5.53314 ratio) > EncodeManager: Tight (JPEG): > EncodeManager: Full Colour: 167 rects, 6.32315 Mpixels > EncodeManager: 795.415 KiB (1:31.0552 ratio) > EncodeManager: Total: 195 rects, 7.37705 Mpixels > EncodeManager: 800.506 KiB (1:36.0008 ratio) > TLS: TLS session wasn't terminated gracefully > ComparingUpdateTracker: 0 pixels in / 0 pixels out > ComparingUpdateTracker: (1:-nan ratio)
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 1595712
:
1455028
| 1455053 |
1455054