Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#1227 - glibc2.3.3 kills nvidia driver
Attached to Project:
Arch Linux
Opened by galen thurber (galen2) - Thursday, 05 August 2004, 03:15 GMT
Opened by galen thurber (galen2) - Thursday, 05 August 2004, 03:15 GMT
|
Detailsafter upgrading to glibc2.3.3
all screens fail including vc/1 vc/2 etc when startx is activated. No X, kernel errors reported just a blank screen requiring soft reboot must resort XF86config to using Driver "nv" |
This task depends upon
Closed by Jan de Groot (JGC)
Monday, 24 January 2005, 23:51 GMT
Reason for closing: Not a bug
Additional comments about closing: We're at glibc 2.3.4 now ;)
Monday, 24 January 2005, 23:51 GMT
Reason for closing: Not a bug
Additional comments about closing: We're at glibc 2.3.4 now ;)
else try rebuilding the module by pacman -S nvidia if you use staging repo or rerun the nvidia-installer
arrogant to assume.
2nd rebuild of nvidia 5336 using .run works so far until some other update breaks it.
No reason not to inform users of update requiresment that breaks their system.
I am not saying that it's unreasonable to expect a message, but I am saying that your accusative tone isn't appreciated.
If you expect a product that will work and won't break on you, then maybe you should start paying for it. That way you'd be allowed to complain because of the promise of support.
Instead you're just complaining to a bunch of people, who are busy enough as it is, about things that you could have searched for to find. Until Arch becomes a fully-staffed, well-managed distro, you will run into errors of this nature. If you don't do a little bit of research and just point fingers and say stuff is wrong, then people won't feel obligated to help you.
peace
How do you propose that this "problem" be addressed? Should we release another glibc package and force people to download another 15 meg package, just so they can get a message? Or should we point people to resources where they can find the directions themselves (like the thread you posted this bug link in)? Or should we make an official announcement and then point all the people to it who don't read official announcements?
I'm not implying that everyone should have to pay for support, but I'm saying that we (the developers) don't have an infinite amount of resources to help/solve all people/problems. People who are nonaccusational and willing to help address the problem are more likely to be helped than people who demand things be fixed.
My gripe with linux users is they expect everything to be handed to them and aren't willing to approach issues on an equal footing. The more people who come to the table willing to look at the problem instead of making over-reaching negative statements, the better.
Including the announcements in pacman itself seems like a wise option.
Equal footing can only be defined from an impartial honest viewpoint. I do not treat users as serving my works, I serve their needs.
PS You sound burned-out