maemo.org - Talk - [Solved] application manager blocked

maemo.org - Talk (https://talk.maemo.org/index.php)

- Applications (https://talk.maemo.org/forumdisplay.php?f=41)

- - [Solved] application manager blocked (https://talk.maemo.org/showthread.php?t=82102)

[Solved] application manager blocked

Hello,
my app manager is blocked.
i get a dpkg error whenever I try to install or upgrade anythign
here is the last dozen lines of the log.
Ignore the timestamp issue (for this thread), that's because my system time is wrong.

Unpacking replacement mp-fremantle-community-pr ...
tar: ./postinst: Zeitstempel 2012-01-19 20:30:58 liegt 96212826.807981618 Sekunden in der Zukunft.
tar: ./md5sums: Zeitstempel 2012-01-19 20:31:10 liegt 96212838.803831228 Sekunden in der Zukunft.
tar: ./control: Zeitstempel 2012-01-19 20:31:10 liegt 96212838.791532643 Sekunden in der Zukunft.
tar: .: Zeitstempel 2012-01-19 20:31:10 liegt 96212838.789365895 Sekunden in der Zukunft.
Preparing to replace qmltube 1.1.1 (using .../qmltube_1.2.6_armel.deb) ...
Unpacking replacement qmltube ...
dpkg: error processing /var/cache/apt/archives/qmltube_1.2.6_armel.deb (--unpack):
trying to overwrite `/usr/lib/hildon-desktop/qmltube-widget', which is also in package qmltube-widget
tar: ./prerm: Zeitstempel 2011-07-21 16:20:37 liegt 80469391.233854433 Sekunden in der Zukunft.
tar: ./postinst: Zeitstempel 2011-07-21 16:20:37 liegt 80469391.218168397 Sekunden in der Zukunft.
tar: ./md5sums: Zeitstempel 2011-07-21 16:20:37 liegt 80469391.214475769 Sekunden in der Zukunft.
tar: ./control: Zeitstempel 2011-07-21 16:20:37 liegt 80469391.210600036 Sekunden in der Zukunft.
tar: .: Zeitstempel 2011-07-21 16:20:37 liegt 80469391.207517761 Sekunden in der Zukunft.
Preparing to replace filebox 0.7-2 (using .../filebox_0.7-4_armel.deb) ...
Unpacking replacement filebox ...
Preparing to replace qcpufreq 0.4.1-1 (using .../qcpufreq_0.4.4-1_armel.deb) ...
Unpacking replacement qcpufreq ...
Errors were encountered while processing:
/var/cache/apt/archives/qmltube_1.2.6_armel.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Re: application manager blocked

Try disabling all repos and enabling one by one. Which one's the problem?

Sounds like you need to clear the cache. Search for dpkg and apt commands. There might be some useful info in the maemo Wiki as well.

Re: application manager blocked

Quote:

Originally Posted by demolition (Post 1160507)

i tried to disable all the repos and exited from appman, then went back in and reenabled them except for extras-devel. I get the same error message though

Re: application manager blocked

Set the clock of your N900 to the right time. It seems your clock drifted off and since the repository files thus have timestamps of the future, they might cause trouble.

Re: application manager blocked

Try to delete these files from filebox.:confused:

/var/cache/apt/pkgcache.bin
/var/cache/apt/srcpkgcache

or in x-terminal

sudogainroot
rm /var/cache/apt/pkgcache.bin
rm /var/cache/apt/srcpkgcache

then

apt-get autoremove
apt-get autoclean
apt-get clean
apt-get install -f
apt-get update -f
apt-get update

Let me know how it goes:D:D

Re: application manager blocked

I set the clock right now!

Quote:

Originally Posted by D@vIcHoJD (Post 1160599)

Try to delete these files from filebox.:confused:

/var/cache/apt/pkgcache.bin
/var/cache/apt/srcpkgcache

or in x-terminal

sudogainroot
rm /var/cache/apt/pkgcache.bin
rm /var/cache/apt/srcpkgcache

that was supposed to be "srcpkgcache.BIN", was it?

Quote:

then

apt-get autoremove
apt-get autoclean
apt-get clean
apt-get install -f
apt-get update -f
apt-get update

- autoremove returned another error "while processing libassa", see 1st screenshot. I've seen this before, I have a hunch that stupid libassa has been causing all this.

Attachment 24952

- autoclean for some reason deleted: ghosts over board,
Cutetubeqml, and Qcpufreq and Filebox!

- clean returned no output
- install -f returned the same error with libassa as autoremove, see 1st screenshot.

- update -f and -update returned what you see on 2nd screenshot:
Attachment 24953

Thanks for any hints!

Re: application manager blocked

The documentations are strip from the packages to save space. To get rid of the libassa error, just create an empty directory

Code:

sudo gainroot

mkdir /usr/share/doc/libassa

dpkg --configure -a

The

Quote:

W: Conflicting distribution: Blah,blah,blah

warning might get ignore or corrected in your repository list.

The time stamp warning/error might get created by a corrupted file system, which now is mounted only with read permissions. Usually this is the MyDocs partition

Code:

sudo gainroot

umount /dev/mmcblk0p1

fsck -af /dev/mmcblk0p1

mount /dev/mmcblk0p1 /home/user/MyDocs

It could get ugly if however the optfs partition got corrupted while you do not have any of BackupMenu, Nitdroid, or MeeGo installed to boot of.
But lets hope to get things done with above code!

Please post any errors here.

Re: application manager blocked

Quote:

Originally Posted by michaaa62 (Post 1161154)

The documentations are strip from the packages to save space. To get rid of the libassa error, just create an empty directory

Code:

sudo gainroot

mkdir /usr/share/doc/libassa

dpkg --configure -a

The warning might get ignore or corrected in your repository list.

The time stamp warning/error might get created by a corrupted file system, which now is mounted only with read permissions. Usually this is the MyDocs partition

Code:

sudo gainroot

umount /dev/mmcblk0p1

fsck -af /dev/mmcblk0p1

mount /dev/mmcblk0p1 /home/user/MyDocs

the timestamp error didn't show up anymore after I corrected system time.

Exactly which information in which repo setting do I need to change to what? I looked at all the repos settings in app man. The only thing I find weird there is the repos in faster app man don't have the same names as in HAM, even though I just imported them all from HAM. for making any installations i usually use faster app man or apt-get in xterm.

here's output from your commands:

Code:

/home/user # umount /dev/mmcb1k0p1

umount: cannot umount /dev/mmcb1k0p1: No such file or directory

/home/user # umount /dev/mmcblk0p1

/home/user # fsck -af /dev/mmcblk0b1

fsck 1.41.3.maemo0 (12-Oct-2008)

fsck.ext2: No such file or directory while trying to open /dev/mmcblk0b1

/dev/mmcblk0b1: 

The superblock could not be read or does not describe a correct ext2

filesystem.  If the device is valid and it really contains an ext2

filesystem (and not swap or ufs or something else), then the superblock

is corrupt, and you might try running e2fsck with an alternate superblock:

    e2fsck -b 8193 <device>



/home/user # mount /dev/mmcblk0p1 /home/user/MyDocs

/home/user # mount /dev/mmcblk0p1 /home/user/MyDocs

Re: application manager blocked

@bennypr0fane,

In the post above you wrote mmcblk0b1. It should be mmcblk0p1 (p, not b).

But anyway, from the first post the problem is clear:

Unpacking replacement qmltube ...
dpkg: error processing /var/cache/apt/archives/qmltube_1.2.6_armel.deb (--unpack):
trying to overwrite `/usr/lib/hildon-desktop/qmltube-widget', which is also in package qmltube-widget

The qmltube package is trying to overwrite a file owned by the qmltube-widget package. Report to maintainer.

You could try first removing qmltube-widget and then installing qmltube and then try qmltube-widget.

But clearly the problem is with the maintainer(s) of qmltube and qmltube-widget.

Re: application manager blocked

I'm not sure which one fixed it, the qmltube or the libassa or the file system - probably all of them. However, everything's fine once more! Thanks a lot everyone!
I wonder how everything got so multiply messed up though....