Viber problem, HELP needed!  [Solved]

Message
Author
User avatar
neogeo
Posts: 85
Joined: Wed Jun 22, 2022 5:39 am

Viber problem, HELP needed!

#1 Post by neogeo »

Hello!
I am using 21.2 KDE Plasma Wildflower and can't run any installed Viber instance. Tried from officiall Viber site .deb installed package, viberappimage, and flatpak installation from MX Package's but no success in running. All of them installed propperly but not to run :(
Any HELP or advice please (need Viber to run).

Here it is my QSI:

Code: Select all

perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
	LANGUAGE = "",
	LC_ALL = (unset),
	LC_TIME = "sr_RS.UTF-8",
	LANG = "en_GB.UTF-8"
    are supported and installed on your system.
perl: warning: Falling back to a fallback locale ("en_GB.UTF-8").

Snapshot created on: 20220411_2300
System:    Kernel: 5.18.0-4mx-amd64 [5.18.16-1~mx21+1] x86_64 bits: 64 compiler: gcc v: 10.2.1 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.18.0-4mx-amd64 
           root=UUID=<filter> ro quiet splash 
           Desktop: KDE Plasma 5.20.5 wm: kwin_x11 vt: 7 dm: SDDM 
           Distro: MX-21.2_KDE-5.16-kernel_x64 Wildflower April 9  2022 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Desktop System: ASUS product: N/A v: N/A serial: <filter> 
           Mobo: ASUSTeK model: PRIME B560M-K v: Rev 1.xx serial: <filter> 
           UEFI: American Megatrends v: 1605 date: 05/13/2022 
CPU:       Info: 6-Core model: Intel Core i5-10400 bits: 64 type: MCP arch: Comet Lake family: 6 
           model-id: A5 (165) stepping: 3 microcode: F0 cache: L2: 12 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 34798 
           Speed: 800 MHz min/max: 800/2900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 
           5: 800 6: 800 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: mmio_stale_data mitigation: Clear CPU buffers; SMT disabled 
           Type: retbleed mitigation: Enhanced IBRS 
           Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 
           mitigation: Enhanced IBRS, IBPB: conditional, RSB filling, PBRSB-eIBRS: SW sequence 
           Type: srbds mitigation: Microcode 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel CometLake-S GT2 [UHD Graphics 630] vendor: ASUSTeK driver: i915 
           v: kernel bus-ID: 00:02.0 chip-ID: 8086:9bc8 class-ID: 0300 
           Display: x11 server: X.Org 1.20.14 compositor: kwin_x11 driver: loaded: modesetting 
           unloaded: fbdev,vesa display-ID: :0 screens: 1 
           Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2") 
           s-diag: 582mm (22.9") 
           Monitor-1: DP-1 res: 1920x1080 hz: 60 dpi: 102 size: 477x268mm (18.8x10.6") 
           diag: 547mm (21.5") 
           OpenGL: renderer: Mesa Intel UHD Graphics 630 (CML GT2) v: 4.6 Mesa 22.0.5 
           direct render: Yes 
Audio:     Device-1: Creative Labs Sound Core3D [Sound Blaster Recon3D / Z-Series] 
           driver: snd_hda_intel v: kernel bus-ID: 02:00.0 chip-ID: 1102:0012 class-ID: 0403 
           Sound Server-1: ALSA v: k5.18.0-4mx-amd64 running: yes 
           Sound Server-2: PulseAudio v: 14.2 running: yes 
Network:   Device-1: Intel Ethernet I219-V vendor: ASUSTeK driver: e1000e v: kernel port: efa0 
           bus-ID: 00:1f.6 chip-ID: 8086:15fa class-ID: 0200 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 1.15 TiB used: 12.96 GiB (1.1%) 
           SMART Message: Unable to run smartctl. Root privileges required. 
           ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Gigabyte model: GP-GSM2NE3512GNTD 
           size: 476.94 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 
           type: SSD serial: <filter> rev: EDFMB0.5 temp: 27.9 C scheme: GPT 
           ID-2: /dev/sda maj-min: 8:0 vendor: Geil model: R3 256GB size: 238.47 GiB block-size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 8A0 
           scheme: GPT 
           ID-3: /dev/sdb maj-min: 8:16 vendor: Toshiba model: MK5061GSYN size: 465.76 GiB 
           block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 7200 
           serial: <filter> rev: 0K scheme: GPT 
Partition: ID-1: / raw-size: 237.98 GiB size: 233.68 GiB (98.20%) used: 12.93 GiB (5.5%) fs: ext4 
           dev: /dev/sda2 maj-min: 8:2 
           ID-2: /boot/efi raw-size: 511.5 MiB size: 510.5 MiB (99.80%) used: 28 MiB (5.5%) 
           fs: vfat dev: /dev/sda1 maj-min: 8:1 
Swap:      Alert: No swap data was found. 
Sensors:   System Temperatures: cpu: 27.8 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Repos:     Packages: 2390 note: see --pkg apt: 2385 lib: 1312 flatpak: 5 
           No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb https://quantum-mirror.hu/mirrors/pub/mx-linux/packages/mx/repo/ bullseye main non-free
           2: deb https://quantum-mirror.hu/mirrors/pub/mx-linux/packages/mx/repo/ bullseye ahs
           Active apt repos in: /etc/apt/sources.list.d/softmaker.list 
           1: deb https://shop.softmaker.com/repo/apt stable non-free
Info:      Processes: 245 Uptime: 45m wakeups: 1 Memory: 14.53 GiB used: 2.51 GiB (17.3%) 
           Init: SysVinit v: 2.96 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: 10.2.1 
           alt: 10 Client: shell wrapper v: 5.1.4-release inxi: 3.3.06 
Boot Mode: UEFI
Homo Homini Lupus Est

User avatar
neogeo
Posts: 85
Joined: Wed Jun 22, 2022 5:39 am

Re: Viber problem, HELP needed!

#2 Post by neogeo »

Any Help/Advice please?!?!
Homo Homini Lupus Est

User avatar
markol
Posts: 416
Joined: Sat Jan 30, 2021 8:33 am

Re: Viber problem, HELP needed!

#3 Post by markol »

Have you checked the log files/messages?

Is there anything if you run

Code: Select all

/opt/viber/Viber %u
in terminal?


Bonus: run sudo dpkg-reconfigure locales

User avatar
neogeo
Posts: 85
Joined: Wed Jun 22, 2022 5:39 am

Re: Viber problem, HELP needed!

#4 Post by neogeo »

Hello.
I'm late replying because I didn't get any post notification :(

So, You are right about Viber run output. Error is in Qt6 environment (as Google says) and a couple of a keyboards choosen... I must remove all Serbian keyboards from list and left only one English UK and Viber runned like a charm...
Is there any way to run Viber in Qt5 environment or something else solution because i need Serbian Keyboards (Latin and Cyrilic) ???

THX

P.S. Here is an Viber running output from terminal:

Code: Select all

qt.webenginecontext: 

GLImplementation: desktop
Surface Type: OpenGL
Surface Profile: CompatibilityProfile
Surface Version: 4.6
Using Default SG Backend: yes
Using Software Dynamic GL: no
Using Angle: no

Init Parameters:
  *  allow-loopback-in-peer-connection  
  *  application-name ViberPC 
  *  autoplay-policy no-user-gesture-required 
  *  browser-subprocess-path /opt/viber/libexec/QtWebEngineProcess 
  *  create-default-gl-context  
  *  disable-features DnsOverHttpsUpgrade,ConsolidatedMovementXY,InstalledApp,BackgroundFetch,WebOTP,WebPayments,WebUSB,PictureInPicture,AudioServiceOutOfProcess 
  *  disable-setuid-sandbox  
  *  disable-speech-api  
  *  enable-features NetworkServiceInProcess,TracingServiceInProcess,NetworkServiceInProcess 
  *  enable-threaded-compositing  
  *  enable-usermedia-screen-capture  
  *  in-process-gpu  
  *  use-gl desktop 

xkbcommon: ERROR: Couldn't process include statement for 'gb(latinyz)'
xkbcommon: ERROR: Abandoning symbols file "(unnamed)"
xkbcommon: ERROR: Failed to compile xkb_symbols
xkbcommon: ERROR: Failed to compile keymap
[31942:31974:0917/081353.874461:FATAL:xkb_keyboard_layout_engine.cc(640)] Keymap file failed to load: gb-latinyz
Trace/breakpoint trap
I have erased all additionall keyboards except GB and all working perfectly. When i turned back Serbian Keyboards, Viber won't start anymore :(
My default SYS format is en_GB and a default SYS language is British English.
Last edited by neogeo on Sat Sep 17, 2022 2:31 am, edited 2 times in total.
Homo Homini Lupus Est

User avatar
JayM
Posts: 6796
Joined: Tue Jan 08, 2019 3:47 am

Re: Viber problem, HELP needed!

#5 Post by JayM »

@neogeo Please edit your post using the pencil icon
Image
to wrap the information inside of code tags as per the forum rules (which please read.) Example: [code]log file contents, configuration file contents and terminal text go here[/code]

Code: Select all

to make it look like this, which is a lot easier to read for large amounts of text:
1. It really stands out as being separate from the text that you're typing due to the different background and font colors
2. It also puts it inside of its own little frame with its own scrollbars, making it easier to navigate.

To do this, select the text by dragging your mouse over it while holding the left button down then click the </> icon in the forum's editor's toolbar and click the Submit button.
Image
Thanks.
Please read the Forum Rules, How To Ask For Help, How to Break Your System and Don't Break Debian. Always include your full Quick System Info (QSI) with each and every new help request.

User avatar
neogeo
Posts: 85
Joined: Wed Jun 22, 2022 5:39 am

Re: Viber problem, HELP needed!

#6 Post by neogeo »

THX
Code solved :) as You suggest (hope so) but Viber problem still persist :(
Homo Homini Lupus Est

User avatar
JayM
Posts: 6796
Joined: Tue Jan 08, 2019 3:47 am

Re: Viber problem, HELP needed!

#7 Post by JayM »

neogeo wrote: Sat Sep 17, 2022 1:59 am So, You are right about Viber run output. Error is in Qt6 environment (as Google says) and a couple of a keyboards choosen... I must remove all Serbian keyboards from list and left only one English UK and Viber runned like a charm...
Is there any way to run Viber in Qt5 environment or something else solution because i need Serbian Keyboards (Latin and Cyrilic) ???
Apparently their app doesn't currently support Serbian keyboards so you would want to ask Viber to add such support. Meanwhile, is Viber working on your phone?

Edit: I just had another idea. Download the Xfce version of MX-21 AHS, use MX Live USB Maker to burn it to a spare USB flash drive stick, boot from it with persistence enabled, download Viber's .deb file for Ubuntu (which works on MX also), right-click on it in the Thunar file manager, select install DEB files and install Viber, then test it. That will tell you if the issue is with the keyboard or with qt5 as Xcfe is GTK-based.
Last edited by JayM on Sat Sep 17, 2022 4:03 am, edited 1 time in total.
Please read the Forum Rules, How To Ask For Help, How to Break Your System and Don't Break Debian. Always include your full Quick System Info (QSI) with each and every new help request.

User avatar
neogeo
Posts: 85
Joined: Wed Jun 22, 2022 5:39 am

Re: Viber problem, HELP needed!

#8 Post by neogeo »

On my phone Viber is working like a charm.
Homo Homini Lupus Est

User avatar
JayM
Posts: 6796
Joined: Tue Jan 08, 2019 3:47 am

Re: Viber problem, HELP needed!

#9 Post by JayM »

neogeo wrote: Sat Sep 17, 2022 3:57 am On my phone Viber is working like a charm.
Good, then you at least have that to use so there's no real urgency in getting their Linux desktop client working (though I understand that it can be a lot more difficult to type on a smartphone's or iphone's touchscreen keyboard vs. a regular keyboard on a computer.)
Please read the Forum Rules, How To Ask For Help, How to Break Your System and Don't Break Debian. Always include your full Quick System Info (QSI) with each and every new help request.

User avatar
neogeo
Posts: 85
Joined: Wed Jun 22, 2022 5:39 am

Re: Viber problem, HELP needed!  [Solved]

#10 Post by neogeo »

I googled a bit and found the following solution. The culprit is the x environment, which does not load the keyboard-related settings well. Here's a temporary sollution:
- - My sys keyboard layouts are set as us,rs,rs, but stackkbmap gives me strange output that prevents Viber from starting:

Code: Select all

$ setxkbmap -query
rules:      evdev
model:      pc101
layout:     us,rs,rs
variant:    ,latinyz,yz
options:    terminate:ctrl_alt_bksp,grp_led:scroll,grp:alt_shift_toggle
When i set the parameters with the same command so that there is a space in the first place like this

Code: Select all

setxkbmap -variant " ,latinyz,yz"
, then I get the following output

Code: Select all

$ setxkbmap -query
rules:      evdev
model:      pc101
layout:     us,rs,rs
variant:     ,latinyz,yz
options:    terminate:ctrl_alt_bksp,grp_led:scroll,grp:alt_shift_toggle
and Viber starts quite normally!
So i put

Code: Select all

setxkbmap -variant " ,latinyz,yz"
to bi Logon executable with Admin privilegies and Voila. All working like a charm!
Homo Homini Lupus Est

Post Reply

Return to “Software / Configuration”