Le mercredi 31 mai 2023 à 13:15 +0200, Stefan Eissing a écrit :
> Hi Bastien,
>
> I was finally able to reproduce here what looks like the crashes you
> see with mod_proxy_http2 (notice the careful wording). And I fixed it
> in https://github.com/icing/mod_h2/releases/tag/v2.0.18
>
> Looking forw
on your system.
Hello,
Thanks for your work. I've put it on my system, I'll report any new
crash (last week I got approximately one every 2 days)
Regards,
--
Bastien Durel
Le mercredi 24 mai 2023 à 14:50 +0200, Stefan Eissing a écrit :
> I continue to improve mod_proxy_http2:
> https://github.com/icing/mod_h2/releases/tag/v2.0.17
>
> Added more edge case tests for the module, fixed observed bugs. But
> have not replicated your crashes which look weird. Sorry.
Hello
Le lundi 22 mai 2023 à 16:36 +0200, Stefan Eissing a écrit :
>
>
> > Am 19.05.2023 um 18:50 schrieb Bastien Durel :
> >
> > Le 19/05/2023 à 18:11, Stefan Eissing a écrit :
> > > Hi Bastien,
> > Hello
> >
> > > I am looking into the fail
nk so ... The knot-resolver I forward DOH requests to seems
to only support HTTP/2 ; if I change it to https://, dog fails to
resolve on it :
Error [http]: Nameserver returned HTTP 502 (Proxy Error)
Regards,
--
Bastien Durel
Le jeudi 18 mai 2023 à 15:04 +0200, Bastien Durel a écrit :
> Le 18/05/2023 à 14:41, Stefan Eissing a écrit :
> > Did you have an warning message like "AH03516: unexpected NN
> > streams in hold" at that time in out error log?
>
> No (grepping AH03516 in *.log ret
Le 18/05/2023 à 14:41, Stefan Eissing a écrit :
Did you have an warning message like "AH03516: unexpected NN streams in hold"
at that time in out error log?
No (grepping AH03516 in *.log returns nothing (nor does "streams in hold"))
--
Bastien Durel
happen at any time during request processing
> and
> this makes it hard to reproduce issues in test cases. We have load
> tests
> with well-behaving clients. Tests with mis-behaving ones are the
> tricky part.
>
> It would be helpful if you could try
> https://github.com
Package: apache2
Version: 2.4.56-1~deb11u2
Severity: important
Dear Maintainer,
I see many segmentation faults in apache2, for exemple in the last 24h I got:
Tue 2023-05-16 13:40:59 CEST 7757403333 11 present /usr/sbin/apache2
Tue 2023-05-16 13:52:44 CEST 7983293333 11 presen
Package: openjdk-7-jre
Version: 7u95-2.6.4-1~deb7u1
When I try to upgrade (with aptitude dist-upgrade) from 7u91-2.6.3-
1~deb7u1 to 7u95-2.6.4-1~deb7u1, I got an unmet dependencies message :
The following NEW packages will be installed:
initscripts:i386{ab} sysvinit-utils:i386{ab}
The followin
One way to workaround this bug is to minimize (default shortcup alt+f9,
or alt+space then click minimize) the "somthing went wrong" window.
Works well here.
--
Bastien
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact list
One way to workaround this bug is to minimize (default shortcup alt+f9,
or alt+space then click minimize) the "somthing went wrong" window.
Works well here.
--
Bastien
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact list
Package: evolution
Version: 3.2.2-1
Severity: important
Tags: upstream
Hello,
I have an old, big, calendar in ical, that I used to publish on my webdav
webserver.
Now it crashes evolution with a sigsegv -- see backtrace attached -- even if I
use another method to publish it.
Evo is crashing at s
ds, and effectively resolving name.
- I think returning NOTFOUND when you cannot load the nss library is an error
(UNAVAIL should be better)
- ia32-libs should include libnss_mdns4_minimal.so.2, as mdns_minimal is
configured by default
Thanks,
Bastien Durel
-- System Information:
Debian R
#x27;s guy at
https://bugzilla.kernel.org/show_bug.cgi?id=11998
the "fix" I used was introduction of a "mdix" parameter, which is not
shown on 2.6.32-5-amd64's e1000e modinfo
I'm sorry to cannot test that.
--
Bastien Durel
--
To UNSUBSCRIBE, email to debian-bugs
uf = {{jmp_buf = {-144048140, 0,
4001536, -283712504, -792986709, 747631003}, mask_was_saved = 0}}, priv
= {pad = {0x0,
0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0,
canceltype = 0}}}
not_first_call =
freesize =
__PRETTY_FUNCTION__ = "start_thread"
---
sn connexion is
notified via a jabber transport. (I'll try to set-up another jabber
account with msn transport to test with)
--
Bastien Durel
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Package: pidgin
Version: 2.7.2-1
Severity: important
Tags: squeeze
At start, pidgin emits sounds to signal logins, and crashes immediatly
Here is the gdb backtrace :
(gdb) where
#0 0xf76f8430 in __kernel_vsyscall ()
#1 0xf6c58751 in *__GI_raise (sig=6) at
../nptl/sysdeps/unix/sysv/linux/raise.
rotocol stack */),
although pilot_connect returns without error. (device->type is
PILOT_DEVICE_USB_VISOR)
I can sync under lenny and ubuntu 9.10, but I can't with squeeze or sid.
--
Bastien Durel
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsu
Package: gdb
Version: 6.8-3
Severity: important
gdb incorrectly prints some objects passed to functions as value.
i.e. for a c-string holder, data pointer is displayed as pointing on itself (or
this), although it points to a valid allocated mem zone.
I put a demonstrating program below :
bdu..
As this bug affects ubuntu, I sent report to launchpad as well
https://bugs.launchpad.net/ubuntu/+source/glunarclock/+bug/459389
You can see SIGGEGV in strcmp() (disassembly & stack trace avaiable)
--
Bastien Durel
smime.p7s
Description: S/MIME cryptographic signature
Hello,
I forgot the pid in my proposed patch, so here's the correct version
--
Bastien Durel
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ mt-daapd\[[0-9]+\]: Rescanning database$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ mt-daapd\[[0-9]+\]: Starting playlist scan$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ mt-daap
Package: mt-daapd
Version: 0.9~r1696.dfsg-6lenny2
Severity: minor
Tags: patch
mt-daapd is filling syslog with informations like "Rescanning database" which
may be ignored by logcheck.
It logs even if a logfile is provided
This could be resolved with a logcheck ignore file like this :
^\w{3} [ :0
-2009-0547.patch
Regards,
Bastien Durel
-- System Information:
Debian Release: 5.0.2
APT prefers stable
APT policy: (990, 'stable'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-2-nomdix (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8
Hello,
Sorry for this mistake, I did not see dbndns subfolder, and I was
confused by an old /usr/local install.
You can drop this non-bug.
Regards,
--
Bastien Durel
smime.p7s
Description: S/MIME cryptographic signature
Package: dbndns
Version: 1:1.05-4
Severity: important
dbndns built from source is same as djbdns
diff debian/dbndns/usr/bin/tinydns debian/djbdns/usr/bin/tinydns reports same
files
I found no trace of 0002-Apply-fefe-s-djbdns-1.05-test23-ipv6-patch.diff in the
source package
-- System Informa
libar(.a), which is not shipped in package(s)
[1] libsmdkim-dev should then depends on libmilter-dev ?
--
Bastien Durel
smime.p7s
Description: S/MIME cryptographic signature
Package: libvpim-ruby1.8
Version: 0.15-1
Severity: normal
encode seems to apply "fields" to an array:
/usr/lib/ruby/1.8/vpim/icalendar.rb:246:in `fields': undefined method `fields'
for # (NoMethodError)
from /usr/lib/ruby/1.8/vpim/icalendar.rb:246:in `each'
from /usr/lib/ruby/1.8
Le lundi 05 janvier 2009 à 18:21 +0100, Evgeni Golov a écrit :
> Hi *,
>
> while looking at RC-bugs I stumbled over this one.
> Yupp, the long descriptions only mentions PHP4. But look at the
> changelog, the latest entry says:
> * Added support for php5(-gd), reviewed all example that seems to
Le samedi 08 novembre 2008 à 00:01 +0100, Moritz Muehlenhoff a écrit :
> On Mon, Sep 22, 2008 at 01:44:38PM +0200, Bastien Durel wrote:
> > Le dimanche 21 septembre 2008 à 15:14 +0200, Bastian Blank a écrit :
> > > On Mon, Sep 01, 2008 at 02:22:00PM +0200, Bastien Durel wrote:
Le dimanche 21 septembre 2008 à 15:14 +0200, Bastian Blank a écrit :
> On Mon, Sep 01, 2008 at 02:22:00PM +0200, Bastien Durel wrote:
> > The e1000e kernel module does not initialize correctly, then the network
> > cannot initialize.
>
> Please explain, the attached log
Package: linux-image-2.6.26-1-686
Version: 2.6.26-3
Severity: important
The e1000e kernel module does not initialize correctly, then the network cannot
initialize.
It does not complain, but packets do not exit correctly. The port's LED on
switch blinks quickly all time, IPv6 RA's are recevied by
;, NULL)))
- return;
+ if (!(bus = libhal_device_get_property_string (hal_ctx, udi,
"info.bus", NULL))) {
+ /* Bastien Durel: newer HAL seems to use info.subsystem, not
info.bus */
+ if (!(bus = libhal_device_get
Package: libphp-jpgraph
Version: 1.5.2-11
Severity: important
As stated on jpgraph website, "Note: The 1.x series is only for PHP4. It will
not work on PHP5."
On my etch server, libphp-jpgraph requires downgrade to php4, but on my lenny
laptop, it installed without complaining.
But it doesn't wo
34 matches
Mail list logo
