Den 09.07.2024 22:00, skrev Terje J. Hanssen:
Den 09.07.2024 17:35, skrev Terje J. Hanssen:
Den 09.07.2024 02:45, skrev Andrew Randrianasulu:
вт, 9 июл. 2024 г., 03:19 Terje J. Hanssen via Cin
<[email protected]>:
AppImageLauncher 2.2.0 build 2022 cause several CinGG launch
errors on current openSUSE Tw Slowroll w/Gnome 46.2
https://github.com/TheAssassin/AppImageLauncher/releases/tag/continuous
Any solution to solve this?
no idea, never used that.
May be rebuild launcher itself on current OS?
Would possibly be the best, but out of scope for me.
And the same error messages occure both on the LTS Leap 15.6 and on
the progressive Tw Slowroll.
Change gtk icon theme?
Well, I haven't tried or changed that. Use the Gnome default.
Regarding CinGG theme, I have wondered what cause legacy desktop keep
legacy CinGG program window with grey left and top panels and some
red buttons,
It's visually better to exemplify this with images:
In the previous CinGG Quickstart, Figure 2 and Figure 7
https://cinelerra-gg.org/download/CinelerraGG_Quickstart.pdf
which except for the FFmeg button looks similar as Cinelerra-cv
http://cinelerra-cv.wikidot.com/cincv-manual-en:program-window
while newer installations get sharper black and white and green buttons?
as in the current CinGG manual
https://cinelerra-gg.org/download/CinelerraGG_Manual/Video_Audio_Tracks_Navigati.html#fig:patchbay
The differences is found in Settings > Preferences > Appearance : Layout
So my own idea is that when installing newer CinGG versions, existing
legacy layout settings won't be overwritten.
Try few tips from
https://askubuntu.com/questions/1351607/gtk-warning-could-not-load-a-pixbuf-from-icon-theme
try to run apps from appimages via this launcher as root and see if
problem still here? If it works as root may be look into
https://bbs.archlinux.org/viewtopic.php?id=261143
for permission fix?
Read that, but I haven't tried to change the permissions, because it
seemed not clear if they should be 755 or 644 or both.
No error messages when starting the CinGG appimage as root in the
terminal, only as user in a terminal. And no error message when
starting from the GUI integrated launcher icon. So I wonder if these
confusing messages can be seen as harmless(?)
As a workaround to cleanup, I tried to delete the installed
Appimagelauncher rpm after the CinGG gui integration, and then the
error messages was gone also as user in a terminal.
(Not comparable, but the current CinGG rpm build which is
possible to install on openSUSE Leap 15.6, cause no error)
./CinGG-20240630-x86_64_32607d503797959daeea6f4f2297ab88.AppImage
/usr/bin/AppImageLauncher: /lib64/libcurl.so.4: no version
information available (required by
/usr/bin/../lib/x86_64-linux-gnu/appimagelauncher/libappimageupdate.so)
** (AppImageLauncher:6412): WARNING **: 01:08:12.144: Pixbuf
theme: Cannot load pixmap file
/usr/share/themes/Adwaita/gtk-2.0/assets/progressbar-horz-trough.png:
Feil under lasting av bilde
«/usr/share/themes/Adwaita/gtk-2.0/assets/progressbar-horz-trough.png»:
Fatal feil i PNG-bildefil: bad parameters to zlib
(AppImageLauncher:6412): GdkPixbuf-CRITICAL **: 01:08:12.144:
gdk_pixbuf_get_width: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
(AppImageLauncher:6412): GdkPixbuf-CRITICAL **: 01:08:12.144:
gdk_pixbuf_get_height: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
** (AppImageLauncher:6412): WARNING **: 01:08:12.144: Invalid
borders specified for theme pixmap:
/usr/share/themes/Adwaita/gtk-2.0/assets/progressbar-horz-trough.png,
borders don't fit within the image
(AppImageLauncher:6412): GdkPixbuf-CRITICAL **: 01:08:12.144:
gdk_pixbuf_get_n_channels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
(AppImageLauncher:6412): GdkPixbuf-CRITICAL **: 01:08:12.144:
gdk_pixbuf_get_pixels_with_length: assertion 'GDK_IS_PIXBUF
(pixbuf)' failed
........ and severak more
--
Cin mailing list
[email protected]
https://lists.cinelerra-gg.org/mailman/listinfo/cin
--
Cin mailing list
[email protected]
https://lists.cinelerra-gg.org/mailman/listinfo/cin
