systemsettings/disk&file - crash creating mount point of windows share

Bug #97237 reported by bs27975
4
Affects Status Importance Assigned to Milestone
kde-guidance (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: kde-systemsettings

sudo mkdir /dev/myshare

menu / system settings / advanced / disk & filesystem, administrator mode, new, windows file sharing, set mount point as /dev/myshare. Hit scan to pick network share - crash.

Can browse to network share just fine. Even create link on desktop and click ok.

(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 -1232667952 (LWP 6740)]
(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)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6 0x084ea1d8 in ?? ()
#7 0xb64bfd49 in ?? () from /usr/lib/python2.5/site-packages/sip.so
#8 0x084f4ae0 in ?? ()
#9 0x00000000 in ?? ()

Revision history for this message
bs27975 (b.s.) wrote :

Filling things out manually, pressing OK does ... nothing ?!?

mount point: /dev/data
network share: smb://myhost/Data
connect as: username me, password password, enable at startup.

writeable, file belongs to me and my megroup, any user to enable/disable.

Advanced left at noauto.

Click OK, nothing happens as far as I can see.

Click cancel, it does.

FWIW

Revision history for this message
Yuriy Kozlov (yuriy-kozlov) wrote :

Thanks for your bug report. This particular bug has already been reported and is a duplicate of bug 87829 and is being marked as such. Please follow up on that bug and feel free to report any other bugs you may find.

Revision history for this message
John Kelly (jpkelly100) wrote :

Same thing happened on my machine with exact same error info.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.