Re: [Cin] AppImage and libGL errors at CinGG startup

2023-05-27 Thread Andrew Randrianasulu via Cin
сб, 27 мая 2023 г., 17:53 Terje J. Hanssen :

>
>
> Den 27.05.2023 12:05, skrev Andrea paz:
>
> @Terje J. Hanssen
>  Noveau are very limiting and problematic (through no fault of those
> who make them, who do a very good job).
> If you have a fairly recent Nvidia you can try using the official open
> drivers: nvidia-open.
> With these drivers Nvidia equalizes with AMD. However, don't think
> they are completely open: just like AMD, they have brought the parts
> they want to keep closed into the firmware and leave only the open
> parts in the driver.
> For more information and a list of supported cards, 
> see:https://github.com/NVIDIA/open-gpu-kernel-modules
>
>
> @Andrea
>
> My legacy Nvidia card was not high-end, but it still works for me with
> Nouveau/Mesa for normal work without heavy graphical tasks.
> Previously I also used Nvidia's proprietary driver, which was (and still
> is) quite easy to install via their specific openSUSE repositories.
>
> But as I continuously upgrade my lp15.x and especially the Tumbleweed
> rolling release in a dual-boot setup, it became extra work and more error
> prone to keep up with Nvidia. Therefore I went with Nouveau as part of the
> official openSUSE lp15.x stablel and tw rolling releases:
>
> # inxi -SCMG
> System:Host: localhost.localdomain Kernel:
> 5.14.21-150400.24.63-default x86_64 bits: 64 Desktop: GNOME 41.9
>Distro: openSUSE Leap 15.4
> Machine:   Type: Desktop System: MSI product: MS-7971 v: 1.0 serial: N/A
>Mobo: MSI model: Z170-A PRO (MS-7971) v: 1.0 serial: GC16013847
> UEFI: American Megatrends v: 1.K0 date: 07/10/2018
> CPU:   Info: Quad Core model: Intel Core i7-6700K bits: 64 type: MT
> MCP cache: L2: 8 MiB
>Speed: 800 MHz min/max: 800/4200 MHz Core speeds (MHz): 1: 800
> 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800
> Graphics:  Device-1: NVIDIA GK208B [GeForce GT 730]
>

sounds reclock-able!

https://github.com/ventureoo/nouveau-reclocking

with additional links in readme ...

well, warning, may _increase_ instability due to higher power usage/thermal
output 



driver: nouveau v: kernel
>Device-2: Microdia Camera type: USB driver:
> snd-usb-audio,uvcvideo
>Device-3: MACROSILICON USB3.0 UHD type: USB driver:
> hid-generic,snd-usb-audio,usbhid,uvcvideo
>Display: server: X.Org 1.20.3 driver: loaded: nouveau unloaded:
> fbdev,modesetting,vesa resolution: 2560x1440~60Hz
>OpenGL: renderer: NV106 v: 4.3 Mesa 21.2.4
>
>
>
> Packages I have installed in additional for Nvidia are
>
> S  | Name  |
> Summary | Type
>
> ---+---+-+
> i  | kernel-firmware-nvidia| Kernel firmware files for Nvidia Tegra
> and graphics drivers | package
> i+ | nvidia-firmware-installer | Downloads and installs nVidia
> firmware  | package
>
>
>
> I have so far not tried NVIDIA Open GPU kernel modules, which according to
> this openSUSe blog seemingly work for Nvidias newer Turing/Ampere GPU
> platforms with Risc-V system processor.
> https://sndirsch.github.io/nvidia/2022/06/07/nvidia-opengpu.html
>
>
>
>
-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin


Re: [Cin] AppImage and libGL errors at CinGG startup

2023-05-27 Thread Terje J. Hanssen via Cin



Den 27.05.2023 12:05, skrev Andrea paz:

@Terje J. Hanssen
  Noveau are very limiting and problematic (through no fault of those
who make them, who do a very good job).
If you have a fairly recent Nvidia you can try using the official open
drivers: nvidia-open.
With these drivers Nvidia equalizes with AMD. However, don't think
they are completely open: just like AMD, they have brought the parts
they want to keep closed into the firmware and leave only the open
parts in the driver.
For more information and a list of supported cards, see:
https://github.com/NVIDIA/open-gpu-kernel-modules


