Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #227922 > unrolled thread

Zoom.

Back to article view | Back to linux.debian.user

Contents

  Zoom. peter@easthope.ca - 2020-10-17 23:10 +0200
    Re: Zoom. Charles Curley <charlescurley@charlescurley.com> - 2020-10-17 23:40 +0200
    Re: Zoom. Peter Ehlert <peter@sdi-baja.com> - 2020-10-18 00:10 +0200
    Re: Zoom. Carl Fink <carlf@panix.com> - 2020-10-18 01:00 +0200
      Re: Zoom. conover@rahul.net (John Conover) - 2020-10-18 01:40 +0200
    Re: Zoom. David <bouncingcats@gmail.com> - 2020-10-18 01:50 +0200
      Re: Zoom. riveravaldez <riveravaldezmail@gmail.com> - 2020-10-18 05:10 +0200
      Re: Zoom. Tom Dial <tddial@comcast.net> - 2020-10-18 09:20 +0200
    Re: Zoom. Bob McGowan <ramjr0915@gmail.com> - 2020-10-18 03:30 +0200
      Re: Zoom. peter@easthope.ca - 2020-10-19 23:10 +0200
        Re: Zoom. Michael Stone <mstone@debian.org> - 2020-10-19 23:10 +0200
          Re: Zoom. peter@easthope.ca - 2020-10-22 15:30 +0200
            Re: Zoom. Michael Stone <mstone@debian.org> - 2020-10-22 16:40 +0200
        Re: Zoom. John Crawley <john@bunsenlabs.org> - 2020-10-20 04:30 +0200
          Re: Zoom. Dan Ritter <dsr@randomstring.org> - 2020-10-20 12:40 +0200
            Re: Zoom. Nicolas George <george@nsup.org> - 2020-10-20 13:20 +0200
            Re: Zoom. Greg Wooledge <wooledg@eeg.ccf.org> - 2020-10-20 13:40 +0200
              Re: Zoom. Dan Ritter <dsr@randomstring.org> - 2020-10-20 14:10 +0200
              Re: shells (was Re: Zoom.) rhkramer@gmail.com - 2020-10-20 17:00 +0200
                Re: shells (was Re: Zoom.) Nicolas George <george@nsup.org> - 2020-10-20 17:00 +0200
                Re: shells (was Re: Zoom.) Tony van der Hoff <lists@vanderhoff.org> - 2020-10-20 17:40 +0200
    Re: Zoom. A_Man_Without_Clue <love.chaser@gmail.com> - 2020-10-18 05:20 +0200
    Re: Zoom. Stefan Monnier <monnier@iro.umontreal.ca> - 2020-10-18 17:20 +0200
      Re: Zoom. Sven Hartge <sven@svenhartge.de> - 2020-10-18 17:50 +0200
        Re: Zoom. <tomas@tuxteam.de> - 2020-10-19 09:30 +0200
          Re: Zoom. Sven Hartge <sven@svenhartge.de> - 2020-10-19 09:40 +0200
            Re: Zoom. David Wright <deblis@lionunicorn.co.uk> - 2020-10-19 17:10 +0200
            Re: Zoom. Stefan Monnier <monnier@iro.umontreal.ca> - 2020-10-19 17:30 +0200
              Re: Zoom. <tomas@tuxteam.de> - 2020-10-19 17:40 +0200
              Re: Zoom. Stefan Monnier <monnier@iro.umontreal.ca> - 2020-10-19 18:00 +0200
            Re: Zoom. Stefan Monnier <monnier@iro.umontreal.ca> - 2020-10-19 17:40 +0200
          Re: Zoom. "Thomas Schmitt" <scdbackup@gmx.net> - 2020-10-19 10:00 +0200
      Re: Zoom. peter@easthope.ca - 2020-10-20 03:20 +0200
        Re: Zoom. <tomas@tuxteam.de> - 2020-10-20 10:10 +0200
      Re: Zoom. peter@easthope.ca - 2020-10-20 03:30 +0200
      Server for Jitsi; was: Zoom. peter@easthope.ca - 2020-10-22 20:20 +0200
        Re: Server for Jitsi; was: Zoom. Dan Ritter <dsr@randomstring.org> - 2020-10-22 20:40 +0200
        Re: Server for Jitsi; was: Zoom. "der.hans" <deb-user@LuftHans.com> - 2020-10-22 21:00 +0200
        Re: Server for Jitsi; was: Zoom. Stefan Monnier <monnier@iro.umontreal.ca> - 2020-10-23 01:40 +0200

