Bug#704190: ltsp-server-standalone: ltsp-build-client fails because of error in packages downloading stage

[Peter Tuharsky]

Package: ltsp-server-standalone
Version: 5.4.2-5
Severity: grave
Justification: renders package unusable

Running the ltsp-build-client --arch i386
dosen't generate valid client image, thus rendering the ltsp package useless. I
suspect that there is either problem with missing apt commandline parameter, or
with invalid GPG signature, or both.

Details:
When the command reaches the apt stage, it reports:

Get:1 http://security.debian.org wheezy/updates Release.gpg [836 B]
Get:2 http://security.debian.org wheezy/updates Release [101 kB]
Get:3 http://cdn.debian.net wheezy Release.gpg [836 B]
Hit http://cdn.debian.net wheezy Release
Ign http://cdn.debian.net wheezy Release
Get:4 http://cdn.debian.net wheezy/main i386 Packages/DiffIndex [7,876 B]
Get:5 http://security.debian.org wheezy/updates/main i386 Packages [3,660 B]
Get:6 http://cdn.debian.net wheezy/main Translation-en [3,854 kB]
Ign http://security.debian.org wheezy/updates/main Translation-en_US
Ign http://security.debian.org wheezy/updates/main Translation-en
Ign http://cdn.debian.net wheezy/main Translation-en_US
Fetched 3,968 kB in 4s (932 kB/s)
Reading package lists... Done
W: GPG error: http://cdn.debian.net wheezy Release: The following signatures
were invalid: BADSIG AED4B06F473041FA Debian Archive Automatic Signing Key
(6.0/squeeze) 
Reading package lists... Done
Building dependency tree... Done
The following extra packages will be installed:
  acl adduser alsa-base alsa-utils busybox console-setup console-setup-linux
  consolekit cpio cpp cpp-4.7 cron cryptsetup cryptsetup-bin cups-bsd
  cups-client cups-common dbus dmsetup dmz-cursor-theme exim4 exim4-base
  exim4-config exim4-daemon-light file fontconfig fontconfig-config
  freerdp-x11 fuse gettext-base gstreamer0.10-pulseaudio gtk2-engines
  heirloom-mailx hicolor-icon-theme ifupdown initramfs-tools inputattach
  iproute iso-codes kbd keyboard-configuration klibc-utils kmod krb5-locales
  ldm ldm-themes libasound2 libasound2-plugins libasprintf0c2 libasyncns0
  libatk1.0-0 libatk1.0-data libatm1 libaudit0 libavahi-client3
  libavahi-common-data libavahi-common3 libavcodec53 libavutil51 libbsd0
  libcairo2 libcap2 libck-connector0 libclass-isa-perl libcrypt-passwdmd5-perl
  libcryptsetup4 libcups2 libcupsimage2 libdatrie1 libdbus-1-3
  libdbus-glib-1-2 libdevmapper1.02.1 libdirac-encoder0 libdrm-intel1
  libdrm-nouveau1a libdrm-radeon1 libdrm2 libedit2 libexif12 libexpat1 libffi5
  libfftw3-3 libfile-copy-recursive-perl libflac8 libfontconfig1 libfontenc1
  libfreerdp-plugins-standard libfreerdp1 libfreetype6 libfribidi0 libfs6
  libfuse2 libgcrypt11 libgd2-xpm libgdbm3 libgdk-pixbuf2.0-0
  libgdk-pixbuf2.0-common libgl1-mesa-dri libgl1-mesa-glx libglapi-mesa
  libglib2.0-0 libglib2.0-data libglu1-mesa libgmp10 libgnutls26 libgomp1
  libgpg-error0 libgphoto2-2 libgphoto2-l10n libgphoto2-port0 libgpm2 libgsm1
  libgssapi-krb5-2 libgstreamer-plugins-base0.10-0 libgstreamer0.10-0
  libgtk2.0-0 libgtk2.0-bin libgtk2.0-common libice6 libieee1284-3
  libjack-jackd2-0 libjasper1 libjbig0 libjpeg8 libjson0 libk5crypto3
  libkeyutils1 libklibc libkmod2 libkrb5-3 libkrb5support0 libldap-2.4-2
  liblockfile-bin liblockfile1 libltdl7 libmagic1 libmp3lame0 libmpc2 libmpfr4
  libmtdev1 libncursesw5 libnewt0.52 libogg0 libopenjpeg2 liborc-0.4-0
  libp11-kit0 libpam-ck-connector libpango1.0-0 libpci3 libpciaccess0 libpcre3
  libpixman-1-0 libpng12-0 libpolkit-gobject-1-0 libpopt0 libprocps0 libpulse0
  libsamplerate0 libsane libsane-common libsane-extras libsane-extras-common
  libsasl2-2 libsasl2-modules libschroedinger-1.0-0 libsm6 libsndfile1
  libspeex1 libspeexdsp1 libsqlite3-0 libssl1.0.0 libswitch-perl
  libsystemd-daemon0 libsystemd-login0 libtalloc2 libtasn1-3 libtdb1
  libthai-data libthai0 libtheora0 libtiff4 libudev0 libusb-1.0-0 libutempter0
  libv4l-0 libv4lconvert0 libva1 libvorbis0a libvorbisenc2 libvpx1
  libwbclient0 libwebrtc-audio-processing-0 libwrap0 libx11-6 libx11-data
  libx11-xcb1 libx264-123 libxau6 libxaw7 libxcb-dri2-0 libxcb-glx0
  libxcb-render0 libxcb-shape0 libxcb-shm0 libxcb-util0 libxcb1 libxcomposite1
  libxcursor1 libxdamage1 libxdmcp6 libxext6 libxfixes3 libxfont1 libxft2
  libxi6 libxinerama1 libxkbfile1 libxml2 libxmu6 libxmuu1 libxpm4 libxrandr2
  libxrender1 libxt6 libxtst6 libxv1 libxvidcore4 libxvmc1 libxxf86dga1
  libxxf86vm1 lockfile-progs logrotate lsb-release lsof ltsp-client-core
  ltspfsd ltspfsd-core mdetect mime-support mkelfimage mtools nbd-client
  netbase netcat-traditional ntpdate numlockx openssh-blacklist
  openssh-blacklist-extra openssh-client pciutils perl perl-modules procps
  psmisc pulseaudio pulseaudio-module-x11 pulseaudio-utils python
  python-daemon python-lockfile python-minimal python-serial python-support
  python2.7 python2.7-minimal rsyslog rtkit samba-common samba-common-bin
  sane-utils sgml-base shared-mime-info smbclient sshfs syslinux
  syslinux-common tcpd tftp-hpa ttf-dejavu-core ucf udev update-inetd usbutils
  whiptail x11-app

Processed: found 704042 in 1:1.4.4-3

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 704042 1:1.4.4-3
Bug #704042 {Done: John Paul Adrian Glaubitz } 
[mongodb] CVE-2013-1892 -- mongodb: Remote shell access via run method's use of 
native_helper
Marked as found in versions mongodb/1:1.4.4-3.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
704042: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704042
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#704114: asterisk: asterisk security advisories: AST-2013-001 / AST-2013-002 / AST-2013-003

[Salvatore Bonaccorso]

Hi Tzafrir

On Thu, Mar 28, 2013 at 09:37:30AM +0200, Tzafrir Cohen wrote:
> On Thu, Mar 28, 2013 at 06:23:32AM +0100, Salvatore Bonaccorso wrote:
> > Package: asterisk
> > Severity: grave
> > Tags: security patch upstream
> > 
> > Hi,
> > 
> > the following vulnerabilities were published for asterisk.
> > 
> > CVE-2013-2685[0]:
> > Buffer Overflow Exploit Through SIP SDP Header
> > 
> > CVE-2013-2686[1]:
> > Denial of Service in HTTP server
> > 
> > CVE-2013-2264[2]:
> > Username disclosure in SIP channel driver
> > 
> > For CVE-2013-2685 the tracker[3] mentions only 1.11.x. Could you
> > doublecheck that squeeze, testing and wheezy are not affected?
> 
> According to the Upstream advisories, both are in effect for 1.8 .
> Didn't yet check backporting it (to our 1.8 in Testing/Unstable) and to
> 1.6.2 in Stable.

Thank you for confirming! (note my above comment was related only to
one of the issues, CVE-2013-2685).

Could you prepare updates to be included via unstable in wheezy?

Thank you for your work!

Regards,
Salvatore


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: tagging 704174, found 704174 in 1:9.7.3.dfsg-1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 704174 + security
Bug #704174 {Done: Michael Gilbert } [src:bind9] 
CVE-2013-2266
Added tag(s) security.
> found 704174 1:9.7.3.dfsg-1
Bug #704174 {Done: Michael Gilbert } [src:bind9] 
CVE-2013-2266
Marked as found in versions bind9/1:9.7.3.dfsg-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
704174: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704174
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#704174: marked as done (CVE-2013-2266)

[Debian Bug Tracking System]

Your message dated Fri, 29 Mar 2013 01:47:48 +
with message-id 
and subject line Bug#704174: fixed in bind9 1:9.8.4.dfsg.P1-6+nmu1
has caused the Debian Bug report #704174,
regarding CVE-2013-2266
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
704174: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704174
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:bind9
Version: 1:9.8.4.dfsg.P1-6
Severity: grave

http://cxsecurity.com/issue/WLB-2013030255
https://kb.isc.org/article/AA-00879

This bug also affects all programs which use libdns.

Regards,
-- 
Wolfgang Walter
--- End Message ---
--- Begin Message ---
Source: bind9
Source-Version: 1:9.8.4.dfsg.P1-6+nmu1

