Re: time_t transitions in testing

[Brad Rogers]

On Fri, 3 May 2024 01:11:31 -0400
songbird  wrote:

Hello songbird,

>  mainly i wanted to make sure that anything removed was
>being replaced and that my desktop would still be usable
>and that seems to have happened.

This has been my experience, too.

I will also add my thanks to the many, many, people that make this
possible;

Thank you, one and all.

-- 
 Regards  _   "Valid sig separator is {dash}{dash}{space}"
 / )  "The blindingly obvious is never immediately apparent"
/ _)rad   "Is it only me that has a working delete key?"
Down the stairs no one cares, he who wins is he who dares
Disco Man - The Damned


pgpdp_nZ8jTbx.pgp
Description: OpenPGP digital signature

Re: Installing testing on Acer Aspire 315

[Sirius]

In days of yore (Thu, 02 May 2024), Paul Scott thus quoth: 
> 
> On 5/1/2024 10:44 AM, Nicolas George wrote:
> > Paul Scott (12024-05-01):
> > > I read that I should try a more complete image which I am downloading
> > > (jigdo) now.
> > Waste of time. The drivers are either in the kernel image or in
> > individual packages, you can install them on top of what you have.
> > 
> > > I would appreciate any thoughts or suggestions,
> > Check the PCI ids of your Ethernet controller. Download the kernel image
> > you are considering, check if any of its modules matches these ids. n
> 
> I may need to do that.  Thank you,
> 
> In the mean time, an install seemed to be working but gave an failure
> error which said it would be in the log and visible on virtual terminal 4,
> I didn't know how to get to a virtual in the installer.  Various
> combinations with F4 didn't seem to work.
> 
> Google didn't seem to help. Can someone tell me how to get to a virtual
> terminal in the installer?

Control-Alt-F4 should get you to vc4. It might be enough with Alt-F4 if it
is text-mode installation, but if you are doing a GUI install (Wayland or
X running) you need the Control-Alt combo.

-- 
Kind regards,

/S

Re: Installing testing on Acer Aspire 315

[Paul Scott]

On 5/1/2024 10:44 AM, Nicolas George wrote:

Paul Scott (12024-05-01):

I read that I should try a more complete image which I am downloading
(jigdo) now.

Waste of time. The drivers are either in the kernel image or in
individual packages, you can install them on top of what you have.


I would appreciate any thoughts or suggestions,

Check the PCI ids of your Ethernet controller. Download the kernel image
you are considering, check if any of its modules matches these ids. n


I may need to do that.  Thank you,

In the mean time, an install seemed to be working but gave an failure 
error which said it would be in the log and visible on virtual terminal 
4, I didn't know how to get to a virtual in the installer.  Various 
combinations with F4 didn't seem to work.


Google didn't seem to help. Can someone tell me how to get to a virtual 
terminal in the installer?


TIA

Paul




Regards,

Re: time_t transitions in testing

[songbird]

songbird wrote:
...
>   thanks to all in the Debian community who have gotten this
> done.

  all looks ok.  :)


  songbird

Re: realpath quoting

[David Christensen]

On 5/2/24 19:56, Max Nikulin wrote:

On 03/05/2024 09:19, Greg Wooledge wrote:

I still insist that this is a workaround that should *not*  be used
to try to cancel out quoting bugs in one's shell scripts.


There are still specific cases when quoting is necessary, e.g. ssh 
remote command 



+1


(however you have to be sure concerning shell on the 
remote host).



+1


In BASH printf has %q format. GNU coreutils supports it as well, but 
dash does not, so be careful.



My practice is to start with '#!/bin/sh' and migrate to '#!/usr/bin/env 
perl' as complexity increases.




Likely Jeremy's case does not really require this kind of quoting.



We need to see the full range of file names the OP is trying to deal with.


While "ls -l" output is for humans, realpath is often used in scripts. 
Certainly it should nor return quoted output by default. I am in doubts 
if a dedicated option should be added to realpath.



Thank you for helping me realize that my solution fails to print the 
resolved absolute file name.  Here is the updated solution:


2024-05-02 21:57:56 dpchrist@laalaa ~
$ touch 'name with spaces'

