This forum has been archived. All content is frozen. Please use KDE Discuss instead.

[SOLVED] Device notifier and usb/cd devices

Tags: None
(comma "," separated)
VulcanRidr
Registered Member
Posts
12
Karma
0
I'm having an issue with the device notifier. This box is a c2d/4GB with an nVidia 8600GT (running the nvidia drivers) running Debian/sid.

It was upgraded from kde 3.5.10 to kde 4.1.x and is currently running kde 4.2.2-2.

When I plug a USB device in to the hub (thumb drive, USB hard drive, mp3 player), it pops up a kde3-style dialog box stating "A new device has been detected...What would you like to do?" which gives me the options "open in Dolphin," "download pictures with digicam," or "do nothing."

However, I cannot do anything with this dialog box. I can't select any of the options, click Ok, Cancel, or even close the dialog using the kde close button. In order to get rid of the dialog, I have to log out and back in.

Initially, I thought it could be a problem with udev, but that didn't explain not being able to get rid of the dialog box.

Just now, I tried to burn a CD. I inserted a blank into the drive, and started k3b. The splash screen came up, and it went gray. I couldn't get rid of it either, not even with a pkill -9 k3b.

I was running kde 4.2.2-2 on Debian/sid on my laptop before I had to turn it in, and didn't have any problems.

Something it the device subsystem is not right, but I am not sure where to look. Does anyone have any suggestions?

TIA,
--vr
User avatar
Alec
Registered Member
Posts
565
Karma
1
OS
It sounds to me that some part of KDE 3.5 is still installed on your system, and it starts up with KDE4. Try looking through the list of packages and see if you can find anything with version 3.5.

By the way, have you tried killing the window by pressing Alt+Ctrl+Esc?


Get problems solved faster - get reply notifications through Jabber!
VulcanRidr
Registered Member
Posts
12
Karma
0
Alec wrote:It sounds to me that some part of KDE 3.5 is still installed on your system, and it starts up with KDE4. Try looking through the list of packages and see if you can find anything with version 3.5.

By the way, have you tried killing the window by pressing Alt+Ctrl+Esc?


Oof. There ar quite a few:

Code: Select all
dcoprss    4:3.5.10-3
kdebase-kio-plugins    4:3.5.10.dfsg.1-2
kdeeject    4:3.5.10.dfsg.1-2
kdelibs    4:3.5.10.dfsg.1-2
kdelibs-data    4:3.5.10.dfsg.1-2
kdelibs4c2a    4:3.5.10.dfsg.1-2
kdenetwork-kfile-plugins    4:3.5.10-3
kdeprint    4:3.5.10.dfsg.1-2
kdict    4:3.5.10-3
kedit    4:3.5.10-2
khelpcenter    4:4.0.0.really.3.5.10.dfsg.1-2
khexedit    4:3.5.10-2
kpager    4:3.5.10.dfsg.1-2
kpf    4:3.5.10-3
kregexpeditor    4:3.5.10-2
ksim    4:3.5.10-2
ksirc    4:3.5.10-3
ktalkd    4:3.5.10-3
kwifimanager    4:3.5.10-3
libkonq4    4:3.5.10.dfsg.1-2
librss1    4:3.5.10-3
libsmokeqt1    4:3.5.10-1
lisa    4:3.5.10-3


I did get rid of the kde3 games, but the ones above, I'm not sure what the repercussions are to the system, or what the kde4 replacement is. I'm going through apt-file to see what I can find.

--vr
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
KDE 4 now has support for a similar style dialog, so it may indeed be supplied by KDE 4. You will be able to tell in particular if it uses Oxygen Icons, looks like all your other KDE 4 applications, etc.

No idea why it locks up though. Sounds like Solid is having problems with some hardware, especially since K3b is having problems also ( is that the KDE 4 version? ). It sounds like they are waiting for I/O, which is one of the few ways to make an application "unkillable"


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
VulcanRidr
Registered Member
Posts
12
Karma
0
bcooksley wrote:KDE 4 now has support for a similar style dialog, so it may indeed be supplied by KDE 4. You will be able to tell in particular if it uses Oxygen Icons, looks like all your other KDE 4 applications, etc.


