Bug 227752 - my devices are not automounted when external eSata drive was connected when computer starts
Summary: my devices are not automounted when external eSata drive was connected when c...
Status: RESOLVED WORKSFORME
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_deviceautomounter (other bugs)
Version First Reported In: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Torrie Fischer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-20 00:02 UTC by Rafał Malinowski
Modified: 2023-01-08 05:16 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rafał Malinowski 2010-02-20 00:02:34 UTC
Version:            (using Devel)
OS:                Linux
Installed from:    Compiled sources

My laptop has 2 HDD:
1. internal HDD (4 partisions)
2. external eSata HDD

External HDD is configured to be automounted at start and connection (as 2 windows partitions of internal HDD)

There are two scenerios how they can be connected:
A. eSata HDD is not connected when computer starts

1. internal HDD gets /dev/hda
2. all windows partitions are properly automounted
3. then I connect eSata HDD to computer
4. eSata gets /dev/hdb
5. eSata is automounted

B. eSata HDD is connected when computer starts
1. internal HDD gets /dev/hdb
2. external HDD gets /dev/hda
3. devices are not automounted
4. when I try to mount them from Dolphin, I get information, that org.freedesktop.hal.storage permissions are not granted

Both scenerios should result in all partitions mounted.
Comment 1 Torrie Fischer 2010-02-22 15:25:42 UTC
At first glance, this looks like a bug with Hal. It sounds like the device isn't getting tagged as being removable. To check this, search for your device with:

hal-find-by-capability --capability storage

Pick the UDI it gives that looks like your eSATA drive, and look at the value of storage.removable via:

hal-device <udi>

If it is false, have a look at what DeviceKit says too, for the 'detachable' value:

devkit-disks --show-info <device-in-/dev>

If DeviceKit says it is removable, then I guess you'll just have to wait until the DeviceKit solid backend is finished. Hal is being depreciated, so theres not likely going to be a bug fix for hal anytime soon.
Comment 2 Rafał Malinowski 2010-02-22 18:02:25 UTC
When eSata disk is detached:

/org/freedesktop/Hal/devices/storage_model_DVD_RAM_UJ_850S
/org/freedesktop/Hal/devices/storage_serial_ST9160821AS_5MA430B6

When eSata disk is attached:

/org/freedesktop/Hal/devices/storage_serial_WD_My_Book_WD_WCAU41138976
/org/freedesktop/Hal/devices/storage_model_DVD_RAM_UJ_850S
/org/freedesktop/Hal/devices/storage_serial_ST9160821AS_5MA430B6

Both drivers gets the same result for "grep det" for both drivers:

vogel@linux-6ij0:~> devkit-disks --show-info /dev/sda | grep det
  detected at:                 pon, 22 lut 2010, 18:00:36
  has media:                   1 (detected at pon, 22 lut 2010, 18:00:36)
    detects change:            0
    detection by polling:      0
    detection inhibitable:     0
    detection inhibited:       0
    detachable:                0
vogel@linux-6ij0:~> devkit-disks --show-info /dev/sdb | grep det
  detected at:                 pon, 22 lut 2010, 18:00:36
  has media:                   1 (detected at pon, 22 lut 2010, 18:00:36)
    detects change:            0
    detection by polling:      0
    detection inhibitable:     0
    detection inhibited:       0
    detachable:                0


But first disks is not detachable and my windows partitions are not mounted at start too. Error is the same.
Comment 3 Andrew Crouthamel 2018-11-02 22:57:38 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Andrew Crouthamel 2018-11-16 05:27:26 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version?

Thank you for helping us make KDE software even better for everyone!
Comment 5 Justin Zobel 2022-12-09 22:13:01 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 6 Bug Janitor Service 2022-12-24 05:23:21 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Bug Janitor Service 2023-01-08 05:16:36 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!