2024-05-02 22:23:01 dpchrist@laalaa ~
$ touch 'name with
> newline'

2024-05-02 22:28:36 dpchrist@laalaa ~
$ perl -MString::ShellQuote '-MFile::Spec::Functions qw(rel2abs)' -e 
'print shell_quote(map { rel2abs $_ } @ARGV), "\n"' name*

'/home/dpchrist/name with
newline' '/home/dpchrist/name with spaces'


David

time_t transitions in testing

[songbird]

songbird wrote:
...
>   the on-going time_t transitions may be causing some packages
> to be removed for a while as dependencies get adjusted.
>
>   i've currently not been doing full upgrades because there are
> many Mate packages that would be removed.

  i decided to see what i could get upgraded tonight and
have done it in layers.

  mainly i wanted to make sure that anything removed was
being replaced and that my desktop would still be usable
and that seems to have happened.

  so far it seems to have gone well but i'm on the last 400
packages (it takes me a bit to download since i'm not on a
super-fast connection).  with how things have gone so far i
don't expect any hiccups.

  i  Debian and testing aka trixie.  :)

  thanks to all in the Debian community who have gotten this
done.


  songbird

Re: realpath quoting

[David Christensen]

On 5/2/24 19:19, Greg Wooledge wrote:

On Thu, May 02, 2024 at 07:11:46PM -0700, David Christensen wrote:

Perhaps Perl and the module String::ShellQuote ?

2024-05-02 18:50:28 dpchrist@laalaa ~
$ touch "name with spaces"

2024-05-02 18:50:45 dpchrist@laalaa ~
$ touch "name with\nnewline"


You didn't create a name with a newline in it here.  You created a name
with a backslash in it.  If you wanted a newline, you would have to use
the $'...' quoting form (in bash).

 touch $'name with\nnewline'



Thank you for the clarification.


RTFM bash(1):

QUOTING
...
Enclosing  characters  in  double quotes preserves the literal
value of all characters within the quotes, with the exception of
$, `,  \,  and, when history expansion is enabled, !. ...
The backslash retains its special  meaning  only when followed
by one of the following characters: $, `, ", \, or .
...
Words of the form $'string' are treated specially.  The word
expands to string,  with backslash-escaped characters replaced
as specified by the ANSI C standard.


I found another way to obtain a file name containing a newline -- by 
pressing  when typing a double-quoted string literal:


2024-05-02 21:52:23 dpchrist@laalaa ~
$ touch "foo
> bar"

2024-05-02 21:52:29 dpchrist@laalaa ~
$ ls -l foo*
-rw-r--r-- 1 dpchrist dpchrist 0 May  2 21:52 'foo'$'\n''bar'

2024-05-02 21:52:36 dpchrist@laalaa ~
$ perl -MString::ShellQuote -e 'print shell_quote(@ARGV), "\n"' foo*
'foo
bar'


It also seems to work for single-quoted string literals:

2024-05-02 21:57:08 dpchrist@laalaa ~
$ touch 'foo
> bar'

2024-05-02 21:57:14 dpchrist@laalaa ~
$ ls -l foo*
-rw-r--r-- 1 dpchrist dpchrist 0 May  2 21:57 'foo'$'\n''bar'

2024-05-02 21:57:18 dpchrist@laalaa ~
$ perl -MString::ShellQuote -e 'print shell_quote(@ARGV), "\n"' foo*
'foo
bar'


I am unable to find $'string' in the dash(1) man page (?).  As I 
typically write "#!/bin/sh" shell scripts, writing such to deal with 
file names containing non-printing characters is going to baffle me.




I still insist that this is a workaround that should *not* be used
to try to cancel out quoting bugs in one's shell scripts.  Just write
the shell scripts correctly in the first place.



I would if I could.


While I am also unable to write Perl scripts correctly in the first 
place, the quoting rules are easier.



David

Re: Installing testing on Acer Aspire 315

[Paul Scott]

On 5/2/2024 8:06 PM, Max Nikulin wrote:

On 02/05/2024 12:19, Sirius wrote:

If your wifi is also the AX200 (maybe a different revision), it *should*
work.


lspci -nn

may help with more precise identification.


