Bug 367745 - KDE neon User Edition 5.7 - xenial 16.04 - sudo apt-get upgrade - appstream is crashing the install or upgrade of software - appstreamcli: symbol lookup error: appstreamcli: undefined symbol: as_data_pool_refresh_cache
Summary: KDE neon User Edition 5.7 - xenial 16.04 - sudo apt-get upgrade - appstream i...
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: neon
Classification: KDE Neon
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Neon Linux
: NOR grave
Target Milestone: ---
Assignee: Neon Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-08-23 23:39 UTC by Cristian Umaña
Modified: 2016-08-26 23:01 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Cristian Umaña 2016-08-23 23:39:57 UTC 
When I trying to keep up to date my software I encountering the following problem:

qma@mjolnir:~$ sudo apt-get upgrade
The following packages will be upgraded:
  appstream
1 upgraded, 0 newly installed, 0 to remove and 7 not upgraded.
Need to get 0 B/70,7 kB of archives.
After this operation, 292 kB of additional disk space will be used.
(Reading database ... 319667 files and directories currently installed.)
Preparing to unpack .../appstream_0.9.7-1+16.04+build1_amd64.deb ...
Unpacking appstream (0.9.7-1+16.04+build1) over (0.9.4-1ubuntu1) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up appstream (0.9.7-1+16.04+build1) ...
appstreamcli: symbol lookup error: appstreamcli: undefined symbol: as_data_pool_refresh_cache


Reproducible: Always

Steps to Reproduce:
1. sudo apt-get upgrade
2. accept the upgrade for appstream
3. appstreamcli: symbol lookup error: appstreamcli: undefined symbol: as_data_pool_refresh_cache

Actual Results:  
I cannot install or upgrade any software.

Expected Results:  
Upgrade the appstream software and resume normal operation.

Reading about appstream I found that the current stable version for Xenial is appstream_0.9.4-1ubuntu1 

But KDE Neon is installing the version 0.9.7-1+16.04+build1 that I think is for Yakkety and is outdated I found the link to this version here:
http://archive.neon.kde.org/dev/stable/pool/main/a/appstream/

The current appstream version for Yakkety is 0.9.8-4 
https://launchpad.net/ubuntu/+source/appstream

I found a workaround to temporary solve the problem:

```
cd /tmp && mkdir asfix
cd asfix
wget https://launchpad.net/ubuntu/+archive/primary/+files/appstream_0.9.4-1ubuntu1_amd64.deb
wget https://launchpad.net/ubuntu/+archive/primary/+files/libappstream3_0.9.4-1ubuntu1_amd64.deb
sudo dpkg -i *.deb
```

More details about the solution on this link:
https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1579712/comments/24

My Kde Neon configuration is:

qma@mjolnir:~$ lsb_release -a
No LSB modules are available.
Distributor ID: neon
Description:    KDE neon User Edition 5.7
Release:        16.04
Codename:       xenial

qma@mjolnir:~$ uname -a
Linux mjolnir 4.6.2-040602-generic #201606100516 SMP Fri Jun 10 09:18:34 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

Regards,
Comment 1 Christoph Feck 2016-08-25 02:33:16 UTC 
Please report this issue to the bug tracker of your distribution.
Comment 2 Cristian Umaña 2016-08-25 17:16:44 UTC 
Hi, I confused, Does KDE Neon has a different bug tracking system?

Regards
Comment 3 Christoph Feck 2016-08-25 21:46:13 UTC 
I can reassign to neon developers, but this one really looks like a downstream (Ubuntu) problem.
Comment 4 Cristian Umaña 2016-08-25 22:57:17 UTC 
Hi, thanks, it's a problem with KDE Neon packages, non Ubuntu's packages.

I now know it, because I did the following:

The offending appstream comes from the Neon archive:
http://archive.neon.kde.org/dev/stable/pool/main/a/appstream/

There's a file in my sources list:
/etc/apt/sources.list.d/neon.list

It contains this line:
deb http://archive.neon.kde.org/user xenial main

If I comment it out and did the upgrade everything works, only with ubuntus ppa's and appstream doesn't break the software updates.

But If I leave it out, KDE Neon packages, will not update.

Regards,
Comment 5 Harald Sitter 2016-08-26 08:58:03 UTC 
(In reply to Cristian Umaña from comment #0)
> qma@mjolnir:~$ sudo apt-get upgrade

Always use dist-upgrade.

> But KDE Neon is installing the version 0.9.7-1+16.04+build1 that I think is
> for Yakkety and is outdated I found the link to this version here:
> http://archive.neon.kde.org/dev/stable/pool/main/a/appstream/
> 
> The current appstream version for Yakkety is 0.9.8-4 
> https://launchpad.net/ubuntu/+source/appstream

Why are you talking about yakkety?

> qma@mjolnir:~$ uname -a
> Linux mjolnir 4.6.2-040602-generic #201606100516 SMP Fri Jun 10 09:18:34 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

That's not a supported kernel.

(In reply to Cristian Umaña from comment #4)
> The offending appstream comes from the Neon archive:
> http://archive.neon.kde.org/dev/stable/pool/main/a/appstream/
> 
> There's a file in my sources list:
> /etc/apt/sources.list.d/neon.list
> 
> It contains this line:
> deb http://archive.neon.kde.org/user xenial main

If you look closely at the URLs you'll see that they don't actually add up.

If you dist-upgrade. Does the issue persist?
Comment 6 Cristian Umaña 2016-08-26 23:01:43 UTC 
> Always use dist-upgrade
Thanks I didn't know that, I think that dist-upgrade is for a complete distro upgrade.

> Why are you talking about yakkety?
This link:
https://launchpad.net/ubuntu/+source/appstream

It's the ubuntu archive for appstream 0.9.7-1 and 0.9.8-4 both are intended for Yakkety
The appstream version 0.9.4-1 is for Xenial

>> qma@mjolnir:~$ uname -a
>> Linux mjolnir 4.6.2-040602-generic #201606100516 SMP Fri Jun 10 09:18:34 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux 
>
>That's not a supported kernel.
My computer was having troubles with my wifi card and that kernel solved it

>If you look closely at the URLs you'll see that they don't actually add up. 
Well you're right they seem different searching on google it was the only place I found it

>If you dist-upgrade. Does the issue persist?
I dist-upgrade and everything is working now, thanks for all the help, I'm sorry to bother you
Regards,