Skip to main content
Topic solved
This topic has been marked as solved and requires no further attention.
Topic: [SOLVED] Viber crashes (Read 4695 times) previous topic - next topic
0 Members and 3 Guests are viewing this topic.

Re: Viber crashes

Reply #15
EDIT: put here output from
Code: [Select]
 ldd /opt/viber/Viber

Code: [Select]
	linux-vdso.so.1 (0x00007ffe403db000)
libXss.so.1 => /usr/lib/libXss.so.1 (0x00007f330de23000)
libqrencode.so => /opt/viber/lib/libqrencode.so (0x00007f330dc0f000)
libXext.so.6 => /usr/lib/libXext.so.6 (0x00007f330dbfa000)
libX11.so.6 => /usr/lib/libX11.so.6 (0x00007f330dab9000)
libQt5Sql.so.5 => /opt/viber/lib/libQt5Sql.so.5 (0x00007f330d86f000)
libQt5Multimedia.so.5 => /opt/viber/lib/libQt5Multimedia.so.5 (0x00007f330d557000)
libQt5WebSockets.so.5 => /opt/viber/lib/libQt5WebSockets.so.5 (0x00007f330d324000)
libQt5WebEngine.so.5 => /opt/viber/lib/libQt5WebEngine.so.5 (0x00007f330d0b1000)
libQt5DBus.so.5 => /opt/viber/lib/libQt5DBus.so.5 (0x00007f330ce21000)
libpthread.so.0 => /usr/lib/libpthread.so.0 (0x00007f330cdff000)
libViberRTC.so => /opt/viber/lib/libViberRTC.so (0x00007f330cbb1000)
libicui18n.so.55 => /opt/viber/lib/libicui18n.so.55 (0x00007f330c6f5000)
libicuuc.so.55 => /opt/viber/lib/libicuuc.so.55 (0x00007f330c340000)
libQt5Quick.so.5 => /opt/viber/lib/libQt5Quick.so.5 (0x00007f330bbf6000)
libQt5Qml.so.5 => /opt/viber/lib/libQt5Qml.so.5 (0x00007f330b5a3000)
libQt5Network.so.5 => /opt/viber/lib/libQt5Network.so.5 (0x00007f330b1f3000)
libQt5Widgets.so.5 => /opt/viber/lib/libQt5Widgets.so.5 (0x00007f330a975000)
libQt5Gui.so.5 => /opt/viber/lib/libQt5Gui.so.5 (0x00007f330a0c7000)
libQt5Core.so.5 => /opt/viber/lib/libQt5Core.so.5 (0x00007f3309898000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00007f33096bb000)
libm.so.6 => /usr/lib/libm.so.6 (0x00007f3309575000)
libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x00007f330955b000)
libc.so.6 => /usr/lib/libc.so.6 (0x00007f3309392000)
/lib64/ld-linux-x86-64.so.2 => /usr/lib64/ld-linux-x86-64.so.2 (0x00007f330de4b000)
libz.so.1 => /usr/lib/libz.so.1 (0x00007f3309378000)
libxcb.so.1 => /usr/lib/libxcb.so.1 (0x00007f330934c000)
libdl.so.2 => /usr/lib/libdl.so.2 (0x00007f3309346000)
libpulse.so.0 => /usr/lib/libpulse.so.0 (0x00007f33092f1000)
libQt5WebEngineCore.so.5 => /opt/viber/lib/libQt5WebEngineCore.so.5 (0x00007f3301b5f000)
libQt5WebChannel.so.5 => /opt/viber/lib/libQt5WebChannel.so.5 (0x00007f330193d000)
libdbus-1.so.3 => /usr/lib/libdbus-1.so.3 (0x00007f33018e6000)
libicudata.so.55 => /opt/viber/lib/libicudata.so.55 (0x00007f32ffe2e000)
libQt5QmlModels.so.5 => /opt/viber/lib/libQt5QmlModels.so.5 (0x00007f32ffb91000)
libGL.so.1 => /usr/lib/libGL.so.1 (0x00007f32ffb0b000)
libpng12.so.0 => /opt/viber/lib/libpng12.so.0 (0x00007f32ff8e4000)
libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0x00007f32ff7ae000)
libXau.so.6 => /usr/lib/libXau.so.6 (0x00007f32ff7a9000)
libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0x00007f32ff7a1000)
libpulsecommon-14.0.so => /usr/lib/pulseaudio/libpulsecommon-14.0.so (0x00007f32ff71d000)
libQt5Positioning.so.5 => /opt/viber/lib/libQt5Positioning.so.5 (0x00007f32ff485000)
librt.so.1 => /usr/lib/librt.so.1 (0x00007f32ff478000)
libnss3.so => /usr/lib/libnss3.so (0x00007f32ff340000)
libnssutil3.so => /usr/lib/libnssutil3.so (0x00007f32ff30d000)
libnspr4.so => /usr/lib/libnspr4.so (0x00007f32ff2ca000)
libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x00007f32ff1f6000)
libexpat.so.1 => /usr/lib/libexpat.so.1 (0x00007f32ff1c7000)
libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0x00007f32ff17a000)
libXcomposite.so.1 => /opt/viber/lib/libXcomposite.so.1 (0x00007f32fef76000)
libXdamage.so.1 => /opt/viber/lib/libXdamage.so.1 (0x00007f32fed72000)
libXfixes.so.3 => /usr/lib/libXfixes.so.3 (0x00007f32fed69000)
libasound.so.2 => /usr/lib/libasound.so.2 (0x00007f32fec8a000)
libxml2.so.2 => /usr/lib/libxml2.so.2 (0x00007f32feb1c000)
libxslt.so.1 => /usr/lib/libxslt.so.1 (0x00007f32fead8000)
libelogind.so.0 => /usr/lib/libelogind.so.0 (0x00007f32fea4c000)
libGLdispatch.so.0 => /usr/lib/libGLdispatch.so.0 (0x00007f32fe995000)
libGLX.so.0 => /usr/lib/libGLX.so.0 (0x00007f32fe962000)
libpcre.so.1 => /usr/lib/libpcre.so.1 (0x00007f32fe8f0000)
libsndfile.so.1 => /usr/lib/libsndfile.so.1 (0x00007f32fe872000)
libasyncns.so.0 => /usr/lib/libasyncns.so.0 (0x00007f32fe86a000)
libplds4.so => /usr/lib/libplds4.so (0x00007f32fe865000)
libplc4.so => /usr/lib/libplc4.so (0x00007f32fe85e000)
libbz2.so.1.0 => /usr/lib/libbz2.so.1.0 (0x00007f32fe84b000)
libpng16.so.16 => /usr/lib/libpng16.so.16 (0x00007f32fe812000)
libharfbuzz.so.0 => /usr/lib/libharfbuzz.so.0 (0x00007f32fe743000)
libicuuc.so.67 => /usr/lib/libicuuc.so.67 (0x00007f32fe55c000)
liblzma.so.5 => /usr/lib/liblzma.so.5 (0x00007f32fe534000)
libFLAC.so.8 => /usr/lib/libFLAC.so.8 (0x00007f32fe4f5000)
libogg.so.0 => /usr/lib/libogg.so.0 (0x00007f32fe4ea000)
libvorbis.so.0 => /usr/lib/libvorbis.so.0 (0x00007f32fe4ba000)
libvorbisenc.so.2 => /usr/lib/libvorbisenc.so.2 (0x00007f32fe40f000)
libresolv.so.2 => /usr/lib/libresolv.so.2 (0x00007f32fe3f5000)
libgraphite2.so.3 => /usr/lib/libgraphite2.so.3 (0x00007f32fe3d0000)
libicudata.so.67 => /usr/lib/libicudata.so.67 (0x00007f32fc8b9000)

