Apport hook should detect fglrx/nvidia

Bug #516264 reported by Mario Limonciello
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
Fix Released
Wishlist
Bryce Harrington

Bug Description

Version: 2:1.7.3.902-1ubuntu9

The xorg-server apport hook should detect situations that the user has 'fglrx' or one of the 'nvidia' modules loaded into the system. When these situations arise, the package should be adjusted to fglrx-installer or the appropriate nvidia source package accordingly. This will prevent triagers from having to sift through bugs that might have been caused by proprietary drivers and reassign packages when they can be spending their time on open source driver bugs.

Related branches

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

also the ones which have "innotek GmbH VirtualBox" as MachineType should be filed against virtualbox-ose.

Changed in xorg-server (Ubuntu):
importance: Undecided → Medium
status: New → Confirmed
Bryce Harrington (bryce)
Changed in xorg-server (Ubuntu):
assignee: nobody → Bryce Harrington (bryceharrington)
Bryce Harrington (bryce)
affects: xorg-server (Ubuntu) → xorg (Ubuntu)
Changed in xorg (Ubuntu):
importance: Medium → Wishlist
status: Confirmed → Triaged
summary: - Xorg-server apport hook should detect fglrx/nvidia
+ Apport hook should detect fglrx/nvidia
Revision history for this message
Bryce Harrington (bryce) wrote :

Mario, could you do me a favor and run `ubuntu-bug xorg` on a Lucid system with nvidia or fglrx installed? I have added apport commands to include make.log and dkms status but have not yet confirmed that they actually get collected. Can you verify this?

Revision history for this message
Mario Limonciello (superm1) wrote :

Bryce:

those two bits shouldn't be necessary. DKMS in Lucid introduced support to file a bug against the source package if it happened to fail to build.

See http://linux.dell.com/git/?p=dkms.git;a=blob;f=dkms_apport.py;h=f308ea94e0166fa6b3955fa99507014c54abb40f;hb=HEAD

and report_build_problem() in the dkms script for more information.

Revision history for this message
Bryce Harrington (bryce) wrote : Re: [Bug 516264] Re: Apport hook should detect fglrx/nvidia

On Sat, Feb 13, 2010 at 03:15:33AM -0000, Mario Limonciello wrote:
> Bryce:
>
> those two bits shouldn't be necessary. DKMS in Lucid introduced support
> to file a bug against the source package if it happened to fail to
> build.
>
> See
> http://linux.dell.com/git/?p=dkms.git;a=blob;f=dkms_apport.py;h=f308ea94e0166fa6b3955fa99507014c54abb40f;hb=HEAD
>
> and report_build_problem() in the dkms script for more information.

Ah okay, is this all hooked up in Lucid? Have there been any bugs
reported using this functionality? Or is there anything further we need
to do to get this hooked up?

Revision history for this message
Mario Limonciello (superm1) wrote :

Yeah I've seen some bugs come in about build failures, so it is working. So that piece of it you can ignore with this apport hook to detect nvidia/fglrx. Just so long as the regular X hook is able to change the source package to fglrx/nvidia and collect the regular stuff.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package xorg - 1:7.5+1ubuntu9

---------------
xorg (1:7.5+1ubuntu9) lucid; urgency=low

  [ Bryce Harrington ]
  * debian/x11-common.links:
    + Update links for renamed packages
    + Add apport hook for nvidia-graphics-drivers
    + Add apport hook for -vmmouse (LP: #517664)
    + Remove apport hooks for packages now removed from repository
  * debian/apport/source_xorg.py:
    + Add tagging of release codename
    + Collect gdm logs as root
    + Remove extraneous checking of $DISPLAY
    + Detect vbox, fglrx, and nvidia and file bugs against the respective
      packages instead.
      (LP: #516264)

  [ Timo Aaltonen ]
  * debian/x11-common.links: Add xf86-input-evtouch and -wacom.
 -- Bryce Harrington <email address hidden> Tue, 23 Feb 2010 18:45:03 -0800

Changed in xorg (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.