Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 158442 - x11-drivers/xf86-input-evdev-1.1.5 uses undefined function xf86OSRingBell (and crashes x11)
Summary: x11-drivers/xf86-input-evdev-1.1.5 uses undefined function xf86OSRingBell (an...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: AMD64 Other
: High normal (vote)
Assignee: Gentoo X packagers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-12-18 03:01 UTC by Waldo
Modified: 2006-12-19 12:30 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Waldo 2006-12-18 03:01:00 UTC
As described in bug 154075 - doing an operation in the terminal that uses the bell (ie, backspacing beyond prompt) crashes x11 dead.  This was a problem in 1.14, requiring a patch 1.1.4-r1.

Emerging xf86-input-evdev-1.15 shows the following:

evdev_key.c: In function 'EvdevKbdBell':
evdev_key.c:245: warning: implicit declaration of function 'xf86OSRingBell'

Apparently the upstream patch described in bug 154075 didn't make it to 1.l.5.

W
Comment 1 Marien Zwart (RETIRED) gentoo-dev 2006-12-18 21:04:59 UTC
Diffing the tarball contents indicates the only changes were to the build system. Applying the patch from bug 154075 should still work (patch should still apply and should still fix this) but I haven't tried it yet :)
Comment 2 Silvence 2006-12-19 01:36:19 UTC
I've applied the patch with the 1.1.5 ebuild. So far, so good. =)
Comment 3 Simon Cooper 2006-12-19 07:51:00 UTC
I have the same problem on x86 - evdev-1.1.5 crashes the x server with the system bell. Interestingly, I didn't have the same problem with 1.1.4...

On a side note, how can I tweak the ebuild to apply the given patch? there isnt an src_unpack()...
Comment 4 Joshua Baergen (RETIRED) gentoo-dev 2006-12-19 12:30:21 UTC
Sorry about that guys.  Somehow I thought the problem had been fixed in 1.1.5.

Patch re-added in 1.1.5-r1.