Re: Bug#78129: kups: Cannot configure my printer anymore
On Mon, Nov 27, 2000 at 06:53:15PM +0100, Mariusz Przygodzki wrote:
> I can not reproduce this bug.
> Versions of the packages (on my machine) kups depends on:
> cupsys 1.1.4-2
> kdelibs3 2.0-final-11
> libc6 2.2-4
> libjpeg62 6b-1.2
> libkupsdconf1 0.8.0.20001119cvs-1.1
> libpng2 1.0.8-1
> libqtcups1 1.1-3.1
> xlib6 3.3.6-15
> xlibs 4.0.1-8
> zlib1g 1.1.3-11
I just updated my system to the most up-to-date packages available but kups
still crashes. Here's the stack trace:
(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)...[New Thread 1024 (LWP 10860)]
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
0x40ce8a99 in wait4 () from /lib/libc.so.6
#0 0x40ce8a99 in wait4 () from /lib/libc.so.6
#1 0x40d4c48c in __check_rhosts_file () from /lib/libc.so.6
#2 0x404e6d60 in KCrash::defaultCrashHandler () from
/usr/lib/libkdecore.so.3
#3 0x40f14a6b in pthread_sighandler () from /lib/libpthread.so.0
#4 0x40c72da8 in sigaction () from /lib/libc.so.6
#5 0x8062bc5 in QCollection::newItem ()
#6 0x805e574 in QCollection::newItem ()
#7 0x40906307 in QListView::rightButtonClicked () from /usr/lib/libqt.so.2
#8 0x40882b90 in QListView::contentsMouseReleaseEvent ()
from /usr/lib/libqt.so.2
#9 0x408c1a35 in QScrollView::viewportMouseReleaseEvent ()
from /usr/lib/libqt.so.2
#10 0x408c1576 in QScrollView::eventFilter () from /usr/lib/libqt.so.2
#11 0x40881a71 in QListView::eventFilter () from /usr/lib/libqt.so.2
#12 0x407f6c48 in QObject::activate_filters () from /usr/lib/libqt.so.2
#13 0x4083a2af in QWidget::event () from /usr/lib/libqt.so.2
#14 0x407a9edb in QApplication::notify () from /usr/lib/libqt.so.2
#15 0x4049c5d4 in KApplication::notify () from /usr/lib/libkdecore.so.3
#16 0x40779470 in QETWidget::translateMouseEvent () from /usr/lib/libqt.so.2
#17 0x40776bca in QApplication::x11ProcessEvent () from /usr/lib/libqt.so.2
#18 0x40775c4a in QApplication::processNextEvent () from /usr/lib/libqt.so.2
#19 0x407abb90 in QApplication::enter_loop () from /usr/lib/libqt.so.2
#20 0x40775bc7 in QApplication::exec () from /usr/lib/libqt.so.2
#21 0x8082cdb in QCollection::newItem ()
#22 0x40c63c1c in __libc_start_main () from /lib/libc.so.6
> Is anybody can help me and reproduce this bug?
There is no difference between running kups as root or as a normal user. The
text printed out on the calling konsole is:
menu value: 7
KCrash: crashing.... crashRecursionCounter = 2
KCrash: Application Name = kups path = <unknown>
Michael
--
Michael Meskes
Michael@Fam-Meskes.De
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!
Reply to: