libmarblewidget16 4:4.11.2 packaged wrong version? Manual download and copy .so allows marble and digikam to run

Bug #1245864 reported by JJ
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
marble (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I _solved_ the following issue by replacing /usr/lib/libmarblewidget.so.0.16.2 with a manually downloaded and extracted copy.
                                                                                       ( from http://packages.ubuntu.com/saucy/i386/libmarblewidget16/download )

Before I did that I was getting errors trying to run marble and digikam:

digikam: symbol lookup error: /usr/lib/libkgeomap.so.1: undefined symbol: _ZNK6Marble14LayerInterface12runtimeTraceEv

marble: Symbol `_ZTVN6Marble17GeoDataLineStringE' has different size in shared object, consider re-linking
marble: symbol lookup error: marble: undefined symbol: _ZN6Marble12MarbleLocale20setMeasurementSystemEN7QLocale17MeasurementSystemE

My apt-get sources are attached ( generally deb http://ca.archive.ubuntu.com/ubuntu/ saucy main restricted )

The BAD file MD5: aa365fe05a894642a8a551a232f86b86 libmarblewidget.so.0.16.2.bak
installed from apt-get install

The GOOD file MD5: 388cd41fc3597134ae362bbf0626c0e9 libmarblewidget.so.0.16.2
copied from a manually uncompressed download from http://packages.ubuntu.com/saucy/i386/libmarblewidget16/download

lsb_release -rd
Description: Ubuntu 13.10
Release: 13.10

( copied bad version back in place and ran this )
apt-cache policy libmarblewidget16
libmarblewidget16:
  Installed: 4:4.11.2-0ubuntu1
  Candidate: 4:4.11.2-0ubuntu1
  Version table:
 *** 4:4.11.2-0ubuntu1 0
        500 http://ca.archive.ubuntu.com/ubuntu/ saucy/universe i386 Packages
        100 /var/lib/dpkg/status

Revision history for this message
JJ (bjustjones) wrote :
tags: added: saucy
Revision history for this message
JJ (bjustjones) wrote :

I manually unpacked the library from the libmarblewidget16_4%3a4.11.2-0ubuntu1_i386.deb in my /var/cache/apt/archives and did an MD5:

388cd41fc3597134ae362bbf0626c0e9 libmarblewidget.so.0.16.2
which matches the GOOD one above !?!?

So I looked to see if there were any other packages that included the file:
apt-file search libmarblewidget.so.0.16.2
libmarblewidget16: /usr/lib/libmarblewidget.so.0.16.2
marble-dbg: /usr/lib/debug/usr/lib/libmarblewidget.so.0.16.2

but of those two I only have the libmarblewidget16 package installed.

Maybe my copy was corrupted some other way?
Wait and see if anyone else has problems?

Revision history for this message
Harald Sitter (apachelogger) wrote :

> Maybe my copy was corrupted some other way?

Yes.
Most likely you'd want to look for problems with your hard disk [1] [2]. This type of corruption can have a wide range of causes finding out what went wrong is not particularly trivial unfortunately. Generally speaking though from a package POV this cannot happen. dpkg syncs every file (i.e. makes sure they are actually physically written, not just cached on the hard disk/kernel) so even if your system lost power dpkg would know that the package installation did not finish as expected and ask you to look into it etc. With that in mind the corrpution probably was caused after installation of the package, and hard disk failure is the most likely there. Other options would include file system failure (which would also be a curious point of failure because usually a file corruption only happens when something is writing to that file and system files are only written to during installation/upgrade), or some script/application manually writing the bogus file version.

To ensure no other files are corrupted you can use the package 'debsums', it will check whether the checksums of all files installed from a package match with what they should be.

[1] http://askubuntu.com/questions/59064/how-to-run-a-checkdisk
[2] https://help.ubuntu.com/community/Smartmontools

Changed in marble (Ubuntu):
status: New → Invalid
Revision history for this message
JJ (bjustjones) wrote :

Agreed.

Thank you for your informative response.

debsums -s didn't find problems with anything else.

I'll run an extensive (smartmon!) test on the brand-new harddrive so i can take advantage of the warranty if necessary.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.