[Testing Update] 2019-06-02 - ZFS, Deepin, KDE-Git, Haskell, Python

This morning, I got a new Kernel Version: 4.19.48-1-MANJARO
And Octopi was moved to community, and maybe upgraded as well.

No breakage so far.

Could this indicate that octopi will be removed in favor of pamac-qt when it will be stable?

I too received several updates this morning; one broke the update process. At some point in the past I had added missing Breath status icons for:
media-playback-paused.svg
media-playback-playing.svg
media-playback-stopped.svg

The breath-icon-theme (0.4.0-1 -> 0.4.0-2) update gave the following errors:

conflicting files:
breath-icon-theme: /usr/share/icons/breath/status/16/media-playback-paused.svg already exists in filesystem
breath-icon-theme: /usr/share/icons/breath/status/16/media-playback-playing.svg already exists in filesystem
breath-icon-theme: /usr/share/icons/breath/status/16/media-playback-stopped.svg already exists in filesystem
breath-icon-theme: /usr/share/icons/breath/status/22/media-playback-paused.svg already exists in filesystem
breath-icon-theme: /usr/share/icons/breath/status/22/media-playback-playing.svg already exists in filesystem
breath-icon-theme: /usr/share/icons/breath/status/22/media-playback-stopped.svg already exists in filesystem
breath-icon-theme: /usr/share/icons/breath/status/24/media-playback-paused.svg already exists in filesystem
breath-icon-theme: /usr/share/icons/breath/status/24/media-playback-playing.svg already exists in filesystem
breath-icon-theme: /usr/share/icons/breath/status/24/media-playback-stopped.svg already exists in filesystem

After deleting the offending status Breath icons I re-ran the update (sudo pacman -Syu). It completed with no errors.

1 Like

Yes and finally its issues are resolved (in 0.9.0-8). At least my preferred "Run in terminal" option works fine again.

2 Likes

I had no time yet to announce the update yet. Was too busy with 18.1.0-rc1 release.

5 Likes

Update today works fine on 18.1 testing KDE.

1 Like

No worries. :slight_smile: Really appreciate fixing Octopi behavior :wink:

3 Likes

Xfce and Cinnamon: No issues with today's update.

Kde-18.0.4-testing updated fine today, thanks!

have twice this error

juin 06 23:22:18 mjro lightdm[688]: gkr-pam: unable to locate daemon control file
juin 06 23:22:23 mjro lightdm[703]: gkr-pam: unable to locate daemon control file

It's all good.
Updates went off without a hitch, changed from kernel 5.0.21 to 5.1.7.

Xfce (4.12) desktop icons are being jumbled or shuffled again on boot. 3/5 boots so far. This has not been a problem for me since using SSD drive. It is problem again.

Something to do with one of these packages I am guessing...

gtk-update-icon-cache-1:3.24.8+177+gae2ef1472c-1
gtk3-1:3.24.8+177+gae2ef1472c-1

[Currently holding all kernel and nvidia packages due to cuda/nvenc segmentation fault in nvidia 430.14, and now this desktop icon problem again. This is not a good week of updates for me. :panda_face:]

Recent relevant xfce change (see https://bugzilla.xfce.org/show_bug.cgi?id=11266 - comment #120 and following) maybe it has affected you?

Package changes might be found here.

1 Like

2019-06-06 update:
kde k51 & VM i3 k52 - all updates just fine
k52 still wont work for my kde but it's not a problem)
Thanks.

Actually, I have been using xfdesktop 4.13.4 for 2 weeks now, and I think my desktop icons started getting shuffled again since then. Today was just the worst. Maybe it wasn't the gtk3 packages after all. So whatever they changed made it worse not better for me.

I am not too mad since I am used to this problem, and I still make backups of my desktop icons every hour. I have 100+ icons on my desktop and it is a pain to re-arrange them by hand.

The nuclear option worked for me :ok_hand:

1 Like

There is definitely something weird with gtk3-1:3.24.8+177+gae2ef1472c-1. Thunar bulk rename tool (Thunar 1.8.6-2) no longer updates the last filename on the fly. Downgrading to gtk3-1:3.24.8-1 fixes.

Screenshot of broken behavior:

I also downgraded gtk-update-icon-cache as well to the same version previous, but I don't know if that is really necessary.

1 Like

Happened to me too on the stable update and, as you posted, deleting those files allows the update to continue....

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.

Forum kindly sponsored by Bytemark