Bug 33310 - Nheko doesn't work in Lxqt Desktop nor in Xfce, but works after installing qtdeclarative5
Summary: Nheko doesn't work in Lxqt Desktop nor in Xfce, but works after installing qt...
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 9
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard: MGA9-64-OK
Keywords: advisory, validated_update
Depends on:
Blocks:
 
Reported: 2024-06-17 08:57 CEST by Jose Manuel López
Modified: 2024-07-01 08:36 CEST (History)
6 users (show)

See Also:
Source RPM: nheko-0.11.3-4.1.mga9
CVE:
Status comment:


Attachments
Nheko terminal output (19.52 KB, text/plain)
2024-06-17 08:59 CEST, Jose Manuel López
Details
Nheko with mesa 24.09 (49.77 KB, image/jpeg)
2024-06-20 09:33 CEST, Jose Manuel López
Details

Description Jose Manuel López 2024-06-17 08:57:57 CEST
Description of problem: Nheko does not boot into the Lxqt desktop environment. It may be due to the latest Plasma updates. I have Kwallet installed (which it also depends on to start), and before it worked for me.

Version-Release number of selected component (if applicable): Nheko and Lxqt desktop


How reproducible: Install Nheko in Lxqt Desktop and run.
Comment 1 Jose Manuel López 2024-06-17 08:59:39 CEST
Created attachment 14573 [details]
Nheko terminal output

I attach nheko terminal output. Here appears various bugs and nheko don't boot.

CC: (none) => joselp

Comment 2 katnatek 2024-06-17 19:44:54 CEST
Not sure what can be I not have this issue, I found some bugs in other applications with the same message, but I don't know how can be related

* Is one one you AMD systems? -> 
 Try uninstall amdgpupro , Not works? -> Then reinstall amdgpupro

* Install vdpauinfo , and libva-utils then run

vdpauinfo

and 

vainfo

Look if one complain about a missing file
Comment 3 Lewis Smith 2024-06-17 20:37:32 CEST
I do not understand comment 0: "Nheko does not boot into the Lxqt desktop environment".; which implies it is something pre-desktop.
Yet it is described as an application:
Summary     : Desktop client for the Matrix protocol
so I think you mean 'does not boot in LxQt...'

Please fill in the Source RPM field.

"Nheko don't work in Lxqt Desktop" makes more sense. And begs the obvious question "Does it work on other desktops?". I do not have a Cauldron system, so cannot try that.

BTAIM katnatek is fielding this. If you pass it to packagers, use pkg-bugs.
Comment 4 Jose Manuel López 2024-06-17 20:39:40 CEST
My system in this case is an Intel Atom, I have tried what Katnatek indicates in comment 2 and it still does not work. The terminal output after executing the two commands is this:

[jose@localhost ~]$ vdpauinfo
display: :0   screen: 0
Failed to open VDPAU backend libvdpau_va_gl.so: cannot open shared object file: No such file or directory
Error creating VDPAU device: 1
[jose@localhost ~]$ vainfo
Trying display: wayland
Trying display: x11
libva info: VA-API version 1.21.0
libva info: Trying to open /usr/lib64/dri/i915_drv_video.so
libva info: va_openDriver() returns -1
vaInitialize failed with error code -1 (unknown libva error),exit
[jose@localhost ~]$
Comment 5 Jose Manuel López 2024-06-17 20:53:25 CEST
I clarify that it does not work in Lightdm on the same computer either, so we can say that it may not be the desktop environment. 

I don't have another team with Lxqt to ensure it.
Comment 6 Jose Manuel López 2024-06-17 21:04:12 CEST
This is output from terminal of vdpauinfo: 

[jose@localhost ~]$ vdpauinfo
display: :0   screen: 0
libva info: VA-API version 1.21.0
libva info: Trying to open /usr/lib64/dri/i915_drv_video.so
libva info: va_openDriver() returns -1
API version: 1
Information string: OpenGL/VAAPI backend for VDPAU

Video surface:

name   width height types
-------------------------------------------
420     4096  4096  NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 NV24 YV24 P010 P016 Y_U_V_444_16 
422     4096  4096  NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 NV24 YV24 P010 P016 Y_U_V_444_16 
444     4096  4096  NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 NV24 YV24 P010 P016 Y_U_V_444_16 
420_16  4096  4096  NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 NV24 YV24 P010 P016 Y_U_V_444_16 
422_16  4096  4096  NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 NV24 YV24 P010 P016 Y_U_V_444_16 
444_16  4096  4096  NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 NV24 YV24 P010 P016 Y_U_V_444_16 

Decoder capabilities:

name                        level macbs width height
----------------------------------------------------
MPEG1                          --- not supported ---
MPEG2_SIMPLE                   --- not supported ---
MPEG2_MAIN                     --- not supported ---
H264_BASELINE                  --- not supported ---
H264_MAIN                      --- not supported ---
H264_HIGH                      --- not supported ---
VC1_SIMPLE                     --- not supported ---
VC1_MAIN                       --- not supported ---
VC1_ADVANCED                   --- not supported ---
MPEG4_PART2_SP                 --- not supported ---
MPEG4_PART2_ASP                --- not supported ---
DIVX4_QMOBILE                  --- not supported ---
DIVX4_MOBILE                   --- not supported ---
DIVX4_HOME_THEATER             --- not supported ---
DIVX4_HD_1080P                 --- not supported ---
DIVX5_QMOBILE                  --- not supported ---
DIVX5_MOBILE                   --- not supported ---
DIVX5_HOME_THEATER             --- not supported ---
DIVX5_HD_1080P                 --- not supported ---
H264_CONSTRAINED_BASELINE      --- not supported ---
H264_EXTENDED                  --- not supported ---
H264_PROGRESSIVE_HIGH          --- not supported ---
H264_CONSTRAINED_HIGH          --- not supported ---
H264_HIGH_444_PREDICTIVE       --- not supported ---
VP9_PROFILE_0                  --- not supported ---
VP9_PROFILE_1                  --- not supported ---
VP9_PROFILE_2                  --- not supported ---
VP9_PROFILE_3                  --- not supported ---
HEVC_MAIN                      --- not supported ---
HEVC_MAIN_10                   --- not supported ---
HEVC_MAIN_STILL                --- not supported ---
HEVC_MAIN_12                   --- not supported ---
HEVC_MAIN_444                  --- not supported ---
HEVC_MAIN_444_10               --- not supported ---
HEVC_MAIN_444_12               --- not supported ---
AV1_MAIN                       --- not supported ---
AV1_HIGH                       --- not supported ---
AV1_PROFESSIONAL               --- not supported ---

Output surface:

name              width height nat types
----------------------------------------------------
B8G8R8A8          2048  2048    y  
R8G8B8A8          2048  2048    y  
R10G10B10A2       2048  2048    y  
B10G10R10A2       2048  2048    y  
A8                2048  2048    y  

Bitmap surface:

name              width height
------------------------------
B8G8R8A8          2048  2048
R8G8B8A8          2048  2048
R10G10B10A2       2048  2048
B10G10R10A2       2048  2048
A8                2048  2048

Video mixer:

feature name                    sup
------------------------------------
DEINTERLACE_TEMPORAL             -
DEINTERLACE_TEMPORAL_SPATIAL     -
INVERSE_TELECINE                 -
NOISE_REDUCTION                  -
SHARPNESS                        -
LUMA_KEY                         -
HIGH QUALITY SCALING - L1        -
HIGH QUALITY SCALING - L2        -
HIGH QUALITY SCALING - L3        -
HIGH QUALITY SCALING - L4        -
HIGH QUALITY SCALING - L5        -
HIGH QUALITY SCALING - L6        -
HIGH QUALITY SCALING - L7        -
HIGH QUALITY SCALING - L8        -
HIGH QUALITY SCALING - L9        -

