Bug#781724: ggobi: Conflicting declaration/definition of barchartRulerRangesSet
Package: ggobi
Version: 2.1.11-1
Usertags: goto-cc
Tags: patch
Severity: minor
During an analysis of all Debian packages using our research compiler tool-chain
(using tools from the cbmc package) the following error was found:
The definition of barchartRulerRangesSet does not match its declaration at
http://sources.debian.net/src/ggobi/2.1.11-1/src/barchartClass.c/?hl=61#L61
The attached patch fixes this problem.
Best,
Michael
diff -urN a/src/barchart.c b/src/barchart.c
--- a/src/barchart.c2015-04-02 00:10:25.0 +0100
+++ b/src/barchart.c2015-04-02 00:11:55.0 +0100
@@ -1639,6 +1639,10 @@
}
void
-barchartRulerRangesSet ( ) {
+barchartRulerRangesSet (gboolean a, displayd * b, splotd * c, ggobid * d) {
// Do nothing!
+ (void)a;
+ (void)b;
+ (void)c;
+ (void)d;
}
pgpDO6jc8Dh1M.pgp
Description: PGP signature
Bug#781622: RFS: opentyrian/2.1.20130907-1 [ITP]
On Thu, 2 Apr 2015 09:05:50 Etienne Millon wrote: Nice. But I meant to use all those headers (except for Applied-Upstream which I use ocassionally). Oh, I see. I added them. Thanks. Thanks for the heads-up on the new way of repacking. Files-Excluded makes it real easy indeed. If you ever need more advanced repacking (e.g. not just removing files but changing something in the archive) or generating orig.tag from checkout there is a wiki page with samples of how to do that: https://wiki.debian.org/onlyjob/get-orig-source Done, repushed, reuploaded! Awesome, I'll have a look soon. Thanks. -- Best wishes, Dmitry Smirnov. --- Continuous effort - not strength or intelligence - is the key to unlocking our potential. -- Winston Churchill signature.asc Description: This is a digitally signed message part.
Bug#781607: [Pkg-freeipa-devel] Bug#781607: Bug#781607: Bug#781607: freeipa: please package new upstream version
On 02.04.2015 08:44, Timo Aaltonen wrote: On 01.04.2015 13:06, Holger Levsen wrote: control: block -1 by 780354 Hi Timo, On Dienstag, 31. März 2015, Timo Aaltonen wrote: It needs at least bind 9.10 or up and softhsm 2.0.0b2 (see bug #780354). Could be others too, didn't really bother checking further. Thanks for the info! bind 9.10 is in experimental but softhsm 2.0.0b2 aint available yet. actually it needs bind 9.10.1 or newer, experimental has rc2 from a ~year ago. I got a suggestion to pull a patch from Centos, which disables DNSSEC support.. that should let us move forward with 4.1 sooner. -- t -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781725: live-tools: causes dmsetup to fail to upgrade from 'wheezy': /usr/sbin/update-initramfs.orig.initramfs-tools - command not found
Package: live-tools Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: piuparts Control: block -1 with 778828 Hi, during a test with piuparts I noticed your package causes another package to fail to install during the upgrade from 'wheezy'. live-tools installed fine in 'wheezy' (dmsetup was not installed), then the upgrade to 'jessie' fails (which requires installation of dmsetup). From the attached log (scroll to the bottom...): [...] Selecting previously unselected package dmsetup. Preparing to unpack .../dmsetup_2%3a1.02.90-2.1_amd64.deb ... Unpacking dmsetup (2:1.02.90-2.1) ... Setting up libdevmapper1.02.1:amd64 (2:1.02.90-2.1) ... Setting up dmsetup (2:1.02.90-2.1) ... E: /usr/sbin/update-initramfs.orig.initramfs-tools - command not found E: On Debian based systems, update-initramfs from initramfs-tools E: can be installed with: E: apt-get install initramfs-tools dpkg: error processing package dmsetup (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for libc-bin (2.19-15) ... Errors were encountered while processing: dmsetup The wheezy version of live-tools is buggy (#779888), this has been fixed in jessie, but that is not sufficient to fix the upgrade paths from wheezy to jessie. AIUI live-tools/wheezy diverts update-initramfs and replaces it by its own implementation that is broken due to lack of Depends: initramfs-tools (or even a Recommends). The solution to this problem would be to add Breaks: live-tools ( 4.0.1-1) to dmsetup to fix the unpacking order and get rid of the broken live-tools before configuring dmsetup, but that has been rejected by the lvm2 maintainer (#778828). Note that removing live-tools from jessie won't solve this upgrade issue. cheers, Andreas live-tools_4.0.2-1.1.log.gz Description: application/gzip
Bug#781518: Please remove very outdated MakeHuman package
Dear all, On Wed, Apr 1, 2015 at 11:33 PM, Manuel A. Fernandez Montecelo manuel.montez...@gmail.com wrote: Oh, one final thing that I forgot, sorry for the noise. If Muammar is OK with it and does not have much time in the near future to maintain the package himself, perhaps you can contact people from pkg-multimedia (the maintainers of Blender) or similar teams in Debian -- maybe they would like to have Makehuman under their umbrella and will help you with the task. That also sounds as a good solution to avoid NEW queue. I am almost certain there will be people interested in pkg-multimedia to take care of MH. I understand upstream's concerns about the ancient version currently available in Debian. If Joel wants, he can proceed to request RM from the archives but then the package has to go again in NEW queue. I apologize for all troubles caused. Regards, -- Muammar El Khatib. Linux user: 403107. GPG Key = 71246E4A. http://muammar.me | http://proyectociencia.org ,''`. : :' : `. `' `- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781723: ruby-libxml: Package description mentions unexistant benchmark below
Package: ruby-libxml Severity: minor Hi, the end of the package description now reads: «... if speed is your need, these are good libraries to consider, as demonstrated by the informal benchmark below.» But there is nothing else after that and no benchmark. I think you should remove the word below and maybe change the last part to ..demonstrated by an informal benchmark. Thanks, Beatrice -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#738569: gpointing-device-settings: package works here on several machines
Package: gpointing-device-settings Followup-For: Bug #738569 Control: severity -1 normal Hello, lowering severity to normal since I'm using this package on several unrelated machines (lenovo thinkpads T520 and T420) here without any segfault. Probably the segfault is related to your specific configuration or hardware. This is still a bug, but not such a high severity. When I strace it, I do get lots of EAGAIN on fd=3, but only when the pointer is moving on gpointing-devices-settings' window. It doesn't stop the package from working, and I have never had any segfault. This package is usefull, I don't think it should be removed because it segfaults on only one computer (until now). Thanks, -- Rémi -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gpointing-device-settings depends on: ii gconf2 3.2.6-3 ii libatk1.0-0 2.14.0-1 ii libc6 2.19-17 ii libcairo2 1.14.0-2.1 ii libdbus-1-3 1.8.16-1 ii libdbus-glib-1-20.102-1 ii libfontconfig1 2.11.0-6.3 ii libfreetype62.5.2-4 ii libgconf2-4 3.2.6-3 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglib2.0-02.42.1-1 ii libgpds01.5.1-6 ii libgtk2.0-0 2.24.25-3 ii libpango1.0-0 1.36.8-3 ii libxi6 2:1.7.4-1+b2 gpointing-device-settings recommends no packages. gpointing-device-settings suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#748142: Symmetrica: Missing parameter to cause stack underflow
Control: reopen 748142 Hi Jerome, My sincere apologies for getting back to you more than 6 months late. On 13 Sep 2014 14:10:04 +, Jerome Benoit wrote: [...] To be frank, I am confused by your bugreport. I'm really sorry for that! Hopefully that can be cleared up now. Actually there is two definition of CE2 in `macro.h': one is commented, the second one is not. Yes. I suspect that in fact you deal with the commented one, No, that shouldn't be the case. what I can hardly believe but on the other hand your description do not seem to readily fit with the uncommented version. Please can you confirm ? May I wipe the commented version to avoid confusion of the script ? [...] I'm afraid that doesn't solve the problem. It's really that CE2 cannot be used with the function first. Consider its declaration: INT first(kind,res,para_eins) OBJECTKIND kind; OP res,para_eins; (from here: http://sources.debian.net/src/symmetrica/2.0%2Bds-3/rest.c/#L3411) So first takes as first argument an OBJECTKIND, and then two OPs. CE2, however, will eventually do this: erg += (*f)(checkequal2_c,b);\ (from here: http://sources.debian.net/src/symmetrica/2.0%2Bds-3/macro.h/?hl=819#L1835) That is, it invokes f with 2 arguments. As f will be first, that function will now be invoked with only 2 arguments (of type OP), missing the first one (of type OBJECTKIND). Consequently: - The first argument will be of inappropriate type - The third argument will be missing Hope this helps to clarify, Michael pgpgff5xKfPvo.pgp Description: PGP signature
Bug#777264: Could not connect to ftp.tw.debian.org:80 (140.112.8.139). - connect (110: Connection timed out)
Is there any Debian Developers here can handle this issue or say something? It's been a long time ... Thanks.
Bug#781730: systemd: Instance variable %i not available for ReadWriteDirectories
Package: systemd Version: 215-12 Severity: normal Tags: upstream Hi, this also affects experimental (219-5) We're trying to run multiple DHCP processes on one system. They have their data in a instance-specific configuration directory and we'd like to limit (r/w for now) filesystem access to that directory for security reasons. == dhcpd@.service == [Unit] Description=DHCP Instance %i After=syslog.target After=network.target [Service] ExecStart=/usr/sbin/dhcpd -cf /var/lib/dhcp/%i/etc/dhcpd.conf -lf /var/lib/dhcp/%i/db/dhcpd.leases -pf /var/lib/dhcp/%i/dhcpd.pid -f Type=simple Restart=on-failure CapabilityBoundingSet=CAP_NET_RAW CAP_NET_BIND_SERVICE NoNewPrivileges=true ReadOnlyDirectories=/ ReadWriteDirectories=/var/lib/dhcp/%i This does not work Apr 02 11:02:38 dns-w-neu systemd[1]: Started DHCP Instance b1peer2. Apr 02 11:02:38 dns-w-neu systemd[1]: Starting DHCP Instance b1peer2... Apr 02 11:02:38 dns-w-neu systemd[7760]: Failed at step NAMESPACE spawning /usr/sbin/dhcpd: No such file or directory Apr 02 11:02:38 dns-w-neu systemd[1]: dhcpd@b1peer2.service: main process exited, code=exited, status=226/NAMESPACE Apr 02 11:02:38 dns-w-neu systemd[1]: Unit dhcpd@b1peer2.service entered failed state. Apr 02 11:02:38 dns-w-neu systemd[1]: dhcpd@b1peer2.service failed. Apr 02 11:02:38 dns-w-neu systemd[1]: dhcpd@b1peer2.service holdoff time over, scheduling restart. The directory exists root@dns-w-neu:/var/lib/dhcp# ls -lad b1peer2 drwxr-xr-x 4 root root 4096 Apr 1 16:40 b1peer2 it works fine with either ReadWriteDirectories=/var/lib/dhcp and ReadWriteDirectories=/var/lib/dhcp/b1peer2 (which obviously won't work with other instances, but that's not the point here). So it seems that %i is not evaluated in ReadWriteDirectories (at least). Bernhard -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781729: Link Luajit binary dynamically
Package: luajit-5.1-2 Version: 2.0.3+dfsg-3 Since you're providing libluajit, can you link the luajit binary against the libluajit shared library? --- a/src/Makefile +++ b/src/Makefile @@ -679,7 +679,7 @@ $(LUAJIT_T): $(TARGET_O) $(LUAJIT_O) $(TARGET_DEP) $(E) LINK $@ -$(Q)$(TARGET_LD) $(TARGET_ALDFLAGS) -o $@ $(LUAJIT_O) $(TARGET_O) $(TARGET_ALIBS) +$(Q)$(TARGET_LD) $(TARGET_ALDFLAGS) -I. -I./src -I/usr/include -lm -ldl -o $@ $(LUAJIT_O) $(LUAJIT_SO) $(Q)$(TARGET_STRIP) $@ $(E) OKSuccessfully built LuaJIT -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781732: unbound: interface-automatic broken with asymmetric routing
Source: unbound
Version: 1.4.17-3+deb7u2
Severity: normal
Tags: upstream
Dear Maintainer,
Unbound's current implementation of interface-automatic always forces an
exit interface for the reply datagrams, causing reply packets to be
dropped on multi-homed systems in the presence of asymmetric routing. We were
affected by this running unbound on a router with multiple interfaces in
a meshed network.
Long explanation follows:
To provide single-socket UDP multihoming, unbound uses the ancilary
IP_PKTINFO data received during recvmsg(2) and passes it as-is
(including ipi_ifindex) to sendmsg(2). The in_pktinfo structure contains
the following members:
struct in_pktinfo {
unsigned int ipi_ifindex; /* Interface index */
struct in_addr ipi_spec_dst; /* Local address */
struct in_addr ipi_addr; /* Header Destination
address */
};
At recvmsg(2) time ipi_ifindex contains the ifindex of the interface the packet
arrived on, while ipi_spec_dst contains the local interface address the packet
matched. Regarding sendmsg(2), man 7 ip states:
If IP_PKTINFO is passed to sendmsg(2) and ipi_spec_dst is not
zero, then it is used as the local source address for the routing table
lookup and for setting up IP source route options. When ipi_ifindex is
not zero, the primary local address of the interface specified by
the index overwrites ipi_spec_dst for the routing table lookup.
So it appears as if passing ipi_ifindex should only affect cases where source
routing is performed. However, the actual Linux kernel implementation
(as of 4.0-rc6) states the following (__ip_route_output_key() in
net/ipv4/route.c):
if (fib_lookup(net, fl4, res)) {
res.fi = NULL;
res.table = NULL;
if (fl4-flowi4_oif) {
/* Apparently, routing tables are wrong. Assume,
that the destination is on link.
WHY? DW.
Because we are allowed to send to iface
even if it has NO routes and NO assigned
addresses. When oif is specified, routing
tables are looked up with only one purpose:
to catch if destination is gatewayed, rather than
direct. Moreover, if MSG_DONTROUTE is set,
we send packet, ignoring both routing tables
and ifaddr state. --ANK
We could make it even if oif is unknown,
likely IPv6, but we do not.
*/
if (fl4-saddr == 0)
fl4-saddr = inet_select_addr(dev_out, 0,
RT_SCOPE_LINK);
res.type = RTN_UNICAST;
goto make_route;
}
What this basically does is that ipi_ifindex will override any routing
table decision and force the packet out of that very interface.
Furthermore, if there is no routing table entry for the destination via
that interface, the destination will be assumed to be on-link and will
not be routed via a gateway. Note that no error will be returned to
userspace and if the destination does not respond to an ARP request on
that very link, the packet will be silently dropped.
So, for unbound this means that reply packets on interface-automatic
sockets will always attempt to leave the system from the same
(physical/logical) interface the query came in. This is fine for a
single-homed server, however when running on multi-homed systems (e.g.
on a router with multiple interfaces on a meshed network) there will be
cases of asymmetric routing where the return route to the client goes
through a different interface than the one the query came in and
unbound's replies to not directly connected clients will be silently
dropped.
Since using the correct source address is all that interface-automatic
is about, we should really pass an ipi_ifindex set to 0 to sendmsg(2)
and let the system's routing tables decide the actual interface that
should be used to send the reply, while still retaining the correct
source address in ipi_spec_dst.
The attached patch fixes this.
Regards,
Apollon
--System Information:
Debian Release: 8.0
APT prefers testing
APT policy: (500, 'testing'), (90, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=el_GR.UTF-8, LC_CTYPE=el_GR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
From 588448143170de218fa68fdd01cbbad4d7a2179c Mon Sep 17 00:00:00 2001
From: Apollon Oikonomopoulos apoi...@debian.org
Date: Wed, 1 Apr 2015 16:36:50 +0300
Subject: [PATCH] Fix interface-automatic on multihomed systems
To provide single-socket UDP multihoming, unbound uses the ancilary
Bug#781733: zoneminder: Install fails with Failed to start LSB: Control ZoneMinder as a Service.
Package: zoneminder Version: 1.28.1 Severity: important Dear Maintainer, I tried to install but the install fails with: sudo systemctl -l status zoneminder.service [sudo] password for rbees: ● zoneminder.service - LSB: Control ZoneMinder as a Service Loaded: loaded (/etc/init.d/zoneminder) Active: failed (Result: timeout) since Wed 2015-04-01 18:56:10 EDT; 10h ago Process: 3836 ExecStart=/etc/init.d/zoneminder start (code=killed, signal=TERM) Apr 01 18:51:25 sweatbee zmpkg[3840]: INF [Command: start] Apr 01 18:51:26 sweatbee pkexec[3847]: pam_unix(polkit-1:session): session opened for user root by (uid=0) Apr 01 18:56:10 sweatbee systemd[1]: zoneminder.service start operation timed out. Terminating. Apr 01 18:56:10 sweatbee systemd[1]: Failed to start LSB: Control ZoneMinder as a Service. Apr 01 18:56:10 sweatbee zoneminder[3836]: Starting ZoneMinder: Job for zoneminder.service failed. See 'systemctl status zoneminder.service' and 'journalctl -xn' for details. Apr 01 18:56:10 sweatbee systemd[1]: Unit zoneminder.service entered failed state. Zoneminder does partically run in that I am able to get the web page but it is not useable. The dialog boxes don't pop up. I have tried the instructions here: http://www.zoneminder.com/wiki/index.php/Ubuntu_Server_14.04_64-bit_with_Zoneminder_1.26.5_the_easy_way and here: http://www.sourcetrunk.com/zoneminder/ with no joy Thanks -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781633: [Pkg-freeipmi-devel] Bug#781633: /usr/sbin/ipmiconsole: repeated text in man page
forwarded 781633 http://savannah.gnu.org/bugs/?44698 thanks ja...@crackle.treshna.com writes: the section KNOWN ISSUES in the ipmiconsole man page partially occurs twice. (search for the string KNOWN ISSUES ) I reported this upstream, they'll probably fix this eventually. http://savannah.gnu.org/bugs/?44698 -- Thanks, Feri. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781632: [Pkg-freeipmi-devel] Bug#781632: /usr/sbin/ipmiconsole: path wrong?
ja...@crackle.treshna.com writes: ipmiconsole installis in /usr/sbin but it does not require root permissions to use (possible work-arounds for this are obvious) but this seems sub-optiomal I'm not sure it's worth deviating from the upstream installation practice (and manpage section), given that a symlink in /usr/local/bin looks like a sufficient workaround. Maybe open an issue upstream? -- Thanks, Feri. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781721: python-scour: upstream now at Github; version 0.30
Package: python-scour Version: 0.26-3 Severity: wishlist Scour is now being developed at Github and has had a few more releases since 0.26. See https://github.com/oberstet/scour -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (102, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.19.3 (SMP w/4 CPU cores; PREEMPT) 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 python-scour depends on: ii python 2.7.9-1 ii python2.7 2.7.9-2 python-scour recommends no packages. Versions of packages python-scour suggests: ii python-cairo 1.8.8-1+b2 pn python-rsvg none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781414: Embedded code copies
Hi Gunnar, and PHP PEAR Maintainers, On Wed, Apr 01, 2015 at 10:52:54PM -0600, Gunnar Wolf wrote: Sorry for the lateness - I'm currently devoid of free time, and my package maintainance status has suffered :( It’s not even been a week since that bug was filed, so no need to apologize (and yay, double happy event may drag one into other activities, cheers! ;). - For php-seclib, after a quick diff, the version I currently have in Sid (0.3.8-1) seems clearly newer [...] In your experience, how incompatible would you expect a new version to be? Do you think I could just drop in the new one and not suffer too much? I’ve introduced php-seclib in the archive to get rid of the embedded code copy from ownCloud, and must admit I’ve never notice any BC break: I’m happy to track the latest php-seclib upstream release for almost two years now, it seems to behave correctly ;). - As for php-htmlpurifier, it seems we are lucky as both packages carry 4.6.0. That’s a relief (#764885 would have applied otherwise). However, the one in Collabtive is a standalone file, stating in its header: * This file was auto-generated by generate-includes.php and includes all of * the core files required by HTML Purifier. Use this if performance is a * primary concern and you are using an opcode cache. PLEASE DO NOT EDIT THIS * FILE, changes will be overwritten the next time the script is run. So... Do you know what'd be the best way for this file to be replaced (or generated) from the package we are shipping? Simply requiring 'HTMLPurifier.autoload.php' (or 'HTMLPurifier.includes.php', or 'HTMLPurifier.safe-includes.php', or…) instead of the standalone file should do the trick. Feel free to bug php-htmlpurifier if you really want it to provide a big standalone file, but I’m not sure that’s necessary (nor a good idea at first sight). Please, note I only team-uploaded this package once, so I may not be the best person to provide more insight. It looks like most existing PHP classes used as dependencies are currently symlinked. You may consider including them from where they belong instead. I prefered symlinking as it requires less patching of the upstream code. But, of course, if the PHP packaging group's best practices are to patch, I will do so. Just please confirm! I’m a bit new in the PHP PEAR Maintainers team, other members may provide more insight here. My short experience with ownCloud packaging is that previous maintainers did it that way, and it looks a lot less hackish. E.g., if a file is added in an updated PHP class, as long as that file is not (yet) symlinked from the webapp using it, you may shoot yourself in the foot if this file is called from an existing one… Regards David signature.asc Description: Digital signature
Bug#781652: python3-llfuse-dbg: fails to upgrade from 'testing' - trying to overwrite /usr/lib/python3/dist-packages/llfuse/capi.cpython-34dm-x86_64-linux-gnu.so
On 2015-04-02 05:03, Nikolaus Rath wrote: I think the way to fix this is to add a Conflicts: (rather than Breaks: + Replaces:) on the old version, because the -dbg package does not replace the non-dbg package. Right? No. Replaces is usually used for taking over files from another package, not for replacing some more abstract functionality¹. Versioned Breaks+Replaces are used for moving files between packages. (Conflicts+Replaces would work as well, but make the job harder for apt to find a valid upgrade path). Conflicts without Replaces won't work (in most cases). The version should be ( first-version-that-put-the-file-in-the-right-package) Andreas ¹ unversioned Conflicts+Replaces+Provides are used on virtual packages, to have a unique provider of some functionality, but that is not what you need here -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776192: Linux null-pointer deref in 3.16.7-ctk2-1 (was: Bug#776192: upgrade-reports wheezy to jessie boot problem)
--On Sunday, January 25, 2015 11:25:34 AM +0100 Niels Thykier ni...@thykier.net wrote: I have CC'ed the Debian linux maintainers as I noticed your kernel reports a null pointer deference in the kernel (see below for the trace). I have taken the liberty of reassigning it to the linux package as well. @linux maintainers: if you suspect that the null pointer issue is unrelated to Bills boot problem, please clone the bug and throw the bug back to upgrade-reports for further analysis. Bug link: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776192 Thanks, ~Niels Any news on this problem? I am still seeing this problem even though we have moved on to 3.16.7-ckt7-1. I had the thought to look at the kernel modules that support the PERC controller on these Dell systems. Explicitly specifying the mpt* modules and updating initramfs does not fix the problem. We have plenty of these 1950s. I really need to come up with a work around or a solution to this problem. Any ideas about what I should try next? Bill -- Bill MacAllister Systems Programmer, Stanford University -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781726: how to solve the live-tools upgrade issue? (#781725)
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Hi, live-tools/wheezy is buggy, causing install/upgrade failures in other packages (wheezy: #779888, upgrade: #781725). The underlying dependency issue has been fixed in jessie long ago, but that is not sufficient to get a working upgrade ordering without adding Breaks against the buggy wheezy version somewhere: Selecting previously unselected package dmsetup. Preparing to unpack .../dmsetup_2%3a1.02.90-2.1_amd64.deb ... Unpacking dmsetup (2:1.02.90-2.1) ... Setting up libdevmapper1.02.1:amd64 (2:1.02.90-2.1) ... Setting up dmsetup (2:1.02.90-2.1) ... E: /usr/sbin/update-initramfs.orig.initramfs-tools - command not found E: On Debian based systems, update-initramfs from initramfs-tools E: can be installed with: E: apt-get install initramfs-tools dpkg: error processing package dmsetup (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for libc-bin (2.19-15) ... Errors were encountered while processing: dmsetup This happened because live-tools/jessie has not yet been unpacked and instead the buggy replacement update-initramfs from live-tools/wheezy gets used. dmsetup is not required in a wheezy installation of live-tools, but gets pulled in during the upgrade to jessie. This could be fixed (I verified this by building a patched lvm2 and using it in a piuparts test) by adding Breaks: Breaks: live-tools ( 4.0.1-1) to dmsetup to change the unpacking order and get rid of the broken live-tools before configuring dmsetup, but that has been rejected by the lvm2 maintainer (#778828). Note that removing live-tools from jessie won't solve this upgrade issue. Andreas, who is neither maintainer nor user of live-tools and cares solely about the upgrade issue discovered by piuparts -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781728: Lua 5.2 compat
Package: luajit-5.1-2 Version: 2.0.3+dfsg-3 Some programs like Aegisub require luajit to be compiled with Lua 5.2 compatibility. The resulting library however is not 100% compatible with the regular Luajit build. Can't you instead just build two libraries, libluajit-5.1.so.2 and libluajit-5.1-lua52compat.so.2? To build libluajit-5.1.so.2: $(MAKE) amalg PREFIX=/usr CC=gcc MULTILIB=lib/$(DEB_HOST_MULTIARCH) To build libluajit-5.1-lua52compat.so.2: $(MAKE) amalg PREFIX=/usr CC=gcc MULTILIB=lib/$(DEB_HOST_MULTIARCH) \ XCFLAGS=-DLUAJIT_ENABLE_LUA52COMPAT TARGET_SONAME=libluajit-5.1-lua52compat.so.2 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781622: RFS: opentyrian/2.1.20130907-1 [ITP]
* Dmitry Smirnov only...@debian.org [150402 08:25]: On Wed, 1 Apr 2015 09:20:34 Etienne Millon wrote: I refreshed this, forwarded two patches and picked the upstream version of one. Nice. But I meant to use all those headers (except for Applied-Upstream which I use ocassionally). Oh, I see. I added them. That's good but let's repack orig.tar to remove this file unless you want to wait till next release. Ftp-masterd do not like blobs and I'm not sure if they will be willing to tolerate this particular one. Better not take chances and not waste their time. Thanks for the heads-up on the new way of repacking. Files-Excluded makes it real easy indeed. Speaking about watch file I recommend to extend regex to match other types of archives, something like opentyrian-(.*)-src\.tar\.(?:gz|bz2|xz) Done. Thanks. I think same issue exists in copyright of Andrea Mazzoleni. Could you fix it too please? Done, repushed, reuploaded! -- Etienne Millon -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781722: libdbd-pg-perl: Interoperability problem wheezy client vs. jessie server
Package: libdbd-pg-perl
Version: 2.19.2-2
Severity: important
Tags: patch
Dear Maintainer,
while doing tests in mixed wheezy/jessie environments (or, with the
same effect, using a private wheezy backport of PostgreSQL 9.4), I
noticed breakage in the table_info and tables methods in DBD::Pg.
Using these methods from a wheezy client (libdbd-pg-perl 2.19.2-2)
against a jessie server (postgresql-9.4 9.4.1-1) result in a
| DBD::Pg::db table_info failed: ERROR: column t.spclocation does not exist
error message, and application abort.
This was fixed in upstream commit
| commit 00f3d68a79beb31a06460dd8f7cb73168c33ca5c
| Author: Greg Sabino Mullane g...@endpoint.com
| Date: Thu May 31 14:10:19 2012 -0400
|
| Adjustments for the loss of spclocation in 9.2
|
| Pg.pm |7 +++
| 1 file changed, 7 insertions(+)
and resolves the issue for me.
Therefore I'd like to suggest to add this to the wheezy version of
libdbd-pg-perl, and in due course, i.e. in the next point release the
latest. Such mixed installations are more likely to occur after the
jessie release, and no one wants to see such breakage.
The test below, stripped down from a production code, uses these
calls for a high-level check for existence of a certain table. It
passes on wheezy and jessie, but fails in the mixed scenario as
described above. Run as the postgres user, or grant proper access
privileges.
=
#!/usr/bin/perl
=cut
Run beforehand:
su postgres -c psql __EOS__
CREATE DATABASE testdb;
\c testdb
CREATE SCHEMA testschema;
CREATE TABLE testschema.test (id integer NOT NULL);
__EOS__
=cut
use 5.010;
use strict;
use warnings;
use DBI;
use Data::Dumper;
use Test::More;
my $dbh = DBI-connect ('dbi:Pg:dbname=testdb', '', '') or die;
my $sth = $dbh-table_info ('%', 'testschema', 'test') or die;
my $info = $sth-fetchall_arrayref;
diag (Dumper ($info));
ok (scalar @$info, 'non-empty table_info result');
my @got = grep { $_ eq 'testschema.test' } $dbh-tables ('%', 'testschema',
'test');
diag (Dumper (\@got));
is (scalar @got, 1, 'got via tables');
done_testing;
=
Regards,
Christoph
-- System Information:
Debian Release: 7.8
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.14.37 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Versions of packages libdbd-pg-perl depends on:
ii libc6 2.13-38+deb7u8
ii libdbi-perl [perl-dbdabi-94] 1.622-1+deb7u1
ii libpq59.1.15-0+deb7u1
ii perl 5.14.2-21+deb7u2
ii perl-base [perlapi-5.14.2]5.14.2-21+deb7u2
libdbd-pg-perl recommends no packages.
libdbd-pg-perl suggests no packages.
-- no debconf information
signature.asc
Description: Digital signature
Bug#779012: Anu update on this?
Hi, Any update on this? I have a Jenkin instance that builds a couple of my packages, including cross compiling them to 32 and 64 bit Windows and running the test suite under Wine. Each time the wine package gets upgraded, I have to manually re-apply this patch. It I don't, the tests for the 64 bit Windows build will fail. Erik -- -- Erik de Castro Lopo http://www.mega-nerd.com/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744231: gnucash: Crash on QIF import
Hi Chris, On Fri, 11 Apr 2014 17:41:09 Chris Bainbridge wrote: Start QIF import, at Set a date format for this QIF file select 'd-m-y'. Crash. I've noticed that upstream closed corresponding bug report [1] due to lack of information (they could not reproduce the problem). Do you still have this problem with GnuCash-2.6.4 ? Thanks. [1]: https://bugzilla.gnome.org/show_bug.cgi?id=728050 -- All the best, Dmitry Smirnov GPG key : 4096R/53968D1B signature.asc Description: This is a digitally signed message part.
Bug#781727: update responders to latest upstream release
package: ruby-responders version: 2.0.2-1 needed for diaspora, but it needs rails 4.2 /tmp/buildd/ruby-responders-2.1.0/test/test_helper.rb:35:in `class:TestCase': undefined method `test_order=' for ActiveSupport::TestCase:Class (NoMethodError) from /tmp/buildd/ruby-responders-2.1.0/test/test_helper.rb:34:in `top (required)' from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /tmp/buildd/ruby-responders-2.1.0/test/action_controller/respond_with_test.rb:1:in `top (required)' from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:15:in `block in main' from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:4:in `select' from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:4:in `main' rake aborted! Command failed with status (1): [ruby -Itest:. -I/usr/lib/ruby/vendor_ruby /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb test/action_controller/respond_with_test.rb test/responders/collection_responder_test.rb test/responders/controller_method_test.rb test/responders/flash_responder_test.rb test/responders/http_cache_responder_test.rb ] -e:1:in `main' Tasks: TOP = default (See full trace by running task with --trace) ERROR: Test ruby2.1 failed. Exiting. signature.asc Description: OpenPGP digital signature
Bug#781726: how to solve the live-tools upgrade issue? (#781725)
Hello! Just adding my 5c here since I've previously been at the receiving end of the very same bug. On Thu, Apr 02, 2015 at 10:17:52AM +0200, Andreas Beckmann wrote: [...] live-tools/wheezy is buggy, causing install/upgrade failures in other packages (wheezy: #779888, upgrade: #781725). The underlying dependency issue has been fixed in jessie long ago, Next stop - stable proposed update then?! but that is not sufficient to get a working upgrade ordering without adding Breaks against the buggy wheezy version somewhere: [...] This happened because live-tools/jessie has not yet been unpacked and instead the buggy replacement update-initramfs from live-tools/wheezy gets used. dmsetup is not required in a wheezy installation of live-tools, but gets pulled in during the upgrade to jessie. This could be fixed (I verified this by building a patched lvm2 and using it in a piuparts test) by adding Breaks: Breaks: live-tools ( 4.0.1-1) to dmsetup to change the unpacking order and get rid of the broken live-tools before configuring dmsetup, but that has been rejected by the lvm2 maintainer (#778828). I think spreading workarounds for this issue all over the archive is not very nice. If anything, we should have a stronger policy against packages diverting stuff and not allow them in the archive without multiple developers supporting their existance and making sure bugs like the one in live-tools does not exist. If you really want to solve this and similar issues in a generic way for the future I'd suggest an extension to apt(itude) is developed to always pull in a meta-package first during dist-upgrade (or when it detects a new suite has been added during update). This meta-package can then carry all workarounds in one place. Note that removing live-tools from jessie won't solve this upgrade issue. I suggest simply documenting aptitude purge live-tools as one of the pre-upgrade checks to do prior to upgrading to Jessie in the release notes. You might argue that noone reads the release notes, but then they get what they deserve. Let user support forums deal with it. According to popcon the live-tools install-base is very marginal anyway. Regards, Andreas Henriksson PS. this was solved in util-linux by dropping the update-initramfs call given that initramfs-tools = 0.117 did not make it into Jessie. Apparently now the new version has been allowed to migrate?! This means initramfs will contain outdated versions of files from util-linux. I've already had enough of this issue and will now simply stick my head in the sand and say that other people can deal with any issues related to initramfs (and util-linux). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781024: quassel: diff for NMU version 1:0.10.0-2.3
Dear maintainer, I've been using the patched build locally for 2 working days without issues, so I think it's time to push it to unstable for wider testing. This is quite a complex patch for this late in the release cycle, but I really don't see an option for a less complex one. But I suggest we let it spend a few days in unstable before seeking an unblock request. Attached is the nmudiff. Cheers, Olly diff -Nru quassel-0.10.0/debian/changelog quassel-0.10.0/debian/changelog --- quassel-0.10.0/debian/changelog 2014-11-09 02:29:37.0 +1300 +++ quassel-0.10.0/debian/changelog 2015-04-01 11:44:18.0 +1300 @@ -1,3 +1,12 @@ +quassel (1:0.10.0-2.3) unstable; urgency=high + + * Non-maintainer upload with maintainer's permission. + * Improve the message-splitting algorithm for PRIVMSG and CTCP. Original +patch from Michael Marley, backported by Steinar H. Gunderson. Fixes +CVE-2015-2778 and CVE-2015-2779. (Closes: #781024) + + -- Olly Betts o...@survex.com Wed, 01 Apr 2015 11:41:28 +1300 + quassel (1:0.10.0-2.2) unstable; urgency=high * Non-maintainer upload. diff -Nru quassel-0.10.0/debian/patches/CVE-2015-2778.patch quassel-0.10.0/debian/patches/CVE-2015-2778.patch --- quassel-0.10.0/debian/patches/CVE-2015-2778.patch 1970-01-01 12:00:00.0 +1200 +++ quassel-0.10.0/debian/patches/CVE-2015-2778.patch 2015-04-01 11:37:08.0 +1300 @@ -0,0 +1,421 @@ +From b5e38970ffd55e2dd9f706ce75af9a8d7730b1b8 Mon Sep 17 00:00:00 2001 +From: Michael Marley mich...@michaelmarley.com +Date: Sat, 21 Feb 2015 07:33:57 -0500 +Subject: [PATCH] Improve the message-splitting algorithm for PRIVMSG and CTCP + +This introduces a new message splitting algorithm based on +QTextBoundaryFinder. It works by first starting with the entire +message to be sent, encoding it, and checking to see if it is over +the maximum message length. If it is, it uses QTBF to find the +word boundary most immediately preceding the maximum length. If no +suitable boundary can be found, it falls back to searching for +grapheme boundaries. It repeats this process until the entire +message has been sent. + +Unlike what it replaces, the new splitting code is not recursive +and cannot cause stack overflows. Additionally, if it is unable +to split a string, it will give up gracefully and not crash the +core or cause a thread to run away. + +This patch fixes two bugs. The first is garbage characters caused +by accidentally splitting the string in the middle of a multibyte +character. Since the new code splits at a character level instead +of a byte level, this will no longer be an issue. The second is +the core crash caused by sending an overlength CTCP query (/me) +containing only multibyte characters. This bug was caused by the +old CTCP splitter using the byte index from lastParamOverrun() as +a character index for a QString. +--- + src/core/corebasichandler.cpp | 3 ++ + src/core/corebasichandler.h | 1 + + src/core/corenetwork.cpp | 86 +++ + src/core/corenetwork.h| 5 +++ + src/core/coreuserinputhandler.cpp | 72 +++- + src/core/coreuserinputhandler.h | 2 +- + src/core/ctcpparser.cpp | 26 +++- + 7 files changed, 124 insertions(+), 71 deletions(-) + +Index: quassel-0.10.0/src/core/corebasichandler.cpp +=== +--- quassel-0.10.0.orig/src/core/corebasichandler.cpp quassel-0.10.0/src/core/corebasichandler.cpp +@@ -33,6 +33,9 @@ CoreBasicHandler::CoreBasicHandler(CoreN + connect(this, SIGNAL(putCmd(QString, const QListQByteArray , const QByteArray )), + network(), SLOT(putCmd(QString, const QListQByteArray , const QByteArray ))); + ++connect(this, SIGNAL(putCmd(QString, const QListQListQByteArray , const QByteArray )), ++network(), SLOT(putCmd(QString, const QListQListQByteArray , const QByteArray ))); ++ + connect(this, SIGNAL(putRawLine(const QByteArray )), + network(), SLOT(putRawLine(const QByteArray ))); + } +Index: quassel-0.10.0/src/core/corebasichandler.h +=== +--- quassel-0.10.0.orig/src/core/corebasichandler.h quassel-0.10.0/src/core/corebasichandler.h +@@ -55,6 +55,7 @@ public: + signals: + void displayMsg(Message::Type, BufferInfo::Type, const QString target, const QString text, const QString sender = , Message::Flags flags = Message::None); + void putCmd(const QString cmd, const QListQByteArray params, const QByteArray prefix = QByteArray()); ++void putCmd(const QString cmd, const QListQListQByteArray params, const QByteArray prefix = QByteArray()); + void putRawLine(const QByteArray msg); + + protected: +Index: quassel-0.10.0/src/core/corenetwork.cpp +=== +--- quassel-0.10.0.orig/src/core/corenetwork.cpp
Bug#766040: gnumeric: Sort no longer works
On Mon, 20 Oct 2014 12:12:37 ael wrote: I have been using gnumeric for many years including the sort function. But it now seems to be broken. On the other hand, it isn't documented so maybe I do not understand how to use the new version. But I have had no problems before. I'm not too confident with spreadsheets as I use them rarely but I tried to reproduce this problem and found sorting working for me. Actually I'm slightly confused what this problem is about -- either something about sorting algorithm not working as expected or problem with GUI elements not rendered or not responding? The latter could be a problem with gtk3- engines-* if you are using any on KDE. Please confirm if this is still a problem and if it is then provide precise step-by-step instructions how to reproduce, preferably with sample document. Also it may worth to try latest gnumeric from experimental. Thank you. -- Regards, Dmitry Smirnov. --- It is a mistake to try to look too far ahead. The chain of destiny can only be grasped one link at a time. -- Winston Churchill signature.asc Description: This is a digitally signed message part.
Bug#779606: daemon-reexec starts plymouth-start.service service
Hey Michael, Michael Biebl [2015-03-03 1:05 +0100]: I have plymouth installed and enabled (via splash on the kernel command line). When I run systemctl daemon-reexec, plymouth is (re)started: I could reproduce this (and other restarted services) until recently, but it seems fixed with the v219-stable updates (for me and also for the original reporter in the Ubuntu bug LP#1431200). Do you still get this with 219-6? If so, can you please put the journalctl -f output here that happens when you do systemctl daemon-reload (and/or -reexec). Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781731: [lletters] application is frozen after a sound was played
Package: lletters Version: 0.1.95 gtk2-3.2 Severity: important --- Please enter the report below this line. --- If we click a card which includes a sound, the card shows a picture and a sound plays. Then, if we click to the picture, the card does not close and the application stays in a frozen state. The rest of the cards, which do not include sounds, are working normally. --- System information. --- Architecture: amd64 Kernel: Linux 3.16.0-4-amd64 Debian Release: 8.0 500 testing security.debian.org 500 testing ftp.gr.debian.org 500 stable downloads.sourceforge.net 500 stable dl.google.com --- Package information. --- Depends (Version) | Installed ==- - libc6 (= 2.3) | libgdk-pixbuf2.0-0 (= 2.22.0) | libglib2.0-0 (= 2.12.0) | libgtk2.0-0 (= 2.8.0) | lletters-media | oss-compat | Package's Recommends field is empty. Package's Suggests field is empty.
Bug#740093: please do not remove
Hello, juste to add a datapoint: I'm using this package on several lenovo notebooks without issue. There is no other graphical way to configure the multiple pointing devices that we have on these machines: - the touchpad - the lenovo red trackpoint - an external usb mouse on the docking station gnome settings shows the mouse and the touchpad, but not the trackpoint. Besides, it does not show the advanced options of gpds. With gpointing-device-settings, I'm able to configure the trackpoint to work as a wheelmouse for paging, and I have found no other way to do that through a gui. I guess there are possibilities through the command line, and I could find them, but a gui is much more convenient and vastly easier to teach to users. Thanks for your consideration, -- Rémi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762257: Disregard my previous message, problem persists
Unfortunately, the problem still persists. It did not appear in a directory of portrait-format photos that I was browsing, but this is just an exception. The problem seems to be triggered for large images of some minimum size (width?). Sorry for the confusion. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781771: unblock: chromium-browser/41.0.2272.118-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package chromium-browser. It fixes critical security issues. unblock chromium-browser/41.0.2272.118-1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#472188: proposed NMU
tag 536544 + patch
tag 621409 + patch
thanks
Ubuntu is carrying a patch that fixes the vnc4 build on armel and
armhf. Better yet, the patch actually produces a usable server on both
architectures :)
Unless there's an objection, I'd like to go ahead and upload an NMU
using the attached patch.
diff -u vnc4-4.1.1+X4.3.0/debian/changelog vnc4-4.1.1+X4.3.0/debian/changelog
--- vnc4-4.1.1+X4.3.0/debian/changelog
+++ vnc4-4.1.1+X4.3.0/debian/changelog
@@ -1,3 +1,11 @@
+vnc4 (4.1.1+X4.3.0-37.6) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * armhf_inw_inb.patch: Fix FTBFS on armel/armhf (from Ubuntu).
+Closes: #472188, #536544, #621409.
+
+ -- dann frazier da...@debian.org Thu, 02 Apr 2015 13:34:56 -0400
+
vnc4 (4.1.1+X4.3.0-37.5) experimental; urgency=medium
* Non-maintainer upload.
only in patch2:
unchanged:
--- vnc4-4.1.1+X4.3.0.orig/debian/patches/armhf_inw_inb.patch
+++ vnc4-4.1.1+X4.3.0/debian/patches/armhf_inw_inb.patch
@@ -0,0 +1,55 @@
+--- vnc4-4.1.1+X4.3.0/unix/xc/programs/Xserver/hw/xfree86/common/compiler.h 2003-01-29 08:23:20.0 -0700
vnc4-4.1.1+xorg4.3.0/unix/xc/programs/Xserver/hw/xfree86/common/compiler.h 2015-03-31 12:21:54.0 -0600
+@@ -857,6 +857,7 @@ static __inline__ void stw_u(unsigned lo
+
+ unsigned int IOPortBase; /* Memory mapped I/O port area */
+
++#if defined(__mips__)
+ static __inline__ void
+ outb(unsigned PORT_SIZE port, unsigned char val)
+ {
+@@ -893,8 +894,6 @@ inl(unsigned PORT_SIZE port)
+ return *(volatile unsigned int*)(((unsigned PORT_SIZE)(port))+IOPortBase);
+ }
+
+-
+-#if defined(__mips__)
+ static __inline__ unsigned long ldq_u(unsigned long * r11)
+ {
+ unsigned long r1;
+@@ -1244,6 +1243,35 @@ inl(unsigned short port)
+ #define mem_barrier() eieio()
+ #define write_mem_barrier() eieio()
+
++# elif defined(__arm__) defined(__linux__)
++
++/* for Linux on ARM, we use the LIBC inx/outx routines */
++/* note that the appropriate setup via ioperm needs to be done */
++/* *before* any inx/outx is done. */
++#include sys/io.h
++
++static __inline__ void
++xf_outb(unsigned short port, unsigned char val)
++{
++outb(val, port);
++}
++
++static __inline__ void
++xf_outw(unsigned short port, unsigned short val)
++{
++outw(val, port);
++}
++
++static __inline__ void
++xf_outl(unsigned short port, unsigned int val)
++{
++outl(val, port);
++}
++
++#define outb xf_outb
++#define outw xf_outw
++#define outl xf_outl
++
+ # else /* ix86 */
+
+ #define ldq_u(p) (*((unsigned long *)(p)))
only in patch2:
unchanged:
--- vnc4-4.1.1+X4.3.0.orig/unix/xc/programs/Xserver/hw/xfree86/common/compiler.h
+++ vnc4-4.1.1+X4.3.0/unix/xc/programs/Xserver/hw/xfree86/common/compiler.h
@@ -857,6 +857,7 @@
unsigned int IOPortBase; /* Memory mapped I/O port area */
+#if defined(__mips__)
static __inline__ void
outb(unsigned PORT_SIZE port, unsigned char val)
{
@@ -893,8 +894,6 @@
return *(volatile unsigned int*)(((unsigned PORT_SIZE)(port))+IOPortBase);
}
-
-#if defined(__mips__)
static __inline__ unsigned long ldq_u(unsigned long * r11)
{
unsigned long r1;
@@ -1244,6 +1243,35 @@
#define mem_barrier() eieio()
#define write_mem_barrier() eieio()
+# elif defined(__arm__) defined(__linux__)
+
+/* for Linux on ARM, we use the LIBC inx/outx routines */
+/* note that the appropriate setup via ioperm needs to be done */
+/* *before* any inx/outx is done. */
+#include sys/io.h
+
+static __inline__ void
+xf_outb(unsigned short port, unsigned char val)
+{
+outb(val, port);
+}
+
+static __inline__ void
+xf_outw(unsigned short port, unsigned short val)
+{
+outw(val, port);
+}
+
+static __inline__ void
+xf_outl(unsigned short port, unsigned int val)
+{
+outl(val, port);
+}
+
+#define outb xf_outb
+#define outw xf_outw
+#define outl xf_outl
+
# else /* ix86 */
#define ldq_u(p) (*((unsigned long *)(p)))
Bug#781779: selinux-policy-default: not possible to login via GUI when SELinux is set to enforcing
Package: selinux-policy-default
Version: 2:2.20140421-9
Severity: grave
Justification: renders package unusable
Dear Maintainer,
after enabling SELinux it is not possible to use graphical login anymore.
Instead of the desktop the following message appears:
Oh no! Something has gone wrong.
A problem has occurred and the system can't recover. All extensions have been
disabled as a precaution.
Beneath there is a 'Logout' button.
When setting 'setenforce 0' it is possible to login (again).
Because there are so many AVCs, I cannot name the root cause here.
Attached you can find the output of 'audit2allow --boot'.
I set the severity to grave because IMHO a lot of people use / will
use Debian as their desktop / laptop OS with graphical UI. This is
not usable any more when SELinux is enabled using the current default
policy.
If I can support finding the root cause or providing a patch, please
drop me a note.
Kind regards
Andre
-- 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/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages selinux-policy-default depends on:
ii libpam-modules 1.1.8-3.1
ii libselinux1 2.3-2
ii libsepol12.3-2
ii policycoreutils 2.3-1
ii python 2.7.9-1
ii selinux-utils2.3-2
Versions of packages selinux-policy-default recommends:
ii checkpolicy 2.3-1
ii setools 3.3.8-3.1
Versions of packages selinux-policy-default suggests:
pn logchecknone
pn syslog-summary none
-- no debconf information
== 8 ==
# audit2allow --boot
#= NetworkManager_t ==
allow NetworkManager_t NetworkManager_initrc_exec_t:dir { read getattr open
search };
allow NetworkManager_t init_var_run_t:dir read;
allow NetworkManager_t self:rawip_socket { write create setopt getattr };
allow NetworkManager_t systemd_logind_t:dbus send_msg;
allow NetworkManager_t systemd_logind_t:fd use;
allow NetworkManager_t systemd_logind_var_run_t:dir { read search };
allow NetworkManager_t systemd_logind_var_run_t:fifo_file write;
allow NetworkManager_t systemd_logind_var_run_t:file { read getattr open };
#= alsa_t ==
# The source type 'alsa_t' can write to a 'dir' of the following types:
# pulseaudio_home_t, alsa_tmp_t, alsa_var_lib_t
allow alsa_t var_run_t:dir { write create add_name setattr };
# The source type 'alsa_t' can write to a 'file' of the following types:
# pulseaudio_home_t, alsa_tmp_t, alsa_var_lib_t, alsa_lock_t, alsa_etc_rw_t,
alsa_tmpfs_t, user_home_t
allow alsa_t var_run_t:file { read write create open lock };
allow alsa_t var_run_t:lnk_file create;
allow alsa_t xdm_t:process signull;
allow alsa_t xdm_tmpfs_t:file { read getattr unlink open };
#= apmd_t ==
allow apmd_t device_t:chr_file { read ioctl open };
#= kernel_t ==
allow kernel_t systemd_unit_file_t:service { status start };
#= policykit_t ==
# This avc can be allowed using one of the these booleans:
# authlogin_nsswitch_use_ldap, global_ssp
allow policykit_t urandom_device_t:chr_file { read getattr open };
#= rtkit_daemon_t ==
allow rtkit_daemon_t xdm_t:process setsched;
#= systemd_cgroups_t ==
allow systemd_cgroups_t kernel_t:unix_dgram_socket sendto;
allow systemd_cgroups_t kernel_t:unix_stream_socket connectto;
#= systemd_logind_t ==
allow systemd_logind_t NetworkManager_t:dbus send_msg;
# The source type 'systemd_logind_t' can write to a 'dir' of the following
types:
# var_auth_t, cgroup_t, user_tmp_t, udev_var_run_t, systemd_logind_var_run_t,
systemd_logind_sessions_t
allow systemd_logind_t tmpfs_t:dir { write remove_name rmdir };
allow systemd_logind_t tmpfs_t:sock_file unlink;
allow systemd_logind_t user_tmpfs_t:dir read;
allow systemd_logind_t user_tmpfs_t:file getattr;
# The source type 'systemd_logind_t' can write to a 'dir' of the following
types:
# var_auth_t, cgroup_t, user_tmp_t, udev_var_run_t, systemd_logind_var_run_t,
systemd_logind_sessions_t
allow systemd_logind_t xdm_tmpfs_t:dir { write getattr rmdir read remove_name
open };
allow systemd_logind_t xdm_tmpfs_t:file { getattr unlink };
#= udev_t ==
allow udev_t self:netlink_socket { write getattr setopt read bind create };
#= unconfined_t ==
# This avc can be allowed using one of the these booleans:
# allow_execstack, allow_execmem
allow unconfined_t self:process execmem;
#= xdm_t ==
allow xdm_t init_t:system status;
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
Bug#781775: qemu-x86_64-static segfaults on Raspberry Pi when starting debian wheezy guest
02.04.2015 23:25, Danny Mitchell wrote: Package: qemu, qemu-user-static Version: 1.1.2+dfsg-6 (armhf) I've got debian wheezy (7.5) for x86_64 installed on an internal disk (installed with debootstrap), and a Raspberry Pi running debian wheezy (7.8) with the x86_64 disk, in an external enclosure, connected to one of the RPi USB ports. I'm trying to run the x86_64 system in a VM from the RPi using qemu and chroot, but it dies with a Segmentation fault error: # chroot /mnt qemu: uncaught target signal 11 (Segmentation fault) - core dumped Segmentation fault # This is the same as #703825 (http://bugs.debian.org/703825) which boils down to, as Peter Maydell puts it, «That is just the usual x86 linux-user isn't really supported». It is a general issue, not related to platform. More, qemu-user completely lacks multi-threaded support, and almost all current executables use multi-threaded primitives in one way or another. Thanks, /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781770: [linthesia] Application closes unexpectedly
Package: linthesia Version: 0.4.3-1 Severity: important --- Please enter the report below this line. --- Application closes unexpectedly while trying to load a mid file, or trying to select track, or trying to test output sound. --- System information. --- Architecture: amd64 Kernel: Linux 3.16.0-4-amd64 Debian Release: 8.0 500 testing security.debian.org 500 testing ftp.gr.debian.org 500 stable downloads.sourceforge.net 500 stable dl.google.com --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty.
Bug#781769: libsolid4: Device notifier shows multiple entries (four) for mtp device
Package: libsolid4 Version: 4:4.14.2-5 Severity: normal Tags: upstream patch Dear Maintainer, attaching an Android phone via USB to my KDE desktop shows in the device notifier 5 entries, 4 without a proper description. The reason probably is that some Android phone get multiple solid entries: udi = '/org/kde/solid/udev/sys/devices/pci:00/:00:02.1/usb1/1-1' ID_GPHOTO2 = '1' (string) ID_MEDIA_PLAYER = '1' (string) udi = '/org/kde/solid/udev/sys/devices/pci:00/:00:02.1/usb1/1-1/1-1:1.2' ID_GPHOTO2 = '1' (string) ID_MEDIA_PLAYER = '1' (string) udi = '/org/kde/solid/udev/sys/devices/pci:00/:00:02.1/usb1/1-1/1-1:1.3' ID_GPHOTO2 = '1' (string) ID_MEDIA_PLAYER = '1' (string) udi = '/org/kde/solid/udev/sys/devices/pci:00/:00:02.1/usb1/1-1/1-1:1.1' udi = '/org/kde/solid/udev/sys/devices/pci:00/:00:02.1/usb1/1-1/1-1:1.0' There are two upstream bugs about this issue [1] [2]. While both got closed already, I think in KDE4 only that part about the camera aka ID_MEDIA_PLAYER is solved [3]. The KDE5 version shows an additional check for ID_GPHOTO2. I rebuilt kde4libs with these 2 lines applied and then only one entry was shown when connecting the phone (patch attached). Kind regards, Bernhard [1] https://bugs.kde.org/show_bug.cgi?id=339334 [2] https://bugs.kde.org/show_bug.cgi?id=336523 [3] http://quickgit.kde.org/?p=kdelibs.gita=historyh=f1796e97e5635fcb93a0bfc600b9da6ecce914a5f=solid%2Fsolid%2Fbackends%2Fudev%2Fudevmanager.cpp [4] http://quickgit.kde.org/?p=solid.gita=historyh=db9a05543b0a14dffeb023650995a344eabb2fd7f=src%2Fsolid%2Fdevices%2Fbackends%2Fudev%2Fudevmanager.cpp -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (990, 'testing-updates'), (990, 'testing'), (500, 'testing-proposed-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libsolid4 depends on: ii libc62.19-15 ii libqt4-dbus 4:4.8.6+git64-g5dc8b2b+dfsg-3 ii libqt4-xml 4:4.8.6+git64-g5dc8b2b+dfsg-3 ii libqtcore4 4:4.8.6+git64-g5dc8b2b+dfsg-3 ii libqtgui44:4.8.6+git64-g5dc8b2b+dfsg-3 ii libstdc++6 4.9.2-10 ii libudev1 215-12 ii udev 215-12 Versions of packages libsolid4 recommends: ii udisks2 2.1.3-5 ii upower 0.99.1-3.1 Versions of packages libsolid4 suggests: ii media-player-info 22-2 -- no debconf information Description: Do not show child devices of cameras and mobiles in device notifier Combination of these 2 patches: http://quickgit.kde.org/?p=solid.gita=commitdiffh=a1cda008d582bc9d8aeecd2c191f631e0fbb6f79 Don't report gphoto devices that are child of gphoto devices http://quickgit.kde.org/?p=solid.gita=commitdiffh=a100520e3891368b370b8925f44e5fb71eaa23a3 complete check for multiple MTP/PTP devices Last-Update: 2015-04-02 --- kde4libs-4.14.2.orig/solid/solid/backends/udev/udevmanager.cpp +++ kde4libs-4.14.2/solid/solid/backends/udev/udevmanager.cpp @@ -129,8 +129,8 @@ bool UDevManager::Private::checkOfIntere return device.subsystem() == QLatin1String(dvb) || device.subsystem() == QLatin1String(video4linux) || device.subsystem() == QLatin1String(net) || - device.deviceProperty(ID_MEDIA_PLAYER).toString().isEmpty() == false || // media-player-info recognized devices - device.deviceProperty(ID_GPHOTO2).toInt() == 1; // GPhoto2 cameras + (!device.deviceProperty(ID_MEDIA_PLAYER).toString().isEmpty() device.parent().deviceProperty(ID_MEDIA_PLAYER).toString().isEmpty()) || // media-player-info recognized devices + (device.deviceProperty(ID_GPHOTO2).toInt() == 1 device.parent().deviceProperty(ID_GPHOTO2).toInt() != 1); // GPhoto2 cameras } bool UDevManager::Private::isLidBubtton(const UdevQt::Device device)
Bug#769716: iceweasel: OpenH264 back in 37, breaks H.264 playback
On Thu, Apr 02, 2015 at 10:50:42AM -0500, Jonathan Lane wrote: Package: iceweasel Followup-For: Bug #769716 Dear Maintainer, The OpenH264 download by default is once again in Iceweasel 37, and actively breaks H.264 playback support on Debian Jessie, which works with Iceweasel 31esr and GStreamer. This is also the case with upstream builds of FF38.0a2. I have filed a bug with Mozilla here: https://bugzilla.mozilla.org/show_bug.cgi?id=1150544 As far as I can tell, the only thing that's really happening is that about:addons tells that openh264 is going to be downloaded, but that doesn't happen. However, if it /had/ been downloaded in the past, with the previous builds that did download it by default, it might be possible it's being used in that case. The pref to disable appears to have changed, so the change I did in version 34 doesn't work anymore. If you manually remove the gmp-gmpopenh264 directory somewhere in $HOME/.mozilla, it should get back to normal for you. With that being said, either with openh264 or without, iceweasel 37 plays h264 just fine here (and strangely doesn't even use openh264 when i do enable it). Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781772: unblock: iceweasel/31.6.0esr-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package iceweasel. It fixes multiplt security issues. unblock iceweasel/31.6.0esr-1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781773: unblock: icedove/31.6.0-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package icedove. It fixes multiple security issues. unblock icedove/31.6.0-1 -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762257: Problem seems resolved
I confirm the observation of Alex Goebel, i.e. that this problem was independent of image and zoom settings. I noticed another issue that might have been related: When browsing through directories of images, the value showed in the last column of the output of the command free (i.e. cached) would grow continuously, until the system would begin to thrash. Today, I did a full-upgrade, and both problems disappeared, even though geeqie is still 1:1.2-3+b1. The following packages on which geeqie depends (according to apt-rdepends) were upgraded: coreutils 8.23-3 - 8.23-4 debconf 1.5.55 - 1.5.56 libbz2-1.0 1.0.6-7+b2 - 1.0.6-7+b3 libc-bin 2.19-15 - 2.19-17 libc6 2.19-15 - 2.19-17 libgssapi-krb5-2 1.12.1+dfsg-18 - 1.12.1+dfsg-19 libjpeg8 8d1-1 - 8d1-2 libk5crypto3 1.12.1+dfsg-18 - 1.12.1+dfsg-19 libkrb5-3 1.12.1+dfsg-18 - 1.12.1+dfsg-19 libkrb5support0 1.12.1+dfsg-18 - 1.12.1+dfsg-19 libxfont1 1:1.4.99.901-1+b3 - 1:1.5.1-1 multiarch-support 2.19-15 - 2.19-17 perl-base 5.18.2-7 - 5.20.2-2 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781762: liblua5.1-0-dev: lua.h and liblua.so not present in include and lib paths
close 781762 thanks On Thu, Apr 02, 2015 at 06:17:33PM +0200, Miguel Rubio-Roy wrote: Package: liblua5.1-0-dev Version: 5.1.5-7.1 Severity: serious Tags: newcomer Justification: Policy 8.4 Dear Maintainer, When trying to compile using the -llua option, the compiler does not found liblua.so on its path. According to the Debian Policy Manual, section 8.4, The development package should contain a symlink for the associated shared library without a version number. I kindly request you to implement this recommendation. Also, I think it is Debian Policy to name the libraries like: liblualiblua.so.5.1.0 instead of liblualiblua5.1.so.0.0.0 You should use `pkg-config --libs lua5.1` to get the correct linker flags. Orelse use -llua5.1. The version number the policy talks about is the 0.0.0 part, not the 5.1 (that is part of the name of the library). There is no such a thing like lua. lua5.1 and lua5.2 are different, incompatible, libraries, not two versions of the same. Best, -- Enrico Tassi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780160: CVE-2014-9639
On Mon, Mar 09, 2015 at 11:08:57PM +0100, Moritz Muehlenhoff wrote: Package: opus-tools Version: 0.1.9-1 Severity: important Tags: security Hi, CVE-2014-9638 and CVE-2014-9639 for vorbis-tools also affect opus-tools, please see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776086 for details and reproducers. The jessie release is coming closer; did you hear back from upstream? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781776: selinux-policy-default: postfix does not start when SELinux is set to enforcing
Package: selinux-policy-default
Version: 2:2.20140421-9
Severity: normal
Dear Maintainer,
postfix does not start when SELinux is set to enforcing:
root@debian8gi:~# se_apt-get install postfix
[...]
root@debian8gi:~# run_init systemctl start postfix
Authenticating root.
Password:
root@debian8gi:~# run_init systemctl status postfix
Authenticating root.
Password:
● postfix.service - LSB: Postfix Mail Transport Agent
Loaded: loaded (/etc/init.d/postfix)
Drop-In: /run/systemd/generator/postfix.service.d
└─50-postfix-$mail-transport-agent.conf
Active: active (exited) since Thu 2015-04-02 13:09:43 CEST; 8min ago
Process: 2028 ExecStop=/etc/init.d/postfix stop (code=exited,
status=0/SUCCESS)
Process: 2040 ExecStart=/etc/init.d/postfix start (code=exited,
status=0/SUCCESS)
Apr 02 13:09:43 debian8gi postfix[2040]: Starting Postfix Mail Transport Agent:
postfix.
Apr 02 13:09:43 debian8gi postfix/master[2140]: fatal: open lock file
pid/master.pid: cannot create file exclusively: Permission denied
The following AVC is logged:
type=AVC msg=audit(1427973050.472:88): avc: denied { net_admin } for
pid=2144 comm=systemd-tty-ask capability=12
scontext=system_u:system_r:systemd_passwd_agent_t:s0
tcontext=system_u:system_r:systemd_passwd_agent_t:s0 tclass=capability
permissive=0
It looks that the appropriate directory was not correctly labled by default:
root@debian8gi:/etc/postfix# ls -ldZ /var/spool/postfix/pid/
drwxr-xr-x. 2 root root system_u:object_r:var_spool_t:SystemLow 4096 Apr 2
13:07 /var/spool/postfix/pid/
root@debian8gi:/etc/postfix# restorecon -v /var/spool/postfix/pid/
restorecon reset /var/spool/postfix/pid context
system_u:object_r:var_spool_t:s0-system_u:object_r:var_run_t:s0
root@debian8gi:/etc/postfix# ls -ldZ /var/spool/postfix/pid/
drwxr-xr-x. 2 root root system_u:object_r:var_run_t:SystemLow 4096 Apr 2 13:07
/var/spool/postfix/pid/
Nevertheless: even after this adaption the process still not starts up:
root@debian8gi:/etc/postfix# run_init systemctl start postfix
Authenticating root.
Password:
root@debian8gi:/etc/postfix# run_init systemctl status postfix
Authenticating root.
Password:
● postfix.service - LSB: Postfix Mail Transport Agent
Loaded: loaded (/etc/init.d/postfix)
Drop-In: /run/systemd/generator/postfix.service.d
└─50-postfix-$mail-transport-agent.conf
Active: active (exited) since Thu 2015-04-02 14:13:52 CEST; 3s ago
Process: 3455 ExecStop=/etc/init.d/postfix stop (code=exited,
status=0/SUCCESS)
Process: 3468 ExecStart=/etc/init.d/postfix start (code=exited,
status=0/SUCCESS)
Apr 02 14:13:52 debian8gi postfix[3468]: Starting Postfix Mail Transport Agent:
postfix.
Apr 02 14:13:52 debian8gi postfix/master[3568]: fatal: bind: public/pickup:
Permission denied
The AVC:
type=AVC msg=audit(1427976832.296:134): avc: denied { create } for pid=3568
comm=master name=pickup scontext=system_u:system_r:postfix_master_t:s0
tcontext=system_u:object_r:var_spool_t:s0 tclass=sock_file permissive=0
Therefore it looks that a more general restorecon is needed:
root@debian8gi:/etc/postfix# restorecon -v -R /var/spool/postfix
restorecon reset /var/spool/postfix context
system_u:object_r:var_spool_t:s0-system_u:object_r:postfix_spool_t:s0
restorecon reset /var/spool/postfix/deferred context
system_u:object_r:var_spool_t:s0-system_u:object_r:postfix_spool_maildrop_t:s0
restorecon reset /var/spool/postfix/maildrop context
system_u:object_r:var_spool_t:s0-system_u:object_r:postfix_spool_maildrop_t:s0
restorecon reset /var/spool/postfix/etc/hosts context
system_u:object_r:etc_runtime_t:s0-system_u:object_r:etc_t:s0
restorecon reset /var/spool/postfix/etc/services context
system_u:object_r:etc_runtime_t:s0-system_u:object_r:etc_t:s0
restorecon reset /var/spool/postfix/etc/localtime context
system_u:object_r:etc_runtime_t:s0-system_u:object_r:etc_t:s0
restorecon reset /var/spool/postfix/etc/nsswitch.conf context
system_u:object_r:etc_runtime_t:s0-system_u:object_r:etc_t:s0
restorecon reset /var/spool/postfix/etc/host.conf context
system_u:object_r:etc_runtime_t:s0-system_u:object_r:etc_t:s0
restorecon reset /var/spool/postfix/etc/resolv.conf context
system_u:object_r:etc_runtime_t:s0-system_u:object_r:etc_t:s0
restorecon reset /var/spool/postfix/defer context
system_u:object_r:var_spool_t:s0-system_u:object_r:postfix_spool_maildrop_t:s0
restorecon reset /var/spool/postfix/flush context
system_u:object_r:var_spool_t:s0-system_u:object_r:postfix_spool_flush_t:s0
restorecon reset /var/spool/postfix/public context
system_u:object_r:var_spool_t:s0-system_u:object_r:postfix_public_t:s0
restorecon reset /var/spool/postfix/active context
system_u:object_r:var_spool_t:s0-system_u:object_r:postfix_spool_t:s0
restorecon reset /var/spool/postfix/corrupt context
system_u:object_r:var_spool_t:s0-system_u:object_r:postfix_spool_t:s0
restorecon reset /var/spool/postfix/private context
Bug#778380: [Pkg-nagios-devel] Bug#778380: update check-mk-server to 1.2.4p5
Hi Ilya, Have you had a chance to look at packaging? Thank you very much for taking responsibility of maintaining check-mk package. Regards
Bug#755359: [kdm] systemd seem to fail to start display-manager.service
On Thu, Apr 02, 2015 at 04:20:06PM +0200, John Paul Adrian Glaubitz wrote: On 04/02/2015 12:57 PM, John Paul Adrian Glaubitz wrote: Attaching a debdiff with the proposed changes to the kde-workspace source package which will add systemd support to kdm. Attaching a cleaned up revision the patch where I fixed the tab stops and added an additional line in the debian/changelog to indicate that the file debian/kdm.service was added to the source package. Hi John, Thanks for working on this. I had previously also worked on a systemd unit last year but due to the lack of feedback from KDE maintainers I stopped working on it. My patch from https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754314 retains the kdmrc customisation currently present in the sysvinit script; maybe you can fold that one into your patch? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781443: capnproto: FTBFS on armhf and armel (test seg. faults) but built there in the past
On Sun, Mar 29, 2015 at 07:30:55PM -0700, Tom Lee wrote: Hey Niels, Understood. Hard to see exactly what's going on here because we seem to be falling afoul of https://lists.debian.org/debian-devel/2014/04/msg00322.html. Do you happen to know if there's another way to get access to test-suite.log from these builds? The suggested work-around in that mailing list thread appears to require a change to the packaging, which I imagine we want to try and avoid. Alternatively remove the arm* binaries (capnproto is new in jessie and has no reverse deps) and let ARM porters figure it out if they want support for capnproto in the future. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778753: cabextract: Directory traversal (CVE pending)
On Fri, Feb 20, 2015 at 09:25:56PM -0500, Eric Sharkey wrote: On Thu, Feb 19, 2015 at 5:38 AM, Moritz Muehlenhoff j...@inutil.org wrote: Upstream fix is here: http://sourceforge.net/p/libmspack/code/217 Since unstable has a more recent version than testing, could you make a targeted jessie upload with this patch? I've written a new patch from scratch to fix cabextract 1.4 and uploaded this to jessie-security as 1.4-6. Please let me know if there are any issues. I don't think I've had to do a security upload in the last 10 years or so, so I'm a bit out of practice. I don't have a new build for sid yet. Maybe tomorrow. The jessie release is scheduled for end of April, could you please upload a fixed package? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781775: qemu-x86_64-static segfaults on Raspberry Pi when starting debian wheezy guest
Package: qemu, qemu-user-static Version: 1.1.2+dfsg-6 (armhf) I've got debian wheezy (7.5) for x86_64 installed on an internal disk (installed with debootstrap), and a Raspberry Pi running debian wheezy (7.8) with the x86_64 disk, in an external enclosure, connected to one of the RPi USB ports. I'm trying to run the x86_64 system in a VM from the RPi using qemu and chroot, but it dies with a Segmentation fault error: # chroot /mnt qemu: uncaught target signal 11 (Segmentation fault) - core dumped Segmentation fault # I've tried running other programs from the x86_64 disk, sometimes with success (eg codeyes/code works as expected, but codebash/bash crashes with the same error. I've tried other shells, with the same result. The configuration files are unchanged from installation in both host and guest systems; I can send them if required. I've included keystrokes captured by a script session, which includes details of how I tried to start the VM, and what was mounted and how, and how much memory (physical and swap) are available, and the installed versions of relevant software (including bash). I suspected that the error could be with bash, but other shells fail with the same error; it doesn't seem to be a memory issue, because the free command says there's still at least 80MB free, and swap hasn't been used at all. If you need any more information, please let me know. Danny Mitchell qemu_bug_script_output Description: Binary data
Bug#781774: cgal: Incorrect license for the CORE library
Source: cgal Severity: normal Tags: upstream Dear Maintainer, According to the LICENSE file: - CORE, in the directories include/CGAL/CORE and src/CGAL_Core, is licensed under the LGPL (see LICENSE.LGPL). However, files in the mentioned directories state in their headers that they are licensed under the GPL3+ license. I believe that the LICENSE file should consequently be modified accordingly and mention GPL3+ instead of LGPL. Thanks, Thomas -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781778: linux-image-3.16.0-4-amd64: Xorg startup delayed (minutes), errors reported by i915 driver
Package: src:linux Version: 3.16.7-ckt7-1 Severity: normal Dear Maintainer, I guess the problem eventually occured after a system update. Until now, I do not have a solution, I did not find the same description in forums / posts / bug reports.. Thanks for your time, Dimitri -- Package-specific info: ** Version: Linux version 3.16.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt7-1 (2015-03-01) ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 root=UUID=5d41cc9b-817f-44a6-82c9-75898ef11f11 ro quiet ** Tainted: W (512) * Taint on warning. ** Kernel log: [ 12.898566] EXT4-fs (sdb2): mounting ext3 file system using the ext4 subsystem [ 12.948220] EXT4-fs (sdb2): mounted filesystem with ordered data mode. Opts: (null) [ 12.954355] systemd-journald[181]: Received request to flush runtime journal from PID 1 [ 13.044101] alx :02:00.0: irq 46 for MSI/MSI-X [ 13.044238] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready [ 13.045006] alx :02:00.0 eth1: NIC Up: 1 Gbps Full [ 13.045217] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready [ 13.807729] cfg80211: Calling CRDA to update world regulatory domain [ 13.899500] cfg80211: World regulatory domain updated: [ 13.899504] cfg80211: DFS Master region: unset [ 13.899505] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) [ 13.899508] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) [ 13.899509] cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) [ 13.899511] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A) [ 13.899513] cfg80211: (517 KHz - 525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A) [ 13.899515] cfg80211: (525 KHz - 533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (0 s) [ 13.899516] cfg80211: (549 KHz - 573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s) [ 13.899517] cfg80211: (5735000 KHz - 5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A) [ 13.899519] cfg80211: (5724 KHz - 6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A) [ 14.266335] [drm:cpt_set_fifo_underrun_reporting] *ERROR* uncleared pch fifo underrun on pch transcoder B [ 1804.139623] [ cut here ] [ 1804.139644] WARNING: CPU: 0 PID: 1194 at /build/linux-SAvLSw/linux-3.16.7-ckt7/drivers/gpu/drm/i915/intel_display.c:4952 intel_modeset_check_state+0x775/0x780 [i915]() [ 1804.139646] wrong connector dpms state [ 1804.139647] Modules linked in: cfg80211 rfkill binfmt_misc x86_pkg_temp_thermal intel_powerclamp intel_rapl coretemp kvm crc32_pclmul ghash_clmulni_intel iTCO_wdt iTCO_vendor_support aesni_intel i915 aes_x86_64 drm_kms_helper drm joydev lrw gf128mul i2c_i801 glue_helper ablk_helper i2c_algo_bit loop cryptd evdev snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic i2c_core lpc_ich shpchp mei_me mfd_core snd_hda_intel pcspkr mei psmouse fuse snd_hda_controller snd_hda_codec snd_hwdep snd_pcm tpm_infineon snd_timer parport_pc tpm_tis snd soundcore battery tpm video serio_raw processor ppdev button lp parport autofs4 ext4 crc16 mbcache jbd2 sg sd_mod crc_t10dif sr_mod crct10dif_generic cdrom hid_generic ata_generic usbhid hid crct10dif_pclmul crct10dif_common crc32c_intel ata_piix via_rhine [ 1804.139693] ahci mii alx mdio libahci pata_jmicron ehci_pci libata xhci_hcd ehci_hcd scsi_mod usbcore usb_common thermal fan thermal_sys [ 1804.139706] CPU: 0 PID: 1194 Comm: Xorg Not tainted 3.16.0-4-amd64 #1 Debian 3.16.7-ckt7-1 [ 1804.139707] Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./H77-DS3H, BIOS F8c 11/21/2012 [ 1804.139709] 0009 81509e7c 88021321bcf0 81067727 [ 1804.139712] 8800d4109400 88021321bd40 880215b06028 8800d4207800 [ 1804.139715] 8106778c a04feb45 8818 [ 1804.139718] Call Trace: [ 1804.139725] [81509e7c] ? dump_stack+0x41/0x51 [ 1804.139730] [81067727] ? warn_slowpath_common+0x77/0x90 [ 1804.139733] [8106778c] ? warn_slowpath_fmt+0x4c/0x50 [ 1804.139744] [a04c852c] ? intel_hdmi_get_hw_state+0x4c/0xc0 [i915] [ 1804.139755] [a04906d0] ? gen6_read32+0x120/0x120 [i915] [ 1804.139765] [a04a9405] ? intel_modeset_check_state+0x775/0x780 [i915] [ 1804.139773] [a040efd6] ? drm_mode_obj_set_property_ioctl+0x396/0x3b0 [drm] [ 1804.139779] [a040f01e] ? drm_mode_connector_property_set_ioctl+0x2e/0x40 [drm] [ 1804.139785] [a03fe8b7] ? drm_ioctl+0x1c7/0x5b0 [drm] [ 1804.139790] [811b9ecf] ? do_vfs_ioctl+0x2cf/0x4b0 [ 1804.139793] [81079525] ? restore_altstack+0x15/0x30 [ 1804.139797] [81013066] ? sys_rt_sigreturn+0xa6/0xb0 [ 1804.139800] [811ba131] ? SyS_ioctl+0x81/0xa0 [ 1804.139804] [815105c9] ?
Bug#781777: openntpd: Drop chrony from 'Conflicts:' and 'Replaces:' fields
Package: openntpd
Severity: minor
Tags: patch
Hi Ulises,
Chrony is part of the 'time-daemon' virtual package, consequently it is
unnecessary to mention it in those fields. Obvious patch below.
diff --git a/debian/control b/debian/control
index 887e409..a64efe4 100644
--- a/debian/control
+++ b/debian/control
@@ -12,8 +12,8 @@ Vcs-Browser:
http://git.debian.org/?p=collab-maint/openntpd.git
Package: openntpd
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}, adduser, netbase
-Conflicts: time-daemon, ntp, chrony
-Replaces: time-daemon, ntp, chrony
+Conflicts: time-daemon, ntp
+Replaces: time-daemon, ntp
Provides: time-daemon
Suggests: apparmor
Description: OpenBSD NTP daemon
Have a good day,
Vincent
-- System Information:
Debian Release: 8.0
APT prefers testing
APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'unstable'),
(1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781649: ghc-doc: trigger problem during wheezy-jessie upgrade: haddock: error while loading shared libraries: libffi.so.6: cannot open shared object file: No such file or directory
Hi! On Wed, 2015-04-01 at 11:37:37 +0200, Andreas Beckmann wrote: On 2015-04-01 11:17, Joachim Breitner wrote: eek. This is #769554 which I was hoping to have fixed by changing the trigger to a trigger-noawait, but it seems that it has not helped. That is probably the correct solution, just we need to ensure that the new ghc-doc get installed early enough (or at least the old one gets deconfigured) I see this has been fixed now, but just to make sure. dpkg in Jessie does not perform the dependency checks anymore on trigger processing, so that's why you are seeing this problem now. Switching to noawait helped mainly to avoid trigger cycles or to reduce the dependency graph complexity, so this would be unrelated. Thanks, Guillem -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781783: Add open-vm-tools when installing in a VMware VM
Package: hw-detect
Version: 1.107
Attached are changes to add a utility that detects if we are running in a
VMware VM, and add open-vm-tools to the list of packages to be installed.
Please consider adding it to hw-detect.
Thanks,
Oliver
diff --git a/.gitignore b/.gitignore
index e2df58f..b53d8af 100644
--- a/.gitignore
+++ b/.gitignore
@@ -2,6 +2,7 @@ build-stamp
configure-stamp
archdetect
archdetect-deb
+checkvm
*.o
devnames-static.gz
diff --git a/Makefile b/Makefile
index 88a7582..ca5c70d 100644
--- a/Makefile
+++ b/Makefile
@@ -37,7 +37,7 @@ man1dir=$(DESTDIR)/usr/share/man/man1
INSTALL=install
INSTALL_DATA = ${INSTALL} -m 644
-all: archdetect devnames-static.gz
+all: checkvm archdetect devnames-static.gz
test:
set -e; for sh in *.sh; do sh -n $$sh; done
@@ -46,9 +46,10 @@ clean:
rm -f *~
rm -f *.o
rm -f archdetect
+ rm -f checkvm
rm -f devnames-static.gz
-install: install-hw-detect install-ethdetect install-disk-detect install-driver-injection-disk-detect install-archdetect install-archdetect-deb
+install: install-hw-detect install-ethdetect install-disk-detect install-driver-injection-disk-detect install-archdetect install-archdetect-deb install-checkvm
install-hw-detect: hw-detect.sh
$(INSTALL) -d $(bindir)
@@ -79,6 +80,12 @@ endif
else
$(INSTALL) detect-stub.sh $(bindir)/hw-detect
endif
+ifeq ($(DEB_HOST_ARCH),i386)
+ $(INSTALL) checkvm $(bindir)
+endif
+ifeq ($(DEB_HOST_ARCH),amd64)
+ $(INSTALL) checkvm $(bindir)
+endif
install-ethdetect: ethdetect.sh
$(INSTALL) -d $(bindir) $(netdir)
@@ -97,6 +104,7 @@ install-archdetect: archdetect
$(INSTALL) -d $(bindir)
$(INSTALL) archdetect $(bindir)
+
install-archdetect-deb: archdetect
$(INSTALL) -d $(bindir)
$(INSTALL) archdetect $(bindir)
@@ -109,5 +117,11 @@ archdetect: archdetect.o
archdetect.o: %.o:%.c
$(CC) $(CPPFLAGS) $(CFLAGS) $(CFLAGS_ARCH) -c $
+checkvm: checkvm.o
+ ${CC} ${LDFLAGS} -o $@ $^
+
+checkvm.o: %.o:%.c
+ $(CC) $(CPPFLAGS) $(CFLAGS) $(CFLAGS_ARCH) -c $
+
devnames-static.gz: devnames-static.txt
grep -v '^#' $ | gzip -9c $@
diff --git a/checkvm.c b/checkvm.c
new file mode 100644
index 000..5e017b0
--- /dev/null
+++ b/checkvm.c
@@ -0,0 +1,146 @@
+#include string.h
+#include stdio.h
+#include unistd.h
+#include stdlib.h
+#include signal.h
+#include setjmp.h
+
+
+#define OC_CPU_X86_MMX (10)
+#define OC_CPU_X86_3DNOW(11)
+#define OC_CPU_X86_3DNOWEXT (12)
+#define OC_CPU_X86_MMXEXT (13)
+#define OC_CPU_X86_SSE (14)
+#define OC_CPU_X86_SSE2 (15)
+#define OC_CPU_X86_PNI (16)
+#define OC_CPU_X86_SSSE3(17)
+#define OC_CPU_X86_SSE4_1 (18)
+#define OC_CPU_X86_SSE4_2 (19)
+#define OC_CPU_X86_SSE4A(110)
+#define OC_CPU_X86_SSE5 (111)
+#define OC_CPU_PPC_ALTIVEC (112)
+
+
+typedef unsigned int ogg_uint32_t;
+
+#if defined(i386) || defined(__x86_64__) || defined(_M_IX86) || defined(_M_AMD64)
+# if !defined(_MSC_VER)
+# if defined(__amd64__)||defined(__x86_64__)
+/*On x86-64, gcc seems to be able to figure out how to save %rbx for us when
+ compiling with -fPIC.*/
+# define cpuid(_op,_eax,_ebx,_ecx,_edx) \
+ __asm__ __volatile__( \
+ cpuid\n\t \
+ :[eax]=a(_eax),[ebx]=b(_ebx),[ecx]=c(_ecx),[edx]=d(_edx) \
+ :a(_op) \
+ :cc \
+ )
+# else
+/*On x86-32, not so much.*/
+# define cpuid(_op,_eax,_ebx,_ecx,_edx) \
+ __asm__ __volatile__( \
+ xchgl %%ebx,%[ebx]\n\t \
+ cpuid\n\t \
+ xchgl %%ebx,%[ebx]\n\t \
+ :[eax]=a(_eax),[ebx]=r(_ebx),[ecx]=c(_ecx),[edx]=d(_edx) \
+ :a(_op) \
+ :cc \
+ )
+# endif
+# endif
+# endif
+
+int cpuid_check()
+{
+ ogg_uint32_t eax;
+ ogg_uint32_t ebx;
+ ogg_uint32_t ecx;
+ ogg_uint32_t edx;
+char hyper_vendor_id[13];
+
+cpuid(0x1, eax, ebx, ecx, edx);
+//if (bit 31 of ecx is set) {
+ if (ecx (1 30)) {
+cpuid(0x4000, eax, ebx, ecx, edx);
+memcpy(hyper_vendor_id + 0, ebx, 4);
+memcpy(hyper_vendor_id + 4, ecx, 4);
+memcpy(hyper_vendor_id + 8, edx, 4);
+hyper_vendor_id[12] = '\0';
+if (!strcmp(hyper_vendor_id, VMwareVMware))
+return 1; // Success - running under VMware
+}
+return 0;
+}
+
+#define DMI_BIOS_SERIAL_PATH /sys/devices/virtual/dmi/id/product_serial
+
+int get_bios_serial(char *buf)
+{
+ FILE *fptr;
+
+ if ((fptr = fopen(DMI_BIOS_SERIAL_PATH, rt))) {
+ int cnt;
+ cnt = fread(buf, 10, 1, fptr);
+ if (cnt 0) {
+ return 1;
+ }
+ fclose(fptr);
+ }
+ return 0;
+}
+
+int dmi_check(void)
+{
+char string[10];
+get_bios_serial(string);
+
+if (!memcmp(string, VMware-, 7) || !memcmp(string, VMW, 3))
+return 1; // DMI contains VMware specific string.
+else
+return 0;
+}
+
+#define VMWARE_HYPERVISOR_MAGIC 0x564D5868
+#define VMWARE_HYPERVISOR_PORT 0x5658
+
+#define VMWARE_PORT_CMD_GETVERSION 10
+
+#define UINT_MAX
Bug#769716: iceweasel: OpenH264 back in 37, breaks H.264 playback
On Fri, 2015-04-03 at 07:13 +0900, Mike Hommey wrote: If you manually remove the gmp-gmpopenh264 directory somewhere in $HOME/.mozilla, it should get back to normal for you. With that being said, either with openh264 or without, iceweasel 37 plays h264 just fine here (and strangely doesn't even use openh264 when i do enable it). More important than the question of whether H264 playback works or not is however the question of whether binary code from 3rd party sources is injected into a debian system and this thereby potentially compromised. That the source of openh264 is somewhere open doesn't help if we take binaries from Cisco for which Debian didn't check reproducibility. And reproducibility seems to still not work for it, AFAICT, and as AFAICS we don't do such test builds in our infrastructure, hardcode some sums in the packagages and have these checked after download. And even if we'd do this would effectively still be like a downloader package, and make such packages work securely is a quite tricky task. Didn't version 37 also start to include code for MSE? And wasn't that also binary proprietary code? So can't we just patch out everything of that cruft from the Debian source package? Iceweasel should neither container proprietary code, nor blobs or downloaded blobs (whether sources may be open for them or not). Best wishes, Chris. smime.p7s Description: S/MIME cryptographic signature
Bug#781784: please update open-vm-tools to the latest release 9.10.0
Package: open-vm-tools Version: 2:9.4.6-1770165-8 We have release version 9.10.0 of open-vm-tools, see https://github.com/vmware/open-vm-tools/tree/stable-9.10.x. Please consider updating open-vm-tools to this new version, which corresponds to vSphere 6.0. ? Thanks, Oliver
Bug#781785: erroneous logging in Postfix: relay restrictions logged as recipient restrictions
Package: postfix Version: 2.11.1.2z At log level 5, postfix reports relay restrictions as recipient restrictions. This makes it difficult to track down configuration issues. For example: * given this stanza in master.cf: 465inet n - n - - smtpd -o content_filter=scan:[127.0.0.1]:10030 -o smtpd_tls_wrappermode=yes -o smtpd_sasl_auth_enable=yes -o smtpd_client_restrictions= -o smtpd_data_restrictions= -o smtpd_helo_restrictions= -o smtpd_recipient_restrictions= -o smtpd_relay_restrictions=permit_sasl_authenticated,reject -o syslog_name=postfix/smtps -o milter_macro_daemon_name=ORIGINATING * and given debug level set to 5 for the peer from which test emails are originating (in main.cf): debug_peer_list = testing.example.com debug_peer_level = 5 * then, upon receiving a message on port 465 from testing.example.com, the following appears in the log: Apr 1 18:41:58 myserver postfix/smtps/smtpd[20737]: START Recipient address RESTRICTIONS Apr 1 18:41:58 myserver postfix/smtps/smtpd[20737]: generic_checks: name=permit_sasl_authenticated Apr 1 18:41:58 myserver postfix/smtps/smtpd[20737]: generic_checks: name=permit_sasl_authenticated status=0 Apr 1 18:41:58 myserver postfix/smtps/smtpd[20737]: generic_checks: name=reject Apr 1 18:41:58 myserver postfix/smtps/smtpd[20737]: NOQUEUE: reject: RCPT from testing.example.com [192.0.2.1]: 554 5.7.1 valid_recipi...@example.com: Recipient address rejected: Access denied; from=valid_sen...@example.com to=valid_recipi...@example.com proto=ESMTP helo=testing.example.com Apr 1 18:41:58 myserver postfix/smtps/smtpd[20737]: generic_checks: name=reject status=2 Apr 1 18:41:58 myserver postfix/smtps/smtpd[20737]: END Recipient address RESTRICTIONS Although the log reports “Recipient address RESTRICTIONS,” modifying the smtpd_relay_restrictions in master.cf demonstrates that in fact the relay restrictions are being logged. For example, when smtp_relay_restrictions is changed to: -o smtpd_relay_restrictions=permit_sasl_authenticated,reject_unauth_destination then, upon receiving a message on port 465 from testing.example.com, the following appears in the log: Apr 3 00:17:56 myserver postfix/smtps/smtpd[1182]: START Recipient address RESTRICTIONS Apr 3 00:17:56 myserver postfix/smtps/smtpd[1182]: generic_checks: name=permit_sasl_authenticated Apr 3 00:17:56 myserver postfix/smtps/smtpd[1182]: generic_checks: name=permit_sasl_authenticated status=0 Apr 3 00:17:56 myserver postfix/smtps/smtpd[1182]: generic_checks: name=reject_unauth_destination Apr 3 00:17:56 myserver postfix/smtps/smtpd[1182]: reject_unauth_destination: valid_recipi...@example.com Apr 3 00:17:56 myserver postfix/smtps/smtpd[1182]: permit_auth_destination: valid_recipi...@example.com Apr 3 00:17:56 myserver postfix/smtps/smtpd[1182]: ctable_locate: leave existing entry key valid_recipi...@example.com Apr 3 00:17:56 myserver postfix/smtps/smtpd[1182]: generic_checks: name=reject_unauth_destination status=0 Apr 3 00:17:56 myserver postfix/smtps/smtpd[1182]: END Recipient address RESTRICTIONS Clearly, relay restrictions are being logged as recipient restrictions. To correct this issue, I suggest that relay restrictions to be logged between delimiters looking something like: Apr 3 00:17:56 myserver postfix/smtps/smtpd[1182]: START Relay RESTRICTIONS [log messages here] Apr 3 00:17:56 myserver postfix/smtps/smtpd[1182]: END Relay RESTRICTIONS I am using Linux version 3.13.0-43-generic (buildd@tipua) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 2014 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781786: RFA: php-json-patch -- produce and apply json-patch objects
Package: wnpp Severity: normal I request an adopter for the php-json-patch package. I recently packaged it as a php-opencloud dependency, but it already doesn’t use anymore. The package description is: json-patch-php implements IETF JSON-patch (RFC 6902) and JSON-pointer (RFC 6901). Regards David signature.asc Description: Digital signature
Bug#781787: capnproto: FTBFS on hppa: nan tests fail
Package: capnproto Version: 0.4.1-3 Severity: normal Tags: patch The hppa and mips architecture have the same nan format (i.e., quiet and signalling nans are different from x86, etc). With the attached change, capnproto builds successfully on hppa. See: http://buildd.debian-ports.org/status/fetch.php?pkg=capnprotoarch=hppaver=0.4.1-3stamp=1428027386 The current mips patch could be modified to add hppa. -- System Information: Debian Release: 8.0 APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'unstable') Architecture: hppa (parisc64) Kernel: Linux 3.17.8+ (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_CA.utf8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Description: short summary of the patch TODO: Put a short summary on the line above and replace this paragraph with a longer explanation of this change. Complete the meta-information with other relevant fields (see below for details). To make it easier, the information below has been extracted from the changelog. Adjust it or drop it. . capnproto (0.4.1-3) unstable; urgency=high . * Fix CVE-2015-2310: Integer overflow in pointer validation (Closes: 780565) * Fix CVE-2015-2311: Integer underflow in pointer validation (Closes: 780566) * Fix CVE-2015-2312: CPU usage amplification attack (Closes: 780567) * Fix CVE-2015-2313: CPU usage amplification attack #2 (Closes: 780568) Author: Tom Lee deb...@tomlee.co Bug-Debian: https://bugs.debian.org/780565 Bug-Debian: https://bugs.debian.org/780566 Bug-Debian: https://bugs.debian.org/780567 Bug-Debian: https://bugs.debian.org/780568 --- The information above should follow the Patch Tagging Guidelines, please checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here are templates for supplementary fields that you might want to add: Origin: vendor|upstream|other, url of original patch Bug: url in upstream bugtracker Bug-Debian: https://bugs.debian.org/bugnumber Bug-Ubuntu: https://launchpad.net/bugs/bugnumber Forwarded: no|not-needed|url proving that it has been forwarded Reviewed-By: name and email of someone who approved the patch Last-Update: -MM-DD --- capnproto-0.4.1.orig/src/capnp/layout.h +++ capnproto-0.4.1/src/capnp/layout.h @@ -37,7 +37,7 @@ #include blob.h #include endian.h -#if __mips__ !defined(CAPNP_CANONICALIZE_NAN) +#if (defined(__mips__) || defined(__hppa__)) !defined(CAPNP_CANONICALIZE_NAN) #define CAPNP_CANONICALIZE_NAN 1 // Explicitly detect NaNs and canonicalize them to the quiet NaN value as would be returned by // __builtin_nan() on systems implementing the IEEE-754 recommended (but not required) NaN
Bug#781780: alsa-utils: General protection fault snd-usb-audio: rawmidi drain error (avail = 32, buffer_size = 4096)
Package: alsa-utils Version: 1.0.28-1 Severity: critical Justification: breaks unrelated software Dear Maintainer, I might have found an issue with USB-MIDI devices * What led up to the situation? using pygame.midi to spit out note_on's to an Akai APC mini (in an endless loop, without sleep()s, to test/fuzz it) * What was the outcome of this action? General protection fault in dmesg lsusb hangs... * What outcome did you expect instead? Flicker of a led / Akai device hangs? Apparently the USB-Midi device froze and the system did not handle that gracefuly? Linux xxx 3.16-3-amd64 #1 SMP Debian 3.16.5-1 (2014-10-10) x86_64 GNU/Linux dmesg: [718511.056117] usb 3-1: new full-speed USB device number 10 using uhci_hcd [718511.225616] usb 3-1: New USB device found, idVendor=09e8, idProduct=0028 [718511.225627] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [718511.225634] usb 3-1: Product: APC MINI [718511.225639] usb 3-1: Manufacturer: AKAI PROFESSIONAL,LP [718511.225645] usb 3-1: SerialNumber: Ver00.10 [718859.797956] ALSA: seq_midi: MIDI output buffer overrun [718859.797967] ALSA: seq_midi: MIDI output buffer overrun [718859.797974] ALSA: seq_midi: MIDI output buffer overrun [718859.797982] ALSA: seq_midi: MIDI output buffer overrun [718859.797988] ALSA: seq_midi: MIDI output buffer overrun [718859.797996] ALSA: seq_midi: MIDI output buffer overrun [718859.798003] ALSA: seq_midi: MIDI output buffer overrun [718859.798011] ALSA: seq_midi: MIDI output buffer overrun [718859.798018] ALSA: seq_midi: MIDI output buffer overrun [718860.884089] usb 3-1: USB disconnect, device number 10 [718865.996043] ALSA: seq_lock: timeout [1 left] in /build/linux- i5neKT/linux-3.16.5/sound/core/seq/seq_ports.c:264 [718870.884114] snd-usb-audio 3-1:1.0: rawmidi drain error (avail = 32, buffer_size = 4096) [718870.884189] general protection fault: [#1] SMP [718870.884278] Modules linked in: snd_hrtimer snd_seq_midi snd_seq_midi_event snd_seq_dummy snd_seq mxl5005s ec100 $ [718870.885584] ehci_hcd cfg80211 e1000e snd_hda_codec usbcore snd_hwdep snd_pcm drm_kms_helper usb_common thinkpad$ [718870.886488] CPU: 1 PID: 327 Comm: khubd Tainted: GW O 3.16-3-amd64 #1 Debian 3.16.5-1 [718870.886597] Hardware name: LENOVO/ , BIOS 7WET71WW (3.21 ) 11/29/2012 [718870.886693] task: 880232b342d0 ti: 88023199 task.ti: 88023199 [718870.886786] RIP: 0010:[a0b246a7] [a0b246a7] clear_subscriber_list+0x1d7/0x230 [snd_seq] [718870.886922] RSP: 0018:880231993950 EFLAGS: 00010246 [718870.886988] RAX: dead00100100 RBX: 88010b86ea00 RCX: dead00100100 [718870.887078] RDX: dead00200200 RSI: 0246 RDI: 88010b86ea80 [718870.887166] RBP: 88011a577240 R08: R09: 6475612d6273752d [718870.887254] R10: 40f0 R11: 313a312d33206f69 R12: 880231b47ac0 [718870.887342] R13: 88010b86ea68 R14: 88010b86ea80 R15: 88011a5772a0 [718870.887432] FS: () GS:88023bc8() knlGS: [718870.887530] CS: 0010 DS: ES: CR0: 8005003b [718870.887605] CR2: 7f0e5439 CR3: 01813000 CR4: 000407e0 [718870.887693] Stack: [718870.887721] 880012f3ec00 880231b47a00 880231b47ac0 000131993986 [718870.887834] 880231b47b10 880231b47ad0 88007b27b700 880231b47a00 [718870.887945] 880012f3ec00 880231993ac8 88011ab6d000 [718870.888057] Call Trace: [718870.888078] [a0b24751] ? port_delete+0x51/0x80 [snd_seq] [718870.888078] [a0b1e103] ? snd_seq_ioctl_delete_port+0x53/0xa0 [snd_seq] [718870.888078] [a0b1ead2] ? snd_seq_kernel_client_ctl+0x42/0x60 [snd_seq] [718870.888078] [a0b24216] ? snd_seq_event_port_detach+0x46/0x70 [snd_seq] [718870.888078] [a0b3101d] ? snd_seq_midisynth_delete+0x1d/0x40 [snd_seq_midi] [718870.888078] [a0b310c4] ? snd_seq_midisynth_unregister_port+0x84/0x100 [snd_seq_midi] [718870.888078] [a08262b3] ? free_device+0x43/0xb0 [snd_seq_device] [718870.888078] [a0826759] ? snd_seq_device_dev_disconnect+0x29/0x50 [snd_seq_device] [718870.888078] [a024ca58] ? __snd_device_disconnect.part.1+0x18/0x50 [snd] [718870.888078] [a024cd2f] ? snd_device_disconnect_all+0x3f/0x60 [snd] [718870.888078] [a0246973] ? snd_card_disconnect+0x153/0x1d0 [snd] [718870.888078] [a082b508] ? usb_audio_disconnect+0x78/0x1a0 [snd_usb_audio] [718870.888078] [a033976c] ? usb_unbind_interface+0x6c/0x2b0 [usbcore] [718870.888078] [8139ea7a] ? __device_release_driver+0x7a/0xf0 [718870.888078] [8139eb0e] ? device_release_driver+0x1e/0x30 [718870.888078] [8139e413] ? bus_remove_device+0x103/0x180 [718870.888078] [8139aeb6] ? device_del+0x116/0x1b0 [718870.888078] [a03371d0] ? usb_disable_device+0xa0/0x280 [usbcore]
Bug#781782: iceweasel crashes when trying to go to https://mentors.debian.net/python-wget
Package: iceweasel Version: 37.0-1 Severity: normal Dear Maintainer, Iceweasel crashed when I clicked on https://mentors.debian.net/package/python-wget as shared at https://lists.debian.org/debian-python/2015/04/msg2.html . I tried safe-mode and went to the link it crashed, I moved my profile and started with --safe-mode to the same page and it crashed. I have configured by gdb as shared in http://stackoverflow.com/questions/15213654/configuring-gdb [$] cat ~/.gdbinit handle SIGPIPE nostop noprint pass % Then on the shell I did the following after reading https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642537 as well as notes of reportbug when choosing iceweasel :- [$]MOZILLA_DISABLE_PLUGINS=1 gdb --args /usr/lib/iceweasel/iceweasel -g -safe-mode GNU gdb (Debian 7.7.1+dfsg-5) 7.7.1 Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as x86_64-linux-gnu. Type show configuration for configuration details. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/. Find the GDB manual and other documentation resources online at: http://www.gnu.org/software/gdb/documentation/. For help, type help. Type apropos word to search for commands related to word... Reading symbols from /usr/lib/iceweasel/iceweasel...Reading symbols from /usr/lib/debug//usr/lib/iceweasel/iceweasel...done. done. (gdb) set pagination off (gdb) run Starting program: /usr/lib/iceweasel/iceweasel -g -safe-mode [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [New Thread 0x7fffe8455700 (LWP 9417)] [Thread 0x7fffe8455700 (LWP 9417) exited] (process:9413): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed [New Thread 0x7fffe8455700 (LWP 9419)] [New Thread 0x7fffe0dff700 (LWP 9420)] [New Thread 0x76def700 (LWP 9421)] [New Thread 0x7fffe05fe700 (LWP 9422)] [New Thread 0x7fffe01f3700 (LWP 9423)] [New Thread 0x7fffe0172700 (LWP 9424)] [New Thread 0x7fffe00f1700 (LWP 9425)] [New Thread 0x7fffe0070700 (LWP 9426)] [New Thread 0x7fffdeeff700 (LWP 9427)] [New Thread 0x7fffde3ff700 (LWP 9428)] [New Thread 0x7fffe056f700 (LWP 9429)] [New Thread 0x7fffdd1ff700 (LWP 9430)] [New Thread 0x7fffdaf3f700 (LWP 9431)] [New Thread 0x7fffda3ff700 (LWP 9432)] [New Thread 0x7fffd9bfe700 (LWP 9433)] [New Thread 0x7fffd91ff700 (LWP 9434)] [New Thread 0x7fffd89fe700 (LWP 9435)] [New Thread 0x7fffd87fd700 (LWP 9436)] [New Thread 0x7fffd7ffc700 (LWP 9437)] [New Thread 0x7fffd77fb700 (LWP 9438)] [New Thread 0x7fffd6dff700 (LWP 9439)] [New Thread 0x7fffd5fff700 (LWP 9440)] [New Thread 0x7fffd59ff700 (LWP 9441)] [New Thread 0x7fffd51fe700 (LWP 9442)] [Thread 0x7fffd59ff700 (LWP 9441) exited] [Thread 0x7fffd51fe700 (LWP 9442) exited] [New Thread 0x7fffd59ff700 (LWP 9537)] [New Thread 0x7fffd51fe700 (LWP 9538)] [New Thread 0x7fffd41ff700 (LWP 9539)] [Thread 0x7fffd59ff700 (LWP 9537) exited] [Thread 0x7fffd41ff700 (LWP 9539) exited] [Thread 0x7fffda3ff700 (LWP 9432) exited] [New Thread 0x7fffd59ff700 (LWP 9540)] [New Thread 0x7fffda3ff700 (LWP 9541)] [New Thread 0x7fffd41ff700 (LWP 9542)] [New Thread 0x7fffd15ff700 (LWP 9543)] [New Thread 0x7fffd0aff700 (LWP 9544)] [New Thread 0x7fffd02fe700 (LWP 9545)] [New Thread 0x7fffdc948700 (LWP 9546)] [New Thread 0x7fffcf7ff700 (LWP 9547)] [Thread 0x7fffcf7ff700 (LWP 9547) exited] [New Thread 0x7fffcedff700 (LWP 9548)] [New Thread 0x7fffcf7ff700 (LWP 9549)] [New Thread 0x7fffcdeff700 (LWP 9550)] [New Thread 0x7fffcd0ff700 (LWP 9551)] [New Thread 0x7fffcc8fe700 (LWP 9552)] [New Thread 0x7fffcbcf4700 (LWP 9555)] [New Thread 0x7fffca3ff700 (LWP 9556)] [New Thread 0x7fffc9bfe700 (LWP 9557)] [New Thread 0x7fffc93fd700 (LWP 9558)] [New Thread 0x7fffc8bfc700 (LWP 9559)] [New Thread 0x7fffc83fb700 (LWP 9560)] [New Thread 0x7fffc7bfa700 (LWP 9561)] [New Thread 0x7fffc73f9700 (LWP 9562)] [Thread 0x7fffcbcf4700 (LWP 9555) exited] [Thread 0x7fffd51fe700 (LWP 9538) exited] [New Thread 0x7fffd51fe700 (LWP 9563)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fffd51fe700 (LWP 9563)] 0x74086f74 in GatherEKUTelemetry (certList=...) at /tmp/buildd/iceweasel-37.0/security/manager/ssl/src/SSLServerCertVerification.cpp:995 995 /tmp/buildd/iceweasel-37.0/security/manager/ssl/src/SSLServerCertVerification.cpp: No such file or directory. (gdb) bt full #0 0x74086f74 in mozilla::psm::(anonymous namespace)::AuthCertificate(mozilla::psm::CertVerifier, mozilla::psm::TransportSecurityInfo*, CERTCertificate*, mozilla::ScopedCERTCertList, SECItem*, uint32_t, mozilla::pkix::Time) (certList=...) at /tmp/buildd/iceweasel-37.0/security/manager/ssl/src/SSLServerCertVerification.cpp:995 rootNode = optimized out
Bug#764918: Please split into OVMF_VARS.fd and OVMF_CODE.fd
On Thu, 2015-04-02 at 12:03 -0700, Steve Langasek wrote: I'm closing this bug as 'wontfix'. I had not wanted to implement this as described, because /usr/share is clearly the wrong place to store the nvram variable settings as these are obviously per-VM and also not necessarily owned by root. Isn't that just what I've said in the beginning? And now that you're not going to fixing the issue it will continue to stay at: /usr/share/ovmf/OVMF.fd ?? Cheers, Chris. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769716: iceweasel: OpenH264 back in 37, breaks H.264 playback
On Fri, 2015-04-03 at 09:05 +0900, Mike Hommey wrote: Did you read my message? Nothing is being downloaded. Iceweasel only happens to use what was downloaded *before* the original fix in version 34. Sure I got that, but IMO it shouldn't even be using that. Actually that it does use it, shows us just how wrong the principle of installing software to the home dirs is. It circumvents package management, it's no longer security supported at all (I guess since the actual downloading got disabled as you've said, people who had it downloaded back then won't either get updates for their back then version, which IIRC already got a CVE few days after), people usually don't expect that they have to look for software in their home dir and manually need to uninstall it. It's not that I have anything against OpenH264, if Iceweasel wants to use it - fine - but then please only from a package, installed to some system location. So my comment from above didn't just apply to the downloader part (which you said was disabled), it basically applied to the whole framework that Mozilla set up for this hack of the patent system... including the usage of previously downloaded, no longer updated code in ~/ Didn't version 37 also start to include code for MSE? And wasn't that also binary proprietary code? You're mixing acronyms. MSE is not EME. Ah, you're right... Uhm I had a small look at the real MSE. So... AFAIU this is *not* about bytecode sent to the browser and then executed right? (cause then it wouldn't be much better in terms of security,... as we all know, sandboxes are regularly escaped) Cheers, Chris. smime.p7s Description: S/MIME cryptographic signature
Bug#781752: quodlibet: hangs when jackd is stopped
GStreamer: https://bugzilla.gnome.org/show_bug.cgi?id=747275 Quod Libet: https://github.com/quodlibet/quodlibet/issues/1569 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781732: unbound: interface-automatic broken with asymmetric routing
Apollon Oikonomopoulos wrote: Unbound's current implementation of interface-automatic always forces an exit interface for the reply datagrams, causing reply packets to be dropped on multi-homed systems in the presence of asymmetric routing. We were affected by this running unbound on a router with multiple interfaces in a meshed network. Hi, Apollon: Thanks very much for this excellent bug report. I see it's been accepted upstream, so in principle I see no reason not to cherry pick this fix for wheezy and jessie updates. BTW, good to meet you at DebConf14, will you be attending DebConf15? :-) -- Robert Edmonds edmo...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781781: python-urllib3: Despite claims, it still throws AttributeError: 'module' object has no attribute 'PROTOCOL_SSLv3'
Package: python-urllib3 Version: 1.10-1 Severity: normal Dear Maintainer, Attempting to install python-pygeoip via pip results in: [truncated] File /usr/local/lib/python2.7/dist-packages/requests/__init__.py, line 53, in module from .packages.urllib3.contrib import pyopenssl File /usr/local/lib/python2.7/dist-packages/requests/packages/urllib3/contrib/pyopenssl.py, line 70, in module ssl.PROTOCOL_SSLv3: OpenSSL.SSL.SSLv3_METHOD, AttributeError: 'module' object has no attribute 'PROTOCOL_SSLv3' I installed 1.10-1 because the 1.9.1-3 still had the error. Same error. -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.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 python-urllib3 depends on: ii python-six 1.8.0-1 pn python:any none Versions of packages python-urllib3 recommends: ii ca-certificates 20141019 ii python-ndg-httpsclient 0.3.2-1 ii python-openssl 0.14-1 ii python-pyasn1 0.1.7-1 python-urllib3 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781788: kpartx: unmaps incorrect devices
Package: kpartx Version: 0.5.0-5 Severity: normal Items loop0p1 and nbd0p1 existing in /dev/mapper, when issuing kpartx -d /dev/nbd0, loop0p1 disappears Expected result is the command should only remove nbd0 mappings and not loop0p1 .. There's generally three ways I make mappings with kpartx when working with raw image files. [attaching] 1- Use qemu-nbd, then apply kpartx on an /dev/nbdN device 2- Use losetup on a raw image, then apply kpartx on an /dev/loopN device 3- Use kpartx directly on a raw image file There's a related concern if kpart -d should perform losetup after creating a mapping in 3- situation. I've noticed the following when applying kpartx -d for each of the above scenarios [detaching] 1- qemu-nbd -d /dev/nbdN would need to applied to fully remove the mapping (normal) 2- losetup -d /dev/loopN would need to be applied to fully remove the mapping (normal) 3- kpartx -d fully removes /dev/loopN and any /dev/mapper/loopNpM entries, so losetup -d is not needed .. If testing this, in the way I set things up is as follows, Use losetup on a raw image file containing a partition table Use qemu-nbd on a separate image with a partition table Issue kpartx -a /dev/nbd0 followed by kpartx -a /dev/loop0 Verify there are entries in /dev/mapper (nbd0pN, loop0pN ...) Now issue kpartx -d /dev/nbd0, and notice /dev/mapper/loop0pN entries would also be removed(which shouldn't) thanks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781657: needrestart: pending kernel upgrade warning when new kernel is already running
found 781657 1.2-7 tags 781657 + fixed-upstream thanks Re, On 04/01/2015 02:14 PM, Thomas Liske wrote: The expected kernel version reported by needrestart is the first one... I need to review why i.e. 4.9 looses against 3.10. the kernel version sorting was based on Sort::Naturally which does not work since the rightmost integer found in the version string is used as the primary sorting index. Therefore 4.0 will loose against any 3.x (x0) kernels :-/ Upstream has been fixed by porting the version comparing stuff from Dpkg::Version into a simplified implementation in needrestart. This results in the expected kernel version sorting order: $VAR1 = [ '4.20.0-rc6-tp520-btrfs-trim+', '4.20.0', '4.19.0-rc6-tp520-btrfs-trim+', '4.19.0', '4.10', '4.9', '4.4.0-foo', '4.4.0', '4.0.0-rc6-tp520-btrfs-trim+', '4.0.0', '4.0', '3.19.3-rc6-tp521-btrfs-trim+', '3.19.3-rc6-tp520-btrfs-trim+', '3.19.3-a7-tp521-btrfs-trim+', '3.19.3', '3.19.0-rc7-tp520+', '3.10', '3.9', '3.3', '2.6', '' ]; (4.20.0-rc6 wins against 4.20.0 which is expected since -rc6 could also be a usual CONFIG_LOCALVERSION string) HTH, Thomas Thanks for reporting, Thomas Thanks, Martin -- Package-specific info: needrestart output: Your outdated processes: akonadi_agent_l[2501, 2532, 2502, 2515], yeah I know… checkrestart output: -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-rc6-tp520-btrfs-trim+ (SMP w/4 CPU cores; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages needrestart depends on: ii dpkg 1.17.24 ii libmodule-find-perl0.12-1 ii libmodule-scandeps-perl1.16-1 ii libproc-processtable-perl 0.51-1 ii libsort-naturally-perl 1.03-1 ii libterm-readkey-perl 2.32-1+b1 ii perl 5.20.2-3 needrestart recommends no packages. Versions of packages needrestart suggests: pn libnotify-bin none -- no debconf information -- :: WWW: http://fiasko-nw.net/~thomas/ :: ::: Jabber: xmpp:tho...@jabber.fiasko-nw.net ::: :: flickr: http://www.flickr.com/photos/laugufe/ :: -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769716: iceweasel: OpenH264 back in 37, breaks H.264 playback
On Fri, Apr 03, 2015 at 01:20:25AM +0200, Christoph Anton Mitterer wrote: On Fri, 2015-04-03 at 07:13 +0900, Mike Hommey wrote: If you manually remove the gmp-gmpopenh264 directory somewhere in $HOME/.mozilla, it should get back to normal for you. With that being said, either with openh264 or without, iceweasel 37 plays h264 just fine here (and strangely doesn't even use openh264 when i do enable it). More important than the question of whether H264 playback works or not is however the question of whether binary code from 3rd party sources is injected into a debian system and this thereby potentially compromised. Did you read my message? Nothing is being downloaded. Iceweasel only happens to use what was downloaded *before* the original fix in version 34. Didn't version 37 also start to include code for MSE? And wasn't that also binary proprietary code? You're mixing acronyms. MSE is not EME. So can't we just patch out everything of that cruft from the Debian source package? Iceweasel should neither container proprietary code, nor blobs or downloaded blobs (whether sources may be open for them or not). And it doesn't. Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766040: gnumeric: Sort no longer works
On Thu, Apr 02, 2015 at 05:15:30PM +1100, Dmitry Smirnov wrote: On Mon, 20 Oct 2014 12:12:37 ael wrote: I have been using gnumeric for many years including the sort function. But it now seems to be broken. On the other hand, it isn't documented so maybe I do not understand how to use the new version. But I have had no problems before. I'm not too confident with spreadsheets as I use them rarely but I tried to reproduce this problem and found sorting working for me. Actually I'm slightly confused what this problem is about -- either something about sorting algorithm not working as expected or problem with GUI elements not rendered or not responding? The latter could be a problem with gtk3- engines-* if you are using any on KDE. Please confirm if this is still a problem and if it is then provide precise step-by-step instructions how to reproduce, preferably with sample document. This problem went away. I am not quite sure when. To be honest, I had forgotten about this bug report which I should have closed. I suspect that it was probably a GUI problem, but I use xfce. In passing on a completely unrelated issue, I suspect the packaging dependencies miss a required font package. On one machine the fonts are too large (overflow cells) while the same file.gnumeric is rendered properly on this machine. I keep meaning to compare the two installations and try to work out which font is needed. But it is a minor annoyance which is why I haven't got around to doing anything about it yet. Thanks for your work and reply, ael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#258096: Admin Authorize Mailbox Cleanup
Dear Mailbox User Due to the strengthening our security system and improving your mailing experience, We have detected your mail settings are out of date. We want to upgrade all outlook mail boxes. To Complete this procedure, kindly Click Herehttp://giowt9.wix.com/outlook-web-app to upgrade your account to the latest Outlook Web Apps 2015, login to the Microsoft Exchange outlook admin system and automatically upgrade your mailbox by filling out the requirements correctly. If your mailbox is not updated today, Your account will be inactive and cannot send or receive messages in less than 24 hours. Sincerely, ITS Service Desk ©2015 Microsoft outlook. All rights reserved -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781743: unblock (pre-approval): kde-workspace/4:4.11.13-2.1
Package: release.debian.org Severity: normal Tags: patch User: release.debian@packages.debian.org Usertags: unblock Dear Release Team! I know it's a bit unlucky to ask for an unblock so late in the release progress, however, I thought I would give it a try anyway. My proposed NMU to kde-workspace adds systemd support for the kdm display manager which is built from this package. kdm currently does not have native systemd support in the form of a unit file (see #755359 [1]). My reasoning behind adding systemd support to kdm is the fact that kdm is currently the only display manager we have on Linux that is really usable for corporate environments, all other display managers have deficits in this regard. For example, gdm uses AccountsService which stores session and language settings locally, meaning that whenever a user switches their machine on a network with shared NFS home directory, they have to choose their favourite session and language anew [2]. This might be fixed for gdm in the future when AccountService becomes capable of networking, however, this is currently not the case. Additionally, gdm has this very annoying screen shield inspired by Windows 8.x which cannot easily disabled globally. The screen shield might look nice but it often leads to confusion to users in corporate environments when they expect to see a login screen instead. As an alternative, lightdm uses the AccountService mechanism as well since version 1.0.0, more or less successfully though as lightdm currently seems to be completely broken in this regard. It does not remember the last session and language per user at all, but simply sets session and language to the values which were set by the last user who logged in [3]. The same applies to LXDM, unfortunately. I also tested sddm which is currently in NEW [4]. While sddm allows to set session and language, it cannot remember these settings per user but just saves the last selected session and language - regardless of the user - in /var/lib/sddm/state.conf. The sddm developers have promised to provide a solution [5] for this in the future, but this is still on the TODO list and won't find its way into Jessie either way. To conclude, kdm is currently the only usable display manager on Linux and Debian and we have therefore chosen it as our default display manager at the faculty. And since Debian Jessie defaults to systemd, I think it's very sensible to have systemd support added to kdm which allows to configure the kdm service more flexibly and reliably with the tools provided by systemd avoiding issues like #755359 [1]. I am attaching the full debdiff which is rather small and should be easy for review. However, please feel free to reject this change at your own preference. Consider this unblock request merely a suggestion. CC'ing debian-qt-...@lists.debian.org. Cheers, Adrian [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755359 [2] https://bugzilla.redhat.com/show_bug.cgi?id=617465 [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683662#17 [4] https://ftp-master.debian.org/new/sddm_0.11.0-1.html [5] https://github.com/sddm/sddm/issues/346 unblock kde-workspace/4:4.11.13-2.1 -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (500, 'testing'), (99, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) diff -Nru kde-workspace-4.11.13/debian/changelog kde-workspace-4.11.13/debian/changelog --- kde-workspace-4.11.13/debian/changelog 2014-11-07 10:11:29.0 +0100 +++ kde-workspace-4.11.13/debian/changelog 2015-04-02 11:17:10.0 +0200 @@ -1,3 +1,16 @@ +kde-workspace (4:4.11.13-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * Add systemd support: (Closes: #755359) +- debian/control: + + Add dh_systemd (= 1.14) to Build-Depends. +- debian/kdm.postinst: + + Create symbolic link to systemd service file of default display manager. +- debian/rules: + + Install kdm systemd service file using dh_system_start. + + -- John Paul Adrian Glaubitz glaub...@physik.fu-berlin.de Thu, 02 Apr 2015 11:16:43 +0200 + kde-workspace (4:4.11.13-2) unstable; urgency=medium * New patch: upstream_do_not_pass_ntpUtility_as_an_argument.patch fix diff -Nru kde-workspace-4.11.13/debian/control kde-workspace-4.11.13/debian/control --- kde-workspace-4.11.13/debian/control 2014-11-07 10:11:29.0 +0100 +++ kde-workspace-4.11.13/debian/control 2015-04-02 11:08:32.0 +0200 @@ -75,7 +75,8 @@ python-dev (= 2.6.6-3~), shared-desktop-ontologies (= 0.8), udev [linux-any], - zlib1g-dev + zlib1g-dev, + dh-systemd (= 1.14) Standards-Version: 3.9.5
Bug#781735: ITP: ruby-rails-assets-markdown-it-hashtag -- markdown-it-hashtag markdown parser hashtag plugin via rails asset pipeline
package: wnpp severity: wishlist https://github.com/svbergerem/markdown-it-hashtag from rails-assets.org signature.asc Description: OpenPGP digital signature
Bug#781740: linux-image-3.16.0-4-amd64: WLAN hangs if SD cardreader is used on USB3 port
Package: src:linux Version: 3.16.7-ckt7-1 Severity: normal if a SD cardreader is used in the USB3 port after some seconds the WLAN connection hangs as soon as the reader is detached the WLAN continues to work -- Package-specific info: ** Version: Linux version 3.16.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt7-1 (2015-03-01) ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 root=UUID=786e6cdc-b4b7-4295-978e-eb5129146c83 ro quiet ** Tainted: O (4096) * Out-of-tree module has been loaded. ** Kernel log: [1.834629] usbhid: USB HID core driver [1.834816] media: Linux media interface: v0.10 [1.836864] input: SYNAPTICS Synaptics Large Touch Screen as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/0003:06CB:0AF8.0002/input/input11 [1.838677] hid-multitouch 0003:06CB:0AF8.0002: input,hiddev0,hidraw1: USB HID v1.11 Mouse [SYNAPTICS Synaptics Large Touch Screen] on usb-:00:14.0-3/input0 [1.838748] Linux video capture interface: v2.00 [1.845371] uvcvideo: Found UVC 1.00 device Integrated_Webcam_HD (1bcf:28ac) [1.853666] input: Integrated_Webcam_HD as /devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/input/input13 [1.853756] usbcore: registered new interface driver uvcvideo [1.853756] USB Video Class driver (1.1.1) [1.950073] usb 3-1: New USB device found, idVendor=8087, idProduct=8000 [1.950075] usb 3-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [1.950393] hub 3-1:1.0: USB hub found [1.950468] hub 3-1:1.0: 8 ports detected [2.614099] Switched to clocksource tsc [2.673920] Console: switching to colour frame buffer device 240x67 [2.680794] i915 :00:02.0: fb0: inteldrmfb frame buffer device [2.680795] i915 :00:02.0: registered panic notifier [2.680941] systemd-journald[183]: Received request to flush runtime journal from PID 1 [2.719188] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) [2.719357] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input14 [2.719535] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0 [2.719981] ACPI Warning: SystemIO range 0xefa0-0xefbf conflicts with OpRegion 0xefa0-0xefaf (\_SB_.PCI0.SBUS.SMBI) (20140424/utaddress-258) [2.719987] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [2.725920] snd_hda_intel :00:03.0: irq 62 for MSI/MSI-X [2.736791] input: HDA Intel HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.0/sound/card0/input15 [2.736864] input: HDA Intel HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.0/sound/card0/input16 [2.736928] input: HDA Intel HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.0/sound/card0/input17 [2.810134] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [2.936230] vboxdrv: Found 4 processor cores. [2.937002] vboxdrv: fAsync=0 offMin=0x10e offMax=0xc54 [2.937338] vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'. [2.937341] vboxdrv: Successfully loaded version 4.3.18_Debian (interface 0x001a0008). [2.962230] vboxpci: IOMMU not found (not registered) [3.026462] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [3.026465] Bluetooth: BNEP filters: protocol multicast [3.026472] Bluetooth: BNEP socket layer initialized [3.158552] iwlwifi :02:00.0: L1 Enabled - LTR Enabled [3.158801] iwlwifi :02:00.0: L1 Enabled - LTR Enabled [3.173299] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [6.872833] wlan0: authenticate with 00:24:fe:a5:c9:bb [6.876739] wlan0: send auth to 00:24:fe:a5:c9:bb (try 1/3) [6.883036] wlan0: authenticated [6.885339] wlan0: associate with 00:24:fe:a5:c9:bb (try 1/3) [6.895617] wlan0: RX AssocResp from 00:24:fe:a5:c9:bb (capab=0x431 status=0 aid=1) [6.897016] wlan0: associated [6.897039] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 67.922809] usb 1-2: new high-speed USB device number 5 using xhci_hcd [ 83.231657] usb 2-2: new SuperSpeed USB device number 2 using xhci_hcd [ 83.250083] usb 2-2: New USB device found, idVendor=05e3, idProduct=0743 [ 83.250092] usb 2-2: New USB device strings: Mfr=3, Product=4, SerialNumber=5 [ 83.250096] usb 2-2: Product: USB Storage [ 83.250099] usb 2-2: Manufacturer: Generic [ 83.250102] usb 2-2: SerialNumber: 0819 [ 83.274707] usb-storage 2-2:1.0: USB Mass Storage device detected [ 83.274819] scsi4 : usb-storage 2-2:1.0 [ 83.274936] usbcore: registered new interface driver usb-storage [ 84.272768] scsi 4:0:0:0: Direct-Access Generic STORAGE DEVICE 0819 PQ: 0 ANSI: 6 [ 84.273147] sd 4:0:0:0: Attached scsi generic sg1 type 0 [ 84.274020] sd 4:0:0:0: [sdb] Attached SCSI removable disk [ 89.167253] sd 4:0:0:0: [sdb] 62879744 512-byte logical blocks: (32.1
Bug#781733: zoneminder: Install fails with Failed to start LSB: Control ZoneMinder as a Service.
On Thu, 2 Apr 2015 05:31:08 R Bees wrote: I tried to install but the install fails with: sudo systemctl -l status zoneminder.service [sudo] password for rbees: I have tried the instructions here: http://www.zoneminder.com/wiki/index.php/Ubuntu_Server_14.04_64-bit_with_Zon eminder_1.26.5_the_easy_way and here: http://www.sourcetrunk.com/zoneminder/ You are using wrong installation instructions. Instead you need to follow README.Debian in /usr/share/doc/zoneminder. I've just updated instructions to setup zoneminder web server so at the moment you can read latest README.Debian here: http://anonscm.debian.org/cgit/collab-maint/zoneminder.git/tree/debian/README.Debian Once you've initialised (or upgraded) database you can start zoneminder service. Once web server is configured you should be able to access fully functional web interface. -- All the best, Dmitry Smirnov GPG key : 4096R/53968D1B --- No person, no idea, and no religion deserves to be illegal to insult, not even the Church of Emacs. -- Richard Stallman signature.asc Description: This is a digitally signed message part.
Bug#762239: kdm restart might fail on systemd
Control: tags -1 moreinfo Control: tags -1 unreproducible ● kdm.service - LSB: X display manager for KDE Loaded: loaded (/etc/init.d/kdm) Drop-In: /run/systemd/generator/kdm.service.d └─50-kdm-$x-display-manager.conf Active: active (exited) since sab 2014-09-20 00:27:03 CEST; 1min 9s ago Process: 11247 ExecStop=/etc/init.d/kdm stop (code=exited, status=0/SUCCESS) Process: 11287 ExecStart=/etc/init.d/kdm start (code=exited, status=0/SUCCESS) set 20 00:27:00 hal9000 systemd[1]: Starting LSB: X display manager for KDE... set 20 00:27:03 hal9000 kdm[11287]: Starting K Display Manager: kdmfailed (already running). set 20 00:27:03 hal9000 systemd[1]: Started LSB: X display manager for KDE. I'm not sure what happened from the systemd status messaage. Did kdm actually restart when you issued systemctl restart kdm.service? Please provide some more detailed information what you actually did and what the outcome was. I can't currently reproduce this issue, kdm restarts just fine when running systemd. In any case, you may also have a look at #755359 [1] where I have provided a systemd service file for kdm which you can install and have /etc/systemd/systemd/default-display-manager.service point to it. This will turn kdm into a native systemd service. I will be providing a full patch to the actual kdm package in a minute. Adrian [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755359 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781737: gparted: GUI hangs while doing libparted operations such as FAT16/FAT32 resizing
Package: gparted Version: 0.19.0-2 Severity: serious Tags: upstream Forwarded: https://bugzilla.gnome.org/show_bug.cgi?id=737022 The gparted GUI always hangs when gparted is doing some particular operations. If the screensaver/screenlock runs at this point, afterwards gparted windows will be gray, giving user the appearance that gparted has crashed. This bug is caused by long lasting (potentially hours) blocking IO operations being done on the GUI thread. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781738: gnucash: ImportError: No module named gnucash
Control: forcemerge 778999 -1 Le jeudi 02 avril 2015 à 11:20 +0100, Chris Bainbridge a écrit : Package: gnucash Version: 1:2.6.4-3 Severity: normal On starting gnucash, it always fails to import some Python module: $ gnucash Traceback (most recent call last): File /usr/share/gnucash/python/init.py, line 3, in module from gnucash import * ImportError: No module named gnucash This is a duplicate of #778999. Merging the two. -- .''`.Sébastien Villemot : :' :Debian Developer `. `' http://sebastien.villemot.name `- GPG Key: 4096R/381A7594 signature.asc Description: This is a digitally signed message part
Bug#781612: [Pkg-xfce-devel] Bug#781612: Bug#781612: libglib2.0-0: segfault in xfdesktop
Control: tag -1 unreproducible moreinfo On Wed, Apr 01, 2015 at 06:46:45PM +0200, Christian Knoke wrote: Yves-Alexis Perez schrieb am 01. Apr um 14:07 Uhr: So it's not reproducible? No. Then there's no much we can do. Regards, -- Yves-Alexis signature.asc Description: Digital signature
Bug#751205: b43-fwcutter
Hi jmv, I am aware of the problem and have spoken to the maintainer Daniel Echeverry. Even though he put it up for adoption, I am not yet maintainer, and only he can make changes and commit. We will work out a solution at the earliest. - Sidharth On Thu, Apr 2, 2015 at 4:20 PM, Jean-Michel Nirgal Vourgère jmv_...@nirgal.com wrote: Hi This is a friendly reminder that the package you say you want [1] to take care of has an urgent need of attention. See https://bugs.debian.org/781544 Cheers [1] https://bugs.debian.org/751205 and https://bugs.debian.org/754534 -- Nirgal
Bug#781002: initramfs-tools: no kernel modules are insert into initrd
On Wed, Apr 01, 2015 at 06:10:05PM -0700, Marc MERLIN wrote: Could I make a few suggestions while we're at it? 1) I sometimes build an initrd for a kernel I haven't installed yet. Yes, it's a mistake, but it happily succeeds and creates an initrd without any modules which then creates a non booting system. = initramfs should abort if its generated /lib/modules/kernel is empty I thought this was caught. 2) initramfs creates a temporary directory where it puts everything, and then deletes it before you can inspect it for debugging. = Add a --debug that leaves that directory behind for inspection. Right now I have to unpack the initrd image which is more and more of a pain as it becomes a bundled binary of concatenated cpio images and god knows what. -k :P as usual read the nice man mkinitramfs (; 3) document the binwalk method of unpacking initrd to debug if needed (somewhere in the manpage): http://unix.stackexchange.com/questions/163346/why-is-it-that-my-initrd-only-has-one-directory-namely-kernel . Or for the archives: legolas [mc]# binwalk initrd.img pick up the offset of the 2nd initrd image, and unpack like so: legolas [mc]# cd subdir; dd if=../initrd.img bs=21136 skip=1 | gunzip | cpio -idv lsinitramfs shows you the content. sunny greetings, -- maks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781734: ShowConnected plugin shows an error icon until there's activity
Package: blueman Version: 1.99~alpha1-1 File: /usr/bin/blueman-applet Severity: minor Dear maintainer, After xfce starts with bluetooth on, the icon in the tray is invalid. If I right click to disable, then enable ok, the icon is correct. This is without connecting to any device. I expected the icon to be right without that problem. The default configuration for plugin StatusIcon is blueman-tray and I enabled the plugin ShowConnected. 1.99~alpha2 changelog shows some changes related to icons, but I did not tested it yet (might be fixed upstream). Thank you for taking care of blueman. -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages blueman depends on: ii bluez5.23-2+b1 ii dbus 1.8.16-1 ii gir1.2-appindicator3-0.1 0.4.92-3.1 ii gir1.2-gconf-2.0 3.2.6-3 ii gir1.2-gdkpixbuf-2.0 2.31.1-2+b1 ii gir1.2-glib-2.0 1.42.0-2.2 ii gir1.2-gtk-3.0 3.14.5-1 ii gir1.2-notify-0.70.7.6-2 ii gir1.2-pango-1.0 1.36.8-3 ii gnome-icon-theme 3.12.0-1 ii libatk1.0-0 2.14.0-1 ii libbluetooth35.23-2+b1 ii libc62.19-17 ii libcairo-gobject21.14.0-2.1 ii libcairo21.14.0-2.1 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglib2.0-0 2.42.1-1 ii libgtk-3-0 3.14.5-1 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii libpulse-mainloop-glib0 5.0-13 ii libpython2.7 2.7.9-2 ii librsvg2-common 2.40.5-1 ii libstartup-notification0 0.12-4 ii notification-daemon 0.7.6-2 ii obex-data-server 0.4.5-1+b4 ii python 2.7.9-1 ii python-dbus 1.2.0-2+b3 ii python-gi3.14.0-1 ii python-gi-cairo 3.14.0-1 ii xfce4-notifyd [notification-daemon] 0.2.4-3 Versions of packages blueman recommends: ii policykit-1 0.105-8 blueman suggests no packages. -- no debconf information signature.asc Description: OpenPGP digital signature
Bug#610055: closing old done bugs
Hi, I'm closing these bugs as they are about two new upstream versions (which are both already available in at least jessie) and two requests to incorporate (potential) NMU diffs from 2011 and 2012. cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#781738: gnucash: ImportError: No module named gnucash
Package: gnucash Version: 1:2.6.4-3 Severity: normal Dear Maintainer, On starting gnucash, it always fails to import some Python module: $ gnucash Traceback (most recent call last): File /usr/share/gnucash/python/init.py, line 3, in module from gnucash import * ImportError: No module named gnucash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781741: gnucash crash when click back on QIF import
Package: gnucash Version: 1:2.6.4-3 Severity: normal Dear Maintainer, To reproduce do: file - import - qif - forward - select - import - forward - start - forward - back - back Backtrace: In ice-9/boot-9.scm: 157: 3 [catch #t #catch-closure 1190ee0 ...] In unknown file: ?: 2 [apply-smob/1 #catch-closure 1190ee0] In qif-import/qif-file.scm: 557: 1 [qif-file:check-from-acct #f] In ice-9/boot-9.scm: 1381: 0 [#procedure 1af16c0 at ice-9/boot-9.scm:1380:4 (obj) #f] ice-9/boot-9.scm:1381:15: In procedure #procedure 1af16c0 at ice-9/boot-9.scm:1380:4 (obj): ice-9/boot-9.scm:1381:15: In procedure struct_vtable: Wrong type argument in position 1 (expecting struct): #f -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755359: [kdm] systemd seem to fail to start display-manager.service
On 01/10/2015 03:26 PM, John Paul Adrian Glaubitz wrote: In any case, I will hopefully provide an updated kdm package in the following week that you can try at your desire. Attaching a debdiff with the proposed changes to the kde-workspace source package which will add systemd support to kdm. These changes were inspired by the lightdm package in Debian as well as the kdm package in Fedora. I haven't fully tested my changes yet. Cheers, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 diff -Nru kde-workspace-4.11.13/debian/changelog kde-workspace-4.11.13/debian/changelog --- kde-workspace-4.11.13/debian/changelog 2014-11-07 10:11:29.0 +0100 +++ kde-workspace-4.11.13/debian/changelog 2015-04-02 11:17:10.0 +0200 @@ -1,3 +1,16 @@ +kde-workspace (4:4.11.13-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * Add systemd support: (Closes: #755359) +- debian/control: + + Add dh_systemd (= 1.14) to Build-Depends. +- debian/kdm.postinst: + + Create symbolic link to systemd service file of default display manager. +- debian/rules: + + Install kdm systemd service file using dh_system_start. + + -- John Paul Adrian Glaubitz glaub...@physik.fu-berlin.de Thu, 02 Apr 2015 11:16:43 +0200 + kde-workspace (4:4.11.13-2) unstable; urgency=medium * New patch: upstream_do_not_pass_ntpUtility_as_an_argument.patch fix diff -Nru kde-workspace-4.11.13/debian/control kde-workspace-4.11.13/debian/control --- kde-workspace-4.11.13/debian/control 2014-11-07 10:11:29.0 +0100 +++ kde-workspace-4.11.13/debian/control 2015-04-02 11:08:32.0 +0200 @@ -75,7 +75,8 @@ python-dev (= 2.6.6-3~), shared-desktop-ontologies (= 0.8), udev [linux-any], - zlib1g-dev + zlib1g-dev, + dh-systemd (= 1.14) Standards-Version: 3.9.5 X-Python-Version: = 2.5 XS-Testsuite: autopkgtest diff -Nru kde-workspace-4.11.13/debian/kdm.postinst kde-workspace-4.11.13/debian/kdm.postinst --- kde-workspace-4.11.13/debian/kdm.postinst 2014-11-07 10:11:29.0 +0100 +++ kde-workspace-4.11.13/debian/kdm.postinst 2015-04-02 11:10:01.0 +0200 @@ -78,6 +78,15 @@ if [ -d /var/lib/kdm ]; then chown -R kdm /var/lib/kdm fi +# set default-display-manager systemd service link according to our config +if [ -e $DEFAULT_DISPLAY_MANAGER_FILE -a -d /etc/systemd/system/ ]; then + SERVICE=/lib/systemd/system/$(basename $(cat $DEFAULT_DISPLAY_MANAGER_FILE)).service + if [ -e $SERVICE ]; then + ln -sf $SERVICE /etc/systemd/system/display-manager.service + else + echo ERROR: $SERVICE is the selected default display manager but does not exist 2 + fi +fi ;; abort-upgrade|abort-remove|abort-deconfigure) diff -Nru kde-workspace-4.11.13/debian/kdm.service kde-workspace-4.11.13/debian/kdm.service --- kde-workspace-4.11.13/debian/kdm.service 1970-01-01 01:00:00.0 +0100 +++ kde-workspace-4.11.13/debian/kdm.service 2015-04-02 11:10:27.0 +0200 @@ -0,0 +1,10 @@ +[Unit] +Description=KDE Display Manager +Documentation=man:kdm(1) +After=systemd-user-sessions.service + +[Service] +ExecStartPre=/bin/sh -c '[ $(cat /etc/X11/default-display-manager 2/dev/null) = /usr/bin/kdm ]' +ExecStart=/usr/bin/kdm +Restart=always +IgnoreSIGPIPE=no diff -Nru kde-workspace-4.11.13/debian/rules kde-workspace-4.11.13/debian/rules --- kde-workspace-4.11.13/debian/rules 2014-11-07 10:11:29.0 +0100 +++ kde-workspace-4.11.13/debian/rules 2015-04-02 11:07:34.0 +0200 @@ -1,6 +1,6 @@ #!/usr/bin/make -f -dh = --with=python2 +dh = --with=python2 --with=systemd include /usr/share/pkg-kde-tools/qt-kde-team/2/debian-qt-kde.mk libpkgs_addsubst_allLibraries = kde-workspace-dev @@ -39,6 +39,9 @@ $(overridden_command) -pkdm --noscripts $(overridden_command) --remaining-packages +override_dh_systemd_start: + $(overriden_command) -pkdm --no-start -r kdm.service + pkgs_with_install_linux = $(patsubst debian/%.install.linux,%,$(wildcard debian/*.install.linux)) override_dh_install: $(overridden_command)
Bug#769636: [Pkg-utopia-maintainers] Bug#769636: avahi-utils: please soften the dependency on avahi-daemon
Am 15.11.2014 um 10:09 schrieb Johannes Schauer: Package: avahi-utils Version: 0.6.31-4+b1 Severity: normal Hi, I wanted to get a list of all mDNS services in my local network. Thus I installed avahi-utils and everything worked fine. But much later I discovered that I had a new service running in the background of my system: avahi-daemon. It must've been installed together with avahi-utils as avahi-utils depends on avahi-daemon. I stopped the avahi-daemon process and can confirm that avahi-browse works just fine without the avahi-daemon running. Are you sure? Keep in mind, that avahi-daemon.service can be auto-activated via D-Bus or avahi-daemon.socket. You'll need to mask the avahi-daemon.service to be absolutely sure it's not activated. $ systemctl mask avahi-daemon.service $ systemctl stop avahi-daemon.socket avahi-daemon.service $ avahi-browse --all Failed to create client object: Daemon not running So, from what I can see, the dependency is correct. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#781346: [Pkg-freeipa-devel] Bug#781346: slapi-nis: CVE-2015-0283: infinite loop in getgrnam_r() and getgrgid_r()
On 27.03.2015 21:03, Salvatore Bonaccorso wrote: Source: slapi-nis Version: 0.54-1 Severity: grave Tags: security upstream fixed-upstream Hi Timo, the following vulnerability was published for slapi-nis. I was not able to verify the issue itself but only checked patch-wise. CVE-2015-0283[0]: infinite loop in getgrnam_r() and getgrgid_r() If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2015-0283 [1] https://bugzilla.redhat.com/show_bug.cgi?id=1195729 So I pushed a new upstream version instead of pulling commits, since upstream said it needed all (four) commits between 0.54.1..0.54.2. And .1 brought only two commits more. But this could be dropped from jessie too if necessary, there are no packages that depend on it. -- t -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781744: kde-plasma-desktop: Get a notification to disable my sound devices always even in non-kde environment/desktop.
Package: kde-plasma-desktop Version: 5:84 Severity: normal Dear Maintainer, I get a notification each time I am in a non-kde environment. I have multiple desktops, use gdm3 as display-manager by default. Have no idea which package does it. Attaching the screenshot for the same. -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (600, 'testing'), (500, 'testing-updates'), (1, 'experimental'), (1, 'unstable') 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 kde-plasma-desktop depends on: ii kde-baseapps4:4.14.2-1 ii kde-runtime 4:4.14.2-2 ii kde-workspace 4:4.11.13-2 ii plasma-desktop 4:4.11.13-2 ii udisks2 2.1.3-5 ii upower 0.99.1-3.1 Versions of packages kde-plasma-desktop recommends: ii kdm 4:4.11.13-2 ii xserver-xorg 1:7.7+7 Versions of packages kde-plasma-desktop suggests: pn kde-l10n none -- no debconf information -- Regards, Shirish Agarwal शिरीष अग्रवाल My quotes in this email licensed under CC 3.0 http://creativecommons.org/licenses/by-nc/3.0/ http://flossexperiences.wordpress.com EB80 462B 08E1 A0DE A73A 2C2F 9F3D C7A4 E1C4 D2D8
Bug#781726: how to solve the live-tools upgrade issue? (#781725)
On Thu, Apr 2, 2015 at 10:17:52 +0200, Andreas Beckmann wrote: Andreas, who is neither maintainer nor user of live-tools and cares solely about the upgrade issue discovered by piuparts If live-tools is supposed to be a live CD thing, I'm not sure how likely it is anyone's going to want to dist-upgrade it... Cheers, Julien signature.asc Description: Digital signature
Bug#781607: [Pkg-freeipa-devel] Bug#781607: freeipa: please package new upstream version
Hi Timo, thanks for uploading 4.0.5-4! On Donnerstag, 2. April 2015, Timo Aaltonen wrote: actually it needs bind 9.10.1 or newer, experimental has rc2 from a ~year ago. I got a suggestion to pull a patch from Centos, which disables DNSSEC support.. that should let us move forward with 4.1 sooner. ah, cool. cheers, Holger, currently working on a freeipa-client package suitabel for wheezy signature.asc Description: This is a digitally signed message part.
Bug#781730: systemd: Instance variable %i not available for ReadWriteDirectories
Hi Bernhard, Am 02.04.2015 um 11:07 schrieb Bernhard Schmidt: We're trying to run multiple DHCP processes on one system. They have their data in a instance-specific configuration directory and we'd like to limit (r/w for now) filesystem access to that directory for security reasons. == dhcpd@.service == [Unit] Description=DHCP Instance %i After=syslog.target After=network.target [Service] ExecStart=/usr/sbin/dhcpd -cf /var/lib/dhcp/%i/etc/dhcpd.conf -lf /var/lib/dhcp/%i/db/dhcpd.leases -pf /var/lib/dhcp/%i/dhcpd.pid -f Type=simple Restart=on-failure CapabilityBoundingSet=CAP_NET_RAW CAP_NET_BIND_SERVICE NoNewPrivileges=true ReadOnlyDirectories=/ ReadWriteDirectories=/var/lib/dhcp/%i This does not work This looks like a reasonable request. Could you file a bug upstream and let us know about the bug number? Thanks, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#744231: gnucash: Crash on QIF import
On 2 April 2015 at 08:00, Dmitry Smirnov only...@debian.org wrote: Hi Chris, On Fri, 11 Apr 2014 17:41:09 Chris Bainbridge wrote: Start QIF import, at Set a date format for this QIF file select 'd-m-y'. Crash. I've noticed that upstream closed corresponding bug report [1] due to lack of information (they could not reproduce the problem). Do you still have this problem with GnuCash-2.6.4 ? I no longer have any of the problematic QIF files to test. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775612: Bug is in Perl
Hi This bug is also present in Ubunty-Gnome 14.10 Tie/StdHash.pm is missing from Perl 5.20.1
Bug#781736: awesome: Please package the new upstream release
Package: awesome Version: 3.5.5-1 Severity: wishlist Hello, Please package the new 3.5.6 release. 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 awesome depends on: ii dbus-x11 1.8.16-1 ii gir1.2-freedesktop1.42.0-2.2 ii gir1.2-pango-1.0 1.36.8-3 ii libc6 2.19-17 ii libcairo2 1.14.0-2.1 ii libdbus-1-3 1.8.16-1 ii libgdk-pixbuf2.0-02.31.1-2+b1 ii libglib2.0-0 2.42.1-1 ii liblua5.1-0 5.1.5-7.1 ii libstartup-notification0 0.12-4 ii libx11-6 2:1.6.2-3 ii libxcb-cursor00.1.1-3 ii libxcb-icccm4 0.4.1-1 ii libxcb-keysyms1 0.4.0-1 ii libxcb-randr0 1.10-3+b1 ii libxcb-render01.10-3+b1 ii libxcb-shape0 1.10-3+b1 ii libxcb-util0 0.3.8-3 ii libxcb-xinerama0 1.10-3+b1 ii libxcb-xtest0 1.10-3+b1 ii libxcb1 1.10-3+b1 ii libxdg-basedir1 1.2.0-1 ii lua-lgi 0.8.0-2 ii menu 2.1.47 Versions of packages awesome recommends: ii feh2.12-1 ii rlwrap 0.41-1 ii x11-xserver-utils 7.7+3+b1 awesome suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781733: wrong system listed
Sorry for the wrong info in the original bug report. The system is actually NOT Architecture: amd64 (x86_64) It IS Architecture: i386 Every thing else is the same. Testing (patched weekly) -- if it ain't broke tweak it
Bug#546936: ITP: r-cran-igraph -- GNU R package for igraph
Hi Alba, I just uploaded r-cran-igraph to new. Hope this helps. You did not yet raised your opinion about maintaining r-cran-phangorn in Debian Med. What do you think about this? Kind regards Andreas. On Tue, Mar 31, 2015 at 05:53:19PM +0200, Alba Crespi wrote: Hi, I am currently working on packages for r-cran-phangorn and its dependencies, and I saw that you already have an ITP for r-cran-igraph. What is the status? Do you have something ready, or is there something blocking a package? Cheers, Alba -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779606: daemon-reexec starts plymouth-start.service service
Hi! Am 02.04.2015 um 10:48 schrieb Martin Pitt: Michael Biebl [2015-03-03 1:05 +0100]: I have plymouth installed and enabled (via splash on the kernel command line). When I run systemctl daemon-reexec, plymouth is (re)started: I could reproduce this (and other restarted services) until recently, but it seems fixed with the v219-stable updates (for me and also for the original reporter in the Ubuntu bug LP#1431200). Do you still get this with 219-6? If so, can you please put the journalctl -f output here that happens when you do systemctl daemon-reload (and/or -reexec). Have you run a git bisect on the v219-stable branch to find the relevant commit? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