Page 1 of 2  [1] 2  Next page →

#227922 — Zoom.

Does anyone have Zoom working in Debian 10?

Here it produces empty windows.  Visible toward the right in this 
screenshot.  http://easthope.ca/Zoom.png

This is the entire output after starting in a terminal and then 
exiting.

peter@joule:~$ zoom 
peter@joule:~$ 

Thx,                       ... P.

-- 
Tel: +1 604 670 0140            Bcc: peter at easthope. ca

[toc] | [next] | [standalone]

#227924

On Sat, 17 Oct 2020 13:23:02 -0700
peter@easthope.ca wrote:

> Does anyone have Zoom working in Debian 10?

Yes.

Linux Client Version is 5.0.418682.0603

(You may have to go to the notification tray and shut it down from there.)

--------------------------------------------------
charles@jhegaala:~$ zoom 
ZoomLauncher started.
Zoom not exist at current directory - /home/charles
Zoom path is: /opt/zoom
cmd line: 
CreateReportChannel bp_server_fd=4
$HOME = /home/charles 
export SSB_HOME=/home/charles/.zoom; export QSG_INFO=1; export LD_LIBRARY_PATH=/opt/zoom; export BREAKPAD_CLIENT_FD=3; /opt/zoom/zoom "" 
zoom started.
Client: Breakpad is using Client-Server Mode! client fd = 3
[CZPClientLogMgr::LogClientEnvironment] [MacAddr: 52:54:00:F6:E2:17][client: Linux][OS: Debian GNU/Linux 10 (buster)][Hardware: CPU Core:2 Frenquency:2.5 G Memory size:7860MB CPU Brand:       Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz GPU Brand:][Req ID: ]
Linux Client Version is 5.0.418682.0603
QSG_RENDER_LOOP is 
XDG_CURRENT_DESKTOP = XFCE;   GDMSESSION = lightdm-xsession
Graphics Card Info:: 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
Zoom package arch is 64bit, runing OS arch is x86_64
Error: Send error, 22 Invalid argument
Error: Send error, 22 Invalid argument
Error: Send error, 22 Invalid argument
AppIconMgr::systemDesktopName log Desktop Name: lightdm-xsession 
qt.scenegraph.general: QSG: basic render loop
qt.scenegraph.general: Using sg animation driver
qt.svg: link image0 hasn't been detected!
qt.svg: :/images/wechat.svg:10:6: Could not resolve property: pattern0
qt.scenegraph.general: texture atlas dimensions: 1024x512
qt.scenegraph.general: R/G/B/A Buffers:    8 8 8 8
qt.scenegraph.general: Depth Buffer:       24
qt.scenegraph.general: Stencil Buffer:     8
qt.scenegraph.general: Samples:            -1
qt.scenegraph.general: GL_VENDOR:          Intel Open Source Technology Center
qt.scenegraph.general: GL_RENDERER:        Mesa DRI Intel(R) Sandybridge Mobile 
qt.scenegraph.general: GL_VERSION:         3.0 Mesa 18.3.6
qt.scenegraph.general: GL_EXTENSIONS:      GL_ARB_color_buffer_float GL_KHR_context_flush_control GL_EXT_blend_equation_separate GL_EXT_packed_depth_stencil GL_INTEL_performance_query GL_EXT_copy_texture GL_ARB_compressed_texture_pixel_storage GL_EXT_polygon_offset_clamp GL_SGIS_texture_lod GL_ARB_shading_language_100 GL_EXT_timer_query GL_ATI_texture_float GL_EXT_texture GL_EXT_texture_rectangle GL_APPLE_object_purgeable GL_KHR_no_error GL_EXT_packed_float GL_NV_texture_rectangle GL_ARB_fragment_shader GL_ARB_debug_output GL_SGIS_texture_edge_clamp GL_ARB_multisample GL_ARB_shader_objects GL_3DFX_texture_compression_FXT1 GL_ARB_texture_storage GL_SGIS_texture_border_clamp GL_ARB_copy_image GL_ATI_texture_env_combine3 GL_EXT_pixel_buffer_object GL_EXT_stencil_wrap GL_ARB_texture_gather GL_KHR_robustness GL_ARB_pipeline_statistics_query GL_ARB_conditional_render_inverted GL_ARB_texture_rgb10_a2ui GL_IBM_rasterpos_clip GL_EXT_texture_array GL_ARB_framebuffer_sRGB GL_ARB_map_buffer_alig
 nment GL_EXT_texture_edge_clamp GL_EXT_blend_color GL_EXT_separate_specular_color GL_EXT_shadow_funcs GL_ARB_texture_cube_map_array GL_ARB_program_interface_query GL_KHR_debug GL_ARB_clear_buffer_object GL_NV_texgen_reflection GL_NV_texture_barrier GL_EXT_framebuffer_multisample GL_ARB_multi_bind GL_EXT_shader_framebuffer_fetch_non_coherent GL_S3_s3tc GL_NV_conditional_render GL_EXT_texture_integer GL_EXT_subtexture GL_EXT_transform_feedback GL_EXT_framebuffer_object GL_MESA_texture_signed_rgba GL_ARB_pixel_buffer_object GL_NV_fog_distance GL_EXT_texture_compression_s3tc GL_ARB_texture_mirror_clamp_to_edge GL_ARB_texture_filter_anisotropic GL_NV_texture_env_combine4 GL_EXT_secondary_color GL_ARB_transpose_matrix GL_ARB_texture_border_clamp GL_ARB_texture_mirrored_repeat GL_ARB_draw_instanced GL_ARB_explicit_uniform_location GL_ATI_draw_buffers GL_EXT_blend_func_separate GL_ARB_draw_elements_base_vertex GL_ANGLE_texture_compression_dxt5 GL_ARB_occlusion_query GL_ARB_shading_language_
 packing GL_ARB_internalformat_query2 GL_EXT_texture_cube_map GL_ARB_map_buffer_range GL_ARB_shading_language_420pack GL_EXT_texture_compression_rgtc GL_OES_EGL_image GL_EXT_texture_env_add GL_ARB_explicit_attrib_location GL_EXT_vertex_array_bgra GL_ARB_uniform_buffer_object GL_SGIS_generate_mipmap GL_ARB_cull_distance GL_ARB_seamless_cubemap_per_texture GL_ARB_occlusion_query2 GL_EXT_point_parameters GL_ARB_clear_texture GL_EXT_abgr GL_ARB_framebuffer_object GL_ARB_vertex_shader GL_ARB_sync GL_NV_packed_depth_stencil GL_ARB_shadow GL_ARB_polygon_offset_clamp GL_EXT_multi_draw_arrays GL_ARB_robustness GL_EXT_texture_sRGB_decode GL_KHR_blend_equation_advanced GL_ARB_clip_control GL_ARB_vertex_program GL_AMD_seamless_cubemap_per_texture GL_ARB_texture_swizzle GL_ARB_texture_env_add GL_ARB_sample_shading GL_ARB_texture_env_dot3 GL_MESA_pack_invert GL_ARB_instanced_arrays GL_ARB_vertex_array_bgra GL_AMD_draw_buffers_blend GL_ARB_texture_query_lod GL_ARB_texture_query_levels GL_EXT_textur
 e_sRGB GL_ARB_depth_buffer_float GL_EXT_texture_compression_dxt1 GL_NV_depth_clamp GL_MESA_window_pos GL_EXT_texture_snorm GL_AMD_shader_trinary_minmax GL_ANGLE_texture_compression_dxt3 GL_EXT_blend_subtract GL_ARB_texture_rectangle GL_ARB_vertex_attrib_binding GL_EXT_stencil_two_side GL_ARB_blend_func_extended GL_ARB_vertex_buffer_object GL_EXT_fog_coord GL_EXT_texture_env_combine GL_MESA_shader_integer_functions GL_EXT_draw_buffers2 GL_ARB_texture_barrier GL_ARB_point_parameters GL_EXT_draw_range_elements GL_ARB_texture_non_power_of_two GL_ARB_vertex_type_10f_11f_11f_rev GL_ARB_multitexture GL_ARB_texture_rg GL_ATI_separate_stencil GL_ARB_depth_texture GL_ARB_fragment_coord_conventions GL_ARB_fragment_program GL_EXT_rescale_normal GL_EXT_texture_swizzle GL_ARB_shader_bit_encoding GL_ARB_arrays_of_arrays GL_EXT_texture_lod_bias GL_ARB_shader_draw_parameters GL_ARB_separate_shader_objects GL_ARB_fragment_layer_viewport GL_ARB_buffer_storage GL_ARB_fragment_program_shadow GL_OES_read
 _format GL_ARB_vertex_type_2_10_10_10_rev GL_NV_blend_square GL_ARB_half_float_pixel GL_ARB_texture_float GL_ARB_shader_texture_lod GL_ARB_ES3_compatibility GL_EXT_texture_shared_exponent GL_NV_light_max_exponent GL_ARB_provoking_vertex GL_ARB_texture_env_crossbar GL_APPLE_packed_pixels GL_ATI_blend_equation_separate GL_ARB_depth_clamp GL_ARB_draw_buffers GL_ARB_draw_buffers_blend GL_ARB_texture_multisample GL_EXT_framebuffer_multisample_blit_scaled GL_EXT_draw_instanced GL_ARB_point_sprite GL_EXT_shader_integer_mix GL_EXT_texture_object GL_IBM_texture_mirrored_repeat GL_ARB_internalformat_query GL_ARB_timer_query GL_ARB_ES2_compatibility GL_EXT_packed_pixels GL_EXT_vertex_array GL_ARB_get_program_binary GL_ARB_texture_cube_map GL_ARB_shader_group_vote GL_EXT_texture_filter_anisotropic GL_ARB_copy_buffer GL_EXT_compiled_vertex_array GL_EXT_blend_minmax GL_EXT_texture_env_dot3 GL_ARB_window_pos GL_ARB_transform_feedback2 GL_ARB_invalidate_subdata GL_ARB_texture_compression GL_ARB_tra
 nsform_feedback_overflow_query GL_SUN_multi_draw_arrays GL_ARB_half_float_vertex GL_EXT_gpu_program_parameters GL_EXT_framebuffer_blit GL_IBM_multimode_draw_arrays GL_ARB_texture_compression_rgtc GL_ARB_sampler_objects GL_NV_primitive_restart GL_ARB_seamless_cube_map GL_ARB_texture_storage_multisample GL_EXT_bgra GL_EXT_framebuffer_sRGB GL_ARB_get_texture_sub_image GL_INGR_blend_func_separate GL_ARB_texture_env_combine GL_EXT_texture3D GL_ARB_vertex_array_object GL_EXT_provoking_vertex