I don't have linux on the machine for which I want the information.  I 
now have the driver name from Windows/Settings.





It requires firmware-iwlwifi from non-free-firmware, so check that 
install image contains firmware.


I would avoid installing testing for several weeks. Maybe a huge 
change with 64 bit time_t has not settled yet.


My experience with

02:00.0 Network controller [0280]: Intel Corporation Wi-Fi 6 AX200 
[8086:2723] (rev 1a)


is far from being positive. Firmware crashes are not infrequent. Not 
all applications handle lost packets and disabling/enabling network 
adapter gracefully. It might depend on the WiFi router (and others 
around).



I'll consider that strongly,

Thank you,

Paul

Re: realpath quoting

[Teemu Likonen]

* 2024-05-03 06:59:37+0800, jeremy ardley wrote:

> I have a need  to get the full path of a file that has spaces in its 
> name to use as a program argument

> jeremy@client:~$ realpath name\ with\ spaces
> /home/jeremy/name with spaces

> Can realpath or other utility return a quoted pathname?

Tools don't need to return a shell-quoted pathname because you as a
shell programmer must do it:

file=$(realpath ...)   # quotes not needed in variable assignment
do_something_for "$file"   # always quote: "$file"


If you don't need variables you can just quote the "realpath" output:

do_something_for "$(realpath ...)"

-- 
/// Teemu Likonen - .-.. https://www.iki.fi/tlikonen/
// OpenPGP: 6965F03973F0D4CA22B9410F0F2CAE0E07608462


signature.asc
Description: PGP signature

Re: realpath quoting

[jeremy ardley]

On 3/5/24 10:56, Max Nikulin wrote:

On 03/05/2024 09:19, Greg Wooledge wrote:

I still insist that this is a workaround that should *not*  be used
to try to cancel out quoting bugs in one's shell scripts.


There are still specific cases when quoting is necessary, e.g. ssh 
remote command (however you have to be sure concerning shell on the 
remote host).


In BASH printf has %q format. GNU coreutils supports it as well, but 
dash does not, so be careful.


Likely Jeremy's case does not really require this kind of quoting.

While "ls -l" output is for humans, realpath is often used in scripts. 
Certainly it should nor return quoted output by default. I am in 
doubts if a dedicated option should be added to realpath.




My use case is very simple. Give an argument to a program that expects a 
single filename/path.


If you give it an unquoted and unescaped filename it will break parsing 
the args thinking there are many.


When invoking from bash with auto completion the filename will get 
escaped as required. When cutting and pasting into a debugger prompt for 
args, not so.


The easy workaround for me is a few lines of python that emits a quoted 
filepath.

Re: Installing testing on Acer Aspire 315

[Max Nikulin]

On 02/05/2024 12:19, Sirius wrote:

If your wifi is also the AX200 (maybe a different revision), it *should*
work.


lspci -nn

may help with more precise identification.

It requires firmware-iwlwifi from non-free-firmware, so check that 
install image contains firmware.


I would avoid installing testing for several weeks. Maybe a huge change 
with 64 bit time_t has not settled yet.


My experience with

02:00.0 Network controller [0280]: Intel Corporation Wi-Fi 6 AX200 
[8086:2723] (rev 1a)


is far from being positive. Firmware crashes are not infrequent. Not all 
applications handle lost packets and disabling/enabling network adapter 
gracefully. It might depend on the WiFi router (and others around).

Re: realpath quoting

[Max Nikulin]

On 03/05/2024 09:19, Greg Wooledge wrote:

I still insist that this is a workaround that should *not*  be used
to try to cancel out quoting bugs in one's shell scripts.


There are still specific cases when quoting is necessary, e.g. ssh 
remote command (however you have to be sure concerning shell on the 
remote host).


In BASH printf has %q format. GNU coreutils supports it as well, but 
dash does not, so be careful.


Likely Jeremy's case does not really require this kind of quoting.

While "ls -l" output is for humans, realpath is often used in scripts. 
Certainly it should nor return quoted output by default. I am in doubts 
if a dedicated option should be added to realpath.

Re: realpath quoting

[Greg Wooledge]

