[disks-admin] Disk Manager won't run when pen drive is attached

[Wladston Viana]

Whenever I try to open System->administration->disks manager and my pen drive is attached, it stays on the grayed out mode forever.

I've run "sudo gksu disks-admin" on the command line and the shell returns no output also.

When I remove the pendrive, it works normaly.

Steps to reproduce:
1. Connect an USB pen drive at the USB plug
2. Try to launch disks manager
3. The program will stay on the "grayed out" mode untill user closes it

[Lionel Le Folgoc (mrpouit)]

disks-admin belongs to gnome-system-tools package.

[Sebastien Bacher (seb128)]

Thanks for your bug. Could you get a backtrace of the hang?
- sudo gdb disks-admin
(gdb) run
<Ctrl-C> when it starts hanging
(gdb) thread apply all bt

and copy that to a comment

[Wladston Viana (wladston)]

Sebastien,

Here it is :

(gdb) run
Starting program: /usr/bin/disks-admin
(no debugging symbols found)
(no debugging symbols found)
(.... lots more of this)
(no debugging symbols found)
---Type <return> to continue, or q <return> to quit---
(no debugging symbols found)
(.... lots more of this)
(no debugging symbols found)
---Type <return> to continue, or q <return> to quit---
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1223993664 (LWP 5461)]
(no debugging symbols found)
(no debugging symbols found)
(.... lots more of this)
(no debugging symbols found)
---Type <return> to continue, or q <return> to quit---
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)

Program received signal SIGINT, Interrupt.
[Switching to Thread -1223993664 (LWP 5461)]
0xffffe410 in __kernel_vsyscall ()
(gdb) thread apply all bt

Thread 1 (Thread -1223993664 (LWP 5461)):
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb73ed88d in poll () from /lib/tls/i686/cmov/libc.so.6
#2 0x0805bd35 in ?? ()
#3 0xbfa841cc in ?? ()
#4 0x00000001 in ?? ()
#5 0x00000064 in ?? ()
#6 0x2f766564 in ?? ()
#7 0x6c6c756e in ?? ()
#8 0x205d7c20 in ?? ()
#9 0x20726f66 in ?? ()
#10 0x00000012 in ?? ()
#11 0x00000001 in ?? ()
#12 0x080d8028 in ?? ()
#13 0xbfa845e8 in ?? ()
#14 0x0805bd8d in ?? ()
#15 0xbfa841fc in ?? ()
#16 0x000003e8 in ?? ()
#17 0x08363c10 in ?? ()
#18 0x00000018 in ?? ()
#19 0x00000018 in ?? ()
#20 0x00000020 in ?? ()
---Type <return> to continue, or q <return> to quit---
#21 0x0000001f in ?? ()
#22 0x6f666e69 in ?? ()
#23 0x69663a3a in ?? ()
#24 0x725f656c in ?? ()
#25 0x705f6e75 in ?? ()
#26 0x5f657069 in ?? ()
#27 0x63637573 in ?? ()
#28 0x3a737365 in ?? ()
#29 0x7069503a in ?? ()
#30 0x20676e69 in ?? ()
#31 0x6d6d6f63 in ?? ()
#32 0x20646e61 in ?? ()
#33 0x5d73255b in ?? ()
#34 0x726f6620 in ?? ()
#35 0x61657220 in ?? ()
#36 0x676e6964 in ?? ()
#37 0x4c3a3a2e in ?? ()
#38 0x4c415f43 in ?? ()
#39 0x20433d4c in ?? ()
#40 0x48544150 in ?? ()
#41 0x4150243d in ?? ()
#42 0x2f3a4854 in ?? ()
#43 0x6e696273 in ?? ()
---Type <return> to continue, or q <return> to quit---
#44 0x73752f3a in ?? ()
#45 0x62732f72 in ?? ()
#46 0x2f206e69 in ?? ()
#47 0x6e696273 in ?? ()
#48 0x6964662f in ?? ()
#49 0x2d206b73 in ?? ()
#50 0x642f206c in ?? ()
#51 0x732f7665 in ?? ()
#52 0x32206264 in ?? ()
#53 0x642f203e in ?? ()
#54 0x6e2f7665 in ?? ()
#55 0x206c6c75 in ?? ()
#56 0x37000a7c in ?? ()
#57 0x263e3220 in ?? ()
#58 0x0a7c2031 in ?? ()
#59 0x00000000 in ?? ()
(gdb)

[Sebastien Bacher (seb128)]

The backtrace is not really useful. Maybe you could get a debug one (https://wiki.ubuntu.com/DebuggingProgramCrash)?

[Wladston Viana (wladston)]

I'm sorry, but I think I don't have the technical expertise to make this ....

Are there any step-by step instructions ?

I've tried to follow it :

wladston@wlad:~$ sudo apt-get build-dep disks-admin
Reading package lists... Done
Building dependency tree... Done
E: Unable to find a source package for disks-admin

I've already installed the devscripts

[Daniel Holbach (dholbach)]

Try 'gnome-system-tools' instead of 'disks-admin'.

[Wladston Viana (wladston)]

After aplying the changes required, the tool now works correctly, tested with my two pendrives, and it now works with both of them.

Probably someone have already fixed it....

[Daniel Holbach (dholbach)]

Thanks for following up. Closing the bug.