I can't get qcma to build using the AUR package https://aur.archlinux.org/packages/qcma-git/

Here is a paste bin of what outputs when I try to compile this

http://pastebin.com/YZUJ1Zvu

Hi. Is it possible to send files into psv via some command?

My use case would be to setup cronjob to download my subscriptions from youtube using https://rg3.github.io/youtube-dl/, then convert the videos using https://www.ffmpeg.org/ and then automatically copy all videos when I connect psv to the pc https://unix.stackexchange.com/questions/28548/how-to-run-custom-scripts-upon-usb-device-plug-in

openfolder cant click
it works on 3.12 but not on 3.13

I have all packages/dependencies installed to run qmca. I run qmca in the terminal, and i get this output:
"qcma: error while loading shared libraries: libavformat.so.56: cannot open shared object file: No such file or directory"
I found out that liabavformat is provided by ffmpeg, but i have double checked that that is installed.
I am running fedora 24.
Thanks.

Feature Request.
Will it be possible to install vpks using qcma? We already have vpk install over ftp using vitaorganizer but it is very slow.

Hi,
I tried to build QCMA 0.3.12 on Gentoo with Qt 4.8.6 and got an error.

x86_64-pc-linux-gnu-g++ -Wl,-O1 -Wl,--as-needed -o qcma_cli main_cli.o singlecoreapplication.o headlessmanager.o moc_singlecoreapplication.o moc_headlessmanager.o    -L/usr/lib64/qt4 -L../common -lqcma_common -lvitamtp -lavformat -lavcodec -lavutil -lswscale -lQtSql -L/usr/lib64/mysql -L/usr/lib64/qt4 -lQtNetwork -lQtCore -lpthread 
../common/libqcma_common.a(sqlitedb.o): In function `SQLiteDB::SQLiteDB(QObject*)':
/var/tmp/portage/games-util/qcma-0.3.12/work/qcma-0.3.12/common/sqlitedb.cpp:160: undefined reference to `QDesktopServices::storageLocation(QDesktopServices::StandardLocation)'
../common/libqcma_common.a(sqlitedb.o): In function `SQLiteDB::clear()':
/var/tmp/portage/games-util/qcma-0.3.12/work/qcma-0.3.12/common/sqlitedb.cpp:226: undefined reference to `(QDesktopServices::StandardLocation)'
collect2: error: ld returned 1 exit status
Makefile:114: recipe for target 'qcma_cli' failed
make[1]: *** [qcma_cli] Error 1
make[1]: Leaving directory '/var/tmp/portage/games-util/qcma-0.3.12/work/qcma-0.3.12/cli'
Makefile:77: recipe for target 'sub-cli-make_default-ordered' failed
make: *** [sub-cli-make_default-ordered] Error 2

The function QDesktopServices::storageLocation is in QtGui module. Why don't you remove the following line in qcma/cli/cli.pro to make QtGui be linked?

QT -= gui

My Vita is connected to my PC (Win8.1 Pro) via WiFi
Everything works - Until my Vita enters Standby...

• After recovering from Standby, the Vita cannot connect to QCMA
• The error on the Vita says "Could not connect to network"

In order to fix this, I need to completely shutdown QCMA and restart it before my Vita can connect

• is this how it is supposed to work?

I'm using QCMA on Win 8.1 Pro with my Vita running on the latest official firmware
Vita is connecting to PC via WiFi
I'm getting disconnections in the following situation

• Under Content Manager, I open Photos or Videos
• Under Content Manager, I leave the Vita and QCMA to run overnight to back up all my apps (not a full backup, just the Vita games)

any idea what's wrong?
I can also provide a log - just need to know where to get that

Hello,

thank's a lot for this wonderfull piece of software !

i build the debian packages of vitaMTP and qcma (with git clone ... and debuild...). The build was OK
but when i launch qcma, the GUI is displayed half a second and then it crashes giving a segmentation fault:

traces are hereafter :

root@grandhuit:/home/grandhuit/SW/psvita# qcma

(process:9451): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(process:9451): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(process:9451): Gtk-CRITICAL **: IA__gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed

(process:9451): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(process:9451): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(process:9451): GLib-GObject-WARNING **: /build/glib2.0-dt6trg/glib2.0-2.42.0/./gobject/gsignal.c:2461: signal 'child-added' is invalid for instance '0x2436140' of type 'GtkMenu'

(process:9451): Gtk-CRITICAL **: IA__gtk_settings_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed

(process:9451): GLib-GObject-CRITICAL **: g_object_ref: assertion 'G_IS_OBJECT (object)' failed

(process:9451): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(process:9451): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(process:9451): Gtk-CRITICAL **: IA__gtk_settings_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed

(process:9451): Gtk-CRITICAL **: IA__gtk_settings_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed

(process:9451): GLib-GObject-CRITICAL **: g_object_ref: assertion 'G_IS_OBJECT (object)' failed

(process:9451): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(process:9451): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(process:9451): Gtk-CRITICAL **: IA__gtk_settings_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed

(process:9451): Gtk-CRITICAL **: IA__gtk_settings_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed

(process:9451): GLib-GObject-CRITICAL **: g_object_ref: assertion 'G_IS_OBJECT (object)' failed

(process:9451): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(process:9451): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(process:9451): Gtk-CRITICAL **: IA__gtk_settings_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed

(process:9451): Gtk-CRITICAL **: IA__gtk_settings_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed

(process:9451): GLib-GObject-CRITICAL **: g_object_ref: assertion 'G_IS_OBJECT (object)' failed

(process:9451): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(process:9451): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(process:9451): Gtk-CRITICAL **: IA__gtk_settings_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed

(process:9451): Gtk-CRITICAL **: IA__gtk_settings_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed

(process:9451): GLib-GObject-CRITICAL **: g_object_ref: assertion 'G_IS_OBJECT (object)' failed

(process:9451): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(process:9451): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(process:9451): Gtk-CRITICAL **: IA__gtk_settings_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed

(process:9451): Gtk-CRITICAL **: IA__gtk_settings_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed

(process:9451): GLib-GObject-CRITICAL **: g_object_ref: assertion 'G_IS_OBJECT (object)' failed

(process:9451): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(process:9451): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(process:9451): Gtk-CRITICAL **: IA__gtk_settings_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed

(process:9451): Gtk-CRITICAL **: IA__gtk_settings_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed

(process:9451): GLib-GObject-CRITICAL **: g_object_ref: assertion 'G_IS_OBJECT (object)' failed

(process:9451): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(process:9451): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(process:9451): Gtk-CRITICAL **: IA__gtk_settings_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed

(process:9451): Gtk-CRITICAL **: IA__gtk_settings_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed

(process:9451): GLib-GObject-CRITICAL **: g_object_ref: assertion 'G_IS_OBJECT (object)' failed

(process:9451): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(process:9451): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(process:9451): Gtk-CRITICAL **: IA__gtk_settings_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed

(process:9451): Gtk-WARNING **: Screen for GtkWindow not set; you must always set
a screen for a GtkWindow before using the window

(process:9451): Gdk-CRITICAL **: IA__gdk_screen_get_display: assertion 'GDK_IS_SCREEN (screen)' failed

(process:9451): Gdk-CRITICAL **: IA__gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed

(process:9451): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(process:9451): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(process:9451): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(process:9451): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(process:9451): Gdk-CRITICAL **: IA__gdk_screen_get_root_window: assertion 'GDK_IS_SCREEN (screen)' failed

(process:9451): Gdk-CRITICAL **: IA__gdk_screen_get_display: assertion 'GDK_IS_SCREEN (screen)' failed

(process:9451): Gdk-CRITICAL **: IA__gdk_x11_display_get_xdisplay: assertion 'GDK_IS_DISPLAY (display)' failed

(process:9451): Gdk-CRITICAL **: IA__gdk_screen_get_number: assertion 'GDK_IS_SCREEN (screen)' failed
Erreur de segmentation
root@grandhuit:/home/grandhuit/SW/psvita#

Ubuntu 13.10 32bit
Gnome Shell 3.8.4

Notification does not display correctly in Gnome 3. It does work fine in Unity.
Here's a screenshot of what it looks like now:
http://wololo.net/talk/viewtopic.php?f=64&t=34677&start=390#p336195

And what all other programs notifications look like:
http://wololo.net/talk/viewtopic.php?f=64&t=34677&start=400#p341587

Please reply in /Talk as I'll probably forget about checking this lol
Thanks again codestation :)

Hallo，
I find three language translations at resources like Spanish，French and Japanese
https://github.com/codestation/qcma/tree/master/common/resources/translations

If I Update a Chinese translation,Can you add it at QCMA 3.14？

