Discover: doesnt show updates anymore, fails with error message

[star-buck]

maybe its due to 5.11.5 and gone with 5.12? Octopi shows this:

[star-buck]

only found this so far: https://bugzilla.redhat.com/show_bug.cgi?id=1188455#c3

[star-buck]

will update via octopi now to plasma 5.12 and see if that fixes it...

[NuLogicSystems]

I don't think that's going to help. I'm getting a failed to initialize packagekit error on testing branch as well. This looks like a packagekit issue or bug, but it could also be a systemd issue. I'm looking into it.

[NuLogicSystems]

I just found this: https://forum.manjaro.org/t/stable-update-2018-01-29-kernels-mesa-xorg-server-browsers-msm-mhwd-gcc/39291/65

Looks like packagekit might just be broken, I'm going to keep looking.

[star-buck]

okay, thanks. Btw. video of discover after latest update here: https://www.dropbox.com/s/w198m4e812igwlr/discover-5.12.1.mkv?dl=0

[NuLogicSystems]

Yea, I'm getting the same thing. Looking for a solution..

[NuLogicSystems]

This is interesting:

[ajslye@Netrunner-Workstation ~]$ systemctl status packagekit
● packagekit.service - PackageKit Daemon
   Loaded: loaded (/usr/lib/systemd/system/packagekit.service; static; vendor preset: disabled)
   Active: failed (Result: core-dump) since Tue 2018-02-20 13:01:22 EST; 25s ago
  Process: 2292 ExecStart=/usr/lib/PackageKit/packagekitd (code=dumped, signal=TRAP)
 Main PID: 2292 (code=dumped, signal=TRAP)

Feb 20 13:01:22 Netrunner-Workstation systemd[1]: Starting PackageKit Daemon...
Feb 20 13:01:22 Netrunner-Workstation PackageKit[2292]: daemon start
Feb 20 13:01:22 Netrunner-Workstation packagekitd[2292]: Failed to initialize alpm: using /etc/PackageKit/alpm.d/pacman.conf: /etc/PackageKit
Feb 20 13:01:22 Netrunner-Workstation systemd[1]: packagekit.service: Main process exited, code=dumped, status=5/TRAP
Feb 20 13:01:22 Netrunner-Workstation systemd[1]: packagekit.service: Failed with result 'core-dump'.
Feb 20 13:01:22 Netrunner-Workstation systemd[1]: Failed to start PackageKit Daemon.
lines 1-12/12 (END)

That looks like the alpm backend might be causing issues again..

[NuLogicSystems]

I think I found the issue. When I ran /usr/lib/PackageKit/packagekitd manually I got this:

(packagekitd:2360): PackageKit-alpm-ERROR **: Failed to initialize alpm: using /etc/PackageKit/alpm.d/pacman.conf: /etc/PackageKit/alpm.d/pacman.conf:8/etc/pacman.conf:20unrecognised directive 'SyncFirst'
Trace/breakpoint trap (core dumped)

Remark out the SyncFirst line in /etc/pacman.conf and it works properly. It definitely looks like a bug in the alpm backend of packagekit..

[star-buck]

Whats alpm? On Feb 20, 2018 19:12, "James Kittsmiller" notifications@github.com wrote:

I think I found the issue. When I ran /usr/lib/PackageKit/packagekitd manually I got this: (packagekitd:2360): PackageKit-alpm-ERROR **: Failed to initialize alpm: using /etc/PackageKit/alpm.d/pacman.conf: /etc/PackageKit/alpm.d/pacman. conf:8/etc/pacman.conf:20unrecognised directive 'SyncFirst' Trace/breakpoint trap (core dumped) Remark out the SyncFirst line and it works properly. It's definitely looks like a bug in the alpm backend of packagekit..

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/netrunner-rolling/2018.01/issues/55#issuecomment-367067399, or mute the thread https://github.com/notifications/unsubscribe-auth/AAzRhlTv7y9INYwaZ2S8NM1CkMQRn7XWks5tWwr1gaJpZM4SMSwO .

[NuLogicSystems]

Arch Linux Package Management https://www.archlinux.org/pacman/#_history

Packagekit backend: https://github.com/hughsie/PackageKit/tree/master/backends/alpm

[NuLogicSystems]

And I found this issue (bug) report: https://github.com/hughsie/PackageKit/issues/237

[star-buck]

@NuLogicSystems : Can we update our package to fix it? or is manjaro working on a fix? Does it even happen on Manjaro KDE?

[NuLogicSystems]

Kerik had patched packagekit for syncfirst, and it is now in manjaro-unstable. https://github.com/manjaro/packages-community/blob/master/packagekit/0001-Fix-SyncFirst-crash.patch https://lists.manjaro.org/pipermail/manjaro-packages/Week-of-Mon-20180219/014971.html

[star-buck]

Any ETA when it lands for netrunner rolling users?

[NuLogicSystems]

For packages to go from unstable to stable in manjaro, this usually takes aprox. a week or two.

[star-buck]

Can we provide this earlier, like with a smaller version number, so it gets simply superseeded when it hits officially manjaro repos? On Feb 21, 2018 10:32, "James Kittsmiller" notifications@github.com wrote:

For packages to go from unstable to stable in manjaro, this usually takes aprox. a week or two.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/netrunner-rolling/2018.01/issues/55#issuecomment-367264935, or mute the thread https://github.com/notifications/unsubscribe-auth/AAzRhrXcaxhAwdm1U8sDL3VBMLfouvQsks5tW-KggaJpZM4SMSwO .

[NuLogicSystems]

Manjaro's repositories are before ours in the pacman tree. I can pull it into our repo but it will require manual upgrade. pacman only upgrades in order of repository hierarchy, regardless of version number. I can see if I can't get them to fast track the process for us.

[star-buck]

Can you do that and we testcase how it goes? Tgen i can announce a hotfix on the website and in forums/readme. On Feb 21, 2018 10:53, "James Kittsmiller" notifications@github.com wrote:

Manjaro's repositories are before ours in the pacman tree. I can pull it into our repo but it will require manual upgrade. pacman only upgrades in order of repository hierarchy, regardless of version number.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/netrunner-rolling/2018.01/issues/55#issuecomment-367271096, or mute the thread https://github.com/notifications/unsubscribe-auth/AAzRhuiXKEmczTrva7GYtBYgevWR33NNks5tW-eggaJpZM4SMSwO .

[NuLogicSystems]

Yes, I was planing on pushing some updates this afternoon when I get back anyway, I will add these two packages to that push.

[NuLogicSystems]

There is also the downgrade and hold option, I had to do this for cups not too long ago. sudo pacman -S downgrade sudo downgrade packagekit choose 1.1.7 from the local listing. When it asks to add packagekit to ignore list you Y. Then once the updated package hits remove it from the ignorelist in the pacman.conf file. Ref: https://wiki.manjaro.org/index.php?title=Using_Downgrade

[star-buck]

lets not do something this complicated

[NuLogicSystems]

Well, I be back in town and heading to the office in about 6 hours. I will pull those packages, add them to what I already have in netrunner-testing, and merge them into the main netrunner repo at that time.

[NuLogicSystems]

As a quick hot fix:

sudo pacman -U http://mirror.dacentec.com/manjaro/unstable/community/x86_64/packagekit-1.1.8-2.1-x86_64.pkg.tar.xz http://mirror.dacentec.com/manjaro/unstable/community/x86_64/libpackagekit-glib-1.1.8-2.1-x86_64.pkg.tar.xz --noconfirm

[NuLogicSystems]

These packages are now in the netrunner repository, to upgrade:

sudo pacman -S netrunner/packagekit netrunner/libpackagekit-glib --noconfirm

[star-buck]

Why nulogic instead of netrunner?

[NuLogicSystems]

Whoops, sorry about that, I just typed it out the wrong. I've corrected my previous comment.

[star-buck]

sudo pacman -S netrunner/packagekit netrunner/libpackagekit --noconfirm error: target not found: libpackagekit

[notuxius]

libpackagekit-glib

[NuLogicSystems]

Thanks notuxius, I can't believe I missed that. Fixed