On Thu, May 02, 2024 at 07:11:46PM -0700, David Christensen wrote:
> Perhaps Perl and the module String::ShellQuote ?
> 
> 2024-05-02 18:50:28 dpchrist@laalaa ~
> $ touch "name with spaces"
> 
> 2024-05-02 18:50:45 dpchrist@laalaa ~
> $ touch "name with\nnewline"

You didn't create a name with a newline in it here.  You created a name
with a backslash in it.  If you wanted a newline, you would have to use
the $'...' quoting form (in bash).

touch $'name with\nnewline'

> 2024-05-02 19:06:01 dpchrist@laalaa ~
> $ perl -MString::ShellQuote -e 'print shell_quote(@ARGV), "\n"' name*
> 'name with spaces' 'name with\nnewline'

I still insist that this is a workaround that should *not* be used
to try to cancel out quoting bugs in one's shell scripts.  Just write
the shell scripts correctly in the first place.

Re: realpath quoting

[David Christensen]

On 5/2/24 15:59, jeremy ardley wrote:
I have a need  to get the full path of a file that has spaces in its 
name to use as a program argument


e.g.

jeremy@client:~$ ls -l name\ with\ spaces
-rw-r--r-- 1 jeremy jeremy 0 May  3 06:51 'name with spaces'
jeremy@client:~$ realpath name\ with\ spaces
/home/jeremy/name with spaces


The spaces without quotes cause problems with subsequent processing.

Can realpath or other utility return a quoted pathname?



Perhaps Perl and the module String::ShellQuote ?

2024-05-02 18:50:28 dpchrist@laalaa ~
$ touch "name with spaces"

2024-05-02 18:50:45 dpchrist@laalaa ~
$ touch "name with\nnewline"

2024-05-02 19:06:01 dpchrist@laalaa ~
$ perl -MString::ShellQuote -e 'print shell_quote(@ARGV), "\n"' name*
'name with spaces' 'name with\nnewline'


David

Re: realpath quoting

[Greg Wooledge]

On Fri, May 03, 2024 at 07:42:20AM +0800, jeremy ardley wrote:
> 
> On 3/5/24 07:29, Greg Wooledge wrote:
> > > The spaces without quotes cause problems with subsequent processing.
> > Then the subsequent processing has bugs in it.  Fix them.
> > 
> > > Can realpath or other utility return a quoted pathname?
> > That would be extremely counterproductive.  Do not look for kludges to
> > work around your script's bugs.  Fix the bugs instead.
> > 
> > Start with.
> > 
> 
> You don't see a problem that ls produces quoted filenames and realpath
> doesn't?

Oh Jesus, don't get me started on ls.

We have a whole page on that.  

Re: realpath quoting

[jeremy ardley]

On 3/5/24 07:29, Greg Wooledge wrote:

The spaces without quotes cause problems with subsequent processing.

Then the subsequent processing has bugs in it.  Fix them.


Can realpath or other utility return a quoted pathname?

That would be extremely counterproductive.  Do not look for kludges to
work around your script's bugs.  Fix the bugs instead.

Start with.



You don't see a problem that ls produces quoted filenames and realpath 
doesn't?

Re: realpath quoting

[Greg Wooledge]

On Fri, May 03, 2024 at 06:59:37AM +0800, jeremy ardley wrote:
> I have a need  to get the full path of a file that has spaces in its name to
> use as a program argument
> 
> e.g.
> 
> jeremy@client:~$ ls -l name\ with\ spaces
> -rw-r--r-- 1 jeremy jeremy 0 May  3 06:51 'name with spaces'
> jeremy@client:~$ realpath name\ with\ spaces
> /home/jeremy/name with spaces

Looks good to me.

> The spaces without quotes cause problems with subsequent processing.

Then the subsequent processing has bugs in it.  Fix them.

> Can realpath or other utility return a quoted pathname?

That would be extremely counterproductive.  Do not look for kludges to
work around your script's bugs.  Fix the bugs instead.

Start with .

Re: realpath quoting

[DdB]

