Processed: Re: Bug#755722: systemd must sync systemclock to RTC on shutdown
Processing control commands: > reassign -1 util-linux 2.25.2-5 Bug #755722 [systemd-sysv] systemd must sync systemclock to RTC on shutdown Bug reassigned from package 'systemd-sysv' to 'util-linux'. Ignoring request to alter found versions of bug #755722 to the same values previously set Ignoring request to alter fixed versions of bug #755722 to the same values previously set Bug #755722 [util-linux] systemd must sync systemclock to RTC on shutdown Marked as found in versions util-linux/2.25.2-5. > severity -1 normal Bug #755722 [util-linux] systemd must sync systemclock to RTC on shutdown Severity set to 'normal' from 'grave' -- 755722: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755722 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#755722: systemd must sync systemclock to RTC on shutdown
Control: reassign -1 util-linux 2.25.2-5 Control: severity -1 normal I still disagree with critical: - If the hardware clock is so broken that at the next boot it has an earlier time than on the previous boot/ntpdate, then writing it once more at shutdown isn't going to entirely fix this problem, as it will again go sufficiently wrong if you don't reboot immediately but after some time. - Second, this doesn't "break" fsck: fsck already correctly notices that the last write time is in the future and handles that appropriately; at least that's what the original reporter mentioned. Also, under sysvinit and upstart it is util-linux which does the hwclock <-> sysclock dance, thus reassigning this. We shouldn't put this logic into different packages for different init systems. I also disagree this should be done in the first place. But I don't want to put myself into eternal wars and "who shouds the loudest wins", so I'll keep this bug open and won't make any further Severity: adjustments. Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature
Processed: your mail
Processing commands for cont...@bugs.debian.org: > forwarded 22 https://bugs.freedesktop.org/89129 Bug #22 [xdg-utils] xdg-open: another command injection vulnerability Set Bug forwarded-to-address to 'https://bugs.freedesktop.org/89129'. > thanks Stopping processing here. Please contact me if you need assistance. -- 22: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=22 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#775715: marked as done (libv8-3.14: limiting security support)
Your message dated Fri, 13 Feb 2015 06:18:42 + with message-id and subject line Bug#775715: fixed in libv8-3.14 3.14.5.8-8.1 has caused the Debian Bug report #775715, regarding libv8-3.14: limiting security support to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 775715: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775715 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- package: libv8-3.14 version: 3.14.5.8-8 severity: grave tags: security Hi, the security team has decided that this package will not receive security support for jessie. This has already been documented in the debian-security-support package for about two months: libv8-3.14 Not covered by security support, only suitable for trusted content Please include a README.Debian.security file describing the security support status and problems for the package. See [0] for an example. Since this will be clearly documented in multiple places, it will no longer be necessary to treat unfixed security bugs as release critical. Best wishes, Mike [0] https://bugs.debian.org/702775 --- End Message --- --- Begin Message --- Source: libv8-3.14 Source-Version: 3.14.5.8-8.1 We believe that the bug you reported is fixed in the latest version of libv8-3.14, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 775...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Gilbert (supplier of updated libv8-3.14 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 13 Feb 2015 05:59:08 + Source: libv8-3.14 Binary: libv8-dev libv8-3.14-dev libv8-3.14.5 libv8-3.14-dbg Architecture: source Version: 3.14.5.8-8.1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Michael Gilbert Description: libv8-3.14-dbg - V8 JavaScript engine - debugging symbols libv8-3.14-dev - V8 JavaScript engine - development files for 3.14 branch libv8-3.14.5 - V8 JavaScript engine - runtime library libv8-dev - V8 JavaScript engine - development files for latest branch Closes: 775715 Changes: libv8-3.14 (3.14.5.8-8.1) unstable; urgency=medium . * Non-maintainer upload. * Add README.Debian.security documenting the lack of security support for this package for jessie (closes: #775715). Checksums-Sha1: 7c393767c6080ab532fd7e6398c3b08644c2944c 3235 libv8-3.14_3.14.5.8-8.1.dsc ab37da53d6bf9e04fab14f775938adda448e294b 42008 libv8-3.14_3.14.5.8-8.1.debian.tar.xz Checksums-Sha256: 3d4c8583b3231c11958dfda90fc74b9224df5c22526bdbe648ea91b376e6b75e 3235 libv8-3.14_3.14.5.8-8.1.dsc be307ca966a837606de9a9cfccc1fdb4396230654f240a119421783d10e08de9 42008 libv8-3.14_3.14.5.8-8.1.debian.tar.xz Files: 9a73fe4f352d6f7aa664e0c1bc223c81 3235 libs optional libv8-3.14_3.14.5.8-8.1.dsc 4c615a63ff3d74524874b1774f9f89f3 42008 libs optional libv8-3.14_3.14.5.8-8.1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQQcBAEBCgAGBQJU3ZWDAAoJELjWss0C1vRzvDAf/2ChKDi/C8hrssXXCV059j17 rppgU0FKg198aGwU48EqHm1rACMImXtKrmWRpKo87uCqw4FI8nG9tvBhM3Y5GUzW eFTbVlprdEMddtITQJ/Q95lOImJjQKRiVVOvS1Xta75NPrpepaPVIw0xPe0QtW9c 4gfVhq4KXGfv39Z4Khs30dnKArk4rMR7Hv4K9j0gm4ehjXWrrvu/soNE3TRlNUKB GABrO9QdsjBS8QSEy2XeqKX/R/5lyJpalZILwe2XTtVSrcnnVzMpLl5tARO/Yewy I8cZQAZjboDxYXmf6HJjz1mDVrqngKHjLwjF9kLhaaJ4gMR9+dzEtP2mx1Xm5e+e jjJ0ZQrhK1RRo/EzpBLo2gKbbygq51H0YaJWg6/hzyDUBnLEfkvP5Ig4hrLNknvO 3QX7JcMLNPDU20GZiQUZ9J2BqQoKZbZ1Asua+Ohvh2ENQzsqAm3qU7f6yGzZ5v6m JSdRz5ZssNus6SRQK8vdeiymgUHer8oN5V6qm2waAwSf1sIMexKEArK9LWtNdmMV 6E/KIHbW+3369EXdEd/yC7pJh6872ZZoA0OCC30PCEEK48pzYOwLSbPV2+bbWWMu 1x4p6ujL1vS+jTpiYHpdR9xoVCI0kmYQ0qM/nk8KJLHbbsczDIhwFP5650BuWiMc 4+uosOS6iVWOMIGeFpDkDohdXsMs5V4jXe/Am8EnVBu5Bpea0Xq+9ko3t9LuOiSv V/w1Q8lN0G3aFwvOYGEu6QofMYoqpGB0mfwYsxWKQHDds0LKuV5Uyw1Tuu4BbEU0 iR2s2t6owxo4RuePIkfBYpPTgkTgG8qkGDm3DatHk9VpL9Ps4Oy7+L4sreI7NQE9 StFN4HrX8yMoWaNxKp05p5iHbxuqrs6qBFxa/8vAvWDSVpAsuzzfBqDlhddYJ84O 5lBein4U4SAoTqRh5olB54xo8vfLudbojjv42GFT5OejAq1FFGAA/H3nar7iYI+d 0Pf2+m6UeA+dYSgdYdBMXxa1KXkqaOw1TeDUjiJIcEBSRDjTkyQs/DBncOrtLNSA gSBYXvMRKN4MBH7ppDP4uCQVIwq6npkTREKBj+YgidHIVoLq7VLJDi3+ucZyFsKd +FTUNWziyt6+8mZMLXHUdeZV3cTYrynF6CqKvMleuhI+f7S/fc
Processed: Re: Bug#755722: systemd must sync systemclock to RTC on shutdown
Processing commands for cont...@bugs.debian.org: > severity 755722 grave Bug #755722 [systemd-sysv] systemd must sync systemclock to RTC on shutdown Severity set to 'grave' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 755722: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755722 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#778238: marked as done (graphicsmagick: CVE-2014-8355)
Your message dated Fri, 13 Feb 2015 06:03:48 + with message-id and subject line Bug#778238: fixed in graphicsmagick 1.3.20-3+deb8u1 has caused the Debian Bug report #778238, regarding graphicsmagick: CVE-2014-8355 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 778238: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778238 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: graphicsmagick Version: 1.3.20-3+b1 Severity: grave Tags: security Hi, the PCX bug from https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767240 also affects graphicsmagick (this is CVE-2014-8355). This was fixed upstream in http://sourceforge.net/p/graphicsmagick/code/ci/4426024497f9ed26cbadc5af5a5de55ac84796ff/ Cheers, Moritz --- End Message --- --- Begin Message --- Source: graphicsmagick Source-Version: 1.3.20-3+deb8u1 We believe that the bug you reported is fixed in the latest version of graphicsmagick, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 778...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Laszlo Boszormenyi (GCS) (supplier of updated graphicsmagick package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 12 Feb 2015 17:40:52 + Source: graphicsmagick Binary: graphicsmagick libgraphicsmagick3 libgraphicsmagick1-dev libgraphicsmagick++3 libgraphicsmagick++1-dev libgraphics-magick-perl graphicsmagick-imagemagick-compat graphicsmagick-libmagick-dev-compat graphicsmagick-dbg Architecture: source amd64 all Version: 1.3.20-3+deb8u1 Distribution: unstable Urgency: high Maintainer: Laszlo Boszormenyi (GCS) Changed-By: Laszlo Boszormenyi (GCS) Description: graphicsmagick - collection of image processing tools graphicsmagick-dbg - format-independent image processing - debugging symbols graphicsmagick-imagemagick-compat - image processing tools providing ImageMagick interface graphicsmagick-libmagick-dev-compat - image processing libraries providing ImageMagick interface libgraphics-magick-perl - format-independent image processing - perl interface libgraphicsmagick++1-dev - format-independent image processing - C++ development files libgraphicsmagick++3 - format-independent image processing - C++ shared library libgraphicsmagick1-dev - format-independent image processing - C development files libgraphicsmagick3 - format-independent image processing - C shared library Closes: 778238 Changes: graphicsmagick (1.3.20-3+deb8u1) unstable; urgency=high . * Backport upstream PCX fix for CVE-2014-8355 (closes: #778238). Checksums-Sha1: 9663f5231f85c6e96ef0855fe7565cfb88b5c114 2788 graphicsmagick_1.3.20-3+deb8u1.dsc 0fcef398e3e570c261aa6a023b68418039752583 138752 graphicsmagick_1.3.20-3+deb8u1.debian.tar.xz a4b06d37dabafc37be77a36bf6bc2344ad9ab55c 783352 graphicsmagick_1.3.20-3+deb8u1_amd64.deb 11d2dc7b6022566aac9bd3f92a8681a6b0d69ee3 1093180 libgraphicsmagick3_1.3.20-3+deb8u1_amd64.deb 2b72dc64c911a55d8ee4e826f1b8320b59772187 1278818 libgraphicsmagick1-dev_1.3.20-3+deb8u1_amd64.deb 1bf996d0b558cecb4f03d33e7bb60b1272ed7297 113256 libgraphicsmagick++3_1.3.20-3+deb8u1_amd64.deb 427e501f33e11b9e82a26af717f9255ac0be91b5 294876 libgraphicsmagick++1-dev_1.3.20-3+deb8u1_amd64.deb 6f27bec2f04de018bae65d54f732f3a67426f167 70762 libgraphics-magick-perl_1.3.20-3+deb8u1_amd64.deb e98fed131091eb2dc6d0384773f8bf283ae7a18d 2216224 graphicsmagick-dbg_1.3.20-3+deb8u1_amd64.deb be90d6f9aed417c6f3d42fd36c8dbd7bb917048f 22856 graphicsmagick-imagemagick-compat_1.3.20-3+deb8u1_all.deb 64f1055c512d9750de5b6f2514c7db3ca35c2ced 26322 graphicsmagick-libmagick-dev-compat_1.3.20-3+deb8u1_all.deb Checksums-Sha256: ef0bc34593f1341131f8e5674d059b9bff4fdf7197d2f4891a8d6bee8236eb23 2788 graphicsmagick_1.3.20-3+deb8u1.dsc f1547e6b8c4e53da1ada0ee93a3497da78f94b80da13d56b79c463f52256293d 138752 graphicsmagick_1.3.20-3+deb8u1.debian.tar.xz bdd9ada6bc253188773e56cc8e41e83360a2f6d457893ab97f0eebe73fa7a0a2 783352 graphicsmagick_1.3.20-3+deb8u1_amd64.deb d6091cc1e1ded7750e9565042354d546e4c8d5257c43a3bd38554ee01b415130 1093180 libgraphicsmagick3_1.3.20-3+deb8u1_amd64.deb 40951a1feadfe50e8
Bug#777665: marked as done (salt-common: salt-call needs python-msgpack to run)
Your message dated Fri, 13 Feb 2015 05:48:55 + with message-id and subject line Bug#777665: fixed in salt 2014.1.13+ds-3 has caused the Debian Bug report #777665, regarding salt-common: salt-call needs python-msgpack to run to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 777665: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777665 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: salt-common Version: 2014.1.13+ds-2 Severity: grave Justification: renders package unusable salt-common contains the salt-call binary which is useful in itself, but it needs to depend on python-msgpack or otherwise salt-call will fail to run. You can reproduce it in a minimal chroot by running: # apt-get install --no-install-recommends salt-common # salt-call --local state.highstate [CRITICAL] Unable to import msgpack or msgpack_pure python modules WARNING: '/etc/salt' directory does not exist. [ERROR ] Could not cache minion ID: [Errno 2] No such file or directory: '/etc/salt/minion_id' [WARNING ] Console logging already configured [CRITICAL] Failed to load grains defined in grain file core.zmqversion in function , error: Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/salt/loader.py", line 1034, in gen_grains ret = fun() File "/usr/lib/python2.7/dist-packages/salt/grains/core.py", line 1205, in zmqversion import zmq ImportError: No module named zmq [CRITICAL] Failed to load grains defined in grain file core.zmqversion in function , error: Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/salt/loader.py", line 1034, in gen_grains ret = fun() File "/usr/lib/python2.7/dist-packages/salt/grains/core.py", line 1205, in zmqversion import zmq ImportError: No module named zmq [ERROR ] An un-handled exception was caught by salt's global exception handler: NameError: global name 'msgpack' is not defined Traceback (most recent call last): File "/usr/bin/salt-call", line 11, in salt_call() File "/usr/lib/python2.7/dist-packages/salt/scripts.py", line 82, in salt_call client.run() File "/usr/lib/python2.7/dist-packages/salt/cli/__init__.py", line 319, in run caller.run() File "/usr/lib/python2.7/dist-packages/salt/cli/caller.py", line 144, in run ret = self.call() File "/usr/lib/python2.7/dist-packages/salt/cli/caller.py", line 81, in call ret['return'] = func(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/salt/modules/state.py", line 294, in highstate serial.dump(ret, fp_) File "/usr/lib/python2.7/dist-packages/salt/payload.py", line 155, in dump fn_.write(self.dumps(msg)) File "/usr/lib/python2.7/dist-packages/salt/payload.py", line 125, in dumps return msgpack.dumps(msg) NameError: global name 'msgpack' is not defined Traceback (most recent call last): File "/usr/bin/salt-call", line 11, in salt_call() File "/usr/lib/python2.7/dist-packages/salt/scripts.py", line 82, in salt_call client.run() File "/usr/lib/python2.7/dist-packages/salt/cli/__init__.py", line 319, in run caller.run() File "/usr/lib/python2.7/dist-packages/salt/cli/caller.py", line 144, in run ret = self.call() File "/usr/lib/python2.7/dist-packages/salt/cli/caller.py", line 81, in call ret['return'] = func(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/salt/modules/state.py", line 294, in highstate serial.dump(ret, fp_) File "/usr/lib/python2.7/dist-packages/salt/payload.py", line 155, in dump fn_.write(self.dumps(msg)) File "/usr/lib/python2.7/dist-packages/salt/payload.py", line 125, in dumps return msgpack.dumps(msg) NameError: global name 'msgpack' is not defined # apt-get install --no-install-recommends python-msgpack # salt-call --local state.highstate [CRITICAL] Failed to load grains defined in grain file core.zmqversion in function , error: Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/salt/loader.py", line 1034, in gen_grains ret = fun() File "/usr/lib/python2.7/dist-packages/salt/grains/core.py", line 1205, in zmqversion import zmq ImportError: No module named zmq [CRITICAL] Failed to load grains defined in grain file core.zmqversion in function
Bug#769941: marked as done (libgstreamer-plugins-base1.0-0: Iceweasel crashes with "gst_app_src_set_size: assertion 'GST_IS_APP_SRC (appsrc)' failed")
Your message dated Thu, 12 Feb 2015 22:01:14 -0500 with message-id and subject line Re: Bug#769941: libgstreamer-plugins-base1.0-0: Iceweasel crashes with "gst_app_src_set_size: assertion 'GST_IS_APP_SRC (appsrc)' failed" has caused the Debian Bug report #769941, regarding libgstreamer-plugins-base1.0-0: Iceweasel crashes with "gst_app_src_set_size: assertion 'GST_IS_APP_SRC (appsrc)' failed" to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 769941: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769941 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libgstreamer-plugins-base1.0-0 Version: 1.4.4-2 Severity: critical Justification: breaks unrelated software Hello, Iceweasel has started crashing when I try and login into Google Mail. Looking at the backtrace it appears to be caused by libgstreamer, so filing a bug against this package (AFAIK this particular package is where those functions came from). Apologies if this was supposed to filed against a different package - feel free to re-assign in that case. ** (iceweasel:5279): CRITICAL **: gst_app_src_set_size: assertion 'GST_IS_APP_SRC (appsrc)' failed [New Thread 0x7fffb7ea5700 (LWP 5356)] [New Thread 0x7fffb726c700 (LWP 5357)] [New Thread 0x7fffafcff700 (LWP 5358)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fffb726c700 (LWP 5357)] gst_ffmpegauddec_frame (ffmpegdec=0x0, data=0x7fffb8ddb090 "\377\373\220d", size=0, have_data=0x1a1, ret=0x1a1) at gstavauddec.c:644 644 gstavauddec.c: No such file or directory. (gdb) bt #0 gst_ffmpegauddec_frame (ffmpegdec=0x0, data=0x7fffb8ddb090 "\377\373\220d", size=0, have_data=0x1a1, ret=0x1a1) at gstavauddec.c:644 #1 0x7fffb684c3b0 in gst_ffmpegauddec_handle_frame (decoder=0x7fffb0ce32a0, inbuf=0x7fffc2661d20) at gstavauddec.c:751 #2 0x7fffb854d047 in gst_audio_decoder_push_buffers (dec=0x7fffb0ce32a0, force=-1033495264) at gstaudiodecoder.c:1416 #3 0x7fffb854d42b in gst_audio_decoder_chain_forward (dec=0x7fffb0ce32a0, buffer=0x7fffc2661c10) at gstaudiodecoder.c:1519 #4 0x7fffb854e4f8 in gst_audio_decoder_chain (pad=0x7fffb9cfe4c0 <_gst_debug_min>, parent=0x7fffb0ce32a0, buffer=0x7fffc2661c10) at gstaudiodecoder.c:1798 #5 0x7fffb9a55d6f in gst_pad_chain_data_unchecked (data=, type=, pad=) at gstpad.c:3836 #6 gst_pad_push_data (pad=0x7fffbc5f5da0, type=3092570464, data=0x7fffc2661c10) at gstpad.c:4069 #7 0x7fffb959a524 in gst_base_parse_push_frame (parse=0x7fffc4a05230, frame=0x7fffc4cd8990) at gstbaseparse.c:2302 #8 0x7fffb959db7f in gst_base_parse_handle_and_push_frame (frame=, parse=) at gstbaseparse.c:2134 #9 gst_base_parse_finish_frame (parse=0x7fffc4a05230, frame=0x7fffc4cd8990, size=0) at gstbaseparse.c:2459 #10 0x7fffb727f0eb in ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstaudioparsers.so #11 0x7fffb9596ac5 in gst_base_parse_handle_buffer (parse=0x7fffc4a05230, buffer=0x7fffc2661390, skip=0x7fffb726bdbc, flushed=0x7fffb726bdb8) at gstbaseparse.c:1961 #12 0x7fffb9597087 in gst_base_parse_scan_frame (parse=0x7fffc4a05230, klass=) at gstbaseparse.c:3121 #13 0x7fffb959bf22 in gst_base_parse_loop (pad=0x7fffb0b58000) at gstbaseparse.c:3194 #14 0x7fffb9a83ad6 in gst_task_func (task=0x7fffbc4605f0) at gsttask.c:317 #15 0x7fffef0212c8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7fffef020935 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x77bc70a4 in start_thread (arg=0x7fffb726c700) at pthread_create.c:309 #18 0x770ebccd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Best regards, George -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/8 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 libgstreamer-plugins-base1.0-0 depends on: ii iso-codes 3.57-1 ii libc6 2.19-13 ii libglib2.0-0 2.42.1-1 ii libgstreamer1.0-0 1.4.4-2 ii liborc-0.4-0 1:0.4.22-1 ii multiarch-support 2.19-13 ii zlib1g 1:1.2.8.dfsg-2 Versions of packages libgstreamer-plugins-base1.0-0 recommends: ii gstreamer1.0-plugins-base 1.4.4-2 Versions of packages libgstreamer-plugins-base1.0-0 suggests: pn gstreamer-codec-install | gnome-codec-install ii libvisual-0.4-plugins 0.4.0.dfsg.1-7 -- n
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tag 775691 + pending Bug #775691 [src:matplotlib] matplotlib: CVE-2013-1424: printf buffer overrun Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 775691: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775691 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#777706: A couple of patches
I've attached here two debdiffs for a couple of options which may be helpful. It looks like the underlying bug has been fixed between versions 1.1 and 1.2 of NUT-Monitor, as the configuration directory is now being created with a sensible mode (0700). The attached patch `fix-permissions-on-start.debdiff' causes NUT-Monitor to detect and correct unsafe permissions on ~/.nut-monitor automatically when it is started. It also includes a NEWS item explaining this. The second patch, `just-warn.debdiff' merely includes a NEWS item explaining the problem and suggesting a fix. Hopefully one of these approaches may be sufficient. -- Michael Fincham Catalyst fix-permissions-on-start.debdiff Description: Binary data just-warn.debdiff Description: Binary data pgpYRk48JG1Yx.pgp Description: PGP signature
Bug#775812: base: HP EliteBook 840 G1 laptop fails to halt/poweroff after 15/12/2015 upgrade
On Tue, 20 Jan 2015 12:42:05 +0100 Miguel wrote: > I'm running Debian testing (jessie) on an HP EliteBook 840 G1 laptop. > Everything goes reasonably well, even very well, except that after > running apt-get update/upgrade on Monday (15 December) I cannot halt > (poweroff) the computer. When I try to switch it off it just reboots. I > manage to get it in sleep mode by pressing the the physical start button > and this is what I'm doing since then. No previous problems in this > sense before that upgrade. I have 'intel-microcode' and > 'firmware-linux-free' installed from the beginning. I can confirm this problem on exactly the same notebook and with 'intel-microcode' installed as well. > After that report I was able to sometimes halt the computer correctly either > from the gnome interface or from the console. I would like to add that I also didn't succeed in halting the notebook by using the GRUB command 'halt', it just rebooted after entering this command. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#767764: marked as done (ldm: setting LDM_DIRECTX=True crashes gnome, gnome-classic, cinnamon, cinnamon-2d)
Your message dated Thu, 12 Feb 2015 23:03:55 + with message-id and subject line Bug#767764: fixed in ltsp 5.5.4-3 has caused the Debian Bug report #767764, regarding ldm: setting LDM_DIRECTX=True crashes gnome, gnome-classic, cinnamon, cinnamon-2d to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 767764: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767764 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ltsp Severity: important Hi, i am setting LDM_DIRECTX=True in lts.conf to speedup X. Now i can't start Gnome or cinnamon. The outher Desktops i try work well (Mate, kde, blackbox, openbox) If i use: X -query server :1 or login over ssh and then start session with gnome-session or cinnamon-session everything works fine. LDM_DIRECTX=False works too. I test it with old thin-client (i586, Nvidia GeForce2 MX/MX 400) and a new one (amd64, Nvidia) with nouveau. Holger Sander -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16-3-amd64 (SMP w/6 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- End Message --- --- Begin Message --- Source: ltsp Source-Version: 5.5.4-3 We believe that the bug you reported is fixed in the latest version of ltsp, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 767...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Vagrant Cascadian (supplier of updated ltsp package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 12 Feb 2015 14:22:07 -0800 Source: ltsp Binary: ltsp-server ltsp-server-standalone ltsp-client-core ltsp-client ltsp-client-builder Architecture: source all Version: 5.5.4-3 Distribution: unstable Urgency: medium Maintainer: LTSP Debian Maintainers Changed-By: Vagrant Cascadian Description: ltsp-client - complete LTSP client environment ltsp-client-builder - build an LTSP environment in the installer target (udeb) ltsp-client-core - basic LTSP client environment ltsp-server - basic LTSP server environment ltsp-server-standalone - complete LTSP server environment Closes: 767764 777184 Changes: ltsp (5.5.4-3) unstable; urgency=medium . * Add debian/ltsp-client-core.maintscript to remove obsolete /etc/init.d/ltsp-client-setup and /etc/default/ltsp-client-setup leftover from squeeze upgrades (Closes: #777184). Thanks to Andreas Beckmann! . * Apply patch from upstream to no longer remove nouveau_vieux driver on boot, which is terribly hackish and no longer appropriate with current versions of LDM (Closes: #767764). Checksums-Sha1: 7c45c51a77df697a66fdac8ada65650158f9bf04 2285 ltsp_5.5.4-3.dsc 1286328b713917e3554e133f74db85ba9d06793d 77324 ltsp_5.5.4-3.debian.tar.xz ad0669a58db5849cd1b3accd248d3dbb16a01583 266018 ltsp-server_5.5.4-3_all.deb 06efec1ca554609f91aea25bb76573b20fb23511 146194 ltsp-server-standalone_5.5.4-3_all.deb 7772333f0a90086e1cf9b48cd70c4c94f4f43dbe 11124 ltsp-client-builder_5.5.4-3_all.udeb Checksums-Sha256: f8a6d0983ebe896a89e42c682fdcb568c65ee4220e2486c4898d85ef0b5d133f 2285 ltsp_5.5.4-3.dsc 6e1439b6aa1c176bdb7384a03fc7cc8f326ad35ba43ef4351c94524b702ab27c 77324 ltsp_5.5.4-3.debian.tar.xz c5ab7a9ab3e034a004a550ef3894b5e795c797eca354bd252ae8e22d293ac2fe 266018 ltsp-server_5.5.4-3_all.deb 6b410e19c567f335bff9941f83211136197d3655fcfe91738ae4d627e0618c01 146194 ltsp-server-standalone_5.5.4-3_all.deb 2d1ab382b8ef6899c8b91114902f382f39459a1d2bad785ef3070b39118a114f 11124 ltsp-client-builder_5.5.4-3_all.udeb Files: c7c9bc88cfd3288cb899918e0c098217 2285 misc extra ltsp_5.5.4-3.dsc adea51d0ddb89022125e361994535280 77324 misc extra ltsp_5.5.4-3.debian.tar.xz 2b4b03669eb116e5efc4a9c7180add02 266018 misc extra ltsp-server_5.5.4-3_all.deb aca8ec5e53c95d48e2e7cbdac8d9efda 146194 misc extra ltsp-server-standalone_5.5.4-3_all.deb 377df414f1d784ce837fc386e676bb0c 11124 debian-installer extra ltsp-client-builder_5.5.4-3_all.udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1
Bug#777613: marked as done (systemctl enable/disable does not handle alias symlinks if there is a corresponding sysv script)
Your message dated Thu, 12 Feb 2015 22:34:13 + with message-id and subject line Bug#777613: fixed in systemd 218-9 has caused the Debian Bug report #777613, regarding systemctl enable/disable does not handle alias symlinks if there is a corresponding sysv script to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 777613: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777613 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd Version: 218-1 Severity: serious Michael spotted that with the experimental systemd, "systemd enable/disable ssh" does not create/remove the /etc/systemd/system/sshd.service symlink any more, it just calls update-rc.d. This worked up to 217-n, but not with 218-1 any more. git bisect confirms that this is to blame: http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=4c6443101c376a1 Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature --- End Message --- --- Begin Message --- Source: systemd Source-Version: 218-9 We believe that the bug you reported is fixed in the latest version of systemd, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 777...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Biebl (supplier of updated systemd package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 12 Feb 2015 18:45:12 +0100 Source: systemd Binary: systemd systemd-sysv libpam-systemd libsystemd0 libsystemd-dev libsystemd-login-dev libsystemd-daemon-dev libsystemd-journal-dev libsystemd-id128-dev udev libudev1 libudev-dev udev-udeb libudev1-udeb libgudev-1.0-0 gir1.2-gudev-1.0 libgudev-1.0-dev python3-systemd systemd-dbg Architecture: source amd64 Version: 218-9 Distribution: experimental Urgency: medium Maintainer: Debian systemd Maintainers Changed-By: Michael Biebl Description: gir1.2-gudev-1.0 - libgudev-1.0 introspection data libgudev-1.0-0 - GObject-based wrapper library for libudev libgudev-1.0-dev - libgudev-1.0 development files libpam-systemd - system and service manager - PAM module libsystemd-daemon-dev - systemd utility library (transitional package) libsystemd-dev - systemd utility library - development files libsystemd-id128-dev - systemd 128 bit ID utility library (transitional package) libsystemd-journal-dev - systemd journal utility library (transitional package) libsystemd-login-dev - systemd login utility library (transitional package) libsystemd0 - systemd utility library libudev-dev - libudev development files libudev1 - libudev shared library libudev1-udeb - libudev shared library (udeb) python3-systemd - Python 3 bindings for systemd systemd- system and service manager systemd-dbg - system and service manager (debug symbols) systemd-sysv - system and service manager - SysV links udev - /dev/ and hotplug management daemon udev-udeb - /dev/ and hotplug management daemon (udeb) Closes: 759320 777601 777613 Changes: systemd (218-9) experimental; urgency=medium . [ Martin Pitt ] * debian/tests/logind: With dropped systemd-logind-launch we don't have a visible /sys/fs/cgroup/systemd/ any more under cgmanager. So adjust the test to check /proc/self/cgroup instead. * Add unit-config autopkgtest to check systemd unit/sysv init enabling and disabling via systemctl. This also reproduces #777613. * systemctl: Always install/enable/disable native units, even if there is a corresponding SysV script and we call update-rc.d; while the latter handles WantedBy=, it does not handle Alias=. (Closes: #777613) * cgroup: Don't trim cgroup trees created by someone else, just the ones that systemd itself created. This avoids cleaning up empty cgroups from e.g. LXC. (Closes: #777601) * Don't parse /etc/mtab for current mounts, but /proc/self/mountinfo. If the former is a file, it's most likely outdated on boot, leading to race conditions and unmounts during boot. (LP: #1419623) . [ Michael Biebl ] * Explici
Bug#778266: Directory traversal
Source: libarchive Severity: grave Tags: security Hi, please see http://www.openwall.com/lists/oss-security/2015/01/16/7 for details. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#775643: pymvpa: FTBFS in jessie: tests failed
Hi guys, sorry for not chiming in timely and wasting your time trying to reproduce it David. This FTBFS is due to a non-robust unittest which fails at times on some data (which is randomly generated). Since that line of mvpa is out of development for a while (we have python-mvpa2) the best would be just to remove this one from both jessie and sid archives. snapshots.d.n will have it for those who might need it to reproduce previous results. Cheers! On Thu, 12 Feb 2015, David Prévot wrote: > Control: tags -1 + unreproducible > Hi, > On Sun, Jan 18, 2015 at 02:11:38AM +0100, Lucas Nussbaum wrote: > > Source: pymvpa > > Version: 0.4.8-3 > > Severity: seriousd > > Tags: jessie sid > > User: debian...@lists.debian.org > > Usertags: qa-ftbfs-20150118 qa-ftbfs > > Justification: FTBFS in jessie on i386 > I’ve not managed to reproduce this issue today (build it four time in a > row in jessie on i386, as well as in sid and amd64 too). > > The full build log is available from: > > > > http://aws-logs.debian.net/ftbfs-logs/2015/01/18/pymvpa_0.4.8-3_jessie-i386.log > Please find attached my latest build log as well as a diff against the > above failing one, maybe the version changes in the build-dependencies > during the last month are the culprit. > Regards > David -- Yaroslav O. Halchenko, Ph.D. http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org Research Scientist,Psychological and Brain Sciences Dept. Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#775643: pymvpa: FTBFS in jessie: tests failed
Processing control commands: > tags -1 + unreproducible Bug #775643 [src:pymvpa] pymvpa: FTBFS in jessie: tests failed Added tag(s) unreproducible. -- 775643: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775643 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: retitle 777583 to debian/copyright for smartmontools is too restrictive ...
Processing commands for cont...@bugs.debian.org: > retitle 777583 debian/copyright for smartmontools is too restrictive Bug #777583 [smartmontools] Incorrect debian/copyright for smartmontools Changed Bug title to 'debian/copyright for smartmontools is too restrictive' from 'Incorrect debian/copyright for smartmontools' > severity 777583 wishlist Bug #777583 [smartmontools] debian/copyright for smartmontools is too restrictive Severity set to 'wishlist' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 777583: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777583 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#777583: Incorrect debian/copyright for smartmontools
retitle -1 debian/copyright for smartmontools is too restrictive severity -1 wishlist On Tue, Feb 10, 2015 at 01:30:33AM -0500, Mark H Weaver wrote: > Package: smartmontools > debian/copyright claims that smartmontools is distributed under GPLv2, > but the copyright notices in its source files include the "or (at your > option) any later version" language. In that case, the Debian package “just” claims a more restrictive term of use than it actually is, but it is not wrong either (GPL-2 is included in GPL-2+, it’s as if the maintainer decided on the option). Regards David signature.asc Description: Digital signature
Processed: wait for release team input
Processing commands for cont...@bugs.debian.org: > block 778196 by 778254 Bug #778196 [openafs-modules-dkms] Fails to built with current Jessie's kernel 778196 was not blocked by any bugs. 778196 was not blocking any bugs. Added blocking bug(s) of 778196: 778254 > thanks Stopping processing here. Please contact me if you need assistance. -- 778196: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778196 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: user debian-secur...@lists.debian.org, usertagging 778238 ..., tagging 778238
Processing commands for cont...@bugs.debian.org: > user debian-secur...@lists.debian.org Setting user to debian-secur...@lists.debian.org (was car...@debian.org). > usertags 778238 + tracked There were no usertags set. Usertags are now: tracked. > retitle 778238 graphicsmagick: CVE-2014-8355 Bug #778238 [graphicsmagick] CVE-2014-8355 Changed Bug title to 'graphicsmagick: CVE-2014-8355' from 'CVE-2014-8355' > tags 778238 + upstream fixed-upstream Bug #778238 [graphicsmagick] graphicsmagick: CVE-2014-8355 Added tag(s) upstream and fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 778238: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778238 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: Pending #777622: lazarus contains files licensed under APSL (non-DFSG)
Processing commands for cont...@bugs.debian.org: > # I am working on this, pieces seem to be in place, only needs time > tags 777622 pending Bug #777622 [src:lazarus] lazarus contains files licensed under APSL (non-DFSG) Added tag(s) pending. > owner 777622 ! Bug #777622 [src:lazarus] lazarus contains files licensed under APSL (non-DFSG) Owner recorded as Paul Gevers . > thanks Stopping processing here. Please contact me if you need assistance. -- 777622: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777622 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#776530: marked as done (dnsmasq: fails to start when dbus is not installed and running systemd)
Your message dated Thu, 12 Feb 2015 18:48:29 + with message-id and subject line Bug#776530: fixed in dnsmasq 2.72-3 has caused the Debian Bug report #776530, regarding dnsmasq: fails to start when dbus is not installed and running systemd to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 776530: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776530 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: dnsmasq Version: 2.72-2 Severity: serious Justification: fails to start with default init system Thanks for maintaining dnsmasq! When runnning dnsmasq with systemd on a freshly installed system, without dbus installed, dnsmasq fails to start. It seems like dnsmasq should depend or at least recommend dbus if it needs dbus in order to function on a default install with systemd. Some ugly chain of "dbus | sysvinit-core | upstart" might also be worth entertaining... Running systemd without dbus installed: ● dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server Loaded: loaded (/lib/systemd/system/dnsmasq.service; enabled) Drop-In: /run/systemd/generator/dnsmasq.service.d └─50-dnsmasq-$named.conf, 50-insserv.conf-$named.conf Active: failed (Result: timeout) since Wed 2015-01-28 17:20:30 PST; 7s ago Process: 4353 ExecStart=/etc/init.d/dnsmasq systemd-exec (code=exited, status=0/SUCCESS) Process: 4350 ExecStartPre=/usr/sbin/dnsmasq --test (code=exited, status=0/SUCCESS) Main PID: 4353 (code=exited, status=0/SUCCESS) Jan 28 17:19:00 testprop dnsmasq[4353]: compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect Jan 28 17:19:00 testprop dnsmasq[4353]: DBus support enabled: bus connection pending Jan 28 17:19:00 testprop dnsmasq[4353]: DNS service limited to local subnets Jan 28 17:19:00 testprop dnsmasq-dhcp[4353]: DHCP, IP range 192.168.99.20 -- 192.168.99.250, lease time 1h Jan 28 17:19:00 testprop dnsmasq[4353]: reading /etc/resolv.conf Jan 28 17:19:00 testprop dnsmasq[4353]: using nameserver 192.168.122.1#53 Jan 28 17:19:00 testprop dnsmasq[4353]: read /etc/hosts - 5 addresses Jan 28 17:20:30 testprop systemd[1]: dnsmasq.service start operation timed out. Terminating. Jan 28 17:20:30 testprop dnsmasq[4353]: exiting on receipt of SIGTERM Jan 28 17:20:30 testprop systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server. Jan 28 17:20:30 testprop systemd[1]: Unit dnsmasq.service entered failed state. After running apt-get install dbus, it works fine: ● dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server Loaded: loaded (/lib/systemd/system/dnsmasq.service; enabled) Drop-In: /run/systemd/generator/dnsmasq.service.d └─50-dnsmasq-$named.conf, 50-insserv.conf-$named.conf Active: active (running) since Wed 2015-01-28 17:17:50 PST; 4s ago Process: 4099 ExecStartPost=/etc/init.d/dnsmasq systemd-start-resolvconf (code=exited, status=0/SUCCESS) Process: 4093 ExecStartPre=/usr/sbin/dnsmasq --test (code=exited, status=0/SUCCESS) Main PID: 4095 (dnsmasq) CGroup: /system.slice/dnsmasq.service └─4095 /usr/sbin/dnsmasq --keep-in-foreground --enable-dbus -x /var/run/dnsmasq/dnsmasq.pid -u dnsmasq -7 /etc/dnsmasq.d,.dpkg-dist,.dpkg-old,.dpkg-new --local-service Jan 28 17:17:50 testprop dnsmasq[4093]: dnsmasq: syntax check OK. Jan 28 17:17:50 testprop dnsmasq[4095]: started, version 2.72 cachesize 150 Jan 28 17:17:50 testprop dnsmasq[4095]: compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect Jan 28 17:17:50 testprop dnsmasq[4095]: DBus support enabled: connected to system bus Jan 28 17:17:50 testprop dnsmasq[4095]: DNS service limited to local subnets Jan 28 17:17:50 testprop dnsmasq-dhcp[4095]: DHCP, IP range 192.168.99.20 -- 192.168.99.250, lease time 1h Jan 28 17:17:50 testprop dnsmasq[4095]: reading /etc/resolv.conf Jan 28 17:17:50 testprop dnsmasq[4095]: using nameserver 192.168.122.1#53 Jan 28 17:17:50 testprop dnsmasq[4095]: read /etc/hosts - 5 addresses live well, vagrant -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16.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 Init: systemd (via /run/systemd/system) Versions of packages dnsmasq depends on: ii dnsmasq-base 2.72-2 ii init-system-helpers 1.22 ii netbase
Processed: update openafs-modules-dkms build failure severity
Processing commands for cont...@bugs.debian.org: > severity 778196 grave Bug #778196 [openafs-modules-dkms] Fails to built with current Jessie's kernel Severity set to 'grave' from 'critical' > thanks Stopping processing here. Please contact me if you need assistance. -- 778196: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778196 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#777583: Incorrect debian/copyright for smartmontools
Package: smartmontools Version: 6.3+svn4002-2+b2 Followup-For: Bug #777583 Attached find a debdiff and a git-diff to add the "or (at your option) any later version" clause to debian/copyright. The debdiff is created using HEAD in git as the original package (so probably NOT the version that is currently in testing) -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages smartmontools depends on: ii debianutils 4.4+b1 ii init-system-helpers 1.22 ii libc62.19-13 ii libcap-ng0 0.7.4-2 ii libgcc1 1:4.9.2-10 ii libselinux1 2.3-2 ii libstdc++6 4.9.2-10 ii lsb-base 4.1+Debian13+nmu1 Versions of packages smartmontools recommends: ii bsd-mailx [mailx] 8.1.2-0.20141216cvs-1 Versions of packages smartmontools suggests: pn gsmartcontrol pn smart-notifier -- no debconf information diff -Nru smartmontools-6.3+svn4002/debian/changelog smartmontools-6.3+svn4002/debian/changelog --- smartmontools-6.3+svn4002/debian/changelog 2015-02-12 17:12:37.0 +0100 +++ smartmontools-6.3+svn4002/debian/changelog 2015-02-12 17:52:38.0 +0100 @@ -1,3 +1,13 @@ +smartmontools (6.3+svn4002-2) UNRELEASED; urgency=medium + + [ Giuseppe Iuculano ] + * Correct maintscript syntax (Closes: #766178) + + [ IOhannes m zmölnig ] + * Fix license: it's really GPL-2+ (Closes: #777583) + + -- Giuseppe Iuculano Thu, 12 Feb 2015 17:52:25 +0100 + smartmontools (6.3+svn4002-1) unstable; urgency=low * [03a62f0] Set EnvironmentFile=-/etc/default/smartmontools in smartd.service diff -Nru smartmontools-6.3+svn4002/debian/copyright smartmontools-6.3+svn4002/debian/copyright --- smartmontools-6.3+svn4002/debian/copyright 2015-02-12 17:48:31.0 +0100 +++ smartmontools-6.3+svn4002/debian/copyright 2015-02-12 17:50:15.0 +0100 @@ -14,5 +14,5 @@ License: You are free to distribute this software under the terms of the GNU General -Public License Version 2. The full text of this license can be found in the -file /usr/share/common-licenses/GPL-2 +Public License Version 2, or (at your option) any later version. The full text +of this license can be found in the file /usr/share/common-licenses/GPL-2 >From 40173c4dde3bf76e5bf801c9df1c8cffea11d9a2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?IOhannes=20m=20zm=C3=B6lnig?= Date: Thu, 12 Feb 2015 17:15:57 +0100 Subject: [PATCH] Fix license: it's really GPL-2+ (Closes: #777583) --- debian/copyright | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/debian/copyright b/debian/copyright index 0803ab3..22d8118 100644 --- a/debian/copyright +++ b/debian/copyright @@ -14,5 +14,5 @@ Copyright: License: You are free to distribute this software under the terms of the GNU General -Public License Version 2. The full text of this license can be found in the -file /usr/share/common-licenses/GPL-2 +Public License Version 2, or (at your option) any later version. The full text +of this license can be found in the file /usr/share/common-licenses/GPL-2 -- 2.1.4
Processed: severity of 770628 is normal
Processing commands for cont...@bugs.debian.org: > # The previous severity bumps had no justification. Even if providing a > working init-script would be valuable, the package in Wheezy (and before) > didn’t, so even if the severity is bumped again to RC, I’d advocate the RT to > tag it jessie-ignore. > severity 770628 normal Bug #770628 [deluged] deluged: Starting daemon has no effect Severity set to 'normal' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 770628: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770628 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#757698: marked as done ([network-manager] network-manager: Not authorized to control networking)
Your message dated Thu, 12 Feb 2015 17:03:34 + with message-id and subject line Bug#760281: fixed in cgmanager 0.36-1 has caused the Debian Bug report #760281, regarding [network-manager] network-manager: Not authorized to control networking to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 760281: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760281 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: network-manager Version: 0.9.10.0-1 Severity: normal --- Please enter the report below this line. --- I cannot control network-manager as a normal user anymore. I used to be able to use the network-manager KDE tray applet: connect/disconnect the wired interface, connect/disconnect the VPN interfaces. However after a recent upgrade (systemd? libpam-systemd?) I cannot use it anymore. Clicking the connect/disconnect button on wired interfaces does nothing, and on VPN interfaces I get this error: Aug 10 19:31:40 debian NetworkManager[2724]: Failed to activate 'MyVPN': Not authorized to control networking. I can reproduce this everytime, after a reboot too. It is reproducible with nmcli too: $ nmcli connection up MyVPN Error: Connection activation failed: Not authorized to control networking. As a workaround I can use sudo to invoke the cli, but I loose the convenience of the tray applet (which is useful with WiFi, but I don't have WiFi on this box): $ sudo nmcli connection up MyVPN My user is member of netdev, plugdev, and I haven't changed group membership lately: $ id uid=1000(edwin) gid=1000(edwin) groups=1000(edwin),24(cdrom),25(floppy),27(sudo),29(audio),30(dip),44(video),46(plugdev),104(scanner),107(bluetooth),109(netdev),122(kvm),123(libvirt) I am using sysvinit-core and systemd-shim, i.e. I am not using systemd-as-pid1. systemd logs this to kmsg (I opened a separate bug about that), I don't know if it is related: [ 27.565727] systemd-logind[3382]: Failed to enable subscription: No such method 'Subscribe' [ 27.566597] systemd-logind[3382]: New seat seat0. [ 27.567357] systemd-logind[3382]: Watching system buttons on /dev/input/event1 (Power Button) [ 27.567475] systemd-logind[3382]: Watching system buttons on /dev/input/event0 (Power Button) [ 27.570542] systemd-logind[3382]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 27.570555] systemd-logind[3382]: Failed to start user service: Unknown unit: user@1000.service [ 27.572213] systemd-logind[3382]: New session 2 of user edwin. [ 27.572249] systemd-logind[3382]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. [ 841.498260] systemd-logind[3382]: Failed to start unit user@65534.service: Unknown unit: user@65534.service [ 841.498272] systemd-logind[3382]: Failed to start user service: Unknown unit: user@65534.service [ 841.499580] systemd-logind[3382]: New session c1 of user nobody. [ 841.517534] systemd-logind[3382]: Failed to abandon scope session-c1.scope [ 841.517542] systemd-logind[3382]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc1_2escope [ 841.524278] systemd-logind[3382]: New session c2 of user nobody. [ 841.537574] systemd-logind[3382]: Failed to abandon scope session-c2.scope [ 841.537583] systemd-logind[3382]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc2_2escope [ 841.545551] systemd-logind[3382]: New session c3 of user nobody. [ 900.432607] systemd-logind[3382]: Failed to abandon scope session-c3.scope [ 900.432618] systemd-logind[3382]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc3_2escope --- System information. --- Architecture: amd64 Kernel: Linux 3.14-2-amd64 Debian Release: jessie/sid 500 unstableftp.ro.debian.org 500 testing ftp.ro.debian.org 1 experimentalftp.ro.debian.org --- Package information. --- Depends (Version) | Installed =-+- libc6 (>= 2.17) | libdbus-1-3(>= 1.0.2) | libdbus-glib-1-2 (>= 0.102) | libgcrypt11(>= 1.4.5) | libglib2.0-0 (>= 2.37.3) | libgnutls-deb0-28 (>= 3.2.10-0) | libgudev-1.0-0 (>= 165) | libmm-glib0(>= 1.0.0) | libndp0
Bug#760281: marked as done (xfce4: cannot mount usb drive: "Not authorized to perform operation")
Your message dated Thu, 12 Feb 2015 17:03:34 + with message-id and subject line Bug#760281: fixed in cgmanager 0.36-1 has caused the Debian Bug report #760281, regarding xfce4: cannot mount usb drive: "Not authorized to perform operation" to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 760281: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760281 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xfce4 Version: 4.10.1 Severity: important Having recently updated testing, I discover that I can no longer mount a USB drive by double-clicking on it in the panel. (If this should be reassigned to xfce4-panel or elsewhere, please do so!) I am running with a SysV init system, not systemd, so I wonder whether this bug is similar to that described in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758557 The error message which pops up says "Failed to mount "drive name" - Not authorized to perform operation". Julian -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xfce4 depends on: ii gtk2-engines-xfce 3.0.1-2 ii libxfce4ui-utils 4.10.0-5 ii orage 4.10.0-1+b1 ii thunar 1.6.3-1 ii xfce4-appfinder4.10.1-1 ii xfce4-mixer4.10.0-3 ii xfce4-panel4.10.1-1 ii xfce4-session 4.10.1-8 ii xfce4-settings 4.10.1-2 ii xfconf 4.10.0-2 ii xfdesktop4 4.10.2-3 ii xfwm4 4.10.1-2 Versions of packages xfce4 recommends: ii desktop-base 7.0.3 ii tango-icon-theme 0.8.90-5 ii thunar-volman 0.8.0-4 ii xfce4-notifyd 0.2.4-3 ii xorg 1:7.7+7 Versions of packages xfce4 suggests: pn gtk3-engines-xfce ii xfce4-goodies4.10 ii xfce4-power-manager 1.2.0-5.1 -- no debconf information --- End Message --- --- Begin Message --- Source: cgmanager Source-Version: 0.36-1 We believe that the bug you reported is fixed in the latest version of cgmanager, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 760...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Serge Hallyn (supplier of updated cgmanager package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 11 Feb 2015 22:24:24 -0600 Source: cgmanager Binary: cgmanager cgmanager-tests libcgmanager0 libcgmanager-dev Architecture: source amd64 all Version: 0.36-1 Distribution: unstable Urgency: medium Maintainer: Serge Hallyn Changed-By: Serge Hallyn Description: cgmanager - Central cgroup manager daemon cgmanager-tests - Central cgroup manager daemon (tests) libcgmanager-dev - Central cgroup manager daemon (dev) libcgmanager0 - Central cgroup manager daemon (client library) Closes: 760281 767468 Changes: cgmanager (0.36-1) unstable; urgency=medium . * New upstream release. - start in a clean mounts namespace (Closes: #760281, #767468) * add *list_keys* to symbols file * pass -c4 to dh_makeshlibs to catch missing smbols in the future Checksums-Sha1: 93181f6eddce3d289978f70b5052d1e87450ef9a 2052 cgmanager_0.36-1.dsc 611f8da062bf8504df07d9ae8526d92bc227c801 428374 cgmanager_0.36.orig.tar.gz ff13af416b6ad0ab3ce31ea471fb736c9a975d4d 10600 cgmanager_0.36-1.debian.tar.xz bba9efc9473c0292c75ce676c50408731edfb9cd 78972 cgmanager_0.36-1_amd64.deb 92d2953ddcb9d70065fa27a75c85611eb3dec4de 13806 cgmanager-tests_0.36-1_all.deb ce525b80b8432e6b30ef0a9ff65f8f8c49ba9726 40898 libcgmanager0_0.36-1_amd64.deb a2aa076fbf60d25663143069dc3396fe0d4ea3d1 10890 libcgmanager-dev_0.36-1_amd64.deb Checksums-Sha256: b09a684963fe3e311924514e2d8e156fdfc38343e33ee2bd87bcf006df0e84d0 2052 cgmanager_0.36-1.dsc f4707f0130efb50ccd8a1900e7ae626c0631947528ce921a63b15ef848fb2a0d 428374 cgmanager_0.36.orig.tar.gz b38a50ee57bb945f81c233fdd2f39eb163ddcd671caf1558c2f6fd6bb47936e4 10600 cgmanager_0.36-1.debian.ta
Bug#760366: marked as done (gdm3: Stopped showing any users, no way to log in)
Your message dated Thu, 12 Feb 2015 17:03:34 + with message-id and subject line Bug#760281: fixed in cgmanager 0.36-1 has caused the Debian Bug report #760281, regarding gdm3: Stopped showing any users, no way to log in to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 760281: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760281 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gdm3 Version: 3.12.2-2.1 Severity: important Since I upgraded my system today, gdm3 does not show any users for selection and no input fields asking for user names or passwords. So log-in to anyone is not possible. I needed to switch to another terminal and install kdm. I'm hoping for a quick fix so I can switch back to gdm3. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gdm3 depends on: ii accountsservice0.6.37-3 ii adduser3.113+nmu3 ii dconf-cli 0.20.0-2 ii dconf-gsettings-backend0.20.0-2 ii debconf [debconf-2.0] 1.5.53 ii gir1.2-gdm33.12.2-2.1 ii gnome-session-bin 3.12.1-3 ii gnome-settings-daemon 3.12.2-1+b1 ii gnome-shell3.12.2-3 ii gsettings-desktop-schemas 3.12.2-1 ii guake [x-terminal-emulator]0.4.4-1 ii libaccountsservice00.6.37-3 ii libatk1.0-02.12.0-1 ii libaudit1 1:2.3.7-1 ii libc6 2.19-10 ii libcairo-gobject2 1.12.16-3 ii libcairo2 1.12.16-3 ii libcanberra-gtk3-0 0.30-2 ii libcanberra0 0.30-2 ii libgdk-pixbuf2.0-0 2.30.7-1 ii libgdm13.12.2-2.1 ii libglib2.0-0 2.40.0-5 ii libglib2.0-bin 2.40.0-5 ii libgtk-3-0 3.12.2-3+b1 ii libpam-modules 1.1.8-3.1 ii libpam-runtime 1.1.8-3.1 ii libpam-systemd 208-8 ii libpam0g 1.1.8-3.1 ii libpango-1.0-0 1.36.6-1 ii libpangocairo-1.0-01.36.6-1 ii librsvg2-common2.40.3-1 ii libselinux12.3-1 ii libsystemd-daemon0 208-8 ii libsystemd-id128-0 208-8 ii libsystemd-journal0208-8 ii libsystemd-login0 208-8 ii libwrap0 7.6.q-25 ii libx11-6 2:1.6.2-3 ii libxau61:1.0.8-1 ii libxdmcp6 1:1.1.1-1 ii libxrandr2 2:1.4.2-1 ii lsb-base 4.1+Debian13 ii metacity [x-window-manager]1:3.12.0-2 ii policykit-10.105-6.1 ii ucf3.0030 ii x11-common 1:7.7+7 ii x11-xserver-utils 7.7+3 ii xfce4-session [x-session-manager] 4.10.1-8 ii xfwm4 [x-window-manager] 4.10.1-2 ii xterm [x-terminal-emulator]308-1 Versions of packages gdm3 recommends: ii at-spi2-core 2.12.0-2 ii desktop-base 7.0.3 ii gnome-icon-theme 3.12.0-1 ii gnome-icon-theme-symbolic 3.12.0-1 ii x11-xkb-utils 7.7+1 ii xserver-xephyr 2:1.16.0-1 ii xserver-xorg 1:7.7+7 ii zenity 3.12.1-1.1 Versions of packages gdm3 suggests: pn gnome-orca ii libpam-gnome-keyring 3.12.2-1 -- debconf information excluded --- End Message --- --- Begin Message --- Source: cgmanager Source-Version: 0.36-1 We believe that the bug you reported is fixed in the latest version of cgmanager, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 760...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Serge Hallyn (supplier of updated cgmanager package) (This message
Bug#754850: marked as done (regression: no suspend/hibernate on non-systemd systems)
Your message dated Thu, 12 Feb 2015 17:03:34 + with message-id and subject line Bug#760281: fixed in cgmanager 0.36-1 has caused the Debian Bug report #760281, regarding regression: no suspend/hibernate on non-systemd systems to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 760281: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760281 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: upower Version: 0.99.0-3 Severity: important The newest update of upower (0.99.0-3) doesn't appear to be functional anymore. As I'm on a desktop, this means suspend and hibernate (obviously, there's no battery I could test). These functions don't even show up in XFCE's logout menu. On the other hand, pm-utils (pm-suspend from the command line) are fully functional. Unlike #718493 which is caused by interactions with logind, my system is free of any systemd components, so this is an unrelated regression. upower 0.9.23-2+b2 worked fine. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (150, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.15.3-x32 (SMP w/6 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages upower depends on: ii dbus 1.8.6-1 ii libc6 2.19-5 ii libdbus-1-31.8.6-1 ii libdbus-glib-1-2 0.102-1 ii libglib2.0-0 2.40.0-3 ii libgudev-1.0-0 204-14 ii libimobiledevice4 1.1.6+dfsg-2 ii libplist2 1.11-3 pn libpolkit-gobject-1-0 ii libupower-glib10.9.23-2+b2 ii libusb-1.0-0 2:1.0.19-1 ii pm-utils 1.4.1-15 ii udev 204-14 Versions of packages upower recommends: ii policykit-1 0.105-4 upower suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: cgmanager Source-Version: 0.36-1 We believe that the bug you reported is fixed in the latest version of cgmanager, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 760...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Serge Hallyn (supplier of updated cgmanager package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 11 Feb 2015 22:24:24 -0600 Source: cgmanager Binary: cgmanager cgmanager-tests libcgmanager0 libcgmanager-dev Architecture: source amd64 all Version: 0.36-1 Distribution: unstable Urgency: medium Maintainer: Serge Hallyn Changed-By: Serge Hallyn Description: cgmanager - Central cgroup manager daemon cgmanager-tests - Central cgroup manager daemon (tests) libcgmanager-dev - Central cgroup manager daemon (dev) libcgmanager0 - Central cgroup manager daemon (client library) Closes: 760281 767468 Changes: cgmanager (0.36-1) unstable; urgency=medium . * New upstream release. - start in a clean mounts namespace (Closes: #760281, #767468) * add *list_keys* to symbols file * pass -c4 to dh_makeshlibs to catch missing smbols in the future Checksums-Sha1: 93181f6eddce3d289978f70b5052d1e87450ef9a 2052 cgmanager_0.36-1.dsc 611f8da062bf8504df07d9ae8526d92bc227c801 428374 cgmanager_0.36.orig.tar.gz ff13af416b6ad0ab3ce31ea471fb736c9a975d4d 10600 cgmanager_0.36-1.debian.tar.xz bba9efc9473c0292c75ce676c50408731edfb9cd 78972 cgmanager_0.36-1_amd64.deb 92d2953ddcb9d70065fa27a75c85611eb3dec4de 13806 cgmanager-tests_0.36-1_all.deb ce525b80b8432e6b30ef0a9ff65f8f8c49ba9726 40898 libcgmanager0_0.36-1_amd64.deb a2aa076fbf60d25663143069dc3396fe0d4ea3d1 10890 libcgmanager-dev_0.36-1_amd64.deb Checksums-Sha256: b09a684963fe3e311924514e2d8e156fdfc38343e33ee2bd87bcf006df0e84d0 2052 cgmanager_0.36-1.dsc f4707f0130efb50ccd8a1900e7ae626c0631947528ce921a63b15ef848fb2a0d 428374 cgmanager_0.36.orig.tar.gz b38a50ee57bb945f81c233fdd2f39eb163ddcd671caf1558c2f6fd6bb47936e4 10600 cgmanager_0.36-1.debian.tar.xz fde26aaa8785efef5a9370d5039b6f6d96dfd02a7e9cde46419f59735944235b 78972 cgmanager_0.36-1_amd64.deb b8a42c3b39edc2a4a8d239b9a4243c3a2ee3a07bd02b218c613167d6e42f04b3 1
Bug#757348: marked as done (systemd: with SysV init, can no longer suspend and shutdown from lightdm)
Your message dated Thu, 12 Feb 2015 17:03:34 + with message-id and subject line Bug#760281: fixed in cgmanager 0.36-1 has caused the Debian Bug report #760281, regarding systemd: with SysV init, can no longer suspend and shutdown from lightdm to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 760281: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760281 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd Version: 208-7 Severity: important The systemd upgrade from 204-14 to 208-7 introduced a regression in lightdm: the "Suspend", "Hibernate", "Restart" and "Shut Down" menu items of lightdm are now greyed out (even before the first login). Note: I'm using SysV init. -- Package-specific info: -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-2-amd64 (SMP w/2 CPU cores) Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd depends on: ii acl 2.2.52-1 ii adduser 3.113+nmu3 ii initscripts 2.88dsf-53.3 ii libacl1 2.2.52-1 ii libaudit11:2.3.7-1 ii libblkid12.20.1-5.8 ii libc62.19-7 ii libcap2 1:2.24-4 ii libcap2-bin 1:2.24-4 ii libcryptsetup4 2:1.6.4-4 ii libdbus-1-3 1.8.6-1 ii libgcrypt11 1.5.3-5 ii libkmod2 18-1 ii liblzma5 5.1.1alpha+20120614-2 ii libpam0g 1.1.8-3 ii libselinux1 2.3-1 ii libsystemd-daemon0 208-7 ii libsystemd-journal0 208-7 ii libsystemd-login0208-7 ii libudev1 208-7 ii libwrap0 7.6.q-25 ii sysv-rc 2.88dsf-53.3 ii udev 208-7 ii util-linux 2.20.1-5.8 Versions of packages systemd recommends: ii libpam-systemd 208-7 Versions of packages systemd suggests: pn systemd-ui -- Configuration Files: /etc/systemd/logind.conf changed: [Login] HandlePowerKey=ignore -- debconf-show failed --- End Message --- --- Begin Message --- Source: cgmanager Source-Version: 0.36-1 We believe that the bug you reported is fixed in the latest version of cgmanager, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 760...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Serge Hallyn (supplier of updated cgmanager package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 11 Feb 2015 22:24:24 -0600 Source: cgmanager Binary: cgmanager cgmanager-tests libcgmanager0 libcgmanager-dev Architecture: source amd64 all Version: 0.36-1 Distribution: unstable Urgency: medium Maintainer: Serge Hallyn Changed-By: Serge Hallyn Description: cgmanager - Central cgroup manager daemon cgmanager-tests - Central cgroup manager daemon (tests) libcgmanager-dev - Central cgroup manager daemon (dev) libcgmanager0 - Central cgroup manager daemon (client library) Closes: 760281 767468 Changes: cgmanager (0.36-1) unstable; urgency=medium . * New upstream release. - start in a clean mounts namespace (Closes: #760281, #767468) * add *list_keys* to symbols file * pass -c4 to dh_makeshlibs to catch missing smbols in the future Checksums-Sha1: 93181f6eddce3d289978f70b5052d1e87450ef9a 2052 cgmanager_0.36-1.dsc 611f8da062bf8504df07d9ae8526d92bc227c801 428374 cgmanager_0.36.orig.tar.gz ff13af416b6ad0ab3ce31ea471fb736c9a975d4d 10600 cgmanager_0.36-1.debian.tar.xz bba9efc9473c0292c75ce676c50408731edfb9cd 78972 cgmanager_0.36-1_amd64.deb 92d2953ddcb9d70065fa27a75c85611eb3dec4de 13806 cgmanager-tests_0.36-1_all.deb ce525b80b8432e6b30ef0a9ff65f8f8c49ba9726 40898 libcgmanager0_0.36-1_amd64.deb a2aa076fbf60d25663143069dc3396fe0d4ea3d1 10890 libcgmanager-dev_0.36-1_amd64.deb Checksums-Sha256: b09a684963fe3e311924514e2d8e156fdfc38343e33ee2bd87bcf006df0e84d0 2052 cgmanager_0.36-1.dsc f4707f0130efb50ccd8a1900e7ae626c0631947528ce921a63b15ef848fb2a0d 428374 cgmanager_0.36.orig
Bug#758746: marked as done (kde-workspace-bin: Energy saving schemes have no effect)
Your message dated Thu, 12 Feb 2015 17:03:34 + with message-id and subject line Bug#760281: fixed in cgmanager 0.36-1 has caused the Debian Bug report #760281, regarding kde-workspace-bin: Energy saving schemes have no effect to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 760281: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760281 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: kde-workspace-bin Version: 4:4.11.11-1 Severity: normal Dear Maintainer, After recent upgrade I cannot keep laptop on while lid is closed. It goes in sleep mode regardless of energy saving settings. I use 'Lock screen' but now whenever I close the lid, system goes to sleep mode. Confirmed on two running laptops. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages kde-workspace-bin depends on: ii iso-codes 3.55-1 ii kde-runtime 4:4.13.3-1 ii kde-style-oxygen 4:4.11.11-1 ii kde-workspace-data4:4.11.11-1 ii kde-workspace-kgreet-plugins 4:4.11.11-1 ii kscreen 1.0.2.1-1 ii libc6 2.19-9 ii libcln6 1.3.3-1 ii libdbusmenu-qt2 0.9.2-1 ii libfontconfig12.11.0-6 ii libfreetype6 2.5.2-1.1 ii libgcc1 1:4.9.1-7 ii libgl1-mesa-glx [libgl1] 10.2.5-1 ii libice6 2:1.0.9-1 ii libjpeg8 8d1-1 ii libkactivities6 4:4.13.3-1 ii libkcmutils4 4:4.14.0-1 ii libkdeclarative5 4:4.14.0-1 ii libkdecore5 4:4.14.0-1 ii libkdesu5 4:4.14.0-1 ii libkdeui5 4:4.14.0-1 ii libkfile4 4:4.14.0-1 ii libkidletime4 4:4.14.0-1 ii libkio5 4:4.14.0-1 ii libknewstuff3-4 4:4.14.0-1 ii libknotifyconfig4 4:4.14.0-1 ii libkparts44:4.14.0-1 ii libkpty4 4:4.14.0-1 ii libkscreensaver5 4:4.11.11-1 ii libkworkspace4abi24:4.11.11-1 ii libnepomukcore4 4:4.13.3-1 ii libpam0g 1.1.8-3 ii libphonon44:4.7.2-1 ii libplasma34:4.14.0-1 ii libplasmagenericshell44:4.11.11-1 ii libpng12-01.2.50-2 ii libprocesscore4abi1 4:4.11.11-1 ii libprocessui4a4:4.11.11-1 ii libqalculate5 0.9.7-9 ii libqimageblitz4 1:0.0.6-4 ii libqjson0 0.8.1-3 ii libqt4-dbus 4:4.8.6+git49-gbc62005+dfsg-1 ii libqt4-declarative4:4.8.6+git49-gbc62005+dfsg-1 ii libqt4-sql4:4.8.6+git49-gbc62005+dfsg-1 ii libqt4-xml4:4.8.6+git49-gbc62005+dfsg-1 ii libqtcore44:4.8.6+git49-gbc62005+dfsg-1 ii libqtgui4 4:4.8.6+git49-gbc62005+dfsg-1 ii libsm62:1.2.2-1 ii libsolid4 4:4.14.0-1 ii libsoprano4 2.9.4+dfsg-1.1 ii libstdc++64.9.1-7 ii libstreamanalyzer00.7.8-1.2 ii libudev1 208-7 ii libusb-0.1-4 2:0.1.12-24 ii libx11-6 2:1.6.2-3 ii libxcursor1 1:1.1.14-1 ii libxext6 2:1.3.2-1 ii libxfixes31:5.0.1-2 ii libxft2 2.3.2-1 ii libxi62:1.7.4-1 ii libxinerama1 2:1.1.3-1 ii libxkbfile1 1:1.0.8-1 ii libxrandr22:1.4.2-1 ii libxrender1 1:0.9.8-1 ii libxtst6 2:1.2.2-1 ii phonon4:4.7.2-1 ii plasma-desktop4:4.11.11-1 ii qdbus 4:4.8.6+git49-gbc62005+dfsg-1 ii x11-utils 7.7+2 ii x11-xserver-utils 7.7+3 Versions of packages kde-workspace-bin recommends: pn plasma-scriptengines ii polkit-kde-1 0.99.1-1 ii upower0.99.0-3 Versions of packages kde-workspace-bin suggests: ii x11-xkb
Bug#759745: marked as done (gdm3: Unable to login post-upgrade without systemd-sysv installed)
Your message dated Thu, 12 Feb 2015 17:03:34 + with message-id and subject line Bug#760281: fixed in cgmanager 0.36-1 has caused the Debian Bug report #760281, regarding gdm3: Unable to login post-upgrade without systemd-sysv installed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 760281: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760281 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gdm3 Version: 3.12.2-2.1 Severity: grave Justification: renders package unusable Performed routine aptitude upgrade and had new version of gdm installed. Shutdown laptop and upon restart was no longer presented with the login greeter. Gnome environment would work by getting to shell and running startx but was presented with a systemd-login error on the console shell when logging in. Installed systemd-sysv which purged sysinit-core, rebooted and the system was once again usable. Suggest that there is a dependency not properly resolving in there to ensure that systemd is running as PID 1. -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gdm3 depends on: ii accountsservice 0.6.37-3 ii adduser 3.113+nmu3 ii dconf-cli0.20.0-2 ii dconf-gsettings-backend 0.20.0-2 ii debconf [debconf-2.0]1.5.53 ii gir1.2-gdm3 3.12.2-2.1 ii gnome-session [x-session-manager]3.12.1-3 ii gnome-session-bin3.12.1-3 ii gnome-session-flashback [x-session-manager] 3.8.1-1 ii gnome-settings-daemon3.12.2-1 ii gnome-shell 3.12.2-3 ii gnome-terminal [x-terminal-emulator] 3.12.3-2 ii gsettings-desktop-schemas3.12.2-1 ii libaccountsservice0 0.6.37-3 ii libatk1.0-0 2.12.0-1 ii libaudit11:2.3.7-1 ii libc62.19-9 ii libcairo-gobject21.12.16-2 ii libcairo21.12.16-2 ii libcanberra-gtk3-0 0.30-2 ii libcanberra0 0.30-2 ii libgdk-pixbuf2.0-0 2.30.7-1 ii libgdm1 3.12.2-2.1 ii libglib2.0-0 2.40.0-4 ii libglib2.0-bin 2.40.0-4 ii libgtk-3-0 3.12.2-3 ii libpam-modules 1.1.8-3.1 ii libpam-runtime 1.1.8-3.1 ii libpam-systemd 208-8 ii libpam0g 1.1.8-3.1 ii libpango-1.0-0 1.36.6-1 ii libpangocairo-1.0-0 1.36.6-1 ii librsvg2-common 2.40.3-1 ii libselinux1 2.3-1 ii libsystemd-daemon0 208-8 ii libsystemd-id128-0 208-8 ii libsystemd-journal0 208-8 ii libsystemd-login0208-8 ii libwrap0 7.6.q-25 ii libx11-6 2:1.6.2-3 ii libxau6 1:1.0.8-1 ii libxdmcp61:1.1.1-1 ii libxrandr2 2:1.4.2-1 ii lsb-base 4.1+Debian13 ii metacity [x-window-manager] 1:3.12.0-2 ii policykit-1 0.105-6.1 ii ucf 3.0030 ii x11-common 1:7.7+7 ii x11-xserver-utils7.7+3 ii xterm [x-terminal-emulator] 308-1 Versions of packages gdm3 recommends: ii at-spi2-core 2.12.0-2 ii desktop-base 7.0.3 ii gnome-icon-theme 3.12.0-1 ii gnome-icon-theme-symbolic 3.12.0-1 ii x11-xkb-utils 7.7+1 ii xserver-xephyr 2:1.16.0-1 ii xserver-xorg
Bug#777601: systemd: Loosing LXC memory cgroups after service install
Control: tag -1 -moreinfo Pierre Mavro [2015-02-12 16:11 +0100]: > I think this may not be a critical bug, however as this is the only way > (as far as I know) to know/monitor the used resources of a container, I > think it's important. Not just a cosmetical problem. Ah, ok. The patch is simple enough (well, at least for me..) so I backported it to master for jessie: http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=255ae60 We'll upload 215-12 in the next days, would be nice if you could confirm that this fixes things! Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature
Processed: Re: Bug#777601: systemd: Loosing LXC memory cgroups after service install
Processing control commands: > tag -1 -moreinfo Bug #777601 [systemd] systemd: Loosing LXC memory cgroups after service install Removed tag(s) moreinfo. -- 777601: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777601 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: [bts-link] source package src:gtk+2.0
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:gtk+2.0 > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). > # remote status report for #777142 (http://bugs.debian.org/777142) > # Bug title: patch - make gdk_event_apply_filters function safe against > changes in filter list > # * http://bugzilla.gnome.org/show_bug.cgi?id=635380 > # * remote status changed: (?) -> RESOLVED > # * remote resolution changed: (?) -> FIXED > # * closed upstream > tags 777142 + fixed-upstream Bug #777142 [src:gtk+2.0] patch - make gdk_event_apply_filters function safe against changes in filter list Added tag(s) fixed-upstream. > usertags 777142 + status-RESOLVED resolution-FIXED There were no usertags set. Usertags are now: status-RESOLVED resolution-FIXED. > thanks Stopping processing here. Please contact me if you need assistance. -- 777142: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777142 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#778238: CVE-2014-8355
Package: graphicsmagick Version: 1.3.20-3+b1 Severity: grave Tags: security Hi, the PCX bug from https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767240 also affects graphicsmagick (this is CVE-2014-8355). This was fixed upstream in http://sourceforge.net/p/graphicsmagick/code/ci/4426024497f9ed26cbadc5af5a5de55ac84796ff/ Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: user debian-secur...@lists.debian.org, usertagging 775681 ...
Processing commands for cont...@bugs.debian.org:
> user debian-secur...@lists.debian.org
Setting user to debian-secur...@lists.debian.org (was car...@debian.org).
> usertags 775681 + tracked
Usertags were: tracked.
Usertags are now: tracked.
> retitle 775681 kamailio: multiple /tmp file vulnerabilities (CVE-2015-1590
> CVE-2015-1591)
Bug #775681 {Done: Victor Seva } [kamailio]
multiple /tmp file vulnerabilities
Changed Bug title to 'kamailio: multiple /tmp file vulnerabilities
(CVE-2015-1590 CVE-2015-1591)' from 'multiple /tmp file vulnerabilities'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
775681: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775681
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#778237: FTBFS on mips
Package: openjdk-7 Version: 7u75-2.5.4-2 Severity: serious Hi, openjdk-7 fails to build from source on mips. This prevents the testing migration of the security fixes in 2.5.4: --- Error occurred during initialization of VM java.lang.ArithmeticException: / by zero at java.util.Hashtable.put(Hashtable.java:520) at java.util.Hashtable.putAll(Hashtable.java:587) at sun.misc.VM.saveAndRemoveProperties(VM.java:277) at java.lang.System.initializeSystemClass(System.java:1135) make[1]: *** [stamps/bootstrap-directory-symlink-stage2.stamp] Error 1 --- Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#775913: vala-0.26: CVE-2014-8154: Heap-buffer overflow in vala-gstreamer bindings at Gst.MapInfo()
On Wed, Jan 21, 2015 at 02:38:21PM +0100, Salvatore Bonaccorso wrote: > Source: vala-0.26 > Version: 0.26.1-1 > Severity: grave > Tags: security upstream patch fixed-upstream > Control: fixed -1 0.26.2-1 > > Hi, > > the following vulnerability was published for vala-0.26. > > CVE-2014-8154[0]: > Heap-buffer overflow in vala-gstreamer bindings at Gst.MapInfo() What's the status? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#777601: systemd: Loosing LXC memory cgroups after service install
Hi Martin, So many questions...thanks for answers ! I think this may not be a critical bug, however as this is the only way (as far as I know) to know/monitor the used resources of a container, I think it's important. Not just a cosmetical problem. To my level, it's hard to say if this issue is linked or not (https://bugzilla.redhat.com/show_bug.cgi?id=1139223). But, what I can see is, swap and memory are both options that requires to be activated from grub to work compared to others which work out of the box. This issue really looks like the same (http://lists.freedesktop.org/archives/systemd-devel/2014-September/023276.html). It may be a good idea to integrate this patch. I also tested something which may be another problem (so another ticket) but the memory and swap limitation doesn't work at all :-(...with or without this bug. I can't tell if it's linked or not. I tested cpu pinning and it works like a charm. The issue seems related to memory and swap only. Thanks Pierre Le 02/12/2015 03:43 PM, Martin Pitt a écrit : > Control: tag -1 pending > > Hello again, > > so the patch that got proposed at > > > http://lists.freedesktop.org/archives/systemd-devel/2014-September/023276.html > > actually makes a lot of sense: This makes systemd only clean up > cgroups that it created by itself, and thus won't clean up empty ones > in other controllers that LXC created. I tested this and committed > this for the experimental branch for now: > > > http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=experimental&id=286ef78fd > > I'd like to see this out in the wild for some time before applying it > to jessie, though. I'm also still interested in what the actual impact > of that is -- critical seems rather inflated? Losing empty cgroups > doesn't sound that dangerous after all, aside from the LXC warnings > when shutting down a container? > > Thanks, > > Martin -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#777601: systemd: Loosing LXC memory cgroups after service install
Processing control commands: > tag -1 pending Bug #777601 [systemd] systemd: Loosing LXC memory cgroups after service install Added tag(s) pending. -- 777601: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777601 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#777601: systemd: Loosing LXC memory cgroups after service install
Control: tag -1 pending Hello again, so the patch that got proposed at http://lists.freedesktop.org/archives/systemd-devel/2014-September/023276.html actually makes a lot of sense: This makes systemd only clean up cgroups that it created by itself, and thus won't clean up empty ones in other controllers that LXC created. I tested this and committed this for the experimental branch for now: http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=experimental&id=286ef78fd I'd like to see this out in the wild for some time before applying it to jessie, though. I'm also still interested in what the actual impact of that is -- critical seems rather inflated? Losing empty cgroups doesn't sound that dangerous after all, aside from the LXC warnings when shutting down a container? Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature
Bug#769941: libgstreamer-plugins-base1.0-0: Iceweasel crashes with "gst_app_src_set_size: assertion 'GST_IS_APP_SRC (appsrc)' failed"
Package: libgstreamer-plugins-base1.0-0 Version: 1.4.5-1 Followup-For: Bug #769941 Hello, I somehow managed to resolve this issue today, but I'm not sure how. :-) What I did was remove the deb-multimedia.org repository and remove all packages from there (and then re-install some necessary packages that got removed as a result). I assume that this is them some weird edge-case of having a mix of Debian and deb-multimedia packages installed. You are welcome to close this issue. Thanks, George -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/8 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 libgstreamer-plugins-base1.0-0 depends on: ii iso-codes 3.57-1 ii libc6 2.19-15 ii libglib2.0-0 2.42.1-1 ii libgstreamer1.0-0 1.4.4-2 ii liborc-0.4-0 1:0.4.22-1 ii multiarch-support 2.19-15 ii zlib1g 1:1.2.8.dfsg-2+b1 Versions of packages libgstreamer-plugins-base1.0-0 recommends: ii gstreamer1.0-plugins-base 1.4.5-1 Versions of packages libgstreamer-plugins-base1.0-0 suggests: pn gstreamer-codec-install | gnome-codec-install ii libvisual-0.4-plugins 0.4.0.dfsg.1-7 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#778196: Severity should be decreased from critical to grave
Dear maintainers, I was wrong when setting the severity to "critical" : i think you can change it to "grave" instead, has it only makes the package unusable. Thanks, YvanM -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#777601: systemd: Loosing LXC memory cgroups after service install
Control: notfixed -1 218-1 Control: tag -1 moreinfo Hello again, Martin Pitt [2015-02-12 13:24 +0100]: > I remember a similar problem when I worked on Ubuntu's "user LXC > container" support/patch, but this issue got fixed with 217 or 218. > Indeed I can't reproduce this report with the experimental version, > marking as fixed there; can you confirm? Sorry, I noticed that sometimes restarting a service isn't enough (sometimes it is..), one really needs to do daemon-reload *and* restart. With that I still get the issue with 218-1, so there's no upstream fix for this yet. So https://bugzilla.redhat.com/show_bug.cgi?id=1139223 might be related, but that wouldn't actually help us, will it? As nothign sets the "Delegate" flag for LXC, this is only done for nspawn. But that bug also talked about moving pids from existing cgroups (i. e. containers), which I cannot reproduce -- i. e. at least as far as I can see this is just the cleanup of empty cgroups, not modifying existing non-empty ones. Can you confirm this? Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature
Processed: Re: Bug#777601: systemd: Loosing LXC memory cgroups after service install
Processing control commands: > notfixed -1 218-1 Bug #777601 [systemd] systemd: Loosing LXC memory cgroups after service install No longer marked as fixed in versions systemd/218-1. > tag -1 moreinfo Bug #777601 [systemd] systemd: Loosing LXC memory cgroups after service install Added tag(s) moreinfo. -- 777601: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777601 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tags 777665 + patch Bug #777665 [salt-common] salt-common: salt-call needs python-msgpack to run Added tag(s) patch. > End of message, stopping processing here. Please contact me if you need assistance. -- 777665: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777665 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#777665: Simple fix attached
Tags: + patch
I've attached a patch for a direct fix.
I'm delaying applying it for 24-48 hours until I hear from upstream if
salt-common should require python-msgpack or not.
A fair bit of the code implies python-msgpack should not be needed for
local (ie salt-call) use.
Joe
diff --git a/debian/control b/debian/control
index 256af75..100f03e 100644
--- a/debian/control
+++ b/debian/control
@@ -25,6 +25,7 @@ Depends: ${python:Depends},
python-jinja2,
python-apt,
python-yaml,
+ python-msgpack,
python-pkg-resources
Recommends: lsb-release,
python-mako
Bug#777601: systemd: Loosing LXC memory cgroups after service install
Control: tag -1 confirmed Control: fixed -1 218-1 Hey Pierre, Pierre Mavro [2015-02-10 15:45 +0100]: > Let's say I've an LXC container called jessie running on jessie. The > container is started and I can see the memory is correctly visible in > the cgroup fs: > > $ ls /sys/fs/cgroup/memory/lxc/jessie/ > [...] > Then let's say I install samba (works with other services): > > $ apt-get -y install samba > > Then the cgroup fs for the container disappeared : > > $ ls /sys/fs/cgroup/memory/lxc/jessie/ > ls: cannot access /sys/fs/cgroup/memory/lxc/jessie/: No such file or > directory I can reproduce this with systemd 215 from jessie/unstable. For the record, it's not necessary to install samba, "systemctl restart haveged" worked for me too. I remember a similar problem when I worked on Ubuntu's "user LXC container" support/patch, but this issue got fixed with 217 or 218. Indeed I can't reproduce this report with the experimental version, marking as fixed there; can you confirm? How much of an actual issue is that in practice? At least for me reloading a service only triggers the cleanup of empty cgroups. Indeed LXC creates the cgroups in all controllers, but only actually puts the processes in the container in some of them (e. g. perf_event and freezer, but not devices and memory), and those which are non-empty stay alive for me. So isn't that just a rather cosmetical problem at this point? Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature
Processed: Re: Bug#777601: systemd: Loosing LXC memory cgroups after service install
Processing control commands: > tag -1 confirmed Bug #777601 [systemd] systemd: Loosing LXC memory cgroups after service install Added tag(s) confirmed. > fixed -1 218-1 Bug #777601 [systemd] systemd: Loosing LXC memory cgroups after service install Marked as fixed in versions systemd/218-1. -- 777601: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777601 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#778196: Fails to built with current Jessie's kernel
Package: openafs-modules-dkms Version: 1.6.9-2 Severity: critical Dear maintainers, openafs-modules-dkms can not compile with linux-headers-3.16.0-4-amd64 version 3.16.7-ckt4-3. With the previous Jessies's kernel (version 3.16.7-ckt2-1) there was no problem. Here is the message when trying to "dpkg-reconfigure openafs-modules-dkms": Uninstall Beginning Module: openafs Version: 1.6.9 Kernel: 3.16.0-4-amd64 (x86_64) - Status: Before uninstall, this module version was ACTIVE on this kernel. openafs.ko: - Uninstallation - Deleting from: /lib/modules/3.16.0-4-amd64/updates/dkms/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. depmod DKMS: uninstall completed. -- Deleting module version: 1.6.9 completely from the DKMS tree. -- Done. Loading new openafs-1.6.9 DKMS files... Building only for 3.16.0-4-amd64 Building initial module for 3.16.0-4-amd64 Error! Bad return status for module build on kernel: 3.16.0-4-amd64 (x86_64) Consult /var/lib/dkms/openafs/1.6.9/build/make.log for more information. The make.log file mentionned above is attached. Thanks for your time and work, Yvan Masson DKMS make.log for openafs-1.6.9 for kernel 3.16.0-4-amd64 (x86_64) jeudi 12 février 2015, 12:47:46 (UTC+0100) checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes /var/lib/dkms/openafs/1.6.9/build/build-tools/missing: Unknown `--is-lightweight' option Try `/var/lib/dkms/openafs/1.6.9/build/build-tools/missing --help' for more information configure: WARNING: 'missing' script is too old or missing checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether make supports nested variables... yes checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking whether gcc understands -c and -o together... yes checking for style of include used by make... GNU checking dependency style of gcc... none checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for flex... no checking for lex... no checking for pkg-config... no checking for libxslt... no checking for saxon... no checking for xalan-j... no checking for xsltproc... no checking for docbook2pdf... no checking for dblatex... no checking for library containing strerror... none required checking for pid_t... yes checking for size_t... yes checking whether ln -s works... yes checking for ranlib... ranlib checking for bison... no checking for byacc... no checking if lex is flex... no checking whether byte order is known at compile time... yes checking whether byte ordering is bigendian... no checking whether printf understands the %z length modifier... yes checking your OS... linux checking if gcc accepts -march=pentium... no checking if gcc needs -fno-strength-reduce... yes checking if gcc needs -fno-strict-aliasing... yes checking if gcc supports -fno-common... yes checking if gcc supports -pipe... yes checking if linux kbuild requires EXTRA_CFLAGS... yes checking for linux kernel module build works... yes checking for linux/config.h... no checking for linux/completion.h... yes checking for linux/exportfs.h... yes checking for linux/freezer.h... yes checking for linux/key-type.h... yes checking for linux/semaphore.h... yes checking for linux/seq_file.h... yes checking for struct vfs_path... no checking for kuid_t... yes checking for write_begin in struct address_space_operations... yes checking for name in struct backing_dev_info... yes checking for session_keyring in struct cred... yes checking for ctl_name in struct ctl_table... no checking for d_automount in struct dentry_operations... yes checking for i_alloc_sem in struct inode... no checking for i_blkbits in struct inode... yes checking for i_blksize in struct inode... no checking for i_mutex in struct inode... yes checking for i_security in struct inode... yes checking for flock in struct file_operations...
Bug#776345: marked as done (dleyna-server: Segfault when playing video)
Your message dated Thu, 12 Feb 2015 11:40:07 +0100 with message-id <1423737607.7670.3.ca...@collabora.com> and subject line Re: Bug#776345: Close this has caused the Debian Bug report #776345, regarding dleyna-server: Segfault when playing video to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 776345: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776345 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: dleyna-server Version: 0.4.0-1 Severity: critical Justification: breaks unrelated software Dear Maintainer, * What led up to the situation? Sporadically, when watching video, typically using Totem. Any video. This did not happen until about a month ago (on testing, keeping up to date) * What exactly did you do (or not do) that was effective (or ineffective)? Typically, the system had been running fine for a while, and then I would turn on a video, and within the first couple of minutes of this video running, the following happened. * What was the outcome of this action? There was a segfault in the dleyna-server, and my gnome-shell logged me out and closed all the windows I had open * What outcome did you expect instead? I would expect the video to keep playing, and all of my windows to still be open. The dmesg output describing the segfault is provided below. Please advise as to how I can give you more information on this issue. [49339.327487] dleyna-server-s[26235]: segfault at 8 ip 7ff711375132 sp 7fffacb1bb20 error 4 in libdleyna-server-1.0.so.1.0.3[7ff711365000+21000] -- System Information: Debian Release: 8.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages dleyna-server depends on: ii libc6 2.19-13 ii libdleyna-connector-dbus-1.0-1 0.2.0-1 ii libdleyna-core-1.0-30.4.0-1 ii libglib2.0-02.42.1-1 ii libgssdp-1.0-3 0.14.10-1 ii libgupnp-1.0-4 0.20.12-1 ii libgupnp-av-1.0-2 0.12.6-1 ii libgupnp-dlna-2.0-3 0.10.2-1 ii libsoup2.4-12.48.0-1 dleyna-server recommends no packages. dleyna-server suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Weird indeed, but you're right, no point in keeping this open if you cannot reproduce it anymore. Feel free to re-open if you get more data about the issue.--- End Message ---
Bug#777741: marked as done (wss4j: CVE-2015-0226 CVE-2015-0227)
Your message dated Thu, 12 Feb 2015 09:23:40 + with message-id and subject line Bug#41: fixed in wss4j 1.6.15-2 has caused the Debian Bug report #41, regarding wss4j: CVE-2015-0226 CVE-2015-0227 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 41: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=41 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wss4j Severity: grave Tags: security Justification: user security hole Hi, please see https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2015-0226 https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2015-0227 Cheers, Moritz --- End Message --- --- Begin Message --- Source: wss4j Source-Version: 1.6.15-2 We believe that the bug you reported is fixed in the latest version of wss4j, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 777...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Bourg (supplier of updated wss4j package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 12 Feb 2015 09:11:29 +0100 Source: wss4j Binary: libwss4j-java Architecture: source all Version: 1.6.15-2 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Emmanuel Bourg Description: libwss4j-java - Apache WSS4J WS-Security implementation Closes: 41 Changes: wss4j (1.6.15-2) unstable; urgency=medium . * Fixed security issues (Closes: #41): - CVE-2015-0227: WSS4J is still vulnerable to Bleichenbacher's attack (incomplete fix for CVE-2011-2487) - CVE-2015-0226: WSS4J doesn't correctly enforce the requireSignedEncryptedDataElements property * Standards-Version updated to 3.9.6 (no changes) Checksums-Sha1: 1919d3cd5bf05dba2796069d251f0bd5b7e95b9a 2124 wss4j_1.6.15-2.dsc 6461136db69ddd7e46064fdd750e1c7823ab5fed 9548 wss4j_1.6.15-2.debian.tar.xz cbaf5c5cb4ab1f8015a2912c7791aa0cb5da9cca 342064 libwss4j-java_1.6.15-2_all.deb Checksums-Sha256: c8a93f439e8c2abd7c95ec246906ee0b00f7fc0c390e3565d9fe66606d782eae 2124 wss4j_1.6.15-2.dsc afa2ec0e05322657fe15544fdbea842fccc32f3195b97b2e77566202a513983d 9548 wss4j_1.6.15-2.debian.tar.xz 9c89700350af318e28122623408b8108a923f21edf16dd76cf05bce2bc9e1584 342064 libwss4j-java_1.6.15-2_all.deb Files: fd08438daabc8ebdc12855052c47f2d5 2124 java optional wss4j_1.6.15-2.dsc bda8c06272cb1f22413e8a55619e0901 9548 java optional wss4j_1.6.15-2.debian.tar.xz 82181395bd8f9f68e3a3157c0bb6f81f 342064 java optional libwss4j-java_1.6.15-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJU3GrgAAoJEPUTxBnkudCssR8QAISJdMUJjehMXcPjaVaAaAr1 HhHyq6BWoko1xgER1rxo53uVLFTbHFFv3DZea6Mi8j5XihWwXsBiofcyc6hWFl51 ZU2zLuU5oImy+oCZ5AcD1Ej1z4rLJNiDNMr4aBwl271CehULRbVREcVJfHdxeoWS Ra29TXcjUV7M6cnGWaXHOFS8/Y6RGrSFY9FH2zgt8Rs4ubsnnxWQTcXyUNJE/iM0 AjNcgiixv/v2fnT1Fjvj5TTJdSzxsErQ3AlfGWlpBW1MAfPTIKPNmEceQF851ois NktPLPEHMf1yD7a6NjClkOkf0ucF01IDg8tIkQ2I2GlQe7jtvWzLEkkdp/6qxy34 UsrEJQdPMJe+aDW/3Bln2RjnmnM38bl65/TjYhBQ2KSZj+Z6hbZk7KVvLY6ExUEk 9gU1NK8GmWoHLZwduCwfbVxKi2iCsroBj1eSSX0X2JPllsxwFRxUcYynAQoXfrsn NR6sopazpPiV1qTSw4fsUfrcIERRgEw1+1n79UEVPyawsvfVkBd6fVFeStxMnf2y VsKe/az6CJFunbXekz3nGJ+Qv+xPHpGffCRwvncdoKgjqHz9wTna/K9ktDs0pLUg N2D1oU7lq6zvek5JGRX4fk7LySda5hmwj6pshM4LmTJi5lzvbIhZ7sFEtYRMLrag 3ASaDBGKaZenmQnXI8Jl =BAPI -END PGP SIGNATURE End Message ---
Processed: tagging 777741
Processing commands for cont...@bugs.debian.org: > tags 41 + pending Bug #41 [wss4j] wss4j: CVE-2015-0226 CVE-2015-0227 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 41: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=41 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
