On 6/26/23 19:16, songbird wrote:
to...@tuxteam.de wrote:
...
Yikes. Those gnomies do love complexity. I know why our ways parted
long ago.
yes, among the many other assumptions. i'm afraid though
that some of these things creep into MATE in time. :(
You might try disabling gvfs-gphoto2-volume-monitor.service and see
what changes (possibly you can't access the camera at all, but who
knows).
disabling or masking. i do that along with a few other
things that i don't use or care about.
I swear, this place is haunted, Songbird. There are no wires hooking up
a back doorbell, I've checked, but at random times, usually at night,
the doorbell goes off with a single bong, waking me up just now. And its
done it for the 33 years I've been here. 4, or 5 times a year...
I've chmod -x both of the files named in a bugreport, so htop can't find
them runninng but to remove the locks, I might have to reboot, which
I've not done yet because it takes about 10 minutes to get my local
network running again. That takes most of that 10 minutes of retyping
my pw. All that suf runs as me, not root. It also takes around 10
sessions of dot sourceing what should be automatic with opening a
terminal but putting it in .bashrc doesn't work. Somebodies #@^&
paranoia....
In any case put pebbles along the way so you can find your way back.
Perhaps someone with more clue chimes in.
Me? I just tell the camera to present a file system, mount it (yes,
manually) on /mnt and do a rsync. It's so much easier than all this
ritual dances that it's not even funny.
I don't believe the camera has anything of that sort available.
yes. someone else downthread says to remove the gphoto2
package but that is useful, i just don't want it automatically
engaged until i specifically ask for it.
And even with that stuff disabled, I still get the popup from the
automounter or whatever it is when I turn the camera on.
Claims its from disks and devices in the popup, that goes away in about
1 second.
The camera shows up as a change in this "ls -R /dev |wc -w":
gene@coyote:~$ ls -R /dev |wc -w
836 (with it turned on)
gene@coyote:~$ ls -R /dev |wc -w
834 (with it turned off)
but I've scanned /dev/tty*
/dev/usb/*
/dev/disk/*
without finding any diff. what other subdir of /dev should I be checking?
Starting from the top of a /dev list, I find there is a /dev/char 7:69
that disappears when its turned off. What the heck does that tell us?
Looking at system-info in the gui menu, at usb devices, it comes and
goes on that screen but doesn't actually show its /dev/location. So
does my geiger counter but thats another story. Currently showing 13,
but it records the peak which I believe to be from the default voltage
setting on the tube being too high and I've not erased the history since
turning the voltage down 2%. I am a C.E.T. and I know how those work.
Plugged into a usb port to keep its li-ion battery charged, it shows up
in the edev output. But that not germain to this problem.
Does anybody else have a clue? How do I go about doing an ldlock?
gene@coyote:~$ lslock
bash: lslock: command not found
gene@coyote:~$ sudo lslock
[sudo] password for gene:
sudo: lslock: command not found
Take care and stay well, all.
songbird
.
Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/>