Re: Viber crashes

Reply #16
Code: [Select]
	linux-vdso.so.1 (0x00007ffe403db000)
libXss.so.1 => /usr/lib/libXss.so.1 (0x00007f330de23000)
libqrencode.so => /opt/viber/lib/libqrencode.so (0x00007f330dc0f000)
libXext.so.6 => /usr/lib/libXext.so.6 (0x00007f330dbfa000)
libX11.so.6 => /usr/lib/libX11.so.6 (0x00007f330dab9000)
libQt5Sql.so.5 => /opt/viber/lib/libQt5Sql.so.5 (0x00007f330d86f000)
libQt5Multimedia.so.5 => /opt/viber/lib/libQt5Multimedia.so.5 (0x00007f330d557000)
libQt5WebSockets.so.5 => /opt/viber/lib/libQt5WebSockets.so.5 (0x00007f330d324000)
libQt5WebEngine.so.5 => /opt/viber/lib/libQt5WebEngine.so.5 (0x00007f330d0b1000)
libQt5DBus.so.5 => /opt/viber/lib/libQt5DBus.so.5 (0x00007f330ce21000)
libpthread.so.0 => /usr/lib/libpthread.so.0 (0x00007f330cdff000)
libViberRTC.so => /opt/viber/lib/libViberRTC.so (0x00007f330cbb1000)
libicui18n.so.55 => /opt/viber/lib/libicui18n.so.55 (0x00007f330c6f5000)
libicuuc.so.55 => /opt/viber/lib/libicuuc.so.55 (0x00007f330c340000)
libQt5Quick.so.5 => /opt/viber/lib/libQt5Quick.so.5 (0x00007f330bbf6000)
libQt5Qml.so.5 => /opt/viber/lib/libQt5Qml.so.5 (0x00007f330b5a3000)
libQt5Network.so.5 => /opt/viber/lib/libQt5Network.so.5 (0x00007f330b1f3000)
libQt5Widgets.so.5 => /opt/viber/lib/libQt5Widgets.so.5 (0x00007f330a975000)
libQt5Gui.so.5 => /opt/viber/lib/libQt5Gui.so.5 (0x00007f330a0c7000)
libQt5Core.so.5 => /opt/viber/lib/libQt5Core.so.5 (0x00007f3309898000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00007f33096bb000)
libm.so.6 => /usr/lib/libm.so.6 (0x00007f3309575000)
libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x00007f330955b000)
libc.so.6 => /usr/lib/libc.so.6 (0x00007f3309392000)
/lib64/ld-linux-x86-64.so.2 => /usr/lib64/ld-linux-x86-64.so.2 (0x00007f330de4b000)
libz.so.1 => /usr/lib/libz.so.1 (0x00007f3309378000)
libxcb.so.1 => /usr/lib/libxcb.so.1 (0x00007f330934c000)
libdl.so.2 => /usr/lib/libdl.so.2 (0x00007f3309346000)
libpulse.so.0 => /usr/lib/libpulse.so.0 (0x00007f33092f1000)
libQt5WebEngineCore.so.5 => /opt/viber/lib/libQt5WebEngineCore.so.5 (0x00007f3301b5f000)
libQt5WebChannel.so.5 => /opt/viber/lib/libQt5WebChannel.so.5 (0x00007f330193d000)
libdbus-1.so.3 => /usr/lib/libdbus-1.so.3 (0x00007f33018e6000)
libicudata.so.55 => /opt/viber/lib/libicudata.so.55 (0x00007f32ffe2e000)
libQt5QmlModels.so.5 => /opt/viber/lib/libQt5QmlModels.so.5 (0x00007f32ffb91000)
libGL.so.1 => /usr/lib/libGL.so.1 (0x00007f32ffb0b000)
libpng12.so.0 => /opt/viber/lib/libpng12.so.0 (0x00007f32ff8e4000)
libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0x00007f32ff7ae000)
libXau.so.6 => /usr/lib/libXau.so.6 (0x00007f32ff7a9000)
libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0x00007f32ff7a1000)
libpulsecommon-14.0.so => /usr/lib/pulseaudio/libpulsecommon-14.0.so (0x00007f32ff71d000)
libQt5Positioning.so.5 => /opt/viber/lib/libQt5Positioning.so.5 (0x00007f32ff485000)
librt.so.1 => /usr/lib/librt.so.1 (0x00007f32ff478000)
libnss3.so => /usr/lib/libnss3.so (0x00007f32ff340000)
libnssutil3.so => /usr/lib/libnssutil3.so (0x00007f32ff30d000)
libnspr4.so => /usr/lib/libnspr4.so (0x00007f32ff2ca000)
libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x00007f32ff1f6000)
libexpat.so.1 => /usr/lib/libexpat.so.1 (0x00007f32ff1c7000)
libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0x00007f32ff17a000)
libXcomposite.so.1 => /opt/viber/lib/libXcomposite.so.1 (0x00007f32fef76000)
libXdamage.so.1 => /opt/viber/lib/libXdamage.so.1 (0x00007f32fed72000)
libXfixes.so.3 => /usr/lib/libXfixes.so.3 (0x00007f32fed69000)
libasound.so.2 => /usr/lib/libasound.so.2 (0x00007f32fec8a000)
libxml2.so.2 => /usr/lib/libxml2.so.2 (0x00007f32feb1c000)
libxslt.so.1 => /usr/lib/libxslt.so.1 (0x00007f32fead8000)
libelogind.so.0 => /usr/lib/libelogind.so.0 (0x00007f32fea4c000)
libGLdispatch.so.0 => /usr/lib/libGLdispatch.so.0 (0x00007f32fe995000)
libGLX.so.0 => /usr/lib/libGLX.so.0 (0x00007f32fe962000)
libpcre.so.1 => /usr/lib/libpcre.so.1 (0x00007f32fe8f0000)
libsndfile.so.1 => /usr/lib/libsndfile.so.1 (0x00007f32fe872000)
libasyncns.so.0 => /usr/lib/libasyncns.so.0 (0x00007f32fe86a000)
libplds4.so => /usr/lib/libplds4.so (0x00007f32fe865000)
libplc4.so => /usr/lib/libplc4.so (0x00007f32fe85e000)
libbz2.so.1.0 => /usr/lib/libbz2.so.1.0 (0x00007f32fe84b000)
libpng16.so.16 => /usr/lib/libpng16.so.16 (0x00007f32fe812000)
libharfbuzz.so.0 => /usr/lib/libharfbuzz.so.0 (0x00007f32fe743000)
libicuuc.so.67 => /usr/lib/libicuuc.so.67 (0x00007f32fe55c000)
liblzma.so.5 => /usr/lib/liblzma.so.5 (0x00007f32fe534000)
libFLAC.so.8 => /usr/lib/libFLAC.so.8 (0x00007f32fe4f5000)
libogg.so.0 => /usr/lib/libogg.so.0 (0x00007f32fe4ea000)
libvorbis.so.0 => /usr/lib/libvorbis.so.0 (0x00007f32fe4ba000)
libvorbisenc.so.2 => /usr/lib/libvorbisenc.so.2 (0x00007f32fe40f000)
libresolv.so.2 => /usr/lib/libresolv.so.2 (0x00007f32fe3f5000)
libgraphite2.so.3 => /usr/lib/libgraphite2.so.3 (0x00007f32fe3d0000)
libicudata.so.67 => /usr/lib/libicudata.so.67 (0x00007f32fc8b9000)
same as my

