Package: wtmpdb
Version: 0.12.0-3
Severity: normal
X-Debbugs-Cc: invernom...@paranoici.org

Hello Chris,
thanks for maintaining this package, which ships command 'last' (as a
symlink).

I installed it on a number of amd64 Debian boxes, without any major
issue.

Then I installed it on the i386 Debian box described below:

  # aptitude install wtmpdb
  [...]
  # exit

Right after having installed it, I have again logged in (through ssh) and:

  $ last
  $USER    ssh          $REMOTE_IP       Thu Jan  1 02:11 - still logged in
  reboot   system boot  6.9.9-686        Thu Jan  1 02:11 - still running
  
  /var/lib/wtmpdb/wtmp.db begins Thu Jan  1 02:11:34 1970

Dates and times seem to be completely wrong, but the system clock is OK:

  $ date -R
  Sat, 20 Jul 2024 16:52:00 +0200

What is funny (or maybe not?!?) is that it seems that it reads all timestamp
as a fixed value. If I log out and then back in, I get:

  $ last
  $USER    ssh          $REMOTE_IP       Thu Jan  1 02:11 - still logged in
  $USER    ssh          $REMOTE_IP       Thu Jan  1 02:11 - 02:11  (00:00)
  reboot   system boot  6.9.9-686        Thu Jan  1 02:11 - still running
  
  /var/lib/wtmpdb/wtmp.db begins Thu Jan  1 02:11:34 1970

In other words, wtmpdb seems to think that everything happens "compressed"
in a single instant at 02:11:34 of January, the 1st, 1970, as in some weird
sci-fi story!   ;-)

Other tools seem to be well aware that we are not living in that weird
sci-fi universe:

  $ who
  $USER    pts/0        2024-07-20 17:09 ($REMOTE_IP)

There must be some bug related with the time_t reading, maybe related to
the fact that i386 has been [excluded] from the 64-bit time_t transition,
thus remaining with the 32-bit time_t...

[excluded]: <https://wiki.debian.org/ReleaseGoals/64bit-time#Decision>


Please fix this bug and/or forward the bug report upstream, as
appropriate.
Thanks for your time (or for your time_t !!!).


P.S.: I would like to see this bug fixed before Thu Jan  1 02:11:34 1970
      ;-p


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (800, 'testing'), (500, 'unstable')
Architecture: i386 (i586)

Kernel: Linux 6.9.9-686 (SMP w/1 CPU thread; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages wtmpdb depends on:
ii  libaudit1    1:3.1.2-4+b1
ii  libc6        2.38-14
ii  libsystemd0  256.2-1
ii  libwtmpdb0   0.12.0-3

Versions of packages wtmpdb recommends:
ii  libpam-wtmpdb  0.12.0-3

wtmpdb suggests no packages.

-- no debconf information

Reply via email to