[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1052248: marked as done (xterm not found in gui (Gnome) applications)

Your message dated Tue, 19 Sep 2023 19:11:49 +0200
with message-id <0f96dc73ec6f66f51970bd3ffc599a87@debian.org>
and subject line Re: Bug#1052248: xterm not found in gui (Gnome) applications
has caused the Debian Bug report #1052248,
regarding xterm not found in gui (Gnome) applications
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1052248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052248
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: xterm
Version: 384-1
Severity: normal

I want to be able to open an xterm from my desktop environment (which
happens to be Gnome 45).  But xterm is missing from the list of known GUI
applications.

Actually the problem is a little worse than that: there is a entry
labelled "Xterm standard terminal emulator for the X Window System",
but when I click on it loads up "Gnome Software" tool showing the
xterm information page, instead of opening xterm itself.

For context, gnome-terminal (which I would normally use from Gnome) is
actually broken at the moment and crashes every 5 minutes. So I NEED
to be able to access the alternative X terminals.

xterm does provide /usr/share/applications/debian-xterm.desktop which
sets Exec=xterm, so Gnome should be able to launch it. I'm not sure if
the problem meas there's a syntax error in the desktop file.  Maybe
it's a bug in Gnome.

For reference, I should compare this bug report against #645736.  What
645736 is asking is diameterically the opposite of what I mean. In my
opinion the request of #645736 is categorically wrong.  If I've
installed software and it has a desktop entry, I want to be able to
see that software in the list of GUI applications.


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en
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.37-10
ii  libfontconfig1  2.14.2-6
ii  libfreetype6    2.13.2+dfsg-1
ii  libice6         2:1.0.10-1
ii  libtinfo6       6.4+20230625-2
ii  libutempter0    1.2.1-3
ii  libx11-6        2:1.8.6-1
ii  libxaw7         2:1.0.14-1
ii  libxext6        2:1.3.4-1+b1
ii  libxft2         2.3.6-1
ii  libxinerama1    2:1.1.4-3
ii  libxmu6         2:1.1.3-3
ii  libxpm4         1:3.5.12-1.1
ii  libxt6          1:1.2.1-1.1
ii  xbitmaps        1.1.1-2.2

Versions of packages xterm recommends:
ii  x11-utils  7.7+5

Versions of packages xterm suggests:
pn  xfonts-cyrillic  <none>

-- no debconf information

--- End Message ---
--- Begin Message --- I'm not the first person tricked by this Gnome con. It's raised both in #856858 (xterm) and in #921705 (gnome-menus)
The problem is gnome-menus and Gnome Developer arrogance ("our way is the Only Way"). gnome-menus has explicitly crippled xterm's own configuration by placing xterm in a blacklist at gnome-menus-blacklist. Not cool.
Jeremy Bicha's idea in #856858 is probably the most effective resolution. Place the xterm desktop files in a separate xterm-desktop package. Then gnome-menus can stop blacklisting xterm. If xterm-desktop is installed, it declares explicitly that it should be found in the menus.
My bug doesn't add any more to that discussion, apart from affirming support for #856858, so I'll close this bug now.
--- End Message ---
Reply to: