Your message dated Mon, 11 Nov 2024 17:05:49 +0000
with message-id <e1taxrj-002clq...@fasolo.debian.org>
and subject line Bug#1085402: Removed package(s) from unstable
has caused the Debian Bug report #679091,
regarding latencytop: fails with error "no protocol specified"
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 ow...@bugs.debian.org
immediately.)


-- 
679091: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679091
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: latencytop
Version: 0.5
Severity: important

Dear Maintainer,

mango:~# latencytop
mount: none already mounted or /sys/kernel/debug/ busy
mount: according to mtab, debugfs is already mounted on /sys/kernel/debug
No protocol specified


Its already mounted, but that should not matter:

mango:~# mount  | grep debug
debugfs on /sys/kernel/debug type debugfs (rw,relatime)


When unmounting it I get:

mango:~# umount /sys/kernel/debug
mango:~# latencytop
No protocol specified


Then after another try:

mango:~# latencytop
mount: none already mounted or /sys/kernel/debug/ busy
mount: according to mtab, none is already mounted on /sys/kernel/debug
No protocol specified


Maybe it doesn´t work cause current Debian kernels do not have latencytop
support enabled:

mango:~# grep LATENCY /boot/config-*
/boot/config-3.2.0-2-amd64:CONFIG_HAVE_LATENCYTOP_SUPPORT=y
/boot/config-3.2.0-2-amd64:# CONFIG_LATENCYTOP is not set
/boot/config-3.3.0-trunk-amd64:CONFIG_HAVE_LATENCYTOP_SUPPORT=y
/boot/config-3.3.0-trunk-amd64:# CONFIG_LATENCYTOP is not set
/boot/config-3.4-trunk-amd64:CONFIG_HAVE_LATENCYTOP_SUPPORT=y
/boot/config-3.4-trunk-amd64:# CONFIG_LATENCYTOP is not set

(Using 3.4 here.)


Okay, verified. These are two bugs.

latencytop tries to connect X server by default. When I try from a sux
session I indeed get:

ms@mango:~> sux
Passwort: 
xauth:  file /root/.Xauthority does not exist
bash: Kann die Prozessgruppe des Terminals nicht setzen (-1).: Unpassender 
IOCTL (I/O-Control) für das Gerät
bash: Keine Job Steuerung in dieser Shell.
mango:/home/ms# latencytop
mount: none already mounted or /sys/kernel/debug/ busy
mount: according to mtab, none is already mounted on /sys/kernel/debug
Please enable the CONFIG_LATENCYTOP configuration in your kernel.
Exiting...


So I let this bug be about the X.org support and how to enable ncurses
and create another one for the missing support for it in the kernel. I
will cross-reference them.


Bug #628883 is related, but it refers to improving the manpage. This one
is about getting latencytop to run out of the box again.

Thanks,
Martin

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing'), (450, 'unstable'), (110, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.4-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages latencytop depends on:
ii  libc6         2.13-33
ii  libglib2.0-0  2.32.3-1
ii  libgtk2.0-0   2.24.10-1
ii  libncursesw5  5.9-9

latencytop recommends no packages.

latencytop suggests no packages.

-- no debconf information



--- End Message ---
--- Begin Message ---
Version: 0.5.0-3+rm

Dear submitter,

as the package latencytop has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1085402

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)

--- End Message ---

Reply via email to