Bug 152040 - misinterpreted network mount shows up as cdrom device on desktop
Summary: misinterpreted network mount shows up as cdrom device on desktop
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-11-09 09:45 UTC by David Jander
Modified: 2012-07-10 19:45 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 David Jander 2007-11-09 09:45:20 UTC
Version:            (using KDE KDE 3.5.8)
Installed from:    Ubuntu Packages
OS:                Linux

I have several samba shares mounted as cifs filesystem on my workstation. One of these samba shares happens to be called "cdroms". The curious thing is that only this share appears as an icon of a cdrom device on the desktop, while it shouldn't. I right-click on it and get a context menu with the options "Eject", "Mount" and "Copy CD with K3B".
This is an ordinary smaba share mounted from a samba server, like many others I use. It seems that only because this one is called something with "cdrom" in it's name, KDE thinks it is a CDROM device!

How to reproduce:

1.- Set up a samba share on a samba-server, and call the share "cdroms".
2.- Make an entry on a KDE desktop computer's /etc/fstab that looks something like this:

\\server\cdroms  /mnt/cdroms  cifs  username=XX,password=YY,uid=ZZ,gid=users  0 0

3.- Give the command "sudo mount -a" on the desktop PC.
4.- Now you have a "CDROM" icon on your KDE desktop, which tries to behave like a CDROM drive, and the share's entry in "system:/media/" looks like a CDROM and not like a network share.

Expected behaviour:

The desktop icon should not appear and the network share should not have a CDROM icon in konqueror/dolphin "system:/media/".
Comment 1 Jekyll Wu 2012-07-10 19:45:12 UTC
KDE3 is unmaintained. If this problem still applies to recent versions of KDE4 (KDE SC 4.8.4 or higher), please feel free to reopen this report or create a new report. Thanks.