Bug#782370: libgtk-3-0:amd64: Mouse movement on a clickpad-style touchpad is interpreted as touchscreen-like panning

[Ondrej Grover]

Package: libgtk-3-0
Version: 3.14.5-1
Severity: important
Tags: newcomer

Dear Maintainer,

In GTK3 apps (Evince, Meld) move movement on my clickpad-style touchpad are
interpreted as touchscreen-like panning of the document or source file. It also
interferes with two finger scrolling. Circular scrolling works though. A normal
USB mouse works well, including scrolling.

This bug is similar to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=716959
and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766707 (the latter
appears to be a duplicate of the former)
and exporting GDK_CORE_DEVICE_EVENTS=1 solves it.

I've attached a log of running
GDK_DEBUG=event evince file.pdf



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

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libgtk-3-0:amd64 depends on:
ii  libatk-bridge2.0-0   2.14.0-2
ii  libatk1.0-0  2.14.0-1
ii  libc62.19-17
ii  libcairo-gobject21.14.0-2.1
ii  libcairo21.14.0-2.1
ii  libcolord2   1.2.1-1+b2
ii  libcups2 1.7.5-11
ii  libfontconfig1   2.11.0-6.3
ii  libfreetype6 2.5.2-3
ii  libgdk-pixbuf2.0-0   2.31.1-2+b1
ii  libglib2.0-0 2.42.1-1
ii  libgtk-3-common  3.14.5-1
ii  libjson-glib-1.0-0   1.0.2-1
ii  libpango-1.0-0   1.36.8-3
ii  libpangocairo-1.0-0  1.36.8-3
ii  libpangoft2-1.0-01.36.8-3
ii  librest-0.7-00.7.92-3
ii  libsoup2.4-1 2.48.0-1
ii  libwayland-client0   1.6.0-2
ii  libwayland-cursor0   1.6.0-2
ii  libx11-6 2:1.6.2-3
ii  libxcomposite1   1:0.4.4-1
ii  libxcursor1  1:1.1.14-1+b1
ii  libxdamage1  1:1.1.4-2+b1
ii  libxext6 2:1.3.3-1
ii  libxfixes3   1:5.0.1-2+b2
ii  libxi6   2:1.7.4-1+b2
ii  libxinerama1 2:1.1.3-1+b1
ii  libxkbcommon00.4.3-2
ii  libxml2  2.9.1+dfsg1-5
ii  libxrandr2   2:1.4.2-1+b1
ii  multiarch-support2.19-17
ii  shared-mime-info 1.3-1

Versions of packages libgtk-3-0:amd64 recommends:
ii  hicolor-icon-theme  0.13-1
ii  libgtk-3-bin3.14.5-1

Versions of packages libgtk-3-0:amd64 suggests:
pn  gvfs 
ii  librsvg2-common  2.40.5-1

-- no debconf information
Gdk-Message: property notify:   window: 46137345, atom(34): "WM_COMMAND"
Gdk-Message: property notify:   window: 46137345, atom(36): "WM_CLIENT_MACHINE"
Gdk-Message: property notify:   window: 46137345, atom(67): "WM_CLASS"
Gdk-Message: property notify:   window: 46137345, atom(318): "WM_LOCALE_NAME"
Gdk-Message: property notify:   window: 46137345, atom(313): "_NET_WM_PID"
Gdk-Message: property notify:   window: 46137345, atom(342): "_NET_STARTUP_ID"
Gdk-Message: property notify:   window: 46137345, atom(314): "_NET_WM_NAME"
Gdk-Message: property notify:   window: 46137345, atom(39): "WM_NAME"
Gdk-Message: property notify:   window: 46137353, atom(312): "_MOTIF_WM_HINTS"
Gdk-Message: property notify:   window: 46137353, atom(714): 
"_NET_WM_OPAQUE_REGION"
Gdk-Message: property notify:   window: 46137353, atom(716): 
"_GTK_UNIQUE_BUS_NAME"
Gdk-Message: property notify:   window: 46137353, atom(717): 
"_GTK_APPLICATION_OBJECT_PATH"
Gdk-Message: property notify:   window: 46137353, atom(718): 
"_GTK_WINDOW_OBJECT_PATH"
Gdk-Message: property notify:   window: 46137353, atom(719): 
"_GTK_APP_MENU_OBJECT_PATH"
Gdk-Message: property notify:   window: 46137353, atom(317): "_NET_WM_ICON"
Gdk-Message: property notify:   window: 46137353, atom(444): "XdndAware"
Gdk-Message: property notify:   window: 46137353, atom(359): "_NET_WM_USER_TIME"
Gdk-Message: property notify:   window: 46137353, atom(714): 
"_NET_WM_OPAQUE_REGION"
Gdk-Message: configure notify:  window: 46137353  x,y: 0 0  w,h: 600 600  
b-w: 0  above: 46137348ovr: 0
Gdk-Message: property notify:   window: 46137353, atom(40): "WM_NORMAL_HINTS"
Gdk-Message: property notify:   window: 46137353, atom(35): "WM_HINTS"
Gdk-Message: configure notify:  window: 46137353  x,y: 0 0  w,h: 600 600  
b-w: 0  above: 46137371ovr: 0
Gdk-Message: destroy notify:window: 46137371
Gdk-Message: reparent notify:   window: 46137353  x,y: 0 0  parent: 10487098
ovr: 0
Gdk-Message: configure notify:  window: 46137353  x,y: 2 2  w,h: 956 1076  
b-w: 0  above: 0  ovr: 0
Gdk-Message: property notify:   window: 46137353, atom(328): "WM_STATE"
Gdk-Message: map notify:window: 46137353
Gdk-Message: visibility notify: window: 46137353 full
Gdk-Message: expose:window: 46137353  0 x,y: 0 0  w,h: 956 1076
Gdk-Message: configure notify:  window: 46137353  x,y: 962 2w,h: 956 1076  
b-w: 0  above: 0  ovr: 0
Gdk-Message: focus out: window

Bug#782369: right there on the man page please mention that ascii2uni -a R will not work

[Dan Jacobson]

X-debbugs-Cc: Bill Poser 
Package: uni2ascii
Version: 4.18-2
Severity: minor

Man page says

 R Convert raw hexadecimal numbers (e.g. 00E9)

however when we try it,

$ echo 00E9|ascii2uni -a R
It isn't possible reliably to parse raw hex unicode out of ASCII text.

it turns out to be a big bait and switch operation! Please mention the
problem on the man page at that line lest one expect it to work.


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

Bug#780573: release-notes: Review from the d-i team

[Baptiste Jammet]

Hello, 

Dixit Niels Thykier, le 16/03/2015 :

>I am contacting you to do a final review of the release-notes for the
>d-i related topics (as listed on [1]):

Here are some items I think it's important to highlight, taken from d-i
release announces.
I tried to clean the page a bit and mark some old stuff as wheezy.
Please review because I'm not a native english, and I surely forgot
some important changes.

Baptiste

P.S. diff against installing.dbk r10511
--- installing.dbk	2014-12-14 19:10:38.058786385 +0100
+++ installing-bj.dbk	2015-04-04 14:33:04.231032879 +0200
@@ -53,36 +53,20 @@
 release-notes authors should check webwml repo or
 http://www.debian.org/devel/debian-installer/
 
-Sources (for wheezy): 
+Sources (for Jessie): 
 
-http://www.debian.org/devel/debian-installer/News/2012/20121122  (7.0 Beta4)
-http://www.debian.org/devel/debian-installer/News/2013/20130217  (7.0 RC1)
-
-http://www.debian.org/devel/debian-installer/
-
-(
-
-http://wiki.debian.org/DebianInstaller/ReleaseAnnounce tends to be filled
-shortly before the release, and renamed right afterwards.  The time window for
-its being interesting is like a few hours.
-
-)
+https://www.debian.org/devel/debian-installer/News/2014/20140319
+https://www.debian.org/devel/debian-installer/News/2014/20140813
+https://www.debian.org/devel/debian-installer/News/2014/20141005
+https://www.debian.org/devel/debian-installer/News/2015/20150126
+https://www.debian.org/devel/debian-installer/News/2015/20150327
 
 -->
 
 
 
@@ -100,15 +84,28 @@
 
 
 
+
+
+Removed ports
+
+
+Support for the 'ia64' and 'sparc' architectures has been dropped from the installer since
+they have been removed from the archive.
+
+
+
+
 
 New ports
+
 
 
-Support for the 'armhf' and 's390x' architectures has been added to the installer.
+Support for the 'arm64' and 'pp64el' architectures has been added to the installer.
 
 
 
 
+
 
 Software speech support
 
@@ -122,6 +119,50 @@
 
 
 
+
+
+New default init system
+
+
+The installation system now installs systemd as the default init system.
+
+
+
+
+
+
+Desktop selection
+
+
+Desktop can now be choosen within tasksel during the installation. Note that
+several desktops can be selected at the same time, but some combinations of
+desktops may not be co-installable.
+
+
+
+
+
+Replacing "--" by "---" for boot parameters
+
+
+Due to a change on the linux kernel side, the "---" separator is now used instead 
+of the historical "--" one to separate kernel parameters from userland parameters.
+
+
+
+
+
+
+Graphical installer
+
+
+Graphical installer is now the default on supported platforms.
+Text installer is still accessible from the very first menu, or if
+the system has limited capabilities.
+
+
+
+
 
 New supported platforms
 
@@ -172,9 +213,10 @@
 
 New languages
 
+
 
-Thanks to the huge efforts of translators, &debian; can now be installed in 74
-languages, including English.  This is three more languages than in &oldreleasename;.
+Thanks to the huge efforts of translators, &debian; can now be installed in 75
+languages, including English.  This is two more languages than in &oldreleasename;.
 Most languages are available in both the text-based installation
 user interface and the graphical user interface, while some
 are only available in the graphical user interface. 
@@ -185,12 +227,14 @@
 
 
 
+
 
 
 Welsh has been re-added to the graphical and
 text-based installer (it had been removed in &oldreleasename;).
 
 
+
 
 
 Tibetan and Uyghur have been added to the graphical installer.
@@ -198,7 +242,7 @@
 
 
 
-
+
 
 The languages that can only be selected using the graphical installer as their
 character sets cannot be presented in a non-graphical environment are: Amharic,
@@ -208,6 +252,7 @@
 
 
 
+
 
   Network configuration
   
@@ -220,6 +265,7 @@
   
 
 
+
 
   Default filesystem
   
@@ -234,6 +280,7 @@
   
 
 
+
 
   UEFI boot
   


signature.asc
Description: PGP signature

Bug#768500: closed by Felipe Sateler (Bug#768500: fixed in pavucontrol 3.0-1)

[Adam Majer]

On Sat, Apr 11, 2015 at 03:24:06AM +, Debian Bug Tracking System wrote:
>  pavucontrol (3.0-1) experimental; urgency=medium
>  .
>* New upstream release. Closes: #781104
>  - Drop all patches: applied upstream
>  - Doesn't expand forever. Closes: #768500

Thank you!!

- Adam


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

Bug#782368: xastir: [INTL:ru] Russian debconf templates translation

[Yuri Kozlov]

Package: xastir
Version: 2.0.6-2
Severity: wishlist
Tags: l10n patch

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***

Russian debconf templates translation is attached.

-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf, armel

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)


ru.po.gz
Description: application/gzip

Bug#782367: ITP: python-psycogreen -- psycopg2 integration with coroutine libraries

[Dmitry Smirnov]

Package: wnpp
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org

   Package name: python-psycogreen
Version: 1.0
Upstream Author: Daniele Varrazzo 
  Copyright: 2010-2012, Daniele Varrazzo
License: BSD-3-clause
URL: https://pypi.python.org/pypi/psycogreen
Vcs-Browser: 
http://anonscm.debian.org/cgit/collab-maint/python-psycogreen.git
Description: psycopg2 integration with coroutine libraries
 This package enables "psycopg2" to work with coroutine libraries, using
 asynchronous calls internally but offering a blocking interface so that
 regular code can run unmodified.

"python-psycogreen" is a dependency of Odoo.

-- 
Cheers,
 Dmitry Smirnov.


