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!
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!
FS#1884 - gnome-keyboard-properties stopped working
Attached to Project:
Arch Linux
Opened by Tor Krill (tor) - Friday, 10 December 2004, 07:17 GMT
Last edited by Tobias Powalowski (tpowa) - Friday, 10 December 2004, 08:35 GMT
Opened by Tor Krill (tor) - Friday, 10 December 2004, 07:17 GMT
Last edited by Tobias Powalowski (tpowa) - Friday, 10 December 2004, 08:35 GMT
|
DetailsAfter upgrading glibc a while back, gnome-keyboard-properties stopped working.
When starting it on the commandline it says: *** glibc detected *** free(): invalid pointer: 0xb74ba9a0 *** And then hangs. |
This task depends upon
Closed by Jan de Groot (JGC)
Friday, 10 December 2004, 15:49 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed this bug in libxklavier, which had an invalid free().
Friday, 10 December 2004, 15:49 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed this bug in libxklavier, which had an invalid free().
I have a load "dri" but no dri _section_.
eugenia from osnews told me that it makes no difference if you have a dri section or not
I have downgraded glibc and that solves my problems.
So, here's why it happens, and how to get around it:
"Recent linux systems have a version of glibc which aborts when dodgy code throws up an error. This is to prevent data corruption, memory leaks, etc.
You have two options until this bug is addressed -- downgrade to an earlier version of glibc, or set MALLOC_CHECK_ to 0 or 1. e.g.:
export MALLOC_CHECK_=1
"
That's the upstream bugreport. It seems to be a bug in libxklavier.