USB UX problems: a welter of 'an operation is already pending' and similar messages

Open
#3,463 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
c
Domain
desktop

Research direction

No source file or test is named. First reproduce the USB eject, physical removal, and reinsertion sequence on Mint 22 with Nemo 6.2.8, then trace where the repeated “An operation is already pending” message is produced. Done means the same sequence gives an informative, actionable result instead of the repeated message.

Written by the indexing model from the issue text.

Description

Distribution

Mint 22

Package version

6.2.8

Frequency

Quite often

Bug description

Nemo (or perhaps some other part of Mint) can generate a warning message when one tells it to 'eject' (or . . 'safely remove') a USB drtive. If one (physically) removes the drive anyway - because some operation with the drive seems to have hung or somehow disappeared - and if one then plugs the USB into another Mint computer, then, on the new computer, one sees - again and again, if one persists in trying to access the drive - a message that, 'An operation is already pending'. This is dire UX.

Steps to reproduce
  1. Tell a Mint PC to 'eject' (or 'safely remove'?) a drive it deems busy.
  2. Physically remove the drive nonetheless (and one can have reason so to do; see my 'Bug Description').
  3. Plug the drive into another computer.
  4. See, repeatedly, the confusing and uninformative message, 'An operation is already pending'.
Expected behavior

Things have gone wrong already if one cannot see how a drive is busy and (yet) Mint is telling one that the drive is busy nonetheless. However: even if the drive is, and clearly is, busy, then removing it and inserting it - the drive - into another PC should not cause what it does. One should get an informative error message - if any error message is necessary - and one should, perhaps after running a repair utility, be able to use the drive.

Additional information

No response

Dominant language
C
Stars
1.6k
Forks
368
Avg merge
4d 4h
Merged PRs (30d)
2

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from linuxmint/nemo

All issues in linuxmint/nemo

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.