SUSE 10.0, KDE 3.5.2 level a. I got a new camera several weeks ago (Panasonic FZ30, if it matters). I end up rebooting a lot (more than Windows now) because so many (four or five) things automatically start up every time the camera is connected. There are a couple of camera-specific dialogs (DigiKam and something else), a couple of KDE Daemon windows - one that says "USB Mass Storage Interface" and shows a camera icon, and one that says "2.1G Removable Media" and shows USB thumbdrive or flash fob. Sometimes I can dismiss the ones that I don't want, OK the one that works (the USB Mass Storage Interface), and get a Konq window that lets me browse and transfer files from the camera to PC. Roughly three times out of four, however, several of the pop-up dialogs are just locked. Can't be OK'd, can't be Configured, can't be Cancelled. I end up killing stuff with KSysguard. If I want to connect the camera, I reboot and try again. Somehow, this seems to be sub-optimal behavior, though I could be wrong. By what part of the interface do I tell K-whatever to open only one dialog (one that will work) when I connect the camera? At least, how do I tell it to permit me to dismiss the ones that I don't want, without interlocking them all into uselessness? I'd prefer not to use Windows for the camera stuff. Thanks, Kevin
Why do you connect the camera to computer? It wastes your camera's battery & is unnecessary?? Use a card reader. -- Gracia...Cooleemee, NC Registered Linux user #263390 - SuSE 10 Pro My country, right or wrong. If right, to be kept right, if wrong, to be put right.
Gracia M. Littauer wrote:
That may be so - but there is indeed something wrong there. I hook up my camera fairly often to store pictures on my hard drive. with 9.3 and 10.0, I usually close the kde popup that appears when I plug in the camera, and start gtkam instead. I've never had any problem with anything freezing. On 10.1 I've been using gnome+xgl out of curiosity, and when I plug in the camera f-spot pops up and allows me to see all the pictures. As before, gtkam can also be used to examine or store the pictures and to delete them from the camera. elefino - Sounds like your camera issues are symptoms of a deeper problem with your setup. The fact that you *ever* had to reboot is a sure sign. since it's not something you'd normally do in linux. I wouldn't be surprised if there were some sort of kernel panic messages in the system logs. If you can see them in dmesg or /var/log/messages, that would provide some clues about what is happening. Alternatively, there could be error messages in .xession-errors, if it's a user-level issue. Speaking of which, suse 10.0 comes with kde 3.4.2 - where did the upgrade come from? Was there any problem with the camera on the original version of kde? j
Have you moved all the windows to look for a modal dialog that never made it to the top of the pile? This has occasionally happened to me and I thought all kinds of bad things. Of course, if this is what is happening some program is badly written and needs a bug fix anyway but it may mean you don't have to reboot all the time. Chuck On 5/21/06, J Sloan <joe@tmsusa.com> wrote:
On Sunday 21 May 2006 15:05, Chuck Davis wrote:
I moved the ones that I saw popping up, but I do normally keep 4 desktops going, so maybe I should have looked on all desktops. Here's a question: When there's a dialog open, one can usually right-click or find a menu option to configure it, but when an event causes several apps to try to run (or at least ask if they should be allowed to run) and those get frozen, how does one approach it from the other direction and configure (say): "At new USB device connect, launch just this app"? Or, how do you work from an event like USB device appears on the bus to find what apps are waiting to pounce on that event? Kevin
Why do you connect the camera to computer? It wastes your camera's battery & is unnecessary?? Use a card reader. -- Gracia...Cooleemee, NC Registered Linux user #263390 - SuSE 10 Pro My country, right or wrong. If right, to be kept right, if wrong, to be put right.
Gracia M. Littauer wrote:
That may be so - but there is indeed something wrong there. I hook up my camera fairly often to store pictures on my hard drive. with 9.3 and 10.0, I usually close the kde popup that appears when I plug in the camera, and start gtkam instead. I've never had any problem with anything freezing. On 10.1 I've been using gnome+xgl out of curiosity, and when I plug in the camera f-spot pops up and allows me to see all the pictures. As before, gtkam can also be used to examine or store the pictures and to delete them from the camera. elefino - Sounds like your camera issues are symptoms of a deeper problem with your setup. The fact that you *ever* had to reboot is a sure sign. since it's not something you'd normally do in linux. I wouldn't be surprised if there were some sort of kernel panic messages in the system logs. If you can see them in dmesg or /var/log/messages, that would provide some clues about what is happening. Alternatively, there could be error messages in .xession-errors, if it's a user-level issue. Speaking of which, suse 10.0 comes with kde 3.4.2 - where did the upgrade come from? Was there any problem with the camera on the original version of kde? j
Have you moved all the windows to look for a modal dialog that never made it to the top of the pile? This has occasionally happened to me and I thought all kinds of bad things. Of course, if this is what is happening some program is badly written and needs a bug fix anyway but it may mean you don't have to reboot all the time. Chuck On 5/21/06, J Sloan <joe@tmsusa.com> wrote:
On Sunday 21 May 2006 15:05, Chuck Davis wrote:
I moved the ones that I saw popping up, but I do normally keep 4 desktops going, so maybe I should have looked on all desktops. Here's a question: When there's a dialog open, one can usually right-click or find a menu option to configure it, but when an event causes several apps to try to run (or at least ask if they should be allowed to run) and those get frozen, how does one approach it from the other direction and configure (say): "At new USB device connect, launch just this app"? Or, how do you work from an event like USB device appears on the bus to find what apps are waiting to pounce on that event? Kevin
participants (4)
-
Chuck Davis
-
elefino
-
Gracia M. Littauer
-
J Sloan