[SOLVED] Unable to start pamac after recent update.

ZeroCC · 2018-05-28 23:33:35

pamac fails thus

>> pamac-manager
Error: Error calling StartServiceByName for org.manjaro.pamac.user: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.manjaro.pamac.user exited with status 127

** (pamac-manager:5724): CRITICAL **: 00:26:51.519: pamac_user_daemon_get_lockfile: assertion 'self != NULL' failed

(pamac-manager:5724): GLib-GIO-CRITICAL **: 00:26:51.519: g_file_new_for_path: assertion 'path != NULL' failed

** (pamac-manager:5724): CRITICAL **: 00:26:51.544: pamac_user_daemon_get_repos_names: assertion 'self != NULL' failed
Segmentation fault (core dumped)

This was directly after an upgrade to Pamac...

Last edited by ZeroCC (2018-05-29 10:17:39)

circleface · 2018-05-28 23:37:29

Are you running Arch or Manjaro?

ZeroCC · 2018-05-28 23:53:04

Arch. I believe the Manjaro reference is about Pamac's origins...

Alad · 2018-05-28 23:54:03

Needs to be updated to work with pacman 5.1.

ZeroCC · 2018-05-28 23:58:55

pacman is currently 5.1.0-1
pamac-aur is at 6.3.2-1

ZeroCC · 2018-05-29 00:03:53

Ah - silly me: it was pacman that was updated....

ZeroCC · 2018-05-29 00:31:30

FYI: I have downgraded pacman until pamac is sorted out. All is well again

Last edited by ZeroCC (2018-05-29 00:31:48)

jasonwryan · 2018-05-29 00:32:50

ZeroCC wrote:

FYI: I have downgraded pacman until pamac is sorted out. All is well again

So much wrongness...

ZeroCC · 2018-05-29 00:35:25

I'm just baaaad....

Alad · 2018-05-29 00:41:57

Anything that links against pacman is now broken on your system, all because of some poorly made package manager for a different distribution.

Kewl · 2018-05-29 06:51:57

Bad choice @ZeroCC: You should rather uninstall pamac until it is fixed and consider another GUI/helper at least temporarily, if not permanently.

Last edited by Kewl (2018-05-29 07:10:58)

ZeroCC · 2018-05-29 07:37:50

It was a choice made before bedtime. Now I'm awake and considering the possibilities.

ZeroCC · 2018-05-29 07:44:56

And... oh, look: there's the update for pamac-aur.....

ee · 2018-05-31 22:47:18

jasonwryan wrote:

ZeroCC wrote:
FYI: I have downgraded pacman until pamac is sorted out. All is well again

So much wrongness...

What specifically was wrong about this approach? I'm trying to learn.

Edit: I found this thread because I came across this issue while trying to update my system today. I did not downgrade pacman, I manually updated package-query then manually updated pamac.

Last edited by ee (2018-05-31 22:53:17)

ee · 2018-05-31 22:50:37

Alad wrote:

Anything that links against pacman is now broken on your system, all because of some poorly made package manager for a different distribution.

Please bear with me, I'm trying to understand and learn. Why do you say that pamac is a poorly made package manager, I installed many of the ones listed in the wiki on a test system a while ago and found pamac to be the most useful and friendly. I don't see anything bad about it, so what if it was originally developed for Manjaro, isn't that the nature of linux itself? Wasn't the base of everything that makes arch linux developed for other distributions?

Alad · 2018-06-01 14:21:11

It has a history of running partial upgrades which are unsupported.

mrunion · 2018-06-01 18:52:43

ee wrote:

Wasn't the base of everything that makes arch linux developed for other distributions?

If I understand your question, the answer is "no". Pacman was developed for Arch, not other distributions. Arch does pull from other open source project -- like the Kernel, etc. But Arch is not a "copied and modified" version of another Linux distribution.

Last edited by mrunion (2018-06-01 18:52:55)

loqs · 2018-06-01 19:23:49

ee wrote:

