You are not logged in.

#1 2018-06-22 04:53:17

gxt25
Member
Registered: 2017-07-05
Posts: 44

munmap_chunk(): invalid pointer after pacman -Syu

Greetings,

After an otherwise apparently successful

pacman -Syu | tee ~HOME/Documents/pacman-2018-06-22.txt

I got

munmap_chunk(): invalid pointer

. Pacman log is:

[2018-06-22 00:28] [PACMAN] Running 'pacman -Syu'
[2018-06-22 00:28] [PACMAN] synchronizing package lists
[2018-06-22 00:28] [PACMAN] starting full system upgrade
[2018-06-22 00:29] [ALPM] transaction started
[2018-06-22 00:29] [ALPM] upgraded attr (2.4.47-3 -> 2.4.48-1)
[2018-06-22 00:29] [ALPM] upgraded acl (2.2.52-4 -> 2.2.53-1)
[2018-06-22 00:29] [ALPM] upgraded lame (3.100-1 -> 3.100-2)
[2018-06-22 00:29] [ALPM] upgraded libogg (1.3.3-2 -> 1.3.3-3)
[2018-06-22 00:29] [ALPM] upgraded libpulse (11.1-1 -> 12.0-1)
[2018-06-22 00:29] [ALPM] upgraded qutebrowser (1.3.2-1 -> 1.3.3-1)
[2018-06-22 00:29] [ALPM] transaction completed
[2018-06-22 00:29] [ALPM] running 'gtk-update-icon-cache.hook'...
[2018-06-22 00:29] [ALPM] running 'systemd-update.hook'...
[2018-06-22 00:29] [ALPM] running 'update-desktop-database.hook'...

I don't know which program spit out that error or if it is significant at all. The error was on a line by itself with no other text or references. Here is the tee:

:: Synchronizing package databases...
downloading core.db...
downloading extra.db...
downloading community.db...
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...

Packages (6) acl-2.2.53-1  attr-2.4.48-1  lame-3.100-2  libogg-1.3.3-3  libpulse-12.0-1  qutebrowser-1.3.3-1

Total Download Size:    2.93 MiB
Total Installed Size:  10.23 MiB
Net Upgrade Size:       0.13 MiB

:: Retrieving packages...
downloading attr-2.4.48-1-x86_64.pkg.tar.xz...
downloading acl-2.2.53-1-x86_64.pkg.tar.xz...
downloading lame-3.100-2-x86_64.pkg.tar.xz...
downloading libogg-1.3.3-3-x86_64.pkg.tar.xz...
downloading libpulse-12.0-1-x86_64.pkg.tar.xz...
downloading qutebrowser-1.3.3-1-any.pkg.tar.xz...
checking keyring...
checking package integrity...
loading package files...
checking for file conflicts...
checking available disk space...
:: Processing package changes...
upgrading attr...
upgrading acl...
upgrading lame...
upgrading libogg...
upgrading libpulse...
upgrading qutebrowser...
:: Running post-transaction hooks...
(1/3) Updating icon theme caches...
(2/3) Arming ConditionNeedsUpdate...
(3/3) Updating the desktop file MIME type cache...

and it was right below the 3/3 line where it appeared. A Pacman error? Google results seem to imply a c error within a program but in the search results I found this error usually indicated which program was spitting out the error. Any pointers on how to trouble shoot this?  Or if I have to at all - so far everything otherwise seems to behaving as expected?


a man a plan a canal panama

Offline

#2 2018-06-22 06:38:21

eschwartz
Fellow
Registered: 2014-08-08
Posts: 4,097

Re: munmap_chunk(): invalid pointer after pacman -Syu

This is an error appearing right after a pacman hook is being run. You could check the hook files in the referenced directory, until you find the message text in /usr/share/libalpm/hooks/update-desktop-database.hook

This hook runs the update-desktop-database command -- does it error out if you run it again?


Managing AUR repos The Right Way -- aurpublish (now a standalone tool)

Offline

#3 2018-06-22 12:22:07

gxt25
Member
Registered: 2017-07-05
Posts: 44

Re: munmap_chunk(): invalid pointer after pacman -Syu

Thank you for the hooks pointer. Running another pacman -Syu did not produce the error message, but the update-desktop-database hook was not called this time, so perhaps I will have to wait until a package is updated which triggers this hook to see if the error is repeated(?).

Last edited by gxt25 (2018-06-22 12:22:31)


a man a plan a canal panama

Offline

Board footer

Powered by FluxBB