qt.scenegraph.general: Max Texture Size:  8192
qt.scenegraph.general: Debug context:     false


WorkerBase::loop() normal exit, fds[0].revents & POLLIN = trueWorkerBase::loop() normal exit, fds[0].revents & POLLIN = trueWorkerBase::loop() normal exit, fds[0].revents & POLLIN = trueWorkerBase::loop() normal exit, fds[0].revents & POLLIN = trueWorkerBase::loop() normal exit, fds[0].revents & POLLIN = trueWorkerBase::loop() normal exit, fds[0].revents & POLLIN = truesuccess to create child process,status is 0.
zoom exited normally.
run zoom successfully,exit code is 0.
ZoomLauncher exit.
charles@jhegaala:~$ locate zoom | egrep /zoom$ | xargs ls -dl
drwxr-xr-x  3 charles charles     4096 Mar 28  2020 /home/charles/.cache/zoom
drwxrwxr-x 20 root    root       20480 Jun 13 11:42 /opt/zoom
-rwxrwxr-x  1 root    root    55682696 Jun  3 06:43 /opt/zoom/zoom
lrwxrwxrwx  1 root    root          22 Jun  3 06:43 /usr/bin/zoom -> /opt/zoom/ZoomLauncher
drwxrwxr-x  2 root    root        4096 Jun 13 11:42 /usr/share/doc/zoom
charles@jhegaala:~$
--------------------------------------------------