Am 03.05.2024 um 00:59 schrieb jeremy ardley:
> I have a need  to get the full path of a file that has spaces in its
> name to use as a program argument
> 
> e.g.
> 
> jeremy@client:~$ ls -l name\ with\ spaces
> -rw-r--r-- 1 jeremy jeremy 0 May  3 06:51 'name with spaces'
> jeremy@client:~$ realpath name\ with\ spaces
> /home/jeremy/name with spaces
> 
> 
> The spaces without quotes cause problems with subsequent processing.
> 
> Can realpath or other utility return a quoted pathname?
> 
> 
Do you mean something along those lines:
> $ touch '/mnt/tmp/gibt es nicht'
> $ realpath -mz "../ln/tmpRAM/gibt es nicht" | xargs -0 ls 
> --quoting-style=escape
> /mnt/tmp/gibt\ es\ nicht

?

realpath quoting

[jeremy ardley]

I have a need  to get the full path of a file that has spaces in its 
name to use as a program argument


e.g.

jeremy@client:~$ ls -l name\ with\ spaces
-rw-r--r-- 1 jeremy jeremy 0 May  3 06:51 'name with spaces'
jeremy@client:~$ realpath name\ with\ spaces
/home/jeremy/name with spaces


The spaces without quotes cause problems with subsequent processing.

Can realpath or other utility return a quoted pathname?

Re: QEMU/KVM virt-manager Problem

[Gareth Evans]

On Thu 02/05/2024 at 20:14, Gareth Evans  wrote:
> On Thu 02/05/2024 at 19:57, Stephen P. Molnar  wrote:
>> On 05/02/2024 12:54 PM, Gareth Evans wrote:
>>>
>>>
 On 2 May 2024, at 17:47, Gareth Evans  wrote:

 

> On 2 May 2024, at 15:43, Stephen P. Molnar  
> wrote:
>
> I am running Bookworm and have implemented QEMU/KVM virt-manager. 
> When I install a client I have been using virt-manager --> View 
> -->Scale Display --> Always. However, now the 'Always ', the only 
> option available is the default 'Only when Fullscreen'.

 Is Bookworm the VM client too?  With GUI?  Does this happen for all 
 clients, just one, or one type?

 Off the top of my head, I think the scale always option may disappear 
 if the guest display doesn't support it - I seem to recall VirtualBox 
 Guest Additions being required for this functionality for some guests 
 in VirtualBox (which I acknowledge you are not using, I'm just 
 saying...) so I don't think it's "straightforward" functionality
>>>
>>> What video protocol are you using?
>>>
>>> spice-vdagent is mentioned here a few comments down
>>>
>>> https://forum.manjaro.org/t/virt-manager-scale-display-not-working/138275/3
>> I am using the procedure in 
>> https://getlabsdone.com/install-windows-10-on-ubuntu-kvm/
>>
>> I am most interested in installing Windows 10, as there computation 
>> chemistry windows apps that I want to use on Bookworm. However, the same 
>> problem is resent for Linux clients that I've installed.
>
> In 
>
> virt-manager > Edit > Preferences > [console tab]
>
> I see options for
>
> Graphical console scaling [ Never / Fullscreen only / Always]
> Resize guest with window [System default / Off / On]
>
> This looks like it might just set defaults for options accessible from 
> the VM view menu, but perhaps worth experimenting with?
>
> The only Linux VM I have in virt-manager used the spice display manager 
> by default.
>
> If you are using spice too, this
>
> https://stackoverflow.com/questions/41990600/virt-manager-guest-resize-not-working
>
> suggests spice-guest-tools is required for Windows clients, with link 
> to download page
>
> Does any of that help?
>
> Best wishes
> Gareth

Just noticed the link you provided includes a ref to spice-guest-tools.

With an Alpine client (and no "tools") I get less than optimal scaling from 
virt-manager - some black space at the horizontal edges, but there is a scaling 
of sorts going on, just not entirely using the available window space.

Are you using the stock version of virt-manager?

$ apt policy virt-manager
virt-manager:
  Installed: 1:4.1.0-2

Re: QEMU/KVM virt-manager Problem

[Gareth Evans]

