Bug#1027762: Regression Pipewire 0.63 breaks underruns breaking emacspeak accessibility
I tested your supplied code with Pipewire 0.3.63-1, and reproduced the bug.
Bug#1026356: Cannot configure Neomutt to use gssapi/kerberos for SMTP
Package: neomutt Version: 20220429+dfsg1-4.1 If my .muttrc configuration includes the line: set smtp_authenticators="gssapi" then Neomutt gives an error on startup while processing the configuration file, citing the above line: "Option smtp_authenticators: gssapi is not a valid authenticator". It correctly authenticates to the server via IMAP with Kerberos/gssapi. Furthermore, Mutt (i.e., from the Mutt package) correctly processes the above configuration. If I recall correctly (and I don't have a system available for checking at the moment), the Neomutt package under Arch Linux, which is probably closer to upstream, does not have this bug; it may be Debian-specific.
Bug#747701: libgl1-mesa-dri: Broken by upgrade to libllvm3.4 1:3.4.1-1
Package: libgl1-mesa-dri Version: 10.1.2-1 Severity: normal ld /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so gives the following: /usr/bin/ld.bfd.real: warning: libLLVM-3.4.so.1, needed by /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so, not found Can you recompile/relink with libLLVM-3.4.1.so.1? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#743155: libcore-ocaml: Cannot be installed under Sid
Package: libcore-ocaml Version: 107.01-5 Severity: normal The following packages have unmet dependencies: libcore-ocaml : Depends: ocaml-base-nox-3.12.1 which is a virtual package. Upon trying to install libcore-ocaml-dev I get these additional dependency issues: The following packages have unmet dependencies: libcore-ocaml-dev : Depends: libbin-prot-camlp4-dev-gt3f4 which is a virtual package. Depends: libcore-ocaml-y9832 which is a virtual package. Depends: libfields-camlp4-dev-kk6t0 which is a virtual package. Depends: libres-ocaml-dev-08mm3 which is a virtual package. Depends: libsexplib-camlp4-dev-nwls8 which is a virtual package. Depends: ocaml-nox-3.12.1 which is a virtual package. I think the package should be brought up to date from upstream and with the dependencies resolved. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#739188: gnome-orca: python-speechd is gone
Paul Gevers wrote: > On 22-02-14 20:07, Emilio Pozuelo Monfort wrote: > > And we can revert the Orca change and keep binding orca+q to quit > > orca (that's a one-liner patch). Or leave it as is (as super+alt+s > > does that too) and see if we hear any complaints. Thoughts? > > I don't have any strong opinion on that. Leave as is seems fine with me, > but maybe somebody on the list has an opinion? I think users would find super+alt+s very helpful to start Orca. There are few situations in which an Orca user, who is relying on it to access the desktop environment, would wish to quit Orca at all. Note that you can turn off speech, for example, while still leaving Orca running. Thus I think the ability to invoke Orca conveniently at any time is the most valuable functionality, and the "quit" command, while still desirable, would be less frequently used. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#637652: dotconf: New upstream version 1.3 available
Luke Yelavich wrote: > On Mon, Oct 28, 2013 at 03:44:19PM PDT, Jason White wrote: > > If you can, I would suggest moving this into a Git repository. > > Sure can do, just not sure where to host it. I don't have a github account > and don't plan to get one, and the package is not technically an > accessibility team package at the moment, so I could put it up on my own > webspace for now. perhaps it would be best to wait until the issue of maintenance is sorted out in Debian in that case - still no response from the current package maintainer. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#637652: dotconf: New upstream version 1.3 available
It compiled and installed here with your latest patch applied. Thanks. Jason. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#637652: dotconf: New upstream version 1.3 available
Luke Yelavich wrote: > On Mon, Oct 28, 2013 at 03:20:36PM PDT, Luke Yelavich wrote: > > here is a patch based on jason's work, with some more improvements. This > > patch applies against the current dotconf packaging in Debian unstable. > > > > Jason, if you could possibly test this on your system, that would be > > appreciated, as I currently don't have an unstable system set up right now. > > Here is an updated patch. I forgot to document one of the changes I made in > the changelog. The patch file you sent lists the file names you changed but lacks the diffs themselves. Could you take another look? If you can, I would suggest moving this into a Git repository. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#726865: consolekit: Reports errors when switching between virtual terminals under systemd
Package: consolekit Version: 0.4.6-3+b1 Severity: normal I'm running systemd under unstable, with all packages up to date. Whenever I switch between virtual consoles I get this error in syslog: Oct 20 09:34:36 jdc console-kit-daemon[2888]: (process:6803): GLib-CRITICAL **: g_slice_set_config: assertion `sys_page_size == 0' failed Also, from what I've read, systemd supersedes consolekit, but it's still running in my configuration and I'm not sure whether to disable it at this point or whether other configuration changes are necessary. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.10-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages consolekit depends on: ii dbus 1.6.16-1 ii libacl12.2.52-1 ii libc6 2.17-93 ii libck-connector0 0.4.6-3+b1 ii libdbus-1-31.6.16-1 ii libdbus-glib-1-2 0.100.2-1 ii libglib2.0-0 2.36.4-1 ii libpolkit-gobject-1-0 0.105-4 ii libudev1 204-5 ii libx11-6 2:1.6.2-1 ii zlib1g 1:1.2.8.dfsg-1 Versions of packages consolekit recommends: ii libpam-ck-connector 0.4.6-3+b1 consolekit 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#726783: Add support for systemd
Package: brltty Version: 4.5-3+b1 Severity: normal Tags: patch User: pkg-systemd-maintain...@lists.alioth.debian.org Usertags: systemd-units X-Debbugs-CC: pkg-systemd-maintain...@lists.alioth.debian.org BRLTTY includes a systemd service file, which is currently not installed by the Debian package. Furthermore, the upstream version of this file has improvements over the version included in the BRLTTY 4.5 source, and additional changes were necessary for the Debian environment (the path and command line options of the executable, most notably). I have included a revised version as debian/brltty.service. Here is a patch. Review and improvements are most welcome. >From ca26011b0b4a7eef89e48c5d68f7bbab7f1c54c3 Mon Sep 17 00:00:00 2001 From: Jason White Date: Sat, 19 Oct 2013 18:03:31 +1100 Subject: [PATCH] Add systemd service. --- debian/brltty.service | 30 ++ debian/changelog | 8 ++-- debian/control| 2 +- debian/rules | 3 +++ 4 files changed, 40 insertions(+), 3 deletions(-) create mode 100644 debian/brltty.service diff --git a/debian/brltty.service b/debian/brltty.service new file mode 100644 index 000..a856712 --- /dev/null +++ b/debian/brltty.service @@ -0,0 +1,30 @@ +[Unit] + +Description=Braille Device Support +Documentation=man:brltty(1) +Documentation=http://mielke.cc/brltty/ + +DefaultDependencies=no +Before=sysinit.target + + +[Service] + +Type=forking +PIDFile=/run/brltty.pid +ExecStart=/sbin/brltty -q -P /run/brltty.pid + +TimeoutStartSec=5 +TimeoutStopSec=10 + +Restart=always +RestartSec=30 + +Nice=-10 +OOMScoreAdjust=-900 + + +[Install] +WantedBy=sysinit.target + + diff --git a/debian/changelog b/debian/changelog index c145a5b..8c31e1a 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,10 +1,14 @@ + [ Samuel Thibault ] * control: - Make python*-brlapi description more explict. - Bump Standards-Version to 3.9.4 (no changes). - -- Samuel Thibault Sun, 23 Jun 2013 21:07:45 +0200 + [ Jason White ] + * Add support for systemd (based on upstream service file). + + -- Jason White Sat, 19 Oct 2013 17:15:54 +1100 brltty (4.5-3) unstable; urgency=low diff --git a/debian/control b/debian/control index 1401a8b..83e26e3 100644 --- a/debian/control +++ b/debian/control @@ -6,7 +6,7 @@ Uploaders: Mario Lang , Samuel Thibault Vcs-Browser: http://git.debian.org/?p=pkg-a11y/brltty.git;a=summary Vcs-Git: git://git.debian.org/git/pkg-a11y/brltty.git Homepage: http://mielke.cc/brltty/ -Build-Depends: debhelper (>= 7), dh-lisp, +Build-Depends: debhelper (>= 7), dh-lisp, dh-systemd (>= 1.5), autotools-dev, autoconf, tcl (>= 8.5~), libasound2-dev [linux-any], python-all-dev (>= 2.7~0), diff --git a/debian/rules b/debian/rules index 953d619..767fbca 100755 --- a/debian/rules +++ b/debian/rules @@ -143,8 +143,11 @@ brltty: build-brltty build-python for file in Drivers/Braille/*/README*; \ do cp $$file `pwd`/debian/$(PACKAGE)/usr/share/doc/brltty/`basename $$(dirname $$file)`.`basename $$file`; \ done + dh_systemd_enable -p$@ # -r because we don't want to lose the console on an upgrade dh_installinit -p$@ -r -- start 25 S . + # and likewise for systemd + dh_systemd_start -p$@ --restart-after-upgrade dh_installchangelogs Documents/ChangeLog dh_installman dh_lintian -- 1.8.4.rc3 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#637652: dotconf: New upstream version 1.3 available
I have made progress toward updating the package to 1.3. Attached is a diff of
the changes made to files in the debian directory, which are documented in the
changelog.
I can now build the package based on the upstream Git repository. (Note that
there is no upstream tar file, but gbp buildpackage can be used to perform the
build).
I have also attempted to address warnings identified by Lintian. The only
significant warning that I haven't resolved is:
libdotconf1.3: package-name-doesnt-match-sonames libdotconf0
I've tried to follow the Debian policy manual in renaming the library package
(made necessary in any case by the version number in the original name).
I'm sure I have made mistakes along the way, thus I would appreciate review of
these changes, so the maintainer can consider them and decide which to
incorporate in the next release.
diff --git a/debian/changelog b/debian/changelog
index c2312a4..76194e8 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,19 @@
+dotconf (1.3~git651d87f-1) UNRELEASED; urgency=low
+
+ * New upstream release. (Closes: #637652)
+ * Add multi-arch support.
+ * Create a package for debugging symbols.
+ * Convert the character encoding of the copyright file to UTF8.
+ * Add copyright notice (in required form) to copyright file
+and identify the current upstream source.
+ * Update dependencies.
+ * Remove dotconf-config(1) manual page as dotconf-config no longer
+exists.
+ * Specify source format as 3.0 (quilt).
+ * Update standards-version to 3.9.4.
+
+ -- Jason White Tue, 30 Jul 2013 10:49:17 +1000
+
dotconf (1.0.13-3) unstable; urgency=low
* Correctly make use of realloc, to prevent applications using dotconf from
diff --git a/debian/compat b/debian/compat
index b8626c4..ec63514 100644
--- a/debian/compat
+++ b/debian/compat
@@ -1 +1 @@
-4
+9
diff --git a/debian/control b/debian/control
index 3611593..4c1b1e4 100644
--- a/debian/control
+++ b/debian/control
@@ -2,14 +2,14 @@ Source: dotconf
Section: libs
Priority: optional
Maintainer: Shane Wegner
-Build-Depends: debhelper (>> 4.0.0)
-Standards-Version: 3.5.8
+Build-Depends: debhelper (>= 9), dh-autoreconf
+Standards-Version: 3.9.4
Package: libdotconf-dev
Architecture: any
Section: libdevel
Priority: extra
-Depends: libdotconf1.0 (= ${Source-Version}), libc6-dev
+Depends: ${misc:Depends}, libdotconf1.3-0 (= ${binary:Version}), libc6-dev
Description: Configuration file parser library - development files
dot.conf is a simple-to-use and powerful configuration-file parser
library written in C. The configuration files created for dot.conf
@@ -24,11 +24,13 @@ Description: Configuration file parser library - development files
This package contains the development files necessary to build
programs using the dotconf library.
-Package: libdotconf1.0
+Package: libdotconf1.3-0
Architecture: any
+Multi-arch: same
Section: libs
Priority: optional
-Depends: ${shlibs:Depends}
+Depends: ${misc:Depends}, ${shlibs:Depends}
+Pre-Depends: multiarch-support
Description: Configuration file parser library - runtime files
dot.conf is a simple-to-use and powerful configuration-file parser
library written in C. The configuration files created for dot.conf
@@ -39,3 +41,24 @@ Description: Configuration file parser library - runtime files
configuration options on-the-fly, a here-documents feature to pass
very long ARG_STR data to your app, and on-the-fly inclusion of
additional config files.
+
+Package: libdotconf1.3-dbg
+Architecture: any
+Multi-arch: same
+Section: debug
+Priority: extra
+Depends: ${misc:Depends}, ${shlibs:Depends}, libdotconf1.3-0 (= ${binary:Version})
+Pre-Depends: multiarch-support
+Description: Configuration file parser library - runtime files
+ dot.conf is a simple-to-use and powerful configuration-file parser
+ library written in C. The configuration files created for dot.conf
+ look very similar to those used by the Apache Webserver. Even
+ Container-Directives known from httpd.conf can easily be used in the
+ exact same manner as for Apache-Modules. It supports various types of
+ arguments, dynamically loadable modules that create their own
+ configuration options on-the-fly, a here-documents feature to pass
+ very long ARG_STR data to your app, and on-the-fly inclusion of
+ additional config files.
+ .
+ This package contains the debugging symbols for libdotconf.
+
diff --git a/debian/copyright b/debian/copyright
index 4f367ab..f99e50e 100644
--- a/debian/copyright
+++ b/debian/copyright
@@ -2,12 +2,14 @@ This package was debianized by Shane Wegner on
Thu, 20 Jan 2000 23:50:36 -0800.
It was downloaded from http://www.azzit.de/dotconf/
+version 1.3 was obtained at git://github.com/williamh/dotconf.git
-Upstream Author: lukas schröder
+Original Upstream Author: lukas schröder
+Current Upstream Maintainer: William Hubbs
-Copyright:
+Copyright 1999,2000,2001,2002 Lukas Schroeder , and others.
-You are free to distri
Bug#637652: dotconf: New upstream version 1.3 available
Package: libdotconf-dev Version: 1.0.13-3 Followup-For: Bug #637652 It's available at git://github.com/williamh/dotconf.git There have been a few small bug fixes since the 1.3 release, so we probably want the latest version from the master branch rather than the tagged release. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#712629: espeak: fails to speak final chunk
Sam Hartman wrote: > Hi. I noticed that espeak as an emacspeak speech server is basically > unusable if you're using pulse, which is kind of the default > configuration in wheezy. I have just tested this. Whether or not the patch is applied (i.e., before and after upgrading to the package recently uploaded to Sid), the speech output breaks up into fragmentary syllables and takes a long time to catch up whenever it is interrupted. This did not occur under Alsa in the absence of Pulse. To reproduce, start Emacspeak with the Espeak speech server and note that the startup messages are garbled. Then, read a line of text without interrupting the speech (C-n and C-p in the buffer for example). This should speak the entire line correctly. To reproduce the issue, try moving up and down through lines of text quickly. The speech should be cancelled as soon as a key is typed, but instead we hear fragments of text for a number of seconds thereafter. I'm using a straightforward USB audio headset for this test. I normally run Emacspeak with the DECTalk Express so I haven't used the Espeak server a lot. When I last looked at it, I noticed that in the Espeak pulse driver the code to flush the buffer was commented out - it obviously could be related. I think I'm describing a separate bug; I can submit a report if you wish. My suggestion: if anyone can reproduce this it can be sent upstream. I'm also in a position to run gdb on it if there's anything you would like me to check further. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#707912: espeak: the AUDIO=runtime compilation ption does not invoke PulseAudio as intended
The problem turned out to be that we were building libespeak.a without AUDIO=runtime enabled, as required for the debian installer according to the Git history. We then built the shared library with AUDIO=runtime set, but the object files weren't regenerated. Here's a proposed patch for this. Anyone with a better solution is welcome to offer it. >From d47ee05d303762567f27c4aae2729d297c52f0f5 Mon Sep 17 00:00:00 2001 From: Jason White Date: Tue, 14 May 2013 10:33:51 +1000 Subject: [PATCH] Rebuild object files with AUDIO=runtime after building static library without it. --- debian/rules | 3 +++ 1 file changed, 3 insertions(+) diff --git a/debian/rules b/debian/rules index 8b38a4b..1afb1a7 100755 --- a/debian/rules +++ b/debian/rules @@ -32,6 +32,9 @@ build-stamp: cp src/portaudio19.h src/portaudio.h cd src && CXXFLAGS="$(CXXFLAGS) $(CFLAGS)" $(MAKE) DATADIR=$(ESPEAK_DATA)/espeak-data libespeak.a + # Remove object files so we can rebuild them with + # AUDIO=runtime enabled + rm -f src/*.o cd src && CXXFLAGS="$(CXXFLAGS) $(CFLAGS)" $(MAKE) DATADIR=$(ESPEAK_DATA)/espeak-data espeak AUDIO=runtime # Build static speak binary -- 1.8.1.3 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#707925: espeak: Makefile overrides compiler flags from the environment
Luke Yelavich wrote: > tags 707925 pending Still need to revert 8325799240b78caa949697860fb1c43a8d0fa814 the newer patch supersedes the one I sent with the bug report. Thanks. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#707925: Makefile overrides compiler flags from the environment
Here's a simpler patch for this. >From 039e1c575d547617a22ef041c2b046f765917f46 Mon Sep 17 00:00:00 2001 From: Jason White Date: Mon, 13 May 2013 09:54:46 +1000 Subject: [PATCH] Pass compiler flags on make command line so they won't be ignored. --- debian/rules | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/debian/rules b/debian/rules index 8b38a4b..ebea9b8 100755 --- a/debian/rules +++ b/debian/rules @@ -31,8 +31,8 @@ build-stamp: dh_testdir cp src/portaudio19.h src/portaudio.h - cd src && CXXFLAGS="$(CXXFLAGS) $(CFLAGS)" $(MAKE) DATADIR=$(ESPEAK_DATA)/espeak-data libespeak.a - cd src && CXXFLAGS="$(CXXFLAGS) $(CFLAGS)" $(MAKE) DATADIR=$(ESPEAK_DATA)/espeak-data espeak AUDIO=runtime + cd src && $(MAKE) CXXFLAGS="$(CXXFLAGS) $(CFLAGS)" DATADIR=$(ESPEAK_DATA)/espeak-data libespeak.a + cd src && $(MAKE) CXXFLAGS="$(CXXFLAGS) $(CFLAGS)" DATADIR=$(ESPEAK_DATA)/espeak-data espeak AUDIO=runtime # Build static speak binary cd platforms/big_endian && CFLAGS="$(CFLAGS)" $(MAKE) -- 1.8.1.3 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#707912: espeak: the AUDIO=runtime compilation ption does not invoke PulseAudio as intended
Reece Dunn wrote: > Are you sure the AUDIO=runtime flags are being set during the build? > > In line 30 of src/Makefile, espeak sets AUDIO=portaudio. This could be > overriding the AUDIO setting like CXXFLAGS were being overrided in bug > #707925. > > If AUDIO=runtime is built correctly, both wave.cpp and wave_pulse.cpp > should be compiled and -DUSE_PULSEAUDIO -DUSE_PORTAUDIO should be passed to > the compiler (see lines 37-39). Yes, indeed, and that's exactly what I see in the output of make during the compilation. It appears that variables specified on the make command line are treated differently from those brought in from the environment. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#707912: espeak: the AUDIO=runtime compilation ption does not invoke PulseAudio as intended
Having built with debug symbols, I can confirm this bug: we're invoking PortAudio even when Pulse is active. Maybe the best solution at this point would be to ask upstream to sort out the code in src/wave.cpp. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#707925: espeak: Makefile overrides compiler flags from the environment
Package: espeak Version: 1.47.07-1 Severity: normal This is the latest Espeak package from the Git repository (not yet uploaded). The makefile overrides CXXFLAGS, hence the flags supplied by debian/rules are never applied. In particular, debug symbols are not generated. Here's a proposed patch. >From cf92768d5d2a46dd3f253eacd82e577fcec9753d Mon Sep 17 00:00:00 2001 From: Jason White Date: Sun, 12 May 2013 18:10:40 +1000 Subject: [PATCH] Don't override compiler flags from the environment in Makefile. --- debian/patches/compiler-flags | 13 + debian/patches/series | 1 + 2 files changed, 14 insertions(+) create mode 100644 debian/patches/compiler-flags diff --git a/debian/patches/compiler-flags b/debian/patches/compiler-flags new file mode 100644 index 000..efe1add --- /dev/null +++ b/debian/patches/compiler-flags @@ -0,0 +1,13 @@ +Index: espeak/src/Makefile +=== +--- espeak.orig/src/Makefile 2013-05-12 17:08:13.919581196 +1000 espeak/src/Makefile2013-05-12 17:13:29.755725063 +1000 +@@ -93,7 +93,7 @@ + OBJS3=$(patsubst %.cpp,%.o,$(SRCS3)) + LIBS3=-lstdc++ -L . -lespeak + +-CXXFLAGS=-O2 ++CXXFLAGS?=-O2 + + + all: $(BIN_NAME) $(LIB_NAME) $(STATIC_LIB_NAME) $(BIN2_NAME) diff --git a/debian/patches/series b/debian/patches/series index 9c398d1..60983b0 100644 --- a/debian/patches/series +++ b/debian/patches/series @@ -1 +1,2 @@ +compiler-flags sonic -- 1.8.1.3 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#707912: espeak: the AUDIO=runtime compilation ption does not invoke PulseAudio as intended
Package: espeak Version: 1.47.07-1 Severity: normal This might explain some of the issues that people have been experiencing with ESpeak lately. Debian properly enables the AUDIO=runtime compilation option, but gdb shows that even when PulseAudio is running on my system, PortAudio functions (e.g., Pa_Initialize()) are invoked. If ALSA is configured to invoke PulseAudio anyway (the default under Debian with PA installed), Alsa issues warnings about underruns on my system. I've looked at the preprocessor directives in src/wave.cpp of ESpeak and it isn't clear how this is supposed to work; it seems to me that the wrappers may not be applied as the author intended. I'm going to rebuild this with proper debugging information and investigate further. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#707196: Activate software speech synthesiser in KDE too (for desktop=kde installs)?
Jude DaShiell wrote: > >From what I understand, kde offers ktts and jovie. I don't know that > the combination constitutes a full screen reader solution though and it > may not be feasible to extend espeakup into kde. The plan, so far as I understand it, was ultimately to use Orca to make KDE accessible. However, this is still very much work in progress on the KDE side, with support for AT-SPI now integrated into QT. I don't think it would be a good idea to support it as an installer option until it's actually usable. I'm not sufficiently aware of the current status to know when this is likely to happen, other than that the AT-SPI support was merged into QT 5, to which KDE will be upgraded. (Prior to QT 5, you need to install the qt-at-spi package and set an environment variable.) I don't know how much work needs to be done to make the desktop compatible with QT accessibility interfaces and hence with AT-SPI. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#706771: gnome-orca: Shutdown manu in Debian 7 is inaccessible
Jann Schneider wrote: > I cannot read the shutdown options in Debian 7 RC2. When i use my users menu > in the top menu, navigate down to shutdown and press enter, i can't read > anything more. Neither speech or braille is giving anymore output. Usually i > just press enter again to shutdown the computer. But there is no > possibility to choose reboot or what else is displayed in this dialog. If I remember correctly, this is known to be a missing accessibility feature in Gnome-Shell 3.4 that was fixed in later versions. I can't remember whether it was corrected for Gnome 3.6 or 3.8. I think there were changes made to Orca as well. My advice would be to wait until Gnome 3.8 enters unstable or testing, then upgrade. Many accessibility improvements have been made since Gnome 3.4. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#691904: lynx-cur: Fails to resolve certain hosts
Package: lynx-cur Version: 2.8.8dev.14-1 Severity: normal Here is an example: Script started on Wed 31 Oct 2012 19:09:38 EST jason@jdc:~$ lynx http://code.google.com Looking up code.google.com Unable to locate remote host code.google.com. Alert!: Unable to connect to remote host. lynx: Can't access startfile http://code.google.com/ jason@jdc:~$ host code.google.com code.google.com is an alias for code.l.google.com. code.l.google.com has address 74.125.237.4 code.l.google.com has address 74.125.237.5 code.l.google.com has address 74.125.237.6 code.l.google.com has address 74.125.237.7 code.l.google.com has address 74.125.237.8 code.l.google.com has address 74.125.237.9 code.l.google.com has address 74.125.237.14 code.l.google.com has address 74.125.237.0 code.l.google.com has address 74.125.237.1 code.l.google.com has address 74.125.237.2 code.l.google.com has address 74.125.237.3 code.l.google.com has IPv6 address 2404:6800:4006:800::1007 jason@jdc:~$ If I visit the same URL with w3m, Iceweasel, etc., all is fine. IPv6 is enabled here and: jason@jdc:~$ ping6 -c 5 code.google.com PING code.google.com(2404:6800:4006:800::1002) 56 data bytes 64 bytes from 2404:6800:4006:800::1002: icmp_seq=1 ttl=55 time=43.4 ms 64 bytes from 2404:6800:4006:800::1002: icmp_seq=2 ttl=56 time=44.3 ms 64 bytes from 2404:6800:4006:800::1002: icmp_seq=3 ttl=55 time=43.5 ms 64 bytes from 2404:6800:4006:800::1002: icmp_seq=4 ttl=55 time=43.4 ms 64 bytes from 2404:6800:4006:800::1002: icmp_seq=5 ttl=56 time=43.8 ms --- code.google.com ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4006ms rtt min/avg/max/mdev = 43.404/43.713/44.309/0.329 ms jason@jdc:~$ If I can debug further let me know. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages lynx-cur depends on: ii libbsd0 0.4.2-1 ii libbz2-1.01.0.6-4 ii libc6 2.13-36 ii libgcrypt11 1.5.0-3 ii libgnutls26 2.12.20-1 ii libidn11 1.25-2 ii libncursesw5 5.9-10 ii libtinfo5 5.9-10 ii zlib1g1:1.2.7.dfsg-13 Versions of packages lynx-cur recommends: ii mime-support 3.52-2 lynx-cur suggests no packages. -- Configuration Files: /etc/lynx-cur/lynx.cfg changed: .h1 Auxiliary Facilities .h2 INCLUDE .ex .ex .h2 STARTFILE .ex .h2 HELPFILE .ex HELPFILE:file://localhost/usr/share/doc/lynx-cur/lynx_help/lynx_help_main.html.gz .h2 DEFAULT_INDEX_FILE DEFAULT_INDEX_FILE:http://lynx.isc.org/ .h1 Interaction .h2 GOTOBUFFER .h2 JUMP_PROMPT .h1 Auxiliary Facilities .h2 JUMPFILE .ex .h2 JUMPBUFFER .h1 Internal Behavior .h2 SAVE_SPACE .h2 REUSE_TEMPFILES .h2 LYNX_HOST_NAME .h2 LOCALHOST_ALIAS .ex 2 .h2 LOCAL_DOMAIN .h1 Session support .h2 AUTO_SESSION .h2 SESSION_FILE .h2 SESSION_LIMIT .h1 Character sets .h2 CHARACTER_SET .nf .fi CHARACTER_SET:iso-8859-1 .h2 LOCALE_CHARSET .h2 ASSUME_CHARSET .h2 ASSUMED_DOC_CHARSET_CHOICE .h2 DISPLAY_CHARSET_CHOICE .ex .ex 4 .h2 ASSUME_LOCAL_CHARSET .h2 PREPEND_CHARSET_TO_SOURCE PREPEND_CHARSET_TO_SOURCE:FALSE .h2 NCR_IN_BOOKMARKS .h2 FORCE_8BIT_TOUPPER .h2 OUTGOING_MAIL_CHARSET .h2 ASSUME_UNREC_CHARSET .h2 PREFERRED_LANGUAGE PREFERRED_LANGUAGE:en .h2 PREFERRED_CHARSET .h2 CHARSETS_DIRECTORY .h2 CHARSET_SWITCH_RULES .h1 Interaction .h2 URL_DOMAIN_PREFIXES .h2 URL_DOMAIN_SUFFIXES .h2 FORMS_OPTIONS .h2 PARTIAL .h2 PARTIAL_THRES .h2 SHOW_KB_RATE .h2 SHOW_KB_NAME .h1 Timeouts .h2 INFOSECS .h2 MESSAGESECS .h2 ALERTSECS .h2 DEBUGSECS .h2 REPLAYSECS .h1 Appearance .h2 USE_SELECT_POPUPS .h2 SHOW_CURSOR SHOW_CURSOR:TRUE .h2 UNDERLINE_LINKS .h2 BOLD_HEADERS .h2 BOLD_H1 .h2 BOLD_NAME_ANCHORS .h1 Internal Behavior .h2 DEFAULT_CACHE_SIZE .h2 DEFAULT_VIRTUAL_MEMORY_SIZE .h2 SOURCE_CACHE .h2 SOURCE_CACHE_FOR_ABORTED .h2 ALWAYS_RESUBMIT_POSTS .h2 TRIM_INPUT_FIELDS .h1 HTML Parsing .h2 NO_ISMAP_IF_USEMAP .h2 SEEK_FRAG_MAP_IN_CUR .h2 SEEK_FRAG_AREA_IN_CUR .h1 CGI scripts .h2 LOCAL_EXECUTION_LINKS_ALWAYS_ON .h2 LOCAL_EXECUTION_LINKS_ON_BUT_NOT_REMOTE LOCAL_EXECUTION_LINKS_ALWAYS_ON:FALSE LOCAL_EXECUTION_LINKS_ON_BUT_NOT_REMOTE:FALSE .h2 TRUSTED_EXEC TRUSTED_EXEC:none .h2 ALWAYS_TRUSTED_EXEC ALWAYS_TRUSTED_EXEC:none .h2 TRUSTED_LYNXCGI TRUSTED_LYNXCGI:none .h2 LYNXCGI_ENVIRONMENT .h2 LYNXCGI_DOCUMENT_ROOT .h1 Cookies .h2 FORCE_SSL_COOKIES_SECURE .h1 Internal Behavior .h2 MAIL_SYSTEM_ERROR_LOGGING .h2 CHECKMAIL .h1 News-groups .h2 NNTPSERVER .h2 LIST_NEWS_NUMBERS .h2 LIST_NEWS_DATES .h2 NEWS_CHUNK_SIZE .h2 NEWS_MAX_CHUNK .h2 NEWS_POSTING .h2 LYNX_SIG_FILE .h1 Bibliographic Protocol (bibp scheme) .h2 BIBP_GLOBAL_SERVER .h2 BIBP_BIBHOST .h1 Interaction .h2 SCROLLBAR .h2 SCROLLBAR_ARROW .h2 USE_MOUSE .h1 HTML Parsing .h2 COLLAPSE_BR_TAGS .h2 TAGSOUP .h1 Cookies .h2 SET_COOKIES .h2 ACCEPT_ALL_COOKIES .h2 COOKIE_
Bug#691718: AT-spi upgrade breaks Gnome-shell accessibility
Package: libatk-adaptor Version: 2.5.3-3 Priority: important I am running Sid with everything up to date, including atk-adaptor 2.5.3-3. Upon starting a Gnome session, I am unable to access gnome-shell and the following error messages appear in ~/.xsession-errors: ** (gnome-shell:20547): WARNING **: Accessibility: org.a11y.atspi schema not found. Are you sure that at-spi or at-spi2 is installed on your system? ** (gnome-shell:20547): WARNING **: Accessibility: invalid module path (NULL) ** (gnome-shell:20547): WARNING **: Accessibility: error loading the atk-bridge. Although the accessibility on the system is enabled and clutter accessibility is also enabled, accessibility support on GNOME She ll will not work According to the changelog, the schema was removed as redundant in the latest at-spi upload, but Gnome-shell is evidently still looking for it, not finding it and therefore not loading the ATK bridge. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#690530: dbus: Unable to launch DBus services without X11 running
Upon investigation, this probably isn't the cause of my PulseAudio problem - my apologies. I'm still getting those error messages, though, from the console. I'm not sure whether this is a bug or not anymore. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#690530: dbus: Unable to launch DBus services without X11 running
Package: dbus Version: 1.6.8-1 Severity: normal Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? I ran, e.g., aplay from the console (no X11 running) with PulseAudio installed and configured. * What was the outcome of this action? Oct 15 18:49:11 jdc pulseaudio[9803]: [pulseaudio] main.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11 * What outcome did you expect instead? A DBus daemon should have been launched and PulseAudio started within the user's session, which was all working perfectly until recently. Note that Alsa is configured to run PulseAudio, if the latter is installed, so the resulting symptom in that case is no audio. Obviously, however, this is a general DBus issue - PulseAudio is only an example of how it bites. *** End of the template - remove these lines *** -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages dbus depends on: ii adduser3.113+nmu3 ii libc6 2.13-35 ii libdbus-1-31.6.8-1 ii libexpat1 2.1.0-1 ii libselinux12.1.9-5 ii libsystemd-login0 44-4 ii lsb-base 4.1+Debian7 dbus recommends no packages. Versions of packages dbus suggests: ii dbus-x11 1.6.8-1 -- 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#689201: biber: Documentation is missing from package
Package: biber Version: 0.9.9+release-1 Severity: wishlist The documentation for this software (biber.pdf) is available from Sourceforge but not included in the package. As a result, the texdoc command fails to find it. (According to the biber(1) manual page, texdoc biber should retrieve the documentation, as is true for TeX/LaTeX packages generally). I hope the documentation can be included in the next version. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#464664: 2.6.24: X86_64 laptop hangs after logging powernow_k8 error while on battery
Jonathan Nieder wrote:
> Thanks for reporting, and sorry for the long silence.
That's understandable.
>
> Do you still have access to this hardware? If so, would you still be
> interested in pursuing this bug? ("No" is an ok answer, but please do
> let us know so we can plan accordingly.)
The corresponding kernel bug was closed with a suggestion to reopen it if it
can be reproduced with a recent kernel. I think that's entirely reasonable.
I still have the hardware on a shelf somewhere here. At some point I'll take
it out, clear the drive and install a recent Debian (probably easier than
trying to upgrade a system that hasn't been booted for four years and there's
nothing worth preserving on the disk anyway).
That's a long way of saying, perhaps just close the bug and when I get to play
with the hardware I'll reopen the bug if I can still reproduce the issue with
an up to date kernel.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#683880: gnome-shell: Sometimes hangs during startup
Here is a backtrace. This time, there weren't any interesting or unusual
messages in ~/.xsession-errors. The user's name did not appear on the top
panel, as reported earlier. The backtrace was obtained by attaching to the
process.
(gdb) thread apply all bt full
Thread 5 (Thread 0x7fe7b2c2c700 (LWP 16566)):
#0 0x7fe7bd8a7ac3 in *__GI___poll (fds=, nfds=, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87
_a3 = -1
_a1 = 140632799675456
resultvar =
_a2 = 5
oldtype = 0
result =
#1 0x7fe7bddc74d4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#2 0x7fe7bddc7932 in g_main_loop_run () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#3 0x7fe7bf35b7f6 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
No symbol table info available.
#4 0x7fe7bdde9df5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#5 0x7fe7bdb67b50 in start_thread (arg=) at
pthread_create.c:304
__res =
pd = 0x7fe7b2c2c700
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140633113282304,
-3046831744863170592, 140736370460096, 140633113283008, 140633461465152, 3,
3060230232543596512, 3060197902268764128},
mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data =
{prev = 0x0, cleanup = 0x0, canceltype = 0}}}
not_first_call =
freesize =
__PRETTY_FUNCTION__ = "start_thread"
#6 0x7fe7bd8b270d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
No locals.
#7 0x in ?? ()
No symbol table info available.
Thread 4 (Thread 0x7fe7b700 (LWP 16567)):
#0 0x7fe7bd8a7ac3 in *__GI___poll (fds=, nfds=, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87
_a3 = -1
_a1 = 20376112
resultvar =
_a2 = 1
oldtype = 0
result =
#1 0x7fe7bddc74d4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#2 0x7fe7bddc7932 in g_main_loop_run () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#3 0x7fe7b2227efb in ?? () from
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
No symbol table info available.
#4 0x7fe7bdde9df5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#5 0x7fe7bdb67b50 in start_thread (arg=) at
pthread_create.c:304
__res =
pd = 0x7fe7b700
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140633102755584,
-3046831744863170592, 140736370459616, 140633102756288, 140633461465152, 3,
3060229960886915040, 3060197902268764128},
mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data =
{prev = 0x0, cleanup = 0x0, canceltype = 0}}}
not_first_call =
freesize =
__PRETTY_FUNCTION__ = "start_thread"
#6 0x7fe7bd8b270d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
No locals.
#7 0x in ?? ()
No symbol table info available.
Thread 3 (Thread 0x7fe7b181a700 (LWP 16568)):
#0 0x7fe7bd8a7ac3 in *__GI___poll (fds=, nfds=, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87
_a3 = -1
_a1 = 20502656
resultvar =
_a2 = 2
oldtype = 0
result =
#1 0x7fe7be2f6e3f in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
No symbol table info available.
#2 0x7fe7be2e839c in pa_mainloop_poll () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
No symbol table info available.
#3 0x7fe7be2e89f9 in pa_mainloop_iterate () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
No symbol table info available.
#4 0x7fe7be2e8ab0 in pa_mainloop_run () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
No symbol table info available.
#5 0x7fe7be2f6def in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
No symbol table info available.
#6 0x7fe7b7ce5423 in ?? () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-2.0.so
No symbol table info available.
#7 0x7fe7bdb67b50 in start_thread (arg=) at
pthread_create.c:304
__res =
pd = 0x7fe7b181a700
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140633092237056,
-3046831744863170592, 140633297068448, 140633092237760, 140633461465152, 3,
3060224158386098144, 3060197902268764128},
mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data =
{prev = 0x0, cleanup = 0x0, canceltype = 0}}}
not_first_call =
freesize =
__PRETTY_FUNCTION__ = "start_thread"
#8 0x7fe7bd8b270d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
No locals.
#9 0x in ?? ()
No symbol table info available.
Thread 2 (Thread 0x7fe7b1009700 (LWP 16569)):
#0 pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
No locals.
#1 0x7fe7c5c35c90 in PR_WaitCondVar () from
/usr/lib/x86_64-linux-gnu/
Bug#683880: gnome-shell: Sometimes hangs during startup
Package: gnome-shell Version: 3.4.2-1 Severity: important I run Gnome via startx from console sessions. This usually works correctly, but sometimes, Gnome-Shell occasionally hangs - it is completely unresponsive after loading. I suspect a race condition somewhere. It has been observed that the name of the user does not appear in the top panel when this occurs. Although I am using Gnome-Orca and accessibility support, the same issue has been noticed by other users of the machine who do not have accessibility requirements and whose Gnome sessions are not configured with accessibility enabled. The system is debian Sid, kept up to date. This problem first appeared when the system was updated from Gnome-Shell 3.2 to 3.4. I can investigate further as requested. Here are errors from my ~/.xession-errors that may be relevant. (gnome-shell:12196): folks-WARNING **: Failed to find primary PersonaStore with type ID 'eds' and ID 'system'. Individuals will not be linked properly and creating new links between Personas will not work. The configured primary PersonaStore's backend may not be installed. If you are unsure, check with your distribution. Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x183 (Orca Scree) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. ** Message: applet now embedded in the notification area nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 30 _toolkitForObject: [panel | ] no longer exists _toolkitForObject: [panel | ] no longer exists _toolkitForObject: [panel | ] no longer exists _toolkitForObject: [panel | ] no longer exists _toolkitForObject: [panel | ] no longer exists _toolkitForObject: [panel | ] no longer exists _toolkitForObject: [panel | ] no longer exists _toolkitForObject: [check box | ] no longer exists _toolkitForObject: [check box | ] no longer exists _toolkitForObject: [panel | ] no longer exists _toolkitForObject: [panel | ] no longer exists _toolkitForObject: [panel | ] no longer exists _toolkitForObject: [panel | ] no longer exists (gnome-settings-daemon:12160): color-plugin-WARNING **: Done switch to new account, reload devices -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages gnome-shell depends on: ii dconf-gsettings-backend [gsettings-backend] 0.12.1-2 ii gconf-service3.2.5-1 ii gir1.2-accountsservice-1.0 0.6.21-6 ii gir1.2-atk-1.0 2.4.0-2 ii gir1.2-caribou-1.0 0.4.2-2 ii gir1.2-clutter-1.0 1.10.8-1 ii gir1.2-cogl-1.0 1.10.2-6 ii gir1.2-coglpango-1.0 1.10.2-6 ii gir1.2-folks-0.6 0.6.9-1+b1 ii gir1.2-freedesktop 1.32.1-1 ii gir1.2-gconf-2.0 3.2.5-1 ii gir1.2-gcr-3 3.4.1-3 ii gir1.2-gdesktopenums-3.0 3.4.2-1 ii gir1.2-gdkpixbuf-2.0 2.26.1-1 ii gir1.2-gee-1.0 0.6.4-2 ii gir1.2-gkbd-3.0 3.4.0.2-1 ii gir1.2-glib-2.0 1.32.1-1 ii gir1.2-gmenu-3.0 3.4.2-3 ii gir1.2-gnomebluetooth-1.03.4.2-1 ii gir1.2-gtk-3.0 3.4.2-2 ii gir1.2-json-1.0 0.14.2-1 ii gir1.2-mutter-3.03.4.1-5 ii gir1.2-networkmanager-1.00.9.4.0-5 ii gir1.2-pango-1.0 1.30.0-1 ii gir1.2-polkit-1.00.105-1 ii gir1.2-soup-2.4 2.38.1-2 ii gir1.2-telepathyglib-0.120.18.2-1 ii gir1.2-telepathylogger-0.2 0.4.0-1 ii gir1.2-upowerglib-1.00.9.17-1 ii gjs 1.32.0-2 ii gnome-bluetooth 3.4.2-1 ii gnome-icon-theme-symbolic3.4.0-2 ii gnome-settings-daemon3.4.2-4 ii gnome-shell-common 3.4.2-1 ii gnome-themes-standard3.4.2-1 ii gsettings-desktop-schemas3.4.2-1 ii libatk1.0-0 2.4.0-2 ii libc62.13-35 ii libcairo-gobject21.12.2-2 ii libcairo21.12.2-2 ii libcanberra0 0.28-4 ii libclutter-1.0-0
Bug#683230: gnome-settings-daemon: Problem it Universal Access tab
Jean-Philippe MENGUAL wrote: > Hi, > > To have orca as automatic started application at the gnome starting, I > don't find any solution via the GUI. So I did the cp suggested, and I > realised that ~/.config/autostart doesn't exist by default and needs to > be created by hand. Once done, indeed, it works and bug has a > workaround. To narrow this down further, could you try editing /etc/xdg/autostart/orca-autostart.desktop and replace the lines Exec=orca --no-setup --disable main-window,splash-window --enable speech,braille NoDisplay=true with the line Exec=orca --replace then move ~/.config/autostart/orca.desktop out of the way and enable Orca as a screen reader, then see if the bug still occurs. The difference between running Orca as an autostart application on the desktop and enabling it as a screen reader, as I understand it, is that in the latter case /etc/xdg/autostart/orca-autostart.desktop is run, which has the extra command line arguments as shown above. If you can run Orca from /etc/xdg/autostart/orca-autostart.desktop without the extra options and if the bug doesn't occur then, it's an Orca bug that should be pushed upstream, in my judgment. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#683230: gnome-settings-daemon: Problem it Universal Access tab
Do you still experience the bug if you load Gnome-shell rather than fallback mode? I'm not experiencing it, but I am loading Orca as an autostart application and I am using Gnome-shell, not fallback. You could also try loading Orca as an autostart application just to see if that makes a difference. This testing should identify more precisely the circumstances in which you encounter the bug. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#683230: gnome-settings-daemon: Problem it Universal Access tab
Jean-Philippe MENGUAL wrote: > Package: gnome-settings-daemon I don't think gnome-settings-daemon is involved here. I would report it as a bug against gnome-orca in the first instance. > Version: 3.4.2-4 > Severity: important I don't think this qualifies as "important", which is defined as: "a bug which has a major effect on the usability of a package, without rendering it completely unusable to everyone." It only causes Orca commands not to work when Orca is started in a particular way. If Orca is run as a startup application from the desktop, the bug does not occur as I have verified. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#682914: Iceweasel Fails to detect that accessibility is enabled on the Gnome 3 desktop
Package: iceweasel Version: 10.0.6esr-1 Severity: normal Debian now uses the Gnome 3 accessibility infrastructure (AT-SPI 2, Orca 3.4, etc.). Iceweasel 10.x is unable to detect that accessibility is enabled under Gnome 3 and it is therefore inaccessible to Orca users unless work-arounds are in place (i.e., GNOME_ACCESSIBILITY=1 is set in the environment by the user). The patch to fix this appears to have been integrated as of Firefox 11: https://bugzilla.mozilla.org/show_bug.cgi?id=693343 and I can confirm that it is working (I use Iceweasel 14 from experimental). Would it be possible to backport the patch to the version of Gecko that will be included in Wheezy? This is becoming a FAQ on the Debian accessibility and Orca mailing lists - users keep encountering this bug after installing testing. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#679712: auctex: Please add support for Emacs 24
Package: auctex Version: 11.86-10 Followup-For: Bug #679712 After upgrading to Emacs 24 in Sid, it was necessary to make the following change in /etc/emacs/site-start.d/50auctex.el to load AUCTeX mode: commit d6e2d76d1498a134a275b36d53ae5e5d866614c9 Author: Jason White Date: Mon Jul 16 10:27:36 2012 +1000 Load AUCTeX mode in Emacs 24. diff --git a/emacs/site-start.d/50auctex.el b/emacs/site-start.d/50auctex.el index 34b2bba..63c48ab 100644 --- a/emacs/site-start.d/50auctex.el +++ b/emacs/site-start.d/50auctex.el @@ -4,7 +4,7 @@ ;;; form "(unload-feature 'tex-site)" (i.e., put that string into your ;;; "~/.emacs" to disable AUCTeX completely). -(if (member debian-emacs-flavor '(emacs23 emacs-snapshot)) +(if (member debian-emacs-flavor '(emacs23 emacs24 emacs-snapshot)) (if (file-exists-p "/usr/share/emacs/site-lisp/auctex/tex.el") (progn (let ((list '((lisp . "auctex") (source . "auctex" -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#678521: gnome-orca: orca and speakup crash when orca is started
Hi, Another suggestion: try turning Speakup off before you start your X session. In the laptop keyboard layout, it's caps lock-enter, and I can't remember what it is in the desktop layout. Those who use Speakup will know. So, turn off Speakup, start your X session and run Orca. This may work around your problem. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#678521: gnome-orca: orca and speakup crash when orca is started
mike wrote: > hi, > > once i start orca speakupd dies and flashes words down the screen but i > can't find anything that woood point to why it is failing any suggested > places to look? rebooting brings speakup back. Is there anything relevant in /var/log/messages? How is Speakup configured - which synthesizer? Are you using Speech-Dispatcher with Speakup, Espeakup, or a serial synthesizer? I've had this all working fine with Espeakup, but I am not a regular Speakup user. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#678521: gnome-orca: orca and speakup crash when orca is started
mike stopka wrote: > Package: gnome-orca > Version: 3.4.2-2 > Severity: important You seem to have left out the text of your bug report. Perhaps you made a mistake when editing? Could you follow up with a description of the problem, including any necesary log messages and error messages? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#676144: clang: compiling with -g flag doesn't introduce line number information recognizable by gdb
Sylvestre Ledru wrote:
> Anything special about your system / install I should know ?
Nothing that comes to mind, but see discussion below.
>
> with amd64:
> $ clang -O3 -g -o test plop.c
> $ gdb test
> GNU gdb (GDB) 7.4.1-debian
> [...]
> Reading symbols from /tmp/test...done.
> (gdb) b main
> Breakpoint 1 at 0x400524: file plop.c, line 5.
> (gdb) run
> Starting program: /tmp/test
>
> Breakpoint 1, main () at plop.c:5
> 5printf("%-6d%-6d\n", i, i*i);
> (gdb) bt
> #0 main () at plop.c:5
> (gdb)
I get identical results to yours if I include the -O3 flag, as above, but if I
omit the optimization flag I get the behaviour shown in the bug report.
Gdb also reports the absence of line number information if I specify -O0
explicitly.
Can you reproduce?
Regards,
Jason.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#676144: clang: compiling with -g flag doesn't introduce line number information recognizable by gdb
Package: clang
Version: 3.1-4
Severity: normal
To reproduce this, suppose we have a simple test program such as:
#include
int main() {
int i;
for (i = 1; i <= 10; i++)
printf("%-6d%-6d\n", i, i*i);
return 0;
}
After compiling with clang -g -o test test.c
(gdb) start
Temporary breakpoint 1 at 0x4005b4
Starting program: /tmp/test
Temporary breakpoint 1, 0x004005b4 in main ()
(gdb) n
Single stepping until exit from function main,
which has no line number information.
If I compile with gcc 4.7.0-11 and run gdb I get line number information as
usual.
The version of gdb installed is 7.4.1-1.1, AMD64 architecture.
This appears to have been introduced as of Clang 3.1.
Apologies in advance if this turns out to be due to an error/oversight on my
part. Thanks to all involved for bringing Clang to Debian - I'm finding it
useful and the excellent error messages are very helpful as I'm trying to
improve
my programming skills at the moment.
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages clang depends on:
ii libc62.13-33
ii libclang-common-dev 3.1-4
ii libffi5 3.0.10-3
ii libgcc1 1:4.7.0-11
ii libllvm3.1 3.1-1
ii libstdc++6 4.7.0-11
ii libstdc++6-4.6-dev 4.6.3-7
Versions of packages clang recommends:
ii llvm-3.1-dev 3.1-1
ii python2.7.2-10
clang 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#675134: libparse-debcontrol-perl: Reports a parse error if first line of file is a comment
Package: libparse-debcontrol-perl
Version: 2.005-3
Severity: normal
If the first line of the control file is a comment and I run dch -i, which
invokes libparse-debcontrol-perl, I get:
Parse error: invalid key/value stansa at line 1 of data ("### Do not edit!
This file is auto-generated from debian/bootstrap.sh.").
This bug was discovered while attempting to compile the FreeSWITCH packages
which are under development for Debian.
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages libparse-debcontrol-perl depends on:
ii liberror-perl 0.17-1
ii libexporter-lite-perl 0.02-2
ii libio-stringy-perl 2.110-5
ii libwww-perl6.04-1
ii perl 5.14.2-11
Versions of packages libparse-debcontrol-perl recommends:
ii libtie-ixhash-perl 1.21-2
libparse-debcontrol-perl 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#667616: brltty greedily grabs serial ports, ftdi_sio loses connection
Mario Lang wrote: > BRLTTY should be installable by default without giving anyone trouble, > thats one of your really big goals for long term. That's fine, but meanwhile the only solution is not to install it. In general, I don't think BRLTTY should be installed unless the user explicitly installs the package or uses braille during the Debian installation. The issue isn't just the current problem under discussion, but also the probing of serial ports (although I suppose that can be turned off if it happens by default). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#667616: brltty greedily grabs serial ports, ftdi_sio loses connection
Witold Baryluk wrote: > I just wanted to add, that I and my few other friends living on sid have > similar problem. Various serial devices (microcontroler programators, 3d > printers, usb-serial converters) stoped working due brltty messup. And brltty > installed automatically on some upgrade due to the some dependencies of other > packages, like text2spearch packages probably. > > After detecting problem it was matter of uninstalling brltty, but still why it > need to make live harder to some people? Because some device manufacturers don't obtain unique vendor/product ids for their products and thus BRLTTY can't distinguish between genuine braille devices and certain other hardware. The solution is simple: if you don't have a braille display then make sure that BRLTTY is not installed. Those who do have a braille display really need it for accessing their systems. Dependency resolution shouldn't result in installation of BRLTTY for users who don't request it, though. Would it be possible to find and fix those dependencies? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#668365: gnome-shell: crashes on startup in cogl
Michael Biebl wrote: > It's a different bug > > You have made a partial upgrade of libcogl. Your version of gnome-shell > tries to load both libcogl9 (via libcogl-pango_1.10.2-2) and libcogl5. I downgraded to libcogl-pango_1.8.2-1 (testing), which was enough to work around it for now. Thanks. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#668365: gnome-shell: crashes on startup in cogl
Package: gnome-shell Version: 3.2.2.1-4 Followup-For: Bug #668365 I am seeing this after running dist-upgrade today (under Sid). >From /var/log/syslog: May 5 13:10:40 jdc kernel: [16574.331243] gnome-shell[28802]: segfault at 10 ip 7f54dfd0 sp 7f5a6030 error 4 in libcogl.so.9.1.1[7f54dfcaa000+87000] May 5 13:10:40 jdc x-session-manager[28749]: WARNING: Application 'gnome-shell.desktop' killed by signal 11 May 5 13:10:41 jdc kernel: [16575.697634] gnome-shell[28885]: segfault at 10 ip 7f8240363111 sp 7fff3ce2cb90 error 4 in libcogl.so.9.1.1[7f824030c000+87000] May 5 13:10:41 jdc x-session-manager[28749]: WARNING: App 'gnome-shell.desktop' respawning too quickly May 5 13:10:42 jdc x-session-manager[28749]: WARNING: Application 'gnome-shell.desktop' killed by signal 11 May 5 13:10:49 jdc acpid: client 28687[0:0] has disconnected I don't know whether it's the same bug though. If you need a gdb backtrace, a reference to instructions on how to get Gnome-shell running under gdb would be helpful. I'm currently running startx from a terminal to invoke an X session. With luck, lots of people who upgrade will be encountering this, making it easier to diagnose. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages gnome-shell depends on: ii dconf-gsettings-backend [gsettings-backend] 0.12.1-1 ii gconf-service3.2.5-1 ii gir1.2-accountsservice-1.0 0.6.15-4 ii gir1.2-atk-1.0 2.4.0-2 ii gir1.2-caribou-1.0 0.4.2-2 ii gir1.2-clutter-1.0 1.8.4-1 ii gir1.2-cogl-1.0 1.10.2-2 ii gir1.2-coglpango-1.0 1.10.2-2 ii gir1.2-folks-0.6 0.6.8-2 ii gir1.2-freedesktop 1.32.1-1 ii gir1.2-gconf-2.0 3.2.5-1 ii gir1.2-gdkpixbuf-2.0 2.26.1-1 ii gir1.2-gee-1.0 0.6.4-1 ii gir1.2-gkbd-3.0 3.4.0.2-1 ii gir1.2-glib-2.0 1.32.1-1 ii gir1.2-gmenu-3.0 3.2.0.1-2 ii gir1.2-gnomebluetooth-1.03.2.2-1 ii gir1.2-gtk-3.0 3.4.1-2 ii gir1.2-json-1.0 0.14.2-1 ii gir1.2-mutter-3.03.2.2-3 ii gir1.2-networkmanager-1.00.9.4.0-3 ii gir1.2-pango-1.0 1.30.0-1 ii gir1.2-polkit-1.00.105-1 ii gir1.2-soup-2.4 2.38.1-2 ii gir1.2-telepathyglib-0.120.18.1-2 ii gir1.2-telepathylogger-0.2 0.4.0-1 ii gir1.2-upowerglib-1.00.9.16-2 ii gjs 1.32.0-2 ii gnome-bluetooth 3.2.2-1 ii gnome-icon-theme-symbolic3.4.0-2 ii gnome-settings-daemon3.2.2-3 ii gnome-shell-common 3.2.2.1-4 ii gsettings-desktop-schemas3.4.1-2 ii libatk1.0-0 2.4.0-2 ii libc62.13-32 ii libcairo-gobject21.12.2-1 ii libcairo21.12.2-1 ii libcamel-1.2-29 3.2.2-3 ii libcanberra0 0.28-4 ii libclutter-1.0-0 1.8.4-1 ii libcogl-pango0 1.10.2-2 ii libcogl5 1.8.2-1 ii libcroco30.6.5-1 ii libdbus-1-3 1.5.12-1 ii libdbus-glib-1-2 0.98-1 ii libdrm2 2.4.33-1 ii libebook-1.2-12 3.2.2-3 ii libecal-1.2-10 3.2.2-3 ii libedataserver-1.2-153.2.2-3 ii libedataserverui-3.0-1 3.2.2-3 ii libffi5 3.0.10-3 ii libfolks25 0.6.8-2 ii libfontconfig1 2.9.0-3 ii libfreetype6 2.4.9-1 ii libgconf-2-4 3.2.5-1 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libgee2 0.6.4-1 ii libgirepository-1.0-11.32.1-1 ii libgjs0b [libgjs0-libmozjs185-1.0] 1.32.0-2 ii libgl1-mesa-glx [
Bug#666691: emacs: I can confirm this
Matija Grabnar wrote: > I can confirm that I am seeing this problem, too. > emacs -nw blocks, eating 100% CPU and not accepting any > input. The only way to get out of it is to kill emacs from > another session. It's the same here when I invoke Emacs from a virtual console. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#664239: gnome-orca: No speech on startup
Shane Wegner wrote: > Traceback (most recent call last): > File "/usr/lib/pymodules/python2.7/orca/speech.py", line 100, in > _initSpeechServer > ['']) > ImportError: No module named gnomespeechfactory Gnome-Speech is obsolete and was removed in Gnome 3. You need to use Speech-dispatcher instead. You probably have an old Orca configuration that still refers to Gnome-Speech. Try re-configuring Orca for Speech-Dispatcher, e.g., orca -t from a terminal. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#659957: [Pkg-shadow-devel] Bug#659957: Bug#659957: login: login at console no longer updates utmp
Christian PERRIER wrote: > See last comment by Nicolas. If I understand correctly, he deactivated > utmp logging in last upstream release because he was thinking that > using pam_lastlog would be enough nowadays. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=605329 is the original bug. It seems that /var/log/wtmp is being updated by pam_lastlog, but /var/run/utmp is not, and there's nothing in the pam_lastlog manual page to suggest that it updates utmp. The result is that now nothing is updating /var/run/utmp when the user logs in. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#659957: [Pkg-shadow-devel] Bug#659957: login: login at console no longer updates utmp
I upgraded another machine (my laptop) to login 4.1.5-1, which was enough to reproduce the bug. Is everyone who upgrades seeing this, or is it specific to a particular configuration? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#642055: daisy-player: reports "corrupt daisy structure" and aborts while reading valid book
Samuel Thibault wrote: > The fixes I have added to the Debian package should be enough. They > at least permit to open almost all Daisy consortium-provided examples > (others require more implementation). So at worse, if upstream does not > upgrade to libxml in time for the wheezy release, we should be fine > enough. That's great work - thanks. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#642055: daisy-player: reports "corrupt daisy structure" and aborts while reading valid book
Samuel Thibault wrote: > Mmm, no begin should really stay at the beginning of the buffer. But if > you need that to get things done I guess it's because p - begin becomes > greater than 250? That rather means that we have to increase the size > of the buffer, as is already done in ebook-speaker. Could you try the > attached patch? I don't have the book anymore that was causing the bug, but the upstream author of daisy-player was able to trigger more bugs by attempting to play sample books published by the Daisy Consortium. He expressed an intention to rewrite the code to use an XML parser instead of the bug-prone implementation currently in place. It might be best to hold the bug until this is done, but I'm certainly willing to try the patch if I can find a book that triggers it. I also agree with you about increasing the buffer size, as far as I can remember the code, which is not well. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#660804: [openadsl-users] [Bug 42809] New: kernel panic when receiving an ipsec packet
Eric Dumazet wrote: > Which driver handles this Traverse Solos card ? solos_pci, which also requires the atm module. (I'm just trying to help here; I'm not affected by the bug.) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#659957: [Pkg-shadow-devel] Bug#659957: login: login at console no longer updates utmp
Nicolas François wrote: > Are you using pam_lastlog for login? (/etc/pam.d/login) I am also experiencing this bug. From /etc/pam.d/login: sessionoptional pam_lastlog.so -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#658667: Crashes DECTALK by sending high-bit characters
Samuel Thibault wrote: > Agreed. Can you perhaps handle submitting the patch upstream too? I've forwarded the bug submission to Mike, who I think also monitors debian-accessibility anyway. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#658667: Crashes DECTALK by sending high-bit characters
Package: yasr
version: 0.6.9-2
Severity: normal
Yasr allows "extended" characters (with the high bit set) to be sent to a
DECTALK Express. Some of these characters cause the synthesizer to crash,
after which it must be power cycled.
I have implemented a local solution that excludes high-bit characters entirely
(see attached patch). The alternative (and superior) approach would be to use
the existing exclusion mechanism in Yasr by populating the array of
"unspeakable" characters for the DECTALK. This would require each of the
extended characters to be tested to identify those responsible for the
crashes. Since DECTALK Express is English only, as far as I know, there really
isn't much point in sending extended characters to it anyway, so I've locally
adopted the more general solution, which might not be acceptable from a Debian
point of view.
A simple patch is attached.
Index: yasr-0.6.9/yasr/tts.c
===
--- yasr-0.6.9.orig/yasr/tts.c 2008-02-03 00:10:07.0 +1100
+++ yasr-0.6.9/yasr/tts.c 2012-02-05 10:59:06.059007839 +1100
@@ -281,6 +281,9 @@
char *p = synth[tts.synth].unspeakable;
if (ch < 32) return 1;
+ /* characters with high bit set cause DECTALK to crash */
+ if (tts.synth == TTS_DECTALK && ch & 0x80)
+return 1;
while (*p)
{
if (*p++ == ch) return 1;
Bug#658564: daisy-player: Hangs while loading, both from disc and directory.
Erik Sundin wrote: > > > The program hangs with the message "Reading Ö..." displaying in the > > top left corner directly after startup. Nothing seems to happen after > > that... This occurs both when running it whitout any arguments > > (presumably it then attempts to play from /dev/cdrom, though this is > > not mentioned anywhere (as far as I can tell)) and when a directory > > is given on the commandline. Unfortunately I only have one book to > > try it with, but the disk in question works as it should in a > > physical player which seems to indicate software trouble. [...] > It may also be worth mentioning that while hung the process consumes > about 95% of my CPU. It failed on one of the books that I tried, and also on some of the samples provided by the Daisy Consortium. I contacted the upstream author, who indicated that he planned to revise it to use a real XML parser (currently it uses its own, very primitive and failure-prone, code for parsing XML). I took one look at this and... wasn't at all surprised that it didn't work. If the rewrite is done, it should be much more robust, however. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#655536: chromium: Native client should be packaged and enabled
Package: chromium Version: 16.0.912.75~r116452-1 Severity: wishlist According to the Debian changelog, native client is currently not included in the package. I am aware of at least one free/open-source Web tool that relies on it (namely Google's ChromeVox accessibility extension with the SVOX Pico text to speech system provided as a nacl executable). I assume that the lack of nacl support in the Chromium package is one reason why this tool doesn't work, even with experimental API extensions enabled. I'm submitting this as a wishlist bug in the hope that the issues which prevent inclusion of nacl will eventually be overcome. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages chromium depends on: ii chromium-inspector16.0.912.75~r116452-1 ii libasound21.0.24.1-4 ii libavcodec-extra-53 4:0.7.3.1 ii libavformat-extra-53 4:0.7.3.1 ii libavutil-extra-514:0.7.3.1 ii libbz2-1.01.0.6-1 ii libc6 2.13-24 ii libcairo2 1.10.2-6.2 ii libcups2 1.5.0-13 ii libdbus-1-3 1.4.16-1 ii libevent-2.0-52.0.16-stable-1 ii libexpat1 2.0.1-7.2 ii libflac8 1.2.1-6 ii libfontconfig12.8.0-3 ii libfreetype6 2.4.8-1 ii libgcc1 1:4.6.2-11 ii libgconf2-4 3.2.3-1 ii libgcrypt11 1.5.0-3 ii libgdk-pixbuf2.0-02.24.0-2 ii libglib2.0-0 2.28.6-1 ii libgtk2.0-0 2.24.8-2 ii libjpeg8 8c-2 ii libnspr4-0d 4.8.9-1 ii libnss3-1d3.13.1.with.ckbi.1.88-1 ii libpango1.0-0 1.29.4-2 ii libpng12-01.2.46-4 ii libspeex1 1.2~rc1-3 ii libstdc++64.6.2-11 ii libv8-3.6.6.143.6.6.14-2 ii libvpx0 0.9.7.p1-2 ii libwebp2 0.1.3-2 ii libx11-6 2:1.4.4-4 ii libxext6 2:1.3.0-3 ii libxml2 2.7.8.dfsg-5.1 ii libxrender1 1:0.9.6-2 ii libxslt1.11.1.26-8 ii libxss1 1:1.2.1-2 ii xdg-utils 1.1.0~rc1+git20111210-4 ii zlib1g1:1.2.3.4.dfsg-3 chromium recommends no packages. Versions of packages chromium suggests: pn chromium-l10n -- 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#651500: ttytter: Returns to shell prompt after downloading feed and repeatedly displays error message
Package: ttytter Version: 1.2.4-1 Severity: normal When I run this version of TTYtter, it downloads the latest posts from my contacts but, instead of returning to the TTYtter prompt, it returns to the shell prompt. However, ps shows that TTYtter is still running, and it continues to write the following error message to the terminal after the shell prompt has returned: -- sorry, nothing to display. To reproduce the bug, run ttytter with posts awaiting download. I'm using Identica, but that might not matter for present purposes. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages ttytter depends on: ii curl 7.23.1-2 ii perl 5.14.2-6 Versions of packages ttytter recommends: ii libterm-readline-gnu-perl 1.20-2+b1 ii libtimedate-perl 1.2000-1 ttytter 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#641046: hGetContents: invalid argument
Package: hpodder Followup-For: Bug #641046 I am not experiencing this bug with version 1.1.5.0+nmu2, but I do experience it with nmu3. Nmu3 upgraded the package to build with ghc 7, suggesting a possible compatibility issue here. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages hpodder depends on: ii curl 7.23.1-2 ii id3v2 0.1.12-2 ii libc6 2.13-21 ii libffi5 3.0.10-3 ii libgmp3c2 2:4.3.2+dfsg-2 ii libsqlite3-0 3.7.9-2 hpodder recommends no packages. hpodder 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#651021: ttytter: refuses to run under Perl 5.14
Package: ttytter Version: 1.2.2-1 Severity: normal When run with Perl 5.14 (which is current in debian Sid) I get: TTYtter requires 'unsafe' Perl signals (which are of course for its purposes perfectly safe). unfortunately, due to Perl bug 92246 5.14+ cannot set this feature itself. set in your environment either of export PERL_SIGNALS=unsafe # sh, bash, ksh, etc. setenv PERL_SIGNALS unsafe # csh, tcsh, etc. and restart TTYtter, or use Perl 5.12 or earlier. Maybe a wrapper shell script to set the environment variable, as above, would solve this until the underlying Perl bug is fixed. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages ttytter depends on: ii curl 7.23.1-2 ii perl 5.14.2-6 Versions of packages ttytter recommends: ii libterm-readline-gnu-perl 1.20-2+b1 ii libtimedate-perl 1.2000-1 ttytter 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#641046: hGetContents: invalid argument
Package: hpodder Version: 1.1.5.0+nmu3 Followup-For: Bug #641046 I am also experiencing this bug. The following Ubuntu bug appears relevant: https://bugs.launchpad.net/ubuntu/+source/hpodder/+bug/494069 and I can confirm that with a very recent hpodder update, the abc.net.au feeds mentioned in the Ubuntu discussion generate the wide character error, whereas they used to be read properly. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages hpodder depends on: ii curl 7.22.0-3 ii id3v2 0.1.12-2 ii libc6 2.13-21 ii libffi5 3.0.10-3 ii libgmp10 2:5.0.2+dfsg-2 ii libsqlite3-0 3.7.9-2 hpodder recommends no packages. hpodder 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#642055: daisy-player: reports "corrupt daisy structure" and aborts while reading valid book
I haven't solved this entirely, but I've made progress.
It turned out that the XML/XHTML attributes in the input file were not being
parsed properly. I think the following patch fixes it. However, this exposes
another bug: the Daisy book is now parsed, but I get this error:
clip_end (959.366000) is smaller than clip_begin (1160.734000).
This is not possible!
Daisy-player can't handle this DTB.
Here's my patch so far.
commit a7d81ada5baeeca158eef45ce2c7da6b21cba6ff
Author: Jason White
Date: Mon Sep 19 18:31:53 2011 +1000
Work on attribute parsing bug.
diff --git a/daisy-player.c b/daisy-player.c
index 2ba53aa..85a83d3 100644
--- a/daisy-player.c
+++ b/daisy-player.c
@@ -395,6 +395,7 @@ void get_attributes (char *p)
break;
strncpy (name, p, 250);
p = name;
+ begin = p;
while (! isspace (*p) && *p != '=')
{
if (*p == '>' || *p == '?')
@@ -434,6 +435,7 @@ void get_attributes (char *p)
value = p;
p = value;
+ begin = p;
while (*p != '"' && *p != '>' && *p != '?')
{
if (p - begin > 250)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#642055: daisy-player: reports "corrupt daisy structure" and aborts while reading valid book
Having started debugging this, it appears that we reach line 529 of daisy-player.c, i.e., read() returns -1. Interestingly, errno = 0 according to gdb, i.e., "print errno" shows a value of 0. We are at the end of the file, apparently: "print p" shows "" as the content of the buffer. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#642055: daisy-player: reports "corrupt daisy structure" and aborts while reading valid book
Package: daisy-player Version: 7.0.4.1-1 Severity: normal -- System Information: this is the first book that I tried, so I'm not sure how general the problem is. Daisy-player parses the book, presents the table of contents, followed by "reading closing announcement", then aborts with the "corrupt daisy structure" error message. There are no debugging options documented in the manual page. the book is subject to copyright and therefore cannot be disclosed in any form. Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages daisy-player depends on: ii libc6 2.13-21 ii libidn11 1.22-3 ii libncursesw5 5.9-1 ii libsox1b 14.3.2-2+b1 ii madplay 0.15.2b-7 ii udisks1.0.4-1 daisy-player recommends no packages. daisy-player 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#623308: linux-image-2.6.38-2-amd64: Lenovo X200 laptop fails to power down under 2.6.38
maximilian attems wrote: > any update on newer 3.0 linux images from testing? The problem hasn't occurred yet with the 3.0.0-1 kernel. Even with laptop-mode not loaded, it still sometimes occurred under 2.6.39. If my poweroff operations continue to succeed under 3.x for a while, we can declare it fixed upstream, I think, whether intentionally or otherwise. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#640978: vpnc-script requires an update for recent iproute
Antonio Borneo wrote: > Hi Jason, > I added in copy the list vpnc-devel. That's a good idea. > > In the fix you provide, > 1) you add ";s/ipid 0x//g" at the end of string. >This does not impact backward compatibility. I'm in favour to commit it. >Could you please provide, as reference, the output of "ip" command > that contains the string "ipid 0x"? Better if together with the > full command line of "ip". Is there a debug level that will provide this? I'm not necessarily recommending the above fix (which was taken from the Web page that I cited); I am merely reporting that it prevented the error message and enabled me to connect. The above page refers to a thread on LKNL, which would be the place to search for a proper discussion. If I can help further with debugging output, let me know. For reference, I'm running iproute 20110629-1 with kernel 3.0.0-1. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#640978: vpnc-script requires an update for recent iproute
Package: vpnc
Version: 0.5.3r449-2.1
Severity: normal
The provided vpnc-script is not compatible with recent versions of iproute,
apparently, as the output format has changed corresponding to version 2.6.39
and later of the kernel. (It isn't clear to me whether the change was in the
kernel itself or in the iproute package, based on the information cited
below.)
This is the bug described here:
http://aptosid.com/index.php?name=PNphpBB2&file=viewtopic&t=1295
and the work-around given on that page comprises the following patch, which I
have tested and which solved the problem for me.
diff --git a/vpnc/vpnc-script b/vpnc/vpnc-script
index 64be38c..4c5e27a 100755
--- a/vpnc/vpnc-script
+++ b/vpnc/vpnc-script
@@ -116,7 +116,7 @@ destroy_tun_device() {
if [ -n "$IPROUTE" ]; then
fix_ip_get_output () {
- sed 's/cache//;s/metric \?[0-9]\+ [0-9]\+//g;s/hoplimit
[0-9]\+//g'
+ sed 's/cache//;s/metric
\?[0-9]\+[0-9]\+//g;s/hoplimit[0-9]\+//g;s/ipid 0x//g'
}
set_vpngateway_route() {
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.0.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages vpnc depends on:
ii libc62.13-18
ii libgcrypt11 1.5.0-3
ii libgnutls26 2.12.10-1
Versions of packages vpnc recommends:
ii iproute 20110629-1
Versions of packages vpnc suggests:
pn resolvconf
-- Configuration Files:
/etc/vpnc/example.conf [Errno 13] Permission denied: u'/etc/vpnc/example.conf'
/etc/vpnc/vpnc-script [Errno 13] Permission denied: u'/etc/vpnc/vpnc-script'
-- 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#640771: unoconv: Deprecated command line arguments used - warnings issued by LibreOffice
Package: unoconv Version: 0.4-1 Severity: normal The unoconv script uses deprecated command line arguments of soffice (as of LibreOffice 3.4.3). The following warnings are issued: Warning: -headless is deprecated. Use --headless instead. Warning: -invisible is deprecated. Use --invisible instead. Warning: -nodefault is deprecated. Use --nodefault instead. Warning: -nofirststartwizard is deprecated. Use --nofirststartwizard instead. Warning: -nologo is deprecated. Use --nologo instead. Warning: -norestore is deprecated. Use --norestore instead. Warning: -accept=socket,host=localhost,port=2002;urp;StarOffice.ComponentContext is deprecated. Use --accept=socket,host=localhost,port=2002;urp;StarOffice.ComponentContext instead. Fixing this should be a one-line change in the script. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages unoconv depends on: ii python 2.6.7-3 ii python-uno 1:3.4.3-1 Versions of packages unoconv recommends: ii libreoffice-core 1:3.4.3-1 ii libreoffice-java-common 1:3.4.3-1 Versions of packages unoconv suggests: ii libreoffice 1:3.4.3-1 -- 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#632915: ifupdown: DHCPv6 support
Bjørn Mork wrote: >Nope, sorry. isc-dhcp-client has no support for ppp interfaces, which >makes it useless for lots of people. See e.g. xs4all's IPv6 access >service. I have a similar need: the ISP provides DHCPv6 prefixes using prefix delegation, e.g., a /60. This has to be obtained on a PPP interface, but then I need to assign a /64 based on the prefix to another interface, e.g., eth0. I wasn't able to make ISC DHCP assign the prefix to a second interface. Wide DHCPv6 can be used in this application, however. There is also dibbler-client, the capabilities of which I have not had time to investigate in detail. A further consideration is whether Wide DHCpv6 is maintained upstream - it appears not to be. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#630556: HP Laserjet 2430 printer fails to print via USB after deprecating usblp support
Package: cups Version: 1.4.7-1 Followup-For: Bug #630556 After upgrading to 1.4.7-1, I can't print either with the usblp kernel module loaded or without it. >From /var/log/syslog (with usblp not loaded): Jul 15 11:18:47 jdc kernel: [ 9498.992515] usb 1-7: usbfs: process 19055 (usb) did not claim interface 1 before use Jul 15 11:18:53 jdc kernel: [ 9504.032580] usb 1-7: usbfs: process 19055 (usb) did not claim interface 1 before use Jul 15 11:18:58 jdc kernel: [ 9509.072634] usb 1-7: usbfs: process 19055 (usb) did not claim interface 1 before use Jul 15 11:19:03 jdc kernel: [ 9514.112557] usb 1-7: usbfs: process 19055 (usb) did not claim interface 1 before use Jul 15 11:19:08 jdc kernel: [ 9519.152505] usb 1-7: usbfs: process 19055 (usb) did not claim interface 1 before use Jul 15 11:19:13 jdc kernel: [ 9524.192668] usb 1-7: usbfs: process 19055 (usb) did not claim interface 1 before use Jul 15 11:19:18 jdc kernel: [ 9529.232593] usb 1-7: usbfs: process 19055 (usb) did not claim interface 1 before use Jul 15 11:19:23 jdc kernel: [ 9534.272652] usb 1-7: usbfs: process 19055 (usb) did not claim interface 1 before use Jul 15 11:19:28 jdc kernel: [ 9539.312584] usb 1-7: usbfs: process 19055 (usb) did not claim interface 1 before use Jul 15 11:19:33 jdc kernel: [ 9544.352496] usb 1-7: usbfs: process 19055 (usb) did not claim interface 1 before use I can't find any informative errors in the cups logs. The printer does nothing, i.e., no error messages there either. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.39-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages cups depends on: ii adduser 3.113add and remove users and groups ii bc 1.06.95-2The GNU bc arbitrary precision cal ii cups-client 1.4.7-1 Common UNIX Printing System(tm) - ii cups-common 1.4.7-1 Common UNIX Printing System(tm) - ii cups-ppdc 1.4.7-1 Common UNIX Printing System(tm) - ii debconf [debconf-2.0] 1.5.40 Debian configuration management sy ii ghostscript 9.02~dfsg-3 interpreter for the PostScript lan ii libacl1 2.2.51-2 Access control list shared library ii libavahi-client30.6.30-5 Avahi client library ii libavahi-common30.6.30-5 Avahi common library ii libc6 2.13-10 Embedded GNU C Library: Shared lib ii libcups21.4.7-1 Common UNIX Printing System(tm) - ii libcupscgi1 1.4.7-1 Common UNIX Printing System(tm) - ii libcupsdriver1 1.4.7-1 Common UNIX Printing System(tm) - ii libcupsimage2 1.4.7-1 Common UNIX Printing System(tm) - ii libcupsmime11.4.7-1 Common UNIX Printing System(tm) - ii libcupsppdc11.4.7-1 Common UNIX Printing System(tm) - ii libdbus-1-3 1.4.12-4 simple interprocess messaging syst ii libgcc1 1:4.6.1-3GCC support library ii libgnutls26 2.10.5-2 the GNU TLS library - runtime libr ii libgssapi-krb5-21.9.1+dfsg-1+b1 MIT Kerberos runtime libraries - k ii libijs-0.35 0.35-7 IJS raster image transport protoco ii libkrb5-3 1.9.1+dfsg-1+b1 MIT Kerberos runtime libraries ii liblcms11.18.dfsg-1.2+b4 Color management library ii libldap-2.4-2 2.4.25-1.1 OpenLDAP libraries ii libpam0g1.1.3-2 Pluggable Authentication Modules l ii libpaper1 1.1.24+nmu1 library for handling paper charact ii libpoppler130.16.7-2 PDF rendering library ii libslp1 1.2.1-7.8OpenSLP libraries ii libstdc++6 4.6.1-3 GNU Standard C++ Library v3 ii libusb-0.1-42:0.1.12-17 userspace USB programming library ii lsb-base3.2-27 Linux Standard Base 3.2 init scrip ii poppler-utils 0.16.7-2 PDF utilities (based on Poppler) ii procps 1:3.2.8-10 /proc file system utilities ii ssl-cert1.0.28 simple debconf wrapper for OpenSSL ii ttf-freefont20100919-1 Freefont Serif, Sans and Mono True ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime Versions of packages cups recommends: ii avahi-daemon 0.6.30-5Avahi mDNS/DNS-SD daemon ii cups-driver-gutenprint 5.2.6-1 printer drivers for CUPS ii foomatic-filters 4.0.7-1 OpenPrinting printer support - fil ii ghostscript-cups 9.02~dfsg-3 inter
Bug#630556: cups: HP Laserjet 2430 printer fails to print via USB after deprecating usblp support
Package: cups Version: 1.4.6-8 Severity: normal After the usblp module was blacklisted and Cups switched to its new USB handler, as of 1.4.6-8, I started experiencing problems printing to my HP LaserJet 2430 printer via the USB port, as follows. No errors were reported in syslog or /var/log/cups/error_log The data light on the printer flashed for a while, and then remained steady and the printer then failed to respond to keys pressed on its panel. The status of Cups showed that the job had been sent, but of course nothing was printed. Subsequent jobs could not be transferred to the printer. The only error messages I managed to get out of it, after several attempts, were: Jun 15 16:01:57 jdc kernel: [26582.320139] usb 1-7: usbfs: USBDEVFS_CONTROL failed cmd usb rqt 161 rq 0 len 1024 ret -110 Jun 15 16:02:07 jdc kernel: [26592.360136] usb 1-7: usbfs: USBDEVFS_CONTROL failed cmd usb rqt 161 rq 0 len 1024 ret -110 Jun 15 16:02:17 jdc kernel: [26602.400123] usb 1-7: usbfs: USBDEVFS_CONTROL failed cmd usb rqt 161 rq 0 len 1024 ret -110 Jun 15 16:02:27 jdc kernel: [26612.440117] usb 1-7: usbfs: USBDEVFS_CONTROL failed cmd usb rqt 161 rq 0 len 1024 ret -110 Most of the time, though, there were no errors reported in the log at all. Last time cups moved to usbfs and usblp was blacklisted, I remember reporting similar issues, so it seems that the problem with the new usbfs code hasn't been fixed. I'm willing to test future versions but I don't have the time/expertise to help debug the USB code. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.39-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages cups depends on: ii adduser 3.113add and remove users and groups ii bc 1.06.95-2The GNU bc arbitrary precision cal ii cups-client 1.4.6-8 Common UNIX Printing System(tm) - ii cups-common 1.4.6-8 Common UNIX Printing System(tm) - ii cups-ppdc 1.4.6-8 Common UNIX Printing System(tm) - ii debconf [debconf-2.0] 1.5.39 Debian configuration management sy ii ghostscript 9.02~dfsg-2 interpreter for the PostScript lan ii libacl1 2.2.49-5 Access control list shared library ii libavahi-client30.6.30-3 Avahi client library ii libavahi-common30.6.30-3 Avahi common library ii libc6 2.13-7 Embedded GNU C Library: Shared lib ii libcups21.4.6-8 Common UNIX Printing System(tm) - ii libcupscgi1 1.4.6-8 Common UNIX Printing System(tm) - ii libcupsdriver1 1.4.6-8 Common UNIX Printing System(tm) - ii libcupsimage2 1.4.6-8 Common UNIX Printing System(tm) - ii libcupsmime11.4.6-8 Common UNIX Printing System(tm) - ii libcupsppdc11.4.6-8 Common UNIX Printing System(tm) - ii libdbus-1-3 1.4.12-2 simple interprocess messaging syst ii libgcc1 1:4.6.0-13 GCC support library ii libgnutls26 2.10.5-1+b1 the GNU TLS library - runtime libr ii libgssapi-krb5-21.9.1+dfsg-1+b1 MIT Kerberos runtime libraries - k ii libijs-0.35 0.35-7 IJS raster image transport protoco ii libkrb5-3 1.9.1+dfsg-1+b1 MIT Kerberos runtime libraries ii liblcms11.18.dfsg-1.2+b4 Color management library ii libldap-2.4-2 2.4.25-1.1 OpenLDAP libraries ii libpam0g1.1.3-1 Pluggable Authentication Modules l ii libpaper1 1.1.24+nmu1 library for handling paper charact ii libpoppler5 0.12.4-1.2 PDF rendering library ii libslp1 1.2.1-7.8OpenSLP libraries ii libstdc++6 4.6.0-13 GNU Standard C++ Library v3 ii libusb-0.1-42:0.1.12-17 userspace USB programming library ii lsb-base3.2-27 Linux Standard Base 3.2 init scrip ii poppler-utils 0.12.4-1.2 PDF utilitites (based on libpopple ii procps 1:3.2.8-10 /proc file system utilities ii ssl-cert1.0.28 simple debconf wrapper for OpenSSL ii ttf-freefont20100919-1 Freefont Serif, Sans and Mono True ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime Versions of packages cups recommends: ii avahi-daemon 0.6.30-3Avahi mDNS/DNS-SD daemon ii cups-driver-gutenprint 5.2.6-1 printer drivers for CUPS ii foomatic-filters 4.0.7-1 OpenPrinting printer support - fil ii ghostscript-cups
Bug#623308: linux-image-2.6.38-2-amd64: Lenovo X200 laptop fails to power down under 2.6.38
Moritz Mühlenhoff wrote: > On Mon, Apr 25, 2011 at 11:29:13AM +1000, Jason White wrote: > > Laptop-mode appears to be the cause; can you reproduce the bug by enabling > > it > > on your X200? > > How did you activate the laptop mode on your system? > > If I install laptop-mode-tools, the system still powers down just fine. > laptop-mode is deactivated as part of the shutdown sequence, though. Laptop-mode was enabled on my system in the same way, namely by installing laptop-mode-tools. It should be disabled during the shutdown by the init script. I will post a follow-up if I can narrow down the cause further. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#623308: linux-image-2.6.38-2-amd64: Lenovo X200 laptop fails to power down under 2.6.38
Laptop-mode appears to be the cause; can you reproduce the bug by enabling it on your X200? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#623308: linux-image-2.6.38-2-amd64: Lenovo X200 laptop fails to power down under 2.6.38
Moritz Mühlenhoff wrote: > Hmm. I'm having a X200 myself and it powers down just fine with the current > sid kernel. Are you using laptop-mode? I'll try it without this. BIOS differences are another possibility, I suppose. Possibly relevant is the fact that acpitool reports, under 2.6.38, that the battery status and thermal readings aren't available, whereas it works under 2.6.32. However, the thermal values are present under /proc/acpi/ibm. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#623308: linux-image-2.6.38-2-amd64: Lenovo X200 laptop fails to power down under 2.6.38
I've just tested this again, and the bug is still present as of the latest package incorporating 2.6.38.4: Linux jpc2 2.6.38-2-amd64 #1 SMP Sat Apr 23 18:47:49 UTC 2011 x86_64 GNU/Linux After completing the normal shutdown (unmounting file systems, etc.), the machine appears to stop very briefly and then it reboots. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#623308: linux-image-2.6.38-2-amd64: Lenovo X200 laptop fails to power down under 2.6.38
Package: linux-2.6 Version: 2.6.38-3 Severity: normal After upgrading to 2.6.38-2-amd64, my Lenovo X200 laptop reboots instead of powering down when I run the poweroff command (or equivalently shutdown -h now). That is, the ordinary reboot/shutdown sequence takes place until the moment at which the machine should power off, but it returns to the BIOS screen and reboots instead. Reverting to 2.6.32-5 avoids the regression. -- Package-specific info: ** Version: Linux version 2.6.38-2-amd64 (Debian 2.6.38-3) (b...@decadent.org.uk) (gcc version 4.4.5 (Debian 4.4.5-15) ) #1 SMP Thu Apr 7 04:28:07 UTC 2011 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.38-2-amd64 root=UUID=dd38c010-c08f-4ff6-bce0-d81452a3aceb ro quiet ** Tainted: C (1024) * Module from drivers/staging has been loaded. ** Kernel log: [8.552237] usbcore: registered new interface driver uvcvideo [8.552239] USB Video Class driver (v1.0.0) [ 11.762974] loop: module loaded [ 11.921533] speakup: module is from the staging directory, the quality is unknown, you have been warned. [ 11.924765] input: Speakup as /devices/virtual/input/input14 [ 11.924850] speakup 3.1.6: initialized [ 11.924864] synth name on entry is: (null) [ 11.925253] initialized device: /dev/synth, node (MAJOR 10, MINOR 25) [ 11.933515] speakup_soft: module is from the staging directory, the quality is unknown, you have been warned. [ 11.934278] synth probe [ 11.934328] initialized device: /dev/softsynth, node (MAJOR 10, MINOR 26) [ 15.488233] e1000e :00:19.0: irq 44 for MSI/MSI-X [ 15.544149] e1000e :00:19.0: irq 44 for MSI/MSI-X [ 15.544509] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 16.154060] RPC: Registered udp transport module. [ 16.154063] RPC: Registered tcp transport module. [ 16.154065] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 16.274675] FS-Cache: Loaded [ 16.341248] FS-Cache: Netfs 'nfs' registered for caching [ 16.369054] Installing knfsd (copyright (C) 1996 o...@monad.swb.de). [ 17.236963] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: None [ 17.236967] e1000e :00:19.0: eth0: 10/100 speed: disabling TSO [ 17.237273] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 17.506338] fuse init (API version 7.16) [ 19.765474] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory [ 19.815238] NFSD: starting 90-second grace period [ 24.952270] Bluetooth: L2CAP ver 2.15 [ 24.952272] Bluetooth: L2CAP socket layer initialized [ 25.075718] Bluetooth: RFCOMM TTY layer initialized [ 25.075722] Bluetooth: RFCOMM socket layer initialized [ 25.075724] Bluetooth: RFCOMM ver 1.11 [ 25.387149] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 25.387151] Bluetooth: BNEP filters: protocol multicast [ 25.682655] Bluetooth: SCO (Voice Link) ver 0.6 [ 25.682658] Bluetooth: SCO socket layer initialized [ 26.068633] lp: driver loaded but no devices found [ 26.208953] ppdev: user-space parallel port driver [ 31.827819] CPUFREQ: Per core ondemand sysfs interface is deprecated - ignore_nice_load [ 32.419067] uhci_hcd :00:1a.0: PCI INT A disabled [ 32.419224] uhci_hcd :00:1a.0: power state changed by ACPI to D3 [ 32.419583] uhci_hcd :00:1a.2: PCI INT C disabled [ 32.419693] uhci_hcd :00:1a.2: power state changed by ACPI to D3 [ 32.419887] ehci_hcd :00:1a.7: PCI INT D disabled [ 32.419952] ehci_hcd :00:1a.7: PME# enabled [ 32.432180] ehci_hcd :00:1a.7: power state changed by ACPI to D3 [ 32.433207] uhci_hcd :00:1d.0: PCI INT A disabled [ 32.433321] uhci_hcd :00:1d.0: power state changed by ACPI to D3 [ 32.433845] ehci_hcd :00:1d.7: PCI INT D disabled [ 32.433910] ehci_hcd :00:1d.7: PME# enabled [ 32.452110] ehci_hcd :00:1d.7: power state changed by ACPI to D3 [ 32.586152] ehci_hcd :00:1a.7: power state changed by ACPI to D0 [ 32.600167] ehci_hcd :00:1a.7: BAR 0: set to [mem 0xf2926c00-0xf2926fff] (PCI address [0xf2926c00-0xf2926fff]) [ 32.600181] ehci_hcd :00:1a.7: power state changed by ACPI to D0 [ 32.600210] ehci_hcd :00:1a.7: restoring config space at offset 0xf (was 0x400, writing 0x40b) [ 32.600248] ehci_hcd :00:1a.7: restoring config space at offset 0x1 (was 0x290, writing 0x2900102) [ 32.600299] ehci_hcd :00:1a.7: PME# disabled [ 32.600311] ehci_hcd :00:1a.7: power state changed by ACPI to D0 [ 32.600321] ehci_hcd :00:1a.7: power state changed by ACPI to D0 [ 32.600339] ehci_hcd :00:1a.7: PCI INT D -> GSI 23 (level, low) -> IRQ 23 [ 32.600352] ehci_hcd :00:1a.7: setting latency timer to 64 [ 32.743244] ehci_hcd :00:1d.7: power state changed by ACPI to D0 [ 32.760089] ehci_hcd :00:1d.7: BAR 0: set to [mem 0xf2927000-0xf29273ff] (PCI address [0xf2927000-0xf29273ff]) [ 32.760103] ehci_hcd :00:1d.7: power state changed by ACPI to D0 [ 32.760131] ehci_hcd :00:1d.7: restoring config
Bug#254615: fedora has patches for this
Christoph Anton Mitterer wrote: > I've just seen that Fedora ships patches which add support for acls, > xattrs and selinux. > > Not sure where the canonical location for these patches is, but they can > be found here: > http://cvs.fedoraproject.org/viewvc/rpms/tar/devel/ which is now a broken link. > > Guess we should try to get them merged upstream. That would be desirable, especially now that the star package is no longer in Debian, leaving, to my knowledge, no means of reading or creating tar files with ACLs. I've logged into a Fedora system, and the ACL support is documented in tar(1). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#619996: nfs-common: idmapd.conf(5) manual page missing
Ben Hutchings wrote: > It is not included in the upstream source - even though idmapd(8) refers > to it! That's weird. Fedora have it, howver. Perhaps this is a "forward upstream" bug. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#619996: nfs-common: idmapd.conf(5) manual page missing
Package: nfs-common Version: 1:1.2.3-1 Severity: wishlist We're missing the idmapd.conf(5) manual page. I checked another distribution and found it there, however, so it does exist. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#606715: jodconverter: produces text files with CR/LF line terminators rather than LF
Package: jodconverter Version: 2.2.2-5 Severity: normal jodconverter file.doc file.txt yields a text file with CR/LF line terminators (i.e., DOS-style rather than UNIX-style LF line terminators). tr can fix this easily enough, but I shouldn't have to do it. I appreciate that this is likely to be an underlying openoffice.org issue. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.35-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages jodconverter depends on: ii gcj-4.4-jre-headless [java2 4.4.5-9 Java runtime environment using GIJ ii gcj-jre-headless [java2-run 4:4.4.5-2Java runtime environment using GIJ ii gij-4.3 [java2-runtime-head 4.3.4-4 The GNU Java bytecode interpreter ii libcommons-cli-java 1.2-3API for working with the command l ii libcommons-io-java 1.4-3Common useful IO related classes ii libjodconverter-java2.2.2-4 Office formats converter - Library ii openjdk-6-jre-headless [jav 6b18-1.8.3-2 OpenJDK Java runtime, using Hotspo jodconverter recommends no packages. jodconverter 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#587884: isc-dhcp-client: Tries to use invalid path for IPv6 leases file
Package: isc-dhcp-client Version: 4.1.1-P1-5 Severity: normal jpc2:~# dhclient -6 -v eth0 Internet Systems Consortium DHCP Client 4.1.1-P1 Copyright 2004-2010 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ can't create /var/db/dhclient6.leases: No such file or directory This should be created in the /var/lib/dhcp directory by default, as with IPv4. I hope it's a simple compile-time option or patch. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages isc-dhcp-client depends on: ii debianutils 3.2.3 Miscellaneous utilities specific t ii ifupdown 0.6.10 high level tools to configure netw ii isc-dhcp-common 4.1.1-P1-5 common files used by all the isc-d ii libc6 2.11.1-3 Embedded GNU C Library: Shared lib ii libssl0.9.8 0.9.8o-1 SSL shared libraries isc-dhcp-client recommends no packages. Versions of packages isc-dhcp-client suggests: ii avahi-autoipd 0.6.25-3 Avahi IPv4LL network address confi pn resolvconf (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#579501: lynx-cur: TLS support missing in this version
Atsuhito Kohda wrote: > Hi Jason, > > On Wed, 28 Apr 2010 14:35:58 +1000, Jason White wrote: > > > Lynx reports that the client does not support HTTPS URLS, > > which is a regression compared with previous versions. > > I can't believe there is any regression in supporting > HTTPS URLs. I don't change anything in this point. > > What difference do you see between a former version and > the latest version? Thank you for your prompt reply. This is very unusual. With the version in testing: Lynx Version 2.8.8dev.2 (25 Nov 2009) libwww-FM 2.14, SSL-MM 1.4.1,, ncurses 5.7.20100313(wide) Built on linux-gnu Apr 4 2010 00:41:35 Copyrights held by the Lynx Developers Group, the University of Kansas, CERN, and other contributors. Distributed under the GNU General Public License (Version 2). See http://lynx.isc.org/ and the online help for more information. and visiting, for example, https://www.debian.org/ works. With the version in Sid: Lynx Version 2.8.8dev.3 (25 Apr 2010) libwww-FM 2.14, ncurses 5.7.20100313(wide) Built on linux-gnu Apr 26 2010 12:56:36 Copyrights held by the Lynx Developers Group, the University of Kansas, CERN, and other contributors. Distributed under the GNU General Public License (Version 2). See http://lynx.isc.org/ and the online help for more information. the SSL library isn't mentioned in the above output, and lynx https://www.debian.org gives Alert!: This client does not contain support for HTTPS URLs. I hope this helps, and please let me know if I can assist further. With best regards, Jason. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#579501: lynx-cur: TLS support missing in this version
Package: lynx-cur Version: 2.8.8dev.3-1 Severity: normal Lynx reports that the client does not support HTTPS URLS, which is a regression compared with previous versions. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.33-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages lynx-cur depends on: ii debconf [debconf-2.0] 1.5.32 Debian configuration management sy ii libbsd0 0.2.0-1 utility functions from BSD systems ii libc6 2.10.2-7 Embedded GNU C Library: Shared lib ii libgcrypt11 1.4.5-2 LGPL Crypto library - runtime libr ii libgnutls26 2.8.6-1 the GNU TLS library - runtime libr ii libidn111.18-1 GNU Libidn library, implementation ii libncursesw55.7+20100313-2 shared libraries for terminal hand ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime Versions of packages lynx-cur recommends: ii mime-support 3.48-1 MIME files 'mime.types' & 'mailcap Versions of packages lynx-cur suggests: pn lynx-cur-wrapper (no description available) -- Configuration Files: /etc/lynx-cur/lynx.cfg changed [not included] -- 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#546397: pwsafe: Complains about not being setuid despite availability of mlock() to unprivileged processes
Iustin Pop wrote: > Pwsafe does the right thing here. mlock default limit is 64K, and pwsafe > binary requests (on my system) 69K. After increase the memlock limit, > there are no warnings anymore. Thank you; that fixed it. Perhaps it merits a note in the README file. Regards, Jason. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#575353: linux-image-2.6.33-2-amd64: 2.6.33 fails to boot - unable to mount root fs
I ran grub-install /dev/sda and (just to be sure) rebuilt the initramfs. After rebooting, kernel 2.6.33-2 loaded successfully. Thank you for the help. I don't know why everything wasn't updated automatically; perhaps grub-pc 1.98 didn't re-install itself during the upgrade. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#575353: linux-image-2.6.33-2-amd64: 2.6.33 fails to boot - unable to mount root fs
maximilian attems wrote: > upps sorry, wrong message previously got confused. > > invoke *if and only if* sda is your harddisc where boot loader is on > install-grub /dev/sda > > update-grub > > also check that you completed upgrade from grub to grub2. I can confirm the latter; Grub 2 has been working (not chain-loaded anymore) since late last year on this system. It will load 2.6.32-3 fine but not 2.6.33-2. I can re-install it if that would help. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#575353: linux-image-2.6.33-2-amd64: 2.6.33 fails to boot - unable to mount root fs
maximilian attems wrote: > aboves error message shows that there is no initramfs passed by the > bootloader. which grub or lilo do you use? Grub 2. Regenerating the initramfs is what I tried first, but it didn't help. I'll try to investigate further. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#575353: linux-image-2.6.33-2-amd64: 2.6.33 fails to boot - unable to mount root fs
Package: linux-2.6 Version: 2.6.33-1~experimental.4 Severity: normal linux-image-2.6.32-3-amd64 is fine, but linux-image-2.6.33-2-amd64 from experimental won't boot. As I can't see the screen, I'm relying on others to report the error message, which is approximately as follows. Kernel panic - unable to mount root fs on unknown-block 0,0 The root file system is XFS, specified as a UUID in /boot/grub/grub.cfg. I also tried booting with the root=/dev/sda1 kernel parameter, but this still resulted in a kernel panic with a stack trace that I wasn't able to capture. I'm planning to set up network console to obtain traces regarding a CPU clock frequency issue on an old laptop that I should be in a position to test in the next week or so, and which is the subject of another outstanding bug report of mine. If necessary, I can apply the same technique here, although it's my primary workstation in this instance and unfortunately the only recovery technique seems to be to power cycle the machine. -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: Hewlett-Packard product_name: HP xw6400 Workstation product_version: chassis_vendor: Hewlett-Packard chassis_version: bios_vendor: Hewlett-Packard bios_version: 786D4 v01.23 board_vendor: Hewlett-Packard board_name: 0A04h board_version: NA ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation 5000X Chipset Memory Controller Hub [8086:25c0] (rev 12) Subsystem: Hewlett-Packard Company Device [103c:3014] Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 00:02.0 PCI bridge [0604]: Intel Corporation 5000 Series Chipset PCI Express x4 Port 2 [8086:25e2] (rev 12) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:03.0 PCI bridge [0604]: Intel Corporation 5000 Series Chipset PCI Express x4 Port 3 [8086:25e3] (rev 12) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:04.0 PCI bridge [0604]: Intel Corporation 5000X Chipset PCI Express x16 Port 4-7 [8086:25fa] (rev 12) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:05.0 PCI bridge [0604]: Intel Corporation 5000 Series Chipset PCI Express x4 Port 5 [8086:25e5] (rev 12) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:06.0 PCI bridge [0604]: Intel Corporation 5000 Series Chipset PCI Express x4 Port 6 [8086:25e6] (rev 12) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:07.0 PCI bridge [0604]: Intel Corporation 5000 Series Chipset PCI Express x4 Port 7 [8086:25e7] (rev 12) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:10.0 Host bridge [0600]: Intel Corporation 5000 Series Chipset FSB Registers [8086:25f0] (rev 12) Subsystem: Hewlett-Packard Company Device [103c:3014] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbo
Bug#573955: (openswan: starts before eth0 acquires IPv6 address)
ipsec auto --status | grep eth0 is as follows after boot: 000 interface eth0/eth0 192.168.0.2 After restarting the daemon: 000 interface eth0/eth0 2001:44b8:702a:4770::2 000 interface eth0/eth0 192.168.0.2 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#573955: openswan: starts before eth0 acquires IPv6 address
Package: openswan Version: 1:2.6.23+dfsg-1 Severity: normal I can reproduce this both on my desktop machine and in a KVM guest. When OpenSwan starts up during boot, it fails to acquire the IPv6 address assigned to my eth0 interface. Consequently, the IPv6 tunnels defined in /etc/ipsec.conf (with auto=start) fail to start. I am using dependency-based boot sequencing. If I later run service ipsec restart, the IPv6 address is acquired and the tunnels are brought up. On my desktop machine, the IPv6 address is assigned, as static, in /etc/network/interfaces; in the KVM guest it is obtained via auto-configuration. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages openswan depends on: ii bind9-host [host] 1:9.7.0.dfsg.1-1 Version of 'host' bundled with BIN ii bsdmainutils8.0.8collection of more utilities from ii debconf [debconf-2.0] 1.5.28 Debian configuration management sy ii debianutils 3.2.2Miscellaneous utilities specific t ii iproute 20100224-3 networking and traffic control too ii libc6 2.10.2-6 Embedded GNU C Library: Shared lib ii libcurl37.20.0-1 Multi-protocol file transfer libra ii libgmp3c2 2:4.3.2+dfsg-1 Multiprecision arithmetic library ii libldap-2.4-2 2.4.17-2.1 OpenLDAP libraries ii libpam0g1.1.1-2 Pluggable Authentication Modules l ii openssl 0.9.8m-2 Secure Socket Layer (SSL) binary a openswan recommends no packages. Versions of packages openswan suggests: ii curl 7.20.0-1 Get a file from an HTTP, HTTPS or pn openswan-modules-source | lin (no description available) -- debconf information: openswan/existing_x509_key_filename: openswan/x509_state_name: openswan/rsa_key_length: 2048 openswan/restart: true openswan/start_level: earliest openswan/enable-oe: false * openswan/existing_x509_certificate: false openswan/existing_x509_certificate_filename: * openswan/create_rsa_key: true openswan/x509_email_address: openswan/x509_country_code: AT * openswan/x509_self_signed: true openswan/x509_organizational_unit: openswan/x509_locality_name: openswan/x509_common_name: * openswan/rsa_key_type: x509 openswan/x509_organization_name: -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#505382: binaries are missing man pages
Package: libnss3-tools Version: 3.12.5-2 Severity: normal There is documentation at http://www.mozilla.org/projects/security/pki/nss/tools/ but it still needs to be provided under a suitable licence and included in the package - preferably, converted to manual pages. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#516991: dnssec-conf and dnssec look-up for Debian
I notice this bug is still open. Has it been decided whether to package dnssec-conf or, if not, how dnssec look-up should be configured under debian? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#562025: linux-image-2.6.32-trunk-amd64: After boot, the current virtual console is not TTY1
Package: linux-2.6 Version: 2.6.32-2 Severity: normal I am experiencing the problem described here: http://article.gmane.org/gmane.linux.kernel/927536/ after upgrading to the 2.6.32 kernel. The symptom is that after boot, the current virtual console is not tty1, but instead, for example, tty6 or tty3 (apparently randomly). -- Package-specific info: ** Version: Linux version 2.6.32-trunk-amd64 (Debian 2.6.32-2) (b...@decadent.org.uk) (gcc version 4.3.4 (Debian 4.3.4-6) ) #1 SMP Thu Dec 17 06:29:18 UTC 2009 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-trunk-amd64 root=UUID=7e6b3589-6e9d-49d9-845e-80bc54b055cb ro quiet ** Not tainted ** Kernel log: [9.083243] mptsas: ioc0: attaching raid volume, channel 1, id 0 [9.083736] scsi 6:1:0:0: Direct-Access LSILOGIC Logical Volume 3000 PQ: 0 ANSI: 2 [9.092062] sd 6:1:0:0: [sda] 285155328 512-byte logical blocks: (145 GB/135 GiB) [9.092296] sd 6:1:0:0: [sda] Write Protect is off [9.092300] sd 6:1:0:0: [sda] Mode Sense: 03 00 00 08 [9.092695] sd 6:1:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [9.093693] sda: sda1 [9.103095] sd 6:1:0:0: [sda] Attached SCSI disk [9.242615] device-mapper: uevent: version 1.0.3 [9.242735] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-de...@redhat.com [9.267685] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled [9.268689] SGI XFS Quota Management subsystem [9.277879] XFS mounting filesystem sda1 [9.339085] Ending clean XFS mount for filesystem: sda1 [ 10.853606] udev: starting version 149 [ 11.385131] pci_hotplug: PCI Hot Plug PCI Core version: 0.5 [ 11.392178] ACPI Error (dsfield-0143): [CAPD] Namespace lookup failure, AE_ALREADY_EXISTS [ 11.392185] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0._OSC] (Node 88013fa3f9a0), AE_ALREADY_EXISTS [ 11.392214] ACPI Warning for \_SB_.PCI0._OSC: Parameter count mismatch - ASL declared 5, ACPI requires 4 (20090903/nspredef-336) [ 11.392338] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 [ 11.401913] ACPI: WMI: Mapper loaded [ 11.522203] parport_pc 00:07: reported by Plug and Play ACPI [ 11.522259] parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE] [ 11.745899] RME Digi9652 (Hammerfall) :01:04.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [ 11.775416] ACPI: SSDT bffe95de 008C4 (v01 COMPAQ CPU_TM2 0001 MSFT 010E) [ 11.775765] processor LNXCPU:00: registered as cooling_device0 [ 11.776026] processor LNXCPU:01: registered as cooling_device1 [ 11.776417] processor LNXCPU:02: registered as cooling_device2 [ 11.776691] processor LNXCPU:03: registered as cooling_device3 [ 11.846275] intel_rng: Firmware space is locked read-only. If you can't or [ 11.846276] intel_rng: don't want to disable this in firmware setup, and if [ 11.846277] intel_rng: you are certain that your system has a functional [ 11.846279] intel_rng: RNG, try using the 'no_fwh_detect' option. [ 11.972654] usbcore: registered new interface driver snd-usb-audio [ 12.082608] alloc irq_desc for 21 on node -1 [ 12.082611] alloc kstat_irqs on node -1 [ 12.082619] HDA Intel :00:1b.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21 [ 12.082674] HDA Intel :00:1b.0: setting latency timer to 64 [ 12.183050] EDAC MC: Ver: 2.1.0 Dec 17 2009 [ 12.232045] input: HDA Digital PCBeep as /devices/pci:00/:00:1b.0/input/input6 [ 12.234922] EDAC MC0: Giving out device to 'i5000_edac.c' 'I5000': DEV :00:10.0 [ 12.234943] EDAC PCI0: Giving out device to module 'i5000_edac' controller 'EDAC PCI controller': DEV ':00:10.0' (POLLED) [ 13.376934] loop: module loaded [ 13.400237] scsi 6:0:0:0: Attached scsi generic sg0 type 0 [ 13.400351] scsi 6:0:1:0: Attached scsi generic sg1 type 0 [ 13.400416] sd 6:1:0:0: Attached scsi generic sg2 type 0 [ 13.412838] smsc47b397: found SMSC SCH5307-NS (base address 0x0480, revision 0) [ 13.412866] ACPI: I/O resource smsc47b397 [0x480-0x481] conflicts with ACPI region SIOH [0x480-0x48f] [ 13.412921] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 13.456511] coretemp coretemp.0: Using relative temperature scale! [ 13.456621] coretemp coretemp.1: Using relative temperature scale! [ 13.456725] coretemp coretemp.2: Using relative temperature scale! [ 13.456842] coretemp coretemp.3: Using relative temperature scale! [ 13.523131] tun: Universal TUN/TAP device driver, 1.6 [ 13.523134] tun: (C) 1999-2004 Max Krasnyansky [ 13.544796] input: PC Speaker as /devices/platform/pcspkr/input/input7 [ 14.065621] Error: Driver 'pcspkr' is already registered, aborting... [ 14.530673] fuse init (API version 7.13) [ 16.170234] alloc irq_desc for 33 on node -1 [ 16.170238] alloc kstat_irqs on node -1 [ 16.170455] tg3 :1f:0
Bug#561225: coreutils: cp --reflink fails with Btrfs file system
>From discussion on the Btrfs list, the reason for this behaviour is that, if the file is empty (thus containing no data extents) the ioctl() call returns EINVAL. It has been suggested on the Btrfs list that it should return success instead, so that the caller doesn't have to check for the empty file case. The problem originally arose for me when I attempted cp -r --reflink directory /tmp/destination where directory contained what turned out, on inspection, to be empty files (I didn't realize these were all empty files - it was a source code tree from a project I downloaded.) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#561225: cp --reflink with Btrfs
Josef Bacik wrote:
>On Sun, Dec 13, 2009 at 12:29:03AM +0000, Jason White wrote:
>> I am testing a Btrfs root file system with Debian (kernel 2.6.32) under KVM.
>>
>> ja...@vrtl:~$ touch testfile
>> ja...@vrtl:~$ cp --reflink testfile /tmp
>> cp: failed to clone `/tmp/testfile': Invalid argument
>>
>> This is with GNU Coreutils 8.0 taken from debian Sid.
>>
>> Is this a Coreutils issue, a Btrfs problem or something in my local
>> configuration?
>>
>
>Try using bcp, if that works then its likely a problem with coreutils.
After reporting this to Debian and engaging on follow-up discussion, it turns
out that bcp copies the data if the ioctl() call to clone the file fails, as
can be seen from the Python code (which I should have read, but didn't...).
Unfortunately the ioctl() call is failing both in bcp and in cp --reflink.
Here's partial strace output from the latter.
cp --reflink testfile testfile2
open("testfile", O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0
open("testfile2", O_WRONLY|O_CREAT|O_EXCL, 0644) = 4
fstat(4, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0
ioctl(4, 0x40049409, 0x3) = -1 EINVAL (Invalid argument)
Kernel 2.6.32 (debian Sid), x86-64 architecture.
Suggestions welcome.
Debian bug report:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=561225
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#561225: coreutils: cp --reflink fails with Btrfs file system
Jim Meyering wrote:
> Can you rerun that via strace and send the log at least
> to the bug-coreutils list (Cc'd)?
>
> strace -o log cp --reflink testfile testfile2
It opens both files and then performs the ioctl() call:
ioctl(4, 0x40049409, 0x3) = -1 EINVAL (Invalid argument)
>
> Even better, can you do that using stock upstream coreutils-8.2,
> assuming it still fails?
This may not be necessary. If I run strace on bcp, it turns out that its
ioctl() call encounters the same error:
ioctl(3, 0x40049409, 0x4) = -1 EINVAL (Invalid argument)
and thus the suggestion that bcp (by behaving like --reflink=auto) is masking
the issue appears to be exactly on point.
execve("/bin/cp", ["cp", "--reflink", "testfile", "testfile2"], [/* 17 vars
*/]) = 0
brk(0) = 0x23ca000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7fbb485b4000
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7fbb485b2000
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=25245, ...}) = 0
mmap(NULL, 25245, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fbb485ab000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/lib/libselinux.so.1", O_RDONLY) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0 ]\0\0\0\0\0\0"..., 832)
= 832
fstat(3, {st_mode=S_IFREG|0644, st_size=113736, ...}) = 0
mmap(NULL, 2213640, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x7fbb4817c000
mprotect(0x7fbb48197000, 2093056, PROT_NONE) = 0
mmap(0x7fbb48396000, 8192, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1a000) = 0x7fbb48396000
mmap(0x7fbb48398000, 1800, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7fbb48398000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/lib/libacl.so.1", O_RDONLY) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\360\36\0\0\0\0\0\0"...,
832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=30472, ...}) = 0
mmap(NULL, 2125648, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x7fbb47f75000
mprotect(0x7fbb47f7c000, 2093056, PROT_NONE) = 0
mmap(0x7fbb4817b000, 4096, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x6000) = 0x7fbb4817b000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/lib/libattr.so.1", O_RDONLY) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0p\24\0\0\0\0\0\0"...,
832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=17808, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7fbb485aa000
mmap(NULL, 2112952, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x7fbb47d71000
mprotect(0x7fbb47d75000, 2093056, PROT_NONE) = 0
mmap(0x7fbb47f74000, 4096, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x3000) = 0x7fbb47f74000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/lib/libc.so.6", O_RDONLY)= 3
read(3,
"\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\320\353\1\0\0\0\0\0"..., 832) =
832
fstat(3, {st_mode=S_IFREG|0755, st_size=1379752, ...}) = 0
mmap(NULL, 3487784, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x7fbb47a1d000
mprotect(0x7fbb47b67000, 2097152, PROT_NONE) = 0
mmap(0x7fbb47d67000, 20480, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x14a000) = 0x7fbb47d67000
mmap(0x7fbb47d6c000, 18472, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7fbb47d6c000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/lib/libdl.so.2", O_RDONLY) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\340\r\0\0\0\0\0\0"...,
832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=14696, ...}) = 0
mmap(NULL, 2109696, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x7fbb47819000
mprotect(0x7fbb4781b000, 2097152, PROT_NONE) = 0
mmap(0x7fbb47a1b000, 8192, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x2000) = 0x7fbb47a1b000
close(3)= 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7fbb485a9000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7fbb485a8000
arch_prctl(ARCH_SET_FS, 0x7fbb485a8790) = 0
mprotect(0x7fbb47a1b000, 4096, PROT_READ) = 0
mprotect(0x7fbb47d67000, 16384, PROT_READ) = 0
mprotect(0x7fbb48396000, 4096, PROT_READ) = 0
mprotect(0x7fbb485b5000, 4096, PROT_READ) = 0
munmap(0x7fbb48
Bug#561225: coreutils: cp --reflink fails with Btrfs file system
Package: coreutils Version: 8.0-2 Severity: normal ja...@vrtl:~$ touch testfile ja...@vrtl:~$ cp --reflink testfile testfile2 cp: failed to clone `testfile2': Invalid argument I am running kernel 2.6.32 with a Btrfs root file system under KVM, x86-64 architecture. It was suggested on the Btrfs mailing list that I test file cloning by running the bcp demonstration script provided as part of btrfs-progs (available from a Btrfs Git repository). In my test, bcp was able to clone a file, suggesting that this may be a Coreutils bug rather than a kernel issue. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (990, 'unstable'), (800, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages coreutils depends on: ii libacl1 2.2.49-1 Access control list shared library ii libattr1 1:2.4.44-1 Extended attribute shared library ii libc6 2.10.2-2 GNU C Library: Shared libraries ii libselinux1 2.0.89-4 SELinux runtime shared libraries coreutils recommends no packages. coreutils 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#560272: initramfs-tools: fails to mount BTRFS root file system under KVM
maximilian attems wrote: > you could simply use rootfstype bootarg, > as described in man initramfs-tools. My mistake was to enter it in uppercase (corresponding to the name of the environment variable in the script) rather than in lowercase as I should have done. It works now. Thanks. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#560272: initramfs-tools: fails to mount BTRFS root file system under KVM
Editing scripts.local to hard-code the file system type worked around this bug. I suppose this is now a wishlist bug for Btrfs file system type detection. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#560272: initramfs-tools: fails to mount BTRFS root file system under KVM
Package: initramfs-tools Version: 0.93.4 Severity: wishlist To experiment with BTRFS as the root file system under KVM, I added btrfs and associated modules to /etc/initramfs-tools/modules and built an initrd image, which I then installed to an EXT3 partition in the QCOW2 image to be loaded by KVM. Grub 2 is used as the boot loader, Debian kernel 2.6.32-trunk-amd64. Btrfs is the root file system. (/boot on /dev/hda1, / on /dev/hda2). The initrd fails with a "no such device" error mounting the root file system and exits to the initrd shell environment. If I then mount the root file system manually: mount /dev/hda2 /root it succeeds, which shows that the btrfs modules are working. Since Btrfs remains experimental, this is probably a low-priority issue, so I've set it to wishlist for now (you're welcome to change this if appropriate, of course.) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