Backup Manager "Online ID/Username" only shows the last connected PS vita account.
I have 2 vitas with 2 different accounts (different regions too). I can only see the account of the last vita I transfered data from/to.

There are lots of restrictions on what code can run inside a signal handler so i went with the dbus route at the time i implemented the feature. I have better knowledge on unix signals so the implementation of HUP+TERM to handle reload and stop can be done.

The downside is that event notifiers are lost so the user wont know when the database indexing is finished. To solve this a new command-line switch will be added and others will change meaning.

--quiet: no output whatsoever.
--verbose: full output including event calls.

If no flag is passed then the daemon will output standard stuff (version, locale) and event results (index status and received pin) so the user can view it via journalctl.

I cant use the album list or anything other than all songs even though id3 tags are verry orderly

This is the crash error that sticks out to me. I am guessing it's the OS trying to stop a possible malicious attempt.

Application Specific Information:
detected buffer overflow

I am guess that it is detecting the Henkaku exploit which I am guessing uses a buffer overflow to get triggered.

Hi there, i'm trying to get purchased content onto my Vita using QCMA. I'm running 3.60 FW but do not see it as selectable in CMA manual protocol field. Do I have an incorrect version?

Upon trying to install, OSX gives general cannot instal error message. What could the issue be?

It keeps saying "cannot open USB connection". I've tried uninstalling and reinstalling and noting. Where is the config files for this thign stored at? I am on 3.51 and used the latest version for wheezy as I don't yet want to upgrade/was feeling lazy.

Starting QCMA 0.3.9
Current locale: "en_US"
Cannot load translation for locale: "en_US"
Starting main thread: 0x00007fa943f3d800
Current desktop: ""
Cannot load libqcma_appindicator plugin
Starting cma threads
Starting usb_thread: 0x00007fa92a91a700
Using protocol mode: "automatic"
Starting wireless_thread: 0x00007fa92a119700
Waiting for wireless connection
VitaMTP: waiting for connection
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
QXcbWindow: Unhandled client message: "_GTK_LOAD_ICONTHEMES"
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
QXcbWindow: Unhandled client message: "_GTK_LOAD_ICONTHEMES"
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
QXcbWindow: Unhandled client message: "_GTK_LOAD_ICONTHEMES"
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
QXcbWindow: Unhandled client message: "_GTK_LOAD_ICONTHEMES"
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
VitaMTP: cannot open usb
Killed

This is the error message that I receive

Makefile:777: recipe for target 'opencma-opencma.o' failed

This error will be thrown after psp2-updatelist.xml request by the Vita if psp2-updatelist.xml returned to the Vita wouldn't contain FW info for the request region.
Current integrated in QCMA psp2-updatelist.xml contains next regions: au, eu, jp, kr, mx, ru, tw, uk, us.
In my case console was requesting FW update info for the "sa" region which is missing from the current integrated psp2-updatelist.xml.

Unsure what the issue is here. The "Backup Manager" dialog can't seem to connect to the console properly, throwing a "mtpr3InvalidUserName" error.

Pic: http://i.imgur.com/fd30sXi.png

thanks for this app! I really like the GUI!
I can't figure what Skip Photo, Video, Music Scanning does in the whole scheme of things.
hope you can shed some light

Hey, like the project, looking forward to making use of it. I was wondering though, would it be possible to create a headless version of it, to use on servers that don't run a gui? I currently run a windows vm on my linux server just so I an run Sony's CMA, and it would be awesome if I wouldn't have to do that anymore.

Hi, I've been looking for the XML code though it doesn't seem to be here any more?

when install the .desktop into 'foo/share/applications/qcma' instead of 'foo/share/applications' like other applications

When I try to run the 0.3.12-2 version I get a crash with the following error:

`Dyld Error Message:
Symbol not found: _kCVImageBufferColorPrimaries_ITU_R_2020

Referenced from: /Applications/Qcma.app/Contents/MacOS/../Frameworks/libavcodec.57.dylib (which was built for Mac OS X 10.11)

Expected in: /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo
in /Applications/Qcma.app/Contents/MacOS/../Frameworks/libavcodec.57.dylib`

Is it because I am running Mac OS X 10.10.5?

Version 0.3.12 ran fine on Mac OS X 10.10.5 as long as I wasn't in Henkaku mode.

my psn nickname pops up on my pc but my vita returns error c0-112644-4 everytime

Been running a PS TV on Firmware 3.50 and trying to get QCMA to detect it. The PC (Windows 8.1 64 bit) and the PS TV are on the same network and I've tried adding a proxy to the PS TV's connection, which didn't do anything.

