xterm huge no longer works, displays same size as large.

Bug #1880821 reported by Robert Dinse
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xterm (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Whether I select large or huge, same size results, huge no longer gives me a very large font which owing to my crappy eyesight is sometimes helpful.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xterm 353-1ubuntu1
Uname: Linux 5.6.0 x86_64
.tmp.unity_support_test.1:

ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted
Date: Wed May 27 00:07:20 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
GraphicsCard:
 Red Hat, Inc. Virtio GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller])
   Subsystem: Red Hat, Inc. Virtio GPU [1af4:1100]
Lsusb:
 Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
 /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
 /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
 /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
 /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
     |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M
MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.6.0 root=UUID=2332aa64-69b1-479f-88e1-dd92583809d9 ro
SourcePackage: xterm
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/06/2015
dmi.bios.vendor: EFI Development Kit II / OVMF
dmi.bios.version: 0.0.0
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-q35-eoan
dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-eoan:cvnQEMU:ct1:cvrpc-q35-eoan:
dmi.product.name: Standard PC (Q35 + ICH9, 2009)
dmi.product.version: pc-q35-eoan
dmi.sys.vendor: QEMU
version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

Revision history for this message
Robert Dinse (nanook) wrote :
Revision history for this message
Nathan Teodosio (nteodosio) wrote :

Can you please attach the output of "appres XTerm" and "xlsfonts"?

Note this can be easily fixed by setting appropriate font resources in ~/.Xresources. See "man xterm" and look for "font6". See for example https://askubuntu.com/questions/161652/how-to-change-the-default-font-size-of-xterm for more context.

Revision history for this message
Robert Dinse (nanook) wrote :

     First, I was using mate-terminal not xterm, but second, I've made a couple of changes since I filed this bug report. I've switched to Intel graphics and I'm using the kernel x-server now. Second, I've upgraded to Ubuntu-Mate 22.04. I'm not sure which of these changes resolved this but this is no longer an issue with 22.04 and the kernel X-server.

Revision history for this message
Robert Dinse (nanook) wrote :

     If I'm the only one reporting this feel free to close it as it is no longer an issue for me.

Revision history for this message
Nathan Teodosio (nteodosio) wrote :

> First, I was using mate-terminal not xterm

You reported the bug against Xterm but you were using Mate-terminal? But Mate-terminal doesn't have a huge and large font, does it?

Revision history for this message
Robert Dinse (nanook) wrote : Re: [Bug 1880821] Re: xterm huge no longer works, displays same size as large.
Download full text (4.1 KiB)

      I am confused, sorry it WAS xterm. At any rate, it is fixed in 22.04 so
no longer an issue.

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
  Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
    Knowledgeable human assistance, not telephone trees or script readers.
  See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

On Wed, 6 Jul 2022, Nathan Teodosio wrote:

> Date: Wed, 06 Jul 2022 13:10:13 -0000
> From: Nathan Teodosio <email address hidden>
> To: <email address hidden>
> Subject: [Bug 1880821] Re: xterm huge no longer works,
> displays same size as large.
>
>> First, I was using mate-terminal not xterm
>
> You reported the bug against Xterm but you were using Mate-terminal? But
> Mate-terminal doesn't have a huge and large font, does it?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1880821
>
> Title:
> xterm huge no longer works, displays same size as large.
>
> Status in xterm package in Ubuntu:
> New
>
> Bug description:
> Whether I select large or huge, same size results, huge no longer
> gives me a very large font which owing to my crappy eyesight is
> sometimes helpful.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 20.04
> Package: xterm 353-1ubuntu1
> Uname: Linux 5.6.0 x86_64
> .tmp.unity_support_test.1:
>
> ApportVersion: 2.20.11-0ubuntu27.2
> Architecture: amd64
> BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
> CasperMD5CheckResult: skip
> CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
> CompositorRunning: None
> CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted
> Date: Wed May 27 00:07:20 2020
> DistUpgraded: Fresh install
> DistroCodename: focal
> DistroVariant: ubuntu
> GraphicsCard:
> Red Hat, Inc. Virtio GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller])
> Subsystem: Red Hat, Inc. Virtio GPU [1af4:1100]
> Lsusb:
> Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Lsusb-t:
> /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
> /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
> /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
> /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
> |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M
> MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
> ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.6.0 root=UUID=2332aa64-69b1-479f-88e1-dd92583809d9 ro
> SourcePackage: xterm
> UpgradeStatus: No upgrade log present (probably fresh install)
> dmi.bios.date: 02/06/2015
> dmi.bios.vendor: EFI Development Kit II / OVMF
> dmi.bios.version: 0.0.0
> dmi.chassis.type: 1
> ...

Read more...

Changed in xterm (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.