I ran into this problem too, and I was able to troubleshoot it.
To the best of my understanding, this is caused by:
https://github.com/libvirt/libvirt/commit/64b966558cc6002fe150a0292a24eb2802a792c5#diff-69678f99af3e2f578ab1665eaaf3423314b3aa01a6e0b09a085b049e82b17903R102
case
Package: libapache2-mod-gnutls
Version: 0.9.0-1.1
Severity: important
Dear Maintainer,
I am having a problem starting apache when mod_gnutls is enabled.
[Tue Jun 04 10:24:34.745316 2024] [gnutls:warn] [pid 50831]
mgs_cache_post_config: Configuring default OCSP cache 'shmcb:gnutls_ocsp_cache'
On 2024-02-10 10:06, Debian Bug Tracking System wrote:
#1063215: gp-saml-gui: package depends on openconnect, but openconnect not
strictly necessary
It has been closed by Debian FTP Masters (reply to
Luca Falavigna ).
Thank you for including this.
-Corey
On 2023-08-06 05:33, Salvatore Bonaccorso wrote:
If possible can you verify the issue is still present in either the
newest 6.4.y upstream or mainline (or nearest to that, the
6.5~rc4-1~exp1 in experimental)?
If so can you report the issue upstream and link back here the
upstream report?
Yes,
I reproduced this with linux-image-6.4.0-1-amd64 (after a reboot, of
course).
This time, a full write via direct I/O did not trigger the crash, but a
subsequent write via buffered I/O did result in a crash.
-Corey
Package: src:linux
Version: 6.3.11-1
Severity: normal
Dear Maintainer,
I was testing RAID-5 write-back journal (AKA cache) for the first time.
https://docs.kernel.org/driver-api/md/raid5-cache.html
I experienced a NULL pointer dereference early in the process.
steps
On 2022-06-13 22:45, Michael Tokarev wrote:
Is it sufficient to use
dpkg-statoverride --add root root 04755 /usr/lib/qemu/qemu-bridge-helper
to fix this on a particular system?
I tested this and found:
1. This does persist across a reinstallation of qemu-system-common.
2. This does not
The original rationale is stated here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691138#10
...with a specific complaint:
> For example, initially the helper always created interfaces in the
> form tapNN (picking up next free number). This way, it weren't
> possible to know which iface
I ran into this issue too. I think that, in principle, daemons should
not be able to write to their own configuration files, so making the
files owned by root is a good thing anyway. The only real trouble is
that things break on upgrade due to the earlier default ownership.
One other related
.1.1c-1
ii lsb-base 10.2019051400
hostapd recommends no packages.
hostapd suggests no packages.
-- Configuration Files:
/etc/default/hostapd changed [not included]
-- no debconf information
commit 45107409549fc3b48f882dd85bc35e354d196038
Author: Corey Hickey
Date: Thu 2019-09-2
On 29/04/2019 06.21, Otto Kekäläinen wrote:
Apparently the comment in your Github PR was wrong then in
https://github.com/MariaDB/mariadb-connector-c/pull/101#issuecomment-466809308
I asked also you where the commit is in the MR at
Package: packer
Version: 1.3.4+dfsg-4
Severity: wishlist
Dear Maintainer,
Thank you for packaging packer. Can you please update the Debian package
for the upstream 1.4.0 release?
https://www.hashicorp.com/blog/announcing-packer-v-1-4-0
Thank you,
Corey
This seems to be due to:
# su debian-security-support --shell /bin/bash --command 'check-support-status
--type ended --no-heading --status-db
"/var/lib/debian-security-support/security-support.semaphore"'
Unknown DEBIAN_VERSION 10. Valid values from 7 and 9
# cat /etc/debian_version
10.0
I
Package: squid-deb-proxy
Version: 0.8.14
Severity: normal
Dear Maintainer,
I have encountered a problem with caching using squid-deb-proxy. This
may be a bug in squid itself, but I am not familiar enough with squid
to determine that.
The symptom of the problem is:
I filed a bug against mariadb-client-core-10.1 for this:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904223
I don't know if there is anything that can be done for
libdbd-mysql-perl, since the problem seems to be in the underlying
mariadb library.
-Corey
The problem in more detail is that when the server hostname is listed as
a SubjectAltName ("SAN") in the certificate, then validation fails.
Validation only succeeds if the server hostname is in the CN of the
certificate.
This seems likely to be a bug in the underlying mariadb library. I was
Package: libdbd-mysql-perl
Version: 4.046-1
Severity: normal
Dear Maintainer,
Upon upgrade from 4.041-2+b1 to 4.046-1, I can no longer connect to our
mysql database with SSL. Reverting to 4.041-2+b1 makes the connection
work again.
Here is a test script to reproduce (with database name and
Hi,
I ran into this change and found it disconcerting overall. Since it's an
upstream change, I don't necessarily expect it to be fixed here, but
I'll report some of what I learned in the hope that it may be generally
useful.
There's a detailed description here:
I've been having this problem a while, and I ran across this bug report.
Ondřej Surý's suggestion of 'ip-transparent: yes' did work for me. This
is a sufficient workaround for me, but I investigated further in the hope
that it is useful.
Peter Palfrader's suggestion of
On 2015-08-09 02:43, Muammar El Khatib wrote:
I have prepared an upload¹, I am waiting it passes the NEW process.
Hopefully in a couple of weeks it should be done. If it does not pass,
I will upload a revision of 0.7.6.
Regards,
1.
Hi,
This package is apparently not installable on sid now.
1. libcegui-mk2-0.7.6 requires libogre-1.8.0
2. libstdc++6 Breaks libogre-1.8.0 = 1.8.0+dfsg1-7+b1
Updating libogre-1.8.0 is apparently a wontfix:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791222
Can you please prepare a new
I noticed this a while back too, and got annoyed enough to research it.
Apparently that behavior is called Client Side Decorations, or CSD,
and gnome and/or GTK apps have been switching to it recently.
Personally, I don't like it at all--it breaks the functionality of a
window manager. Even
Package: ipmitool
Version: 1.8.14-4
Severity: normal
Hi,
On my desktop, I use ipmitool purely as a client for accessing servers I
manage. The ipmitool package includes ipmievd, which seems to be
disabled by default, but there are still some kernel modules that get
loaded.
$ cat
On 2014-10-08 01:23, Aníbal Monsalve Salazar wrote:
do you still see this? (curl has since switched to gnutls28) And if
you still see the problem could you check whether building mod_gnutls
against libgnutls28-dev from experimental (which has corrected symbol
versioning) fixes the issue for
I agree. At the least, the group ownership should be libvirt-qemu and
the mode 775.
For anyone wondering why this matters, it prevents a startup failure
when using a qemu guest agent as documented here:
http://wiki.libvirt.org/page/Qemu_guest_agent
Package: libapache2-mod-gnutls
Version: 0.5.10-1.1
Severity: important
Dear Maintainer,
I just did an apt-get upgrade and ran into a problem that prevents
apache from starting:
apache2: Syntax error on line 140 of /etc/apache2/apache2.conf: Syntax
error on line 1 of
Hmm, I ran into this bug too. It can apparently be worked around by
adding -C 3 to the arguments.
http://lists.fedoraproject.org/pipermail/package-announce/2012-November/093545.html
https://bugzilla.redhat.com/show_bug.cgi?id=877219
-Corey
--
To UNSUBSCRIBE, email to
On 2012-12-29 09:08, Martin Naughton wrote:
Hello Corey,
Do you have the file that is produced missing the line?
You say both files below are missing the line. When you do the work around
does it write this missing line to the files below?
/etc/default/grub
/boot/grub/grub.cfg
Package: libcrypt-cbc-perl
Version: 2.31-1
Severity: important
Tags: upstream
Dear Maintainer,
2.31 seems to have introduced a bug that makes data always appear
tainted:
$ /tmp/t.pl
Taint checks are turned on and your key is tainted. Please untaint the
key and try again at /tmp/t.pl line 11
On 2012-05-31 00:09, Alexander Golovko wrote:
As for the problem with the patch in the URL I originally sent, the
issue is that mysql considers columns to be identifiers, and the
way
to quote an identifier is to use backticks.
wrong: select MaxValue from Counters;
right: select `MaxValue
On 2012-05-29 07:28, Alexander Golovko wrote:
Hi!
Thank you for bugreport!
Can you say, what is wrong with upstream patch (bug 5104 in upstream
bugtracker)?
Assuming you mean bug 1504, that patch is incomplete--it fixes table
creation, but not access.
As for the problem with the patch in
Package: bacula-director-mysql
Version: 5.0.3+dfsg-0.1
Severity: important
Tags: patch
Hi,
I've been getting some errors from bacula like:
You have an error in your SQL syntax; check the manual that corresponds
to your MySQL server version for the right syntax to use near
I tested the patch wrong; attached is a better patch.
-Corey
diff -Naur bacula-5.0.3+dfsg.orig/src/cats/make_mysql_tables.in
bacula-5.0.3+dfsg/src/cats/make_mysql_tables.in
--- bacula-5.0.3+dfsg.orig/src/cats/make_mysql_tables.in2010-08-05
07:29:51.0 -0700
+++
Seems to be this bug:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669883
https://bugzilla.gnome.org/show_bug.cgi?id=673749
I got my setup working again with libgtk-3-0, libgtk-3-common, and
gir1.2-gtk-3.0 packages from here:
http://snapshot.debian.org/package/gtk%2B3.0/3.2.3-1/
-Corey
Wow, this bug drove me nuts when I was doing some unrelated reboots
yesterday.
That whole function seems kind of strange to me (making a directory to
pass state from one part of the function to another...?).
Here's a patch that makes the function seem cleaner to me, if anybody
wants it.
-Corey
Thankyouthankyouthankyou for this bug fix--it has been vexing me for
several weeks and I finally got a bug report ready only to find this one
instead!
I tried the patch on the version of xserver-xorg-core currently in sid,
and it fixes the problem perfectly.
-Corey
--
To UNSUBSCRIBE, email
Package: nsd3
Version: 3.2.7-1
Severity: wishlist
Tags: patch
Hi,
I'm not yet too familiar with nsd, but it seems to me that the most
common task for an administrator is to update a zone file and then apply
those changes.
The attached patch uses '/etc/init.d/nsd3 reload' to do the following:
*
Package: dkimproxy
Version: 1.2-6
Severity: minor
Tags: patch
Hi,
I seem to have introduced a typo in my patch for bug #493816. The
attached patch fixes that typo.
Thanks,
Corey
-- System Information:
Debian Release: 5.0.8
APT prefers stable
APT policy: (990, 'stable'), (500, 'testing')
Package: dkimproxy
Version: 1.2-6
Severity: normal
Tags: patch
Hi,
I'm setting up dkimproxy on a fresh system, and it didn't have an
fqdn set in /etc/hosts. The current init script for dkimproxy fails
in that situation.
Here's a small patch to fall back on 'localdomain' and print a
warning.
Package: bacula-fd
Version: 5.0.2-2.2+b1
Severity: normal
Tags: patch
Hi,
If I run /etc/init.d/bacula-fd start, and bacula-fd is already
running, then the init script fails and exits with status 1. This
caused me some trouble today when I had to reboot during an apt-get
upgrade (for unrelated
Package: grub-pc
Version: 1.96+20090808-1
Severity: normal
Hello,
I like the transition from grub-legacy to grub2 so far, except for one
detail that I have been unable to troubleshoot yet. When I install the
grub-pc package, I get prompted:
The following Linux command line was extracted from
notforwarded 514073
tags 514073 - fixed-upstream
thanks
Hello,
I'm trying to figure out what's happening with an iptraf bug I reported
(and patched) back in 2009-02-03. As far as I can tell, the bug hasn't
received any attention and remains unfixed. The Debian package remains
at 3.0.0-6 and the
On Thu, March 5, 2009 8:43 pm, aelmahmo...@users.sourceforge.net wrote:
On Sat, Feb 21, 2009 at 04:56:46PM -0800, Corey Hickey wrote:
Ok, here's the patch. Feel free to tweak it as you see fit.
I'm at my mom's house right now, so I hooked up the land line, dialed,
and
gave the patch
On Wed, February 18, 2009 10:31 pm, Corey Hickey wrote:
Additionally, I can write a patch that checks the current limit and
makes slmodemd warn or die if the limit is judged to be too low. I'm
mildly in favor of that approach rather than having slmodemd modify the
limit itself.
Ok, here's
أحمد المحمودي wrote:
It sounds reasonable. As you see, I have asked Ian to comment on this.
In the meantime I see that wether we leave it unlimited or if we limit
it to say 16 MB, there is the issue that a user who may want to run
slmodemd manually (like Corey does), so we can do
أحمد المحمودي wrote:
Yet I have been asking myself since yesterday, why does it happen with
Corey, yet not with me nor Mau ?! That problem does not seem to be
device specific problem, does it ?
I would guess that your locked memory limit is either high or unlimited.
See 'ulimit -l' or
أحمد المحمودي wrote:
On Tue, Feb 17, 2009 at 03:15:03AM -0800, Corey Hickey wrote:
I would guess that your locked memory limit is either high or unlimited.
See 'ulimit -l' or 'ulimit -a'.
---end quoted text---
I just found out that /etc/init.d/sl-modem-daemon got this:
ulimit -Hl
Maurizio Avogadro wrote:
Il 16/02/2009 00:40, Corey Hickey ha scritto:
Ok, here's the problem.
modem_main.c:976 function modem_main()
--
if (need_realtime) {
struct sched_param prm
Maurizio Avogadro wrote:
Il 13/02/2009 00:14, Corey Hickey ha scritto:
There aren't any flags on the open() system call; O_CREAT would be
needed.
The data file is actually created on the first write:
modem/modem_datafile.c:110, function datafile_save_info
Corey Hickey wrote:
I don't know why the malloc() fails. I went to the same line in my
slmodemd binary that doesn't have 10_drop_privileges.diff, and that
malloc() succeeded, with the same arguments.
Going back to the regular privilege-dropping binary, I used gdb to run
some malloc() tests
Corey Hickey wrote:
I just tried the Debian 2.6.26-1-686 kernel, and the slmodemd process
was killable, but the modem didn't work: it kept responding NO CARRIER
immediately after dialing.
[cut]
I'm going to try to figure out what it is in my particular kernel
configuration that's causing
أحمد المحمودي wrote:
- Forwarded message from Maurizio Avogadro mav...@gmail.com -
sorry for my late but I'm very busy... after the first glance:
1. I noticed that some previous version left a
- ---Sr--r-T root root data.(slamr|modem:)[0-9]
file in /var/lib/slmodem: maybe the
I just tried the Debian 2.6.26-1-686 kernel, and the slmodemd process
was killable, but the modem didn't work: it kept responding NO CARRIER
immediately after dialing.
In case it's of any use, I'm attaching a couple log files:
slmodemd_2.6.26-1-686.log
slmodemd_2.6.26-1-686_no-drop-privs.log
Package: iptraf
Version: 3.0.0-6
Severity: normal
Tags: patch
Hello,
This bug has been bugging me for a while and I finally chased it down.
I'd send a report upstream, but the original source won't compile for
me, so I can only test the Debian-patched version.
According to the HTML docs,
On Sun, January 18, 2009 11:31 am, aelmahmo...@users.sourceforge.net wrote:
On Sat, Jan 17, 2009 at 01:07:48PM -0800, Corey Hickey wrote:
The process being unkillable is rather worrisome to me, and makes me
wonder if the privilege dropping is actually exposing a kernel bug. What
kernel version
On Sat, January 17, 2009 2:53 am, Ø£ØÙ
د اÙÙ
ØÙ
Ùد٠wrote:
Hello,
I cannot reproduce the same problem that you have encountered. I have
a question though. Does that problem happen in older versions of
sl-modem package (2.9.9d+e-pre2-10 or later) ?
I got the source for
Package: sl-modem-daemon
Version: 2.9.11~20080817-1
Severity: important
Hello,
slmodemd from the Debian package doesn't work for me, and I can't seem to kill
the process, even with kill -9. When I compile version 2.9.11 from upstream,
it works fine. I tracked the problem down to a particular
Thanks for the update. For some reason I didn't get the message relayed
from bugs.debian.org, or I would have replied earlier.
I'm glad the patch is helpful. Let me know if you have any related
questions or requests.
-Corey
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
Package: dkimproxy
Version: 1.0.1-6
Severity: normal
Tags: patch
Hello,
I have made several improvements to /etc/init.d/dkimproxy. Many of the problems
I found are interrelated, so please forgive me for not sending individual
patches. I've tested the patch on my system, and so far it seems to
Thomas Goirand wrote:
Your patch is good, however, your configuration file has everything
disabled by default. I do NOT want to do things this way, I think it
should be set to be run with all the full options as much as possible.
So why did you comment out all things in it? Is there any
For what it's worth, a slightly ugly workaround is to comment out the
relay line in /etc/dkimproxy/dkimproxy_in.conf; this makes the inbound
dkimproxy fail to start.
I don't like that much, though, and a file in /etc/default would be nice.
-Corey
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
Package: singularity
Version: 0.27-1
Severity: minor
Tags: patch
Hello,
This patch corrects a few small grammatical errors in the English text.
Thanks,
Corey
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Package: singularity
Version: 0.27-1
Severity: minor
Tags: patch
Hello,
This patch fixes a few small grammatical errors.
Thanks,
Corey
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Debian Bug Tracking System wrote:
Thank you for filing a new Bug report with Debian.
Dang! Sorry for the dupe report. I didn't realize the first message had
made it to the queue before I sent the second. Feel free to disregard
either #477256 or #477257.
Thanks,
Corey
--
To UNSUBSCRIBE,
Package: cron
Version: 3.0pl1-103
Severity: normal
Tags: patch
Cron keeps mailing me:
/etc/cron.daily/standard:
df: no file systems processed
The offending line is:
df -P --type=ext2 --type=ext3 --type=xfs
I don't have any mounted filesystems of those types, so df errors out.
The attached
Package: amavisd-new-milter
Version: 1:2.4.2-6.1
Followup-For: Bug #47
This bug is not amd64-specific -- the build script mistakenly configures
the helper programs with the wrong socket location. The first hunk of
the attached patch corrects this. The second hunk is ancillary: it makes
Package: nvclock
Version: 0.8b-1
Severity: wishlist
Hi. Thanks for packaging nvidia stuff. There's a new version of nvclock
available at:
http://www.linuxhardware.org/nvclock/
The new version builds and runs just fine for me.
-Corey
-- System Information:
Debian Release: testing/unstable
APT
Andreas, thanks for posting your patch. Based on the information in your
bugreport I was able to make a new patch for 39.1+cvs20050929-1.
With the attached patch, scorched3d compiles with gcc 4.0.2-4 on
Debian-amd64 sid. I haven't tested it heavily, but a few bots are now
craters. :)
-Corey
diff
Package: java-package
Version: 0.25
Severity: normal
Tags: patch
These two patches add support for Blackdown Java 1.4.2-02. I've tested
this on amd64 but the i386 support should work fine.
Note:
I don't know what the right method is for finding
j2se_expected_min_size. I tested using a couple
I thought reportbug was going to prompt me for multiple patches. Here's
the j2sdk one.
-Corey
--- blackdown-j2sdk.sh.orig 2005-07-10 11:05:03.0 -0700
+++ blackdown-j2sdk.sh 2005-08-28 12:59:10.0 -0700
@@ -50,6 +50,11 @@
j2se_expected_min_size=88 # 90316 kB
Helge Kreutzmann wrote:
Hello,
as you might have noticed, a very similar bug was opened 6 years ago
(bug number one order of magnitude lower than current). Unfortunately
I don't have access to an testing/unstable alpha right now.
I was wondering if this might fix that, but I don't know
Package: bb
Version: 1.3rc1-5
Severity: grave
Tags: patch
Justification: renders package unusable
bb segfaults on amd64 after playing for several minutes. The attached
patch (a fix by Lennart Sorensen) fixes the bug. I've also tested the
patch on an i386 system just to be safe.
-- System
72 matches
Mail list logo