-- 
Does anybody read signatures any more?

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

[toc] | [prev] | [next] | [standalone]

#227927

I have zoom on a couple Debian 10 machines. Both are Mate desktop
Both work as expected.

this one opens the zoom window using $ zoom in a terminal
and by using the Mate launcher (/usr/bin/zoom %U)


On 10/17/20 1:23 PM, peter@easthope.ca wrote:
> Does anyone have Zoom working in Debian 10?
>
> Here it produces empty windows.  Visible toward the right in this
> screenshot.  http://easthope.ca/Zoom.png
>
> This is the entire output after starting in a terminal and then
> exiting.
>
> peter@joule:~$ zoom
> peter@joule:~$
>
> Thx,                       ... P.
>

[toc] | [prev] | [next] | [standalone]

#227928

On 10/17/20 4:23 PM, peter@easthope.ca wrote:
> Does anyone have Zoom working in Debian 10?

Working fine here. Did you set up the Microsoft repo?

-- 
Carl Fink                           nitpicking@nitpicking.com

Read my blog at blog.nitpicking.com.  Reviews!  Observations!

[toc] | [prev] | [next] | [standalone]

#227929

Carl Fink writes:
> On 10/17/20 4:23 PM, peter@easthope.ca wrote:
> > Does anyone have Zoom working in Debian 10?
> 
> Working fine here. Did you set up the Microsoft repo?
>

