Jonathan Wiltshire wrote:
...
Thanks. The bug #1050288 isn't fixed in unstable according to the BTS,
which is a requirement. What's the status?
The problem described in #1050288 does not longer occur since NSIS 3.09.
The problem appeared in Debian 12 because the Mingw-w64 toolchain now
On Sat, 26 Aug 2023 14:23, Thomas Gaugler wrote:
Therefore I would appreciate if you create a "bookworm proposed
updates request" by issuing the "reportbug release.debian.org" command
on a Debian system.
I did, but obviously it was incomplete. Unfortunately the immediate
error report didn't
This should no longer happen with smartd 7.4, see
https://www.smartmontools.org/ticket/1222
Regards,
Christian
smartmontools.org
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: n...@packages.debian.org, christian.fra...@t-online.de
Control: affects -1 + src:nsis
Please update nsis 3.08-3 to 3.09.
[ Reason ]
Generated installers contain
A manual download of nsis{-common}-3.09-1 from debian testing and 'dpgk
--install --force-all' succeeded and makensis works then. With this
version, the problem does not occur.
A backport of this version to bookworm should fix the problem.
Severity of this bug promoted to 'grave' because further tests show that
generated installers may not work at all:
Testcase:
$ cat /etc/debian_version
12.1
$ makensis -VERSION
v3.08-3
$ cat test.nsi
RequestExecutionLevel user
Section "Test"
MessageBox MB_OK "Hello, World!"
SectionEnd
$
Control: severity -1 grave
.
This is also not the case with the upstream 3.08 and 3.09 builds for
windows which are available at
https://sourceforge.net/projects/nsis/files/NSIS%203/
Related: https://sourceforge.net/p/nsis/bugs/1299/
--
Regards
Christian Franke
smartmontools.org
Hi Bjarni,
this bug
Split a punctuation from a single argument, if a two-font macro is meant
64:.B /etc/smartd.conf.
and minor mandoc / groff warnings are now fixed upstream:
https://www.smartmontools.org/changeset/5506
https://www.smartmontools.org/changeset/5520
The remaining
Thanks for the suggestions. Possibly too late for upcoming smartmontools
7.4, but will be addressed later.
In general, non-trivial syntax changes require tests with several
formatting tools including those used on Free/Net/OpenBSD. Changes shall
also work with older tool versions still used
Fixed upstream: https://www.smartmontools.org/changeset/5475
Alban Browaeys wrote:
Why is smartd of type notify? Does it send notification to systemd via
sd_notify?
Yes, otherwise this would not appear in systemctl status output:
Status: "No devices to monitor"
See 'man smartd' for details.
Unfortunately it does not properly work in conjunction
Possible fix for the package: Add '-q nodev0' or '-q never' to ExecStart
in smartmontools.service.
Workaround for users: Add one of these to smartd_opts in
/etc/default/smartmontools.
Option '-q nodev0' is available since smartmontools 7.3. Then smartd
will exit with status 0 instead of 17
A note for upcoming smartmontools release 7.4:
It NOTIFY_SOCKET is set in environment, smartd 7.4 will sd_notify
"EXTEND_TIMEOUT_USEC=2000" for each disk during device registration
and then for each disk during first device checks.No such calls will
occur after "READY=1" has been
What is the idea behind these emails?
The drive reports bad sectors pending for reallocation (HDD) or retirement
(SSD).
What is the recommended way to turn them off?
Run a long self-test (smartctl -t long ...). Also check Device Statistics and
Pending Defects log (smartctl -l devstat -l
ich change the 'no devices' exit code from 17 to 0. The
service should be no longer reported as failed then. "No devices to
monitor" is reported via sd_notify() if configured.
Regards,
Christian Franke
smartmontools.org
be processed if used interactively.
Related security issues:
https://security-tracker.debian.org/tracker/CVE-2021-32749
https://www.smartmontools.org/ticket/1535
Fixed in mailutils 3.13, see https://savannah.gnu.org/bugs/?60937
If possible, please backport the fix to (old)stable.
Regar
Please test recent build from https://builds.smartmontools.org/
Possibly related report for Micron_2200_MTFDHBA1T0TCK with firmware P1MU003:
https://www.smartmontools.org/ticket/1404
smartd.conf file ?
If DEVICESCAN is used: How many devices are detected ?
Triggering self-tests should not require any additional memory as the
actual tests are handled by drive firmware.
Regards,
Christian
smartmontools.org
Fixed upstream in r5077: https://www.smartmontools.org/changeset/5077
BTW: https://www.smartmontools.org/changeset/5078
Added upstream in r5084, r5087:
https://www.smartmontools.org/changeset/5084
https://www.smartmontools.org/changeset/5087
Please update the drive database.
Dear Maintainer (or NMUploader),
if possible, please also include the attached patch to a
smartmontools-7.0 package.
Details: https://www.smartmontools.org/ticket/1154
Thanks,
Christian
smartmontools.org
Index: ataprint.cpp
===
> Read NVMe SMART/Health Information failed: NVMe Status 0x4002
Which device name did you use for smartctl 6.6 ?
If it was '/dev/nvme0n1', please retry with '/dev/nvme0' or
'/dev/nvme0n1,0x'.
Smartctl 6.6 uses selected namespace to read SMART/Health and Error logs.
Smartctl 7.0 always
Marc Haber wrote:
On Thu, Jan 10, 2019 at 03:47:24PM +0100, Christoph Anton Mitterer wrote:
...
Plus it automatically imports the shipped public key into the keyring
of the executing user… which is IMO also unacceptable.
Agreed, the script should use its own keyring.
The script creates a
Christoph Anton Mitterer wrote:
...
I've just hat a quick glance at current upstream:
https://svn.code.sf.net/p/smartmontools/code/trunk/smartmontools/update-smart-drivedb.in
Comments are welcome.
It seems it now contains some code verification, both X.509 CA based
and/or OpenPGP based.
I
BTW: smartmontools 7.0 supports Type=notify.
https://www.smartmontools.org/browser/tags/RELEASE_7_0/smartmontools/NEWS
smartmontools 7.0 enables '-with-nvme-devicescan' by default on Linux.
https://www.smartmontools.org/browser/tags/RELEASE_7_0/smartmontools/NEWS
Please provide two differing "smartctl -i -l error /dev/nvmeX" outputs
of an affected device.
The error log may be filled with "Invalid Field in Command" or a similar
"Generic Command" (0x0) errors.
Smartd should possibly limit the error count to entries with Status Code
Type "Media and Data
This means that the package maintainer did not override the upstream
decision to exclude NVMe devices from default DEVICESCAN. Here the
related message printed by ./configure if no '--with*-nvme-devicescan'
option is specified:
"
configure: WARNING:
This version of smartmontools provides
The file /etc/default/smartmontools has no effect if systemd is used.
Simply disable the service with:
# systemctl disable smartd
See also upstream tickets:
https://www.smartmontools.org/ticket/1080
https://www.smartmontools.org/ticket/1081
There is no smartd command line option -U (see 'smartd -h' or 'man
smartd') but a smartd.conf directive -U (see 'smartd -D' or 'man
smartd.conf').
Conclusion: Place '-U 198+' in the file /etc/smartd.conf instead.
Please upgrade to smartmontools-6.6 and add '-d removable' to
smartd.conf (see Bug#770872).
For a smartmontools-6.6+ package, please reconsider the decision to
remove the update-smart-drivedb script (Bug#804299) as it now validates
the downloaded file.
See https://www.smartmontools.org/ticket/751 for details.
Related: Bug#824795
Fixed upstream since r4399.
https://www.smartmontools.org/changeset/4399
Fix is included in new smartmontools-6.6 release.
The update-smart-drivedb script now validates the downloaded file with
GnuPG. The assumptions which resulted in the removal of the update
script (Bug#804299) are possibly no longer true.
See https://www.smartmontools.org/ticket/751 for details.
Smartmontools 6.5 provides a new ./configure option
'--without-update-smart-drivedb'. It removes the update script, its man
page and all references from the other man pages.
See: https://www.smartmontools.org/changeset/4299
Please consider to provide drivedb.h updates as a separate package
Christoph Anton Mitterer wrote:
- Removing "-F nologdir" option from Intel 320/710 SSD entries may
result in drive a firmware crash if Log Directory is read.
- Setting a bogus USB "-d TYPE" option may result in disconnected USB
devices or more serious problems.
I think in the past there were
Christoph Anton Mitterer wrote:
Even if it would be properly secured with some key that upstream has,
it would allow them to selectively inject code into Debian systems.
Then anything we could do upstream (e.g. provide a drivedb.h.asc file,
check it in update-smart-drivedb) won't help.
Some
Please provide info about affected drive models and sample temperature
outputs from smartd and smartctl.
Note that a ATA/SATA devices may have various sources for current
temperature: SMART Attributes (190, 194, ...), SCT Status and Device
Statistics. Smartctl could read all, but smartd only
Jon Bendtsen wrote:
UUID is not enough.
I would rather that the emails like the one quoted below would include as much
information as possible or maybe configureable.
smartctl -i /dev/sds
fdisk -l /dev/sds
...
sg_inq /dev/sds
This could be done by a custom script run via '-M exec'
Package: quagga
Version: 0.99.23.1-1
Severity: minor
Hello Chris,
doing a standard Debian installation and then installing Quagga, it will use
less as a pager for vtysh. While less might be a neat pager for vtysh with
more configuration, the less with default configuration is a usability hurdle.
For that the package recommends two MTAs: 'mailx' or 'mailutils'. Both of these
packages do not provide a 'mail' binary or script nor neither does any other
standard Debian package (e.g. do 'apt-file search bin/mail')
This test is not valid to check for missing commands.
The /usr/bin/mail
release 6.3 (r3976).
The Debian package build from smartmontools r4002 still provides the
original version. No problem for this package, but future versions of
the upstream man page might contain significant changes.
Thanks,
Christian Franke
smartmontools.org
--
To UNSUBSCRIBE, email
There is random garbage in the upper bytes of the 48-bit LBA field:
00312581807 = 0x12A19EAF (Max possible LBA)
00020399756 = 0x0137468C (Self-test Log #10/#11)
138688809354892 = 0x7E230137468C (Extended Self-test Log #10)
244890465683084 = 0xDEBA0137468C (Extended Self-test Log
Package: grub-common
Version: 2.02~beta2-21
Severity: important
Dear Maintainer,
I just tried to install Debian Jessie using the current debian-installer for
Jessie.
I went through the installation and created a partition layout like this:
/dev/vda1 2GiB Swap
/dev/vda2 40GiB JFS2
I
with the 'st' chain.
Regards,
Christian
2014-07-07 Christian Franke fra...@computer.org
* eval.c (expand): Fix missing initialization of st_head.quote.
(Closes #636601 ?)
diff -rup posh-0.12.3.orig/eval.c posh-0.12.3/eval.c
--- posh-0.12.3.orig/eval.c 2012-11-01 15:33:25.0 +0100
+++ posh
I added ./configure options --with-smartdscriptdir and
--with-smartdplugindir to upstream smartmontools.
Defaults are unchanged:
--with-smartdscriptdir=${sysconfdir}
--with-smartdplugindir=${smartdscriptdir}/smartd_warning.d
Thanks,
Christian
--
To UNSUBSCRIBE, email to
Added to upstream drivedb.h r3908. Please run
/usr/sbin/update-smart-drivedb to test.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Fixed upstream in r3854.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: ikiwiki
Version: 3.20130212
Severity: important
The following bug has been observed with testing, an upgrade to unstable
did not bring an improvement.
Setup:
I have an ikiwiki at https://sublab.org/wiki/ which supports editing via
CGI. It is served by an Apache which has Alias /wiki/
Just to avoid confusion: At the given URL, I hot-wired the parentlinks
plugin so that it will not generate relative links, so the described
behaviour is not observable there.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Fix is included in upstream smartmontools-6.1.tar.gz.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Such a long test duration is actually uncommon for the short SMART
self-test. This is a drive firmware bug which cannot be fixed by
smartmontools.
All SMART self-tests are controlled by drive firmware. Smartctl and
smartd only issue the ATA command to start the test.
--
To UNSUBSCRIBE,
Bob Proulx wrote:
Christian Franke wrote:
This is logged as LOG_INFO and no sign of trouble. Tracking of
self-test and offline data collection status was added in 5.40 and
5.41 and is enabled by default (-l selftest, -a).
I don't understand. The log message says that the action was
suspended
Could not reproduce this with the same package.
But there is actually a very old bug in the option parser: errno is not
cleared before strtoull(). Now fixed upstream in r3661.
Possible workarounds for this package:
- Enabling debug messages first with -r ioctl,1 clears errno, -t
The Areca SAS patch adds the Enclosure Parameter to '-d areca' option.
This was added upstream in r3540 and therefore should be already
included in Debian package 5.42+svn3561-X.
Please note that this requires upcoming 1.51 Areca firmware or a recent
beta version. Firmware versions = 1.50 do
This should be fixed in Debian package 5.42+svn3539-1.
Offline data collection status is no longer tracked unless '-l
offlinests' is specified.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Fixed upstream in r3529.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Using /dev/disk/by-id/... as a device name should work for non-RAID
volumes since 5.41 r3269.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Some pass-through I/O-controls may fail if called immediately after
resume from suspend.
There is a fix in upstream smartd r3424 (included in 5.42).
Some extra sleep() time is added if resume from suspend is detected.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with
Added to upstream drivedb.h r3471. Please run
/usr/sbin/update-smart-drivedb to test.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
This is logged as LOG_INFO and no sign of trouble. Tracking of self-test
and offline data collection status was added in 5.40 and 5.41 and is
enabled by default (-l selftest, -a).
Smartmontools 5.42 adds new directives -l selfteststs (included in -a)
and -l offlinests (not included in -a) to
I changed the warning message accordingly (drivedb.h r3456).
Run /usr/sbin/update-smart-drivedb to test.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
On Sun, 17 Jul 2011 17:51:14 +0200, Christian Franke wrote:
This fault now also occured with version 2.6.39-3 of the
linux-image-2.6.39-2-amd64 package.
On Fri, 22 Jul 2011 01:19:33 +0200, Ben Hutchings wrote:
I think this bug was fixed in 2.6.39-3 along with bug #629932. Let us
know
Package: linux-2.6
Version: 2.6.39-3
Severity: normal
Tags: wheezy
Unfortunately I have not found a way to reproduce this problem yet. So
the only thing I can give is a describtion what I did.
The box has some ethernet interfaces, among them eth0 and eth1.
eth0 is part of a bridge, which is
This fault now also occured with version 2.6.39-3 of the
linux-image-2.6.39-2-amd64 package. At the time of the fault there was
definetly no traffic on eth1. Most traffic at that time was NFS from a
box attached to the network at eth0 to an NFS server in a VM attached to
br0, though there might
Added to upstream drivedb.h r3404. Please run
/usr/sbin/update-smart-drivedb to test.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
According to
http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?DocId=207951
the ST31000340AS with firmware SD15 is affected and should be updated to
SD1A.
Did Seagate actually fix this serious bug without changing the reported
firmware version number? If this is the case the only
Added 2010-07-21 to upstream drivedb.h r3126 (USB 0x0411:0x0181) and
r3127 (SAMSUNG HM250HI). This is included in Debian wheezy
smartmontools-5.40+svn3296-1
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Added to upstream drivedb.h r3321. Please run
/usr/sbin/update-smart-drivedb to test.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
The os_generic.cpp is a dummy OS interface module which is selected by
configure for platforms not yet supported by smartmontools.
I would suggest to remove the smartmontools package from hurd-i386.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
The new Intel X25-M firmware 2CV102M3 fixes possible drive hangs when
reading SMART self-test log.
http://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=18363
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Package: mplayer
Version: 2:1.0~rc3++final.dfsg1-1
Severity: important
Tags: squeeze
nihi...@menelaos:~$ wget
http://ftp.ccc.de/congress/27C3/mp4-h264-HQ/4018-en-frozencache.mp4
[...]
nihi...@menelaos:~$ mplayer 4018-en-frozencache.mp4
MPlayer 1.0rc3-4.4.4 (C) 2000-2009 MPlayer Team
mplayer:
and prints
attributes of SandForce based SSDs correctly.
--
Christian Franke
smartmontools-supp...@lists.sourceforge.net
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
.
--
Christian Franke
smartmontools-supp...@lists.sourceforge.net
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
We cannot fix this. A note was added to man page in r3097.
Please set this bug to wontfix.
--
Christian Franke
smartmontools-supp...@lists.sourceforge.net
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas
It is not possible to print such a warning for ATA/SATA devices. The ATA
standard does not specify a method to check whether Attribute Autosave
is enabled. I will add a note to the man page.
--
Christian Franke
smartmontools-supp...@lists.sourceforge.net
--
To UNSUBSCRIBE, email to debian
at the
beginning of MailWarning(), see lines 2849-51 of:
http://ftp.de.debian.org/debian/pool/main/s/smartmontools/smartmontools_5.39-3.diff.gz
Please reopen this bug.
Cheers,
Christian
--
Christian Franke
smartmontools-supp...@lists.sourceforge.net
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ
Package: bind9
Version: 1:9.5.1.dfsg.P3-1
Severity: important
I need the named to bind on a specific address, let's say 2001:123:1234::1.
I specify: listen-on-v6 { 2001:123:1234::1/128; }; in the named.conf.options.
When starting named with /etc/init.d/bind9, it does not listen on IPv6.
The init
81 matches
Mail list logo
