Bug 115688 - Quanta does not remmber smb-pwd and chrashes when trying to open/save a file via smb
Summary: Quanta does not remmber smb-pwd and chrashes when trying to open/save a file ...
Status: RESOLVED DUPLICATE of bug 103795
Alias: None
Product: quanta
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: András Manţia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-04 18:18 UTC by Björn Bartels
Modified: 2005-11-04 19:10 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Björn Bartels 2005-11-04 18:18:37 UTC
Version:            (using KDE KDE 3.4.0)
Installed from:    SuSE RPMs
OS:                Linux

I am using QUANTA to edit several files (php, html...). After a while,
when trying to save the changings, quanta demands for the smb-password
again, again, and again, and... even thou it is set for systemwide use.
Next, sometimes the file is saved but seemingly more often I am told that
my access to that file is denied. When I try to repeat those saving-steps
it comes that QUANTA chrashes with "Signal 11 (SIGSEGV)" and spits out
these following lines:

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 1104581344 (LWP 15598)]
[KCrash handler]
#7  0x40b026d1 in KDirListerCache::slotUpdateResult ()
   from /opt/kde3/lib/libkio.so.4
#8  0x40b02fc7 in KDirListerCache::qt_invoke () from /opt/kde3/lib/libkio.so.4
#9  0x414820ee in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#10 0x40a1ba72 in KIO::Job::result () from /opt/kde3/lib/libkio.so.4
#11 0x40a74bdc in KIO::Job::emitResult () from /opt/kde3/lib/libkio.so.4
#12 0x40a7e03c in KIO::SimpleJob::slotFinished ()
   from /opt/kde3/lib/libkio.so.4
#13 0x40a7e3de in KIO::ListJob::slotFinished () from /opt/kde3/lib/libkio.so.4
#14 0x40a70c7b in KIO::ListJob::qt_invoke () from /opt/kde3/lib/libkio.so.4
#15 0x414820ee in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#16 0x41482896 in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#17 0x40a20f3c in KIO::SlaveInterface::finished ()
   from /opt/kde3/lib/libkio.so.4
#18 0x40a52824 in KIO::SlaveInterface::dispatch ()
   from /opt/kde3/lib/libkio.so.4
#19 0x40a3fbf3 in KIO::SlaveInterface::dispatch ()
   from /opt/kde3/lib/libkio.so.4
#20 0x40a2e78b in KIO::Slave::gotInput () from /opt/kde3/lib/libkio.so.4
#21 0x40a55c3a in KIO::Slave::qt_invoke () from /opt/kde3/lib/libkio.so.4
#22 0x414820ee in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#23 0x4148271d in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#24 0x417d2fe0 in QSocketNotifier::activated ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#25 0x414a1d40 in QSocketNotifier::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#26 0x4141f85f in QApplication::internalNotify ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#27 0x41421423 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3
#28 0x410b1ad1 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4
#29 0x414139d6 in QEventLoop::activateSocketNotifiers ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#30 0x413ccf12 in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#31 0x414377b1 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#32 0x414375f6 in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#33 0x414212ef in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#34 0x0809d8a3 in main ()
Comment 1 Thiago Macieira 2005-11-04 19:10:29 UTC
Upgrade KDE. This bug has been fixed for almost 7 months.

*** This bug has been marked as a duplicate of 103795 ***