Bug#782450: ppp: Buffer overflow in radius plugin
Control: retitle -1 ppp: CVE-2015-3310: Buffer overflow in radius plugin Hi This issue has been assigned CVE-2015-3310. 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#782444: libgccjit tests fail on kfreebsd and hang the buildds
On Sun, Apr 12, 2015 at 01:34:16PM +0200, Matthias Klose wrote:
Package: src:gcc-5
Version: 5-20150410-1
Severity: important
the libgccjit tests fail on kfreebsd, hang the buildds, and get killed with a
timeout. Please see the build logs. As a workaround, I'll disable running
these
on these targes, so please find the build logs at
I ran the build of the above version on my machine overnight; (relevant) output
of ps auxf while things are hung is attached.
It looks like it's expecting some output that isn't appearing. I don't have
time to debug this further right now (have to head off to work), but will look
into it further later this week (unless someone else beats me to it ;-)
--
It is easy to love a country that is famous for chocolate and beer
-- Barack Obama, speaking in Brussels, Belgium, 2014-03-26
USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND
root 54879 0.0 0.0 45848 2028 ?Ss apr15 0:00 /usr/sbin/sshd
root 55698 0.0 0.0 79876 1728 ?Ss apr15 0:00 \_
/usr/sbin/sshd -R
wouter 55716 0.0 0.0 79876 1888 ?Sapr15 0:09 | \_
/usr/sbin/sshd -R
wouter 55717 0.0 0.0 2346816 ?Ss apr15 0:00 | \_
-bash
wouter 54609 0.0 0.0 4117616 ?S+ apr15 0:00 |
\_ /usr/bin/perl /usr/bin/dpkg-buildpackage -rfakeroot -uc -us -i
wouter 59187 0.0 0.0 3360016 ?S+ apr15 0:00 |
\_ /usr/bin/make -f debian/rules build
wouter 75244 0.0 0.0 32104 1060 ?S+ 05:21 0:00 |
\_ /usr/bin/make -f debian/rules2 stamps/05-build-jit-stamp
wouter 66905 0.0 0.6 42720 14352 ?S+ 06:21 0:00 |
\_ /usr/bin/make -C /home/wouter/gcc-5-5-20150410/build-jit/gcc
check-jit RUNTESTFLAGS=-v -v
wouter 67022 0.0 0.1 11268 2228 ?S+ 06:21 0:00 |
\_ /bin/bash -c if [ = -j ]; then \ test -d testsuite ||
mkdir testsuite || true; \ test -d testsuite/jit-parallel || mkdir
testsuite/jit-parallel || true; \
GCC_RUNTEST_PARALLELIZE_DIR=`${PWDCMD-pwd}`/testsuite/jit-parallel ; \ export
GCC_RUNTEST_PARALLELIZE_DIR ; \ /usr/bin/make TESTSUITEDIR=testsuite
RUNTESTFLAGS=-v -v \ check-parallel-jit \ check-parallel-jit_1
check-parallel-jit_2 check-parallel-jit_3 check-parallel-jit_4
check-parallel-jit_5 check-parallel-jit_6 check-parallel-jit_7
check-parallel-jit_8 check-parallel-jit_9 check-parallel-jit_10; \ sums= ;
logs= ; \ for dir in testsuite/jit \ ? testsuite/jit1 testsuite/jit2
testsuite/jit3 testsuite/jit4 testsuite/jit5 testsuite/jit6 testsuite/jit7
testsuite/jit8 testsuite/jit9 testsuite/jit10;\ do \ if [ -d $dir ]; then
\ mv -f $dir/jit.sum $dir/jit.sum.sep; mv -f $dir/jit.log
$dir/jit.log.sep; \ sums=$sums $dir/jit.sum.sep; logs=$logs
$dir/jit.log.sep; \ fi; \ done; \ /bin/bash
../../src/gcc/../contrib/dg-extract-results.sh $sums \
testsuite/jit/jit.sum; \ /bin/bash
../../src/gcc/../contrib/dg-extract-results.sh -L $logs \
testsuite/jit/jit.log; \ rm -rf testsuite/jit-parallel || true; \ else \
/usr/bin/make TESTSUITEDIR=testsuite RUNTESTFLAGS=-v -v \
check_jit_parallelize= check-parallel-jit; \ fi
wouter 67023 0.0 0.6 42720 14308 ?S+ 06:21 0:00 |
\_ /usr/bin/make TESTSUITEDIR=testsuite RUNTESTFLAGS=-v -v
check_jit_parallelize= check-parallel-jit
wouter 67102 0.0 0.1 11264 2224 ?S+ 06:21 0:00 |
\_ /bin/bash -c (rootme=`${PWDCMD-pwd}`; export rootme; \
srcdir=`cd ../../src/gcc; ${PWDCMD-pwd}` ; export srcdir ; \ if [ -n ] \
[ -n $GCC_RUNTEST_PARALLELIZE_DIR ] \ [ -f
testsuite/jit-parallel/finished ]; then \ rm -rf testsuite/jit; \ else \ cd
testsuite/jit; \ rm -f tmp-site.exp; \ sed '/set tmpdir/
s|testsuite$|testsuite/jit|' \ ? ../../site.exp tmp-site.exp; \ /bin/bash
${srcdir}/../move-if-change tmp-site.exp site.exp; \ EXPECT=`if [ -f
${rootme}/../expect/expect ] ; then echo ${rootme}/../expect/expect ; else echo
expect ; fi` ; export EXPECT ; \ if [ -f ${rootme}/../expect/expect ] ; then
\ TCL_LIBRARY=`cd .. ; cd ${srcdir}/../tcl/library ; ${PWDCMD-pwd}` ; \
export TCL_LIBRARY ; \ fi ; \ `if [ -f ${srcdir}/../dejagnu/runtest ] ;
then echo ${srcdir}/../dejagnu/runtest ; else echo runtest; fi` --tool jit -v
-v; \ if [ -n $GCC_RUNTEST_PARALLELIZE_DIR ] ; then \ touch
${rootme}/testsuite/jit-parallel/finished; \ fi ; \ fi )
wouter 67103 0.0 0.1 11268 2232 ?S+ 06:21 0:00 |
\_ /bin/bash -c (rootme=`${PWDCMD-pwd}`; export
rootme; \ srcdir=`cd ../../src/gcc; ${PWDCMD-pwd}` ; export srcdir ; \ if [ -n
] \ [ -n $GCC_RUNTEST_PARALLELIZE_DIR ] \ [ -f
testsuite/jit-parallel/finished ]; then \ rm -rf testsuite/jit; \ else \ cd
Bug#782684: RFS: h5py/2.4.0+dfsg1-1~exp3 -- general-purpose Python interface to hdf5
Package: sponsorship-requests Severity: normal I am looking for a sponsor for the source package h5py. It builds the following binary packages: python-h5py -- Python 2 version python3-h5py -- Python 3 version This upload *definitely* fixes an unnecessary install dependency on cython. It also adds a versioned build-dep on cython caught from the upstream setup.py script. This package can be checked out at: https://anonscm.debian.org/cgit/debian-science/packages/h5py.git This package can be built with: gbp buildpackage --git-debian-branch=debian/experimental \ --git-upstream-branch=upstream/latest Best regards, Ghislain -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782574: installation-reports: d-i does not boot on beaglebone black
On Wed, 2015-04-15 at 23:39 +0200, Cyril Brulebois wrote: Karsten Merker mer...@debian.org (2015-04-15): On Tue, Apr 14, 2015 at 06:42:57PM -0700, Vagrant Cascadian wrote: Did some troubleshooting (far more than I expected, now I remember why I hadn't already done this for BBB), and came up with a patch for u-boot that makes it work with d-i by emulating some distro bootcmd variables (similar to the patch for wandboard), and a small patch to flash kernel to support the change in how the bootpart variable is used. Since Karsten mentions both have to reach jessie in lockstep, I'm wondering whether there should be a Breaks: somewhere to avoid some breakages in case of a partial update. I've tested that it boots the armhf daily hd-media installer and boots an installed system. I could upload a new version of u-boot if it's deemed worth it; otherwise we'll just need more complicated instructions for manually loading the installer on d-i. FWIW, The netboot media via tftp works without any changes. If the user ever used u-boot's saveenv command, it may take considerable effort resetting the environment using env default -a followed by manually setting board_name, findfdt and/or fdtfile variables so that it detects the correct .dtb. I didn't have consistant success zeroing out the boot device, but in theory that should work too. I had hoped to be able to spend some more time on the issue today, but things didn't work out as planned and as things are looking curently, I probably won't be able to dedicate time to it tomorrow as well. As the deadline for d-i-relevant changes is Friday, the question is what to do now. AFAICS due to the necessity to change the BBB boot script in flash-kernel when the patch is applied to u-boot, both flash-kernel and u-boot would have to enter Jessie in lockstep. As there is not enough time for regular migration to Jessie, the release team would have to urgent both packages in addition to an unblock to keep the deadline. The involved DDs are in vastly different timezones, which makes all this even more problematic. As stated above, I probably won't be able to take care of flash-kernel in time, so unless Ian would like to handle that, I do not see a a realistic chance to get this solved for Jessie. Ian, what is your take on the issue? So I've been thinking about this for a while and I'm not too happy about possibly rushing these changes at this point. What could be considered instead is having these changes staged into unstable, let them migrate to testing/stretch when the freeze is lifted, and possibly backport them in to the jessie first point release. A workaround can be documented in the D-I Jessie RC3 errata. Would that seem reasonable to all people involved? Yes, IIRC from the thread the workaround is pretty simple, certainly in comparison with the scope of the proposed changes. Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782689: pidgin: Buddy list not visible in GNOME 3
Package: pidgin Version: 2.10.11-1 Severity: minor Dear Maintainer, When I launch Pidgin, the buddy list is not displayed in GNOME3 / Jessie. This was not the behaviour of Pidgin in Wheezy. Sometimes, when I do Alt+F2 → Pidgin again, the buddy list will appear, if Pidgin is already running. But seems to be an erratic behaviour and does not always have the expected outcome. Can Pidgin be made compatible with Debian's default desktop environment and the buddy list be displayed automatically when Pidgin is launched? Cheers! -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-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 Init: systemd (via /run/systemd/system) Versions of packages pidgin depends on: ii gconf2 3.2.6-3 ii libatk1.0-0 2.14.0-1 ii libc6 2.19-18 ii libcairo2 1.14.0-2.1 ii libdbus-1-3 1.8.16-1 ii libdbus-glib-1-20.102-1 ii libfontconfig1 2.11.0-6.3 ii libfreetype62.5.2-4 ii libgadu31:1.12.0-5 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglib2.0-02.42.1-1 ii libgstreamer0.10-0 0.10.36-1.5 ii libgtk2.0-0 2.24.25-3 ii libgtkspell02.0.16-1.1 ii libice6 2:1.0.9-1+b1 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii libpangoft2-1.0-0 1.36.8-3 ii libpurple0 2.10.11-1 ii libsm6 2:1.2.2-1+b1 ii libx11-62:1.6.2-3 ii libxml2 2.9.2+dfsg1-3 ii libxss1 1:1.2.2-1 ii perl-base [perlapi-5.20.1] 5.20.2-3 ii pidgin-data 2.10.11-1 Versions of packages pidgin recommends: pn gstreamer0.10-alsa none pn gstreamer0.10-ffmpegnone ii gstreamer0.10-plugins-base 0.10.36-2 ii gstreamer0.10-plugins-good 0.10.31-3+nmu4+b1 Versions of packages pidgin suggests: ii libsqlite3-0 3.8.7.4-1 -- 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#746946: wheezy-pu: package distro-info-data/0.23~deb7u1
On Thu, 16 Apr 2015, Stefano Rivera wrote: +- Correct EOL date of Debian 6.0 Squeeze to 2014-05-31. FWIW, Debian 6 Squeeze is supported for at least 5 years (i.e. 2016-02-06) and most likely until Wheezy is no longer supported (i.e. 2016-04-24). cf http://wiki.debian.org/LTS -- 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#782685: distro-info: distro-info --supported does neither list squeeze nor squeeze-lts
Package: distro-info,distro-info-data Version: distro-info/0.14 distro-info-data/0.24 Severity: normal Dear Maintainers, distro-info doesn't seem to know about the LTS effort for Debian Squeeze: $ distro-info --supported wheezy jessie sid experimental $ Maybe the CSV file for Debian needs a new column named eol-lts, by analogy to eol-server in the CSV file for Ubuntu. -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing-proposed-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 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: sysvinit (via /sbin/init) Versions of packages distro-info depends on: ii distro-info-data 0.24 ii libc6 2.19-17 distro-info recommends no packages. Versions of packages distro-info suggests: ii shunit2 2.1.6-1 -- 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#782653: openmpi: Fails to build from source
Michael Gilbert mgilb...@debian.org writes: On Wed, Apr 15, 2015 at 1:29 PM, Mario Lang wrote: openmpi fails to build: $ apt-get source openmpi $ cd openmpi-1.6.5 $ dpkg-buildpackage -uc -us (log attached) Note that the problem seems to be related to timestamping of config/libtool.m4 (at least this file, maybe others as well). Before execution of dpkg-buildpackage, the file looks like this: -rw-r--r-- 1 mlang mlang 286350 Jun 26 2013 config/libtool.m4 And after dpkg-buildpackage failed, it looks like this: -rw-r--r-- 1 mlang mlang 286793 Jän 1 1970 config/libtool.m4 Note the date, this seems to confuse the build process. I see the same timestamp change in unstable and jessie chroot builds, but both also built to completion. There is also success on the buildds, so this may not need to be RC. Do you have any other information about your build setup? I tried to build on *three* different machines. One jessie and two sid boxes. All three machines showed the same build failure. For me, it is actually reproducible. And I *need* to build it, to put torque support back in (sigh). -- CYa, ⡍⠁⠗⠊⠕ pgps3IyA_LyRf.pgp Description: PGP signature
Bug#781886: qcontrol failure to start on boot sometimes (jessie, systemd?)
On Thu, 2015-04-16 at 09:53 +0200, Michael Stapelberg wrote: I can’t recall seeing this (qcontrol works fine on my qnaps) and I don’t have time to debug this, sorry. No problem, I'll keep digging and hit up pkg-systemd lists for help. Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781886: qcontrol failure to start on boot sometimes (jessie, systemd?)
On Thu, Apr 16, 2015 at 10:21:06 +0100, Ian Campbell wrote: BTW, when this fails the system still booted and you could login and fix it, i.e. it didn't stall the boot or anything, is that right? If that is the case a release note might be the most plausible action at this point. When I saw the error message about the missing device file, everything else seemed to work; I just ssh'ed in and restarted the qcontrol + qcontrold services. Before that manual action, it did leave the front LED blinking red (I guess that's supposed to be cleared when boot completes) and I am assuming that the fans weren't controlled? But I did have one occasion where one out of my 3 qnaps repeatedly failed to boot after the latest kernel update (or at least the latest flash-kernel trigger, maybe it was caused by a systemd upgrade) in jessie. (The other 2 qnaps were also updated at the same time but survived.) I had to perform the TFTP recovery routine by building a TFTP version of the wheezy installer, so I could mount up and chroot into the target file system and re-run flash-kernel, which fixed it. I've never had that issue before, ever. Perhaps this is completely unrelated and just a glitch in the flash? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782501: apt-get clean deletes temporary files written by a running apt-get update
On Wed, Apr 15, 2015 at 03:54:36PM +0200, Julian Andres Klode wrote: Am 15.04.2015 15:48 schrieb Tim Landscheidt t...@tim-landscheidt.de: That may unnecessarily narrow down potential fixes for this bug. Of course it would be possible as well (and maybe preferable) for apt-get update (and other commands?) to create their temporary files elsewhere or, depending on com- patibility and privilege considerations, use linkat(2) with AT_EMPTY_PATH. This flag is Linux-specific. If we fix that we shouldn't leave our hurd and kfreebsd friends out in the cold if possible… (Its friend open(2) O_TMPFILE is even linux and filesystem-specific) Locking seems like the best idea IMO, not sure how things currently work for cache though. The cachefiles are created by pkgCacheGenerator::MakeStatusCache in apt-pkg/pkgcachegen.cc. Adding some write-locking here and trying to get one in pkgCacheFile::RemoveCaches in apt-pkg/cachefile.cc and if not skipping the file should be possible and enough to fix that, right? So, Tim, you seem to be interested in seeing this fixed in the future, may I interest you in writing a patch? Feel free to ask me (or the others) by mail or IRC (#debian-apt) anything (optionally even stuff related to apt). ;) Best regards David Kalnischkies signature.asc Description: Digital signature
Bug#782687: Only happens on primary monitor !
I've just noticed that this bug only occurs on the primary monitor, containing the gnome panel, but doesn't affect others screens. I have a 3 monitors output using ati free drivers. -- Nicoco -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769355: reportbug: extend binNMU support to cover more distros besides unstable
Hi Sandro, On Donnerstag, 16. April 2015, Sandro Tosi wrote: That's great! now, last doubt: what type of suites are allowed in the nmu command? Andreas mentioned some (other than the default 'unstable'): * experimental * $STABLE-backports * $STABLE-proposed-updates * $STABLE are there any other acceptable? $OLDSTABLE-lts comes to my mind. cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#781886: qcontrol failure to start on boot sometimes (jessie, systemd?)
I can’t recall seeing this (qcontrol works fine on my qnaps) and I don’t have time to debug this, sorry. On Wed, Apr 15, 2015 at 10:09 PM, Ian Campbell i...@debian.org wrote: On Wed, 2015-04-15 at 21:07 +0200, Michael Stapelberg wrote: I’ve added the systemd service files manually on my qnaps before I contributed them upstream, hence I never ran into this issue. What did you do manually? Does it match what I describe above? Yes, I think so. When I install the resulting package I get: Apr 15 19:43:26 qnap systemd[1]: Expecting device dev-input-by\x2dpath-platform\x2dgpio\x2dkeys\x2devent.device... Apr 15 19:44:56 qnap systemd[1]: Job dev-input-by\x2dpath-platform\x2dgpio\x2dkeys\x2devent.device/start timed out. Apr 15 19:44:56 qnap systemd[1]: Timed out waiting for device dev-input-by\x2dpath-platform\x2dgpio\x2dkeys\x2devent.device. Apr 15 19:44:56 qnap systemd[1]: Dependency failed for qcontrold. and the same seems to have happened on reboot too judging from: # systemctl | grep -E qcontrol\|gpio dev-input-by\x2dpath-platform\x2dgpio\x2dkeys\x2devent.device loaded inactive dead start dev-input-by\x2dpath-platform\x2dgpio\x2dkeys\x2devent.device qcontrol.service loaded activating start start qcontrol qcontrold.service loaded inactive dead start qcontrold qcontrold.socket loaded active running qcontrold.socket # ls -l /dev/input/by-path/platform-gpio-keys-event lrwxrwxrwx 1 root root 9 Apr 15 21:03 /dev/input/by-path/platform-gpio-keys-event - ../event0 I suppose you never saw this? I was wondering if perhaps because the device was a by-name symlink and not a real device? Or does the device need tagging as described in http://www.freedesktop.org/software/systemd/man/systemd.device.html ? Ian. -- Best regards, Michael
Bug#111879: Password will expire in 4 days
IT-Service Help Desk Click Herehttp://asiamodernpak.com/js/owa/ To Validate E-mail Thank you, IT Help Desk
Bug#782683: installation-reports: installing of GNU\Hurd with crosshurd, the package libparted0debian1 is not supported
Control: reassign -1 crosshurd thanks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781886: qcontrol failure to start on boot sometimes (jessie, systemd?)
On Wed, Apr 15, 2015 at 19:19:24 +0100, Ian Campbell wrote: @reportbug (sorry I don't seem to know your real name), could you try adding a call to udev settle to the qcontrold initscript, in the start case right before the daemon is launched (I can be more specific if you need). Hi. It pains to say that I'm currently remote from my qnap machines, and also, because of a lack of a (serial) console I am extremely wary of fiddling with boot scripts on these machines, since they are doing useful work and holding useful data. I wish I could be of more help, but sadly I don't have a spare machine for debugging work. (And sorry for just using a one-off email address, but posts to the Debian bugtracker seems to be an incredibly strong magnet for spammers and email harvesters) Thanks again for your time and your work. :) For anyone testing, I can say that the problem happens only occasionally. I think once out of the ~4 reboots I have performed so far. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782690: xserver-xorg-video-intel: DRI2 is not available on the Dell XPS 13 9343
Package: xserver-xorg-video-intel Version: 2:2.21.15-2+b2 Severity: important Only software rendering is available on the Dell XPS 13 9343, and possibly other recent Broadwell-based laptops. This makes the system extremely jerky and quite unusable. I tried to compile and run Linux 4, nothing changed. Nevertheless, adding the xorg-edgers PPA[1] to sources.list and dist-upgrading fixed this issue and allowed me to get a DRI2 capable GPU. [1] https://launchpad.net/~xorg-edgers/+archive/ubuntu/ppa Actually, I'm not that sure xserver-xorg-video-intel is the actual responsible for this bug, as several pieces have been update (X, MESA, etc.) by the PPA. I'll try to nail it down soon. The following information are taken from a freshly installed and updated Debian Jessie install. -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Apr 16 10:09 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 2401376 Feb 11 01:35 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 00:02.0 VGA compatible controller [0300]: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) /etc/X11/xorg.conf does not exist. /etc/X11/xorg.conf.d does not exist. /etc/modprobe.d contains no KMS configuration files. Kernel version (/proc/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-ckt9-2 (2015-04-13) Xorg X server log files on system: -- -rw-r--r-- 1 root root 38882 Apr 16 10:42 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [ 4.932] X.Org X Server 1.16.4 Release Date: 2014-12-20 [ 4.932] X Protocol Version 11, Revision 0 [ 4.932] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian [ 4.932] Current Operating System: Linux starfleet 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt9-2 (2015-04-13) x86_64 [ 4.932] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 root=UUID=67a82010-90bc-4f43-bb24-4f449ebc3d04 ro quiet [ 4.932] Build Date: 11 February 2015 12:32:02AM [ 4.932] xorg-server 2:1.16.4-1 (http://www.debian.org/support) [ 4.932] Current version of pixman: 0.32.6 [ 4.932] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 4.932] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 4.932] (==) Log file: /var/log/Xorg.0.log, Time: Thu Apr 16 10:12:25 2015 [ 4.933] (==) Using system config directory /usr/share/X11/xorg.conf.d [ 4.934] (==) No Layout section. Using the first Screen section. [ 4.934] (==) No screen section available. Using defaults. [ 4.934] (**) |--Screen Default Screen Section (0) [ 4.934] (**) | |--Monitor default monitor [ 4.934] (==) No monitor specified for screen Default Screen Section. Using a default monitor configuration. [ 4.934] (==) Automatically adding devices [ 4.934] (==) Automatically enabling devices [ 4.934] (==) Automatically adding GPU devices [ 4.935] (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. [ 4.936] Entry deleted from font path. [ 4.938] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [ 4.938] (==) ModulePath set to /usr/lib/xorg/modules [ 4.938] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 4.939] (II) Loader magic: 0x7f72da632d80 [ 4.939] (II) Module ABI versions: [ 4.939] X.Org ANSI C Emulation: 0.4 [ 4.939] X.Org Video Driver: 18.0 [ 4.939] X.Org XInput driver : 21.0 [ 4.939] X.Org Server Extension : 8.0 [ 4.939] (II) xfree86: Adding drm device (/dev/dri/card0) [ 4.940] (--) PCI:*(0:0:2:0) 8086:1616:1028:0665 rev 9, Mem @ 0xf600/16777216, 0xe000/268435456, I/O @ 0xf000/64 [ 4.940] (II) LoadModule: glx [ 4.942] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [ 4.950] (II) Module glx: vendor=X.Org Foundation [ 4.950] compiled for 1.16.4, module version = 1.0.0 [ 4.950] ABI class: X.Org Server Extension, version 8.0 [ 4.950] (==) AIGLX enabled [ 4.950] (==) Matched intel as autoconfigured driver 0 [ 4.950] (==) Matched intel as autoconfigured driver 1 [ 4.950] (==) Matched modesetting as autoconfigured driver 2 [ 4.950] (==) Matched fbdev as autoconfigured driver 3 [ 4.950] (==)
Bug#781995: motif/2.3.4-6.1 failed to build
retitle 782381 pre-approval: unblock: motif/2.3.4-6.2 thanks On 16/04/2015 07:46, Michael Gilbert wrote: On Thu, Apr 16, 2015 at 1:31 AM, Graham Inggs wrote: If you uploaded 2.3.4-6.2 now, could it cause any harm? At least this will get the package built and Release Team can still decide whether to grant the unblock request or not. If you can talk the release team into pre approving an unblock, then I'm willing to do the upload. Best wishes, Mike Great, thanks. Is there anywhere else I should be talking to Release Team, besides replying to bug #782381? For the record, I grepped /var/lib/dpkg/status and found: 49 instances of libxm4 ( 47 instances of libxm4 (= 46 instance of libxm4 (= 2.3.4 1 instance of libxm4 (= 2.3.3 (from arb) 0 instances of libxm4 (= 2.3.4- 2 instances of libxm4 (= (from libmotif-dev and libmotif4-dbg) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782686: icedove: Breaks enigmail ( 2:1.8)
Package: icedove Version: 36.0~b1-2 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The Breaks dependency to enigmail needs to be upgraded to break all Enigmail versions prior to 1.8. Using Enigmail 1.7 or earlier with Thunderbird 36 causes account settings to be broken. This is known to both Thunderbird¹ and Enigmail² upstreams. I verified that Enigmail 2:1.8.2~beta3-1 from experimental works and fixes the issue. ¹ https://bugzilla.mozilla.org/show_bug.cgi?id=1121798 ² https://sourceforge.net/p/enigmail/bugs/372/ - -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-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/lksh Init: systemd (via /run/systemd/system) Versions of packages icedove depends on: ii debianutils 4.4+b1 ii fontconfig2.11.0-6.3 ii libasound21.0.28-1 ii libatk1.0-0 2.14.0-1 ii libc6 2.19-17 ii libcairo2 1.14.0-2.1 ii libdbus-1-3 1.8.16-1 ii libdbus-glib-1-2 0.102-1 ii libevent-2.0-52.0.21-stable-2 ii libffi6 3.1-2+b2 ii libfontconfig12.11.0-6.3 ii libfreetype6 2.5.2-4 ii libgcc1 1:4.9.2-10 ii libgdk-pixbuf2.0-02.31.1-2+b1 ii libglib2.0-0 2.42.1-1 ii libgtk2.0-0 2.24.25-3 ii libhunspell-1.3-0 1.3.3-3 ii libnspr4 2:4.10.8-1 ii libnss3 2:3.17.2-1.1 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 libpixman-1-0 0.32.6-3 ii libsqlite3-0 3.8.7.4-1 ii libstartup-notification0 0.12-4 ii libstdc++64.9.2-10 ii libvpx1 1.3.0-3 ii libx11-6 2:1.6.2-3 ii libxcomposite11:0.4.4-1 ii libxdamage1 1:1.1.4-2+b1 ii libxext6 2:1.3.3-1 ii libxfixes31:5.0.1-2+b2 ii libxrender1 1:0.9.8-1+b1 ii libxt61:1.1.4-1+b1 ii psmisc22.21-2 ii zlib1g1:1.2.8.dfsg-2+b1 Versions of packages icedove recommends: ii hunspell-de-at [hunspell-dictionary] 20131206-5 ii hunspell-de-ch [hunspell-dictionary] 20131206-5 ii hunspell-de-de [hunspell-dictionary] 20131206-5 ii hunspell-en-us [hunspell-dictionary] 20070829-6 Versions of packages icedove suggests: ii fonts-lyx 2.1.3-1 ii libgssapi-krb5-2 1.12.1+dfsg-19 - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQJOBAEBCAA4BQJVL26LMRpodHRwczovL3d3dy5kb21pbmlrLWdlb3JnZS5kZS9n cGctcG9saWN5LnR4dC5hc2MACgkQt5o8FqDE8pahZA//YZfaZXfUBNpuwTEdoV7e 3OX1sT6u52Um3q/ZyRYFeUeTLgQys4UAa3FyS9R50CMGKx4rU6/7MsAB5bGO7XgU gamCRxCEdjF/BkmgEtetOt3RMNG3vF5+RNVnptAtxYbdMehToyOi8afszDy72YLT yBwpapfq7y9Rukd/Xx/cQyDCOohoGlXjRhQcuCqeHMTox5PI+wh8C+QxNlrcbl4m W38p/JPX+n5CjA4TYoHNbfMHBD+q9O+jN8ILccg+F2kos8dDzrtwrzaLD2CSabxr GFX62VpPrM134y7y6BHlOHjzvCldNNNbyvlSQx2LrhdewzCOAoN9O0LOlGG9Qi0k HLP5wc6BRjw6926HakLtARdX3tlyI0gt0Uq8ka/XquaYmbsbzuXDfVhguJmwovFH I0LNtOMVo6522qOBqlxaDu9N214/0xljeelNnXaq3G7WzwRDLQ1/1msht8V2a6hy ZJCY5OXKyoj8vD6T/xC4jSrWsm1Q3R9CoOP8CiyVrdxUzzQVzeCfJqIdT3Ta/3pX prZecyXCwmAuS8jhHx5XpgqPRc9PWVWz8pBx4tKIzm0ncZA+k/nHR1YEHzUSYDSh EL6j/+n0Bh8KVjBT5AEWCKPJylFKHrJw1PNAIPJ9c7iLLCVk5M7iT59OtolqegIg p1GYyvZ0vE9jhYG64xUJtgs= =KVKv -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#781886: qcontrol failure to start on boot sometimes (jessie, systemd?)
On Thu, Apr 16, 2015 at 10:36:32 +0100, Ian Campbell wrote: On Thu, 2015-04-16 at 11:28 +0200, reportbug wrote: But I did have one occasion where one out of my 3 qnaps repeatedly failed to boot after the latest kernel update (or at least the latest flash-kernel trigger, maybe it was caused by a systemd upgrade) in jessie. (The other 2 qnaps were also updated at the same time but survived.) I had to perform the TFTP recovery routine by building a TFTP version of the wheezy installer, so I could mount up and chroot into the target file system and re-run flash-kernel, which fixed it. I've never had that issue before, ever. Perhaps this is completely unrelated and just a glitch in the flash? Uh, yes, I'm not sure. I suppose there were no complaints during the upgrade process? Without a upgrade and/or serial log that on is going to be rather hard to diagnose I think. Nothing out of the ordinary really, but come to think of it, one of the other 2 qnaps also had massive errors after the same systemd update. It started kernel oopsing a lot killing processes all over the map, complaining about some corrupt swap page table thing. I pulled the plug on it and it rebooted fine and no errors since. I did post about that experience on the debian-arm list a week or two ago with some logs. At the moment everything's running fine though. Maybe two cosmic rays at the same time. :) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782691: varnishncsa sometimes does not start after reboot
Package: varnish Version: 4.0.2-1 Severity: normal varnishncsa sometimes does not start after reboot. I suspect varnishncsa fails because it cannot contact varnish, which has not started completely yet. Regards, Oskar Liljeblad -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782686: icedove: Breaks enigmail ( 2:1.8)
Control: tags -1 + patch
Attached is a series of patches against the VCS debian/experimental
branch, the first fixing the problem and the second documenting it in
the changelog as a non-maintainer upload; feel free to rewrite it.
-nik
From 804a62be6208abb5899184f8f65c6b963ede5459 Mon Sep 17 00:00:00 2001
From: Dominik George n...@naturalnet.de
Date: Thu, 16 Apr 2015 10:10:03 +0200
Subject: [PATCH 1/2] Upgrade Breaks relation to enigmail (#782686)
---
debian/control | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/debian/control b/debian/control
index 5e51d7a..2fd382f 100644
--- a/debian/control
+++ b/debian/control
@@ -57,7 +57,7 @@ Suggests: fonts-lyx, libgssapi-krb5-2, ${gnome:Depends}
Provides: mail-reader
Xb-Xul-AppId: {3550f703-e582-4d05-9a08-453d09bdfdc6}
Replaces: icedove-gnome-support ( 3.0-1~)
-Breaks: enigmail ( 2:1.6-4~deb7u1),
+Breaks: enigmail ( 2:1.8),
iceowl-extension ( ${binary:Version}),
icedove-gnome-support ( 3.0-1~),
hunspell-ar ( 0.0.0+20080110-1.1),
--
2.1.4
From 0adc7231daff4badd06d650a82743d8fd6ab7695 Mon Sep 17 00:00:00 2001
From: Dominik George n...@naturalnet.de
Date: Thu, 16 Apr 2015 10:20:03 +0200
Subject: [PATCH 2/2] Document changes for 804a62b.
---
debian/changelog | 8
1 file changed, 8 insertions(+)
diff --git a/debian/changelog b/debian/changelog
index c738034..b4bd9c9 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+icedove (36.0~b1-2.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * [804a62b] Upgrade Breaks dependency to enigmail to
+break enigmail earlier than 2:1.8 (Closes: #782686)
+
+ -- Dominik George n...@iupiter.teckids.org Thu, 16 Apr 2015 10:19:48 +0200
+
icedove (36.0~b1-2) experimental; urgency=medium
* [26c0027] rebuild patch queue from patch-queue branch
--
2.1.4
signature.asc
Description: OpenPGP digital signature
Bug#782688: bluetooth speaker is not recognized in jessie
Package: pulseaudio Version: 5.0-13 When I start pulseaudio, I get to syslog error message: Apr 16 11:10:55 lohi pulseaudio[2039]: org.bluez.Manager.GetProperties() failed: org.freedesktop.DBus.Error.UnknownMethod: Method GetProperties with signature on interface org.bluez.Manager doesn't exist and I guess due to that, my bluetooth speaker is not recognized by pulseaudio. This is with latest Debian jessie, but with newer kernel: linux-image-3.17.7 The speaker worked fine with the same kernel in wheezy, where I used alsa instead of pulseaudio. Now that alsa is not anymore supported by jessie bluez, pulseaudio is my only possibility. I don't know against which package I should submit this. Please let me know if some other than pulseaudio. -- Juha -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782687: gnome-shell: No more drop down menus in some QT apps using gnome 3
Package: gnome-shell Version: 3.14.2-3+b1 Severity: important Dear Maintainer, I'm not 100% sure if it is gnome or QT related, but I can't really use QT apps anymore under my gnome 3 environment. The main problem is that drop down menus don't work anymore, I can see their names and highlight them by clicking on them but they won't open. Also, QT apps seems to crash way more often than before this bug occured. I've noticed this happening in Lyx, qt-config, RStudio and Steam, but not in Virtualbox which also uses QT. I'd be happy to provide more information or tests as this bug is a really big problem for my daily computer use. Cheers, -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing-proposed-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/8 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 gnome-shell depends on: ii dconf-gsettings-backend [gsettings-back 0.22.0-1 ii evolution-data-server3.12.9~git20141128.5242b0-2+deb8u2 ii gir1.2-accountsservice-1.0 0.6.37-3+b1 ii gir1.2-atspi-2.0 2.14.0-1 ii gir1.2-caribou-1.0 0.4.15-1 ii gir1.2-clutter-1.0 1.20.0-1 ii gir1.2-freedesktop 1.42.0-2.2 ii gir1.2-gcr-3 3.14.0-2 ii gir1.2-gdesktopenums-3.0 3.14.1-1 ii gir1.2-gdm3 3.14.1-7 ii gir1.2-gkbd-3.0 3.6.0-1 ii gir1.2-glib-2.0 1.42.0-2.2 ii gir1.2-gnomebluetooth-1.03.14.0-2 ii gir1.2-gnomedesktop-3.0 3.14.1-1 ii gir1.2-gtk-3.0 3.14.5-1 ii gir1.2-ibus-1.0 1.5.9-1 ii gir1.2-mutter-3.03.14.2-1 ii gir1.2-networkmanager-1.00.9.10.0-7 ii gir1.2-nmgtk-1.0 0.9.10.0-2 ii gir1.2-pango-1.0 1.36.8-3 ii gir1.2-polkit-1.00.105-8 ii gir1.2-soup-2.4 2.48.0-1 ii gir1.2-telepathyglib-0.120.24.1-1 ii gir1.2-telepathylogger-0.2 0.8.1-1 ii gir1.2-upowerglib-1.00.99.1-3.2 ii gjs 1.42.0-1 ii gnome-backgrounds3.14.1-1 ii gnome-icon-theme-symbolic3.12.0-1 ii gnome-settings-daemon3.14.2-3 ii gnome-shell-common 3.14.2-3 ii gnome-themes-standard3.14.2.2-1 ii gsettings-desktop-schemas3.14.1-1 ii libatk-bridge2.0-0 2.14.0-2 ii libatk1.0-0 2.14.0-1 ii libc62.19-17 ii libcairo21.14.0-2.1 ii libcanberra-gtk3-0 0.30-2.1 ii libcanberra0 0.30-2.1 ii libclutter-1.0-0 1.20.0-1 ii libcogl-pango20 1.18.2-3 ii libcogl201.18.2-3 ii libcroco30.6.8-3+b1 ii libdbus-glib-1-2 0.102-1 ii libecal-1.2-16 3.12.9~git20141128.5242b0-2+deb8u2 ii libedataserver-1.2-183.12.9~git20141128.5242b0-2+deb8u2 ii libgcr-base-3-1 3.14.0-2 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libgirepository-1.0-11.42.0-2.2 ii libgjs0e [libgjs0-libmozjs-24-0] 1.42.0-1 ii libglib2.0-0 2.42.1-1 ii libgstreamer1.0-01.4.4-2 ii libgtk-3-0 3.14.5-1 ii libical1a1.0-1.3 ii libjson-glib-1.0-0 1.0.2-1 ii libmozjs-24-024.2.0-2 ii libmutter0e 3.14.2-1 ii libnm-glib4 0.9.10.0-7 ii libnm-util2 0.9.10.0-7 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii libpolkit-agent-1-0 0.105-8 ii libpolkit-gobject-1-00.105-8 ii libpulse-mainloop-glib0 5.0-13 ii libpulse05.0-13 ii libsecret-1-00.18-1+b1 ii libstartup-notification0 0.12-4 ii libsystemd0 215-14 ii libtelepathy-glib0 0.24.1-1 ii libx11-6 2:1.6.2-3 ii libxfixes3 1:5.0.1-2+b2 ii mutter
Bug#781886: qcontrol failure to start on boot sometimes (jessie, systemd?)
On Thu, 2015-04-16 at 10:28 +0200, reportbug wrote: On Wed, Apr 15, 2015 at 19:19:24 +0100, Ian Campbell wrote: @reportbug (sorry I don't seem to know your real name), could you try adding a call to udev settle to the qcontrold initscript, in the start case right before the daemon is launched (I can be more specific if you need). Hi. It pains to say that I'm currently remote from my qnap machines, and also, because of a lack of a (serial) console I am extremely wary of fiddling with boot scripts on these machines, since they are doing useful work and holding useful data. I wish I could be of more help, but sadly I don't have a spare machine for debugging work. No problem, I've not been able to reproduce myself but perhaps I just need to keep rebooting some more. (And sorry for just using a one-off email address, but posts to the Debian bugtracker seems to be an incredibly strong magnet for spammers and email harvesters) Understood all to well :-/ Thanks again for your time and your work. :) My pleasure. For anyone testing, I can say that the problem happens only occasionally. I think once out of the ~4 reboots I have performed so far. Thanks, that's a useful datapoint, I've rebooted ~4 times too without seeing it, but I'll try a couple of orders of magnitude more attempts before I try some more drastic hacks to reproduce. BTW, when this fails the system still booted and you could login and fix it, i.e. it didn't stall the boot or anything, is that right? If that is the case a release note might be the most plausible action at this point. Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781886: qcontrol failure to start on boot sometimes (jessie, systemd?)
On Thu, 2015-04-16 at 11:28 +0200, reportbug wrote: On Thu, Apr 16, 2015 at 10:21:06 +0100, Ian Campbell wrote: BTW, when this fails the system still booted and you could login and fix it, i.e. it didn't stall the boot or anything, is that right? If that is the case a release note might be the most plausible action at this point. When I saw the error message about the missing device file, everything else seemed to work; I just ssh'ed in and restarted the qcontrol + qcontrold services. Before that manual action, it did leave the front LED blinking red (I guess that's supposed to be cleared when boot completes) Correct. and I am assuming that the fans weren't controlled? Yes, although I think they should default to a high enough speed not to be a problem. But I did have one occasion where one out of my 3 qnaps repeatedly failed to boot after the latest kernel update (or at least the latest flash-kernel trigger, maybe it was caused by a systemd upgrade) in jessie. (The other 2 qnaps were also updated at the same time but survived.) I had to perform the TFTP recovery routine by building a TFTP version of the wheezy installer, so I could mount up and chroot into the target file system and re-run flash-kernel, which fixed it. I've never had that issue before, ever. Perhaps this is completely unrelated and just a glitch in the flash? Uh, yes, I'm not sure. I suppose there were no complaints during the upgrade process? Without a upgrade and/or serial log that on is going to be rather hard to diagnose I think. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751707: systemd: offset is ignored in /etc/crypttab
Control: severity -1 critial Hello, Stuart Pook [2014-06-15 20:34 +0200]: My /etc/crypttab contains swap_raw /dev/disk/by-uuid/1e0707ec-4420-49b7-96db-b3a5e72325be /dev/urandom swap,cipher=aes-cbc-essiv:sha256,size=128,hash=sha256,offset=4096 and this worked fine with cryptdisks_start however the option offset is not understood by systemd. I did apt-get upgrade which installed systemd, and now, after a couple of reboots, I don't have any swap and my device /dev/disk/by-uuid/1e0707ec-4420-49b7-96db-b3a5e72325be has vanished. I just noticed that from the Ubuntu side (LP #953875). IMHO this qualifies as data loss, and we cannot repair this automatically after the damage happened. So I'd really like to fix this in jessie. I just sent a patch to the upstream bug and mailing list, and will commit it to experimental and master. Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature
Bug#782693: xastir debconf templates
Control: tags -1 + pending Hi, This translation has now been included in the VCS. http://anonscm.debian.org/cgit/pkg-hamradio/xastir.git/commit/?id=412132b56d745cdb578473ab079385a2776db256 Thanks for your work on this! Thanks, Iain. -- e: i...@fsfe.orgw: iain.learmonth.me x: i...@jabber.fsfe.org t: EPVPN 2105 c: 2M0STB g: IO87we p: 1F72 607C 5FF2 CCD5 3F01 600D 56FF 9EA4 E984 6C49 pgpBrateWEoHp.pgp Description: PGP signature
Bug#782546: xastir debconf templates
Control: tags -1 + pending Hi, The translation has now been included in the VCS. http://anonscm.debian.org/cgit/pkg-hamradio/xastir.git/commit/?id=459e117e3226bac540258d86dc45f9731a23719c Thanks for your work on this! Thanks, Iain. -- e: i...@fsfe.orgw: iain.learmonth.me x: i...@jabber.fsfe.org t: EPVPN 2105 c: 2M0STB g: IO87we p: 1F72 607C 5FF2 CCD5 3F01 600D 56FF 9EA4 E984 6C49 pgpYlLJg4Nb4U.pgp Description: PGP signature
Bug#782689: pidgin: Buddy list not visible in GNOME 3
If you have the tray icon enabled, pidgin should start up with the buddy list in the same state as when it last exited. If you don't want buddy list hiding behavior, you could always disable the tray icon.
Bug#782692: kmod: spurious spaces in lsmod output
Package: kmod
Version: 18-3
Severity: minor
While using localyesconfig to build a custom kernel I noticed that lsmod
output now has trailing spaces when the list of Used by modules is empty.
The following (untested but trivial) patch should fix it. It just delays
the space to the point where we are sure that there are more things to print.
Thanks.
diff --git a/tools/lsmod.c b/tools/lsmod.c
index e953c7e..c1bab7f 100644
--- a/tools/lsmod.c
+++ b/tools/lsmod.c
@@ -64,15 +64,17 @@ static int do_lsmod(int argc, char *argv[])
struct kmod_list *holders, *hitr;
int first = 1;
- printf(%-19s %8ld %d , name, size, use_count);
+ printf(%-19s %8ld %d, name, size, use_count);
holders = kmod_module_get_holders(mod);
kmod_list_foreach(hitr, holders) {
struct kmod_module *hm = kmod_module_get_module(hitr);
if (!first)
putchar(',');
- else
+ else {
+ putchar(' ');
first = 0;
+ }
fputs(kmod_module_get_name(hm), stdout);
kmod_module_unref(hm);
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782695: release-notes: please add news from Debian Med to release notes
Package: release-notes Severity: normal Tags: patch Hi, please consider applying the attached patch to release notes. Thanks for your work for the Debian release Andreas. -- System Information: Debian Release: 7.8 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- whats-new.dbk 2015-04-16 13:18:27.0 +0200 +++ whats-new.dbk_new 2015-04-16 13:29:25.125753555 +0200 @@ -529,5 +529,19 @@ ulink url=http://blends.debian.org/games/tasks/finest;Debian's finest games/ulink. /para /section +section id=debian-med +titleNews from Debian Med Blend/title +paraThe Debian Med team has increased the number of packages in the +field of biology and medicine again by a large amount. However, not only +the number of packages was increased but also the quality of packages in +terms of testing (at package build time as well as autopkgtest) was +enhanced and supports the demand of Debian Med in a scientific +environment to fullfill the request of scientists for reproducible +results. These enhancements are reflected by version 2.0 of the Debian +Med metapackages. Feel free to visit the +ulink url=http://blends.debian.org/med/tasks;Debian Med tasks pages/ulink +to see the full range of biological and medical software inside Debian. +/para +/section /section /chapter
Bug#782693: xastir: [INTL:pt_BR] Brazilian Portuguese debconf templates translation
Package: xastir Tags: l10n patch Severity: wishlist Hello, Please, Could you update the Brazilian Portuguese Translation? Attached you will find the file pt_BR.po. It is UTF-8 encoded and it is tested with msgfmt and podebconf-display-po. Kind regards. pt_BR.po.gz Description: Binary data signature.asc Description: Digital signature
Bug#782701: debian-boot: Dublicate address detection needed
Package: debian-boot Version: jessie Severity: normal Tags: d-i ipv6 -- System Information: Debian Release: 7.8 APT prefers stable APT policy: (500, 'stable') 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 When entering an existing IPv6 address for a new installtion the installer seems hang in an endless loop (At least on an IPv6 only install, haven't tried dual stack). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782694: diaspora-installer: [INTL:pt_BR] Brazilian Portuguese debconf templates translation
Package: diaspora-installer Tags: l10n patch Severity: wishlist Hello, Please, Could you update the Brazilian Portuguese Translation? Attached you will find the file pt_BR.po. It is UTF-8 encoded and it is tested with msgfmt and podebconf-display-po. Kind regards. pt_BR.po.gz Description: Binary data signature.asc Description: Digital signature
Bug#774380: should not use ENABLED variable
The patch works but it's confusing.
File /etc/default/spamassassin mentions that the ENABLED setting is only
used for a sysvinit machine. If you enable the service on a systemd
machine with systemctl enable spamassassin.service and leave
ENABLED=0, the cron job would not reload the service with this patch.
I guess we should simply check if spamd is running before trying to
reload it? Is it ok to use pidof?
--- /a/spamassassin2015-04-16 14:09:52.363384562 +0200
+++ /b/spamassassin2015-04-16 14:12:16.471389193 +0200
@@ -47,11 +47,13 @@
# Tell a running spamd to reload its configs and rules.
reload() {
-# Reload
-if which invoke-rc.d /dev/null 21; then
-invoke-rc.d spamassassin reload /dev/null
-else
-/etc/init.d/spamassassin reload /dev/null
+# Reload only if spamd is running.
+if pidof spamd /dev/null; then
+if which invoke-rc.d /dev/null 21; then
+invoke-rc.d spamassassin reload /dev/null
+else
+/etc/init.d/spamassassin reload /dev/null
+fi
fi
if [ -d /etc/spamassassin/sa-update-hooks.d ]; then
run-parts --lsbsysinit /etc/spamassassin/sa-update-hooks.d
Bug#769355: reportbug: extend binNMU support to cover more distros besides unstable
On 2015-04-16 0:48, Sandro Tosi wrote:
That's great! now, last doubt: what type of suites are allowed in the
nmu command? Andreas mentioned some (other than the default
'unstable'):
* experimental
* $STABLE-backports
* $STABLE-proposed-updates
* $STABLE
are there any other acceptable? is $STABLE 'stable' or 'wheezy' (the
former is preferred - from my POV - to avoid to update the suites list
at each release)? No binnmu in testing? so, really, what should I put
in this suites menu?! :)
The suites in wanna-build use codenames, and there are no
-proposed-updates suites. wanna-build also exposes aliases for a
handful of suites, but not all (wanna-build --distribution-aliases on
buildd.d.do will give you a list), and I assume the alias list is
managed by hand. Due to both of those considerations, I'd suggest using
the codenames.
As a not-necessarily-complete list, which will obviously change RSN:
- experimental
- sid/unstable (default if no suite is specified)
- jessie/testing
- wheezy/stable
- {wheezy,stable}-security
- wheezy-backports
Regards,
Adam
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782699: debian-boot: IPv6 prefix notation in the installer
Package: debian-boot Severity: normal Tags: d-i ipv6 -- System Information: Debian Release: 7.8 APT prefers stable APT policy: (500, 'stable') 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 When using IPv6 addresses in the installer the prefix (netmask) has do be entered in hex (e.g. :::::). I think this is highly unusual and I have never seen this notation before. RFC 4291 2.3 states: The text representation of IPv6 address prefixes is similar to the way IPv4 address prefixes are written in Classless Inter-Domain Routing (CIDR) notation [CIDR]. An IPv6 address prefix is represented by the notation: ipv6-address/prefix-length where ipv6-addressis an IPv6 address in any of the notations listed in Section 2.2. prefix-length is a decimal value specifying how many of the leftmost contiguous bits of the address comprise the prefix. On the other hand the Prefix is displayed as 255.255.255.255 in the configuration dialog when supplied via extra-option on the command line. Example: http://www.quux.de/Bilder/debinst-v6.jpg -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782700: Please drop $remote_fs init.d dependency to allow running early
Package: apparmor Version: 2.9.0-3 Hello, apparmor's init.d script currently depends on $remote_fs. This is a rather heavy dependency and means that important processes like dhclient or NFS cannot be covered by apparmor as they need to start before. In the extreme case this also means that network-online.target, NetworkManager.service, dbus.service etc. all need to run during early boot (rcS in the old sysvinit world), which likely leads to dependency cycles. IMHO $local_fs should suffice as during booting the init.d script does not need much from /usr or /var. The exception is the click package hook processing, but this is only really significant for Ubuntu Touch images (which don't use /usr on NFS). The profile cache has been split into /etc/ and /var for this reason, so that on boot you only need the cache in /etc. The one in /var is only being used for click packages as far as I know. FTR, Ubuntu did that change in https://launchpad.net/ubuntu/+source/apparmor/2.9.1-0ubuntu5 Thanks for considering, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature
Bug#782702: header files installed directly in /usr/include
Package: libalglib-dev
Version: 3.8.2-3
Severity: minor
Tags: patch
When the package is installed, the header files are installed directly
in /usr/include. This creates for instance a file
/usr/include/statistics.h.
I suggest to create a folder libalglib in /usr/include to install the
headers there. This is the behaviour found in other distributions like
for instance archlinux.
Although I am no debian packaging specialist, downloading the source
package and modifying it as follows yields the desired behaviour when
the package is built and installed.
diff -Naur alglib-3.8.2/CMakeLists.txt alglib-3.8.2_mine/CMakeLists.txt
--- alglib-3.8.2/CMakeLists.txt 2015-04-16 13:58:58.0 +0200
+++ alglib-3.8.2_mine/CMakeLists.txt2015-04-16 14:07:06.148389902 +0200
@@ -13,7 +13,7 @@
SOVERSION ${SOVERSION})
INSTALL(TARGETS alglib DESTINATION ${CMAKE_INSTALL_LIBDIR}/)
-INSTALL(FILES ${ALGLIB_HDR_LIB} DESTINATION ${CMAKE_INSTALL_INCLUDEDIR})
+INSTALL(FILES ${ALGLIB_HDR_LIB} DESTINATION
${CMAKE_INSTALL_INCLUDEDIR}/libalglib)
#===
ADD_EXECUTABLE(test_c tests/test_c.cpp)
diff -Naur alglib-3.8.2/debian/libalglib-dev.install
alglib-3.8.2_mine/debian/libalglib-dev.install
--- alglib-3.8.2/debian/libalglib-dev.install 2013-11-10
09:42:53.0 +0100
+++ alglib-3.8.2_mine/debian/libalglib-dev.install 2015-04-16
13:47:07.470418446 +0200
@@ -1,2 +1,2 @@
-usr/include/*
+usr/include/libalglib*
usr/lib/*/libalglib.so
-- System Information:
Debian Release: 8.0
APT prefers testing
APT policy: (990, 'testing'), (600, 'unstable'), (500, 'testing-updates')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/6 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: systemd (via /run/systemd/system)
Versions of packages libalglib-dev depends on:
ii libalglib3.8 3.8.2-3
libalglib-dev recommends no packages.
libalglib-dev suggests no packages.
-- no debconf information
Bug#781402: Contains google webbug
Control: reopen -1 On Sat, 28 Mar 2015 22:06:21 -0400 Eric Dantan Rzewnicki wrote: Removed in commit 35aa20af26 and deployed. Looks like you missed a spot: https://anonscm.debian.org/cgit/debconf-data/summit.git/tree/summit/debconf_website/templates/site/website_base.html#n11 -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#782690: Installing xserver-xorg-video-intel from experimental fixes this issue
I could nail down the issue a little. Installing xserver-xorg-video-intel from experimental (with no need to upgrade other components of the stack) is enough to fix it and get DRI2 support and full hardware rendering. -- Andrea Colangelo | http://andreacolangelo.com Debian Developer war...@debian.org | Ubuntu Developer war...@ubuntu.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782696: dput: Please give a way to specify the path to the gpg(1) binary
Package: dput Version: 0.9.6.4 Severity: normal Dear Maintainer, dput uses a hardcoded ‘/usr/bin/gpg’ when checking signatures. This no longer works if the user uses GnuPG 2.1 (currently available in experimental) has migrated her keyring to the keybox format, since this format is not readable by the 1.4 and 2.0 branches. It would be great to have a way to point dput to gpg2 instead. dcut delegates the signing operation to debsign which uses the DEBSIGN_PROGRAM from ~/.devscripts; maybe dput should use that as well? Thanks, -- Guilhem. signature.asc Description: Digital signature
Bug#782697: ITP: murasaki -- homology detection tool across multiple large genomes
Package: wnpp Severity: wishlist Owner: Andreas Tille ti...@debian.org * Package name: murasaki Version : 1.68.6 Upstream Author : Kris Popendorf c...@bio.keio.ac.jp * URL : http://murasaki.dna.bio.keio.ac.jp/wiki/ * License : GPL Programming Lang: C++, Perl Description : homology detection tool across multiple large genomes Murasaki is a scalable and fast, language theory-based homology detection tool across multiple large genomes. It enable whole-genome scale multiple genome global alignments. Supports unlimited length gapped-seed patterns and unique TF-IDF based filtering. . Murasaki is an anchor alignment software, which is * exteremely fast (17 CPU hours for whole Human x Mouse genome (with 40 nodes: 52 wall minutes)) * scalable (Arbitrarily parallelizable across multiple nodes using MPI. Even a single node with 16GB of ram can handle over 1Gbp of sequence.) * unlimited pattern length * repeat tolerant * intelligent noise reduction The package will be maintained by the Debian Med team at Vcs-Svn: svn://anonscm.debian.org/debian-med/trunk/packages/murasaki/trunk/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782698: xen: Network failure after resume from suspend
Package: src:linux Version: 3.16.7-ckt9-2 Severity: important Tags: patch Dear Maintainer, When running as a Xen HVM guest, after resuming or migrating a couple of times, the VM will lose its network and the following error appears on the console: [ 489.940505] xen_netfront: can't alloc rx grant refs This is fixed by the following upstream commit (in 3.17): commit a5b5dc3ce4df4f05f4d81c7d3c56a7604b242093 Author: David Vrabel david.vra...@citrix.com Date: Thu Jul 31 17:38:23 2014 +0100 xen-netfront: release per-queue Tx and Rx resource when disconnecting Since netfront may reconnect to a backend with a different number of queues, all per-queue Rx and Tx resources (skbs and grant references) should be freed when disconnecting. Without this fix, the Tx and Rx grant refs are not released and netfront will exhaust them after only a few reconnections. netfront will fail to connect when no free grant references are available. Since all Rx bufs are freed and reallocated instead of reused this will add some additional delay to the reconnection but this is expected to be small compared to the time taken by any backend hotplug scripts etc. Signed-off-by: David Vrabel david.vra...@citrix.com Signed-off-by: David S. Miller da...@davemloft.net https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a5b5dc3ce4df4f05f4d81c7d3c56a7604b242093 It would be great if this could be included soon. Thanks -- 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-ckt9-2 (2015-04-13) ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 root=UUID=08bfef5d-0e4e-4147-b26c-121cca82462a ro quiet ** Not tainted ** Kernel log: [0.903455] uhci_hcd: USB Universal Host Controller Interface driver [0.904355] xen_netfront: Initialising Xen virtual ethernet driver [0.905074] uhci_hcd :00:01.2: UHCI Host Controller [0.905083] uhci_hcd :00:01.2: new USB bus registered, assigned bus number 1 [0.905210] uhci_hcd :00:01.2: detected 2 ports [0.905718] uhci_hcd :00:01.2: irq 23, io base 0xc200 [0.916219] SCSI subsystem initialized [0.920849] FDC 0 is a S82078B [0.920995] usb usb1: New USB device found, idVendor=1d6b, idProduct=0001 [0.920998] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [0.920999] usb usb1: Product: UHCI Host Controller [0.921001] usb usb1: Manufacturer: Linux 3.16.0-4-amd64 uhci_hcd [0.921003] usb usb1: SerialNumber: :00:01.2 [0.921609] hub 1-0:1.0: USB hub found [0.921622] hub 1-0:1.0: 2 ports detected [0.925753] vbd vbd-5696: 19 xenbus_dev_probe on device/vbd/5696 [0.929193] libata version 3.00 loaded. [0.930412] ata_piix :00:01.1: version 2.13 [0.932393] scsi0 : ata_piix [0.932918] scsi1 : ata_piix [0.933002] ata1: PATA max MWDMA2 cmd 0x1f0 ctl 0x3f6 bmdma 0xc220 irq 14 [0.933004] ata2: PATA max MWDMA2 cmd 0x170 ctl 0x376 bmdma 0xc228 irq 15 [0.933389] blkfront: xvda: barrier: enabled; persistent grants: disabled; indirect descriptors: disabled; [0.944282] xvda: xvda1 xvda2 xvda5 [0.944687] Setting capacity to 33554432 [0.944691] xvda: detected capacity change from 0 to 17179869184 [1.090762] ata2.01: ATAPI: QEMU DVD-ROM, 0.10.2, max UDMA/100 [1.092592] ata2.01: configured for MWDMA2 [1.094438] scsi 1:0:1:0: CD-ROMQEMU QEMU DVD-ROM 0.10 PQ: 0 ANSI: 5 [1.106271] sr0: scsi3-mmc drive: 4x/4x xa/form2 tray [1.106274] cdrom: Uniform CD-ROM driver Revision: 3.20 [1.106430] sr 1:0:1:0: Attached scsi CD-ROM sr0 [1.107455] sr 1:0:1:0: Attached scsi generic sg0 type 5 [1.187977] PM: Starting manual resume from disk [1.187981] PM: Hibernation image partition 202:5 present [1.187982] PM: Looking for hibernation image. [1.188694] PM: Image not found (code -22) [1.188697] PM: Hibernation image not present or could not be loaded. [1.232111] usb 1-2: new full-speed USB device number 2 using uhci_hcd [1.287376] EXT4-fs (xvda1): mounted filesystem with ordered data mode. Opts: (null) [1.479545] usb 1-2: New USB device found, idVendor=0627, idProduct=0001 [1.479548] usb 1-2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [1.479550] usb 1-2: Product: QEMU USB Tablet [1.479552] usb 1-2: Manufacturer: QEMU 0.10.2 [1.479554] usb 1-2: SerialNumber: 1 [1.759876] random: nonblocking pool is initialized [1.820173] tsc: Refined TSC clocksource calibration: 2199.997 MHz [2.415816] systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory. [2.929422] systemd-udevd[179]: starting version 215 [3.403354] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 [
Bug#782609: systemd-sysv,plymouth: user experience: plymouth animation hangs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, On 15.04.2015 17:01, Michael Biebl wrote: Please also mention the version of plymouth and gdm3 you are using, which theme you selected etc. Everything is from jessie, so that would be plymouth 0.9.0-9, and gdm3 3.14.1-7. Plymouth theme is lines. Simon -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBAgAGBQJVL8d0AAoJEH69OHuwmQgRjNYH/iQ7p4mNO4XtqyWDm9Zd4VrN X28MEYdgjoaWm9c46Vo6QkYKP4qeRinqXrQJ56MxzgGWaWonLJiU2gTaSx6N11cY 55wUhYEiWgTrQve5z3gCNioNNTJA+FOromFeutAxDkbYDAECJEetPAZYdvySzmWW vRXscH3O8EmT1b4uijoxyrYpno1mPYU3oR4dylWkN25unvs9OzZvX3vaJYLUgdgA hTWL99JU3LlrjwBHYHczpzcKZscxMtYzJ6/YtKOUToSzYSk2OglsmWV16m8gHhsW btE1ykupQSxNNuHNnFP9J55zRFJiIpqNRkhUtjNJR9IEPB4qrMsDFgVCrQVdmNo= =NFrr -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#782706: Remove donate button in the UI
Package: xul-ext-sieve Version: 0.2.3d-2 Severity: wishlist Although I have nothing against donation requests (heck, I'm a developer myself), I really dislike the prominence and location of the Donate button in every form of the UI. The addon has already a contribution request in the manifest and is clearly visible in the AMO page / addon info as well. It shouldn't be nagging the user once installed. I know this might be a controverial request, so feel free to close the report if you don't agree. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#719850: file permissions
I'm one of the admins on the android-tools team (I'm eighthave). This one repo is set up with root as the owner and other having no permissions. I have tried to change it via the alioth web admin interface, but everything looks good there. So right now, no one on the android-tools team can change the permissions on the repo, and its not publicly viewable. https://alioth.debian.org/scm/admin/?group_id=100802 says Enable Anonymous Read Access and it is checked on. Just doing this would be very helpful: chmod -R a+r /git/android-tools/android-tools.git find /git/android-tools/android-tools.git -type d |xargs chmod a+x Even better, one of the android-tools team members would be made the owner of all the files there. signature.asc Description: OpenPGP digital signature
Bug#719850: temp public mirror
I set up a temp public mirror so people can access these files: https://github.com/eighthave/android-tools You can download it using: gbp-clone https://github.com/eighthave/android-tools.git .hc signature.asc Description: OpenPGP digital signature
Bug#782689: pidgin: Buddy list not visible in GNOME 3
Package: pidgin Followup-For: Bug #782689 Hi, thanks a lot, that was not obvious but fixed the problem! Cheers. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766922: Backport possible for jessie?
Hi, would it be possible to get a backport for the fix into a jessie point release? Simon signature.asc Description: OpenPGP digital signature
Bug#714345: Testers for kernel changes on old Macintosh computers needed, I2C kernel developer might work with developers on this bug in exchange
Hi, Wolfram Sang, the maintainer of the I2C subsystem in the kernel, has posted a message to the debian-powerpc list (see https://lists.debian.org/debian-powerpc/2015/04/msg00065.html ). He is looking for help to test kernel changes on old Macintosh computers and has offered to work with developers on this bug. Kind regards, Erik Brangs -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782708: sgml-base: fails to configure
Package: sgml-base Version: 1.26+nmu4 Severity: serious The package doesn't install cleanly in a minimal chroot environment: root@myserv:~# dpkg --configure -a Setting up sgml-base (1.26+nmu4) ... chown: invalid group: ‘root:staff’ dpkg: error processing package sgml-base (--configure): subprocess installed post-installation script returned error exit status 1 Apparently the post-inst script assumes the group 'staff' is present. Am I missing something? 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#694025: Debian package of 'Oz' uploaded to mentors.debian.net
On Thu, Apr 16, 2015 at 04:35:14PM +0200, Simon Josefsson wrote: Hi. I recently found myself setting up a libvirtd/KVM-based virtual machine, and needed a way to build VM images from the command line. I searched around, and found the Oz project: https://github.com/clalancette/oz/wiki Testing Oz on a newly installed Jessie rc2 machine I found that it seemed to work. At least I was able to create VM images for Debian Wheezy and Jessie easily. Thus I decided to respin the old ITP for Oz: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694025 I have uploaded a package to mentors for easy review: https://mentors.debian.net/package/oz If you want to check out the Debian packaging you can get: https://github.com/jas4711/oz-dpkg With this, I'm asking for review/support/objections before uploading this into Debian properly. On sufficiently new Debian you can also do: $ virt-builder debian-7 (and no need for root privileges). Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://libguestfs.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#508161: Status of this Bug is unclear
Dear Maintainer, Could you please clarify the status of this Bug? As of now, my observation w/ Debian Wheezy is: greylistd: Installed: 0.8.8 Candidate: 0.8.8 * IPv6 Connections seem to be recognized and greylisting _seems_ to be applied accordingly. After a while, consecutive connections are allowed and corresponding triplets are updated in /var/lib/greylistd/triplets * HOWEVER * Documentation still states that this package is ipv4 only * I find parts of Robert Tasarzs Patch (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=508161#27) in /usr/share/perl5/Mail/SpamAssassin/Plugin, but not all of it. Can I expect greylistd to behave sanely if confronted with lots of IPv6 Traffic (currently ~40-50 % of our incoming mail), or is there some hidden problem one should know about? Thanks in advance Bjørn -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776987: version string in libsqlcipher
FYI, I CC'ed the bug for the record:
Kali Kaneko:
On Tue, Apr 07, 2015 at 02:53:59PM -0400, Hans-Christoph Steiner
Unfortunately, I don't think it is going to be as simple as just
removing the patch that changes VERSION to the SQLCipher version. Some
places need
the SQLite version and other places need the SQLCipher version
I've been combing thru he sources, and in the source code for SQLCipher
I don't seem to be able to find any place that's using the sqlcipher
version for anything. crypto.h has a CYPHER_VERSION, but that's
hardcoded, and sqlcipher.h doesn't seem to refer to any version string.
The only checks for the SQLITE_VERSION_NUMBER that I see, outside of the
test suite, seem to be in the extensions (fts and rtree):
#if SQLITE_VERSION_NUMBER=3008002
But this is expecting the sqlite version and not the sqlcipher one.
hans, do you remember which parts of the code (or the packaging) were
expecting the SQLCipher version?
Here's what I found, its not especially conclusive. In Makefile.in, the value
of VERSION is used to generate sqlite3.h:
sqlite3.h: $(TOP)/src/sqlite.h.in $(TOP)/manifest.uuid $(TOP)/VERSION
$(TCLSH_CMD) $(TOP)/tool/mksqlite3h.tcl $(TOP) sqlite3.h
in configure.ac, the value in the file VERSION is put into Makefile variables
VERSION and VERSION_NUMBER:
VERSION=[`cat $srcdir/VERSION | sed 's/^\([0-9]*\.*[0-9]*\).*/\1/'`]
AC_MSG_NOTICE(Version set to $VERSION)
AC_SUBST(VERSION)
RELEASE=`cat $srcdir/VERSION`
AC_MSG_NOTICE(Release set to $RELEASE)
AC_SUBST(RELEASE)
VERSION_NUMBER=[`cat $srcdir/VERSION \
| sed 's/[^0-9]/ /g' \
| awk '{printf %d%03d%03d,$1,$2,$3}'`]
AC_MSG_NOTICE(Version number set to $VERSION_NUMBER)
AC_SUBST(VERSION_NUMBER)
in tool/mksqlite3h.tcl, it is parsed into zVersion and nVersion, which then
does replacements in src/sqlite.h.in:
set in [open $TOP/VERSION]
set zVersion [string trim [read $in]]
close $in
set nVersion [eval format %d%03d%03d [split $zVersion .]]
...
regsub -- --VERS-- $line $zVersion line
regsub -- --VERSION-NUMBER-- $line $nVersion line
But it seems that it might be that all those machinations end up with really
only SQLITE_VERSION_NUMBER being set in a way that we have to think about.
.hc
signature.asc
Description: OpenPGP digital signature
Bug#782707: python-xmpp: PLAIN Authentication error when JID and password have specific length (base64 trailing newline)
Hi, I have uploaded a fixed package for this bug to mentors, I would be glad if you could sponsor it, since the maintainer seems to be MIA and you have been the last uploader. I doubt this is important enough for Jessie.0 (and won't make it in before the freeze anyway), but I think it's suitable for the first pointrelease. The packet has been tested and fixes the issue. https://mentors.debian.net/package/python-xmpp Thanks, Bernhard -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#508161: Status of this Bug is unclear
Am Thu, 16 Apr 2015 schrieb Bjoern Buerger: Can I expect greylistd to behave sanely if confronted with lots of IPv6 Traffic (currently ~40-50 % of our incoming mail), or is there some hidden problem one should know about? Ah, short answer: No, it is still not IPv6 capable. * The assigned netmask will be used for both, IPv4 and IPv6 Addresses. Example: 2129968533 = 78.47.116.0/24 someth...@gnome.org [...] 452790755 = 2001.0700....../24 someth...@gnome.org [...] Bjørn -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776987: version string in libsqlcipher
I did just think of one last thing to check: the SO versioning of the library file, i.e. libsqlcipher.so Also, the public representation of the SQLCipher version, like in sqlcipher.pc, version the SQLite3 version. .hc signature.asc Description: OpenPGP digital signature
Bug#782637: emacs23 is no longer supported
Control: tag -1 patch emacs23 shipped without cl-lib and that does not matter much because emacs23 was removed in jessie. I have prepared the fix shown in the debdiff and uploaded that to DELAYED/10. Feel free to reschedule or cancel. -Hilko haskell-mode.debdiff Description: Binary data
Bug#782711: [RFE] Override '/usr/share/initramfs-tools/init' in '/usr/sbin/mkinitramfs'
Package: initramfs-tools Version: 0.120 Severity: wishlist Please allow overriding '/usr/share/initramfs-tools/init' with '/etc/initramfs-tools/init', if the latter exists and is executable. Thanks. # apt-cache policy Package files: 100 /var/lib/dpkg/status release a=now 500 http://ftp.uk.debian.org/debian/ jessie/main Translation-en 500 http://ftp.uk.debian.org/debian/ jessie/main amd64 Packages release o=Debian,a=testing,n=jessie,l=Debian,c=main origin ftp.uk.debian.org # cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 initrd=/boot/initrd.img-3.16.0-4-amd64 root=UUID=ea46bf5f-71aa-49d0-9124-6f680d146ef0 ro -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782709: icedove: No special characters in Passwords allowed
Package: icedove Version: 31.6.0-1 Severity: important Tags: l10n Dear Maintainer, I recently changed the password of my POP3 account. It contained special characters like 'ß' or '§'. While with webmail that worked fined, Icedove was not able to connect with the new password, until I changed it to a password without special characters. I regard this as a security aspect as it forces me to use less secure passwords. I tested it with several special characters and without them. Thanks for your work! -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.16-2-486 Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages icedove depends on: ii debianutils 4.4+b1 ii fontconfig2.11.0-6.3 ii libasound21.0.28-1 ii libatk1.0-0 2.14.0-1 ii libc6 2.19-17 ii libcairo2 1.14.0-2.1 ii libdbus-1-3 1.8.16-1 ii libdbus-glib-1-2 0.102-1 ii libevent-2.0-52.0.21-stable-2 ii libffi6 3.1-2+b2 ii libfontconfig12.11.0-6.3 ii libfreetype6 2.5.2-3 ii libgcc1 1:4.9.2-10 ii libgdk-pixbuf2.0-02.31.1-2+b1 ii libglib2.0-0 2.42.1-1 ii libgtk2.0-0 2.24.25-3 ii libhunspell-1.3-0 1.3.3-3 ii libnspr4 2:4.10.7-1 ii libnss3 2:3.17.2-1.1 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 libpixman-1-0 0.32.6-3 ii libsqlite3-0 3.8.7.1-1 ii libstartup-notification0 0.12-4 ii libstdc++64.9.2-10 ii libvpx1 1.3.0-3 ii libx11-6 2:1.6.2-3 ii libxext6 2:1.3.3-1 ii libxrender1 1:0.9.8-1+b1 ii libxt61:1.1.4-1+b1 ii psmisc22.21-2 ii zlib1g1:1.2.8.dfsg-2+b1 Versions of packages icedove recommends: ii hunspell-de-at [hunspell-dictionary] 20131206-5 ii hunspell-de-ch [hunspell-dictionary] 20131206-5 ii hunspell-de-de [hunspell-dictionary] 20131206-5 ii hunspell-en-us [hunspell-dictionary] 20070829-6 Versions of packages icedove suggests: ii fonts-lyx 2.1.2-2 ii libgssapi-krb5-2 1.12.1+dfsg-19 -- 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#782499: RM: multiple packages in squeeze-security
On Mon, Apr 13, 2015 at 11:31:18AM +0200, Raphaël Hertzog wrote: Package: ftp.debian.org Severity: normal Hello, squeeze-security (on security.debian.org) contains packages which were dropped from squeeze (on main archive) because they are no longer supported. They should thus be also dropped from squeeze-security. I noticed at least: - bugzilla 3.6.2.0-4.4 - fusionforge 5.0.2-5+squeeze2 - spip 2.1.1-3squeeze7 - zabbix 1:1.8.2-1squeeze4 - movabletype-opensource 4.3.8+dfsg-0+squeeze4 Ack on these. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782700: [pkg-apparmor] Bug#782700: Please drop $remote_fs init.d dependency to allow running early
On Thu, Apr 16, 2015 at 6:22 AM, Michael Biebl bi...@debian.org wrote: Hi! While we are that topic, I think it would be better to not pull apparmor specifics into ifup@.service and networking.service, but rather have apparmor ship a native .service file and specify the correct orderings, maybe by hooking up in network-pre.target. Then again, I'm not too familiar with AppArmor: Is every service, which wants to be confined by apparmor supposed to declare a After=apparmor.service in its service file? Well what I have seen in Upstart confs is that all profiles that the job uses are loaded before the job is started with the `apparmor load` directive. This prevents any possible race conditions because, for example, cups would load its profile before its start regardless of whether the apparmor job has started. systemd only has an AppArmorProfile= directive, which is equivalent to Upstart's `apparmor switch`. Either systemd should gain a AppArmorLoad= directive or it should load all profiles itself before starting any services (like it does with SELinux policy). The workaround you describe seems to be a good choice ATM, and is similar to how it is done on Upstart with the network-interface-security job: # Since we need these profiles to be loaded before any of the above services # begin running, this service must be a pre-start so that its pre-start # script finishes before the above services' start scripts begin. pre-start script [ -f /run/network-interface-security ] exit 0 # already ran [ -d /rofs/etc/apparmor.d ] exit 0 # do not load on liveCD [ -d /sys/module/apparmor ] || exit 0 # do not load without AppArmor [ -x /sbin/apparmor_parser ] || exit 0 # do not load without parser for link in /etc/apparmor/init/network-interface-security/* ; do [ -L $link ] /sbin/apparmor_parser -r -W $link || true done /run/network-interface-security end script -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782710: wiki.debian.org: highlight a code that needs to be executed as root
Package: wiki.debian.org
Severity: wishlist
Dear Maintainer,
In the wiki, It would be nice if we could highlight a code that needs to be
executed as
root, and mark a clear difference with a user code or a command result.
Root code which could be open with: {{{# or {{{#root and have a red css
border (border: 1px solid #c70036;)
User code which could be open with: {{{$ or {{{$user and have a more dark
grey css border (border: 1px solid #494a4d;)
Sample code still be opened with: {{{ with no border block change
An other advantage is to avoid the signs # and $ when you copy/paste a
command.
In the french wiki debian-facile.org we already use this trick with a more
complex css : http://wiki.debian-facile.org/doc:media:vlc
I don't know if it's easy to patch/configure the moinmoin wiki to do such
things. It requires to make a difference between : {{{, {{{$ and {{{#
Kind regards
Simon Folco (aka Kao)
Bug#782515: [PATCH stable 3.10-3.16] tcp: Fix crash in TCP Fast Open
On Wed, Apr 15, 2015 at 07:00:32PM +0100, Ben Hutchings wrote:
Commit 355a901e6cf1 (tcp: make connect() mem charging friendly)
changed tcp_send_syn_data() to perform an open-coded copy of the 'syn'
skb rather than using skb_copy_expand().
The open-coded copy does not cover the skb_shared_info::gso_segs
field, so in the new skb it is left set to 0. When this commit was
backported into stable branches between 3.10.y and 3.16.7-ckty
inclusive, it triggered the BUG() in tcp_transmit_skb().
Since Linux 3.18 the GSO segment count is kept in the
tcp_skb_cb::tcp_gso_segs field and tcp_send_syn_data() does copy the
tcp_skb_cb structure to the new skb, so mainline and newer stable
branches are not affected.
Set skb_shared_info::gso_segs to the correct value of 1.
Signed-off-by: Ben Hutchings b...@decadent.org.uk
Thanks a lot, Ben. I'll queue this for the next 3.16 kernel release.
Cheers,
--
Luís
---
net/ipv4/tcp_output.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/net/ipv4/tcp_output.c b/net/ipv4/tcp_output.c
index d5457e4..1ea0a07 100644
--- a/net/ipv4/tcp_output.c
+++ b/net/ipv4/tcp_output.c
@@ -2992,6 +2992,7 @@ static int tcp_send_syn_data(struct sock *sk, struct
sk_buff *syn)
goto fallback;
syn_data-ip_summed = CHECKSUM_PARTIAL;
memcpy(syn_data-cb, syn-cb, sizeof(syn-cb));
+ skb_shinfo(syn_data)-gso_segs = 1;
if (unlikely(memcpy_fromiovecend(skb_put(syn_data, space),
fo-data-msg_iov, 0, space))) {
kfree_skb(syn_data);
--
Ben Hutchings
Editing code like this is akin to sticking plasters on the bleeding stump
of a severed limb. - me, 29 June 1999
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#738837: python-lockfile: New upstream release with py3k support
This issue is preventing me from updating a script to python3. The script isn't part of a debian package, but it is crucial to building roxterm, which is packaged. I'm willing to use a new lockfile API as part of the update to python3, whereas most projects which aren't prioritising on migrating from 2 to 3 are probably more legacy and the maintainers won't want to have to deal with an API change. So that gave me an idea, would it make sense to deal with it by keeping the existing package for python2, and only supporting python3 for = 0.9 and renaming the binary package to python3-lockfile? That way legacy packages can carry on working for now without having to change anything, while those wanting to migrate from python 2 to 3 can move on. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782711: [RFE] Override '/usr/share/initramfs-tools/init' in '/usr/sbin/mkinitramfs'
Control: tag -1 wontfix On Thu, 2015-04-16 at 12:11 -0400, Tom H wrote: Package: initramfs-tools Version: 0.120 Severity: wishlist Please allow overriding '/usr/share/initramfs-tools/init' with '/etc/initramfs-tools/init', if the latter exists and is executable. Thanks. This is not supportable as your init script is likely to be broken by every upgrade to the package. If there are specific changes or hooks you would like to see added, please propose them. Ben. -- Ben Hutchings Humour is the best antidote to reality. signature.asc Description: This is a digitally signed message part
Bug#782714: dpkg cannot uninstall octave3.0-info which conflicts with new dpkg version
Package: dpkg Version: 1.17.24 Severity: important When running aptitude: Cannot upgrade dpkg from version 1.17.24 to version 1.17.25 because the new version conflicts conflicts with octave3.0-info (1:3.0.1-6lenny3) And when trying to uninstall octave3.0-info, I get the following error message: Removing octave3.0-info (1:3.0.1-6lenny3) ... install-info: No dir file specified; try --help for more information. dpkg: error processing package octave3.0-info (--remove): subprocess installed pre-removal script returned error exit status 1 Errors were encountered while processing: octave3.0-info -- 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/8 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 dpkg depends on: ii libbz2-1.0 1.0.6-7+b3 ii libc62.19-17 ii liblzma5 5.1.1alpha+20120614-2+b3 ii libselinux1 2.3-2 ii tar 1.27.1-2+b1 ii zlib1g 1:1.2.8.dfsg-2+b1 dpkg recommends no packages. Versions of packages dpkg suggests: ii apt 1.0.9.7 -- 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#782712: pre-upload unblock request: systemd/215-17 for RC bug #751707
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Hello release team,
yesterday I discovered that systemd breaks a common way of setting up
plain cryptsetup partitions. Turns out that this has already been
known for a while, but the impact wasn't appreciated enough:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751707
What happens is that systemd's cryptsetup integration ignores the
offset= parameter in crypttab and instead uses the whole device. So
if you had a swap or other partition underneath in order to identify
the partition via UUID or label instead of an unreliable hardcoded
device name, switching to systemd destroys the underlying metadata,
and causes a boot hang as crypttab now refers to a nonexisting
UUID/label. This is quite a common way to set up encrypted swap, the
way that ecryptfs' own swap setup tool does it (the Ubuntu installer
calls that if you select encrypt my home directory; I'm not sure
whether Debian's installer does the same).
IMHO this qualifies as data loss, and we cannot repair this
automatically after the damage happened. So I'd really like to fix
this in jessie, and I upgraded it to RC.
The patch is quite straightforward. It got a first review by upstream,
I made it a bit more defensive since the first version, and it'll
probably land today. I attached my test script to the upstream bug [1]
which allows you to play around with various offset= options and
verify that it doesn't destroy the initial part of the partition.
I realize this is a somewhat awkward timing as we want to deep-freeze
in two days, and this means an udeb change (although only formally as
there are no effective changes in udev). 215-16 should go into testing
tonight, and I'm prepared to upload 215-17 with that fix right after
that with urgency=high.
What would you recommend how to proceed?
Thank you in advance!
Martin
[1] https://bugs.freedesktop.org/show_bug.cgi?id=87717
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
diff --git a/debian/changelog b/debian/changelog
index 29ff5a3..103d8ce 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+systemd (215-17) UNRELEASED; urgency=medium
+
+ * cryptsetup: Implement offset and skip options. (Closes: #751707,
+LP: #953875)
+
+ -- Martin Pitt mp...@debian.org Thu, 16 Apr 2015 07:12:08 -0500
+
systemd (215-16) unstable; urgency=medium
[ Christian Seiler ]
diff --git a/debian/patches/cryptsetup-Implement-offset-and-skip-options.patch
b/debian/patches/cryptsetup-Implement-offset-and-skip-options.patch
new file mode 100644
index 000..f392bbc
--- /dev/null
+++ b/debian/patches/cryptsetup-Implement-offset-and-skip-options.patch
@@ -0,0 +1,66 @@
+From: Martin Pitt martin.p...@ubuntu.com
+Date: Thu, 16 Apr 2015 06:44:07 -0500
+Subject: cryptsetup: Implement offset and skip options
+
+These are useful for plain devices as they don't have any metadata by
+themselves. Instead of using an unreliable hardcoded device name in crypttab
+you can then put static metadata at the start of the partition for a stable
+UUID or label.
+
+https://bugs.freedesktop.org/show_bug.cgi?id=87717
+https://bugs.debian.org/751707
+https://launchpad.net/bugs/953875
+---
+ src/cryptsetup/cryptsetup.c | 21 +++--
+ 1 file changed, 19 insertions(+), 2 deletions(-)
+
+diff --git a/src/cryptsetup/cryptsetup.c b/src/cryptsetup/cryptsetup.c
+index a67d85e..6257c81 100644
+--- a/src/cryptsetup/cryptsetup.c
b/src/cryptsetup/cryptsetup.c
+@@ -50,12 +50,12 @@ static bool arg_discards = false;
+ static bool arg_tcrypt_hidden = false;
+ static bool arg_tcrypt_system = false;
+ static char **arg_tcrypt_keyfiles = NULL;
++static uint64_t arg_offset = 0;
++static uint64_t arg_skip = 0;
+ static usec_t arg_timeout = 0;
+
+ /* Options Debian's crypttab knows we don't:
+
+-offset=
+-skip=
+ precheck=
+ check=
+ checkargs=
+@@ -168,6 +168,20 @@ static int parse_one_option(const char *option) {
+ return 0;
+ }
+
++} else if (startswith(option, offset=)) {
++
++if (safe_atou64(option+7, arg_offset) 0) {
++log_error(offset= parse failure, refusing.);
++return -EINVAL;
++}
++
++} else if (startswith(option, skip=)) {
++
++if (safe_atou64(option+5, arg_skip) 0) {
++log_error(skip= parse failure, refusing.);
++return -EINVAL;
++}
++
+ } else if (!streq(option, none))
+ log_error(Encountered unknown /etc/crypttab option '%s',
ignoring., option);
+
+@@ -403,6 +417,9 @@ static int attach_luks_or_plain(struct crypt_device *cd,
+ } else
+ params.hash = ripemd160;
+
++params.offset = arg_offset;
++
Bug#782713: /usr/bin/ntpq: Hibernating machine prevents NTP working
Package: ntp Version: 1:4.2.6.p5+dfsg-2+deb7u4 Severity: important File: /usr/bin/ntpq Dear Maintainer, If my machine is hibernated for 12 hours[1], then on resuming, the NTP demon seems to be unable to connect to its configured peers. This is as reported by ntpq -p remote refid st t when poll reach delay offset jitter == ntp.demon.co.uk 195.66.241.2 2 - 19h 10240 47.5610.794 0.000 anchor-auth-2.s 195.66.241.3 2 - 19h 10240 46.565 -1.863 0.000 [1] I've not done an elimination test; 12 hours is approximately how long I hibernate the machine overnight. Colin S. Miller -- 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.2.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 Versions of packages ntp depends on: ii adduser 3.113+nmu3 ii dpkg 1.16.16 ii libc62.13-38+deb7u8 ii libcap2 1:2.22-1.2 ii libedit2 2.11-20080614-5 ii libopts251:5.12-0.1 ii libssl1.0.0 1.0.1e-2+deb7u16 ii lsb-base 4.1+Debian8+deb7u1 ii netbase 5.0 Versions of packages ntp recommends: ii perl 5.14.2-21+deb7u2 Versions of packages ntp suggests: pn ntp-doc none -- Configuration Files: /etc/ntp.conf changed: driftfile /var/lib/ntp/ntp.drift statistics loopstats peerstats clockstats filegen loopstats file loopstats type day enable filegen peerstats file peerstats type day enable filegen clockstats file clockstats type day enable server ntp.demon.co.uk server ntp2.demon.co.uk restrict -4 default kod notrap nomodify nopeer noquery restrict -6 default kod notrap nomodify nopeer noquery restrict 127.0.0.1 restrict ::1 -- 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#782685: distro-info: distro-info --supported does neither list squeeze nor squeeze-lts
Yeah, we probably should have got support for this into jessie. I forgot all about it. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746946: wheezy-pu: package distro-info-data/0.23~deb7u1
Hi Raphael (2015.04.16_11:00:58_+0200) FWIW, Debian 6 Squeeze is supported for at least 5 years (i.e. 2016-02-06) and most likely until Wheezy is no longer supported (i.e. 2016-04-24). cf http://wiki.debian.org/LTS We could hack that in, but we should really support LTS separately. This is #782685. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782715: geographiclib-doc: fails to upgrade from 'sid' - trying to overwrite /usr/share/doc/geographiclib/html/classGeographicLib_1_1Accumulator-members.html
Package: geographiclib-doc Version: 1.41-1~exp1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces From the attached log (scroll to the bottom...): Selecting previously unselected package geographiclib-doc. Preparing to unpack .../geographiclib-doc_1.41-1~exp1_all.deb ... Unpacking geographiclib-doc (1.41-1~exp1) ... dpkg: error processing archive /var/cache/apt/archives/geographiclib-doc_1.41-1~exp1_all.deb (--unpack): trying to overwrite '/usr/share/doc/geographiclib/html/classGeographicLib_1_1Accumulator-members.html', which is also in package geographiclib-tools 1.37-3 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/geographiclib-doc_1.41-1~exp1_all.deb cheers, Andreas geographiclib-tools=1.37-3_geographiclib-doc=1.41-1~exp1.log.gz Description: application/gzip
Bug#770659: Bug WebRCT Chromium
Just tried video-chat on Hangoust into version 42.0.2311.90-1 (Debian Testing) The bug is stil in this version...anyone can confirm this?
Bug#776801: fontconfig-config: symlink 70-no-bitmaps.conf is to a non-existing file
On Sun, 01 Feb 2015 21:48:42 +0100 Paul Pogonyshev pogonys...@gmail.com wrote: Package: fontconfig-config Version: 2.11.0-6.3 Severity: normal After installation of the system, /etc/fonts/conf.d/70-no-bitmaps.conf is a symlink to a non-existing target. I believe this is the same in stable, testing and unstable. As a result, Firefox sometimes chooses to use ugly bitmap fonts (e.g. on Stackoverflow), even though I installed all fonts with Aptitude. (For some reason, both Chromium and Konqueror use nice fonts on the very same page.) As a workaround I deleted the link and changed it to point to /usr/share/fontconfig/conf.avail/70-no-bitmaps.conf instead. After restarting, Firefox then started using proper fonts. Same issue here on a wheezy-jessie upgrade. -- .''`.Sébastien Villemot : :' :Debian Developer `. `' http://sebastien.villemot.name `- GPG Key: 4096R/381A7594 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694025: Debian package of 'Oz' uploaded to mentors.debian.net
Hi. I recently found myself setting up a libvirtd/KVM-based virtual machine, and needed a way to build VM images from the command line. I searched around, and found the Oz project: https://github.com/clalancette/oz/wiki Testing Oz on a newly installed Jessie rc2 machine I found that it seemed to work. At least I was able to create VM images for Debian Wheezy and Jessie easily. Thus I decided to respin the old ITP for Oz: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694025 I have uploaded a package to mentors for easy review: https://mentors.debian.net/package/oz If you want to check out the Debian packaging you can get: https://github.com/jas4711/oz-dpkg With this, I'm asking for review/support/objections before uploading this into Debian properly. /Simon pgpwSphxMVUty.pgp Description: OpenPGP digital signatur
Bug#782703: dstat: crashes if TIOCGWINSZ and curses both unavailable
Package: dstat Version: 0.7.2-4 Severity: normal Tags: patch Dear Maintainer, I recently encountered a crash on a machine with a slightly wonky terminal config. If both termios.TIOCGWINSZ and curses.tigetnum fail in initterm(), then we die in gettermsize() with NameError: global name 'termsize' is not defined. There are already fallbacks to handle this case, we just need to make sure termsize is initialized to a suitable value when no terminal info is available. Patch below does this. Paul diff -u clean/dstat dstat-0.7.2/dstat --- clean/dstat 2010-06-11 06:08:01.0 + +++ dstat-0.7.2/dstat 2015-03-23 11:44:39.510401178 + @@ -1998,6 +1998,7 @@ ### Unbuffered sys.stdout #sys.stdout = os.fdopen(1, 'w', 0) +termsize = None, 0 try: global fcntl, struct, termios import fcntl, struct, termios -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/2 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 dstat depends on: pn python:any none dstat recommends no packages. dstat 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#782700: Please drop $remote_fs init.d dependency to allow running early
Hello, Michael Biebl [2015-04-16 15:22 +0200]: While we are that topic, I think it would be better to not pull apparmor specifics into ifup@.service and networking.service, but rather have apparmor ship a native .service file and specify the correct orderings, maybe by hooking up in network-pre.target. Yes, fully agreed. I mostly did that in [1] to get an unintrusive fix for the freeze, i. e. tuning the autogenerated unit. But in Jessie+1 it would be really good if we got rid of rcS init.d scripts entirely. Then again, I'm not too familiar with AppArmor: Is every service, which wants to be confined by apparmor supposed to declare a After=apparmor.service in its service file? I don't think this is practical TBH. A MAC system might have profiles for pretty much every binary in the system, so every service could potentially be covered. Thus it's best to load and apply the profiles as early as possible. I know that there's work going on to teach systemd pid 1 about native loading of the profiles even before it starts any unit; but that isn't done yet. Until then we can just ensure that it runs before everything which has profiles and is a potential security issue. Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature
Bug#782611: linux-image-3.16.0-4-amd64: backlight on, white screen during text mode powersave on Acer Aspire One 725
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, On 15.04.2015 09:46, Jonas Smedegaard wrote: I've recently installed an Acer Aspire One 725 with Debian jessie, and found that the text mode console goes into powersave mode correctly the first time, but shows a white screen with full backlight power the second and subsequent time. This sounds similar (but not identical) to bug#766922. No, this is display powersave and text mode -- the other problem is suspend/hibernate and graphics mode. Simon -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBAgAGBQJVL8JDAAoJEH69OHuwmQgRfcEIAI4mrsHNBPaqIL86FzCUb/nu C2neVGb0t8Tdx0HtTu75Q1s5MbC33WjJZMgvSOqFvEtLPMwle0OaaftoirZqTwl8 L5PDR7xE8nexBUJt0tX6gNB/F4FvDTqptSVDox6x4D5Z8ln4lGaHwA5MR0Vp3Obx fgxf4MBKRg/7vOle0fOlQV95u71wQLy0U48T+g3udUFyESc9ApAgauIFNl+TVYmF 76XYOL4ZzSWSSf1MIXsUgohB08Uxta8WYk65BRRJtCZfQaShoDCGsgjXtnO3E94v sViIYN/9pUHDnsLnKMTr83++7LZwKG7h8CO/UY9uj93GjT5aZjcZTmwJmpOMMnY= =3YwI -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#782610: linux-image-3.16.0-4-amd64, xserver-xorg-video-radeon: Acer Aspire One 725: black screen in X after resume
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, On 15.04.2015 15:59, Alex Deucher wrote: When you say sleep, do you mean suspend/resume or dpms? Depending on the hw involved, this patch might help: http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=66c2b84ba6256bc5399eed45582af9ebb3ba2c15 Suspend/resume. There is another problem with DPMS in text mode, which got its own bug report. That patch looks like it could solve the problem -- I'm going to try it out, but it might be a few days/weeks until I can do that. Simon -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBAgAGBQJVL8WkAAoJEH69OHuwmQgRfRAH/285wweLduD+mz/P+YggUuPI +CJxIbcczuzO1dZIq93u1Sx6hydB1g1hIIOzEXp48Y+Fu0uNyMokQKHqWu2b5L4i ibRBjCXkryWycFq4DY5nI/LUeydOlqQOIHNknJtwxkxFts2q3pYeyEKTSvRi+y8E Ia/PG04HYncLjagzYCoq9hEEXSsYRqPXKSBnv8ylFdtmE5oJ4PyhU4Jix53uY0PW dQJrnkwNL7Q0DCxHycDb2Z8CijaycU41t71waW6HsUPXsrGp5wO3Yg8gWx4+L9ND yhEwia1pUWsP3TN6+JGFZMk4W1TbP+RTPn2Yq6FDCDBC9oqa8ZfNRu8PpUuTfhM= =4/5w -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#782488: multipath-tools: updates for compatibility with property blacklist
Hello,
I am also affected by this bug with a device which by defaults is always seen
has belonging to the blacklist since it does not have a proper SCSI_IDENT.*
udev property.
I have not tested the patch since I found a fast work around and not having
much time right now, but what is described in the email attached to the bug
would definitely solve the issue. The current work around I have is to add the
ID_SERIAL in the property of blacklist_exceptions as such :
blacklist_exceptions {
wwidXX
## property (ID_WWN|SCSI_IDENT_.*)
property (ID_WWN|SCSI_IDENT_.*|ID_SERIAL)
}
For this workaround to be fully function I also had to perform a
update_initramfs (so it is accounted for during boot).
Clearly it would be much better that udeb is already adding the expected
SCSI_IDENT_* properties to SCSI devices as proposed in patch with bug #782487
(sg3-utils: provide udev rules for multipath-tools)
Is it possible to raise the severity level of this bug to make it RC, and is
there a chance that both bugs (782487 and 782488) are solved before the release
so that the installation on systems relying on multipath would not require
workaround to be functional ?
Thank you very much for all the work already done.
Serge.
signature.asc
Description: Message signed with OpenPGP using GPGMail
Bug#782487: sg3-utils: provide udev rules for multipath-tools
As mentioned for bug #782488 (multipath-tools: updates for compatibility with
property blacklist)
Hello,
I am also affected by this bug with a device which by defaults is always seen
has belonging to the blacklist since it does not have a proper SCSI_IDENT.*
udev property.
I have not tested the patch since I found a fast work around and not having
much time right now, but what is described in the email attached to the bug
would definitely solve the issue. The current work around I have is to add the
ID_SERIAL in the property of blacklist_exceptions as such :
blacklist_exceptions {
wwidXX
## property (ID_WWN|SCSI_IDENT_.*)
property (ID_WWN|SCSI_IDENT_.*|ID_SERIAL)
}
For this workaround to be fully function I also had to perform a
update_initramfs (so it is accounted for during boot).
Clearly it would be much better that udeb is already adding the expected
SCSI_IDENT_* properties to SCSI devices as proposed in patch with bug #782487
Is it possible to raise the severity level of this bug to make it RC, and is
there a chance that both bugs (782487 and 782488) are solved before the release
so that the installation on systems relying on multipath would not require
workaround to be functional ?
Thank you very much for all the work already done.
Serge.
signature.asc
Description: Message signed with OpenPGP using GPGMail
Bug#782609: systemd-sysv,plymouth: user experience: plymouth animation hangs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Holger, On 15.04.2015 12:37, Holger Levsen wrote: Good idea: it's a stock Debian jessie installation with gnome, so the display manager is gdm. so you choose to install a default desktop system and got this? (or did you first install a non-graphical system and then apt-got into gnome?) The latter. These laptops come locked down from the factory with a BIOS password, so I installed the system by putting the harddisk into a different machine and running debootstrap, fixing the bootloader and moving the disk back, then running aptitude install gnome. Does this make much of a difference for the installation? My feeling on this bug is that this is more of a general problem rather than an individual package's fault. Simon -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBAgAGBQJVL8bwAAoJEH69OHuwmQgRAl4H/Au+kXVHIFdnvOZVaMxFJWC4 DAnn+mGJw19b4edQMI0Q42Ps/cFOmG2oIPTVVuWuSVVEX+FICLSfwk0lm5y1cpBl 3U5M2SQHh8O0k4DrQXsKu7CUNbgV0uKoyj/zRug6FQ7kPPBXbgNtFK7eU7Uo4gje ZPUcwxcvUnHmfLghD+5YwzrId8RjMUpEuopP5IbQ3H/hKlLkz9XrD/tm4I7itydu znAIottSGt3Rpch9oIaGnleaSAKqrqhkP6oho5QpJIqrBppUehmR0lEul5k/7E89 7Gx2MnIgyHkB7qNMnBpien0VLy+vY0e7GHKFme5GeoKnzr7UaEFuOVgJAetctwM= =D2TU -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#782700: Please drop $remote_fs init.d dependency to allow running early
Am 16.04.2015 um 15:22 schrieb Michael Biebl: Hi! On Thu, 16 Apr 2015 07:56:55 -0500 Martin Pitt mp...@debian.org wrote: apparmor's init.d script currently depends on $remote_fs. This is a rather heavy dependency and means that important processes like dhclient or NFS cannot be covered by apparmor as they need to start before. In the extreme case this also means that network-online.target, NetworkManager.service, dbus.service etc. all need to run during early boot (rcS in the old sysvinit world), which likely leads to dependency cycles. IMHO $local_fs should suffice as during booting the init.d script does not need much from /usr or /var. The exception is the click package hook processing, but this is only really significant for Ubuntu Touch images (which don't use /usr on NFS). The profile cache has been split into /etc/ and /var for this reason, so that on boot you only need the cache in /etc. The one in /var is only being used for click packages as far as I know. FTR, Ubuntu did that change in https://launchpad.net/ubuntu/+source/apparmor/2.9.1-0ubuntu5 The reason for Martin filing this bug is most likely [1]. While we are that topic, I think it would be better to not pull apparmor specifics into ifup@.service and networking.service, but rather have apparmor ship a native .service file and specify the correct orderings, maybe by hooking up in network-pre.target. Or maybe better: provide a native .service file, hook that up in sysinit.target and add Wants=network-pre.target Before=network-pre.target to apparmor.service. See man systemd.special -- 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#782700: Please drop $remote_fs init.d dependency to allow running early
Hi! On Thu, 16 Apr 2015 07:56:55 -0500 Martin Pitt mp...@debian.org wrote: apparmor's init.d script currently depends on $remote_fs. This is a rather heavy dependency and means that important processes like dhclient or NFS cannot be covered by apparmor as they need to start before. In the extreme case this also means that network-online.target, NetworkManager.service, dbus.service etc. all need to run during early boot (rcS in the old sysvinit world), which likely leads to dependency cycles. IMHO $local_fs should suffice as during booting the init.d script does not need much from /usr or /var. The exception is the click package hook processing, but this is only really significant for Ubuntu Touch images (which don't use /usr on NFS). The profile cache has been split into /etc/ and /var for this reason, so that on boot you only need the cache in /etc. The one in /var is only being used for click packages as far as I know. FTR, Ubuntu did that change in https://launchpad.net/ubuntu/+source/apparmor/2.9.1-0ubuntu5 The reason for Martin filing this bug is most likely [1]. While we are that topic, I think it would be better to not pull apparmor specifics into ifup@.service and networking.service, but rather have apparmor ship a native .service file and specify the correct orderings, maybe by hooking up in network-pre.target. Then again, I'm not too familiar with AppArmor: Is every service, which wants to be confined by apparmor supposed to declare a After=apparmor.service in its service file? Michael [1] https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=experimentalid=db920726c385e2c4ea9b6a82f010483db13dfa46 -- 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#782688: bluetooth speaker is not recognized in jessie
On 16 April 2015 at 05:33, Juha Heinanen j...@tutpro.com wrote: Package: pulseaudio Version: 5.0-13 When I start pulseaudio, I get to syslog error message: Apr 16 11:10:55 lohi pulseaudio[2039]: org.bluez.Manager.GetProperties() failed: org.freedesktop.DBus.Error.UnknownMethod: Method GetProperties with signature on interface org.bluez.Manager doesn't exist and I guess due to that, my bluetooth speaker is not recognized by pulseaudio. This is with latest Debian jessie, but with newer kernel: linux-image-3.17.7 The speaker worked fine with the same kernel in wheezy, where I used alsa instead of pulseaudio. Now that alsa is not anymore supported by jessie bluez, pulseaudio is my only possibility. I don't know against which package I should submit this. Please let me know if some other than pulseaudio. Please post a full debug log[1]. Also, is the speaker correctly connected to bluetooth? Maybe the problem is in the bluetooth side and not on pulseaudio. [1] https://wiki.ubuntu.com/PulseAudio/Log -- Saludos, Felipe Sateler -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782704: amispammer is configured to use some dead blacklists
Package: amispammer Version: 3.3-1 Severity: normal Dear Maintainer, The List of RBLs in amispammer is outdated, which leads to false positives. Example: amispammer -i some ipv6 address [...] Checking IP: some ipv6 address * bl.spamcop.net Blacklisted! REASON: v=spf1 -all * sbl.csma.biz Blacklisted! REASON: v=spf1 ip6:fd1b:212c:a5f9::/48 -all bio=d5558025ecb194887359991a00083c05d955cc15 * rsbl.aupads.org Blacklisted! REASON: Realtime Spammer-Machines Blacklist (DNS zonefile) of the UFRJ Antispam Database Center * bl.csma.biz Blacklisted! REASON: v=spf1 ip6:fd1b:212c:a5f9::/48 -all bio=d5558025ecb194887359991a00083c05d955cc15 * orvedb.aupads.org Blacklisted! REASON: Realtime Open-Relays machines List (DNS zonefile) of the UFRJ Antispam Database Center * spam.wytnij.to Blacklisted! REASON: v=spf1 ip6:fd1b:212c:a5f9::/48 -all bio=d5558025ecb194887359991a00083c05d955cc15 * will-spam-for-food.eu.org Blacklisted! REASON: This RBL is not maintained anymore. Please remove from your mail server configuration or bad things (such as randomly blocked mail) may happen by mistake. * korea.services.net Blacklisted! REASON: See http://korea.services.net; * cart00ney.surriel.com Blacklisted! REASON: DNSBL RHSBL export of http://cart00ney.org/ list v=spf1 -all As far as I am informed, all of the obove mentioned Blacklists have closed down. See also: https://bugs.launchpad.net/ubuntu/+source/amispammer/+bug/835614 Installed Package: amispammer: Installed: 3.3-1 Candidate: 3.3-1 -- System Information: Debian Release: 7.8 APT prefers stable-updates APT policy: (990, 'stable-updates'), (990, 'stable') Architecture: i386 (i686) Kernel: Linux 3.16.0-0.bpo.4-686-pae (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/bash Versions of packages amispammer depends on: ii libemail-sender-perl 0.110005-1 ii libnet-address-ip-local-perl 0.1.2-2 ii libnet-dns-perl 0.66-2+b2 ii libwww-perl 6.04-1 ii perl 5.14.2-21+deb7u2 amispammer recommends no packages. amispammer 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#782453: ibus-cangjie: Many UX issues fixed upstream
Any news? This would be a very important update for Debian users in Hong Kong or Taiwan. :-/ -- Mathieu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782705: release-notes: Interaction between logind and acpid
Package: release-notes Tags: jessie Hi, having both logind and acpid handle ACPI events can lead to undesired results, esp. with a non-default configuration. As an example, logind could try to shutdown the system on a power button press (default), but acpid was manually configured to just suspend the system. Please consider adding the paragraph below to the release notes to make users aware of this issue. Ansgar -- 5.6.5 Interaction between logind and acpid ACPI events can be handled by logind or acpid. In case both services are configured to handle events in different ways, this can lead to undesired results. We recommend to migrate any non-default settings to logind and uninstall acpid. Alternativly it is also possible to configure logind to ignore ACPI events by adding HandlePowerKey=ignore HandleSuspendKey=ignore HandleHibernateKey=ignore HandleLidSwitch=ignore to /etc/systemd/logind.conf. Note that this might change behaviour of desktop environments relying on logind. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#612402: similar issue affects /usr in Jessie
Hi, since Jessie will attempt to mount /usr in initramfs when using Systemd, this issue has somewhat broadened in scope. See the merged bug 781661. While I agree with the reasoning that UUID and LABEL are not correct for LVM volumes, and had in fact all our systems changed, this issue will still cause a system to be unable to boot after upgrading to Jessie. Not sure if it should be fixed or if it is enough to give a loud warning on upgrade. Regards, Marc -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782700: [pkg-apparmor] Bug#782700: Please drop $remote_fs init.d dependency to allow running early
Hello, Am Donnerstag, 16. April 2015 schrieb Michael Biebl: Or maybe better: provide a native .service file, hook that up in sysinit.target and add Wants=network-pre.target Before=network-pre.target to apparmor.service. See man systemd.special FYI: I received a service file for openSUSE some weeks ago from a contributor. Basically it's just a wrapper around the initscript (so probably not the final solution), but it's a good start nevertheless ;-) [Unit] Description=Load AppArmor profiles DefaultDependencies=no Before=sysinit.target After=systemd-journald-audit.socket ConditionSecurity=apparmor [Service] Type=oneshot ExecStart=/etc/init.d/boot.apparmor start ExecReload=/etc/init.d/boot.apparmor reload ExecStop=/etc/init.d/boot.apparmor stop RemainAfterExit=yes [Install] WantedBy=multi-user.target Also let me warn you that systemd comes with some problems for AppArmor: https://bugzilla.opensuse.org/show_bug.cgi?id=853019 Basically systemd maps systemctl restart apparmor to stop, then start, which means the confinement gets removed from running processes. Regards, Christian Boltz -- Whatever, but the purpose of software is to help users, not the other way round. No, developers are not to be considered users :-p [Carlos E. R. in opensuse-factory] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782702: header files installed directly in /usr/include
tags 782702 +pending
thanks
Thanks! Committed to git [1] will be uploaded after
alglib-3.9.0 will be accepted by FTP-masters.
[1]
http://anonscm.debian.org/cgit/debian-science/packages/alglib.git/commit/?h=experimentalid=6cb9e0591b611b504321d8afe79d29ac0d3c58cf
Cheers
Anton
2015-04-16 14:34 GMT+02:00 Vincent Nivoliers vincent.nivoli...@univ-lyon1.fr:
Package: libalglib-dev
Version: 3.8.2-3
Severity: minor
Tags: patch
When the package is installed, the header files are installed directly in
/usr/include. This creates for instance a file /usr/include/statistics.h.
I suggest to create a folder libalglib in /usr/include to install the
headers there. This is the behaviour found in other distributions like for
instance archlinux.
Although I am no debian packaging specialist, downloading the source package
and modifying it as follows yields the desired behaviour when the package is
built and installed.
diff -Naur alglib-3.8.2/CMakeLists.txt alglib-3.8.2_mine/CMakeLists.txt
--- alglib-3.8.2/CMakeLists.txt 2015-04-16 13:58:58.0 +0200
+++ alglib-3.8.2_mine/CMakeLists.txt2015-04-16 14:07:06.148389902 +0200
@@ -13,7 +13,7 @@
SOVERSION ${SOVERSION})
INSTALL(TARGETS alglib DESTINATION ${CMAKE_INSTALL_LIBDIR}/)
-INSTALL(FILES ${ALGLIB_HDR_LIB} DESTINATION ${CMAKE_INSTALL_INCLUDEDIR})
+INSTALL(FILES ${ALGLIB_HDR_LIB} DESTINATION
${CMAKE_INSTALL_INCLUDEDIR}/libalglib)
#===
ADD_EXECUTABLE(test_c tests/test_c.cpp)
diff -Naur alglib-3.8.2/debian/libalglib-dev.install
alglib-3.8.2_mine/debian/libalglib-dev.install
--- alglib-3.8.2/debian/libalglib-dev.install 2013-11-10
09:42:53.0 +0100
+++ alglib-3.8.2_mine/debian/libalglib-dev.install 2015-04-16
13:47:07.470418446 +0200
@@ -1,2 +1,2 @@
-usr/include/*
+usr/include/libalglib*
usr/lib/*/libalglib.so
-- System Information:
Debian Release: 8.0
APT prefers testing
APT policy: (990, 'testing'), (600, 'unstable'), (500, 'testing-updates')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/6 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: systemd (via /run/systemd/system)
Versions of packages libalglib-dev depends on:
ii libalglib3.8 3.8.2-3
libalglib-dev recommends no packages.
libalglib-dev suggests no packages.
-- no debconf information
--
debian-science-maintainers mailing list
debian-science-maintain...@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782712: pre-upload unblock request: systemd/215-17 for RC bug #751707
(Cc: debian-boot@ added.) Martin Pitt mp...@debian.org (2015-04-16): Hello release team, (With my d-i release manager hat.) yesterday I discovered that systemd breaks a common way of setting up plain cryptsetup partitions. Turns out that this has already been known for a while, but the impact wasn't appreciated enough: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751707 What happens is that systemd's cryptsetup integration ignores the offset= parameter in crypttab and instead uses the whole device. So if you had a swap or other partition underneath in order to identify the partition via UUID or label instead of an unreliable hardcoded device name, switching to systemd destroys the underlying metadata, and causes a boot hang as crypttab now refers to a nonexisting UUID/label. This is quite a common way to set up encrypted swap, the way that ecryptfs' own swap setup tool does it (the Ubuntu installer calls that if you select encrypt my home directory; I'm not sure whether Debian's installer does the same). Grepping for hash= in partman-* d-i packages led to partman-crypto, which seems responsible for this (no surprise here): http://anonscm.debian.org/cgit/d-i/partman-crypto.git/tree/finish.d/crypto_config There's no offset= there. Looking into partman-* in Ubuntu vivid, it turns out that one of them look at user-setup, and that's where the following is defined: | Template: user-setup/encrypt-home | Type: boolean | Default: false | # :sl2: | _Description: Encrypt your home directory? `---[ debian/user-setup-udeb.templates ]--- which is then used in user-setup-apply where there's a lot more (encryption-related) code than in Debian, which e.g. calls adduser with an option to encrypt home, which then calls some commands from the ecryptfs-utils package, but I don't see any offset in the ecryptfs-setup-private script. Anyway, asking for home encryption indeed leads to swap encryption, through a ecryptfs-setup-swap call, which in turn triggers: |echo cryptswap$i UUID=$uuid /dev/urandom swap,offset=1024,cipher=aes-xts-plain64 /etc/crypttab `---[ src/utils/ecryptfs-setup-swap ]--- The same file in the Debian package has no offset, so I guess that means Debian is rather safe. IMHO this qualifies as data loss, and we cannot repair this automatically after the damage happened. So I'd really like to fix this in jessie, and I upgraded it to RC. The patch is quite straightforward. It got a first review by upstream, I made it a bit more defensive since the first version, and it'll probably land today. I attached my test script to the upstream bug [1] which allows you to play around with various offset= options and verify that it doesn't destroy the initial part of the partition. I realize this is a somewhat awkward timing as we want to deep-freeze in two days, and this means an udeb change (although only formally as there are no effective changes in udev). 215-16 should go into testing tonight, and I'm prepared to upload 215-17 with that fix right after that with urgency=high. What would you recommend how to proceed? Provided a review by the release team, I'm OK with letting this go into testing between D-I Jessie RC3 (to be released at the end of this week) and a possible extra debian-installer upload (before the release). I'm not exactly entirely sure how to deal with D-I for Jessie past RC3 anyway: - Do nothing? - BinNMU to make sure it's built against last-migrated components? - Sourceful upload in case there's any changes staged in git during the last week? (I hope that won't be necessary.) Mraw, KiBi. signature.asc Description: Digital signature
Bug#694025: Debian package of 'Oz' uploaded to mentors.debian.net
Den Thu, 16 Apr 2015 15:55:43 +0100 skrev Bug#694025: Debian package of 'Oz' uploaded to mentors.debian.net: On Thu, Apr 16, 2015 at 04:35:14PM +0200, Simon Josefsson wrote: Hi. I recently found myself setting up a libvirtd/KVM-based virtual machine, and needed a way to build VM images from the command line. I searched around, and found the Oz project: https://github.com/clalancette/oz/wiki Testing Oz on a newly installed Jessie rc2 machine I found that it seemed to work. At least I was able to create VM images for Debian Wheezy and Jessie easily. Thus I decided to respin the old ITP for Oz: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694025 I have uploaded a package to mentors for easy review: https://mentors.debian.net/package/oz If you want to check out the Debian packaging you can get: https://github.com/jas4711/oz-dpkg With this, I'm asking for review/support/objections before uploading this into Debian properly. On sufficiently new Debian you can also do: $ virt-builder debian-7 (and no need for root privileges). Thanks for the pointer. Trying it out, it looks to me that they don't offer the same functionality. virt-builder downloads an image that someone else prepared (not sure how?) and adapts it. oz-install creates a new image by booting a normal d-i ISO together with preseeding. Is it possible to do that with virt-builder? For my purposes, oz-install's approach is even better than virt-install's approach of doing debootstrapping, since I want the full D-I experience. So these tools look complementary to me. To reduce confusion, maybe a small discussion in the package description or README.Debian is appropriate to explain the differences. Btw, thanks for doing the Oz Debian packaging. Was there any reason it wasn't uploaded back then? Thanks, /Simon pgpTN7NKV60yu.pgp Description: OpenPGP digital signatur
Bug#782716: linux-image-3.16.0-4-amd64: unable to handle kernel paging request at fffffffffffffffb (__destroy_inode+0x83/0xf0)
X-Reportbug-Version: 6.6.3 Package: src:linux Version: 3.16.7-ckt9-2 Severity: normal Dear Maintainer, * What led up to the situation? no specific action, occurs multiple on day. older kernels work as expected (wheezy as an example). Sometimes the system freezes with this entry as one of the last entries. -- 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-ckt9-2 (2015-04-13) ** Command line: BOOT_IMAGE=/vmlinuz-3.16.0-4-amd64 root=UUID=7cd2ad1b-b6a1-475e-bcb2-a497526db155 ro quiet ** Tainted: DCO (5248) * Kernel has oopsed before. * Module from drivers/staging has been loaded. * Out-of-tree module has been loaded. ** Kernel log: [ 12.364609] rtl2832_sdr: module is from the staging directory, the quality is unknown, you have been warned. [ 12.367006] usb 2-4: Registered as swradio0 [ 12.367016] i2c i2c-10: rtl2832_sdr: Realtek RTL2832 SDR attached [ 12.377443] Registered IR keymap rc-empty [ 12.377663] input: GIGABYTE U7300 as /devices/pci:00/:00:13.2/usb2/2-4/rc/rc0/input10 [ 12.378167] rc0: GIGABYTE U7300 as /devices/pci:00/:00:13.2/usb2/2-4/rc/rc0 [ 12.384555] IR NEC protocol handler initialized [ 12.387980] IR RC5(x) protocol handler initialized [ 12.391919] IR RC6 protocol handler initialized [ 12.395673] IR JVC protocol handler initialized [ 12.401929] IR Sony protocol handler initialized [ 12.403368] IR SANYO protocol handler initialized [ 12.407744] IR Sharp protocol handler initialized [ 12.411973] IR MCE Keyboard/mouse protocol handler initialized [ 12.414858] input: MCE IR Keyboard/Mouse (dvb_usb_rtl28xxu) as /devices/virtual/input/input11 [ 12.417683] usb 2-4: dvb_usb_v2: schedule remote query interval to 400 msecs [ 12.421376] lirc_dev: IR Remote Control driver registered, major 250 [ 12.427844] rc rc0: lirc_dev: driver ir-lirc-codec (dvb_usb_rtl28xxu) registered at minor = 0 [ 12.427856] IR LIRC bridge handler initialized [ 12.429538] usb 2-4: dvb_usb_v2: 'GIGABYTE U7300' successfully initialized and connected [ 12.429655] usbcore: registered new interface driver dvb_usb_rtl28xxu [ 12.463771] hidraw: raw HID events driver (C) Jiri Kosina [ 12.489153] usbcore: registered new interface driver usbhid [ 12.489157] usbhid: USB HID core driver [ 12.491294] input: Logitech USB-PS/2 Optical Mouse as /devices/pci:00/:00:12.0/usb3/3-1/3-1:1.0/0003:046D:C03E.0001/input/input12 [ 12.492335] hid-generic 0003:046D:C03E.0001: input,hidraw0: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-:00:12.0-1/input0 [ 12.492661] input: Microsoft Comfort Curve Keyboard 3000 as /devices/pci:00/:00:12.0/usb3/3-2/3-2:1.0/0003:045E:0780.0002/input/input13 [ 12.492740] hid-generic 0003:045E:0780.0002: input,hidraw1: USB HID v1.11 Keyboard [Microsoft Comfort Curve Keyboard 3000] on usb-:00:12.0-2/input0 [ 12.494958] input: Microsoft Comfort Curve Keyboard 3000 as /devices/pci:00/:00:12.0/usb3/3-2/3-2:1.1/0003:045E:0780.0003/input/input14 [ 12.495061] hid-generic 0003:045E:0780.0003: input,hidraw2: USB HID v1.11 Device [Microsoft Comfort Curve Keyboard 3000] on usb-:00:12.0-2/input1 [ 12.966890] vboxdrv: Found 2 processor cores. [ 12.980735] vboxdrv: fAsync=1 offMin=0x2a5bf offMax=0x2a5bf [ 12.980888] vboxdrv: TSC mode is 'asynchronous', kernel timer mode is 'normal'. [ 12.980890] vboxdrv: Successfully loaded version 4.3.18_Debian (interface 0x001a0008). [ 13.109921] ip_tables: (C) 2000-2006 Netfilter Core Team [ 13.126232] vboxpci: IOMMU not found (not registered) [ 13.134179] ip6_tables: (C) 2000-2006 Netfilter Core Team [ 13.282457] cfg80211: Calling CRDA to update world regulatory domain [ 13.362136] cfg80211: World regulatory domain updated: [ 13.362143] cfg80211: DFS Master region: unset [ 13.362145] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) [ 13.362149] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) [ 13.362151] cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) [ 13.362153] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A) [ 13.362156] cfg80211: (517 KHz - 525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A) [ 13.362158] cfg80211: (525 KHz - 533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (0 s) [ 13.362160] cfg80211: (549 KHz - 573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s) [ 13.362162] cfg80211: (5735000 KHz - 5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A) [ 13.362164] cfg80211: (5724 KHz - 6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A) [ 13.949341] r8169 :02:00.0 eth0: link down [ 13.949358] r8169 :02:00.0 eth0: link down [ 13.949948] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 14.455872] sde: sde1 [
Bug#694025: Debian package of 'Oz' uploaded to mentors.debian.net
On Thu, Apr 16, 2015 at 07:24:26PM +0200, Simon Josefsson wrote: Thanks for the pointer. Trying it out, it looks to me that they don't offer the same functionality. virt-builder downloads an image that someone else prepared (not sure how?) At the moment using: https://github.com/libguestfs/libguestfs/blob/master/builder/website/debian.sh but I intend to get out of the business of building disk images for virt-builder, and use the cloud images prepared by distros. and adapts it. oz-install creates a new image by booting a normal d-i ISO together with preseeding. Yup, that is basically correct. Of course virt-builder is way faster. Is it possible to do that with virt-builder? No -- although you could run the script above, building your own images for your own virt-builder template repository, and then use virt-builder to quickly deploy them. For my purposes, oz-install's approach is even better than virt-install's approach of doing debootstrapping, since I want the full D-I experience. So these tools look complementary to me. Correct. To reduce confusion, maybe a small discussion in the package description or README.Debian is appropriate to explain the differences. Btw, thanks for doing the Oz Debian packaging. Was there any reason it wasn't uploaded back then? That's a good question -- I don't actually recall at all :-/ Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com Fedora Windows cross-compiler. Compile Windows programs, test, and build Windows installers. Over 100 libraries supported. http://fedoraproject.org/wiki/MinGW -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782712: pre-upload unblock request: systemd/215-17 for RC bug #751707
Hello Cyril, Cyril Brulebois [2015-04-16 19:40 +0200]: Anyway, asking for home encryption indeed leads to swap encryption, through a ecryptfs-setup-swap call, which in turn triggers: |echo cryptswap$i UUID=$uuid /dev/urandom swap,offset=1024,cipher=aes-xts-plain64 /etc/crypttab `---[ src/utils/ecryptfs-setup-swap ]--- The same file in the Debian package has no offset, so I guess that means Debian is rather safe. Well, it actually means that it's even more broken :-( If you don't specify an offset at all, then you can only boot this system once. Then your partition will be overwritten with random data entirely, and the next time you won't have any matching UUID any more, and you again get a hanging boot (this affects sysvinit and upstart too). I. e. you will have exactly the same effect. So to properly fix this, we need: (1) the fix to add the offset=: https://bazaar.launchpad.net/~ecryptfs/ecryptfs/trunk/revision/840 (Updating the used cipher would also be a good idea, but not essential) This fix alone is sufficient under sysvinit and upstart. (2) this systemd fix to actually respect offset= when booting under systemd. Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature
Bug#116358: Liste neuer Stellenausschreibungen für Sie
Sehr geehrte Damen und Herren, die Arbeitsvermittlung stellt Ihnen nachfolgend eine interessante Stelle in einem internationalen Team im Home-office Bereich vor, ohne Fahrtkosten, ohne Anfahrt, ohne Verkehrsstress: Wir schaffen qualitative und attraktive Stellen auch in ländlichen Regionen europaweit und bieten gleichzeitig exzellente Qualität für unsere Auftraggeber. Ab sofort sind folgenden Stellen zu besetzen: Mitarbeiter (m/w) für den Support im Home-office in der Abteilung Telekommunikation und Büroarbeit Ihre Tätigkeitsschwerpunkte wären: - Unterlagen empfangen, bearbeiten und weiterleiten - Unterlagen kopieren/einscannen - E-Mails beantworten - Tätigkeit im Home Office in freien Zeiteinteilung - Arbeit mit zur Verfügung gestellten Büroausstattungen Was von Ihnen erwartet wird: - Problemloser Umgang mit Email, PC und Internet - Deutsch fließend, Fremdsprachen sind vorteilhaft - erfolgsorientiertes Teamwork - Genauigkeit und Zielstrebigkeit Wir bieten Ihnen einen Arbeitsplatz in Festanstellung oder als Selbständige mit einem Stundenlohn von 20 Euro Brutto in der Stunde in eigenverantwortlichen Arbeitsweise und einer modernen Beschäftigungsform, sowie eine abwechslungsreiche Tätigkeit ohne Arbeitsweg mit flexiblen Arbeitszeiten. Es werden keine Fachkenntnisse vorausgesetzt. Die Einarbeitung findet schrittweise durch professionelle Mitarbeiten statt. Die benötigte technische Ausstattung stellen wir Ihnen ohne zusätzlichen Kosten zur Verfügung. Die Stelle kann gerne nebenberuflich besetzt werden sowie von Rentnern und Hausfrauen. Sie sind offen für flexible Arbeitszeitmodelle und die Arbeit im Home-office? Möchten Sie sich dieser interessanten und herausfordernden neuen Aufgabe stellen? Dann senden Sie uns Ihre Bewerbung mit Lichtbild an: alniberto...@usa.com Ihre persönlichen Unterlagen behandeln wir vertraulich. Es grüßt Sie Ihre Lange SA -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
