Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 192773 - Via driver fails to load
Via driver fails to load
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-via (Show other bugs)
All Linux
medium Severity high
: ---
: ---
Assigned To: Adam Jackson
Depends On:
  Show dependency treegraph
Reported: 2006-05-22 17:04 EDT by paul
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-09-21 18:40:48 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description paul 2006-05-22 17:04:32 EDT
Description of problem:
Via driver fails to load with 

X: symbol lookup error: /usr/lib/xorg/modules/drivers/via_drv.so: undefined
symbol: assert

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Attempt to start X server configured to use "via" driver
Actual results:

Expected results:

Additional info:

Problem is in via_dri.c which has two assert()s in VIADRIFinishScreenInit but no
#include of <assert.h>
Comment 1 Mike A. Harris 2006-05-23 09:50:22 EDT
Please report this issue to X.Org developers by filing a bug report in
the X.Org bugzilla located at http://bugs.freedesktop.org in the "xorg"

Once you've filed your bug report to X.Org, if you paste the new
bug URL here, Red Hat will continue to track the issue in the
centralized X.Org bug tracker, and will review any bug fixes that
become available for consideration in future updates.

Setting status to "NEEDINFO_REPORTER", awaiting X.Org bug URL
for tracking.
Comment 2 paul 2006-05-23 15:11:01 EDT
Done, URL is https://bugs.freedesktop.org/show_bug.cgi?id=7010
Comment 3 Adam Jackson 2006-09-21 18:40:48 EDT
Fixed in xorg-x11-drv-via 0.2.1-5.

Note You need to log in before you can comment on or make changes to this bug.