Re: Viber crashes

Reply #17
no second Intel graphics card?

can you try "nouveau" driver instead nvidia?
pacman -S xf86-video-nouveau (editing Xorg files necessary) https://wiki.archlinux.org/index.php/Nouveau
Nope, I only have a separate video card. I can try to setup nouveau during the weekend and will post what I find out.

 

Re: Viber crashes

Reply #18
Wild guess: make a copy of /etc/machine-id and see if it changes after reboot. You might also have one in /var/lib/dbus/machine-id, if so check that too.
If  machine-id is unchanged, post a strace -s 128 /opt/viber/Viber at https://paste.artixlinux.org.

Also, do yourself a favour and run all binary spyware blobs inside a fire jail or something. This actually might solve the crash too.

Re: Viber crashes

Reply #19
Just to report that I tried using Viber on my laptop, which uses ATI Mobility Radeon HD 5470, using the same account and it works even after reboot. So it might be the NVIDIA driver which is messing with Viber. I'll try to switch to nouveau and post here what I find out. Also:

Wild guess: make a copy of /etc/machine-id and see if it changes after reboot. You might also have one in /var/lib/dbus/machine-id, if so check that too.
If  machine-id is unchanged, post a strace -s 128 /opt/viber/Viber at https://paste.artixlinux.org.
Will do and post here after I check.

