KDEmod (KDE) device notifier won't unmount devices

I'm using KDEmod 4.4 currently, but this has been happening since 4.3 using plain KDE too. For some reason, when I use the device notifier to mount a flash drive and then try to unmount it, I sometimes get the "Could not unmount the device. One or more files on this device are open within an application" error message. However, I am able to unmount from the command line, so I think it must just be an issue with device notifier.

jlacroix wrote:
armageddon09 wrote:No. Could you please explain a little ?
On my install, whenver I save files to my desktop (KDE 4.3.2) the files don't show up until I rightclick the desktop and click "refresh". The same thing happens when I delete a file. When I delete a file, the file still shows up on my desktop until I rightclick and refresh the desktop.
Whatever KDE uses to monitor when files are deleted and whatnot is not working.
I have the same issue here. I belive it's because of the current kernel. Take a look at this http://bugs.archlinux.org/task/16193?st … &closedto=
Try enabling Nepomuk.
Last edited by eldarion (2009-10-19 16:11:17)

Similar Messages

Cdemu issues (again), this time with KDE Device Notifier

OK, so I'm having trouble with cdemu again. This time it's not about mounting an image, but getting rid of it
Essentially, when I load an image with the cdemu client, KDE Device Notifier immediately recognises it as an inserted optical media... which is cool.
However, when I try to unload it with cdemu, it stays "stuck" in KDE Device Notifier, and I can't access any other image which I mount via cdemu afterwards.
In other words, I do the following...
cdemu load 0 <name>.iso
The image appears to be successfully loaded, and I can access it's contents with no trouble at all. KDE Device Notifier sees it normally, can mount it and open it in Dolphin.
Then, when I'm done with it, I do the following...
cdemu unload 0
This apparently unloads the image, as I can't open it in Dolphin anymore (or any other application within KDE), but KDE Device Notifier still sees it as if the "optical drive" is inserted, and it won't go away. If I try loading another image in cdemu, KDE will still see the previous one, and I won't be able to do anything with it.
I cannot mount or unmount it, I cannot open it in Dolphin or any other application (obviously, because the image isn't mounted anymore), but KDE Device Notifier still insists that it's there, and won't let me access any other image mounted via cdemu.
Since I have very little experience with cdemu and KDE's logs, I don't know what else I should post here, or where to find it...
Any advice or idea would be much appreciated. TIA!

Today the issue disappeared!
I don't understand, yesterday I spent my whole afternoon trying to find why it was not recognised, I rebooted a few times without any luck. In the evening I still had a cdemu iso mounted and left my laptop in "suspend to ram" state, and this morning as soon as I wake from suspend to ram I have a notification from device notifier that my iso is available! I tried to unmount / mount and reboot then mount / unmount, it now works fine...
So it seems the issue fixed itself... Don't know how though..
And the new version of kde-cdemu-manager works fine as well.

KDE Device Notifier does not autohide

The KDE device notifier appears when a new mass storage device is plugged in. In the past it would autohide after a few seconds if I didn't take any action. But now, it stays on the screen forever, until I click on it to hide it. It's pretty annoying.
I've had this before and solved it by reinstalling my whole system and starting with a fresh profile. I hope someone knows an easier fix? There is nothing interesting in .xsession-errors when I plug it in:
kded(995)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
kded(995)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:

xvello,
The issue might be in hal
I could hug you
You're absolutely right. Hal was the culprit. Under /etc/hal/fdi/information/ there were two files "media-check-disable-storage_model_<my CDs model name>" and both of them had a line:
<merge key="storage.media_check_enabled" type="bool">false</merge>
Setting them to
<merge key="storage.media_check_enabled" type="bool">true</merge>
reenabled the notification of KDE's device Notifier.
As users always say: I never changed this
Marking this as solved.
Thanks a lot
Harvey

KDE Device Notifier command for specific Konqueror View Profile?

Hi,
I added a custom action in KDE device notifier widget for optical devices to be opened with Konqueror. However, is it possible to modify that command so that Konqueror opens with a specific view profile?
Many thanks in advance.

Thanks a bunch!
However, one tiny problem still persists: When I execute konqueror --profile <profile_name> %f, a Konqueror window split into four opens, one showing the optical device but the other three are void. My view profile indeed splits the window into 4 sub-windows, but what I'm trying to do is basically view the optical device in one sub-window while the others show two certain websites and one samba shared folder.
I know it sounds weird, but is it at least possible?

[SOLVED] 0 B Removeable Media in KDE Device Notifier

Hi all.
Recently, I noticed a entry in the KDE Device Notifier named "0 B Removeable Media". I haven't the foggiest idea what this is or how it got there. Does anyone have an idea as to how I should go about removing or hiding this entry? Does anyone know where this "ghost" entry is from?
Thanks in advance.
Last edited by allevil669 (2013-09-26 20:28:01)

drcouzelis wrote:
I don't know the answer, but I have some ideas.
Is the "0 B Removeable Media" entry always there?
Is the entry there if you create a new user and then start KDE as the new user?
Does the entry provide any more details if you right-click it or something? (I don't use KDE)
How many drives are in your computer?
How your your drives partitioned?
The entry is always there. Persistent through every reboot since I noticed it.
The entry is in the Device Manager with a new user.
No other information is forthcoming with either a right, or left click. Left click simple gives me the standard options for "what to do with this", and right click gives me the option of changing the Device Notifier settings.
There are seven drives in my computer. One HDD, one DVD drive, and one multi-card reader w/ five individual slots. Each of these drives are behaving properly in the Device Manager.
The only drive that is partitioned is my HDD. Partition list incoming...
cfdisk (util-linux 2.23.2)
Disk Drive: /dev/sda
Size: 320071851520 bytes, 320.0 GB
Heads: 255 Sectors per Track: 63 Cylinders: 38913
Name Flags Part Type FS Type [Label] Size (MB)
Pri/Log Free Space 1.05 *
sda1 Boot Primary ext4 [ROOT] 26843.55 *
sda2 Primary ext4 [HOME] 293226.94 *
Pri/Log Free Space 0.32 *

External hard drive won't unmount for disk utility.

Im not sure if this is the right topic area but I have a white macbook and my external hard drive won't unmount. I want to erase it via disk utility but it keeps telling me other programs are using it.

Drive Preparation
1. Open Disk Utility in your Utilities folder.
2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Click on the Partition tab in the DU main window.
3. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, set the partition scheme to GUID (for Intel Macs) or APM (for PPC Macs) then click on the OK button. Click on the Partition button and wait until the process has completed.

Lacie won't unmount

Greetings Gurus,
I took part of my system home to do some work over the holidays and am now having trouble unmounting my Lacie BigDiskExtremeTriple. This drive has always been connected to my Dual G5 desktop (profile listed below), but I'd hoped to get some work done on the MBPro 17.
Here's what info I have so far:
I believe the problem started from having several external FW drives looped through a Belkin FW hub (sorry, no specs on it right now other than 3 FW 6pin ports on each side of the hub) - computer froze and I had to reboot.
I believe this caused some possible directory damage to the Lacie since I had been unable to 'unmount' the drive properly.
Support and Google searches have offered several things to try, but none have resolved the issue yet. Most suggest a 'directory issue with the drive' that Disk Warrior may fix. I have DW3.0, but also read that it's not going to work if the drive won't unmount in Disk Utility (which it wont')
Here is what I've tried so far.
any usage of Finder/Spotlight locks up the system.
Drive seems to work, though I've delayed pushing it with apps (mostly FCStudio), until I can resolve the issue.
Force Quit Finder - have been able to then unmount the drive once or twice, but usually not.
Restart Mac - can usually then unmount the drive, but not always
Check Activity monitor - this shows a Process ID/Name 'mds' at Root level running 99% (any ideas there?)
Run Terminal commmand 'sudo lsof | grep "The-Volume-Name"
- This gives me 4 items (one at Finder and 3 at mds) - Here is what it listed...
Finder 98 kevandholdsworth 19r VDIR 14,11 68 10944 /Volumes/MEDIA/.Trashes/501
mds 186 root 22u VREG 14,11 1069056 4392 /Volumes/MEDIA/.Spotlight-V100/store.db
mds 186 root 23u VREG 14,11 1069056 4393 /Volumes/MEDIA/.Spotlight-V100/.store.db
mds 186 root 24u VREG 14,11 0 4395 /Volumes/MEDIA/.Spotlight-V100/.journalHistoryLog
Is it possible to just locate these files and delete them? or will DW need to do it's own thing?
I'm ready to try Disk Warrior, but would appreciate any feedback regarding the issue before I attempt it.
(sadly, I broke the cardinal rule of not double posting [initially in the 'Finder, Dock & Dashboard Forum], but feel much more confident of getting strong advice here...my apolgies to any I've upset by doing so)
Thanks,
Kevan
PS - just checked my profile and it does not yet list the MBP...It's a 17" w/2GB Ram, same OS and Software as on the G5

It's not backed up yet...I'll do that before running DiskWarrior
I'm not convinced what the issue is. I now am unable to unmount any external HDs (all FW) from my G5.
Jim, Disk Utility is not giving me the option to 'disable journaling'.
Spotlight prefs won't let me add(+) either volume to 'privacy'...that's my understanding on how to remove it from being indexed. However, when I tried 'dragging' one of the volumes into the 'privacy' area, it went 'Poof'...now showing up on desktop, but no longer in finder...is this what you are referring to?
Kenneth, I'm the only user/admin...not seeing an issue there. Maybe I'm missing something from your suggestion. I simply boot up as I always do.
UPDATE...
FYI, here is the original prompt I get when trying to unmount any external hard drives: "The disk "DISK NAME" is in use and could not be ejected. Try quitting applications and try again"
There are no visible applications open...I notice now after dragging a volume to spotlight privacy that one of the text lines from the Terminal sudo command no longer shows up.
I have been able to unmount all drives after starting up from a backup drive (Panther). However, restarting from Tiger does not allow this. I'm also a bit concerned about doing restarts without properly unmounting any of these drives.
Here are a couple of links I've been trying to apply, but it's looking like a backup and DiskWarrior are next steps. A show deadline is preventing me from doing so at this time.
http://www.macworld.co.uk/forums/msgs.cfm?msg=80013&forum=4
http://www.shirt-pocket.com/forums/archive/index.php/t-1572.html
http://discussions.apple.com/thread.jspa?messageID=3651281&#3651281
http://www.thexlab.com/faqs/stopspotlightindex.html
http://docs.info.apple.com/article.html?artnum=301562
Thanks again for all suggestions. I need to crunch out this show and will keep up with this thread until I can resolve the whole issue...will have to award points in a few days.
K

[SOLVED] kdebase-workspace: conflicts with kdemod-kde-common

Hi! My pacman -Syu failed today: Here there is the output (of a retrial):
:: Synchronizing package databases...
kdemod-core is up to date
kdemod-extragear is up to date
core is up to date
extra is up to date
community is up to date
:: Starting full system upgrade...
:: Replace qtmod with kdemod-core/kdemod-kde-common? [Y/n] Y
:: Replace guidance-power-manager with extra/kdebase-workspace? [Y/n] Y
resolving dependencies...
looking for inter-conflicts...
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: kdebase-workspace: conflicts with kdemod-kde-common
Any suggestions on how to get this update right?
Last edited by joan (2009-02-23 02:18:30)

joan wrote:Hi! My pacman -Syu failed today: Here there is the output (of a retrial):
:: Replace qtmod with kdemod-core/kdemod-kde-common? [Y/n] Y
:: Replace guidance-power-manager with extra/kdebase-workspace? [Y/n] Y
Any suggestions on how to get this update right?
Try:
pacman -Rd gtmod
pacman -S qt
#Qtmod not needed anymore
pacman -R guidance-power-manager /or pacman -Rcsn ....
pacman -Syu kdemod /or pacman -Syu kdemod-complete
also backup/ remove ~/.kde4 to start with clean config, especially if you have your own plasmoids.
#powerdevil is included in kde now, so other inferior powermanagers might conflict with it.

RAID won't unmount...can't repair

Problem: after fixed failed RAID (lost in poweroutage), RAID'd drive won't mount. If I drop to single user mode and fsck the boot volume (no errors listed), after reboot it's the RAID volume is back. I loose it after a restart without fsck (boot volume loads but RAID is "unrecognizeable").
When it mounts everything functions as it should (users get home folders and have read/wrote access, etc.). However if I try to repair it in disk utility (per Apple phone support), i get an error message saying that the disk can't unmount so therefore can't check it.
Any suggestions (besides clean install) that you have to keep the RAID volume intact? I refuse to believe that it's toast as i am able to have it function. I guess I wouldn't be opposed to a wipe if I could get a good backup of it, but I can't even do that since it won't unmount.
Can't wait to hear what you come up with!
Thanks in advance.

Really, how toasted can it be when it all works flawlessly
until reboot? THis really bothers me....
Don't get me started about the Apple Hardware RAID card. I hope you have the write caches turned off for all LUNs because they don't always fully flush on graceful power down (the drives are disconnected from the bus before caches are flushed) - I've had a RADAR bug report turned in for almost 2 years on that, it was very hard to track down and create a reproducible test case. LSI Logic fixed the bug in their microcode after Apple split its version from the LSI Logic code tree to modify for use in the Xserve; don't expect this bug to ever be fixed because the product is EOL, only known workaround is to turn off the write caches.
That said, the disks are big. You think it's working flawlessly, but it may not be. Mystery garbage blocks from space, especially on a RAID, can be hard to track down. For example, on a RAID 1, the read data might not always come from the same disk of the mirror.
If you really think that the mirror is good, I'd suggest cloning it off while booted from another disk (perhaps split the mirror, clone - not image - to one of the split disks, then recreate the mirror from the good copy).
Yea, your DiskWarrior issue is because the disk can't be unmounted.
Russ
Xserve G5 2.0 GHz 2 GB RAM Mac OS X (10.4.8) Apple Hardware RAID, ATTO UL4D, Exabyte VXA-2 1x10 1u

Solved! KDE Device Notifier Never Activates

Sorry for the Newbie question. I'm an old Gentoo user, but new to Arch.
I want KDE to present me with a device notifier pop-up whenever I insert a USB disk. I don't want to automatically mount the device, but I do want to get a notification so that I can mount if if desired.
Currently, dmesg sees the USB disk, and I can manually mount the USB device, but KDE never seems to know the new device is present.
Do I therefore still need to follow the instructions in the udev wiki about auto-mounting?
(https://wiki.archlinux.org/index.php/Ud … SB_devices)
Is there some other setting that I may have missed?
Any suggestions would be greatly appreciated!
Last edited by NerdWorld (2012-03-25 15:49:59)

NerdWorld wrote:
I agree, it *should* work out of the box (it always did in Gentoo and Debian).
I figured that maybe Arch just required more configuration than those "other leading brands" of Linux. Of course, I'm just not sure what extra configuration I'm missing <sigh>
Welcome to Arch. How are you starting KDE and could you post the daemons from your rc.conf? I'm running KDE and the device notifier does pop up when inserting a USB or any other device. Are you also saying that it doesn't auto-mount also?
Here's my daemons list, FWIW.
DAEMONS=(syslog-ng ntpd dbus networkmanager cupsd avahi-daemon crond kdm)

KDE Device notifier detects two cameras

I have a DSLR camera which I connect through usb to my computer. The device notifier pops up but it displays two cameras along with their actions.
$ solid-hardware listen
Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QString)
Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QString)
Listening to add/remove events:
Device Added:
udi = '/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:1d.7/usb8/8-1'
Device Added:
udi = '/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:1d.7/usb8/8-1/8-1:1.0'
If I click on one of the two cameras and try to download photos with digikam I get this message
The specified camera ("/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:1d.7/usb8/8-1/8-1:1.0") is not supported.
If I click the other camera digikam starts correctly.
These are the groups my user belongs to
$ groups
lp wheel video audio optical storage scanner users vboxusers axel
A while ago it worked correctly. Any ideas how to solve this?

Whell, as I said in my message, whith --monitor command I have no response. I plugged in and out several times and 2 o 3 pendrives.
Yes, I have dbus in my DAEMONS array in rc.conf:
DAEMONS=(hwclock syslog-ng dbus cpufreq @network netfs @crond @alsa @cupsd)
and seems it's working:
# /etc/rc.d/dbus start
:: Starting D-BUS system messagebus [BUSY]
Failed to start message bus: The pid file "/run/dbus/pid" exists, if the message bus is not running, remove this file [FAIL]
[root@linux manc0ntr0]# /etc/rc.d/dbus restart
:: Stopping D-BUS system messagebus [DONE]
:: Starting D-BUS system messagebus [DONE
My KDE starts trough /etc/inittab as is explained in wiki:
x:5:respawn:/usr/bin/kdm -nodaemon
As mann138 said, my system recognizes all pendrives but Device Notification doesn't.
I can mount them and automount rule works perfect, but no notifications.
Thanks

[KDE] Device Icons Gone

I've been using arch with kde for some time and recently I enabled the testing repo (I know it was stupid) because compiz fusion no longer worked without it. Ever since then (at least I think that's what caused it, I don't use my pen drive much) the icons for pen drives and usb hard disks no longer appear on the desktop to allow me to easily mount them. Does anyone else have this problem and/or know a solution?
Thanks
rocktorrentz

try this:
http://docs.kde.org/userguide/multimedi … able-disks
You can also setup KDE to display a device icon on the desktop. To start or configure this feature in the KDE Control Center go to Desktop+Behavior and select the Device Icons Tab. The device icon action can be used to show both mounted and unmounted devices, or to only create an icon when media is detected and automounted (only if automount is properly configured), by not checking the unmounted boxes.

Cheap Camera Won't Unmount!

For my daughter's sixth birthday we bought her an inexpensive digital camera to introduce her to the world of photography.
The instructions that came with the driver download noted that when connecting the camera to a computer running Mac OS X, one can downlod the photos as normal but it will not be recognized as a mounted disc on the desktop.
Evere since I downloading the first batch of photos, iPhoto goes into its "Ready to Import" phase each time it's launched (though it recognizes there are no items to import). When restarting, Image Capture launches immediately and looks for items to download (though it recognizes there are none there). When the camera is connected, Disk Utility shows no volume for it, so I can't even try to mount/unmount. Frustrating.
Any idea how I can "reset" this phantom volume?
B.

Try changing the preference in Image Capture so that
it does not automatically open iPhoto when you
connect the camera. Then, instead of using iPhoto to
download the pictures use Image Capture to download
the pictures to the desktop or some other folder and
then open iPhoto and import the pictures in to it.
That may solve the issue.
This is already my current setup.
Interestingly enough, though, I delved into the Preferences/Options of Image Capture and found the following in the Information window:
Device Module /System/Library/Image Capture/Devices/MyDSC_905C.app
Device Type camera
Remote NO
The item listed as the Device Module is the driver for the Hello Kitty camera. I tried removing it from the Devices file in the System Library but "The item MyDSC_905C.app cannnot be moved to the Trash because it is open."
This leads me to believe the camera driver has hijacked my Image Capture and iPhoto download controls. Any suggestions on how I can rid my Mac of this thing?

Disk images won't unmount/eject for admin user, DVDs & iDisk also affected

This problem started when I was on Tiger, and seemed to follow me onto Leopard.
It only affects me, the primary user on my Mac. *One other user on the computer; she also has admin level access and does not have any of these problems.*
Here's the deal:
*Once mounted, disk images won't eject/unmount.*
- Dragging to the trash can doesn't work. The eject icon appears, but nothing happens.
- Ctrl-click does not show Eject as an option when highlighting the mounted image.
- CMD-E doesn't work
- EJect doesn't appear as an option in the finder menu
- Clicking on the Eject button in the sidebar of the Finder window doesn't work.
- I've logged out, rebooted, repaired permission, and installed a new OS (clean install of 10.5, then did the import of my old user settings. Since I had the problem in Tiger, it's clear the problem followed me, but what the heck causes it?)
*The only way to unmount/eject a disk image is to use the Disk Utility Program.*
*DVDs also can only be ejected via Disk Utility*
The iDisk connection can only be killed by opening Activity Monitor and killing the webdavfs_agent process.
Would love some help. I've searched a lot and have a fair amount of folks with this problem, but no real solution.

That'll work; however, then the OP has to reset all of his preferences. Easier would be to log into the newly created admin account, backup the bad account's folder, delete the bad account, selecting the save data option (which is stored in /Users/Deleted Users/ as a disk image), recreate the bad account using the same username/password combo, log out and back into the recreated original account. Mount the saved data dmg file in /Users/Deleted Users/, open the /Library/Preferences/ folder from the saved data, open the current /Users/restored account/Library/Preferences/ folder, and slowly copy plist files from the saved data folder to the current one. Log out and back in to ensure there's no conflict and things still work correctly. Resolving these kinds of conflicts is a laborious process, but not as laborious as resetting preferences or even remembering what you set weeks, months, or years ago.

Kde 4.2 won't login after xorg-server-1.6.1.901-1 upgrade

I upgraded my system this afternoon, but when the upgrade completed all my window decorations were gone and plasma as down. I restarted kde from virtual console 1 and the login screen was brought up. Now when i go to login i get stuck in an endless loop. I type in my username and password, and then after a few seconds the login window reappears.
I checked /var/log/errors.log and there are a number of lines like this:
kdm_greet[3623]: Cannot open default user face
i then installed gdm which wouldn't log me in either, but gave an error along the lines of xclient doesn't exist
this error occured after installing xorg-server-1.6.1.901-1
any help would be appeciated as i can't use arch at all atm!

sorry, i forgot to mention it. I've tried both of those things and niether helped. Same problem. I also changed the permissions on the /tmp directory which removed another error message to the effect of: cannnot save user authorization,
oh and just fyi, my disk is not full, there is at least 5gb free on that partition, so thats not what was causing that error.

KDEmod (KDE) device notifier won't unmount devices

Similar Messages

Maybe you are looking for