Bug#597575: Update on Saving of downloaded file or webpage, which very long filename do not work
tag 597575 -moreinfo thanks On mar., 2011-05-17 at 03:27 +0200, Witold Baryluk wrote: On 05-16 16:46, Yves-Alexis Perez wrote: Hey, is this still reproducible with 0.3.6-1 currently in unstable? Yes, midori still improperly indicate that file was properly saved. Howver it isn't saved. In console I see: (midori:20329): GLib-GIO-CRITICAL **: g_output_stream_write_all: assertion `G_IS_OUTPUT_STREAM (stream)' failed Ok, will ping upstream about that. Thanks, -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#596739: Still reproducible. Was: Does not restore tabs after crash
On mar., 2011-05-17 at 03:35 +0200, Witold Baryluk wrote: Still I think that post-crash startup dialog should be changed. Button Do not restore session / tabs, should be changed to checkbox. because after clicking it, there is no way back (it deactivates), and all tabs will be lost (hovewer one can Close this dialog using X button or Alt-F4, and restart midori, but this is not perfect). Hmh, but this is the whole point of that popup. If loading the tabs makes midori crash, you don't want them to load at all. Resetting the session means exactly that, you forget about everything open. What would you expect exactly? Regards, -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#627029: libredcloth-ruby1.8: require RedCloth not working
Package: libredcloth-ruby1.8 Version: 4.2.2-1.1 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, the command require RedCloth does not work. Only require redcloth. I exepcted the camelcase modulename after reading the online documentation of RedCloth. And it also causes problems for the tracks GTD software which uses RedCloth as module name. Regards, Bastian - -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38grog6 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libredcloth-ruby1.8 depends on: ii libc62.13-4 Embedded GNU C Library: Shared lib ii libruby1.8 1.8.7.334-5 Libraries necessary to run Ruby 1. libredcloth-ruby1.8 recommends no packages. libredcloth-ruby1.8 suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk3SA/oACgkQeBwlBDLsbz65zQCePfD6+tGteZfGozdZs7UOQi4x ASQAnjOy7C4DvSP1l62WZAR1l8pFlu3X =I8aV -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#626895: pu: package samba/2:3..6~dfsg-3squeeze4
Version: 2:3.5.7~dfsg-1 Quoting Adam D. Barratt (a...@adam-barratt.org.uk): Hi, On Mon, 2011-05-16 at 09:51 +0200, Christian Perrier wrote: Here's another samba bug for which I would like to cherrypick the upstream fix. In #605728, it is reported fail to copy files to an SMB share using signed SMB. This breaks Gnome desktop copying which is, IMHO, important enough to deserve being fixed in squeeze. Has this already been included in a version of samba uploaded to unstable? I assumed that it would have been, given the date of the upstream fix, but #605728 still appears to be marked as unfixed. Yes, it has. This fix is indeed in upstream 3.5.7. I was doing bug triaging yesterday when I re-discovered this bug. Indeed, after sending the p-u request, I wanted to close the bug with version tracking but forgot to do so anbd moved to something else. Thanks for reminding me..:-). Doing so right now... signature.asc Description: Digital signature
Bug#612504: [Pkg-xfce-devel] Bug#612504: Bug#612504: xfce4-session: Attempted suspend
On lun., 2011-05-16 at 23:34 -0400, Frank Zambrini wrote: With xfce 4.6 I switched to gdm from slim and everything was working fine. However after upgrading to xfce 4.8, the session manager broke again for both gdm and slim. slim is broken anyway. If Prompt on Logout is unchecked from the Session and Startup menu, clicking the logout button on the panel causes the session to restart back to the slim/gdm login screen. This is standard behavior. If Prompt on Logout is checked, then the logout window will be displayed (after waiting about 30 seconds) That looks like some app in the session doesn't respond correctly. Try to quit everything (including stuff in the systray) and provide the list of running processes for your users before hitting the logout button. but only has options for shutdown, restart, and Log Out. Suspend is missing from the menu, but I can still put the computer in standby with sudo pm-suspend. Looks like a Consolekit issue, read README.Debian in xfce4 and xfce4-session. Is upower installed, by the way? I did a backtrace of xfce4-session (using slim, w/out Prompt on Logout), but I don't know if it will do much good. For some reason, when gdb is attached to xfce4-session (from a VT), clicking the logout button will not cause the session to restart. Instead, I get a Failed to connect to session manager error message. Then when I quit gdb, the session restarts and returns to the login screen. There's nothing to debug with gdb here. If there is anything else I can do let me know. Maybe I should file a bug against consolekit? Not really. Slim has an issue but gdm should work fine. Regards, -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#626791: Bug in libdbd-mysql-perl fixed in revision 74615
tag 626791 + pending thanks Some bugs are closed in revision 74615 by Ansgar Burchardt (ansgar) Commit message: debian/control: Fix typo in package description. (Closes: #626791) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#627030: [debcheckout] Buggy “this is probably a bug” when specifying a target directory
Package: devscripts Version: 2.10.73 Severity: normal Hi, this is slightly annoying: | $ debcheckout mesa mesa.git | declared git repository at git://git.debian.org/git/pkg-xorg/lib/mesa | git clone git://git.debian.org/git/pkg-xorg/lib/mesa mesa.git ... | Cloning into mesa.git... | remote: Counting objects: 378199, done. | remote: Compressing objects: 100% (62487/62487), done. | remote: Total 378199 (delta 314631), reused 376526 (delta 313102) | Receiving objects: 100% (378199/378199), 102.80 MiB | 2.10 MiB/s, done. | Resolving deltas: 100% (314631/314631), done. | debcheckout did not create the mesa directory - this is probably a bug So, yeah, I specified a target directory, there's indeed a bug: please check for that directory's being created, instead of the default. :) Mraw, KiBi. -- Package-specific info: Killed, probably irrelevant. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#627031: [INTL:es] Spanish debconf template translation for apparmor
Package: apparmor Version: 2.6.1-3 Severity: wishlist Tags: l10n patch -- Saludos Fran # apparmor po-debconf translation to Spanish # Copyright (C) 2011 Software in the Public Interest # This file is distributed under the same license as the apparmor package. # # Changes: # - Initial translation # Francisco Javier Cuadrado fcocuadr...@gmail.com, 2011 # # Traductores, si no conocen el formato PO, merece la pena leer la # documentación de gettext, especialmente las secciones dedicadas a este # formato, por ejemplo ejecutando: # info -n '(gettext)PO Files' # info -n '(gettext)Header Entry' # # Equipo de traducción al español, por favor, lean antes de traducir # los siguientes documentos: # # - El proyecto de traducción de Debian al español #http://www.debian.org/intl/spanish/ #especialmente las notas de traducción en #http://www.debian.org/intl/spanish/notas # # - La guía de traducción de po's de debconf: #/usr/share/doc/po-debconf/README-trans #o http://www.debian.org/intl/l10n/po-debconf/README-trans # msgid msgstr Project-Id-Version: apparmor 2.6.1-3\n Report-Msgid-Bugs-To: ubuntu-devel-disc...@lists.ubuntu.com\n POT-Creation-Date: 2010-01-05 17:45-0600\n PO-Revision-Date: 2011-05-06 13:45+0100\n Last-Translator: Francisco Javier Cuadrado fcocuadr...@gmail.com\n Language-Team: Debian l10n Spanish debian-l10n-span...@lists.debian.org\n MIME-Version: 1.0\n Content-Type: text/plain; charset=UTF-8\n Content-Transfer-Encoding: 8bit\n #. Type: string #. Description #: ../templates:1001 msgid Additional home directory locations: msgstr Rutas adicionales de los directorios personales: #. Type: string #. Description #: ../templates:1001 msgid Please enter a space separated list of any additional locations for user home directories. These locations are in addition to those specified in /etc/apparmor.d/tunables/home and must end with a '/'. msgstr Introduzca una lista separada por espacios con las rutas adicionales para los directorios personales. Estas rutas se suman a las indicadas en «/etc/apparmor.d/tunables/home» y deben terminar con una barra «/». #. Type: string #. Description #: ../templates:1001 msgid Example: if user's directories are stored in /srv/nfs/home and /mnt/homes, you should enter \/srv/nfs/home/ /mnt/homes/\. msgstr Por ejemplo: si los directorios del usuario están ubicados en «/srv/nfs/home» y «/mnt/homes», debería introducir «/srv/nfs/home/ /mnt/homes/».
Bug#627032: [INTL:es] Spanish debconf template translation for cacti
Package: cacti Version: 0.8.7g-3 Severity: wishlist Tags: l10n patch -- Saludos Fran # cacti po-debconf translation to Spanish # Copyright (C) 2005, 2011 Software in the Public Interest # This file is distributed under the same license as the cacti package. # # Changes: # - Initial translation # César Gómez MartÃn cesar.go...@gmail.com # # - Updates # Francisco Javier Cuadrado fcocuadr...@gmail.com, 2011 # # Traductores, si no conocen el formato PO, merece la pena leer la # documentación de gettext, especialmente las secciones dedicadas a este # formato, por ejemplo ejecutando: # info -n '(gettext)PO Files' # info -n '(gettext)Header Entry' # # Equipo de traducción al español, por favor, lean antes de traducir # los siguientes documentos: # # - El proyecto de traducción de Debian al español #http://www.debian.org/intl/spanish/ #especialmente las notas de traducción en #http://www.debian.org/intl/spanish/notas # # - La guÃa de traducción de po's de debconf: #/usr/share/doc/po-debconf/README-trans #o http://www.debian.org/intl/l10n/po-debconf/README-trans # msgid msgstr Project-Id-Version: cacti 0.8.7g-3\n Report-Msgid-Bugs-To: ca...@packages.debian.org\n POT-Creation-Date: 2011-02-16 06:33+\n PO-Revision-Date: 2011-05-04 12:50+0100\n Last-Translator: Francisco Javier Cuadrado fcocuadr...@gmail.com\n Language-Team: Debian l10n Spanish debian-l10n-span...@lists.debian.org\n MIME-Version: 1.0\n Content-Type: text/plain; charset=UTF-8\n Content-Transfer-Encoding: 8bit\n Language: es\n #. Type: select #. Choices #: ../cacti.templates:1001 msgid Apache2 msgstr Apache2 #. Type: select #. Choices #: ../cacti.templates:1001 msgid None msgstr Ninguno #. Type: select #. Description #: ../cacti.templates:1002 msgid Webserver type msgstr Tipo de servidor web #. Type: select #. Description #: ../cacti.templates:1002 msgid Please select the webserver type for which cacti should be automatically configured. msgstr Escoja el tipo de servidor web para el que cacti se deberÃa configurar automáticamente. #. Type: select #. Description #: ../cacti.templates:1002 msgid Select \None\ if you would like to configure your webserver by hand. msgstr Escoja «Ninguno» si quiere configurar su servidor web manualmente. #~ msgid Which kind of web server should be used by cacti? #~ msgstr ¿Qué tipo de servidor web quiere usar con cacti? #~ msgid Apache, Apache-SSL, Apache2, All, None #~ msgstr Apache, Apache-SSL, Apache2, Todos, Ninguno #~ msgid MySQL installs and upgrades must be performed manually! #~ msgstr #~ ¡Las instalaciones y actualizaciones de MySQL se deben hacer de forma #~ manual! #~ msgid #~ For the time being, support for automatic upgrading of the cacti mysql #~ database has been disabled. Please see the rationale and what you will #~ need to do for either installing or upgrading cacti in /usr/share/doc/ #~ cacti/README.Debian.gz. #~ msgstr #~ Por ahora el soporte para la actualización automática de la base de datos #~ MySQL de Cacti se ha deshabilitado. Por favor, consulte en /usr/share/doc/ #~ cacti/README.Debian.gz los motivos y lo que necesita para instalar o #~ actualizar Cacti. #~ msgid #~ Note that you will still be prompted for the relevant information, which #~ will be used to generate the appropriate configuration files. #~ msgstr #~ Tenga en cuenta que todavÃa se le preguntará sobre la información #~ relevante que se usará para generar los ficheros de configuración #~ apropiados. #~ msgid Database structure changes in cacti configuration #~ msgstr #~ Cambios de la estructura de la base de datos en la configuración de cacti. #~ msgid #~ You are upgrading from a pre 0.8.x version. Unfortunately, your old #~ database will not work with the latest version of cacti. Please see /usr/ #~ share/doc/cacti/README.Debian.gz to see what your options are. #~ msgstr #~ Está actualizando desde una versión previa a 0.8.x. Desafortunadamente su #~ vieja base de datos no funcionará con la última versión de Cacti. Por #~ favor, lea /usr/share/doc/cacti/README.Debian.gz para ver las distintas #~ opciones de las que dispone. #~ msgid MySQL server host name #~ msgstr Nombre de máquina del servidor MySQL #~ msgid Please enter the name of the machine hosting the cacti database. #~ msgstr #~ Por favor, introduzca el nombre de la máquina en la que está la base de #~ datos de Cacti. #~ msgid Database name for cacti #~ msgstr Nombre de la base de datos para cacti #~ msgid #~ Please enter the cacti database name. Cacti will store and fetch data #~ there. #~ msgstr #~ Por favor, introduzca el nombre de la base de datos de Cacti. Cacti #~ almacenará y obtendrá datos de ella. #~ msgid MySQL administrator username #~ msgstr Nombre de usuario del administrador de MySQL #~ msgid #~ Please enter the MySQL administrator name (needed for cacti database #~ creation). #~ msgstr #~ Por favor, introduzca el nombre
Bug#622620: [Pascal de Bruijn] Re: O: argyll -- Color Management System, calibrator and profiler
Forwarding an email I assume should have been directed at the bug. ---BeginMessage--- On Wed, Apr 13, 2011 at 2:46 PM, Roland Mas lola...@debian.org wrote: Package: wnpp Severity: normal I think it's time for me to stop pretending I have enough time/energy/interest to properly maintain Argyll. I'm therefore regretfully orphaning the package. Thanks for your excellent work which I've been able to enjoy. Prospective adopters: most of the difficulty I've had in maintaining this package comes from my switch of build system from Jam to Autoconf/Automake/Libtool. If you can live with Jam, then you'll probably have an easier job. I bumped Greame about modifying the Jam files slightly making packaging a bit more easy. I have a first version of Jam based packaging available here (Argyll 1.3.3 / Ubuntu Natty): https://launchpad.net/~pmjdebruijn/+archive/argyll-release I'm quite prepared to offer sponsorship and/or guidance to anyone willing to adopt the package and needing one or the other. I'm not willing to take responsibility to maintain that package upstream. Sorry. Regards, Pascal de Bruijn ---End Message--- -- Roland Mas $ chown -R us:us your_base*
Bug#626955: libgl1-mesa-dri: Version 7.10.2 does not work with gnome-shell, 7.10-4 works ok
Hi, Arief M Utama ar...@life2play.net (17/05/2011): I'll do that, but honestly, mesa is still a new thing for me, could you please let me know how to build r600c instead of r600g ? Is it --disable-gallium ? Apparently, appending the following flags to the default ones mentioned in the ./configure call on the howto does the trick: --with-dri-drivers=r600 --disable-gallium-r600 --disable-gallium-r300 (Passing --disable-gallium would mean turning off some other options since OpenVG can't be built without gallium; disabling r300g is also needed if you haven't installed llvm development packages, hence the last flag.) If the issue persists, please file the bug upstream and tell us about the bug number/URL so that we can track it, a good start is likely to be the Mesa product on: http://bugs.freedesktop.org/ Mraw, KiBi. signature.asc Description: Digital signature
Bug#627034: [CRASH] Uncaught exception AttributeError in Backend/PythonApt.py:801
Package: update-manager-core
Version: 0.200.5-1
Severity: normal
File: /usr/share/pyshared/UpdateManager/Backend/PythonApt.py
*** /tmp/update-manager-bugTfnuUB
The information below has been automatically generated.
Please do not remove this from your bug report.
- Exception Type: type 'exceptions.AttributeError'
- Exception Value: AttributeError('NoneType' object has no attribute
'get_package_list',)
- Exception Origin: BugHandler.Thread(PythonAptCommit, started -1306068112)
- Exception Traceback:
File /usr/lib/pymodules/python2.6/UpdateManager/BugHandler.py, line 89, in
run
threading.Thread.run(self, *args, **kwargs)
File /usr/lib/python2.6/threading.py, line 484, in run
self.__target(*self.__args, **self.__kwargs)
File /usr/lib/pymodules/python2.6/UpdateManager/Backend/PythonApt.py, line
801, in thread_helper
for pkg_info in self._available_updates.get_package_list():
-- System Information:
Debian Release: 6.0.1
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-686 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages update-manager-core depends on:
ii lsb-release 3.2-23.2squeeze1 Linux Standard Base version report
ii python 2.6.6-3+squeeze6 interactive high-level object-orie
ii python-apt 0.7.100.1Python interface to libapt-pkg
ii python-support 1.0.10 automated rebuilding support for P
Versions of packages update-manager-core recommends:
ii update-manager-gnome 0.200.5-1 GNOME application that manages sof
update-manager-core 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#627035: [rkhunher] rkhunter always fails with Invalid BINDIR configuration option:
Package: rkhunher Version: 1.3.8-6 Severity: grave --- Please enter the report below this line. --- This version always fails with ipnp21:/home/davidek# rkhunter -c --rwo Invalid BINDIR configuration option: Invalid directory found: . Even specifying the --bindir option does not help, e.g.: ipnp21:/home/davidek# rkhunter --bindir /sbin -c --rwo Invalid '--bindir' option: Invalid directory found: . It sounds like the package is badly compiled --- System information. --- Architecture: amd64 Kernel: Linux 2.6.32-5-amd64 Debian Release: 6.0.1 850 stable ftp.debian.org 800 testing www-ucjf.troja.mff.cuni.cz 500 testing www-ucjf.troja.mff.cuni.cz 500 stable www.debian-multimedia.org 500 proposed-updates ftp.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#626723: RFP: rhythmbox-plugin-ror -- Remember last played song and play it as first song after rhythmbox restarts.
Le samedi 14 mai 2011 à 21:21 +0400, Roman V. Nikolaev a écrit : Package name: rhythmbox-plugin-ror Version: unknown Upstream Author: Michal Nánási m...@ksp.rhythmboxplugin.ksp.sk URL: http://people.ksp.sk/~mic/Projects/RhythmboxROR License: GPL3 Description: Remember last played song and play it as first song after rhythmbox restarts. These plugins are way too small to make it relevant to package each of them separately. I encourage anyone interested in rhythmbox plugins to start collecting third-party plugins and put them in a single package. -- .''`. Josselin Mouette : :' : `. `' `- signature.asc Description: This is a digitally signed message part
Bug#626717: Is the 0.12 stuck in 'New queue' or somewhere else ?
Hi all, Sorry for the noise. I saw the bug yesterday and have tried to see the updated package in all suites (via browser as well) but came up empty or precisely till 0.11.2 which has the bug. $ apt-show-versions -a libstartup-notification0 libstartup-notification0 0.10-1 install ok installed libstartup-notification0 0.10-1 stable ftp.us.debian.org libstartup-notification0 0.10-1 testing ftp.us.debian.org libstartup-notification0 0.11-2 sid ftp.us.debian.org libstartup-notification0/sid upgradeable from 0.10-1 to 0.11-2 A package which has update in experimental :- $ apt-show-versions -a debdelta debdelta 0.41 install ok installed debdelta 0.39trl stable ftp.us.debian.org debdelta 0.41testing ftp.us.debian.org debdelta 0.41sid ftp.us.debian.org debdelta 0.42exp experimental ftp.us.debian.org debdelta/testing uptodate 0.41 Just asking if somebody knows what the status of the updated package, maybe its stuck somewhere in the 'New' queue or something like that. (don't really know how the internals of how updates/upgrades are done within debian.org archives so will shut up here. ) Looking for info. -- Regards, Shirish Agarwal शिरीष अग्रवाल My quotes in this email licensed under CC 3.0 http://creativecommons.org/licenses/by-nc/3.0/ http://flossexperiences.wordpress.com 065C 6D79 A68C E7EA 52B3 8D70 950D 53FB 729A 8B17 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#627036: [kate-syntax-go] kate not capitalized in short description
Package: kate-syntax-go Version: 1:57.1-1 Severity: minor The short description reads: Syntax files to highlight Go in kate Kate is a proper noun and must be capitalized. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#626713: ntop crashes my kernel
package ntop severity 626713 important tags 626713 + moreinfo thanks Lowering severity as looks like it is dependent on your specific a hardware and is likely to be a kernel bug. However, I need some more information (see previous message) before reassigning the bug. Thanks, Ludovico -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#626960: ldap2zone: man page for ldap2bind
Hi Andi, thanks. It's now included. Cheers, Cajus Am Montag, den 16.05.2011, 20:19 +0200 schrieb Andreas B. Mundt: Package: ldap2zone Severity: normal Tags: patch Find attached a manual page for the executable ldap2bind. Best Regards, Andi -- System Information: Debian Release: wheezy/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash signature.asc Description: This is a digitally signed message part
Bug#627037: python-tables: module fails to import due to undefined symbol H5T_STD_U8BE_g
Package: python-tables Version: 2.1.2-3.1+b2 Severity: important When importing tables, I get the following traceback. user@host:~$ python Python 2.6.6 (r266:84292, Apr 20 2011, 09:34:38) [GCC 4.5.2] on linux2 Type help, copyright, credits or license for more information. import tables Traceback (most recent call last): File stdin, line 1, in module File /usr/lib/python2.6/dist-packages/tables/__init__.py, line 76, in module from tables.file import File, openFile, copyFile File /usr/lib/python2.6/dist-packages/tables/file.py, line 43, in module from tables import hdf5Extension ImportError: /usr/lib/python2.6/dist-packages/tables/hdf5Extension.so: undefined symbol: H5T_STD_U8BE_g -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages python-tables depends on: ii libc6 2.13-4 Embedded GNU C Library: Shared lib ii libhdf5-serial-1.8.4 [lib 1.8.4-patch1-2 Hierarchical Data Format 5 (HDF5) ii python2.6.6-14 interactive high-level object-orie ii python-central0.6.17 register and build utility for Pyt ii python-numpy 1:1.5.1-2+b1 Numerical Python adds a fast array python-tables recommends no packages. Versions of packages python-tables suggests: pn python-netcdf none (no description available) pn python-tables-doc none (no description available) -- no debconf information __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#627002: daisy-player: Should recommend udisks only, not depend on it.
tags 627002 + pending thanks daisy-player currently does not enter testing automatically because it's non-installable on kfreebsd-*, because udisks is not available there. Does the udisks dependency really need to be strict? As I understand it, udisks is only a help to daisy-player, so it could be a Recommends only, which nowadays has the same effect as a Depends (i.e. installed by default), whithout making daisy-player uninstallable on all !linux archs (yes, udisks is really a linux-only package) I already fixed this in the git repository, but by removing the dependency for !linux on udisks (I described the fact in README.Debian). Daisy-player expects udisks to be present if you don't start it with a directory on command line, so I prefer it this way. Do you think the recommends is the better solution? I am waiting for bug 625649 (unrelated problem) to get fixed and I will upload a new version. Paul signature.asc Description: OpenPGP digital signature
Bug#627038: ITP: libacsccid -- PC/SC driver for ACS USB CCID smart card readers
Package: wnpp Severity: wishlist Owner: Godfrey Chung godfrey.ch...@acs.com.hk * Package name: libacsccid Version : 1.0.2 Upstream Author : Advanced Card Systems Ltd. i...@acs.com.hk * URL : http://www.acs.com.hk/ * License : LGPL-2.1 Programming Lang: C Description : PC/SC driver for ACS USB CCID smart card readers This library provides a PC/SC IFD handler implementation for the ACS USB smart card readers compliant to the CCID protocol. This package is needed to communicate with the ACS CCID smartcard readers through the PC/SC Lite resource manager (pcscd). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#627040: freeipmi-ipmidetect configuration sample
Package: freeipmi-ipmidetect Version: 0.7.17~beta2-1 Severity: wishlist Thanks for packaging freeipmi! Could you include a sample /etc/ipmidetectd.conf? I'd like to see some examples of what others are doing with this tool. BTW I just succeeded in installing Intel's CLI Server Management Utilities -- dpcproxy and dpccli -- and it would be useful to know whether they interact with freeipmi in some way. Configuring ipmi on Debian seems to require membership in a secret society. -- System Information: Debian Release: 6.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.36.2 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=ISO-8859-1) (ignored: LC_ALL set to en_US) Shell: /bin/sh linked to /bin/dash Versions of packages freeipmi-ipmidetect depends on: ii libc6 2.11.2-10 Embedded GNU C Library: Shared lib ii libfreeipmi6 0.7.17~beta2-1 GNU IPMI - libraries ii libipmidetect00.7.17~beta2-1 GNU IPMI - IPMI node detection lib freeipmi-ipmidetect recommends no packages. freeipmi-ipmidetect 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#627039: chromium chooses a very poor font for Japanese text
Package: chromium Version: 11.0.696.65~r84435-1 Severity: normal Recently (basically following the most recent upgrade, to version 11) chromium has started using a poor font for rendering Japanese text -- it uses the kanjistrokeorders font, which is not really designed for normal text display (and as a result, tends to be somewhat hard to read). I don't really understand how default fonts get chosen for the system in general (some fontconfig setting?), but no other app seems to choose this font; I have a bunch of Japanese fonts installed, and most of them would be a better choice than the kanjistrokeorders font. [Ideally it would be nice to allow per-language font customization -- chromium only seems to allow setting a single default font, which in most cases won't be appropriate for CJK text (FF, for instance, allows per-language font settings).] Thanks, -Miles -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (50, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38-2-amd64 (SMP w/2 CPU cores) Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages chromium depends on: ii chromium-inspect 11.0.696.65~r84435-1page inspector for the chromium br ii libasound2 1.0.23-4shared library for ALSA applicatio ii libbz2-1.0 1.0.5-6 high-quality block-sorting file co ii libc62.13-4 Embedded GNU C Library: Shared lib ii libcairo21.10.2-6The Cairo 2D vector graphics libra ii libcups2 1.4.6-5 Common UNIX Printing System(tm) - ii libdbus-1-3 1.4.8-3 simple interprocess messaging syst ii libdbus-glib-1-2 0.92-1 simple interprocess messaging syst ii libevent-1.4-2 1.4.13-stable-1 An asynchronous event notification ii libexpat12.0.1-7 XML parsing C library - runtime li ii libfontconfig1 2.8.0-2.2 generic font configuration library ii libfreetype6 2.4.4-1 FreeType 2 font engine, shared lib ii libgcc1 1:4.6.0-7 GCC support library ii libgconf2-4 2.32.1-1GNOME configuration database syste ii libgcrypt11 1.4.6-5 LGPL Crypto library - runtime libr ii libgdk-pixbuf2.0 2.23.3-3GDK Pixbuf library ii libglib2.0-0 2.28.6-1The GLib library of C routines ii libgtk2.0-0 2.24.4-3The GTK+ graphical user interface ii libjpeg626b1-1 The Independent JPEG Group's JPEG ii libnspr4-0d 4.8.7-2 NetScape Portable Runtime Library ii libnss3-1d 3.12.9.with.ckbi.1.82-1 Network Security Service libraries ii libpam0g 1.1.2-3 Pluggable Authentication Modules l ii libpango1.0-01.28.3-6Layout and rendering of internatio ii libpng12-0 1.2.44-2PNG library - runtime ii libspeex11.2~rc1-1 The Speex codec runtime library ii libstdc++6 4.6.0-7 The GNU Standard C++ Library v3 ii libvpx0 0.9.6-1 VP8 video codec (shared library) ii libx11-6 2:1.4.3-1 X11 client-side library ii libxdamage1 1:1.1.3-1 X11 damaged region extension libra ii libxext6 2:1.3.0-1 X11 miscellaneous extension librar ii libxml2 2.7.8.dfsg-2+b1 GNOME XML library ii libxrender1 1:0.9.6-1 X Rendering Extension client libra ii libxslt1.1 1.1.26-7+b1 XSLT 1.0 processing library - runt ii libxss1 1:1.2.1-1 X11 Screen Saver extension library ii libxtst6 2:1.2.0-1 X11 Testing -- Record extension li ii xdg-utils1.1.0~rc1-2 desktop integration utilities from ii zlib1g 1:1.2.5.dfsg-1 compression library - runtime chromium recommends no packages. Versions of packages chromium suggests: pn chromium-l10n 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#626815: The uzbl package is missing important dependencies.
forcemerge 626815 626818 tag 626815 + pending thanks Don Allen scrisse: The uzbl package provided by Debian 6.0.1 is missing important dependences, e.g., socat, dmenu (part of suckless-tools). Please note that those are not important dependencies, as they're used by helper scripts and not needed by uzbl-core by itself. They're currently suggested packages, but I'm moving to recommended in order to automatically install them by default while leaving the option of removing them. Patch is already in git repo, it will be included in the next cumulative upload. Cheers, Luca -- .''`. ** Debian GNU/Linux ** | Luca Bruno (kaeso) : :' : The Universal O.S.| lucab (AT) debian.org `. `'` | GPG Key ID: 3BFB9FB3 `- http://www.debian.org | Debian GNU/Linux Developer signature.asc Description: PGP signature
Bug#627041: ipmitool: Configuration with bmcautoconf.sh
Package: ipmitool Version: 1.8.11-2 Severity: wishlist What happened to bmcautoconf.sh? It would be useful to have an auto-configuration script. Cheers, David -- System Information: Debian Release: 6.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.36.2 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=ISO-8859-1) (ignored: LC_ALL set to en_US) Shell: /bin/sh linked to /bin/dash Versions of packages ipmitool depends on: ii libc6 2.11.2-10Embedded GNU C Library: Shared lib ii libncurses5 5.7+20100313-5 shared libraries for terminal hand ii libreadline66.1-3GNU readline and history libraries ii libssl0.9.8 0.9.8o-4squeeze1 SSL shared libraries ii lsb-base3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip ipmitool recommends no packages. Versions of packages ipmitool suggests: ii openipmi 2.0.16-1.2 Intelligent Platform Management In -- 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#533799: Should look in /etc/midori/styles/, not /usr/local/share/midori/styles/.
Well, that depends if you consider the styles config or data. Currently midori considers them as data and look for them in XDG_DATA_DIR. Changing to XDG_CONFIG_DIR would look for them in /etc and .config but it's not what upstream wants, afaict. Regards, -- Yves-Alexis -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#569531: More info
tag 569531 moreinfo thanks Hey, can you still reproduce using midori 0.3.6-1 in unstable? Regards, -- Yves-Alexis -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#611659: cfengine seems to dislike Debian's symlinks
I also experienced the same problem. The correct workaround seems to be this: The symlink /var/lib/cfengine3/inputs has to be a real directory. E.g., cd /var/lib/cfengine3 mv inputs inputs.old mkdir inputs cp /usr/share/doc/cfengine3/examples/* /var/lib/cfengine3/inputs * be careful to set the directory permission to of inputs. Usually, root-owned and not world writable should be OK. env LANG=C ls -l /var/lib/cfengine3 total 180 lrwxrwxrwx 1 root root 9 Apr 13 06:45 bin - /usr/sbin -rw--- 1 root root 16384 May 17 15:51 cf_classes.db drwxr-xr-x 2 root root 4096 May 16 12:20 inputs lrwxrwxrwx 1 root root 14 Apr 13 06:45 inputs.old - /etc/cfengine3 drwxr-xr-x 2 root root 4096 May 16 12:15 lastseen drwxr-xr-x 2 root root 4096 May 16 12:18 masterfiles drwx-- 2 root root 4096 May 16 12:15 modules drwxr-xr-x 2 root root 4096 May 17 15:51 outputs -rw--- 1 root root 8192 May 17 15:50 performance.db drwx-- 2 root root 4096 May 16 12:15 ppkeys -rw--- 1 root root 116528 May 17 15:51 promise_summary.log -rw-r--r-- 1 root root 1024 May 16 12:15 randseed drwxr-xr-x 2 root root 4096 May 16 12:15 reports drwxr-xr-x 2 root root 4096 May 17 15:52 state This wastes /etc/cfengine3. The files under it are not used at all. The cause: Obviously, the link /var/lib/cfengine3/inputs was created as a handy manner to refer to /etc/cfengine3/. But cfengine3 seems to have a rather peculiar security concern of using a symlink to refer to the directory where configuration files are stored. Such a caution is not unexpected for a security-conscious program. (Still I am a little surprised here since sendmail v8 used to allow the reference to user-defined programs that are invoked during sendmail run through a symlink under a protected diretory. cfengine3 seems to take a more serious attitude re symlinks. That is, this symlink is BELOW a root-owned world-non-writable directory, and is safe IMHO. But cfengine probably was never intended to refer to configuration files through a symlink anyway.) From /usr/share/doc/cfengine3/README.cfengine3 --- quote begins --- *) cfengine3 is FHS, that means that, unlike the original, we log in /var/log, the binaries are located in /usr/sbin and the inputs files are in /etc/cfengine3; for upstream compatibility we have two symlinks: /etc/cfengine3 - /var/lib/cfengine3/inputs /usr/sbin - /var/lib/cfengine3/bin --- end quote So the choice of FHS file layout is something to blame until cfengine3 source file is fixed to allow for *THIS* particular setup (and NOT others for obvious security reasons). Oh wait. I just tried to install cfengine3 yesterday, and have not tested the invocation of various commands through cron entries. I wonder if /var/lib/cfengine3/bin is suffering from the same problem ??? At least the crontab entries installed by cfengine3 seems to be invoked every 5 minutes without major ill-effects: but I have yet to configure cfengine3 to copy various files from the master repository, etc. and so the relevant commands may not have been invoked really. Hope this helps. CI -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#617759: Also experienced here
Package: icedove Version: 3.1.10-1 I also just hit this bug. Icedove last started fine 2 days ago. Since then the only related change is the upgrade of xul-ext-firetray from 0.2.8-2 to 0.2.8-3, which must have started it. This is an i386 testing/unstable mix. Many thanks to Jonathan for the workaround (running Icedove that way once fixes it). I'm writing this mail from my usual Icedove thanks to you. I confirm the description from Jonathan (Message #119). More precisely, on this machine, icedove seems to break if and only if: While glibc 2.13 is installed, icedove is [re]installed, or an extension (maybe not any) is manipulated (that is installed, upgraded or removed). glibc 2.13 migrated to testing 3 days ago. 2 days ago a testing user reported http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626812 icedove: Icedove crash on start with libimgicon.so undefined symbol NS_GetServiceManager which has to be related. https://bugs.launchpad.net/ubuntu/+source/seamonkey/+bug/759406 seamonkey 2.0.13 does not start, missing libxpcom.so and libxpcom_core.so (Natty, x86_64) was reported on April 13th against Seamonkey and sounds a lot like #626812. --- System information. --- Architecture: i386 Kernel: Linux 2.6.38-2-686-bigmem Debian Release: wheezy/sid 990 testing security.debian.org 990 testing ftp.ca.debian.org 500 unstable ftp.ca.debian.org 1 experimental ftp.ca.debian.org --- Package information. --- Depends (Version) | Installed =-+-= fontconfig | 2.8.0-2.2 psmisc | 22.13-1 debianutils (= 1.16) | 3.4.4 libasound2 ( 1.0.18) | 1.0.23-3 libatk1.0-0 (= 1.12.4) | 2.0.0-1 libc6 (= 2.3.6-6~) | 2.13-4 libcairo2 (= 1.8.8) | 1.10.2-6 libdbus-1-3 (= 1.0.2) | 1.4.8-3 libffi5 (= 3.0.4) | 3.0.9-4 libfontconfig1 (= 2.8.0) | 2.8.0-2.2 libfreetype6 (= 2.2.1) | 2.4.4-1 libgcc1 (= 1:4.1.1) | 1:4.6.0-2 libgdk-pixbuf2.0-0 (= 2.22.0) | 2.23.3-3 libglib2.0-0 (= 2.24.0) | 2.28.6-1 libgtk2.0-0 (= 2.24.0) | 2.24.4-3 libhunspell-1.2-0 (= 1.2.11) | 1.2.14-4 libjpeg62 (= 6b1) | 6b1-1 libnspr4-0d (= 4.7.0~1.9b1) | 4.8.7-2 libnss3-1d (= 3.12.6) | 3.12.9.with.ckbi.1.82-1 libpango1.0-0 (= 1.14.0) | 1.28.3-6 libpixman-1-0 (= 0.11.2) | 0.21.8-1 libpng12-0 (= 1.2.13-4) | 1.2.44-2 libsqlite3-0 (= 3.6.5) | 3.7.6.2-1 libstartup-notification0 (= 0.11) | 0.11-2 libstdc++6 (= 4.1.1) | 4.6.0-2 libx11-6 | 2:1.4.3-1 libxrender1 | 1:0.9.6-1 libxt6 | 1:1.1.1-1 zlib1g (= 1:1.1.4) | 1:1.2.3.4.dfsg-3 Recommends (Version) | Installed ==-+-=== myspell-en-us | OR hunspell-dictionary | OR myspell-dictionary | Suggests (Version) | Installed =-+-=== ttf-lyx | 2.0.0~rc3-2 libgssapi-krb5-2 | 1.9+dfsg-1+b1 libdbus-glib-1-2 (= 0.78) | 0.92-1 libgconf2-4 (= 2.27.0) | 2.28.1-6 libgnomevfs2-0 (= 1:2.17.90) | 1:2.24.4-1 libnotify1 (= 0.5.0) | 0.5.0-2 libnotify1-gtk2.10 |
Bug#615133: [lm-sensors] FAULT status of sensors
On Mon, 16 May 2011 19:32:52 -0700, Guenter Roeck wrote: On Mon, May 16, 2011 at 02:23:44PM -0400, Jan Wagner wrote: Hi there, we got a bugreport[1] against our nagios-plugins package. Unfortunately we are unsure about what FAULT means. In case this is a hardware problem of a sensor in form of it got damaged, we would report CRITICAL, as a problem occured. If this means there is a problem detecting the sensor or something software like problem, we would report UNKNOWN as this not means a hardware problem happened. It is supposed to indicate a HW problem. Here is the text describing the sysfs attribute: Each input channel may have an associated fault file. This can be used to notify open diodes, unconnected fans etc. where the hardware supports it. When this boolean has value 1, the measurement for that channel should not be trusted. Note that critical in the hwmon ABI means that a critical limit has been reached. You would get a critical alarm in this case. You might have a terminology problem if you use critical for a hardware failure. An undetected sensor should not show up in the first place. In fact, FAULT can happen in two different cases. First case (most common) is unused channel by the manufacturer and the channel should indeed be ignored. Second case is thermal diode dying or fan stalling, and reporting this makes sense. So I would: * Ignore sensor channels which report FAULT when you start monitoring. * Report FAULT as an actual problem if it happens later during monitoring, for a channel which reported real values before. The terminology is up to you. -- Jean Delvare -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#626680: console-data: setting overwritten by reboot
Hello Christian :
Christian PERRIER bubu...@debian.org writes:
Quoting Boris Daix (boris.d...@alysse.org):
Very unlikely. console-data should be replaced by console-setup, some
day. It is currently in very very low maintenance mode. You'd better
use console-setup.
Well, I understand. That's why I had to apt-get install console-data.
However I still need console-data to get pc-dvorak-latin1 keymap
installed. How would you set this keymap up as
XKB{MODEL,LAYOUT,VARIANT,OPTIONS} variables in /etc/default/keyboard?
By installing and configuring console-setup..:-).
I would be very pleased if I could use console-setup to set
pc-dvorak-latin1 up *once for all* but this keymap is not available
through console-setup. So I repeat my question : how could I (really)
set my console keymap up?...
Thanks,
--
Boris Daix
pgpnlCooZmj0J.pgp
Description: PGP signature
Bug#626955: libgl1-mesa-dri: Version 7.10.2 does not work with gnome-shell, 7.10-4 works ok
On Die, 2011-05-17 at 06:38 +0200, Cyril Brulebois wrote: Arief M Utama ar...@life2play.net (17/05/2011): Not sure how to start gnome-shell with all the exports override, so I just did a make install. Result is, gnome-shell works ok, as it was before in 7.10-4. alright; what if you build r600c instead? It's good to see that current r600g is alright (as was 7.10), but knowing if r600c is still buggy was my point, so that you could report a bug upstream to possibly get that fixed. Not sure that's worth it, as r600c isn't really being actively developed anymore. In fact, I wonder if it wouldn't be better to switch back to shipping r600g again. I think the worst problems that prompted the move back from r600g to r600c should be fixed with current Mesa 7.10 branch and kernels, and even if there's still something left, the chances of getting a fix backported from master should be better with r600g than r600c. -- Earthling Michel Dänzer |http://www.vmware.com Libre software enthusiast | Debian, X and DRI developer -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#626955: libgl1-mesa-dri: Version 7.10.2 does not work with gnome-shell, 7.10-4 works ok
Michel Dänzer daen...@debian.org (17/05/2011): In fact, I wonder if it wouldn't be better to switch back to shipping r600g again. I think the worst problems that prompted the move back from r600g to r600c should be fixed with current Mesa 7.10 branch and kernels, and even if there's still something left, the chances of getting a fix backported from master should be better with r600g than r600c. I've been pondering that since my first message in this bug. Given 7.10.2 hit wheezy already, that's probably a good idea to try that again. Arief, you may want to cancel any testing, thanks anyway! Mraw, KiBi. signature.asc Description: Digital signature
Bug#626808: qemu: failed to find romfile
On Sun, May 15, 2011 at 10:50 PM, Vagrant Cascadian vagr...@freegeek.org wrote: could you be more specific about the exact commandline options, .img and .iso used? For example, `qemu -hda debian-live-6.0.1-i386-gnome-desktop.img` (image file is downloaded from live.debian.net) if i use a working hd.img, or a working cdrom.iso, qemu boots to that. when i created an empty hd.img and cdrom.iso, it fails to boot, but gives expected error messages (i.e. boot from hard disk, boot from floppy, boot from cd...) and errors out with no bootable device. if i specify to do network boot (with -boot n), it finds pxe-e1000.bin just fine, and boots from that. pxe-e1000.bin should be a symlink to the relevent etherboot-qemu rom (which is a dependency of qemu-system). -boot n gives the same error message. pxe-e1000.bin is located in /usr/share/qemu/pxe-e1000.bin, though I have no idea why qemu has not found it. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#627039: Acknowledgement (chromium chooses a very poor font for Japanese text)
ah... actually, installing the chromium-l10n package fixes this problem. [I used to have the chromium-browser-l10n package installed, but somehow the switch to the new package names didn't end up installing chromium-l10n...] Thanks, -Miles -- Cat is power. Cat is peace. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#627042: security flaw in 2.9.21
Package: nbd-server Version: 1:2.9.21-1 Severity: normal Tags: security nbd 2.9.21 contains a security issue in the negotiation phase (remote DoS). It should not migrate, ever. -- System Information: Debian Release: wheezy/sid APT prefers testing-proposed-updates APT policy: (500, 'testing-proposed-updates'), (500, 'oldstable'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38-2-amd64 (SMP w/2 CPU cores) Locale: LANG=nl_BE.UTF-8, LC_CTYPE=nl_BE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages nbd-server depends on: ii adduser 3.112+nmu2 add and remove users and groups ii debconf [debconf-2.0]1.5.39 Debian configuration management sy ii libc62.13-4 Embedded GNU C Library: Shared lib ii libglib2.0-0 2.28.6-1The GLib library of C routines ii ucf 3.0025+nmu2 Update Configuration File: preserv nbd-server recommends no packages. nbd-server suggests no packages. -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#627028: Broken perl dependencies in testing
On Tue, May 17, 2011 at 07:42:52AM +0200, Matthias Faulstich wrote: Package: perl-base / liblocale-gettext-perl / libxml-parser-perl Version: 5.10.1-20 Debian Version: testing Package to be installed: perl-base_5.12.3-6_amd64.deb Trying apt-get dist-update on testing fails since Monday, 05/16/2011 caused by broken dependencies in the perl libraries. After removing all perl packages with broken dependencies I don't need actually, following stay unresolved: (Sorry, my system is localized in German) apt-get install --reinstall perl-base Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut Statusinformationen werden eingelesen... Fertig Probieren Sie »apt-get -f install«, um dies zu korrigieren: Die folgenden Pakete haben unerfüllte Abhängigkeiten: liblocale-gettext-perl : Hängt ab von (vorher): perlapi-5.10.0 libxml-parser-perl : Hängt ab von: perlapi-5.10.0 This seems wrong; as you can see from http://packages.debian.org/wheezy/libxml-parser-perl this package depends on perlapi-5.12.3, not perlapi-5.10.0. Please could you post the contents of your /etc/apt/sources.list and the output of apt-cache policy libxml-parser-perl These packages cannot be removed since they are part of the Debian configuration mechanism: sudo dpkg --purge liblocale-gettext-perl dpkg: Abhängigkeitsprobleme verhindern Entfernen von liblocale-gettext-perl: libparse-debianchangelog-perl hängt ab von liblocale-gettext-perl; aber: Paket liblocale-gettext-perl soll entfernt werden. debconf-i18n hängt ab von liblocale-gettext-perl. tasksel hängt ab von liblocale-gettext-perl. dpkg: Fehler beim Bearbeiten von liblocale-gettext-perl (--purge): Abhängigkeitsprobleme - wird nicht entfernt Fehler traten auf beim Bearbeiten von: liblocale-gettext-perl If you really wanted to remove liblocale-gettext-perl you could install debconf-english instead, but that's probably not the best approach here. -- Dominic Hargreaves | http://www.larted.org.uk/~dom/ PGP key 5178E2A5 from the.earth.li (keyserver,web,email) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#627043: sane-backends: [INTL:nl] Dutch translation of debconf templates
Package: sane-backends Severity: wishlist Tags: patch l10n Hello, Attached is the Dutch translation of the sane-backends debconf templates. Please include it in your next upload. Regards, -- Jeroen Schot # Dutch translation of sane-backends debconf templates. # Copyright (C) 2011 THE PACKAGE'S COPYRIGHT HOLDER # This file is distributed under the same license as the sane-backends package. # Jeroen Schot sc...@a-eskwadraat.nl, 2011. # msgid msgstr Project-Id-Version: sane-backends 1.0.22-2\n Report-Msgid-Bugs-To: sane-backe...@packages.debian.org\n POT-Creation-Date: 2009-12-12 13:14+0100\n PO-Revision-Date: 2011-05-17 10:34+0200\n Last-Translator: Jeroen Schot sc...@a-eskwadraat.nl\n Language-Team: Debian l10n Dutch debian-l10n-du...@lists.debian.org\n MIME-Version: 1.0\n Content-Type: text/plain; charset=UTF-8\n Content-Transfer-Encoding: 8bit\n Language: nl\n #. Type: boolean #. Description #: ../sane-utils.templates:1001 msgid Enable saned as a standalone server? msgstr Wilt u saned als losstaande server activeren? #. Type: boolean #. Description #: ../sane-utils.templates:1001 msgid The saned server, when enabled, makes scanners available over the network. msgstr Indien geactiveerd maakt de saned-server scanners beschikbaar over het netwerk. #. Type: boolean #. Description #: ../sane-utils.templates:1001 msgid There are two ways of running saned:\n - as an inetd service, started by the inetd superserver. In this mode,\n saned is started on demand when a client connects to the server;\n - as a standalone daemon, started at system boot. In this mode, saned\n runs in the background all by itself and listens for client connections. msgstr Er zijn twee manieren om saned te draaien:\n - Als een inetd-dienst, gestart door de inetd-superserver. In deze modus\n wordt saned pas opgestart wanneer een client verbinding met de server maakt.\n - Als een losstaande achtergronddienst, opgestart bij de systemstart. In\n deze modus draait saned zelfstandig op de achtergrond en luistert naar\n client-verbindingen. #. Type: boolean #. Description #: ../sane-utils.templates:1001 msgid When run in standalone mode, saned advertises itself on the network and can be detected automatically by the SANE clients with no configuration on the client side. You still need to configure the server to accept connections from your clients. This feature is experimental and requires a running Avahi daemon. msgstr Wanneer saned in losstaande modus draait adverteert het zichzelf op het netwerk en kan door SANE-clients zonder configuratie automatisch worden gedetecteerd. U dient wel nog steeds de server te configureren om verbindingen van uw clients te accepteren. Deze functionaliteit is experimenteel en vereist een draaiende Avahi-achtergronddienst. #. Type: boolean #. Description #: ../sane-utils.templates:1001 msgid Accept this option if you want to make use of this feature. msgstr Kies voor deze optie als u gebruik wilt maken van deze functionaliteit. #. Type: boolean #. Description #: ../sane-utils.templates:2001 msgid Add saned user to the scanner group? msgstr De saned-gebruiker toevoegen aan de scanner-groep? #. Type: boolean #. Description #: ../sane-utils.templates:2001 msgid The saned server, when enabled, makes scanners available over the network. By applying different permissions to the different scanners connected to your machine, you can control which ones will be made available over the network. msgstr Indien geactiveerd maakt de saned-server scanners beschikbaar over het netwerk. Door verschillende permissies toe te kennen aan de verschillende scanners van deze machine kunt u bepalen welke er over het netwerk beschikbaar worden gemaakt. #. Type: boolean #. Description #: ../sane-utils.templates:2001 msgid Read /usr/share/doc/sane-utils/README.Debian for details on how to manage permissions for saned. By default, saned is run under the saned user and group. msgstr Lees /usr/share/doc/sane-utils/README.Debian voor informatie over het beheren van permissies voor saned. Standaard draait saned onder de saned- gebruiker en groep. #. Type: boolean #. Description #: ../sane-utils.templates:2001 msgid Accept this option if you want to make all your scanners available over the network without restriction. msgstr Kies voor deze optie als u al uw scanners zonder beperkingen over het netwerk beschikbaar wilt maken.
Bug#627039: chromium chooses a very poor font for Japanese text
Hi chromium maintainers! Am 17.05.2011 09:40, schrieb Miles Bader: Package: chromium Version: 11.0.696.65~r84435-1 Severity: normal Recently (basically following the most recent upgrade, to version 11) chromium has started using a poor font for rendering Japanese text -- [..] I'm just sending your this mail to be sure, that you are aware of this bug report, as it was send to the pkg-games team (as maintainer of the old chromium game I guess). Best regards, Alexander -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#627044: dictionaries-common: [INTL:nl] Dutch translation of debconf templates
Package: dictionaries-common
Version: 1.5.17
Severity: wishlist
Tags: patch l10n
Hello,
Attached is the updated Dutch translation of the dictionaries-common
debconf templates. Please include it in your next upload.
Regards,
--
Jeroen Schot
# Dutch translation of dictionaries-common debconf templates.
# Copyright (C) 2003-2011 THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the dictionaries-common
package.
# Bart Cornelis cob...@linux.be, 2003.
# Jeroen Schot sc...@a-eskwadraat.nl, 2011.
#
msgid
msgstr
Project-Id-Version: dictionaries-common 1.10.11\n
Report-Msgid-Bugs-To: dictionaries-com...@packages.debian.org\n
POT-Creation-Date: 2011-04-26 18:21+0200\n
PO-Revision-Date: 2011-05-17 10:38+0200\n
Last-Translator: Jeroen Schot sc...@a-eskwadraat.nl\n
Language-Team: Debian l10n Dutch debian-l10n-du...@lists.debian.org\n
Language: nl\n
MIME-Version: 1.0\n
Content-Type: text/plain; charset=UTF-8\n
Content-Transfer-Encoding: 8bit\n
#. Type: note
#. Description
#: ../dictionaries-common.templates:1001
msgid An invalid debconf value [${value}] has been found
msgstr Er is een ongeldige debconfwaarde (${value}) gevonden.
#. Type: note
#. Description
#: ../dictionaries-common.templates:1001
msgid It does not correspond to any installed package in the system.
msgstr
Deze is niet van toepassing op een op dit systeem geïnstalleerd pakket.
#. Type: note
#. Description
#: ../dictionaries-common.templates:1001
msgid
That is usually caused by problems at some time during packages
installation, where the package providing [${value}] was selected for
installation but finally not installed because of errors in other packages.
msgstr
Dit wordt gewoonlijk veroorzaakt door problemen tijdens het installeren van
pakketten, waarbij het pakket dat de waarde (${value}) leverde uitgekozen
was voor installatie maar uiteindelijk niet geïnstalleerd werd omwille van
fouten in andere pakketten.
#. Type: note
#. Description
#: ../dictionaries-common.templates:1001
msgid
To fix this error, reinstall (or install) the package that provides the
missing value. Then, if you don't want this package on your system, remove
it, which will also remove its debconf entries. Menu to be shown after this
message will try to leave the system in a working state until then.
msgstr
Om deze fout te verhelpen, herinstalleert u het pakket dat de ontbrekende
waarde levert. Daarna kunt u dat pakket, mocht u het niet op uw systeem
willen, verwijderen. Hierdoor worden ook de debconf-ingangen verwijderd. Het
volgende menu poogt het systeem achter te laten in een werkende staat.
#. Type: note
#. Description
#: ../dictionaries-common.templates:1001
msgid
This error message can also appear during ispell dictionary or wordlist
renaming (e.g., wenglish- wamerican). In this case it is harmless and
everything will be fixed after you select your default in the menu(s) shown
after this message.
msgstr
Deze foutmelding kan ook verschijnen tijdens het hernoemen van een ispell-
woordenboek of woordenlijst (bv. wenglish - wamerican). In dat geval is
deze melding onschuldig en zal alles opgelost worden wanneer u de standaard
selecteert in de menu(s) die zometeen getoond worden.
#. Type: select
#. Choices
#. Type: select
#. Choices
#: ../dictionaries-common.templates:2001 ../dictionaries-common.templates:3001
msgid ${echoices}
msgstr ${echoices}
#. Type: select
#. Choices
#. Type: select
#. Choices
#: ../dictionaries-common.templates:2001 ../dictionaries-common.templates:3001
msgid Manual symlink setting
msgstr Handmatig instellen van symbolische koppeling(en)
#. Type: select
#. Description
#: ../dictionaries-common.templates:2002
msgid System default ispell dictionary:
msgstr Wat is het standaard ispell-woordenboek voor dit systeem?
#. Type: select
#. Description
#: ../dictionaries-common.templates:2002
msgid
Please indicate which dictionary ispell should use as system-wide default
when no other spell-checking dictionary is specified.
msgstr
Geef aan welk ispell-woordenboek als de standaard voor dit systeem moet
worden gebruikt als er geen ander woordenboek voor spellingscontrole is
opgegeven.
#. Type: select
#. Description
#: ../dictionaries-common.templates:2002
msgid
This sets up the /usr/lib/ispell/default.aff and /usr/lib/ispell/default.
hash symlinks, as well as ispell's global ispell-wrapper and Emacs defaults.
msgstr
Dit maakt de symbolische koppelingen /usr/lib/ispell/default.aff en /usr/lib/
ispell/default.hash aan. Daarnaast bepaalt het ook de globale ispell-wrapper
en standaardinstellingen van Emacs.
#. Type: select
#. Description
#: ../dictionaries-common.templates:2002
msgid
Use \Manual symlink setting\ if you want to handle the symlinks yourself.
In this case ispell will have no global ispell-wrapper or Emacs defaults.
msgstr
Gebruik \Handmatig instellen van symbolische koppeling(en)\ als u de
koppelingen zelf wilt beheren. In dat geval zal er geen globale ispell-
wrapper zijn
Bug#627038: See my Ubuntu PPA package of libacsccid
I have already prepared a package of libacsccid (binary: libacsccid1) and published it in my Ubuntu PPA. Might be useful to you as a starting point. https://launchpad.net/~jdthood/+archive/ppa In the same place you will also find packages of libnfc and mfoc; you are welcome to adopt those for Debian too. -- Thomas Hood -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#627045: qemu-kvm: VNC viewer kills kvm
Package: qemu-kvm Version: 0.12.5+dfsg-5+squeeze1 Severity: important Hi, I have a problem using vnc and kvm. I have a Windows 7 guest, and connect to kvm using VNC. The first time I launch a vncviewer, there is no problem. If I kill the vncviewer, and launch it again, kvm is killed. I do not know where to look to diagnose the problem. The command I use to launch kvm is the following: sudo kvm -daemonize \ -smp 4 -m 2000 \ -hda /dev/vg0/win7vm \ -boot order=cd \ -k fr \ -usb -usbdevice tablet \ -name Windows7 \ -vga std \ -vnc :1 \ -rtc base=localtime \ -net nic -net user best regards, E. -- Package-specific info: /proc/cpuinfo: processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 30 model name : Intel(R) Core(TM) i7 CPU 860 @ 2.80GHz stepping: 5 cpu MHz : 1199.000 cache size : 8192 KB physical id : 0 siblings: 8 core id : 0 cpu cores : 4 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm ida tpr_shadow vnmi flexpriority ept vpid bogomips: 5586.78 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: -- System Information: Debian Release: 6.0.1 Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) Shell: /bin/sh linked to /bin/dash Versions of packages qemu-kvm depends on: ii adduser3.112+nmu2add and remove users and groups ii bridge-utils 1.4-5 Utilities for configuring the Linu ii iproute20100519-3networking and traffic control too ii libaio10.3.107-7 Linux kernel AIO access library - ii libasound2 1.0.23-2.1shared library for ALSA applicatio ii libbluetooth3 4.66-3Library to use the BlueZ Linux Blu ii libbrlapi0.5 4.2-7 braille display access via BRLTTY ii libc6 2.11.2-10 Embedded GNU C Library: Shared lib ii libcurl3-gnutls7.21.0-1 Multi-protocol file transfer libra ii libgnutls262.10.5-1+b1 the GNU TLS library - runtime libr ii libncurses55.7+20100313-5shared libraries for terminal hand ii libpci31:3.1.7-6 Linux PCI Utilities (shared librar ii libpulse0 0.9.21-3+squeeze1 PulseAudio client libraries ii libsasl2-2 2.1.23.dfsg1-7Cyrus SASL - authentication abstra ii libsdl1.2debian1.2.14-6.1Simple DirectMedia Layer ii libuuid1 2.17.2-9 Universally Unique ID library ii libvdeplug22.2.3-3 Virtual Distributed Ethernet - Plu ii libx11-6 2:1.3.3-4 X11 client-side library ii python 2.6.6-3+squeeze6 interactive high-level object-orie ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime Versions of packages qemu-kvm recommends: ii linux-image-2.6.32-5-amd64 [l 2.6.32-31 Linux 2.6.32 for 64-bit PCs Versions of packages qemu-kvm suggests: ii debootstrap 1.0.26+squeeze1Bootstrap a basic Debian system ii samba 2:3.5.6~dfsg-3squeeze2 SMB/CIFS file, print, and login se ii vde2 2.2.3-3Virtual Distributed Ethernet -- 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#627046: zsh: Typo in make-kpkg completion
Package: zsh Version: 4.3.11-5 Severity: minor Tag: patch Hello, I just spotted a typo in make-kpkg completion help. Patch attached. Laurent. From 536d287c3ca3609f71ab0367d97529d54b570625 Mon Sep 17 00:00:00 2001 From: Laurent Fousse laur...@komite.net Date: Tue, 17 May 2011 10:41:23 +0200 Subject: [PATCH] Fix typo in make-kpkg completion. --- Completion/Debian/Command/_make-kpkg |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/Completion/Debian/Command/_make-kpkg b/Completion/Debian/Command/_make-kpkg index 68ddadc..c079d9a 100644 --- a/Completion/Debian/Command/_make-kpkg +++ b/Completion/Debian/Command/_make-kpkg @@ -35,7 +35,7 @@ _arguments \ kernel-source\:package of the kernel sources \ kernel-headers\:package of the header files included in the kernel \ kernel-manual\:package of the manual pages included in the kernel \ -kernel-doc\:package of teh documentation included in the kernel \ +kernel-doc\:package of the documentation included in the kernel \ kernel-image\:package of the kernel image \ build\:compiles the kernel \ modules\:build all add-on modules \ -- 1.7.5.1
Bug#615157: Using -Werror in CFLAGS for a debian package build
On 05/17/2011 01:31 AM, Wouter Verhelst wrote: [...] see http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-werror;users=debian-...@lists.debian.org This package builds with -Werror, and GCC 4.6 triggers new warnings which will make the package fail to build. Currently a Debian patch just passes -Wno-error=unused-but-set-variable and -Wno-error=unused-but-set-parameter to avoid build failures, but this patch will be reverted with the GCC 4.6.1 release, and the severity of the report will be raised. The list of packages may contain some false positives. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#609690: Debian x86 32-bits built for i586 !?
On 05/15/2011 04:39 PM, Henrique de Moraes Holschuh wrote: On Sun, 15 May 2011, Ben Hutchings wrote: On Sun, 2011-05-15 at 09:28 -0300, Henrique de Moraes Holschuh wrote: On Sun, 15 May 2011, Mike Hommey wrote: I just found out that gcc is compiled with --with-arch-32=i586, which effectively means it builds with -march=i586 by default (and that it still claims an i486-linux-gnu target). I'm wondering. Is the project at large aware that we're not building for i486, but for i586 ? That even the maintainer doesn't know why for No. And unless we got a bug report form an i486 user, our users probably didn't notice it either. What are the *exact* differences between code generated for march=i486 to code generated for march=i586? What CPUs would break? [...] There are a few new instructions on the Pentium that can be used in ring 3: cmpxchg8 and rdtsc. Linux has separate options for '586' and '586 with TSC', both of which result in -m586, so gcc does not appear to assume the existence of rdtsc. I would not expect gcc to generate cmpxchg8 except through an intrinsic, but I could be wrong. Assuming we can't just do away with i486 support for now, did anyone track down exactly what was causing breakages that forced the change from march=486 to march=586? libgomp assumes 586; there were some GFortran/OMP issues on i386. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#609690: Debian x86 32-bits built for i586 !?
On 05/16/2011 04:36 AM, Henrique de Moraes Holschuh wrote: On Mon, 16 May 2011, Ben Hutchings wrote: I think any claim that Debian supports 486-class processors is more of an aspiration. What maintainer has the time to test on such antiques regularly? Well, nobody is running regular kernel regression testing on 486-class hardware AFAIK, and that includes the kernel upstream. I'd doubt even i586 is getting any serious testing... So yes, it will break every so often, and the situation is not going to get any better. Note that some software is only built for i586 and newer processors, like OpenJDK in both lenny and squeeze, but apparently not used/tested on 486-class systems. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#627047: New upstream release: qsynth 0.3.6
Package: qsynth Severity: wishlist Hi, a new bugfix release of qsynth was released one month ago. The upstream's latest changelog entry follows: 2011-04-07 0.3.6 Slip release. - Main window layout fixing with regard to its user preferred size and recall when system-tray icon is not enabled. - Channels list preset items now activated on double-click. - Desktop environment session shutdown (eg. logout) is now tapped for graceful application exit, even though the main window is active (visible) and minimizing to system tray is enabled. Both were causing first shutdown/logout attempt to abort. Not anymore, hopefully ;). - libX11 is now being added explicitly to the build link phase, as seen necessary on some bleeding-edge distros eg. Fedora 13, Debian 6. - General standard dialog buttons layout is now in place. - CMake build system. It was silently available in 0.3.5, but now it is officially unveiled. - Fixed a couple of dangling pointers. So, please update. Thanks in advance. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38-2-amd64 (SMP w/4 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (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#615133: [lm-sensors] FAULT status of sensors
Hi Jonathan, thanks for your bugreport. On Tuesday 17 May 2011 09:36:00 Jean Delvare wrote: On Mon, 16 May 2011 19:32:52 -0700, Guenter Roeck wrote: On Mon, May 16, 2011 at 02:23:44PM -0400, Jan Wagner wrote: we got a bugreport[1] against our nagios-plugins package. Unfortunately we are unsure about what FAULT means. In case this is a hardware problem of a sensor in form of it got damaged, we would report CRITICAL, as a problem occured. If this means there is a problem detecting the sensor or something software like problem, we would report UNKNOWN as this not means a hardware problem happened. It is supposed to indicate a HW problem. Here is the text describing the sysfs attribute: Each input channel may have an associated fault file. This can be used to notify open diodes, unconnected fans etc. where the hardware supports it. When this boolean has value 1, the measurement for that channel should not be trusted. Note that critical in the hwmon ABI means that a critical limit has been reached. You would get a critical alarm in this case. You might have a terminology problem if you use critical for a hardware failure. An undetected sensor should not show up in the first place. In fact, FAULT can happen in two different cases. First case (most common) is unused channel by the manufacturer and the channel should indeed be ignored. Second case is thermal diode dying or fan stalling, and reporting this makes sense. So I would: * Ignore sensor channels which report FAULT when you start monitoring. * Report FAULT as an actual problem if it happens later during monitoring, for a channel which reported real values before. The terminology is up to you. (Jean: many thanks for your clarification) This means, that FAULT can be happen, if the hardware conditions are fine and hardware is failing too. On Saturday 26 February 2011 00:07:22 Jonathan Wiltshire wrote: The attached patch causes check_sensors to return a critical status if faulty sensors are detected. For nagios-plugins this means, we don't know if there is exactly a problem. We should report UNKNOWN via check_sensors if FAULT is reported by the sensor. As the source of this may also not a problem with the hardware conditions itself, something like --ignore-fault needs to be implemented too. With kind regards, Jan. -- Never write mail to w...@spamfalle.info, you have been warned! -BEGIN GEEK CODE BLOCK- Version: 3.12 GIT d-- s+: a C+++ UL P+ L+++ E--- W+++ N+++ o++ K++ w--- O M V- PS PE Y++ PGP++ t-- 5 X R tv- b+ DI D+ G++ e++ h r+++ y --END GEEK CODE BLOCK-- signature.asc Description: This is a digitally signed message part.
Bug#616715: ld.gold: internal error in value_from_output_section, at ../../gold/reloc.cc:1508
tags 616715 - moreinfo forwarded 616715 http://sourceware.org/bugzilla/show_bug.cgi?id=12771 quit Timo Juhani Lindfors wrote: Weird. Thanks again. I've taken the liberty of forwarding this upstream; I hope that's okay. Further discussion should probably happen there. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#626993: [l10n] Italian translation update for 1.10.11
tag 626993 +pending thanks On Mon, May 16, 2011 at 11:39:30PM +0200, Giuseppe Sacco wrote: Package: dictionaries-common Version: 1.10.10 Severity: wishlist Tags: l10n Hi, please update the Italian translation for dictionaries-common-1.10.11 with the attached file that has been proofread and reviewed by the Italian team. Thanks a lot. Committed to our git repo. Will go in next upload. Regards, -- Agustin Agustin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#627044: dictionaries-common: [INTL:nl] Dutch translation of debconf templates
tag 627044 +pending thanks On Tue, May 17, 2011 at 10:39:38AM +0200, Jeroen Schot wrote: Package: dictionaries-common Version: 1.5.17 Severity: wishlist Tags: patch l10n Hello, Attached is the updated Dutch translation of the dictionaries-common debconf templates. Please include it in your next upload. Thanks a lot. Committed to our git repo. Will go in next upload. Regards, -- Agustin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#620182: NMU for iitalian
On So, 15 Mai 2011, Julien Cristau wrote:
On Thu, Apr 14, 2011 at 18:48:58 +0900, Norbert Preining wrote:
Ciao Francesco,
Insieme con Robert Luberda ho preparato un NMU per iitalian, i cambiamenti
saranno:
[ Robert Luberda ]
* Rebuild with new ispell.
[ Norbert Preining ]
* add misc:Depends dependency
* remove post{inst,rm}.debhelper, it is auto generated
* reword synopsis (lintian warning)
* bump standards version to 3.9.2, no changes necessary
Attaccato trovi il diff del NMU. In caso che non senti niente di te
per una settimana farò un upload nel DELAYED/7.
Was this uploaded anywhere?
Unfortunately not, it dropped out pf my eyes. I will try to make the upload
when I am back from my work trip.
Thanks for reminding me.
Best wishes
Norbert
Norbert Preiningpreining@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan TeX Live Debian Developer
DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
GREELEY (n.)
Someone who continually annoys you by continually apologising for
annoying you.
--- Douglas Adams, The Meaning of Liff
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#626907: do a better job of differentiating find and oldfind
Fixed in git: http://git.savannah.gnu.org/cgit/findutils.git/commit/?id=b28cc8c49386540553d70567d2a5712ba6625bcf -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#627048: libsysfs2: Patch from LSI for cdev_name_equal
Package: libsysfs2 Version: 2.1.0+repack-1 Severity: minor Tags: patch upstream LSI bundled a modified libsysfs library with their recent versions of their CLI raid controller utility where they apparently patched a bug in cdev_name_equal. Upstream for sysfsutils _SEEMS_ very dead, reporting here instead. You can find their modified (and versionbumped) library at http://amd.co.at/data/sysfsutils-2.2.0.tar.gz, the diff to 2.1.0 from linux-diag.sf.net here: http://amd.co.at/data/sysfsutils.patch. A download link for the tool from LSI (including the library) can be found e.g. at http://www.lsi.com/storage_home/products_home/internal_raid/megaraid_sas/feature_line/9280-4i4e/index.html Support Downloads - MegaCLI - Linux (Version 8.01.06) -- System Information: Debian Release: 6.0.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-openvz-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/bash Versions of packages libsysfs2 depends on: ii libc6 2.11.2-10 Embedded GNU C Library: Shared lib libsysfs2 recommends no packages. libsysfs2 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#627049: Please install i18n-extension.h in the -dev package
Package: libv8 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, please install src/extensions/experimental/i18n-extension.h in the -dev package, chromium needs it. Cheers, Giuseppe. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk3SRdEACgkQNxpp46476aqLxQCgn6AvnoE9YPh291UKph9VzD71 qq8An2GRypTUTUQn2bG+Rp+HNYBcnJFq =uanp -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#627050: openssh-server: sftp server crashes
Package: openssh-server Version: 1:5.5p1-6 Severity: important Tags: wheezy Hi, I just did a fresh install of my Testing Debian AMD64 using a lot of config files from my backup (which I recon could be the cause of the problem). Whenever sftp-server is called for my main user, it crashes with a simple 'connection closed' message to the user... what's getting me crazy is that there is no error message for other users! (And no problem for regular ssh either) Below I copy the debug output. Let me know if I should provide more info. Thank you very much! Patricio - OUTPUT OF A FAILED CONNECTION FOR USER pato debug2: load_server_config: filename /etc/ssh/sshd_config debug2: load_server_config: done config len = 647 debug2: parse_server_config: config /etc/ssh/sshd_config len 647 debug3: /etc/ssh/sshd_config:5 setting Port 22 debug3: /etc/ssh/sshd_config:9 setting Protocol 2 debug3: /etc/ssh/sshd_config:11 setting HostKey /etc/ssh/ssh_host_rsa_key debug3: /etc/ssh/sshd_config:12 setting HostKey /etc/ssh/ssh_host_dsa_key debug3: /etc/ssh/sshd_config:14 setting UsePrivilegeSeparation yes debug3: /etc/ssh/sshd_config:17 setting KeyRegenerationInterval 3600 debug3: /etc/ssh/sshd_config:18 setting ServerKeyBits 768 debug3: /etc/ssh/sshd_config:21 setting SyslogFacility AUTH debug3: /etc/ssh/sshd_config:22 setting LogLevel INFO debug3: /etc/ssh/sshd_config:25 setting LoginGraceTime 120 debug3: /etc/ssh/sshd_config:26 setting PermitRootLogin yes debug3: /etc/ssh/sshd_config:27 setting StrictModes yes debug3: /etc/ssh/sshd_config:29 setting RSAAuthentication yes debug3: /etc/ssh/sshd_config:30 setting PubkeyAuthentication yes debug3: /etc/ssh/sshd_config:34 setting IgnoreRhosts yes debug3: /etc/ssh/sshd_config:36 setting RhostsRSAAuthentication no debug3: /etc/ssh/sshd_config:38 setting HostbasedAuthentication no debug3: /etc/ssh/sshd_config:43 setting PermitEmptyPasswords no debug3: /etc/ssh/sshd_config:47 setting ChallengeResponseAuthentication no debug3: /etc/ssh/sshd_config:62 setting X11Forwarding yes debug3: /etc/ssh/sshd_config:63 setting X11DisplayOffset 10 debug3: /etc/ssh/sshd_config:64 setting PrintMotd no debug3: /etc/ssh/sshd_config:65 setting PrintLastLog yes debug3: /etc/ssh/sshd_config:66 setting TCPKeepAlive yes debug3: /etc/ssh/sshd_config:73 setting AcceptEnv LANG LC_* debug3: /etc/ssh/sshd_config:75 setting Subsystem sftp /usr/lib/openssh/sftp-server debug3: /etc/ssh/sshd_config:86 setting UsePAM yes debug1: sshd version OpenSSH_5.5p1 Debian-6 debug3: Not a RSA1 key file /etc/ssh/ssh_host_rsa_key. debug1: read PEM private key done: type RSA debug1: Checking blacklist file /usr/share/ssh/blacklist.RSA-2048 debug1: Checking blacklist file /etc/ssh/blacklist.RSA-2048 debug1: private host key: #0 type 1 RSA debug3: Not a RSA1 key file /etc/ssh/ssh_host_dsa_key. debug1: read PEM private key done: type DSA debug1: Checking blacklist file /usr/share/ssh/blacklist.DSA-1024 debug1: Checking blacklist file /etc/ssh/blacklist.DSA-1024 debug1: private host key: #1 type 2 DSA Restarting OpenBSD Secure Shell server: sshddebug2: load_server_config: filename /etc/ssh/sshd_config debug2: load_server_config: done config len = 647 debug2: parse_server_config: config /etc/ssh/sshd_config len 647 debug3: /etc/ssh/sshd_config:5 setting Port 22 debug3: /etc/ssh/sshd_config:9 setting Protocol 2 debug3: /etc/ssh/sshd_config:11 setting HostKey /etc/ssh/ssh_host_rsa_key debug3: /etc/ssh/sshd_config:12 setting HostKey /etc/ssh/ssh_host_dsa_key debug3: /etc/ssh/sshd_config:14 setting UsePrivilegeSeparation yes debug3: /etc/ssh/sshd_config:17 setting KeyRegenerationInterval 3600 debug3: /etc/ssh/sshd_config:18 setting ServerKeyBits 768 debug3: /etc/ssh/sshd_config:21 setting SyslogFacility AUTH debug3: /etc/ssh/sshd_config:22 setting LogLevel INFO debug3: /etc/ssh/sshd_config:25 setting LoginGraceTime 120 debug3: /etc/ssh/sshd_config:26 setting PermitRootLogin yes debug3: /etc/ssh/sshd_config:27 setting StrictModes yes debug3: /etc/ssh/sshd_config:29 setting RSAAuthentication yes debug3: /etc/ssh/sshd_config:30 setting PubkeyAuthentication yes debug3: /etc/ssh/sshd_config:34 setting IgnoreRhosts yes debug3: /etc/ssh/sshd_config:36 setting RhostsRSAAuthentication no debug3: /etc/ssh/sshd_config:38 setting HostbasedAuthentication no debug3: /etc/ssh/sshd_config:43 setting PermitEmptyPasswords no debug3: /etc/ssh/sshd_config:47 setting ChallengeResponseAuthentication no debug3: /etc/ssh/sshd_config:62 setting X11Forwarding yes debug3: /etc/ssh/sshd_config:63 setting X11DisplayOffset 10 debug3: /etc/ssh/sshd_config:64 setting PrintMotd no debug3: /etc/ssh/sshd_config:65 setting PrintLastLog yes debug3: /etc/ssh/sshd_config:66 setting TCPKeepAlive yes debug3: /etc/ssh/sshd_config:73 setting AcceptEnv LANG LC_* debug3: /etc/ssh/sshd_config:75 setting Subsystem sftp /usr/lib/openssh/sftp-server debug3: /etc/ssh/sshd_config:86 setting UsePAM yes debug1: sshd version OpenSSH_5.5p1 Debian-6 debug3: Not a
Bug#331499: dokuwiki: multisite support
Hi, El dg 08 de 05 de 2011 a les 23:21 +0200, en/na Tanguy Ortolo va escriure: Tanguy Ortolo, 2011-04-13 21:26 UTC+0200: Let me check that the farming system is not to get unsupported in future releases, and I shall do the work. Finally, it appears that it will be supported in the next releases, and I should be able to add multisite support without much trouble. However, given that this will be a quite important and error-prone change, I shall upload it to experimental, not to unstable. Could you let us know when it's uploaded? Thanks for your work! Mònica signature.asc Description: This is a digitally signed message part
Bug#626851: More info
The error described can be also seen if compiling a vanilla kernel with the exact config as the Debian one (in my case 2.6.38.6) . I'm writing this from the same machine running 2.6.38.4 with a custom config and it works fine. Hope it helps. -- Rares Aioanei -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#626851: linux-image-2.6.38-2-amd64: after last update fails to boot
tags 626851 + upstream moreinfo quit Hi, Rares Aioanei wrote: Loading, please wait... /scripts/local-premount/resume : line 63 : /bin/resume : not found mount : mounting /dev/disk-by-uuid/uuid here on /root failed : no such file or directory [...] The error described can be also seen if compiling a vanilla kernel with the exact config as the Debian one (in my case 2.6.38.6) . I'm writing this from the same machine running 2.6.38.4 with a custom config and it works fine. Hope it helps. Could you attach a dmesg from the working configuration and the two .config files for comparison? What commands do you use to build and install a custom kernel? Does the custom configuration build in the disk driver (i.e., Y instead of M), and does it use an initramfs? Thanks for writing, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#627051: sdlgfx: New upstream version required by warmux
Package: src:sdlgfx Version: 2.0.20-1.1 Severity: important SDL_gfx 2.0.22 has been released some time ago. It is required by warmux 11.04 so it blocks updating the package. Please consider packaging the new version soon. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#627052: /usr/share/doc/git-doc/git-revert.html: Part of example command line is in subscript
Package: git-doc Version: 1:1.7.2.5-1 Severity: minor File: /usr/share/doc/git-doc/git-revert.html Second example for git revert is git revert -n master5..master2 with the part 5..master in subscript. I guess the following is meant git revert -n master~5..master~2 Similarly, in the HTML documentation of cherry-pick, the forth example is git cherry-pick master4 master2 with 4 master in subscript. Probably git cherry-pick master~4 master~2 is intended. Best wishes, Gábor Braun -- System Information: Debian Release: 6.0.1 APT prefers stable APT policy: (990, 'stable'), (650, 'testing'), (600, 'unstable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=hu_HU.UTF-8, LC_CTYPE=hu_HU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash git-doc depends on no packages. git-doc recommends no packages. Versions of packages git-doc suggests: ii git 1:1.7.2.5-1 fast, scalable, distributed revisi pn git-arch none (no description available) pn git-cvs none (no description available) pn git-emailnone (no description available) ii git-svn 1:1.7.2.5-1 fast, scalable, distributed revisi ii gitk 1:1.7.2.5-1 fast, scalable, distributed revisi pn gitweb 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#627053: approx update re-adds entry to inetd
Package: approx Version: 4.5-1+squeeze1 Severity: critical Hi, upgrading approx added the line 80 stream tcp nowait approx /usr/sbin/approx /usr/sbin/approx again to my /etc/inetd.conf, although i changed the line so it would only listen to only one ip (apache is used on the others). This breaks the unrelated web server software on the system (when the services are started in a way that allows inetd to listen before the other web servers), so i think critical is the correct severity level. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#624027: Fixed in VLC 1.2.0
tags 624027 + upstream fixed-upstream confirmed thanks Hello, I believe this bug is fixed in upstream VLC 1.2.0. Thanks you for your report. Best regards, -- Rémi Denis-Courmont http://www.remlab.net/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#627054: 404 Not Found status.html link on http://www.debian.org/mirror/
Package: www.debian.org Severity: normal On http://www.debian.org/mirror/ (at least the English and French versions), the http://mirror.debian.org/status.html link near the end gives a 404 Not Found error. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38-2-amd64 (SMP w/8 CPU cores) Locale: LANG=POSIX, LC_CTYPE=en_US.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#627055: linux-image-2.6.32: ipw2200 periodically stops transmitting packets, needs to be reinserted
Package: linux-2.6 Version: 2.6.32-31 Severity: normal File: linux-image-2.6.32 Every now and then when the network is stressed the interface just dies. Network manager displays flawless signal and connectivity but not as much as a ping will go out. If module is removed and reinserted normal operation resumes (until the next time this happens anyway). If Bittorrent is used, this occurs practically daily. -- Package-specific info: ** Version: Linux version 2.6.32-5-amd64 (Debian 2.6.32-31) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Mon Mar 7 21:35:22 UTC 2011 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-amd64 root=UUID=36a9a51f-5159-47e9-8d7e-6a36de6c8112 ro quiet ** Not tainted ** Kernel log: [157065.737187] ipw2200: No space for Tx [157065.737193] ipw2200: Failed to send SSID: Reason -16 [157100.772368] ipw2200: No space for Tx [157100.772374] ipw2200: Failed to send SCAN_REQUEST_EXT: Reason -16 [157135.799493] ipw2200: No space for Tx [157135.799500] ipw2200: Failed to send SSID: Reason -16 [157170.832089] ipw2200: No space for Tx [157170.832095] ipw2200: Failed to send SCAN_REQUEST_EXT: Reason -16 [157205.864129] ipw2200: No space for Tx [157205.864136] ipw2200: Failed to send SSID: Reason -16 [157240.897188] ipw2200: No space for Tx [157240.897194] ipw2200: Failed to send SCAN_REQUEST_EXT: Reason -16 [157275.928088] ipw2200: No space for Tx [157275.928095] ipw2200: Failed to send SSID: Reason -16 [157310.943645] ipw2200: No space for Tx [157310.943651] ipw2200: Failed to send SCAN_REQUEST_EXT: Reason -16 [157345.978819] ipw2200: No space for Tx [157345.978826] ipw2200: Failed to send SSID: Reason -16 [157380.992090] ipw2200: No space for Tx [157380.992096] ipw2200: Failed to send SCAN_REQUEST_EXT: Reason -16 [157416.024087] ipw2200: No space for Tx [157416.024094] ipw2200: Failed to send SSID: Reason -16 [157451.059262] ipw2200: No space for Tx [157451.059269] ipw2200: Failed to send SCAN_REQUEST_EXT: Reason -16 [157486.093468] ipw2200: No space for Tx [157486.093475] ipw2200: Failed to send SSID: Reason -16 [157521.128643] ipw2200: No space for Tx [157521.128650] ipw2200: Failed to send SCAN_REQUEST_EXT: Reason -16 [157556.139742] ipw2200: No space for Tx [157556.139749] ipw2200: Failed to send SSID: Reason -16 [157591.152098] ipw2200: No space for Tx [157591.152104] ipw2200: Failed to send SCAN_REQUEST_EXT: Reason -16 [157626.182914] ipw2200: No space for Tx [157626.182920] ipw2200: Failed to send SSID: Reason -16 [157661.213227] ipw2200: No space for Tx [157661.213235] ipw2200: Failed to send SCAN_REQUEST_EXT: Reason -16 [157696.244588] ipw2200: No space for Tx [157696.244595] ipw2200: Failed to send SSID: Reason -16 [157731.279769] ipw2200: No space for Tx [157731.279776] ipw2200: Failed to send SCAN_REQUEST_EXT: Reason -16 [157766.292088] ipw2200: No space for Tx [157766.292095] ipw2200: Failed to send SSID: Reason -16 [157801.326690] ipw2200: No space for Tx [157801.326697] ipw2200: Failed to send SCAN_REQUEST_EXT: Reason -16 [157836.361865] ipw2200: No space for Tx [157836.361872] ipw2200: Failed to send SSID: Reason -16 [157871.397039] ipw2200: No space for Tx [157871.397046] ipw2200: Failed to send SCAN_REQUEST_EXT: Reason -16 [157906.432358] ipw2200: No space for Tx [157906.432364] ipw2200: Failed to send SSID: Reason -16 [157941.467276] ipw2200: No space for Tx [157941.467283] ipw2200: Failed to send SCAN_REQUEST_EXT: Reason -16 [157976.502448] ipw2200: No space for Tx [157976.502455] ipw2200: Failed to send SSID: Reason -16 [158011.521417] ipw2200: No space for Tx [158011.521424] ipw2200: Failed to send SCAN_REQUEST_EXT: Reason -16 [158046.553186] ipw2200: No space for Tx [158046.553192] ipw2200: Failed to send SSID: Reason -16 [158081.588337] ipw2200: No space for Tx [158081.588343] ipw2200: Failed to send SCAN_REQUEST_EXT: Reason -16 [158116.623266] ipw2200: No space for Tx [158116.623272] ipw2200: Failed to send SSID: Reason -16 [158151.658443] ipw2200: No space for Tx [158151.658450] ipw2200: Failed to send SCAN_REQUEST_EXT: Reason -16 [158186.693193] ipw2200: No space for Tx [158186.693200] ipw2200: Failed to send SSID: Reason -16 [158221.716567] ipw2200: No space for Tx [158221.716573] ipw2200: Failed to send SCAN_REQUEST_EXT: Reason -16 [158256.736101] ipw2200: No space for Tx [158256.736108] ipw2200: Failed to send SSID: Reason -16 [158291.771273] ipw2200: No space for Tx [158291.771280] ipw2200: Failed to send SCAN_REQUEST_EXT: Reason -16 [158326.789357] ipw2200: No space for Tx [158326.789364] ipw2200: Failed to send SSID: Reason -16 [158361.820132] ipw2200: No space for Tx [158361.820138] ipw2200: Failed to send SCAN_REQUEST_EXT: Reason -16 [158396.848628] ipw2200: No space for Tx [158396.848634] ipw2200: Failed to send SSID: Reason -16 [158431.872185] ipw2200: No space for Tx [158431.872192] ipw2200: Failed to send SCAN_REQUEST_EXT: Reason -16 [158466.905740] ipw2200: No space for Tx [158466.905747] ipw2200: Failed to send SSID: Reason
Bug#627056: tzdata-java: Depends on tzdata=2011c-0squeeze1
Package: tzdata-java Severity: important tzdata-java depends on tzdata=2011c-0squeeze1, while tzdata=2011d-0squeeze1 is a security fix and the latest version available in squeeze This renders e.x. openjdk-6-jdk uninstallable. Fix: apt-get install openjdk-6-jdk tzdata=2011c-0squeeze1 But i think, then the security of the system is tainted. Best regards, Jörg -- System Information: Debian Release: 6.0.1 APT prefers stable APT policy: (990, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash :r -- Jörg Kurlbaum (j...@corsario.org) GPG-ID: CAC40EA9 Fingerprint: D4D4 9F5E D3C7 86B2 0D7F 67F9 9B22 7396 CAC4 0EA9 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#627022: wl-draft-reply triggers error
On May 16, 2011 at 7:27PM -0700, thompdump (at gmail.com) wrote: Package: wl-beta Version: 2.15.9+0.20100801-2 The problematic behavior: pressing 'A' while a message is selected in a 'Summary' buffer no longer facilitates composing a reply. Instead, wl-draft-reply triggers the error 'byte-code: Wrong type argument: stringp, (From)'. If L349, (message r-to-list), is commented out, the problematic behavior seems to be resolved (i.e., one can compose a reply to a message). In my wl/wl-draft.el, there isn't (message r-to-list), which seems to be your debugging code. Could you please reinstall the wl-beta package? # rm -rf /usr/share/emacs/site-lisp/wl # apt-get --reinstall install wl-beta Thanks, -- Tatsuya Kinoshita pgpscP8coq8tm.pgp Description: PGP signature
Bug#627057: [firmware-linux-nonfree] Please add new ralink firmware
Package: firmware-linux-nonfree Version: 0.29 Severity: wishlist Please add new nonfree firmware for ralink wifi cards. URL: http://www.ralinktech.com/support.php?s=2 License: * * Copyright (c) 2011, Ralink Technology Corporation All rights reserved. * * * * Redistribution. Redistribution and use in binary form, without modification, * * are permitted provided that the following conditions are met: * * * * -Redistributions must reproduce the above copyright notice and the following * * disclaimer in the documentation and/or other materials provided with the * * distribution. * * -Neither the name of Ralink Technology Corporation nor the names of its * * suppliers may be used to endorse or promote products derived from this * * software without specific prior written permission. * * -No reverse engineering, decompilation, or disassembly of this software is * * permitted. * * * * Limited patent license. Ralink Technology Corporation grants a world-wide, * * royalty-free, non-exclusive license under patents it now or hereafter owns * * or controls to make, have made, use, import, offer to sell and sell (Utilize) * * this software, but solely to the extent that any such patent is necessary to * * Utilize the software alone, or in combination with an operating system * * licensed under an approved Open Source license as listed by the Open Source * * Initiative at http://opensource.org/licenses. The patent license shall not apply * * to any other combinations which include this software. No hardware perse is * * licensed hereunder. * * * * DISCLAIMER. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND * * CONTRIBUTORS AS IS AND ANY EXPRESS OR IMPLIED WARRANTIES,INCLUDING, * * BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND * * FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE * * COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, * * INCIDENTAL,SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, * * BUT NOT LIMITED TO,PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;LOSS OF * * USE, DATA,OR PROFITS;OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON * * ANY THEORY OF LIABILITY,WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT * * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE * * OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. * ** I need Firmware RT28XX/RT30XX USB series (RT2870/RT2770/RT3572/RT3070), but you can add all on this page. Tested on my card: ID 0b05:1784 ASUSTek Computer, Inc. USB-N13 802.11n Network Adapter [Ralink RT2870] P.S. For download you need write you name and email and accept this license. P.P.S. This is close this my previous bug report too: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=616017 --- System information. --- Architecture: amd64 Kernel: Linux 2.6.38-2-amd64 -- Roman V. Nikolaev mail:rsha...@rambler.ru icq: 198-364-657 jabber: rsha...@jabber.org site:http://www.rshadow.ru signature.asc Description: OpenPGP digital signature
Bug#604687: vlc: xvideo output not working on powerbook (radeon video card, powerpc)
Hello, Unfortunately, I am unable to corroborate the vlc log and xvinfo output from your bug report. It seems VLC does not see the XVideo adapters at all. Normally, it should print plenty of messages in the log if it could not use a specific adapter, unless the X server returns protocol errors. Please make sure that xvideo-adaptors is set to -1. I guess this won't work. Then I'm afraid the only option is to step through the VLC code to figure out what is failing in xcb_xv.c (I don't have the same hardware, so I cannot do it myself). Best regards, -- Rémi Denis-Courmont http://www.remlab.net/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#627058: python-debian: deb822.GpgInfo.from_file is all broken
Package: python-debian Version: 0.1.18 Severity: normal Tags: patch Two problems with GpgInfo: 1. from_file calls from_sequence instead of GpgInfo.from_sequence, resulting in: File /usr/lib/pymodules/python2.6/debian/deb822.py, line 685, in from_file return from_sequence(file(target), *args) NameError: global name 'from_sequence' is not defined 2. from_sequence wants non-\n-terminated lines in the sequence, otherwise it sends bogus data to gpgv (thanks to the \n.join(sequence) sent to the pipe). the sequence returned by file(foo) has \n at the end of each line. Works a lot better with: diff --git a/lib/debian/deb822.py b/lib/debian/deb822.py index a0cad69..163fc5f 100644 --- a/lib/debian/deb822.py +++ b/lib/debian/deb822.py @@ -682,7 +682,7 @@ class GpgInfo(dict): @staticmethod def from_file(target, *args): Create a new GpgInfo object from the given file, calls from_sequence(file(target), *args) -return from_sequence(file(target), *args) +return GpgInfo.from_sequence(file(target).read(), *args) ### Although you might want to fix from_sequence instead. Incidentally it would be nice to be able to pass a list of keyrings to Deb822.get_gpg_info(). Cheers, Julien -- System Information: Debian Release: 6.0.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages python-debian depends on: ii python 2.6.6-3+squeeze6 interactive high-level object-orie ii python-chardet 2.0.1-1 universal character encoding detec ii python-support 1.0.10 automated rebuilding support for P Versions of packages python-debian recommends: ii python-apt0.7.100.1 Python interface to libapt-pkg Versions of packages python-debian suggests: ii gpgv 1.4.10-4 GNU privacy guard - signature veri -- 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#626851: linux-image-2.6.38-2-amd64: after last update fails to boot
On Tue, 17 May 2011 05:35:24 -0500 Jonathan Nieder jrnie...@gmail.com wrote: tags 626851 - moreinfo quit (cc-ing the bug log) Rares Aioanei wrote: I used the exact sequence of commands in building the working kernel and the non-working kernel; and yes, the disk driver is , of course, 'y', not built as a module. Was there a change in the config file in this last update? That's possible, but more likely the bug is in some specific driver that the working kernel does not use (or something like that). Thanks for the info. The reason for asking about built-in disk drivers is that the Debian kernel installs many drivers like that as modules that get loaded in the initramfs. One way to track this down might be to adapt chunks of the .config to more closely resemble the Debian kernel until it fails, and then pare it down until it succeeds again. Others may have better ideas. Regards, Jonathan My custom working config is just the Debian config stripped of unnecessary drivers (wireless, v4l, etc.). I guess I'll get help from my friend diff(1) and see if I can help further. Regards, -- Rares Aioanei -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#375179: /#394945: libxnvctrl and sensors-applet
Has there been any progress on these very old bugs? On Wednesday, 12. December 2007 12:01:25 Alex Murray wrote: The difference is that if hddtemp is not installed, the hddtemp module simply fails to run the hddtemp program. But if libXNVCtrl is not installed, the whole program will fail to load because of the missing shared library (assuming that libXNVCtrl even is a shared library... back when it was included in nvidia-settings it was only shipped as a static library). But libNVCtrl could be packaged separately (as it is GPL2) and sensors-applet could depend on it, then sensors-applet would load fine and it could all work as I described previously. There is now a separate libxnvctrl-dev package (in contrib) containing the headers and a static library - this stuff was not really suited to the nvidia-settings package. In case there are more things missing (more headers, another library, ... there might be some additional code available in the nvidia-settings source package), please let me know. If you need a shared library, a patch would be welcome, I never looked into the creation of shared libraries. I think we decided in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=434887 that that way to fix this is to make the various sensors-applet modules into DSOs that can be dlopen'd ... This has happened inbetween ... so someone needs to write a nvidia module for sensors-applet which needs to go into contrib ... On Tuesday, 24. October 2006 02:56:29 Sam Morris wrote: retitle -1 sensors-applet: libXNVCtrl can't read sensors of certain graphics cards So, it seems that libXNVCtrl can't read the sensors on our cards. I'm not sure about how best to contact upstream (NVIDIA) about this. Could you retry with the latest version of nvidia-settings (and libxnvctrl-dev) available in unstable? And if this does not work, try to look here: http://www.nvnews.net/vbulletin/showthread.php?t=46678 Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#567957: Wontfix
tag 567957 + upstream wontfix thanks Hello, By design, VLC can only handle UTF-8 encoded file names. To access file systems in other encoding, either the filesystem driver must do the conversion (a good option for VFAT especially), or the locale (LC_CTYPE or LANG) must be set to the corresponding encoding. This latter option will be removed in VLC 1.2. Debian and most Linux distributions defaults to UTF-8 and there are absolutely no plans to support anything else in VLC upstream. -- Rémi Denis-Courmont http://www.remlab.net/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#577257: Spaces in URL are not legal
tags 577257 + wontfix thanks Hello, As far as I can tell, there are no reasons why VLC would even need to bother about white spaces in URLs. URLs cannot contain white spaces by specification. White spaces in URLs should be encoded as %20. So to me, it looks like the bug lies in your file manager or whichever other application is parsing the vlc.desktop: That application is not passing syntactically valid URLs to VLC. Feel free to reassign to the correct package. Best regards, -- Rémi Denis-Courmont http://www.remlab.net/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#622935: Fixed in VLC 1.1.10
tags 622935 + upstream fixed-upstream thanks Hello, I believe I fixed this bug in upcoming VLC 1.1.10. Unfortunately, the DVD ISO auto-detection was a bit too relax and could fail positively on Ogg files with a low probability (but consistently on affected files). Best regards, -- Rémi Denis-Courmont http://www.remlab.net/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#626994: python-gtk2: fails to load with python2.7
* Jameson Graef Rollins jroll...@finestructure.net, 2011-05-16, 15:05: servo:~ 0 python2.7 -c import pygtk Traceback (most recent call last): File string, line 1, in module ImportError: No module named pygtk pygtk has been already rebuilt to add support for Python 2.7. However, for various reason the new binaries haven't migrated to testing yet. -- 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#620526: Removal of nvidia-graphics-drivers-legacy-71xx
On 2011-05-16 19:22, Russ Allbery wrote: Andreas Beckmann deb...@abeckmann.de writes: I would prefer to replace it with some transitional packages that, well, transition to ... a debconf note describing the situation. The current packages are not installable due to the Xorg conflict and so eventually were ignored by some people. That way they never got the cleanup process ran ... having some ancient files (buggy init scripts) remaining on their systems that could cause trouble in the future. That's an even better idea. Okay, I'll not do anything for the time being until we get a chance to do that. ... -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#627059: gpicview: segfault when using http url as parameter
Package: gpicview Version: 0.2.1-1+b1 Severity: normal Hi, gpicview segfaults when using http urls as parameter: $ gpicview http://www.google.de/images/logos/ps_logo2.png; (gpicview:8322): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_file_info: assertion `filename != NULL' failed (gpicview:8322): GdkPixbuf-CRITICAL **: gdk_pixbuf_animation_new_from_file: assertion `filename != NULL' failed zsh: segmentation fault gpicview http://www.google.de/images/logos/ps_logo2.png; -- Sebastian -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (100, 'unstable'), (50, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.39-rc6-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 gpicview depends on: ii libatk1.0-0 2.0.0-1 The ATK accessibility toolkit ii libc6 2.13-4 Embedded GNU C Library: Shared lib ii libcairo2 1.10.2-6 The Cairo 2D vector graphics libra ii libfontconfig1 2.8.0-2.2generic font configuration library ii libfreetype62.4.4-1 FreeType 2 font engine, shared lib ii libglib2.0-02.28.6-1 The GLib library of C routines ii libgtk2.0-0 2.24.4-3 The GTK+ graphical user interface ii libjpeg62 6b1-1The Independent JPEG Group's JPEG ii libpango1.0-0 1.28.3-6 Layout and rendering of internatio ii libx11-62:1.4.3-1X11 client-side library ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime Versions of packages gpicview recommends: ii xdg-utils1.1.0~rc1-2 desktop integration utilities from gpicview 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#627038: ITP: libacsccid -- PC/SC driver for ACS USB CCID smart card readers
Zitat von Godfrey Chung godfrey.ch...@acs.com.hk: Package: wnpp Severity: wishlist Owner: Godfrey Chung godfrey.ch...@acs.com.hk * Package name: libacsccid Version : 1.0.2 Upstream Author : Advanced Card Systems Ltd. i...@acs.com.hk * URL : http://www.acs.com.hk/ * License : LGPL-2.1 Programming Lang: C Description : PC/SC driver for ACS USB CCID smart card readers This library provides a PC/SC IFD handler implementation for the ACS USB smart card readers compliant to the CCID protocol. This package is needed to communicate with the ACS CCID smartcard readers through the PC/SC Lite resource manager (pcscd). Does libccid not work for your reader? If it doesn't, maybe reword the description about the differences to libccid (which should support CCID compliant devices). The URL above only links to the main page of the vendor. Can it be a bit more specific (the URL where you got the source from)? HS -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#626851: linux-image-2.6.38-2-amd64: after last update fails to boot
Rares Aioanei wrote: My custom working config is just the Debian config stripped of unnecessary drivers (wireless, v4l, etc.). I guess I'll get help from my friend diff(1) and see if I can help further. Excellent. Also, i'm starting to worry I misread what you wrote. :) So here's a summary: - packaged 2.6.38-4 worked ok - packaged 2.6.38-5 did not work ok - gregkh's 2.6.38.6 with .config from 2.6.38-5 did not work ok - gregkh's 2.6.38.4 with custom .config worked ok In particular, I had somehow confused myself into thinking that tested 2.6.38.4 with the Debian configuration failed or 2.6.38.6 with the custom .config worked ok, but rereading the bug log, I don't see that. Am I understanding correctly? If I am and the .config indeed seems to be a red herring, would you be willing to bisect between 2.6.38.4 and 2.6.38.5? I can guide you through the process if you'd like (and it probably would have been worth writing a patch for the kernel guide for that by now; sorry). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#447517: nvidia-settings: Overclocking Auto Detect never available
Hi Mikael, On Sunday, 21. October 2007 22:39:05 Mikael Åkersund wrote: Package: nvidia-settings Version: 1.0+20070502-1 After some major system upgrades (switching RAM sticks, motherboard, PSU, graphic cards and xservers) I found that nvidia-settings no longer could auto-detect the optimal overclocking frequencies. The Auto Detect button would always be greyed out even though I had enabled Coolbits in Xorg.conf In case you still have that machine (or a similar one), does the current version of nvidia-settings in unstable (270.41.06-1) still show this behavior? Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#624384: what is this a duplicate of?
I am trying to find out how to fix my VirtualBox install, and this matches my symptoms. Can you provide an indication of where I can find this other bug, please? Cheers God bless Sam SammyTheSnake Penny -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#558785: nvidia-settings: Detect Displayes doesn't update Display Configuration pane if external display is changed
On Monday, 30. November 2009 15:47:42 Chris AtLee wrote: Package: nvidia-settings Version: 185.18.31-1 Could you retry this with the current version of nvidia-settings (270.41.06-1)? Thanks Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#626851: linux-image-2.6.38-2-amd64: after last update fails to boot
On Tue, 17 May 2011 05:55:12 -0500 Jonathan Nieder jrnie...@gmail.com wrote: Rares Aioanei wrote: My custom working config is just the Debian config stripped of unnecessary drivers (wireless, v4l, etc.). I guess I'll get help from my friend diff(1) and see if I can help further. Excellent. Also, i'm starting to worry I misread what you wrote. :) So here's a summary: - packaged 2.6.38-4 worked ok - packaged 2.6.38-5 did not work ok - gregkh's 2.6.38.6 with .config from 2.6.38-5 did not work ok - gregkh's 2.6.38.4 with custom .config worked ok Yes, that is correct. In particular, I had somehow confused myself into thinking that tested 2.6.38.4 with the Debian configuration failed or 2.6.38.6 with the custom .config worked ok, but rereading the bug log, I don't see that. Am I understanding correctly? If I am and the .config indeed seems to be a red herring, would you be willing to bisect between 2.6.38.4 and 2.6.38.5? I can guide you through the process if you'd like (and it probably would have been worth writing a patch for the kernel guide for that by now; sorry). Yes, I could use some guidance. :-) -- Rares Aioanei -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#303662: nvidia-settings: Shows PCI bus as AGP
Hi David, On Friday, 8. April 2005 01:25:00 David Liontooth wrote: Package: nvidia-settings Version: 1.0+3-1 I run x-windows off an nVidia PCI card, but nvidia-settings claims it's AGP. It also sees the OS as Linux x86 when it's really GNU/Linux amd64. You probably don't have that system any longer. But just in case you do, could you try the current version of nvidia-settings (270.41.06-1) there and see if this was fixed inbetween? Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#590287: ALSA bug, now fixed
forcemerge 5595252 590287 600496 thanks Hello, These two bugs should be fixed by the recent ALSA-lib update in Debian Sid. Best regards, -- Rémi Denis-Courmont http://www.remlab.net/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#532320: nvidia-settings: Restoring settings automatically
Hi Tony, hi Ivan, just in case NVIDIA changed something, could you try the current version of nvidia-settings (270.41.06-1) from unstable? On Monday, 8. June 2009 15:34:02 Tony Houghton wrote: Package: nvidia-settings Version: 180.22-1 The man page explains how to use .xinitrc to automatically run nvidia-settings --load-config-only when X starts. AFAIK gdm etc don't use .xinitrc for a standard GNOME Session, KDE Session etc so that advice won't work for many people. Besides improving the documentation I think it would be a good idea to add an XDG autostart entry for nvidia-settings so inexperienced users don't have the bother of editing scripts or using the likes of gnome-session-manager. AFAICT running nvidia-settings --load-config-only in the absence of a .nvidia-settings-rc or even the NVidia driver merely fails silently, so I don't think this idea poses a danger for non-NVidia users. Patches would be welcome, both for documentation and for autostart scripts. On Saturday, 14. May 2011 01:33:08 Ivan Baldo wrote: Hello. This seems the right thing to do, if the user puts a special setting in the nvidia-settings program then it expects that setting to remain for the next reboot and not to have to load the program to apply the setting again. I use all default settings but anyway... Thanks for looking this. Have a nice day!!! At least there could be a button Save these settings as defaults or whatever. (I must admit, I'm packaging this, but I'm not actively using it) Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#410776: (pas de sujet)
tags 410776 + moreinfo thanks Hello, Bug #410776 looks like a memory corruption error in the VLC DTS decoder plugin. There have been a lot of VLC updates/fixes since you made the report, including to audio buffer management. Please retry with a newer version. If the bug still applies, please provide a valgrind trace of the failing VLC process. Thanks in advance, best regards, -- Rémi Denis-Courmont http://www.remlab.net/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#608043: software-properties-gtk: Fixed in sid
Package: software-properties-gtk Followup-For: Bug #608043 If it helps, this bug doesn't exist anymore in the current version in Debian sid. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.38-2-686 (SMP w/1 CPU core) Locale: LANG=pt_BR.utf8, LC_CTYPE=pt_BR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages software-properties-gtk depends on: ii gksu 2.0.2-5graphical frontend to su ii python2.6.6-14 interactive high-level object-orie ii python-gtk2 2.24.0-1 Python bindings for the GTK+ widge ii python-software-prope 0.76.7debian2+nmu1 manage the repositories that you i ii python2.6 2.6.6-10 An interactive high-level object-o ii synaptic 0.75.1 Graphical package manager software-properties-gtk recommends no packages. software-properties-gtk 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#612681: x11-common: treat empty session names silently as default session
On Mon, May 16, 2011 at 10:21:14PM +0200, Marko Macek wrote: On 05/16/2011 03:51 PM, Agustin Martin wrote: These are the .xsession-error messages for the failing icewm-session invocation from wdm (lines with AMD-WARNING are the extra info I requested) Xsession: X session started for testuser at Mon May 16 15:26:28 CEST 2011 Xsession: AMD-WARNING: Running /etc/X11/wdm/Xsession with arguments icewm-session Xsession: AMD-WARNING: Passing session as argument icewm-session /home/testuser/.Xresources:1:24: warning: missing terminating ' character /home/testuser/.Xresources:13:28: warning: missing terminating ' character Xsession: AMD-WARNING: starting /usr/bin/ssh-agent /usr/bin/ck-launch-session /usr/bin/dbus-launch --exit-with-session icewm-session icewm-session: using /home/testuser/.icewm for private configuration files IceWM: using /home/testuser/.icewm for private configuration files icewmtray: using /home/testuser/.icewm for private configuration files icewmbg: using /home/testuser/.icewm for private configuration files XIO: fatal IO error 104 (Connection reset by peer) on X server :0 after 205 requests (205 known processed) with 2 events remaining. XIO: fatal IO error 11 (Resource temporarily unavailable) on X server :0 after 110 requests (105 known processed) with 0 events remaining. XIO: fatal IO error 104 (Connection reset by peer) on X server :0 after 122 requests (122 known processed) with 0 events remaining. Invalid MIT-MAGIC-COOKIE-1 keyicewmbg: Can't open display: :0. X must be running and $DISPLAY set. Does the X server crash here? Any messages in Xorg log? I found a bug in X in Fedora that fails like this, might be the same. In my case seems that icewmbg is the one to blame, but still have to check before cloning #626331 and reassigning. Possible upstream bug report: http://sourceforge.net/tracker/?func=detailatid=100031aid=3289566group_id=31 Possible Ubuntu launchpad bug report: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/757610 If I have time today, I will try to reproduce the problem once again, but now looking more carefully at Xorg log. Regards, -- Agustin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#620958: your mail
found 620958 1.16.0.3 thanks On 2011-04-16 09:09:43 -0700, D. Kelly wrote: You can include me in the number of users who is now being spammed by all the warnings. I managed to get rid of quite a few of them with dpkg --clear-avail but I still get all the status ones. For example: Me too (for my old PowerBook). -- Vincent Lefèvre vinc...@vinc17.net - Web: http://www.vinc17.net/ 100% accessible validated (X)HTML - Blog: http://www.vinc17.net/blog/ Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#536659: closed by Rémi Denis-Courmont r...@remlab.net (Already fixed)
On 2011-05-17 12:54, Debian Bug Tracking System wrote: This is an automatic notification regarding your Bug report which was filed against the vlc package: #536659: Please enable midi support by depending on libfluidsynth1 It has been closed by Rémi Denis-Courmontr...@remlab.net. Their explanation is attached below along with your original report. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact Rémi Denis-Courmontr...@remlab.net by replying to this email. Hi Remi and thanks for your answer. I'm a FluidSynth developer myself and not aware of any current memory leak issues, and AFAIK it hasn't been reported on the fluid-dev mailinglist or ticket system, and does not seem to affect other users of libfluidsynth (or I assume we would have heard about it). In what form would you prefer we work together to resolve this memory leak issue? // David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#626641: cryptsetup: bug #587220 re-introduced
On Mon, 16 May 2011 22:35:12 -0300, Henrique de Moraes Holschuh h...@debian.org wrote: Then, 'stop' tries to close all managed crypto devices and aborts *with an error* if it cannot. 'Start' tries to open all managed crypto devices, and aborts *with an error* if it cannot. And 'restart' should not be supported, and return with the appropriate error, or it could just be stop+start. You likely don't want to run this on package upgrades. You'd still have to call 'stop' and abort the package removal in prerm [when removing the package. You will have to diferentiate the various reasons for why prerm is called] if it cannot close all crypto devices it manages. And 'start' on postinst, of course. I'm not totally sure why, but also don't like the idea calling these from the maintainer scripts. Especially (but I'm not sure on this) as it might ignore any non-crypttab-managed dm-crypt devices. Still, the IMHO best solution would be: - let any scripts fail with $? != 0 if the action they're expected to perform failed = this however does not comply with the crude Debian init-scripts policy AND - if cryptsetup is removed OR purged, give a big fat debconf-prio-low warning that devices a b c are still open, and cannot be closed using cryptsetup, if the user decides to continue. Then we've warned/instructed the interactive user and we've also secured any (clean[0]) script usage of the scripts within the cryptsetup package. Well, I think it is not appropriate to even let the package get removed in the first place if there are devices still open. This would make removal of the package impossible, if you e.g. use dm-crypt for the root-fs. Happy hacking, Chris. [0] Of course we cannot force any users to check the exit codes,.. but this is then really their fault. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#569531: More info
On mar., 2011-05-17 at 13:02 +0200, G. L. Gragnani wrote: On 05/17/11 10:06, Yves-Alexis Perez wrote: tag 569531 moreinfo thanks Hey, can you still reproduce using midori 0.3.6-1 in unstable? Regards, Yes, I can reproduce it. It is maybe related to wrong javascript code to deal with this kind of sites. Can you try with the webkit GtkLauncher (/usr/lib/webkit-1.0-2/libexec/GtkLauncher) and report back? Regards, -- Yves-Alexis -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#611452: xserver-xorg-core: switching to linux console leaves screen blank
Hello, is this issue still present with the 270.41.06-1 driver which is available in unstable? I just installed it and, yes, unfortunately it is still there. For a moment I thought its gone, because after X started and the startup screen of KDE is displayed I could still switch to the console. But after the KDE startup is finished I can no longer switch, or rather, I get the blank screen behind which the console might be hidden. Maybe this gives further insight in what might be the problem? E.g. some special graphics funcion enabled only after KDE is up and running. However, I don't have compositing enabled, which is the only thing that came to my mind... If I can help with any further checks, please tell me so. Cheers, Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#616156: VLC bookmark issue was fixed in 1.0.6/1.1.0
tags 616156 + moreinfo thanks Hello, As far as is known, the security issue you have reported against Debian VLC 1.1.3 was fixed in VLC 1.0.6 and 1.1.0. I am not able to reproduce the problem with the linked sample exploit file. Are you sure the problem actually exists with the specified version? What exploit file did you use? Best regards, -- Rémi Denis-Courmont http://www.remlab.net/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#627025: perl: data loss in output when both stdout and stderr are redirected to a pipe
This may be a regression, as I cannot reproduce this problem on a Debian/lenny machine, still with a local repository, but a different one. However the environment is rather different, and since the bug may be due to a race condition, one cannot draw a definitive conclusion. -- Vincent Lefèvre vinc...@vinc17.net - Web: http://www.vinc17.net/ 100% accessible validated (X)HTML - Blog: http://www.vinc17.net/blog/ Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#626641: [pkg-cryptsetup-devel] Bug#626641: cryptsetup: bug #587220 re-introduced
On Mon, 16 May 2011 22:25:45 -0300, Henrique de Moraes Holschuh h...@debian.org wrote: Because the initscript returned status 0 when there were still cryptsetup-managed dm-crypt devices active? If it does that, it is broken. AFAIU just this happens right now. Because the package allowed itself to be uninstalled while the initscript was returning an error? If it does that, it is broken IMO. I think cryptsetup is special here,... and successful stopping is quite likely not to work during uninstall (e.g. dm-crypted root-fs). We shouldn't call this from the maintainer scripts. Because the initscript returned status 0 when there were NO cryptsetup-managed dm-crypt devices, but some other sort of dm-crypt device? The user should have known better. Actually I'm not sure on how /etc/init.d/cryptdisks and -early are intended with respect to this. Jonas, should they also handle (i.e. close) any unmanaged dm-crypt devices? Wouldn't be to bad, if stopping is just tried for any open device e.g. on shutdown, would it? The conffile issue is not going to change, ever. Our respect for the local administrator during package upgrades It is one of the major things that sets Debian apart from the rest. Honestly I don't see how this gives or takes freedom. Of course there are always people that wanna change anything, but then... what's the big difference between e.g. the crpytsetup initscripts and cryptdisk.funcitons? Both scripts, both handle cryptdisks, but we give the former special status as confile and not the later. I know this discussion doesn't belong here... but init-scripts are IMHO just code and especially not configuration. If the script is well written, it can be fully configured via /etc/defaults/fooo If this is not enough for an admin he should need to take care himself, also on updates. This is as we already handle ALL other scripts which were simply not put in /etc/init.d. Taking myself as an example, I've forked my own personal cryptsetup package due to several concerns... and I also modify some non-/etc/init.d/ scripts there,... if I change them,.. it's my responsibility to take care of them. Note that I am against cryptsetup allowing itself to be removed while devices *it manages* are still open in the first place. The more I think about it... the more I could like the idea,... but ONLY if it refuses to be removed if *any* dm-crypt device is still open. We really shouldn't make different grades of devices where one handled more important than the other. Cheers, Chris. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#627025: perl: data loss in output when both stdout and stderr are redirected to a pipe
On Tue, May 17, 2011 at 01:34:27PM +0200, Vincent Lefevre wrote: This may be a regression, as I cannot reproduce this problem on a Debian/lenny machine, still with a local repository, but a different one. However the environment is rather different, and since the bug may be due to a race condition, one cannot draw a definitive conclusion. Thanks for letting us know. My next question (not yet having had time to do any detailed analysis of the issue) would be whether it can be reproduced on squeeze (or even better, pre-5.12 sid/wheezy, but that's probably rather awkward to set up now). Cheers, Dominic. -- Dominic Hargreaves | http://www.larted.org.uk/~dom/ PGP key 5178E2A5 from the.earth.li (keyserver,web,email) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#626641: [pkg-cryptsetup-devel] Bug#626641: cryptsetup: bug #587220 re-introduced
Hey, On 17/05/2011 Christoph Anton Mitterer wrote: On Mon, 16 May 2011 22:35:12 -0300, Henrique de Moraes Holschuh h...@debian.org wrote: Then, 'stop' tries to close all managed crypto devices and aborts *with an error* if it cannot. 'Start' tries to open all managed crypto devices, and aborts *with an error* if it cannot. And 'restart' should not be supported, and return with the appropriate error, or it could just be stop+start. You likely don't want to run this on package upgrades. You'd still have to call 'stop' and abort the package removal in prerm [when removing the package. You will have to diferentiate the various reasons for why prerm is called] if it cannot close all crypto devices it manages. And 'start' on postinst, of course. I'm not totally sure why, but also don't like the idea calling these from the maintainer scripts. Especially (but I'm not sure on this) as it might ignore any non-crypttab-managed dm-crypt devices. Well, I think it is not appropriate to even let the package get removed in the first place if there are devices still open. This would make removal of the package impossible, if you e.g. use dm-crypt for the root-fs. I disagree with Henrique here. Christoph is right: It's a bad idea do start/stop the cryptdisks initscript from debian maintainer scripts. This is for several reasons: - cryptsetup is not the only userspace tool which manages dm-crypt devices. Low-level tools like dmsetup, udev, hal; commandline tools like cryptmount and gui applications like gnome-mount etc. might unlock/lock encrypted devices as well. - the cryptdisks initscript only manages dm-crypt devices which are listed in the crypttab. Therefore otherwise unlocked devices are ignored. - for most setups, the solution that Henrique suggested, would mean that cryptsetup fails to be removed/purged. usualle the unlocked dm-crypt devices are mounted if the system is running, maybe even as root filesystem. Still, the IMHO best solution would be: - let any scripts fail with $? != 0 if the action they're expected to perform failed = this however does not comply with the crude Debian init-scripts policy Sorry Christoph, but this is simply not an option. AND - if cryptsetup is removed OR purged, give a big fat debconf-prio-low warning that devices a b c are still open, and cannot be closed using cryptsetup, if the user decides to continue. At the moment I consider this as the best solution. Greetings, jonas signature.asc Description: Digital signature