On Thu 02/05/2024 at 19:57, Stephen P. Molnar  wrote:
> On 05/02/2024 12:54 PM, Gareth Evans wrote:
>>
>>
>>> On 2 May 2024, at 17:47, Gareth Evans  wrote:
>>>
>>> 
>>>
 On 2 May 2024, at 15:43, Stephen P. Molnar  
 wrote:

 I am running Bookworm and have implemented QEMU/KVM virt-manager. 
 When I install a client I have been using virt-manager --> View 
 -->Scale Display --> Always. However, now the 'Always ', the only 
 option available is the default 'Only when Fullscreen'.
>>>
>>> Is Bookworm the VM client too?  With GUI?  Does this happen for all 
>>> clients, just one, or one type?
>>>
>>> Off the top of my head, I think the scale always option may disappear 
>>> if the guest display doesn't support it - I seem to recall VirtualBox 
>>> Guest Additions being required for this functionality for some guests 
>>> in VirtualBox (which I acknowledge you are not using, I'm just 
>>> saying...) so I don't think it's "straightforward" functionality
>>
>> What video protocol are you using?
>>
>> spice-vdagent is mentioned here a few comments down
>>
>> https://forum.manjaro.org/t/virt-manager-scale-display-not-working/138275/3
> I am using the procedure in 
> https://getlabsdone.com/install-windows-10-on-ubuntu-kvm/
>
> I am most interested in installing Windows 10, as there computation 
> chemistry windows apps that I want to use on Bookworm. However, the same 
> problem is resent for Linux clients that I've installed.

In 

virt-manager > Edit > Preferences > [console tab]

I see options for

Graphical console scaling [ Never / Fullscreen only / Always]
Resize guest with window [System default / Off / On]

This looks like it might just set defaults for options accessible from the VM 
view menu, but perhaps worth experimenting with?

The only Linux VM I have in virt-manager used the spice display manager by 
default.

If you are using spice too, this

https://stackoverflow.com/questions/41990600/virt-manager-guest-resize-not-working

suggests spice-guest-tools is required for Windows clients, with link to 
download page

Does any of that help?

Best wishes
Gareth

Re: QEMU/KVM virt-manager Problem

[Stephen P. Molnar]

On 05/02/2024 12:54 PM, Gareth Evans wrote:




On 2 May 2024, at 17:47, Gareth Evans  wrote:



On 2 May 2024, at 15:43, Stephen P. Molnar  
wrote:


I am running Bookworm and have implemented QEMU/KVM virt-manager. 
When I install a client I have been using virt-manager --> View 
-->Scale Display --> Always. However, now the 'Always ', the only 
option available is the default 'Only when Fullscreen'.


Is Bookworm the VM client too?  With GUI?  Does this happen for all 
clients, just one, or one type?


Off the top of my head, I think the scale always option may disappear 
if the guest display doesn't support it - I seem to recall VirtualBox 
Guest Additions being required for this functionality for some guests 
in VirtualBox (which I acknowledge you are not using, I'm just 
saying...) so I don't think it's "straightforward" functionality


What video protocol are you using?

spice-vdagent is mentioned here a few comments down

https://forum.manjaro.org/t/virt-manager-scale-display-not-working/138275/3
I am using the procedure in 
https://getlabsdone.com/install-windows-10-on-ubuntu-kvm/


I am most interested in installing Windows 10, as there computation 
chemistry windows apps that I want to use on Bookworm. However, the same 
problem is resent for Linux clients that I've installed.


--
Stephen P. Molnar, Ph.D.
https://insilicochemistry.net
(614)312-7528 (c)
Skype:  smolnar1

Re: QEMU/KVM virt-manager Problem

[Gareth Evans]

