[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#425267: marked as done (umount timeout too short for some devices)

Your message dated Fri, 12 Mar 2010 18:24:59 -0500
with message-id <9f694b821003121524t26e4e1aeg1c759230b19ca851@mail.gmail.com>
and subject line Re: Bug#425267: About bug # 425267 in Debian BTS
has caused the Debian Bug report #425267,
regarding umount timeout too short for some devices
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
425267: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=425267
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: hal
Version: 0.5.8.1-9
Severity: normal

*** Please type your report below this line ***

I hope this is the correct package for this report, I get the following
behaviour for unmounting the device though media:/ in konqueror, so the
timeout value might come from kde.

some devices(in my case a mobile phone with a hard drive) take very long to
unmount(> 1 minute) if you've copied data to it. I assume that's because the
data is buffered either on the PC or in the phone memory and copied to the
harddisk on unmount.
anyway, konqueror reports a failure after some time has passed even though
the 'umount' process is still running, and thus the device is never
'eject'ed.
either you have to increase the timeout value or, better, wait until the 
umount process is finished.


-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)

Versions of packages hal depends on:
ii  adduser                   3.102          Add and remove users and groups
ii  dbus                      1.0.2-1        simple interprocess messaging 
syst
ii  libc6                     2.3.6.ds1-13   GNU C Library: Shared libraries
ii  libdbus-1-3               1.0.2-1        simple interprocess messaging 
syst
ii  libdbus-glib-1-2          0.71-3         simple interprocess messaging 
syst
ii  libexpat1                 1.95.8-3.4     XML parsing C library - runtime 
li
ii  libglib2.0-0              2.12.4-2       The GLib library of C routines
ii  libhal-storage1           0.5.8.1-9      Hardware Abstraction Layer - 
share
ii  libhal1                   0.5.8.1-9      Hardware Abstraction Layer - 
share
ii  libusb-0.1-4              2:0.1.12-5     userspace USB programming library
ii  libvolume-id0             0.105-4        libvolume_id shared library
ii  lsb-base                  3.1-23.1       Linux Standard Base 3.1 init 
scrip
ii  pciutils                  1:2.2.4~pre4-1 Linux PCI Utilities
ii  udev                      0.105-4        /dev/ and hotplug management 
daemo
ii  usbutils                  0.72-7         USB console utilities

Versions of packages hal recommends:
ii  eject                         2.1.4-3    ejects CDs and operates 
CD-Changer

-- no debconf information

--- End Message ---
--- Begin Message --- 
Submitter won't try to reproduce this.
I'm closing this old bug right now. if someone is able to reproduce it
with a recent version of the package, feel free to reopen.
Olivier

2010/3/12  <strasser@uni-bremen.de>:
> Zitat von Olivier Vitrat <ovit.debian@gmail.com>:
>
>> Hello
>> You've reported the following bug in Debian BTS:
>> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=425267
>>
>> Are you able to reproduce it with a recent version of the package ?
>> If not, can we close this old bug report ?
>
>
> honestly, I don't care and I'm not going to try.
> the debian bug tracking system is totally useless.
>
> every bug I reported took literally years to be picked up on.
> if I try to reproduce it now, it'll probably take another 2 years and it'll
> be outdated again.
>
>
>
>
>

--- End Message ---
Reply to: