Your message dated Tue, 12 May 2009 23:11:59 +0200
with message-id <[email protected]>
and subject line Re: Bug#528305: pmount: /etc/fstab entry breaks the automatic 
mount execution
has caused the Debian Bug report #528305,
regarding pmount: /etc/fstab entry breaks the automatic mount execution
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 [email protected]
immediately.)


-- 
528305: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=528305
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: pmount
Version: 0.9.19-1
Severity: important

Some time ago, the automatic mount of inserted USB device stopped working.

I use /etc/fstab entries for SD, USB stick and CDROM. Everything should be set 
up
correctly, since it worked before and works manually now.

When /etc/fstab includes an entry about a device inserted, "mount" is being
invoked instead of "pmount" (as written in "man pmount"). But this is not so
now. Neither mount nor pmount is being invoked. The whole procedure ends up by
creating the device node e.g. /dev/sdd1.

After this, if I invoke (as a normal user) "pmount /dev/sdd1" manually, the 
device
is properly mounted. If I invoke "mount /de/sdd1" manually, the device is also
properly mounted.

If I remove the appropriate entry from /etc/fstab, all works as expected.

For CDROM, it works ok even when there is similar entry in the /etc/fstab as for
the USB devices.

Thanks.

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.29-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages pmount depends on:
ii  libblkid1    1.41.5-1                    block device id library
ii  libc6        2.9-12                      GNU C Library: Shared libraries
ii  libdbus-1-3  1.2.14-2                    simple interprocess messaging syst
ii  libhal-stora 0.5.12~git20090406.46dc48-2 Hardware Abstraction Layer - share
ii  libhal1      0.5.12~git20090406.46dc48-2 Hardware Abstraction Layer - share

pmount recommends no packages.

Versions of packages pmount suggests:
pn  cryptsetup   <none>                      (no description available)
ii  hal          0.5.12~git20090406.46dc48-2 Hardware Abstraction Layer

-- no debconf information



--- End Message ---
--- Begin Message ---
  Hello,

SkyRaT wrote:
>>   What shall we do ? Do you want to file a fresh bug to gnome-mount (I
>> would prefer that) or would you rather reassign this bug to gnome-mount
>> ? The problem of the second option is that it is much less visible for
>> the gnome-mount maintainers, that's why I prefer the first one.
> 
> If there is not already a related bug report in gnome-mount, I will create 
> one.
> Anyway, it would be good to strip down this conversation a bit and place it
> there as well.
> Is there a better way??? e.g. bind the reports with a cross-reference link, 
> ...

  I think the best is to simply open a new bug report with relevant
information from this thread. It would be good to give them the bug
number of this bug so they can read the full exchange if need arises.

  Meanwhile, I'm closing this bug, since you want to open a new one, and
since it is now clear that it is not a pmount bug.

  Thanks,

        Vincent

-- 
Vincent Fourmond, Debian Developer
http://vince-debian.blogspot.com/

Donkey: No one told me I had the right to remain silent !
Shrek: You *have* the right to remain silent. What you lack is the capacity.
 -- Shrek 2

Vincent, listening to The Beds Too Big Without You (The Police)


--- End Message ---

Reply via email to