Also, do yourself a favour and run all binary spyware blobs inside a fire jail or something. This actually might solve the crash too.
Thanks, I'll try that.

Re: Viber crashes

Reply #20
Ok, just checked and machine-id is indeed changing upon reboot. Firejail didn't make a difference on my desktop. Also I tried to switch to nouveau, by removing all nvidia* packages and the blacklisting of nouveau in kernel and rebooting, and it didn't help. Here's the output of lsmod | grep 'nouveau\|nvidia":
Code: [Select]
nouveau              2355200  5
mxm_wmi                16384  1 nouveau
wmi                    36864  2 mxm_wmi,nouveau
i2c_algo_bit           16384  1 nouveau
ttm                   122880  1 nouveau
drm_kms_helper        266240  1 nouveau
drm                   585728  8 drm_kms_helper,ttm,nouveau
agpgart                53248  3 ttm,nouveau,drm
And inxi -F:
Code: [Select]
System:    Host: meneltarma Kernel: 5.9.10-artix1-1 x86_64 bits: 64 Desktop: dwm 6.2 Distro: Artix Linux 
Machine:   Type: Desktop System: Gigabyte product: N/A v: N/A serial: <superuser/root required>
           Mobo: Gigabyte model: H61M-DS2V v: x.x serial: <superuser/root required> UEFI: American Megatrends v: F5
           date: 04/17/2013
