Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Users Search
Help Dashboard Sign In Sign Up
Q&A Meta
Q&A
Posts Tags Edits
Ask Question

Comments on After update, OpenGL does not work until reboot

Post

After update, OpenGL does not work until reboot

+1
−0

Whenever I do a big system update, OpenGL stops working until the next reboot. This also prevent OpenGL apps from launching. Example:

$ glxgears 
X Error of failed request:  BadValue (integer parameter out of range for operation)
  Major opcode of failed request:  151 (GLX)
  Minor opcode of failed request:  3 (X_GLXCreateContext)
  Value in failed request:  0x0
  Serial number of failed request:  28
  Current serial number in output stream:  29

This goes away when I reboot. How can I make it go away without rebooting?

arch-linux updates opengl
posted over 1 year ago
user card
matthewsnyder‭
1806 reputation 122 75 285 109
History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

1 comment thread

Can you pinpoint exactly what you updated? You might (might) be able to `rmmod` and then `modprobe` t... (3 comments)
Can you pinpoint exactly what you updated? You might (might) be able to `rmmod` and then `modprobe` t...
terdon‭ wrote over 1 year ago
copy link

Can you pinpoint exactly what you updated? You might (might) be able to rmmod and then modprobe the relevant kernel module, but the details will depend on exactly what needs to be done.

matthewsnyder‭ wrote over 1 year ago
copy link

Hmm. I assumed there was just a single obvious program that is the culprit. This was a big pacman update, so it's hard to say exactly why it was. I can keep an eye on it in future updates. What exactly would I do with rmmod/modprobe? Are there any useful keywords to look for in the pacman log?

terdon‭ wrote over 1 year ago
copy link

No, not really, they are just the commands that load (modprobe) and unload (rmmod or, actually, these days modprobe -r instead) modules ("drivers" in the Windows world) from the kernel. What you describe is often caused by a new module that needs to be reloaded although I haven't seen this in a while now since most are handled via DKMS.