Thank you for notifying us of the issue.
Unfortunately Discover uses packagekit in the background.
The problem with packagekit is that it just doesn’t handle manual interventions (conflicting packages, package name changes, separating of packages, etc.) properly.
I’ve updated the announcement to reflect this issue.
The update was smooth and no failure happened. Except that, in System Settings there are few modules that need to be removed, because they did not represent the actual ones and are duplicates of the others. I am attaching screenshot. Thanx.
We don’t add or remove anything from usr/share/kservices5/, our adjustment (reorganization) of system settings are done elsewhere. Those entries in tree view are upstream grouping settings not actual modules, these are not used by the Netrunner regrouping of system settings and why your getting those errors. Please switch back to icon view or you can just ignore those entries. What your looking for would be under Personal > Desktop Appearance.
Tree view shows all groupings and modules.
Icon view does not show unused entries or missing modules.
I have noticed two problems after this update. They are:
firefox-kde does not obey the system theme (Breeze Dark) in its panels at the top of the window. They are light grey rather than black, as before. Starting firefox in safemode does not seem to help. Interestingly, thunderbird-kde does not exhibit this changed behaviour. The GTK3 theme is Carbon and GTK2 theme is carbon-gtk.
The default audio input device in system-settings, which was previously set to be “rear microphone” gets somehow changed to “front microphone” after the update, and thus interferes with the operation of skype, requiring manual intervention. I wonder if there is a foolproof method of setting it that does not get changed after an update. The rear microphone is also erroneously reported by PulseAudio Volume Control as “unplugged” even when left connected.
I am reporting these because they were noticed after the most recent update, but cannot be certain that they are not due to other causes. They are more inconveniences than major problems.
Firefox has changed from using GTK2 to GTK3 and thus would be using Carbon.
Try changing the Gnome Application Settings from breeze-gtk - gtk2 and Carbon - gtk3 settings to the new upstream Breeze Dark theme.
Personally, i think the the KDE Artwork team have done an excellent job on their GTK breeze themes.
Pulses audios per user settings are stored in your home directory under .config/pulse/.
However, If the issue is with the system wide defaults in the pulse audio packaging, then there is nothing that can be done.
This is an upstream arch package which does use the do not overwrite (backup) string for it configuration files, and any changes to them would be lost when updated.
and selected Breeze-Dark for GTK and have the firefox panels now honouring the Breeze Dark theme.
The pulseaudio settings under ~/.config/pulse comprise several files, only two of which are ASCII text, one for source and another for sink. Neither seems to have any device-specific setting like “front microphone” or “rear microphone”. My previous experience in Kubuntu has been that PulseAudio has always been fraught with unexpected behaviour after updates, and manually configured settings on PulseAudio Volume Control do not seem to persist after a system poweroff. The same appears to be happening in NRR now. Should I be changing the alsa settings on the terminal instead?
Changing the alsa settings did not seem to affect the behaviour of the audio input device. What is concerning, though, is that System Settings does not persistently honour the “Rear Microphone” selected as Input device in Audio Settings. It reverts to “Front Microphone” after each shutdown. I will run the most recent update to see if this goes away now.
Regarding the GUI for firefox, the KDE and GTK GUIs have an annoying discrepancy: The “Cancel” button is on the left for KDE and on the right for GTK when a binary choice is presented. In previous versions of firefox-kde, this was altered so that firefox-kde followed the KDE convention. This is now not so, and makes for a lot of habit-driven errors, since firefox-kde seems to follow the GTK convention at present.
Hmm, I never noticed this about Firefox, both the firefox and firefox-kde use GTK, the difference is firefox-kde uses the Suse patches for better integration. Firefox is now using GTK3 and may be partly to blame for some of these differences. Since the Manjaro team are maintaining the firefox-kde packages, would you mind posting this issue in the Manjaro forums as well?
Well why use Muon at all?
Octopi has its own updater that handles conflicts just fine.
Maybe the netrunner rolling edition should drop muon if its such dead weight?
I know that is blue systems baby but if it is so essential to things why have it so broken when it comes to arch style updates?
Just drop it, the things useless anyhow for a arch user.
Sorry for bringing up the old topic but it does seem like Muon is the rolling edition of Netrunners main weakness
