Opened 9 years ago

Last modified 9 years ago

#7509 new defect

journal fails to mount specific usb drive

Reported by: dsd Owned by: tomeu
Priority: high Milestone: 9.1.0-cancelled
Component: journal-activity Version:
Keywords: joyride-2131:- blocks-:8.2.0 8.2.0:- Cc: bjordan, jg, gregorio
Blocked By: Blocking:
Deployments affected: Action Needed: diagnose
Verified: no


Joyride 2131: The journal fails to mount Brian's usb drive.

Attachments (2)

org.laptop.JournalActivity-1.log (6.2 KB) - added by dsd 9 years ago.
journal log (347.8 KB) - added by dsd 9 years ago.
tarball of broken directory

Download all attachments as: .zip

Change History (10)

Changed 9 years ago by dsd

journal log

Changed 9 years ago by dsd

tarball of broken directory

comment:1 Changed 9 years ago by dsd

  • Component changed from not assigned to journal-activity
  • Owner set to tomeu

comment:2 Changed 9 years ago by cjb

  • Action Needed changed from never set to diagnose
  • Keywords blocks?:8.2.0 8.2.0:? added
  • Milestone set to 8.2.0 (was Update.2)
  • Priority changed from normal to blocker

Bumping up, at least until diagnosis.

comment:3 Changed 9 years ago by gregorio

  • Cc jg gregorio added

Hi Brian,

Which USB drive is it? Did it work in previous releases?

Do we know if other USB drives work?

Thanks for filing this one. If its only one specific USB drive that is not common and never worked before I would not mark this a blocker, but if it used to work and its common or it affects a whole class of USB stick I would make it a blocker.

I'll leave it ? for now.


Greg S

comment:4 Changed 9 years ago by dsd

It is not the USB stick in question, it is the contents of it. sugar has somehow created a corrupt cache, or something has corrupted sugar's cache, and sugar is not dealing with it. If you extract the tarball I added onto *any* blank USB stick then you will reproduce the problem.

comment:5 Changed 9 years ago by kimquirk

  • Keywords blocks-:8.2.0 added; blocks?:8.2.0 removed

I think there is a workaround in that if you find and remove the problem file on the USB, then you will see the rest of the files. If this is not the case, we will need to re-evaluate. If this is true, it is not a blocker.

Should be in release notes.

comment:6 Changed 9 years ago by marco

Kim is correct.

comment:7 Changed 9 years ago by marco

  • Priority changed from blocker to high

Well, actually you need to remove the index ( But I suppose that's equivalent for the blocker status of this bug.

comment:8 Changed 9 years ago by marco

  • Keywords 8.2.0:- added; 8.2.0:? removed
  • Milestone changed from 8.2.0 (was Update.2) to 9.1.0
Note: See TracTickets for help on using tickets.