cloudbearings / jusbpmp

Automatically exported from code.google.com/p/jusbpmp
0 stars 0 forks source link

Device Report #1

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago

The following code:
        DeviceManager m = DeviceManager.getInstance();
        m.createInstance();
        m.scanDevices();
        System.out.println(m.getDeviceList());

Results in:

Device 1 (VID=041e and PID=4162) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
PTP: Opening session
#
# An unexpected error has been detected by Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x904d99f4, pid=28224, tid=308439336

#
# Java VM: Java HotSpot(TM) Server VM (11.0-b15 mixed mode linux-x86)
# Problematic frame:
# C  [libmtp.so.7+0x199f4]  ptp_mtp_getobjectproplist+0x124
#
# An error report file with more information is saved as:
# /home/siyb/NetBeansProjects/JZen/hs_err_pid28224.log
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
Java Result: 134

I hereby report the Zen X-Fi as an Device (data above) and I really hope
that this isn't yet another dead mtp implementation for java.

Regards siyb

Original issue reported on code.google.com by siyb.the...@gmail.com on 26 Dec 2008 at 9:09

GoogleCodeExporter commented 8 years ago
aix, just saw "report to libmtp development team", well still the mtp device is
accessible via the native library without causing program failure, tried 
transferring
data using amarok (works) and mounting the device using mtpfs (works too)

Original comment by siyb.the...@gmail.com on 26 Dec 2008 at 9:23

GoogleCodeExporter commented 8 years ago
Forgot to add the error report file, will try to recreate the error asap. Where 
can I
obtain the sources for the libraries? 

Original comment by siyb.the...@gmail.com on 28 Dec 2008 at 2:12

GoogleCodeExporter commented 8 years ago

Have you tried in verbose mode? (DeviceManager.setVerbose(1))

Do you have the same issue on Windows?

Original comment by netcm...@gmail.com on 23 Jan 2009 at 7:41