[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde
Subject:    Re: Create new devices is BIGTIME broken in KDE 2.1
From:       Troy Unrau <troy () kde ! org>
Date:       2001-01-13 22:21:52
[Download RAW message or body]


You are using mandrake, no?

In mandrake, they use the supermount thing for cdroms and floppies.  You 
don't actually have to mount them, so to access the cdrom, just point konq to 
/mnt/cdrom.  When creating a link on the desktop, don't create a new device, 
create a shortcut to /mnt/cdrom.  That should be all you need to do.

Troy

On Saturday 13 January 2001 11:44, Praedor Tempus wrote:
> I once thought I had this fixed but it isn't so.
>
> I ask you to indulge me here if you are using KDE 2.1.  Delete the desktop
> icon for your CDROM device.   Now try to re-create it using the desktop
> menu for Create new.
>
> I imagine that upon doing this many of you will find that the icon doesn't
> work.  You can click all you want on what SHOULD be a working CDROM device
> icon but nothing will come of it.  If you look in your .xsession-errors
> file you will likely see entries like this for each time you clicked on the
> BROKEN device link:
>
> Syntax error: Unknown command '/mnt/cdrom'
>
> This problem will arise if you delete and try to re-create your other
> device links too (other folders/mount points).
>
> Here is what my CDROM kdelnk contents look like after re-creating the CDROM
> device:
>
> [Desktop Action Eject]
> Exec=kdeeject %v
> Name=Eject
> [Desktop Entry]
> Actions=Eject
> Dev=/dev/cdrom
> FSType=supermount
> Icon=cdrom_mount
> MountPoint=/mnt/cdrom
> ReadOnly=true
> Type=FSDevice
> UnmountIcon=cdrom_unmount
>
> Looks OK, but it isn't.  Konqueror fails to open the damn CDROM and instead
> adds a ridiculous  "Syntax error:..." message to .xsession-errors.
>
> Why would KDE people break something so simple and fundamental as this?  It
> has worked fine since KDE's inception but now, with the latest versions, it
> is broken BIG TIME.  It makes much of the desktop unusable as a result.
> Oddly enough, if you open up Konqueror to your home directory and then
> navigate over to the offending mountpoint (/mnt/cdrom or wherever your
> cdrom is mounted) it will work OK.  The device link on the desktop chokes. 
> I can't even look at Trash because Konqueror refuses to open the damn thing
> on the desktop.

-- 
first there were monkeys, then there was unix.
-- 
Send posts to:  kde@lists.netcentral.net
 Send all commands to:  kde-request@lists.netcentral.net
  Put your command in the SUBJECT of the message:
   "subscribe", "unsubscribe", "set digest on", or "set digest off"
PLEASE READ THE ARCHIVED MESSAGES AT http://lists.kde.org/ BEFORE POSTING
**********************************************************************
This list is from your pals at NetCentral <http://www.netcentral.com/>

[prev in list] [next in list] [prev in thread] [next in thread]