CPU:       Info: Quad Core model: Intel Core i5-3450 bits: 64 type: MCP L2 cache: 6144 KiB
           Speed: 3350 MHz min/max: 1600/3500 MHz Core speeds (MHz): 1: 3351 2: 3336 3: 3468 4: 3468
Graphics:  Device-1: NVIDIA GK107 [GeForce GTX 650] driver: nouveau v: kernel
           Display: server: X.Org 1.20.9 driver: nouveau unloaded: modesetting,vesa resolution: 1920x1080~60Hz
           OpenGL: renderer: NVE7 v: 4.3 Mesa 20.2.3
Audio:     Device-1: Intel 6 Series/C200 Series Family High Definition Audio driver: snd_hda_intel
           Device-2: NVIDIA GK107 HDMI Audio driver: snd_hda_intel
           Sound Server: ALSA v: k5.9.10-artix1-1
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: 90:2b:34:4d:4f:6a
Drives:    Local Storage: total: 1.82 TiB used: 47.27 GiB (2.5%)
           ID-1: /dev/sda vendor: Western Digital model: WD20EZRZ-00Z5HB0 size: 1.82 TiB
Partition: ID-1: / size: 91.17 GiB used: 11.87 GiB (13.0%) fs: ext4 dev: /dev/sda6
           ID-2: /home size: 772.53 GiB used: 35.37 GiB (4.6%) fs: ext4 dev: /dev/sda7
Swap:      ID-1: swap-1 type: partition size: 7.45 GiB used: 0 KiB (0.0%) dev: /dev/sda5
Sensors:   System Temperatures: cpu: 29.8 C mobo: 27.8 C gpu: nouveau temp: 35.0 C
           Fan Speeds (RPM): N/A gpu: nouveau fan: 1350
Info:      Processes: 208 Uptime: 4m Memory: 7.74 GiB used: 482.0 MiB (6.1%) Shell: Bash inxi: 3.1.07

Re: Viber crashes

Reply #21
something is wrong set  in your computer, because the viber crash ... unfortunately I'm not able to remotely detect what :( I'm running out of ideas for what it could be.

Re: Viber crashes

Reply #22
Well, I didn't do anything special (to my knowing). The only difference is that Artix on my laptop was installed from i3-s6 iso, (and then regularly upgraded), and on my desktop from base-s6 iso. On both I have pretty much the same setup with dwm, except, of course, that laptop has a different video card.

I can post the strace of viber, if that will help. Also, I checked my laptop (where Viber works) and it also has machine-id changed upon reboot. The difference is that laptop also has /var/lib/dbus/machine-id (with a different id than /etc/machine-id) and the desktop only has /etc/machine-id.

P.S: I tried creating the paste with the entire output of trace but I get "413 Request Entity Too Large", so here's the last 100 lines: https://paste.artixlinux.org/view/89578eb9

(I replaced my phone number with XXXXXXX using sed.)

Re: Viber crashes

Reply #23
Ok, just checked and machine-id is indeed changing upon reboot. Firejail didn't make a difference on my desktop.

The machine-id change is a tweak we introduced in /etc/local.d/change-machine-id.start, which runs at every boot. The purpose of this is to avoid Artix systems being traced and identified by a unique ID. Now, if you comment out the dbus-uuidgen lines in that file, fresh-start viber and reboot, what happens?

Re: Viber crashes