Working fine with my wife's Buster; used extensively for months,
(daily,) with no problems.

Installed from zoom_amd64.deb obtained from the Zoom site, with
standard "apt install zoom_amd64.deb".

    John

-- 

John Conover, conover@rahul.net, http://www.johncon.com/

[toc] | [prev] | [next] | [standalone]

#227930

On Sun, 18 Oct 2020 at 08:03, <peter@easthope.ca> wrote:

> Does anyone have Zoom working in Debian 10?

Yes. I downloaded
  zoom_amd64-5.0.413237.0524.deb
from here
  https://zoom.us/download?os=linux
and installed it using apt (to provide dependencies).

Because zoom is not trusted software, I did this in a separate primary
partition where I made a clean minimal install of Debian with LXDE,
used only for zoom.

That install has no LUKS tools installed. All my other activities on
that machine are inside a LUKS volume and so are completely
inaccessible to any local snooping attempts by zoom.

[toc] | [prev] | [next] | [standalone]

#227935

On 10/17/20, David <bouncingcats@gmail.com> wrote:
> On Sun, 18 Oct 2020 at 08:03, <peter@easthope.ca> wrote:
>
>> Does anyone have Zoom working in Debian 10?
>
> Yes. I downloaded
>   zoom_amd64-5.0.413237.0524.deb
> from here
>   https://zoom.us/download?os=linux
> and installed it using apt (to provide dependencies).
>
> Because zoom is not trusted software, I did this in a separate primary
> partition where I made a clean minimal install of Debian with LXDE,
> used only for zoom.

I consider this important. Not trusted and not free/open-source -
which ultimately is one and the same thing...

I've been forced to install it in some machines for employers
imposition, and turned to the flatpak-flathub way in order to attain
some level of security through sandbox. It works fine.

Now I ask: is this enough?, anyone have some info about it?

Thanks a lot. Best regards.

[toc] | [prev] | [next] | [standalone]

#227938

On 10/17/20 17:47, David wrote:
> On Sun, 18 Oct 2020 at 08:03, <peter@easthope.ca> wrote:
> 
>> Does anyone have Zoom working in Debian 10?
> 
> Yes. I downloaded
>   zoom_amd64-5.0.413237.0524.deb
> from here
>   https://zoom.us/download?os=linux
> and installed it using apt (to provide dependencies).

Zoom has had security issues in the past and, like all large packages,
will have them in the future. It is updated often (recently, every
couple of weeks or so) and probably should be kept up to date. The
current version as of 17 Oct is 5.3.472687.1012.

I've been running Zoom successfully under Buster since the beginning of
April, through 13 versions beginning with 3.5, with only one issue,
inoperable audio between users of different versions (I think between
3.5 and 5.0). It seems to be generally  stable and well behaved, and
interoperates well between Debian and Ubuntu, Windows, and Mac,
including IPads and IPhones. It has an Android version

It installs easily in /opt/zoom, with a small number of files under
/usr. Its files are owned by root, but has no setuid or setgid files,
and as far as I can tell runs with the UID and GID of whoever starts it.
It creates a number of files under ~/zoom.

I suspect it could be set up and run with an unprivileged owner and
group, but have made no effort to do so. A less intrusive (on the
install process) approach would be to confine it with selinux, something
I ma get to shortly. Apparmor as installed and running by default on
Debian 10 has no apparent problem with it.

Regards,
Tom Dial

> 
> Because zoom is not trusted software, I did this in a separate primary
> partition where I made a clean minimal install of Debian with LXDE,
> used only for zoom.
> 
> That install has no LUKS tools installed. All my other activities on
> that machine are inside a LUKS volume and so are completely
> inaccessible to any local snooping attempts by zoom.
> 

[toc] | [prev] | [next] | [standalone]

#227931

On 10/17/20 1:23 PM, peter@easthope.ca wrote:
> Does anyone have Zoom working in Debian 10?
>
> Here it produces empty windows.  Visible toward the right in this
> screenshot.  http://easthope.ca/Zoom.png
>
> This is the entire output after starting in a terminal and then
> exiting.
>
> peter@joule:~$ zoom
> peter@joule:~$
>
> Thx,                       ... P.
>
When I start Zoom using the command line, I get a single window with 
options to join or start a meeting, schedule a meeting or share screen.  
Plus additional choices, but the point is, I see nothing like what your 
screenshot looks like.

I've seen the browser part only when I click on a link in an email invite.

As for exiting, so long as Zoom considers it a normal exit, it will give 
an exit status of zero and you will simply see the next prompt.  That is 
as expected.

