* Anders <[email protected]> [11-19-17 14:17]: > På Sun, 19 Nov 2017 13:59:49 -0500 > Patrick Shanahan <[email protected]> skrev: > > * [email protected] <[email protected]> [11-19-17 > > 13:31]: > > > I'm also interested in the subsject > > > > > > On Sun, 19 Nov 2017 19:01:45 +0100 > > > Michael Rasmussen <[email protected]> wrote: > > > > > > >Possible solutions (I have never used tethering so I do not know > > > >whether my solutions are already implemented in DT): > > > >1) You should do a complete reset of tethering in DT > > > > > > How to do that? Turn off the camera? or something on the computer or > > > in DT? > > > > > > >... > > > > > > > >3) You should forcefully terminate the broken session in your OS > > > >before reconnecting your camera which should drop the device > > > >reference and notifying user land applications like DT about the > > > >termination > > > > > > How to do that? > > > > how about "kill <process-id>" > > Which process?
I don't "tether", no need and do not know what processes dt uses to attach to the camera. I would hazzard a guess gphoto. you might open dmesg and watch it's output. ps is the utility to look for the processID -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode ____________________________________________________________________________ darktable user mailing list to unsubscribe send a mail to [email protected]
