Warning: elektroid-git: local (2.0.r6.ga62065c-1) is newer than pamac_aur (2.0.beta.r101.ge94eb07-1)
Warning: kvantum-theme-matchama: local (20191118-1) is newer than pamac_aur (r265.8525e05-2)
Resolving dependencies...
Checking inter-conflicts...
Warning: removing 'dbus' from target list because it conflicts with 'dbus-nosystemd'
Error: unresolvable package conflicts detected
Failed to prepare transaction:
conflicting dependencies:
- dbus-nosystemd and dbus-x11 are in conflict
Transaction cancelled.
is it safe to remove dbus-nosystemd or dbus-x11? I m a bit paranoid about that
I dont know how this got messed up, i was just trying to run an update as usual and didnt install any new packages in between as far as i remember…
Before we go any further, please post the content of your pacman.conf. You are using unsupported third-party repos and we need to know what modifications you have made.
cat /etc/pacman.conf
#
# /etc/pacman.conf
#
# See the pacman.conf(5) manpage for option and repository directives
#
# GENERAL OPTIONS
#
[options]
# The following paths are commented out with their default values listed.
# If you wish to use different paths, uncomment and update the paths.
#RootDir = /
#DBPath = /var/lib/pacman/
CacheDir = /var/cache/pacman/pkg/
#LogFile = /var/log/pacman.log
#GPGDir = /etc/pacman.d/gnupg/
#HookDir = /etc/pacman.d/hooks/
HoldPkg = pacman glibc manjaro-system
# If upgrades are available for these packages they will be asked for first
SyncFirst = manjaro-system archlinux-keyring manjaro-keyring
#XferCommand = /usr/bin/curl -C - -f %u > %o
#XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u
#CleanMethod = KeepInstalled
#UseDelta = 0.7
Architecture = auto
#IgnorePkg =
#IgnorePkg =
#IgnoreGroup =
#NoUpgrade =
#NoExtract =
# Misc options
#UseSyslog
#Color
#TotalDownload
# We cannot check disk space from within a chroot environment
CheckSpace
#VerbosePkgLists
# By default, pacman accepts packages signed by keys that its local keyring
# trusts (see pacman-key and its man page), as well as unsigned packages.
SigLevel = Required DatabaseOptional
LocalFileSigLevel = Optional
#RemoteFileSigLevel = Required
# NOTE: You must run `pacman-key --init` before first using pacman; the local
# keyring can then be populated with the keys of all official Manjaro Linux
# packagers with `pacman-key --populate archlinux manjaro`.
#
# REPOSITORIES
# - can be defined here or included from another file
# - pacman will search repositories in the order defined here
# - local/custom mirrors can be added here or in separate files
# - repositories listed first will take precedence when packages
# have identical names, regardless of version number
# - URLs will have $repo replaced by the name of the current repo
# - URLs will have $arch replaced by the name of the architecture
#
# Repository entries are of the format:
# [repo-name]
# Server = ServerName
# Include = IncludePath
#
# The header [repo-name] is crucial - it must be present and
# uncommented to enable the repo.
#
# The testing repositories are disabled by default. To enable, uncomment the
# repo name header and Include lines. You can add preferred servers immediately
# after the header, and they will be used before the default mirrors.
[core]
SigLevel = PackageRequired
Include = /etc/pacman.d/mirrorlist
[extra]
SigLevel = PackageRequired
Include = /etc/pacman.d/mirrorlist
[community]
SigLevel = PackageRequired
Include = /etc/pacman.d/mirrorlist
# If you want to run 32 bit applications on your x86_64 system,
# enable the multilib repositories as required here.
[multilib]
SigLevel = PackageRequired
Include = /etc/pacman.d/mirrorlist
# An example of a custom package repository. See the pacman manpage for
# tips on creating your own repositories.
#[custom]
#SigLevel = Optional TrustAll
#Server = file:///home/custompkgs
###REPO for MEGA###
#[DEB_Arch_Extra]
#SigLevel = Required TrustedOnly
#Server = https://mega.nz/linux/repo/Arch_Extra/x86_64/
###END REPO for MEGA###
pacman (or pamac?) certainly “thinks” that it is there
… just say yes to replace it?
You probably should install dbus - to replace dbus-x11
the former is the standard repository package - the latter is one from the AUR
… prefer the former to the latter
Using the AUR is not set and forget - it requires maintenance and, ideally, knowing what you are doing
To verify this sort of information in the future, go to Manjaro Packages: Packages and you’ll see that this package does not exist.
Manjaro users should always read the Stable Update Announcements, at least the first 2 posts. There is a section, where philm lists known issues and/or actions to take.
2022-12-20
dbus-x11 demoted to AUR
2022-10-05
ceph, ceph-libs and ceph-mgr dropped to the AUR
Looks like you’ll have some cleanup to do because of the foreign repo that was added to pacman.conf.
Thanks stargazer for the infos! Reading the posts now, although not sure what I would need to do to get back to order. when dbus-x11 demotes to AUR and ceph, ,.etc dropped to the AUR, do they compete with the "not foreign " repos and I should delete them? Is there a beginners thread where i can ask questions? It seems people get mad at me cause I have no clue, came from linux mint / debian a while ago but never had this kind of problem. …
Thank you Nachlese, I see, I ll try cleaning up the AUR mess… somehow… I basically install Bitwig-Studio and Mega and Mullvad via AUR as I use it daily , but seems it gives me more trouble that i can handle
I know for a fact that mullvad, which is in the AUR,
which does not require you to add an additional external repository (like Mega),
is not a problem at all.
The external repository is what gave you problems (which are relatively easily solvable - I think - it’s just outdated pgp keys).
Thanks Nachlese, so it is Mega, which I commented out in the pacman.conf after that got recommended to me, that gave me the trouble, right? As you recommended I installed dbus (didnt work in pamac but then via the command line sudo pacman -S dbus ) and removed dbus-x11.
I also needed to remove lib32-db to start the system update, now fingers crossed…
The Announcement is the Instruction Manual, if you will, and contains what is new, what has changed, and if action is required. The Announcement’s second post gets updated if something is discovered by users during their update or after their update that is the direct result of the update.
In the Announcement, expand the bullet arrow to the left of the text and it shows what may need to be done. Sometimes there is some wiggle room for the user to take a particular action based on their needs. After reviewing the bullet issues, I would either scroll through the Topic or do a find to get some more details. If you type ctrl-f once, the forum’s software captures the keystroke and you use the forum’s find textbox. If you type it twice, the keystroke is passed to your browser and you use your browser’s find. Most often the course of action is simply to uninstall. In some cases, you might be prompted during the install.
I clipped the expanded text from the Stable Update Announcements for the sake of this conversation:
Just to clarify, software, known as packages (skipping: flatpak, snaps, appimage), are not demoted or dropped to the AUR. The package is removed from the Manjaro supported repositories. It is an important distinction. The package, may or may not be in the AUR.
The AUR is not Manjaro supported. Although, the Manjaro community may help.
You are in the right Category to ask questions. A couple of suggestions:
Browse and search this forum. The forum software is called Discourse.
super helpful information here , the terminology with packages etc. was not clear to me so this now makes it all more understandable! I will read up and will wrap my head around. If I would have known in the beginning that my problem is caused by packages installed from AUR I would have posted it to the AUR category. now it seems my system is responsive and I am just running the updates , lets see how it goes!
