DebuggingRemovableDevices

Differences between revisions 23 and 24
⇤ ← Revision 23 as of 2007-08-31 18:00:54 →
Size: 2862
Editor: dhcp46-106
Comment: making terminal commands slightly clearer with indents
← Revision 24 as of 2007-09-17 23:16:08 → ⇥
Size: 2862
Editor: 67
Comment: Changed capitalization of first words for consistency
Deletions are marked like this. Additions are marked like this.
Line 20: Line 20:
 0. Press Control-C to stop the foreground gnome-volume-manager  0. press Control-C to stop the foreground gnome-volume-manager
Line 27: Line 27:
 0. Press Alt-F2 and type `gnome-volume-manager` to get your background g-v-m back (or just log out and back in again)  0. press Alt-F2 and type `gnome-volume-manager` to get your background g-v-m back (or just log out and back in again)
Line 44: Line 44:
 0. Restore the background hal: [[BR]]  0. restore the background hal: [[BR]]
Line 48: Line 48:
 0. Restart your desktop session  0. restart your desktop session

Introduction

Help on debugging removable device issues.

How to report

When reporting a problem with removable devices, such as USB storage devices ("keys", hard drives, card readers, music players, digital cameras, etc.), please do the following steps:

  1. disconnect the device

  2. stop gvm BR

    • killall gnome-volume-manager

  3. start gvm and capture output BR

    • gnome-volume-manager -n 2>&1 | tee gvm.log

  4. and in another terminal, start udevmonitor and capture output BR

    • sudo udevmonitor -e | tee udev.log

  5. connect the device
  6. wait a few seconds
  7. press Control-C to stop the foreground gnome-volume-manager
  8. press Control-C to stop the udevmonitor

  9. capture lshal, dmesg and ls the attached volumes BR

    • lshal > lshal.txt BR dmesg > dmesg.txt BR ls -l /dev/sd* > devices.txt

  10. attach gvm.log, lshal.txt, devices.txt, dmesg.txt and udev.log (dapper only) to the bug report

  11. press Alt-F2 and type gnome-volume-manager to get your background g-v-m back (or just log out and back in again)

  12. paste the output of id into the bug report

  13. paste the output of id hal into the bug report

  14. paste the output of id haldaemon into the bug report

  15. paste the output of uname -a into the bug report

In easy cases this is everything that is needed. However, you might be asked for a "hal debug output"; please do the following steps to get it:

  1. disconnect the device

  2. stop hald BR

    • sudo killall hald

  3. start hald while capturing its output BR

    • sudo hald --daemon=no --verbose=yes 2>&1 | tee hal.log

  4. wait until the flood of messages settled
  5. connect the device
  6. wait again until no more messages appear
  7. press Control-C to stop the foreground hal

  8. restore the background hal: BR

    • sudo /etc/init.d/dbus-1 restart (in Warty and Hoary)BR OR BR sudo /etc/dbus-1/event.d/20hal start (in Breezy, Dapper, Edgy and Feisty)

  9. attach hal.log to the bug report
  10. restart your desktop session

Debugging procedure

TBD.

Known bugs

Description of known issues, how to recognise them and stock responses/actions.

Open

Bug#

Description

Action

TBD.

TBD.

TBD.

Closed

Bug#

Description

Action

TBD.

TBD.

TBD.

Non-bugs

TBD.

Also see:

CategoryBugSquad

DebuggingRemovableDevices (last edited 2011-01-07 14:06:15 by 67-42-160-182)