Trouble with Faster Application Manager / libqtm
 

Right, so there I was trying to install backup manager with the faster application manager, and to my shock and surprise it throws the following error log at me:

--- 2013-05-28 02:01:07 ---
Start reading package lists
--- 2013-05-28 02:01:21 ---
Finished reading package lists
--- 2013-05-28 02:01:21 ---
Start fetching package dates
--- 2013-05-28 02:01:21 ---
need to fetch date for 0 packages
--- 2013-05-28 02:01:21 ---
sent 0 requests, received 0 replies with 0 errors
--- 2013-05-28 02:01:21 ---
Finished fetching package dates
--- 2013-05-28 02:02:43 ---
/usr/bin/apt-get -qsy --allow-unauthenticated -o Dir::Etc::sourcelist=/opt/fapman-cache/sources.list -o Dir::State::lists=/opt/fapman-cache/lists -o Dir::Etc::sourceparts="" --auto-remove install backupmenu
--- 2013-05-28 02:02:47 ---
Output from last process:
---
Reading package lists...
Building dependency tree...
Reading state information...
The following packages were automatically installed and are no longer required:
dsme-thermalobject-surface libqtm-bearer libqt4-translations
Hmm, seems like the AutoRemover destroyed something which really
shouldn't happen. Please file a bug report against apt.

The following information may help to resolve the situation:

The following packages have unmet dependencies:
qtm-maemo-metapackage: Depends: libqtm-bearer (>= 1:1.0.2-maemo1) but it is not going to be installed
E: Internal Error, AutoRemover broke stuff


So, obviously things arent working like they're supposed to. Happens with all the applications i try to install.

The appication worked fine previously but then i thought "what the hell i can remove some unneeded software, and inserted the following command in x term: apt-get remove --purge ap-installer amazon-installer foreca-installer facebook-installer tutorial-home-applet google-search-widget ovi-promotion-widget sharing-service-ovi

In retrospect that might have not been the smartest thing to do, as i assume that somehow screwed up my libqtm dependencies. Originally i was missing a whole lot more than just the "bearer". Tried fixing it myself, another mistake. Here's the command: apt-get install libqtm-contacts libqtm-messaging libqtm-multimedia libqtm-publishsubscribe libqtm-sensors libqtm-serviceframework libqtm-systeminfo libqtm-versit

So, all in all, i haven't achieved much. still cant install anything properly with the manager. Any tips?

Re: Trouble with Faster Application Manager / libqtm
 

I believe it's part of QtMobility. Have you tried fixing it by force?

Re: Trouble with Faster Application Manager / libqtm
 

Apparently FAM has known issues. I didn't know it was on the list of broken packages either until I came across said list by chance:

http://wiki.maemo.org/Community_SSU/...roken_packages
http://talk.maemo.org/showthread.php?t=65996

Re: Trouble with Faster Application Manager / libqtm
 

The libqtm-bearer package also pops up for installation in HAM along the road to installing CSSU.

Once Step 5 of the installation has been done, HAM will show the package (and several others) as installation candidates (but they can't be installed).

Proceeding with the installation steps clears the issue.

merlin1991 expands on the issue here:
http://mg.pov.lt/maemo-ssu-irclog/%2...11-13T21:09:06

Has the OP tried to enable CSSU, and not completed step 6 (clicking on the Community SSU icon in the app menu)?

Re: Trouble with Faster Application Manager / libqtm
 

looks like that did it. thanks!

EDIT: woops, meant to quote antonie's post.

Re: Trouble with Faster Application Manager / libqtm
 

If you turn off the autoremove option, it works pretty well in my experience.

Re: Trouble with Faster Application Manager / libqtm
 

@salamisami

Please mark the thread as "solved" for future reference.

Re: Trouble with Faster Application Manager / libqtm
 

You can edit your post to quote the correct one. I wouldn't like to take undue credit.

Re: Trouble with Faster Application Manager / libqtm
 

I can only speak for myself, but the broken package info was new to me, plus the thread contained the same solution, so credit where it's due, pichlo ;)