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

Similar Messages

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?

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 *

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)

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)

Pb detection two cameras GigE with MAX on the same pc

I installed on the same pc two GigE camera, each camera has its own interface card (IP), but only one camera in dtected with max.
sometimes cam0 and sometimes cam1.I have to carry out has each camera a fixed address IP but always only camera is detected.
my question is how to make the configuration to appear both camera at the same time with max.
I use the MAX version 5.3
NI IMAQDX 4.0
Think you very match for your help.
Hamd2015
Solved!
Go to Solution.

Hi Hamden,
Could we get a little more information about your setup as it will help narrow down the issue?
- What network interface cards (NIC) are you using?
- What cameras are you using?
- Are we running the cameras through a network or directly connecting them to the computer?
- Can we see each camera when plugged in individually?
- It sounds like you said that you are using a static IP address, but I wanted to confirm this.
- Can we see both NICs in Windows Device Manger?
Bill E. | Applications Engineer | National Instruments

[SOLVED] Device Notifier doesn't work in KDE 4.8.4

Hi.
I searched for this problem but can't find any solution that works for me.
Have been using Arch since years, but never had this problem.
I did a fresh install few days ago. I installed KDE, but only minimal packages to work. Everything seems work ok but Device Notifier doesn't work in any way. It doesn't detects USB nor CD/DVD, but system does and I can mount USB pendrive manually, for example, using pmount.
Any help will be appreciated.
Regards.
Last edited by manc0ntr0 (2012-07-19 22:04:31)

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

[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

Capturing two cameras using JMF

Hi,
I am trying to capture media from two Logitech USB cameras, but I am not able to do so. Detect Capture Devices lists only one camera.
Please let me know how can I get around with this problem.
- t_k_m

This is a known bug.... JMF sometimes doesn't detect the 2nd / multiple cameras. No easy workarounds.... The bug has been open since 2003, but there's no development or bug fixing on JMF anymore.
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4890873
regards,
Owen

Two cameras at the same time Lab view (NI MAX)

I have two similar Point Grey Firefly MV cameras. I need to use them simultaneously in LabVIEW, but NI MAX only detects one at the same time (the two cameras are detected properly separately). I think that NI MAX identifies both camera as the same camera, but I dont know how to change the name of one of those cameras, or maybe change the serial number. Also NI MAX gives the same serial number to both of them. I would apreciate your help
Thank you.

Hi Aurelio,
This is a commom issue for USB Cameras. Once IMAQdx calls the camera driver to acquire image, if the camera driver cannot acquire from 2 cameras, IMAQdx cannot acquire from 2 cameras too.
You can ask to camera vendor about how the camera driver works.
http://digital.ni.com/public.nsf/allkb/D13527D8471D5FC5862576A4006BD081?OpenDocument
Regards,
Abel Souza
Engenheiro de Aplicações
National Instruments Brasil

Two camera footage: one drop frame, one non-drop frame

We recently were delivered a batch of tapes for a two camera project that we're doing the post work on. The timecode was jammed to synch the two cameras. Unfortuantely, one of the cameras seems to be drop and the other non-drop. As a result, the tape that is showing as non-drop stops every couple of minutes for a timecode break in order to synch up with the jammed timecode.
The reality is that there is no break in footage in the sense that this footage was recorded as a real-time 30 minute presentation, but because timecode is being jammed, and because the tape was being recorded in non-drop frame, Final Cut cannot capture this footage in its entirety.
My only thought would be to capture through S-video out and place the footage on a timeline, and force the sequence timecode with the appropriate timecode.
Has anyone run into this issue before and know a better solution? Or if the above solution will work?

Update: Rather than S-Video, we're setting the FCP capture setting to non-controllable device. That will give it higher quality, and so far, that is capturing just fine without the breaks.

Why doesn't Photoshop Elements 13 detect my camera or a card in a card reader?

I hooked my camera directly to my computer and tried to import my pictures. I kept getting the message no device detected. I bought a card reader because I read on Canon's forum that should work. Using the card reader, I still get the message that no device is detected.

sarahf47615149 wrote:
The only place I can find it is in the control panel under printers and devices. It comes up as a mass storage device, but I can't figure out how to do anything with it.
Is that with it in the card reader?

Hp pavilion dv2910us No Bluetooth Device was detected.........

Hello........
My Hp pavilion dv2910us
after install windoas 7 when i try to install my bluetooth driver its say
No Bluetooth device was detected.............
i try SP38167 And SP46038 but same error ..............
what to do............. is it driver problem and device problem......?????
Thanks
manoranjan
waiting for great reply

Hi
Please press the Fn & Esc Button you will find the details of what i have asked you i needs the complete model number & Product number so i can check if the Bluetooth cam integrated on your unit.
Let us know how it goes!
"I work for HP."
****Click the (purple thumbs up icon in the lower right corner of a post) to say thanks****
****Please mark Accept As Solution if it solves your problem****
Regards
Manjunath

KDE Device notifier detects two cameras

Similar Messages

Maybe you are looking for