Bug#846570: aptitude: Fails when trying to upgrade apt
affects 846570 apt thanks I was able to continue by running "dpkg --configure --pending", which set up the "apt" package without further issues, then re-running "aptitude safe-upgrade" to upgrade the remaining packages. Ulrich
Bug#846570: aptitude: Fails when trying to upgrade apt
Package: aptitude Version: 0.8.3-1+b2 Severity: important When running an "aptitude safe-upgrade" on a Debian testing system that, among other things, was meant to upgrade the apt package (from 1.3.1 to 1.4~beta1), I got this output: > ... > Vorbereitung zum Entpacken von .../libapt-pkg5.0_1.4~beta1_amd64.deb ... > Entpacken von libapt-pkg5.0:amd64 (1.4~beta1) über (1.3.1) ... > libapt-pkg5.0:amd64 (1.4~beta1) wird eingerichtet ... > (Lese Datenbank ... 266980 Dateien und Verzeichnisse sind derzeit > installiert.) > Vorbereitung zum Entpacken von .../0-libapt-inst2.0_1.4~beta1_amd64.deb ... > Entpacken von libapt-inst2.0:amd64 (1.4~beta1) über (1.3.1) ... > Vorbereitung zum Entpacken von .../1-apt_1.4~beta1_amd64.deb ... > Entpacken von apt (1.4~beta1) über (1.3.1) ... > dpkg: Fehler: dpkg-Status-Datenbank ist von einem anderen Prozess gesperrt > dpkg: Fehler: dpkg-Status-Datenbank ist von einem anderen Prozess gesperrt > dpkg: Fehler: dpkg-Status-Datenbank ist von einem anderen Prozess gesperrt > E: Sub-process /usr/bin/dpkg returned an error code (2) > E: Unterprozess dpkg --set-selections hat Fehlercode zurückgegeben (2) > E: Couldn't revert dpkg selection for approved remove/purge after an error > was encountered! > E: Unterprozess dpkg --set-selections hat Fehlercode zurückgegeben (2) > E: Couldn't restore dpkg selection states which were present before this > interaction! > dpkg: Fehler: dpkg-Status-Datenbank ist von einem anderen Prozess gesperrt > E: Konnte Sperre /var/lib/dpkg/lock nicht bekommen - open (11: Die Ressource > ist zur Zeit nicht verfügbar) > E: Sperren des Administrationsverzeichnisses (/var/lib/dpkg/) nicht möglich, > wird es von einem anderen Prozess verwendet? > E: Die System-Sperre konnte nicht zurückerlangt werden! (Vielleicht läuft > noch ein apt oder dpkg?) > E: Konnte Sperre /var/lib/dpkg/lock nicht bekommen - open (11: Die Ressource > ist zur Zeit nicht verfügbar) > E: Sperren des Administrationsverzeichnisses (/var/lib/dpkg/) nicht möglich, > wird es von einem anderen Prozess verwendet? > > Aktueller Status: 1 (+1) broken, 182 (-13) upgradable. > W: Zwischenspeicher-Datei konnte nicht gesperrt werden. Das bedeutet in der > Regel, dass dpkg oder ein anderes APT-Werkzeug bereits Pakete installiert. > Öffnen im Nur-Lesen-Modus. Alle Änderungen, die Sie am Status von Paketen > durchführen, werden VERLOREN gehen! The messages are mostly in German. The essential point, however, is that dpkg could not get a lock on its database. I had of course no parallel invocation of aptitude, apt, dpkg or anything running at the time, only this "aptitude safe-upgrade". It may be that it is actually a bug in a script for the apt package? If so, please feel free to reassign. Ulrich -- Package-specific info: Terminal: xterm $DISPLAY is set. which aptitude: /usr/bin/aptitude aptitude version information: aptitude 0.8.3 Compiler: g++ 6.2.0 20161103 Compiled against: apt version 5.0.0 NCurses version 6.0 libsigc++ version: 2.10.0 Gtk+ support disabled. Qt support disabled. Current library versions: NCurses version: ncurses 6.0.20160917 cwidget version: 0.5.17 Apt version: 5.0.1 aptitude linkage: linux-vdso.so.1 (0x7ffe5fba) libapt-pkg.so.5.0 => /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0 (0x7fdabba1) libncursesw.so.5 => /lib/x86_64-linux-gnu/libncursesw.so.5 (0x7fdabb7e) libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5 (0x7fdabb5b6000) libsigc-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 (0x7fdabb3af000) libcwidget.so.3 => /usr/lib/x86_64-linux-gnu/libcwidget.so.3 (0x7fdabb0b2000) libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 (0x7fdabada8000) libboost_iostreams.so.1.62.0 => /usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.62.0 (0x7fdabab9) libboost_filesystem.so.1.62.0 => /usr/lib/x86_64-linux-gnu/libboost_filesystem.so.1.62.0 (0x7fdaba977000) libboost_system.so.1.62.0 => /usr/lib/x86_64-linux-gnu/libboost_system.so.1.62.0 (0x7fdaba773000) libxapian.so.30 => /usr/lib/x86_64-linux-gnu/libxapian.so.30 (0x7fdaba365000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fdaba148000) libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x7fdab9dc5000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fdab9ac1000) libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x7fdab98aa000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fdab950c000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fdab9308000) libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 (0x7fdab90f1000) libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7fdab8ed5000) libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 (0x7fdab8cc5000)
Bug#839112: vim: please provide vim-legacy packages
retitle 839112 Please revert to previous default settings thanks I also consider this change of defaults (the "mouse=a" change, at least) a bug and would like to have it reverted. It is a very disruptive change; to me, it was a sudden "WTF?! Pasting text from another terminal no longer works!". If, on the other hand, this is going to stay, users definitely need to be warned about this change when upgrading the package. Furthermore in that case, /etc/vim/vimrc needs updating. It currently says (and has said for years), among other things: " The following are commented out as they cause vim to behave a lot " differently from regular Vi. They are highly recommended though. (...) "set mouse=a" Enable mouse usage (all modes) It should instead say something to the effect of mouse usage being enabled for all modes by default despite it being very differently from Vi, and how to disable it. Ulrich
Bug#800576: gitk --all doesn’t work anymore in some locales
tags 800576 + upstream fixed-upstream thanks I can confirm that the (trivial) upstream change mentioned by Jerome above fixes this issue. Ulrich
Bug#801514: firmware-realtek: Please include rtl8821a_fw.bin
Package: firmware-realtek Version: 0.44 Severity: wishlist There is an rtl_bt/rtl8821a_fw.bin file in the upstream linux-firmware repository (added in commit 8e181320b11de501046cf75c8c30915cd09a1e39), but it is not yet included in the firmware-realtek Debian package. On the other hand, the newest kernel package already contains the corresponding changes to make use of this firmware, so when I upgraded the kernel, my bluetooth controller stopped working. Excerpt from dmesg: Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000a lmp_ver=06 lmp_subver=8821 Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_fw.bin bluetooth hci0: firmware: failed to load rtl_bt/rtl8821a_fw.bin (-2) bluetooth hci0: Direct firmware load for rtl_bt/rtl8821a_fw.bin failed with error -2 Bluetooth: hci0: Failed to load rtl_bt/rtl8821a_fw.bin Please include this file in the next package release. For good measure and in the interest of people using different hardware, the other firmware blobs from that commit should probably be added, too. Ulrich -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) firmware-realtek depends on no packages. firmware-realtek recommends no packages. Versions of packages firmware-realtek suggests: ii initramfs-tools 0.120 -- no debconf information
Bug#674951: [libapt-pkg4.12] aptitude crashes while updating packages list
I had a similar segfault issue in version 1.0.9.5, though in a different place: #0 0xb7f604e7 in debStatusIndex::Merge(pkgCacheGenerator, OpProgress*) const () from /usr/lib/i386-linux-gnu/libapt-pkg.so.4.12 #1 0xb7ebddb4 in ?? () from /usr/lib/i386-linux-gnu/libapt-pkg.so.4.12 #2 0xb7ec135d in pkgCacheGenerator::MakeStatusCache(pkgSourceList, OpProgress*, MMap**, bool) () from /usr/lib/i386-linux-gnu/libapt-pkg.so.4.12 #3 0xb7ec2036 in pkgMakeStatusCache(pkgSourceList, OpProgress, MMap**, bool) () from /usr/lib/i386-linux-gnu/libapt-pkg.so.4.12 #4 0x801c4ffb in ?? () #5 0x801cf96b in ?? () #6 0x80177cc0 in ?? () #7 0x80174319 in ?? () #8 0x80037870 in main () This happened whenever I tried to run any aptitude or apt-get command (update, search, etc.). Deleting the cache files (/var/cache/apt/*.bin*) did not help, though the next run took longer before crashing, apparently recreating the cache first (successfully, because further commands crashed immediately again). This was 100% reproducible, also after reboot. The other solution suggested in this bug worked, however: apt-get update -o APT::Cache-Start=1 did not crash, and since having run that, everything works normally again (i.e. I don't specify the Cache-Start option and it still works). So the issue is fixed for me, I'm just reporting this experience in case it somehow helps tracking down the bug. Ulrich -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773806: libdb5.3-java: Pre-installation script fails
Package: libdb5.3-java Version: 5.3.28-7~deb8u1 Severity: grave Justification: prevents package from being installed/upgraded Unfortunately, there is another[1] bug in libdb5.3-java.maintscript which means that the package still can't be installed or, if an earlier version is present, can't be upgraded. The error message is: dpkg-maintscript-helper: error: original symlink target is not an absolute path So, the target argument to symlink_to_dir must be an absolute path, i.e. /usr/share/doc/libdb5.3 instead of just libdb5.3. See [2] for an explanation of why this was changed in dpkg 1.17.13. Ulrich [1] http://bugs.debian.org/771877 [2] http://bugs.debian.org/758778 -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (990, 'testing'), (800, 'unstable'), (100, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libdb5.3-java depends on: ii dpkg 1.17.13 ii libdb5.3-java-jni 5.3.28-7~deb8u1 libdb5.3-java recommends no packages. Versions of packages libdb5.3-java suggests: pn libdb5.3-java-gcj none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771877: original symlink target is not an absolute path on libdb5.3-java_5.3.28-7~deb8u1
Tangui, Jan: It is a different (though closely related) bug for which I opened bug #773806 [1]. As soon as that bug is fixed in a new version, it should be possible to upgrade normally. Ulrich [1] http://bugs.debian.org/773806 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766396: picard: New upstream release (1.3)
Package: picard Version: 1.2-2+b1 Severity: wishlist Upstream has released Picard 1.3: http://blog.musicbrainz.org/2014/10/21/picard-1-3-released/ In light of the imminent Jessie freeze, it'd be great if this could be packaged quickly. :-) Ulrich -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681111: imagemagick: Use fftw3-dev, not fftw-dev
found 68 8:6.7.7.10+dfsg-1 thanks After two years, this trivial fix has still not found its way into unstable, meaning that the fft effect doesn't work. Any chance this could be considered for inclusion in the near future? Ulrich -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746600: liblist-allutils-perl: New upstream version
Source: liblist-allutils-perl Version: 0.03-1 Severity: wishlist The current version on CPAN is 0.08. Please update the package. Ulrich -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (800, 'unstable'), (100, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732199: xul-ext-greasemonkey: Migrated to testing prematurely (unsuitable dependencies)
Package: xul-ext-greasemonkey Version: 1.12-1 Severity: important Version 1.12-1 of the Greasemonkey package has successfully migrated to testing even though it is not compatible with the Iceweasel version there. This means that it is currently not possible to use Greasemonkey on testing. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (800, 'unstable'), (100, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-2-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash xul-ext-greasemonkey depends on no packages. Versions of packages xul-ext-greasemonkey recommends: ii iceweasel 17.0.9esr-1~deb7u1 xul-ext-greasemonkey suggests no packages. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#711747: sox: Plugin version mismatch
reassign 711747 libasound2-plugins forcemerge 709855 711747 affects 709855 sox thanks Victor Porton wrote: $ rec ~/t/x.wav ALSA lib pcm_ioplug.c:920:(snd_pcm_ioplug_create) ioplug: Plugin version mismatch rec FAIL formats: can't open input `default': snd_pcm_open error: No such device or address This is not caused by SoX, but by the packages libasound2 and libasound2-plugins being out of sync in testing (missing versioned dependency). I'm merging the bug into #709855, originally filed against alsaplayer. Incidentally, libasound2 1.0.27.1-1 has just migrated into testing earlier today and is compatible with libasound2-plugins 1.0.27-2 which has been there for a while already. Just upgrade to current testing, this should make the problem disappear. Ulrich -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#710062: FLAC 1.3.0 has been released
Fabian Greffrath wrote: Do you know if the library interface/ABI has been changed in this release? API-wise, there are a few added functions in libFLAC and libFLAC++, but no existing functions have been removed or changed. Regarding the ABI, I am not sure; but if the SHLIBS version is to be trusted, there should not be any changes (went from 10:0:2 to 11:0:3 and from 8:0:2 to 9:0:3, respectively, so it is still libflac8 and libflac++6). Ulrich -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#710062: FLAC 1.3.0 has been released
Source: flac Version: 1.2.1-6 Severity: wishlist After several years, a new upstream version of FLAC (1.3.0) has been released by the Xiph.Org Foundation: http://lists.xiph.org/pipermail/flac-dev/2013-May/004191.html https://www.xiph.org/flac/changelog.html#flac_1_3_0 http://downloads.xiph.org/releases/flac/ Please find attached a new debian/watch file. This release includes fixes for bugs 527542 and 705601. It also resolves the whole Debian delta, i.e. you can drop all patches that exist in 1.2.1-6. Ulrich flac-watch Description: Binary data
Bug#581201: [amd64] sox was built in dirty environment (unsatisfied dependencies)
reassign 581201 libsox-fmt-ffmpeg 14.3.1-1 fixed 581201 14.3.1-1+b1 fixed 581201 14.3.1-2 thanks Didier 'OdyX' Raboud wrote on 2010-05-17 [yes, that's three years ago]: sox (14.3.1-1+b1) unstable; urgency=low * Recompile against Debian official ffmpeg library (closes: #581201). Closing… (why hasn't it been closed by the binary package upload ?). It seems the bug was filed against the source package, which doesn't know of a +b1 version. Reassigning to libsox-fmt-ffmpeg and marking as fixed so that the bug finally can get archived. Ulrich -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#706967: sox: [Wheezy] play issues Segmentation fault
unarchive 676167 thanks Bohdan Linda wrote: After an upgrade from Squeeze to Wheezy, `play` command starts issuing segmentation fault. Bellow attached last part of strace. Most probably, this is bug 676167. Could you try one of the workarounds mentioned there (specifying the audio driver explicitly) and see if it solves the problem? E.g., if you are using OSS, please try play file -t oss or AUDIODRIVER=oss play file. Ulrich -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#705601: namespace pollution: FLAC/assert.h conflicts with assert.h
Fabian Greffrath wrote: That should at least fix the symtom. However, I think it is still much too easy to trigger this bug by accident. IMHO, there should not be another header file called assert.h in a name space just one directory level beneath /usr/include. You are probably right. I doubt Erik would accept a patch for 1.3.0 anymore at this point, however; you never know what might break. I'm going to propose a change for the release after that. Ulrich -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#705601: namespace pollution: FLAC/assert.h conflicts with assert.h
This should be fixed in 1.3.0, which is due any day now. :) https://git.xiph.org/?p=flac.git;a=commitdiff;h=b76d4f817c54c6fcfcb82fe72e38660c1b480774 Josh Coalson jcoal...@users.sourceforce.net Sat, 29 Nov 2008 20:55:52 + (20:55 +) Ulrich -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#622969: flac doesn't correctly redraw progress line with UTF-8 filenames
I can't reproduce this with 1.2.1-6, although there weren't any apparently related changes since 1.2.1-3. I created a test file with the same name and also removed the MD5 hash, such that I got the same warning as in the original report. I also varied the terminal width a bit. Still, there were no problems with the progress indicator to be seen. Ulrich -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#537803: flac cannot decode from file without known extensions
fixed 537803 1.2.1-6 thanks Christoph Anton Mitterer wrote: Version: 1.2.1-1.2 It seems that flac cannot decode flac files, that have no known extension (ogg/oga/flac). One gets an error like: filename: *** Got error code 0:FLAC__STREAM_DECODER_ERROR_STATUS_LOST_SYNC I can't reproduce this in 1.2.1-6: $ mv example.flac example $ file example example: FLAC audio bitstream data, 24 bit, stereo, 48 kHz, 5280 samples $ flac -d example (...) example: done $ file example.wav example.wav: RIFF (little-endian) data, WAVE audio, Microsoft PCM, 24 bit, stereo 48000 Hz $ rm example.wav $ mv example example.tst $ flac -d example.tst (...) example.tst: done $ file example.wav example.wav: RIFF (little-endian) data, WAVE audio, Microsoft PCM, 24 bit, stereo 48000 Hz Ulrich -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#527542: flac: replay-gain option ignores -o when reading from stdin
The fix for this is in flac 1.3.0 that is going to be released soon. Ulrich -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#701937: file: debian/copyright out of date
Package: file Version: 5.11-2 Severity: normal The debian/copyright file lists the file magic/Magdir/os9 as being licensed under 4-clause BSD. However, this file has been relicensed to 2-clause BSD in the meantime, the same as the rest of the code. -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (990, 'testing'), (800, 'unstable'), (100, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libmagic1 depends on: ii libc6 2.13-38 ii multiarch-support 2.13-38 ii zlib1g 1:1.2.7.dfsg-13 libmagic1 recommends no packages. Versions of packages libmagic1 suggests: ii file 5.11-2 Versions of packages file depends on: ii libc6 2.13-38 ii zlib1g 1:1.2.7.dfsg-13 -- 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#676167: WARN alsa: can't encode 0-bit Unknown or not applicable
Pascal Giard evily...@gmail.com: I'll probably just push a 14.4.0-5 with it (14.4.0-4 went to experimental). The change is also in 14.4.1 (which will be out in two weeks' time), so a 14.4.0-5 isn't really necessary. Won't hurt either, of course. Ulrich -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693642: FTBFS against libav9
Reinhard Tartler siret...@tauware.de: Your package currently FTBFS against libav9 in experimental. The reason is that the configure script checks the function 'av_open_input_file', which has been replaced a long time ago by 'avformat_open_input': It seems that the file build-tree/sox-14.4.0/src/ffmpeg.c also uses the old API: ... Nevertheless, please check if this has been fixed in a newer upstream release. No, there are no pending changes upstream. We are vaguely aware of the problem though, as there have been a lot of deprecated-declaration warnings for a while now (compiling on current Debian testing, there are warnings about av_close_input_file, avcodec_decode_audio3, avcodec_encode_audio, avcodec_open, av_find_stream_info, av_new_stream, av_open_input_file, av_set_parameters, av_write_header, error_recognition, url_fclose, url_ferror, url_fopen). There is very limited developer interest to fix this and other problems/limitations in the driver, so upstream has considered completely removing it and referring users to the command-line tools, which can then be connected to SoX via pipes. Seems to be the time for a decision ... Ulrich -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#687035: sox: play crashes when playing any WAV file, unless pulseaudio is installed
forcemerge 676167 687035 thanks Torbjörn Andersson eriknos...@telia.com: (All this seems familiar somehow... probably because I commented on bug #664301 earlier this year. ...) Yes, they are related: This problem is caused by the fix to #664301. :) You'll find more information in bug #676167. However, I am a bit surprised that setting AUDIODRIVER=alsa works for you, yet the auto-detect code falls through to OSS: play WARN alsa: can't encode 0-bit Unknown or not applicable play DBUG alsa: selecting format 0: S8 (Signed 8 bit) play INFO oss: OSS driver only supports bytes and words play INFO oss: Forcing to signed linear word Segmentation fault Strange. Ulrich -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#672567: sox: terminates early on certain Ogg Vorbis files
tags 672567 + fixed-upstream thanks Committed a fix to the Ogg Vorbis problem identified above. Ubuntu6226: Could you confirm whether your problem only occurred with files having 3, 5, 6, 7 etc. channels? Ulrich -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#676167: WARN alsa: can't encode 0-bit Unknown or not applicable
tags 676167 + patch
thanks
It'd be interesting to know which driver causes the segfault on
platforms without ALSA support; it might be alsa there too, or one
of the following.
Apparently it is the oss format itself, which passes NULL to fileno().
I've attached a patch to replace the
01_default_audio_driver_fallback.patch file introduced in 14.4.0-3. It
restricts using the new try_device() to pulseaudio, where it seems to
work well and solves the original problem (bug #664301). It's not
ideal of course, as users of OSS still have to manually uninstall
libsox-fmt-alsa or set AUDIODRIVER.
Pascal, would you consider replacing the original patch with this one?
Ulrich
--- src/sox.c.old 2012-08-24 08:42:17.840058210 +0200
+++ src/sox.c 2012-08-24 08:41:59.495637788 +0200
@@ -2542,12 +2542,31 @@
return name? from_env? from_env : name : NULL;
}
+static char const * try_device(char const * name)
+{
+ sox_format_handler_t const * handler = sox_find_format(name, sox_false);
+ if (handler) {
+sox_format_t format, * ft = format;
+lsx_debug(Looking for a default device: trying format `%s', name);
+memset(ft, 0, sizeof(*ft));
+ft-filename = (char *)device_name(name);
+ft-priv = lsx_calloc(1, handler-priv_size);
+if (handler-startwrite(ft) == SOX_SUCCESS) {
+ handler-stopwrite(ft);
+ free(ft-priv);
+ return name;
+}
+free(ft-priv);
+ }
+ return NULL;
+}
+
static char const * set_default_device(file_t * f)
{
/* Default audio driver type in order of preference: */
if (!f-filetype) f-filetype = getenv(AUDIODRIVER);
if (!f-filetype sox_find_format(coreaudio, sox_false)) f-filetype = coreaudio;
- if (!f-filetype sox_find_format(pulseaudio , sox_false)) f-filetype = pulseaudio;
+ if (!f-filetype) f-filetype = try_device(pulseaudio);
if (!f-filetype sox_find_format(alsa, sox_false)) f-filetype = alsa;
if (!f-filetype sox_find_format(waveaudio , sox_false)) f-filetype = waveaudio;
if (!f-filetype sox_find_format(sndio, sox_false)) f-filetype = sndio;
Bug#676143: sox: misleading error message
tags 676143 + fixed-upstream thanks Frank Heckenbach f.heckenb...@fh-soft.de: The following error message is misleading: %sox -r441000 -s foo.raw foo.wav sox FAIL formats: bad input format for file `foo.raw': data encoding was not specified since the encoding (-s) was actually specified. What's missing is the sample size, but it took me to RTFS to find out what it wanted. The patch below changes the wording to make it clearer. Thanks, I've adopted the new wording upstream. Also, it fixes a bad line break in the help output, since floating-point is an actual value for the argument. This had already been changed in the course of removing the deprecated -o/a/etc. options. The relevant part of the help message is now: -e|--encoding ENCODING Set encoding (ENCODING may be one of signed-integer, unsigned-integer, floating-point, mu-law, a-law, ima-adpcm, ms-adpcm, gsm-full-rate) Ulrich -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#672567: sox: play WARN alsa: under-runplay WARN alsa: under-run
retitle 672567 sox: terminates early on certain Ogg Vorbis files found 672567 14.4.0-3 tags 672567 + upstream thanks Ubuntu 6226 ubuntu6...@yahoo.com: It cannot play any OGG or it is very very choppy. It is unfortuneltealy of no use.. any ogg playing is not working I created a test file using this command: sox -c 3 -r 44100 -n tst.ogg synth 0:30 whitenoise gain -15 It is played back correctly by ogg123, so seems to be OK. SoX, however, stops processing it after only 0.015 seconds of audio: $ sox tst.ogg -n stats [...] Num samples 682 Length s 0.015 [...] Trying different test files with a varying number of channels shows that the problem manifests whenever the channel count is not a power of two (i.e., when it is 3, 5, 6, 7, 9, etc.). It thus resembles the problems that we had with several effects that expected buffer sizes to be divisible by the number of channels. As 3*682 = 2046, it seems that processing is aborted after just one buffer. Ulrich -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#676167: WARN alsa: can't encode 0-bit Unknown or not applicable
Bob Proulx b...@proulx.com: Is there any clue as to the root cause of the problem? Yes. If an audio driver is explicitly specified by the user (via the AUDIODRIVER environment variable or the -t option), SoX will use this and there's no problem. Otherwise, SoX will try possible drivers in this (hard-wired) order: coreaudio (MacOS), pulseaudio, alsa, waveaudio, sndio, oss, sunau, ao. Previously (14.4.0-2), it was only checked whether the relevant format driver was available (compiled in, or as a module). But it is very much possible that a format, even though present in SoX, isn't supported by the environment (OS or userland). This led to bug #664301 (insists on using pulseaudio even when not available). 14.4.0-3 tries to remedy this by opening a dummy output for each format driver, and only choosing this driver if the open succeeded. As it seems, though, not all format drivers can handle this dummy open. Depending on which options are available, SoX will get down more or less far on its list and hit different problems (or none). Until someone gets around fixing the dummy-open for all drivers, we should probably restrict the try-and-open method to pulseaudio. Ulrich -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#676167: WARN alsa: can't encode 0-bit Unknown or not applicable
Bob Proulx b...@proulx.com: Although I don't know about coreaudio it probably doesn't hurt. (shrug) No, it isn't supposed to be compiled in at all on platforms other than MacOS. Opening what driver produces the WARN alsa: can't encode 0-bit Unknown or not applicable message? By the above and my case it must be either coreaudio or pulseaudio because alsa works fine and I do not have pulseaudio installed. It is alsa, I think. It gives this warning, but is identified as working nonetheless. It'd be interesting to know which driver causes the segfault on platforms without ALSA support; it might be alsa there too, or one of the following. Ulrich -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#662830: Apparently fixed
fixed 662830 2.91.3+git20120514.b9fec3e1-1 thanks The problem has disappeared in current testing (hamster-applet 2.91.3+git20120514.b9fec3e1-1). Ulrich -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#665698: sox does not work on hw:2,0
It simply does not work if one try to : play -t alsa with hw:2,0 and some files files.mp3 It cannot play on another sound device else than the default one : hw:0,0 (playing not sox converting). What soundcards do you use (cat /proc/asound/cards shows a list)? Is card 2 by any chance a USB device? If so, please try plughw:2,0 also. If it doesn't work with plughw either, please provide the output of the play command with option -V5 added. Ulrich -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#665346: Unaffected versions
I've encountered the same bug, also in 2.7.3~rc2-1. I went through versions 2.7.2-8, 2.7.2-13, and 2.7.3~rc1-1 previously, and none of them exhibited this problem. Ulrich -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#664301: sox: insists on using pulseaudio even when not available
retitle 664301 sox: insists on using pulseaudio even when not available tags 664301 + upstream thanks So the problem appears to be that SoX only checks whether its PulseAudio format handler is present and, if so, decides to use it, even if PulseAudio isn't running or not installed at all. This behaviour was concealed in previous versions because the PulseAudio format handler had a lower priority then. Until there is an upstream solution, you have at least three options: 1. actually use pulseaudio (i.e. install and properly configure it) 2. override the default by setting AUDIODRIVER=alsa 3. remove the libsox-fmt-pulse package Regarding the third option, you have to be careful as you probably don't want to remove the other libsox-fmt-* packages, especially libsox-fmt-alsa. You can try aptitude remove libsox-fmt-pulse but if it complains about dependencies, you should instead use aptitude install libsox-fmt-base+ libsox-fmt-alsa+ libsox-fmt-ao+ \ libsox-fmt-oss+ libsox-fmt-ffmpeg+ libsox-fmt-mp3+ \ libsox-fmt-all- libsox-fmt-pulse- libsox-dev- (If you only use ALSA, you can turn the + after libsox-fmt-ao and libsox-fmt-oss into -.) Ulrich -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#664301: sox: play FAIL formats: can't open output file `default': can not open audio device: Connection refused
Hi, a) what is your default audio device? Pulseaudio, or do you use JACK via ALSA? b) You have a version mismatch between sox and its format handlers: Package: sox Version: 14.4.0-2 ii libsox-fmt-alsa 14.3.2-3 ii libsox-fmt-ao 14.3.2-3 ii libsox-fmt-base 14.3.2-3 ii libsox-fmt-oss14.3.2-3 ii libsox-fmt-pulse 14.3.2-3 ii libsox2 14.4.0-2 Could you try to update all libsox-fmt-* packages to 14.4.0-2? Installing libsox-fmt-all from unstable should do it, too. Ulrich -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#662830: hamster-applet: Adding previous activities only works once per run
Package: hamster-applet Version: 2.91.3+git20120211.9ebb889-2 Severity: normal I'm using hamster in standalone mode, i.e. I run it as hamster-time-tracker from a terminal. Adding a previous activity only works once. When trying to use this function a second time, only a small window without any control elements appears. To work around it, I have to quit hamster and restart it; I can then use the function again exactly once. This is a regression, it used to work OK in version 2.91.3+git20110714.9aefd7-2. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (800, 'unstable'), (100, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages hamster-applet depends on: ii gconf23.2.3-3 ii python2.7.2-10 ii python-cairo 1.8.8-1+b2 ii python-dbus 0.84.0-3 ii python-gconf 2.28.1+dfsg-1 ii python-gnome2 2.28.1+dfsg-1 ii python-gobject-2 2.28.6-9 ii python-gtk2 2.24.0-3 ii python-wnck 2.32.0+dfsg-1 ii python-xdg0.19-3 ii python2.6 2.6.7-4 ii python2.7 2.7.2-13 Versions of packages hamster-applet recommends: ii gnome-icon-theme 3.2.1.2-1 ii python-notify 0.1.1-3 Versions of packages hamster-applet suggests: pn python-evolution none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#640482: OK in experimental
fixed 640482 8:6.7.4.0-1 thanks I tried version 8:6.7.4.0-1 from experimental, and the bug is not present there. Ulrich -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#586292: xserver-xorg-core: deadlocks for no apparent reason
Jonathan Nieder jrnie...@gmail.com: Sorry for the slow reply. What kernel do you use nowadays? Does this still happen? Thank you for looking into this. The problem persisted for several months, I think, but then disappeared. I don't think I have experienced such a deadlock in the last half-year or so, but unfortunately can't remember more precisely when the change happened. So probably this bug report can be closed. For the record, I'm still using a more-or-less current testing all the time, so at the moment the kernel is 3.1.0-1-amd64. Ulrich -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#640482: Similar problem with display -update
I'd like to add to this bug report that a very similar (the same?) problem occurs when using the -update option to display. The image will not be updated every time the file changes, and there are the same messages about scenes. On 2011-09-20, site admin magick wrote in the forum thread that Moshe referred to above, i.e. http://www.imagemagick.org/discourse-server/viewtopic.php?t=19141 : We can reproduce the problem you reported and will have a patch within a day or two. Thanks. I couldn't find a related change in the subversion repo, I'm not sure I looked in the right places however. So I hope there will soon be an updated package, as this bug is really very annoying. Ulrich -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#627321: New upstream version
severity 627321 grave tags 627321 + fixed-upstream thanks The older upstream fix has now been released as a new upstream version (2.25.0), could you please package it? Changing severity to grave since a bidding program that can't bid is unusable or mostly so, in my opinion. Ulrich -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#619212: cups: pdftoraster-poppler regression: segfaults in 1.4.6-1 but not 1.4.4-7
Package: cups Version: 1.4.6-1 Severity: important With cups 1.4.6-1, I can't print some postscripts files anymore that used to work before. (All the affected files are made with TeX and dvips, which may or may not be a coincidence; not all dvips postscript files are affected.) The error_log shows that pdftoraster-poppler crashes with a segfault. See the attached log file excerpt. Printing these files works again after downgrading to 1.4.4-7 (current stable version). For the downgrade, I only did dpkg -i cups_1.4.4-7_amd64.deb - no other packages where changed. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (800, 'unstable'), (100, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.37-1-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages cups depends on: ii adduser 3.112+nmu2 add and remove users and groups ii bc 1.06.95-2The GNU bc arbitrary precision cal ii cups-client 1.4.6-1 Common UNIX Printing System(tm) - ii cups-common 1.4.6-1 Common UNIX Printing System(tm) - ii cups-ppdc 1.4.6-1 Common UNIX Printing System(tm) - ii debconf [debconf-2.0] 1.5.38 Debian configuration management sy ii ghostscript 9.01~dfsg-2 interpreter for the PostScript lan ii libavahi-client30.6.28-4 Avahi client library ii libavahi-common30.6.28-4 Avahi common library ii libc6 2.11.2-11Embedded GNU C Library: Shared lib ii libcups21.4.6-1 Common UNIX Printing System(tm) - ii libcupscgi1 1.4.6-1 Common UNIX Printing System(tm) - ii libcupsdriver1 1.4.6-1 Common UNIX Printing System(tm) - ii libcupsimage2 1.4.6-1 Common UNIX Printing System(tm) - ii libcupsmime11.4.6-1 Common UNIX Printing System(tm) - ii libcupsppdc11.4.6-1 Common UNIX Printing System(tm) - ii libdbus-1-3 1.4.6-1 simple interprocess messaging syst ii libgcc1 1:4.5.2-4GCC support library ii libgnutls26 2.10.5-1 the GNU TLS library - runtime libr ii libgssapi-krb5-21.8.3+dfsg-4 MIT Kerberos runtime libraries - k ii libijs-0.35 0.35-7 IJS raster image transport protoco ii libkrb5-3 1.8.3+dfsg-4 MIT Kerberos runtime libraries ii libldap-2.4-2 2.4.23-7 OpenLDAP libraries ii libpam0g1.1.2-2 Pluggable Authentication Modules l ii libpaper1 1.1.24 library for handling paper charact ii libpoppler5 0.12.4-1.2 PDF rendering library ii libslp1 1.2.1-7.8OpenSLP libraries ii libstdc++6 4.5.2-4 The GNU Standard C++ Library v3 ii libusb-0.1-42:0.1.12-17 userspace USB programming library ii lsb-base3.2-27 Linux Standard Base 3.2 init scrip ii poppler-utils 0.12.4-1.2 PDF utilitites (based on libpopple ii procps 1:3.2.8-10 /proc file system utilities ii ssl-cert1.0.28 simple debconf wrapper for OpenSSL ii ttf-freefont20100919-1 Freefont Serif, Sans and Mono True ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime Versions of packages cups recommends: ii cups-driver-gutenprint 5.2.6-1 printer drivers for CUPS ii foomatic-filters 4.0.7-1 OpenPrinting printer support - fil ii ghostscript-cups 9.01~dfsg-2 interpreter for the PostScript lan Versions of packages cups suggests: ii cups-bsd 1.4.6-1Common UNIX Printing System(tm) - pn cups-pdf none (no description available) ii foomatic-db 20110209-1 OpenPrinting printer support - dat ii hplip 3.11.1-2 HP Linux Printing and Imaging Syst pn smbclient none (no description available) ii udev 166-1 /dev/ and hotplug management daemo pn xpdf-korean | xpdf-japanese | none (no description available) -- debconf information: cupsys/raw-print: true cupsys/backend: ipp, lpd, parallel, scsi, serial, socket, usb, snmp, dnssd E [22/Mar/2011:00:37:06 +0100] [Job 92] SpliX Cannot get input slot information. E [22/Mar/2011:00:37:06 +0100] PID 4431 (/usr/lib/cups/filter/pdftoraster-poppler) crashed on signal 11! D [22/Mar/2011:00:37:18 +0100] [Job 92] The following messages were recorded from 00:36:30 to 00:37:18 D [22/Mar/2011:00:37:18 +0100] [Job 92] Adding start banner page none. D [22/Mar/2011:00:37:18 +0100] [Job 92] Queued on
Bug#576404: evince: lots of Error: Illegal entry in bfrange block in ToUnicode CMap when opening pdfs
It seems this is a bug in libpoppler that has already been fixed upstream: https://bugs.freedesktop.org/show_bug.cgi?id=27728 However, it is still present in current testing (evince 2.30.3-1). Ulrich -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#606325: cron: Off-by-one in manpage example
Package: cron Version: 3.0pl1-115 Severity: minor In the EXAMPLE CRON FILE section of crontab(5), there is this example: # Run on every second Saturday of the month 0 4 8-15 * *test $(date +\%u) -eq 6 echo 2nd Saturday The range of days (8-15) in this example is one day too wide. In months starting with a Saturday, the echo command will be executed both on the 8th (the second Saturday, as desired) and on the 15th (the third Saturday). The range should be corrected to 8-14. Also, when viewing crontab(5) with man 5 crontab the line above is actually shown like this: 0 4 8-15 * *test $(date +u) -eq 6 echo 2nd Saturday I.e. the percent sign and the backslash escaping it are missing. I suspect the backslash has not been properly escaped itself in the manpage source. -- Package-specific info: --- EDITOR: not set --- usr/bin/editor: /bin/nano --- /usr/bin/crontab: -rwxr-sr-x 1 root crontab 35040 Oct 16 13:37 /usr/bin/crontab --- /var/spool/cron drwxr-xr-x 5 root root 4096 Aug 25 2009 /var/spool/cron --- /var/spool/cron/crontabs drwx-wx--T 2 root crontab 4096 Sep 28 2008 /var/spool/cron/crontabs -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (800, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages cron depends on: ii adduser 3.112+nmu2 add and remove users and groups ii debianutils 3.4Miscellaneous utilities specific t ii dpkg 1.15.8.5 Debian package management system ii libc6 2.11.2-7 Embedded GNU C Library: Shared lib ii libpam-runtime1.1.1-6.1 Runtime support for the PAM librar ii libpam0g 1.1.1-6.1 Pluggable Authentication Modules l ii libselinux1 2.0.96-1 SELinux runtime shared libraries ii lsb-base 3.2-23.1 Linux Standard Base 3.2 init scrip Versions of packages cron recommends: ii exim4 4.72-2 metapackage to ease Exim MTA (v4) ii exim4-daemon-light [mail-tran 4.72-2 lightweight Exim MTA (v4) daemon ii lockfile-progs0.1.15 Programs for locking and unlocking Versions of packages cron suggests: ii anacron 2.3-14 cron-like program that doesn't go pn checksecurity none (no description available) ii logrotate 3.7.8-6Log rotation utility Versions of packages cron is related to: pn libnss-ldap none (no description available) pn libnss-ldapd none (no description available) pn libpam-ldap none (no description available) pn libpam-mount none (no description available) pn nis none (no description available) pn nscd none (no description available) -- 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#582898: network-manager-gnome: impossible to edit Wi-Fi connections
Package: network-manager-gnome Version: 0.8-1 Severity: normal When editing a Wi-Fi connection (applet context menu - edit connections - Wi-Fi - edit; or similar wording, as I am using the German localization), the Apply button is always greyed out, even after doing changes. It is therefore not possible to commit these changes (e.g. to change the name of the connection or to deactivate automatic connecting). -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.32-3-686 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages network-manager-gnome depends on: ii dbus-x111.2.24-1 simple interprocess messaging syst ii gconf2 2.28.1-3 GNOME configuration database syste ii gnome-icon-theme2.30.2.1-1 GNOME Desktop icon theme ii libatk1.0-0 1.30.0-1 The ATK accessibility toolkit ii libc6 2.10.2-6 Embedded GNU C Library: Shared lib ii libcairo2 1.8.10-4 The Cairo 2D vector graphics libra ii libdbus-1-3 1.2.24-1 simple interprocess messaging syst ii libdbus-glib-1-20.86-1 simple interprocess messaging syst ii libfontconfig1 2.8.0-2.1generic font configuration library ii libfreetype62.3.11-1 FreeType 2 font engine, shared lib ii libgconf2-4 2.28.1-3 GNOME configuration database syste ii libglade2-0 1:2.6.4-1library to load .glade files at ru ii libglib2.0-02.24.1-1 The GLib library of C routines ii libgnome-bluetooth7 2.30.0-1 GNOME Bluetooth tools - support li ii libgnome-keyring0 2.30.1-1 GNOME keyring services library ii libgtk2.0-0 2.20.1-1 The GTK+ graphical user interface ii libnm-glib-vpn1 0.8-1network management framework (GLib ii libnm-glib2 0.8-1network management framework (GLib ii libnm-util1 0.8-1network management framework (shar ii libnotify1 [libnotify1- 0.4.5-1 sends desktop notifications to a n ii libpango1.0-0 1.28.0-1 Layout and rendering of internatio ii libxml2 2.7.7.dfsg-2 GNOME XML library ii network-manager 0.8-1network management framework daemo ii policykit-1-gnome 0.96-2 GNOME authentication agent for Pol ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime Versions of packages network-manager-gnome recommends: ii gnome-bluetooth 2.30.0-1 GNOME Bluetooth tools ii libpam-gnome-keyring [libpam- 2.30.1-2 PAM module to unlock the GNOME key ii mobile-broadband-provider-inf 20100507-1 database of mobile broadband servi ii notification-daemon 0.4.0-2a daemon that displays passive pop Versions of packages network-manager-gnome suggests: pn network-manager-openvpn-gnome none (no description available) pn network-manager-pptp-gnomenone (no description available) pn network-manager-vpnc-gnomenone (no description available) -- 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#537184: gnuplot: Axis labels missing on terminal png after set size
I can confirm this problem for the version currently in stable; for me, also a title set with set title is not shown. It does work correctly in 4.4 from testing (gnuplot-nox 4.4.0-1), both with png and pngcairo (after adapting to the new size semantics): set terminal png size 1280,960 set output 'ok_nocairo.png' plot sin(x) set terminal pngcairo size 1280,960 set output 'ok_cairo.png' plot sin(x) Ulrich Klauer -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#573297: openoffice.org-core: should report an error when a required component is not installed
Package: openoffice.org-core Version: 1:3.1.1-16 Severity: normal I tried to open a Word document. After calling ooffice x.doc the OOo splash appeared and disappeared again, then nothing happened. ps showed a sleeping OOo instance. I tried again calling only ooffice and the welcome screen appeared, allowing me to choose a document to open. Again, nothing happened; the welcome screen persisted. While preparing a bug report, I found out that the package openoffice.org-writer was not installed. After installation, everything worked as expected. I think the OOo main binary should show *some* kind of error message or other information indicating that it won't proceed, due to a required component not being installed. -- Package-specific info: all deployed shared packages: Identifier: org.openoffice.legacy.mailmerge.py URL: vnd.sun.star.expand:$UNO_SHARED_PACKAGES_CACHE/uno_packages/x4aoRG_/mailmerge.py is registered: yes Media-Type: application/vnd.sun.star.uno-component;type=Python Description: all deployed user packages: none -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.32-trunk-486 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages openoffice.org-core depends on: ii fontconfig 2.8.0-2 generic font configuration library ii libc6 2.10.2-6 Embedded GNU C Library: Shared lib ii libcairo2 1.8.8-2 The Cairo 2D vector graphics libra ii libcurl3-gnutls7.19.7-1 Multi-protocol file transfer libra ii libdb4.8 4.8.26-1 Berkeley v4.8 Database Libraries [ ii libexpat1 2.0.1-7 XML parsing C library - runtime li ii libfreetype6 2.3.11-1 FreeType 2 font engine, shared lib ii libgcc11:4.4.2-9 GCC support library ii libglib2.0-0 2.22.4-1 The GLib library of C routines ii libgstreamer-plugins-b 0.10.26-1 GStreamer libraries from the base ii libgstreamer0.10-0 0.10.26-1 Core GStreamer libraries and eleme ii libgtk2.0-02.18.6-1 The GTK+ graphical user interface ii libhunspell-1.2-0 1.2.8-6 spell checker and morphological an ii libhyphen0 2.5-1 ALTLinux hyphenation library - sha ii libice62:1.0.6-1 X11 Inter-Client Exchange library ii libicu42 4.2.1-3 International Components for Unico ii libjpeg62 6b-16.1 The Independent JPEG Group's JPEG ii libldap-2.4-2 2.4.17-2.1OpenLDAP libraries ii libneon27-gnutls 0.29.3-2 An HTTP and WebDAV client library ii libnspr4-0d4.8.3-1 NetScape Portable Runtime Library ii libnss3-1d 3.12.5-2 Network Security Service libraries ii librdf01.0.10-1 Redland Resource Description Frame ii libsm6 2:1.1.1-1 X11 Session Management library ii libstdc++6 4.4.2-9 The GNU Standard C++ Library v3 ii libstlport4.6ldbl 4.6.2-7 STLport C++ class library ii libx11-6 2:1.3.3-1 X11 client-side library ii libxaw72:1.0.7-1 X11 Athena Widget library ii libxext6 2:1.1.1-2 X11 miscellaneous extension librar ii libxinerama1 2:1.1-2 X11 Xinerama extension library ii libxml22.7.6.dfsg-2+b1 GNOME XML library ii libxrandr2 2:1.3.0-3 X11 RandR extension library ii libxrender11:0.9.5-1 X Rendering Extension client libra ii libxslt1.1 1.1.26-2 XSLT processing library - runtime ii libxt6 1:1.0.7-1 X11 toolkit intrinsics library ii libxtst6 2:1.1.0-2 X11 Testing -- Resource extension ii openoffice.org-common 1:3.1.1-16full-featured office productivity ii ttf-opensymbol 1:3.1.1-16OpenSymbol TrueType font ii ure1.5.1+OOo3.1.1-16 OpenOffice.org UNO runtime environ ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime openoffice.org-core recommends no packages. openoffice.org-core suggests no packages. Versions of packages openoffice.org-common depends on: ii debconf [debconf-2.0] 1.5.28Debian configuration management sy ii openoffice.org-style-a 1:3.1.1-16full-featured office productivity ii openoffice.org-style-g 1:3.1.1-16full-featured office productivity ii openoffice.org-style-o 1:3.1.1-16full-featured office productivity ii openoffice.org-style-t 1:3.1.1-16full-featured office productivity ii ure1.5.1+OOo3.1.1-16 OpenOffice.org UNO runtime environ