jasonwryan wrote:
ZeroCC wrote:
FYI: I have downgraded pacman until pamac is sorted out. All is well again

So much wrongness...
What specifically was wrong about this approach? I'm trying to learn.

The downgrade would be an unsupported partial upgrade.

ee wrote:

Edit: I found this thread because I came across this issue while trying to update my system today. I did not downgrade pacman, I manually updated package-query then manually updated pamac.

Which does not have that same issue as the approach taken by ZeroCC.

ee wrote:

I don't see anything bad about it, so what if it was originally developed for Manjaro, isn't that the nature of linux itself? Wasn't the base of everything that makes arch linux developed for other distributions?

Arch officially supports the pacman package manager and no AUR helpers. Nothing is done to prevent you from using those packages but support will not be provided.

eschwartz · 2018-06-01 19:55:50

ee wrote:

Alad wrote:
Anything that links against pacman is now broken on your system, all because of some poorly made package manager for a different distribution.
Please bear with me, I'm trying to understand and learn. Why do you say that pamac is a poorly made package manager, I installed many of the ones listed in the wiki on a test system a while ago and found pamac to be the most useful and friendly. I don't see anything bad about it, so what if it was originally developed for Manjaro, isn't that the nature of linux itself? Wasn't the base of everything that makes arch linux developed for other distributions?

pacman works fine on Windows, where it powers MSYS2 (like Cygwin, except with pacman!), and it's also been used on macOS and BSD. Any of these groups might support partial upgrades, as pacman itself does, even though *Arch Linux* does not.

Manjaro is a poorly developed distro which which does inadvisable things, and is often confused for Arch Linux. So too, Pamac which is designed for Manjaro, does inadvisable things on Arch Linux systems.

If you're trying to say "but linux, gimme muh open source" to justify some program which this community has determined is inadvisable on Arch Linux... then you're missing the point.

It was developed for Manjaro, not for Arch, and it was developed to fit in with the mindset of Manjaro, which we feel conflicts with good practices on Arch. Therefore it itself is bad from the perspective of Arch.

Arch Linux

#1 2018-05-28 23:33:35

[SOLVED] Unable to start pamac after recent update.

#2 2018-05-28 23:37:29

Re: [SOLVED] Unable to start pamac after recent update.

#3 2018-05-28 23:53:04

Re: [SOLVED] Unable to start pamac after recent update.

#4 2018-05-28 23:54:03

Re: [SOLVED] Unable to start pamac after recent update.

#5 2018-05-28 23:58:55

Re: [SOLVED] Unable to start pamac after recent update.

#6 2018-05-29 00:03:53

Re: [SOLVED] Unable to start pamac after recent update.

#7 2018-05-29 00:31:30

Re: [SOLVED] Unable to start pamac after recent update.

#8 2018-05-29 00:32:50

Re: [SOLVED] Unable to start pamac after recent update.

#9 2018-05-29 00:35:25

Re: [SOLVED] Unable to start pamac after recent update.

#10 2018-05-29 00:41:57

Re: [SOLVED] Unable to start pamac after recent update.

#11 2018-05-29 06:51:57

Re: [SOLVED] Unable to start pamac after recent update.

#12 2018-05-29 07:37:50

Re: [SOLVED] Unable to start pamac after recent update.

#13 2018-05-29 07:44:56

Re: [SOLVED] Unable to start pamac after recent update.

#14 2018-05-31 22:47:18

Re: [SOLVED] Unable to start pamac after recent update.

#15 2018-05-31 22:50:37

Re: [SOLVED] Unable to start pamac after recent update.

#16 2018-06-01 14:21:11

Re: [SOLVED] Unable to start pamac after recent update.

#17 2018-06-01 18:52:43

Re: [SOLVED] Unable to start pamac after recent update.

#18 2018-06-01 19:23:49

Re: [SOLVED] Unable to start pamac after recent update.

#19 2018-06-01 19:55:50

Re: [SOLVED] Unable to start pamac after recent update.

Board footer