LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software
User Name
Password
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.

Notices

Reply
 
LinkBack Search this Thread
Old 02-13-2009, 08:48 AM   #1
scorpion77
Member
 
Registered: Sep 2003
Distribution: Slackware64 14.1
Posts: 63

Rep: Reputation: 15
KWrite crashes with Nvidia drivers 180.29


Hi,
I have a problem with KWrite and Nvidia drivers 180.29. I use Slackware 12.2 with kernel 2.6.27.7-smp and KDE 3.5.10.
When I quit KWrite, I get a window with this title: unknown - The KDE Crash Handler. This window has two tabs.
"General" tab shows a short description: The application unknown (kwrite) crashed and caused the signal 11 (SIGSEGV).
"Backtrace" tab shows this:

Code:
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb5a96910 (LWP 6279)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#5  0x08203518 in ?? ()
#6  0xb759a04e in QGDict::remove_ascii ()
   from /usr/lib/qt-3.3.8b/lib/libqt-mt.so.3
#7  0xb72e7d06 in QMetaObject::~QMetaObject ()
   from /usr/lib/qt-3.3.8b/lib/libqt-mt.so.3
#8  0xb72e7ba4 in QMetaObjectCleanUp::~QMetaObjectCleanUp ()
   from /usr/lib/qt-3.3.8b/lib/libqt-mt.so.3
#9  0xb54cfac0 in ?? () from /usr/lib/kde3/libkatepart.so
#10 0xb55e47e0 in ?? () from /usr/lib/kde3/libkatepart.so
#11 0xb6af9ff4 in ?? () from /lib/libc.so.6
#12 0xbfce1b18 in ?? ()
#13 0xb69dfc24 in exit () from /lib/libc.so.6
Backtrace stopped: frame did not save the PC
This happens only if I open a file with KWrite clicking on its icon, using Konqueror or directly in my desktop. If I open a file using a shell like Konsole, when I quit KWrite I get no errors.
Until now, I noticed this strange behavior only with KWrite and Nvidia drivers 180.29. With Nvidia drivers 177.82 I have no problem. It's a very annoying bug.

Any idea to solve the problem?

Thanks,

Scorpion77
 
Old 02-14-2009, 10:37 AM   #2
stress_junkie
Senior Member
 
Registered: Dec 2005
Location: Massachusetts, USA
Distribution: Ubuntu 10.04 and CentOS 5.5
Posts: 3,873

Rep: Reputation: 331Reputation: 331Reputation: 331Reputation: 331
I think that the solution is obvious; use the older drivers.

I'm sure that you would prefer to find the actual problem and fix it but that is often not a realistic goal. Computers are complicated enough that it is impossible for developers to fix every problem. Given that, it makes no sense to me to try to fix every problem 'the right way' at the system administrator's level if a workaround is available.
 
Old 02-15-2009, 06:47 AM   #3
scorpion77
Member
 
Registered: Sep 2003
Distribution: Slackware64 14.1
Posts: 63

Original Poster
Rep: Reputation: 15
I solved installing KDE 4.2.0.
 
Old 02-15-2009, 07:23 AM   #4
metrofox
Member
 
Registered: Jan 2009
Location: Palermo, Italy
Distribution: Slackware
Posts: 236

Rep: Reputation: 37
You didn't solve the problem, you escaped from it, any way, you solved 'cause you installed the new version of kwrite
 
Old 04-03-2009, 07:53 AM   #5
perfect_circle
Senior Member
 
Registered: Oct 2004
Location: Athens, Greece
Distribution: Slackware, arch
Posts: 1,783

Rep: Reputation: 52
Same distro, same kernel almost same driver (180.22), same problem here.
 
Old 04-03-2009, 09:48 AM   #6
the trooper
Senior Member
 
Registered: Jun 2006
Location: England
Distribution: Debian Testing/Unstable Amd64
Posts: 1,471

Rep: Reputation: Disabled
Quote:
Originally Posted by perfect_circle View Post
Same distro, same kernel almost same driver (180.22), same problem here.
Try the current stable driver 180.44.

Regards.
The trooper.
 
Old 04-03-2009, 10:26 AM   #7
amani
Senior Member
 
