http://blog.gmane.org/gmane.linux.debian.devel.bugs.general hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.linux.debian.devel.bugs.general/1053128 <pre>Package: mksh Version: 46-1 Severity: serious Dear Maintainer, The handling of built-using is wrong. It is not meant to encode the compiler used, nor binutils or kernel headers should be recorded there It is specifically for building against -source packages and for hacks like ia32libs where binaries are copied into a source package. Not for 'everything'. What you effectively are doing is asking for a mksh rebuild on each upload of the kernel, of gcc and what else you have put there. Imagine if we all did that. Buildd power. or mirror size. or both. /Sune </pre> Sune Vuorela 2013-05-22T21:37:26 http://comments.gmane.org/gmane.linux.debian.devel.bugs.general/1053126 <pre>Dear GMP developers, I am forwarding a bug I already report to the Debian BTS (http://bugs.debian.org/708264) with libgmp 5.1.1 on IA64. It seems the file mpn/ia64/divrem_2.asm do not restore f17 register which sort of contradict mpn/ia64/README which says that only f6-f15 f32-f127 are caller-save. Thus programs calling e.g. mpn_sqrtrem might end up have having corrupted registers (f16 to f18) libgmp works fine when rebuild with the file removed. I did not test libgmp 5.1.2 yet but the file mpn/ia64/divrem_2.asm is identical so it is likely the bug is still there. I attach a test case (which uses a lot of double in the hope the compiler use f17). I tested gcc 4.6, gcc 4.7 and 4.8 (debian build). The correct output (without call to mpn_sqrtrem) %gcc gmptest.c -g -O1 -lgmp -o test &amp;&amp; ./test 8.53996 1.56883 8.15584 44.3965 10.1088 6.97113 52.5523 -36.2406 3.142 2.718 0.5772 14.13 8.53996 1.56883 8.15584 44.3965 33.3916 The corrupted output (with a call to mpn_sqrtrem) %gcc gmptest.c -g -O1 -lgmp -o test -DSQRTN &amp;&amp; ./test 8.53996 1.56883 8.15584 44.3965 9.84742e-309 5.14474e-309 1.51044e+19 -36.2406 3.142 2.718 0.5772 14.13 8.53996 1.56883 8.15584 44.3965 33.3916 Cheers, Bill. </pre> Bill Allombert 2013-05-22T21:36:03 http://comments.gmane.org/gmane.linux.debian.devel.bugs.general/1053124 <pre>severity 709359 normal tags 709359 - unreproducible thanks Thanks for your report, I can't reproduce your problem. Could you downgrade xinetd and upgrade it again and see what happens? </pre> Salvo Tomaselli 2013-05-22T21:26:37 http://comments.gmane.org/gmane.linux.debian.devel.bugs.general/1053122 <pre>Package: gsw Version: 3.0.1-1 Severity: normal Tags: patch It appears from the python3-all-dev build-depend and the use of dh_python3 in debian/rules that you intend gsw to support python3, but it doesn't. I've put together the changes needed as well as a few other clean up items in the attached debdiff. </pre> Scott Kitterman 2013-05-22T21:30:47 http://comments.gmane.org/gmane.linux.debian.devel.bugs.general/1053119 <pre>Package: glchess Version: 1:3.4.2-3 Severity: important Dear Maintainer, glchess crashes on start. Backtrace: (gdb) bt #0 0x00007ffff7796168 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #1 0x00007ffff79e2024 in gtk_window_set_application () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #2 0x00007ffff77b025c in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #3 0x00007ffff5fd5a94 in g_cclosure_marshal_VOID__OBJECTv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #4 0x00007ffff5fd28e7 in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #5 0x00007ffff5feb2b6 in g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #6 0x00007ffff5febf82 in g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #7 0x0000000000415599 in application_construct () #8 0x0000000000418d5d in gl_chess_main () #9 0x00007ffff516ba55 in __libc_start_main (main=0x40f5c0 &lt;main&gt;, argc=1, ubp_av=0x7fffffffe408, init=&lt;optimized out&gt;, fini=&lt;optimized out&gt;, rtld_fini=&lt;optimized out&gt;, stack_end=0x7fffffffe3f8) at libc-start.c:260 #10 0x000000000040f609 in _start () </pre> Mislav Blažević 2013-05-22T21:25:38 http://comments.gmane.org/gmane.linux.debian.devel.bugs.general/1053116 <pre>Hi, This bug also affects Konsole in KDE, using Kwin as window manager. When I try to (un-)maximize the Konsole window, the X server infrequently segfaults. It seems to happen about 20% of the time, with chances increasing when the X session has been running longer. Extensive dragging of Konsole windows across screens can consistently crash the X server. I've also managed to reproduce the crash using a closed-source Qt application once. A quick Google search turned up the following relevant information: (*) ArchLinux and Gentoo are affected too: https://bbs.archlinux.org/viewtopic.php?pid=1176889 http://forums.gentoo.org/viewtopic-t-955708-start-0.html (*) 13.1 should have fixed this, but it doesn't work. There's a report of 12.6 working for someone (I haven't tried it yet). http://forum.kde.org/viewtopic.php?f=227&amp;t=109597 (*) It has already been reported upstream, where someone mentioned that it only happens in multimontior environments, which might be true; I'm using one. http://ati.cchtml.com/show_bug.cgi?id=724 For reference, the relevant part from my Xorg.0.log: [ 15420.810] [ 15420.810] Backtrace: [ 15420.810] 0: /usr/bin/X (xorg_backtrace+0x36) [0x7fe526771d06] [ 15420.811] 1: /usr/bin/X (0x7fe5265f3000+0x182859) [0x7fe526775859] [ 15420.811] 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fe525919000+0xf210) [0x7fe525928210] [ 15420.811] 3: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 (0x7fe525693000+0x727ed) [0x7fe5257057ed] [ 15420.811] 4: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 (0x7fe525693000+0x72b5f) [0x7fe525705b5f] [ 15420.811] 5: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 (pixman_blt+0x52) [0x7fe52569d8b2] [ 15420.811] 6: /usr/lib/xorg/modules/libfb.so (fbCopyNtoN+0x2c9) [0x7fe521480469] [ 15420.811] 7: /usr/lib/xorg/modules/glesx.so (0x7fe51e4a8000+0x758c1) [0x7fe51e51d8c1] [ 15420.811] 8: /usr/lib/xorg/modules/glesx.so (0x7fe51e4a8000+0x77c25) [0x7fe51e51fc25] [ 15420.811] 9: /usr/bin/X (0x7fe5265f3000+0x110a79) [0x7fe526703a79] [ 15420.811] 10: /usr/bin/X (0x7fe5265f3000+0xd9955) [0x7fe5266cc955] [ 15420.811] 11: /usr/bin/X (0x7fe5265f3000+0xdacaf) [0x7fe5266cdcaf] [ 15420.811] 12: /usr/bin/X (0x7fe5265f3000+0xd7e1c) [0x7fe5266cae1c] [ 15420.811] 13: /usr/bin/X (ConfigureWindow+0x378) [0x7fe52666eec8] [ 15420.811] 14: /usr/bin/X (0x7fe5265f3000+0x4d904) [0x7fe526640904] [ 15420.811] 15: /usr/bin/X (0x7fe5265f3000+0x52e61) [0x7fe526645e61] [ 15420.811] 16: /usr/bin/X (0x7fe5265f3000+0x41ec5) [0x7fe526634ec5] [ 15420.812] 17: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf5) [0x7fe5245a4a55] [ 15420.812] 18: /usr/bin/X (0x7fe5265f3000+0x4219d) [0x7fe52663519d] [ 15420.812] [ 15420.812] Segmentation fault at address 0x7fe4f9c15000 [ 15420.812] Fatal server error: [ 15420.812] Caught signal 11 (Segmentation fault). Server aborting [ 15420.812] [ 15420.812] Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 15420.812] Please also check the log file at "/var/log/Xorg.0.log" for additional information. I'm using kernel 3.8, but can also reproduce the crash with 3.6. X and fglrx stack from testing installed (xserver-xorg-core 2:1.12.4-6, fglrx-driver 1:13.4-2). </pre> Oxan van Leeuwen 2013-05-22T20:11:24 http://comments.gmane.org/gmane.linux.debian.devel.bugs.general/1053110 <pre>Package: lintian Version: 2.5.12 Severity: normal tags: patch Please apply this patch </pre> bastien ROUCARIES 2013-05-22T21:12:33 http://comments.gmane.org/gmane.linux.debian.devel.bugs.general/1053109 <pre>Package: ifupdown Version: 0.7.43 Severity: normal Dear Maintainer, Since ifupdown 0.7.43 entered testing, I have noticed "ifup -v lo" and "ifdown -v lo" attempting to bring the loopback interface up/down twice. I guess this is because ifup/ifdown now predefine lo internally as an auto interface. They bring lo up/down once for the internal definition and once for the definition in /etc/network/interfaces (which will be present in almost all systems upgraded from wheezy). Unless ifup/ifdown can be made smarter about dealing with multiple definitions, perhaps you should recommend that all mention of lo be omitted from /etc/network/interfaces from now on? The documentation available via "man interfaces" and in /usr/share/doc/ifupdown/examples would need changing to reflect this. Regards, Matthew </pre> Matthew Foulkes 2013-05-22T21:13:21 http://comments.gmane.org/gmane.linux.debian.devel.bugs.general/1053102 <pre>Package: mythtv-status Version: 0.10.2-3 Severity: normal Hi! It's annoying that mythtv-status reports times like: Recording Now: Blah blah blah (CHANNEL) Ends: 21:00:00Z when it's already 21:30 on the clock, because I'm in a +0100 timezone at present. Much more meaningful would be: Recording Now: Blah blah blah (CHANNEL) Ends: 22:00:00 BST I haven't tested it, but it would seem that manipulating the times by doing something like this: $localdate=UnixDate(ParseDate($date), "%Y-%m-%d %H:%M:%S %Z") should do the job. But unfortunately it would require some rewriting of the code, as the current mechanism is only set up to do a simple substitution at present. Julian </pre> Julian Gilbey 2013-05-22T20:55:22 http://comments.gmane.org/gmane.linux.debian.devel.bugs.general/1053098 <pre>your patch is rather suboptimal; first, it's backports unfriendly by adding an uneeded (versioned) depends against lsb-base; second, it doesn't follow the used coding style, and third, it's overly complicated. i've commited a proper version of above, and added the upstart job unchanged. </pre> Daniel Baumann 2013-05-22T20:49:22 http://comments.gmane.org/gmane.linux.debian.devel.bugs.general/1053095 <pre>Package: python-dap Version: 2.2.6.7-1 Severity: minor Tags: upstream patch Dear Maintainer, With python-dap installed, I get the following warning message: Module dap was already imported from None, but /usr/lib/python2.7/dist-packages is being added to sys.path The easiest way to trigger this message is to run "import pkg_resources". A gentoo bug report at https://bugs.gentoo.org/show_bug.cgi?id=54161#c29 suggests that the 'dap' package needs to be added to the top of /usr/lib/python2.7/dist-packages//dap-2.2.6.7.egg-info/namespace_packages.txt (or whatever the equivalent location is). The easiest way to fix this is to change the 'namespace_packages' parameter being used in setup.py, in the Debian source package. I've attached a patch which adds the root 'dap' package to namespace_package. This fixes the warning message in my local tests. Thanks, Mike </pre> Mike Neish 2013-05-22T20:30:32 http://comments.gmane.org/gmane.linux.debian.devel.bugs.general/1053092 <pre>Package: ttyload Version: 0.5-7 Severity: minor There's a typo in the manpage: xReleased -&gt; Released </pre> Jakub Wilk 2013-05-22T20:30:10 http://comments.gmane.org/gmane.linux.debian.devel.bugs.general/1053091 <pre>For #709364 I was able to look at the Access Point that the problem is occurring with. Manufacturer: TP-LINK Model #: TLWR740N Ver 2.1 I'm pretty sure the owner updated the firmware either to a newer manufacturer version or to something like openwrt/ddwrt. Hopefully I will hear back from them in the next few days. </pre> Matt Taggart 2013-05-22T20:28:24 http://comments.gmane.org/gmane.linux.debian.devel.bugs.general/1053087 <pre>Package: ftp.debian.org Severity: normal Please remove python-jinja2-dbg and python3-jinja-dbg from unstable. After the conversion of python{,3}-jinja2 from Arch: any to Arch: all they are no longer built from jinja2. Kind regards </pre> Sebastian Ramacher 2013-05-22T20:16:34 http://comments.gmane.org/gmane.linux.debian.devel.bugs.general/1053083 <pre>Package: kbd Version: 1.15.3-9 Severity: normal "loadkeys -d" is supposed to load the default keymap. Instead it loads stdin. "loadkeys -d somefile" should load the default keymap, then somefile. This patch fixes all the usage cases, I think, but the loop logic is getting ugly so you might want to rework it. Index: kbd-1.15.3/src/loadkeys.y =================================================================== --- kbd-1.15.3.orig/src/loadkeys.y2013-05-22 05:32:30.378879662 -0500 +++ kbd-1.15.3/src/loadkeys.y2013-05-22 05:36:37.890876881 -0500 &lt; at &gt;&lt; at &gt; -1163,7 +1163,8 &lt; at &gt;&lt; at &gt; close(fd); } -for (i = optind; argv[i]; i++) { +int did_optd = 0; +for (i = optind; optd || argv[i]; i++) { FILE *f; char *ev; &lt; at &gt;&lt; at &gt; -1177,8 +1178,10 &lt; at &gt;&lt; at &gt; } if (optd) { +--i; /* first read default map - search starts in . */ optd = 0; +did_optd = 1; if ((f = findfile(DEFMAP, dirpath, suffixes)) == NULL) { fprintf(stderr, _("Cannot find %s\n"), DEFMAP); exit(EXIT_FAILURE); &lt; at &gt;&lt; at &gt; -1199,7 +1202,7 &lt; at &gt;&lt; at &gt; parse_keymap(f); } -if (optind == argc) { +if (optind == argc &amp;&amp; !did_optd) { strcpy(pathname, "&lt;stdin&gt;"); parse_keymap(stdin); } </pre> Alan Curry 2013-05-22T20:05:29 http://comments.gmane.org/gmane.linux.debian.devel.bugs.general/1053082 <pre>I am seeing problems with the "Intel Corporation Centrino Advanced-N 6235 [8086:088e]" card in my laptop. When connected to a particular access point using 802.11n I get frequent disconnects, dropped packets, erratic latency, and slow data rates. Some access points don't have the problem. I have tested both the Debian wheezy (3.2.41 based) and sid (3.8.13 based) kernels and both have the problems. I reported the problem and details to the Debian BTS here http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709364 (cc'd) and I think it's the same problem as this ubuntu bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/836250 Let me know if you want me to try anything or need me to send more info. Thanks, </pre> Matt Taggart 2013-05-22T20:01:49 http://comments.gmane.org/gmane.linux.debian.devel.bugs.general/1053079 <pre>I forgot to include the dmesg stuff in #709364 for when the problem is occurring. Here's with N-mode enabled: [ 89.904188] wlan1: deauthenticated from 54:e6:fc:bc:70:dc (Reason: 2) [ 89.932000] cfg80211: Calling CRDA to update world regulatory domain [ 89.957262] cfg80211: World regulatory domain updated: [ 89.957270] cfg80211: (start_freq - end_freq &lt; at &gt; bandwidth), (max_antenna_gain, max_eirp) [ 89.957278] cfg80211: (2402000 KHz - 2472000 KHz &lt; at &gt; 40000 KHz), (300 mBi, 2000 mBm) [ 89.957285] cfg80211: (2457000 KHz - 2482000 KHz &lt; at &gt; 20000 KHz), (300 mBi, 2000 mBm) [ 89.957292] cfg80211: (2474000 KHz - 2494000 KHz &lt; at &gt; 20000 KHz), (300 mBi, 2000 mBm) [ 89.957298] cfg80211: (5170000 KHz - 5250000 KHz &lt; at &gt; 40000 KHz), (300 mBi, 2000 mBm) [ 89.957305] cfg80211: (5735000 KHz - 5835000 KHz &lt; at &gt; 40000 KHz), (300 mBi, 2000 mBm) [ 93.234265] wlan1: authenticate with 54:e6:fc:bc:70:dc (try 1) [ 93.236721] wlan1: authenticated [ 93.239542] wlan1: associate with 54:e6:fc:bc:70:dc (try 1) [ 93.244528] wlan1: RX ReassocResp from 54:e6:fc:bc:70:dc (capab=0x431 status=0 aid=8) [ 93.244540] wlan1: associated [ 93.289789] wlan1: Wrong control channel in association response: configured center-freq: 2452 hti-cfreq: 2472 hti-&gt;control_chan: 13 band: 0. Disabling HT. It doesn't seem to log anything about the problems when N-mode is disabled, it just gets flakey. </pre> Matt Taggart 2013-05-22T20:07:11 http://comments.gmane.org/gmane.linux.debian.devel.bugs.general/1053078 <pre>package: adequate severity: wishlist x-debbugs-cc: piuparts-devel&lt; at &gt;lists.alioth.debian.org Hi, http://piuparts.debian.org/squeeze2wheezy/pass/debian-edu-artwork_0.0.33-3.log has the following adequate issues: 1m29.2s DEBUG: Starting command: ['adequate', '--root', '/srv/piuparts.debian.org/tmp/tmp35wC4J', 'debian-edu-artwork'] 1m29.3s DUMP: debian-edu-artwork: broken-symlink /usr/share/ldm/themes/debian-edu/host.png -&gt; ../ltsp/host.png debian-edu-artwork: broken-symlink /usr/share/ldm/themes/debian-edu/reboot.png -&gt; ../ltsp/reboot.png debian-edu-artwork: broken-symlink /usr/share/ldm/themes/debian-edu/shutdown.png -&gt; ../ltsp/shutdown.png debian-edu-artwork: broken-symlink /usr/share/ldm/themes/debian-edu/bg.png -&gt; ../ltsp/bg.png debian-edu-artwork: broken-symlink /usr/share/ldm/themes/debian-edu/session.png -&gt; ../ltsp/session.png debian-edu-artwork: broken-symlink /usr/share/ldm/themes/debian-edu/language.png -&gt; ../ltsp/language.png 1m29.3s DEBUG: Command ok: ['adequate', '--root', '/srv/piuparts.debian.org/tmp/tmp35wC4J', 'debian-edu-artwork'] piuparts also detects broken symlinks so it would be nice if there was an option to run adequate without a check for broken symlinks. This will make http://piuparts.debian.org/squeeze2wheezy/inadequate_issue.html and friends way more useful :-) cheers, Holger </pre> Holger Levsen 2013-05-22T19:59:19 http://comments.gmane.org/gmane.linux.debian.devel.bugs.general/1053076 <pre>Package: swi-prolog-nox Version: 6.2.6-2 Severity: important For now shlibs generation is suppressed. The library may need to be split into a separate package. </pre> Євгеній Мещеряков 2013-05-22T19:48:38 http://comments.gmane.org/gmane.linux.debian.devel.bugs.general/1053075 <pre>Package: phatch Severity: important -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Dear Maintainer, As seen in http://pad.lv/1173704 phatch imports PIL modules directly, assuming the existence of PIL.pth. With the switch to Pillow for python-imaging, the ..pth file is only available with python-imaging-compat, so you need to add a Depend on this for the phatch-cli binary package. I will commit a fix to svn for this. - -- System Information: Debian Release: wheezy/sid APT prefers saucy-updates APT policy: (500, 'saucy-updates'), (500, 'saucy-security'), (500, 'saucy'), (100, 'saucy-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.9.0-2-generic (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJRnSCIAAoJEBJutWOnSwa/CvQP/2pbTl+jHJcSwq2j9Gqh+dxj LF86/yk5E8W9IhV+B0HnAQ60HOItGfvNZucCesqp3xIuXGUElE56oExcXQ3X/42V I+/t1u/o0FbmRLrvGVcFALXAIp9pvU95+zvKeiO3od6yCtr4coZlYdCjr4L0odxB aTlkLdSk/7KMfjc+aEtpm/24Pz2Cb3HwxqA0OFG6Tj7ooh8MFD+luH035G27+Cvx x0c6xfR77QOwClS9f1+kSJUGfpxGXNnAc7iMJKXDvsZwOaw+8pTGuJzLCULrKzDs 1ulRA3TwwH+whwkzEnrKWU9h+0BpxEar77TSFuMH0/1geG3DLQk6jPyklHNWlhqk GNjr7Xk7nesvJCLXsxjNrp9XrX/wunb9c75XV2RYZ+eQyH0bORIK72O5wP/zrwx1 6o1HaUv9jV7O6ZF7ZUO3PvZulw2yMUJslFcJ8VbuvoishxavpTcnAFJIurtpoyQm 7ctSkX6Q1Z4+UBUQ0tqz57RjRweNONv3VvzTagWUgKgXdhSrjzXvn+wMMml8RFbe qOxdGHlInnemvZUa0vqZLALFv7UAlYUiWsIyQSVNsQ6qNR1S//drDQbkEowmLyQ3 /ePl47uyyVgVB10htFx7aptDyvJ7VIkplF2MwD2XQ07WXooUNY4OpACNCOZnixgw QRIirG4kRXg1/pxVFWn+ =o6gZ -----END PGP SIGNATURE----- </pre> Barry Warsaw 2013-05-22T19:46:17 http://comments.gmane.org/gmane.linux.debian.devel.bugs.general/1053073 <pre>of course 1.1.5. </pre> Eric Valette 2013-05-22T19:34:02 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.linux.debian.devel.bugs.general