Bug#1069301: Bug reported upstream
Over the weekend I reported the issue to the linux-bluetooth mailing list, which led to bisecting the issue down to a single commit: https://lore.kernel.org/linux-bluetooth/CADRbXaDqx6S+7tzdDPPEpRu9eDLrHQkqoWTTGfKJSRxY=ht...@mail.gmail.com/ Jeremy
Bug#1069301: linux-image-6.1.0-20-amd64: bluetooth causes kernel BUG - list_del corruption, (address)->prev is LIST_POISON2
Hi Salvatore, I've finished bisecting and the version that seems to introduce the breakage is 6.1.83. I tested the following upstream kernels: - linux 6.1.80 => OK - linux 6.1.82 => OK - linux 6.1.83 => BUG - linux 6.1.85 => BUG - linux 6.1.87 => BUG I looks like 6.1.83 introduced quite a few bluetooth changes, so I don't know which one caused the breakage: https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.1.83 What else can I do to assist? Cheers, Jeremy
Bug#1069301: linux-image-6.1.0-20-amd64: bluetooth causes kernel BUG - list_del corruption, (address)->prev is LIST_POISON2
Hi Salvatore, It had been a while (like 10+ years) since I built a kernel from source, so this guide was very welcome, and the "make bindeb-pkg" target is great: https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#s-kernel-org-package It looks like the problem is present in the upstream kernel, I have so far reproduced it with: - linux 6.1.85 - linux 6.1.87 I'll start building previous patch releases until I find one that works, but it's slow going! Cheers, Jeremy
Bug#1069301: linux-image-6.1.0-20-amd64: bluetooth causes kernel BUG - list_del corruption, (address)->prev is LIST_POISON2
Package: src:linux Version: 6.1.85-1 Severity: important X-Debbugs-Cc: jeremy.la...@m4x.org Dear Maintainer, After upgrading from linux-image-6.1.0-18-amd64 to linux-image-6.1.0-20-amd64, bluetooth no longer works and a kernel BUG is visible in dmesg hinting at a memory safety issue. It is not necessary to attempt to connect to any specific bluetooth device to trigger the problem, the problem arises as soon as the system boots. I cannot reproduce the problem when booting back into the previous kernel image. -- Package-specific info: ** Version: Linux version 6.1.0-20-amd64 (debian-ker...@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC Debian 6.1.85-1 (2024-04-11) ** Command line: BOOT_IMAGE=/vmlinuz-6.1.0-20-amd64 root=/dev/mapper/yuzu--vg-root ro quiet ** Tainted: D (128) * kernel died recently, i.e. there was an OOPS or BUG ** Kernel log: [ 19.489647] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 19.497033] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 19.497276] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 19.719465] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 19.739192] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 19.739699] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 19.740149] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 19.740166] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 20.037515] wlp0s20f3: authenticate with 3e:94:ed:ae:f8:23 [ 20.037540] wlp0s20f3: 80 MHz not supported, disabling VHT [ 20.044248] wlp0s20f3: send auth to 3e:94:ed:ae:f8:23 (try 1/3) [ 20.077295] wlp0s20f3: authenticated [ 20.080607] wlp0s20f3: associate with 3e:94:ed:ae:f8:23 (try 1/3) [ 20.184598] wlp0s20f3: associate with 3e:94:ed:ae:f8:23 (try 2/3) [ 20.199647] wlp0s20f3: RX AssocResp from 3e:94:ed:ae:f8:23 (capab=0x1431 status=0 aid=3) [ 20.220862] wlp0s20f3: associated [ 20.361778] IPv6: ADDRCONF(NETDEV_CHANGE): wlp0s20f3: link becomes ready [ 20.424603] Bluetooth: hci0: command 0x0408 tx timeout [ 20.424648] Bluetooth: hci0: Opcode 0x0408 failed: -110 [ 20.474223] kauditd_printk_skb: 24 callbacks suppressed [ 20.474230] audit: type=1400 audit(1713540473.670:38): apparmor="DENIED" operation="open" profile="mariadbd_akonadi" name="/sys/devices/system/node/" pid=2378 comm="mysqld" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [ 20.545041] audit: type=1400 audit(1713540473.742:39): apparmor="DENIED" operation="open" profile="mariadbd_akonadi" name="/sys/devices/system/node/" pid=2453 comm="mysqld" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [ 20.602910] audit: type=1400 audit(1713540473.798:40): apparmor="DENIED" operation="open" profile="mariadbd_akonadi" name="/sys/block/" pid=2453 comm="mysqld" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [ 20.637180] audit: type=1400 audit(1713540473.834:41): apparmor="DENIED" operation="open" profile="mariadbd_akonadi" name="/sys/devices/virtual/block/dm-1/queue/physical_block_size" pid=2453 comm="mysqld" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [ 22.500681] Bluetooth: hci0: command 0x0408 tx timeout [ 22.500728] Bluetooth: hci0: Opcode 0x0408 failed: -110 [ 22.660771] Bluetooth: hci0: Opcode 0x0408 failed: -114 [ 22.660847] list_del corruption, 94d9f6302000->prev is LIST_POISON2 (dead0122) [ 22.660887] [ cut here ] [ 22.660890] kernel BUG at lib/list_debug.c:56! [ 22.660907] invalid opcode: [#1] PREEMPT SMP NOPTI [ 22.660917] CPU: 10 PID: 139 Comm: kworker/u25:0 Not tainted 6.1.0-20-amd64 #1 Debian 6.1.85-1 [ 22.660929] Hardware name: Dell Inc. XPS 9315/00KRKP, BIOS 1.19.1 03/14/2024 [ 22.660936] Workqueue: hci0 hci_cmd_sync_work [bluetooth] [ 22.661128] RIP: 0010:__list_del_entry_valid.cold+0x4b/0x6f [ 22.661147] Code: fe ff 0f 0b 48 89 f2 48 89 fe 48 c7 c7 48 18 7a 9f e8 14 a1 fe ff 0f 0b 48 89 fe 48 89 ca 48 c7 c7 10 18 7a 9f e8 00 a1 fe ff <0f> 0b 48 89 fe 48 c7 c7 d8 17 7a 9f e8 ef a0 fe ff 0f 0b 48 89 fe [ 22.661156] RSP: :ae0e406efde0 EFLAGS: 00010246 [ 22.661164] RAX: 004e RBX: 94d9f6302000 RCX: 0027 [ 22.661172] RDX: RSI: 0001 RDI: 94dfaf8a03a0 [ 22.661177] RBP: 94d859392000 R08: R09: ae0e406efc78 [ 22.661182] R10: 0003 R11: 9fed4448 R12: 94d859392000 [ 22.661187] R13: 94d859392770 R14: 94d858cb9800 R15: dead0100 [ 22.661194] FS: () GS:94dfaf88() knlGS: [ 22.661202] CS: 0010 DS: ES: CR0: 80050033 [ 22.661208] CR2: 7f423c024038
Bug#959606: Headless inkscape
The -z option for inkscape used to allow running inkscape in a headless mode, but it seems to have been removed. I'm not sure what the equivalent is now to be able to render SVG to raster formats using inkscape.. Jeremy
Bug#907150: Thanks for the patch!
Thanks for the patch I will prepare an upload. Cheers, Jeremy
Bug#884887: closed by Michael Gilbert <mgilb...@debian.org> (re: chromium: rejects access to microphone without prompt)
You cannot be serious about this being the intended behavior! The current behavior is unacceptable, how are users supposed to guess why access to their microphone fails, and how are they supposed to re-enable it? "You have to switch to root and edit a file which gets overwritten on each update" is not a valid answer. More fundamentally, why did you actively break a feature of the browser? If you are going to cripple chromium, at the very least own up to it by explicitly documenting it + the rationale behind it. Jeremy On 28 Jan 2018 03:45, "Debian Bug Tracking System" <ow...@bugs.debian.org> wrote: > This is an automatic notification regarding your Bug report > which was filed against the chromium package: > > #884887: chromium: rejects access to microphone without prompt > > It has been closed by Michael Gilbert <mgilb...@debian.org>. > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact Michael Gilbert < > mgilb...@debian.org> by > replying to this email. > > > -- > 884887: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884887 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems > > > -- Forwarded message -- > From: Michael Gilbert <mgilb...@debian.org> > To: 884887-cl...@bugs.debian.org > Cc: > Bcc: > Date: Sat, 27 Jan 2018 21:43:16 -0500 > Subject: re: chromium: rejects access to microphone without prompt > This is the intended default. > > Best wishes, > Mike > > -- Forwarded message -- > From: "Jeremy Lainé" <jeremy.la...@m4x.org> > To: sub...@bugs.debian.org > Cc: > Bcc: > Date: Thu, 21 Dec 2017 01:27:02 +0100 > Subject: chromium: rejects access to microphone without prompt > Package: chromium > Version: 63.0.3239.84-1 > Severity: normal > > When trying to make use of any website which uses getUserMedia(), > including the reference WebRTC app, the request fails with a > NotAllowedError without prompting me at all. The expected behaviour is > for the usual prompt to appear, asking for access to the microphone. > > I have checked that the "Block" and "Allow" lists in content settings > are both empty and the default action is "Ask before accessing". > Furthermore, manually adding websites to the "Allow" list makes no > difference, I still get the crossed out microphone icon to the right of > the URL bar indicating access to the microphone was denied. > > This really seems to be a UX issue and not a problem accessing the > underlying hardware, as everything works fine if I start Chromium with > the –use-fake-ui-for-media-stream flag. > > I have also tried the Google-provided .deb for Chrome (also M63) on the > same machine everything works out of the box, so it really looks like > this issue is specific to the Debian/Chromium build. > > Let me know if there are any further tests I can perform to narrow down > the root cause of the issue. > > > -- System Information: > Debian Release: buster/sid > APT prefers unstable > APT policy: (500, 'unstable'), (500, 'testing') > Architecture: amd64 (x86_64) > > Kernel: Linux 4.14.0-1-amd64 (SMP w/4 CPU cores) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), > LANGUAGE=en_US:en (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages chromium depends on: > ii chromium-common 63.0.3239.84-1 > ii libasound2 1.1.3-5 > ii libatk1.0-0 2.26.1-1 > ii libavcodec57 7:3.4.1-1 > ii libavformat577:3.4.1-1 > ii libavutil55 7:3.4.1-1 > ii libc62.25-5 > ii libcairo21.15.8-2 > ii libcups2 2.2.6-3 > ii libdbus-1-3 1.12.2-1 > ii libevent-2.1-6 2.1.8-stable-4 > ii libexpat12.2.5-3 > ii libflac8 1.3.2-1 > ii libfontconfig1 2.12.6-0.1 > ii libfreetype6 2.8.1-0.1 > ii libgcc1 1:7.2.0-18 > ii libgdk-pixbuf2.0-0 2.36.11-1 > ii libglib2.0-0 2.54.2-3 > ii libgtk-3-0 3.22.26-2 > ii libharfbuzz0b1.7.2-1 > ii libicu57 57.1-8 > ii libjpeg62-turbo 1:1.5.2-2+b1 > ii liblcms2-2 2.9-1 > ii libminizip1 1.1-8+b1 > ii libnspr4 2:4.16-1+b1 > ii libnss3 2:3.34-1 > ii libopus0 1.2.1-1 > ii libpango-1.0-0 1.40.13-2 > ii libpangocairo-1.0-0 1.40.13-2 > ii libpng16-16 1.6.34-1 > ii libpulse0
Bug#885989: Downgrade the severity of this bug, or close it
TLS guarantees you have established a secure connection to the host name you requested, nothing else. If a host name resolves to cloudflare's servers, that's the domain owner's decision. Almost every production deployment involves reverse proxies at one point or another (terminating TLS in the application server is exceedingly rare), so "end to end encryption" is definitely not the promise. Suggested that detecting certain headers to flag "man in the middle attacks" is not a serious claim either. This bug report should be closed as wontfix, and should not hold up a transition from unstable to testing. Jeremy
Bug#884887: Jochen's fix works for me
I can confirm that the change suggested by Jochen works, so the root cause is well understood. One caveat : in my case the master preferences had trickled down into my own preferences in $HOME/.config/chromium/Default/Preferences so that I also had to remove the hardware.audio_capture_enabled entry there for the change to work. As a result, users will probably remain affected by this issue even once the master preferences have been fixed. Jeremy
Bug#884887: chromium: rejects access to microphone without prompt
Package: chromium Version: 63.0.3239.84-1 Severity: normal When trying to make use of any website which uses getUserMedia(), including the reference WebRTC app, the request fails with a NotAllowedError without prompting me at all. The expected behaviour is for the usual prompt to appear, asking for access to the microphone. I have checked that the "Block" and "Allow" lists in content settings are both empty and the default action is "Ask before accessing". Furthermore, manually adding websites to the "Allow" list makes no difference, I still get the crossed out microphone icon to the right of the URL bar indicating access to the microphone was denied. This really seems to be a UX issue and not a problem accessing the underlying hardware, as everything works fine if I start Chromium with the –use-fake-ui-for-media-stream flag. I have also tried the Google-provided .deb for Chrome (also M63) on the same machine everything works out of the box, so it really looks like this issue is specific to the Debian/Chromium build. Let me know if there are any further tests I can perform to narrow down the root cause of the issue. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages chromium depends on: ii chromium-common 63.0.3239.84-1 ii libasound2 1.1.3-5 ii libatk1.0-0 2.26.1-1 ii libavcodec57 7:3.4.1-1 ii libavformat57 7:3.4.1-1 ii libavutil55 7:3.4.1-1 ii libc6 2.25-5 ii libcairo2 1.15.8-2 ii libcups2 2.2.6-3 ii libdbus-1-3 1.12.2-1 ii libevent-2.1-6 2.1.8-stable-4 ii libexpat1 2.2.5-3 ii libflac8 1.3.2-1 ii libfontconfig1 2.12.6-0.1 ii libfreetype6 2.8.1-0.1 ii libgcc1 1:7.2.0-18 ii libgdk-pixbuf2.0-0 2.36.11-1 ii libglib2.0-0 2.54.2-3 ii libgtk-3-0 3.22.26-2 ii libharfbuzz0b 1.7.2-1 ii libicu57 57.1-8 ii libjpeg62-turbo 1:1.5.2-2+b1 ii liblcms2-2 2.9-1 ii libminizip1 1.1-8+b1 ii libnspr4 2:4.16-1+b1 ii libnss3 2:3.34-1 ii libopus0 1.2.1-1 ii libpango-1.0-0 1.40.13-2 ii libpangocairo-1.0-0 1.40.13-2 ii libpng16-16 1.6.34-1 ii libpulse0 11.1-4 ii libre2-3 20170101+dfsg-1 ii libsnappy1v5 1.1.7-1 ii libstdc++6 7.2.0-18 ii libvpx4 1.6.1-3 ii libwebp6 0.6.0-4 ii libwebpdemux2 0.6.0-4 ii libwebpmux3 0.6.0-4 ii libx11-6 2:1.6.4-3 ii libx11-xcb1 2:1.6.4-3 ii libxcb1 1.12-1 ii libxcomposite1 1:0.4.4-2 ii libxcursor1 1:1.1.15-1 ii libxdamage1 1:1.1.4-3 ii libxext6 2:1.3.3-1+b2 ii libxfixes3 1:5.0.3-1 ii libxi6 2:1.7.9-1 ii libxml2 2.9.4+dfsg1-5.2 ii libxrandr2 2:1.5.1-1 ii libxrender1 1:0.9.10-1 ii libxslt1.1 1.1.29-5 ii libxss1 1:1.2.2-1+b2 ii libxtst6 2:1.2.3-1 ii zlib1g 1:1.2.8.dfsg-5 Versions of packages chromium recommends: ii fonts-liberation 1:1.07.4-5 Versions of packages chromium suggests: pn chromium-driver pn chromium-l10n pn chromium-shell pn chromium-widevine -- no debconf information
Bug#836611: Possibly related issue
I am having the same problem, and the symptoms match pretty well with this: https://bugzilla.redhat.com/show_bug.cgi?id=1361157
Bug#760919: RFA: ocfs2-tools -- tools for managing OCFS2 cluster filesystems
I think you should go ahead and take over maintainership, thank you very much for stepping up Valentin! Cheers, Jeremy
Bug#807902: konsole: segfault on exit
On 12/24/2015 01:40 AM, Lisandro Damián Nicanor Pérez Meyer wrote: > > Please update qt to the current version in unstable (5.5.1+dfsg-10) > and try again > Updating Qt fixed the problem for me, but I'll let the original submitter reply. Cheers, Jeremy
Bug#808840: sddm vs keyboard configuration
There has to be something specific about your setup, because the default configuration of SDDM correctly picks up my french keyboard. Jeremy
Bug#795197: kde-l10n-de: Incorrect translation
Hi Mark, Thanks for spotting this. What would the correct wording be? Thanks, Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794838: Does not sound like a KDE bug
This is just an effect of the ongoing gcc5 transition, all packages should get an automatic rebuild. Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770659: The cause seems to be access to /dev/urandom
Hello,
I have finally managed to get chromium to work with the a patched
version of libsrtp!
The trick is to use fopen(3) to open /dev/urandom instead of open(2) in
libsrtp. Chromium's sandbox allows fopen(3) to be called on /dev/urandom
for NSS's random number generator to work. If we use the same mechanism
for libsrtp, we also get a working random number generator.
The call to setvbuf(3) is used to operate in unbuffered mode, otherwise
calls
to fread(3) will return more data than wanted, unnecessarily draining the
entropy pool, see: https://bugzilla.mozilla.org/show_bug.cgi?id=927230
The same patch works both with libsrtp 1.4.5 (stable, testing, unstable)
and 1.5.2 (experimental).
Cheers,
Jeremy
Description: Use fopen(3) instead of open(2) to escape Chromium sandbox
The Chromium sandboxing mechanisms prevent direct access to the file system,
including /dev/urandom which is used by the random number generator. However,
it allows fopen(3) to be called on /dev/urandom for NSS's random number
generator to work. We therefore use the same mechanism for libsrtp.
The call to setvbuf(3) is used to operate in unbuffered mode, otherwise calls
to fread(3) will return more data than wanted, unnecessarily draining the
entropy pool, see: https://bugzilla.mozilla.org/show_bug.cgi?id=927230
Author: Jeremy Lainé jeremy.la...@m4x.org
Bug-Debian: http://bugs.debian.org/770659
Last-Update: 2015-07-30
diff --git a/crypto/rng/rand_source.c b/crypto/rng/rand_source.c
index 1eb6fbb..0174ce0 100644
--- a/crypto/rng/rand_source.c
+++ b/crypto/rng/rand_source.c
@@ -45,8 +45,7 @@
#include config.h
#ifdef DEV_URANDOM
-# include fcntl.h /* for open() */
-# include unistd.h /* for close() */
+# include stdio.h
#elif defined(HAVE_RAND_S)
# define _CRT_RAND_S
# include stdlib.h
@@ -73,6 +72,9 @@
#define RAND_SOURCE_READY (17)
static int dev_random_fdes = RAND_SOURCE_NOT_READY;
+#ifdef DEV_URANDOM
+static FILE* dev_random_file = NULL;
+#endif
err_status_t
@@ -83,9 +85,11 @@ rand_source_init(void) {
}
#ifdef DEV_URANDOM
/* open random source for reading */
- dev_random_fdes = open(DEV_URANDOM, O_RDONLY);
- if (dev_random_fdes 0)
+ dev_random_file = fopen(DEV_URANDOM, r);
+ if (dev_random_file == NULL)
return err_status_init_fail;
+ setvbuf(dev_random_file, NULL, _IONBF, 0);
+ dev_random_fdes = RAND_SOURCE_READY;
#elif defined(HAVE_RAND_S)
dev_random_fdes = RAND_SOURCE_READY;
#else
@@ -108,7 +112,7 @@ rand_source_get_octet_string(void *dest, uint32_t len) {
uint8_t *dst = (uint8_t *)dest;
while (len)
{
-ssize_t num_read = read(dev_random_fdes, dst, len);
+ssize_t num_read = fread(dst, len, 1, dev_random_file);
if (num_read = 0 || num_read len)
return err_status_fail;
len -= num_read;
@@ -150,7 +154,8 @@ rand_source_deinit(void) {
return err_status_dealloc_fail; /* well, we haven't really failed, *
* but there is something wrong*/
#ifdef DEV_URANDOM
- close(dev_random_fdes);
+ fclose(dev_random_file);
+ dev_random_file = NULL;
#endif
dev_random_fdes = RAND_SOURCE_NOT_READY;
Bug#764778: Patch incorrectly cherry-picked
While trying to enable srtp's OpenSSL support, I ran into a build error
and noticed that the patch for bug #764778 hand not been fully
cherry-picked from upstream, there were 3 remaining references to
sha1_ctx_t which were left unpatched.
I am attaching both the fixed 020141104~c270245.patch and the delta
against the current version of the patch.
Cheers,
Jeremy
diff --git a/debian/patches/020141104~c270245.patch b/debian/patches/020141104~c270245.patch
index 777c8d2..1fddf50 100644
--- a/debian/patches/020141104~c270245.patch
+++ b/debian/patches/020141104~c270245.patch
@@ -3,7 +3,7 @@ Origin: upstream, https://github.com/cisco/libsrtp/commit/c270245
Author: jfigus fol...@cisco.com
Forwarded: yes
Bug-Debian: http://bugs.debian.org/764778
-Last-Update: 2015-06-02
+Last-Update: 2015-07-29
--- a/crypto/hash/hmac.c
+++ b/crypto/hash/hmac.c
@@ -266,20 +266,20 @@ Last-Update: 2015-06-02
*/
-static inline void sha1_init (sha1_ctx_t *ctx)
-+static inline void srtp_sha1_init (sha1_ctx_t *ctx)
++static inline void srtp_sha1_init (srtp_sha1_ctx_t *ctx)
{
EVP_MD_CTX_init(ctx);
EVP_DigestInit(ctx, EVP_sha1());
}
-static inline void sha1_update (sha1_ctx_t *ctx, const uint8_t *M, int octets_in_msg)
-+static inline void srtp_sha1_update (sha1_ctx_t *ctx, const uint8_t *M, int octets_in_msg)
++static inline void srtp_sha1_update (srtp_sha1_ctx_t *ctx, const uint8_t *M, int octets_in_msg)
{
EVP_DigestUpdate(ctx, M, octets_in_msg);
}
-static inline void sha1_final (sha1_ctx_t *ctx, uint32_t *output)
-+static inline void srtp_sha1_final (sha1_ctx_t *ctx, uint32_t *output)
++static inline void srtp_sha1_final (srtp_sha1_ctx_t *ctx, uint32_t *output)
{
unsigned int len = 0;
Description: Rename SHA1 functions to avoid conflicts with downstream packages.
Origin: upstream, https://github.com/cisco/libsrtp/commit/c270245
Author: jfigus fol...@cisco.com
Forwarded: yes
Bug-Debian: http://bugs.debian.org/764778
Last-Update: 2015-07-29
--- a/crypto/hash/hmac.c
+++ b/crypto/hash/hmac.c
@@ -141,11 +141,11 @@
debug_print(mod_hmac, ipad: %s, octet_string_hex_string(ipad, 64));
/* initialize sha1 context */
- sha1_init(state-init_ctx);
+ srtp_sha1_init(state-init_ctx);
/* hash ipad ^ key */
- sha1_update(state-init_ctx, ipad, 64);
- memcpy(state-ctx, state-init_ctx, sizeof(sha1_ctx_t));
+ srtp_sha1_update(state-init_ctx, ipad, 64);
+ memcpy(state-ctx, state-init_ctx, sizeof(srtp_sha1_ctx_t));
return err_status_ok;
}
@@ -153,7 +153,7 @@
err_status_t
hmac_start(hmac_ctx_t *state) {
- memcpy(state-ctx, state-init_ctx, sizeof(sha1_ctx_t));
+ memcpy(state-ctx, state-init_ctx, sizeof(srtp_sha1_ctx_t));
return err_status_ok;
}
@@ -165,7 +165,7 @@
octet_string_hex_string(message, msg_octets));
/* hash message into sha1 context */
- sha1_update(state-ctx, message, msg_octets);
+ srtp_sha1_update(state-ctx, message, msg_octets);
return err_status_ok;
}
@@ -183,7 +183,7 @@
/* hash message, copy output into H */
hmac_update(state, (const uint8_t*)message, msg_octets);
- sha1_final(state-ctx, H);
+ srtp_sha1_final(state-ctx, H);
/*
* note that we don't need to debug_print() the input, since the
@@ -193,16 +193,16 @@
octet_string_hex_string((uint8_t *)H, 20));
/* re-initialize hash context */
- sha1_init(state-ctx);
+ srtp_sha1_init(state-ctx);
/* hash opad ^ key */
- sha1_update(state-ctx, (uint8_t *)state-opad, 64);
+ srtp_sha1_update(state-ctx, (uint8_t *)state-opad, 64);
/* hash the result of the inner hash */
- sha1_update(state-ctx, (uint8_t *)H, 20);
+ srtp_sha1_update(state-ctx, (uint8_t *)H, 20);
/* the result is returned in the array hash_value[] */
- sha1_final(state-ctx, hash_value);
+ srtp_sha1_final(state-ctx, hash_value);
/* copy hash_value to *result */
for (i=0; i tag_len; i++)
--- a/crypto/hash/hmac_ossl.c
+++ b/crypto/hash/hmac_ossl.c
@@ -163,11 +163,11 @@
debug_print(mod_hmac, ipad: %s, octet_string_hex_string(ipad, sizeof(ipad)));
/* initialize sha1 context */
-sha1_init(state-init_ctx);
+srtp_sha1_init(state-init_ctx);
state-init_ctx_initialized = 1;
/* hash ipad ^ key */
-sha1_update(state-init_ctx, ipad, sizeof(ipad));
+srtp_sha1_update(state-init_ctx, ipad, sizeof(ipad));
return (hmac_start(state));
}
@@ -192,7 +192,7 @@
octet_string_hex_string(message, msg_octets));
/* hash message into sha1 context */
-sha1_update(state-ctx, message, msg_octets);
+srtp_sha1_update(state-ctx, message, msg_octets);
return err_status_ok;
}
@@ -211,8 +211,8 @@
}
/* hash message, copy output into H */
-sha1_update(state-ctx, message, msg_octets);
-sha1_final(state-ctx, H);
+srtp_sha1_update(state-ctx, message, msg_octets);
+srtp_sha1_final(state-ctx, H);
/*
* note that we don't need to debug_print() the input, since the
Bug#770659: The cause seems to be access to /dev/urandom
I added a couple of printf's in srtp to track down why the call to srtp_init() was failing. I tracked it down to the rand_source_init() function, specifically: open(DEV_URANDOM, O_RDONLY) could not open /dev/urandom : Operation not permitted As everything works fine when the sandbox is disabled, I'd venture a guess that the sandbox is preventing access to /dev/urandom. I am not sure how to move forward to fix this though. Cheers, Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764778: Can you hold off uploading a bit?
Thank you Jonas for your quick reply! Before you make your new upload, one question : would you consider enabling OpenSSL support? I am currently investigating bug #770659, and am wondering whether an OpenSSL-enabled libsrtp would fix the issue. Cheers, Jeremy
Bug#791795: plasma-sdk seems to be the only package without an epoch
Hi Bogdan! Thanks for spotting the inconsistency in our package versioning. I had a look around, and plasma-sdk seems to be the exception and not the norm, the following packages *do* have an epoch (4:) : - bluedevil - plasma-desktop - plasma-nm - plasma-workspace - powerdevil Cheers, Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#793026: kde-window-manager: upgrade to 4:5.3.2-2 generates
On 26 Jul 2015 6:32 pm, MERLIN Philippe phil-deb1.mer...@laposte.net wrote: actually it's impossible to install kde-full apt-get -s install kde-full kde-standard Lecture des listes de paquets... Fait Construction de l'arbre des dépendances Lecture des informations d'état... Fait Certains paquets ne peuvent être installés. Ceci peut signifier que vous avez demandé l'impossible, ou bien, si vous utilisez la distribution unstable, que certains paquets n'ont pas encore été créés ou ne sont pas sortis d'Incoming. L'information suivante devrait vous aider à résoudre la situation : Les paquets suivants contiennent des dépendances non satisfaites : kde-full : Dépend: kde-plasma-desktop (= 5:87) mais ne sera pas installé kde-standard : Dépend: kde-plasma-desktop (= 5:87) mais ne sera pas installé Recommande: plasma-widget-networkmanagement mais il n'est pas installable E: Impossible de corriger les problèmes, des paquets défectueux sont en mode « garder en l'état ».apt-get -s install kde-full kde-standard Lecture des listes de paquets... Fait Construction de l'arbre des dépendances Lecture des informations d'état... Fait Certains paquets ne peuvent être installés. Ceci peut signifier que vous avez demandé l'impossible, ou bien, si vous utilisez la distribution unstable, que certains paquets n'ont pas encore été créés ou ne sont pas sortis d'Incoming. L'information suivante devrait vous aider à résoudre la situation : Les paquets suivants contiennent des dépendances non satisfaites : kde-full : Dépend: kde-plasma-desktop (= 5:87) mais ne sera pas installé kde-standard : Dépend: kde-plasma-desktop (= 5:87) mais ne sera pas installé Recommande: plasma-widget-networkmanagement mais il n'est pas installable E: Impossible de corriger les problèmes, des paquets défectueux sont en mode « garder en l'état ». The latest upload (5:88) should allow you to install kde-full without errors, but that is a different issue anyway. Jeremy
Bug#790703: Status moving forward?
On 07/23/2015 07:13 PM, Matt Wallace wrote: systemsettings5 correctly displays settings for KF5 applications, so it's just a question of more KF5 packages making their way into the archive. You can verify this by installing bluedevil (currently 4:5.3.2-1 in unstable) : a bluetooth icon appears. This seems reasonable, but I don't understand what the plan is here. It seems like it was premature to upgrade systemsettings to the v5 version before the rest of the system was ready to handle it. I ran apt-get upgrade and my whole settings system broke. Was this really the intended behavior? The exact timing of when each package hits unstable is unfortunately not entirely in the maintainers' hands : - a lot of packages had to trickle through the NEW queue - as some packages Build-Depend on others, they could not hit unstable simultaneously - etc.. Hopefully by now you have recovered the bulk of the system settings applets? Cheers, Jeremy
Bug#792875: What plasmoid causes the crash?
Both packageName and appletId are optimised out in the crash trace, any idea what plasmoid is causing the crash? Cheers, Jeremy
Bug#793037: no more bluetooth since upgrade to 4:5.3.2-1
On 07/23/2015 02:36 PM, Alexandre Pereira Nunes wrote: Package: bluedevil Version: 4:5.3.2-1 Followup-For: Bug #793037 In my system, the tray icon is missing, but I can still access bluetooth settings in the configuration panel. Are you running plasma-desktop 5.3.2? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792250: Transition to Qt 5.x
On 07/13/2015 10:55 AM, Boris Pek wrote: Source: qxmpp Severity: wishlist Hi Jeremy, It is time for updating qxmpp package to the latest stable release v0.8.3. What do you think about switching to Qt 5.x in this update? Any objections? I think it's a good iea to switch to Qt5, I was going to suggest the same. Cheers, Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792290: .desktop files are used, symlinks to script not
Hi, I agree that symlinks to scripts no longer seem to work, whether manually created or from System Settings = Startup and shutdown = Add script. On the other hand, using .desktop files as described in [1] does work. If you do System Settings = Startup and shutdown = Add program, it will create the .desktop file for you. [1] http://standards.freedesktop.org/autostart-spec/autostart-spec-latest.html -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#790703: systemsettings5 works fine, but operates only on KF5 packages
systemsettings5 correctly displays settings for KF5 applications, so it's just a question of more KF5 packages making their way into the archive. You can verify this by installing bluedevil (currently 4:5.3.2-1 in unstable) : a bluetooth icon appears. I have also built kwin using the packaging in the Debian Qt/KDE Maintainers git repo, and the window decoration settings appear too. Cheers, Jeremy
Bug#791729: What version of systemsettings?
Hi Diederik, What version of systemsettings are you running? Cheers, Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#790703: Is a depends on kded5 missing?
Installing kded5 reduces the number of error when launching systemsetting5. I do however end up with totally frozen / unusable UI, but that is possibly an entirely different issue. Cheers, Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773713: NMU interdiff
DKMS make.log for broadcom-sta-6.30.223.248 for kernel 4.1.0-rc1 (x86_64) Sat May 2 20:28:51 CEST 2015 /bin/sh: line 0: [: : integer expression expected /bin/sh: line 0: [: : integer expression expected I cannot reproduce this with 4.1.0-rc2 and dkms. Might be a locale issues. If you still get it with 4.1.0-rc2, consider reporting that as dkms bug, IMHO. I got this same warning against kernel 3.19 so I don't think it is specific to a kernel version. Anyway it did not break my build. Cheers, Jeremy
Bug#643583: Does #643583 still apply?
tags 643583 +moreinfo thanks Does bug #643583 also occur on recent asterisk versions? Cheers, Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749321: Poor transition path
I think the transition to pypdf2 was handled rather poorly. The module name is different, so I would expect a python-pypdf2 package instead of a misleading python-pypdf .. which does not contain a pypdf module. What I would suggest: - add a new python-pypdf2 package - if we really want to stop shipping python-pypdf, at least provide a minimal pypdf/__init__.py which does: from PyPDF2 import * (possibly with a deprecation warning) This would avoid breaking all reverse depends. Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762186: pyPdf = PyPDF2 transition breakage
Recently the pypdf2 source package, was uploaded to unstable, and forcibly took over the python-pypdf binary package. The problem is that pypdf2 does not provide a pyPdf module, but PyPDF2 which broke all the reverse dependencies. I would suggest: - pypdf2 be changed to provide a python-pypdf2 and python3-pypdf2 module - the last version of python-pypdf be re-uploaded - encouraging python-pypdf's reverse dependencies be patched to allow python-pypdf | python-pypdf2 Cheers, Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762083: Patch to fix pdfshuffler
tags 762083 +patch thanks Simply changing the import from pyPdf to PyPDF2 works. I am attaching a patch which does just that. Cheers, Jeremy Description: Use PyPDF2 instead of pyPdf --- a/pdfshuffler/pdfshuffler.py 2012-04-28 16:15:17.0 +0200 +++ b/pdfshuffler/pdfshuffler.py 2014-09-26 15:07:07.797798373 +0200 @@ -71,7 +71,7 @@ import cairo import poppler #for the rendering of pdf pages -from pyPdf import PdfFileWriter, PdfFileReader +from PyPDF2 import PdfFileWriter, PdfFileReader from pdfshuffler_iconview import CellRendererImage gobject.type_register(CellRendererImage)
Bug#595287: Does #595287 still apply?
tags 595287 + moreinfo thanks Does bug #595287 still apply to recent asterisk versions? From reading the source code, it looks as though there already is code which runs sox -m in res_monitor. Also, the MixMonitor app seems to be prefered over Monitor, and it handles mixing itself. Cheers, Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761985: Master.csv not rotated?
Hi Daniel, On 09/17/2014 04:31 PM, Daniel Pocock wrote: The package provides a logrotate configuration /etc/logrotate.d/asterisk The Master.csv file is not listed in there though. Is there a reason for this and could that be commented on in README.Debian perhaps? Or should it be rotated by default? I would have no problem with including Master.csv in the logrotate file, but I lack the history on this: oversight or deliberate choice? Maybe Tzafrir can give us some insight? The only downside I can see is that it changes the behaviour compared to previous releases (so users may have developed their own scripts), but that can be addressed by a note in the NEWS file. Personally I disable writing CDRs to CSV, so I don't have any strong feelings either way. Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#617648: Does #617648 still occur?
tags 617648 +moreinfo thanks Does bug #617648 also occur on recent asterisk versions? Cheers, Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#533307: Does #533307 still apply?
tags 533307 +moreinfo thanks Does bug #533307 still apply to recent asterisk versions? Cheers, Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#689109: Bug #689109 is now fixable
I have uploaded a new version of asterisk, which now Provides asterisk-$$AST_BUILDOPT_SUM, so bug #689109 should now be fixable. Cheers, Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#504741: Does bug #504741 exist on a recent asterisk?
tags 504741 +moreinfo thanks Could you please let me know whether bug #504741 still applies on a recent asterisk? Thanks, Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#497032: Does bug #497032
tags 497032 +moreinfo thanks A while back you filed bug #497032. Are you still able to reproduce this bug with a recent asterisk? Cheers, Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#563878: What is the impact of bug #563878
tags 563878 +moreinfo thanks In bug #563878 you reported that /etc/asterisk/manager.d is owned by root, which is correct. How does this pose a problem? Kind regards, Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#531728: asterisk: console video support
reopen 531728 thanks OK, I obviously misunderstood the status of this bug so I am reopening it. Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756425: asterisk: lua doesn't work in 11.11.0
Looks like a resurgence of the following bug: https://issues.asterisk.org/jira/browse/ASTERISK-17279 .. and this regression was caused by the fix for: https://issues.asterisk.org/jira/browse/ASTERISK-23818 Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#741186: Fix hot and cold plugging
Since the switch to systemd, the udev configuration needs to be reworked
to work properly both for hot and cold plugging.
The Fedora maintainers have kindly shared their solution here:
https://lists.gnu.org/archive/html/gpsd-users/2014-04/msg00037.html
The attached patch introduces a gpsdctl systemd service, which replaces
the hotplug wrapper script. I have successfuly tested the patch with
real hardware:
- booting without a GPS attached, and plugging in the GPS once the
system is started
- booting with a GPS attached
Cheers,
Jeremy
commit eff9cb9a8831d68a3e8c5381954e2acad6b0d5cf
Author: Jeremy Lainé jeremy.la...@m4x.org
Date: Mon Aug 4 19:41:48 2014 +0200
fix hot and cold plugging (from Fedora)
diff --git a/debian/gpsdctl@.service b/debian/gpsdctl@.service
new file mode 100644
index 000..d528ddc
--- /dev/null
+++ b/debian/gpsdctl@.service
@@ -0,0 +1,12 @@
+[Unit]
+Description=Manage %I for GPS daemon
+Requires=gpsd.socket
+BindsTo=dev-%i.device
+After=dev-%i.device
+
+[Service]
+Type=oneshot
+EnvironmentFile=-/etc/default/gpsd
+RemainAfterExit=yes
+ExecStart=/bin/sh -c [ \$USBAUTO\ = true ] /usr/sbin/gpsdctl add /dev/%I || :
+ExecStop=/bin/sh -c [ \$USBAUTO\ = true ] /usr/sbin/gpsdctl remove /dev/%I || :
diff --git a/debian/rules b/debian/rules
index 57b6e3f..12c7307 100755
--- a/debian/rules
+++ b/debian/rules
@@ -167,14 +167,11 @@ install-stamp: build-stamp build-static-stamp $(LIBGPS_DEBIAN_FILE_TARGETS)
done
# install static lib
cp static_lib/libgps.a debian/tmp/usr/lib/$(DEB_HOST_MULTIARCH)
- # install hotplug wrapper
- mkdir -p debian/tmp/lib/udev
- cp gpsd.hotplug debian/tmp/lib/udev
- chmod 755 debian/tmp/lib/udev/gpsd.hotplug
cp INSTALL TROUBLESHOOTING
# install systemd files
mkdir -p debian/tmp/lib/systemd/system
cp systemd/* debian/tmp/lib/systemd/system
+ cp debian/gpsdctl@.service debian/tmp/lib/systemd/system
# fix various manpages
for i in cgps.1 gegps.1 lcdgps.1 xgps.1 xgpsspeed.1 gpxlogger.1; do \
rm -f debian/tmp/usr/share/man/man1/$$i ;\
@@ -219,7 +216,8 @@ binary: install-stamp
dh_python2 -pgpsd-dbg usr/lib/gpsd/debug
dh_python2 -pgpsd-clients /usr/bin
dh_python2 -pgpsd /lib/udev/
- cp $(CURDIR)/gpsd.rules $(CURDIR)/debian/gpsd.udev
+ # Use gpsdctl service instead of hotplug script
+ sed 's|RUN+=/lib/udev/gpsd.hotplug|TAG+=systemd, ENV{SYSTEMD_WANTS}=gpsdctl@%k.service|' $(CURDIR)/gpsd.rules $(CURDIR)/debian/gpsd.udev
dh_installudev
dh_link
dh_strip --dbg-package=$(PACKAGE_GPSDDBG)
Bug#542384: Close this bug?
I cannot reproduce this bug with a vanilla setup in sid, and I have serious doubts it even exists in oldstable. I would suggest closing it. Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#697664: Please check whether #697664 applies to unstable
tags 697664 +moreinfo thanks Could you please check whether this bug still applies with a recent gpsd version? Cheers, Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#725925: Can I get my $500 now, please? ;-)
Hi Thorsten, Thanks for the patch. I am not entirely convinced it is correct though, as it does change what gets gets passed into realtime_ldap_base_ap (two arguments have been already been consumed). An alternative patch was suggested in the upstream issue which instead makes a copy of the variadic list: https://issues.asterisk.org/jira/browse/ASTERISK-19941 Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#742783: Fixed by commit 157ff24279baf1e9775ea58d1409fcb8f00bda2a ?
Hi Daniel, Does your commit 157ff24279baf1e9775ea58d1409fcb8f00bda2a fix the issue you reported? I am working on packaging asterisk 11.9.0 and am trying to put together the debian/changelog. Thanks, Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#595288: Please provide an example for bug #595288
tags 595288 + moreinfo unreproducible thanks I am using MixMonitor without any problems from the dialplan, can you please let me know: - if the bug you reported is still relevant on modern asterisk versions - how to reproduce your bug Thanks, Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#531728: Is bug 531728 still relevant?
A while ago you filed bug #531728 against asterisk asking for console video support using ffmpeg. Since ffmpeg has to my knowledge been made obsolete by libav, is this still relevant? Jeremy
Bug#694805: Status of bug #694805
Where do we stand on this bug now that Asterisk 11 is in unstable? I see the bug was marked as pending in preparation for the upload of 11.4.0 but never actually got closed. Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#733955: per-peer TURN server settings
tags 733955 + upstream thanks Daniel, it looks like this bug would be better handled upstream. What action do you expect from the Debian maintainers? On 2 Jan 2014 17:12, Daniel Pocock dan...@pocock.com.au wrote: Package: asterisk Severity: wishlist In recent versions of Asterisk it is possible to configure a TURN server in rtp.conf It would be useful in some situations to configure more than one TURN server and specify which one to use on a per-peer basis ___ Pkg-voip-maintainers mailing list pkg-voip-maintain...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-voip-maintainers
Bug#733956: TURN without ICE
tags 733956 + upstream thanks Same comment as for #733955, this needs to be sent to upstream. A debian-specific change does not make sense.
Bug#733955: per-peer TURN server settings
Please at least bring this up on the asterisk development mailing list. The BTS is not a wiki and there is little point in filing bugs which are not actionable by Debian
Bug#564316: Does bug #546316 occur on a modern asterisk?
Could you please retest the bug on a recent asterisk?
Bug#721622: More changes needed for libfreeradius-client2
It seems just linking against libfreeradius-client2 is not sufficient, we also need to change the default RADIUS configuration path in the asterisk code. If libfreeradius-client2 tries to load the old configuration file (/etc/radiusclient-ng/radiusclient.conf) it bombs with a segfault: #0 0x7fffab126f38 in rc_conf_int () from /usr/lib/x86_64-linux-gnu/libfreeradius-client.so.2 #1 0x7fffab127108 in test_config () from /usr/lib/x86_64-linux-gnu/libfreeradius-client.so.2 #2 0x7fffab127605 in rc_read_config () from /usr/lib/x86_64-linux-gnu/libfreeradius-client.so.2 #3 0x7fff9fb011d1 in load_module () at cdr_radius.c:268 #4 0x004cf590 in start_resource (mod=0xefa870) at loader.c:845 #5 0x004d0300 in start_resource (mod=optimized out) at loader.c:1037 #6 load_resource_list (load_order=load_order@entry=0x7fffc480, global_symbols=global_symbols@entry=0, mod_count=mod_count@entry=0x7fffc47c) at loader.c:1047 #7 0x004d0605 in load_modules (preload_only=preload_only@entry=0) at loader.c:1200 #8 0x00426ded in main (argc=optimized out, argv=optimized out) at asterisk.c:4239 Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#731971: asterisk-vpb: not installable in sid
tag 731971 + pending stop I have set the Breaks/Replaces version to 1:11.6.0~dfsg-1 in git, thanks for reporting this. Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#721622: Improved patch commited to git
tags 721622 + pending stop Daniel, I have commited a modified version of your patch which allows building against FreeRADIUS-client or the older radiusclient-ng2 library. Hopefully this should be acceptable upstream. Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#721622: Patch needs some more work it seems
I tried applying the suggested patch, and while the build succeeded, the resulting asterisk-modules seem to be built without RADIUS support. I will take a closer look when I have a moment. Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685753: No more ocfs2-tools in Debian
severity 685753 important thanks This bug was marked as grave, although it does not render the whole of ocfs2-tools unusable, just ocfs2-tools-pacemaker (for I do not have a test setup). Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#709360: Any chance of seeing this fixed soon?
As I understand it, fixing bug #709360 is straightforward, so when can we expect a fixed upload of python-imaging? As things stand some packages are totally broken by this bug (for instance fretsonfire): http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729209 Cheers, Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#729209: fretsonfire-game: does not launch as PngImagePlugin is not found
On a side note, upstream should probably stop using the deprecated PIL imports, as I suppose the python-imaging compatibility package won't be around forever. For instance the bug with PngImagePlugin can be fixed with the attached one-liner. Jeremy --- a/src/Texture.py 2013-11-10 13:34:33.200829642 +0100 +++ a/src/Texture.py 2013-11-10 13:34:23.504895668 +0100 @@ -27,7 +27,7 @@ import Image import pygame import StringIO -import PngImagePlugin +from PIL import PngImagePlugin from OpenGL.GL import * from OpenGL.GLU import * from Queue import Queue, Empty
Bug#725210: embeds multiple libraries, at least two of which undistributable
On 10/02/2013 10:23 PM, Faidon Liambotis wrote: Package: asterisk Version: 1:11.5.1~dfsg-2 Severity: serious I was surprised and initially happy to see Asterisk 11 uploaded into sid. My happiness quickly diminished when I saw that the upload contains the embedded pjproject as-is, despite this issue having been flagged for months now and being the sole blocker for an upload since the release of Asterisk 11 eleven months ago. There are several policy violations here: - Contains a convenience copy of pjproject under res/pjproject (§4.13) This is indeed a slip-up, the pjproject source was definitely intended to be stripped from the asterisk tarball, as documented in debian/changelog. I found the commit which removed the pjproject-stripping-code from debian/rules: http://anonscm.debian.org/gitweb/?p=pkg-voip/asterisk.git;a=commitdiff;h=6148e287cc35d0756785af74fe2bfa6f3148d706 - pjproject itself contains convenience copies of several libraries under res/pjproject/third_party/ some of which already packaged in Debian (§4.13) - All of the above are completely undocumented in d/copyright (§12.5) - Not only they are undocumented, but it looks like no audit has happened on them whatsoever. From a very cursory look, at least res/pjproject/third_party/milenage/ res/pjproject/third_party/g7221/ seem to completely lack license information other than the occasional All right reserved, which makes them undistributable by Debian or anyone else. (§2.3) You may not have noticed, but pjproject has its own package: http://packages.qa.debian.org/p/pjproject.html Go take a look at the pjproject packaging and you will find these points have been addressed. I'm baffled on how a DD could ever upload this into the archive, esp. since these issues were widely known and discussed beforehand. Please refrain from making such uploads in the future, as it's both a disgrace to Debian's standards and a legal risk. I suggest you have more than a cursory look next time before using this kind of tone. Thanks anyway for the report, Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#708122: Status / need help for pjproject packaging?
I am assuming the current version of the packaging is on git.tzafrir.org, can we move this to a repo on alioth, presumably under control of pkg-voip-maintainers? I have spotted what looks like a mistake in debian/control for pjproject: - it has a Build-Depends on libpulse-dev (which looks unnecessary) - it is missing a Build-Depends on portaudio19-dev (without which it FTBFS for me) The attached patch fixes this. Jeremy commit 559a90618b65cc809cc9db7b69bc4574faf4fd8a Author: Jeremy Lainé jeremy.la...@m4x.org Date: Tue Jul 30 10:15:54 2013 +0200 Fix Build-Depends: replace pulse by portaudio diff --git a/debian/control b/debian/control index cd7561d..a50dda0 100644 --- a/debian/control +++ b/debian/control @@ -6,7 +6,7 @@ Build-Depends: debhelper (= 8), libspeex-dev, libspeexdsp-dev, libgsm1-dev, libsrtp0-dev, - libpulse-dev + portaudio19-dev Standards-Version: 3.9.3 #Homepage: http://www.reviewboard.org/ #Vcs-Git: git://anonscm.debian.org/collab-maint/rbtools.git
Bug#708122: Status / need help for pjproject packaging?
Tzafrir, What is the current status of your Debian packaging for pjproject (still the one on github?)? Can I help you out in any way, as I am eager to see asterisk 11.x in Debian? Cheers, Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#714846: iceweasel: please enable getUserMedia
On 07/04/2013 03:21 AM, Mike Hommey wrote: That doesn't tell much. As a matter of fact, your url works for me with iceweasel 22 from experimental. If Chromium and Iceweasel don't use the same source for video, it's possible it works in one and not the other (like one using a library and the other using a different one, etc.) You are right, running Iceweasel 22 on another box works just fine, so it looks like it is hardware specific. I also tried running an x86_64 build of Firefox (from ftp.mozilla.org) and got the same result, so it looks as though I should be chasing this issue upstream. But that could also be a config problem on your end. Can you try with a fresh profile or after resetting your profile (from Help Troubleshooting information) Yes, unfortunately a fresh profile doesn't solve the problem. Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#714846: iceweasel: please enable getUserMedia
On 07/03/2013 01:53 PM, Mike Hommey wrote: It is enabled by default. But it's prefixed. navigator.mozGetUserMedia. Mike I know about the prefixing, but as the tests I ran failed I assumed the feature was disabled. I tried: http://simpl.info/getusermedia/ I was never prompted for permissions to use the camera, and as far as I can tell getUserMedia calls neither the success nor the error callback. The camera itself is unlikely to be the cause of the problem, as getUserMedia works fine for me in Chromium. Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#714142: qdjango: New upstream release (0.3.0)
Hi Pete, I'll upload the new version, but I'm not sure I understand why the Qt5-specific patch is required. How does disabling deprecated functions help the build? Jeremy Le Jun 26, 2013 à 10:39 AM, Pete Woods a écrit : Package: qdjango Severity: wishlist Tags: patch Dear Maintainer, I have packaged the new release of QDjango with the following bugfixes: * Fix and test unique field option. * Add a unique_together model option. * Don't crash if QDjango::database() is called before QDjango::setDatabase(). * Make index names coincide with those used by django. * Register models without instantiating them. * Improve foreign keys: - Do not take object ownership in QDjangoMetaModel::setForeignKey(). - Fix QDjangoQuerySet::selectRelated() with NULL foreign keys. Patch included to build against latest Qt version. Original source tarball came without modification from: https://qdjango.googlecode.com/files/qdjango-0.3.0.tar.gz -- System Information: Debian Release: wheezy/sid APT prefers saucy-updates APT policy: (500, 'saucy-updates'), (500, 'saucy-security'), (500, 'saucy'), (100, 'saucy-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.9.0-6-generic (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash qdjango_0.3.0-1.debian.tar.gzqdjango_0.3.0-1.dsc -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#714142: qdjango: New upstream release (0.3.0)
Pete, Le Jun 26, 2013 à 10:55 AM, Pete Woods a écrit : That macro is confusing, I admit. It actually enables the deprecated functions! As Qt5 has not landed yet in Debian/unstable, I will be uploading QDjango 0.3.0 without the Qt5 patch. As I'm also the upstream author, I will address any Qt5-related issues upstream. I am a bit surprised by the need for the macro you mention, I had successfully built QDjango against Qt5 betas. Does this sound OK to you? Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#710557: asterisk: SIP causes are incorrectly mapped to asterisk causes
Package: asterisk
Version: 1:1.8.13.1~dfsg-3
Severity: normal
Tags: upstream patch
asterisk 1.8.x has a regression which results in SIP error causes being
incorrectly mapped to generic asterisk error causes. One consequence of
this bug is that it is not possible to distinguish calls to unallocated
numbers from other errors.
The issue is discussed here:
http://markmail.org/message/wkfyiq2qdjiqfz6p
and was tracked upstream (and fixed) here:
https://issues.asterisk.org/jira/browse/ASTERISK-19914
Please consider applying the attached patch.
-- System Information:
Debian Release: 7.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages asterisk depends on:
ii adduser 3.113+nmu3
ii asterisk-config 1:1.8.13.1~dfsg-3
ii asterisk-core-sounds-en [asterisk-prompt-en] 1.4.22-1
ii asterisk-core-sounds-en-gsm 1.4.22-1
ii asterisk-modules 1:1.8.13.1~dfsg-3
ii libc6 2.13-37
ii libcap2 1:2.22-1.2
ii libgcc1 1:4.7.2-5
ii libssl1.0.0 1.0.1e-1
ii libstdc++64.7.2-5
ii libtinfo5 5.9-10
ii libxml2 2.8.0+dfsg1-7+nmu1
Versions of packages asterisk recommends:
ii asterisk-moh-opsound-gsm 2.03-1
ii asterisk-voicemail [asterisk-voicemail-storage] 1:1.8.13.1~dfsg-3
ii sox 14.4.0-3
Versions of packages asterisk suggests:
pn asterisk-dahdi none
pn asterisk-dev none
pn asterisk-doc none
pn asterisk-ooh323 none
-- no debconf information
Subject: Incorrect SIP cause to Asterisk cause mapping in chan_sip
Author: Pavel Troller
Bug: http://issues.asterisk.org/jira/browse/ASTERISK-19914
Since certain time, chan_sip incorrectly maps the SIP three digit return
codes to the Asterisk internal (ITU.T based) Clear Cause values. There is
a mapping function hangup_sip2cause(), but it is not used in all the places,
where it should be, and various hardcoded constants are used instead, which
are sometimes way off the recommended values. For example, the 404 Not found
now maps to AST_CAUSE_CONGESTION (Clear Cause 34), while it should be mapped
to AST_CAUSE_UNALLOCATED (Clear Cause 1). It also influences the SIP SIP
B2BUA functionality, where a totally different response codes are
retransmitted (for example, 404 changes to 503).
--- a/channels/chan_sip.c 2012-05-25 18:44:25.898834370 +0200
+++ b/channels/chan_sip.c 2012-05-25 18:45:28.405343312 +0200
@@ -20371,7 +20371,7 @@
ast_log(LOG_WARNING, Received response: \Forbidden\ from '%s'\n, get_header(p-initreq, From));
if (!req-ignore p-owner) {
ast_set_hangupsource(p-owner, p-owner-name, 0);
- ast_queue_hangup_with_cause(p-owner, AST_CAUSE_CONGESTION);
+ ast_queue_hangup_with_cause(p-owner, hangup_sip2cause(resp));
}
break;
@@ -20379,7 +20379,7 @@
xmitres = transmit_request(p, SIP_ACK, seqno, XMIT_UNRELIABLE, FALSE);
if (p-owner !req-ignore) {
ast_set_hangupsource(p-owner, p-owner-name, 0);
- ast_queue_hangup_with_cause(p-owner, AST_CAUSE_CONGESTION);
+ ast_queue_hangup_with_cause(p-owner, hangup_sip2cause(resp));
}
break;
@@ -20389,7 +20389,7 @@
ast_log(LOG_WARNING, Re-invite to non-existing call leg on other UA. SIP dialog '%s'. Giving up.\n, p-callid);
xmitres = transmit_request(p, SIP_ACK, seqno, XMIT_UNRELIABLE, FALSE);
if (p-owner) {
- ast_queue_hangup_with_cause(p-owner, AST_CAUSE_CONGESTION);
+ ast_queue_hangup_with_cause(p-owner, hangup_sip2cause(resp));
}
break;
@@ -20404,7 +20404,7 @@
append_history(p, Identity, SIP identity is required. Not supported by Asterisk.);
ast_log(LOG_WARNING, SIP identity required by proxy. SIP dialog '%s'. Giving up.\n, p-callid);
if (p-owner !req-ignore) {
- ast_queue_hangup_with_cause(p-owner, AST_CAUSE_CONGESTION);
+ ast_queue_hangup_with_cause(p-owner, hangup_sip2cause(resp));
}
break;
@@ -20437,7 +20437,7 @@
} else {
/* We can't set up this call, so give up */
if (p-owner !req-ignore) {
-ast_queue_hangup_with_cause(p-owner, AST_CAUSE_CONGESTION);
+ast_queue_hangup_with_cause(p-owner, hangup_sip2cause(resp));
}
}
break;
@@ -20445,7 +20445,7 @@
xmitres = transmit_request(p, SIP_ACK, seqno, XMIT_UNRELIABLE, FALSE);
if (p-owner !req-ignore) {
if (p-owner-_state != AST_STATE_UP) {
-ast_queue_hangup_with_cause(p-owner, AST_CAUSE_CONGESTION);
+ast_queue_hangup_with_cause(p-owner, hangup_sip2cause(resp));
} else {
/* This is a re-invite that failed. */
Bug#705921: asterisk: debian/rules using ` instead of $(shell
Package: asterisk Version: 1:1.8.13.1~dfsg-3 Severity: normal The debian/rules file is using backticks to set CFLAGS and LDFLAGS instead of $(shell ..) which is incorrect, as it is not garanteed to be expanded: CFLAGS = `dpkg-buildflags --get CFLAGS` LDFLAGS = `dpkg-buildflags --get LDFLAGS` CFLAGS += `dpkg-buildflags --get CPPFLAGS` This currently has no visible effect to my knowledge, but it will cause trouble when packaging asterisk 11, the build fails with: dpkg-buildflags: No such file or directory The same issue was found and fixed in rsync in #699165. -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages asterisk depends on: ii adduser 3.113+nmu3 pn asterisk-config | asterisk-config-custom none pn asterisk-core-sounds-en-gsm | asterisk-prompt-en none pn asterisk-modules none ii libc6 2.13-37 ii libcap2 1:2.22-1.2 ii libgcc1 1:4.7.2-5 ii libssl1.0.0 1.0.1e-1 ii libstdc++64.7.2-5 ii libtinfo5 5.9-10 ii libxml2 2.8.0+dfsg1-7+nmu1 Versions of packages asterisk recommends: pn asterisk-moh-opsound-gsm none pn asterisk-voicemail | asterisk-voicemail-storage none ii sox 14.4.0-3 Versions of packages asterisk suggests: pn asterisk-dahdi none pn asterisk-dev none pn asterisk-doc none pn asterisk-ooh323 none -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704707: trac-authopenid crashes when an OpenID provider does not provide a full name
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/04/2013 11:18 PM, Daniel Kahn Gillmor wrote: Hi Jeremy-- On 04/04/2013 04:48 PM, Daniel Kahn Gillmor wrote: Without the attached patch, when an OpenID provider declines to provide a full name, trac crashes by accessing the authname variable before it was initialized. I've just pushed this fix into the collab-maint svn repository mentioned in the Vcs-* headers of debian/control, and added myself to Uploaders: on the theory that its placement in collab-maint encourages collaborative maintenance. I've tested this patch and it works fine, so i'm uploading it to unstable. I hope i'm not stepping on your toes, Jeremy! If you'd rather i just contribute patches via the BTS and the VCS, but not upload, let me know and i won't take the uploading step in the future. Thanks for the patch Daniel! I have absolutely no problem with your upload, as you said it's in collab-maint for a reason. Feel free to upload again as needed. Cheers, Jeremy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlFed/cACgkQ4mJJZqJp2SehzACglrCHsx+d0jE3RyF70XreBtf9 Bj0AoJ9aY7e6BQcCKVtGqqOuMn78bbfb =/KBm -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#700669: Allow pyrad 1.2-1+deb7u1 into wheezy
On 02/23/2013 02:33 PM, Adam D. Barratt wrote: On Sun, 2013-02-17 at 13:59 +, Jonathan Wiltshire wrote: Once 1.2-1+deb7u1 reaches wheezy (next 24 hours) we will be able to use 1.2-1+deb6u1 for any hypothetical DSA to slot in between squeeze and wheezy. Well, there's a 1.2.1+deb6u1 in p-u-NEW. I can't find a p-u request for it though... I have just filed the missing p-u request. Cheers, Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#700669: Allow pyrad 1.2-1+deb7u1 into wheezy
Dear release team, Yesterday the following security vulnerability in the pyrad package was brought to my attention by Salvatore Bonaccorso: https://security-tracker.debian.org/tracker/CVE-2013-0294 It is tracked in the following bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700669 I have uploaded version 1.2-1+deb7u1 targeted at testing-proposed-updates (debdiff attached), as unstable carries a different upstream version. Could you please let this version into wheezy? Thanks in advance, Jeremy pyrad_1.2-1+deb7u1.debdiff Description: Binary data
Bug#700669: pyrad: CVE-2013-0294: potentially predictable password hashing and packet IDs
Hi Salvatore, I have just uploaded the requested version to testing-proposed-updates and will get in touch with the release team to allow it into wheezy. For squeeze, the package will be exactly the same (squeeze / wheezy both have pyrad 1.2-1), but what should the version number be? Cheers, Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#700669: Allow pyrad 1.2-1+deb7u1 into wheezy
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/17/2013 01:19 AM, Jonathan Wiltshire wrote: It's traditional to seek approval *before* uploading; more so in this case since adding a patch system is a no-no. The change itself is fine, please upload with this only. You will have to bump the version number IIRC. OK, attached is the resulting debdiff. On a sidenote, you might consider updating the following page to make it cristal clear, as I obviously did not get the message: http://release.debian.org/wheezy/freeze_policy.html Rule #1: Changing patch systems = Adding or changing patch systems Rule #2: If in doubt, first contact the release team = Always contact the release team first Thanks, Jeremy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlEgiHgACgkQ4mJJZqJp2SeURwCfehij0NsJR5BO10rIP32pYjqe On0AnixhAivkdmHVHj82URcWnnCdzTzg =8wEX -END PGP SIGNATURE- diff -u pyrad-1.2/debian/changelog pyrad-1.2/debian/changelog --- pyrad-1.2/debian/changelog +++ pyrad-1.2/debian/changelog @@ -1,3 +1,10 @@ +pyrad (1.2-1+deb7u2) testing-proposed-updates; urgency=high + + * Use a better random number generator to prevent predictable password +hashing and packet IDs (CVE-2013-0294, Closes: #700669). + + -- Jeremy Lainé jeremy.la...@m4x.org Sun, 17 Feb 2013 08:21:08 +0100 + pyrad (1.2-1) unstable; urgency=low * New upstream release (Closes: #532843). only in patch2: unchanged: --- pyrad-1.2.orig/pyrad/packet.py +++ pyrad-1.2/pyrad/packet.py @@ -31,8 +31,11 @@ CoAACK = 44 CoANAK = 45 +# Use cryptographic-safe random generator as provided by the OS. +random_generator = random.SystemRandom() + # Current ID -CurrentID = random.randrange(1, 255) +CurrentID = random_generator.randrange(1, 255) class PacketError(Exception): pass @@ -219,7 +222,7 @@ data= for i in range(16): -data+=chr(random.randrange(0,256)) +data+=chr(random_generator.randrange(0, 256)) return data CreateAuthenticator=staticmethod(CreateAuthenticator) @@ -234,7 +237,7 @@ :rtype: integer -return random.randrange(0,256) +return random_generator.randrange(0, 256) def ReplyPacket(self):
Bug#682517: Allow ocfs2-tools 1.6.4-2 into wheezy
Le Sep 10, 2012 à 9:01 PM, Adam D. Barratt a écrit : On Wed, 2012-08-15 at 13:46 +0100, Adam D. Barratt wrote: On 15.08.2012 10:47, Jeremy Lainé wrote: I have uploaded a new revision of ocfs2-tools to unstable which fixes bug #682517 (inability to launch the ocfs2console GUI): [...] Unblocked; thanks. Unfortunately, that's not going to work. The migration is blocked by both corosync and redhat-cluster, neither of which has been unblocked; the latter is RC-buggy and itself depends on gfs2-utils, which is also RC-buggy. Please could you prepare a package targeted at testing-proposed-updates and versioned as 1.6.4-1+deb7u1 and open an unblock bug with a debdiff attached? I have uploaded the requested version, will open an unblock bug immediately. Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682517: ocfs2-tools: diff for NMU version 1.6.4-1.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sorry, was away for a couple of days. Thanks for the diagnostics and the fix: the patch indeed had the opposite behaviour to the expected one! I will be uploading the fixed package in a couple of minutes. Jeremy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlArUw0ACgkQ4mJJZqJp2SfPrACeMj5ooVgwDyQCm4UQzIMrXzPl UgIAn1+m6rfqQXL2rwSHtbH6x/hgonQo =gkqh -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682517: Allow ocfs2-tools 1.6.4-2 into wheezy
Dear release team, I have uploaded a new revision of ocfs2-tools to unstable which fixes bug #682517 (inability to launch the ocfs2console GUI): http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682517 The fix (thanks Sébastien Villemot) is straight-forward: drop a bad Debian/Ubuntu specific patch, as can be seen from the attached debdiff. Could you please let this new version migrate into wheezy? Thanks, Jeremy diff -Nru ocfs2-tools-1.6.4/debian/changelog ocfs2-tools-1.6.4/debian/changelog --- ocfs2-tools-1.6.4/debian/changelog 2012-04-18 09:16:36.0 +0200 +++ ocfs2-tools-1.6.4/debian/changelog 2012-08-15 09:32:32.0 +0200 @@ -1,3 +1,10 @@ +ocfs2-tools (1.6.4-2) unstable; urgency=low + + * Remove popen2-ignore-depreciation-warn.patch: it has the opposite effect, +turning deprecation warnings into errors (Closes: #682517, LP: #923754). + + -- Jeremy Lainé jeremy.la...@m4x.org Wed, 15 Aug 2012 09:31:09 +0200 + ocfs2-tools (1.6.4-1) unstable; urgency=low * New upstream release. Closes: #669023. diff -Nru ocfs2-tools-1.6.4/debian/patches/popen2-ignore-depreciation-warn.patch ocfs2-tools-1.6.4/debian/patches/popen2-ignore-depreciation-warn.patch --- ocfs2-tools-1.6.4/debian/patches/popen2-ignore-depreciation-warn.patch 2011-03-25 16:48:30.0 +0100 +++ ocfs2-tools-1.6.4/debian/patches/popen2-ignore-depreciation-warn.patch 1970-01-01 01:00:00.0 +0100 @@ -1,18 +0,0 @@ -Description: Ignore the depreciation warning that popen2 will raise when it is imported. - Pending conversion to subprocess module. -Author: Dave Walker (Daviey) davewal...@ubuntu.com -Bug: https://launchpad.net/bugs/655548 a/ocfs2console/ocfs2console -+++ b/ocfs2console/ocfs2console -@@ -13,6 +13,11 @@ - # - import warnings - warnings.filterwarnings(error) -+ -+# Ignore the depreciation warning that popen2 will raise when it is imported. -+# FIXME: Pending conversion to subprocess module. -+warnings.simplefilter(ignore, DeprecationWarning) -+ - try: - import gtk - except Exception, e: diff -Nru ocfs2-tools-1.6.4/debian/patches/series ocfs2-tools-1.6.4/debian/patches/series --- ocfs2-tools-1.6.4/debian/patches/series 2012-04-18 09:02:42.0 +0200 +++ ocfs2-tools-1.6.4/debian/patches/series 2012-08-15 09:41:00.0 +0200 @@ -5,7 +5,6 @@ shorten-manpage-lines.patch ld-no-add-needed.diff ld-as-needed.diff -popen2-ignore-depreciation-warn.patch ocfs2-controld-pcmk-id.patch format-security.patch ocfs2-controld-headers.patch
Bug#669615: Close this bug?
qxmpp-dev's additional features have almost entirely been merged into plain QXmpp, and I am working closely with Georg Rudoy to merge the remaining differences. I therefore think that packaging qxmpp-dev at this point is not the way to go. Any thoughts? Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#669615: Close this bug?
On 08/02/2012 08:33 PM, Boris Pek wrote: Unfortunately, integration is not finished yet. When leechcraft can be built with unmodified library, I'll close this ITP. Sounds good to me. We should be able to complete the merge within the month or so. Cheers, Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#662784: qxmpp 0.4.0-1 builds from source
qxmpp 0.4.0-1 does build from source against multi-arch Qt 4.8, so I don't think the bug should be serious. It doesn't however install its libs into /usr/lib/THE_ARCH, so I'll keep this bug open to track this. Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#658483: Georg is now a QXmpp committer
Hi Boris, Georg Rudoy is now a QXmpp committer, so I am sure we can get whatever features are required for LeechCraft into QXmpp core (LeechCraft-specific stuff can still live inside LeechCraft). I would really rather there only be a single QXmpp, otherwise it'll make life difficult for developers. On a side note, QXmpp trunk is now built as a shared library by default, which is probably something you'd want. Cheers, Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#662229: mongrel-cluster: breaks mongrel_rails
No objection on my behalf, its definitely legacy. On 04/03/2012 20:18 Antonio Terceiro wrote: Package: mongrel-cluster Version: 1.0.5-5 Severity: grave Justification: renders package unusable Having mongrel-cluster installed, running mongrel_rails in a mostly empty rails app crashes: /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:76:in `_deprecated_load_specification': uninitialized constant Gem::Path (NameError) from /usr/lib/ruby/vendor_ruby/1.8/rubygems/deprecate.rb:39:in `skip_during' from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:75:in `_deprecated_load_specification' from /usr/lib/ruby/vendor_ruby/1.8/rubygems/deprecate.rb:63:in `send' from /usr/lib/ruby/vendor_ruby/1.8/rubygems/deprecate.rb:63:in `load_specification' from /usr/lib/ruby/1.8/gem_plugin.rb:114:in `load' from /usr/lib/ruby/1.8/gem_plugin.rb:113:in `each' from /usr/lib/ruby/1.8/gem_plugin.rb:113:in `load' from /usr/bin/mongrel_rails:279 If I remove mongrel-cluster, mongrel is able to start. This problem might be caused by libgemplugin-ruby, since mongrel-cluster seems to be the only gem plugin packaged in Debian, and its mechanism is not triggered if there are no gem plugins installed (the case when I remove mongrel-cluster). -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=pt_BR.utf8, LC_CTYPE=pt_BR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mongrel-cluster depends on: ii libgemplugin-ruby 0.2.3-2 ii mongrel 1.1.5-6 ii ruby 4.8 ii ruby1.8 [ruby] 1.8.7.352-2 mongrel-cluster recommends no packages. mongrel-cluster suggests no packages. -- no debconf information -- Antonio Terceiro terce...@debian.org
Bug#645599: Any chance of getting this fixed?
I also got bitten by bug 645599 and was locked out of my servers. This is really not acceptable, especially for an update to a stable release! Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#644064: ocfs2-tools errors with -Werror=format-security
Hi, I have put together a patch (attached) which fixes all the warnings, except for one on which I would need some help. The relevant information is here: http://oss.oracle.com/pipermail/ocfs2-tools-devel/2011-October/004008.html It's basically a case where custom printf handlers are registered, and a non-litteral format (user supplied, but escaped so as to avoid standard format specifiers) is being passed to fprintf like this: fprintf(stdout, fmt); Is there any way to inhibit the warning for this specific line? Or will I end up having to compile the whole package with -Wno-format-nonliteral ? Thanks in advance for any pointers, Jeremy format-security.patch Description: Binary data
Bug#633279: More information about bug #633279
tag 633279 upstream thanks Was the file system mounted when you attempted the fsck? In any case this looks like an upstream issue and would probably be better handled by the ocfs2-tools developers. Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#616389: Works for me with mesa 7.10.2-1
Since I upgraded libgl1-mesa-dri to version 7.10.2-1 I no longer experience a crash when closing an X session. I'll let the original reporter confirm, but it would seem the bug is fixed. Cheers, Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#616726: ocfs2-tools: Kernel bug seems to occur on ocfs2+drbd in pri-pri
reassign 616726 linux-2.6 thanks The bug report you submitted is a kernel bug, so I am reassigning it to the linux-2.6 package. Also, I suspect that solving this issue requires an intimate knowledge of the OCFS2 code, in which case you'd probably be better served by posting this to the OCFS2 users mailing list: http://oss.oracle.com/mailman/listinfo/ocfs2-users Regards, Jeremy On 03/06/2011 11:39 PM, Tim Stoop wrote: Package: ocfs2-tools Version: 1.4.4-3 Severity: normal Hi there, Not sure if this is the correct package to report it against, but we've been seeing a lot of these messages lately: Mar 6 22:31:50 wp1 kernel: [382123.062506] BUG: unable to handle kernel NULL pointer dereference at 0002 Mar 6 22:31:50 wp1 kernel: [382123.063396] IP: [810e7c50] __kmalloc+0xd2/0x141 Mar 6 22:31:50 wp1 kernel: [382123.063833] PGD 0 Mar 6 22:31:50 wp1 kernel: [382123.064281] Oops: [#6] SMP Mar 6 22:31:50 wp1 kernel: [382123.064516] last sysfs file: /sys/module/drbd/parameters/cn_idx Mar 6 22:31:50 wp1 kernel: [382123.064516] CPU 1 Mar 6 22:31:50 wp1 kernel: [382123.064516] Modules linked in: ocfs2 jbd2 quota_tree drbd lru_cache cn ocfs2_dlmfs ocfs2_stack_o2cb ocfs2_dlm ocfs2_nodemanager ocfs2_stackglue configfs ip6t_REJECT nf_conntrack_ipv6 ip6table_filter ip6_tables ipt_REJECT xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack iptable_filter ip_tables x_tables loop i2c_piix4 snd_pcm i2c_core snd_timer snd soundcore evdev button snd_page_alloc psmouse pcspkr serio_raw processor virtio_balloon ext3 jbd mbcache dm_mod ata_generic uhci_hcd ehci_hcd ata_piix libata usbcore virtio_blk floppy virtio_net nls_base scsi_mod virtio_pci virtio_ring virtio thermal thermal_sys [last unloaded: scsi_wait_scan] Mar 6 22:31:50 wp1 kernel: [382123.064516] Pid: 11487, comm: sshd Tainted: G D2.6.32-5-amd64 #1 Bochs Mar 6 22:31:50 wp1 kernel: [382123.064516] RIP: 0010:[810e7c50] [810e7c50] __kmalloc+0xd2/0x141 Mar 6 22:31:50 wp1 kernel: [382123.064516] RSP: 0018:88021dd2fd88 EFLAGS: 00010002 Mar 6 22:31:50 wp1 kernel: [382123.064516] RAX: RBX: 0002 RCX: 0010 Mar 6 22:31:50 wp1 kernel: [382123.064516] RDX: 880008c92070 RSI: 8020 RDI: 81269a88 Mar 6 22:31:50 wp1 kernel: [382123.064516] RBP: 0046 R08: 74f4f75f R09: 7f7636f24d31 Mar 6 22:31:50 wp1 kernel: [382123.064516] R10: R11: 81152d1d R12: 81455200 Mar 6 22:31:50 wp1 kernel: [382123.064516] R13: 8020 R14: 8020 R15: 0010 Mar 6 22:31:50 wp1 kernel: [382123.064516] FS: 7f7636eb77c0() GS:880008c8() knlGS: Mar 6 22:31:50 wp1 kernel: [382123.064516] CS: 0010 DS: ES: CR0: 80050033 Mar 6 22:31:50 wp1 kernel: [382123.064516] CR2: 0002 CR3: 00021b78f000 CR4: 06e0 Mar 6 22:31:50 wp1 kernel: [382123.064516] DR0: DR1: DR2: Mar 6 22:31:50 wp1 kernel: [382123.064516] DR3: DR6: 0ff0 DR7: 0400 Mar 6 22:31:50 wp1 kernel: [382123.064516] Process sshd (pid: 11487, threadinfo 88021dd2e000, task 88021cf1cdb0) Mar 6 22:31:50 wp1 kernel: [382123.064516] Stack: Mar 6 22:31:50 wp1 kernel: [382123.064516] 88021eef9098 81269a88 00101e1bb7a0 0001 Mar 6 22:31:50 wp1 kernel: [382123.064516] 0 88021fc0b000 0001 0001 0010 Mar 6 22:31:50 wp1 kernel: [382123.064516] 0 2cdf 81269a88 Mar 6 22:31:50 wp1 kernel: [382123.064516] Call Trace: Mar 6 22:31:50 wp1 kernel: [382123.064516] [81269a88] ? nl_pid_hash_rehash+0x49/0xf1 Mar 6 22:31:50 wp1 kernel: [382123.064516] [81269a88] ? nl_pid_hash_rehash+0x49/0xf1 Mar 6 22:31:50 wp1 kernel: [382123.064516] [8126a513] ? netlink_insert+0xbc/0x123 Mar 6 22:31:50 wp1 kernel: [382123.064516] [8126a619] ? netlink_autobind+0x9f/0xbc Mar 6 22:31:50 wp1 kernel: [382123.064516] [8126ab94] ? netlink_bind+0x82/0x179 Mar 6 22:31:50 wp1 kernel: [382123.064516] [812419c7] ? sys_bind+0x7a/0xb9 Mar 6 22:31:50 wp1 kernel: [382123.064516] [812fe0b6] ? do_page_fault+0x2e0/0x2fc Mar 6 22:31:50 wp1 kernel: [382123.064516] [81010b42] ? system_call_fastpath+0x16/0x1b Mar 6 22:31:50 wp1 kernel: [382123.064516] Code: fa 66 0f 1f 44 00 00 65 8b 04 25 a8 e3 00 00 48 98 49 8b 94 c4 f0 02 00 00 8b 4a 18 89 4c 24 14 48 8b 1a 48 85 db 74 0c 8b 42 14 48 8b 04 c3 48 89 02 eb 19 48 8b 4c 24 08 49 89 d0 44 89 ee 83 Mar 6 22:31:50 wp1 kernel: [382123.064516] RIP [810e7c50] __kmalloc+0xd2/0x141 Mar 6 22:31:50 wp1 kernel: [382123.064516]
Bug#610530: ocfs2-tools: BUG at fs/ocfs2/dlm/dlmmaster.c:2226! invalid opcode
reassign 610530 linux-2.6 thanks The bug report you submitted is a kernel bug, so I am reassigning it to the linux-2.6 package. Also, expect the severity of your bug to be lowered, I doubt it will remain critical. Regards, Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#598014: Version 1.6 is important, not a whishlist
I am pretty sure the problems you describe are related to the kernel code, not the userspace tools. I hope that the freeze won't be a no-go for this request otherwise we'll have OCFS2 in squeeze that will not be production ready. The whole concept of the freeze is that new versions of packages don't migrate to testing, so for sure ocfs2-tools 1.6.x won't be making it into squeeze. I will however be uploading ocfs2-tools 1.6.3 to unstable once I fix some build issues I am encountering. Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#587287: mkfs.ocfs2 depends on libdlm-dev
It looks as though there are two issues here: a/ My understanding is that upstream does a dlopen() on libdlm_lt.so in order to be able to use libdlm_lt.so.2 or libdlm_lt.so.3 depending on the system. On Debian/squeeze or better, the package in use is libdlm3, so libo2dlm should dlopen() libdlm_lt.so.3 directly instead of libdlm_lt.so, so that we only need the libdlm3 package, not libdlm3-dev. I have added a patch for the next upload of ocfs2-tools which does just that: http://svn.debian.org/wsvn/collab-maint/deb-maint/ocfs2-tools/trunk/debian/patches/libo2dlm-dlopen-libdlm_lt.patch b/ libdlm3 is only required when using a userspace cluster stack instead of the built-in o2cb. Therefore, having a ocfs2-tools *depend* on libdlm3 is probably wrong. I think that making ocfs2-tools-cman and ocfs2-tools-pacemaker depend on libdlm3 is probably the way to go. Any thoughts on this Joel? Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#586778: ocfs2-tools 1.4.4 is on its way
tags 586784 + pending tags 586778 + pending tags 457803 + pending thanks I have uploaded ocfs2-tools 1.4.4 today but it will sit in the NEW queue for a bit, because I have put pacemaker and cman support in separate binary packages: http://ftp-master.debian.org/new/ocfs2-tools_1.4.4-1.html Cheers, Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#582716: Vincent's solution works for me
Just a me too to say that applying the patch suggested by Vincent Ordy got things working again for me. Cheers, Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#579947: kdevelop: Please upgrade KDevelop to the stable 4 version
Now KDevelop 4 is released [0], could you please upload it to sid, that would be really great for all the KDE users :) I will be uploading it as soon as kdevplatform 1.0.0 goes in (uploaded this morning). Cheers, Jeremy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#279422: ITP python-nltk: status?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Robin, I am no longer working on the package, I tried uploading it back in May but it got rejected because the license/copyright holders of some of the files was not clear. Some of the problematic files: - what is the license for nltk/app/nemo_app.py, nltk/mis/chomsky.py nltk/mis/babelfish.py? what is the license for nltk/mis/chomsky.py? The licnse for nltk/decorators.py is missing from debian/copyright. ntlk/etree copyright is noted but seems to me to carry a different license (see __init__.py). nltk/test/coverage.py has a license not mentioned in debian/copyright - Feel free to take over the bug. Cheers, Jeremy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAktunh0ACgkQ4mJJZqJp2Sd8MwCeNIhmKk6JdCDgdnz+c3TCzB9r H5IAn3SRK2tVt134i+ullsuucYAiw5iF =fFjp -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#549543: Bug caused by my.cnf
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 After probing around some more, it would seem the bug is triggered if you have a MySQL configuration file (~/.my.cnf). If I get rid of the MySQL config file, Amarok's collection works fine. FYI, my ~/my.cnf looks like: [client] database = somedb user = someuser password = somepassword Jeremy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkrJisgACgkQ4mJJZqJp2SdE+QCgh9TzdWPq0wLGBtX+Ip3Cb36l zK4AoMNYsWJmYS+//S1u2zNXyCqkPRE+ =k213 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#533620: Re-assign 533620 to linux-2.6
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 reassign 533620 linux-2.6 thanks The problem described in bug 533620 is a kernel bug, so I am re-assigning it to the linux-2.6 package. What version of the kernel were you running when you experienced the crash? Jeremy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkpRg+AACgkQ4mJJZqJp2ScVygCgvlIrS8qdyp4ov8lc3ibHCxPj 3PMAoMY9WNtv07RBUiJZgBmliCkq6PfY =hjiT -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
