Bug 130105 - qt/kde apps which use splash screen feature freezes system
Summary: qt/kde apps which use splash screen feature freezes system
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: X.Org (show other bugs)
Version: unspecified
Hardware: Other Other
: P5 - None : Normal
Target Milestone: ---
Assignee: Stefan Dirsch
QA Contact: Stefan Dirsch
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-21 21:34 UTC by Dennis Lubert
Modified: 2006-01-12 14:07 UTC (History)
1 user (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dennis Lubert 2005-10-21 21:34:13 UTC 
Hi,

I just installed a fresh new SuSE 10.0 on my laptop (as addition to the old one,
which still runs fine) with nvidia chipset and nvidia driver and all up2date
packets I could find on the SuSE ftps. Now I have the problem that whenever some
program uses the qt/kde splashscreen feature, the system freezes, it looks like
the reason is that X freezes. Examples are the splash-screen like kde load
screen or kvirc. I don't know what to do to further identify the cause of the error.
Comment 1 Lubos Lunak 2005-10-24 14:05:31 UTC 
- Make sure you have the latest nvidia drivers.
- Try with the opensource nvidia drivers.
- Is the system frozen completely or only X? Can you ping the computer, log in remotely?
Comment 2 Dennis Lubert 2005-10-24 20:29:08 UTC 
- I have nvidia driver 7676 which seem to be the latest ones.
- the opensource nvidia drivers crash here on x startup
- its frozen completely, not even sysreq keys work.

I have looked a bit further at it with a few debuggers and since konqueror at startup without any website freezes too I assumed a more general problem. It looks like the X is somehow using the render extension always the times when it happens. So either its beeing called in an unusualy way or the driver does have bad support. unfortunately it looks like to disable render extension I have to recompile X...
Comment 3 Lubos Lunak 2006-01-11 17:27:17 UTC 
Looks like X problem to me.
Comment 4 Stefan Dirsch 2006-01-11 23:57:41 UTC 
Please attach /etc/X11/xorg.conf and /var/log/Xorg.0.log for a "nv" driver configuration.
Comment 5 Dennis Lubert 2006-01-12 13:01:45 UTC 
Now nearl 3 months have passed after reporting of the problem. I now use kde 3.5.0, nvidia 8178 a newer qt, kernel and lots of other stuff updated. starting up kde with enabled render extension now works again, and I dont know which of the updated packets was the one (maybe a combination of some?)
So a nv driver config log cannot be attached too, the driver still crashes immediately on startup.
Comment 6 Stefan Dirsch 2006-01-12 13:55:17 UTC 
What does mean crashing? Does it freeze the system? In this case you can reboot into runlevel 3 and copy /var/log/Xorg.0.log to attach it later.
If this is not an option for you we should close this bugreport as WONTFIX.
Comment 7 Dennis Lubert 2006-01-12 14:07:34 UTC 
crash as in segfault and drop to console (im per default in rl3). The log file isnt showing anything beside the banner. As I dont need the nv driver (nvidias is working fine now, and nv is slow like hell), Im not investigating this further for now, and even if it would have to be an entirely different bugreport.
I mark the bug as FIXED now, since the kde freeze problem with nvidia driver and render extension is solved, since the updates within the last three months somehow fixed it.