Bug 126755

Summary: kopete 0.11.2(!) crashes without v4l devices connected (user interaction needed)
Product: [Unmaintained] kopete Reporter: Johannes Schaub <Schaub-Johannes>
Component: Audio/Video PluginAssignee: Kopete Developers <kopete-bugs-null>
Status: RESOLVED FIXED    
Severity: crash    
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Possible fix (not tested)

Description Johannes Schaub 2006-05-04 22:20:25 UTC 
Version:            (using KDE Devel)
Installed from:    Compiled sources

kopete crashes if you go to Settings Dialog, select Device and then go to the middle dropdown (named "Input"). if there are no devices in the list and you focus that dropdown list and press up / down on your keyboard, kopete will crash providing this backtrace:


Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 29957)]
[KCrash handler]
#6  0x426eddc7 in Kopete::AV::VideoDevice::inputs ()
   from /opt/kde3/lib/libkopete_videodevice.so.0
#7  0x423c5e41 in AVDeviceConfig::slotInputKComboBoxChanged ()
   from /opt/kde3/lib/kde3/kcm_kopete_avdeviceconfig.so
#8  0x423cb9ff in AVDeviceConfig::qt_invoke ()
   from /opt/kde3/lib/kde3/kcm_kopete_avdeviceconfig.so
#9  0x414735b4 in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#10 0x41473bdb in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#11 0x417d8b60 in QComboBox::activated () from /usr/lib/qt3/lib/libqt-mt.so.3
#12 0x41516744 in QComboBox::keyPressEvent ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#13 0x414ad259 in QWidget::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#14 0x4140eb9f in QApplication::internalNotify ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#15 0x4140f1e2 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3
#16 0x40f774b5 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4
#17 0x4139e1ae in QETWidget::translateKeyEvent ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#18 0x413a53e4 in QApplication::x11ProcessEvent ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#19 0x413b91b5 in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#20 0x41425301 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#21 0x41425256 in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#22 0x4140dcff in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#23 0x0806d9c3 in main ()
Comment 1 Petr Sýkora 2006-06-12 15:11:12 UTC 
Kopete 0.11.1 :
probably same bug, only it crashes when you click on section "devices", you even don't get to selecting that dropdown menu.
Comment 2 Johannes Schaub 2006-06-12 16:01:51 UTC 
yes, actually i wanted to report that bug of kopete 0.11.1, but then when it was fixed in kopete 0.11.2 i searched if it is really fixed and found this, reported bug :(
Comment 3 Philip Rodrigues 2006-06-12 23:27:29 UTC 
I get the same with the 0.12 branch,  r531801.
Comment 4 Philip Rodrigues 2006-06-14 10:16:55 UTC 
Created attachment 16594 [details]
Possible fix (not tested)

More bounds checking needed (a la bug 120117), this time in
videodevicepool.cpp. The patch is a "schematic" solution - I haven't tested it
(it might not even compile!), and there are a bunch more places in the code
where bounds checking could/should also be done.

As in bug 120117, I guess the whole code path for the case where no video
devices are available could be rethought, but I don't have time to do this -
maybe in a few weeks.
Comment 5 Philip Rodrigues 2006-06-14 20:09:10 UTC 
Just tested, and it prevents the crash, although CPU usage goes to 100% on entering that dialog - I don't remember whether that happened before.
Comment 6 Johannes Schaub 2006-06-18 15:41:08 UTC 
yes, the problem with 100% CPU usage was there before too :(
Comment 7 Johannes Schaub 2006-12-23 19:50:49 UTC 
it still crashes with the most recent kopete (branch 3.5 of KDE)
Comment 8 Cláudio da Silveira Pinheiro 2008-01-22 03:45:21 UTC 
Tested recent builds, 3.5.x, 4.0.x and trunk. Couldn't reproduce the bug.