You are not logged in.
Pages: 1
Hey everyone!
I am looking for help with Jami. It started about a week ago right after I performed update/upgrade of my Devuan-testing (daedalus) installation. There were Mesa, QT and bunch of other cool software updates which I do not remember . Today I have performed another system update/upgrade and installed latest Debian-testing Jami client (20221213.0836.556a248~dfsg1-1) but the window issue is still there. Though the window looks totally blank (it is filled with desktop objects from below itself or desktop wallpaper) the arrow cursor transforms to "hand" or "input" cursor in some particular window areas. If I quit the client, its window just for a moment shows up its fully normal content and disappear.
console error output:
qrc:/mainview/components/ConversationSmartListContextMenu.qml:99:13: Unable to assign [undefined] to bool
Could not create display context: Could not find any FBConfig's to use (check attributes?)
(jami:30116): GStreamer-CRITICAL **: 20:29:51.271: gst_object_unref: assertion 'object != NULL' failed
Could not create display context: Could not find any FBConfig's to use (check attributes?)
I can upload full output if needed. !it is big!
By the way CoreCtrl window acts the same weird way now. Though fan control (curve) which I set up earlier works
fine.
I am guessing there could be some another Mesa bug. I tried RX 460 GPU instead of my primary RX 6600 and nothing changed. But when I swaped the system disk drive to a machine with Intel UHD 630 IGPU - jami acted FINE!
UPD. Not so FINE actually... Though the window looks ok, in about 2 minutes (I did several restart attempts) Jami is surely self terminated with following console output :
jami[3114]: segfault at 0 ip 00007f93f828e4a3 sp 00007fff502294b0 error 4 in libQt6Core.so.6.2.3[7f93f809f000+2e2000] likely on CPU 3 (core 3, socket 0)
[ 210.009859] Code: 11 45 00 41 0f 11 45 10 48 83 c4 28 5b 5d 41 5c 41 5d c3 0f 1f 40 00 41 55 41 54 55 48 89 f5 53 48 89 fb 48 89 f7 48 83 ec 38 <48> 8b 06 4c 8b 6e 08 48 89 54 24 08 ff 10 48 8b 74 24 08 48 85 c0
Last edited by mr12345 (2023-01-12 09:30:21)
I am just a Linux beginner enthusiast
Offline
So I kind of "managed" to get all the broken windows back to work. As I am sure of this has begin within first several days of january I thought it worth of a try. I just have rolled back to a old december `22-released kernel. So any latest kernel is not good for me for the time being.
And I had to swap original jami loader-file (I do not know how to call it ) for the one from the "debian 11 stable" deb-packet in order to stop the messenger crashing.
But the "kernel-mesa" problem is still persists and I will be happy to know what is wrong. Any help appreciated
I am just a Linux beginner enthusiast
Offline
Yesterday I tried again to use the latest kernel and it went FINE! No "kernel-mesa" issue or anything else so far! I really do not know what was all that. You could think this all was a joke but actually it was a spliter in my butt for about a month. Although I can say I am kinda happy to have bunch of new experience I got within this month.
I am just a Linux beginner enthusiast
Offline
Thanks for the report and marking this as solved.
Offline
Pages: 1