More details on exactly what you are doing and how you are getting your 
environment set up would be helpful.

Bob

[toc] | [prev] | [next] | [standalone]

#227988

From: Bob McGowan <ramjr0915@gmail.com>
Date: Sat, 17 Oct 2020 18:18:18 -0700
> I've seen the browser part only when I click on a link in an email 
> invite.

I shouldn't have included the browser window.  Not really pertinent.

> As for exiting, so long as Zoom considers it a normal exit, it will 
> give an exit status of zero and you will simply see the next prompt. 
> That is as expected.

At least one earlier reply had output in the launching terminal.  Here 
nothing in the terminal.  No exit status.  Nothing.

> More details on exactly what you are doing and how you are getting 
> your environment set up would be helpful. 

Obvious factor: replies mention 64 bit machines.  32 b here.  Anyone 
have Zoom running on a 32 b machine with Debian 10?

LXDE environment here.  Installed strictly according to the 
instructions at zoom.us.  Used apt or apt-get.  Checked all the 
dependancies specified in zoom.us.

I found nothing to configure zoom.  I guess a working zoom window 
might have an edit or preferences button.  No such thing here.

From: A_Man_Without_Clue <love.chaser@gmail.com> 
Date: Sun, 18 Oct 2020 12:09:52 +0900 
Message-id: <d10950be-3bc9-a32d-41b4-717d82a3b495@gmail.com> 
> Mine is working fine except it pops up occasionally for no reason. Quite 
> annoying though.

The automatic startup happens here; about every 30 minutes. The window 
is always empty.

Seems I should carefully work through the installation again.  
Wondering whether I am the only person try a 32 bit machine.

Thanks for all the feedback,                     ... P.



-- 
Tel: +1 604 670 0140            Bcc: peter at easthope. ca

[toc] | [prev] | [next] | [standalone]

#227989

On Mon, Oct 19, 2020 at 12:57:52PM -0700, peter@easthope.ca wrote:
>Obvious factor: replies mention 64 bit machines.  32 b here.  Anyone
>have Zoom running on a 32 b machine with Debian 10?

Probably not many, if any. I'd strongly recommend switching to the amd64 
distribution for a variety of reasons.

[toc] | [prev] | [next] | [standalone]

#228107

From: Michael Stone <mstone@debian.org>
Date: Mon, 19 Oct 2020 17:08:10 -0400
> I'd strongly recommend switching to the amd64 distribution for a variety of reasons. 

Reasonable advice but for all other needs, the old machine serves 
well.  

A mobile data account includes an Android-Alcatel tablet.  Zoom can be 
used on that.  The contamination of the Debian system with 
proprietary software is avoided.

Thanks,                         ... P.


  

-- 
Tel: +1 604 670 0140            Bcc: peter at easthope. ca

[toc] | [prev] | [next] | [standalone]

#228115

On Thu, Oct 22, 2020 at 06:08:23AM -0700, peter@easthope.ca wrote:
>From: Michael Stone <mstone@debian.org>
>Date: Mon, 19 Oct 2020 17:08:10 -0400
>> I'd strongly recommend switching to the amd64 distribution for a variety of reasons.
>
>Reasonable advice but for all other needs, the old machine serves
>well.

I'd assumed it was just a machine that could run amd64 but had i386 on 
it for legacy reasons. If it's really a machine that's too old for amd64 
I'd be amazed if zoom could possibly work on it.

[toc] | [prev] | [next] | [standalone]

#227999

On 20/10/2020 04:57, peter@easthope.ca wrote:
> From: Bob McGowan <ramjr0915@gmail.com>
> Date: Sat, 17 Oct 2020 18:18:18 -0700
>> As for exiting, so long as Zoom considers it a normal exit, it will
>> give an exit status of zero and you will simply see the next prompt.
>> That is as expected.
> 
> At least one earlier reply had output in the launching terminal.  Here
> nothing in the terminal.  No exit status.  Nothing.
Off the main topic, but the exit status of a command does not appear in  
the terminal. To see it, run:
echo $?

-- 
John

[toc] | [prev] | [next] | [standalone]

#228012

John Crawley wrote: 
> On 20/10/2020 04:57, peter@easthope.ca wrote:
> > From: Bob McGowan <ramjr0915@gmail.com>
> > Date: Sat, 17 Oct 2020 18:18:18 -0700
> > > As for exiting, so long as Zoom considers it a normal exit, it will
> > > give an exit status of zero and you will simply see the next prompt.
> > > That is as expected.
> > 
> > At least one earlier reply had output in the launching terminal.  Here
> > nothing in the terminal.  No exit status.  Nothing.
> Off the main topic, but the exit status of a command does not appear in the
> terminal. To see it, run:
> echo $?

