Hi, thanks for reporting this bug.
added the committers

Keywords: (none) => Junior_job
CC: (none) => anssi.hannula, doktor5000
Summary: 2_alpha1: fglrx.ko dangling link => fglrx.ko dangling link
Source RPM: (none) => fglrx

assigning to maintainer

CC: (none) => marja11
Assignee: bugsquad => anssi.hannula

Trying to ping 41 bug reports in one move, because nothing has happened with them for more than 3 months, they still have the status NEW or REOPENED, there is no "OK" on the Whiteboard and severity and priority are "normal" or higher.

Is this one still valid for Mageia 2 rc?

If it is and you're the assignee, please set status to ASSIGNED if you think this bug was assigned correctly. If for work flow reasons you can't do that, then please put OK on the whiteboard instead.
If it wasn't assigned correctly, please assign back to Bug Squad and explain.

(In reply to comment #3)

> Is this one still valid for Mageia 2 rc?

Other than link change, it shows up after a clean Mageia-2-rc-x86_64-DVD.iso + updates + fglrx + urpme --auto-orphans 

#  symlinks -r / | grep dangling "snippet"

dangling: /var/lib/dkms/fglrx/8.961-1.mga2.nonfree/build/fglrx.ko -> 2.6.x/fglrx.ko

Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

(In reply to comment #5)


> Please report whether this bug is still valid for Mageia 2.


dangling: /var/lib/dkms/fglrx/8.961-1.mga2.nonfree/build/fglrx.ko -> 2.6.x/fglrx.ko

still valid.

Please look at the bottom of this mail to see whether you're the assignee of this  bug, if you don't already know whether you are.


If you're the assignee:

We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead.

If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard.

Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why.

Thanks :)

**************************** 

@ the reporter and persons in the cc of this bug:

If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us.

@ the reporter of this bug

If you didn't reply yet to a request for more information, please do so within two weeks from now.

Thanks all :-D

Is this bug still valid? Its rather old

CC: (none) => micheelsen

(In reply to comment #8)
> Is this bug still valid? Its rather old

# symlinks -r / | grep fglrx.ko
dangling: /var/lib/dkms/fglrx/9.012-1.mga3.nonfree/build/fglrx.ko -> 2.6.x/fglrx.ko

# uname -r
3.8.0-desktop-1.mga3

Sorry to be asking again, but since nothing happened in a long time, I have to: is this still valid?

Keywords: (none) => NEEDINFO

(In reply to Samuel VERSCHELDE from comment #10)
> Sorry to be asking again, but since nothing happened in a long time, I have
> to: is this still valid?

Yep, I see the fglrx.ko dangling link on every new kernel install.
Snippets from my automated install scripts;
# grep fglrx.ko  *
dangling_auditor.rpt:5_b3: fglrx.ko dangling link
dangling_auditor.rpt:/var/lib/dkms/fglrx/14.501.1003-3.mga5.nonfree/build/fglrx.ko 
install_changes_script.log:working /var/lib/dkms/fglrx/14.501.1003-3.mga5.nonfree/build/fglrx.ko
_install_rpt.rpt:dangling: /var/lib/dkms/fglrx/14.501.1003-3.mga5.nonfree/build/fglrx.ko -> 2.6.x/fglrx.ko

Just verifying if bug report is still valid.

$ grep fglrx.ko  *5_new_install.rpt
mtv_official_5_new_install.rpt:dangling: /var/lib/dkms/fglrx/14.501.1003-3.mga5.nonfree/build/fglrx.ko -> 2.6.x/fglrx.ko

Whiteboard: MGA3TOO => MGA3TOO MGA4TOO MGA5TOO

closing bug

Status: NEW => RESOLVED
Resolution: (none) => OLD