Bug 27832 - Early versions of libudev cause crash
Summary: Early versions of libudev cause crash
Status: RESOLVED INVALID
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/nouveau (show other bugs)
Version: git
Hardware: x86-64 (AMD64) Linux (All)
: medium critical
Assignee: Nouveau Project
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-25 15:14 UTC by Bob Gleitsmann
Modified: 2013-08-18 18:09 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
Patch to configure.ac to check libudev version >= 142 (487 bytes, patch)
2010-04-25 15:14 UTC, Bob Gleitsmann 		no flags Details | Splinter Review
View All

Description Bob Gleitsmann 2010-04-25 15:14:28 UTC 
Created attachment 35286 [details] [review]
Patch to configure.ac to check libudev version >= 142

It appears that at least version 142 of udev is required to properly support the recently added uevent code. Haven't tested with 142 because I don't want to mess up my distro Fedora 11. This only has 141. However, everything is usable if the driver thinks you don't have udev at all. Hence the attached patch.

Best Wishes,

Bob Gleitsmann
Comment 1 Ilia Mirkin 2013-08-18 18:09:34 UTC 
It appears that this bug report has laid dormant for quite a while. Sorry we haven't gotten to it. Since we fix bugs all the time, chances are pretty good that your issue has been fixed with the latest software. Please give it a shot. (Linux kernel 3.10.7, xf86-video-nouveau 1.0.9, mesa 9.1.6, or their git versions.) If upgrading to the latest isn't an option for you, your distro's bugzilla is probably the right destination for your bug report.

In an effort to clean up our bug list, we're pre-emptively closing all bugs that haven't seen updates since 2011. If the original issue remains, please make sure to provide fresh info, see http://nouveau.freedesktop.org/wiki/Bugs/ for what we need to see, and re-open this one.

Thanks,

The Nouveau Team

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.