I have this in my PS1 definition:

\$(if [[ \$? == 0 ]]; then echo \"+\"; else echo \"-\"; fi)\

Which has the effect of telling me the rough exit status of the
last command in my prompt. 

-dsr-

[toc] | [prev] | [next] | [standalone]

#228013

[Multipart message — attachments visible in raw view] — view raw

Dan Ritter (12020-10-20):
> I have this in my PS1 definition:
> 
> \$(if [[ \$? == 0 ]]; then echo \"+\"; else echo \"-\"; fi)\
> 
> Which has the effect of telling me the rough exit status of the
> last command in my prompt. 

With zsh, I suggest "setopt pritexitvalue".

Regards,

-- 
  Nicoals George

[toc] | [prev] | [next] | [standalone]

#228016

On Tue, Oct 20, 2020 at 06:36:15AM -0400, Dan Ritter wrote:
> I have this in my PS1 definition:
> 
> \$(if [[ \$? == 0 ]]; then echo \"+\"; else echo \"-\"; fi)\
> 
> Which has the effect of telling me the rough exit status of the
> last command in my prompt. 

The weird backslashing tells me you're defining PS1 with double quotes
instead of single quotes, which is weird, and probably indicates that
you're doing even worse things, like dynamically generating pieces of
your PS1... I've seen things... things that no man should see....

Anyway, in addition to the weird quoting and possible abominations
unrevealed, your command substitution forks.  Every time the prompt
is drawn, a new process is forked, just to do that simple "if" check.

The standard workaround for that is to use an array variable with the
two possible outcomes, and a bit of arithmetic.

unicorn:~$ green=$(tput setaf 2) red=$(tput setaf 1) normal=$(tput sgr0)
unicorn:~$ status=(+ -) statcolor=("$green" "$red")
unicorn:~$ PS1='\[${statcolor[!!$?]}\]${status[!!$?]}\[$normal\] \h:\w\$ '
+ unicorn:~$ true
+ unicorn:~$ false
- unicorn:~$ true
+ unicorn:~$ 

(You can't see the colors in the mailing list, but they're there.)

Just remember the basics:

1) Use single quotes around your definition of PS1, because you want all
   of the parts of it to be taken literally, and quoting is already hard
   enough without making it worse.

2) Variable expansions are "free" (do not cost a process fork).  This
   includes variables that are set by PRMOPT_COMMAND, which is the more
   efficient way to set variables dynamically if you *really* need that,
   which you probably don't.

3) Color and other terminal escape codes can and should be stored in
   variables, which you can expand in PS1, as long as the PS1 definition
   is single-quoted.  Don't store raw terminal sequences, because they
   are not the same for all terminals.  This is what tput(1) is for.

4) Terminal escape sequences that don't change the cursor position should
   be enclosed in \[ \] so the shell knows where the cursor is at all
   times.

