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#1727 - libxklavier 1.10 causes gnome session daemon to stop working

Attached to Project: Arch Linux
Opened by William DeMoss II (wdemoss) - Wednesday, 03 November 2004, 20:24 GMT
Last edited by arjan timmerman (blaasvis) - Wednesday, 03 November 2004, 22:33 GMT
Task Type Bug Report
Category System
Status Closed
Assigned To arjan timmerman (blaasvis)
Architecture not specified
Severity High
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

After recent pacman -Syu, my gnome session daemon stopped working. After trying to revert version of each one at a time, I dertermined that everything worked fine if I backed out libxklavier to version 1.03. Not sure what else information I can supply, let me know for any configurations that could help.
This task depends upon

Closed by  arjan timmerman (blaasvis)
Friday, 05 November 2004, 10:23 GMT
Reason for closing:  Fixed
Comment by William DeMoss II (wdemoss) - Wednesday, 03 November 2004, 20:39 GMT
it appears that 1.04 is intended to be distributed with gnome 2.8.1. looking at libxklavier home page, 1.10 is intended to be used with gnome 2.9.
Comment by arjan timmerman (blaasvis) - Wednesday, 03 November 2004, 21:24 GMT
well i can't reverse it now.
so i baked up a patch, it is only a minor change in the api. almost done ;)
need to test it.
Comment by William DeMoss II (wdemoss) - Wednesday, 03 November 2004, 21:33 GMT
would be happy to help test it, if you email me the patch and package build, or provide access to the pkg over ftp or something.
Comment by arjan timmerman (blaasvis) - Wednesday, 03 November 2004, 22:29 GMT
well i couldn't get it to work, i have decided to reverse to 1.04 instead of 1.10
Comment by Gary Singleton (gsinglet) - Friday, 05 November 2004, 09:44 GMT
Is this bug fixed? It seems to be working for me now and I have version 1.04-1 installed which leads me to believe that reverting to 1.04 fixed everything. Thanks.
Comment by arjan timmerman (blaasvis) - Friday, 05 November 2004, 10:23 GMT
well i left it open for feedback ;)
thx for telling me everything is fine again.
closing it up

Loading...