When I run qcma with a vita slim 3.15, I just keep getting a popup that says that the device has been disconnected. My other 3.01 vita slim works fine.

This is the output:

Starting QCMA v0.3.6-2-ga4662a1
Current locale: "en_US"
Cannot load translation for locale: "en_US"
Starting main thread: 0x00007f5c760cf780
Current desktop:  ""
Cannot load libqcma_appindicator plugin
No systemtrayicon available
Starting cma threads
Starting usb_thread: 0x00007f5c5ebd8700
Starting wireless_thread: 0x00007f5c5e3d7700
Waiting for wireless connection
VitaMTP: waiting for connection
PTP: Opening session
VitaMTP: Cannot read device name, tying to continue
Starting new USB connection
Vita connected: id 44712542209730C61
Cannot retreve device information.
Error while exchanging info with the vita
Releasing device...
Icon changed - disconnected
PTP: Opening session
VitaMTP: Cannot read device name, tying to continue
... (loops)

As titled. Rather than necro bumping another thread I choose to open this new one. I'm running Windows 10 x64 and PSTV (FW 3.57) just can't find qcma. I checked Windows firewall and qcma is not blocked by it.

PSTV is connected to LAN by Ethernet, and PSTV can go online like PSN or web browser.

I was wondering if you plan on making packages for F24, as packages were updated for the latest Ubuntu.

Is this in the works? Or are you waiting for the next version? If that is the case is there an ETA for the 0.3.13(?)?

Hi,

Congrats on QCMA, it works really well and it's really handy!

On Mint 17 / Ubuntu 14.10, with Cinnamon 2.2, using vitamtp 2.4.0-1 and qcma compiled from git master today (11/04/14), I can't close the systray/applet menu.

After qcma is launched, everything works as normal. I right-click on the applet and see the menu (Settings , Refresh database etc...). Menu items work fine.

But whether I click somewhere else or whether I click on a menu item, the menu doesn't close.

Trying to do a backup using a .psvimg file triggers a segmentation fault randomly during the transfer.

Steps to recreate the bug:
1/ Create a HUGE .psvimg file on the pc (mine was around 33Gb)
2/ Backup using this file

bug observed on : qcma 0.3.9 (debian jessie and windows version) or qcma_cli 0.3.9 debian jessie + vita2a(fat) on FW 3.51

Also using --verbose on debian jessie results in an immediate segmentation fault at startup.