5) When expanding the index of an indexed array variable, the square
   brackets are a math context.  In a math context, !!$? means "negate
   the previous command's exit status twice".  So, 0 -> 1 -> 0, or
   nonzero -> 0 -> 1.  Thus, !!$? always expands to either 0 or 1.  And
   because it's in single quotes, it shouldn't trip history expansion,
   if you still have history expansion turned on.  (I don't.)

[toc] | [prev] | [next] | [standalone]

#228018

Greg Wooledge wrote: 
> On Tue, Oct 20, 2020 at 06:36:15AM -0400, Dan Ritter wrote:
> > I have this in my PS1 definition:
> > 
> > \$(if [[ \$? == 0 ]]; then echo \"+\"; else echo \"-\"; fi)\
> > 
> > Which has the effect of telling me the rough exit status of the
> > last command in my prompt. 
> 
> The weird backslashing tells me you're defining PS1 with double quotes
> instead of single quotes, which is weird, and probably indicates that
> you're doing even worse things, like dynamically generating pieces of
> your PS1... I've seen things... things that no man should see....


Regain some SAN points: none of the rest of it is weird. 

Two lines. First line is a colorized \u@\h:\w\, the second line
is the exit status and \$  


> Anyway, in addition to the weird quoting and possible abominations
> unrevealed, your command substitution forks.  Every time the prompt
> is drawn, a new process is forked, just to do that simple "if" check.
> 
> The standard workaround for that is to use an array variable with the
> two possible outcomes, and a bit of arithmetic.
> 
> unicorn:~$ green=$(tput setaf 2) red=$(tput setaf 1) normal=$(tput sgr0)
> unicorn:~$ status=(+ -) statcolor=("$green" "$red")
> unicorn:~$ PS1='\[${statcolor[!!$?]}\]${status[!!$?]}\[$normal\] \h:\w\$ '
> + unicorn:~$ true
> + unicorn:~$ false
> - unicorn:~$ true
> + unicorn:~$ 

Thanks, When I get around to redoing my PS1, I'll use that and
fix the quoting.

-dsr-

[toc] | [prev] | [next] | [standalone]

#228027 — Re: shells (was Re: Zoom.)

Top posting intentionally as I don't think any (or much) context is required.

I am always impressed with Greg's knowledge of the Bash shell (maybe all 
shells), but, wow, Bash seems like a convoluted mess to keep track of all the 
little details / gotchas.

Is there a shell that is better in that respect?  Maybe the c-shell?  I don't 
like c (because I have a hard time programming in it), but if the c-shell has 
less intricacies (and is quite consistent with the c language), then maybe 
(for me) it is worth switching to (someday ;-)

Nothing new below this line.

On Tuesday, October 20, 2020 07:36:39 AM Greg Wooledge wrote:
> The weird backslashing tells me you're defining PS1 with double quotes
> instead of single quotes, which is weird, and probably indicates that
> you're doing even worse things, like dynamically generating pieces of
> your PS1... I've seen things... things that no man should see....
> 
> Anyway, in addition to the weird quoting and possible abominations
> unrevealed, your command substitution forks.  Every time the prompt
> is drawn, a new process is forked, just to do that simple "if" check.
> 
> The standard workaround for that is to use an array variable with the
> two possible outcomes, and a bit of arithmetic.
> 
> unicorn:~$ green=$(tput setaf 2) red=$(tput setaf 1) normal=$(tput sgr0)
> unicorn:~$ status=(+ -) statcolor=("$green" "$red")
> unicorn:~$ PS1='\[${statcolor[!!$?]}\]${status[!!$?]}\[$normal\] \h:\w\$ '
> + unicorn:~$ true
> + unicorn:~$ false
> - unicorn:~$ true
> + unicorn:~$
> 
> (You can't see the colors in the mailing list, but they're there.)
> 
> Just remember the basics:
> 
> 1) Use single quotes around your definition of PS1, because you want all
>    of the parts of it to be taken literally, and quoting is already hard
>    enough without making it worse.
> 
> 2) Variable expansions are "free" (do not cost a process fork).  This
>    includes variables that are set by PRMOPT_COMMAND, which is the more
>    efficient way to set variables dynamically if you *really* need that,
>    which you probably don't.
> 
> 3) Color and other terminal escape codes can and should be stored in
>    variables, which you can expand in PS1, as long as the PS1 definition
>    is single-quoted.  Don't store raw terminal sequences, because they
>    are not the same for all terminals.  This is what tput(1) is for.
> 
> 4) Terminal escape sequences that don't change the cursor position should
>    be enclosed in \[ \] so the shell knows where the cursor is at all
>    times.
> 
> 5) When expanding the index of an indexed array variable, the square
>    brackets are a math context.  In a math context, !!$? means "negate
>    the previous command's exit status twice".  So, 0 -> 1 -> 0, or
>    nonzero -> 0 -> 1.  Thus, !!$? always expands to either 0 or 1.  And
>    because it's in single quotes, it shouldn't trip history expansion,
>    if you still have history expansion turned on.  (I don't.)

[toc] | [prev] | [next] | [standalone]

#228029 — Re: shells (was Re: Zoom.)

[Multipart message — attachments visible in raw view] — view raw

rhkramer@gmail.com (12020-10-20):
> Top posting intentionally as I don't think any (or much) context is required.

Then you could just omit it.

> I am always impressed with Greg's knowledge of the Bash shell (maybe all 
> shells), but, wow, Bash seems like a convoluted mess to keep track of all the 
> little details / gotchas.
> 
> Is there a shell that is better in that respect?  Maybe the c-shell?  I don't 
> like c (because I have a hard time programming in it), but if the c-shell has 
> less intricacies (and is quite consistent with the c language), then maybe 
> (for me) it is worth switching to (someday ;-)

I strongly suggest zsh.

Among other advantages, it will not re-expand and re-split variables,
even without quotes, and it has a powerful globbing mechanism, with
recursive search and filters on files properties (size, ownership,
mode).

Regards,

-- 
  Nicolas George

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | linux.debian.user

csiph-web