signature.asc
Description: This is a digitally signed message part.

Bug#367715: ppp: overwrites /etc/resolv.conf despite "usepeerdns" being unset

[Paulo Roberto Evangelista]

This problem can be solved running the command below

apt-get install resolvconf

Bug#378363: /etc/ppp/ip-down.d/0000usepeerdns bug?

[Paulo Roberto Evangelista]

this problem can be solved running the command below

apt-get install resolvconf

Bug#782058: Pegasos II: installer boots up to 'returning from prom_init'

[Milan Kupcevic]

On 04/10/2015 06:05 PM, Ben Hutchings wrote:
> On Fri, 2015-04-10 at 17:39 -0400, Milan Kupcevic wrote:
>> On 04/09/2015 08:21 AM, Ben Hutchings wrote:
>> [...]
>>
>>>
>>> It isn't reverted.  All I've done is to add radeonfb.ko to the drivers
>>> that are included *in the installer*.
>>>
>>> Neither radeon.ko nor xserver-xorg-video-radeon are included in the
>>> installer, so how could they possibly be used?  If you though those
>>> should be used in the installer, you should have told people that
>>> earlier.
>>>
>>> As it is, I think that the installer should be able to work using
>>> radeonfb.ko and xserver-xorg-video-fbdev, though I'm not sure whether
>>> radeonfb.ko will be loaded automatically.
>>>
>>> Ben.
>>>
>>
>> The module landed in sid D-I. It gets loaded automatically as it is not
>> blacklisted in D-I. I've been able to boot and run the installer on an
>> XServe G4 DP, a G4 Mac Mini, and a Pegasos II. All three machines have
>> radeon cards.
> 
> Using the graphical or text-based installer?
> 
> Ben.
> 

Using text-based installer. I do not remember when I last time saw
graphical installer on PowerPC platform. As far as I know there is no
graphical installer on this platform for very long time. It seems no one
is even trying to make it work.

Milan






signature.asc
Description: OpenPGP digital signature

Bug#782362: Regression: 3.16.7-ckt9-1: mouning rootpartition cause a deadlock at mount time

[Ben Hutchings]

Control: tag -1 patch moreinfo

On Sat, 2015-04-11 at 01:30 +0300, Lebedev Roman wrote:
> Package: src:linux
> Version: 3.16.7-ckt9-1
> Severity: important
> 
> Dear Maintainer,
> 
> kernel version 3.16.7-ckt9-1 is broken, a deadlock at mount time happens in 
> BTRFS.
> Previous kernel version (which i'm using right now to report this) - 
> 3.16.7-ckt7-1 is fine.
> 
> This is a known upstream issue:
> >From https://btrfs.wiki.kernel.org/index.php/Gotchas
> * Stable kernel version 3.19.1+ can cause a deadlock at mount time
> * * workaround: boot with older kernel, or run btrfs-zero-log to clear the 
> log (beware of the consequences)
> * * fix: scheduled for 3.19.4, or apply 9c4f61f01d269815bb7c37.
> * * also affected: 3.14.35+, 3.18.9+
> 
> I consider this issue to be of "grave" severity, but only for those using 
> BTRFS.
> 
> Please fix this.
> (either backport that patch or revert to previous kernel (3.16.7-ckt7-1) or 
> drop the patches that cause this)
> 
> NOTE: i have already downgraded to ckt7 to report this, so all the lines 
> below are for ckt7, not ckt9.

Please test a kernel package built with this patch added:
https://people.debian.org/~benh/packages/linux-image-3.16.0-4-amd64_3.16.7-ckt9-2~bwh.1_amd64.deb

The sha256sum of that file is:
f6f194e841341a8e837fac9d53c0a82b2b7e77cb31807784167869a1c97058b7  
linux-image-3.16.0-4-amd64_3.16.7-ckt9-2~bwh.1_amd64.deb

Ben.

-- 
Ben Hutchings
compatible: Gracefully accepts erroneous data from any source
From: David Sterba 
Date: Fri, 2 Jan 2015 19:12:57 +0100
Subject: btrfs: simplify insert_orphan_item
Origin: https://git.kernel.org/linus/9c4f61f01d269815bb7c37be3ede59c5587747c6
Bug-Debian: https://bugs.debian.org/782362

We can search and add the orphan item in one go,
btrfs_insert_orphan_item will find out if the item already exists.

Signed-off-by: David Sterba 
---
 fs/btrfs/tree-log.c | 16 
 1 file changed, 4 insertions(+), 12 deletions(-)

--- a/fs/btrfs/tree-log.c
+++ b/fs/btrfs/tree-log.c
@@ -1263,21 +1263,13 @@ out:
 }
 
 static int insert_orphan_item(struct btrfs_trans_handle *trans,
-			  struct btrfs_root *root, u64 offset)
+			  struct btrfs_root *root, u64 ino)
 {
 	int ret;
-	struct btrfs_path *path;
 
-	path = btrfs_alloc_path();
-	if (!path)
-		return -ENOMEM;
-
-	ret = btrfs_find_item(root, path, BTRFS_ORPHAN_OBJECTID,
-			offset, BTRFS_ORPHAN_ITEM_KEY, NULL);
-	if (ret > 0)
-		ret = btrfs_insert_orphan_item(trans, root, offset);
-
-	btrfs_free_path(path);
+	ret = btrfs_insert_orphan_item(trans, root, ino);
+	if (ret == -EEXIST)
+		ret = 0;
 
 	return ret;
 }


signature.asc
Description: This is a digitally signed message part

Bug#782366: libcunit1-dev: pkg-config file is broken

[Colomban Wendling]

Package: libcunit1-dev
Version: 2.1-2.dfsg-2
Severity: important
Tags: patch

Dear Maintainer,

The pkg-config file distributed with libcunit1-dev is broken:

1. it has no "Version" field, which makes pkg-config error-out:

   $ pkg-config --libs cunit
   Package 'cunit' has no Version: field

   Fixing this only requires adding a "Version: 2.1" (or alike) field.

2. its "libdir" variable misses a "$" to expand "exec_prefix", leading
   to a literal "{exec_prefix}":

   $ pkg-config --libs cunit
   -L\{exec_prefix\}/lib -lcunit

   Fixing this is even easier, just add the missing "$":

   libdir=${exec_prefix}/lib


After fixing these two issues, the pkg-config file seem to work nicely
-- to my limited cunit knowledge, all I needed was building something
using it.

Interestingly apparently the source file debian/cunit.pc contains the
issues, but what I can only assume is the upstream template,
cunit.pc.in, does not suffer from the issues.

Maybe simply distributing upstream's version would fix it, but note it
has a difference: it adds "/usr/include" to the search path, not
"/usr/include/CUnit".  Presumably upstream expects users to list the
prefix "CUnit/" in their includes -- and the package I tried to build
did just that.  If this is a problem, a patch could be added to add
both paths, keeping compatibility with both sides -- but as the current
pkg-config file in Debian does not work, I doubt it is a real problem.

Regards,
Colomban

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

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libcunit1-dev depends on:
ii  libcunit1  2.1-2.dfsg-2

libcunit1-dev recommends no packages.

Versions of packages libcunit1-dev suggests:
pn  libcunit1-doc  

-- no debconf information
From: Colomban Wendling 
Date: Sat Apr 11 02:44:06 2015 +0200
Subject: Fix pkg-config file

diff -Nur cunit-2.1-2.dfsg.old/debian/cunit.pc cunit-2.1-2.dfsg/debian/cunit.pc
--- cunit-2.1-2.dfsg.old/debian/cunit.pc	2015-04-11 02:06:05.569044199 +0200
+++ cunit-2.1-2.dfsg/debian/cunit.pc	1970-01-01 01:00:00.0 +0100
@@ -1,9 +0,0 @@
-prefix=/usr
-exec_prefix=${prefix}
-libdir={exec_prefix}/lib
-includedir=${prefix}/include/CUnit
-
-Name: CUnit
-Description: The C Unit Test Library
-Libs: -L${libdir} -lcunit
-CFlags: -I${includedir}
diff -Nur cunit-2.1-2.dfsg.old/debian/libcunit1-dev.install cunit-2.1-2.dfsg/debian/libcunit1-dev.install
--- cunit-2.1-2.dfsg.old/debian/libcunit1-dev.install	2015-04-11 02:06:05.569044199 +0200
+++ cunit-2.1-2.dfsg/debian/libcunit1-dev.install	2015-04-11 02:22:03.547971399 +0200
@@ -1,5 +1,5 @@
-debian/tmp-cunit/usr/include   usr
-debian/tmp-cunit/usr/lib/lib*.ausr/lib
-debian/tmp-cunit/usr/lib/lib*.so   usr/lib
-debian/tmp-cunit/usr/share/man/man3usr/share/man
-debian/cunit.pcusr/lib/pkgconfig
+debian/tmp-cunit/usr/include  usr
+debian/tmp-cunit/usr/lib/lib*.a   usr/lib
+debian/tmp-cunit/usr/lib/lib*.so  usr/lib
+debian/tmp-cunit/usr/share/man/man3   usr/share/man
+debian/tmp-cunit/usr/lib/pkgconfig/cunit.pc   usr/lib/pkgconfig
diff -Nur cunit-2.1-2.dfsg.old/debian/libcunit1-ncurses-dev.install cunit-2.1-2.dfsg/debian/libcunit1-ncurses-dev.install
--- cunit-2.1-2.dfsg.old/debian/libcunit1-ncurses-dev.install	2015-04-11 02:06:05.569044199 +0200
+++ cunit-2.1-2.dfsg/debian/libcunit1-ncurses-dev.install	2015-04-11 02:21:32.620005868 +0200
@@ -1,5 +1,5 @@
-debian/tmp-cunit-ncurses/usr/include   usr
-debian/tmp-cunit-ncurses/usr/lib/lib*.ausr/lib
-debian/tmp-cunit-ncurses/usr/lib/lib*.so   usr/lib
-debian/tmp-cunit-ncurses/usr/share/man/man3usr/share/man
-debian/cunit.pcusr/lib/pkgconfig
+debian/tmp-cunit-ncurses/usr/include  usr
+debian/tmp-cunit-ncurses/usr/lib/lib*.a   usr/lib
+debian/tmp-cunit-ncurses/usr/lib/lib*.so  usr/lib
+debian/tmp-cunit-ncurses/usr/share/man/man3   usr/share/man
+debian/tmp-cunit-ncurses/usr/lib/pkgconfig/cunit.pc   usr/lib/pkgconfig

Bug#782365: gxine crashes at start

[Christoph Anton Mitterer]

Package: gxine
Version: 0.5.908-3.1
Severity: grave
Justification: renders package unusable


Hey.

gxine crashes immediately when stargin:

$ gxine
gxine has suffered a fatal internal error.
To get a backtrace, run gxine in a debugger such as gdb.
gxine: error: Fatal error: Segmentation fault
Then, when the error occurs:
  (gdb) thread apply all bt
^C
calestyo@heisenberg:~$ gdb gxine
GNU gdb (Debian 7.7.1+dfsg-5) 7.7.1
Copyright (C) 2014 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 "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from gxine...(no debugging symbols found)...done.
(gdb) thread apply all bt
(gdb) run
Starting program: /usr/bin/gxine 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x77fea700 (LWP 30146)]
[New Thread 0x77fac700 (LWP 30147)]
[New Thread 0x77f8b700 (LWP 30148)]
[New Thread 0x7fffede8d700 (LWP 30149)]
[New Thread 0x7fffed65e700 (LWP 30150)]

Program received signal SIGSEGV, Segmentation fault.
__GI___pthread_mutex_lock (mutex=0x7fffabe0)
at ../nptl/pthread_mutex_lock.c:66
66  ../nptl/pthread_mutex_lock.c: No such file or directory.
(gdb) thread apply all bt

Thread 6 (Thread 0x7fffed65e700 (LWP 30150)):
#0  pthread_cond_wait@@GLIBC_2.3.2 ()
at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x70da36c0 in PR_WaitCondVar ()
   from /usr/lib/x86_64-linux-gnu/libnspr4.so
