Bug#767906: libgtk-3-0: Size of menus on screen top is not properly calculated
Hi, Yes, I see it now. The upstream bug report says Looks like this is result after enabling csd for GtkMenu. Is there a Debian bug report for [1]? Looks like it's still not fixed. [1] https://bugzilla.gnome.org/show_bug.cgi?id=726030
Bug#764630: missing JNI path in jarwrapper
On Tue, Nov 25, 2014 at 12:49 AM, Emmanuel Bourg ebo...@apache.org wrote: Le 21/11/2014 17:12, Mathieu Malaterre a écrit : Maybe this is time to change the Java policy §2.4 Java libraries This means that dicomscope package would install only the `jar` file, and the x86 or x86_64 native lib (*.so) can be installed whether the user want the 32bits or the 64bits version. Comments ? The policy change is certainly a good idea, but it will not solve this specific issue. For example, let say we are on an amd64 system and we install the package libfoo-java that depends on libfoo-jni. libfoo-jni installs its .so in a multiarch path (/usr/lib/x86_64-linux-gnu). We install the 32 bits JRE from Oracle and set it as the default JRE. Then we run foo with jarwrapper. jarwrapper tries to build the library path, and seeing we are on amd64 set it to /usr/lib:/usr/lib/x86_64-linux-gnu. foo fails because we tried loading a 64 bits library from a 32 bits VM. That is the correct behavior. When I want to run an x86 executable (apps are not co-installable) but install the default amd64 (x86_64) it does not work (the amd64 is used instead). So to run an x86 you need to explicitly install libfoo-jni:i386, that is the intended behavior. Actually jarwrapper has to guess the 32/64 bits architecture of the VM and build the library path accordingly (at least for the architectures where Oracle provides a JVM, that's amd64/i386 and maybe the arm variants). So the logic would be: Are we running on amd64/i386? - Yes : Check if the VM is 32 or 64 bits (by parsing the output of java -d32 -version and java -d64 -version) - 32 bits : set the library path to /usr/lib:/usr/lib/i386-linux-gnu - 64 bits : set the library path to /usr/lib:/usr/lib/x86_64-linux-gnu - No : this is a Debian VM and the path is ok by default, do nothing Building a proper library path for an Oracle JRE is maybe outside of debian policy ? and beyond debian-java responsabilities ? Maybe what was not clear is that jexec does have the proper behavior, jarwrapper should only be used only if the first binfmts (=jexec) fails to execute. In summary: 1. Make jexec the default binfmts (before jarwrapper) 2. Update jarwrapper to use the above mentionned `java -d32|64` trick to build the library path. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770907: /sbin/trackpad: trackpad command will not enable tap to click
Hi, what hardware exactly does this happen on? Please provide a copy of your boot log detailing the devices detected. Note that the existence of /dev/adb does not necessarily imply presence of ADB support by your hardware, or the presence of a trackpad device on the ADB bus in particular. Regards, Michael Schmitz Package: powerpc-utils Version: 1.1.3-25 Severity: normal File: /sbin/trackpad Tags: d-i Dear Maintainer, For some reason I am getting this error when I try to enable tap to click using the trackpad command. rican-linux@debian-ppc:~/Documents$ sudo trackpad tap [sudo] password for rican-linux: writing /dev/adb: No such device or address However I do have that device... rican-linux@debian-ppc:~/Documents$ ls -l /dev/adb crw--- 1 root root 56, 0 Nov 24 21:44 /dev/adb rican-linux@debian-ppc:~/Documents$ -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: powerpc (ppc) Kernel: Linux 3.16-2-powerpc Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages powerpc-utils depends on: ii libc6 2.19-13 powerpc-utils recommends no packages. powerpc-utils 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#770404: systemd: breaks lightdm, does not start anymore
Actually, I think we can settle it that way (which would help fixing fixing bug #770633: Everytime we have a service which provided an alternative, we declare an Alias=this alternative.service name. Then, we patch systemctl to update the alternative file (if it exists) on this alias name for those units having an alias. That's fixing the systemctl enable service - put in sync the alternative. Then, we patch update-alternative to look for a correspond .service name, and if any (and systemctl installed), we call systemctl enable --force service (and need to find a way to not have the circular dependency on both, like checking the alternatives file directly) That's fixing the update-alternative command - syncing on systemctl state. With this, we can even remove the tweaked postinst for the DMs as the normal alternative prompts will do the right thing. That of course wouldn't fix people changing the alternatives file by hand, but I'm unsure we can gracefully handle this. What do you think? Didier -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770914: unblock: ruby-bootstrap-sass/2.3.1.0-4
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Dear Release team, This upload fixes RC bug #770913. debdiff is attahced. Thanks Praveen diff -Nru ruby-bootstrap-sass-2.3.1.0/debian/changelog ruby-bootstrap-sass-2.3.1.0/debian/changelog --- ruby-bootstrap-sass-2.3.1.0/debian/changelog2014-11-22 21:20:31.0 +0530 +++ ruby-bootstrap-sass-2.3.1.0/debian/changelog2014-11-25 13:33:35.0 +0530 @@ -1,3 +1,9 @@ +ruby-bootstrap-sass (2.3.1.0-4) unstable; urgency=medium + + * Ship assets (closes: #770913) + + -- Pirate Praveen prav...@debian.org Tue, 25 Nov 2014 13:33:31 +0530 + ruby-bootstrap-sass (2.3.1.0-3) unstable; urgency=medium * Rebuild for ruby 2.1 compatibility. diff -Nru ruby-bootstrap-sass-2.3.1.0/debian/install ruby-bootstrap-sass-2.3.1.0/debian/install --- ruby-bootstrap-sass-2.3.1.0/debian/install 1970-01-01 05:30:00.0 +0530 +++ ruby-bootstrap-sass-2.3.1.0/debian/install 2014-11-25 13:32:41.0 +0530 @@ -0,0 +1 @@ +vendor usr/share/ruby-bootstrap-sass diff -Nru ruby-bootstrap-sass-2.3.1.0/debian/patches/engine-root.patch ruby-bootstrap-sass-2.3.1.0/debian/patches/engine-root.patch --- ruby-bootstrap-sass-2.3.1.0/debian/patches/engine-root.patch 1970-01-01 05:30:00.0 +0530 +++ ruby-bootstrap-sass-2.3.1.0/debian/patches/engine-root.patch 2014-11-25 13:32:41.0 +0530 @@ -0,0 +1,15 @@ +Index: ruby-bootstrap-sass/lib/bootstrap-sass/engine.rb +=== +--- ruby-bootstrap-sass.orig/lib/bootstrap-sass/engine.rb ruby-bootstrap-sass/lib/bootstrap-sass/engine.rb +@@ -1,7 +1,8 @@ + module Bootstrap + module Rails + class Engine ::Rails::Engine ++ config.root = '/usr/share/ruby-bootstrap-sass' + # Rails, will you please look in our vendor? kthx + end + end +-end +\ No newline at end of file ++end diff -Nru ruby-bootstrap-sass-2.3.1.0/debian/patches/series ruby-bootstrap-sass-2.3.1.0/debian/patches/series --- ruby-bootstrap-sass-2.3.1.0/debian/patches/series 1970-01-01 05:30:00.0 +0530 +++ ruby-bootstrap-sass-2.3.1.0/debian/patches/series 2014-11-25 13:32:41.0 +0530 @@ -0,0 +1 @@ +engine-root.patch signature.asc Description: OpenPGP digital signature
Bug#767653:
Hi Tobi, * Tobias Frost t...@debian.org [2014-11-24 22:12]: Ok, pulled from the git and comparing to the version currently in Jessie: As we are in the freeze, you need to create targeted fixes for RC Bugs only.* So the doxygen one isn't. This seems to be coming from a new Doxygen version and is only needed for debclean , but I can revert it without problems. And be more detailed in freeze time: Will do. I'd write Do not ship but create at install time the files ... Is the register modules change needed for 767653? (I assume yes, but then the changelog should make that clear too) That's actually all part of one change, but ended up in two commits, so git-dch made two lines out of it. Will change the changelog. Why are you moving the util-binaries to the libary package? I would find it better to depend on the utils package instead, (especially as you should consider implement multi-arch for Jessie+1) openni-utils contains sample applications depending on libopenni0. Leaving niReg/niLicense in there would generate a circular dependency, as we need them in the libopenni0 postinst. Is there an other option? Declaring a circular dependency is not a problem here and well handled by dpkg. When postinst is called, both packages are guaranteed to be unpacked, so the library / binaries are in place at this point of time. (See Policy §7.2) Cheers Jochen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767903: fixed in pcre3 1:8.36-1
Control: reopen -1 Hi, On Mon, Nov 24, 2014 at 11:49:23PM +, Mark Baker wrote: To: 767903-cl...@bugs.debian.org pcre3 (1:8.36-1) unstable; urgency=medium . * New upstream release Did you read the freeze policy? This part will need to be reverted. * Upped shlibs dependency to 8.35 (Closes: #767903) This part of the issue is actually #767907, not #767903 * Upstream patch for heap buffer overflow, CVE-2014-8964 (Closes: #770478) Cheers, Ivo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770915: ITP: utox -- uTox is a lightweight audio/video chat client based on the secure tox protocol.
Package: wnpp Severity: wishlist Owner: gaffa ga...@folkemagt.dk * Package name: utox Version : 0+git20141121 Upstream Author : notsecure * URL : https://github.com/notsecure/uTox/ * License : GPL-3 Programming Lang: C Description : uTox is a lightweight audio/video chat client based on the secure tox protocol. Tox is a free P2P audio/video protocol that requires no configuration. Using torrent-style DHT, peers can find the IP of other peers by using their Tox ID. Once the IP is obtained, peers can initiate a secure connection with each other and exchange messages, send files, start video chats, etc. using encrypted communications. I have already created a package for the version mentioned above. There are no official source tarballs and no version tags on the VCS. This package depends on libtoxcore. I've packaged libtoxcore and is currently waiting for replies to the ITP bug report, before I request a sponsor. The package is uploaded to mentors.debian.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770908: [Aptitude-devel] Bug#770908: aptitude does not know about the new _apt user. Must use apt-get update as a workaround
Control: forcemerge -1 764506 Control: tag -1 + stretch Hi Dan, 積丹尼 Dan Jacobson wrote: Severity: grave aptitude does not know about the new _apt user in e.g., apt 1.1~exp8. Why should that be grave (in the current situation)? aptitude does not work well with apt from experimental yet, yes, see #764506 and #762846. But since it's apt from experimental, it's not release-critical for Jessie. Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767653:
Hi Tobi, * Tobias Frost t...@debian.org [2014-11-24 22:12]: Ok, pulled from the git and comparing to the version currently in Jessie: As we are in the freeze, you need to create targeted fixes for RC Bugs only.* So the doxygen one isn't. This seems to be coming from a new Doxygen version and is only needed for debclean , but I can revert it without problems. And be more detailed in freeze time: Will do. I'd write Do not ship but create at install time the files ... Is the register modules change needed for 767653? (I assume yes, but then the changelog should make that clear too) That's actually all part of one change, but ended up in two commits, so git-dch made two lines out of it. Will change the changelog. Why are you moving the util-binaries to the libary package? I would find it better to depend on the utils package instead, (especially as you should consider implement multi-arch for Jessie+1) openni-utils contains sample applications depending on libopenni0. Leaving niReg/niLicense in there would generate a circular dependency, as we need them in the libopenni0 postinst. Is there an other option? Declaring a circular dependency is not a problem here and well handled by dpkg. When postinst is called, both packages are guaranteed to be unpacked, so the library / binaries are in place at this point of time. (See Policy §7.2) Cheers Jochen I wanted to point you to Policy §8.2 as well, but forgot in the rush. -- it is actually forbidden to have the binaries in the libary package. (-- some simpications applied; the Policy has details.) -- tobi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770812: tasksel: task-sysvinit to allow easy installation of non-systemd systems
HI, Besides: I'm not sure where you got the impression I owe you anything. Any user writing a reasonable bug report deserves to be treated with respect, and deserves a useful answer (spam and duplicate reports are an obvious exception). Not just a no (which is an unwritten f... off) Otherwise, our users will stop reporting bugs at all, if you treat them this way. It's bad enough that you won't even consider our current #1 installer feature request as future wishlist item. This itself is already highly disrespectful, and I'm not surprised that some people are annoyed, if all they get in return are shut up messages. I guess we'll see a forked installer sooner or later because of that. (But I won't be doing that, I do use systemd myself) Regards, Erich -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770917: devhelp: devhelp.el overwrites standard Emacs keybindings
Package: devhelp Version: 3.14.0-1 Severity: normal Dear Maintainer, The devhelp.el defines a global keybinding for F11: (global-set-key [f11] 'devhelp-word-at-point) But in Emacs 24 F11 is already bound to toggle-frame-fullscreen. Devhelp should not overwrite the default Emacs keybindings. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=nl_BE.utf8, LC_CTYPE=nl_BE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages devhelp depends on: ii libatk1.0-0 2.14.0-1 ii libc6 2.19-13 ii libcairo-gobject2 1.14.0-2.1 ii libcairo2 1.14.0-2.1 ii libdevhelp-3-2 3.14.0-1 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 it libglib2.0-02.42.1-1 ii libgtk-3-0 3.14.5-1 ii libjavascriptcoregtk-3.0-0 2.4.7-2 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii libsoup2.4-12.48.0-1 ii libwebkit2gtk-3.0-252.4.7-2 Versions of packages devhelp recommends: ii libglib2.0-doc 2.42.1-1 ii libgtk-3-doc 3.14.5-1 ii libpango1.0-doc 1.36.8-3 devhelp suggests no packages. -- Configuration Files: /etc/emacs/site-start.d/50devhelp.el changed [not included] -- 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#770916: failed to find asset during precompile
package: ruby-handlebars-assets version: 0.15-2 severity: grave I think this is an upstream bug (config.root is not respected) ** Execute assets:precompile I, [2014-11-25T08:23:13.301523 #17268] INFO -- : Writing /usr/share/diaspora/public/assets/mobile-9c8138c58dc33879dd5b438b97865c58.js I, [2014-11-25T08:23:13.745973 #17268] INFO -- : Writing /usr/share/diaspora/public/assets/profile-bd746989c4a102d4699cd598683f9f58.js rake aborted! Errno::ENOENT: No such file or directory @ rb_sysopen - /usr/lib/ruby/vendor/assets/javascripts/handlebars.js (in /usr/share/diaspora/app/assets/templates/activity-streams-photo_tpl.jst.hbs) /usr/lib/ruby/vendor_ruby/handlebars_assets/handlebars.rb:35:in `read' /usr/lib/ruby/vendor_ruby/handlebars_assets/handlebars.rb:35:in `read' /usr/lib/ruby/vendor_ruby/handlebars_assets/handlebars.rb:35:in `source' /usr/lib/ruby/vendor_ruby/handlebars_assets/handlebars.rb:27:in `apply_patches_to_source' /usr/lib/ruby/vendor_ruby/handlebars_assets/handlebars.rb:31:in `context' /usr/lib/ruby/vendor_ruby/handlebars_assets/handlebars.rb:10:in `precompile' /usr/lib/ruby/vendor_ruby/handlebars_assets/handlebars_template.rb:76:in `compile_default' /usr/lib/ruby/vendor_ruby/handlebars_assets/handlebars_template.rb:65:in `evaluate' /usr/lib/ruby/vendor_ruby/tilt/template.rb:103:in `render' /usr/lib/ruby/vendor_ruby/sprockets/context.rb:197:in `block in evaluate' /usr/lib/ruby/vendor_ruby/sprockets/context.rb:194:in `each' /usr/lib/ruby/vendor_ruby/sprockets/context.rb:194:in `evaluate' /usr/lib/ruby/vendor_ruby/sprockets/processed_asset.rb:12:in `initialize' /usr/lib/ruby/vendor_ruby/sprockets/base.rb:379:in `new' /usr/lib/ruby/vendor_ruby/sprockets/base.rb:379:in `block in build_asset' /usr/lib/ruby/vendor_ruby/sprockets/base.rb:400:in `circular_call_protection' /usr/lib/ruby/vendor_ruby/sprockets/base.rb:378:in `build_asset' /usr/lib/ruby/vendor_ruby/sprockets/index.rb:94:in `block in build_asset' /usr/lib/ruby/vendor_ruby/sprockets/caching.rb:58:in `cache_asset' /usr/lib/ruby/vendor_ruby/sprockets/index.rb:93:in `build_asset' /usr/lib/ruby/vendor_ruby/sprockets/base.rb:287:in `find_asset' /usr/lib/ruby/vendor_ruby/sprockets/index.rb:61:in `find_asset' /usr/lib/ruby/vendor_ruby/sprockets/processed_asset.rb:111:in `block in resolve_dependencies' /usr/lib/ruby/vendor_ruby/sprockets/processed_asset.rb:105:in `each' /usr/lib/ruby/vendor_ruby/sprockets/processed_asset.rb:105:in `resolve_dependencies' /usr/lib/ruby/vendor_ruby/sprockets/processed_asset.rb:97:in `build_required_assets' /usr/lib/ruby/vendor_ruby/sprockets/processed_asset.rb:16:in `initialize' /usr/lib/ruby/vendor_ruby/sprockets/base.rb:379:in `new' /usr/lib/ruby/vendor_ruby/sprockets/base.rb:379:in `block in build_asset' /usr/lib/ruby/vendor_ruby/sprockets/base.rb:400:in `circular_call_protection' /usr/lib/ruby/vendor_ruby/sprockets/base.rb:378:in `build_asset' /usr/lib/ruby/vendor_ruby/sprockets/index.rb:94:in `block in build_asset' /usr/lib/ruby/vendor_ruby/sprockets/caching.rb:58:in `cache_asset' /usr/lib/ruby/vendor_ruby/sprockets/index.rb:93:in `build_asset' /usr/lib/ruby/vendor_ruby/sprockets/base.rb:287:in `find_asset' /usr/lib/ruby/vendor_ruby/sprockets/index.rb:61:in `find_asset' /usr/lib/ruby/vendor_ruby/sprockets/bundled_asset.rb:16:in `initialize' /usr/lib/ruby/vendor_ruby/sprockets/base.rb:382:in `new' /usr/lib/ruby/vendor_ruby/sprockets/base.rb:382:in `build_asset' /usr/lib/ruby/vendor_ruby/sprockets/index.rb:94:in `block in build_asset' /usr/lib/ruby/vendor_ruby/sprockets/caching.rb:58:in `cache_asset' /usr/lib/ruby/vendor_ruby/sprockets/index.rb:93:in `build_asset' /usr/lib/ruby/vendor_ruby/sprockets/base.rb:287:in `find_asset' /usr/lib/ruby/vendor_ruby/sprockets/index.rb:61:in `find_asset' /usr/lib/ruby/vendor_ruby/sprockets/manifest.rb:211:in `block in find_asset' /usr/lib/ruby/vendor_ruby/sprockets/manifest.rb:257:in `benchmark' /usr/lib/ruby/vendor_ruby/sprockets/manifest.rb:210:in `find_asset' /usr/lib/ruby/vendor_ruby/sprockets/manifest.rb:119:in `block in compile' /usr/lib/ruby/vendor_ruby/sprockets/manifest.rb:118:in `each' /usr/lib/ruby/vendor_ruby/sprockets/manifest.rb:118:in `compile' /usr/lib/ruby/vendor_ruby/sprockets/rails/task.rb:61:in `block (3 levels) in define' /usr/lib/ruby/vendor_ruby/rake/sprocketstask.rb:146:in `with_logger' /usr/lib/ruby/vendor_ruby/sprockets/rails/task.rb:60:in `block (2 levels) in define' /usr/lib/ruby/vendor_ruby/rake/task.rb:240:in `call' /usr/lib/ruby/vendor_ruby/rake/task.rb:240:in `block in execute' /usr/lib/ruby/vendor_ruby/rake/task.rb:235:in `each' /usr/lib/ruby/vendor_ruby/rake/task.rb:235:in `execute' /usr/lib/ruby/vendor_ruby/rake/task.rb:179:in `block in invoke_with_call_chain' /usr/lib/ruby/2.1.0/monitor.rb:211:in `mon_synchronize' /usr/lib/ruby/vendor_ruby/rake/task.rb:172:in `invoke_with_call_chain' /usr/lib/ruby/vendor_ruby/rake/task.rb:165:in `invoke' /usr/lib/ruby/vendor_ruby/rake/application.rb:150:in `invoke_task'
Bug#770918: Two CVEs against FLAC
Package: flac Version: 1.3.0-2+b1 Severity: serious Tags: security From: http://lists.xiph.org/pipermail/flac-dev/2014-November/005226.html Google Security Team member, Michele Spagnuolo, recently found two potential problems in the FLAC code base. They are : CVE-2014-9028 : Heap buffer write overflow CVE-2014-8962 : Heap buffer read overflow For Linux distributions, the specific fixes for these two CVEs are available from Git here: https://git.xiph.org/?p=flac.git;a=commit;h=fcf0ba06ae12ccd7c67cee3c8d948df15f946b85 https://git.xiph.org/?p=flac.git;a=commit;h=5b3033a2b355068c11fe637e14ac742d273f076e and are simple enough that they should apply cleanly to the last official release 1.3.0 and possibly even the previous one, 1.2.1. A pre-release (version 1.3.1pre1) for the next version which includes these fixes and more is available here: http://downloads.xiph.org/releases/flac/beta/ A full release (version 1.3.1) will be available in the next couple of days. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing'), (800, 'unstable'), (500, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.17-rc5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_AU.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages flac depends on: ii libc6 2.19-13 ii libflac8 1.3.0-2+b1 flac recommends no packages. flac 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#770919: unblock: haskell-src-exts/1.14.0.1-4
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Please unblock package haskell-src-exts someone figured out how to build this package on mips*, the change is an additional flag for gcc that does not affect the resulting binaries. This allowed a few reverse dependencies to build, I assume these will migrate automatically with it (as their source package is already in testing). The output of the tool you’d run anyways is attached. unblock haskell-src-exts/1.14.0.1-4 - -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 armhf Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlR0P/0ACgkQ9ijrk0dDIGxXLgCgmgcb6MjDKMhH4QsgHAXGzUBC BewAn3Wg9vjJVSRpv1j+BGhURJciMk2L =PdxI -END PGP SIGNATURE- Base version: haskell-src-exts_1.14.0.1-1 from testing Target version: haskell-src-exts_1.14.0.1-4 from unstable No hints in place. Excuses: haskell-src-exts (1.14.0.1-1 to 1.14.0.1-3) Maintainer: Debian Haskell Group Too young, only 0 of 5 days old Not touching package due to block request by freeze (check https://release.debian.org/jessie/freeze_policy.html if update is needed) Not considered changelog | 19 +++ rules | 17 + 2 files changed, 36 insertions(+) [0;0mgpgv: Schlüsselblockhilfsmittel`/home/nomeata/.gnupg/trustedkeys.gpg': Fehler beim Öffnen der Datei[0;0m [0;0mgpgv: Unterschrift vom Sa 07 Jun 2014 22:51:45 UTC mittels RSA-Schlüssel ID F0FBF51F[0;0m [0;0mgpgv: Unterschrift kann nicht geprüft werden: Öffentlicher Schlüssel nicht gefunden[0;0m [0;0mdpkg-source: Warnung: Fehler beim Überprüfen der Signatur von /tmp/tmpBXcGRv/haskell-src-exts_1.14.0.1-1.dsc[0;0m [0;0mgpgv: Schlüsselblockhilfsmittel`/home/nomeata/.gnupg/trustedkeys.gpg': Fehler beim Öffnen der Datei[0;0m [0;0mgpgv: Unterschrift vom Mo 24 Nov 2014 22:45:39 UTC mittels RSA-Schlüssel ID F0FBF51F[0;0m [0;0mgpgv: Unterschrift kann nicht geprüft werden: Öffentlicher Schlüssel nicht gefunden[0;0m [0;0mdpkg-source: Warnung: Fehler beim Überprüfen der Signatur von /tmp/tmpBXcGRv/haskell-src-exts_1.14.0.1-4.dsc[0;0m [1;32mdiff -Nru haskell-src-exts-1.14.0.1/debian/changelog haskell-src-exts-1.14.0.1/debian/changelog[0;0m [1;31m--- haskell-src-exts-1.14.0.1/debian/changelog 2014-06-07 22:43:32.0 +[0;0m [1;34m+++ haskell-src-exts-1.14.0.1/debian/changelog 2014-11-24 21:45:09.0 +[0;0m [1;35m@@ -1,3 +1,22 @@[0;0m [1;34m+haskell-src-exts (1.14.0.1-4) unstable; urgency=medium[0;0m [1;34m+[0;0m [1;34m+ * s/optoins/options/. sigh. [0;0m [1;34m+[0;0m [1;34m+ -- Joachim Breitner nome...@debian.org Mon, 24 Nov 2014 22:45:09 +0100[0;0m [1;34m+[0;0m [1;34m+haskell-src-exts (1.14.0.1-3) unstable; urgency=medium[0;0m [1;34m+[0;0m [1;34m+ * Fix passing ggc-min-expand=10 to gcc. [0;0m [1;34m+[0;0m [1;34m+ -- Joachim Breitner nome...@debian.org Mon, 24 Nov 2014 19:21:17 +0100[0;0m [1;34m+[0;0m [1;34m+haskell-src-exts (1.14.0.1-2) unstable; urgency=medium[0;0m [1;34m+[0;0m [1;34m+ * Pass ggc-min-expand=10 to gcc, might make this compile on mips*. Thanks to[0;0m [1;34m+Dejan Latinovic for the patch. Closes: #770830[0;0m [1;34m+[0;0m [1;34m+ -- Joachim Breitner nome...@debian.org Mon, 24 Nov 2014 16:07:29 +0100[0;0m [1;34m+[0;0m [0;0m haskell-src-exts (1.14.0.1-1) unstable; urgency=medium[0;0m [0;0m [0;0m [0;0m * New upstream release[0;0m [1;32mdiff -Nru haskell-src-exts-1.14.0.1/debian/rules haskell-src-exts-1.14.0.1/debian/rules[0;0m [1;31m--- haskell-src-exts-1.14.0.1/debian/rules 2012-10-13 11:42:14.0 +[0;0m [1;34m+++ haskell-src-exts-1.14.0.1/debian/rules 2014-11-24 21:44:45.0 +[0;0m [1;35m@@ -2,8 +2,25 @@[0;0m [0;0m [0;0m [0;0m DEB_CABAL_PACKAGE=src-exts[0;0m [0;0m DEB_BUILD_DEPENDENCIES = build-arch[0;0m [1;34m+[0;0m [0;0m DEB_SETUP_GHC6_CONFIGURE_ARGS = --ghc-options=+RTS -V0 -RTS[0;0m [0;0m [0;0m [1;34m+# haskell-src-exts needs a lot of memory during compilation.[0;0m [1;34m+# Unfortunately, this amount of memory is not available on all platforms,[0;0m [1;34m+# and error: virtual memory exhausted: Cannot allocate memory. could appear.[0;0m [1;34m+# [0;0m [1;34m+# In this case possible solution could be using ggc-min-expand.[0;0m [1;34m+# This parameter specifies the minimum percentage by which the[0;0m [1;34m+# garbage collector’s heap should be allowed to expand between collections.[0;0m [1;34m+# Tuning this may improve compilation speed; it has no effect on code generation.[0;0m [1;34m+#[0;0m [1;34m+#
Bug#770920: RM: haskell-ed25519 -- ROM; RC-buggy, no upstream reaction, leaf package
Package: ftp.debian.org Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, this package is RC buggy, which did not bother anyone (including upstream at https://github.com/thoughtpolice/hs-ed25519/issues/3), and it is not used by any other package in Debian. Seems to be safe to just remove this. Greetings, Joachim -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlR0QoMACgkQ9ijrk0dDIGz7lwCgpJClM2pLiNK98Qi5xyKyHncF CQsAoJGYU2ZYKiipkqzZ/s2MscPZj3pP =LXf7 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763599: Workaround
Hello, I found a workaround. Download the latest source from sourceforge ./configure --disable-credssp --disable-smartcard make make install Worked for me. It looks like the developers need to fix the fallback routines if credssp fails. Regards, Simon
Bug#766464: gksu pluma any_file sets the ownership of /run/user/1000/dconf/user to root:root
Hi, Thank you so much for investigating this issue. I've been busy with my job and various bugs so I never had the time to look into it. However, I've checked systemd's source code and found out the mentioned commit [1] is already there. No wonder - the commit is one year old, and the version of systemd in Debian Testing is already 215. You can check the code yourself to see that (just remember that pam-module.c has been renamed to pam_systemd.c). Also, Debian maintainers have made a lot of patches for systemd, but the only patch that modifies the files in question is [2], and it seems to be minor. So, either the mentioned commit didn't fix the problem completely, or there were some more changes along the way that made the problem appear again. [1] http://cgit.freedesktop.org/systemd/systemd/commit/?id=baae0358f349870544884e405e82e4be7d8add9f [2] http://sources.debian.net/src/systemd/215-6/debian/patches/Start-logind-on-demand-via-libpam-systemd.patch
Bug#770843: gcc vs. clang
Some additional info: There are no problems with GCC, but clang reports those errors. -- Jochen Topf joc...@remote.org http://www.jochentopf.com/ +49-173-7019282 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770921: synaptic: Sometimes says (erroneusly) that packages are not authenticated
Package: synaptic Version: 0.81.2 Severity: normal Dear Maintainer, sometimes synaptic says that the packages are not authenticated. Here are the steps to reproduce the problem in my system: * Select one or some packages (today I did this with the apache2 packages I have to upgrade) * Right click, select Mark for removal * Click Cancel in the window that asks confirmation to remove related packages * Reselect the same (apache2 packages in my case) packages as before * Right click, select Mark for upgrade * Select Apply in the toolbar Now synaptic tells that the packages I am about to install are not authenticated. To make the warning go away I have to unmark the packages, reload, and then select Mark for upgrade. This happens everytime I made the mistake to click on remove instead of upgrade. Kind regards, Mark -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages synaptic depends on: ii hicolor-icon-theme 0.13-1 ii libapt-inst1.5 1.0.9.3 ii libapt-pkg4.12 1.0.9.3 ii libatk1.0-0 2.14.0-1 ii libc62.19-7 ii libcairo-gobject21.14.0-2.1 ii libcairo21.14.0-2.1 ii libept1.4.12 1.0.12.1 ii libgcc1 1:4.9.1-19 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglib2.0-0 2.42.0-2 ii libgtk-3-0 3.14.4-2 ii libpango-1.0-0 1.36.8-2 ii libpangocairo-1.0-0 1.36.8-2 ii libstdc++6 4.9.1-19 ii libvte-2.90-91:0.36.3-1 ii libx11-6 2:1.6.2-3 ii libxapian22 1.2.19-1 ii libxext6 2:1.3.3-1 ii zlib1g 1:1.2.8.dfsg-2 Versions of packages synaptic recommends: ii gksu 2.0.2-7 ii libgtk2-perl 2:1.2492-3 ii policykit-10.105-7 ii rarian-compat 0.8.1-6 Versions of packages synaptic suggests: ii apt-xapian-index 0.47 ii deborphan1.7.28.8-0.1 pn dwww none ii menu 2.1.47 ii software-properties-gtk 0.92.25debian1 ii tasksel 3.29 -- no debconf information -- . ''`. | GPG Public Key : 0xCD542422 - Download it from http://is.gd/fOa7Vm : :' : | GPG Fingerprint : 0823 A40D F31B 67A8 5621 AD32 E293 A2EB CD54 2422 `. `'` | Powered by Debian GNU/Linux, http://www.debian.org `-| Try not. Do, or do not. There is no try. - Master Yoda, TESB. signature.asc Description: Digital signature
Bug#766670: RC bug in stable and oldstable for getmail4
Hi, On Sun, 23 Nov 2014, Osamu Aoki wrote: By the way, I uploaded getmail4_4.46.0-1~bpo70+1_amd64 We can consider a new upstream version for squeeze-lts and we can ask the security team's opinion for wheezy. Would you like to prepare a 4.46.0-1~deb6u1.dsc working in squeeze and submit it for review to debian-...@lists.debian.org ? It would be nice if you could test it though, because we don't have many testers before release... https://ftp-master.debian.org/new/getmail4_4.46.0-1~bpo70%2B1.html This can probably be renumbered 4.46.0-1~deb7u1.dsc and submitted to the security team ? Or does it depend on other packages from backports ? Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: http://www.freexian.com/services/debian-lts.html Learn to master Debian: http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770388: apt-cache as a non-root user if a APT .list file is not readable
Hi David, thank you for your thorough answer. On Sun, Nov 23, 2014 at 03:20:26PM +0100, David Kalnischkies wrote: Hi Jonathan, On Thu, Nov 20, 2014 at 10:35:40PM +0100, Jonathan Ballet wrote: I tracked down the problem using strace and it seems that if a APT .list file is not readable by a non-root user, apt-cache (in this case) goes much, much slower: Yes, but this isn't a bug. The sources.list tells us which repositories to get data from and by extension which files on disk contain this data. If the current user can't read the sources.list files, apt will not know which files are to be used and which ones are stale. The binary cache it deploys to avoid reparsing all these files all the time will be considered invalid as it contains data from sources which (might or might not) be still in the unreadable sources.list file. The only reason we can be fast by using a binary cache is that we know that it is current – otherwise we would need to be a lot more careful while working with the data files which means we are a lot slower (as you experienced). So, this is all by design… In other words: If you want to use apt, the user you run it with needs read access to sources.list files. There is no point in forbidding read access here anyway as you /can/ force apt to consider the binary cache as valid and hence extract the data or lookup the filenames in the lists directory or or or. I understand this design decision, my use-case was more like: I created a sources.list file with the wrong permission, and my normal user couldn't read it. As such, running apt-cache without being root was much, much slower. As I usually never use apt-cache as root and that nothing reports that this file can't be read and that apt-cache is going to use this slower codepath, I thought there was a much more serious problem on my machine than just this file permission issue. In the end, I had to resort to strace to discover the real underlying problem, which is not really intuitive although 1. this situation is kind of abnormal (I understand what you said this way) and 2. the fix is really simple. Is there a way this issue could have been avoided? Best regards, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770922: ruby-ferret: FTBFS on arm64
Source: ruby-ferret Version: 0.11.8.5-1 It failed to build on arm64: http://buildd.debian.org/status/package.php?p=ruby-ferretsuite=sid The error was: posh.h:516:4: error: #error POSH cannot determine target CPU # error POSH cannot determine target CPU It seems trivial to fix. You can just add something like this in ext/posh.h just before where the error is generated: #if defined __aarch64__ # define POSH_CPU_AARCH64 1 # define POSH_CPU_STRING AArch64 #endif -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770923: xserver-xorg-input-synaptics: Clickpad SoftButtons stop working after some clicks
Package: xserver-xorg-input-synaptics Version: 1.8.1-1 Severity: important Tags: upstream Dear Maintainer, I just set up a Lenovo T440p and defined a config file for the soft buttons on the top since they did not work: # /usr/share/X11/xorg.conf.d/thinkpad_clickpad.conf Section InputClass Identifier tp only with clickpad buttons MatchDriver synaptics # Option SoftButtonAreas RBL RBR RBT RBB MBL MBR MBT MBB Option SoftButtonAreas 75% 0 0 35% 52% 75% 0 35% Option HasSecondarySoftButtons off Option AreaBottomEdge 1 #disable moving but not buttons EndSection After that I noticed that the buttons work at first but after a about 30 seconds they stop working. I can't click anything. I reenabled the touchpad (AreaBottomEdge) to see if it makes a difference but it stops working the same moment, even without clicking at that moment. Events are still visible when using evtest. But I can't say if they are correct or something, there are events when pressing the pad and the coordinates appropriate when moving. I would be nice if you could look into it. There is the xorg log with information about the Clickpad. -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Aug 7 09:49 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 2397280 Nov 3 22:52 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 00:02.0 VGA compatible controller [0300]: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) 02:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK208M [GeForce GT 730M] [10de:1290] (rev a1) /etc/X11/xorg.conf does not exist. /etc/X11/xorg.conf.d does not exist. KMS configuration files: /etc/modprobe.d/radeon-kms.conf: options radeon modeset=1 Kernel version (/proc/version): --- Linux version 3.16.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.8.3 (Debian 4.8.3-13) ) #1 SMP Debian 3.16.7-2 (2014-11-06) Xorg X server log files on system: -- -rw-r--r-- 1 root root 35973 Nov 25 09:37 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [ 2261.115] X.Org X Server 1.16.1.901 (1.16.2 RC 1) Release Date: 2014-11-02 [ 2261.115] X Protocol Version 11, Revision 0 [ 2261.115] Build Operating System: Linux 3.2.0-4-amd64 x86_64 Debian [ 2261.115] Current Operating System: Linux spike 3.16.0-4-amd64 #1 SMP Debian 3.16.7-2 (2014-11-06) x86_64 [ 2261.115] Kernel command line: BOOT_IMAGE=/vmlinuz-3.16.0-4-amd64 root=/dev/mapper/spike-root ro quiet [ 2261.115] Build Date: 03 November 2014 09:44:08PM [ 2261.115] xorg-server 2:1.16.1.901-1 (http://www.debian.org/support) [ 2261.115] Current version of pixman: 0.32.6 [ 2261.115]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 2261.115] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 2261.116] (==) Log file: /var/log/Xorg.0.log, Time: Tue Nov 25 09:27:50 2014 [ 2261.116] (==) Using system config directory /usr/share/X11/xorg.conf.d [ 2261.116] (==) No Layout section. Using the first Screen section. [ 2261.116] (==) No screen section available. Using defaults. [ 2261.116] (**) |--Screen Default Screen Section (0) [ 2261.116] (**) | |--Monitor default monitor [ 2261.116] (==) No monitor specified for screen Default Screen Section. Using a default monitor configuration. [ 2261.116] (==) Automatically adding devices [ 2261.116] (==) Automatically enabling devices [ 2261.116] (==) Automatically adding GPU devices [ 2261.116] (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. [ 2261.116]Entry deleted from font path. [ 2261.116] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [ 2261.116] (==) ModulePath set to /usr/lib/xorg/modules [ 2261.116] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 2261.116] (II) Loader magic: 0x7f8aa5b03d80 [ 2261.116] (II) Module ABI versions: [ 2261.116]X.Org ANSI C Emulation: 0.4 [ 2261.116]X.Org Video Driver: 18.0 [ 2261.116]X.Org XInput driver : 21.0 [ 2261.116]X.Org Server Extension : 8.0 [ 2261.116] (II) xfree86: Adding drm device (/dev/dri/card1) [ 2261.188] (II) xfree86: Adding drm device (/dev/dri/card0) [ 2261.860] (--) PCI:*(0:0:2:0) 8086:0416:17aa:221d rev 6, Mem @ 0xf100/4194304,
Bug#770925: wanna-build patches to support foreign-arch Build-Depends
Package: src:sbuild Severity: normal Hi. The cross toolchains now in unstable (for instance https://tracker.debian.org/pkg/cross-gcc-4.9-armhf) have Build-Depends on both the host and target architecture. This was not supported by wanna-build, and a patch series to add this support is available here: http://anonscm.debian.org/cgit/users/dkogan-guest/wanna-build.git/ I developed and tested these by setting up a wanna-build instance as described here: https://wiki.debian.org/DebianWannaBuildInfrastructureOnOneServer https://wiki.debian.org/SetupBuildServiceForWanna-build The setup also required a patch posted earlier: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765111 I suspect this extra patch is only required because of my specific setup, since presumably wanna-build has been working just fine in the wild. On my test box I see wanna-build refuse to set a cross-gcc source package to Needs-Build unless all Build-Depends are satisfied, both native and foreign. This is the test of basic functionality, and it appears to work. I'll run more thorough tests if somebody has specific requests along those lines. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770924: RFS: abiword/3.0.0-8 [QA] -- fixes #766845
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for the abiword package. * Package name: abiword Version : 3.0.0-8 Upstream Author : AbiSource.com * URL : http://www.abisource.com/ * License : GPL-2+ Section : gnome It builds those binary packages: abiword- efficient, featureful word processor with collaboration abiword-common - efficient, featureful word processor with collaboration -- common abiword-dbg - debugging symbols for abiword word processor abiword-plugin-grammar - grammar checking plugin for AbiWord abiword-plugin-mathview - equation editor plugin for AbiWord libabiword-3.0 - efficient, featureful word processor with collaboration -- shared libabiword-3.0-dev - efficient, featureful word processor with collaboration -- develo To access further information about this package, please visit the following URL: http://mentors.debian.net/package/abiword Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/a/abiword/abiword_3.0.0-8.dsc Changes since the last upload: * QA upload. * Apply an upstream patch to fix format painter bug. (Closes: #766845). -- Edward. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770889: ITP: python-pymysql -- Pure-Python MySQL driver
On 11/25/2014 02:20 PM, Brian May wrote: On 25 Nov 2014 09:24, Thomas Goirand z...@debian.org mailto:z...@debian.org wrote: This package contains a pure-Python MySQL client library. The goal of PyMySQL is to be a drop-in replacement for MySQLdb and work on CPython, PyPy, IronPython and Jython. This is yet another new dependency for OpenStack. Note that this package is interesting because it has Python 3 support. I assume you know about the alternatives for Python 3 support, but just in case, have a look at: https://packages.debian.org/sid/python3-mysql.connector Bug#768096: ITP: python-mysqlclient -- Python interface to MySQL http://bugs.debian.org/768096 (Currently in new awaiting entry to experimental). Just to confirm: this package doesn't appear to conflict with python-mysqldb, is that correct? Correct, this is a different implementation. You'd import it with import pymysql and not import mysqldb. I know about other implementations, though that one is a dependency for newer code in OpenStack. Cheers, Thomas Goirand (zigo) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764587: installation-reports: After successful installation from usb stick the stick is not recognised on reboot.
On Thu, 2014-10-09 at 23:32 +1300, Philip Charles wrote: Package: installation-reports Severity: normal After successful installation from usb stick the stick is not recognised on reboot. Boot method: usb stick Image version: beta 2 installer amd64 DVD1 (copied to usb stick) Date: Oct 2014 From a email sent to me, One of my friends works for an NGO and is based in rural parts of Asia and Latin America for about 10 months of the year. He told me that most of the machines were second-hand and had faulty DVD drives. Moreover DVD discs are prone to scratches and wear-and-tear. On the other hand USB flash drives are ubiquitous and relatively inexpensive. Even used machines have at least a USB port. I have produced complete 32 64 bit installation sticks for wheezy (~43GB) and Jessie (~55GB) which fit nicely on a 64GB stick. However, the stick is of limited use because the stick cannot be accessed after the initial installation which means that additional software cannot be installed. -- Philip Charles; 39a Paterson Street, Abbotsford, Dunedin, New Zealand +64 3 488 2818Fax +64 3 488 2875Mobile 027 663 4453 phil...@copyleft.co.nz - personal.i...@copyleft.co.nz - business -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770926: debian-faq: Missing word(s) in faq section 1.5
Package: debian-faq Version: 5.0.1 Severity: minor Tags: patch Hello, please see the attached patch. Index: basic_defs.sgml === --- basic_defs.sgml (Revision 10498) +++ basic_defs.sgml (Arbeitskopie) @@ -141,7 +141,7 @@ very strict about shipping truly free software. The guidelines used to determine if a work is free are provided in url id=http://www.debian.org/social_contract#guidelines; name=The Debian Free - Software. + Software Guidelines (DFSG). tag/The Debian package maintenance system:/ itemThe entire system, or any individual component of it, can be
Bug#756855: synaptic: Should not set APT::Install-Recommends (globally)
found 756855 0.75.13 user cont...@itopie.ch usertags 756855 + itopie.ch-installation user i...@codha.ch usertags 756855 + codha.ch-installation thanks 0.75.13 Hi there, On Sat, 02 Aug 2014 18:30:58 +0200, Axel Beckert wrote: Package: synaptic Version: 0.81.2 This happens in wheezy as well, marked. synaptic ships /etc/apt.conf.d/99synaptic which sets APT::Install-Recommends to true globally for all APT based applications. Actually, the above file is not present in the package itself, but it is generated the first time synaptic is started, as etckeeper told me. IMHO no application should be so arrogant to change that value globally [...] If it's needed for synaptic's well-behaving (which I doubt), it should set that value internally, but not globally. Fully, agree. Please note that IMHO this bug is at least important, if not more. Thx, bye, Gismo / Luca signature.asc Description: Digital signature
Bug#770927: python-caja installs files to debian/tmp..
Package: python-caja Version: 1.8.1-1 Severity: important The python-caja documentation does not get complete installed into the bin:package python-caja. The reasone is very probably an upstream autotools issue: /bin/mkdir -p 'BUILD_BASE/python-caja-1.8.1/debian/tmp../docs/xsl' /usr/bin/install -c -m 644 xsl/common.xsl xsl/devhelp.xsl xsl/html.xsl xsl/pdf-style.xsl xsl/pdf.xsl xsl/style.css ./xsl/fixxref.py 'BUILD_BASE/python-caja-1.8.1/debian/tmp../docs/xsl' With a falcon's eye you will spot debian/tmp.. as installation path in the above installation destination... Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgpq2EOJqqlKL.pgp Description: Digitale PGP-Signatur
Bug#756855: synaptic: Should not set APT::Install-Recommends (globally)
Control: severity -1 important Hi Luca, Luca Capello wrote: synaptic ships /etc/apt.conf.d/99synaptic which sets APT::Install-Recommends to true globally for all APT based applications. Actually, the above file is not present in the package itself, but it is generated the first time synaptic is started, as etckeeper told me. Thanks for the investigation and details. Actually I noticed it because of tracking /etc/apt/ in git, too. (I likely wouldn't have noticed it on those machines where I use etckeeper as it does the commits automaticallt by default. :-) Please note that IMHO this bug is at least important, if not more. Thanks for the comment. I was unsure about the real severity (I veered between minor and important) and hence removed the explicit Severity: normal deliberately because of that. Since there's now a second opinion, I've now set the severity to important. Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770812: tasksel: task-sysvinit to allow easy installation of non-systemd systems
Erich Schubert er...@debian.org (2014-11-25): HI, HELLO, Besides: I'm not sure where you got the impression I owe you anything. Any user writing a reasonable bug report deserves to be treated with respect, and deserves a useful answer (spam and duplicate reports are an obvious exception). I'm not sure why you think insisting we need this feature within d-i is considered respectful in the first place. As I wrote, a *decision* was made *not* to include such a thing in d-i, and it could have been seen by anyone interested in this topic (which seems to be everyone sending mails at the moment). Coming up with more bug reports looks more like you're harassing developers than anything else. So yes, I did answer, because there's no use letting people do work on this. And I did answer “no” because every possible reason for not including this “feature” in d-i was already given. Why should we spend time discussing “technical merits” if it isn't going to get merged? Not just a no (which is an unwritten f... off) If I really wanted to write this, believe me, I would have. Otherwise, our users will stop reporting bugs at all, if you treat them this way. We surely don't need more bug reports on that specific topic. It's bad enough that you won't even consider our current #1 installer feature request as future wishlist item. AH AH AH AH AH AH AH AH AH AH AH AH AH AH AH AH AH AH AH AH AH AH. This itself is already highly disrespectful, and I'm not surprised that some people are annoyed, if all they get in return are shut up messages. Annoying people leads to annoyed people, I couldn't agree more. I guess we'll see a forked installer sooner or later because of that. Great. Forks are good. People can scratch their itches. KiBi. signature.asc Description: Digital signature
Bug#764506: Processed: severity of 764506 is normal
Hi, Debian Bug Tracking System wrote: severity 764506 normal Bug #764506 [aptitude] aptitude: aptitude update no more works with apt 1.1~exp4 Bug #764601 [aptitude] Could not open file /var/lib/apt/lists/...Packages.IndexDiff - open (2: No such file or directory) Bug #770908 [aptitude] aptitude does not know about the new _apt user. Must use apt-get update as a workaround Severity set to 'normal' from 'grave' Severity set to 'normal' from 'grave' Severity set to 'normal' from 'grave' I'm confused that I had to do that manually as I expected that forcemerge already does that. Anyway: Reason why I consider this not even important is that nobody so far checked if rebuilding aptitude against apt from experimental would already solve the issue -- which IMHO is not that unlikely. (I though could imagine that it may FTBFS on that occassion.) If I find time and leisure before the Jessie release, I'll check that. Otherwise we'll soon see after the Jessie release. Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770928: squid3: Superfluous dependencies
Package: squid3 Version: 3.1.20-2.2+deb7u2 Severity: minor dh_shlibdeps -psquid3 dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/squid3/usr/lib/squid3/squid_kerb_auth_test debian/squid3/usr/lib/squid3/negotiate) dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/squid3/usr/lib/squid3/squid_ldap_group debian/squid3/usr/lib/squid3/ntlm_smb_lm_a) dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/squid3/usr/lib/squid3/squid_kerb_auth_test debian/squid3/usr/lib/squid3/negotiate) dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/squid3/usr/lib/squid3/squid_kerb_auth_test debian/squid3/usr/lib/squid3/negotiate) dh_shlibdeps -psquidclient dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/squidclient/usr/bin/squidclient was not linked against libdl.so.2 (it uses none o) dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/squidclient/usr/bin/squidclient was not linked against libcap.so.2 (it uses none ) dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/squidclient/usr/bin/squidclient was not linked against libnsl.so.1 (it uses none ) dh_shlibdeps -psquid-cgi dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/squid-cgi/usr/lib/cgi-bin/cachemgr.cgi was not linked against libdl.so.2 (it uses) dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/squid-cgi/usr/lib/cgi-bin/cachemgr.cgi was not linked against libcap.so.2 (it use) dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/squid-cgi/usr/lib/cgi-bin/cachemgr.cgi was not linked against libnsl.so.1 (it use) Those reports are send by a build (to enable ssl, cf. bug 641944). -- System Information: Debian Release: 7.5 Architecture: armhf (armv6l) Kernel: Linux 3.12.22+ (PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages squid3 depends on: ii adduser 3.113+nmu3 ii libc6 2.13-38+rpi2+deb7u1 ii libcap2 1:2.22-1.2 ii libcomerr21.42.5-1.1 ii libdb5.1 5.1.29-5 ii libexpat1 2.1.0-1+deb7u1 ii libgcc1 1:4.7.2-5+rpi1 ii libgssapi-krb5-2 1.10.1+dfsg-5+deb7u2 ii libk5crypto3 1.10.1+dfsg-5+deb7u2 ii libkrb5-3 1.10.1+dfsg-5+deb7u2 ii libldap-2.4-2 2.4.31-1+nmu2 ii libltdl7 2.4.2-1.1 ii libpam0g 1.1.3-7.1 ii libsasl2-22.1.25.dfsg1-6+deb7u1 ii libstdc++64.7.2-5+rpi1 ii libxml2 2.8.0+dfsg1-7+wheezy2 ii logrotate 3.8.1-4 ii lsb-base 4.1+Debian8+rpi1+deb7u1 ii netbase 5.0 ii squid3-common 3.1.20-2.2+deb7u2 squid3 recommends no packages. Versions of packages squid3 suggests: pn resolvconf none ii smbclient2:3.6.6-6+deb7u4 ii squid-cgi3.1.20-2.2+deb7u2 ii squidclient 3.1.20-2.2+deb7u2 ii ufw 0.31.1-2 -- Configuration Files: /etc/logrotate.d/squid3 changed [not included] /etc/squid3/squid.conf changed [not included] -- 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#770929: bugs.debian.org: TLS handshaking fails (cf. #707049 archived)
Package: bugs.debian.org Severity: important Tags: security When sending a bug, the mail gets sent to the mx bugs-master.debian.org. The handling port 25 on that box has a tls cert with CN=buxtehude.debian.org. AFAICT there also is no subAltName extension for bugs-master.debian.org. It seems to be a problem to establish secure connections SMTP transfer. Nov 25 10:26:02 greedo sm-mta[17032]: STARTTLS=client, error: connect failed=-1, SSL_error=5, errno=104, retry=-1 Nov 25 10:26:02 greedo sm-mta[17032]: ruleset=tls_server, arg1=SOFTWARE, relay=buxtehude.debian.org, reject=403 4.7.0 TLS handshake failed. Nov 25 10:26:02 greedo sm-mta[17032]: sALEe9rf025810: to=sub...@bugs.debian.org, delay=3+18:45:52, xdelay=00:00:10, mailer=esmtp, pri=49203754, relay=buxteh. Nov 25 10:26:09 greedo sm-mta[17055]: sAP9Q64s017055: [137.116.204.56] did not issue MAIL/EXPN/VRFY/ETRN during connection to MTA4-v4 libgnutls26 : 2.12.20-8+deb7u2 0 The only workaround (for sendmail) is to add a Tls disable specifically for buxtehude in the /etc/mail/access map : Try_TLS:buxtehude.debian.orgNO But it is a workaround, as the main securit is not solved by disabling security… -- System Information: Debian Release: 7.5 Architecture: armhf (armv6l) Kernel: Linux 3.12.22+ (PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#532486: taskbar/notification area icon does not survive restart
According to the discussion upstream [1] it works with awesome-3.5.5, maybe due to the migration to GTK+ 3 in the meantime. [1] https://github.com/blueman-project/blueman/issues/8 I'm thus closing this. Drop me a line if you can still reproduce. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768695: Bug #768695: statsmodels: FTBFS in jessie: ImportError: cannot import name DateRange
On Sun, Nov 23, 2014 at 07:13:07PM +0100, Michael Banck wrote: Hi have uploaded the attached debdiff targetted at testing-proposed-updates to DELAYED/3-day. See also the pre-approval/unblock bug for relesae.debian.org, #770730. Unfortunately, it FTBFS on i386 still, there are a couple of test suite failures: https://buildd.debian.org/status/fetch.php?pkg=statsmodelsarch=i386ver=0.4.2-1.1stamp=1416885423 Michael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770713: Preferences Xiphos
I have posted some information here: http://forums.debian.net/viewtopic.php?f=10t=119049 Thank you for your work!
Bug#770517: autopkgtest: installs an init script with inconsistent dependencies/sequencing
Control: tag -1 pending Simon McVittie [2014-11-21 22:10 +]: My search indicated that autopkgtest can install an init script (on VMs) with: # X-Start-Before:$network [...] Is there any reason for this script not to start earlier, in rcS? Argh, thanks for pointing this out! The X-Start-Before is just some leftover from copypaste'ing. The script doesn't require networking at all. I don't want to start the script too early, at least not during rcS. Fixed here: http://anonscm.debian.org/cgit/autopkgtest/autopkgtest.git/commit/?id=fbd5b 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#762399: console-setup: WARNING: Unknown X keysym permille
Martin-Éric Racine martin-eric.rac...@iki.fi (2014-11-23): Thanks for fixing the issue in 1.115. However, the package is currently blocked because of the freeze and it would need an unblock request to propagate into Testing. 'd console-setup' says binary diffs and: 151 files changed, 93 insertions(+), 9257 deletions(-) Trying to rebuild a clean source package from git (adding just a changelog entry) I'm still getting this, between 1.114 and 1.116: 55 files changed, 100 insertions(+), 9257 deletions(-) (Without binary diffs this time.) I'm really uncomfortable with vouching for such an unblock. Mraw, KiBi. signature.asc Description: Digital signature
Bug#770764: unblock: espeakup/1:0.71-18
Jonathan Wiltshire j...@debian.org (2014-11-23): On Sun, Nov 23, 2014 at 11:32:42PM +0100, Cyril Brulebois wrote: Control: tag -1 confirmed Jonathan Wiltshire j...@debian.org (2014-11-23): Control: tag -1 d-i On Sun, Nov 23, 2014 at 10:28:47PM +0100, Samuel Thibault wrote: Samuel Thibault, le Sun 23 Nov 2014 22:24:16 +0100, a écrit : I have uploaded 1:0.71-18, which uses characters instead of tts:char, fixing the issue, could you unblock it? Sorry, I forgot to attach the debdiff, here it is. Looks good to me; needs a d-i ack. ACK, ta. Thanks, unblocked. You want (to add) an unblock-udeb line. ;) Mraw, KiBi. signature.asc Description: Digital signature
Bug#770930: mpv memory leak
Package: mpv Version: 0.6.2-2 Severity: important Hello, when you use mpv with bigger files it happens that mpv consumes all RAM and swap and the system gets unusable. The mpv team investigated the issue: https://github.com/mpv-player/mpv/issues/1204 It looks like there is a problem with libav. But there is a patch. I think there are two solutions: * compile with ffmpeg * patch libav I filed the bug here, because i only experience the problem with mpv. Thanks for maintaining mpv. Greetings Moritz -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-proposed-updates'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mpv depends on: ii libasound2 1.0.28-1 ii libass5 0.10.2-3 ii libavcodec566:11-2 ii libavdevice55 6:11-2 ii libavfilter56:11-2 ii libavformat56 6:11-2 ii libavresample2 6:11-2 ii libavutil54 6:11-2 ii libbluray1 1:0.6.2-1 ii libbs2b03.1.0+dfsg-2.1 ii libc6 2.19-13 ii libcdio-cdda1 0.83-4.2 ii libcdio-paranoia1 0.83-4.2 ii libcdio13 0.83-4.2 ii libdvdnav4 5.0.1-1 ii libdvdread4 5.0.0-1 ii libegl1-mesa [libegl1-x11] 10.3.2-1 ii libenca01.16-1 ii libgl1-mesa-glx [libgl1]10.3.2-1 ii libguess1 1.2-1 ii libjack-jackd2-0 [libjack-0.116]1.9.10+20140719git3eb0ae6a~dfsg-2 ii libjpeg62-turbo 1:1.3.1-10 ii liblcms2-2 2.6-3+b3 ii liblircclient0 0.9.0~pre1-1.1 ii liblua5.2-0 5.2.3-1.1 ii libmpg123-0 1.20.1-2 ii libpulse0 5.0-13 ii libquvi70.4.1-2.1 ii libsdl2-2.0-0 2.0.2+dfsg1-5 ii libswscale3 6:11-2 ii libuuid12.25.2-3 ii libva-glx1 1.4.1-1 ii libva-x11-1 1.4.1-1 ii libva1 1.4.1-1 ii libvdpau1 0.8-3 ii libwayland-client0 1.6.0-2 ii libwayland-cursor0 1.6.0-2 ii libwayland-egl1-mesa [libwayland-egl1] 10.3.2-1 ii libx11-62:1.6.2-3 ii libxext62:1.3.3-1 ii libxinerama12:1.1.3-1+b1 ii libxkbcommon0 0.4.3-2 ii libxrandr2 2:1.4.2-1+b1 ii libxss1 1:1.2.2-1 ii libxv1 2:1.0.10-1+b1 ii zlib1g 1:1.2.8.dfsg-2 mpv recommends no packages. mpv 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#769687: autopkgtest: FTBFS with no network access
Hey Daniel, Daniel Schepler [2014-11-22 20:21 -0800]: OK, the original test failure that triggered me to try this build was: I'm doing a local rebuild of all packages in the archive, using a setup with a local archive so that it can eat its own dog food. With that setup, I'm getting this failure: [...] AssertionError: 'libcgraph' not found in '[...] Hmm, no error from apt. I suppose for that I'd need to be able to reproduce that failure here. But anyway, this should be fixed in git now, where the test gets skipped if apt-get download isn't available. Note that you can build with DEB_BUILD_OPTIONS=nocheck to skip the test suite. In my testing, this didn't seem to be the case. Your debian/rules overrides dh_auto_test without reproducing the DEB_BUILD_OPTIONS=nocheck handling of dh_auto_test. Argh, indeed. Fixed: http://anonscm.debian.org/cgit/autopkgtest/autopkgtest.git/commit/?id=6abf62a0 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#766187: /etc/inittab - base-files?
Hi, the problem of having to cope with a non-existing inittab would imho be solved if the inittab file could be transplanted to base-files. But then, sysvinit would need to be modified to patch an existing inittab, instead of simply installing its basic known-good version. I am not sure that this will not simply open a different can of worms. The decision then becomes, which entries to keep, and which to overwrite. It also looks like the keys in the inittab are agreed upon by convention, not by standard - right? Kind regards, --Toni++ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770931: osmctools: new upstream version of osmconvert - adds alternative granularity support
Package: osmctools Version: 0.3-1 Severity: normal I wrote to Markus Weber, the upstream author of osmctools with a feature request, concerning OSM plant file in PBF download from this site: http://download.bbbike.org/osm/planet/ These files were created with the osmosis setting granularity=1. When trying to read with osmconvert it produced this error: node nanodegrees must be 100:1 Markus has added support for PBF plant dumps with non-standard granularity, it would be great to have his new version of osmconvert in Debian. Here is the commit: https://gitorious.org/osm-c-tools/osmctools/commit/e40dad41670473e4963c94ab5491e9a9397f12d5 Thanks, -- Edward. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770751: adt-run fail with ValueError: Invalid version string '10.1.1-1]'
Control: severity -1 normal Control: tag -1 moreinfo Hello, Pirate Praveen [2014-11-24 1:21 +0530]: pravi@savannah:~/forge/debian/git/pkg-ruby-extras/ruby-jwt $ adt-run -B .// --- null I checked current ruby-jwt git and there's no autopkgtest there, so I suppose you didn't commit that yet. raise ValueError(Invalid version string %r % version) ValueError: Invalid version string '10.1.1-1]' This looks like a typo in your debian/tests/control, you seem to have an extra ']' there. If that's not it, can you please attach your file or the complete test so that I can reproduce? Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature
Bug#770764: unblock: espeakup/1:0.71-18
On Tue, Nov 25, 2014 at 11:07:02AM +0100, Cyril Brulebois wrote: Jonathan Wiltshire j...@debian.org (2014-11-23): On Sun, Nov 23, 2014 at 11:32:42PM +0100, Cyril Brulebois wrote: Control: tag -1 confirmed Jonathan Wiltshire j...@debian.org (2014-11-23): Control: tag -1 d-i On Sun, Nov 23, 2014 at 10:28:47PM +0100, Samuel Thibault wrote: Samuel Thibault, le Sun 23 Nov 2014 22:24:16 +0100, a écrit : I have uploaded 1:0.71-18, which uses characters instead of tts:char, fixing the issue, could you unblock it? Sorry, I forgot to attach the debdiff, here it is. Looks good to me; needs a d-i ack. ACK, ta. Thanks, unblocked. You want (to add) an unblock-udeb line. ;) Details, details... -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 signature.asc Description: Digital signature
Bug#770932: ruby2.1: CVE-2014-8090
Package: ruby2.1 Severity: grave Tags: security Hi, please see https://www.ruby-lang.org/en/news/2014/11/13/rexml-dos-cve-2014-8090/ for details. 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#770933: [mdbtools] Please update homepage in package description
Package: mdbtools Version: 0.7.1-2 Severity: minor --- Please enter the report below this line. --- The package description should be updated to reference https://github.com/brianb/mdbtools instead of the sourceforge homepage. --- System information. --- Architecture: i386 Kernel: Linux 3.16.6 Debian Release: jessie/sid 500 unstableftp.de.debian.org 1 experimentalftp.de.debian.org --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770931: osmctools: new upstream version of osmconvert - adds alternative granularity support
Control: severity -1 wishlist Markus has added support for PBF plant dumps with non-standard granularity, it would be great to have his new version of osmconvert in Debian. Once a new osm-c-tools release is published we'll update the Debian package. We could include a patch for the commit in the package, but it won't make it into the jessie release anyway, so there is no hurry. Unless the next osm-c-tools release is not due for a long time, then we should consider adding a patch for the commit. Kind Regards, Bas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770815: openafs-client: OpenAFS Client 1.6.10 does not start anymore
On Monday 24 November 2014 13:43:55 Benjamin Kaduk wrote: Can you please provide the contents of /var/cache/openafs-client/*.env ? Sure. On my Desktop i have this: # openafs-client.env AFSD_ARGS= -dynroot -fakestat AFS_SETCRYPT=off AFS_SYSNAME=-help KMOD=openafs # openafs-client.shutdown.env KMOD=openafs I also have a Live-System for a USB-Stick with this: # openafs-client.env AFSD_ARGS=-memcache -dynroot -fakestat AFS_SETCRYPT=on AFS_SYSNAME=-help KMOD=openafs # openafs-client.shutdown.env KMOD=openafs I now also checked and compared several machines (i have some not that up to date jessie machines and i figured out that on one of them there was a functional openafs-client 1.6.10-2), and this is what i found: On that machine AFSD_ARGS also contained -afsdb ! ( AFS_AFSDB=true in /etc/openafs/afs.conf.client ) Seems i missed that earlier when trying different settings. Now i need to figure out if i had a good reason for AFSD_ARGS=false ... Also please verify that you can 'modprobe openafs' and 'rmmod openafs' successfully. Yep, no problem with that. I also found out that the openafs-client 1.6.10~pre1-1 works with openafs-modules-dkms 1.6.10-2 -- Wolfgang Scheicher Institut fur ComputerGraphik und WissensVisualisierung Inffeldgasse 16c -- TU Graz -- A-8010 Graz -- Austria -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762399: console-setup: WARNING: Unknown X keysym permille
[ Please reply to the bug report and involved people, instead of to the mailing list. ] Thorsten Glaser t...@mirbsd.de (2014-11-25): Cyril Brulebois dixit: 'd console-setup' says binary diffs and: 151 files changed, 93 insertions(+), 9257 deletions(-) The person doing the upload did not do so cleanly. There is an extra subdirectory fontconfig/ in the .tgz recently, which has 940'632 bytes in 96 files in 1.115 (I noticed because I regularily rebuild console-setup locally, with local patches; my own builds do not have that directory). I know. That's not the part I'm worried about, see the portion of my mail you cut off… Mraw, KiBi. signature.asc Description: Digital signature
Bug#770771: unblock: rebuilds for rubygems integration fix
Control: tag -1 moreinfo On Tue, Nov 25, 2014 at 04:45:30AM +0530, Pirate Praveen wrote: control: tags -1 - moreinfo On Tuesday 25 November 2014 01:25 AM, Jonathan Wiltshire wrote: Ok, you'd better go ahead. Please remove the moreinfo tag when they are all in sid. The following packages are in sid, rack-mobile-detect ruby-equalizer ruby-i18n-inflector ruby-rack-pjax Unblocked. ruby-jwt Not in unstable; did it get missed? ruby-bootstrap-sass Not in testing; no unblock for this one. -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 signature.asc Description: Digital signature
Bug#768707: getting this into jessie?
Hi, as far as I can see, the one problem is that these two small dependencies, python-sphinx-testing and python3-sphinx-testing, are not in Jessie, which apparently prevents several packages from going into Jessie. I can see two ways forward: One, make an exception for python*-sphinx-testing, and the other, patching the testing code out of the builds for the sphinx-* packages. Which one do you prefer? Cheers, --Toni++ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770934: rails: CVE-2014-7818 CVE-2014-7829
Package: rails Severity: important Tags: security Hi, please see http://seclists.org/oss-sec/2014/q4/648 and http://www.openwall.com/lists/oss-security/2014/10/30/5 for details. 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#729924: vim: Add Python 3 support
Just for the note, I've stumbled upon this bug report, and thought it might be useful to tell that as I'm running wheezy and I needed a more recent version of vim, I recompiled it and enabled both python3 and python2: 888---8 VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Nov 11 2014 21:41:52) Included patches: 1-488 Modified by pkg-vim-maintain...@lists.alioth.debian.org Compiled by guy...@bugz.eclipse.m0g.net Huge version with GTK2 GUI. Features included (+) or not (-): +acl +farsi +mouse_netterm +syntax +arabic +file_in_path+mouse_sgr +tag_binary +autocmd +find_in_path-mouse_sysmouse +tag_old_static +balloon_eval+float +mouse_urxvt -tag_any_white +browse +folding +mouse_xterm +tcl ++builtin_terms -footer +multi_byte +terminfo +byte_offset +fork() +multi_lang +termresponse +cindent +gettext -mzscheme+textobjects +clientserver-hangul_input+netbeans_intg +title +clipboard +iconv +path_extra +toolbar +cmdline_compl +insert_expand +perl+user_commands +cmdline_hist+jumplist+persistent_undo +vertsplit +cmdline_info+keymap +postscript +virtualedit +comments+langmap +printer +visual +conceal +libcall +profile +visualextra +cryptv +linebreak +python/dyn +viminfo +cscope +lispindent +python3/dyn +vreplace +cursorbind +listcmds+quickfix+wildignore +cursorshape +localmap+reltime +wildmenu +dialog_con_gui +lua +rightleft +windows +diff+menu+ruby+writebackup +digraphs+mksession +scrollbind +X11 +dnd +modify_fname+signs -xfontset -ebcdic +mouse +smartindent +xim +emacs_tags +mouseshape -sniff +xsmp_interact +eval+mouse_dec +startuptime +xterm_clipboard +ex_extra+mouse_gpm +statusline -xterm_save +extra_search-mouse_jsbterm -sun_workshop+xpm […] Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -pthread -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -g -O2 -fPIE -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -I/usr/include/tcl8.5 -D_REENTRANT=1 -D_THREAD_SAFE=1 -D_LARGEFILE64_SOURCE=1 Linking: gcc -L. -Wl,-z,relro -rdynamic -Wl,-export-dynamic -Wl,-E -fPIE -pie -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -o vim -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0 -lpangocairo-1.0 -lgdk_pixbuf-2.0 -lcairo -lpango-1.0 -lfreetype -lfontconfig -lgobject-2.0 -lglib-2.0 -lSM -lICE -lXpm -lXt -lX11 -lXdmcp -lSM -lICE -lm -ltinfo -lelf -lnsl -lselinux -lacl -lattr -lgpm -L/usr/lib -llua5.2 -Wl,-E -fstack-protector -L/usr/local/lib -L/usr/lib/perl/5.14/CORE -lperl -ldl -lm -lpthread -lcrypt -L/usr/lib -ltcl8.5 -ldl -lpthread -lieee -lm -lruby-1.9.1 -lpthread -lrt -ldl -lcrypt -lm -L/usr/lib 888---8 I did not run into any issue so far, though when I try to run both python 2 and python 3 from ex command line: 888---8 :py import sys;print(sys.version) 2.7.3 (default, Mar 13 2014, 11:26:58) [GCC 4.7.2] :py3 import sys;print(sys.version) E837: This Vim cannot execute :py3 after using :python E263: Sorry, this command is disabled, the Python library could not be loaded. 888---8 Which is a nice explicit error! I'm also in favour of switching to python3 which is mature enough and should replace python2 everywhere it can. So I do believe the dual compilation option is the best option, as you leave it to the user to make sure his whole configuration is being run using one or the other. But to promote transition to py3, the software package needs to be able to load py3 components! Cheers, -- Bernard Pratz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#689991: CUPS: error_log flooded due to AllowUser restriction
On Tue, Feb 25, 2014 at 03:28:37PM +0100, Didier Raboud wrote: Le vendredi, 26 avril 2013, 13.08:22 Alberto Gonzalez Iniesta a écrit : I'm also experiencing this problem when my print clients were upgraded from Ubuntu 10.04 to 12.04 [1]. The CUPS server [2] runs Debian Squeeze. Alberto, Sergio: is this problem still present with a Wheezy CUPS server? Hi, just upgraded the print server to Wheezy and the problem persists. Hundreds of lines in error.log when an unauthorized users tries to print. -- Alberto Gonzalez Iniesta| Formación, consultoría y soporte técnico mailto/sip: a...@inittab.org | en GNU/Linux y software libre Encrypted mail preferred| http://inittab.com Key fingerprint = 5347 CBD8 3E30 A9EB 4D7D 4BF2 009B 3375 6B9A AA55 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770935: python-2.7.pc: erroneously provides non-multiarch ${libdir}
Package: libpython2.7-dev
Severity: important
Version: 2.7.8-12
The python2.7.pc file provides
libdir=${prefix}/lib (aka /usr/lib)
However, the libpython2.7.so file is found at the multi-arch location
/usr/lib/triplet/libpython2.7.so.
I looked at several other multi-arch packages and they (correctly?)
reference ${libdir} as a multi-arch library path.
Please consider changing this with one of the next uploads or give
feedback why you think ${libdir} should stay as is. THANKS!
Btw: I currently have to work around this in python-caja (see #766879 [1]).
Greets,
Mike
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766879
--
DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976 148
GnuPG Key ID 0x25771B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb
pgplmo2zGR3ZU.pgp
Description: Digitale PGP-Signatur
Bug#770283: xfburn crashes when adding Data Composition files
Hi, as one can see, there is not much xfburn code active when the SIGSEGV happens. I guess it is thread 1 which suffers it. Now while there is still the possibility that xfburn started the problem by subtle corruption of memory management, it is strange that this does not happen on arch amd64. xfburn source code itself makes no differences between processor types. In may 2014 i had a semi-private (german) conversation with an Ubuntu i386 user who experienced SIGSEGV in the GTK libraries when starting a burn run. We involved the memory checker program valgrind and the developer of xfburn. Regrettably the case could not be solved because valgrind did not find any wrongdoing in xfburn code, and because the entrails of GTK are too complicated for me, valgrind, and the developer of xfburn. Valgrind detected the memory problems earlier than the SIGSEGV happened, but it could not show us the initial trigger in GTK. (I'm glad that my own sports only deals with burner drives and ISO 9660 filesystem entrails. It's so relaxing if you depend only on command line, core operating system, and own code.) If you feel apt to do in a shell session (aka terminal window): sudo apt-get install valgrind valgrind $(which xfburn) 21 | tee -i /tmp/valgrind_messages and then replay the user input which leads to the crash, then please post the resulting file /tmp/valgrind_messages. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770936: python-3.4.pc: erroneously provides non-multiarch ${libdir}
Package: libpython3.4-dev
Severity: important
Version: 3.4.2-2
The python3.4.pc file provides
libdir=${prefix}/lib (aka /usr/lib)
However, the libpython2.7.so file is found at the multi-arch location
/usr/lib/triplet/libpython2.7.so.
I looked at several other multi-arch packages and they (correctly?)
reference ${libdir} as a multi-arch library path.
Please consider changing this with one of the next uploads or give
feedback why you think ${libdir} should stay as is. THANKS!
Btw: for libpython2.7-dev I currently have to work around this in
python-caja (see #766879 [1]). The issue does also seem to apply to
libpython3.4-dev (though python-caja does not use python3).
Greets,
Mike
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766879
--
DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976 148
GnuPG Key ID 0x25771B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb
pgpQQflPLV55F.pgp
Description: Digitale PGP-Signatur
Bug#770016: Clarify network access for building packages in main
[Let's leave the problem of d-i aside for the moment. I suppose it'll require a special exception in Policy, at least for the time being.] * Lucas Nussbaum lu...@debian.org, 2014-11-24, 10:21: I wonder if it should be turned into the package must not rely on external access network to build correctly. That's better than nothing, but... A package that checks if network access is available, and run more tests if it's the case, could be fine. I, for one, would consider my package RC buggy if it tried to use external network, even if such access had no influence on the resulting binary packages. I do appreciate that having tests that require network connectivity is useful for some packages. We could add an option for DEB_BUILD_OPTIONS to let users opt-in for such tests. -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766187: The inittab interface - Re: Bug#766187: runit: Fails to install runit after fresh install of jessie beta2
I noticed that my last mail about 766187 being related to 768657 didn't actually go to the bug report. (which was about this bug being related) Anyway, both of these bugs seem to be about providing /etc/inittab in one form or another. Please see KiBi's last entry about providing it via D-I which has gone unanswered. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768657 I'm only sharing this as it would appear there are two separate conversations happening about the same problem. (and i'm assuming that a solution should / would solve both) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770937: needrestart: Kills wdm session on system running systemd g (maybe via dbus restart)
Package: needrestart
Version: 1.2-5
Severity: grave
Justification: data loss
Hi Thomas and Patrick,
recently, it happened twice that needrestart killed my X session which
was started by wdm and is running the awesome window manager via
~/.Xsession.
I don't think it's the new upload but rather the recent dbus updates. I
can't exactly remember if the second-last case was at the time when dbus
was updated (and if so, needrestart would have been at version 1.2-4),
but the case today definitely had a dbus update included.
According to the logs it also restarted systemd itself.
Despite there is
$nrconf{override_rc} = {
# DBus
q(^dbus) = 0,
[…]
}
in the (used) default config, systemd restarted dbus:
Nov 25 11:18:57 c-cactus systemd[1]: Stopping D-Bus System Message Bus...
A more verbose log excerpt of what seems relevant to me:
Nov 25 11:18:57 c-cactus systemd[1]: Reexecuting.
Nov 25 11:18:57 c-cactus systemd[1]: systemd 215 running in system mode. (+PAM
+AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ -SECCOMP
-APPARMOR)
Nov 25 11:18:57 c-cactus systemd[1]: Detected architecture 'x86-64'.
Nov 25 11:18:57 c-cactus systemd[1]: Started ACPI event daemon.
Nov 25 11:18:57 c-cactus systemd[1]: Mounted /var.
Nov 25 11:18:57 c-cactus systemd[1]: Mounted /home.
Nov 25 11:18:57 c-cactus systemd[1]: Mounted /boot.
Nov 25 11:18:57 c-cactus systemd[1]: Mounted /.
Nov 25 11:18:57 c-cactus systemd[1]: Started File System Check on
/dev/disk/by-uuid/….
[…]
Nov 25 11:18:57 c-cactus systemd[1]: Activated swap /dev/…/swap.
Nov 25 11:18:57 c-cactus systemd[1]: Stopping Accounts Service...
Nov 25 11:18:57 c-cactus systemd[1]: Stopping Avahi mDNS/DNS-SD Stack...
Nov 25 11:18:57 c-cactus systemd[1]: Stopping Bluetooth service...
Nov 25 11:18:57 c-cactus systemd[1]: Stopping Regular background program
processing daemon...
Nov 25 11:18:57 c-cactus systemd[1]: Starting Regular background program
processing daemon...
Nov 25 11:18:57 c-cactus systemd[1]: Started Regular background program
processing daemon.
Nov 25 11:18:57 c-cactus systemd[1]: Stopping D-Bus System Message Bus...
Nov 25 11:18:57 c-cactus systemd[1]: Starting Accounts Service...
Nov 25 11:18:57 c-cactus systemd[1]: Starting Bluetooth service...
Nov 25 11:18:57 c-cactus systemd[1]: Stopping OpenBSD Secure Shell server...
Nov 25 11:18:57 c-cactus systemd[1]: Stopping Journal Service...
Nov 25 11:18:57 c-cactus systemd[1641]: Stopping Default.
Nov 25 11:18:57 c-cactus systemd[1641]: Stopped target Default.
Nov 25 11:18:57 c-cactus systemd[1641]: Stopping Basic System.
Nov 25 11:18:57 c-cactus systemd[1641]: Stopped target Basic System.
Nov 25 11:18:57 c-cactus systemd[1641]: Stopping Paths.
Nov 25 11:18:57 c-cactus systemd[1641]: Stopped target Paths.
Nov 25 11:18:57 c-cactus systemd[1641]: Stopping Timers.
Nov 25 11:18:57 c-cactus systemd[1641]: Stopped target Timers.
Nov 25 11:18:57 c-cactus systemd[1641]: Stopping Sockets.
Nov 25 11:18:57 c-cactus systemd[1641]: Stopped target Sockets.
Nov 25 11:18:57 c-cactus systemd[1641]: Starting Shutdown.
Nov 25 11:18:57 c-cactus systemd[1641]: Reached target Shutdown.
Nov 25 11:18:57 c-cactus systemd[1641]: Starting Exit the Session...
Nov 25 11:18:57 c-cactus systemd[1]: Starting OpenBSD Secure Shell server...
Nov 25 11:18:57 c-cactus systemd[1]: Started OpenBSD Secure Shell server.
Nov 25 11:18:57 c-cactus systemd[1641]: Received SIGRTMIN+24 from PID 12082
(kill).
Nov 25 11:18:57 c-cactus systemd[1]: Started Trigger Flushing of Journal to
Persistent Storage.
Nov 25 11:18:57 c-cactus systemd[1]: Starting Daemon for power management...
Nov 25 11:18:57 c-cactus systemd[1]: Starting LSB: Starts and stops Wicd...
Nov 25 11:18:57 c-cactus systemd[1]: Starting D-Bus System Message Bus...
Nov 25 11:18:57 c-cactus systemd[1]: Started D-Bus System Message Bus.
Nov 25 11:18:57 c-cactus systemd[1]: Started Bluetooth service.
Nov 25 11:18:57 c-cactus systemd[1]: Starting Hostname Service...
Nov 25 11:18:57 c-cactus systemd[1]: Started Accounts Service.
Nov 25 11:18:57 c-cactus systemd[1]: Started Daemon for power management.
Nov 25 11:18:57 c-cactus systemd[1]: Starting User Manager for UID 1000...
Nov 25 11:18:57 c-cactus systemd[1]: Starting Login Service...
Nov 25 11:18:57 c-cactus systemd[1]: Started Hostname Service.
Nov 25 11:18:57 c-cactus systemd[1]: Started Login Service.
Nov 25 11:18:57 c-cactus systemd[1]: Started User Manager for UID 1000.
Nov 25 11:18:58 c-cactus systemd[1]: Starting Session c1 of user abe.
Nov 25 11:18:58 c-cactus systemd[1]: Started Session c1 of user abe.
Nov 25 11:18:59 c-cactus systemd[1]: Starting LSB: start or stop the WINGs
display manager...
Nov 25 11:18:59 c-cactus systemd[1]: Started LSB: start or stop the WINGs
display manager.
Nov 25 11:18:59 c-cactus systemd[1]: Starting X11 Display Manager.
Nov 25 11:18:59 c-cactus systemd[1]: Reached target X11 Display Manager.
I can send an even more complete journal log by private e-mail.
-- Package-specific
Bug#767906: libgtk-3-0: Size of menus on screen top is not properly calculated
Hi, On Tue, 25 Nov 2014 10:54:48 +0300, Vlad Orlov wrote: Is there a Debian bug report for [1]? Looks like it's still not fixed. No, all bugs in src:gtk+3.0 with ‘menu’ in title seem irrelevant. -- Dmitry Shachnev signature.asc Description: OpenPGP digital signature
Bug#768163: CUPS and CM option
I think we do not really need this patch. What is does is allowing to set color calibration mode as default setting for a print queue via the CUPS web interface. But this option should only be set when calibrating the printer, not permanently, so Mike Sweet is right that this is a per-job option. It makes much more sense to post feature requests for the print dialogs (GTK, KDE, ...) or even to let it only get supplied by color calibration apps when sending the jobs with the calibrartion pages. The actual execution of the option happens completely in cups-filters, as the color correction based on the ICC profiles is done there. Till On 11/23/2014 01:50 PM, Didier 'OdyX' Raboud wrote: Hi Joe, hi Till, As you might have seen from this Debian bug (#768163), the Color management option is missing all non-english translations. I must say that I'm quite concerned by this Color management patch for the following reasons: - Debian's now in freeze; adding HTML template patches across 9 languages (without having resources to translate these…) is slightly invasive for this freeze phase. - In https://www.cups.org/str.php?L4462, upstream basically refused to accept your patch on a longer term. I will _not_ adopt the maintenance of this patch as Debian maintainer, so that questions the long-term maintainability of this patch. - There's still #763517 about a failure to work correctly (which is arguably in need of more info from the submitter). I'm now considering either of these options: a) Leave it as-is for Jessie; this leaves CUPS in jessie with no non- english translations for this feature at the advantage of not needing much work. I'm still questioning the responsibility for that patch over the course of the jessie stable release lifecycle. b) Patch 9 translations with english content; this makes CUPS in jessie with english texts in native translations, and I'm not sure that it will be accepted at this point of the release cycle by the release team. c) Drop the Color Management patch entirely for the Jessie release cycle: given that upstream has released the 2.0.x series and that, as far as I know, there is no color-management patch available for that codebase yet (and that upstream has declined to include your patch), I tend to think that this is the most future-proof decision for this patch. What's your opinion on this? TIA, cheers, OdyX Le mercredi, 5 novembre 2014, 16.33:26 Pascal Obry a écrit : I just found out that on the CUPS page when defining (or modifying) a printer the Color Calibration Mode check box only appears only when the language of the desktop is set to English. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770908: [Aptitude-devel] Bug#770908: aptitude does not know about the new _apt user. Must use apt-get update as a workaround
AB == Axel Beckert a...@debian.org writes: AB Why should that be grave (in the current situation)? aptitude does not AB work well with apt from experimental yet, yes, see #764506 and AB #762846. But since it's apt from experimental, it's not AB release-critical for Jessie. I was just thinking that the first command one needs to do is aptitude update file:///usr/share/doc/aptitude/html/en/ch01s01s05.html Once you have fresh lists of packages, you can choose the packages to upgrade, install, or remove as described in the previous section. To review the actions you have requested, press g once. When installing the kaffeine-mozilla package (from the previous example), the following screen appears: So they couldn't get started. P.S., from man page -u Begins updating the package lists as soon as the program starts. i.e., very important. update Updates the list of available packages from the apt sources (this is equivalent to apt-get update) Actually no longer equivalent as it is broken. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770330: how to change UID_MIN, UID_MAX, FIRST_GID, LAST_GID, etc.?
android-permissions integrates the Android permissions into a Debian chroot running on Android. This package should only ever run on a Debian chroot running with an Android kernel. It should modify things like GID_MAX or LAST_GID in /etc/login.defs and /etc/adduser.conf to reflect the hard-coded Android UIDs and GIDs, but it is a policy violation for a package to modify those files. Any suggestions as how to best tackle this issue? signature.asc Description: OpenPGP digital signature
Bug#770930: mpv memory leak
Control: reassign -1 libavutil54 Control: retitle -1 libavutil54: lavu memory leak Control: forwarded -1 http://lists.libav.org/pipermail/libav-devel/2014-November/064747.html On mar, nov 25, 2014 at 11:12:17 +0100, Moritz Fiedler wrote: Package: mpv Version: 0.6.2-2 Severity: important Hello, when you use mpv with bigger files it happens that mpv consumes all RAM and swap and the system gets unusable. The mpv team investigated the issue: https://github.com/mpv-player/mpv/issues/1204 It looks like there is a problem with libav. But there is a patch. I think there are two solutions: * compile with ffmpeg There is an mpv package compiled against ffmpeg in experimental (the version is 0.6.2-2+ffmpeg). You may want to try that, however it's not possible to have it in unstable (and thus testing) yet. * patch libav Unfortunately the patch doesn't seem to be merged upstream yet so this may take a while. I filed the bug here, because i only experience the problem with mpv. Still, it's a libav bug, hence reassigning. Cheers signature.asc Description: Digital signature
Bug#718596: (no subject)
Hi, I want to confirm that downgrading to 0.46 version did not solve the problem in my Debian Jessie. To downgrade, I downloaded the deb file of the 0.46 version and installed it using dpkg -i packagename. Is it right? Thanks, Habib -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770231: Amd64-efi installer becomes unresponsive on x86 bios
On Mon, 2014-11-24 at 16:26 -0500, Samuel Comeau wrote: Hello Ian, Well, it appears I have made a mistake about the type of processor that's in here : Intel(R) Pentium(R) 4 CPU 2.80GHz. I think the P4 had 64-bit support in some variants, but it does sound likely that yours isn't one of them. I don't have the text of the menu screen for you yet, I would have to retry installing linux, which I haven't had the time to do yet. I can at least tell you, however, that the menu I got to was very similar to this one http://debian-handbook.info/browse/stable/images/inst-boot.png , OK thanks for clarifying, so you are failing at the bootloader screen and not making it to the installer proper. Given that I think what Steve said regarding not booting amd64 kernels on i386 hardware is probably the most likely theory. I'm not sure why the message about incompatible arch should be AWOL, perhaps related to the bootloader having enabled graphical mode? Does an i386 image work on your system? apart from the fact that my installer boot menu didn't have 64 bit anywhere in it. I think (but I'm not 100% sure) that this is expected for a single arch image, IOW if the image is only for amd64 then you just get Install etc and not 64 bit install. Install will laucn amd64. For dual/multi-arch images then you get both options, one of which launches 32-bit and the other 64-bit. The hang occurs when I try to select any option. Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770938: snapper: Snapshot before and after package upgrades like etckeeper?
Package: snapper
Version: 0.2.4-1
Severity: wishlist
One feature I read about from OpenSuSe is the ability for yast to
snapshot the system before doing package upgrades, to allow rollback and
checking what was changed during the upgrade.
What about adding a similar feature to snapper using a file in
/etc/apt/apt.conf.d/ like etckeeper is, to run snapper before and after
packages are installed and upgraded using apt?
Perhaps something like this (with more arguments, perhaps) would work?
DPkg::Pre-Invoke { if [ -x /usr/bin/snapper ]; then /usr/bin/snapper
-t pre; fi; };
DPkg::Post-Invoke { if [ -x /usr/bin/snapper ]; then /usr/bin/snapper
-t post; fi; };
--
Happy hacking
Petter Reinholdtsen
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770915: ITP: utox -- uTox is a lightweight audio/video chat client based on the secure tox protocol.
Le mardi 25 novembre 2014 à 09:18 +0100, gaffa a écrit : Package: wnpp Severity: wishlist Owner: gaffa ga...@folkemagt.dk * Package name: utox Version : 0+git20141121 Upstream Author : notsecure * URL : https://github.com/notsecure/uTox/ * License : GPL-3 Programming Lang: C Description : uTox is a lightweight audio/video chat client based on the secure tox protocol. Tox is a free P2P audio/video protocol that requires no configuration. Using torrent-style DHT, peers can find the IP of other peers by using their Tox ID. Once the IP is obtained, peers can initiate a secure connection with each other and exchange messages, send files, start video chats, etc. using encrypted communications. I have already created a package for the version mentioned above. There are no official source tarballs and no version tags on the VCS. This package depends on libtoxcore. I've packaged libtoxcore and is currently waiting for replies to the ITP bug report, before I request a sponsor. The package is uploaded to mentors.debian.net hello, i gave utox a try... and it rules, despite being in alpha/a little buggy. You should upload your packaging work on http://mentors.debian.net/ and ask from there. Jérémy. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760177: apticron tells me about packages with pending update that are not even installed
Dear Maintainer, It seems that the bug occurs in mixed stable/testing environment. So it's apt-get error. Regards -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770939: opensmtpd: fails to install: subprocess installed post-installation script returned error exit status 1
Package: opensmtpd Version: 5.4.2p1-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. From the attached log (scroll to the bottom...): Selecting previously unselected package opensmtpd. (Reading database ... 7423 files and directories currently installed.) Preparing to unpack .../opensmtpd_5.4.2p1-3_amd64.deb ... Unpacking opensmtpd (5.4.2p1-3) ... Setting up opensmtpd (5.4.2p1-3) ... dpkg: error processing package opensmtpd (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: opensmtpd Rerunning the test manually and debugging it afterwards: set -x, DEBCONF_DEBUG=developer # dpkg --configure --pending Setting up opensmtpd (5.4.2p1-3) ... + set -e + . /usr/share/debconf/confmodule + [ ! ] + PERL_DL_NONLAZY=1 + export PERL_DL_NONLAZY + [ ] + exec /usr/share/debconf/frontend /var/lib/dpkg/info/opensmtpd.postinst configure debconf (developer): frontend started debconf (developer): frontend running, package name is opensmtpd debconf (developer): starting /var/lib/dpkg/info/opensmtpd.config configure debconf (developer): -- FGET opensmtpd/mailname seen debconf (developer): -- 0 false dpkg: error processing package opensmtpd (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: opensmtpd cheers, Andreas opensmtpd_5.4.2p1-3.log.gz Description: application/gzip
Bug#768133: evince print only blank page in landscape / okular work
Not only Evince affected, see: https://bugzilla.gnome.org/show_bug.cgi?id=739723 How to handle this in Debian Jessie now? Wait for a new Gnome bugfix release? https://wiki.gnome.org/ThreePointFifteen
Bug#767653:
Hi Tobi, thanks for the clearifications, I've pushed a new version. Can you have a look again? Cheers Jochen signature.asc Description: Digital signature
Bug#770941: nova-common - Overrides database config in nova.conf
Package: nova-common Version: 2014.1.3-6 Severity: serious A simple upgrade or re-install of nova-common overrides the database settings in nova.conf: | diff -ur nova/nova.conf /etc/nova/nova.conf | --- nova/nova.conf 2014-10-02 15:09:04.672855761 +0200 | +++ /etc/nova/nova.conf 2014-11-25 12:02:37.194997496 +0100 | @@ -349,7 +349,7 @@ | # DATABASE # | | [database] | -connection = postgresql:///nova | +connection = postgresql://novacommon:X@localhost/novadb | | | # This violates §10.7.3 of the Debian policy: local changes must be preserved. Bastian -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766676: Re : /usr/bin/Xorg: symbol lookup error: /usr/lib/xorg/modules/linux/libglx.so: undefined symbol: LoadExtension
On 2014-11-24 01:41, Anthony Callegaro wrote: Hello guys, I believe I may have found the source of this issue. For some reason I had the amd-opencl-icd-legacy package installed. This is probably a remainder of consecutive upgrades. After replacing it by amd-opencl-icd I do not have the /usr/bin/Xorg: symbol lookup error: /usr/lib/xorg/modules/linux/libglx.so: undefined symbol: LoadExtension error. I don't see how these two could be related ... can you reproduce the problem by installing amd-opencl-icd-legacy again ? Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770940: error: ‘lgamma_r’ was not declared in this scope
Package: libc6-dev
Version: 2.19-13
Severity: important
I cannot compile the following pseudo code (see attachment) it fails with:
$ g++ -ffast-math foo.cxx
In file included from /usr/include/math.h:432:0,
from foo.cxx:3:
/usr/include/x86_64-linux-gnu/bits/math-finite.h: In function ‘double
lgamma(double)’:
/usr/include/x86_64-linux-gnu/bits/math-finite.h:260:41: error:
‘lgamma_r’ was not declared in this scope
return lgamma_r (__d, __local_signgam);
^
/usr/include/x86_64-linux-gnu/bits/math-finite.h: In function ‘float
lgammaf(float)’:
/usr/include/x86_64-linux-gnu/bits/math-finite.h:269:42: error:
‘lgammaf_r’ was not declared in this scope
return lgammaf_r (__d, __local_signgam);
^
/usr/include/x86_64-linux-gnu/bits/math-finite.h: In function ‘long
double lgammal(long double)’:
/usr/include/x86_64-linux-gnu/bits/math-finite.h:279:42: error:
‘lgammal_r’ was not declared in this scope
return lgammal_r (__d, __local_signgam);
^
/usr/include/x86_64-linux-gnu/bits/math-finite.h: In function ‘double
gamma(double)’:
/usr/include/x86_64-linux-gnu/bits/math-finite.h:293:41: error:
‘lgamma_r’ was not declared in this scope
return lgamma_r (__d, __local_signgam);
^
/usr/include/x86_64-linux-gnu/bits/math-finite.h: In function ‘float
gammaf(float)’:
/usr/include/x86_64-linux-gnu/bits/math-finite.h:302:42: error:
‘lgammaf_r’ was not declared in this scope
return lgammaf_r (__d, __local_signgam);
^
/usr/include/x86_64-linux-gnu/bits/math-finite.h: In function ‘long
double gammal(long double)’:
/usr/include/x86_64-linux-gnu/bits/math-finite.h:312:42: error:
‘lgammal_r’ was not declared in this scope
return lgammal_r (__d, __local_signgam);
thanks.
#include errno.h
#undef __USE_MISC
#include math.h
int main(){}
Bug#770814: packagekit-gtk3-module: should depend on packagekit
Quoting Matthias Klumpp (2014-11-25 02:01:39)
2014-11-24 12:19 GMT+01:00 Jonas Smedegaard d...@jones.dk:
Seems package packagekit-gtk3-module is missing a dependency on
packagekit.
The package depends on libpackagekit-glib, which itself recommends
packagekit. Therefore, everything should be fine here.
It seems to me that packagekit-gtk3-module 1.0.1-1 on amd64 do not
depend on anything *packagekit*, nor does it have any reverse
dependencies/recommandations/suggestions at all. It seems to me that
(at least that particular version on this particular architecture) the
package is untied to other parts of packagekit.
Seems an issue also for Jessie - here's on a clean jessie chroot:
root@bastian:/# aptitude --with-recommends install
packagekit-gtk3-module
The following NEW packages will be installed:
adwaita-icon-theme{a} at-spi2-core{a} colord{a} colord-data{a} dbus{a}
dconf-gsettings-backend{a} dconf-service{a} fontconfig{a} fontconfig-config{a}
fonts-dejavu-core{a} glib-networking{a} glib-networking-common{a}
glib-networking-services{a} gsettings-desktop-schemas{a} hicolor-icon-theme{a}
krb5-locales{a} libatk-bridge2.0-0{a} libatk1.0-0{a} libatk1.0-data{a}
libatspi2.0-0{a} libavahi-client3{a} libavahi-common-data{a}
libavahi-common3{a} libcairo-gobject2{a} libcairo2{a} libcap-ng0{a}
libcolord2{a} libcolorhug2{a} libcroco3{a} libcups2{a} libdatrie1{a}
libdbus-1-3{a} libdconf1{a} libexif12{a} libexpat1{a} libffi6{a}
libfile-copy-recursive-perl{a} libfontconfig1{a} libfreetype6{a} libgd3{a}
libgdk-pixbuf2.0-0{a} libgdk-pixbuf2.0-common{a} libglib2.0-0{a}
libglib2.0-data{a} libgnutls-deb0-28{a} libgphoto2-6{a} libgphoto2-l10n{a}
libgphoto2-port10{a} libgraphite2-3{a} libgssapi-krb5-2{a} libgtk-3-0{a}
libgtk-3-bin{a} libgtk-3-common{a} libgudev-1.0-0{a} libgusb2{a}
libharfbuzz0b{a} libhogweed2{a} libieee1284-3{a} libjasper1{a} libjbig0{a}
libjpeg62-turbo{a} libjson-glib-1.0-0{a} libjson-glib-1.0-common{a}
libk5crypto3{a} libkeyutils1{a} libkrb5-3{a} libkrb5support0{a} liblcms2-2{a}
libltdl7{a} libnettle4{a} libp11-kit0{a} libpam-systemd{a} libpango-1.0-0{a}
libpangocairo-1.0-0{a} libpangoft2-1.0-0{a} libpixman-1-0{a} libpng12-0{a}
libpolkit-agent-1-0{a} libpolkit-backend-1-0{a} libpolkit-gobject-1-0{a}
libproxy1{a} librest-0.7-0{a} librsvg2-2{a} librsvg2-common{a} libsane{a}
libsane-common{a} libsane-extras{a} libsane-extras-common{a}
libsoup-gnome2.4-1{a} libsoup2.4-1{a} libtasn1-6{a} libthai-data{a} libthai0{a}
libtiff5{a} libusb-1.0-0{a} libv4l-0{a} libv4lconvert0{a} libvpx1{a}
libwayland-client0{a} libwayland-cursor0{a} libx11-6{a} libx11-data{a}
libxau6{a} libxcb-render0{a} libxcb-shm0{a} libxcb1{a} libxcomposite1{a}
libxcursor1{a} libxdamage1{a} libxdmcp6{a} libxext6{a} libxfixes3{a} libxi6{a}
libxinerama1{a} libxkbcommon0{a} libxml2{a} libxpm4{a} libxrandr2{a}
libxrender1{a} libxtst6{a} packagekit-gtk3-module policykit-1{a} sane-utils{a}
sgml-base{a} shared-mime-info{a} ucf{a} update-inetd{a} x11-common{a}
xdg-user-dirs{a} xkb-data{a} xml-core{a}
0 packages upgraded, 131 newly installed, 0 to remove and 0 not
upgraded.
Need to get 47.1 MB of archives. After unpacking 152 MB will be used.
Nothing *packagekit* other than the package itself will get installed.
What did you do to end up on a system w/o packagekit?
I did not use it on a system, just browsed around in aptitude to locate
packagekit-related resources, for having it covered in Boxer:
https://anonscm.debian.org/cgit/boxer/boxer-data.git/commit/?id=c79e4d5
- Jonas
--
* Jonas Smedegaard - idealist Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/
[x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: signature
Bug#766464: gksu pluma any_file sets the ownership of /run/user/1000/dconf/user to root:root
Control: close -1 Hi All, On Di 25 Nov 2014 09:58:04 CET, Vlad Orlov wrote: Hi, Thank you so much for investigating this issue. I've been busy with my job and various bugs so I never had the time to look into it. However, I've checked systemd's source code and found out the mentioned commit [1] is already there. No wonder - the commit is one year old, and the version of systemd in Debian Testing is already 215. You can check the code yourself to see that (just remember that pam-module.c has been renamed to pam_systemd.c). Also, Debian maintainers have made a lot of patches for systemd, but the only patch that modifies the files in question is [2], and it seems to be minor. So, either the mentioned commit didn't fix the problem completely, or there were some more changes along the way that made the problem appear again. [1] http://cgit.freedesktop.org/systemd/systemd/commit/?id=baae0358f349870544884e405e82e4be7d8add9f [2] http://sources.debian.net/src/systemd/215-6/debian/patches/Start-logind-on-demand-via-libpam-systemd.patch as the underlying issue has been fixed in libpam-systemd 204-8, I close this bug, as well. Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgpeHaDtbaeua.pgp Description: Digitale PGP-Signatur
Bug#770330: ideas from #debian-devel
The package android-permissions integrates the Android permissions into a Debian chroot running on Android. Android permissions are implemented in Android's Linux kernel using UIDs and GIDs. Therefore, this package should only ever run on a Debian chroot running with an Android kernel. It adds all of the hard-coded users and groups to Debian. It should also modify things like GID_MAX or LAST_GID in /etc/login.defs and /etc/adduser.conf to reflect the hard-coded Android UIDs and GIDs. One idea for a solution was to make a debootstrap variant, but I'm not sure that cdebootstrap supports that. The idea is rather than having the package do these changes directly, it provides a script that does the changes to a specified root directory. Then this script is run as part of the variant. Another idea is to create /etc/login.defs.d and /etc/adduser.conf.d so that packages can add definitions there. I'm not sure yet whether either approach is good. signature.asc Description: OpenPGP digital signature
Bug#770942: kernel panic from wlc_ioctl
Package: broadcom-sta-dkms Version: 6.30.223.248-2 Severity: critical this bug report is about a kernel panic that happens pretty reproducibly on two systems with different broadcom card models and kernel builds. in both cases, it does not happen during normal network traffic, but only when the instant messenger gajim is started. i'll call the affected systems by their hostnames. hephaistos has a BCM43142 wifi card and uses the 3.16-1~exp1 kernel. here's a transcript a screenshot's relevant parts (can provide full screenshot if it helps): BUG: unable to handle kernel NULL pointer dereference at 0360 IP: [a062e963] wlc_ioctl+0x21/0x168 [wl] [...] CPU: 1 PID: 21221 Comm: gajim Tainted: P O 3.16-trunk-amd64 #1 Debian 3.16-1~exp1 [...] Call Trace: wl_proc_read+0x40/0xa0 [wl] proc_read_reg+0x34/0x70 vfs_read+0x8e/0x170 SyS_read+0x3d/0xa0 system_call_fast_compare_end+0x10/0x15 hephaistos has been on sid plus some experimental since long, and the behavior first appeared around 2014-10-29. i blamed it on failing hardware (graphics card behaved oddly at the same time) and replaced the device. artemis has a BCM4313, and was recently (around 2014-11-20) upgraded from wheezy to jessie. it has a 3.16.0-4-amd64 kernel. its backtrace only differs in gajim PID, kernel taint (there's an additional W), kernel version (3.16.0-4-amd64 #1 Debian 3.16.7-2) and the details of the call trace (the +0x00 part is larger by 5 for all but system_call_fast_compare_end). i'll try to further narrow down which kernel versions are affected, and what kind of traffic causes the issue (my first wild guess would be multicasting, which gajim probably does for lan-local autodiscovery). is there any further information i can provide to find a solution for this? -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages broadcom-sta-dkms depends on: ii dkms 2.2.0.3-2 Versions of packages broadcom-sta-dkms recommends: ii wireless-tools 30~pre9-8 broadcom-sta-dkms suggests no packages. -- To use raw power is to make yourself infinitely vulnerable to greater powers. -- Bene Gesserit axiom signature.asc Description: Digital signature
Bug#770918: patches
Attached patches from upstream, which apply to 1.2.1-6. DSA should be created.
---
Henri Salo
--- src/libFLAC/stream_decoder.c.orig 2014-11-25 13:41:50.280032892 +0200
+++ src/libFLAC/stream_decoder.c 2014-11-25 13:48:39.697566936 +0200
@@ -94,7 +94,7 @@
*
***/
-static FLAC__byte ID3V2_TAG_[3] = { 'I', 'D', '3' };
+static const FLAC__byte ID3V2_TAG_[3] = { 'I', 'D', '3' };
/***
*
@@ -1386,6 +1386,10 @@
id = 0;
continue;
}
+
+ if(id = 3)
+ return false;
+
if(x == ID3V2_TAG_[id]) {
id++;
i = 0;
--- src/libFLAC/stream_decoder.c.orig 2014-11-25 13:41:50.280032892 +0200
+++ src/libFLAC/stream_decoder.c 2014-11-25 13:46:21.862277460 +0200
@@ -2726,7 +2726,8 @@
if(decoder-private_-frame.header.blocksize predictor_order) {
send_error_to_client_(decoder, FLAC__STREAM_DECODER_ERROR_STATUS_LOST_SYNC);
decoder-protected_-state = FLAC__STREAM_DECODER_SEARCH_FOR_FRAME_SYNC;
- return true;
+ /* We have received a potentially malicious bt stream. All we can do is error out to avoid a heap overflow. */
+ return false;
}
}
else {
signature.asc
Description: Digital signature
Bug#765093: Following up
Hi, Is there any news about this bug? I'm still having problems with it, 4 to 5 times a week.
Bug#770943: When built using newer Qemu, openstack-debian-images produces an image that doesn't work on older Qemu
Package: openstack-debian-images Version: 1.0 Severity: important Building an image needs the option -o compat=0.10 so that the image can work on older Qemu, like the ones that are often on public clouds (like the one at HP). I'm uploading a fix soon. Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770941: neutron-common - Overrides database config in neutron.conf and fails to upgrade
Control: clone -1 -2 Control: reassign -2 neutron-common 2014.1.3-6 Hi The same is true for neutron-common. However it have the additional problem that postinst actually fails: | Installing new version of config file /etc/neutron/rootwrap.d/l3.filters ... | Installing new version of config file /etc/neutron/policy.json ... | Installing new version of config file /etc/logrotate.d/neutron-common ... | PKG-Openstack now calling: dbc_go neutron-common configure 2014.1.2-1~bpo70+1 | dbconfig-common: writing config to /etc/dbconfig-common/neutron-common.conf | dbconfig-common: flushing administrative password | No handlers could be found for logger neutron.common.legacy | Traceback (most recent call last): | File /usr/bin/neutron-db-manage, line 10, in module | sys.exit(main()) | File /usr/lib/python2.7/dist-packages/neutron/db/migration/cli.py, line 169, in main | CONF.command.func(config, CONF.command.name) | File /usr/lib/python2.7/dist-packages/neutron/db/migration/cli.py, line 82, in do_upgrade_downgrade | do_alembic_command(config, cmd, revision, sql=CONF.command.sql) | File /usr/lib/python2.7/dist-packages/neutron/db/migration/cli.py, line 60, in do_alembic_command | getattr(alembic_command, cmd)(config, *args, **kwargs) | File /usr/lib/python2.7/dist-packages/alembic/command.py, line 124, in upgrade | script.run_env() | File /usr/lib/python2.7/dist-packages/alembic/script.py, line 199, in run_env | util.load_python_file(self.dir, 'env.py') | File /usr/lib/python2.7/dist-packages/alembic/util.py, line 199, in load_python_file | module = load_module(module_id, path) | File /usr/lib/python2.7/dist-packages/alembic/compat.py, line 55, in load_module | mod = imp.load_source(module_id, path, fp) | File /usr/lib/python2.7/dist-packages/neutron/db/migration/alembic_migrations/env.py, line 103, in module | run_migrations_online() | File /usr/lib/python2.7/dist-packages/neutron/db/migration/alembic_migrations/env.py, line 78, in run_migrations_online | connection = engine.connect() | File /usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py, line 1641, in connect | return self._connection_cls(self, **kwargs) | File /usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py, line 59, in __init__ | self.__connection = connection or engine.raw_connection() | File /usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py, line 1699, in raw_connection | return self.pool.unique_connection() | File /usr/lib/python2.7/dist-packages/sqlalchemy/pool.py, line 220, in unique_connection | return _ConnectionFairy(self).checkout() | File /usr/lib/python2.7/dist-packages/sqlalchemy/pool.py, line 431, in __init__ | rec = self._connection_record = pool._do_get() | File /usr/lib/python2.7/dist-packages/sqlalchemy/pool.py, line 871, in _do_get | return self._create_connection() | File /usr/lib/python2.7/dist-packages/sqlalchemy/pool.py, line 225, in _create_connection | return _ConnectionRecord(self) | File /usr/lib/python2.7/dist-packages/sqlalchemy/pool.py, line 318, in __init__ | self.connection = self.__connect() | File /usr/lib/python2.7/dist-packages/sqlalchemy/pool.py, line 379, in __connect | connection = self.__pool._creator() | File /usr/lib/python2.7/dist-packages/sqlalchemy/engine/strategies.py, line 80, in connect | return dialect.connect(*cargs, **cparams) | File /usr/lib/python2.7/dist-packages/sqlalchemy/engine/default.py, line 283, in connect | return self.dbapi.connect(*cargs, **cparams) | File /usr/lib/python2.7/dist-packages/psycopg2/__init__.py, line 179, in connect | connection_factory=connection_factory, async=async) | sqlalchemy.exc.OperationalError: (OperationalError) could not connect to server: Connection refused | Is the server running on host localhost (127.0.0.1) and accepting | TCP/IP connections on port 5432? | None None | dpkg: error processing neutron-common (--configure): | subprocess installed post-installation script returned error exit status 1 | dpkg: dependency problems prevent configuration of neutron-server: -- Bastian Blank Berater Telefon: +49 2161 / 4643-194 E-Mail: bastian.bl...@credativ.de credativ GmbH, HRB Mönchengladbach 12080, USt-ID-Nummer: DE204566209 Hohenzollernstr. 133, 41061 Mönchengladbach Geschäftsführung: Dr. Michael Meskes, Jörg Folz, Sascha Heuer -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769072: , #769191, #770588: nvidia-opencl-icd breaking non-nvidia systems
On 2014-11-24 22:47, Rebecca N. Palmer wrote: First of all, many thanks for analyzing the problem and keeping track of the many duplicates! (Should we merge these bugs? Also, #767803 looks like another instance of this, though it doesn't have the apt log to confirm it yet) and perhaps move the discussion to one of these bugs and trim the Cc list a bit ... If you merge them, please reassign them to src:nvidia-driver and add Affects for the packages where they have been reported. * nvidia-kernel-dkms: Switch to Recommends: nvidia-driver | libcuda1 to break the chain libcuda1 - nvidia-kernel-dkms - nvidia-driver. ...or drop this Recommends: entirely That Recommends has been there since nvidia-kernel-dkms was added in 2010. I thinks its main purpose is for people that try to install the wrong package (i.e. nvidia-kernel-dkms instead of nvidia-driver (or nvidia-glx back then)) to get a working NVIDIA driver installation (well, still needs some manual configuration, but debconf will tell you that). I don't want to touch (as in remove) that right now. (IIRC circular Depends/Recommends are discouraged because they confuse apt's autoremover, though I can't find where I saw that). I don't want to workaround bugs in unrelated packages Cutting the chain here (tested with apt-get install nvidia-libopencl1 nvidia-driver-, the - after a package means remove/don't install) does still allow much of nvidia-* (including nvidia-kernel-dkms and glx-alternative-nvidia) to be installed, but that appears to be harmless and you get the full set of lib*GL* diversions, too ... this and some more are needed to allow switching between nvidia-opencl-icd and nvidia$LEGACY-opencl-icd which will become available once I fork off (and backport) nvidia-graphics-drivers-legacy-340xx after the jessie release. without libgl1-nvidia-glx (at least on my Intel IvyBridge M GT2, both graphics and OpenCL continue to work after rebooting). That would be a bug otherwise :-) Given that the error on loading nvidia-opencl-icd in a non-Nvidia system is modprobe: ERROR: could not insert 'nvidia_current': No such device it is plausible that nvidia-opencl-icd uses the nvidia kernel module (i.e. nvidia-kernel-dkms | nvidia-kernel-version) and as such _should_ pull it in (whether or not it also needs libcuda1), In wheezy all this OpenCL stuff was rather new and only proprietary implementations were available ... as a result installing nvidia-opencl-icd was harmless (due to lack of dependencies) but also useless (due to lack of dependencies) unless you had nvidia-driver installed, too. This I wanted to fix in jessie :-) while #768185 suggests that nvidia-opencl-icd works without the graphics side (can someone check that?), I'm pretty sure NVIDIA CUDA and OpenCL work in headless setups, i.e. without X server running. They just need the kernel module to be loaded (and the corresponding device to be created). (Contrary to AMD which needs X to communicate with the GPU for doing OpenCL) making this the more correct place to cut the chain. Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770328: (no subject)
Thanks for the patch, I'm working on including it now. Unfortunately, android-platform-system-core_21-4 does not fix the other related bug: https://bugs.debian.org/769251 I'm working on that still, that fix will be in a different package: android-platform-frameworks-native .hc signature.asc Description: OpenPGP digital signature
Bug#762670: libjavascriptcoregtk-3.0-0: crashes on ppc64el when building sphinx
On Mon, Nov 24, 2014 at 01:23:56PM +0400, Dmitry Shachnev wrote: If you could give that patch a try we can try to have it included in jessie. Sorry for the delay. We finally managed to test it (actually it was Laney who did that). With the patch from Fedora, sphinx builds successfully on ppc64el. But then did you try the patch from Fedora or the one from the upstream bugzilla? Berto -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770945: ITP: libemail-stuffer-perl -- A more casual approach to creating and sending Email:: emails
Package: wnpp Owner: Dominique Dumont d...@debian.org Severity: wishlist X-Debbugs-CC: debian-de...@lists.debian.org,debian-p...@lists.debian.org * Package name: libemail-stuffer-perl Version : 0.009 Upstream Author : Adam Kennedy ad...@cpan.org, Ricardo SIGNES r...@cpan.org * URL : https://metacpan.org/release/Email-Stuffer * License : Artistic or GPL-1+ Programming Lang: Perl Description : A more casual approach to creating and sending Email:: emails The basics should all work, but this module is still subject to name and/or API changes Email::Stuffer, as its name suggests, is a fairly casual module used to stuff things into an email and send them. It is a high-level module designed for ease of use when doing a very specific common task, but implemented on top of the light and tolerable Email:: modules. Email::Stuffer is typically used to build emails and send them in a single statement, as seen in the synopsis. And it is certain only for use when creating and sending emails. As such, it contains no email parsing capability, and little to no modification support. To re-iterate, this is very much a module for those slap it together and fire it off situations, but that still has enough grunt behind the scenes to do things properly. -- https://github.com/dod38fr/ -o- http://search.cpan.org/~ddumont/ http://ddumont.wordpress.com/ -o- irc: dod at irc.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#770946: Improved default ruleset
Package: ferm
Version: 2.2-3
Severity: wishlist
Tags: upstream
Please consider the attached ruleset as an alternative to the
default. It is functionally equivalent and the user needs not change
anything, but it provides the following benefits:
1. IPsec and SSH acceptance are configurable at the top;
2. It is possible to exclude additional interfaces like lo (e.g.
interfaces used for SAN);
3. It is trivially possible to configure REJECT instead of DROP,
which is nicer on everyone;
4. Instead of droppping INVALID packets and then passing through
filter rules, three new chains {input,forward,output}-new are
available which receive only truly NEW packets. However, since
processing then falls back to the main chains, their use is
optional (though recommended);
5. The same ruleset applies to both IPv4 and IPv6.
This is what the result looks like:
*filter
:INPUT DROP [0:0]
:FORWARD DROP [0:0]
:OUTPUT DROP [0:0]
:forward-new - [0:0]
:input-new - [0:0]
:output-new - [0:0]
-A INPUT -i lo -j ACCEPT
-A INPUT -m state --state INVALID -j REJECT --reject-with icmp-admin-prohibited
-A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
-A INPUT -m state --state NEW -j input-new
-A FORWARD -m state --state INVALID -j REJECT --reject-with
icmp-admin-prohibited
-A FORWARD -m state --state RELATED,ESTABLISHED -j ACCEPT
-A FORWARD -m state --state NEW -j forward-new
-A OUTPUT -m state --state INVALID -j REJECT --reject-with icmp-admin-prohibited
-A OUTPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
-A OUTPUT -m state --state NEW -j output-new
-A forward-new -p icmp -j ACCEPT
-A input-new -p icmp -j ACCEPT
-A input-new -p udp -m udp --dport 500 -j ACCEPT
-A input-new -p esp -j ACCEPT
-A input-new -p ah -j ACCEPT
-A input-new -p tcp -m tcp --dport 22 -j ACCEPT
-A output-new -j ACCEPT
COMMIT
For reference, this is the current result:
*filter
:INPUT DROP [19:1342]
:FORWARD DROP [0:0]
:OUTPUT ACCEPT [0:0]
-A INPUT -m state --state INVALID -j DROP
-A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -p icmp -j ACCEPT
-A INPUT -p udp -m udp --dport 500 -j ACCEPT
-A INPUT -p esp -j ACCEPT
-A INPUT -p ah -j ACCEPT
-A INPUT -p tcp -m tcp --dport 22 -j ACCEPT
-A FORWARD -m state --state INVALID -j DROP
-A FORWARD -m state --state RELATED,ESTABLISHED -j ACCEPT
-A OUTPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
COMMIT
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages ferm depends on:
ii debconf 1.5.53
ii iptables 1.4.21-2
ii lsb-base 4.1+Debian13
ii perl 5.20.1-1
Versions of packages ferm recommends:
ii libnet-dns-perl 0.80-1
ferm suggests no packages.
--
.''`. martin f. krafft madduck@d.o @martinkrafft
: :' : proud Debian developer
`. `'` http://people.debian.org/~madduck
`- Debian - when you have better things to do than fixing systems
# ferm.conf
#
# Sensible, secure default ferm configuration file with configurable
# parameters and IPv4/IPv6 support.
#
# Copyright (c) 2009-2014 Martin F. Krafft madd...@debian.org
# Released under the GPLv2+, like ferm itself.
#
### DEFAULTS
@def $ACCEPT_INCOMING_IPSEC = 1;
@def $ACCEPT_INCOMING_SSH = 1;
@def $UNWALLED_IFACES = (lo);
@def $REJECT_INSTEAD_OF_DROP = 0;
# names of the chains that should then actually be used for filtering
@def $INPUT_FILTER_CHAIN = input-new;
@def $FORWARD_FILTER_CHAIN = forward-new;
@def $OUTPUT_FILTER_CHAIN = output-new;
### CHAIN POLICIES ###
domain (ip ip6) {
# be on the safe side and drop everything
table filter chain (INPUT FORWARD OUTPUT) policy DROP;
# … which does not make sense in the mangle table
table mangle chain (INPUT PREROUTING FORWARD POSTROUTING OUTPUT)
policy ACCEPT;
}
domain ip {
# no nat table in the ip6 domain
table nat chain (PREROUTING POSTROUTING OUTPUT) policy ACCEPT;
}
### HELPERS #
@def CONNTRACK_NEW_PACKETS_INTO($sourcechain, $newchain) = {
table filter chain $sourcechain {
# reject invalid packets
mod state state INVALID REJECT reject-with icmp-admin-prohibited;
# accept existing connections.
mod state state (ESTABLISHED RELATED) ACCEPT;
# and put new connections into their own chain. This is safer since it
# lets packets that conntrack cannot qualify properly fall through into the
# policy, rather than to let it run through the regular filter chains.
mod state state NEW jump $newchain;
}
}
### FILTER RULES #
## STANDARDS
# exclude unwalled
Bug#766670: RC bug in stable and oldstable for getmail4
On Tue, Nov 25, 2014 at 10:04:34AM +0100, Raphael Hertzog wrote: Hi, On Sun, 23 Nov 2014, Osamu Aoki wrote: By the way, I uploaded getmail4_4.46.0-1~bpo70+1_amd64 We can consider a new upstream version for squeeze-lts and we can ask the security team's opinion for wheezy. Would you like to prepare a 4.46.0-1~deb6u1.dsc working in squeeze and submit it for review to debian-...@lists.debian.org ? See below. It does not look like simple re-versioning and safe backporting without careful review. It would be nice if you could test it though, because we don't have many testers before release... I only use this package for POP3. Most of the changes are in IMAP4 code so my test with POP3 is useless. Henrique's test on my backported package is the good reference. https://ftp-master.debian.org/new/getmail4_4.46.0-1~bpo70%2B1.html I build this under pure wheezy chroot. This can probably be renumbered 4.46.0-1~deb7u1.dsc and submitted to the security team ? Or does it depend on other packages from backports ? This package is one of those python package using debian/rules as: %: dh $@ --with python2 Since I build this jessie package in the old jessie/sid environment which is very similar to released wheezy, I was not asked to add the dh-python dependency to the debian/control. In wheezy, --with python2 is supported via python package, as I understood. So building for wheezy point release is simple and safe with bumping version to 4.46.0-1~deb7u1. I am not quite sure what change is needed for backporting python package with older python helper scripts. Also, I do not know if compat 8 is supported by squeeze. (as for debhelper, I see no major issue as long as compat7 is provided.) Thus, squeeze is a bit more complicated and requires more testing. FYI: I moved to current packaging style in 2011-07 with 4.20.3-1 The oldstable package oldstable 4.20.0-1 was made with different python helper script in 2010-07. (If I do this backport as my job, I will probably keep old packaging style.) For all practical purpose, if someone needs to use this package under oldstable, he should do so by just dpkg -i newpackage since python helper script does not matter for binary packages. I am not really motivated to do this Osamu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759588: [pkg-cryptsetup-devel] Bug#759588: release-notes: Disk encrypted with cryptsetup LUKS whirlpool needs to be migrated manually
On Tue, Nov 25, 2014 at 08:33:06AM +0100, Niels Thykier wrote: On Thu, 11 Sep 2014 23:15:00 +0200 Jonas Meurer jo...@freesources.org wrote: Am 11.09.2014 um 16:43 schrieb Osamu Aoki: [...] Proposed text with or without grep thing looks good tome. Regards, Osamu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762993: xserver-xorg-video-intel: LVDS display blanks when DP is plugged in
reassign 762993 src:linux 3.16.7-2 tags 762993 upstream thanks On Mon, Nov 24, 2014 at 10:52:24PM +0200, Alberto Garcia wrote: [3.164796] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0 [7.101437] [drm:intel_dp_aux_native_write] *ERROR* too many retries, giving up [7.101449] [drm:intel_dp_start_link_train] *ERROR* failed to enable link training [7.108350] [drm:intel_dp_aux_native_write] *ERROR* too many retries, giving up [7.108367] [drm:intel_dp_complete_link_train] *ERROR* failed to start channel equalization [7.140438] [drm:cpt_verify_modeset] *ERROR* mode set failed: pipe A stuck [7.204652] WARNING: CPU: 0 PID: 1129 at /build/linux-2CRRWB/linux-3.14.15/drivers/gpu/drm/i915/intel_display.c:9468 intel_modeset_check_state+0x62c/0x770 [i915]() [7.204659] Modules linked in: bnep btusb bluetooth uvcvideo videobuf2_vmalloc 6lowpan_iphc videobuf2_memops videobuf2_core videodev media openafs(PO) binfmt_misc nfsd auth_rpcgss oid_registry nfs_acl nfs lockd fscache sunrpc x86_pkg_temp_thermal intel_powerclamp arc4 intel_rapl joydev coretemp snd_hda_codec_hdmi hid_multitouch iwldvm kvm mac80211 crc32_pclmul snd_hda_codec_realtek crc32c_intel snd_hda_codec_generic ghash_clmulni_intel iTCO_wdt iTCO_vendor_support aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd iwlwifi evdev psmouse pcspkr serio_raw i2c_i801 i915 cfg80211 snd_hda_intel snd_hda_codec thinkpad_acpi snd_hwdep ac nvram snd_pcm mei_me wmi rfkill drm_kms_helper mei snd_timer battery drm snd soundcore tpm_tis tpm i2c_algo_bit i2c_core lpc_ich video mfd_core button shpchp processor fuse parport_pc ppdev lp parport autofs4 usbhid hid ext4 crc16 mbcache jbd2 sg sd_mod crc_t10dif crct10dif_generic crct10dif_pclmul crct10dif_common ehci_pci ahci ehci_hcd xhci_hcd libahci libata sdhci_pci sdhci scsi_mod mmc_core usbcore thermal usb_common thermal_sys [7.204919] [a02ccbd5] ? drm_mode_set_config_internal+0x55/0xd0 [drm] [7.204936] [a02cf7ab] ? drm_mode_setcrtc+0xeb/0x5a0 [drm] [7.204952] [a02c189d] ? drm_ioctl+0x42d/0x530 [drm] [7.205009] [drm:intel_pipe_config_compare] *ERROR* mismatch in has_dp_encoder (expected 1, found 0) This seems to be a kernel bug, see https://bugs.freedesktop.org/show_bug.cgi?id=81537 There's also a workaround suggested there. The workaround seems to work for me, the computer no longer crashes, although when plugging an external monitor sometimes the brightness of my laptop screen is set to 0 and I have to increase it manually, but it otherwise seems stable. Reassigning bug to the kernel. Berto -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769830: (no subject)
source is included for these minified javascripts, in the debian directory. -- Salvo Tomaselli Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di senso, ragione ed intelletto intendesse che noi ne facessimo a meno. -- Galileo Galilei http://ltworf.github.io/ltworf/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769947: mate-terminal: Segfaults after update
Control: severity -1 grave Control: tag -1 moreinfo Hi all, On Mo 17 Nov 2014 21:09:15 CET, Alex Corcoles wrote: Package: mate-terminal Version: 1.8.1+dfsg1-2 Severity: important Hi, After my latest apt-get upgrade, mate-terminal segfaults on start. $ gdb mate-terminal GNU gdb (Debian 7.7.1+dfsg-5) 7.7.1 (gdb) run Starting program: /usr/bin/mate-terminal [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. Program received signal SIGSEGV, Segmentation fault. get_initial_workspace () at terminal.c:539 539 terminal.c: No such file or directory. (gdb) where #0 get_initial_workspace () at terminal.c:539 #1 main (argc=1, argv=0x7fffe388) at terminal.c:645 (gdb) continue Continuing. Program terminated with signal SIGSEGV, Segmentation fault. The program no longer exists. (gdb) where No stack. (gdb) quit (I'm afraid my gdb skills are pretty much non-existent) Cheers, Alex Raising severity to RC bug status for now. It would be good if either of you (Alex, Ben) could provide more info on how you use mate-terminal (locale, with MATE desktop, in some other X11 context, what theme, etc.). As I personally can not reproduce this bug, I am unsure how to narrow down its cause. Is there a way for me to reproduce this issue on a freshly installed system? Any recipe that you can give? Greets, Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgpwoGdDG8Mzf.pgp Description: Digitale PGP-Signatur
Bug#602378: Please can you try 4.1 from Wheezy
Control: tag -1 +moreinfo Looks like I failed to cc -submitter with that previous request, sorry. I suppose the question should now be extended to the Xen 4.4 packages in Jessie. Thanks, Ian. On Mon, Jul 09, 2012 at 04:10:51PM -0600, Ian Campbell wrote: There's a couple of patches in 4.1 which might plausibly be the fix for this. changeset: 23246:8f927378135a user:Jan Beulich jbeul...@suse.com date:Wed Mar 07 08:35:58 2012 + files: xen/arch/ia64/xen/domain.c xen/arch/x86/domain.c xen/arch/x86/domctl.c description: passthrough: release assigned PCI devices earlier during domain shutdown changeset: 22133:9c5f084135b8 user:Keir Fraser keir.fra...@citrix.com date:Mon Sep 13 17:00:10 2010 +0100 files: xen/common/page_alloc.c description: page_alloc: Check neighbouring chunks belong to same NUMA node before merging in free_heap_pages(). (the latter being the fix for http://mid.gmane.org/bay121-w4629fe3344480f9671824cda...@phx.gbl which Bastian referred to earlier.) Is there any chance that you could try with the Xen packages from Wheezy and see if this issue has been fixed. Thanks, Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#665433: xen hypervisor FATAL PAGE FAULT after linux kernel BUG: unable to handle kernel paging request
Control: tag -1 +moreinfo Hi Daniel, You say you weren't able to reproduce back then, so I suspect I know what the answer will be, but are you able to reproduce this with the Xen packages from Wheezy and/or Jessie? If this was just a one-off with the Squeeze version of the hypervisor then I'd be inclined to close it by now. Thanks, Ian. On Fri, Mar 23, 2012 at 11:12:53PM -0400, Daniel Kahn Gillmor wrote: Package: xen-hypervisor-4.0-i386 Version: 4.0.1-4 This is the same machine referenced in http://bugs.debian.org/665413. It is an HP d530 SFF workstation (model DG784A) with 4GiB of RAM. It has run for years on the lenny xen + linux stack. If my notes are correct, it also ran smoothly for about a year with the lenny hypervisor + kernel and the squeeze userland. Rebooting into squeeze xen + linux makes the machine very crashy. The dom0 kernel often crashes, and the xen hypervisor also crashes. This is a report of a hypervisor crash (i have not been able to reproduce it, because the machine does not actually reboot in 5 seconds as claimed, and physical access to hard-reset the box is more time-consuming than i'd like): [ 471.094798] BUG: unable to handle kernel paging request at c1194b18 [ 471.094827] IP: [c104fe70] prepare_creds+0x39/0x82 [ 471.094850] *pdpt = 1dd86001 *pde = 02e31067 *pte = 01194061 [ 471.094875] Oops: 0003 [#2] SMP [ 471.094890] last sysfs file: /sys/module/mii/initstate (XEN) [ Xen-4.0.1 x86_32p debug=n Not tainted ] (XEN) CPU:0 (XEN) EIP:e008:[0fff] ??? (XEN) EFLAGS: 00010092 CONTEXT: hypervisor (XEN) eax: ffb80280 ebx: 0004 ecx: edx: 0004 (XEN) esi: ff32bf8c edi: ff32bfb8 ebp: ff32bf88 esp: ff32becc (XEN) cr0: 8005003b cr4: 06f0 cr3: d148 cr2: 0fff (XEN) ds: e010 es: e010 fs: 00d8 gs: 00e0 ss: e010 cs: e008 (XEN) Xen stack trace from esp=ff32becc: (XEN)ff15004d 0004 0004 ffbd8000 feda8970 (XEN)000b ffb80280 ff32bfb4 ff32bfb4 ffb80280 ff14e079 0004 2f69696d (XEN)6cb90e00 006e c3246050 39194000 f7bbda34 ff111a16 0001 (XEN)0001 7ff0 0004 c3246050 0020 (XEN)ffb8029c ffbd8000 0972eb40 ff226000 ff32bfb4 c1194b18 ff32bfb4 c1194b18 (XEN)ff16963b 3ffc e010 e010 ef29 ff147642 ff32bf88 3ffc (XEN)e010 c14800fc 007b 007b ef29 0011 00f1 ff1ccc93 (XEN)e008 0203 3ffc c14800fc c1489fbc ef29 ef29 (XEN)0011 000e0003 c1002227 0061 0246 de6b5cfc 0069 007b (XEN)007b 00d8 00e0 ffbd8000 (XEN) Xen call trace: (XEN)[0fff] ??? (XEN)[ff15004d] move_masked_irq+0x9d/0xc0 (XEN)[ff14e079] do_IRQ+0x89/0x650 (XEN)[ff111a16] do_multicall+0x156/0x2c0 (XEN)[ff16963b] do_page_fault+0x10b/0x320 (XEN)[ff147642] common_interrupt+0x52/0x60 (XEN)[ff1ccc93] hypercall+0x53/0x9b (XEN) (XEN) Pagetable walk from 0fff: (XEN) L3[0x000] = d147f001 0001f01f (XEN) L2[0x07f] = (XEN) (XEN) (XEN) Panic on CPU 0: (XEN) FATAL PAGE FAULT (XEN) [error_code=] (XEN) Faulting linear address: 0fff (XEN) (XEN) (XEN) Reboot in five seconds... I'll be happy to report other details when i can get around to rebooting the machine; feel free to request any data you need that might be helpful in debugging. Thanks for maintaining xen in debian! Regards, --dkg -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
