Gnomad2 segfaults when scanning media from Creative Vision W.
Output from console.
$ gnomad2
Xlib: extension "RANDR" missing on display ":0.0".
PDE device NULL.
Detected connected device VID=0x041e/PID=0x4153, protocol: mtp
UDI: /org/freedesktop/Hal/devices/usb_device_41e_4153_35510FD7EC0CDE1F_if0
PDE device NULL.
PDE device NULL.
Queried Creative ZEN Vision W
Segmentation fault
$ dmesg [....]
[690871.628281] usb 1-8: new high speed USB device using ehci_hcd and address 13
[690871.743628] usb 1-8: configuration #1 chosen from 1 choice
[690880.952079] gnomad2[12803]: segfault at 52 ip 08059c0b sp b3ee6290 error 4 in gnomad2[8048000+2a000]
$ sudo gdb /usr/bin/gnomad2
warning: Can not parse XML syscalls information; XML support was disabled at compile time.
GNU gdb (Gentoo 7.0 p1) 7.0
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu".
For bug reporting instructions, please see:
http://bugs.gentoo.org/...
Reading symbols from /usr/bin/gnomad2...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/gnomad2
[Thread debugging using libthread_db enabled]
Xlib: extension "RANDR" missing on display ":0.0".
[New Thread 0xb4adfb70 (LWP 12863)]
[Thread 0xb4adfb70 (LWP 12863) exited]
[New Thread 0xb4adfb70 (LWP 12864)]
[Thread 0xb4adfb70 (LWP 12864) exited]
Queried Creative ZEN Vision W
[New Thread 0xb4adfb70 (LWP 12866)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb4adfb70 (LWP 12866)]
0x08059c0b in ?? ()
(gdb) backtrace
(gdb) finish
Run till exit from #0 0x08059c0b in ?? ()
[Thread 0xb4adfb70 (LWP 12875) exited]
Program terminated with signal SIGSEGV, Segmentation fault.
The program no longer exists.
(gdb)
I recently made a thorough overhaul of Gnomad2, removing many bugs, as a result I think it has been re-adopted to Debian (it was staged for removal). Can you please try the 2.9.6 version and see if the problem persists?