Bug#1078255: xterm: segmentation fault when clicking on the right button
On Fri, Aug 09, 2024 at 02:44:46PM -0400, Thomas Dickey wrote: > On Fri, Aug 09, 2024 at 10:22:11AM +0200, Vincent Lefevre wrote: > > Package: xterm > > Version: 393-1 > > Severity: important > > > > I got a segmentation fault when clicking on the right button. > > > > Core was generated by `/usr/bin/xterm -xrm *printFileOnXError: > > /home/vinc17/private/xterm-saved-172316'. > > Program terminated with signal SIGSEGV, Segmentation fault. > > #0 class_of (cell=0x7fb5479b9da8, ld=0x0) at ../button.c:3606 > > hmm - the functions on the stack trace haven't changed recently > (except of course for the large case-statements where again nothing > on this stack appears to have changed recently, e.g,. in the past year). > > There were some recent fixes/updates in wcwidth.c, which should not make > a difference, unless there's some sign-extension or similar bug. > > Is this something that you might reproduce, to provide test-data? > > > The full backtrace: > > > > Thread 1 (Thread 0x7fb547a6a280 (LWP 5045)): > > #0 class_of (cell=0x7fb5479b9da8, ld=0x0) at ../button.c:3606 ...although none this is recent code, it can still have bugs. The immediate problem with ld == 0 can be addressed by adding a null-pointer check in okPosition. ld could be null if there's some inconsistency in the select begin/end bookkeeping, or if (for example) in selecting from the scrollback and there's some inconsistency in the function that retrieves a pointer to the line. Adding a check in okPosition can help some, but a bug in the scrollback logic will probably surface in some other place. If it's an inconsistency in the select begin/end bookkeeping, that's something that you might recall the sequence of operations which triggered the problem. The stack trace says that the beginning of the selection has no valid line pointer. > > temp = {row = , col = 0} > > result = 0 > > temp = > > result = > > #1 ComputeSelect (xw=xw@entry=0x7fb5479ad010, extend=extend@entry=0, > > normal=1, endc=0x7fb5479b9dd8, startc=0x7fb5479b9dd0) at ../button.c:4160 > > mark = > > screen = 0x7fb5479ad1d0 > > cclass = > > first = {row = -260, col = 0} > > last = > > ignored = 0 '\000' > > ld = {startSel = 0x0, endSel = 0x559b94310190} ^^ > > ltmp = > > #2 0x559b7d2adf6d in ExtendExtend (xw=xw@entry=0x7fb5479ad010, > > cell=cell@entry=0x7fffa94a9be8) at ../button.c:3319 > > screen = 0x7fb5479ad1d0 > > coord = > > #3 0x559b7d2ae065 in EndExtend (xw=xw@entry=0x7fb5479ad010, > > event=event@entry=0x7fffa94aa0a0, params=params@entry=0x559b941ab410, > > num_params=2, use_cursor_loc=use_cursor_loc@entry=0) at ../button.c:3101 > > cell = {row = 19, col = 10} > > screen = 0x7fb5479ad1d0 > > #4 0x559b7d2afcf6 in do_select_end (num_params=, > > use_cursor_loc=0, params=0x559b941ab410, event=0x7fffa94aa0a0, > > xw=0x7fb5479ad010) at ../button.c:1573 > > screen = > > screen = > > #5 do_select_end (use_cursor_loc=0, num_params=0x559b941ab3b0, > > params=0x559b941ab410, event=0x7fffa94aa0a0, xw=0x7fb5479ad010) at > > ../button.c:1553 > > screen = 0x7fb5479ad1d0 > > screen = > > #6 HandleSelectEnd (w=, event=0x7fffa94aa0a0, > > params=0x559b941ab410, num_params=0x559b941ab3b0) at ../button.c:1591 > > xw = 0x7fb5479ad010 ...from here on, the stack isn't showing anything useful. > > #7 0x7fb548071d1f in HandleActions (w=w@entry=0x7fb5479ad010, > > event=0x7fffa94aa0a0, stateTree=0x559b941abf80, accelWidget= > out>, procs=0x559b941efe58, actions=actions@entry=0x559b941ab3a0) at > > ../../src/TMstate.c:653 > > actionHookList = 0x0 > > bindWidget = > > #8 0x7fb5480725e1 in HandleSimpleState (w=w@entry=0x7fb5479ad010, > > tmRecPtr=tmRecPtr@entry=0x7fb5479ad058, > > curEventPtr=curEventPtr@entry=0x7fffa94a9df0) at ../../src/TMstate.c:878 > > bindData = > > procs = > > accelWidget = > > xlations = 0x559b941c83f0 > > contextPtr = 0x7fb5479ad068 > > i = > > actions = > > matchExact = > > match = > > complexMatchState = > > typeIndex = > > modIndex = > > matchTreeIndex = > > #9 0x7fb548073508 in _XtTranslateEvent (w=w@entry=0x7fb5479ad010, > > event=event@entry=0x7fffa
Bug#1078255: xterm: segmentation fault when clicking on the right button
, > xconfigurerequest = {type = 5, serial = 26860, send_event = 0, display = > 0x559b941837d0, parent = 35651612, window = 1662, x = 0, y = 0, width = > 22007178, height = 0, border_width = 131, above = 2237677961566, detail = > 3072, value_mask = 4294967297}, xcirculate = {type = 5, serial = 26860, > send_event = 0, display = 0x559b941837d0, event = 35651612, window = 1662, > place = 0}, xcirculaterequest = {type = 5, serial = 26860, send_event = 0, > display = 0x559b941837d0, parent = 35651612, window = 1662, place = 0}, > xproperty = {type = 5, serial = 26860, send_event = 0, display = > 0x559b941837d0, window = 35651612, atom = 1662, time = 0, state = 22007178}, > xselectionclear = {type = 5, serial = 26860, send_event = 0, display = > 0x559b941837d0, window = 35651612, selection = 1662, time = 0}, > xselectionrequest = {type = 5, serial = 26860, send_event = 0, display = > 0x559b941837d0, owner = 35651612, requestor = 1662, selection = 0, target = > 22007178, property = 1851130904707, time = 2237677961566}, xselection = {type > = 5, serial = 26860, send_event = 0, display = 0x559b941837d0, requestor = > 35651612, selection = 1662, target = 0, property = 22007178, time = > 1851130904707}, xcolormap = {type = 5, serial = 26860, send_event = 0, > display = 0x559b941837d0, window = 35651612, colormap = 1662, new = 0, state > = 0}, xclient = {type = 5, serial = 26860, send_event = 0, display = > 0x559b941837d0, window = 35651612, message_type = 1662, format = 0, data = {b > = "\212\315O\001\000\000\000\000\203\000\000\000\257\001\000\000^\001\000", s > = {-12918, 335, 0, 0, 131, 0, 431, 0, 350, 0}, l = {22007178, 1851130904707, > 2237677961566, 17179872256, 4294967297}}}, xmapping = {type = 5, serial = > 26860, send_event = 0, display = 0x559b941837d0, window = 35651612, request = > 1662, first_keycode = 0, count = 0}, xerror = {type = 5, display = 0x68ec, > resourceid = 0, serial = 94126692906960, error_code = 28 '\034', request_code > = 0 '\000', minor_code = 32 ' '}, xkeymap = {type = 5, serial = 26860, > send_event = 0, display = 0x559b941837d0, window = 35651612, key_vector = > "~\006", '\000' , > "\212\315O\001\000\000\000\000\203\000\000\000\257\001\000"}, xgeneric = > {type = 5, serial = 26860, send_event = 0, display = 0x559b941837d0, > extension = 35651612, evtype = 0}, xcookie = {type = 5, serial = 26860, > send_event = 0, display = 0x559b941837d0, extension = 35651612, evtype = 0, > cookie = 1662, data = 0x0}, pad = {5, 26860, 0, 94126692906960, 35651612, > 1662, 0, 22007178, 1851130904707, 2237677961566, 17179872256, 4294967297, 0 > }} > found = 1 '\001' > #15 0x559b7d2c55df in in_put (xw=) at ../charproc.c:6680 > size = > time_select = > screen = > i = > should_wait = 1 > my_timeout = {tv_sec = 0, tv_usec = 0} > update = 0 > select_mask = {fds_bits = {8, 0 }} > write_mask = {fds_bits = {0 }} > screen = > i = > update = > should_wait = > my_timeout = > size = > time_select = > __d = > __d = > __i__ = > __d = > __i__ = > __i = > __arr = > try_timeout = > tick = > try_timeout = > __d = > __d = > __d = > #16 doinput (xw=0x7fb5479ad010) at ../charproc.c:6697 > screen = 0x7fb5479ad1d0 > screen = > #17 VTparse (xw=xw@entry=0x7fb5479ad010) at ../charproc.c:6169 > keep_running = > #18 0x559b7d2c5c59 in VTRun (xw=0x7fb5479ad010) at ../charproc.c:9348 > screen = 0x7fb5479ad1d0 > #19 0x559b7d2a6a8a in main (argc=, argv=) > at ../main.c:3098 > tblFullscreen = {{name = 0x559b7d3155ba "Always", code = 2}, {name = > 0x559b7d3155c1 "Never", code = 3}} > form_top = 0x559b941ac590 > menu_top = 0x559b941ac590 > menu_high = 0 > screen = > mode = > my_class = 0x559b9417f330 "XTerm" > line_speed = 15 > winToEmbedInto = 0 > > -- System Information: > Debian Release: trixie/sid > APT prefers unstable-debug > APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, > 'stable-security'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), > (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') > Architecture: amd64 (x86_64) > > Kernel: Linux 6.11.0-rc2+ (SMP w/16 CPU threads; PREEMPT) > Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages xterm depends on: > ii libc6 2.39-6 > ii libfontconfig1 2.15.0-1.1 > ii libfreetype62.13.2+dfsg-1+b4 > ii libice6 2:1.0.10-1+b1 > ii libtinfo6 6.5-2 > ii libutempter01.2.1-3+b1 > ii libx11-62:1.8.7-1+b1 > ii libxaw7 2:1.0.14-1+b2 > ii libxext62:1.3.4-1+b1 > ii libxft2 2.3.6-1+b1 > ii libxinerama12:1.1.4-3+b1 > ii libxmu6 2:1.1.3-3+b2 > ii libxpm4 1:3.5.17-1+b1 > ii libxt6t64 1:1.2.1-1.2 > ii xbitmaps1.1.1-2.2 > > Versions of packages xterm recommends: > ii luit [luit] 2.0.20221028-1 > ii x11-utils7.7+6+b1 > > Versions of packages xterm suggests: > pn xfonts-cyrillic > > -- no debconf information > > -- > Vincent Lefèvre - Web: <https://www.vinc17.net/> > 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> > Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) > -- Thomas E. Dickey https://invisible-island.net signature.asc Description: PGP signature
Bug#1077886: xterm: spurious characters in reverse video in scrollback buffer
On Sun, Aug 04, 2024 at 03:34:12AM +0200, Vincent Lefevre wrote: > Package: xterm > Version: 393-1 > Severity: normal > > Some characters in the scrollback buffer can appear in reverse video. > But after scrolling again, they appear as normal, even when there was > no output. so... a) is this something that you can reproduce? b) were the characters in the scrollback supposed to be reversed, and then incorrectly reset? c) is this with bitmap fonts, or TrueType? d) there's no screenshot or other clue to see how to proceed. Comparing with #392, I suppose it's possible that there's an inconsistency in drawing/redrawing for some format-effector code, etc., but without some details on how to reproduce it, not much can be done. > This occurred while I was upgrading packages with apt on a remote > machine (via ssh in xterm), perhaps due to the progress bar, which > uses reverse video. But this was still occurring after the upgrade > terminated (so there was no output at this time). -- Thomas E. Dickey https://invisible-island.net signature.asc Description: PGP signature
Bug#1077282: libxaw: Uploading latest upstream version will cause FTBFS
On Tue, Jul 30, 2024 at 10:55:54AM +0200, Preuße, Hilmar wrote: > On 30.07.2024 09:32, Thomas Dickey wrote: > > On Tue, Jul 30, 2024 at 12:45:09AM +0200, Hilmar Preusse wrote: > > > On 28.07.24 Thomas Dickey (dic...@his.com) wrote: > > > > On Sat, Jul 27, 2024 at 11:31:33PM +0200, Hilmar Preusse wrote: > > Hi Thomas, > > > > > > Source: libxaw > > > > > Version: 2:1.0.14-1 > > > > > > > > 1.0.16 is the latest version. Retitling the bug would be helpful, > > > > because your comment states that the latest version is the regression, > > > > rather than a version from several years ago. > > > > > > > OK, I give it a try, hope that I've done it correctly. 2nd. > > > > This report doesn't show where to see the build-log for texlive-bin > > (nor the proposed workaround). The change in 1.0.16 was made to > > address the changes in compiler warnings. > > > > The issue came to my attention, when gcc-14 became the default compiler and > texlive-bin stopped compiling [1]. Later I found out that the xdvi from TL > 2024 has been made compatible to libxaw 1.0.16 already and the build fails, > b/c Debian still has libxaw 1.0.14. I had to introduce a patch to fix > compatibility, when needs to be kicked out again once 1.0.16 enters the > archive. yes... I haven't tried building texlive (looks like a lot of diskspace), but made the change for 1.0.16 because I was cd'd on a discussion of this: https://bugs.gentoo.org/919069 https://github.com/TeX-Live/texlive-source/pull/64 Changing the type from an explicit const char * to String allows packager/developers to override that without patching (and since packagers don't usually _rely_ upon the configure script, that seemed an acceptable workaround -- with some coordination between package updates). diff --git a/include/X11/Xaw/List.h b/include/X11/Xaw/List.h index 48a6482..59de980 100644 --- a/include/X11/Xaw/List.h +++ b/include/X11/Xaw/List.h @@ -167,7 +167,7 @@ _XFUNCPROTOBEGIN void XawListChange ( Widgetw, - _Xconst char **list, + String*list, int nitems, int longest, #if NeedWidePrototypes ...because Xt's Intrinsic.h does this: /* * As used in its function interface, the String type of libXt can be readonly. * But compiling libXt with this feature may require some internal changes, * e.g., casts and occasionally using a plain "char*". */ #ifdef _CONST_X_STRING typedef const char *String; #else typedef char *String; #endif (and defining or un-defining _CONST_X_STRING seems workable). > Hilmar > > [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075564 > -- > sigfault I did see a few messages with a large number of packages that failed to build (checking the list on Friday, none were for programs that I maintain, but I didn't look for texlive) -- Thomas E. Dickey https://invisible-island.net signature.asc Description: PGP signature
Bug#1077282: libxaw: Uploading latest upstream version will cause FTBFS
On Tue, Jul 30, 2024 at 12:45:09AM +0200, Hilmar Preusse wrote: > Control: retitle -1 libxaw: Uploading upstream version 1.0.16 will cause FTBFS > > On 28.07.24 Thomas Dickey (dic...@his.com) wrote: > > On Sat, Jul 27, 2024 at 11:31:33PM +0200, Hilmar Preusse wrote: > > > > Source: libxaw > > > Version: 2:1.0.14-1 > > > > 1.0.16 is the latest version. Retitling the bug would be helpful, > > because your comment states that the latest version is the regression, > > rather than a version from several years ago. > > > OK, I give it a try, hope that I've done it correctly. 2nd. This report doesn't show where to see the build-log for texlive-bin (nor the proposed workaround). The change in 1.0.16 was made to address the changes in compiler warnings. -- Thomas E. Dickey https://invisible-island.net signature.asc Description: PGP signature
Bug#1075713: Regression: firmware/sysfb.c device path
Hi Am 23.07.24 um 19:38 schrieb Olsak, Marek: [AMD Official Use Only - AMD Internal Distribution Only] Hi, If you have a patch, I'd like to test it. Here's the proposed change: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1612/diffs?commit_id=a745f59bb193c7a87959fddade9b637278e5528e BTW, did you see https://lore.kernel.org/dri-devel/1ff5b407-ff81-40ef-8aa3-9f155491f...@leemhuis.info/ ? This looks similar to your bug report. Best regards Thomas Thanks, Marek *From:* Tj *Sent:* July 15, 2024 05:29 *To:* Thomas Zimmermann *Cc:* Olsak, Marek ; linux-ker...@vger.kernel.org ; 1075...@bugs.debian.org <1075...@bugs.debian.org> *Subject:* Re: Regression: firmware/sysfb.c device path On Monday, 15 July 2024 at 10:22, Thomas Zimmermann wrote: > We should definitely get your patch into the Xorg upstream. Working on that now. -- -- Thomas Zimmermann Graphics Driver Developer SUSE Software Solutions Germany GmbH Frankenstrasse 146, 90461 Nuernberg, Germany GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman HRB 36809 (AG Nuernberg)
Bug#1077282: libxaw: Uploading latest upstream version will cause FTBFS
On Sat, Jul 27, 2024 at 11:31:33PM +0200, Hilmar Preusse wrote: > Source: libxaw > Version: 2:1.0.14-1 1.0.16 is the latest version. Retitling the bug would be helpful, because your comment states that the latest version is the regression, rather than a version from several years ago. -- Thomas E. Dickey https://invisible-island.net signature.asc Description: PGP signature
ANN: xterm-393
Files: https://invisible-island.net/archives/xterm/current/xterm-393.tgz https://invisible-island.net/archives/xterm/current/xterm-393.tgz.asc https://invisible-island.net/archives/xterm/patches/xterm-393.patch.gz https://invisible-island.net/archives/xterm/patches/xterm-393.patch.gz.asc https://invisible-island.net/archives/xterm/xterm-393.tgz https://invisible-island.net/archives/xterm/xterm-393.tgz.asc Patch #393 - 2024/07/11 * add a check for ANSI SC/RC, to ignore CSI parameters. * improve check for missing characters for bitmap-fonts by using the normal font for reference in the case where the current font, e.g., the wide-font was derived from the normal font and lacks per-character metrics (report by Rajeev V. Pillai). * fix regression in error-recovery for SGR parameters from patch #357 (report by James Holderness). * remove some duplicates in xtermcfg.h (report by Matthew Green). * change default for --enable-imake configure option. * fixes for wcwidth: + return 0 for format effectors, like a zero-width printing character rather than -1 like a control character (report by Rajeev V. Pillai). + correct doublewidth to account for reserved codepoints which are listed in the EastAsianWidth file. + add a special case for surrogate pairs, which might be checked in testing the wcwidth function. * amend sixel bounds-check added in patch #371 to not wrap out-of-bounds data. * eliminate maxStringParse limit for SIXEL. * improve logic which ignores APC, PM and SOS controls to also not accumulate their data temporarily in a buffer. * exclude TERM_INGRESS from cleanup of environment variables (patch by Iain Riley). * fix some documentation typos (report by Thomas Wolff). -- Thomas E. Dickey https://invisible-island.net signature.asc Description: PGP signature
ANN: xterm-392
Files: https://invisible-island.net/archives/xterm/current/xterm-392.tgz https://invisible-island.net/archives/xterm/current/xterm-392.tgz.asc https://invisible-island.net/archives/xterm/patches/xterm-392.patch.gz https://invisible-island.net/archives/xterm/patches/xterm-392.patch.gz.asc https://invisible-island.net/archives/xterm/xterm-392.tgz https://invisible-island.net/archives/xterm/xterm-392.tgz.asc Patch #392 - 2024/05/22 * improve input decoding for non-Latin1 character sets by preserving the sense of GL/GR. * add resource preferLatin1 to simplify UPSS configuration (Gentoo #932154). * build-fix for --disable-boxchars; patch #390 reuses that feature's code to draw the part of the DEC Technical character set which has no Unicode equivalent. * modify #include of pty.h to work with musl (report by Khem Raj). * improvedefinitionsusedinclock_gettimelogic in graphics_sixel.c, as well as updating comments (patch by Ben Wong). * amend allowC1Printable changes from patch #391, restoring a special case which caused C1 characters to be ignored (report/testcase by Dmytro Bagrii). -- Thomas E. Dickey https://invisible-island.net signature.asc Description: PGP signature
ANN: xterm-391
Files: https://invisible-island.net/archives/xterm/current/xterm-391.tgz https://invisible-island.net/archives/xterm/current/xterm-391.tgz.asc https://invisible-island.net/archives/xterm/patches/xterm-391.patch.gz https://invisible-island.net/archives/xterm/patches/xterm-391.patch.gz.asc https://invisible-island.net/archives/xterm/xterm-391.tgz https://invisible-island.net/archives/xterm/xterm-391.tgz.asc Patch #391 - 2024/05/12 * improve integration between UTF-8 and allowC1Printable. * alter SIXEL HLS computation to make blue 0 degrees (patch by Ben Wong). * disable SIXEL aspect-ratio, pending a rewrite (patch by Ben Wong). * add resource incrementalGraphics (prompted by patch by Ben Wong). * reorganize graphics_sixel.c as a step toward eliminating graphics buffer-size (integrated patch by Ben Wong). * use __linux__ consistently rather than the older linux. * build-fix for musl (report by Jonáš Vidra, adapted patch by Khem Raj): + modify ifdef for USE_OPENPTY, changing test for __GLIBC__ to __linux__ + change ifdef's for _POSIX_SOURCE to _POSIX_VERSION + modify ifdef for setsid to use a configure-script check for that function's existence and move the old check to imake fallbacks. * minor consistency fixes for manpage. * fix regression in patch #390: non-UTF8 text pasted as a XA_UTF8_STRING was not decoded (report by Petri Kaukasoina). -- Thomas E. Dickey https://invisible-island.net signature.asc Description: PGP signature
Bug#1066263: xfonts-utils: FTBFS: ../fonttosfnt/util.c:89:10: error: implicit declaration of function ‘vasprintf’; did you mean ‘vsprintf’? [-Werror=implicit-function-declaration]
On Wed, Mar 13, 2024 at 10:44:07PM +0500, Andrey Rakhmatullin wrote: > On Wed, Mar 13, 2024 at 12:46:49PM +0100, Lucas Nussbaum wrote: > > > ../fonttosfnt/util.c: In function ‘vsprintf_alloc’: > > > ../fonttosfnt/util.c:89:10: error: implicit declaration of function > > > ‘vasprintf’; did you mean ‘vsprintf’? > > > [-Werror=implicit-function-declaration] > Looks like it's caused by the lack of -D_GNU_SOURCE, not sure who should > set it. There is a very old debian/changelog entry about temporarily > setting it from d/rules and fonttosfnt/write.c sets it but > fonttosfnt/util.c doesn't and there is nothing related in the autotools > stuff. The Debian rules file is rather old, which may be the problem. https://salsa.debian.org/xorg-team/font/xfonts-utils In my (other) test packages, I haven't had to add -D_DEFAULT_SOURCE,** only for non-package builds has that been necessary. ** -D_GNU_SOURCE should only be used for the rare program relying upon non-POSIX interfaces. -- Thomas E. Dickey https://invisible-island.net signature.asc Description: PGP signature
ANN: xterm-390
Files: https://invisible-island.net/archives/xterm/current/xterm-390.tgz https://invisible-island.net/archives/xterm/current/xterm-390.tgz.asc https://invisible-island.net/archives/xterm/patches/xterm-390.patch.gz https://invisible-island.net/archives/xterm/patches/xterm-390.patch.gz.asc https://invisible-island.net/archives/xterm/xterm-390.tgz https://invisible-island.net/archives/xterm/xterm-390.tgz.asc Patch #390 - 2024/02/19 * improve typography of control-sequences page (patches by Branden Robinson). * amend UPSS change from patch #389, fixing a regression in VT100/VT220 character sets. * modify ANSI conformance per ECMA-43 and DEC 070: + set ANSI conformance level to 3 for DEC levels 2 and up. + disable locking shifts in level 1, e.g., VT100. + disable single-shifts from G2/G3 in level 1. + use UPSS for G2/G3 in levels 2 and up. * modify invisible-character attribute to permit DECRQCRA to report a consistent checksum (report/testcase by Thomas Wolff). * align terminfo building blocks in terminfo to correspond to recent refactoring/trimming in ncurses. * set flag in regexec call for onNClicks to handle “^” anchor (patch by Matthew Martin). * add line-drawing data for the characters in DEC Technical which have no Unicode equivalents. * remove a special case in encode_scs which made xterm report Latin-1 when encoding is set to UTF-8, where ASCII is the selected character set. This fixes a regression in vttest for the DECRSPS cursor test. * correct values for Ps of DECAUPSS in ctlseqs.ms (report by James Holderness). * simplify/correct expression for checking Unicode non-characters (report by Thomas Wolff). * correct loop for trimming environment variables (report/patch by Casper Dik). * fixes for manpage formatting (Debian #1041809). * update config.guess, config.sub -- Thomas E. Dickey https://invisible-island.net signature.asc Description: PGP signature
ANN: xterm-389
Files: https://invisible-island.net/archives/xterm/current/xterm-389.tgz https://invisible-island.net/archives/xterm/current/xterm-389.tgz.asc https://invisible-island.net/archives/xterm/patches/xterm-389.patch.gz https://invisible-island.net/archives/xterm/patches/xterm-389.patch.gz.asc https://invisible-island.net/archives/xterm/xterm-389.tgz https://invisible-island.net/archives/xterm/xterm-389.tgz.asc Patch #389 - 2024/01/01 * interchange variables in subparameter parsing, fixing a bug where subparameters after the first parameter could be misidentified (patch by Adam Saponara). * correct popping of icon/window titles in a case where only one was pushed from patch #385 changes. * add XTQMODKEYS response in DECRQSS, as alternative for vim. * correct DECCIR encoded information on character set size, handle a VT525 quirk, and add DECST8C (Windows Terminal #14984). * improve DECRQCRA (prompted by discussion with James Holderness, Windows Terminal #14974). * add part of VT525 color controls: + DECAC, to update default foreground/background, respond to DECRQSS + DECATC, to respond with DECRQSS * prevent Unicode non-characters from being printed (prompted by patch by Grady Martin). * modify send_SGR() to avoid modifying colors 16 to 255 in printed output (patch by Grady Martin). * minor cleanup of miscellaneous error-codes with ERROR_MISC. * remove legacy CSI 53 for locator status, corrected in patch #294. * modify DECRQUPSS and DECAUPSS feature to support VT5xx character sets (report by Thomas Wolff). * improve configure script: + reduce configure-check compiler warnings (prompted by Florian Weimer, Redhat #2251945) + improve usage messages in configure script to make it clearer when an option value is optional. * improve EWMH handling (report/analysis by Edward Rosten) + reset _NET_WM_STATE_HIDDEN flag from _NET_WM_STATE before mapping the window to deiconify. + cache X properties to reduce latency (adapted from patch by Edward Rosten). -- Thomas E. Dickey https://invisible-island.net signature.asc Description: PGP signature
Bug#1006193: Remove luit, now packaged separately
On Wed, Mar 02, 2022 at 03:09:37PM -0500, Thomas Dickey wrote: > On Wed, Mar 02, 2022 at 08:15:15PM +0100, Sven Joachim wrote: > > On 2022-02-21 10:14 +1100, Brendan O'Dea wrote: > > > > > Package: x11-utils > > > Version: 7.7+5 > > > Severity: normal > > > Tags: patch > > > X-Debbugs-Cc: b...@debian.org > > > > > > Merge request to remove luit from x11-utils: > > > > > > https://salsa.debian.org/xorg-team/app/x11-utils/-/merge_requests/1 > > > > > > now packaged separately, this commit removes luit and adds a recommends > > > for > > > the new package. > > > > Thanks, I have merged that now. Are there any packages besides xterm > > that use luit? On codesearch.debian.net I found some 75 hits[1], but > > they seem to be either completely unrelated or only commentaries. While this has been applied, it's not moving along because the related version x11-utils (7.7+6) has not gone into testing yet - more than a year. What has to be done to make that happen? -- Thomas E. Dickey https://invisible-island.net signature.asc Description: PGP signature
ANN: xterm-388
Files: https://invisible-island.net/archives/xterm/current/xterm-388.tgz https://invisible-island.net/archives/xterm/current/xterm-388.tgz.asc https://invisible-island.net/archives/xterm/patches/xterm-388.patch.gz https://invisible-island.net/archives/xterm/patches/xterm-388.patch.gz.asc https://invisible-island.net/archives/xterm/xterm-388.tgz https://invisible-island.net/archives/xterm/xterm-388.tgz.asc Patch #388 - 2023/10/22 * improve disallowPasteControls by adding a category for the special characters known to stty (prompted by discussion with David Leadbeater). * amend support of DECAUPSS, undoing change to initialization of G2/G3 so that pasting of GR characters works properly (report/analysis by Petri Kaukasoina). * update config.guess, config.sub -- Thomas E. Dickey https://invisible-island.net signature.asc Description: PGP signature
ANN: xterm-387
Files: https://invisible-island.net/archives/xterm/current/xterm-387.tgz https://invisible-island.net/archives/xterm/current/xterm-387.tgz.asc https://invisible-island.net/archives/xterm/patches/xterm-387.patch.gz https://invisible-island.net/archives/xterm/patches/xterm-387.patch.gz.asc https://invisible-island.net/archives/xterm/xterm-387.tgz https://invisible-island.net/archives/xterm/xterm-387.tgz.asc Patch #387 - 2023/10/15 * add DECRQUPSS and DECAUPSS. * add DECRQDE (report by Jake Hamby). * correct indexing expression in title-stack, from patch #385 changes (report by Brian Lindholm). -- Thomas E. Dickey https://invisible-island.net signature.asc Description: PGP signature
ANN: xterm-386
Files: https://invisible-island.net/archives/xterm/current/xterm-386.tgz https://invisible-island.net/archives/xterm/current/xterm-386.tgz.asc https://invisible-island.net/archives/xterm/patches/xterm-386.patch.gz https://invisible-island.net/archives/xterm/patches/xterm-386.patch.gz.asc https://invisible-island.net/archives/xterm/xterm-386.tgz https://invisible-island.net/archives/xterm/xterm-386.tgz.asc Patch #386 - 2023/10/09 * improve references in ctlseqs.ms (prompted by discussion with Kirill Chibisov). * make the maximum amount of memory used for buffering DCS and OSC strings configurable with maxStringParse resource (report by Daniel Franke). * improve performance of ReGIS when initializing the largest fontsize (report by Ben Wong). * fix regression in SIXEL colors, in patch #385 (report/patch by Jonny Langley). * fix typo in --with-wtmp (report/patch by Sven Joachim) -- Thomas E. Dickey https://invisible-island.net signature.asc Description: PGP signature
ANN: xterm-385
Files: https://invisible-island.net/archives/xterm/current/xterm-385.tgz https://invisible-island.net/archives/xterm/current/xterm-385.tgz.asc https://invisible-island.net/archives/xterm/patches/xterm-385.patch.gz https://invisible-island.net/archives/xterm/patches/xterm-385.patch.gz.asc https://invisible-island.net/archives/xterm/xterm-385.tgz https://invisible-island.net/archives/xterm/xterm-385.tgz.asc Patch #385 - 2023/10/01 * fixes for ReGIS (report by Ben Wong). + correct conversion from HLS to RGB + improve font-caching performance. * update tables in wcwidth.c based on Unicode 15.1.0 * improve fastScroll resource: + suppress screen-refreshes for carriage-returns + add -jf option to simplify use of this resource. + add a control sequence for enabling/disabling the resource. + enable this feature by default * extend title-stack feature to allow an additional parameter to directly access the stack, like the XTPUSHCOLORS and XTPOPCOLORS feature. * correct size and position of box shown for double-cell character which happens to be missing from the bitmap font (report by Peter Fabinski). * improved configure script: + add pattern for uClibc-ng to CF_XOPEN_SOURCE (report/patch by Waldemar Brodkorb). + add configure options --with-utmp-path and --with-wtmp-path to override configure script's check for utmp/wtmp pathnames which are shown in the manual (Debian #1042767). + CF_XOPEN_SOURCE provides for defining _DEFAULT_SOURCE for MinGW32 and MinGW64. + sed expression used to report gcc version now works with MinGW * ensure that line-attributes are reset after drawing missing character (report by Christian Weisgerber). * update config.guess, config.sub -- Thomas E. Dickey https://invisible-island.net signature.asc Description: PGP signature
Bug#1043299: xterm: build with ReGIS support
On Tue, Aug 08, 2023 at 02:33:10PM -0400, Benjamin Barenblat wrote: > Package: xterm > Version: 384-1 > Severity: wishlist > > Xterm supports ReGIS (DEC vector graphics) emulation, but it’s not > compiled in by default. Would you be willing to add > `--enable-regis-graphics` to the `configure` invocation in debian/rules? INSTALL says: --enable-regis-graphics enable support for ReGIS graphics Compile-in code to support experimental ReGIS graphics -- Thomas E. Dickey https://invisible-island.net signature.asc Description: PGP signature
Bug#1043140: Patches work for me
FYI when rebuilding weston-12 with the patches listed in https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1257/commits weston stop crashing. Best regards, Thomas
Bug#1043140: libweston-12-0: Weston fails to start with "Assertion `csi->width == width' failed"
Package: libweston-12-0 Version: 12.0.1-1 Severity: important Tags: upstream After upgrading my system sddm fails to start a wayland session with the following error in .local/share/sddm/wayland-session.log: weston: ../libweston/output-capture.c:398 weston_output_pull_capture_task: Assertion `csi->width == width' failed. Failed to process Wayland connection: Broken pipe failed to create display: Broken pipe Failed to process Wayland connection: Broken pipe failed to create display: Broken pipe This seems to match upstream bug https://gitlab.freedesktop.org/wayland/weston/-/issues/757 which is also against weston 12.0 and has a fix. Hopefully this can be applied to the Debian package. Best regards, Thomas -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (900, 'unstable'), (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'stable-security'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.4.0-1-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libweston-12-0 depends on: ii libaml0 0.3.0-1 ii libc6 2.37-7 ii libcairo2 1.16.0-7 ii libdrm2 2.4.115-1 ii libegl1 1.6.0-1 ii libfontconfig1 2.14.1-4 ii libfreerdp-server2-22.10.0+dfsg1-1 ii libfreerdp2-2 2.10.0+dfsg1-1 ii libgbm1 23.1.4-1 ii libgles21.6.0-1 ii libglib2.0-02.77.1-2 ii libgstreamer-plugins-base1.0-0 1.22.4-1 ii libgstreamer1.0-0 1.22.4-1 ii libinput10 1.23.0-2 ii libjpeg62-turbo 1:2.1.5-2 ii liblcms2-2 2.14-2 ii libneatvnc0 0.6.0+dfsg-4+b1 ii libpam0g1.5.2-6 ii libpango-1.0-0 1.50.14+ds-1 ii libpangocairo-1.0-0 1.50.14+ds-1 ii libpipewire-0.3-0 0.3.77-1 ii libpixman-1-0 0.42.2-1 ii libpng16-16 1.6.40-1 ii libseat10.8.0-1 ii libudev1254-1 ii libva-drm2 2.19.0-1 ii libva2 2.19.0-1 ii libwayland-client0 1.22.0-2 ii libwayland-cursor0 1.22.0-2 ii libwayland-egl1 1.22.0-2 ii libwayland-server0 1.22.0-2 ii libwebp71.2.4-0.2 ii libwinpr2-2 2.10.0+dfsg1-1 ii libx11-62:1.8.6-1 ii libx11-xcb1 2:1.8.6-1 ii libxcb-composite0 1.15-1 ii libxcb-render0 1.15-1 ii libxcb-shm0 1.15-1 ii libxcb-xfixes0 1.15-1 ii libxcb-xkb1 1.15-1 ii libxcb1 1.15-1 ii libxcursor1 1:1.2.1-1 ii libxkbcommon0 1.5.0-1 libweston-12-0 recommends no packages. libweston-12-0 suggests no packages. -- no debconf information
Bug#1042767: xterm: wrong path to utmp file in manpage
On Fri, Aug 04, 2023 at 05:36:12PM +0200, Sven Joachim wrote: > On 2023-07-31 20:13 -0400, Thomas Dickey wrote: > > > On Mon, Jul 31, 2023 at 05:56:59PM +0200, Sven Joachim wrote: > >> Package: xterm > >> Version: 384-1 > >> Severity: minor > >> > >> The path to the utmp(5) file in the xterm manpage is wrong: > >> > >> , > >> | $ man xterm | grep -A1 /utmp > >> |/etc/utmp > >> | the system log file, which records user logins. > >> ` > >> > >> That should read /var/run/utmp rather than /etc/utmp. The minstall > >> script tries to detect the path to the utmp file and substitute the > >> correct value, but in the build chroot /var/run/utmp has apparently been > >> absent, as no-one has ever logged in there. > > > > yes... /etc/utmp appears to be the convention on AIX and HPUX. > > I could put that last, (along with /var/adm), since those are > > systems where people actually log in -- odd, but perhaps the > > default should be the system where the file is least likely to > > exist :-) > > That would make sense if the autodetection worked on the other systems, > but in a world where distributors build packages in chroots and > containers this is generally not the case. > > I checked the xterm manpage in the packages for Arch Linux, Fedora > Rawhide, Mageia Cauldron and Opensuse Tumbleweed. All but the last of > these do not only mention /etc/utmp but also /etc/wtmp in the FILES > section, and I am pretty sure those two files do not exist. > > Since autodetection for the paths to the utmp and wtmp files does not > work reliably, maybe new configure options could help packagers? that'd be the most reliable way (for Linux - I'm think of "auto" as the default). -- Thomas E. Dickey https://invisible-island.net signature.asc Description: PGP signature
Bug#1042767: xterm: wrong path to utmp file in manpage
On Mon, Jul 31, 2023 at 05:56:59PM +0200, Sven Joachim wrote: > Package: xterm > Version: 384-1 > Severity: minor > > The path to the utmp(5) file in the xterm manpage is wrong: > > , > | $ man xterm | grep -A1 /utmp > |/etc/utmp > | the system log file, which records user logins. > ` > > That should read /var/run/utmp rather than /etc/utmp. The minstall > script tries to detect the path to the utmp file and substitute the > correct value, but in the build chroot /var/run/utmp has apparently been > absent, as no-one has ever logged in there. yes... /etc/utmp appears to be the convention on AIX and HPUX. I could put that last, (along with /var/adm), since those are systems where people actually log in -- odd, but perhaps the default should be the system where the file is least likely to exist :-) -- Thomas E. Dickey https://invisible-island.net signature.asc Description: PGP signature
ANN: xterm-384
Files: https://invisible-island.net/archives/xterm/current/xterm-384.tgz https://invisible-island.net/archives/xterm/current/xterm-384.tgz.asc https://invisible-island.net/archives/xterm/patches/xterm-384.patch.gz https://invisible-island.net/archives/xterm/patches/xterm-384.patch.gz.asc https://invisible-island.net/archives/xterm/xterm-384.tgz https://invisible-island.net/archives/xterm/xterm-384.tgz.asc Patch #384 - 2023/07/10 * exclude ASCII space from showMissingGlyphs, since a few bitmap fonts lack this (report by "SanRemo", Emanuel Haupt). * correct a step in rendering double-width characters with bitmap-fonts (report by Peter Fabinski, Debian #1039986). * fixes for ReGIS-related problems (report by Ben Wong): + mimic an undocumented hardware VT340 feature which handles color initialization with incomplete parameters. + handle whitespace between operator/operands for color values. + reset ReGIS-context when resetting graphics in RIS. -- Thomas E. Dickey https://invisible-island.net signature.asc Description: PGP signature
Bug#1025419: libunwind 1.6.2-2 upgrade makes xorg crash on startup
Hello Axel, > And that fix seems to have been backported in 1.6.2-3 (now in stable, > testing and unstable), see https://bugs.debian.org/1026217 > So this bug report likely can be closed as fixed in libunwind/1.6.2-3 > or (force-) merged with #1026217. (But I'd like to have a second pair > of eyes agreeing that these two issues are indeed the same before > merging or closing.) yes, it was fixed within one week after I opened the bugreport. Cheers, Thomas
Bug#1039986: xterm unicode rendering issue
On Fri, Jun 30, 2023 at 06:54:00PM +0200, 10dmar10 wrote: > Package: xterm > Version: 382-2 > Severity: minor > > Hi, > > I noticed a unicode character rendering issue in xterm since > the latest update in debian testing. > > The problem seems to be limited to double width japanese/chinese characters > and > only when using the default bitmap x11 font. thanks - I had thought the boxes problem was fixed in #381, but someone reported a related problem on Wednesday, and followed up with some debugging details (will be working on that soon - after a more urgent bug-fix). -- Thomas E. Dickey https://invisible-island.net signature.asc Description: PGP signature
ANN: xterm-383
Files: https://invisible-island.net/archives/xterm/current/xterm-383.tgz https://invisible-island.net/archives/xterm/current/xterm-383.tgz.asc https://invisible-island.net/archives/xterm/patches/xterm-383.patch.gz https://invisible-island.net/archives/xterm/patches/xterm-383.patch.gz.asc https://invisible-island.net/archives/xterm/xterm-383.tgz https://invisible-island.net/archives/xterm/xterm-383.tgz.asc Patch #383 - 2023/06/27 * expand description of full- and soft-reset in the manual. * fixes for full- and soft-reset: + clear alternate screen on full reset. + disable menu-entry for active icon; it merely shows whether the feature is enabled. + use appcursorDefault and appkeypadDefault resources for reset of DECCKM and DECKPM. + save initial resource values for sixelScrolling and privateColorRegisters, using those in full reset. + update checkbox for Enable Blinking Cursor (report by Rajeev V. Pillai). * add reply for DECSACE with DECRQSS. * modify status-line feature to exit without erasing for DECSTR. * add private mode 1045 which imitates the original xterm cursor-back reverse wrapping mode 45 (see patch #380). * improve checks for non-Unicode values, e.g., in DECRQCRA. * re-checkout from RCS archive to fix stale identifiers (report by Sven Joachim). -- Thomas E. Dickey https://invisible-island.net signature.asc Description: PGP signature
ANN: xterm-382
Files: https://invisible-island.net/archives/xterm/current/xterm-382.tgz https://invisible-island.net/archives/xterm/current/xterm-382.tgz.asc https://invisible-island.net/archives/xterm/patches/xterm-382.patch.gz https://invisible-island.net/archives/xterm/patches/xterm-382.patch.gz.asc https://invisible-island.net/archives/xterm/xterm-382.tgz https://invisible-island.net/archives/xterm/xterm-382.tgz.asc Patch #382 - 2023/05/30 * amend change to CursorBack in patch #380, allowing the result to be on the hidden right-half of double-cell characters (report by Rajeev V. Pillai). * amend xtermDrawString, fixing regression with --disable-wide-chars configuration from patch #380. * corrected pathname for run-tic.sh, for full install in an out-of-tree build (report by Rajeev V. Pillai). -- Thomas E. Dickey https://invisible-island.net signature.asc Description: PGP signature
ANN: xterm-381
Files: https://invisible-island.net/archives/xterm/current/xterm-381.tgz https://invisible-island.net/archives/xterm/current/xterm-381.tgz.asc https://invisible-island.net/archives/xterm/patches/xterm-381.patch.gz https://invisible-island.net/archives/xterm/patches/xterm-381.patch.gz.asc https://invisible-island.net/archives/xterm/xterm-381.tgz https://invisible-island.net/archives/xterm/xterm-381.tgz.asc Patch #381 - 2023/05/28 * fix a regression in wide bitmap fonts versus check for missing glyphs (report by Rajeev V. Pillai). -- Thomas E. Dickey https://invisible-island.net signature.asc Description: PGP signature
ANN: xterm-380
Files: https://invisible-island.net/archives/xterm/current/xterm-380.tgz https://invisible-island.net/archives/xterm/current/xterm-380.tgz.asc https://invisible-island.net/archives/xterm/patches/xterm-380.patch.gz https://invisible-island.net/archives/xterm/patches/xterm-380.patch.gz.asc https://invisible-island.net/archives/xterm/xterm-380.tgz https://invisible-island.net/archives/xterm/xterm-380.tgz.asc Patch #380 - 2023/05/09 * simplify the change for sixelScrolling from patch #374 (report by Per Bothner). * add xterm+focus and report+da2, update report+version building blocks in terminfo, from post-ncurses 6.4 * drop the -title option from uxterm and koi8rxterm, because that interferes with deriving the default title from the -e option (Debian #1031837). Compensate for this by using the -class option to derive a default title. * improve description of readline 2003 mode in ctlseqs.ms (report by Thomas Wolff). * other improvements to status-line feature (report by Thomas Wolff): + clear status line on DECCOLM + ignore DECSASD if no previous DECSSDT + allow DECSSDT 1 immediately after DECSSDT 2, i.e., without switching back to host mode. * adjust RequestResize to avoid shrinking screen when using DECCOLM while the status-line is active (report/patch by Thomas Wolff). * disallow wrapping before the beginning of the screen, to the end of the screen, for cursor-back sequences (Redhat #2182357). * modify makefile to install the 16x16 xpm files (report by Harald Dunkel). * update test-package to reflect resolution of Debian #906901. * change default of showMissingGlyphs to True. * improve handling of double-sized characters when those happen to be missing from the bitmap font and/or are fullwidth. * pointer/overflow fixes (reported by David Leadbeater): + improve limit-checks for control-sequence numeric parameters in SIXEL graphics. + add null-pointer checks in WriteNow macro to handle a case where SS2 or SS3 might be in effect while processing a combining character. + disallow ReGIS reporting for character-set names containing characters other than alphanumerics or underscore. + implement TrueType fallback font for double-sized characters, including Unicode fullwidth. Also add limitFontHeight to provideforconfiguringthedistinctionbetween slightly-oversized glyphs and double-sized glyphs. * configure script improvements: + check for nfsd_t * fix a typo in the underline cursor thickness derivation (patch by Jan Engelhardt). -- Thomas E. Dickey https://invisible-island.net signature.asc Description: PGP signature
Bug#1022006: Acknowledgement (New version fixes a warning)
- Original Message - | From: "Bjarni Ingi Gislason" | To: 1022...@bugs.debian.org | Cc: "Bjarni Ingi Gislason" | Sent: Sunday, March 5, 2023 4:24:44 PM | Subject: Bug#1022006: Acknowledgement (New version fixes a warning) | The new version did not fix the observed behaviour. For the given bug-report, I don't recall any relevant changes. -- Thomas E. Dickey https://invisible-island.net
ANN: xterm-379
Files: https://invisible-island.net/archives/xterm/current/xterm-379.tgz https://invisible-island.net/archives/xterm/current/xterm-379.tgz.asc https://invisible-island.net/archives/xterm/patches/xterm-379.patch.gz https://invisible-island.net/archives/xterm/patches/xterm-379.patch.gz.asc https://invisible-island.net/archives/xterm/xterm-379.tgz https://invisible-island.net/archives/xterm/xterm-379.tgz.asc Patch #379 - 2023/02/15 * improve text-cursor (patch by Jan Engelhardt): + allow selecting CURSOR_BAR mode from command-line/Xresources. + draw cursor using filled rectangle instead of rectangle outline to permit thicker underlines/bars. + scale up cursor relative to font size. * improve readline modes (Fedora #2166860): + document readline modes + change the feature to configure by default + replace hard-coded SS3 for cursor movement with current mode + replace hard-coded erase/lnext characters with current values * improve status-line (report by Thomas Wolff): + RIS turns off status-line + Right-margin (DECLRMM and DECSLRM) limits the length of text written/updated in the status-line. + Most controls which affect the whole screen are ignored while updating the status-line. * modify configure check for tgetent to allow for some special cases of ncurses configuration (report by Satadru Pramani). * reduce timeout, improve warning message if resize is run on a terminal which is not VT100-compatible. * reduce compiler warnings in configure script. -- Thomas E. Dickey https://invisible-island.net signature.asc Description: PGP signature
ANN: xterm-378
Files: https://invisible-island.net/archives/xterm/current/xterm-378.tgz https://invisible-island.net/archives/xterm/current/xterm-378.tgz.asc https://invisible-island.net/archives/xterm/patches/xterm-378.patch.gz https://invisible-island.net/archives/xterm/patches/xterm-378.patch.gz.asc https://invisible-island.net/archives/xterm/xterm-378.tgz https://invisible-island.net/archives/xterm/xterm-378.tgz.asc Patch #378 - 2023/01/09 * improve descriptions of XTQMODKEYS and XTQALLOWED features in ctlseqs.ms (reports by Bram Moolenaar, Thomas Wolff). * add bracketed+paste and report+version building blocks to terminfo, from ncurses 6.4 * improve check for unsupported formatting characters, e.g., zero-width space, to properly ignore them (report by Thomas Wolff). * improve/document error-checking for some of the controls which return responses: DECRQSS, XTGETXRES, XTSETTCAP, XTGETTCAP (prompted by discussion with David Leadbeater). * improve limit-checks for fallback font cache (report by Dimitrije Erdeljan). * improve check for too-wide glyph in fallback font by allowing xterm to continue searching for a suitable font rather than just failing on the first. Also add limitFontWidth to allow changing the amount by which a glyph must extend outside the font's bounding box to disallow it. -- Thomas E. Dickey https://invisible-island.net signature.asc Description: PGP signature
Bug#1025419: libunwind 1.6.2-2 upgrade makes xorg crash on startup
Hello, the issue is already fixed upstream in libunwind. Cheers, Thomas
Bug#1025419: libunwind 1.6.2-2 upgrade makes xorg crash on startup
Hello, at least the problem on apple silicon systems is due to libunwind assuming 4k page size. Find the patch by Daniel Moody here: https://tg.st/u/0001-libunwind-1.6.2-dynamic-page-size.patch Janne Grunau pointed me to it. Cheers, Thomas
Bug#1025419: libunwind 1.6.2-2 upgrade makes xorg crash on startup
Hello, running Debian testing on apple silicon had the same issue. The culprit seems to be that libunwind was recently updated to 1.6.2-2 which triggers the issue for us. Downgrading to the old version works for us: wget http://ftp.de.debian.org/debian/pool/main/libu/libunwind/libunwind8_1.3.2-2_arm64.deb sudo dpkg -i libunwind8_1.3.2-2_arm64.deb I also tried to build Xorg against the new libunwind, which did __not__ resolve the issue. Output when libunwind is upgraded to 1.6.2-2: (EE) (EE) Backtrace: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x188) [0xe58f96c8] (EE) unw_get_proc_info failed: no unwind info found [-10] (EE) (EE) Segmentation fault at address 0x0 (EE) Fatal server error: (EE) Caught signal 11 (Segmentation fault). Server aborting (EE) (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. (EE) Cheers, Thomas
ANN: xterm-377
Files: https://invisible-island.net/archives/xterm/current/xterm-377.tgz https://invisible-island.net/archives/xterm/current/xterm-377.tgz.asc https://invisible-island.net/archives/xterm/patches/xterm-377.patch.gz https://invisible-island.net/archives/xterm/patches/xterm-377.patch.gz.asc https://invisible-island.net/archives/xterm/xterm-377.tgz https://invisible-island.net/archives/xterm/xterm-377.tgz.asc Patch #377 - 2022/11/25 * add control sequences for reporting the current state of the modified keys options (XTQMODKEYS) and allowed/disallowed operations (XTQALLOWED), (prompted by discussion with Bram Moolenaar). * amend modifyOtherKeys case 2 to distinguish the escape character with modifiers, e.g., shift-escape, from a plain escape character (suggested by Bram Moolenaar). * improve parsing and error-recovery in the case where a list of X11 bitmap fonts is given in the -fn and related options. * change default for xftTrackMemUsage to false, because libXft has does not handle certain fonts. -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
ANN: xterm-376
Files: https://invisible-island.net/archives/xterm/current/xterm-376.tgz https://invisible-island.net/archives/xterm/current/xterm-376.tgz.asc https://invisible-island.net/archives/xterm/patches/xterm-376.patch.gz https://invisible-island.net/archives/xterm/patches/xterm-376.patch.gz.asc https://invisible-island.net/archives/xterm/xterm-376.tgz https://invisible-island.net/archives/xterm/xterm-376.tgz.asc Patch #376 - 2022/11/16 * modify configure script to always check for gcc attributes, * update install-sh. * fix parsing of result -u in vttests/halves.pl. * add a note in ctlseqs.ms about compatibility of TBC. * fix a copy/paste error in manual (patch by Grady Martin). * add null-pointer checks in x_strcasecmp and x_strncasecmp, to help with error-recovery for a missing font (Debian #1022942). -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
Bug#1022942: xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*"
On Wed, Nov 16, 2022 at 04:02:18AM -0500, Thomas Dickey wrote: > On Wed, Nov 16, 2022 at 09:50:36AM +0100, Andreas Tille wrote: > > Control: severity -1 minor ... > > After restarting X xterm is starting properly now. It somehow seems > > that the mkfontdir call changed the game. Unfortunately we do not > > really know what might have caused the issue. As I said I would also > > have loved if xterm would not have crashed. > > agreed (I did try reproducing the crash for the case where the font > was missing, but so far unsuccessful). never mind - I see the problem now (was thinking that it occurred when the font _was_ installed). Will upload #376 in the early morning. -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
Bug#1022942: xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*"
On Wed, Nov 16, 2022 at 09:50:36AM +0100, Andreas Tille wrote: > Control: severity -1 minor > > Hi Thomas, > > at first thanks a lot for your patience. > > Am Tue, Nov 15, 2022 at 08:10:18PM -0500 schrieb Thomas Dickey: > > On Tue, Nov 15, 2022 at 09:15:43AM +0100, Andreas Tille wrote: > > > Hi again, > > > > > > I need to admit that the issue "vanished" on my workhorse laptop which is > > > nice on one hand but having an explanation would be even nicer. ;-) > > > I've now tried the other laptop with the same problem: > > > > > > $ dpkg --get-selections | grep terminus > > > fonts-terminusinstall > > > $ xlsfonts | grep terminus > > > > That might be one of these possibilities: > > > > a) the X configuration (seen with "xset -q") has something amiss with > >the fontpath (see attached example from my Debian/testing). > > There was no attachment but here is mine: sorry - will do that, for the record > $ xset -q > Keyboard Control: > auto repeat: onkey click percent: 0LED mask: > XKB indicators: > 00: Caps Lock: off01: Num Lock:off02: Scroll Lock: off > 03: Compose: off04: Kana:off05: Sleep: off > 06: Suspend: off07: Mute:off08: Misc:off > 09: Mail:off10: Charging:off11: Shift Lock: off > 12: Group 2: off13: Mouse Keys: off > auto repeat delay: 400repeat rate: 20 > auto repeating keys: 00ffdbbf > fedfffefffed > 9fff > fff7 > bell percent: 50bell pitch: 400bell duration: 100 > Pointer Control: > acceleration: 2/1threshold: 4 > Screen Saver: > prefer blanking: yesallow exposures: yes > timeout: 180cycle: 600 > Colors: > default colormap: 0x20BlackPixel: 0x0WhitePixel: 0xff > Font Path: > > /usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/75dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,/usr/share/fonts/X11/75dpi,built-ins > DPMS (Energy Star): > Standby: 0Suspend: 300Off: 600 > DPMS is Enabled > Monitor is On > > > > b) updates to the bitmap font-directories have to be finished using > >mkfontdir (part of xfonts-utils). I've seen occasional comments > >where package updates didn't work as intended. > > > > Either way, "dpkg -L xfonts-terminus" tells me that the relevant files > > are in > > > > /usr/share/fonts/X11/misc > > > > If xset reports that's in the font path, I'd try (based on the manpage) > > > > sudo mkfontdir /usr/share/fonts/X11/misc > > Done. > > > or (by habit, since long ago it ignored the parameter...) > > > > cd /usr/share/fonts/X11/misc > > sudo mkfontdir > > > > and restart X. > > After restarting X xterm is starting properly now. It somehow seems > that the mkfontdir call changed the game. Unfortunately we do not > really know what might have caused the issue. As I said I would also > have loved if xterm would not have crashed. agreed (I did try reproducing the crash for the case where the font was missing, but so far unsuccessful). > In any case I consider the severity of the bug as lower now and have > set it to minor. I'll leave it to your decision whether you consider > it closed or some helpful resource to find a way to avoid the issue. > > Kind regards and thanks again for your help >Andreas. > > -- > http://fam-tille.de > -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net Keyboard Control: auto repeat: onkey click percent: 0LED mask: 0002 XKB indicators: 00: Caps Lock: off01: Num Lock:on 02: Scroll Lock: off 03: Compose: off04: Kana:off05: Sleep: off 06: Suspend: off07: Mute:off08: Misc:off 09: Mail:off10: Charging:off11: Shift Lock: off 12: Group 2: off13: Mouse Keys: off auto repeat delay: 500repeat rate: 20 auto repeating keys: 00ffdbbf fadfffefffed 9fff fff7 bell percent: 50bell pitch: 400bell duration: 100 Pointer Control: acceleration: 2/1threshold: 4 Screen Saver: prefer blanking: yesallow exposures: yes timeout: 600cycle: 600 Colors: default colormap: 0x20BlackPixel: 0x0WhitePixel: 0xff Font Path: /usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/75dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,/usr/share/fonts/X11/75dpi,built-ins DPMS (Energy Star): Standby: 600Suspend: 0Off: 900 DPMS is Enabled Monitor is On signature.asc Description: PGP signature
Bug#1022942: xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*"
On Tue, Nov 15, 2022 at 09:15:43AM +0100, Andreas Tille wrote: > Hi again, > > I need to admit that the issue "vanished" on my workhorse laptop which is > nice on one hand but having an explanation would be even nicer. ;-) > I've now tried the other laptop with the same problem: > > $ dpkg --get-selections | grep terminus > fonts-terminusinstall > $ xlsfonts | grep terminus That might be one of these possibilities: a) the X configuration (seen with "xset -q") has something amiss with the fontpath (see attached example from my Debian/testing). b) updates to the bitmap font-directories have to be finished using mkfontdir (part of xfonts-utils). I've seen occasional comments where package updates didn't work as intended. Either way, "dpkg -L xfonts-terminus" tells me that the relevant files are in /usr/share/fonts/X11/misc If xset reports that's in the font path, I'd try (based on the manpage) sudo mkfontdir /usr/share/fonts/X11/misc or (by habit, since long ago it ignored the parameter...) cd /usr/share/fonts/X11/misc sudo mkfontdir and restart X. -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
Bug#1022942: xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*"
On Mon, Nov 14, 2022 at 06:21:50PM +0100, Andreas Tille wrote: > Am Mon, Nov 14, 2022 at 04:27:30AM -0500 schrieb Thomas Dickey: > > > Since xterm is crashing before this does not report anything > > > interesting. > > > > hmm - it's not showing much. > > > > What does xfd do with that pattern? (using single quotes): > > > > xfd -fn '-*-terminus-*-*-*-32-*-*-*-*-*-*-*' > > > > If you don't have that installed, it's part of x11-utils: /usr/bin/xfd > > > > (reinstalling the font might be helpful) > > OK > > ~$ sudo apt install fonts-terminus > Paketlisten werden gelesen… Fertig > Abhängigkeitsbaum wird aufgebaut… Fertig > Statusinformationen werden eingelesen… Fertig > Die folgenden NEUEN Pakete werden installiert: > fonts-terminus > 0 aktualisiert, 1 neu installiert, 0 zu entfernen und 2 nicht aktualisiert. > Es müssen 81,0 kB an Archiven heruntergeladen werden. > Nach dieser Operation werden 464 kB Plattenplatz zusätzlich benutzt. > Holen:1 http://deb.debian.org/debian testing/main amd64 fonts-terminus amd64 > 1.2.0+ds-7 [81,0 kB] > Es wurden 81,0 kB in 0 s geholt (596 kB/s). > Vormals nicht ausgewähltes Paket fonts-terminus wird gewählt. > (Lese Datenbank ... 417804 Dateien und Verzeichnisse sind derzeit > installiert.) > Vorbereitung zum Entpacken von .../fonts-terminus_1.2.0+ds-7_amd64.deb ... > Entpacken von fonts-terminus (1.2.0+ds-7) ... > fonts-terminus (1.2.0+ds-7) wird eingerichtet ... > Trigger für fontconfig (2.13.1-4.5) werden verarbeitet ... > ~$ xfd -fn '-*-terminus-*-*-*-32-*-*-*-*-*-*-*' > Warning: Cannot convert string "-*-terminus-*-*-*-32-*-*-*-*-*-*-*" to type > FontStruct > xfd: no font to display That's (sort of) promising - it tells me that it's not a bug in _xterm_. xterm and xfd use the same font-related libraries. It could still be a configuration problem -- I seem to recall seeing cases where mkfontdir wasn't run on font updates. xlsfonts should show the terminus fonts in its (usually long) output. For instance, on my Debian/oldstable, I get 494 lines from xlsfonts | grep terminus (including an alias "terminus-32"). xlsfonts doesn't use any of those font-related libraries, talks directly to the X server. The Xlib calls that xterm uses for bitmap fonts (e.g., Terminus) should use the same information. If you were using a TrueType font, xterm and xfd would use the Xft and fontconfig libraries (the "font-related" libraries that I mentioned). xterm and xfd if using "-fa" (rather than "-fn") will ask fontconfig for the font, and it does know enough to do that, e.g., xfd -fa terminus-32 xterm -fa terminus-32 -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
Bug#1022942: xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*"
On Mon, Nov 14, 2022 at 09:02:22AM +0100, Andreas Tille wrote: > Am Sun, Nov 13, 2022 at 08:33:09PM -0500 schrieb Thomas Dickey: > > > LANGUAGE= > > > LC_CTYPE="de_DE.UTF-8" > > > LC_NUMERIC="de_DE.UTF-8" > > > LC_TIME="de_DE.UTF-8" > > > LC_COLLATE="de_DE.UTF-8" > > > LC_MONETARY="de_DE.UTF-8" > > > LC_MESSAGES="de_DE.UTF-8" > > > LC_PAPER="de_DE.UTF-8" > > > LC_NAME="de_DE.UTF-8" > > > LC_ADDRESS="de_DE.UTF-8" > > > LC_TELEPHONE="de_DE.UTF-8" > > > LC_MEASUREMENT="de_DE.UTF-8" > > > LC_IDENTIFICATION="de_DE.UTF-8" > > > LC_ALL= > > > > I tried that - no change > > I admit I do not think the locale setting is responsible for the issue. > > > > I've made the Geometry that size to fit exactly a quarter of my screen > > > fitting 4 xterms at one time. Xfce4 places these intelligently in a > > > 2x2 matrix. > > > > Something like this will work, but fixing the problem with the menus: > > > > XTerm*VT100.geometry: 111x36 > > > > It's in the FAQ: > > > > https://invisible-island.net/xterm/xterm.faq.html#tiny_menus > > Thanks for the hint but I think this was not my main problem. ;-) > > > > I'm using Debian packages exclusively - I have no time to spent > > > extra fancy things. BTW. I'm observing the very same bug on my > > > second laptop I'm using for traveling (but my desktop with the > > > same setup works without any problem) > > > > > > Could you send me the full command line > > >"xrdb -load ??" > > > > I pasted the text from earlier mail as "bad.ad" (attached), > > and loaded it with > > > > xrdb -load bad.ad > > I tried this but it did not changed the problem. > > > > I could check here. What strace call should I send to track > > > down the issue. Please note that while I'm an experienced > > > > I'd just > > > > strace -o trace.log -s 1024 xterm > > > > to capture a long trace (~200kb), > > and look to see if there's something interesting where xterm dies. > > I've attached my gziped trace.log. > > > I also ran xterm using -report-fonts, which shows the fonts opened. > > Since xterm is crashing before this does not report anything > interesting. hmm - it's not showing much. What does xfd do with that pattern? (using single quotes): xfd -fn '-*-terminus-*-*-*-32-*-*-*-*-*-*-*' If you don't have that installed, it's part of x11-utils: /usr/bin/xfd (reinstalling the font might be helpful) -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
Bug#1024058: Please add qwerty-fr layout
Package: xkb-data Version: 2.35.1-1 Severity: wishlist Hi, I've switched to the layout described here: https://github.com/qwerty-fr/qwerty-fr and I am very happy of it. Rather than packaging it as an add-on, I thought it'd be nicer to have xkb-data to support this layout an embbed the file at: https://github.com/qwerty-fr/qwerty-fr/blob/master/linux/us_qwerty-fr Now, let's discuss how to close this bug. 1/ If you think this should be packaged separately, please let me know, and I will do the work (super easy...). 2/ If you have no time to patch this yourself, I'd appreciate some directions on how to patch xkb-data, so I can write a MR on Salsa. I can see that symbols are in the upstream "symbols" dir, but then should I just add a debian/patches file to add the us_qwerty-fr file? Or is there a better way? Cheers, Thomas Goirand (zigo)
Bug#1022942: xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*"
On Sat, Nov 12, 2022 at 03:17:01PM +0100, Andreas Tille wrote: > Am Sun, Nov 06, 2022 at 07:55:33PM -0500 schrieb Thomas Dickey: > > On Tue, Nov 01, 2022 at 09:23:55AM +0100, Andreas Tille wrote: > > > Am Sun, Oct 30, 2022 at 04:53:24PM -0400 schrieb Thomas Dickey: > > > > > > $ grep font /etc/X11/Xresources/xterm | grep -v ^! > > > > > > *VT100.utf8Fonts.font: fixed > > > > what locale settings are you using? > > > > (that might be relevant - or the choice of desktop/window-manager) > > $ locale > LANG=de_DE.UTF-8 > LANGUAGE= > LC_CTYPE="de_DE.UTF-8" > LC_NUMERIC="de_DE.UTF-8" > LC_TIME="de_DE.UTF-8" > LC_COLLATE="de_DE.UTF-8" > LC_MONETARY="de_DE.UTF-8" > LC_MESSAGES="de_DE.UTF-8" > LC_PAPER="de_DE.UTF-8" > LC_NAME="de_DE.UTF-8" > LC_ADDRESS="de_DE.UTF-8" > LC_TELEPHONE="de_DE.UTF-8" > LC_MEASUREMENT="de_DE.UTF-8" > LC_IDENTIFICATION="de_DE.UTF-8" > LC_ALL= I tried that - no change > Desktop environment is xfce4. > > > > Sorry its "comment". > > > > > > > > (the grep seems to indicate that the latter is meant) > > > > > > > > > > > crash with segmentation fault when not finding some specified font. > > > > I suppose the problem is something along the lines of the X server > > returning some error in using the fonts. If it were TrueType fonts, > > I'd use strace to verify that they're opened -- but for bitmap > > fonts, that's done on the server side. > > I admit I'm fine with any nicely readable font. I once considered the > terminus fonts to fit this requirement and never found any reason > to change this. > > > > The crash happens for > > > > > > $ xrdb -query > > > *VT100.utf8Fonts.font: fixed > > > XTermVT100.faceSize:22 > > > XTerm*geometry: 111x36 > > > > hmm - I'm still not seeing _this_ problem. > > (by the way, the geometry resource is over-broad, making the font-menu > > less than useful). > > I've made the Geometry that size to fit exactly a quarter of my screen > fitting 4 xterms at one time. Xfce4 places these intelligently in a > 2x2 matrix. Something like this will work, but fixing the problem with the menus: XTerm*VT100.geometry: 111x36 It's in the FAQ: https://invisible-island.net/xterm/xterm.faq.html#tiny_menus > > I used xcfe4 for testing, on a virtual machine. > > > > My most recent snapshot (from 2022/11/01) didn't work - some problem > > with X and the window manaager), so I upgraded from 2022/10/29, > > to get a workable machine. > > > > Given that (I also have the terminus font installed), > > I used "xrdb -load" with these resources, and ran xterm > > from the Debian package. It looks okay to me - no crash. > > I'm using Debian packages exclusively - I have no time to spent > extra fancy things. BTW. I'm observing the very same bug on my > second laptop I'm using for traveling (but my desktop with the > same setup works without any problem) > > Could you send me the full command line >"xrdb -load ??" I pasted the text from earlier mail as "bad.ad" (attached), and loaded it with xrdb -load bad.ad > I could check here. What strace call should I send to track > down the issue. Please note that while I'm an experienced I'd just strace -o trace.log -s 1024 xterm to capture a long trace (~200kb), and look to see if there's something interesting where xterm dies. I also ran xterm using -report-fonts, which shows the fonts opened. > Debian user and long year developer I would not consider myself > an X expert. > > Kind regards > >Andreas. > > -- > http://fam-tille.de -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net Loaded VTFonts(font6) fNorm: -*-terminus-*-*-*-32-*-*-*-*-*-*-* all chars: no default char: 63 direction: 0 ascent:26 descent: 6 first char:0 last char: 255 maximum-chars: 256 missing-chars: 37 present-chars: 219 min_byte1: 0 max_byte1: 0 properties:22 min_bounds: lbearing: 0 rbearing: 0 width:16 ascent: -1
Bug#1022942: xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*"
On Tue, Nov 01, 2022 at 09:23:55AM +0100, Andreas Tille wrote: > Am Sun, Oct 30, 2022 at 04:53:24PM -0400 schrieb Thomas Dickey: > > > > $ grep font /etc/X11/Xresources/xterm | grep -v ^! > > > > *VT100.utf8Fonts.font: fixed what locale settings are you using? (that might be relevant - or the choice of desktop/window-manager) > > > > XTerm.VT100.font1: -*-terminus-*-*-*-16-*-*-*-*-*-*-* > > > > XTerm.VT100.font2: -*-terminus-*-*-*-18-*-*-*-*-*-*-* > > > > > > > > XTerm.VT100.font3: -*-terminus-*-*-*-20-*-*-*-*-*-*-* > > > > > > > > XTerm.VT100.font4: -*-terminus-*-*-*-24-*-*-*-*-*-*-* > > > > XTerm.VT100.font5: -*-terminus-*-*-*-28-*-*-*-*-*-*-* > > > > > > > > XTerm.VT100.font6: -*-terminus-*-*-*-32-*-*-*-*-*-*-* > > > > for the record, xfonts-terminus includes all of these sizes. > > > > > > here. If I uncomment these settings xterm starts. However, I think > > > > xterm should not > > > > > > Is that "uncomment", or "comment"? > > Sorry its "comment". > > > > (the grep seems to indicate that the latter is meant) > > > > > > > crash with segmentation fault when not finding some specified font. I suppose the problem is something along the lines of the X server returning some error in using the fonts. If it were TrueType fonts, I'd use strace to verify that they're opened -- but for bitmap fonts, that's done on the server side. > > > > > > agreed - > > > > I've not been able to reproduce the problem, which I suspect is in > > the error-recovery section of xterm's xtermLoadFont function. > > > > Perhaps seeing the whole set of resources would help > > (the output of "xrdb -query", too). > > I have: > > $ xrdb -query > *VT100.utf8Fonts.font: fixed > XTermVT100.faceSize:22 > XTerm*geometry: 111x36 > xterm*vt100.initialFont:6 > YTerm*geometry: 90x50 > xterm*visualBell: true > Rxvt.keysym.Delete: \b > Rxvt.termName: xterm > XTerm*decTerminalID:200 > XTerm*color0: black > XTerm*color1: red > XTerm*color2: green > XTerm*color3: yellow > XTerm*color4: blue > XTerm*color5: magenta > XTerm*color6: cyan > XTerm*color7: white > XTerm*color8: black > XTerm*color9: red > XTerm*color10: green > XTerm*color11: yellow > XTerm*color12: blue > XTerm*color13: magenta > XTerm*color14: cyan > XTerm*color15: white > XTerm*termName: xterm > XTerm*title:XTerm > XTerm*colorMode:on > XTerm*background: blue > XTerm*foreground: white > XTerm*loginShell: true > XTerm*dynamicColors:on > > > The crash happens for > > $ xrdb -query > *VT100.utf8Fonts.font: fixed > XTermVT100.faceSize:22 > XTerm*geometry: 111x36 hmm - I'm still not seeing _this_ problem. (by the way, the geometry resource is over-broad, making the font-menu less than useful). I used xcfe4 for testing, on a virtual machine. My most recent snapshot (from 2022/11/01) didn't work - some problem with X and the window manaager), so I upgraded from 2022/10/29, to get a workable machine. Given that (I also have the terminus font installed), I used "xrdb -load" with these resources, and ran xterm from the Debian package. It looks okay to me - no crash. > XTerm.VT100.font1: -*-terminus-*-*-*-16-*-*-*-*-*-*-* > XTerm.VT100.font2: -*-terminus-*-*-*-18-*-*-*-*-*-*-* > XTerm.VT100.font3: -*-terminus-*-*-*-20-*-*-*-*-*-*-* > XTerm.VT100.font4: -*-terminus-*-*-*-24-*-*-*-*-*-*-* > XTerm.VT100.font5: -*-terminus-*-*-*-28-*-*-*-*-*-*-* > XTerm.VT100.font6: -*-terminus-*-*-*-32-*-*-*-*-*-*-* > xterm*vt100.initialFont:6 > YTerm*geometry: 90x50 > xterm*visualBell: true > Rxvt.keysym.Delete: \b > Rxvt.termName: xterm > XTerm*decTerminalID:200 > XTerm*color0: black > XTerm*color1: red > XTerm*color2: green > XTerm*color3: yellow > XTerm*color4: blue > XTerm*color5: magenta > XTerm*color6: cyan > XTerm*color7: white > XTerm*color8: black > XTerm*color9: red > XTerm*color10: green > XTerm*color11: yellow > XTerm*color12: blue > XTerm*color13: magenta > XTerm*color14: cyan > XTerm*color15: white > XTerm*termName: xterm > XTerm*title:XTerm > XTerm*colorMode:on > XTerm*background: blue > XTerm*foreground: white > XTerm*loginShell: true > XTerm*dynamicColors:on > > > I confir
Bug#1022942: xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*"
On Fri, Oct 28, 2022 at 03:49:52AM -0400, Thomas Dickey wrote: > On Fri, Oct 28, 2022 at 08:51:50AM +0200, Andreas Tille wrote: > > Package: xterm > > Version: 375-1 > > Severity: important > > > > Hi, > > > > after upgrading from xterm 374-1 to 375-1 I get: > > > > $ xterm > > xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*" > > Segmentation fault > > > > I guess this local setting is relevant: > > > > $ grep font /etc/X11/Xresources/xterm | grep -v ^! > > *VT100.utf8Fonts.font: fixed > > XTerm.VT100.font1: -*-terminus-*-*-*-16-*-*-*-*-*-*-* > > XTerm.VT100.font2: -*-terminus-*-*-*-18-*-*-*-*-*-*-* > > > > XTerm.VT100.font3: -*-terminus-*-*-*-20-*-*-*-*-*-*-* > > > > XTerm.VT100.font4: -*-terminus-*-*-*-24-*-*-*-*-*-*-* > > XTerm.VT100.font5: -*-terminus-*-*-*-28-*-*-*-*-*-*-* > > > > XTerm.VT100.font6: -*-terminus-*-*-*-32-*-*-*-*-*-*-* for the record, xfonts-terminus includes all of these sizes. > > here. If I uncomment these settings xterm starts. However, I think xterm > > should not > > Is that "uncomment", or "comment"? > > (the grep seems to indicate that the latter is meant) > > > crash with segmentation fault when not finding some specified font. > > agreed - I've not been able to reproduce the problem, which I suspect is in the error-recovery section of xterm's xtermLoadFont function. Perhaps seeing the whole set of resources would help (the output of "xrdb -query", too). -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
Bug#1022942: xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*"
On Fri, Oct 28, 2022 at 08:51:50AM +0200, Andreas Tille wrote: > Package: xterm > Version: 375-1 > Severity: important > > Hi, > > after upgrading from xterm 374-1 to 375-1 I get: > > $ xterm > xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*" > Segmentation fault > > I guess this local setting is relevant: > > $ grep font /etc/X11/Xresources/xterm | grep -v ^! > *VT100.utf8Fonts.font: fixed > XTerm.VT100.font1: -*-terminus-*-*-*-16-*-*-*-*-*-*-* > XTerm.VT100.font2: -*-terminus-*-*-*-18-*-*-*-*-*-*-* > > XTerm.VT100.font3: -*-terminus-*-*-*-20-*-*-*-*-*-*-* > > XTerm.VT100.font4: -*-terminus-*-*-*-24-*-*-*-*-*-*-* > XTerm.VT100.font5: -*-terminus-*-*-*-28-*-*-*-*-*-*-* > > XTerm.VT100.font6: -*-terminus-*-*-*-32-*-*-*-*-*-*-* > > here. If I uncomment these settings xterm starts. However, I think xterm > should not Is that "uncomment", or "comment"? (the grep seems to indicate that the latter is meant) > crash with segmentation fault when not finding some specified font. agreed - > Kind regards > Andreas. > > > -- System Information: > Debian Release: bookworm/sid > APT prefers unstable > APT policy: (500, 'unstable'), (500, 'testing'), (50, 'buildd-unstable'), > (1, 'experimental') > Architecture: amd64 (x86_64) > > Kernel: Linux 6.0.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) > Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not > set > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages xterm depends on: > ii libc6 2.35-4 > ii libfontconfig1 2.13.1-4.5 > ii libfreetype62.12.1+dfsg-3 > ii libice6 2:1.0.10-1 > ii libtinfo6 6.3+20220423-2 > ii libutempter01.2.1-2 > ii libx11-62:1.8.1-2 > ii libxaw7 2:1.0.14-1 > ii libxext62:1.3.4-1+b1 > ii libxft2 2.3.6-1 > ii libxinerama12:1.1.4-3 > ii libxmu6 2:1.1.3-3 > ii libxpm4 1:3.5.12-1 > ii libxt6 1:1.2.1-1 > ii xbitmaps1.1.1-2.2 > > Versions of packages xterm recommends: > ii x11-utils 7.7+5 > > Versions of packages xterm suggests: > pn xfonts-cyrillic > > -- no debconf information > -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
ANN: xterm-375
Files: https://invisible-island.net/archives/xterm/current/xterm-375.tgz https://invisible-island.net/archives/xterm/current/xterm-375.tgz.asc https://invisible-island.net/archives/xterm/patches/xterm-375.patch.gz https://invisible-island.net/archives/xterm/patches/xterm-375.patch.gz.asc https://invisible-island.net/archives/xterm/xterm-375.tgz https://invisible-island.net/archives/xterm/xterm-375.tgz.asc Patch #375 - 2022/10/23 * improve error-recovery when setting a bitmap font for the VT100 window, e.g., in case OSC 50 failed, restoring the most recent valid font so that a subsequent OSC 50 reports this correctly (report by David Leadbeater). * exclude MC_XDG_OPEN from environment variables trimmed on startup (report by Gabor Hauzer). * check for null pointer in isSelect() (report by Column Paget). -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
ANN: xterm-374
Files: https://invisible-island.net/archives/xterm/current/xterm-374.tgz https://invisible-island.net/archives/xterm/current/xterm-374.tgz.asc https://invisible-island.net/archives/xterm/patches/xterm-374.patch.gz https://invisible-island.net/archives/xterm/patches/xterm-374.patch.gz.asc https://invisible-island.net/archives/xterm/xterm-374.tgz https://invisible-island.net/archives/xterm/xterm-374.tgz.asc Patch #374 - 2022/10/10 * eliminate use of grep aliases from vttests scripts. * amend discussion of DECSDM versus Sixel Scrolling in ctlseqs.ms (reports by Hayaki Saito, Ben Wong). * change default for sixelScrolling resource to better match VT330/VT340 DECSDM setting (patch by Ben Wong). * fix some gcc and coverity warnings. * improve memory usage for OSC 52 (report by David Leadbeater). * fixregressioninxterm-373change adding resources xftTrackMemUsage to xftMaxGlyphMemory, which did not first cache the server's resource-settings (report/testcase by Gabor Hauzer, as well as Debian #1021243). * fix regression in xterm-373 change for status-line vs alternate screen (report by Rajeev V. Pillai). * configure script improvements: + modify CF_XOPEN_SOURCE to handle more special cases of Linux (reports by Adam Sampson, Sven Joachim). + modify checks for egrep/fgrep aliases to work around warning messages from GNU grep 3.8 -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
Bug#1021243: xterm: different font size after upgrading from 372-1 to 373-1
- Original Message - | From: "Thomas Dickey" | To: 1021...@bugs.debian.org | Cc: 1021243-submit...@bugs.debian.org | Sent: Tuesday, October 4, 2022 8:22:23 PM | Subject: Bug#1021243: xterm: different font size after upgrading from 372-1 to 373-1 | On Tue, Oct 04, 2022 at 11:36:50AM +0200, Emanuele Rocca wrote: |> Package: xterm |> Version: 373-1 |> Severity: important |> |> Hi, |> |> the upgrade from xterm 372-1 to 373-1 changes font size on my system. |> |> See what the fonts used to look like with 372-1 vs 373-1 in the attached |> screenshots. | | thanks (I had a similar report yesterday, and am investigating) https://github.com/ThomasDickey/xterm-snapshots/commit/932678ac4823db3f94fc831b4c0db89307b04a5c -- Thomas E. Dickey http://invisible-island.net ftp://ftp.invisible-island.net
Bug#1021243: xterm: different font size after upgrading from 372-1 to 373-1
On Tue, Oct 04, 2022 at 11:36:50AM +0200, Emanuele Rocca wrote: > Package: xterm > Version: 373-1 > Severity: important > > Hi, > > the upgrade from xterm 372-1 to 373-1 changes font size on my system. > > See what the fonts used to look like with 372-1 vs 373-1 in the attached > screenshots. thanks (I had a similar report yesterday, and am investigating) -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
ANN: xterm-373
Files: https://invisible-island.net/archives/xterm/current/xterm-373.tgz https://invisible-island.net/archives/xterm/current/xterm-373.tgz.asc https://invisible-island.net/archives/xterm/patches/xterm-373.patch.gz https://invisible-island.net/archives/xterm/patches/xterm-373.patch.gz.asc https://invisible-island.net/archives/xterm/xterm-373.tgz https://invisible-island.net/archives/xterm/xterm-373.tgz.asc Patch #373 - 2022/09/25 * improve rendering of TrueType fonts: + add resource xftTrackMemUsage to enable/disable a new feature of Xft which improves performance. + add resources xftMaxGlyphMemory and xftMaxUnrefFonts to customize memory-usage of Xft and fontconfig. + provide for display of colored fonts in libXft 2.3.5 + allow for an extra TrueType font to be specified using the -fa option, as an override to the fontconfig scheme of fallback fonts (request by Nickolas Raymond Kaczynski). + improve caching of TrueType missing-glyph tests. + allow no more than 255 fonts to be scanned for a fontset. + eliminate a table-lookup in findXftGlyph * improvements status-line feature: + save/restore wraparound flag when updating the status-line (report by Rajeev V. Pillai). + avoid clearing the status-line when switching between normal and alternate screens (report by Valtteri Vuorikoski). + remove adjustment from update_winsize leftover from initial work (report by Valtteri Vuorikoski). * modify wcwidth tables to separate Unicode Cf category as formatting control-characters, to better match the guideline for unsupported characters (report by Tim Chase). * add configure option --disable-exec-selection. * use mkstemp where mkdtemp is unavailable, when initializing colored cursor. * adapt fixes from OpenBSD xenocara: + improve ifdef's for a few optional features. + correct #ifdef to #if in a few uses of OPT_PRINT_ON_EXIT. * set StartupWMClass in “.desktop” files, e.g., to help cinnamon-session notice that xterm sets WM_CLASS and use its icon (patch by Richard de Boer). * disable pixel computation when rgb width is greater than 8, to work with depth 30 (patch by Denis Kaganovich). * improve color-computation for SGR 2 faint/dim (patch by Boian Bonev). Add resource faintIsRelative to specify if the modified computation should be used (prompted by discussion with Matthieu Herrb). * correct comparison-length for environment variable cleanup (patch by Brendan O' Dea). * correct dsl capability for dec+sl block in terminfo (report by Rajeev V. Pillai). * improve output formatting by vttests/utf8.pl * repair test/demo scripts still using "vxt-" prefix, some cleanup with shellcheck. * enable page-number for DECXCPR response in VT330. * amend change for combining characters in patch #371 to limit it to the currently-defined codes (report by Thomas Wolff). * add directory-template parameter to mktemp in shell-scripts to improve portability to older systems (patch by Ryan Schmidt). * mention webpage XTerm – bracketed-paste in ctlseqs.ms * update manual-page descriptions for allowPasteControls and disallowedPasteControls (patch #363). * further extended list of environment variables to purge on startup (suggested by Thomas Wolff). * update config.guess, config.sub -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
Bug#1014625: xterm: screen corruption of scrollback buffer
On Sat, Jul 09, 2022 at 02:39:41PM +1000, Tim Connors wrote: > Package: xterm > Version: 372-1 > Severity: normal > > I'm getting screen corruption (scattered blocks of blackness) over > text in the xterm display when scrolling back. The blocks move with > the contents of the scrollback when scrolling. When that text is > eventually scrolled off the screen, scrolling back may induce a > different corruption pattern. Forcing a redisplay of the contents of > the terminal by going to a different virtual desktop and back will get > rid of the corruption. also, menu "Main Options", "Redraw Window" can help. > This has happened ever since I changed my hardware -- mostly updating > my video card to a radeon RX570 -- necessitating new versions of some > drivers and kernel. While I would happily accept that the video card > might have some dodgy memory (note to self: find a GPU memory stress > tester), this corruption has not affected any other program other than > xterm's scrollback buffer, so I wonder if it's a bug instead. > > Screengrabs of the symptom: > > https://rather.puzzling.org/~tconnors/tmp/screengrab-xterm-scrollback-corruption.png > https://rather.puzzling.org/~tconnors/tmp/screengrab-xterm-scrollback-corruption2.png > > radeon amdgpu drivers and firmware are the latest version allowed by > otherwise being on debian stable - ie, It looks like the problem is in the drivers (not xterm). That could be defective implementation of XCopyArea, for instance. https://bugs.freedesktop.org/show_bug.cgi?id=110214 -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
Bug#1010628: libsm6: Missing symbolic link libSM.so (to libSM.so.6.0.1)
On Thu, May 05, 2022 at 01:43:00PM -0400, Kevin Cole wrote: > Package: libsm6 The symbolic link is provided by the development package, and doesn't belong in the runtime. -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
Bug#1010630: libice6: Missing symbolic link libICE.so (to libICE.so.6.3.0)
On Thu, May 05, 2022 at 01:45:53PM -0400, Kevin Cole wrote: > Package: libice6 The symbolic link is provided in the development package (libice-dev) /. /usr /usr/include /usr/include/X11 /usr/include/X11/ICE /usr/include/X11/ICE/ICE.h /usr/include/X11/ICE/ICEconn.h /usr/include/X11/ICE/ICElib.h /usr/include/X11/ICE/ICEmsg.h /usr/include/X11/ICE/ICEproto.h /usr/include/X11/ICE/ICEutil.h /usr/lib /usr/lib/x86_64-linux-gnu /usr/lib/x86_64-linux-gnu/libICE.a /usr/lib/x86_64-linux-gnu/pkgconfig /usr/lib/x86_64-linux-gnu/pkgconfig/ice.pc /usr/share /usr/share/doc /usr/share/doc/libice-dev /usr/share/doc/libice-dev/changelog.Debian.gz /usr/share/doc/libice-dev/changelog.gz /usr/share/doc/libice-dev/copyright /usr/lib/x86_64-linux-gnu/libICE.so -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
Bug#1007709: xterm: Sometimes xterm last lines are not shown, amd64->arm64
On Tue, Mar 15, 2022 at 01:05:17PM +0100, Jose L. Fernandez Jambrina wrote: > Package: xterm > Version: 366-1 > Severity: normal > X-Debbugs-Cc: j.fdez.jambr...@gr.ssr.upm.es > > Dear Maintainer, > > Sometimes xterm last lines are not shown, pressing enter forces them to > appear. This happen with xterm running on an amd4 machine but displayed in a > raspberry-4 machine, both running bullseye /stable That sounds like a problem with the X server rather than xterm. -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
ANN: xterm-372
Files: ftp://ftp.invisible-island.net/xterm/current/xterm-372.tgz ftp://ftp.invisible-island.net/xterm/current/xterm-372.tgz.asc ftp://ftp.invisible-island.net/xterm/patches/xterm-372.patch.gz ftp://ftp.invisible-island.net/xterm/patches/xterm-372.patch.gz.asc ftp://ftp.invisible-island.net/xterm/xterm-372.tgz ftp://ftp.invisible-island.net/xterm/xterm-372.tgz.asc Patch #372 - 2022/03/09 * amend allocation/freeing of scrollback lines, eliminating an adjustment for status-line added in patch #371 (report/testcase by Rajeev V. Pillai). -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
Bug#1006193: Remove luit, now packaged separately
On Wed, Mar 02, 2022 at 08:15:15PM +0100, Sven Joachim wrote: > On 2022-02-21 10:14 +1100, Brendan O'Dea wrote: > > > Package: x11-utils > > Version: 7.7+5 > > Severity: normal > > Tags: patch > > X-Debbugs-Cc: b...@debian.org > > > > Merge request to remove luit from x11-utils: > > > > https://salsa.debian.org/xorg-team/app/x11-utils/-/merge_requests/1 > > > > now packaged separately, this commit removes luit and adds a recommends for > > the new package. > > Thanks, I have merged that now. Are there any packages besides xterm > that use luit? On codesearch.debian.net I found some 75 hits[1], but > they seem to be either completely unrelated or only commentaries. I'm not aware of any other direct dependencies such as xterm. The occasional mention that I see for luit is for running it manually from the command-line, e.g., to make a shell for using emacs with some legacy character set. > Cheers, >Sven > > > 1. https://codesearch.debian.net/search?q=%5Cbluit%5Cb&literal=0 > -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
ANN: xterm-371
Files: ftp://ftp.invisible-island.net/xterm/current/xterm-371.tgz ftp://ftp.invisible-island.net/xterm/current/xterm-371.tgz.asc ftp://ftp.invisible-island.net/xterm/patches/xterm-371.patch.gz ftp://ftp.invisible-island.net/xterm/patches/xterm-371.patch.gz.asc ftp://ftp.invisible-island.net/xterm/xterm-371.tgz ftp://ftp.invisible-island.net/xterm/xterm-371.tgz.asc Patch #371 - 2022/02/24 * drop double-buffer default from test-packages, since that interferes with status-line. * add faceSize7 to table in charproc.c, overlooked in patch #360 (patch by Vladimir A. Pavlov). * use XDrawString rather than XDrawString16 for text when the latter is not needed. * improve performance for initializing/reusing graphic objects in the SIXEL feature. * improve error-checking for resize. * fix errata in manual page (Debian #988221). * extended list of environment variables to purge on startup, i.e., in case a user starts xterm from another terminal emulator. * add comment in cursor.c to explain why autowrap (DECAWM) does not apply to data saved/restored with save/restore cursor-operations (report by Thomas Wolff). * add special case in generating the combining-character table in wcwidth.c, for Hangul Jamo Extended-B (report by Luis Javier Merino). * simplify/improve portability of trap commands in shell-scripts. * update configure options --disable-rectangles, --disable-tcap-fkeys and --disable-tcap-query to account for changed default settings. * rather than ignore empty parameter for setting title, use that to reset it to “xterm” for scripting. * check for out-of-bounds condition while drawing sixels, and quit that operation (report by Nick Black). * add fallback definition for PROJECTROOT so that a suitable default location for luit will be compiled-in on build-servers. * implement DEC status-line controls DECSASD/DECSSDT: + decode controls, set state + implement DECRQSS responses + implement indicator-style status-line + add configure option --enable-status-line + add resource indicatorFormat + implementhost-writable status-line, able to handle video-attributes and simple left/right cursor movement. This disallows all of the DEC/xterm private modes such as switching to/from the alternate screen. + move the status-line if the window is resized. + Note: the associated screen-resizing does not work for the special case of TrueType fonts with double-buffering (see note in patch #349). * modify configure-script fixup for -Werror options to exclude fixup for -Werror=format, e.g., -Werror=format-security. * amend change from patch #370; DEC 070's pseudo-code for DECCOLM incorrectly suggests that it enables DECLRMM as a side-effect. * fix some memory leaks seen using esctest and asan2 (patch by Luis Javier Merino). -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
Bug#576670: #576670 xterm: *.sh and *pl files are not installed (color scripts)
A separate package probably wouldn't be that useful (since most of the xterm features are poorly supported by other terminal emulators). There are currently 60 scripts. In my test-packages, I add those in /usr/share/doc/*/examples: dh_installexamples tektests vttests which consumes about as much diskspace as the changelog (xterm.log.html). -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
Bug#699746: #699746 x11-utils: xprop assumes that WM_ICON_NAME and WM_NAME are encoded in ISO-8859-1
I was recently reminded of this one, and can see that it's no longer relevant: + The bug-report made incorrect assumptions about what xprop ought to be doing. So it's not relevant to xprop. + Cloos' comment about xterm was interesting but not useful for xterm, because the encoding as STRING rather than COMPOUND_STRING is done by the X Toolkit library. Reading the Shell.c file in libXt, arguably an application _could_ set the resources titleEncoding and iconNameEncoding while setting the title and icon-name, but even setting those to COMPOUND_STRING (which does _not_ hold UTF-8) wouldn'd make the server transmute those into EWMH names (which _does_ hold UTF-8). + Regarding xterm, my changes in patch #349 make it do by default what Vincent assumed. Patch #349 - 2019/09/22 * improve title-string feature: + if any of allowC1Printable, utf8Title or titleModes hint that an application might send a title-string encoded in UTF-8, check if that is the case, and if it is recodable into ISO-8859-1, use that for the ICCCM-style title. + check if the title given by a control sequence happens to be already encoded in UTF-8, to avoid double-encoding (FreeBSD #240393). + Make sameName resource work for the EWMH titles. + Modify menu-state of utf8Title to be consistent with the utf8 source, i.e., setting the EWMH properties automatically when UTF-8 is active. just for grins, I'll close this (expecting the usual response from Vincent). -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
Bug#1005272: libxt6: out-of-date copyright file
Package: libxt6 Version: 1:1.2.0-20190617 Severity: important The copyright file in package libxt (version 1:1.2.1-1) is out-of-date. The sources from which libxt were built have a current copyright file at the top of the source-tree "COPYRIGHT" which can be used to replace the out-of-date copyright file in the package. Debian policy addresses this issue: https://www.debian.org/doc/debian-policy/ch-source.html#copyright-debian-copyright Every package must be accompanied by a verbatim copy of its distribution license(s) in the file /usr/share/doc/PACKAGE/copyright. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.15.0-3-amd64 (SMP w/2 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libxt6 depends on: ii libc6 2.33-5 ii libice62:1.0.10-1 ii libsm6 2:1.2.3-1 ii libx11-6 2:1.7.2-2+b1 ii multiarch-support 2.28-10 libxt6 recommends no packages. libxt6 suggests no packages. -- no debconf information
Re: libxt_1.2.1-1_source.changes ACCEPTED into unstable
On Wed, Feb 09, 2022 at 03:49:04PM +, Debian FTP Masters wrote: > > > Accepted: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Format: 1.8 > Date: Wed, 09 Feb 2022 17:28:15 +0200 > Source: libxt > Built-For-Profiles: noudeb > Architecture: source > Version: 1:1.2.1-1 > Distribution: unstable > Urgency: medium > Maintainer: Debian X Strike Force > Changed-By: Timo Aaltonen > Changes: > libxt (1:1.2.1-1) unstable; urgency=medium > . >* New upstream release. >* control: Migrate to x11proto-dev. The package copyright file has not been updated. https://salsa.debian.org/xorg-team/lib/libxt/-/blob/debian-unstable/COPYING >* Update README.source for salsa. >* control: Bump debhelper-compat to 13, policy to 4.6.0. >* Update signing-key.asc. > Checksums-Sha1: > 422a452c06dcc2ffb00ed6dfe11967f24622a838 2312 libxt_1.2.1-1.dsc > d0020bf4e2e48336aed5a6871d2a6b6e1a6bf02e 1024473 libxt_1.2.1.orig.tar.gz > b7bedcc667f50c9382af1e723a6c62bc76be282e 358 libxt_1.2.1.orig.tar.gz.asc > 9a520501d9e6332d7bd671b91b519c308349fa1c 45419 libxt_1.2.1-1.diff.gz > ab1245d70276e5abaf861740149d6fbc65a47feb 7124 libxt_1.2.1-1_source.buildinfo > Checksums-Sha256: > 910bf9521a14849eb0c5c2d6f35222065cabc55fa712223773f7d1305211dbe3 2312 > libxt_1.2.1-1.dsc > 6da1bfa9dd0ed87430a5ce95b129485086394df308998ebe34d98e378e3dfb33 1024473 > libxt_1.2.1.orig.tar.gz > da406cc94c25ca6773bb37c2055e2eb5665491f7ca6dfc9ea04f0f30ea3fd098 358 > libxt_1.2.1.orig.tar.gz.asc > 2aaf37ac880e8a9b04ecf999f3911e3ac840649a9ee0d0c5d160dd6536ff9416 45419 > libxt_1.2.1-1.diff.gz > 7e068520c98634f7bb56a5db55982f14788149d8fd7915ecf19396c4cf0a35f8 7124 > libxt_1.2.1-1_source.buildinfo > Files: > 07e5c50bf275b4ea90d5999772e9d4dd 2312 x11 optional libxt_1.2.1-1.dsc > c98b235835a44fb7ced85a11914af900 1024473 x11 optional libxt_1.2.1.orig.tar.gz > f73bcf17c9fcacff676a1d90549f64e4 358 x11 optional libxt_1.2.1.orig.tar.gz.asc > 68e29b394889aa74008a101b24a40b7d 45419 x11 optional libxt_1.2.1-1.diff.gz > e4775bfb81947f895e5544746a8edb6c 7124 x11 optional > libxt_1.2.1-1_source.buildinfo > > -BEGIN PGP SIGNATURE- > > iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAmID3kYACgkQy3AxZaiJ > hNy7yA//RpZmFrw6ulW0rBsK0UKruC8iAELKsJx7OIUePV9l/Ewe7jC8ci4KrAtR > oohAb8pwV9ZuPypY3XQdQhjjLf67zY5YS5ikqm7YYvFav5aP5psfx7dPU3Ok24Tl > s1++vbSGW9qr/BRpqONm59WULOziMrzCOmtXbgc3PFoT4LGEwHg0E8cwSFjuf6ja > 5XaZRa9AQfRoGUibf/d49LmsdO8hez38lVMScJkbrAiSzRx+fCTU8eZoBhjOt2ko > Hp+nI/ewxJpJ18SyNl3N1p+OaPsAL5LlnoGNOqybkarJ01rLc8dWL968sYe6dBef > YXeuWXujZnswBekffm56heq65ftX4TliBeSGgFwYKxbaaC2L0lkRH4beao7fwJfz > hHJIObw9kYZJ/Escbc95PH4iE0ZLLne16i5cDAREwbCWuJwHO3WloGAlskWJ8MN+ > XQF/HlLBxb/l89fdZujCIke2VHKPznfCGtVG3K7sdWEW1UL9RKgKZoHYK72F1cV1 > A4FgKpsxv1s9RiG5VZB1XE+N/IACz23juV2P3cUdLbG8/ciGyDQFpoQnsDgsgCJ9 > 7BlvQcbl7kJ977DE/NU3JPJwtl39QitOpszxLgDl2fjkkHee68IYABT02kf4HPk4 > 7CS7WTv9XeaKmyyhMXlQQJubszl8oZf/2bZX1uNVa3Ksu57n1NM= > =asNn > -END PGP SIGNATURE- > > > Thank you for your contribution to Debian. > -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
Bug#1004689: xterm: CVE-2022-24130
On Mon, Jan 31, 2022 at 08:37:03PM +0100, Salvatore Bonaccorso wrote: > Source: xterm > Version: 370-1 > Severity: important > Tags: security upstream > X-Debbugs-Cc: car...@debian.org, Debian Security Team > > > Hi, > > The following vulnerability was published for xterm. > > CVE-2022-24130[0]: > | xterm through Patch 370, when Sixel support is enabled, allows > | attackers to trigger a buffer overflow in set_sixel in > | graphics_sixel.c via crafted text. > > > If you fix the vulnerability please also make sure to include the > CVE (Common Vulnerabilities & Exposures) id in your changelog entry. changelog as usual reflects the actual report, not a succession of secondhand information. I applied a fix for the issue yesterday, which will be in #371. For backports, do as suggested here: http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/x11/xterm/patches/patch-graphics__sixel.c derived from https://github.com/ThomasDickey/xterm-snapshots/blob/master/graphics_sixel.c -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
Bug#904572: move x11-utils to Suggests
On Mon, Jan 24, 2022 at 10:06:46AM +0100, Harald Dunkel wrote: > Maybe the Recommends could be replaced by a Suggests: x11-utils. > By now I didn't even know that there is a tool "luit". It's used (when available and if the locale encoding is not UTF-8) by xterm for quite a while. But it doesn't use the X display (unlike the other programs in x11-utils). Moving it to a separate package would only affect xterm and a (probably) small number of direct command-line users. Changing the "recommends" to a "suggests" would have an impact on xterm, since some users would not see luit automatically. As I understand it, the best route would be to get luit available separately and then change the xterm package to recommend luit rather than x11-utils. By the way - the existing version of luit uses libfontenc, which _is_ used by several applications. Take a look at apt-rdepends --reverse libfontenc1 However, in my upgrade, I dispensed with that dependency, so the resulting luit depends only on glibc and libz. That makes it easily portable - unlike most of x11-utils :-) So... decoupling luit (and libfontenc1) from x11-utils will improve the dependencies of both xterm and x11-utils. -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
Bug#904572: move x11-utils to Suggests
On Sun, Jan 23, 2022 at 05:55:37PM +, Ivan Shmakov wrote: > >>>>> Harald Dunkel writes: > > > Package: xterm > > Version: 333-1 > > > xterm recommends x11-utils. Assuming the default configuration, this > > brings in a huge list of packages unrelated to xterm's main purpose: > > Running a shell or another cli program. Sample: xterm actually should recommend luit, which is not yet a separate package see #1003130 and #1003770: https://mentors.debian.net/package/luit/ once that's completed, the xterm package should be changed to recommend luit (about 130kb for that package, no dependencies except that it might suggest the xfonts-encodings package). > There’re several ways to resolve the issue, one of which is > indeed to move luit into a package of its own, though I can’t > say I’m particularly fond of practices that lead to the > expansion of the Packages files, as well as /var/lib/dpkg/. that's unclear (there's only ~66 thousand packages so far) -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
Bug#1003130: ITP: luit in 2013.
On Tue, Jan 04, 2022 at 11:46:03AM -0500, Thomas Dickey wrote: > Package: x11-utils > Version: 7.7+5 > Severity: normal > > Dear Maintainer, > >* x11-utils copy of luit was superseded by luit 2.0 in 2013. >* mentioned this several times to developers in X Strike Force >* developers did not reply to those comments >* developers could have suggested a way to address the issue > > As a solution to that, I propose to create a new package "luit2", Actually, the package should be named "luit", but the executable "luit2". -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
Bug#1003130: x11-utils copy of luit was superseded by luit 2.0 in 2013.
Package: x11-utils Version: 7.7+5 Severity: normal Dear Maintainer, * x11-utils copy of luit was superseded by luit 2.0 in 2013. * mentioned this several times to developers in X Strike Force * developers did not reply to those comments * developers could have suggested a way to address the issue As a solution to that, I propose to create a new package "luit2", and modify x11-utils to install its luit as "luit1", allowing the alternatives feature to let users select an up-to-date luit. The change to x11-utils is in bug #1003021. This bug covers the new packaging for luit. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.15.0-2-amd64 (SMP w/2 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages x11-utils depends on: ii libc6 2.33-1 ii libfontconfig1 2.13.1-4.2 ii libfontenc1 1:1.1.4-1 ii libgl1 1.3.4-2+b1 ii libx11-62:1.7.2-2+b1 ii libx11-xcb1 2:1.7.2-2+b1 ii libxaw7 2:1.0.13.1-20191125 ii libxcb-shape0 1.14-3 ii libxcb1 1.14-3 ii libxcomposite1 1:0.4.5-1 ii libxext62:1.3.4-1 ii libxft2 2.3.2-2 ii libxi6 2:1.8-1 ii libxinerama12:1.1.4-2 ii libxkbfile1 1:1.1.0-1 ii libxmu6 2:1.1.2-2+b3 ii libxmuu12:1.1.2-2+b3 ii libxrandr2 2:1.5.2-1 ii libxrender1 1:0.9.10-1 hi libxt6 1:1.2.0-20190617 ii libxtst62:1.2.3-1 ii libxv1 2:1.0.11-1 ii libxxf86dga12:1.1.4-1+b3 ii libxxf86vm1 1:1.1.4-1+b2 x11-utils recommends no packages. Versions of packages x11-utils suggests: ii mesa-utils 8.4.0-1+b2 -- no debconf information
Bug#1003021: x11-utils: luit - looking for a sponsor of this bug
On Mon, Jan 03, 2022 at 08:23:43PM -0500, Thomas Dickey wrote: > On Sun, Jan 02, 2022 at 03:56:58PM -0500, Thomas Dickey wrote: > > Package: x11-utils > > Version: 7.7+5 > > Severity: normal > ... > > a) modify x11-utils, making its copy of luit configurable via > > the alternatives feature (renaming it to "luit1", accessed as > > "luit") > > I've implemented that here: > > https://salsa.debian.org/dickey/x11-utils/-/commit/bcf8729a50c5034875526b05380b4abbab539836 > > > > > b) to provide an up-to-date package for luit as "luit2", also > > of course configurable via the alternatives feature. > > as well as this, here: > > https://salsa.debian.org/dickey/luit/-/commit/087e3504e384915244a06e39bfbcaf7524ad4faa > > > c) After some time, the copy in x11-utils can be replaced by a > > "recommends". > > > > Incidentally, doing this would fix #816289 > > > > The point of this bug report is to get feedback on "a" (modify x11-utils). looking at https://lists.debian.org/cgi-bin/search?P=luit&DEFAULTOP=or&B=Gdebian-x&SORT=0&HITSPERPAGE=10&xP=luit&xFILTERS=Gdebian-x%7E-%7E%7E4294967295 this issue has been mentioned several times without any response from XStrikeForce. I'm the upstream developer for luit and xterm, but am not a Debian Developer. I'm looking for a sponsor for the changes (and having that in place, would allow updating the xterm package to close #904572). -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
Bug#1003021: x11-utils: luit - please upgrade
On Sun, Jan 02, 2022 at 03:56:58PM -0500, Thomas Dickey wrote: > Package: x11-utils > Version: 7.7+5 > Severity: normal ... > a) modify x11-utils, making its copy of luit configurable via > the alternatives feature (renaming it to "luit1", accessed as "luit") I've implemented that here: https://salsa.debian.org/dickey/x11-utils/-/commit/bcf8729a50c5034875526b05380b4abbab539836 > > b) to provide an up-to-date package for luit as "luit2", also > of course configurable via the alternatives feature. as well as this, here: https://salsa.debian.org/dickey/luit/-/commit/087e3504e384915244a06e39bfbcaf7524ad4faa > c) After some time, the copy in x11-utils can be replaced by a > "recommends". > > Incidentally, doing this would fix #816289 > > The point of this bug report is to get feedback on "a" (modify x11-utils). :-) -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
Bug#1003021: x11-utils: luit - please upgrade
Package: x11-utils Version: 7.7+5 Severity: normal Dear Maintainer, * The version of luit in x11-utils is very old, and its nominal upstream is defunct. https://lists.x.org/archives/xorg-devel/2018-August/057386.html See this for a summary of the relationship of "xorg luit" to luit: https://invisible-island.net/luit/#metrics * Prior discussion with the package maintainers had no effect. * To remedy the situation, I propose to a) modify x11-utils, making its copy of luit configurable via the alternatives feature (renaming it to "luit1", accessed as "luit") b) to provide an up-to-date package for luit as "luit2", also of course configurable via the alternatives feature. c) After some time, the copy in x11-utils can be replaced by a "recommends". Incidentally, doing this would fix #816289 The point of this bug report is to get feedback on "a" (modify x11-utils). -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.15.0-2-amd64 (SMP w/2 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages x11-utils depends on: ii libc6 2.33-1 ii libfontconfig1 2.13.1-4.2 ii libfontenc1 1:1.1.4-1 ii libgl1 1.3.4-2+b1 ii libx11-62:1.7.2-2+b1 ii libx11-xcb1 2:1.7.2-2+b1 ii libxaw7 2:1.0.13.1-20191125 ii libxcb-shape0 1.14-3 ii libxcb1 1.14-3 ii libxcomposite1 1:0.4.5-1 ii libxext62:1.3.4-1 ii libxft2 2.3.2-2 ii libxi6 2:1.8-1 ii libxinerama12:1.1.4-2 ii libxkbfile1 1:1.1.0-1 ii libxmu6 2:1.1.2-2+b3 ii libxmuu12:1.1.2-2+b3 ii libxrandr2 2:1.5.2-1 ii libxrender1 1:0.9.10-1 hi libxt6 1:1.2.0-20190617 ii libxtst62:1.2.3-1 ii libxv1 2:1.0.11-1 ii libxxf86dga12:1.1.4-1+b3 ii libxxf86vm1 1:1.1.4-1+b2 x11-utils recommends no packages. Versions of packages x11-utils suggests: ii mesa-utils 8.4.0-1+b2 -- no debconf information
ANN: xterm-370
Files: ftp://ftp.invisible-island.net/xterm/current/xterm-370.tgz ftp://ftp.invisible-island.net/xterm/current/xterm-370.tgz.asc ftp://ftp.invisible-island.net/xterm/patches/xterm-370.patch.gz ftp://ftp.invisible-island.net/xterm/patches/xterm-370.patch.gz.asc ftp://ftp.invisible-island.net/xterm/xterm-370.tgz ftp://ftp.invisible-island.net/xterm/xterm-370.tgz.asc Patch #370 - 2021/11/13 * add -a, -c and -d options to query-status.pl to improve test for DECRQSS. * expanded discussion of maximum graphics geometry in ctlseqs.ms (suggested by Bon Wong). * corrected parameter symbol for DECCARA and DECRARA in ctlseqs.ms to indicate that multiple parameters may be used (report by Thomas Wolff). * add several test/demo scripts. * improve DECCOLM, DECLRMM and DECALN referring to pseudo-code in DEC 070. * amend a change in patch #348 which caused left/right margin mode to be reset when resizing the terminal window (report by Valentine Barshak). * fix a misnamed macro-parameter (patch by Rajeev V. Pillai). * fix spacing of wideFont when its width is not exactly twice as wide as the normal font (report by Rajeev V. Pillai). * suppress loading of italic font in a few places when colorITmode is enabled (report/analysis by Rajeev V. Pillai). * modify XTSMGRAPHICS to return failure status if the terminal is not configured to support the corresponding ReGIS or SIXEL feature (report by Nick Black, notcurses #2252, notcurses #2257). * modify DECERA and DECFRA to erase corresponding area in SIXEL graphics (patch by Nick Black, notcurses #1740, vt340test #16). Also modify DECSERA. * equate visuals for TrueColor and DirectColor (patch by Denis Kaganovich). * correct computation for pixel value of rgb when using depth 16 (report by Denis Kaganovich). * correct wrapping of VT100-style double-sized characters when configured for Unicode wide-characters (report by Luis Javier Merino). * updated default value for sixelScrolling resource to match expected behavior versus DECSDM change in patch #369 (report by Grant Taylor). -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
ANN: xterm-369
Files: ftp://ftp.invisible-island.net/xterm/current/xterm-369.tgz ftp://ftp.invisible-island.net/xterm/current/xterm-369.tgz.asc ftp://ftp.invisible-island.net/xterm/patches/xterm-369.patch.gz ftp://ftp.invisible-island.net/xterm/patches/xterm-369.patch.gz.asc ftp://ftp.invisible-island.net/xterm/xterm-369.tgz ftp://ftp.invisible-island.net/xterm/xterm-369.tgz.asc Patch #369 - 2021/09/21 * modify run-tic.sh to work around bug in development version of ncurses which was packaged in FreeBSD ports. * remove ifdef's for OPT_COLOR_RES and OPT_COLOR_RES2. * improve performance over slow connections (report by Harald Dunkel). * update cursor if restoring mode for DECTCEM. * modify CharWidth macro to ensure that the shortcut for Latin-1 is only applied when UTF-8 is not enabled, to fix a bug in handling soft-hyphen from patch #334 changes (patch by Martijn van Duren). * improve terminfo: + fill-in function-keys in terminfo which are not Sun/HP keyboards using xterm+nopcfkeys building-block. + add kbeg to xterm+keypad to accommodate termcap applications + add smglp and smgrp to vt420+lrmm, to provide useful data for the "tabs" +m option * support shift-tab in Sun, HP and SCO keyboards. * document some legacy features in ctlseqs.ms (prompted by discussion with Jimmy Aguilar Mena "Ergus"). * add “trim” option to cdXtraScroll and tiXtraScroll. * remove support for non-fifo save-lines configuration. * extend cdXtraScroll to check if the cursor is at the upper-left of the scrolling region when the erasure is for the remainder of the screen versus the whole screen (prompted by discussion with Jörg Breitbart). * add workaround for broken pcre2 package in Debian 10. * change screen-refresh call used for DECCARA and DECRARA to ensure that trailing blanks which are part of the rectangle are repainted (report/analysis by Dennis Filder). * when resetting the terminal, ensure that the cursor shape also is reset, e.g., if DECSCUSR has been used to modify the cursor shape for an xterm which was started with the underlined cursor option (report/analysis by Luis Javier Merino). * prevent DECSCUSR from blinking the cursor if the cursorBlink resource is “never” (report by Vladimir D Seleznev). * invert the sense of DECSDM, to correspond with VT382 manuals (lsix #41). * update tables in wcwidth.c based on Unicode 14.0.0 -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
Bug#989664: xterm: .Xresources VT100 override for copy/paste ignored
On Thu, Jun 10, 2021 at 04:37:04PM -0400, Casey M. Bessette wrote: > Here's the output of xrdb: > > $ xrdb -q ...colors shouldn't matter... > Xcursor.size: 0 > Xcursor.theme: > Xcursor.theme_core: 1 > Xft.hintstyle: hintnone > Xft.rgba: none > xterm*VT100.Translations: #override Ctrl Shift V: ^ missing "\n" > insert-selection(CLIPBOARD) \n Ctrl Shift C: copy-selection(CLIPBOARD) I have this: *customization: -color XScreenSaver.newLoginCommand: gdm-control --switch-user Xcursor.size: 0 Xcursor.theme: Xcursor.theme_core: 1 Xft.hintstyle: hintnone Xft.rgba: none xterm*VT100.Translations: #override \n Ctrl Shift C: copy-selection(CLIPBOARD) \n Ctrl Shift V: insert-selection(CLIPBOARD) If the "\n" is missing, then the code for control/shift/V is all part of a comment. -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
Bug#989664: xterm: .Xresources VT100 override for copy/paste ignored
On Wed, Jun 09, 2021 at 01:53:09PM -0400, Casey M. Bessette wrote: > Package: xterm > Version: 366-1 > Severity: normal > X-Debbugs-Cc: casey.besse...@gmail.com > > Dear Maintainer, > > My .Xresources file has this in it: > > !enable copy/paste: > !http://unix.stackexchange.com/questions/225062/how-can-i-copy-text-from-xterm-awesome-debian-virtualbox > xterm*VT100.Translations: #override \ > Ctrl Shift V:insert-selection(CLIPBOARD) \n\ > Ctrl Shift C:copy-selection(CLIPBOARD) > > I run xrdb -merge ~/.Xresources after editing the file. This has enabled me > to use ctrl-shift-c to copy and ctrl-shift-v to paste in and out of xterm. > > In bullseye, this no longer works. Now if I hit ctrl-shift-c, it acts > no different than if I hit ctrl-c. This worked for me on jessie and stretch. > I haven't used buster. It's working for me :-( (testing with bullseye, and xterm #366 as packaged by Debian) > If I modify other lines in my .Xresources file, such as the size of the > font, colors, or xterm geometry, those changes are still honored and > work as expected. > > I'm using Xfce 4.16 and X.Org 1.20.11. ...same here If it hadn't worked, I'd be checking on the order of translation-resources and looking at the debug trace. But since it works for me, I suggest adding the output of "xrdb -q", which might be helpful. -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
ANN: xterm-368
Files: ftp://ftp.invisible-island.net/xterm/current/xterm-368.tgz ftp://ftp.invisible-island.net/xterm/current/xterm-368.tgz.asc ftp://ftp.invisible-island.net/xterm/patches/xterm-368.patch.gz ftp://ftp.invisible-island.net/xterm/patches/xterm-368.patch.gz.asc ftp://ftp.invisible-island.net/xterm/xterm-368.tgz ftp://ftp.invisible-island.net/xterm/xterm-368.tgz.asc Patch #368 - 2021/06/07 * add DefaultOff option to RenderFont resource, as part of the session-management feature. * add auto-scroll-lock feature (patch by add Stelios Bounanos). * update the window-size information returned via TIOCGWINSZ when rows/columns are unchanged but the font-size changes (report by Nick Black). * improve session-management feature by saving/restoring the font settings. * update config.guess, config.sub -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
Bug#988554: xterm does not render U+A7BA ... U+A7F6
On Mon, May 17, 2021 at 09:22:35AM +0200, Uwe Waldmann wrote: > > According to https://unicodeplus.com/U+A7BA > > > > The character Ꞻ (Latin Capital Letter Glottal A) is represented by the > > Unicode codepoint U+A7BA. It is encoded in the Latin Extended-D block, > > which belongs to the Basic Multilingual Plane. It was added to Unicode > > in version 12.0 (March, 2019). It is HTML encoded as Ꞻ. > > > > xterm #344 is a little earlier than that. Its fallback copy of wcwidth > > doesn't list that range (I updated the table to Unicode 12 in #345, > > and added a test-driver around that time). > > > > The system wcwidth doesn't cover that range either. > > > > Characters which aren't known to wcwidth are treated as nonprinting... > > > > (In Debian 9.1, it still worked correctly.) > > > > hmm - which version of xterm was that? > > > > I'm guessing that it was #327 > > yes. > > > (it should not have worked, but there's always the possibility that I > > fixed a bug which was making it appear to work) > > OK, that's possible. Thanks for the explanation. In #327, xterm's wcwidth checked if the codes were combining characters (using a table), or control characters and (for example this case) matched it against some ranges of double-width characters. If it was none of those, it assumed single-width. Starting in #330, I added another table "unknowns" to account for codes which had no specific width: Patch #330 - 2017/06/20 * modify wcwidth.c to return -1 for non-Unicode values, and adjust a couple of blocks to better match assumptions about ambiguous-width characters in other implementations. Also modify wcwidth.c to support configurable soft-hyphen, so there is no drawback to using this version rather than a system wcwidth. -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
Bug#988554: xterm does not render U+A7BA ... U+A7F6
On Sat, May 15, 2021 at 04:11:12PM +0200, Uwe Waldmann wrote: > Package: xterm > Version: 344-1+deb10u1 > Severity: important > > Dear Maintainer, > > xterm renders all characters between U+A7BA and U+A7F6 with width zero, > that is, not at all, even if they are present in the chosen font. > For instance, According to https://unicodeplus.com/U+A7BA The character Ꞻ (Latin Capital Letter Glottal A) is represented by the Unicode codepoint U+A7BA. It is encoded in the Latin Extended-D block, which belongs to the Basic Multilingual Plane. It was added to Unicode in version 12.0 (March, 2019). It is HTML encoded as Ꞻ. xterm #344 is a little earlier than that. Its fallback copy of wcwidth doesn't list that range (I updated the table to Unicode 12 in #345, and added a test-driver around that time). The system wcwidth doesn't cover that range either. Characters which aren't known to wcwidth are treated as nonprinting... > printf '<\uA7B9>\n' > > displays "" with a slash through "u" (correct), whereas > > printf '<\uA7BA>\n' > > displays "<>" (incorrect) instead of "" with an apostrophe before > "A". The problem shows up with arbitrary fonts (both pcf and otb are > affected). Using -mk_width does not change the situation. > > (In Debian 9.1, it still worked correctly.) hmm - which version of xterm was that? I'm guessing that it was #327 (it should not have worked, but there's always the possibility that I fixed a bug which was making it appear to work) -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
Bug#988315: xterm menu display garbled
On Thu, May 13, 2021 at 09:12:01AM +0200, Philipp Marek wrote: > > > > If that's the case, trying a different window manager (xfce4 for > > > > instance) > > > > would show if the window manager is the appropriate place to go. > > > > > > Sorry I'm running LXQT, which uses xfce4 by default: > > > > > >1755 ?Sl 0:00 \_ > > > /usr/lib/x86_64-linux-gnu/xfce4/xfconf/xfconfd > > > > Those are utilities -- but the window manager defaults to openbox. > > Here's a slice from the output of pstree showing that: > > Ah yeah, right, sorry. > > $ wmctrl -m > Name: Xfwm4 > Class: xfwm4 > PID: 1728 > Window manager's "showing the desktop" mode: N/A > > apt tells me > > xfwm4 - window manager of the Xfce project > > and > > $ ps fax | grep openbox >389565 pts/15 S+ 0:00 | \_ grep openbox > $ > > so it looks like the window manager is not at fault. > > If I "ssh -X @localhost xterm", so that my personal > ~/.Xresources > don't apply, I can reproduce the blinking pixels; with "xpra" I still don't > have the right or bottom borders, but the blinking pixels do not appear. > >390309 ?RLl0:04 /usr/bin/python3 /usr/bin/xpra start > --ssh=ssh > -l ard --start=xterm >390310 ?Sl 0:01 \_ Xvfb-for-Xpra-S390306 +extension GLX > +extension Composite -scre >390452 ?S 0:00 \_ xterm >390511 pts/20 Ss 0:00 \_ sh >390519 pts/20 R+ 0:00 \_ ps fax > > xpra says "Client OpenGL: disabled", "window rendering: GTK3: Cairo (1)". > > glxinfo says (abbreviated): > > name of display: :0 > display: :0 screen: 0 > direct rendering: Yes > server glx vendor string: SGI > server glx version string: 1.4 > server glx extensions: > ... > client glx vendor string: Mesa Project and SGI > client glx version string: 1.4 > client glx extensions: > ... > GLX version: 1.4 > GLX extensions: > ... > Extended renderer info (GLX_MESA_query_renderer): > Vendor: Intel (0x8086) > Device: Mesa Intel(R) UHD Graphics 620 (KBL GT2) (0x5917) > Version: 20.3.4 > Accelerated: yes > Video memory: 3072MB > Unified memory: yes > Preferred profile: core (0x1) > Max core profile version: 4.6 > Max compat profile version: 4.6 > Max GLES1 profile version: 1.1 > Max GLES[23] profile version: 3.2 > OpenGL vendor string: Intel > OpenGL renderer string: Mesa Intel(R) UHD Graphics 620 (KBL GT2) > OpenGL core profile version string: 4.6 (Core Profile) Mesa 20.3.4 > OpenGL core profile shading language version string: 4.60 > OpenGL core profile context flags: (none) > OpenGL core profile profile mask: core profile > OpenGL core profile extensions: > ... > OpenGL version string: 4.6 (Compatibility Profile) Mesa 20.3.4 > OpenGL shading language version string: 4.60 > OpenGL context flags: (none) > OpenGL profile mask: compatibility profile > OpenGL extensions: > ... > OpenGL ES profile version string: OpenGL ES 3.2 Mesa 20.3.4 > OpenGL ES profile shading language version string: OpenGL ES GLSL ES > 3.20 > OpenGL ES profile extensions: > ... > 122 GLX Visuals > ... > > > Can I disable OpenGL for a single application or a single window, perhaps? I expect that the answer is "no". (this is in the area of "X server", though admittedly "add-ons"). -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
Bug#988315: xterm menu display garbled
On Wed, May 12, 2021 at 08:38:03AM +0200, Philipp Marek wrote: > > If that's the case, trying a different window manager (xfce4 for > > instance) > > would show if the window manager is the appropriate place to go. > > Sorry I'm running LXQT, which uses xfce4 by default: > >1755 ?Sl 0:00 \_ > /usr/lib/x86_64-linux-gnu/xfce4/xfconf/xfconfd Those are utilities -- but the window manager defaults to openbox. Here's a slice from the output of pstree showing that: |-gdm3-+-gdm-session-wor-+-gdm-x-session-+-Xorg---5*[{Xorg}] | | | |-lxqt-session-+-lxqt-globalkeys---3*[{lxqt-globalkeys}] | | | | |-lxqt-notificati---10*[{lxqt-notificati}] | | | | |-lxqt-panel---11*[{lxqt-panel}] | | | | |-lxqt-policykit4*[{lxqt-policykit-}] | | | | |-lxqt-powermanag---2*[{lxqt-powermanag}] | | | | |-lxqt-runner---2*[{lxqt-runner}] | | | | |-openbox | | | | |-pcmanfm-qt-+-dragon---15*[{dragon}] | | | | | `-12*[{pcmanfm-qt}] | | | | |-ssh-agent | | | | |-xmessage | | | | `-10*[{lxqt-session}] | | | `-2*[{gdm-x-session}] | | `-2*[{gdm-session-wor}] | `-2*[{gdm3}] I set up LXQT this morning, but none of the window managers which it offered me as a choice were related to XFCE4, so I chose openbox. xterm seems to run properly in that (see screenshot). -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
Bug#988315: xterm menu display garbled
On Tue, May 11, 2021 at 10:59:16AM +0200, Philipp Marek wrote: > > It's possible that you have some font resource (such as a proportional > > font) which confuses it, causing it to write outside its window. > > XTerm*faceName: DejaVu Sans Mono actually Xaw uses only bitmap fonts (though some versions of fontconfig can be told to offer those fonts...) Thinking that locale might be a clue, I tried setting it to de_AT.UTF-8, without seeing any problems. > > But that would be apparent in xterm (thinking that a wildcard font > > resource which affects one would affect both). > > > > Given that, I'm expecting that the answer is that the X server > > (for some less-used device) is not handling the window properly. > > Hmmm > > 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (rev > 07) I can't tell :-( That gets into hardware dependencies. In your first comment, you mentioned "the few existing pixels blink". That makes it sound like the X server (since the contents of the window from xterm's point of view are generally static, unless programmed to blink using an escape sequence). If this had been simply a missing border, I'd ask about the window manager (noting that on a couple of machines, I see the gnome stuff overriding the resource-settings, while most window managers leave that alone). Then again (one of those was Fedora34, whose effect was apparent because it took about a second to _redraw_ the menu border), you might be using some version of gnome-session/-shell/-whatever, which has bugs in its attempt to redraw the border. If that's the case, trying a different window manager (xfce4 for instance) would show if the window manager is the appropriate place to go. (xterm has had its own problems with drawing, but so far this doesn't match any of the situations where I would assume xterm's at fault) -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
Bug#988315: xterm menu display garbled
On Tue, May 11, 2021 at 08:00:24AM +0200, Philipp Marek wrote: > > That's more likely a problem with the X server than xterm > > (the menus are via Xaw, which is pretty stable). > > So the menus being cut off on the right and the bottom is on purpose? > > > > For instance, > > you might be using Wayland... > > No, I don't think so: > >1156 ?Ssl0:17 /usr/bin/sddm >1199 tty7 Ssl+ 161:33 \_ /usr/lib/xorg/Xorg -nolisten tcp -auth > /var/run/sddm/{ef674451-7b94-4f32-8c33-3e49df7fdecc} -background none > -noreset -displayfd 17 -seat seat0 vt7 > > And I don't have any other garbage on the display either... Xaw (e.g,. libxaw7:amd64) draws the menus, but uses X resources. In a quick check (looking at the debugging trace), I suppose that xterm's event-loop may handle exposure events for the menus(*), but xterm doesn't know what's in the menus, in that level of detail. It's possible that you have some font resource (such as a proportional font) which confuses it, causing it to write outside its window. But that would be apparent in xterm (thinking that a wildcard font resource which affects one would affect both). Given that, I'm expecting that the answer is that the X server (for some less-used device) is not handling the window properly. (*) the debugging trace shows me the window-id, but not the creator... -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
Bug#988315: xterm menu display garbled
On Mon, May 10, 2021 at 12:53:44PM +0200, Philipp Marek wrote: > Package: xterm > Version: 367-1 > Severity: minor > X-Debbugs-Cc: phil...@marek.priv.at > > Please see the attached screenshot. > > It doesn't matter which menu I open (Ctrl+left, Ctrl+right, ctrl+middle > mouse button) - the right and bottom borders are always missing. That's more likely a problem with the X server than xterm (the menus are via Xaw, which is pretty stable). For instance, you might be using Wayland... -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
Bug#988221: xterm: uses unescaped backslashes in manpage example
On Sat, May 08, 2021 at 04:21:32AM +0200, Thorsten Glaser wrote: > Package: xterm > Version: 366-1 > Severity: minor > Tags: upstream > X-Debbugs-Cc: t...@mirbsd.de > > The manual page includes example commands such as… > >printf '\033]2;Hello world!\033\' > > … which use unescaped backslashes at the end of the command. > > In general this works… > > $ printf '\' | hd > 5c|\| > > … but when copying this specific example into a larger string, The example is correct, however. xterm's manpage isn't a tutorial on shell programming. -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
ANN: xterm-367
Files: ftp://ftp.invisible-island.net/xterm/current/xterm-367.tgz ftp://ftp.invisible-island.net/xterm/current/xterm-367.tgz.asc ftp://ftp.invisible-island.net/xterm/patches/xterm-367.patch.gz ftp://ftp.invisible-island.net/xterm/patches/xterm-367.patch.gz.asc ftp://ftp.invisible-island.net/xterm/xterm-367.tgz ftp://ftp.invisible-island.net/xterm/xterm-367.tgz.asc Patch #367 - 2021/03/26 * add OSC 22 to allow programs to select different pointer cursor at runtime. * change configuration for no-return functions to use _Noreturn when it is available, because clang --analyze does not properly handle the gcc noreturn attribute. * add cursorTheme resource to provide a way to enable or disable the cursor theme feature. * modified CopyWait event retries to use shorter sleeps, to improve responsiveness (tmux #2556). * improve quoting/escaping in demo-scripts per shellcheck. * add resizeByPixel resource, to permit disabling window manager resizing-hints (patch by Tim Oehl). * corrected printOptsImmediate handling of alternate-screen (report by Abhijit Dasgupta). * update sample terminfo to more closely match ncurses. * add/improve limit-checks for Xlib calls (report by Roman Fiedler). * fix a typo in the help-message (report by Tomas Korbar). -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
Bug#984615: xterm: bug in CVE-2021-27135 patch in at least stretch
On Sat, Mar 06, 2021 at 06:46:25PM +0100, Sven Joachim wrote: ... > Run xterm under valgrind and select some text. Valgrind will be very > unhappy with xterm 327-2+deb9u1 but should not show up any errors in valgrind usually has something to say, but (noting that I'm only interested in what it says when I configure --with-valgrind(*)), I get a report of ~5000 lines using these options OPTS="-v \ --num-callers=10 \ --error-limit=no \ --show-reachable=yes \ --leak-resolution=high \ --track-origins=yes \ --leak-check=yes \ --show-reachable=yes" ...and almost all of that is stuff that I can't fix without adding interfaces in X11, Xt and Xaw. (*) asan2 also has things to say, but most of that is not useful without a complete set of debug-libraries (again, X11/Xt/Xaw). -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
Bug#984615: xterm: bug in CVE-2021-27135 patch in at least stretch
On Sat, Mar 06, 2021 at 06:07:43PM +, Thorsten Glaser wrote: > Sven Joachim dixit: > > >I see that this might be a problem (albeit unlikely to happen in > >practice), however I have trouble understanding exactly where a > >use-after-realloc bug comes into play. Maybe Thorsten can help me fix > >my blindness? > > The next time something is selected, the code a little further > up will check if the allocated size is sufficient, and, if so, > use screen->selection_data which was the pre-realloc address of > line. > > >> I am glad and surprised that sid is okay and there doesn't seem to be > > The code in sid completely differs (structures, variable names, etc). The renaming (selection_size) comes from patch #338, which looks like this item: Patch #338 - 2018/12/09 * amend solution for Debian #758633 to ensure that replies for bracketed paste are not sent while processing a selection for exec-formatted (Debian #913237). > >suggestion you could also apply the patches to the SaltTextAway() > >function from xterm 365e. > > If 365e is like 366 (currently in sid), you’ll have lots of fun due > to the renamed everything. 366 is current. I have some changes for 367 which I'll put out after seeing what I can do to improve performance with fwvm active-icon. > I’d rather Tom changed xterm upstream to address the realloc-failure > difference. I know he reads Debian bugreports ;-) and he’s really > busy so probably takes longer to respond. it used to be the case that downstream would ask my opinion on patches like this -- it's been a while since anyone did -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
Bug#816289: #816289 luit: unable to use advertised conversion charset
That works with luit 2.0 (which is older than this bug report). I don't expect that cc'ing Juliusz Chroboczek as mentioned had much effect, since he's not been involved with luit for about 15 years. https://invisible-island.net/luit/luit.html -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
ANN: xterm-366
Files: ftp://ftp.invisible-island.net/xterm/current/xterm-366.tgz ftp://ftp.invisible-island.net/xterm/current/xterm-366.tgz.asc ftp://ftp.invisible-island.net/xterm/patches/xterm-366.patch.gz ftp://ftp.invisible-island.net/xterm/patches/xterm-366.patch.gz.asc ftp://ftp.invisible-island.net/xterm/xterm-366.tgz ftp://ftp.invisible-island.net/xterm/xterm-366.tgz.asc Patch #366 - 2021/02/10 * correct a compiler-warning fix in patch #352 which allowed sign-extension of coordinate values (report by "CismonX"). * correct upper-limit for selection buffer, accounting for combining characters (report/testcase by Tavis Ormandy). * with alwaysHighlight true, xterm does not properly track focus. The screen->select FOCUS flag remains always on, which prevents bellIsUrgent from working, as the urgent WM_HINT flag is only set in setXUrgency() when the window is not focused. Fix this by updating screen->select in unselectwindow() regardless of the value of always_highlight (patch by Jiri Bohac). * improve fix for interaction between SRM and ENQ (report by Grant Taylor). * build-fix for --with-Xaw3dxft, needed when --with-toolbar is omitted (report by Jimmy Olgeni, Emanuel Haupt). -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
ANN: xterm-365
Files: ftp://ftp.invisible-island.net/xterm/current/xterm-365.tgz ftp://ftp.invisible-island.net/xterm/current/xterm-365.tgz.asc ftp://ftp.invisible-island.net/xterm/patches/xterm-365.patch.gz ftp://ftp.invisible-island.net/xterm/patches/xterm-365.patch.gz.asc ftp://ftp.invisible-island.net/xterm/xterm-365.tgz ftp://ftp.invisible-island.net/xterm/xterm-365.tgz.asc Patch #365 - 2021/02/03 * amend fix for “word” selection in patch #364 to limit that to the insert-selectable action, which reads data from the screen. This restores the interactive behavior where double-clicking on a “word” would make subsequent selection extensions by words as well as suppressing some boundary-checks (report by David Wolfskill, FreeBSD #253225). -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
ANN: xterm-364
Files: ftp://ftp.invisible-island.net/xterm/current/xterm-364.tgz ftp://ftp.invisible-island.net/xterm/patches/xterm-364.patch.gz ftp://ftp.invisible-island.net/xterm/patches/xterm-364.patch.gz.asc ftp://ftp.invisible-island.net/xterm/xterm-364.tgz Patch #364 - 2021/02/02 * add -fc option. * correct/improve limit-checks for SRM versus ENQ from patch #344 (report by Tom Szilagyi). * enable XftFont resource in Xaw3dxft configuration (patch by Tavis Ormandy). * improve quoting/escaping in build-scripts per shellcheck. * add libpcre2-posix to the packages tested for --with-pcre2 option, needed with Fedora (report by Tomas Korbar). * correct a typo in manual page, and note that KeepClipboard may not be compiled-in (report/patch by Sean C Farley). * corrected boundary-checks for “word” selection used in onNClicks resources (report by Tavis Ormandy). * update to autoconf-2.52-20210101, to improve shellcheck warnings. * improve configure check for desktop categories. -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
ANN: xterm-363
Files: ftp://ftp.invisible-island.net/xterm/current/xterm-363.tgz ftp://ftp.invisible-island.net/xterm/current/xterm-363.tgz.asc ftp://ftp.invisible-island.net/xterm/patches/xterm-363.patch.gz ftp://ftp.invisible-island.net/xterm/patches/xterm-363.patch.gz.asc ftp://ftp.invisible-island.net/xterm/xterm-363.tgz ftp://ftp.invisible-island.net/xterm/xterm-363.tgz.asc Patch #363 - 2020/12/26 * disable groff hyphenation in generated html when using man2html. * change SCS “&4” Cyrillic to non-NRCS, per VT520 manual. * amend fix for SCS in patch #198 to remove DEL rather than converting it to a space (report by Thomas Wolff). * modify state transitions for selecting character sets to eliminate an ambiguity between the “A” used in VT220 versus VT320. * improve error recovery when selecting characters by resetting to US ASCII when no suitable encoding is found, e.g., attempting to use an NRCS sequence when NRCS is not enabled. * turn off hyphenation in “.txt” conversion, prompted by groff changes. * add VT5xx ISO Latin-2 (prompted by discussion with Thomas Wolff). * amend change from patch #361 to event-handling in CopyWait to handle active-icon as a special case (Debian #975687). * add call to loadColorTable to get the visual information needed to decode BE RGBA32 color format (patch by Leandro Lupori). * modify the resource-parsing for disallowedPasteControls and similar lists of names/numbers to recognize “~;” (tilde) for cancelling a given name/number. * add ENQ, EOT and NUL to default for disallowedPasteControls. * change default for disallowedPasteControls to omit the tab character (suggested by Harald Dunkel). * fix swapped height/width in regisScreenSize and maxGraphicSize resources using "auto" value, from patch #314 (report by Anton Lavrentiev) * revise patch #362 change for shift-modifier versus mouse protocol and select/paste by adding resource shiftEscape, which can be enabled via a control sequence (prompted by discussion with Matthijs van Duin). * simplify/improve ifdef in trace code for using a separate set of files for each run of xterm. * add options -r and -t to vttests/query-color.pl to show the 6-digit RGB code and actual colors. * add nel to xterm-basic terminfo. * alter vttests/modify-keys.pl to omit HTML reference links to the modified-keys table where no keycode was available. -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
Bug#965293: Please backport mesa to stable (buster)
Control: severity -1 important Changing this bug from severity whishlist to important, as that severity description seems to match the situation more closely: a bug which has a major effect on the usability of a package, without rendering it completely unusable to everyone. All people using AMD RNDA 1.0 GPUs, which got released since almost a year ago, cannot use any graphical session due to old mesa. The current kernel in backports is 5.9.6+1~bpo10+1[0], which supports this and newer GPU releases; so the single thing still breaking usage is the old mesa version in buster and no backport available. So again, please, consider releasing a current testing version to backports. FWIW, this would not be a new precedent, in Debian Stretch we got regular backports, starting not even a year after Stretch got released[1], so having no backport in Buster, which got released almost 1.5 year ago, seems a bit odd. regards, Thomas [0]: https://tracker.debian.org/news/1198182/accepted-linux-signed-amd64-5961bpo101-source-into-buster-backports-buster-backports/ [1]: https://tracker.debian.org/news/955405/accepted-mesa-1739-1bpo91-source-amd64-into-stretch-backports-stretch-backports/
Bug#975687: xterm: loses text lines, even descenders from some lines
On Sun, Dec 20, 2020 at 11:39:15PM +, Thorsten Glaser wrote: > Thomas Dickey dixit: > > >I'm guessing that it's timing, e.g., xterm could wait a few milliseconds > >to retry and then give up on that loop, in case the window events don't > >arrive rapidly enough. > > “rapidly enough” as criterium isn’t going to help everyone. > > We have multi-GHz desktop bolides, few-MHz m68k/SPARC/POWER/… machines, > and running X11 over various network protocols (X, VNC, RDP, NX, x2go), > with varying latencies. > > If the solution for this issue with XCheckWindowEvent is dependent on > such things, I’d argue that not using XCheckWindowEvent is the correct > fix instead ☺ I'm aware of that. It's called a "dilemma" (in this case, a bug which I'm easily able to reproduce versus one that I'm not). Since I'm able to reproduce the case with the active-icon, I might decide to use XCheckWindowEvent with a timeout for that scenario and the XWindowEvent for the other. -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
Bug#975687: xterm: loses text lines, even descenders from some lines
On Sun, Dec 20, 2020 at 10:40:39PM +, Thorsten Glaser wrote: > Thomas Dickey dixit: > > >how far below? > > > >Just the window-decoration, or a line or so? > > About a line, give or take (for the syslog window, the last line > is the cursor, so I don’t need it, and I took a bit more than a > line there; for that test, it’s a bit less). > > >Looking at the changes for #361, there's the changes for wrap-mark, > >and copy-wait. The latter was just this: > > I did… > > begin 644 xterm_362-1.0.1.debdiff ... > … to revert that, and voilà, problem fixed. > > Perhaps some events are lost with XCheckWindowEvent or something? The descriptions for XWindowEvent and XCheckWindowEvent are very similar. I'm guessing that it's timing, e.g., xterm could wait a few milliseconds to retry and then give up on that loop, in case the window events don't arrive rapidly enough. -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
Bug#975687: xterm: loses text lines, even descenders from some lines
On Sun, Dec 20, 2020 at 07:47:15PM +, Thorsten Glaser wrote: > Thomas Dickey dixit: > > >I see that version in testing, but don't see a problem on the screen. > >I made a short script to cat those lines to the terminal, sleeping 0.2 > >seconds between bursts, and the result looks ok, even with a magnifier. > > Indeed, tricky. I experimented with this a bit. > > I can reproduce this if I change your script from while true > to for x in 1 2 3 (so it does that only three times) but, and > this is important, move the xterm so that its bottom is below > the bottom end of the X11 screen. how far below? Just the window-decoration, or a line or so? From the screenshot in your followup, I'm guessing the latter. > If I move the syslog terminal up by a few pixels, the problem > does not happen. > > If I use other terminal, font, etc. sizes, I also get display > corruption effects which vary (see screenshot). > > If I switch virtual workspaces (Ctrl-Alt-[1-8←→] in evilwm) > the effects go away as well. ...repainting uses a different path. > Maybe you can reproduce it with this info? I'll try that. (Of course if it depends on video hardware, etc., that won't succeed). Looking at the changes for #361, there's the changes for wrap-mark, and copy-wait. The latter was just this: REV:1.859 util.c 2020/10/14 00:45:31 tom tags:xterm-361a, xterm-361, xterm-360e replace a call to XWindowEvent (which will block if there's no exposure events) in CopyWait with a call to XCheckWindowEvent (which lets me bail out on no more exposure events). That seems to fix a hang reported by Dave Kemper when iconifying/deiconifying while blasting lots of characters to an active icon. The XWindowEvent call dates back to 1991. --- util.c 2020/10/01 08:11:43 1.858 +++ util.c 2020/10/14 00:45:31 1.859 @@ -1,4 +1,4 @@ -/* $XTermId: util.c,v 1.857 2020/09/29 08:05:41 tom Exp $ */ +/* $XTermId: util.c,v 1.858 2020/10/01 08:11:43 tom Exp $ */ /* * Copyright 1999-2019,2020 by Thomas E. Dickey @@ -2082,8 +2082,10 @@ return; #endif -for (;;) { - XWindowEvent(screen->display, VWindow(screen), ExposureMask, &reply); +while (XCheckWindowEvent(screen->display, +VWindow(screen), +ExposureMask, +&reply)) { switch (reply.type) { case Expose: HandleExposure(xw, &reply); as part of this: https://github.com/ThomasDickey/xterm-snapshots/commit/d98fb8ac7854e9b7906e7d1e65cf446ba6c78432#diff-e21ac3db1fb1f4c2521d0911da5ca3414412766a9aecad6c4c0cfad5d67b5165R2085 -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
Bug#976172: xfonts-utils: fonttosfnt gives error "Couldn't select character map"
Package: xfonts-utils Version: 1:7.7+6 Severity: normal It seems that the call to FT_Select_Charmap at read.c:231 does not work for some fonts, at least. I tried it with a Latin-1 encoded BDF font. By default, fonttosfnt wants to reencode as Unicode, which is fine. Freetype finds the Latin-1 encoding of the BDF font, and thus decides it needs to be reencoded, although for some reason it records the charmap as Unicode (which is fine, being a superset of Latin-1). The logic at read.c:228 then tries to select the ft_encoding_none charmap, which is only valid for bitmap fonts with no encoding (reading the freetype source, ftobjs.c:3512). But this bitmap font has an encoding, so it is not allowed. I think the test at line 228 is bogus: for a symbol font (i.e. one that declares no encoding) it’s OK to use ft_encoding_none. Otherwise, if we’re recoding (i.e. we have a mapping) then we should use ft_encoding_unicode. If we’re in neither case, then we should just use the existing charmap, i.e. not call FT_Select_Charmap. Hence, this stanza should look something like: rc = 0; // In case we do nothing if(symbol) rc = FT_Select_Charmap(face, ft_encoding_none); else if(mapping) rc = FT_Select_Charmap(face, ft_encoding_unicode); Of course in my case, the selection of a Charmap is a no-op, since it merely reselects the only charmap in the font. -- System Information: Debian Release: bullseye/sid APT prefers focal-updates APT policy: (500, 'focal-updates'), (500, 'focal-security'), (500, 'focal'), (100, 'focal-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-54-generic (SMP w/16 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages xfonts-utils depends on: ii libc6 2.31-0ubuntu9.1 ii libfontenc1 1:1.1.4-0ubuntu1 ii libfreetype6 2.10.1-2ubuntu0.1 ii x11-common1:7.7+19ubuntu14 ii xfonts-encodings 1:1.0.5-0ubuntu1 ii zlib1g1:1.2.11.dfsg-2ubuntu1.2 xfonts-utils recommends no packages. xfonts-utils suggests no packages. -- no debconf information
Bug#976159: xfonts-utils: bdftopcf(1) documentation of some flags is misleading
Package: xfonts-utils Version: 1:7.7+6 Severity: normal The -t and -i flags for bdftopcf are documented thus: -t When this option is specified, bdftopcf will convert fonts into "terminal" fonts when possible. A terminal font has each glyph image padded to the same size; the X server can usually render these types of fonts more quickly. -i This option inhibits the normal computation of ink metrics. When a font has glyph images which do not fill the bitmap image (i.e., the "on" pixels don't extend to the edges of the metrics) bdftopcf computes the actual ink metrics and places them in the .pcf file; the -t option inhibits this behaviour. However, looking at the source code bdftopcf.c, they are both parsed, but ignored. I suggest changing the man page to read: -t, -i Ignored. Further, it may be worth patching the code, as currently it reads: case 't': /* attempt to make terminal fonts if possible */ if (argv[0][2] != '\0') goto usage; break; case 'i': /* inhibit ink metric computation */ if (argv[0][2] != '\0') goto usage; break; It might make sense to add a “TODO:” at the start of each comment. Further investigation might reveal that the flags used to do something, but the above changes would at least help reduce confusion without prejudice to (unlikely?) future improvements. -- System Information: Debian Release: bullseye/sid APT prefers focal-updates APT policy: (500, 'focal-updates'), (500, 'focal-security'), (500, 'focal'), (100, 'focal-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-54-generic (SMP w/16 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages xfonts-utils depends on: ii libc6 2.31-0ubuntu9.1 ii libfontenc1 1:1.1.4-0ubuntu1 ii libfreetype6 2.10.1-2ubuntu0.1 ii x11-common1:7.7+19ubuntu14 ii xfonts-encodings 1:1.0.5-0ubuntu1 ii zlib1g1:1.2.11.dfsg-2ubuntu1.2 xfonts-utils recommends no packages. xfonts-utils suggests no packages. -- no debconf information
Bug#975687: xterm: loses text lines, even descenders from some lines
On Fri, Nov 27, 2020 at 12:04:07AM +, Thorsten Glaser wrote: > Hi Thomas, > > >If you're going to compile it, the debug-trace can be useful > >(--enable-trace). If not, the -report-fonts option is helpful. > > I hadn’t recompiled, at least not with actual changes. > The -report-fonts output is attached, fNorm is the one > in question. > > I did a little bisecting: Debian’s 360-1 did not have > the bug, 361-1 did, and when recompiling 360-1 unchanged > in a current unstable chroot, it also doesn’t have the > bug, so it’s not something else that changed. sounds promising - > Looking at debian/patches/ in 361-1 it also doesn’t change > any of the code, so I guess it’s some upstream change. > > >If I can reproduce it, I'll see what I can do. > > If not but you still have patches I could test, send them > and I’ll apply them and rebuild locally. If you need the > trace, I’ll also do that, but not tonight… fwiw https://invisible-island.net/personal/git-exports.html https://github.com/ThomasDickey/xterm-snapshots > > bye, > //mirabilos > -- > 21:12⎜ sogar bei opensolaris haben die von der community so > ziemlich jeden mist eingebaut │ man sollte unices nich so machen das > desktopuser zuviel intresse kriegen │ das macht die code base kaputt > 21:13⎜ linux war früher auch mal besser :D > Script started on 2020-11-27 00:46:29+01:00 [TERM="screen" TTY="/dev/pts/15" > COLUMNS="113" LINES="34"] > tglase@tglase-nb:~ $ /usr/bin/xterm +sb -fg black -geom 90x11+475+637 > -report-fonts -bg cornflowerblue -e tail +sb -fg black -geom 90x11+475+637 -report-fonts -bg cornflowerblue -e tail <-F /var/log/syslog > Loaded VTFonts(default) > fNorm: -misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso10646-1 > all chars: no > default char: 0 > direction: 0 > ascent:11 > descent: 2 > first char:0 > last char: 65535 > maximum-chars: 65536 > missing-chars: 61413 > present-chars: 4123 > min_byte1: 0 > max_byte1: 255 > properties:22 > min_bounds: > lbearing: 0 > rbearing: 0 > width:6 > ascent: -1 > descent: -10 > max_bounds: > lbearing: 5 > rbearing: 6 > width:6 > ascent: 11 > descent: 2 > fBold: -misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso10646-1 > all chars: no > default char: 0 > direction: 0 > ascent:11 > descent: 2 > first char:0 > last char: 65535 > maximum-chars: 65536 > missing-chars: 61413 > present-chars: 4123 > min_byte1: 0 > max_byte1: 255 > properties:22 > min_bounds: > lbearing: 0 > rbearing: 0 > width:6 > ascent: -1 > descent: -10 > max_bounds: > lbearing: 5 > rbearing: 6 > width:6 > ascent: 11 > descent: 2 > fWide: -misc-fixed-medium-r-normal-ja-13-120-75-75-c-120-iso10646-1 > all chars: no > default char: 0 > direction: 0 > ascent:11 > descent: 2 > first char:0 > last char: 65535 > maximum-chars: 65536 > missing-chars: 46328 > present-chars: 19208 > min_byte1: 0 > max_byte1: 255 > properties:23 > min_bounds: > lbearing: 0 > rbearing: 0 > width:12 > ascent: -1 > descent: -10 > max_bounds: > lbearing: 11 > rbearing: 12 > width:12 > ascent: 11 > d