Summary: | kwintv crashes after KDE update to 3.1.3 | ||
---|---|---|---|
Product: | [Unmaintained] kwintv | Reporter: | Oliver Schwabedissen <Oliver> |
Component: | general | Assignee: | KWinTV Developers <kwintv> |
Status: | RESOLVED INTENTIONAL | ||
Severity: | crash | ||
Priority: | NOR | ||
Version First Reported In: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Oliver Schwabedissen
2003-08-09 22:12:11 UTC
Having exact same problem. Saw from the developer's reply on another bug that he recommends QtVision, which I installed now. Seems to work reasonably, though I've not used it for more than 1 hour yet. It imports the old channels file. I downloaded an RPM for SuSE with a reasonable up-to-date version from : http://packman.links2linux.org/?action=327 exact probleme suse 8.2 : (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)...[New Thread 16384 (LWP 6044)] (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... 0x40f42cf7 in waitpid () from /lib/libpthread.so.0 #0 0x40f42cf7 in waitpid () from /lib/libpthread.so.0 #1 0x40651ad9 in KCrash::defaultCrashHandler(int) () from /opt/kde3/lib/libkdecore.so.4 #2 0x40f41895 in __pthread_sighandler () from /lib/libpthread.so.0 #3 <signal handler called> #4 0x08098603 in QListView::removeItem(QListViewItem*) () #5 0x08097e73 in QListView::removeItem(QListViewItem*) () #6 0x08098950 in QListView::removeItem(QListViewItem*) () #7 0x409e1bc7 in QObject::activate_signal(QConnectionList*, QUObject*) () from /usr/lib/libqt-mt.so.3 #8 0x409e1ca8 in QObject::activate_signal(int, int) () from /usr/lib/libqt-mt.so.3 #9 0x40ce5dd1 in QComboBox::highlighted(int) () from /usr/lib/libqt-mt.so.3 #10 0x40a6ec8c in QComboBox::internalHighlight(int) () from /usr/lib/libqt-mt.so.3 #11 0x40ce6046 in QComboBox::qt_invoke(int, QUObject*) () from /usr/lib/libqt-mt.so.3 #12 0x409e1bc7 in QObject::activate_signal(QConnectionList*, QUObject*) () from /usr/lib/libqt-mt.so.3 #13 0x409e1ca8 in QObject::activate_signal(int, int) () from /usr/lib/libqt-mt.so.3 #14 0x40cee1e0 in QListBox::highlighted(int) () from /usr/lib/libqt-mt.so.3 #15 0x40aa592c in QListBox::setCurrentItem(QListBoxItem*) () from /usr/lib/libqt-mt.so.3 #16 0x40aa5768 in QListBox::setCurrentItem(int) () from /usr/lib/libqt-mt.so.3 #17 0x40a71070 in QComboBox::popDownListBox() () from /usr/lib/libqt-mt.so.3 #18 0x40a72266 in QComboBox::setEnabled(bool) () from /usr/lib/libqt-mt.so.3 #19 0x0809810d in QListView::removeItem(QListViewItem*) () #20 0x0806e934 in QWidget::setGeometry(QRect const&) () #21 0x0807cb88 in QMemArray<char>::detach() () #22 0x0807dabc in QMemArray<char>::detach() () #23 0x410a18ae in __libc_start_main () from /lib/libc.so.6 Ditch KWinTV, Try QtVision ! I'm using it for more than a month now and had no problems with it ! Subject: Re: kwintv crashes after KDE update to 3.1.3 eric@veltman.nu wrote: >------- You are receiving this mail because: ------- >You are a voter for the bug, or are watching someone who is. > >http://bugs.kde.org/show_bug.cgi?id=62429 > > > > >------- Additional Comments From eric@veltman.nu 2003-09-26 23:08 ------- >Ditch KWinTV, Try QtVision ! I'm using it for more than a month now and had no >problems with it ! > > > > > Thanks for the reply Eric but that's exactly what I did and it has enought base features to make me happy for the moment. Guy. Sorry folks, we're only fixing bugs in the rewrite, which is unfortunately coming along very slowly. The old code is very buggy and dangerous to change without breaking many many things. |