parameter name                  sup      min      max
-----------------------------------------------------
VIDEO_SURFACE_WIDTH              -  
VIDEO_SURFACE_HEIGHT             -  
CHROMA_TYPE                      -  
LAYERS                           -  

attribute name                  sup      min      max
-----------------------------------------------------
BACKGROUND_COLOR                 -  
CSC_MATRIX                       -  
NOISE_REDUCTION_LEVEL            -  
SHARPNESS_LEVEL                  -  
LUMA_KEY_MIN_LUMA                -  
LUMA_KEY_MAX_LUMA                -  


[jose@localhost ~]$
Comment 7 katnatek 2024-06-18 00:41:20 CEST
(In reply to Jose Manuel López from comment #4)
> My system in this case is an Intel Atom, I have tried what Katnatek
> indicates in comment 2 and it still does not work. The terminal output after
> executing the two commands is this:
> 
> [jose@localhost ~]$ vdpauinfo
> display: :0   screen: 0
> Failed to open VDPAU backend libvdpau_va_gl.so: cannot open shared object
> file: No such file or directory
>
urpmf libvdpau_va_gl.so -f
lib64vdpau-va-gl1-0.4.2-5.mga9.x86_64:/usr/lib64/vdpau/libvdpau_va_gl.so.1

Try installing lib64vdpau-va-gl1

I am reformatting my VM to see if I can reproduce
Comment 8 katnatek 2024-06-18 01:52:21 CEST
Oh this is in cauldron ups, I will try again tomorrow I hope
Comment 9 Jose Manuel López 2024-06-18 08:50:35 CEST
I I have tried to install nheko un Xfce desktop in the same computer. The bug is here still.
Comment 10 katnatek 2024-06-19 03:12:49 CEST Comment hidden (obsolete)
Comment 11 katnatek 2024-06-20 03:14:23 CEST
Conversations with Jose Manuel López brings to light that is a Mageia 9 system so forget the qtdeclarative6 thing, that is a bug for cualdron

Source RPM: (none) => nheko-0.11.3-4.1.mga9.src.rpm
Hardware: All => x86_64
Version: Cauldron => 9

katnatek 2024-06-20 03:29:06 CEST

Source RPM: nheko-0.11.3-4.1.mga9.src.rpm => nheko-0.11.3-4.1.mga9,mesa-24.0.9-1.mga9.tainted,mesa-24.0.9-1.mga9

Comment 12 katnatek 2024-06-20 03:29:43 CEST
Adding mesa package because we suspect of the recent update
Comment 13 Jose Manuel López 2024-06-20 09:27:02 CEST
Hello,

Steps to check:

- Reinstallation of the clean system.
- Nheko installation.
- Nheko Startup Test. It doesn't start.
- Installation of qtdeclarative5.
- Nheko startup test, now it works correctly, so qtdeclarative should be marked as a dependency.
- System update by unchecking everything related to Xorg and Mesa and reboot.
- Nheko Startup Test. It's still working.
- Installing Xorg updates and reboot.
- Nheko Startup Test. It's still working.
- Installation of Mesa updates and reboot.
- Nheko startup test, it starts, but the letters in the application have been lost, you can't see the conversations, or the titles, or anything, just the icons.
Comment 14 Jose Manuel López 2024-06-20 09:33:09 CEST
Created attachment 14576 [details]
Nheko with mesa 24.09

This is the image of Nehko with Mesa version 24.09, as you can see, the texts do not appear in the application.
Comment 15 Marja Van Waes 2024-06-20 21:32:35 CEST
(In reply to Jose Manuel López from comment #13)
> Hello,
> 
> Steps to check:
> 
> - Reinstallation of the clean system.
> - Nheko installation.
> - Nheko Startup Test. It doesn't start.
> - Installation of qtdeclarative5.
> - Nheko startup test, now it works correctly, so qtdeclarative should be
> marked as a dependency.

Assigning to the registered Nheko maintainer.

> - System update by unchecking everything related to Xorg and Mesa and reboot.
> - Nheko Startup Test. It's still working.
> - Installing Xorg updates and reboot.
> - Nheko Startup Test. It's still working.
> - Installation of Mesa updates and reboot.
> - Nheko startup test, it starts, but the letters in the application have
> been lost, you can't see the conversations, or the titles, or anything, just
> the icons.

That's a different bug. I'll leave it to the Nheko maintainer to decide whether a separate bug report is needed

Assignee: bugsquad => chb0
CC: (none) => marja11
Summary: Nheko don't work in Lxqt Desktop => Nheko doesn't work in Lxqt Desktop nor in Xfce, but works after installing qtdeclarative5

Comment 16 christian barranco 2024-06-21 19:10:14 CEST
Sorry, the thread is a bit confusing. Is it so the need is just to add qtdeclarative5 as a dependency?
Comment 17 katnatek 2024-06-21 21:01:30 CEST
(In reply to christian barranco from comment #16)
> Sorry, the thread is a bit confusing. Is it so the need is just to add
> qtdeclarative5 as a dependency?

Yes but also recent mesa update produce some issues in the system of the reporter
Comment 18 christian barranco 2024-06-22 10:11:05 CEST
Is the mesa related issue on MGA9 ou Cauldron?
Comment 19 katnatek 2024-06-22 22:38:43 CEST
(In reply to christian barranco from comment #18)
> Is the mesa related issue on MGA9 ou Cauldron?

9 as is stated in version and versions of src.rpms of this report, similar lack of require on qtdeclarative was fixed on bug#33318
Comment 20 christian barranco 2024-06-23 11:37:28 CEST
(In reply to katnatek from comment #19)
> (In reply to christian barranco from comment #18)
> > Is the mesa related issue on MGA9 ou Cauldron?
> 
> 9 as is stated in version and versions of src.rpms of this report, similar
> lack of require on qtdeclarative was fixed on bug#33318

Hi. You lost me again.

What I'd like to know:
* Are the qtdeclarative and mesa issues different or the same issue?
* If they are different, do they apply on MGA9 or Cauldron, or both?
Comment 21 katnatek 2024-06-23 20:58:27 CEST
(In reply to christian barranco from comment #20)
> (In reply to katnatek from comment #19)
> > (In reply to christian barranco from comment #18)
> > > Is the mesa related issue on MGA9 ou Cauldron?
> > 
> > 9 as is stated in version and versions of src.rpms of this report, similar
> > lack of require on qtdeclarative was fixed on bug#33318
> 
> Hi. You lost me again.
> 
> What I'd like to know:
> * Are the qtdeclarative and mesa issues different or the same issue?
> * If they are different, do they apply on MGA9 or Cauldron, or both?

I guess are different bugs detected on same application
The lack of qtdeclarative5 as require is for Mageia 9
In cauldron I report lack of qtdeclarative6 as requires is already fixed

Please solve just lack of qtdeclarative5 as require in Mageia 9 and the reporter must open other bug for his mesa issues, I remove the mesa packages from SRPMS

Source RPM: nheko-0.11.3-4.1.mga9,mesa-24.0.9-1.mga9.tainted,mesa-24.0.9-1.mga9 => nheko-0.11.3-4.1.mga9

Comment 22 Jose Manuel López 2024-06-24 09:13:45 CEST
They are two different errors.

On the one hand, the qtdeclarative5 dependency makes Nheko start correctly on my computer.

On the other hand, the update to Mesa 24.09 breaks the graphical aspect of the application, preventing you from seeing the texts of both messages and the entire application, as shown in the attached file.

As Katnatek indicates in comment 21, we leave this bug for qtdeclarative5, necessary in Mageia 9 and I open another bug for Nheko and mesa 24.09.

Greetings!
katnatek 2024-06-25 20:44:55 CEST

CC: (none) => j.alberto.vc

Comment 23 Morgan Leijström 2024-06-26 08:35:50 CEST
(In reply to Jose Manuel López from comment #22)
> I open another bug for Nheko and mesa 24.09.

-> The mesa bug is bug 33324

CC: (none) => fri

Comment 24 christian barranco 2024-06-29 12:17:39 CEST
Ready for QA!

nheko-zsh-completion-0.11.3-4.2.mga9.noarch.rpm
nheko-0.11.3-4.2.mga9.x86_64.rpm

Assignee: chb0 => qa-bugs

Comment 25 katnatek 2024-06-29 19:52:11 CEST
RH mageia x86_64

rpm -q qtdeclarative5
qtdeclarative5-5.15.7-1.mga9

rpm -e qtdeclarative5-5.15.7-1.mga9 --nodeps

LC_ALL=C rpm -q qtdeclarative5
package qtdeclarative5 is not installed

LC_ALL=C urpmi --auto --auto-update
medium "QA Testing (32-bit)" is up-to-date
medium "QA Testing (64-bit)" is up-to-date
medium "Core Release (distrib1)" is up-to-date
medium "Core Updates (distrib3)" is up-to-date
medium "Nonfree Release (distrib11)" is up-to-date
medium "Nonfree Updates (distrib13)" is up-to-date
medium "Tainted Release (distrib21)" is up-to-date
medium "Tainted Updates (distrib23)" is up-to-date
medium "Core 32bit Release (distrib31)" is up-to-date
medium "Core 32bit Updates (distrib32)" is up-to-date
medium "Nonfree 32bit Release (distrib36)" is up-to-date
medium "Tainted 32bit Release (distrib41)" is up-to-date
medium "Tainted 32bit Updates (distrib42)" is up-to-date

    https://mirror.math.princeton.edu/pub/mageia/distrib/9/x86_64/media/core/release/qtdeclarative5-5.15.7-1.mga9.x86_64.rpm
installing /var/cache/urpmi/rpms/qtdeclarative5-5.15.7-1.mga9.x86_64.rpm                                                            
//home/katnatek/qa-testing/x86_64/nheko-0.11.3-4.2.mga9.x86_64.rpm
//home/katnatek/qa-testing/x86_64/nheko-zsh-completion-0.11.3-4.2.mga9.noarch.rpm
Preparing...                     ##################################################################################################
      1/3: qtdeclarative5        ##################################################################################################
      2/3: nheko-zsh-completion  ##################################################################################################
      3/3: nheko                 ##################################################################################################
      1/2: removing nheko-0.11.3-4.1.mga9.x86_64
                                 ##################################################################################################
      2/2: removing nheko-zsh-completion-0.11.3-4.1.mga9.noarch
                                 ##################################################################################################

Checking other requires recommends not detect regressions 

For  Jose Manuel López is possible that after you get this update you must reapply the workarround for mesa

Whiteboard: (none) => MGA9-64-OK
CC: (none) => andrewsfarm

katnatek 2024-06-29 19:57:49 CEST

Keywords: (none) => advisory

Comment 26 Thomas Andrews 2024-06-29 20:47:47 CEST
Validating this part, anyway.

Keywords: (none) => validated_update
CC: (none) => sysadmin-bugs

Comment 27 Jose Manuel López 2024-06-30 13:56:17 CEST
I have installed the new version and it starts, but it does not finish running, not even with the command indicated above for Mesa.
Comment 28 katnatek 2024-06-30 19:13:30 CEST
(In reply to Jose Manuel López from comment #27)
> I have installed the new version and it starts, but it does not finish
> running, not even with the command indicated above for Mesa.

I remove the validation for the moment
Please attach new log from terminal

Keywords: validated_update => (none)

Comment 29 Jose Manuel López 2024-06-30 22:04:00 CEST
I have uninstalled the application and reinstalled it and now it works correctly with the command indicated for table. 

I think we can close this bug.
Comment 30 Morgan Leijström 2024-07-01 08:36:50 CEST
Thank you for the new test Jose.
Validating.

Keywords: (none) => validated_update


Note You need to log in before you can comment on or make changes to this bug.