Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#57030 - [json-c] error loading shared libraries

Attached to Project: Arch Linux
Opened by Antonino Cangialosi (fanofactor) - Tuesday, 09 January 2018, 20:14 GMT
Last edited by Eli Schwartz (eschwartz) - Thursday, 18 January 2018, 15:29 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: when I update to version 0.13-1, I have many problems with gnome. Firefox stop working and every tab crashes, when logging off after putting the password of my user, the log in screen splashes back to the begining, and when rebooting the system it does not even manage to load the login screen, getting stuck soon after the boot phase. Luckily, on tty2 without the gnome gui I managed to downgrade it to version 0.12.1-1


Additional info:
* package version(s) 0.13-1
* config and/or log files etc.


Steps to reproduce: upgrade to 0.13-1

This task depends upon

Closed by  Eli Schwartz (eschwartz)
Thursday, 18 January 2018, 15:29 GMT
Reason for closing:  Not a bug
Additional comments about closing:  Outdated AUR package that replaced pulseaudio had not been rebuilt as it was supposed to be.)
Comment by Doug Newgard (Scimmia) - Tuesday, 09 January 2018, 20:18 GMT
Sounds like a partial update. Did you update everything and rebuild anything from outside the repos that would need it?
Comment by Antonino Cangialosi (fanofactor) - Tuesday, 09 January 2018, 20:29 GMT
It first came upgrading the system, so I had no clue it was this specific package. By trial and error, it was only when this package was the only one downgraded and the system was running again that I identied it as the source of the problem.




Comment by Doug Newgard (Scimmia) - Tuesday, 09 January 2018, 20:36 GMT
None of which answers my questions.
Comment by Antonino Cangialosi (fanofactor) - Tuesday, 09 January 2018, 20:48 GMT
I am sorry. Could you rephrase and separate the questions? I am a rookie, but I want to help for what I am able to...
Comment by Doug Newgard (Scimmia) - Tuesday, 09 January 2018, 21:49 GMT
Was the ENTIRE system updated, nothing held back?

Was anything you have installed from outside the repos rebuilt if it needed to be? This would include anything in /usr/local/, any packages installed from the AUR, etc.

I'll add a 3rd question: Is this vanilla Arch or a derivative?
Comment by Antonino Cangialosi (fanofactor) - Tuesday, 09 January 2018, 22:19 GMT
1) I initially upgraded the entire system, yes. But the trouble is when upgrading this single package. Indeed, I upgragred every other then this package now.
2) Nothing installed outside the repo needed to be rebuilt.
3) it is vanilla Arch.
Comment by loqs (loqs) - Tuesday, 09 January 2018, 22:31 GMT
Are there any coredumps from when json-c was installed? So you have reviewed everything you have installed from outside the repo and verified there are no executables linked against the old json-c?
Comment by Jan de Groot (JGC) - Wednesday, 10 January 2018, 09:01 GMT
Probably fixed by these two commits (1st is important one with the fix, 2nd is recommended also).

https://github.com/json-c/json-c/commit/9aca3b6a087a396a81d7e26f4557eb97fecc1386
https://github.com/json-c/json-c/commit/c233f5c05e92909a764973524a03471bfad78f09
Comment by Antonino Cangialosi (fanofactor) - Thursday, 11 January 2018, 21:07 GMT
@loqs please, forgive my ineptitude. how can I provided you with the coredumps? and I don't understand the second question either, sorry. Could you please explain it? (sorry for the delayed answer)
Comment by loqs (loqs) - Thursday, 11 January 2018, 21:22 GMT
https://wiki.archlinux.org/index.php/Core_dump#Examining_a_core_dump if something crashes it should unless the system has been configured otherwise
produce a coredump the backtrace from which may provide insight into the issue.
Also could you rebuild json-c with the 2 patches JCG linked and see if the issue still occurs.
With the second question I was asking you to go through every executable not installed from the arch repositories and see if was linked against /usr/lib/libjson-c.so.2
but please try rebuilding json-c with the patches first and test that as it is probably simpler.
Comment by Antonino Cangialosi (fanofactor) - Thursday, 18 January 2018, 14:20 GMT
ok, I had a (probably unrelated) problem with my hard drive...

I tried the two patches and it did not worked. I tried to give coredumpctl list to receive:

coredumpctl: error while loading shared libraries: libjson-c.so.2: cannot open shared object file: No such file or directory

Then, downgraded to json-c 0.12 brought things back to a stable state...
The executables not from repo linked against libjson-c.so.2 are:
libjson-c.so.2 => /usr/lib/libjson-c.so.2 (0x00007f3586953000)
/usr/bin/pacat
libjson-c.so.2 => /usr/lib/libjson-c.so.2 (0x00007fa44e7f1000)
/usr/bin/pactl
libjson-c.so.2 => /usr/lib/libjson-c.so.2 (0x00007
/usr/bin/pamon
libjson-c.so.2 => /usr/lib/libjson-c.so.2 (0x00007
/usr/bin/paplay
libjson-c.so.2 => /usr/lib/libjson-c.so.2 (0x00007
/usr/bin/parec
libjson-c.so.2 => /usr/lib/libjson-c.so.2 (0x00007
/usr/bin/parecord
libjson-c.so.2 => /usr/lib/libjson-c.so.2 (0x00007
/usr/bin/pacmd
libjson-c.so.2 => /usr/lib/libjson-c.so.2 (0x00007
/usr/bin/pasuspender
libjson-c.so.2 => /usr/lib/libjson-c.so.2 (0x00007
/usr/bin/pax11publish
libjson-c.so.2 => /usr/lib/libjson-c.so.2 (0x00007
/usr/bin/pulseaudio
Comment by Antonino Cangialosi (fanofactor) - Thursday, 18 January 2018, 15:23 GMT
ok, solved. It was a package from AUR...

Loading...