Reply #24
Sorry for the late reply. I don't appear to have the /etc/local.d/change-machine-id.start file at all. This is the output of ls:
Code: [Select]
$ ls /etc/local.d/
branding.start  cleanup.start  local.start  local.stop
$
and this is the output of grep uuidgen:
Code: [Select]
$ grep uuidgen /etc/local.d/*
$
Also:
Code: [Select]
$ grep uuidgen /etc/* 2>/dev/null
/etc/services:uuidgen           697/tcp
/etc/services:uuidgen           697/udp
$ grep -ri uuidgen /etc/* 2>/dev/null
/etc/s6/sv/dbus-srv/run:foreground { redirfd -w 1 /etc/machine-id dbus-uuidgen }
/etc/s6/rc/compiled-1606213602/servicedirs/dbus-srv/run.user:foreground { redirfd -w 1 /etc/machine-id dbus-uuidgen }
/etc/s6/rc/compiled-1605466993/servicedirs/dbus-srv/run.user:foreground { redirfd -w 1 /etc/machine-id dbus-uuidgen }
/etc/s6/rc/compiled-1605531063/servicedirs/dbus-srv/run.user:foreground { redirfd -w 1 /etc/machine-id dbus-uuidgen }
/etc/s6/rc/compiled-1606805156/servicedirs/dbus-srv/run.user:foreground { redirfd -w 1 /etc/machine-id dbus-uuidgen }
/etc/s6/rc/compiled-1605369917/servicedirs/dbus-srv/run.user:foreground { redirfd -w 1 /etc/machine-id dbus-uuidgen }
/etc/s6/rc/compiled-1605385859/servicedirs/dbus-srv/run.user:foreground { redirfd -w 1 /etc/machine-id dbus-uuidgen }
/etc/s6/rc/compiled-1605370061/servicedirs/dbus-srv/run.user:foreground { redirfd -w 1 /etc/machine-id dbus-uuidgen }
/etc/s6/rc/compiled-1605385371/servicedirs/dbus-srv/run.user:foreground { redirfd -w 1 /etc/machine-id dbus-uuidgen }
/etc/s6/rc/compiled-1605385977/servicedirs/dbus-srv/run.user:foreground { redirfd -w 1 /etc/machine-id dbus-uuidgen }
/etc/s6/rc/compiled-1605385611/servicedirs/dbus-srv/run.user:foreground { redirfd -w 1 /etc/machine-id dbus-uuidgen }
/etc/s6/rc/compiled-1606805136/servicedirs/dbus-srv/run.user:foreground { redirfd -w 1 /etc/machine-id dbus-uuidgen }
/etc/s6/rc/compiled-1605385956/servicedirs/dbus-srv/run.user:foreground { redirfd -w 1 /etc/machine-id dbus-uuidgen }
/etc/s6/rc/compiled-1605531161/servicedirs/dbus-srv/run.user:foreground { redirfd -w 1 /etc/machine-id dbus-uuidgen }
/etc/s6/rc/compiled-1605385821/servicedirs/dbus-srv/run.user:foreground { redirfd -w 1 /etc/machine-id dbus-uuidgen }
/etc/s6/rc/compiled-1605385910/servicedirs/dbus-srv/run.user:foreground { redirfd -w 1 /etc/machine-id dbus-uuidgen }
/etc/s6/rc/compiled-1605385784/servicedirs/dbus-srv/run.user:foreground { redirfd -w 1 /etc/machine-id dbus-uuidgen }
/etc/services:uuidgen           697/tcp
/etc/services:uuidgen           697/udp
$

Re: Viber crashes

Reply #25
Hm, I had no idea our s6 also played with /etc/machine-id...

Until some s6 expert advises you how to change that, you can in the meantime make /etc/machine-id immutable:
Code: [Select]
# chattr +i /etc/machine-id
and test.

Re: Viber crashes

Reply #26
Yes! This helped, thank you! :D

I am getting an error message now during the boot, about the /etc/machine-id being unwritable, but at least I can run Viber now without it crashing immediately.

Although this is only a temporary workaround, I will mark the topic as solved.

Re: [SOLVED] Viber crashes

Reply #27
And this is a perfect example of how companies use whatever means they can to track us and uniquely identify us, in the pretext of our "safety" and "better services provided" - with "free", closed-source products. This situation was also the intent behind our regularly changing /etc/machine-id.

Don't run viber/skype/any_blob unrestrained, use a container. They feed on your private data. Try to talk your employer into using something open source, there are plenty of excellent solutions out there.

Re: [SOLVED] Viber crashes

Reply #28
I completely agree, and thank you again for introducing firejail to me, I didn't even know something like that is a thing.

I am definitely using firejail to run Viber, which I am sadly not allowed to replace with something like Telegram for my job, but on the other hand it is something only forced during the hopefully temporary work from home in the most recent coronavirus outbreak.

Re: [SOLVED] Viber crashes

Reply #29
Viber is not proprietary like whatsapp? I mean same bullshit?