We believe that the bug you reported is fixed in the latest version of
bind9, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 704...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Gilbert  (supplier of updated bind9 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 29 Mar 2013 00:47:25 +
Source: bind9
Binary: bind9 bind9utils bind9-doc host bind9-host libbind-dev libbind9-80 
libdns88 libisc84 liblwres80 libisccc80 libisccfg82 dnsutils lwresd
Architecture: source all amd64
Version: 1:9.8.4.dfsg.P1-6+nmu1
Distribution: unstable
Urgency: high
Maintainer: LaMont Jones 
Changed-By: Michael Gilbert 
Description: 
 bind9  - Internet Domain Name Server
 bind9-doc  - Documentation for BIND
 bind9-host - Version of 'host' bundled with BIND 9.X
 bind9utils - Utilities for BIND
 dnsutils   - Clients provided with BIND
 host   - Transitional package
 libbind-dev - Static Libraries and Headers used by BIND
 libbind9-80 - BIND9 Shared Library used by BIND
 libdns88   - DNS Shared Library used by BIND
 libisc84   - ISC Shared Library used by BIND
 libisccc80 - Command Channel Library used by BIND
 libisccfg82 - Config File Handling Library used by BIND
 liblwres80 - Lightweight Resolver Library used by BIND
 lwresd - Lightweight Resolver Daemon
Closes: 699145 704174
Changes: 
 bind9 (1:9.8.4.dfsg.P1-6+nmu1) unstable; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * Fix cve-2012-5689: issue in nameservers using DNS64 to perform a 
 lookup for a record with an A record overwrite rule in a Response Policy
 Zone (closes: #699145).
   * Fix cve-2013-2266: issues in regular expression handling (closes: #704174).
Checksums-Sha1: 
 f457875fbf5d57fe6f0f81f81a88503bfc302a80 3304 bind9_9.8.4.dfsg.P1-6+nmu1.dsc
 2564dd0178d84acb34e98a3435d0ddffa6e6f730 672591 
bind9_9.8.4.dfsg.P1-6+nmu1.diff.gz
 b65354a9acf91e94e66da504f4ecef3741135cce 364768 
bind9-doc_9.8.4.dfsg.P1-6+nmu1_all.deb
 ce69383565d451b1612687230bfe3092834b9d92 19994 
host_9.8.4.dfsg.P1-6+nmu1_all.deb
 d84084bf4d74b1da96793d6fb5e147992630d303 369032 
bind9_9.8.4.dfsg.P1-6+nmu1_amd64.deb
 2d32f80f456aa862b6a0edc4a17b539c3015ad7a 125078 
bind9utils_9.8.4.dfsg.P1-6+nmu1_amd64.deb
 2029c70d2fea3612d1050324ea9057a30e9a7c60 71148 
bind9-host_9.8.4.dfsg.P1-6+nmu1_amd64.deb
 4277a5a50e5ec6b2b351b491d585f2ce32986eb9 1579578 
libbind-dev_9.8.4.dfsg.P1-6+nmu1_amd64.deb
 036d6da5c9caea1a1c875a813472d16dd7827ea8 41672 
libbind9-80_9.8.4.dfsg.P1-6+nmu1_amd64.deb
 e1730d8cb8d3f13dd41b2af89b13e980f37d8f9d 748172 
libdns88_9.8.4.dfsg.P1-6+nmu1_amd64.deb
 da9e94e5f629afff3340a07004bcdad4788689cd 182766 
libisc84_9.8.4.dfsg.P1-6+nmu1_amd64.deb
 b15901bd1d0645c67045bbe4d7d477e2797dbcbf 54666 
liblwres80_9.8.4.dfsg.P1-6+nmu1_amd64.deb
 d4e2ea1d8abcbe797ff2e0d84bf58e4090caca86 35310 
libisccc80_9.8.4.dfsg.P1-6+nmu1_amd64.deb
 44272ba792ca15d5db5c45b465455bf53932ad81 62792 
libisccfg82_9.8.4.dfsg.P1-6+nmu1_amd64.deb
 cea72bd7576339d45608e848a3fc025abbfe0698 162284 
dnsutils_9.8.4.dfsg.P1-6+nmu1_amd64.deb
 654912b28caa421041b5c34a91cf3526164c194d 248726 
lwresd_9.8.4.dfsg.P1-6+nmu1_amd64.deb
Checksums-Sha256: 
 943e83e3c2ffdff47632d1117485d159b46c0782e32d37bdf4d2ce126d0383ab 3304 
bind9_9.8.4.dfsg.P1-6+nmu1.dsc
 326ff1b62ef9ad5d4f33de7c43f914a782ebe43097a18636f49d99f243ea1bec 672591 
bind9_9.8.4.dfsg.P1-6+nmu1.diff.gz
 c0e942632f274fb34f7fbeea7a194fbfef846a989a7

Bug#704174: Security nmu

[Michael Gilbert]

Hi,

I've uploaded an nmu fixing these issues.  Please see attached patch.

Best wishes,
Mike


bind9.patch
Description: Binary data

Bug#703726: [PATCH] libcogl12: SIGSEGV in cogl_onscreen_add_frame_callback

[Daniel Vacek]

Hi,

  I can confirm the bug and this patch fixes it.

  Basicaly it crashed in cogl_onscreen_add_frame_callback because
macro COGL_TAILQ_REMOVE in cogl_onscreen_remove_frame_callback
incorrectly removed an element from queue and corrupted the queue and
tail pointer.

--- a/cogl/cogl-queue.h 2011-08-12 15:45:58.0 +0200
+++ b/cogl/cogl-queue.h 2013-03-29 01:06:20.049909221 +0100
@@ -614,14 +614,18 @@
 COGL_QMD_SAVELINK(oldprev, (elm)->field.tqe_prev);  \
 COGL_QMD_TAILQ_CHECK_NEXT(elm, field);  \
 COGL_QMD_TAILQ_CHECK_PREV(elm, field);  \
-if ((COGL_TAILQ_NEXT((elm), field)) != NULL)\
+(*(elm)->field.tqe_prev)->field.tqe_next =  \
+COGL_TAILQ_NEXT((elm), field);  \
+if ((COGL_TAILQ_NEXT((elm), field)) != NULL) {  \
 COGL_TAILQ_NEXT((elm), field)->field.tqe_prev = \
 (elm)->field.tqe_prev;  \
-else {  \
+if (COGL_TAILQ_NEXT((elm), field)->field.tqe_next == NULL)  \
+(head)->tqh_last =  \
+&(*(elm)->field.tqe_prev)->field.tqe_next;  \
+} else {\
 (head)->tqh_last = (elm)->field.tqe_prev;   \
 COGL_QMD_TRACE_HEAD(head);  \
 }   \
-*(elm)->field.tqe_prev = COGL_TAILQ_NEXT((elm), field); \
 COGL_TRASHIT(*oldnext); \
 COGL_TRASHIT(*oldprev); \
 COGL_QMD_TRACE_ELEM(&(elm)->field); \

--nX


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#704154: vdr - Fails if started without any of CAP_SYS_TIME, CAP_SYS_NICE or CAP_NET_RAW

[Tobias Grimm]

I'm not sure, if this qualifies for a "serious" severity, turning this 
into an RC bug.


You can still run VDR as root with "-u root" (or USER=root in 
/etc/default/vdr).


CAP_SYS_TIME is required to update the system time with the time from the 
DVB broadcasters. This behavior is optional, disabled by default and if 
setting the time fails, this just gets logged to the syslog.


So I guess, failing at CAP_SYS_TIME can be ignored.

CAP_SYS_NICE is required to set the thread priority. I think VDR is 
correct here to exit with an error level if CAP_SYS_NICE is not available.


I'm not sure why CAP_NET_RAW is required. The only networking stuff 
happening is at the SVDRP interface.


It might be that this was added to allow plugins like Streamdev to have 
raw network access.


What do you suggest to solve this? Ignore CAP_SYS_TIME if it can't be set?

Tobias


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#703468: linux-image-3.2.0-4-amd64 fails to boot on apple iMac

[Bob Bib]

Thu, 28 Mar 2013 16:52:17 +1100 from Geoff Crompton:
> This time I did take a photo of the screen when it crashes. It's
> unfortunately a little blurry.

The following string is still recognizable:
i915_gem_init_ppgtt+0x93/0x16c [i915]

Looks like something's bad with Intel graphics driver...



Best wishes, Bob

Processed: limit source to request-tracker4, tagging 704107

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> #request-tracker4 (4.0.7-5) UNSTABLE; urgency=low
> #
> #  * Closes: #704107
> #
> limit source request-tracker4
Limiting to bugs with field 'source' containing at least one of 
'request-tracker4'
Limit currently set to 'source':'request-tracker4'

> tags 704107 + pending
Bug #704107 [request-tracker4] request-tracker4: GPG data stored in /var/cache
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
704107: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704107
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: fixed

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> fixed 704025 olsrd/0.6.2-2.1
Bug #704025 {Done: Hans-Christoph Steiner } [olsrd] olsrd does 
not connect with others on amd64
Marked as fixed in versions olsrd/0.6.2-2.1.
> fixed 704025 olsrd/0.6.3-5.1
Bug #704025 {Done: Hans-Christoph Steiner } [olsrd] olsrd does 
not connect with others on amd64
Marked as fixed in versions olsrd/0.6.3-5.1.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
704025: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704025
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#704025: marked as done (olsrd does not connect with others on amd64)

[Debian Bug Tracking System]

Your message dated Thu, 28 Mar 2013 15:54:51 -0700
with message-id <5154ca3b.1050...@eds.org>
and subject line close
has caused the Debian Bug report #704025,
regarding olsrd does not connect with others on amd64
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
704025: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704025
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: olsrd
Version: 0.6.2-2
Severity: grave
Tags: patch pending upstream fixed-upstream wheezy

The net_output() function indirectly uses the stack variables dst and dst6
outside of the scope they're declared in, this might leads to olsr_sendto()
being called with a corrupted destination sockaddr_in.

This failure condition can be observed in the log, olsrd will continuosly
print "sendto(v4): Invalid Argument" or a similar message. On ARM it has been
reported to result in "Unsupported Address Family".

This bug became apparant on a custon OpenWrt x86_64 uClibc target using the
Linaro GCC 4.7-2012.04 compiler, it has been reported for an unspecified ARM
target as well.

The offending code seems to be unchanged since 2008 and it does not cause
issues on 32bit systems and/or with older (Linaro) GCC versions, but the
compiler used in our tests seems to perform more aggressive optimizations
leading to a stack corruption.

full thread and discussion here:
https://lists.olsr.org/pipermail/olsr-dev/2013-March/006718.html
(self signed cert SHA1:
6D 93 1C 9C C3 7C 67 7A 44 A8 C7 B0 2F E7 44 C7 48 D6 27 49)

fix is already included upstream in v0.6.4:
http://olsr.org/git/?p=olsrd.git;a=commitdiff;h=f4d250ad4fad5fcfe5b5feaac3f3e121adef3fba

I marked it 'grave' because it makes olsrd non-functional on platforms like 
amd64.
From f4d250ad4fad5fcfe5b5feaac3f3e121adef3fba Mon Sep 17 00:00:00 2001
From: Jo-Philipp Wich 
Date: Fri, 22 Jun 2012 03:17:59 +0200
Subject: [PATCH] olsrd: fix stack corruption in net_output()

The net_output() function indirectly uses the stack variables dst and dst6
outside of the scope they're declared in, this might leads to olsr_sendto()
being called with a corrupted destination sockaddr_in.

This failure condition can be observed in the log, olsrd will continuosly
print "sendto(v4): Invalid Argument" or a similar message. On ARM it has been
reported to result in "Unsupported Address Family".

This bug became apparant on a custon OpenWrt x86_64 uClibc target using the
Linaro GCC 4.7-2012.04 compiler, it has been reported for an unspecified ARM
target as well.

The offending code seems to be unchanged since 2008 and it does not cause
issues on 32bit systems and/or with older (Linaro) GCC versions, but the
compiler used in our tests seems to perform more aggressive optimizations
leading to a stack corruption.
---
 src/net_olsr.c |4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/net_olsr.c b/src/net_olsr.c
index 7d85f4f..66e103d 100644
--- a/src/net_olsr.c
+++ b/src/net_olsr.c
@@ -336,6 +336,8 @@ net_output(struct interface *ifp)
 {
   struct sockaddr_in *sin = NULL;
   struct sockaddr_in6 *sin6 = NULL;
+  struct sockaddr_in dst;
+  struct sockaddr_in6 dst6;
   struct ptf *tmp_ptf_list;
   union olsr_packet *outmsg;
   int retval;
@@ -354,7 +356,6 @@ net_output(struct interface *ifp)
   outmsg->v4.olsr_packlen = htons(ifp->netbuf.pending);
 
   if (olsr_cnf->ip_version == AF_INET) {
-struct sockaddr_in dst;
 /* IP version 4 */
 sin = (struct sockaddr_in *)&ifp->int_broadaddr;
 
@@ -365,7 +366,6 @@ net_output(struct interface *ifp)
 if (sin->sin_port == 0)
   sin->sin_port = htons(olsr_cnf->olsrport);
   } else {
-struct sockaddr_in6 dst6;
 /* IP version 6 */
 sin6 = (struct sockaddr_in6 *)&ifp->int6_multaddr;
 /* Copy sin */
-- 
1.7.9.5



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
closing, we'll settle for 0.6.2-2.1
--- End Message ---

Bug#703852: [Pkg-mediawiki-devel] Bug#703852: [mediawiki] mw{en,dis}ext ineffective for new installs

[Filipus Klutiero]

On 2013-03-25 05:43, Thorsten Glaser wrote:

tags 703852 + pending
thanks

On Sun, 24 Mar 2013, Filipus Klutiero wrote:


The scripts mwenext and mwdisext are supposed to respectively enable and
disable a MediaWiki extension. But this doesn't work anymore on new installs
following
http://anonscm.debian.org/viewvc/pkg-mediawiki?view=revision&revision=261

Oh.


Although most of debian_specific_config.patch may have been merged the
upstream, the last part hasn't. It is needed to load
/etc/mediawiki-extensions/extensions.php, which is the basis of the extensions
mechanism.

Thanks, added it back (for now, in SVN).


Thanks



I recommend that the snippet above be restored, but in system files rather
than in LocalSettings.php. The snippet is necessary for the Debian
mediawiki-extensions system to work, so it is not local configuration.

No, LocalSettings.php is the place this *must* go (which is also
the reason e.g. I didn’t notice it earlier, as the FusionForge
LocalSettings contain this inclusion) because it doesn’t use the
require_once statement. Adding it *also* in some other place
would include it twice, which *will* break existing installations,
both these where it’s part of the admin’s setup and these where
it’s part of the code (such as fusionforge-plugin-mediawiki).
Yeah, that’s sad.

Maybe we should note this in NEWS.Debian or something? jmw?


There's a very simple solution to that which would solve even more 
problems. Unfortunately, it requires a larger change.
/etc/mediawiki-extensions/extensions.php is not a "configuration file", 
but rather a file which has loading configuration files as its role. 
Therefore, it should not be in /etc/. By moving it in the codebase and 
forcing its inclusion in the main codebase (or just adding its content 
to a setup file), we would make sure the extensions system keeps working 
no matter how the machine is configured.



By the way, the extensions list needs an update at least for Interwiki.

Which list, where?


The list of extensions in 
/etc/mediawiki-extensions/extensions-available/ has nothing for 
Interwiki (except a symlink to its predessors, SpecialInterwiki).



--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: re: libseccomp-dev - No static library

[Debian Bug Tracking System]

Processing control commands:

> severity -1 wishlist
Bug #704155 [libseccomp-dev] libseccomp-dev - No static library
Severity set to 'wishlist' from 'serious'

-- 
704155: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704155
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#704155: libseccomp-dev - No static library

[Michael Gilbert]

control: severity -1 wishlist

> The libseccomp-dev package does not include a static library.

That doesn't violate policy.

Best wishes,
Mike


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#661419: marked as done (krusader: Crash at start with 'floating point exception' after update)

[Debian Bug Tracking System]

Your message dated Fri, 29 Mar 2013 08:52:12 +1100
with message-id <201303290852.18001.m...@purcell.id.au>
and subject line Re: Bug#661419: krusader: Crash at start with 'floating point 
exception' after update
has caused the Debian Bug report #661419,
regarding krusader: Crash at start with 'floating point exception' after update
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
661419: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661419
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: krusader
Version: 1:2.4.0~beta1+git76+de1ea35-1
Severity: grave
Justification: renders package unusable

After update krusader crash with 'floater pointer exception'.

Data from crashlog:

Application: Krusader (krusader), signal: Floating point exception
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f9db9228760 (LWP 8471))]

Thread 2 (Thread 0x7f9d9bc5b700 (LWP 8472)):
#0  0x787ff8de in ?? ()
#1  0x7f9daec48e86 in clock_gettime () from /lib/x86_64-linux-gnu/librt.so.1
#2  0x7f9db46e7964 in ?? () from /usr/lib/libQtCore.so.4
#3  0x7f9db47a963d in ?? () from /usr/lib/libQtCore.so.4
#4  0x7f9db47a9973 in ?? () from /usr/lib/libQtCore.so.4
#5  0x7f9db47a83ec in ?? () from /usr/lib/libQtCore.so.4
#6  0x7f9db47a8495 in ?? () from /usr/lib/libQtCore.so.4
#7  0x7f9db0027672 in g_main_context_prepare () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x7f9db002846d in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7f9db0028a99 in g_main_context_iteration () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x7f9db47a8e96 in 
QEventDispatcherGlib::processEvents(QFlags) () 
from /usr/lib/libQtCore.so.4
#11 0x7f9db477d492 in 
QEventLoop::processEvents(QFlags) () from 
/usr/lib/libQtCore.so.4
#12 0x7f9db477d68f in 
QEventLoop::exec(QFlags) () from 
/usr/lib/libQtCore.so.4
#13 0x7f9db469530f in QThread::exec() () from /usr/lib/libQtCore.so.4
#14 0x7f9db476035f in ?? () from /usr/lib/libQtCore.so.4
#15 0x7f9db4697cf5 in ?? () from /usr/lib/libQtCore.so.4
#16 0x7f9db1956b50 in start_thread () from 
/lib/x86_64-linux-gnu/libpthread.so.0
#17 0x7f9db395a90d in clone () from /lib/x86_64-linux-gnu/libc.so.6
#18 0x in ?? ()

Thread 1 (Thread 0x7f9db9228760 (LWP 8471)):
[KCrash Handler]
#6  0x004578b7 in ?? ()
#7  0x00456e6a in ?? ()
#8  0x00459882 in ?? ()
#9  0x00459cd0 in ?? ()
#10 0x00463d82 in ?? ()
#11 0x00469d99 in ?? ()
#12 0x004626f7 in ?? ()
#13 0x7f9db38a0ead in __libc_start_main () from 
/lib/x86_64-linux-gnu/libc.so.6
#14 0x004503b9 in _start ()

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages krusader depends on:
ii  kdebase-runtime   4:4.6.5-1+b1
ii  libc6 2.13-26
ii  libgcc1   1:4.6.2-15
ii  libkdecore5   4:4.6.5-2+b1
ii  libkdeui5 4:4.6.5-2+b1
ii  libkfile4 4:4.6.5-2+b1
ii  libkhtml5 4:4.6.5-2+b1
ii  libkio5   4:4.6.5-2+b1
ii  libkjsapi44:4.6.5-2+b1
ii  libkonq5abi1  4:4.6.5-1
ii  libkparts44:4.6.5-2+b1
ii  libnepomuk4   4:4.6.5-2+b1
ii  libnepomukutils4  4:4.6.5-2+b1
ii  libphonon44:4.6.0.0-1
ii  libqt4-dbus   4:4.7.4-2
ii  libqt4-network4:4.7.4-2
ii  libqt4-svg4:4.7.4-2
ii  libqt4-xml4:4.7.4-2
ii  libqtcore44:4.7.4-2
ii  libqtgui4 4:4.7.4-2
ii  libsolid4 4:4.6.5-2+b1
ii  libsoprano4   2.6.0+dfsg.1-4
ii  libstdc++64.6.2-15
ii  zlib1g1:1.2.6.dfsg-2

krusader recommends no packages.

Versions of packages krusader suggests:
ii  arj
ii  ark
ii  bzip2  1.0.6-1
ii  cpio   2.11-7
ii  kdiff3 | kompare | xxdiff  
ii  kmail  
ii  konsole
ii  krename
ii  lha
ii  md5deep | cfv  
ii  okteta 
ii  p7zip  9.20.1~dfsg.1-4
ii  rpm
ii  unace  1.2b-9
ii  unrar  1:4.1.4-1
ii  unzip  6.0-5
ii  zip3.0-4

-- debconf-show fail

Bug#704025: marked as done (olsrd does not connect with others on amd64)

[Hans-Christoph Steiner]

Sigh... I give up.  We should leave 0.6.2-2.1 in wheezy and take our chances
with it.

I personally believe this kind of thing is a violation of the Debian Social
Contract #4 *"Our priorities are our users and free software*" but it seems
most people in Debian think that the policy trumps everything else.

We have been working hard on making this package work well for users, we have
been testing it widely.  We have a version of this package that we know is
working well, and it is being prevented from inclusion for many months now.
Multiple upstream devs, me included, have stated 0.6.3 is a better release for
Debian.  0.6.3-3 didn't make the freeze because of a small change which broke
on kFreeBSD, which we then quickly fixed and uploaded to unstable.  olsrd is a
minor, optional package, the risk of including our unblock request is tiny to
Debian.

But having a solid, working olsrd in Debian is very important to the people
trying to make OLSR mesh work well.  I guess we are forced to work out of
Ubuntu and let the Debian people fend for themselves.  That is not why I
became a DD... but it looks like the only option I have here...  I guess I
should take my rant to debian-private rather than the BTS.



signature.asc
Description: OpenPGP digital signature

Processed: notfound 694933 in 1.2.1.1-2

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> notfound 694933 1.2.1.1-2
Bug #694933 {Done: Joachim Breitner } [src:haskell-warp] 
haskell-warp: FTBFS: unsatisfiable build-dependency: 
libghc-blaze-builder-conduit-dev (<< 0.5)
No longer marked as found in versions haskell-warp/1.2.1.1-2.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
694933: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694933
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#704174: CVE-2013-2266

[Wolfgang Walter]

Package: src:bind9
Version: 1:9.8.4.dfsg.P1-6
Severity: grave

http://cxsecurity.com/issue/WLB-2013030255
https://kb.isc.org/article/AA-00879

This bug also affects all programs which use libdns.

Regards,
-- 
Wolfgang Walter


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: Re: Bug#696727: cheese does not start with Gtk-Warning

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 696727 important
Bug #696727 [cheese] cheese does not start with Gtk-Warning
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
696727: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696727
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#696727: cheese does not start with Gtk-Warning

[Jonathan Dowland]

severity 696727 important
thanks

(Downgrading since no evidence that it fails for the majority)

On 28 Mar 2013, at 18:56, Emilio Pozuelo Monfort  wrote:

> After that I'd try with another tool
> that doesn't use gstreamer, then we can pinpoint whether this is a gstreamer 
> bug
> or not.
Already done
> 
> I remember from when I did video integration in empathy that some webcams will
> only work once, and after that you have to unload the kernel module and load 
> it
> again for them to work. If that was the case here, the problem could be that
> cheese is not stopping them properly.

Cheese fails on first attempt after module reload without invoking any other 
webcam software first.

Thanks

--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: Back to severity important

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 703242 important
Bug #703242 [nova] Bugging issue with nova-consoleauth on newest nova build 
2012.1.1-15
Severity set to 'important' from 'grave'
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
703242: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703242
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#704025: marked as done (olsrd does not connect with others on amd64)

[John Paul Adrian Glaubitz]

On 03/28/2013 07:44 PM, Hans-Christoph Steiner wrote:


Its a bad idea to just throw this patch into the ancient version of olsrd
(0.6.2) and hope it works, olsrd has proven itself fragile to changes.  We
have a whole testing setup for working with 0.6.3-5 (and soon -6), including
deployed packages in a Launchpad PPA [2].


Which won't help here. Introducing a new upstream version won't help 
much here since the release team won't unblock the package at this point 
during the freeze.


If it's not possible to fix the package with a simple patch, the only 
proper and accepted solution for such an RC bug is removing the package 
as per policy, see [1].


Adrian

> [1] http://release.debian.org/wheezy/freeze_policy.html

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#696727: cheese does not start with Gtk-Warning

[Emilio Pozuelo Monfort]

On 03/28/2013 03:26 PM, Jonathan Dowland wrote:
> On Thu, Mar 28, 2013 at 10:21:30AM +, Jonathan Dowland wrote:
>> UI ("No device found"). Interesting stuff. I'm going to try splicing some
>> debug statements into the code to see at what point it reaches and whether
>> that helps get any further.
> 
> I've poked around a little, attached is a backtrace taken when interrupting 
> the
> spinning process. It shows the last routine executed in cheese code as
> cheese_camera_play. Poking around in the C, 
> 
> cheese_camera_play (CheeseCamera *camera)
> {
>   …
> gst_element_set_state (priv->camerabin, GST_STATE_PLAYING);
> 
> ^^
> 
> That's as far as cheese gets. So, is this a gstreamer bug? (or
> gstreamer0.10-plugins-bad)? Seems it uses 'camerabin', which has been
> deprecated in favour of 'camerabin2' in gst 0.10, and dropped by 1.0.
> Cheese moved to camerabin2 between 3.5.5 and 3.5.091.
> 

Most likely not a cheese bug; you can confirm that by trying e.g. empathy, which
will probably fail to use the webcam too. After that I'd try with another tool
that doesn't use gstreamer, then we can pinpoint whether this is a gstreamer bug
or not.

I remember from when I did video integration in empathy that some webcams will
only work once, and after that you have to unload the kernel module and load it
again for them to work. If that was the case here, the problem could be that
cheese is not stopping them properly.

Regards,
Emilio


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed (with 1 errors): reopen 704025

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reopen 704025
Bug #704025 {Done: John Paul Adrian Glaubitz } 
[olsrd] olsrd does not connect with others on amd64
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions olsrd/0.6.2-2.1 and olsrd/0.6.3-5.1.
> reopening to sync NMU work with maintainers' work
Unknown command or malformed arguments to command.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
704025: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704025
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#704025: marked as done (olsrd does not connect with others on amd64)

[Hans-Christoph Steiner]

Hey Adrian, I appreciate your willingness to contribute here, but you should
have contacted us before doing an NMU. I'm a co-maintainer of this package
with Roland Stigge, and I was directly working on this problem in the
package's SVN repo.  Also, we already have a longstanding unblock request
#689772 [1] to include the version of the package that we have been working on
since before the wheezy freeze.  This is the version that we have done all the
testing on, including as part of the Commotion Wireless project, and this is
the version that should be included in Wheezy.

Its a bad idea to just throw this patch into the ancient version of olsrd
(0.6.2) and hope it works, olsrd has proven itself fragile to changes.  We
have a whole testing setup for working with 0.6.3-5 (and soon -6), including
deployed packages in a Launchpad PPA [2].

[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689772
[2] https://launchpad.net/~guardianproject/+archive/commotion/+packages

So I propose you remove your NMU, and we work together on this issue.  As for
updating unstable, feel free to do that.  We're keeping the SVN's trunk pinned
to the wheezy 0.6.3 work until it gets accepted, but you can work out of a 
branch.



signature.asc
Description: OpenPGP digital signature

Bug#704030: marked as done (python-bcrypt: CVE-2013-1895: concurrency issue leading to auth bypass)

[Debian Bug Tracking System]

Your message dated Thu, 28 Mar 2013 18:37:34 +
with message-id 
and subject line Bug#704126: Removed package(s) from unstable
has caused the Debian Bug report #704030,
regarding python-bcrypt: CVE-2013-1895: concurrency issue leading to auth bypass
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
704030: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704030
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-bcrypt
Version: 0.1-1
Severity: important
Tags: security

Dear Maintainer,

Upstream has released an update (v0.3) which fixes a security issue, please see:

https://code.google.com/p/py-bcrypt/source/detail?r=3bc365ff43736d26ff37e9f2a4084f37b381b569
--- End Message ---
--- Begin Message ---
Version: 0.1-1+rm

Dear submitter,

as the package python-bcrypt has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see http://bugs.debian.org/704126

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@debian.org.

Debian distribution maintenance software
pp.
Ansgar Burchardt (the ftpmaster behind the curtain)--- End Message ---

Bug#704157: libvirt0 - lxc: Mounts root cgroup in container

[Bastian Blank]

Package: libvirt0
Version: 1.0.2-3
Severity: grave

The lxc support in libvirt mounts the root cgroups within the container.
Per default the guest have the permission needed to move processes out
of it's own cgroup into the root cgroup. This can evade restrictions
imposed by the device cgroup or resource restrictions.

Bastian

-- System Information:
Debian Release: 7.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.8-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#704155: libseccomp-dev - No static library

[Bastian Blank]

Package: libseccomp-dev
Version: 1.0.1-2
Severity: serious

The libseccomp-dev package does not include a static library.

Bastian

-- System Information:
Debian Release: 7.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.8-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#704154: vdr - Fails if started without any of CAP_SYS_TIME, CAP_SYS_NICE or CAP_NET_RAW

[Bastian Blank]

Package: vdr
Version: 1.7.28-1
Severity: serious

vdr tries to drop almost all capabilities except of CAP_SYS_TIME,
CAP_SYS_NICE and CAP_NET_RAW. It does this without checking the current
capability set, which may not include any of them[1], and fails hard if this
does not work.

| capget(0x20080522, 0, NULL) = 0
| capset(0x20080522, 0, {CAP_NET_RAW|CAP_SYS_NICE|CAP_SYS_TIME, 
CAP_NET_RAW|CAP_SYS_NICE|CAP_SYS_TIME, 0}) = -1 EPERM (Operation not permitted)
| write(2, "vdr: cap_set_proc failed: Operat"..., 50) = 50
| exit_group(2)   = ?

Bastian

[1]: In case of LXC, it does not include at least CAP_SYS_TIME, because it
 affects always the whole system.

-- System Information:
Debian Release: 7.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.8-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#704030: python-bcrypt: Upstream has released a security update.

[John Paul Adrian Glaubitz]

On 03/28/2013 04:51 PM, Kevin Coyner wrote:

Just saw this and would have to concur. The package has a very small
following and can be removed.


It can probably be replaced with python-passlib, can't it?

Adrian

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#704030: python-bcrypt: Upstream has released a security update.

[Kevin Coyner]

On Thu, Mar 28, 2013 at 11:52 AM, John Paul Adrian Glaubitz <
glaub...@physik.fu-berlin.de> wrote:

> On 03/28/2013 04:51 PM, Kevin Coyner wrote:
>
>> Just saw this and would have to concur. The package has a very small
>> following and can be removed.
>>
>
> It can probably be replaced with python-passlib, can't it?



I would think so but I'd have to take to take a closer look at
python-passlib.

Kevin




> python-passlib
>
> Adrian
>
>
> --
>  .''`.  John Paul Adrian Glaubitz
> : :' :  Debian Developer - glaub...@debian.org
> `. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
>   `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
>



-- 
Kevin Coyner  GnuPG key: 2048R/C85D8F71  http://rustybear.com/publickey.html

Bug#704030: python-bcrypt: Upstream has released a security update.

[Kevin Coyner]

Just saw this and would have to concur. The package has a very small
following and can be removed.

Kevin



On Thu, Mar 28, 2013 at 11:12 AM, John Paul Adrian Glaubitz <
glaub...@physik.fu-berlin.de> wrote:

> Hi,
>
> after talking with the release team, the package has now been requested to
> be removed, see [1].
>
> Adrian
>
> > [1] 
> > http://bugs.debian.org/cgi-**bin/bugreport.cgi?bug=704126
>
> --
>  .''`.  John Paul Adrian Glaubitz
> : :' :  Debian Developer - glaub...@debian.org
> `. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
>   `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
>



-- 
Kevin Coyner  GnuPG key: 2048R/C85D8F71  http://rustybear.com/publickey.html

Bug#704030: python-bcrypt: Upstream has released a security update.

[Kevin Coyner]

Adrian

Many thanks for your work in creating the patch. However, it seems to be
built against version 0.2. The version in the Debian repositories is 0.1-1,
so your patch cannot be directly applied.

I'll work on bringing the package up to date to version 0.2, and then will
apply your patch.

Thank you for your work.

Kevin


On Wed, Mar 27, 2013 at 9:10 AM, John Paul Adrian Glaubitz <
glaub...@physik.fu-berlin.de> wrote:

> I have prepared an NMU with the attached debdiff. I'd be happy to upload
> if the maintainer agrees.
>
>
> Adrian
>
> --
>  .''`.  John Paul Adrian Glaubitz
> : :' :  Debian Developer - glaub...@debian.org
> `. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
>   `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
>



-- 
Kevin Coyner  GnuPG key: 2048R/C85D8F71  http://rustybear.com/publickey.html

Bug#702573: libopenms1 - No stable ABI

[Filippo Rusconi]

Greetings, Fellow Debichemists,

> Package: libopenms1
> Version: 1.9.0-2
> Severity: serious

> OpenMS upstream does not provide a stable ABI of libOpenMS. So neither
> the patch to add one nor this package name are appropriate.

I am back to you about this bug. After a few mails exchanged with the
OpenMS crew (Oliver Kohlbacher, specifically), I ended coming out with
the following reasoning:

1 - OpenMS is a well-respected project that has an interesting user
base;

2 - While the library is functionally stable (that is, it provides
features that perform fine), it is not stable in the ABI stability
sense;

3 - In the context of Debian, ABI stability is crucial for
largely-used libraries because it avoids having to recompile all
the packages that depend on the libraries each time 
new ABI-breaking versions are released;

4 - Availability of mass spectrometry packages in Debian is almost
NULL, since my project to bring to Debichem a complete set of such
packages is still in its infancy. Therefore, at the moment, there
is not a single source package that depends on libopenms;

5 - New versions of OpenMS are released at a pretty low rate, and I
would think that this fact somehow limits the negative impact of
having ABI breakage between versions. Thus, it might be perfectly
possible to have a new soname version each time a new release is
done;

6 - The authors of OpenMS state that ABI stability of libopenms is not
their immediate priority and that they do not intend to change
anything about it;

7 - I think that, because OpenMS is a powerful library aimed at
allowing people to craft flexible mass data analysis workflows, we
should accept the impact of ABI instability in favour of providing
users with a properly-packaged library. For those present at my
FOSDEM2013 talk [0], remember that the OpenMS software
(2 libraries, 114 binaries) is huge and that the few mass
spectrometrists I spoke with about packaging it told me that they
could not even build it! I really think it is of primary
importance to have that software packaged in Debian.

[0] https://fosdem.org/2013/schedule/event/mass_spectrometry_debian/

After having said all this, I remain with a question : is this sound,
or is this totally unreasonable?

Thank you for your input on this subject.

Cheers,
Filippo

-- 
Filippo Rusconi, PhD - public crypto key C78F687C @ pgp.mit.edu
Researcher at CNRS and Debian Developer 
Author of ``massXpert'' at http://www.massxpert.org


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#702087: marked as done (UDD: vcs importer broken since PET moved to alioth)

[Debian Bug Tracking System]

Your message dated Thu, 28 Mar 2013 16:14:18 +0100
with message-id <20130328151418.ga13...@xanadu.blop.info>
and subject line Re: UDD: vcs importer broken since PET moved to alioth
has caused the Debian Bug report #702087,
regarding UDD: vcs importer broken since PET moved to alioth
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
702087: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702087
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qa.debian.org
Severity: serious
User: qa.debian@packages.debian.org
Usertags: udd

Hi,

The UDD vcs importer gathers data from PET about the status of team's
VCS repositories.

It uses a direct postgresql connection to the PET database.

Since the move to alioth, the direct postgresql connection is not
available anymore.

A example of service affected by that is the VCS column on
http://udd.debian.org/dmd.cgi

The vcs importer has been disabled in cron in the meantime.

Lucas
--- End Message ---
--- Begin Message ---
On 27/03/13 at 22:22 +0100, Andreas Tille wrote:
> Hi,
> 
> I've got confirmation that a guest account at pet.d.n was created.
> 
> I was able to connect using
> 
>   psql -h pet.debian.net -p 5432 pet guest
> 
> and
> 
>   udd@ullmann:/srv/udd.debian.org/udd$ ./update-and-run.sh vcs
> 
> seemed to work fine - at least there were no error messages.  So I
> reenabled the cron job and hope all works fine.
> 
> Please check if all is fine and close the bug after checking.

Thanks, everything seems to work fine. Closing the bug!

Lucas--- End Message ---

Bug#704030: python-bcrypt: Upstream has released a security update.

[John Paul Adrian Glaubitz]

Hi,

after talking with the release team, the package has now been requested 
to be removed, see [1].


Adrian

> [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704126

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#704025: marked as done (olsrd does not connect with others on amd64)

[Debian Bug Tracking System]

Your message dated Thu, 28 Mar 2013 14:48:41 +
with message-id 
and subject line Bug#704025: fixed in olsrd 0.6.3-5.1
has caused the Debian Bug report #704025,
regarding olsrd does not connect with others on amd64
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
704025: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704025
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: olsrd
Version: 0.6.2-2
Severity: grave
Tags: patch pending upstream fixed-upstream wheezy

The net_output() function indirectly uses the stack variables dst and dst6
outside of the scope they're declared in, this might leads to olsr_sendto()
being called with a corrupted destination sockaddr_in.

This failure condition can be observed in the log, olsrd will continuosly
print "sendto(v4): Invalid Argument" or a similar message. On ARM it has been
reported to result in "Unsupported Address Family".

This bug became apparant on a custon OpenWrt x86_64 uClibc target using the
Linaro GCC 4.7-2012.04 compiler, it has been reported for an unspecified ARM
target as well.

The offending code seems to be unchanged since 2008 and it does not cause
issues on 32bit systems and/or with older (Linaro) GCC versions, but the
compiler used in our tests seems to perform more aggressive optimizations
leading to a stack corruption.

full thread and discussion here:
https://lists.olsr.org/pipermail/olsr-dev/2013-March/006718.html
(self signed cert SHA1:
6D 93 1C 9C C3 7C 67 7A 44 A8 C7 B0 2F E7 44 C7 48 D6 27 49)

fix is already included upstream in v0.6.4:
http://olsr.org/git/?p=olsrd.git;a=commitdiff;h=f4d250ad4fad5fcfe5b5feaac3f3e121adef3fba

I marked it 'grave' because it makes olsrd non-functional on platforms like 
amd64.
From f4d250ad4fad5fcfe5b5feaac3f3e121adef3fba Mon Sep 17 00:00:00 2001
From: Jo-Philipp Wich 
Date: Fri, 22 Jun 2012 03:17:59 +0200
Subject: [PATCH] olsrd: fix stack corruption in net_output()

The net_output() function indirectly uses the stack variables dst and dst6
outside of the scope they're declared in, this might leads to olsr_sendto()
being called with a corrupted destination sockaddr_in.

This failure condition can be observed in the log, olsrd will continuosly
print "sendto(v4): Invalid Argument" or a similar message. On ARM it has been
reported to result in "Unsupported Address Family".

This bug became apparant on a custon OpenWrt x86_64 uClibc target using the
Linaro GCC 4.7-2012.04 compiler, it has been reported for an unspecified ARM
target as well.

The offending code seems to be unchanged since 2008 and it does not cause
issues on 32bit systems and/or with older (Linaro) GCC versions, but the
compiler used in our tests seems to perform more aggressive optimizations
leading to a stack corruption.
---
 src/net_olsr.c |4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/net_olsr.c b/src/net_olsr.c
index 7d85f4f..66e103d 100644
--- a/src/net_olsr.c
+++ b/src/net_olsr.c
@@ -336,6 +336,8 @@ net_output(struct interface *ifp)
 {
   struct sockaddr_in *sin = NULL;
   struct sockaddr_in6 *sin6 = NULL;
+  struct sockaddr_in dst;
+  struct sockaddr_in6 dst6;
   struct ptf *tmp_ptf_list;
   union olsr_packet *outmsg;
   int retval;
@@ -354,7 +356,6 @@ net_output(struct interface *ifp)
   outmsg->v4.olsr_packlen = htons(ifp->netbuf.pending);
 
   if (olsr_cnf->ip_version == AF_INET) {
-struct sockaddr_in dst;
 /* IP version 4 */
 sin = (struct sockaddr_in *)&ifp->int_broadaddr;
 
@@ -365,7 +366,6 @@ net_output(struct interface *ifp)
 if (sin->sin_port == 0)
   sin->sin_port = htons(olsr_cnf->olsrport);
   } else {
-struct sockaddr_in6 dst6;
 /* IP version 6 */
 sin6 = (struct sockaddr_in6 *)&ifp->int6_multaddr;
 /* Copy sin */
-- 
1.7.9.5



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: olsrd
Source-Version: 0.6.3-5.1

We believe that the bug you reported is fixed in the latest version of
olsrd, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 704...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
John Paul Adrian Glaubitz  (supplier of updated 
olsrd package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by 

Bug#696727: cheese does not start with Gtk-Warning

[Jonathan Dowland]

On Thu, Mar 28, 2013 at 10:21:30AM +, Jonathan Dowland wrote:
> UI ("No device found"). Interesting stuff. I'm going to try splicing some
> debug statements into the code to see at what point it reaches and whether
> that helps get any further.

I've poked around a little, attached is a backtrace taken when interrupting the
spinning process. It shows the last routine executed in cheese code as
cheese_camera_play. Poking around in the C, 

cheese_camera_play (CheeseCamera *camera)
{
  …
gst_element_set_state (priv->camerabin, GST_STATE_PLAYING);

^^

That's as far as cheese gets. So, is this a gstreamer bug? (or
gstreamer0.10-plugins-bad)? Seems it uses 'camerabin', which has been
deprecated in favour of 'camerabin2' in gst 0.10, and dropped by 1.0.
Cheese moved to camerabin2 between 3.5.5 and 3.5.091.
#0  type_check_is_value_type_U (type=)
at /tmp/buildd/glib2.0-2.33.12+really2.32.4/./gobject/gtype.c:4098
#1  g_type_check_value (value=value@entry=0x1dddfb0)
at /tmp/buildd/glib2.0-2.33.12+really2.32.4/./gobject/gtype.c:4140
#2  0x77769d9c in gst_value_init_and_copy (dest=0x1e33520, 
src=0x1dddfb0) at gstvalue.c:4007
#3  0x7776a03f in copy_garray_of_gstvalue (
src=, 
src=) at 
gstvalue.c:230
#4  0x7776a130 in gst_value_copy_list_or_array (src_value=, 
dest_value=0x7fffd8b0) at gstvalue.c:241
#5  0x7776d35f in gst_value_list_append_value 
(value=value@entry=0x7fffd970, 
append_value=append_value@entry=0x7fffd8f0) at gstvalue.c:314
#6  0x7776da4b in gst_value_intersect_list (dest=0x7fffd970, 
value2=0x1a40460, 
value1=) at 
gstvalue.c:2752
#7  0x7776d999 in gst_value_intersect_list (dest=0x7fffd9f0, 
value2=0x1a40460, 
value1=) at 
gstvalue.c:2746
#8  0x7776d999 in gst_value_intersect_list (dest=0x7fffda70, 
value2=0x1d84658, 
value1=) at 
gstvalue.c:2746
#9  0x7776d999 in gst_value_intersect_list (dest=0x7fffdaf0, 
value2=0x1d84658, 
value1=) at 
gstvalue.c:2746
#10 0x7776d999 in gst_value_intersect_list (dest=0x7fffdb70, 
value2=0x1d84658, 
value1=) at 
gstvalue.c:2746
#11 0x7776d999 in gst_value_intersect_list (dest=0x7fffdbf0, 
value2=0x1d84658, 
value1=) at 
gstvalue.c:2746
#12 0x77750a73 in gst_structure_intersect_field1 (id=3915, 
val1=0x1a3d4a8, data=0x7fffdc60)
at gststructure.c:2981
#13 0x77750fc1 in gst_structure_foreach (structure=0x1a5fb90, 
func=0x77750a20 , 
user_data=0x7fffdc60) at gststructure.c:1097
#14 0x77753c00 in gst_structure_intersect 
(struct1=struct1@entry=0x1a5fb90, struct2=0x1c88330)
at gststructure.c:3030
#15 0x7770f3a4 in gst_caps_intersect_first (caps2=0x19d1e80, 
caps1=0x198ce40) at gstcaps.c:1423
#16 gst_caps_intersect_full (caps1=caps1@entry=0x198ce40, 
caps2=caps2@entry=0x19d1e80, 
mode=mode@entry=GST_CAPS_INTERSECT_FIRST) at gstcaps.c:1454
#17 0x7fffefff4c94 in gst_base_transform_getcaps (pad=0x19c9d90) at 
gstbasetransform.c:768
#18 0x7772cf96 in gst_pad_get_caps_unlocked (pad=pad@entry=0x19c9d90) 
at gstpad.c:2254
#19 0x777305b5 in gst_pad_get_caps_reffed (pad=pad@entry=0x19c9d90) at 
gstpad.c:2338
#20 0x7776148b in gst_element_get_compatible_pad 
(element=element@entry=0x1b8e240, 
pad=pad@entry=0x19c9d90, caps=caps@entry=0x0) at gstutils.c:1146
#21 0x7776216a in gst_element_link_pads_full (src=src@entry=0x1a16090, 
srcpadname=srcpadname@entry=0x0, dest=dest@entry=0x1b8e240, 
destpadname=destpadname@entry=0x0, 
flags=flags@entry=GST_PAD_LINK_CHECK_CAPS) at gstutils.c:1799
#22 0x7fffe16020ea in gst_camerabin_try_add_element 
(bin=bin@entry=0x196e020, 
new_elem=new_elem@entry=0x1b8e240) at camerabingeneral.c:99
#23 0x7fffe160228f in gst_camerabin_add_element (bin=bin@entry=0x196e020, 
new_elem=new_elem@entry=0x1b8e240) at camerabingeneral.c:56
#24 0x7fffe160247d in gst_camerabin_create_and_add_element 
(bin=bin@entry=0x196e020, 
elem_name=, elem_name@entry=0x7fffe16043fd "videoscale", 
instance_name=instance_name@entry=0x7fffe16043f9 "src-videoscale") at 
camerabingeneral.c:146
#25 0x7fffe15f67a0 in camerabin_create_src_elements (camera=0x196e020) at 
gstcamerabin.c:623
#26 camerabin_create_elements (camera=0x196e020) at gstcamerabin.c:779
#27 gst_camerabin_change_state (element=0x196e020, 
transition=GST_STATE_CHANGE_NULL_TO_READY)
at gstcamerabin.c:3892
#28 0x7771a81c in gst_element_change_state 
(element=element@entry=0x196e020, 
transition=transition@entry=GST_STATE_CHANGE_NULL_TO_READY) at 
gstelement.c:2761
#29 0x7771b168 in gst_element_set_state_func (element=0x196e020, 
state=GST_STATE_PLAYING)
at gstelement.c:2717
#30 0x77bd23f5 in cheese_camera_play (camera=0x1774d90) at 
libcheese/cheese-camera.c:725
#31 0x0041805e in cheese_main_window_setup_camera (self=, uri=)
at src/cheese-window.c:5059
#32 0x00

Processed: Re: olsrd does not connect with others on amd64

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 704025 0.6.3-5
Bug #704025 {Done: John Paul Adrian Glaubitz } 
[olsrd] olsrd does not connect with others on amd64
Marked as found in versions olsrd/0.6.3-5 and reopened.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
704025: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704025
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#704025: olsrd does not connect with others on amd64

[John Paul Adrian Glaubitz]

found 704025 0.6.3-5
thanks

According to the discussion [1], the version in unstable is affected as 
well. Therefore tagging the bug report as such.


I just did the NMU for testing, would also do it for unstable by 
packaging upstream 0.6.4 if no one steps up.


Will file an unblock request now first.

Cheers,

Adrian

> [1] https://lists.olsr.org/pipermail/olsr-dev/2013-March/006718.html

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#696727: cheese does not start with Gtk-Warning

[Dmitry Shachnev]

Package: cheese
Version: 3.4.2-2
Followup-For: Bug #696727

I didn’t use Cheese before, but to test this bug I installed cheese
from wheezy on my machine (which is running mostly experimental GNOME),
and it segfaults. A full gdb stacktrace is attached.

--
Dmitry Shachnev

-- System Information:
Debian Release: 7.0
  APT prefers experimental
  APT policy: (500, 'experimental'), (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-4-686-pae (SMP w/4 CPU cores)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages cheese depends on:
ii  cheese-common 3.4.2-2
ii  gnome-video-effects   0.4.0-1
ii  libc6 2.13-38
ii  libcanberra-gtk3-00.28-6
ii  libcheese-gtk21   3.4.2-2
ii  libcheese33.4.2-2
ii  libclutter-1.0-0  1.13.10-1
ii  libclutter-gtk-1.0-0  1.4.4-2
ii  libgdk-pixbuf2.0-02.28.0-1
ii  libgee2   0.6.4-2
ii  libglib2.0-0  2.36.0-1
ii  libgnome-desktop-3-2  3.4.2-1
ii  libgstreamer0.10-00.10.36-1.1
ii  libgtk-3-03.8.0-1

Versions of packages cheese recommends:
ii  gnome-icon-theme3.7.91-1
ii  gvfs1.12.3-4
ii  hicolor-icon-theme  0.12-1
pn  nautilus-sendto 
ii  yelp3.4.2-1+b1

cheese suggests no packages.

-- no debconf information
(gdb) run
Starting program: /usr/bin/cheese 
[Thread debugging using libthread_db enabled]
Using host libthread_db library 
"/lib/i386-linux-gnu/i686/cmov/libthread_db.so.1".
[New Thread 0xb3923b70 (LWP 20056)]

(cheese:20053): Gtk-WARNING **: Attempting to add a widget with type GtkImage 
to a GtkToggleButton, but as a GtkBin subclass a GtkToggleButton can only 
contain one widget at a time; it already contains a widget of type GtkLabel

(cheese:20053): Gtk-WARNING **: Attempting to add a widget with type GtkImage 
to a GtkToggleButton, but as a GtkBin subclass a GtkToggleButton can only 
contain one widget at a time; it already contains a widget of type GtkLabel

(cheese:20053): Gtk-WARNING **: Attempting to add a widget with type GtkImage 
to a GtkToggleButton, but as a GtkBin subclass a GtkToggleButton can only 
contain one widget at a time; it already contains a widget of type GtkLabel

(cheese:20053): Gtk-WARNING **: Attempting to add a widget with type GtkImage 
to a GtkButton, but as a GtkBin subclass a GtkButton can only contain one 
widget at a time; it already contains a widget of type GtkLabel

(cheese:20053): Gtk-WARNING **: Attempting to add a widget with type GtkGrid to 
a GtkToggleButton, but as a GtkBin subclass a GtkToggleButton can only contain 
one widget at a time; it already contains a widget of type GtkLabel

(cheese:20053): Gtk-WARNING **: Attempting to add a widget with type GtkImage 
to a GtkButton, but as a GtkBin subclass a GtkButton can only contain one 
widget at a time; it already contains a widget of type GtkLabel
[New Thread 0xb30edb70 (LWP 20057)]

Program received signal SIGSEGV, Segmentation fault.
0xb6cef18e in cogl_onscreen_add_frame_callback (onscreen=0x8571198, 
callback=callback@entry=0xb7d4f340 , 
user_data=user_data@entry=0x83f1c80, destroy=destroy@entry=0)
at ./cogl-onscreen.c:370
370 ./cogl-onscreen.c: No such file or directory.
(gdb) bt full
#0  0xb6cef18e in cogl_onscreen_add_frame_callback (onscreen=0x8571198, 
callback=callback@entry=0xb7d4f340 , 
user_data=user_data@entry=0x83f1c80, destroy=destroy@entry=0)
at ./cogl-onscreen.c:370
closure = 0x8566580
#1  0xb7d502f8 in clutter_stage_cogl_realize (stage_window=0x83f1c80)
at ./cogl/clutter-stage-cogl.c:163
stage_cogl = 0x83f1c80
backend = 
framebuffer = 
error = 0x0
#2  0xb7d49c7f in clutter_stage_x11_realize (stage_window=0x83f1c80)
at ./x11/clutter-stage-x11.c:609
stage_x11 = 0x83f1c80
stage_cogl = 0x83f1c80
backend = 0x8087800
backend_x11 = 0x8087800
device_manager = 
event_flags = 
width = 682
height = 450
#3  0xb7dd0573 in _clutter_stage_window_realize (window=0x83f1c80)
at ./clutter-stage-window.c:88
No locals.
#4  0xb7dc989d in clutter_stage_realize (self=0x84f17f0)
at ./clutter-stage.c:761
priv = 
is_realized = 
#5  0xb755628a in g_cclosure_marshal_VOID__VOIDv (closure=0x84f04e0, 
return_value=0x0, instance=0x84f17f0, 
args=0xbfffe72c "\241\062C\267\364?T\267@\nW\b\001", 
marshal_data=0xb7dc9850, n_params=0, param_types=0x0)
at /tmp/buildd/glib2.0-2.36.0/./gobject/gmarshal.c:115
cc = 0x84f04e0
data1 = 
data2 = 0x84eb4a0
callback = 0xb7dc9850 
#6  0xb7552df7 in g_type_class_meta_marshalv (closure=closure@entry=0x84f04e0, 
return_value=return_value@entry=0x0, instance=instance@entry=0x84f17f0, 
args=args@entry=0xbfffe72c "\241\062C\267\364?T\267@\nW\b\001", 
marshal_data=marshal_data@entry=0x54, n_params=n_params@entry=0, 
param_types=param_types@entry=

Bug#704025: marked as done (olsrd does not connect with others on amd64)

[Debian Bug Tracking System]

Your message dated Thu, 28 Mar 2013 13:47:59 +
with message-id 
and subject line Bug#704025: fixed in olsrd 0.6.2-2.1
has caused the Debian Bug report #704025,
regarding olsrd does not connect with others on amd64
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
704025: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704025
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: olsrd
Version: 0.6.2-2
Severity: grave
Tags: patch pending upstream fixed-upstream wheezy

The net_output() function indirectly uses the stack variables dst and dst6
outside of the scope they're declared in, this might leads to olsr_sendto()
being called with a corrupted destination sockaddr_in.

This failure condition can be observed in the log, olsrd will continuosly
print "sendto(v4): Invalid Argument" or a similar message. On ARM it has been
reported to result in "Unsupported Address Family".

This bug became apparant on a custon OpenWrt x86_64 uClibc target using the
Linaro GCC 4.7-2012.04 compiler, it has been reported for an unspecified ARM
target as well.

The offending code seems to be unchanged since 2008 and it does not cause
issues on 32bit systems and/or with older (Linaro) GCC versions, but the
compiler used in our tests seems to perform more aggressive optimizations
leading to a stack corruption.

full thread and discussion here:
https://lists.olsr.org/pipermail/olsr-dev/2013-March/006718.html
(self signed cert SHA1:
6D 93 1C 9C C3 7C 67 7A 44 A8 C7 B0 2F E7 44 C7 48 D6 27 49)

fix is already included upstream in v0.6.4:
http://olsr.org/git/?p=olsrd.git;a=commitdiff;h=f4d250ad4fad5fcfe5b5feaac3f3e121adef3fba

I marked it 'grave' because it makes olsrd non-functional on platforms like 
amd64.
From f4d250ad4fad5fcfe5b5feaac3f3e121adef3fba Mon Sep 17 00:00:00 2001
From: Jo-Philipp Wich 
Date: Fri, 22 Jun 2012 03:17:59 +0200
Subject: [PATCH] olsrd: fix stack corruption in net_output()

The net_output() function indirectly uses the stack variables dst and dst6
outside of the scope they're declared in, this might leads to olsr_sendto()
being called with a corrupted destination sockaddr_in.

This failure condition can be observed in the log, olsrd will continuosly
print "sendto(v4): Invalid Argument" or a similar message. On ARM it has been
reported to result in "Unsupported Address Family".

This bug became apparant on a custon OpenWrt x86_64 uClibc target using the
Linaro GCC 4.7-2012.04 compiler, it has been reported for an unspecified ARM
target as well.

The offending code seems to be unchanged since 2008 and it does not cause
issues on 32bit systems and/or with older (Linaro) GCC versions, but the
compiler used in our tests seems to perform more aggressive optimizations
leading to a stack corruption.
---
 src/net_olsr.c |4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/net_olsr.c b/src/net_olsr.c
index 7d85f4f..66e103d 100644
--- a/src/net_olsr.c
+++ b/src/net_olsr.c
@@ -336,6 +336,8 @@ net_output(struct interface *ifp)
 {
   struct sockaddr_in *sin = NULL;
   struct sockaddr_in6 *sin6 = NULL;
+  struct sockaddr_in dst;
+  struct sockaddr_in6 dst6;
   struct ptf *tmp_ptf_list;
   union olsr_packet *outmsg;
   int retval;
@@ -354,7 +356,6 @@ net_output(struct interface *ifp)
   outmsg->v4.olsr_packlen = htons(ifp->netbuf.pending);
 
   if (olsr_cnf->ip_version == AF_INET) {
-struct sockaddr_in dst;
 /* IP version 4 */
 sin = (struct sockaddr_in *)&ifp->int_broadaddr;
 
@@ -365,7 +366,6 @@ net_output(struct interface *ifp)
 if (sin->sin_port == 0)
   sin->sin_port = htons(olsr_cnf->olsrport);
   } else {
-struct sockaddr_in6 dst6;
 /* IP version 6 */
 sin6 = (struct sockaddr_in6 *)&ifp->int6_multaddr;
 /* Copy sin */
-- 
1.7.9.5



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: olsrd
Source-Version: 0.6.2-2.1

We believe that the bug you reported is fixed in the latest version of
olsrd, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 704...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
John Paul Adrian Glaubitz  (supplier of updated 
olsrd package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by 

Bug#700169: non-free license: requires to obey US export regulation even, when not in the US

[Michael Stapelberg]

Hi Mattia,

Mattia Dongili  writes:
> I don't see a valid reason to get a newer version in wheezy at this
> stage of the freeze.
I agree.

Adam, here is the diffstat between the version currently in wheezy
(upstream git commit f07ee8aa562b7cee0138a88219169f501fd9c041) and the
version which is in the NEW queue (upstream commit
4fddab2e860aa7e14bd543aef6ed808be4b04aa2):

git clone git://github.com/acpica/acpica.git
cd acpica
git diff --stat 
f07ee8aa562b7cee0138a88219169f501fd9c041..4fddab2e860aa7e14bd543aef6ed808be4b04aa2
…
 1694 files changed, 109757 insertions(+), 45915 deletions(-)

Can we just ignore this bug for wheezy? To me, the licensing intention
seems very clear.

-- 
Best regards,
Michael


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#703919: marked as done (kvpm: When moving a disk partition, if another partition is mounted the data being moved may become corrupted.)

[Debian Bug Tracking System]

Your message dated Thu, 28 Mar 2013 11:34:57 +
with message-id 
and subject line Bug#703919: fixed in kvpm 0.8.6-2+deb7u1
has caused the Debian Bug report #703919,
regarding kvpm: When moving a disk partition, if another partition is mounted 
the data being moved may become corrupted.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
703919: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703919
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kvpm
Version: 0.8.6-3
Severity: critical
Tags: upstream patch
Justification: causes serious data loss

Dear Maintainer,
If a partition with data on it is moved by kvpm and that same disk
has another partition which is mounted then sometimes the data on the
moved partition is scrambled. Even the filesystem is gone. Unmounting
the other partition is the only fix for the problem.

-- System Information:
Debian Release: 7.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/2 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 kvpm depends on:
ii  kde-runtime4:4.9.5-0r1
ii  libblkid1  2.20.1-5.3
ii  libc6  2.13-38
ii  libkdecore54:4.9.5-0r1
ii  libkdeui5  4:4.9.5-0r1
ii  libkio54:4.9.5-0r1
ii  liblvm2app2.2  2.02.98-1
ii  libparted0debian1  2.3-12
ii  libqtcore4 4:4.8.2+dfsg-11
ii  libqtgui4  4:4.8.2+dfsg-11
ii  libstdc++6 4.7.2-5

Versions of packages kvpm recommends:
ii  dosfstools 3.0.16-2
ii  jfsutils   1.1.15-2
ii  ntfs-3g1:2013.1.13AR.1-2
ii  reiserfsprogs  1:3.6.21-1
ii  xfsprogs   3.1.9

Versions of packages kvpm suggests:
pn  btrfs-tools   
pn  reiser4progs  

-- no debconf information
This patch corrects a bug in which data is sometimes corrupted when moving a disk 
partition while the disk has other partitions mounted.
--- a/kvpm/partchange.cpp
+++ b/kvpm/partchange.cpp
@@ -649,13 +649,8 @@
 return false;
 }
 else {
-if( !movefs(old_start, current_start, old_size) ){
-return false;
-}
-else{
-pedCommitAndWait(m_ped_disk);
-return true;
-}
+pedCommitAndWait(m_ped_disk);
+	return movefs(old_start, current_start, old_size);
 }
 }
 
--- End Message ---
--- Begin Message ---
Source: kvpm
Source-Version: 0.8.6-2+deb7u1

We believe that the bug you reported is fixed in the latest version of
kvpm, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 703...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
John Paul Adrian Glaubitz  (supplier of updated 
kvpm package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 28 Mar 2013 12:00:54 +0100
Source: kvpm
Binary: kvpm kvpm-dbg
Architecture: source amd64
Version: 0.8.6-2+deb7u1
Distribution: testing-proposed-updates
Urgency: high
Maintainer: Benjamin J. Scott 
Changed-By: John Paul Adrian Glaubitz 
Description: 
 kvpm   - Logical volume manager and disk partitioner GUI based on KDE
 kvpm-dbg   - kvpm's debugging symbols
Closes: 703919
Changes: 
 kvpm (0.8.6-2+deb7u1) testing-proposed-updates; urgency=high
 .
   [ Benjamin J. Scott ]
   * Changed file kvpm/partchange.cpp to fix potential data corruption bug
 when moving a partition on a disk with mounted partitions (Closes: 
#703919).
 .
   [ John Paul Adrian Glaubitz ]
   * Rebuild version 0.8.6-3 for testing due the dependency on liblvm2app2.2
 which has a different version in unstable.
Checksums-Sha1: 
 641bdc229c8200a5e9c63169f143f3480fe52b20 2035 kvpm_0.8.6-2+deb7u1.dsc
 a10315770b47ff3336213843412b70b06a13c135 808921 kvpm_0.8.6.orig.tar.gz
 aefed343dcc4f8e057ab90d176ffb2398a477408 11059 
kvpm_0.8.6-2+deb7u1.debian.tar.gz
 e7b346996fcd65f2cf11fb76102b3cd078ae5d41 913576 kvpm_0.8.6-2+deb7u1_amd64.deb
 1e770ef99df950d66765d75abd4d6d325bae1dc2 10451500 
kvpm-dbg_0.8.6-2+deb7u1_amd64.deb
Checksums-Sha256: 
 f9e50cb8a8520bd6d4015a54b0c226a8bf8733a2c2b0c0a4544e6cb6dc9d02e7 2035 
kvpm_0.8.6-2+deb7u1.

Bug#702965: marked as done (procps: ps dies with SIGSEGV on kernels > 3.2.29 and lots of supplementary groups)

[Debian Bug Tracking System]

Your message dated Thu, 28 Mar 2013 11:17:29 +
with message-id 
and subject line Bug#702965: fixed in procps 1:3.3.3-3
has caused the Debian Bug report #702965,
regarding procps: ps dies with SIGSEGV on kernels > 3.2.29 and lots of 
supplementary groups
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
702965: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702965
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: procps
Version: 1:3.2.8-9squeeze1
Severity: normal


We found that under the following circumstances:
* Kernel > 3.2.29 (which shows > 32 groups in /proc/${pid}/status)
* one or more users logged in with lots of supplementary groups

then ps(1) fails with a SIGSEGV after attempting to allocate lots of memory.

This appears to be due flawed assumption in ps: That the contents of
/proc/${pid}/status will fit into a buffer of 1024 bytes: if the file
is larger, only the first 1024 bytes are read, and when subsequently
scanning the buffer the code "falls off the end":

  http://forums.grsecurity.net/viewtopic.php?f=3&t=3298

Although 32 groups sounds ample, sites using Active Directory will
often find their users being members of lots of groups, as group
membership is a recursive concept in AD. And the numeric group IDs are
(in our case) 9 characters each, thus easily overflowing the 1024 byte
buffer.

Here's an example:

- 8< cut here 8< -
karl@someserver: ~$ ps


Signal 11 (SEGV) caught by ps (procps version 3.2.8).
Please send bug reports to  or 
karl@someserver: ~$ strace ps 2>&1 | tail -30
stat("/proc/1997", {st_mode=S_IFDIR|0555, st_size=0, ...}) = 0
open("/proc/1997/stat", O_RDONLY)   = 6
read(6, "1997 (sshd) S 1989 1989 1989 0 -"..., 1023) = 191
close(6)= 0
open("/proc/1997/status", O_RDONLY) = 6
read(6, "Name:\tsshd\nState:\tS (sleeping)\nT"..., 1023) = 1023
close(6)= 0
mmap(NULL, 135168, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7f037a2fd000
mremap(0x7f037a2fd000, 135168, 266240, MREMAP_MAYMOVE) = 0x7f0379cd9000
mremap(0x7f0379cd9000, 266240, 528384, MREMAP_MAYMOVE) = 0x7f0379c58000
mremap(0x7f0379c58000, 528384, 1052672, MREMAP_MAYMOVE) = 0x7f0379b57000
mremap(0x7f0379b57000, 1052672, 2101248, MREMAP_MAYMOVE) = 0x7f0379956000
mremap(0x7f0379956000, 2101248, 4198400, MREMAP_MAYMOVE) = 0x7f0379555000
mremap(0x7f0379555000, 4198400, 8392704, MREMAP_MAYMOVE) = 0x7f0378d54000
mremap(0x7f0378d54000, 8392704, 16781312, MREMAP_MAYMOVE) = 0x7f0377d53000
mremap(0x7f0377d53000, 16781312, 33558528, MREMAP_MAYMOVE) = 0x7f0375d52000
mremap(0x7f0375d52000, 33558528, 67112960, MREMAP_MAYMOVE) = 0x7f0371d51000
mremap(0x7f0371d51000, 67112960, 134221824, MREMAP_MAYMOVE) = 0x7f0369d5
mremap(0x7f0369d5, 134221824, 268439552, MREMAP_MAYMOVE) = 0x7f0359d4f000
mremap(0x7f0359d4f000, 268439552, 536875008, MREMAP_MAYMOVE) = 0x7f0339d4e000
mremap(0x7f0339d4e000, 536875008, 1073745920, MREMAP_MAYMOVE) = 0x7f02f9d4d000
mremap(0x7f02f9d4d000, 1073745920, 2147487744, MREMAP_MAYMOVE) = 0x7f0279d4c000
mremap(0x7f0279d4c000, 2147487744, 4096, MREMAP_MAYMOVE) = 0x7f0279d4c000
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
write(2, "\n\nSignal 11 (SEGV) caught by ps "..., 132

Signal 11 (SEGV) caught by ps (procps version 3.2.8).
Please send bug reports to  or 
) = 132
exit_group(139) = ?


karl@someserver: ~$ wc --bytes < /proc/1997/status
1810
- 8< cut here 8< -

I have a (temporary) patch which increases the buffer size to 8K,
which appears sufficient in our case. But this does not fix the
underlying problem of having a limited buffer size to start with...


- 8< cut here 8< -
--- a/proc/readproc.c   2013-03-12 19:43:24.0 +
+++ b/proc/readproc.c   2013-03-13 10:12:47.744038428 +
@@ -28,6 +28,15 @@
 #include 
 #include 
 
+/* Max # of bytes to expect in /proc/%d/status.
+
+   This may be a crazy amount if lots of supplementary groups are
+   listed.  Most kernels will limit the contents to 32 (NGROUPS_SMALL)
+   groups, but kernels > 3.2.29 may show ALL of the supplementary
+   groups...
+ */
+#define PROC_STATUS_BUFSIZE 8192
+
 // sometimes it's easier to do this manually, w/o gcc helping
 #ifdef PROF
 extern void __cyg_profile_func_enter(void*,void*);
@@ -560,7 +569,7 @@
 // room to spare.
 static proc_t* simple_readproc(PROCTAB *restrict const PT, proc_t *restrict 
const p) {
 static struct stat sb; // stat() b

Bug#704122: ndiswrapper-dkms: Fails to build module because of missing BUILT_MODULE_NAME

[Julian Andres Klode]

Control: reassign -1 dkms
Control: forcemerge 690747 -1
Control: affects 690747 ndiswrapper-dkms

On Thu, Mar 28, 2013 at 10:35:04AM +0100, Patrick Matthäi wrote:
> Package: ndiswrapper-dkms
> Version: 1.57-1
> Severity: serious
> Tags: patch
> 
> Hi,
> 
> the module fails to build with dkms, because BUILT_MODULE_NAME is not defined
> in the dkms.conf, here is a patch:
> 
> diff -Naur ndiswrapper-1.57.orig/debian/ndiswrapper-dkms.dkms.in 
> ndiswrapper-1.57/debian/ndiswrapper-dkms.dkms.in
> --- ndiswrapper-1.57.orig/debian/ndiswrapper-dkms.dkms.in   2012-03-05 
> 16:49:17.0 +0100
> +++ ndiswrapper-1.57/debian/ndiswrapper-dkms.dkms.in2013-03-28 
> 10:32:28.520623214 +0100
> @@ -1,4 +1,5 @@
>  PACKAGE_NAME="ndiswrapper"
>  PACKAGE_VERSION="@VERSION@"
> +BUILT_MODULE_NAME[0]="$PACKAGE_NAME"
>  DEST_MODULE_LOCATION[0]="/updates"
>  AUTOINSTALL="yes"
> 

The configuration file is fully specified as defined by the dkms manual
page and worked previously. As such, dkms should be considered broken; 
not ndiswrapper. It is not my task to work around third party mistakes.

I asked the dkms maintainers in the other bug on 2013-03-03, but have
not received any explanation for the breakage.

I just noticed that I cannot even reproduce this problem; so whatever
you do to get this breakage, please discuss this with the dkms
maintainers.

-- Log showing that it works for me:

Get:1 http://localhost/debian/ sid/main dkms all 2.2.0.3-1.2 [77.4 kB]
Get:2 http://localhost/debian/ sid/main linux-headers-3.2.0-4-common amd64 
3.2.41-2 [3,547 kB]
Get:3 http://localhost/debian/ sid/main linux-kbuild-3.2 amd64 3.2.17-1 [238 kB]
Get:4 http://localhost/debian/ sid/main linux-headers-3.2.0-4-amd64 amd64 
3.2.41-2 [598 kB]  
Get:5 http://localhost/debian/ sid/main linux-headers-amd64 amd64 3.2+46 [4,450 
B]   
Get:6 http://localhost/debian/ sid/main ndiswrapper-dkms all 1.57-1 [192 kB]
 
Fetched 4,657 kB in 7s (623 kB/s)   
 
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
serious bugs of ndiswrapper-dkms (-> 1.57-1) 
Summary:
 ndiswrapper-dkms(1 bug)
Are you sure you want to install/upgrade the above packages? [Y/n/?/...] y
Selecting previously unselected package dkms.
(Reading database ... 201512 files and directories currently installed.)
Unpacking dkms (from .../dkms_2.2.0.3-1.2_all.deb) ...
Selecting previously unselected package linux-headers-3.2.0-4-common.
Unpacking linux-headers-3.2.0-4-common (from 
.../linux-headers-3.2.0-4-common_3.2.41-2_amd64.deb) ...
Selecting previously unselected package linux-kbuild-3.2.
Unpacking linux-kbuild-3.2 (from .../linux-kbuild-3.2_3.2.17-1_amd64.deb) ...
Selecting previously unselected package linux-headers-3.2.0-4-amd64.
Unpacking linux-headers-3.2.0-4-amd64 (from 
.../linux-headers-3.2.0-4-amd64_3.2.41-2_amd64.deb) ...
Selecting previously unselected package linux-headers-amd64.
Unpacking linux-headers-amd64 (from .../linux-headers-amd64_3.2+46_amd64.deb) 
...
Selecting previously unselected package ndiswrapper-dkms.
Unpacking ndiswrapper-dkms (from .../ndiswrapper-dkms_1.57-1_all.deb) ...
Processing triggers for man-db ...
Setting up dkms (2.2.0.3-1.2) ...
Setting up linux-headers-3.2.0-4-common (3.2.41-2) ...
Setting up linux-kbuild-3.2 (3.2.17-1) ...
Setting up linux-headers-3.2.0-4-amd64 (3.2.41-2) ...
Examining /etc/kernel/header_postinst.d.
run-parts: executing /etc/kernel/header_postinst.d/dkms 3.2.0-4-amd64
Setting up linux-headers-amd64 (3.2+46) ...
Setting up ndiswrapper-dkms (1.57-1) ...
Loading new ndiswrapper-1.57 DKMS files...
First Installation: checking all kernels...
Building only for 3.2.0-4-amd64
Building initial module for 3.2.0-4-amd64
Done.

ndiswrapper:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/3.2.0-4-amd64/updates/dkms/

depmod



-- 
Julian Andres Klode  - Debian Developer, Ubuntu Member

See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.


pgp3WEcLPQ0Yc.pgp
Description: PGP signature

Bug#704041: marked as done (procps: Signal 11 (SEGV) caught by ps (procps-ng version 3.3.3). ps:display.c:59: please report)

[Debian Bug Tracking System]

Your message dated Thu, 28 Mar 2013 11:17:29 +
with message-id 
and subject line Bug#702965: fixed in procps 1:3.3.3-3
has caused the Debian Bug report #702965,
regarding procps: Signal 11 (SEGV) caught by ps (procps-ng version 3.3.3). 
ps:display.c:59: please report
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
702965: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702965
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: procps
Version: 1:3.3.3-2
Severity: normal

I just got this in the mailbox. I do not have any further
information, but can try to get some if needed and told
which. There’s nothing related in dmesg, but syslog was
rotated at 07:36:06 +0100.

From: Anacron 
Message-ID: <20130327063606.b860e4a0...@evolvis.org>
To: r...@evolvis.org
Date: Wed, 27 Mar 2013 07:36:06 +0100 (CET)
Subject: Anacron job 'cron.daily' on evolvis.org

/etc/cron.daily/sysklogd:   
Signal 11 (SEGV) caught by ps (procps-ng version 
3.3.3).
ps:display.c:59: please report this bug


Running manually also triggers it:

root@evolvis:~ # ps
Signal 11 (SEGV) caught by ps (procps-ng version 3.3.3).
ps:display.c:59: please report this bug

There’s no procps-dbg, that’s why the backtrace is a bit poor:

root@evolvis:~ # gdb /bin/ps
GNU gdb (GDB) 7.4.1-debian
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu".
For bug reporting instructions, please see:
...
Reading symbols from /bin/ps...(no debugging symbols found)...done.
(gdb) r
Starting program: /bin/ps

Program received signal SIGSEGV, Segmentation fault.
0xb7edfb4f in memcpy () from /lib/i386-linux-gnu/libc.so.6
(gdb) bt
#0  0xb7edfb4f in memcpy () from /lib/i386-linux-gnu/libc.so.6
#1  0xb7fb92d9 in ?? () from /lib/i386-linux-gnu/libprocps.so.0
#2  0xb7fba711 in ?? () from /lib/i386-linux-gnu/libprocps.so.0
#3  0xb7fba988 in readproc () from /lib/i386-linux-gnu/libprocps.so.0
#4  0x0804a402 in ?? ()
#5  0xb7e7be16 in __libc_start_main () from /lib/i386-linux-gnu/libc.so.6
#6  0x0804a575 in ?? ()


-- System Information:
Debian Release: 7.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-4-686-pae (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/mksh-static

Versions of packages procps depends on:
ii  initscripts   2.88dsf-41
ii  libc6 2.13-38
ii  libncurses5   5.9-10
ii  libncursesw5  5.9-10
ii  libprocps01:3.3.3-2
ii  libtinfo5 5.9-10
ii  lsb-base  4.1+Debian8

Versions of packages procps recommends:
ii  psmisc  22.19-1+deb7u1

procps suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: procps
Source-Version: 1:3.3.3-3

We believe that the bug you reported is fixed in the latest version of
procps, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 702...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Craig Small  (supplier of updated procps package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 28 Mar 2013 21:03:15 +1100
Source: procps
Binary: procps libprocps0 libprocps0-dev
Architecture: source amd64
Version: 1:3.3.3-3
Distribution: testing-proposed-updates
Urgency: medium
Maintainer: Craig Small 
Changed-By: Craig Small 
Description: 
 libprocps0 - library for accessing process information from /proc
 libprocps0-dev - library for accessing process information from /proc
 procps - /proc file system utilities
Closes: 702965
Changes: 
 procps (1:3.3.3-3) testing-proposed-updates; urgency=medium
 .
   * 3.3.3-3 Fix ps crash with large process groups Closes: #702965
Checksums-Sha1: 
 c10f1e3971f58e793824724785144cf324cfe852 1952 procps_3.3.3-3.dsc
 ce7435ca45bd083b6b0bd9b1576a50ade9

Processed: fixed 702965 in 1:3.3.4-1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # as per maintainer
> fixed 702965 1:3.3.4-1
Bug #702965 {Done: Craig Small } [procps] procps: ps dies 
with SIGSEGV on kernels > 3.2.29 and lots of supplementary groups
Bug #704041 {Done: Craig Small } [procps] procps: Signal 11 
(SEGV) caught by ps (procps-ng version 3.3.3). ps:display.c:59: please report
Marked as fixed in versions procps/1:3.3.4-1.
Marked as fixed in versions procps/1:3.3.4-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
702965: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702965
704041: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704041
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: Re: Bug#704122: ndiswrapper-dkms: Fails to build module because of missing BUILT_MODULE_NAME

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 dkms
Bug #704122 [ndiswrapper-dkms] ndiswrapper-dkms: Fails to build module because 
of missing BUILT_MODULE_NAME
Bug reassigned from package 'ndiswrapper-dkms' to 'dkms'.
No longer marked as found in versions ndiswrapper/1.57-1.
Ignoring request to alter fixed versions of bug #704122 to the same values 
previously set
> forcemerge 690747 -1
Bug #690747 [dkms] ndiswrapper-dkms: breaks dkms on kernel upgrades
Bug #704122 [dkms] ndiswrapper-dkms: Fails to build module because of missing 
BUILT_MODULE_NAME
Severity set to 'important' from 'serious'
Bug #690747 [dkms] ndiswrapper-dkms: breaks dkms on kernel upgrades
Added tag(s) patch.
Merged 690747 704122
> affects 690747 ndiswrapper-dkms
Bug #690747 [dkms] ndiswrapper-dkms: breaks dkms on kernel upgrades
Bug #704122 [dkms] ndiswrapper-dkms: Fails to build module because of missing 
BUILT_MODULE_NAME
Added indication that 690747 affects ndiswrapper-dkms
Added indication that 704122 affects ndiswrapper-dkms

-- 
690747: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690747
704122: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704122
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#702965: Fixed in 3.3.4-1

[Craig Small]

Package: procps
Version: 1%3.3.4-1

Upstream commit at
https://www.gitorious.org/procps/procps/commit/7933435584aa1fd75460f4c7715a3d4855d97c1c
fixed this which appeared in upstream version 3.3.4.

 - Craig
-- 
Craig Small VK2XLZ   http://enc.com.au/  csmall at : enc.com.au
Debian GNU/Linux http://www.debian.org/  csmall at : debian.org
GPG fingerprint: 5D2F B320 B825 D939 04D2  0519 3938 F96B DF50 FEA5


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#703444: marked as done (ecere-sdk: Must build-dep on and use libgif-dev instead of included libungif)

[Debian Bug Tracking System]

Your message dated Thu, 28 Mar 2013 11:03:16 +
with message-id 
and subject line Bug#703444: fixed in ecere-sdk 0.44.06-1
has caused the Debian Bug report #703444,
regarding ecere-sdk: Must build-dep on and use libgif-dev instead of included 
libungif
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
703444: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703444
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ecere-sdk
Severity: serious
Version: 0.44.03-1

libungif has been removed from debian in favour of libgif.

ecere-sdk should build-dep on libgif-dev & use that instead of the
included copy of code.

Also it would be preferred for ecere-sdk to not have "/deps/" - external
copies of code included in the release tarball

Regards,

Dmitrijs.
--- End Message ---
--- Begin Message ---
Source: ecere-sdk
Source-Version: 0.44.06-1

We believe that the bug you reported is fixed in the latest version of
ecere-sdk, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 703...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jerome St-Louis  (supplier of updated ecere-sdk package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 28 Mar 2013 01:00:00 -0400
Source: ecere-sdk
Binary: ecere-sdk ecere-dev libecere0 libecerecom0 libecc0 libeda0 
libedasqlite0 ecere-samples ecere-extras
Architecture: source amd64 all
Version: 0.44.06-1
Distribution: experimental
Urgency: low
Maintainer: Jerome St-Louis 
Changed-By: Jerome St-Louis 
Description: 
 ecere-dev  - Ecere SDK Development Tools
 ecere-extras - Extras for the Ecere SDK
 ecere-samples - Project samples for the Ecere SDK
 ecere-sdk  - Ecere cross-platform SDK
 libecc0- eC Compiler Library
 libecere0  - Ecere Runtime Library
 libecerecom0 - eC Core Runtime Library
 libeda0- Ecere Data Access
 libedasqlite0 - EDA SQLite Driver
Closes: 703444
Changes: 
 ecere-sdk (0.44.06-1) experimental; urgency=low
 .
   * Fixed bugs causing build to fail on PowerPC
   * Fixed cross-bitness compiling issues
   * Fixed UTF8 text processing issues
   * Fixed serialization/unserialization of Map container objects
   * Fixed ListBox row moving bug
   * Fixed ColorPicker in IDE to be consistent with other dialogs
   * Enabled holding up/down buttons down to reorder directories
 in compiler settings
   * Relying on giflib rather than bundled libungif, taking out deps folder
 for Debian packages (Closes: #703444)
Checksums-Sha1: 
 38c87d97ab9123909345e96ed44b2ed62ec67f5a 2355 ecere-sdk_0.44.06-1.dsc
 9a51aeee7a8ee0f19b6a098e3cbdc594d3448b0a 11799546 
ecere-sdk_0.44.06.orig.tar.bz2
 8bbd8e83af4d8f5f6b32bcc7e7b4d7071bb1b413 8623 ecere-sdk_0.44.06-1.debian.tar.gz
 c556f047c87267c0b1201015f974de35d5fb453b 10546 ecere-sdk_0.44.06-1_amd64.deb
 c25e6b3dc4c16cd593bb418a538b63d43a0845bb 4355252 ecere-dev_0.44.06-1_amd64.deb
 45abc94803203a22642abc063b025fa9f70c9492 885476 libecere0_0.44.06-1_amd64.deb
 a8cc44e7680bc534ba231184a95fbe24a05ab43b 105908 
libecerecom0_0.44.06-1_amd64.deb
 3fd6e580ed5e83cfc391721edab3d40859f54edd 347250 libecc0_0.44.06-1_amd64.deb
 b683c649b61314fea27acadc46797f849d9b8e84 97046 libeda0_0.44.06-1_amd64.deb
 7c776069ca747412167e04da9ddc442827dd9cc1 31426 
libedasqlite0_0.44.06-1_amd64.deb
 7d14bb3ef02060efb58212e8730ec38bfb9df81f 6882840 
ecere-samples_0.44.06-1_all.deb
 0f754cb7ab7eafecf27c0c90377c55cc1585d6e3 225920 ecere-extras_0.44.06-1_all.deb
Checksums-Sha256: 
 e8ee37543dc7d4a687e6db8ee78f5248035215df8493d53770740f7c984bc740 2355 
ecere-sdk_0.44.06-1.dsc
 8035ae34e4a5bc33265508779da71789e161f57c711f42c81c426e03839f4ea6 11799546 
ecere-sdk_0.44.06.orig.tar.bz2
 39b946325a21cf548f0f6787c23ecaf7ab3d67a883a2d0440e2f031f49abf09f 8623 
ecere-sdk_0.44.06-1.debian.tar.gz
 73e17003e6832433db829468eb8df180753c92f236d7ac2945214af8a1bc76bd 10546 
ecere-sdk_0.44.06-1_amd64.deb
 f4a2c4f10c0302d117ab9941d7ed792fd8a53c3f64eae482eb2519a20a056b3f 4355252 
ecere-dev_0.44.06-1_amd64.deb
 4c91288939e3f0090d2f39409f42a78a6fceffe2330e0e2f8576c0dfba7d5c78 885476 
libecere0_0.44.06-1_amd64.deb
 7fbb454855e61bab0c701636c3995375979767e73dae3409f4305729309b5478 105908 
libece

Bug#696727: Info received (Bug#696727: cheese does not start with Gtk-Warning)

[Jonathan Dowland]

I've just noticed that cheese is busy looping and mallocing whilst it's
seemingly doing nothing:

>   PID USER  PR  NI  VIRT  RES  SHR S  %CPU %MEMTIME+  COMMAND 
>   
> 18958 jon   20   0 7513m 6.2g 3236 R  92.1 80.0  20:03.57 cheese  
>   


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#704041: procps: Signal 11 (SEGV) caught by ps (procps-ng version 3.3.3). ps:display.c:59: please report

[Craig Small]

On Wed, Mar 27, 2013 at 01:14:53PM +0100, Thorsten Glaser wrote:
> > Can you run strace on it? It looks like libproc doesn't like something
> > found in the kernel /proc filesystem but strace will tell us which one.
> 
> typescript attached.
Thanks for that trace and the report.  Just in case you don't follow
the bug tracker to closely I have raised the level of the bug report and
the one its merged with to serious.  The reason for this is that a lot
of other people will cop this bug if they have larger than "normal"
set of groups for processes.

I have prepared a minimal patch for wheezy and asked for procps 3.3.3-3
to be unblocked so this bug can not be in wheezy.  While I feel pretty
bad giving the release team more work at this important time, ps
crashing is a pretty bad bug.

So, cross your fingers and hope they let the patch through!
Again, thanks for the report. It has basically (hopefully) stopped a bad
ps going into the wheezy release.

 - Craig
-- 
Craig Small VK2XLZ   http://enc.com.au/  csmall at : enc.com.au
Debian GNU/Linux http://www.debian.org/  csmall at : debian.org
GPG fingerprint: 5D2F B320 B825 D939 04D2  0519 3938 F96B DF50 FEA5


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#696727: cheese does not start with Gtk-Warning

[Jonathan Dowland]

On Thu, Mar 28, 2013 at 11:13:34AM +0100, John Paul Adrian Glaubitz wrote:
> How about unloading the kernel module then? I guess it's probably an
> UVC camera, so modprobe -r uvcvideo should do the trick for most
> cameras (as most of them are UVC).

Thanks for the tip. It is indeed uvcvideo, and unloading it means cheese draws 
its
UI ("No device found"). Interesting stuff. I'm going to try splicing some debug
statements into the code to see at what point it reaches and whether that helps
get any further.

FWIW some earlier verison of cheese worked with this webcam on this laptop.


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#696727: ~ Re: Bug#696727: cheese does not start with Gtk-Warning

[John Paul Adrian Glaubitz]

On 03/28/2013 09:55 AM, Jonathan Dowland wrote:

On 27 Mar 2013, at 23:41, John Paul Adrian Glaubitz 
 wrote:


could anyone who is seeing the issue with Cheese freezing try to disconnect 
their webcam


In my case I don't think so- it's built into the frame of my laptop screen.


How about unloading the kernel module then? I guess it's probably an UVC 
camera, so modprobe -r uvcvideo should do the trick for most cameras (as 
most of them are UVC).


Adrian
--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#704123: virtualbox-ose: my debian desktop will be shutdown after i click some links.

[rainysia]

Package: virtualbox-ose
Version: 3.2.10-dfsg-1+squeeze1
Severity: grave
Tags: upstream
Justification: causes non-serious data loss

hi,

After i installed virtualbox in squeeze,it has comflict with the NVIDIA
drivers(Version304.43), some links are broken!
when i click some links like virtualbox's network setup ,some WINE soft
url, or other software setup (such as rhythmbox ),my debian will be shut down,
there is something horrible, i was listenning the music with rhythmbox, my
earplug receiver a loudly beeper sounds like BBU!!!  : ( , it scared me !



-- System Information:
Debian Release: 6.0.7
  APT prefers proposed-updates
  APT policy: (500, 'proposed-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/2 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 virtualbox-ose depends on:
ii  adduser3.112+nmu2add and remove users and groups
ii  libc6  2.11.3-4  Embedded GNU C Library: Shared lib
ii  libcurl3   7.21.0-2.1+squeeze2   Multi-protocol file transfer libra
ii  libgcc11:4.4.5-8 GCC support library
ii  libpng12-0 1.2.44-1+squeeze4 PNG library - runtime
ii  libpython2.6   2.6.6-8+b1Shared Python runtime library (ver
ii  libsdl1.2debian1.2.14-6.1Simple DirectMedia Layer
ii  libssl0.9.80.9.8o-4squeeze14 SSL shared libraries
ii  libstdc++6 4.4.5-8   The GNU Standard C++ Library v3
ii  libvncserver0  0.9.7-2+b1API to write one's own vnc server
ii  libx11-6   2:1.3.3-4 X11 client-side library
ii  libxcursor11:1.1.10-2X cursor management library
ii  libxext6   2:1.1.2-1 X11 miscellaneous extension librar
ii  libxml22.7.8.dfsg-2+squeeze7 GNOME XML library
ii  libxmu62:1.0.5-2 X11 miscellaneous utility library
ii  libxt6 1:1.0.7-1 X11 toolkit intrinsics library
ii  python 2.6.6-3+squeeze7  interactive high-level object-orie
ii  python-central 0.6.16+nmu1   register and build utility for Pyt
ii  zlib1g 1:1.2.3.4.dfsg-3  compression library - runtime

Versions of packages virtualbox-ose recommends:
ii  libgl1-mesa-glx [ 7.7.1-5A free implementation of the OpenG
ii  libqt4-opengl 4:4.6.3-4+squeeze1 Qt 4 OpenGL module
ii  libqtcore44:4.6.3-4+squeeze1 Qt 4 core module
ii  libqtgui4 4:4.6.3-4+squeeze1 Qt 4 GUI module
ii  virtualbox-ose-dk 3.2.10-dfsg-1+squeeze1 x86 virtualization solution - kern
ii  virtualbox-ose-qt 3.2.10-dfsg-1+squeeze1 x86 virtualization solution - Qt b

Versions of packages virtualbox-ose suggests:
ii  libasound2 1.0.23-2.1shared library for ALSA applicatio
ii  libpulse0  0.9.21-3+squeeze1 PulseAudio client libraries
ii  vde2   2.2.3-3   Virtual Distributed Ethernet
pn  virtualbox-guest-addit (no description available)

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: Re: Bug#455769: same problem on wheezy + Thinkpad X220T

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #455769 [gnome-power-manager] gnome-power-manager: Suspend on lid close 
only works every other time
Severity set to 'important' from 'critical'

-- 
455769: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=455769
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#455769: same problem on wheezy + Thinkpad X220T

[Julien Cristau]

Control: severity -1 important

On Thu, Mar 28, 2013 at 11:01:10 +0100, Daniel Pocock wrote:

> 
> I recently updated a Lenovo X220T to wheezy
> 
> I am using the standard wheezy kernel and gnome desktop
> 
> $ dpkg --list | grep gnome-power
> ii  gnome-power-manager  
> 3.4.0-2amd64power management tool
> for the GNOME desktop
> 
> 
> Here are my settings:
> 
> $ gsettings get org.gnome.settings-daemon.plugins.power
> lid-close-battery-action
> 'suspend'
> 
> $ gsettings get org.gnome.settings-daemon.plugins.power lid-close-ac-action
> 'suspend'
> 
> 
> So, it should always suspend when I close the lid - but sometimes it
> does not suspend
> 
> e.g. I have the laptop on my desk.  I remove the AC cable and close the
> screen, put the laptop in my backpack.  Walk to the train station, sit
> on the train, take out the laptop, it is extremely hot.
> 
> On one occasion, it was so hot that the screen had gone off and was
> non-responsive, I had to poweroff completely by holding the power button
> for 10 seconds and let it cool before I could use it again. 
> 
> I am raising this bug to critical, as it meets the definition "makes
> unrelated software on the system (or the whole system) break"

No, it does not.  hw will shut itself off before getting damaged.

Cheers,
Julien


signature.asc
Description: Digital signature

Processed: raising to critical - can damage hardware

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 455769 critical
Bug #455769 [gnome-power-manager] gnome-power-manager: Suspend on lid close 
only works every other time
Severity set to 'critical' from 'normal'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
455769: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=455769
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: severity of 702965 is grave

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> #This bug will impact everyone with extra groups and make ps and other procps 
> programs crash
> severity 702965 grave
Bug #702965 [procps] procps: ps dies with SIGSEGV on kernels > 3.2.29 and lots 
of supplementary groups
Bug #704041 [procps] procps: Signal 11 (SEGV) caught by ps (procps-ng version 
3.3.3). ps:display.c:59: please report
Severity set to 'grave' from 'normal'
Severity set to 'grave' from 'normal'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
702965: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702965
704041: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704041
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#704122: ndiswrapper-dkms: Fails to build module because of missing BUILT_MODULE_NAME

[Patrick Matthäi]

Package: ndiswrapper-dkms
Version: 1.57-1
Severity: serious
Tags: patch

Hi,

the module fails to build with dkms, because BUILT_MODULE_NAME is not defined
in the dkms.conf, here is a patch:

diff -Naur ndiswrapper-1.57.orig/debian/ndiswrapper-dkms.dkms.in 
ndiswrapper-1.57/debian/ndiswrapper-dkms.dkms.in
--- ndiswrapper-1.57.orig/debian/ndiswrapper-dkms.dkms.in   2012-03-05 
16:49:17.0 +0100
+++ ndiswrapper-1.57/debian/ndiswrapper-dkms.dkms.in2013-03-28 
10:32:28.520623214 +0100
@@ -1,4 +1,5 @@
 PACKAGE_NAME="ndiswrapper"
 PACKAGE_VERSION="@VERSION@"
+BUILT_MODULE_NAME[0]="$PACKAGE_NAME"
 DEST_MODULE_LOCATION[0]="/updates"
 AUTOINSTALL="yes"


-- 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/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#704111: clang fails to correctly implement hard float ABI during default compiles due to rediculously low default CPU setting.

[Sylvestre Ledru]

On 28/03/2013 10:16, peter green wrote:
> Sylvestre Ledru wrote:
>> No need to do a NMU here.
>>   
> Ok I've attached a diff. Note: i'm currently running a test build of
> this version i'll follow up later with results from that test to confirm
> things are ok (I don't see why they wouldn't be)
OK. Looks like you have all things set. Don't hesitate to upload without
any DELAY.
I will sync that into the svn.

Sylvestre


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#704111: clang fails to correctly implement hard float ABI during default compiles due to rediculously low default CPU setting.

[peter green]

Sylvestre Ledru wrote:

No need to do a NMU here.
  
Ok I've attached a diff. Note: i'm currently running a test build of 
this version i'll follow up later with results from that test to confirm 
things are ok (I don't see why they wouldn't be)
diff -urN clang-3.0/debian/changelog clang-3.0.new/debian/changelog
--- clang-3.0/debian/changelog	2013-02-10 14:47:29.0 +
+++ clang-3.0.new/debian/changelog	2013-03-28 09:06:53.0 +
@@ -1,3 +1,15 @@
+clang (1:3.0-6.2) unstable; urgency=low
+
+  * 29-set-default-cpu-for-armhf.diff increase default cpu for armhf builds.
+Previous absurdly low default did not work correctly with 
+-mfloat-abi=hard leading to broken code.
++ Use armv6 as new default because in clang 3.0 armv7 implies features that
+   we don't require in debian armhf (extra fpu registers and neon)
+  * 30-powerpc-no-altivec.patch disable altivec by default on powerpc because
+debian powerpc does not require altivec (patch cherry picked from ubuntu)
+
+ -- Peter Michael Green   Thu, 28 Mar 2013 09:02:01 +
+
 clang (1:3.0-6.1) unstable; urgency=low
 
   * Non-maintainer upload.
diff -urN clang-3.0/debian/patches/29-set-default-cpu-for-armhf.diff clang-3.0.new/debian/patches/29-set-default-cpu-for-armhf.diff
--- clang-3.0/debian/patches/29-set-default-cpu-for-armhf.diff	1970-01-01 00:00:00.0 +
+++ clang-3.0.new/debian/patches/29-set-default-cpu-for-armhf.diff	2013-03-28 08:47:26.0 +
@@ -0,0 +1,39 @@
+Description: Fix CPU type default for armhf
+  Without this patch clang defaults to a CPU type of "arm7tdmi" which
+  does not work correctly with -mfloat-abi=hard leading to broken
+  code.
+  
+  Use armv6 because as far as I can tell clang 3.0 does not properly 
+  support an armv7 setting without neon or the extra floating point 
+  registers. It may be possible to patch it to add support but I feel 
+  such a Patch would likely be considered unacceptable at this stage in
+  The release process.
+Author: Peter Michael Green 
+
+---
+The information above should follow the Patch Tagging Guidelines, please
+checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here
+are templates for supplementary fields that you might want to add:
+
+Origin: , 
+Bug: 
+Bug-Debian: http://bugs.debian.org/
+Bug-Ubuntu: https://launchpad.net/bugs/
+Forwarded: 
+Reviewed-By: 
+Last-Update: 
+
+Index: clang-3.0/tools/clang/lib/Driver/Tools.cpp
+===
+--- clang-3.0.orig/tools/clang/lib/Driver/Tools.cpp	2013-03-27 19:50:18.0 +
 clang-3.0/tools/clang/lib/Driver/Tools.cpp	2013-03-27 19:53:28.0 +
+@@ -442,6 +442,9 @@
+   if (Arg *A = Args.getLastArg(options::OPT_march_EQ)) {
+ // Otherwise, if we have -march= choose the base CPU for that arch.
+ MArch = A->getValue(Args);
++  } else if (Triple.getEnvironment() == llvm::Triple::GNUEABIHF) {
++// Use armv6 for armhf (raspbian version of patch)
++MArch = "armv6";
+   } else {
+ // Otherwise, use the Arch from the triple.
+ MArch = Triple.getArchName();
diff -urN clang-3.0/debian/patches/30-powerpc-no-altivec.patch clang-3.0.new/debian/patches/30-powerpc-no-altivec.patch
--- clang-3.0/debian/patches/30-powerpc-no-altivec.patch	1970-01-01 00:00:00.0 +
+++ clang-3.0.new/debian/patches/30-powerpc-no-altivec.patch	2013-03-28 09:00:48.0 +
@@ -0,0 +1,20 @@
+Description: Make sure PowerPC doesn't default to altivec on
+Author: Adam Conrad 
+Forwarded: no
+Reviewed-By: Colin Watson 
+Last-Update: 2012-04-24
+
+Index: b/tools/clang/lib/Lex/Makefile
+===
+--- a/tools/clang/lib/Lex/Makefile
 b/tools/clang/lib/Lex/Makefile
+@@ -16,9 +16,5 @@
+ 
+ LIBRARYNAME := clangLex
+ 
+-ifeq ($(ARCH),PowerPC)
+-CXX.Flags += -maltivec
+-endif
+-
+ include $(CLANG_LEVEL)/Makefile
+ 
diff -urN clang-3.0/debian/patches/series clang-3.0.new/debian/patches/series
--- clang-3.0/debian/patches/series	2013-02-06 12:53:12.0 +
+++ clang-3.0.new/debian/patches/series	2013-03-28 09:01:26.0 +
@@ -9,3 +9,5 @@
 26-set-correct-float-abi.diff
 27-dynamic-linker.diff
 28-gcc-4.7.diff
+29-set-default-cpu-for-armhf.diff
+30-powerpc-no-altivec.patch

Bug#703146: debootstrap patch disabling InRelease handling

[Didier 'OdyX' Raboud]

Hi Julien,

FYI, I have tested the patch disabling InRelease handling as pushed to 
debootstrap's git in two situations:

* standard package; debootstrap a wheezy chroot: OK
* d-i environment (built mini.iso, installed debootstrap-udeb in it): OK

Cheers,

OdyX


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#696727: some more device informations

[Andreas B. Mundt]

Hi again,

I collected a bit more information about the device:

  andi@fuzi:~$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 004: ID 045e:00f7 Microsoft Corp. LifeCam VX-1000 <= works fine
Bus 002 Device 002: ID 5986:01a6 Acer, Inc Lenovo Integrated Webcam <= fails

Attached is the detailed output of lsusb -v for the cams.  I had the
integrated cam working some time ago, but no idea when it failed the
first time, as I do not need it usually.  Kernel issue?

Best regards,

 Andi
Bus 003 Device 004: ID 045e:00f7 Microsoft Corp. LifeCam VX-1000
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   1.10
  bDeviceClass0 (Defined at Interface level)
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMaxPacketSize064
  idVendor   0x045e Microsoft Corp.
  idProduct  0x00f7 LifeCam VX-1000
  bcdDevice1.01
  iManufacturer   0
  iProduct1 USB camera
  iSerial 0
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength  382
bNumInterfaces  3
bConfigurationValue 1
iConfiguration  0
bmAttributes 0x80
  (Bus Powered)
MaxPower  500mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   3
  bInterfaceClass   255 Vendor Specific Class
  bInterfaceSubClass255 Vendor Specific Subclass
  bInterfaceProtocol255 Vendor Specific Protocol
  iInterface  0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81  EP 1 IN
bmAttributes1
  Transfer TypeIsochronous
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x  1x 0 bytes
bInterval   1
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82  EP 2 IN
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0040  1x 64 bytes
bInterval   0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83  EP 3 IN
bmAttributes3
  Transfer TypeInterrupt
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0001  1x 1 bytes
bInterval 100
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   1
  bNumEndpoints   3
  bInterfaceClass   255 Vendor Specific Class
  bInterfaceSubClass255 Vendor Specific Subclass
  bInterfaceProtocol255 Vendor Specific Protocol
  iInterface  0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81  EP 1 IN
bmAttributes1
  Transfer TypeIsochronous
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0080  1x 128 bytes
bInterval   1
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82  EP 2 IN
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0040  1x 64 bytes
bInterval   0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83  EP 3 IN
bmAttributes3
  Transfer TypeInterrupt
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0001  1x 1 bytes
bInterval 100
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   2
  bNumEndpoints   3
  bInterfaceClass   255 Vendor Specific Class
  bInterfaceSubClass255 Vendor Specific Subclass
  bInterfaceProtocol255 Vendor Specific Protocol
  iInterface  0
  Endpoint Descriptor:
 

Processed: serverity

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity #702251 serious
Bug #702251 [otrs2] otrs2: upgrade fails from 3.1.11 to 3.2.2
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
702251: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702251
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#696727: ~ Re: Bug#696727: cheese does not start with Gtk-Warning

[Jonathan Dowland]

On 27 Mar 2013, at 23:41, John Paul Adrian Glaubitz 
 wrote:

> could anyone who is seeing the issue with Cheese freezing try to disconnect 
> their webcam

In my case I don't think so- it's built into the frame of my laptop screen.

--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 703332 1:1.0~git20111214-1
Bug #703332 [libactiviz.net-cil] If they are API compatible you MUST generate 
and install a GAC policy file!
Marked as found in versions activiz.net/1:1.0~git20111214-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
703332: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703332
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#704111: [cfe-dev] Bug#704111: clang fails to correctly implement hard float ABI during default compiles due to rediculously low default CPU setting.

[Anton Korobeynikov]

> 2: If noone can provide an answer to the above question then taking into the
> account how late we are in the freeze should we play it safe and specify a
> lower (armv6) CPU version to make sure that neon and the extra vfp registers
> don't get accidently used. I personally think that the answer is yes but I'm
> open to arguments.
Given that 3.0 is pretty old (~1.5 year) LLVM version you can do with
debian-provided version whatever you want. I doubt anyone cares here
now about that old version.

ARM (especially hardware FP) support is known to contain many problems
in that old version. The recent LLVM 3.2 release provides proper
hardware FP support out of the box.

cortex-a8 indeed by default implies full vfp and NEON. This seems to
be reasonable default for ARMv7.

--
With best regards, Anton Korobeynikov
Faculty of Mathematics and Mechanics, Saint Petersburg State University


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#704111: [cfe-dev] Bug#704111: clang fails to correctly implement hard float ABI during default compiles due to rediculously low default CPU setting.

[Tim Northover]

Hi Peter,

> 1: What does the "coretex-a8" CPU setting imply for clang/llvm? in
> particular does it imply neon and the extra vfp registers?

At the LLVM level, the options that have to be enabled are "NEON" and
"restrict to 16 registers". Looking at (Clang's) lib/Basic/Targets.cpp
from 3.0 (and current). Cortex-A8 defaults to NEON enabled and using
all registers.

The option you ideally want to be using is "-mfpu". In current Clang,
this can have the value "vfpv3-d16", which disables NEON and restricts
to 16 registers, which sounds like exactly what you want.
Unfortunately this doesn't seem to exist in 3.0.

Backporting it would be a relatively simple feat. The following block
in addFPUArgs in lib/Driver/Tools.cpp implements it:
  } else if (FPU == "vfp3-d16" || FPU == "vfpv3-d16") {
CmdArgs.push_back("-target-feature");
CmdArgs.push_back("+vfp3");
CmdArgs.push_back("-target-feature");
CmdArgs.push_back("+d16");
CmdArgs.push_back("-target-feature");
CmdArgs.push_back("-neon");
  }

The one risk I see is that trunk LLVM contains two references to
hasD16, but 3.0 only refers to it once. The common reference is the
obvious place to implement the limit in LLVM. The second could mean
extra functionality was added which relies on the extra registers, or
it could mean there was a latent bug in 3.0 (around lowering
ConstantFPs). I can't really tell without more detailed investigation.

Hope this helps.

Tim.


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#704111: clang fails to correctly implement hard float ABI during default compiles due to rediculously low default CPU setting.

[Sylvestre Ledru]

On 28/03/2013 06:31, peter green wrote:
> Ok I just had a discussion with adam conrad about this on IRC.
> 
> According to him clang currently does assume that armv7 means coretex a8
> and that coretex a8 mean full vfpv3 and neon. There is a patch in ubuntu
> precise/quantal to fix this  (26-armv7-not-neon.patch) but it's a pretty
> big patch and is self-described as a hideous hack. I doubt the release
> team would accept such a patch at this stage. Therefore it seems the
> only reasonable thing to do is to select armv6 for clang on armhf in
> wheezy.
> 
> He also alerted me to a patch that disables altivec by default on
> powerpc since not all powerpc hardware debian supports has altivec. I
> intend to include this in the proposed NMU, a copy of it is attached.
> 
> Since I now have confirmation on what clang does i'll prepare the NMU
> diff in a day or two.
No need to do a NMU here.

I can upload it right now.
S


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#696727: external cam works, builtin fails

[Andreas B. Mundt]

Hi,

indeed, a USB attached cam works fine here whereas the builtin laptop
camera fails completely: I have exactly the symptoms described here -- 
no cheese at all, process "hanging".  

If I run cheese with the USB cam pluged in and switch to the builtin cam 
within the cheese preferences menu, the application locks up.

Best regards,  

Andi


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#704114: asterisk: asterisk security advisories: AST-2013-001 / AST-2013-002 / AST-2013-003

[Tzafrir Cohen]

On Thu, Mar 28, 2013 at 06:23:32AM +0100, Salvatore Bonaccorso wrote:
> Package: asterisk
> Severity: grave
> Tags: security patch upstream
> 
> Hi,
> 
> the following vulnerabilities were published for asterisk.
> 
> CVE-2013-2685[0]:
> Buffer Overflow Exploit Through SIP SDP Header
> 
> CVE-2013-2686[1]:
> Denial of Service in HTTP server
> 
> CVE-2013-2264[2]:
> Username disclosure in SIP channel driver
> 
> For CVE-2013-2685 the tracker[3] mentions only 1.11.x. Could you
> doublecheck that squeeze, testing and wheezy are not affected?

According to the Upstream advisories, both are in effect for 1.8 .
Didn't yet check backporting it (to our 1.8 in Testing/Unstable) and to
1.6.2 in Stable.

> 
> If you fix the vulnerabilities please also make sure to include the
> CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.
> 
> For further information see:
> 
> [0] http://security-tracker.debian.org/tracker/CVE-2013-2685
> http://downloads.asterisk.org/pub/security/AST-2013-001.html
> [1] http://security-tracker.debian.org/tracker/CVE-2013-2686
> http://downloads.asterisk.org/pub/security/AST-2013-002.html
> [2] http://security-tracker.debian.org/tracker/CVE-2013-2264
> http://downloads.asterisk.org/pub/security/AST-2013-003.html
> [3] https://issues.asterisk.org/jira/browse/ASTERISK-20901
> 
> Please adjust the affected versions in the BTS as needed.

-- 
   Tzafrir Cohen
icq#16849755  jabber:tzafrir.co...@xorcom.com
+972-50-7952406   mailto:tzafrir.co...@xorcom.com
http://www.xorcom.com  iax:gu...@local.xorcom.com/tzafrir


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org