Here is the log I obtain when using qcma_console --verbose under windows 8.0 (I've cut the boring parts):
http://pastebin.com/0FKdzFhW

ps : I initialy started this ticked because I downloaded the wrong package (wheezy for my debian jessie). So yeah, I'm recycling it

Though renaming the files in translations works, installation from AUR will fail.

==> Starting build()...
lrelease error: Cannot open ../qcma/resources/translations/*.ts: No such file or directory
==> ERROR: A failure occurred in build().

Hi,

You have taken so many efforts to build a nice .deb ; why not ask to add your package to the Debian archive ?

You may think of the ITP (Intent To Package) process as a bit circimonvoluted; I can do most steps for you if you like, and upload to mentors.debian.org where a Debian Developper will review it once again and push it in the archive.

`Starting Qcma 0.3.12
Current locale: "en_IN"
Cannot load translation for locale: "en_IN"
Starting main thread: 0x00007fd8d8ee1900
Current desktop: "Unity"
Cannot load libqcma_appindicator plugin from "/usr/lib/qcma"
Starting cma threads
Starting usb_thread: 0x00007fd8c671e700
Using protocol mode: "manual"
PTP: Opening session
Starting wireless_thread: 0x00007fd8af7fe700
Waiting for wireless connection
VitaMTP: waiting for connection
VitaMTP: Detected device name: PlayStation(R)Vita
Starting new USB connection
Vita connected, id: 03274174220264801
Using protocol mode: "manual"
Sending Qcma protocol version: 1000010
Identifying as "EmptyBox"
Starting event loop
Starting event_thread: 0x00007fd8aedeb700
Icon changed - connected
Sending new event
Event received in void CmaEvent::vitaEventSendHttpObjectFromURL(vita_event_t_, int), code: 0xc10b, id: 2
Reading from local file
Sending 582 bytes of data for HTTP request http://feu01.psp2.update.playstation.net/update/psp2/list/eu/psp2-updatelist.xml
Ended event, code: 0xc10b, id: 2
Sending new event
Event received in void CmaEvent::vitaEventSendHttpObjectFromURL(vita_event_t_, int), code: 0xc10b, id: 3
Reading from local file
Sending 752 bytes of data for HTTP request http://feu01.psp2.update.playstation.net/update/psp2/list/eu/psp2-updatelist.xml
Ended event, code: 0xc10b, id: 3

`
I am trying to connect , but I am always getting "Connect through a usb cable issue"
I have seen other user on firmware having this issue.

I checked for this information on the Wiki but it's empty (Do you need help with that? If so I will contact you if you would like help filling it out, I've done Wiki work before for open source software), but I was wondering if the data created by QCMA is compatible with Sony's official Windows CMA?

Would I be able to restore a Vita/PS TV with data created by QCMA using Sony's CMA under Windows?

I have no issues with QCMA and do not plan on using Sony's CMA but this is just information that I was curious about.

Thanks.

Hi guys,

I would like to thank you for the hard work done on qcma.

I want to inform you that the new vita dumps savedata is deleted after saving the game on pc and restore it by qcma.

Can you please correct this bug.

Best regards

klinux

Hello! First and foremost, thanks for your work - I'm finally able to use my Vita in sync with my computer.

I set up QCMA's directory according to my local media folders, and keep quite a large number of music files in here. I made it so QCMA starts automatically with my user session; each time the application starts up, it takes a quite fair large time to re-index its database, displaying a progress bar.

I'm not aware of any option allowing QCMA to start silently and not display the "Refreshing database" dialog. I'd love it to be able to start silently in the background, perhaps displaying a "Ready" notification bubble when all initializing routines are completed.

Thanks!

Hi, I recently Updated from 3.52 to the last firmware (3.61). But when I try to send music from the PC to PSVita, the music app of the psvita says me is a damaged file. I tried with converting the music (mp3 to mp3) with ffmpeg, vlc but nothing.
I use the qcma client of Linux installed from aur.
With the official cma I can send the music without any problem.

Qcma startup 1 time, i got through the first start configuration and the it would not start any more, i have tried deleting al the preferences and application support files and downloading a new version but to no avail.

crash report gives main reason as:

Dyld Error Message:
Symbol not found: _OSAtomicIncrement32Barrier
Referenced from: /Users/USER/Desktop/Qcma.app/Contents/MacOS/../Frameworks/libusb-1.0.0.dylib
Expected in: /usr/lib/libSystem.B.dylib

i am on osx 10.8.5.

It seems that something changed on the last FW versions so this disconnection only happens on qcma (works fine on official CMA).

I have checked wireshark logs and tried to make byte-per-byte equal connection as the official one but it still disconnects after the PTP_EC_VITA_RequestGetSettingInfo event finishes.

Looks like a timing issue to me but cannot find the root cause yet. This bug blocks the 0.3.10 release and the possible official debian package.

I'm trying to update qcma in Archlinux using the aur/qcma-git package and I get this on the build stage:

==> Compilando e instalando el paquete
==> Creando el paquete: qcma-git 20140503-1 (mar jul 15 10:47:20 CEST 2014)
==> Resolviendo dependencias...
==> Verificando conflictos...
==> Recibiendo fuentes...
-> Clonando qcma repositorio git...
Cloning into bare repository '/tmp/yaourt-tmp-javi/aur-qcma-git/qcma'...
remote: Reusing existing pack: 1392, done.
remote: Counting objects: 3, done.
remote: Compressing objects: 100% (3/3), done.
remote: Total 1395 (delta 0), reused 1 (delta 0)
Receiving objects: 100% (1395/1395), 506.13 KiB | 115.00 KiB/s, done.
Resolving deltas: 100% (943/943), done.
Checking connectivity... done.
==> Validando el archivo fuente con md5sums...
qcma ... Saltando
==> Descomprimiendo fuentes...
-> Creating working copy of qcma git repo...
Cloning into 'qcma'...
done.
==> Iniciando build()...
Updating 'resources/translations/qcma_es.qm'...
Generated 95 translation(s) (95 finished and 0 unfinished)
Ignored 7 untranslated source text(s)
Updating 'resources/translations/qcma_ja.qm'...
Generated 68 translation(s) (68 finished and 0 unfinished)
Ignored 34 untranslated source text(s)
( test -e Makefile.qcma_gui || /usr/bin/qmake-qt5 /tmp/yaourt-tmp-javi/aur-qcma-git/src/qcma/qcma_gui.pro PREFIX=/usr -o Makefile.qcma_gui ) && make -f Makefile.qcma_gui
make[1]: Entering directory '/tmp/yaourt-tmp-javi/aur-qcma-git/src/qcma'
/usr/lib/qt/bin/uic src/forms/configwidget.ui -o ui_configwidget.h
/usr/lib/qt/bin/uic src/forms/backupmanagerform.ui -o ui_backupmanagerform.h
/usr/lib/qt/bin/uic src/forms/backupitem.ui -o ui_backupitem.h
/usr/lib/qt/bin/uic src/forms/confirmdialog.ui -o ui_confirmdialog.h
/usr/lib/qt/bin/uic src/forms/progressform.ui -o ui_progressform.h
/usr/lib/qt/bin/uic src/forms/pinform.ui -o ui_pinform.h
g++ -c -pipe -Wno-write-strings -Wall -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong --param=ssp-buffer-size=4 -Wall -W -D_REENTRANT -fPIE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -DQCMA_VER="v0.3.2-3-ga85d49e" -DQT_NO_DEBUG -DQT_WIDGETS_LIB -DQT_DBUS_LIB -DQT_SQL_LIB -DQT_NETWORK_LIB -DQT_GUI_LIB -DQT_CORE_LIB -I/usr/lib/qt/mkspecs/linux-g++ -I. -Isrc -isystem /usr/include/libusb-1.0 -isystem /usr/include/libxml2 -isystem /usr/include/qt -isystem /usr/include/qt/QtWidgets -isystem /usr/include/qt/QtDBus -isystem /usr/include/qt/QtSql -isystem /usr/include/qt/QtNetwork -isystem /usr/include/qt/QtGui -isystem /usr/include/qt/QtCore -I. -I. -o capability.o src/capability.cpp
In file included from src/capability.cpp:20:0:
src/capability.h: En la función miembro ‘const char* DeviceCapability::getOnlineId()’:
src/capability.h:39:26: error: ‘vita_info_t’ no tiene un miembro llamado ‘onlineId’
return vita_info.onlineId;
^
src/capability.h: En la función miembro ‘const char* DeviceCapability::getModelInfo()’:
src/capability.h:42:26: error: ‘vita_info_t’ no tiene un miembro llamado ‘modelInfo’
return vita_info.modelInfo;
^
src/capability.cpp: En el destructor ‘DeviceCapability::~DeviceCapability()’:
src/capability.cpp:124:42: error: ‘VitaMTP_Data_Free_VitaInfo’ no se declaró en este ámbito
VitaMTP_Data_Free_VitaInfo(&vita_info);
^
Makefile.qcma_gui:663: recipe for target 'capability.o' failed
make[1]: *** [capability.o] Error 1
make[1]: Leaving directory '/tmp/yaourt-tmp-javi/aur-qcma-git/src/qcma'
Makefile:37: recipe for target 'sub-qcma_gui-pro-make_first' failed
make: *** [sub-qcma_gui-pro-make_first] Error 2
==> ERROR: Se produjo un error en build().
Cancelando...
==> ERROR: Makepkg no ha podido compilar qcma-git.

Debian is now transitioning to ffmpeg (and avcodec fork will likely be left to die)

https://lwn.net/Articles/607591/

Needs changes in debian/control

Hi just want to share my experienced with qcma in mac when connecting , im not avail to connect, any advice on how to make this work?

Hi,

Feel free to close this as it's a question and not a bug report. I'd like to create a Cinnamon applet for QCMA. It would do the same as your systray icon but it would look native and the user would be able to place it anywhere on the panel (or on the desktop as a desklet). Depending on whether the applet is there or not, Cinnamon would either show the applet or your systray icon. I'm missing a few info about QCMA to implement this:

Once qcma is running, is it possible to invoke the backup manager from the command line or over dbus or via any other method?

Also if you're interested this can be ported as a GNOME extension pretty easily.

Note: I'm not suggesting to replace the systray here (which is cross-DE and cross-platform) but this would be handy to Cinnamon/Shell users.

http://cinnamon-spices.linuxmint.com/applets
https://extensions.gnome.org

Having an issue when i try to update.
C0-10139-4
Only thing i could found on the internet was that it has something to do with the region (not confirmed) but i tried every region now and it failed every time

The console will just say (could not connect to network) instaid of showing the content forcing me to restart the program