Bug#825292: grub-common: does not provide the correct device name for booting the Hurd.
El 30/5/2016 21:07, "Samuel Thibault" escribió: > > Yes, that should be correct. Note that it's the 30_os-prober.in file > which needs to be modified. Also, since this is an upstream file, you > should probably contact upstream to get it integrated there, so Debian > doesn't maintain the change ad æternam. > Ok. Reported upstream at: http://savannah.gnu.org/bugs/?48068
Bug#825292: grub-common: does not provide the correct device name for booting the Hurd.
On Wed, May 25, 2016 at 11:20 PM, Samuel Thibault
wrote:
>
> Why adding another variable, instead of just fixing mach_device? I
> guess grub-probe simply changed something and the mach_device definition
> needs to be updated.
>
> This is really meant to be a mach device name, not a "hurd device name".
>
> Samuel
>
I understand. I did not know the exact terminology. So the patch might boil
down to:
-
--- 30_os-prober2016-02-05 18:30:35.0 +0100
+++ 30_os-prober-32016-05-26 11:54:35.819822599 +0200
@@ -331,7 +331,7 @@
save_default_entry | grub_add_tab
prepare_grub_to_access_device ${DEVICE} | grub_add_tab
grub_device="`${grub_probe} --device ${DEVICE} --target=drive`"
- mach_device="`echo "${grub_device}" | sed -e
's/(\(hd.*\),msdos\(.*\))/\1s\2/'`"
+ mach_device=`${grub_probe} --device ${DEVICE}
--target=compatibility_hint | sed 's/,msdos/s/'`
grub_fs="`${grub_probe} --device ${DEVICE} --target=fs`"
case "${grub_fs}" in
*fs)hurd_fs="${grub_fs}" ;;
-
So this is one more step to get working flawlessly and out of the box the
procedure at:
https://www.gnu.org/software/hurd/hurd/running/debian/CrossInstall.html
It remains at least to determine whether --readonly is needed, and maybe to
provide a way to boot in single user mode (-s) (needed for the first two
reboots).
By the moment it does not work out of the box yet because of these and
maybe other issues.
Rodrigo.
Bug#825292: grub-common: does not provide the correct device name for booting the Hurd.
Package: grub-common
Version: 2.02~beta2-22+deb8u1
Severity: normal
Tags: patch
The script /etc/grub.d/30_os-prober does not provide the correct device name
for booting the Hurd, e.g. when installed with crosshurd.
The bug also applies to the grub version currently in sid.
The patch changes provided device names from, e.g.:
(hostdisk//dev/sda,msdos2)
to:
hd0s2
This is the patch that solved the problem in my case, and may be correct:
-
--- 30_os-prober2016-02-05 18:30:35.0 +0100
+++ 30_os-prober-2 2016-05-25 17:13:17.518318125 +0200
@@ -332,13 +332,14 @@
prepare_grub_to_access_device ${DEVICE} | grub_add_tab
grub_device="`${grub_probe} --device ${DEVICE} --target=drive`"
mach_device="`echo "${grub_device}" | sed -e
's/(\(hd.*\),msdos\(.*\))/\1s\2/'`"
+ hurd_device=`${grub_probe} --device ${DEVICE}
--target=compatibility_hint | sed 's/,msdos/s/'`
grub_fs="`${grub_probe} --device ${DEVICE} --target=fs`"
case "${grub_fs}" in
*fs)hurd_fs="${grub_fs}" ;;
*) hurd_fs="${grub_fs}fs" ;;
esac
cat << EOF
- multiboot /boot/gnumach.gz root=device:${mach_device}
+ multiboot /boot/gnumach.gz root=device:${hurd_device}
module /hurd/${hurd_fs}.static ${hurd_fs} --readonly \\
--multiboot-command-line='\${kernel-command-line}' \\
--host-priv-port='\${host-port}' \\
-
Bug#825229: crosshurd: Incompatibility with update-grub. Fails to boot.
Package: crosshurd Version: 1.7.50 Severity: normal Tags: patch Running crosshurd to install in a disk partition and then running update-grub, rebooting and selecting the Hurd entry, fails to boot because the Grub does not find /boot/gnumach.gz (there is /boot/gnumach-1.6-486.gz). The following patch solves the problem in my case: - --- makehurddir.sh 2016-05-22 16:28:32.0 +0200 +++ makehurddir2.sh 2016-05-24 21:25:48.678706572 +0200 @@ -43,6 +43,8 @@ if [ -e $TARGET/var/cache/apt/archives/gnumach-image-1.6-486_* ] ; then extract gnumach-image-1.6-486 +# place symlink for compatibility with update-grub (/etc/grub.d/30_os-prober) +ln -s gnumach-1.6-486.gz "$TARGET/boot/gnumach.gz" fi if [ -e $TARGET/var/cache/apt/archives/libbz2-1.0_* ] ; then - Afterwards, the Hurd starts to boot but fails (hangs) with the following error (maybe an issue with partition names): start ext2fs: ext2fs: device:(hostdisk//dev/sda,msdos2): No such device or address Also I have observed that, running "grep TARGET /usr/share/crosshurd/*" yields some results with "$TARGET/..." quoted and some others not, so if we run crosshurd with a path with spaces, it may fail. -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=gl_ES.utf8, LC_CTYPE=gl_ES.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages crosshurd depends on: ii dialog1.2-20140911-1 ii dpkg-dev 1.17.26 Versions of packages crosshurd recommends: pn attr crosshurd suggests no packages. -- no debconf information
Bug#598427:
This bug also affects current version in unstable.
If you choose a base-unexistent path in crosshurd,
which subsequently will be passed to makehurddir.sh,
makehurddir.sh will call readlink -f,
which may return an empty string in some cases,
thus $TARGET will be "", so commands like:
cp /etc/resolv.conf "$TARGET/etc/resolv.conf"
will end up overwriting some of root filesystem's files.
Do not try this as root !!!
Here is a possible patch for makehurddir.sh:
--- a/makehurddir.sh2016-02-21 23:28:54.0 +0100
+++ b/makehurddir.sh2016-05-18 17:07:46.578718033 +0200
@@ -10,6 +10,11 @@
DEB_TARGET_GNU_CPU=$2
DEB_TARGET_GNU_SYSTEM=$3
+if [ x"$TARGET" = x ]; then
+ echo "Refused to overwrite inexistent/empty TARGET."
+ exit 1
+fi
+
. /usr/share/crosshurd/functions
debs=`cat /etc/crosshurd/packages/{common,$DEB_TARGET_GNU_SYSTEM} |
grep -v '^#'`
Bug#508729: #508729 - nautilus: cannot delete files under a NFS-mounted volume
> Is it a remote drive ? maybe those drives do not support trash idk. Yes, it was a remote drive. Maybe that is the case. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#508729: #508729 - nautilus: cannot delete files under a NFS-mounted volume
> Could you please still reproduce this issue with newer nautilus version > like 3.4.2-1+build1 or 3.8.2-3 ? Hi Pedro, I did a quick test with nautilus 3.4.2-1+build1 (Debian 7.6) and it seems ok; works well. It warns about: Cannot move file to trash, do you want to delete immediately? The file "b" cannot be moved to the trash. but then I can delete files. So maybe the bug no longer affects nautilus. Thanks. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#689983: python-twisted: does not fully support IPv6
Package: python-twisted Version: 10.1.0 Severity: normal Tags: ipv6 The version of Twisted in Squeeze does not support IPv6. Version 12.0.0 supports it partially, and versions 12.1.0 and 12.2.0 support it better. Currently only version 12.0.0 is in testing/Wheezy so it is not clear whether it will pass the IPv6 release goal. see: http://twistedmatrix.com/trac/browser/tags/releases/twisted-12.2.0/NEWS?format=raw http://twistedmatrix.com/trac/wiki/IPv6 -- System Information: Debian Release: 6.0.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-0.bpo.3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#613863: brasero: creates an invalid .cue file in order to burn an audio CD
Package: brasero Version: 2.30.3-2 Severity: important when creating an audio CD from some .flac files, brasero creates an invalid .cue file and BraseroCdrdao refuses to burn it. it seems that the problem is an invalid fraction of second written in the .cue file: 75/75, in track 13. below is a relevant fragment of brasero .log file and the .cue file: BraseroCdrdao called brasero_job_get_action BraseroCdrdao getting varg BraseroCdrdao called brasero_job_get_action BraseroCdrdao called brasero_job_get_current_track BraseroCdrdao got varg: BraseroCdrdao deactivating BraseroCdrdao called brasero_job_get_action BraseroCdrdao getting varg BraseroCdrdao called brasero_job_get_action BraseroCdrdao called brasero_job_get_input_type BraseroCdrdao called brasero_job_get_current_track BraseroCdrdao called brasero_job_get_bus_target_lun BraseroCdrdao called brasero_job_get_flags BraseroCdrdao called brasero_job_get_flags BraseroCdrdao called brasero_job_get_speed BraseroCdrdao called brasero_job_set_use_average_rate BraseroCdrdao called brasero_job_set_current_action BraseroCdrdao got varg: cdrdao write --device /dev/sr0 -n -v 2 --speed 10 /tmp/brasero_tmp_GWRXQV.cue BraseroCdrdao Launching command in /tmp BraseroCdrdao called brasero_job_get_fd_in BraseroCdrdao called brasero_job_get_fd_out BraseroCdrdao stderr: WARNING: Environment variable 'HOME' not defined- cannot $ BraseroCdrdao called brasero_job_get_action BraseroCdrdao called brasero_job_get_action BraseroCdrdao called brasero_job_get_current_track BraseroCdrdao stderr: Cdrdao version 1.2.3 - (C) Andreas Mueller (no description available) pn vcdimager (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#568822: Gnome shows the login screen on shutdown
Package: gdm Version: 2.20.11-2 Severity: normal I have a similar problem in testing: when I select shutdown from gnome or from login window, sometimes shuts down, sometimes not. When it does not shutdown, it shows the virtual terminal 1, and nothing happens. If I execute after: # shutdown -h now the system shuts down but takes more time than normal, and complains about gdm and other processes not being terminated. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=gl_ES.UTF-8, LC_CTYPE=gl_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gdm depends on: ii adduser 3.112add and remove users and groups ii debconf [debconf-2.0] 1.5.36 Debian configuration management sy ii gksu2.0.2-5 graphical frontend to su ii gnome-session [x-session-ma 2.30.2-3 The GNOME Session Manager - GNOME ii gnome-terminal [x-terminal- 2.30.2-1 The GNOME terminal emulator applic ii libart-2.0-22.3.21-1 Library of functions for 2D graphi ii libatk1.0-0 1.30.0-1 The ATK accessibility toolkit ii libattr11:2.4.44-2 Extended attribute shared library ii libaudit0 1.7.13-1+b2 Dynamic library for security audit ii libc6 2.11.2-7 Embedded GNU C Library: Shared lib ii libcairo2 1.8.10-6 The Cairo 2D vector graphics libra ii libdbus-1-3 1.2.24-3 simple interprocess messaging syst ii libdbus-glib-1-20.88-2 simple interprocess messaging syst ii libdmx1 1:1.1.0-2X11 Distributed Multihead extensio ii libfontconfig1 2.8.0-2.1generic font configuration library ii libfreetype62.4.2-2.1FreeType 2 font engine, shared lib ii libglade2-0 1:2.6.4-1library to load .glade files at ru ii libglib2.0-02.24.2-1 The GLib library of C routines ii libgnomecanvas2-0 2.30.1-1 A powerful object-oriented display ii libgtk2.0-0 2.20.1-2 The GTK+ graphical user interface ii libpam-modules 1.1.1-6.1Pluggable Authentication Modules f ii libpam-runtime 1.1.1-6.1Runtime support for the PAM librar ii libpam0g1.1.1-6.1Pluggable Authentication Modules l ii libpango1.0-0 1.28.3-1 Layout and rendering of internatio ii librsvg2-2 2.26.3-1 SAX-based renderer library for SVG ii librsvg2-common 2.26.3-1 SAX-based renderer library for SVG ii libselinux1 2.0.96-1 SELinux runtime shared libraries ii libwrap07.6.q-19 Wietse Venema's TCP wrappers libra ii libx11-62:1.3.3-4X11 client-side library ii libxau6 1:1.0.6-1X11 authorisation library ii libxdmcp6 1:1.0.3-2X11 Display Manager Control Protoc ii libxext62:1.1.2-1X11 miscellaneous extension librar ii libxi6 2:1.3-5 X11 Input extension library ii libxinerama12:1.1-3 X11 Xinerama extension library ii libxml2 2.7.8.dfsg-1 GNOME XML library ii lsb-base3.2-23.1 Linux Standard Base 3.2 init scrip ii metacity [x-window-manager] 1:2.30.1-3 lightweight GTK+ window manager ii twm [x-window-manager] 1:1.0.4-2Tab window manager ii xterm [x-terminal-emulator] 261-1X terminal emulator Versions of packages gdm recommends: ii gdm-themes0.6.2 Themes for the GNOME Display Manag ii whiptail 0.52.11-1 Displays user-friendly dialog boxe pn xserver-xephyr | xnest (no description available) ii xserver-xorg 1:7.5+8the X.Org X server ii zenity2.30.0-1 Display graphical dialog boxes fro Versions of packages gdm suggests: ii libpam-gnome-keyring 2.30.3-4 PAM module to unlock the GNOME key ii locales 2.11.2-7 Embedded GNU C Library: National L ii pm-utils 1.3.0-3utilities and scripts for power ma -- debconf information: gdm/daemon_name: /usr/sbin/gdm * shared/default-x-display-manager: gdm -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#574169: suggestion
On Tue, Apr 13, 2010 at 5:51 PM, Andres Cimmarusti wrote: > I have a similar card (also the xpress 200m), I will try to reproduce this > bug. However, Rodrigo's Xorg0.log shows all these warnings and errors. > > (WW) RADEON(0): Direct rendering disabled > > (II) RADEON(0): XAA Render acceleration unsupported on Radeon 9500/9700 and > newer. Please use EXA instead. > (II) RADEON(0): Render acceleration disabled > > [355167.718141] [drm] Loading R300 Microcode > [355167.818662] [drm:radeon_do_init_cp] *ERROR* Failed to load firmware! > > > Perhaps these need to be addressed to fix your other issue. Please install > libdrm-radeon1, firmaware-linux, firmware-linux-nonfree. Also use EXA in > your xorg.conf > > For example: > > Section "ServerLayout" > > Identifier "Default Layout" > Screen "Default Screen" > EndSection > > Section "Device" > Identifier "ATI Radeon Xpress 200M" > Driver "radeon" > > BusID "PCI:1:5:0" > Option "AccelMethod" "EXA" > Option "AccelDFS" "1" > Option "EnablePageFlip""1" > Option "Monitor-LVDS" "Internal Monitor" > > EndSection > > Section "Monitor" > Identifier "Internal Monitor" > EndSection > > Section "Screen" > Identifier "Default Screen" > Device "ATI Radeon Xpress 200M" > > Monitor "Internal Monitor" > DefaultDepth24 > SubSection "Display" > Depth 24 > Virtual 2560 1824 > EndSubSection > EndSection > > Please report back! > > Andres > Hi, I did the changes proposed, and now the laptop has microcode, direct rendering and EXA acceleration. Since then, the dim issue did not happen again. But today I had a system freeze while the display was locked; completely frozen; not responding to any key. -- Rodrigo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#574169: xserver-xorg-video-radeon: dims display after some days of uptime
Last days I upgraded xserver-xorg-video-radeon to version 1:6.12.6-1 and yesterday I got the same problem: a quite dark screen. Moreover, today I found the system frozen, not responding to keyboard (not even NumLock). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#574169: xserver-xorg-video-radeon: dims display after some days of uptime
2010/3/18 Michel Dänzer > > On Tue, 2010-03-16 at 22:03 +0100, Rodrigo Valiña Gutiérrez wrote: > > Package: xserver-xorg-video-radeon > > Version: 1:6.12.4-2local1 > > Severity: normal > > > > After the laptop spends some days on, and the screensaver activated > > and locked the screen several times, the display goes dark, > > with no apparent solution. > > Restarting server or starting a new session as another user provides > > a normal display, e.g. a dark display at CTRL-ALT-F7 and a normal > > display at CTRL-ALT-F8. > > The screen is dark, but not completely dark, and I am able to unlock > > the screen and see the desktop, but much darker than normal. > > The only thing that seems at normal bright is the mouse pointer. > > Can you fix the darkness e.g. with xgamma? > No, I can't. I tried in a normal display and the effect of xgamma is not the same as the effect of the bug. Yesterday I upgraded linux kernel to 2.6.32-9 and xserver-xorg-video-radeon to 1:6.12.5-1, and then rebooted. Today, after a day of uptime, I have again my graphical session locked and this time completely black. Another session that is open has no problem at the moment. Now xgamma does nothing. My session shows everything black except the mouse pointer. I can see the mouse pointer changing shape when it is over the (now invisible) password entry of the screensaver. I think I unlocked the screen, entering the password, but everything is black except the mouse pointer, now with more variety of shapes. Now I think I have to kill the session... -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#574169: xserver-xorg-video-radeon: dims display after some days of uptime
On Tue, Mar 16, 2010 at 10:58 PM, Brice Goglin wrote: > Rodrigo Valiña Gutiérrez wrote: > > Package: xserver-xorg-video-radeon > > Version: 1:6.12.4-2local1 > > Severity: normal > > > > After the laptop spends some days on, and the screensaver activated > > and locked the screen several times, the display goes dark, > > with no apparent solution. > > Restarting server or starting a new session as another user provides > > a normal display, e.g. a dark display at CTRL-ALT-F7 and a normal > > display at CTRL-ALT-F8. > > The screen is dark, but not completely dark, and I am able to unlock > > the screen and see the desktop, but much darker than normal. > > The only thing that seems at normal bright is the mouse pointer. > > > > My local version is the same as 1:6.12.4-2 but with the patch in: > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=561942 > > > > This patch is in 1:6.12.4-3. And there's even 6.12.5 in testing and > 6.12.6 in unstable now. Please test them. If they don't help, please try > 6.12.192 from experimental, and maybe with KMS froma recent kernel too. > > Brice > > I think the patch I mentioned has nothing to do with the bug I reported, I only mentioned it because I patched the package meanwhile the patch was not available in testing. And the patch works (for its bug). Soon I will upgrade to 6.12.5 or later. The bug I reported was about the screen that darks or even gets completely black (and unusable) after some days of uptime. It is hard to reproduce because it may spend several days before it appears. When I upgrade the radeon driver I will look whether this behaviour continues. -- Rodrigo
Bug#561942: xserver-xorg-video-radeon: Radeon 200M (RS4XX) freezes on xorg startup
The patch worked for me: no more system freezes when switching VT. Please take it into account. amd64 testing 01:05.0 VGA compatible controller [0300]: ATI Technologies Inc RS482 [Radeon Xpress 200M] [1002:5975] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#561942: xserver-xorg-video-radeon: Radeon 200M (RS4XX) freezes on xorg startup
Hi, I have a similar problem: system freezes after several (5-10) VT switches to/from an X session. This happens since today's upgrade from lenny to testing. my card is: 01:05.0 VGA compatible controller: ATI Technologies Inc RS482 [Radeon Xpress 200M] I will try the proposed patch to see whether it works for me. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#551991: python-vtk: Segmentation Fault when adding a scene
Package: python-vtk Version: 5.0.4-1.1 Severity: important A simple wx python app that uses python-vtk and libvtk5 crashes when doing the following: Add a scene (in a tab/notebook) to the window. Close that tab. Add another scene. The program outputs the following: (python:4635): Gtk-CRITICAL **: gtk_widget_set_colormap: assertion `!GTK_WIDGET_REALIZED (widget)' failed (python:4635): Gtk-CRITICAL **: gtk_widget_set_colormap: assertion `!GTK_WIDGET_REALIZED (widget)' failed Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb7d688c0 (LWP 4635)] ---Type to continue, or q to quit--- 0xb31742c0 in ?? () (gdb) bt #0 0xb31742c0 in ?? () #1 0xb42e6eb4 in ?? () from /usr/lib/libGL.so.1 #2 0x09e1cd60 in ?? () #3 0x0a158c38 in ?? () #4 0x in ?? () -- System Information: Debian Release: 5.0.3 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-686 (SMP w/1 CPU core) Locale: LANG=gl_ES.UTF-8, LC_CTYPE=gl_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages python-vtk depends on: ii libc6 2.7-18GNU C Library: Shared libraries ii libexpat1 2.0.1-4 XML parsing C library - runtime li ii libfreetype6 2.3.7-2+lenny1FreeType 2 font engine, shared lib ii libgcc11:4.3.2-1.1 GCC support library ii libgl1-mesa-glx [libgl 7.0.3-7 A free implementation of the OpenG ii libice62:1.0.4-1 X11 Inter-Client Exchange library ii libjpeg62 6b-14 The Independent JPEG Group's JPEG ii libpng12-0 1.2.27-2+lenny2 PNG library - runtime ii libsm6 2:1.0.3-2 X11 Session Management library ii libstdc++6 4.3.2-1.1 The GNU Standard C++ Library v3 ii libtiff4 3.8.2-11.2Tag Image File Format (TIFF) libra ii libvtk55.0.4-1.1 Visualization Toolkit - A high lev ii libx11-6 2:1.1.5-2 X11 client-side library ii libxext6 2:1.0.4-1 X11 miscellaneous extension librar ii libxt6 1:1.0.5-3 X11 toolkit intrinsics library ii python 2.5.2-3 An interactive high-level object-o ii python-support 0.8.4lenny1 automated rebuilding support for P ii python2.5 2.5.2-15 An interactive high-level object-o ii tcl8.4 8.4.19-2 Tcl (the Tool Command Language) v8 ii tk8.4 8.4.19-2 Tk toolkit for Tcl and X11, v8.4 - ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime python-vtk recommends no packages. Versions of packages python-vtk suggests: pn mayavi (no description available) ii vtk-doc 5.0.4-1.1 VTK class reference documentation ii vtk-examples 5.0.4-1.1 C++, Tcl and Python example progra -- 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#546288: upstream accepted
i filed a bug, http://bugs.freedesktop.org/show_bug.cgi?id=23876 and upstream accepted the patch, so should someone close this bug?, or wait until the new version reaches Debian ? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#546288: xkb-data: spanish keymap: 3 ascii tildes and no dead_tilde: unable to write in portuguese
Package: xkb-data
Version: 1.3-2
Severity: normal
Tags: patch
spanish keymap has at least 3 ascii_tilde and no dead_tilde, so it is
hard to write in portuguese correctly. given that portugal is
geographically next to spain, there is a need to communicate in that
language.
of the 3 ascii tildes in the keyboard, i think the less invasive to
change is the one in the key '¡', also that key is next to the other
dead marks `'"^ ... and is present in desktop and laptop keyboards
it is matter to change in /usr/share/X11/xkb/symbols/es line 20 from
asciitilde to dead_tilde.
-- System Information:
Debian Release: 5.0.3
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.26-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=gl_ES.UTF-8, LC_CTYPE=gl_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
-- no debconf information
--- a/xkb-data/usr/share/X11/xkb/symbols/es 2008-08-14 19:55:54.0
+0200
+++ b/xkb-data/usr/share/X11/xkb/symbols/es 2008-09-21 17:24:53.0
+0200
@@ -17,7 +17,7 @@
key { [ 4, dollar, asciitilde, dollar ] };
key { [ 6, ampersand, notsign, fiveeighths ] };
key { [apostrophe, question,backslash, questiondown ] };
-key { [exclamdown, questiondown, asciitilde, asciitilde ] };
+key { [exclamdown, questiondown, dead_tilde, asciitilde ] };
key { [dead_grave, dead_circumflex, bracketleft, dead_abovering ] };
key { [ plus, asterisk, bracketright, dead_macron ] };
Bug#528392: [Python-apps-team] Bug#528392: wxPython apps using mayavi2 crash when exitting
2009/6/26 Varun Hiremath : > Hi Rodrigo, > > On Tue, 12 May, 2009 at 06:21:48PM +0200, Rodrigo Valiña Gutiérrez wrote: >> Package: mayavi2 >> Version: 3.2.0-1 >> Severity: important >> >> >> 1) wxPython apps using mayavi2 work well, but when I close the window, it >> reports a crash. Below is the output of the first case: >> >> $ python /usr/share/doc/mayavi2/examples/mayavi/wx_embedding.py >> (python:6883): Gtk-CRITICAL **: gtk_widget_set_colormap: assertion >> `!GTK_WIDGET_REALIZ$ >> The program 'python' received an X Window System error. >> This probably reflects a bug in the program. >> The error was 'BadDrawable (invalid Pixmap or Window parameter)'. >> (Details: serial 4055 error_code 9 request_code 136 minor_code 9) >> (Note to programmers: normally, X errors are reported asynchronously; >> that is, you will receive the error a while after causing it. >> To debug your program, run it with the --sync command line >> option to change this behavior. You can then get a meaningful >> backtrace from your debugger if you break on the gdk_x_error() function.) > > I can't reproduce this bug with the latest mayavi2 3.2.0-3 package in > sid. Could you please check if it works for you? Also make sure you > get the latest version of python-vtk 5.2.1-6. > > Thanks, > Varun > hi, Varun now i tried in another computer and the bug is present, the warning is displayed. maybe it is an OpenGL / VTK / WxWidgets bug ? i also observed that python-vtk with wxpython has the same or similar bug: having some vtk scenes in a wx.Notebook, and closing all pages, makes application crash. it does not crash when doing the same in a wx.aui.Notebook. $ python /usr/share/doc/mayavi2/examples/mayavi/wx_embedding.py (python:16598): Gtk-CRITICAL **: gtk_widget_set_colormap: assertion `!GTK_WIDGET_REALIZED (widget)' failed The program 'python' received an X Window System error. This probably reflects a bug in the program. The error was 'BadDrawable (invalid Pixmap or Window parameter)'. (Details: serial 3089 error_code 9 request_code 136 minor_code 9) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#530561: python-vtk: not usable on amd64: ImportError: No module named libvtkCommonPython
Package: python-vtk Version: 5.2.1-5 Severity: important amd64: bug #529961 persists after updating to 5.2.1-5 the only difference is that installing or reconfiguring does not print anything: # dpkg-reconfigure python-vtk # but it still prints error when trying to execute any example: $ /usr/share/vtk/Rendering/Python/rainbow.py Traceback (most recent call last): File "/usr/share/vtk/Rendering/Python/rainbow.py", line 5, in import vtk File "/usr/lib/pymodules/python2.5/vtk/__init__.py", line 41, in from common import * File "/usr/lib/pymodules/python2.5/vtk/common.py", line 7, in from libvtkCommonPython import * ImportError: No module named libvtkCommonPython $ -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.29-2-amd64 (SMP w/2 CPU cores) Locale: LANG=gl_ES.UTF-8, LC_CTYPE=gl_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages python-vtk depends on: ii libc6 2.9-12GNU C Library: Shared libraries ii libexpat1 2.0.1-4 XML parsing C library - runtime li ii libfreetype6 2.3.9-4.1 FreeType 2 font engine, shared lib ii libgcc11:4.4.0-5 GCC support library ii libgl1-mesa-glx [libgl 7.4.1-1 A free implementation of the OpenG ii libice62:1.0.5-1 X11 Inter-Client Exchange library ii libjpeg62 6b-14 The Independent JPEG Group's JPEG ii libpng12-0 1.2.36-1 PNG library - runtime ii libsm6 2:1.1.0-2 X11 Session Management library ii libstdc++6 4.4.0-5 The GNU Standard C++ Library v3 ii libtiff4 3.8.2-11 Tag Image File Format (TIFF) libra ii libvtk5.2 5.2.1-5 Visualization Toolkit - A high lev ii libx11-6 2:1.2.1-1 X11 client-side library ii libxext6 2:1.0.4-1 X11 miscellaneous extension librar ii libxft22.1.13-3 FreeType-based font drawing librar ii libxml22.7.3.dfsg-1 GNOME XML library ii libxt6 1:1.0.5-3 X11 toolkit intrinsics library ii python 2.5.4-2 An interactive high-level object-o ii python-support 1.0.3 automated rebuilding support for P ii python2.5 2.5.4-1 An interactive high-level object-o ii tcl8.4 8.4.19-3 Tcl (the Tool Command Language) v8 ii tk8.4 8.4.19-3 Tk toolkit for Tcl and X11, v8.4 - ii zlib1g 1:1.2.3.3.dfsg-13 compression library - runtime python-vtk recommends no packages. Versions of packages python-vtk suggests: pn mayavi (no description available) ii vtk-doc 5.2.1-5VTK class reference documentation ii vtk-examples 5.2.1-5C++, Tcl and Python example progra -- 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#529961: python-vtk: not usable on amd64: ImportError: No module named libvtkCommonPython
Package: python-vtk Version: 5.2.1-4 Severity: important amd64: executing any python script that uses python-vtk fails: e.g.: [file in package vtk-examples] $ /usr/share/vtk/DataManipulation/Python/CreateStrip.py Traceback (most recent call last): File "/usr/share/vtk/DataManipulation/Python/CreateStrip.py", line 6, in import vtk File "/usr/lib/pymodules/python2.5/vtk/__init__.py", line 41, in from common import * File "/usr/lib/pymodules/python2.5/vtk/common.py", line 7, in from libvtkCommonPython import * ImportError: No module named libvtkCommonPython $ maybe it is a problem with shared libraries, since it seems that on amd64 are installed in diferent locations: /usr/lib/python-support/python-vtk/python2.5/libvtkCommonPython.so python-vtk [amd64] /usr/lib/python-support/python-vtk/python2.5/vtk/libvtkCommonPython.so python-vtk [mips, hppa, m68k, sparc] also, when installed or reconfigured, it says: # dpkg-reconfigure python-vtk Can't list /usr/lib/python2.5/site-packages/vtk Can't list /usr/lib/python2.5/site-packages/vtk # -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.29-2-amd64 (SMP w/2 CPU cores) Locale: LANG=gl_ES.UTF-8, LC_CTYPE=gl_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages python-vtk depends on: ii libc6 2.9-12GNU C Library: Shared libraries ii libexpat1 2.0.1-4 XML parsing C library - runtime li ii libfreetype6 2.3.9-4.1 FreeType 2 font engine, shared lib ii libgcc11:4.4.0-5 GCC support library ii libgl1-mesa-glx [libgl 7.4.1-1 A free implementation of the OpenG ii libice62:1.0.5-1 X11 Inter-Client Exchange library ii libjpeg62 6b-14 The Independent JPEG Group's JPEG ii libpng12-0 1.2.36-1 PNG library - runtime ii libsm6 2:1.1.0-2 X11 Session Management library ii libstdc++6 4.4.0-5 The GNU Standard C++ Library v3 ii libtiff4 3.8.2-11 Tag Image File Format (TIFF) libra ii libvtk5.2 5.2.1-4 Visualization Toolkit - A high lev ii libx11-6 2:1.2.1-1 X11 client-side library ii libxext6 2:1.0.4-1 X11 miscellaneous extension librar ii libxft22.1.13-3 FreeType-based font drawing librar ii libxml22.7.3.dfsg-1 GNOME XML library ii libxt6 1:1.0.5-3 X11 toolkit intrinsics library ii python 2.5.4-2 An interactive high-level object-o ii python-support 1.0.3 automated rebuilding support for P ii python2.5 2.5.4-1 An interactive high-level object-o ii tcl8.4 8.4.19-3 Tcl (the Tool Command Language) v8 ii tk8.4 8.4.19-3 Tk toolkit for Tcl and X11, v8.4 - ii zlib1g 1:1.2.3.3.dfsg-13 compression library - runtime python-vtk recommends no packages. Versions of packages python-vtk suggests: pn mayavi (no description available) pn vtk-doc(no description available) ii vtk-examples 5.2.1-4C++, Tcl and Python example progra -- 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#528392: wxPython apps using mayavi2 crash when exitting
Package: mayavi2 Version: 3.2.0-1 Severity: important 1) wxPython apps using mayavi2 work well, but when I close the window, it reports a crash. Below is the output of the first case: $ python /usr/share/doc/mayavi2/examples/mayavi/wx_embedding.py (python:6883): Gtk-CRITICAL **: gtk_widget_set_colormap: assertion `!GTK_WIDGET_REALIZ$ The program 'python' received an X Window System error. This probably reflects a bug in the program. The error was 'BadDrawable (invalid Pixmap or Window parameter)'. (Details: serial 4055 error_code 9 request_code 136 minor_code 9) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) 2) The second case is a bigger app that has an embedded Mayavi2 visualization similar to the first one in this report. It displays the Gtk-CRITICAL when showing the 3D object, and crashes on exit: (python:5413): Gtk-CRITICAL **: gtk_widget_set_colormap: assertion `!GTK_WIDGET_REALIZED (widget)' failed Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb7e468d0 (LWP 5413)] 0xb7eb8142 in free () from /lib/i686/cmov/libc.so.6 (gdb) bt #0 0xb7eb8142 in free () from /lib/i686/cmov/libc.so.6 #1 0xafa03f1d in _mesa_free () from /usr/lib/dri/r200_dri.so #2 0xaf99cbf9 in __driUtilUpdateDrawableInfo () from /usr/lib/dri/r200_dri.so #3 0xaf9a3af5 in r200GetLock () from /usr/lib/dri/r200_dri.so #4 0xaf9a2110 in r200FlushCmdBuf () from /usr/lib/dri/r200_dri.so #5 0xaf9a21be in r200Flush () from /usr/lib/dri/r200_dri.so #6 0xaf9a221b in r200Finish () from /usr/lib/dri/r200_dri.so #7 0xaf9d0781 in _mesa_Finish () from /usr/lib/dri/r200_dri.so #8 0xb1e57bb1 in vtkXOpenGLRenderWindow::DestroyWindow () from /usr/lib/libvtkRendering.so.5.2 #9 0xb1e52b58 in vtkXOpenGLRenderWindow::Finalize () from /usr/lib/libvtkRendering.so.5.2 #10 0xb1e5768a in vtkXOpenGLRenderWindow::~vtkXOpenGLRenderWindow () from /usr/lib/libvtkRendering.so.5.2 #11 0xb3c6ee63 in vtkObjectBase::UnRegisterInternal () from /usr/lib/libvtkCommon.so.5.2 #12 0xb3c6d714 in vtkObject::UnRegisterInternal () from /usr/lib/libvtkCommon.so.5.2 #13 0xb3c6ed30 in vtkObjectBase::UnRegister () from /usr/lib/libvtkCommon.so.5.2 #14 0xb1dabec4 in vtkRenderWindow::UnRegister () from /usr/lib/libvtkRendering.so.5.2 #15 0xb1db7ac3 in vtkRenderWindowInteractor::SetRenderWindow () ---Type to continue, or q to quit--- from /usr/lib/libvtkRendering.so.5.2 #16 0xb1db7b82 in vtkRenderWindowInteractor::UnRegister () from /usr/lib/libvtkRendering.so.5.2 #17 0xb3ca1a65 in vtkSmartPointerBase::~vtkSmartPointerBase () from /usr/lib/libvtkCommon.so.5.2 #18 0xb3e33620 in std::_Rb_tree, std::_Select1st >, std::less, std::allocator > >::_M_erase () from /usr/lib/libvtkCommonPythonD.so.5.2 #19 0xb3e33612 in std::_Rb_tree, std::_Select1st >, std::less, std::allocator > >::_M_erase () from /usr/lib/libvtkCommonPythonD.so.5.2 #20 0xb3e33612 in std::_Rb_tree, std::_Select1st >, std::less, std::allocator > >::_M_erase () from /usr/lib/libvtkCommonPythonD.so.5.2 #21 0xb3e31a62 in vtkPythonUtil::~vtkPythonUtil () from /usr/lib/libvtkCommonPythonD.so.5.2 #22 0xb3e31ace in vtkPythonHashDelete () from /usr/lib/libvtkCommonPythonD.so.5.2 #23 0x080ecff7 in Py_Finalize () #24 0x08058d3f in Py_Main () ---Type to continue, or q to quit--- #25 0x08058722 in main () (gdb) -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.29-2-686 (SMP w/1 CPU core) Locale: LANG=gl_ES.UTF-8, LC_CTYPE=gl_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages mayavi2 depends on: ii libc62.9-12 GNU C Library: Shared libraries ii libjs-jquery 1.3.2-2 JavaScript library for dynamic web ii libvtk5 5.2.1-3 Visualization Toolkit - A high lev ii python 2.5.4-2 An interactive high-level object-o ii python-apptools 3.2.0-1 ETS Application Tools ii python-central 0.6.11 register and build utility for Pyt ii python-configobj 4.5.2-2 a simple but powerful config file ii python-envisagecore 3.1.0-1 Extensible Application Framework ii python-envisageplugins 3.1.0-1 Plugins for the Envisage framework ii python-numpy 1:1.2.1-1 Numerical Python adds a fast array ii python-pkg-resources 0.6c9-2 Package Discovery and Resource Acc ii python-traits3.1.0-1 Manifest typing and reactive progr ii python-traitsgui 3.0.4-1 Traits-capable windowing framework ii python-vtk
Bug#517121: debian-installer: installs linux-image-2.6-486 instead of linux-image-2.6-686 with a VIA C7-D Processor
Package: debian-installer Severity: normal debian-installer selects and does not allow changing the 486 kernel. This processor supports a 686 kernel, and also the 486 kernel has some drawbacks such as not supporting more than 1GB of RAM. It showld detect the processor and install by default the corresponding kernel. Though it can be changed later with: # aptitude install linux-image-2.6-686 below is the output of cat /proc/cpuinfo with this processor: processor : 0 vendor_id : CentaurHauls cpu family : 6 model : 13 model name : VIA C7-D Processor 1500MHz stepping: 0 cpu MHz : 1499.990 cache size : 128 KB fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge cmov pat clflush acpi mmx fxsr sse sse2 tm nx up pni xtpr rng rng_en ace ace_en ace2 ace2_en phe phe_en pmm pmm_en bogomips: 3002.89 clflush size: 64 power management: -- System Information: Debian Release: 5.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#451828: bakery closes window without asking for save data
Package: libbakery-2.4-dev Version: 2.4.0-2 With debian 4.0r0 etch i386 The problem can be reproduced executing one of the examples that come with bakery, on: /usr/share/doc/libbakery-2.4-dev/examples/WithDocView/ g++ -Wall -c *.cc `pkg-config bakery-2.4 --cflags` g++ -Wall -o main *.o `pkg-config bakery-2.4 --libs` $ ./main Then write some text on the Entry. After that, open a file with some text. Then try to close the first window; it closes without asking for saving the data. On the other hand, if you close it before opening the new document, it warns about unsaved data. The problem is present also in bakery 2.4.2 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#415286: dd: has no option to continue after write errors
Package: coreutils Version: 5.2.1-2 Severity: wishlist dd has an option to continue after read errors, but not to continue after write errors. I am using dd to clean data from a hard disk that has some bad sectors: # dd if=/dev/zero of=/dev/hdb conv=noerror but it stops after first write failure. It would be useful that had an option to continue after write errors, discarding data while it can not be written. -- System Information: Debian Release: 3.1 Architecture: i386 (i586) Kernel: Linux 2.6.8-2-386 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages coreutils depends on: ii libacl1 2.2.23-1 Access control list shared library ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#390752: navigation slowdown connected to terminal Ericsson F251m
Package: kernel-image-2.6.8-2-686 Version: 2.6.8-16 I am using Debian 3.1r0a Sarge and I connect to Internet with a serial modem plugged to the phone line which ends into terminal "Ericsson F251m". When i connect the Linux box to the modem: 1) navigation is much slower than from the Windows box with same hardware and configuration. but downloading with wget or similar ir equally fast. 2) I can not connect to my msn account not with Gaim not with aMSN the avobe problems dissapear if I connect the Linux box to a Windows box with DHCP. so it is strange. maybe a bug in PPP? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#380010: more error messages
here is the output of today dmesg [plugged the usb key] usb 1-1: new full speed USB device using address 2 SCSI subsystem initialized Initializing USB Mass Storage driver... scsi0 : SCSI emulation for USB Mass Storage devices Vendor: Model: Rev: 2.00 Type: Direct-Access ANSI SCSI revision: 02 USB Mass Storage device found at 2 usbcore: registered new driver usb-storage USB Mass Storage support registered. SCSI device sda: 2040319 512-byte hdwr sectors (1045 MB) sda: assuming Write Enabled sda: assuming drive cache: write through /dev/scsi/host0/bus0/target0/lun0: unknown partition table Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0 usb 1-1: USB disconnect, address 2 [plugged the usb key a second time] usb 1-1: new full speed USB device using address 3 scsi1 : SCSI emulation for USB Mass Storage devices Vendor: Model: Rev: 2.00 Type: Direct-Access ANSI SCSI revision: 02 SCSI device sda: 2040319 512-byte hdwr sectors (1045 MB) sda: assuming Write Enabled sda: assuming drive cache: write through [attempted to mount the volume: mount blocks and does not get killed even by kill -9] /dev/scsi/host1/bus0/target0/lun0:SCSI error : <1 0 0 0> return code = 0x7 end_request: I/O error, dev sda, sector 0 Buffer I/O error on device sda, logical block 0 SCSI error : <1 0 0 0> return code = 0x7 end_request: I/O error, dev sda, sector 1 Buffer I/O error on device sda, logical block 1 SCSI error : <1 0 0 0> return code = 0x7 end_request: I/O error, dev sda, sector 2 Buffer I/O error on device sda, logical block 2 SCSI error : <1 0 0 0> return code = 0x7 end_request: I/O error, dev sda, sector 3 Buffer I/O error on device sda, logical block 3 SCSI error : <1 0 0 0> return code = 0x7 end_request: I/O error, dev sda, sector 4 Buffer I/O error on device sda, logical block 4 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#380010: usb mass storage device: can not plug it and mount it a second time
Package: kernel-image-2.6.8-2-686Version: 2.6.8-16when i plug the 1GB usb mass storage device i recently purchased, all seems well: the device is mounted automatically (has a single FAT16 partition that occupyes whole disk), but when i umount it "#umount /dev/sda" then unplug it, and then plug it, it does not mouts automatically, and any attempt to mount or access the device causes the process doing it ( e.g. "dd if=/dev/sda of=contents.raw bs=1k count=1" or "lsusb" or "mount /dev/sda /mnt") to hang and not being killed even by "kill -9 pid".it happens to me on two computers with debian 3.1 sarge. on the same computers, under windows xp, i can plug the device several times, and works well.so i can only plug the usb key one time per boot.below is the (hopefully) relevant output of dmesg: (...)eth0: no IPv6 routers presentusb 1-1: new full speed USB device using address 2usb 1-1: can't set config #1, error -71usb 1-1: new full speed USB device using address 3SCSI subsystem initialized Initializing USB Mass Storage driver...scsi0 : SCSI emulation for USB Mass Storage devices Vendor: Model: Rev: 2.00 Type: Direct-Access ANSI SCSI revision: 02 USB Mass Storage device found at 3usbcore: registered new driver usb-storageUSB Mass Storage support registered.SCSI device sda: 2040319 512-byte hdwr sectors (1045 MB)sda: assuming Write Enabledsda: assuming drive cache: write through /dev/scsi/host0/bus0/target0/lun0: unknown partition tableAttached scsi removable disk sda at scsi0, channel 0, id 0, lun 0usb 1-1: USB disconnect, address 3usb 1-2: new full speed USB device using address 4 scsi1 : SCSI emulation for USB Mass Storage devices Vendor: Model: Rev: 2.00 Type: Direct-Access ANSI SCSI revision: 02SCSI device sda: 2040319 512-byte hdwr sectors (1045 MB) sda: assuming Write Enabledsda: assuming drive cache: write throughthe first time i plug it, all seems ok, but second time it does not automatically mount, and any apttempt to access it blocks the process.
