[Bug 1011145] New: xterm cursor disappears and characters not replaced
http://bugzilla.opensuse.org/show_bug.cgi?id=1011145 Bug ID: 1011145 Summary: xterm cursor disappears and characters not replaced Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: xorg-maintainer-bugs@forge.provo.novell.com Reporter: batpul@gmail.com QA Contact: xorg-maintainer-bugs@forge.provo.novell.com Found By: --- Blocker: --- Created attachment 702816 --> http://bugzilla.opensuse.org/attachment.cgi?id=702816&action=edit xterm has no cursor and characters are not replaced but overstriked. Today upgraded from 42.1 to 42.2. Now the cursor in xterm disappears. I have a white text on a black background with: xterm*vt100*cursorColor: yellow If I don't use any X resources at all then the problem persists in a white xterm. If I type some long command line and scroll backwards I see no cursor and the character under the unvisible cursor is blackened (invisible). Also, the characters are not properly erased when using vi editing mode and replacing. Instead they are overwritten where the previous characters persists as well. See attached screendump. This doesn't happen if xterm is positioned against the left side of the screen or slightly off the left side. It happens only when the xterm is significantly positioned away from the left side. I can open several xterms simultaneously. All xterms to the left side are fine, while those to the right of the screen have this problem. If I use konsole no such problem is detected, but I much prefer xterm or uxterm. Below follows xdpyinfo: $ xdpyinfo name of display: :0 version number: 11.0 vendor string: The X.Org Foundation vendor release number: 11803000 X.Org version: 1.18.3 maximum request size: 16777212 bytes motion buffer size: 256 bitmap unit, bit order, padding: 32, LSBFirst, 32 image byte order: LSBFirst number of supported pixmap formats: 7 supported pixmap formats: depth 1, bits_per_pixel 1, scanline_pad 32 depth 4, bits_per_pixel 8, scanline_pad 32 depth 8, bits_per_pixel 8, scanline_pad 32 depth 15, bits_per_pixel 16, scanline_pad 32 depth 16, bits_per_pixel 16, scanline_pad 32 depth 24, bits_per_pixel 32, scanline_pad 32 depth 32, bits_per_pixel 32, scanline_pad 32 keycode range: minimum 8, maximum 255 focus: window 0x1400022, revert to None number of extensions: 28 BIG-REQUESTS Composite DAMAGE DOUBLE-BUFFER DPMS DRI2 DRI3 GLX Generic Event Extension MIT-SCREEN-SAVER MIT-SHM Present RANDR RECORD RENDER SECURITY SGI-GLX SHAPE SYNC X-Resource XC-MISC XFIXES XFree86-VidModeExtension XINERAMA XInputExtension XKEYBOARD XTEST XVideo default screen number: 0 number of screens: 1 screen #0: dimensions: 1920x1200 pixels (508x317 millimeters) resolution: 96x96 dots per inch depths (7): 24, 1, 4, 8, 15, 16, 32 root window id: 0xcb depth of root window: 24 planes number of colormaps: minimum 1, maximum 1 default colormap: 0x20 default number of colormap cells: 256 preallocated pixels: black 0, white 16777215 options: backing-store WHEN MAPPED, save-unders NO largest cursor: 256x256 current input event mask: 0xfa200c ButtonPressMask ButtonReleaseMask ButtonMotionMask StructureNotifyMask SubstructureNotifyMask SubstructureRedirectMask FocusChangeMask PropertyChangeMask ColormapChangeMask number of visuals: 40 default visual id: 0x21 visual: visual id: 0x21 class: TrueColor depth: 24 planes available colormap entries: 256 per subfield red, green, blue masks: 0xff0000, 0xff00, 0xff significant bits in color specification: 8 bits -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1011145
http://bugzilla.opensuse.org/show_bug.cgi?id=1011145#c1
Stefan Dirsch
This doesn't happen if xterm is positioned against the left side of the screen > or slightly off the left side. It happens only when the xterm is significantly > positioned away from the left side. I can open several xterms simultaneously. > All xterms to the left side are fine, while those to the right of the screen have this problem.
Sounds more like a graphics driver issue to me. Please attach /var/log/Xorg.0.log. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1011145
http://bugzilla.opensuse.org/show_bug.cgi?id=1011145#c2
Max Staudt
http://bugzilla.opensuse.org/show_bug.cgi?id=1011145
http://bugzilla.opensuse.org/show_bug.cgi?id=1011145#c3
--- Comment #3 from Bat Pul
http://bugzilla.opensuse.org/show_bug.cgi?id=1011145
http://bugzilla.opensuse.org/show_bug.cgi?id=1011145#c4
--- Comment #4 from Max Staudt
http://bugzilla.opensuse.org/show_bug.cgi?id=1011145
http://bugzilla.opensuse.org/show_bug.cgi?id=1011145#c5
--- Comment #5 from Bat Pul
http://bugzilla.opensuse.org/show_bug.cgi?id=1011145
Stefan Dirsch
http://bugzilla.opensuse.org/show_bug.cgi?id=1011145
http://bugzilla.opensuse.org/show_bug.cgi?id=1011145#c6
--- Comment #6 from Max Staudt
http://bugzilla.opensuse.org/show_bug.cgi?id=1011145
Max Staudt
http://bugzilla.opensuse.org/show_bug.cgi?id=1011145
http://bugzilla.opensuse.org/show_bug.cgi?id=1011145#c7
--- Comment #7 from Max Staudt
http://bugzilla.opensuse.org/show_bug.cgi?id=1011145
http://bugzilla.opensuse.org/show_bug.cgi?id=1011145#c8
--- Comment #8 from Bat Pul
http://bugzilla.opensuse.org/show_bug.cgi?id=1011145
http://bugzilla.opensuse.org/show_bug.cgi?id=1011145#c9
--- Comment #9 from Bat Pul
http://bugzilla.opensuse.org/show_bug.cgi?id=1011145
http://bugzilla.opensuse.org/show_bug.cgi?id=1011145#c10
--- Comment #10 from Bat Pul
http://bugzilla.opensuse.org/show_bug.cgi?id=1011145
http://bugzilla.opensuse.org/show_bug.cgi?id=1011145#c11
--- Comment #11 from Max Staudt
I don't understand how Mesa could be used, since it isn't linked or loaded by any of the programs according to ldd and lsof.
Since you're on Skylake hardware, you're using the modesetting DDX, a generic Xorg backend for kernel drivers that support the KMS interface. This generic backend has only one way of accelerating 2D graphics, namely GLAMOR, which goes through OpenGL. Yes, the OpenGL that was originally meant for 3D graphics. Mesa implements OpenGL, and most of the 3D acceleration code for Intel GPUs is in Mesa. So you need Mesa for 3D, and thus for 2D acceleration on your machine. Could you please attach a full screen dump so I can have an idea of where you placed the window and the rest of your setup? If you're wary of leaking personal information, please close any applications that may be revealing. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1011145
http://bugzilla.opensuse.org/show_bug.cgi?id=1011145#c12
--- Comment #12 from Bat Pul
http://bugzilla.opensuse.org/show_bug.cgi?id=1011145
http://bugzilla.opensuse.org/show_bug.cgi?id=1011145#c13
--- Comment #13 from Bat Pul
http://bugzilla.opensuse.org/show_bug.cgi?id=1011145
http://bugzilla.opensuse.org/show_bug.cgi?id=1011145#c14
--- Comment #14 from Max Staudt
http://bugzilla.opensuse.org/show_bug.cgi?id=1011145
http://bugzilla.opensuse.org/show_bug.cgi?id=1011145#c15
--- Comment #15 from Max Staudt
http://bugzilla.opensuse.org/show_bug.cgi?id=1011145
http://bugzilla.opensuse.org/show_bug.cgi?id=1011145#c16
--- Comment #16 from Bat Pul
http://bugzilla.opensuse.org/show_bug.cgi?id=1011145
http://bugzilla.opensuse.org/show_bug.cgi?id=1011145#c17
Max Staudt
http://bugzilla.opensuse.org/show_bug.cgi?id=1011145
Max Staudt
http://bugzilla.opensuse.org/show_bug.cgi?id=1011145
http://bugzilla.opensuse.org/show_bug.cgi?id=1011145#c18
Max Staudt
http://bugzilla.opensuse.org/show_bug.cgi?id=1011145
http://bugzilla.opensuse.org/show_bug.cgi?id=1011145#c19
--- Comment #19 from Bat Pul
http://bugzilla.opensuse.org/show_bug.cgi?id=1011145
http://bugzilla.opensuse.org/show_bug.cgi?id=1011145#c20
--- Comment #20 from Max Staudt
http://bugzilla.opensuse.org/show_bug.cgi?id=1011145
http://bugzilla.opensuse.org/show_bug.cgi?id=1011145#c21
Max Staudt
participants (1)
-
bugzilla_noreply@novell.com