Ubuntu
kde-guidance package

Kubuntu 7.04 "Disk & Filesystems" always crashes

Bug #109820 reported by Sb on 2007-04-25

This bug report is a duplicate of: Bug #87829: Feisty: kde-systemsettings, disk & filesystems, crashes when adding smb-share. Edit Remove

Affects		Status	Importance	Assigned to	Milestone
	kde-guidance (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

Hi,

I'm trying to mount a remote Windows share on Kubuntu 7.04. I goto System Settings --> Disk & Filesystems and enable as Administrator mode. I goto "New" and select Type: "Windows File Sharing". I pick my mount point, and then I click "Scan" next to network share. It loads some sort of network browser, and then quickly crashes. It does this every time. Below is the backtrace. Any suggestion?

Thanks for your help!

=========

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(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)
[Thread debugging using libthread_db enabled]
[New Thread -1233099056 (LWP 8269)]
(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)
(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)
[KCrash handler]
#6 0x089fb4a8 in ?? ()
#7 0xb5adfd49 in ?? () from /usr/lib/python2.5/site-packages/sip.so
#8 0x086c2e38 in ?? ()
#9 0x00000000 in ?? ()

Revision history for this message

Jonathan Jesse (jjesse) wrote on 2007-04-25:

Confirming thsi bug on Feisty. The crash is the window that opens up open clicking on "new" not the whole systems settings application

Revision history for this message

Yuriy Kozlov (yuriy-kozlov) wrote on 2007-04-30:

Thanks for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 87829 and is being marked as such. Please feel free to report any other bugs you may find.