#2  0x7671c556 in ?? () from /usr/lib/libmozjs185.so.1.0
#3  0x70da8fa8 in ?? () from /usr/lib/x86_64-linux-gnu/libnspr4.so
#4  0x74a2e0a4 in start_thread (arg=0x7fffed65e700)
at pthread_create.c:309
#5  0x7476304d in clone ()
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 5 (Thread 0x7fffede8d700 (LWP 30149)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 ()
at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238
#1  0x77b7e6ce in ?? () from /usr/lib/libxine.so.2
#2  0x74a2e0a4 in start_thread (arg=0x7fffede8d700)
at pthread_create.c:309
#3  0x7476304d in clone ()
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 4 (Thread 0x77f8b700 (LWP 30148)):
#0  0x747565dd in read () at ../sysdeps/unix/syscall-template.S:81
---Type  to continue, or q  to quit---
#1  0x746f23f0 in _IO_new_file_underflow (fp=0x7fffe8c0)
at fileops.c:605
#2  0x746e7e45 in _IO_getdelim (lineptr=0x77f8aca0, 
n=0x77f8aca8, delimiter=10, fp=0x7fffe8c0) at iogetdelim.c:77
#3  0x00413f02 in ?? ()
#4  0x74a2e0a4 in start_thread (arg=0x77f8b700)
at pthread_create.c:309
#5  0x7476304d in clone ()
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 3 (Thread 0x77fac700 (LWP 30147)):
#0  0x747565dd in read () at ../sysdeps/unix/syscall-template.S:81
#1  0x746f23f0 in _IO_new_file_underflow (fp=0x7fffe80008c0)
at fileops.c:605
#2  0x746e7e45 in _IO_getdelim (lineptr=0x77fabca0, 
n=0x77fabca8, delimiter=10, fp=0x7fffe80008c0) at iogetdelim.c:77
#3  0x00413f02 in ?? ()
#4  0x74a2e0a4 in start_thread (arg=0x77fac700)
at pthread_create.c:309
#5  0x7476304d in clone ()
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x77fea700 (LWP 30146)):
#0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
---Type  to continue, or q  to quit---
#1  0x75d5653c in g_cond_wait (cond=cond@entry=0x66f988, 
mutex=mutex@entry=0x66f980)
at /tmp/buildd/glib2.0-2.42.1/./glib/gthread-posix.c:1396
#2  0x75ce6aab in g_async_queue_pop_intern_unlocked (
queue=queue@entry=0x66f980, wait=wait@entry=1, end_time=end_time@entry=-1)
at /tmp/buildd/glib2.0-2.42.1/./glib/gasyncqueue.c:419
#3  0x75ce6f17 in g_async_queue_pop (queue=0x66f980)
at /tmp/buildd/glib2.0-2.42.1/./glib/gasyncqueue.c:453
#4  0x00413d14 in ?? ()
#5  0x74a2e0a4 in start_thread (arg=0x77fea700)
at pthread_create.c:309
#6  0x7476304d in clone ()
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x77fae980 (LWP 30142)):
#0  __GI___pthread_mutex_lock (mutex=0x7fffabe0)
at ../nptl/pthread_mutex_lock.c:66
#1  0x757ca3ba in XrmQGetResource ()
   from /usr/lib/x86_64-linux-gnu/libX11.so.6
#2  0x00

Bug#761023: bb: Visual stops when audio starts under pulseaudio

[Anthony DeRobertis]

Package: bb
Followup-For: Bug #761023

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

If you do a README.Debian update to fix that typo, here is another
thing to add—this makes bb work on my PA system:

pasuspender -- env PULSE_SERVER= bb

pasuspender makes PulseAudio release the sound hardware, then setting
PULSE_SERVER= to blank makes bb not connect to PA (falling back to ALSA
instead, which works).

- -- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (500, 'testing'), (130, 'unstable'), (120, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages bb depends on:
ii  libaa1  1.4p5-43
ii  libc6   2.19-17
ii  libmikmod3  3.3.7-1
ii  oss-compat  6

bb recommends no packages.

bb suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iEYEARECAAYFAlUoXPIACgkQ+z+IwlXqWf4jhACgisipycEFHwdCVlA1kxQtyW6C
M2wAniiFqSHa+qvDUub6sRTO6bcpleLg
=/Yoz
-END PGP SIGNATURE-


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

Bug#782364: linux-image-3.16.0-4-armmp: please configure drivers for both Cubox i4pro real time clocks

[Ben Hutchings]

Control: severity -1 important

On Fri, 2015-04-10 at 16:28 -0700, Rick Thomas wrote:
> Package: src:linux
> Version: 3.16.7-ckt7-1
> Severity: wishlist
> Tags: newcomer
> 
> Whenever I reset my cubox-i4Pro by disconnecting the power plug, the hardware 
> real-time-clock gets
> reset to midnight UTC, Dec 31, 1970.
> Even though the SolidRun literature says that the i4Pro has a battery backed 
> RTC.
> 
> A bit of googling reveals that this is related to the following fact (Quoted 
> from the SolidRun forums)
> 
> >There are two RTC inside CuBox-i 
> >1. One connected to the SNVS rail (internal i.MX6) which is not battery 
> >backed and typically goes to /dev/rtc0

If this RTC is not battery backed, it seems like it ought to be disabled
in this board's device tree.

> >2. Second is NXP PFC8523 based and that one has battery backup (/dev/rtc1)
> >SolidRun Engineering
> >user rabeeh in #cubox on Freenode IRC
> >by rabeeh  Sat Jan 25, 2014 7:04 pm 
> 
> >It's a standard non rechargeable lithium 3.3v coin cell.
> >Available only on the models that has RTC.
> >SolidRun Engineering
> >user rabeeh in #cubox on Freenode IRC
> 
> Curiously, when I look at the Debian Jessie system running on the box, I find 
> that there is only one /dev/rtc* device,
> and that seems to be associated with the SNVS clock.  The PFC8523 clock is 
> not available
> 
> Checking /boot/config-3.16.0-4-armmp, I see what I think is an explanation, 
> because
> 
> # CONFIG_RTC_DRV_PCF8523 is not set
> 
> and
> 
> CONFIG_RTC_DRV_SNVS=y
> 
> Other Linux systems (e.g. Arch) appear (according to the above mentioned 
> googling) to have their kernel compiled so as to
> provide both /dev/rtc0 attached to the SNVS clock, and /dev/rtc1 attached to 
> the PFC8523 clock.
> 
> Would it be possible to configure the default Debian Jessie kernel to do the 
> same?

Yes, we can do that.

> Ideally, the PFC8523 clock should show up as /dev/rtc0, linked to /dev/rtc,
> so that the battery backed clock is used by default to set the system clock 
> at boot-time.
> Failing that, it may be possible to address this by setting HCTOSYS_DEVICE in 
> /etc/default/hwclock appropriately.
> Or maybe one could tweak a rule in /etc/udev ?

I wonder about that.  I think it would make more sense to disable the
useless RTC so there's no need to treat this board specially in
userland.

> Karsten Merker commented via email:
> 
> Yes, that should just need enabling the appropriate module.
> The device-tree instantiates the pcf8523 clock chip:
> 
> &i2c3 {
>pinctrl-names = "default";
>pinctrl-0 = <&pinctrl_cubox_i_i2c3>;
> 
>status = "okay";
> 
>rtc: pcf8523@68 {
>compatible = "nxp,pcf8523";
>reg = <0x68>;
>};
> };
> 
> So if the module is available, it should be loaded automatically.
> 
> Please file a wishlist bug against "Source: linux, Version: 
> 3.16.7-ckt9-1" so that the kernel maintainers can enable the
> module for the next kernel upload.

Actually we consider missing hardware support as severity 'important'.

Ben.

-- 
Ben Hutchings
compatible: Gracefully accepts erroneous data from any source


signature.asc
Description: This is a digitally signed message part

Bug#782364: linux-image-3.16.0-4-armmp: please configure drivers for both Cubox i4pro real time clocks

[Rick Thomas]

Package: src:linux
Version: 3.16.7-ckt7-1
Severity: wishlist
Tags: newcomer

Whenever I reset my cubox-i4Pro by disconnecting the power plug, the hardware 
real-time-clock gets
reset to midnight UTC, Dec 31, 1970.
Even though the SolidRun literature says that the i4Pro has a battery backed 
RTC.

A bit of googling reveals that this is related to the following fact (Quoted 
from the SolidRun forums)

>There are two RTC inside CuBox-i 
>1. One connected to the SNVS rail (internal i.MX6) which is not battery backed 
>and typically goes to /dev/rtc0
>2. Second is NXP PFC8523 based and that one has battery backup (/dev/rtc1)
>SolidRun Engineering
>user rabeeh in #cubox on Freenode IRC
>by rabeeh » Sat Jan 25, 2014 7:04 pm 

>It's a standard non rechargeable lithium 3.3v coin cell.
>Available only on the models that has RTC.
>SolidRun Engineering
>user rabeeh in #cubox on Freenode IRC

Curiously, when I look at the Debian Jessie system running on the box, I find 
that there is only one /dev/rtc* device,
and that seems to be associated with the SNVS clock.  The PFC8523 clock is not 
available…

Checking /boot/config-3.16.0-4-armmp, I see what I think is an explanation, 
because

# CONFIG_RTC_DRV_PCF8523 is not set

and

CONFIG_RTC_DRV_SNVS=y

Other Linux systems (e.g. Arch) appear (according to the above mentioned 
googling) to have their kernel compiled so as to
provide both /dev/rtc0 attached to the SNVS clock, and /dev/rtc1 attached to 
the PFC8523 clock.

Would it be possible to configure the default Debian Jessie kernel to do the 
same?

Ideally, the PFC8523 clock should show up as /dev/rtc0, linked to /dev/rtc,
so that the battery backed clock is used by default to set the system clock at 
boot-time.
Failing that, it may be possible to address this by setting HCTOSYS_DEVICE in 
/etc/default/hwclock appropriately.
Or maybe one could tweak a rule in /etc/udev ?

Karsten Merker commented via email:

Yes, that should just need enabling the appropriate module.
The device-tree instantiates the pcf8523 clock chip:

&i2c3 {
   pinctrl-names = "default";
   pinctrl-0 = <&pinctrl_cubox_i_i2c3>;

   status = "okay";

   rtc: pcf8523@68 {
   compatible = "nxp,pcf8523";
   reg = <0x68>;
   };
};

So if the module is available, it should be loaded automatically.

Please file a wishlist bug against "Source: linux, Version: 
3.16.7-ckt9-1" so that the kernel maintainers can enable the
module for the next kernel upload.


-- Package-specific info:
** Version:
Linux version 3.16.0-4-armmp (debian-ker...@lists.debian.org) (gcc version 
4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt7-1 (2015-03-01)

** Command line:
console=ttymxc0,115200 quiet

** Tainted: C (1024)
 * Module from drivers/staging has been loaded.

** Kernel log:
[3.659929] IR RC5(x) protocol handler initialized
[3.661235] IR SANYO protocol handler initialized
[3.682273] [drm] Initialized drm 1.1.0 20060810
[3.684385] ipu_smfc_init: ioremap 0x0265 -> f05a8000
[3.685339] imx-ipuv3 240.ipu: IPUv3H probed
[3.685411] lirc_dev: IR Remote Control driver registered, major 243 
[3.685844] ipu_smfc_init: ioremap 0x02a5 -> f05c2000
[3.685851] leds_pwm pwmleds: unable to request PWM for imx6:red:front: -517
[3.685879] platform pwmleds: Driver leds_pwm requests probe deferral
[3.694394] imx-ipuv3 280.ipu: IPUv3H probed
[3.722182] i2c i2c-1: IMX I2C adapter registered
[3.726369] rc rc0: lirc_dev: driver ir-lirc-codec (gpio-rc-recv) registered 
at minor = 0
[3.726389] IR LIRC bridge handler initialized
[3.735281] i2c i2c-2: IMX I2C adapter registered
[3.764961] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[3.768187] imxdrm: module is from the staging directory, the quality is 
unknown, you have been warned.
[3.769810] imxdrm: module is from the staging directory, the quality is 
unknown, you have been warned.
[3.775554] imx_hdmi: module is from the staging directory, the quality is 
unknown, you have been warned.
[3.794884] imx_ipuv3_crtc: module is from the staging directory, the 
quality is unknown, you have been warned.
[3.794888] imx_ipuv3_crtc: module is from the staging directory, the 
quality is unknown, you have been warned.
[3.794893] imx_ipuv3_crtc: module is from the staging directory, the 
quality is unknown, you have been warned.
[3.796261] imx_ipuv3_crtc: module is from the staging directory, the 
quality is unknown, you have been warned.
[3.799664] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[3.799677] [drm] No driver support for vblank timestamp query.
[3.799852] imx-drm display-subsystem: bound imx-ipuv3-crtc.0 (ops .LANCHOR0 
[imx_ipuv3_crtc])
[3.799942] imx-drm display-subsystem: bound imx-ipuv3-crtc.1 (ops .LANCHOR0 
[imx_ipuv3_crtc])
[3.800053] imx-drm display-subsystem: bound imx-ipuv3-crtc.4 (ops .LANCHOR0 
[imx_ipuv3_crtc])
[3.800140] imx-drm disp

Bug#782363: multipath-tools-boot: include dm-service-time in initramfs (new default path selector)

[Mauricio Faria de Oliveira]

Package: src:multipath-tools
Version: 0.5.0-6
Severity: serious

Hi Ritesh,

With the default path selector changing to dm-service-time [1], it's not
possible to boot from multipath currently, as it's not in the initramfs:

# multipath -v3
...
	... | mpathg: assembled map [1 queue_if_no_path 1 alua 2 1 service-time 
0 1 1 8:80 1 service-time 0 1 1 8:176 1]

... | mpathg: set ACT_CREATE (map does not exist)
[...] device-mapper: table: 254:0: multipath: unknown path selector type
...

May you please consider the attached patch for an upload for jessie?

# gzip -dc /boot/initrd.img | cpio -t | grep dm-service-time
118384 blocks
lib/modules/.../kernel/drivers/md/dm-service-time.ko

Thanks!

Links:
  [1] 
http://git.opensvc.com/gitweb.cgi?p=multipath-tools/.git;a=commit;h=c015b128103e7a6426d124a38cd679a181573b88


--
Mauricio Faria de Oliveira
IBM Linux Technology Center
diff -Nru multipath-tools-0.5.0/debian/changelog 
multipath-tools-0.5.0/debian/changelog
--- multipath-tools-0.5.0/debian/changelog  2015-03-04 05:53:28.0 
-0300
+++ multipath-tools-0.5.0/debian/changelog  2015-04-10 14:57:34.0 
-0300
@@ -1,3 +1,9 @@
+multipath-tools (0.5.0-6pathselector1) UNRELEASED; urgency=medium
+
+  * initramfs/hooks: include dm-service-time in initramfs (new default path 
selector).
+
+ -- Mauricio Faria de Oliveira   Fri, 10 Apr 2015 
14:51:30 -0300
+
 multipath-tools (0.5.0-6) unstable; urgency=medium
 
   [ Mauricio Faria de Oliveira ]
diff -Nru multipath-tools-0.5.0/debian/initramfs/hooks 
multipath-tools-0.5.0/debian/initramfs/hooks
--- multipath-tools-0.5.0/debian/initramfs/hooks2014-09-05 
06:12:29.0 -0300
+++ multipath-tools-0.5.0/debian/initramfs/hooks2015-04-10 
14:50:53.0 -0300
@@ -48,7 +48,7 @@
 [ -r /etc/multipath.conf ] && cp /etc/multipath.conf $DESTDIR/etc/
 add_bindings
 
-for x in dm-multipath dm-round-robin dm-emc; do
+for x in dm-multipath dm-service-time dm-round-robin dm-emc; do
manual_add_modules ${x}
 done
 

Bug#777753: marked as done (gcc: LTO produces unreproducible debug information)

[Matthias Klose]

Control: reopen -1

Eduard,

 - please don't close issues in packages you are not responsible
   for.
 - your fix is wrong. please don't work around issues which
   can be really fixed.  unstable is still frozen, and you
   should wait for the fix.

Jeremy, maybe it is worth pointing out that package maintainers shouldn't apply
these workarounds.

Matthias


On 04/11/2015 12:21 AM, Debian Bug Tracking System wrote:
> Your message dated Fri, 10 Apr 2015 22:18:36 +
> with message-id 
> and subject line Bug#53: fixed in apt-cacher-ng 0.8.1-1
> has caused the Debian Bug report #53,
> regarding gcc: LTO produces unreproducible debug information
> to be marked as done.


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

Bug#780000: closed by Eduard Bloch (Bug#777753: fixed in apt-cacher-ng 0.8.1-1)

[Thorsten Glaser]

reopen 78
thanks

Debian Bug Tracking System dixit:

>Their explanation is attached below along with your original report.
>If this explanation is unsatisfactory and you have not received a
>better one in a separate message then please contact Eduard Bloch 
> by
>replying to this email.

This is nonsense, a bug in gcc cannot be closed by an apt-cacher-ng
upload as they are unrelated.

bye,
//mirabilos
-- 
 exceptions: a truly awful implementation of quite a nice idea.
 just about the worst way you could do something like that, afaic.
 it's like anti-design.   that too… may I quote you on that?
 sure, tho i doubt anyone will listen ;)


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

Bug#782362: Regression: 3.16.7-ckt9-1: mouning rootpartition cause a deadlock at mount time

[Lebedev Roman]

Package: src:linux
Version: 3.16.7-ckt9-1
Severity: important

Dear Maintainer,

kernel version 3.16.7-ckt9-1 is broken, a deadlock at mount time happens in 
BTRFS.
Previous kernel version (which i'm using right now to report this) - 
3.16.7-ckt7-1 is fine.

This is a known upstream issue:
>From https://btrfs.wiki.kernel.org/index.php/Gotchas
* Stable kernel version 3.19.1+ can cause a deadlock at mount time
* * workaround: boot with older kernel, or run btrfs-zero-log to clear the log 
(beware of the consequences)
* * fix: scheduled for 3.19.4, or apply 9c4f61f01d269815bb7c37.
* * also affected: 3.14.35+, 3.18.9+

I consider this issue to be of "grave" severity, but only for those using BTRFS.

Please fix this.
(either backport that patch or revert to previous kernel (3.16.7-ckt7-1) or 
drop the patches that cause this)

NOTE: i have already downgraded to ckt7 to report this, so all the lines below 
are for ckt7, not ckt9.

-- Package-specific info:
** Version:
Linux version 3.16.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 
4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt7-1 (2015-03-01)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 
root=UUID=f99a9c37-6cc5-4c06-82b8-5f70809512a8 ro cgroup_enable=memory 
swapaccount=1

** Tainted: PO (4097)
 * Proprietary module has been loaded.
 * Out-of-tree module has been loaded.

** Kernel log:
[   15.283385] ohci-pci :00:13.0: OHCI PCI host controller
[   15.284033] ohci-pci :00:13.0: new USB bus registered, assigned bus 
number 11
[   15.285262] ohci-pci :00:13.0: irq 20, io mem 0xfeb08000
[   15.23] AVX version of gcm_enc/dec engaged.
[   15.335594] alg: No test for __gcm-aes-aesni (__driver-gcm-aes-aesni)
[   15.344694] usb usb11: New USB device found, idVendor=1d6b, idProduct=0001
[   15.345349] usb usb11: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
[   15.345965] usb usb11: Product: OHCI PCI host controller
[   15.346608] usb usb11: Manufacturer: Linux 3.16.0-4-amd64 ohci_hcd
[   15.347251] usb usb11: SerialNumber: :00:13.0
[   15.347984] hub 11-0:1.0: USB hub found
[   15.348635] hub 11-0:1.0: 5 ports detected
[   15.349509] ohci-pci :00:14.5: OHCI PCI host controller
[   15.350156] ohci-pci :00:14.5: new USB bus registered, assigned bus 
number 12
[   15.350792] ohci-pci :00:14.5: irq 18, io mem 0xfeb06000
[   15.408595] usb usb12: New USB device found, idVendor=1d6b, idProduct=0001
[   15.409266] usb usb12: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
[   15.409892] usb usb12: Product: OHCI PCI host controller
[   15.410542] usb usb12: Manufacturer: Linux 3.16.0-4-amd64 ohci_hcd
[   15.411169] usb usb12: SerialNumber: :00:14.5
[   15.411937] hub 12-0:1.0: USB hub found
[   15.412573] hub 12-0:1.0: 2 ports detected
[   15.413392] ohci-pci :00:16.0: OHCI PCI host controller
[   15.414033] ohci-pci :00:16.0: new USB bus registered, assigned bus 
number 13
[   15.414674] ohci-pci :00:16.0: irq 22, io mem 0xfeb05000
[   15.472617] usb usb13: New USB device found, idVendor=1d6b, idProduct=0001
[   15.473259] usb usb13: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
[   15.473915] usb usb13: Product: OHCI PCI host controller
[   15.474536] usb usb13: Manufacturer: Linux 3.16.0-4-amd64 ohci_hcd
[   15.475186] usb usb13: SerialNumber: :00:16.0
[   15.475955] hub 13-0:1.0: USB hub found
[   15.476586] hub 13-0:1.0: 4 ports detected
[   15.487941] asus_wmi: ASUS WMI generic driver loaded
[   15.514470] asus_wmi: Initialization: 0x0
[   15.515137] asus_wmi: BIOS WMI version: 0.9
[   15.515809] asus_wmi: SFUN value: 0x0
[   15.516770] input: Eee PC WMI hotkeys as 
/devices/platform/eeepc-wmi/input/input18
[   15.518163] asus_wmi: Disabling ACPI video driver
[   15.684704] alg: No test for crc32 (crc32-pclmul)
[   15.808345] usb 10-1: new full-speed USB device number 2 using ohci-pci
[   15.874342] kvm: Nested Virtualization enabled
[   15.875000] kvm: Nested Paging enabled
[   15.975272] usb 10-1: New USB device found, idVendor=09da, idProduct=9090
[   15.975969] usb 10-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
[   15.976631] usb 10-1: Product: USB Device
[   15.977322] usb 10-1: Manufacturer: A4TECH
[   16.645917] fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, 
Starnberg, GERMANY' taints kernel.
[   16.646596] Disabling lock debugging due to kernel taint
[   16.679864] <6>[fglrx] Maximum main memory to use for locked dma buffers: 
31498 MBytes.
[   16.680895] <6>[fglrx]   vendor: 1002 device: 6798 count: 1
[   16.681853] <6>[fglrx] IOMMU is enabled, CrossFire are not supported on this 
platform
[   16.682567] <6>[fglrx] Disable IOMMU in BIOS options or kernel boot 
parameters to support CF
[   16.683606] <6>[fglrx] ioport: bar 4, base 0xe000, size: 0x100
[   16.684659] FAT-fs (sda2): utf8 is not a recommended IO charset for FAT 
filesystems, filesystem will be case sensitive!
[   16.684671] <6>[fglrx] Kernel PAT support 

Bug#782160: squeeze update of chrony + wheezy update of chrony

[Joachim Wiedorn]

Hello Raphael,

Raphael Hertzog wrote on 2015-04-10 21:33:

> If that workflow is a burden to you, feel free to just prepare an
> updated source package and send it to debian-...@lists.debian.org
> (via a debdiff, or with an URL pointing to the the source package,
> or even with a pointer to your packaging repository), and the members
> of the LTS team will take care of the rest. Indicate clearly whether you
> have tested the updated package or not.

I would be very pleased, if someone of the LTS team could sponsor 
my both packages:

for squeeze-security: chrony 1.24-3+squeeze2
see here:  http://www.joonet.de/sources/chrony/squeeze-security/
Both architectures were produced with pbuilder in a clean environment.
The deb files were not tested!

for wheezy-security:  chrony 1.24-3.1+deb7u3
see here: http://www.joonet.de/sources/chrony/wheezy-security/
Both architectures were produced with pbuilder in a clean environment.
The deb file for amd64 were tested, but not for i386.

For your information:
In the "debian" directory I have added a directory "applied" with
all applied patches to the sources, because both packages still
have source format 1.0. Only the three patches 11, 12, 13 are
new.

Changes since the last uploads:

  * With the following security bugfixes (See: #782160):
- Fix CVE-2015-1853: Protect authenticated symmetric NTP
 associations against DoS attacks.
- Fix CVE-2015-1821: Fix access configuration with subnet
 size indivisible by 4.
- Fix CVE-2015-1822: Fix initialization of reply slots for
 authenticated commands.


---
Have a nice day.

Joachim (Germany)


signature.asc
Description: PGP signature

Bug#782299: debian-cd: include rdnssd deb on the first discs

[Michael Gilbert]

On Fri, Apr 10, 2015 at 1:28 PM, Steve McIntyre wrote:
> I guess that makes sense, yes. We already have special handling for
> other tools like wpasupplicant there, in
> tools/generate_di+k_list. While I'm updating, I see that netcfg-udeb
> also depends on ndisc6-udeb and wide-dhcpv6-client-udeb. Should we
> consider pulling in ndisc6 and wide-dhcpv6-client as well?

>From a quick look at the netcfg source package, those are only needed
in the installer environment.  There aren't any apt-install commands
that would cause a problem similar to the rdnssd one.  So I don't
think that's necessary.

Best wishes,
Mike


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

Bug#782058: Pegasos II: installer boots up to 'returning from prom_init'

[Ben Hutchings]

On Fri, 2015-04-10 at 17:39 -0400, Milan Kupcevic wrote:
> On 04/09/2015 08:21 AM, Ben Hutchings wrote:
> [...]
> 
> > 
> > It isn't reverted.  All I've done is to add radeonfb.ko to the drivers
> > that are included *in the installer*.
> > 
> > Neither radeon.ko nor xserver-xorg-video-radeon are included in the
> > installer, so how could they possibly be used?  If you though those
> > should be used in the installer, you should have told people that
> > earlier.
> > 
> > As it is, I think that the installer should be able to work using
> > radeonfb.ko and xserver-xorg-video-fbdev, though I'm not sure whether
> > radeonfb.ko will be loaded automatically.
> > 
> > Ben.
> > 
> 
> The module landed in sid D-I. It gets loaded automatically as it is not
> blacklisted in D-I. I've been able to boot and run the installer on an
> XServe G4 DP, a G4 Mac Mini, and a Pegasos II. All three machines have
> radeon cards.

Using the graphical or text-based installer?

Ben.

-- 
Ben Hutchings
Everything should be made as simple as possible, but not simpler.
   - Albert Einstein


signature.asc
Description: This is a digitally signed message part

Bug#728669: analysis link of goldbug, its developers and etc

[Zenaan Harkness]

https://www.mail-archive.com/cypherpunks@cpunks.org/msg05277.html

"goldbug" and all its developers now have zero credibility with me.


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

Bug#782095: squeeze update of ntp?

[Kurt Roeckx]

On Fri, Apr 10, 2015 at 11:33:22PM +0200, Raphael Hertzog wrote:
> Hi,
> 
> On Fri, 10 Apr 2015, Kurt Roeckx wrote:
> > On Fri, Apr 10, 2015 at 11:05:47PM +0200, Raphael Hertzog wrote:
> > > Would you like to take care of this yourself? We are still understaffed so
> > > any help is always highly appreciated.
> > 
> > You really don't have patience do you?
> 
> I do, but contacting maintainers is just part of the workflow of CVE
> triage we defined for Debian LTS. Sorry if this mail bothered you. Is
> there a way to do it that would have been better received on your side?

The upload to unstable (and wheezy) only happened a few hours ago
because I didn't have time before.


Kurt


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

Bug#782058: Pegasos II: installer boots up to 'returning from prom_init'

[Milan Kupcevic]

On 04/09/2015 08:21 AM, Ben Hutchings wrote:
[...]

> 
> It isn't reverted.  All I've done is to add radeonfb.ko to the drivers
> that are included *in the installer*.
> 
> Neither radeon.ko nor xserver-xorg-video-radeon are included in the
> installer, so how could they possibly be used?  If you though those
> should be used in the installer, you should have told people that
> earlier.
> 
> As it is, I think that the installer should be able to work using
> radeonfb.ko and xserver-xorg-video-fbdev, though I'm not sure whether
> radeonfb.ko will be loaded automatically.
> 
> Ben.
> 

The module landed in sid D-I. It gets loaded automatically as it is not
blacklisted in D-I. I've been able to boot and run the installer on an
XServe G4 DP, a G4 Mac Mini, and a Pegasos II. All three machines have
radeon cards.

Milan



signature.asc
Description: OpenPGP digital signature

Bug#782095: squeeze update of ntp?

[Raphael Hertzog]

Hi,

On Fri, 10 Apr 2015, Kurt Roeckx wrote:
> On Fri, Apr 10, 2015 at 11:05:47PM +0200, Raphael Hertzog wrote:
> > Would you like to take care of this yourself? We are still understaffed so
> > any help is always highly appreciated.
> 
> You really don't have patience do you?

I do, but contacting maintainers is just part of the workflow of CVE
triage we defined for Debian LTS. Sorry if this mail bothered you. Is
there a way to do it that would have been better received on your side?

And thanks again for caring about Squeeze!

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/


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

Bug#780958: squeeze update of dulwich?

[Raphael Hertzog]

Hello Jelmer,

the Debian LTS team would like to fix the security issues which are
currently open in the Squeeze version of dulwich:
https://security-tracker.debian.org/tracker/CVE-2014-9706
https://security-tracker.debian.org/tracker/CVE-2015-0838
(CVE-2014-9390 is also open but it's lower priority and can be ignored)

Would you like to take care of this yourself? We are still understaffed so
any help is always highly appreciated.

If yes, please follow the workflow we have defined here:
http://wiki.debian.org/LTS/Development

If that workflow is a burden to you, feel free to just prepare an
updated source package and send it to debian-...@lists.debian.org
(via a debdiff, or with an URL pointing to the the source package,
or even with a pointer to your packaging repository), and the members
of the LTS team will take care of the rest. Indicate clearly whether you
have tested the updated package or not.

If you don't want to take care of this update, it's not a problem, we
will do our best with your package. Just let us know whether you would
like to review and/or test the updated package before it gets released.

Thank you very much.

Raphaël Hertzog,
  on behalf of the Debian LTS team.

PS: A member of the LTS team might start working on this update at
any point in time. You can verify whether someone is registered
on this update in this file:
https://anonscm.debian.org/viewvc/secure-testing/data/dla-needed.txt?view=markup
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/


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

Bug#781927: RFS: qemuctl - control gui for qemu / 0.3.1-4 [ITA]

[Tobias Frost]

Am Freitag, den 10.04.2015, 23:55 +0300 schrieb Antti Järvinen:
> Tobias Frost writes:
>  > how's about getting you a collab-maint account (as described in some
>  > classified-ad related mail)?
> 
> I understood I need to get myself identified with PGP-key-signature
> first? Or is just e-mail to n...@debian.org with subject 
> "collab-maint request" as described in 
> https://lists.debian.org/debian-devel-announce/2015/02/msg1.html
> enough? 

Seems so
So, what is your desired username? :)

>  > (Usually we avoid uploading without having other changes too)
> 
> No prob but I tried searching for bugs to fix for the package and
> found none - this is really the case? Previous maintainer has taken
> care of all the bugs?
> 
> --
> Antti


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

Bug#769118: Bug#782355: Acknowledgement (gnome-shell: Week numbers in calendar are wrong during northern DST)

[Ben Hutchings]

Please can this also be fixed in a wheezy point release?  I'm attaching
a patch that worked for me.

I think that the potential for incorrect timesheets and missed meetings
is a good reason to fix this in stable.

Ben.

From: =?UTF-8?q?Florian=20M=C3=BCllner?= 
Date: Thu, 13 Nov 2014 15:14:56 +
Subject: [PATCH] calendar: Stop computing week number ourselves
Origin: https://bugzilla.gnome.org/attachment.cgi?id=290644&action=edit
Bug-Debian: https://bugs.debian.org/782355

Correctly computing the ISO week number is tricky and we already
have code in the platform to do it, so just refer its computation
to GDateTime rather than doing it ourselves.

https://bugzilla.gnome.org/show_bug.cgi?id=736722

[benh: Adjust context for 3.4]
---
 js/ui/calendar.js | 19 +--
 1 file changed, 1 insertion(+), 18 deletions(-)

--- a/js/ui/calendar.js
+++ b/js/ui/calendar.js
@@ -78,23 +78,6 @@ function _formatEventTime(event, clockFo
 return ret;
 }
 
-function _getCalendarWeekForDate(date) {
-// Based on the algorithms found here:
-// http://en.wikipedia.org/wiki/Talk:ISO_week_date
-let midnightDate = new Date(date.getFullYear(), date.getMonth(), date.getDate());
-// Need to get Monday to be 1 ... Sunday to be 7
-let dayOfWeek = 1 + ((midnightDate.getDay() + 6) % 7);
-let nearestThursday = new Date(midnightDate.getFullYear(), midnightDate.getMonth(),
-   midnightDate.getDate() + (4 - dayOfWeek));
-
-let jan1st = new Date(nearestThursday.getFullYear(), 0, 1);
-let diffDate = nearestThursday - jan1st;
-let dayNumber = Math.floor(Math.abs(diffDate) / MSECS_IN_DAY);
-let weekNumber = Math.floor(dayNumber / 7) + 1;
-
-return weekNumber;
-}
-
 function _getDigitWidth(actor){
 let context = actor.get_pango_context();
 let themeNode = actor.get_theme_node();
@@ -592,7 +575,7 @@ const Calendar = new Lang.Class({
{ row: row, col: offsetCols + (7 + iter.getDay() - this._weekStart) % 7 });
 
 if (this._useWeekdate && iter.getDay() == 4) {
-let label = new St.Label({ text: _getCalendarWeekForDate(iter).toString(),
+let label = new St.Label({ text: iter.toLocaleFormat('%V'),
style_class: 'calendar-day-base calendar-week-number'});
 this.actor.add(label,
{ row: row, col: 0, y_align: St.Align.MIDDLE });

Bug#782095: squeeze update of ntp?

[Kurt Roeckx]

On Fri, Apr 10, 2015 at 11:05:47PM +0200, Raphael Hertzog wrote:
> Hello dear maintainer(s),
> 
> the Debian LTS team would like to fix the security issues which are
> currently open in the Squeeze version of ntp:
> https://security-tracker.debian.org/tracker/CVE-2015-1798
> https://security-tracker.debian.org/tracker/CVE-2015-1799
> https://security-tracker.debian.org/tracker/TEMP-000-C29A8D
> 
> Would you like to take care of this yourself? We are still understaffed so
> any help is always highly appreciated.

You really don't have patience do you?


Kurt


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

Bug#782095: squeeze update of ntp?

[Raphael Hertzog]

Hello dear maintainer(s),

the Debian LTS team would like to fix the security issues which are
currently open in the Squeeze version of ntp:
https://security-tracker.debian.org/tracker/CVE-2015-1798
https://security-tracker.debian.org/tracker/CVE-2015-1799
https://security-tracker.debian.org/tracker/TEMP-000-C29A8D

Would you like to take care of this yourself? We are still understaffed so
any help is always highly appreciated.

If yes, please follow the workflow we have defined here:
http://wiki.debian.org/LTS/Development

If that workflow is a burden to you, feel free to just prepare an
updated source package and send it to debian-...@lists.debian.org
(via a debdiff, or with an URL pointing to the the source package,
or even with a pointer to your packaging repository), and the members
of the LTS team will take care of the rest. Indicate clearly whether you
have tested the updated package or not.

If you don't want to take care of this update, it's not a problem, we
will do our best with your package. Just let us know whether you would
like to review and/or test the updated package before it gets released.

Thank you very much.

Raphaël Hertzog,
  on behalf of the Debian LTS team.

PS: A member of the LTS team might start working on this update at
any point in time. You can verify whether someone is registered
on this update in this file:
https://anonscm.debian.org/viewvc/secure-testing/data/dla-needed.txt?view=markup
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/


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

Bug#780056: network-manager: fails to restore DNS settings and default route on resume

[Michael Biebl]

Hi,

Am 10.04.2015 um 23:00 schrieb Micha Lenk:
> Am 09.04.2015 um 00:46 schrieb Michael Biebl:
>> Am 08.04.2015 um 20:10 schrieb Micha Lenk:
>>> Hi maintainers of package network-manager,
>>>
>>> I got no human reply for my bug report since a month, so I just
>>> wanted to remind you that I am still waiting for it.
>>
>> Please test with version 1.0 from experimental. If that still
>> exhibits the problem, please file the bug upstream.
> 
> The version from experimental works fine in my setup. So I am marking
> this bug as fixed in network-manager/1.0.0-4.
> 
> Nevertheless, a similar upstream bug already exists:
> https://bugzilla.redhat.com/show_bug.cgi?id=1100034
> 
> But how do we proceed with this bug to decide whether it is release
> critical for Debian Lenny or not? Michael, what do you suggest?

If you can reproduce the issue reliably, you could run  git bisect
between 0.9.10 and 1.0.0 to find the commit which fixed it. Then we
could evaluate, if that fix is (easily) backportable.

Michael


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#770984: [apcupsd] apcaccess may not work on ARM

[Emanuele Rocca]

Hi,

On 25/11 07:15, Adrien Grellier wrote:
> apcaccess is not working on raspberry pi : it always respond as if -h
> option was given.

I can confirm that the issue is reproducible on asachi.debian.org (armhf):

(sid_armhf-dchroot)ema@asachi:~$ /sbin/apcaccess 
Usage: apcaccess [-f ] [-h [:]] [-p 
] [-u] [] [[:]]

 -f  Load default host,port from given conf file (default: 
/etc/apcupsd/apcupsd.conf)
 -h  Connect to host and port (supercedes conf file)
 -p  Return only the value of the named parameter rather than all 
parameters and values
 -u  Strip unit labels

Supported commands: 'status' (default)
Trailing host/port spec overrides -h and conf file.

And that the proposed patch fixes the bug:

(sid_armhf-dchroot)ema@asachi:~$ ./x/sbin/apcaccess 
APC  : 001,017,0437
DATE : 2015-04-10 20:51:16 +  
HOSTNAME : asachi
[...]


--- apcupsd-3.14.12.orig/src/apcaccess.c
+++ apcupsd-3.14.12/src/apcaccess.c
@@ -146,7 +146,7 @@
 #endif
 
// Process standard options
-   char ch;
+   int ch;
while ((ch = getopt(argc, argv, "f:h:p:u")) != -1)
{
   switch (ch)


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

Bug#782160: squeeze update of chrony?

[Joachim Wiedorn]

Hello Raphael,

Raphael Hertzog wrote on 2015-04-10 21:33:

> Would you like to take care of this yourself? We are still understaffed so
> any help is always highly appreciated. If you planned to prepare a fixed
> wheezy version, it should not be too hard to handle squeeze at the same
> time since squeeze has the same upstream version than wheezy.

At first I have looked for patching the Wheezy package. It was doable.
Now I will test it on my (main) PC, which still have Wheezy installed.

Then I think it should be easy for Squeeze, too.

You will hear from me.

---
Have a nice day.

Joachim (Germany)


signature.asc
Description: PGP signature

Bug#709335: [Pkg-libvirt-maintainers] Bug#709335: libvirtd memory leakage

[Salvatore Bonaccorso]

Control: reassign -1 libnetcf1 0.1.9-2
Control: fixed -1 1:0.2.3-4
Control: affects -1 + libvirt

Hi

On Sat, Apr 11, 2015 at 08:21:56AM +1200, Daniel Reurich wrote:
> Hi Salvatore, Hi All,
> 
> On 10/04/15 09:13, Salvatore Bonaccorso wrote:
> >Hi Daniel, hi all,
> >
> >On Thu, Apr 09, 2015 at 07:24:20PM +1200, Daniel Reurich wrote:
> >>Hi Salvatore,
> >>
> >>No. You are right the leak is still there.  The newer version in wheezy did
> >>fix another issue I had though.
> >>
> >>Any chance of applying the patching to the wheezy version?  It's a really
> >>annoying bug.
> >>
> >>My apologies for the misdirection.
> >
> >No problem! I prepared an update for netcf containing that patch, it
> >is on https://people.debian.org/~carnil/tmp/netcf/ . Can you confirm
> >that this is fixing the issue you are seeing?
> >
> This fixes the leak for me.  libvirtd has not used any more memory in 24
> hours which is definitely an improvement.

Okay thanks for confirming! Reassigning now the bug to the netcf
source package. Will ask for the inclusing into the upcoming wheezy
point release as well.
> 
> >If so I would reassing the bug to netcf, adding fixing version and as
> >well contact the stable release manager to propose the attache debdiff
> >for the the upcoming wheezy point update.
> 
> Excellent.  Thanks for your work on this :-)

You are welcome.

Regards,
Salvatore


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

Bug#780056: network-manager: fails to restore DNS settings and default route on resume

[Micha Lenk]

Control: fixed -1 network-manager/1.0.0-4

Hi Michael,

Am 09.04.2015 um 00:46 schrieb Michael Biebl:
> Am 08.04.2015 um 20:10 schrieb Micha Lenk:
>> Hi maintainers of package network-manager,
>> 
>> I got no human reply for my bug report since a month, so I just
>> wanted to remind you that I am still waiting for it.
> 
> Please test with version 1.0 from experimental. If that still
> exhibits the problem, please file the bug upstream.

The version from experimental works fine in my setup. So I am marking
this bug as fixed in network-manager/1.0.0-4.

Nevertheless, a similar upstream bug already exists:
https://bugzilla.redhat.com/show_bug.cgi?id=1100034

But how do we proceed with this bug to decide whether it is release
critical for Debian Lenny or not? Michael, what do you suggest?

Best regards,
Micha


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

Bug#779974: josm: invalid certificate

[Sebastiaan Couwenberg]

Hi Salvo,

Can I conclude from your lack of response that the issue has been resolved?

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1


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

Bug#781927: RFS: qemuctl - control gui for qemu / 0.3.1-4 [ITA]

[Antti Järvinen]

Tobias Frost writes:
 > how's about getting you a collab-maint account (as described in some
 > classified-ad related mail)?

I understood I need to get myself identified with PGP-key-signature
first? Or is just e-mail to n...@debian.org with subject 
"collab-maint request" as described in 
https://lists.debian.org/debian-devel-announce/2015/02/msg1.html
enough? 

 > (Usually we avoid uploading without having other changes too)

No prob but I tried searching for bugs to fix for the package and
found none - this is really the case? Previous maintainer has taken
care of all the bugs?

--
Antti


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

Bug#781806: das-watchdog: diff for NMU version 0.9.0-3.1

[Salvatore Bonaccorso]

Control: tags 781806 + pending

Dear maintainer,

I've prepared an NMU for das-watchdog (versioned as 0.9.0-3.1) and
uploaded it due to the close Jessie release. Attached here is the used
debdiff for the upload.

Regards,
Salvatore
diff -Nru das-watchdog-0.9.0/debian/changelog das-watchdog-0.9.0/debian/changelog
--- das-watchdog-0.9.0/debian/changelog	2013-10-16 18:37:01.0 +0200
+++ das-watchdog-0.9.0/debian/changelog	2015-04-10 22:34:03.0 +0200
@@ -1,3 +1,13 @@
+das-watchdog (0.9.0-3.1) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * Fix buffer overflow in the handling of the XAUTHORITY env variable
+(CVE-2015-2831) (Closes: #781806)
+  * Remove duplicate check for temp[i] == '\0' in das_watchdog.c
+  * Fix infinite loop on platforms where char is unsigned
+
+ -- Salvatore Bonaccorso   Fri, 10 Apr 2015 22:19:18 +0200
+
 das-watchdog (0.9.0-3) unstable; urgency=low
 
   * Team upload.
diff -Nru das-watchdog-0.9.0/debian/patches/0001-Fix-memory-overflow-if-the-name-of-an-environment-is.patch das-watchdog-0.9.0/debian/patches/0001-Fix-memory-overflow-if-the-name-of-an-environment-is.patch
--- das-watchdog-0.9.0/debian/patches/0001-Fix-memory-overflow-if-the-name-of-an-environment-is.patch	1970-01-01 01:00:00.0 +0100
+++ das-watchdog-0.9.0/debian/patches/0001-Fix-memory-overflow-if-the-name-of-an-environment-is.patch	2015-04-10 22:34:03.0 +0200
@@ -0,0 +1,41 @@
+From bd20bb02e75e2c0483832b52f2577253febfb690 Mon Sep 17 00:00:00 2001
+From: Kjetil Matheussen 
+Date: Wed, 1 Apr 2015 16:06:48 +0200
+Subject: [PATCH] Fix memory overflow if the name of an environment is larger
+ than 500 characters. Bug found by Adam Sampson.
+
+---
+ das_watchdog.c | 10 +-
+ 1 file changed, 9 insertions(+), 1 deletion(-)
+
+diff --git a/das_watchdog.c b/das_watchdog.c
+index c98bbea..8473fe8 100644
+--- a/das_watchdog.c
 b/das_watchdog.c
+@@ -306,7 +306,9 @@ static int checksoftirq(int force){
+ 
+ 
+ static char *get_pid_environ_val(pid_t pid,char *val){
+-  char temp[500];
++  int temp_size = 500;
++  char *temp = malloc(temp_size);
++  
+   int i=0;
+   int foundit=0;
+   FILE *fp;
+@@ -319,6 +321,12 @@ static char *get_pid_environ_val(pid_t pid,char *val){
+ 
+   
+   for(;;){
++
++if (i >= temp_size) {
++  temp_size *= 2;
++  temp = realloc(temp, temp_size);
++}
++  
+ temp[i]=fgetc(fp);
+ 
+ if(foundit==1 && (temp[i]==0 || temp[i]=='\0' || temp[i]==EOF)){
+-- 
+2.1.4
+
diff -Nru das-watchdog-0.9.0/debian/patches/0001-Fixed-memory-leak-in-bd20bb02e75e2c0483832b52f257725.patch das-watchdog-0.9.0/debian/patches/0001-Fixed-memory-leak-in-bd20bb02e75e2c0483832b52f257725.patch
--- das-watchdog-0.9.0/debian/patches/0001-Fixed-memory-leak-in-bd20bb02e75e2c0483832b52f257725.patch	1970-01-01 01:00:00.0 +0100
+++ das-watchdog-0.9.0/debian/patches/0001-Fixed-memory-leak-in-bd20bb02e75e2c0483832b52f257725.patch	2015-04-10 22:34:03.0 +0200
@@ -0,0 +1,50 @@
+From 286489dd7dad59f8b5a9b9fdfececb95bcf5c570 Mon Sep 17 00:00:00 2001
+From: Kjetil Matheussen 
+Date: Wed, 1 Apr 2015 16:12:39 +0200
+Subject: [PATCH] Fixed memory leak in bd20bb02e75e2c0483832b52f2577253febfb690
+
+---
+ das_watchdog.c | 13 ++---
+ 1 file changed, 6 insertions(+), 7 deletions(-)
+
+diff --git a/das_watchdog.c b/das_watchdog.c
+index 8381d56..26385b2 100644
+--- a/das_watchdog.c
 b/das_watchdog.c
+@@ -316,9 +316,10 @@ static char *get_pid_environ_val(pid_t pid,char *val){
+   sprintf(temp,"/proc/%d/environ",pid);
+ 
+   fp=fopen(temp,"r");
+-  if(fp==NULL)
++  if(fp==NULL){
++free(temp);
+ return NULL;
+-
++  }
+   
+   for(;;){
+ 
+@@ -330,17 +331,15 @@ static char *get_pid_environ_val(pid_t pid,char *val){
+ temp[i]=fgetc(fp);
+ 
+ if(foundit==1 && (temp[i]==0 || temp[i]=='\0' || temp[i]==EOF)){
+-  char *ret;
+-  temp[i]=0;
+-  ret=malloc(strlen(temp)+10);
+-  sprintf(ret,"%s",temp);
+   fclose(fp);
+-  return ret;
++  temp[i]=0;
++  return temp;
+ }
+ 
+ switch(temp[i]){
+ case EOF:
+   fclose(fp);
++  free(temp);
+   return NULL;
+ case '=':
+   temp[i]=0;
+-- 
+2.1.4
+
diff -Nru das-watchdog-0.9.0/debian/patches/0001-Remove-duplicate-check-for-temp-i-0.patch das-watchdog-0.9.0/debian/patches/0001-Remove-duplicate-check-for-temp-i-0.patch
--- das-watchdog-0.9.0/debian/patches/0001-Remove-duplicate-check-for-temp-i-0.patch	1970-01-01 01:00:00.0 +0100
+++ das-watchdog-0.9.0/debian/patches/0001-Remove-duplicate-check-for-temp-i-0.patch	2015-04-10 22:34:03.0 +0200
@@ -0,0 +1,25 @@
+From b76e17f733bddb5295ef34eed4dd444b31c7b12f Mon Sep 17 00:00:00 2001
+From: Adam Sampson 
+Date: Wed, 1 Apr 2015 20:28:28 +0100
+Subject: [PATCH 1/3] Remove duplicate check for temp[i] == '\0'
+
+---
+ das_watchdog.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/das_watchdog.c b/das_watchdog.c
+index ab97753..176fb1b 100644
+--- a/das_watch

Bug#782361: netgen crashes on launch

[Jeffrey Ratcliffe]

Package: netgen
Version: 4.9.13.dfsg-8+b3
Severity: grave
Justification: renders package unusable

$ netgen 
NETGEN-4.9.13
Developed at RWTH Aachen University, Germany
and Johannes Kepler University Linz, Austria
Including OpenCascade geometry kernel
Parsing ng.tcl
optfile ./ng.opt does not exist - using default values
X Error of failed request:  BadValue (integer parameter out of range for 
operation)
  Major opcode of failed request:  156 (GLX)
  Minor opcode of failed request:  3 (X_GLXCreateContext)
  Value in failed request:  0x0
  Serial number of failed request:  498
  Current serial number in output stream:  499


-- System Information:
Debian Release: 8.0
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages netgen depends on:
ii  libc6 2.19-17
ii  libgcc1   1:4.9.2-10
ii  libgl1-mesa-glx [libgl1]  10.3.2-1
ii  libglu1-mesa [libglu1]9.0.0-2
ii  libjpeg62-turbo   1:1.3.1-12
ii  libnglib-4.9.13   4.9.13.dfsg-8+b3
ii  liboce-foundation80.15-5
ii  liboce-modeling8  0.15-5
ii  liboce-ocaf-lite8 0.15-5
ii  liboce-ocaf8  0.15-5
ii  liboce-visualization8 0.15-5
ii  libstdc++64.9.2-10
ii  libtcl8.5 8.5.17-1
ii  libtk8.5  8.5.17-1
ii  libtogl1  1.7-12
ii  libxmu6   2:1.1.2-1
ii  tix   8.4.3-5
ii  tix-dev   8.4.3-5

netgen recommends no packages.

netgen suggests no packages.

-- no debconf information


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

Bug#782360: qutecom: unable to connect

[eingousef]

Package: qutecom
Version: 2.2.1+dfsg1-5.2
Severity: important

Dear Maintainer,

qutecom fails to connect to my linphone.org account, where other SIP clients
succeed, for unknown reason. It provides a nice message on the console while
floundering, though :

(warn) 22:47:24 [Common] virtual void CurlHttpRequest::run(): Couldn't connect
to server



-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (990, 'testing'), (980, 'stable-updates'), (980, 'stable'), (90, 
'experimental'), (90, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages qutecom depends on:
ii  libasound2  1.0.28-1
ii  libavcodec5610:2.6.1-dmo2
ii  libavutil54 10:2.6.1-dmo2
ii  libboost-program-options1.55.0  1.55.0+dfsg-3
ii  libboost-serialization1.55.01.55.0+dfsg-3
ii  libboost-signals1.55.0  1.55.0+dfsg-3
ii  libboost-system1.55.0   1.55.0+dfsg-3
ii  libboost-thread1.55.0   1.55.0+dfsg-3
ii  libc6   2.19-17
ii  libcurl37.38.0-4
ii  libgcc1 1:4.9.2-10
ii  libglib2.0-02.42.1-1
ii  libpurple0  2.10.11-1
ii  libqt4-dbus 4:4.8.6+git64-g5dc8b2b+dfsg-3
ii  libqt4-network  4:4.8.6+git64-g5dc8b2b+dfsg-3
ii  libqt4-svg  4:4.8.6+git64-g5dc8b2b+dfsg-3
ii  libqt4-xml  4:4.8.6+git64-g5dc8b2b+dfsg-3
ii  libqtcore4  4:4.8.6+git64-g5dc8b2b+dfsg-3
ii  libqtgui4   4:4.8.6+git64-g5dc8b2b+dfsg-3
ii  libqtwebkit42.3.4.dfsg-3
ii  libsamplerate0  0.1.8-8
ii  libsndfile1 1.0.25-9.1
ii  libspeex1   1.2~rc1.2-1
ii  libssl1.0.0 1.0.1k-3
ii  libstdc++6  4.9.2-10
ii  libswscale3 10:2.6.1-dmo2
ii  libtinyxml2.6.2 2.6.2-2
ii  libuuid12.25.2-6
ii  libx11-62:1.6.2-3
ii  libxau6 1:1.0.8-1
ii  libxdmcp6   1:1.1.1-1+b1
ii  qutecom-data2.2.1+dfsg1-5.2

qutecom recommends no packages.

qutecom suggests no packages.

-- no debconf information


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

Bug#782359: twinkle just doesn't launch

[eingousef]

Package: twinkle
Version: 1:1.4.2-4
Severity: important

Dear Maintainer,

Here is what I have when trying twinkle on jessie :

name@desktop:~$ twinkle

Critical: Cannot open file for reading: /home/name/.twinkle/twinkle.cfg



^C
name@desktop:~$ touch /home/name/.twinkle/twinkle.cfg
name@desktop:~$ twinkle
Twinkle 1.4.2, February 25 2009
Copyright (C) 2005-2009  Michel de Boer

Users:
* twinkle
 

Local IP:   255.255.255.255


twinkle: registering phone...

Twinkle>
twinkle, registration failed: 404 Not Found


^D
Info: Deregistering phone...


^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^CProcessus arrêté


and I had to kill -9 the process to get access to the console again.

And now that I've overwritten my clipboard, I don't remember the yahoo groups
address reportbug asked me to CC this bug report to.



-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (990, 'testing'), (980, 'stable-updates'), (980, 'stable'), (90, 
'experimental'), (90, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages twinkle depends on:
ii  libasound21.0.28-1
ii  libboost-regex1.54.0  1.54.0-5+b1
ii  libc6 2.19-17
ii  libccgnu2-1.8-0   1.8.1-6+b2
ii  libccrtp0 2.0.3-4
ii  libgcc1   1:4.9.2-10
ii  libgsm1   1.0.13-4
ii  libmagic1 1:5.22+15-2
ii  libncurses5   5.9+20140913-1+b1
ii  libreadline6  6.3-8+b3
ii  libsndfile1   1.0.25-9.1
ii  libspeex1 1.2~rc1.2-1
ii  libspeexdsp1  1.2~rc1.2-1
ii  libstdc++64.9.2-10
ii  libtinfo5 5.9+20140913-1+b1
ii  libucommon6   6.1.10-1
ii  libxml2   2.9.1+dfsg1-5
ii  libzrtpcpp2   2.3.4-1+b1
ii  zlib1g1:1.2.8.dfsg-2+b1

twinkle recommends no packages.

twinkle suggests no packages.

-- no debconf information


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

Bug#782358: linphone: Uses TLSv1.0

[eingousef]

Package: linphone
Version: 3.6.1-2.4+b1
Severity: normal

Dear Maintainer,

linphone seems to use the outdated TLSv1.0 protocol to secure connexions. It
should use TLSv1.2 if the server supports it.
(tested on sip.linphone.org servers, which seem to support TLSv1.2)

Regards,



-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (990, 'testing'), (980, 'stable-updates'), (980, 'stable'), (90, 
'experimental'), (90, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages linphone depends on:
ii  libasound21.0.28-1
ii  libatk1.0-0   2.14.0-1
ii  libavcodec56  10:2.6.1-dmo2
ii  libavutil54   10:2.6.1-dmo2
ii  libc6 2.19-17
ii  libcairo2 1.14.0-2.1
ii  libexosip2-11 4.1.0-2
ii  libfontconfig12.11.0-6.3
ii  libfreetype6  2.5.2-3
ii  libgdk-pixbuf2.0-02.31.1-2+b1
ii  libgl1-mesa-glx [libgl1]  10.3.2-1
ii  libglew1.10   1.10.0-3
ii  libglib2.0-0  2.42.1-1
ii  libglu1-mesa [libglu1]9.0.0-2
ii  libgtk2.0-0   2.24.25-3
ii  liblinphone5  3.6.1-2.4+b1
ii  libmediastreamer-base33.6.1-2.4+b1
ii  libnotify40.7.6-2
ii  libogg0   1.3.2-1
ii  libopus0  1.1-2
ii  libortp9  3.6.1-2.4+b1
ii  libosip2-11   4.1.0-2
ii  libpango-1.0-01.36.8-3
ii  libpangocairo-1.0-0   1.36.8-3
ii  libpangoft2-1.0-0 1.36.8-3
ii  libpulse0 5.0-13
ii  libsoup2.4-1  2.48.0-1
ii  libspandsp2   0.0.6-2+b2
ii  libspeex1 1.2~rc1.2-1
ii  libspeexdsp1  1.2~rc1.2-1
ii  libsqlite3-0  3.8.7.1-1
ii  libswscale3   10:2.6.1-dmo2
ii  libtheora01.1.1+dfsg.1-6
ii  libudev1  215-14
ii  libupnp6  1:1.6.19+git20141001-1
ii  libv4l-0  1.6.0-2
ii  libvpx1   1.3.0-3
ii  libx11-6  2:1.6.2-3
ii  libxv12:1.0.10-1+b1
ii  linphone-nogtk3.6.1-2.4+b1

linphone recommends no packages.

Versions of packages linphone suggests:
pn  yelp  

-- no debconf information


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

Bug#782357: linphone: Wrong section in apt

[eingousef]

Package: linphone
Version: 3.6.1-2.4+b1
Severity: minor

Dear Maintainer,

linphone is currently in "sound", but it should probably be in "net", where
most SIP clients are.

Regards,



-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (990, 'testing'), (980, 'stable-updates'), (980, 'stable'), (90, 
'experimental'), (90, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages linphone depends on:
ii  libasound21.0.28-1
ii  libatk1.0-0   2.14.0-1
ii  libavcodec56  10:2.6.1-dmo2
ii  libavutil54   10:2.6.1-dmo2
ii  libc6 2.19-17
ii  libcairo2 1.14.0-2.1
ii  libexosip2-11 4.1.0-2
ii  libfontconfig12.11.0-6.3
ii  libfreetype6  2.5.2-3
ii  libgdk-pixbuf2.0-02.31.1-2+b1
ii  libgl1-mesa-glx [libgl1]  10.3.2-1
ii  libglew1.10   1.10.0-3
ii  libglib2.0-0  2.42.1-1
ii  libglu1-mesa [libglu1]9.0.0-2
ii  libgtk2.0-0   2.24.25-3
ii  liblinphone5  3.6.1-2.4+b1
ii  libmediastreamer-base33.6.1-2.4+b1
ii  libnotify40.7.6-2
ii  libogg0   1.3.2-1
ii  libopus0  1.1-2
ii  libortp9  3.6.1-2.4+b1
ii  libosip2-11   4.1.0-2
ii  libpango-1.0-01.36.8-3
ii  libpangocairo-1.0-0   1.36.8-3
ii  libpangoft2-1.0-0 1.36.8-3
ii  libpulse0 5.0-13
ii  libsoup2.4-1  2.48.0-1
ii  libspandsp2   0.0.6-2+b2
ii  libspeex1 1.2~rc1.2-1
ii  libspeexdsp1  1.2~rc1.2-1
ii  libsqlite3-0  3.8.7.1-1
ii  libswscale3   10:2.6.1-dmo2
ii  libtheora01.1.1+dfsg.1-6
ii  libudev1  215-14
ii  libupnp6  1:1.6.19+git20141001-1
ii  libv4l-0  1.6.0-2
ii  libvpx1   1.3.0-3
ii  libx11-6  2:1.6.2-3
ii  libxv12:1.0.10-1+b1
ii  linphone-nogtk3.6.1-2.4+b1

linphone recommends no packages.

Versions of packages linphone suggests:
pn  yelp  

-- no debconf information


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

Bug#709335: [Pkg-libvirt-maintainers] Bug#709335: libvirtd memory leakage

[Daniel Reurich]

Hi Salvatore, Hi All,

On 10/04/15 09:13, Salvatore Bonaccorso wrote:

Hi Daniel, hi all,

On Thu, Apr 09, 2015 at 07:24:20PM +1200, Daniel Reurich wrote:

Hi Salvatore,

No. You are right the leak is still there.  The newer version in wheezy did
fix another issue I had though.

Any chance of applying the patching to the wheezy version?  It's a really
annoying bug.

My apologies for the misdirection.


No problem! I prepared an update for netcf containing that patch, it
is on https://people.debian.org/~carnil/tmp/netcf/ . Can you confirm
that this is fixing the issue you are seeing?

This fixes the leak for me.  libvirtd has not used any more memory in 24 
hours which is definitely an improvement.



If so I would reassing the bug to netcf, adding fixing version and as
well contact the stable release manager to propose the attache debdiff
for the the upcoming wheezy point update.


Excellent.  Thanks for your work on this :-)

Regards,
Daniel


--
Daniel Reurich
Centurion Computer Technology (2005) Ltd


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

Bug#782356: linphone: account wizard refuses legal e-mail adresses

[eingousef]

Package: linphone
Version: 3.6.1-2.4+b1
Severity: normal

Dear Maintainer,

The linphone account wizard doesn't accept e-mail adresses containing a '+' in
the username when registering a new account on linphone.org. If it's a client
bug, it should be fixed. If it's a server-side restriction, it should be
explained in the accound wizard.

Regards,



-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (990, 'testing'), (980, 'stable-updates'), (980, 'stable'), (90, 
'experimental'), (90, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages linphone depends on:
ii  libasound21.0.28-1
ii  libatk1.0-0   2.14.0-1
ii  libavcodec56  10:2.6.1-dmo2
ii  libavutil54   10:2.6.1-dmo2
ii  libc6 2.19-17
ii  libcairo2 1.14.0-2.1
ii  libexosip2-11 4.1.0-2
ii  libfontconfig12.11.0-6.3
ii  libfreetype6  2.5.2-3
ii  libgdk-pixbuf2.0-02.31.1-2+b1
ii  libgl1-mesa-glx [libgl1]  10.3.2-1
ii  libglew1.10   1.10.0-3
ii  libglib2.0-0  2.42.1-1
ii  libglu1-mesa [libglu1]9.0.0-2
ii  libgtk2.0-0   2.24.25-3
ii  liblinphone5  3.6.1-2.4+b1
ii  libmediastreamer-base33.6.1-2.4+b1
ii  libnotify40.7.6-2
ii  libogg0   1.3.2-1
ii  libopus0  1.1-2
ii  libortp9  3.6.1-2.4+b1
ii  libosip2-11   4.1.0-2
ii  libpango-1.0-01.36.8-3
ii  libpangocairo-1.0-0   1.36.8-3
ii  libpangoft2-1.0-0 1.36.8-3
ii  libpulse0 5.0-13
ii  libsoup2.4-1  2.48.0-1
ii  libspandsp2   0.0.6-2+b2
ii  libspeex1 1.2~rc1.2-1
ii  libspeexdsp1  1.2~rc1.2-1
ii  libsqlite3-0  3.8.7.1-1
ii  libswscale3   10:2.6.1-dmo2
ii  libtheora01.1.1+dfsg.1-6
ii  libudev1  215-14
ii  libupnp6  1:1.6.19+git20141001-1
ii  libv4l-0  1.6.0-2
ii  libvpx1   1.3.0-3
ii  libx11-6  2:1.6.2-3
ii  libxv12:1.0.10-1+b1
ii  linphone-nogtk3.6.1-2.4+b1

linphone recommends no packages.

Versions of packages linphone suggests:
pn  yelp  

-- no debconf information


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

Bug#782355: gnome-shell: Week numbers in calendar are wrong during northern DST

[Ben Hutchings]

Package: gnome-shell
Version: 3.4.2-7+deb7u1
Severity: important

The calendar in the shell has an option to show the ISO week number.
The week numbers are currently wrong here in the UK, and I think they
are wrong in all northern hemisphere time zones during Daylight Saving
Time:

https://bugzilla.gnome.org/show_bug.cgi?id=736722

Ben.

-- System Information:
Debian Release: 7.8
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages gnome-shell depends on:
ii  dconf-gsettings-backend [gsettings-backe  0.12.1-3
ii  gconf-service 3.2.5-1+build1
ii  gir1.2-accountsservice-1.00.6.21-8
ii  gir1.2-atk-1.02.4.0-2
ii  gir1.2-caribou-1.00.4.4-1
ii  gir1.2-clutter-1.01.10.8-2
ii  gir1.2-cogl-1.0   1.10.2-7
ii  gir1.2-coglpango-1.0  1.10.2-7
ii  gir1.2-folks-0.6  0.6.9-1+b1
ii  gir1.2-freedesktop1.32.1-1
ii  gir1.2-gconf-2.0  3.2.5-1+build1
ii  gir1.2-gcr-3  3.4.1-3
ii  gir1.2-gdesktopenums-3.0  3.4.2-3
ii  gir1.2-gdkpixbuf-2.0  2.26.1-1
ii  gir1.2-gee-1.00.6.4-2
ii  gir1.2-gkbd-3.0   3.4.0.2-1
ii  gir1.2-glib-2.0   1.32.1-1
ii  gir1.2-gmenu-3.0  3.4.2-5
ii  gir1.2-gnomebluetooth-1.0 3.4.2-1
ii  gir1.2-gtk-3.03.4.2-7
ii  gir1.2-json-1.0   0.14.2-1
ii  gir1.2-mutter-3.0 3.4.1-5
ii  gir1.2-networkmanager-1.0 0.9.4.0-10
ii  gir1.2-pango-1.0  1.30.0-1
ii  gir1.2-polkit-1.0 0.105-3
ii  gir1.2-soup-2.4   2.38.1-3
ii  gir1.2-telepathyglib-0.12 0.18.2-2
ii  gir1.2-telepathylogger-0.20.4.0-1
ii  gir1.2-upowerglib-1.0 0.9.17-1
ii  gjs   1.32.0-5
ii  gnome-bluetooth   3.4.2-1
ii  gnome-icon-theme-symbolic 3.4.0-2
ii  gnome-settings-daemon 3.4.2+git20121218.7c1322-3+deb7u3
ii  gnome-shell-common3.4.2-7+deb7u1
ii  gnome-themes-standard 3.4.2-2.1
ii  gsettings-desktop-schemas 3.4.2-3
ii  libatk1.0-0   2.4.0-2
ii  libc6 2.13-38+deb7u8
ii  libcairo-gobject2 1.12.2-3
ii  libcairo2 1.12.2-3
ii  libcanberra0  0.28-6
ii  libclutter-1.0-0  1.10.8-2
ii  libcogl-pango01.10.2-7
ii  libcogl9  1.10.2-7
ii  libcroco3 0.6.6-2
ii  libdbus-1-3   1.6.8-1+deb7u6
ii  libdbus-glib-1-2  0.100.2-1
ii  libebook-1.2-13   3.4.4-3+deb7u1
ii  libecal-1.2-113.4.4-3+deb7u1
ii  libedataserver-1.2-16 3.4.4-3+deb7u1
ii  libedataserverui-3.0-13.4.4-3+deb7u1
ii  libffi5   3.0.10-3
ii  libfolks250.6.9-1+b1
ii  libgck-1-03.4.1-3
ii  libgconf-2-4  3.2.5-1+build1
ii  libgcr-3-13.4.1-3
ii  libgdk-pixbuf2.0-02.26.1-1
ii  libgee2   0.6.4-2
ii  libgirepository-1.0-1 1.32.1-1
ii  libgjs0b [libgjs0-libmozjs185-1.0]1.32.0-5
ii  libgl1-mesa-glx [libgl1]  8.0.5-4+deb7u2
ii  libglib2.0-0  2.33.12+really2.32.4-5
ii  libgnome-keyring0 3.4.1-1
ii  libgnome-menu-3-0 3.4.2-5
ii  libgstreamer0.10-00.10.36-1.2
ii  libgtk-3-03.4.2-7
ii  libical0  0.48-2
ii  libjson-glib-1.0-00.14.2-1
ii  libmozjs185-1.0   1.8.5-1.0.0+dfsg-4
ii  libmutter03.4.1-5
ii  libnm-glib4   0.9.4.0-10
ii  libnm-util2   0.9.4.0-10
ii  libnspr4  2:4.9.2-1+deb7u2
ii  libp11-kit0   0.12-3
ii  libpango1.0-0 1.30.0-1
ii  libpolkit-agent-1-0 

Bug#772503: vlc: CRC errors in FLAC files, not occurring in other players

[Andoru Ekkusu]

> Then I think it'd be best to contact upstream about it. Could you please
follow
> https://wiki.videolan.org/Report_bugs to report the bug upstream?

I did, and it was already reported, so I'm guessing they're working on it.

Bug#780880: squeeze update of inspircd?

[Raphael Hertzog]

Hello dear maintainer(s),

the Debian LTS team would like to fix the security issues which are
currently open in the Squeeze version of inspircd:
https://security-tracker.debian.org/tracker/source-package/inspircd

Would you like to take care of this yourself? We are still understaffed so
any help is always highly appreciated.

If yes, please follow the workflow we have defined here:
http://wiki.debian.org/LTS/Development

If that workflow is a burden to you, feel free to just prepare an
updated source package and send it to debian-...@lists.debian.org
(via a debdiff, or with an URL pointing to the the source package,
or even with a pointer to your packaging repository), and the members
of the LTS team will take care of the rest. Indicate clearly whether you
have tested the updated package or not.

If you don't want to take care of this update, it's not a problem, we
will do our best with your package. Just let us know whether you would
like to review and/or test the updated package before it gets released.

Thank you very much.

Raphaël Hertzog,
  on behalf of the Debian LTS team.

PS: A member of the LTS team might start working on this update at
any point in time. You can verify whether someone is registered
on this update in this file:
https://anonscm.debian.org/viewvc/secure-testing/data/dla-needed.txt?view=markup
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/


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

Bug#781806: squeeze update of das-watchdog?

[Raphael Hertzog]

Hello dear maintainer(s),

the Debian LTS team would like to fix the security issues which are
currently open in the Squeeze version of das-watchdog:
https://security-tracker.debian.org/tracker/CVE-2015-2831

Would you like to take care of this yourself? We are still understaffed so
any help is always highly appreciated.

If yes, please follow the workflow we have defined here:
http://wiki.debian.org/LTS/Development

If that workflow is a burden to you, feel free to just prepare an
updated source package and send it to debian-...@lists.debian.org
(via a debdiff, or with an URL pointing to the the source package,
or even with a pointer to your packaging repository), and the members
of the LTS team will take care of the rest. Indicate clearly whether you
have tested the updated package or not.

If you don't want to take care of this update, it's not a problem, we
will do our best with your package. Just let us know whether you would
like to review and/or test the updated package before it gets released.

Thank you very much.

Raphaël Hertzog,
  on behalf of the Debian LTS team.

PS: A member of the LTS team might start working on this update at
any point in time. You can verify whether someone is registered
on this update in this file:
https://anonscm.debian.org/viewvc/secure-testing/data/dla-needed.txt?view=markup
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/


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