common source for many apps crashing: KDELIBS4C2A

Bug #137445 reported by Ryan Budney
2
Affects Status Importance Assigned to Milestone
kdelibs (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: kdelibs4c2a

I have the same crashing phenomena happening with various different apps. I include here output from ktorrent, amarok, kate, qtdoc and kded. Comments follow below.

ktorrent:

rybu@rybu-laptop:~/movies$ ktorrent
X Error: BadDevice, invalid or uninitialized input device 156
  Major opcode: 145
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 156
  Major opcode: 145
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
DCOP aborting call from 'anonymous-9598' to 'kded'
kded: ERROR: Communication problem with kded, it probably crashed.
Qt: Warning: X Error: BadDevice, invalid or uninitialized input device 156
  Major opcode: 145
  Minor opcode: 3
  Resource id: 0x0
Qt: Warning: Failed to open device
Qt: Warning: X Error: BadDevice, invalid or uninitialized input device 156
  Major opcode: 145
  Minor opcode: 3
  Resource id: 0x0
Qt: Warning: Failed to open device
DCOP aborting call from 'anonymous-9587' to 'ktorrent'
ERROR: Communication problem with ktorrent, it probably crashed.

rybu@rybu-laptop:~/movies$ ktorrent -v
Qt: 3.3.7
KDE: 3.5.7
KTorrent: 2.2.1

amarok:

rybu@rybu-laptop:~/movies$ amarok
X Error: BadDevice, invalid or uninitialized input device 156
  Major opcode: 145
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 156
  Major opcode: 145
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
Segmentation fault (core dumped)

rybu@rybu-laptop:~/movies$ amarok -v
Qt: 3.3.7
KDE: 3.5.7
Amarok: 1.4.7

kate: (this was working earlier today, but now it crashes)

rybu@rybu-laptop:~/movies$ kate
X Error: BadDevice, invalid or uninitialized input device 156
  Major opcode: 145
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 156
  Major opcode: 145
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
Segmentation fault (core dumped)

rybu@rybu-laptop:~/movies$ kate -v
Qt: 3.3.7
KDE: 3.5.7
Kate: 2.5.7

Since kate was working earlier today it leads me to think that the source of these failures is not so much the individual apps, but some library they have in common.

kword similarly fails. qtdoc similarly fails:

rybu@rybu-laptop:~/movies$ qtdoc
X Error: BadDevice, invalid or uninitialized input device 156
  Major opcode: 145
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 156
  Major opcode: 145
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
DCOP aborting call from 'anonymous-9821' to 'kded'
kded: ERROR: Communication problem with kded, it probably crashed.
WARNING: DCOPReply<>: cast to 'QCString' error
rybu@rybu-laptop:~/movies$ Launched ok, pid = 9827
X Error: BadDevice, invalid or uninitialized input device 156
  Major opcode: 145
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 156
  Major opcode: 145
  Minor opcode: 3
  Resource id: 0x0
Failed to open device

rybu@rybu-laptop:~/movies$ kded -v
Qt: 3.3.7
KDE: 3.5.7
KDE Daemon: $Id: kded.cpp 634204 2007-02-16 16:12:23Z lunakl $

running kded without any options causes a failure, too:

rybu@rybu-laptop:~/movies$ kded
FATAL: DCOP communication problem!
Aborted (core dumped)

Let me know if there is anything else I can send your way to help.

Revision history for this message
Ryan Budney (delooper) wrote :

I'm running Ubuntu 7.10 with all the current updates as of today, Sept 4th, 2007. I'm using a Lenovo Thinkpad T61p (64bit Ubuntu kernel). Let me know what if anything can help.

Revision history for this message
Ryan Budney (delooper) wrote :

Here is a sample amarok backtrace (it's my first time doing this, bear with me!)

Revision history for this message
Ryan Budney (delooper) wrote :
Revision history for this message
Ryan Budney (delooper) wrote :

Something has changed. The KDE apps like amarok no longer crash. They still output the same error messages, but it doesn't cause them to crash anymore. The only major changes since I started this thread is I've kept updating the distribution, and finally got the native NVIDIA drivers working. I wish I knew what the problem was, but I don't.

Revision history for this message
Ryan Budney (delooper) wrote :

The problem has been fixed. I don't know what the cause was, or what the solution was.... but it's gone.

Changed in kdelibs:
status: New → Fix Committed
Changed in kdelibs:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.