I never saw that dialog on the laptop, which was also running sid and kde 4.2.2. I'll admit, the laptop was upgraded to kde4 a couple of weeks before the desktop I am having issues with. Unfortunately, I was recently laid off and no longer have direct access to said laptop.

k3b is version 1.0.5-3+b1. I don't think 1.6.5 is in Debian yet.

No idea why it locks up though. Sounds like Solid is having problems with some hardware, especially since K3b is having problems also ( is that the KDE 4 version? ). It sounds like they are waiting for I/O, which is one of the few ways to make an application "unkillable"


The thing is that sound works fine. In fact, better than it ever did under aRts in kde3. All of my apps have sound. I have a tv capture card in the machine, and can get sound for that, for amaroK, everywhere I need it...Is there a way I can test for this condition?

I was still wondering about the rogue kde3 app that didn't get uninstalled as Alec suggested. I went through last night with Synaptic and removed some stuff, but I still see a few things that are installed that I was not sure were needed (for non-upgraded apps), like kdebase-kio-plugins, kdelibskdelibs4c2a, etc. I just hate doing this kind of selective surgery...I always seem to end up breaking something.

--vr
VulcanRidr
Registered Member
Posts
12
Karma
0
Alec wrote:By the way, have you tried killing the window by pressing Alt+Ctrl+Esc?


Ctrl+Alt+Esc does not work my case.
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
Try running the command "solid-hardware list" and see if it manages to complete also. You could also try running "lsof" aganist a process once it has frozen, which will tell you what I/O it is waiting for.
Code: Select all
lsof $(pidof )


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
VulcanRidr
Registered Member
Posts
12
Karma
0
bcooksley wrote:Try running the command "solid-hardware list" and see if it manages to complete also. You could also try running "lsof" aganist a process once it has frozen, which will tell you what I/O it is waiting for.
Code: Select all
lsof $(pidof )



solid-hardware completed just fine. I also took the liberty of doing you one better. I inserted a CD into the drive, then ran strace k3b. There were several pages of output, which I will save, but the last page or so is as follows:

Code: Select all
munmap(0xb8094000, 4096)                = 0
write(3, "\041\03\0\0\020\0\0\0\0\0\0\0l34534630027523If226357]|337302'341", 32) = 32
read(3, "\010\022\0\0\0", 8)         = 8
read(3, "3\0KDE\0\0\03\0002.0\0\0\0", 16) = 16
getsockopt(3, SOL_SOCKET, SO_PEERCRED, "!%\0\03503\0\03503\0\0", [12]) = 0
getuid32()                              = 1000
write(3, "121\0I\0\0\0\0\0\0\0", 12) = 12
write(3, "\0\0\0\0\0\0\0vDCOPServer\0\0\0\01\0\0\0\025regi"..., 53) = 53
write(3, "\0\0\020anonymous-30241\0", 20) = 20
read(3, "23\0\0028\0\0\0", 8)         = 8
read(3, "H\0\0\0", 4)                   = 4
read(3, "\0\0\0vDCOPServer\0\0\0\0\0\0\0\0tQCString\0"..., 56) = 56
write(3, "121\0Z\0\0\0H\0\0\0", 12)  = 12
write(3, "\0\0\020anonymous-30241\0\0\0\0vDCOPServ"..., 82) = 82
write(3, "\0\0\04k3b\0", 8)            = 8
read(3, "23\0\0024\0\0\0", 8)         = 8
read(3, "H\0\0\0", 4)                   = 4
read(3, "\0\0\0vDCOPServer\0\0\0\020anonymous-302"..., 52) = 52
write(3, "121\0f\0\0\02\0\0\0", 12) = 12
write(3, "\0\0\020anonymous-30241\0\0\0\04k3b\0\0\0\04"..., 58) = 58
write(3, "\0\0\024/home/storm/Desktop\0\0\0\01\0\0\0\0"..., 44) = 44
read(3,


--vr
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
It appears to be having problems communicating with the DCOP server, so you are using the KDE 3 version of K3b. Please ensure that it is running and its socket ( located in $HOME ) has correct permissions.


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
VulcanRidr
Registered Member
Posts
12
Karma
0
bcooksley wrote:It appears to be having problems communicating with the DCOP server, so you are using the KDE 3 version of K3b. Please ensure that it is running and its socket ( located in $HOME ) has correct permissions.


Okay. I looked, and I have the following:

Code: Select all
-rw-r--r-- 1 storm storm 56 2009-05-08 09:14 .DCOPserver_defiant__0
lrwxrwxrwx 1 storm storm 34 2009-05-07 22:12 .DCOPserver_defiant_:0 -> /home/storm/.DCOPserver_defiant__0
-rw-r--r-- 1 storm storm 56 2007-06-13 08:05 .DCOPserver_defiant_unix_1009
lrwxrwxrwx 1 storm storm 41 2008-05-12 12:46 .DCOPserver_defiant_unix:1009 -> /home/storm/.DCOPserver_defiant_unix_1009
-rw-r--r-- 1 storm storm 56 2007-06-27 08:00 .DCOPserver_defiant_unix_1011
lrwxrwxrwx 1 storm storm 41 2008-05-12 12:46 .DCOPserver_defiant_unix:1011 -> /home/storm/.DCOPserver_defiant_unix_1011
-rw-r--r-- 1 storm storm 56 2007-07-12 13:20 .DCOPserver_defiant_unix_1016
lrwxrwxrwx 1 storm storm 41 2008-05-12 12:46 .DCOPserver_defiant_unix:1016 -> /home/storm/.DCOPserver_defiant_unix_1016


Now will getting rid of the .DCOPserver_defiant_10* files help? How do I fix it once and for all? I've done a little digging around, and found that /usr/bin/dcop belongs to the kdelibs4c2a package, which is version 3.5.10.

So it appears you are correct that DCOP/DBUS is still running from kde3. What packages do I need to delete from the system from kde3 and what do I need to [re]install from kde4 to get this where it needs to be?

Thanks,
--vr
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
Since k3b for KDE 4 is still not released, you will need to keep KDE 3 so you can use k3b.
Removing the DCOPServer sockets will cause it to generate new correct ones, which will hopefully stop the problem.


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
VulcanRidr
Registered Member
Posts
12
Karma
0
bcooksley wrote:Since k3b for KDE 4 is still not released, you will need to keep KDE 3 so you can use k3b.
Removing the DCOPServer sockets will cause it to generate new correct ones, which will hopefully stop the problem.


I trued connecting my iRiver H10 after deleting the .DCOPserver sockets, and still get the same problem. I checked the processes, and found the last few items in the list were:

Code: Select all
storm    25729  0.0  0.0   8032  2400 ?        S    May08   0:00 /usr/lib/gvfs/gvfs-hal-volume-monitor
storm    25731  0.0  0.0   5624  1668 ?        S    May08   0:00 /usr/lib/gvfs/gvfsd-burn --spawner :1.34 /org/gtk/gvfs/exec_spaw/0
storm    25735  0.0  0.0   8416  2016 ?        S    May08   0:00 /usr/lib/gvfs/gvfs-gphoto2-volume-monitor


which I killed, but I still can't get rid of the dialog box, nor can use it to mount the device. I'm grasping at straws here, but could it be a problem with hal?

--vr
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
It could possibly be a problem with HAL, although solid-hardware should have problems as well if that was the case. It seems very unusual to have GNOME desktop components launching in a KDE session, please ensure that there are no GNOME applications being autostarted.


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
VulcanRidr
Registered Member
Posts
12
Karma
0
bcooksley wrote:It could possibly be a problem with HAL, although solid-hardware should have problems as well if that was the case. It seems very unusual to have GNOME desktop components launching in a KDE session, please ensure that there are no GNOME applications being autostarted.


The apps I have Autostarted are several screenlets, fusion-icon and tilda (similar to yakuake).

The recurring startup apps gnome-terminal and kontact. (Firefox has stopped autostarting).

I have always preferred KDE over Gnome, but got in the habit of using some of the Gnome apps (like the terminal).

--vr
VulcanRidr
Registered Member
Posts
12
Karma
0
Well, I made some headway. I created a new user and logged in and was able to mount and dismount to my heart's content. Which means that the problem, unless I am mistaken, is in the .kde directory. Is there a way to surgically alter this directory or should I move it out of the way, let the system recreate it then cherry pick thte folders I need from the old .kde directory?

--vr


Bookmarks



Who is online

Registered users: bartoloni, Bing [Bot], Evergrowing, Google [Bot], q.ignora