Package: zstd
Version: 1.5.5+dfsg2-2
Severity: normal
Dear Maintainer,
here is a quick benchmark of the zstd build in Debian:
$ zstd -V
*** Zstandard CLI (64-bit) v1.5.5, by Yann Collet ***
$ zstd -b
3#Synthetic 50% : 1000 -> 3230847 (x3.095), 168.9 MB/s, 1310.7 MB/s
and here is
Hi again,
the error log in my previous message comes from this directory:
/var/lib/systemd/pstore/7285820828300/
Each time the system reboots, a new directory is created, and 3 files are
created in it.
For the sake of completeness, here are the 3 files.
Thanks,
--
Package: src:linux
Version: 6.1.55-1
Severity: normal
Dear Maintainer,
each time this system is rebooted, during shutdown, the kernel outputs the
following error message.
The kernel thinks it encountered a "Hardware Error", but the error is most
probably not a hardware error, because I also
Package: src:linux
Version: 6.1.20-2
Severity: normal
Dear Maintainer,
each time I shutdown this system (a Debian 11 system with the bookworm kernel),
the Linux kernel outputs the following error message.
This error could have been unnoticed, but:
- it triggers an alarm in the iDRAC
On 1/18/23 16:46, Salvatore Bonaccorso wrote:
Would it be possible to test 6.1.7, which contains related nfs changes
with the nfsd filecache?
Yes, of course, as soon as it is available as a Debian package...
Regards,
--
Laurent.
Package: gpxviewer
Version: 1.1.0-5
Severity: normal
Dear Maintainer,
according to the package metadata the homepage of the project is as follows:
$ dpkg -s gpxviewer
[...]
Version: 1.1.0-5
[...]
Homepage: https://github.com/andrewgee/gpxviewer
However, on this page, I only see tags up to
On 12/5/22 18:26, Diederik de Haas wrote:
Do you know what the faulty and fixed 5.10 version were/are?
The problem was not really in the kernel, but in rpc.svcgssd that has trouble
with large Kerberos credentials.
The only problem with 5.10 kernels is that they only display warnings about
On 12/5/22 17:34, Diederik de Haas wrote:
btw: What's the reason for not using a 5.10 kernel on a Stable system?
(Not that I mind, just curious)
Thanks for your interest :>.
I had a NFS problem with the 5.10 kernel and tested a more recent kernel to see
if this problem had been fixed.
(For
Package: src:linux
Version: 5.14.9-2
Severity: important
Dear Maintainer,
I boot this system with the page_poison=1 kernel option and during boot, and
more precisely during SCSI initialization (for external USB disks), I get this
scary error dump:
[3.350394] pagealloc: memory
Package: qemu-system-data
Version: 1:6.1+dfsg-6
Severity: normal
Dear Maintainer,
when I start a KDE program I see the following error messages:
kf.service.services: The desktop entry file "/usr/share/applications/qemu.desktop" has
Type= "Application" but no Exec line
kf.service.sycoca:
On 27/09/2021 21.40, Salvatore Bonaccorso wrote:
I believe this is fixed by
https://salsa.debian.org/kernel-team/linux/-/commit/b7f5082c34ea43622ebd9cd42f5fdd7b5ed49761
pending for the next upload.
Thanks a lot for the quick fix!
--
Laurent.
Hi,
since the backtrace contains functions from Tomoyo, I tried to disable Tomoyo
with ccsecurity=off on the kernel command line but it does not help.
Any other suggestion ?
Thanks,
--
Laurent.
Package: src:linux
Version: 5.14.6-2
Severity: important
Dear Maintainer,
on a system that is used as a Samba server, the kernel logs are spammed by
WARNINGs such as this one:
Sep 26 07:42:40 hostname kernel: [ cut here ]
Sep 26 07:42:40 hostname kernel: Buffer
On 3/18/21 9:08 PM, Charles Curley wrote:
How much memory does the computer have?
It is a VM with 1GB of RAM.
On my FIT-PCs, using the same
installer (but with firmware), I see that debian installer (d-i) goes
to ext2 rather than ext4. They have 228Mi of physical memory. On my IBM
R51, with
On 3/18/21 7:51 PM, Ben Hutchings wrote:
I think that the installer uses ext2 for /boot because some boot
loaders only support(ed) ext2 and not its successor filesystem formats.
But I think that's an historical problem for most release
architectures.
If that is true, then an even simpler
Package: debian-installer
Severity: normal
Dear Maintainers,
I did a test installation using debian-testing-amd64-netinst.iso from
2021-03-15 (Debian bullseye/11), chose the LVM option,
and noticed that once the system is installed and boots, the kernel complains
with this message:
ext2
Package: libxapp1
Version: 2.0.6-2
Severity: normal
Dear Maintainer,
here is the problem:
$ dpkg-query -W -f='${Conffiles}\n' | grep obsolete$
[...]
/etc/xdg/autostart/xapp-sn-watcher.desktop a9fa3be7aaf46761adcdb856c63c125f
obsolete
Simply installing libxapp1 on a system is sufficient to
On 1/23/21 9:07 PM, Mehdi Dogguy wrote:
Thanks for the bugreport and sorry for not replying earlier!
No problem!
I wasn't able to reproduce this bug.
Thanks for trying!
FWIW, I've just uploaded dochelp 0.1.8 with a couple of bugfixes
(none is related to memory management though). Can
On 1/12/21 1:02 PM, Vasyl Gello wrote:
This is probably a regression due to ABI change in libnfs. Let me
check if upstream has a fix for it.
Thanks a lot for looking at this bug!
Do you use NFS shares with Kodi in your HTPC setup?
Not at all. I am just trying to rebuild kodi before doing
Package: kodi
Version: 2:19.0~beta2+dfsg1-5
Severity: important
Dear Maintainer,
in fact there are 2 compilation errors. Note that my system has dev packages
from experimental, but libnfs-dev and libdrm-dev are from sid:
Package: libnfs-dev
Version: 4.0.0-1
Package: libdrm-dev
Hi,
here is more information with error messages from pipewire in the logs:
# journalctl | grep pipewire
Jan 11 11:58:45 hosname dbus-daemon[589]: [system] Activating via systemd: service
name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.10'
(uid=0 pid=4725
Package: pipewire
Version: 0.3.15-1
Severity: normal
Dear Maintainer,
* What led up to the situation?
I log in with SSH to the root account of a system where pipewire is installed.
* What was the outcome of this action?
A pipewire process is started automatically by systemd:
#
Package: extra-cmake-modules
Version: 5.77.0-2
Severity: normal
Dear Maintainer,
when I run "deborphan" on my system, the extra-cmake-modules package is always listed as an
"orphaned" library. This comes from the fact that this package is in the "libs" section
and no other package depends
Package: plocate
Version: 1.1.0-2
Severity: normal
Dear Maintainer,
here is a sequence of commands to demonstrate the problem:
- We start with a system with neither mlocate nor plocate and check that the
system is free of obsolete conffiles
# apt purge plocate mlocate
# dpkg-query -W
On 11/5/20 10:39 PM, Debian Bug Tracking System wrote:
#973829: xfwm4: tracker complains about xfce-workspaces-settings.desktop
It has been closed by Debian FTP Masters (reply to
Yves-Alexis Perez ).
xfwm4 (4.15.3-1) experimental; urgency=medium
.
* New upstream version 4.15.3
- Fix
Hi,
I confirm that removing the blank line fixes the problem.
Thanks,
--
Laurent.
Package: xfwm4
Version: 4.15.2-1
Severity: normal
Dear Maintainer,
here is an error message I see in the logs of my system:
# journalctl | grep tracker | grep xfce
Nov 05 19:10:20 hostname tracker-extract[2240]: Could not load desktop file
On 10/29/20 6:10 PM, Jonas Smedegaard wrote:
Did you have fonts-noto-core 20181227-1 installed, or installed and then
removed, or installed and then purged, when you ran that command?
I don't remember exactly. However I tried to reproduce the problem on a recent
system both with
On 10/29/20 4:30 PM, Jonas Smedegaard wrote:
Please elaborate: What_is_ the issue?
It is my understanding that packages should not create obsolete conffiles.
That's what I understood when reading this:
On 10/24/20 6:22 PM, Bdale Garbee wrote:
I took a quick look and the problem is with the use of localhost: in
the filename,
Thanks for checking! In fact the problem also exists for remote hosts.
it appears to be unrelated to the compression algorithm chosen.
With xz I can create correct
Package: tar
Version: 1.30+dfsg-7
Severity: important
Dear Maintainer,
here is a a short list of commands that demonstrate the problem (it needs a SSH
server):
$ mkdir foo
$ tar --zstd -cvf localhost:foo.tar.zst foo
$ zstd -t foo.tar.zst
foo.tar.zst : 0 MB... zstd:
Package: apt
Version: 2.1.10
Severity: normal
Dear Maintainer,
* What led up to the situation?
I am trying to perform an upgrade on a sid system.
* What exactly did you do (or not do) that was effective (or
ineffective)?
# apt upgrade
Reading package lists... Done
Building
Package: sendfile
Version: 2.1b.20080616-6
Severity: normal
Dear Maintainer,
each week I receive an e-mail with the following content:
/etc/cron.weekly/sendfile:
WARNING: tempfile is deprecated; consider using mktemp instead.
Could you please update /etc/cron.weekly/sendfile to use mktemp
Package: plasma-discover
Version: 5.19.4-1
Severity: normal
Dear Maintainer,
I see the following error message in the kernel logs on my system:
[ 1794.049495] systemd-xdg-autostart-generator[3071]: Configuration file
/etc/xdg/autostart/org.kde.discover.notifier.desktop is marked
Package: kmix
Version: 4:20.08.0-1
Severity: normal
Dear Maintainer,
I see the following error message in the kernel logs on my system:
[ 1794.033071] systemd-xdg-autostart-generator[3071]:
/etc/xdg/autostart/kmix_autostart.desktop:6: Unknown key name 'MimeType' in
section 'Desktop
Package: orthanc
Version: 1.7.3+dfsg-1
Severity: normal
Dear Maintainer,
the systemd unit file shipped in orthanc:
/lib/systemd/system/orthanc.service
contains the following line:
Documentation=man orthanc(8) https://book.orthanc-server.com/index.html
which according to systemd is
Package: repsnapper
Version: 2.5a5-2+b1
Severity: normal
Dear Maintainer,
here is the problem:
Setting up flwm (1.02+git2015.10.03+7dbb30-7) ...
Exec key for 'repsnapper' contains '%F', '%U' or '%D' at the wrong place
dpkg: error processing package flwm (--configure):
-- System
Package: deepin-icon-theme
Version: 2020.06.30-1
Severity: normal
Dear Maintainer,
here is the problem:
# apt install deepin-icon-theme
[...]
Unpacking deepin-icon-theme (2020.06.30-1) ...
Setting up deepin-icon-theme (2020.06.30-1) ...
gtk-update-icon-cache: The generated cache was invalid.
Package: pki-base
Version: 10.9.0~a2-2
Severity: serious
Dear Maintainer,
here is the problem:
# source /usr/share/pki/scripts/config
-bash: break: only meaningful in a `for', `while', or `until' loop
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
APT
Package: pki-base
Version: 10.9.0~a2-2
Severity: serious
Dear Maintainer,
here is the problem:
Setting up pki-base (10.9.0~a2-2) ...
dpkg: error processing package pki-base (--configure):
installed pki-base package post-installation script subprocess returned error
exit status 1
Errors
Package: deepin-icon-theme
Version: 2020.06.11-1
Severity: serious
Dear Maintainer,
here is the problem:
Setting up deepin-icon-theme (2020.06.11-1) ...
update-alternatives: error: alternative path
/usr/share/icons/deepin/cursor.theme doesn't exist
dpkg: error processing package
Package: python3-uflash-doc
Version: 1.2.4+dfsg-1
Severity: normal
Dear Maintainer,
here is the problem:
$ dpkg -s python3-uflash-doc
[...]
Suggests: -browser
---^
there is an extra w here.
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
APT
Package: python3-pip
Version: 20.1.1-1
Severity: normal
Dear Maintainer,
running "pip3 debug" ends with a FileNotFoundError exception:
$ pip3 debug
WARNING: This command is only meant for debugging. Do not use this with
automation for parsing and getting these details, since the output and
Package: python3-pip
Version: 20.0.2-5
Severity: normal
Dear Maintainer,
* What led up to the situation?
I was trying all pip3 subcommands.
* What exactly did you do (or not do) that was effective (or
ineffective)?
$ pip3 debug
Traceback (most recent call last):
File
On 4/11/20 9:56 AM, Kan-Ru Chen wrote:
> I can not reproduce the FTBFS issue on my local machine or pbuilder. There is
> also no
> failure reported on buildd network.
Thanks for checking!
> Perhaps there is something local to your environment causing the problem?
Indeed. My system has many
Hi,
thank you for this new package version and attempt to fix this bug!
Unfortunately I am still getting an exception on my system:
Package: python3-pip
Version: 20.0.2-2
# pip3 list --outdated
WARNING: pip is being invoked by an old script wrapper. This will fail in a
future version of
Package: qgis-providers
Version: 3.10.3+dfsg-1+b1
Severity: serious
Dear Maintainer,
here is the problem:
Setting up qgis-providers (3.10.3+dfsg-1+b1) ...
free(): invalid pointer
Aborted (core dumped)
dpkg: error processing package qgis-providers (--configure):
installed qgis-providers
Package: apt
Version: 2.0.0
Severity: normal
Dear Maintainer,
* What led up to the situation?
Those packages are installed on my system:
ii libsingular4m1:amd64
1:4.1.1-p2+ds-4+b1
Package: powertop
Version: 2.11-1
Severity: serious
Dear Maintainer,
here is the problem:
$ apt -b source powertop
Reading package lists... Done
NOTICE: 'powertop' packaging is maintained in the 'Git' version control system
at:
https://salsa.debian.org/debian/powertop.git
Please use:
git
Hi again,
here is some debugging info:
# strace dochelp update
[...]
openat(AT_FDCWD, "/usr/share/doc/lilypond/html/Documentation",
O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = 3
fstat(3, {st_mode=S_IFDIR|0755, st_size=12288, ...}) = 0
getdents64(3, /* 312 entries */, 32768) = 8256
Package: dochelp
Version: 0.1.7+b1
Severity: important
Dear Maintainer,
here is the problem:
# apt upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not
On 04/12/2019 16.15, Brice Goglin wrote:
> PCIe links (since Gen3) are encoded 128 data rate over 130 signal rate.
> That's why you get 3.93 (truncated to 3.9). We decided to keep that
> value exact in hwloc because the data/signal rate is different among
> PCIe generations. We could round it up
Package: hwloc
Version: 2.1.0+dfsg-2
Severity: normal
Dear Maintainer,
my system has a NVMe SSD. It is displayed correctly in lstopo. However the
PCIe link has a value of "3.9" (see attached file) whereas it should probably
be "4.0".
-- System Information:
Debian Release: bullseye/sid
5.11.3+dfsg1-4
ii libqt5xml5 5.11.3+dfsg1-4
ii libstdc++6 9.2.1-8
akonadi-server recommends no packages.
--
Laurent Bonnaud.
https://iut2.univ-grenoble-alpes.fr/formations/les-departements-de-
Package: udev
Version: 243-2
Severity: normal
Dear Maintainer,
here is an error message I see in the journal:
Oct 01 09:32:00 host systemd-udevd[403]:
/usr/lib/udev/rules.d/73-special-net-names.rules:14 Invalid value "/bin/sh -ec
'D=${DEVPATH#*/vio/}; D=${D/*}; D=${D#}; D=${D#0};
Hi,
I reported this issue here:
https://gitlab.gnome.org/GNOME/gdm/issues/513
--
Laurent.
On 7/8/19 6:24 PM, Yves-Alexis Perez wrote:
> Indeed, thanks for the report. I've updated the manpage, that'll be part of
> the next upload.
Thank you for the fix!
--
Laurent.
Package: xfce4-places-plugin
Version: 1.7.0-4
Severity: normal
Dear Maintainer,
this manpage:
/usr/share/man/man2/xfce4-popup-places.22.gz
is in section 22, which is most certainly a mistake.
-- System Information:
Debian Release: 10.0
APT prefers unstable-debug
APT policy: (500,
Package: kded5
Version: 5.54.0-1
Severity: important
Dear Maintainer,
As a defense against machine code injection attacks made possible by buffer
overflow bugs, most Linux distributions have worked over the years to remove as
many rwx memory mappings as possible in processes.
I checked this
Hi,
the bug is still present in the latest 4.19 kernel available in Debian:
# uname -a
Linux erebus4 4.19.0-5-amd64 #1 SMP Debian 4.19.37-1 (2019-05-05) x86_64
GNU/Linux
# dmesg
[...]
[17385.914817] RPC request reserved 228 but used 368
[24814.736955] RPC request reserved 228 but used 368
On 12/9/18 10:08 PM, Pierre-Elliott Bécue wrote:
> I'm sorry nobody gave you any feedback on your bug.
No problem, and sorry to answer after such a long time :>.
> I've made an upload of lxc 3 in unstable. Could you run some tests with it
> and tell me if you get the same issue?
Yes. With
Hi,
this "bug" still exists in the latest 4.19 kernel in Debian:
# uname -a
Linux irancy 4.19.0-4-amd64 #1 SMP Debian 4.19.28-2 (2019-03-15) x86_64
GNU/Linux
# ip addr
[...]
2: eth0: mtu 1500 qdisc pfifo_fast state UP
group default qlen 1000
--
Laurent.
Hi,
the bug is still present in the latest 4.19 kernel available in Debian:
# uname -a
Linux erebus4 4.19.0-4-amd64 #1 SMP Debian 4.19.28-2 (2019-03-15) x86_64
GNU/Linux
# dmesg | grep RPC
[3.742768] systemd[1]: Listening on RPCbind Server Activation Socket.
[3.775310] RPC: Registered
Subject: uwsgi-emperor: duplicate
Package: uwsgi-emperor
Version: 2.0.18-1
Severity: important
Dear Maintainer,
here is the problem:
# systemctl status logrotate.service
● logrotate.service - Rotate log files
Loaded: loaded (/lib/systemd/system/logrotate.service; static; vendor
preset:
On 3/24/19 2:06 PM, Osamu Aoki wrote:
> FYI: I have uploaded 0.41-1 which is essentially code clean up with
> lintian warning removal actions such as adding autopkgtest data.
> So use this 0.41-1, please.
Thanks a lot!
> I will be curious how these affects performance.
SSH connections are now
On 20/03/2019 19.39, Michael Biebl wrote:
> Another info that might help give a clue is setting
> LogLevel=debug in /etc/systemd/user.conf, reboot, log in, then attach
> the output of journalctl --user -b
Thanks, it allowed me to find the cause of the problem:
Mar 21 13:41:49 hostname
On 3/20/19 7:24 PM, Michael Biebl wrote:
>> Do you have any (user) generators which might take a long time?
> Typical places to check:
>
> /usr/lib/systemd/user-environment-generators/
> /usr/lib/systemd/user-generators/
Here is what I have in this system:
# ls -l
On 3/20/19 5:52 PM, Michael Biebl wrote:
> Is this problem reproducible if you login locally?
Yes. When I log in from a local VT, just after typing the password:
- I see the contents of /etc/motd
- I wait for 11 seconds
- then I see the shell prompt
Thanks,
--
Laurent.
On 3/20/19 5:47 PM, Michael Prokop wrote:
> What do you mean with "Further connections are fast", ssh-ing into
> the system as the same user ?
Exactly.
> (do you use ssh with ControlMaster?)
I do not use ControlMaster.
> Is connecting via `ssh -o ControlPath=none ...` also slow?
Using the
On 3/20/19 5:47 PM, Michael Prokop wrote:
> Just a quick shot, are you sure your reverse DNS is OK?
Yes.
> If you set `UseDNS no` in /etc/ssh/sshd_config, is the SSH login faster?
Setting "UseDNS no" does not solve the problem.
Thanks,
--
Laurent.
On 3/20/19 5:52 PM, Michael Biebl wrote:
> Is this problem reproducible if you login locally?
Sorry, I will have to wait until tomorrow to have physical access to this
system...
Thanks,
--
Laurent.
Package: systemd
Version: 241-2
Severity: important
Dear Maintainer,
on this system, an initial ssh connection needs 11 seconds to complete (as root
or any other user). Further connections are fast.
This is not a slow boot problem because it occurs even when the machine has
been booted for
Hi,
the bug is still there in this package version:
Source: linux-signed-amd64 (4.19.28+2)
Version: 4.19.28-2
[ 311.093489] RPC: Unregistered named UNIX socket transport module.
[ 311.093493] RPC: Unregistered udp transport module.
[ 311.093494] RPC: Unregistered tcp transport module.
[
Package: fonts-noto-core
Version: 20181227-1
Severity: normal
Dear Maintainer,
here is the problem:
$ dpkg-query -W -f='${Conffiles}\n' | grep obsolete$
/etc/fonts/conf.avail/30-droid-noto.conf a34074694dce0a5ccc5844ec0a1315ea
obsolete
-- Package-specific info:
Hi,
I tested the latest kernel from sid on a Debian stretch NFS server and I am
still seeing those errors:
# uname -a
Linux xxx 4.19.0-3-amd64 #1 SMP Debian 4.19.20-1 (2019-02-11) x86_64 GNU/Linux
# dmesg | grep RPC
[3.771107] RPC: Registered named UNIX socket transport module.
[
Subject: linux-image-4.19.0-2-rt-amd64-unsigned: BUG
Package: src:linux
Version: 4.19.16-1
Severity: normal
Dear Maintainer,
I was trying to remove the sunrpc module from the kernel and got the following
BUG and backtrace.
Note that the kernel is tainted because of this previous error that is
Hi,
after all these years, this bug still exists:
$ desktop-file-validate /usr/share/applications/mb-applet-battery.desktop
/usr/share/applications/mb-applet-battery.desktop: error: value "PanelApp" for
key "Type" in group "Desktop Entry" is not a registered type value
("Application", "Link"
Package: spice-vdagent
Version: 0.17.0-1
Severity: normal
Dear Maintainer,
here is the problem:
# apt install spice-vdagent
[...]
Setting up spice-vdagent (0.17.0-1) ...
[...]
[/usr/lib/tmpfiles.d/spice-vdagentd.conf:2] Line references path below legacy
directory /var/run/, updating
Package: fail2ban
Version: 0.10.2-2.1
Severity: normal
Dear Maintainer,
here is the problem:
# apt install fail2ban
[...]
Setting up fail2ban (0.10.2-2.1) ...
[fail2ban-tmpfiles.conf:1] Line references path below legacy directory
/var/run/, updating /var/run/fail2ban → /run/fail2ban; please
Source: mesa
Severity: wishlist
Dear Maintainer,
the Mesa source package contains this file:
./mesa-18.1.1/src/intel/tools/intel_sanitize_gpu.c
but it is not built during the Debian binary packages creation. Could you
please build it?
It would be very helpful to debug Mesa issues, such
Package: dhelp
Version: 0.6.25
Severity: normal
Dear Maintainer,
here is the problem:
$ /usr/sbin/dhelp_parse
/usr/lib/ruby/vendor_ruby/debian.rb:223: warning: parentheses after method name
is interpreted as an argument list, not a decomposed argument
/usr/lib/ruby/vendor_ruby/debian.rb:224:
Package: bind9
Version: 1:9.11.3+dfsg-1
Severity: normal
Dear Maintainer,
here is the problem:
# aa-logprof
Reading log entries from /var/log/audit/audit.log.
Updating AppArmor profiles in /etc/apparmor.d.
ERROR: Include file /etc/apparmor.d/local/usr.sbin.named not found
[fatal error:
On 02/06/2018 01:55 PM, Alastair McKinstry wrote:
> This appears to be a downgrade from experimental 3.0.1*.
I confirm that I had experimental packages that I later downgraded.
Thanks for looking at this and for the fix!
--
Laurent.
Package: trousers
Version: 0.3.14+fixed1-1
Severity: important
Dear Maintainer,
here is the problem:
# apt install tpm-tools
[...]
Apr 08 12:33:44 xeelee trousers[12046]: * Starting Trusted Computing daemon
tcsd
Apr 08 12:33:44 xeelee trousers[12046]: /etc/init.d/trousers: 32: [: /dev/tpm0:
Not a bug according to upstream. Closing...
--
Laurent.
> I confirm that on another test system with an AMD GPU I do not observe the
> deleted mappings.
With the more recent Xorg/mesa version now in sid the deleted objects have a
different name:
# grep i915 /proc/$(pidof Xorg)/maps
7f4c2793-7f4c27935000 rw-s 00:16 1011645
Package: xserver-xorg-core
Version: 2:1.19.6-1
Severity: normal
Dear Maintainer,
the Xorg process runs with one memory zone that has both write and execute
permissions:
# grep rwxp /proc/$(pidof Xorg)/maps
7f4c2d5e8000-7f4c2d5e9000 rwxp 00:00 0
I see this in my 2 test systems, one
On 2/13/18 6:29 PM, Felipe Sateler wrote:
> Changelog has this by Marco d'Itri:
>
>> * Do not install sysctl.d/50-default.conf because the systemd package
>>should not change kernel policies, at least until it will become
>>the only supported init system.
Thanks for pointing this out!
Package: systemd
Version: 237-2
Severity: normal
Dear Maintainer,
by default Debian uses the pfifo_fast network queuing algorithm:
# tc -s qdisc show
[...]
qdisc pfifo_fast 0: dev eth0 root refcnt 2 bands 3 priomap 1 2 2 2 1 2 0 0 1 1
1 1 1 1 1 1
Sent 413728102 bytes 475015 pkt (dropped
Package: policykit-1
Version: 0.113-6
Severity: normal
Tags: security
Dear Maintainer,
the polkitd process runs with several memory zones with both write and execute
permissions:
# grep rwxp /proc/$(pidof polkitd)/maps
7f2638828000-7f2638838000 rwxp 00:00 0
7f263884f000-7f263885f000
Package: libopenmpi-dev
Version: 2.1.1-8
Severity: important
Dear Maintainer,
here is the problem:
Setting up libopenmpi-dev (2.1.1-8) ...
update-alternatives: error: alternative link
/usr/lib/x86_64-linux-gnu/libmpi.so is already managed by mpi-x86_64-linux-gnu
dpkg: error processing package
Package: ruby-soap4r
Version: 2.0.5-3
Severity: normal
Dear Maintainer,
here is the problem:
Retrieving bug reports... 0%
/usr/lib/ruby/vendor_ruby/soap/mapping/encodedregistry.rb:150: warning:
constant ::Fixnum is deprecated
/usr/lib/ruby/vendor_ruby/soap/mapping/encodedregistry.rb:216:
Package: libbeansbinding-java-doc
Version: 1.2.1-3
Severity: normal
Dear Maintainer,
after each package installation, I see the following error message:
Processing 1 removed doc-base file, 4 added doc-base files...
Error while merging /usr/share/doc-base/libbeansbinding-java-doc with
Package: ruby-debian
Version: 0.3.9+b7
Severity: normal
Dear Maintainer,
after most package installations, I see the following error messages:
Processing 1 removed doc-base file, 4 added doc-base files...
/usr/lib/ruby/vendor_ruby/debian.rb:223: warning: parentheses after method name
is
Package: libsvnclientadapter-java-doc
Version: 1.10.12-1
Severity: normal
Dear Maintainer,
after each package installation, I see the following error message:
Processing 1 removed doc-base file, 4 added doc-base files...
Error while merging /usr/share/doc-base/libsvnclientadapter-java-doc with
Hi,
this bug is still there:
Package: iipimage-server
Version: 1.0-2
apache2_reload: apache2: Syntax error on line 147 of /etc/apache2/apache2.conf:
Syntax error on line 20 of /etc/apache2/mods-enabled/iipsrv.conf: Expected
but saw
--
Laurent.
Package: python3-pip
Version: 9.0.1-2
Severity: normal
Dear Maintainer,
here is the problem:
$ pip3 list --outdated
DEPRECATION: The default format will switch to columns in the future. You can
use --format=(legacy|columns) (or define a format=(legacy|columns) in your
pip.conf under the
Package: gssproxy
Version: 0.7.0-2
Severity: important
Dear Maintainer,
here is an error message I see on my system during boot:
sept. 11 16:27:48 hostname systemd[1]: gssproxy.service: Found ordering cycle
on gssproxy.service/start
sept. 11 16:27:48 hostname systemd[1]: gssproxy.service:
Hi,
this bug is still there in kernel 4.11.6 :
$ uname -a
Linux irancy.iut2.upmf-grenoble.fr 4.11.0-1-rt-amd64 #1 SMP PREEMPT RT Debian
4.11.6-1 (2017-06-19) x86_64 GNU/Linux
$ dmesg
[...]
[690935.587688] NOHZ: local_softirq_pending 80
When this error occurred the system was accessing a btrfs
Package: sntp
Version: 1:4.2.8p10+dfsg-4
Severity: normal
Dear Maintainer,
here is the problem:
# sntp pool.ntp.org
sntp 4.2.8p10@1.3728-o (1)
kod_init_kod_db(): Cannot open KoD db file /var/db/ntp-kod: No such file or
directory
2017-06-20 11:05:44.073428 (-0100) +0.006359 +/- 0.025993
1 - 100 of 1002 matches
Mail list logo