@Andrea

My legacy Nvidia card was not high-end, but it still works for me with 
Nouveau/Mesa for normal work without heavy graphical tasks.
Previously I also used Nvidia's proprietary driver, which was (and still 
is) quite easy to install via their specific openSUSE repositories.


But as I continuously upgrade my lp15.x and especially the Tumbleweed 
rolling release in a dual-boot setup, it became extra work and more 
error prone to keep up with Nvidia. Therefore I went with Nouveau as 
part of the official openSUSE lp15.x stablel and tw rolling releases:


# inxi -SCMG
System:    Host: localhost.localdomain Kernel: 
5.14.21-150400.24.63-default x86_64 bits: 64 Desktop: GNOME 41.9

   Distro: openSUSE Leap 15.4
Machine:   Type: Desktop System: MSI product: MS-7971 v: 1.0 serial: N/A
   Mobo: MSI model: Z170-A PRO (MS-7971) v: 1.0 serial: 
GC16013847 UEFI: American Megatrends v: 1.K0 date: 07/10/2018
CPU:   Info: Quad Core model: Intel Core i7-6700K bits: 64 type: MT 
MCP cache: L2: 8 MiB
   Speed: 800 MHz min/max: 800/4200 MHz Core speeds (MHz): 1: 
800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800
Graphics:  Device-1: NVIDIA GK208B [GeForce GT 730] driver: nouveau v: 
kernel
   Device-2: Microdia Camera type: USB driver: 
snd-usb-audio,uvcvideo
   Device-3: MACROSILICON USB3.0 UHD type: USB driver: 
hid-generic,snd-usb-audio,usbhid,uvcvideo
   Display: server: X.Org 1.20.3 driver: loaded: nouveau 
unloaded: fbdev,modesetting,vesa resolution: 2560x1440~60Hz

   OpenGL: renderer: NV106 v: 4.3 Mesa 21.2.4



Packages I have installed in additional for Nvidia are

S  | Name  | 
Summary | Type

---+---+-+
i  | kernel-firmware-nvidia    | Kernel firmware files for Nvidia Tegra 
and graphics drivers | package
i+ | nvidia-firmware-installer | Downloads and installs nVidia 
firmware  | package




I have so far not tried NVIDIA Open GPU kernel modules, which according 
to this openSUSe blog seemingly work for Nvidias newer Turing/Ampere GPU 
platforms with Risc-V system processor.

https://sndirsch.github.io/nvidia/2022/06/07/nvidia-opengpu.html


-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin


Re: [Cin] AppImage and libGL errors at CinGG startup

2023-05-27 Thread Andrea paz via Cin
@Terje J. Hanssen
 Noveau are very limiting and problematic (through no fault of those
who make them, who do a very good job).
If you have a fairly recent Nvidia you can try using the official open
drivers: nvidia-open.
With these drivers Nvidia equalizes with AMD. However, don't think
they are completely open: just like AMD, they have brought the parts
they want to keep closed into the firmware and leave only the open
parts in the driver.
For more information and a list of supported cards, see:
https://github.com/NVIDIA/open-gpu-kernel-modules
-- 
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin


Re: [Cin] AppImage and libGL errors at CinGG startup

2023-05-26 Thread Andrew Randrianasulu via Cin
сб, 27 мая 2023 г., 03:40 Terje J. Hanssen :

> Phyllis and Andrew,
>
> Yes, Applications/CinGG-20230101-x86_64.AppImage resulted in the same
> errors.
>
> Over time I have added some (several) OBS community and other add--on
> repositories to Leap 15.4, which was on kernel version 6.2.
>
> I searhed my system for the claimed missing /usr/lib64/dri/nouveau_dri.so
> and found that Mesa-dri-nouveau - Mesa DRI plug-in for 3D acceleration via
> Nouveau contained nouveau_dri.so, which is necessary for Nouveau's 3D
> acceleration to work. It is packaged separately since it is still
> experimental.
> I then tried to install the latest
> Mesa-dri-nouveau-23.1.0~git20230218-lp154.7.1.x86_64 but lost my desktop ..
>

