[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 <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |CONFIRMED CC| |batpul@gmail.com Flags| |needinfo?(batpul@gmail.com) --- Comment #1 from Stefan Dirsch <sndirsch@suse.com> ---
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 <mstaudt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mstaudt@suse.com --- Comment #2 from Max Staudt <mstaudt@suse.com> --- Can you please also tell us which desktop environment you're using? Is a compositor running? -- 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#c3 --- Comment #3 from Bat Pul <batpul@gmail.com> --- Created attachment 703271 --> http://bugzilla.opensuse.org/attachment.cgi?id=703271&action=edit /var/log/Xorg.0.log With fixed fonts there is no such problem, only with fonts like courier, droid, dejavu, etc. -- 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#c4 --- Comment #4 from Max Staudt <mstaudt@suse.com> --- Bat, could you please tell us whether you're using GNOME, KDE, or some other desktop environment? Is compositing active? What's your hardware (lspci -nn) ? -- 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#c5 --- Comment #5 from Bat Pul <batpul@gmail.com> --- sddm for login and then icewm for windowmanager. No compositing that i'm aware of. 00:00.0 Host bridge [0600]: Intel Corporation Skylake Host Bridge/DRAM Registers [8086:190f] (rev 07) 00:02.0 VGA compatible controller [0300]: Intel Corporation Skylake Integrated Graphics [8086:1912] (rev 06) 00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller [8086:a12f] (rev 31) 00:14.2 Signal processing controller [1180]: Intel Corporation Sunrise Point-H Thermal subsystem [8086:a131] (rev 31) 00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-H CSME HECI #1 [8086:a13a] (rev 31) 00:17.0 SATA controller [0106]: Intel Corporation Sunrise Point-H SATA controller [AHCI mode] [8086:a102] (rev 31) 00:1b.0 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Root Port #19 [8086:a169] (rev f1) 00:1c.0 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #3 [8086:a112] (rev f1) 00:1c.4 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #5 [8086:a114] (rev f1) 00:1c.5 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #6 [8086:a115] (rev f1) 00:1d.0 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #9 [8086:a118] (rev f1) 00:1d.4 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #13 [8086:a11c] (rev f1) 00:1f.0 ISA bridge [0601]: Intel Corporation Sunrise Point-H LPC Controller [8086:a144] (rev 31) 00:1f.2 Memory controller [0580]: Intel Corporation Sunrise Point-H PMC [8086:a121] (rev 31) 00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-H HD Audio [8086:a170] (rev 31) 00:1f.4 SMBus [0c05]: Intel Corporation Sunrise Point-H SMBus [8086:a123] (rev 31) 00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (2) I219-V [8086:15b8] (rev 31) 03:00.0 Ethernet controller [0200]: Intel Corporation I211 Gigabit Network Connection [8086:1539] (rev 03) 04:00.0 Network controller [0280]: Intel Corporation Wireless 8260 [8086:24f3] (rev 3a) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1011145 Stefan Dirsch <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(batpul@gmail.com) | -- 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#c6 --- Comment #6 from Max Staudt <mstaudt@suse.com> --- I set up a system with Leap 42.2, used sddm to log in to IceWM, then started an xterm from which I ran: xterm -fa Courier That second xterm I moved to the bottom right corner of the 1680x1050 screen, and the error did not occur. No idea... except that maybe, for some reason, you're using xf86-video-intel? Can you please check in /var/log/Xorg.0.log or maybe even attach the file to the bug report? xf86-video-intel is slightly broken on Broadwell, and very broken on Skylake. That's why we have resorted to using xf86-video-modesetting by default instead - but maybe an old config of yours overrides this. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1011145 Max Staudt <mstaudt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(batpul@gmail.com) -- 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#c7 --- Comment #7 from Max Staudt <mstaudt@suse.com> --- Uh, just saw that you're using modeset, so xf86-video-intel is ruled out as a cause :( I'm afraid I can't reproduce your issue. Can you please try whether installing a bleeding edge Mesa package helps? You can get binaries for Leap 42.2 from here: https://build.opensuse.org/package/show/X11:XOrg/Mesa -- 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#c8 --- Comment #8 from Bat Pul <batpul@gmail.com> --- I have the same problem with urxvt when I use the following X resources: URxvt*geometry: 88x49 URxvt*font: -misc-droid sans mono-medium-r-normal--0-0-0-0-m-0-iso10646-1 URxvt*jumpScroll: true URxvt*skipScroll: true URxvt*saveLines: 10000 URxvt*scrollBar: true URxvt*scrollBar_right: false URxvt*scrollBar_floating: false URxvt*scrollTtyOutput: false URxvt*scrollTtyKeypress: true URxvt*cursorBlink: false URxvt*cursorColor: yellow URxvt*cursorColor2: #aaaaaa URxvt.iso14755: off URxvt.iso14755_52: off URxvt.perl-lib: .urxvt/ URxvt.perl-ext-common: default,matcher,tabbed URxvt.url-launcher: /usr/bin/firefox URxvt.matcher.button: 1 URxvt.tabbed.tabbar-fg: 7 URxvt.tabbed.tabbar-bg: 8 URxvt.tabbed.tab-fg: 8 URxvt.tabbed.tab-bg: 7 URxvt.tabbed.title: true URxvt.tabbed.title-bg: 8 URxvt.tabbed.title-fg: 7 URxvt*termName: rxvt-256color Then scrolling backwards using Shift-PageUp or replacing characters in the bash command line give bad results. See the attached screendump. 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. See the attached -- 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#c9 --- Comment #9 from Bat Pul <batpul@gmail.com> --- Created attachment 706899 --> http://bugzilla.opensuse.org/attachment.cgi?id=706899&action=edit screendump of urxvt overwrite / replace bug -- 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#c10 --- Comment #10 from Bat Pul <batpul@gmail.com> --- The urxvt resources use google-droid-fonts-20121204-6.1.noarch -- 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#c11 --- Comment #11 from Max Staudt <mstaudt@suse.com> --- (In reply to Bat Pul from comment #8)
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 <batpul@gmail.com> --- Created attachment 707113 --> http://bugzilla.opensuse.org/attachment.cgi?id=707113&action=edit full screen dump of 2 urxvt windows at the top of the screen -- 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#c13 --- Comment #13 from Bat Pul <batpul@gmail.com> --- urxvt windows to the left side are fine. urxvt windows some distance away from the left side are not. see attached fullscreendump.png. the given Mesa url is not recognized as a valid repository by zypper or yast2. -- 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#c14 --- Comment #14 from Max Staudt <mstaudt@suse.com> --- On that page, there is a link "Download Package". Follow that, and you'll get options to install the package(s) for your distribution and machine type: https://software.opensuse.org/download.html?project=X11%3AXOrg&package=Mesa I can try to reproduce the issue one more time in January when I have access to Skylake hardware. But if I can't reproduce it then, I'm afraid I have no way of fixing your bug. -- 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#c15 --- Comment #15 from Max Staudt <mstaudt@suse.com> --- Can you please also attach the output of 'sudo hwinfo'? -- 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#c16 --- Comment #16 from Bat Pul <batpul@gmail.com> --- The new Mesa repo url worked, but the bug persists. hwinfo gives a lot of detailed info. what do you need specifically? -- 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#c17 Max Staudt <mstaudt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(batpul@gmail.com) | --- Comment #17 from Max Staudt <mstaudt@suse.com> --- I wanted to know the exact CPU and chipset, in order to look for a machine that's as close as possible to yours, hardware wise. I'll try to reproduce this one more time in January. If I can't, I'm afraid I can't help. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1011145 Max Staudt <mstaudt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|xorg-maintainer-bugs@forge. |mstaudt@suse.com |provo.novell.com | -- 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#c18 Max Staudt <mstaudt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |patrik.jakobsson@suse.com --- Comment #18 from Max Staudt <mstaudt@suse.com> --- CC Patrik, maybe you've seen this before? -- 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#c19 --- Comment #19 from Bat Pul <batpul@gmail.com> --- Created attachment 707512 --> http://bugzilla.opensuse.org/attachment.cgi?id=707512&action=edit hwinfo output of cpu,chipset,gfx See attachment for hwinfo output -- 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#c20 --- Comment #20 from Max Staudt <mstaudt@suse.com> --- Okay, we have: CPU: i3-6100 GPU: 8086:1912 Intel HD Graphics 530 Chipset: ? on some Gigabyte mainboard OK, I'll look for the closest match to that hardware when I can, in January. -- 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#c21 Max Staudt <mstaudt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #21 from Max Staudt <mstaudt@suse.com> --- Bat, I still can't reproduce this. I booted a fully updated Leap 42.2 on a Skylake system with the same GPU as yours (8086:1912), logged in via SDDM, ran an IceWM session, and launched uxterm like this: uxterm -fa "DejaVu Sans Mono" I then moved the window to the bottom right of the 1680x1050 screen, ran "man xterm" in that terminal and scrolled down and up. It's all working. I'm closing this as WORKSFORME, as I can't reproduce this. Feel free to reopen if I have made a mistake in my attempt at reproducing the bug. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com