Re: Screenshot with Gnome

[Curt]

On 2022-07-26, Richmond  wrote:
> Curt  writes:
>
>> On 2022-07-26, Greg Wooledge  wrote:
>>> On Tue, Jul 26, 2022 at 05:03:09PM +0300, Antti Talsta wrote:
 On Tue, Jul 26, 2022 at 12:40:53PM +0100, Richmond wrote:
 > I am trying to take a screenshot of a selected area.
 > I think something is broken. Maybe there is another utility?
 
 scrot
>>>
>>> I second this.  scrot is what I use for screenshots, either full or
>>> partial.  (Note: I don't use GNOME.  Just fvwm.)
>>>
>>>
>>
>> For a brief, but horrible second I thought it was an expletive.
>
> So did I. But I tried it and it didn't quite work. I've now found out
> that my menu item is actually calling xfce4-screenshooter so that's
> probably why it doesn't work, and this works:
>
> gnome-screenshot -i
>
>

I've Imagemagick installed, so

 import image.png

from a terminal works (though it seems you're confined to the active
window).

Re: Screenshot with Gnome

[Nicolas George]

Curt (12022-07-27):
> I've Imagemagick installed, so
> 
>  import image.png

This is my go-to solution too. Except when I want to capture the mouse
pointer too, in this case I use “ffmpeg -f x11grab”.

I would advise to add -depth 8; otherwise the PNG needlessly uses 16
bits per component.

> from a terminal works (though it seems you're confined to the active
> window).

import immediately makes a server grab to capture the mouse and let you
click on the window you want to import. If you need a few seconds to
focus the window you want to capture:

sleep 2; import -depth 8 image.png

Regards,

-- 
  Nicolas George


signature.asc
Description: PGP signature

Re: *Now* what is starting ssh-agent?

[Michael Biebl]

Can you post the output of
systemd-cgls


OpenPGP_signature
Description: OpenPGP digital signature

Re: Screenshot with Gnome

[Curt]

On 2022-07-27, Nicolas George  wrote:
>
> Curt (12022-07-27):
>> I've Imagemagick installed, so

>>  import image.png
>
> This is my go-to solution too. Except when I want to capture the mouse
> pointer too, in this case I use =E2=80=9Cffmpeg -f x11grab=E2=80=9D.
>
> I would advise to add -depth 8; otherwise the PNG needlessly uses 16
> bits per component.

>> from a terminal works (though it seems you're confined to the active
>> window).
>
> import immediately makes a server grab to capture the mouse and let you
> click on the window you want to import. If you need a few seconds to
> focus the window you want to capture:
>
> sleep 2; import -depth 8 image.png

Seems obvious, but I would've never thought of that. Thanks.

> Regards,
>

>   Nicolas George
>


-- 

Re: *Now* what is starting ssh-agent?

[Chris Mitchell]

On Tue, 26 Jul 2022 21:54:18 +0200
Erwan David  wrote:

> ssh-agent is usually started by your session manager. I do not know 
> wether all DE use this, but you can find it in
> 
> /etc/X11/Xsession.d/90x11-common_ssh-agent

True. The snippet in that file is nested in a conditional, though:
  if has_option use-ssh-agent; then
  …

If I'm not mistaken, disabling "use_ssh_agent" in
/etc/X11/Xsession.options causes that conditional to fail, so
/etc/X11/Xsession.d/90x11-common_ssh-agent will do nothing.

man Xsession(5) uses the wording "If the line ‘use-ssh-agent’ is
present in Xsession.options", but man Xsession.options(5) says "All  of
the  above options are enabled by default" and instructs to disable
them by prefixing the option with "no-". Prior experience suggests that
commenting the line out *is* sufficient to disable it, but just to be
sure I have uncommented the line and changed it to "no-use-ssh-agent".
Even after a reboot, this has made no difference to the situation.

$ grep -i ssh ~/.xsession-errors returns no results, and that file
*does* have entries showing other environment variables being set via
dbus-update-activation-environment.

I suppose I could try commenting out the whole snippet in
/etc/X11/Xsession.d/90x11-common_ssh-agent, or moving the file away, but
at this point I'm reasonably confident Xsession is not the culprit.

Thanks for the lead, though. I know a bit more about how Xsession works
now than I did yesterday.

Cheers!
 -Chris

Re: Screenshot with Gnome

[rudu]

Le 27/07/2022 à 08:49, Thiemo Kellner a écrit :
My favorite is flameshot for its capabilities for annotation, marking 
and such.




+1

Re: Screenshot with Gnome

[Peter Ehlert]

On 7/26/22 04:40, Richmond wrote:

I am trying to take a screenshot of a selected area. The Wiki here:

https://wiki.debian.org/ScreenShots

I find it curious that only Gnome, Xfce, and KDE are listed on that page...
someone should step up and flesh it out for the other common desktops, 
Please!


says I can use "take screenshot" from the menu. On my menu I have
"screenshot" but it doesn't work (although I think it used to) it just
displays a tiny box which I cannot make larger.

Assuming the command line is:

gnome-screenshot -a -d 20

I tried this but the mouse pointer immediately changes to a cross and I
cannot change tasks, so all I can do is photo the terminal window.

I think something is broken. Maybe there is another utility?


I use the Mate desktop. "mate-screenshot" works great for me.
However I am surprised that it appears to only be bundled in the 
mate-utils-common and mate-utils packages.

perhaps you might like the other utilities that are included.

Re: *Now* what is starting ssh-agent?

[tomas]

On Wed, Jul 27, 2022 at 09:08:59AM -0300, Chris Mitchell wrote:
> On Tue, 26 Jul 2022 21:54:18 +0200
> Erwan David  wrote:
> 
> > ssh-agent is usually started by your session manager. I do not know 
> > wether all DE use this, but you can find it in
> > 
> > /etc/X11/Xsession.d/90x11-common_ssh-agent
> 
> True. The snippet in that file is nested in a conditional, though:
>   if has_option use-ssh-agent; then
>   …
> 
> If I'm not mistaken, disabling "use_ssh_agent" in
> /etc/X11/Xsession.options causes that conditional to fail, so
> /etc/X11/Xsession.d/90x11-common_ssh-agent will do nothing.
> 
> man Xsession(5) uses the wording "If the line ‘use-ssh-agent’ is
> present in Xsession.options", but man Xsession.options(5) says "All  of
> the  above options are enabled by default" and instructs to disable
> them by prefixing the option with "no-". Prior experience suggests that
> commenting the line out *is* sufficient to disable it,

It isn't, see below.

>but just to be
> sure I have uncommented the line and changed it to "no-use-ssh-agent".
> Even after a reboot, this has made no difference to the situation.

I think it doesn't work as you think it does. Obviously, has_option
is a shell function. It is defined in /etc/X11/Xsession:

  has_option() {
# Ensure that a later no-foo overrides an earlier foo
if [ "$(echo "$OPTIONS" | grep -Eo "^(no-)?$1\>" | tail -n 1)" = "$1" ]; 
then
  return 0
else
  return 1
fi
  }

Why prefixing things with `no-' doesn't help you I can't say either.
Since this is all shell script, I'd insert some code in your
90x11-common_ssh-agent to clarify the situation. E.g. some little
thing echoing hello to some file in /tmp at strategic places.

Then you know whether to continue chasing that one or looking elsewhere.

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: *Now* what is starting ssh-agent?

[Greg Wooledge]

On Wed, Jul 27, 2022 at 09:08:59AM -0300, Chris Mitchell wrote:
> On Tue, 26 Jul 2022 21:54:18 +0200
> Erwan David  wrote:
> 
> > ssh-agent is usually started by your session manager. I do not know 
> > wether all DE use this, but you can find it in
> > 
> > /etc/X11/Xsession.d/90x11-common_ssh-agent
> 
> True. The snippet in that file is nested in a conditional, though:
>   if has_option use-ssh-agent; then
>   …
> 
> If I'm not mistaken, disabling "use_ssh_agent" in
> /etc/X11/Xsession.options causes that conditional to fail, so
> /etc/X11/Xsession.d/90x11-common_ssh-agent will do nothing.

That all sounds correct, and matches up with your earlier message stating
that ssh-agent is a direct child of systemd PID 1.  It's not being started
by Xsession.

We really need to see the systemd diagnostics that have been requested
by multiple people, now.

Re: *Now* what is starting ssh-agent?

[Chris Mitchell]

Jul. 26, 2022 17:00:46 Greg Wooledge :

> On Tue, Jul 26, 2022 at 03:40:48PM -0300, Chris Mitchell wrote:
>> Here's my service file:
>>
>> $ cat /etc/systemd/user/ssh-agent.service
>
> According to systemd.unit(5) this directory is for "User units created
> by the administrator".

Yup, that's me!
In practice, it means units placed there are user units that are
available to all users on the system, so they can
start/stop/enable/disable/… their own instances of those units via
"systemctl --user" commands (or root can do the same for all users at
once with "systemctl --global). A unit in this directory will supersede
a same-named unit in /usr/lib/systemd/user, and may in turn be
superseded on a user-by-user basis via their respective
~/.config/systemd/user directories.

> PID 1 is the system instance of systemd.  Not a user instance.
> The ssh-agent with PID 3011 is being started by the system instance,
> so it is a system unit.  It's not your locally defined user unit.

Oh, yes. I should have realized that. Weird that the system instance
would be configured to start an ssh-agent at all, but I'll definitely
look there next.

> Things you should look at next, I suppose:
>
> systemctl status ssh-agent
> systemctl --user status ssh-agent

The --user one shows that my custom "global" user unit at
/etc/systemd/user is up and running as expected, which I can verify by
manually changing SSH_AUTH_SOCK to point to the socket specified there
and accessing the agent. If the *system* systemd instance is actually
launching an ssh-agent and injecting corresponding env-vars into my
regular user environment, that is deeply strange, and I'm reasonably
sure I haven't done anything that could cause that outcome.

# systemctl status ssh-agent.service
  Unit ssh-agent.service could not be found.

# systemctl list-units --all *ssh*
  UNIT LOAD ACTIVE SUB DESCRIPTION
  0 loaded units listed.

> Starting an ssh-agent via systemd is completely outside of my
> experience, though, and I don't really understand why you'd attempt
> it.  It's not clear to me *at all* how you would communicate the
> environment variables from the ssh-agent invocation over to the
> user's login session.

My setup is to have each user's "user" systemd instance manage their
ssh-agent (which is also how the Bookworm package handles it, though
with some differences in the implementation details). Being a
long-running daemon type process that provides a service to other
processes, ssh-agent struck me as an ideal candidate for being handled
by the service manager. The only environment variable that remains
relevant now that systemd handles the process control stuff is
SSH_AUTH_SOCK, and because I specify a consistent socket location, I
can set that statically for all login sessions, the same way you would
go about adding a custom location to PATH or whatever.

Advantages include:
* hands-on learning experience with systemd, which is clearly here to
  stay,
* make ssh-agent start, and behave consistently, regardless of what DE
  I use, or no DE, or no X or Wayland or graphical anything,
* any user who has a non-zero number of active login sessions gets
  exactly one ssh-agent process, regardless of what "type" of session(s)

For example: if I log in to XFCE4, load a few ssh keys into my
ssh-agent, and something causes X to hang, I swap to VT1 and log in
there. Systemd no-ops my ssh-agent.service because it's already
running, and access to ssh-agent works right there in VT1, including the
already-loaded keys. Now I restart lightdm, which kills the session
that started my ssh-agent.service, but because I still have a non-zero
number of active login sessions (VT1), systemd keeps that service
running. Then I can swap back to the lightdm greeter and log in to
XFCE4, or KDE, or Enlightenment, or whatever, and my ssh-agent is
already up and ready with the keys I loaded earlier. Just for fun, if I
want to make ssh-agent socket-activated for every user on the system
instead of auto-started at login, I can drop a ~5 line ssh-agent.socket
file in /etc/systemd/user/ alongside the ssh-agent.service file,
systemctl --global disable the .service unit and enable the .socket
unit instead, and that's it.

I've been using this "global" systemd user unit to manage ssh-agent for
a couple of years now, and it's just about perfect… except when some
legacy workaround comes along and clobbers things.

Cheers!
 -Chris

Re: *Now* what is starting ssh-agent?

[Chris Mitchell]

On Wed, 27 Jul 2022 11:04:49 +0200
Michael Biebl  wrote:

> Can you post the output of
> systemd-cgls

First, for context:

$ systemd-cgls --user-unit ssh-agent.service 
Unit ssh-agent.service
(/user.slice/user-1000.slice/user@1000.service/app.slice> └─3166
/usr/bin/ssh-agent -D -a /run/user/1000/ssh-agent.socket

That is my custom "global" user ssh-agent.service, not the rogue
ssh-agent.

The rogue ssh-agent is also started:

$ env | grep -i ssh
SSH_AUTH_SOCK=/tmp/ssh-XX3Q3EAs/agent.3302
SSH_AGENT_PID=3303

The full output of
# systemd-cgls
is over 200 lines, and paste.debian.net rejected it with the message
"do not spam", so here we go:

https://pastebin.com/68wWRnyb

Cheers!
 -Chris

Re: Twice load - rndc.key ?

[Chris Mitchell]

On Mon, 11 Jul 2022 13:40:32 -0600
Charles Curley  wrote:

> On Mon, 11 Jul 2022 21:01:48 +0200
> Maurizio Caloro  wrote:

> > 
> > # cat /lib/systemd/system/named.service  
> 
> First mistake: you should not be editing files in /lib/systemd/.
> Instead copy the file to edit into /etc/systemd/, and edit it there. I
> believe there is a systemd command that will do that for you if
> necessary. The reason is that when an upgrade comes along, it will
> stomp on any changes you have made in /lib/systemd/.

If you want to supersede the entire unit file from /lib/systemd/ so
that no future package updates to that file will have any effect at
all, then yes. Copy the unit file to /etc/systemd/[system|user]/ as
appropriate and edit it. If you want to selectively override only
specific directives rather than supersede the unit completely, the easy
way is "systemctl edit ". That command automatically creates for
you an appropriately named ".d" drop-in directory below
/etc/systemd, creates a .conf file in the drop-in directory, and
launches an editor where you can define the directives you want.

Caveat: when using drop-in overrides, values you set are generally
*added* to whatever was set before. If you want to *replace* the value
of a particular directive, you have to explicitly set it to null first,
on a line by itself, like:
ExecStartPre=
...and *then* add a line setting it to whatever you want.

I got some very confusing results when overriding .timer files before I
learned that detail.

Cheers!
 -Chris

Re: Help: disk swap

[Jude DaShiell]

Have the running linux system on the machine.  Run lsblk to locate the
name of the boot partition.  Once you have the name run blkid and copy the
uuid for use in the end of /etc/fstab and put in the path to the boot
device, the disk format ext4, defaults,nofail 1 2 on an fstab entry.
Next, run update-grub and you should get a new boot entry in grub.  If you
boot the machine on the boot screen hit down-arrow followed by enter and
your other disk should boot up.
I got a new computer with no sata tray in it and have a sata caddy and
some older sata disks and that's how I got those to boot.  hth.

Re: Help: disk swap

[gene heskett]

On 7/27/22 08:02, tony wrote:

Hi,

I turned on my main home server after a few weeks absence,  and got
smoke from its power supply. Fortunately, I have a backup system, which
does work; both are running Debian 10, so I swapped use to that machine.
and am able to work with that, but some of the files and settings are a
bit out of date.

I decided to move the disk from the broken machine to the backup, but on
booting I'm dropped into a grub screen saying disk id  not
found. Not entirely surprising perhaps.

So, how do I get it to recognize, and boot from the old disK.

Cheers, Tony

.

name the disk partition, and use that "name" in the /etc/fstab to mount it.
You may have to rerun grub install too.

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 

Re: Help: disk swap

[David Christensen]

On 7/27/22 04:37, tony wrote:

Hi,

I turned on my main home server after a few weeks absence,  and got
smoke from its power supply. Fortunately, I have a backup system, which
does work; both are running Debian 10, so I swapped use to that machine.
and am able to work with that, but some of the files and settings are a
bit out of date.

I decided to move the disk from the broken machine to the backup, but on
booting I'm dropped into a grub screen saying disk id  not
found. Not entirely surprising perhaps.

So, how do I get it to recognize, and boot from the old disK.

Cheers, Tony



Please provide a hardware inventory for each computer.


For each disk drive, please describe the purpose of the drive.


Please tell us how each computer is booted, what services are provided, 
and what data is stored.



Prior to the disaster, please tell us about your disaster preparedness 
measures.  Were backups, archives, images, etc., up-to-date?



Since the disaster, where is your live data?  Have your disaster 
preparedness measures changed?  Are your backups, archives, images, 
etc., up-to-date?



Have you repaired the main home server?  When the power supply failed, 
did anything else fail?



Suggestions:

1.  Install Debian onto a high quality USB 3.0 flash drive, to use for 
maintenance and troubleshooting.


2.  Buy a hardware power supply tester.

3.  Buy external drive adapters corresponding to whatever internal 
drives you use -- so that you can remove internal drives, connect them 
to the adapters, and access them using another computer.


4.  Do not be afraid to "throw money at the problem" -- e.g. maintain an 
inventory of spare parts and computers.  The last time I lost data was 
when I decided not to buy big, new, backup HDD's for a data migration.



David

AW: Three unsolvable Problems PRINTER SELFCHECK

[Schwibinger Michael]

HP printers have aself check.

You push the button and there is a check page.

Regards
Thank You

Von: Charles Curley 
Gesendet: Dienstag, 26. Juli 2022 16:13
An: Debian Users 
Betreff: Re: Three unsolvable Problems PRINTER SELFCHECK

On Tue, 26 Jul 2022 14:19:25 +
Schwibinger Michael  wrote:

> What does this have to do
> with the selfcheck?

To what self-check are you referring?

--
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: Help: disk swap

[Felix Miata]

tony composed on 2022-07-27 12:37 (UTC+0100):

> I turned on my main home server after a few weeks absence,  and got
> smoke from its power supply. Fortunately, I have a backup system, which
> does work; both are running Debian 10, so I swapped use to that machine.
> and am able to work with that, but some of the files and settings are a
> bit out of date.

> I decided to move the disk from the broken machine to the backup, but on
> booting I'm dropped into a grub screen saying disk id  not
> found. Not entirely surprising perhaps.

> So, how do I get it to recognize, and boot from the old disK.

It could be as simple as striking the right key at POST. If you have two UEFI 
PCs
and the disks were installed in UEFI mode, you might be able to select the 
foreign
disk with a BBS key:

BBS Boot Keys

[*]ASRock   F11
[*]Asus F8
[*]Biostar  F9?
[*]Dell F12
[*]eCS  F10
[*]eMachinesF10
[*]EVGA F7
[*]Gigabyte F12
[*]HP   F9 or ESC or ESC,F9
[*]Lenovo   F12 or F8 or F10
[*]MSI  F11
[*]Toshiba  F12

If one PC was configured to use legacy mode while the other UEFI, you might need
to go into BIOS to enable the other mode.

There are all sorts of reasons possible for your predicament. David's reply 
covers
many ways to minimize or eliminate the inconvenience of a PC or disk failure, 
and
includes your providing information for helping us to help you.

One possible way to encounter your non-recognition situation is to add the other
disk rather than substituting. Swapping SATA cables between the two drives with
both installed at once might work around that issue.

The "name" Gene's reply refers to is called a volume label, easier for mere 
humans
to deal with than the UUIDs Grub uses by default, and referred to by Jude. Use
e2label or tune2fs to assign labels where they don't already exist on EXTn
filesystems. Volume labels are how I do all native Linux filesystem mounting and
booting, never UUIDs.
-- 
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata

Re: Help: disk swap

[Erik Mathis]

I would look at the UEFI vs BIOS boot options in the "backup" server and
compare it to the "broken" server and make sure they are the same. Also
check for BIOS updates and such.


-Erik-


On Wed, Jul 27, 2022 at 7:59 AM tony  wrote:

> Hi,
>
> I turned on my main home server after a few weeks absence,  and got
> smoke from its power supply. Fortunately, I have a backup system, which
> does work; both are running Debian 10, so I swapped use to that machine.
> and am able to work with that, but some of the files and settings are a
> bit out of date.
>
> I decided to move the disk from the broken machine to the backup, but on
> booting I'm dropped into a grub screen saying disk id  not
> found. Not entirely surprising perhaps.
>
> So, how do I get it to recognize, and boot from the old disK.
>
> Cheers, Tony
>
>

Re: Help: disk swap

[Charlie Gibbs]

On Wed Jul 27 10:30:05 2022 tony  wrote:

> I turned on my main home server after a few weeks absence,  and got
> smoke from its power supply. Fortunately, I have a backup system,
> which does work; both are running Debian 10, so I swapped use to that
> machine. and am able to work with that, but some of the files and
> settings are a bit out of date.
>
> I decided to move the disk from the broken machine to the backup, but
> on booting I'm dropped into a grub screen saying disk id 
> not found. Not entirely surprising perhaps.
>
> So, how do I get it to recognize, and boot from the old disK.

You might not be able to.  I once had a power supply fail
in such a way as to destroy the motherboard and the two
hard drives in the machine.  I lost about 180GB of stuff,
only some of which I was able to replace.  My backups are
_much_ better now.

Let's hope you're luckier than that.

--
/~\  Charlie Gibbs  |  Life is perverse.
\ /|  It can be beautiful -
 X   I'm really at ac.dekanfrus |  but it won't.
/ \  if you read it the right way.  |-- Lily Tomlin

Re: Three unsolvable Problems PRINTER SELFCHECK

[David Wright]

On Wed 27 Jul 2022 at 16:51:19 (+), Schwibinger Michael wrote:
> HP printers have a self check.

Yes, and sometimes several (printing, wireless, fax, etc).

> You push the button and there is a check page.

I don't think HP printers have a button that you can just press
and get a test page. Please give more details on the model name,
number, and approximate year of the printer. Does it use ink
or toner?

Cheers,
David.

Re: Three unsolvable Problems PRINTER SELFCHECK

[Brian]

On Wed 27 Jul 2022 at 14:04:55 -0500, David Wright wrote:

> On Wed 27 Jul 2022 at 16:51:19 (+), Schwibinger Michael wrote:
> > HP printers have a self check.
> 
> Yes, and sometimes several (printing, wireless, fax, etc).
> 
> > You push the button and there is a check page.
> 
> I don't think HP printers have a button that you can just press
> and get a test page. Please give more details on the model name,
> number, and approximate year of the printer. Does it use ink
> or toner?

It doesn't really matter whether they do or don't (mine does). Not
printing a self-test page has nothing do with the printing system
or Debian. It is a entirely a function of the printer itself.

-- 
Brian.

How do you mount a solid state drive? ...

[Albretch Mueller]

 I googled: "mount solid state drive" Linux, and I got very few hits
(like 16?) which were mostly totally irrelevant.
 I got a laptop with Windows installed on which I installed WSLg.
WIndows and WSLg both seem to detect the SSD just fine, but in ways
that are not totally clear to me.
 What I care about is using the SSD for my data intensive code in
Linux, but when I boot that computer with Debian live I can't see the
SSD.
 What could be going on?
 lbrtchx

Re: How do you mount a solid state drive? ...

[Albretch Mueller]

 https://wiki.debian.org/SSDOptimization
~

Re: How do you mount a solid state drive? ...

[Dan Ritter]

Albretch Mueller wrote: 
>  I got a laptop with Windows installed on which I installed WSLg.
> WIndows and WSLg both seem to detect the SSD just fine, but in ways
> that are not totally clear to me.
>  What I care about is using the SSD for my data intensive code in
> Linux, but when I boot that computer with Debian live I can't see the
> SSD.
>  What could be going on?

An SSD shows up as a disk. What's in /dev/disk/by-id/ ?


-dsr-

Virtualization anomalies

[paulf]

Folks:

I'm running an Intel Core i3, model 10100. According to Intel's spec
sheet on their site, this CPU has VT-x (virtualization) support. From
what I've read, this shows up in "lscpu" as the "vmx" flag. When I run
lscpu on this chip, that flag doesn't show up. As a result, I can't run
any of the virtualization options (virt-manager, etc.).

(As a point of reference, an older CPU I had in a different machine
(6th gen i5) *did* show this flag when I ran lscpu.)

I'd like to upgrade the CPU to a model which does support
virtualization. But I'm afraid I'll just end up with another chip which
Intel says works with virtualization, and lscpu says doesn't.

Can anyone explain this discrepancy, or provide insights?

Paul

-- 
Paul M. Foster
Personal Blog: http://noferblatz.com
Company Site: http://quillandmouse.com
Software Projects: https://gitlab.com/paulmfoster

Re: Virtualization anomalies

[Nicolas George]

pa...@quillandmouse.com (12022-07-27):
> Folks:
> 
> I'm running an Intel Core i3, model 10100. According to Intel's spec
> sheet on their site, this CPU has VT-x (virtualization) support. From
> what I've read, this shows up in "lscpu" as the "vmx" flag. When I run
> lscpu on this chip, that flag doesn't show up. As a result, I can't run
> any of the virtualization options (virt-manager, etc.).
> 
> (As a point of reference, an older CPU I had in a different machine
> (6th gen i5) *did* show this flag when I ran lscpu.)
> 
> I'd like to upgrade the CPU to a model which does support
> virtualization. But I'm afraid I'll just end up with another chip which
> Intel says works with virtualization, and lscpu says doesn't.
> 
> Can anyone explain this discrepancy, or provide insights?

Have you checked if virtualization is disabled in the setup? IIRC many
systems disable it by default because it is supposed to make rootkits
more dangerous or something.

Regards,

-- 
  Nicolas George


signature.asc
Description: PGP signature

Re: Three unsolvable Problems Printer II

[Gareth Evans]

> On 25 Jul 2022, at 13:03, Schwibinger Michael  wrote:
> 
> 
> Hello
> Ist the best way to repair
> the self check?
> 
> HP 600

Hi Sophie, please would you confirm the exact model - eg Deskjet 600, OfficeJet 
600, something else?

If you can't tell from looking at the machine, then running the command

lpinfo -v

in a terminal should tell you.

Thanks,
Gareth

Re: Virtualization anomalies

[paulf]

On Wed, 27 Jul 2022 23:17:33 +0200
Nicolas George  wrote:

> Have you checked if virtualization is disabled in the setup? IIRC many
> systems disable it by default because it is supposed to make rootkits
> more dangerous or something.

Can you clarify "in the setup"?

Paul

-- 
Paul M. Foster
Personal Blog: http://noferblatz.com
Company Site: http://quillandmouse.com
Software Projects: https://gitlab.com/paulmfoster

Re: Three unsolvable Problems Printer II

[Gareth Evans]

On Wed 27 Jul 2022, at 22:28, Gareth Evans  wrote:
>> On 25 Jul 2022, at 13:03, Schwibinger Michael  wrote:
>>  
>> Hello
>> Ist the best way to repair
>> the self check?
>> 
>> HP 600
> 
> Hi Sophie, please would you confirm the exact model - eg Deskjet 600, 
> OfficeJet 600, something else?
> 
> If you can't tell from looking at the machine, then running the command

> lpinfo -v

...that perhaps should have been...

sudo lpinfo -v

If you see an error about not being in the sudo group, then run the command

su -

and enter the root password, then run the command

lpinfo -v

again

Thanks,
Gareth

Re: No HDMI Audio

[Joel Roth]

On Sun, Jul 24, 2022 at 01:37:34PM -0400, Timothy M Butterworth wrote:
> All,
> 
> I am not getting any sound through HDMI. I have an AMD Ryzen 7 4700U CPU
> with integrated Renior Graphics. I checked the device and it is not muted.
> Does anyone have any ideas?
> 
> inxi -F
> Audio:Device-1: Advanced Micro Devices [AMD/ATI] driver: snd_hda_intel
>   Device-2: Advanced Micro Devices [AMD]
> Raven/Raven2/FireFlight/Renoir Audio Processor driver: snd_rn_pci_acp3x
>   Device-3: Advanced Micro Devices [AMD] Family 17h HD Audio driver:
> snd_hda_intel
>   Sound Server: ALSA v: k5.10.0-16-amd64
> 
> *aplay -l*
> card 0: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0]
>  Subdevices: 1/1
>  Subdevice #0: subdevice #0
> card 0: Generic [HD-Audio Generic], device 7: HDMI 1 [HDMI 1]
>  Subdevices: 1/1
>  Subdevice #0: subdevice #0
> card 1: Generic_1 [HD-Audio Generic], device 0: ALC287 Analog [ALC287
> Analog]
>  Subdevices: 1/1
>  Subdevice #0: subdevice #0
> 
> *lspci*
> 04:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Device 1637
> 04:00.5 Multimedia controller: Advanced Micro Devices, Inc. [AMD]
> Raven/Raven2/FireFlight/Renoir Audio Processor (rev 01)
> 04:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models
> 10h-1fh) HD Audio Controller

I would stop pulseaudio and test `aplay sample.wav`
using the device option to target various alsa devices.
Once you've found the HDMI device that works, you
can set it as the default device. 

-- 
Joel Roth

Re: Three unsolvable Problems Printer II

[Brian]

On Wed 27 Jul 2022 at 22:39:56 +0100, Gareth Evans wrote:

> On Wed 27 Jul 2022, at 22:28, Gareth Evans  wrote:
> >> On 25 Jul 2022, at 13:03, Schwibinger Michael  wrote:
> >>  
> >> Hello
> >> Ist the best way to repair
> >> the self check?
> >> 
> >> HP 600
> > 
> > Hi Sophie, please would you confirm the exact model - eg Deskjet 600, 
> > OfficeJet 600, something else?
> > 
> > If you can't tell from looking at the machine, then running the command
> 
> > lpinfo -v
> 
> ...that perhaps should have been...
> 
> sudo lpinfo -v

lpinfo is not in a user's path. Use /usr/sbin/lpinfo.

The main point is that self-checking is a printer function, not a
printing system function. The question does not have an answer within
Debian.

-- 
Brian.

Re: How do you mount a solid state drive? ...

[Jude DaShiell]

An easy way to locate an ssd is to have it unplugged from the system and
run lsblk and save that to a file then plug the ssd in and run lsblk again
saving its output to another file.  The line in the second file that's
missing from the first file is the ssd.


On Wed, 27 Jul 2022, Dan Ritter wrote:

> Albretch Mueller wrote:
> >  I got a laptop with Windows installed on which I installed WSLg.
> > WIndows and WSLg both seem to detect the SSD just fine, but in ways
> > that are not totally clear to me.
> >  What I care about is using the SSD for my data intensive code in
> > Linux, but when I boot that computer with Debian live I can't see the
> > SSD.
> >  What could be going on?
>
> An SSD shows up as a disk. What's in /dev/disk/by-id/ ?
>
>
> -dsr-
>
>

Re: Three unsolvable Problems Printer II

[Gareth Evans]

> On 27 Jul 2022, at 23:42, Brian  wrote:
> On Wed 27 Jul 2022 at 22:39:56 +0100, Gareth Evans wrote:
> 
>> On Wed 27 Jul 2022, at 22:28, Gareth Evans  wrote:
 On 25 Jul 2022, at 13:03, Schwibinger Michael  wrote:
 
 Hello
 Ist the best way to repair
 the self check?
 HP 600
>>> Hi Sophie, please would you confirm the exact model - eg Deskjet 600, 
>>> OfficeJet 600, something else?
>>> If you can't tell from looking at the machine, then running the command
>> 
>>> lpinfo -v
>> 
>> ...that perhaps should have been...
>> 
>> sudo lpinfo -v
> 
> lpinfo is not in a user's path. Use /usr/sbin/lpinfo.
> 
> The main point is that self-checking is a printer function, not a
> printing system function. The question does not have an answer within
> Debian.
> 

Hi Brian,

My understanding is that self-check (where available) and test page printing 
are distinct processes, which may have been conflated here to some extent.

I recall having a printer with self check capability where no feedback was 
reported (on windows, ages ago) if there were no problems.

No disagreement re the independence of self checking functionality, but the 
command still has to be properly transmitted to the right endpoint.  My printer 
doesn't have a self check facility so I can't explore if/how that works with a  
fax printer under different setup conditions.

If the printer concerned is an OfficeJet 600, that is fax capable according to 
hp docs

http://h10032.www1.hp.com/ctg/Manual/bpu60078.pdf

in which case, I think it's possible this  may be another case of the 
driverless+fax bug, where all jobs seem to end up in the outgoing fax queue and 
nothing prints, unless the queue was added via lpadmin. This does seem to be 
Bullseye-cups-related.

I don't know yet if this printer supports driverless printing, or if driverless 
printing is in use, but the lack of test page output alone doesn't seem to 
reliably indicate a hardware or external-to-Debian problem.

Just a thought, or three.

Best wishes,
Gareth

Re: Three unsolvable Problems Printer II

[Gareth Evans]

> On 28 Jul 2022, at 00:36, Gareth Evans  wrote:
> 
> [blah blah blah]

I would like Sophie to confirm the exact model so further checksg can be 
suggested if indicated.  There may be a solution of sorts.

Best wishes,
Gareth

Re: Virtualization anomalies

[David]

On Thu, 28 Jul 2022 at 07:35,  wrote:
> On Wed, 27 Jul 2022 23:17:33 +0200 Nicolas George  wrote:

> > Have you checked if virtualization is disabled in the setup? IIRC many
> > systems disable it by default because it is supposed to make rootkits
> > more dangerous or something.
>
> Can you clarify "in the setup"?

They're referring to the machine's hardware BIOS/UEFI configuration.
The very first thing you can access when powering up the machine.
Usually it offers: press some key to access some configuration menu.
Where there's often a facility to enable/disable the CPU virtualisation
feature.

gnome2/keyrings/login.keyring.temp-nnnnnnnnn

[Joe Pfeiffer]

I just noticed I have over a million files lurking in
$HOME/.gnome2/keyrings/ with names of the form
login.keyring.temp-n
where n is a nine digit number.

Literally over a million:
ls ~/.gnome2/keyrings/ | wc
1695549 1695549 50118672

>From the names, I assume these are temporary files that are being
created but not delete as they should be.  Is there an accepted way to
keep them from accumulating like this?

Re: Three unsolvable Problems Printer II

[Gareth Evans]

> On 28 Jul 2022, at 00:36, Gareth Evans  wrote:
> 
>>> [...] unless the [driverless] queue was added via lpadmin.

Just to correct the point, i keep forgetting, it seems even this fails with the 
latest cups version on Bullseye where fax printers are concerned.

Re: Virtualization anomalies

[paulf]

On Thu, 28 Jul 2022 09:41:51 +1000
David  wrote:

> On Thu, 28 Jul 2022 at 07:35,  wrote:
> > On Wed, 27 Jul 2022 23:17:33 +0200 Nicolas George 
> > wrote:
> 
> > > Have you checked if virtualization is disabled in the setup? IIRC
> > > many systems disable it by default because it is supposed to make
> > > rootkits more dangerous or something.
> >
> > Can you clarify "in the setup"?
> 
> They're referring to the machine's hardware BIOS/UEFI configuration.
> The very first thing you can access when powering up the machine.
> Usually it offers: press some key to access some configuration menu.
> Where there's often a facility to enable/disable the CPU
> virtualisation feature.
> 

Thanks for the clarification. I'll check.

Paul


-- 
Paul M. Foster
Personal Blog: http://noferblatz.com
Company Site: http://quillandmouse.com
Software Projects: https://gitlab.com/paulmfoster

Re: Three unsolvable Problems Printer II

[gene heskett]

On 7/27/22 20:25, Gareth Evans wrote:



On 28 Jul 2022, at 00:36, Gareth Evans  wrote:


[...] unless the [driverless] queue was added via lpadmin.

Just to correct the point, i keep forgetting, it seems even this fails with the 
latest cups version on Bullseye where fax printers are concerned.
.
I haven't forgotten. The driverless stuff DOES NOT work, and you cannot 
delete it until you un-install the cups-browser. You can delete it, and 
cups says its deleted, but in the 5 seconds it gives you to read the 
deleted msg,
cups-browser has recreated it again so its still there by the time you 
click on printers again.  And it blocks
the makers drivers which in the case of Brother, do everything  the 
printer is capable of.


Driverless might work with some of the recent $40 printers, but it is a 
long way from being ready for

prime time on a 5 yo $700 printer.


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 

Re: gnome2/keyrings/login.keyring.temp-nnnnnnnnn

[Charles Curley]

On Wed, 27 Jul 2022 17:50:42 -0600
Joe Pfeiffer  wrote:

> I just noticed I have over a million files lurking in
> $HOME/.gnome2/keyrings/ with names of the form
> login.keyring.temp-n

> Is there an accepted way to
> keep them from accumulating like this?

You can probably cobble something together for logrotate.


-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: Three unsolvable Problems Printer II

[Gareth Evans]

On Thu 28 Jul 2022, at 02:56, gene heskett  wrote:
> [...] The driverless stuff DOES NOT work [...]

Hi Gene,

The reports from you, myself and Hans (and the lack of complaints from 
non-fax-printer users) seem to suggest the problem affects only fax-capable 
printers.  This remains to be seen in Sophie's case, but I wait with interest.

The conversation seemed to drift towards a printer problem, but I think there 
are other possibilities, and barring that, I hope and imagine there are 
solutions for Sophie's printer as there have been for ours.

I do wish the upstream bug report would get some response, and that Debian 
would consider a cups update given that there are no such issues in Ubuntu's 
cups 2.4, though there's more to be considered of course.  I think it's a 
serious breakage that got worse in the recent Bullseye update.  If 
auto-detected/created queues used IPP Everywhere (which seems to work 
flawlessly) it wouldn't be such an issue, but it's a showstopper for 
inexperienced users, not to mention some more experienced ones!

Best wishes,
Gareth

Re: gnome2/keyrings/login.keyring.temp-nnnnnnnnn

[Joe Pfeiffer]

Charles Curley  writes:

> On Wed, 27 Jul 2022 17:50:42 -0600
> Joe Pfeiffer  wrote:
>
>> I just noticed I have over a million files lurking in
>> $HOME/.gnome2/keyrings/ with names of the form
>> login.keyring.temp-n
>
>> Is there an accepted way to
>> keep them from accumulating like this?
>
> You can probably cobble something together for logrotate.

With the number of gnome users out there there's got to be something
more standard than that.

Re: How do you mount a solid state drive? ...

[tomas]

On Wed, Jul 27, 2022 at 03:06:47PM -0500, Albretch Mueller wrote:
>  I googled: "mount solid state drive" Linux, and I got very few hits
> (like 16?) which were mostly totally irrelevant.

First of all, you don't mount a drive. You mount a file system.

This may sound like an unimportant nit to pick, but it actually
can get very confusing when there's more than one partition
(and thus potentially more than one file system) on that drive.

Then, from the system software side, there's no difference between
an SSD and a "traditional" hard disk. As far as you, the sysadmin,
are concerned, they both present themselves as block devices you
can partition, put file systems there, etc.

*If*

 (a) there is a file system on your drive (perhaps in a partition
in there)
 (b) your OS is set up in a way that it automatically recognises
it

then it'll probably somehow auto-mount that file system (that
may be helpful or not).

Now the question back to you: *what* are you trying to do?

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: How do you mount a solid state drive? ...

[tomas]

On Wed, Jul 27, 2022 at 06:54:32PM -0400, Jude DaShiell wrote:
> An easy way to locate an ssd is to have it unplugged from the system and
> run lsblk and save that to a file then plug the ssd in and run lsblk again
> saving its output to another file.  The line in the second file that's
> missing from the first file is the ssd.

Nice trick :)

To add one to the toolbox: do "tail -f /var/log/messages" while plugging
in the device: you'll watch your OS pondering on what to do about it.

Or do "dmesg | tail" right away after having plugged it in. In both cases
you'll see which name the device was registered with.

Both need root privilege, so "sudo" or "su" or whatever.

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: How do you mount a solid state drive? ...

[David Wright]

On Wed 27 Jul 2022 at 15:06:47 (-0500), Albretch Mueller wrote:
>  I googled: "mount solid state drive" Linux, and I got very few hits
> (like 16?) which were mostly totally irrelevant.
>  I got a laptop with Windows installed on which I installed WSLg.
> WIndows and WSLg both seem to detect the SSD just fine, but in ways
> that are not totally clear to me.

Oh, come on.

>  What I care about is using the SSD for my data intensive code in
> Linux, but when I boot that computer with Debian live I can't see the
> SSD.
>  What could be going on?

And we're meant to guess, when you don't even report the observations
you /have/ made. Please.

Cheers,
David.

Re: Three unsolvable Problems PRINTER SELFCHECK

[David Wright]

On Wed 27 Jul 2022 at 20:22:08 (+0100), Brian wrote:
> On Wed 27 Jul 2022 at 14:04:55 -0500, David Wright wrote:
> > On Wed 27 Jul 2022 at 16:51:19 (+), Schwibinger Michael wrote:
> > > HP printers have a self check.
> > 
> > Yes, and sometimes several (printing, wireless, fax, etc).
> > 
> > > You push the button and there is a check page.
> > 
> > I don't think HP printers have a button that you can just press
> > and get a test page. Please give more details on the model name,
> > number, and approximate year of the printer. Does it use ink
> > or toner?
> 
> It doesn't really matter whether they do or don't (mine does).

Well, it doesn't appear to be a feature of any of the three HP600
printers that I could find on the web (Desk, Office and Laser).

The closest thing I've seen to an actual Printer Test button on HP
printers is a combined press of the power and cancel buttons when
turning on. In the last century, you'd get a ripple pattern printed
ad infinitum, whereas nowadays you get more interesting information.

The latter usually involves working through a menu system so, for
example, this 8500 requires five taps of the screen (± swipe) to
get one printed. I'm talking about the printer itself, of course.
Are we certain that the OP is? Many HP printer manuals only describe
Test Page menus in a computer application context. And at least we
now (possibly) know a piece of paper is involved, rather than a code
number obtained in some manner. (I have little confidence that what
we read matches up with what the OP writes.)

> Not
> printing a self-test page has nothing do with the printing system
> or Debian. It is a entirely a function of the printer itself.

Sure. Quoting HP, "If the sample page prints, the printer is not
the problem." But if it doesn't, the problem could be with the
printer or the operator.

Cheers,
David.

Re: Three unsolvable Problems Printer II

[David Wright]

On Wed 27 Jul 2022 at 21:56:44 (-0400), gene heskett wrote:
> On 7/27/22 20:25, Gareth Evans wrote:
> > > On 28 Jul 2022, at 00:36, Gareth Evans  wrote:
> > > 
> > > > > [...] unless the [driverless] queue was added via lpadmin.
> > Just to correct the point, i keep forgetting, it seems even this fails with 
> > the latest cups version on Bullseye where fax printers are concerned.
> > .
> I haven't forgotten. The driverless stuff DOES NOT work, and you
> cannot delete it until you un-install the cups-browser. You can delete
> it, and cups says its deleted, but in the 5 seconds it gives you to
> read the deleted msg,
> cups-browser has recreated it again so its still there by the time you
> click on printers again.  And it blocks
> the makers drivers which in the case of Brother, do everything  the
> printer is capable of.
> 
> Driverless might work with some of the recent $40 printers, but it is
> a long way from being ready for
> prime time on a 5 yo $700 printer.

At least you could print a test page throughout. Here
we're in danger of running before we can walk.

Cheers,
David.

Re: How do you mount a solid state drive? ...

[David Wright]

On Thu 28 Jul 2022 at 06:33:18 (+0200), to...@tuxteam.de wrote:
> On Wed, Jul 27, 2022 at 06:54:32PM -0400, Jude DaShiell wrote:
> > An easy way to locate an ssd is to have it unplugged from the system and
> > run lsblk and save that to a file then plug the ssd in and run lsblk again
> > saving its output to another file.  The line in the second file that's
> > missing from the first file is the ssd.
> 
> Nice trick :)
> 
> To add one to the toolbox: do "tail -f /var/log/messages" while plugging
> in the device: you'll watch your OS pondering on what to do about it.
> 
> Or do "dmesg | tail" right away after having plugged it in. In both cases
> you'll see which name the device was registered with.
> 
> Both need root privilege, so "sudo" or "su" or whatever.

I'd be surprised if a laptop had so many block devices that
it was that difficult to spot the SSD, if it's showing up
at all. That's disregarding the tediousness of opening up
a laptop.

Cheers,
David.

Re: How do you mount a solid state drive? ...

[Nicolas George]

to...@tuxteam.de (12022-07-28):
> To add one to the toolbox: do "tail -f /var/log/messages" while plugging
> in the device: you'll watch your OS pondering on what to do about it.
> 
> Or do "dmesg | tail" right away after having plugged it in. In both cases
> you'll see which name the device was registered with.

dmesg -w

> Both need root privilege, so "sudo" or "su" or whatever.

sudo vim /etc/sysctl.conf
kernel.dmesg_restrict=0

Regards,

-- 
  Nicolas George


signature.asc
Description: PGP signature