> On 2 May 2024, at 17:47, Gareth Evans  wrote:
> 
> 
> 
>> On 2 May 2024, at 15:43, Stephen P. Molnar  wrote:
>> 
>> I am running Bookworm and have implemented QEMU/KVM virt-manager. When I 
>> install a client I have been using virt-manager --> View -->Scale Display 
>> --> Always. However, now the 'Always ', the only option available is the 
>> default 'Only when Fullscreen'.
> 
> Is Bookworm the VM client too?  With GUI?  Does this happen for all clients, 
> just one, or one type?
> 
> Off the top of my head, I think the scale always option may disappear if the 
> guest display doesn't support it - I seem to recall VirtualBox Guest 
> Additions being required for this functionality for some guests in VirtualBox 
> (which I acknowledge you are not using, I'm just saying...) so I don't think 
> it's "straightforward" functionality

What video protocol are you using?

spice-vdagent is mentioned here a few comments down

https://forum.manjaro.org/t/virt-manager-scale-display-not-working/138275/3

Re: QEMU/KVM virt-manager Problem

[Gareth Evans]

> On 2 May 2024, at 15:43, Stephen P. Molnar  wrote:
> 
> I am running Bookworm and have implemented QEMU/KVM virt-manager. When I 
> install a client I have been using virt-manager --> View -->Scale Display --> 
> Always. However, now the 'Always ', the only option available is the default 
> 'Only when Fullscreen'.

Is Bookworm the VM client too?  With GUI?  Does this happen for all clients, 
just one, or one type?

Off the top of my head, I think the scale always option may disappear if the 
guest display doesn't support it - I seem to recall VirtualBox Guest Additions 
being required for this functionality for some guests in VirtualBox (which I 
acknowledge you are not using, I'm just saying...) so I don't think it's 
"straightforward" functionality

Re: QEMU/KVM virt-manager Problem

[Curt]

On 2024-05-02, Stephen P. Molnar  wrote:
> I am running Bookworm and have implemented QEMU/KVM virt-manager. When I 
> install a client I have been using virt-manager --> View -->Scale 
> Display --> Always. However, now the 'Always ', the only option 
> available is the default 'Only when Fullscreen'.
>
> Now this in not exactly a major problem, but it makes me wonder what 
> else might be going wrong?
>
> I would appreciate some guidance in this matter.
>
> Thanks in advance.
>

>
> Thanks in advance.


https://askubuntu.com/questions/43861/how-do-i-unmaximize-full-screen-view-in-virt-manager


A variety of answers to the fullscreeen conundrum, some of which are rather
recent if you scroll downward sufficiently.

QEMU/KVM virt-manager Problem

[Stephen P. Molnar]

I am running Bookworm and have implemented QEMU/KVM virt-manager. When I 
install a client I have been using virt-manager --> View -->Scale 
Display --> Always. However, now the 'Always ', the only option 
available is the default 'Only when Fullscreen'.


Now this in not exactly a major problem, but it makes me wonder what 
else might be going wrong?


I would appreciate some guidance in this matter.

Thanks in advance.

--
Stephen P. Molnar, Ph.D.
https://insilicochemistry.net
(614)312-7528 (c)
Skype:  smolnar1

Re: Zutty fonts - zutty always uses the same font and fontsize

[Richmond]

Sirius  writes:


> Good old urxvt is quite lightweight compared to kitty.

It understands the font names from xfontsel which is a major improvement
on zutty.

urxvt -bg black -fn -*-courier-*-r-*-*-24-*-*-*-*-*-*-*

8)

Re: speaker-test: no correct sound output on LFE and others speakers

[Alexandre Rossi]

Hi,

> > > The issue is that speaker-test doesn't play sound to the correct speaker. 
> > > If
> > > I run:
> > > 
> > > ~$ speaker-test -Dplug:surround51 -c6 -s3 -f75
> > > 
> > > The sound comes from (Center), (Front right), (Rear left) and (Rear right)
> > > speakers instead (Front right) only.
> > 
> > What's bothering me is that you get sound from multiple speakers while
> > instructing out on only one.
> > 
> > The usual issues of these setups with surround analog out are:
> > - channel mapping issues (driver/hardware mismatch)
> > - software downmixing to stereo
> > 
> > There are other usual issues with surrount digital out but this is not
> > your setup.
> > 
> > You can have a look at [1] for software fixes on this.
> > 
> > [1] https://alsa.opensrc.org/SurroundSound
> 
> The link you posted it shows rather outdated fixes, it talked about Jackd
> daemon and surround, but I have pulseaudio daemon, maybe I've pulseaudio
> daemon misconfiguration

My understanding is that pulseaudio uses alsa for kernel interface and
that speaker-test uses alsa directly. So if one cannot get speaker-test
to sound right, it cannot work with pulseaudio. That why I suggest workarounds
in alsa conf (asoundrc).

Alex