for nouveau-specific troubleshooting you can look at irc channel

https://nouveau.freedesktop.org/IrcChatLogs.html

#nouveau on www.oftc.net

may be something broke in latest kernel/mesa or interface between two 


> Ok, I had the console left and downgraded lp15.4 to more official and
> semi-official repos based on kernel 5.14.21-150400.24.63-default.
> Mesa-packages now are
>
> S  | Name | Type  | Version   | Arch   | Repository
>
> ---+--+---+---++-
> i+ | Mesa | pakke | 21.2.4-150400.68.12.1 | x86_64 |
> SUSE:SLE-15:Update
> i+ | Mesa | pakke | 21.2.4-150400.68.12.1 | x86_64 | Update
> repository with updates from SUSE Linux Enterprise 15
> i  | Mesa-demo-x  | pakke | 8.3.0-1.33| x86_64 | Main
> Repository
> i+ | Mesa-dri | pakke | 21.2.4-150400.68.12.1 | x86_64 |
> SUSE:SLE-15:Update
> i+ | Mesa-dri | pakke | 21.2.4-150400.68.12.1 | x86_64 | Update
> repository with updates from SUSE Linux Enterprise 15
> i+ | Mesa-dri-nouveau | pakke | 21.2.4-150400.68.12.1 | x86_64 |
> SUSE:SLE-15:Update
> i+ | Mesa-dri-nouveau | pakke | 21.2.4-150400.68.12.1 | x86_64 | Update
> repository with updates from SUSE Linux Enterprise 15
> i+ | Mesa-gallium | pakke | 21.2.4-150400.68.12.1 | x86_64 |
> SUSE:SLE-15:Update
> i+ | Mesa-gallium | pakke | 21.2.4-150400.68.12.1 | x86_64 | Update
> repository with updates from SUSE Linux Enterprise 15
> i+ | Mesa-libEGL1 | pakke | 21.2.4-150400.68.12.1 | x86_64 |
> SUSE:SLE-15:Update
> i+ | Mesa-libEGL1 | pakke | 21.2.4-150400.68.12.1 | x86_64 | Update
> repository with updates from SUSE Linux Enterprise 15
> i+ | Mesa-libGL1  | pakke | 21.2.4-150400.68.12.1 | x86_64 |
> SUSE:SLE-15:Update
> i+ | Mesa-libGL1  | pakke | 21.2.4-150400.68.12.1 | x86_64 | Update
> repository with updates from SUSE Linux Enterprise 15
> i  | Mesa-libglapi0   | pakke | 21.2.4-150400.68.12.1 | x86_64 |
> SUSE:SLE-15:Update
> i  | Mesa-libglapi0   | pakke | 21.2.4-150400.68.12.1 | x86_64 | Update
> repository with updates from SUSE Linux Enterprise 15
> i  | Mesa-libva   | pakke | 21.2.4-150400.68.12.1 | x86_64 |
> SUSE:SLE-15:Update
> i  | Mesa-libva   | pakke | 21.2.4-150400.68.12.1 | x86_64 | Update
> repository with updates from SUSE Linux Enterprise 15
>
>
> The libGL errors disappeared, while the AppImageLauncher: GdkPixbuf
> errors are still there at CinGG startup.
>
>
> Den 26.05.2023 23:39, skrev Phyllis Smith:
>
> Terje, also could you verify that the previous appimage still works that
> you had been using just to rule out O/S changes?
>
> On Fri, May 26, 2023 at 10:41 AM Terje J. Hanssen via Cin <
> cin@lists.cinelerra-gg.org> wrote:
>
>> I tried to start the latest CinGG Appimages in a terminal and got
>> several libGL errors. Any suggestions to the reason and how to solve it?
>>
>> 1) As user:
>>
>> terje@localhost:~/Applications>  ls -1 CinGG*
>> CinGG-20230430-x86_64_bb12884636d31e78f606210fbe8af744.AppImage
>> CinGG-20230430-x86_64-multibit_45292c165a611fccf83b42dca4a96209.AppImage
>>
>> terje@localhost:~/Applications>
>> ./CinGG-20230430-x86_64_bb12884636d31e78f606210fbe8af744.AppImage
>> /usr/bin/AppImageLauncher: /usr/lib64/libcurl.so.4: no version
>> information available (required by
>> /usr/bin/../lib/x86_64-linux-gnu/appimagelauncher/libappimageupdate.so)
>>
>> ** (AppImageLauncher:22280): WARNING **: 16:25:48.400: Pixbuf theme:
>> Cannot load pixmap file
>> /usr/share/themes/Breeze/gtk-2.0/../assets/progressbar-trough.png: Feil
>> under lasting av bilde
>> «/usr/share/themes/Breeze/gtk-2.0/../assets/progressbar-trough.png»:
>> Fatal feil i PNG-bildefil: bad parameters to zlib
>>
>>
>> (AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400:
>> gdk_pixbuf_get_width: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
>>
>> (AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400:
>> gdk_pixbuf_get_height: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
>>
>> ** (AppImageLauncher:22280): WARNING **: 16:25:48.400: Invalid borders
>> specified for theme pixmap:
>> /usr/share/themes/Breeze/gtk-2.0/../assets/progressbar-trough.png,
>> borders don't fit within the 

Re: [Cin] AppImage and libGL errors at CinGG startup

2023-05-26 Thread Terje J. Hanssen via Cin

Phyllis and Andrew,

Yes, Applications/CinGG-20230101-x86_64.AppImage resulted in the same 
errors.


Over time I have added some (several) OBS community and other add--on 
repositories to Leap 15.4, which was on kernel version 6.2.


I searhed my system for the claimed missing 
/usr/lib64/dri/nouveau_dri.so and found that Mesa-dri-nouveau - Mesa DRI 
plug-in for 3D acceleration via Nouveau contained nouveau_dri.so, which 
is necessary for Nouveau's 3D acceleration to work. It is packaged 
separately since it is still experimental.
I then tried to install the latest 
Mesa-dri-nouveau-23.1.0~git20230218-lp154.7.1.x86_64 but lost my desktop ..


Ok, I had the console left and downgraded lp15.4 to more official and 
semi-official repos based on kernel 5.14.21-150400.24.63-default.

Mesa-packages now are

S  | Name | Type  | Version   | Arch   | Repository
---+--+---+---++-
i+ | Mesa | pakke | 21.2.4-150400.68.12.1 | x86_64 | 
SUSE:SLE-15:Update
i+ | Mesa | pakke | 21.2.4-150400.68.12.1 | x86_64 | Update 
repository with updates from SUSE Linux Enterprise 15
i  | Mesa-demo-x  | pakke | 8.3.0-1.33    | x86_64 | Main 
Repository
i+ | Mesa-dri | pakke | 21.2.4-150400.68.12.1 | x86_64 | 
SUSE:SLE-15:Update
i+ | Mesa-dri | pakke | 21.2.4-150400.68.12.1 | x86_64 | Update 
repository with updates from SUSE Linux Enterprise 15
i+ | Mesa-dri-nouveau | pakke | 21.2.4-150400.68.12.1 | x86_64 | 
SUSE:SLE-15:Update
i+ | Mesa-dri-nouveau | pakke | 21.2.4-150400.68.12.1 | x86_64 | Update 
repository with updates from SUSE Linux Enterprise 15
i+ | Mesa-gallium | pakke | 21.2.4-150400.68.12.1 | x86_64 | 
SUSE:SLE-15:Update
i+ | Mesa-gallium | pakke | 21.2.4-150400.68.12.1 | x86_64 | Update 
repository with updates from SUSE Linux Enterprise 15
i+ | Mesa-libEGL1 | pakke | 21.2.4-150400.68.12.1 | x86_64 | 
SUSE:SLE-15:Update
i+ | Mesa-libEGL1 | pakke | 21.2.4-150400.68.12.1 | x86_64 | Update 
repository with updates from SUSE Linux Enterprise 15
i+ | Mesa-libGL1  | pakke | 21.2.4-150400.68.12.1 | x86_64 | 
SUSE:SLE-15:Update
i+ | Mesa-libGL1  | pakke | 21.2.4-150400.68.12.1 | x86_64 | Update 
repository with updates from SUSE Linux Enterprise 15
i  | Mesa-libglapi0   | pakke | 21.2.4-150400.68.12.1 | x86_64 | 
SUSE:SLE-15:Update
i  | Mesa-libglapi0   | pakke | 21.2.4-150400.68.12.1 | x86_64 | Update 
repository with updates from SUSE Linux Enterprise 15
i  | Mesa-libva   | pakke | 21.2.4-150400.68.12.1 | x86_64 | 
SUSE:SLE-15:Update
i  | Mesa-libva   | pakke | 21.2.4-150400.68.12.1 | x86_64 | Update 
repository with updates from SUSE Linux Enterprise 15



The libGL errors disappeared, while the AppImageLauncher: GdkPixbuf 
errors are still there at CinGG startup.



Den 26.05.2023 23:39, skrev Phyllis Smith:
Terje, also could you verify that the previous appimage still works 
that you had been using just to rule out O/S changes?


On Fri, May 26, 2023 at 10:41 AM Terje J. Hanssen via Cin 
 wrote:


I tried to start the latest CinGG Appimages in a terminal and got
several libGL errors. Any suggestions to the reason and how to
solve it?

1) As user:

terje@localhost:~/Applications>  ls -1 CinGG*
CinGG-20230430-x86_64_bb12884636d31e78f606210fbe8af744.AppImage
CinGG-20230430-x86_64-multibit_45292c165a611fccf83b42dca4a96209.AppImage

terje@localhost:~/Applications>
./CinGG-20230430-x86_64_bb12884636d31e78f606210fbe8af744.AppImage
/usr/bin/AppImageLauncher: /usr/lib64/libcurl.so.4: no version
information available (required by
/usr/bin/../lib/x86_64-linux-gnu/appimagelauncher/libappimageupdate.so)

** (AppImageLauncher:22280): WARNING **: 16:25:48.400: Pixbuf theme:
Cannot load pixmap file
/usr/share/themes/Breeze/gtk-2.0/../assets/progressbar-trough.png:
Feil
under lasting av bilde
«/usr/share/themes/Breeze/gtk-2.0/../assets/progressbar-trough.png»:
Fatal feil i PNG-bildefil: bad parameters to zlib


(AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400:
gdk_pixbuf_get_width: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400:
gdk_pixbuf_get_height: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

** (AppImageLauncher:22280): WARNING **: 16:25:48.400: Invalid
borders
specified for theme pixmap:
/usr/share/themes/Breeze/gtk-2.0/../assets/progressbar-trough.png,
borders don't fit within the image

(AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400:
gdk_pixbuf_get_n_channels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400:
gdk_pixbuf_get_pixels_with_length: assertion 'GDK_IS_PIXBUF
(pixbuf)' failed

(AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400:

Re: [Cin] AppImage and libGL errors at CinGG startup

2023-05-26 Thread Phyllis Smith via Cin
Terje, also could you verify that the previous appimage still works that
you had been using just to rule out O/S changes?

On Fri, May 26, 2023 at 10:41 AM Terje J. Hanssen via Cin <
cin@lists.cinelerra-gg.org> wrote:

> I tried to start the latest CinGG Appimages in a terminal and got
> several libGL errors. Any suggestions to the reason and how to solve it?
>
> 1) As user:
>
> terje@localhost:~/Applications>  ls -1 CinGG*
> CinGG-20230430-x86_64_bb12884636d31e78f606210fbe8af744.AppImage
> CinGG-20230430-x86_64-multibit_45292c165a611fccf83b42dca4a96209.AppImage
>
> terje@localhost:~/Applications>
> ./CinGG-20230430-x86_64_bb12884636d31e78f606210fbe8af744.AppImage
> /usr/bin/AppImageLauncher: /usr/lib64/libcurl.so.4: no version
> information available (required by
> /usr/bin/../lib/x86_64-linux-gnu/appimagelauncher/libappimageupdate.so)
>
> ** (AppImageLauncher:22280): WARNING **: 16:25:48.400: Pixbuf theme:
> Cannot load pixmap file
> /usr/share/themes/Breeze/gtk-2.0/../assets/progressbar-trough.png: Feil
> under lasting av bilde
> «/usr/share/themes/Breeze/gtk-2.0/../assets/progressbar-trough.png»:
> Fatal feil i PNG-bildefil: bad parameters to zlib
>
>
> (AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400:
> gdk_pixbuf_get_width: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
>
> (AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400:
> gdk_pixbuf_get_height: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
>
> ** (AppImageLauncher:22280): WARNING **: 16:25:48.400: Invalid borders
> specified for theme pixmap:
> /usr/share/themes/Breeze/gtk-2.0/../assets/progressbar-trough.png,
> borders don't fit within the image
>
> (AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400:
> gdk_pixbuf_get_n_channels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
>
> (AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400:
> gdk_pixbuf_get_pixels_with_length: assertion 'GDK_IS_PIXBUF (pixbuf)'
> failed
>
> (AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400:
> gdk_pixbuf_get_rowstride: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
>
> (AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400:
> gdk_pixbuf_get_n_channels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
>
> (AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400:
> gdk_pixbuf_get_pixels_with_length: assertion 'GDK_IS_PIXBUF (pixbuf)'
> failed
>
> (AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400:
> gdk_pixbuf_get_rowstride: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
>
> (AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400:
> gdk_pixbuf_get_n_channels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
>
> (AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400:
> gdk_pixbuf_get_pixels_with_length: assertion 'GDK_IS_PIXBUF (pixbuf)'
> failed
>
> (AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400:
> gdk_pixbuf_get_rowstride: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
>
> (AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400:
> gdk_pixbuf_get_n_channels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
>
> (AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400:
> gdk_pixbuf_get_pixels_with_length: assertion 'GDK_IS_PIXBUF (pixbuf)'
> failed
>
> (AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400:
> gdk_pixbuf_get_rowstride: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
>
> (AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400:
> gdk_pixbuf_get_n_channels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
>
> (AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400:
> gdk_pixbuf_get_pixels_with_length: assertion 'GDK_IS_PIXBUF (pixbuf)'
> failed
>
> (AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400:
> gdk_pixbuf_get_rowstride: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
>
> (AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400:
> gdk_pixbuf_get_n_channels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
>
> (AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400:
> gdk_pixbuf_get_pixels_with_length: assertion 'GDK_IS_PIXBUF (pixbuf)'
> failed
>
> (AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400:
> gdk_pixbuf_get_rowstride: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
>
> (AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400:
> gdk_pixbuf_get_n_channels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
>
> (AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400:
> gdk_pixbuf_get_pixels_with_length: assertion 'GDK_IS_PIXBUF (pixbuf)'
> failed
>
> (AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400:
> gdk_pixbuf_get_rowstride: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
>
> (AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400:
> gdk_pixbuf_get_n_channels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
>
> (AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400:
> gdk_pixbuf_get_pixels_with_length: assertion 'GDK_IS_PIXBUF (pixbuf)'
> failed
>
> (AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400:
> gdk_pixbuf_get_rowstride: 

Re: [Cin] AppImage and libGL errors at CinGG startup

2023-05-26 Thread Andrew Randrianasulu via Cin
пт, 26 мая 2023 г., 19:41 Terje J. Hanssen via Cin <
cin@lists.cinelerra-gg.org>:

> I tried to start the latest CinGG Appimages in a terminal and got
> several libGL errors. Any suggestions to the reason and how to solve it?
>


may be Suse removed mesa3d part with nouveau (nvidia libre) driver? (it
tend to be slow on gpus past 750ti due to non-working gpu reclocking - due
to reclocking sub-processor on gpu demanding secured firmware ) Try to
look in package manager for *nouveau* - xf86 part is 2d driver, dri (.so)
is 3d part.

if you have multi-gpu setup try DRI_PRIME=1 (I had some artefacts on
2*Nvidia with nouveau and cingg with dri3 mode, but I do not have this
setup for re-testing anymore )

>
> 1) As user:
>
> terje@localhost:~/Applications>  ls -1 CinGG*
> CinGG-20230430-x86_64_bb12884636d31e78f606210fbe8af744.AppImage
> CinGG-20230430-x86_64-multibit_45292c165a611fccf83b42dca4a96209.AppImage
>
> terje@localhost:~/Applications>
> ./CinGG-20230430-x86_64_bb12884636d31e78f606210fbe8af744.AppImage
> /usr/bin/AppImageLauncher: /usr/lib64/libcurl.so.4: no version
> information available (required by
> /usr/bin/../lib/x86_64-linux-gnu/appimagelauncher/libappimageupdate.so)
>
> ** (AppImageLauncher:22280): WARNING **: 16:25:48.400: Pixbuf theme:
> Cannot load pixmap file
> /usr/share/themes/Breeze/gtk-2.0/../assets/progressbar-trough.png: Feil
> under lasting av bilde
> «/usr/share/themes/Breeze/gtk-2.0/../assets/progressbar-trough.png»:
> Fatal feil i PNG-bildefil: bad parameters to zlib
>
>
> (AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400:
> gdk_pixbuf_get_width: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
>
> (AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400:
> gdk_pixbuf_get_height: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
>
> ** (AppImageLauncher:22280): WARNING **: 16:25:48.400: Invalid borders
> specified for theme pixmap:
> /usr/share/themes/Breeze/gtk-2.0/../assets/progressbar-trough.png,
> borders don't fit within the image
>
> (AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400:
> gdk_pixbuf_get_n_channels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
>
> (AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400:
> gdk_pixbuf_get_pixels_with_length: assertion 'GDK_IS_PIXBUF (pixbuf)'
> failed
>
> (AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400:
> gdk_pixbuf_get_rowstride: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
>
> (AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400:
> gdk_pixbuf_get_n_channels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
>
> (AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400:
> gdk_pixbuf_get_pixels_with_length: assertion 'GDK_IS_PIXBUF (pixbuf)'
> failed
>
> (AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400:
> gdk_pixbuf_get_rowstride: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
>
> (AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400:
> gdk_pixbuf_get_n_channels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
>
> (AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400:
> gdk_pixbuf_get_pixels_with_length: assertion 'GDK_IS_PIXBUF (pixbuf)'
> failed
>
> (AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400:
> gdk_pixbuf_get_rowstride: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
>
> (AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400:
> gdk_pixbuf_get_n_channels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
>
> (AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400:
> gdk_pixbuf_get_pixels_with_length: assertion 'GDK_IS_PIXBUF (pixbuf)'
> failed
>
> (AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400:
> gdk_pixbuf_get_rowstride: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
>
> (AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400:
> gdk_pixbuf_get_n_channels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
>
> (AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400:
> gdk_pixbuf_get_pixels_with_length: assertion 'GDK_IS_PIXBUF (pixbuf)'
> failed
>
> (AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400:
> gdk_pixbuf_get_rowstride: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
>
> (AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400:
> gdk_pixbuf_get_n_channels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
>
> (AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400:
> gdk_pixbuf_get_pixels_with_length: assertion 'GDK_IS_PIXBUF (pixbuf)'
> failed
>
> (AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400:
> gdk_pixbuf_get_rowstride: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
>
> (AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400:
> gdk_pixbuf_get_n_channels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
>
> (AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400:
> gdk_pixbuf_get_pixels_with_length: assertion 'GDK_IS_PIXBUF (pixbuf)'
> failed
>
> (AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400:
> gdk_pixbuf_get_rowstride: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
>
> (AppImageLauncher:22280): 

[Cin] AppImage and libGL errors at CinGG startup

2023-05-26 Thread Terje J. Hanssen via Cin
I tried to start the latest CinGG Appimages in a terminal and got 
several libGL errors. Any suggestions to the reason and how to solve it?


1) As user:

terje@localhost:~/Applications>  ls -1 CinGG*
CinGG-20230430-x86_64_bb12884636d31e78f606210fbe8af744.AppImage
CinGG-20230430-x86_64-multibit_45292c165a611fccf83b42dca4a96209.AppImage

terje@localhost:~/Applications> 
./CinGG-20230430-x86_64_bb12884636d31e78f606210fbe8af744.AppImage
/usr/bin/AppImageLauncher: /usr/lib64/libcurl.so.4: no version 
information available (required by 
/usr/bin/../lib/x86_64-linux-gnu/appimagelauncher/libappimageupdate.so)


** (AppImageLauncher:22280): WARNING **: 16:25:48.400: Pixbuf theme: 
Cannot load pixmap file 
/usr/share/themes/Breeze/gtk-2.0/../assets/progressbar-trough.png: Feil 
under lasting av bilde 
«/usr/share/themes/Breeze/gtk-2.0/../assets/progressbar-trough.png»: 
Fatal feil i PNG-bildefil: bad parameters to zlib



(AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400: 
gdk_pixbuf_get_width: assertion 'GDK_IS_PIXBUF (pixbuf)' failed


(AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400: 
gdk_pixbuf_get_height: assertion 'GDK_IS_PIXBUF (pixbuf)' failed


** (AppImageLauncher:22280): WARNING **: 16:25:48.400: Invalid borders 
specified for theme pixmap:

/usr/share/themes/Breeze/gtk-2.0/../assets/progressbar-trough.png,
borders don't fit within the image

(AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400: 
gdk_pixbuf_get_n_channels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed


(AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400: 
gdk_pixbuf_get_pixels_with_length: assertion 'GDK_IS_PIXBUF (pixbuf)' failed


(AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400: 
gdk_pixbuf_get_rowstride: assertion 'GDK_IS_PIXBUF (pixbuf)' failed


(AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400: 
gdk_pixbuf_get_n_channels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed


(AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400: 
gdk_pixbuf_get_pixels_with_length: assertion 'GDK_IS_PIXBUF (pixbuf)' failed


(AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400: 
gdk_pixbuf_get_rowstride: assertion 'GDK_IS_PIXBUF (pixbuf)' failed


(AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400: 
gdk_pixbuf_get_n_channels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed


(AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400: 
gdk_pixbuf_get_pixels_with_length: assertion 'GDK_IS_PIXBUF (pixbuf)' failed


(AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400: 
gdk_pixbuf_get_rowstride: assertion 'GDK_IS_PIXBUF (pixbuf)' failed


(AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400: 
gdk_pixbuf_get_n_channels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed


(AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400: 
gdk_pixbuf_get_pixels_with_length: assertion 'GDK_IS_PIXBUF (pixbuf)' failed


(AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400: 
gdk_pixbuf_get_rowstride: assertion 'GDK_IS_PIXBUF (pixbuf)' failed


(AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400: 
gdk_pixbuf_get_n_channels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed


(AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400: 
gdk_pixbuf_get_pixels_with_length: assertion 'GDK_IS_PIXBUF (pixbuf)' failed


(AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400: 
gdk_pixbuf_get_rowstride: assertion 'GDK_IS_PIXBUF (pixbuf)' failed


(AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400: 
gdk_pixbuf_get_n_channels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed


(AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400: 
gdk_pixbuf_get_pixels_with_length: assertion 'GDK_IS_PIXBUF (pixbuf)' failed


(AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400: 
gdk_pixbuf_get_rowstride: assertion 'GDK_IS_PIXBUF (pixbuf)' failed


(AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400: 
gdk_pixbuf_get_n_channels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed


(AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400: 
gdk_pixbuf_get_pixels_with_length: assertion 'GDK_IS_PIXBUF (pixbuf)' failed


(AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400: 
gdk_pixbuf_get_rowstride: assertion 'GDK_IS_PIXBUF (pixbuf)' failed


(AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400: 
gdk_pixbuf_get_n_channels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed


(AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400: 
gdk_pixbuf_get_pixels_with_length: assertion 'GDK_IS_PIXBUF (pixbuf)' failed


(AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400: 
gdk_pixbuf_get_rowstride: assertion 'GDK_IS_PIXBUF (pixbuf)' failed


(AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400: 
gdk_pixbuf_get_n_channels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed


(AppImageLauncher:22280): GdkPixbuf-CRITICAL **: 16:25:48.400: 
gdk_pixbuf_get_pixels_with_length: assertion 'GDK_IS_PIXBUF (pixbuf)' failed


(AppImageLauncher:22280):