Registered: Jul 2006
Location: Kolkata, India
Distribution: 64-bit GNU/Linux, Kubuntu64, Fedora QA, Slackware,
Posts: 2,754

Rep: Reputation: Disabled
Can you reproduce th bug with kate?
 
Old 04-23-2009, 03:44 PM   #8
El Nigromante
Member
 
Registered: Aug 2008
Distribution: Slackware 12.2, Slackware 13.0
Posts: 40

Rep: Reputation: 17
Hello,

Same problem here. As reported in this thread: http://www.linuxquestions.org/questi...61#post3518861

My card is an NVIDIA 8400GS. Full info (lspci -vvv -nn):

Code:
02:00.0 VGA compatible controller [0300]: nVidia Corporation GeForce 8400 GS [10de:0422] (rev a1) (prog-if 00 [VGA controller])
	Subsystem: ASUSTeK Computer Inc. Unknown device [1043:050a]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at fd000000 (32-bit, non-prefetchable) [size=16M]
	Region 1: Memory at d0000000 (64-bit, prefetchable) [size=256M]
	Region 3: Memory at fa000000 (64-bit, non-prefetchable) [size=32M]
	Region 5: I/O ports at ec00 [size=128]
	[virtual] Expansion ROM at febe0000 [disabled] [size=128K]
	Capabilities: [60] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [68] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
		Address: 0000000000000000  Data: 0000
	Capabilities: [78] Express (v1) Endpoint, MSI 00
		DevCap:	MaxPayload 128 bytes, PhantFunc 0, Latency L0s <512ns, L1 <4us
			ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
		DevCtl:	Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
			RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
			MaxPayload 128 bytes, MaxReadReq 512 bytes
		DevSta:	CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
		LnkCap:	Port #0, Speed 2.5GT/s, Width x16, ASPM L0s L1, Latency L0 <512ns, L1 <4us
			ClockPM- Suprise- LLActRep- BwNot-
		LnkCtl:	ASPM Disabled; RCB 128 bytes Disabled- Retrain- CommClk+
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
	Capabilities: [100] Virtual Channel <?>
	Capabilities: [128] Power Budgeting <?>
	Capabilities: [600] Vendor Specific Information <?>
	Kernel driver in use: nvidia
	Kernel modules: nvidiafb, nvidia
I have tested with 180.29 and with current stable driver 180.51, and in both cases the problem is still present. I also reinstalled kdebase (just in case it was corrupted). No way.

Here is the output of the "backtrace" window:

Code:
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb5a2f910 (LWP 19967)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#5  0x081ffe98 in ?? ()
#6  0xb753004e in QGDict::remove_ascii ()
   from /usr/lib/qt-3.3.8b/lib/libqt-mt.so.3
#7  0xb727dd06 in QMetaObject::~QMetaObject ()
   from /usr/lib/qt-3.3.8b/lib/libqt-mt.so.3
#8  0xb727dba4 in QMetaObjectCleanUp::~QMetaObjectCleanUp ()
   from /usr/lib/qt-3.3.8b/lib/libqt-mt.so.3
#9  0xb5441ac0 in ?? () from /usr/lib/kde3/libkatepart.so
#10 0xb55567e0 in ?? () from /usr/lib/kde3/libkatepart.so
#11 0xb6a94ff4 in ?? () from /lib/libc.so.6
#12 0xbff725e8 in ?? ()
#13 0xb697ac24 in exit () from /lib/libc.so.6
Backtrace stopped: frame did not save the PC
Note: The bug does not happen with kate

Last edited by El Nigromante; 04-23-2009 at 04:48 PM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Has anyone been able to get the nvidia 180 series drivers to work on slack? walmartshopper Slackware 75 04-24-2009 09:50 AM
screensaver crashes. nvidia drivers maybe? doralsoral Linux - Software 3 02-18-2007 10:38 AM
[X] after latest nVidia drivers: X crashes G00fy Linux - Software 21 02-18-2007 10:31 AM
FC4 crashes after installing Nvidia Drivers Daedalus_i Fedora 6 12-16-2005 06:21 PM
WindowMaker crashes after installing nVIDIA drivers Tim2000 Linux - Software 2 10-17-2003 06:34 AM


All times are GMT -5. The time now is 07:51 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration