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

Similar Messages

[SOLVED] KDE 4.5: Device Notifier does not show CDs anymore

During one of the last updates KDE's Device Notifier lost the ability to display CDs I put into my CD drives. USB sticks do show up correctly. DBUS and HAL are running, the device Manager is configured to show up all removable medias. I can manually mount the CDs by using the mount command. Also if I connect the drive to my virtualbox XP installation they autoplay correctly. So this is no hardware failure.
I just want to put a CD in and the device manager should pop up and inform me of the actions that are possible. KDE 4.4 did this, KDE 4.5 does not. I am using the testing repo and my system is up-to-date.
Any advice?
Harvey
Last edited by Harey (2010-10-22 07:41:47)

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

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)

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.

[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 *

SOLVED: Mounting IDE ZIP Drives, "Special Device hdb4 Does Not Exist"

I thought I would post a follow-up, since I have finally resolved this long standing issue, which has plagued me since my first days with Linux many years ago.
As outlined in my original post below, every time I would attempt to access a Zip disk for the first time since boot, Linux (pretty much all distros I have ever tried, with the exception of SuSE 9.3) would fail to mount the disk and report back that "Special device hdb4 does not exist". Of course the "hdb4" part varies from distro to distro and machine to machine, depending on how your Zip disk is connected and how the distro names its disks, but the basic error has been constant. I have always worked around it by redoing the mount command specifying just the device, not the partition, and while that would always fail, it would force the creation of the device /dev/hdb4, and I could carry on. Annoying but effective.
FINALLY, a long term answer. I got my inspiration from a really snarky post I read in another online forum where someone had posted this very same question (this is a very common problem with no common answer it seems!). The respondant, who completely failed to provide a helpful answer, basically said "listen, the OS is telling you what is wrong - the device hdb4 doesn't exist - so fix it, and all will be just fine". Of course, the respondant didn't even bother to offer a suggestion about HOW to fix it.
However, therein lies the inspiration for the solution. Indeed they are right, /dev/hdb4 *doesn't* exist, so how to fix that? They had a point. I started researching the mysteries of mknod, a program that can create /dev files, and the even deeper mysteries of Linux device numbers, both major and minor.
In the end, I found a wonderfully informative document that described the current standard for the device numbering scheme used by mknod, and Linux in general. The key things of interest are this:
1/ The major number for IDE based drives is 3.
2/ IDE allows for 64 partitions per device, so the minor numbers are 0-63 for device "a", 64-127 for device "b" and so on. You derive the minor number of interest for your particular device by taking the starting value of the minor number range of interest for your device and adding the partition number to it. So, for example, hdb4 would have a minor number of 64 (the start of the minor number range for device "b") plus 4 (the partition number in "hdb4"), yielding a result of 68.
3/ The major number for SCSI based drives, or those that your OS treats as SCSI, is 8.
4/ SCSI allows for 16 partitions per device, so the minor numbers are 0-15 for device "a", 16-31 for device "b" and so on. You derive the minor number of interest for your particular device by taking the starting value of the minor number range of interest for your device and adding the partition number to it. So, for example, sdb4 would have a minor number of 16 (the start of the minor number range for device "b") plus 4 (the partition number in "hdb4"), yielding a result of 20.
In my case, Arch seems to be treating all of my disk based devices as SCSI, perhaps because I do have a real SCSI interfaced Jaz drive in my machine. So, the Zip disk of interest in my machine is sdc4 (my real SCSI jaz is sda, my Arch root is sdb, and the IDE Zip is sdc). Applying the above, for /dev/sdc4:
- The major number is 8.
- The minor number is 32 (start of range for device "c") plus 4 (the partition number) = 36.
Armed with this knowledge, I su'd to root and entered:
# mknod /dev/sdc4 b 8 36
and like magic, there is was, /dev/sdc4. I popped a disk into the drive and my first attempt to access it was greeted with success, not the usual "device does not exist" error! By the way, the "b" in the above command is just part of the mknod syntax, and indicates that I am creating a block device (vs. a character device, or some other type of device - disk drives all seem to be "block" devices for apparent reasons).
SO, determine your major number by device type (it will usually be 3 or 8), compute your minor number by device letter and partition number, and add a mknod command to your system startup (so you don't have to do it manually every time) and you are done! No more annoying "device does not exist" errors.
Now for the kicker. It turns out that this information has been available under my nose all along. I just didn't recognize the code. If you do the following:
# ls -ald /dev/sd*
Linux obligingly provides you with the major number and the start of the minor number range for your device. Since Linux has always detected the Zip *device* (just not the partition) this is really all you need to know. When I issue the above command, I get an output like:
brw-rw---- 1 root disk 8, 32 date time /dev/sdc
Guess what, there they are! "8" is the major number of interest, "32" is the start of the minor number range of interest. If I had just recognized that, and known that all I had to do was add the partition number to the minor number to get the magic number to feed into mknod, things would have been easier.
Sorry for the long post, but like so many things in Linux, the OS doesn't make this easy on the uninitiated. I sincerely hope that this post may help lots of other people to resolve this vexing and longstanding problem.

Solved!
See the lengthy response in this post:
http://bbs.archlinux.org/viewtopic.php?id=36468
I posted the solution separately, with the most informative title I could come up with, so that others Googling this topic on the web may hopefully easily find it.

The device option does not appear when i plug in my itouch

the device option does not appear on my itouch or ipod when it is plugged in

If you have iTunes 11 turn on the Sidebar. Go to iTunes>View and click on Show Sidebar. You can also do a Crtl+S to show the sidebar. The sidebar is where Devices appears. and Control+B to show the Menu bar
Next try:
iOS: Device not recognized in iTunes for Windows

WVC210 Device manger does not detect camera driver

Hi, Iam doing a java application project which captures a vedio from linksys wvc210 network camera, the problem is the device manager does not detect the camera as one of the imaging devices or as any, and so the jmf registry editor does not also detect the camera in which i am stuck on how to make java detect it and work on it which is impossible without being detected with the jmf registry so i need windows first to detect it at the device manager which will lead jmf registry editor to also detect it.
note that: the camera installation worked properly and i can access it normally. by the way iam using windows vista.
any help please...

First of all, thanks for ur reply, i will state the problem again: iam doing a java api application using the java media framework (JMF), the application goal is to capture a vedio from the ip camera, the application is done and works with my web cam which is detected by the java capture device manager, on the other hand the capture device manager does not detect the ip camera as one of the captured device in which i can't run my application on it. So the easiet way is to make windows detect it as one of the devices at the device manager so java capture device manager can detect it and my application will work immediatly. any suggestions ?

Update was terminated - Class PO - Number 366 - Device ARCH does not exist

Dear Gurus,
We are using Automatic PO generation through ME59, we also applied one SAP note to pick the custom document type through ME59 (normally the system pick NB as standard document)
In MN05 - if i set as default output type 1 - print ( then the document is generating with the correct document with correct number range)
But if i set in MN05 - default output as 2 - fax ( then i am getting this Update was terminated - Class PO - Number 366 - Device ARCH does not exist).
Please advice
Regards
RS

Dear Friend,
Output determination for fax is not done properly. check the device connnectivity.
SPRo>>Maintain Message type of PO
For the particular document type - i have removed the default PO Print out settings - now its working fine. Is this the right way?
Please advice
RS

Device type does not support page format

Hi All,
There is one issue when I print a sapscript. I get an error message as follows:
Device type EPESCP9 does not support page format ZSG02
Could someone advise?
Thanks
Alice

Hi,
The page format ZSG02 is not present in Device type EPESCP9.
in SPAD t.code add the page format in that device type.
Better inform to BASIS people they will add page format in that device type.
Refer the link Device type does not support page format
Regards,
Dhina..

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?

Bringing up interface eth0: e1000 device eth0 does not seem to be present, delaying initialization.

I performed a software reboot on the MSE3310. After the reboot the MSE was no longer visible on the network. I went and consoled into the device and it was operational. I ran the msed stop and msed start commands. I got this message when it tried to load eth0
Bringing up interface eth0: e1000 device eth0 does not seem to be present, delaying initialization.
[FAILED]
Earlier in the day I had updgraded the firmware from 6.0 to 7.0.230.0.
Can I recover the eth0? Is this related to the firmware upgrade?
Thanks.
Jason

Tarik,
This procedure worked great! After adding the HWADDR parameter to the eth0 config file and rebooting the server, we are now able to access the server on the network again. Thank you very much for the quick reply!
Here is the procedure if others need this.
ifconfig -a showed the eth0 interface was renamed to _tmp462132856
[root@MSE-CPW-01 ~]# ifconfig -a
__tmp462132856 Link encap:Ethernet HWaddr 00:15:17:F1:4D:C7
          BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
          Interrupt:169 Memory:e8180000-e81a0000
eth1      Link encap:Ethernet HWaddr 00:15:17:F1:4D:C8
          BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Then issued
vi /etc/sysconfig/network-scripts/ifcfg-eth0
to edit the file and add the HWADDR=xx:xx:xx:xx:xx:xx
Then issued a 'shutdown -r now' to reboot the server
After a reboot, network connectivity was restored!
Thanks!
Brian

TS3253 Is my original iPad compatible with iHome DM12 wireless speaker. I am having trouble with pairing. The iPad sees the device but does not connect

Is my original iPad compatible with iHome iDM12 wireless speakers? I am having trouble pairing. iPad sees device but does not connect.

It should be it the iHome supports the bluetooth profiles that the iPod supports. See:
iOS: Supported Bluetooth profiles
Try resetting the iHome if it was previusly paired to another device.
Also see:
'iOS: Third-party Bluetooth headsets, headphones, and keyboards

HT4623 phone is locked with a passcode and I don't have the passode, it says connect to itunes, and itunes won't connect because it says to enter passcode on phone. The device also does not show in itunes so I can't restore

iphone 4s is disabled. It says connect to itunes. Itunes ays could not connect because phone is locked with a passcode and to enter passcode on iphone before it can be used with itunes, but I can't enter the passcode because 1) don't know it 2) it's disabled. The device also does not show up in itunes, so how can I restore the phone or unlock it?

Same answer as last time you asked the exact same question:
HT1430 Iphone 4s says disabled connect to itunes and itunes won't connect because phone locked with a passcode. I don't have the passcode to unlock the phone

Anyone who has had a webcam failure where the "device manager does not recognize the hardware"?

HP Pavilion dv7 running win 7 64 bit
Device manager does not recognize trueVision HD webcam. Tried all the suggestions on HP website, which eventually says it's a hardware failure. Has anyone had any resolution to this issue? I see the problem occurs across various platforms with varying resolutions to the problem.

Ha Ha. I'm replying to my own post!
Solution.... If your laptop does not recognize the built-in camera at all in the device manager and your warranty has expired or your willing to void your warranty. You can see if you have the same problem as I had. Gently pry the plastic frame around your camera and display screen apart you need to go at least half way down the sides. There is also some adhesive tape you will need to push to one side or the other. To the right of the camera there is a very small connector, it wont even look as if it is separated. Use a tweezer or small screwdriver to push the connector into the socket. This fixed my problem ...The next startup recognized the camera and has worked perfectly since. In my opinion (13yrs experience in reliability engineering semiconductor manufacturing) this is a manufacturing reliability issue either the socket cannot hold the connector in place or there is too much strain on the wiring to the connector. Good luck.

KDE Device Notifier does not autohide

Similar Messages

Maybe you are looking for